Recovery / fallback after unsuccessful 2-step random access attempt

By detecting the failure of two-step random access in a wireless device and performing appropriate back-back, selecting the appropriate beam and RA configuration, the recovery problem after the failure of two-step random access in a 5G system is solved, and the connection efficiency and stability are improved .

CN114365575BActive Publication Date: 2024-12-03TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202080056843.7
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2019-06-10
Filing Date
2020-06-09
Publication Date
2024-12-03
Estimated Expiration
2040-06-09

AI Technical Summary

Technical Problem

In 5G wireless communication systems, if the two-step random access fails during the process of two-step random access, it is difficult for the existing technology to effectively recover and fall back, resulting in increased connection delay and waste of resources.

Method used

The detection and fallback mechanism of two-step random access attempts is realized in a wireless device. By selecting the appropriate beam and RA configuration, the two-step or four-step random access process is retryed to ensure connection stability and resource efficiency.

Benefits of technology

By dynamically adjusting the RA process, the uncertainty of access delay and resource allocation is reduced, the system flexibility and connection success rate are improved, and the network load and user waiting time are reduced.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN114365575B_ABST
    Figure CN114365575B_ABST
Patent Text Reader

Abstract

A method, system, network node, and wireless device for random access are provided. In one or more embodiments, the wireless device (22) is configured to communicate with the network node (16). The wireless device (22) includes a processing circuit (84) configured to: trigger a random access (RA) procedure; select a first beam for the RA procedure, the selected first beam being associated with a two-step RA configuration, a characteristic of the selected first beam being determined to satisfy a predefined threshold; and perform the RA procedure associated with the two-step RA configuration using the selected first beam.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates to wireless communications, and in particular to two-step random access, such as recovery and fallback after an unsuccessful two-step random access attempt. Background Art

[0002] Wireless communication systems in the 3rd Generation Partnership Project (3GPP)

[0003] refer to Figure 1 In the example of a simplified wireless communication system shown in , a wireless device WD 102 communicates with one or more access nodes 103-104 using radio connections 107-108. The access nodes 103-104 are connected to a core node 106. The access nodes 103-104 are part of a radio access network 100.

[0004] For wireless communication systems in accordance with the 3rd Generation Partnership Project (3GPP) Evolved Packet System EPS (also known as Long Term Evolution LTE or 4G) standard specifications (such as specified in 3GPP Technical Standard (TS) 36.300 and related specifications), the access nodes 103-104 generally correspond to evolved NodeBs (eNBs), and the network node 106 generally corresponds to a mobility management entity (MME) and / or a serving gateway (SGW). The eNB is part of the radio access network 100, which in this case is an E-UTRAN (Evolved Universal Terrestrial Radio Access Network), while both the MME and the SGW are part of the EPC (Evolved Packet Core).

[0005] For a wireless communication system in accordance with the 3GPP 5G system 5GS (also known as New Radio NR or 5G) standard specifications (such as specified in 3GPP TS38.300 and related specifications), the access nodes 103-104 generally correspond to 5G NodeBs (gNBs), and the core node 106 generally corresponds to an access and mobility management function (AMF) and / or a user plane function (UPF). The gNB is part of the radio access network 100, which in this case is a NG-RAN (Next Generation Radio Access Network), and both the AMF and the UPF are part of the 5G core network (5GC).

[0006] The nature of 5G / NR

[0007] The nature of the upcoming 5G system (e.g., NR) is to use high carrier frequencies, for example in the range of 24.25-52.6 GHz. The atmospheric, penetration, and diffraction attenuation properties may be much worse for such high frequency spectrum than for lower frequency spectrum. In addition, the receiver antenna aperture, which is a measure of the effective receiver antenna area that collects electromagnetic energy from incoming electromagnetic waves, is inversely proportional to the frequency, i.e., if omnidirectional receiving and transmitting antennas are used, the link budget will be worse for the same link distance even in a free space scenario. This motivates the use of beamforming to compensate for the loss of link budget in the high frequency spectrum. This may be important when communicating with WDs with poor receivers (e.g., low cost / low complexity WDs). Other means for improving the link budget include repetition of transmissions (e.g., allowing wide beam or omnidirectional transmissions) or the use of single frequency network transmissions of multiple total radiated powers (TRPs) from the same or different cells.

[0008] Due to the above properties, in high frequency bands, it is expected that many downlink signals (such as synchronization signals, system information, and paging) that should cover a certain area (i.e., not just targeting a single WD with a known position / direction) (e.g., a cell) are transmitted using beam scanning, i.e., the signal is transmitted in one beam at a time, sequentially changing the direction and coverage area of ​​the beam until the entire intended coverage area (e.g., a cell) has been covered by the transmission. In addition, in lower carrier frequencies, such as ranging from below 3 GHz to 6 GHz, it is still envisioned to use beamforming in NR to improve coverage, although there are fewer beams covering the cell area.

[0009] The signals and channels corresponding to the Primary Synchronization Signal (PSS), Secondary SS (SSS), Cell Specific Reference Signal (CRS) and Physical Broadcast Channel (PBCH) in LTE (which carries the Master Information Block (MIB) and Layer 1 generated bits), namely PSS, SSS, Demodulation Reference Signal (DMRS) for PBCH and PBCH (sometimes referred to as NR-PSS, NR-SSS, DMRS for NR-PBCH and NR-PBCH in NR), are put together in an entity / structure referred to as SS Block (SSB) or (in other terms) SS / PBCH Block (the term SS Block is usually used in 3GPP TSG-RAN WG2 (RAN2), while 3GPP TSG-RAN WG1 (RAN1) usually uses the term SS / PBCH Block). Therefore, SS Block, SSB and SS / PBCH Block are three synonyms (although SSB is actually an abbreviation of SS Block). PSS+SSS enables WDs to synchronize with the cell and also carries information from which the Physical Cell Identity (PCI) can be derived. The PBCH portion of the SSB, including the Demodulation Reference Signal (DMRS), carries a portion of the system information referring to the MIB (Master Information Block) or NR-MIB, 8 layer-1 generated bits, and the SSB index within the SS Burst Set. In high frequencies, SS blocks will be transmitted periodically using beam scanning. Multiple such beamformed SS block transmissions are grouped into SS burst sets that constitute a full beam scan of SS block transmissions. When many beams are used, longer gaps are inserted into the beam scan, such as 2 or 4 time slots (where each time slot contains 14 OFDM symbols). This effectively creates groups of SS block transmissions within a SS burst set, which may be referred to as SS bursts using outdated terminology.

[0010] The synchronization signal and PBCH block (SSB) consists of the primary synchronization signal (PSS) and the secondary synchronization signal (SSS), each of which occupies 1 symbol and 127 subcarriers, and the PBCH spans 3 OFDM symbols and 240 subcarriers, but leaves one symbol for the unused portion of the SSS on some of the subcarriers in the middle, such as Figure 2As shown in . The possible time positions of the SSB within the half frame are determined by the subcarrier spacing and the periodicity of the half frame, where the SSB is transmitted according to the network configuration. During the half frame, different SSBs can be transmitted in different spatial directions (i.e., using different beams, across the coverage area of ​​the cell). Multiple SSBs can be transmitted within the frequency span of the carrier. The PCI of SSBs transmitted at different frequency positions does not have to be unique, i.e., different SSBs in the frequency domain may have different PCIs. However, when an SSB is associated with the remaining minimum system information (RMSI), the SSB corresponds to a single cell with a unique NR cell global identifier (NCGI). Such an SSB is called a cell-defined SSB (CD-SSB). The primary cell (PCell) is associated with a CD-SSB located on the synchronization grid.

[0011] For PBCH, polar coding is used. In addition, WDs may assume the band-specific subcarrier spacing used for SSB, unless the network has configured the WDs to assume a different subcarrier spacing. PBCH symbols carry their own frequency-multiplexed DMRS. Quadrature Phase Shift Keying (QPSK) modulation is used for PBCH.

[0012] Similar to LTE, NR uses OFDM (Orthogonal Frequency Division Multiplexing) in the downlink (i.e., from the network node, gNB, eNB or base station to the user equipment or WD). The basic NR physical resources on the antenna ports can thus be viewed as Figure 3 The time-frequency grid shown in FIG. 1 shows resource blocks (RBs) in a 14-symbol slot. A resource block corresponds to 12 contiguous subcarriers in the frequency domain. Resource blocks are numbered in the frequency domain starting with 0 from one end of the system bandwidth. Each resource element corresponds to one OFDM subcarrier during one OFDM symbol interval.

[0013] Different subcarrier spacing values ​​are supported in NR. The supported subcarrier spacing values ​​(also called different numerologies) are given by Δf=(15×2 α )kHz, where α∈(0,1,2,3,4). Δf=15kHz is the basic (or reference) subcarrier spacing, which is also used in LTE.

[0014] In the time domain, downlink and uplink transmissions in NR can be organized into subframes of equal size, each subframe is 1ms, which is similar to LTE. The subframe is further divided into multiple slots of equal duration. The slot length for a subcarrier spacing of Δf=(15×2^α)kHz is 1 / 2^αms. At Δf=15kHz, there is only one slot per subframe, and the slot has 14 OFDM symbols.

[0015] As can be understood from the above, there are differences in the L1 time domain structure of the radio interface between LTE and NR. While LTE always has the same structure, NR has a different structure as it may include different so-called parameter sets (which in essence can be translated into different subcarrier spacings (SCS) and resulting differences in the time domain, e.g., the length of the OFDM symbol). In LTE, the L1 radio interface time domain structure consists of symbols, subframes and radio frames, where a 1ms subframe consists of 14 symbols (12 if an extended cyclic prefix is ​​used) and 10 subframes form a 10ms radio frame. In NR, the concepts of subframe and radio frame are reused in the sense that they represent the same time period (i.e., 1ms and 10ms), respectively, but their internal structure varies depending on the parameter set. For this reason, an additional term "slot" is introduced in NR, which is a time domain structure that always contains 14 symbols (for a normal cyclic prefix), regardless of the symbol length. Therefore, the number of slots and symbols in a subframe and radio frame varies with the parameter set, but the number of symbols in a slot remains consistent. The parameter sets and parameters are chosen so that a subframe always contains an integer number of slots (ie, no partial slots). More details on the physical layer structure are described below.

[0016] Downlink transmissions are dynamically scheduled, i.e., in each slot, the gNB transmits downlink control information (DCI) about which WDs the data will be transmitted to and on which resource blocks in the current downlink slot the data is transmitted. In NR, this control information is usually transmitted in the first one or two OFDM symbols in each slot. Control information is carried on the physical control channel (PDCCH) and data is carried on the physical downlink shared channel (PDSCH). The WD first detects and decodes the PDCCH, and if the PDCCH is successfully decoded, the WD then decodes the corresponding PDSCH based on the control information decoded in the PDCCH.

[0017] In addition to the PDCCH and PDSCH, there may be other channels and reference signals transmitted in the downlink.

[0018] Mobility in RRC_CONNECTED state in LTE and NR

[0019] An RRC_CONNECTED WD in LTE (also known as E-UTRA) may be configured by the network (e.g., a network node) to perform measurements, and when a measurement report is triggered, the network may send a handover command to the WD (RRConnectionReconfiguration with a field called mobilityControlInfo in LTE and RRCReconfiguration with a reconfigurationWithSync field in NR).

[0020] These reconfigurations are actually prepared by the target cell upon request from the source node (e.g., via the X2 or S1 interface in the case of E-UTRA-EPC, or via the Xn or NG interface in the case of E-UTRA-5GC / E-UTRA-NGC or NR), and take into account the existing Radio Resource Control (RRC) configuration that the WD has with the source cell (which is provided in the inter-node request). Along with other parameters, the reconfiguration provided by the target cell contains all the information that the WD should need to access the target cell, such as the random access configuration, the new C-RNTI (Radio Network Temporary Identifier) ​​assigned by the target cell, and security parameters that enable the WD to calculate new security keys associated with the target cell so that the WD can send a (encrypted and integrity protected) handover completion message on SRB1 based on the new security keys when accessing the target cell.

[0021] Figure 4 The flow signaling between the WD, source node, and target node during the handover process is outlined.

[0022] In both LTE and NR, there are some principles for handover (or more generally, mobility under RRC_CONNECTED):

[0023] Mobility under RRC_CONNECTED is network-based because the network has the best information about the current situation, such as load conditions, resources in different nodes, available frequencies, etc. From a resource allocation perspective, the network can also consider the situation of many WDs in the network.

[0024] • The network prepares the target cell before the WD accesses the cell. The source provides the WD with the RRC configuration to be used in the target cell, including the SRB1 configuration for sending the Handover (HO) Complete message.

[0025] The target C-RNTI is provided to the WD by the target node, i.e. the target identifies the WD for the HO Complete message from message 3Msg3 at MAC level. Therefore, there is no context fetching unless a failure occurs.

[0026] • To speed up handover, the network provides information on how to access the target, such as RACH configuration, for example, via a network node, so the WD does not have to acquire SI before handover.

[0027] • The WD may be provided with CFRA resources, ie, in this case, the target identifies the WD from the preamble (message 1 Msg1). This process can always be optimized with dedicated resources. In HO, there may be uncertainty about the final target, and there is uncertainty about timing.

[0028] Security should be prepared before the WD accesses the target cell, i.e., before sending the RRCConnectionReconfigurationComplete (in LTE) or RRCReconfigurationComplete (in NR) message, the keys should be refreshed based on new keys as well as ciphering and integrity protection so that the WD can be authenticated in the target cell.

[0029] • Supports both full reconfiguration and incremental reconfiguration so that HO commands can be minimized.

[0030] System Information in NR

[0031] In NR, system information (SI) is divided into "minimum SI" and "other SI", where the minimum SI is the SI required to access the cell. The minimum SI consisting of the master information block (MIB) and SIB1 (where SIB1 is also called the remaining minimum system information RMSI) is broadcast periodically in the cell, while other SI can be broadcast periodically or delivered on demand, for example, triggered by a random access preamble (also called Msg1) or random access message 3 (also called Msg3) from a WD in RRC_IDLE or RRC_INACTIVE state, or via RRC signaling request from a WD in RRC_CONNECTED state. If a random access preamble (Msg1) is used for transmission, different preambles may be used to request different parts of other SI (e.g., (one or more) SIBs or SIB groups or (one or more) SI messages). If random access message 3 (Msg3) transmission is used, the WD may specify in such a message which parts of other SI (eg, SIB(s) or SIB groups or SI message(s)) the WD wants the network to broadcast / transmit.

[0032] With the Msg1 solution, reception of one of the relevant dedicated preambles triggers the network to broadcast the requested SIB(s) according to the scheduling information in the minimum SI. The network (i.e., gNB) also transmits, in response to Msg1, a Msg2 to the requesting WD confirming successful reception of Msg1 and confirming that the requested SI will be broadcast. When the WD uses the Msg1 method to request on-demand SI, the WD selects the preamble associated with the desired on-demand SI (as specified in the minimum SI) and transmits the preamble to the network using PRACH resources. The WD then waits for confirmation of Msg2 (during the Msg2 window), and after receiving the confirmation Msg2, the WD monitors the downlink for broadcasting the requested SI according to the scheduling information of the requested SI as indicated in the minimum SI. Figure 5 The process is shown in FIG.

[0033] With the Msg3 solution, the request process starts like a regular random access process - that is, the WD transmits one of the regular (non-dedicated) preambles in Msg1 and receives a regular Msg2 in response, where Msg2, like any regular Msg2, allocates uplink transmission resources for the transmission of Msg3, and provides a timing advance indication to enable the WD to transmit Msg3 with the correct timing. The SI request included in Msg3 triggers the network to broadcast / transmit the portion of other SI specified in Msg3 from the WD according to the scheduling information in the minimum SI. The network (i.e., gNB) also transmits Msg4 confirming the successful reception of Msg3 and confirming that the requested SI will be broadcast. When the WD uses the Msg3 method for requesting on-demand SI, the WD randomly selects one of the regular non-dedicated preambles (as specified in the minimum SI) and transmits the preamble to the network using PRACH resources. Then, the WD waits for Msg2 (during the Msg2 window), and after receiving Msg2, the WD transmits Msg3 (using the timing advance and uplink transmission resources indicated in Msg2), and monitors the downlink for confirmation Msg4. After receiving confirmation Msg4, the WD monitors the downlink for broadcasting the requested SI according to the scheduling information of the requested SI as indicated in the minimum SI. Figure 6 The process is shown in FIG.

[0034] The MIB is transmitted on the PBCH as part of the SS block and can thus be found when the WD has detected the PSS / SSS. The MIB in turn includes information that allows the WD to receive the system information block SIB1. And as mentioned above, SIB1 contains scheduling information for other SIBs, as well as an indication of whether they are broadcast periodically or provided on demand.

[0035] Operation in unlicensed spectrum

[0036] For LTE, 3GPP has specified standards for LTE-based communications in unlicensed spectrum, i.e., coexistence with other systems such as Wi-Fi. For LTE, this is enabled only in close interworking (e.g., dual connectivity) with systems using licensed spectrum (i.e., conventional LTE). LTE-based communications in unlicensed spectrum in this way are labeled as licensed assisted access (LAA). For NR, such a system is referred to as unlicensed NR (NR Unlicensed) (NR-U). NR-U will be specified for both close interworking (e.g., dual connectivity) with conventional NR systems and as an independent system. Compared to conventional NR in licensed spectrum, coexistence with other systems (and other NR-U systems / cells) in unlicensed spectrum requires different operations at the physical layer, including, for example, the listen-before-talk (LBT) principle, i.e., clear channel assessment (CCA), where the gNB or WD listens to the radio channel to verify that the channel is idle (unused) before accessing the medium for transmission. The inherently uncoordinated operation of different systems in unlicensed spectrum also makes the signal more susceptible to destructive interference.

[0037] Random Access Channel (RACH) Configuration in NR

[0038] As with LTE, the random access procedure is described in the NR MAC specification and the parameters are configured by RRC, for example, in system information or handover (RRCReconfiguration with reconfigurationWithSync). Random access is triggered in many different situations, for example, when the WD is in RRC_IDLE or RRC_INACTIVE and wants to access the cell on which the WD is camping (i.e., transitioning to RRC_CONNECTED).

[0039] In NR, the RACH configuration is broadcasted in SIB1 as part of the servingCellConfigCommon information element (IE) (with both DL and UL configurations), where the RACH configuration is within the uplinkConfigCommon IE. The exact RACH parameters are within the so-called initialUplinkBWP, as this is the part of the UL frequency where the WD can access and search for RACH resources.

[0040] Example RACH configuration parameters (as described in 3GPP TS 38.331) are shown below, focusing mainly on parameters related to the mapping of preamble and RACH resources / opportunities, which in future versions of the specification may also potentially be mapped to PUSCH resources for MsgA transmission in 2-step random access.

[0041] RACH-ConfigGeneric Information Element

[0042]

[0043]

[0044]

[0045] RACH-ConfigCommon Information Element

[0046]

[0047]

[0048]

[0049]

[0050]

[0051]

[0052] In NR, random access resource selection may be performed within a cell, depending on measurements performed on the SSB (Synchronization Signal Block) or CSI-RS. A cell in NR is essentially defined by a set (one or more) of these SSBs, which may be transmitted in one or more downlink beams (where a single or a few SSBs / beams are more suitable for lower carrier frequencies, e.g. below 6 GHz, while implementations with many SSBs / beams are more suitable for higher carrier frequencies). For the same cell, these SSBs carry the same physical cell identifier (PCI) and MIB. For standalone operation, i.e. to support WDs residing on NR cells, they also carry the RACH configuration in SIB1, which includes a mapping between the detected SSBs of the covering WD at a given point in time and the PRACH configuration to be used (e.g. time, frequency, preamble, etc.). To this end, each of these beams may transmit its own SSB, which may be represented by Figure 7 The SSB index is shown in .

[0053] The mapping between RACH resources and SSBs (or CSI-RS) is also provided as part of the RACH configuration (in RACH-ConfigCommon, as shown above). There are two settings that are relevant here:

[0054] #SSBs-per-PRACH-occasion: 1 / 8, 1 / 4, 1 / 2, 1, 2, 8, or 16, which indicates the number of SSBs per RACH occasion; and

[0055] ·#CB-preambles-per-SSB preambles per SS block: how many preambles are allocated within the RACH opportunity.

[0056] For example, if the number of SSBs per RACH opportunity is 1, and if the WD is under the coverage of a particular SSB (e.g., with SSB index 2), there will be a RACH opportunity for that SSB index 2. If the WD moves and is now under the coverage of another particular SSB (e.g., with SSB index 5), there will be another RACH opportunity for that SSB index 5, i.e., each SSB detected by a given WD will have its own RACH opportunity. Therefore, on the network side, when a preamble is detected at a particular RACH opportunity, the network knows which SSB the WD has selected, and therefore which downlink beam is covering the WD, so that the network can use that beam to continue downlink transmissions, such as random access responses (RARs), etc. The factor 1 is an indication that each SSB has its own RACH resource, i.e., the preamble detected in that RACH resource / opportunity indicates to the network which SSB the WD has selected, i.e., which DL beam the network should use to communicate with the WD, such as the beam that sent the RAR. Figure 8 is the time-frequency diagram of the channel and synchronization signal. Fig. 9 is an alternative time-frequency diagram of the channel and synchronization signal.

[0057] For example, if #SSBs-per-PRACH-occasion has CHOICE equal to 1 / 8, there will be 8 RACH opportunities for each SSB, and if n12 is set, there will be 12 preambles chosen by the WD for that selected SSB, i.e., up to 12 WDs may be multiplexed in the same RACH opportunity.

[0058] Note that each SS block is typically mapped to multiple preambles (different cyclic shifts and Zadoff-Chu roots) within a PRACH opportunity, making it possible to multiplex different WDs in the same RACH opportunity since they can be under the coverage of the same SSB. In the second example shown below, the number of SSBs per RACH opportunity is 2. Therefore, the preamble received in this RACH opportunity indicates to the network that one of the two beams is being selected by the WD. Therefore, the network either has a component that distinguishes the two beams via implementation, and / or should perform beam scanning in the downlink, by either transmitting the RAR in both beams simultaneously, or transmitting in one beam, waiting for a response from the WD, and if not present, transmitting in the other. Within a RACH opportunity, the network may also configure different preambles (sets) for different SSBs mapped to the RACH opportunity, so that the preamble indicates to the network which of the SSB beams mapped to the RACH opportunity the WD has selected (and therefore in which DL beam the response should be transmitted).

[0059] According to 3GPP TS 38.211, the random access preamble may be transmitted only in the time resources given by the higher layer parameter prach-ConfigurationIndex according to Tables 6.3.3.2-2 to 6.3.3.2-4 in 3GPP TS 38.211 and depends on FR1 or FR2 and the spectrum type. The random access preamble may only be transmitted in the frequency resources given by the higher layer parameter msg1-FrequencyStart.

[0060] Beam selection and mapping to specific RACH resources for preamble transmission is defined as part of the random access procedure as part of the Medium Access Control (MAC) specification (3GPP TS 38.321) and is sometimes referred to as RACH resource selection.

[0061] See Appendix A for additional examples of random access procedure initialization and random access resource selection.

[0062] WD actions upon expiration of Random Access Response (RAR) timer in 4-step random access in NR

[0063] Now assume that: in the first attempt, the WD has selected an SSB (based on measurements performed in the cell), has transmitted the selected preamble associated with the PRACH resource mapped to the selected SSB at the initial power, and has not received the RAR within the RAR time window (i.e., the timer associated with the RAR time window expires). According to the MAC specification (3GPP TS 38.321), the WD may still perform a preamble retransmission (i.e., the maximum number of allowed transmissions has not been reached).

[0064] As in LTE, at each preamble retransmission attempt, the WD can assume the same SSB as the previous attempt and perform a power ramp similar to LTE. The maximum number of attempts is also defined in NR, which is also controlled by the parameter PREAMBLE_TRANSMISSION_COUNTER.

[0065] On the other hand, unlike LTE, at each preamble retransmission attempt, the WD may alternatively select a different SSB, as long as the new SSB has acceptable quality (i.e., its measurements are above a configurable threshold). In this case, when a new SSB (or more generally, a new beam) is selected, the WD does not perform a power ramp, but transmits the preamble at a transmit power targeting the same target receive power at the receiving node (e.g., gNB) as the previous preamble transmission. This is Fig.10 Shown in .

[0066] Note that when the WD reselects a new beam, despite the lack of power ramping, the preamble transmission power may be different from the transmission power used for the previous preamble transmission because the transmission power is calculated based on the received power target at the receiver and the estimated path loss, where the estimated path loss may be different in different beams.

[0067] For this reason, a new variable called PREAMBLE_POWER_RAMPING_COUNTER is defined in the NR MAC specification (3GPP TS 38.321) to prevent the same beam from being selected on retransmission. At the same time, the previous LTE variable (PREAMBLE_TRANSMISSION_COUNTER) still exists in the NR MAC specification so that the total number of attempts is still limited, regardless of whether the WD performs SSB / beam reselection or power ramping on each attempt.

[0068] Thus, if, for example, the initial preamble transmission associated with SSB-2 is unsuccessful, and the WD selects the same SSB / beam, the PREAMBLE_POWER_RAMPING_COUNTER is incremented (i.e., set to 2 in this second attempt), and the transmission power will be:

[0069] PREAMBLE_RECEIVED_TARGET_POWER=preambleReceivedTargetPower+DELTA_PREAMBLE+1*PREAMBLE_POWER_RAMPING_STEP;

[0070] Otherwise, if instead the WD selects a different SSB / beam, the PREAMBLE_POWER_RAMPING_COUNTER is not incremented (i.e. remains at 1), and the transmit power will be the same as the first transmission:

[0071] PREAMBLE_RECEIVED_TARGET_POWER=preambleReceivedTargetPower+DELTA_PREAMBLE;

[0072] In summary, when a preamble is sent and no RAR is received, the WD can either select the same beam and perform power ramping before the next attempt, or perform beam reselection.

[0073] Fallback between CFRA and CBRA during beam selection / reselection in 4-step RACH (legacy):

[0074] This beam selection / reselection process upon expiration of the RAR timer becomes slightly more complicated when, for example in the case of handover, the WD is also configured with contention-free random access (CFRA) resources for at least one beam (e.g., specific SSBs and / or CSI-RS). As described in the stage 2 specification (e.g., 3GPP TS 38.300), the following is allowed as a possible configuration from the network to the WD:

[0075] The common RACH configuration of the beam in the target cell is only associated with (one or more) SSBs;

[0076] The network may have a dedicated RACH configuration associated with (one or more) SSBs and / or have a dedicated RACH configuration associated with (one or more) CSI-RS within a cell;

