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

Abstract

The present disclosure relates to a method performed by a user equipment in a wireless communication system and an apparatus supporting the method, and more particularly to a method and an apparatus supporting the method, the method comprising the following steps: obtaining a message A related to a random access procedure; sending the message A; and receiving a message B related to the random access procedure in response to the message A, wherein the message A includes a physical random access channel (PRACH) preamble and a physical uplink shared channel (PUSCH); sending the PUSCH based on the received information related to the PUSCH configuration for the message A; based on the information related to the PUSCH configuration including information related to an indication of a code division multiplexing (CDM) group of a demodulation reference signal (DMRS) for the PUSCH, the CDM group is set to a group indicated by information related to the indication of the CDM group among two predetermined groups; performing communication after the random access procedure; based on the communication, receiving a physical downlink shared channel (PDSCH); and based on discontinuous reception (DRX) being set, monitoring a physical downlink control channel (PDCCH) for the PDSCH within an on-duration related to the DRX.

Description

Technical Field

[0001] Embodiments of the present disclosure relate to wireless communication systems. Background Art

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

[0003] Technical issues

[0004] Various embodiments may provide a method of transmitting and receiving a signal in a wireless communication system and an apparatus for supporting the method.

[0005] Various embodiments may provide a method for a 2-step random access channel (RACH) procedure in a wireless communication system and an apparatus for supporting the method.

[0006] Various embodiments may provide a method for configuring a physical uplink shared channel (PUSCH) demodulation reference signal (DMRS) and an apparatus for supporting the method in a wireless communication system.

[0007] Various embodiments may provide a method for mapping a preamble to a PUSCH opportunity in a wireless communication system and an apparatus for supporting the method.

[0008] Those skilled in the art will understand that the purposes that can be achieved by various embodiments of the present disclosure are not limited to the contents specifically described above, and the above and other purposes that can be achieved by various embodiments of the present disclosure will be more clearly understood from the following detailed description.

[0009] Technical Solution

[0010] Various embodiments may provide a method of transmitting and receiving a signal in a wireless communication system and an apparatus for supporting the method.

[0011] According to various embodiments, a method performed by a user equipment (UE) in a wireless communication system may be provided.

[0012] According to various embodiments, the method may include the following steps: obtaining a message A related to a random access procedure; sending the message A; and receiving a message B related to the random access procedure in response to the message A.

[0013] According to various embodiments, message A may include a physical random access channel (PRACH) preamble and a physical uplink shared channel (PUSCH).

[0014] According to various embodiments, the PUSCH may be sent based on received information related to the PUSCH configuration for message A.

[0015] According to various embodiments, based on the fact that the information related to the PUSCH configuration includes information related to an indication of a code division multiplexing (CDM) group for a demodulation reference signal (DMRS) for the PUSCH, the CDM group may be configured as a group indicated by the information related to the indication of the CDM group, one of two predetermined groups.

[0016] According to various embodiments, communication may be performed after a random access procedure.

[0017] According to various embodiments, a physical downlink control channel (PDSCH) may be received based on the communication.

[0018] According to various embodiments, based on the configuration of discontinuous reception (DRX), a physical downlink control channel (PDCCH) for the PDSCH may be monitored during the DRX-related on-duration.

[0019] According to various embodiments, based on the fact that the information related to the PUSCH configuration does not include information related to the indication of the CDM group, the CDM group may be configured as two predetermined groups.

[0020] According to various embodiments, the number of ports used for DMRS may be determined in the set of {1, 2, 4}.

[0021] According to various embodiments, based on the disabled transform precoding for PUSCH, two different identifiers (IDs) related to identifying a sequence for initialization of a pseudo-random sequence generator related to sequence generation of a DMRS may be obtained based on two different higher layer parameters, respectively.

[0022] According to various embodiments, a scrambling ID (SCID) associated with an index identifying two different IDs is determined based on a PRACH preamble.

[0023] According to various embodiments, based on transform precoding being enabled, an ID associated with identifying a sequence for initialization of a pseudo-random sequence generator may be obtained based on higher layer parameters.

[0024] According to various embodiments, the PRACH preamble may be obtained from among a plurality of PRACH preambles.

[0025] According to various embodiments, the SCID may be determined based on a mapping between a plurality of preambles and PUSCH opportunities for transmitting the PUSCH.

[0026] According to various embodiments, an apparatus configured to operate in a wireless communication system may be provided.

[0027] According to various embodiments, the apparatus may include: a memory; and at least one processor connected to the memory.

[0028] According to various embodiments, at least one processor may be configured to: obtain a message A related to a random access procedure; send the message A; and receive a message B related to the random access procedure in response to the message A.

[0029] According to various embodiments, message A may include a PRACH preamble and a PUSCH.

[0030] According to various embodiments, the PUSCH may be sent based on received information related to the PUSCH configuration for message A.

[0031] According to various embodiments, based on the information related to PUSCH configuration including information related to indication of a CDM group for a DMRS of a PUSCH, the CDM group may be configured as a group indicated by the information related to indication of the CDM group, of two predetermined groups.

[0032] According to various embodiments, communication may be performed after a random access procedure.

[0033] According to various embodiments, the PDSCH may be received based on the communication.

[0034] According to various embodiments, based on the DRX configuration, the PDCCH for the PDSCH may be monitored during the DRX-related On-Duration.

[0035] According to various embodiments, based on the fact that the information related to the PUSCH configuration does not include information related to the indication of the CDM group, the CDM group may be configured as two predetermined groups.

[0036] According to various embodiments, the number of ports used for DMRS may be determined in the set of {1, 2, 4}.

[0037] According to various embodiments, based on the disabled transform precoding for PUSCH, two different identifiers (IDs) related to identifying a sequence for initialization of a pseudo-random sequence generator related to sequence generation of a DMRS may be obtained based on two different higher layer parameters, respectively.

[0038] According to various embodiments, a scrambling ID (SCID) associated with an index identifying two different IDs is determined based on a PRACH preamble.

[0039] According to various embodiments, the device may communicate with at least one of a mobile terminal, a network, or an autonomous driving vehicle other than a vehicle including the device.

[0040] According to various embodiments, a method performed by a base station (BS) in a wireless communication system may be provided.

[0041] According to various embodiments, the method may include the following steps: receiving a message A related to a random access procedure; obtaining a PRACH preamble and a PUSCH based on the message A; and sending a message B related to the random access procedure in response to the message A.

[0042] According to various embodiments, the PUSCH may be obtained based on the transmitted information related to the PUSCH configuration for message A.

[0043] According to various embodiments, based on the information related to PUSCH configuration including information related to indication of a CDM group for a DMRS of a PUSCH, the CDM group may be configured as a group indicated by the information related to indication of the CDM group, of two predetermined groups.

[0044] According to various embodiments, communication may be performed after a random access procedure.

[0045] According to various embodiments, the physical PDSCH may be transmitted based on the communication.

[0046] According to various embodiments, based on the configuration of discontinuous reception (DRX), the PDCCH for the PDSCH may be transmitted during the on-duration associated with the DRX.

[0047] According to various embodiments, an apparatus configured to operate in a wireless communication system may be provided.

[0048] According to various embodiments, the apparatus may include: a memory; and at least one processor connected to the memory.

[0049] According to various embodiments, at least one processor may be configured to: receive message A related to a random access procedure; obtain a PRACH preamble and a PUSCH based on message A; and send message B related to the random access procedure in response to message A.

[0050] According to various embodiments, the PUSCH may be obtained based on the transmitted information related to the PUSCH configuration for message A.

[0051] According to various embodiments, based on the information related to PUSCH configuration including information related to indication of a CDM group for a DMRS of a PUSCH, the CDM group may be configured as a group indicated by the information related to indication of the CDM group, of two predetermined groups.

[0052] According to various embodiments, communication may be performed after a random access procedure.

[0053] According to various embodiments, the PDSCH may be transmitted based on the communication.

[0054] According to various embodiments, based on the configuration of discontinuous reception (DRX), the PDCCH for the PDSCH may be transmitted during the on-duration associated with the DRX.

[0055] According to various embodiments, an apparatus configured to operate in a wireless communication system may be provided.

[0056] According to various embodiments, the apparatus may include: at least one processor; and at least one memory configured to store one or more instructions for causing the at least one processor to perform a method.

[0057] According to various embodiments, the method may include the following steps: obtaining a message A related to a random access procedure; sending the message A; and receiving a message B related to the random access procedure in response to the message A.

[0058] According to various embodiments, message A may include a PRACH preamble and a PUSCH.

[0059] According to various embodiments, the PUSCH may be sent based on received information related to the PUSCH configuration for message A.

[0060] According to various embodiments, based on the information related to PUSCH configuration including information related to indication of a CDM group for a DMRS of a PUSCH, the CDM group may be configured as a group indicated by the information related to indication of the CDM group, of two predetermined groups.

[0061] According to various embodiments, communication may be performed after a random access procedure.

[0062] According to various embodiments, the PDSCH may be received based on the communication.

[0063] According to various embodiments, based on the DRX configuration, the PDCCH for the PDSCH may be monitored during the DRX-related On-Duration.

[0064] According to various embodiments, a processor-readable medium may be provided that is configured to store one or more instructions for causing at least one processor to perform a method.

[0065] According to various embodiments, the method may include the following steps: obtaining a message A related to a random access procedure; sending the message A; and receiving a message B related to the random access procedure in response to the message A.

[0066] According to various embodiments, message A may include a PRACH preamble and a PUSCH.

[0067] According to various embodiments, the PUSCH may be sent based on received information related to the PUSCH configuration for message A.

[0068] According to various embodiments, based on the information related to PUSCH configuration including information related to indication of a CDM group for a DMRS of a PUSCH, the CDM group may be configured as a group indicated by the information related to indication of the CDM group, of two predetermined groups.

[0069] According to various embodiments, communication may be performed after a random access procedure.

[0070] According to various embodiments, the PDSCH may be received based on the communication.

[0071] According to various embodiments, based on the DRX configuration, the PDCCH for the PDSCH may be monitored during the DRX-related On-Duration.

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

[0073] Beneficial effects

[0074] According to various embodiments, signals can be efficiently transmitted and received in a wireless communication system.

[0075] According to various embodiments, Message A physical uplink shared channel (PUSCH) demodulation reference signal (DMRS) resources (eg, DMRS ports / sequences, etc.) may be efficiently used.

[0076] According to various embodiments, the preamble may be used efficiently.

[0077] Those skilled in the art will appreciate that the effects that can be achieved by various embodiments of the present invention are not limited to the effects described above, and other advantageous effects of various embodiments of the present invention will be more clearly understood from the following detailed description. In other words, those skilled in the art can deduce unexpected effects according to the embodiments of the present invention from the various embodiments of the present invention. BRIEF DESCRIPTION OF THE DRAWINGS

[0078] The accompanying drawings, which are included to provide a further understanding of the various embodiments of the present disclosure, provide various embodiments of the present disclosure and detailed descriptions. However, the technical characteristics of the various embodiments of the present disclosure are not limited to the specific drawings. The features disclosed in each drawing can be combined with each other to configure new embodiments. The reference numerals in each drawing correspond to structural elements.

[0079] Figure 1 is a diagram illustrating physical channels and a signal transmission method using the physical channels that can be used in various embodiments of the present disclosure.

[0080] Figure 2 This is a diagram illustrating a radio frame structure in a new radio access technology (NR) system to which various embodiments of the present disclosure are applicable.

[0081] Figure 3 This is a diagram illustrating a time slot structure in a New Radio (NR) system to which various embodiments of the present disclosure are applicable.

[0082] Figure 4 This is a diagram illustrating the mapping of physical channels in time slots to which various embodiments are applicable.

[0083] Figure 5 This is a diagram illustrating the structure of a synchronization signal block (SSB) to which various embodiments of the present disclosure are applicable.

[0084] Figure 6 is a diagram illustrating an exemplary SSB transmission method to which various embodiments of the present disclosure are applicable.

[0085] Figure 7 The acquisition of DL time synchronization information at a user equipment (UE) to which various embodiments of the present disclosure are applicable is illustrated.

[0086] Figure 8 The system information (SI) acquisition process applicable to various embodiments of the present disclosure is illustrated.

[0087] Figure 9 is a diagram illustrating an exemplary multi-beam transmission to which various embodiments are applicable.

[0088] Figure 10 This is a diagram illustrating a method of indicating an actually transmitted SSB (SSB_tx), to which various embodiments are applicable.

[0089] Figure 11 is a diagram illustrating an exemplary 4-step random access channel (RACH) procedure to which various embodiments of the present disclosure are applicable.

[0090] Figure 12 is a diagram illustrating an exemplary 2-step RACH procedure to which various embodiments of the present disclosure are applicable.

[0091] Figure 13 is a diagram illustrating an exemplary contention-free RACH procedure to which various embodiments of the present disclosure are applicable.

[0092] Figure 14 is a diagram illustrating transmission of an SSB and a physical random access channel (PRACH) resource linked to the SSB according to various embodiments of the present disclosure.

[0093] Figure 15 is a diagram illustrating transmission of an SSB and a PRACH resource linked to the SSB according to various embodiments of the present disclosure.

[0094] Figure 16 is a diagram illustrating an exemplary RACH opportunity configuration to which various embodiments of the present disclosure are applicable.

[0095] Figure 17 is a diagram schematically illustrating a method of operating a UE and a base station (BS) according to various embodiments of the present disclosure.

[0096] Figure 18 is a diagram schematically illustrating a method of operating a UE according to various embodiments.

[0097] Figure 19 is a diagram schematically illustrating a method of operating a BS according to various embodiments.

[0098] Figure 20 is a diagram illustrating an exemplary resource configuration for message A (MsgA) according to various embodiments.

[0099] Figure 21 is a diagram illustrating an exemplary MsgA configuration according to various embodiments.

[0100] Figure 22 is a diagram illustrating an exemplary MsgA configuration according to various embodiments.

[0101] Figure 23 is a diagram illustrating exemplary time domain locations for the MsgA RACH and the MsgA Physical Uplink Shared Channel (PUSCH) according to various embodiments.

[0102] Figure 24is a diagram illustrating an initial network access procedure and a subsequent communication procedure.

[0103] Figure 25 is an exemplary discontinuous reception (DRX) operation according to various embodiments of the present disclosure.

[0104] Figure 26 is a diagram schematically illustrating a method of operating a UE and a BS according to various embodiments.

[0105] Figure 27 is a flowchart illustrating a method of operating a UE according to various embodiments.

[0106] Figure 28 is a flowchart illustrating a method of operating a BS according to various embodiments.

[0107] Figure 29 It is a diagram illustrating a device for implementing various embodiments of the present disclosure.

[0108] Figure 30 An exemplary communication system to which various embodiments of the present disclosure are applied is illustrated.

[0109] Figure 31 An exemplary wireless device to which various embodiments of the present disclosure are applicable is illustrated.

[0110] Figure 32 Other exemplary wireless devices to which various embodiments of the present disclosure are applied are illustrated.

[0111] Figure 33 Exemplary portable devices to which various embodiments of the present disclosure are applied are illustrated.

[0112] Figure 34 An exemplary vehicle or autonomous vehicle illustrating various embodiments of the present disclosure is provided. DETAILED DESCRIPTION

[0113] Various embodiments are applicable to various radio access technologies such as code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), and single carrier frequency division multiple access (SC-FDMA). CDMA can be implemented as a radio technology such as Universal Terrestrial Radio Access (UTRA) or CDMA2000. TDMA can 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 can be implemented as a radio technology such as Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wireless Fidelity (Wi-Fi)), IEEE 802.16 (Worldwide Interoperability for Microwave Access (WiMAX)), IEEE 802.20, and Evolved UTRA (E-UTRA). UTRA is part of the Universal Mobile Telecommunications System (UMTS). 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) is part of Evolved UMTS (E-UMTS) using E-UTRA, and LTE-Advanced (A) is an evolved version of 3GPP LTE. 3GPP NR (New Radio or New Radio Access Technology) is an evolved version of 3GPP LTE / LTE-A.

[0114] For clarity of description, various embodiments are described in the context of 3GPP communication systems (e.g., including LTE, NR, 6G, and next-generation wireless communication systems), but the technical spirit of the various embodiments is not limited thereto. With respect to background technology, the terms and abbreviations used in the description of the various embodiments refer to technical specifications published before this disclosure. For example, you can refer to 3GPP TS 36.211, 3GPP TS 36.212, 3GPP TS 36.213, 3GPP TS 36.300, 3GPP TS 36.321, 3GPP TS 36.331, 3GPP TS 36.355, 3GPP TS 36.455, 3GPP TS 37.355, 3GPP TS 37.455, 3GPP TS 38.211, 3GPP TS 38.212, 3GPP TS 38.213, 3GPP TS 38.214, 3GPP TS 38.215, 3GPP TS 38.300, 3GPP TS 38.321, 3GPP TS 38.331, 3GPP TS 38.355, 3GPP TS 38.455, etc.

[0115] 1.3GPP system

[0116] 1.1. Physical Channels and Signal Transmission and Reception

[0117] In a wireless access system, a UE receives information from a base station (BS) on the downlink (DL) and transmits information to the BS on the uplink (UL). Information sent and received between the UE and BS includes general data and various types of control information. Depending on the type and purpose of the information sent and received between the BS and UE, various physical channels exist.

[0118] Figure 1 is a diagram illustrating physical channels that can be used in various embodiments of the present disclosure and a signal transmission method using the physical channels.

[0119] When a UE is powered on or enters a new cell, it performs an initial cell search (S11). The initial cell search involves acquiring synchronization with the base station (BS). Specifically, the UE synchronizes its timing with the BS and acquires information such as the cell identifier (ID) by receiving the Primary Synchronization Channel (P-SCH) and Secondary Synchronization Channel (S-SCH) from the BS.

[0120] The UE may then acquire information broadcast in the cell by receiving a physical broadcast channel (PBCH) from the BS.

[0121] During the initial cell search, the UE may monitor the DL channel status by receiving a downlink reference signal (DL RS).

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

[0123] Subsequently, to complete the connection with the BS, the UE may perform a random access procedure with the BS (S13 to S16). During the random access procedure, the UE may transmit a preamble on a physical random access channel (PRACH) (S13), and may receive a PDCCH and a random access response (RAR) for the preamble on a PDSCH associated with the PDCCH (S14). The UE may transmit a PUSCH using the scheduling information in the RAR (S15) and perform a contention resolution procedure, including receiving a PDCCH signal and a PDSCH signal corresponding to the PDCCH signal (S16).

[0124] When the random access procedure is performed in two steps, steps S13 and S15 may be performed in one operation for UE transmission, and steps S14 and S16 may be performed in one operation for BS transmission.

[0125] After the above process, in a general UL / DL signal transmission process, the UE may receive a PDCCH and / or a PDSCH from the BS ( S17 ) and transmit a physical uplink shared channel (PUSCH) and / or a physical uplink control channel (PUCCH) to the BS ( S18 ).

[0126] The control information sent by the UE to the BS is generally called UCI. UCI includes hybrid automatic repeat request acknowledgement / negative acknowledgement (HARQ-ACK / NACK), scheduling request (SR), channel quality indicator (CQI), precoding matrix index (PMI), rank indicator (RI), etc.

[0127] Typically, UCI is transmitted periodically on the PUCCH. However, if control information and service data should be transmitted simultaneously, the control information and service data can be transmitted on the PUSCH. In addition, UCI can be transmitted aperiodically on the PUSCH upon receiving a request / command from the network.

[0128] 1.2. Radio Frame Structure

[0129] Figure 2 This is a diagram illustrating a radio frame structure in an NR system to which various embodiments of the present disclosure are applicable.

