Method and apparatus for transmitting / receiving signals in a wireless communication system

Abstract

According to one embodiment of the present invention, a method and apparatus for transmitting / receiving a signal in a wireless communication system performs a 2-step random access procedure or a 4-step random access procedure in a shared spectrum. In a method for interpreting an FDRA field for PUSCH transmission corresponding to an RAR in a 4-step random access procedure or a fallback RAR in a 2-step random access procedure, X LSBs of the FDRA field are truncated or the FDRA field is filled with Y MSBs based on whether an interleaving allocation for PUSCH accessing a shared spectrum channel is set, and the FDRA field is interpreted as an FDRA field of downlink control information DCI format 0_0.

Description

Technical Field

[0001] The present disclosure relates to methods and apparatus for use in a wireless communication system. Background Art

[0002] Wireless communication systems are widely deployed to provide various types of communication services such as voice and data. Generally, wireless communication systems are multiple access systems that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmission power, etc.). Examples of multiple access systems include CDMA (Code Division Multiple Access) systems, FDMA (Frequency Division Multiple Access) systems, TDMA (Time Division Multiple Access) systems, OFDMA (Orthogonal Frequency Division Multiple Access) systems, and SC-FDMA (Single Carrier Frequency Division Multiple Access) systems, etc. Summary of the invention

[0003] Technical issues

[0004] A technical problem of the present disclosure is to provide a method for receiving and transmitting a signal for efficiently performing a random access procedure in a wireless communication system and an apparatus thereof.

[0005] The technical problems of the present disclosure are not limited to the above-mentioned technical problems, and other technical problems can be inferred from the embodiments of the present disclosure.

[0006] Technical Solution

[0007] The present disclosure provides a method and apparatus for receiving and transmitting signals in a wireless communication system.

[0008] Regarding one aspect of the present disclosure, a method for sending and receiving signals by a user equipment UE in a wireless communication system, the method comprising the following steps: receiving a random access response RAR based on a physical random access channel PRACH; and sending a physical uplink shared channel PUSCH based on the RAR; wherein the PUSCH is sent based on a frequency domain resource assignment FDRA field, wherein the FDRA field is truncated to its X least significant bits LSB, or filled with Y most significant bits MSB, based on whether an interleaved allocation of the PUSCH for shared spectrum channel access is provided, and wherein the FDRA field is interpreted as the FDRA field of downlink control information DCI format 0_0.

[0009] In another aspect of the present disclosure, a communication device (user equipment, UE) for sending and receiving signals in a wireless communication system includes: at least one transceiver; at least one processor; and at least one memory, wherein the at least one memory is operatively connected to the at least one processor and stores instructions, and the instructions cause the at least one processor to perform specific operations based on being executed, and the specific operations include the following operations: receiving a random access response RAR based on a physical random access channel PRACH; and sending a physical uplink shared channel PUSCH based on the RAR, and the PUSCH is sent based on a frequency domain resource assignment FDRA field, and, based on whether an interleaved allocation of the PUSCH for shared spectrum channel access is provided, the FDRA field is truncated to its X least significant bits LSB, or the FDRA field is filled with Y most significant bits MSB, and the FDRA field is interpreted as the FDRA field of DCI (downlink control information) DCI format 0_0.

[0010] In another aspect of the present disclosure, a device for user equipment UE includes: at least one processor; and at least one computer memory, which is operatively connected to the at least one processor and causes the at least one processor to perform operations based on being executed, and the operations include the following operations: receiving a random access response RAR based on a physical random access channel PRACH; and sending a physical uplink shared channel PUSCH based on the RAR, and the PUSCH is sent based on a frequency domain resource assignment FDRA field, and based on whether an interleaved allocation of the PUSCH for shared spectrum channel access is provided, the FDRA field is truncated to its X least significant bits LSB, or the FDRA field is filled with Y most significant bits MSB, and the FDRA field is interpreted as the FDRA field of DCI (downlink control information) DCI format 0_0.

[0011] In another aspect of the present disclosure, a computer-readable storage medium is provided, the computer-readable storage medium comprising at least one computer program for causing at least one processor to perform operations, and the operations include the following operations: receiving a random access response RAR based on a physical random access channel PRACH; and sending a physical uplink shared channel PUSCH based on the RAR; and the PUSCH is sent based on a frequency domain resource assignment FDRA field, and, based on whether an interleaved allocation of the PUSCH for shared spectrum channel access is provided, the FDRA field is truncated to its X least significant bits LSB, or the FDRA field is filled with Y most significant bits MSB, and the FDRA field is interpreted as the FDRA field of DCI (downlink control information) DCI format 0_0.

[0012] In the method and apparatus, based on the fact that the interleaved allocation of the PUSCH for access to the shared spectrum channel is not provided and the number of PRBs in a bandwidth part BWP is equal to or less than 90, the FDRA field may be truncated to its X LSBs, and the X LSBs may be determined based on the number of PRBs in the BWP.

[0013] In the method and apparatus, based on the fact that the interleaving allocation of the PUSCH for access to the shared spectrum channel is not provided and the number of PRBs in the BWP is greater than 90, the FDRA field may be populated with Y MSBs, and the Y MSBs may be determined based on the number of PRBs in the BWP.

[0014] In the method and apparatus, based on the number of PRBs in the BWP being N, the X LSBs may be determined as ceil(log2(N*(N+1) / 2)) LSBs, and the Y MSBs may be determined as ceil(log2(N*(N+1) / 2))-12 MSBs.

[0015] In the method and apparatus, the FDRA field may be received by the base station as 12 bits, and when resources are allocated based on the interleaved allocation of the PUSCH without providing access to the shared spectrum channel, the 90 may be determined taking into account the maximum number of PRBs that can be indicated by the 12 bits in the BWP.

[0016] In the method and apparatus, based on providing the interleaved allocation of the PUSCH for the shared spectrum channel access, the X LSBs may be determined as 5 LSBs for a 30kHz subcarrier spacing SCS, and may be determined as 6 LSBs for a 15kHz SCS.

[0017] The communication device may include at least a terminal, a network, and an autonomous driving vehicle capable of communicating with an autonomous driving vehicle other than the communication device.

[0018] The above-mentioned aspects of the present disclosure are only some preferred embodiments of the present disclosure, and those skilled in the art can derive and understand various embodiments reflecting the technical features of the present disclosure based on the detailed description of the present disclosure to be described below.

[0019] Beneficial Effects

[0020] According to one embodiment of the present disclosure, when a random access procedure between a UE and a base station is performed, there is an advantage that a more efficient random access procedure can be performed through an operation different from the conventional disclosure.

[0021] The technical effects of the present disclosure are not limited to the above-mentioned technical effects, and other technical effects can be inferred from the embodiments of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] Figure 1 The structure of a radio frame is illustrated.

[0023] Figure 2 A resource grid of time slots is illustrated.

[0024] Figure 3 An example of mapping physical channels in time slots is illustrated.

[0025] Figure 4 The ACK / NACK transmission process is illustrated.

[0026] Figure 5 A wireless communication system supporting an unlicensed frequency band is illustrated.

[0027] Figure 6 A method of occupying resources in an unlicensed band is illustrated.

[0028] Figure 7 and Figure 8 is a flow chart of CAP (Channel Access Procedure) for signal transmission via unlicensed band.

[0029] Fig. 9 RB interleaving is illustrated.

[0030] Fig.10 and Fig.11 It is a diagram related to the random access process.

[0031] Figures 12 to 17 is a diagram for describing a random access procedure according to an embodiment of the present disclosure.

[0032] Figures 18 to 21A device according to an embodiment of the present disclosure is illustrated. DETAILED DESCRIPTION

[0033] The following technologies can be used for various radio access systems such as CDMA, FDMA, TDMA, OFDMA, SC-FDMA, etc. CDMA can be implemented with radio technologies such as Universal Terrestrial Radio Access (UTRA) or CDMA2000. TDMA can be implemented with radio technologies such as Global System for Mobile Communications (GSM) / General Packet Radio Service (GPRS) / Enhanced Data Rates for GSM Evolution (EDGE). OFDMA can be implemented with radio technologies such as IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, Evolved UTRA (E-UTRA), etc. UTRA is part of Universal Mobile Telecommunications System (UMTS). 3GPP (3rd Generation Partnership Project) Long Term Evolution (LTE) is part of Evolved UMTS (E-UMTS) using E-UTRA, and LTE-A (Advanced) / LTE-A pro is an evolved version of 3GPP LTE. 3GPP NR (New Radio or New Radio Access Technology) is an evolved version of 3GPP LTE / LTE-A / LTE-A pro.

[0034] For the sake of clarity of description, the description is based on the 3GPP communication system (e.g., LTE, NR), but the technical spirit of the present disclosure is not limited to this. LTE refers to the technology after 3GPP TS 36.xxx version 8. Specifically, the LTE technology after 3GPP TS 36.xxx version 10 is called LTE-A, and the LTE technology after 3GPP TS 36.xxx version 13 is called LTE-Apro. 3GPP NR refers to the technology after TS 38.xxx version 15. LTE / NR can be referred to as a 3GPP system. "xxx" represents the specific number of the standard document. LTE / NR can be collectively referred to as a 3GPP system. For the background technology, terms, abbreviations, etc. used in the description of the present disclosure, reference can be made to the contents described in the standard documents disclosed before the present disclosure. For example, reference can be made to the following documents.

[0035] 3GPP NR

[0036] -38.211: Physical channels and modulation

[0037] -38.212: Multiplexing and channel coding

[0038] -38.213: Physical layer control procedures

[0039] -38.214: Physical layer data procedures

[0040] -38.300: NR and NG-RAN general description

[0041] -38.331: Radio Resource Control (RRC) protocol specification

[0042] Figure 1 The structure of a radio frame used in NR is illustrated.

[0043] The uplink (UL) transmission and downlink (DL) transmission in NR consist of frames. The length of the radio frame is 10ms and is defined as two 5ms half-frames (Half-Frame, HF). The half-frame is defined as five 1ms subframes (Subframe, SF). The subframe is divided into one or more time slots, and the number of time slots in the subframe depends on the subcarrier spacing (SCS). Depending on the cyclic prefix (CP), each time slot includes 12 or 14 OFDM (A) symbols. When using normal CP (CP), each time slot includes 14 symbols. When using extended CP (extended CP), each time slot includes 12 symbols. Here, the symbol may include OFDM symbols (or CP-OFDM symbols) and SC-FDMA symbols (or DFT-s-OFDM) symbols).

[0044] Table 1 illustrates 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 when a normal CP is used.

[0045] [Table 1]