[0077] Possible combinations:

[0078] a) Common RACH configuration (SSB only);

[0079] b) Dedicated RACH configuration + common RACH configuration associated with SSB;

[0080] c) Common RACH configuration + dedicated RACH configuration associated with CSI-RS.

[0081] The dedicated RACH configuration allocates (one or more) RACH resources along with a quality threshold for their use. When dedicated RACH resources are provided, they are prioritized by the WD and as long as the quality threshold for those dedicated resources is met, the WD should not switch to contention-based RACH resources. The order of accessing dedicated RACH resources depends on the WD implementation.

[0082] Another aspect is the prioritization of CSI-RS based random access resource selection over SSB based random access resource selection. What this means is that the random access resource selection is based on a specific RS type (e.g., SSB) and the WD performs measurements on that specific RS type to perform beam selection, which is implicitly a random access resource selection.

[0083] It shows how CFRA takes precedence over CBRA, and in each case how CSI-RS based random access takes precedence over SSB based random access:

[0084] See Appendix B for an example of section 5.1.2 of 3GPP Technical Standard (TS) 38.321.

[0085] Two-step random access

[0086] 2-step random access is a possible modification to the conventional 4-step random access procedure, which has been discussed at, for example, TSG-RAN Plenary Meeting #82, where it was decided that a 2-step random access procedure should be specified for NR (including NR-U, i.e. NR operating in unlicensed spectrum).

[0087] This variation of the random access procedure can be simply described as the collection of Msg1 and Msg3 into a single first step transmitted by the WD in the form of a message labeled MsgA, followed by a second final step consisting of the combination of Msg2 and Msg4 labeled MsgB. Thus, MsgA contains the random access preamble transmitted on PRACH transmission resources combined with the transmission of the remainder of MsgA (corresponding to Msg3) on PUSCH transmission resources.

[0088] The term "MsgA" may have one or more definitions / interpretations. One interpretation is that it contains Msg1+Msg3, while another interpretation is that MsgA corresponds only to Msg3. According to the former definition, the first step of the 2-step RA procedure thus consists of MsgA, which is divided into two transmissions, one (the preamble) on the PRACH and one (the part of MsgA corresponding to Msg3) on the PUSCH. With the latter definition, the first step of the 2-step RA procedure instead consists of the transmission of the preamble (on the PRACH resources) and the transmission of MsgA (on the PUSCH resources). The former definition seems to have the most support, and this is the definition used in the present disclosure. With this definition, the PUSCH transmission of the first step of the 2-step RA procedure is sometimes referred to as the "payload of MsgA", and another possible term is the "PUSCH part of MsgA". The present disclosure introduces the abbreviation MsgA PUSCH Refers to the part of MsgA transmitted on PUSCH.

[0089] Figure 11-12 A comparison between 2-step RA and conventional RA is shown.

[0090] One of the benefits of 2-step RA is delay gain. Fig.13 The delay calculation for LTE is shown in FIG. 1. It can be seen that the minimum delay from the WD transmitting the RA preamble in the 4-step conventional process until receiving the final response is 13 subframes (preamble at x, RAR at x+3, Msg3 at x+3+6, Msg4 at x+3+6+4).

[0091] Depending on the parameter set or TTI duration used in NR, this will result in a delay of no more than 13ms until the RA procedure is completed. In the 2-step process shown below, even when assuming the long processing delay currently specified for LTE, the corresponding minimum delay is 4 subframes, i.e. 4ms (MsgA (i.e. preamble + MsgA PUSCH At x, MsgB (i.e., Msg2+Msg4) is at x+4). Therefore, the 2-step process can result in approximately a 3x reduction compared to the 4-step process. Even when NR achieves a shorter processing time compared to LTE, the 2-step RA process provides significant latency reduction compared to the traditional 4-step process. Fig.14 It is the delay diagram of the two-step RA process.

[0092] According to some proposals for a yet-to-be-written 2-step RA specification, the Random Access Preamble and will be used for MsgA PUSCH There may be an association between the PUSCH transmission resources of the preamble code and the PUSCH resource. This preamble-PUSCH resource association may potentially be one-to-one or even one-to-many.

[0093] Therefore, there may be a set of preambles dedicated to 2-step RA in a cell. Alternatively, a separate PRACH resource (e.g., time / frequency resource) may be provided for 2-step RA. In the latter case, there may be, for example, N frequency-multiplexed PRACH resources (i.e., occurring simultaneously but on different frequencies, e.g., on different subcarriers), of which M (M≤N) of these PRACH resources are associated with conventional 4-step RA, and the remaining NM PRACH resources are associated with 2-step RA.

[0094] In RAN2#105bis, the following is discussed:

[0095] The criteria on whether the WD uses 2-step RACH or 4-step RACH should be clearly defined.

[0096] The start of the msgB receive window is after the PUSCH transmission opportunity of msgA. For 2-step RACH and fallback, the details are for further study (FFS), i.e., currently undefined.

[0097] If CCCH SDU is included in MsgA, contention resolution may be based on the contention resolution ID included in MsgB. For other conditions, FFS.

[0098] Other Discussions

[0099] 1. 2-step RACH is applicable to SI request based on Msg3.

[0100] 2. 2-step RACH is applicable to CB BFR. For CFRA, FFS

[0101] 2-step RA reduces access latency and, for NR-U, also reduces the number of times the channel has to be accessed through a listen-before-talk (LBT) procedure. However, there is a cost in terms of transmission resources, since PUSCH transmission resources for transmitting MsgAPUSCH (e.g., RRCSetupRequest message, RRCResumeRequest message, or similar HO completion messages such as RRCReconfigurationComplete) have to be allocated for each 2-step RA opportunity, regardless of whether they are used. In addition, MsgAPUSCH transmissions themselves are not very resource efficient since they are transmitted without dynamic link adaptation (i.e., since the preamble on the PRACH is not included, this is the first transmission to the network, so the default configuration is used). Therefore, 2-step RA may be used with caution, including the configuration of the 2-step RA opportunities (PRACH resources and PUSCH resources), and methods for selectively applying 2-step RA based on relevant criteria may be desired.

[0102] Due to different trade-offs in terms of load, network efficiency, and latency, it is described herein that for a given target cell, for example, on a per-beam basis (e.g., SSB or CSI-RS resource), the WD may be configured with:

[0103] - 2-step CFRA;

[0104] - 2-step CBRA;

[0105] - 4-step CFRA; or

[0106] -4 step CBRA.

[0107] Any combination of these, e.g., 2-step CBRA and 4-step CFRA in a given beam;

[0108] In initial 3GPP releases, 2-step CFRA may not be supported, i.e., for example, for a given SSB or CSI-RS being selected, the following combinations may be possible:

[0109] 2-step CBRA+4-step CFRA+4-step CBRA.

[0110] At least in the case of CFRA, this may be available only for a subset of beams (e.g., a subset of specific SSBs of the target cell, a subset of specific CSI-RS of the target cell, etc.), while 2-step CBRA and 4-step CBRA may be configured for all subsets. Fig.15 is an example of the RA selection method.

[0111] Flexible configurations and how WDs can perform resource selection according to various possible configurations are described herein. In terms of prioritization, multiple configurations can be provided for the same selected beam, even allowing the WD to prioritize a certain beam available for a specific configuration, such as 2-step RA.

[0112] Additionally, this only addresses initial resource selection for the first RA preamble transmission attempt based on the configuration provided. In other words, it is unclear what kind of prioritization should be performed if the WD tries the first method for initial resource selection (e.g., 2-step RA) and is unsuccessful.

[0113] Some high-level discussions about fallback between 2-step RA and 4-step RA occurred in RAN2#106, mainly concerning failure detection (which is performed via reception of RAR) and this possibility. The following are the conventions from these discussions:

[0114] From RAN2 perspective, 2-step RACH selection can be based on indication to all WDs via SIB, or dedicated configuration in RRC_CONNECTED / INACTIVE / IDLE state. If radio quality is used for 2-step RACH selection, then FFS.

[0115] From RAN2 perspective, for msgA retransmission (ie preamble and PUSCH), it is assumed that WD retries on 2-step RACH.

[0116] Whether WD can fall back to 4-step RACH, FFS after a certain period of time. RAN1 determines whether the preamble transmission performance of 2-step RACH and 4-step RACH is the same.

[0117] …

[0118] For CCCH, MsgB may include an SRB RRC message. The format may be designed for both with and without an RRC message.

[0119] …

[0120] The network's response to msgA (i.e. msgB / msg2) may include the following:

[0121] a)SuccessRAR;

[0122] b) FallbackRAR; and / or

[0123] c) Backoff instruction.

[0124] FFS: format of successRAR and whether successRAR is split into more than one message and format of fallbackRAR and whether legacy msg2 can be reused for fallbackRAR

[0125] …

[0126] Upon receiving the fallbackRAR, the WD may enter the msg3 step of the 4-step RACH process.

[0127] FallbackRAR can contain the following fields

[0128] a) RAPID;

[0129] b) UL grant (retransmission of msgA payload). If different grant and reestablishment, restrictions on grant and WD behavior, FFS;

[0130] c) TC-RNTI; and

[0131] d)TA command

[0132] From the RAN2 perspective, no further offset is used for the start of the msgB monitoring window (ie no offset is used to cover RRC processing delays and / or F1 delays).

[0133] WD 22 may use a single msgB-agreed window to monitor for response messages.

[0134] MsgB containing successRAR may not be multiplexed with the traditional 4-step RACH RAR in the same MACPD

[0135] Despite these conventions and discussions, many issues remain unresolved, for example, regarding 2-step RA errors and fallback situations. For example, it is unresolved what happens in the case of contention-free random access (CFRA) (e.g., if a 4-step CFRA configuration is available in parallel with a 2-step RA (e.g., 2-step CBRA)). Prioritization and how priorities work in conjunction with resource selection at fallback (e.g., whether the WD must always try the same beam, or whether the WD is allowed to reselect another beam, or even another RS ​​type, etc.) are open issues that remain unresolved. Summary of the invention

[0136] Some embodiments advantageously provide methods and WDs for recovery and fallback after an unsuccessful two-step random access attempt.

[0137] Some embodiments include a method at a wireless device (WD) (also referred to herein as a user equipment - UE) for performing a random access including a fallback action upon detecting that a 2-step random access attempt was not successfully completed. The WD action may include:

[0138] Selecting a random access resource when random access is triggered, and selecting a beam (e.g., SSB or CSI-RS resource) with associated random access configuration(s), and initiating a 2-step RA configuration if the selected beam has a configuration available for 2-step RA and satisfies the conditions for performing 2-step RA;

[0139] Detecting an unsuccessful attempt to perform a 2-step RA (e.g., by receiving an RAR-like message such as a fallback RAR instead of MsgB, by monitoring the expiration of a timer for a response to MsgA, or by receiving MsgB containing contention resolution information. An example is a WD contention resolution identity media access control (MAC) control element (CE) indicating that MsgB is intended for another WD (i.e., contention resolution failed));

[0140] Determine appropriate fallback actions or other responses to detected faults based on configuration and / or current conditions; and

[0141] ·Perform fallback actions or other responses determined in response to detected failures.

[0142] The fallback action may be either a prepared fallback (controlled by explicit indication from the network), e.g., fallback to 4-step RA (e.g., if the network responds to MsgA with a RAR-like message), or an unprepared fallback (uncontrolled, no explicit indication from the network) (e.g., if the WD does not receive a RAR-like message). Fallback actions or other reactions may include:

[0143] Re-initiate the 2-step RA procedure using the 2-step RA configuration for the same beam (with or without power ramping);

[0144] Initiate 4-step CFRA (if configuration is available) using the 4-step CFRA configuration of the same beam (with or without power ramping);

[0145] Falling back to 4-step CBRA (with or without power ramping) using the same beam’s 4-step CBRA configuration; or

[0146] Fall back to beam (re)selection and re-initiate the random access procedure (2-step RA, 4-step CFRA or 4-step CBRA) using the RA configuration associated with the alternative beam.

[0147] With the methods and / or processes described herein, the WD may appropriately fall back from 2-step RA to 4-step RA when such a fallback is beneficial. In some cases, it may be possible to try 2-step RA again (e.g., in the same beam or in a different beam with available 2-step RA configuration and resources and with good radio conditions) or, for example, to only try to perform 4-step RA in the same beam (in cases where a more robust fallback process is desired).

[0148] According to one aspect of the present disclosure, a wireless device is configured to communicate with a network node. The wireless device includes a processing circuit configured to: trigger a random access (RA) procedure; select a first beam for the RA procedure, the selected first beam being associated with a two-step RA configuration, a characteristic of the selected first beam being determined to satisfy a predefined threshold; and perform the RA procedure associated with the two-step RA configuration using the selected first beam.

[0149] According to one or more embodiments of this aspect, the processing circuit is further configured to: receive system information; and determine, based at least on the system information, whether the selected first beam is associated with a two-step RA configuration, the two-step RA configuration corresponding to a mapping of the selected first beam to a physical uplink shared channel PUSCH configuration. According to one or more embodiments of this aspect, the selected first beam is selected from a plurality of beams, a subset of the plurality of beams being associated with the two-step RA configuration. According to one or more embodiments of this aspect, the subset of the plurality of beams is one of: a subset of a synchronization signal block SSB beam and a set of a channel state information reference signal CSI-RS beam.

[0150] According to one or more embodiments of this aspect, a subset of the SSB beams is associated with a contention-free RA resource for a contention-free RA. According to one or more embodiments, at least one other beam in the plurality of beams is not associated with a two-step RA configuration. According to one or more embodiments of this aspect, at least one of the subset of beams is associated with a contention-based RA, and the contention-free RA is prioritized over the contention-based RA. According to one or more embodiments of this aspect, the characteristic of the selected first beam is a channel quality, and the predefined threshold is a channel quality threshold.

[0151] According to one or more embodiments of this aspect, the processing circuit is further configured to: determine that a step of the two-step RA procedure has failed; and in response to determining that a step of the two-step RA procedure has failed, perform one of the following: retransmit the uplink shared channel portion of message A msgA as an uplink shared channel message in a four-step RA procedure; and retry the two-step RA procedure at least in part by performing beam reselection. According to one or more embodiments of this aspect, the processing circuit is further configured to determine that a step of the two-step RA procedure has failed based on one of the following: lack of a response to msgA; receiving a random access response RAR message including backoff information; and receiving a message B msgB including first information indicating that a step of the two-step RA procedure has failed.

[0152] According to one or more embodiments of this aspect, the backoff information includes an indication that a step of the two-step RA process has failed. According to one or more embodiments of this aspect, the first information is contention resolution information. According to one or more embodiments of this aspect, the retransmission is performed based on reselecting a beam from a plurality of beams, the reselection including using a contention-free RA resource configured for one of a channel state information reference signal CSI-RS and a synchronization signal block SSB.

[0153] According to another aspect of the present disclosure, a method implemented by a wireless device configured to communicate with a network node is provided. A random access (RA) procedure is triggered. A first beam is selected for the RA procedure, wherein the selected first beam is associated with a two-step RA configuration, and wherein a characteristic of the selected first beam is determined to satisfy a predefined threshold. The RA procedure associated with the two-step RA configuration is performed using the selected first beam.

[0154] According to one or more embodiments of this aspect, system information is received, and a determination is performed based at least on the system information as to whether the selected first beam is associated with a two-step RA configuration, and wherein the two-step RA configuration corresponds to a mapping of the selected first beam to a physical uplink shared channel (PUSCH) configuration. According to one or more embodiments of this aspect, the selected first beam is selected from a plurality of beams, a subset of the plurality of beams being associated with the two-step RA configuration. According to one or more embodiments of this aspect, the subset of the plurality of beams is one of: a subset of synchronization signal block (SSB) beams and a set of channel state information reference signal (CSI-RS) beams.

[0155] According to one or more embodiments of this aspect, a subset of the SSB beams is associated with contention-free RA resources for contention-free RA. According to one or more embodiments of this aspect, at least one other beam in the plurality of beams is not associated with a two-step RA configuration. According to one or more embodiments of this aspect, at least one of the subset of beams is associated with contention-based RA, and contention-free RA takes precedence over contention-based RA.

[0156] According to one or more embodiments of this aspect, the characteristic of the selected first beam is a channel quality, and the predefined threshold is a channel quality threshold. According to one or more embodiments of this aspect, determining that a step of the two-step RA procedure has failed; and in response to determining that a step of the two-step RA procedure has failed, performing one of the following: retransmitting the uplink shared channel portion of message A msgA as an uplink shared channel message in a four-step RA procedure; and retrying the two-step RA procedure at least in part by performing beam reselection. According to one or more embodiments of this aspect, determining that a step of the two-step RA procedure has failed is based on one of the following: lack of a response to msgA; receiving a random access response RAR message including backoff information; and receiving a message BmsgB including first information indicating that a step of the two-step RA procedure has failed.

[0157] According to one or more embodiments of this aspect, the backoff information includes an indication that a step of the two-step RA procedure has failed. According to one or more embodiments of this aspect, the first information is contention resolution information. According to one or more embodiments of this aspect, the retransmission is performed based on reselecting a beam from a plurality of beams, wherein the reselection includes using a contention-free RA resource configured for one of a channel state information reference signal CSI-RS and a synchronization signal block SSB.

[0158] According to another aspect of the present disclosure, a network node configured to communicate with a wireless device is provided. The network node includes a processing circuit configured to: associate multiple beams with multiple random access RA configurations, a first beam of the multiple beams is associated with a two-step RA configuration; and perform an RA procedure using the first beam based on the two-step RA configuration associated with the first beam.

[0159] According to one or more embodiments of this aspect, the processing circuit is further configured to transmit system information indicating multiple RA configurations. According to one or more embodiments of this aspect, a subset of the multiple beams is associated with the two-step RA configuration. According to one or more embodiments of this aspect, the subset of the multiple beams is one of the following: a subset of synchronization signal block SSB beams and a set of channel state information reference signal CSI-RS beams.

[0160] According to one or more embodiments of this aspect, a subset of the SSB beams is associated with a contention-free RA resource for a contention-free RA. According to one or more embodiments of this aspect, at least one of the subset of beams is associated with a contention-based RA, the contention-free RA taking precedence over the contention-based RA. According to one or more embodiments of this aspect, at least one other beam in the plurality of beams is not associated with a two-step RA configuration.

[0161] According to one or more embodiments of this aspect, the processing circuit is further configured to perform one of the following: receiving the uplink shared channel portion of the transmission of message A msgA as an uplink shared channel message in the four-step RA process; and determining that a beam reselection has occurred, the beam selection being associated with a retry of performing the two-step RA process. According to one or more embodiments of this aspect, the processing circuit is further configured to: determine that the two-step RA process has failed; and in response to the determination that the two-step RA process has failed, perform one of the following: transmitting a random access response RAR message including backoff information; and transmitting a message B msgB including first information indicating that a step of the two-step RA process has failed. According to one or more embodiments of this aspect, the backoff information includes an indication that a step of the two-step RA process has failed. According to one or more embodiments of this aspect, the first information is contention resolution information.

[0162] According to another aspect of the present disclosure, a method implemented by a network node configured to communicate with a wireless device is provided. A plurality of beams are associated with a plurality of random access RA configurations, wherein a first beam of the plurality of beams is associated with a two-step RA configuration, and based on the two-step RA configuration associated with the first beam, an RA procedure using the first beam is performed.

[0163] According to one or more embodiments of this aspect, system information is transmitted, wherein the system information indicates a plurality of RA configurations. According to one or more embodiments of this aspect, a subset of the plurality of beams is associated with a two-step RA configuration. According to one or more embodiments of this aspect, the subset of the plurality of beams is one of: a subset of synchronization signal block (SSB) beams and a set of channel state information reference signal (CSI-RS) beams.

[0164] According to one or more embodiments of this aspect, a subset of the SSB beams is associated with a contention-free RA resource for a contention-free RA. According to one or more embodiments of this aspect, at least one of the subset of beams is associated with a contention-based RA, the contention-free RA taking precedence over the contention-based RA. According to one or more embodiments of this aspect, at least one other beam in the plurality of beams is not associated with a two-step RA configuration.

[0165] According to one or more embodiments of this aspect, an uplink shared channel portion of a transmission of message A msgA is received as an uplink shared channel message in a four-step RA procedure; and a beam reselection is determined to have occurred, wherein the beam selection is associated with a retry of performing a two-step RA procedure. According to one or more embodiments of this aspect, a determination is made that the two-step RA procedure has failed, and in response to the determination that the two-step RA procedure has failed, one of the following is performed: a random access response RAR message is transmitted including backoff information; and a message B msgB is transmitted including first information indicating that a step of the two-step RA procedure has failed. According to one or more embodiments of this aspect, the backoff information includes an indication that a step of the two-step RA procedure has failed. According to one or more embodiments of this aspect, the first information is contention resolution information.

[0166] According to another aspect of the present disclosure, a computer storage medium stores computer instructions, which, when executed by a processor, cause the processor to control and / or perform any one of the above methods. BRIEF DESCRIPTION OF THE DRAWINGS

[0167] A more complete understanding of the present embodiments and the attendant advantages and features thereof will be more readily appreciated by reference to the following detailed description when considered in conjunction with the accompanying drawings, in which:

[0168] Figure 1 is an example of a simplified wireless communication system;

[0169] Figure 2 Channel and synchronization signals are shown;

[0170] Figure 3 is the time-frequency grid;

[0171] Figure 4 The signaling between the WD, source node, and target node during the handover process is summarized;

[0172] Figure 5 Summarizes the signaling between WD and gNB;

[0173] Figure 6 Summarizes additional signaling between WD and gNB;

[0174] Figure 7 shows indexed synchronization signal signaling;

[0175] Figure 8 A time-frequency diagram of the channel and synchronization signals is shown;

[0176] Fig. 9 Alternative time-frequency diagrams of channels and synchronization signals are shown;

[0177] Fig.10Successive attempts to receive the RAR are shown;

[0178] Fig.11 is a comparison between 2-step RA and traditional RA;

[0179] Fig.12 is a comparison between 2-step RA and 4-step RA;

[0180] Fig.13 is a timing diagram of random access message exchange;

[0181] Fig.14 is a timing diagram of random access message exchange;

[0182] Fig.15 is an example of RA selection method;

[0183] Fig.16 is a schematic diagram of an exemplary network architecture showing a communication system connected to a host computer via an intermediate network according to the principles of the present disclosure;

[0184] Fig.17 is a block diagram of a host computer communicating with a wireless device via a network node over an at least partially wireless connection according to some embodiments of the present disclosure;

[0185] Fig.18 is a flow chart illustrating an exemplary method for executing a client application at a wireless device implemented in a communication system including a host computer, a network node, and a wireless device according to some embodiments of the present disclosure;

[0186] Fig.19 is a flow chart illustrating an exemplary method for receiving user data at a wireless device implemented in a communication system including a host computer, a network node, and a wireless device according to some embodiments of the present disclosure;

[0187] Fig. 20 is a flow chart illustrating an exemplary method for receiving user data from a wireless device at a host computer implemented in a communication system including a host computer, a network node, and a wireless device according to some embodiments of the present disclosure;

[0188] Fig.21 is a flow chart illustrating an exemplary method for receiving user data at a host computer implemented in a communication system including a host computer, a network node, and a wireless device according to some embodiments of the present disclosure;

[0189] Fig. 22 is a flow chart of an exemplary process in a wireless device according to some embodiments of the present disclosure;

[0190] Fig.23is a flow chart of another exemplary process in a wireless device according to some embodiments of the present disclosure;

[0191] Fig.24 is a flow chart of an exemplary process in a network node according to some embodiments of the present disclosure;

[0192] Fig.25 is an example of RA method selection;

[0193] Fig.26 is a flow chart of a signal exchange that provides a fallback from a two-step random access attempt;

[0194] Fig. 27 is an alternative flow diagram of a signal exchange providing a backoff from a two-step random access attempt;

[0195] Fig.28 shows beam selection and reception of fallback RAR;

[0196] Fig.29 is an example of WD action when the WD retries a 2-step RA in a new beam when no RAR or RAR-like message is received; and

[0197] Fig.30 It is shown that no RAR is received after beam selection. DETAILED DESCRIPTION

[0198] Before describing the exemplary embodiments in detail, it is noted that the embodiments reside primarily in a combination of device components and processing steps related to two-step random access, such as recovery and fallback after an unsuccessful two-step random access attempt. Thus, components have been represented by conventional symbols where appropriate in the accompanying drawings, and only those specific details relevant to understanding the embodiments are shown so as not to obscure the present disclosure with details that will be readily apparent to those skilled in the art having the benefit of the description herein. Throughout this description, like numbers refer to like elements.

[0199] As used herein, relational terms such as "first" and "second", "top" and "bottom", etc., may be used solely to distinguish one entity or element from another entity or element, without necessarily requiring or implying any physical or logical relationship or order between such entities or elements. The terms used herein are for the purpose of describing specific embodiments only and are not intended to limit the concepts described herein. As used herein, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "comprise, comprising, include and / or including", when used herein, specify the presence of the described features, wholes, steps, operations, elements and / or components, but do not exclude the presence or addition of one or more other features, wholes, steps, operations, elements, components and / or groups thereof.

[0200] In the embodiments described herein, the connection terms "in communication with..." and the like may be used to indicate electrical communication or data communication, which may be achieved, for example, by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling, or optical signaling. Those skilled in the art will recognize that multiple components may interoperate, and modifications and variations in achieving electrical communication and data communication are possible.

[0201] In some embodiments described herein, the terms "coupled," "connected," and the like may be used herein to indicate a connection (although not necessarily a direct one), and may include wired and / or wireless connections.

[0202] The term "network node" used herein may be any kind of network node included in a radio network, which may further include any of the following items: a base station (BS), a radio base station, a base transceiver station (BTS), a base station controller (BSC), a radio network controller (RNC), a gNode B (gNB), an evolved Node B (eNB or eNodeB), a Node B, an MSR radio node such as a multi-standard radio (MSR) BS, a multi-cell / multicast coordination entity (MCE), an integrated access and backhaul (IAB) node, a relay node, an integrated access and backhaul (IAB) node, a donor node controlling a relay, a radio access point (AP), a transmission point, a transmission node, a remote radio unit (RRU) remote radio head (RRH), a core network node (e.g., a mobile management entity (MME), a self-organizing network (SON) node, a coordination node, a positioning node, an MDT node, etc.), an external node (e.g., a third-party node, a node outside the current network), a node in a distributed antenna system (DAS), a spectrum access system (SAS) node, an element management system (EMS), etc. The network node may also include a test device. As used herein, the term "radio node" may also be used to refer to a wireless device (WD), such as a wireless device (WD) or a radio network node.