[0130] NR systems can support multiple parameter sets. Parameter sets can be defined by subcarrier spacing (SCS) and cyclic prefix (CP) overhead. Multiple SCSs can be derived by scaling the default SCS by an integer N (or μ). Furthermore, even assuming that very small SCSs are not used at very high carrier frequencies, the parameter set to be used can be selected independently of the cell's frequency band. Furthermore, NR systems can support various frame structures based on multiple parameter sets.

[0131] Now, we will describe the OFDM parameter sets and frame structures that can be considered for the NR system. The multiple OFDM parameter sets supported by the NR system can be defined as listed in Table 1. For the bandwidth part (BWP), μ and CP are obtained from the RRC parameters provided by the BS.

[0132] [Table 1]

[0133] μ <![CDATA[Δf=2 μ ·15[kHz]]]> Cyclic prefix 0 15 normal 1 30 normal 2 60 Normal, Extended 3 120 normal 4 240 normal

[0134] In NR, multiple parameter sets (e.g., SCS) are supported to support various 5G services. For example, 15kHz SCS supports wide areas of the cellular band, 30kHz / 60kHz SCS supports dense urban areas, lower latency, and wider carrier bandwidth, and 60kHz or higher SCS supports bandwidths greater than 24.25GHz to overcome phase noise.

[0135] The NR band is defined by two types of frequency ranges: FR1 and FR2. FR1 can be the sub-6 GHz range, and FR2 can be the range above 6 GHz, i.e., the millimeter wave (mmWave) band.

[0136] As an example, Table 2 below defines the NR frequency bands.

[0137] [Table 2]

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

[0139] Regarding the frame structure in the NR system, the time domain size of various fields is expressed as the basic time unit T of NR. c =1 / (△f max *N f ), where △f max =480*10 3 Hz, and the value N related to the Fast Fourier Transform (FFT) size or the Inverse Fast Fourier Transform (IFFT) size f Given as N f =4096. T c and T s (Based on LTE time units and sampling time, given as T s =1 / ((15kHz)*2048)) is set to the following relationship: T s / T c = 64. DL transmission and UL transmission are organized as T f =(△f max *N f / 100)*T c =10ms duration (radio) frame. Each radio frame consists of 10 subframes, each subframe has T sf =(△f max *N f / 100)*T c = 1ms duration. There can be one frame set for UL and one frame set for DL. For parameter set μ, the time slots are in increasing order in the subframe with n μ s ∈{0,…,N slot ,μ subframe -1} and are numbered in increasing order in the radio frame. μ s,f ∈{0,…,N slot,μ frame -1} number. A time slot includes N μ symb consecutive OFDM symbols, and N μ symbDepends on CP. Time slot n in subframe μ s The beginning of the OFDM symbol n in the same subframe μ s *N μ symb The start of is aligned in time.

[0140] Table 3 lists the number of symbols per time slot, the number of time slots per frame, and the number of time slots per subframe for each SCS under normal CP, and Table 4 lists the number of symbols per time slot, the number of time slots per frame, and the number of time slots per subframe for each SCS under extended CP.

[0141] [Table 3]

[0142]

[0143] [Table 4]

[0144]

[0145] In the above table, N slot symb Indicates the number of symbols in a time slot, N frame,μ slot Indicates the number of time slots in a frame, N subframe,μ slot Indicates the number of time slots in a subframe.

[0146] In an NR system to which various embodiments of the present disclosure are applicable, different OFDM(A) parameter sets (e.g., SCS, CP length, etc.) may be configured for multiple cells aggregated for one UE. Therefore, the (absolute time) period of a time resource (collectively referred to as a time unit (TU) for convenience) including the same number of symbols (e.g., subframes (SFs), time slots, or TTIs) may be configured differently for the aggregated cells.

[0147] Figure 2 Assume an example of μ=2 (i.e., SCS of 60 kHz), wherein referring to Table 3, one subframe may include four time slots. Figure 2 One subframe = {1, 2, 4} time slots, which is exemplary. The number of time slots that may be included in one subframe is defined as listed in Table 3 or Table 4.

[0148] Furthermore, a mini-slot may include 2, 4, or 7 symbols, less than 2 symbols, or more than 7 symbols.

[0149] Figure 3 This is a diagram illustrating a time slot structure in an NR system to which an embodiment of the present disclosure is applicable.

[0150] Reference Figure 3 A time slot includes multiple symbols in the time domain. For example, a time slot includes 7 symbols in the normal CP case and 6 symbols in the extended CP case.

[0151] A carrier includes multiple subcarriers in the frequency domain. An RB is defined by multiple (eg, 12) consecutive subcarriers in the frequency domain.

[0152] A BWP defined by a plurality of consecutive (P)RBs in the frequency domain may correspond to one parameter set (eg, SCS, CP length, etc.).

[0153] A carrier may include up to N (eg, 5) BWPs. Data communication may be performed in the activated BWPs, and only one BWP may be activated for a UE. In a resource grid, each element is referred to as an RE, and one complex symbol may be mapped to an RE.

[0154] Figure 4 is a diagram illustrating an exemplary mapping of physical channels in time slots to which various embodiments are applicable.

[0155] A time slot may include all of the DL control channel, DL data or UL data, and the UL control channel. For example, the first N symbols of the time slot may be used to send the DL control channel (hereinafter referred to as the DL control region), and the last M symbols of the time slot may be used to send the UL control channel (hereinafter referred to as the UL control region). Each of N and M is an integer equal to or greater than 0. The resource region (hereinafter referred to as the data region) between the DL control region and the UL control region may be used to send DL data or UL data. There may be a time gap between the control region and the data region for DL ​​to UL or UL to DL switching. PDCCH may be sent in the DL control region, and PDSCH may be sent in the DL data region. Some symbols at the DL to UL switching time in the time slot may be used as time gaps.

[0156] 1.3. Channel Structure

[0157] DL Channel Structure

[0158] The BS transmits a related signal to the UE on a DL channel as described below, and the UE receives a related signal from the BS on the DL channel.

[0159] 1.3.1.1. Physical Downlink Shared Channel (PDSCH)

[0160] PDSCH transmits DL data (e.g., DL shared channel transport block (DL-SCH TB)) and uses modulation schemes such as quadrature phase shift keying (QPSK), hexadecimal quadrature amplitude modulation (16QAM), 64QAM, or 256QAM. TB is encoded as a codeword. PDSCH can transmit up to two codewords. Scrambling and modulation mapping are performed based on the codeword, and the modulation symbols generated from each codeword are mapped to one or more layers (layer mapping). Each layer is mapped to a resource together with a demodulation reference signal (DMRS), generated as an OFDM symbol signal, and sent through the corresponding antenna port.

[0161] 1.3.1.2. Physical Downlink Control Channel (PDCCH)

[0162] The PDCCH may transmit downlink control information (DCI) (e.g., DL data scheduling information, UL data scheduling information, etc.) and the PUCCH may transmit uplink control information (UCI) (e.g., ACK / NACK for DL ​​data, channel state information (CSI), scheduling request (SR), etc.).

[0163] The PDCCH carries DCI and is modulated using QPSK. A PDCCH consists of 1, 2, 4, 8, or 16 control channel elements (CCEs) depending on the aggregation level (AL). A CCE consists of 6 resource element groups (REGs). A REG is defined by one OFDM symbol x one (P)RB.

[0164] The PDCCH is transmitted in a control resource set (CORESET). A CORESET is defined as a set of REGs with a given parameter set (e.g., SCS, CP length, etc.). Multiple CORESETs for one UE may overlap with each other in the time / frequency domain. A CORESET may be configured by system information (e.g., Master Information Block (MIB)) or UE-specific higher-layer (RRC) signaling. Specifically, the number of RBs and the number of symbols (up to 3 symbols) included in a CORESET may be configured by higher-layer signaling.

[0165] The UE acquires the DCI transmitted on the PDCCH by decoding a set of PDCCH candidates (so-called blind decoding). The set of PDCCH candidates decoded by the UE is defined as a PDCCH search space set. The search space set can be a common search space (CSS) or a UE-specific search space (USS). The UE can acquire DCI by monitoring PDCCH candidates in one or more search space sets configured by the MIB or higher-layer signaling. Each CORESET configuration is associated with one or more search space sets, and each search space set is associated with one CORESET configuration. One search space set is determined based on the following parameters.

[0166] Table 5 lists exemplary features of each search space type.

[0167] [Table 5]

[0168]

[0169] Table 6 lists exemplary DCI formats transmitted on the PDCCH.

[0170] [Table 6]

[0171] DCI format use 0_0 PUSCH scheduling in a cell 0_1 PUSCH scheduling in a cell 1_0 PDSCH scheduling in a cell 1_1 PDSCH scheduling in a cell 2_0 Notify a group of UEs of the timeslot format 2_1 Inform a group of UEs that the UE may assume that no PRBs and OFDM symbols intended for that UE are transmitted 2_2 Transmit TPC commands for PUCCH and PUSCH 2_3 Transmits a set of TPC commands for SRS transmission to one or more UEs

[0172] DCI format 0_0 can be used to schedule TB-based (or TB-level) PUSCH, and DCI format 0_1 ​​can be used to schedule TB-based (or TB-level) PUSCH or code block group (CBG)-based (or CBG-level) PUSCH. DCI format 1_0 can be used to schedule TB-based (or TB-level) PDSCH, and DCI format 1_1 can be used to schedule TB-based (or TB-level) PDSCH or CBG-based (or CBG-level) PDSCH. DCI format 2_0 is used to transmit dynamic slot format information (e.g., dynamic slot format indicator (SFI)) to the UE, and DCI format 2_1 is used to transmit DL preemption information to the UE. DCI format 2_0 and / or DCI format 2_1 can be transmitted to a group of UEs on the group common PDCCH (GC-PDCCH) (PDCCH directed to a group of UEs).

[0173] UL Channel Structure

[0174] The UE transmits a relevant signal to the BS on a UL channel described later, and the BS receives the relevant signal from the UE on the UL channel.

[0175] 1.3.2.1. Physical Uplink Shared Channel (PUSCH)

[0176] The PUSCH transmits UL data (e.g., UL shared channel transport blocks (UL-SCH TBs)) and / or UCI using a cyclic prefix-orthogonal frequency division multiplexing (CP-OFDM) waveform or a discrete Fourier transform-spreading-orthogonal multiplexing (DFT-s-OFDM) waveform. If the PUSCH is transmitted using a DFT-s-OFDM waveform, the UE applies transform precoding to transmit the PUSCH. For example, if transform precoding is not possible (e.g., transform precoding is disabled), the UE may transmit the PUSCH using a CP-OFDM waveform, whereas if transform precoding is possible (e.g., transform precoding is enabled), the UE may transmit the PUSCH using a CP-OFDM waveform or a DFT-s-OFDM waveform. PUSCH transmission may be dynamically scheduled by a UL grant in the DCI or semi-statically scheduled by higher-layer signaling (e.g., RRC signaling) (and / or Layer 1 (L1) signaling (e.g., PDCCH)) (configured grant). PUSCH transmission may be performed in a codebook-based or non-codebook-based manner.

[0177] 1.3.2.2. Physical Uplink Control Channel (PUCCH)

[0178] PUCCH transmits UCI, HARQ-ACK and / or SR, and is classified as short PUCCH or long PUCCH according to the transmission duration of PUCCH. Table 7 lists exemplary PUCCH formats.

[0179] [Table 7]

[0180]

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

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

[0183] PUCCH format 2 transmits more than 2 bits of UCI and transmits the modulation symbols of the DCI with the DMRS using frequency division multiplexing (FDM). The DMRS is located in symbols #1, #4, #7, and #10 of a given RB at a density of 1 / 3. A pseudo-noise (PN) sequence is used for the DMRS sequence. Frequency hopping can be activated for 1-symbol PUCCH format 2.

[0184] PUCCH format 3 does not support UE multiplexing within the same PRBS and transmits more than 2 bits of UCI. In other words, PUCCH format 3 PUCCH resources do not include OCC. Modulation symbols and DMRS are sent using time-division multiplexing (TDM).

[0185] PUCCH format 4 supports multiplexing up to four UEs in the same PRBS and transmits more than two bits of UCI. In other words, the PUCCH resources of PUCCH format 3 include OCC. Modulation symbols and DMRS are sent using time-division multiplexing (TDM).

[0186] 1.4. Bandwidth Part (BWP)

[0187] The NR system can support up to 400MHz per carrier. If the UE always turns on the radio frequency (RF) module for all carriers while operating in such a wideband carrier, the battery consumption of the UE may increase. Considering multiple use cases operating in one wideband carrier (e.g., enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), massive machine type communication (mMTC), vehicle-to-everything (V2X), etc.), different parameter sets (e.g., SCS) can be supported for each frequency band of the carrier. In addition, considering that each UE may have different capabilities regarding the maximum bandwidth, the BS may instruct the UE to operate only in part of the bandwidth of the wideband carrier instead of the entire bandwidth. The partial bandwidth is called a BWP. A BWP is a subset of contiguous common RBs defined by a parameter set μi in a BWP i for a carrier in the frequency domain, and one parameter set (e.g., SCS, CP length, and / or slot / mini-slot duration) may be configured for each BWP.

[0188] The BS can configure one or more BWPs in a carrier assigned to a UE. Alternatively, if UEs are concentrated in a specific BWP, the BS can move some UEs to another BWP for load balancing. For frequency-domain inter-cell interference cancellation between adjacent cells, the BS can configure BWPs on both sides of the cell, except for some center spectrum within the entire bandwidth within the same time slot. That is, the BS can configure at least one DL / UL BWP associated with a wideband carrier for the UE, activate at least one DL / UL BWP among the configured DL / UL BWPs at a specific time (via L1 signaling as a physical layer control signal, MAC Control Element (CE) as a MAC layer control signal, or RRC signaling), and instruct the UE to switch to another configured DL / UL BWP (via L1 signaling, MAC CE, or RRC signaling). Alternatively, the BS can configure a timer and switch the UE to a predetermined DL / UL BWP upon expiration of the timer. In particular, the activated DL / UL BWP is called an active DL / UL BWP. The UE may not receive any DL / UL BWP configuration when performing initial access or before establishing an RRC connection. The DL / UL BWP assumed by the UE in this case is called the initial active DL / UL BWP.

[0189] 1.5. Synchronization Signal Block (SSB) Transmission and Related Operations

[0190] Figure 5 This is a diagram illustrating the structure of a synchronization signal block (SSB) to which various embodiments of the present disclosure are applicable.

[0191] The UE can perform cell search, system information acquisition, beam alignment for initial access, DL measurement, etc. based on the SSB. The term SSB is used interchangeably with the synchronization signal / physical broadcast channel (SS / PBCH) block.

[0192] Reference Figure 5 , the SSB to which various embodiments of the present disclosure are applicable may include 20 RBs in four consecutive OFDM symbols. In addition, the SSB may include the PSS, SSS, and PBCH, and the UE may perform cell search, system information acquisition, beam alignment for initial access, DL measurement, etc. based on the SSB.

[0193] Each of the PSS and SSS consists of one OFDM symbol x 127 subcarriers, and the PBCH consists of three OFDM symbols x 576 subcarriers. Polarization coding and QPSK are applied to the PBCH. The PBCH includes data REs and DMRS REs in each OFDM symbol. There are three DMRS REs per RB, with three data REs between every two adjacent DMRS REs.

[0194] Cell Search

[0195] Cell search refers to the process by which a UE acquires time / frequency synchronization with a cell and detects the cell ID (e.g., physical layer cell ID (PCID)) of the cell. The PSS can be used to detect a cell ID within a cell ID group, and the SSS can be used to detect a cell ID group. The PBCH can be used to detect the SSB (time) index and half-frame.

[0196] The cell search process of the UE can be summarized as shown in Table 8 below.

[0197] [Table 8]

[0198]

[0199] There are 336 cell ID groups, each of which includes three cell IDs. There are a total of 1008 cell IDs. Information about the cell ID group to which a cell's cell ID belongs can be provided / obtained through the cell's SSS, and information about the cell IDs of the 336 cells can be provided / obtained through the PSS.

[0200] Figure 6 is a diagram illustrating an exemplary SSB transmission method to which various embodiments of the present disclosure are applicable.

[0201] Reference Figure 6 , SSBs are sent periodically according to the SSB periodicity. The default SSB periodicity assumed by the UE during the initial cell search is defined as 20ms. After cell access, the network (e.g., BS) may set the SSB periodicity to one of {5ms, 10ms, 20ms, 40ms, 80ms, 160ms}. An SSB burst set is configured at the beginning of the SSB period. An SSB burst set may be configured with a 5ms time window (i.e., half a frame), and an SSB may be repeatedly sent up to L times within an SS burst set. The maximum number of SSB transmissions L may be given as follows based on the frequency band of the carrier. One time slot includes at most two SSBs.

[0202] - For the frequency range up to 3 GHz, L = 4

[0203] - For the frequency range of 3 GHz to 6 GHz, L = 8

[0204] - For the frequency range of 6 GHz to 52.6 GHz, L = 64

[0205] The temporal position of an SSB candidate in an SS burst set may be defined according to the SCS as follows. The temporal position of an SSB candidate is indexed (SSB index) 0 to L-1 in temporal order within an SSB burst set (i.e., half-frame). In the description of various embodiments of the present disclosure, candidate SSB and SSB candidate may be used interchangeably.

[0206] - Case A: 15-kHz SCS: The index of the first symbol of the candidate SSB is given as {2,8}+14*n

[0207] --For operation without shared spectrum channel access (e.g., L-band and LCell): where n=0, 1 for carrier frequencies equal to or less than 3 GHz, and n=0, 1, 2, 3 for carrier frequencies from 3 GHz to 6 GHz.

[0208] --For operations of shared spectrum channel access (eg, U-band and UCell): where n=0, 1, 2, 3, 4.

[0209] - Case B: 30-kHz SCS: The index of the first symbol of the candidate SSB is given as {4, 8, 16, 20} + 28*n, where n = 0 for carrier frequencies equal to or less than 3 GHz, and n = 0, 1 for carrier frequencies from 3 GHz to 6 GHz.

[0210] - Case C: 30-kHz SCS: The index of the first symbol of the candidate SSB is given as {2, 8}+14*n

[0211] -For operation without shared spectrum channel access: (1) In the case of paired spectrum operation, for carrier frequencies equal to or less than 3 GHz, n=0, 1, and for carrier frequencies within FR1 and greater than 3 GHz, n=0, 1, 2, 3; (2) In the case of unpaired spectrum operation, for carrier frequencies equal to or less than 2.4 GHz, n=0, 1, and for carrier frequencies within FR1 and greater than 2.4 GHz, n=0, 1, 2, 3.

[0212] -For shared spectrum channel access operations: where n=0, 1, 2, 3, 4, 6, 7, 8, 9.

[0213] -Case D: 120-kHz SCS: The index of the first symbol of the candidate SSB is given as {4, 8, 16, 20} + 28*n, where for carrier frequencies greater than 6 GHz, n = 0, 1, 2, 3, 5, 6, 7, 8, 10, 11, 12, 13, 15, 16, 17, 18.

[0214] -Case E: 240-kHz SCS: The index of the first symbol of the candidate SSB is given as {8, 12, 16, 20, 32, 36, 40, 44} + 56*n, where for carrier frequencies greater than 6 GHz, n = 0, 1, 2, 3, 5, 6, 7, 8.

[0215] Synchronization process

[0216] Figure 7 The acquisition of DL time synchronization information at a UE to which various embodiments of the present disclosure are applicable is illustrated.

[0217] The UE can acquire DL synchronization by detecting SSBs. The UE can identify the structure of the SSB burst set based on the index of the detected SSB and thus detect the symbol, slot, or half-frame boundary. The number of the frame or half-frame to which the detected SSB belongs can be identified by the SFN information and the half-frame indication information.