[0046] SCS(15*2^u) <![CDATA[N slot symb ]]> <![CDATA[N frame,u slot ]]> <![CDATA[N frame,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

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

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

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

[0050] Table 2 illustrates that when the extended CP is used, the number of symbols per slot, the number of slots per frame, and the number of slots per subframe vary according to the SCS.

[0051] [Table 2]

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

[0053] In the NR system, OFDM (A) parameter sets (e.g., SCS, CP length, etc.) may be configured differently between multiple cells merged into one user equipment (UE). Therefore, the (absolute time) duration of time resources (e.g., SF, time slot, or TTI) (collectively referred to as TU (time unit) for convenience) consisting of the same number of symbols may be configured differently between the merged cells.

[0054] NR supports multiple OFDM (Orthogonal Frequency Division Multiplexing) parameter sets (e.g., subcarrier spacing, SCS) to support various 5G services. For example, when SCS is 15kHz, NR supports wide areas in conventional cellular bands, and when SCS is 30kHz / 60kHz, NR supports dense cities, lower latency, and wider carrier bandwidth.

[0055] The NR band is defined as two types of frequency ranges (FR) (FR1, FR2). FR1 / FR2 may be configured as shown in the following Table 3. In addition, FR2 may mean millimeter wave (mmW).

[0056] [Table 3]

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

[0058] Figure 2 The structure of a radio frame is illustrated.

[0059] A slot includes multiple symbols in the time domain. For example, in the case of normal CP, a slot may include 14 symbols, and in the case of extended CP, a slot may include 12 symbols. A carrier includes multiple subcarriers in the frequency domain. A resource block (RB) is defined as multiple (e.g., 12) consecutive subcarriers in the frequency domain. Multiple RB interleavings (referred to as interleavings) may be defined in the frequency domain. Interleaving m∈{0, 1, ..., M-1} may be composed of (common) RBs{m, M+m, 2M+m, 3M+m, ...}. M represents the number of interleavings. A BWP (bandwidth part) is defined as multiple consecutive RBs (e.g., physical RBs, PRBs) in the frequency domain and may correspond to an OFDM parameter set (e.g., SCS(u), CP length, etc.). A carrier may include up to N (e.g., 5) BWPs. Data communication is performed through an activated BWP, and only one BWP can be activated for one UE in one cell / carrier. Each element in a resource grid is called a resource element (RE) and may map one modulation symbol.

[0060] In a wireless communication system, a UE receives information from a base station through a downlink (DL), and the UE sends information to the base station through an uplink (UL). The information sent and received between the base station and the UE includes data and various control information, and there are various physical channels / signals according to the type / purpose of the information they send and receive. A physical channel corresponds to a set of resource elements (REs) that carry information from a higher layer. A physical signal corresponds to a set of resource elements (REs) that are used by a physical layer (PHY) but do not carry information from a higher layer. The higher layer includes a medium access control (MAC) layer, a radio link control (RLC) layer, a packet data convergence protocol (PDCP) layer, a radio resource control (RRC) layer, and the like.

[0061] DL physical channels include PBCH (Physical Broadcast Channel), physical PDSCH (Downlink Shared Channel) and PDCCH (Physical Downlink Control Channel). DL physical signals include DL RS (Reference Signal), PSS (Primary Synchronization Signal) and SSS (Secondary Synchronization Signal). DL reference signals (RS) include DM-RS (Demodulation Reference Signal), PT-RS (Phase Tracking Reference Signal) and CSI-RS (Channel State Information RS). UL physical channels include PRACH (Physical Random Access Channel), PUSCH (Physical Uplink Shared Channel) and PUCCH (Physical Uplink Control Channel). UL physical signals include UL RS. UL RS includes DM-RS, PT-RS and SRS (Sounding RS).

[0062] Figure 3 An example in which physical channels are mapped into time slots is illustrated.

[0063] DL control channel, DL data or UL data, UL control channel, etc. can all be included in a time slot. For example, the first N symbols in the time slot can be used to send a DL control channel (hereinafter referred to as the DL control region), and the last M symbols in the time slot can be used to send a UL control channel (hereinafter referred to as the UL control region). N and M are both integers greater than or equal to 0. The resource area (hereinafter referred to as the data area) between the DL control area and the UL control area can be used for DL ​​data transmission or for UL data transmission. There may be a time gap between the control area and the data area for DL ​​to UL switching or UL to DL switching. PDCCH can be sent in the DL control area, and PDSCH can be sent in the DL data area. Some symbols at the time of switching from DL to UL in the time slot can be used as time gaps.

[0064] In the present disclosure, a base station may be, for example, a gNodeB.

[0065] Downlink (DL) physical channel / signal

[0066] (1)PDSCH

[0067] PDSCH carries DL shared transport blocks (DL-SCHTB). TB is encoded as a codeword (CW) and then sent through a scrambling and modulation process. CW includes one or more code blocks (CB). One or more CBs are grouped into a CBG (CB group). Depending on the configuration of the cell, the PDSCH bearer can carry up to two CWs. Scrambling and modulation are performed for each CW, and the modulation symbols generated from each CW are mapped to one or more layers. Each layer is mapped to resources together with DMRS through precoding and sent through the corresponding antenna port. PDSCH can be dynamically scheduled by PDCCH, or semi-statically scheduled (configured scheduling, CS) based on high-level (e.g., RRC) signaling (and / or layer 1 (L1) signaling (e.g., PDCCH)). Therefore, in dynamic scheduling, PDSCH transmission is accompanied by PDCCH, but in CS, PDSCH transmission is not accompanied by PDCCH. CS includes semi-persistent scheduling (SPS).

[0068] (2)PDCCH

[0069] PDCCH carries DCI (downlink control information). For example, PDCCH carries DL-SCH transmission format and resource allocation, frequency / time resource allocation information for UL-SCH (shared channel), paging information about PCH (paging channel), system information about DL-SCH, random access response sent on PDSCH, frequency / time resource allocation information for high-layer control messages such as (RAR), transmission power control commands, and activation / deactivation information about SPS / CS (configured scheduling). Various DCI formats are provided according to the information in DCI.

[0070] Table 4 illustrates a DCI format transmitted through the PDCCH.

[0071] [Table 4]

[0072]

[0073] 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 CBG (code block group)-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 (DL grant DCI) can be used to schedule TB-based (or TB-level) PDSCH or CBG-based (or CBG-level) PDSCH. 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 UL scheduling information. DCI format 2_0 can be used to convey dynamic slot format information (e.g., dynamic SFI) to the UE, and DCI format 2_1 can be used to convey downlink preemption information to the UE. DCI format 2_0 and / or DCI format 2_1 may be delivered to UEs in a corresponding group through a group common PDCCH (Group common PDCCH), which is a PDCCH delivered to UEs defined as a group.

[0074] The PDCCH / DCI includes a cyclic redundancy check (CRC), and the CRC is masked / scrambled using various identifiers (e.g., a radio network temporary identifier, RNTI) depending on the owner or purpose of the PDCCH. For example, if the PDCCH is for a specific UE, the CRC is masked using the C-RNTI (Cell-RNTI). If the PDCCH involves paging, the CRC is masked using the paging-RNTI (P-RNTI). If the PDCCH involves system information (e.g., system information block, SIB), the CRC is masked using the system information RNTI (SI-RNTI). If the PDCCH involves a random access response, the CRC is masked using the random access-RNTI (RA-RNTI).

[0075] Table 5 illustrates the usage of PDCCH and transport channels according to RNTI. The transport channel indicates a transport channel related to data carried by PDSCH / PUSCH scheduled by PDCCH.

[0076] [Table 5]

[0077]

[0078] The modulation scheme of PDCCH is fixed (e.g., Quadrature Phase Shift Keying, QPSK), and one PDCCH consists of 1, 2, 4, 8, 16 CCEs (Control Channel Elements) according to the aggregation level (AL). One CCE consists of six REGs (Resource Element Groups). One REG is defined as one OFDMA symbol and one (P)RB.

[0079] The PDCCH is sent through a CORESET (Control Resource Set). A CORESET corresponds to a set of physical resources / parameters used to carry PDCCH / DCI within a BWP. For example, a CORESET contains a set of REGs with a given parameter set (e.g., SCS, CP length, etc.). The CORESET can be configured through system information (e.g., MIB) or UE-specific high-level (e.g., RRC) signaling. Examples of parameters / information for configuring a CORESET are as follows. One or more CORESETs are configured for a UE, and multiple CORESETs may overlap in the time / frequency domain.

[0080] -controlResourceSetId: It indicates the identification (ID) information of CORESET

[0081] -frequencyDomainResources: It indicates the frequency domain resources of CORESET. It is indicated by a bitmap, and each bit corresponds to an RB group (= 6 consecutive RBs). For example, the most significant bit (MSB) of the bitmap corresponds to the first RB group in the BWP. The RB group corresponding to the bit with a bit value of 1 is allocated as the frequency domain resource of CORESET.

[0082] -Duration: It indicates the time domain resource of CORESET. It indicates the number of consecutive OFDMA symbols constituting CORESET. For example, the duration value is 1 to 3.

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

[0084] -precoderGranularity: It indicates the granularity of the precoder in the frequency domain

[0085] -tci-StatesPDCCH: It indicates information indicating a transmission configuration indication (TCI) for PDCCH (eg, TCI-StateID). TCI state is used to provide a quasi co-location (QCL) relationship (TCI-state) between a DLRS in an RS set and a PDCCH DMRS port.

[0086] -tci-PresentInDCI: This indicates whether the TCI field is included in the DCI.

[0087] -pdcch-DMRS-ScramblingID: This indicates information for initialization of a PDCCH DMRS scrambling sequence.

[0088] For PDCCH reception, the UE may monitor a set of PDCCH candidates in a CORESET (e.g., blind decoding). A PDCCH candidate represents a CCE monitored by the UE for PDCCH reception / detection. PDCCH monitoring may be performed in one or more CORESETs in an active DL BWP in each activated cell for which PDCCH monitoring is configured. A set of PDCCH candidates monitored by the UE is defined as a PDCCH search space (SS) set. An SS set may be a common search space (CSS) set or a UE-specific search space (USS) set.

[0089] Table 6 illustrates a PDCCH search space.

[0090] [Table 6]

[0091]

[0092] The SS set may be configured through system information (e.g., MIB) or UE-specific high-level (e.g., RRC) signaling. S (e.g., 10) 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 is associated with a CORESET, and each CORESET configuration may be associated with one or more SS sets.

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

[0094] -controlResourceSetId: This indicates the CORESET associated with the SS set.

[0095] - monitoringSlotPeriodicityAndOffset: It indicates the PDCCH monitoring periodicity interval (time slot unit) and the PDCCH monitoring interval offset (time slot unit).

[0096] -monitoringSymbolsWithinSlot: It indicates the first OFDMA symbol used for PDCCH monitoring within the slot where PDCCH monitoring is configured. It is indicated by a bitmap, and each bit corresponds to each OFDMA symbol in the slot. The MSB of the bitmap corresponds to the first OFDM symbol in the slot. The OFDM symbol corresponding to the bit with a bit value of 1 corresponds to the first symbol of the CORESET in the slot.

[0097] -nrofCandidates: It 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).

[0098] -searchSpaceType: It indicates whether the SS type is CSS or USS.

[0099] -DCI format: It indicates the DCI format of the PDCCH candidate

[0100] Based on the CORESET / SS set configuration, the UE can monitor PDCCH candidates in one or more SS sets in a time slot. The timing (e.g., time / frequency resources) of monitoring PDCCH candidates is defined as a PDCCH (monitoring) opportunity. One or more PDCCH (monitoring) opportunities can be configured within a time slot.

[0101] Uplink (UL) physical channels / signals

[0102] (1) PUSCH

[0103] The PUSCH carries uplink data (e.g., UL-SCH TB) and / or uplink control information (UCI), and is transmitted based on a CP-OFDM (Cyclic Prefix-Orthogonal Frequency Division Multiplexing) waveform or a DFT-s-transmit OFDM (Discrete Fourier Transform-Spread-Orthogonal Frequency Division Multiplexing) waveform. When the PUSCH is transmitted based on the DFT-s-OFDM waveform, the UE transmits the PUSCH by applying transform precoding. For example, when transform precoding is not possible (e.g., transform precoding is disabled), the UE transmits the PUSCH based on the CP-OFDM waveform, and when transform precoding is possible (e.g., transform precoding is enabled), the UE may transmit the PUSCH based on the CP-OFDM waveform or the DFT-s-OFDM waveform. The PUSCH may be dynamically scheduled by the PDCCH or semi-statically scheduled (configured scheduling, CS) based on higher layer (e.g., RRC) signaling (and / or layer 1 (L1) signaling (e.g., PDCCH)). Therefore, in dynamic scheduling, PUSCH transmission is accompanied by PDCCH, but in CS, PUSCH transmission is not accompanied by PDCCH. CS includes type 1CG (configured grant) PUSCH transmission and type 2CG PUSCH transmission. In type 1CG, all parameters for PUSCH transmission are signaled by higher layers. In type 2CG, some parameters for PUSCH transmission are signaled by higher layers, and the remaining parameters are signaled by PDCCH. Basically, in CS, PDCCH is not accompanied by PUSCH transmission.

[0104] (2) PUCCH

[0105] PUCCH carries uplink control information (UCI). UCI includes:

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

[0107] -HARQ-ACK (Hybrid Automatic Repeat and Request Acknowledgement): It is a reception response signal for a DL signal (e.g., PDSCH, SPS release PDCCH). The HARQ-ACK response may include a positive ACK (abbreviated as ACK), a negative ACK (NACK), DTX (discontinuous transmission), or NACK / DTX. HARQ-ACK may be mixed with A / N, ACK / NACK, HARQ-ACK / NACK, etc. HARQ-ACK may be generated in TB units / CBG units.

[0108] - CSI (Channel State Information): It is feedback information related to a DL channel. CSI includes CQI (Channel Quality Information), RI (Rank Indicator), PMI (Precoding Matrix Indicator), and PTI (Precoding Type Indicator).

[0109] Table 7 illustrates the PUCCH format. The PUCCH format can be classified according to the UCI payload size / transmission length (e.g., the number of symbols constituting the PUCCH resource) / transmission structure. The PUCCH format can be classified into short PUCCH (format 0, 2) and long PUCCH (format 1, 3, 4) according to the transmission length.

[0110] [Table 7]

[0111]

[0112] (0)PUCCH format 0 (PF0)

[0113] - Supported UCI payload size: up to K bits (e.g., K=2)

[0114] -The number of OFDM symbols constituting a single PUCCH: 1 to X symbols (e.g., X=2)

[0115] - Transmission structure: It consists of only the UCI signal without DM-RS, and the UCI status is transmitted by selecting and transmitting one of a plurality of sequences.

[0116] (1) PUCCH format 1 (PF1)

[0117] - Supported UCI payload size: up to K bits (e.g., K=2)

[0118] -The number of OFDM symbols constituting a single PUCCH: Y to Z symbols (e.g., Y = 4, Z = 14)

[0119] -Transmission structure: DM-RS and UCI consist of different OFDM symbols in TDM form, and UCI is in the form of a specific sequence multiplied by a modulation (e.g., QPSK) symbol. CDM is supported between multiple PUCCH resources (according to PUCCH format 1) by applying CS (cyclic shift) / OCC (orthogonal cover code) to both UCI and DM-RS (in the same RB).

[0120] (2) PUCCH format 2 (PF2)

[0121] - Supported UCI payload size: more than K bits (e.g., K=2)

[0122] -The number of OFDM symbols constituting a single PUCCH: 1 to X symbols (e.g., X=2)

[0123] - Transmission structure: DMRS and UCI are configured / mapped into the same symbol in an FDM form and transmitted by applying IFFT instead of DFT only to the coded UCI bits.

[0124] (3) PUCCH format 3 (PF3)

[0125] - Supported UCI payload size: more than K bits (e.g., K=2)

[0126] -The number of OFDM symbols constituting a single PUCCH: Y to Z symbols (e.g., Y = 4, Z = 14)

[0127] -Transmission structure: DMRS and UCI are configured / mapped on different symbols in TDM form, and DFT is applied to the coded UCI bits for transmission. OCC is applied to UCI at the front end of DFT and CS (or IFDM mapping) is applied to DMRS to support multiplexing of multiple UEs.

[0128] (4) PUCCH format 4 (PF4)

[0129] - Supported UCI payload size: more than K bits (e.g., K=2)

[0130] -The number of OFDM symbols constituting a single PUCCH: Y to Z symbols (e.g., Y = 4, Z = 14)

[0131] - Transmission structure: A structure in which DMRS and UCI are configured / mapped on different symbols in a TDM form, and DFT is applied to coded UCI bits to be transmitted without multiplexing between terminals.

[0132] Figure 4 The ACK / NACK transmission process is illustrated. Figure 4 , the UE may detect the PDCCH in slot #n. Here, the PDCCH includes downlink scheduling information (e.g., DCI format 1_0 or DCI format 1_1), and the PDCCH indicates DL assignment to PDSCH offset (K0) and PDSCH-HARQ-ACK report offset (K1). For example, DCI format 1_0 and DCI format 1_1 may include the following information.

[0133] - Frequency domain resource assignment: It indicates the RB set allocated to PDSCH.

[0134] - Time domain resource assignment: K0, which indicates the starting position (eg, OFDM symbol index) and length (eg, number of OFDM symbols) of the PDSCH in a slot.

[0135] -PDSCH to HARQ_Feedback Timing Indicator: It indicates K1.

[0136] Thereafter, after receiving the PDSCH in time slot #(n+K0) according to the scheduling information of time slot #n, the UE may send UCI through the PUCCH in time slot #(n+K1). Here, the UCI includes a HARQ-ACK response to the PDSCH. If the PDSCH is configured to send a maximum of 1 TB, the HARQ-ACK response may be configured with 1 bit. When the PDSCH is configured to send a maximum of two TBs, the HARQ-ACK response may be configured with two bits when spatial bundling is not configured, and with one bit when spatial bundling is configured. When the HARQ-ACK transmission time for multiple PDSCHs is designated as time slot #(n+K1), the UCI sent in time slot #(n+K1) includes HARQ-ACK responses for multiple PDSCHs.

[0137] 1. Support wireless communication systems in unlicensed frequency bands.

[0138] Figure 5 An example of a wireless communication system supporting an unlicensed band to which the present disclosure is applicable is illustrated.

[0139] 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 a (DL / UL) LCC (licensed component carrier). In addition, 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 a (DL / UL) UCC. The carrier / carrier frequency of a cell may refer to an operating frequency (e.g., center frequency) of the cell. A cell / carrier (e.g., CC) is generally referred to as a cell.

[0140] like Figure 5 As shown in (a), when the UE and the base station transmit and receive signals through the LCC and UCC of the carrier combination, the LCC can be configured as the PCC (primary CC) and the UCC can be configured as the SCC (secondary CC). Figure 5 As shown in (b), the UE and the base station can send and receive signals through one UCC or a UCC coupled with multiple carriers. That is, the UE and the base station can send and receive signals only through the UCC but not through the LCC. For independent operation, PRACH, PUCCH, PUSCH, SRS transmission, etc. can be supported in the U cell.

[0141] Hereinafter, the signal transmission / reception operation in the unlicensed band described in the present disclosure may be performed based on all of the above deployment scenarios (unless otherwise specified).

[0142] Unless otherwise stated, the following definitions may apply to the terms used in this specification.

[0143] - Channel: It consists of consecutive RBs and may refer to a carrier or a portion of a carrier, where a channel access procedure is performed in a shared spectrum.

[0144] - CAP (Channel Access Procedure): This is a process for evaluating channel availability based on sensing in order to determine whether a channel is used by other communication nodes before signal transmission. The basic unit for sensing is a duration of T sl =9us sensing time slot. When the base station or UE senses the channel during the sensing time slot period, and the power detected in at least 4us during the sensing time slot duration is less than the energy detection threshold X Thresh When the sensing time slot period T sl is considered to be an idle state. Otherwise, the sensing time slot period T sl = 9us is considered as a busy state. CAP can be called Listen Before Talk (LBT).

[0145] - Channel occupancy: After performing the channel access procedure, it means the corresponding transmission made by the base station / UE on the channel.

[0146] -COT (Channel Occupancy Time): After the base station / terminal performs the channel access procedure, it refers to the total time that any base station / UE sharing the channel occupancy with the base station / terminal can perform transmission on the channel. When determining the COT, if the transmission gap is 25us or less, the gap period is also counted in the COT. The COT can be shared for transmission between the base station and the corresponding terminal.

[0147] -DL transmission burst: It is defined as a group of transmissions from a base station with no gaps exceeding 16us. Transmissions from a base station separated by gaps greater than 16us are considered DL transmission bursts separated from each other. Within a DL transmission burst, a base station may perform transmissions after a gap without sensing channel availability.

[0148] -UL transmission burst: It is defined as a group of transmissions from a UE with no gaps exceeding 16us. Transmissions from a UE separated by gaps greater than 16us are considered UL transmission bursts separated from each other. Within a UL transmission burst, a UE may perform transmissions after a gap without sensing channel availability.

[0149] - Discovery Burst: It refers to a DL transmission burst including a set of signals and / or channels, which are bounded within a (time) window and associated with a duty cycle. In LTE-based systems, a discovery burst is a transmission initiated by a base station, including PSS, SSS and cell-specific RS (CRS), and may also include non-zero power CSI-RS. A discovery burst in an NR-based system is a transmission initiated by a base station, including at least SS / PBCH blocks, and may also include a CORESET for scheduling a PDSCH with SIB1, a PDSCH carrying SIB1 and / or a PDCCH with non-zero power CSI-RS.

[0150] Figure 6 The method of occupying resources in the unlicensed band is illustrated. According to the regional regulations on the unlicensed band, the communication node in the unlicensed band must determine whether other communication nodes use the channel before sending a signal. Specifically, the communication node can check whether other communication nodes send signals by first performing carrier sensing (CS) before signal transmission. The situation where other communication nodes are determined not to send signals is defined as CCA (clear channel assessment) has been confirmed. If there is a CCA threshold configured by predefined or high-level (e.g., RRC) signaling, if an energy changed by a CCA threshold is detected on the channel, the communication node determines the channel state as busy, otherwise, the channel state can be considered to be idle. For reference, in the Wi-Fi standard (802.11ac), the CCA threshold is defined as -62dBm for non-WiFi signals and -82dBm for Wi-Fi signals. If the channel state is determined to be idle, the communication node can start sending signals in the U cell. The above series of processes can be referred to as LBT (listen before talking) or CAP (channel access process). LBT, CAP and CCA can be expressed interchangeably.

[0151] Specifically, for downlink reception / uplink transmission in an unlicensed band, one or more of the CAP methods described below may be used in a wireless communication system associated with the present disclosure.

[0152] Downlink signal transmission method through unlicensed frequency band

[0153] The base station may perform one of the following unlicensed band access procedures (eg, channel access procedure, CAP) for downlink signal transmission in the unlicensed band.

[0154] (1) Type 1 Downlink CAP Method

[0155] In a Type 1 DL CAP, the length of the duration spanned by a sensing slot sensed as idle before a transmission is random. The Type 1 DL CAP may be applied to the following transmissions.

[0156] - a transmission initiated by a base station, comprising (i) a unicast PDSCH with user plane data, or (ii) a unicast PDSCH with user plane data and a unicast PDCCH scheduling user plane data, or

[0157] - A transmission initiated by the base station, either (i) a discovery burst only or (ii) a discovery burst multiplexed with non-unicast information.

[0158] Figure 7 is a flow chart of a CAP operation for downlink signal transmission in an unlicensed band through a base station.

[0159] Reference Figure 7 , the base station may first sense whether the channel is in an idle state during the sensing time slot period of the delay duration Td, and then may perform transmission when the counter N becomes 0 (S1234). At this time, the counter N is adjusted by sensing the channel during the additional sensing time slot period according to the following process:

[0160] Step 1) (S1220) Set N=N init Here, N init is evenly distributed from 0 to CW p Then, go to step 4.