[0203] As used herein in one or more embodiments, a "network" refers to a network node.

[0204] The non-limiting terms wireless device (WD) or user equipment (UE) are used interchangeably. The WD herein may be any type of wireless device capable of communicating with a network node or another WD via a radio signal, such as a wireless device (WD). The WD may also be a radio communication device, a target device, a device-to-device (D2D) WD, a machine-type WD, or a WD capable of machine-to-machine communication (M2M), a low-cost and / or low-complexity WD, a sensor equipped with a WD, a tablet, a mobile terminal, a smart phone, a laptop embedded device (LEE), a laptop mounted device (LME), a USB dongle, a customer premises equipment (CustomerPremisesEquipment) (CPE), an Internet of Things (IoT) device, or a narrowband IoT (NB-IOT) device, etc.

[0205] Furthermore, in some embodiments, the generic term "radio network node" is used. It may be any kind of radio network node, which may include any of the following: base station, radio base station, base transceiver station, base station controller, network controller, RNC, evolved Node B (eNB), Node B, gNB, multi-cell / multicast coordination entity (MCE), IAB node, relay node, access point, radio access point, remote radio unit (RRU), remote radio head (RRH).

[0206] Transmission in a downlink may involve transmission from a network or a network node to a terminal. Transmission in an uplink may involve transmission from a terminal to a network or a network node. Transmission in a sidelink may involve (direct) transmission from one terminal to another. Uplink, downlink and sidelink (e.g., sidelink transmission and reception) may be considered as communication directions. In some variants, uplink and downlink may also be used to describe wireless communications between network nodes, such as for wireless backhaul and / or relay communications and / or (wireless) network communications between, for example, base stations or similar network nodes, in particular communications terminated therein. It may be considered that backhaul and / or relay communications and / or network communications are implemented as sidelink or uplink communications or in the form of communications similar thereto.

[0207] Note that although terminology from one particular wireless system such as, for example, 3GPP LTE and / or New Radio (NR) may be used in this disclosure, this should not be seen as limiting the scope of the disclosure to only the aforementioned systems. Other wireless systems, including but not limited to Wideband Code Division Multiple Access (WCDMA), Worldwide Interoperability for Microwave Access (WiMax), Ultra Mobile Broadband (UMB), and Global System for Mobile Communications (GSM), may also benefit from applying the ideas covered in this disclosure.

[0208] Further note that the functions described herein as being performed by a wireless device or network node may be distributed across multiple wireless devices and / or network nodes. In other words, it is contemplated that the functions of the network nodes and wireless devices described herein are not limited to being performed by a single physical device and, in fact, may be distributed across several physical devices.

[0209] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by those of ordinary skill in the art to which the present disclosure belongs. It will be further understood that, unless expressly defined as such herein, the terms used herein should be interpreted as having a meaning consistent with their meaning in the context of the relevant art and this specification, and will not be interpreted in an idealized or overly formal sense.

[0210] Some embodiments include beam selection as one of the steps. In the context of some embodiments, a "beam" may be a reference signal detected by the WD and having an associated identifier. For example, if the embodiments are applied to the 3GPP NR standard, the reference signal may be either an SS block (SSB), i.e., a synchronization signal and a PBCH block, or a CSI-RS. When it is mentioned that the selected beam is mapped to a 2-step random access configuration, it means that the WD has performed measurements on the RS (which may be beamformed, like an SSB or CSI-RS resource), at least the beam was selected according to criteria, and the RS configuration may have a mapping to a 2-step random access configuration (e.g., in the configuration provided to the WD).

[0211] In the case of SSB, it consists of a primary synchronization signal (PSS) and a secondary synchronization signal (SSS), each occupying 1 symbol and 127 subcarriers, and the PBCH spans 3 OFDM symbols and 240 subcarriers, but leaves an unused portion in the middle for the SSS on one symbol, such as Figure 2 As shown in .

[0212] Referring again to the drawings, wherein like elements are referred to by like reference numerals, Fig.16 1 shows a schematic diagram of a communication system 10 according to an embodiment, such as a 3GPP type cellular network that can support standards such as LTE and / or NR (5G), which includes an access network 12 (such as a radio access network) and a core network 14. The access network 12 includes a plurality of network nodes 16a, 16b, 16c (collectively referred to as network nodes 16) (such as NBs, eNBs, gNBs or other types of wireless access points), each of which defines a corresponding coverage area 18a, 18b, 18c (collectively referred to as coverage area 18). Each network node 16a, 16b, 16c is connectable to the core network 14 via a wired or wireless connection 20. A first wireless device (WD) 22a located in the coverage area 18a is configured to be wirelessly connected to the corresponding network node 16c, or to be paged by the corresponding network node 16c. A second WD 22b in the coverage area 18b is wirelessly connectable to the corresponding network node 16a. Although multiple WDs 22a, 22b (collectively referred to as wireless devices 22) are shown in this example, the disclosed embodiments are equally applicable to situations where only a single WD is located in the coverage area or a single WD is connecting to a corresponding network node 16. Note that although only two WDs 22 and three network nodes 16 are shown for convenience, the communication system may include more WDs 22 and network nodes 16.

[0213] Furthermore, it is contemplated that the WD 22 may communicate with more than one network node 16 and more than one type of network node 16 simultaneously, and / or be configured to communicate with them alone. For example, the WD 22 may have dual connectivity with a network node 16 that supports LTE and the same or different network nodes 16 that support NR. As an example, the WD 22 may communicate with an eNB for LTE / E-UTRAN and a gNB for NR / NG-RAN.

[0214] The communication system 10 itself may be connected to a host computer 24, which may be embodied in hardware and / or software as a stand-alone server, a cloud-implemented server, a distributed server, or as processing resources in a server farm. The host computer 24 may be under the ownership or control of a service provider, or may be operated by or on behalf of the service provider. The connections 26, 28 between the communication system 10 and the host computer 24 may extend directly from the core network 14 to the host computer 24, or may extend via an optional intermediate network 30. The intermediate network 30 may be a public network, a private network, or a combination of one or more of a managed network. The intermediate network 30, if any, may be a backbone network or the Internet. In some embodiments, the intermediate network 30 may include two or more subnetworks (not shown).

[0215] Fig.16 The communication system as a whole can realize the connectivity between one of the connected WD 22a, 22b and the host computer 24. This connectivity can be described as an over-the-top (OTT) connection. The host computer 24 and the connected WD 22a, 22b are configured to use the access network 12, the core network 14, any intermediate network 30 and possible additional infrastructure (not shown) as intermediaries to transfer data and / or signaling via the OTT connection. The OTT connection can be transparent in the sense that at least some of the participating communication devices through which the OTT connection passes do not know the routes of the uplink and downlink communications. For example, the past routes of the incoming downlink communications may not or need not be notified to the network node 16, and the downlink communications have data to be forwarded (e.g., handed over) to the connected WD 22a originating from the host computer 24. Similarly, the network node 16 does not need to know the future routes of the outgoing uplink communications originating from the WD 22a toward the host computer 24.

[0216] The network node 16 is configured to include a configuration unit 33 configured to perform one or more network node 16 functions described herein, such as with respect to a random access procedure. The wireless device 22 is configured to include a random access unit 34 configured to perform one or more wireless device 22 functions described herein, such as with respect to a two-step random access procedure.

[0217] According to the embodiment, reference will now be made to Fig.17 An example implementation of the WD 22, network node 16, and host computer 24 discussed in the previous paragraphs is described. In the communication system 10, the host computer 24 includes hardware (HW) 38, which includes a communication interface 40, which is configured to establish and maintain a wired or wireless connection for the interface with different communication devices of the communication system 10. The host computer 24 further includes a processing circuit 42, which may have storage and / or processing capabilities. The processing circuit 42 may include a processor 44 and a memory 46. In particular, in addition to or in place of a processor and a memory such as a central processing unit, the processing circuit 42 may also include an integrated circuit for processing and / or control, for example, one or more processors and / or processor cores and / or FPGAs (field programmable gate arrays) and / or ASICs (application-specific integrated circuits) suitable for executing instructions. The processor 44 may be configured to access (e.g., write to and / or read from) a memory 46, which may include any type of volatile and / or non-volatile memory, such as cache and / or buffer memory and / or RAM (random access memory) and / or ROM (read only memory) and / or optical memory and / or EPROM (erasable programmable read-only memory).

[0218] Processing circuit 42 may be configured to control any of the methods and / or processes described herein, and / or to cause such methods and / or processes to be performed, for example, by host computer 24. Processor 44 corresponds to one or more processors 44 for performing the functions of host computer 24 described herein. Host computer 24 includes memory 46, which is configured to store data, programmatic software code, and / or other information described herein. In some embodiments, software 48 and / or host application 50 may include instructions that, when executed by processor 44 and / or processing circuit 42, cause processor 44 and / or processing circuit 42 to perform the processes described herein with respect to host computer 24. The instructions may be software associated with host computer 24.

[0219] The software 48 can be executed by the processing circuit 42. The software 48 includes a host application 50. The host application 50 is operable to provide services to a remote user (such as a WD 22 connected via an OTT connection 52 terminated at the WD 22 and the host computer 24). When providing services to the remote user, the host application 50 can provide user data transmitted using the OTT connection 52. "User data" can be data and information described herein as implementing the functionality. In one embodiment, the host computer 24 can be configured to provide control and functionality to a service provider, and can be operated by or on behalf of the service provider. The processing circuit 42 of the host computer 24 can enable the host computer 24 to observe, monitor, control the network node 16 and / or the wireless device 22 and transmit and / or receive to and from the network node 16 and / or the wireless device 22.

[0220] The communication system 10 further includes a network node 16, which is arranged in the communication system 10 and includes hardware 58, which enables it to communicate with the host computer 24 and the WD 22. The hardware 58 may include a communication interface 60 for establishing and maintaining a wired or wireless connection to the interface of different communication devices of the communication system 10, and a radio interface 62 for establishing and maintaining a wireless connection 64 with the WD 22 located in the coverage area 18 served by the network node 16. The radio interface 62 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers. The communication interface 60 may be configured to facilitate a connection 66 to the host computer 24. The connection 66 may be direct, or it may pass through the core network 14 of the communication system 10 and / or through one or more intermediate networks 30 external to the communication system 10.

[0221] In the illustrated embodiment, the hardware 58 of the network node 16 further includes a processing circuit 68. The processing circuit 68 may include a processor 70 and a memory 72. In particular, in addition to or in place of a processor such as a central processing unit and a memory, the processing circuit 68 may also include an integrated circuit for processing and / or control, for example, one or more processors and / or processor cores and / or an FPGA (field programmable gate array) and / or an ASIC (application-specific integrated circuit) adapted to execute instructions. The processor 70 may be configured to access the memory 72 (e.g., write to the memory 72 and / or read from the memory 72), and the memory 72 may include any type of volatile and / or non-volatile memory, such as a cache and / or buffer memory and / or a RAM (random access memory) and / or a ROM (read-only memory) and / or an optical memory and / or an EPROM (erasable programmable read-only memory).

[0222] Therefore, the network node 16 further has software 74, which is stored internally, for example, in the memory 72, or stored in an external memory (e.g., a database, a storage array, a network storage device, etc.) accessible by the network node 16 via an external connection. The software 74 can be executed by the processing circuit 68. The processing circuit 68 can be configured to control any of the methods and / or processes described herein, and / or cause such methods and / or processes to be performed, for example, by the network node 16. The processor 70 corresponds to one or more processors 70 for performing the network node 16 functions described herein. The memory 72 is configured to store data, programmed software code, and / or other information described herein. In some embodiments, the software 74 may include instructions that, when executed by the processor 70 and / or the processing circuit 68, cause the processor 70 and / or the processing circuit 68 to perform the processes described herein with respect to the network node 16. The processing circuit 68 may include a configuration unit 33, which is configured to perform one or more network node 16 functions described herein, such as with respect to the random access process.

[0223] The communication system 10 further includes the already mentioned WD 22. The WD 22 may have hardware 80, which may include a radio interface 82 configured to establish and maintain a wireless connection 64 with a network node 16 serving the coverage area 18 in which the WD 22 is currently located. The radio interface 82 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers.

[0224] The hardware 80 of the WD 22 further includes a processing circuit 84. The processing circuit 84 may include a processor 86 and a memory 88. In particular, in addition to or in place of a processor such as a central processing unit and a memory, the processing circuit 84 may include an integrated circuit for processing and / or control, such as one or more processors and / or processor cores and / or an FPGA (field programmable gate array) and / or an ASIC (application-specific integrated circuit) adapted to execute instructions. The processor 86 may be configured to access the memory 88 (e.g., write to the memory 88 and / or read from the memory 88), and the memory 88 may include any kind of volatile and / or non-volatile memory, such as a cache and / or buffer memory and / or a RAM (random access memory) and / or a ROM (read-only memory) and / or an optical memory and / or an EPROM (erasable programmable read-only memory).

[0225] Therefore, WD 22 may further include software 90 stored in, for example, a memory 88 at WD 22 or stored in an external memory (e.g., a database, a storage array, a network storage device, etc.) accessible by WD 22. The software 90 may be executed by the processing circuit 84. The software 90 may include a client application 92. The client application 92 may operate to provide services to a human or non-human user via WD 22 with the support of the host computer 24. In the host computer 24, the executed host application 50 may communicate with the executed client application 92 via the OTT connection 52 terminated at WD 22 and the host computer 24. When providing services to the user, the client application 92 may receive request data from the host application 50 and provide user data in response to the request data. The OTT connection 52 may transmit request data and user data. The client application 92 may interact with the user to generate the user data it provides.

[0226] The processing circuit 84 may be configured to control any method and / or process described herein, and / or cause such method and / or process to be performed, for example, by the WD 22. The processor 86 corresponds to one or more processors 86 for performing the WD 22 functions described herein. The WD 22 includes a memory 88, which is configured to store data, programmed software code, and / or other information described herein. In some embodiments, the software 90 and / or the client application 92 may include instructions that, when executed by the processor 86 and / or the processing circuit 84, cause the processor 86 and / or the processing circuit 86 to perform the process described herein with respect to the WD 22. For example, the processing circuit 84 of the wireless device 22 may include a random access unit 34 that is configured to perform one or more wireless device 22 functions described herein, such as with respect to the two-step random access process.

[0227] In some embodiments, the internal workings of network node 16, WD 22, and host computer 24 may be as follows: Fig.17 As shown in , and independently, the surrounding network topology can be Fig.16 network topology.

[0228] exist Fig.17 , the OTT connection 52 has been abstractly drawn to illustrate communications between the host computer 24 and the wireless device 22 via the network node 16, without explicit reference to any intermediary devices and the precise routing of messages via these devices. The network infrastructure may determine the routing, which may be configured to be hidden from the WD 22 or the service provider operating the host computer 24, or both. When the OTT connection 52 is active, the network infrastructure may further make decisions by which it dynamically changes the routing (e.g., based on reconfiguration of the network or load balancing considerations).

[0229] The wireless connection 64 between the WD 22 and the network node 16 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improves the performance of the OTT service provided to the WD 22 using the OTT connection 52, where the wireless connection 64 may form the last leg. More specifically, the teachings of some of these embodiments may improve data rates, latency, and / or power consumption, and thereby provide benefits such as reduced user waiting time, relaxed restrictions on file size, better responsiveness, extended battery life, and the like.

[0230] In some embodiments, a measurement process may be provided for the purpose of monitoring the data rate, latency, and other factors improved by one or more embodiments. There may further be optional network functionality for reconfiguring the OTT connection 52 between the host computer 24 and the WD 22 in response to changes in the measurement results. The measurement process and / or network functionality for reconfiguring the OTT connection 52 may be implemented with the software 48 of the host computer 24, or with the software 90 of the WD 22, or with both. In an embodiment, a sensor (not shown) may be deployed in or associated with a communication device through which the OTT connection 52 passes; the sensor may participate in the measurement process by supplying the values ​​of the monitored quantities exemplified above, or supplying the values ​​of other physical quantities from which the software 48, 90 can calculate or estimate the monitored quantities. The reconfiguration of the OTT connection 52 may include message formats, retransmission settings, preferred routes, etc.; the reconfiguration does not need to affect the network node 16, and it may be unknown or imperceptible to the network node 16. Some such processes and functionalities may be known and practiced in the art. In some embodiments, the measurements may involve proprietary WD signaling that facilitates the host computer 24's measurement of throughput, propagation time, latency, etc. In some embodiments, the measurements may be achieved because the software 48, 90 uses the OTT connection 52 to cause messages (particularly empty or 'dummy' messages) to be transmitted while it monitors propagation time, errors, etc.

[0231] Thus, in some embodiments, the host computer 24 includes processing circuitry 42 configured to provide user data and a communication interface 40 configured to forward the user data to a cellular network for transmission to the WD 22. In some embodiments, the cellular network also includes a network node 16 having a radio interface 62. In some embodiments, the network node 16 is configured and / or the processing circuitry 68 of the network node 16 is configured to perform the functions and / or methods described herein for preparing / initiating / maintaining / supporting / ending transmissions to the WD 22 and / or preparing / terminating / maintaining / supporting / ending reception of transmissions from the WD 22.

[0232] In some embodiments, host computer 24 includes processing circuitry 42 and communication interface 40 configured to receive user data originating from transmissions from WD 22 to network node 16. In some embodiments, WD 22 is configured to and / or includes a radio interface 82 and / or processing circuitry 84 configured to perform the functions and / or methods described herein for preparing / initiating / maintaining / supporting / ending transmissions to network node 16 and / or preparing / terminating / maintaining / supporting / ending reception of transmissions from network node 16.

[0233] although Fig.16 and Fig.17 Various "units" such as random access unit 34 and configuration unit 33 are shown as being within a corresponding processor, but it is contemplated that these units may be implemented such that a portion of the unit is stored in a corresponding memory within the processing circuit. In other words, these units may be implemented within the processing circuit in hardware or a combination of hardware and software.

[0234] Fig.18 is a diagram showing a communication system (such as, for example, Fig.16 and Figure 7 24, a network node 16, and a WD 22, which may be reference Fig.16 Those host computers, network nodes, and WDs described herein. In a first step of the method, host computer 24 provides user data (box S100). In an optional sub-step of the first step, host computer 24 provides user data by executing a host application (such as, for example, host application 50) (box S102). In a second step, host computer 24 initiates a transmission to WD 22 carrying user data (box S104). In an optional third step, in accordance with the teachings of the embodiments described throughout this disclosure, network node 16 transmits user data carried in the transmission initiated by host computer 24 to WD 22 (box S106). In an optional fourth step, WD 22 executes a client application (such as, for example, client application 92) associated with the host application 50 executed by host computer 24 (box S108).

[0235] Fig.19 is a diagram showing a communication system (such as, for example, Fig.16 24, a network node 16, and a WD 22, which may be reference Fig.16 and Fig.171 and 2. In the first step of the method, host computer 24 provides user data (block S110). In an optional substep (not shown), host computer 24 provides user data by executing a host application (such as, for example, host application 50). In a second step, host computer 24 initiates a transmission to WD 22 carrying user data (block S112). According to the teachings of the embodiments described throughout this disclosure, the transmission can be transmitted via network node 16. In an optional third step, WD 22 receives the user data carried in the transmission (block S114).

[0236] Fig. 20 is a diagram showing a communication system (such as, for example, Fig.16 24, a network node 16, and a WD 22, which may be reference Fig.16 and Fig.17 Those host computers, network nodes and WDs described herein. In the optional first step of the method, WD 22 receives input data provided by host computer 24 (box S116). In the optional sub-step of the first step, WD 22 executes client application 92, which provides user data (box S118) as a reaction to the received input data provided by host computer 24. Additionally or alternatively, in the optional second step, WD 22 provides user data (box S120). In the optional sub-step of the second step, WD provides user data (box S122) by executing a client application (such as, for example, client application 92). When providing user data, the executed client application 92 may further consider user input received from the user. Regardless of the specific manner in which the user data is provided, in the optional third sub-step, WD 22 may initiate the transmission of user data to host computer 24 (box S124). In the fourth step of the method, according to the teachings of the embodiments described throughout the present disclosure, host computer 24 receives user data transmitted from WD 22 (box S126).

[0237] Fig.21 is a diagram showing a communication system (such as, for example, Fig.16 The communication system may include a host computer 24, a network node 16, and a WD 22, which may be a reference Fig.16 and Fig.17In an optional first step of the method, network node 16 receives user data from WD 22 in accordance with the teachings of the embodiments described throughout this disclosure (block S128). In an optional second step, network node 16 initiates transmission of the received user data to host computer 24 (block S130). In a third step, host computer 24 receives user data carried in the transmission initiated by network node 16 (block S132).

[0238] Fig. 22 is a flow chart of an exemplary process in the wireless device 22 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of the wireless device 22, such as by one or more of the processing circuit 84 (including the random access unit 34), the processor 86, the radio interface 82, and / or the communication interface 60. The wireless device 22 is configured to detect whether the attempt to perform two-step random access is successful (block S134), such as via the processing circuit 84 and / or the processor 86 and / or the radio interface 82. If yes, the process continues. If the attempt to perform two-step random access is unsuccessful, the WD 22 performs at least one of the following: retrying the two-step random access attempt and performing a four-step random access process (block S136).

[0239] Fig.23 is a flowchart of another exemplary process in the wireless device 22 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of the wireless device 22, such as by one or more of the processing circuit 84 (including the random access unit 34), the processor 86, the radio interface 82, and / or the communication interface 60. The wireless device 22 is configured to trigger a random access (RA) process, such as via the processing circuit 84 and / or the processor 86 and / or the radio interface 82, as described herein (block S138). The wireless device 22 is configured to select a first beam for the RA process, such as via the processing circuit 84 and / or the processor 86 and / or the radio interface 82, wherein the selected first beam is associated with a two-step RA configuration, and the characteristics of the selected first beam are determined to meet a predefined threshold, as described herein (block S140). The wireless device 22 is configured to perform a RA process associated with the two-step RA configuration using the selected first beam, such as via the processing circuit 84 and / or the processor 86 and / or the radio interface 82, as described herein (block S142).

[0240] According to one or more embodiments, the processing circuit 84 is further configured to: receive system information; and determine, based at least on the system information, whether the selected first beam is associated with a two-step RA configuration, the two-step RA configuration corresponding to a mapping of the selected first beam to a physical uplink shared channel PUSCH configuration. According to one or more embodiments, the selected first beam is selected from a plurality of beams, wherein a subset of the plurality of beams is associated with the two-step RA configuration. According to one or more embodiments, the subset of the plurality of beams is one of: a subset of a synchronization signal block SSB beam and a set of a channel state information reference signal CSI-RS beam.

[0241] According to one or more embodiments, a subset of the SSB beams is associated with a contention-free RA resource. According to one or more embodiments, at least one other beam in the plurality of beams is not associated with a two-step RA configuration. According to one or more embodiments, at least one of the subset of beams is associated with a contention-based RA, wherein contention-free RA takes precedence over contention-based RA. According to one or more embodiments, the characteristic of the selected first beam is a channel quality, and the predefined threshold is a channel quality threshold.

[0242] According to one or more embodiments, the processing circuit 84 is further configured to: determine that a step of the two-step RA procedure has failed; and in response to determining that a step of the two-step RA procedure has failed, perform one of the following: retransmit the uplink shared channel portion of message A msgA as an uplink shared channel message in a four-step RA procedure; and retry the two-step RA procedure at least in part by performing beam reselection. According to one or more embodiments, the processing circuit 84 is further configured to determine that a step of the two-step RA procedure has failed based on one of the following: lack of a response to msgA; receiving a random access response RAR message including backoff information; and receiving a message B msgB including first information indicating that a step of the two-step RA procedure has failed. According to one or more embodiments, the backoff information includes an indication that a step of the two-step RA procedure has failed.

[0243] According to one or more embodiments, the first information is contention resolution information. According to one or more embodiments, retransmission is performed based on reselecting a beam from a plurality of beams, wherein the reselection includes using a contention-free RA resource configured for one of a channel state information reference signal CSI-RS and a synchronization signal block SSB.

[0244] Fig.241 is a flow chart of an exemplary process in the network node 16 according to some embodiments of the present disclosure. One or more blocks and / or functions performed by the network node 16 may be performed by one or more elements of the network node 16, such as by the configuration unit 33 in the processing circuit 68, the processor 70, the radio interface 62, etc. In one or more embodiments, the network node 16 is configured, such as via one or more of the processing circuit 68, the processor 70, the configuration unit 33, the communication interface 60, and the radio interface 62, to associate multiple beams with multiple random access RA configurations, wherein a first beam of the multiple beams is associated with a two-step RA configuration, as described herein (block S144). In one or more embodiments, the network node 16 is configured, such as via one or more of the processing circuit 68, the processor 70, the configuration unit 33, the communication interface 60, and the radio interface 62, to perform a RA process using the first beam based on the two-step RA configuration associated with the first beam, as described herein (block S146).

[0245] According to one or more embodiments, the processing circuit 68 is further configured to transmit system information, wherein the system information indicates a plurality of RA configurations. According to one or more embodiments, a subset of the plurality of beams is associated with the two-step RA configuration. According to one or more embodiments, the subset of the plurality of beams is one of: a subset of synchronization signal block SSB beams and a set of channel state information reference signal CSI-RS beams.

[0246] According to one or more embodiments, a subset of the SSB beams is associated with contention-free RA resources for contention-free RA. According to one or more embodiments, at least one of the subset of beams is associated with contention-based RA, and contention-free RA takes precedence over contention-based RA. According to one or more embodiments, at least one other beam in the plurality of beams is not associated with a two-step RA configuration.

[0247] According to one or more embodiments, the processing circuit 68 is further configured to one of: receive the transmitted uplink shared channel portion of the message A msgA as an uplink shared channel message in the four-step RA procedure; and determine that a beam reselection has occurred, the beam selection being associated with a retry of performing the two-step RA procedure. According to one or more embodiments, the processing circuit 68 is further configured to: determine that the two-step RA procedure has failed; and in response to the determination that the two-step RA procedure has failed, perform one of the following: transmit a random access response RAR message including backoff information; and transmit a message B msgB including first information indicating that a step of the two-step RA procedure has failed. According to one or more embodiments, the backoff information includes an indication that a step of the two-step RA procedure has failed. According to one or more embodiments, the first information is contention resolution information.

[0248] Having described the general process flow of the arrangements of the present disclosure, and having provided examples of hardware and software arrangements for implementing the processes and functions of the present disclosure, the following section provides details and examples of arrangements for recovery and fallback after an unsuccessful two-step random access attempt.

[0249] The possible time positions of the SSB within the half frame are determined by the subcarrier spacing, and the periodicity of the half frame in which the SSB is transmitted is configured by the network node 16. During the half frame, different SSBs may be transmitted in different spatial directions (i.e., using different beams, across the coverage area of ​​the cell). Within the frequency span of the carrier, multiple SSBs may be transmitted, such as via one or more of the processing circuit 68, the processor 70, the radio interface 62, the configuration unit 33, etc. The PCI of SSBs transmitted at different frequency positions does not have to be unique, i.e., different SSBs in the frequency domain may have different PCIs. However, when an SSB is associated with an RMSI, the SSB corresponds to a single cell having a unique NR cell global identifier (NCGI). Such an SSB is referred to as a cell-defined SSB (CD-SSB). A PCell may always be associated with a CD-SSB located on a synchronization grid.

[0250] The term "beam measurement" for beam selection may include the measured radio conditions (e.g., RSRP, RSRQ, or SINR) of one or more beams. Layer 1 (layers herein refer to open system interconnection (OSI) layers) may receive a set of SS / PBCH block indices (or CSI-RS) from higher layers and provide a corresponding set of RSRP, RSRQ, and / or SINR measurements to the higher layers. These may be referred to as L1 measurements per SSB, L1 measurements per CSI-RS, or L1 measurements per beam.

[0251] These measurements may be performed according to an embodiment described as those measurements that may be described in the L1 specification, reproduced as follows (for simplicity, only RRSP definitions are provided for CSI-RS and SSB):

[0252] SS reference signal received power (SS-RSRP);

[0253] a) SS Reference Signal Received Power (SS-RSRP) is defined as the linear average of the power contributions of resource elements carrying secondary synchronization signals. The measurement time resource(s) for SS-RSRP are limited to the SS / PBCH Block Measurement Time Configuration (SMTC) window duration. If SS-RSRP is used for L1-RSRP as configured by a reporting configuration defined in one or more wireless communication standards such as 3GPP TS 38.214, the measurement time resource restriction(s) of the SMTC window duration is not applicable.

[0254] b) For SS-RSRP determination, the demodulation reference signal of the physical broadcast channel (PBCH) may be used and, if indicated by higher layers, the CSI reference signal may be used in addition to the secondary synchronization signal. SS-RSRP using the demodulation reference signal or the CSI reference signal for the PBCH may be measured by linearly averaging the power contribution of the resource elements carrying the corresponding reference signal taking into account the power scaling of the reference signal, as defined in wireless communication standards such as 3GPP TS38.213. If SS-RSRP is not used for L1-RSRP, the additional use of the CSI reference signal for SS-RSRP determination is not applicable.

[0255] c) SS-RSRP may be measured only among reference signals corresponding to SS / PBCH blocks having the same SS / PBCH block index and the same physical layer cell identity.

[0256] d) If SS-RSRP is not used for L1-RSRP, and higher layers indicate certain SS / PBCH blocks to be used for performing SS-RSRP measurements, then SS-RSRP is measured only from the indicated set of (one or more) SS / PBCH blocks.

