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

Abstract

The present disclosure relates to a method performed by a terminal in a wireless communication system and a device supporting the method, and more specifically, to a method including the steps of obtaining a message A and sending the message A, the message A including a physical uplink shared channel (PUSCH) and a physical random access channel (PRACH) preamble, wherein the PUSCH is sent based on information related to the PUSCH configuration for the message A being received, and based on the information related to the PUSCH configuration including information related to an instruction of a code division multiplexing (CDM) group for a demodulation reference signal (DM-RS) for the PUSCH, the CDM group is set to a group indicated by information related to an indication of the CDM group among two preset groups. The present disclosure also relates to a device supporting the same.

Description

Technical Field

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

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

[0003] Technical issues

[0004] 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 two-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 message A physical uplink shared channel (PUSCH) demodulation reference signal (DMRS) in a wireless communication system and an apparatus for supporting the method.

[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 appreciate that the purposes that can be achieved by various embodiments of the present disclosure are not limited to those specifically described above, and based on the following detailed description, the above and other purposes that can be achieved by various embodiments of the present disclosure will be more clearly understood.

[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: obtaining a message A including a physical random access channel (PRACH) preamble and a physical uplink shared channel (PUSCH); and sending the message A.

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

[0014] According to various embodiments, 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 may be configured as a group indicated by the information related to the indication of the CDM group in two predetermined groups.

[0015] 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.

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

[0017] According to various embodiments, based on that transform precoding for PUSCH is disabled: two different identifiers (IDs) can be obtained based on two different higher layer parameters, respectively, and the two different identifiers (IDs) are related to identifying a sequence for initializing a pseudo-random sequence generator associated with sequence generation of DMRS.

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

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

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

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

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

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

[0024] According to various embodiments, the at least one processor may be configured to: obtain message A including a PRACH preamble and a PUSCH; and send message A.

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

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

[0027] 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.

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

[0029] According to various embodiments, based on that transform precoding for PUSCH is disabled: two different identifiers (IDs) can be obtained based on two different higher layer parameters, respectively, and the two different identifiers (IDs) are related to identifying a sequence for initializing a pseudo-random sequence generator associated with sequence generation of DMRS.

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

[0031] 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.

[0032] According to various embodiments, a method performed by a Base Station (BS) in a wireless communication system may be provided.

[0033] According to various embodiments, the method may include: receiving message A; and obtaining a PRACH preamble and a PUSCH based on message A.

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

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

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

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

[0038] According to various embodiments, the at least one processor may be configured to: receive message A; and obtain a PRACH preamble and a PUSCH based on message A.

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

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

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

[0042] According to various embodiments, the apparatus may include: at least one processor; obtaining message A including a PRACH preamble and a PUSCH; and sending message A.

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

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

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

[0046] According to various embodiments, the method may include: obtaining a message A including a PRACH preamble and a PUSCH; and sending the message A.

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

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

[0049] Those skilled in the art will understand that the objectives that can be achieved by the present disclosure are not limited to what has been 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.

[0050] Beneficial Effects

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

[0052] According to various embodiments, message A physical uplink shared channel (PUSCH) demodulation reference signal (DMRS) resources (e.g., DMRS port / sequence, etc.) may be efficiently used.

[0053] According to various embodiments, the preamble may be effectively used.

[0054] Those skilled in the art will appreciate that the effects that can be achieved by the various embodiments of the present disclosure are not limited to those described above, and other advantageous effects of the various embodiments of the present disclosure will be more clearly understood from the detailed description below. That is, those skilled in the art can derive the unexpected effects according to the embodiments of the present disclosure from the various embodiments of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

[0057] Figure 2 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.

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

[0059] Figure 4 is a diagram illustrating the mapping of physical channels in time slots to which various embodiments may apply.

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

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

[0062] Figure 7 The illustration shows acquisition of DL time synchronization information at a user equipment (UE), to which various embodiments of the present disclosure may be applied.

[0063] Figure 8 A system information (SI) acquisition process to which various embodiments of the present disclosure are applicable is illustrated.

[0064] Fig. 9 is a diagram illustrating an exemplary multi-beam transmission to which various embodiments may be applicable.

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

[0066] Fig.11 is a diagram illustrating an exemplary 4-step Random Access Channel (RACH) procedure to which various embodiments of the present disclosure may be applicable.

[0067] Fig.12 is a diagram illustrating an exemplary 2-step RACH procedure to which various embodiments of the present disclosure may be applicable.

[0068] Fig.13 is a diagram illustrating an exemplary contention-free RACH procedure to which various embodiments of the present disclosure may be applied.

[0069] Fig.14 is a diagram illustrating transmission of SSBs and physical random access channel (PRACH) resources linked to the SSBs according to various embodiments of the present disclosure.

[0070] Fig.15 is a diagram illustrating transmission of SSBs and PRACH resources linked to SSBs according to various embodiments of the present disclosure.

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

[0072] Fig.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.

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

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

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

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

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

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

[0079] Fig.24 is a diagram schematically illustrating a method of operating a UE and a BS according to various embodiments.

[0080] Fig.25 is a flowchart illustrating a method of operating a UE according to various embodiments.

[0081] Fig.26 is a flowchart illustrating a method of operating a BS according to various embodiments.

[0082] Fig. 27 is a diagram illustrating a device for implementing various embodiments of the present disclosure.

[0083] Fig.28 An exemplary communication system to which various embodiments of the present disclosure are applied is illustrated.

[0084] Fig.29 An exemplary wireless device to which various embodiments of the present disclosure may be applied is illustrated.

[0085] Fig.30 Other exemplary wireless devices to which various embodiments of the present disclosure are applied are illustrated.

[0086] Fig.31 An exemplary portable device to which various embodiments of the present disclosure are applied is illustrated.

[0087] Fig.32 An exemplary vehicle or autonomous driving vehicle to which various embodiments of the present disclosure are applied is illustrated. DETAILED DESCRIPTION

[0088] Various embodiments may be applicable to various wireless 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, or Evolved UTRA (E-UTRA). UTRA is part of Universal Mobile Telecommunications System (UMTS). 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) is a part of Evolved UMTS (E-UMTS) using E-UTRA, and LTE-Advanced (LTE-A) is an evolved version of 3GPP LTE. 3GPP NR (New Radio or New Radio Access Technology) is an evolved version of 3GPP LTE / LTE-A.

[0089] For the sake of clarity, 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. For the background technology, terms, and abbreviations used in the description of the various embodiments, please refer to the 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 3GPP TS 38.355, 3GPP TS 38.455, etc.

[0090] 1.3GPP system

[0091] 1.1. Physical channels and general signal transmission and reception

[0092] In a wireless access system, a UE receives information from a BS on DL and sends information to the BS on UL. The information sent and received between the UE and the BS includes general data information and various types of control information. Depending on the type / usage of the information sent and received between the BS and the UE, there are many physical channels.

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

[0094] When a UE is powered on or enters a new cell, the UE performs an initial cell search (S11). The initial cell search involves acquiring synchronization with the BS. Specifically, the UE synchronizes its timing with the BS and acquires information such as a cell identifier (ID) by receiving a primary synchronization channel (P-SCH) and a secondary synchronization channel (S-SCH) from the BS.

[0095] The UE can then obtain information broadcast in the cell by receiving a physical broadcast channel (PBCH) from the BS.

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

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

[0098] Subsequently, in order to complete the connection to the BS, the UE may perform a random access procedure with the BS (S13 to S16). In the random access procedure, the UE may send a preamble on a physical random access channel (PRACH) (S13), and may receive a PDCCH and a random access response (RAR) to the preamble on a PDSCH associated with the PDCCH (S14). The UE may send a PUSCH by using 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).

[0099] 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.

[0100] 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).

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

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

[0103] 1.2 Radio Frame Structure

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

[0105] The NR system may support multiple parameter sets. The parameter set may be defined by a subcarrier spacing (SCS) and a cyclic prefix (CP) overhead. Multiple SCSs may be derived by scaling the default SCS by an integer N (or μ). In addition, even assuming that very small SCSs are not used in very high carrier frequencies, the parameter set to be used may be selected independently of the frequency band of the cell. In addition, the NR system may support various frame structures based on multiple parameter sets.

[0106] Now, a description of OFDM parameter sets and frame structures that can be considered for the NR system will be given. Various 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.

[0107] [Table 1]

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

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

[0110] The NR band is defined by two types of frequency ranges, FR1 and FR2. FR1 may be a range below 6 GHz, while FR2 may be a range above 6 GHz, i.e., a millimeter wave (mmWave) band.

[0111] As an example, the following Table 2 defines the NR frequency band.

[0112] [Table 2]

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

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

[0115] 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 in the normal CP case, 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 in the extended CP case.