[0161] Step 2) (S1240) If N>0 and the base station chooses to decrement the counter, set N=N-1.

[0162] Step 3) (S1250) The channel is sensed during the additional sensing time slot period. At this time, if the additional sensing time slot period is idle (Yes), the process moves to step 4. If not (No), it goes to step 5.

[0163] Step 4) (S1230) If N=0 (Yes), then end the CAP procedure (S1232). Otherwise (No), go to step 2.

[0164] Step 5) (S1260) The channel is sensed until a busy sensing slot is detected within the additional delay duration Td or all sensing slots within the additional delay duration Td are detected as idle.

[0165] Step 6) (S1270) If the channel is sensed as idle during all sensing time slot periods of the additional delay duration Td, proceed to Step 4. If not (No), proceed to Step 5.

[0166] Table 8 shows the m applied to CAP p, minimum contention window (CW), maximum CW, maximum channel occupancy time (MCOT), and allowed CW size vary according to the channel access priority category.

[0167] [Table 8]

[0168]

[0169] The delay duration Td is configured in the following order: Duration T f (16us)+m p Continuous sensing time slot period T sl (9us).T f The sensing time slot period T is included at the start time of the 16us period. sl .

[0170] CW min,p <=CW p <=CW max,p .CW p Can be configured as CW p =CW min,p And before step 1, the CW size is updated based on the HARQ-ACK feedback (e.g., ACK or NACK ratio) for the previous DL burst (e.g., PDSCH). p Can be initialized to CW based on HARQ-ACK feedback for previous DL burst min,p , can be increased to the next highest allowed value or maintained at the existing value.

[0171] (2) Type 2 Downlink (DL) CAP Method

[0172] In a Type 2 DL CAP, the length of the duration spanned by a sensing slot sensed as idle before transmission is deterministic. Type 2 DL CAPs are classified as Type 2A / 2B / 2C DL CAPs.

[0173] Type 2A DL CAP may be applied to the following transmissions. In Type 2A DL CAP, the base station may transmit the following transmissions at least during the sensing period T short_dl = 25us, the transmission is sent immediately after the channel is sensed as idle. Here, T short_dl Time period T f (=16us) and a sensing time slot period immediately following it. f A sensing time slot is included at the beginning of the duration.

[0174] - BS initiated transmissions, (i) discovery bursts only or (ii) discovery bursts multiplexed with non-unicast information, or;

[0175] - The base station's transmission after a gap of 25us from the UE's transmission within the shared channel occupancy.

[0176] Type 2B DL ​​CAP may be applicable to transmissions performed by the base station after a 16us gap from the UE's transmission during the shared channel occupancy time. In Type 2B DL ​​CAP, the base station may sense that the channel is idle for T f =16us later, the transmission is sent immediately. f The sensing slot is included in the last 9us of the duration. Type 2C DL CAP may be applicable to transmissions performed by the base station after a maximum of 16us from the UE's transmission within the shared channel occupancy time. In Type 2C DL CAP, the base station does not sense the channel before performing a transmission.

[0177] Uplink signal transmission method through unlicensed frequency band

[0178] The UE performs type 1 or type 2 CAP for uplink signal transmission in the unlicensed band. Generally, the UE can perform the CAP (e.g., type 1 or type 2) configured by the base station for uplink signal transmission. For example, the UE can include CAP type indication information in the UL grant (e.g., DCI format 0_0, DCI format 0_1) for scheduling PUSCH transmission.

[0179] (1) Type 1 Uplink (UL) CAP method

[0180] In Type 1 UL CAP, the length of the duration spanned by the sensing slots sensed as idle before transmission is random. Type 1 UL CAP may be applied to the following transmissions.

[0181] -PUSCH / SRS transmission configured and / or scheduled by the base station.

[0182] - PUCCH transmission configured and / or scheduled from the base station.

[0183] - Transmission-related Random Access Procedure (RAR)

[0184] Figure 8 is a flow chart of a Type 1 CAP operation of a UE for uplink signal transmission.

[0185] Reference Figure 8 , the UE may first sense whether the channel is in an idle state during the sensing time slot period of the delay duration Td, and then may perform transmission when the counter N becomes 0 (S1534). At this time, the counter N is adjusted by sensing the channel during the additional sensing time slot period according to the following process:

[0186] Step 1) (S1520) Set N = N init Here, N init is evenly distributed from 0 to CW p Then, go to step 4.

[0187] Step 2) (S1540) If N>0 and the UE chooses to decrement the counter, set N=N-1.

[0188] Step 3) (S1550) The channel is sensed during the additional sensing time slot period. At this time, if the additional sensing time slot period is idle (Yes), the process moves to Step 4. If not (No), it goes to Step 5.

[0189] Step 4) (S1530) If N=0 (Yes), terminate the CAP program (S1532). Otherwise (No), go to step 2.

[0190] Step 5) (S1560) The channel is sensed until a busy sensing slot is detected in the additional delay duration Td or all sensing slots in the additional delay duration Td are detected as idle.

[0191] Step 6) (S1570) If the channel is sensed as idle during all sensing time slot periods of the additional delay duration Td (Yes), move to Step 4. If not (No), enter Step 5.

[0192] Table 9 shows the m applied to CAP p , minimum contention window (CW), maximum CW, maximum channel occupancy time (MCOT), and allowed CW size vary according to the channel access priority category.

[0193] [Table 9]

[0194]

[0195] The delay duration Td is configured in the following order: Duration T f (16us)+m p Continuous sensing time slot period T sl (9us).T f The sensing time slot period T is included at the start time of the 16us period. sl .

[0196] CW min,p <=CW p <=CW max,p .CW p Can be configured as CW p =CW min,p, and is updated (CW size update) based on explicit / implicit reception response to the 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 burst min,p , can be increased to the next highest allowed value or can be maintained at the existing value.

[0197] (2) Type 2 Uplink (UL) CAP method

[0198] In a Type 2 UL CAP, the length of the duration spanned by the sensing slot that is sensed as idle before transmission is deterministic. Type 2 UL CAP is classified as Type 2A / 2B / 2C UL CAP. In a Type 2A UL CAP, the UE may transmit a signal when the channel is sensed as idle for at least the sensing period T. short_dl =25us before sending the transmission immediately. Here, T short_dl By section T f (=16us) and a sensing time slot period immediately following it. 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 sense the channel as idle for a sensing period T short_dl =16us after which the transmission is sent immediately. In Type 2B UL CAP, T f Includes a sensing slot in the last 9us of duration. In Type 2C DL CAP, the UE does not sense the channel before performing a transmission.

[0199] RB interweaving

[0200] Fig. 9 RB interleaving is illustrated. In a shared spectrum, considering the provisions on OCB (occupied channel bandwidth) and PSD (power spectral density), a set of (single) non-contiguous RBs in frequency (at regular intervals) (or a single RB) can be defined as a resource unit used / allocated as a UL (physical) channel / signal transmission. For convenience, such a non-contiguous RB set is defined as RB interleaving (abbreviated as interleaving).

[0201] Reference Fig. 9, multiple RB interlaces (referred to as interlaces) may be defined within a frequency band. Here, a frequency band may include a (broadband) cell / CC / BWP / RB set, and an RB may include a PRB. For example, interlace #m∈{0, 1, ..., M-1} may be composed of (common) RBs{m, M+m, 2M+m, 3M+m, ...}. M represents the number of interlaces. A transmitter (e.g., a UE) may use one or more interlaces to send a signal / channel. The signal / channel may include a PUCCH or a PUSCH.

[0202] 2. Random Access (RA) Process

[0203] Fig.10 The random access procedure is shown. Fig.10 (a) shows a contention-based random access procedure, and Fig.10 (b) illustrates a dedicated random access procedure.

[0204] Reference Fig.10 (a), the contention-based random access procedure includes the following steps. Hereinafter, the messages sent in steps 1 to 4 may be referred to as messages (Msg) 1 to 4, respectively.

[0205] -Step 1: UE sends RACH preamble via RPACH.

[0206] - Step 2: The UE receives a Random Access Response (RAR) from the base station through the DL-SCH.

[0207] -Step 3: The UE sends a layer 2 / layer 3 message to the base station via UL-SCH.

