Method and device for random access procedure
By introducing a frequency RO index offset and configuring OFDM symbol indices within the additional RACH configuration, the method addresses RA-RNTI conflicts, ensuring reliable and efficient random access procedures in mobile communication systems.
Patent Information
- Application Number
- PCT/KR2024/005594
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-11
- Filing Date
- 2024-04-25
- Publication Date
- 2024-11-14
AI Technical Summary
The existing method for calculating RA-RNTI in mobile communication systems can result in conflicts and improper reception of RAR due to overlapping RA-RNTI values, especially when different RACH configurations are used, leading to increased latency in random access procedures.
The proposed method introduces a frequency RO index offset and OFDM symbol index configuration within the additional RACH configuration to prevent RA-RNTI conflicts by setting unique values for RA-RNTI calculation, ensuring reliable RACH procedures across various feature combinations.
This solution effectively prevents RA-RNTI conflicts and ensures reliable random access procedures by setting unique RA-RNTI values, thereby reducing latency and improving the overall efficiency of the random access process.
Smart Images

Figure KR2024005594_14112024_PF_FP_ABST
Abstract
Description
Method and device for random access procedure
[0001] The present specification relates to a method and apparatus for a random access procedure.
[0002] Mobile communication systems were developed to provide voice services while ensuring user activity. However, they have expanded beyond voice to include data services. Currently, explosive growth in traffic is leading to resource shortages and users are demanding faster services, necessitating a more advanced mobile communication system.
[0003] Next-generation mobile communication systems must support explosive data traffic growth, dramatically increasing data rates per user, a vastly increased number of connected devices, ultra-low end-to-end latency, and high energy efficiency. To achieve these goals, various technologies are being studied, including dual connectivity, massive multiple input multiple output (MIMO), in-band full duplex, non-orthogonal multiple access (NOMA), super wideband support, and device networking.
[0004] Repeated PRACH transmissions were introduced to enhance Rel-18 coverage. In this case, RACH resources for single PRACH transmissions and RACH resources for multiple PRACH transmissions can be independently configured. If both RACH resources are configured for the same time instance, RA-RNTI value collisions may occur. According to the existing method, the RA-RNTI can be calculated based on i) the frequency-domain index of the PRACH occasion and ii) the first OFDM symbol index of the PRACH occasion.
[0005] The purpose of this specification is to propose a method to solve the problem of RA-RNTI collision.
[0006] The technical problems to be achieved in this specification are not limited to the technical problems mentioned above, and other technical problems not mentioned can be clearly understood by a person having ordinary skill in the technical field to which the present invention belongs from the description below.
[0007] A method performed by a terminal according to one embodiment of the present disclosure includes the steps of receiving a random access channel (RACH) configuration and transmitting a random access preamble based on a random access (RA)-radio network temporary identifier (RNTI).
[0008] The above RA-RNTI is determined based on i) a first index related to the time domain of a Physical Random Access Channel (PRACH) occasion and ii) a second index related to the frequency domain of the PRACH occasion.
[0009] The above RACH setting is based on an additional RACH setting. The first index or the second index is determined based on the additional RACH setting.
[0010] The first index may be associated with an OFDM (Orthogonal Frequency Division Multiplexing) symbol index. The second index may be associated with an index of the PRACH occasion in the frequency domain.
[0011] The above additional RACH configuration may include information about the offset.
[0012] The second index may be determined based on i) the index of the PRACH occasion and ii) the offset.
[0013] The index of the above PRACH occasion can be determined based on the offset.
[0014] Information about the above OFDM symbol index can be set based on the additional RACH configuration or System Information Block (SIB).
[0015] The above OFDM symbol index may be predefined for the additional RACH configuration.
[0016] The above OFDM symbol index may be based on a symbol defined among symbols based on the PRACH occasion.
[0017] The symbol defined above may be the Nth symbol or the last symbol among the symbols based on the PRACH occasion.
[0018] The above PRACH occasion may be the last PRACH occasion among PRACH occasions based on the repetition number.
[0019] The method may further include a step of receiving downlink control information (DCI) related to a random access response (RAR). A cyclic redundancy check (CRC) related to the DCI may be scrambled by the RA-RNTI.
[0020] A terminal according to another embodiment of the present disclosure includes one or more transceivers, one or more processors, and one or more memories connected to the one or more processors and storing instructions.
[0021] The instructions are characterized in that, based on being executed by the one or more processors, the one or more processors are set to perform all steps of any one of the methods.
[0022] A device according to another embodiment of the present disclosure comprises one or more memories and one or more processors functionally connected to the one or more memories.
[0023] Said one or more memories are characterized in that they store instructions that cause said one or more processors to perform all steps of any one of said methods based on what is executed by said one or more processors.
[0024] In another embodiment of the present disclosure, one or more non-transitory computer-readable media store instructions, the instructions being executable by one or more processors, characterized in that they cause the one or more processors to perform all steps of any one of the methods.
[0025] A method performed by a base station according to another embodiment of the present disclosure includes the steps of transmitting a Random Access CHannel (RACH) configuration and receiving a Random Access preamble based on a Random Access (RA)-Radio Network Temporary Identifier (RNTI).
[0026] The above RA-RNTI is determined based on i) a first index related to the time domain of a Physical Random Access Channel (PRACH) occasion and ii) a second index related to the frequency domain of the PRACH occasion.
[0027] The above RACH setting is based on an additional RACH setting. The first index or the second index is determined based on the additional RACH setting.
[0028] A base station according to another embodiment of the present disclosure includes one or more transceivers, one or more processors, and one or more memories coupled to the one or more processors and storing instructions.
[0029] The instructions are characterized in that they are executed by the one or more processors, and the one or more processors are set to perform all steps of the method.
[0030] According to an embodiment of the present specification, it is possible to prevent RA-RNTIs from being calculated as the same value in RACH procedures based on different feature combinations (feature combinations including / not including MSG1 repetition feature).
[0031] Additionally, since the Cyclic Redundancy Check (CRC) associated with RARs based on different RACH procedures is scrambled based on the same RA-RNTI, cases where RARs associated with a specific RACH procedure are not properly received can be prevented. Consequently, the reliability of RACH procedures performed based on various feature combinations can be secured.
[0032] The effects that can be obtained from this specification are not limited to the effects mentioned above, and other effects that are not mentioned can be clearly understood by a person having ordinary skill in the technical field to which this specification belongs from the description below.
[0033] Figure 1 illustrates physical channels and typical signal transmission used in a 3GPP system.
[0034] Figure 2 shows RACH occasions by preamble format.
[0035] Figure 3 illustrates a random access procedure.
[0036] Figure 4 is a diagram illustrating a case where RA-RNTI overlaps.
[0037] FIG. 5 is a diagram illustrating f_id for calculating RA-RNTI according to one embodiment of the present specification.
[0038] FIG. 6 is a flowchart illustrating a method performed by a terminal according to one embodiment of the present specification.
[0039] FIG. 7 is a flowchart illustrating a method performed by a base station according to another embodiment of the present specification.
[0040] FIG. 8 is a drawing showing the configuration of the first device and the second device according to an embodiment of the present specification.
[0041] Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings. The detailed description set forth below, together with the accompanying drawings, is intended to illustrate exemplary embodiments of the present invention and is not intended to represent the only embodiments in which the present invention may be practiced. The following detailed description includes specific details to provide a thorough understanding of the present invention. However, one of ordinary skill in the art will appreciate that the present invention may be practiced without these specific details.
[0042] In some cases, to avoid obscuring the concept of the present invention, well-known structures and devices may be omitted or illustrated in block diagram form focusing on the core functions of each structure and device.
[0043] Hereinafter, downlink (DL) refers to communication from a base station to a terminal, and uplink (UL) refers to communication from a terminal to a base station. In downlink, a transmitter may be part of a base station, and a receiver may be part of a terminal. In uplink, a transmitter may be part of a terminal, and a receiver may be part of a base station. A base station may be expressed as a first communication device, and a terminal may be expressed as a second communication device. A base station (BS) may be replaced by terms such as a fixed station, Node B, eNB (evolved-NodeB), gNB (Next Generation NodeB), BTS (base transceiver system), access point (AP: Access Point), network (5G network), AI system, RSU (road side unit), vehicle, robot, drone (Unmanned Aerial Vehicle, UAV), AR (Augmented Reality) device, VR (Virtual Reality) device, etc. In addition, the terminal may be fixed or mobile, and may be replaced with terms such as UE (User Equipment), MS (Mobile Station), UT (user terminal), MSS (Mobile Subscriber Station), SS (Subscriber Station), AMS (Advanced Mobile Station), WT (Wireless terminal), MTC (Machine-Type Communication) device, M2M (Machine-to-Machine) device, D2D (Device-to-Device) device, vehicle, robot, AI module, drone (Unmanned Aerial Vehicle, UAV), AR (Augmented Reality) device, VR (Virtual Reality) device, etc.
[0044] Physical channels and general signal transmission
[0045] Figure 1 illustrates the physical channels and typical signal transmission used in the 3GPP system. In a wireless communication system, a terminal receives information from a base station via the downlink (DL), and the terminal transmits information to the base station via the uplink (UL). The information transmitted and received between the base station and the terminal includes data and various control information, and various physical channels exist depending on the type and purpose of the information they transmit and receive.
[0046] When a terminal is powered on or enters a new cell, it performs an initial cell search operation, such as synchronizing with the base station (S101). To this end, the terminal receives a Primary Synchronization Signal (PSS) and a Secondary Synchronization Signal (SSS) from the base station to synchronize with the base station and obtain information such as a cell ID. Afterwards, the terminal can receive a Physical Broadcast Channel (PBCH) from the base station to obtain broadcast information within the cell. Meanwhile, the terminal can receive a Downlink Reference Signal (DL RS) during the initial cell search phase to check the downlink channel status.
[0047] A terminal that has completed initial cell search can obtain more specific system information by receiving a physical downlink control channel (PDCCH) and a physical downlink shared channel (PDSCH) according to information carried in the PDCCH (S102).
[0048] Meanwhile, when accessing a base station for the first time or when there are no radio resources for signal transmission, the terminal may perform a random access procedure (RACH) for the base station (S103 to S106). To this end, the terminal may transmit a specific sequence as a preamble via a physical random access channel (PRACH) (S103 and S105) and receive a response message (RAR (Random Access Response) message) to the preamble via a PDCCH and a corresponding PDSCH. In the case of a contention-based RACH, a contention resolution procedure may additionally be performed (S106).
[0049] The terminal that has performed the procedure described above can then perform PDCCH / PDSCH reception (S107) and physical uplink shared channel (PUSCH) / physical uplink control channel (PUCCH) transmission (S108) as general uplink / downlink signal transmission procedures. In particular, the terminal can receive downlink control information (DCI) through the PDCCH. Here, the DCI includes control information such as resource allocation information for the terminal, and different formats can be applied depending on the purpose of use.
[0050] Meanwhile, the control information that the terminal transmits to the base station via the uplink or that the terminal receives from the base station may include downlink / uplink ACK / NACK signals, CQI (Channel Quality Indicator), PMI (Precoding Matrix Index), RI (Rank Indicator), etc. The terminal may transmit the above-described control information such as CQI / PMI / RI via PUSCH and / or PUCCH.
[0051] Next, let's look at the RACH slot.
[0052] A RACH slot contains one or more RACH Occasion(s).
[0053] The slot duration is 1ms for {1.25kHz, 5kHz} subcarrier spacing and has scalable duration (i.e. 1ms, 0.5ms, 0.25ms, 0.125ms) for {15kHz, 30kHz, 60kHz, 120kHz} subcarrier spacing.
[0054] For short preamble formats, the starting OFDM symbol index in the RACH slot has values {0,2,x}.
[0055] Figure 2 shows RACH occasions by preamble format.
[0056] Referring to Fig. 2, a RACH slot may include one or more RACH occasions (ROs) for each preamble format (e.g., A1, A2, ..C2). Fig. 2 (a) shows a case where the start OFDM symbol is '0', and Fig. 2 (b) shows a case where the start OFDM symbol is '2'.
[0057] Figure 3 illustrates a random access procedure.
[0058] Figure 3 (a) shows a contention-based RACH procedure, and Figure 3 (b) shows a contention-free RACH procedure.
[0059] Below, we will look at MSG1 transmission.
[0060] Subcarrier spacing for MSG1 is set in the RACH configuration and provided in the handover command for contention-free RA procedures for handover.
[0061] Preamble indices for contention based random access (CBRA) and contention free random access (CFRA) are mapped consecutively to one SSB in one RACH transmission occasion.
[0062] CBRA: The association between a SS block (SSB) and a subset of RACH resources and / or preamble indices within an SS burst set is established by a parameter set in the RMSI.
[0063] CFRA: The UE may be configured to transmit multiple MSG1s via dedicated multi-RACH transmission opportunities in the time domain before the end of the monitored RAR window.
[0064] And, the association between CFRA preamble and SSB is reestablished via UE-specific RRC.
[0065] The random access procedure can be a Type-1 random access procedure (4-step RA) or a Type-2 random access procedure (2-step RA).
[0066] The above Type-1 random access procedure may include transmitting a random access preamble (Msg1) on a physical random access channel (PRACH), receiving a random access response (RAR) (Msg2), transmitting a PUSCH scheduled by an UL grant of the RAR (Msg3), and transmitting a PDSCH for contention resolution (Msg4). If the random access procedure is contention-free random access (CFRA), the Msg3 transmission and Msg4 reception operations are omitted.
[0067] The above Type-2 random access procedure may include transmission of a random access preamble and PUSCH (MsgA) and reception of a RAR (MsgB).
[0068] Table 1 below illustrates the settings / operations related to the random access preamble.
[0069]
[0070]
[0071]
[0072]
[0073]
[0074]
[0075] The settings / definitions / operations according to Table 1 above may be referred to to clarify the definitions / operations of the embodiments described below. For example, in the embodiments described below, ROs may mean valid PRACH occasions mentioned in Table 1. For example, in the embodiments described below, multiple ROs having the same beam index may mean 1 / N (where N<1) consecutive valid PRACH occasions to which one SS / PBCH index is mapped.
[0076] Tables 2 to 4 below illustrate PRACH configuration tables that can be applied to the embodiments described below.
[0077]
[0078]
[0079]
[0080]
[0081]
[0082]
[0083]
[0084]
[0085]
[0086]
[0087]
[0088]
[0089]
[0090]
[0091]
[0092]
[0093]
[0094]
[0095]
[0096]
[0097]
[0098]
[0099]
[0100]
[0101]
[0102]
[0103]
[0104]
[0105]
[0106]
[0107]
[0108] For example, in the embodiments described below, ROs (PRACH occasions) may be ROs based on one of Tables 2 to 4.
[0109] The contents discussed above can be applied in combination with the methods proposed in this specification, which will be described later, or can be supplemented to clarify the technical features of the methods proposed in this specification.
[0110] In addition, the methods related to the PRACH transmission occasion configuration described later are related to uplink transmission and can be equally applied to the uplink signal transmission method in the NR system (licensed band) or U-Band system (unlicensed band) described above, and of course, the technical idea proposed in this specification can be modified or replaced to fit the terms, expressions, structures, etc. defined in each system so that it can be implemented in the relevant system as well.
[0111] For example, uplink transmission through methods related to the PRACH transmission occasion configuration described later can be performed in an L-cell (a cell operating in a licensed band (L-band)) and / or a U-cell (a cell operating in an unlicensed band (U-band)) defined in an NR system or a U-Band system.
[0112] NR supports multiple numerologies (or subcarrier spacings (SCS)) to support various 5G services. For example, an SCS of 15 kHz supports wide areas in traditional cellular bands; an SCS of 30 kHz / 60 kHz supports dense urban areas, lower latency, and wider carrier bandwidth; and an SCS of 60 kHz or higher supports bandwidths greater than 24.25 GHz to overcome phase noise.
[0113] The NR frequency band is defined by two types of frequency ranges (FR1 and FR2). FR1 and FR2 can be configured as shown in Table 5 below. FR2 can also mean millimeter wave (mmW).
[0114]
[0115] Meanwhile, repeated transmission of the PRACH preamble is being considered to enhance UL coverage in the existing NR system. Meanwhile, the RA-RNTI and MSGB-RNTI formulas currently applied to the FR1 / 2 region are defined as shown in Table 6 below.
[0116]
[0117] At this time, if the base station allocates additional RACH configuration to the terminal for repeated PRACH transmission, the corresponding RACH resource and the RACH resource allocated through legacy RACH configuration may be frequency multiplexed (FDMed) and allocated in the same time instance. In this case, the expected RA-RNTI values between the terminal and the base station may become identical. For a specific example, ROs may be configured as shown in Fig. 4.
[0118] Figure 4 is a diagram illustrating a case where RA-RNTI overlaps.
[0119] Referring to FIG. 4, it can be assumed that a legacy RACH configuration (i.e., single PRACH TX) and an additional RACH configuration (i.e., multiple PRACH TX) are allocated as separate ROs (i.e., separated RACH configurations). In other words, ROs (legacy RO) (A to H) based on RACH configurations for single PRACH transmission and ROs (Additional RO) (I to P) based on RACH configurations for repeated PRACH transmissions can be separately configured. In this case, multiple ROs corresponding to different RACH configurations can be FDMed and allocated at the same time instance. At this time, UE1 and UE2 can perform PRACH transmission and RA-RNTI calculation as follows.
[0120] UE1 can perform PRACH repetition with repetition factor 4 by selecting RO I, RO J, RO K, and RO L and calculate RA-RNTI based on RO L. UE2 can perform single PRACH transmission using RO D and calculate RA-RNTI based on RO D. UE1 and UE2 start monitoring RAR window at the same time, and RA-RNTI values expected by UE1 and UE2 are the same (assuming that both configurations are msg1-FDM = 2). Here, msg1-FDM indicates the number of PRACH occasions that are FDMed in one time instance.
[0121] As a result, both UE1 and UE2 operate based on the scheduled PDSCH, which is based on the DCI format 1_0 scrambled with the same RA-RNTI, expecting that the RAR transmitted is the appropriate RAR for each UE. Consequently, either UE1 or UE2 fails to receive the appropriate RAR in time. This ultimately leads to an increase in latency in the RACH procedure.
[0122] To address these issues, this specification proposes a method to address the RA-RNTI overlapping issue when a PRACH (Msg. A) preamble repetition operation is defined.
[0123] RA-RNTI collision handling for PRACH repeated transmission.
[0124] [Method 1]
[0125] A method of introducing a frequency RO index offset within the parameters for additional RACH configuration may be considered. The additional RACH configuration may be configured via higher layer signaling (e.g., SIB1). This will be described in detail below.
[0126] An offset parameter for changing the frequency index of RO can be additionally introduced in the parameter for additional RACH configuration (e.g., AdditionalRACH-Config-r17).
[0127] For example, the base station can set / instruct the UE to set / instruct the FDMed RO index offset-related parameter (e.g., msg1-FDM-index-offset) through a parameter for additional RACH configuration. At this time, considering all RACH configurations provided within the cell, the base station can instruct the offset value so that the total number of ROs that can be FDMed at the same time instance does not exceed 8.
[0128] If the above FDMed RO index offset related parameter (e.g., msg1-FDM-index-offset) is set / indicated in the parameter for additional RACH configuration (e.g., AdditionalRACH-Config-r17), the terminal and base station can be configured to additionally apply the corresponding offset value when calculating RA-RNTI. The specific terminal operation is described as follows.
[0129] According to the existing operation for RA-RNTI calculation, the terminal uses the frequency index corresponding to a random RO selected from among the FDMed ROs allocated by the base station in the MAC layer as the f_id value.
[0130] For example, according to the present embodiment, if a parameter related to FDMed RO index offset (e.g., msg1-FDM-index-offset) is set / instructed to a terminal from a base station, the terminal may be configured to use the f_id value by adding the instructed msg1-FDM-index-offset to a frequency index value corresponding to an arbitrary RO selected in the MAC layer (e.g., the last RO among ROs).
[0131] f_id according to this embodiment can be determined / defined as follows.
[0132] f_id = frequency index of RO + msg1-FDM-index-offset
[0133] For example, according to the present embodiment, the frequency index (i.e., f_id) may be defined / determined based on the order of selected ROs among the FDMed ROs (starting from that value) based on the FDMed RO index offset-related parameter (e.g., msg1-FDM-index-offset) set / instructed by the base station. As a specific example, when the RA-RNTI is calculated based on the first RO among the FDM ROs, f_id may be determined / defined as msg1-FDM-index-offset+0. When the RA-RNTI is calculated based on the second RO among the FDM ROs, f_id may be determined / defined as msg1-FDM-index-offset+1. Characteristically, the actual frequency positions of the ROs allocated through the additional RACH configuration may be determined through the msg1-FDM value and msg1-FrequencyStart in the same manner as in the existing terminal operation.
[0134] A specific example of the above proposed method can be illustrated as in Fig. 5. Fig. 5 is a diagram illustrating f_id for calculating RA-RNTI according to one embodiment of the present specification.
[0135] Figure 5 (a) illustrates f_id determined / defined without FDMed RO index offset. Figure 5 (b) illustrates f_id determined / defined based on FDMed RO index offset according to an embodiment of the present specification. Below, specific examples of settings / operations related to the offset (msg1-FDM-index-offset value) are described.
[0136] For example, it may be assumed that the base station allocates only two RACH configurations (i.e., a legacy RACH configuration and one additional RACH configuration) to the cell, and the msg1-FDM value of the legacy RACH configuration is 4, and the msg1-FDM value of the additional RACH configuration is 4. In this case, the msg1-FDM-index-offset value of the additional RACH configuration may be set to 4.
[0137] For example, the base station can configure / instruct the terminal to use the msg1-FDM value of the legacy RACH configuration as the msg1-FDM-index-offset of the additional RACH configuration.
[0138] For example, the base station can use a separate parameter to configure / instruct the terminal whether to enable / disable the FDM offset. If the base station indicates that the FDM offset is enabled, the terminal can operate as follows. The terminal can use the msg1-FDM-index-offset value if it is indicated. If the msg1-FDM-index-offset is not indicated, the terminal can be configured to use the msg1-FDM value of the legacy RACH configuration as the msg1-FDM-index-offset value. As a specific example, it can be assumed that the msg1-FDM-index-offset value is 4 and the frequency index value of the RO randomly selected by the terminal through the MAC layer is 2. If the terminal (base station) transmits (receives) a PRACH based on the RO, the f_id value used for the RA-RNTI can be 6.
[0139] [Method 2]
[0140] A method of setting / indicating an OFDM symbol index value for calculating s_id of RA-RNTI within parameters for additional RACH configuration may be considered. The additional RACH configuration may be set via higher layer signaling (e.g., SIB1). This will be described in detail below.
[0141] According to the existing terminal / base station operation, the first OFDM symbol index of the RO where the preamble is transmitted / received is defined to be used as the s_id value when calculating the RA-RNTI. However, since the PRACH formats defined in NR use at least two OFDM symbols per RO, some RA-RNTI values may remain unused within a specific cell depending on the RACH configuration. Therefore, the base station can configure / instruct the terminal to use the remaining RA-RNTI values for the RO allocated by the additional RACH configuration.
[0142] A method may be considered in which the base station indicates the s_id (i.e., OFDM symbol index) value to be used for RA-RNTI calculation within higher layer signaling (e.g., SIB1) for additional RACH configuration or within parameters for additional RACH configuration. This is described in detail below.
[0143] The base station can select the value to be used as s_id based on the total number of OFDM symbols in one RO for the PRACH format set through a specific RACH configuration. That is, the base station can indicate to the terminal the Nth OFDM symbol in the RO to be used for s_id.
[0144] For example, the base station can indicate the OFDM symbol for s_id to the terminal in the form of 1st OFDM symbol of RO, 2nd OFDM symbol of RO, 3rd OFDM symbol of RO, last OFDM symbol of RO, etc. When such a parameter is indicated, the terminal and the base station can be configured to use the s_id value as the OFDM symbol index value corresponding to the indicated OFDM symbol position of the corresponding RO when calculating RA-RNTI. That is, when the 2nd OFDM symbol of the RO is indicated based on the parameter, the s_id for calculating RA-RNTI can be determined / defined as the index of the 2nd OFDM symbol of the RO. When the base station does not separately indicate the parameter to the terminal, the first OFDM symbol index of the corresponding RO can be set / defined to be used as s_id when calculating RA-RNTI, similar to the existing terminal / base station operation.
[0145] For example, when PRACH is transmitted / received based on an RO of an additional RACH configuration, it may be defined in advance to use a specific Nth OFDM symbol of the corresponding RO for the s_id value when calculating RA-RNTI. As a specific example, the specific Nth OFDM symbol may be the last OFDM symbol of the corresponding RO. As another example, it may be defined in advance to know which OFDM symbol position in a specific RO the value of N is, such as 2 or 3. When the s_id value is defined in advance for RA-RNTI calculation for the additional RACH configuration as described above, the terminal and the base station may be set / defined to operate as follows. The terminal / base station may use the OFDM symbol index corresponding to the predefined OFDM symbol position of the corresponding RO as the s_id value when calculating RA-RNTI.
[0146] [Method 3]
[0147] A method of providing additional information to distinguish RACH configurations through settings for other signals / channels may be considered.
[0148] The base station can separately set / instruct additional information to a specific signal / channel to distinguish whether it is a legacy RACH configuration or an additional RACH configuration.
[0149] For example, based on the reserved 1 bit field of the MAC payload in the RAR that schedules Msg. 3 PUSCH, the configuration related to the RAR can be indicated / determined as a legacy RACH configuration or an additional RACH configuration. In other words, if the value of the reserved 1 bit field of the MAC payload in the RAR is set to 0, the RAR can be indicated / determined as an RAR for the legacy RACH configuration. If the value of the reserved 1 bit field of the MAC payload in the RAR is set to 1, the RAR can be indicated / determined as an RAR for the additional RACH configuration.
[0150] Since the reserved field only has 1 bit, when multiple additional RACH configurations are allocated, it may be difficult to distinguish them from the legacy RACH configuration. In other words, when the multiple additional RACH configurations are allocated to overlap with the legacy RACH configuration at a specific point in time, it may be difficult to distinguish between the different configurations. In such cases, the following embodiments may be considered.
[0151] For example, the following fields may be utilized to distinguish whether a configuration related to RAR is a legacy RACH configuration or an additional RACH configuration. Specifically, when DCI format 1_0 is scrambled with RA-RNTI, some of the reserved fields of the DCI format 1_0 may be used as RACH configuration indication fields. That is, the N bit field(s) of the reserved field may be set / instructed to distinguish between the legacy RACH configuration and k additional RACH configurations. In other words, one of the legacy RACH configuration and k additional RACH configurations may be indicated based on the value of the N bit field(s).
[0152] At this time, the N value can be determined as N=ceil(log2(1+k)). N MSB bits (or LSB bits) of the reserved field can be used as the RACH configuration indication field.
[0153] Assuming k=3, the value of N can be determined as 2 (=ceil(log2(1+3)). The RACH configuration can be indicated as follows by the value of the 2-bit field.
[0154] {00, 01, 10, 11} = {legacy RACH configuration, additional RACH configuration #1, additional RACH configuration #2, additional RACH configuration #3} can be expressed.
[0155] Assuming k=2, the value of N can be determined as 2 (=ceil(log2(1+2)). The RACH configuration can be indicated as follows by the value of the 2-bit field.
[0156] {00, 01, 10, 11} = {legacy RACH configuration, additional RACH configuration #1, additional RACH configuration #2, reserved}
[0157] For example, the k additional RACH configurations may be all additional RACH configurations set by the base station for the corresponding cell.
[0158] For example, the k additional RACH configurations may be the legacy RACH configuration and additional RACH configurations that can be deployed in FDM at any time instance.
[0159] Based on the above additional information (i.e., information indicating RACH configuration), the terminal can operate as follows.
[0160] The terminal checks the RA-RNTI value scrambled in DCI format 1_0 and additionally checks the additional information. If the RACH configuration indicated based on the additional information corresponds to the RO selected by the terminal, the terminal can be configured to interpret the corresponding RAR. That is, the terminal can receive / interpret the RAR based on the PDSCH scheduled by the corresponding DCI format.
[0161] However, since terminals prior to Rel-17 cannot interpret the additional information, they will try to interpret the RAR if only the RA-RNTI scrambled in DCI format 1_0 matches. Considering this, the following embodiment can be additionally applied. The base station can transmit the RAR for the legacy RACH configuration (i.e., the DCI format 1_0 with RA-RNTI that schedules the RAR) before the RAR for the additional RACH configuration.
[0162] [Method 4]
[0163] A method to configure different RA-RNTIs to be used depending on the RACH configuration may be considered.
[0164] Since the problem mentioned above is caused by the same RA-RNTI, a method of setting the RA-RNTI for additional RACH configuration independently from the RA-RNTI for legacy RACH configuration can be considered.
[0165] For example, among additional RACH configurations, an RA-RNTI for multiple PRACHs can be independently configured / defined. Specifically, the RA-RNTI can be defined to be calculated based on the following mathematical expression 1.
[0166]
[0167] For example, the additional RACH configuration index may be an index that considers all additional RACH configurations allocated within the cell.
[0168] For example, the additional RACH configuration index may be an index that considers only a single PRACH and additional RACH configurations to which RO is allocated in FDM format in a specific time instance. Specifically, the index values of the additional RACH configurations corresponding to the above-mentioned considerations may be set / indicated as follows. The base station may set / indicate the index values of the additional RACH configurations corresponding to the above-mentioned considerations using positive integers that sequentially increase from 1 so that they do not overlap. Assuming that the number of additional RACH configurations is 3, the index according to the present embodiment may be set / indicated as follows. Index 1 may be set / indicated for additional RACH configuration #1. Index 2 may be set / indicated for additional RACH configuration #2. Index 3 may be set / indicated for additional RACH configuration #3.
[0169] For example, it can be defined / set by mapping the index for the RACH configuration by increasing it from 1 in ascending (or descending) order of the repetition number value set / indicated in the RACH configuration. Assuming that the number of additional RACH configurations is 3, the index for the additional RACH configuration can be defined / set as follows.
[0170] It can be assumed that the repetition number is set as follows. The repetition number based on additional RACH configuration #1 may be 2, the repetition number based on additional RACH configuration #2 may be 4, and the repetition number based on additional RACH configuration #3 may be 8. In this case, index 1 may be set / indicated for additional RACH configuration #1. Index 2 may be set / indicated for additional RACH configuration #2. Index 3 may be set / indicated for additional RACH configuration #3.
[0171] [Method 5]
[0172] A method to configure different DL BWPs to be used depending on the RACH configuration may be considered.
[0173] According to the existing operation, the legacy RACH configuration and / or additional RACH configurations configured by the base station are allocated within the initial UL BWP. Thereafter, when the UE transmits a preamble to any RO, it is configured to monitor the RAR using the same initial DL BWP, regardless of the RACH configuration selected.
[0174] Therefore, in order to resolve cases where RA-RNTI overlaps for different RACH configurations, a method may be considered in which the DL BWP for which the terminal monitors RAR is set to be distinguished for different RACH configurations.
[0175] For example, an additional DL BWP capable of monitoring the RAR window may be configured / indicated within the additional RACH configuration. That is, if the base station configures an additional DL BWP, the terminal may be configured to monitor RAR in the DL BWP based on the configuration. If the base station does not separately configure an additional DL BWP, the terminal may be configured to monitor RAR using the initial DL BWP as in the existing operation.
[0176] Specifically, if the base station configures an additional DL BWP within the additional RACH configuration, the transmission and reception of DL signals / channels for the RACH procedure performed by the terminal / base station can be configured to be performed through the additional DL BWP. If there is no BWP switching instruction from the base station after the terminal enters the RRC connected state, the terminal can be configured to continue using the additional DL BWP as the active DL BWP.
[0177] Additionally, the base station can configure / instruct the terminal to an additional (initial) UL BWP that is independent of the initial UL BWP. At this time, the base station can configure the legacy RACH configuration to be allocated within the initial UL BWP. The base station can separately configure / instruct the terminal to which UL BWP among the initial UL BWP and / or the additional (initial) UL BWP the additional RACH configuration is allocated.
[0178] In the absence of the above separate configuration / instruction information, the terminal may interpret that the additional RACH configuration is allocated to the initial UL BWP and operate as before. If the base station configures the additional RACH configuration to be allocated to the additional (initial) UL BWP, the terminal may interpret that the corresponding RACH resources are allocated to the additional (initial) UL BWP and operate. Thereafter, the initial DL BWP may also be separately configured / instructed as in the above-mentioned method.
[0179] Meanwhile, when ROs corresponding to multiple RACH configurations are configured in an FDMed format, a preamble index set can be allocated / configured so that RAPID (Random Access Preamble IDentity) can be distinguished. Specifically, the base station can distinguish and configure the preamble index set available for each RACH configuration so that even if the RA-RNTI is the same when the terminal receives the RAR, the RAPID can be distinguished.
[0180] For example, the RO of the legacy RACH configuration may be configured to use 32 RAPIDs 0 to 31. The RO of the additional RACH configuration may be configured to use 32 RAPIDs 32 to 63.
[0181] Although the above proposed method was proposed mainly considering the time of calculating RA-RNTI, it can be applied to calculating MSGB-RNTI in the same / similar manner. In addition, the above proposed method can be set / applied to other UL signals / channels such as PUSCH / PUCCH. In addition, it is clear that examples of the proposed method described above can also be included as one of the implementation methods of the present specification, and thus can be considered as a type of proposed method. In addition, the proposed methods described above can be implemented independently, but can also be implemented in the form of a combination (or merge) of some of the proposed methods. Information on whether the proposed methods are applied (or information on the rules of the proposed methods) can be defined by a rule so that the base station notifies the terminal of the application of the proposed methods through a predefined signal (e.g., a physical layer signal or a higher layer signal). The higher layer can include one or more of functional layers such as MAC, RLC, PDCP, RRC, and SDAP.
[0182] The methods, embodiments or descriptions for implementing the method proposed in this specification may be applied separately, or one or more methods (or embodiments or descriptions) may be applied in combination.
[0183] In terms of implementation, the operations of the base station / terminal according to the embodiments described above (e.g., operations based on at least one of methods 1 to 5) can be processed by the device of FIG. 8 described below (e.g., processor (110, 210) of FIG. 8).
[0184] In addition, the operations of the base station / terminal according to the above-described embodiment (e.g., operations based on at least one of methods 1 to 5) may be stored in a memory (e.g., 140, 240 of FIG. 8) in the form of commands / programs (e.g., instructions, executable codes) for driving at least one processor (e.g., 110, 210 of FIG. 8).
[0185] The embodiments described below are specifically described with reference to FIGS. 6 and 7 in terms of the operation of the terminal and base station. The methods described below are distinguished for convenience of explanation, and it is understood that some components of one method may be substituted for or combined with some components of another method.
[0186] FIG. 6 is a flowchart illustrating a method performed by a terminal according to one embodiment of the present specification.
[0187] Referring to FIG. 6, a method performed by a terminal according to one embodiment of the present specification includes a RACH configuration receiving step (S610) and a random access preamble transmitting step (S620) based on an RA-RNTI.
[0188] In S610, the terminal receives a random access channel (RACH) setting from the base station.
[0189] For example, the RACH configuration may be received based on a System Information Block (SIB) (e.g., SIB1). A BWP-uplinkCommon parameter may be configured based on the SIB. The RACH configuration may be one of the RACH configurations based on the BWP-uplinkCommon parameter. As a specific example, one or more AdditionalRACH-Config parameters may be configured based on the BWP-uplinkCommon parameter. The RACH configuration may be based on one of the one or more AdditionalRACH-Config parameters. The additional RACH configuration described below may refer to an AdditionalRACH-Config parameter.
[0190] In S620, the terminal transmits a random access preamble to the base station based on the RA (Random Access)-RNTI (Radio Network Temporary Identifier). Transmission of the random access preamble may mean transmission of a physical random access channel (PRACH) / MSG1.
[0191] For example, the random access preamble may be transmitted based on a repetition number. The random access preamble may be transmitted based on Table 1. Transmitting the random access preamble based on a repetition number may mean that MSG1 (PRACH) transmission based on one PRACH occasion is performed multiple times. The repeated transmission of the PRACH may mean PRACH transmission based on multiple PRACH occasions. In this case, the multiple PRACH occasions may be associated with the same Synchronization Signal / Physical Broadcast CHannel Block index (SS / PBCH Block index).
[0192] In one embodiment, the RA-RNTI may be determined based on i) a first index related to a time domain of a Physical Random Access Channel (PRACH) occasion and ii) a second index related to a frequency domain of the PRACH occasion. In this case, the PRACH occasion may be based on one of the PRACH occasions based on a repetition number. As a specific example, the PRACH occasion may be based on the last PRACH occasion among the PRACH occasions based on the repetition number (e.g., the last RO(L) among the ROs(I to L) of FIG. 4). The present embodiment may be based on Method 1 and / or Method 2. The RACH configuration may be based on an Additional RACH configuration. As an example, the first index and / or the second index may be determined based on the Additional RACH configuration. For example, the first index and / or the second index may be determined based on predefined information (e.g., the Nth symbol).
[0193] The first index may be associated with an OFDM (Orthogonal Frequency Division Multiplexing) symbol index. The first index may be the s_id described above. The second index may be associated with an index of the PRACH occasion in the frequency domain. The second index may be the f_id described above.
[0194] In one embodiment, the additional RACH configuration may include information regarding an offset. The second index may be determined based on the offset. This embodiment may be based on Method 1, which will be described in detail below.
[0195] For example, the second index may be determined based on i) the index of the PRACH occasion and ii) the offset. Specifically, the second index may be determined as the sum of the index of the PRACH occasion and the offset.
[0196] For example, the index of the PRACH occasion may be determined based on the offset. That is, the second index may be the index of the PRACH occasion determined based on the offset.
[0197] For example, the offset may be set / defined based on the value of the msg1-FDM parameter based on the RACH configuration. The msg1-FDM parameter indicates the number of PRACH occasions that are frequency multiplexed in one time instance. As a specific example, based on the value of the msg1-FDM parameter being 4, the offset may be set / defined as 4. The offset may be determined / set / indicated based on an existing parameter (i.e., the msg1-FDM parameter) based on the RACH configuration.
[0198] In one embodiment, information about the OFDM symbol index may be set / indicated based on higher layer signaling. This embodiment may be based on Method 2. For example, information about the OFDM symbol index may be set based on the additional RACH configuration or a System Information Block (SIB) (e.g., SIB1).
[0199] In one embodiment, the OFDM symbol index may be predefined for the additional RACH configuration. This embodiment may be based on Method 2. The OFDM symbol index may be based on a defined symbol among the symbols based on the PRACH occasion. The defined symbol may be the Nth symbol or the last symbol among the symbols based on the PRACH occasion. N may be a positive integer (e.g., 1, 2, etc.).
[0200] The method may further include a DCI receiving step. In the DCI receiving step, the terminal receives downlink control information (DCI) related to a random access response (RAR) from a base station. The DCI may be based on DCI format 1_0. A cyclic redundancy check (CRC) related to the DCI may be scrambled by the RA-RNTI. In other words, the terminal may receive a DCI having a CRC scrambled by the RA-RNTI from the base station.
[0201] The operations based on the S610 to S620 and DCI receiving steps described above can be implemented by the device of FIG. 8. For example, the terminal (200) can control one or more transceivers (230) and / or one or more memories (240) to perform the operations based on the S610 to S620 and DCI receiving steps.
[0202] The embodiments described below are specifically described in terms of base station operation.
[0203] The S710 to S720 and DCI transmission steps described below correspond to the S610 to S620 and DCI reception steps described in FIG. 6. Considering the above correspondence, redundant descriptions are omitted. That is, the specific description of the base station operation described below may be replaced with the description / embodiment of FIG. 6 corresponding to the operation. For example, the description / embodiment of S610 to S620 of FIG. 6 may be additionally applied to the base station operation of S710 to S720 described below. For example, the description / embodiment of the terminal operation of the DCI reception step may be additionally applied to the base station operation of the DCI transmission step described below.
[0204] FIG. 7 is a flowchart illustrating a method performed by a base station according to another embodiment of the present specification.
[0205] Referring to FIG. 7, a method performed by a base station according to another embodiment of the present specification includes a RACH configuration transmission step (S710) and a step of receiving a random access preamble based on an RA-RNTI (S720).
[0206] In S710, the base station transmits a random access channel (RACH) setting to the terminal.
[0207] In S720, the base station receives a random access preamble based on RA (Random Access)-RNTI (Radio Network Temporary Identifier) from the terminal.
[0208] The above RA-RNTI may be determined based on i) a first index related to a time domain of a physical random access channel (PRACH, occasion) and ii) a second index related to a frequency domain of the PRACH occasion.
[0209] The above method may further include a DCI transmission step. In the DCI transmission step, the base station transmits downlink control information (DCI) related to a random access response (RAR) to the terminal. The CRC (Cyclic Redundancy Check) related to the DCI may be scrambled by the RA-RNTI. In other words, the base station may transmit the DCI having the CRC scrambled by the RA-RNTI to the terminal.
[0210] The operations based on the S710 to S730 and DCI transmission steps described above can be implemented by the device of FIG. 8. For example, the base station (100) can control one or more transceivers (130) and / or one or more memories (140) to perform operations based on the S710 to S730 and DCI transmission steps.
[0211] Hereinafter, a device to which an embodiment of the present specification can be applied (a device that implements a method / operation according to an embodiment of the present specification) is described with reference to FIG. 8.
[0212] FIG. 8 is a drawing showing the configuration of the first device and the second device according to an embodiment of the present specification.
[0213] The first device (100) may include a processor (110), an antenna unit (120), a transceiver (130), and a memory (140).
[0214] The processor (110) performs baseband-related signal processing and may include a higher layer processing unit (111) and a physical layer processing unit (115). The higher layer processing unit (111) may process operations of a MAC layer, an RRC layer, or higher layers. The physical layer processing unit (115) may process operations of a PHY layer. For example, when the first device (100) is a base station device in base station-terminal communication, the physical layer processing unit (115) may perform uplink reception signal processing, downlink transmission signal processing, etc. For example, when the first device (100) is a first terminal device in terminal-to-terminal communication, the physical layer processing unit (115) may perform downlink reception signal processing, uplink transmission signal processing, sidelink transmission signal processing, etc. In addition to performing baseband-related signal processing, the processor (110) may also control the overall operation of the first device (100).
[0215] The antenna unit (120) may include one or more physical antennas, and when it includes multiple antennas, it may support MIMO transmission and reception. The transceiver (130) may include an RF (Radio Frequency) transmitter and an RF receiver. The memory (140) may store information processed by the processor (110), and software, an operating system, applications, etc. related to the operation of the first device (100), and may also include components such as a buffer.
[0216] The processor (110) of the first device (100) may be configured to implement the operation of the base station in the base station-to-terminal communication (or the operation of the first terminal device in the terminal-to-terminal communication) in the embodiments described in the present disclosure.
[0217] The second device (200) may include a processor (210), an antenna unit (220), a transceiver (230), and a memory (240).
[0218] The processor (210) performs baseband-related signal processing and may include a higher layer processing unit (211) and a physical layer processing unit (215). The higher layer processing unit (211) may process operations of a MAC layer, an RRC layer, or higher layers. The physical layer processing unit (215) may process operations of a PHY layer. For example, when the second device (200) is a terminal device in base station-terminal communication, the physical layer processing unit (215) may perform downlink reception signal processing, uplink transmission signal processing, etc. For example, when the second device (200) is a second terminal device in terminal-to-terminal communication, the physical layer processing unit (215) may perform downlink reception signal processing, uplink transmission signal processing, sidelink reception signal processing, etc. In addition to performing baseband-related signal processing, the processor (210) may also control the overall operation of the second device (210).
[0219] The antenna unit (220) may include one or more physical antennas, and when it includes multiple antennas, it may support MIMO transmission and reception. The transceiver (230) may include an RF transmitter and an RF receiver. The memory (240) may store information processed by the processor (210), software, an operating system, applications, etc. related to the operation of the second device (200), and may also include components such as a buffer.
[0220] The processor (210) of the second device (200) may be configured to implement operations of the terminal in base station-to-terminal communication (or operations of the second terminal device in terminal-to-terminal communication) in the embodiments described in the present disclosure.
[0221] In the operation of the first device (100) and the second device (200), the same explanations given for the base station and the terminal (or the first terminal and the second terminal in the terminal-to-terminal communication) in the examples of the present disclosure may be applied, and redundant explanations are omitted.
[0222] Here, the wireless communication technology implemented in the device (100, 200) of the present disclosure may include not only LTE, NR, and 6G, but also Narrowband Internet of Things (NB-IoT) for low-power communication. For example, NB-IoT technology may be an example of LPWAN (Low Power Wide Area Network) technology, and may be implemented in standards such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the above-described names.
[0223] Additionally or alternatively, the wireless communication technology implemented in the device (100, 200) of the present disclosure may perform communication based on LTE-M technology. For example, LTE-M technology may be an example of LPWAN technology and may be called by various names such as eMTC (enhanced Machine Type Communication). For example, LTE-M technology may be implemented by at least one of various standards such as 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (non-Bandwidth Limited), 5) LTE-MTC, 6) LTE Machine Type Communication, and / or 7) LTE M, and is not limited to the above-described names.
[0224] Additionally or alternatively, the wireless communication technology implemented in the device (100, 200) of the present disclosure may include at least one of ZigBee, Bluetooth, and Low Power Wide Area Network (LPWAN) that take low-power communication into account, and is not limited to the above-described names. For example, ZigBee technology can create personal area networks (PANs) related to small / low-power digital communication based on various standards such as IEEE 802.15.4, and may be called by various names.
Claims
1. In a method performed by a terminal, A step of receiving a Random Access Channel (RACH) setting; and A step of transmitting a random access preamble based on RA(Random Access)-RNTI(Radio Network Temporary Identifier); including, The above RA-RNTI is determined based on i) a first index related to the time domain of a physical random access channel (PRACH, occasion) and ii) a second index related to the frequency domain of the PRACH occasion, The above RACH settings are based on the additional RACH settings, A method characterized in that the first index or the second index is determined based on the additional RACH setting.
2. In paragraph 1, A method characterized in that the first index is related to an OFDM (Orthogonal Frequency Division Multiplexing) symbol index, and the second index is related to an index of the PRACH occasion in the frequency domain.
3. In paragraph 2, A method characterized in that the above additional RACH configuration includes information about an offset.
4. In paragraph 3, A method characterized in that the second index is determined based on i) the index of the PRACH occasion and ii) the offset.
5. In paragraph 3, A method characterized in that the index of the PRACH occasion is determined based on the offset.
6. In paragraph 2, A method characterized in that information about the OFDM symbol index is set based on the additional RACH setting or a system information block (SIB).
7. In paragraph 2, A method characterized in that the above OFDM symbol index is predefined for the above additional RACH configuration.
8. In paragraph 7, A method characterized in that the OFDM symbol index is based on a symbol defined among symbols based on the PRACH occasion.
9. In paragraph 8, A method characterized in that the above defined symbol is the Nth symbol or the last symbol among the symbols based on the PRACH occasion.
10. In paragraph 1, A method characterized in that the above PRACH occasion is the last PRACH occasion among PRACH occasions based on a repetition number.
11. In paragraph 1, Further comprising a step of receiving downlink control information (DCI) related to a random access response (RAR); A method characterized in that the CRC (Cyclic Redundancy Check) associated with the DCI is scrambled by the RA-RNTI.
12. At the terminal, One or more transmitters and receivers; one or more processors; and One or more memories connected to said one or more processors and storing instructions, A terminal characterized in that the instructions are set to cause the one or more processors to perform all steps of the method according to any one of claims 1 to 11, based on being executed by the one or more processors.
13. In a device comprising one or more memories and one or more processors functionally connected to the one or more memories, A device characterized in that said one or more memories store instructions that cause said one or more processors to perform all steps of a method according to any one of claims 1 to 11, based on being executed by said one or more processors.
14. In one or more non-transitory computer-readable media storing instructions, One or more non-transitory computer-readable media characterized in that the instructions executable by one or more processors cause the one or more processors to perform all steps of the method according to any one of claims 1 to 11.
15. In a method performed by a base station, A step of transmitting a Random Access Channel (RACH) setting; and A step of receiving a random access preamble based on RA(Random Access)-RNTI(Radio Network Temporary Identifier); including, The above RA-RNTI is determined based on i) a first index related to the time domain of a physical random access channel (PRACH, occasion) and ii) a second index related to the frequency domain of the PRACH occasion, The above RACH setting is based on the additional RACH setting, A method characterized in that the first index or the second index is determined based on the additional RACH setting.
16. At the base station, One or more transmitters and receivers; one or more processors; and One or more memories connected to said one or more processors and storing instructions, A base station characterized in that the instructions are set to cause the one or more processors to perform all steps of the method according to claim 15, based on the instructions being executed by the one or more processors.
Citation Information
Patent Citations
Highly-durable conductive fiber with retained electrical properties after washing and its manufacturing method
KR103011806B1
Random access radio network temporary identifier for higher subcarrier spacing
US20230108411A1
Multi-preamble physical random access channel indication
WO2023014761A1
Using physical random access channel (PRACH) to identify multiple features and combinations of features
WO2023044025A1
Cited By
Random access techniques
WO2026129175A1
Additional random access channel (RACH) resource indexing
WO2026206228A1
Ra-RNTI determination for additional prach resources
WO2026207397A1