[0116] [Table 3]

[0117]

[0118] [Table 4]

[0119]

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

[0121] In the 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 a plurality of cells aggregated for one UE. Therefore, an (absolute time) period (for convenience, generally referred to as a time unit (TU)) of time resources including the same number of symbols (e.g., subframe (SF), time slot, or TTI) may be configured differently for the aggregated cells.

[0122] Figure 2 An example of μ=2 (i.e., SCS of 60 kHz) is shown, where referring to Table 6, one subframe may include four time slots. Figure 2 One subframe = {1, 2, 4} time slots, which is exemplary, and the number of time slots that can be included in one subframe is defined as listed in Table 3 or Table 4.

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

[0124] Figure 32 is a diagram illustrating a time slot structure in an NR system to which various embodiments of the present disclosure are applicable.

[0125] refer to 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.

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

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

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

[0129] Figure 4 is a diagram illustrating an exemplary mapping of physical channels in time slots to which various embodiments may apply.

[0130] A time slot may include all DL control channels, DL or UL data, and UL control channels. For example, the first N symbols of a time slot may be used to send a downlink control channel (hereinafter referred to as the DL control region), and the last M symbols of the time slot may be used to send a 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 of the DL to UL switching time in the time slot may be used as time gaps.

[0131] 1.3. Channel structure

[0132] DL channel structure

[0133] 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.

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

[0135] PDSCH conveys DL data (e.g., DL shared channel transport block (DL-SCH TB)) and uses a modulation scheme such as quadrature phase shift keying (QPSK), 16-order quadrature amplitude modulation (16QAM), 64QAM, or 256QAM. TB is encoded into codewords. PDSCH can deliver up to two codewords. Scrambling and modulation mapping are performed on a codeword basis, 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 a corresponding antenna port.

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

[0137] The PDCCH may deliver downlink control information (DCI), such as DL data scheduling information, UL data scheduling information, etc. The PUCCH may deliver uplink control information (UCI), such as ACK / NACK information for DL ​​data, channel state information (CSI), scheduling request (SR), etc.

[0138] PDCCH carries DCI and is modulated with QPSK. One PDCCH includes 1, 2, 4, 8 or 16 control channel elements (CCEs) according to the aggregation level (AL). One CCE includes 6 resource element groups (REGs). One REG is defined by one OFDM symbol multiplied by one (P)RB.

[0139] 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 each other in the time / frequency domain. A CORESET may be configured by system information (e.g., a master information block (MIB)) or by 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.

[0140] The UE acquires the DCI delivered 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 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. A search space set is determined based on the following parameters.

[0141] Table 5 lists exemplary features of the corresponding search space types.

[0142] [Table 5]

[0143]

[0144] Table 6 lists an exemplary DCI format transmitted on the PDCCH.

[0145] [Table 6]

[0146]

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

[0148] 1.3.2.UL channel structure

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

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

[0151] The PUSCH delivers UL data (e.g., UL shared channel transport block (UL-SCHTB)) and / or UCI in a cyclic prefix-orthogonal frequency division multiplexing (CP-OFDM) waveform or a discrete Fourier transform-spread-orthogonal frequency division multiplexing (DFT-s-OFDM) waveform. If the PUSCH is sent in a DFT-s-OFDM waveform, the UE sends the PUSCH by applying transform precoding. For example, if transform precoding is not possible (e.g., transform precoding is disabled), the UE may send the PUSCH in a CP-OFDM waveform, and if transform precoding is possible (e.g., transform precoding is enabled), the UE may send the PUSCH in a CP-OFDM waveform or a DFT-s-OFDM waveform. PUSCH transmission may be dynamically scheduled by a UL grant in a 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.

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

[0153] PUCCH delivers 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.

[0154] [Table 7]

[0155]

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

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

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

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

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

[0161] 1.4. Bandwidth Part (BWP)

[0162] The NR system can support up to 400 MHz for each carrier. If the UE always turns on the radio frequency (RF) module for all carriers when operating on such a wideband carrier, the battery consumption of the UE may increase. Considering multiple use cases operating on 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) may 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 instead of the full bandwidth of the wideband carrier. The partial bandwidth is called a BWP. A BWP is a subset of contiguous common RBs defined for a parameter set μi in a BWP i of a carrier in the frequency domain, and a parameter set (e.g., SCS, CP length, and / or slot / microslot duration) may be configured for each BWP.

