Patent Description:
Generally, a wireless communication system is developing to diversely cover a wide range to provide such a communication service as an audio communication service, a data communication service and the like. The wireless communication is a sort of a multiple access system capable of supporting communications with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). For example, the multiple access system may include one of code division multiple access (CDMA) system, frequency division multiple access (FDMA) system, time division multiple access (TDMA) system, orthogonal frequency division multiple access (OFDMA) system, single carrier frequency division multiple access (SC-FDMA) system, and the like.

<CIT> discloses operation examples of a method for determining various parameters for transmitting a physical random access channel preamble on an unlicensed band, and a terminal based on the same. <CIT> discloses a method and an apparatus for transmitting and receiving signals in a wireless communication system which comprises transmitting a first physical random access channel and receiving a random access response on the basis thereof, wherein the first physical random access channel may be configured by a physical random access channel sequence of a particular length, which is mapped to <NUM> consecutive physical resource blocks, being repetitively mapped multiple times in the frequency domain. The publication "<NPL>) aims at finding a common understanding on regulations and requirements in connection with channel access mechanism. The publication "<NPL>) focuses inter alia on channel access mechanism in order to comply with the regulatory requirements applicable to unlicensed spectrum for frequencies between <NUM>,<NUM> and <NUM>.

The object of the present disclosure is to provide a method and apparatus for performing a random access procedure efficiently in a wireless communication system.

The present disclosure provides a method and apparatus for transmitting and receiving a signal in a wireless communication system with the features of the independent claims.

In one aspect of the present invention, a method for transmitting and receiving signals by a user equipment in a wireless communication system is provided.

In another aspect of the present invention, as device for performing the signal transmission and reception method, a user equipment is provided.

In the method and device, based on a number of PRACH slots in the reference slot being <NUM>, a value for the one PRACH slot may be N-<NUM>.

In the method and device, based on the number of PRACH slots in the reference slot being <NUM>, values for the two PRACH slots may be N/<NUM>-<NUM> and N-<NUM>.

In the method and device, based on the number of PRACH slots in the reference slot being <NUM>, values for the two PRACH slots may be N-<NUM> and N-<NUM>.

The above-described aspects of the present disclosure are only some of the preferred embodiments of the present disclosure, and various embodiments reflecting the technical features of the present disclosure may be derived and understood from the following detailed description of the present disclosure by those skilled in the art.

According to an embodiment of the present disclosure, a communication apparatus may perform a random access procedure more efficiently in a different way from the prior art.

The following technology may be used in various wireless access systems such as code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), single carrier frequency division multiple access (SC-FDMA), and so on. CDMA may be implemented as a radio technology such as universal terrestrial radio access (UTRA) or CDMA2000. TDMA may be implemented as a radio technology such as global system for mobile communications (GSM)/general packet radio service (GPRS)/enhanced data rates for GSM evolution (EDGE). OFDMA may be implemented as a radio technology such as institute of electrical and electronics engineers (IEEE) <NUM> (wireless fidelity (Wi-Fi)), IEEE <NUM> (worldwide interoperability for microwave access (WiMAX)), IEEE <NUM>, evolved UTRA (E-UTRA), and so on. UTRA is a part of universal mobile telecommunications system (UMTS). 3rd generation partnership project (3GPP) long term evolution (LTE) is a part of evolved UMTS (E-UMTS) using E-UTRA, and LTE-advanced (LTE-A) is an evolution of 3GPP LTE. 3GPP new radio or new radio access technology (NR) is an evolved version of 3GPP LTE/LTE-A.

For clarity of description, the present disclosure will be described in the context of a 3GPP communication system (e.g., LTE and NR). LTE refers to a technology beyond 3GPP TS <NUM>. xxx Release <NUM>. Specifically, the LTE technology beyond 3GPP TS <NUM>. xxx Release <NUM> is called LTE-A, and the LTE technology beyond 3GPP TS <NUM>. xxx Release <NUM> is called LTE-A pro. 3GPP NR is the technology beyond 3GPP TS <NUM>. xxx Release <NUM>. LTE/NR may be referred to as a 3GPP system. "xxx" specifies a technical specification number. LTE/NR may be generically referred to as a 3GPP system. For the background technology, terminologies, abbreviations, and so on as used herein, refer to technical specifications published before the present disclosure. For example, the following documents may be referred to.

<FIG> illustrates a radio frame structure used for NR.

In NR, UL and DL transmissions are configured in frames. Each radio frame has a length of <NUM> and is divided into two <NUM>-ms half-frames. Each half-frame is divided into five <NUM>-ms subframes. A subframe is divided into one or more slots, and the number of slots in a subframe depends on a subcarrier spacing (SCS). Each slot includes <NUM> or <NUM> OFDM(A) symbols according to a cyclic prefix (CP). When a normal CP is used, each slot includes <NUM> OFDM symbols. When an extended CP is used, each slot includes <NUM> OFDM symbols. A symbol may include an OFDM symbol (or a CP-OFDM symbol) and an SC-FDMA symbol (or a discrete Fourier transform-spread-OFDM (DFT-s-OFDM) symbol).

Table <NUM> exemplarily illustrates that the number of symbols per slot, the number of slots per frame, and the number of slots per subframe vary according to SCSs in a normal CP case.

Table <NUM> illustrates that the number of symbols per slot, the number of slots per frame, and the number of slots per subframe vary according to SCSs in an extended CP case.

In the NR system, different OFDM(A) numerologies (e.g., SCSs, CP lengths, and so on) may be configured for a plurality of cells aggregated for one UE. Accordingly, the (absolute time) duration of a time resource (e.g., a subframe, a slot, or a transmission time interval (TTI)) (for convenience, referred to as a time unit (TU)) composed of the same number of symbols may be configured differently between the aggregated cells.

<FIG> illustrates a resource grid during the duration of one slot.