[0218] Specifically, the UE may obtain 10-bit SFN system information s0 to s9 from the PBCH. 6 bits of the 10-bit SFN information are obtained from a master information block (MIB), and the remaining 4 bits are obtained from a PBCH transport block (TB).

[0219] The UE can then obtain 1-bit half-frame indication information c0. When the carrier frequency is 3 GHz or lower, the half-frame indication information can be implicitly signaled by the PBCH DMRS. The PBCH DMRS uses one of the 8 PBCH DMRS sequences to indicate 3 bits of information. Therefore, when L=4, the remaining one bit, except for the bit indicating the SSB index among the 3 bits that can be indicated by the 8 PBCH DMRS sequences, can be used as a half-frame indication.

[0220] Finally, the UE can obtain the SSB index based on the DMRS sequence and the PBCH payload. The SSB candidates are indexed with 0 to L-1 in time order in the SSB burst set (i.e., half-frame). When L=8 or L=64, the three least significant bits (LSBs) b0, b1, and b2 of the SSB index can be indicated by 8 different PBCH DMRS sequences. When L=64, the three most significant bits (MSBs) b3, b4, and b5 of the SSB index are indicated by PBCH. When L=2, the two LSBs b0 and b1 of the SSB index can be indicated by 4 different PBCH DMRS sequences. When L=4, the remaining one bit b2, except for the bit indicating the SSB index in the three bits, can be used as a half-frame indication.

[0221] System information acquisition

[0222] Figure 8The system information (SI) acquisition process applicable to various embodiments of the present disclosure is illustrated.

[0223] The UE can obtain access stratum (AS) / non-access stratum (NAS) information in the SI acquisition procedure. The SI acquisition procedure is applicable to UEs in RRC_IDLE, RRC_INACTIVE and RRC_CONNECTED states.

[0224] SI may be divided into a master information block (MIB) and a plurality of system information blocks (SIBs). SI other than the MIB may be referred to as remaining minimum system information (RMSI), which will be described in detail below.

[0225] -MIB may include information / parameters related to the reception of System Information Block Type 1 (SIB1) and may be transmitted through the PBCH of the SSB.

[0226] -MIB may include information / parameters related to reception of System Information Block Type 1 (SIB1) and may be transmitted through the PBCH of the SSB. The information of the MIB may be understood with reference to 3GPP TS 38.331 and may include the following fields.

[0227] -subCarrierSpacingCommon ENUMERATED{scs15or60,scs30or120}

[0228] -ssb-SubcarrierOffset INTEGER(0..15)

[0229] -pdcch-ConfigSIB1 INTEGER(0..255)

[0230] -dmrs-TypeA-Position ENUMERATED{pos2, pos3} ...

[0232] -spare BIT STRING(SIZE(1))

[0233] Descriptions of the fields are shown in Table 9 below.

[0234] [Table 9]

[0235]

[0236] When selecting the initial cell, the UE may assume that the half-frame with SSB repeats with a period of 20ms. The UE may check whether there is a control resource set (CORESET) (e.g., CORESET#0) for the Type0-PDCCH common search space based on the MIB. SSB <=23 (for FR1) or k SSB <=11 (for FR2), the UE may determine that a CORESET exists for the Type0-PDCCH common search space. SSB >23 (for FR1) or k SSB >11 (for FR2), the UE may determine that there is no CORESET for the Type0-PDCCH common search space. The Type0-PDCCH common search space may be a type of PDCCH search space and may be used to send a PDCCH for scheduling SI messages. When there is a Type0-PDCCH common search space, the UE may determine (i) a plurality of consecutive RBs and one or more consecutive symbols included in a CORESET (e.g., CORESET#0), and (ii) a PDCCH opportunity (i.e., a position in the time domain for PDCCH reception) (e.g., search space#0) based on information in the MIB (e.g., pdcch-ConfigSIB1). When there is no Type0-PDCCH common search space, pdcch-ConfigSIB1 may provide information about the frequency position where SSB / SIB1 exists and the frequency range where SSB / SIB1 does not exist.

[0237] SIB1 may include information related to the availability and scheduling (e.g., transmission period and SI window size) of the remaining SIBs (hereinafter referred to as SIBx, where x is an integer equal to or greater than 2). For example, SIB1 may inform whether SIBx is broadcast periodically or provided using an on-demand method in response to a request from a UE. When SIBx is provided using an on-demand method, SIB1 may include information required for the UE to request SI. SIB1 may be transmitted over the PDSCH, the PDCCH for scheduling SIB1 may be transmitted over the Type0-PDCCH common search space, and SIB1 may be transmitted over the PDSCH indicated by the PDCCH.

[0238] SIBx may be included in the SI message and may be transmitted through the PDSCH.Each SI message may be transmitted within a periodically generated window (ie, SI window).

[0239] Beam alignment

[0240] Figure 9is a diagram illustrating an exemplary multi-beam transmission to which various embodiments are applicable.

[0241] Beam scanning refers to the transmission reception point (TRP) (e.g., BS / cell) changing the beam (direction) of the radio signal over time (hereinafter, the terms beam and beam direction are used interchangeably). SSBs can be sent periodically by beam scanning. In this case, the SSB index is implicitly linked to the SSB beam. The SSB beam can be changed based on the SSB (index) or based on the SS (index) group. In the latter, the same SSB beam is maintained in the SSB (index) group. That is, the transmission beam direction of the SSB is repeated for multiple consecutive SSBs. Depending on the frequency band of the carrier, the maximum number of times L that an SSB is sent in an SSB burst set can have a value of 4, 8, or 64. Therefore, the maximum number of SSB beams in an SSB burst set can be given as follows according to the frequency band of the carrier.

[0242] - For frequency range up to 3 GHz, maximum number of beams = 4

[0243] - For the frequency range from 3 GHz to 6 GHz, the maximum number of beams = 8

[0244] - For the frequency range from 6 GHz to 52.6 GHz, the maximum number of beams = 64

[0245] When multi-beam transmission is not applied, the number of SSB beams is 1.

[0246] When a UE attempts to initially access a BS, it can align its beam with that of the BS based on the SSB. For example, the UE identifies the best SSB after performing SSB detection. Thereafter, the UE can send a RACH preamble to the BS on a PRACH resource linked to / corresponding to the index (i.e., beam) of the best SSB. The SSB can be used to align the beam between the BS and the UE after initial access.

[0247] Channel measurement and rate matching

[0248] Figure 10 This is a diagram illustrating a method of indicating an actually transmitted SSB (SSB_tx), to which various embodiments are applicable.

[0249] A maximum of L SSBs can be sent in an SSB burst set, and the number and position of the SSBs actually sent can vary for each BS / cell. The number and position of the SSBs actually sent can be used for rate matching and measurement, and information about the SSBs actually sent can be indicated as follows (e.g., ssb-PositionsInBurst).

[0250] -When the number and position of SSBs actually transmitted are related to rate matching, this information may be indicated by UE-specific RRC signaling or RMSI. UE-specific RRC signaling includes a full bitmap (e.g., length L) for frequency ranges below and above 6 GHz. RMSI includes a full bitmap for frequency ranges below 6 GHz and a compressed bitmap for frequency ranges above 6 GHz. Specifically, information about SSBs actually transmitted may be indicated by a group bitmap (8 bits) + an intra-group bitmap (8 bits). Resources (e.g., REs) indicated by UE-specific RRC signaling or RMSI may be reserved for SSB transmission, and PDSCH and / or PUSCH may be rate matched taking into account the SSB resources.

[0251] -When the number and position of SSBs actually transmitted are relevant to the measurement, if the UE is in RRC connected mode, the network (e.g., BS) may indicate the SSB set to be measured during the measurement period. The SSB set may be indicated for each frequency layer. If no SSB set is indicated, a default SSB set may be used. The default SSB set includes all SSBs during the measurement period. The SSB set may be indicated by a full bitmap (e.g., length L) of RRC signaling. When the UE is in RRC idle mode, the default SSB set is used.

[0252] 2. Random Access (RACH) Process

[0253] When the UE initially accesses the BS or has no radio resources for signal transmission, the UE may perform a random access procedure with the BS.

[0254] The random access procedure is used for various purposes. For example, it can be used for initial network access in the RRC_IDLE state, RRC connection re-establishment, handover, UE-triggered UL data transmission, transitions in the RRC_INACTIVE state, time alignment establishment for SCell addition, OSI request, and beam failure recovery. The UE can acquire UL synchronization and UL transmission resources during the random access procedure.

[0255] The random access procedure can be classified into a contention-based random access procedure and a contention-free random access procedure. The contention-based random access procedure is further divided into a 4-step random access (4-step RACH) procedure and a 2-step random access (2-step RACH) procedure.

[0256] 2.1.4 RACH: Type 1 Random Access Procedure

[0257] Figure 11 is a diagram illustrating an exemplary 4-step RACH procedure to which various embodiments of the present disclosure are applicable.

[0258] When the (contention-based) random access procedure is performed in four steps (4-step RACH procedure), the UE can transmit a message (message 1 (Msg1)) including a preamble related to a specific sequence on the PRACH (1401) and receive a response message (RAR message) for the preamble on the PDCCH and the PDSCH corresponding to the PDCCH (message 2 (Msg2)) (1403). The UE transmits a message (message 3 (Msg3)) including a PUSCH based on scheduling information included in the RAR (1405) and performs a contention resolution procedure involving receiving a PDCCH signal and a PDSCH signal corresponding to the PDCCH signal. The UE can receive a message (message 4 (Msg4)) including contention resolution information for the contention resolution procedure from the BS (1707).

[0259] The 4-step RACH procedure of the UE can be summarized in Table 10 below.

[0260] [Table 10]

[0261]

[0262] During the random access procedure, the UE may first send a RACH preamble as Msg1 on the PRACH.

[0263] Two different lengths of random access preamble sequences are supported: the longer sequence length 839 is applied to 1.25kHz and 5kHz SCS, while the shorter sequence length 139 is applied to 15kHz, 30Hz, 60kHz, and 120kHz SCS.

[0264] Multiple preamble formats are defined by one or more RACH OFDM symbols and different CPs (and / or guard times). The RACH configuration for a cell is provided to the UE in the cell's system information. The RACH configuration includes information about the PRACH SCS, available preambles, and preamble formats. The RACH configuration includes information about the association between SSBs and RACH (time-frequency) resources. The UE transmits a random access preamble in the RACH time-frequency resources associated with the detected or selected SSB.

[0265] The SSB threshold for RACH resource association may be configured by the network, and the RACH preamble is transmitted or retransmitted based on the SSB having a reference signal received power (RSRP) measurement that meets the threshold. For example, the UE may select one of the SSBs that meets the threshold and transmit or retransmit the RACH preamble based on the RACH resource associated with the selected SSB. For example, when retransmitting the RACH preamble, the UE may reselect one of the SSBs and retransmit the RACH preamble in the RACH resource associated with the reselected SSB. That is, the RACH resource used for the retransmission of the RACH preamble may be the same as or different from the RACH resource used for the transmission of the RACH preamble.

[0266] Upon receiving the RACH preamble from the UE, the BS sends a RAR message (Msg2) to the UE. The PDCCH that schedules the PDSCH carrying the RAR is masked with a cyclic redundancy check (CRC) by a random access radio network temporary identifier (RA-RNTI) and sent. Upon detecting the PDCCH masked by the RA-RNTI, the UE can receive the RAR on the PDSCH scheduled by the DCI carried on the PDCCH. The UE determines whether the RAR includes RAR information for the preamble (that is, Msg1) sent to it. The UE can make this determination by checking the presence or absence of the RACH preamble ID of the preamble it sends in the RAR. In the absence of a response to Msg1, the UE can resend the RACH preamble a predetermined number of times or less while performing power ramping. The UE calculates the PRACH transmission power for preamble retransmission based on the latest path loss and power ramp counter.

[0267] The RAR information may include a preamble sequence sent by the UE, a temporary cell RNTI (TC-RNTI) that the BS has assigned to the UE attempting random access, UL transmit time alignment information, UL transmit power adjustment information, and UL radio resource allocation information. Upon receiving its RAR information on the PDSCH, the UE may obtain the initial UL grant, TC-RNTI, and timing advance information for UL synchronization. The timing advance information is used to control the UL signal transmission timing. For better alignment between the UE's PUSCH / PUCCH transmission and the subframe timing on the network side, the network (e.g., BS) may measure the time difference between the PUSCH / PUCCH / SRS reception and the subframe, and send timing advance information based on the time difference. The UE may send an UL signal on the UL-SCH as Msg3 of the random access procedure based on the RAR information. Msg3 may include an RRC connection request and a UE ID. The network may send Msg4 in response to Msg3. Msg4 may be regarded as a contention resolution message on the DL. When the UE receives Msg4, the UE may enter the RRC_CONNECTED state.

[0268] As previously mentioned, the UL grant included in the RAR schedules the PUSCH transmission to the BS. The PUSCH that carries the initial UL transmission based on the RAR UL grant is called Msg3 PUSCH. The contents of the RAR UL grant start with the most significant bit (MSB) and end in the least significant bit (LSB), as shown in Table 11.

[0269] [Table 11]

[0270] RAR UL Permit Field Number of bits Frequency Hopping Flag 1 Msg3 PUSCH frequency resource allocation 12 Msg3 PUSCH time resource allocation 4 Modulation and Coding Scheme (MCS) 4 Msg3 PUSCH transmit power control (TPC) 3 CSI Request 1

[0271] The transmit power control (TPC) command is used to determine the transmission power of Msg3 PUSCH. For example, the TPC command is interpreted according to Table 12.

[0272] [Table 12]

[0273] TPC Command Value [dB] 0 -6 1 -4 2 -2 3 0 4 2 5 4 6 6 7 8

[0274] 2.2.2 RACH: Type 2 Random Access Procedure

[0275] Figure 12 is a diagram illustrating an exemplary 2-step RACH procedure to which various embodiments of the present disclosure are applicable.

[0276] A (contention-based) RACH procedure performed in two steps (ie, a 2-step RACH procedure) has been proposed to simplify the RACH procedure, thus achieving low signaling overhead and low latency.

[0277] In the 2-step RACH procedure, the operations of sending Msg1 and Msg3 in the 4-step RACH procedure can be combined into one operation in which the UE sends a single message (Message A (MsgA) including PRACH and PUSCH). In the 4-step RACH procedure, the operations of sending Msg2 and Msg4 by the BS can be combined into one operation in which the BS sends a single message (Message B (MsgB) including RAR and contention resolution information).

[0278] That is, in the 2-step RACH procedure, the UE may combine Msg1 and Msg3 of the 4-step RACH procedure into one message (eg, MsgA) and send the message to the BS (1201).

[0279] Furthermore, in the 2-step RACH procedure, the BS may combine Msg2 and Msg4 of the 4-step RACH procedure into one message (eg, MsgB) and send the message to the UE (1203).

[0280] Based on the combination of these messages, the 2-step RACH procedure can be transformed into a low-latency RACH procedure.

[0281] More specifically, in the 2-step RACH procedure, MsgA may carry the PRACH preamble included in Msg1 and the data included in Msg3. In the 2-step RACH procedure, MsgB may carry the RAR included in Msg2 and the contention resolution information included in Msg4.

[0282] 2.3. Contention-Free RACH

[0283] Figure 13 is a diagram illustrating an exemplary contention-free RACH procedure to which various embodiments of the present disclosure are applicable.

[0284] The contention-free RACH process can be used for the UE to switch to another cell or BS, or it can be executed when the BS commands a request. The contention-free RACH process is basically similar to the contention-based RACH process. However, compared to the contention-based RACH process in which the preamble to be used is randomly selected from multiple RACH preambles, in the contention-free RACH process, the BS assigns the UE the preamble to be used (called a dedicated RACH preamble) (1901). Information about the dedicated RACH preamble may be included in an RRC message (e.g., a handover command) or provided to the UE via a PDCCH command. When the RACH process starts, the UE sends a dedicated RACH preamble to the BS (1903). When the UE receives a RAR from the BS, the RACH process is completed (1905).

[0285] In the contention-free RACH procedure, the CSI request field in the RAR UL grant indicates whether the UE should include aperiodic CSI reporting in the corresponding PUSCH transmission. The SCS used for Msg3 PUSCH transmission is provided by RRC parameters. The UE can transmit PRACH and Msg3 PUSCH on the same UL carrier in the same serving cell. The UL BWP for Msg3 PUSCH transmission is indicated by SIB1.

[0286] 2.4. Mapping between SSB blocks and PRACH resources (timings)

[0287] Figure 14 and Figure 15 is a diagram illustrating an example of transmission of an SS block and a PRACH resource linked to the SS block according to various embodiments of the present disclosure.

[0288] In order for a BS to communicate with a UE, it is necessary to find the optimal beam direction between the BS and the UE, and as the UE moves, the optimal beam direction may change, and therefore it is necessary to continuously track the optimal beam direction. The process of finding the optimal beam direction between the BS and the UE may be referred to as a beam acquisition process, and the process of continuously tracking the optimal beam direction may be referred to as a beam tracking process. This process may be required for a state in which the optimal beam is lost and communication with the BS cannot be maintained in an optimal communication state or enters a state in which communication is impossible (i.e., beam recovery for recovering beam failure during 1) initial access when the UE attempts to access the BS for the first time, 2) switching from one BS to another BS, and 3) beam tracking for finding the optimal beam between the UE and the BS).

[0289] In the case of an NR system, a multi-step beam acquisition process for beam acquisition in an environment using multiple beams is discussed. In the multi-step beam acquisition process, the BS and UE can use a wide beam to perform connection establishment in the initial access phase, and after the connection establishment is completed, the BS and UE can use a narrow beam to perform communication with optimal quality. An example of the beam acquisition process in an NR system according to various embodiments of the present disclosure will be described below.

[0290] -1) The BS can send a synchronization block for each wide beam so that the UE can find the BS in the initial access phase (that is, perform cell search or cell acquisition), measure the quality of the channel of each beam of the wide beam, and find the optimal wide beam to be used in the main phase of beam acquisition.

[0291] -2) The UE may perform a cell search on a synchronization block for each beam and may perform DL beam acquisition using the detection result for each beam.

[0292] -3) The UE may perform a RACH procedure in order to notify the UE of its intention to access the BS discovered by the UE.

[0293] -4) To enable the UE to inform the BS of the DL beam acquisition result (e.g., beam index) at the wide beam level simultaneously with the RACH procedure, the BS may link or associate the synchronization block transmitted for each beam with the PRACH resource to be used for PRACH transmission. When the UE performs the RACH procedure using the PRACH resource connected to the optimal beam direction discovered by the UE, the BS may acquire information about the DL beam suitable for the UE during the process of receiving the PRACH preamble.

[0294] In a multi-beam environment, it may be important for the UE and / or transmit and receive point (TRP) to accurately determine the Tx beam and / or Rx beam direction between the UE and the TRP. In a multi-beam environment, beam scanning for repeatedly transmitting or receiving signals according to the TX / RX reciprocal capability of the TRP (e.g., BS) or the UE may be considered. The TX / RX reciprocal capability may be referred to as TX / RX beam correspondence in the TRP and the UE. In a multi-beam environment, when the TX / RX reciprocal capability in the TRP and the UE is not maintained, the UE may not be able to transmit a UL signal in the beam direction in which the UE receives a DL signal. This is because the optimal path for the UL and the optimal path for the DL are different. When the TRP determines the TRP RX beam for corresponding UL reception based on DL measurements of one or more TX beams of the UE relative to the TRP and / or the TRP determines the TRP TX beam for corresponding DL transmission based on UL measurements of one or more RX beams of the TRP' relative to the TRP, the TX / RX beam correspondence in the TRP may be maintained. The TX / RX beam correspondence in the UE may be maintained when the UE determines a UE RX beam for corresponding UL transmission based on DL measurements of the UE relative to one or more RX beams of the UE and / or the UE determines a UE RX beam for corresponding DL reception based on an indication of a TRP based on UL measurements of one or more TX beams relative to the UE.