[0163] The BS may configure one or more BWPs in one carrier configured to the UE. Alternatively, if the UEs are concentrated in a specific BWP, the BS may move some UEs to another BWP for load balancing. For frequency domain inter-cell interference elimination between adjacent cells, the BS may configure BWPs on both sides of the cell in addition to some center spectrums in the full bandwidth within the same time slot. That is, the BS may configure at least one DL / UL BWP for a UE associated with a broadband carrier, activate at least one DL / UL BWP among the DL / UL BWPs configured at a specific time (through 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 (through L1 signaling, MAC CE, or RRC signaling). Alternatively, the BS may configure a timer and switch the UE to a predetermined DL / UL BWP when the timer expires. In particular, the activated DL / UL BWP is referred to as an active DL / UL BWP. The UE may not receive any DL / UL BWP configuration before performing initial access or setting up an RRC connection. The DL / UL BWP assumed by the UE in this case is called the initial active DL / UL BWP.

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

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

[0166] 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 a synchronization signal / physical broadcast channel (SS / PBCH) block.

[0167] refer to 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 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.

[0168] Each of the PSS and SSS includes one OFDM symbol multiplied by 127 subcarriers, and the PBCH includes three OFDM symbols multiplied by 576 subcarriers. Polar coding and QPSK are applied to the PBCH. The PBCH includes data REs and DMRS REs in each OFDM symbol. Each RB has three DMRS REs, and there are three data REs between every two adjacent DMRS REs.

[0169] Community Search

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

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

[0172] [Table 8]

[0173]

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

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

[0176] refer to 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 SSB periodicity can be set by the network (e.g., BS) 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 can be configured with a 5 millisecond time window (i.e., half a frame), and an SSB can be repeatedly sent up to L times within an SS burst set. The maximum number of transmissions L of an SSB can be given as follows according to the frequency band of the carrier. One time slot includes up to two SSBs.

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

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

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

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

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

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

[0183] --For operation with shared spectrum channel access (e.g., U-band and UCell): where n=0, 1, 2, 3, 4.

[0184] - 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 lower than 3 GHz, and n=0,1 for carrier frequencies from 3 GHz to 6 GHz.

[0185] - Case C: 30-kHz SCS: The index of the first symbol of the candidate SSB is given as {2,8}+14*n, where n=0,1 for carrier frequencies equal to or below 3 GHz, and n=0,1,2,3 for carrier frequencies from 3 GHz to 6 GHz.

[0186] - For operation without shared spectrum channel access: (1) In 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 case of non-paired 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.

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

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

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

[0190] Synchronization process

[0191] Figure 7 The diagram illustrates acquisition of DL time synchronization information at a UE, to which various embodiments of the present disclosure may be applied.

[0192] The UE can obtain DL synchronization by detecting the SSB. The UE can identify the structure of the SSB burst set based on the index of the detected SSB, and thereby detect the symbol, time 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.

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

[0194] The UE can then obtain 1-bit half-frame indication information c0. When the carrier frequency is 3 GHz or below, the half-frame indication information can be implicitly signaled through 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 1 bit of the 3 bits that can be indicated by the 8 PBCH DMRS sequences, except for the bit indicating the SSB index, can be used as a half-frame indication.

[0195] Finally, the UE can obtain the SSB index based on the DMRS sequence and the PBCH payload. The SSB candidates are indexed from 0 to L-1 in chronological 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 of the three bits except the bit indicating the SSB index can be used as a half-frame indication.

[0196] System information acquisition

[0197] Figure 8A system information (SI) acquisition process to which various embodiments of the present disclosure are applicable is illustrated.

[0198] The UE may acquire access stratum (AS) / non-access stratum (NAS) information in the SI acquisition procedure. The SI acquisition procedure may be applied to UEs in RRC_IDLE, RRC_INACTIVE, and RRC_CONNECTED states.

[0199] 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.

[0200] -MIB may include information / parameters related to the reception of SystemInformationBlockType1 (SIB1) and may be transmitted over the PBCH of the SSB.

[0201] -MIB may include information / parameters related to the reception of SystemInformationBlockType1 (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.

[0202] -subCarrierSpacingCommon ENUMERATED{scs15or60,scs30or120},

[0203] -ssb-SubcarrierOffset INTEGER(0..15),

[0204] -pdcch-ConfigSIB1 INTEGER(0..255),

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

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

[0207] The fields are described in Table 9 below.

[0208] [Table 9]

[0209]

[0210] When selecting an initial cell, the UE may assume that a half frame with SSB is repeated in a period of 20 ms. 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 can determine that the CORESET for the Type0-PDCCH common search space exists. SSB >23 (for FR1) or k SSB >11 (for FR2), the UE may determine that a CORESET for a Type0-PDCCH common search space does not exist. A Type0-PDCCH common search space may be a type of a PDCCH search space and may be used to send a PDCCH for scheduling an SI message. When a Type0-PDCCH common search space exists, 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 receiving a PDCCH (e.g., search space#0) based on information in the MIB (e.g., pdcch-ConfigSIB1). When a Type0-PDCCH common search space does not exist, pdcch-ConfigSIB1 may provide information about the frequency positions where SSB / SIB1 exist and the frequency ranges where SSB / SIB1 does not exist.

[0211] SIB1 may include information about 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 the information required for the UE to request SI. SIB1 may be sent via PDSCH, the PDCCH for scheduling SIB1 may be sent via the Type0-PDCCH common search space, and SIB1 may be sent via the PDSCH indicated by the PDCCH.

[0212] 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).

[0213] Beam Alignment

[0214] Fig. 9 is a diagram illustrating an exemplary multi-beam transmission to which various embodiments may be applicable.

[0215] Beam scanning refers to changing the beam (direction) of a radio signal over time through a transmit receive point (TRP) (e.g., BS / cell) (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 remains in the SSB (index) group. That is, the transmission beam direction of the SSB is repeated for multiple consecutive SSBs. 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, depending on the frequency band of the carrier. 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.

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

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

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

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

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

[0221] Channel Measurement and Rate Matching

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

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

[0224] -When the number and position of SSBs actually sent are related to rate matching, this information can be indicated by UE-specific RRC signaling or RMSI. UE-specific RRC signaling includes a complete bitmap (e.g., length L) for frequency ranges below and above 6 GHz. RMSI includes a complete bitmap for the frequency range below 6 GHz and a compressed bitmap for the frequency range above 6 GHz. Specifically, information about the SSBs actually sent can 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 can be reserved for SSB transmission, and PDSCH and / or PUSCH can be rate matched taking into account the SSB resources.

[0225] -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 within the measurement period. The SSB set may be indicated for each frequency layer. If the SSB set is not indicated, a default SSB set may be used. The default SSB set includes all SSBs within the measurement period. The SSB set may be indicated by a complete bitmap (e.g., of length L) of RRC signaling. When the UE is in RRC idle mode, the default SSB set is used.

[0226] 2. Random Access (RACH) Process

[0227] 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.

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

[0229] The random access procedure can be divided 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.

[0230] 2.1.4 RACH: Type 1 Random Access Procedure

[0231] Fig.14 is a diagram illustrating an exemplary 4-step RACH procedure to which various embodiments of the present disclosure may be applicable.

[0232] When performing a (contention-based) random access procedure (4-step RACH procedure) in four steps, the UE may transmit a message (message 1 (Msg1)) including a preamble associated with a specific sequence on a PRACH (1401), and receive a response message (RAR message) for the preamble on a PDCCH and a 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 may receive a message (message 4 (Msg4)) including contention resolution information for the contention resolution procedure from the BS (1407).

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

[0234] [Table 10]

[0235]

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

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

[0238] Multiple preamble formats are defined by one or more RACH OFDM symbols and different CPs (and / or guard times). The RACH configuration of a cell is provided to the UE in the system information of the cell. 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 sends a RACH preamble in the RACH time-frequency resources associated with the detected or selected SSB.

[0239] The SSB threshold for RACH resource association may be configured by the network, and the RACH preamble may be sent or resent based on the SSB having a reference signal received power (RSRP) measurement that satisfies the threshold. For example, the UE may select one of the SSBs that satisfies the threshold and send or resend the RACH preamble in the RACH resource associated with the selected SSB. For example, when resending the RACH preamble, the UE may reselect one of the SSBs and resend the RACH preamble in the RACH resource associated with the reselected SSB. That is, the RACH resource used to resend the RACH preamble may be the same and / or different from the RACH resource used to send the RACH preamble.

[0240] 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 by the random access radio network temporary identifier (RA-RNTI) cyclic redundancy check (CRC) and is transmitted. 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 the RAR information of the preamble it sends, i.e., Msg1. The UE can make a 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 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.

[0241] 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 transmission time alignment information, UL transmission power adjustment information, and UL radio resource allocation information. Upon receiving its RAR information on the PDSCH, the UE may obtain timing advance information, initial UL grant, and TC-RNTI 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 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 for 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.

[0242] As described previously, the UL grant included in the RAR schedules PUSCH transmission to the BS. The PUSCH carrying the initial UL transmission based on the UL grant of the RAR is called Msg3 PUSCH. The content of the RAR UL grant starts from the most significant bit (MSB) and ends at the least significant bit (LSB), as shown in Table 11.

[0243] [Table 11]

[0244] 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 Transmit Power Control (TPC) for Msg3 PUSCH 3 CSI Request 1

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

[0246] [Table 12]

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

[0248] 2.2.2 RACH: Type 2 Random Access Procedure

[0249] Fig.12 is a diagram illustrating an exemplary 2-step RACH procedure to which various embodiments of the present disclosure may be applicable.

[0250] The (contention-based) RACH procedure is performed in two steps, that is, a 2-step RACH procedure has been proposed to simplify the RACH procedure and thus achieve low signaling overhead and low delay.

[0251] In the 2-step RACH process, the operation of sending Msg1 and the operation of sending Msg3 in the 4-step RACH process can be incorporated into the operation of sending one message (message A (MsgA) including PRACH and PUSCH) by the UE. The operation of sending Msg2 and the operation of sending Msg4 by the BS in the 4-step RACH process can be incorporated into the operation of sending one message (message B (MsgB) including RAR and contention resolution information).

[0252] 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).

[0253] In addition, 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).

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

[0255] 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.

[0256] 2.3 Non-contention RACH

[0257] Fig.13 is a diagram illustrating an exemplary contention-free RACH procedure to which various embodiments of the present disclosure may be applied.

[0258] The contention-free RACH procedure can be used for handover of the UE to another cell or BS, or can be performed upon a BS command request. The contention-free RACH procedure is substantially similar to the contention-based RACH procedure. However, compared to the contention-based RACH procedure in which the preamble to be used is randomly selected from multiple RACH preambles, the preamble to be used by the UE in the contention-free RACH procedure (referred to as a dedicated RACH preamble) is assigned to the UE by the BS (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 procedure starts, the UE sends a dedicated RACH preamble to the BS (1903). When the UE receives a RAR from the BS, the RACH procedure is completed (1905).

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

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

[0261] Fig.14 and Fig.15 is a diagram showing 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.

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

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

[0264] 1) The BS may send a synchronization block for each wide beam so that the UE can find the BS in the initial access phase, i.e., perform cell search or cell acquisition to measure the channel quality of each beam used for the wide beam and find the best wide beam for the initial stage of beam acquisition.

[0265] 2) The UE can perform a cell search on the synchronization block of each beam and can use the detection result of each beam to perform DL beam acquisition.

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

[0267] 4) In order for the UE to inform the BS of the DL beam acquisition result (e.g., beam index) at the wide beam level at the same time as the RACH process, the BS can connect or associate the synchronization block transmitted for each beam and the PRACH resource to be used for PRACH transmission. When the UE performs the RACH process using the PRACH resource connected to the best beam direction found by the UE, the BS can acquire information about the DL beam suitable for the UE during the process of receiving the PRACH preamble.

[0268] In a multi-beam environment, it may be important to accurately determine the Tx beam and / or Rx beam direction between the UE and the TRP by the UE and / or the transmit receive point (TRP). In a multi-beam environment, beam scanning of repeated transmission signals or reception signals depending on the TX / RX reciprocity capability of the TRP (e.g., BS) or the UE may be considered. The TX / RX reciprocity 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 reciprocity capability in the TRP and the UE is not maintained, the UE may 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 the UE's DL measurement of one or more TX beams of the TRP, and / or the TRP determines the TRP TX beam for corresponding DL transmission based on the TRP's UL measurement of one or more RX beams of 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 the UE's DL measurements of 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 the TRP based on UL measurements of one or more TX beams of the UE.

[0269] 2.5.PRACH preamble structure

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

[0271] - Cyclic Prefix (CP): This prevents access from the previous / forward (OFDM) symbol and can bundle PRACH preamble signals arriving at the BS with different time delays in the same time zone. That is, when the CP is set to fit the maximum cell radius, the PRACH preambles sent by UEs in the cell in the same resource can enter the PRACH reception window corresponding to the PRACH preamble length 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 .

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