[0208] - Step 4: The UE receives a contention resolution message from the base station via the DL-SCH.

[0209] The UE may receive information about random access from the base station through system information.

[0210] If random access is required, the UE sends a RACH preamble to the base station as in step 1. The base station can distinguish each random access preamble by time / frequency resources (RACH opportunity; RO) and a random access preamble index (PI) where the random access preamble is sent.

[0211] When the base station receives a random access preamble from the UE, as in step 2, the base station sends a random access response (RAR) message to the UE. In order to receive the random access message, the UE monitors the L1 / L2 control channel (PDCCH) with a CRC masked by RA-RNTI (Random Access-RNTI) within a preconfigured time window (e.g., ra-ResponseWindow), which includes scheduling information about the random access response message. The PDCCH masked with RA-RNTI can be sent only through the common search space. When receiving a scheduling signal masked by RA-RNTI, the UE can receive a random access response message from the PDSCH indicated by the scheduling information. Thereafter, the UE checks whether there is random access response information indicated to it in the random access response message. Whether the random access response information indicated to itself exists can be checked by whether the random access preamble ID (RAPID) of the preamble sent by the UE exists. The index and RAPID of the preamble sent by the UE can be the same. The random access response information includes the corresponding random access preamble code index, timing offset information for UL synchronization (e.g., timing advance command, TAC), UL scheduling information for message 3 transmission (e.g., UL grant) and terminal temporary identification information (e.g., temporary-C-RNTI, TC-RNTI).

[0212] As in step 3, the UE receiving the random access response information sends UL-SCH (shared channel) data (message 3) through the PUSCH according to the UL scheduling information and the timing offset value. Message 3 may include the ID of the UE (or the global ID of the UE). Alternatively, message 3 may include information related to the RRC connection request for initial access (e.g., RRCSetupRequest message). In addition, message 3 may include a buffer status report (BSR) about the amount of data available for transmission by the UE.

[0213] After receiving the UL-SCH data, as in step 4, the base station sends a contention resolution message (message 4) to the UE. When the UE receives the contention resolution message and the contention is successfully resolved, the TC-RNTI is changed to the C-RNTI. Message 4 may include the UE's ID and / or RRC connection related information (e.g., RRCSetup message). If the information sent through message 3 and the information received through message 4 do not match, or if message 4 is not received within a certain period of time, the UE may resend message 3 when contention resolution fails.

[0214] Reference Fig.10(b), the dedicated random access procedure includes the following 3 steps. Hereinafter, the messages sent in steps 0 to 2 may be referred to as messages (Msg) 0 to 2, respectively. The dedicated random access procedure may be triggered using a PDCCH (hereinafter referred to as a PDCCH command) for instructing a base station to send a RACH preamble.

[0215] - Step 0: The base station allocates a RACH preamble to the UE through dedicated signaling.

[0216] -Step 1: UE sends RACH preamble via PRACH.

[0217] - Step 2: The UE receives a Random Access Response (RAR) from the base station through the DL-SCH.

[0218] The operations of steps 1 and 2 of the dedicated random access procedure may be the same as steps 1 and 2 of the contention-based random access procedure.

[0219] In NR, DCI format 1_0 is used to initiate a non-contention-based random access procedure using a PDCCH order. DCI format 1_0 is used to schedule PDSCH in one DL cell. On the other hand, when the CRC (cyclic redundancy check) of DCI format 1_0 is scrambled with C-RNTI and all bit values ​​of the "frequency domain resource allocation" field are 1, DCI format 1_0 is used as a PDCCH order indicating a random access procedure. In this case, the fields of DCI format 1_0 are configured as follows.

[0220] -RA preamble index: 6 bits

[0221] -UL / SUL (Supplementary UL) indicator: 1 bit. When the bit values ​​of the RA preamble index are all non-zero and SUL is configured in the cell for the UE, the UL / SUL indicator indicates the UL carrier on which the PRACH is transmitted in the cell. Otherwise, the UL / SUL indicator is retained.

[0222] -SSB (Synchronization Signal / Physical Broadcast Channel) Index: 6 bits. When all bits of the RA preamble index are non-zero, the SSB index indicates the SSB used to determine the RACH opportunity for PRACH transmission. Otherwise, the SSB index is reserved.

[0223] -PRACH mask index: 4 bits. When all bits of the RA preamble index are non-zero, the PRACH mask index indicates the RACH opportunity associated with the SSB indicated by the SSB index. Otherwise, the PRACH mask index is reserved.

[0224] - Reserved: 10 bits.

[0225] When DCI format 1_0 does not correspond to a PDCCH command, DCI format 1_0 consists of fields for scheduling PDSCH (eg, time domain resource allocation, modulation and coding scheme (MCS), HARQ process number, PDSCH to HARQ_feedback timing indicator, etc.).

[0226] 2-step random access process

[0227] As described above, conventional random access is performed through a four-step process. In a conventional LTE system, as shown in Table 10, the four-step random access process takes an average of 15.5 ms.

[0228] [Table 10]

[0229]

[0230] In the NR system, lower latency may be required than in the existing system. In addition, if the random access process occurs in the U-band, the random access process is terminated and the contention is resolved only when both the UE and the base station successfully perform LBT sequentially in the 4-step random access process. If LBT fails even in one step of the 4-step random access process, resource efficiency is reduced and latency is increased. Specifically, if LBT fails in the scheduling / transmission process associated with message 2 or message 3, a significant reduction in resource efficiency and an increase in latency may occur. In various scenarios of the NR system, even the random access process in the L-band may require a low-latency random access process. Therefore, a 2-step random access process can also be performed on the L-band.

[0231] like Fig.11 As shown in (a), the 2-step random access process may include two steps of uplink signal transmission from the UE to the base station (referred to as message A) and downlink signal transmission from the base station to the UE (referred to as message B).

[0232] The following description focuses on the initial access procedure, but the method proposed below can be equally applied to the random access procedure after the RRC connection is established between the UE and the base station. Fig.11 As shown in (b), in the non-contention random access process, the random access preamble code and the PUSCH part can be sent together.

[0233] Although not shown, a PDCCH for scheduling message B that can be transmitted from the base station to the terminal may be referred to as Msg.B PDCCH.

[0234] 3. Random access procedure in unlicensed bands

[0235] The above contents (3GPP system (or NR system), frame structure, etc.) can be applied in combination with the method proposed in the present disclosure described later, or can supplement and clearly describe the technical features of the method proposed in the present disclosure.

[0236] As described above, in the Wi-Fi standard (802.11ac), the CCA threshold is defined as -62dBm for non-Wi-Fi signals and -82dBm for Wi-Fi signals. In other words, when a signal from a device that does not belong to the Wi-Fi system is received at a power of -62dBm or higher in a specific frequency band, the STA (station) or AP (access point) of the Wi-Fi system does not transmit a signal in the specific frequency band.

[0237] The PRACH (Physical Random Access Channel) format includes a long RACH format and a short RACH format. The PRACH corresponding to the long RACH format consists of a sequence of length 839. The PRACH corresponding to the short RACH format consists of a sequence of length 139. In the following, the structure of the sequence consisting of the short RACH format is proposed. In the FR1 (Frequency Range 1) band less than 6 GHz, the SCS pair of the short RACH format corresponds to 15 KHz and / or 30 KHz. Fig.12 As shown in FIG. 1 , a PRACH corresponding to a short RACH format may be transmitted through 12 RBs. The 12 RBs include 144 REs, and the PRACH may be transmitted on 139 tones (139 REs) of the 144 REs. Fig.12 In the example, the two REs in the lowest index order and the three REs in the highest index order among the 144 REs correspond to the null tone, but the position of the null tone can be different from Fig.12 The positions shown in are different.

[0238] In the present disclosure, the short RACH format may be referred to as a short PRACH format, and the long RACH format may be referred to as a long PRACH format. The PRACH format may be referred to as a preamble format.

[0239] The short PRACH format may consist of the values ​​defined in Table 11.

[0240] [Table 11]

[0241]

[0242] In Table 11, L RA is the length of the sequence, Δf RAis the SCS applied to RACH, and k is Ts / Tc = 64. When μ∈{0,1,2,3}, μ is determined to be one of 0, 1, 2, and 3 according to the SCS value. For example, for 15kHz SCS, μ is set to 0, and for 30kHz SCS, μ is set to 1.

[0243] The base station can notify which PRACH format can be sent at a specific timing in a specific time period (duration) through high-layer signaling, and how many ROs there are in the corresponding time slot. Tables 6.3.3.2-2 to 6.3.3.2-4 of the 38.211 standard correspond to this. Table 12 only shows some specific excerpts of the indexes of A1, A2, A3, B1, B2, and B3 used alone or in combination in Table 6.3.3.2-3 of the 38.211 standard.

[0244] [Table 12]

[0245]

[0246] like Fig.12 As shown, it can be known how many ROs are defined in the RACH slot for each preamble format (the time domain PRACH opportunity within the PRACH slot in Table 12) and how many OFDM (Orthogonal Frequency Division Multiplexing) symbols are occupied by the PRACH preamble of each preamble format (the PRACH duration in Table 12). In addition, since the start symbol of the first RO can be indicated for each preamble format, information about which point in the corresponding RACH slot the RO starts from can be sent / received between the base station and the UE. Fig.13 Table 12 shows the configuration of RO in the RACH slot for each PRACH configuration index value.

[0247] On the other hand, the device operating in the unlicensed band checks whether the channel on which the signal is transmitted is in an idle state or a busy state. When the channel is in an idle state, the signal is transmitted through the corresponding channel. When the channel is in a busy state, the device transmitting the signal waits until the channel becomes idle before transmitting the signal. Figure 6 and Figure 7 As described, such operation may be referred to as LBT or channel access scheme. In addition, there may be LBT categories as shown in Table 13.

[0248] [Table 13]

[0249]

[0250] LBT corresponding to category 1 is a method of accessing a channel without LBT. According to LBT corresponding to category 1, after a specific node occupies a channel, if the time interval until the next transmission is less than 16us, the specific node can access the channel regardless of the state. Next, category 2 LBT is a method of accessing a channel after performing a single-shot LBT without a backoff counter value. According to LBT corresponding to category 2, a specific node transmits after determining whether the channel is idle for 16us (or 25us).

[0251] For LBT corresponding to category 3 and category 4, a backoff counter value is randomly selected within the contention window (CW). In the present disclosure, the LBT corresponding to category 3 may be referred to as Cat 3LBT, and the LBT corresponding to category 4 may be referred to as Cat 4LBT. For the LBT corresponding to category 3, a backoff counter value is randomly selected based on a contention window size value that is always fixed. For the LBT corresponding to category 4, whenever the LBT fails, the contention window size value is increased by 1 step in the allowed candidates starting from the first minimum contention window size value. The maximum value, minimum value, and allowed contention window size value candidates of the contention window size are predefined for each channel access priority category (see Tables 3 and 4). For example, for Cat 4LBT with a channel access priority category of 4, the UE initially randomly selects a backoff counter value from 0 to 15. If the UE fails to complete the LBT, the UE randomly selects a backoff counter value from 0 to 31.

[0252] The LBT corresponding to Category 1 may include Type 2C DL CAP and Type 2C UL CAP as described above. The LBT corresponding to Category 2 may include Type 2A DL CAP, Type 2B DL ​​CAP, and Type 2B UL CAP. The LBT corresponding to Category 4 may include Type 1 DL CAP and Type 1 UL CAP.

[0253] If the channel is idle for 16+9×m p +K×9us, the UE selects the backoff counter value based on the value defined in Table 9 and performs the uplink transmission indicated and / or configured by the base station. K is the selected backoff counter value, and m p Corresponding to the time slot applied according to the channel access priority category. The channel access priority category and LBT category for PRACH transmission can be shown in Table 14.

[0254] [Table 14]

[0255]

[0256] Based on the values ​​that can be derived from Table 13 and Table 14, the UE can start PRACH transmission if the channel is idle for 16+9*2+K*9=34+K*9(us). As described above, the backoff counter value K is randomly selected within the contention window size value of varying size.

[0257] The above-mentioned 2-step random access process consists of the transmission of message A (Msg.A; PRACH preamble and Msg.3PUSCH) by the UE and the transmission of message B (Msg.B; RAR and Msg.4PDSCH) by the base station. For the convenience of description, in the present disclosure, the time and frequency resources to which the PRACH preamble signal of Msg.A is mapped / sent are defined as RO (RACH opportunity), and the time and frequency resources to which the Msg.3PUSCH signal is mapped / sent are defined as PO (PUSCH opportunity). In the following, a specific method for configuring Msg.A is proposed. The RACH preamble constituting Msg.A may be referred to as Msg.A RACH preamble and Msg.A PRACH. Msg.3PUSCH constituting Msg.A may be referred to as Msg.A PUSCH. RAR constituting Msg.B may be referred to as Msg.B. The Msg.4 PDSCH constituting Msg.B may be referred to as Msg.B PDSCH.

[0258] Specifically, in NR-U, it is necessary to define the channel access procedure (channel access procedure) for UE to send Msg.A in RO and PO. Therefore, the present disclosure proposes a channel access procedure based on the time / frequency resources of RO and PO and the timing gap between RO and PO. For ease of description, as Fig.14 The parameters defining the time / frequency resources of RO and PO and the time interval between RO and PO are shown in FIG. Fig.14 , T1 represents the duration of RO, T2 represents the duration of PO, T represents T1+T2, F1 represents the frequency bandwidth of RO, F2 represents the frequency band of PO, and P1 represents the time interval between RO and PO.

[0259] Hereinafter, an operation of a UE for performing channel access using channel occupancy sharing proposed in the present disclosure will be described.

[0260] (1) First, the UE receives control information related to RO and / or PO from the base station. Here, the control information may include Fig.14 Parameters shown. (2) Next, the UE determines the type of LBT to be performed before RO and / or PO based on the control information. (3) Next, the UE sends Msg.A preamble and / or Msg.A PUSCH in RO and / or PO based on the determined LBT type.

[0261] For more detailed information, reference will be made to the methods described later. That is, the methods described later can be combined with the processes of (1) to (3) above to achieve the objectives / effects proposed in the present disclosure. In addition, the methods described later can be combined with the processes described in the two-step random access procedure to achieve the objectives / effects proposed in the present disclosure. In the present disclosure, the 'license-free band' can be replaced by the'shared spectrum' and mixed with the'shared spectrum'. In addition, in the present disclosure, the 'LBT type' can be replaced by the 'channel access type' and mixed with the 'channel access type'. 'LBT' can be replaced by 'channel access' and mixed with 'channel access'.