A slot includes a plurality of symbols in the time domain. For example, one slot includes <NUM> symbols in a normal CP case and <NUM> symbols in an extended CP case. A carrier includes a plurality of subcarriers in the frequency domain. A resource block (RB) may be defined by a plurality of (e.g., <NUM>) consecutive subcarriers in the frequency domain. A plurality of RB interlaces (simply, interlaces) may be defined in the frequency domain. Interlace m ∈{<NUM>, <NUM>,. , M-<NUM>} may be composed of (common) RBs {m, M+m, <NUM>+m, <NUM>+m,. M denotes the number of interlaces. A bandwidth part (BWP) may be defined by a plurality of consecutive (physical) RBs ((P)RBs) in the frequency domain and correspond to one numerology (e.g., SCS, CP length, and so on). A carrier may include up to N (e.g., <NUM>) BWPs. Data communication may be conducted in an active BWP, and only one BWP may be activated for one UE. Each element in a resource grid may be referred to as a resource element (RE), to which one complex symbol may be mapped.

<FIG> illustrates a structure of a self-contained slot.

In the NR system, a frame has a self-contained structure in which a DL control channel, DL or UL data, a UL control channel, and the like may all be contained in one slot. For example, the first N symbols (hereinafter, DL control region) in the slot may be used to transmit a DL control channel, and the last M symbols (hereinafter, UL control region) in the slot may be used to transmit a UL control channel. N and M are integers greater than or equal to <NUM>. A resource region (hereinafter, a data region) that is between the DL control region and the UL control region may be used for DL data transmission or UL data transmission. For example, the following configuration may be considered. Respective sections are listed in a temporal order.

The PDCCH may be transmitted in the DL control region, and the PDSCH may be transmitted in the DL data region. The PUCCH may be transmitted in the UL control region, and the PUSCH may be transmitted in the UL data region. The GP provides a time gap in the process of the UE switching from the transmission mode to the reception mode or from the reception mode to the transmission mode. Some symbols at the time of switching from DL to UL within a subframe may be configured as the GP.

In the present disclosure, a base station (BS) may be, for example, a gNode B (gNB).

<FIG> illustrates an exemplary wireless communication system supporting an unlicensed band applicable to the present disclosure.

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

When a BS and a UE transmit and receive signals on carrier-aggregated LCC and UCC as illustrated in <FIG>, the LCC and the UCC may be configured as a primary CC (PCC) and a secondary CC (SCC), respectively. The BS and the UE may transmit and receive signals on one UCC or on a plurality of carrier-aggregated UCCs as illustrated in <FIG>. In other words, the BS and UE may transmit and receive signals only on UCC(s) without using any LCC. For an SA operation, PRACH, PUCCH, PUSCH, and SRS transmissions may be supported on a UCell.

Signal transmission and reception operations in a U-band as described in the present disclosure may be applied to the afore-mentioned deployment scenarios (unless specified otherwise).

Unless otherwise noted, the definitions below are applicable to the following terminologies used in the present disclosure.

<FIG> illustrates a resource occupancy method in a U-band. According to regional regulations for U-bands, a communication node in the U-band needs to determine whether a channel is used by other communication node(s) before transmitting a signal. Specifically, the communication node may perform carrier sensing (CS) before transmitting the signal so as to check whether the other communication node(s) perform signal transmission. When the other communication node(s) perform no signal transmission, it is said that clear channel assessment (CCA) is confirmed. When a CCA threshold is predefined or configured by higher layer signaling (e.g., RRC signaling), the communication node may determine that the channel is busy if the detected channel energy is higher than the CCA threshold. Otherwise, the communication node may determine that the channel is idle. The Wi-Fi standard (<NUM>. 11ac) specifies a CCA threshold of -<NUM> dBm for non-Wi-Fi signals and a CCA threshold of -<NUM> dBm for Wi-Fi signals. When it is determined that the channel is idle, the communication node may start the signal transmission in a UCell. The series of processes described above may be referred to as Listen-Before-Talk (LBT) or a channel access procedure (CAP). The LBT, CAP, and CCA may be interchangeably used in this document.

Specifically, for DL reception/UL transmission in a U-band, at least one of the following CAP methods to be described below may be employed in a wireless communication system according to the present disclosure.

The BS may perform one of the following U-band access procedures (e.g., CAPs) for DL signal transmission in a U-band.

In the Type <NUM> DL CAP, the length of a time duration spanned by sensing slots sensed to be idle before transmission(s) may be random. The Type <NUM> DL CAP may be applied to the following transmissions:.

<FIG> is a flowchart illustrating CAP operations performed by a BS to transmit a DL signal in a U-band.

Referring to <FIG>, the BS may sense whether a channel is idle for sensing slot durations of a defer duration Td. Then, if a counter N is zero, the BS may perform transmission (S1234). In this case, the BS may adjust the counter N by sensing the channel for additional sensing slot duration(s) according to the following steps:.

Table <NUM> shows that mp, a minimum contention window (CW), a maximum CW, a maximum channel occupancy time (MCOT), and an allowed CW size, which are applied to the CAP, vary depending on channel access priority classes.

The defer duration Td is configured in the following order: duration Tf (<NUM>) + mp consecutive sensing slot durations Tsl (<NUM>). Tf includes the sensing slot duration Tsl at the beginning of the <NUM>-us duration.

The following relationship is satisfied: CWmin,p <= CWp <= CWmax,p. CWp may be initially configured by CWp = CWmin,p and updated before step <NUM> based on HARQ-ACK feedback (e.g., ACK or NACK) for a 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. Alternatively, CWp may be increased to the next highest allowed value or maintained as it is.

In the Type <NUM> DL CAP, the length of a time duration spanned by sensing slots sensed to be idle before transmission(s) may be determined. The Type <NUM> DL CAP is classified into Type 2A/2B/2C DL CAPs.

The Type 2A DL CAP may be applied to the following transmissions. In the Type 2A DL CAP, the BS may perform transmission immediately after the channel is sensed to be idle at least for a sensing duration Tshort_dl = <NUM>. Here, Tshort_dl includes the duration Tf (=<NUM>) and one sensing slot duration immediately after the duration Tf, where the duration Tf includes a sensing slot at the beginning thereof.

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

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

In the Type <NUM> UL CAP, the length of a time duration spanned by sensing slots sensed to be idle before transmission(s) is random. The Type <NUM> UL CAP may be applied to the following transmissions.

<FIG> is a flowchart illustrating Type <NUM> CAP operations performed by a UE to transmit a UL signal.

Referring to <FIG>, the UE may sense whether a channel is idle for sensing slot durations of a defer duration Td. Then, if a counter N is zero, the UE may perform transmission (S1534). In this case, the UE may adjust the counter N by sensing the channel for additional sensing slot duration(s) according to the following steps:.

Table <NUM> shows that mp, a minimum CW, a maximum CW, an MCOT, and an allowed CW size, which are applied to the CAP, vary depending on channel access priority classes.

The defer duration Td is configured in the following order: duration Tf(<NUM>) + mp consecutive sensing slot durations Tsl (<NUM>). Tf includes the sensing slot duration Tsl at the beginning of the <NUM>-us duration.

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

In the Type <NUM> UL CAP, the length of a time duration spanned by sensing slots sensed to be idle before transmission(s) may be determined. The Type <NUM> UL CAP is classified into Type 2A/2B/2C UL CAPs. In the Type 2A UL CAP, the UE may perform transmission immediately after the channel is sensed to be idle at least for a sensing duration Tshort_dl = <NUM>. Here, Tshort_dl includes the duration Tf (=<NUM>) and one sensing slot duration immediately after the duration Tf. In the Type 2A UL CAP, Tf includes a sensing slot at the beginning thereof. In the Type 2B UL CAP, the UE may perform transmission immediately after the channel is sensed to be idle for the sensing duration Tf =<NUM>. In the Type 2B UL CAP, Tf includes a sensing slot within <NUM> from the end of the duration. In the Type 2C UL CAP, the UE does not perform channel sensing before performing transmission.

<FIG> illustrates random access procedures. <FIG> illustrates the contention-based random access procedure, and <FIG> illustrates the dedicated random access procedure.

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

The UE may receive random access information in system information from the BS.

When the UE needs random access, the UE transmits an RACH preamble to the BS as in step <NUM>. The BS may identify each RACH preamble by a time/frequency resource (RACH occasion (RO)) in which the RACH preamble is transmitted, and a preamble index (PI).

Upon receipt of the RACH preamble from the UE, the BS transmits an RAR message to the UE as in step <NUM>. To receive the RAR message, the UE monitors an L1/L2 PDCCH with a cyclic redundancy check (CRC) masked with a random access-RNTI (RA-RNTI), including scheduling information for the RAR message, within a preconfigured time window (e.g., ra-ResponseWindow). The PDCCH masked with the RA-RNTI may be transmitted only in a common search space. When receiving a scheduling signal masked with the RA-RNTI, the UE may receive an RAR message on a PDSCH indicated by the scheduling information. The UE then checks whether there is RAR information directed to the UE in the RAR message. The presence or absence of the RAR information directed to the UE may be determined by checking whether there is a random access preamble ID (RAPID) for the preamble transmitted by the UE. The index of the preamble transmitted by the UE may be identical to the RAPID. The RAR information includes the index of the corresponding RACH preamble, timing offset information (e.g., timing advance command (TAC)) for UL synchronization, UL scheduling information (e.g., UL grant) for Msg3 transmission, and UE temporary identification information (e.g., temporary-C-RNTI (TC-RNTI)).

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

After receiving the UL-SCH data, the BS transmits a contention resolution message (Msg4) to the UE as in step <NUM>. When the UE receives the contention resolution message and succeeds in contention resolution, the TC-RNTI is changed to a C-RNTI. Msg4 may include the ID of the UE and/or RRC connection-related information (e.g., an RRCSetup message). When information transmitted in Msg3 does not match information received in Msg4, or when the UE has not received Msg4 for a predetermined time, the UE may retransmit Msg3, determining that the contention resolution has failed.

Referring to <FIG>, the dedicated random access procedure includes the following three steps. Messages transmitted in steps <NUM> to <NUM> may be referred to as Msg0 to Msg2, respectively. The BS may trigger the dedicated random access procedure by a PDCCH serving the purpose of commanding RACH preamble transmission (hereinafter, referred to as a PDCCH order).

Steps <NUM> and <NUM> of the dedicated random access procedure may be the same as steps <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 procedure by a PDCCH order. DCI format 1_0 is used to schedule a PDSCH in one DL cell. When the CRC of DCI format 1_0 is scrambled with a C-RNTI, and all bits of a "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 fields of DCI format 1_0 are configured as follows.

When DCI format 1_0 does not correspond to a PDCCH order, DCI format 1_0 includes fields used to schedule a PDSCH (e.g., a time domain resource assignment, a modulation and coding scheme (MCS), an HARQ process number, a PDSCH-to-HARQ_feedback timing indicator, and so on).

In the prior art, random access is performed by a <NUM>-step procedure as described above. In the legacy LTE system, an average of <NUM> is required for the <NUM>-step random access procedure.

The NR system may require lower latency than conventional systems. When random access occurs in a U-band, the random access may be terminated, that is, contention may be resolved only if the UE and BS sequentially succeed in LBT in all steps of the <NUM>-step random access procedure. If the LBT fails even in one step of the <NUM>-step random access procedure, resource efficiency may decrease, and latency may increase. If the LBT fails in a scheduling/transmission process associated with Msg2 or Msg3, the resource efficiency may significantly decrease, and the latency may significantly increase. For random access in an L-band, low latency may be required in various scenarios of the NR system. Therefore, a <NUM>-step random access procedure may be performed in the L-band as well.

In order to reduce the latency in the random access procedure, a <NUM>-step random access procedure is proposed in the present disclosure.

As illustrated in <FIG>, the <NUM>-step random access procedure may include two steps: transmission of a UL signal (referred to as MsgA) from the UE to the BS and transmission of a DL signal (referred to as MsgB) from the BS to the UE.

The following description focuses on the initial access procedure, but the proposed methods may be equally applied to the random access procedure after the UE and BS establish an RRC connection. Further, a random access preamble and a PUSCH part may be transmitted together in a non-contention random access procedure as shown in <FIG>.

While not shown, the BS may transmit a PDCCH for scheduling MsgB to the UE, which may be referred to as an MsgB PDCCH.

<FIG> illustrates an RB interlace. In a shared spectrum, a set of inconsecutive RBs (at the regular interval) (or a single RB) in the frequency domain may be defined as a resource unit used/allocated to transmit a UL (physical) channel/signal in consideration of regulations on occupied channel bandwidth (OCB) and power spectral density (PSD). Such a set of inconsecutive RBs is defined as the RB interlace (or interlace) for convenience.

Referring to <FIG>, a plurality of RB interlaces (interlaces) may be defined in a frequency bandwidth. Here, the frequency bandwidth 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) RBs {m, M+m, <NUM>+m, <NUM>+m,. }, where M represents the number of interlaces. A transmitter (e.g., UE) may use one or more interlaces to transmit a signal/channel. The signal/channel may include a PUCCH or PUSCH.

The signal/channel may include PUCCH, PUSCH and/or PRACH.

The above-described contents (NR frame structure, U-Band system, etc.) may be applied in combination with the methods according to the present disclosure described later, or may be supplemented to clarify the technical features of the methods proposed in the present disclosure.

In addition, the methods to be described later are related to uplink transmission and may be equally applied to the uplink signal transmission method in the above-described NR system (licensed band) or U-band system (unlicensed band). It should also be noted that embodiments of the present disclosure can be modified or replaced to fit the terms, expressions, structures, etc. defined in each system such that the technical idea proposed in the present disclosure can be implemented in the corresponding system.

For example, downlink transmission using the methods described below may be performed in the L-cell and/or U-cell defined in the U-band system.

In a cellular communication system such as the LTE/NR system, utilizing not only the unlicensed bands such as the <NUM> band, which is mainly used by the legacy Wi-Fi system, but also the unlicensed bands such as the <NUM>/<NUM> and <NUM> bands for traffic offloading is under discussion.

As described above, in the Wi-Fi standard (<NUM>. 11ac), the CCA threshold is defined as -<NUM> dBm for the non-Wi-Fi signal and -<NUM> dBm for the Wi-Fi signal. In other words, when a station (STA) or an access point (AP) of the Wi-Fi system receives a signal from a device not belonging to the Wi-Fi system at the power of -<NUM> dBm or more in a specific band, it skips signal transmission in the specific band.