[0273] – Guard Time (GT): This may be a duration defined to prevent a PRACH signal transmitted from the farthest to the BS within the PRACH coverage and delayed to arrive at the BS from interfering with a signal arriving at the BS after the PRACH symbol duration, and during this period the UE does not transmit a signal, and thus the GT may not be defined based on the PRACH signal. The GT may have a length of T GP .

[0274] 2.6. Mapping to physical resources for physical random access channel

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

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

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

[0278] -The PRACH configuration index in the RACH configuration table can be given from the higher layer parameters prach-ConfigurationIndex, msgA-prach-ConfigurationIndexNew (if configured), etc. of the RACH configuration table for random access configuration regarding FR1 and paired spectrum / supplementary uplink and the RACH configuration table for random access configuration regarding FR2 and non-paired spectrum.

[0279] The RACH configuration table may be a PRACH configuration index, preamble format, n SFN A table showing the relationship between one or more of mod x=y, a subframe number, a start symbol, a PRACH slot number, a time-domain PRACH opportunity number within a PRACH slot, and a PRACH duration.

[0280] These situations are described below:

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

[0282] -(2) Random access configuration for FR1 and non-paired spectrum

[0283] -(3) Random access configuration for FR2 and non-paired spectrum

[0284] Table 13 below shows a portion of a RACH configuration index example for random access configuration of (2) FR1 and non-paired spectrum.

[0285] [Table 13]

[0286]

[0287] The RACH configuration table indicates specific values ​​for parameters that require configuration of RACH opportunities (e.g., preamble format, periodicity, SFN offset, RACH subframe / time slot index, starting OFDM symbol, RACH time slot number, opportunity number, OFDM symbol of RACH format, etc.). When a RACH configuration index is indicated, a specific value associated with the indicated index may be used.

[0288] 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.

[0289] 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 time slot.

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

[0291] For example, the RACH timeslot number (in a subframe and / or timeslot with a specific SCS) may be indicated by a parameter: RACH timeslot number.

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

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

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

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

[0296] refer to Fig.16 (b), for example, when the starting OFDM symbol is indicated by 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 the value indicated by the parameter: the number of time domain RACH opportunities within the RACH slot. For example, the preamble format may be indicated by the parameter: preamble format. For example, the preamble formats A1 / B1, B1, A2 / B2, A3 / B3, B4, C0, C2, etc. may be indicated.

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

[0298] 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 between the following parameters may be satisfied: PRACH configuration index, RACH format, period (x)=8, SFN offset (y), subframe number, start symbol (index), number of PRACH slots in a subframe, number of PRACH opportunities in a PRACH slot, PRACH duration / OFDM symbol for RACH format, etc. The correspondence relationship may be identified by the RACH configuration index and the RACH configuration table.

[0299] 3. Various embodiments of the present disclosure

[0300] A detailed description of various embodiments of the present disclosure will be given based on the above technical concepts. The foregoing contents of Clauses 1 and 2 apply to 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 Clauses 1 and 2.

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

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

[0303] -BWP: Bandwidth Part

[0304] -CBRA: Contention-based random access

[0305] -CDM: Code Division Multiplexing (Code Domain Sharing)

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

[0307] -CFRA: Contention-free random access

[0308] -CP-OFDM: Orthogonal frequency division multiplexing based on cyclic prefix, which can be understood as the case where transform precoding is disabled.

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

[0310] -DL: Downlink

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

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

[0313] -MCS: Modulation and Coding Scheme

[0314] -OCC: Orthogonal Cover Code

[0315] -OFDM: Orthogonal Frequency Division Multiplexing

[0316] -PAPR: Peak to Average Power Ratio

[0317] -PRACH: Physical Random Access Channel

[0318] -PRB: Physical Resource Block

[0319] -PRU: PUSCH resource unit

[0320] -PO: PUSCH timing

[0321] -PUSCH: Physical Uplink Shared Channel

[0322] -RA: Random Access

[0323] -RACH: Random Access Channel

[0324] -RAPID: Random Access Preamble Identifier

[0325] -RAR: Random Access Response

[0326] -RB: Resource Block

[0327] -RE: Resource Element

[0328] -RNTI: Radio Network Temporary Identifier

[0329] -RO: RACH timing or PRACH timing

[0330] -SCID: Scrambling Identifier

[0331] -TBS: Transport Block Size

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

[0333] -UL: Uplink

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

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

[0336] In the description of various embodiments, when it is said that something is more / greater than or equal to A, this may be interpreted to mean that it is greater than or equal to / more than A.

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

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

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