[0295] 2.5.PRACH Preamble Structure

[0296] In the NR system, a RACH signal for initial access to a BS (that is, initial access to the BS through a cell used by the BS) may be configured using the following factors.

[0297] - Cyclic Prefix (CP): This prevents the interface from the previous / previous (OFDM) symbol and can bundle the PRACH preamble signals that arrive at the BS with various time delays in the same time zone. That is, when the CP is set to be suitable for the maximum cell radius, the PRACH preambles sent by the UEs in the cell in the same resource can enter the PRACH reception window corresponding to the length of the PRACH preamble set by the BS for PRACH reception. The length of the CP can generally be set to be equal to or greater than the maximum round trip delay. The CP can have a length of T CP .

[0298] - Preamble (sequence): A sequence for the BS to detect the transmission of a signal may be defined, and the preamble may carry the sequence. The preamble sequence may have a length of T SEQ .

[0299] - Guard Time (GT): This may be a duration defined to prevent a PRACH signal from interfering with a signal arriving at the BS after the PRACH symbol duration. The PRACH signal is transmitted from a location farthest from the BS in the PRACH coverage and arrives at the BS with a delay, and the UE does not transmit a signal during this duration. Therefore, the GT may not be defined based on the PRACH signal. The GT may have a length of T GP .

[0300] 2.6. Physical Resources Mapped to the Physical Random Access Channel

[0301] The random access preamble may be transmitted only within time resources acquired based on a RACH configuration table preconfigured for RACH configuration, FR1, FR2, and a preconfigured spectrum type.

[0302] The PRACH configuration index in the RACH configuration table may be given as follows.

[0303] -For the RACH configuration table for random access configuration for FR1 and unpaired spectrum, the PRACH configuration index in the RACH configuration table can be given from the higher-layer parameter prach-ConfigurationIndexNew (if configured). Otherwise, the PRACH configuration index in the RACH configuration table can be given from prach-ConfigurationIndex, msgA-prach-ConfigurationIndex, msgA-prach-ConfigurationIndexNew (if configured), etc.

[0304] -For the RACH configuration table for random access configurations regarding FR1 and paired spectrum / supplementary uplink and for the RACH configuration table for random access configurations regarding FR2 and unpaired spectrum, the PRACH configuration index in the RACH configuration table may be given from higher layer parameters prach-ConfigurationIndex, msgA-prach-ConfigurationIndexNew (if configured), etc.

[0305] The RACH configuration table may be about PRACH configuration index, preamble format, n SFN A table of relationships between one or more of mod x=y, a subframe number, a starting symbol, a number of PRACH slots, a number of time-domain PRACH opportunities within a PRACH slot, and in some cases, a PRACH duration.

[0306] These situations are described below.

[0307] -(1) Random access configuration for FR1 and paired spectrum / supplementary uplink

[0308] -(2) Random access configuration for FR1 and unpaired spectrum

[0309] -(3) Random access configuration for FR2 and unpaired spectrum

[0310] Table 13 below shows a portion of an example of a RACH configuration index for (2) random access configuration of FR1 and unpaired spectrum.

[0311] [Table 13]

[0312]

[0313] The RACH configuration table indicates specific values ​​of parameters required for configuring RACH opportunities (e.g., preamble format, period, SFN offset, RACH subframe / slot index, starting OFDM symbol, number of RACH slots, number of opportunities, OFDM symbols used for RACH format, etc.). When a RACH configuration index is indicated, a specific value associated with the indicated index may be used.

[0314] For example, when the start OFDM symbol parameter is n, one or more consecutive (time domain) RACH opportunities may be configured from the OFDM symbol with index #n.

[0315] For example, the number of one or more RACH opportunities may be indicated by the following parameter: the number of time-domain PRACH opportunities within a RACH slot.

[0316] For example, a RACH slot may include one or more RACH opportunities.

[0317] For example, the number of RACH slots (in a subframe and / or slot with a specific SCS) may be indicated by the following parameter: Number of RACH Slots.

[0318] For example, the system frame number (SFN) including the RACH opportunity can be obtained by n SFN mod x=y is determined, where mod is a modular operation (modular arithmetic or modular operation), which is an operation for obtaining a remainder r obtained by dividing a dividend q by a divisor d (r=q mod(d)).

[0319] For example, the subframe / timeslot (index) including the RACH opportunity in the system frame may be indicated by the following parameter: RACH subframe / timeslot index.

[0320] For example, the preamble format used for RACH transmission / reception may be indicated by the following parameter: Preamble Format.

[0321] Reference Figure 16 (a), for example, when the starting OFDM symbol is indicated as 0, one or more consecutive (time domain) RACH opportunities can be configured from OFDM symbol #0. For example, the number of one or more RACH opportunities can depend on the value indicated by the following parameter: the number of time domain RACH opportunities within the RACH slot. For example, the preamble format can be indicated by the following parameter: preamble format. For example, preamble formats A1, A2, A3, B4, C0, C2, etc. can be indicated. For example, one of the last two OFDM symbols can be used as a GT, and the other can be used for transmission of other UL signals such as PUCCH, sounding reference signal (SRS), etc.

[0322] Reference Figure 16 (b), for example, when the starting OFDM symbol is indicated as 2, one or more consecutive (time domain) RACH opportunities may be configured from OFDM symbol #2. For example, 12 OFDM symbols may be used for RACH opportunities, and no GT may be configured in the last OFDM symbol. For example, the number of one or more RACH opportunities may depend on a value indicated by the following parameter: the number of time domain RACH opportunities within a RACH slot. For example, the preamble format may be indicated by the following parameter: preamble format. For example, preamble formats A1 / B1, B1, A2 / B2, A3 / B3, B4, C0, C2, etc. may be indicated.

[0323] Reference Figure 16(c), for example, when the starting OFDM symbol is indicated as 7, one or more consecutive (time domain) RACH opportunities can be configured from OFDM symbol #7. For example, 6 OFDM symbols can be used for RACH opportunities, and the last OFDM symbol (OFDM symbol #13) can be used for transmission of other UL signals such as PUCCH, SRS, etc. For example, the number of one or more RACH opportunities can depend on the value indicated by the following parameter: the number of time domain RACH opportunities within the RACH slot. For example, the preamble format can be indicated by the following parameter: preamble format. For example, preamble formats A1, B1, A2, A3, B3, B4, C0, C2, etc. can be indicated.

[0324] For example, the parameters included in the RACH configuration table may satisfy a predetermined correspondence relationship identified / determined by the RACH configuration table and the RACH configuration index. For example, a predetermined correspondence relationship may be satisfied between the following parameters: PRACH configuration index, RACH format, period (x) = 8, SFN offset (y), subframe number, starting symbol (index), number of PRACH slots within a subframe, number of PRACH opportunities within a PRACH slot, PRACH duration / OFDM symbol for the RACH format, etc. The correspondence relationship may be identified by the RACH configuration index and the RACH configuration table.

[0325] 3. Various embodiments of the present disclosure

[0326] Based on the above technical ideas, a detailed description of various embodiments of the present disclosure will be given. The above contents of Sections 1 and 2 are applicable to the various embodiments of the present disclosure described below. For example, operations, functions, terms, etc. not defined in various embodiments of the present disclosure may be performed and described based on Sections 1 and 2.

[0327] Symbols / abbreviations / terms used in the description of various embodiments of the present disclosure may be defined as follows.

[0328] -A / B / C: A and / or B and / or C

[0329] -BWP: Bandwidth Part

[0330] -CBRA: Contention-based random access

[0331] -CDM: Code Division Multiplexing (code domain sharing)

[0332] - Comb: Comb can refer to a method of mapping signals at regular intervals in the frequency domain. For example, comb 2 (comb-2 or 2-comb) can mean mapping the same specific RS to each RE spaced by two subcarriers. Comb 4 (comb-4 or 4-comb) can mean mapping the same specific RS to each RE spaced by four subcarriers.

[0333] -CFRA: Contention-Free Random Access

[0334] -CP-OFDM: Cyclic prefix-based Orthogonal Frequency Division Multiplexing, which can be understood as a case where transform precoding is disabled.

[0335] -DFT-s-OFDM: Discrete Fourier Transform-Spread Orthogonal Frequency Division Multiplexing, which can be understood as the case where transform precoding is enabled.

[0336] -DL: Downlink

[0337] -DM-RS (DMRS): Demodulation Reference Signal

[0338] -FDM: Frequency Division Multiplexing (frequency domain sharing)

[0339] -MCS: Modulation and Coding Scheme

[0340] -OCC: Orthogonal Cover Code

[0341] -OFDM: Orthogonal Frequency Division Multiplexing

[0342] -PAPR: Peak to Average Power Ratio

[0343] -PRACH: Physical Random Access Channel

[0344] -PRB: Physical Resource Block

[0345] -PRU: PUSCH resource unit

[0346] -PO: PUSCH timing

[0347] -PUSCH: Physical Uplink Shared Channel

[0348] -RA: Random Access

[0349] -RACH: Random Access Channel

[0350] -RAPID: Random Access Preamble Identifier

[0351] -RAR: Random Access Response

[0352] -RB: Resource Block

[0353] -RE: Resource Element

[0354] -RNTI: Radio Network Temporary Identifier

[0355] -RO: RACH timing or PRACH timing

[0356] -SCID: Scrambled Identifier

[0357] -TBS: Transport Block Size

[0358] -TDM: Time Division Multiplexing (time domain sharing)

[0359] -UL: Uplink

[0360] - Rel-15 (REL.15): Rel-15 refers to 3GPP Technical Specification (TS) Release 15. Additionally / alternatively, Rel-15 means a system supporting 3GPP TS Release 15 and / or a system capable of coexisting therewith.

[0361] - Rel-16 (REL.16): Rel-16 refers to 3GPP TS Release 16. Additionally / alternatively, Rel-16 means a system supporting 3GPP TS Release 16 and / or a system capable of coexisting therewith.

[0362] In the description of various embodiments, when it is mentioned that something is greater than / greater than or equal to A, it can be interpreted to mean that the thing is greater than or equal to / greater than A.

[0363] In the description of various embodiments, when it is mentioned that something is less than / less than or equal to B, it may be interpreted to mean that the thing is less than or equal to / less than B.

[0364] In the description of various embodiments, unless otherwise specified, (transmission of) PUSCH may be included in (transmission of) MsgA.

[0365] In the description of various embodiments, unless otherwise specified, PUSCH / PO / PRU may be interchanged.

[0366] In the 2-step RACH process, the MsgA sent in the UL may include the PRACH preamble and the PUSCH resources. For example, the PRACH preamble and the PUSCH resources may be mapped together based on the SSB, and it may be difficult to establish this relationship in a simple manner. For example, the RO state (e.g., periodicity, the number of available ROs, SSB to RO mapping relationship, etc.) and the PUSCH configuration (e.g., periodicity, the number of available ROs / POs, the number of DMRS antenna ports / sequences, etc.) may be considered together.

[0367] Various embodiments may relate to a method of configuring a MsgA PUSCH.

[0368] Various embodiments may be directed to a method of configuring DMRS for MsgA PUSCH.

[0369] Various embodiments may relate to RACH preamble to PUSCH (resource element) mapping methods for supporting a 2-step RACH procedure.

[0370] Figure 17 is a diagram schematically illustrating a method of operating a UE and a BS according to various embodiments of the present disclosure.

[0371] Figure 18 is a diagram schematically illustrating a method of operating a UE according to various embodiments.

[0372] Figure 19 is a diagram schematically illustrating a method of operating a BS according to various embodiments.

[0373] Reference Figures 17 to 19 In operations 1701 and 1801 according to various embodiments, the UE may obtain / generate MsgA. For example, the UE may obtain / generate MsgA by mapping the PRACH preamble to RO, mapping the PUSCH to PO, and / or mapping the DMRS.

[0374] In operations 1703 , 1803 , and 1901 according to various embodiments, the UE may transmit MsgA, and the BS may receive the MsgA.

[0375] In operations 1705 and 1903 according to various embodiments, the BS may decode (detect) Msg A. For example, the BS may decode Msg A to obtain a PRACH preamble, a PUSCH, and / or a DMRS included in the Msg A.

[0376] In operations 1707 , 1805 , 1905 according to various embodiments, the BS may transmit MsgB and / or Msg2 in response to MsgA, and the UE may receive MsgB and / or Msg2.

[0377] Detailed operations, functions, terms, etc. according to each exemplary embodiment may be performed and described based on various embodiments to be described later.

[0378] Hereinafter, various embodiments will be described in detail. It can be clearly understood by those skilled in the art that, unless mutually exclusive, the various embodiments described below can be combined in whole or in part to constitute other embodiments.

[0379] DMRS for MsgA PUSCH

[0380] DMRS configuration type for MsgA PUSCH

[0381] According to various embodiments, only Type 1 DMRS may be applied to MsgA PUSCH of the 2-step RACH procedure.

[0382] In NR systems to which various embodiments apply, two DMRS types may be supported: DMRS configuration type 1 and DMRS configuration type 2. For example, the DMRS type may be configured using dmrs-Type. If there is no corresponding information element (IE) (if the information does not exist), DMRS type 1 may be used.

[0383] For example, for configuration type 1, the smallest REG may be one RE in the frequency domain. For example, for configuration type 2, the smallest REG may be two consecutive REs in the frequency domain.

[0384] For example, for configuration type 1, three pairs of DMRS (6 REs) can be distributed in one OFDM symbol / one RB at intervals of four REs. The two REs in each pair can be separated by an interval of two REs. For example, all 6 REs of a DMRS symbol can be distributed to different REs in the frequency domain. For dual-symbol DMRS, 8 DMRS ports (ports 1000 to 1007) can be supported. For single-symbol DMRS, four DMRS ports (ports 1000 to 1003) can be supported.

[0385] For example, for configuration type 2, two pairs of DMRS (4 REs) can be distributed in one OFDM symbol / one RB at intervals of 6 REs. The two REs in each pair can be separated by an interval of one RE, which can mean that the two REs in each pair are consecutive. For dual-symbol DMRS, 12 DMRS ports (ports 1000 to 1011) can be supported. For single-symbol DMRS, 8 DMRS ports (ports 1000 to 1007) can be supported.

[0386] According to various embodiments, Type 1 DMRS may be applied to Msg3 PUSCH in a 4-step RACH procedure. For example, Type 1 DMRS may be used for Msg3 transmission in a specific UL BWP.

[0387] According to various embodiments, considering that the RACH configuration for the 2-step RACH procedure can be configured through the BWP-UplinkCommon applicable to the UE, only Type 1 DMRS can be applied to the MsgA PUSCH in the 2-step RACH procedure. For example, BWP-UplinkCommon can be a cell-specific IE used to configure common parameters for UL BWP.

[0388] PUSCH DMRS port / sequence

[0389] According to various embodiments, a network (eg, a BS) may configure the number of antenna ports for MsgA PUSCH DMRS.

[0390] According to various embodiments, the maximum number of antenna ports may be 4.

[0391] For example, when the number of configured antenna ports is 2, antenna port 0 and antenna port 1 may be used.

[0392] For example, when the number of configured antenna ports is 1, antenna port 0 may be used.

[0393] According to various embodiments, for Type 1 DMRS, when using one OFDM symbol, up to four antenna ports may be allocated. For example, the antenna ports may be configured with frequency resources (e.g., 2-comb resources) and cyclic shift values ​​(e.g., 0 and π (pi)).

[0394] According to various embodiments, a PRACH preamble mapping may be defined.

[0395] According to various embodiments, the PRACH preamble may be mapped to valid PRUs within the MsgA association period in the following order.

[0396] - First, in ascending order of the frequency resource index of the frequency reuse PO

[0397] -Secondly, in ascending order of DMRS index within a single PO

[0398] -- The DMRS index may be determined first in ascending order of the DMRS port index and second in ascending order of the DMRS sequence index.

[0399] -Third, in ascending order of the time resource index of the time division multiplexing PO within a PUSCH time slot

[0400] - Fourth, in ascending order of PUSCH slot index

[0401] - For multiple configurations, mapping may be performed between the PRUs of each MsgA PUSCH configuration and the preambles in the associated preamble group.

[0402] --Each MsgA PUSCH configuration can identify a subset of DMRS port / sequence combinations.

[0403] For example, one or more consecutive preamble indices of (valid) PRACH opportunities in a slot:

[0404] - First, in ascending order of preamble index within a PRACH opportunity

[0405] -Secondly, in ascending order of frequency resource index of frequency reuse PRACH opportunity

[0406] - Third, in ascending order of the time resource index of the time division multiplexing PRACH opportunity within the PRACH time slot

[0407] can be mapped to a (valid) PO:

[0408] - First, in ascending order of the frequency resource index of the frequency reuse PO

[0409] - Second, in ascending order of DMRS index within the PO, wherein the DMRS index may be determined first in ascending order of DMRS port index and second in ascending order of DMRS sequence index.

[0410] - Third, in ascending order of the time resource index of the time division multiplexing PO within the PUSCH time slot

[0411] - Fourth, in ascending order of PUSCH slot index.

[0412] According to various embodiments, a method of indicating DMRS resources including a DMRS port and / or a DMRS sequence may be provided.

[0413] In the 4-step RACH procedure, a single antenna port can be used for Msg3 transmission. However, in the 2-step RACH procedure, all antenna ports can be used to improve PUSCH resource efficiency.

[0414] According to various embodiments, a network (eg, a BS) may configure the number of antenna ports for MsgA PUSCH DMRS.

[0415] According to various embodiments, network coverage and / or geometry may be considered when determining the number of antenna ports. For example, if the network coverage is relatively wide and / or the geometry is not favorable for supporting multiple UEs in the PO, a relatively small number of antenna ports (e.g., 1 or 2) may be allocated. Conversely, for example, if the 2-step RACH process is performed in a relatively narrow network coverage and / or with relatively good geometry, a relatively large number of antenna ports (e.g., 2 or 4) may be allocated in the PO.

[0416] According to various embodiments, if two antenna ports are configured, antenna ports 0 and 1 (or antenna ports 2 and 3) with the same frequency resources and different cyclic shift values ​​can be used. This is because the cyclic shift can identify the antenna port even if the OFDM symbol reception timing is quite large (e.g., FFT size / 4).

[0417] MsgA PUSCH DMRS sequence initialization

[0418] According to various embodiments, in the case of CP-OFDM (when DMRS is based on CP-OFDM or when transform precoding is disabled), up to two different initial values ​​and / or seed values ​​(seed values) can be configured by a higher layer signal (e.g., SIB1 and / or RACH-ConfigCommon). According to various embodiments, the sequence can be specified / indicated according to RAPID (in the description of various embodiments, the term "according to" can be replaced with the following terms: based on, using, etc.).

[0419] Additionally / alternatively, according to various embodiments, when transform precoding is disabled, the following equation 1 may be used for the pseudo-random sequence generator for MsgAPUSCH. According to various embodiments, when transform precoding is disabled, the pseudo-random sequence generator for MsgAPUSCH may be initialized according to the following equation 1.

[0420] [Formula 1]

[0421] c init =(2 17 (N slot symb n u s，f +l+1)(2N nSCID ID +1)+2N nsCID ID +n SCID )mod 2 31

[0422] For example, C init It can represent the initial value of the scrambling sequence generator.

[0423] For example, N slot symb It can represent the number of symbols per time slot.

[0424] For example, u s，f It can represent the time slot number in the frame for SCS configuration u.

[0425] For example, N 0 ID 、N 1 ID ,…,N M-1 ID ∈{0, 1, ..., 65535} can be given by the higher-layer parameters scramblingID0, scramblingID1 and scramblingIDM-1 in the higher-layer signal, respectively.

