Method for transmitting and receiving signals in a wireless communication system and apparatus supporting the same

Abstract

According to an embodiment of the present invention, a method for transmitting and receiving a signal in a wireless communication system and an apparatus supporting the same include: receiving information about a PUSCH start symbol #K; and transmitting a PUSCH in a predetermined position based on a result of performing CAP. The predetermined position is determined based on a parameter related to the length of a CPE, and the length of the CPE is less than or equal to the length of an OFDM symbol.

Description

Technical Field

[0001] The present disclosure relates to a method and apparatus for transmitting and receiving signals in a wireless communication system. Background Art

[0002] Wireless access systems have been widely deployed to provide various types of communication services such as voice or data. Generally, wireless access systems are multiple access systems that support communication of multiple users by sharing available system resources (bandwidth, transmission power, etc.) among multiple users. For example, multiple access systems include code division multiple access (CDMA) systems, frequency division multiple access (FDMA) systems, time division multiple access (TDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, and single carrier frequency division multiple access (SC-FDMA) systems. Summary of the invention

[0003] Technical issues

[0004] A method and apparatus for efficiently performing wireless signal transmission and reception procedures are provided.

[0005] Those skilled in the art will understand that the objects that can be achieved by the present disclosure are not limited to those specifically described above, and the above and other objects that can be achieved by the present disclosure will be more clearly understood from the following detailed description.

[0006] Technical Solution

[0007] According to a first aspect of the present disclosure, a method performed by a user equipment (UE) in a wireless communication system is provided herein, the method comprising: receiving information for a physical uplink shared channel (PUSCH) start symbol #K; and transmitting the PUSCH at a specific position based on a result of performing a channel access procedure (CAP). The specific position may be determined based on a parameter related to a length of a cyclic prefix extension (CPE), and the length of the CPE may be equal to or less than the length of one orthogonal frequency division multiplexing (OFDM) symbol.

[0008] According to a second aspect of the present disclosure, a user equipment (UE) for use in a wireless communication system is provided herein, the UE comprising: at least one transceiver; at least one processor; and at least one computer memory, which is operatively connected to the at least one transceiver and the at least one processor and configured to cause the at least one transceiver and the at least one processor to perform operations when executed. The operations may include: receiving information for a physical uplink shared channel (PUSCH) start symbol #K; and sending the PUSCH at a specific location based on a result of performing a channel access procedure (CAP). The specific location may be determined based on a parameter related to the length of a cyclic prefix extension (CPE), and the length of the CPE may be equal to or less than the length of an orthogonal frequency division multiplexing (OFDM) symbol.

[0009] According to a third aspect of the present disclosure, a device for a user equipment (UE) is provided herein, the device comprising at least one processor and at least one memory, the at least one memory being configured to store one or more instructions that cause the at least one processor to perform operations. The operations may include: receiving information for a physical uplink shared channel (PUSCH) start symbol #K; and sending the PUSCH at a specific location based on a result of performing a channel access procedure (CAP). The specific location may be determined based on a parameter related to the length of a cyclic prefix extension (CPE), and the length of the CPE may be equal to or less than the length of an orthogonal frequency division multiplexing (OFDM) symbol.

[0010] According to a fourth aspect of the present disclosure, a processor-readable medium storing one or more instructions is provided herein, wherein the one or more instructions cause at least one processor to perform operations. The operations may include: receiving information for a physical uplink shared channel (PUSCH) start symbol #K; and sending the PUSCH at a specific position based on a result of performing a channel access procedure (CAP). The specific position may be determined based on a parameter related to the length of a cyclic prefix extension (CPE), and the length of the CPE may be equal to or less than the length of an orthogonal frequency division multiplexing (OFDM) symbol.

[0011] The parameter may be an integer such that the length of CPE is equal to or less than the length of one OFDM symbol, and the length of one OFDM symbol may be the symbol length of symbol #K.

[0012] The length of one OFDM symbol may vary based on the subcarrier spacing (SCS).

[0013] The parameters may be determined based on the subcarrier spacing (SCS).

[0014] The parameters may be determined based on the type of CAP.

[0015] The length of the CPE may be determined based on the parameters and the timing advance (TA).

[0016] Based on the fact that the parameter is not configured through a higher layer signal, the parameter may be a maximum integer such that the length of the CPE does not exceed the symbol length of symbol #K.

[0017] The specific position may be a position earlier than the symbol #K by the length of CPE.

[0018] The PUSCH may be transmitted in the unlicensed band.

[0019] The apparatus applied to the embodiment of the present disclosure may include an autonomous driving device.

[0020] The above aspects of the present disclosure are only a part of the preferred embodiments of the present disclosure, and those skilled in the art will derive and understand various embodiments reflecting the technical features of the present disclosure based on the following detailed description of the present disclosure.

[0021] Beneficial Effects

[0022] According to the embodiments of the present disclosure, signals can be efficiently transmitted and received in a wireless communication system.

[0023] According to an embodiment of the present disclosure, an efficient signal transmission method considering characteristics of an unlicensed frequency band is provided.

[0024] According to the embodiments of the present disclosure, the PUSCH starting position can be determined efficiently.

[0025] Those skilled in the art will appreciate that the effects that can be achieved using the present disclosure are not limited to those specifically described above, and other advantages of the present disclosure will be more clearly understood from the following detailed description in conjunction with the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] The accompanying drawings, which are included to provide a further understanding of the disclosure, illustrate embodiments of the disclosure and together with the description serve to explain the principle of the disclosure.

[0027] Figure 1 Physical channels in a 3rd Generation Partnership Project (3GPP) system as an exemplary wireless communication system and a general signal transmission method using the physical channels are shown.

[0028] Figure 2 Shows the radio frame structure.

[0029] Figure 3 The resource grid is shown during the duration of a time slot.

[0030] Figure 4 An exemplary mapping of physical channels in time slots is shown.

[0031] Figure 5 Exemplary uplink (UL) transmission operations of a user equipment (UE) are shown.

[0032] Figure 6 An exemplary repeated transmission based on configuration permissions is shown.

[0033] Figure 7 A wireless communication system supporting an unlicensed frequency band is shown.

[0034] Figure 8 An exemplary method of occupying resources in an unlicensed frequency band is shown.

[0035] Fig. 9An exemplary channel access procedure of a UE for UL signal transmission in an unlicensed band applicable to the present disclosure is shown.

[0036] Figures 10 to 13 The signal transmission process according to the embodiment of the present disclosure is shown.

[0037] Figures 14 to 17 Exemplary uplink signal transmission according to an embodiment of the present disclosure is shown.

[0038] Fig.18 Shows the initial access and subsequent communication process of the network.

[0039] Fig.19 An exemplary communication system applicable to the present disclosure is shown.

[0040] Fig. 20 An exemplary wireless device suitable for use with the present disclosure is shown.

[0041] Fig.21 Another exemplary wireless device suitable for use with the present disclosure is shown.

[0042] Fig. 22 An exemplary vehicle or autonomous vehicle suitable for use with the present disclosure is shown. DETAILED DESCRIPTION

[0043] The following technologies may be used in various wireless access systems such as code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), single carrier frequency division multiple access (SC-FDMA), etc. CDMA may be implemented as a radio technology such as Universal Terrestrial Radio Access (UTRA) or CDMA2000. TDMA may be implemented as a radio technology such as Global System for Mobile Communications (GSM) / General Packet Radio Service (GPRS) / Enhanced Data Rates for GSM Evolution (EDGE). OFDMA may be implemented as a radio technology such as Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wireless Fidelity (WiFi)), IEEE802.16 (Worldwide Interoperability for Microwave Access (WiMAX)), IEEE 802.20, Evolved UTRA (E-UTRA), etc. UTRA is part of Universal Mobile Telecommunications System (UMTS). 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) is a part of Evolved UMTS (E-UMTS) using E-UTRA, and LTE-advanced (LTE-A) is an evolution of 3GPP LTE. 3GPP New Radio or New Radio Access Technology (NR) is an evolved version of 3GPP LTE / LTE-A.

[0044] As more and more communication devices require greater communication capacity, there is a demand for enhanced mobile broadband communication relative to traditional radio access technology (RAT). Large-scale machine type communication (MTC) that provides various services to multiple interconnected devices and things anytime and anywhere is one of the significant problems to be solved by the next generation of communication. Communication system design considering services sensitive to reliability and delay is also under discussion. Therefore, the introduction of next-generation radio access technology (RAT) for enhanced mobile broadband communication (eMBB), massive MTC (mMTC) and ultra-reliable low-latency communication (URLLC) is under discussion. For convenience, this technology is referred to as NR or new RAT in this disclosure.

[0045] Although the following description is given in the context of a 3GPP communication system (e.g., NR) for clarity, the technical spirit of the present disclosure is not limited to the 3GPP communication system. For the background technology, terms, and abbreviations used in the present disclosure, reference is made to technical specifications published before the present disclosure (e.g., 38.211, 38.212, 38.213, 38.214, 38.300, 38.331, etc.).

[0046] In a wireless access system, a user equipment (UE) receives information from a base station (BS) on DL and transmits information to the BS on UL. The information transmitted and received between the UE and the BS includes general data and various types of control information. There are many physical channels depending on the type / purpose of the information transmitted and received between the BS and the UE.

[0047] Figure 1 Physical channels in a 3GPP system and a general signal transmission method using the physical channels are shown.

[0048] When the UE is powered on or enters a new cell, the UE performs an initial cell search (S11). The initial cell search involves acquiring synchronization with the BS. To this end, the UE receives a synchronization signal block (SSB) from the BS. The SSB includes a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a physical broadcast channel (PBCH). The UE synchronizes its timing with the BS and obtains information such as a cell identifier (ID) based on the PSS / SSS. In addition, the UE can obtain information broadcast in the cell by receiving a PBCH from the BS. During the initial cell search, the UE can also monitor the DL channel status by receiving a downlink reference signal (DL RS).

[0049] After the initial cell search, the UE may acquire more detailed system information by receiving a physical downlink control channel (PDCCH) and a physical downlink shared channel (PDSCH) corresponding to the PDCCH (S12).

[0050] Subsequently, in order to complete the connection with the BS, the UE may perform a random access procedure with the BS (S13 to S16). Specifically, the UE may send a preamble on a physical random access channel (PRACH) (S13), and may receive a PDCCH and a random access response (RAR) to the preamble on a PDSCH corresponding to the PDCCH (S14). The UE may then use the scheduling information in the RAR to send a physical uplink shared channel (PUSCH) (S15) and perform a contention resolution procedure, including receiving a PDCCH and a PDSCH signal corresponding to the PDCCH (S16).

[0051] When the random access procedure is performed in two steps, steps S13 and S15 may be performed as one step (wherein the UE sends message A), and steps S14 and S16 may be performed as one step (wherein the BS sends message B).

[0052] After the above process, in the general UL / DL signal transmission process, the UE may receive PDCCH and / or PDSCH from the BS (S17) and send a physical uplink shared channel (PUSCH) and / or a physical uplink control channel (PUCCH) to the BS (S18). The control information sent by the UE to the BS is generally referred to as uplink control information (UCI). UCI includes hybrid automatic repeat request acknowledgment / negative acknowledgment (HARQ-ACK / NACK), scheduling request (SR), channel state information (CSI), etc. CSI includes channel quality indicator (CQI), precoding matrix index (PMI), rank indication (RI), etc. Typically, UCI is sent on PUCCH. However, if control information and data should be sent simultaneously, the control information and data may be sent on PUSCH. In addition, the UE may send UCI aperiodically on PUSCH when receiving a request / command from the network.

[0053] Figure 2 Shows the radio frame structure.

[0054] In NR, UL and DL transmissions are configured on a frame basis. Each radio frame has a length of 10ms and is divided into two 5ms half-frames. Each half-frame is divided into five 1ms subframes. A subframe is divided into one or more time slots, and the number of time slots in a subframe depends on the subcarrier spacing (SCS). Depending on the cyclic prefix (CP), each time slot includes 12 or 14 OFDM (A) symbols. When a normal CP is used, each time slot includes 14 OFDM symbols. When an extended CP is used, each time slot includes 12 OFDM symbols. Symbols may include OFDM symbols (or CP-OFDM symbols) and SC-FDMA symbols (or discrete Fourier transform-extended-OFDM (DFT-s-OFDM) symbols).

[0055] Table 1 exemplarily shows that the number of symbols per slot, the number of slots per frame, and the number of slots per subframe vary according to the SCS in the normal CP case.

[0056] [Table 1]

[0057] SCS(15*2^u) <![CDATA[N slot symb ]]> <![CDATA[N frame,u slot ]]> <![CDATA[N subframe,u slot ]]> 15KHz(u=0) 14 10 1 30KHz(u=1) 14 20 2 60KHz(u=2) 14 40 4 120KHz(u=3) 14 80 8 240KHz(u=4) 14 160 16

[0058] *N slot symb : The number of symbols in a time slot

[0059] *N frame,u slot : Number of time slots in a frame

[0060] *N subframe,u slot : Number of time slots in a subframe

[0061] Table 2 shows that the number of symbols per slot, the number of slots per frame, and the number of slots per subframe vary according to SCS in the case of extended CP.

[0062] [Table 2]

[0063] SCS(15*2^u) <![CDATA[N slot symb ]]> <![CDATA[N frame,u slot ]]> <![CDATA[N subframe,u slot ]]> 60KHz(u=2) 12 40 4

[0064] The frame structure is only an example, and the number of subframes, the number of time slots, and the number of symbols in a frame may be changed in various ways.

[0065] In the NR system, different OFDM(A) parameter sets (e.g., SCS, CP length, etc.) may be configured for multiple cells aggregated for one UE. Therefore, the (absolute time) duration of a time resource (e.g., a subframe, a time slot, or a transmission time interval (TTI)) (referred to as a time unit (TU) for convenience) consisting of the same number of symbols may be configured differently between the aggregated cells.

[0066] In NR, various parameter sets (or SCS) can be supported to support various 5th generation (5G) services. For example, for an SCS of 15kHz, wide areas in the traditional cellular band can be supported, while for an SCS of 30kHz or 60kHz, dense urban areas, lower latency, and wide carrier bandwidth can be supported. For an SCS of 60kHz or higher, bandwidths greater than 24.25kHz can be supported to overcome phase noise.

[0067] The NR band can be defined by two types of frequency ranges (FR1 and FR2). FR1 and FR2 can be configured as described in Table 3 below. FR2 can be millimeter wave (mmW).

[0068] [Table 3]

[0069] Frequency range specification Corresponding frequency range Subcarrier spacing FR1 450MHz-7125MHz 15, 30, 60kHz FR2 24250MHz-52600MHz 60, 120, 240kHz