[0340] 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 such a relationship in a simple manner. For example, the state of the RO (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.

[0341] Various embodiments may be directed to a method of configuring a MsgA PUSCH.

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

[0343] Various embodiments may be directed to a RACH preamble to PUSCH (resource element) mapping method for supporting a 2-step RACH procedure.

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

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

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

[0347] refer to 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.

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

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

[0350] 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.

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

[0352] 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.

[0353] DMRS for MsgA PUSCH

[0354] DMRS configuration type for MsgA PUSCH

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

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

[0357] 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.

[0358] For example, for configuration type 1, three pairs (6 REs) of DMRS 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.

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

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

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

[0362] PUSCH DMRS port / sequence

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

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

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

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

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

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

[0369] According to various embodiments, the PRACH preambles may be mapped to valid PRUs within the MsgA associated period in the following order:

[0370] - First, in ascending order of frequency resource index of PO used for frequency reuse

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

[0372] --The DMRS index may be determined first in ascending order of DMRS port index and secondly in ascending order of DMRS sequence index.

[0373] - Third, in ascending order of the time resource index of the PO used for time multiplexing within a PUSCH time slot

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

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

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

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

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

[0379] -Secondly, in ascending order of frequency resource index of PRACH opportunities used for frequency reuse

[0380] - Third, in ascending order of the time resource index of the PRACH opportunities used for time multiplexing within the PRACH time slot

[0381] can be mapped to (effective) PO:

[0382] - First, in ascending order of frequency resource index of PO used for frequency reuse

[0383] - Secondly, in ascending order of DMRS indices within the PO, wherein the DMRS indices may be determined first in ascending order of DMRS port indices and secondly in ascending order of DMRS sequence indices.

[0384] - Third, in ascending order of the time resource index of the PO used for time multiplexing within the PUSCH time slot

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

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

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

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

[0389] 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 suitable for supporting multiple UEs in the PO, a relatively low number of antenna ports (e.g., 1 or 2) may be allocated. Conversely, for example, if a 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.

[0390] 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. The reason for this is that even if the OFDM symbol reception timing is quite large (e.g., FFT size / 4), the cyclic shift can identify the antenna port.

[0391] Sequence initialization for MsgA PUSCH DMRS

[0392] 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 ​​may be configured by a higher layer signal (e.g., SIB1 and / or RACH-ConfigCommon). According to various embodiments, the sequence may be specified / indicated depending on RAPID (in the description of various embodiments, the term "depending on" may be replaced with the following terms: based on, using, etc.).

[0393] Additionally / alternatively, according to various embodiments, when transform precoding is disabled, the following Equation 1 may be used for a pseudo-random sequence generator for MsgA PUSCH. According to various embodiments, when transform precoding is disabled, the pseudo-random sequence generator for MsgA PUSCH may be initialized according to the following Equation 1.

[0394] [Equation 1]

[0395] c init =(2 17 (N slot symb n u s，f +1+1)(2N nSCID ID +1)+2N nSCID ID +n sCID )mod 2 31

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

[0397] For example, N slot symb The number of symbols per time slot can be indicated.

[0398] For example, u s，f Can represent the timeslot number in the frame for SCS configuration u.

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

[0400] For example, n can be specified depending on RAPIDSCID ∈{0, 1, ..., M-1}.

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

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

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

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

[0405] According to various embodiments, for MsgA PUSCH, the seed value (eg, N 0 ID and N 1 ID ).

[0406] According to various embodiments, n in the above equation 1 may be specified depending on 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 .

[0407] 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.

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

[0409] 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.

[0410] 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 CDM group of two (CDM) groups may be configured for the two antenna ports.

[0411] According to various embodiments, when the number of PRUs in the PO 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 PO, two CDM groups may be used with the same DMRS sequence. For example, when two antenna ports are used in the PO, one of the two (CDM) groups may be configured with two different DMRS sequences.

[0412] 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.

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

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

[0415] [Table 14]

[0416] Number of PRUs in PO {Number of DMRS ports, number of DMRS sequences 1 {1,1} 2 {2,1}、{1,2} 4 {4,1}、{2,2} 8 {4,2}

[0417] 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.

[0418] For example, when the number of PRUs in the PO is 2, two sets of combinations of DMRS ports and DMRS sequences can be defined (e.g., {2,1}, {1,2}). 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.

[0419] For example, when the number of PRUs in the PO 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 PO, two CDM groups may be used with the same DMRS sequence. For example, when two antenna ports are used in the PO, one of the two (CDM) groups may be configured with two different DMRS sequences.

[0420] For example, 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.

[0421] 3.2.MsgA PUSCH configuration

[0422] MsgA PUSCH scrambling sequence

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

[0424] 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 CFRA.

[0425] According to various embodiments, the value c used for scrambling sequence initialization int Can be configured with n RNTI and n ID .

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

[0427] For example, in the 4-step RACH process, TC-RNTI / C-RNTI can be applied as n for Msg3 PUSCH 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 (e.g., RA-RNTI) different from TC-RNTI / C-RNTI may be applied as n RNTI According to various embodiments, the C-RNTI may be used as n RNTI Applicable to UE in RRC_CONNECTED state.

[0428] In the 4-step RACH process, N can be applied for Msg3 PUSCH ID cell (Physical Cell Identifier (PCI)) as n ID On the other hand, for MsgA PUSCH of the 2-step RACH procedure, multiple RAPIDs may 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, a method of applying n ID Multiple scrambling sequences generated by different values ​​of N ID cell (Applied to UL MIMO) According to various embodiments, in case of CBRA, RAPID may be applied as n for MsgA PUSCH. ID According to various embodiments, in case of CBRA, RAPID and C-RNTI may be applied as seed values ​​for sequence initialization for MsgA PUSCH.

[0429] According to various embodiments, the PUSCH scrambling sequence initialization equation may vary depending on the usage of mapping between preamble and PRU.

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

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

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

[0433] [Equation 2]

[0434] c init=RA-RNTI×2 16 +RAPID×2 10 +n ID

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

[0436] For example, n may be configured via cell-specific higher layer parameters. ID , and / or n ID =N ID cell .

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

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

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

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

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

[0442] For example, including RAPID in the equations (Equation 1, etc.) for initializing the scrambling sequence may be to improve the inter-user interference randomization effect on the PUSCH resources.

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

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

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

[0446] In case 1, RAPID can be changed to a DMRS index.

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

[0448] 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 equation 3. At least one of the parameters used in the following equation 3 may be generated / obtained / determined according to various embodiments. Equation 3 may be understood as a more specific equation than equation 2.

[0449] [Equation 3]

[0450]

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

[0452] For example, the value of each parameter may be determined as follows.

[0453] - 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 in the CSS via DCI format 1_0, and if the higher layer parameter dataScramblingIdentityPUSCH is configured, then n ID ∈{0, 1, ..., 1023} may have the value indicated in the higher layer parameter dataScramblingIdentityPUSCH.

[0454] - 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.

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

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

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

[0458] For example, you can use n ID Randomize inter-cell interference.

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

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

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

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

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

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

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

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

[0467] According to various embodiments, the MCS may be indicated only for the PUSCH configuration. According to various embodiments, among the MCS for MsgAPUSCH and the RRC for TBS, only the MCS may be signaled. According to various embodiments, the TBS may be determined based on a predetermined correspondence with the MCS value by a predetermined TBS table. According to various embodiments, a value range of the TBS and / or MCS may be preconfigured.

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

[0469] In the 4-step RACH process, the MCS for Msg3 can be allocated / indicated by the UL grant in the RAR message. For example, the BS can specify the MCS from low index to high index depending on the channel state of the UE. For example, the time / frequency resources for PUSCH can be allocated depending on the selected MCS level and the required coverage.

[0470] On the other hand, in the 2-step RACH procedure, it may be difficult to allow flexible MCS selection. If the UE selects an MCS level for UL transmission depending on DL measurement results, it may be difficult to apply the MCS level to UL transmission because the channel state and interference level 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.

[0471] 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.

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

[0473] According to various embodiments, when multiple sets for DMRS frequency resources are allowed, each DMRS frequency resource (eg, CDM group) may be configured by a MsgA PUSCH configuration.

[0474] 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 depending on the MCS level.

[0475] 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 part of the value range may consist of a set of RAPIDs that may be associated with MsgA PUSCH configurations. In addition, according to various embodiments, other parts of the value range may be associated with other MsgA PUSCH configurations.

[0476] 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.

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

[0478] [Table 15]

[0479]

[0480] According to various embodiments, when multiple MCS levels are allowed for PUSCH transmission, multiple types of PUSCH resources may be defined depending on the MCS level. As a result, 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 a RAPID associated with the MCS level.

[0481] 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.

[0482] For example, assuming two different PUSCH resources (eg, 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 may be specified for each PUSCH resource.

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

[0484] refer to Fig. 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.

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

[0486] 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.

[0487] 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.

[0488] 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.

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

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

[0491] 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 / slot offset for PO group, etc.) may be independently configured for each MsgA PUSCH configuration. According to various embodiments, allowing multiple configurations may be for configuring 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.

[0492] 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.

[0493] 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 time / frequency resources (see Fig. 20 ).

[0494] PUSCH configuration indication

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

[0496] - 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.

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

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

[0499] --For example, the UE may select a preamble group depending on a channel state (eg, synchronization signal reference signal received power (SS-RSRP)).

[0500] 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 part of the value range may consist of a RAPID set that may be associated with a MsgA PUSCH configuration. According to various embodiments, other parts of the value range may be associated with other PUSCH configurations.

[0501] According to various embodiments, a method of indicating selection of different PUSCH configurations may be provided.

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

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

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

[0505] - For a UE in RRC_ACTIVE state:

[0506] --Up to two MsgA PUSCH configurations can be supported in UL BWP.

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

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

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

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

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

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

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

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

[0515] [Table 16]

[0516]

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

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

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

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

[0521] Frequency hopping and guard bands within time slots

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

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

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

[0525] According to various embodiments, intra-slot hopping per PO for MsgA may be configured based on configuration per MsgA.

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

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

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

[0529] - According to various embodiments, POs may be continuous and / or discontinuous in time.

[0530] According to various embodiments, inter-transition guard periods may or may not be used. According to various embodiments, use of guard periods between transitions may or may not be allowed.

[0531] According to various embodiments, frequency diversity gain may be obtained based on time slot hopping.

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

[0533] 3.3. Mapping of RACH preamble and PUSCH resources

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

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

[0536] According to various embodiments, for RO separation between 2-step RACH procedure and 4-step RACH procedure, configuration of a subset for using RO in a time slot may be allowed.

[0537] 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.

[0538] 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.

[0539] 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 where RO sharing is allowed and not allowed, the PRACH preamble for the 4-step RACH procedure and the PRACH preamble for the 2-step RACH procedure may be configured / specified separately.

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

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

[0542] 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 sending the PRACH preamble expects to initiate a 2-step RACH process or a 4-step RACH process based on the corresponding RO.

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

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

[0545] 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:

[0546] -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 under the assumption that most OFDM symbols in the 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.

[0547] -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 the RO. According to various embodiments, the OFDM symbols after the RO may be allocated for the PUSCH of MsgA.

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

[0549] refer to Fig.21 , the RO for sending the PRACH preamble included in the MsgA and the PO for sending the PUSCH included in the MsgA can be time division multiplexed (TDM) at the time slot level.

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

[0551] For example, each of the ROs and / or POs may be multiplexed in each time slot in various ways.

[0552] Fig.21 (a) illustrates an example in which TDM is performed on RO in a RACH slot and FDM / TDM is performed on PUSCH in a PUSCH slot.

[0553] Fig.21(b) illustrates an example in which FDM / TDM is performed on RO in a RACH slot and FDM is performed on PUSCH in a PUSCH slot.

[0554] Fig.21 (c) illustrates an example in which FDM is performed on RO in a RACH slot and TDM is performed on PUSCH in a PUSCH slot.

[0555] Fig.21 (d) illustrates an example in which TDM is performed on RO in a RACH slot and TDM / CDM is performed on PUSCH in a PUSCH slot.

[0556] 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 a RACH time slot including the RO and a PUSCH time slot including the PO in the time domain.

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

[0558] As a contrary example, when the time offset is not configured, the RACH slot and the PUSCH slot may be continuous in the time domain.

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

[0560] refer to Fig. 22 , the RO used to send the PRACH preamble included in the MsgA and the PO used to send the PUSCH included in the MsgA can be TDMed at the symbol level.

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

[0562] For example, RO may be included in a RACH half-slot located earlier than a PUSCH half-slot in the time domain, 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 a PUSCH half-slot located after a RACH half-slot in the time domain, or mapped to a PUSCH half-slot located after a RACH half-slot in the time domain.

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

[0564] For example, each of the ROs and / or POs may be multiplexed in each half-slot in various ways.

[0565] Fig. 22 (a) illustrates an example in which one RO is configured in a RACH half slot and FDM is performed on a PUSCH in a PUSCH half slot.

[0566] Fig. 22 (b) illustrates an example in which FDM is performed on RO in a RACH half slot and TDM is performed on PUSCH in a PUSCH half slot.

[0567] Fig. 22 (c) illustrates an example in which TDM is performed on RO in a RACH half slot and FDM / TDM is performed on PUSCH in a PUSCH half slot.

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

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

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

[0571] - 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.

[0572] According to various embodiments, the 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, the period A may be the same as the SSB to RACH association period.

[0573] 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.

[0574] According to various embodiments, the association 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 association period for SSB to RO mapping may be mapped to the PRU in the available / valid PO in the association period.

[0575] 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 the PO group.

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

[0577] -0) Which POs are available for validity checking.

[0578] -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.

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

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

[0581] --B) (Many-to-one mapping) If the number of preambles for CBRA in the available RO in period A is greater than the number of PRUs in the available PO in period B, all preambles for 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.

