Patent Description:
Wireless communication systems are being widely deployed to provide various types of communication services such as voice and data. In general, a wireless communication system is multiple access system that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmission power and the like). Examples of the multiple access system include CDMA(Code Division Multiple Access) system, FDMA(Frequency Division Multiple Access) system, TDMA(Time Division Multiple Access) system, OFDMA(Orthogonal Frequency Division Multiple Access) system, and SC-FDMA(Single Carrier Frequency Division Multiple Access) system and the like. Document: <NPL>), relates to UL/DL resource allocation in 3GPP.

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 therefor.

The technical problem of the present disclosure is not limited to the above-described technical problem, and other technical problems may be inferred from the embodiments of the present disclosure.

The present disclosure is to provide a method and an apparatus for receiving and transmitting a signal in a wireless communication system.

As an aspect of the present disclosure, a method of transmitting and receiving according to claim <NUM> is provided.

In another aspect of the present disclosure, a communication device(user equipment, UE) for transmitting and receiving a signal according to claim <NUM> is provided.

In another aspect of the present disclosure, a method according to claim <NUM> is provided.

In the method and devices, based on the interlace allocation of the PUSCH for the shared spectrum channel access being not provided and a number of PRBs in a bandwidth part (BWP) being equal to or less than <NUM>, the FDRA field may be truncated to its X LSBs, where the X LSBs may be determined based on the number of PRBs in the BWP.

In the method and devices, based on the interlace allocation of the PUSCH for the shared spectrum channel access being not provided and a number of PRBs in the BWP being greater than <NUM>, the FDRA field may be padded with Y MSBs, where the X MSBs may be determined based on the number of PRBs in the BWP.

In the method and devices, based on the number of PRBs in the BWP being N, the X LSBs may be determined as ceil (log<NUM>(N * (N+<NUM>)/<NUM>)) LSB and the Y MSBs may be determined as ceil (log<NUM>(N * (N+<NUM>)/<NUM>)) -<NUM> MSB.

In the method and devices, the FDRA field may be received by a base station in <NUM> bits, the <NUM> may be determined in consideration of a maximum number of PRBs that can be indicated by <NUM> bits in the BWP when resources are allocated based on the interlace allocation of PUSCH for the shared spectrum channel access being not provided.

In the method and devices, based on the interlace allocation of the PUSCH for the shared spectrum channel access being provided, the X LSBs may be determined as <NUM> LSB for <NUM> subcarrier spacing (SCS) and <NUM> LSB for <NUM> SCS.

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

The above-described aspects of the present disclosure are only some of the preferred embodiments of the present disclosure, and various embodiments in which the technical features of the present disclosure are reflected may be derived and understood by those of ordinary skill in the art based on the detailed description of the present disclosure to be described below.

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

The technical effects of the present disclosure is not limited to the above-described technical effects, and other technical effects may be inferred from the embodiments of the present disclosure.

The following techniques may be used in various radio access systems such as CDMA, FDMA, TDMA, OFDMA, SC-FDMA, and the like. CDMA may be implemented with a radio technology such as Universal Terrestrial Radio Access (UTRA) or CDMA2000. TDMA may be implemented with a radio technology such as Global System for Mobile communications (GSM)/General Packet Radio Service (GPRS)/Enhanced Data Rates for GSM Evolution (EDGE). OFDMA may be implemented with a radio technology such as IEEE <NUM> (Wi-Fi), IEEE <NUM> (WiMAX), IEEE <NUM>-<NUM>, Evolved UTRA (E-UTRA), and the like. UTRA is part of the Universal Mobile Telecommunications System (UMTS). 3GPP (<NUM>rd Generation Partnership Project) Long Term Evolution (LTE) is a 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.

For clarity of description, it is described based on a 3GPP communication system (e.g., LTE, NR), but the technical idea of the present disclosure is not limited thereto. LTE refers to technology after 3GPP TS <NUM>. xxx Release <NUM>. In detail, LTE technology after 3GPP TS <NUM>. xxx Release <NUM> is referred to as LTE-A, and LTE technology after 3GPP TS <NUM>. xxx Release <NUM> is referred to as LTE-A pro. 3GPP NR refers to technology after TS <NUM>. xxx Release <NUM>. LTE/NR may be referred to as a 3GPP system, "xxx" stands for standard document detail number. LTE/NR may be collectively referred to as a 3GPP system. For background art, terms, abbreviations, etc. used in the description of the present disclosure, reference may be made to matters described in standard documents published before the present disclosure. For example, it may refer to the following documents:.

<FIG> illustrates the structure of a radio frame used in NR.

Uplink (UL) and downlink (DL) transmission in NR consists of frames. A radio frame has a length of <NUM> and is defined as two <NUM> half-frames (Half-Frame, HF). A half-frame is defined as <NUM><NUM> subframes (Subframe, SF). A subframe is divided into one or more slots, and the number of slots in a subframe depends on subcarrier spacing (SCS). Each slot includes <NUM> or <NUM> OFDM(A) symbols according to a cyclic prefix (CP). When a normal CP (CP) is used, each slot includes <NUM> symbols. When an extended CP (extended CP) is used, each slot includes <NUM> symbols. Here, the symbol may include an OFDM symbol (or, a CP-OFDM symbol) and an SC-FDMA symbol (or, a DFT-s-OFDM symbol).

Table <NUM> exemplifies that the number of symbols per a slot, the number of slots per a frame, and the number of slots per a subframe vary according to the SCS when the normal CP is used.

Table <NUM> exemplifies that the number of symbols per a slot, the number of slots per a frame, and the number of slots per a subframe vary according to the SCS when the extended CP is used.

In the NR system, OFDM (A) numerology (e.g., SCS, CP length, etc.) may be configured differently between a plurality of cells merged into one user equipment (UE). Accordingly, an (absolute time) duration of a time resource (e.g., SF, slot, or TTI) (commonly referred to as TU (Time Unit) for convenience) composed of the same number of symbols may be configured differently between the merged cells.

NR supports multiple OFDM(Orthogonal Frequency Division Multiplexing) numerology (e.g., subcarrier spacing, SCS) to support various <NUM> services. For example, when the SCS is <NUM>, it supports a wide area in traditional cellular bands, and when the SCS is <NUM>/ <NUM>, it supports dense-urban, lower latency and a wider carrier bandwidth.

NR frequency band is defined as two types of frequency range (FR) (FR1, FR2). FR1/FR2 may be configured as shown in Table <NUM> below. In addition, FR2 may mean a millimeter wave (mmW).

<FIG> exemplifies a slot structure of an NR frame.