[0257] e) For frequency range 1, the reference point for SS-RSRP may be the antenna connector of WD 22. For frequency range 2, SS-RSRP may be measured based on the combined signals from the antenna elements corresponding to a given receiver branch. For frequency ranges 1 and 2, if WD 22 is using receiver diversity, the reported SS-RSRP value may not be lower than the corresponding SS-RSRP of any of the receiver branches of WD 22.

[0258] f) NOTE 1: The number of resource elements within a measurement period used by WD 22 to determine SS-RSRP depends on the WD implementation, with the restriction that the corresponding measurement accuracy requirement can be met.

[0259] g) NOTE 2: The power per resource element is determined based on the energy received during the useful portion of the symbol excluding the cyclic prefix (CP), such as via one or more of the processing circuit 84, the processor 86, the radio interface 82, the random access unit 34, etc.

[0260] Channel state information (CSI) reference signal received power (CSI-RSRP);

[0261] a) The CSI reference signal received power (CSI-RSRP) is defined as the linear average over the power contributions of the resource elements of the antenna port(s) carrying the CSI reference signal configured for RSRP measurement within the considered measurement frequency bandwidth in the configured CSI-RS occasions.

[0262] b) For CSI-RSRP determination, a CSI reference signal transmitted on antenna port 3000 according to one or more wireless communication standards (such as 3GPP TS38.211) may be used. If CSI-RSRP is used for L1-RSRP, the CSI reference signal transmitted on antenna ports 3000, 3001 may be used for CSI-RSRP determination.

[0263] c) For intra-frequency CSI-RSRP measurements, if no measurement gaps are configured, the WD 22 is not expected to measure CSI-RS resource(s) outside the active downlink bandwidth portion.

[0264] d) For frequency range 1, the reference point for CSI-RSRP may be the antenna connector of WD 22. For frequency range 2, CSI-RSRP may be measured based on the combined signals from the antenna elements corresponding to a given receiver branch. For frequency ranges 1 and 2, if WD 22 is using receiver diversity, such as via one or more of processing circuitry 84, processor 86, radio interface 82, random access unit 34, etc., the reported CSI-RSRP value may not be lower than the corresponding CSI-RSRP of any of the receiver branches.

[0265] e) NOTE 1: The number of resource elements within the measurement frequency bandwidth and measurement period considered for determining CSI-RSRP by WD 22 depends on the WD implementation, with the restriction that the corresponding measurement accuracy requirement should be met.

[0266] Some embodiments include a method for performing random access at a wireless device (an example of which is a user equipment) that involves unsuccessful (one or more) random access procedure attempts followed by a fallback action or other reaction to the detected unsuccessful. Some aspects include steps performed by the WD 22 upon detecting a random access failure in conjunction with a 2-step RA attempt. Prior to reaching this point, the WD 22 performs several initial steps involved in preparing for and initiating the random access process. The following are these initial steps performed by the WD 22, such as via one or more of the processing circuit 84, the processor 86, the radio interface 82, the random access unit 34, etc.:

[0267] Obtain (one or more) random access configurations for a cell (e.g., a serving cell or a target cell (e.g., in conjunction with a handover or SCG change / addition) on which WD 22 is camping (in RRC_IDLE or RRC_INACTIVE state)), including a 2-step random access (RA) configuration for each beam or beam group in the cell (where a group of beams may constitute a subset of the beams in the cell). In other words, at least one beam may have an associated 2-step RA configuration (but not necessarily all beams of the target cell may be associated with a 2-step RA configuration), or in other words, alternatively, at least one beam will not have an associated 2-step RA configuration. In this context, a beam refers to an SSB beam or a CSI-RS beam. Both signal types may be beam references (i.e., act as a "template") and may have associated (one or more) random access configurations.

[0268] a) The above configuration may be provided during configuration of handover, dual connectivity procedures (eg, SCG addition, SCG change), carrier aggregation procedures (eg, SCell establishment, Scell ​​addition, Scell ​​activation, etc.).

[0269] b) The above configuration may be provided for beam failure recovery procedure, where only a subset of the beams of the target cell are provided to WD 22 as a beam candidate list, currently defined in RRC as the field candidateBeamRSList. In this sense, if the network only wants to support 2-step RA for CBRA for beam failure recovery (BFR), only the beams in this list may be configured with 2-step RA.

[0270] c) The above configuration may be provided in the system information provided by the network node 16, wherein when the WD camps on a cell, the WD 22 obtains the SI and may access the cell, such as via one or more of the processing circuit 84, processor 86, radio interface 82, random access unit 34, etc.

[0271] d) Configurations such as one or more 2-step RA configurations may be mapped per beam, such as directly or indirectly by the network node 16. For example, there may be a relationship between a selected beam and a PRACH configuration, and then a relationship between a PRACH configuration and a 2-step RA configuration.

[0272] e) Configurations such as one or more 2-step RA configurations may be provided by the network node 16 per RS ​​type, i.e., there may be a 2-step RA configuration associated with each of a set or subset of SSBs and / or a 2-step RA configuration associated with each of a set or subset of CSI-RS.

[0273] f) The manner in which the (possibly beam-dependent) 2-step RA configuration is encoded in RRC (ASN.1), such as via one or more of the processing circuit 68, the processor 70, the radio interface 62, the configuration unit 33, etc., may be different, and in different solutions the WD 22 obtains the 2-step RA configuration (e.g., mapping to PUSCH resources) in different information elements (Ie).

[0274] i) In one alternative, WD 22 obtains the 2-step RA configuration as part of IE RACH-ConfigCommon, such as via one or more of processing circuitry 84, processor 86, radio interface 82, random access unit 34, etc.

[0275] ii) In an alternative, WD 22 obtains the 2-step RA configuration as part of the IE RACH-ConfigDedicated, such as via one or more of processing circuitry 84, processor 86, radio interface 82, random access unit 34, etc.

[0276] iii) In one alternative, WD 22 obtains the 2-step RA configuration as part of IE RACH-ConfigGeneric, such as via one or more of processing circuitry 84, processor 86, radio interface 82, random access unit 34, etc.

[0277] iv) In an alternative, the WD 22 obtains the 2-step RA configuration in different IEs, such as via one or more of the processing circuit 84, the processor 86, the radio interface 82, the random access unit 34, etc., where different parameters are provided in each of them, for example as part of the IEs RACH-ConfigGeneric and RACH-ConfigCommon, and it is possible to include a new IE to clearly distinguish what is a 2-step RA configuration or a 4-step RA configuration.

[0278] v) In an alternative, WD 22 obtains the 2-step RA configuration in a new IE different from the above IE.

[0279] One aspect of the 2-step RA configuration is how the selected beam (e.g., SSB-x) is mapped to the PRACH resources and PUSCH resources (i.e., PRACH preamble + MsgAPUSCH) for MsgA transmission. In the 4-step RACH configuration in the RRC specification, the PRACH configuration index (prach-ConfigurationIndex) defines what time domain and frequency domain resources are used for PRACH transmission. In an alternative, the PUSCH resource configuration may also be present and may be encoded by an index in the RRC pointing to a hard decoding table (e.g., in the L1 specification).

[0280] • Such as triggering a random access at WD 22 (eg, upon request from upper layers).

[0281] a) Triggering random access can be done in different ways. For example, when RRC submits a message to the lower layer and reaches the MAC layer towards the target cell with which the WD 22 is not synchronized, such as when the WD 22 receives a handover and a handover complete message should be sent in the target cell.

[0282] b) Random access may be triggered by any other process that relies on random access, such as detection of beam failure recovery, where the WD 22 detects a beam failure, such as via one or more of the processing circuit 84, the processor 86, the radio interface 82, the random access unit 34, etc., and should select a beam from a list of candidate beams, each of which may have a 2-step RA configuration.

[0283] c) Another situation that may trigger random access is when uplink (UL) data appears in WD 22 (e.g., created by an application in WD 22). This will trigger random access if WD 22 is in RRC_IDLE or RRC_INACTIVE state and WD 22 should transition to RRC_CONNECTED state before WD 22 can transmit pending UL data. Pending UL data in WD 22 in RRC_CONNECTED state may also trigger random access if WD 22 lacks a valid timing advance and a valid timing advance should be acquired before WD 22 can transmit pending UL data.

[0284] d) Yet another case where a random access is triggered is if the WD 22 is paged and should transition to the RRC_CONNECTED state in response to the paging.

[0285] e) Another case of triggering random access is if WD 22 receives a PDCCH command to perform random access to acquire a valid timing advance. This may occur if the network node 16 receives DL data for WD 22 in the RRC_CONNECTED state that lacks a valid timing advance. The network node 16 may then command WD 22 to acquire a valid timing advance before the DL data is transmitted to WD 22 so that WD 22 can transmit HARQ feedback in the UL.

[0286] Performing beam selection

[0287] a) Beam selection may be, for example, SSB selection based on radio conditions, where the WD 22 selects the SSB with the highest RSRP among the detected SSBs of the serving cell or target cell, such as via one or more of the processing circuit 84, the processor 86, the radio interface 82, the random access unit 34, etc. The cell in which the WD 22 performs SSB selection may be the serving cell during the transition from the RRC_IDLE or RRC_INACTIVE state to the RRC_CONNECTED state or when the WD 22 in the RRC_CONNECTED state reacquires a valid timing advance, or the cell may be a target cell in conjunction with handover, or a potential target cell. In conjunction with handover, beam selection may consist of selection of a CSI-RS beam in the target cell, such as via one or more of the processing circuit 84, the processor 86, the radio interface 82, the random access unit 34, etc.

[0288] b) Beam selection may be equivalent to the so-called “random access resource selection” in the MAC specification, where the selected beam (e.g. the selected SSB) is mapped to the resources for transmitting the preamble (and in case of 2-step RA, also to the resources for transmitting MsgA on PUSCH). PUSCH resources).

[0289] -Determine whether the selected beam (e.g., the selected SSB) has an associated 2-step RACH configuration.

[0290] c) This step may be implemented by WD 22 checking the existence of a random access configuration for the selected SSB or CSI-RS, such as via one or more of the processing circuit 84, the processor 86, the radio interface 82, the random access unit 34, etc., i.e., the existence of a 2-step random access configuration indicates that there is a mapping between the selected beam (e.g., SSB) and the 2-step random access configuration.

[0291] d) The 2-step RA configuration in this context may include the selected beam and PUSCH configuration (i.e., for transmitting MsgA PUSCH Mapping between indication of PUSCH transmission resources).

[0292] e) The 2-step RA configuration in this context may include the PRACH configuration associated with the selected beam and (for transmitting MsgA PUSCH Compared with the above case, this is an indirect mapping via PRACH mapping.

[0293] f) The 2-step RA configuration in this context may include the PRACH configuration associated with the selected beam and (for transmitting MsgA PUSCH) PUSCH configurations, which includes a mapping for URLLC data mapped to a logical channel (LCH) that satisfies MsgA PUSCH LCH mapping for reliability (e.g. MCS, PUSCH duration, etc.).

[0294] If the selected beam (e.g., the selected SSB) has an associated 2-step RACH configuration, the WD 22 initiates a 2-step RA procedure using the mapped configuration, such as via one or more of the processing circuitry 84, processor 86, radio interface 82, random access unit 34, etc. Fig.25 is an illustration of a RA configuration associated and / or mapped to one or more beams. A configuration in this context may include a mapping between a selected beam and a Physical Uplink Shared Channel (PUSCH) configuration (for transmission of MsgAPUSCH).

[0295] g) In some embodiments, the above conditions may be necessary conditions, but according to embodiments, the method may also include further conditions to be tested before the WD 22 initiates the 2-step RA process for the selected beam, such as the radio channel quality condition (e.g., RSRP, RSRQ and / or SINR) of the selected beam (e.g., the selected SSB or CSI-RS) is higher than at least one threshold value determined by the WD 22, such as via one or more of the processing circuit 84, the processor 86, the radio interface 82, the random access unit 34, etc. As an example, if resources are configured and the channel quality is higher than a configured or standardized threshold, the WD 22 may initiate a 2-step RA, but if on the contrary the channel quality is lower than the threshold, a 4-step RA is initiated.

[0296] Otherwise, if the selected beam (e.g., the selected SSB or CSI-RS) does not have an associated 2-step RACH configuration, the WD 22, such as via one or more of the processing circuit 84, the processor 86, the radio interface 82, the random access unit 34, etc., may select an alternative way to access the network. Such alternative ways and the actions involved are described in detail herein. For example, the WD 22, such as via one or more of the processing circuit 84, the processor 86, the radio interface 82, the random access unit 34, etc., may initiate a 4-step RA process using a 4-step RA configuration mapped to the same beam.

[0297] At this point, the WD 22, such as via one or more of the processing circuitry 84, the processor 86, the radio interface 82, the random access unit 34, etc., may detect that the attempt to end the initiated random access procedure was unsuccessful, and this is where the WD 22, such as via one or more of the processing circuitry 84, the processor 86, the radio interface 82, the random access unit 34, etc., performs method steps (which include detecting an unsuccessful random access attempt and actions triggered by the detection):

[0298] - Detection that the initiated 2-step random access procedure was unsuccessful. This may include:

[0299] a) Receiving a RAR message or RAR-like message in response to a MsgA transmission, such as via one or more of the processing circuitry 84, the processor 86, the radio interface 82, the random access unit 34, etc. This is a robust preamble transmission that was successful, but a less robust MsgA on the PUSCH PUSCH Transmission (ie, MsgA PUSCH An indication that a transmission was unsuccessful.

[0300] b) No response (eg, after a timer or response window expires) in response to the MsgA transmission at WD 22. This is an indication that even the robust preamble transmission was unsuccessful.

[0301] c) Receiving a MsgB, such as via one or more of the processing circuit 84, the processor 86, the radio interface 82, the random access unit 34, etc., the MsgB containing contention resolution information, such as a WD contention resolution identity MAC CE, indicating that the MsgB is intended for another WD 22 (ie, contention resolution failed).

[0302] d) Any other unsuccessful 2-step RA detection mechanism.

[0303] After the fault detection step, the method may follow different paths including different steps, depending on the type of unsuccessful 2-step RA detection. In addition, for each of those method paths, there are different sets of alternative steps, corresponding to different embodiments including alternative steps. These alternative paths are discussed below.

[0304] Method Path A: In response to MsgA transmission, WD upon receiving a RAR message or a RAR-like message 22 Actions

[0305] NOTE: These steps are applicable to any other type of failure detection scenario, which implies that the network node 16 (e.g. a radio base station such as a gNB) is able to receive the RACH preamble, but is unable to receive the PUSCH transmission (or is unable to process the content of the PUSCH transmission, e.g. due to a shortage of processing resources).

[0306] In case an unsuccessful attempt is detected, possible WD 22 actions are as follows:

[0307] Upon detection of an unsuccessful attempt to complete a 2-step RA, wherein the detection of the unsuccessful attempt consists of reception of a RAR message or a RAR-like message (e.g., similar to a fallback RAR indicated by the network) following the transmission of MsgA, WD 22 transmits Msg3 (i.e., WD 22 falls back and continues with 4-step RA) using the received UL grant in the RAR or RAR-like message, such as via one or more of the processing circuitry 84, the processor 86, the radio interface 82, the random access unit 34, etc., and in the same direction as previously (e.g., with similar beamforming properties) considering that WD 22 had previously selected the same beam (i.e., the same SSB or the same CSI-RS) for mapping to the 2-step RA resources in the first attempt. In such a fallback to a 4-step RA, the following conditions may apply:

[0308] If the same selected beam (where the unsuccessful 2-step RA occurred) is a CSI-RS beam (e.g., using CSI-RS as a QCL source) and has CFRA resources configured for that CSI-RS, and if the existing conditions for CFRA are met (e.g., validity timer, radio channel quality conditions, etc.), then:

[0309] i) WD 22 continues CFRA according to the configuration associated with the CSI-RS, such as via one or more of the processing circuit 84, the processor 86, the radio interface 82, the random access unit 34, etc., i.e., after transmitting Msg3 (i.e., essentially a retransmission of the MsgAPUSCH transmission), WD 22 does not expect a contention resolution message, i.e., at this point, WD 22 considers the random access procedure to be successful (and performs subsequent actions, such as stopping a timer, etc.).

[0310] ii) A note on the meaning of contention-free random access (CFRA). The same selected resource used for the first transmission has an associated 2-step RA resource and an associated 4-step RA resource (e.g., to be used in the fallback case). The 4-step RA configuration can be either CBRA or CFRA. This example shows a CFRA case where the WD 22 sends MsgA, such as via one or more of the processing circuit 84, the processor 86, the radio interface 82, the random access unit 34, etc., receives a fallback RAR or RAR-like message (i.e., the PUSCH portion of the MsgA), but does not expect a contention resolution message in response (because CFRA is configured for 4-step RA for that resource).

[0311] iii) To improve the chances of at least having good fallback performance, one possible configuration is that the network node 16, such as via one or more of the processing circuit 68, the processor 70, the radio interface 62, the configuration unit 33, etc., allocates a dedicated CFRA preamble (regardless of whether the network node 16 also allocates a dedicated CFRA preamble for MsgA in a 2-step RA configuration). PUSCH Thus, if, when transmitting the first MsgA, WD 22 receives a fallback RAR or RAR-like message, such as via one or more of processing circuitry 84, processor 86, radio interface 82, random access unit 34, etc., this is a preamble detection success but MsgA PUSCH WD 22 then sends Msg3 (i.e., retransmits MsgA) using the UL grant in a RAR or RAR-like message, such as via one or more of processing circuitry 84, processor 86, radio interface 82, random access unit 34, etc. PUSCH ), but does not expect a contention resolution message in response.

[0312] Otherwise, if the same selected beam (where the unsuccessful 2-step RA occurred) is a SSB beam (e.g., using SSB as a quasi collocated (QCL) source) and has CFRA resources configured for that SSB, and if the conditions for CFRA are met (e.g., validity timer, radio channel quality conditions, etc.), then:

[0313] a) WD 22, such as via one or more of processing circuitry 84, processor 86, radio interface 82, random access unit 34, etc., continues CFRA according to the configuration associated with the SSB, i.e., the transmission of the UL grant Msg3 in a RAR or RAR-like message (i.e., MsgA PUSCH retransmission), WD 22 does not expect a contention resolution message in response.

[0314] b) NOTE: Clarification of the meaning of CFRA is as follows. The same selected resource used for the first transmission has an associated 2-step RA resource and an associated 4-step RA resource (e.g., to be used in the fallback case). The 4-step RA configuration can be either CBRA or CFRA. This example illustrates a CFRA case where the WD 22 sends MsgA, such as via one or more of the processing circuit 84, the processor 86, the radio interface 82, the random access unit 34, etc., receives a fallback RAR or RAR-like message, retransmits Msg3 (i.e., the PUSCH portion of MsgA), but does not expect a contention resolution message in response (because CFRA is configured for 4-step RA for this resource).

[0315] c) To improve the chances of having at least good fallback performance, one possible configuration is for the network node 16 to allocate a dedicated CFRA preamble (regardless of whether the network node 16 also allocates a dedicated CFRA preamble for MsgA in a 2-step RA configuration). PUSCH Thus, if, when transmitting the first MsgA, WD 22 receives a fallback RAR or RAR-like message, such as via one or more of processing circuitry 84, processor 86, radio interface 82, random access unit 34, etc., this is a preamble detection success but MsgA PUSCH WD 22 then sends Msg3 (i.e., retransmits MsgA) using the UL grant in a RAR or RAR-like message, such as via one or more of processing circuitry 84, processor 86, radio interface 82, random access unit 34, etc. PUSCH ), but does not expect a contention resolution message in response.

[0316] Otherwise, if the same selected beam (where the unsuccessful 2-step RA occurred) is a SSB beam (e.g., using SSB as QCL source) and has CBRA resources configured for that SSB, and if the conditions for CBRA are met (e.g., validity timer, radio channel quality conditions, etc.), then:

[0317] a) WD 22, such as via one or more of processing circuitry 84, processor 86, radio interface 82, random access unit 34, etc., continues CBRA according to the configuration associated with the SSB resource, i.e., the transmission of the UL grant Msg3 in a RAR or RAR-like message (i.e., MsgA PUSCH retransmission), the WD 22 expects a contention resolution message in response and acts accordingly.

[0318] b) NOTE: To clarify the meaning of CBRA. The same selected resource used for the first transmission has an associated 2-step RA resource and an associated 4-step RA resource (e.g., to be used in the case of fallback). And, the 4-step RA configuration can be either CBRA or CFRA. This example shows a CBRA case, where WD 22 sends MsgA, such as via one or more of the processing circuit 84, the processor 86, the radio interface 82, the random access unit 34, etc., receives a fallback RAR or RAR-like message, retransmits Msg3 (i.e., the PUSCH portion of MsgA), and expects a contention resolution message in response (because CBRA is configured for 4-step RA for the resource). Herein, the PUSCH resource in the 2-step RA may have been dedicated or public, but the 4-step portion is a CBRA (i.e., WD 22 may receive a contention resolution message in response to Msg3).

[0319] Fig.26 is an illustration of an example of WD 22 actions in the event of an unsuccessful attempt being detected as described above. WD 22 selects beam SSb-x (box S148). MsgA (e.g., preamble + Msg3) is transmitted to network node 16 (box S150). A fallback RAR or RAR-like message (without MsgB) is received from network node 16 (box S152). WD 22 selects a beam SSB-x (box S154). WD 22 considers the UL direction (e.g., Tx beam) associated with SSB-x (box S156). WD 22 retransmits Msg3 using the UL grant provided in the fallback RAR (box S158). Msg3 retransmission is performed by WD 22 (S160). If this is a CFRA (e.g., a dedicated preamble), WD 22 does not expect Msg4 for contention resolution (box S162).

[0320] Fig. 27 is another example process diagram, where Fig.26 Some boxes are described. If the WD 22 has selected SSB-x for 2-step RA and receives a RAR or RAR-like message in response, the WD 22 continues with 4-step RA using the configuration associated with the same SSB-x (i.e., considering the same SSB-x (beam) as the selected SSB-x (beam)), such as via one or more of the processing circuit 84, the processor 86, the radio interface 82, the random access unit 34, etc. Alternatively, if the WD 22 has selected CSI-RS-y for 2-step RA and receives a RAR or RAR-like message in response, the WD 22 continues with 4-step RA using the configuration associated with the same CSI-RS-y (i.e., considering the same CSI-RS-y (beam) as the selected CSI-RS-y (beam)), such as via one or more of the processing circuit 84, the processor 86, the radio interface 82, the random access unit 34, etc. Fig.28 In particular, if this is CBRA, WD 22 expects Msg4 for contention resolution (block S164). Msg4 (contention resolution) is received at WD 22 (block S166).

[0321] Another alternative also referred to as backoff with beam reselection is described as follows:

[0322] Upon detection of an unsuccessful attempt to complete a 2-step RA, wherein the detection of the unsuccessful attempt consists of reception of a RAR message or a RAR-like message (e.g., similar to a fallback RAR indicated by the network node 16) following the transmission of MsgA, WD 22 transmits Msg3 (i.e., WD 22 falls back and continues with 4-step RA) using the UL grant received in the RAR or RAR-like message, such as via one or more of the processing circuitry 84, the processor 86, the radio interface 82, the random access unit 34, etc., and in the direction of the newly selected beam, taking into account a different selected beam than the beam that WD 22 used to map to the 2-step RA resources in the first attempt (i.e., a different SSB or a different CSI-RS). This may be referred to as fallback to 4-step RA with beam reselection. The following conditions may apply:

[0323] a) A network node 16 (such as a radio base station, e.g. a gNB) may support digital receive beamforming in order to optimally receive transmissions with the new UL TX beamforming.