[0582] --C) (One-to-one mapping with multiple cycles) When the number of preambles for CBRA in the available RO in period A is less than the number of PRUs in the available PO in period B, all preambles for 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.

[0583] --If the set of (multiple) actually transmitted SSBs (ATSS) mapped to the RO in the SSB to RO association period is not completely mapped with 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.

[0584] --The remaining preambles for the 2-step RACH procedure that are not mapped to the PRU may be used for MsgA preamble transmission only.

[0585] - 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.

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

[0587] [Table 17]

[0588] PRACH configuration period (msec) Associated 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}

[0589] For example, a predetermined number of SS / PBCH blocks obtained according to 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 serving cell of the UE) 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 a PRACH opportunity for 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 160ms.

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

[0591] For an unpaired spectrum:

[0592] -When tdd-UL-DL-ConfigurationCommon is not provided for the UE, the PRACH opportunity in the PRACH slot may be valid if it does not precede the SS / PBCH block in the PRACH slot and starts at least N symbols after the last SS / PBCH block received symbol (where N is an integer or natural number), 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 when the UE does not perform transmission.

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

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

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

[0596] --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 after the last DL symbol (where N is an integer or a natural number) or starts at least N symbols after the last SS / PBCH block received symbol (where N is an integer or a natural number), 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.

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

[0598] Fig.23 is a diagram illustrating exemplary time domain locations of MsgA RACH and MsgA PUSCH according to various embodiments.

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

[0600] According to various embodiments, since the number of valid ROs in a RACH period is different, two periods (eg, an association period and an association pattern period) for SSB-to-RO mapping may be defined.

[0601] 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 the SSB.

[0602] According to various embodiments, for a 2-step RACH procedure, preamble-to-PRU mapping may be provided taking into account the equal number of preambles and PRUs per SSB.

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

[0604] According to various embodiments, when a valid MsgA RO in period A and a valid MsgA PO in period B are determined, preamble-to-PRU mapping may work.

[0605] According to various embodiments, the 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, the period A may be equivalent to the SSB to RACH association period.

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

[0607] -0) Which POs are available for validity checking.

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

[0609] --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.

[0610] --C) POs that do not conflict with SSB may be available.

[0611] -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.

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

[0613] --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.

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

[0615] --A) If the set of ATSS mapped to the RO in the association period of the SSB to RO mapping is not completely mapped to the PRU in the available PO within the SSB association period, the preamble in the available RO may not be mapped to the available PRU in the available PO.

[0616] --B) The remaining preambles for the 2-step RACH procedure that are not mapped to the PRU may be used for MsgA preamble-only transmission.

[0617] Additionally / alternatively, according to various embodiments, a mapping rule between RACH preamble and PRU may be defined as follows:

[0618] -0) Which POs are available for validity checking.

[0619] -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.

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

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

[0622] --B) (Many-to-one mapping) If the number of CBRA preambles in the available RO in period A is greater than the number of PRUs in the available PO in period B, all preambles used for 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.

[0623] --C) (One-to-one mapping with multiple cycles) When the number of preambles for CBRA in the available RO in period A is less than the number of PRUs in the available PO in period B, all preambles for 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.

[0624] --If the set of (multiple) ATSS mapped to the RO in the SSB to RO association period is not completely mapped with the PRU in the available PO in period B, the preamble in the available RO may not be mapped to the PRU in the available PO.

[0625] --The remaining preambles for the 2-step RACH procedure that are not mapped to the PRU may be used for MsgA preamble transmission only.

[0626] -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. That is, each of the N consecutive PRACH preamble indices of a valid PRACH opportunity in a PRACH slot may be mapped to a PO (and a DMRS resource associated therewith). According to various embodiments, the number of consecutive PRACH preamble indices N may be determined based on the number of valid PRACH opportunities and the number of valid POs.

[0627] Fig.24 is a diagram schematically illustrating a method of operating a UE and a BS according to various embodiments.

[0628] Fig.25 is a flowchart illustrating a method of operating a UE according to various embodiments.

[0629] Fig.26 is a flowchart illustrating a method of operating a BS according to various embodiments.

[0630] refer to Figure 24 to Figure 26 In operations 2401 and 2501 according to various embodiments, the UE may obtain / generate MsgA. According to various embodiments, MsgA may include a PRACH preamble and a PUSCH.

[0631] In operations 2403 , 2503 , and 2603 according to various embodiments, the UE may transmit MsgA, and the BS may receive MsgA.

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

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

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

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

[0636] 4. Exemplary Configuration of Devices Implementing Various Embodiments of the Disclosure

[0637] 4.1. Exemplary configuration of devices to which various embodiments of the present disclosure are applied

[0638] Fig.28 is a diagram illustrating a device for implementing various embodiments of the present disclosure.

[0639] Fig.28 The illustrated device may be a UE and / or BS (e.g., an eNB or gNB) adapted to perform the aforementioned mechanisms, or any device that performs the same operations.

[0640] refer to Fig.28 , 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 the transceiver 235 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.

[0641] In particular, Fig.28 A UE may be illustrated including 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 also include a processor 210 coupled to the transceiver 235.

[0642] also, Fig.28 A network device may be illustrated including a transmitter 235 configured to send a request message to a UE and a receiver 235 configured to receive timing transmission / reception timing information from the UE. These transmitters and receivers may form a transceiver 235. The network may also include a processor 210 coupled to the transceiver 235. The processor 210 may calculate a delay based on the transmission / reception timing information.

[0643] 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.

[0644] 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.

[0645] 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.

[0646] 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 including the PRACH preamble and the PUSCH.

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

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

[0649] 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 information related to indication of CDM groups of two predetermined groups.

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

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

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

[0653] 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 information related to indication of CDM groups of two predetermined groups.

[0654] 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 aforementioned Clauses 1 to 3.

[0655] Unless contradicted with each other, various embodiments of the present disclosure may be implemented in combination. For example, unless contradicted with each other, a BS and / or a UE according to various embodiments of the present disclosure may perform operations in a combination of the embodiments of the aforementioned clauses 1 to 3.

[0656] 4.2. Examples of communication systems to which various embodiments of the present disclosure are applied

[0657] In this specification, various embodiments of the present disclosure have been described mainly with respect to data transmission and reception between a BS and a UE in a wireless communication system. However, various embodiments of the present disclosure are not limited thereto. For example, various embodiments of the present disclosure may also relate to the following technical configurations.

[0658] 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.

[0659] Hereinafter, a description will be given in more detail 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.

[0660] Fig.28 An exemplary communication system to which various embodiments of the present disclosure are applied is illustrated.