[0262] 3.1 Embodiment 1: Channel access procedure considering channel occupancy sharing.

[0263] As a first method, the UE performs channel access operations for the method of channel occupancy (CO) sharing for Msg.A preamble and Msg.A PUSCH transmission as follows. At this time, the reason for considering CO sharing is that if CO sharing is not performed, Cat-4 LBT (based on random backoff) must be performed before all transmissions. That is, through CO sharing, the LBT process other than the first LBT process can be Cat-1 LBT (no LBT) or Cat-2 LBT (single-shot LBT). Therefore, channel access can be performed faster and more easily. In Fig.14 the following parameters used in the description are shown.

[0264] Referring to Table 9, the CO sharing time (T ulmcotp ) is defined according to the priority class (PC). That is, if the PC is 1, the CO sharing time is 2 ms or less; if the PC is 2, the CO sharing time is 4 ms or less; and if the PC is 3 or 4, the CO sharing time is 6 ms or 10 ms or less (whether it is 6 ms or 10 ms is determined by higher-layer signaling). Therefore, the next operation can be divided into the following three durations according to the CO sharing time and PC.

[0265] Duration 1: 0 ms < T <= 2 ms, in this case, for CO sharing, the PC RO can be 1.

[0266] Duration 2: 2 ms < T <= 4 ms, in this case, for CO sharing, the PC RO can be 2.

[0267] Duration 3: 4 ms < T <= 6 ms (or 10 ms), in this case, for CO sharing, the PC RO can be 3 or 4.

[0268] For each duration defined above, the UE may perform the following operations.

[0269] 1-1. For each interval, the UE uses the priority class PC before the Msg A preamble (RACH) opportunity (RO) RO To perform Cat-4 LBT. After successful LBT, the UE sends the Msg A preamble,

[0270] 1-1-A. If P1<16(us), since CO sharing is possible, the UE performs Cat-1 LBT (ie, no LBT) before Msg.A PUSCH opportunity (PO).

[0271] 1-1-B. Otherwise, if P1 is 16(us),

[0272] If T2>X, the UE performs Cat-2 LBT (i.e., 16 (us) single-shot LBT) before PO because CO sharing is possible. X is the maximum timing duration allowed for UL signal / channel transmission without performing LBT operation. This can be indicated by the base station through high-layer signaling (e.g., SIB or RMSI (Remaining Minimum System Information) etc.). For example, X can be 0.5 ms.

[0273] If T2<=X, the UE performs Cat-1 LBT before PO (ie, no LBT) since CO sharing is possible.

[0274] 1-1-C. Otherwise, if P1 is 25(us), since CO sharing is possible, the UE performs Cat-2 LBT (ie, 25(us) single-shot LBT) before PO.

[0275] 1-1-D. Otherwise, if P1 is greater than 25(us),

[0276] If CO sharing is allowed, the UE performs Cat-2 LBT (i.e., 25(us) single-shot LBT) or Cat-4 LBT indicated by higher-layer signaling (e.g., SIB or RMSI, etc.). The priority class PC used by the UE performing Cat-4 LBT before PO PO (For example, PC PO Can be used with PC RO The same) can be agreed in advance, or can be indicated by the base station through high-layer signaling (for example, SIB or RMSI, etc.).

[0277] If CO sharing is not allowed, the UE performs Cat-4 LBT before PO. The priority class PC used by the UE performing Cat-4 LBT before PO PO(For example, PC PO may be the same as PC RO ), which can be agreed in advance, or can be indicated by the base station through high-layer signaling (e.g., SIB or RMSI).

[0278] Characteristically, the upper limit of the PI that can perform Cat-2 LBT can be configured. The base station can configure the upper limit of P1 that can perform Cat-2 LBT (or defined in the specification) for the UE through high-layer signaling (e.g., SIB or RMSI, etc.), and the UE can determine the LBT type and perform the channel access procedure by comparing the upper limit value of P1 with the current P1 value. For example, if the upper limit of P1 that can perform Cat-2 LBT is P1 MAX , then if P1 is less than P1 MAX , the UE can perform Cat-2 LBT before PO. If P1 is greater than P1 MAX , the UE can perform Cat-4 LBT before PO. In this case, the priority class PC PO (For example, PC PO may be the same as PC RO ), which can be agreed in advance, or can be indicated by the base station through high-layer signaling (e.g., SIB or RMSI, etc.).

[0279] The base station can also indicate whether CO sharing is allowed through high-layer signaling (e.g., SIB or RMSI, etc.).

[0280] 1-2. When F1 and F2 exist in the same LBT sub-band and / or when F1 includes F2, the operations of Embodiment 1 can be applied.

[0281] 3.2 Embodiment 2: Channel access procedure without considering channel occupancy sharing.

[0282] A proposal for the channel access operation of a method for the UE not to consider CO sharing for Msg.A preamble and Msg A.PUSCH transmission is as follows. The parameters used in the following description are shown in Fig.14 . Similarly in Embodiment 2, the following three durations described in Embodiment 1 can be applied.

[0283] Duration 1: 0ms < T <= 2ms, in this case, for CO sharing, PC RO can be 1.

[0284] Duration 2: 2ms < T <= 4ms, in this case, for CO sharing, PC RO can be 2.

[0285] Duration 3: 4 ms < T <= 6 ms (or 10 ms), in which case, for CO sharing, PC RO can be 3 or 4.

[0286] For each of the durations defined above, the UE can perform the following operations.

[0287] 2-1. For each duration, even if T is greater than the maximum value of each duration (because CO sharing is not considered), the UE uses the priority class PC RO before the Msg.A preamble RO to perform Cat-4 LBT. The maximum value of each duration can be, for example, 2 ms in duration 1, 4 ms in duration 2, and 6 ms (or 10 ms) in duration 3. When T is greater than 2 ms, PC RO can be 1; when T is greater than 4 ms, PC RO can be 1 or 2; and when T is greater than 6 ms (or 10 ms), PC RO can be 1, 2, 3, or 4. After a successful LBT, the UE sends the Msg.A preamble,

[0288] 2-1-A. (Because CO sharing is not considered), the UE performs Cat-4 LBT before PO. The priority class PC used by the UE that performs Cat-4 LBT before PO PO (e.g., PC PO can be the same as PC RO ) can be pre-agreed, or can be indicated by the base station through higher layer signaling (e.g., SIB or RMSI, etc.).

[0289] 2-2. Additionally, F1 and F2 do not exist in the same LBT sub-band, and / or F1 does not include F2, and the UE is configured to perform Cat-4 LBT before PO.

[0290] If the FBE (frame-based device) configuration or the LBT before RO is configured as Cat-2 LBT, the LBT before PO can also be configured as Cat 2-LBT or be configured to apply the same rules as RO.

[0291] 3.3 Embodiment 3: LBT type configuration for A / N feedback transmission of Msg.B

[0292] Next, when the UE receives a message (e.g., RRC connection establishment, etc.) indicating that the RACH procedure has been successful through the MAC CE of Msg.B, etc. from the base station, the UE needs to send A / N feedback (e.g., ACK) for it. Before the PUCCH resource for A / N feedback transmission, the UE needs to perform LBT, and the method for determining the corresponding LBT type can be as follows.

[0293] 3-1. Method for indicating all UEs receiving Msg.B through common LBT type

[0294] 3-1-A. Option 1) The base station schedules the PDCCH (eg, DCI field, etc.) of the PDSCH carrying Msg.B to indicate the LBT type shared by all UEs (or UE groups).

[0295] When configured in this manner, among the UEs receiving the corresponding Msg.B, the UE that needs to send A / N feedback can be indicated as having the same LBT type through the corresponding PDCCH (e.g., a specific DCI field), and can use the indicated LBT type (e.g., Cat-2 LBT) to perform the channel access process.

[0296] If the base station divides UEs into N (e.g., N=2) groups by a specification standard and indicates different LBT types to the N (e.g., N=2) groups for a specific reason (e.g., whether the base station successfully receives Msg B), the LBT type corresponding to each group is used. UEs belonging to a specific group can use the same LBT type to perform a channel access procedure.

[0297] Different LBT types may be indicated using an independent DCI field, etc. If the base station indicates the LBT type for one group through a specific DCI field, the LBT type of another group may be determined as the pre-agreed LBT type according to the indicated DCI field.

[0298] 3-1-B. Option 2) The base station indicates the LTB type common to all UEs (or UE groups) by adding a common field to the PDSCH carrying Msg.B (eg, the header part of the MAC CE).

[0299] If configured according to 3-1-B, among the UEs receiving Msg.B, the UEs for which A / N feedback needs to be sent can receive the same LBT type indication through the PDSCH of Msg.B (for example, the header part of the MAC CE), and can use the indicated LBT type (for example, Cat-2 LBT) to perform the channel access process.

[0300] If the base station divides UEs into N (e.g., N=2) groups by a specification standard and indicates different LBT types to the N (e.g., N=2) groups for a specific reason (e.g., whether the base station successfully receives Msg B), the LBT type corresponding to each group is used. UEs belonging to a specific group can use the same LBT type to perform a channel access procedure.

[0301] Different LBT types may be indicated using independent MAC CE header fields, etc. If the base station indicates the LBT type of one group through a specific MAC CE header field, the LBT type of another group may be determined as the pre-agreed LBT type according to the indicated MAC CE header field.

[0302] 3-1-C. Option 3) The base station indicates the LBT type common to all UEs (or UE groups) through high-layer signaling (eg, SIB or RMSI, etc.).

[0303] If configured according to 3-1-C, among the UEs receiving Msg.B, the UEs for which A / N feedback needs to be sent can receive the same LBT type indication through high-layer signaling (e.g., SIB or RMSI) and use the indicated LBT type (e.g., Cat-2 LBT) to perform the channel access process.

[0304] If the base station divides UEs into N (e.g., N=2) groups by a specification standard and indicates different LBT types to the N (e.g., N=2) groups for a specific reason, the LBT type corresponding to each group is used. UEs belonging to a specific group can use the same LBT type to perform a channel access procedure.

[0305] Different LBT types may be indicated by independent high-layer signaling, etc. If the base station indicates the LBT type of one group by high-layer signaling, the LBT type of another group may be determined as the pre-agreed LBT type according to the indicated high-layer signaling.

[0306] 3-1-D. When the base station indicates the LBT type in common, the resource overhead for indication can be reduced, and the advantage is that the A / N to be sent by the UE can be easily multiplexed. However, when A / N multiplexing is not performed, since UEs performing a common LBT type can perform channel access at the same time, the probability of collision between A / N transmissions increases.

[0307] 3-2. Method for receiving an indication of a UE-specific LBT type for each successful RAR of a UE receiving Msg.B

[0308] 3-2-A. Indicating the UE-specific LBT type for each successful RAR by adding a specific field (or using a reserved field) to the part indicating the value transmitted according to each preamble (and / or PUSCH) of the MAC CE included in the PDSCH carrying Msg B,

[0309] If configured in this way, among the UEs receiving Msg.B, the UE for which A / N feedback needs to be sent can receive an indication of a UE-specific LBT type for each successful RAR through MAC CE, and can perform channel access using the indicated LBT type. Therefore, the UE sends A / N feedback based on the indicated LBT type.

[0310] When the base station indicates a UE-specific LBT type for each successful RAR, the probability of collision between A / N transmissions is reduced because the time to perform channel access between UEs may vary. However, there is a disadvantage in that resource overhead for specifically indicating the UE occurs and it is difficult to perform A / N multiplexing.

[0311] 3-3. A method of indicating the LBT type to the UE receiving Msg.B in different ways according to whether the base station successfully receives Msg.B.

[0312] For example, the base station may indicate a common LBT type through a success RAR, and may indicate a RAPID-specific LBT type of the MAC-CE (in the RAR message) through a fallback RAR.

[0313] Here, each option of 3-1 in Implementation 3 may be applied as a method of indicating a common LBT type.

[0314] 3.4 Implementation 4: RA field configuration of 4-step Msg.2RAR or 2-step fallback RAR and LBT type indication method for Msg 3PUSCH transmission.

[0315] like Fig.15 As shown, Msg.2RAR of the traditional 4-step RACH process is defined.

[0316] In addition, 27 bits constituting the UL grant of Msg.2RAR are defined as shown in Table 15.

[0317] [Table 15]

[0318] RAR Permission Field Number of bits Frequency Hopping Flag 1 PUSCH frequency resource allocation 14 PUSCH time resource allocation 4 MCS 4 TPC commands for PUSCH 3 CSI Request 1

[0319] In addition, the CSI request field can be used or reserved depending on whether there is contention as follows. ("In a non-contention based random access procedure, the CSI request field in the RAR UL grant indicates whether the UE includes aperiodic CSI reporting in the corresponding PUSCH transmission according to [6, TS 38.214]. In a contention based random access procedure, the CSI request field is reserved.")

[0320] Since the LBT type of Msg.3PUSCH needs to be sent through RAR, the following method can be proposed.

[0321] Proposed method 4-1-1: a method of using the reserved 1 bit of RAR to indicate the LBT type.

[0322] When 1 bit is used to indicate the LBT type, 1 bit can indicate whether it is Cat-2 LBT or Cat-4 LBT.

[0323] Proposed method 4-1-2: Since the CSI request field of the RAR UL grant is reserved in the contention-based RACH procedure, a method of using 1 bit of the CSI request field to indicate the LBT type can be proposed.

[0324] When 1 bit of the CSI request field is used to indicate the LBT type, 1 bit of the CSI request field may indicate Cat-2 LBT or Cat-4 LBT.

[0325] However, in a non-contention based RACH procedure (eg, contention-free RACH), since the CSI request field is used, another proposed method may be used.

[0326] Proposed method 4-1-3: A method of indicating the LBT type using a field that is unnecessary in shared spectrum operation in the RAR UL license.

[0327] For example, when frequency resources for Msg 3 PUSCH transmission are allocated in an interleaving structure during NR-U operation, since there is no need to use the frequency hopping flag field, the LBT type can be indicated by using (reinterpreting) 1 bit of the frequency hopping flag field.