[0324] b) If the new beam is a CSI-RS beam (e.g., using CSI-RS as a QCL source) and has CFRA resources configured for the CSI-RS, and if the existing conditions for CFRA are met (e.g., validity timer, radio channel quality conditions, etc.), then:

[0325] i) WD 22, such as via one or more of processing circuit 84, processor 86, radio interface 82, random access unit 34, etc., continues CFRA according to the configuration associated with the CSI-RS, i.e., in Msg3 transmission (i.e., MsgA PUSCH retransmission), the WD 22 does not expect a contention resolution message as a response, i.e., the WD 22 considers the random access procedure to be successful (and performs actions accordingly, e.g., stopping a timer, etc.).

[0326] c) Otherwise, if the new beam is an SSB beam (e.g., using SSB as a QCL source) and has CFRA resources configured for the SSB, and if the existing conditions for CFRA are met (e.g., validity timer, radio channel quality conditions, etc.), then:

[0327] i) WD 22, such as via one or more of processing circuitry 84, processor 86, radio interface 82, random access unit 34, etc., continues CFRA according to the configuration associated with the SSB, i.e., in the Msg3 transmission (i.e., MsgA PUSCH retransmission), the WD 22 does not expect a contention resolution message as a response, i.e., the WD 22 considers the random access procedure to be successful (and performs actions accordingly, e.g., stopping a timer, etc.).

[0328] d) Otherwise, if the newly selected beam is an SSB beam (e.g., using SSB as a QCL source) and has CBRA resources configured for the SSB, and if the existing conditions for CBRA are met (e.g., validity timer, radio channel quality conditions, etc.), then:

[0329] i) WD 22 continues CBRA according to the configuration associated with the SSB, such as via one or more of processing circuit 84, processor 86, radio interface 82, random access unit 34, etc., i.e., in Msg3 transmission (i.e., MsgA PUSCH retransmission), WD 22 expects a contention resolution message in response and acts accordingly.

[0330] Method Path B: Within the timer or time window for receiving MsgB and / or RAR message or RAR-like message Action upon expiration, ie, action upon determining the absence of a response to the MsgA transmission.

[0331] Fig.29 is an example signaling diagram of method path B according to one or more embodiments of the present disclosure. Fig.26 Some boxes are described. WD 22 does not receive MsgB or RAR or RAR-like message (box S168). Timer expiration of Msgb and / or RAR or RAR-like message occurs (box S170). WD 22 reselects beam SSB-y (box S172). WD 22 determines that 2-step RA is supported in alternative beam SSB-y (box S174). Power ramping of preamble is performed by WD 22 (box S176). Power ramping of Msg3 (PUSCH) is performed by WD 22 (box S178). Ramp counter for preamble is incremented by WD 22 (box S180). Ramp counter for Msg3 is incremented by WD 22 (box S182). MsgA (e.g., preamble+Msg3) is transmitted to network node 16 (box S184).

[0332] NOTE: These steps may be applied to any other type of failure detection situation, implying that a network node 16 such as a radio base station, gNB, etc. is not able to receive a preamble (or is not able to process a preamble, e.g. due to a shortage of processing resources or too many preambles being received simultaneously).

[0333] In case an unsuccessful 2-step RA attempt is detected, possible WD actions are as follows:

[0334] Upon detecting an unsuccessful attempt to complete a 2-step RA, where the detection is based on a determination of a lack of response to the transmission of MsgA, for example, based on expiration of a timer or time window for receiving MsgB and / or RAR messages or RAR-like messages, the WD 22 has not received the information of MsgB, and has not received the information included in the RAR message. In some embodiments, when faced with this situation, the WD 22, such as via one or more of the processing circuit 84, the processor 86, the radio interface 82, the random access unit 34, etc., performs at least one of the following sub-alternatives:

[0335] a) 4-step RA in a new attempt in the same beam WD 22 selects / reselects the same beam as before (e.g., if conditions are met at least for 4-step RA, e.g., radio channel quality is above a threshold), such as via one or more of processing circuitry 84, processor 86, radio interface 82, random access unit 34, etc., and performs preamble transmission power ramping (increasing transmission power according to configuration), and retransmits the preamble (but only for 4-step RA). In other words, in this retry, WD 22 does not transmit MsgA (i.e., it does not transmit content like Msg3 on PUSCH resources, and in response to the preamble, expects a RAR message).

[0336] i) In this alternative, WD 22, such as via one or more of processing circuit 84, processor 86, radio interface 82, random access unit 34, etc., will only attempt once for 2-step RA in the same beam, and if it fails, WD 22 will not attempt 2-step RA again in the same beam. Therefore, even if the 4-step RA retry fails (e.g., RAR message is not received), WD 22 can reselect another beam. But if WD 22 keeps the same beam, WD 22 will only continue 4-step RA retry until success or final failure detection (maximum number of attempts is reached).

[0337] b) 4-step RA with preamble transmit power ramp in a new attempt in another beam. WD 22 determines, such as via one or more of processing circuit 84, processor 86, radio interface 82, random access unit 34, etc., whether the conditions are met at least for 4-step RA in another beam (e.g., radio channel quality is above a threshold), and if so, WD 22 selects / reselects the other beam (which may be assumed to be the second best beam from the perspective of radio channel quality), such as via one or more of processing circuit 84, processor 86, radio interface 82, random access unit 34, etc. Then, WD 22 performs preamble transmission power ramping (increasing transmission power according to configuration, which may be based on the perceived DL path loss in the new beam) and retransmits the preamble (but only for 4-step RA). In other words, in this retry, WD 22 does not transmit MsgA (i.e., WD 22 does not transmit content similar to Msg3 on PUSCH resources, and in response to the preamble, expects a RAR message).

[0338] i) In this alternative, WD 22, such as via one or more of processing circuit 84, processor 86, radio interface 82, random access unit 34, etc., will only make one attempt for 2-step RA. That is, if it fails, WD 22 will no longer attempt 2-step RA. Therefore, even if the retry of 4-step RA fails (e.g., RAR message is not received), WD 22 can reselect another beam, but WD 22, such as via one or more of processing circuit 84, processor 86, radio interface 82, random access unit 34, etc., will only continue 4-step RA retry until success or final failure detection (maximum number of attempts is reached).

[0339] c) 4-step RA without preamble transmit power ramp in a new attempt in another beam WD 22 Such as By one or more of the processing circuit 84, the processor 86, the radio interface 82, the random access unit 34, etc.Determine whether the conditions are met at least for 4-step RA in another beam (e.g., the radio channel quality is above a threshold), and if so, WD 22 selects / reselects the other beam (e.g., it can be assumed to be the second best beam from the perspective of radio channel quality). WD 22 then retransmits the preamble in the new beam without transmit power ramping, such as via one or more of processing circuit 84, processor 86, radio interface 82, random access unit 34, etc. Note that the preamble transmit power may still be different from the preamble transmit power in the first attempt because the preamble transmit power is set relative to the DL path loss perceived in the new beam. Although a new beam is selected / reselected, WD 22 only attempts a 4-step RA. In other words, in this retry, WD 22 does not transmit the PUSCH portion of MsgA (i.e., WD 22 does not transmit content similar to Msg3 on the PUSCH resource, and in response to the preamble, expects a RAR message).

[0340] i) In this alternative, WD 22, such as via one or more of processing circuitry 84, processor 86, radio interface 82, random access unit 34, etc., will only attempt once for 2-step RA. That is, if it fails, WD 22 will no longer attempt 2-step RA. Therefore, even if the retry of 4-step RA fails (e.g., RAR message is not received), WD 22 may reselect to another beam, such as via one or more of processing circuitry 84, processor 86, radio interface 82, random access unit 34, etc., but WD 22 will only continue 4-step RA retry until success or final failure detection (maximum number of attempts is reached).

[0341] d) 2-step without beam reselection, with preamble transmit power ramping but without PUSCH transmit power ramping RA Retry The WD 22 maintains the same beam as before (assuming that the conditions for 2-step RA are still met (or optionally at least the conditions for 4-step RA are met), such as the radio channel quality is above the threshold), such as via one or more of the processing circuit 84, the processor 86, the radio interface 82, the random access unit 34, etc., and performs a preamble transmission power ramp (i.e., increases the transmission power according to the configuration), and transmits the preamble (with the increased transmission power) on the PRACH resources and the remaining part of the MsgA (MsgA) on the PUSCH resources. PUSCH ) without increasing the transmit power (i.e., no power ramping is applied for transmission on PUSCH resources) to retry the 2-step RA procedure.

[0342] i) This situation may be considered as a retry to perform a 2-step RA, which may be controlled by a timer that is started at the first attempt to perform a 2-step RA and stopped at a successful 2-step RA. Also, upon expiration, WD 22 is not allowed to continue attempting to perform a 2-step RA, i.e., when the timer expires and WD 22 is still performing random access (e.g., resource selection), WD 22 either falls back to a 4-step RA or declares RA failure, such as via one or more of the processing circuit 84, the processor 86, the radio interface 82, the random access unit 34, etc. Whether to declare RA failure or fall back to a 4-step RA may be controlled by a separate timer (or counter) that configures and / or limits the time (or number) of 4-step RA attempts.

[0343] ii) This situation may be considered as a retry to perform a 2-step RA, which may be controlled by a counter that is incremented at each attempt to perform a 2-step RA. And, upon reaching its (configurable) maximum value, the WD 22 is not allowed to continue attempting to perform a 2-step RA, i.e., the 2-step RA is considered to have failed. If a separate counter is used for 4-step RA attempts, and if this counter is still below its maximum value, the WD 22 may continue with 4-step RA with or without power ramping, with or without beam selection / reselection.

[0344] iii) This situation can be considered as a retry to perform 2-step RA, which can be controlled by counters and timers according to the above defined behavior. That is, no matter which of the timer expiration and the counter reaching its maximum value occurs first, WD 22 can be triggered to stop trying to perform 2-step RA.

[0345] e) No beam reselection, with MsgA power ramp (i.e. preamble transmit power ramp and PUSCH transmit power ramp) 2-step RA retry with both rate ramps . The WD 22 keeps / maintains the same beam as before (assuming that the conditions for 2-step RA are still met (or optionally at least the conditions for 4-step RA are met), such as the radio channel quality is above a threshold), such as via one or more of the processing circuit 84, the processor 86, the radio interface 82, the random access unit 34, etc., and performs MsgA transmission power ramping (i.e., increasing the transmission power according to the configuration), and retries the 2-step RA process by transmitting the preamble (with increased transmission power) on the PRACH resources and the remaining part of the MsgA with increased transmission power on the PUSCH resources. Note that this will be based on the DL path loss perceived in the new beam, i.e., the transmission power ramping is applied to both the preamble transmission and the PUSCH transmission. The transmission power ramping may involve the same power increase step for both the preamble transmission and the PUSCH transmission, or different power increase steps for the preamble transmission and the PUSCH transmission.

[0346] i) This situation may be considered as a retry to perform a 2-step RA, which may be controlled by a timer that is started at the first attempt to perform a 2-step RA and stopped at a successful 2-step RA. Also, upon expiration of the timer, WD 22 is not allowed to continue attempting to perform a 2-step RA. In other words, upon expiration of the timer while WD 22 is still performing random access (e.g., resource selection), WD 22 either falls back to a 4-step RA or declares RA failure, such as via one or more of the processing circuit 84, the processor 86, the radio interface 82, the random access unit 34, etc. Whether to declare RA failure or fall back to a 4-step RA may be controlled by a separate timer (or counter) that configures and / or limits the time (or number) of 4-step RA attempts.

[0347] ii) This situation may be considered as a retry to perform a 2-step RA, which may be controlled by a counter that is incremented at each attempt to perform a 2-step RA. And, upon reaching its (configurable) maximum value, the WD 22 is not allowed to continue attempting to perform a 2-step RA, i.e., the 2-step RA is considered to have failed. If a separate counter is used for 4-step RA attempts, and if this counter for 4-step RA is still below its maximum value, the WD 22 may continue with 4-step RA with or without power ramping, with or without beam selection / reselection, such as via one or more of the processing circuitry 84, the processor 86, the radio interface 82, the random access unit 34, etc.

[0348] iii) This situation can be considered as a retry to perform 2-step RA, which can be controlled by counters and timers according to the above defined behavior. That is, no matter which of the timer expiration and the counter reaching its maximum value occurs first, WD 22 can be triggered to stop trying to perform 2-step RA.

[0349] f) 2-step RA retry with beam reselection and preamble transmit power ramping WD 22 selects / reselects another beam (if the conditions in the beam are met for 2-step RA, e.g., 2-step RA configuration is available and the radio channel quality is above a threshold (or optionally, at least the conditions are met for 4-step RA)), such as via one or more of processing circuitry 84, processor 86, radio interface 82, random access unit 34, etc., and performs preamble transmission power ramping (i.e., increases the transmission power according to the configuration, which may be based on the DL path loss sensed in this new beam), and retries the 2-step RA procedure by transmitting the preamble on PRACH resources (with ramped transmission power) and transmitting the remaining Msg3 on PUSCH (without transmission power ramping). In other words, in this example, no power ramping is applied for transmission on PUSCH resources.

[0350] i) This situation may be considered as a retry to perform a 2-step RA, which may be controlled by a timer that is started at the first attempt to perform a 2-step RA and stopped at a successful 2-step RA. Also, upon expiration, WD 22 is not allowed to continue attempting to perform a 2-step RA, i.e., when the timer expires and WD 22 is still performing random access (e.g., resource selection), WD 22 either falls back to a 4-step RA or declares RA failure, such as via one or more of the processing circuit 84, the processor 86, the radio interface 82, the random access unit 34, etc. Whether to declare RA failure or fall back to a 4-step RA may be controlled by a separate timer (or counter) that configures and / or limits the time (or number) of 4-step RA attempts.

[0351] ii) This situation may be considered as a retry to perform a 2-step RA, which may be controlled by a counter that is incremented at each attempt to perform a 2-step RA. Upon reaching its maximum value (which is configurable), the WD 22 is not allowed to continue attempting to perform a 2-step RA. In other words, the 2-step RA is considered to have failed. If a separate counter is used for 4-step RA attempts, and if this counter for 4-step RA is still below its maximum value, the WD 22 may continue with 4-step RA with or without power ramping, with or without beam selection / reselection, such as via one or more of the processing circuit 84, the processor 86, the radio interface 82, the random access unit 34, etc.

[0352] iii) This situation can be considered as a retry to perform 2-step RA, which can be controlled by counters and timers according to the above defined behavior. That is, no matter which of the timer expiration and the counter reaching its maximum value occurs first, WD 22 can be triggered to stop trying to perform 2-step RA.

[0353] g) 2-step RA retry with beam reselection, with MsgA transmit power ramp. The WD 22 selects / reselects another beam, such as via one or more of the processing circuit 84, the processor 86, the radio interface 82, the random access unit 34, etc., if the conditions in the beam are met for 2-step RA (e.g., the 2-step RA configuration is available and the radio channel quality is above a threshold (or optionally, at least the conditions are met for 4-step RA)), and performs a preamble transmission power ramp (i.e., increasing the transmission power according to the configuration, which may be based on the DL path loss perceived in this new beam). The WD 22 retries the 2-step RA procedure by transmitting the preamble on the PRACH resources (with increased transmission power) and transmitting the MsgA remainder on the PUSCH resources (with increased transmission power, which may be based on the DL path loss perceived in the new beam), such as via one or more of the processing circuit 84, the processor 86, the radio interface 82, the random access unit 34, etc. In other words, the transmission power ramp is applied to both the preamble transmission and the PUSCH transmission. The transmit power ramp may involve the same power increase steps for both preamble transmission and PUSCH transmission, or different power increase steps for preamble transmission and PUSCH transmission. The transmit power ramp may involve the same power increase steps for both preamble transmission and PUSCH transmission, or different power increase steps for preamble transmission and PUSCH transmission.

[0354] i) This situation may be considered as a retry to perform a 2-step RA, which may be controlled by a timer that is started at the first attempt to perform a 2-step RA and stopped at a successful 2-step RA. Also, upon expiration, WD 22 is not allowed to continue attempting to perform a 2-step RA, i.e., when the timer expires and WD 22 is still performing random access (e.g., resource selection), WD 22 either falls back to a 4-step RA or declares RA failure, such as via one or more of the processing circuit 84, the processor 86, the radio interface 82, the random access unit 34, etc. Whether to declare RA failure or fall back to a 4-step RA may be controlled by a separate timer (or counter) that configures and / or limits the time (or number) of 4-step RA attempts.

[0355] ii) This situation may be considered as a retry to perform a 2-step RA, which may be controlled by a counter that is incremented at each attempt to perform a 2-step RA. And, upon reaching its maximum value (which is configurable), the WD 22 is not allowed to continue attempting to perform a 2-step RA, i.e., the 2-step RA is considered to have failed. If a separate counter is used for 4-step RA attempts, and if this counter for 4-step RA is still below its maximum value, the WD 22 may continue with 4-step RA with or without power ramping, with or without beam selection / reselection.

[0356] iii) This situation can be considered as a retry to perform 2-step RA, which can be controlled by counters and timers according to the above defined behavior. That is, no matter which of the timer expiration and the counter reaching its maximum value occurs first, WD 22 can be triggered to stop trying to perform 2-step RA.

[0357] h) 2-step RA retry with beam reselection without MsgA transmit power ramp WD 22 selects / reselects another beam, such as via one or more of processing circuitry 84, processor 86, radio interface 82, random access unit 34, etc., if the conditions in the beam are met for 2-step RA (e.g., 2-step RA configuration is available and the radio channel quality is above a threshold (or optionally, at least the conditions are met for 4-step RA)). WD 22, such as via one or more of processing circuitry 84, processor 86, radio interface 82, random access unit 34, etc., then retransmits the preamble on PRACH resources without transmit power ramping in the new beam (note that the preamble transmit power may still be different from the preamble transmit power in the first attempt because the preamble transmit power is set relative to the DL path loss perceived in the new beam), and also retransmits the remaining part of MsgA on PUSCH resources without transmit power ramping (note that the PUSCH transmit power may still be different from the PUSCH transmit power in the first attempt because the PUSCH transmit power is set relative to the DL path loss perceived in the new beam). In other words, no power ramp is applied to any of the transmissions in the MsgA portion.

[0358] i) This situation may be considered as a retry to perform a 2-step RA, which may be controlled by a timer that is started at the first attempt to perform a 2-step RA and stopped at a successful 2-step RA. Also, upon expiration, WD 22 is not allowed to continue attempting to perform a 2-step RA, i.e., when the timer expires and WD 22 is still performing random access (e.g., resource selection), WD 22 either falls back to a 4-step RA or declares RA failure, such as via one or more of the processing circuit 84, the processor 86, the radio interface 82, the random access unit 34, etc. Whether to declare RA failure or fall back to a 4-step RA may be controlled by a separate timer (or counter) that configures and / or limits the time (or number) of 4-step RA attempts.

[0359] ii) This situation may be considered as a retry to perform a 2-step RA, which may be controlled by a counter that is incremented at each attempt to perform a 2-step RA. And, upon reaching its maximum value (which is configurable), the WD 22 is not allowed to continue attempting to perform a 2-step RA, i.e., the 2-step RA is considered to have failed. If a separate counter is used for 4-step RA attempts, and if this counter is still below its maximum value, the WD 22 may continue with the 4-step RA with or without power ramping, with or without beam selection / reselection, such as via one or more of the processing circuit 84, the processor 86, the radio interface 82, the random access unit 34, etc.

[0360] This situation can be considered as a retry to perform 2-step RA, which can be controlled by counters and timers according to the above defined behavior. That is, no matter which one of the timer expiration and the counter reaching its maximum value occurs first, WD 22 can be triggered to stop trying to perform 2-step RA.

[0361] Fig. 27 The signaling flow of shows a method path B alternative, where beam selection / reselection and MsgA transmit power ramping are performed. Other method path B alternatives with 2-step RA with retry can be derived from this method by skipping any of the steps (one or more).

[0362] Method path C. Action upon receiving MsgB, which contains a message indicating that MsgB is intended for another WD 22 (ie, contention resolution failure), for example, WD contention resolution identity MAC CE.

[0363] This type of failure detection implies that a preamble collision occurred and that the WD 22 did not manage to successfully transmit MsgA to the network node 16, such as a radio base station or gNB, while another WD 22 using the same preamble managed to do so successfully. The reason may be that the WD 22 used too low a transmission power, or there may be other reasons. All alternatives of method path B also apply to this type of failure detection (i.e., to method path C), with the alternative of retrying the 2-step RA being preferred.

[0364] Strategies for multi-step applications of the method (i.e., when multiple RA attempts fail in succession)

[0365] If WD 22 fails RA multiple times in succession, the above process for different alternatives for different method paths may be repeated. For each consecutive failure, the method path is governed by the type of fault detection. However, even if the same type of fault detection occurs, e.g., lack of MsgB and / or RAR message or RAR-like message, and thus the same method path is applicable, WD 22 may select the same or different alternative (among the alternatives applicable to the method path) for each new fault detection within the method path.

[0366] Furthermore, when trying multiple beams (e.g., RA configurations associated with multiple SSBs and / or CSI-RS), the WD 22, such as via one or more of the processing circuitry 84, the processor 86, the radio interface 82, the random access unit 34, etc., may apply different (configured or implementation-dependent) multi-step strategies for selecting beams and how to apply the RA method:

[0367] - With one strategy (1), the WD 22 attempts a 2-step RA in a first beam, such as via one or more of the processing circuitry 84, the processor 86, the radio interface 82, the random access unit 34, etc., and if that fails, the WD reselects another beam and retries the 2-step RA in that beam, etc. When all beams that satisfy the conditions for a 2-step RA have been tried, the WD 22 returns (i.e., reselects) the first beam (or the beam with the best radio channel quality), such as via one or more of the processing circuitry 84, the processor 86, the radio interface 82, the random access unit 34, etc., and attempts a 4-step RA. If this fails, the WD 22 may reselect another beam and attempt a 4-step RA, etc.

[0368] - With another strategy (2), the WD 22 attempts a 2-step RA in a first beam, such as via one or more of the processing circuitry 84, the processor 86, the radio interface 82, the random access unit 34, etc., and if the 2-step RA fails, the WD 22 attempts a 4-step RA in the same beam. If this also fails, the WD 22 reselects a new beam, such as via one or more of the processing circuitry 84, the processor 86, the radio interface 82, the random access unit 34, etc., and first attempts a 2-step RA, and then (if beneficial) attempts a 4-step RA in the new beam, etc. That is, the WD 22 attempts both a 2-step RA and a 4-step RA in each beam before reselecting a new beam.

[0369] -The above two strategies can be seen as two basic strategies. Mixtures (mixtures / hybrids), variations and extensions of these basic strategies are possible. Some examples include:

[0370] o The WD 22, such as via one or more of the processing circuit 84, the processor 86, the radio interface 82, the random access unit 34, etc., attempts 2-step RA multiple times before reselecting a new beam, with or without transmit power ramping for PRACH and / or PUSCH transmissions. (This is an extension / variation of basic strategy 1.)

[0371] o The WD 22 attempts 2-step RA (with or without transmit power ramping for PRACH and / or PUSCH transmissions) one or more times, such as via one or more of the processing circuitry 84, the processor 86, the radio interface 82, the random access unit 34, etc., and then attempts 4-step RA (with or without transmit power ramping) one or more times before reselecting a new beam. (This is an extension / variation of basic strategy 2.)

[0372] o The WD 22 attempts 2-step RA (with or without transmit power ramping for PRACH and / or PUSCH transmission) one or more times in two or more beams (but not necessarily all beams that satisfy the 2-step RA condition, e.g., N beams), such as via one or more of the processing circuitry 84, the processor 86, the radio interface 82, the random access unit 34, etc., and then returns to the first beam (or the beam with the best radio channel quality), and attempts 4-step RA in each of an equal number of beams (i.e., N beams) one or more times. The WD 22 then returns to attempt 2-step RA, such as via one or more of the processing circuitry 84, the processor 86, the radio interface 82, the random access unit 34, etc., but this time continues with the N+1th best beam (which satisfies the condition for 2-step RA). That is, the WD 22, such as via one or more of the processing circuitry 84, the processor 86, the radio interface 82, the random access unit 34, etc., may continue to try 2-step RA in a set of beams before trying 4-step RA in a set of beams, and then try 2-step RA in another set of beams, and then try 4-step RA in another set of beams, etc. (This is a hybrid and extension / variation of the two basic strategies).

[0373] o The WD 22 attempts a 2-step RA once in each beam in a first set of beams (e.g., all beams that satisfy the 2-step RA condition), such as via one or more of the processing circuitry 84, the processor 86, the radio interface 82, the random access unit 34, etc., and then attempts a 4-step RA in a second set of beams. If the failure still persists, the WD 22 retries the 2-step RA in the first set of beams, such as via one or more of the processing circuitry 84, the processor 86, the radio interface 82, the random access unit 34, etc., but this time with a ramped transmit power (for PRACH transmissions, PUSCH transmissions, or both). If this still fails, the WD 22 may retry the 4-step RA in the second set of beams, such as via one or more of the processing circuitry 84, the processor 86, the radio interface 82, the random access unit 34, etc. Note that the first set of beams and the second set of beams may include the same beams. The reason for making these sets different could be that 2-step RA is not supported in all beams and the second set of beams could consist of beams with better radio channel quality since they do not have to have an associated 2-step RA configuration. (This is a mix and extension / variation of the two basic strategies).

[0374] ο Obviously, the above examples of mixing / expanding / changing can be further changed, for example, by changing the number of times a certain RA method is retried between consecutive beams, or by mixing / changing strategies between consecutive beams, etc. For example, WD 22, such as via one or more of processing circuit 84, processor 86, radio interface 82, random access unit 34, etc., may follow a schedule similar to the following: Beam 1: try 2-step RA, Beam 2: try 2-step RA followed by 4-step RA, Beam 3: try only 4-step RA. Then, declare final failure or return to the first beam (beam 1) or reselect the beam with the best radio channel quality and try only 4-step RA. Intermediate steps with power ramping can be inserted. In another example, WD 22 can follow basic strategy 1, but when no more beams meet the conditions for 2-step RA, there may still be one or more untried beams that meet the conditions for 4-step RA, and WD 22 can try 4-step RA in this / these beams before reselecting the first beam to try 4-step RA according to basic strategy 1. In yet another example, WD 22 follows basic strategy 1, but does not try all beams that satisfy the 2-step RA condition. Instead, WD 22 follows basic strategy 1 for a first set of beams, and then, if the failure still persists, continues to perform basic strategy 1 for a second set of beams (where the beams of the first set are assumed to have and preferably have better radio channel quality than the beams of the second set), etc. The division into different sets may be based on a radio channel quality threshold, or the number of beams in each set may be configured.