[0661] refer to Fig.28, the communication system 1 applied to various embodiments of the present disclosure includes a wireless device, a base station (BS), and a network. In this article, a wireless device refers to a device that uses a radio access technology (RAT) (e.g., 5G new RAT (NR)) or long term evolution (LTE)) to perform communication 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. In this article, a vehicle may include an unmanned aerial vehicle (UAV) (e.g., 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 (HMD), head up displays (HUD) installed in vehicles, televisions, smart phones, computers, wearable devices, home appliances, digital signage, vehicles, robots, etc. Handheld devices may include smart phones, smart boards, wearable devices (e.g., smart watches or smart glasses), and computers (e.g., notebook computers). Home appliances may include TVs, refrigerators, and washing machines. IoT devices may include sensors and smart meters. For example, BSs and networks may be implemented as wireless devices and a specific wireless device 200a may operate as a BS / network node with respect to other wireless devices.

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

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

[0664] 4.2.1 Examples of wireless devices to which various embodiments of the present disclosure are applied

[0665] Fig.29 An exemplary wireless device to which various embodiments of the present disclosure are applicable is illustrated.

[0666] refer to Fig.29 , the first wireless device 100 and the second wireless device 200 can transmit radio signals through multiple RATs (e.g., LTE and NR). In this document, {the first wireless device 100 and the second wireless device 200} may correspond to Fig.28 {wireless device 100x and BS 200} and / or {wireless device 100x and wireless device 100x}.

[0667] The first wireless device 100 may include one or more processors 102 and one or more memories 104 and additionally include one or more transceivers 106 and / or one or more antennas 108. The processor 102 may control the memory 104 and / or the transceiver 106 and may be configured to implement the descriptions, functions, processes, proposals, methods and / or operational flowcharts disclosed in this document. For example, the processor 102 may process the information in the memory 104 to generate first information / signals, and then transmit a 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 codes including commands for executing part 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. In this article, 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 send and / or receive radio signals through one or more antennas 108. Each of the transceivers 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.

[0668] The second wireless device 200 may include one or more processors 202 and one or more memories 204 and additionally include one or more transceivers 206 and / or one or more antennas 208. The processor 202 may control the memory 204 and / or the transceiver 206 and may be configured to implement the description, functions, processes, proposals, methods and / or 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 106, and then store the 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 codes including commands for executing part or all of the process controlled by the processor 202 or for executing the description, functions, processes, proposals, methods and / or operational flowcharts disclosed in this document. In this article, 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 send and / or receive radio signals through one or more antennas 208. Each of the transceivers 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.

[0669] In the following, 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 description, 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 the one or more transceivers 106 and 206 and obtain the PDU, SDU, message, control information, data, or information according to the description, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document.

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

[0671] 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, register, cache memory, computer-readable storage medium, and / or a combination thereof. One or more memories 104 and 204 may be located inside and / or outside of one or more processors 102 and 202. One or more memories 104 and 204 may be connected to one or more processors 102 and 202 via various technologies such as wired or wireless connections.

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

[0673] 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 operably coupled to the one or more memories to perform operations according to various embodiments or implementations of the present disclosure.

[0674] 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.

[0675] 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 operably coupled to the one or more memories to perform operations according to various embodiments or implementations of the present disclosure.

[0676] 4.2.2. Examples of using wireless devices applying various embodiments of the present disclosure

[0677] Fig.30 Other exemplary wireless devices to which various embodiments of the present disclosure are applied are illustrated. The wireless device may be implemented in various forms according to use cases / services (see Fig.28 ).

[0678] refer to Fig.30 , the wireless devices 100 and 200 may correspond to Fig.29 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 Fig.29 One or more processors 102 and 202 and / or one or more memories 104 and 204. For example, the transceiver 114 may include Fig.29 The control unit 120 is electrically connected to the communication unit 110, the memory 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 send information stored in the memory unit 130 to the outside (e.g., other communication devices) via the communication unit 110 through a wireless / wired interface, or store information received from the outside (e.g., other communication devices) via the communication unit 110 through a wireless / wired interface in the memory unit 130.

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

[0680] exist Fig.30 In the wireless devices 100 and 200, all of the various elements, components, units / parts and / or modules in the wireless devices 100 and 200 may be connected to each other through a wired interface, or at least a part thereof may be connected wirelessly through the communication unit 110. For example, in each of the wireless devices 100 and 200, the control unit 120 and the communication unit 110 may be connected through a wire and the control unit 120 and the first unit (e.g., 130 and 140) may be connected wirelessly through the communication unit 110. Each element, component, unit / part and / or module 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 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.

[0681] Hereinafter, the implementation will be described in detail with reference to the accompanying drawings. Fig.30 .

[0682] 4.2.3. Examples of portable devices to which various embodiments of the present disclosure are applied

[0683] Fig.31 An exemplary portable device to which various embodiments of the present disclosure are applied is illustrated. The portable device may be any one of a smart phone, a smart board, a wearable device (e.g., a smart watch 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).

[0684] refer to Fig.31, 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 Fig.30 Blocks 110 to 130 / 140.

[0685] The communication unit 110 may send signals (e.g., data and control signals) to other wireless devices or BSs and receive signals (e.g., data and control signals) from other wireless devices or BSs. The control unit 120 may perform various operations by controlling the constituent elements of the handheld device 100. The control unit 120 may include an application processor (AP). The memory unit 130 may store data / parameters / programs / codes / commands required to drive the handheld device 100. The memory unit 130 may store input / output data / information. The power supply unit 140a may supply power to the handheld device 100 and include a wired / wireless charging circuit, a battery, etc. The interface unit 140b may support the connection of the handheld device 100 to other external devices. The interface unit 140b may include various ports (e.g., audio I / O ports and video I / O ports) for connecting to external devices. The I / O unit 140c may input or output video information / signals, audio information / signals, data and / or information input by a 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.

[0686] As an example, in the case of data communication, the I / O unit 140c may acquire information / signals (e.g., touch, text, voice, image, or video) input by a user and may store the acquired information / signals in the memory unit 130. The communication unit 110 may convert the information / signals stored in the memory into radio signals and transmit the converted radio signals directly to other wireless devices or to a BS. The communication unit 110 may 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 may be stored in the memory unit 130 and may be output as various types (e.g., text, voice, image, video, or tactile) through the I / O unit 140c.

[0687] 4.2.4. Examples of vehicles or autonomous driving vehicles to which various embodiments of the present disclosure are applied

[0688] Fig.32An 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.

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

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

[0691] For example, the communication unit 110 can receive map data, traffic information data, etc. from an external server. The autonomous driving unit 140d can generate an autonomous driving path and a driving plan from the obtained data. The control unit 120 can control the drive unit 140a so that the vehicle or the autonomous driving vehicle 100 can move along the autonomous driving path according to the driving plan (e.g., speed / direction control). In the autonomous driving, the communication unit 110 can aperiodically / periodically obtain the latest traffic information data from the external server and obtain surrounding traffic information data from neighboring vehicles. In the autonomous driving, the sensor unit 140c can obtain vehicle status and / or surrounding environment information. The autonomous driving unit 140d can update the autonomous driving path and driving plan based on the re-acquired data / information. The communication unit 110 can transfer information about the vehicle position, autonomous driving path and / or driving plan to an external server. The external server can 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.

[0692] In summary, various embodiments of the present disclosure may be implemented through a certain device and / or UE.

[0693] For example, a device may be a BS, a network node, a transmitting 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.

[0694] For example, the UE may be any of the following: 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.

[0695] A smart phone refers to a terminal that has the advantages of both a mobile communication terminal and a PDA, which is achieved by integrating the functions of a PDA such as scheduling, fax transmission and reception, and data communication functions of Internet connection in a mobile communication terminal. In addition, an MM-MB terminal refers to a terminal that has a built-in multi-modem chip and can therefore operate in all portable Internet systems and other mobile communication systems (e.g., CDMA 2000, WCDMA, etc.).

[0696] Alternatively, the UE may be any of the following: 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 such as a smart watch, smart glasses, and a head-mounted display (HMD). For example, a UAV may be an unmanned aerial vehicle that flies under the control of a wireless control signal. For example, an HMD may be a display device worn around the head. For example, an HMD may be used to implement AR or VR.

[0697] The wireless communication technology for implementing the various embodiments of the present disclosure may include narrowband Internet of Things for low power communication as well as LTE, NR and 6G. In this case, for example, NB-IoT technology may be an example of low power wide area network (LPWAN) technology and may be implemented as a standard such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the names described above. 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 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 is not limited to the aforementioned terms. Additionally or alternatively, considering low-power communication, 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), 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 as various terms.

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

[0699] In hardware configuration, the method according to the exemplary embodiments 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.

[0700] In a firmware or software configuration, the method according to various embodiments of the present disclosure may be implemented in the form of a module, a process, a function, etc. that performs the above 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 is located inside or outside the processor and may send and receive data to and from the processor via various known means.

[0701] Those skilled in the art will appreciate that, without departing from the spirit and essential characteristics of the various embodiments of the present disclosure, the various embodiments of the present disclosure may be performed in other specific ways than those set forth herein. The above embodiments are therefore to be interpreted in all respects as illustrative and not restrictive. The scope of the present disclosure should be determined by the appended claims and their legal equivalents, rather than by the above description, and all changes falling within the meaning and equivalent range of the appended claims are intended to be included 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 in combination as embodiments of the present disclosure, or may be included as new claims by subsequent amendments after the filing of this application.

[0702] Industrial Applicability

[0703] 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, various embodiments of the present disclosure are also applicable to all technical fields in which wireless access systems find their applications. In addition, the proposed method can also be applied to millimeter wave communications using ultra-high frequency bands.

Claims

