METHOD FOR TRANSMITTING AND RECEIVING SIGNAL IN WIRELESS COMMUNICATION SYSTEM AND APPARATUS SUPPORTING THE SAME
The two-step RACH procedure optimizes signal transmission and reception in wireless communication systems by efficiently mapping PRACH preambles to PUSCH opportunities, addressing inefficiencies in existing systems and reducing latency.
Patent Information
- Application Number
- JP2022520607
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2019-11-08
- Filing Date
- 2020-10-05
- Publication Date
- 2024-11-12
- Estimated Expiration
- 2040-10-05
AI Technical Summary
Existing wireless communication systems face inefficiencies in signal transmission and reception, particularly in the context of random access procedures, which can lead to increased latency and resource wastage.
A method and apparatus for a two-step RACH procedure in wireless communication systems, involving the generation of a PRACH preamble within valid PRACH occasions, mapping preambles to PUSCH opportunities, and optimizing the use of DMRS resources to enhance signal transmission efficiency.
This approach allows for more efficient use of resources and reduced latency in signal transmission and reception, particularly in scenarios involving multiple access systems like CDMA, FDMA, TDMA, and OFDMA.
Smart Images

Figure 0007581339000029 
Figure 0007581339000030 
Figure 0007581339000031
Abstract
Description
[Technical field]
[0001] Various embodiments relate to wireless communication systems. [Background technology]
[0002] Wireless access systems have been widely deployed to provide various communication services such as voice and data. In general, wireless access systems are multiple access systems that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of 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, single carrier frequency division multiple access (SC-FDMA) systems, etc. Summary of the Invention [Problem to be solved by the invention]
[0003] Various embodiments provide methods and apparatus supporting same for transmitting and receiving signals in a wireless communication system.
[0004] Various embodiments provide a method and apparatus for supporting a two-step RACH procedure in a wireless communication system.
[0005] Various embodiments provide a method and apparatus for supporting a Message A PUSCH DMRS configuration method in a wireless communication system.
[0006] Various embodiments provide a method and apparatus for supporting mapping of preambles to PUSCH opportunities in a wireless communication system.
[0007] The technical objectives to be achieved by the present invention are not limited to those mentioned above, and other technical problems not mentioned may be considered by a person having ordinary skill in the art to which the present invention pertains from the embodiments of the present invention described below. [Means for solving the problem]
[0008] Various embodiments provide methods and apparatus supporting same for transmitting and receiving signals in a wireless communication system.
[0009] According to various embodiments, a method is provided for a terminal in a wireless communication system.
[0010] According to various embodiments, the method includes: transmitting a physical random access channel (PRACH) preamble within any valid PRACH opportunity among a plurality of valid PRACH opportunities within a PRACH slot; and obtaining information related to a random access response (RAR) in response to the PRACH preamble.
[0011] According to various embodiments, the PRACH preamble is included in multiple PRACH preambles associated with multiple valid PRACH opportunities.
[0012] According to various embodiments, the multiple PRACH preambles are mapped to a first physical uplink shared channel (PUSCH) opportunity among the multiple PRACH preambles, based on which multiple consecutive PRACH preambles included in the multiple PRACH preambles are mapped to one valid PUSCH opportunity.
[0013] According to various embodiments, a PUSCH associated with a random access procedure is transmitted during one of the first PUSCH opportunities.
[0014] According to various embodiments, the second PUSCH opportunities remaining from the plurality of available PUSCH opportunities, other than the first PUSCH opportunity, are not used for transmitting PUSCH associated with the voluntary access procedure.
[0015] According to various embodiments, among the multiple PUSCH opportunities, the multiple valid PUSCH opportunities are determined to be PUSCH opportunities that (i) are included in an uplink (UL) symbol or (ii) begin at least N symbols after the last downlink (DL) symbol, where N is an integer greater than or equal to 0.
[0016] According to various embodiments, a PRACH preamble that is not included in the plurality of PRACH preambles may be transmitted on a valid PRACH opportunity associated with a PRACH preamble that is not included in the plurality of PRACH preambles based on the valid PRACH opportunity associated with a PRACH preamble that is not included in the plurality of PRACH preambles not being mapped to a PUSCH opportunity.
[0017] According to various embodiments, the number of consecutive PRACH preambles is determined based on the number of PRACH preambles and the number of available PUSCH opportunities.
[0018] According to various embodiments, the number of the plurality of PRACH preambles is the number of the plurality of PRACH preambles included within the first time interval.
[0019] According to various embodiments, the number of valid PUSCH opportunities is the number of valid PUSCH opportunities contained within the second time interval.
[0020] According to various embodiments, each of the first time interval and the second time interval is the same time interval.
[0021] According to various embodiments, an apparatus is provided for operating in a wireless communication system.
[0022] According to various embodiments, the apparatus includes a memory; and one or more processors coupled to the memory.
[0023] According to various embodiments, the one or more processors may: transmit a PRACH preamble within any valid PRACH opportunity among a plurality of valid PRACH opportunities within a PRACH slot; and obtain information related to a random access response (RAR) in response to the PRACH preamble.
[0024] According to various embodiments, the PRACH preamble is included in multiple PRACH preambles associated with multiple valid PRACH opportunities.
[0025] According to various embodiments, the multiple PRACH preambles are mapped to a first physical uplink shared channel (PUSCH) opportunity among the multiple PRACH preambles, based on which multiple consecutive PRACH preambles included in the multiple PRACH preambles are mapped to one valid PUSCH opportunity.
[0026] According to various embodiments, a PUSCH associated with a random access procedure is transmitted during one of the first PUSCH opportunities.
[0027] According to various embodiments, the second PUSCH opportunities remaining from the plurality of available PUSCH opportunities, other than the first PUSCH opportunity, are not used for transmitting PUSCH associated with the voluntary access procedure.
[0028] According to various embodiments, among the multiple PUSCH opportunities, the multiple valid PUSCH opportunities are determined to be PUSCH opportunities that (i) are included in an uplink (UL) symbol or (ii) begin at least N symbols after the last downlink (DL) symbol, where N is an integer greater than or equal to 0.
[0029] According to various embodiments, a PRACH preamble that is not included in the plurality of PRACH preambles may be transmitted on a valid PRACH opportunity associated with a PRACH preamble that is not included in the plurality of PRACH preambles based on the valid PRACH opportunity associated with a PRACH preamble that is not included in the plurality of PRACH preambles not being mapped to a PUSCH opportunity.
[0030] According to various embodiments, the device communicates with any of a mobile terminal, a network, and an autonomous vehicle other than the vehicle in which the device is included.
[0031] According to various embodiments, a method is provided that is performed by a base station in a wireless communication system.
[0032] According to various embodiments, the method includes receiving a physical random access channel (PRACH) preamble within any valid PRACH opportunity among a plurality of valid PRACH opportunities within a PRACH slot; and transmitting information related to a random access response (RAR) in response to the PRACH preamble.
[0033] According to various embodiments, the PRACH preamble is included in multiple PRACH preambles associated with multiple valid PRACH opportunities.
[0034] According to various embodiments, the multiple PRACH preambles are mapped to a first physical uplink shared channel (PUSCH) opportunity among the multiple PRACH preambles, based on which multiple consecutive PRACH preambles included in the multiple PRACH preambles are mapped to one valid PUSCH opportunity.
[0035] According to various embodiments, an apparatus is provided for operating in a wireless communication system.
[0036] According to various embodiments, the apparatus includes a memory and one or more processors coupled to the memory.
[0037] According to various embodiments, the one or more processors receive a physical random access channel (PRACH) preamble within any valid PRACH opportunity among a plurality of valid PRACH opportunities within a PRACH slot, and transmit information related to a random access response (RAR) in response to the PRACH preamble.
[0038] According to various embodiments, the PRACH preamble is included in multiple PRACH preambles associated with multiple valid PRACH opportunities.
[0039] According to various embodiments, the multiple PRACH preambles are mapped to a first physical uplink shared channel (PUSCH) opportunity among the multiple PRACH preambles, based on which multiple consecutive PRACH preambles included in the multiple PRACH preambles are mapped to one valid PUSCH opportunity.
[0040] According to various embodiments, an apparatus is provided for operating in a wireless communication system.
[0041] According to various embodiments, the apparatus includes one or more processors and one or more memories that store one or more instructions that cause the one or more processors to perform a method.
[0042] According to various embodiments, the method includes transmitting a physical random access channel (PRACH) preamble within any valid PRACH opportunity among a plurality of valid PRACH opportunities within a PRACH slot, and obtaining information related to a random access response (RAR) in response to the PRACH preamble.
[0043] According to various embodiments, the PRACH preamble is included in multiple PRACH preambles associated with multiple valid PRACH opportunities.
[0044] According to various embodiments, the multiple PRACH preambles are mapped to a first physical uplink shared channel (PUSCH) opportunity among the multiple PRACH preambles, based on which multiple consecutive PRACH preambles included in the multiple PRACH preambles are mapped to one valid PUSCH opportunity.
[0045] According to various embodiments, a processor-readable medium is provided that stores one or more instructions that cause one or more processors to perform a method.
[0046] According to various embodiments, the method includes transmitting a physical random access channel (PRACH) preamble within any valid PRACH opportunity among a plurality of valid PRACH opportunities within a PRACH slot, and obtaining information related to a random access response (RAR) in response to the PRACH preamble.
[0047] According to various embodiments, the PRACH preamble is included in multiple PRACH preambles associated with multiple valid PRACH opportunities.
[0048] According to various embodiments, the multiple PRACH preambles are mapped to a first physical uplink shared channel (PUSCH) opportunity among the multiple PRACH preambles, based on which multiple consecutive PRACH preambles included in the multiple PRACH preambles are mapped to one valid PUSCH opportunity.
[0049] The various embodiments described above are merely some of the preferred embodiments of this disclosure, and various embodiments reflecting the technical features of the various embodiments can be derived and understood by those having ordinary skill in the art based on the following detailed description. Effect of the Invention
[0050] Various embodiments allow for efficient transmission and reception of signals in a wireless communication system.
[0051] According to various embodiments, resources (eg, DMRS ports / sequences) of the Message A PUSCH DMRS may be used efficiently.
[0052] According to various embodiments, the preamble can be used efficiently.
[0053] The effects obtained from the various embodiments are not limited to those mentioned above, and other effects not mentioned will be clearly derived and understood by those having ordinary skill in the art to which the present invention pertains from the following description of the embodiments of the present invention. [Brief description of the drawings]
[0054] The drawings attached below are for aiding understanding of the present invention, and together with the detailed description provide examples of the present invention. However, the technical features of the present invention are not limited to specific drawings, and the features disclosed in each drawing may be combined with each other to form a new embodiment. Reference numerals in each drawing refer to structural elements.
[0055] [Figure 1] FIG. 2 illustrates physical channels that can be used in various embodiments and how they are used to transmit signals. [Diagram 2] FIG. 1 illustrates a radio frame structure based on an NR system to which various embodiments can be applied. [Diagram 3] FIG. 1 illustrates a slot structure based on an NR system to which various embodiments are applicable. [Figure 4] FIG. 1 illustrates an example of mapping physical channels into slots to which various embodiments are applicable. [Diagram 5] FIG. 1 is a diagram showing the structure of a Synchronization Signal Block (SSB) to which various embodiments can be applied. [Figure 6] FIG. 2 is a diagram showing an example of an SSB transmission method to which various embodiments can be applied. [Figure 7] FIG. 2 illustrates an example of a method for a terminal to which various embodiments can be applied to obtain information regarding DL time synchronization. [Figure 8] FIG. 2 illustrates an example of a system information (SI) acquisition process to which various embodiments can be applied. [Figure 9] FIG. 1 illustrates an example of multi-beam transmission to which various embodiments can be applied. [Figure 10] FIG. 13 illustrates an example of a method for indicating an actually transmitted SSB (SSB_tx) to which various embodiments are applicable. [Figure 11] FIG. 2 illustrates an example of a 4-step RACH procedure to which various embodiments can be applied. [Figure 12] FIG. 2 illustrates an example of a 2-step RACH procedure to which various embodiments can be applied. [Figure 13] FIG. 1 illustrates an example of a contention-free RACH procedure to which various embodiments can be applied. [Figure 14] FIG. 2 illustrates an example of SS block transmission and PRACH resources linked to SS blocks according to various embodiments. [Figure 15] FIG. 2 illustrates an example of SS block transmission and PRACH resources linked to SS blocks according to various embodiments. [Figure 16] FIG. 2 illustrates an example of a RACH opportunity configuration to which various embodiments are applicable. [Figure 17] FIG. 2 is a simplified diagram illustrating a method of operation of a terminal and a base station in accordance with various embodiments. [Figure 18] FIG. 2 is a simplified diagram illustrating a method of operation of a terminal according to various embodiments. [Figure 19] FIG. 2 is a simplified diagram illustrating a method of operation of a base station according to various embodiments. [Figure 20] FIG. 2 illustrates an example of resource configuration for message A according to various embodiments. [Figure 21] FIG. 1 illustrates an example of a Message A configuration according to various embodiments. [Figure 22] FIG. 1 illustrates an example of a Message A configuration according to various embodiments. [Diagram 23] FIG. 2 illustrates an example of time domain locations for message A RACH and message A PUSCH in accordance with various embodiments. [Figure 24] FIG. 2 is a simplified diagram illustrating the process of initial network connection and subsequent communication in accordance with various embodiments. [Diagram 25]FIG. 2 is a simplified diagram illustrating a method of operation of a terminal and a base station in accordance with various embodiments. [Figure 26] 4 is a flow chart illustrating a method of operating a terminal in accordance with various embodiments. [Figure 27] 5 is a flow chart illustrating a method of operating a base station in accordance with various embodiments. [Figure 28] FIG. 1 illustrates an apparatus in which various embodiments may be implemented. [Figure 29] FIG. 1 illustrates a communication system for use in various embodiments. [Diagram 30] FIG. 1 illustrates a wireless device for use in various embodiments. [Diagram 31] FIG. 1 illustrates another example of a wireless device for use in various embodiments. [Diagram 32] FIG. 1 illustrates a portable device for use in various embodiments. [Diagram 33] 1 illustrates a vehicle or an autonomous vehicle that may be used in accordance with various embodiments. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0056] The following technologies can be used for various wireless access systems, such as CDMA, FDMA, TDMA, OFDMA, SC-FDMA, etc. CDMA is implemented by radio technologies such as Universal Terrestrial Radio Access (UTRA) and CDMA2000. TDMA is implemented by radio technologies such as Global System for Mobile communications (GSM) / General Packet Radio Service (GPRS) / Enhanced Data Rates for GSM Evolution (EDGE). OFDMA is implemented by radio technologies such as IEEE802.11 (Wi-Fi), IEEE802.16 (WiMAX), IEEE802-20, Evolved UTRA (E-UTRA), etc. UTRA is part of the Universal Mobile Telecommunications System (UMTS). 3GPP (3rd Generation Partnership Project) LTE (long term evolution) is a part of E-UMTS (Evolved UMTS) that uses E-UTRA, and LTE-A (Advanced) / LTE-A pro is an evolution of 3GPP LTE. 3GPP NR (New Radio or New Radio Access Technology) is an evolution of 3GPP LTE / LTE-A / LTE-A pro.
[0057] For a clearer description, various embodiments are described based on a 3GPP (registered trademark) communication system (including, for example, LTE, NR, 6G, and next-generation wireless communication systems), but the technical ideas of various embodiments are not limited thereto. For background techniques, terms, abbreviations, etc. used in the description of various embodiments, reference may be made to matters described in standard documents published prior to the present invention. For example, reference may be made to documents such as 3GPP TS37.213, 3GPP TS38.211, 3GPP TS38.212, 3GPP TS38.213, 3GPP TS38.214, 3GPP TS38.215, 3GPP TS38.300, 3GPP TS38.321, and 3GPP TS38.331.
[0058] 1.3 GPP System
[0059] 1.1. Physical Channels and Signal Transmission / Reception
[0060] In a wireless access system, a terminal receives information from a base station through a downlink (DL) and transmits information to the base station through an uplink (UL). Information transmitted and received between the base station and the terminal includes general data information and various control information, and various physical channels exist depending on the type / purpose of the information transmitted and received.
[0061] FIG. 1 is a diagram illustrating physical channels that may be used in various embodiments and the manner in which signals are transmitted using them.
[0062] When a terminal is turned on after being turned off or when the terminal newly enters a cell, the terminal performs an initial cell search such as synchronizing with the base station (S11). To do this, the terminal receives a primary synchronization channel (P-SCH) and a secondary synchronization channel (S-SCH) from the base station to synchronize with the base station and obtain information such as a cell ID.
[0063] Thereafter, the terminal receives a physical broadcast channel (PBCH) signal from the base station to obtain intra-cell broadcast information.
[0064] Meanwhile, in the initial cell search stage, the UE receives a downlink reference signal (DL RS) to check the downlink channel state.
[0065] After completing the initial cell search, the terminal receives a physical downlink control channel (PDCCH) and a physical downlink shared channel (PDSCH) corresponding to the physical downlink control channel information to obtain more specific system information (S12).
[0066] Thereafter, the terminal performs a random access procedure to complete connection to the base station (S13 to S16). To this end, the terminal transmits a preamble on a physical random access channel (PRACH) (S13) and receives a random access response (RAR) for the preamble on a physical downlink control channel and a corresponding physical downlink shared channel (S14). The terminal transmits a physical uplink shared channel (PUSCH) using scheduling information in the RAR (S15) and performs a contention resolution procedure such as receiving a physical downlink control channel signal and a corresponding physical downlink shared channel signal (S16).
[0067] When the voluntary access procedure is performed in two stages, S13 / S15 is performed by a single operation in which the terminal performs transmission, and S14 / S16 is performed by a single operation in which the base station performs transmission.
[0068] After performing the above-mentioned procedure, the terminal then receives a physical downlink control channel signal and / or a physical downlink shared channel signal (S17) and transmits a physical uplink shared channel (PUSCH) signal and / or a physical uplink control channel (PUCCH) signal (S18) as a general uplink / downlink signal transmission procedure.
[0069] The control information that a terminal transmits to a base station is collectively called uplink control information (UCI). UCI includes hybrid automatic repeat and reQuest acknowledgement / negative-ACK (HARQ-ACK / NACK), scheduling request (SR), channel quality indication (CQI), precoding matrix indication (PMI), and rank indication (RI).
[0070] UCI is generally transmitted periodically on the PUCCH, but may be transmitted on the PUSCH if control information and traffic data are to be transmitted simultaneously. UCI may also be transmitted aperiodically on the PUSCH upon request / instruction from the network.
[0071] 1.2. Radio Frame Structure
[0072] FIG. 2 is a diagram illustrating a radio frame structure based on an NR system to which various embodiments can be applied.
[0073] The NR system supports multiple numerologies. Here, the numerology is defined by the subcarrier spacing (SCS) and the cyclic prefix (CP) overhead. In this case, multiple subcarrier spacing is derived by scaling the basic subcarrier spacing to an integer N (or μ). Also, assuming that very low subcarrier spacing is not used at very high carrier frequencies, the numerology used can be selected independently of the frequency band of the cell. In addition, the NR system supports various frame structures with multiple numerologies.
[0074] Hereinafter, the orthogonal frequency division multiplexing (OFDM) neurology and frame structure considered in the NR system will be described. A number of OFDM neurology supported in the NR system can be defined as shown in Table 1. μ and CP (Cyclic Prefix) for the bandwidth part are obtained from the RRC parameters provided by the BS.
[0075] [Table 1]
[0076] NR supports multiple neurologies (e.g., subcarrier spacing) to support various 5G services. For example, a subcarrier spacing of 15 kHz supports wide areas in traditional cellular bands, a subcarrier spacing of 30 kHz / 60 kHz supports dense urban areas, lower latency and wider carrier bandwidth, and a subcarrier spacing of 60 kHz or higher supports bandwidths larger than 24.25 GHz to overcome phase noise.
[0077] The NR frequency band is defined by two types of frequency ranges: FR1 and FR2. FR1 is the sub 6GHz range, and FR2 is the above 6GHz range, which stands for millimeter wave (mmWave).
[0078] Table 2 below illustrates the definitions of the NR frequency bands.
[0079] [Table 2]
[0080] With respect to the frame structure in the NR system, the size of the various fields in the time domain is determined by the basic time unit for NR, T c =1 / (△f max *N f ) where △f max =480*10 3 N is a number in Hz related to the size of the fast Fourier transform (FFT) or inverse fast Fourier transform (IFFT). f = 4096. c is the LTE base time unit, and T s = 1 / ((15kHz)*2048) and has the following relationship: T s / T c = 64. Downlink and uplink transmission is T f =(△f max *N f / 100)*T c = 10 ms duration, where each radio frame is T sf =(△f max *N f / 1000)*T c= 1 ms duration. There is one set of frames for the uplink and one set of frames for the downlink. For pneumatics μ, the slots are arranged in increasing order within a subframe. μ s ∈{0,…,N slot,μ subframe -1}, and within a radio frame, μ s,f ∈{0,…,N slot,μ frame -1}. 1 slot is numbered as N μ symb It consists of N consecutive OFDM symbols. μ symb depends on the cyclic prefix (CP). μ s The start of OFDM symbol n μ s *N μ symb is time-aligned with the start of
[0081] Table 3 shows the number of symbols per slot, the number of slots per frame, and the number of slots per subframe according to the SCS when the general CP is used, and Table 4 shows the number of symbols per slot, the number of slots per frame, and the number of slots per subframe according to the SCS when the extended CSP is used.
[0082] [Table 3]
[0083] [Table 4]
[0084] In the above table, N slot symb denotes the number of symbols in a slot, and N frame,μslot denotes the number of slots in the frame, and N subframe,μ slot indicates the number of slots in a subframe.
[0085] In an NR system to which various embodiments can be applied, different OFDM(A) neurology (e.g., SCS, CP length, etc.) are set between multiple cells merged into one terminal, so that the (absolute time) duration of time resources (e.g., SF, slot, or TTI) (collectively referred to as TU (Time Unit) for convenience) consisting of the same number of symbols differs between the merged cells.
[0086] FIG 2 is an example when μ=2 (i.e., subcarrier spacing is 60 kHz), and one subframe includes four slots according to Table 3. One subframe={1,2,4} slots shown in FIG 2 is an example, and the number of slots included in one subframe can be defined as shown in Table 6 or Table 7.
[0087] A minislot may also contain 2, 4 or 7 symbols, or it may contain more or less symbols.
[0088] FIG. 3 illustrates a slot structure based on an NR system to which various embodiments can be applied.
[0089] 3, one slot includes a number of symbols in the time domain, for example, in the case of the general CP, one slot includes seven symbols, whereas in the case of the extended CP, one slot includes six symbols.
[0090] A carrier includes multiple subcarriers in the frequency domain. A resource block (RB) is defined by multiple (e.g., 12) consecutive subcarriers in the frequency domain.
[0091] A BWP (Bandwidth Part) is defined by multiple consecutive (P)RBs in the frequency domain and corresponds to one neurology (e.g., SCS, CP length, etc.).
[0092] A carrier wave includes up to N (e.g., 5) BWPs. Data communication is performed by the activated BWPs, and only one BWP can be activated for one terminal. Each element in the resource grid is called a resource element (RE), and one complex symbol can be mapped to it.
[0093] FIG. 4 shows an example of mapping of physical channels into slots to which various embodiments are applicable.
[0094] A DL control channel, DL or UL data, and a UL control channel are all included in one slot. For example, the first N symbols in a slot are used to transmit the DL control channel (hereinafter, DL control region), and the last M symbols in the slot are used to transmit the UL control channel (hereinafter, UL control region). N and M are integers equal to or greater than 0. The resource region between the DL control region and the UL control region (hereinafter, data region) is used for DL data transmission or UL data transmission. There is a time gap between the control region and the data region for DL-to-UL or UL-to-DL switching. The PDCCH is transmitted in the DL control region, and the PDSCH is transmitted in the DL data region. Some symbols at the time of switching from DL to UL within a slot are used as the time gap.
[0095] 1.3.Channel Structure
[0096] 1.3.1. Downlink Channel Structure
[0097] The base station transmits relevant signals to the terminal via a downlink channel, which will be described later, and the terminal receives relevant signals from the base station via a downlink channel, which will be described later.
[0098] 1.3.1.1. Physical Downlink Shared Channel (PDSCH)
[0099] The PDSCH carries downlink data (e.g., DL-shared channel transport block, DL-SCH TB) and uses modulation methods such as QPSK (Quadrature Phase Shift Keying), 16QAM (Quadrature Amplitude Modulation), 64QAM, and 256QAM. The TB is encoded to generate a codeword. The PDSCH can carry up to two codewords. Scrambling and modulation mapping are performed for each codeword, and the modulation symbols generated from each codeword are mapped to one or more layers (layer mapping). Each layer is mapped to resources together with a DMRS (Demodulation Reference Signal) to be generated as an OFDM symbol signal and transmitted through the corresponding antenna port.
[0100] 1.3.1.2. Physical Downlink Control Channel (PDCCH)
[0101] The PDCCH transmits DCI (Downlink Control Information), such as DL data scheduling information, UL data scheduling information, etc. The PUCCH transmits UCI (Uplink Control Information), such as ACK / NACK (Positive Acknowledgement / Negative Acknowledgement) information, CSI (Channel State Information), SR (Scheduling Request), etc., related to DL data.
[0102] PDCCH carries downlink control information (DCI) and uses the QPSK modulation method. One PDCCH consists of 1, 2, 4, 8, or 16 CCEs (Control Channel Elements) depending on the AL (Aggregation Level). One CCE consists of 6 REGs (Resource Element Groups). One REG is defined by one OFDM symbol and one (P)RB.
[0103] The PDCCH is transmitted by a control resource set (CORESET). The CORESET is defined by a set of REGs having a certain neurology (e.g., SCS, CP length, etc.). Multiple OCRESETs for one UE can be overlapped in the time / frequency domain. The CORESET is configured by system information (e.g., MIB) or UE-specific higher layer (e.g., radio resource control, RRC, layer) signaling. Specifically, the number of RBs and the number of symbols (maximum 3) that constitute the CORESET are configured by higher layer signaling.
[0104] The UE obtains DCI transmitted via the PDCCH by performing decoding (so-called blind decoding) on a set of PDCCH candidates. The set of PDCCH candidates decoded by the UE is defined as a PDCCH search space set. The search space set is a common search space or a UE-specific search space. The UE obtains DCI by monitoring PDCCH candidates in one or more search space sets configured by MIB or higher layer signaling.
[0105] Table 5 illustrates the characteristics of each search space type.
[0106] [Table 5]
[0107] Table 6 illustrates an example of a DCI format transmitted via the PDCCH.
[0108] [Table 6]
[0109] DCI format0_0 is used to schedule a TB-based (or TB-level) PUSCH, and DCI format0_1 is used to schedule a TB-based (or TB-level) PUSCH or a Code Block Group (CBG)-based (or CBG-level) PUSCH. DCI format1_0 is used to schedule a TB-based (or TB-level) PDSCH, and DCI format1_1 is used to schedule a TB-based (or TB-level) PDSCH or a CBG-based (or CBG-level) PDSCH. DCI format2_0 is used to deliver dynamic slot format information (e.g., dynamic SFI) to a terminal, and DCI format2_1 is used to deliver downlink pre-emption information to a terminal. DCI format2_0 and / or DCI format2_1 are delivered to terminals in a corresponding group via a group common PDCCH, which is a PDCCH delivered to terminals defined in one group.
[0110] 1.3.2. Uplink Channel Structure
[0111] The terminal transmits related signals to the base station via an uplink channel, which will be described later, and the base station receives related signals from the terminal via an uplink channel, which will be described later.
[0112] 1.3.2.1. Physical Uplink Shared Channel (PUSCH)
[0113] The PUSCH carries uplink data (e.g., UL-shared Channel transport block, UL-SCH TB) and / or uplink control information (UCI) and is transmitted based on a CP-OFDM (Cyclic Prefix-Orthogonal Frequency Division Multiplexing) waveform or a DFT-s-OFDM (Discrete Fourier Transform-spread-Orthogonal Frequency Division Multiplexing) waveform. When the PUSCH is transmitted based on the DFT-s-OFDM waveform, the terminal applies transform precoding to transmit the PUSCH. As an example, when transform precoding is not possible (e.g., transform precoding is disabled), the terminal transmits the PUSCH based on the CP-OFDM waveform, and when transform precoding is possible (e.g., transform precoding is enabled), the terminal transmits the PUSCH based on the CP-OFDM waveform or the DFT-s-OFDM waveform. PUSCH transmissions may be dynamically scheduled by UL grants in the DCI or semi-statically scheduled (configured grant) based on higher layer (e.g., RRC) signaling (and / or Layer 1 (L1) signaling (e.g., PDCCH)). PUSCH transmissions may be codeword-based or non-codeword-based.
[0114] 1.3.2.2. Physical Uplink Control Channel (PUCCH)
[0115] The PUCCH carries uplink control information, HARQ-ACK, and / or a scheduling request (SR), and is classified into a Short PUCCH and a Long PUCCH according to the PUCCH transmission length. Table 7 shows an example of a PUCCH format.
[0116] [Table 7]
[0117] PUCCH format 0 carries UCI with a maximum size of 2 bits and is mapped and transmitted based on a sequence. Specifically, the terminal transmits one of a plurality of sequences to the base station via a PUCCH with PUCCH format 0 to transmit a specific UCI. The terminal transmits a PUCCH with PUCCH format 0 within a PUCCH resource for a corresponding SR setting only when transmitting a positive SR.
[0118] PUCCH format 1 carries UCI with a maximum size of 2 bits, and the modulation symbols are spread in the time domain by an orthogonal cover code (OCC) (set differently depending on whether frequency hopping is used or not). DMRS is transmitted in symbols where no modulation symbols are transmitted (i.e., it is transmitted using TDM (Time Division Multiplexing)).
[0119] PUCCH format 2 carries UCI with a bit size larger than 2 bits, and modulation symbols are transmitted after frequency division multiplexing (FDM) with DMRS. DM-RS is located at symbol indexes #1, #4, #7, and #10 in a 1 / 3 density resource block. A Pseudo Noise (PN) sequence is used for the DM_RS sequence. Frequency hopping can be activated for the 2-symbol PUCCH format 2.
[0120] In PUCCH format 3, terminals are not multiplexed in the same physical resource block, and UCI with a bit size larger than 2 bits is carried. That is, the PUCCH resource of PUCCH format 3 does not include an orthogonal cover code. Modulation symbols are transmitted after being time-division multiplexed with DMRS (Time Division Multiplexing).
[0121] PUCCH format 4 supports multiplexing of up to four terminals in the same physical resource block and carries UCI with a bit size larger than 2 bits. That is, the PUCCH resource of PUCCH format 3 includes an orthogonal cover code. Modulation symbols are transmitted after being time division multiplexed (TDM) with DMRS.
[0122] 1.4.BWP (Bandwidth part)
[0123] In the NR system, each carrier can support up to 400 MHz. If a UE operating on such a wideband carrier always operates with the radio frequency (RF) module for the entire carrier turned on, the UE battery will be consumed. Alternatively, when considering various use cases (e.g., eMBB, URLLC, mMTC, V2X, etc.) operating within one wideband carrier, different neurologies (e.g., subcarrier spacing) are supported for each frequency band within the corresponding carrier. Alternatively, each UE has a different maximum bandwidth capability. In consideration of this, the BS instructs the UE to operate only with a portion of the bandwidth of the wideband carrier rather than the entire bandwidth, and the portion of the bandwidth is called a bandwidth part (BWP). In the frequency domain, a BWP is a subset of contiguous common resource blocks defined for a neurology μi within bandwidth part i on a carrier, for which one neurology (e.g., subcarrier spacing, CP length, slot / minislot duration) can be configured.
[0124] In addition, the BS may set one or more BWPs in one carrier set to the UE. Alternatively, if UEs are concentrated in a specific BWP, some UEs may be moved to another BWP for load balancing. Alternatively, in consideration of frequency domain inter-cell interference cancellation between adjacent cells, some central spectrum of the entire bandwidth may be excluded and the BWPs on both sides of the cell may be set in the same slot. That is, the base station may set at least one DL / UL BWP for the UE associated with the wideband carrier, activate at least one DL / UL BWP set at a specific time (by L1 signaling, which is a physical layer control signal, a MAC control element (CE), which is a MAC layer control signal, or RRC signaling, etc.), and may instruct the UE to switch to another set DL / UL BWP (by L1 signaling, MAC CE, or RRC signaling, etc.) or may set a timer value so that the UE switches to a specific DL / UL BWP when the timer expires. An activated DL / UL BWP is specifically referred to as an active DL / UL BWP. In situations such as when the UE is in the process of initial access or before the UE's RRC connection is set up, the UE may not receive configuration for the DL / UL BWP. In such a situation, the DL / UL BWP assumed by the UE is referred to as an initially active DL / UL BWP.
[0125] 1.5.SSB (Synchronization Signal Block) transmission and related operations
[0126] FIG. 5 is a diagram showing the structure of an SSB (Synchronization Signal Block) to which various embodiments can be applied.
[0127] The terminal uses SSB to perform cell search, system information acquisition, beam alignment for initial connection, DL measurement, etc. SSB can be mixed with SS / PBCH (Synchronization Signal / Physical Broadcast channel) block.
[0128] Referring to FIG. 5, an SSB applicable to various embodiments is composed of 20 RBs within four consecutive OFDM symbols, and the SSB is composed of a PSS, an SSS, and a PBCH, and a terminal performs cell search, system information acquisition, beam alignment for initial connection, DL measurement, etc. based on the SSB.
[0129] The PSS and SSS each consist of one OFDM symbol and 127 subcarriers, and the PBCH consists of three OFDM symbols and 576 subcarriers. Polar coding and Quadrature Phase Shift Keying (QPSK) are applied to the PBCH. The PBCH consists of data REs and Demodulation Reference Signal (DMRS) REs for each OFDM symbol. There are three DMRS REs per RB, and three data REs between the DMRS REs.
[0130] Cell search
[0131] Cell search refers to the process in which a terminal acquires time / frequency synchronization of a cell and detects the cell ID (identifier) of the cell (e.g., Physical layer Cell ID, PCID). The PSS is used to detect a cell ID within a cell ID group, and the SSS is used to detect a cell ID group. The PBCH is used for SSB (time) index detection and half-frame detection.
[0132] The cell search process of the terminal is summarized in Table 8 below.
[0133] [Table 8]
[0134] There are 336 Cell ID groups, and 3 Cell IDs for each Cell ID group. There are 1008 Cell IDs in total. Information about the Cell ID group to which the Cell ID of a cell belongs is provided / obtained via the SSS of the cell, and information about the Cell IDs of the 336 cells in the Cell ID group is provided / obtained via the PSS.
[0135] FIG. 6 is a diagram illustrating an example of a method of transmitting SSB to which various embodiments can be applied.
[0136] Referring to FIG. 6, the SSB is transmitted periodically according to the SSB periodicity. The SSB basic period assumed by the terminal during initial cell search is defined as 20 ms. After cell connection, the SSB periodicity is set by the network (e.g., base station) to one of {5 ms, 10 ms, 20 ms, 40 ms, 80 ms, 160 ms}. An SSB burst set is configured at the beginning of the SSB period. The SSB burst set is configured in a 5 ms time window (i.e., half-frame), and the SSB can be transmitted a maximum of L times within the SS burst set. The maximum number of SSB transmissions L is given as follows, depending on the frequency band of the carrier. One slot contains a maximum of two SSBs.
[0137] -For frequency range up to 3GHz,L=4
[0138] -For frequency range from 3GHz to 6GHz,L=8
[0139] -For frequency range from 6GHz to 52.6GHz,L=64
[0140] The time position of the SSB candidate within the SS burst set is defined according to the SCS as follows: The time position of the SSB candidate is indexed from 0 to L-1 in the SSB burst set (i.e., half-frame) in time order (SSB index). In the description of various embodiments, the terms candidate SSB and SSB candidate can be used interchangeably.
[0141] - Case A: 15kHz SCS: The index of the starting symbol of the candidate SSB is given by {2,8}+14*n.
[0142] - For operation without shared spectrum channel access (e.g., L-Band, LCell): If the carrier frequency is 3 GHz or less, n = 0, 1. If the carrier frequency is 3 GHz to 6 GHz, n = 0, 1, 2, 3.
[0143] - - for operation with shared spectrum channel access (e.g., U-band, UCell): n = 0, 1, 2, 3, 4.
[0144] - Case B: 30kHz SCS: The index of the starting symbol of the candidate SSB is given by {4,8,16,20}+28*n. If the carrier frequency is 3GHz or less, n=0. If the carrier frequency is 3GHz to 6GHz, n=0,1.
[0145] - Case C: 30kHz SCS: The index of the starting symbol of the candidate SSB is given by {2,8}+14*n.
[0146] - -If shared spectrum channel connection operation is not performed / supported: (1) For paired spectrum operation, if the carrier frequency is less than or equal to 3 GHz, n = 0, 1. If the carrier frequency is within FR1 and greater than 3 GHz, n = 0, 1, 2, 3. (2) For unpaired spectrum operation, if the carrier frequency is less than or equal to 2.4 GHz, n = 0, 1. If the carrier frequency is within FR1 and greater than 2.4 GHz, n = 0, 1, 2, 3.
[0147] - -When shared spectrum channel access operation is performed / supported: n = 0, 1, 2, 3, 4, 6, 7, 8, 9.
[0148] - Case D: 120kHz SCS: The index of the starting symbol of the candidate SSBs is given by {4,8,16,20}+28*n, where n=0,1,2,3,5,6,7,8,10,11,12,13,15,16,17,18 when the carrier frequency is greater than 6GHz.
[0149] - Case E: 240kHz SCS: The index of the starting symbol of the candidate SSBs is given by {8,12,16,20,32,36,40,44}+56*n, where n=0,1,2,3,5,6,7,8 if the carrier frequency is greater than 6GHz.
[0150] Synchronization procedure
[0151] FIG. 7 is a diagram illustrating an example of a method for a terminal to obtain information regarding DL time synchronization, which is applicable to various embodiments.
[0152] The terminal can obtain DL synchronization by detecting the SSB. Based on the detected SSB index, the terminal identifies the structure of the SSB burst set, which allows it to detect the symbol / slot / half-frame boundary. The frame / half-frame number to which the detected SSB belongs is identified using the SFN information and the half-frame indication information.
[0153] Specifically, a terminal can obtain 10-bit SFN (System Frame Number) information from the PBCH (s0 to s9). Of the 10-bit SFN information, 6 bits are obtained from the MIB (Master Information Block), and the remaining 4 bits are obtained from the PBCH TB (Transport Block).
[0154] Then, the terminal can obtain 1-bit half-frame indication information (c0). When the carrier frequency is 3 GHz or less, the half-frame indication information is implicitly signaled using the PBCH DMRS. The PBCH DMRS indicates 3-bit information by using one of the 8 PBCH DMRS sequences. Therefore, when L=4, of the 3 bits indicated using the 8 PBCH DMRS sequences, the remaining 1 bit after indicating the SSB index can be used for half-frame indication.
[0155] Finally, the terminal 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 time order within the SSB burst set (i.e., half-frame). When L=8 or 64, the three least significant bits (LSBs) of the SSB index are indicated using eight different PBCH DMRS sequences (b0 to b2). When L=64, the three most significant bits (MSBs) of the SSB index are indicated by the PBCH (b3 to b5). When L=2, the two least significant bits (LSBs) of the SSB index are indicated using four different PBCH DMRS sequences (b0, b1). When L=4, of the three bits that can be indicated using eight PBCH DMRS sequences, one bit remaining after indicating the SSB index can be used for indicating a half-frame (b2).
[0156] Get System Information
[0157] FIG. 8 illustrates an example of a process for acquiring system information (SI) that may be used in various embodiments.
[0158] The UE obtains AS (access stratum)- / NAS (non access stratum)-information through the SI acquisition process. The SI acquisition process is applied to UEs in the RRC_IDLE, RRC_INACTIVE and RRC_CONNECTED states.
[0159] SI is divided into MIB (Master Information Block) and multiple SIB (System Information Block). SI other than MIB is called RMSI (Remaining Minimum System Information). For more information, see below.
[0160] -The MIB contains information / parameters related to the reception of SIB1 (System Information Block Type 1) and is transmitted via the PBCH of the SSB.
[0161] -The MIB contains information / parameters related to the reception of SIB1 (System Information Block Type 1) and is transmitted via the PBCH of the SSB. The MIB information can refer to 3GPP TS 38.331 and includes the following fields:
[0162] -subCarrierSpacingCommon ENUMERATED{SCS15or60, SCS30or120},
[0163] -ssb-SubcarrierOffset INTEGER(0..15),
[0164] -pdcch-ConfigSIB1 INTEGER(0..255),
[0165] -dmrs-TypeA-Position ENUMERATED{pos2, pos3},
[0166] ...
[0167] -spare BIT STRING(SIZE(1))
[0168] See Table 9 for an explanation of each field.
[0169] [Table 9]
[0170] When selecting an initial cell, the terminal assumes that a half-frame having an SSB is repeated at a period of 20 ms. The terminal can check whether a CORESET (Control Resource Set) (e.g., CORESET#0) for the Type0-PDCCH common search space exists based on the MIB. SSB ≦23(for FR1) or k SSB If ≦11 (for FR2), the terminal determines that there is no CORESET for the Type0-PDCCH common search space. The Type0-PDCCH common search space is a type of PDCCH search space and is used to transmit a PDCCH that schedules an SI message. If the Type0-PDCCH common search space exists, the terminal may determine (i) a number of consecutive RBs and one or more consecutive symbols constituting a CORESET (e.g., CORESET#0) and (ii) a PDCCH mechanism (i.e., a time domain position for PDCCH reception) (e.g., search space#0) based on information in the MIB (e.g., pdcch-ConfigSIB1). If the Type0-PDCCH common search space does not exist, pdcch-ConfigSIB1 provides information on the frequency position where SSB / SIB1 exists and the frequency range where SSB / SIB1 does not exist.
[0171] -SIB1 includes information related to availability and scheduling (e.g., transmission period, SI-window size) of the remaining SIBs (hereinafter, SIBx, where x is a constant equal to or greater than 2). For example, SIB1 indicates whether SIBx is broadcast periodically or whether it is provided at the request of a terminal in an on-demand manner. If SIBx is provided in an on-demand manner, SIB1 includes information required for a terminal to make an SI request. SIB1 is transmitted via a PDSCH, and the PDCCH that schedules SIB1 is transmitted via a Type0-PDCCH common search space, and SIB1 is transmitted via a PDSCH indicated by the PDCCH.
[0172] -SIBx are contained in SI messages and transmitted over the PDSCH. Each SI message is transmitted within a periodically occurring time window (i.e., SI-window).
[0173] Beam alignment
[0174] FIG. 9 is a diagram illustrating an example of a multi-beam transmission to which various embodiments can be applied.
[0175] Beam sweeping means that a TRP (Transmission Reception Point) (e.g., base station / cell) changes the beam (direction) of a radio signal over time (hereinafter, beam and beam direction are used interchangeably). SSBs are transmitted periodically using beam sweeping. In this case, the SSB index is implicitly linked to the SSB beam. The SSB beam is changed on an SSB (index) basis or on an SSB (index) group basis. In the latter case, the SSB beam is maintained the same within the SSB (index) group. That is, the transmission beam direction of an SSB is repeated for multiple consecutive SSBs. The maximum number of SSB transmissions L in an SSB burst set has a value of 4, 8, or 64 depending on the frequency band to which the carrier belongs. Therefore, the maximum number of SSB beams in an SSB burst set is also given by the frequency band of the carrier as follows:
[0176] -For frequency range up to 3GHz, Max number of beams=4
[0177] -For frequency range from 3GHz to 6 GHz, Max number of beams=8
[0178] -For frequency range from 6GHz to 52.6GHz, Max number of beams=64
[0179] If multi-beam transmission is not applied, the number of SSB beams is one.
[0180] When a terminal attempts an initial connection to a base station, the terminal aligns a beam with the base station based on the SSB. For example, the terminal identifies the best SSB after performing SSB detection. The terminal then transmits a RACH preamble to the base station using a PRACH resource linked / corresponding to the index (i.e., beam) of the best SSB. The SSB can also be used for beam alignment between the base station and the terminal after the initial connection.
[0181] Channel Measurement and Rate Matching
[0182] FIG. 10 is a diagram illustrating an example of a method for indicating an actual transmitted SSB (SSB_tx) to which various embodiments can be applied.
[0183] A maximum of L SSBs are transmitted in the SSB burst set, and the number / position of the SSBs actually transmitted varies for each base station / cell. The number / position of the SSBs actually transmitted is used for rate matching and measurement, and information about the SSBs actually transmitted (e.g., ssb-PositionsInBurst) is indicated as follows:
[0184] - In the case related to rate matching: Indicated by UE-specific RRC signaling or RMSI. UE-specific RRC signaling includes full (e.g., length L) bitmaps in the frequency ranges below 6 GHz and above 6 GHz. Meanwhile, RMSI includes full bitmaps below 6 GHz and includes compressed bitmaps above 6 GHz as shown. Specifically, information on the actually transmitted SSB is indicated using group-bitmap (8 bits) + intra-group bitmap (8 bits). Here, resources (e.g., RE) indicated by UE-specific RRC signaling or RMSI are reserved for SSB transmission, and PDSCH / PUSCH, etc. are rate-matched taking into account the SSB resources.
[0185] - In case of measurement related: In case of RRC connected mode, the network (e.g., base station) indicates the SSB set to be measured in the measurement period. The SSB set is indicated per frequency layer. If there is no indication for an SSB set, a default SSB set is used. The default SSB set includes all SSBs in the measurement period. The SSB set is indicated using a full (e.g., length L) bitmap in RRC signaling. In case of RRC idle mode, the default SSB set is used.
[0186] 2. Random Access Procedure (RACH)
[0187] When initially connecting to a base station or when there are no radio resources for signal transmission, the terminal can perform an optional connection procedure to the base station.
[0188] The voluntary access procedure is used for various purposes. For example, the voluntary access procedure is used for initial network access from RRC_IDLE, RRC connection re-establishment procedure, handover, UE-triggered UL data transmission, transition from RRC_INACTIVE, time alignment establishment when adding a SCell, OSI (other system information) request, and beam failure recovery, etc. The UE can obtain UL synchronization and UL transmission resources through the voluntary access procedure.
[0189] The contention-based and contention-free access procedures are classified into 4-step RACH and 2-step RACH.
[0190] 2.1.4-step RACH:Type-1 Random Access Procedure
[0191] FIG. 11 is a diagram illustrating an example of a 4-step RACH procedure to which various embodiments can be applied.
[0192] When a (contention-based) random access procedure is performed in four steps (4-step RACH), the terminal transmits a message (message 1, Msg1) including a preamble related to a specific sequence via a physical random access channel (PRACH) (1701) and receives a response message (RANDOM ACCESS RESPONSE (RAR) message) (message 2, Msg2) to the preamble via a PDCCH and a corresponding PDSCH (1703). The terminal transmits a message (message 3, Msg3) including a PUSCH (Physical Uplink Shared Channel) using scheduling information in the RAR (1705) and performs a contention resolution procedure such as receiving a physical downlink control channel signal and a corresponding physical downlink shared channel signal. The terminal receives a message (message 4, Msg4) including contention resolution information for the contention resolution procedure from the base station (1707).
[0193] The 4-step RACH procedure of the terminal can be summarized as shown in Table 10 below.
[0194] [Table 10]
[0195] First, the terminal may transmit an optional access preamble via PRACH as Msg1 of the optional access procedure in the UL.
[0196] Arbitrary access preamble sequences of different lengths are supported: long sequence 839 applies to subcarrier spacings of 1.25 and 5 kHz, and short sequence 139 applies to subcarrier spacings of 15, 30, 60, and 120 kHz.
[0197] Multiple preamble formats are defined by one or more RACH OFDM symbols and different cyclic prefixes (and / or guard times). RACH configuration for the initial bandwidth of a Pcell (Primary cell) is included in the cell's system information and provided to the UE. The RACH configuration includes information on the subcarrier spacing of the PRACH, available preambles, preamble formats, etc. The RACH configuration includes association information between SSBs and RACH (time-frequency) resources. The UE transmits an optional connection preamble on the RACH time-frequency resource associated with the detected or selected SSB.
[0198] A threshold value of an SSB for RACH resource association is set by the network, and a RACH preamble is transmitted or retransmitted based on an SSB whose reference signal received power (RSRP) measured based on the SSB satisfies the threshold value. For example, the UE selects one of the SSBs that satisfies the threshold value, and transmits or retransmits the RACH preamble based on the RACH resource associated with the selected SSB. For example, when retransmitting the RACH preamble, the UE reselects one of the SSBs, and retransmits the RACH preamble based on the RACH resource associated with the reselected SSB. That is, the RACH resource for retransmission of the RACH preamble is the same and / or different from the RACH resource for transmission of the RACH preamble.
[0199] When the base station receives the random access preamble from the terminal, the base station transmits a random access response (RAR) message (Msg2) to the terminal. The PDCCH for scheduling the PDSCH carrying the RAR is CRC masked and transmitted by a random access (RA) radio network temporary identifier (RNTI) (RA-RNTI). The terminal that detects the PDCCH CRC scrambled in the RA-RNTI receives the RAR from the PDSCH scheduled by the DCI carried by the PDCCH. The terminal checks whether the random access response information related to the preamble transmitted by itself, i.e., Msg1, is present in the RAR. Whether the random access information related to the Msg1 transmitted by itself exists is determined by whether the random access preamble ID related to the preamble transmitted by the terminal exists. If there is no response to Msg1, the terminal retransmits the RACH preamble within a predetermined number of times while performing power ramping. The terminal calculates the PRACH transmit power for the retransmission of the preamble based on the most recent transmit power, the power increment amount, and the power ramping counter.
[0200] The voluntary access response information includes a preamble sequence transmitted by the terminal, a temporary cell-RNTI() assigned by the base station to the terminal attempting the voluntary access, uplink transmit time alignment information, uplink transmit power adjustment information, and uplink radio resource allocation information. When the terminal receives the voluntary access response information for itself on the PDSCH, the terminal knows timing advance information for UL synchronization, an initial UL grant, and TC-RNTI. The timing advance information is used to control the uplink signal transmission timing. In order for the PUSCH / PUCCH transmission by the terminal to be correctly aligned with the subframe timing in the network, the network (e.g., BS) obtains timing advance information based on timing information detected from the PRACH preamble received from the terminal and sends the corresponding timing advance information. The terminal transmits UL transmission on the uplink shared channel as Msg3 of the voluntary access procedure based on the voluntary access response information. Msg3 includes an RRC connection request and a terminal identifier. In response to Msg3, the network sends Msg4, which is treated as a contention resolution message on the DL. Upon receiving Msg4, the terminal can enter the RRC connected state.
[0201] As described above, the UL grant in the RAR schedules the base station to transmit a PUSCH. The PUSCH carrying the initial UL transmission by the UL grant in the RAR can also be referred to as the Msg3 PUSCH. The contents of the RAR UL grant, starting from the MSB and ending with the LSB, are given in Table 11.
[0202] [Table 11]
[0203] The TPC command is used to determine the transmission power of the Msg3 PUSCH and is interpreted, for example, as shown in Table 12.
[0204] [Table 12]
[0205] 2.2.2-step RACH:Type-2 random access procedure
[0206] FIG. 12 is a diagram illustrating an example of a 2-step RACH procedure to which various embodiments can be applied.
[0207] A 2-step RACH procedure, in which the (contention-based) voluntary access procedure is performed in two steps, has been proposed to simplify the RACH procedure in order to achieve low signaling overhead and low delay.
[0208] The operations of transmitting message 1 and message 3 in the 4-step RACH procedure are performed by a single operation in which the terminal transmits one message (message A) including PRACH and PUSCH in the 2-step RACH procedure, and the operations of transmitting message 2 and message 4 in the 4-step RACH procedure are performed by a single operation in which the base station transmits one message (message B) including RAR and collision resolution information in the 2-step RACH procedure.
[0209] That is, in the 2-step RACH procedure, the terminal combines messages 1 and 3 in the 4-step RACH procedure into one message (e.g., message A (MsgA)) and transmits the one message to the base station (1801).
[0210] Also, in the 2-step RACH procedure, the base station combines messages 2 and 4 in the 4-step RACH procedure into one message (eg, message B (MsgB)) and transmits the one message to the terminal (1803).
[0211] Based on such a combination of messages, the 2-step RACH procedure can provide a low-latency RACH procedure.
[0212] More specifically, in the 2-step RACH procedure, message A includes a PRACH preamble included in message 1 and data included in message 3. In the 2-step RACH procedure, message B includes a random access response (RAR) included in message 2 and contention resolution information included in message 4.
[0213] 2.3 Contention-free RACH
[0214] FIG. 13 illustrates an example of a contention-free RACH procedure to which various embodiments can be applied.
[0215] A contention-free RACH is used when a terminal is handing over to another cell or base station, or is performed when requested by a command from the base station. The basic process of the contention-free RACH is similar to that of the contention-based RACH. However, unlike the contention-based RACH in which the terminal randomly selects a preamble to be used from among multiple RACH preambles, in the contention-free RACH, a preamble to be used by the terminal (hereinafter, a dedicated RACH preamble) is assigned to the terminal by the base station (1901). Information on the dedicated RACH preamble is included in an RRC message (e.g., handover command) or is provided to the terminal by a PDCCH order. When the RACH is started, the terminal transmits a dedicated RACH preamble to the base station (1903). When the terminal receives a RACH response from the base station, the RACH procedure is completed (1905).
[0216] In the non-contention optional access procedure, the CSI request field in the RAR UL grant indicates whether the UE includes aperiodic CSI reporting in the corresponding PUSCH transmission. The subcarrier spacing for the Msg3 PUSCH transmission is provided by an RRC parameter. The UE transmits the PRACH and Msg3 PUSCH on the same uplink carrier of the same serving cell. The UL BWP for the Msg3 PUSCH transmission is indicated by SIB1 (System Information Block 1).
[0217] 2.4.MappingBetweenSSBBlockandPRACHresource(occasion)
[0218] 14 and 15 are diagrams illustrating an example of SS block transmission and PRACH resources linked to SS blocks according to various embodiments.
[0219] In order for a base station to communicate with a UE, it is necessary to know the optimal beam direction between the base station and the UE, and since the optimal beam direction also changes depending on the movement of the UE, it is necessary to continuously track the optimal beam direction. The process of knowing the optimal beam direction between the base station and the UE is called a beam acquisition process, and the process of continuously tracking the optimal beam direction is called a beam tracking process. The beam acquisition process is necessary for 1) initial connection in which the UE first attempts to connect to the base station, 2) handover in which the UE moves from one base station to another, and 3) beam recovery to recover from a state in which the optimal beam is lost during beam tracking to find the optimal beam between the UE and the base station, and the communication with the base station cannot maintain an optimal communication state or becomes impossible, i.e., beam failure.
[0220] In the case of an NR system, a multi-stage beam acquisition process is being discussed for beam acquisition in an environment using multiple beams. In the multi-stage beam acquisition process, the base station and the UE proceed with connection setup using a wide beam in the initial connection stage, and after the connection setup is completed, the base station and the UE communicate with optimal quality using a narrow beam. An example of a beam acquisition process of an NR system applicable to various embodiments is as follows.
[0221] 1) The base station transmits a synchronization block for each wide beam so that the UE searches for a base station in the initial connection phase, i.e., performs a cell search or cell acquisition, measures the channel quality for each wide beam, and searches for the optimal wide beam to use in the first phase of beam acquisition.
[0222] 2) The UE performs cell search for the synchronization block for each beam, and acquires downlink beam using the cell detection result for each beam.
[0223] 3) The UE performs a RACH procedure to inform the base station it has found of its connection.
[0224] 4) In order for the UE to inform the base station of the downlink beam acquisition result (e.g., beam index) at a broad beam level during the RACH process, the base station links or associates the synchronization block transmitted for each beam with the PRACH resource used for PRACH transmission. When the UE performs the RACH process using the PRACH resource linked to the optimal beam direction it found, the base station obtains information about the downlink beam suitable for the UE during the process of receiving the PRACH preamble.
[0225] In a multi-beam environment, the question is whether the UE and / or the transmission and reception point (TRP) can accurately determine the Tx beam and / or reception (Rx) beam direction between the UE and the TRP. In a multi-beam environment, the TX / RX reciprocity of the TRP (e.g., base station) or the UE may repeat signal transmission or perform beam sweeping for signal reception. TX / RX reciprocity is also called TX / RX beam correspondence in the TRP and the UE. In a multi-beam environment, if the TX / RX reciprocity is not enabled in the TRP and the UE, the UE may not transmit the uplink signal in the beam direction in which it received the downlink signal. This is because the optimal UL route and the optimal DL route may be different. TX / RX beam compatibility at a TRP is valid when the TRP can determine a TRP RX beam for a corresponding uplink reception based on the UE's downlink measurements for one or more TX beams of the TRP and / or the TRP can determine a TRP TX beam for a corresponding downlink transmission based on the TRP's uplink measurements for one or more RX beams of the TRP. TX / RX beam compatibility at a UE is valid when the UE can determine a UE RX beam for a corresponding uplink transmission based on the UE's downlink measurements for one or more RX beams of the UE and / or the UE can determine a UE TX beam for a corresponding downlink reception based on an indication of the TRP based on the uplink measurements for one or more TX beams of the UE.
[0226] 2.5.PRACH preamble structure
[0227] In an NR system, the RACH signal used for initial connection to a base station, i.e., for initial connection to a base station through a cell used by the base station, is configured using the following elements.
[0228] -Cyclic prefix (CP): prevents interference from previous / previous (OFDM) symbols and collects PRACH preamble signals arriving at the base station with various time delays into one same time period. That is, if the CP is set to match the maximum radius of the cell, the PRACH preambles transmitted by the UEs in the cell on the same resource will fall within the PRACH reception window corresponding to the PRACH preamble length set by the gNB for PRACH reception. The length of the CP is generally set to be greater than or equal to the maximum round trip delay. The CP has a length T CP has.
[0229] - Preamble (sequence): A sequence is defined for the base station to detect that a signal has been transmitted, and the preamble carries this sequence. The preamble sequence has a length of T SEQ has.
[0230] - Guard time (GT): A period defined to prevent the PRACH signal, which is transmitted from the farthest point from the base station on the RACH coverage and is delayed to enter the base station, from interfering with signals entering after the PRACH symbol period. Since the UE does not transmit a signal in this period, the GT may not be defined as the PRACH signal. The guard time has a length of T GP has.
[0231] 2.6.Mapping to physical resources for Physical random-access channel
[0232] The optional connection preamble is transmitted only within time resources obtained based on a pre-configured table for RACH configuration (RACH configuration table) and FR1, FR2, and a pre-configured spectrum type.
[0233] The PRACH configuration index in the RACH configuration table is as follows:
[0234] For RACH configuration tables for FR1 optional connection configuration and unpaired spectrum, it is given by the higher layer parameter prach-ConfigurationIndexNew(if configured). Otherwise, it is given by prach-ConfigurationIndex, msgA-prach-ConfigurationIndex, or msgA-prach-ConfigurationIndexNew(if configured), etc.
[0235] -For the RACH configuration table for optional connection setup and paired spectrum / supplementary uplink in FR1, and the RACH configuration table for optional connection setup and unpaired spectrum in FR2, it is given by the upper layer parameter prach-ConfigurationIndex, or msgA-prach-ConfigurationIndexNew(if configured), etc.
[0236] The RACH configuration table includes the PRACH configuration index, preamble format, n SFN 4 is a table of relationships between mod x=y, the number of subframes, the starting symbol, the number of PRACH slots, the number of time-domain PRACH occasions within a PRACH slot, and any of the PRACH periods.
[0237] The different cases are as follows:
[0238] -(1) FR1 optional connection setup and spectrum / additional uplink
[0239] -(2) FR1 arbitrary connection settings and unpaired spectrum
[0240] -(3) FR2 Arbitrary Connection Setup and Unpaired Spectrum
[0241] Table 13 below shows a portion of an example of a RACH configuration table for (2) FR1 arbitrary connection configuration and unpaired spectrum.
[0242] [Table 13]
[0243] The RACH configuration table indicates specific values of parameters (preamble format, period, SFN offset, RACH subframe / slot index, starting OFDM symbol, number of RACH slots, number of occasions, OFDM symbol for RACH format, etc.) required to configure a RACH occasion. When a RACH configuration index is specified, a specific value corresponding to the specified index is used.
[0244] For example, if the Starting OFDM symbol parameter is n, then one or more consecutive RACH opportunities (in the time domain) are configured starting from the OFDM symbol with index #n.
[0245] For example, the number of one or more RACH occasions may be indicated in the time domain by a number of time-domain PRACH occasions within a RACH slot parameter.
[0246] For example, a RACH slot may include one or more RACH opportunities.
[0247] For example, the number of RACH slots (within a subframe and / or within a slot of a particular SCS) may be indicated by a number of RACH slots parameter.
[0248] For example, the number of system frames (SFN) that contain RACH opportunities is n SFN It is determined by mod x = y. mod is a modulo arithmetic operation that finds the remainder r when the dividend q is divided by the divisor (r = q mod(d)).
[0249] For example, the subframe / slot (index) in which the RACH opportunity resides within the system frame is indicated by the RACH subframe / slot index parameter.
[0250] For example, the preamble format for RACH transmission and reception is indicated by the preamble format parameter.
[0251] Referring to FIG. 16(a), for example, when the starting OFDM symbol is designated as 0, one or more consecutive RACH opportunities (in the time domain) are set from OFDM symbol #0. For example, the number of one or more RACH opportunities follows a value designated by a RACH opportunity number parameter in a RACH slot in the time domain. For example, a preamble format is designated by a preamble format parameter. For example, preamble formats A1, A2, A3, B4, C0, C2, etc. are designated. For example, of the last two OFDM symbols, one is used as a guard interval, and the other is used for other uplink signal transmissions such as PUCCH, SRS (sounding reference signal), etc.
[0252] Referring to FIG. 16(b), for example, if the starting OFDM symbol is designated as 2, one or more consecutive RACH opportunities (in the time domain) are set from the OFDM symbol #2. For example, 12 OFDM symbols are used for RACH opportunities, and no guard interval is set in the last OFDM symbol. For example, the number of one or more RACH opportunities follows the value designated by the RACH opportunity number in RACH slot parameter in the time domain. For example, the preamble format is designated by the preamble format parameter. For example, preamble formats A1 / B1, B1, A2 / B2, A3 / B3, B4, C0, C2, etc. are designated.
[0253] Referring to FIG. 16(c), for example, if the starting OFDM symbol is designated as 7, one or more consecutive RACH opportunities (in the time domain) are set from OFDM symbol #7. For example, six OFDM symbols are used for RACH opportunities, and the last OFDM symbol (OFDM symbol #13) is used for other uplink signal transmissions such as PUCCH, SRS (sounding reference signal), etc. For example, the number of one or more RACH opportunities follows a value designated by a RACH opportunity number parameter in a RACH slot in the time domain. For example, a preamble format is designated by a preamble format parameter. For example, preamble formats A1, B1, A2, A3, B3, B4, C0, C2, etc. are designated.
[0254] For example, the parameters included in the RACH configuration table satisfy a predefined correspondence relationship that is identified / determined by the RACH configuration table and the RACH configuration index. For example, a predefined correspondence relationship is satisfied among the PRACH configuration index, the RACH format, the period (x)=8, the SFN offset (y), the number of subframes, the starting symbol (index), the number of PRACH slots in the subframe, the number of PRACH opportunities in the PRACH slot, the OFDM symbol for the PRACH period / RACH format, etc., and such correspondence relationship is identified by the RACH configuration index and the RACH configuration table.
[0255] 3. Various Examples
[0256] Various embodiments will be described in more detail below based on the above technical ideas. In the various embodiments described below, the contents of 1. and 2. above are applied. For example, operations, functions, terms, etc. not defined in the various embodiments described below can be performed and explained based on the contents of 1. and 2.
[0257] The symbols / abbreviations / terms used in the description of the various embodiments are as follows:
[0258] -A / B / C: A and / or B and / or C
[0259] -BWP:bandwidth part
[0260] -CBRA:contention-based random access
[0261] -CDM:code division multiplexing(code domain sharing)
[0262] -comb: A comb refers to a method of mapping a signal at a fixed interval in the frequency domain. For example, comb-2 (or 2-comb) means mapping the same specific RS to REs spaced apart by two subcarrier intervals. For example, comb-4 (or 4-comb) means mapping the same specific RS to REs spaced apart by four subcarrier intervals.
[0263] -CFRA:contention-free random access
[0264] -CP-OFDM: cyclic prefix based orthogonal frequency division multiplex, which can be understood as a case where transform precoding is disabled.
[0265] -DFT-s-OFDM: discrete Fourier transform spread orthogonal frequency division multiplex, which can be understood as the case when transmit precoding is enabled.
[0266] -DL:downlink
[0267] -DM-RS(DMRS):demodulation reference signal
[0268] -FDM:frequency division multiplexing(frequency domain sharing)
[0269] -MCS: modulation and coding scheme
[0270] -OCC: orthogonal cover code
[0271] -OFDM:orthogonal frequency division multiplexing
[0272] -PAPR:peak to average power ratio
[0273] -PRACH:physical random access channel
[0274] -PRB:physical Resource block
[0275] -PRU:PUSCH Resource unit
[0276] -PO:PUSCH occasion
[0277] -PUSCH:physical uplink shared channel
[0278] -RA:random access
[0279] -RACH:random access channel
[0280] -RAPID:random access preamble identifier
[0281] -RAR:random access response
[0282] -RB:Resource block
[0283] -RE:Resource element
[0284] -RNTI:radio network temporary identifier
[0285] -RO:RACH occasion or PRACH occasion
[0286] -SCID: scrambling identifier
[0287] -TBS: transmission block size
[0288] -TDM:Time division multiplexing (Time domain sharing)
[0289] -UL:uplink
[0290] -Rel-15 (REL.15): 3GPP (3rd generation partnership project) TS (technical specification) Release 15 and / or a system that supports 3GPP TS Release 15 and / or a system that can coexist with it
[0291] -Rel-16 (REL.16): 3GPP (3rd generation partnership project) TS (technical specification) Release 16 and / or a system that supports 3GPP TS Release 16 and / or a system that can coexist with it
[0292] In the discussion of various embodiments, the term "greater than / greater than A" may be interchanged with "greater than / greater than A."
[0293] In the description of various embodiments, the term "less than / equal to B" may be replaced with "less than / equal to B."
[0294] In the description of various embodiments, PUSCH(transmission) is included in message A(transmission) unless otherwise stated.
[0295] In the description of various embodiments, PUSCH / PO / PRU may be interchanged unless otherwise stated.
[0296] For example, in the case of 2-step RACH, message A transmitted in the uplink is composed of a PRACH preamble and a PUSCH resource. For example, the PRACH preamble and the PUSCH resource are mapped together from the SSB, but it is difficult to set such a relationship in a simple manner. For example, the state of the RACH occasion (e.g., period, number of available ROs, mapping relationship between SSB and RO, etc.) and the PUSCH configuration method (period, number of available RO / PO (PUSCH occasions), number of DMRS antenna ports / sequences, etc.) must be considered.
[0297] Various embodiments relate to a method for configuring a message A PUSCH.
[0298] Various embodiments relate to a method for configuring a DM-RS for a message A PUSCH.
[0299] Various embodiments relate to a RACH preamble to PUSCH (Resource unit) mapping method to support a two-step RACH.
[0300] FIG. 17 is a simplified diagram illustrating the operation of a terminal and a base station in accordance with various embodiments.
[0301] FIG. 18 is a simplified diagram illustrating a method of operation of a terminal according to various embodiments.
[0302] FIG. 19 is a simplified diagram illustrating a method of operating a base station in accordance with various embodiments.
[0303] 17 to 19, in operations 1701, 1801 according to various embodiments, a terminal derives / generates a message A. For example, the terminal derives / generates the message A based on mapping a PRACH preamble to an RO and / or mapping a PUSCH to a PUSCH opportunity and / or mapping a DM-RS.
[0304] In operations 1703, 1803, and 1901 according to various embodiments, a terminal transmits a message A and a base station receives the message A.
[0305] In operations 1705, 1903 according to various embodiments, the base station decodes (detects) message A. For example, the base station decodes message A to obtain a PRACH preamble and / or a PUSCH and / or a DM-RS included within message A.
[0306] In operations 1707, 1805, 1905 according to various embodiments, the base station transmits message B and / or message 2 in response to message A, and the terminal receives message B and / or message 2 in response.
[0307] More specific operations, functions, terms, etc. in the operations according to each exemplary embodiment can be performed and explained based on various embodiments described below.
[0308] Various embodiments will be described in detail below. The various embodiments described below can be combined in whole or in part to form various other embodiments, unless they are mutually exclusive, and it will be clearly understood by those skilled in the art.
[0309] 3.1 DMRS for msgA PUSCH
[0310] DMRS configuration type for msgA PUSCH
[0311] According to various embodiments, in a two-step RACH, only type 1 DMRS is applied for message A PUSCH.
[0312] In an NR system to which various embodiments can be applied, two DMRS types are supported, such as DMRS configuration type 1 and type 2. For example, the type of DMRS is configured from dmrs-Type, and if there is no corresponding information element (IE), DMRS type 1 is used.
[0313] For example, in configuration type 1, the minimum resource element group (REG) in the frequency domain is one RE, and for example, in configuration type 2, the minimum REG in the frequency domain is two consecutive REs.
[0314] For example, in configuration type 1, 3 pairs (6 REs) of DMRS are distributed across 1 OFDM symbol / 1 RB with 4 RE intervals. The 2 REs in each pair are separated by 2 RE intervals. For example, the 6 REs of a DMRS symbol are distributed across every other RE in the frequency domain. For example, 8 DMRS ports (ports 1000 to 1007) are supported for double-symbol DMRS. For example, 4 DMRS ports (ports 1000 to 1003) are supported for single symbol DMRS.
[0315] For example, in configuration type 2, two pairs (4 REs) of DMRS are distributed across one OFDM symbol / one RB with an interval of 6 REs. The 2 REs in each pair are separated by an interval of 1 RE, which means that the 2 REs of each pair are consecutive. For example, in dual-symbol DMRS, 12 DMRS ports (ports 1000 to 1011) are supported. For example, in single-symbol DMRS, 8 DMRS ports (ports 1000 to 1007) are supported.
[0316] According to various embodiments, a type 1 DMRS is applied for the PUSCH of message 3 in a 4-step RACH procedure, e.g., a type 1 DMRS is used for the transmission of message 3 within a specific UL BWP.
[0317] According to various embodiments, in a two-step RACH procedure, considering that the RACH configuration for the two-step RACH procedure is configured by the BWP-UplinkCommon applied to the terminal, only the type 1 DMRS is applied for the message A PUSCH. For example, the BWP-UplinkCommon is a cell-specific information element (IE) used for configuring common parameters of the uplink BWP.
[0318] PUSCH DMRS port / sequence
[0319] According to various embodiments, a network (eg, a base station) can configure the number of antenna ports for the message A PUSCH DMRS.
[0320] According to various embodiments, the maximum number of antenna ports is four.
[0321] For example, if the number of configured antenna ports is 2, antenna port 0 and antenna port 1 are used.
[0322] For example, if the number of configured antenna ports is 1, antenna port 0 is used.
[0323] According to various embodiments, for a Type-1 DMRS, when one OFDM symbol is used, up to four antenna ports are assigned, for example, an antenna port is configured with a frequency resource (e.g., a 2-comb type resource) and a cyclic shift value (e.g., 0 and π (pi)).
[0324] According to various embodiments, a PRACH preamble mapping is defined.
[0325] According to various embodiments, within a message A association period, the PRACH preambles are mapped to valid PRUs based on the following order:
[0326] First, ascending order of frequency resource index for frequency multiplexed PUSCH opportunities
[0327] Second, ascending order of DMRS index within one PUSCH opportunity
[0328] --The DMRS index is determined based on considering the ascending order of the DMRS port indexes and then considering the ascending order of the DMRS sequence indexes.
[0329] Third, ascending order of time resource index for time multiplexed PUSCH opportunities within one PUSCH slot
[0330] Fourth, ascending order of indices for PUSCH slots
[0331] For multiple configurations, mapping is performed between preambles in the preamble group corresponding to the PRU of each message A PUSCH configuration.
[0332] Each message A PUSCH configuration may identify a sub-set of DMRS port / sequence combinations.
[0333] For example, one or more consecutive preamble indices of (valid) PRACH opportunities in a slot:
[0334] First, ascending order of preamble index within one PRACH opportunity;
[0335] second, ascending order of frequency resource index for frequency multiplexed PRACH opportunities;
[0336] third, ascending order of time resource index for time multiplexed PRACH opportunities within PRACH slots mapped to (valid) PUSCH opportunities;
[0337] Mapped to (valid) PUSCH opportunities:
[0338] first, in ascending order of frequency resource index for frequency multiplexed PUSCH resources;
[0339] Second, an ascending order of DMRS indices within a PUSCH opportunity, for example, the DMRS indices are determined based on considering an ascending order of DMRS port indices and then an ascending order of DMRS sequence indices.
[0340] third, ascending order of time resource index for time multiplexed PUSCH opportunities within a PUSCH slot;
[0341] Fourth, ascending order of indices for PUSCH slots
[0342] According to various embodiments, a method is provided for indicating DMRS resources, including DMRS ports and / or DMRS sequences.
[0343] For example, in a 4-step RACH, a single antenna port is applied for message 3 transmission, but for example, in a 2-step RACH, all antenna ports are used for increased efficiency of PUSCH resources.
[0344] According to various embodiments, the network (eg, a base station) configures the number of antenna ports for the message A PUSCH DMRS.
[0345] According to various embodiments, the number of antenna ports is determined taking into account network coverage and / or geometry. For example, if the network coverage is relatively wide and / or the geometry is not favorable for supporting a large number of terminals in a PUSCH opportunity, a relatively low number of antenna ports (e.g., one or two) may be assigned. Conversely, if, for example, a two-step RACH is operated in a relatively narrow network coverage and / or the geometry is relatively good, a relatively high number of antenna ports (e.g., two or four) may be assigned to a PUSCH opportunity.
[0346] According to various embodiments, when two antenna ports are configured, antenna ports 0 and 1 (or 2 and 3) with the same frequency resource and different cyclic shift values are used, for example, because the cyclic shift allows the antenna ports to be distinguished even when the OFDM symbol reception timing is very large (e.g., FFT (fast Fourier transform) size / 4).
[0347] sequence initialization for msgA PUSCH DMRS
[0348] According to various embodiments, in the case of CP-OFDM (when DMRS is based on CP-OFDM, transmit precoding is deactivated), up to two different initial values and / or seed values are configured from higher layer signals (e.g., SIB1 and / or RACH-ConfigCommon). According to various embodiments, the sequence is specified / instructed depending on RAPID.
[0349] And / or, according to various embodiments, if transmit precoding is deactivated, the following equation (1) is used for the pseudo-random sequence generator for message A PUSCH: According to various embodiments, if transmit precoding is deactivated, the pseudo-random sequence generator for message A PUSCH is initialized by the following equation (1):
[0350] [Number 1] c init =(2 17 (N slot symb n u s,f +l+1)(2N nSCID ID +1)+2N nSCID ID +n SCID )mod 2 31
[0351] For example, C init denotes the initial value of the scrambling sequence generator.
[0352] For example, N slot symb means the number of symbols per slot.
[0353] For example, n u s,f means the slot number within the frame for SCS setting u.
[0354] For example, N 0 ID , N 1 ID ,…,N M-1 ID ∈ {0,1,...,65535} are given by the upper layer parameters scramblingID0, scrambling ID1, and scrambling IDM-1 in the upper layer signal, respectively.
[0355] For example, n SCID∈ {0,1,…,M-1} is specified depending on RAPID.
[0356] For example, M is at most 2.
[0357] According to various embodiments, in the case of DFT-s-OFDM (when the DMRS is based on DFT-s-OFDM and transmit precoding is activated), one root index of the Zadoff-chu (ZC) sequence is set from the higher layer signal.
[0358] According to various embodiments, multiple DMRS sequences are applied per antenna port to increase the efficiency of PUSCH resources. For example, in the case of CP-OFDM, a pseudo-random sequence (PN sequence) can be applied to the DMRS sequence. For example, for UL multi-user multiple input and multiple output (MU-MIMO), two different seed values are configured from an RRC signal, and one of the two seed values is specified / indicated from a DCI. For example, for spatially separated terminals, two different DMRS sequences are applied even if the terminals are assigned the same antenna port. For example, when CP-OFDM is used for message A PUSCH, multiple DMRS sequences are applied. For example, the seed value is configured from SIB1 and / or RACH-ConfigCommon, and is specified / indicated depending on RAPID. For example, the seed value is configured from SIB1 and / or RACH-ConfigCommon, and is specified / indicated based on one or more RAPIDs among the configured seed values. For example, RACH-ConfigCommon is an IE used to instantiate cell-specific optional connection parameters.
[0359] According to various embodiments, for the DMRS of message A PUSCH, Equation 1 above is used to initialize a pseudo-arbitrary sequence generator.
[0360] According to various embodiments, for the message A PUSCH, the seed value (e.g., N 0 ID , N 1 ID ) is configured from SIB1 and / or RACH-ConfigCommon.
[0361] According to various embodiments, n in the above number 1 SCID is specified depending on RAPID. For example, the PRU is assigned a DMRS port and a DMRS sequence index (e.g., n SCID ), n SCID is obtained automatically by RAPID to PRU mapping.
[0362] According to various embodiments, for DFT-s-OFDM, low PAPR sequences (eg, Zadoff-chu sequences) are applied and one sequence is assigned as a DMRS sequence.
[0363] According to various embodiments, the number of PRUs in a PO is one of {1, 2, 4, 8}.
[0364] According to various embodiments, if the number of PRUs in a PO is one, then only one set is defined for the (number of) DMRS ports and the (number of) DMRS sequences.
[0365] According to various embodiments, when the number of PRUs in a PO is two, two sets of DMRS port and DMRS sequence combinations (e.g., {2, 1}, {1, 2}) are defined. For example, when two antenna ports are used in a PO, one of two (CDM) groups is configured for the two antenna ports.
[0366] According to various embodiments, when the number of PRUs in a PO is four, two sets of DMRS port and DMRS sequence combinations (e.g., {4, 1}, {2, 2}) are defined. For example, when four antenna ports are used in a PO, two CDM groups (all) are used for the same DMRS sequence. For example, when two antenna ports are used in a PO, one of the two (CDM) groups is configured with two different DMRS sequences.
[0367] According to various embodiments, if the number of PRUs in a PO is 8, the four antenna ports in the two CDM groups are used with two different DMRS sequences. According to various embodiments, unless otherwise configured, all two (CDM) groups can be used.
[0368] According to various embodiments, within a PO, multiple PRUs are defined depending on the combination of the (number of) DMRS ports and the (number of) DMRS sequences.
[0369] For example, the set of PRUs in a PO is defined as shown in Table 14.
[0370] [Table 14]
[0371] For example, if the number of PRUs in a PO is 1, then only one set is defined for the (number of) DMRS ports and the (number of) DMRS sequences.
[0372] For example, if the number of PRUs in a PO is two, two sets of DMRS port and DMRS sequence combinations (e.g., {2, 1}, {1, 2}) are defined. For example, if two antenna ports are used in a PO, one of two (CDM) groups is configured for the two antenna ports.
[0373] For example, if the number of PRUs in a PO is 4, then two sets of DMRS port and DMRS sequence combinations (e.g., {4, 1}, {2, 2}) are defined. For example, if four antenna ports are used in a PO, then two CDM groups (all) are used with the same DMRS sequence. For example, if two antenna ports are used in a PO, then one of the two (CDM) groups is set to two different DMRS sequences.
[0374] For example, if the number of PRUs in a PO is 8, then 4 antenna ports in 2 CDM groups are used with 2 different DMRS sequences. According to various embodiments, unless otherwise configured, all 2 (CDM) groups are used.
[0375] 3.2. msgA PUSCH configuration
[0376] Msg a PUSCH scrambling sequence
[0377] According to various embodiments, for the message A PUSCH data scrambling sequence, the random access-RNTI (RA-RNTI) and / or RAPID are used as seed values for sequence initialization for CBRA.
[0378] According to various embodiments, for the Message A PUSCH data scrambling sequence, the C-RNTI is used as a seed value for sequence initialization for CFRA.
[0379] According to various embodiments, the initialization value c for the scrambling sequence is int is RNTI and ID It is composed of:
[0380] According to various embodiments, for a message A PUSCH in a 2-step RACH, n RNTI and ID It is determined which value applies for
[0381] For example, in the case of a 4-step RACH, TC-RNTI (temporary cell-RNTI) / C-RNTI (cell-RNTI) is the nth RNTI for message 3 PUSCH. RNTI On the other hand, for message A PUSCH in the case of 2-step RACH, TC-RNTI / C-RNTI is not applied to terminals in RRC_IDLE and RRC_INACTIVE states. In consideration of this, according to various embodiments, an RNTI (e.g., RA-RNTI) different from TC-RNTI / C-RNTI is applied to n RNTI According to various embodiments, the terminal in the RRC_CONNECTED state has a C-RNTI of n RNTI applies to.
[0382] For example, in the case of a 4-step RACH, N ID cell (PCI(physical cell identifier)) is n for message 3 PUSCH ID On the other hand, for message A PUSCH in the case of 2-step RACH, multiple RAPIDs are mapped to one PUSCH opportunity. In this case, for example, inter-layer interference between PUSCH data REs may increase. To reduce this interference, according to various embodiments, N ID cell instead of n ID According to various embodiments, in the case of CBRA, RAPID is n for message A PUSCH. ID According to various embodiments, in the case of CBRA, for message A PUSCH, RAPID is applied with C-RNTI as a seed value for sequence initialization.
[0383] According to various embodiments, the PUSCH scrambling sequence initialization formula is changed depending on the use case of mapping between preamble to PRU.
[0384] According to various embodiments, in the case where one RAPID is mapped to multiple PRUs in a PO, a formula for PUSCH scrambling sequence initialization based on DMRS index is used instead of RAPID.
[0385] According to various embodiments, for the case where one RAPID is mapped to multiple PRUs in each PO, a formula for PUSCH scrambling sequence initialization based on RAPID is used.
[0386] According to various embodiments, the initialization ID for message A PUSCH scrambling is:
[0387] [Number 2] c init =RA-RNTI x 2 16 +RAPID×2 10 + nID
[0388] For example, C init denotes the initial value of the scrambling sequence generator.
[0389] For example, n ID is set to a cell-specific higher hierarchical parameter, and / or ID =N ID cell It is.
[0390] According to various embodiments, the RAPID may or may not be modified to a DMRS index.
[0391] According to various embodiments, one-to-multiple mapping between preambles and PRUs may and / or may not be supported.
[0392] According to various embodiments, in one-to-many mapping, the following two cases are considered:
[0393] -1) Case 1: One RAPID is mapped to multiple PRUs within a PO.
[0394] -2) Case 2: One RAPID is mapped to multiple PRUs within each PO.
[0395] For example, the inclusion of RAPID in the formulas (such as Equation 1) for scrambling sequence initialization is intended to improve the effect of inter-user interference randomization within the PUSCH resource.
[0396] For example, in case 1, if multiple terminals that select the same RAPID transmit PUSCHs using the same scrambling sequence, the base station cannot obtain the effect of randomizing interference between users.
[0397] On the other hand, for example, in case 2, the base station can obtain the effect of randomizing the interference between users by using the formula (such as formula 1) for initializing the scrambling sequence.
[0398] According to various embodiments, depending on which of the one-to-many mapping cases is selected, it is determined whether or not the formula (such as formula 1) for scrambling sequence initialization including RAPID is used.
[0399] For example, in case 1, RAPID is changed to a DMRS index.
[0400] For example, in case 2, RAPID is used as is.
[0401] For example, a scrambling sequence generator used for generating the PUSCH (or for the PUSCH) is initialized by the following equation (3): Any of the parameters used in the following equation (3) may be generated / obtained / determined based on various embodiments. For example, the equation (3) may be understood as a more specific version of the equation (2).
[0402]
number
[0403] For example, C init denotes the initial value of the scrambling sequence generator.
[0404] For example, the value of each parameter is determined based on the following:
[0405] -If the RNTI is a C-RNTI, an MCS-C-RNTI (modulation and coding scheme C-RNTI), an SP-CSI-RNTI (semi persistent channel state information RNTI) or a CS-RNTI (configured scheduling RNTI), and the (PUSCH) transmission is not scheduled by DCI format 1_0 in the common search space, and the higher layer parameter dataScramblingIdentityPUSCH is configured, JPEG0007581339000016.jpg1051 has the value indicated by the higher layer parameter dataScramblingIdentityPUSCH.
[0406] - if the (PUSCH) transmission is triggered by a type 2 voluntary access procedure (2-step RACH procedure) and the higher layer parameter msgA-dataScramblingIdentity is set, JPEG0007581339000017.jpg1051 has the value indicated in the higher hierarchical parameter msgA-dataScramblingIdentity.
[0407] -If not, JPEG0007581339000018.jpg1336. That is, JPEG0007581339000019.jpg1113 has a value such as a PCI (physical cell identifier), and has a value from 0 to 1007, for example.
[0408] - JPEG0007581339000020.jpg1126 is the index of the optional connection preamble sent for message A. For example, JPEG0007581339000021.jpg1126 corresponds to information associated with the PRACH preamble selected by the terminal (or user) as the seed value of the scrambling sequence, The user can distinguish from JPEG0007581339000022.jpg1126.
[0409] - JPEG0007581339000023.jpg1125 (for the PUSCH contained in message A) has the same value as the RA-RNTI for message A. For example, JPEG0007581339000024.jpg1125 corresponds to the RA-RNTI mentioned above as a seed value for the scrambling sequence or the RNTI used to monitor the (base station's) response to the message A PUSCH. As another example, there is a value of RA-RNTI for a 4-step RACH.
[0410] for example, According to JPEG0007581339000025.jpg1113, inter-cell interference is randomized.
[0411] On the other hand, for example, in a two-step RACH procedure, there may be an RA-RNTI and a msgB-RNTI corresponding to a specific RO.
[0412] According to various embodiments, the RA-RNTI is used for PUSCH data scrambling sequence generation / acquisition, and the msgB-RNTI is used for monitoring the PDCCH for message B.
[0413] That is, according to various embodiments, a distinction is made between the uses of the RA-RNTI and msgB-RNTI corresponding to a particular RO.
[0414] Also, according to various embodiments, the RA-RNTI and RAPID are distinguished and used as seed values for PUSCH data scrambling sequence generation / acquisition.
[0415] Supported MCS and time-frequency Resource size of PUSCH in msgA etc
[0416] According to various embodiments, a limited number of MCS levels are used for the PUSCH in message A. For example, one and / or two MCS levels are used.
[0417] According to various embodiments, only quadrature phase shift keying (QPSK) for CP-OFDM is applied for the PUSCH in message A.
[0418] According to various embodiments, two types of coding rates are used.
[0419] According to various embodiments, only the MCS is indicated in the PUSCH configuration. According to various embodiments, only the MCS is signaled in the RRC configuration for MCS and TBS for message A PUSCH. According to various embodiments, the TBS etc. is determined based on a pre-defined correspondence with the MCS value, for example by a pre-defined TBS table. According to various embodiments, a range of values for the TBS and / or MCS is pre-defined.
[0420] According to various embodiments, a modulation order and / or coding rate for message A PUSCH is provided.
[0421] For example, in a 4-step RACH, the MCS for message 3 is assigned / indicated by the UL grant in the RAR message. For example, depending on the terminal channel condition, the base station can assign the MCS from a low index to a high index. For example, the time / frequency resources for the PUSCH are assigned depending on the selected MCS level and the required coverage.
[0422] On the other hand, for example, due to a two-step RACH, it is difficult to allow flexible MCS selection. For example, if a terminal selects an MCS level for UL transmission depending on DL measurement results, it may not be applicable to UL transmission because not only the channel state but also the interference level is very different between the DL channel and the UL channel. In addition, for example, the required amount of PUSCH resources for message A may change depending on the MCS level.
[0423] Thus, for example, if multiple MCS levels are allowed, many types of PUSCH resources may be defined and / or pre-assigned, which may be undesirable in terms of resource utilization.
[0424] According to various embodiments, a very limited number of MCS levels is used for the PUSCH in message A. For example, one and / or two MCS levels are used. According to various embodiments, only quadrature phase shift keying (QPSK) for CP-OFDM is applied for the PUSCH in message A. According to various embodiments, two types of coding rates are used.
[0425] According to various embodiments, if multiple sets for DMRS frequency resources are allowed, each DMRS frequency resource (eg, a CDM group) is configured by message A PUSCH configuration.
[0426] According to various embodiments, if multiple MCS levels are allowed for PUSCH transmission, multiple types of PUSCH resources are configured by the message A PUSCH configuration depending on the MCS level.
[0427] According to various embodiments, the value range defined by ssb-perRACH-OccasionAndCB-PreamblesPerSSB-msgA (msgA-SSB-PerRACH-OccasionAndCB-PreamblesPerSSB) is divided into N-parts (N: natural number). According to various embodiments, one part of the range value is composed of a set of RAPIDs and is associated with a (one) message A PUSCH configuration. According to various embodiments, another part of the range value is associated with another message A PUSCH configuration.
[0428] According to various embodiments, msgA-SSB-PerRACH-OccasionAndCB-PreamblesPerSSB is included in RACH-ConfigCommonTwoStepRA, which is used to instantiate cell specific parameters for the two-step RACH procedure.
[0429] According to various embodiments, msgA-SSB-PerRACH-OccasionAndCB-PreamblesPerSSB is defined as follows in Table 15:
[0430] [Table 15]
[0431] According to various embodiments, when multiple MCS levels are allowed for PUSCH transmission, multiple types of PUSCH resources are defined depending on the MCS level. As a result, according to various embodiments, when a PUSCH resource is associated / corresponding to RAPID, RAPID can also be associated / corresponding to an MCS level. Thus, according to various embodiments, when a terminal determines a suitable MCS level for PUSCH transmission, the terminal can select a RAPID associated with the MCS level.
[0432] According to various embodiments, multiple sets of DMRS frequency resources are permitted, with each DMRS frequency resource defined as being associated with an MCS level.
[0433] For example, if two different PUSCH resources (e.g., a larger first frequency resource (set) for a lower MCS level / a smaller second frequency resource (set) for a higher MCS level) are assumed, then two different frequency resource sets are specified for each PUSCH resource.
[0434] 20 illustrates an example of resource configuration for message A according to various embodiments. FIG 20 illustrates an example of DMRS RE designation according to PUSCH resources and MCS levels according to various embodiments.
[0435] 20, for example, when a relatively high MCS level is used for the PUSCH included in message A, a relatively small frequency resource consisting of one RB is used for the PUSCH included in message A. That is, for example, when a relatively high MCS level is used for the PUSCH included in message A, the PUSCH included in message A is allocated to a relatively small frequency resource consisting of one RB.
[0436] For example, when a relatively low MCS level is used for the PUSCH included in message A, a relatively large frequency resource consisting of two RBs is used for the PUSCH included in message A. That is, when a relatively low MCS level is used for the PUSCH included in message A, the PUSCH included in message A is allocated within a relatively large frequency resource consisting of two RBs.
[0437] For example, 1 contains a set of REs with even indices st Comb, a set of REs with odd indices, containing 2 nd The comb is set.
[0438] For example, if a relatively high MCS level is used for the PUSCH included in message A, the DM-RS is 1 st Assigned to a comb.
[0439] For example, if a relatively low MCS level is used for the PUSCH contained in message A, the DM-RS is 2 nd Assigned to a comb.
[0440] That is, for example, a DM-RS resource (eg, a DM-RS port) for the PUSCH included in message A is determined based on the MCS level.
[0441] Or, for example, in the case of multiple PUSCH configurations with overlapping DM-RS symbols, the base station (and / or network) may assign different CDM groups to each Message A PUSCH configuration.
[0442] According to various embodiments, at least two message A PUSCH configurations are supported. According to various embodiments, parameters (e.g., MCS, MCS / TBS, antenna ports / sequences, time / frequency resources for PO, period / slot offset for PO group, etc.) are set independently for each message A PUSCH configuration. According to various embodiments, multiple configurations are allowed for setting different MCS levels and / or different time / frequency resources. And / or, according to various embodiments, period / offset may be set differently for each message A PUSCH configuration.
[0443] On the other hand, if the number of valid POs in the time domain is different, the mapping of the preamble of message A to the PRU (msgA preamble to PRU mapping) becomes more difficult. In consideration of this, according to various embodiments, the POs configured by different message A PUSCH configurations are located at least at the same time position.
[0444] According to various embodiments, the configured POs may overlap in time / frequency. According to various embodiments, if different CDM groups are configured for each PO, the network can separate multiple UL signals transmitted in the time / frequency resources (see FIG. 20).
[0445] PUSCH configuration indication
[0446] According to various embodiments, the preamble group in the CBRA is used for both the message A PUSCH indication and the preamble group indication.
[0447] For example, if preamble groups A and B are used for 2-step RACH, then such preamble groups are used to indicate all of the message A PUSCH configurations and preamble groups.
[0448] For example, the terminal selects a preamble group depending on the size of the message for transmission.
[0449] For example, if preamble groups A and B are not configured for 2-step RACH, then such preamble groups are only used when message A indicates PUSCH configuration.
[0450] For example, the terminal selects a preamble group depending on the channel condition (e.g., synchronization signal reference signal received power, SS-RSRP).
[0451] According to various embodiments, the value range defined by ssb-perRACH-OccasionAndCB-PreamblesPerSSB-msgA (msgA-SSB-PerRACH-OccasionAndCB-PreamblesPerSSB) is divided into N-parts (N: natural number). According to various embodiments, one part of the range value constitutes a set of RAPIDs associated with the message A PUSCH configuration. According to various embodiments, another part of the range value is associated with another PUSCH configuration.
[0452] According to various embodiments, different methods of indicating PUSCH configuration selection are provided.
[0453] According to various embodiments, for the two configurations, different preamble groups are used for different configuration instructions.
[0454] According to various embodiments, the maximum number of settings is defined as follows:
[0455] For a terminal in RRC_IDLE / INACTIVE state, more than one message A PUSCH configuration is not supported for REL.16.
[0456] -For terminals in RRC_ACTIVE state:
[0457] --Up to two message A PUSCH configurations are supported within the UL BWP.
[0458] ---Message A If the PUSCH configuration is not configured for UL BWP, the initial BWP configuration may be followed.
[0459] ---The preamble group based method defined for the RRC_IDLE / INACTIVE state is used.
[0460] ---The number of message A PUSCH configurations may or may not match that of the terminal in RRC_IDLE / INACTIVE state.
[0461] --- Either the PRACH configuration and / or the message A PUSCH configuration is BWP specific and / or cell-specific.
[0462] According to various embodiments, preamble group A and preamble group B for 2-step RACH are introduced.
[0463] According to various embodiments, the selection formulas for the 4-step RACH of REL.15 are used to select between the 2-step RACH preamble groups A and B.
[0464] According to various embodiments, for the date threshold, a ra-MsgASizeGroupA (ra-MsgA-SizeGroupA) parameter is introduced.
[0465] According to various embodiments, ra-MsgASizeGroupA (ra-MsgA-SizeGroupA) is defined as shown in Table 15 below.
[0466] [Table 16]
[0467] According to various embodiments, the preamble in the CBRA is used to indicate the PUSCH configuration.
[0468] According to various embodiments, two preamble groups (eg, group A and group B) in the CBRA are used to indicate message size.
[0469] According to various embodiments, if 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 for preamble groups A and B, different sizes of time / frequency resources are allocated for each PUSCH in different PUSCH configurations. According to various embodiments, the terminal may select a preamble group and a PUSCH configuration depending on the TBS size to be transmitted.
[0470] According to various embodiments, if the network does not operate preamble groups A and B, the preamble groups are used only when instructing PUSCH configuration. According to various embodiments, the configured PUSCH resources may have different MCS levels for the same TBS size, so that the terminal can select the preamble group depending on the channel condition (e.g., based on RSRP, etc.).
[0471] intra-slot frequency hopping and guard band
[0472] According to various embodiments, intra-slot hopping is configured without a guard period within a PO.
[0473] According to various embodiments, intra-slot hopping is supported for message A PUSCH.
[0474] According to various embodiments, PRB-level guard banding between FDMed PUSCH opportunities consisting of only {0, 1} PRB values is supported.
[0475] According to various embodiments, per-PO intra-slot hopping for message A is configured using a per-message A configuration.
[0476] According to various embodiments, the hopping pattern is based on the hopping pattern of message 3 of REL.15.
[0477] According to various embodiments, UL-BWP specific parameters are used.
[0478] According to various embodiments, guard intervals between hops are used and / or not.
[0479] According to various embodiments, the POs in time are continuous and / or discontinuous.
[0480] According to various embodiments, guard intervals between hops may and / or may not be used. According to various embodiments, the use of guard intervals between hops may and / or may not be permitted.
[0481] According to various embodiments, frequency diversity gain is obtained from slot hopping.
[0482] For example, when a guard time is set, a guard time interval of twice the length is required within the PO. For example, compared with frequency diversity gain and energy loss, intra-slot hopping may not provide performance gain. In view of this, preferably, according to various embodiments, slot hopping may be set without a guard interval within the PO.
[0483] 3.3.mapping for RACH preamble and PUSCH resource
[0484] RO mapping / RACH preamble configuration for 2-step RACH
[0485] According to various embodiments, the RO is configured / mapped based on whether RO sharing is allowed between the 2-step RACH and the 4-step RACH.
[0486] According to various embodiments, for the case of separate ROs for 2-step RACH and 4-step RACH, a configuration is allowed where a subset of intra-slot ROs are used.
[0487] According to various embodiments, for the case of separate RO for 2-step RACH and 4-step RACH, a configuration is allowed in which the OFDM symbol in the first half RACH slot is used as the RO.
[0488] According to various embodiments, parameters are introduced to update / reconfigure parameter values set by the RACH configuration, e.g., parameters are introduced to update / reconfigure the number of ROs in a slot, the starting OFDM symbol, etc.
[0489] For example, RO sharing is performed between a two-step RACH procedure and a four-step RACH procedure. For example, a PRACH preamble for a four-step RACH procedure and a PRACH preamble for a two-step RACH procedure are configured / specified separately. For example, a PRACH preamble for a four-step RACH procedure and a PRACH preamble for a two-step RACH procedure are configured / specified separately in both cases where RO sharing is allowed and not allowed.
[0490] For example, if 64 PRACH preambles are allocated for a contention-based voluntary access procedure, the first 32 PRACH preambles are set / designated as PRACH preambles for a 4-step RACH procedure, and the last 32 PRACH preambles are set / designated as PRACH preambles for a 2-step RACH procedure. For example, the corresponding setting / indication is based on the RACH configuration included in the system information block type 1 (SIB1) and / or UE-specific RRC signaling.
[0491] For example, the PRACH preamble can be understood as a code-domain resource and can be distinguished based on the root index of the preamble. For example, a base station receiving a PRACH preamble can determine whether the corresponding PRACH preamble is a PRACH preamble for a 4-step RACH and / or a PRACH preamble for a 2-step RACH, and can identify whether the terminal that transmitted the PRACH preamble has initiated a 2-step RACH procedure and / or a 4-step RACH procedure.
[0492] On the other hand, for example, when RO sharing is not allowed (RO separate), the RO for the 4-step RACH procedure and the RO for the 2-step RACH procedure are distinguished, and the base station can identify whether the terminal that transmitted the PRACH preamble has initiated a 2-step RACH procedure and / or a 4-step RACH procedure based on the corresponding RO.
[0493] According to various embodiments, in an RO configured for a (contention-based) 4-step RACH, a PRACH preamble for a (contention-based) 2-step RACH may be configured among the remaining PRACH preambles (outside the PRACH preamble for the 4-step RACH). According to various embodiments, the purpose of the PRACH transmission (e.g., whether it is for a 2-step RACH and / or for a 4-step RACH) is identified from the base station. According to various embodiments, since the PRACH preamble is distinguished into one for a 2-step RACH and one for a 4-step RACH, the base station can identify whether the PRACH transmission is for a 2-step RACH or a 4-step RACH from the PRACH preamble.
[0494] According to various embodiments, in case of RO sharing, the PUSCH in message A is assigned to a PUSCH slot after the RACH slot.
[0495] According to various embodiments, if RO sharing is not allowed, an RO for the 2-step RACH is configured. According to various embodiments, for RO configuration for the 2-step RACH, one of two methods can be considered:
[0496] -1) Slot level TDM / slot level multiplexing: According to various embodiments, the RACH configuration table for the 4-step RACH is reused. For example, the RACH configuration table is reused for the RACH slot or the second (2 nd) is designed under the assumption that most of the OFDM symbols in the RACH half-slot are used as RO. Therefore, in this case, for example, RO and PUSCH can be multiplexed in different slots.
[0497] -2) Symbol level TDM / symbol level multiplexing: According to various embodiments, the OFDM symbols in the first half RACH slot are set to be used as RO. According to various embodiments, the OFDM symbols after the RO are allocated for the PUSCH of message A.
[0498] 21 is a diagram illustrating an example of a message A configuration according to various embodiments. FIG 21 illustrates an example of a scheme in which the RO for message A and the PUSCH for message A described above are slot-level multiplexed.
[0499] Referring to FIG. 21, the RO for transmitting the PRACH preamble included in message A and the PUSCH opportunity for transmitting the PUSCH included in message A are TDMed at the slot level.
[0500] For example, the RO is included or mapped into a RACH slot that is located earlier than the PUSCH slot in the time domain. For example, the PUSCH opportunity is included or mapped into a PUSCH slot that is located later than the RACH slot in the time domain.
[0501] For example, within each slot, the RO and / or PUSCH opportunities may be multiplexed in different manners.
[0502] For example, FIG. 21(a) shows an example in which RO is TDM-modulated in a RACH slot, and PUSCH is FDM / TDM-modulated in a PUSCH slot.
[0503] For example, FIG. 21(b) shows an example in which RO is FDM / TDMed in a RACH slot, and PUSCH is FDMed in a PUSCH slot.
[0504] For example, FIG. 21(c) shows an example in which RO is FDM-modulated in a RACH slot and PUSCH is TDM-modulated in a PUSCH slot.
[0505] For example, FIG. 21(d) shows an example in which RO is TDM-modulated in a RACH slot, and PUSCH is TDM / CDM-modulated in a PUSCH slot.
[0506] For example, a certain time offset is set between the RO and the PUSCH opportunity in the time domain, i.e., for example, a certain time offset is set between the RACH slot including the RO and the PUSCH slot including the PUSCH opportunity in the time domain.
[0507] For example, the time offset may consist of a certain number of slots.
[0508] Conversely, if the time offset is not set, the RACH slot and the PUSCH slot may be consecutive in the time domain.
[0509] 22 is a diagram illustrating an example of a configuration of message A according to various embodiments. FIG 22 illustrates an example of a manner in which the RO for message A and the PUSCH for message A described above are symbol level multiplexed.
[0510] Referring to FIG. 22, the RO for transmitting the PRACH preamble included in message A and the PUSCH opportunity for transmitting the PUSCH included in message A are TDMed at the symbol level.
[0511] For example, the RO and PUSCH opportunities are contained within one slot.
[0512] For example, the RO is included or mapped into a RACH half-slot that is located earlier in the time domain than the PUSCH half-slot, and for example, the PUSCH opportunity is included or mapped into a PUSCH half-slot that is later in the time domain than the RACH half-slot.
[0513] For example, an RO may be included or mapped to one or more OFDM symbols within a RACH half-slot. For example, a PUSCH opportunity may be included or mapped to one or more OFDM symbols within a PUSCH half-slot.
[0514] For example, within each half-slot, the RO and / or PUSCH opportunities may be multiplexed in various manners.
[0515] For example, FIG. 22(a) shows an example in which one RO is configured in the RACH half-slot, and PUSCH is FDM-multiplexed in the PUSCH half-slot.
[0516] For example, FIG. 22(b) shows an example in which RO is FDM-modulated within a RACH half-slot and PUSCH is TDM-modulated within a PUSCH half-slot.
[0517] For example, FIG. 22(c) shows an example in which RO is TDM-modulated within a RACH half-slot and PUSCH is FDM / TDM-modulated within a PUSCH half-slot.
[0518] For example, FIG. 22(d) shows an example in which RO is FDM / TDMed in the RACH half-slot and PUSCH is TDM / CDMed in the PUSCH half-slot.
[0519] RACH Preamble to PRU mapping for 2-step RACH / periodicity
[0520] According to various embodiments, a (RACH Preamble to PRU) mapping is defined between message A RACH opportunities in interval A and message A PUSCH opportunities in interval B.
[0521] According to various embodiments, interval B is determined based on the SSB-to-RACH association interval, e.g., interval A has the same duration (length) as interval A, but the starting point is shifted to a single offset in the message A PUSCH configuration.
[0522] According to various embodiments, interval A is determined based on the SSB-to-RACH association interval, e.g., interval A is the same as the SSB-to-RACH association interval because the number of valid message A RACH opportunities within the SSB-to-RO association interval is identified.
[0523] According to various embodiments, a preamble in an available / valid RO of a RACH slot before an available / valid PO is mapped to a PRU in the available / valid PO.
[0524] According to various embodiments, the association interval for mapping SSB to RO can be applied to mapping RACH preamble to PRU. According to various embodiments, a preamble in an additional / valid RO in the association interval for mapping SSB to RO is mapped to a PRU in an additional / valid PO in the association interval.
[0525] According to various embodiments, one offset value for PO group position indication is allowed. According to various embodiments, if the period of a RACH and its PO group is the same, each RACH slot is mapped to a PO group.
[0526] According to various embodiments, the mapping rule between the RACH preamble and the PRU is defined as follows:
[0527] -0) Validation check related to whether PO is added or not
[0528] -1) The preamble in the additional RO of the RACH slot before the additional PO is mapped to the PRU in the additional PO.
[0529] -2) The preamble in the RO for use in period A is mapped to the PRU in the PO for use in period B.
[0530] --A) (One-to-one mapping) If the number of preambles for CBRA in a shared RO in interval A is the same as the number of PRUs in a shared PO in interval B, all preambles for CBRA are mapped to all PRUs.
[0531] --B) (Many-to-one mapping) If the number of preambles for CBRA in the associated RO in interval A is greater than the number of PRUs in the associated PO in interval B, all preambles for CBRA are mapped to all PRUs and / or a subset thereof. If a subset of PRUs is used, the remaining PRUs are not used for 2-step RACH.
[0532] --C) (One-to-one mapping with multiple cycles) If the number of preambles for CBRA in the additional RO in interval A is less than the number of PRUs in the additional PO in interval B, all preambles for CBRA are mapped to all PRUs and / or a subset thereof. If a subset of PRUs is used, the remaining PRUs are not used for 2-step RACH.
[0533] --If the set of ATSSs mapped to the RO in the SSB-to-RO association section is not fully mapped to the PRU in the additional PO in section B, the mapping of the preamble in the additional RO to the PRU in the additional PO is not applied.
[0534] --The remaining preambles for the two-step RACH that are not mapped to a PRU are used for message A preamble only transmission.
[0535] In many-to-one mapping, consecutive PRACH preambles (N consecutive PRACH preamble indices) are mapped to the same PRU, and then consecutive PRACH preambles (N consecutive PRACH preamble indices) are mapped to the next PRU.
[0536] For example, starting from frame 0, the association period for the SS / PBCH block to PRACH occasion mapping is the minimum value in the set determined by the PRACH configuration period according to Table 17.
[0537] [Table 17]
[0538] For example, a certain number of SS / PBCH blocks obtained from the value of ssb-PositionsInBurst indicating actually transmitted SSBs (ATSS) included in SIB1 and / or ServingCellConfigCommon (IE used to configure cell-specific parameters of the terminal's serving cell) are mapped to one or more PRACH opportunities within the association period. For example, within the association period, a certain number of SS / PBCH blocks are cyclically mapped to PRACH opportunities a certain integer number of times. For example, an association pattern period includes one or more association periods, and is determined such that a pattern between PRACH opportunities and SS / PBCH indices is repeated at most every 160 ms.
[0539] For example, for paired spectrum, all PRACH opportunities are available.
[0540] For example, for an unpaired spectrum:
[0541] - If tdd-UL-DL-ConfigurationCommon is not provided to the terminal, a PRACH opportunity in a PRACH slot is valid if it does not precede an SS / PBCH block in the PRACH slot and starts at least N symbols (N: integer or natural number) after the last SS / PBCH block received symbol, and if ChannelAccessMode-r16=semistatic is provided, it does not overlap with a set of consecutive symbols before the start of the next channel occupancy period in which the terminal does not transmit.
[0542] --Candidate SS / PBCH block indices for an SS / PBCH block correspond to the SS / PBCH block indices provided by ssb-PositionsInBurst.
[0543] When the terminal is provided with tdd-UL-DL-ConfigurationCommon, a PRACH opportunity in a PRACH slot is valid if any of the following conditions are met:
[0544] --Within the UL symbol, and / or
[0545] --Does not precede an SS / PBCH block in a PRACH slot, begins at least N symbols (N: integer or natural number) after the last DL symbol and at least N symbols (N: integer or natural number) after the last SS / PBCH block received symbol, and when ChannelAccessMode-r16=semistatic is provided, does not overlap with a set of consecutive symbols before the start of the next channel occupancy period during which no transmission takes place.
[0546] --Candidate SS / PBCH block indices for an SS / PBCH block correspond to the SS / PBCH block indices provided by ssb-PositionsInBurst.
[0547] FIG. 23 illustrates an example of time domain location for message A RACH and message A PUSCH in accordance with various embodiments.
[0548] 23, for example, assume that a UL slot is allocated every 2.5 ms, and the RACH is set to subframe index 9 within a 10 ms interval. For example, the PO group is set to a 2.5 ms offset and a 10 ms period.
[0549] According to various embodiments, two intervals for SSB-to-RO mapping (eg, an association interval and an association pattern interval) can be defined as the number of valid ROs in a RACH interval differs from each other.
[0550] According to various embodiments, the SSB-to-RO association interval is determined by comparing the number of SSBs and the number of valid ROs, and since the number of preambles per SSB is the same, the remaining RACH preambles in the mapping interval are not mapped to the SSBs.
[0551] According to various embodiments, for a 2-step RACH, a mapping of preambles to PRUs is provided taking into account the uniformity of the number of preambles and PRUs per SSB.
[0552] According to various embodiments, timely closed OFDM symbols are allocated for the message A preamble and the message A PUSCH to reduce delays due to mapping of the preamble to the PRU.
[0553] According to various embodiments, once valid message ARACH opportunities within interval A and valid message A PUSCH opportunities within interval B are determined, a mapping of preambles to PRUs is performed.
[0554] According to various embodiments, interval A is determined based on the SSB-to-RACH association interval, e.g., an available number of message A RACH opportunities within the SSB-to-RO association interval are identified, so interval A is the SSB-to-RACH association interval.
[0555] According to various embodiments, the mapping rule between the RACH preamble and the PRU is defined as follows:
[0556] -0) Validation check related to whether PO is added or not
[0557] --A) PO in flexible / UL slot is additional.
[0558] --B) The PO after the N-symbol (N: integer / natural number equal to or greater than 0) gap period from the last DL symbol is additive.
[0559] --C) PO that does not collide with SSB is additive.
[0560] -1) The preamble in the additional RO of the RACH slot before the additional PO is mapped to the PRU in the additional PO.
[0561] -2) The SSB to RO association section is applied to RACH preamble to PRU mapping.
[0562] --A) For SSB and RO mapping, the preamble in the additional RO in the associated section is mapped to the PRU in the additional PO in the associated section.
[0563] -3) If the number of preambles for CBRA in an additional RO in the associated interval is equal to or greater than the number of PRUs in an additional PO in the associated interval, all or a subset of preambles for CBRA are mapped to PRUs in the additional PO.
[0564] --A) If the set of actually transmitted SSBs mapped to the RO in the association section for SSB and RO mapping is not completely mapped to the PRU in the additional PO in the SSB association section, it may not apply that the preamble in the additional RO is mapped to the additional PRU in the additional PO.
[0565] --B) The remaining preambles for the 2-step RACH procedure that are not mapped to a PRU are used for message A preamble-only transmission.
[0566] And / or according to various embodiments, the mapping rule between the RACH preamble and the PRU is defined as follows:
[0567] -0) Validation check related to whether PO is added or not
[0568] -1) The preamble in the additional RO of the RACH slot before the additional PO is mapped to the PRU in the additional PO.
[0569] -2) A preamble in an additional RO in period A is mapped to a PRU in an additional PO in period B.
[0570] --A) (One-to-one mapping) If the number of preambles for CBRA in a shared RO in interval A is the same as the number of PRUs in a shared PO in interval B, all preambles for CBRA are mapped to all PRUs.
[0571] --B) (Many-to-one mapping) If the number of preambles for CBRA in the additional RO in period A is greater than the number of PRUs in the additional PO in period B, all preambles for CBRA are mapped to all PRUs and / or a subset thereof. If a subset of PRUs is used, the remaining PRUs may not be used for 2-step RACH.
[0572] --C) (One-to-one mapping with multiple cycles) If the number of preambles for CBRA in the additional RO in interval A is less than the number of PRUs in the additional PO in interval B, all preambles for CBRA are mapped to all PRUs and / or a subset thereof. If a subset of PRUs is used, the remaining PRUs may not be used for 2-step RACH.
[0573] --If the set of ATSSs mapped to the RO in the SSB-to-RO association section is not fully mapped to the PRU in the additional PO in section B, the mapping of the preamble in the additional RO to the PRU in the additional PO may not be applied.
[0574] --The remaining preambles for the two-step RACH that are not mapped to a PRU are used for message A preamble only transmission.
[0575] In case of many-to-one mapping, consecutive PRACH preambles(consecutive number of N PRACH preamble indexes) are mapped to same PRU, then next consecutive PRACH preambles(consecutive number of N PRACH preamble indexes) are mapped to next PRU. That is, each consecutive N PRACH preamble index of a valid PRACH opportunity in a PRACH slot is mapped to one PUSCH opportunity (and associated DMRS resource). According to various embodiments, the number N of consecutive PRACH preamble indexes is determined based on the number of valid PRACH opportunities and the number of valid PUSCH opportunities.
[0576] 3.4. Network Initial Connection and Communication Process
[0577] A terminal according to various embodiments performs a network access process to perform the above-described / proposed procedures and / or methods. For example, the terminal receives system information and configuration information required to perform the above-described / proposed procedures and / or methods while accessing a network (e.g., a base station) and stores the information in a memory. The configuration information required for this disclosure is received by higher layer (e.g., RRC layer; Medium Access Control, MAC, layer, etc.) signaling.
[0578] FIG. 24 is a diagram illustrating a simple network initial connection and subsequent communication process according to various embodiments. In an NR system to which various embodiments can be applied, physical channels and reference signals are transmitted using beam-forming. When beam-forming based signal transmission is supported, a beam management process is involved in aligning beams between a base station and a terminal. In addition, signals proposed in various embodiments are transmitted / received using beam-forming. In RRC (Radio Resource Control) IDLE mode, beam alignment is performed based on SSB (or SS / PBCH block). On the other hand, in RRC CONNECTED mode, beam alignment is performed based on CSI-RS (in DL) and SRS (in UL). Meanwhile, when beam-forming based signal transmission is not supported, operations related to beams can be omitted in the following description.
[0579] As shown in FIG. 24, a base station (e.g., BS) periodically transmits an SSB (2702). Here, the SSB includes PSS / SSS / PBCH. The SSB is transmitted using beam sweeping. Then, the base station transmits RMSI (Remaining Minimum System Information) and OSI (Other System Information) (2704). The RMSI includes information (e.g., PRACH configuration information) required for the terminal to initially connect to the base station. Meanwhile, the terminal identifies the best SSB after performing SSB detection. Then, the terminal transmits a RACH preamble (Message 1, Msg1) to the base station using a PRACH resource linked / corresponding to the index (i.e., beam) of the best SSB (2706). The beam direction of the RACH preamble is associated with the PRACH resource. The association between the PRACH resource (and / or RACH preamble) and the SSB (index) is set by system information (e.g., RMSI). Thereafter, as part of the RACH process, the base station sends a Random Access Response (RAR) (Msg2) in response to the RACH preamble (2708), the terminal uses the UL grant in the RAR to send Msg3 (e.g., an RRC Connection Request) (2710), and the base station sends a contention resolution message (Msg4) (2712), which includes the RRC Connection Setup.
[0580] Once an RRC connection is established between the base station and the terminal through the RACH process, subsequent beam alignment is performed based on SSB / CSI-RS (in DL) and SRS (in UL). For example, the terminal receives SSB / CSI-RS (2714). The SSB / CSI-RS is used by the terminal to generate a beam / CSI report. Meanwhile, the base station requests the terminal to send a beam / CSI report via DCI (2716). In this case, the terminal generates a beam / CSI report based on the SSB / CSI-RS and transmits the generated beam / CSI report to the base station via PUSCH / PUCCH (2718). The beam / CSI report includes information on the preferred beam, etc., based on the beam measurement result. The base station and the terminal switch beams based on the beam / CSI report (2720a, 2720b).
[0581] Then, the terminal and the base station perform the above-mentioned / proposed procedures and / or methods. For example, the terminal and the base station process information in the memory according to various embodiments based on configuration information obtained from a network connection process (e.g., a system information acquisition process, an RRC connection process via RACH, etc.) to transmit a radio signal, or process a received radio signal and store it in the memory. Here, the radio signal includes any one of a PDCCH, a PDSCH, and a Reference Signal (RS) in the downlink, and any one of a PUCCH, a PUSCH, and an SRS in the uplink.
[0582] And / or the terminal and base station may perform the procedures and / or methods described / suggested above as at least part of the initial access procedure described above.
[0583] The above initial connection process can be combined with the contents of 1. to 3. above to form further various embodiments of this disclosure, which can be clearly understood by a person having ordinary skill in the art.
[0584] FIG. 25 is a simplified diagram illustrating the operation of a terminal and a base station in accordance with various embodiments.
[0585] FIG. 26 is a flow chart illustrating a method of operating a terminal in accordance with various embodiments.
[0586] FIG. 27 is a flow chart illustrating a method of operating a base station in accordance with various embodiments.
[0587] 25 to 27, in various embodiments, a terminal may transmit a PRACH preamble and a base station may receive it in operations 2501, 2601, and 2701. According to various embodiments, the PRACH preamble may be transmitted or received within any valid PRACH opportunity among multiple valid PRACH opportunities within a PRACH slot.
[0588] In operations 2503, 2603, 2703 according to various embodiments, the base station transmits information related to the RAR, which the terminal can receive.
[0589] According to various embodiments, the PRACH preamble is included in multiple PRACH preambles associated with multiple valid PRACH opportunities.
[0590] According to various embodiments, multiple PRACH preambles may be mapped to a first PUSCH opportunity among multiple valid PUSCH opportunities, based on multiple consecutive PRACH preambles included in multiple PRACH prints being mapped to one valid PUSCH opportunity.
[0591] It is obvious that the above-mentioned proposed method may be included as one of various embodiments and may be regarded as a kind of proposed method. Also, the above-mentioned proposed method may be implemented independently or may be implemented in the form of a combination (or merging) of some of the proposed methods. A rule may be defined so that the base station notifies the terminal of information on whether the proposed method is applied (or information on the rule of the proposed method) through a predefined signal (e.g., a physical layer signal or a higher layer signal) by the terminal.
[0592] 4. Device configuration examples for implementing various embodiments
[0593] 4.1. Examples of device configurations to which various embodiments are applied
[0594] FIG. 28 shows an apparatus in which various embodiments may be implemented.
[0595] The device shown in FIG. 28 may be a user equipment (UE) and / or a base station (e.g., eNB or gNB) adapted to perform the above-mentioned mechanisms, or may be any device performing the same tasks.
[0596] 28, the device includes a DSP (Digital Signal Processor) / microprocessor 210 and an RF (Radio Frequency) module (transmitter / receiver; 235). The DSP / microprocessor 210 is electrically connected to and controls the transceiver 235. In addition, the device may also include a power management module 255, a battery 215, 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, depending on the designer's choice.
[0597] In particular, Figure 28 may show a terminal including a receiver 235 configured to receive messages from a network and a transmitter 235 configured to transmit transmission and reception timing information to the network. Such a receiver and transmitter constitute the transceiver 235. The terminal may further include a processor 210 coupled to the transceiver 235.
[0598] 28 may also show a network device including a transmitter 235 configured to transmit a request message to a terminal and a receiver 235 configured to receive transmit and receive timing information from the terminal. The transmitter and receiver constitute the transceiver 235. The network further includes a processor 210 coupled to the transmitter and receiver. The processor 210 may calculate a delay based on the transmit and receive timing information.
[0599] Thus, a processor included in a terminal (or a communication device included in a terminal) and a base station (or a communication device included in a base station) according to various embodiments controls a memory to operate as follows.
[0600] In various embodiments, a terminal or base station includes one or more transceivers, one or more memories, and one or more processors coupled to the transceivers and the memories. The memories store instructions that cause the one or more processors to perform the following operations:
[0601] In this case, the communication device included in the terminal or base station is configured to include one or more processors and one or more memories, or the communication device is configured to include one or more transceivers or not include one or more transceivers but be connected to one or more transceivers.
[0602] According to various embodiments, one or more processors included in the terminal (or one or more processors in a communication device included in the terminal) transmit a PRACH preamble within any one of a plurality of valid PRACH opportunities within a PRACH slot.
[0603] According to various embodiments, one or more processors included in the terminal may obtain / receive information related to the RAR in response to the PRACH preamble.
[0604] According to various embodiments, the PRACH preamble is included in multiple PRACH preambles associated with multiple valid PRACH opportunities.
[0605] According to various embodiments, the multiple PRACH preambles are mapped to a first PUSCH opportunity among the multiple valid PUSCH opportunities, based on mapping multiple consecutive PRACH preambles included in the multiple PRACH preambles to one valid PUSCH opportunity.
[0606] According to various embodiments, one or more processors included in the base station (or one or more processors of a communication device included in the base station) may receive a PRACH preamble within any valid PRACH opportunity among multiple valid PRACH opportunities within a PRACH slot.
[0607] According to various embodiments, one or more processors included in the base station can transmit information related to the RAR in response to the PRACH preamble.
[0608] According to various embodiments, the PRACH preamble is included in multiple PRACH preambles associated with multiple valid PRACH opportunities.
[0609] According to various embodiments, the multiple PRACH preambles are mapped to a first PUSCH opportunity among the multiple valid PUSCH opportunities, based on which multiple consecutive PRACH preambles included in the multiple PRACH preambles are mapped to one valid PUSCH opportunity.
[0610] More specific operations of the processor included in the base station and / or terminal according to the various embodiments described above can be described and implemented based on the contents of 1. to 3. above.
[0611] In addition, various embodiments can be implemented in combination / combination with each other unless they contradict each other. For example, a base station and / or a terminal (such as a processor included in the base station and / or a terminal) according to various embodiments can operate in combination / combination with the above-mentioned embodiments 1 to 3 unless they contradict each other.
[0612] 4.2. Example of a Communication System in Which Various Embodiments May be Applied
[0613] Although the various embodiments are described with a focus on a data transmission / reception relationship between a base station and a terminal in a wireless communication system, the various embodiments are not limited thereto. For example, the various embodiments are also related to the following technical configurations.
[0614] Without being limited thereto, the description, functions, procedures, suggestions, methods and / or flow charts of various embodiments may be applied to various fields requiring wireless communication / connection between devices (e.g., 5G).
[0615] Hereinafter, a more detailed description will be given with reference to the drawings. In the following drawings / description, the same reference numerals denote the same or corresponding hardware blocks, software blocks or function blocks, unless otherwise specified.
[0616] FIG. 29 illustrates a communication system in which various embodiments may be applied.
[0617] Referring to FIG. 29, a communication system 1 applied to various embodiments includes a wireless device, a base station, and a network. Here, the wireless device means a device that communicates using a wireless connection technology (e.g., 5G NR, LTE), and is also referred to as a communication / wireless / 5G device. The wireless device includes, but is not limited to, a robot 100a, a vehicle 100b-1, 100b-2, an XR (eXtended Reality) device 100c, a handheld device (Hand-held Device) 100d, a home appliance 100e, an IoT (Internet of Thing) device 100f, and an AI device / server 400. For example, the vehicle includes a vehicle equipped with a wireless communication function, an autonomous vehicle, a vehicle capable of inter-vehicle communication, and the like. Here, the vehicle includes a UAV (Unmanned Aerial Vehicle) (e.g., a drone). XR devices include Augmented Reality (AR) / Virtual Reality (VR) / Mixed Reality (MR) devices, and are embodied in the form of Head-Mounted Devices (HMDs), Head-Up Displays (HUDs) mounted on vehicles, TVs, smartphones, computers, wearable devices, home appliances, digital billboards, vehicles, robots, etc. Portable devices include smartphones, smart pads, wearable devices (e.g., smart watches, smart glasses), computers (e.g., notebook computers, etc.), etc. Home appliances include TVs, refrigerators, washing machines, etc. IoT devices include sensors, smart meters, etc. For example, base stations and networks may also be embodied as wireless devices, and a specific wireless device 200a may operate as a base station / network node for other wireless devices.
[0618] The wireless devices 100a to 100f are connected to a network 300 via a base station 200. AI (Artificial Intelligence) technology is applied to the wireless devices 100a to 100f, and the wireless devices 100a to 100f are connected to an AI server 400 via the network 300. The network 300 is configured using a 3G network, a 4G (e.g., LTE) network, or a 5G (e.g., NR) network. The wireless devices 100a to 100f can communicate with each other via the base station 200 / network 300, but can also communicate directly without going through the base station / network (e.g., sidelink communication). For example, the vehicles 100b-1 and 100b-2 can communicate directly (e.g., V2V (Vehicle to Vehicle) / V2X (Vehicle to everything) communication). Also, an IoT device (e.g., a sensor) can directly communicate with another IoT device (e.g., a sensor) or another wireless device 100a to 100f.
[0619] Wireless communication / connections 150a, 150b, and 150c are performed between the wireless devices 100a to 100f / base stations 200 and the base stations 200. Here, the wireless communication / connections are performed by various wireless connection technologies such as uplink / downlink communication 150a and sidelink communication 150b (or D2D communication) and inter-base station communication 150c (e.g., relay, IAB (Integrated Access Backhaul) (e.g., 5G NR). Through the wireless communication / connections 150a, 150b, and 150c, the wireless devices and base stations, and the base stations and base stations can transmit / receive wireless signals to each other. For example, the wireless communication / connections 150a, 150b, and 150c can transmit / receive signals via various physical channels. To this end, any one of various configuration information setting processes for transmitting / receiving wireless signals, various signal processing processes (e.g., channel coding / decoding, modulation / demodulation, resource mapping / demapping, etc.), and resource allocation processes is performed based on various proposals of the present invention.
[0620] 4.2.1 Examples of Wireless Devices to which Various Embodiments May Apply
[0621] FIG. 30 illustrates a wireless device that can be used in various embodiments.
[0622] 30, a first wireless device 100 and a second wireless device 200 transmit and receive wireless signals using various wireless access technologies (e.g., LTE, NR), where {first wireless device 100, second wireless device 200} corresponds to {wireless device 100x, base station 200} and / or {wireless device 100x, wireless device 100x} in FIG.
[0623] The first wireless device 100 includes one or more processors 102 and one or more memories 104, and further includes one or more transceivers 106 and / or one or more antennas 108. The processor 102 is configured to control the memory 104 and / or the transceiver 106 to implement the descriptions, functions, procedures, suggestions, methods, and / or flowcharts of various embodiments. For example, the processor 102 processes information in the memory 104 to generate a first information / signal, and then transmits a wireless signal including the first information / signal via the transceiver 106. The processor 102 also receives a wireless signal including a second information / signal via the transceiver 106, and then stores information obtained from signal processing of the second information / signal in the memory 104. The memory 104 is coupled to the processor 102 and stores various information related to the operation of the processor 102. For example, the memory 104 stores software code including instructions for performing some or all of the processes controlled by the processor 102 or for performing the descriptions, functions, procedures, suggestions, methods, and / or flowcharts disclosed herein. Here, the processor 102 and memory 104 are part of a communication modem / circuit / chip designed to implement a wireless communication technology (e.g., LTE, NR). The transceiver 106 is coupled to the processor 102 and transmits and / or receives wireless signals via one or more antennas 108. The transceiver 106 includes a transmitter and / or a receiver. The transceiver 106 may also be referred to as an RF (radio frequency) unit. In the present invention, a wireless device may also refer to a communication modem / circuit / chip.
[0624] The second wireless device 200 includes one or more processors 202 and one or more memories 204, and further includes one or more transceivers 206 and / or one or more antennas 208. The processor 202 is configured to control the memory 204 and / or the transceiver 206 to implement the descriptions, functions, procedures, suggestions, methods, and / or flowcharts disclosed herein. For example, the processor 202 processes information in the memory 204 to generate a third information / signal, and then transmits a wireless signal including the third information / signal via the transceiver 206. The processor 202 also receives a wireless signal including a fourth information / signal via the transceiver 206, and then stores information obtained from the signal processing of the fourth information / signal in the memory 204. The memory 204 is coupled to the processor 202 and stores various information related to the operation of the processor 202. For example, the memory 204 stores software code including instructions for performing some or all of the processes controlled by the processor 202 or for performing the descriptions, functions, procedures, suggestions, methods, and / or flowcharts according to various embodiments. Here, the processor 202 and memory 204 are part of a communication modem / circuit / chip designed to implement a wireless communication technology (e.g., LTE, NR). The transceiver 206 is coupled to the processor 202 and transmits and / or receives wireless signals via one or more antennas 208. The transceiver 206 includes a transmitter and / or a receiver. The transceiver 206 may also be referred to as an RF unit. In the present invention, a wireless device may also refer to a communication modem / circuit / chip.
[0625] The hardware elements of the wireless device 100, 200 are described in more detail below. One or more protocol layers may be implemented by one or more processors 102, 202, without limitation. For example, one or more processors 102, 202 may implement one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, SDAP). One or more processors 102, 202 may generate one or more protocol data units (PDUs) and / or one or more service data units (SDUs) according to the descriptions, functions, procedures, suggestions, methods, and / or flowcharts of various embodiments. One or more processors 102, 202 may generate messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods, and / or flowcharts of various embodiments. One or more processors 102, 202 may generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information according to the functions, procedures, suggestions, and / or methods of various embodiments, and provide the signals to one or more transceivers 106, 206. One or more processors 102, 202 may receive signals (e.g., baseband signals) from one or more transceivers 106, 206 and obtain PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods and / or flowcharts of various embodiments.
[0626] The one or more processors 102, 202 may also be referred to as a controller, microcontroller, microprocessor, or microcomputer. The one or more processors 102, 202 may be implemented using hardware, firmware, software, or a combination thereof. As an example, one or more application specific integrated circuits (ASICs), one or more digital signal processors (DSPs), one or more digital signal processing devices (DSPDs), one or more programmable logic devices (PLDs), or one or more field programmable gate arrays (FPGAs) may be included in the one or more processors 102, 202. The descriptions, functions, procedures, suggestions, methods, and / or flowcharts of various embodiments may be implemented using firmware or software, and the firmware or software may be implemented to include modules, procedures, functions, and the like. Firmware or software configured to perform the descriptions, functions, procedures, suggestions, methods, and / or flowcharts of various embodiments may be included in the one or more processors 102, 202, or may be stored in one or more memories 104, 204 and executed by the one or more processors 102, 202. The descriptions, functions, procedures, suggestions, methods and / or flow charts according to various embodiments may be implemented using firmware or software in the form of code, instructions and / or sets of instructions.
[0627] The one or more memories 104, 204 are coupled to the one or more processors 102, 202 and store various types of data, signals, messages, information, programs, code, instructions, and / or commands. The one or more memories 104, 204 may be comprised of ROM, RAM, EPROM, flash memory, hard drives, registers, cache memory, computer readable storage media, and / or combinations thereof. The one or more memories 104, 204 may be located internal and / or external to the one or more processors 102, 202. Additionally, the one or more memories 104, 204 may be coupled to the one or more processors 102, 202 via various techniques, such as wired or wireless connections.
[0628] The one or more transceivers 106, 206 may transmit user data, control information, wireless signals / channels, etc., as described in the methods and / or flow charts according to various embodiments to one or more other devices. The one or more transceivers 106, 206 may receive user data, control information, wireless signals / channels, etc., as described in the descriptions, functions, procedures, suggestions, methods and / or flow charts according to various embodiments from one or more other devices. For example, the one or more transceivers 106, 206 may be coupled to one or more processors 102, 202 to transmit and receive wireless signals. For example, the one or more processors 102, 202 may control the one or more transceivers 106, 206 to transmit user data, control information, or wireless signals to one or more other devices. Also, the one or more processors 102, 202 may control the one or more transceivers 106, 206 to receive user data, control information, or wireless signals from one or more other devices. The one or more transceivers 106, 206 are coupled to one or more antennas 108, 208, and the one or more transceivers 106, 206 are configured to transmit and receive user data, control information, radio signals / channels, etc., via the one or more antennas 108, 208, as described, functions, procedures, suggestions, methods and / or flow charts according to various embodiments. In various embodiments, the one or more antennas are multiple physical antennas or multiple logical antennas (e.g., antenna ports). The one or more transceivers 106, 206 convert the received user data, control information, radio signals / channels, etc., from RF band signals to baseband signals for processing by the one or more processors 102, 202. The one or more transceivers 106, 206 convert the user data, control information, radio signals / channels, etc., processed by the one or more processors 102, 202, from baseband signals to RF band signals. To this end, the one or more transceivers 106, 206 include (analog) oscillators and / or filters.
[0629] According to various embodiments, one or more memories (e.g., 104 or 204) store instructions or programs that, when executed, cause one or more processors operatively coupled to the one or more memories to perform operations according to various embodiments or implementations.
[0630] According to various embodiments, a computer-readable storage medium stores one or more instructions or computer programs that, when executed by one or more processors, cause the one or more processors to perform operations according to various embodiments or implementations.
[0631] According to various embodiments, a processing device or apparatus includes one or more processors and one or more computer memories coupled to the one or more processors, the one or more computer memories storing instructions or programs that, when executed, cause the one or more processors operably coupled to the one or more memories to perform operations according to various embodiments or implementations.
[0632] 4.2.2. Examples of Wireless Devices to which Various Embodiments May be Applied
[0633] 31 illustrates another example of a wireless device to which various embodiments may be applied. The wireless device may be embodied in various forms depending on the use case / service (see FIG. 29).
[0634] Referring to Fig. 31, the wireless device 100, 200 corresponds to the wireless device 100, 200 of Fig. 30 and is composed of various elements, components, units / parts and / or modules. For example, the wireless device 100, 200 includes a communication unit 110, a control unit 120, a memory unit 130 and an additional element 140. The communication unit includes a communication circuit 112 and a transceiver 114. For example, the communication circuit 112 includes one or more processors 102, 202 and / or one or more memories 104, 204 in Fig. 30. For example, the transceiver 114 includes one or more transceivers 106, 206 and / or one or more antennas 108, 208 in Fig. 30. The control unit 120 is electrically connected to the communication unit 110, the memory unit 130 and the additional element 140 and controls the overall operation of the wireless device. For example, the control unit 120 controls the electrical / mechanical operation of the wireless device based on the program / code / instruction / information stored in the memory unit 130. In addition, the control unit 120 transmits information stored in the memory unit 130 to the outside (e.g., other communication device) via the communication unit 110 via a wireless / wired interface, or stores information received from the outside (e.g., other communication device) via the wireless / wired interface in the memory unit 130.
[0635] The additional element 140 may be configured in various ways depending on the type of wireless device. For example, the additional element 140 may include any one of a power unit / battery, an input / output unit (I / O unit), a driving unit, and a computer unit. The wireless device may be embodied in the form of, but not limited to, a robot (FIG. 29, 100a), a vehicle (FIG. 29, 100b-1, 100b-2), an XR device (FIG. 29, 100c), a mobile device (FIG. 29, 100d), a home appliance (FIG. 29, 100e), an IoT device (FIG. 29, 100f), a digital broadcasting terminal, a hologram device, a public safety device, an MTC device, a medical device, a Fintech device (or a financial device), a security device, a climate / environment device, an AI server / device (FIG. 29, 400), a base station (FIG. 29, 200), and a network node. The wireless device may be mobile or fixed depending on the use case / service.
[0636] In FIG. 31, various elements, components, units / parts and / or modules in the wireless devices 100 and 200 are connected to each other by a wired interface as a whole, or at least some of them are connected wirelessly by the communication unit 110. For example, in the wireless devices 100 and 200, the control unit 120 and the communication unit 110 are connected by wire, and the control unit 120 and a first unit (e.g., 130, 140) are connected wirelessly by the communication unit 110. Also, each element, component, unit / part and / or module in the wireless devices 100 and 200 further includes one or more elements. For example, the control unit 120 is configured with a set of one or more processors. For example, the control unit 120 is configured with a set of a communication control processor, an application processor, an ECU (Electronic Control Unit), a graphics processor, a memory control processor, etc. As another example, the memory unit 130 may be composed of 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.
[0637] Hereinafter, this embodiment will be described in more detail with reference to FIG.
[0638] 4.2.3. Examples of Mobile Devices to which Various Embodiments May be Applied
[0639] 33 illustrates a mobile device applied to various embodiments. The mobile device includes a smart phone, a smart pad, a wearable device (e.g., a smart watch, a smart glass), and a mobile computer (e.g., a notebook computer, etc.). The mobile device is also called 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).
[0640] 32, the portable device 100 includes 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 input / output unit 140c. The antenna unit 108 is configured as a part of the communication unit 110. Blocks 110 to 130 / 140a to 140c correspond to blocks 110 to 130 / 140 in FIG. 31, respectively.
[0641] The communication unit 110 transmits and receives signals (e.g., data, control signals, etc.) to and from other wireless devices and base stations. The control unit 120 controls the components of the portable device 100 to perform various operations. The control unit 120 includes an AP (Application Processor). The memory unit 130 stores data / parameters / programs / codes / commands required to operate the portable device 100. The memory unit 130 also stores input / output data / information, etc. The power supply unit 140a supplies power to the portable device 100 and includes wired / wireless charging circuits, a battery, etc. The interface unit 140b supports connection between the portable device 100 and other external devices. The interface unit 140b includes various ports (e.g., audio input / output ports, video input / output ports) for connection with external devices. The input / output unit 140c inputs or outputs video information / signals, audio information / signals, data, and / or information input by a user. The input / output unit 140c may include a camera, a microphone, a user input unit, a display unit 140d, a speaker, and / or a haptic module.
[0642] As an example, in the case of data communication, the input / output unit 140c obtains information / signals (e.g., touch, text, voice, image, video) input by a user, and the obtained information / signals are stored in the memory unit 130. The communication unit 110 converts the information / signals stored in the memory into wireless signals, and transmits the converted wireless signals directly to another wireless device or to a base station. The communication unit 110 also receives wireless signals from another wireless device or a base station, and then restores the received wireless signals to the original information / signals. The restored information / signals are stored in the memory unit 130, and then output in various forms (e.g., text, voice, image, video, tactile sensation) by the input / output unit 140c.
[0643] 4.2.4. Examples of Vehicles or Autonomous Vehicles to which Various Embodiments May Apply
[0644] 33 illustrates an example of a vehicle or an autonomous vehicle to which the present invention is applied. The vehicle or the autonomous vehicle may be realized as a mobile robot, a car, a train, an aerial vehicle (AV), a ship, or the like.
[0645] 33, a vehicle or autonomous vehicle 100 includes 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 is configured as a part of the communication unit 110. Blocks 110 / 130 / 140a to 140d correspond to blocks 110 / 130 / 140 in FIG. 31, respectively.
[0646] The communication unit 110 transmits and receives signals (e.g., data, control signals, etc.) to and from external devices such as other vehicles, base stations (e.g., base stations, road side units, etc.), and servers. The control unit 120 controls elements of the vehicle or autonomous vehicle 100 to perform various operations. The control unit 120 includes an ECU (Electronic Control Unit). The driving unit 140a causes the vehicle or autonomous vehicle 100 to run on the ground. The driving unit 140a includes an engine, a motor, a power train, wheels, brakes, a steering device, etc. The power supply unit 140b supplies power to the vehicle or autonomous vehicle 100 and includes wired / wireless charging circuits, a battery, etc. The sensor unit 140c can obtain vehicle status, surrounding environment information, user information, etc. The sensor unit 140c includes an IMU (inertial measurement unit) sensor, a collision sensor, a wheel sensor, a speed sensor, a tilt sensor, a weight sensor, a heading sensor, a position 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, an illuminance sensor, a pedal position sensor, etc. The autonomous driving unit 140d embodies a technology for maintaining a lane while driving, a technology for automatically adjusting speed such as an adaptive cruise control, a technology for automatically driving according to a predetermined route, a technology for automatically setting a route when a destination is set, and the like.
[0647] For example, the communication unit 110 receives map data, traffic information data, etc. from an external server. The autonomous driving unit 140d generates an autonomous driving route and a drive plan based on the obtained data. The control unit 120 controls the driving unit 140a (e.g., speed / direction adjustment) so that the vehicle or autonomous driving vehicle 100 moves along the autonomous driving route according to the drive plan. The communication unit 110 non-periodically obtains the latest traffic information data from an external server during autonomous driving, and also obtains surrounding traffic information data from surrounding vehicles. In addition, the sensor unit 140c obtains vehicle status and surrounding environment information during autonomous driving. The autonomous driving unit 140d updates the autonomous driving route and the drive plan based on the newly obtained data / information. The communication unit 110 transmits information regarding the vehicle position, the autonomous driving route, the drive plan, etc. to the external server. The external server can predict traffic information data in advance using AI technology, etc. based on information collected from the vehicle or autonomous driving vehicle, and provide the predicted traffic information data to the vehicle or autonomous driving vehicle.
[0648] In summary, various embodiments may be implemented by certain devices and / or terminals.
[0649] For example, certain devices may be a base station, a network node, a transmitting terminal, a receiving terminal, a wireless device, a wireless communication device, a vehicle, a vehicle with an autonomous driving function, a drone (unmanned aerial vehicle, UAV), an AI (artificial intelligence, AI) module, a robot, an AR (augmented reality) device, a VR (virtual reality) device, or other devices.
[0650] For example, the terminal may be a personal digital assistant (PDA), a cellular phone, a personal communication service (PCS) phone, a Global System for Mobile (GSM) phone, a Wideband CDMA (WCDMA) phone, a Mobile Broadband System (MBS) phone, a smart phone, or a multi-mode multi-band (MM-MB) terminal.
[0651] Here, a smartphone is a terminal that combines the advantages of a mobile communication terminal and a personal portable terminal, and refers to a terminal that integrates the functions of a personal portable terminal, such as schedule management, facsimile transmission and reception, and data communication functions such as Internet connection, into a mobile communication terminal. Also, a multi-mode multi-band terminal refers to a terminal that has a built-in multi-modem chip and can operate in both the mobile Internet system and other mobile communication systems (e.g., CDMA (Code Division Multiple Access) 2000 system, WCDMA (Wideband CDMA) system, etc.).
[0652] In addition, terminals include notebook computers, handheld PCs, tablet PCs, ultrabooks, slate PCs, digital broadcasting terminals, portable multimedia players (PMPs), navigation systems, wearable devices such as smartwatches, smart glasses, and head mounted displays (HMDs). For example, a drone is an aircraft that does not carry a person and flies using a wireless control signal. For example, an HMD is a display device that is worn on the head. For example, an HMD is used to realize VR or AR.
[0653] The wireless communication technology in which various embodiments are embodied includes not only LTE, NR, and 6G, but also NB-IoT (Narrowband Internet of Things) for low power communication. In this case, for example, the NB-IoT technology is an example of LPWAN (Low Power Wide Area Network) technology and may be embodied in a standard such as LTE Cat (category) NB1 and / or LTE Cat NB2, and is not limited to the above-mentioned names. Additionally / alternatively, the wireless communication technology embodied in the wireless device according to various embodiments performs communication based on the LTE-M technology. In this case, as an example, the LTE-M technology is an example of LPWAN technology and may be called by various names such as eMTC (enhanced Machine Type Communication). For example, the LTE-M technology may be embodied in any one of various standards such as 1) LTE CAT0, 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 above-mentioned names. Additionally / alternatively, the wireless communication technology implemented in the wireless device according to various embodiments may include any of ZigBee (registered trademark), Bluetooth (registered trademark), and Low Power Wide Area Network (LPWAN) that consider low power communication, but are not limited to the above names. As an example, ZigBee technology creates personal area networks (PANs) related to small / low power digital communication based on various standards such as IEEE 802.15.4, and is called by various names.
[0654] Various embodiments may be implemented in various ways, such as in hardware, firmware, software, or any combination thereof.
[0655] When implemented in hardware, the methods according to embodiments of the present invention may be implemented using 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.
[0656] In the case of implementation by firmware or software, the methods according to various embodiments may be implemented in the form of modules, procedures, or functions that perform the functions or operations described above. For example, software code may be stored in a memory and executed by a processor. The memory unit may be provided inside or outside the processor and may exchange data with the processor by various means that are already known in the art.
[0657] Various embodiments may be embodied in other specific forms without departing from the technical ideas and essential features thereof. Therefore, the above detailed description should not be construed as limiting in any respect, but should be considered as illustrative. The scope of the present invention should be determined by a reasonable interpretation of the appended claims, and any modifications within the scope of the present invention are included in the scope of the present invention. In addition, claims that are not explicitly cited in the claims may be combined to form an embodiment, or may be included as a new claim by amendment after filing. [Industrial Applicability]
[0658] Various embodiments can be applied to various wireless access systems. Examples of various wireless access systems include 3GPP (3rd Generation Partnership Project) and 3GPP2 systems. Various embodiments can be applied to the various wireless access systems, as well as to all technical fields to which the various wireless access systems are applied. Furthermore, the proposed method can also be applied to mmWave communication systems that use ultra-high frequency bands.
Claims
1. A method performed by a user equipment (UE) in a wireless communication system, the method comprising: transmitting a message associated with a two-stage optional access procedure, the message including a physical random access channel (PRACH) preamble for at least one valid PRACH opportunity among a plurality of valid PRACH opportunities in a PRACH slot; and obtaining information related to a random access response (RAR) in response to the message; the PRACH preamble is included in a plurality of PRACH preambles associated with the plurality of valid PRACH opportunities; The message further includes a physical uplink shared channel (PUSCH) for at least one valid PUSCH opportunity among a plurality of valid PUSCH opportunities; The PUSCH is transmitted based on PUSCH configuration information associated with the two-stage optional access procedure; The PUSCH configuration information includes DM-RS configuration information regarding a demodulation reference signal (DM-RS) for the PUSCH, The method, wherein up to four DM-RS ports are configured based on the DM-RS configuration information including DM-RS port information.
2. A plurality of consecutive PRACH preambles included in the plurality of PRACH preambles are mapped to one of the plurality of valid PUSCH opportunities; 2. The method of claim 1, wherein the number of the plurality of consecutive PRACH preambles is determined based on a number of the plurality of PRACH preambles and the plurality of valid PUSCH opportunities.
3. the number of the PRACH preambles is the number of the PRACH preambles included in a first time period, the number of valid PUSCH opportunities is a number of valid PUSCH opportunities included in a second time period, The method of claim 1 , wherein the first time interval and the second time interval have the same time duration.
4. 1. An apparatus for operating in a wireless communication system, the apparatus comprising: Memory, at least one processor coupled to the memory; The at least one processor: transmitting a message associated with a two-stage optional access procedure, the message including a physical random access channel (PRACH) preamble for at least one valid PRACH opportunity among a plurality of valid PRACH opportunities in a PRACH slot; configured to obtain information related to a ransom access response (RAR) in response to the message; the PRACH preamble is included in a plurality of PRACH preambles associated with the plurality of valid PRACH opportunities; The message further includes a physical uplink shared channel (PUSCH) for at least one valid PUSCH opportunity among a plurality of valid PUSCH opportunities; The PUSCH is transmitted based on PUSCH configuration information associated with the two-stage optional access procedure; The PUSCH configuration information includes DM-RS configuration information regarding a demodulation reference signal (DM-RS) for the PUSCH, The apparatus, wherein up to four DM-RS ports are configured based on the DM-RS configuration information including DM-RS port information.
5. The device of claim 4 , wherein the device communicates with at least one of a mobile terminal, a network, and an autonomous vehicle other than the vehicle that contains the device.
6. A method performed by a base station (BS) in a wireless communication system, the method comprising: receiving a message associated with a two-stage random access procedure, the message including a physical random access channel (PRACH) preamble for at least one valid PRACH opportunity among a plurality of valid PRACH opportunities in a PRACH slot; transmitting information related to a random access response (RAR) in response to the message; the PRACH preamble is included in a plurality of PRACH preambles associated with the plurality of valid PRACH opportunities; The message further includes a physical uplink shared channel (PUSCH) for at least one valid PUSCH opportunity among a plurality of valid PUSCH opportunities; The PUSCH is received based on PUSCH configuration information associated with the two-stage optional access procedure; The PUSCH configuration information includes DM-RS configuration information regarding a demodulation reference signal (DM-RS) for the PUSCH, The method, wherein up to four DM-RS ports are configured based on the DM-RS configuration information including DM-RS port information.
7. 1. An apparatus for operating in a wireless communication system, the apparatus comprising: Memory, at least one processor coupled to the memory; The at least one processor: receiving a message associated with a two-stage random access procedure, the message including a physical random access channel (PRACH) preamble for at least one valid PRACH opportunity among a plurality of valid PRACH opportunities in a PRACH slot; configured to transmit information related to a random access response (RAR) in response to said message; the PRACH preamble is included in a plurality of PRACH preambles associated with the plurality of valid PRACH opportunities; The message further includes a physical uplink shared channel (PUSCH) for at least one valid PUSCH opportunity among a plurality of valid PUSCH opportunities; The PUSCH is received based on PUSCH configuration information associated with the two-stage optional access procedure; The PUSCH configuration information includes DM-RS configuration information regarding a demodulation reference signal (DM-RS) for the PUSCH, The apparatus, wherein up to four DM-RS ports are configured based on the DM-RS configuration information including DM-RS port information.
Citation Information
Patent Citations
Random Access Procedures in Next Generation Networks
JP2019524031A