A slot includes a pluarlity of symbols in a time domain. For example, in the case of a normal CP, one slot includes <NUM> symbols, and in the case of an extended CP, one slot includes <NUM> symbols. The carrier includes a plurality of subcarriers in a frequency domain. A resource block (RB) is defined as a plurality of (e.g., <NUM>) consecutive subcarriers in a frequency domain. A plurality of RB interlaces (simply, interlaces) may be defined in a frequency domain. Interlace mE{<NUM>, <NUM>,. , M-<NUM>} may be composed of (common) RB {m, M+m, <NUM>+m, <NUM>+m,. M represents the number of interlaces. BWP (Bandwidth Part) is defined as a plurality of consecutive RBs (e.g., physical RB, PRB) in the frequency domain, and may correspond to one OFDM numerology (e.g., SCS (u), CP length, etc.). A carrier may include a maximum of N (e.g., <NUM>) BWPs. Data communication is performed through the activated BWP, and only one BWP can be activated for one UE in one cell/carrier. Each element in the resource grid is referred to as a resource element (RE), and one modulation symbol may be mapped.

In a wireless communication system, the UE receives information through downlink (DL) from the base station and the UE transmits information through uplink (UL) to the base station. Information transmitted and received between the base station and the UE includes data and various control information, and various physical channels/signals exist according to the type/use of the information they transmit and receive. A physical channel corresponds to a set of resource elements (REs) carrying information derived from a higher layer. A physical signal corresponds to a set of resource elements (RE) used by the physical layer (PHY), but does not carry information derived 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.

DL physical channel includes PBCH(Physical Broadcast Channel), PDSCH (Physical Downlink Shared Channel) and PDCCH (Physical Downlink Control Channel). DL physical signal includes DL RS (Reference Signal), PSS(Primary synchronization signal) and SSS(Secondary synchronization signal). DL reference signal (RS) includes DM-RS(Demodulation RS), PT-RS(Phase-tracking RS) and CSI-RS(Channel-state information RS). UL physical channel includes PRACH (Physical Random Access Channel), PUSCH (Physical Uplink Shared Channel) and PUCCH(Physical Uplink Control Channel). UL physical signal includes UL RS. UL RS includes DM-RS, PT-RS and SRS(Sounding RS).

<FIG> illustrates an example in which a physical channel is mapped in a slot.

A DL control channel, DL or UL data, UL control channel, etc. may all be included in one slot. For example, the first N symbols in a slot may be used to transmit a DL control channel (hereinafter, DL control region), and the last M symbols in a slot may be used to transmit a UL control channel (hereinafter, UL control region). N and M are each an integer greater than or equal to <NUM>. A resource region (hereinafter, referred to as a data region) between the DL control region and the UL control region may be used for DL data transmission or for UL data transmission. A time gap for DL-to-UL or UL-to-DL switching may exist between the control region and the data region. The PDCCH may be transmitted in the DL control region, and the PDSCH may be transmitted in the DL data region. Some symbols at the time of switching from DL to UL in a slot may be used as a time gap.

In this present disclosure, the base station may be, for example, gNodeB.

PDSCH carries a DL-shared transport block (DL-SCH TB). TB is coded as CodeWord (CW) and then transmitted through a scrambling and modulation procedures. CW includes one or more code blocks (CBs). The one or more CBs are grouped into one CBG (CB group). According to configuration of the cell, PDSCH carry can carry up to two CWs. Scrambling and modulation are performed for each CW, and modulation symbols generated from each CW are mapped to one or more layers. Each layer is mapped to a resource together with DMRS through precoding, and transmitted through a corresponding antenna port. The PDSCH may be dynamically scheduled by the PDCCH or semi-statically (configured scheduling, CS) based on higher layer (e.g., RRC) signaling (and/or Layer <NUM> (L1) signaling (e.g., PDCCH)). Accordingly, in dynamic scheduling, PDSCH transmission is accompanied by a PDCCH, but in CS, PDSCH transmission is not accompanied by a PDCCH. CS includes semi-persistent scheduling (SPS).

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 on PCH (paging channel), system information on DL-SCH, random access response transmitted on PDSCH Frequency /time resource allocation information for higher layer control messages such as (RAR), transmit power control commands, and information on activation/deactivation of SPS/CS (Configured Scheduling). Various DCI formats are provided according to information in the DCI.

Table <NUM> illustrates DCI formats transmitted through the PDCCH.

DCI format 0_0 may be used to schedule a TB-based (or TB-level) PUSCH, andDCI format 0_1 may be used to schedule a TB-based (or TB-level) PUSCH or a CBG (Code Block Group) -based (or CBG-level) PUSCH. DCI format 1_0 may be used to schedule a TB-based (or TB-level) PDSCH, and DCI format 1_1 (DL grant DCI) may be used to schedule a TB-based (or TB-level) PDSCH or a CBG-based (or CBG-level) PDSCH. DCI format 0_0/0_1 may be referred to as UL grant DCI or UL scheduling information, and DCI format 1_0/1_1 may be referred to as DL grant DCI or UL scheduling information. DCI format 2_0 may be used to deliver dynamic slot format information (e.g., dynamic SFI) to the UE, and DCI format 2_1 may be used to deliver downlink pre-emption information to the UE. DCI format 2_0 and/or DCI format 2_1 may be delivered to the UEs in a corresponding group through a group common PDCCH (Group common PDCCH), which is a PDCCH delivered to the UEs defined as one group.

PDCCH/DCI includes a cyclic redundancy check (CRC), and the CRC is masked/scrambled with various identifiers (e.g., Radio Network Temporary Identifier, RNTI) according to the owner or use purpose of the PDCCH. For example, if the PDCCH is for a specific UE, the CRC is masked with a C-RNTI (Cell-RNTI). If the PDCCH relates to paging, the CRC is masked with a Paging-RNTI (P-RNTI). If the PDCCH relates to system information (e.g., System Information Block, SIB), the CRC is masked with a System Information RNTI (SI-RNTI). If the PDCCH relates to a random access response, the CRC is masked with a random access-RNTI (RA-RNTI).

Table <NUM> illustrates the use and transport channel of the PDCCH according to the RNTI. The transport channel indicates a transport channel related to data carried by a PDSCH/PUSCH scheduled by the PDCCH.

The modulation method of the PDCCH is fixed (e.g., Quadrature Phase Shift Keying, QPSK), and one PDCCH is <NUM>, <NUM>, <NUM>, <NUM>, <NUM> CCE (Control Channel Element), and one PDCCH is composed of <NUM>, <NUM>, <NUM>, <NUM>, or <NUM> CCEs (Control Channel Elements) according to an Aggregation Level (AL). One CCE consists of six REGs (Resource Element Groups). One REG is defined as one OFDMA symbol and one (P)RB.

A PDCCH is transmitted through a CORESET (Control Resource Set). A CORESET corresponds to a set of physical resources/parameters used to carry PDCCH/DCI within the BWP. For example, the CORESET contains a REG set with a given numerology (e.g., SCS, CP length, etc.). The CORESET may be configured through system information (e.g., MIB) or UE-specific higher layer (e.g., RRC) signaling. Examples of parameters/information used to configure the CORESET are as follows. One or more CORESETs are configured for one UE, and a plurality of CORESETs may overlap in the time/frequency domain.

For PDCCH reception, the UE may monitor a set of PDCCH candidates (e.g., blind decoding) in CORESET. The PDCCH candidate indicates CCE(s) monitored by the UE for PDCCH reception/detection. PDCCH monitoring may be performed in one or more CORESETs on active DL BWPs on each activated cell in which PDCCH monitoring is configured. The set of PDCCH candidates monitored by the UE is defined as a PDCCH search space (SS) set. The SS set may be a Common Search Space (CSS) set or a UE-specific Search Space (USS) set.

Table <NUM> exemplifies a PDCCH search space.

A SS set may be configured through system information (e.g., MIB) or UE-specific higher layer (e.g., RRC) signaling. S (e.g., <NUM>) or less SS sets may be configured in each DL BWP of the serving cell. For example, the following parameters/information may be provided for each SS set. Each SS set is associated with one CORESET, and each CORESET configuration may be associated with one or more SS sets.

Based on the CORESET / SS set configuration, the UE may monitor PDCCH candidates in one or more SS sets in the slot. An occasion (e.g., time/frequency resource) to monitor PDCCH candidates is defined as a PDCCH (monitoring) occasion. One or more PDCCH (monitoring) occasions may be configured within a slot.

A PUSCH carries uplink data (e.g., UL-SCH TB) and/or uplink control information (UC) and is transmitted based on CP-OFDM(Cyclic Prefix-Orthogonal Frequency Division Multiplexing) waveform or DFT-s-OFDM(Discrete Fourier Transform-spread-OFDM) 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 a PUSCH based on the CP-OFDM waveform, and when transform precoding is possible (e.g., transform precoding is enabled), the UE transmits the CP-OFDM PUSCH may be transmitted based on a waveform or a DFT-s-OFDM waveform. PUSCH may be dynamically scheduled by PDCCH or semi-statically scheduled based on a higher layer (e.g., RRC) signaling (and/or Layer <NUM> (L1) signaling (e.g., PDCCH))(configured Scheduling, CS). Accordingly, in dynamic scheduling, PUSCH transmission is accompanied by a PDCCH, but in CS, PUSCH transmission is not accompanied by a PDCCH. CS includes Type-<NUM> CG (Configured Grant) PUSCH transmission and Type-<NUM> CG PUSCH transmission. In Type-<NUM> CG, all parameters for PUSCH transmission are signaled by a higher layer. In Type-<NUM> CG, some of the parameters for PUSCH transmission are signaled by a higher layer, and the rest are signaled by the PDCCH. Basically, in CS, PDCCH is not accompanied by PUSCH transmission.

A PUCCH carries uplink control information (UCI). The UCI includes:.

CSI (Channel status information) : it is feedback information related to DL channels. The CSI includes CQI(Channel Quality Information), RI(Rank Indicator), PMI(Precoding Matrix Indicator), and PTI(Precoding Type Indicator).

Table <NUM> exemplifies PUCCH formats. The PUCCH format may 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 may be classified into Short PUCCH (format <NUM>, <NUM>) and Long PUCCH (format <NUM>, <NUM>, <NUM>) according to a transmission length.

<FIG> exemplifies ACK/NACK transmission procedure. Referring to <FIG>, the UE may detect the PDCCH in slot #n. Here, the PDCCH includes downlink scheduling information (e.g., DCI formats 1_0 and 1_1), and the PDCCH indicates a DL assignment-to-PDSCH offset (K0) and a PDSCH-HARQ-ACK reporting offset (K1). For example, DCI formats 1_0 and 1_1 may include the following information.

Thereafter, the UE may transmit the UCI through the PUCCH in the slot #(n+K1) after receiving the PDSCH in the slot #(n+K0) according to the scheduling information of the slot #n. Here, the UCI includes a HARQ-ACK response for the PDSCH. If the PDSCH is configured to transmit up to <NUM> TB, the HARQ-ACK response may be configured with <NUM>-bit. When the PDSCH is configured to transmit up to two TBs, the HARQ-ACK response may be configured with <NUM>-bits when spatial bundling is not configured, and may be configured with <NUM>-bits when spatial bundling is configured. When the HARQ-ACK transmission time for the plurality of PDSCHs is designated as slot #(n+K1), the UCI transmitted in the slot #(n+K1) includes HARQ-ACK responses for the plurality of PDSCHs.

<FIG> illustrates an example of a wireless communication system supporting the unlicensed band to which the present disclosure is applicable.

In the following description, a cell operating in a licensed band (L-band) is defined as an L-cell, and a carrier of the L-cell is defined as (DL/UL) LCC (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 (DL/UL) UCC. The carrier/carrier-frequency of the cell may refer to an operating frequency (e.g., center frequency) of the cell. A cell/carrier (e.g., CC) is collectively referred to as a cell.

When the UE and the base station transmit and receive signals through the carrier combined LCC and UCC, as shown in <FIG>, the LCC may be configured to PCC (Primary CC) and UCC may be configured to SCC (Secondary CC). As shown in <FIG> , the UE and the base station may transmit and receive signals through one UCC or a plurality of carrier-coupled UCCs. That is, the UE and the base station may transmit and receive signals through only UCC(s) without LCC. For standalone operation, PRACH, PUCCH, PUSCH, SRS transmission, etc. may be supported in the Ucell.

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

Unless otherwise stated, the following definitions may be applied to terms used in this specification.

<FIG> illustrates a method of occupying resources in an unlicensed band. According to regional regulation on unlicensed bands, communication nodes within unlicensed bands must determine whether other communication nodes use channels before transmitting signals. Specifically, the communication nodes may check whether other communication nodes transmit a signal by first performing carrier sensing (CS) before signal transmission. A case in which it is determined that other communication nodes do not transmit a signal is defined as CCA (Clear Channel Assessment) has been confirmed. If there is a CCA threshold configured by predefined or higher layer (e.g., RRC) signaling, the communication nodes may determine the channel state as busy if energy higher than the CCA threshold is detected in the channel, otherwise the channel state may be considered as idle. For reference, in the Wi-Fi standard (<NUM>. 11ac), the CCA threshold is defined as -<NUM> dBm for a non-Wi-Fi signal and -<NUM> dBm for a Wi-Fi signal. If it is determined that the channel state is in an idle state, the communication nodes may start transmitting a signal in the Ucell. The above-described series of procedures may be referred to as LBT (Listen-Before-Talk) or CAP (Channel Access Procedure). LBT, CAP, and CCA may be expressed interchangeably.

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

The base station may perform one of the following unlicensed band access procedures (e.g., Channel Access Procedure, CAP) for downlink signal transmission in the unlicensed band.

The length of the time duration spanned by the sensing slot sensed as idle before transmission (s) in the type <NUM> DL CAP is random. Type <NUM> DL CAP may be applied to the following transmission.

<FIG> is a CAP operation flowchart for downlink signal transmission through the unlicensed band of the base station.

Referring to <FIG>, the base station may first sense whether the channel is in an idle state during the sensing slot period of the defer duration Td, and then when the counter N becomes <NUM>, transmission may be performed (S1234). At this time, the counter N is adjusted by sensing the channel during additional sensing slot period(s) according to procedure below:.

Table <NUM> shows that mp applied to CAP, minimum contention window (CW), maximum CW, maximum channel occupancy time (MCOT) and allowed CW sizes vary according to the channel access priority class.

The defer duration Td is configured in the order of the period Tf (<NUM>) + mp consecutive sensing slot period Tsl (<NUM>). Tf includes the sensing slot period Tsl at the start time of the <NUM> period.

CWmin,p <= CWp <= CWmax,p. CWp may be configured as CWp = CWmin,p, and may be updated before step <NUM> based on HARQ-ACK feedback (e.g., ACK or NACK ratio) for the previous DL burst (e.g., PDSCH) (CW size update). For example, CWp may be initialized to CWmin,p based on the HARQ-ACK feedback for the previous DL burst, may be increased to the next highest allowed value, or the existing value may be maintained.

The length of time duration spanned by the sensing slot sensed as idle before transmission (s) in the type <NUM> DL CAP is deterministic (deterministic). Type <NUM> DL CAPs are classified into Type 2A/2B/2C DL CAPs.

Type 2A DL CAP may be applied to the following transmission. In Type 2A DL CAP, the base station may transmit transmission immediately after the channel is sensed as idle for at least the sensing period Tshort_dl=<NUM>. Here, Tshort_dl consists of a period Tf (=<NUM>) and one sensing slot period immediately following. Tf includes a sensing slot at the beginning of the duration.

Type 2B DL CAP may be applicable to transmission (s) performed by the base station after a <NUM> gap from the transmission (s) by the UE within the shared channel occupation time. In Type 2B DL CAP, the base station may transmit transmission immediately after the channel is sensed as idle for Tf=<NUM>. Tf includes a sensing slot within the last <NUM> of the duration. Type 2C DL CAP may be applicable to transmission (s) performed by the base station after a maximum of <NUM> gap from transmission (s) by the UE within the shared channel occupation time. In Type 2C DL CAP, the base station does not sense the channel before performing transmission.

The UE performs a Type <NUM> or Type <NUM> CAP for uplink signal transmission in the unlicensed band. In general, the UE may perform a CAP (e.g., type <NUM> or type <NUM>) configured by the base station for uplink signal transmission. For example, the UE may include CAP type indication information in a UL grant (e.g., DCI formats 0_0, 0_1) for scheduling PUSCH transmission.

The length of time duration spanned by the sensing slot sensed as idle before transmission (s) in the type <NUM> DL CAP is random. Type <NUM> UL CAP may be applied to the following transmission.

<FIG> is a flow chart of the Type <NUM> CAP operation of the UE for uplink signal transmission.

Referring to <FIG>, the UE first may sense whether the channel is in an idle state during the sensing slot period of the defer duration Td, and then when the counter N becomes <NUM>, transmission may be performed (S1534). At this time, the counter N is adjusted by sensing the channel during the additional sensing slot period(s) according to the procedure below:.

CWmin,p <= CWp <= CWmax,p. CWp is configured as CWp = CWmin,p, and may be updated before step <NUM> based on an explicit/implicit reception response to a previous UL burst (e.g., PUSCH) (CW size update). For example, CWp may be initialized to CWmin,p based on an explicit/implicit reception response to the previous UL burst, may be increased to the next highest allowed value, or the existing value may be maintained.

The length of the time duration spanned by a sensing slot sensed as idle before transmission (s) in a Type <NUM> UL CAP is deterministic (deterministic). Type <NUM> UL CAPs are classified into Type 2A/2B/2C UL CAPs. In Type 2A UL CAP, the UE may transmit transmission immediately after the channel is sensed as idle for at least the sensing period Tshort_dl=<NUM>. Here, Tshort_dl consists of a section Tf (=<NUM>) and one sensing slot period immediately following. In Type 2AULCAP, Tf includes a sensing slot at the beginning of the duration. In Type 2B UL CAP, the UE may transmit transmission immediately after the channel is sensed as idle for the sensing period Tf=<NUM>. In Type 2B UL CAP, Tf includes a sensing slot within the last <NUM> of the duration. In Type 2C UL CAP, the UE does not sense a channel before performing transmission.

<FIG> illustrates an RB interlace. In the shared spectrum, in consideration of OCB (Occupied Channel Bandwidth) and PSD (Power Spectral Density) related regulations, a set of (single) discontinuous (single) RBs (at equal intervals) on a frequency may be defined as a unit resource used/allocated for UL (physical) channel/signal transmission. Such a discontinuous RB set is defined as "RB interlace" (simply, interlace) for convenience.

Referring to <FIG>, a plurality of RB interlaces (simply, interlaces) may be defined within a frequency band. Here, the frequency band may include a (wideband) cell/CC/BWP/RB set, and the RB may include a PRB. For example, interlace #m∈{<NUM>, <NUM>,. , M-<NUM>} may consist of (common) RB {m, M+m, <NUM>+m, <NUM>+m,. M represents the number of interlaces. A transmitter (e.g., a UE) may transmit a signal/channel using one or more interlaces. The signal/channel may include PUCCH or PUSCH.

<FIG> shows a random access procedure. <FIG> shows a contention-based random access procedure, and <FIG> illustrates a dedicated random access procedure.

Referring to <FIG>, the contention-based random access procedure includes the following steps. Hereinafter, the message transmitted in steps <NUM> to <NUM> may be referred to as messages (Msg) <NUM> to <NUM>, respectively.

The UE may receive information on the random access from the base station through system information.

If random access is required, the UE transmits the RACH preamble to the base station as in step <NUM>. The base station may distinguish each random access preamble through a time/frequency resource (RACH Occasion; RO) and a random access preamble index (PI) in which the random access preamble is transmitted.

When the base station receives the random access preamble from the UE, the base station transmits the random access response (RAR) message to the UE as in step <NUM>. For the reception of the random access message, the UE monitors the L1/L2 control channel (PDCCH) with CRC masked by RA-RNTI (random access-RNTI), including scheduling information on a random access response message, within a preconfigured time window(e.g., ra-ResponseWindow). PDCCH masked with RA-RNTI may be transmitted only through a common search space. When receiving the scheduling signal masked by the RA-RNTI, the UE may 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 or not random access response information indicated to itself exists may be checked by whether a random access preamble ID (RAPID) for a preamble transmitted by the UE exists. The index and RAPID of the preamble transmitted by the UE may be the same. The random access response information includes a corresponding random access preamble index, timing offset information for UL synchronization (e.g., Timing Advance Command, TAC), UL scheduling information for message <NUM> transmission (e.g., UL grant) and terminal temporary identification information (e.g., Temporary-C-RNTI, TC-RNTI).

The UE receiving the random access response information, as in step <NUM>, transmits UL-SCH (shared channel) data (message <NUM>) through the PUSCH according to the UL scheduling information and the timing offset value. The message <NUM> may include the ID of the UE (or, the global ID of the UE). Alternatively, the message <NUM> may include information related to RRC connection request (e.g., RRCSetupRequest message) for initial access. In addition, the message <NUM> may include a buffer status report (BSR) on the amount of data available for transmission by the UE.

After receiving UL-SCH data, as in step <NUM>, the base station transmits a contention resolution message (message <NUM>) to the UE. When the UE receives the contention resolution message and the contention is resolved successfully, the TC-RNTI is changed to the C-RNTI. Message <NUM> may include the ID of the UE and/or RRC connection related information (e.g., an RRCSetup message). If the information transmitted through the message <NUM> and the information received through the message <NUM> do not match, or if the message <NUM> is not received for a certain period of time, the UE may retransmit the message <NUM> as the contention resolution has failed.

Referring to <FIG>, the dedicated random access procedure includes the following <NUM> steps. Hereinafter, the messages transmitted in steps <NUM> to <NUM> may be referred to as messages (Msg) <NUM> to <NUM>, respectively. The dedicated random access procedure may be triggered using a PDCCH (hereinafter referred to as a PDCCH order) for instructing the base station to transmit the RACH preamble.

Operations of steps <NUM> and <NUM> of the dedicated random access procedure may be the same as step <NUM> and <NUM> of the contention-based random access procedure.

In NR, DCI format 1_0 is used to initiate a non-contention-based random access process with a PDCCH command (order). DCI format 1_0 is used to schedule a 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 assignment" field are <NUM>, DCI format 1_0 is used as a PDCCH order indicating a random access procedure. In this case, the field of DCI format 1_0 is configured as follows.

When the DCI format 1_0 does not correspond to the PDCCH order, the DCI format 1_0 consists of fields used to schedule the PDSCH (e.g., time domain resource assignment, MCS(Modulation and Coding Scheme), HARQ process number, PDSCH-to-HARQ_feedback timing indicator and the like).

As described above, the conventional random access goes through a four-step procedure. In the conventional LTE system, as shown in Table <NUM>, an average of <NUM> was required for the four-step random access procedure.

In NR system, lower latency than the existing system may be required. In addition, if the random access procedure occurs in the U-band, the random access procedure is terminated and contention is resolved only when the UE and the base station sequentially succeed in LBT in both the <NUM>-step random access procedure. If the LBT fails even in one step of the <NUM>-step random access procedure, resource efficiency is reduced and latency is increased. In particular, if the LBT fails in the scheduling/transmission procedure associated with message <NUM> or message <NUM>, a decrease in resource efficiency and an increase in latency may occur significantly. Even a random access procedure in the L-band may require a low-latency random access process in various scenarios of an NR system. Accordingly, the <NUM>-step random access procedure may be performed on the L-band as well.

As shown in <FIG>, the <NUM>-step random access procedure may consist of two steps of uplink signal (referred to as message A) transmission from the UE to the base station and downlink signal (referred to as message B) transmission from the base station to the UE.

The following description focuses on the initial access process, but the following proposed method may be equally applied to the random access process after the RRC connection between the UE and the base station is made. Also, in the non-contention random access process, as shown in <FIG> , the random access preamble and the PUSCH part may be transmitted together.

Although not shown, a PDCCH for scheduling message B may be transmitted from the base station to the terminal, which is Msg. It may be referred to as B PDCCH.

The above-mentioned contents (3GPP system(or NR system), frame structure, etc.) may be applied in combination with the methods proposed in the present disclosure to be described later, or the technical characteristics of the methods proposed in the present disclosure may be clearly described may be supplemented.

As described above, in the Wi-Fi standard (<NUM>. 11ac), the CCA threshold is defined as -<NUM> dBm for a non-Wi-Fi signal and -<NUM> dBm for a Wi-Fi signal. In other words, when a signal from a device not belonging to the Wi-Fi system is received with a power of -<NUM> dBm or higher in a specific band, the STA (Station) or AP (Access Point) of the Wi-Fi system does not transmit signals in the specific band.

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 length <NUM> sequence. The PRACH corresponding to the Short RACH format consists of a <NUM>-length sequence. Hereinafter, a structure of a sequence constituted by the Short RACH format is proposed. In the FR1 (Frequency Range <NUM>) band of less than <NUM>, the SCS of the Short RACH format corresponds to <NUM> and/or <NUM>. The PRACH corresponding to the Short RACH format may be transmitted through <NUM> RBs as shown in <FIG>. <FIG> RBs include <NUM> REs, and PRACH may be transmitted on <NUM> tones (<NUM> REs) of <NUM> REs. In <FIG>, two REs in the order of the lowest index and three REs in the order of the highest index of the <NUM> REs correspond to null tones, but the positions of the null tones may be different from those shown in <FIG>.

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.

The short PRACH format may consist of values defined in Table <NUM>.

In the Table <NUM>, LRA is the length of sequence, ΔfRA is the SCS applied to RACH, AND k is Ts/Tc=<NUM>. As µ∈ {<NUM>,<NUM>,<NUM>,<NUM>}, µ is determined as one of <NUM>, <NUM>, <NUM>, and <NUM> according to the SCS value. For example, µ is set to <NUM> for <NUM> SCS, and µ is set to <NUM> for <NUM> SCS.

The base station may inform, through higher layer signaling, which the PRACH format can be transmitted at a specific timing for a specific period (duration), and up to how many Ros are in the corresponding slot. Table <NUM>. <NUM>-<NUM> to Table <NUM>. <NUM>-<NUM> of the <NUM> standard correspond to this. Table <NUM> shows only a few specific excerpts from the indexes that may use A1, A2, A3, B1, B2, B3 alone or in combination in Table <NUM>. <NUM>-<NUM> of the <NUM> standard.

As shown in <FIG>, it may to know how many Ros are defined in the RACH slot for each preamble format (the number of time-domain PRACH occasions within a PRACH slot of Table <NUM>) and how many OFDM (orthogonal frequency-division multiplexing) symbols are occupied (PRACH duration of Table <NUM>) by the PRACH preamble of each preamble format (PRACH duration in Table <NUM>). In addition, since the starting symbol of the first RO may be indicated for each preamble format, information on from which point in the corresponding RACH slot the RO starts may be transmitted/received between the base station and the UE. <FIG> shows a configuration of an RO in a RACH slot for each PRACH configuration index value of Table <NUM>.

On the other hand, the device operating in the unlicensed band checks whether a channel to transmit a signal is in an idle state or a busy state. When a channel is in an idle state, a signal is transmitted through the corresponding channel. When the channel is in the busy state, the device to transmit the signal waits until the channel becomes the idle state before transmitting the signal. As previously described through <FIG> and <FIG>, such an operation may be referred to as an LBT or channel access scheme. In addition, there may be LBT categories (category) as shown in Table <NUM>.

LBT corresponding to category <NUM> is a method of accessing a channel without LBT. According to the LBT corresponding to the specific category <NUM>, after the specific node occupies the channel, if the time interval until just before the next transmission is less than <NUM> the specific node may access the channel regardless of the state. Next, category <NUM> LBT is a method of accessing a channel after performing one-shot LBT without a back-off counter value. According to the LBT corresponding to category <NUM>, a specific node performs transmission after determining whether a channel is idle for <NUM> (or <NUM>).

For LBT corresponding to the category <NUM> and the category <NUM>, a backoff counter value is randomly selected within a contention window (CW). In this present disclosure, the LBT corresponding to the category <NUM> may be referred to as a Cat <NUM> LBT, and the LBT corresponding to the category <NUM> may be referred to as Cat <NUM> LBT. For the LBT corresponding to the category <NUM>, a back-off counter value is selected randomly based on the always fixed contention window size value. For the LBT corresponding to the category <NUM>, the contention window size value is increased by <NUM> step in the allowed candidates each time the LBT fails, starting from the first minimum contention window size value. Candidates for the maximum value, the minimum value, and the allowed contention window size value of the contention window size are predefined for each channel access priority class (see Tables <NUM> and <NUM>). For example, for Cat <NUM> LBT having a channel access priority class of <NUM>, the UE initially selects a backoff counter value randomly from <NUM> to <NUM>. If the UE fails the LBT, the UE randomly selects a backoff counter value from <NUM> to <NUM>.

The LBT corresponding to the LBT may include a type 2C DL CAP and a type 2C UL CAP as described above. The LBT corresponding to the category <NUM> may include a type 2A DL CAP, a type 2B DL CAP, and a type 2B UL CAP. The LBT corresponding to the category <NUM> may include a type <NUM> DL CAP and a type <NUM> UL CAP.

The UE selecting the back-off counter value based the values defined in Table <NUM>, if the channel is idle for <NUM>+<NUM>×mp+K×<NUM>, performs an uplink transmission indicated and/or configured from the base station. K is the selected backoff counter value, and mp corresponds to the slot time applied according to the channel access priority class. The channel access priority class and LBT category for PRACH transmission may be as shown in Table <NUM>.

Based on the values that can be derived through Tables <NUM> and <NUM>, the UE may start PRACH transmission if the channel is idle for <NUM>+<NUM>*<NUM> + K*<NUM> = <NUM> + K*<NUM> (us). As described above, the backoff counter value K is randomly selected within the size-varying contention window size value.

The above-described <NUM>-step random access procedure consist of transmission of message A (Msg. A; PRACH preamble and Msg. <NUM> PUSCH) of the UE, and transmission of message B (Msg. B; RAR and Msg. <NUM> PDSCH) of the base station. For convenience of description, in the present disclosure, the time and frequency resource to which the PRACH preamble signal of Msg. A is mapped/transmitted is defined as RO (RACH Occasion), and the time and frequency resource to which a Msg. <NUM> PUSCH signal is mapped/transmitted is defined as PO (PUSCH Occasion). Hereinafter, 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. <NUM> PUSCH constituting Msg. A may be referred to as Msg. The RAR constituting Msg. B may be referred to as Msg. <NUM> PDSCH constituting Msg. B may be referred to as The Msg.

In particular, in NR-U, the operation for the UE's channel access procedure (channel access procedure) to transmit Msg. A in the RO and PO needs to be defined. Accordingly, the present disclosure proposes a channel access procedure according to time/frequency resources of RO and PO and a timing gap between RO and PO. For convenience of description, parameters for time/frequency resources of RO and PO and a time interval between RO and PO are defined as shown in <FIG>. That is, according to <FIG>, T1 means a time duration of RO, T2 means a time duration of PO, T means T1+T2, F1 means a frequency bandwidth of RO, F2 means a frequency band of PO, and P1 means a time interval between RO and PO.

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

(<NUM>) First, the UE receives control information related to the RO and/or PO from the base station. Here, the control information may include parameters shown in <FIG>. (<NUM>) Next, the UE determines the LBT type to be performed in front of the RO and/or PO based on the control information. (<NUM>) Next, the UE transmits an Msg. A preamble and/or Msg. A PUSCH in the RO and/or PO based on the determined LBT type.

For more detailed information, refer to methods to be described later. That is, the methods to be described later may be combined with the procedures of (<NUM>) to (<NUM>) above to achieve the object/effect proposed in the present disclosure. In addition, the methods to be described later may be combined with the procedure described in the <NUM> random access process to achieve the object/effect proposed in the present disclosure. In this present disclosure, 'unlicensed band' may be substituted and mixed with `shared spectrum'. Also, in this present disclosure, 'LBT type' may be substituted and mixed with 'channel access type'. 'LBT' may be substituted and mixed with 'channel access'.

As a first method, a channel access operation for a method in which the UE considers channel occupancy (CO) sharing for Msg. A preamble and Msg. A PUSCH transmission is as follows. At this time, the reason for considering the CO sharing is that if the CO sharing is not performed, Cat-<NUM> LBT (random back-off based) must be performed before all transmissions. That is, through the CO sharing, the LBT process other than the first LBT process may be Cat-<NUM> LBT (no LBT) or Cat-<NUM> LBT (one shot LBT). Therefore, channel access may be performed more quickly and easily. The parameters used in the following description are shown in <FIG>.

Referring to Table <NUM>, the CO sharing time (Tulmcotp) is defined according to priority class (PC). That is, if the PC is <NUM>, the CO sharing time is <NUM> or less, if the PC is <NUM>, the CO sharing time is <NUM> or less, and if the PC is <NUM> or <NUM>, the CO sharing time is <NUM> or <NUM> or less (whether <NUM> or <NUM> is determined by higher layer signaling). Therefore, the next operation may be divided into the following three durations according to the CO sharing time and PC.

For each duration defined above, the UE may perform the following operation.

Characteristically, an upper limit of PI that may perform Cat-<NUM> LBT may be configured. The base station may configure the upper limit of P1 that may perform Cat-<NUM> LBT to the UE through higher layer signaling (e.g., SIB or RMSI, etc.) (or defined in the specification), and the UE may determine the LBT type by comparing the upper limit value of the P1 with the current P1 value and perform a channel access procedure. For example, if the upper limit of the P1 that may perform Cat-<NUM> LBT is P1MAX, if the P1 is smaller than P1MAX, the UE may perform Cat-<NUM> LBT in front of the PO. If the P1 is greater than P1MAX, the UE may perform Cat-<NUM> LBT in front of the PO. In this case, the priority class PCPO (e.g., PCPO may be the same as PCRO) used by the UE may be promised in advance, or may be indicated by the base station through higher layer signaling (e.g., SIB or RMSI, etc.).

The base station may also indicate whether the CO sharing is allowed through higher layer signaling (e.g., SIB or RMSI, etc.).

<NUM>-<NUM>. The operation of embodiment <NUM> may be applied when F1 and F2 exist in the same LBT sub-band, and/or when F1 includes F2.

A proposal of a channel access operation for a method in which the UE does not 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>. Also in embodiment <NUM>, the following three time duration, described in Embodiment <NUM>, may be applied.

<NUM>-<NUM>. For each duration, even if T is greater than the maximum value of each duration (because CO sharing is not considered), the UE performs Cat-<NUM> LBT using the priority class PCRO in front of Msg. A preamble RO. The maximum value of each duration may be, for example, <NUM> in Duration <NUM>, <NUM> in Duration <NUM>, and <NUM> (or <NUM>) in Duration <NUM>. PCRO may be <NUM> when T is greater than <NUM>, PCRO may be <NUM> or <NUM> when T is greater than <NUM>, and PCRO may be <NUM>, <NUM>, <NUM>, or <NUM> when T is greater than <NUM> (or <NUM>). After successful LBT, the UE transmits Msg. A preamble,.

<NUM>-<NUM>-A. (Because CO sharing is not considered), the UE performs Cat-<NUM> LBT in front of the PO. The priority class, PCPO (e.g., PCPO may be the same as PCRO) used by the UE performing Cat-<NUM> LBT in front of the PO may be promised in advance, or may be indicated by the base station through higher layer signaling (e.g., SIB or RMSI, etc.).

<NUM>-<NUM>. Additionally, F1 and F2 do not exist in the same LBT sub-band, and/or F1 does not include F2, the UE is configured to perform Cat-<NUM> LBT in front of PO.

If the FBE (frame based equipment) configuration or the LBT before the RO is configured to Cat-<NUM> LBT, the LBT before the PO may be also configured to Cat <NUM>-LBT or configured to apply the same rule as RO.

Next, upon receiving a message (e.g., RRC connection setup, 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 transmit an A/N feedback (e.g., ACK) for it. In front of the PUCCH resource for A/N feedback transmission, the UE needs to perform LBT, and a method of determining the corresponding LBT type may be as follows.

When configured in this way, among the UEs receiving the corresponding Msg. B, the UE that needs to transmit the A / N feedback may be instructed with the same LBT type through the corresponding PDCCH (e.g., specific DCI field), and may perform a channel access procedure using the indicated LBT type (e.g., Cat-<NUM> LBT).

If the base station divides the UE into N (e.g., N=<NUM>) groups through a specification criteria, and indicates different LBT types to the N (e.g., N=<NUM>) groups for a specific reason (e.g., whether the base station successfully received Msg B), the LBT type corresponding to each group is used. UEs belonging to a specific group may perform a channel access procedure using the same LBT type.

Different LBT types may be indicated using an independent DCI field and the like. If the base station indicates the LBT type for one group through a specific DCI field, the LBT type of the other group may be determined as the LBT type promised in advance according to the indicated DCI field.

<NUM>-<NUM>-B. Opt2) the base station indicates the LTB type in common to all UEs (or, group of UE), by adding a common field to the PDSCH(e.g., the header part of MAC CE) carrying Msg.

If configured as <NUM>-<NUM>-B, among the UEs receiving Msg. B, the UE that needs to transmit A/N feedback for it may receive the same LBT type indication through the PDSCH (e.g., the header part of MAC CE) of Msg. B, and may perform channel access procedure using the indicated LBT type (e.g., Cat-<NUM> LBT).

If the base station divides the UE into N (e.g., N=<NUM>) groups through a specific criterion, and indicates different LBT types to the N (e.g., N=<NUM>) groups for a specific reason (e.g., whether the base station successfully received Msg B), the LBT type corresponding to each group is used. UEs belonging to a specific group may perform a channel access procedure using the same LBT type.

Different LBT types may be indicated using an independent MAC CE header field and the like. If the base station indicates the LBT type for one group through a specific MAC CE header field, the LBT type of another group may be determined as an LBT type promised in advance according to the indicated MAC CE header field.

<NUM>-<NUM>-C. Opt <NUM>) the base station indicates the LBT type common to all UEs (or group of UE) through higher layer signaling (e.g., SIB or RMSI, etc.).

If configured as <NUM>-<NUM>-C, among the UEs receiving Msg. B, the UE that needs to transmit A/N feedback for it may receive the same LBT type indication through higher layer signaling (e.g., SIB or RMSI) and perform channel access procedure using the indicated LBT type (e.g., Cat-<NUM> LBT).

If the base station divides the UE into N (e.g., N=<NUM>) groups through a specific criterion and indicates different LBT types to the N (e.g., N=<NUM>) groups for a specific reason, the LBT type corresponding to each group is used. UEs belonging to a specific group may perform a channel access procedure using the same LBT type.

Different LBT types may be indicated through independent higher layer signaling and the like. If the base station indicates the LBT type for one group through higher layer signaling, the LBT type of the other group may be determined as an LBT type promised in advance according to the indicated higher layer signaling.

If configured in this way, among the UEs receiving Msg. B, the UE that needs to transmit A/N feedback for it may receive an indication of the UE-specific LBT type for each success-RAR through the MAC CE, and may perform a channel access using the indicated LBT type. Accordingly, the UE transmits A/N feedback based on the indicated LBT type.

When the base station indicates a UE-specific LBT type for each success RAR, since the time for performing a channel access between the UEs may vary, the probability of collision between A / N transmission is reduced. However, there are disadvantages in that a resource overhead for specifically indicating a UE occurs and it is difficult to perform A/N multiplexing.

<NUM>-<NUM>. Method of indicating the LBT type to the UE receiving Msg. B in different ways depending on whether the base station has successfully received Msg.

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

Here, each option of <NUM>-<NUM> in embodiment <NUM> may be applied as a method of indicating the common LBT type.

<NUM> RAR of the conventional <NUM>-step RACH procedure is defined as shown in <FIG>.

In addition, <NUM> bits constituting the UL grant of the Msg. <NUM> RAR are defined as shown in table <NUM>-<NUM>.

Additionally, the CSI request field (CSI request field) may be used or reserved depending on whether the contention is as follows. ("In a non-contention based random access procedure, the CSI request field in the RAR UL grant indicates whether or not the UE includes an aperiodic CSI report in the corresponding PUSCH transmission according to [<NUM>, TS <NUM>]. In a contention based random access procedure, the CSI request field is reserved.

Since the LBT type of Msg. <NUM> PUSCH needs to be transmitted through the RAR, the following methods may be proposed.

Proposed method <NUM>-<NUM>-<NUM> : Method of indicating the LBT type using the reserved <NUM> bit of RAR.

When using <NUM> bit to indicate the LBT type, <NUM> bit may indicate either Cat-<NUM> LBT or Cat-<NUM> LBT.

Proposed method <NUM>-<NUM>-<NUM>: Since the CSI request field of the RAR UL grant is reserved in the contention-based RACH process, a method for indicating the LBT type using <NUM> bit of the CSI request field may be proposed.

When indicating the LBT type using <NUM> bit of the CSI request field, <NUM> bit of the CSI request field may indicate either Cat-<NUM> LBT or Cat-<NUM> LBT.

However, in the non-contention-based RACH procedure (e.g., contention free RACH), since the CSI request field is used, another proposed method may be used.

Proposed method <NUM>-<NUM>-<NUM>: Method of indicating the LBT type using a field unnecessary in the shared spectrum operation among RAR UL grants.

For example, when the frequency resource for Msg <NUM> PUSCH transmission is allocated in an interlace structure during NR-U operation, since the frequency hopping flag field does not need to be used, the LBT type may be indicated by using (reinterpreting) <NUM> bit of the frequency hopping flag field.

In the case of indicating the LBT type using <NUM> bit of the frequency hopping flag field, <NUM> bit of the frequency hopping flag field may indicate either Cat-<NUM> LBT or Cat-<NUM> LBT.

Even when the frequency resource for Msg. <NUM> PUSCH transmission during shared spectrum operation is indicated by contiguous PRB allocation of the conventional system, the LBT type may be indicated through 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.

Proposed method <NUM>-<NUM>-<NUM>: Method of indicating the LBT type using the MSB (Most Significant Bit) (or LSB; Least Significant Bit) L bit(s) of a specific field.

For example, in the PUSCH frequency resource allocation field, the number of bits used as shown in Table <NUM> varies according to the resource allocation type. Table <NUM> shows the number of bits of the frequency resource allocation field for PUSCH transmission based on the <NUM> LBT subband.

Referring to Table <NUM>, PUSCH frequency resource allocation field may be used from a maximum of <NUM> bits to a minimum of <NUM> bits.

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

For example, when the LBT type is indicated using the MSB <NUM> bit of the PUSCH frequency resource allocation field, the MSB <NUM> bit of the PUSCH frequency resource allocation field may indicate Cat-<NUM> LBT or Cat-<NUM> LBT.

As another example, when the LBT type is indicated using <NUM> bits of the MSB (or LSB) of the PUSCH frequency resource allocation field, two types of priority classes together with Cat-<NUM> LBT or Cat-<NUM> LBT (e.g. , PC0 or PC1) may be indicated.

As another example, when the LBT type is indicated using <NUM> bits of the MSB (or LSB) of the PUSCH frequency resource allocation field, four types of priority classes (e.g., one of PC0 to PC3) may be indicated together with Cat-<NUM> LBT or Cat-<NUM> LBT. Alternatively, Cat-<NUM> LBT, Cat-<NUM> LBT, Cat-<NUM> LBT and various priority classes may be combined and indicated.

Characteristically, the UE interpreting the actual PUSCH frequency resource allocation field may be configured to understand PUSCH frequency resource allocation, assuming that the MSB (or LSB) L bit value used for the LBT type is <NUM>.

Proposed method <NUM>-<NUM>-<NUM>: Method of reducing the size of a specific field by L bits and making it a field indicating the LBT type by using the reduced L bits.

<NUM>-<NUM>-<NUM>-A: During the RACH process in the shared spectrum, since the Msg <NUM> PUSCH uses the conventional RA type <NUM> (Rel-<NUM> RA Type <NUM> in Table <NUM>) or a new RA type (Rel-<NUM> Interlace level allocation in Table <NUM>), the PUSCH frequency resource allocation field may be configured to <NUM> bits. Among the <NUM> bits for the conventional PUSCH frequency resource allocation field, the remaining <NUM> bit may be configured as a field indicating the LBT type. As an example, when the LBT type is indicated using <NUM> bit MSB in the <NUM>-bit PUSCH frequency resource allocation field, Cat-<NUM> LBT or Cat-<NUM> LBT may be indicated.

<NUM>-<NUM>-<NUM>-B: Additionally, the actual PUSCH frequency resource allocation field may be configured to a less than <NUM> bits(e.g., <NUM> bit, etc.). The remaining bits among <NUM> bits for the conventional PUSCH frequency resource allocation field may be configured as a field indicating the LBT type. As an example, when the LBT type is indicated using <NUM> bits of the MSB (or LSB) in the <NUM>-bit PUSCH frequency resource allocation field, two types of priority classes (e.g., PC0 or PC1) may be indicated together with Cat-<NUM> LBT or Cat-<NUM> LBT. The UE may be configured to understand PUSCH frequency resource allocation assuming that the reduced MSB (or LSB) is <NUM>. For example, among the <NUM> bits in which the conventional PUSCH frequency resource allocation field is located in the RAR grant, <NUM> bits of MSB are used as a field indicating a channel access type, and <NUM> bits of LSB are used as a frequency resource allocation field as in the prior art, but LSB <NUM> Bits may be interpreted like a <NUM>-bit field, assuming that there are zeros of two bits before <NUM> bits. As another example, when PUSCH frequency resource allocation is performed with <NUM> bits, the UE assumes that <NUM>-bit MSB (or LSB) is <NUM>, and may be configured to understand PUSCH frequency resource allocation. Because RIV requires up to <NUM> bits, only <NUM>-<NUM> = <NUM> bit MSB (or LSB) is treated as <NUM>.

The proposed method <NUM>-<NUM>-<NUM> is additionally applied to the proposed method <NUM>-<NUM>-<NUM>, and the LBT type field and the MSB (or LSB) L-bit combination of the specific field (e.g., PUSCH frequency resource allocation field) LBT The type may be indicated.

Proposed method <NUM>-<NUM>-<NUM>: a combination of the proposedmethods of <NUM>-<NUM>-<NUM> to <NUM>-<NUM>-<NUM> may be considered.

That is, the LBT type may be indicated by a combination of reserved <NUM> bit of RAR, and/or CSI request field <NUM> bit of RAR UL grant, and/or a field not used in a shared spectrum among RAR UL grants, and/or MSB (or LSB) L bit(s) of a specific field.

Additionally, it may be considered that Msg. <NUM> does not indicate the LBT type for PUSCH transmission. As an example, when the LBT type for Msg. <NUM> PUSCH transmission is configured to LBE (load based equipment) through SIB, a default value may be configured/defined as Cat-<NUM> LBT. When the LBT type for Msg. <NUM> PUSCH transmission is configured to FBE (frame based equipment) through SIB, the default value may be configured/defined as Cat-<NUM> LBT with <NUM> usec (or with <NUM> usec).

Characteristically, when the UE is configured to LBE through SIB in the <NUM>-step RACH procedure, even if the default value of Msg. A PUSCH (or Msg. <NUM> PUSCH) transmission is configured/defined as Cat-<NUM> LBT, another category of LBT may be used according to the interval between RO-Pos as in the embodiments of the present specification. Similarly, when the UE is configured to FBE through SIB, even if the default value of Msg. A PUSCH (or Msg. <NUM> PUSCH) transmission is configured/defined as Cat-<NUM> LBT with <NUM> usec, (in the gap between RO-PO Depending) Cat-<NUM> LBT with <NUM> usec or Cat-<NUM> LBT may be used.

Additionally, not only the LBT type but also the Msg. <NUM> PUSCH start position may be additionally signaled through the RAR. This is summarized as follows.

<NUM>-<NUM>-<NUM>) when the legacy NR waveform is configured to (Msg. <NUM>) PUSCH waveform from the base station,.

<NUM>-<NUM>-<NUM>) When the interlace waveform is configured as the (Msg. <NUM>) PUSCH waveform from the base station,.

Accordingly, the LBT type indicated through the RAR grant in the previous proposed methods (suggested methods <NUM>-<NUM>-<NUM> to <NUM>-<NUM>-<NUM>, etc.) may mean a combination of LBT type or starting position or {LBT type, starting position} according to Opt <NUM> to <NUM> method of <NUM>-<NUM>-<NUM>. 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 <NUM>-bit, one of {Symbol #K, Symbol#(K-N) + <NUM>} may be indicated, or one of {Symbol #K, Symbol#(K-N) + <NUM> + TA} may be indicated. On the other hand, if the starting position is not indicated through the RAR grant and is determined as a single fixed value, the value may be defined as Symbol #K.

As described above through the proposed method <NUM>-<NUM>-<NUM>-B, when it is necessary to indicate the LBT type for Msg <NUM> transmission from the base station (e.g., for operation with shared spectrum channel access), the size of the PUSCH frequency resource allocation field of the RAR may be reduced by <NUM> bits. <NUM> bits not used as the PUSCH frequency resource allocation field may be used as a field for explicitly transmitting the LBT type. A field for transmitting the LBT type may be defined as a ChannelAccess-Cpext field. The fields of the RAR grant shown in Table <NUM> may be redefined as shown in Table <NUM>.

On the other hand, when the size (i.e., <MAT>) of the PUSCH resource allocation field becomes <NUM> (i.e., when it is necessary to indicate the LBT type for Msg <NUM> transmission from the base station), the contents of Table <NUM> below describing truncation and padding of the conventional PUSCH frequency resource allocation field may be insufficient for the UE to interpret the ChannelAccess-Cpext field and the PUSCH frequency resource allocation field.

Therefore, Table <NUM> may be modified based on the proposal of the present disclosure as follows.

<NUM>-<NUM>-<NUM>. For the operation without shared spectrum channel access, operation of conventional system. <NUM>-<NUM>-<NUM>-A. If the number of PRBs in BWP is <NUM> or less,
The UE truncates the FDRA (Frequency domain resource assignment) field to as much as its LSB <MAT>, and interprets the truncated FDRA field as an FDRA field of DCI format 0_0. <NUM>-<NUM>-<NUM>-B. If the number of PRBs in BWP is more than <NUM>,
the UE performs padding <NUM> as much as MSB <MAT> in front of the FDRA field, and interprets the extended FERA field as an FDRA field of DCI format 0_0. At this time, if the frequency hopping flag is <NUM>, NUL,hopis <NUM>, and if the frequency hopping flag is <NUM>, NUL,hop follows Table <NUM>.

<NUM>-<NUM>-<NUM>-B. End If
<NUM>-<NUM>-<NUM>. Shared spectrum channel access operation
<NUM>-<NUM>-<NUM>-A. When the higher layer parameter useInterlacePUSCH-Common is not provided (If useInterlacePUSCH-Common is not provided), that is, when continuous mapping which is uplink resource allocation type <NUM> (uplink resource allocation type <NUM>) is used,
<NUM>-<NUM>-<NUM>-A-i. If the number of PRBs <MAT>in BWP is <NUM> or less
the UE truncates the FDRA field to as much as its LSB <MAT>, and interprets the truncated FDRA field as an FDRA field of DCI format 0_0. <NUM>-<NUM>-<NUM>-A-ii. If the number of PRBs in BWP is more than <NUM>,
the UE performs padding <NUM> as much as MSB in front of the FDRA field, and interprets the extended FDRA field as an FDRA field of DCI format 0_0. At this time, if the frequency hopping flag is <NUM>, NUL,hop is <NUM>, and if the frequency hopping flag is <NUM>, NUL,hop follows Table <NUM>. <NUM>-<NUM>-<NUM>-A-iii. End If
<NUM>-<NUM>-<NUM>-A-iv. In this case, the new threshold value of <NUM> means the maximum number of PRBs of the BWP that can be transmitted in <NUM> bits when the uplink resource allocation type <NUM> (RIV) scheme is used. (<NUM>*<NUM>/<NUM> = <NUM> ≤ <NUM> = <NUM>)
<NUM>-<NUM>-<NUM>-B. If higher layer parameter useInterlacePUSCH-Common is provided, that is, when the uplink resource allocation type <NUM> which is interlace mapping is used
<NUM>-<NUM>-<NUM>-B-i. 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 transmitted in a band in which <NUM> SCS is configured (i. , µ=<NUM>), X is <NUM>, and when PUSCH is transmitted in a band in which <NUM> SCS is configured (i.e., µ=<NUM>), X is <NUM>. <NUM>-<NUM>-<NUM>-B-ii. When LBT sub-band allocation is added, the Y bit may be added in front of or rear of the X bit of FDRA field. According to the number of LBT subbands set in the BWP, Y may be determined as one of {<NUM>, <NUM>, <NUM>, <NUM>, <NUM>}.

Based on <NUM>-<NUM>-<NUM> and <NUM>-<NUM>-<NUM>, table <NUM> may be modified as shown in table <NUM>.

Additionally, when useInterlacePUSCH-Common is provided, the RAR UL grant field size may be defined/configured as follows.

Since only X bits are required for the actual FDRA, the FDRA field size is defined as X bits and the remaining bits may be used as a reserved field. In addition, the reserved field position may be immediately in front of or rear of the FDRA field, or a specific position of the RAR UL grant (e.g., the last, i.e., LSBs in RAR UL grant).

Characteristically, when the SCS for PUSCH transmission is <NUM>, X may be <NUM> bits, and when the SCS for PUSCH transmission is <NUM>, X may be <NUM> bits.

As an example, if the example in which the reserved field position is the last one is applied, each field in the RAR grant may be defined as shown in Table <NUM>.

Since only X bits are required for the actual FDRA, the FDRA field size may be defined as X bits and the remaining bits may be used as a reserved field. In addition, the reserved field position may be immediately in front of or rear of the FDRA field, or a specific position of the RAR UL grant (e.g., the last, i.e., LSBs in RAR UL grant).

At this time, since <NUM> bits are required when the SCS for PUSCH transmission is <NUM> and <NUM> bits are required when the SCS is <NUM>, X may be configured to <NUM> bits to satisfy both SCSs.

In this case, when the SCS is <NUM>, the UE may truncate the FDRA field to <NUM> bits of the LSB (or MSB) and interpret it as the FDRA field.

Y bit for LBT subband allocation may be further included in PUSCH frequency resource allocation. Accordingly, in Table <NUM> and/or Table <NUM>, the Y bit may be added to the PUSCH frequency resource allocation field and the Y bit may be omitted from the Reserved field.

The UE may perform the DRX operation while performing the procedures and/or methods described/proposed above. The DRX configured UE may reduce power consumption by discontinuously receiving the DL signal. DRX may be performed in RRC (Radio Resource Control)_IDLE state, RRC_INACTIVE state, and RRC_CONNECTED state. In RRC_IDLE state and RRC_INACTIVE state, DRX is used to receive paging signal discontinuously. Hereinafter, DRX performed in the RRC_CONNECTED state will be described (RRC_CONNECTED DRX).

<FIG> illustrates DRX cycle (RRC_CONNECTED state).

Referring to <FIG>, the DRX cycle consists of On Duration and Opportunity for DRX. The DRX cycle defines a time interval in which On Duration is periodically repeated. On Duration indicates a time period that the UE monitors to receive the PDCCH. When DRX is configured, the UE performs PDCCH monitoring during On Duration. If there is a successfully detected PDCCH during PDCCH monitoring, the UE operates an inactivity timer and maintains an awake state. On the other hand, if there is no PDCCH successfully detected during PDCCH monitoring, the UE enters a sleep state after On Duration ends. Accordingly, when DRX is configured, PDCCH monitoring/reception may be discontinuously performed in the time domain in performing the procedures and/or methods described/proposed above. For example, when DRX is configured, in the present disclosure, a PDCCH reception opportunity (e.g., a slot having a PDCCH search space) may be configured discontinuously according to the DRX configuration. On the other hand, when DRX is not configured, PDCCH monitoring/reception may be continuously performed in the time domain in performing the procedures and/or methods described/proposed above. For example, when DRX is not configured, PDCCH reception opportunities (e.g., a slot having a PDCCH search space) in the present disclosure may be continuously configured. Meanwhile, regardless of whether DRX is configured or not, PDCCH monitoring may be limited in a time interval configured as a measurement gap.

Table <NUM> shows the process of the UE related to DRX(RRC_CONNECTED state). Referring to table <NUM>, DRX configuration information is received through higher layer (e.g., RRC) signaling, and whether DRX on/off is controlled by a DRX command of MAC layer. If DRX is configured, the UE may discontinuously perform PDCCH monitoring in performing the procedures and/or methods proposed/described in the present disclosure, as illustrated in <FIG>.

Here, MAC-CellGroupConfig includes configuration information necessary to configure MAC (Medium Access Control) parameters for the cell group. MAC-CellGroupConfig may also include configuration information related to DRX. For example, MAC-CellGroupConfig may include information as follows to define DRX.

Here, if any one of drx-OnDurationTimer, drx-InactivityTimer, drx-HARQ-RTT-TimerDL, drx-HARQ-RTT-TimerDL is in operation, the UE performs PDCCH monitoring at every PDCCH occasion while maintaining the awake state.

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

<FIG> is a flowchart of a signal transmission/reception method according to embodiments of the present disclosure.

Referring to <FIG>, embodiments of the present disclosure may be performed by the UE and may include a step of receiving RAR based on a PRACH (S1701) and a step of transmitting a PUSCH based on RAR (S1703). Although not shown, the embodiment of the present disclosure performed from the standpoint of the base station may include a step of transmitting RAR based on PRACH and receiving a PUSCH based on RAR.

RAR may be configured based on the embodiment <NUM>. For example, the RAR may be a fallback RAR for message A in a <NUM>-step random access procedure. RAR may be Msg. <NUM> RAR for Msg. <NUM> PRACH in a <NUM>-step random access procedure.

The channel access type (LBT type) for PUSCH (Msg. <NUM> PUSCH) may be determined based on one or more of the methods of the proposed method <NUM>-<NUM>-<NUM> to <NUM>-<NUM>-<NUM> of the embodiment <NUM>.

Frequency resource for transmitting a PUSCH may be determined basedon FDRA (Frequency domain resource assignment) field. According to <NUM>-<NUM>-<NUM> of the present disclosure, the interpretation of the FDRA field for the PUSCH transmitted in shared spectrum may be different from the interpretation of the FDRA field for the PUSCH transmitted in non-shared spectrum.

For example, depending on whether higher layer parameter useInterlacePUSCH-Common is provided, whether the <NUM>-bit FDRA field is truncated to some of its LSBs or whether MSBs are padded in addition to the <NUM>-bit FDRA field is different, the number of X LSB and Y MSB is also different. That is, the FDRA field may be truncated to its X LSB or the FDRA field may be padded with Y MSB based on whether or not interlace allocation of PUSCH for shared spectrum channel access is provided.

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

According to <NUM>-<NUM>-<NUM>-A-i, based on the interlace allocation of PUSCH for shared spectrum channel access being not provided and the number of PRBs in the BWP being <NUM> or less, the FDRA field is truncated to its X LSB, where the X LSB is determined based on the number of PRBs in the BWP.

When the number of PRBs in BWP is <MAT>, X LSB is determined as <MAT> LSB, that is, ceil (log<NUM> (N * (N+<NUM>)/<NUM>)) LSB.

According to <NUM>-<NUM>-<NUM>-A-ii, based on the interlace allocation of PUSCH for shared spectrum channel access being not provided and the number of PRBs in the BWP being more than <NUM>, the FDRA field is padded with Y MSB, where the Y MSB is determined based on the number of PRBs in the BWP.

When the number of PRBs in BWP is <MAT>, Y MSB is determined as <MAT>, that is, ceil (log<NUM> (N * (N+<NUM>)/<NUM>))-<NUM> MSB.

The threshold value of <NUM> is determined in consideration of the maximum number of PRBs that can be indicated by <NUM> bits within the BWP when resources are allocated based on not providing interlace allocation of PUSCH for shared spectrum channel access.

According to <NUM>-<NUM>-<NUM>-B, based on the provision of interlace allocation of PUSCH for shared spectrum channel access, X LSB is determined to be <NUM> LSB for <NUM> SCS and <NUM> LSB for <NUM> SCS.

In addition to the operation described with reference to <FIG>, one or more of the operations described with reference to <FIG> and/or the operations described with respect to embodiments <NUM> to <NUM> may be combined and additionally performed. 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.

Although not limited thereto, various descriptions, functions, procedures, proposals, methods, and/or operational flowcharts of the present disclosure disclosed in this document may be applied in various fields requiring wireless communication/connection (e.g., <NUM>) between devices.

Hereinafter, it will be exemplified in more detail with reference to the drawings. In the following drawings/descriptions, the same reference numerals may represent the same or corresponding hardware blocks, software blocks, or functional blocks, unless otherwise indicated.

Referring to <FIG>, the communication system <NUM> 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., <NUM> NR (New RAT), LTE (Long Term Evolution)), and may be referred to as a communication/wireless/<NUM> device. Although not limited thereto, the wireless device includes a robot 100a, a vehicle 100b-<NUM>, 100b-<NUM>, an extended Reality (XR) device 100c, a hand-held device 100d, and a home appliance 100e, an Internet of Thing (IoT) device 100f, and an AI device/server <NUM>. For example, the vehicle may include a vehicle equipped with a wireless communication function, an autonomous driving vehicle, a vehicle capable of performing inter-vehicle communication, and the like. Here, the vehicle may include an Unmanned Aerial Vehicle (UAV) (e.g., a drone). XR devices include AR (Augmented Reality)/VR (Virtual Reality) /MR (Mixed Reality) devices, and may be implemented in the form of a Head-Mounted Device (HMD), a Head-Up Display (HUD) provided 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. The portable device may include a smart phone, a smart pad, a wearable device (e.g., a smart watch, smart glasses), a computer (e.g., a laptop computer), and the like. Home appliances may include a TV, a refrigerator, a washing machine, and the like. The IoT device may include a sensor, a smart meter, and the like. For example, the base station and the network may be implemented as a wireless device, and the specific wireless device 200a may operate as a base station/network node to other wireless devices.

The wireless devices 100a to 100f may be connected to the network <NUM> through the base station <NUM>. 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 <NUM> through the network <NUM>. The wireless devices 100a to 100f may communicate with each other through the base station <NUM>/network <NUM>, but may also communicate directly (e.g., sidelink communication) without passing through the base station/network. For example, the vehicles 100b-<NUM> and 100b-<NUM> may perform direct communication (e.g., Vehicle to Vehicle (V2V)/Vehicle to everything (V2X) communication). In addition, the IoT device (e.g., sensor) may directly communicate with other IoT devices (e.g., sensor) or other wireless devices 100a to 100f.

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

<FIG> illustrates wireless devices to which the present disclosure is applied.

Referring to <FIG>, the first wireless device <NUM> and the second wireless device <NUM> may transmit/receive wireless signals through various wireless access technologies (e.g., LTE, NR). Here, {first wireless device <NUM>, second wireless device <NUM>} may correspond to {wireless device 100x, base station <NUM>} and/or {wireless device 100x, wireless device 100x} of <FIG>.

The first wireless device <NUM> includes one or more processors <NUM> and one or more memories <NUM>, and may further include one or more transceivers <NUM> and/or one or more antennas <NUM>. The processor <NUM> controls the memory <NUM> and/or the transceiver <NUM> and may be configured to implement the descriptions, functions, procedures, suggestions, methods, and/or operational flow charts disclosed herein. For example, the processor <NUM> may process information in the memory <NUM> to generate first information/ signal, and then transmit a wireless signal including the first information/ signal through the transceiver <NUM>. In addition, the processor <NUM> may receive the radio signal including the second information/ signal through the transceiver <NUM>, and then store the information obtained from the signal processing of the second information/signal in the memory <NUM>. The memory <NUM> may be connected to the processor <NUM> and may store various information related to the operation of the processor <NUM>. For example, the memory <NUM> may store software code including instructions for performing some or all of processes controlled by the processor <NUM>, or for performing the descriptions, functions, procedures, suggestions, methods, and/or operational flowcharts disclosed in the document. Here, the processor <NUM> and the memory <NUM> may be part of a communication modem/circuit/chip designed to implement a wireless communication technology (e.g., LTE, NR). A transceiver <NUM> may be coupled to the processor <NUM> and may transmit and/or receive wireless signals via one or more antennas <NUM>. The transceiver <NUM> may include a transmitter and/or a receiver. The transceiver <NUM> 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.

The second wireless device <NUM> includes one or more processors <NUM>, one or more memories <NUM>, and may further include one or more transceivers <NUM> and/or one or more antennas <NUM>. The processor <NUM> controls the memory <NUM> and/or the transceiver <NUM> and may be configured to implement the descriptions, functions, procedures, suggestions, methods, and/or flow charts disclosed herein. For example, the processor <NUM> may process the information in the memory <NUM> to generate third information/signal, and then transmit a wireless signal including the third information/ signal through the transceiver <NUM>. In addition, the processor <NUM> may receive the radio signal including the fourth information/signal through the transceiver <NUM>, and then store information obtained from signal processing of the fourth information/signal in the memory <NUM>. The memory <NUM> may be connected to the processor <NUM> and may store various information related to the operation of the processor <NUM>. For example, the memory <NUM> may store software code including instructions for performing some or all of the processes controlled by the processor <NUM>, or for performing the descriptions, functions, procedures, suggestions, methods, and/or operational flowcharts disclosed in the document. Here, the processor <NUM> and the memory <NUM> may be part of a communication modem/circuit/chip designed to implement a wireless communication technology (e.g., LTE, NR). The transceiver <NUM> may be coupled to the processor <NUM> and may transmit and/or receive wireless signals via one or more antennas <NUM>. Transceiver <NUM> may include a transmitter and/or receiver. Transceiver <NUM> may be used interchangeably with an RF unit. In the present disclosure, a wireless device may refer to a communication modem/circuit/chip.

Hereinafter, hardware elements of the wireless devices <NUM> and <NUM> will be described in more detail. Although not limited thereto, one or more protocol layers may be implemented by one or more processors <NUM>, <NUM>. For example, one or more processors <NUM>, <NUM> may implement one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, SDAP). The one or more processors <NUM>, <NUM> may generate one or more Protocol Data Units (PDUs) and/or one or more Service Data Units (SDUs) according to the description, function, procedure, proposal, method and/or operational flowcharts disclosed herein. One or more processors <NUM> , <NUM> may generate messages, control information, data, or information according to the description, function, procedure, proposal, method, and/or flow charts disclosed herein. The one or more processors <NUM> and <NUM> generate a signal (e.g., a baseband signal) including PDUs, SDUs, messages, control information, data or information according to the functions, procedures, proposals and/or methods disclosed herein and provide it to one or more transceivers <NUM> and <NUM>. One or more processors <NUM>, <NUM> may receive signals (e.g., baseband signals) from one or more transceivers <NUM>, <NUM>, and may obtain PDUs, SDUs, messages, control information, data, or information according to description, functions, procedures, proposals, methods, and/or operational flowcharts disclosed herein.

One or more processors <NUM>, <NUM> may be referred to as a controller, microcontroller, microprocessor, or microcomputer. One or more processors <NUM> , <NUM> 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 <NUM> , <NUM>. The descriptions, functions, procedures, suggestions, methods, and/or flowcharts of operations disclosed in this document may be implemented using firmware or software, and the firmware or software may be implemented to include modules, procedures, functions, and the like. Firmware or software configured to perform the descriptions, functions, procedures, suggestions, methods, and/or flow charts disclosed herein may be included in one or more processors <NUM>, <NUM> or may be stored in one or more memories <NUM>, <NUM> and driven by one or more processors <NUM>, <NUM>. The descriptions, functions, procedures, suggestions, methods, and/or flowcharts of operations disclosed herein may be implemented using firmware or software in the form of code, instructions, and/or a set of instructions.

One or more memories <NUM>, <NUM> may be coupled to one or more processors <NUM>, <NUM> and may store various forms of data, signals, messages, information, programs, codes, instructions, and/or instructions. One or more memories <NUM>, <NUM> may be comprised of ROM, RAM, EPROM, flash memory, hard drives, registers, cache memory, computer readable storage media, and/or combinations thereof. One or more memories <NUM> , <NUM> may be located inside and/or external to one or more processors <NUM> , <NUM>. Additionally, one or more memories <NUM>, <NUM> may be coupled to one or more processors <NUM>, <NUM> through various technologies, such as wired or wireless connections.

One or more transceivers <NUM>, <NUM> may transmit user data, control information, radio signals/channels, etc. referred to in the methods and/or operation flowcharts herein, to one or more other devices. The one or more transceivers <NUM>, <NUM> may receive user data, control information, radio signals/channels, etc. referred to in the descriptions, functions, procedures, suggestions, methods and/or flow charts, etc. disclosed herein, from one or more other devices. For example, one or more transceivers <NUM>, <NUM> may be coupled to one or more processors <NUM> , <NUM> and may transmit and receive wireless signals. For example, one or more processors <NUM>, <NUM> may control one or more transceivers <NUM>, <NUM> to transmit user data, control information, or wireless signals to one or more other devices. In addition, one or more processors <NUM>, <NUM> may control one or more transceivers <NUM>, <NUM> to receive user data, control information, or wireless signals from one or more other devices. Further, one or more transceivers <NUM>, <NUM> may be coupled to one or more antennas <NUM>, <NUM>, and may be configured to transmit and receive, through the one or more antennas <NUM>, <NUM>, user data, control information, radio signals/channels, etc. mentioned in description, functions, procedures, proposals, methods and/or operation flowcharts. In this document, one or more antennas may be a plurality of physical antennas or a plurality of logical antennas (e.g., antenna ports). The one or more transceivers <NUM>, <NUM> convert the received radio signal/channel, etc. from the RF band signal into a baseband signal to process the received user data, control information, radio signal/channel, etc. using the one or more processors <NUM>, <NUM>. One or more transceivers <NUM> and <NUM> may convert user data, control information, radio signals/channels, etc. processed using one or more processors <NUM> and <NUM> from baseband signals to RF band signals. To this end, one or more transceivers <NUM> , <NUM> may include (analog) oscillators and/or filters.

<FIG> shows another example of a wireless device applied to the present disclosure. The wireless device may be implemented in various forms according to use-examples/services (refer to <FIG>).

Referring to <FIG>, wireless devices <NUM> and <NUM> may correspond to wireless devices <NUM> and <NUM> of <FIG>, and may consist of various elements, components, units/units, and/or modules. For example, the wireless devices <NUM> and <NUM> may include a communication unit <NUM> , a control unit <NUM>, a memory unit <NUM>, and an additional element <NUM>. The communication unit may include communication circuitry <NUM> and transceiver(s) <NUM>. For example, communication circuitry <NUM> may include one or more processors <NUM>, <NUM> and/or one or more memories <NUM>, <NUM> of <FIG>. For example, the transceiver (s) <NUM> may include one or more transceivers <NUM>, <NUM> and/or one or more antennas <NUM>, <NUM> of <FIG>. The control unit <NUM> is electrically connected to the communication unit <NUM>, the memory unit <NUM>, and the additional element <NUM>, and controls general operations of the wireless device. For example, the controller <NUM> may control the electrical/mechanical operation of the wireless device based on the program/code/command/information stored in the memory unit <NUM>. In addition, the control unit <NUM> may transmit the information stored in the memory unit <NUM> to the outside(e.g., another communication device) through the communication unit <NUM> through a wireless/wired interface, or may store information received from the outside (e.g., another communication device) through a wireless/wired interface through the communication unit <NUM> in the memory unit <NUM>.

The additional element <NUM> may be variously configured according to the type of the wireless device. For example, the additional element <NUM> may include at least one of a power unit/battery, an input/output unit (I/O unit), a driving unit, and a computing unit. Although not limited thereto, a wireless device may include a robot (<FIG> and 100a ), a vehicle (<FIG> , 100b-<NUM> , 100b-<NUM> ), an XR device (<FIG> and 100c ), a mobile device (<FIG> and 100d ), and a home appliance (<FIG>, 100e), IoT device (<FIG>, 100f), digital broadcasting terminal, hologram device, public safety device, MTC device, medical device, fintech device (or financial device), security device, climate/environment device, It may be implemented in the form of an AI server/device (<FIG> and <NUM> ), a base station (<FIG> and <NUM>), and a network node. The wireless device may be mobile or used in a fixed location depending on the use-example/service.

In <FIG>, various elements, components, units/units, and/or modules in the wireless devices <NUM> and <NUM> may be all interconnected through a wired interface, or at least some of them may be wirelessly connected through the communication unit <NUM>. For example, in the wireless devices <NUM> and <NUM>, the control unit <NUM> and the communication unit <NUM> are connected by wire, and the control unit <NUM> and the first unit (e.g., <NUM> , <NUM> ) may be connected to the communication unit <NUM> wirelessly through the communication unit <NUM>. In addition, each element, component, unit/unit, and/or module within the wireless device <NUM>, <NUM> may further include one or more elements. For example, the controller <NUM> may be configured with one or more processor sets. For example, the control unit <NUM> may be configured as a set of a communication control processor, an application processor, an electronic control unit (ECU), a graphic processing processor, a memory control processor, and the like. As another example, the memory unit <NUM> may include random access memory (RAM), dynamic RAM (DRAM), read only memory (ROM), flash memory, volatile memory, and non-volatile memory, volatile memory) and/or a combination thereof.

<FIG> exemplifies a vehicle or an autonomous driving vehicle to which the present disclosure is applied. The vehicle or autonomous driving vehicle may be implemented as a mobile robot, a vehicle, a train, an aerial vehicle (AV), a ship, and the like.

Referring to <FIG>, the vehicle or autonomous vehicle <NUM> may include an antenna unit <NUM>, a communication unit <NUM>, a control unit <NUM>, a driving unit 140a, a power supply unit 140b, and a sensor unit 140c, and an autonomous driving unit 140d. Blocks <NUM>/<NUM>/140a-140d correspond to blocks <NUM>/<NUM>/<NUM> of <FIG>, respectively.

The communication unit <NUM> may transmit and receive signals (e.g., data, control signals, etc.) with external devices such as other vehicles, base stations (e.g., base stations, roadside base stations, etc.), servers, and the like. The controller <NUM> may control elements of the vehicle or the autonomous driving vehicle <NUM> to perform various operations. The controller <NUM> may include an Electronic Control Unit (ECU). The driving unit 140a may cause the vehicle or the autonomous driving vehicle <NUM> to run on the ground. The driving unit 140a may include an engine, a motor, a power train, a wheel, a brake, a steering device, and the like. The power supply unit 140b supplies power to the vehicle or the autonomous driving vehicle <NUM>, and may include a wired/wireless charging circuit, a battery, and the like. The sensor unit 140c may obtain vehicle status, surrounding environment information, user information, and the like. The sensor unit 140c may include an inertial measurement unit (IMU) sensor, a collision sensor, a wheel sensor, a speed sensor, an inclination sensor, a weight sensor, a heading sensor, a position 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 illuminance sensor, a pedal position sensor, and the like. The autonomous driving unit 140d may implement a technology for maintaining a driving lane, a technology for automatically adjusting speed such as adaptive cruise control, a technology for automatically driving along a predetermined route, and a technology for automatically setting a route when a destination is set.

As an example, the communication unit <NUM> may receive map data, traffic information data, and the like 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 <NUM> may control the driving unit 140a to move the vehicle or the autonomous driving vehicle <NUM> along the autonomous driving path (e.g., speed/direction adjustment) according to the driving plan. During autonomous driving, the communication unit <NUM> may obtain the latest traffic information data from an external server non/periodically, and may acquire surrounding traffic information data from surrounding vehicles. Also, during autonomous driving, the sensor unit 140c may acquire vehicle state 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 <NUM> may transmit information about a vehicle location, an autonomous driving route, a driving plan, and the like to an external server. The external server may predict traffic information data in advance using AI technology or the like based on information collected from the vehicle or autonomous driving vehicles, and may provide the predicted traffic information data to the vehicle or autonomous driving vehicles.

It is apparent to those skilled in the art that the present disclosure can be embodied in other specific forms without departing from the characteristics of the present disclosure. Accordingly, the above detailed description should not be construed as restrictive in all respects but as exemplary. The scope of the present disclosure should be determined by a reasonable interpretation of the appended claims.

Claim 1:
A method for transmitting and receiving signals by a user equipment, UE, operating in a wireless communication system, the method comprising:
receiving (S1701) a random access response, RAR, based on a physical random access channel, PRACH, transmission by the UE; and
transmitting (S1703), in a bandwidth part, BWP, a physical uplink shared channel, PUSCH, for shared spectrum channel access, based on the RAR;
wherein a frequency domain resource allocation in the BWP for the PUSCH transmission is based on a frequency domain resource assignment, FDRA, field in the RAR,
wherein, based on information regarding interlace allocation of the PUSCH being not provided by higher-layer signaling:
(i) based on a number of physical resource blocks, PRBs, (N) in the BWP being equal to or less than a threshold of <NUM>, the FDRA field is truncated to <MAT> least significant bits, LSBs, and
(ii) based on the number of PRBs (N) in the BWP being greater than the threshold of <NUM>, the FDRA field is padded with <MAT> most significant bits ,MSBs,
wherein, based on the information regarding the interlace allocation of the PUSCH being provided by the higher-layer signaling:
(i) based on a subcarrier spacing, SCS, for the BWP being <NUM>, the FDRA field is truncated to <NUM> LSBs, or
(ii) based on the SCS for the BWP being <NUM>, the FDRA field is truncated to <NUM> LSBs, and
wherein the FDRA field is interpreted as a FDRA field in downlink control information, DCI, format 0_0.