1. A method performed by a user equipment UE in a wireless communication system, the method comprising: Receiving information related to a physical uplink shared channel PUSCH configuration of a message A related to a random access procedure; Sending the message A; as well as In response to the message A, receiving a message B related to the random access procedure, wherein a PRACH preamble among a plurality of physical random access channel PRACH preambles used for the random access procedure is included in the message A, The multiple PRACH preambles include: (i) at least one first PRACH preamble which is mapped to at least one valid PUSCH opportunity among a plurality of valid PUSCH opportunities, and (ii) at least one second PRACH preamble that is not mapped to any of the plurality of valid PUSCH opportunities, wherein, based on the message A including the PRACH preamble in the at least one first PRACH preamble, the message A includes the PUSCH, wherein a PRACH preamble in the at least one second PRACH preamble is available to be transmitted, wherein, based on the PUSCH configuration, the PUSCH is sent, and Wherein, based on the information related to the demodulation reference signal DM-RS code division multiplexing CDM group configured for the PUSCH, at least one DM-RS CDM group for the PUSCH is configured among two pre-configured groups.

2. The method according to claim 1, wherein: based on the PUSCH configuration including the information related to the DM-RS CDM group, the information related to the DM-RS CDM group indicating which of the two pre-configured groups is used for at least one DM-RS CDM group of the PUSCH, and Based on the fact that the PUSCH configuration does not include information related to the DM-RS CDM group, the at least one DM-RS CDM group for the PUSCH is configured as the two predetermined groups.

3. The method according to claim 1, wherein: The number of ports used for the DM-RS is determined in the set of {1, 2, 4}.

4. The method according to claim 1, wherein: Based on the transform precoding for the PUSCH being disabled, two different identifiers ID are obtained based on two different higher layer parameters, respectively, the two different IDs are related to identifying a sequence for initializing a pseudo-random sequence generator associated with sequence generation of the DM-RS, and Wherein, based on the PRACH preamble, a scrambling ID SCID related to an index for identifying the two different IDs is determined.

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

6. The method according to claim 4, wherein: obtaining the PRACH preamble from among a plurality of PRACH preambles, and The SCID is determined based on a mapping between the multiple preambles and valid PUSCH opportunities for sending the PUSCH.

7. An apparatus configured to operate in a wireless communication system, the apparatus comprising: Memory; and at least one processor connected to the memory, Wherein, the at least one processor is configured to: Receiving information related to a physical uplink shared channel PUSCH configuration of a message A related to a random access procedure; sending the message A; and In response to the message A, receiving a message B related to the random access procedure, wherein a PRACH preamble among a plurality of physical random access channel PRACH preambles used for the random access procedure is included in the message A, The multiple PRACH preambles include: (i) at least one first PRACH preamble which is mapped to at least one valid PUSCH opportunity among a plurality of valid PUSCH opportunities, and (ii) at least one second PRACH preamble that is not mapped to any of the plurality of valid PUSCH opportunities, wherein, based on the message A including the PRACH preamble in the at least one first PRACH preamble, the message A includes the PUSCH, wherein a PRACH preamble in the at least one second PRACH preamble is available to be transmitted, wherein, based on the PUSCH configuration, the PUSCH is sent, and Wherein, based on the information related to the demodulation reference signal DM-RS code division multiplexing CDM group configured for the PUSCH, at least one DM-RS CDM group for the PUSCH is configured among two pre-configured groups.

8. The device according to claim 7, wherein: based on the PUSCH configuration including the information related to the DM-RS CDM group, the information related to the DM-RS CDM group indicating which of the two pre-configured groups is used for at least one DM-RS CDM group of the PUSCH, and Based on the fact that the PUSCH configuration does not include information related to the DM-RS CDM group, the at least one DM-RS CDM group for the PUSCH is configured as the two predetermined groups.

9. The device according to claim 7, wherein: The number of ports used for the DM-RS is determined in the set of {1, 2, 4}.

10. The device according to claim 7, wherein: Based on the transform precoding for the PUSCH being disabled, two different identifiers ID are obtained based on two different higher layer parameters, respectively, the two different IDs are related to identifying a sequence for initializing a pseudo-random sequence generator associated with sequence generation of the DM-RS, and Wherein, based on the PRACH preamble, a scrambling ID SCID related to an index for identifying the two different IDs is determined.

11. The device according to claim 7, 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.

12. A method performed by a base station BS in a wireless communication system, the method comprising: Sending information related to the physical uplink shared channel PUSCH configuration of message A related to the random access procedure; Receiving the message A; as well as In response to the message A, sending a message B related to the random access procedure, wherein a PRACH preamble among a plurality of physical random access channel PRACH preambles used for the random access procedure is included in the message A, The multiple PRACH preambles include: (i) at least one first PRACH preamble which is mapped to at least one valid PUSCH opportunity among a plurality of valid PUSCH opportunities, and (ii) at least one second PRACH preamble that is not mapped to any of the plurality of valid PUSCH opportunities, wherein, based on the message A including the PRACH preamble in the at least one first PRACH preamble, the message A includes the PUSCH, wherein a PRACH preamble in the at least one second PRACH preamble is available for reception, wherein, based on the PUSCH configuration, the PUSCH is received, and Wherein, based on the information related to the demodulation reference signal DM-RS code division multiplexing CDM group configured for the PUSCH, at least one DM-RS CDM group for the PUSCH is configured among two pre-configured groups.

13. An apparatus configured to operate in a wireless communication system, the apparatus comprising: Memory; and at least one processor connected to the memory, Wherein, the at least one processor is configured to: Sending information related to the physical uplink shared channel PUSCH configuration of message A related to the random access procedure; receiving the message A; and In response to the message A, sending a message B related to the random access procedure, wherein a PRACH preamble among a plurality of physical random access channel PRACH preambles used for the random access procedure is included in the message A, The multiple PRACH preambles include: (i) at least one first PRACH preamble which is mapped to at least one valid Physical Uplink Shared Channel (PUSCH) opportunity among a plurality of valid PUSCH opportunities, and (ii) at least one second PRACH preamble that is not mapped to any of the plurality of valid PUSCH opportunities, wherein, based on the message A including the PRACH preamble in the at least one first PRACH preamble, the message A includes the PUSCH, wherein a PRACH preamble in the at least one second PRACH preamble is available for reception, wherein, based on the PUSCH configuration, the PUSCH is received, and Wherein, based on the information related to the demodulation reference signal DM-RS code division multiplexing CDM group configured for the PUSCH, at least one DM-RS CDM group for the PUSCH is configured among two pre-configured groups.

14. An apparatus configured to operate in a wireless communication system, the apparatus comprising: at least one processor; and at least one memory configured to store one or more instructions, the instructions causing the at least one processor to perform a method comprising: Receiving information related to a physical uplink shared channel PUSCH configuration of a message A related to a random access procedure; sending the message A; and In response to the message A, receiving a message B related to the random access procedure, wherein a PRACH preamble among a plurality of physical random access channel PRACH preambles used for the random access procedure is included in the message A, The multiple PRACH preambles include: (i) at least one first PRACH preamble which is mapped to at least one valid PUSCH opportunity among a plurality of valid PUSCH opportunities, and (ii) at least one second PRACH preamble that is not mapped to any of the plurality of valid PUSCH opportunities, wherein, based on the message A including the PRACH preamble in the at least one first PRACH preamble, the message A includes the PUSCH, wherein a PRACH preamble in the at least one second PRACH preamble is available to be transmitted, wherein, based on the PUSCH configuration, the PUSCH is sent, and Wherein, based on the information related to the demodulation reference signal DM-RS code division multiplexing CDM group configured for the PUSCH, at least one DM-RS CDM group for the PUSCH is configured among two pre-configured groups.

15. A processor-readable medium configured to store one or more instructions that cause at least one processor to perform a method comprising: Receiving information related to a physical uplink shared channel PUSCH configuration of a message A related to a random access procedure; Sending the message A; as well as In response to the message A, receiving a message B related to the random access procedure, The multiple physical random access channel PRACH preambles used for the random access process include: (i) at least one first PRACH preamble which is mapped to at least one valid PUSCH opportunity among a plurality of valid PUSCH opportunities, and (ii) at least one second PRACH preamble that is not mapped to any of the plurality of valid PUSCH opportunities, wherein, based on the message A including the PRACH preamble in the at least one first PRACH preamble, the message A includes the PUSCH, wherein a PRACH preamble in the at least one second PRACH preamble is available to be transmitted, wherein, based on the PUSCH configuration, the PUSCH is sent, and Wherein, based on the information related to the demodulation reference signal DM-RS code division multiplexing CDM group configured for the PUSCH, at least one DM-RS CDM group for the PUSCH is configured among two pre-configured groups.

Images