[0328] In the case of using 1 bit of the frequency hopping flag field to indicate the LBT type, 1 bit of the frequency hopping flag field may indicate Cat-2 LBT or Cat-4 LBT.

[0329] Even when the frequency resources for Msg.3 PUSCH transmission during shared spectrum operation are indicated by contiguous PRB allocation of a legacy system, the LBT type may be indicated by the frequency hopping flag field, but since frequency hopping is required in contiguous PRB allocation, the frequency hopping flag field may be used for its intended purpose.

[0330] Proposed method 4-1-4: a method of indicating an LBT type using L bits of the MSB (most significant bit) (or LSB; least significant bit) of a specific field.

[0331] For example, in the PUSCH frequency resource allocation field, the number of bits used varies according to the resource allocation type as shown in Table 16. Table 16 shows the number of bits of the frequency resource allocation field for PUSCH transmission based on a 20 MHz LBT sub-band.

[0332] [Table 16]

[0333]

[0334] Referring to Table 16, a PUSCH frequency resource allocation field from a maximum of 14 bits to a minimum of 5 bits can be used.

[0335] Here, the LBT type may be indicated using L bits of the MSB (or LSB) of the PUSCH frequency resource allocation field.

[0336] For example, when 1 bit of the MSB of the PUSCH frequency resource allocation field is used to indicate the LBT type, 1 bit of the MSB of the PUSCH frequency resource allocation field may indicate Cat-2 LBT or Cat-4 LBT.

[0337] As another example, when 2 bits of the MSB (or LSB) of the PUSCH frequency resource allocation field are used to indicate the LBT type, two types of priority categories (e.g., PC0 or PC1) and Cat-2 LBT or Cat-4 LBT can be indicated together.

[0338] As another example, when the 3 bits of the MSB (or LSB) of the PUSCH frequency resource allocation field are used to indicate the LBT type, four types of priority categories (e.g., one of PC0 to PC3) and Cat-2 LBT or Cat-4 LBT may be indicated together. Alternatively, Cat-1 LBT, Cat-2 LBT, Cat-4 LBT, and various priority categories may be combined and indicated.

[0339] Characteristically, assuming that the L bit values ​​for the MSB (or LSB) of the LBT type are 0, a UE interpreting the actual PUSCH frequency resource allocation field may be configured to understand the PUSCH frequency resource allocation.

[0340] Proposed method 4-1-5: A method of reducing the size of a specific field by L bits and making it a field indicating an LBT type by using the reduced L bits.

[0341] 4-1-5-A: During the RACH process in the shared spectrum, since Msg 3 PUSCH uses the legacy RA type 1 (Rel-15 RA type 1 in Table 15) or the new RA type (Rel-16 interleaving level allocation in Table 15), the PUSCH frequency resource allocation field can be configured as 13 bits. Of the 14 bits for the legacy PUSCH frequency resource allocation field, the remaining 1 bit can be configured as a field indicating the LBT type. As an example, when the 1-bit MSB in the 14-bit PUSCH frequency resource allocation field is used to indicate the LBT type, Cat-2 LBT or Cat-4 LBT can be indicated.

[0342] 4-1-5-B: In addition, the actual PUSCH frequency resource allocation field may be configured to be less than 13 bits (e.g., 12 bits, etc.). The remaining bits of the 14 bits of the conventional PUSCH frequency resource allocation field may be configured as a field indicating the LBT type. As an example, when the MSB (or LSB) of 2 bits in the 14-bit PUSCH frequency resource allocation field is used to indicate the LBT type, two types of priority categories (e.g., PC0 or PC1) and Cat-2 LBT or Cat-4 LBT may be indicated together. Assuming that the reduced MSB (or LSB) is 0, the UE may be configured to understand the PUSCH frequency resource allocation. For example, in the 14 bits of the conventional PUSCH frequency resource allocation field located in the RAR grant, the MSB of 2 bits is used as a field indicating the channel access type, and the LSB of 12 bits is used as a frequency resource allocation field as in the prior art, but assuming that there are two bits of zero before the 12 bits, the 12 bits of the LSB may be interpreted as a 14-bit field. As another example, when PUSCH frequency resource allocation is performed using 12 bits, the UE assumes that 1 bit MSB (or LSB) is 0 and can be configured to understand the PUSCH frequency resource allocation. Because RIV requires a maximum of 13 bits, only 13-12=1 bit MSB (or LSB) is considered as 0.

[0343] Proposed method 4-1-3 is additionally applied to proposed method 4-1-5, and as a combination of an LBT type field and a specific field (eg, an L-bit combination of the MSB (or LSB) of the PUSCH frequency resource allocation field), the LBT type may also be indicated.

[0344] Proposed method 4-1-6: A combination of the methods 4-1-1 to 4-1-5 may be considered.

[0345] That is, the LBT type can be indicated by a reserved 1 bit of the RAR, and / or 1 bit of the CSI request field of the RAR UL grant, and / or an unused field in the shared spectrum between RAR UL grants, and / or a combination of the MSB (or LSB) L bits of a specific field.

[0346] In addition, it can be considered that Msg.3 does not indicate the LBT type for PUSCH transmission. As an example, when the LBT type for Msg.3 PUSCH transmission is configured as LBE (load-based equipment) through SIB, the default value can be configured / defined as Cat-4 LBT. When the LBT type for Msg.3 PUSCH transmission is configured as FBE (frame-based equipment) through SIB, the default value can be configured / defined as Cat-2 LBT with 25us (or with 16us).

[0347] Characteristically, when the UE is configured as LBE through SIB in a 2-step RACH process, even if the default value of Msg.APUSCH (or Msg.3PUSCH) transmission is configured / defined as Cat-4 LBT, another category of LBT can be used according to the interval between RO-PO as in the embodiment of the present specification. Similarly, when the UE is configured as FBE through SIB, even if the default value of Msg.APUSCH (or Msg.3PUSCH) transmission is configured / defined as Cat-2 LBT with 25us, Cat-2 LBT with 16us or Cat-1 LBT can be used (according to the gap between RO-PO).

[0348] In addition, not only the LBT type but also the Msg.3 PUSCH start position can be additionally signaled through RAR. This is summarized as follows.

[0349] 4-2-1) When the legacy NR waveform is configured as the (Msg.3) PUSCH waveform from the base station,

[0350] Option 1: Apply fixed start position to fixed LBT type for Msg.3 PUSCH transmission

[0351] Option 2: Apply a fixed LBT type to Msg.3 PUSCH transmission, and indicate one of multiple starting positions as the RAR (or UL grant of the RAR).

[0352] Option 3: Apply a fixed starting position to Msg.3 PUSCH transmission, and indicate that one of the multiple LBT types is RAR (or UL grant of RAR).

[0353] 4-2-2) When the interleaved waveform is configured as the (Msg.3) PUSCH waveform from the base station,

[0354] Option 1: Indicate one of the combinations of multiple LBT types and multiple start positions through RAR (or UL grant of RAR).

[0355] Therefore, the LBT type indicated by the RAR grant in the previously proposed method (proposed methods 4-1-1 to 4-1-6, etc.) may mean the LBT type or the starting position or the combination of {LBT type, starting position} according to the methods of options 1 to 3 of 4-2-1. At this time, assuming that the starting symbol of the resource mapping the PUSCH signal is indicated by symbol #K, when the starting position is indicated by 1 bit, it may indicate one of {symbol #K, symbol #(KN)+25us}, or it may indicate one of {symbol #K, symbol #(KN)+25us+TA}. On the other hand, if the starting position is not indicated by the RAR grant and is determined as a single fixed value, the value may be defined as symbol #K.

[0356] As described above, by proposing method 4-1-5-B, when it is necessary to indicate the LBT type for Msg 3 transmission from the base station (for example, for operations for shared spectrum channel access), the size of the PUSCH frequency resource allocation field of the RAR can be reduced by 2 bits. The 2 bits not used as the PUSCH frequency resource allocation field can be used as a field for explicitly sending the LBT type. The field for sending the LBT type can be defined as the Channel Access-Cpext field. The fields of the RAR permission shown in Table 16 can be redefined as shown in Table 17.

[0357] [Table 17]

[0358]

[0359] On the other hand, when the size of the PUSCH resource allocation field (i.e., ) changes to 12 (i.e., when it is necessary to indicate the LBT type for Msg3 transmission from the base station), the contents of Table 18 below describing the truncation and padding of the traditional PUSCH frequency resource allocation field may be insufficient for the UE to interpret the Channel Access-Cpext field and the PUSCH frequency resource allocation field.

[0360] [Table 18]

[0361]

[0362] Thus, Table 18 can be modified as follows based on the proposal of the present disclosure.

[0363] 4-3-1. For operations without shared spectrum channel access, traditional system operations.

[0364] 4-3-1-A. If the number of PRBs in a BWP is 180 or less,

[0365] The UE truncates the FDRA (Frequency Domain Resource Allocation) field to its LSB And the truncated FDRA field is interpreted as the FDRA field of DCI format 0_0.

[0366] 4-3-1-B. If the number of PRBs in the BWP is greater than 180,

[0367] The UE performs the same operation as the MSB before the FDRA field. The same number of 0s is filled in, and the extended FERA field is interpreted as the FDRA field of DCI format 0_0. At this time, if the frequency hopping flag is 0, N UL，hop is 0, and if the frequency hopping flag is 1, then N UL，hop Follow Table 19.

[0368] [Table 19]

[0369]

[0370] 4-3-1-B. End

[0371] 4-3-2. Shared spectrum channel access operation

[0372] 4-3-2-A. When the higher layer parameter useInterlacePUSCH-Common is not provided (If useInterlacePUSCH-Common is not provided), that is, when continuous mapping of uplink resource allocation type 1 (Uplink resource allocation type 1) is used,

[0373] 4-3-2-Ai. If the number of PRBs in a BWP is 90 or less

[0374] The UE shall truncate the FDRA field to its LSB. And the truncated FDRA field is interpreted as the FDRA field of DCI format 0_0.

[0375] 4-3-2-A-ii. If the number of PRBs in the BWP is greater than 90,

[0376] Then the UE performs padding of 0s as many as the MSB before the FDRA field and interprets the extended FDRA field as the FDRA field of DCI format 0_0. At this time, if the frequency hopping flag is 0, N UL，hopis 0, and if the frequency hopping flag is 1, then N UL，hop Follow Table 19.

[0377] 4-3-2-A-iii. End

[0378] 4-3-2-A-iv. In this case, the new threshold 90 means the maximum number of PRBs of a BWP that can be transmitted with 12 bits when the uplink resource allocation type 1 (RIV) scheme is used. (90*91 / 2=4095≤4096=212)

[0379] 4-3-2-B. If the higher layer parameter useInterlacePUSCH-common is provided, i.e., when uplink resource allocation type 2 as interlace mapping is used

[0380] 4-3-2-Bi. The UE truncates the FDRA field to its LSB (or MSB) X bits and interprets the truncated FDRA field as the FDRA field of DCI format 0_0. When PUSCH is sent in a band configured with 30kHz SCS (i.e., μ=1), X is 5, and when PUSCH is sent in a band configured with 15kHz SCS (i.e., μ=0), X is 6.

[0381] 4-3-2-B-ii. When adding LBT subband allocation, Y bits may be added before or after the X bits of the FDRA field. Depending on the number of LBT subbands set in the BWP, Y may be determined as one of {0, 1, 2, 3, 4}.

[0382] Based on 4-3-1 and 4-3-2, Table 18 can be modified as shown in Table 20.

[0383] [Table 20]

[0384]

[0385]

[0386] In addition, when useInterlacePUSCH-common is set, the RAR UL grant field size may be defined / configured as follows.

[0387] 4-4-1. Alternative option 1)

[0388] Since the actual FDRA only requires X bits, the size of the FDRA field is defined as X bits, and the remaining bits can be used as a reserved field. In addition, the reserved field position can be immediately before or after the FDRA field, or a specific position of the RAR UL grant (e.g., the last (i.e., LSB) in the RAR UL grant).

[0389] Characteristically, when the SCS for PUSCH transmission is 30 kHz, X may be 5 bits, and when the SCS for PUSCH transmission is 15 kHz, X may be 6 bits.

[0390] As an example, if the application reserves the example of the field position being the last one, each field in the RAR license may be defined as shown in Table 21.

[0391] [Table 21]

[0392]

[0393] 4-4-2. Option 2)

[0394] Since the actual FDRA only requires X bits, the size of the FDRA field can be defined as X bits, and the remaining bits can be used as a reserved field. In addition, the reserved field position can be immediately before or after the FDRA field, or a specific position of the RAR UL grant (e.g., the last (i.e., LSB) in the RAR UL grant).

[0395] At this time, since 5 bits are required when the SCS for PUSCH transmission is 30 kHz and 6 bits are required when the SCS is 15 kHz, X may be configured as 6 bits to satisfy two SCSs.

[0396] In this case, when the SCS is 30 kHz, the UE may truncate the FDRA field to 5 bits of LSB (or MSB) and interpret it as the FDRA field.

[0397] As an example, if the application reserves the example of the field position being the last one, each field in the RAR license can be defined as shown in Table 22.

[0398] [Table 22]

[0399]

[0400] The Y bits allocated for the LBT subband may also be included in the PUSCH frequency resource allocation. Therefore, in Table 21 and / or Table 22, Y bits may be added to the PUSCH frequency resource allocation field and Y bits may be omitted from the reserved field.

[0401] DRX (Discontinuous Receive) Operation

[0402] The UE may perform DRX operation while executing the above / proposed process and / or method. A DRX-configured UE may reduce power consumption by discontinuously receiving DL signals. DRX may be performed in the RRC (Radio Resource Control)_IDLE state, the RRC_INACTIVE state, and the RRC_CONNECTED state. In the RRC_IDLE state and the RRC_INACTIVE state, DRX is used to discontinuously receive paging signals. In the following, DRX performed in the RRC_CONNECTED state (RRC_CONNECTED DRX) will be described.

[0403] Fig.16 The DRX cycle (RRC_CONNECTED state) is illustrated.