[0426] For example, SCID∈{0, 1, ..., M-1} can be specified according to RAPID.

[0427] For example, M may have a maximum value of 2.

[0428] According to various embodiments, in the case of DFT-s-OFDM (when DMRS is DFT-s-OFDM based or when transform precoding is enabled), one root index of the Zadoff-Chu (ZC) sequence may be configured by a higher layer signal.

[0429] According to various embodiments, multiple DMRS sequences can be applied to each antenna port to improve PUSCH resource efficiency. In the case of CP-OFDM, a pseudo-noise (PN) sequence can be applied as a DMRS sequence. For UL multi-user multiple input and multiple output (MU-MIMO), two different seed values ​​can be configured through RRC signals, and one of the two seed values ​​can be specified / indicated by DCI. For spatially separated UEs, two different DMRS sequences can be applied even if the UEs are assigned the same antenna port. For MsgA PUSCH, multiple DMRS sequences can be applied when CP-OFDM is used. The seed value can be configured through SIB1 and / or RACH-ConfigCommon, and the value can be specified / indicated based on RAPID. Specifically, the seed value can be configured through SIB1 and / or RACH-ConfigCommon, and the value can be specified / indicated based on the RAPID of at least one of the configured seed values. For example, RACH-ConfigCommon can be an IE for specifying cell-specific random access parameters.

[0430] According to various embodiments, for the MsgA PUSCH DMRS, the above equation 1 may be used to initialize a pseudo-random sequence generator.

[0431] According to various embodiments, for MsgA PUSCH, the seed value of Equation 1 (eg, N 0 ID and N 1 ID ) can be configured through SIB1 and / or RACH-ConfigCommon.

[0432] According to various embodiments, n in the above formula 1 can be specified according to RAPID. SCID For example, if the PRU is configured with a DMRS port and a DMRS sequence index (e.g., n SCID ), then n can be automatically obtained from the RAPID to PRU mapping SCID .

[0433] According to various embodiments, in case of DFT-s-OFDM, a low PAPR sequence (eg, a ZC sequence) may be applied, and one sequence may be allocated as a DMRS sequence.

[0434] According to various embodiments, the number of PRUs in a PO may be one of {1, 2, 4, 8}.

[0435] According to various embodiments, when the number of PRUs in the PO is 1, only one set may be defined for (the number of) DMRS ports and (the number of) DMRS sequences.

[0436] According to various embodiments, when the number of PRUs in the PO is 2, two sets of combinations of DMRS ports and DMRS sequences (e.g., {2, 1} and {1, 2}) may be defined. For example, when two antenna ports are used in the PO, one of two (CDM) groups may be configured for the two antenna ports.

[0437] According to various embodiments, when the number of PRUs in the POR is 4, two sets of combinations of DMRS ports and DMRS sequences may be defined (e.g., {4, 1}, {2, 2}). For example, when four antenna ports are used in the POR, two CDM groups may be used with the same DMRS sequence. For example, when two antenna ports are used in the POR, one of the two (CDM) groups may be configured with two different DMRS sequences.

[0438] According to various embodiments, when the number of PRUs in the PO is 8, four antenna ports in two CDM groups may be used with two different DMRS sequences. According to various embodiments, if there is no separate configuration, two (CDM) groups may be used.

[0439] According to various embodiments, multiple PRUs may be defined based on a combination of (the number of) DMRS ports and (the number of) DMRS sequences within a PO.

[0440] For example, the set of PRUs in PO can be defined as shown in Table 14.

[0441] [Table 14]

[0442] Number of PRUs in the PO {Number of DMRS ports, number of DMMRS sequences} 1 {1，1} 2 {2，1}，{1，2} 4 {4，1}，{2，2} 8 {4，2}

[0443] For example, when the number of PRUs in the PO is 1, only one set may be defined for (the number of) DMRS ports and (the number of) DMRS sequences.

[0444] For example, when the number of PRUs in the PO is 2, two sets of combinations of DMRS ports and DMRS sequences (e.g., {2, 1}, {1, 2}) can be defined. For example, when two antenna ports are used in the PO, one CDM group in two (CDM) groups can be configured for the two antenna ports.

[0445] For example, when the number of PRUs in the POR is 4, two sets of combinations of DMRS ports and DMRS sequences can be defined (e.g., {4, 1}, {2, 2}). For example, when four antenna ports are used in the POR, two CDM groups can be used with the same DMRS sequence. For example, when two antenna ports are used in the POR, one CDM group of the two (CDM) groups can be configured with two different DMRS sequences.

[0446] For example, when the number of PRUs in the PO is 8, four antenna ports in two CDM groups can be used with two different DMRS sequences. According to various embodiments, if there is no separate configuration, two (CDM) groups can be used.

[0447] 3.2.MsgA PUSCH Configuration

[0448] MsgA PUSCH scrambling sequence

[0449] According to various embodiments, for the MsgA PUSCH data scrambling sequence, RA-RNTI and / or RAPID may be used as a seed value for sequence initialization of CBRA.

[0450] According to various embodiments, for the MsgA PUSCH data scrambling sequence, the C-RNTI may be used as a seed value for sequence initialization of the CFRA.

[0451] According to various embodiments, the value c used for scrambling sequence initialization int You can use n RNTI and n ID Configuration.

[0452] According to various embodiments, it may be determined which values ​​need to be applied to n for MsgA PUSCH for a 2-step RACH procedure. RNTI and n ID .

[0453] For example, in the 4-step RACH process, for Msg3 PUSCH, TC-RNTI / C-RNTI can be used as n RNTIOn the other hand, for MsgA PUSCH of the 2-step RACH procedure, TC-RNTI / C-RNTI may not be applicable to UEs in RRC_IDLE or RRC_INACTIVE state. Therefore, according to various embodiments, an RNTI different from TC-RNTI / C-RNTI (e.g., RA-RNTI) may be used as n RNTI According to various implementations, C-RNTI can be used as n RNTI Applicable to UE in RRC_CONNECTED state.

[0454] In the 4-step RACH process, for Msg3 PUSCH, N ID cell (Physical Cell Identifier (PCI)) can be used as n ID On the other hand, for MsgA PUSCH of 2-step RACH process, multiple RAPIDs can be mapped to one PO. In this case, for example, inter-layer interference between PUSCH data REs may increase. According to various embodiments, in order to reduce interference, the method consisting of n ID Instead of N, multiple scrambling sequences are generated by different values ​​of ID cell (Applied to UL MIMO)) According to various embodiments, in the case of CBRA, for MsgA PUSCH, RAPID can be used as n ID According to various embodiments, in the case of CBRA, for MsgA PUSCH, RAPID and C-RNTI may be applied as seed values ​​for sequence initialization.

[0455] According to various embodiments, the PUSCH scrambling sequence initialization formula may vary depending on the use case of the mapping between preambles and PRUs.

[0456] According to various embodiments, when one RAPID is mapped to multiple PRUs in a PO, a DMRS index-based PUSCH scrambling sequence initialization formula may be used instead of a RAPID-based PUSCH scrambling sequence initialization formula.

[0457] According to various embodiments, when one RAPID is mapped to multiple PRUs in each PO, a RAPID-based PUSCH scrambling sequence initialization formula may be used.

[0458] According to various embodiments, the initialization ID for MsgA PUSCH scrambling may be defined as shown in Equation 2 below.

[0459] [Formula 2]

[0460] cinit =RA-RNTI×2 16 +RAPID×2 10 +n ID

[0461] For example, C init It can represent the initial value of the scrambling sequence generator.

[0462] For example, ID It can be configured by cell-specific higher-layer parameters, and / or n ID =N ID cell .

[0463] According to various embodiments, RAPID may or may not change the DMRS index.

[0464] According to various embodiments, a one-to-many mapping between preambles and PRUs may be supported and / or may not be supported.

[0465] According to various implementations, for one-to-many mapping, the following two cases may be considered:

[0466] -1) Case 1: One RAPID can be mapped to multiple PRUs in PO.

[0467] -2) Case 2: One RAPID can be mapped to multiple PRUs in each PO.

[0468] For example, RAPID included in the equations (e.g., Equation 1) for initializing the scrambling sequence may be for improving the inter-user interference randomization effect on the PUSCH resources.

[0469] In case 1, if multiple UEs that have selected the same RAPID transmit PUSCHs with the same scrambling sequence, the BS may not be able to obtain inter-user interference randomization effect.

[0470] In case 2, the BS can obtain an inter-user interference randomization effect according to an equation (equation 1, etc.) for initializing the scrambling sequence.

[0471] According to various embodiments, whether to use the equation for initializing the scrambling sequence including RAPID (Equation 1, etc.) may be determined according to which case is selected for one-to-many mapping.

[0472] In case 1, RAPID may be changed to a DMRS index.

[0473] In case 2, RAPID can be used as is.

[0474] For example, a scrambling sequence generator for generating a PUSCH (or a scrambling sequence generator for a PUSCH) may be initialized according to the following Formula 3. According to various embodiments, at least one of the parameters used in the following Formula 3 may be generated / obtained / determined. Formula 3 may be understood as a more specific formula than Formula 2.

[0475] [Formula 3]

[0476]

[0477] For example, C init It can represent the initial value of the scrambling sequence generator.

[0478] For example, the value of each parameter can be determined as follows.

[0479] - If the RNTI is a C-RNTI, a Modulation and Coding Scheme C-RNTI (MCS-C-RNTI), a Semi-Persistent Channel State Information RNTI (SP-CSI-RNTI), or a Configured Scheduling RNTI (CS-RNTI), if the (PUSCH) transmission is not scheduled by DCI format 1_0 in the CSS, and if the higher layer parameter dataScramblingIdentityPUSCH is configured, then n ID ∈{0, 1, ..., 1023} may have a value indicated in the higher layer parameter dataScramblingIdentityPUSCH.

[0480] - If the (PUSCH) transmission is triggered by a type 2 random access procedure (2-step RACH procedure) and if the higher layer parameter msgA-dataScramblingIdentity is configured, then n ID ∈{0, 1, ..., 1023} may have a value indicated by a higher layer parameter msgA-dataScramblingIdentity.

[0481] -otherwise, That is, n ID Can have the same value as PCI. For example, n ID Can have a value from 0 to 1007.

[0482] -n RAPID It can be the index of the random access preamble code sent for MsgA. For example, n RAPID It may correspond to information related to the PRACH preamble code selected by the UE (or user) as the seed value of the scrambling sequence, and the user may select the seed value of the scrambling sequence by n RAPID Logo.

[0483] -n RNTIIt may have the same value as the RA-RNTI for MsgA (for PUSCH included in MsgA). RNTI may be the seed value of the scrambling sequence, and more specifically, n RNTI It may correspond to the RNTI used to monitor the response (from the BS) to the above-mentioned RA-RNTI or MsgA PUSCH. As another example, n RNTI It can have the same value as the RA-RNTI used for the 4-step RACH procedure.

[0484] For example, inter-cell interference can be achieved by n ID Randomization.

[0485] In the 2-step RACH procedure, there may be RA-RNTI and MsgB-RNTI associated with a specific RO.

[0486] According to various embodiments, the RA-RNTI may be used to generate / obtain the PUSCH data scrambling sequence, and the MsgB-RNTI may be used to monitor the PDCCH for MsgB.

[0487] That is, according to various embodiments, the usage of the RA-RNTI and MsgB-RNTI associated with a specific RO may be distinguished.

[0488] In addition, according to various embodiments, RA-RNTI is distinguished from RAPID and used as a seed value for generating / obtaining a PUSCH data scrambling sequence.

[0489] Supported MCS and time-frequency resource size for PUSCH in MsgA

[0490] According to various embodiments, a limited number of MCS levels may be used for PUSCH in Msg A. For example, one and / or two MCS levels may be used.

[0491] According to various embodiments, QPSK for CP-OFDM only may be applied to PUSCH in MsgA.

[0492] According to various embodiments, two types of coding rates may be used.

[0493] According to various embodiments, the MCS may be indicated only for the PUSCH configuration. According to various embodiments, of the MCS used for MsgA PUSCH and the RRC used for TBS, only the MCS may be signaled. According to various embodiments, the TBS may be determined based on a predetermined correspondence with MCS values ​​using a predefined TBS table. According to various embodiments, a range of TBS and / or MCS values ​​may be preconfigured.

[0494] According to various embodiments, a modulation order and / or coding rate for MsgA PUSCH may be provided.

[0495] In the 4-step RACH procedure, the MCS for Msg3 can be assigned / indicated by the UL grant in the RAR message. For example, the BS can assign MCSs from low to high indexes based on the UE's channel state. For example, time / frequency resources for PUSCH can be allocated based on the selected MCS level and the required coverage.

[0496] On the other hand, the 2-step RACH procedure may have difficulty enabling flexible MCS selection. If the UE selects the MCS level for UL transmission based on DL measurement results, it may be difficult to apply the MCS level to UL transmissions because channel conditions and interference levels may vary significantly between DL and UL channels. In addition, the amount of resources required for MsgA PUSCH may vary depending on the MCS level.

[0497] That is, if multiple MCS levels are allowed, many types of PUSCH resources may be defined and / or pre-assigned, which may be bad in terms of resource utilization.

[0498] According to various embodiments, an extremely limited number of MCS levels may be used for the PUSCH in MsgA. For example, one and / or two MCS levels may be used. According to various embodiments, only QPSK for CP-OFDM may be applied to the PUSCH in MsgA. According to various embodiments, two types of coding rates may be used.

[0499] According to various embodiments, when multiple sets of DMRS frequency resources are allowed, each DMRS frequency resource (eg, CDM group) may be configured through a MsgAPUSCH configuration.

[0500] According to various embodiments, when multiple MCS levels are allowed for PUSCH transmission, multiple types of PUSCH resources may be configured through MsgA PUSCH configuration according to the MCS levels.

[0501] According to various embodiments, the value range configured by ssb-perRACH-OccasionAndCB-PreamblesPerSSB-msgA (msgA-SSB-PerRACH-OccasionAndCB-PreamblesPerSSB) can be divided into N parts (where N is a natural number). According to various embodiments, a portion of the value range can consist of a RAPID set, which can be associated with the MsgA PUSCH configuration. In addition, according to various embodiments, other portions of the value range can be associated with other MsgAPUSCH configurations.

[0502] According to various embodiments, msgA-SSB-PerRACH-OccasionAndCB-PreamblesPerSSB may be included in RACH-ConfigCommonTwoStepRA for specifying cell-specific parameters for a 2-step RACH procedure.

[0503] According to various embodiments, msgA-SSB-PerRACH-OccasionAndCB-PreamblesPerSSB may be defined as shown in Table 15 below.

[0504] [Table 15]

[0505]

[0506] According to various embodiments, when multiple MCS levels are allowed for PUSCH transmission, multiple types of PUSCH resources may be defined based on the MCS level. Consequently, according to various embodiments, when a PUSCH resource is associated / correlated with a RAPID, the RAPID may also be associated / correlated with an MCS level. Therefore, according to various embodiments, if the UE determines an appropriate MCS level for PUSCH transmission, the UE may select the RAPID associated with the MCS level.

[0507] According to various embodiments, if multiple sets of DMRS frequency resources are allowed, each DMRS frequency resource may be defined in association with an MCS level.

[0508] For example, assuming two different PUSCH resources (e.g., a first larger frequency resource (set) for a lower MCS level and a second smaller frequency resource (set) for a higher MCS level), two different frequency resource sets can be specified for each PUSCH resource.

[0509] Figure 20 is a diagram illustrating an exemplary resource configuration for MsgA according to various embodiments. Specifically, Figure 20An example of specifying DMRS REs according to PUSCH resources and MCS levels according to various embodiments is illustrated.

[0510] Reference Figure 20 For example, when a relatively high MCS level is used for a PUSCH included in MsgA, a relatively small frequency resource consisting of one RB may be used for the PUSCH included in MsgA. That is, when a relatively high MCS level is used for a PUSCH included in MsgA, the PUSCH included in MsgA may be allocated to a relatively small frequency resource consisting of one RB.

[0511] For example, when a relatively low MCS level is used for the PUSCH included in MsgA, a relatively large frequency resource consisting of two RBs can be used for the PUSCH included in MsgA. That is, when a relatively low MCS level is used for the PUSCH included in MsgA, the PUSCH included in MsgA can be allocated to a relatively large frequency resource consisting of two RBs.

[0512] For example, a first comb including a set of REs each having an even index and a second comb including a set of REs each having an odd index may be configured.

[0513] For example, when a relatively high MCS level is used for a PUSCH included in MsgA, a DMRS may be allocated to the first comb.

[0514] In addition, when a relatively low MCS level is used for a PUSCH included in MsgA, a DMRS may be allocated to the second comb.

[0515] That is, DMRS resources (eg, DMRS ports) for the PUSCH included in MsgA may be determined based on the MCS level.

[0516] Alternatively, for multiple PUSCH configurations with overlapping DMRS symbols, the BS (and / or network) may allocate a different CDM group to each MsgA PUSCH configuration.

[0517] According to various embodiments, at least two MsgA PUSCH configurations may be supported. According to various embodiments, parameters (e.g., MCS, MCS / TBS, antenna port / sequence, time / frequency resources for PO, duration / time slot offset for PO group, etc.) may be independently configured for each MsgA PUSCH configuration. According to various embodiments, multiple configurations may be allowed to configure different MCS levels and / or different time / frequency resources. Additionally / alternatively, according to various embodiments, different time periods / offsets may be configured for each MsgA PUSCH configuration.

[0518] On the other hand, if the number of valid POs in the time domain varies, MsgA preamble to PRU mapping may become more difficult.Therefore, according to various embodiments, POs configured by different MsgA PUSCH configurations may be located at least at the same time position.

[0519] According to various embodiments, the configured POs may overlap in the time / frequency domain. According to various embodiments, if different CDM groups are configured for each PO, the network may separate multiple UL signals sent on the time / frequency resources (see Figure 20 ).

[0520] PUSCH configuration indication

[0521] According to various embodiments, the preamble group in CBRA may be used for both MsgA PUSCH indication and preamble group indication.

[0522] - For example, if preamble groups A and B are used for a 2-step RACH procedure, these preamble groups can be used to indicate both the MsgAPUSCH configuration and the preamble group.

[0523] --For example, the UE may select a preamble group based on the message size for transmission.

[0524] - For example, if preamble groups A and B are not configured for 2-step RACH procedure, these preamble groups may only be used to indicate MsgA PUSCH configuration.

[0525] --For example, the UE may select a preamble group according to the channel status (eg, synchronization signal reference signal received power (SS-RSRP)).

[0526] According to various embodiments, the value range configured by ssb-perRACH-OccasionAndCB-PreamblesPerSSB-msgA (msgA-SSB-PerRACH-OccasionAndCB-PreamblesPerSSB) may be divided into N parts (where N is a natural number). According to various embodiments, a portion of the value range may consist of a RAPID set, which may be associated with an MsgA PUSCH configuration. According to various embodiments, other portions of the value range may be associated with other PUSCH configurations.

[0527] According to various embodiments, methods of indicating selection of different PUSCH configurations may be provided.

[0528] According to various embodiments, for the two configurations, different preamble groups may be used to indicate the different configurations.

[0529] According to various embodiments, the maximum number of configurations may be defined as follows:

[0530] - In REL.16, for a UE in RRC_IDLE / INACTIVE state, two or more MsgA PUSCH configurations may not be supported.

[0531] - For UE in RRC_ACTIVE state:

[0532] --A maximum of two MsgA PUSCH configurations can be supported in UL BWP.

[0533] ---When MsgA PUSCH configuration is not configured for UL BWP, the initial BWP configuration can be applied.

[0534] ---The preamble group based method defined for RRC_IDLE / INACTIVE state can be used.

[0535] ---The number of MsgA PUSCH configurations may or may not be equal to the number of UEs in RRC_IDLE / INACTIVE state.