[0070] Figure 3 The resource grid during the duration of one time slot is shown.

[0071] A slot includes multiple symbols in the time domain. For example, a slot includes 14 symbols in the normal CP case and 12 symbols in the extended CP case. A carrier includes multiple subcarriers in the frequency domain. A resource block (RB) may be defined by multiple (e.g., 12) consecutive subcarriers in the frequency domain. A bandwidth part (BWP) may be defined by multiple consecutive (physical) RBs ((P)RBs) in the frequency domain and corresponds to a parameter set (e.g., SCS, CP length, etc.). A carrier may include up to N (e.g., five) BWPs. Data communication may be performed in an active BWP, and only one BWP may be enabled for a UE. Each element in a resource grid may be referred to as a resource element (RE), to which a complex symbol may be mapped.

[0072] Figure 4 An exemplary mapping of physical channels in time slots is shown.

[0073] DL control channel, DL or UL data and UL control channel may all be included in one time slot. For example, the first N symbols in the time slot (hereinafter referred to as the DL control region) may be used to send the DL control channel, and the last M symbols in the time slot (hereinafter referred to as the UL control region) may be used to send the UL control channel. N and M are integers equal to or greater than 0. The resource region (hereinafter referred to as the data region) between the DL control region and the UL control region may be used for DL ​​data transmission or UL data transmission. A time gap for DL ​​to UL or UL to DL switching may be defined between the control region and the data region. PDCCH may be sent in the DL control region, and PDSCH may be sent in the DL data region. Some symbols in the time slot when switching from DL to UL may be configured as time gaps.

[0074] Now, a detailed description will be given of the physical channels.

[0075] PDSCH transmits DL data (e.g., downlink shared channel (DL-SCH) transport block (TB)) and adopts a modulation scheme such as quadrature phase shift keying (QPSK), 16-phase quadrature amplitude modulation (16QAM), 64-phase QAM (64QAM) or 256-phase QAM (256QAM). TB is encoded as a codeword. PDSCH can transmit up to two codewords. The codewords are individually subjected to scrambling and modulation mapping, and the modulation symbols from each codeword are mapped to one or more layers. OFDM signals are generated by mapping each layer to a resource together with a DMRS and are sent through the corresponding antenna port.

[0076] PDCCH transmits DCI. For example, PDCCH (i.e., DCI) may carry information about the transmission format and resource allocation of the DL shared channel (DL-SCH), resource allocation information of the uplink shared channel (UL-SCH), paging information about the paging channel (PCH), system information about DL-SCH, information about resource allocation of high-level control messages (e.g., RAR sent on PDSCH), transmit power control commands, information about the activation / release of the configured scheduling, etc. DCI includes a cyclic redundancy check (CRC). The CRC is masked using various identifiers (IDs) (e.g., radio network temporary identifier (RNTI)) according to the owner or purpose of the PDCCH. For example, if the PDCCH is used for a specific UE, the CRC is masked by the UE ID (e.g., cell-RNTI (C-RNTI)). If the PDCCH is used for a paging message, the CRC is masked by the paging-RNTI (P-RNTI). If the PDCCH is for system information (eg, system information block (SIB)), the CRC is masked by a system information RNTI (SI-RNTI). When the PDCCH is for RAR, the CRC is masked by a random access-RNTI (RA-RNTI).

[0077] PDCCH uses a fixed modulation scheme (e.g., QPSK). One PDCCH includes 1, 2, 4, 8, or 16 control channel elements (CCEs) depending on its aggregation level (AL). One CCE includes 6 resource element groups (REGs), each REG being defined by one OFDM symbol x one (P)RB.

[0078] The PDCCH is sent in a control resource set (CORESET). A CORESET corresponds to a set of physical resources / parameters used to transmit PDCCH / DCI in a BWP. For example, a CORESET is defined as a set of REGs with a given parameter set (e.g., SCS, CP length, etc.). A CORESET may be configured by system information (e.g., a master information block (MIB)) or UE-specific high-layer signaling (e.g., RRC signaling). For example, the following parameters / information may be used to configure a CORESET, and multiple CORESETs may overlap each other in the time / frequency domain.

[0079] -controlResourceSetId: indicates the ID of the CORESET.

[0080] -frequencyDomainResources: Indicates the frequency domain resources of the CORESET. The frequency domain resources are indicated by a bitmap, and each bit of the bitmap corresponds to an RB group (i.e., six consecutive RBs). For example, the most significant bit (MSB) of the bitmap corresponds to the first RB group of the BWP. The RB group corresponding to the bit set to 1 is allocated as the frequency domain resource of the CORESET.

[0081] -duration: Indicates the time region resource of the CORESET. It indicates the number of consecutive OFDMA symbols in the CORESET. For example, duration is set to one of 1 to 3.

[0082] -cce-REG-MappingType: indicates the CCE to REG mapping type. Both interleaved and non-interleaved types are supported.

[0083] -precoderGranularity: Indicates the precoder granularity in the frequency domain.

[0084] -tci-StatesPDCCH: Provides information indicating the transmission configuration indication (TCI) state of the PDCCH (eg, TCI-StateID). The TCI state is used to provide a quasi-co-location relationship between the DL RS in the RS set (TCI-state) and the PDCCH DMRS port.

[0085] -tci-PresentInDCI: Indicates whether the TCI field is included in the DCI.

[0086] -pdcch-DMRS-ScramblingID: Provides information for initialization of the PDCCH DMRS scrambling sequence.

[0087] To receive the PDCCH, the UE may monitor (e.g., blindly decode) a set of PDCCH candidates in a CORESET. A PDCCH candidate is a CCE that the UE monitors for PDCCH reception / detection. PDCCH monitoring may be performed in one or more CORESETs in an active DL BWP on each active cell configured with PDCCH monitoring. The set of PDCCH candidates monitored by the UE is defined as a PDCCH search space (SS) set. The SS set may be a common search space (CSS) set or a UE-specific search space (USS) set.

[0088] Table 4 lists exemplary PDCCH SSs.

[0089] [Table 4]

[0090]

[0091] The SS set may be configured by system information (e.g., MIB) or UE-specific high-level (e.g., RRC) signaling. S or fewer SS sets may be configured in each DL BWP of a serving cell. For example, the following parameters / information may be provided for each SS set. Each SS set may be associated with one CORESET, and each CORESET configuration may be associated with one or more SS sets.

[0092] -searchSpaceId: indicates the ID of the SS set.

[0093] -controlResourceSetId: Indicates the CORESET associated with the SS set.

[0094] - monitoringSlotPeriodicityAndOffset: indicates the PDCCH monitoring periodicity (in time slots) and the PDCCH monitoring offset (in time slots).

[0095] -monitoringSymbolsWithinSlot: Indicates the first OFDMA symbol for PDCCH monitoring in a slot configured with PDCCH monitoring. The OFDMA symbol is indicated by a bitmap, and each bit of the bitmap corresponds to an OFDM symbol in the slot. The MSB of the bitmap corresponds to the first OFDM symbol of the slot. The OFDMA symbol corresponding to the bit set to 1 corresponds to the first symbol of the CORESET in the slot.

[0096] -nrofCandidates: indicates the number of PDCCH candidates for each AL={1,2,4,8,16} (eg, one of 0, 1, 2, 3, 4, 5, 6, and 8).

[0097] -searchSpaceType: Indicates whether the SS type is CSS or USS.

[0098] -DCI format: indicates the DCI format of the PDCCH candidate.

[0099] The UE may monitor PDCCH candidates in one or more SS sets in a time slot based on the CORESET / SS set configuration. The timing (e.g., time / frequency resource) at which the PDCCH candidate should be monitored is defined as the PDCCH (monitoring) timing. One or more PDCCH (monitoring) timings may be configured in a time slot.

[0100] Table 5 shows an exemplary DCI format transmitted on the PDCCH.

[0101] [Table 5]

[0102]

[0103] DCI format 0_0 can be used to schedule TB-based (or TB-level) PUSCH, and DCI format 0_1 ​​can be used to schedule TB-based (or TB-level) PUSCH or code block group (CBG)-based (or CBG-level) PUSCH. DCI format 1_0 can be used to schedule TB-based (or TB-level) PDSCH, and DCI format 1_1 can be used to schedule TB-based (or TB-level) PDSCH or CBG-based (or CBG-level) PDSCH (DL grant DCI). DCI format 0_0 / 0_1 can be referred to as UL grant DCI or UL scheduling information, and DCI format 1_0 / 1_1 can be referred to as DL grant DCI or DL ​​scheduling information. DCI format 2_0 is used to transmit dynamic slot format information (e.g., dynamic slot format indicator (SFI)) to the UE, and DCI format 2_1 is used to transmit DL preemptive information to the UE. DCI format 2_0 and / or DCI format 2_1 can be transmitted to a corresponding group of UEs on a group common PDCCH (PDCCH pointing to a group of UEs).

[0104] DCI format 0_0 and DCI format 1_0 may be referred to as fallback DCI formats, while DCI format 0_1 ​​and DCI format 1_1 may be referred to as non-fallback DCI formats. Under the fallback DCI format, the DCI size / field configuration remains the same regardless of the UE configuration. In contrast, under the non-fallback DCI format, the DCI size / field configuration varies according to the UE configuration.

[0105] PUCCH transmits uplink control information (UCI). UCI includes the following information.

[0106] -SR: Information used to request UL-SCH resources.

[0107] -HARQ-ACK: A response to a DL data packet (e.g., a codeword) on the PDSCH. HARQ-ACK indicates whether the DL data packet is successfully received. In response to a single codeword, a 1-bit HARQ-ACK may be sent. In response to two codewords, a 2-bit HARQ-ACK may be sent. The HARQ-ACK response includes a positive ACK (abbreviated as ACK), a negative ACK (NACK), a discontinuous transmission (DTX), or NACK / DTX. The term "HARQ-ACK" may be used interchangeably with HARQ ACK / NACK and ACK / NACK.

[0108] -CSI: Feedback information for DL ​​channels. Multiple-input multiple-output (MIMO) related feedback information includes RI and PMI.

[0109] Table 6 shows an exemplary PUCCH format. Based on PUCCH transmission duration, the PUCCH format may be divided into short PUCCH (formats 0 and 2) and long PUCCH (formats 1, 3, and 4).

[0110] [Table 6]

[0111]

[0112] PUCCH format 0 conveys up to 2 bits of UCI and is mapped in a sequence-based manner for transmission. Specifically, the UE sends a specific UCI to the BS by sending one of multiple sequences on the PUCCH of PUCCH format 0. The UE sends the PUCCH of PUCCH format 0 in the PUCCH resources for the corresponding SR configuration only when the UE sends a positive SR.

[0113] PUCCH format 1 transmits up to 2 bits of UCI and the modulation symbol of UCI is spread in the time domain using an orthogonal cover code (OCC) (configured differently depending on whether frequency hopping is performed). DMRS is transmitted in symbols where modulation symbols are not transmitted (ie, transmitted in time division multiplexing (TDM)).

[0114] PUCCH format 2 transmits more than 2 bits of UCI and the modulation symbol of DCI is sent with DMRS in frequency division multiplexing (FDM). DMRS is located in symbols #1, #4, #7 and #10 of a given RB with a density of 1 / 3. Pseudo-noise (PN) sequence is used for DMRS sequence. For 2-symbol PUCCH format 2, frequency hopping can be enabled.

[0115] PUCCH format 3 does not support UE multiplexing in the same PRBS and transmits UCI of more than 2 bits. In other words, the PUCCH resources of PUCCH format 3 do not include OCC. The modulation symbols and DMRS are sent in TDM.

[0116] PUCCH format 4 supports multiplexing of up to 4 UEs in the same PRBS and transmits more than 2 bits of UCI. In other words, the PUCCH resources of PUCCH format 3 include OCC. The modulation symbols and DMRS are sent in TDM.

[0117] The PUSCH transmits UL data (e.g., UL shared channel transport block (UL-SCH TB)) and / or UCI based on a CP-OFDM waveform or a DFT-s-OFDM waveform. When the PUSCH is sent in a DFT-s-OFDM waveform, the UE sends the PUSCH by transform precoding. For example, when transform precoding is not possible (e.g., disabled), the UE may send the PUSCH in a CP-OFDM waveform, and when transform precoding is possible (e.g., enabled), the UE may send the PUSCH in a CP-OFDM or DFT-s-OFDM waveform. PUSCH transmission may be dynamically scheduled by a UL grant in a DCI, or semi-statically scheduled by higher layer (e.g., RRC) signaling (and / or layer 1 (L1) signaling such as a PDCCH) (configured scheduling or configured grant). PUSCH transmission may be performed in a codebook-based or non-codebook-based manner.

[0118] On the DL, the BS can dynamically allocate resources for DL ​​transmission to the UE through PDCCH (including DCI format 1_0 or DCI format 1_1). In addition, the BS can indicate to a specific UE through PDCCH (including DCI format 2_1) that some resources pre-scheduled for the UE have been preempted for signal transmission to another UE. In addition, the BS can configure the DL assignment periodicity through high-layer signaling and signal the activation / deactivation of the configured DL assignment through PDCCH in a semi-persistent scheduling (SPS) scheme to provide the UE with a DL assignment for initial HARQ transmission. When retransmission of the initial HARQ transmission is required, the BS explicitly schedules the retransmission resources through PDCCH. When a DCI-based DL assignment conflicts with an SPS-based DL assignment, the UE can give priority to the DCI-based DL assignment.

[0119] Similar to DL, for UL, the BS can dynamically allocate resources for UL transmission to the UE through PDCCH (including DCI format 0_0 or DCI format 0_1). In addition, the BS can allocate UL resources for initial HARQ transmission to the UE based on the configuration grant (CG) method (similar to SPS). Although dynamic scheduling involves PDCCH for PUSCH transmission, configuration grant does not involve PDCCH for PUSCH transmission. However, UL resources for retransmission are explicitly allocated by PDCCH. Therefore, the operation of the BS pre-configuring UL resources without dynamic grant (DG) (for example, by scheduling UL grant of DCI) is called "CG". Two types are defined for CG.

[0120] - Type 1: UL grants with predetermined periodicity are provided by higher layer signaling (without L1 signaling).

[0121] -Type 2: The periodicity of UL grant is configured by higher layer signaling, and the activation / deactivation of CG is signaled through PDCCH to provide UL grant.

[0122] Figure 5 FIG. 4 shows an exemplary UL transmission operation of a UE. The UE may be based on DG( Figure 5 (a)) or based on CG( Figure 5 (b)) sends the expected packet.

[0123] Resources for CG can be shared among multiple UEs. CG-based UL signal transmission from each UE can be identified by time / frequency resources and RS parameters (e.g., different cyclic shifts, etc.). Therefore, when a UE fails to send an UL signal due to a signal conflict, the BS can identify the UE and explicitly send a retransmission permission for the corresponding TB to the UE.