[0404] Reference Fig.16 , the DRX cycle consists of an on-duration and an opportunity for DRX. The DRX cycle defines a time interval, wherein the on-duration is repeated periodically. The on-duration indicates the time period during which the UE monitors and receives the PDCCH. When DRX is configured, the UE performs PDCCH monitoring during the on-duration. If the PDCCH is successfully detected during the PDCCH monitoring, the UE operates the inactivity timer and remains awake. On the other hand, if the PDCCH is not successfully detected during the PDCCH monitoring, the UE enters a sleep state after the on-duration ends. Therefore, when DRX is configured, PDCCH monitoring / reception can be performed discontinuously in the time domain when performing the process and / or method described / proposed above. For example, when DRX is configured, in various embodiments, the PDCCH reception opportunity (e.g., a time slot with a PDCCH search space) can be configured discontinuously according to the DRX configuration. On the other hand, when DRX is not configured, PDCCH monitoring / reception can be performed continuously in the time domain when performing the process and / or method described / proposed above. For example, when DRX is not configured, the PDCCH reception opportunities (eg, time slots with PDCCH search spaces) in various embodiments may be configured continuously. In addition, regardless of whether DRX is configured, PDCCH monitoring may be limited to time intervals configured as measurement gaps.

[0405] Table 23 shows the process of UE related to DRX (RRC_CONNECTED state). Referring to Table 31, DRX configuration information is received through high-layer (e.g., RRC) signaling, and whether DRX is turned on / off is controlled by a DRX command of the MAC layer. If DRX is configured, the UE may perform PDCCH monitoring discontinuously when performing the processes and / or methods proposed / described in various embodiments.

[0406] [Table 23]

[0407]

[0408] Here, MAC-CellGroupConfig includes configuration information necessary for configuring MAC (Media Access Control) parameters for a cell group. MAC-CellGroupConfig may also include configuration information related to DRX. For example, MAC-CellGroupConfig may include the following information to define DRX.

[0409] -drx-OnDurationTimer value: defines the length of the start duration of the DRX cycle

[0410] - Value of drx-InactivityTimer: defines the length of time that the UE stays awake after detecting a PDCCH opportunity indicating a PDCCH for initial UL or DL ​​data.

[0411] - Value of drx-HARQ-RTT-TimerDL: defines the length of the maximum duration from the reception of a DL initial transmission until the reception of a DL retransmission.

[0412] - Value of drx-HARQ-RTT-TimerDL: defines the length of the maximum duration from receiving the UL initial transmission grant until receiving the UL retransmission grant.

[0413] -drx-LongCycleStartOffset: defines the time length and starting point of the DRX cycle.

[0414] -drx-ShortCycle (optional): defines the duration of the short DRX cycle.

[0415] Here, if any one of drx-OnDurationTimer, drx-InactivityTimer, drx-HARQ-RTT-TimerDL, and drx-HARQ-RTT-TimerDL is in operation, the UE performs PDCCH monitoring at each PDCCH opportunity while maintaining an awake state.

[0416] After the operations described in each embodiment of the present disclosure, the UE may perform such a DRX-related operation. The UE performs a RACH procedure according to an embodiment of the present disclosure. The UE performs a RACH procedure according to an embodiment of the present disclosure, and then the UE performs PDCCH monitoring during the startup duration, and when the PDCCH is successfully detected during the PDCCH monitoring, the UE operates an inactivity timer (drx-InactivityTimer) and maintains the awake state.

[0417] Implementation Example

[0418] Fig.17 is a flowchart of a signal transmission / reception method according to an embodiment of the present disclosure.

[0419] Reference Fig.17 , an embodiment of the present disclosure may be performed by a UE and may include a step of receiving a RAR based on a PRACH (S1701) and a step of sending a PUSCH based on the RAR (S1703). Although not shown, an embodiment of the present disclosure performed from the perspective of a base station may include the steps of sending a RAR based on a PRACH and receiving a PUSCH based on the RAR.

[0420] The RAR may be configured based on implementation mode 4. For example, the RAR may be a fallback RAR for message A in a 2-step random access procedure. The RAR may be a Msg.2RAR for Msg.1PRACH in a 4-step random access procedure.

[0421] The channel access type (LBT type) for PUSCH (Msg.3PUSCH) can be determined based on one or more of the proposed methods 4-1-1 to 4-1-6 of implementation mode 4.

[0422] The frequency resources used to transmit the PUSCH may be determined based on the FDRA (Frequency Domain Resource Allocation) field. According to 4-3-2 of the present disclosure, the interpretation of the FDRA field for the PUSCH transmitted in the shared spectrum may be different from the interpretation of the FDRA field for the PUSCH transmitted in the non-shared spectrum.

[0423] For example, depending on whether the high-level parameter useInterlacePUSCH-common is set, whether the 12-bit FDRA field is truncated to some of its LSBs or whether the MSBs other than the 12-bit FDRA field are filled is different, and the number of X LSBs and Y MSBs is also different. That is, based on whether interleaving allocation of PUSCH for shared spectrum channel access is provided, the FDRA field may be truncated to its X LSBs, or the FDRA field may be filled with Y MSBs.

[0424] The FDRA field is truncated or padded, and the truncated FDRA field or the padded FDRA field is interpreted as the FDRA field of DCI format 0_0.

[0425] In accordance with 4-3-2-Ai, based on the fact that interleaving allocation of PUSCH for shared spectrum channel access is not provided and the number of PRBs in the BWP is 90 or less, the FDRA field is truncated to its X LSBs, where the X LSBs are determined based on the number of PRBs in the BWP.

[0426] When the number of PRBs in a BWP is N When X LSBs are determined LSBs (i.e., ceil(log2(N*(N+1) / 2)) LSBs).

[0427] According to 4-3-2-A-ii, based on the fact that no interleaving allocation of PUSCH for shared spectrum channel access is provided and the number of PRBs in the BWP is greater than 90, the FDRA field is populated with Y MSBs, where the Y MSBs are determined based on the number of PRBs in the BWP.

[0428] When the number of PRBs in a BWP is N When Y MSBs are determined as MSBs (i.e., ceil(log2(N*(N+1) / 2))-12 MSBs).

[0429] When resources are allocated based on interleaved allocation that does not provide PUSCH for shared spectrum channel access, the threshold 90 is determined in consideration of the maximum number of PRBs that can be indicated by 12 bits within the BWP.

[0430] According to 4-3-2-B, based on the setting of interleaved allocation of PUSCH for shared spectrum channel access, for 30kHz SCS, X LSBs are determined to be 5 LSBs, and for 15kHz SCS, X LSBs are determined to be 6 LSBs.

[0431] In addition to reference Fig.17 In addition to the operations described, refer to Figures 1 to 16 One or more of the operations described and / or the operations described with respect to embodiments 1 to 4 may be combined and performed additionally. For example, the UE may perform uplink LBT before transmission of the PRACH. Alternatively, the UE may monitor the PDCCH based on DRX configured after random access.

[0432] Example of a communication system to which the present disclosure is applied

[0433] Although not limited thereto, the various descriptions, functions, processes, proposals, methods and / or operational flowcharts of the present disclosure disclosed in this document may be applied to various fields requiring wireless communication / connection (e.g., 5G) between devices.

[0434] In the following, examples will be described in more detail with reference to the accompanying drawings. In the following drawings / descriptions, unless otherwise specified, the same reference numerals may represent the same or corresponding hardware blocks, software blocks or functional blocks.

[0435] Fig.18 A communication system 1 applied to the present disclosure is illustrated.

[0436] Reference Fig.18 , the communication system 1 applied to the present disclosure includes a wireless device, a base station and a network. Here, the wireless device means a device that performs communication using a wireless access technology (e.g., 5G NR (new RAT), LTE (long term evolution)), and may be referred to as a communication / wireless / 5G device. Although not limited to this, the wireless device includes a robot 100a, a vehicle 100b-1, 100b-2, an extended reality (XR) device 100c, a handheld device 100d and a home appliance 100e, an Internet of Things (IoT) device 100f and an AI device / server 400. For example, a vehicle may include a vehicle equipped with a wireless communication function, an autonomous driving vehicle, a vehicle capable of inter-vehicle communication, and the like. Here, the vehicle may include an unmanned aerial vehicle (UAV) (e.g., a drone). The XR device includes an AR (augmented reality) / VR (virtual reality) / MR (mixed reality) device, and may be implemented in the form of a head-mounted device (HMD), a head-up display (HUD) set in a vehicle, a television, a smartphone, a computer, a wearable device, a home appliance, a digital signage, a vehicle, a robot, and the like. Portable devices may include smart phones, smart tablets, wearable devices (e.g., smart watches, smart glasses), computers (e.g., laptop computers), etc. Home appliances may include televisions, refrigerators, washing machines, etc. IoT devices may include sensors, smart meters, etc. For example, base stations and networks may be implemented as wireless devices, and a specific wireless device 200a may operate as a base station / network node relative to other wireless devices.

[0437] The wireless devices 100a to 100f may be connected to the network 300 through the base station 200. Artificial intelligence (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 through 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. The wireless devices 100a to 100f may communicate with each other through the base station 200 / network 300, but may also communicate directly (e.g., side link communication) without going through the base station / network. For example, the vehicles 100b-1 and 100b-2 may perform direct communication (e.g., vehicle-to-vehicle (V2V) / vehicle-to-everything (V2X) communication). In addition, an IoT device (e.g., a sensor) may communicate directly with other IoT devices (e.g., a sensor) or other wireless devices 100a to 100f.

[0438] Wireless communication / connection 150a, 150b, 150c can be performed between wireless devices 100a to 100f and base station 200 and between base station 200 and base station 200. Here, wireless communication / connection can be performed through various wireless access technologies (e.g., 5G NR) such as uplink / downlink communication 150a, sidelink communication 150b (or D2D communication) and inter-base station communication 150c. Through wireless communication / connection 150a, 150b and 150c, wireless devices and base stations / wireless devices and base stations and base stations can send / receive radio signals to each other. For example, wireless communication / connection 150a, 150b and 150c can send / receive signals through various physical channels. To this end, based on various proposals of the present disclosure, at least a part of various configuration information configuration processes, various signal processing processes (e.g., channel coding / decoding, modulation / demodulation, resource mapping / demapping, etc.), resource allocation processes, etc. can be performed.

[0439] Examples of wireless devices applicable to the present disclosure

[0440] Fig.19 A wireless device to which the present disclosure is applied is exemplified.

[0441] Reference Fig.19 , the first wireless device 100 and the second wireless device 200 can send / receive wireless signals through various wireless access technologies (e.g., LTE, NR). Here, {the first wireless device 100, the second wireless device 200} can be connected to Fig.18 The wireless device 100x and the base station 200 correspond to each other.

[0442] The first wireless device 100 includes one or more processors 102 and one or more memories 104, and may also include one or more transceivers 106 and / or one or more antennas 108. The processor 102 controls the memory 104 and / or the transceiver 106 and may be configured to implement the descriptions, functions, processes, suggestions, methods and / or operational flowcharts disclosed herein. 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. In addition, the processor 102 may receive a radio signal including second information / signals through the transceiver 106, and then store information obtained from the signal processing of 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 some or all processes controlled by the processor 102 or for executing the descriptions, functions, processes, suggestions, methods and / or operational flowcharts disclosed in the document. Here, the processor 102 and the memory 104 may be part of a communication modem / circuit / chip designed to implement wireless communication technology (e.g., LTE, NR). The transceiver 106 may be connected to the processor 102 and may send and / or receive wireless signals via one or more antennas 108. The 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, a wireless device may refer to a communication modem / circuit / chip.

[0443] The second wireless device 200 includes one or more processors 202, one or more memories 204, and may also include one or more transceivers 206 and / or one or more antennas 208. The processor 202 controls the memory 204 and / or the transceiver 206 and may be configured to implement the descriptions, functions, processes, suggestions, methods and / or operational flowcharts disclosed herein. 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. In addition, the processor 202 may receive a radio signal including fourth information / signals through the transceiver 206, and then store information obtained from signal processing of the fourth information / signals in the memory 204. The memory 204 may be connected to the processor 202 and may store various information related to the operation of the processor 202. For example, the memory 204 may store software codes including instructions for executing some or all processes controlled by the processor 202 or for executing the descriptions, functions, processes, suggestions, methods and / or operational flowcharts disclosed in the document. Here, the processor 202 and the memory 204 may be part of a communication modem / circuit / chip designed to implement wireless communication technology (e.g., LTE, NR). The transceiver 206 may be connected to the processor 202 and may send and / or receive wireless signals via one or more antennas 208. The transceiver 206 may include a transmitter and / or a receiver. The transceiver 206 may be used interchangeably with an RF unit. In various embodiments, the wireless device may refer to a communication modem / circuit / chip.

[0444] In the following, the hardware elements of the wireless devices 100 and 200 will be described in more detail. Although not limited to this, one or more protocol layers can be implemented by one or more processors 102, 202. For example, one or more processors 102, 202 can implement one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, SDAP). One or more processors 102, 202 can 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 herein. One or more processors 102, 202 can generate messages, control information, data, or information according to the descriptions, functions, processes, proposals, methods, and / or flowcharts disclosed herein. One or more processors 102 and 202 generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information according to the functions, procedures, proposals, and / or methods disclosed herein and provide them to one or more transceivers 106 and 206. One or more processors 102, 202 may receive signals (e.g., baseband signals) from one or more transceivers 106, 206 and may obtain PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or operational flow charts disclosed herein.

[0445] One or more processors 102, 202 may be referred to as controllers, microcontrollers, microprocessors, or microcomputers. One or more processors 102, 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, 202. The descriptions, functions, processes, suggestions, methods, and / or operational flowcharts disclosed in this document may be implemented using firmware or software, and the firmware or software may be implemented to include modules, processes, functions, and the like. Firmware or software configured to perform the descriptions, functions, processes, suggestions, methods, and / or flowcharts disclosed herein may be included in one or more processors 102, 202, or may be stored in one or more memories 104, 204 and driven by one or more processors 102, 202. The descriptions, functions, processes, suggestions, methods and / or operational flow charts disclosed herein may be implemented using firmware or software in the form of codes, instructions and / or instruction sets.

[0446] One or more memories 104, 204 may be coupled to one or more processors 102, 202 and may store various forms of data, signals, messages, information, programs, codes, instructions, and / or instructions. One or more memories 104, 204 may include ROM, RAM, EPROM, flash memory, hard drive, registers, cache memory, computer-readable storage media, and / or combinations thereof. One or more memories 104, 204 may be located inside and / or outside of one or more processors 102, 202. In addition, one or more memories 104, 204 may be coupled to one or more processors 102, 202 via various technologies such as wired or wireless connections.