In the present disclosure, the term "unlicensed band" may be replaced or interchangeably used with "shared spectrum.

The NR system supports a number of kinds of numerology and SCS to support various services. For example, when the SCS is <NUM>, the NR system supports a wide area in traditional cellular bands. When the SCS is <NUM>/<NUM>, the NR system supports a dense-urban, lower latency and wider carrier bandwidth. When the SCS is <NUM> or higher, the NR system supports a bandwidth greater than <NUM> to overcome phase noise.

The NR frequency band is defined as two types of frequency ranges, FR1 and FR2. FR1 and FR2 may be configured as shown in Table <NUM>. FR2 may represent a millimeter wave (mmW).

A band (e.g., the <NUM> to <NUM> bands, particularly <NUM>) higher than the FR1 and FR2 bands is referred to as FR4.

The FR4 band may be used as an unlicensed band.

The configuration for a PRACH transmission occasion for the conventional FR2 region is shown in <FIG> is an excerpt from Section <NUM>. <NUM> of the document 3GPP TS <NUM>, and Tables <NUM>. <NUM>-<NUM> to <NUM>. <NUM>-<NUM> refer to the tables in the document 3GPP TS <NUM>. Referring to <FIG>, the configuration of the PRACH transmission occasion is defined based on the slot for the <NUM> SCS. When the <NUM> SCS is used, two slots corresponding to the <NUM> SCS may be present in one slot corresponding to the <NUM> SCS. Accordingly, when the <NUM> SCS is used, a method of selecting one or two of the two slots corresponding to the one slot of the <NUM> SCS as a PRACH transmission occasion is described. In the present disclosure, the slots of Y kHz SCS corresponding to the slots of X kHz SCS (where X and Y are any positive numbers, and X is less than Y) may mean slots of Y kHz that may be included in the time interval occupied by the slot of X kHz SCS. In general, slots of Y kHz SCS are included in the slot of X kHz SCS by the ratio of X to Y. For example, the slots of <NUM> corresponding to the <NUM> SCS may be <NUM> slots (since <NUM>:<NUM> = <NUM>:<NUM>).

In <FIG>, when the value of the parameter "Number of PRACH slots within a <NUM> slot" is <NUM>, only one of the two slots of the <NUM> SCS corresponding to one slot of the two <NUM> SCS is used as a slot for PRACH transmission. Referring to <FIG>, the later one of the two slots of the <NUM> SCS is used as a slot for PRACH transmission (i.e., <MAT>).

When the value of the parameter "Number of PRACH slots within a <NUM> slot" is <NUM> (this case is described as "otherwise" in <FIG>. However, the "Number of PRACH slots within a <NUM> slot" has only a value of <NUM> or <NUM>, and therefore, "otherwise" refers to <NUM>), both slots of the <NUM> SCS corresponding to one slot of <NUM> SCS are used as slots for PRACH transmission (i.e., <MAT>).

In the FR4 region, it is considered to use a greater SCS value (e.g., <NUM>, <NUM>, <NUM>) than the <NUM> SCS. Currently, a method for configuring a PRACH transmission occasion for an SCS value greater than the <NUM> SCS and a PRACH configuration table have not been invented. Therefore, there is a need for a method for configuring a PRACH transmission occasion for a high frequency band.

The following proposed methods may be considered as a PRACH transmission occasion configuration method for FR4. In the methods proposed below, a reference SCS represents an SCS that is a reference for defining a PRACH configuration table. The reference SCS serves as a reference for the size of a single slot required to configure a PRACH transmission occasion using an SCS larger than the reference SCS. For example, for FR2, the <NUM> SCS is a reference SCS, and up to <NUM> SCS is supported.

In addition, the methods proposed below are mainly described based on the PRACH transmission occasion of a <NUM>-step RACH, but may be equally or similarly applied to the PRACH transmission occasion and/or the PUSCH transmission occasion for a <NUM>-step RACH. Hereinafter, the PRACH transmission occasion may be referred to as RO, and the PUSCH transmission occasion may be referred to as PO. Also, the PRACH slot of <FIG> may be referred to as a RACH slot.

Referring to Table <NUM>, the SCS value may be changed based on the value of u. Here, u is an SCS configuration parameter. u is the same as µ in the 3GPP standard document. The values of u when the SCS from <NUM> SCS to <NUM> is applied to the PRACH slot are shown in Table <NUM>.

When u is <NUM>, SCS corresponds to <NUM>. When u is <NUM>, SCS corresponds to <NUM>.

In the first method, the PRACH configuration tables (Tables <NUM>. <NUM>-<NUM> to <NUM>. <NUM>-<NUM> of the document 3GPP TS <NUM>) used for the previously defined FR2 are used even in the FR4 region, and the <NUM> SCS is defined as a reference SCS as in the existing FR2. In FR4, SCS such as <NUM>, <NUM>, <NUM>, and <NUM> may be additionally introduced.