[0124] K repetition transmissions including initial transmission are supported for the same TB through CG. The same HARQ process ID is determined for the K repetition UL signals based on the resources used for the initial transmission. The redundancy version (RV) of the K repetition TB has one of the patterns {0,2,3,1}, {0,3,0,3} and {0,0,0,0}.

[0125] Figure 6 An exemplary CG-based repeated transmission is shown.

[0126] The UE performs repeated transmission until one of the following conditions is met:

[0127] - Successfully received UL grant for the same TB;

[0128] -TB is repeated up to K times; and

[0129] - (In option 2), the end time of period P is reached.

[0130] Similar to the Licensed Assisted Access (LAA) in the traditional 3GPP LTE system, the use of unlicensed bands for cellular communications is also being considered in the 3GPP NR system. Unlike LAA, standalone (SA) operation is for NR cells in unlicensed bands (hereinafter referred to as NR unlicensed cells (UCells)). For example, PUCCH, PUSCH, and PRACH transmissions can be supported in NR UCells.

[0131] In the NR system to which various embodiments of the present disclosure are applicable, up to 400 MHz per component carrier (CC) may be allocated / supported. When a UE operating in such a wideband CC operates with a radio frequency (RF) module always turned on for the entire CC, battery consumption of the UE may increase.

[0132] Alternatively, considering various use cases (e.g., eMBB, URLLC, mMTC, etc.) operating within a single wideband CC, different parameter sets (e.g., SCS) may be supported for each frequency band within the CC.

[0133] Alternatively, each UE may have a different maximum bandwidth capability.

[0134] In this regard, the BS may indicate to the UE to operate only in a partial bandwidth instead of the total bandwidth of the wideband CC. The partial bandwidth may be defined as a bandwidth part (BWP).

[0135] A BWP may be a subset of contiguous RBs on the frequency axis. One BWP may correspond to one parameter set (eg, SCS, CP length, slot / mini-slot duration, etc.).

[0136] The BS may configure multiple BWPs in one CC configured for the UE. For example, the BS may configure a BWP occupying a relatively small frequency region in the PDCCH monitoring time slot, and schedule the PDSCH indicated (or scheduled) by the PDCCH in a larger BWP. Alternatively, when the UEs are concentrated on a specific BWP, the BS may configure another BWP for some UEs for load balancing. Alternatively, the BS may exclude some spectrum of the total bandwidth and configure BWPs on both sides of the cell in the same time slot considering frequency domain inter-cell interference elimination between adjacent cells.

[0137] The BS may configure at least one DL / UL BWP for a UE associated with a wideband CC, enable at least one DL / UL BWP configured at a specific time point (through L1 signaling (e.g., DCI), MAC signaling, or RRC signaling), and instruct switching to another configured DL / UL BWP (through L1 signaling, MAC signaling, or RRC signaling). In addition, when a timer value (e.g., a BWP inactivity timer value) expires, the UE may switch to a predetermined DL / UL BWP. The enabled DL / UL BWP may be referred to as an active DL / UL BWP. During initial access or before RRC connection establishment, the UE may not receive configuration of a DL / UL BWP from the BS. The DL / UL BWP assumed by the UE in this case is defined as the initial active DL / UL BWP.

[0138] Embodiments of the present disclosure

[0139] Figure 7 An exemplary wireless communication system supporting an unlicensed frequency band suitable for the present disclosure is shown.

[0140] In the following description, a cell operating in a licensed band (L band) is defined as an L cell, and a carrier of the L cell is defined as (DL / UL) LCC. A cell operating in an unlicensed band (U band) is defined as a U cell, and a carrier of the U cell is defined as (DL / UL) UCC. A carrier / carrier frequency of a cell may refer to an operating frequency (e.g., a center frequency) of the cell. A cell / carrier (e.g., CC) is generally referred to as a cell.

[0141] When BS and UE Figure 7 When sending and receiving signals on the LCC and UCC of carrier aggregation as shown in (a), the LCC and UCC can be configured as a primary CC (PCC) and a secondary CC (SCC), respectively. Figure 7 As shown in (b), signals are sent and received on one UCC or on a plurality of carrier aggregated UCCs. In other words, the BS and UE can send and receive signals only on the UCC without using any LCC. For SA operation, PRACH, PUCCH, PUSCH and SRS transmission can be supported on the UCell.

[0142] The signal transmission and reception operations in the unlicensed band as described in the present disclosure are applicable to the above-mentioned deployment scenarios (unless otherwise specified).

[0143] Unless otherwise stated, the following definitions apply to the following parameter sets used in this disclosure.

[0144] - Channel: A carrier or part of a carrier consisting of a set of contiguous RBs that perform a channel access procedure (CAP) in a shared spectrum.

[0145] - Channel Access Procedure (CAP): A procedure for evaluating channel availability based on sensing before signal transmission in order to determine whether other communication nodes are using the channel. The basic sensing unit is a sensing slot of duration Tsl=9μs. The BS or UE senses the slot during the sensing slot duration. When the power detected within at least 4μs within the sensing slot duration is less than the energy detection threshold XThresh, the sensing slot duration Tsl is considered idle. Otherwise, the sensing slot duration Tsl is considered busy. CAP may also be referred to as Listen Before Talk (LBT).

[0146] - Channel occupancy: Transmissions on the channel from BS / UE after CAP.

[0147] - Channel Occupancy Time (COT): The total time that a BS / UE and any BS / UE sharing the channel occupancy perform transmissions on the channel after the CAP. With respect to COT determination, if a transmission gap is less than or equal to 25 μs, the gap duration may be accounted for in the COT. The COT may be shared for transmissions between a BS and a corresponding UE.

[0148] - DL transmission burst: A set of transmissions from a BS without any gap greater than 16 μs. Transmissions from a BS separated by gaps greater than 16 μs are considered separate DL transmission bursts. The BS may perform transmissions after a gap within a DL transmission burst without sensing channel availability.

[0149] - UL transmission burst: A set of transmissions from a UE without any gap greater than 16 μs. Transmissions from a UE separated by gaps greater than 16 μs are considered separate UL transmission bursts. A UE may perform transmissions after a gap within a DL transmission burst without sensing channel availability.

[0150] - Discovery burst: A DL transmission burst that includes a set of signals and / or channels confined within a window and associated with a duty cycle. A discovery burst may include a transmission initiated by the BS that includes PSS, SSS, and cell-specific RS (CRS), and also includes non-zero power CSI-RS. In an NR system, a discovery burst may include a transmission initiated by the BS that includes at least an SS / PBCH block and also includes a CORESET for scheduling a PDSCH carrying SIB1, a PDSCH carrying SIB1, and / or a PDCCH with non-zero power CSI-RS.

[0151] Figure 8 An exemplary method of occupying resources in an unlicensed frequency band is shown.

[0152] Reference Figure 8 , a communication node (e.g., BS or UE) operating in an unlicensed band should determine whether other communication nodes are using the channel before signal transmission. To this end, the communication node may perform CAP to access the channel to be transmitted in the unlicensed band. CAP may be performed based on sensing. For example, a communication node may determine whether other communication nodes are sending signals on the channel by carrier sensing (CS) before signal transmission. Determining that other communication nodes are not sending signals is defined as confirmation of idle channel assessment (CCA). In the presence of a CCA threshold (e.g., Xthresh) predefined or configured by high-level (e.g., RRC) signaling, when energy above the CCA threshold is detected in the channel, the communication node may determine that the channel is busy. Otherwise, the communication node may determine that the channel is idle. When it is determined that the channel is idle, the communication node may start sending signals in the unlicensed band. CAP may be replaced by LBT.

[0153] Table 7 describes an exemplary CAP supported in NR-U.

[0154] [Table 7]

[0155]

[0156] In a wireless communication system supporting an unlicensed band, a cell (or carrier (e.g., CC)) or BWP configured for a UE may be a broadband with a larger bandwidth (BW) than in conventional LTE. However, the BW for which CCA is required based on independent LBT operation may be restricted according to regulations. A subband (SB) for which LBT is performed individually is defined as an LBT-SB. Then, multiple LBT-SBs may be included in one broadband cell / BWP. The set of RBs included in the LBT-SB may be configured by high-level (e.g., RRC) signaling. Therefore, one or more LBT-SBs may be included in one cell / BWP based on (i) the BW of the cell / BWP and (ii) RB set allocation information.

[0157] Multiple LBT-SBs may be included in a BWP of a cell (or carrier). For example, the LBT-SB may be a 20-MHz frequency band. The LBT-SB may include multiple contiguous (P)RBs in the frequency domain and may therefore be referred to as a (P)RB set.

[0158] The UE performs a Type 1 or Type 2 CAP for UL signal transmission in an unlicensed band. Typically, the UE may perform a CAP (e.g., Type 1 or Type 2) configured by the BS for UL signal transmission. For example, the CAP type indication information may be included in a UL grant (e.g., DCI format 0_0 or DCI format 0_1) that schedules PUSCH transmission.

[0159] In the Type 1 UL CAP, the length of the time period spanned by the sensing slots sensed as idle before transmission is random. The Type 1 UL CAP is applicable to the following transmissions.

[0160] -PUSCH / SRS transmission scheduled and / or configured by the BS

[0161] - PUCCH transmissions scheduled and / or configured by the BS

[0162] - Transmissions related to the Random Access Procedure (RAP)

[0163] Fig. 9 A Type 1 CAP among CAPs of a UE for UL signal transmission in an unlicensed band applicable to the present disclosure is shown.

[0164] Reference Fig. 9 , the UE may sense whether the channel is idle during the sensing time slot duration in the deferral duration Td. When the counter N is reduced to 0, the UE may perform transmission (S934). The counter N is adjusted by sensing the channel during the additional time slot duration according to the following process.

[0165] Step 1) Set N=Ninit, where Ninit is a random number uniformly distributed between 0 and CWp, and go to step 4 (S920).

[0166] Step 2) If N>0 and the UE chooses to decrease the counter, set N=N-1 (S940).

[0167] Step 3) Sense the channel during the additional time slot duration, and if the additional time slot duration is idle (Yes), go to step 4. Otherwise (No), go to step 5 (S950).

[0168] Step 4) If N=0 (Yes) (S930), stop CAP (S932). Otherwise (No), go to step 2.

[0169] Step 5) The channel is sensed until a busy sensing time slot is detected within the additional deferral duration Td or all time slots of the additional deferral duration Td are sensed as idle (S960).

[0170] Step 6) If the channel is sensed as idle during all time slot durations of the additional deferral duration Td (Yes), go to Step 4. Otherwise (No), go to Step 5 (S970).

[0171] Table 8 shows that mp, minimum CW, maximum CW, maximum channel occupancy time (MCOT), and allowed CW size applied to CAP vary according to the channel access priority category.

[0172] [Table 8]

[0173]

[0174] Delay duration T d Including duration T f (16μs), followed by m p The duration of each time slot is T sl is 9μs, and T f The beginning of the 16 μs duration includes the sensing time slot duration T sl .

[0175] CW min,p <=CW p <=CW max,p .CW p Set to CW min,p , and may be updated (CW size update) based on an explicit / implicit reception response to a previous UL burst (e.g., PUSCH) before step 1. For example, CW p Can be initialized to CW based on explicit / implicit reception response to previous UL burstmin,p , can be increased to the next highest allowed value, or can be maintained at the existing value.

[0176] In a Type 2 UL CAP, the length of the time period spanned by the sensing slot that is sensed as idle before transmission is deterministic. Type 2 UL CAPs are classified into Type 2A UL CAPs, Type 2B UL CAPs, and Type 2C UL CAPs. In a Type 2A UL CAP, the UE may select a sensing slot that is idle for at least the sensing duration T. short_dl The signal is sent immediately after the channel is sensed as idle during (=25μs). short_dl The duration Tf (=16 μs) and the one immediately following the sensing slot duration. In Type 2A UL CAP, T f The sensing time slot is included at the beginning of the duration. In a Type 2B UL CAP, the UE may f The signal is sent immediately after the channel is sensed as idle during (=16μs). In Type 2B ULCAP, T f The last 9 μs of the duration include a sensing slot.In Type 2C UL CAP, the UE does not sense the channel before transmission.

[0177] The present disclosure proposes a method for indicating an LBT type and a PUSCH starting position for UL transmission scheduling in a wireless communication system including a BS and a UE in an unlicensed band, and a method for performing UL transmission based on the indicated LBT type and PUSCH starting position. The present disclosure also proposes a method for configuring a reference resource referred to when adjusting a contention window size (CWS) by receiving a result of a PDSCH or PUSCH transmission via feedback.

[0178] In order to allow the UE to send UL data in the unlicensed band, the BS should successfully perform an LBT operation to send an UL grant in the unlicensed band, and the UE should also successfully perform an LBT operation to send UL data. That is, the UE can attempt UL data transmission only when the LBT operations of both the BS and the UE are successful. In addition, since a delay of at least 4 msec is involved between the UL grant and the scheduled UL data in the LTE system, an earlier access from another transmission node coexisting in the unlicensed band during the time period may postpone the scheduled UL data transmission of the UE. In this context, a method of increasing the efficiency of UL data transmission in the unlicensed band is being discussed.

[0179] In LTE LAA, the BS may inform the UE of autonomous uplink (AUL) subframes or time slots for autonomous UL transmission through an X-bit bitmap (eg, X=40 bits), where the UE may send UL data without receiving a UL grant.

[0180] When autonomous transmission is enabled, the UE may send UL data in the subframe or time slot indicated by the relevant bitmap even if no UL grant is received. When sending PDSCH to the UE, the BS also sends PDCCH as scheduling information required for decoding. Similarly, when sending PUSCH to the BS on AUL, the UE also sends AUL UCI as information required for the BS to decode PUSCH. AUL UCI includes information required for receiving AUL PUSCH, such as HARQ ID, new data indicator (NDI), redundancy version (RV), AUL subframe start position and AUL subframe end position, and information for sharing UE-initiated COT with the BS. "Sharing UE-initiated COT with the BS" means assigning a portion of the channel occupied by the UE through a Category 4 LBT (or Type 1 CAP) based on random backoff to the BS and sending PDCCH (and PDSCH) on the channel by the BS when the channel is idle as a result of a one-slot LBT of 25μsec (based on the timing gap caused by the UE clearing the last symbol).