[0447] One or more transceivers 106, 206 can send user data, control information, radio signals / channels, etc. mentioned in the methods and / or operation flow charts of this article to one or more other devices. One or more transceivers 106, 206 can receive user data, control information, radio signals / channels, etc. mentioned in the description, function, process, suggestion, method and / or flow chart disclosed in this article from one or more other devices. For example, one or more transceivers 106, 206 can be connected to one or more processors 102, 202 and can send and receive wireless signals. For example, one or more processors 102, 202 can control one or more transceivers 106, 206 to send user data, control information or wireless signals to one or more other devices. In addition, one or more processors 102, 202 can control one or more transceivers 106, 206 to receive user data, control information or wireless signals from one or more other devices. In addition, one or more transceivers 106, 206 may be connected to one or more antennas 108, 208, and may be configured to send and receive user data, control information, radio signals / channels, etc. mentioned in the description, function, process, proposal, method and / or operation flow chart through one or more antennas 108, 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, 206 convert received radio signals / channels, etc. from RF band signals to baseband signals to process received user data, control information, radio signals / channels, etc. using one or more processors 102, 202. One or more transceivers 106 and 206 may convert user data, control information, radio signals / channels, etc. processed using one or more processors 102 and 202 from baseband signals to RF band signals. To this end, one or more transceivers 106, 206 may include (analog) oscillators and / or filters.

[0448] Examples of applications of wireless devices to which the present disclosure is applied

[0449] Fig. 20 Another example of a wireless device applied to the present disclosure is shown. The wireless device can be based on the use example / service (refer to Fig.18 ) are implemented in various forms.

[0450] Reference Fig. 20 , the wireless devices 100 and 200 can communicate with Fig.19 The wireless devices 100 and 200 of the present invention correspond to each other and may be composed of various elements, components, units and / or modules. For example, the wireless devices 100 and 200 may include a communication unit 110, a control unit 120, a memory unit 130 and an additional element 140. The communication unit may include a communication circuit 112 and a transceiver 114. For example, the communication circuit 112 may include Fig.19 The one or more processors 102, 202 and / or one or more memories 104, 204 of the present invention may include: Fig.19 The controller 120 may be configured to control one or more transceivers 106, 206 and / or one or more antennas 108, 208 of the wireless device. The control unit 120 is electrically connected to the communication unit 110, the memory unit 130, and the additional element 140, and controls the general operation of the wireless device. For example, the controller 120 may control the electrical / mechanical operation of the wireless device based on the program / code / command / information stored in the memory unit 130. In addition, the control unit 120 may transmit information stored in the memory unit 130 to the outside (e.g., another communication device) through the communication unit 110 via a wireless / wired interface, or may store information received from the outside (e.g., another communication device) through the communication unit 110 via a wireless / wired interface in the memory unit 130.

[0451] The additional element 140 may be variously configured according to the type of the wireless device. For example, the additional element 140 may include at least one of a power supply unit / battery, an input / output unit (I / O unit), a drive unit, and a computing unit. Although not limited thereto, the wireless device may be a robot ( Fig.18 and 100a), vehicles ( Fig.18 , 100b-1, 100b-2), XR device ( Fig.18 , 100c), mobile device ( Fig.18 , 100d), household appliances ( Fig.18 , 100e), IoT devices ( Fig.18 , 100f), digital broadcast terminal, holographic device, public safety device, MTC device, medical device, fintech device (or financial device), security device, climate / environmental device, AI server / device ( Fig.18,400),base station( Fig.18 , 200) and the form of a network node. Depending on the use case / service, the wireless device can be mobile or used in a fixed location.

[0452] exist Fig. 20 In the wireless devices 100 and 200, various elements, components, units and / or modules in the wireless devices 100 and 200 may all be interconnected through a wired interface, or at least some of them may be wirelessly connected through the communication unit 110. For example, in the wireless devices 100 and 200, the control unit 120 and the communication unit 110 are connected by wiring, and the control unit 120 and the first unit (e.g., 130, 140) may be wirelessly connected to the communication unit 110 through the communication unit 110. In addition, each element, component, unit and / or module in the wireless devices 100 and 200 may also include one or more elements. For example, the controller 120 may be configured with one or more processor groups. For example, the control unit 120 may be configured as a group of communication control processors, application processors, electronic control units (ECUs), graphics processing processors, memory control processors, etc. As another example, the memory unit 130 may include a random access memory (RAM), a dynamic RAM (DRAM), a read-only memory (ROM), a flash memory, a volatile memory, and a non-volatile memory) and / or a combination thereof.

[0453] Examples of vehicles or autonomous driving vehicles to which the present disclosure is applied

[0454] Fig.21 The vehicle or autonomous driving vehicle to which the present disclosure is applied is exemplified. The vehicle or autonomous driving vehicle can be implemented as a mobile robot, a vehicle, a train, an aircraft (AV), a ship, etc.

[0455] Reference Fig.21 , the vehicle or autonomous 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 and 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. The blocks 110 / 130 / 140a-140d are respectively Fig. 20 Corresponding to blocks 110 / 130 / 140.

[0456] The communication unit 110 can send and receive signals (e.g., data, control signals, etc.) with other vehicles, base stations (e.g., base stations, roadside base stations, etc.), servers, etc. The controller 120 can control the elements of the vehicle or autonomous driving vehicle 100 to perform various operations. The controller 120 may include an electronic control unit (ECU). The drive unit 140a can enable the vehicle or autonomous driving vehicle 100 to travel on the ground. The drive unit 140a may include an engine, a motor, a powertrain, wheels, brakes, a steering device, etc. The power supply unit 140b supplies power to the vehicle or autonomous driving vehicle 100, and may include a wired charging circuit / wireless charging circuit, a battery, etc. The sensor unit 140c can obtain 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 tilt sensor, a weight sensor, a heading sensor, a location module, and a vehicle forward movement / reverse movement sensor, a battery sensor, a fuel sensor, a tire sensor, a steering sensor, a temperature sensor, a humidity sensor, an ultrasonic sensor, an illumination sensor, a pedal position sensor, etc. The autonomous driving unit 140d may implement a technology for maintaining a driving lane, a technology for automatically adjusting a speed (e.g., adaptive cruise control), a technology for autonomous driving along a predetermined route, and a technology for automatically setting a route when a destination is set.

[0457] As an 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 based on the acquired data. The controller 120 may control the drive unit 140a to move the vehicle or the autonomous driving vehicle 100 along the autonomous driving path (e.g., speed / direction adjustment) according to the driving plan. During autonomous driving, the communication unit 110 may obtain the latest traffic information data from an external server aperiodically / periodically, and may obtain surrounding traffic information data from surrounding vehicles. In addition, during autonomous driving, the sensor unit 140c may obtain vehicle status and surrounding environment information. The autonomous driving unit 140d may update the autonomous driving route and driving plan based on the newly acquired data / information. The communication unit 110 may send information about the vehicle position, autonomous driving route, driving plan, etc. to an external server. The external server may use AI technology, etc., based on information collected from the vehicle or autonomous driving vehicle, to predict traffic information data in advance, and may provide the predicted traffic information data to the vehicle or autonomous driving vehicle.

[0458] It is obvious to those skilled in the art that the present disclosure can be implemented in other specific forms without departing from the features of the present disclosure. Therefore, the above detailed description should not be interpreted as restrictive in all aspects, but should be interpreted as exemplary. The scope of the present disclosure should be determined by a reasonable interpretation of the attached claims, and all modifications within the equivalent scope of the present disclosure are included in the scope of the present disclosure.

[0459] Industrial Applicability

[0460] As described above, the present disclosure can be applied to various wireless communication systems.

Claims

1. A method for transmitting and receiving a signal by a user equipment UE operating in a wireless communication system, the method comprising the following steps: Receiving a random access response RAR based on a physical random access channel PRACH; as well as In the bandwidth part BWP, a physical uplink shared channel PUSCH for shared spectrum channel access is transmitted based on the RAR; The frequency domain resource allocation for the PUSCH transmission in the BWP is based on the frequency domain resource assignment FDRA field in the RAR, Wherein, based on the fact that no information on the interleaving allocation of the PUSCH is provided through high-layer signaling, (i) based on the number of physical resource blocks (PRBs) N in the BWP being equal to or less than a threshold value of 90, the FDRA field is truncated to The least significant bit LSB, and (ii) based on the number N of physical resource blocks (PRBs) in the BWP being greater than a threshold value of 90, using The most significant bits MSB are used to fill the FDRA field. Wherein, based on providing the information about the interleaving allocation of the PUSCH through the high-layer signaling: (i) based on the subcarrier spacing SCS for the BWP being 30 kHz, truncating the FDRA field to 5 LSBs, or (ii) based on the SCS for the BWP being a 15kHz SCS, truncating the FDRA field to 6 LSBs, and The FDRA field is interpreted as the FDRA field of the downlink control information DCI format 0_0.

2. The method according to claim 1, wherein: Based on the fact that no information about the interlace allocation of the PUSCH is provided by the higher layer signaling, uplink resource allocation type 1 is used, and Based on the information about the interlace allocation of the PUSCH being provided through the higher layer signaling, uplink resource allocation type 2 is used.

3. The method according to claim 1, wherein: For the shared spectrum channel access, the 12-bit FDRA field is received from a base station.

4. The method according to claim 3, wherein: When resources are allocated based on the fact that the information on the interlace allocation of the PUSCH is not provided through the higher layer signaling, the threshold 90 is determined in consideration of a maximum number of PRBs in the BWP that can be indicated by 12 bits.

5. A user equipment UE configured to send and receive signals in a wireless communication system, the UE comprising: at least one transceiver; at least one processor; as well as At least one memory operatively coupled to the at least one processor and storing instructions, the instructions upon being executed causing the at least one processor to perform operations, the operations comprising: Receiving a random access response RAR based on a physical random access channel PRACH; as well as In the bandwidth part BWP, a physical uplink shared channel PUSCH for shared spectrum channel access is transmitted based on the RAR, The frequency domain resource allocation for the PUSCH transmission in the BWP is based on the frequency domain resource assignment FDRA field in the RAR, Wherein, based on the fact that no information on the interleaving allocation of the PUSCH is provided through high-layer signaling, (i) based on the number of physical resource blocks (PRBs) N in the BWP being equal to or less than a threshold value of 90, the FDRA field is truncated to The least significant bit LSB, and (ii) based on the number N of physical resource blocks (PRBs) in the BWP being greater than a threshold value of 90, using The most significant bits MSB are used to fill the FDRA field. Wherein, based on providing the information about the interleaving allocation of the PUSCH through the high-layer signaling: (i) based on the subcarrier spacing SCS for the BWP being 30 kHz, truncating the FDRA field to 5 LSBs, or (ii) based on the SCS for the BWP being a 15kHz SCS, truncating the FDRA field to 6 LSBs, and The FDRA field is interpreted as the FDRA field of the downlink control information DCI format 0_0.

6. The UE according to claim 5, wherein: Based on the fact that no information about the interlace allocation of the PUSCH is provided by the higher layer signaling, uplink resource allocation type 1 is used, and Based on the information about the interlace allocation of the PUSCH being provided through the higher layer signaling, uplink resource allocation type 2 is used.

7. The UE according to claim 5, wherein: For the shared spectrum channel access, the 12-bit FDRA field is received from a base station.

8. The UE according to claim 7, wherein: When resources are allocated based on the fact that the information on the interlace allocation of the PUSCH is not provided through the higher layer signaling, the threshold 90 is determined in consideration of a maximum number of PRBs in the BWP that can be indicated by 12 bits.

9. A method for transmitting and receiving signals by a base station operating in a wireless communication system, the method comprising the steps of: Sending a random access response RAR based on a physical random access channel PRACH; as well as In the bandwidth part BWP, a physical uplink shared channel PUSCH for shared spectrum channel access is received based on the RAR; The frequency domain resource allocation for the PUSCH transmission in the BWP is based on the frequency domain resource assignment FDRA field in the RAR, Wherein, based on the fact that no information on the interleaving allocation of the PUSCH is provided through high-layer signaling, (i) based on the number of physical resource blocks (PRBs) N in the BWP being equal to or less than a threshold value of 90, the FDRA field is truncated to The least significant bit LSB, and (ii) based on the number N of physical resource blocks (PRBs) in the BWP being greater than a threshold value of 90, using The most significant bits MSB are used to fill the FDRA field. Wherein, based on providing the information about the interleaving allocation of the PUSCH through the high-layer signaling: (i) based on the subcarrier spacing SCS for the BWP being 30 kHz, truncating the FDRA field to 5 LSBs, or (ii) based on the SCS for the BWP being a 15kHz SCS, truncating the FDRA field to 6 LSBs, and The FDRA field is interpreted as the FDRA field of the downlink control information DCI format 0_0.

10. A device for a user equipment UE, the device comprising: at least one processor; as well as at least one computer memory operatively coupled to the at least one processor and storing instructions that upon being executed cause the at least one processor to perform operations, The operations include the following: receiving a random access response RAR based on a physical random access channel PRACH; and In the bandwidth part BWP, a physical uplink shared channel PUSCH for shared spectrum channel access is transmitted based on the RAR, The frequency domain resource allocation for the PUSCH transmission in the BWP is based on the frequency domain resource assignment FDRA field in the RAR, Wherein, based on the fact that no information on the interleaving allocation of the PUSCH is provided through high-layer signaling, (i) based on the number of physical resource blocks (PRBs) N in the BWP being equal to or less than a threshold value of 90, the FDRA field is truncated to The least significant bit LSB, and (ii) based on the number N of physical resource blocks (PRBs) in the BWP being greater than a threshold value of 90, using The most significant bits MSB are used to fill the FDRA field. Wherein, based on providing the information about the interleaving allocation of the PUSCH through the high-layer signaling: (i) based on the subcarrier spacing SCS for the BWP being 30 kHz, truncating the FDRA field to 5 LSBs, or (ii) based on the SCS for the BWP being a 15kHz SCS, truncating the FDRA field to 6 LSBs, and The FDRA field is interpreted as the FDRA field of the downlink control information DCI format 0_0.

Images