For a single slot of the <NUM> SCS, a different number of N slots may correspond to each SCS considered in FR4. Values that may be <MAT> in Equation <NUM> are {<NUM>, <NUM>,. , N-<NUM>}. N may be a value obtained by dividing each SCS value considered in FR4 by the <NUM> SCS. For example, in the case of <NUM> SCS, the possible values of <MAT> are {<NUM>, <NUM>, <NUM>, <NUM>}. In the case of <NUM> SCS, the possible values of <MAT> are {<NUM>, <NUM>,. Hereinafter, <MAT> may be referred to as a "value for a PRACH slot.

According to proposed method <NUM>, two values among the possible values of <MAT> for each SCS may be selected according to a specific rule, and the PRACH configuration table for FR2 may be reused. The two selected values may be reinterpreted as a first slot defined for <NUM> in the PRACH configuration table (the part to which <MAT> is substituted in <FIG>) or a second slot (the part to which <MAT> is substituted in Table <NUM>).

For example, the smaller one of the two selected values may be reinterpreted as the first slot (the part corresponding to <MAT> in <FIG>), and the greater value may be reinterpreted as the second slot (the part corresponding to <MAT> in <FIG>). As a specific example, when the two selected values are a and b (a<b), the part to which <MAT> is substituted in <FIG> may be reinterpreted as <MAT> (for the first slot), and the part to which <MAT> is substituted in <FIG> may be reinterpreted as <MAT> (for the second slot).

As one of the specific rules for selecting two values among the possible values of <MAT> for each SCS, the two greatest values (i.e., N-<NUM>, N-<NUM>) may be selected from among <NUM> to N-<NUM> that may be values of <MAT>. Alternatively, the greatest number and the median (i.e., N-<NUM>, N/<NUM>-<NUM>) may be selected. An example of the PRACH transmission occasion given when the two greatest values (i.e., N-<NUM>, N-<NUM>) are selected is shown in <FIG>. In addition, an example of the PRACH transmission occasion given when the greatest number and the median (i.e., N-<NUM>, N/<NUM>-<NUM>) are selected is shown in <FIG>. For the <NUM> SCS and <NUM> SCS, the PRACH transmission occasion is determined by the conventional technology. When proposed method <NUM> is applied to <NUM>, <NUM>, and <NUM> SCSs, slots indicated by hatched lines in <FIG> and/or <NUM> are slots including a PRACH transmission occasion.

In the examples of proposed method <NUM>, selecting the slots corresponding to the two greatest numbers (N-<NUM>, N-<NUM>) as a PRACH transmission occasion results in setting, based on the single slot of the <NUM> SCS, the PRACH transmission occasion to the last slot (based on the SCS greater than <NUM>). This result has an advantage in determining validation of the PRACH transmission occasion because a UL symbol is very likely to be present at the rear in the TDD configuration.

Selecting the greatest number and the median (N/<NUM>-<NUM>, N-<NUM>) as another example, has an advantage in that the PRACH transmission occasion time interval is widened and thus time diversity may be obtained.

In addition to the proposed method <NUM>, the BS may indicate to the UE one or two slot indexes among the values that may be <MAT> in the above equation through higher layer signaling (e.g., SIB or dedicated RRC signaling).

As an example, when the BS sets the "Number of PRACH slots within a <NUM> slot" to <NUM>, the UE may configure a PRACH transmission occasion in slot N-<NUM> (i.e., the last slot among the N slots corresponding to the <NUM> SCS single slot duration). The UE may configure a PRACH transmission occasion in a specific slot, slot k, indicated by the BS. Thereafter, the UE may transmit the PRACH preamble through the designated PRACH transmission occasion.

As another example, when the BS sets the "Number of PRACH slots within a <NUM> slot" to <NUM>, two slot indexes indicated by the BS may be used. The UE may reinterpret the smaller one of the two values indicated by the BS as the first slot (the part corresponding to <MAT> in <FIG>) or the second slot (the part corresponding to <MAT> in <FIG>). For example, the smaller one of the two selected values may be reinterpreted as the first slot (the part corresponding to <MAT> in <FIG>), and the greater value may be reinterpreted as the second slot (the part corresponding to <MAT> in <FIG>). As a specific example, when the two selected values are a and b (a<b), the part to which <MAT> is substituted in <FIG> may be reinterpreted as <MAT> (for the first slot), and the part to which <MAT> is substituted in <FIG> may be reinterpreted as <MAT> (for the second slot).

Alternatively, the BS may distinguish slot values serving as the first slot and the second slot and separately indicate the same to the UE. Alternatively, the BS may indicate only the slot index corresponding to the first slot as slot k, and configure the slot index corresponding to the second slot as slot N-<NUM> (i.e., the last slot among the N slots corresponding to the <NUM> SCS single slot duration). Thereafter, the UE may configure a PRACH transmission occasion in the indicated/configured slot and transmit the PRACH preamble therethrough.

With the proposed method, it is not necessary to modify the equation for configuring the PRACH configuration table and the PRACH transmission occasion for the existing FR2.

The BS may configure a <NUM> RACH slot according to the method disclosed in <FIG>. Next, when the SCS to be actually used in the RACH procedure is set to <NUM> and/or <NUM>, the RACH slot may be configured/indicated using the following methods.

[Method <NUM>-B-<NUM>] A specific one (e.g., the first slot in time, or the last slot in time) of a plurality of <NUM> slots and/or <NUM> slots corresponding to a <NUM> RACH slot or a specific number of slots (e.g., slots configured by the BS) may be configured as an actual <NUM> RACH slot and/or a <NUM> RACH slot.

When the BS indicates one or multiple slots, the BS may indicate a slot number based on a specific SCS (e.g., <NUM> SCS). The UE may use a value indicated for another SCS by scaling the same at the SCS ratio. As an example, the BS may configure slot indexes a and b based on the <NUM> SCS. In this case, when the actual SCS for the RACH is <NUM>, the UE may configure x2 (or x2+<NUM>), where x denotes each slot index, and use slot indexes 2a (or 2a+<NUM>) and 2b (or 2b+<NUM>) as RACH slots. Here, +<NUM> is added to select a later slot between the slots facing each other.

For example, when the BS indicates PRACH config index <NUM> as shown in <FIG>, <NUM> slots (e.g., slots <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>) corresponding to <NUM> reference slots <NUM>, <NUM>, <NUM>, and <NUM> are RACH slot candidates. Since the "Number of PRACH slots within a <NUM> slot" is set to <NUM>, the <NUM> slots (e.g., slots <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>) corresponding to the <NUM> reference slots <NUM>, <NUM>, <NUM>, and <NUM> are all configured as RACH slots.

The number of <NUM> slots or <NUM> slots corresponding to the <NUM> slots configured as RACH slots may have four or eight per <NUM> slot. As in the examples of <FIG>, one or more slots may be used as RACH slots.

<FIG> shows an example in which the first slot among the <NUM> slots and/or <NUM> slots corresponding to a configured <NUM> RACH slot is used as a RACH slot. <FIG> shows an example in which the last slot among the <NUM> slots and/or <NUM> slots corresponding to the configured <NUM> RACH slot is used as a RACH slot.

<FIG> shows an example in which a slot of a configured slot index among the <NUM> slots and/or <NUM> slots corresponding to the configured <NUM> RACH slot is used as a RACH slot. <FIG> shows an example in which slot indexes 8N+<NUM>, 8N+<NUM>, 8N+<NUM> and 8N+<NUM> are configured as RACH slots based on the <NUM> SCS and an example in which slot indexes 16N+<NUM>, 16N+<NUM>, 16N+<NUM> and 16N+<NUM> are configured as RACH slots based on the <NUM> SCS. Slots of other indexes configured differently from <FIG> may be used as RACH slots.

[Method <NUM>-B-<NUM>] All the multiple <NUM> slots and/or <NUM> slots corresponding to the configured <NUM> RACH slot may be configured as <NUM> RACH slots and/or <NUM> RACH slots.

In this case, referring to the example (e.g., PRACH config index <NUM>) through <FIG> of Method <NUM>-B-<NUM>, <NUM> slots (e.g., slots <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, and <NUM>) are all configured as RACH slots.

The number of <NUM> slots or <NUM> slots corresponding to the <NUM> slots configured as RACH slots may have four or eight per <NUM> slot. As in the example of <FIG>, all the <NUM> slots or <NUM> slots corresponding to the <NUM> slot may be used as RACH slots.

[Method <NUM>-B-<NUM>] <NUM> slots (i.e., radio frame) to be included in one radio frame including the configured <NUM> RACH slot and the normal slot (a slot that is not a RACH slot) may be configured. RACH slots may be configured by repeating the configured radio frame for <NUM> <NUM> times within a period of <NUM> slots in the radio frame for <NUM>. RACH slots may be configured by repeating the configured radio frame for <NUM> <NUM> times within a period of <NUM> slots in the radio frame for <NUM>.

Method <NUM>-B-<NUM> is different from methods <NUM>-B-<NUM> and <NUM>-B-<NUM> in that slots corresponding to the <NUM> RACH slot are not selected, but the slot configuration is established by repeating the <NUM> slots for <NUM> <NUM> times at <NUM> and/or repeating the same <NUM> times at <NUM>.

For example, when slot indexes {a, b,. , x} among the <NUM> slots constituting the radio frame based on the <NUM> SCS are configured as RACH slots, slot indexes {a, b,. , <NUM>+a, <NUM>+b,. , <NUM>+x,. , <NUM>+a, <NUM>+b,. , <NUM>+x,. , <NUM>+a, <NUM>+b,. , <NUM>+x} among the <NUM> slots constituting the radio frame based on the <NUM> SCS are configured as RACH slots (i.e., the RACH slot pattern of the <NUM> SCS or the <NUM> SCS is repeated <NUM> times).

As another example, when slot indexes {a, b,. , x} among the <NUM> slots constituting the radio frame based on the <NUM> SCS are configured as RACH slots, slot indexes {a, b,. , <NUM>+a, <NUM>+b,. , <NUM>+x,. , <NUM>+a, <NUM>+b,. , <NUM>+x,. , <NUM>+a, <NUM>+b,. , <NUM>+x,. , <NUM>+a, <NUM>+b,. , <NUM>+x,. , <NUM>+a, <NUM>+b,. , <NUM>+x,. , <NUM>+a, <NUM>+b,. , <NUM>+x,. , <NUM>+a, <NUM>+b,. , <NUM>+x} among the <NUM> slots constituting the radio frame based on the <NUM> SCS are configured as RACH slots (i.e., the RACH slot pattern of the <NUM> SCS or the <NUM> SCS is repeated <NUM> times).

According to Method <NUM>-B-<NUM>, RACH slot configuration may be established for the <NUM> or <NUM> SCS based on legacy configuration methods by adding the operation of repeating the RACH slot pattern, without the need for the BS to signal additional information for a UE operation.

The BS may set <NUM> as a reference SCS and configure a <NUM> RACH slot, or may set <NUM> as a reference SCS and configure a <NUM> RACH slot. According to the RACH configuration established/indicated by the BS, ROs for the UE may be mapped to the corresponding RACH slot. <NUM>*X (or <NUM>*X) OFDM symbols using the <NUM>/<NUM> SCS corresponding to X-OFDM symbols occupied by ROs for the <NUM> SCS may be candidates for the RO positions.

For example, when the BS indicates PRACH config index <NUM> as shown in <FIG>, RACH slots may be configured in the <NUM> reference slot indexes <NUM>, <NUM>, <NUM>, and <NUM>. In terms of <NUM>, RACH slots may be configured in slot indexes <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, and <NUM> (because the Number of PRACH slots within a <NUM> slot is <NUM>). An example of representation of mapping of an RO to <NUM> reference slot index N is shown in <FIG>.

In this case, OFDM symbols for the <NUM>/<NUM> SCS corresponding to the OFDM symbols occupied by the ROs for the <NUM> SCS may be candidates for the RO positions.

As an example, the start OFDM symbol of the RO may be aligned. An example of representation of the RO mapping of <NUM>/<NUM> with reference to <FIG> is shown in <FIG>. Referring to <FIG>, among the <NUM>/<NUM> SCS-applied OFDM symbols corresponding to the OFDM symbols occupied by ROs to which the <NUM> SCS is applied, OFDM symbols corresponding to a PRACH duration from the first OFDM symbol may be mapped to ROs.

As a second example, among the <NUM>/<NUM> SCS-applied OFDM symbols corresponding to OFDM symbols occupied by ROs to which the <NUM> SCS is applied, the last OFDM symbol boundary of the RO (i.e., the point where OFDM symbol ends) may be aligned. An example of representation of the RO mapping of <NUM>/<NUM> with reference to <FIG> is shown in <FIG>. Referring to <FIG>, among the <NUM>/<NUM> SCS-applied OFDM symbols corresponding to the OFDM symbols occupied by ROs to which the <NUM> SCS is applied, the RO mapping may start with an OFDM symbol preceding the last OFDM symbol by a PRACH duration such that the OFDM symbols up to the last OFDM symbol may be mapped to ROs.

As in Method <NUM>-C, when ROs to which different SCSs are applied are aligned with an OFDM symbol boundary at a specific predefined position, the changed operation may be simple compared to the existing RO mapping method, and thus UE complexity may be reduced. That is, a method of "aligning the starting symbol boundary of the RO of <NUM>/<NUM> SCS with the starting symbol boundary of the RO of the <NUM> SCS" or "aligning the ending symbol boundary of the RO of the <NUM>/<NUM> SCS with the ending symbol boundary of the RO of the <NUM> SCS" may be considered.

The BS may configure and/or indicate a specific OFDM symbol among <NUM>*X (or <NUM>*X) the <NUM> (or <NUM>) kHz SCS-applied OFDM symbols corresponding to the X OFDM symbols occupied by ROs to which the <NUM> SCS is applied as a starting point of RO mapping. Alternatively, the BS configure and/or indicate starting of RO mapping from one of <NUM> (or <NUM>) OFDM symbols (with a spacing of X OFDM symbols considering that each RO occupies X OFDM symbols) among <NUM>*X (or <NUM>*X) <NUM> (or <NUM>) kHz SCS-applied OFDM symbols corresponding to the X OFDM symbols occupied by an RO to which <NUM> SCS is applied.

When the UE maps an RO, starting at a specific OFDM symbol position indicated by the BS, the mapped RO may be expected not to be outside the <NUM> (or <NUM>) kHz-applied OFDM symbols corresponding to the OFDM symbols occupied by the RO for the <NUM> SCS.

For example, the BS may indicate one in {<NUM>, <NUM>,. , <NUM>*X-X} for <NUM> SCS, and one in {<NUM>, <NUM>,. , <NUM>*X-X} for <NUM>. The UE may expect that one in {<NUM>, <NUM>,. , <NUM>*X-X} is indicated for <NUM> SCS, and that one in {<NUM>, <NUM>,. , <NUM>*X-X} is indicated for <NUM>.

Alternatively, the BS may indicate one in {<NUM>, X, <NUM>*X,. , <NUM>*X-X} for <NUM> SCS, and one in {<NUM>, X, <NUM>*X,. , <NUM>*X-X} for <NUM>. The UE may expect that one in {<NUM>, X, <NUM>*X,. , <NUM>*X-X} is indicated for <NUM> SCS, and that one in {<NUM>, X, <NUM>*X,. , <NUM>*X-X} is indicated for <NUM>.

More specifically, when the PRACH duration of <NUM> SCS is <NUM> OFDM symbols, <NUM> OFDM symbols corresponding to the <NUM> OFDM symbols may be candidates for the RO in the case of <NUM> SCS, and <NUM> OFDM symbols corresponding to the <NUM> OFDM symbols may be candidates for the RO in the case of <NUM> SCS. Since the PRACH duration is <NUM> OFDM symbols, the BS may indicate one in {<NUM>, <NUM>,. , <NUM>} for <NUM> SCS, and one in {<NUM>, <NUM>,. , <NUM>} for <NUM>. The UE may expect that one in {<NUM>, <NUM>,. , <NUM>} is indicated for <NUM> SCS, and that one in {<NUM>, <NUM>,. , <NUM>} is indicated for <NUM>.

Alternatively, the BS may indicate one in {<NUM>, <NUM>, <NUM>, <NUM>} for <NUM> SCS and one in {<NUM>, <NUM>, <NUM>,. , <NUM>} for <NUM> (with a spacing of <NUM> OFDM symbols considering that each RO may occupy <NUM> OFDM symbols). The UE may expect that one in {<NUM>, <NUM>, <NUM>, <NUM>} is indicated for <NUM> SCS, and that one in {<NUM>, <NUM>, <NUM>,. , <NUM>} is indicated for <NUM>.

Specifically, the symbol level index mentioned in Method <NUM>-C is not an OFDM symbol index within an actual slot of <NUM>/<NUM> SCS, and corresponds to indexing from <NUM> to <NUM>*X-<NUM> in chronological order for <NUM>*X <NUM> SCS-applied OFDM symbols corresponding to X OFDM symbols occupied by ROs to which <NUM> SCS is applied. Alternatively, it corresponds to indexing from <NUM> to <NUM>*X-<NUM> in chronological order for <NUM>*X <NUM> SCS-applied OFDM symbols corresponding to the X OFDM symbols occupied by the ROs to which <NUM> SCS is applied.

Equation <NUM> below is a conventional equation for deriving the RA-RNTI.

Here, * represents a multiplication operation. s_id denotes a starting symbol index occupied by an RO on which the UE has transmitted the PRACH preamble. t_id denotes the index of a slot to which the RO on which the UE has transmitted the PRACH preamble belongs.

When the position of the RO for a higher SCS (e.g., <NUM>/<NUM>) is configured and/or indicated to be within the OFDM symbol duration of the RO occupied by the reference SCS (e.g., <NUM>), RA-RNTI may be derived based on Equation <NUM> by allowing the UE and the BS to reinterpreting the starting symbol index and slot index based on the reference SCS (e.g., <NUM>) rather than the higher SCS (e.g., <NUM>/<NUM>). The UE and the BS that need to calculate the RA-RNTI may reinterpret s_id and t_id, which are parameters for deriving the RA-RNTI based on the reference SCS (e.g., <NUM>) even if the SCS of the RO on which the actual PRACH preamble is transmitted/received is configured as a higher SCS (e.g., <NUM>/<NUM>). In other words, the values of s_id and t_id used in deriving the RA-RNTI may be values based on the reference SCS, not the values for the SCS actually applied to the RO on which the PRACH preamble is transmitted.

For example, referring to RO1 of <FIG>, the actual starting symbol index and slot index of RO1 in the <NUM> SCS are s_id=<NUM> and t_id=4N, respectively. The starting symbol index and symbol index reinterpreted based on RO1 of the <NUM> SCS (to be used for RA-RNTI derivation) are s_id=<NUM> and t_id=N, respectively. Similarly, in <NUM> SCS, the actual starting symbol index and slot index of RO1 are s_id = <NUM> and t_id = 8N, respectively, but the starting symbol index and slot index reinterpreted based on RO1 of <NUM> SCS (to be used for RA-RNTI derivation) are s_id=<NUM> and t_id=N, respectively.

As another example, for RO4 of <FIG>, the actual starting symbol index and the slot index of RO4 in the <NUM> SCS are s_id=<NUM> and t_id=4N+<NUM>, respectively. The starting symbol index and slot index reinterpreted based on RO4 of <NUM> SCS (to be used for RA-RNTI derivation) are s_id=<NUM> and t_id=N, respectively. Similarly, in the <NUM> SCS, the actual starting symbol index and slot index of RO4 are s_id=<NUM> and t_id=8N+<NUM>, respectively. The starting symbol index and slot index reinterpreted based on RO4 of <NUM> SCS (to be used for RA-RNTI derivation) are s_id=<NUM> and t_id=N, respectively.

In addition, according to proposed method <NUM>-C, when a timing gap is required between ROs, the timing gap naturally exists between ROs even if the BS does not additionally indicate an explicit timing gap. Therefore, proposed method <NUM>-C may be used when the BS needs to configure/indicate a timing gap between ROs.

In other words, when the BS configures/indicates use of the inter-RO timing gap, proposed method <NUM>-C may be used. When the BS configures/indicates disallowance of use of the inter-RO timing gap (or does not configure the inter-RO timing gap), another proposed method (e.g., proposed method <NUM>, <NUM>-A, or <NUM>-B) by which the ROs may be consecutively mapped without a timing gap may be used.

Alternatively, two different RO mapping methods may be used together. For example, an RO mapping method such as proposed method <NUM>-C in which the timing gap between ROs naturally exists may be used as one mapping type (e.g., RO mapping type <NUM>), and an RO mapping method such as proposed method <NUM>, <NUM>-A, or <NUM>-B in which there is no timing gap between ROs may be used as another mapping type (e.g., RO mapping type <NUM>). When it is necessary to use the inter-RO timing gap, the BS may configure/indicate RO mapping type <NUM>. When it is not necessary to use the inter-RO timing gap, the BS may configure/indicate RO mapping type <NUM>.

Alternatively, in the case where an explicit parameter for configuring a timing gap between ROs to be used is introduced (or the timing gap between ROs is indicated by an implicit method), when the BS indicates presence of a timing gap between ROs through the explicit parameter (or the implicit method), RO mapping type <NUM> may be used based thereon. In contrast, when the BS indicates absence of a timing gap between ROs through the explicit parameter (or the implicit method) (or when the explicit parameter is not transmitted to the UE), RO mapping type <NUM> may be used.

Alternatively, in the case where there is an explicit parameter indicating whether to perform the LBT procedure for the RACH procedure (or it is indicated whether to perform the LBT procedure using an implicit method), when the BS indicates, through the explicit parameter (or the implicit method), that the LBT procedure for the RACH procedure is to be performed, RO mapping type <NUM> may be used (because a timing gap is required between ROs at this time). When the BS indicates, through the explicit parameter (or the implicit method), that the LBT procedure for the RACH procedure is not to be performed (or the explicit parameter is not transmitted to the UE), RO mapping type <NUM> may be used (because a timing gap is not required between the ROs).

When SCS to be used for FR4 is defined, one of the SCSs may be defined as a reference SCS. For example, when <NUM> SCS is configured as the reference SCS for FR4, the RACH slot may be determined in <NUM> and <NUM> SCSs through a method defined for FR2. In addition, a new PRACH configuration table (or a method of reinterpreting the legacy PRACH configuration table) may be defined based on the <NUM> SCS. A method of calculating the PRACH transmission occasion for <NUM> and <NUM> SCSs may be configured similarly to the method of <FIG> (the legacy method consisting of <NUM> SCS and <NUM> SCS).

First, a new PRACH configuration table (or the method of reinterpreting the legacy PRACH configuration table) is considered, the "Slot number" field in the legacy PRACH configuration table may be replaced with a new value, or may be reinterpreted as k times the existing value (e.g., k = <NUM>/<NUM> = <NUM> when the <NUM> SCS is configured as the reference SCS).

For example, when the PRACH config index is <NUM> as shown in <FIG>, the <NUM> SCS reference slot numbers are <NUM> and <NUM>. Since k is <NUM>, the slot numbers in the <NUM> SCS may be <NUM>*<NUM>=<NUM> and <NUM>*<NUM>=<NUM>. Accordingly, slot <NUM> and slot <NUM> may be selected as RACH slots based on the <NUM> SCS.

Additionally, when k times the slot index is set, the PRACH transmission occasion is mapped to the first slot among the slots corresponding to the <NUM> SCS reference slot. Alternatively, additional slots may be configured as many as m slots after k times the slot index is set, where m ∈ {<NUM>, <NUM>,. , k-<NUM>}. When m is <NUM>, the first slot among the <NUM> SCS reference slots corresponding to the <NUM> SCS reference slot may be configured as a RACH slot. When m is k-<NUM>, the last slot among the <NUM> SCS reference slots corresponding to the <NUM> SCS reference slot may be configured as a RACH slot. According to the example of <FIG>, when m is <NUM>, the slots with indexes <NUM>*<NUM>=<NUM> and <NUM>*<NUM>=<NUM> are RACH slots. When m is <NUM>, the slots with indexes <NUM>*<NUM>+<NUM>=<NUM> and <NUM>*<NUM>+<NUM>=<NUM> become RACH slots. When m is <NUM>, the slots with indexes <NUM>*<NUM>+<NUM>=<NUM> and <NUM>*<NUM>+<NUM>=<NUM> are RACH slots. When m is <NUM>, the slots with indexes <NUM>*<NUM>+<NUM>=<NUM> and <NUM>*<NUM>+<NUM>=<NUM> are RACH slots.

The additional slot configuration value of m may be predefined so as to be pre-recognized by the UE and the BS. Also, the UE and the BS may pre-store the configuration of the value of m. Alternatively, the BS may indicate the same to the UE through higher layer signaling (e.g., SIB or dedicated RRC signaling). For example, the default value of m may be <NUM>, and the BS may set one of values <NUM> to k-<NUM> to the UE as the value of m. Specifically, the same value of m may be indicated in the first slot and the second slot, or different values of m may be independently set in the first slot and the second slot. The value of m for the first slot may be indicated by the BS, and the value of m for the second slot may be set according to a preconfigured rule (e.g., (m+<NUM>) mod k, or (m-<NUM>) mod k). Alternatively, the value of m for the second slot may be indicated by the BS, and the value of m for the first slot may be set according to the preconfigured rule (e.g., (m+<NUM>) mod k, or (m-<NUM>) mod k).

<FIG> show examples of RACH slots configured by Method <NUM>. The figures show examples of extension from <NUM> SCS to <NUM> SCS when k = <NUM> and m is <NUM>, <NUM>, <NUM>, and <NUM>, respectively.

Additionally, when <NUM> SCS is configured as the reference SCS, <NUM> SCS may be reinterpreted by the UE according to the method of <FIG> (i.e., configuring a PRACH transmission occasion of <NUM> SCS for <NUM> SCS). For the <NUM> SCS, other methods proposed herein (e.g., proposed methods <NUM> to <NUM>) may be used.

With Method <NUM>, the equation for configuring the PRACH configuration table and PRACH transmission occasion for the existing FR2 only needs to be slightly modified or a little reinterpretation method needs to be added.

In the case of the <NUM> SCS, a PRACH transmission occasion may be present in a single slot. In the case of <NUM> SCS, a PRACH transmission occasion may be present in up to two slots. As such, for <NUM> SCS, <NUM> SCS, and <NUM> SCS, PRACH transmission occasions may be configured in up to <NUM>, <NUM>, and <NUM> slots.

For example, in the case of <NUM> SCS, a maximum of four configuration methods may be considered. That is, since up to four <NUM> SCS slots may be present in a single slot duration of <NUM> SCS, a configuration method using one slot to four slots as a PRACH transmission occasion may be used. The BS may indicate one of the four configuration methods to the UE (e.g., the previously defined parameter "Number of PRACH slots within a <NUM> slot" may be indicated as one of <NUM> to <NUM>), and the UE may configure a PRACH transmission occasion according to the indicated number of slots and then transmit a PRACH preamble. For example, when the number of slots indicated to the UE is <NUM>, <NUM> slots up to the last slot (or <NUM> slots from the first slot) may be used for a PRACH transmission occasion.

An example of option <NUM>-<NUM> is shown in <FIG> shows an exemplary case where it is indicated that a PRACH transmission occasion is to be configured in three slots up to the last slot in the <NUM> SCS.

Additionally, in the case of <NUM> SCS, a maximum of <NUM> configuration methods may be used. In the case of <NUM> SCS, a maximum of <NUM> configuration methods may be used.

For example, in the case of <NUM> SCS, up to four <NUM> SCS slots may be present in the single slot duration of <NUM> SCS, and accordingly configuration methods of using one to four slots as the PRACH transmission occasion may be used. In this case, the UE and the BS may be pre-configured to use two pre-selected configuration methods among the four configuration methods, and the BS may indicate the two configuration methods to the UE (e.g., the previously defined parameter "Number of PRACH slots within a <NUM> slot" may indicate one of two pre-selected numbers among <NUM> to <NUM>). Additionally, the above two configuration methods may not be pre-selected. Instead, the BS may indicate the same to the UE through higher layer signaling (e.g., SIB or dedicated RRC signaling).

Thereafter, the UE may configure a PRACH transmission occasion according to the indicated number of slots and then transmit a PRACH preamble. For example, when the number of preselected slots is <NUM> or <NUM>, and the number of slots indicated to the UE is <NUM>, <NUM> slots up to the last slot (or <NUM> slots from the first slot) may be used for a PRACH transmission occasion.

An example of option <NUM>-<NUM> is shown in <FIG> and <FIG>. <FIG> and <FIG> represent two configuration methods set to two or four. <FIG> illustrates a case where a PRACH transmission occasion is indicated to be configured in a total of two slots up to the last slot in the <NUM> SCS. <FIG> illustrates a case where a PRACH transmission occasion is indicated to be configured in a total of <NUM> slots up to the last slot in the <NUM> SCS.

Additionally, in the case of <NUM> SCS, two out of a maximum of <NUM> configuration methods may be used. In the case of <NUM> SCS, two out of a maximum of <NUM> configuration methods may be used.

Briefly, the BS may indicate, through higher layer signaling (e.g., SIB or dedicated RRC signaling), N configuration methods and even the number of slots indicated by each of the N configuration methods. For example, when N = <NUM>, there are a total of two configuration methods. The first configuration method (configuration method <NUM>-<NUM>-<NUM>) is to configure a PRACH transmission occasion in X (consecutive) slots, and the second configuration method (configuration method <NUM>-<NUM>-<NUM>) is to configure a PRACH transmission occasion in Y (consecutive) slots. Specifically, as many consecutive slots (up to the rear end) as the number of slots corresponding to X and Y may be configured as a PRACH transmission occasion. Alternatively, X or Y slots may be consecutive slots, but the BS may indicate a set of slots with a Z-slot gap between the slots (e.g., the previously defined parameter "Number of PRACH slots within a <NUM> slot" may be set to X and Y, and then the X slots or Y slots up to the rear end among the slots overlapping the <NUM> reference slot may be selected).

An example of option <NUM>-<NUM> is shown in <FIG> shows a case where a PRACH transmission occasion is indicated to be configured in a total of X and Y slots up to the last slot in the <NUM> SCS (e.g., X=<NUM>, Y=<NUM>).

It has been proposed that the positions of the RACH slots correspond to a specific number of slots (as consecutive slots or with a Z-slot gap therebetween) up to the rear end. The positions of the RACH slots may be configured in a method other than the method of configuring a specific number of slots up to the rear end. For example, when N=<NUM>, a PRACH transmission occasion may be configured in X slots up to the last slot according to a specific number (e.g., X) for configuration method <NUM>-<NUM>-<NUM>, and then a PRACH transmission occasion may be configured in Y slots from the slot before the X slots according to a specific number (e.g., Y) for configuration method <NUM>-<NUM>-<NUM>. With this configuration, X slots up to the last slot and Y slots thereafter may be used for PRACH transmission occasions.

This configuration may be represented as shown in <FIG> shows a case where it is indicated that a PRACH transmission occasion is to be configured in a total of X slots up to the last slot in the <NUM> SCS, and a PRACH transmission occasion is to be configured in Y slots from the next slot before the X slots (e.g., X=<NUM>, Y=<NUM>).

As another example, when N = <NUM>, X slots up to the last slot as many as a specific number (e.g., X) for configuration method <NUM>-<NUM>-<NUM> may be used for a PRACH transmission occasion, and Y slots up to the last slot in which the <NUM> SCS reference slot is divided in half, as many as a specific number (e.g., Y) for configuration method <NUM>-<NUM>-<NUM>, may be used for a PRACH transmission occasion.

This configuration may be represented as shown in <FIG> shows a case where it is indicated that a PRACH transmission occasion is to be configured in the X slots up to the last slot in the <NUM> SCS, and a PRACH transmission occasion is to be configured in the Y slots up to the last slot in which the <NUM> SCS reference slot is divided in half (e.g., X=<NUM>, Y=<NUM>).

Additionally, when slot groups corresponding to the respective configuration methods are not defined as they overlap in time as described above, a configuration method for selecting both slot groups may be added. As an example, when N = <NUM>, X slots up to the last slot as many as a specific number (e.g., X) for configuration method <NUM>-<NUM>-<NUM> may be used for a PRACH transmission occasion, and a PRACH transmission occasion may be configured in Y slots from the slot after the X slots as many as a specific number (e.g., Y) for configuration method <NUM>-<NUM>-<NUM>. Finally, as a third configuration method (configuration method <NUM>-<NUM>-<NUM>), slots corresponding to both X and Y may be configured for PRACH transmission occasions.

The above proposed methods may be used independently, or two or more of the proposed methods may be combined.

In addition, examples of the above-described proposed methods may also be included as one of the implementation methods of the present disclosure, and therefore it is apparent that they may be regarded as a kind of proposed methods. In addition, the above-described proposed methods may be implemented independently, or may be implemented by combining (or merging) some of the proposed methods. A rule may be defined such that the BS may provide the UE with information about whether the proposed methods are to be applied (or information about the rules of the proposed methods) through a predefined signal (e.g., a physical layer signal or a higher layer signal). The higher layer may include, for example, one or more of functional layers such as MAC, RLC, PDCP, RRC, and SDAP.

The UE may perform a DRX operation, while performing the aforedescribed/proposed procedures and/or methods. A UE configured with DRX may reduce power consumption by discontinuously receiving a DL signal. DRX may be performed in an RRC_IDLE state, an RRC_INACTIVE state, and an RRC_CONNECTED stated. DRX is used for discontinuous reception of a paging signal in the RRC_IDLE state and the RRC_INACTIVE state. Now, DRX performed in the RRC _CONNECTED state (RRC_CONNECTED DRX) will be described below.

<FIG> is a diagram illustrating a DRX cycle (RRC_CONNECTED state).

Referring to <FIG>, the DRX cycle includes On Duration and Opportunity for DRX. The DRX cycle defines a time interval in which On Duration is periodically repeated. On Duration is a time period during which the UE monitors to receive a PDCCH. When DRX is configured, the UE performs PDCCH monitoring during the On Duration. When there is any successfully detected PDCCH during the PDCCH monitoring, the UE operates an inactivity timer and is maintained in an awake state. On the other hand, when there is no successfully detected PDCCH during the PDCCH monitoring, the UE enters a sleep state, when the On Duration ends. Therefore, if DRX is configured, PDCCH monitoring/reception may be performed discontinuously in the time domain, when the afore-described/proposed procedures and/or methods are performed. For example, if DRX is configured, PDCCH reception occasions (e.g., slots having PDCCH search spaces) may be configured discontinuously according to a DRX configuration in the present disclosure. On the contrary, if DRX is not configured, PDCCH monitoring/reception may be performed continuously in the time domain, when the afore-described/proposed procedures and/or methods are performed. For example, if DRX is not configured, PDCCH reception occasions (e.g., slots having PDCCH search spaces) may be configured continuously in the present disclosure. PDCCH monitoring may be limited in a time period configured as a measurement gap, irrespective of whether DRX is configured.

Table <NUM> describes a UE operation related to DRX (in the RRC_CONNECTED state). Referring to Table <NUM>, DRX configuration information is received by higher-layer (RRC) signaling, and DRX ON/OFF is controlled by a DRX command of the MAC layer. Once DRX is configured, the UE performs PDCCH monitoring discontinuously in performing the described/proposed procedures and/or methods according to the present disclosure, as illustrated in <FIG>.

MAC-CellGroupConfig includes configuration information required to configure MAC parameters for a cell group. MAC-CellGroupConfig may also include DRX configuration information. For example, MAC-CellGroupConfig may include the following information in defining DRX.

When at least one of drx-OnDurationTimer, drx-InactivityTimer, drx-HARQ-RTT-TimerDL, or drx-HARQ-RTT-TimerDL is running, the UE performs PDCCH monitoring in each PDCCH occasion, while staying in the awake state.

Before or after the operations described in each embodiment of the present disclosure, the UE may perform a DRX-related operation. For example, the UE may perform the DRX operation after the random access procedure is completed according to the above-described embodiment.

One or more of the operations described above may be combined to implement embodiments.

One of the embodiments implemented by the combination of the operations described above may be configured as shown in <FIG>.

The UE performs a random access procedure (S3401), and monitors the PDCCH in an on duration based on the configured DRX operation (S3403). In addition, the UE operates an inactivity timer based on the PDCCH successfully received in the on duration (S3405).

When the UE performs the operation described in <FIG>, a random access preamble is transmitted during a random access procedure. A PRACH transmission occasion for transmission of the random access preamble transmission is determined by combining one or more of the operations described in proposed methods <NUM> to <NUM>.

For example, according to proposed method <NUM>, when a random access preamble is transmitted based on one of the SCS configuration values <NUM> and <NUM>, the value for the PRACH slot used as an input value of Equation <NUM> may be reinterpreted as a first slot or a second slot instead of <NUM> or <NUM> in <FIG>.

Specifically, referring to proposed method <NUM> and <FIG>, when the random access preamble is transmitted based on one of the SCS configuration values <NUM> and <NUM>, the SCS configuration value for the reference slot is <NUM> (because Number of PRACH slots is within a <NUM> slot).

According to proposed method <NUM>, when one of the SCS configuration values <NUM> and <NUM> is applied to a slot in which a random access preamble is transmitted, if the number of PRACH slots within the reference slot (a <NUM> slot) is equal to <NUM>, the value for the PRACH slot, <NUM>, may be reinterpreted as the value of the second slot, b. In proposed method <NUM>, the value of the second slot, b is the greatest value among <NUM> to N-<NUM>. Accordingly, when the value of u is <NUM>, b corresponds to <NUM>. When the value of u is <NUM>, b corresponds to <NUM>.

When one of the SCS configuration values <NUM> and <NUM> is applied to a slot in which a random access preamble is transmitted, if the number of PRACH slots in the reference slot is not <NUM> (otherwise, <NUM>), <NUM> between <NUM> and <NUM>, which are the values of PRACH slots, may be reinterpreted as the value for the first slot, a, and <NUM> as the value for the second slot, b. In Proposed Method <NUM>, the value for the second slot, b is the greatest value among <NUM> to N-<NUM>. Accordingly, when the value of u is <NUM>, b corresponds to <NUM>. When the value of u is <NUM>, b corresponds to <NUM>. In proposed method <NUM>, when a, the value for the first slot, is N/<NUM>-<NUM>, b corresponds to <NUM> if the value of u is <NUM>. If the value of u is <NUM>, b corresponds to <NUM>. A modified example of <FIG> in consideration that a, the value for the first slot, is N/<NUM>-<NUM> is shown in <FIG>. In proposed method <NUM>, when a, the value for the first slot, is N-<NUM>, b corresponds to <NUM> if the value of u is <NUM>. If the value of u is <NUM>, b corresponds to <NUM>. A modified example of <FIG> in consideration that a, the value for the first slot, is N-<NUM> is shown in <FIG>.

In other words, according to proposed method <NUM>, the SCS configuration value for the reference slot for determining the PRACH slot(s) is <NUM> based on PRACH being transmitted within one or two PRACH slots to which one of the SCS configuration values <NUM> and <NUM> is applied. Accordingly, the one or two PRACH slots are determined among N slots corresponding to the reference slot to which the SCS configuration value <NUM> is applied. Since N is determined based on the ratio between SCSs, N=<NUM> if u is <NUM>, and N=<NUM> if u is <NUM>.

Referring to proposed method <NUM> and <FIG>, <FIG>, <FIG>, based on that the number of PRACH slots within the reference slot is <NUM>, one PRACH slot is used, and the value for the PRACH slot is N-<NUM>. In addition, based on that the number of PRACH slots within the slot is not <NUM>, two PRACH slots are used, and the values for the PRACH slots are N/<NUM>-<NUM> and N-<NUM>. In addition, based on that the number of PRACH slots within the slot is not <NUM>, two PRACH slots are used, and the values for the PRACH slots may be N-<NUM> and N-<NUM>.

In addition to the operation of <FIG> described above, one or more of the operations described with reference to <FIG> and/or the operations described in Sections <NUM> to <NUM> may be combined and additionally performed.

The various descriptions, functions, procedures, proposals, methods, and/or operation flowcharts of the present disclosure described herein may be applied to, but not limited to, various fields requiring wireless communication/connectivity (e.g., <NUM>) between devices.

More specific examples will be described below with reference to the drawings. In the following drawings/description, like reference numerals denote the same or corresponding hardware blocks, software blocks, or function blocks, unless otherwise specified.

Referring to <FIG>, the communication system <NUM> applied to the present disclosure includes wireless devices, BSs, and a network. A wireless device is a device performing communication using radio access technology (RAT) (e.g., <NUM> NR (or New RAT) or LTE), also referred to as a communication/radio/<NUM> device. The wireless devices may include, not limited to, a robot 100a, vehicles 100b-<NUM> and 100b-<NUM>, an extended reality (XR) device 100c, a hand-held device 100d, a home appliance 100e, an IoT device 100f, and an artificial intelligence (AI) device/server <NUM>. For example, the vehicles may include a vehicle having a wireless communication function, an autonomous driving vehicle, and a vehicle capable of vehicle-to-vehicle (V2V) communication. Herein, the vehicles may include an unmanned aerial vehicle (UAV) (e.g., a drone). The XR device may include an augmented reality (AR)/virtual reality (VR)/mixed reality (MR) device and may be implemented in the form of a head-mounted device (HMD), a head-up display (HUD) mounted in a vehicle, a television (TV), a smartphone, a computer, a wearable device, a home appliance, a digital signage, a vehicle, a robot, and so on. The hand-held device may include a smartphone, a smart pad, a wearable device (e.g., a smart watch or smart glasses), and a computer (e.g., a laptop). The home appliance may include a TV, a refrigerator, a washing machine, and so on. The IoT device may include a sensor, a smart meter, and so on. For example, the BSs and the network may be implemented as wireless devices, and a specific wireless device 200a may operate as a BS/network node for other wireless devices.

An 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> via the network <NUM>. Although the wireless devices 100a to 100f may communicate with each other through the BSs <NUM>/network <NUM>, the wireless devices 100a to 100f may perform direct communication (e.g., sidelink communication) with each other without intervention of the BSs/network. For example, the vehicles 100b-<NUM> and 100b-<NUM> may perform direct communication (e.g., V2V/vehicle-to-everything (V2X) communication).

Wireless communication/connections 150a, 150b, and 150c may be established between the wireless devices 100a to 100f/BS <NUM> and between the BSs <NUM>. Herein, the wireless communication/connections may be established through various RATs (e.g., <NUM> NR) such as UL/DL communication 150a, sidelink communication 150b (or, D2D communication), or inter-BS communication (e.g., relay or integrated access backhaul (IAB)). Wireless signals may be transmitted and received between the wireless devices, between the wireless devices and the BSs, and between the BSs through the wireless communication/connections 150a, 150b, and 150c. For example, signals may be transmitted and receive don various physical channels through the wireless communication/connections 150a, 150b and 150c. To this end, at least a part of various configuration information configuring processes, various signal processing processes (e.g., channel encoding/decoding, modulation/demodulation, and resource mapping/demapping), and resource allocation processes, for transmitting/receiving wireless signals, may be performed based on the various proposals of the present disclosure.

Referring to <FIG>, a first wireless device <NUM> and a second wireless device <NUM> may transmit wireless signals through a variety of RATs (e.g., LTE and NR). {The first wireless device <NUM> and the second wireless device <NUM>} may correspond to {the wireless device 100x and the BS <NUM>} and/or {the wireless device 100x and the wireless device 100x} of <FIG>.

The first wireless device <NUM> may include one or more processors <NUM> and one or more memories <NUM>, and further include one or more transceivers <NUM> and/or one or more antennas <NUM>. The processor(s) <NUM> may control the memory(s) <NUM> and/or the transceiver(s) <NUM> and may be configured to implement the descriptions, functions, procedures, proposals, methods, and/or operation flowcharts disclosed in this document. For example, the processor(s) <NUM> may process information in the memory(s) <NUM> to generate first information/signals and then transmit wireless signals including the first information/signals through the transceiver(s) <NUM>. The processor(s) <NUM> may receive wireless signals including second information/signals through the transceiver(s) <NUM> and then store information obtained by processing the second information/signals in the memory(s) <NUM>. The memory(s) <NUM> may be connected to the processor(s) <NUM> and may store various pieces of information related to operations of the processor(s) <NUM>. For example, the memory(s) <NUM> may store software code including instructions for performing all or a part of processes controlled by the processor(s) <NUM> or for performing the descriptions, functions, procedures, proposals, methods, and/or operation flowcharts disclosed in this document. The processor(s) <NUM> and the memory(s) <NUM> may be a part of a communication modem/circuit/chip designed to implement RAT (e.g., LTE or NR). The transceiver(s) <NUM> may be connected to the processor(s) <NUM> and transmit and/or receive wireless signals through the one or more antennas <NUM>. The transceiver(s) <NUM> may be interchangeably used with radio frequency (RF) unit(s). In the present disclosure, the wireless device may be a communication modem/circuit/chip.

The second wireless device <NUM> may include one or more processors <NUM> and one or more memories <NUM>, and further include one or more transceivers <NUM> and/or one or more antennas <NUM>. The processor(s) <NUM> may control the memory(s) <NUM> and/or the transceiver(s) <NUM> and may be configured to implement the descriptions, functions, procedures, proposals, methods, and/or operation flowcharts disclosed in this document. For example, the processor(s) <NUM> may process information in the memory(s) <NUM> to generate third information/signals and then transmit wireless signals including the third information/signals through the transceiver(s) <NUM>. The processor(s) <NUM> may receive wireless signals including fourth information/signals through the transceiver(s) <NUM> and then store information obtained by processing the fourth information/signals in the memory(s) <NUM>. The memory(s) <NUM> may be connected to the processor(s) <NUM> and store various pieces of information related to operations of the processor(s) <NUM>. For example, the memory(s) <NUM> may store software code including instructions for performing all or a part of processes controlled by the processor(s) <NUM> or for performing the descriptions, functions, procedures, proposals, methods, and/or operation flowcharts disclosed in this document. The processor(s) <NUM> and the memory(s) <NUM> may be a part of a communication modem/circuit/chip designed to implement RAT (e.g., LTE or NR). The transceiver(s) <NUM> may be connected to the processor(s) <NUM> and transmit and/or receive wireless signals through the one or more antennas <NUM>. In the present disclosure, the wireless device may be a communication modem/circuit/chip.

Now, hardware elements of the wireless devices <NUM> and <NUM> will be described in greater detail. One or more protocol layers may be implemented by, not limited to, one or more processors <NUM> and <NUM>. For example, the one or more processors <NUM> and <NUM> may implement one or more layers (e.g., functional layers such as physical (PHY), medium access control (MAC), radio link control (RLC), packet data convergence protocol (PDCP), RRC, and service data adaptation protocol (SDAP)). The one or more processors <NUM> and <NUM> may generate one or more protocol data units (PDUs) and/or one or more service data Units (SDUs) according to the descriptions, functions, procedures, proposals, methods, and/or operation flowcharts disclosed in this document. The one or more processors <NUM> and <NUM> may generate messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and/or operation flowcharts disclosed in this document and provide the messages, control information, data, or information to one or more transceivers <NUM> and <NUM>. The one or more processors <NUM> and <NUM> may generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and/or operation flowcharts disclosed in this document and provide the generated signals to the one or more transceivers <NUM> and <NUM>. The one or more processors <NUM> and <NUM> may receive the signals (e.g., baseband signals) from the one or more transceivers <NUM> and <NUM> and acquire the PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and/or operation flowcharts disclosed in this document.

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 the one or more processors <NUM> and <NUM>. The descriptions, functions, procedures, proposals, methods, and/or operation flowcharts disclosed in this document may be implemented using firmware or software, and the firmware or software may be configured to include the modules, procedures, or functions. Firmware or software configured to perform the descriptions, functions, procedures, proposals, methods, and/or operation flowcharts disclosed in this document may be included in the one or more processors <NUM> and <NUM> or may be stored in the one or more memories <NUM> and <NUM> and executed by the one or more processors <NUM> and <NUM>. The descriptions, functions, procedures, proposals, methods, and/or operation flowcharts disclosed in this document may be implemented using firmware or software in the form of code, an instruction, and/or a set of instructions.

The one or more memories <NUM> and <NUM> may be configured to include read-only memories (ROMs), random access memories (RAMs), electrically erasable programmable read-only memories (EPROMs), flash memories, hard drives, registers, cash memories, computer-readable storage media, and/or combinations thereof.

The one or more transceivers <NUM> and <NUM> may transmit user data, control information, and/or wireless signals/channels, mentioned in the methods and/or operation flowcharts of this document, to one or more other devices. The one or more transceivers <NUM> and <NUM> may receive user data, control information, and/or wireless signals/channels, mentioned in the descriptions, functions, procedures, proposals, methods, and/or operation flowcharts disclosed in this document, from one or more other devices. For example, the one or more transceivers <NUM> and <NUM> may be connected to the one or more processors <NUM> and <NUM> and transmit and receive wireless signals. For example, the one or more processors <NUM> and <NUM> may perform control so that the one or more transceivers <NUM> and <NUM> may transmit user data, control information, or wireless signals to one or more other devices. The one or more processors <NUM> and <NUM> may perform control so that the one or more transceivers <NUM> and <NUM> may receive user data, control information, or wireless signals from one or more other devices. The one or more transceivers <NUM> and <NUM> may be connected to the one or more antennas <NUM> and <NUM> and the one or more transceivers <NUM> and <NUM> may be configured to transmit and receive user data, control information, and/or wireless signals/channels, mentioned in the descriptions, functions, procedures, proposals, methods, and/or operation flowcharts disclosed in this document, through the one or more antennas <NUM> and <NUM>. The one or more transceivers <NUM> and <NUM> may convert received wireless signals/channels from RF band signals into baseband signals in order to process received user data, control information, and wireless signals/channels using the one or more processors <NUM> and <NUM>. The one or more transceivers <NUM> and <NUM> may convert the user data, control information, and wireless signals/channels processed using the one or more processors <NUM> and <NUM> from the baseband signals into the RF band signals.

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

Referring to <FIG>, wireless devices <NUM> and <NUM> may correspond to the wireless devices <NUM> and <NUM> of <FIG> and may be configured to include various elements, components, units/portions, and/or modules. The communication unit <NUM> may include a communication circuit <NUM> and transceiver(s) <NUM>. The control unit <NUM> is electrically connected to the communication unit <NUM>, the memory <NUM>, and the additional components <NUM> and provides overall control to the wireless device. For example, the control unit <NUM> may control an electric/mechanical operation of the wireless device based on programs/code/instructions/information stored in the memory unit <NUM>. The control unit <NUM> may transmit the information stored in the memory unit <NUM> to the outside (e.g., other communication devices) via the communication unit <NUM> through a wireless/wired interface or store, in the memory unit <NUM>, information received through the wireless/wired interface from the outside (e.g., other communication devices) via the communication unit <NUM>.

The additional components <NUM> may be configured in various manners according to type of the wireless device. The wireless device may be implemented in the form of, not limited to, the robot (100a of <FIG>), the vehicles (100b-<NUM> and 100b-<NUM> of <FIG>), the XR device (100c of <FIG>), the hand-held device (100d of <FIG>), the home appliance (100e of <FIG>), the IoT device (100f of <FIG>), a digital broadcasting terminal, a hologram device, a public safety device, an MTC device, a medical device, a FinTech device (or a finance device), a security device, a climate/environment device, the AI server/device (<NUM> of <FIG>), the BSs (<NUM> of <FIG>), a network node, or the like. The wireless device may be mobile or fixed according to a use case/service.

In <FIG>, all of the various elements, components, units/portions, and/or modules in the wireless devices <NUM> and <NUM> may be connected to each other through a wired interface or at least a part thereof may be wirelessly connected through the communication unit <NUM>. Each element, component, unit/portion, and/or module in the wireless devices <NUM> and <NUM> may further include one or more elements. For example, the control unit <NUM> may be configured with a set of one or more processors. For example, the control unit <NUM> may be configured with a set of a communication control processor, an application processor, an electronic control unit (ECU), a graphical processing unit, and a memory control processor. In another example, the memory <NUM> may be configured with a RAM, a dynamic RAM (DRAM), a ROM, a flash memory, a volatile memory, a non-volatile memory, and/or a combination thereof.

<FIG> illustrates a vehicle or an autonomous driving vehicle applied to the present disclosure. The vehicle or autonomous driving vehicle may be implemented as a mobile robot, a car, a train, a manned/unmanned aerial vehicle (AV), a ship, or the like.

Referring to <FIG>, a vehicle or autonomous driving 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, a sensor unit 140c, and an autonomous driving unit 140d.

The control unit <NUM> may perform various operations by controlling elements of the vehicle or the autonomous driving vehicle <NUM>. The control unit <NUM> may include an ECU. The driving unit 140a may enable the vehicle or the autonomous driving vehicle <NUM> to drive on a road. The driving unit 140a may include an engine, a motor, a powertrain, a wheel, a brake, a steering device, and so on. The power supply unit 140b may supply power to the vehicle or the autonomous driving vehicle <NUM> and include a wired/wireless charging circuit, a battery, and so on. The sensor unit 140c may acquire information about a vehicle state, ambient environment information, user information, and so on. The sensor unit 140c may include an inertial measurement unit (IMU) sensor, a collision sensor, a wheel sensor, a speed sensor, a slope sensor, a weight sensor, a heading sensor, a position module, a vehicle forward/backward sensor, a battery sensor, a fuel sensor, a tire sensor, a steering sensor, a temperature sensor, a humidity sensor, an ultrasonic sensor, an illumination sensor, a pedal position sensor, and so on. The autonomous driving unit 140d may implement technology for maintaining a lane on which the vehicle is driving, technology for automatically adjusting speed, such as adaptive cruise control, technology for autonomously driving along a determined path, technology for driving by automatically setting a route if a destination is set, and the like.

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

Claim 1:
A method for transmitting and receiving signals by a user equipment in a wireless communication system, the method comprising:
performing (S3401) a random access procedure;
after performing the random access procedure, monitoring (S3403) a Physical Downlink Control Channel, PDCCH, for an on duration based on configured Discontinuous Reception, DRX; and
based on the PDCCH successfully received for the on duration, operating (S3405) an inactivity timer,
wherein, during the random access procedure, a random access preamble is transmitted in one or two Physical Random Access Channel, PRACH, slots,
wherein the one or two PRACH slots are determined among N slots, wherein the N slots are within a reference slot,
wherein, based on a SubCarrier Spacing, SCS, configuration value applied to the N slots being <NUM> and based on an SCS configuration value for the reference slot being <NUM>, N is <NUM>, and
wherein, based on the SCS configuration value applied to the N slots being <NUM> and based on the SCS configuration value for the reference slot being <NUM>, N is <NUM>.