[0181] In order to support UL transmission with relatively high reliability and relatively low time delay, NR also supports CG type 1 and CG type 2, in which the BS pre-configures time, frequency and code resources for the UE through high-layer signaling (e.g., RRC signaling) or both high-layer signaling and L1 signaling (e.g., DCI). Without receiving a UL grant from the BS, the UE can perform UL transmission in resources configured with type 1 or type 2. In type 1, the periodicity of the CG, the offset from SFN=0, the time / frequency resource allocation, the number of repetitions, the DMRS parameters, the MCS / TB size (TBS), the power control parameters, etc. are all configured only by high-layer signaling such as RRC signaling without L1 signaling. Type 2 is a scheme in which the periodicity and power control parameters of the CG are configured by high-layer signaling such as RRC signaling and the information about the remaining resources (e.g., the offset of the initial transmission timing, the time / frequency resource allocation, the DMRS parameters and the MCS / TBS) is indicated by enabling DCI as L1 signaling.

[0182] The AUL of LTE LAA and the CG of NR show huge differences in the method of sending HARQ-ACK feedback for the PUSCH sent by the UE without receiving a UL grant and in whether there is UCI sent together with the PUSCH. Although the HARQ process is determined by the equation of symbol index, symbol periodicity and number of HARQ processes in the CG of NR, explicit HARQ-ACK feedback information is sent in the AUL downlink feedback information (AUL-DFI) in LTE LAA. In addition, in LTE LAA, whenever AUL PUSCH transmission is performed, UCI including information such as HARQ ID, NDI and RV is also sent in the AUL UCI. In the case of NR's CG, the BS identifies the UE by the time / frequency resources and DMRS resources used for PUSCH transmission, while in the case of LTE LAA, the BS identifies the UE by the UE ID explicitly included in the AUL UCI sent together with the PUSCH and the DMRS resources.

[0183] Before describing the proposed method, the NR-based channel access scheme for the unlicensed band used in this disclosure is categorized as follows.

[0184] - Category 1 (Cat-1): After a switching gap within the COT, the next transmission immediately follows the previous transmission, and the switching gap is shorter than 16 μs (even including the transceiver round trip time). Cat-1 LBT may correspond to the above-mentioned Type 2C CAP.

[0185] - Category 2 (Cat-2): LBT method without backoff. Once the channel is confirmed to be idle during a specific time period shortly before transmission, the transmission can be performed immediately. Cat-2 LBT can be subdivided according to the length of the minimum sensing duration required for channel sensing immediately before transmission. For example, Cat-2 LBT with a minimum sensing duration of 25μs may correspond to the above-mentioned Type 2A CAP, and Cat-2 LBT with a minimum sensing duration of 16μs may correspond to the above-mentioned Type 2B CAP. The minimum sensing duration is only exemplary, and a minimum sensing duration less than 25μs or 16μs (for example, a minimum sensing duration of 9μs) may also be available.

[0186] - Category 3 (Cat-3): LBT method with backoff based on a fixed contention window size (CWS) i. The transmitting entity selects a random number N in the range of 0 to the (fixed) maximum CWS value and decrements the counter value each time it determines that the channel is idle. When the counter value reaches 0, the transmitting entity is allowed to perform transmission.

[0187] - Category 4 (Cat-4): LBT method with variable CWS-based backoff. The transmitting entity selects a random number N in the range of 0 to a (variable) maximum CWS value, and decreases the counter value each time the channel is determined to be idle. When the counter value reaches 0, the transmitting entity is allowed to perform the transmission. If the transmitting entity receives feedback indicating a reception failure of the transmission, the transmitting entity increases the maximum CWS value by one level, selects a random number again within the increased CWS value, and performs the LBT process. Cat-4 LBT may correspond to the above-mentioned Type 1 CAP.

[0188] The following description is given with the understanding that the term frequency band is used interchangeably with CC / cell, and CC / cell (index) may be replaced by BWP (index) configured within the CC / cell or a combination of CC / cell (index) and BWP (index).

[0189] The terms are defined below.

[0190] -UCI: control information sent by the UE on UL. UCI includes various types of control information (ie, UCI types). For example, UCI may include HARQ-ACK (abbreviated as A / N or AN), SR, and CSI.

[0191] -PUCCH: A physical layer UL channel used for UCI transmission. For convenience, PUCCH resources configured and / or indicated for A / N, SR and CSI transmission are referred to as A / N PUCCH resources, SR PUCCH resources and CSI PUCCH resources, respectively.

[0192] -UL Grant DCI: DCI for UL grant. For example, UL Grant DCI means DCI formats 0_0 and 0_1, and is transmitted on the PDCCH.

[0193] -DL assignment / grant DCI: DCI for DL ​​grant. For example, DL assignment / grant DCI means DCI formats 1_0 and 1_1, and is transmitted on the PDCCH.

[0194] -PUSCH: Physical layer UL channel used for UL data transmission.

[0195] -Slot: A basic time unit (TU) (or time interval) for data scheduling. A slot includes a plurality of symbols. Herein, a symbol includes an OFDM symbol (e.g., a CP-OFDM symbol or a DFT-s-OFDM symbol). In this specification, the terms symbol, OFDM-based symbol, OFDM symbol, CP-OFDM symbol, and DFT-s-OFDM symbol may be used interchangeably.

[0196] - Perform LBT on / for channel X: This means performing LBT in order to confirm whether to transmit channel X. For example, CAP may be performed before transmission of channel X starts.

[0197] In LTE enhanced LAA (eLAA), two types of CAPs for UL data transmission have been widely defined. CAP type 1 (hereinafter, Cat-4 LBT) is a backoff-based mechanism similar to the CAP for DL ​​data transmission, and CAP type 2 (hereinafter, 25μs Cat-2 LBT) is a mechanism for starting UL transmission by considering the channel to be idle when the energy measured by a short CCA of minimum 25μs or longer immediately before the UL transmission is lower than a threshold. According to the description of ETSI EN 301 893, if the UE performs UL transmission before 16μs after receiving the UL grant from the BS (or the initiating device), the UE (or the responding device) may perform UL transmission without CCA. The present disclosure relates to a process of performing UL transmission without LBT due to a gap between DL transmission and UL transmission being less than 16μs as Cat-1 LBT, and a process of starting UL transmission by considering the channel to be idle if the energy measured by a short CCA of 16μs immediately before the transmission is lower than a threshold as 16μs Cat-2 LBT.