[0375] In any of these above-described cases (i.e., method paths and alternatives), when the WD 22 is described as selecting or reselecting a beam, such as via one or more of the processing circuit 84, the processor 86, the radio interface 82, the random access unit 34, etc., the method includes actions in which the WD 22 prioritizes CSI-RS based and contention-free RA, if available for the selected beam during fallback to a 4-step RA, i.e., prioritizes CSI-RS based and CFRA over at least one other RA configuration.

[0376] In all of these above cases, each time the WD 22 fails to receive a RAR, the power ramp counter is incremented, so that when the maximum number of attempts is reached, the WD 22 triggers a random access failure, such as via one or more of the processing circuit 84, the processor 86, the radio interface 82, the random access unit 34, etc. This can be modeled as a MAC level failure, because RA is a MAC level process, and this can trigger the MAC layer to notify the upper layer so that the upper layer can trigger other processes, such as radio link reestablishment.

[0377] In the case where WD 22 is allowed to perform 2-step RA retries, a maximum number of allowed attempts may be defined before WD 22 falls back to 4-step RA only, i.e., when this number is reached, WD 22 may perform 4-step RA only regardless of whether the conditions for 2-step RA are met (e.g., resource availability and radio conditions, like RSRP, RSRQ, SINR, etc.).

[0378] In any of these above cases (i.e., method paths and alternatives), the PUSCH transmission of MsgA (i.e., the part of MsgA transmitted on PUSCH and which corresponds exactly or approximately to Msg3) can be an RRC message like RRCRequest, RRCResumeRequest, RRCResumeRequest1, RRCReestablishmentRequest, RRCReconfigurationComplete, etc.

[0379] The method also includes: WD 22, in conjunction with beam selection / reselection, prioritizing beams with associated 2-step RA configurations, for example, in the absence of MsgB and / or RAR messages or RAR-like messages in response to MsgA, wherein the detection may be based on the expiration of a timer or time window for monitoring the reception of MsgB and / or RAR messages or RAR-like messages. In this case, WD 22, such as via one or more of the processing circuit 84, the processor 86, the radio interface 82, the random access unit 34, etc., may search for these beams, and if these beams meet the conditions for 2-step RA, WD 22 re-initiates 2-step RA.

[0380] The method also includes the WD 22 being configured to perform any of these different sub-alternatives described above.

[0381] The method also includes the WD 22 receiving a RAR-like message including one or more indications, such as via one or more of the processing circuit 84, the processor 86, the radio interface 82, the random access unit 34, etc., regarding whether the WD 22 should retry the 2-step RA or go to a 4-step RA (either as a continuation of an already started RA process or as a restarted RA process), or which of the above-mentioned strategies of the multi-step application of the method the WD 22 should use.

[0382] See Appendix C for examples of possible changes to the 3GPP standards to implement the arrangements described herein.

[0383] Fig.30 84, the processor 86, the radio interface 82, the random access unit 34, etc., when no RAR or RAR-like message is received, the WD 22, such as via one or more of the processing circuit 84, the processor 86, the radio interface 82, the random access unit 34, etc., retries the 2-step RA in the new beam. As can be seen, the WD 22 keeps / maintains two counters, one for the 2-step RA and the other (similar to the traditional counter) for the 4-step RA. In another alternative, a single counter is defined for both the 2-step RA and the 4-step RA. In either case, different rules may be associated with the counter, such as the number of times the WD 22 is allowed or required to retry the 2-step RA before the WD 22 falls back to the 4-step RA (when available and when conditions are met).

[0384] One aspect of the present disclosure includes WD actions upon random access resource selection, i.e., upon triggering random access and selecting a beam (e.g., SSB or CSI-RS resource), performing 2-step RA configuration (if the selected beam has an available configuration for 2-step RA and satisfies the conditions for performing 2-step RA), and then detecting an unsuccessful attempt to perform 2-step RA (e.g., by receiving a RAR-like message, such as fallback RAR, or by expiration of a timer of a MsgB / RAR timer or a RAR-like message), which may be either a prepared fallback to 4-step RA (e.g., if the network responds to MsgA with a RAR-like message) or an unprepared fallback (e.g., if the WD 22 does not receive any response to MsgA at all). Upon detecting an unsuccessful 2-step RA attempt, the WD 22, such as via one or more of the processing circuit 84, the processor 86, the radio interface 82, the random access unit 34, etc., performs at least one of the following:

[0385] Retry the RA using a 2-step RA that does not include any of the following, one or more of the following:

[0386] a) Power ramp of preamble PRACH transmission;

[0387] b) Power ramping of MsgA PUSCH (i.e. MsgAPUSCH) transmissions; and

[0388] c) Beam reselection.

[0389] Retry the RA using a 4-step RA that does not include any, one, or more of the following:

[0390] a) Power ramp of preamble PRACH transmission;

[0391] b) beam reselection; and

[0392] c) Choice between CFRA and CBRA.

[0393] Some embodiments also include a multi-step strategy, where WD 22 mixes the selection of RA methods (2-step or 4-step), beam reselection, and transmit power ramping in different orders according to different strategies.

[0394] According to one aspect, WD 22 is configured to fall back from a two-step random access procedure. WD 22 has processing circuitry 84 configured to, after an unsuccessful attempt to perform a two-step random access, perform at least one of: retry the two-step random access attempt and perform a four-step random access procedure.

[0395] According to this aspect, in some embodiments, retrying the two-step random access attempt includes power ramping of a preamble physical random access channel PRACH transmission. In some embodiments, performing a four-step random access procedure includes beam reselection and selecting between contention-free random access or contention-based random access.

[0396] Some examples

[0397] Embodiment A1. A wireless device 22 (WD 22) configured to communicate with a network node 16, the WD 22 being configured to and / or including a radio interface 82 and / or a processing circuit 84 configured to:

[0398] After an unsuccessful attempt to perform two-step random access, perform at least one of the following:

[0399] retry the two-step random access attempt; and

[0400] A four-step random access procedure is performed.

[0401] Embodiment A2. WD 22 of Embodiment A1, wherein retrying the two-step random access attempt includes power ramping of a preamble Physical Random Access Channel (PRACH) transmission.

[0402] Embodiment A3. The WD 22 of Embodiment A1, wherein a four-step random access procedure is performed including beam reselection and selecting between contention-free random access or contention-based random access.

[0403] Embodiment B1. A method implemented in a wireless device 22 (WD 22), the method comprising:

[0404] After an unsuccessful attempt to perform two-step random access, perform at least one of the following:

[0405] retry the two-step random access attempt; and

[0406] A four-step random access procedure is performed.

[0407] Embodiment B2. The method of embodiment B1, wherein the retry of the two-step random access attempt includes a power ramp of a preamble Physical Random Access Channel (PRACH) transmission.

[0408] Embodiment B3. The method of embodiment B1, wherein performing a four-step random access procedure includes beam reselection and selecting between contention-free random access or contention-based random access.

[0409] Appendix A

[0410] 5.1.1 Random Access Process Initialization

[0411] According to 3GPP TS 38.300, the random access procedure described in this subclause is initiated by a PDCCH command, by the MAC entity itself, or by RRC for the event. There is only one ongoing random access procedure in the MAC entity at any point in time. The random access procedure on the SCell shall only be initiated by a PDCCH command where the ra-PreambleIndex is different from 0b00000.

[0412] NOTE 1: If a new random access procedure is triggered while another procedure is already in progress in the MAC entity, it is up to the WD implementation whether to continue the ongoing procedure or to start a new procedure (e.g., for SI request).

[0413] RRC configures the following parameters for the random access procedure:

[0414] -prach-ConfigurationIndex: the available set of PRACH opportunities for transmission of random access preambles;

[0415] -preambleReceivedTargetPower: initial random access preamble power;

[0416] -rsrp-ThresholdSSB: RSRP threshold used to select SSB. If the random access procedure is initiated for beam failure recovery, the rsrp-ThresholdSSB used to select SSB in candidateBeamRSList refers to the rsrp-ThresholdSSB in the BeamFailureRecoveryConfig IE;

[0417] -rsrp-ThresholdCSI-RS: RSRP threshold for selecting CSI-RS. If the random access procedure is initiated for beam failure recovery, rsrp-ThresholdCSI-RS is equal to rsrp-ThresholdSSB in BeamFailureRecoveryConfig IE;

[0418] -rsrp-ThresholdSSB-SUL: RSRP threshold for selecting between NUL carrier and SUL carrier;

[0419] -CandidateBeamRSList: a list of reference signals (CSI-RS and / or SSB) identifying candidate beams for recovery and associated random access parameters;

[0420] -recoverySearchSpaceId: Search space identity used to monitor responses to beam failure recovery requests

[0421] -powerRampingStep: power ramping factor;

[0422] -powerRampingStepHighPriority: power ramping factor in case of prioritized random access procedure;

[0423] -scalingFactorBI: scaling factor for the prioritized random access process;

[0424] -ra-PreambleIndex: random access preamble;

[0425] -ra-ssb-OccasionMaskIndex: defines the PRACH occasion(s) associated with the SSB, where the MAC entity may transmit the random access preamble (see subclause 7.4);

[0426] -ra-OccasionList: defines the PRACH occasion(s) associated with the CSI-RS, where the MAC entity may transmit the random access preamble;

[0427] -ra-PreambleStartIndex: starting index of (one or more) random access preambles for on-demand SI request;

[0428] -preambleTransMax: Maximum number of random access preamble transmissions;

[0429] -ssb-perRACH-OccasionAndCB-PreamblesPerSSB: defines the number of SSBs mapped to each PRACH opportunity and the number of contention-based random access preambles mapped to each SSB;

[0430] - If groupBconfigured is configured, configure random access preamble group B.

[0431] - Among the contention-based random access preambles (as defined in 3GPP TS 38.213) associated with an SSB, the first numberOfRA-PreamblesGroupA random access preambles belong to random access preamble group A. The remaining random access preambles associated with an SSB belong to random access preamble group B (if configured).

[0432] NOTE 2: If the cell supports random access preamble group B, random access preamble group B is included for each SSB.

[0433] -If random access preamble group B is configured, then:

[0434] -ra-Msg3SizeGroupA: determines the threshold of the random access preamble group;

[0435] -msg3-DeltaPreamble: Delta in 3GPP TS 38.213 PREAMBLE_Msg3 ;

[0436] -messagePowerOffsetGroupB: power offset for preamble selection;

[0437] -numberOfRA-PreamblesGroupA: defines the number of random access preambles in random access preamble group A for each SSB.

[0438] - The set of PRACH opportunities and / or random access preambles used for SI request, if any;

[0439] - The set of PRACH opportunities and / or random access preambles used for beam failure recovery request, if any;

[0440] - the set of PRACH opportunities and / or random access preambles used for reconfiguration with synchronization, if any;

[0441] -ra-ResponseWindow: time window to monitor (one or more) RA responses (SpCell only);

[0442] -ra-ContentionResolutionTimer: Contention resolution timer (SpCell only).

[0443] Furthermore, it is assumed that the following information of the relevant serving cell is available to the WD:

[0444] -If random access preamble group B is configured, then:

[0445] - If the serving cell for the random access procedure is configured with a supplementary uplink as specified in 3GPP TS 38.331 and a SUL carrier is selected for performing the random access procedure, then:

[0446] - P for the SUL carrier as specified in 3GPP TS 38.101-1, 3GPP TS 38.101-2 and 3GPP TS 38.101-3 CMAX,f,c .

[0447] -otherwise:

[0448] - P for NUL carriers as specified in 3GPP TS 38.101-1, 3GPP TS 38.101-2 and 3GPP TS 38.101-3 CMAX,f,c .

[0449] The following WD variables are used in the random access process:

[0450] -PREAMBLE_INDEX;

[0451] -PREAMBLE_TRANSMISSION_COUNTER;

[0452] -PREAMBLE_POWER_RAMPING_COUNTER;

[0453] -PREAMBLE_POWER_RAMPING_STEP;

[0454] -PREAMBLE_RECEIVED_TARGET_POWER;

[0455] -PREAMBLE_BACKOFF;

[0456] -PCMAX;

[0457] -SCALING_FACTOR_BI;

[0458] -TEMPORARY_C-RNTI.

[0459] When a random access procedure is initiated on a serving cell, the MAC entity shall:

[0460] 1>Flush the Msg3 buffer;

[0461] 1> Set PREAMBLE_TRANSMISSION_COUNTER to 1;

[0462] 1> Set PREAMBLE_POWER_RAMPING_COUNTER to 1;

[0463] 1> Set PREAMBLE_BACKOFF to 0ms;

[0464] 1> If the carrier used for the random access procedure is explicitly signaled, then:

[0465] 2> Select the signaled carrier for performing the random access procedure;

[0466] 2> Set PCMAX to the P of the signaled carrier CMAX,f,c .

[0467] 1> Otherwise, if the carrier used for the random access procedure is not explicitly signaled; and

[0468] 1> if the serving cell for the random access procedure is configured with a supplementary uplink as specified in 3GPP TS 38.331; and

[0469] 1> If the RSRP referenced by the downlink path loss is less than rsrp-ThresholdSSB-SUL, then:

[0470] 2> Select the SUL carrier for performing the random access procedure;

[0471] 2> Set PCMAX to the P of the SUL carrier CMAX,f,c .

[0472] 1> Otherwise:

[0473] 2> Select the NUL carrier for performing the random access procedure;

[0474] 2> Set PCMAX to the P of NUL carrier CMAX,f,c .

[0475] 1> Perform the BWP operation as specified in subclause 5.15;

[0476] 1> Set PREAMBLE_POWER_RAMPING_STEP to powerRampingStep;

[0477] 1>Set SCALING_FACTOR_BI to 1;

[0478] 1> if the random access procedure is initiated for beam failure recovery (as specified in subclause 5.17); and

[0479] 1> If beamFailureRecoveryConfig is configured for the active UL BWP of the selected carrier, then:

[0480] 2> Start beamFailureRecoveryTimer, if configured;

[0481] 2> Apply the parameters powerRampingStep, preambleReceivedTargetPower and preambleTransMax configured in beamFailureRecoveryConfig;

[0482] 2> If powerRampingStepHighPriority is configured in beamFailureRecoveryConfig, then:

[0483] 3> Set PREAMBLE_POWER_RAMPING_STEP to powerRampingStepHighPriority.

[0484] 2> Otherwise:

[0485] 3>Set PREAMBLE_POWER_RAMPING_STEP to powerRampingStep.

[0486] 2> If scalingFactorBI is configured in beamFailureRecoveryConfig, then:

[0487] 3>Set SCALING_FACTOR_BI to scalingFactorBI.

[0488] 1> Otherwise, if the random access procedure is initiated for handover; and

[0489] 1> If rach-ConfigDedicated is configured for the selected carrier, then:

[0490] 2> If powerRampingStepHighPriority is configured in rach-ConfigDedicated, then:

[0491] 3> Set PREAMBLE_POWER_RAMPING_STEP to powerRampingStepHighPriority.

[0492] 2> If scalingFactorBI is configured in rach-ConfigDedicated, then:

[0493] 3>Set SCALING_FACTOR_BI to scalingFactorBI.

[0494] 1> Perform the random access resource selection procedure (see subclause 5.1.2).

[0495] 5.1.2 Random Access Resource Selection

[0496] The MAC entity shall:

[0497] 1> if the random access procedure is initiated for beam failure recovery (as specified in subclause 5.17); and

[0498] 1> if beamFailureRecoveryTimer (in subclause 5.17) is running or not configured; and

[0499] 1> if contention-free random access resources for beam failure recovery request associated with any of the SSBs and / or CSI-RS have been explicitly provided by RRC; and

[0500] 1> If at least one of the following is available: an SSB with an SS-RSRP higher than rsrp-ThresholdSSB among the SSBs in candidateBeamRSList or a CSI-RS with a CSI-RSRP higher than rsrp-ThresholdCSI-RS among the CSI-RS in candidateBeamRSList, then:

[0501] 2> Select an SSB with an SS-RSRP higher than rsrp-ThresholdSSB among the SSBs in candidateBeamRSList or a CSI-RS with a CSI-RSRP higher than rsrp-ThresholdCSI-RS among the CSI-RSs in candidateBeamRSList;

[0502] 2> If a CSI-RS is selected and there is no ra-PreambleIndex associated with the selected CSI-RS, then:

[0503] 3> Set PREAMBLE_INDEX to the ra-PreambleIndex corresponding to the SSB in candidateBeamRSList that is quasi-co-located with the selected CSI-RS as specified in 3GPP TS 38.214.

[0504] 2> Otherwise:

[0505] 3> Set PREAMBLE_INDEX to the ra-PreambleIndex corresponding to the selected SSB or CSI-RS from the set of random access preambles used for beam failure recovery request.

[0506] 1> Otherwise, if ra-PreambleIndex has been explicitly provided by PDCCH; and

[0507] 1> If ra-PreambleIndex is not 0b00000, then:

[0508] 2> Set PREAMBLE_INDEX to the signaled ra-PreambleIndex;

[0509] 2> Select the SSB signaled by PDCCH.

[0510] 1> Otherwise, if a contention-free random access resource associated with the SSB has been explicitly provided in rach-ConfigDedicated, and at least one SSB with an SS-RSRP higher than rsrp-ThresholdSSB is available among the associated SSBs, then:

[0511] 2> Select an SSB with a SS-RSRP higher than rsrp-ThresholdSSB among the associated SSBs;

[0512] 2> Set PREAMBLE_INDEX to the ra-PreambleIndex corresponding to the selected SSB.

[0513] 1> Otherwise, if a contention-free random access resource associated with a CSI-RS has been explicitly provided in rach-ConfigDedicated, and at least one CSI-RS with a CSI-RSRP higher than rsrp-ThresholdCSI-RS is available among the associated CSI-RSs, then:

[0514] 2> Select a CSI-RS with a CSI-RSRP higher than rsrp-ThresholdCSI-RS among the associated CSI-RS;

[0515] 2> Set PREAMBLE_INDEX to the ra-PreambleIndex corresponding to the selected CSI-RS.

[0516] 1> Otherwise, if the random access procedure is initiated for an SI request (as specified in 3GPP TS 38.331); and

[0517] 1> If the random access resources for the SI request have been explicitly provided by RRC, then:

[0518] 2> If at least one of the SSBs with SS-RSRP higher than rsrp-ThresholdSSB is available, then:

[0519] 3> Select an SSB with SS-RSRP higher than rsrp-ThresholdSSB.

[0520] 2> Otherwise:

[0521] 3>Select Any SSB.

[0522] 2> Select the random access preamble corresponding to the selected SSB from the (one or more) random access preambles determined according to ra-PreambleStartIndex as specified in 3GPP TS 38.331;

[0523] 2> Set PREAMBLE_INDEX to the selected random access preamble.

[0524] 1> Otherwise (i.e., for contention-based random access preamble selection):

[0525] 2> If at least one of the SSBs with SS-RSRP higher than rsrp-ThresholdSSB is available, then:

[0526] 3> Select an SSB with SS-RSRP higher than rsrp-ThresholdSSB.

[0527] 2> Otherwise:

[0528] 3>Select Any SSB.

[0529] 2> If Msg3 has not been sent, then:

[0530] 3> If random access preamble group B is configured, then:

[0531] 4> If the potential Msg3 size (UL data available for transmission plus MAC header and MAC CE (if required)) is greater than ra-Msg3SizeGroupA, and the path loss is less than PCMAX-preambleReceivedTargetPower-msg3-DeltaPreamble-messagePowerOffsetGroupB (of the serving cell performing the random access procedure); or

[0532] 4> If a random access procedure is initiated for the CCCH logical channel and the CCCH SDU size plus the MAC subheader is greater than ra-Msg3SizeGroupA, then:

[0533] 5> Select random access preamble group B.

[0534] 4> Otherwise:

[0535] 5> Select random access preamble group A.

[0536] 3> Otherwise:

[0537] 4> Select random access preamble group A.

[0538] 2> Otherwise (i.e., Msg3 is being retransmitted):

[0539] 3> Select the same random access preamble group as the random access preamble group used for the random access preamble transmission attempt corresponding to the first transmission of Msg3.

[0540] 2> Randomly select a random access preamble with equal probability from the random access preambles associated with the selected SSB and the selected random access preamble group.

[0541] 2> Set PREAMBLE_INDEX to the selected random access preamble.

[0542] 1> if the random access procedure is initiated for an SI request (as specified in 3GPP TS 38.331); and

[0543] 1> If ra-AssociationPeriodIndex and si-RequestPeriod are configured, then:

[0544] 2> Determine the next available PRACH opportunity among the PRACH opportunities corresponding to the selected SSB in the association period given by ra-AssociationPeriodIndex in si-RequestPeriod permitted by the restrictions given by ra-ssb-occasionMaskIndex (if configured) (the MAC entity shall randomly select the PRACH opportunity with equal probability among the consecutive PRACH opportunities corresponding to the selected SSB according to subclause 8.1 of 3GPP TS38.213).

[0545] 1> Otherwise, if SSB is selected above, then:

[0546] 2> Determine the next available PRACH opportunity from the PRACH opportunities corresponding to the selected SSB permitted by the restriction given by ra-ssb-OccasionMaskIndex (if configured or indicated by PDCCH) (the MAC entity shall randomly select the PRACH opportunity with equal probability among the consecutive PRACH opportunities corresponding to the selected SSB according to subclause 8.1 of 3GPP TS 38.213; the MAC entity may take into account the possible occurrence of measurement gaps when determining the next available PRACH opportunity corresponding to the selected SSB).

[0547] 1> Otherwise, if CSI-RS is selected above, then:

[0548] 2> If there is no contention-free random access resource associated with the selected CSI-RS, then:

[0549] 3> Determine the next available PRACH opportunity from the PRACH opportunities corresponding to the SSB quasi-co-located with the selected CSI-RS in candidateBeamRSList as specified in 3GPP TS 38.214, permitted by the restrictions given by ra-ssb-OccasionMaskIndex (if configured) (the MAC entity shall randomly select the PRACH opportunity with equal probability among the consecutive PRACH opportunities corresponding to the SSB quasi-co-located with the selected CSI-RS according to subclause 8.1 of 3GPP TS 38.213; the MAC entity may take into account the possible occurrence of measurement gaps when determining the next available PRACH opportunity corresponding to the SSB quasi-co-located with the selected CSI-RS).

[0550] 2> Otherwise:

[0551] 3> Determine the next available PRACH opportunity from the PRACH opportunities in the ra-OccasionList corresponding to the selected CSI-RS (the MAC entity should randomly select the PRACH opportunity with equal probability among the PRACH opportunities corresponding to the selected CSI-RS that appear at the same time but on different subcarriers; the MAC entity may take into account the possible occurrence of measurement gaps when determining the next available PRACH opportunity corresponding to the selected CSI-RS).

[0552] 1> Perform the random access preamble transmission procedure (see subclause 5.1.3).

[0553] NOTE: When the WD determines whether there is an SSB with an SS-RSRP higher than rsrp-ThresholdSSB or a CSI-RS with a CSI-RSRP higher than rsrp-ThresholdCSI-RS, the WD uses the most recent unfiltered L1-RSRP measurement.

[0554] Appendix B

[0555] 5.1.2 Random Access Resource Selection

[0556] The MAC entity shall:

[0557] 1> if the random access procedure is initiated for beam failure recovery (as specified in subclause 5.17); and

[0558] 1> if beamFailureRecoveryTimer (in subclause 5.17) is running or not configured; and

[0559] 1> if contention-free random access resources for beam failure recovery request associated with any of the SSBs and / or CSI-RS have been explicitly provided by RRC; and

[0560] …

[0561] 1> Otherwise, if a contention-free random access resource associated with the SSB has been explicitly provided in rach-ConfigDedicated, and at least one SSB with an SS-RSRP higher than rsrp-ThresholdSSB is available among the associated SSBs, then:

[0562] …

[0563] 1> Otherwise, if a contention-free random access resource associated with a CSI-RS has been explicitly provided in rach-ConfigDedicated, and at least one CSI-RS with a CSI-RSRP higher than rsrp-ThresholdCSI-RS is available among the associated CSI-RSs, then:

[0564] …

[0565] 1> Otherwise (i.e., for contention-based random access preamble selection):

[0566] …

[0567] 1> Otherwise, if SSB is selected above, then:

[0568] 2> Determine the next available PRACH opportunity from the PRACH opportunities corresponding to the selected SSB permitted by the restriction given by ra-ssb-OccasionMaskIndex (if configured or indicated by PDCCH) (the MAC entity shall randomly select the PRACH opportunity with equal probability among the consecutive PRACH opportunities corresponding to the selected SSB according to subclause 8.1 of 3GPP TS 38.213; the MAC entity may take into account the possible occurrence of measurement gaps when determining the next available PRACH opportunity corresponding to the selected SSB).

[0569] 1> Otherwise, if CSI-RS is selected above, then:

[0570] 2> If there is no contention-free random access resource associated with the selected CSI-RS, then:

[0571] 3> Determine the next available PRACH opportunity from the PRACH opportunities corresponding to the SSB quasi-co-located with the selected CSI-RS in candidateBeamRSList as specified in 3GPP TS 38.214, permitted by the restrictions given by ra-ssb-OccasionMaskIndex (if configured) (the MAC entity shall randomly select the PRACH opportunity with equal probability among the consecutive PRACH opportunities corresponding to the SSB quasi-co-located with the selected CSI-RS according to subclause 8.1 of 3GPP TS 38.213; the MAC entity may take into account the possible occurrence of measurement gaps when determining the next available PRACH opportunity corresponding to the SSB quasi-co-located with the selected CSI-RS).

[0572] 2> Otherwise:

[0573] 3> Determine the next available PRACH opportunity from the PRACH opportunities in the ra-OccasionList corresponding to the selected CSI-RS (the MAC entity should randomly select the PRACH opportunity with equal probability among the PRACH opportunities corresponding to the selected CSI-RS that appear at the same time but on different subcarriers; the MAC entity may take into account the possible occurrence of measurement gaps when determining the next available PRACH opportunity corresponding to the selected CSI-RS).

[0574] 1> Perform the random access preamble transmission procedure (see subclause 5.1.3).

[0575] NOTE: When the WD determines whether there is an SSB with an SS-RSRP higher than rsrp-ThresholdSSB or a CSI-RS with a CSI-RSRP higher than rsrp-ThresholdCSI-RS, the WD uses the most recent unfiltered L1-RSRP measurement.