[0536] ---At least one of the PRACH configuration or the MsgA PUSCH configuration may be BWP-specific and / or cell-specific.

[0537] According to various embodiments, preamble groups A and B may be introduced for a 2-step RACH procedure.

[0538] According to various embodiments, the selection formula of REL.15 for the 4-step RACH procedure may be used to select one of the following 2-step RACH preamble groups: preamble groups A and B.

[0539] According to various embodiments, a parameter ra-MsgASizeGroupA (ra-MsgA-SizeGroupA) may be introduced for the data threshold.

[0540] According to various embodiments, ra-MsgASizeGroupA (ra-MsgA-SizeGroupA) may be defined as shown in Table 16 below.

[0541] [Table 16]

[0542]

[0543] According to various embodiments, the preamble in the CBRA may be used to indicate the PUSCH configuration.

[0544] According to various embodiments, two preamble groups (eg, group A and group B) in CBRA may be used to indicate message size.

[0545] According to various embodiments, when preamble groups A and B are activated, the preamble groups may be aligned with the PUSCH configurations. According to various embodiments, depending on the TBS size of preamble groups A and B, different sized time / frequency resources may be allocated for each PUSCH in different PUSCH configurations. According to various embodiments, the UE may select the preamble group and PUSCH configuration based on the TBS size to be transmitted.

[0546] According to various embodiments, when the network does not operate preamble groups A and B, the preamble group can be used only to indicate the PUSCH configuration. According to various embodiments, since the configured PUSCH resources can have different MCS levels for the same TBS size, the UE can select the preamble group according to the channel status (e.g., based on RSRP, etc.).

[0547] Intra-slot frequency hopping and guard band

[0548] According to various embodiments, intra-slot hopping (intra-slot hopping) may be established without a guard period in the PO.

[0549] According to various embodiments, intra-slot hopping may be supported for MsgA PUSCH.

[0550] According to various embodiments, PRB-level guard band configurations between frequency division multiplexed (FDMed) POs, each consisting of PRB values ​​{0, 1}, may be supported.

[0551] According to various embodiments, intra-slot hopping per PO for MsgA may be configured on a per-MsgA basis.

[0552] - According to various embodiments, the hopping pattern may be based on the Msg3 hopping pattern of REL.15.

[0553] - According to various embodiments, UL-BWP specific parameters may be used.

[0554] - According to various embodiments, a guard period between transitions may or may not be used.

[0555] - According to various embodiments, PO can be continuous and / or discontinuous in time.

[0556] According to various embodiments, the inter-hop guard period may or may not be used. According to various embodiments, the use of a guard period between hops may or may not be allowed.

[0557] According to various embodiments, frequency diversity gain may be obtained from time slot hopping.

[0558] For example, if a guard time is configured, then the duration of twice the guard time may be required within the PO. For example, intra-time slot hopping may not provide performance gains compared to frequency diversity gain and energy loss. Therefore, according to various embodiments, time slot hopping can be configured within the PO without any guard period.

[0559] 3.3. Mapping of RACH Preamble and PUSCH Resources

[0560] RO mapping / RACH preamble configuration for 2-step RACH

[0561] According to various embodiments, ROs may be configured / mapped based on whether RO sharing is allowed between a 2-step RACH procedure and a 4-step RACH procedure.

[0562] According to various embodiments, for RO separation between a 2-step RACH procedure and a 4-step RACH procedure, configuration of a subset of ROs in a used timeslot may be allowed.

[0563] According to various embodiments, for RO separation between a 2-step RACH procedure and a 4-step RACH procedure, a configuration for using OFDM symbols in the first RACH half-slot as RO may be allowed.

[0564] According to various embodiments, parameters for updating / reconfiguring the values ​​of parameters configured through RACH configuration may be introduced. For example, parameters for updating / reconfiguring the number of ROs in a slot, the starting OFDM symbol, etc. may be introduced.

[0565] For example, the RO may be shared between a 2-step RACH procedure and a 4-step RACH procedure. For example, the PRACH preamble for the 4-step RACH procedure and the PRACH preamble for the 2-step RACH procedure may be configured / specified separately. For example, in the two cases of allowing and not allowing RO sharing, the PRACH preamble for the 4-step RACH procedure and the PRACH preamble for the 2-step RACH procedure may be configured / specified separately.

[0566] For example, if 64 PRACH preambles are allocated for a contention-based RACH process, the first 32 PRACH preambles may be configured / indicated to be PRACH preambles for a 4-step RACH process and the last 32 PRACH preambles may be configured / indicated to be PRACH preambles for a 2-step RACH process. For example, the corresponding configuration / indication may be based on SIB1 and / or a RACH configuration included in UE-specific RRC signaling.

[0567] For example, a PRACH preamble may be understood as a code-domain resource that may be identified by a root index of the preamble. For example, upon receiving a PRACH preamble, the BS may check whether the corresponding PRACH preamble is a PRACH preamble for a 4-step RACH procedure and / or a PRACH preamble for a 2-step RACH procedure, so that the BS may identify whether the UE sending the PRACH preamble desires to initiate a 2-step RACH procedure or a 4-step RACH procedure.

[0568] On the other hand, if RO sharing is not allowed (that is, for RO separation), the RO for the 4-step RACH process and the RO for the 2-step RACH process can be separated. In this case, the BS can identify whether the UE transmitting the PRACH preamble code desires to initiate a 2-step RACH process or a 4-step RACH process based on the corresponding RO.

[0569] According to various embodiments, among the PRACH preambles within the RO configured for the (contention-based) 4-step RACH procedure (in addition to the PRACH preamble used for the 4-step RACH procedure), a PRACH preamble can be configured for the (contention-based) 2-step RACH procedure. According to various embodiments, the BS can identify the purpose of the PRACH transmission (e.g., whether the PRACH transmission is for the 2-step RACH procedure or the 4-step RACH procedure). According to various embodiments, since the PRACH preamble is separated into the PRACH preamble for the 2-step RACH procedure and the PRACH preamble for the 4-step RACH procedure, the BS can determine whether the PRACH transmission is for the 2-step RACH procedure or the 4-step RACH procedure based on the PRACH preamble.

[0570] According to various embodiments, for RO sharing, the PUSCH in MsgA may be allocated to a PUSCH slot following a RACH slot.

[0571] According to various embodiments, when RO sharing is not allowed, an RO for a 2-step RACH procedure may be configured. According to various embodiments, at least one of the following two methods may be considered to configure an RO for a 2-step RACH procedure.

[0572] 1) Slot-level TDM / slot-level multiplexing: According to various embodiments, the RACH configuration table used for the 4-step RACH process can be reused. For example, the RACH configuration table can be designed assuming that most OFDM symbols in a RACH slot or the second RACH half-slot are used as RO. Therefore, in this case, RO and PUSCH can be multiplexed in different slots.

[0573] -2) Symbol-level TDM / symbol-level multiplexing: According to various embodiments, the OFDM symbols in the first RACH half-slot may be configured to be used as RO. According to various embodiments, the OFDM symbols after RO may be allocated for the PUSCH of MsgA.

[0574] Figure 21 is a diagram illustrating an exemplary MsgA configuration according to various embodiments. Specifically, Figure 21 An exemplary method of multiplexing the RO for MsgA and the PUSCH for MsgA at the slot level is shown.

[0575] Reference Figure 21 , the RO for transmitting the PRACH preamble included in the MsgA and the PO for transmitting the PUSCH included in the MsgA may be time division multiplexed (TDM) at a slot level.

[0576] For example, the RO may be included in or mapped to a RACH slot located earlier than the PUSCH slot in the time domain. In addition, the PO may be included in or mapped to a PUSCH slot located after the RACH slot in the time domain.

[0577] For example, each of the RO and / or PO may be multiplexed in each time slot in various ways.

[0578] Figure 21 (a) illustrates an example in which RO is TDMed in a RACH slot and PUSCH is FDM / TDMed in a PUSCH slot.

[0579] Figure 21 (b) illustrates an example in which RO is FDM / TDM in a RACH slot and PUSCH is FDM in a PUSCH slot.

[0580] Figure 21 (c) illustrates an example in which RO is FDMed in a RACH slot and PUSCH is TDMed in a PUSCH slot.

[0581] Figure 21 (d) illustrates an example in which RO is TDMed in a RACH slot and PUSCH is TDM / CDMed in a PUSCH slot.

[0582] A prescribed time offset may be set between the RO and the PO in the time domain. That is, a prescribed time offset may be configured between the RACH time slot including the RO and the PUSCH time slot including the PO in the time domain.

[0583] For example, the corresponding time offset may consist of a predetermined number of time slots.

[0584] As an opposite example, when no time offset is configured, the RACH slot and the PUSCH slot may be continuous in the time domain.

[0585] Figure 22 is a diagram illustrating an exemplary MsgA configuration according to various embodiments. Specifically, Figure 22 An exemplary method of multiplexing the RO for MsgA and the PUSCH for MsgA at the symbol level is shown.

[0586] Reference Figure 22 , the RO used to transmit the PRACH preamble included in MsgA and the PO used to transmit the PUSCH included in MsgA may be TDM-ed at the symbol level.

[0587] For example, RO and PO may be included in one time slot.

[0588] For example, RO may be included in or mapped to a RACH half-slot located earlier than a PUSCH half-slot in the time domain. In addition, PO may be included in or mapped to a PUSCH half-slot located after a RACH half-slot in the time domain.

[0589] For example, RO may be included in or mapped to one or more OFDM symbols in a RACH half-slot. In addition, PO may be included in or mapped to one or more OFDM symbols in a PUSCH half-slot.

[0590] For example, each of the RO and / or PO may be multiplexed in various ways within each half-slot.

[0591] Figure 22 (a) illustrates an example in which one RO is configured in a RACH half slot and a PUSCH is FDMed in a PUSCH half slot.

[0592] Figure 22 (b) illustrates an example in which RO is FDMed in a RACH half slot and PUSCH is TDMed in a PUSCH half slot.

[0593] Figure 22 (c) illustrates an example in which RO is TDMed in a RACH half slot and PUSCH is FDM / TDMed in a PUSCH half slot.

[0594] Figure 22 (d) illustrates an example in which RO is FDM / TDM in a RACH half slot and PUSCH is TDM / CDM in a PUSCH half slot.

[0595] RACH preamble to PRU mapping and / or its periodicity for 2-step RACH

[0596] According to various embodiments, a (RACH preamble to PRU) mapping may be defined between MsgA RO in period A and MsgA RO in period B.

[0597] According to various embodiments, period B may be determined based on the SSB to RACH association period. For example, period B has the same duration (length) as period A, but its starting point may be shifted by a single offset of the MsgA PUSCH configuration.

[0598] According to various embodiments, period A may be determined based on the SSB to RACH association period. For example, since the number of valid MsgA ROs is identified within the SSB to RO association period, period A may be the same as the SSB to RACH association period.

[0599] According to various embodiments, the preamble in the available / valid RO of the RACH slot preceding the available / valid PO may be mapped to the PRU within the available / valid PO.

[0600] According to various embodiments, the associated period for SSB to RO mapping may be applied to RACH preamble to PRU mapping. According to various embodiments, the preamble in the available / valid RO in the associated period for SSB to RO mapping may be mapped to the PRU in the available / valid PO in the associated period.

[0601] According to various embodiments, a single offset value for indicating the location of the PO group may be allowed. According to various embodiments, if the periodicity of the RACH is the same as the periodicity of the PO group, each RACH slot may be mapped to a PO group.

[0602] According to various embodiments, the mapping rule between RACH preamble and PRU may be defined as follows:

[0603] -0) Verify which POs are available.

[0604] -1) The preamble in the available RO of the RACH slot preceding the available PO can be mapped to the PRU in the available PO.

[0605] -2) The preamble in the available RO in period A can be mapped to the PRU in the available PO in period B.

[0606] --A) (One-to-one mapping) If the number of preambles of the CBRA in the available RO in period A is the same as the number of PRUs in the available PO in period B, all preambles of the CBRA may be mapped to all PRUs.

[0607] --B) (Many-to-one mapping) If the number of preambles of the CBRA in the available RO in period A is greater than the number of PRUs in the available PO in period B, all preambles of the CBRA may be mapped to all PRUs and / or a subset thereof. When a subset of PRUs is used, the remaining PRUs may not be used for the 2-step RACH procedure.

[0608] --C) (One-to-one mapping with multiple cycles) When the number of preambles of the CBRA in the available RO in period A is less than the number of PRUs in the available PO in period B, all preambles of the CBRA may be mapped to all PRUs and / or a subset thereof. When a subset of PRUs is used, the remaining PRUs may not be used for the 2-step RACH procedure.

[0609] --If a set (or multiple) of actually transmitted SSBs (ATSS) mapped to RO in the SSB to RO association period is not completely mapped to the PRUs in the available PO in period B, the preamble in the available RO may not be mapped to the PRUs in the available PO.

[0610] --The remaining preambles not mapped to PRUs for the 2-step RACH procedure can be used for MsgA preamble only transmission.

[0611] - In many-to-one mapping, consecutive PRACH preambles (N consecutive PRACH preamble indices) may be mapped to the same PRU, and then the next consecutive PRACH preamble (N consecutive PRACH preamble indices) may be mapped to the next PRU.

[0612] For example, the association period for SS / PBCH block to PRACH opportunity mapping starting from frame 0 may be equal to the minimum value in the set determined by the PRACH configuration period according to Table 17.

[0613] [Table 17]

[0614] PRACH configuration period (msec) Association period (number of PRACH configuration periods) 10 {1，2，4，8，16} 20 {1，2，4，8} 40 (1，2，4} 80 {1，2} 160 {1}

[0615] For example, a predetermined number of SS / PBCH blocks obtained from the value of ssb-PositionsInBurst indicating the ATSS included in SIB1 and / or ServingCellConfigCommon (which is an IE for configuring cell-specific parameters of the UE's serving cell) may be mapped to one or more PRACH opportunities within the association period. For example, a predetermined number of SS / PBCH blocks may be cyclically mapped to the PRACH opportunity a predetermined integer number of times within the association period. For example, the association pattern period may include one or more association periods, and the pattern between the PRACH opportunity and the SS / PBCH index may be determined to repeat at most every 160 ms.

[0616] For paired spectrum, all PRACH opportunities may be valid.

[0617] For the unpaired spectrum:

[0618] -When the UE is not provided with tdd-UL-DL-ConfigurationCommon, if the PRACH opportunity in the PRACH slot does not precede the SS / PBCH block in the PRACH slot and starts at least N symbols (where N is an integer or natural number) after the last SS / PBCH block received symbol, then if ChannelAccessMode-r16=semistatic is provided, and if the PRACH opportunity in the PRACH slot does not overlap with a set of consecutive symbols before the start of the next channel occupancy time in which the UE does not perform transmission, then the PRACH opportunity in the PRACH slot may be valid.

[0619] --The candidate SS / PBCH block index of the SS / PBCH block may correspond to the SS / PBCH block index provided by ssb-PositionsInBurst.

[0620] If the UE is provided with tdd-UL-DL-ConfigurationCommon, a PRACH opportunity in a PRACH slot may be valid if at least one of the following conditions is met:

[0621] -- if the PRACH opportunity in the PRACH slot is within a UL symbol; and / or

[0622] -- If a PRACH opportunity in a PRACH slot does not precede an SS / PBCH block in the PRACH slot and starts at least N symbols (where N is an integer or a natural number) after the last DL symbol, or starts at least N symbols (where N is an integer or a natural number) after the last SS / PBCH block received symbol, if ChannelAccessMode-r16=semistatic is provided, and if a PRACH opportunity in a PRACH slot does not overlap with a set of consecutive symbols before the start of the next channel occupancy time in which no transmission is performed.

[0623] --The candidate SS / PBCH block index of the SS / PBCH block may correspond to the SS / PBCH block index provided by ssb-PositionsInBurst.

[0624] Figure 23 is a diagram illustrating exemplary time domain locations for MsgA RACH and MsgA PUSCH according to various embodiments.

[0625] exist Figure 23 In FIG, it is assumed that a UL time slot is allocated every 2.5 ms within a period of 10 ms and a RACH is configured in a subframe with an index of 9. For example, a PO group may be configured with an offset of 2.5 ms and a period of 10 ms.

[0626] According to various embodiments, due to different numbers of valid ROs within a RACH period, two periods (eg, an associated period and an associated mode period) for SSB to RO mapping may be defined.

[0627] According to various embodiments, the SSB to RO association period may be determined by comparing the number of SSBs and the number of valid ROs. Since the number of preambles per SSB is the same, the remaining RACH preambles in the mapping period may not be mapped to SSBs.

[0628] According to various embodiments, for the 2-step RACH procedure, the equality of the number of preambles and PRUs per SSB may be considered to provide preamble-to-PRU mapping.

[0629] According to various embodiments, for preamble to PRU mapping, it may be considered to assign timely closed OFDM symbols for MsgA preamble and MsgAPUSCH to reduce latency.

[0630] According to various embodiments, the preamble to PRU mapping may operate when determining a valid MsgA RO in period A and a valid MsgAPO in period B.

[0631] According to various embodiments, period A may be determined based on the SSB to RACH association period. For example, since the number of valid MsgA ROs is identified within the SSB to RO association period, period A may be equivalent to the SSB to RACH association period.

[0632] According to various embodiments, the mapping rule between RACH preamble and PRU may be defined as follows:

[0633] -0) Verify which POs are available.

[0634] --A) PO in flexible / UL timeslot may be available.

[0635] --B) PO may be available after a gap period of N symbols (where N is an integer or natural number greater than or equal to 0) from the last DL symbol.

[0636] --C) PO that does not conflict with SSB may be available.

[0637] -1) The preamble in the available RO of the RACH slot preceding the available PO can be mapped to the PRU in the available PO.

[0638] -2) The SSB to RO association period may be applied to RACH preamble to PRU mapping.

[0639] --A) The preamble in the available RO in the association period for SSB to RO mapping can be mapped to the PRU in the available PO in the association period.

[0640] -3) If the number of preambles of the CBRA in the available RO in the association period is equal to or greater than the number of PRUs in the available PO in the association period, all preambles or a subset of preambles of the CBRA may be mapped to PRUs in the available PO.

[0641] --A) If a set of ATSSs mapped to RO in an association period for SSB to RO mapping is not completely mapped to PRUs in available POs in the SSB association period, the preamble in the available RO may not be mapped to available PRUs in the available POs.

[0642] --B) The remaining preambles not mapped to PRUs for the 2-step RACH procedure can be used for MsgA preamble-only transmission.

[0643] Additionally / alternatively, according to various embodiments, the mapping rules between RACH preambles and PRUs may be defined as follows:

[0644] -0) Verify which POs are available.

[0645] -1) The preamble in the available RO of the RACH slot preceding the available PO can be mapped to the PRU in the available PO.

[0646] -2) The preamble in the available RO in period A can be mapped to the PRU in the available PO in period B.

[0647] --A) (One-to-one mapping) If the number of preambles of the CBRA in the available RO in period A is the same as the number of PRUs in the available PO in period B, all preambles of the CBRA may be mapped to all PRUs.

[0648] --B) (Many-to-one mapping) If the number of preambles of the CBRA in the available RO in period A is greater than the number of PRUs in the available PO in period B, all preambles of the CBRA may be mapped to all PRUs and / or a subset thereof. When a subset of PRUs is used, the remaining PRUs may not be used for the 2-step RACH procedure.

[0649] --C) (One-to-one mapping with multiple cycles) When the number of preambles of the CBRA in the available RO in period A is less than the number of PRUs in the available PO in period B, all preambles of the CBRA may be mapped to all PRUs and / or a subset thereof. When a subset of PRUs is used, the remaining PRUs may not be used for the 2-step RACH procedure.