[0198] The transmission of UL data such as PUSCH is indicated by DCI (i.e., UL grant) sent via PDCCH. The DCI includes information about the LBT type and PUSCH starting position that the UE will use during the CAP. Specifically, in conventional LTE eLAA, whether the CAP type used for the CAP is type 1 (Cat-4 LBT) or type 2 (25μs Cat-2 LBT) is indicated by a 1-bit field in the UL grant DCI, and one of the 4 PUSCH starting positions {symbol #0, symbol #0+25μs, symbol #0+25μs+timing advance (TA), symbol #1} is indicated by another 2-bit field.

[0199] In NR, the BS can indicate the time domain resources of PUSCH to the UE through the start and length indicator value (SLIV) in the UL grant, that is, the position of the starting symbol of PUSCH and the number of symbols constituting PUSCH. In other words, all symbols constituting the time slot are not always used for PUSCH transmission, but PUSCH corresponding to the length from the starting symbol indicated by SLIV is sent. Therefore, the PUSCH starting position traditionally exists between symbol #0 and symbol #1, while in NR, based on the starting symbol (symbol #K) indicated by SLIV, the PUSCH starting position may exist between symbol #K and symbol #(KN) according to the gap between SCS and transmission.

[0200] When the symbol indicated by SLIV is symbol #K, the candidates for the available PUSCH start position may be defined as {symbol #(KN)+16μs, symbol #(KN)+16μs+TA, symbol #(KN)+25μs, symbol #(KN)+25μs+TA, symbol #K}, and {symbol #(KN)+16μs+TA} may be replaced with {symbol #(K-1)+max(16μs,TA)}. If TA exists in the first symbol of the next time slot after DL transmission is performed until the symbol immediately before the PUSCH transmission start symbol (for example, when UL transmission starts immediately after DL reception (16μs-TA)), {symbol #(K-1)+16μs+TA} may be excluded from the candidates for the PUSCH start position. N may be predefined as a specific value (for example, N=1), or may be separately configured / indicated by RRC signaling (or DCI or a combination of RRC and DCI). Alternatively, the BS may (scalably) configure the N value to different values ​​for the UE according to the parameter set. For example, according to SCS, for 15 kHz, N=1, and for 30 kHz, N=2.

[0201] For BS-initiated (or gNB-initiated) channel occupancy, the reference duration for CWS adjustment may be defined as follows: For channel occupancy with a set of unicast PDSCH and LBT bandwidth maintaining a single contention window, the reference duration for CWS adjustment may be the duration generated first from the start of channel occupancy to the end of the first time slot in which at least one unicast PDSCH is transmitted through all resources allocated to PDSCH and from the start of channel occupancy to the end of the first transmission burst including unicast PDSCH transmitted by the BS through all resources allocated to PDSCH.

[0202] If there is channel occupancy with a unicast PDSCH, but the unicast PDSCH is not transmitted through all resources allocated to the PDSCH, the duration of the first transmission burst of the BS in the channel occupancy including the unicast PDSCH may be a reference duration for CWS adjustment.

[0203] For UE-initiated channel occupancy, the reference duration for CWS adjustment may be defined as follows. For channel occupancy with a set of PUSCH and LBT bandwidth maintaining a single contention window, the reference duration for CWS adjustment may be the duration first generated from the start of channel occupancy to the end of the first time slot in which at least one PUSCH is sent through all resources allocated to PUSCH and the duration from the start of channel occupancy to the end of the first transmission burst of PUSCH sent by the UE through all resources allocated to PUSCH. If there is channel occupancy with PUSCH, but PUSCH is not sent through all resources allocated to PUSCH, the duration of the first transmission burst of the UE in the channel occupancy including PUSCH may be the reference duration for CWS adjustment.

[0204] Before describing the proposed method, a frame-based device (FBE) and a load-based device (LBE) in the present disclosure will be briefly described. FBE refers to a device that sends and receives signals based on a periodic time such as a frame fixed period (FFP), and LBE refers to a device that sends and receives signals when it is intended to send and receive signals regardless of the period. FBE mode and LBE mode may be types of channel access modes. A wireless communication system of an unlicensed band to which the present disclosure is applied may support both FBE mode and LBE mode as channel access modes. When a BS or a UE operates in FBE mode, the BS and the UE may send a signal in the next FFP by performing CAP in an idle period within the FFP. On the contrary, when a BS or a UE operates in LBE mode, the BS and the UE may send a signal by performing CAP when it is intended to send a signal regardless of a specific period. In LBE mode, both a random backoff-based CAP (e.g., a Type 1 CAP or a Cat-4 LBT) and a non-random backoff CAP may be performed. In FBE mode, a random backoff-based CAP is not performed.

[0205] In addition, CP insertion is used in OFDM transmission. CP insertion means that the last part of the OFDM symbol is copied and inserted into the beginning of the OFDM symbol. The transmission after padding the CP in front of a specific OFDM symbol by adjusting the CP length may be called CP extension (CPE), and a CPE of appropriate length is required according to the LBT type and SCS.

[0206] [Proposed Method #1] A method of transmitting UL data by receiving a PUSCH transmission start symbol (symbol #K) indicated by SLIV in a UL grant from a BS and receiving an LBT type and a PUSCH start position of a PUSCH as indicated below

[0207] (1-1) Method of receiving one of the states of 4 LBT types and 5 PUSCH start position combinations indicated by a specific 4-bit field in UL Grant

[0208] The following Table 9 shows the LBT type and PUSCH starting position configured by joint coding.

[0209] [Table 9]

[0210]

[0211] In Table 9, one or both of the states where the LBT type is Cat-1 LBT or 16μs Cat-2 LBT and the PUSCH start position is symbol #(K), that is, one or both of state #2 and state #5, can be excluded from the states that need to be indicated. In addition, state #1 can also be excluded. This is because, in Cat-1 LBT, the UE can perform UL transmission without channel sensing as long as the gap between transmissions is 16μs or less, and in 16μs Cat-2 LBT, LBT can only be performed when an exact 16μs gap should be guaranteed. In Table 9, N is a value that is predefined differently for each state (in the standard) or configured / indicated by the BS. When the PUSCH start position is indicated, only the gap used for LBT other than symbol #(KN) in Table 9 (for example, only 16μs in the case of state #0) can be signaled.

[0212] (1-2) A method of distinguishing between [Cat-1 LBT, Cat-2 LBT] and [Cat-4 LBT] by a 1-bit flag in UL Grant and receiving one of the states of the combination of the LBT type and the PUSCH start position indicated by another 3-bit field

[0213] The following Table 10 shows an exemplary combination of LBT type and PUSCH start position when [Cat-1 LBT, Cat-2 LBT] is indicated.

[0214] [Table 10]

[0215] state LBT Type PUSCH starting position 0 Cat-1 LBT Symbol #(KN)+16μs 1 Cat-1 LBT Symbol #(KN)+16μs+TA 2 Cat-1 LBT Symbol #K 3 16μs Cat-2LBT Symbol #(KN)+16μs 4 16μs Cat-2LBT Symbol #(KN)+16μs+TA 5 25μs Cat-2LBT Symbol #(KN)+25μs 6 25μs Cat-2LBT Symbol #(KN)+25μs+TA 7 25μs Cat-2LBT Symbol #K

[0216] The following Table 11 shows an example of a combination of an LBT type and a PUSCH start position when [Cat-4 LBT] is indicated.

[0217] [Table 11]

[0218]

[0219] In Table 10, one or both of the states in which the LBT type is Cat-1 LBT or 16μs Cat-2 LBT and the PUSCH start position is symbol #(K) may be excluded from the states that need to be indicated, that is, one or both of state #1 and state #2 in Table 10. This is because, in Cat-1 LBT, the UE can perform UL transmission without channel sensing as long as the gap between transmissions is 16μs or less, and in 16μs Cat-2 LBT, LBT can be performed only when an exact 16μs gap should be guaranteed. In these tables, N is a value that is predefined differently for each state (in the standard) or configured / indicated by the BS. When the PUSCH start position is indicated, only the gap used for LBT other than symbol #(KN) in the above table (for example, only 16μs in the case of state #0) may be signaled.

[0220] If 4 LBT types and 5 PUSCH start positions are indicated by separate fields in the UL grant, a total of 5 bits are required. However, a cell configured to use only some of the 4 LBT types through high-layer signals such as RRC signaling or through the remaining minimum system information (RMSI) may not need to indicate all LBT types and PUSCH start positions. For example, a cell operating in FBE mode only needs to indicate one of the remaining two LBT types other than Cat-4 LBT and 16μs Cat-2 LBT to the UE. As another example, when the use of the remaining 3 LBT types other than 25μs Cat-2 LBT among the 4 LBT types is semi-statically indicated by RRC signaling, and one of the 3 LBT types is dynamically indicated by the UL grant, if the PUSCH transmission start symbol is indicated as symbol #K through SLIV, it may not be necessary to indicate {symbol #(KN)+25μs, symbol #(KN)+25μs+TA} among the PUSCH start positions.

[0221] As in (1-1), the BS may define a state by combining an LBT type and a PUSCH start position to configure the state through RMSI or RRC signaling, or the state may be predefined in the standard. Table 9 is an example of defining the LBT type and the PUSCH start position as one state, and the order of states constituting the actual table or the number of states may be different from those shown in Table 9. As mentioned in the above description, all combinations may constitute the states shown in Table 9 and may be configured and defined. Then, only some states to be actually used may be configured / indicated. That is, only some states in the set of combinations of the total LBT type and the PUSCH start position may be configured / indicated as a subset for the UE according to the operation mode or specific purpose of the cell.

[0222] As in (1-2), another method of indicating the LBT type and the PUSCH starting position is to distinguish between [Cat-1 LBT, Cat-2 LBT] and [Cat-4] through a 1-bit flag in the UL grant (i.e., to divide the LBT type into Cat-4 LBT and non-Cat-4 LBT) and to indicate a state of the LBT type and PUSCH starting position combination through another 3-bit field. Table 10 shows an example of configuration by combining Cat-1 or Cat-2 LBT and the corresponding PUSCH starting position when the 1-bit flag indicates [Cat-1 LBT, Cat-2 LBT]. Table 11 shows the configurable PUSCH starting position when [Cat-4 LBT] is indicated. The advantage of this method is that when a specific cell operates in FBE mode, since there is no need to indicate Cat-4 LBT, the 1-bit flag and Table 11 may not be used.

[0223] Tables 10 and 11 are examples shown by defining the LBT type and the PUSCH start position as one state, and the order of states constituting the actual tables or the number of states may be different from those shown in Tables 10 and 11. In addition, only some states in the set of combinations of total LBT types and PUSCH start positions that can be indicated when the LBT type is [Cat-1, Cat-2 LBT] or [Cat-4 LBT] may be configured / indicated as a subset according to the operation mode or specific purpose of the cell.

[0224] [Proposed method #2] When the BS configures the UE with information about the LBT type or channel access mode (e.g., FBE mode or LBE mode) to be used in the corresponding cell through a higher layer signal such as RRC, or the BS informs the UE of the information through a physical layer signal such as DCI or through a combination of a higher layer signal and a physical layer signal, a method of configuring a field indicating the LBT type and the PUSCH start position (or a state in which the two are combined) in a UL grant (or DL ​​assignment)

[0225] The four LBT types that the BS can indicate to the UE are {Cat-1 LBT, 16μs Cat-2 LBT, 25μs Cat-2 LBT, Cat-4 LBT}. However, depending on the capabilities of the UE or the operating mode of the cell, the UE may be instructed to use only some of the four LBT types. Two bits are required to indicate a total of four LBT types. However, when only some LBT types are configured / indicated to be used, since only one of the configured / indicated LBT types needs to be indicated, the number of bits required to indicate the LBT type in the UL grant (or DL ​​allocation for PUCCH transmission) may be less than two bits. For example, if the UE reports that Cat-1 LBT and 16μs Cat-2 LBT are not supported, the BS only needs to indicate one of the 25μs Cat-2 LBT and Cat-4 LBT by one bit. If the UE is informed by a higher layer signal (e.g., SIB) that the cell is operating in FBE mode, the UE can expect to indicate one of the remaining three LBT types other than Cat-4 LBT among the four LBT types. Alternatively, the BS may inform the UE in advance of the LBT type to be used through a higher layer signal, a physical layer signal, or a combination thereof, and may indicate one of the three LBT types.

[0226] If the LBT type to be indicated to the UE is preconfigured / indicated as described above, the PUSCH start position candidate set indicated together with the LBT type may also change accordingly. When the PUSCH start position (symbol #K) is indicated to the UE through SLIV, the candidate set of the PUSCH start position that can be indicated is four in total, namely, {symbol #(K-C1)+25μs, symbol #(K-C2)+16μs+TA, symbol #(K-C3)+25μs+TA, symbol #K}. However, since the PUSCH start position corresponds to each LBT type, the PUSCH start position subset can be determined according to the LBT type configured / indicated for the corresponding cell. Here, the C1, C2, and C3 values ​​may be different according to the SCS and the PUSCH start position candidates, and the gap from the corresponding start position to symbol #K may be filled by the CPE of the first symbol of the PUSCH. For example, if the LBT type configured / indicated for the cell is only 16 μs Cat-2 LBT, the PUSCH starting position subset may be determined as {symbol #(K-C2)+16 μs+TA, symbol #K}.

[0227] In order to indicate all LBT types and all PUSCH start positions to the UE, 2 bits are required for each, so a total of 4 bits are required for the UL grant (or DL ​​allocation). However, when the channel access mode or LBT type to be used in the cell is pre-configured / indicated, the number of LBT types and PUSCH start positions to be indicated can be reduced. Therefore, (i) the number of bits required when the LBT type and the PUSCH start position are indicated as one state by their combination as in (1-1) of the proposed method #1 can be determined as ceiling[log2(the total number of states that can be indicated)]. Alternatively, (ii) when the LBT type and the PUSCH start position are indicated by individual fields, the number of bits of the field used to distinguish between the LBT types can be determined as ceiling[log2(the number of configured / indicated LBT types)], and the number of bits required to indicate the PUSCH start position can be determined as ceiling[log2(the maximum value among the number of PUSCH start position states that can be indicated corresponding to the configured / indicated LBT type)]. Here, the maximum value among the number of PUSCH start position states that can be indicated corresponding to the configured / indicated LBT type is applied as follows. For example, when two LBT types, i.e., 16μs Cat-2 LBT and Cat-4 LBT, are configured / indicated for a cell, since the number of PUSCH start position candidates for 16μs Cat-2 LBT is 2, {symbol #(K-C2)+16μs TA, symbol #K}, and the number of PUSCH start position candidates for Cat-4 LBT is 4, {symbol #(K-C1)+25μs, symbol #(K-C2)+16μs+TA, symbol #(K-C3)+25μs+TA, symbol #K}, the number of bits of the field required to indicate the PUSCH start position is log2(4). Even when the LBT type is distinguished by a flag and the PUSCH start position table is changed accordingly as in (1-2) of the proposed method #1, the method (ii) is also applicable.

[0228] [Proposed method #3] When the PUSCH transmission start symbol (symbol #K), LBT type, and PUSCH start position are indicated by SLIV in the UL grant received from the BS, the length of the gap corresponding to the indicated PUSCH start position is considered from the symbol # (KN) regardless of the TA as follows:

[0229] In this case, N may be a value configured / indicated in advance for each SCS through each RMSI / RRC / DCI or a combination thereof regardless of the TA value, or may be a value defined in the standard.

[0230] (3-1) When the UE successfully performs LBT according to the indicated type, a method for transmitting a PUSCH by filling the gap between the indicated PUSCH start position and the symbol #K indicated by the SLIV using the CP of the symbol #K based on the N value preconfigured / indicated / defined for each SCS

[0231] However, when there is no gap between the PUSCH start position and symbol #K, the UE can immediately send PUSCH without CPE.

[0232] (3-2) When the value obtained by adding the gap corresponding to the indicated PUSCH start position to the symbol # (KN) exceeds the PUSCH transmission start symbol (symbol #K) indicated by SLIV, a method of treating the relevant scheduling as invalid and discarding its DCI (UL grant) or treating the relevant scheduling as an error case

[0233] In LTE eLAA, one of the four PUSCH start positions {symbol #0, symbol #0+25μs, symbol #0+25μs+TA, symbol #1} can be indicated by 2 bits in the UL grant. Among them, when the transmission of the previous subframe is UL, the PUSCH start position between symbol #0 and symbol #1 (for example, symbol #0+25μs) can be indicated, and when the transmission of the previous subframe is DL, symbol #0+25μs+TA can be indicated. When LBT is successful, the UE sends PUSCH by filling the gap between the PUSCH start position indicated by the CPE of symbol #1 and symbol #1. The reason is that, when the PUSCH start position existing between symbol #0 and symbol #1 is indicated to the UE and the UE successfully performs LBT so that the UE attempts to start transmission from symbol #1, another node (e.g., Wi-Fi) can determine that there is no transmission in the gap between {symbol #0+25μs} and {symbol #1} or the gap between {symbol #0+25μs+TA} and {symbol #1} and occupy the channel in the gap.

[0234] Similarly, in NR-Unlicensed (NR-U), when one of the PUSCH starting positions between symbol #K indicated by SLIV and symbol #(KN) defined by the N value pre-configured / indicated / defined for each SCS is indicated, that is, when one of {symbol #(KN)+16μs, symbol #(KN)+16μs+TA, symbol #(KN)+25μs, symbol #(KN)+25μs+TA} is indicated, the UE can send PUSCH by filling the gap between symbol #K and the indicated PUSCH starting position by the CPE.

[0235] Fig.10 The length of the CPE is shown when the PUSCH start position of the 15kHz SCS is indicated. Fig.10 , if the PUSCH transmission start symbol indicated by SLIV is OS#1 and the PUSCH start position a, b, c or d is indicated in the duration of the symbol before symbol OS#1 (i.e., OS#0) after the UE performs DL reception or UL transmission (i.e., if the PUSCH start symbol indicated by SLIV is symbol #0, the PUSCH start position is indicated between symbol #0 and symbol #1), the UE can send PUSCH by filling the gap between the PUSCH start position and OS#1 by the CPE.

[0236] As an example, when the N value is configured / indicated / defined as 1 regardless of the TA value, since the length of one OFDM symbol for 15kHz SCS is approximately 70μs, even when symbol #(KN) is added with one of {16μs, 16μs+TA, 25μs, 25μs+TA}, considering the typical TA value, it does not occur that the length of the gap corresponding to each PUSCH start position exceeds symbol #K.

[0237] However, if the TA value is very large so that the value of ({25μs+TA}+gap) from symbol #(KN) exceeds symbol #K, the UE may determine that the relevant scheduling is invalid and discard the corresponding DCI (UL grant) as in (3-2) or handle the relevant scheduling as an error case.

[0238] In the case of 30kHz SCS, the length of one OFDM symbol is about 33μs, and in the case of 60kHz SCS, the length of one OFDM symbol is about 16μs. Therefore, it may happen that when symbol #(KN) is added to {16μs, 16μs+TA, 25μs, 25μs+TA}, the length of the gap corresponding to each PUSCH start position according to the configured / indicated / defined N value exceeds symbol #K.

[0239] The N value for each state may be determined based on the gap corresponding to a specific PUSCH starting position regardless of the TA. For example, the N value defined in the standard may be predefined for each PUSCH starting position for each SCS as follows.

[0240] 15kHz: {Symbol #(K-1)+16μs,Symbol #(K-1)+16μs+TA,Symbol #(K-1)+25μs,Symbol #(K-1)+25μs+TA,Symbol #K}

[0241] 30kHz: {Symbol #(K-1)+16μs,Symbol #(K-1)+16μs+TA,Symbol #(K-1)+25μs,Symbol #(K-2)+25μs+TA,Symbol #K}

[0242] 60kHz: {Symbol #(K-2)+16μs,Symbol #(K-2)+16μs+TA,Symbol #(K-3)+25μs,Symbol #(K-3)+25μs+TA,Symbol #K}

[0243] If a specific PUSCH starting position defined based on the N value determined in the standard exceeds symbol #K due to an actual TA value, the UE may consider the related scheduling invalid and discard the DCI (UL grant) or handle the related scheduling as an error case.

[0244] Fig.11 The length of the CPE when each PUSCH start position of the 30 kHz SCS is indicated is shown.

[0245] Reference Fig.11 , if the PUSCH start symbol of the 30kHz SCS indicated by SLIV is OS#1 and the PUSCH start position is indicated in the symbol (i.e., OS#0) duration before symbol OS#1 after the UE performs DL reception or UL transmission (i.e., the PUSCH start position is indicated between symbol #0 and symbol #1 when the PUSCH start symbol indicated by SLIV is symbol #0), the UE can send PUSCH by filling the gap between the PUSCH start position and OS#1 by the CPE.

[0246] As an example, when the N value is configured / indicated / defined as 1 regardless of the TA value, since the length of one OFDM symbol for 30kHz SCS is about 33μs, a situation where the length of the gap corresponding to each PUSCH start position exceeds symbol #1 may occur according to the TA value. For example, among {16μs, 16μs+TA, 25μs, 25μs+TA}, the length of the gap corresponding to the PUSCH start position is indicated as {25μs+TA}, and a situation where the length of the gap exceeds symbol #1 may occur according to the TA value. In this case, the UE may determine that the relevant scheduling is invalid and discard the corresponding DCI (UL grant) as in (3-2) or handle the relevant scheduling as an error case.

[0247] [Proposed method #4] A method of calculating an N value as a reference for a PUSCH start position according to a TA value and transmitting a PUSCH when a BS indicates a PUSCH transmission start symbol (symbol #K), an LBT type, and a PUSCH start position through SLIV in a UL grant

[0248] The N value may be configured to not exceed symbol #K when the gap corresponding to the indicated PUSCH start position is added to symbol # (KN), or N may be configured to not exceed the length of one OFDM symbol based on the corresponding SCS when the UE sends PUSCH by filling the duration from the PUSCH start position to symbol #K by the CPE.

[0249] The UE may calculate the N value of each SCS and send the PUSCH by filling the gap between the indicated PUSCH start position and the symbol #K indicated by the SLIV using the CP (ie, CPE) of symbol #K.

[0250] However, if there is no gap between the PUSCH start position and symbol #K, the PUSCH may be transmitted immediately without CPE.

[0251] If one of the PUSCH start positions existing between symbol #K indicated by SLIV and symbol #(KN) calculated according to the N value based on the TA value of each SCS is indicated to the UE, the UE can send PUSCH by filling the gap between symbol #K and the indicated PUSCH start position with the CP of symbol #K. Since the length of CPE may vary according to the N value, the BS may calculate and configure the N value so that the length of CPE of each SCS does not exceed the length of one OFDM symbol. In addition, the BS may configure the N value so that a specific PUSCH start position does not exceed symbol #K indicated by SLIV according to the TA value.

[0252] For example, in Fig.11 In the example, if the UE configures the N value to not exceed the PUSCH start symbol indicated by SLIV considering the TA value, the N value may be set to 2.

[0253] That is, the proposed method is related to a method in which the length of CPE does not exceed the length of one OFDM symbol. Since the length of one OFDM symbol is different according to each SCS, the length of CPE can be configured to be no longer than the length of one OFDM symbol based on each SCS. As an example, the length of one OFDM symbol may be the symbol length of symbol #K indicated to the UE through SLIV with respect to the configured SCS.

[0254] The present proposal provides a method for determining a parameter (i.e., N value) so that the length of CPE does not exceed the length of one OFDM symbol. More specifically, the present proposal provides a method for determining a parameter N value so that the length of CPE does not exceed symbol #K (the PUSCH start symbol indicated by SLIV).

[0255] Comparing the proposed method #4 with the above-mentioned proposed method #1, in the proposed method #1, the length of the CPE (i.e., the N value) is also indicated to the UE, while the proposed method #4 is related to the UE determining the N value when the N value is not indicated to the UE (e.g., RACH process or fallback DCI). Specifically, the N value is determined as an integer value so that the length of the CPE does not exceed the length of one OFDM symbol.

[0256] For example, when the N value is not configured through a higher layer signal, the N value may be determined as a maximum integer value such that the length of the CPE does not exceed the length of one OFDM symbol.

[0257] Since the length of one OFDM symbol varies according to each SCS, the SCS should be considered when determining the N value. On the other hand, the TA value should be considered for UL transmission. Therefore, the SCS and TA values ​​of the UE should be considered when determining the length of the CPE with respect to the PUSCH starting position. In addition, in a system supporting the U band applied to an embodiment of the present disclosure, the CAP type may also be considered when determining the N value, that is, the length of the channel sensing duration according to the CAP type.

[0258] As an example, the length of CPE is calculated considering the TA value of UE and the N value determined by considering SCS and CAP type. When the calculated length of CPE exceeds the length of one OFDM symbol, the length of one symbol may be determined as the length of CPE.

[0259] The UE may start PUSCH transmission at a position earlier than symbol #K by the length of CPE.

[0260] Reference Fig.12 and Fig.13, the UE may receive information about the PUSCH start symbol #K (S1210 and S1310) and transmit the PUSCH at a specific position based on the result of performing the CAP (S1220 and S1330). For example, the symbol #K and the CAP type may be indicated by the DCI. The specific position may be in front of the symbol #K and may be a position earlier than the length of the CPE. That is, the UE may start PUSCH transmission at a position earlier than the length of the CPE than the symbol #K. As a parameter related to the length of the CPE, the N value may be configured by a high-layer signal as in the proposed method #1 or may be determined as an integer value such that the length of the CPE does not exceed the length of one OFDM symbol as in the proposed method #4. The length of one OFDM symbol length may differ according to the SCS and may be, for example, the length of the symbol #K. That is, the parameter N value may be an integer value (e.g., a maximum integer value) such that the length of the CPE does not exceed the symbol #K. The UE may determine the PUSCH start position based on the length of the CPE (S1320). As an example, the parameter may be determined based on the SCS and the CAP type, and the length of the CPE may be determined based on the parameter and the TA value. The UE may start PUSCH transmission at a position earlier than symbol #K by the length of CPE.

[0261] [Proposed Method #5] Although the BS has considered the LBT type (or CAP type) and the UE's TA value to indicate CPE when scheduling PUSCH for the UE through UL grant, if the CPE duration calculated by the UE becomes different from the value originally expected by the BS due to an inaccurate TA value, so that the gap between transmissions does not match the LBT type indicated to the UE, the UE may operate as follows.

[0262] (5-1) When the initially indicated LBT type is 25μs Cat-2 LBT and the gap between actual transmissions is greater than 25μs, a method for performing 25μs Cat-2 LBT and sending PUSCH 25μs before the UL start time actually calculated by the UE

[0263] (5-2) When the initially indicated LBT type is 16μs Cat-2 LBT and the gap between actual transmissions is greater than 16μs, a method for performing 16μs Cat-2 LBT and sending PUSCH 16μs before the UL start time actually calculated by the UE

[0264] (5-3) When the initially indicated LBT type is 16μs Cat-2 LBT and the gap between actual transmissions is greater than 25μs, a method of performing 25μs Cat-2 LBT and sending PUSCH before the UL start time actually calculated by the UE is 25μs

[0265] (5-4) When the initially indicated LBT type is 16μs Cat-1 LBT and the gap between actual transmissions is greater than 16μs, a method for performing 16μs Cat-2 LBT and sending PUSCH 16μs before the UL start time actually calculated by the UE

[0266] (5-5) When the initially indicated LBT type is 16μs Cat-1 LBT and the gap between actual transmissions is greater than 25μs, a method for performing 25μs Cat-2 LBT and sending PUSCH before the UL start time actually calculated by the UE is 25μs

[0267] (5-6) Method for skipping PUSCH transmission when the initially indicated LBT type is 16μs Cat-1 LBT and the gap between actual transmissions is greater than 16μs

[0268] (5-7) A method for transmitting PUSCH in Cat-1 LBT by allowing the CPE to be longer than the length of one OFDM symbol when the initially indicated LBT type is 16μs Cat-1 LBT and the gap between actual transmissions is greater than 16μs

[0269] The BS may indicate the CPE and LBT type by considering the TA value of the UE during UL scheduling through UL grant by tracking the TA value of the UE after establishing an RRC connection with the UE. However, when the TA value managed by the BS and the actual TA value of the UE are different from each other, the length of the CPE calculated based on the indication of the BS may be less than 0 or longer than the length of one OFDM symbol. If the length of the CPE is maintained at a value that is always greater than 0 and less than the length of one OFDM symbol, the gap between transmissions considered by the BS during UL scheduling and the LBT type corresponding thereto may not match the actual length of the gap.

[0270] That is, the TA value of the BS and the actual TA value of the UE may be different, so that the gap before UL scheduling may be longer than the length of the gap originally expected by the BS. For example, although the BS indicates the CPE to indicate a 25μs Cat-2 LBT under the assumption that the gap between the previous transmission and the UL transmission to be scheduled is 25μs by considering the TA value and the LBT gap, when the length of the CP is calculated using the actual TA value of the UE, the length of the CP required for the 25μs gap may be greater than the length of one symbol. In this case, if the length of the CP is limited to not more than the length of one symbol, the gap between the previous transmission and the UL transmission scheduled by the UE may be greater than 25μs. Therefore, since the indicated LBT type, the actual length of the gap, and the recalculated actual UL transmission start time are changed, the UE can operate as in the methods of (5-1) to (5-7).

[0271] More specifically, referring to the CPE calculation section of Section 5.3.1 of TS 38.211, the UE calculates Text using the formula in Table 5.3.1-1 based on the information indicated by the UL grant and applies the formula The final CPE value calculated. As described above, if the required Text value calculated by the UE based on the actual TA value is greater than the length of one OFDM symbol, but the CP length of the maximum length of one OFDM symbol shorter than the actual required length according to the above formula is applied, the length of the gap between the previous transmission and the scheduled UL transmission may be longer than the length expected by the BS. Therefore, in this case, the gap between the indicated LBT type and the actual transmission may be different, and the UE may send PUSCH by applying the methods (5-1) to (5-7).

[0272] In the case of method (7), since 16μs Cat-1 LBT can be applied only when the length of the gap between transmissions is exactly 16μs, a CP length longer than the length of one OFDM symbol is allowed as an exception to allow the UE to send PUSCH even when the gap between transmissions is greater than 16μs due to the limitation of the CP length.

[0273] The proposed method #5 is applicable to other UL signals / channels that require CPE, such as PUCCH or SRS scheduled by DL assignment and PUSCH scheduled by UL grant.

[0274] [Proposed Method #6] When the indicated LBT type and gap do not match the actual TA value of the UE based on the TA value of the UE tracked by the BS, thereby requiring a CPE of more than one symbol length, the UE may operate as follows.

[0275] (6-1) If the LBT type indicated by the BS or performed by the UE is Cat-4 LBT, the CPE length calculated by the CPE calculation formula defined in Section 5.3.1 of TS 38.211 may be applied, and the corresponding UL transmission may be discarded in case of Cat-1 LBT or 16μs or 25μs Cat-2 LBT.

[0276] (6-2) If the LBT type indicated by the BS or performed by the UE is Cat-1 LBT or 16μs or 25μs Cat-2 LBT, the UE may indicate to the BS that the actual gap is larger than the gap expected by the BS through the previously defined or configured / indicated DM-RS sequence or through UCI piggybacking.

[0277] During UL scheduling, the BS indicates the CPE and LBT type required by the UE to the UE based on the TA value of the UE tracked by the BS considering the gap with the previously transmitted one. However, since the actual TA value of the UE may be different from the TA value of the BS, the gap between actual transmissions may be greater than the gap expected by the BS. In this case, a CPE greater than one symbol may be required.

[0278] Since the length of the CPE is specified not to exceed the maximum length of one OFDM symbol, if the LBT type indicated by the BS or performed by the UE is Cat-4 LBT, the UE can calculate Text by the formula in Table 5.3.1-1 based on the information indicated by the UL grant, and apply the final CPE value calculated by the formula If the LBT type indicated by the BS or performed by the UE is Cat-1 LBT, 16μs Cat-2 or 25μs Cat-2 LBT, since UL transmission is allowed only when the gap is exactly 16μs or 25μs, in the case the UE can discard the corresponding UL transmission.

[0279] When the UE performs a subsequent UL transmission after performing Cat-1 LBT, 16μs Cat-2 or 25μs Cat-2 LBT by sharing the COT obtained by the BS through Cat-4 LBT for DL transmission, if the gap between the DL transmission and the UL transmission is exactly 16μs or 25μs and there is a COT left after the UL transmission (for example, DL length + UL length < COT length), multiple DL / UL handovers where the BS can perform a DL transmission again after the UL transmission can be performed. If the gap between the DL transmission and the UL transmission within the COT is greater than 16μs or 25μs, when a 16μs or 25μs Cat-2 LBT is successfully performed immediately before the UL transmission and subsequent DL transmission cannot be performed even if there is a COT left, a single UL transmission can be performed. Since only a single DL-UL handover transmission allows this paused COT operation, if the actual length of the gap is greater than the gap expected by the BS, that is, if then the BS can be informed through the DM-RS sequence predefined or preconfigured / indicated in the standard or through UCI piggybacking that it is impossible to perform multiple DL / UL handover transmissions of DL transmission followed by UL transmission. This proposal is especially applicable when the LBT type indicated by the BS or performed by the UE is Cat-1 LBT, 16μs Cat-2 or 25μs Cat-2 LBT.

[0280] [Proposed method #7] When a UE intends to determine a reference duration T for CWS adjustment for a UE-initiated COT in a carrier aggregation (CA) case where multiple cells with different SCSs are configured, a method for configuring the reference duration T and reflecting the HARQ-ACK for the PUSCH in the reference duration T to adjust the CWS as follows

[0281] (7-1) Method based on cell configuration in which unicast PUSCH is transmitted by all resources allocated to PUSCH until the nearest time slot boundary as T

[0282] (7-2) Method of configuring T as the nearest time slot boundary in any cell configured with CA

[0283] (7-3) Method of configuring T to be the time slot boundary closest to the cell with the minimum or maximum SCS

[0284] (7-4) Method of configuring the time slot boundary of a specific cell closest to the BS configured / indicated by RRC, DCI, or a combination of RRC and DCI as T

[0285] (7-5) Method of configuring T until the time slot boundary closest to the cell with the lowest index or the highest index

[0286] However, the reference duration T for CWS adjustment in a cell having a specific SCS may be the first one of the duration from the start of the COT to the end of the first time slot of at least one PUSCH transmitted through all resources allocated to the PUSCH and the duration from the start of the COT to the end of the first UL burst including the PUSCH transmitted by the UE through all resources allocated to the PUSCH. Although there is channel occupancy with the PUSCH, if the PUSCH is not transmitted through all resources allocated to the PUSCH, the first UL burst duration of the UE in the channel occupancy including the PUSCH may be the reference duration T for CWS adjustment.

[0287] When the UE receives data scheduling from a single cell, the duration of the time slot from the UE-initiated COT to the unicast PUSCH sent through all resources allocated to the PUSCH among the PUSCHs constituting the UL burst can be configured as a reference duration T. However, when the UE is configured to receive scheduled CA from multiple cells with different SCSs, the time slot boundaries may differ according to each cell. In NR, since the UE can also receive CBG-based scheduling or non-time slot-based scheduling in addition to time slot-based scheduling, the unicast PUSCH sent through all resources allocated to the PUSCH occurs in a cell with a specific SCS. Therefore, if it is desired to configure the reference duration T, the reference duration T may not be aligned with the time slot boundary of a cell with another SCS. In this case, an agreement / definition as in the methods (7-1) to (7-5) above may be required to determine which time slot of each cell should be included in the reference duration T.

[0288] Fig.14 A case is shown where three cells with different SCSs are configured with CA and UL transmission is scheduled for the UE.

[0289] Reference Fig.14 , cells A, B, and C having different SCSs are configured with CA and UL transmission is scheduled for the UE. TB2 transmitted in the mini-slot appears in the 30kHz cell B through the PUSCH transmitted by all resources allocated to the PUSCH, and is configured as a reference duration T based on the cell transmitted through all resources allocated to the PUSCH until the boundary of the nearest slot as in method (7-1). That is, TB 2 transmitted through all resources allocated to the PUSCH appears in the middle of the first slot of the cell B, thereby configuring a reference duration T including a duration based on the SCS of 30kHz to the end of the slot including TB 2. In the case of cell C, since TB 5 and TB 6 belong to the configured reference duration T, the reference duration T can be reflected in the CWS adjustment of the UE according to the decoding results of TB 2, TB 3, TB 5, and TB 6 (whether retransmission scheduling by NDI is performed).

[0290] Fig.15 Another case is shown where three cells with different SCSs are configured with CA and UL transmission is scheduled for the UE.

[0291] If in Fig.15 In the case shown, if the reference duration T is configured in method (7-2), the time slot until TB 5 of cell C is scheduled based on TB2 can be configured as T.

[0292] Fig.16Another case is shown where three cells with different SCSs are configured with CA and UL transmission is scheduled for the UE.

[0293] If the reference duration T is configured based on the minimum SCS in method (7-3), the time slots up to and including TB1 of cell A are configured as the reference duration T, so that all TBs are included in the reference duration T. If the reference duration T is configured based on the large SCS, the time slots up to and including TB 5 of scheduled cell C may be configured as the reference duration T as in method (7-2).

[0294] The BS may indicate / configure in advance to the UE whether to configure the reference duration T based on the time slot boundary of any cell through RRC, DCI, or a combination of RRC and DCI as in (7-4). Alternatively, as in (7-5), the reference duration T may be configured based on the time slot boundary of the cell with the minimum or maximum cell index among the multiple cells configured with CA.

[0295] [Proposed method #8] When the minimum duration D1 consumed by the UE until a UL grant containing feedback for the PUSCH (e.g., NDI or CBG transmission information (CBGTI)) is received from the BS through a higher layer signal such as RRC, and then the UE expects to configure a reference duration T in the latest UE-initiated COT before n-D1 for UL CWS adjustment, if there is no PUSCH sent through all resources allocated to the PUSCH among the unicast PUSCHs sent from the corresponding COT to n-D1 in the COT (in other words, PUSCHs sent through only some of all resources allocated to the PUSCH among the unicast PUSCHs sent from the COT to n-D1), the reference duration T may be configured as follows and reflected in the CWS adjustment.

[0296] (8-1) Method for configuring reference duration T based only on PUSCHs transmitted through some resources allocated to PUSCHs among PUSCHs transmitted in the latest UE-initiated COT before n-D1

[0297] (8-2) Method for configuring the reference duration T based on the feedback result within the reference duration T by returning to the most recent (previous) UE-initiated COT sent earlier

[0298] Here, D1 is the time from the last symbol of PUSCH to the start symbol of the UL grant containing feedback, and can be configured in units of slots or symbols. If D1 is not configured, but the minimum duration D2 consumed after CG-PUSCH transmission until CG-DFI is received is configured, D2 may be used as the D1 value. Even if the D1 value is configured, the D1 value may be replaced with a D2 value previously defined in a previous configuration / indication or standard, or the D1 value may be determined as a function of the D1 and D2 values, such as min(D1, D2) or max(D1, D2).

[0299] For UE-initiated channel occupancy, the reference duration for CWS adjustment may be defined as follows. For channel occupancy with a set of PUSCH and LBT bandwidth maintaining a single contention window, the reference duration for CWS adjustment may be the duration first generated from the start of channel occupancy to the end of the first time slot in which at least one PUSCH is sent through all resources allocated to PUSCH and the duration from the start of channel occupancy to the end of the first transmission burst of PUSCH including the UE sent through all resources allocated to PUSCH. If there is channel occupancy with PUSCH, but PUSCH is not sent through all resources allocated to PUSCH, the duration of the first transmission burst of the UE in the channel occupancy including PUSCH may be the reference duration for CWS adjustment.

[0300] The UE may receive a minimum duration D1 required to receive a UL grant including feedback on a PUSCH transmitted by the BS through a high-layer signal such as RRC. Upon receiving the UL grant, the UE may configure a reference duration T for CWS adjustment until a PUSCH slot transmitted through all resources allocated to the PUSCH among the PUSCH transmitted in the latest UE-initiated COT before n-D1, and adjust the CWS based on the feedback result of the PUSCH within the reference duration. However, if a PUSCH transmitted through all resources allocated to the PUSCH among the PUSCH transmitted in the latest UE-initiated COT before n-D1 does not exist at the CWS adjustment timing, the reference duration T may not be configured according to the definition of the reference duration.

[0301] Fig.17 The CWS adjustment timing and PUSCH of the UE in the latest UE-initiated COT before the configured D1 are exemplarily shown.

[0302] exist Fig.17In the case of, when D1=4 (time slot) is configured, the UE receives UL grant in time slot #5, and among the PUSCHs sent in the latest UE-initiated COT before D1, in order to perform CWS adjustment, the PUSCHs sent with HARQ ID #0 and HARQ ID #1 are not sent through all resources allocated to the PUSCH, and the PUSCHs sent with HARQ ID #2 are sent through all resources allocated to the PUSCH. In this example, since there is no PUSCH sent through all resources allocated to the PUSCH in the latest UE-initiated COT before n-D1 at the time when the UE receives the UL grant, according to the definition of the reference duration, the reference duration T may not be configured.

[0303] In this case, the UE can adjust the CWS by (8-1) or (8-2) of the proposed method. In the case of (8-1), although the reference duration T is not configured because there is no PUSCH transmitted through all resources allocated to the PUSCH in the latest UE-initiated COT before n-D1, the PUSCH transmitted through some resources is configured as the reference duration T (in Fig.11 In the example of , the duration until the PUSCH is transmitted with HARQ ID #0 is configured as T). In the case of (8-2), the CWS is adjusted based on the feedback result within the reference duration T by returning to the UL burst transmitted earlier than the latest UE-initiated COT n-D1 ago.

[0304] The UE may perform a process of accessing the network to perform the process and / or method described / proposed in the present disclosure ( Figures 10 to 17 ). For example, while accessing a network (e.g., a BS), the UE may receive system information and configuration information required to perform the processes and / or methods described / proposed above, and store the system information and configuration information in a memory. The configuration information required for the present disclosure may be received via high-level (e.g., RRC, MAC, or layer) signaling.

[0305] Fig.18 is a diagram showing initial network access and subsequent communication processing. In NR, physical channels and RSs may be sent through beamforming. When beamforming-based signal transmission is supported, beam management may follow for beam alignment between the BS and the UE. In addition, the signals proposed in the present disclosure may be sent / received through beamforming. In RRC_IDLE mode, beam alignment may be performed based on SSB, and in RRC_CONNECTED mode, beam alignment may be performed based on CSI-RS (in DL) and SRS (in UL). Conversely, when beamforming-based signal transmission is not supported, the beam-related operations described below may be skipped.

[0306] Reference Fig.18 , the BS (e.g., eNB) may periodically send SSBs (S2102). SSBs include PSS / SSS / PBCH. SSBs may be sent through beam scanning. PBCH may include a master information block (MSB), and MIB may include scheduling information of the remaining minimum system information (RMSI). The BS may then send RMSI and other system information (OSI) (S2104). RMSI may include information required for initial access to the BS (e.g., PRACH configuration information). After detecting the SSBs, the UE identifies the best SSB. The UE may then send a RACH preamble (message 1; Msg1) in a PRACH resource linked / corresponding to the index (i.e., beam) of the best SSB (S2106). The beam direction of the RACH preamble is associated with the PRACH resource. The association between the PRACH resource (and / or RACH preamble) and the SSB (SSB index) may be configured by system information (e.g., RMSI). Subsequently, in the RACH process, the BS may send a random access response (RAR) (Msg2) (S2108) in response to the RACH preamble, the UE may send Msg3 (e.g., RRC connection request) (S2110) based on the UL grant included in the RAR, and the BS may send a contention resolution message (Msg4) (S2120). Msg4 may include RRC connection establishment.

[0307] When an RRC connection is established between the BS and the UE during the RACH process, beam alignment may then be performed based on the SSB / CSI-RS (in DL) and the SRS (in UL). For example, the UE may receive the SSB / CSI-RS (S2114). The SSB / CSI-RS may be used by the UE to generate a beam / CSI report. The BS may request the UE to send a beam / CSI report via DCI (S2116). In this case, the UE may generate a beam / CSI report based on the SSB / CSI-RS and send the generated beam / CSI report to the BS on the PUSCH / PUCCH (S2118). The beam / CSI report may include beam measurement results, information about a preferred beam, and the like. The BS and the UE may switch beams based on the beam / CSI report (S2120a and S2120b).

[0308] Subsequently, the UE and the BS may perform the above described / proposed procedures and / or methods ( Figures 10 to 17). For example, based on the configuration information obtained in the network access process (e.g., the system information acquisition process, the RRC connection process on the RACH, etc.), the UE and the BS may send a wireless signal by processing the information stored in the memory, or may process the received wireless signal according to the proposal of the present disclosure and store the processed signal in the memory. The wireless signal may include at least one of the PDCCH, PDSCH, or RS on the DL and at least one of the PUCCH, PUSCH, or SRS on the UL.

[0309] Each of the above-proposed methods can be combined and applied together with other proposed methods unless they conflict with each other.

[0310] The various descriptions, functions, processes, proposals, methods and / or operational flowcharts of the present disclosure described herein may be applied to (but not limited to) various fields requiring wireless communication / connection between devices (e.g., 5G).

[0311] More specific examples will be described below with reference to the accompanying drawings. In the following drawings / descriptions, similar reference numerals represent the same or corresponding hardware blocks, software blocks or functional blocks unless otherwise specified.

[0312] Fig.19 A communication system 1 applied to the present disclosure is shown.

[0313] Reference Fig.19, the communication system 1 applied to the present disclosure includes a wireless device, a BS, and a network. The wireless device is a device that performs communication using a radio access technology (RAT) (e.g., 5G NR (or new RAT) or LTE), also referred to as a communication / radio / 5G device. The wireless device may include (but is not limited to) a robot 100a, a vehicle 100b-1 and 100b-2, an extended reality (XR) device 100c, a handheld device 100d, a home appliance 100e, an IoT device 100f, and an artificial intelligence (AI) device / server 400. For example, a vehicle may include a vehicle with a wireless communication function, an autonomous driving vehicle, and a vehicle capable of vehicle-to-vehicle (V2V) communication. Herein, a vehicle may include an unmanned aerial vehicle (UAV) (e.g., a drone). The XR device may include an augmented reality (AR) / virtual reality (VR) / mixed reality (MR) device, and may be implemented in the form of a head-mounted device (HMD), a head-up display (HUD) installed in a vehicle, a television (TV), a smart phone, a computer, a wearable device, a home appliance, a digital signage, a vehicle, a robot, and the like. Handheld devices may include smart phones, smart boards, wearable devices (e.g., smart watches or smart glasses), and computers (e.g., laptop computers). Home appliances may include TVs, refrigerators, washing machines, etc. IoT devices may include sensors, smart meters, etc. For example, a BS and a network may be implemented as wireless devices, and a specific wireless device 200a may operate as a BS / network node for other wireless devices.

[0314] The wireless devices 100a to 100f may be connected to the network 300 via the BS 200. AI technology may be applied to the wireless devices 100a to 100f, and the wireless devices 100a to 100f may be connected to the AI ​​server 400 via the network 300. The network 300 may be configured using a 3G network, a 4G (e.g., LTE) network, or a 5G (e.g., NR) network. Although the wireless devices 100a to 100f may communicate with each other via the BS 200 / network 300, the wireless devices 100a to 100f may perform direct communication (e.g., side link communication) with each other without the intervention of the BS / network. For example, the vehicles 100b-1 and 100b-2 may perform direct communication (e.g., V2V / vehicle-to-everything (V2X) communication). An IoT device (e.g., a sensor) may perform direct communication with other IoT devices (e.g., a sensor) or other wireless devices 100a to 100f.

[0315] Wireless communication / connection 150a, 150b, and 150c may be established between wireless devices 100a to 100f / BS 200 and between BSs 200. Herein, wireless communication / connection may be established through various RATs (e.g., 5G NR) such as UL / DL communication 150a, sidelink communication 150b (or D2D communication), or inter-BS communication (e.g., relay or integrated access backhaul (IAB)). Wireless signals may be sent and received between wireless devices, between wireless devices and BSs, and between BSs through wireless communication / connection 150a, 150b, and 150c. For example, signals may be sent and received via various physical channels through wireless communication / connection 150a, 150b, and 150c. To this end, at least a portion of various configuration information for configuring a process for sending / receiving wireless signals, various signal processing processes (e.g., channel coding / decoding, modulation / demodulation, and resource mapping / demapping), and a resource allocation process may be performed based on various proposals of the present disclosure.

[0316] Fig. 20 A wireless device suitable for use with the present disclosure is shown.

[0317] Reference Fig. 20 , the first wireless device 100 and the second wireless device 200 may transmit wireless signals via various RATs (e.g., LTE and NR). {The first wireless device 100 and the second wireless device 200} may correspond to Fig.19 {wireless device 100x and BS 200} and / or {wireless device 100x and wireless device 100x}.

[0318] The first wireless device 100 may include one or more processors 102 and one or more memories 104, and also include one or more transceivers 106 and / or one or more antennas 108. The processor 102 may control the memory 104 and / or the transceiver 106, and may be configured to implement the description, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document. For example, the processor 102 may process the information in the memory 104 to generate first information / signals, and then transmit a wireless signal including the first information / signals through the transceiver 106. The processor 102 may receive a wireless signal including second information / signals through the transceiver 106, and then store information obtained by processing the second information / signals in the memory 104. The memory 104 may be connected to the processor 102, and may store various information related to the operation of the processor 102. For example, the memory 104 may store software codes including instructions for executing all or part of the processing controlled by the processor 102 or for executing the description, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document. The processor 102 and the memory 104 may be part of a communication modem / circuit / chip designed to implement a RAT (e.g., LTE or NR). The transceiver 106 may be connected to the processor 102 and transmit and / or receive wireless signals through one or more antennas 108. Each transceiver 106 may include a transmitter and / or a receiver. The transceiver 106 may be used interchangeably with a radio frequency (RF) unit. In the present disclosure, the wireless device may be a communication modem / circuit / chip.

[0319] The second wireless device 200 may include one or more processors 202 and one or more memories 204, and also include one or more transceivers 206 and / or one or more antennas 208. The processor 202 may control the memory 204 and / or the transceiver 206, and may be configured to implement the description, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document. For example, the processor 202 may process the information in the memory 204 to generate third information / signals, and then transmit a wireless signal including the third information / signals through the transceiver 206. The processor 202 may receive a wireless signal including fourth information / signals through the transceiver 106, and then store information obtained by processing the fourth information / signals in the memory 204. The memory 204 may be connected to the processor 202 and store various information related to the operation of the processor 202. For example, the memory 204 may store software codes including instructions for executing all or part of the processing controlled by the processor 202 or for executing the description, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document. The processor 202 and the memory 204 may be part of a communication modem / circuit / chip designed to implement a RAT (e.g., LTE or NR). The transceiver 206 may be connected to the processor 202 and transmit and / or receive wireless signals through one or more antennas 208. Each transceiver 206 may include a transmitter and / or a receiver. The transceiver 206 may be used interchangeably with an RF unit. In the present disclosure, the wireless device may be a communication modem / circuit / chip.

[0320] Now, the hardware elements of the wireless devices 100 and 200 will be described in more detail. One or more protocol layers may be implemented by (but not limited to) one or more processors 102 and 202. For example, one or more processors 102 and 202 may implement one or more layers (e.g., functional layers such as physical (PHY), medium access control (MAC), radio link control (RLC), packet data convergence protocol (PDCP), RRC, and service data adaptation protocol (SDAP)). One or more processors 102 and 202 may generate one or more protocol data units (PDUs) and / or one or more service data units (SDUs) according to the descriptions, functions, processes, proposals, methods, and / or operational flowcharts disclosed in this document. One or more processors 102 and 202 may generate messages, control information, data, or information according to the descriptions, functions, processes, proposals, methods, and / or operational flowcharts disclosed in this document, and provide these messages, control information, data, or information to one or more transceivers 106 and 206. One or more processors 102 and 202 may generate a signal (e.g., a baseband signal) including a PDU, SDU, message, control information, data, or information according to the description, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document, and provide the generated signal to one or more transceivers 106 and 206. One or more processors 102 and 202 may receive a signal (e.g., a baseband signal) from one or more transceivers 106 and 206 and obtain the PDU, SDU, message, control information, data, or information according to the description, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document.

[0321] One or more processors 102 and 202 may be referred to as controllers, microcontrollers, microprocessors or microcomputers. One or more processors 102 and 202 may be implemented by hardware, firmware, software or a combination thereof. For example, one or more application specific integrated circuits (ASICs), one or more digital signal processors (DSPs), one or more digital signal processing devices (DSPDs), one or more programmable logic devices (PLDs) or one or more field programmable gate arrays (FPGAs) may be included in one or more processors 102 and 202. The descriptions, functions, processes, proposals, methods and / or operational flow charts disclosed in this document may be implemented using firmware or software, and the firmware or software may be configured to include modules, processes or functions. Firmware or software configured to execute the descriptions, functions, processes, proposals, methods and / or operational flow charts disclosed in this document may be included in one or more processors 102 and 202 or may be stored in one or more memories 104 and 204 and driven by one or more processors 102 and 202. The descriptions, functions, processes, proposals, methods and / or operational flow charts disclosed in this document may be implemented in the form of codes, instructions and / or instruction sets using firmware or software.

[0322] One or more memories 104 and 204 may be connected to one or more processors 102 and 202 and store various types of data, signals, messages, information, programs, codes, instructions and / or commands. One or more memories 104 and 204 may be configured to include read-only memory (ROM), random access memory (RAM), electrically erasable programmable read-only memory (EPROM), flash memory, hard drive, registers, cache memory, computer-readable storage media and / or combinations thereof. One or more memories 104 and 204 may be located inside and / or outside of one or more processors 102 and 202. One or more memories 104 and 204 may be connected to one or more processors 102 and 202 via various technologies such as wired or wireless connections.

[0323] One or more transceivers 106 and 206 may send user data, control information and / or wireless signals / channels mentioned in the method and / or operation flow chart of this document to one or more other devices. One or more transceivers 106 and 206 may receive user data, control information and / or wireless signals / channels mentioned in the description, function, process, proposal, method and / or operation flow chart disclosed in this document from one or more other devices. For example, one or more transceivers 106 and 206 may be connected to one or more processors 102 and 202 and send and receive wireless signals. For example, one or more processors 102 and 202 may perform control so that one or more transceivers 106 and 206 may send user data, control information or wireless signals to one or more other devices. One or more processors 102 and 202 may perform control so that one or more transceivers 106 and 206 may receive user data, control information or wireless signals from one or more other devices. One or more transceivers 106 and 206 may be connected to one or more antennas 108 and 208, and one or more transceivers 106 and 206 may be configured to send and receive user data, control information and / or radio signals / channels mentioned in the description, functions, processes, proposals, methods and / or operation flow charts disclosed in this document through one or more antennas 108 and 208. In this document, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). One or more transceivers 106 and 206 may convert the received wireless signals / channels from RF band signals to baseband signals so as to process the received user data, control information and wireless signals / channels using one or more processors 102 and 202. One or more transceivers 106 and 206 may convert the user data, control information and wireless signals / channels processed using one or more processors 102 and 202 from baseband signals to RF band signals. To this end, one or more of the transceivers 106 and 206 may include (analog) oscillators and / or filters.

[0324] Fig.21 Another example of a wireless device applicable to the present disclosure is shown. The wireless device can be used according to the usage / service (refer to Fig.19 ) are implemented in various forms.

[0325] Reference Fig.21 , the wireless devices 100 and 200 may correspond to Fig. 20The wireless devices 100 and 200 of the present invention may be configured to include various elements, components, units / portions and / or modules. For example, each of the wireless devices 100 and 200 may include a communication unit 110, a control unit 120, a memory unit 130 and an additional component 140. The communication unit 110 may include a communication circuit 112 and a transceiver 114. For example, the communication circuit 112 may include Fig. 20 One or more processors 102 and 202 and / or one or more memories 104 and 204. For example, the transceiver 114 may include Fig. 20 The control unit 120 is electrically connected to the communication unit 110, the memory 130, and the additional components 140, and provides overall control of the wireless device. For example, the control unit 120 may control the electrical / mechanical operation of the wireless device based on the program / code / instruction / information stored in the memory unit 130. The control unit 120 may send information stored in the memory unit 130 to the outside (e.g., other communication devices) via the communication unit 110 through a wireless / wired interface, or store information received from the outside (e.g., other communication devices) via the communication unit 110 in the memory unit 130 through a wireless / wired interface.

[0326] The additional component 140 may be configured in various ways depending on the type of wireless device. For example, the additional component 140 may include at least one of a power supply unit / battery, an input / output (I / O) unit, a drive unit, and a computing unit. The wireless device may be configured in (but not limited to) a robot ( Fig.19 100a), vehicles ( Fig.19 100b-1 and 100b-2), XR devices ( Fig.19 100c), handheld device ( Fig.19 100d), household appliances ( Fig.19 100e), IoT devices ( Fig.19 100f), digital broadcasting terminal, holographic device, public safety device, MTC device, medical device, fintech device (or financial device), security device, climate / environmental device, AI server / device ( Fig.19 400), BS( Fig.19 200), network nodes, etc. Depending on the use case / service, the wireless device can be mobile or fixed.

[0327] exist Fig.21In the wireless devices 100 and 200, various elements, components, units / parts and / or modules in the wireless devices 100 and 200 may all be connected to each other through a wired interface, or at least a part thereof may be wirelessly connected through the communication unit 110. For example, in each of the wireless devices 100 and 200, the control unit 120 and the communication unit 110 may be wired, and the control unit 120 and the first unit (e.g., 130 and 140) may be wirelessly connected through the communication unit 110. The various elements, components, units / parts and / or modules in the wireless devices 100 and 200 may also include one or more elements. For example, the control unit 120 may be configured using a collection of one or more processors. For example, the control unit 120 may be configured using a collection of a communication control processor, an application processor, an electronic control unit (ECU), a graphics processing unit and a memory control processor. In another example, the memory 130 may be configured using RAM, dynamic RAM (DRAM), ROM, flash memory, volatile memory, non-volatile memory and / or a combination thereof.

[0328] Fig. 22 A vehicle or an autonomous vehicle applied to the present disclosure is shown. The vehicle or the autonomous vehicle may be implemented as a mobile robot, a car, a train, a manned / unmanned aerial vehicle (AV), a ship, etc.

[0329] Reference Fig. 22 , the vehicle or autonomous driving vehicle 100 may include an antenna unit 108, a communication unit 110, a control unit 120, a drive unit 140a, a power supply unit 140b, a sensor unit 140c, and an autonomous driving unit 140d. The antenna unit 108 may be configured as a part of the communication unit 110. Blocks 110 / 130 / 140a to 140d correspond to Fig.21 Block 110 / 130 / 140.

[0330] The communication unit 110 may send and receive signals (e.g., data and control signals) to and from external devices such as other vehicles, BSs (e.g., gNBs and roadside units), and servers. The control unit 120 may perform various operations by controlling elements of the vehicle or autonomous driving vehicle 100. The control unit 120 may include an ECU. The drive unit 140a may enable the vehicle or autonomous driving vehicle 100 to travel on a road. The drive unit 140a may include an engine, a motor, a power system, wheels, brakes, a steering device, etc. The power supply unit 140b may supply power to the vehicle or autonomous driving vehicle 100, and include a wired / wireless charging circuit, a battery, etc. The sensor unit 140c may obtain information about the vehicle status, surrounding environment information, user information, etc. The sensor unit 140c may include an inertial measurement unit (IMU) sensor, a collision sensor, a wheel sensor, a speed sensor, a slope sensor, a weight sensor, a heading sensor, a position module, a vehicle forward / reverse sensor, a battery sensor, a fuel sensor, a tire sensor, a steering sensor, a temperature sensor, a humidity sensor, an ultrasonic sensor, a lighting sensor, a pedal position sensor, etc. The autonomous driving unit 140d may implement a technology for maintaining a lane in which the vehicle is traveling, a technology for automatically adjusting a speed (e.g., adaptive cruise control), a technology for autonomously traveling along a determined path, a technology for traveling by automatically setting a route if a destination is set, and the like.

[0331] For example, the communication unit 110 may receive map data, traffic information data, etc. from an external server. The autonomous driving unit 140d may generate an autonomous driving route and a driving plan from the obtained data. The control unit 120 may control the drive unit 140a so that the vehicle or the autonomous driving vehicle 100 may move along the autonomous driving route according to the driving plan (e.g., speed / direction control). During autonomous driving, the communication unit 110 may aperiodically / periodically obtain the latest traffic information data from the external server and obtain surrounding traffic information data from neighboring vehicles. During autonomous driving, the sensor unit 140c may obtain information about the vehicle state and / or surrounding environment information. The autonomous driving unit 140d may update the autonomous driving route and driving plan based on the newly obtained data / information. The communication unit 110 may transmit information about the vehicle position, autonomous driving route, and / or driving plan to an external server. The external server may predict traffic information data using AI technology based on information collected from the vehicle or autonomous driving vehicle, and provide the predicted traffic information data to the vehicle or autonomous driving vehicle.

[0332] The above-mentioned embodiments of the present disclosure are combinations of elements and features of the present disclosure. Unless otherwise mentioned, elements or features may be considered as selective. Each element or feature may be put into practice without being combined with other elements or features. In addition, the embodiments of the present disclosure may be constructed by combining some elements and / or features. The order of operations described in the embodiments of the present disclosure may be rearranged. Some constructions of any one embodiment may be included in another embodiment and may be replaced by the corresponding construction of another embodiment. It is obvious to those skilled in the art that the claims that are not clearly referenced to each other in the attached claims may be presented as embodiments of the present disclosure in combination, or may be included as new claims by subsequent amendments after submitting an application.

[0333] The above focuses on the signal transmission and reception relationship between the UE and the BS to describe the embodiments of the present disclosure. The signal transmission and reception relationship is extended to the signal transmission and reception between the UE and the repeater or between the BS and the repeater in the same manner or in a similar manner. The specific operation described as being performed by the BS may be performed by the upper node of the BS. That is, it is obvious that in a network composed of multiple network nodes including the BS, various operations performed for communicating with the UE may be performed by the BS or network nodes other than the BS. The term BS may be replaced by the term fixed station, Node B, enhanced Node B (eNode B or eNB), access point, etc. In addition, the term UE may be replaced by the term terminal, mobile station (MS), mobile subscriber station (MSS), etc.

[0334] Those skilled in the art will appreciate that the present disclosure may be implemented in other specific forms other than those described herein without departing from the spirit and essential characteristics of the present disclosure. Therefore, the above-described embodiments should be interpreted as being illustrative in all respects, rather than restrictive. The scope of the present disclosure should be determined by the appended claims and their legal equivalents, rather than by the above description, and all changes falling within the meaning and equivalent scope of the appended claims are intended to be covered therein.

[0335] Industrial Applicability

[0336] The present disclosure may be used in a UE, a BS or other devices in a mobile communication system.

Claims

1. A method performed by a user equipment UE in a wireless communication system, the method comprising the following steps: Receiving information on a value N of a symbol #KN preceding a start symbol #K of a physical uplink shared channel PUSCH from a base station BS, wherein the value N is a positive integer; receiving an uplink UL grant including first information related to the starting symbol #K for the PUSCH and second information related to a starting position for PUSCH transmission; and sending the PUSCH based on the UL grant, wherein an interval of a cyclic prefix extension CPE before the start symbol #K of the PUSCH is determined based on the value N and the second information, and The value N is configured by the BS so that the interval for the CPE is equal to or less than the length of one orthogonal frequency division multiplexing (OFDM) symbol.

2. The method according to claim 1, wherein: The length of one OFDM symbol is determined based on the subcarrier spacing SCS.

3. The method according to claim 1, wherein: The second information is determined based on the subcarrier spacing SCS.

4. The method according to claim 3, wherein: The second information is used to notify a channel access type for the PUSCH.

5. The method according to claim 1, wherein: The interval for the CPE is determined based on the second information and a timing advance TA.

6. The method according to claim 1, wherein: The PUSCH is transmitted in an unlicensed frequency band.

7. A user equipment UE used in a wireless communication system, the UE comprising: at least one transceiver; at least one processor; as well as At least one computer memory operatively connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations comprising: Receiving information on a value N of a symbol #KN preceding a start symbol #K of a physical uplink shared channel PUSCH from a base station BS, wherein the value N is a positive integer; receiving an uplink UL grant including first information related to the starting symbol #K for the PUSCH and second information related to a starting position for PUSCH transmission; and sending the PUSCH based on the UL grant, wherein an interval of a cyclic prefix extension CPE before the start symbol #K of the PUSCH is determined based on the value N and the second information, and The value N is configured by the BS so that the interval for the CPE is equal to or less than the length of one orthogonal frequency division multiplexing (OFDM) symbol.

8. The UE according to claim 7, wherein: The UE includes an autonomous vehicle in communication with at least one of a network or another autonomous vehicle external to the UE.

9. A device for a user equipment UE, the device comprising: at least one processor; as well as At least one computer memory operatively connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations comprising: Receiving information on a value N of a symbol #KN preceding a start symbol #K of a physical uplink shared channel PUSCH from a base station BS, wherein the value N is a positive integer; receiving an uplink UL grant including first information related to the starting symbol #K for the PUSCH and second information related to a starting position for PUSCH transmission; and sending the PUSCH based on the UL grant, wherein an interval of a cyclic prefix extension CPE before the start symbol #K of the PUSCH is determined based on the value N and the second information, and The value N is configured by the BS so that the interval for the CPE is equal to or less than the length of one orthogonal frequency division multiplexing (OFDM) symbol.

10. A computer-readable storage medium storing at least one computer program comprising instructions that, when executed by at least one processor, cause the at least one processor to perform operations comprising: Receiving information on a value N of a symbol #KN preceding a start symbol #K of a physical uplink shared channel PUSCH from a base station BS, wherein the value N is a positive integer; receiving an uplink UL grant including first information related to the starting symbol #K for the PUSCH and second information related to a starting position for PUSCH transmission; and sending the PUSCH based on the UL grant, wherein an interval of a cyclic prefix extension CPE before the start symbol #K of the PUSCH is determined based on the value N and the second information, and The value N is configured by the BS so that the interval for the CPE is equal to or less than the length of one orthogonal frequency division multiplexing (OFDM) symbol.

Images