[0576] Then, in an excerpt from Section 5.1.4 of 3GPP TS 28.321, we show the actions when the RAR timer expires after preamble transmission.

[0577] 5.1.4 Random Access Response Reception

[0578] Once the Random Access Preamble has been transmitted, and regardless of the possible occurrence of Measurement Gaps, the MAC entity shall:

[0579] …

[0580] 1> Otherwise, if a downlink assignment has been received for the RA-RNTI on the PDCCH and the received TB is successfully decoded, then:

[0581] 2> If the Random Access Response contains a MAC subPDU with a Backoff Indicator, then:

[0582] 3> Set PREAMBLE_BACKOFF to the value of the BI field of the MAC subPDU multiplied by SCALING_FACTOR_BI using Table 7.2-1.

[0583] 2> Otherwise:

[0584] 3> Set PREAMBLE_BACKOFF to 0ms.

[0585] 2> If the Random Access Response contains a MAC subPDU with a Random Access Preamble identifier corresponding to the transmitted PREAMBLE_INDEX (see subclause 5.1.3), then:

[0586] 3> This random access response is considered to be received successfully.

[0587] 2> If the random access response is considered to be received successfully, then:

[0588] 3> If the Random Access Response includes a MAC subPDU with only RAPID, then:

[0589] 4> The random access process is considered to be successfully completed;

[0590] 4>Indicates to the upper layer the receipt of confirmation of the SI request.

[0591] 3> Otherwise:

[0592] 4> Apply the following actions to the serving cell in which the random access preamble is transmitted:

[0593] 5> Process the received timing advance command (see subclause 5.2);

[0594] 5> Indicate to the lower layer the amount of power ramp applied to the latest random access preamble transmission (i.e. (PREAMBLE_POWER_RAMPING_COUNTER–1)×PREAMBLE_POWER_RAMPING_STEP) and preambleReceivedTargetPower;

[0595] 5> If the serving cell of the random access procedure is an SRS-only SCell, then:

[0596] 6> Ignore the received UL grant.

[0597] 5> Otherwise:

[0598] 6> Process the received UL grant value and indicate it to the lower layer.

[0599] 4> If the random access preamble is not selected by the MAC entity among (one or more) contention-based random access preambles, then:

[0600] 5> The random access process is considered to be successfully completed.

[0601] 4> Otherwise:

[0602] 5> Set TEMPORARY_C-RNTI to the value received in the random access response;

[0603] 5> If this is the first successful random access response received within this random access procedure, then:

[0604] 6> If the transmission is not for the CCCH logical channel, then:

[0605] 7> Indicate to the multiplexing and assembly entity to include the C-RNTI MAC CE in subsequent uplink transmissions.

[0606] 6> Obtain the MAC PDU to be transmitted from the multiplexing and assembly entity and store it in the Msg3 buffer.

[0607] NOTE: If within a random access procedure, the uplink grant provided in a random access response for the same group of contention based random access preambles has a different size than the first uplink grant allocated during this random access procedure, the WD behavior is not defined.

[0608] 1> if the ra-ResponseWindow configured in BeamFailureRecoveryConfig expires and if no PDCCH transmission on the search space indicated by recoverySearchSpaceId addressed to the C-RNTI has been received on the serving cell in which the preamble was transmitted; or

[0609] 1> If the ra-ResponseWindow configured in RACH-ConfigCommon expires and if a random access response containing a random access preamble identifier matching the transmitted PREAMBLE_INDEX has not been received, then:

[0610] 2> The random access response reception is considered unsuccessful;

[0611] 2>Increment PREAMBLE_TRANSMISSION_COUNTER by 1;

[0612] 2> If PREAMBLE_TRANSMISSION_COUNTER = preambleTransMax + 1, then:

[0613] 3> If the random access preamble is transmitted on the SpCell, then:

[0614] 4>Indicate random access problems to the upper layer;

[0615] 4> If this random access procedure is triggered by an SI request, then:

[0616] 5> The random access process is considered to have not been successfully completed.

[0617] 3> Otherwise, if the random access preamble is transmitted on the SCell, then:

[0618] 4> The random access process is considered to have not been successfully completed.

[0619] 2> If the random access process is not completed, then:

[0620] 3> Select a random backoff time based on a uniform distribution between 0 and PREAMBLE_BACKOFF;

[0621] 3> If the criteria for selecting a contention-free random access resource (as defined in subclause 5.1.2) are met during the back-off time, then:

[0622] 4>Perform the random access resource selection process (see subclause 5.1.2);

[0623] 3> Otherwise:

[0624] 4> Perform the random access resource selection procedure after the backoff time (see subclause 5.1.2).

[0625] Appendix C

[0626] 5.3.4 Random Access

[0627] Two different lengths of random access preamble sequences are supported. Long sequence length 839 is applied to subcarrier spacings of 1.25 and 5 kHz, while short sequence length 139 is applied to subcarrier spacings of 15, 30, 60, and 120 kHz. Long sequences support both unrestricted and restricted sets of Type A and Type B, while short sequences only support unrestricted sets.

[0628] Multiple PRACH preamble formats are defined with one or more PRACH OFDM symbols and different cyclic prefixes and guard times. The PRACH preamble configuration to be used is provided to the WD in the system information.

[0629] The WD calculates the PRACH transmit power for preamble retransmission based on the most recently estimated path loss and a power ramp counter.

[0630] System information provides information for WD to determine the association between SSB and RACH resources. The RSRP threshold for SSB selection for RACH resource association is configurable by the network.

[0631] In case of 2-step random access, the WD selects a beam (e.g., SSB or CSI-RS) and determines whether there is an association between the SSB (or CSI-RS in case of mobility) and the 2-step random access configuration (e.g., PUSCH resources associated with the SSB). The additional RSRP threshold for SSB (or CSI-RS) selection for 2-step random access association is configurable by the network, and the WD performs a 2-step RA only if both conditions are met (otherwise the WD performs a 4-step RA).

[0632] If the WD receives a RAR-like message (indicating successful preamble reception but unsuccessful decoding of msg3) when a 2-step RA is triggered in the selected beam, the WD reselects the same beam and continues with the 4-step RA (i.e., the WD retransmits msg3 using the UL grant provided in the RAR-like message).

[0633] If the WD does not receive a RAR-like message within the RAR time window (i.e., until the RAR timer expires) when a 2-step RA is triggered in the selected beam, then it is up to the WD implementation to select another beam or perform a power ramp (within the same beam). If the WD reselects another beam, the WD is allowed to perform a 2-step RA if the conditions are met (e.g., radio conditions, availability of a 2-step RA configuration, and the 2-step RA timer is running). Otherwise, the WD falls back to a 4-step RA.

[0634] …

[0635] 9.2.3.2 Switching

[0636] …

[0637] In the common RACH configuration, the network configures the WD with a 2-step or 4-step RA, where the 2-step RA can be configured per beam (as in the case of CFRA). The common RACH configuration for the beam in the target cell is associated only with the SSB(s). The network may have dedicated RACH configurations associated with the SSB(s) and / or have dedicated RACH configurations associated with the CSI-RS(s) within the cell. The target gNB can only include one of the following RACH configurations in the handover command to enable the WD to access the target cell:

[0638] i) Common RACH configuration, possibly including 2-step RA configuration per beam;

[0639] ii) Common RACH configuration (possibly including 2-step RA configuration per beam) + dedicated RACH configuration associated with SSB;

[0640] iii) Common RACH configuration (possibly including 2-step RA configuration per beam) + dedicated RACH configuration associated with CSI-RS.

[0641] The dedicated RACH configuration allocates (one or more) RACH resources along with a quality threshold for their use. When dedicated RACH resources are provided, they are prioritized by the WD and as long as the quality threshold for those dedicated resources is met, the WD should not switch to contention-based RACH resources. The order of accessing dedicated RACH resources depends on the WD implementation. And, when common RACH resources for 2-step RA are provided, they are prioritized by the WD and as long as the quality threshold for those dedicated resources is met, the WD should not switch to contention-based RACH resources. The order of accessing dedicated RACH resources depends on the WD implementation.

[0642] When 2-step random access resources are offered, they are prioritized by the WD, otherwise, if 4-step CFRA is offered, it is prioritized, otherwise a 4-step CBRA is initiated.

[0643] During handover, when timer T304 is running (and when the 2-step RA timer is running), the WD may fall back from 2-step RA to 4-step RA, otherwise only 4-step RA is allowed.

[0644] The following changes might be applied to the NR specification 3GPP TS 38.321 (note that these are examples and there are other ways of modifying the specification to implement / support some embodiments):

[0645] 5.1.1 Random Access Process Initialization

[0646] According to 3GPP TS 38.300, the random access procedure described in this subclause is initiated by a PDCCH command, by the MAC entity itself, or by RRC for the event. There is only one ongoing random access procedure in the MAC entity at any point in time. The random access procedure on the SCell shall only be initiated by a PDCCH command where the ra-PreambleIndex is different from 0b00000.

[0647] NOTE 1: If a new random access procedure is triggered while another procedure is already in progress in the MAC entity, it is up to the WD implementation whether to continue the ongoing procedure or to start a new procedure (e.g., for SI request).

[0648] RRC configures the following parameters for the random access procedure:

[0649] -prach-ConfigurationIndex: the available set of PRACH opportunities for transmission of random access preambles;

[0650] -preambleReceivedTargetPower: initial random access preamble power;

[0651] -rsrp-ThresholdSSB: RSRP threshold used to select SSB. If the random access procedure is initiated for beam failure recovery, the rsrp-ThresholdSSB used to select SSB in candidateBeamRSList refers to the rsrp-ThresholdSSB in the BeamFailureRecoveryConfig IE;

[0652] -rsrp-ThresholdCSI-RS: RSRP threshold for selecting CSI-RS. If the random access procedure is initiated for beam failure recovery, rsrp-ThresholdCSI-RS is equal to rsrp-ThresholdSSB in BeamFailureRecoveryConfig IE;

[0653] -rsrp-ThresholdSSB-SUL: RSRP threshold for selecting between NUL carrier and SUL carrier;

[0654] -CandidateBeamRSList: a list of reference signals (CSI-RS and / or SSB) identifying candidate beams for recovery and associated random access parameters; it may contain a list of candidate beams with configured 2-step RA resources;

[0655] -recoverySearchSpaceId: Search space identity used to monitor responses to beam failure recovery requests

[0656] -powerRampingStep: power ramping factor;

[0657] -powerRampingStepMsg3: power ramping factor for msg3 in 2-step RA;

[0658] -powerRampingStepHighPriority: power ramping factor in case of prioritized random access procedure;

[0659] -scalingFactorBI: scaling factor for the prioritized random access process;

[0660] -ra-PreambleIndex: random access preamble;

[0661] -ra-ssb-OccasionMaskIndex: defines the PRACH occasion(s) associated with the SSB, where the MAC entity may transmit the random access preamble (see subclause 7.4);

[0662] -ra-OccasionList: defines the PRACH occasion(s) associated with the CSI-RS, where the MAC entity may transmit the random access preamble;

[0663] -ra-PreambleStartIndex: starting index of (one or more) random access preambles for on-demand SI request;

[0664] -preambleTransMax: Maximum number of random access preamble transmissions;

[0665] -ssb-perRACH-OccasionAndCB-PreamblesPerSSB: defines the number of SSBs mapped to each PRACH opportunity and the number of contention-based random access preambles mapped to each SSB;

[0666] - If groupBconfigured is configured, configure random access preamble group B.

[0667] - Among the contention-based random access preambles (as defined in 3GPP TS 38.213) associated with an SSB, the first numberOfRA-PreamblesGroupA random access preambles belong to random access preamble group A. The remaining random access preambles associated with an SSB belong to random access preamble group B (if configured).

[0668] NOTE 2: If the cell supports random access preamble group B, random access preamble group B is included for each SSB.

[0669] -If random access preamble group B is configured, then:

[0670] -ra-Msg3SizeGroupA: determines the threshold of the random access preamble group;

[0671] -msg3-DeltaPreamble: Delta in 3GPP TS 38.213 PREAMBLE_Msg3 ;

[0672] -messagePowerOffsetGroupB: power offset for preamble selection;

[0673] -numberOfRA-PreamblesGroupA: defines the number of random access preambles in random access preamble group A for each SSB.

[0674] - The set of PRACH opportunities and / or random access preambles used for SI request, if any;

[0675] - The set of PRACH opportunities and / or random access preambles used for beam failure recovery request, if any;

[0676] - the set of PRACH opportunities and / or random access preambles used for reconfiguration with synchronization, if any;

[0677] -ra-ResponseWindow: time window to monitor (one or more) RA responses (SpCell only);

[0678] -ra-ContentionResolutionTimer: Contention resolution timer (SpCell only).

[0679] Furthermore, it is assumed that the following information of the relevant serving cell is available to the WD:

[0680] -If random access preamble group B is configured, then:

[0681] - If the serving cell for the random access procedure is configured with a supplementary uplink as specified in 3GPP TS 38.331 and a SUL carrier is selected for performing the random access procedure, then:

[0682] - P for the SUL carrier as specified in 3GPP TS 38.101-1, 3GPP TS 38.101-2 and 3GPP TS 38.101-3 CMAX,f,c .

[0683] -otherwise:

[0684] - P for NUL carriers as specified in 3GPP TS 38.101-1, 3GPP TS 38.101-2 and 3GPP TS 38.101-3 CMAX,f,c .

[0685] The following WD variables are used in the random access process:

[0686] -PREAMBLE_INDEX;

[0687] -PREAMBLE_TRANSMISSION_COUNTER;

[0688] -PREAMBLE_POWER_RAMPING_COUNTER;

[0689] -PREAMBLE_POWER_RAMPING_STEP;

[0690] -PREAMBLE_RECEIVED_TARGET_POWER;

[0691] -PREAMBLE_BACKOFF;

[0692] -PCMAX;

[0693] -SCALING_FACTOR_BI;

[0694] -TEMPORARY_C-RNTI.

[0695] When a random access procedure is initiated on a serving cell, the MAC entity shall:

[0696] 1> Dump and clear Msg3 buffer;

[0697] 1> Set PREAMBLE_TRANSMISSION_COUNTER to 1;

[0698] 1> Set PREAMBLE_POWER_RAMPING_COUNTER to 1;

[0699] 1> Set PREAMBLE_BACKOFF to 0ms;

[0700] 1> If the carrier used for the random access procedure is explicitly signaled, then:

[0701] 2> Select the signaled carrier for performing the random access procedure;

[0702] 2> Set PCMAX to the P of the signaled carrier CMAX,f,c .

[0703] 1> Otherwise, if the carrier used for the random access procedure is not explicitly signaled; and

[0704] 1> if the serving cell for the random access procedure is configured with a supplementary uplink as specified in 3GPP TS 38.331; and

[0705] 1> If the RSRP referenced by the downlink path loss is less than rsrp-ThresholdSSB-SUL, then:

[0706] 2> Select the SUL carrier for performing the random access procedure;

[0707] 2> Set PCMAX to the P of the SUL carrier CMAX,f,c .

[0708] 1> Otherwise:

[0709] 2> Select the NUL carrier for performing the random access procedure;

[0710] 2> Set PCMAX to the P of NUL carrier CMAX,f,c .

[0711] 1> Perform the BWP operation as specified in subclause 5.15;

[0712] 1> Set PREAMBLE_POWER_RAMPING_STEP to powerRampingStep;

[0713] 1>Set SCALING_FACTOR_BI to 1;

[0714] 1> if the random access procedure is initiated for beam failure recovery (as specified in subclause 5.17); and

[0715] 1> If beamFailureRecoveryConfig is configured for the active UL BWP of the selected carrier, then:

[0716] 2> Start beamFailureRecoveryTimer, if configured;

[0717] 2> Apply the parameters powerRampingStep, preambleReceivedTargetPower and preambleTransMax configured in beamFailureRecoveryConfig;

[0718] 2> If powerRampingStepHighPriority is configured in beamFailureRecoveryConfig, then:

[0719] 3> Set PREAMBLE_POWER_RAMPING_STEP to powerRampingStepHighPriority.

[0720] 2> Otherwise:

[0721] 3>Set PREAMBLE_POWER_RAMPING_STEP to powerRampingStep.

[0722] 2> If scalingFactorBI is configured in beamFailureRecoveryConfig, then:

[0723] 3>Set SCALING_FACTOR_BI to scalingFactorBI.

[0724] 1> Otherwise, if the random access procedure is initiated for handover; and

[0725] 1> If rach-ConfigDedicated is configured for the selected carrier, then:

[0726] 2> If powerRampingStepHighPriority is configured in rach-ConfigDedicated, then:

[0727] 3> Set PREAMBLE_POWER_RAMPING_STEP to powerRampingStepHighPriority.

[0728] 2> If scalingFactorBI is configured in rach-ConfigDedicated, then:

[0729] 3>Set SCALING_FACTOR_BI to scalingFactorBI.

[0730] 1> Perform the random access resource selection procedure (see subclause 5.1.2).

[0731] 5.1.2 Random Access Resource Selection

[0732] The MAC entity shall:

[0733] 1> if the random access procedure is initiated for beam failure recovery (as specified in subclause 5.17); and

[0734] 1> if beamFailureRecoveryTimer (in subclause 5.17) is running or not configured; and

[0735] 1> if the 2-step random access resource timer for beam failure recovery is running; and

[0736] 1> if the 2-step random access resources (e.g. PRACH and PUSCH resources) for the beam failure recovery request associated with any of the SSBs and / or CSI-RS have been explicitly provided by RRC; and

[0737] 1> If at least one of the following is available: an SSB with an SS-RSRP higher than rsrp-ThresholdSSB2-stepRA and rsrp-ThresholdSSB among the SSBs in candidateBeamRSList or a CSI-RS with a CSI-RSRP higher than rsrp-ThresholdCSI-RS2-stepRA and rsrp-ThresholdCSI-RS among the CSI-RS in candidateBeamRSList, then:

[0738] 2> Select an SSB with an SS-RSRP higher than rsrp-ThresholdSSB and rsrp-ThresholdSSB2-stepRA among the SSBs in candidateBeamRSList or a CSI-RS with a CSI-RSRP higher than rsrp-ThresholdCSI-RS2-stepRA and rsrp-ThresholdCSI-RS among the CSI-RS in candidateBeamRSList;

[0739] 2> If a CSI-RS is selected and there is no ra-PreambleIndex associated with the selected CSI-RS, then:

[0740] 3> Set PREAMBLE_INDEX to the ra-PreambleIndex corresponding to the SSB in candidateBeamRSList that is quasi-co-located with the selected CSI-RS as specified in 3GPP TS 38.214.

[0741] 2> Otherwise:

[0742] 3> Set PREAMBLE_INDEX to the ra-PreambleIndex corresponding to the selected SSB or CSI-RS from the set of random access preambles used for beam failure recovery request.

[0743] 1> Otherwise, if contention-free random access resources for beam failure recovery request associated with any of the SSBs and / or CSI-RS have been explicitly provided by RRC; and

[0744] 1> If at least one of the following is available: an SSB with an SS-RSRP higher than rsrp-ThresholdSSB among the SSBs in candidateBeamRSList or a CSI-RS with a CSI-RSRP higher than rsrp-ThresholdCSI-RS among the CSI-RS in candidateBeamRSList, then:

[0745] 2> Select an SSB with an SS-RSRP higher than rsrp-ThresholdSSB among the SSBs in candidateBeamRSList or a CSI-RS with a CSI-RSRP higher than rsrp-ThresholdCSI-RS among the CSI-RSs in candidateBeamRSList;

[0746] 2> If a CSI-RS is selected and there is no ra-PreambleIndex associated with the selected CSI-RS, then:

[0747] 3> Set PREAMBLE_INDEX to the ra-PreambleIndex corresponding to the SSB in candidateBeamRSList that is quasi-co-located with the selected CSI-RS as specified in 3GPP TS 38.214.

[0748] 2> Otherwise:

[0749] 3> Set PREAMBLE_INDEX to the ra-PreambleIndex corresponding to the selected SSB or CSI-RS from the set of random access preambles used for beam failure recovery request.

[0750] 1> Otherwise, if ra-PreambleIndex has been explicitly provided by PDCCH; and

[0751] 1> If ra-PreambleIndex is not 0b00000, then:

[0752] 2> Set PREAMBLE_INDEX to the signaled ra-PreambleIndex;

[0753] 2> Select the SSB signaled by PDCCH.

[0754] 1> Otherwise, if 2-step random access resources (e.g., PRACH and PUSCH resources) associated with the SSB have been explicitly provided by RRC (e.g., in system information or RRCReconfiguration), and at least one SSB among the associated SSBs with SS-RSRP higher than rsrp-ThresholdSSB2-stepRA and rsrp-ThresholdSSB is available, and if the 2-step random access resource timer is running, then:

[0755] 2> Select an SSB with SS-RSRP higher than rsrp-ThresholdSSB2-stepRA and rsrp-ThresholdSSB among the associated SSBs (i.e., WD prioritizes 2-step RA if available and if the conditions are met);

[0756] 2> Set PREAMBLE_INDEX to the ra-PreambleIndex corresponding to the selected SSB.

[0757] 1> Otherwise, if a contention-free random access resource associated with the SSB has been explicitly provided in rach-ConfigDedicated, and at least one SSB with an SS-RSRP higher than rsrp-ThresholdSSB is available among the associated SSBs, then:

[0758] 2> Select an SSB with a SS-RSRP higher than rsrp-ThresholdSSB among the associated SSBs;

[0759] 2> Set PREAMBLE_INDEX to the ra-PreambleIndex corresponding to the selected SSB.

[0760] 1> Otherwise, if 2-step random access resources (e.g., PRACH and PUSCH resources) associated with the CSI-RS have been explicitly provided by RRC (e.g., in system information or RRCReconfiguration), and at least one CSI-RS among the associated CSI-RS with a CSI-RSRP higher than rsrp-ThresholdCSI-RS 2-stepRA and rsrp-ThresholdCSI-RS is available, and if the 2-step random access resource timer is running, then:

[0761] 2> Select a CSI-RS with a CSI-RSRP higher than rsrp-ThresholdCSI-RS2-stepRA and rsrp-ThresholdCSI-RS among the associated CSI-RS;

[0762] 2> Set PREAMBLE_INDEX to the ra-PreambleIndex corresponding to the selected CSI-RS.

[0763] 1> Otherwise, if a contention-free random access resource associated with a CSI-RS has been explicitly provided in rach-ConfigDedicated, and at least one CSI-RS with a CSI-RSRP higher than rsrp-ThresholdCSI-RS is available among the associated CSI-RSs, then:

[0764] 2> Select a CSI-RS with a CSI-RSRP higher than rsrp-ThresholdCSI-RS among the associated CSI-RS;

[0765] 2> Set PREAMBLE_INDEX to the ra-PreambleIndex corresponding to the selected CSI-RS.

[0766] 1> Otherwise, if the random access procedure is initiated for an SI request (as specified in 3GPP TS 38.331); and

[0767] 1> If the random access resources for the SI request have been explicitly provided by RRC, then:

[0768] 2> If at least one of the SSBs with SS-RSRP higher than rsrp-ThresholdSSB is available, then:

[0769] 3> Select an SSB with SS-RSRP higher than rsrp-ThresholdSSB.

[0770] 2> Otherwise:

[0771] 3>Select Any SSB.

[0772] 2> Select the random access preamble corresponding to the selected SSB from the (one or more) random access preambles determined according to ra-PreambleStartIndex as specified in 3GPP TS 38.331;

[0773] 2> Set PREAMBLE_INDEX to the selected random access preamble.

[0774] 1> Otherwise (i.e., for 4-step contention-based random access preamble selection):

[0775] 2> If at least one of the SSBs with SS-RSRP higher than rsrp-ThresholdSSB is available, then:

[0776] 3> Select an SSB with SS-RSRP higher than rsrp-ThresholdSSB.

[0777] 2> Otherwise:

[0778] 3>Select Any SSB.

[0779] 2> If Msg3 has not been sent, then:

[0780] 3> If random access preamble group B is configured, then:

[0781] 4> If the potential Msg3 size (UL data available for transmission plus MAC header and MAC CE (if required)) is greater than ra-Msg3SizeGroupA, and the path loss is less than PCMAX-preambleReceivedTargetPower-msg3-DeltaPreamble-messagePowerOffsetGroupB (of the serving cell performing the random access procedure); or

[0782] 4> If a random access procedure is initiated for the CCCH logical channel and the CCCH SDU size plus the MAC subheader is greater than ra-Msg3SizeGroupA, then:

[0783] 5> Select random access preamble group B.

[0784] 4> Otherwise:

[0785] 5> Select random access preamble group A.

[0786] 3> Otherwise:

[0787] 4> Select random access preamble group A.

[0788] 2> Otherwise (i.e., Msg3 is being retransmitted):

[0789] 3> Select the same random access preamble group as the random access preamble group used for the random access preamble transmission attempt corresponding to the first transmission of Msg3.

[0790] 2> Randomly select a random access preamble with equal probability from the random access preambles associated with the selected SSB and the selected random access preamble group.

[0791] 2> Set PREAMBLE_INDEX to the selected random access preamble.

[0792] 1> if the random access procedure is initiated for an SI request (as specified in 3GPP TS 38.331); and

[0793] 1> If ra-AssociationPeriodIndex and si-RequestPeriod are configured, then:

[0794] 2> Determine the next available PRACH opportunity among the PRACH opportunities corresponding to the selected SSB in the association period given by ra-AssociationPeriodIndex in si-RequestPeriod permitted by the restrictions given by ra-ssb-occasionMaskIndex (if configured) (the MAC entity shall randomly select the PRACH opportunity with equal probability among the consecutive PRACH opportunities corresponding to the selected SSB according to subclause 8.1 of 3GPP TS38.213).

[0795] 1> Otherwise, if SSB is selected above, then:

[0796] 2> Determine the next available PRACH opportunity from the PRACH opportunities corresponding to the selected SSB permitted by the restriction given by ra-ssb-OccasionMaskIndex (if configured or indicated by PDCCH) (the MAC entity shall randomly select the PRACH opportunity with equal probability among the consecutive PRACH opportunities corresponding to the selected SSB according to subclause 8.1 of 3GPP TS 38.213; the MAC entity may take into account the possible occurrence of measurement gaps when determining the next available PRACH opportunity corresponding to the selected SSB).

[0797] 1> Otherwise, if CSI-RS is selected above, then:

[0798] 2> If there is no contention-free random access resource associated with the selected CSI-RS, then:

[0799] 3> Determine the next available PRACH opportunity from the PRACH opportunities corresponding to the SSB quasi-co-located with the selected CSI-RS in candidateBeamRSList as specified in 3GPP TS 38.214, permitted by the restrictions given by ra-ssb-OccasionMaskIndex (if configured) (the MAC entity shall randomly select the PRACH opportunity with equal probability among the consecutive PRACH opportunities corresponding to the SSB quasi-co-located with the selected CSI-RS according to subclause 8.1 of 3GPP TS 38.213; the MAC entity may take into account the possible occurrence of measurement gaps when determining the next available PRACH opportunity corresponding to the SSB quasi-co-located with the selected CSI-RS).

[0800] 2> Otherwise:

[0801] 3> Determine the next available PRACH opportunity from the PRACH opportunities in the ra-OccasionList corresponding to the selected CSI-RS (the MAC entity should randomly select the PRACH opportunity with equal probability among the PRACH opportunities corresponding to the selected CSI-RS that appear at the same time but on different subcarriers; the MAC entity may take into account the possible occurrence of measurement gaps when determining the next available PRACH opportunity corresponding to the selected CSI-RS).

[0802] 1> Perform the random access preamble transmission procedure (see subclause 5.1.3).

[0803] NOTE: When the WD determines whether there is an SSB with an SS-RSRP higher than rsrp-ThresholdSSB or a CSI-RS with a CSI-RSRP higher than rsrp-ThresholdCSI-RS, the WD uses the most recent unfiltered L1-RSRP measurement.

[0804] 5.1.3 Random Access Preamble Transmission

[0805] For each random access preamble, the MAC entity shall:

[0806] 1> If PREAMBLE_TRANSMISSION_COUNTER is greater than 1; and

[0807] 1> If the notification to suspend the power ramp counter has not been received from the lower layer; and

[0808] 1> If the selected SSB or CSI-RS has not changed from the selection in the last random access preamble transmission, then:

[0809] 2>Increment PREAMBLE_POWER_RAMPING_COUNTER by 1;

[0810] 1> Select the value of DELTA_PREMIUM according to subclause 7.3;

[0811] 1>Set PREAMBLE_RECEIVED_TARGET_POWER to preambleReceivedTargetPower+DELTA_PREAMBLE+(PREAMBLE_POWER_RAMPING_COUNTER–1)×PREAMBLE_POWER_RAMPING_STEP;

[0812] 1> Calculate the RA-RNTI associated with the PRACH opportunity in which the random access preamble is transmitted, except for the contention-free random access preamble used for beam failure recovery request;

[0813] 1> Command the physical layer to transmit a random access preamble using the selected PRACH opportunity, the corresponding RA-RNTI (if available), PREAMBLE_INDEX and PREAMBLE_RECEIVED_TARGET_POWER.

[0814] The RA-RNTI associated with the PRACH opportunity in which the random access preamble is transmitted is calculated as:

[0815] RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id

[0816] Where s_id is the index of the first OFDM symbol of the PRACH opportunity (0≤s_id<14), t_id is the index of the first time slot of the PRACH opportunity in the system frame (0≤t_id<80), where the subcarrier spacing that determines t_id is based on the μ value specified in subclause 5.3.2 in 3GPP TS38.211, f_id is the index of the PRACH opportunity in the frequency domain (0≤f_id<8), and ul_carrier_id is the UL carrier used for random access preamble transmission (0 for NUL carrier and 1 for SUL carrier).

[0817] 5.1.4 Random Access Response Reception

[0818] Once the Random Access Preamble has been transmitted, and regardless of the possible occurrence of Measurement Gaps, and regardless of the possible joint transmission with msg3 in a 2-step RA, the MAC entity shall:

[0819] 1> If the contention-free random access preamble for beam failure recovery request is transmitted by the MAC entity, then:

[0820] 2> At the first PDCCH timing specified in 3GPP TS 38.213 after the random access preamble transmission is completed, start the ra-ResponseWindow configured in BeamFailureRecoveryConfig;

[0821] 2> When ra-ResponseWindow is running, monitor PDCCH transmission on the search space indicated by recoverySearchSpaceId of the SpCell identified by C-RNTI.

[0822] 1> Otherwise:

[0823] 2> At the first PDCCH opportunity specified in 3GPP TS 38.213 after the random access preamble transmission is completed, start the ra-ResponseWindow configured in RACH-ConfigCommon;

[0824] 2> While ra-ResponseWindow is running, monitor the PDCCH of the SpCell for the random access response(s) identified by the RA-RNTI.

[0825] 1> If notification of reception of a PDCCH transmission on the search space indicated by recoverySearchSpaceId is received from the lower layer of the serving cell in which the preamble was transmitted; and

[0826] 1> if the PDCCH transmission is addressed to the C-RNTI; and

[0827] 1> If the contention-free random access preamble for beam failure recovery request is transmitted by the MAC entity, then:

[0828] 2> The random access process is considered to be completed successfully.

[0829] 1> Otherwise, if a downlink assignment has been received for the RA-RNTI on the PDCCH and the received TB is successfully decoded, then:

[0830] 2> If the Random Access Response contains a MAC subPDU with a Backoff Indicator, then:

[0831] 3> Set PREAMBLE_BACKOFF to the value of the BI field of the MAC subPDU multiplied by SCALING_FACTOR_BI using Table 7.2-1.

[0832] 2> Otherwise:

[0833] 3> Set PREAMBLE_BACKOFF to 0ms.

[0834] 2> If the Random Access Response contains a MAC subPDU with a Random Access Preamble identifier corresponding to the transmitted PREAMBLE_INDEX (see subclause 5.1.3), then:

[0835] 3> This random access response is considered to be received successfully.

[0836] 2> If the random access response is considered to be received successfully, then:

[0837] 3> If the Random Access Response includes a MAC subPDU with only RAPID, then:

[0838] 4> The random access process is considered to be successfully completed;

[0839] 4>Indicates to the upper layer the receipt of confirmation of the SI request.

[0840] 3> Otherwise:

[0841] 4> Apply the following actions to the serving cell in which the random access preamble is transmitted:

[0842] 5> Process the received timing advance command (see subclause 5.2);

[0843] 5> Indicate to the lower layer the amount of power ramp applied to the latest random access preamble transmission (i.e. (PREAMBLE_POWER_RAMPING_COUNTER–1)×PREAMBLE_POWER_RAMPING_STEP) and preambleReceivedTargetPower;

[0844] 5> If the serving cell of the random access procedure is an SRS-only SCell, then:

[0845] a 6> Ignore the received UL grant.

[0846] 5> Otherwise:

[0847] b 6> Process the received UL grant value and indicate it to the lower layer.

[0848] 4> If the random access preamble is not selected by the MAC entity among (one or more) contention-based random access preambles, then:

[0849] 5> The random access process is considered to be successfully completed.

[0850] 4> Otherwise:

[0851] 5> Set TEMPORARY_C-RNTI to the value received in the random access response;

[0852] 5> If this is the first successful random access response received within this random access procedure, then:

[0853] c 6> If the transmission is not for the CCCH logical channel, then:

[0854] 7> Indicate to the multiplexing and assembly entity to include the C-RNTI MAC CE in subsequent uplink transmissions.

[0855] d 6> Obtain the MAC PDU to be transmitted from the multiplexing and assembly entity and store it in the Msg3 buffer.

[0856] NOTE: If within a random access procedure, the uplink grant provided in a random access response for the same group of contention based random access preambles has a different size than the first uplink grant allocated during this random access procedure, the WD behavior is not defined.

[0857] 1> if the ra-ResponseWindow configured in BeamFailureRecoveryConfig expires and if no PDCCH transmission on the search space indicated by recoverySearchSpaceId addressed to the C-RNTI has been received on the serving cell in which the preamble was transmitted; or

[0858] 1> if the ra-ResponseWindow2stepRA configured in BeamFailureRecoveryConfig expires and if a PDCCH transmission on the search space indicated by recoverySearchSpaceId addressed to the C-RNTI has not been received on the serving cell in which the preamble was transmitted; or

[0859] 1> if the ra-ResponseWindow2stepRA configured in RACH-ConfigCommon expires and if a random access response containing a random access preamble identifier matching the transmitted PREAMBLE_INDEX has not been received; or

[0860] 1> If the ra-ResponseWindow configured in RACH-ConfigCommon expires and if a random access response containing a random access preamble identifier matching the transmitted PREAMBLE_INDEX has not been received, then:

[0861] 2> The random access response reception is considered unsuccessful;

[0862] 2>Increment PREAMBLE_TRANSMISSION_COUNTER by 1;

[0863] 2> If this is a 2-step RA attempt, then:

[0864] 3>Increment PREAMBLE_TRANSMISSION_COUNTER_2_STEP_RA by 1;

[0865] 4> If PREAMBLE_TRANSMISSION_COUNTER_2_STEP_RA=preambleTransMax2Step+1, then:

[0866] 5> If the random access preamble is transmitted on the SpCell, then:

[0867] 6> Indicate 2-step RA problem to the upper layer;

[0868] 6> If this random access procedure is triggered by an SI request, then:

[0869] 7> The 2-step RA process is considered to have not been completed successfully.

[0870] 5> Otherwise, if the random access preamble is transmitted on the SCell, then:

[0871] 6> The 2-step RA process is considered to have not been completed successfully.

[0872] 5> Continue the process with only 4 steps of RA.

[0873] 2> If PREAMBLE_TRANSMISSION_COUNTER = preambleTransMax + 1, then:

[0874] 3> If the random access preamble is transmitted on the SpCell, then:

[0875] 4>Indicate random access problems to the upper layer;

[0876] 4> If this random access procedure is triggered by an SI request, then:

[0877] 5> The random access process is considered to have not been successfully completed.

[0878] 3> Otherwise, if the random access preamble is transmitted on the SCell, then:

[0879] 4> The random access process is considered to have not been successfully completed.

[0880] 2> If the random access process is not completed, then:

[0881] 3> Select a random backoff time based on a uniform distribution between 0 and PREAMBLE_BACKOFF;

[0882] 3> If the criteria for selecting a contention-free random access resource (as defined in subclause 5.1.2) are met during the back-off time, then:

[0883] 4>Perform the random access resource selection process (see subclause 5.1.2);

[0884] 3> Otherwise:

[0885] 4> Perform the random access resource selection procedure after the backoff time (see subclause 5.1.2).

[0886] The MAC entity may stop the ra-ResponseWindow (and therefore stop monitoring for (one or more) random access responses) after successfully receiving a random access response containing a random access preamble identifier that matches the transmitted PREAMBLE_INDEX.

[0887] HARQ operation is not applicable for random access response reception.

[0888] As will be appreciated by those skilled in the art, the concepts described herein may be embodied as methods, data processing systems, computer program products, and / or computer storage media storing executable computer programs. Thus, the concepts described herein may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware aspects, all generally referred to herein as "circuits" or "modules". Any process, step, action, and / or functionality described herein may be performed and / or associated with a corresponding module, which may be implemented in software and / or firmware and / or hardware. Further, the present disclosure may take the form of a computer program product on a tangible computer-usable storage medium, in which a computer program code executable by a computer is embodied. Any suitable tangible computer-readable medium may be utilized, including a hard disk, a CD-ROM, an electronic storage device, an optical storage device, or a magnetic storage device.

[0889] Some embodiments are described herein with reference to flowchart illustrations and / or block diagrams of methods, systems, and computer program products. It will be appreciated that each frame of the flowchart illustration and / or block diagram and the combination of frames in the flowchart illustration and / or block diagram can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer (thereby creating a special-purpose computer), a special-purpose computer, or other programmable data processing device to produce a machine, so that instructions executed by the processor of the computer or other programmable data processing device create components for implementing the functions / operations specified in one or more flowcharts and / or block diagram frames.

[0890] These computer program instructions may also be stored in a computer-readable memory or storage medium, which can direct a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture including instruction components, which implement the functions / operations specified in one or more flowcharts and / or block diagrams.

[0891] The computer program instructions may also be loaded onto a computer or other programmable data processing device to cause a series of operable steps to be performed on the computer or other programmable device to produce a computer-implemented process, so that the instructions executed on the computer or other programmable device provide steps for implementing the functions / operations specified in one or more flowcharts and / or block diagram blocks.

[0892] It is to be understood that the functions / operations indicated in the blocks may not occur in the order indicated in the operational diagrams. For example, two blocks shown in succession may actually be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending on the functionality / operations involved. Although some of the figures include arrows on communication paths to illustrate the primary direction of communication, it is to be understood that communication may occur in the opposite direction of the arrows depicted.

[0893] Computer program code for carrying out operations of the concepts described herein may be used, for example, The computer program code for carrying out the operations of the present disclosure may be written in an object-oriented programming language such as C++ or C++. However, the computer program code for carrying out the operations of the present disclosure may also be written in a conventional procedural programming language such as the "C" programming language. The program code may be executed entirely on the user's computer, partially on the user's computer, as a stand-alone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer. In the latter case, the remote computer may be connected to the user's computer via a local area network (LAN) or a wide area network (WAN), or a connection may be established with an external computer (e.g., via the Internet using an Internet service provider's Internet).

[0894] Many different embodiments have been disclosed herein in conjunction with the above description and accompanying drawings. It will be understood that it would be unduly repetitive and confusing to literally describe and illustrate every combination and subcombination of these embodiments. Thus, all embodiments can be combined in any manner and / or combination, and this specification (including the accompanying drawings) should be interpreted as constituting a complete written description of all combinations and subcombinations of the embodiments described herein, as well as the manner and process of making and using them, and should support claims to any such combination or subcombination.

[0895] Abbreviations that may be used in the foregoing description include:

[0896] Abbreviation

[0897] 3GPP Third Generation Partnership Project

[0898] 4G Fourth Generation

[0899] 5G Fifth Generation

[0900] 5GC 5G Core Network

[0901] 5GS 5G System

[0902] AMF Access and Mobility Management Function

[0903] BFR Beam Failure Recovery

[0904] CBRA Contention-based random access

[0905] CCA Clear Channel Assessment

[0906] CFRA Contention-free random access

[0907] CN Core Network

[0908] C-RNTI Cell Radio Network Temporary Identifier

[0909] CRS Cell-specific Reference Signal

[0910] DCI Downlink Control Information

[0911] DL Downlink

[0912] DMRS Demodulation Reference Signal

[0913] eNB Evolved NodeB (radio base station in LTE)

[0914] EPC Evolved Packet Core

[0915] EPS Evolved Packet System

[0916] E-UTRA Evolved Universal Terrestrial Radio Access

[0917] E-UTRAN Evolved Universal Terrestrial Radio Access Network

[0918] GHz Gigahertz

[0919] gNB NR radio base station

[0920] HO Handover

[0921] IE Information Elements

[0922] kHz kilohertz

[0923] LAA License Assisted Access

[0924] LBT Listen before you speak

[0925] LTE Long Term Evolution

[0926] MAC Media Access Control

[0927] MCS Modulation and Coding Scheme

[0928] MIB Master Information Block

[0929] MME Mobility Management Entity

[0930] ms milliseconds

[0931] Msg

[0932] NGC Next Generation Core

[0933] NG-RAN Next Generation RAN

[0934] NR New Radio

[0935] NR-U Unlicensed NR (i.e. NR operating in unlicensed spectrum.)

[0936] OFDM Orthogonal Frequency Division Multiplexing

[0937] O&M Operation and Maintenance

[0938] PBCH Physical Broadcast Channel

[0939] PCI Physical Cell Identity

[0940] PDCCH Physical Downlink Control Channel

[0941] PDSCH Physical Downlink Shared Channel

[0942] PRACH Physical Random Access Channel

[0943] PSS Primary Synchronization Signal

[0944] PUCCH Physical Uplink Control Channel

[0945] PUSCH Physical Uplink Shared Channel

[0946] RA Random Access

[0947] RACH Random Access Channel

[0948] RAN Radio Access Network

[0949] RB Resource Block

[0950] RMSI Remaining Minimum System Information

[0951] RNTI Radio Network Temporary Identifier

[0952] RRC Radio Resource Control

[0953] RTT Round Trip Time

[0954] Interface between RAN and CN (i.e., between E-UTRAN and EPC) in S1 EPS / LTE

[0955] SCS Subcarrier Spacing

[0956] SGW Service Gateway

[0957] SI System Information

[0958] SIB System Information Block

[0959] SON Self-organizing network / self-optimizing network

[0960] SRB Signalling Radio Bearer

[0961] SS Sync Signal

[0962] SSB Synchronous Signal Block

[0963] SSS Secondary synchronization signal

[0964] TA Timing Advance

[0965] TDD Time Division Duplex

[0966] TS Technical Specifications

[0967] TSG Technical Specification Group

[0968] UE User Equipment

[0969] UL Uplink

[0970] UPF User Plane Function

[0971] URLLC Ultra-Reliable Low Latency Communications

[0972] Interface between Uu RAN and WD (e.g., between gNB and WD in NR)

[0973] WG Working Group

[0974] X2 Interface / reference point between two eNBs

[0975] Xn Interface / reference point between two gNBs

[0976] Those skilled in the art will appreciate that the embodiments described herein are not limited to what has been particularly shown and described herein above. Furthermore, unless mentioned to the contrary above, it should be noted that all drawings are not to scale.

[0977] Many modifications and variations are possible in light of the above teaching without departing from the scope of the following claims.

Claims

1. A wireless device (22) configured to communicate with a network node (16), the wireless device (22) comprising: A processing circuit (84), the processing circuit (84) being configured to: Triggering the random access (RA) process; selecting a first beam for the RA process, the selected first beam being associated with a two-step RA configuration, a characteristic of the selected first beam being determined to satisfy a predefined threshold; and performing the RA procedure associated with the two-step RA configuration using the selected first beam, Wherein, the processing circuit (84) is further configured to: determining that a step of the two-step RA procedure has failed by receiving a fallback random access response RAR; In response to determining that a step of the two-step RA process has failed, performing one of the following: retransmitting the uplink shared channel portion of message A msgA as an uplink shared channel message in a four-step RA procedure; and The two-step RA process is reattempted at least in part by performing beam reselection.

2. The wireless device (22) of claim 1, wherein: The processing circuit (84) is further configured to: Receive system information; as well as A determination is made based at least on the system information whether the selected first beam is associated with the two-step RA configuration, the two-step RA configuration corresponding to a mapping of the selected first beam to a physical uplink shared channel (PUSCH) configuration.

3. The wireless device (22) according to any one of claims 1 to 2, wherein: The selected first beam is selected from a plurality of beams, a subset of the plurality of beams being associated with the two-step RA configuration.

4. The wireless device (22) of claim 3, wherein: The subset of the plurality of beams is one of: a subset of synchronization signal block, SSB, beams and a set of channel state information reference signal, CSI-RS, beams.

5. The wireless device (22) of claim 4, wherein: The subset of SSB beams is associated with contention-free RA resources for contention-free RA.

6. The wireless device (22) according to any one of claims 4 to 5, wherein: At least one other beam of the plurality of beams is not associated with the two-step RA configuration.

7. The wireless device (22) of claim 5, wherein: At least one of the subset of beams is associated with a contention-based RA, and the contention-free RA takes precedence over the contention-based RA.

8. The wireless device (22) according to any one of claims 1 to 7, wherein: The characteristic of the selected first beam is a channel quality, and the predefined threshold is a channel quality threshold.

9. The wireless device (22) of claim 1, wherein: The processing circuit (84) is further configured to determine that the step of the two-step RA process has failed based on one of: lack of response to the msgA; Receiving a random access response RAR message including fallback information; as well as A message B msgB is received comprising first information indicating that said step of said two-step RA procedure has failed.

10. The wireless device (22) of claim 9, wherein: The back-off information includes an indication that the step of the two-step RA procedure has failed.

11. The wireless device (22) of claim 9, wherein: The first information is contention resolution information.

12. The wireless device (22) of claim 3, wherein: The retransmission is performed based on reselecting a beam from the plurality of beams, the reselecting comprising using a contention-free RA resource configured for one of a channel state information reference signal CSI-RS and a synchronization signal block SSB.

13. A method implemented by a wireless device (22) configured to communicate with a network node (16), the method comprising: Triggering (S138) a random access (RA) procedure; selecting (S140) a first beam for the RA process, the selected first beam being associated with a two-step RA configuration, a characteristic of the selected first beam being determined to satisfy a predefined threshold; as well as performing (S142) the RA procedure associated with the two-step RA configuration using the selected first beam, The method further comprises: determining that a step of the two-step RA procedure has failed by receiving a fallback random access response RAR; as well as In response to determining that a step of the two-step RA process has failed, performing one of the following: retransmitting the uplink shared channel portion of message A msgA as an uplink shared channel message in a four-step RA procedure; and The two-step RA process is reattempted at least in part by performing beam reselection.

14. The method of claim 13, further comprising: Receive system information; as well as A determination is made based at least on the system information whether the selected first beam is associated with the two-step RA configuration, the two-step RA configuration corresponding to a mapping of the selected first beam to a physical uplink shared channel (PUSCH) configuration.

15. The method according to any one of claims 13 to 14, wherein: The selected first beam is selected from a plurality of beams, a subset of the plurality of beams being associated with the two-step RA configuration.

16. The method of claim 15, wherein: The subset of the plurality of beams is one of: a subset of synchronization signal block, SSB, beams and a set of channel state information reference signal, CSI-RS, beams.

17. The method of claim 16, wherein: The subset of SSB beams is associated with contention-free RA resources for contention-free RA.

18. The method according to any one of claims 16 to 17, wherein: At least one other beam of the plurality of beams is not associated with the two-step RA configuration.

19. The method of claim 17, wherein: At least one of the subset of beams is associated with a contention-based RA, and the contention-free RA takes precedence over the contention-based RA.

20. The method of any one of claims 13 to 19, wherein: The characteristic of the selected first beam is a channel quality, and the predefined threshold is a channel quality threshold.

21. The method of claim 13, further comprising determining that the step of the two-step RA process has failed based on one of: lack of response to the msgA; A random access response RAR message including backoff information is received; and A message B msgB is received comprising first information indicating that said step of said two-step RA procedure has failed.

22. The method of claim 21, wherein: The back-off information includes an indication that the step of the two-step RA procedure has failed.

23. The method of claim 21, wherein: The first information is contention resolution information.

24. The method of claim 15, wherein: The retransmission is performed based on reselecting a beam from the plurality of beams, the reselecting comprising using a contention-free RA resource configured for one of a channel state information reference signal CSI-RS and a synchronization signal block SSB.

25. A network node (16) configured to communicate with a wireless device (22), the network node (16) comprising: A processing circuit (68), the processing circuit (68) being configured to: Associating a plurality of beams with a plurality of random access RA configurations, a first beam of the plurality of beams being associated with a two-step RA configuration; and performing an RA procedure using the first beam based on the two-step RA configuration associated with the first beam, wherein the processing circuit (68) is further configured to: Determine that the two-step RA process has failed; In response to determining that the two-step RA process has failed, performing one of the following: transmitting a fallback random access response RAR and receiving the transmitted uplink shared channel portion of the message AmsgA as an uplink shared channel message in a four-step RA procedure; and It is determined that a beam reselection has occurred, the beam reselection being associated with a reattempt to perform the two-step RA procedure.

26. The network node (16) of claim 25, wherein: The processing circuit is further configured to transmit system information, the system information indicating the plurality of RA configurations.

27. The network node (16) according to any one of claims 25-26, wherein: A subset of the plurality of beams is associated with the two-step RA configuration.

28. The network node (16) of claim 27, wherein: The subset of the plurality of beams is one of: a subset of synchronization signal block, SSB, beams and a set of channel state information reference signal, CSI-RS, beams.

29. The network node (16) according to any one of claims 27-28, wherein: The subset of SSB beams is associated with contention-free RA resources for contention-free RA.

30. The network node (16) of claim 29, wherein: At least one of the subset of beams is associated with a contention-based RA, and the contention-free RA takes precedence over the contention-based RA.

31. The network node (16) according to any one of claims 25 to 30, wherein: At least one other beam of the plurality of beams is not associated with the two-step RA configuration.

32. The network node (16) according to any one of claims 25 to 31, wherein: In response to determining that the two-step RA process has failed, the processing circuit (68) is further configured to perform one of the following: Transmitting a random access response RAR message including back-off information; and A message B msgB is transmitted comprising first information indicating that a step of the two-step RA procedure has failed.

33. The network node (16) of claim 32, wherein: The back-off information includes an indication that the step of the two-step RA procedure has failed.

34. The network node (16) according to any one of claims 32-33, wherein: The first information is contention resolution information.

35. A method implemented by a network node (16) configured to communicate with a wireless device (22), the method comprising: Associating a plurality of beams with a plurality of random access RA configurations (S144), a first beam of the plurality of beams being associated with a two-step RA configuration; as well as performing (S146) an RA procedure using the first beam based on the two-step RA configuration associated with the first beam, The method further comprises: Determine that the two-step RA process has failed; In response to determining that the two-step RA process has failed, performing one of the following: transmitting a fallback random access response RAR and receiving the transmitted uplink shared channel part of the message AmsgA as an uplink shared channel message in a four-step RA procedure; as well as It is determined that a beam reselection has occurred, the beam reselection being associated with a reattempt to perform the two-step RA procedure.

36. The method of claim 35, further comprising transmitting system information, the system information indicating the plurality of RA configurations.

37. The method of any one of claims 35-36, wherein: A subset of the plurality of beams is associated with the two-step RA configuration.

38. The method of claim 37, wherein: The subset of the plurality of beams is one of: a subset of synchronization signal block, SSB, beams and a set of channel state information reference signal, CSI-RS, beams.

39. The method of any one of claims 37-38, wherein: The subset of SSB beams is associated with contention-free RA resources for contention-free RA.

40. The method of claim 39, wherein: At least one of the subset of beams is associated with a contention-based RA, and the contention-free RA takes precedence over the contention-based RA.

41. The method of any one of claims 35 to 40, wherein: At least one other beam of the plurality of beams is not associated with the two-step RA configuration.

42. The method of any one of claims 35-41, in response to determining that the two-step RA process has failed, the method further comprising performing one of the following: Transmitting a random access response RAR message including back-off information; and A message B msgB is transmitted comprising first information indicating that a step of the two-step RA procedure has failed.

43. The method of claim 42, wherein: The back-off information includes an indication that the step of the two-step RA procedure has failed.

44. The method of any one of claims 42-43, wherein: The first information is contention resolution information.

45. A computer storage medium storing computer instructions which, when executed by a processor (70, 86), cause the processor (70, 86) to control and / or perform the method of any one of claims 13-24 and 35-44.

46. ​​A computer program product storing computer instructions which, when executed by a processor (70, 86), cause the processor (70, 86) to control and / or perform the method of any one of claims 13-24 and 35-44.