[0650] --If a set (or multiple) of ATSSs mapped to RO in the SSB to RO association period are not completely mapped with PRUs in available PO in period B, the preamble in the available RO may not be mapped to the PRUs in the available PO.

[0651] -- The remaining preambles not mapped to PRUs for the 2-step RACH procedure may be used for MsgA-only preamble transmission.

[0652] - In a many-to-one mapping, consecutive PRACH preambles (N consecutive PRACH preamble indices) may be mapped to the same PRU, and then the next consecutive PRACH preamble (N consecutive PRACH preamble indices) may be mapped to the next PRU. That is, each of the N consecutive PRACH preamble indices of a valid PRACH opportunity in a PRACH slot may be mapped to one PO (and its associated DMRS resource). According to various embodiments, the number N of consecutive PRACH preamble indices may be determined based on the number of valid PRACH opportunities and the number of valid POs.

[0653] 3.4. Initial network access and communication process

[0654] According to various embodiments of the present disclosure, the UE may perform a network access procedure to execute the above-mentioned / proposed procedures and / or methods. For example, the UE may receive system information and configuration information required to execute the above-mentioned / proposed procedures and / or methods, and store the received information in a memory. The configuration information required for various embodiments of the present disclosure may be received by higher-layer signaling (e.g., RRC signaling or MAC signaling).

[0655] Figure 24 It is a diagram illustrating the initial network access and subsequent communication processes. In the NR system to which various embodiments of the present disclosure are applicable, physical channels and RSs can be transmitted through beamforming. When beamforming-based signal transmission is supported, beam management can be performed to perform beam alignment between the BS and the UE. In addition, the signals proposed in the various embodiments of the present disclosure can be sent / received through beamforming. In RRC_IDLE mode, beam alignment can be performed based on synchronization signal blocks (SSB or SS / PBCH blocks), and in RRC_CONNECTED mode, beam alignment can be performed based on CSI-RS (in DL) and SRS (in UL). On the contrary, when beamforming-based signal transmission is not supported, beam-related operations can be omitted in the following description.

[0656] Reference Figure 24 , a BS (e.g., an eNB) may periodically transmit an SSB (2702). The SSB includes PSS / SSS / PBCH. The SSB may be transmitted through beam scanning. Subsequently, the BS may transmit remaining minimum system information (RMSI) and other system information (OSI) (2704). The RMSI may include information required for the UE to perform initial access to the BS (e.g., PRACH configuration information). After detecting the SSB, the UE identifies the best SSB. The UE may then transmit a RACH preamble (message 1; Msg1) (2706) in a PRACH resource linked / corresponding to the index (i.e., beam) of the best SSB. The beam direction of the RACH preamble is associated with the PRACH resource. The association between the PRACH resource (and / or RACH preamble) and the SSB (SSB index) may be configured by system information (e.g., RMSI). Subsequently, in the RACH process, the BS may transmit a random access response (RAR) (Msg2) in response to the RACH preamble (2708), the UE may transmit a Msg3 (e.g., RRC connection request) (2710) based on the UL grant included in the RAR, and the BS may transmit a contention resolution message (Msg4) (2712). Msg4 may include RRC connection establishment.

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

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

[0659] Additionally / alternatively, the UE and the BS may perform the above-mentioned / proposed procedures and / or methods as at least a part of the above-mentioned initial access procedure.

[0660] 3.5. Discontinuous Reception (DRX) Operation

[0661] Figure 25 is an exemplary DRX operation according to various embodiments of the present disclosure.

[0662] According to various embodiments of the present disclosure, the UE may perform DRX operation in the aforementioned / proposed procedures and / or methods. When the UE is configured with DRX, the UE may reduce power consumption by discontinuously receiving downlink signals. DRX may be performed in the RRC_IDLE state, the RRC_INACTIVE state, and the RRC_CONNECTED state. In the RRC_IDLE state and the RRC_INACTIVE state, DRX is used to discontinuously receive paging signals.

[0663] RRC_CONNECTEDDRX

[0664] In the RRC_CONNECTED state, DRX is used to discontinuously receive the PDCCH. The DRX in the RRC_CONNECTED state is called RRC_CONNECTED DRX.

[0665] Reference Figure 25 (a), the DRX cycle includes an on-duration and an opportunity for DRX. The DRX cycle defines a time interval in which the on-duration is repeated periodically. The on-duration is a time period during which the UE monitors the PDCCH. When the UE is configured with DRX, the UE performs PDCCH monitoring during the on-duration. When the UE successfully detects the PDCCH during the PDCCH monitoring period, the UE starts an inactivity timer and remains awake. On the other hand, if the UE does not detect the PDCCH during the PDCCH monitoring period, the UE enters a sleep state after the on-duration expires. Therefore, when DRX is configured, PDCCH monitoring / reception can be performed discontinuously in the time domain while performing the aforementioned / proposed processes and / or methods. For example, when DRX is configured, the PDCCH reception opportunity (e.g., a time slot including a PDCCH search space) can be configured as discontinuous according to the DRX configuration. In contrast, when DRX is not configured, PDCCH monitoring / reception can be performed continuously in the time domain. For example, when DRX is not configured, PDCCH reception opportunities (eg, time slots including a PDCCH search space) may be configured to be continuous. Regardless of whether DRX is configured, PDCCH monitoring may not be allowed in a time period corresponding to a measurement gap.

[0666] Table 18 shows the UE procedures related to DRX (in the RRC_CONNECTED state). Referring to Table 18, DRX configuration information can be received by higher layer (RRC) signaling, and DRX on / off can be controlled by DRX commands at the MAC layer. Once DRX is configured, the UE can discontinuously perform PDCCH monitoring while performing the procedures and / or methods described / proposed in various embodiments.

[0667] [Table 18]

[0668]

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

[0670] -drx-OnDurationTimer value: defines the duration of the start period of the DRX cycle.

[0671] - Value of drx-InactivityTimer: defines the duration of the period in which the UE is awakened after a PDCCH opportunity in which a PDCCH indicating initial UL or DL ​​data has been detected.

[0672] - Value of drx-HARQ-RTT-TimerDL: defines the duration of the maximum time period until a DL retransmission is received after a DL initial transmission is received.

[0673] - Value of drx-HARQ-RTT-TimerDL: defines the duration of the maximum time period until a grant for UL retransmission is received after receiving a grant for UL initial transmission.

[0674] -drx-LongCycleStartOffset: defines the duration and start time of the DRX cycle.

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

[0676] When any of drx-OnDurationTimer, drx-InactivityTimer, drx-HARQ-RTT-TimerDL and drx-HARQ-RTT-TimerDL is running, the UE performs PDCCH monitoring in each PDCCH opportunity and remains in the awake state.

[0677] RRC_IDLEDRX

[0678] In the RRC_IDLE state and the RRC_INACTIVE state, DRX is used to discontinuously receive a paging signal. For convenience, DRX performed in the RRC_IDLE (or RRC_INACTIVE) state is referred to as RRC_IDLE DRX.

[0679] Therefore, when DRX is configured, in the aforementioned / proposed procedures and / or methods, PDCCH monitoring / reception may be performed discontinuously in the time domain.

[0680] Reference Figure 25(b) DRX may be configured for discontinuous reception of paging signals. The UE may receive DRX configuration information from the BS through higher layer (e.g., RRC) signaling. The DRX configuration information may include a DRX cycle, a DRX offset, configuration information for a DRX timer, and the like. The UE repeats the on-duration and the sleep-duration according to the DRX cycle. The UE may operate in an awake mode during the on-duration and in a sleep mode during the sleep-duration. In awake mode, the UE may monitor a paging occasion (PO) to receive a paging message. A PO means a time resource / interval (e.g., a subframe or time slot) in which the UE expects to receive a paging message. PO monitoring includes monitoring a PDCCH (MPDCCH or NPDCCH) scrambled with a P-RNTI (hereinafter referred to as a paging PDCCH) in the PO. The paging message may be included in a paging PDCCH or in a PDSCH scheduled by the paging PDCCH. One or more POs may be included in a paging frame (PF), and the PF may be periodically configured based on the UE ID. The PF may correspond to one radio frame, and the UE ID may be determined based on the International Mobile Subscriber Identity (IMSI) of the UE. When DRX is configured, the UE monitors only one PO per DRX cycle. When the UE receives a paging message indicating a change in its ID and / or system information in the PO, the UE may perform a RACH procedure to initialize (or reconfigure) a connection with the BS, or receive (or obtain) new system information from the BS. Therefore, PO monitoring may be performed discontinuously in the time domain to perform a RACH procedure for connecting to the BS or to receive (or obtain) new system information from the BS in the aforementioned process and / or method.

[0681] Those skilled in the art will appreciate that the above-mentioned initial access process and / or DRX operation may be combined with the details described in Sections 1 to 3 above to form other implementations.

[0682] Figure 26 is a diagram schematically illustrating a method of operating a UE and a BS according to various embodiments.

[0683] Figure 27 is a flowchart illustrating a method of operating a UE according to various embodiments.

[0684] Figure 28 is a flowchart illustrating a method of operating a BS according to various embodiments.

[0685] Reference Figures 26 to 28 In operations 2601 and 2701 according to various embodiments, the UE may obtain / generate MsgA related to the RACH process. According to various embodiments, the MsgA may include a PRACH preamble and a PUSCH.

[0686] In operations 2603 , 2703 , and 2803 according to various embodiments, the UE may transmit MsgA, and the BS may receive the MsgA.

[0687] In operations 2605 and 2805 according to various embodiments, the BS may obtain a PRACH preamble and a PUSCH based on MsgA.

[0688] In operations 2607 , 2707 , and 2807 according to various embodiments, the BS transmits MsgB in response to MsgA, and the UE may receive MsgB.

[0689] According to various embodiments, the PUSCH may be transmitted / received based on reception information / transmission information related to the PUSCH configuration for MsgA.

[0690] According to various embodiments, based on the information related to PUSCH configuration including information related to indication of a CDM group for a DMRS of a PUSCH, the CDM group may be configured as a group indicated by the information related to indication of the CDM group, of two predetermined groups.

[0691] According to various embodiments, communication may be performed after the RACH procedure.

[0692] According to various embodiments, the PDSCH may be transmitted / received based on communication.

[0693] According to various embodiments, based on the DRX configuration, the PDCCH for the PDSCH may be monitored / transmitted during the DRX-related On-Duration.

[0694] Since the examples of the above-mentioned proposed methods can also be included in one of the implementation methods of various embodiments of the present disclosure, it is obvious that these examples are considered to be a proposed method. Although the above-mentioned methods can be implemented independently, the proposed method can be implemented in a combined (aggregated) form of a part of the proposed method. The rule can be defined so that the BS notifies the UE of information on whether to apply the proposed method (or information on the rules of the proposed method) through a predefined signal (e.g., a physical layer signal or a higher layer signal).

[0695] 4. Exemplary Configurations of Apparatuses for Implementing Various Embodiments of the Disclosure

[0696] 4.1. Exemplary Configurations of Apparatuses to Which Various Embodiments of the Present Disclosure Are Applied

[0697] Figure 29 It is a diagram illustrating a device for implementing various embodiments of the present disclosure.

[0698] Figure 29The apparatus shown may be a UE and / or BS (e.g., eNB or gNB) adapted to perform the above-described mechanisms or any apparatus that performs the same operations.

[0699] Reference Figure 29 The device may include a digital signal processor (DSP) / microprocessor 210 and a radio frequency (RF) module (transceiver) 235. The DSP / microprocessor 210 is electrically coupled to and controls the transceiver 235. Depending on the designer's choice, the device may also include a power management module 205, a battery 255, a display 215, a keypad 220, a SIM card 225, a memory device 230, an antenna 240, a speaker 245, and an input device 250.

[0700] Specifically, Figure 29 The UE may include a receiver 235 configured to receive a request message from a network and a transmitter 235 configured to send timing transmission / reception timing information to the network. These receivers and transmitters may form a transceiver 235. The UE may further include a processor 210 coupled to the transceiver 235.

[0701] also, Figure 29 A network device including a transmitter 235 configured to transmit a request message to a UE and a receiver 235 configured to receive transmission / reception timing information from the UE may be exemplified. These receiver and transmitter may form a transceiver 235. The network may further include a processor 210 coupled to the transceiver 235. The processor 210 may calculate a delay based on the transmission / reception timing information.

[0702] The processors included in the UE (or a communication device included in the UE) and the BS (or a communication device included in the BS) according to various embodiments of the present disclosure may operate as follows while controlling the memory.

[0703] According to various embodiments of the present disclosure, a UE or a BS may include at least one transceiver, at least one memory, and at least one processor coupled to the at least one transceiver and the at least one memory. The at least one memory may store instructions for causing the at least one processor to perform the following operations.

[0704] The communication device included in the UE or BS may be configured to include at least one processor and at least one memory. The communication device may be configured to include at least one transceiver, or may be configured not to include at least one transceiver but to be connected to at least one transceiver.

[0705] According to various embodiments, at least one processor included in the UE (or at least one processor of the communication device included in the UE) may obtain MsgA related to the RACH process.

[0706] According to various embodiments, at least one processor included in the UE may send the MsgA.

[0707] According to various embodiments, at least one processor in the UE may receive MsgB related to a RACH procedure in response to MsgA.

[0708] According to various embodiments, at least one processor included in the UE may include the PRACH preamble and the PUSCH in the MsgA.

[0709] According to various embodiments, the PUSCH may be transmitted based on received information related to the PUSCH configuration for MsgA.

[0710] According to various embodiments, based on the information related to PUSCH configuration including information related to indication of a CDM group for a DMRS of a PUSCH, the CDM group may be configured as a group indicated by the information related to indication of the CDM group, of two predetermined groups.

[0711] According to various embodiments, communication may be performed after the RACH procedure.

[0712] According to various embodiments, the PDSCH may be received based on the communication.

[0713] According to various embodiments, based on the DRX configuration, the PDCCH for the PDSCH may be monitored during the DRX-related On-Duration.

[0714] According to various embodiments, at least one processor included in the BS (or at least one processor of a communication device included in the BS) may receive MsgA related to the RACH procedure.

[0715] According to various embodiments, at least one processor included in the BS may obtain a PRACH preamble and a PUSCH based on MsgA.

[0716] According to various embodiments, at least one processor included in the BS may transmit MsgB related to the RACH procedure in response to MsgA.

[0717] According to various embodiments, the PUSCH may be obtained based on the transmitted information related to the PUSCH configuration for MsgA.

[0718] According to various embodiments, based on the information related to PUSCH configuration including information related to indication of a CDM group for a DMRS of a PUSCH, the CDM group may be configured as a group indicated by the information related to indication of the CDM group, of two predetermined groups.

[0719] According to various embodiments, communication may be performed after the RACH procedure.

[0720] According to various embodiments, the PDSCH may be transmitted based on the communication.

[0721] According to various embodiments, based on the DRX configuration, the PDCCH for the PDSCH may be transmitted during the DRX-related On-Duration.

[0722] More specific operations of the processor included in the BS and / or UE according to various embodiments of the present disclosure may be described and performed based on the above Sections 1 to 3.

[0723] Unless otherwise contradictory, various embodiments of the present disclosure may be implemented in combination. For example, unless otherwise contradictory, a BS and / or UE according to various embodiments of the present disclosure may perform operations in combination with the embodiments of Sections 1 to 3 above.

[0724] 4.2. Examples of Communication Systems to Which Various Embodiments of the Present Disclosure Are Applied

[0725] In this specification, various embodiments of the present disclosure are described primarily with respect to data transmission and reception between a base station and a user equipment terminal in a wireless communication system. However, the various embodiments of the present disclosure are not limited thereto. For example, the various embodiments of the present disclosure may also involve the following technical configurations.

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

[0727] Hereinafter, a more detailed description will be given with reference to the accompanying drawings. In the following drawings / descriptions, unless otherwise described, the same reference numerals may represent the same or corresponding hardware blocks, software blocks or functional blocks.

[0728] Figure 30 An exemplary communication system to which various embodiments of the present disclosure are applied is illustrated.

[0729] Reference Figure 30, the communication system 1 applied to various embodiments of the present disclosure includes a wireless device, a base station (BS) and a network. Herein, the wireless device refers to a device that performs communication using a radio access technology (RAT) (for example, 5G New RAT (NR) or Long Term Evolution (LTE)), and may be referred to as a communication / radio / 5G device. The wireless device may include (but is not limited to) a robot 100a, vehicles 100b-1 and 100b-2, an extended reality (XR) device 100c, a handheld device 100d, a home appliance 100e, an Internet of Things (IoT) device 100f, and an artificial intelligence (AI) device / server 400. For example, a vehicle may include a vehicle with a wireless communication function, an autonomous driving vehicle, and a vehicle capable of performing communication between vehicles. Herein, a vehicle may include an unmanned aerial vehicle (UAV) (for example, a drone). XR devices may include augmented reality (AR) / virtual reality (VR) / mixed reality (MR) devices and may be implemented in the form of head-mounted devices (HMDs), head-up displays (HUDs) installed in vehicles, televisions, smartphones, computers, wearable devices, home appliance devices, digital signage, vehicles, robots, and the like. Handheld devices may include smartphones, smart pads, wearable devices (e.g., smart watches or smart glasses), and computers (e.g., notebooks). Home appliances may include TVs, refrigerators, and washing machines. IoT devices may include sensors and smart meters. For example, a BS and a network may be implemented as wireless devices, and a specific wireless device 200a may operate as a BS / network node relative to other wireless devices.

[0730] Wireless devices 100a to 100f can connect to network 300 via BS 200. AI technology can be applied to wireless devices 100a to 100f, and wireless devices 100a to 100f can connect to AI server 400 via network 300. Network 300 can be configured using a 3G network, a 4G (e.g., LTE) network, or a 5G (e.g., NR) network. Although wireless devices 100a to 100f can communicate with each other via BS 200 / network 300, wireless devices 100a to 100f can perform direct communication (e.g., sidelink communication) with each other without going through the BS / network. For example, vehicles 100b-1 and 100b-2 can perform direct communication (e.g., vehicle-to-vehicle (V2V) / vehicle-to-everything (V2X) communication). IoT devices (e.g., sensors) can perform direct communication with other IoT devices (e.g., sensors) or other wireless devices 100a to 100f.

[0731] Wireless communication / connections 150a, 150b, or 150c may be established between wireless devices 100a to 100f / BS 200 or BS 200 / BS 200. Here, wireless communication / connections may be established via various RATs (e.g., 5G NR), such as uplink / downlink communication 150a, sidelink communication 150b (or D2D communication), or inter-BS communication (e.g., relay, integrated access backhaul (IAB)). The wireless device and the BS / wireless device may transmit / receive radio signals to / from each other via the wireless communication / connections 150a and 150b. For example, the wireless communication / connections 150a and 150b may transmit / receive signals via various physical channels. To this end, various configuration information configuration processes, various signal processing processes (e.g., channel coding / decoding, modulation / demodulation, and resource mapping / demapping), and at least a portion of the resource allocation process for transmitting / receiving radio signals may be performed based on various proposals of the present disclosure.

[0732] 4.2.1 Examples of Wireless Devices to Which Various Embodiments of the Present Disclosure Are Applied

[0733] Figure 31 An exemplary wireless device to which various embodiments of the present disclosure are applicable is illustrated.

[0734] Reference Figure 31 , the first wireless device 100 and the second wireless device 200 can transmit radio signals through various RATs (e.g., LTE and NR). Herein, {the first wireless device 100 and the second wireless device 200} may correspond to Figure 30 {wireless device 100x and BS 200} and / or {wireless device 100x and wireless device 100x}.

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

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

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

[0738] The one or more processors 102 and 202 may be referred to as controllers, microcontrollers, microprocessors, or microcomputers. The one or more processors 102 and 202 may be implemented by hardware, firmware, software, or a combination thereof. As an 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 102 and 202. The descriptions, functions, processes, proposals, methods, and / or operational flowcharts disclosed in this document may be implemented using firmware or software, and the firmware or software may be configured to include modules, processes, or functions. The firmware or software configured to execute the descriptions, functions, processes, proposals, methods, and / or operational flowcharts disclosed in this document may be included in the one or more processors 102 and 202 or stored in the one or more memories 104 and 204 to be driven by the one or more processors 102 and 202. The descriptions, functions, processes, proposals, methods and / or operational flow charts disclosed in this document may be implemented in the form of codes, commands and / or command sets using firmware or software.

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

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

[0741] According to various embodiments of the present disclosure, one or more memories (e.g., 104 or 204) may store instructions or programs that, when executed, cause one or more processors operatively connected to the one or more memories to perform operations according to various embodiments or implementations of the present disclosure.

[0742] According to various embodiments of the present disclosure, a computer-readable storage medium may store one or more instructions or computer programs, which, when executed by one or more processors, cause the one or more processors to perform operations according to various embodiments or implementations of the present disclosure.

[0743] According to various embodiments of the present disclosure, a processing device or apparatus may include one or more processors and one or more computer memories connected to the one or more processors. The one or more computer memories may store instructions or programs that, when executed, cause one or more processors operatively coupled to the one or more memories to perform operations according to various embodiments or implementations of the present disclosure.

[0744] 4.2.2. Examples of Using Wireless Devices to Which Various Embodiments of the Present Disclosure Are Applied

[0745] Figure 32 Other exemplary wireless devices to which various embodiments of the present disclosure are applied are illustrated. The wireless device may be configured to perform various functions according to the use case / service (see Figure 30 ) are implemented in various forms.

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

[0747] The additional components 140 may be configured differently depending on the type of wireless device. For example, the additional components 140 may include at least one of a power supply unit / battery, an input / output (I / O) unit, a drive unit, and a computing unit. The wireless device may be configured in the following manner: Figure 30 100a), vehicles ( Figure 30 100b-1 and 100b-2), XR devices ( Figure 30 100c), handheld device ( Figure 30 100d), household appliances ( Figure 30 100e), IoT devices ( Figure 30 100f), digital broadcasting terminal, holographic device, public safety device, MTC device, medical device, fintech device (or financial device), security device, climate / environmental device, AI server / device ( Figure 30 400), BS( Figure 30 200), a network node, etc. The wireless device can be used in a mobile or fixed location depending on the use case / service.

[0748] exist Figure 32 In the wireless devices 100 and 200, the various elements, components, units / portions, and / or modules may all be connected to each other via a wired interface, or at least a portion thereof may be wirelessly connected via the communication unit 110. For example, in each of the wireless devices 100 and 200, the control unit 120 and the communication unit 110 may be wired, and the control unit 120 and the first unit (e.g., 130 and 140) may be wirelessly connected via the communication unit 110. The various elements, components, units / portions, and / or modules within the wireless devices 100 and 200 may also include one or more elements. For example, the control unit 120 may be configured by a collection of one or more processors. As an example, the control unit 120 may be configured by a collection of a communication control processor, an application processor, an electronic control unit (ECU), a graphics processing unit, and a memory control processor. As another example, the memory unit 130 may be configured by a random access memory (RAM), a dynamic RAM (DRAM), a read-only memory (ROM), a flash memory, a volatile memory, a non-volatile memory, and / or a combination thereof.

[0749] Hereinafter, the implementation will be described in detail with reference to the accompanying drawings. Figure 32 .

[0750] 4.2.3. Examples of Portable Devices to Which Various Embodiments of the Present Disclosure Are Applied

[0751] Figure 33 The present invention illustrates an exemplary portable device applicable to various embodiments of the present disclosure. The portable device may be any of a smartphone, a smartpad, a wearable device (e.g., a smartwatch or smart glasses), and a portable computer (e.g., a laptop computer). The portable device may also be referred to as a mobile station (MS), a user terminal (UT), a mobile subscriber station (MSS), a subscriber station (SS), an advanced mobile station (AMS), or a wireless terminal (WT).

[0752] Reference Figure 33, the handheld device 100 may include an antenna unit 108, a communication unit 110, a control unit 120, a memory unit 130, a power supply unit 140a, an interface unit 140b, and an I / O unit 140c. The antenna unit 108 may be configured as a part of the communication unit 110. Blocks 110 to 130 / 140a to 140c correspond to Figure 32 Blocks 110 to 130 / 140.

[0753] The communication unit 110 can send and receive signals (e.g., data and control signals) to and from other wireless devices or a base station. The control unit 120 can perform various operations by controlling the components of the handheld device 100. The control unit 120 may include an application processor (AP). The memory unit 130 can store data / parameters / programs / codes / commands required to operate the handheld device 100. The memory unit 130 can store input / output data / information. The power supply unit 140a can supply power to the handheld device 100 and includes wired / wireless charging circuits, a battery, etc. The interface unit 140b can support connection between the handheld device 100 and other external devices. The interface unit 140b may include various ports (e.g., an audio I / O port and a video I / O port) for connecting to external devices. The I / O unit 140c can input or output video information / signals, audio information / signals, data, and / or information input by the user. The I / O unit 140c may include a camera, a microphone, a user input unit, a display unit 140d, a speaker, and / or a haptic module.

[0754] As an example, in the case of data communication, the I / O unit 140c can obtain information / signals (e.g., touch, text, voice, image, or video) input by the user, and the obtained information / signals can be stored in the memory unit 130. The communication unit 110 can convert the information / signals stored in the memory into radio signals and directly transmit the converted radio signals to other wireless devices or BSs. The communication unit 110 can receive radio signals from other wireless devices or BSs and then restore the received radio signals to the original information / signals. The restored information / signals can be stored in the memory unit 130 and can be output as various types (e.g., text, voice, image, video, or tactile) through the I / O unit 140c.

[0755] 4.2.4. Examples of Vehicles or Autonomous Driving Vehicles to Which Various Embodiments of the Disclosure Are Applied

[0756] Figure 34 An exemplary vehicle or autonomous driving vehicle to which various embodiments of the present disclosure are applied is illustrated. 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, etc.

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

[0758] The communication unit 110 can send and receive signals (e.g., data and control signals) to and from external devices such as other vehicles, base stations (e.g., gNBs and roadside units), and servers. The control unit 120 can perform various operations by controlling components of the vehicle or autonomous vehicle 100. The control unit 120 may include an electronic control unit (ECU). The drive unit 140a can enable the vehicle or autonomous vehicle 100 to travel on a road. The drive unit 140a may include an engine, a motor, a power system, wheels, brakes, a steering system, etc. The power supply unit 140b can supply power to the vehicle or autonomous vehicle 100 and may include wired / wireless charging circuits, a battery, etc. The sensor unit 140c can acquire vehicle status, surrounding environment information, user information, etc. The sensor unit 140 c 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 location module, a vehicle forward / backward sensor, a battery sensor, a fuel sensor, a tire sensor, a steering sensor, a temperature sensor, a depth sensor, an ultrasonic sensor, a lighting sensor, a pedal position sensor, etc. The autonomous driving unit 140 d may implement a technology for maintaining a lane in which the vehicle is traveling, a technology for automatically adjusting the speed (e.g., adaptive cruise control), a technology for autonomously traveling along a determined path, a technology for traveling by automatically setting a path if a destination is set, etc.

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

[0760] In summary, various embodiments of the present disclosure may be implemented through specific devices and / or UEs.

[0761] For example, the specific device can be any one of a BS, a network node, a sending UE, a receiving UE, a wireless device, a wireless communication device, a vehicle, a vehicle equipped with an autonomous driving function, an unmanned vehicle (UAV), an artificial intelligence (AI) module, a robot, an augmented reality (AR) device, a virtual reality (VR) device, and other devices.

[0762] For example, the UE may be any one of a personal digital assistant (PDA), a cellular phone, a personal communications service (PCS) phone, a global system for mobile (GSM) phone, a wideband CDMA (WCDMA) phone, a mobile broadband system (MBS) phone, a smart phone, and a multi-mode multi-band (MM-MB) terminal.

[0763] A smartphone is a terminal that combines the advantages of both a mobile communication terminal and a PDA by integrating data communication functions (e.g., scheduling, fax sending and receiving, and Internet connection) into a mobile communication terminal. Furthermore, an MM-MB terminal is a terminal with a built-in multi-modem chip, enabling it to operate on all portable Internet systems and other mobile communication systems (e.g., CDMA 2000, WCDMA, etc.).

[0764] Alternatively, the UE may be any of a laptop PC, a handheld PC, a tablet PC, an ultrabook, a slate PC, a digital broadcast terminal, a portable multimedia player (PMP), a navigator, and a wearable device (e.g., a smartwatch, smart glasses, and a head-mounted display (HMD)). For example, a UAV may be an unmanned vehicle that flies under the control of a wireless control signal. For example, an HMD may be a display device worn on the head. For example, an HMD may be used to implement AR or VR.

[0765] The wireless communication technology used to implement the various embodiments of the present disclosure may include narrowband IoT for low-power communication as well as LTE, NR and 6G. In this case, for example, NB-IoT technology may be an example of a low-power wide area network (LPWAN) technology and may be implemented in standards such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the above names. Additionally or alternatively, the wireless communication technology implemented in the wireless device according to the various embodiments of the present disclosure may perform communication based on LTE-M technology. In this case, for example, LTE-M technology may be an example of an LPWAN technology and may be referred to as various terms such as enhanced machine type communication (eMTC). For example, LTE-M technology may be implemented as at least one of various standards such as 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (non-bandwidth limited), 5) LTE-MTC, 6) LTE machine type communication and / or 7) LTE M, and may not be limited to the aforementioned terms. Additionally or alternatively, the wireless communication technology implemented in the wireless device according to various embodiments of the present disclosure may include at least one of ZigBee, Bluetooth, or a low-power wide area network (LPWAN) considering low-power communication, and is not limited to the aforementioned terms. For example, ZigBee technology can generate a personal area network (PAN) related to small / low-power digital communication based on various standards such as IEEE 802.15.4, and can be referred to by various terms.

[0766] Various embodiments of the present disclosure may be implemented in various ways. For example, various embodiments of the present disclosure may be implemented in hardware, firmware, software, or a combination thereof.

[0767] In hardware configuration, the method according to the exemplary embodiment of the present disclosure can be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, etc.

[0768] In a firmware or software configuration, the methods according to various embodiments of the present disclosure may be implemented in the form of modules, procedures, functions, etc. that perform the above-described functions or operations. The software code may be stored in the memory 50 or 150 and executed by the processor 40 or 140. The memory may be located inside or outside the processor and may send and receive data to and from the processor via various known means.

[0769] Those skilled in the art will understand that, without departing from the spirit and basic features of the various embodiments of the present disclosure, the various embodiments of the present disclosure may be implemented in other specific ways other than those set forth herein. Therefore, the above-mentioned embodiments are to be interpreted as being illustrative in all respects, and not restrictive. The scope of the present disclosure should be determined by the appended claims and their legal equivalents (rather than the above description), and all changes that fall within the meaning and equivalent scope of the appended claims are intended to be covered therein. It is obvious to those skilled in the art that claims that are not explicitly referenced to each other in the appended claims may be presented as embodiments of the present disclosure in combination, or may be included as new claims by subsequent amendments after submitting the application.

[0770] Industrial Applicability

[0771] The various embodiments of the present disclosure are applicable to various wireless access systems including 3GPP systems and / or 3GPP2 systems. In addition to these wireless access systems, the various embodiments of the present disclosure are applicable to all technical fields to which wireless access systems can be applied. In addition, the proposed method can also be applied to mmWave communications using ultra-high frequency bands.

Claims

1. A method performed by a user equipment (UE) in a wireless communication system, the method comprising the following steps: receiving configuration information related to a message A, wherein the message A includes a physical random access channel (PRACH) preamble and a physical uplink shared channel (PUSCH); Perform a 2-step random access procedure; After performing the two-step random access procedure, monitoring a physical downlink control channel (PDCCH) during an on-duration based on the configured discontinuous reception (DRX); and receiving a physical downlink shared channel PDSCH based on the PDCCH, The steps of performing the two-step random access process include the following steps: Sending the message A based on the configuration information; and In response to the message A, receiving a message B including a random access response RAR, wherein a scrambling sequence for scrambling the PUSCH is initialized based on a random access radio network temporary identifier RA-RNTI, a random access preamble identifier RAPID of the PRACH preamble, and a specific value; The specific value is configured by high-level parameters. The configuration information includes demodulation reference signal (DMRS) configuration information for the PUSCH. Wherein, based on the code division multiplexing (CDM) group information included in the DMRS configuration information for the PUSCH, at least one CDM group for the DMRS is configured in two pre-configured groups.

2. The method according to claim 1, wherein The number of ports used for the DMRS is determined in the set of {1, 2, 4}.

3. The method according to claim 1, wherein Based on the transform precoding for the PUSCH being disabled, obtaining two different identifiers ID associated with a sequence for identifying an initialization of a pseudo-random sequence generator associated with sequence generation of the DMRS based on two different higher layer parameters, respectively; and The scrambling ID SCID associated with the index identifying the two different IDs is determined based on the PRACH preamble code.

4. The method according to claim 3, wherein: Based on the transform precoding being enabled, an ID associated with identifying the sequence for the initialization of the pseudo-random sequence generator is obtained based on higher layer parameters.

5. The method according to claim 3, wherein: The PRACH preamble is obtained from a plurality of PRACH preambles, and The SCID is determined based on a mapping between a plurality of preamble codes and a PUSCH opportunity for sending the PUSCH.

6. An apparatus configured to operate in a wireless communication system, the apparatus comprising: Memory; as well as at least one processor connected to the memory, Wherein, the at least one processor is configured to: receiving configuration information related to a message A, wherein the message A includes a physical random access channel (PRACH) preamble and a physical uplink shared channel (PUSCH); Perform a 2-step random access procedure; After performing the two-step random access procedure, monitoring a physical downlink control channel (PDCCH) during an on-duration based on the configured discontinuous reception (DRX); and receiving a physical downlink shared channel PDSCH based on the PDCCH, The steps of performing the two-step random access process include the following steps: Sending the message A based on the configuration information; and In response to the message A, receiving a message B including a random access response RAR, The scrambling sequence for scrambling the PUSCH is initialized based on a random access radio network temporary identifier RA-RNTI, a random access preamble identifier RAPID of the PRACH preamble, and a specific value. The specific value is configured by high-level parameters. The configuration information includes demodulation reference signal (DMRS) configuration information for the PUSCH. Wherein, based on the code division multiplexing (CDM) group information included in the DMRS configuration information for the PUSCH, at least one CDM group for the DMRS is configured in two pre-configured groups.

7. The device according to claim 6, wherein The number of ports used for the DMRS is determined in the set of {1, 2, 4}.

8. The device according to claim 6, wherein Based on the transform precoding for the PUSCH being disabled, obtaining two different identifiers ID associated with a sequence for identifying an initialization of a pseudo-random sequence generator associated with sequence generation of the DMRS based on two different higher layer parameters, respectively; and The scrambling ID SCID associated with the index identifying the two different IDs is determined based on the PRACH preamble code.

9. The device according to claim 6, wherein The device communicates with at least one of a mobile terminal, a network, or an autonomous driving vehicle other than a vehicle including the device.

10. A method performed by a base station (BS) in a wireless communication system, the method comprising the following steps: Sending configuration information related to message A, wherein message A includes a physical random access channel PRACH preamble and a physical uplink shared channel PUSCH; Perform a 2-step random access procedure; After performing the two-step random access procedure, transmitting a physical downlink control channel (PDCCH) in an on-duration associated with discontinuous reception (DRX); and Sending a physical downlink shared channel PDSCH based on the PDCCH, The steps of performing the two-step random access process include the following steps: receiving the message A based on the configuration information; and In response to the message A, a message B including a random access response RAR is sent, The scrambling sequence for scrambling the PUSCH is initialized based on a random access radio network temporary identifier RA-RNTI, a random access preamble identifier RAPID of the PRACH preamble, and a specific value. The specific value is configured by high-level parameters. The configuration information includes demodulation reference signal (DMRS) configuration information for the PUSCH. Wherein, based on the code division multiplexing (CDM) group information included in the DMRS configuration information for the PUSCH, at least one CDM group for the DMRS is configured in two pre-configured groups.

11. An apparatus configured to operate in a wireless communication system, the apparatus comprising: Memory; as well as at least one processor connected to the memory, Wherein, the at least one processor is configured to: Sending configuration information related to message A, wherein message A includes a physical random access channel PRACH preamble and a physical uplink shared channel PUSCH; Perform a 2-step random access procedure; After performing the two-step random access procedure, transmitting a physical downlink control channel (PDCCH) in an on-duration associated with discontinuous reception (DRX); and Sending a physical downlink shared channel PDSCH based on the PDCCH, The steps of performing the two-step random access process include the following steps: receiving the message A based on the configuration information; and In response to the message A, a message B including a random access response RAR is sent, The scrambling sequence for scrambling the PUSCH is initialized based on a random access radio network temporary identifier RA-RNTI, a random access preamble identifier RAPID of the PRACH preamble, and a specific value. The specific value is configured by high-level parameters. The configuration information includes demodulation reference signal (DMRS) configuration information for the PUSCH. Wherein, based on the code division multiplexing (CDM) group information included in the DMRS configuration information for the PUSCH, at least one CDM group for the DMRS is configured in two pre-configured groups.

12. An apparatus configured to operate in a wireless communication system, the apparatus comprising: at least one processor; as well as At least one memory configured to store one or more instructions for causing the at least one processor to perform a method comprising the steps of: receiving configuration information related to a message A, wherein the message A includes a physical random access channel (PRACH) preamble and a physical uplink shared channel (PUSCH); Perform a 2-step random access procedure; After performing the two-step random access procedure, monitoring a physical downlink control channel (PDCCH) during an on-duration based on the configured discontinuous reception (DRX); and receiving a physical downlink shared channel PDSCH based on the PDCCH, The steps of performing the two-step random access process include the following steps: Sending the message A based on the configuration information; and In response to the message A, receiving a message B including a random access response RAR, The scrambling sequence for scrambling the PUSCH is initialized based on a random access radio network temporary identifier RA-RNTI, a random access preamble identifier RAPID of the PRACH preamble, and a specific value. The specific value is configured by high-level parameters. The configuration information includes demodulation reference signal (DMRS) configuration information for the PUSCH. Wherein, based on the code division multiplexing (CDM) group information included in the DMRS configuration information for the PUSCH, at least one CDM group for the DMRS is configured in two pre-configured groups.

13. A processor-readable medium configured to store one or more instructions for causing at least one processor to perform a method comprising the steps of: receiving configuration information related to a message A, wherein the message A includes a physical random access channel (PRACH) preamble and a physical uplink shared channel (PUSCH); Perform a 2-step random access procedure; After performing the two-step random access procedure, monitoring a physical downlink control channel (PDCCH) during an on-duration based on the configured discontinuous reception (DRX); and receiving a physical downlink shared channel PDSCH based on the PDCCH, The steps of performing the two-step random access process include the following steps: Sending the message A based on the configuration information; and In response to the message A, receiving a message B including a random access response RAR, The scrambling sequence for scrambling the PUSCH is initialized based on a random access radio network temporary identifier RA-RNTI, a random access preamble identifier RAPID of the PRACH preamble, and a specific value. The specific value is configured by high-level parameters. The configuration information includes demodulation reference signal (DMRS) configuration information for the PUSCH. Wherein, based on the code division multiplexing (CDM) group information included in the DMRS configuration information for the PUSCH, at least one CDM group for the DMRS is configured in two pre-configured groups.

Images