Random access channel adaptation techniques

Abstract

This disclosure relates generally to Random Access Channel (RACH) adaptation techniques. In some implementations, a User Equipment (UE) determines one or more resources to monitor for RACH adaptation indicators based on the UE's connectivity state and the UE's ability to support RACH adaptation. Therefore, the UE monitors one or more resources to obtain RACH adaptation indicators. In some implementations, the UE receives indications for one or more triggering conditions to achieve RACH adaptation, and enables RACH adaptation in response to determining that one or more triggering conditions are met.

Description

Cross-reference to related applications

[0001] This application claims the benefit of U.S. Provisional Patent Application No. 63 / 800,904, filed May 6, 2025, the entire disclosure of which is incorporated herein by reference for all purposes. Technical Field

[0002] This disclosure relates in general to wireless communications, and more specifically to adaptive random access channel (RACH) techniques. Background Technology

[0003] Wireless communication networks provide an integrated communication platform and telecommunications services to wireless user equipment. Example telecommunications services include telephone, data (e.g., voice, audio, video), messaging, and / or other services. Wireless communication networks have wireless access nodes that use one or more wireless network protocols, such as those described in various telecommunications standards issued by the European Telecommunications Standards Institute (ETSI) 3GPP program, to exchange wireless signals with wireless user equipment. Wireless communication networks use techniques such as Orthogonal Frequency Division Multiple Access (OFDMA), Multiple-Input Multiple-Output (MIMO), Advanced Channel Decoding, Massive MIMO, beamforming, and / or other features to facilitate mobile broadband services. Summary of the Invention

[0004] One aspect of this disclosure relates to a method comprising: determining one or more resources to monitor for RACH adaptation indicators based on the connectivity state of a user equipment (UE) and the UE's ability to support random access channel (RACH) adaptation; and monitoring one or more resources to obtain RACH adaptation indicators.

[0005] In some specific implementations, the connectivity status of a UE includes Radio Resource Control (RRC) connected status, RRC idle status, or RRC inactive status.

[0006] In some specific implementations, monitoring one or more resources includes monitoring at least one paging opportunity (PO) per paging cycle or per system information modification period while the UE is in RRC connected state to obtain paging messages with RACH adaptive indicators.

[0007] In some specific implementations, the method further includes receiving downlink control information (DCI) format 1_0 with a physical downlink control channel (PDCCH) command including a RACH adaptive indicator.

[0008] In some implementations, the method also includes overwriting the RACH resource activation or deactivation status indicated by the DCI associated with the Paging Radio Network Temporary Identifier (P-RNTI).

[0009] In some specific implementations, the method further includes receiving a first system information block (SIB1) having bits indicating whether semi-static RACH adaptation is enabled or disabled.

[0010] In some specific implementations, SIB1 reception occurs simultaneously with the UE being in RRC idle state.

[0011] In some specific implementations, SIB1 reception occurs while the UE is in an RRC inactive state.

[0012] In some specific implementations, semi-static RACH adaptation is enabled, and the method further includes discarding the RACH adaptation indicator from the paging DCI message when the bit is set to 1.

[0013] In some implementations, semi-static RACH adaptation is disabled and the method further includes monitoring paging DCI messages to obtain RACH adaptation indicators when the bit is set to 0.

[0014] In some implementations, semi-static RACH adaptation is enabled and the method further includes monitoring paging DCI messages to obtain the RACH adaptation indicator, regardless of whether the bit is set to 0 or 1.

[0015] In some implementations, the method further includes: identifying an unaligned activation or deactivation state between a semi-static RACH adaptive indicator and a dynamic RACH adaptive indicator in a paging DCI message; and overwriting the semi-static RACH adaptive indicator with a dynamic RACH adaptive indicator from the paging DCI message.

[0016] In some implementations, monitoring one or more resources includes monitoring the next Broadcast Control Channel (BCCH) timing after receiving a paging short message to obtain SIB1 updates.

[0017] In some implementations, monitoring one or more resources includes monitoring the current BCCH period after receiving a paging short message to obtain SIB1 updates when the bit indication semi-static RACH adaptation in SIB1 is enabled.

[0018] In some implementations, monitoring one or more resources includes monitoring the current BCCH period to obtain SIB1 updates after receiving a paging short message that enables immediate access to SIB1 updates.

[0019] In some implementations, monitoring one or more resources includes monitoring the next BCCH period to obtain SIB1 updates after receiving a paging short message that disables immediate access to SIB1 updates.

[0020] In some specific implementations, the method further includes receiving a first system information block (SIB1) while the UE is in an RRC connection state, the SIB1 including bits indicating whether semi-static RACH adaptation is enabled or disabled.

[0021] In some implementations, monitoring one or more resources includes monitoring at least one PO per BCCH modification period or per paging cycle to obtain SIB1 updates when the bit indication semi-static RACH adaptation in SIB1 is enabled.

[0022] In some specific implementations, the method further includes receiving a handover command having bits indicating whether RACH adaptation is enabled for the target cell.

[0023] In some specific implementations, the method also includes enabling RACH adaptation for the target cell during the handover period according to the handover command.

[0024] In some specific implementations, the method further includes receiving SIB1 via the target cell, which includes bits indicating whether RACH adaptation is enabled for the target cell.

[0025] In some specific implementations, the method also includes enabling RACH adaptation for the target cell based on bits in the handover command and bits in SIB1.

[0026] Another aspect of this disclosure relates to a method comprising: receiving an indication of one or more triggering conditions to implement RACH adaptation; and enabling RACH adaptation for a UE in response to determining that one or more triggering conditions are met.

[0027] In some implementations, receiving an indication of one or more triggering conditions includes receiving an SIB indicating a unified access control (UAC) threshold for enabling RACH adaptation.

[0028] In some specific implementations, enabling RACH adaptation for a UE includes enabling RACH adaptation in response to determining that the UE's UAC access probability meets a UAC threshold indicated by the SIB.

[0029] In some specific implementations, a set of UAC thresholds is configured for RACH adaptation, with each UAC threshold corresponding to a specific combination of access class and access identity.

[0030] In some specific implementations, a UAC threshold is configured for all access categories and access identities.

[0031] In some specific implementations, the SIB further indicates the probability to be used to determine whether to activate RACH adaptation.

[0032] In some specific implementations, determining whether one or more triggering conditions are met includes determining whether paging adaptation is enabled for the UE.

[0033] In some specific implementations, RACH adaptation is disabled for the UE when paging adaptation is disabled.

[0034] In some specific implementations, enabling RACH adaptation includes enabling RACH adaptation during the paging frame (PF) derived from the UE's paging configuration.

[0035] In some implementations, RACH adaptation is disabled in frames other than the PF derived from the UE's paging configuration.

[0036] In some specific implementations, RACH adaptation is enabled in several frames immediately following the PF derived from the UE's paging configuration, and the number of frames is configured by the SIB.

[0037] In some specific implementations, determining whether one or more triggering conditions are met includes determining whether to enable Synchronization Signal Block (SSB) or On-Demand SSB (OD-SSB) adaptation for the UE.

[0038] In some specific implementations, RACH adaptation is disabled when SSB or OD-SSB adaptation is disabled for the UE.

[0039] In some specific implementations, determining whether one or more triggering conditions are met includes determining that the SSB period is less than a threshold configured in the network.

[0040] In some specific implementations, RACH adaptation is disabled when the SSB period is greater than or equal to a threshold.

[0041] In some specific implementations, determining whether one or more triggering conditions are met includes determining that the number of RACH preamble retransmissions performed by the UE is greater than a threshold configured by the network.

[0042] In some specific implementations, the method also includes using a set of additional RACH resources configured for RACH adaptation when one or more triggering conditions are met.

[0043] In some specific implementations, the UE cannot switch back to the default RACH resource from the set of additional RACH resources after switching from the default RACH resource to the additional RACH resource.

[0044] In some specific implementations, the method also includes using the default RACH resource in subsequent RACH procedures.

[0045] In some implementations, receiving an indication for one or more triggering conditions includes receiving a Media Access Control (MAC) control element (MAC-CE) that triggers RACH adaptation and OD-SSB adaptation.

[0046] In some specific implementations, the method also includes disabling RACH adaptation after OD-SSB adaptation is disabled.

[0047] In some specific implementations, OD-SSB adaptation is either deactivated by receiving a second MAC-CE or after the threshold number of SSB adaptation opportunities has passed.

[0048] In some specific implementations, receiving indications for one or more triggering conditions includes receiving group common DCI messages that trigger RACH adaptation and SSB adaptation.

[0049] In some specific implementations, the method further includes disabling RACH adaptation after receiving a second set of public DCI messages to disable SSB adaptation.

[0050] Another aspect of this disclosure relates to a method comprising: determining one or more resources to be used for transmitting a RACH adaptation indicator based on the connectivity state of a UE and the UE's ability to support RACH adaptation; and transmitting a message including the RACH adaptation indicator via the one or more resources.

[0051] In some specific implementations, the connectivity status of a UE includes RRC connected status, RRC idle status, or RRC inactive status.

[0052] In some specific implementations, the method further includes sending a DCI format 1_0 with a PDCCH command including a RACH adaptive indicator.

[0053] In some implementations, the method also includes overwriting the RACH resource activation or deactivation status indicated by the DCI associated with the P-RNTI.

[0054] In some specific implementations, the method further includes sending SIB1 with bits indicating whether semi-static RACH adaptation is enabled or disabled.

[0055] In some specific implementations, SIB1 transmission occurs simultaneously with the UE being in RRC idle state.

[0056] In some specific implementations, SIB1 transmission occurs simultaneously with the UE being in an RRC inactive state.

[0057] In some implementations, sending messages via one or more resources includes sending an SIB1 update at the next BCCH timing after sending a paging short message.

[0058] In some implementations, sending messages via one or more resources includes sending SIB1 updates during the current BCCH timing when the bit indication semi-static RACH adaptation in SIB1 is enabled.

[0059] In some implementations, sending messages via one or more resources includes sending the SIB1 update at the current BCCH timing after sending a paging short message that enables immediate access to SIB1 updates.

[0060] In some implementations, sending messages via one or more resources includes sending the SIB1 update at the next BCCH timing after sending a paging short message disabling immediate access to SIB1 updates.

[0061] In some specific implementations, the method further includes sending SIB1 while the UE is in the RRC connected state, the SIB1 including bits indicating whether semi-static RACH adaptation is enabled or disabled.

[0062] In some specific implementations, the method further includes sending a handover command with bits indicating whether RACH adaptation is enabled for the target cell.

[0063] Another aspect of this disclosure relates to a method comprising: configuring one or more triggering conditions to enable RACH adaptation; and enabling RACH adaptation for a UE in response to determining that one or more triggering conditions are met.

[0064] In some implementations, configuring one or more triggering conditions includes sending an SIB indicating a UAC threshold for enabling RACH adaptation.

[0065] In some specific implementations, a set of UAC thresholds is configured for RACH adaptation, with each UAC threshold corresponding to a specific combination of access class and access identity.

[0066] In some specific implementations, a UAC threshold is configured for all access categories and access identities.

[0067] In some specific implementations, the SIB further indicates the probability to be used to determine whether to activate RACH adaptation.

[0068] In some specific implementations, determining whether one or more triggering conditions are met includes determining whether paging adaptation is enabled for the UE.

[0069] In some specific implementations, RACH adaptation is disabled for the UE when paging adaptation is disabled.

[0070] In some specific implementations, enabling RACH adaptation includes enabling RACH adaptation during the PF associated with the UE's paging configuration.

[0071] In some implementations, RACH adaptation is disabled in frames other than the PF associated with the UE's paging configuration.

[0072] In some specific implementations, RACH adaptation is enabled in several frames immediately following the PF associated with the UE's paging configuration, and the number of frames is configured by the SIB.

[0073] In some specific implementations, determining whether one or more triggering conditions are met includes determining whether SSB or OD-SSB adaptation is enabled for the UE.

[0074] In some specific implementations, RACH adaptation is disabled when SSB or OD-SSB adaptation is disabled for the UE.

[0075] In some specific implementations, determining whether one or more triggering conditions are met includes determining that the SSB period is less than a threshold configured in the network.

[0076] In some specific implementations, RACH adaptation is disabled when the SSB period is greater than or equal to a threshold.

[0077] In some specific implementations, determining whether one or more triggering conditions are met includes determining that the number of RACH preamble retransmissions performed by the UE is greater than a threshold configured by the network.

[0078] In some specific implementations, configuring one or more triggering conditions includes sending MAC-CE that triggers RACH adaptation and OD-SSB adaptation.

[0079] In some specific implementations, the method also includes disabling RACH adaptation after OD-SSB adaptation is disabled.

[0080] In some specific implementations, OD-SSB adaptation is deactivated either through a second MAC-CE or after the threshold number of SSB adaptation opportunities has passed.

[0081] In some specific implementations, configuring one or more triggering conditions includes sending a group common DCI message that triggers RACH adaptation and SSB adaptation.

[0082] In some specific implementations, the method further includes disabling RACH adaptation after sending a second set of public DCI messages to disable SSB adaptation.

[0083] Another aspect of this disclosure relates to an apparatus comprising: one or more processors; and a memory storing instructions that, when executed, cause the one or more processors to perform any of the aforementioned operations.

[0084] Another aspect of this disclosure relates to a baseband processor configured to perform any of the operations described above.

[0085] Details of one or more embodiments of these systems and methods are set forth in the following figures and description. Other features, objects, and advantages of these systems and methods will be apparent from the specification, figures, and claims. Attached Figure Description

[0086] Figure 1 Examples of wireless networks based on some specific implementations are illustrated.

[0087] Figure 2 An example Physical Random Access Channel (PRACH) resource diagram is shown according to some specific implementations.

[0088] Figure 3 Examples of unified access control (UAC) schemes based on some specific implementations are illustrated.

[0089] Figure 4 Two example paging adaptive schemes based on some specific implementations are illustrated.

[0090] Figure 5 Two example on-demand synchronization signal block (OD-SSB) transmission schemes are illustrated based on some specific implementations.

[0091] Figures 6 to 9 A flowchart illustrating an example method for adaptive random access channel (RACH) according to some specific implementations is shown.

[0092] Figure 10 Example user equipment (UE) based on some specific implementations are illustrated.

[0093] Figure 11 Example access nodes are shown according to some specific implementations. Detailed Implementation

[0094] This disclosure relates overall to the adaptation of common downlink and uplink transmissions to support 3GPP New Radio (NR) Network Energy Efficiency (NES) objectives, such as On-Demand Synchronization Signal Block (OD-SSB) transmissions for connected-mode user equipment (UEs). SSB transmissions, Physical Random Access Channel (PRACH) opportunities, and paging opportunities (POs) are typically configured with fixed periods and spatial allocations. Such static configurations may not fully account for dynamic changes in cell load or energy efficiency objectives. Adaptation of SSB periods, PRACH resource allocation (both temporally and spatially), and time-domain constraints on POs can improve NES performance without increasing paging latency or negatively impacting legacy UEs.

[0095] In conventional networks, only fully dynamic triggering, such as paging downlink control information (DCI), is allowed to initiate RACH adaptation. This process typically involves transmitting common group DCI, which can increase signaling overhead and latency. For connected UEs, semi-static adaptation via System Information Block 1 (SIB1) is currently not supported. There is also uncertainty as to when connected UEs should monitor SIB1 updates, and SIB1 can only be updated during the next Broadcast Channel (BCCH) modification period (which may introduce latency). Furthermore, OD-SSB transmission and paging adaptation can increase RACH collisions during high network traffic handover or periods. These issues can lead to lower energy savings, more collisions, and unpredictable RACH performance.

[0096] The RACH adaptation framework described herein specifies when a UE should monitor both dynamic signaling (e.g., DCI format 1_0) and semi-static signaling (e.g., SIB1 update) to support both dynamic and semi-static RACH adaptation. In some implementations, a connected UE may be configured to monitor a single PO per paging cycle to obtain a paging DCI. The DCI message may include a 1-bit indication of additional PRACH resource availability. In other implementations, a new bit in SIB1 may enable or disable semi-static RACH adaptation for idle / inactive UEs, thereby enabling the UE to obtain an SIB1 update in the current BCCH period after a paging short message. Some aspects of this disclosure relate to conditional triggering of RACH adaptation without explicit signaling (e.g., access probability thresholds derived from the Unified Access Control (UAC) in the SIB, paging configuration parameters, OD-SSB or SSB cycle thresholds, and / or preamble retransmission counts). Joint signaling indicators—such as MAC-CE or group common DCI controlling OD-SSB or SSB adaptation—may simultaneously enable or disable RACH adaptation.

[0097] According to the RACH adaptive technique described herein, when network load increases, the network can provide additional PRACH resources to 3GPP Release 19 (Rel-19) UEs (e.g., UEs supporting NES functionality). To do this, the network can send a DCI 1_0 scrambled with a Paging Radio Network Temporary Identifier (P-RNTI), which includes the effective duration and a 1-bit flag indicating the activation of the secondary PRACH resource pool according to a non-uniform spatial mapping relative to the SSB beam. Therefore, the connected UE can monitor a PO per paging cycle, decode the 1-bit flag in the Physical Downlink Control Channel (PDCCH) command, and select to use these additional PRACH resources for initial access. If the network later broadcasts a deactivation indication (via the same DCI or the expiration of an effective timer), the UE can revert to the traditional PRACH configuration.

[0098] The RACH adaptation technique described herein reduces signaling latency because the UE knows precisely when to monitor RACH adaptation indicators. The described framework also reduces signaling overhead because group common DCI messages can be reused or minimized. Additionally, this disclosure helps ensure alignment between the UE and the network in RACH resource usage, which reduces the frequency of RACH collisions. The described technique maintains / preserves legacy UE performance and does not increase paging latency or disrupt UEs that do not support NES features. Furthermore, conditional triggering via UAC and SIB thresholds allows the network to implicitly adapt RACH behavior in response to real-time load fluctuations, improving energy efficiency and system efficiency without additional signaling overhead.

[0099] Figure 1 An example wireless network 100 according to some specific implementation is illustrated. The wireless network 100 includes a UE 102 and a base station 104 connected via one or more channels 106A, 106B across an air interface 108. The UE 102 and the base station 104 communicate using a system that supports control for managing the UE 102's access to the network via the base station 104.

[0100] In some implementations, wireless network 100 is, for example, a standalone (SA) network incorporating fifth-generation (5G) NR. In other implementations, wireless network 100 is a non-standalone (NSA) network incorporating Long Term Evolution (LTE) and 5G NR. In these implementations, wireless network 100 may be an Evolved Universal Terrestrial Radio Access (E-UTRA) NR Dual Connectivity (EN-DC) network or an NR-EUTRA Dual Connectivity (NE-DC) network. Furthermore, it is possible to implement wireless networks using one or more other types of communication standards, including future 3GPP systems (e.g., sixth-generation "6G"), IEEE 802.11 technologies, etc. While this document uses terminology generally associated with 5G NR to describe aspects, the aspects of this disclosure can be applied to other systems, such as systems beyond 5G (e.g., 6G).

[0101] In wireless network 100, UE 102 and any other UE may be, for example, a laptop computer, smartphone, tablet computer, machine-type device (such as a smart meter or specialized device for healthcare), intelligent transportation system, or any other wireless device. In network 100, base station 104 provides UE 102 with network connectivity to a wider network (not shown). This connectivity is provided to UE 102 via air interface 108 within the base station service area provided by base station 104. In some implementations, this wider network may be a wide area network operated by a cellular network provider, or it may be the Internet. Each base station service area associated with base station 104 is supported by one or more antennas integrated with base station 104. The service area may be divided into several sectors associated with one or more specific antennas. Such sectors may be physically associated with one or more fixed antennas, or may be assigned to a physical area having one or more tunable antennas or antenna configurations that can be adjusted during beamforming to direct signals to a specific sector.

[0102] UE 102 includes control circuitry 110 coupled to transmitting circuitry 112 and receiving circuitry 114. Transmitting circuitry 112 and receiving circuitry 114 may each be coupled to one or more antennas. Control circuitry 110 may include dedicated circuitry, baseband circuitry, or any combination thereof. Transmitting circuitry 112 and receiving circuitry 114 may be adapted to transmit and receive data respectively, and may include radio frequency (RF) circuitry and / or front-end module (FEM) circuitry.

[0103] In various specific implementations, aspects of the transmitting circuit 112, the receiving circuit 114, and / or the control circuit 110 can be integrated in various ways to implement the operations described herein. The control circuit 110 can be adapted to or configured to perform various operations, such as the various UE-related operations described elsewhere in this disclosure. For example, the control circuit 110 can determine whether to enable or disable RACH adaptation based on indications in SIB1.

[0104] Transmitting circuit 112 can perform various operations described herein. For example, transmitting circuit 112 can use additional PRACH resources activated based on network conditions to transmit random access messages. Additionally, transmitting circuit 112 can use multiplexed uplink physical channels for transmission. The uplink physical channels can be multiplexed, for example, according to time division multiplexing (TDM) or frequency division multiplexing (FDM), and in some specific implementations, carrier aggregation (CA). Transmitting circuit 112 can be configured to receive block data from control circuit 110 for transmission on air interface 108.

[0105] Receiver circuit 114 can perform various operations described herein. For example, receiver circuit 114 can receive SIB1 with RACH adaptive indication for a connected UE. Additionally, receiver circuit 114 can receive multiplexed downlink physical channels from air interface 108 and relay these physical channels to control circuit 110. The downlink physical channels can be multiplexed, for example, according to TDM or FDM, such as together with carrier aggregation. Transmitter circuit 112 and receiver circuit 114 can respectively transmit and receive control data and content data (e.g., messages, images, video) structured within data blocks carried by the physical channels.

[0106] Figure 1 Base station 104 is also illustrated. In some implementations, base station 104 may be a 5G radio access network (RAN), a next-generation RAN, an E-UTRAN, a non-terrestrial cell, or a traditional RAN (such as UTRAN). As used herein, the term "5GRAN" and the like may refer to base station 104 operating in an NR wireless network 100, and the term "E-UTRAN" and the like may refer to base station 104 operating in an LTE wireless network 100. UE 102 utilizes connections (or channels) 106A and 106B, each connection including a physical communication interface or layer.

[0107] The base station 104 circuitry may include control circuitry 116 coupled (directly or indirectly) to transmitting circuitry 118 and / or receiving circuitry 120. Transmitting circuitry 118 and receiving circuitry 120 may each be coupled (directly or indirectly) to one or more antennas, which may be used for communication via air interface 108. Transmitting circuitry 118 and receiving circuitry 120 may be adapted to transmit and receive data, respectively, to any UE connected to base station 104. Receiving circuitry 120 may receive uplink physical channel transmissions from one or more UEs, including UE 102.

[0108] exist Figure 1 In this embodiment, one or more channels 106A, 106B are exemplified as air interfaces for implementing communication coupling and may conform to cellular communication protocols such as LTE, LTE-A (LTE-Advanced), LTE-based Unlicensed Spectrum Access (LTE-U), NR, NR-based Unlicensed Spectrum Access (NR-U), and / or any other communication protocol. In some implementations, UE 102 may directly exchange communication data via the ProSe interface. The ProSe interface may alternatively be referred to as a sidelink (SL) interface and may include one or more logical channels, including but not limited to the Physical Sidelink Control Channel (PSCCH), Physical Sidelink Discovery Channel (PSDCH), or Physical Sidelink Broadcast Channel (PSBCH).

[0109] This disclosure relates in general to UE monitoring behavior and conditional triggering for dynamic and semi-static RACH adaptation. Some aspects of this disclosure relate to NES objectives for NR, such as OD-SSB SCell operation for connected-mode UEs. Adaptation of common signaling / channel transmission can improve NES. This includes adaptation of SSB in the time domain (e.g., adaptation period), adaptation of PRACH in the time domain, adaptation of PRACH in the spatial domain (e.g., non-uniform PRACH resources per SSB), adaptation of PO (e.g., limiting PO in the time domain), etc. This adaptation will not increase paging latency or negatively affect legacy UE operation. For NES adaptation of SSB, the configuration or adaptation of longer periods for SSB / SIB1 and / or uplink random access opportunities may involve signaling mechanisms for informing UE 102 how the configuration or adaptation of common signaling / channel may affect system information acquisition, initial access, RRM / RLM / BM measurements, and the performance of legacy UEs and other UEs that do not support the techniques described herein.

[0110] Two sets of PRACH resources can be used in different scenarios. An additional set of PRACH resources can be used to dynamically adapt to changes in NES cell load. Legacy UEs can be configured to use legacy PRACH resources with sparse periods. When cell load is high, an additional set (such as...) can be dynamically provided for Rel-19 UEs. Figure 2 (As shown). In existing networks, only dynamically triggered (e.g., DCI for paging operations) is permitted for RACH adaptation (e.g., semi-static RACH adaptation is not allowed). For DCI-based adaptation of additional PRACH resources, DCI 1_0 with P-RNTI indicates the availability information of the additional PRACH resources from the reference point and within the effective duration. The effective duration of availability can be configured by higher-layer signaling or predefined. Details such as the location of the reference point, the value / granularity of the effective duration, and whether DCI can be used to explicitly deactivate additional PRACH resources are currently under discussion.

[0111] When DCI signaling triggers RACH adaptation, the paging DCI includes a valid duration. For the PRACH to be adapted in the time domain for a connected-mode UE (such as UE 102), a 1-bit field in DCI 1_0 with C-RNTI is used to trigger the PRACH (e.g., a PDCCH command) to indicate whether additional PRACH resources are available for the triggered PRACH. Details such as UE behavior when additional PRACH resources are indicated (e.g., applicable resources for the PRACH mask index) and the process of reusing existing bits for the 1-bit indication are currently under discussion.

[0112] User-Agent Control (UAC) was introduced in 3GPP Release 15. Using UAC, NG-RAN broadcasts prohibition control information (e.g., probabilities) associated with access class and access identity. Figure 3 An example UAC scheme is shown. For network sharing, prohibition control information can be set individually for each PLMN. UE 102 determines whether an access attempt is authorized to proceed based on the prohibition information broadcast to the selected PLMN, as well as the selected access category and access identity. For example, UE 102 can flip a coin with an indicated probability. Additional details regarding access identity and access category are specified in sections 6.22.2.2 and 6.22.2.3 of 3GPP TS 22.261.

[0113] Several paging adaptive schemes are supported in Rel-19 NES. Figure 4The paging adaptation schemes shown involve bundling paging frames (PFs), extending the value of N to have increased intervals between PFs (e.g., T / 64, T / 128), and compensating for the reduction in the number of PFs by increasing the number of POs per PF. This effectively concentrates PF / PFs to allow the gNB to spend more time in sleep mode. However, this method can lead to RACH collisions. OD-SSB is another Rel-19 NES feature. Figure 5 The example OD-SSB transmission scheme is described. The purpose of OD-SSB is to transmit an additional SSB to assist UE measurements during HO and reduce SCell activation latency. However, OD-SSB transmission may also cause RACH collisions during HO.

[0114] There are some issues regarding how connected UEs monitor dynamic signaling (such as DCI). In legacy systems, the timing for idle / inactive UEs to monitor paging messages is explicitly defined. However, this is not defined for connected UEs. In legacy systems, connected UEs can monitor any Point of Purchase (PO) to obtain System Information Change Indications and / or Public Alarm System (PWS) notifications. Additionally, there is the issue of how idle / inactive UEs monitor semi-static RACH adaptation via SIB updates. Semi-static RACH adaptation via SIB is useful during the Open Host (HO) period. DCI signaling is not applicable during the HO period. In legacy systems, SIB1 can only be updated after the next BCCH modification, which introduces latency. There is also some uncertainty regarding when connected UEs monitor semi-static RACH adaptation via SIB updates. In legacy systems, there are no constraints on when connected UEs receive SIB1 updates.

[0115] If only dynamically triggered (e.g., paging DCI) is allowed for RACH adaptation, this involves transmitting group common DCI, which can increase signaling overhead and latency. Group common DCI may be unreliable and typically does not provide feedback for group common DCI. If UE 102 cannot decode the group common DCI, UE 102 and the network (e.g., base station 104) may not be aligned on which RACH resources to use, potentially leading to RACH failure. A valid duration can be introduced for group common DCI. However, if UE 102 misses a group common DCI, UE 102 will not know when the valid duration has expired.

[0116] Some aspects of this disclosure relate to specifying when UE 102 should monitor dynamic / semi-static signaling to enable RACH adaptation. For example, a connected UE can be configured to monitor dynamic signaling (such as paging DCI) at specific times. Similarly, an idle / inactive UE can be configured to monitor semi-static signaling (for SIB1 updates) at specific times. This reduces the signaling latency required for the UE to enable RACH adaptation. A connected UE can also be configured to monitor semi-static signaling (for SIB1 updates) at specific times.

[0117] According to the framework described herein, if a connected UE is configured with RACH adaptation, the UE will exhibit the same monitoring behavior as an idle / inactive UE. For example, UE 102 should monitor at least one PO per paging cycle to obtain a paging message with RACH adaptation indication, according to the PF / PO formula defined in 3GPP TS 38.304. Alternatively, UE 102 may monitor any PO to obtain a paging message with RACH adaptation indication (as a conventional connected UE does), but UE 102 may be configured to monitor at least one PO per system information modification period or BCCH modification period.

[0118] Alternatively, UE 102 may monitor any PO to obtain paging messages with RACH adaptive indication (as is done by a conventional connected UE), but UE 102 may be configured to monitor at least one PO per paging cycle. In some specific implementations, UE 102 does not monitor DCIs addressed by P-RNTI, but UE 102 monitors DCI 1-0 for PDCCH commands with RACH adaptive indication. If DCI 1-0 for a PDCCH command with RACH adaptive indication is received, the indication may override the additional RACH resource activation / deactivation state indicated by the DCI addressed by P-RNTI.

[0119] For idle / inactive UEs, a bit can be added to SIB1 to enable / disable semi-static RACH adaptation. For example, when this bit is set to 1, semi-static RACH adaptation is enabled from the BCCH modification period when UE 102 decodes the indication, and UE 102 ignores paging DCIs used for RACH adaptation. When this bit is set to 0, semi-static RACH adaptation is disabled from the BCCH modification period when UE 102 decodes the indication, and UE 102 does not monitor paging DCIs used for RACH adaptation. Alternatively, when this bit is set to 1, semi-static RACH adaptation is enabled from the BCCH modification period when UE 102 decodes the indication, but UE 102 continues to monitor paging DCIs used for RACH adaptation. When this bit is set to 0, semi-static RACH adaptation is disabled from the BCCH modification period when UE 102 decodes the indication, and UE 102 continues to monitor paging DCIs used for RACH adaptation. If UE 102 identifies a misalignment enabled / disabled state of RACH adaptation between the indication in SIB1 and the paging DCI, the UE prioritizes the indication in the paging DCI to determine whether to enable RACH adaptation. The indication in SIB1 can be ignored. In some specific implementations, UE 102 monitors the next BCCH after receiving a paging SMS to obtain SIB1 updates. For UEs supporting RACH adaptation, if the indication in SIB1 is enabled, UE 102 can monitor SIB1 updates during the current BCCH period after receiving a paging SMS. No modification to the paging SMS payload is required. New bits can also be added to the paging SMS. When this bit is set to a specific value, UE 102 immediately obtains the SIB1 update. For UEs supporting RACH adaptation, if the indication in SIB1 is enabled, UE 102 can monitor SIB1 updates during the current BCCH after receiving a paging SMS with the new bit enabled. Upon receiving a paging SMS with the new bit disabled, UE 102 can monitor SIB1 updates during the next BCCH.

[0120] A new bit for connecting UEs can also be added to SIB1. For connected UEs supporting RACH adaptation, if the indication in SIB1 is enabled, UE 102 will monitor at least one PO for SIB1 updates every BCCH modification period. Alternatively, UE 102 can be configured to monitor at least one PO for SIB1 updates every paging cycle. In some implementations, a bit can be added to the HO command to indicate that RACH adaptation for the target cell is enabled. For connected UEs supporting RACH adaptation, if this bit is enabled, UE 102 will apply RACH adaptation for the target cell during the HO period, regardless of the new bit for the target cell in SIB1. Alternatively, if the new bit in SIB1 for the target cell is also enabled, UE 102 may apply RACH adaptation for the target cell during the HO period. Otherwise, UE 102 will not apply RACH adaptation.

[0121] For conditional triggering of RACH adaptation, UE 102 can consider additional RACH resources as activated to trigger RACH adaptation when specific conditions are met. According to the framework described herein, RACH adaptation, which is typically triggered under high system load, can be implemented implicitly without signaling. When UE 102 determines that the system load is high (e.g., based on UAC parameters), the method described herein can help distinguish UEs of different access classes and / or access identities. When paging adaptation is enabled, RACH collisions can occur as the PF / PO ratio increases with paging adaptation. When OD-SSB is triggered and the number of retransmissions exceeds a given threshold, the network can configure a signaling indication to simultaneously trigger RACH adaptation and other NES features (such as OD-SSB).

[0122] For conditional triggering via UAC, the access probability of UAC for each access class and access identity reflects network traffic / load status. Within the SIB, one or more UAC access probability thresholds can be defined. After receiving the SIB data, the UE102 compares the applied UAC access probability with the specified thresholds to determine whether to activate RACH adaptation. In some examples, multiple access probability thresholds are configured, and each threshold corresponds to a [access class, access identity] pair. In other examples, a single threshold is configured for all combinations of [access class, access identity].

[0123] In some cases, another probability indication can be added to the SIB. If one or more of the conditions discussed above are met, UE 102 can determine whether to activate RACH adaptation by flipping a coin based on the configured probability. This method can help distinguish UEs with different access categories and access identities (e.g., when multiple access probability thresholds are configured for different pairs of access categories and access identities).

[0124] For conditional triggering of paging adaptation via the SIB, the network can configure RACH adaptation to be implicitly triggered when paging adaptation is enabled. RACH adaptation can be implicitly disabled when paging adaptation is disabled. In the SIB, the network can configure RACH adaptation to be implicitly triggered during a PF derived from the Rel-19 paging configuration. (i) In frames other than the PF derived from the Rel-19 paging configuration, or (ii) when paging adaptation is disabled, RACH adaptation can be implicitly disabled. In the SIB, the network can configure RACH adaptation to be triggered during frames derived from the Rel-19 paging configuration (such as the PF and subsequent frames). X Frame, in which X (Configured by SIB) is implicitly triggered during (i) except when located in PF+ X In frames other than those in the frame or (ii) when paging adaptation is disabled, RACH adaptation may be implicitly disabled.

[0125] For conditional triggering via OD-SSB or SSB adaptation, the network can (in the SIB) configure RACH adaptation to be implicitly triggered when OD-SSB or SSB adaptation is triggered. RACH adaptation can be implicitly disabled when OD-SSB or SSB adaptation is disabled. Alternatively, the network can (in the SIB) configure a threshold SSB period. RACH adaptation can be implicitly triggered when the specified SSB period is below the threshold. RACH adaptation can be implicitly disabled when the SSB period is greater than or equal to the threshold.

[0126] For conditional triggering via a preamble retransmission count, a specific preamble retransmission count in the RACH can indicate network overload. In the SIB, the network can configure a threshold preamble retransmission count. When the indicated preamble retransmission count exceeds this threshold, RACH adaptation can be implicitly triggered. In some examples, UE 102 starts with traditional RACH resources and uses additional RACH resources for RACH adaptation when the condition is met. After switching to additional RACH resources, UE 102 may not switch back to traditional RACH resources. When another RACH procedure is triggered, UE 102 starts with traditional RACH resources.

[0127] Some aspects of this disclosure relate to conditional triggering via a joint signaling indicator. In Rel-19 NES, OD-SSB, SSB adaptation, and RACH adaptation can be used in system overload scenarios. In some specific implementations, the network can be configured with a signaling to simultaneously trigger RACH adaptation and other NES features (e.g., OD-SSB). RACH adaptation can be implicitly triggered when a MAC-CE triggering OD-SSB transmission is received. RACH adaptation can be implicitly disabled when OD-SSB transmission is terminated, including upon receiving a disable MAC-CE or after a configured M SSB transmission timing. Additionally or alternatively, RACH adaptation can be implicitly triggered when a group common DCI triggering SSB adaptation is received. RACH adaptation can be implicitly disabled when a group common DCI stopping SSB adaptation is received.

[0128] Figure 2 Example PRACH resource diagram 200 is illustrated according to some specific implementations. PRACH resource diagram 200 shows two sets of random access opportunities available to a UE (such as UE 102) in a time-domain sequence transmitted by the SSB. Figure 2 Within this, there are two consecutive SSB beams associated with the corresponding random access timing. As described herein, conventional PRACH resource 202 is configured with a relatively sparse periodicity and uniform spatial mapping for conventional UEs. According to various aspects of this disclosure, additional PRACH resource 204 can be dynamically activated for Rel-19 UEs when network load conditions require increased RACH capacity.

[0129] For reference Figure 1 As described, base station 104 can transmit SSBs at fixed intervals to achieve initial access and measurement reporting. At each SSB transmission timing, base station 104 can provide a supplementary set of PRACH timings (e.g., additional PRACH resources 204) to augment traditional PRACH resources 202 without altering the timing or spatial pattern of the original SSB beam. Resource diagram 200 illustrates how PRACH resource allocation in the time domain can be semi-statically or dynamically adapted to support NR NES objectives. When network traffic is detected as high (e.g., based on UAC thresholds or paging configuration parameters), base station 104 can transmit a paging DCI 1_0 (scrambled with P-RNTI) with a 1-bit flag and a valid duration. A Rel-19 UE (such as UE 102) that decodes this flag then considers the additional PRACH resources 204 to be active within the timer's duration, which increases random access capacity without affecting traditional UE behavior on traditional PRACH resources 202.

[0130] In some examples, a connected Rel-19 UE can be configured to monitor a single PO per cycle. Upon receiving a PDCCH command carrying DCI 1_0 with an activation flag set, the UE can consider Additional PRACH resource 204 as available for RACH transmission. If the Rel-19 UE initiates a random access procedure during the SSB period, it can select one of the Additional PRACH resources 204 to reduce the probability of signal collisions with other legacy UEs. If the network subsequently sends a deactivation indication or the DCI validity timer expires, the UE can revert to using legacy PRACH resource 202 for subsequent access attempts.

[0131] Figure 3 An example UAC scheme 300 according to some specific implementation is illustrated. UAC scheme 300 is a mechanism by which UE 102 can determine whether to continue RACH procedures under varying load conditions. In the radio network 100, base station 104 and associated core network (CN) functions broadcast access control parameters to all UEs. Figure 3 The broadcast and decision-making process is abstracted into two logical protocol layers: the non-access spectrum (NAS) 306, which handles higher-level mobility and session management functions, and the access spectrum (AS) 308, which performs lower-level procedures necessary for initiating uplink transmissions. Figure 3 This illustrates how UAC can be used as a conditional trigger within the broader RACH adaptive framework described above.

[0132] UAC scheme 300 begins with base station 104 broadcasting a prohibition message 304 in SIB1 or via dedicated signaling. The prohibition message 304 is provided by combining the access class, access identity, establishment reason, and the probability governing whether a given access attempt will be permitted. Upon receiving this message, NAS 306 forwards the relevant parameters to AS 308. In some cases, AS uses an Access Class Prohibition (ACB) algorithm to generate an ACB result by drawing random numbers against the received prohibition probabilities (e.g., "coin flip"). The ACB result returned by AS 308 indicates whether UE 102 is currently prohibited from transmitting.

[0133] If the ACB result indicates that the UE is not prohibited, AS 308 can proceed with access attempt 302, thereby initiating a PRACH transmission for UE 102. In some specific implementations, UE 102 will select one of the traditional PRACH resources 202, or, if dynamically triggered and continuously active, one of the supplementary PRACH resources 204 for this access attempt 302. The output from AS 308 thus triggers a contention-based random access procedure in the RAN.

[0134] In response to access attempt 302, base station 104 may respond with a random access response (RAR) or a prohibition message, and NAS 306 will again interpret any new prohibition information carried in subsequent SIB updates 304. Figure 3 UAC scheme 300 represents a possible conditional triggering for semi-static RACH adaptation: by differentiating UEs based on access category or access identity, and by applying a per-category prohibition threshold, the network can implicitly throttle access during periods of high load without relying solely on group common DCI. Therefore, UAC scheme 300 enables the network to activate or deactivate additional PRACH resources in response to real-time network conditions.

[0135] Figure 4 Example paging adaptation schemes 400 and 401 are illustrated according to some specific implementations. Paging adaptation scheme 400 illustrates PF bundling, where the first four paging frames (PF1-PF4) are bundled into a single consecutive burst at the beginning of each 32-frame period (T=32 frames). In some implementations, the network may set the PF interval parameter N to T / 8 (i.e., 4 frames) and increase the number of paging opportunities (Ns) per frame to 4, thereby concentrating the four POs into PF1 while preserving the overall paging capacity. In some implementations, (SFN + PF_offset) mod T = (UE_ID Mod N), where SFN is the system frame number (SFN) and UE_ID is the UE identifier. A connected UE 102 supporting NES functionality can be configured to monitor only one burst (PF1) in each paging period for any paging DCI 1_0 carrying a 1-bit RACH adaptation flag. After decoding the paging DCI or confirming that there are no paging messages pending, base station 104 can spend the remaining 28 frames in a low-power state because PF2-PF8 have been effectively "moved" into the burst of PF1.

[0136] In contrast, paging adaptive scheme 401 illustrates how paging points (POs) can be concentrated into a single paging function (PF). For example, base station 104 can concentrate paging transmissions into two different clusters within the same T=32 frame period. In one example, the first cluster (PF1) can be configured with Ns = 8 POs and N = T / 32 (e.g., 1 frame), while the second cluster (PF2) at the end of the period can use Ns = 4 and N = T / 16 (e.g., 2 frames). In some specific implementations, (SFN + PF_offset) mod T = (Tdiv N) (UE_ID Mod N), where N = 1 / T. UE 102 can determine these clusters via PF / PO calculation and “wake up” for PF1 and PF2, thereby allowing base station 104 to concentrate all POs into two narrow windows. This two-layer clustering allows the network to spend even more time in sleep mode.

[0137] Figure 4 The two adaptive schemes described in the text are based on Figure 1 In the static paging configuration described, PF and PO are fixed in both the time and spatial domains. Paging adaptation schemes 400 and 401 are also supplemented by providing alternative semi-static paging patterns that can be enabled or disabled without incurring additional group common DCI overhead. Figure 2 Dynamic PRACH adaptive scheme and Figure 3 The UAC-based conditional triggering scheme. For example, base station 104 can signal the selection between these paging adaptation schemes via a new bit in SIB1 for idle / inactive UEs or via DCI 1_0 for connected UEs, so UE 102 can adjust its monitoring behavior accordingly: one PF burst per cycle (as shown in paging adaptation scheme 400) or two PF clusters per cycle (as shown in paging adaptation scheme 401).

[0138] Figure 5 Examples of example OD-SSB transmission schemes 500 and 501 are illustrated according to some specific implementations. In OD-SSB transmission scheme 500, the primary cell (PCell) 504 continues to broadcast SSB 508 at a fixed period (“always on”), while the secondary cell (SCell) 506 remains silent until on-demand SSB 502 is triggered. In some specific implementations, PCell 504 broadcasts SSB 508 according to a baseline period defined in the system information, which provides support for legacy UEs and initial access procedures. When the network determines that additional measurement opportunities or handover preparations are needed (e.g., based on a signal quality report or impending SCell activation), base station 104 transmits a MAC-CE to trigger one or more on-demand SSB bursts on SCell 506. These OD-SSB transmissions provide additional synchronization reference points to UEs (such as UE 102) without requiring SCell 506 to remain constantly active.

[0139] In OD-SSB transmission scheme 501, SCell 506 transmits both periodic (“always-on”) transmissions and OD-SSB transmissions. In this scheme, PCell 504 continues to broadcast according to a defined SSB schedule, and SCell 506 broadcasts a baseline always-on SSB (much like PCell 504) to provide continuous measurement and mobility support. When a conditional OD-SSB trigger is detected, SCell 506 can transmit a burst of OD-SSB 502 transmissions between periodic always-on SSBs 508. OD-SSBs 502 can be grouped together in a cluster of M frames, after which SCell 506 can return to its normal periodic SSB schedule. This hybrid approach helps reduce the latency of SCell activation and measurement handover without permanently causing interference or increasing power consumption on SCell 506.

[0140] Figure 6 A flowchart illustrating an example method 600 for RACH adaptation according to some specific implementation is shown. For clarity, method 600 is described in the context of the preceding figures. For example, method 600 may be provided by a UE (such as...) Figure 1 Method 600 can be executed by any suitable system, environment, software, hardware, or combination thereof. In some implementations, the operations of method 600 may be performed in parallel, in combination, cyclically, or in any order. Figure 6 The example method 600 shown can be modified or reconfigured to include additional, fewer, or different steps. Figure 6 (not shown in the image), these steps can be performed in the order shown or in a different order.

[0141] In 602, the UE determines one or more resources to monitor for RACH adaptation indicators based on the UE's connectivity status and the UE's ability to support RACH adaptation.

[0142] In 604, the UE monitors one or more resources to obtain the RACH adaptive indicator.

[0143] Figure 7 A flowchart illustrating an example method 700 for RACH adaptation according to some specific implementation is shown. For clarity, method 700 is described in the context of the preceding figures. For example, method 700 may be provided by a UE (such as...) Figure 1 Method 700 can be executed by any suitable system, environment, software, hardware, or combination thereof. In some implementations, the operations of method 700 may be performed in parallel, in combination, cyclically, or in any order. Figure 7The example method 700 shown can be modified or reconfigured to include additional, fewer, or different steps. Figure 7 (not shown in the image), these steps can be performed in the order shown or in a different order.

[0144] In 702, the UE receives an indication of one or more triggering conditions to achieve RACH adaptation.

[0145] In 704, the UE responds to determining that one or more triggering conditions are met to enable RACH adaptation.

[0146] Figure 8 A flowchart illustrating an example method 800 for RACH adaptation according to some specific implementation is shown. For clarity, method 800 is described in the context of the preceding figures. For example, method 800 may be provided by an access node (such as...) Figure 1 The method 800 is executed by base station 104. The method 800 can also be executed by any suitable system, environment, software, hardware, or combination thereof. In some specific implementations, the operation of method 800 can be performed in parallel, in combination, cyclically, or in any order. Figure 8 The example method 800 shown can be modified or reconfigured to include additional, fewer, or different steps. Figure 8 (not shown in the image), these steps can be performed in the order shown or in a different order.

[0147] In 802, the access node is based on the UE (such as...). Figure 1 The connectivity status of UE 102 and the UE's ability to support RACH adaptation are used to determine one or more resources to be used to send RACH adaptation indicators.

[0148] At 804, the access node sends a message including a RACH adaptive indicator via one or more resources.

[0149] Figure 9 A flowchart illustrating an example method 900 for RACH adaptation according to some specific implementation is shown. For clarity, method 900 is described in the context of the preceding figures. For example, method 900 may be provided by an access node (such as...) Figure 1 The method 900 is executed by base station 104. The method 900 can also be executed by any suitable system, environment, software, hardware, or combination thereof. In some specific implementations, the operation of method 900 can be performed in parallel, in combination, cyclically, or in any order. Figure 9 The example method 900 shown can be modified or reconfigured to include additional, fewer, or different steps. Figure 9 (not shown in the image), these steps can be performed in the order shown or in a different order.

[0150] In 902, the access node configures one or more triggering conditions to achieve RACH adaptation.

[0151] In 904, the access node responds to determining that one or more triggering conditions are met to target the UE (such as...). Figure 1 UE102) enables RACH adaptation.

[0152] Figure 10 An example UE 1000 according to some specific implementations is illustrated. UE 1000 may be similar to Figure 1 UE 1000 is interchangeable with UE 102 and / or substantially interchangeable with UE 1000. UE 1000 can be any mobile or non-mobile computing device, such as, for example, a mobile phone, computer, tablet, industrial wireless sensor, video device (e.g., camera or camcorder), wearable device (e.g., smartwatch), slack IoT device, etc.

[0153] UE 1000 may include a processor 1002, RF interface circuitry 1004, memory / storage device 1006, user interface 1008, sensor 1010, drive circuitry 1012, power management integrated circuit (PMIC) 1014, one or more antennas 1016, and / or battery 1018. Components of UE 1000 may be implemented as integrated circuits (ICs), portions of integrated circuits, discrete electronic devices or other modules, logic components, hardware, software, firmware, or combinations thereof. Figure 10 The block diagram shows a high-level view of some of the components of the UE 1000. However, some of the components shown may be omitted, additional components may be present, and different arrangements of the components shown may be used in other specific implementations.

[0154] The components of UE 1000 can be coupled to various other components via one or more interconnects 1020, which can represent any type of interface, input / output, bus (local, system, or extended), transmit line, trace, optical connection, etc., allowing various circuit components (on common or different chips or chipsets) to interact with each other.

[0155] Processor 1002 may include one or more processors. For example, processor 1002 may include processor circuitry such as, for example, baseband processor circuitry (BB) 1022A, central processing unit circuitry (CPU) 1022B, and graphics processing unit circuitry (GPU) 1022C. Processor 1002 may include any type of circuitry or processor circuitry that executes or otherwise operates computer-executable instructions (such as program code, software modules, or functional procedures from memory / storage device 1006) to cause UE 1000 to perform the operations described herein.

[0156] In some implementations, the baseband processor circuit 1022A can access the communication protocol stack 1024 in the memory / storage device 1006 to communicate over a 3GPP-compatible network. Generally, the baseband processor circuit 1022A can access the communication protocol stack to perform user plane functions at the Physical (PHY) layer, Medium Access Control (MAC) layer, Radio Link Control (RLC) layer, Packet Data Convergence Protocol (PDCP) layer, Serving Data Adaptive Protocol (SDAP) layer, and Protocol Data Unit (PDU) layer; and to perform control plane functions at the PHY layer, MAC layer, RLC layer, PDCP layer, RRC layer, and Non-Access Stratum (NAS) layer. In some implementations, PHY layer operations may additionally / optionally be performed by components of the RF interface circuit 1004. The baseband processor circuit 1022A can generate or process baseband signals or waveforms carrying information in a 3GPP-compatible network. In some specific implementations, the waveform used for NR may be based on Cyclic Prefix Orthogonal Frequency Division Multiplexing (CP-OFDM) in the uplink or downlink, and Discrete Fourier Transform Extended OFDM (DFT-S-OFDM) in the uplink.

[0157] The memory / storage device 1006 may include one or more non-transitory computer-readable media, including instructions (e.g., a communication protocol stack 1024) that can be executed by the processor 1002 to cause the UE 1000 to perform the various operations described herein. The memory / storage device 1006 may include any type of volatile or non-volatile memory that can be distributed throughout the UE 1000. In some specific implementations, the memory / storage device 1006 may reside on the processor 1002 itself (e.g., L1 cache and L2 cache), while other memory / storage devices 1006 may be located external to the processor 1002 but accessible via a memory interface. The memory / storage device 1006 may include any suitable volatile or non-volatile memory, such as, but not limited to, dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state memory, or any other type of memory device technology.

[0158] The RF interface circuit 1004 may include transceiver circuitry and a radio frequency front-end module (RFEM) that allows the UE 1000 to communicate with other devices via a radio access network. The RF interface circuit 1004 may include various components arranged in the transmit or receive path. These components may include, for example, switches, mixers, amplifiers, filters, synthesizer circuitry, control circuitry, etc.

[0159] In the receiving path, the RFEM can receive the radiated signal from the air interface via antenna 1016 and continue to filter and amplify the signal (using a low-noise amplifier). This signal can then be provided to the transceiver's receiver, which down-converts the RF signal into a baseband signal for the baseband processor.

[0160] In the transmission path, the transceiver's transmitter up-converts the baseband signal received from the baseband processor and provides the RF signal to the RFEM. The RFEM can amplify the RF signal using a power amplifier before it is radiated across the air interface via antenna 1016. In various specific implementations, the RF interface circuitry 1004 can be configured to transmit / receive signals in a manner compatible with NR access technologies.

[0161] Antenna 1016 may include one or more antenna elements to convert electrical signals into radio waves for travel through the air and to convert received radio waves into electrical signals in the air. In some embodiments, these antenna elements may be arranged as one or more antenna panels. Antenna 1016 may have omnidirectional, directional, or a combination thereof antenna panels to enable beamforming and multiple-input multiple-output communication. Antenna 1016 may include any / all of the following: microstrip antenna, printed antenna fabricated on the surface of one or more printed circuit boards, patch antenna, phased array antenna, etc. Antenna 1016 may have one or more panels designed for one or more specific frequency bands (such as bands in FR1 or FR2).

[0162] User interface 1008 includes various input / output (I / O) devices designed to enable a user to interact with UE 1000. User interface 1008 includes input device circuitry and output device circuitry. Input device circuitry includes any physical or virtual components for accepting input, particularly including one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, keypad, mouse, touchpad, touchscreen, microphone, scanner, or head-mounted device. Output device circuitry includes any physical or virtual components for displaying information or otherwise conveying information (such as sensor readings, actuator positions, or other similar information). Output device circuitry may include any number or combination of audio or visual displays, particularly including one or more simple visual outputs / indicators (e.g., binary status indicators, such as light-emitting diodes "LEDs," and multi-character visual outputs), or more complex outputs such as display devices or touchscreens (e.g., liquid crystal displays "LCDs," LED displays, quantum dot displays, projectors), wherein the output of characters, graphics, multimedia objects, etc., is generated or produced through the operation of UE 1000.

[0163] Sensor 1010 may include devices, modules, or subsystems intended to detect events or changes in their environment and transmit information (sensor data) about the detected events to other devices, modules, subsystems, etc. Examples of such sensors include, in particular, inertial measurement units including accelerometers, gyroscopes, or magnetometers; microelectromechanical systems (MEMS) or nanoelectromechanical systems (NEMS) including 3-axis accelerometers, 3-axis gyroscopes, or magnetometers; level sensors; temperature sensors (e.g., thermistors); pressure sensors; image capture devices (e.g., cameras or lensless aperture devices); light detection and ranging sensors; proximity sensors (e.g., infrared radiation detectors, etc.); depth sensors; ambient light sensors; ultrasonic transceivers; microphones or other similar audio capture devices; and so on.

[0164] The driving circuit 1012 may include software and hardware elements that operate to control a specific device embedded in, attached to, or otherwise communicatively coupled to the UE 1000. The driving circuit 1012 may include various drivers that allow other components to interact with or control various input / output (I / O) devices that may exist within or be connected to the UE 1000. For example, the driving circuit 1012 may include: a display driver for controlling and allowing access to a display device; a touchscreen driver for controlling and allowing access to a touchscreen interface; a sensor driver for acquiring sensor readings of sensor 1010 and controlling and allowing access to sensor 1010; a driver for acquiring actuator positioning of electromechanical components or controlling and allowing access to electromechanical components; a camera driver for controlling and allowing access to an embedded image capture device; and an audio driver for controlling and allowing access to one or more audio devices.

[0165] PMIC 1014 manages the power supplied to various components of UE 1000. Specifically, relative to processor 1002, PMIC 1014 controls power selection, voltage scaling, battery charging, or DC-DC conversion.

[0166] In some implementations, PMIC 1014 may control various power-saving mechanisms of UE 1000 or otherwise become part of various power-saving mechanisms of the UE. Battery 1018 may power UE 1000, but in some examples, UE 1000 may be installed and deployed in a fixed location and may have a power source coupled to the power grid. Battery 1018 may be a lithium-ion battery, a metal-air battery such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, etc. In some implementations, such as in vehicle-based applications, battery 1018 may be a typical lead-acid automotive battery.

[0167] Figure 11 An example access node 1100 according to some specific implementations is illustrated. Access node 1100 (also referred to as a base station or gNB) may be similar to and / or substantially interchangeable with base station 104. Access node 1100 may include one or more of a processor 1102, RF interface circuitry 1104, core network (CN) interface circuitry 1106, memory / storage device circuitry 1108, and one or more antennas 1110. Processor 1102 may include any type of circuitry or processor circuitry that executes or otherwise operates computer-executable instructions (such as program code, software modules, or functional procedures from memory / storage device circuitry 1108) to cause access node 1100 to perform the operations described herein.

[0168] Components of access node 1100 can be coupled to various other components via one or more interconnects 1112. Processor 1102, RF interface circuitry 1104, memory / storage device circuitry 1108 (including communication protocol stack 1114), antenna 1110, and interconnects 1112 can be similarly coupled to... Figure 10 Similar named components are shown and described. For example, processor 1102 may include processor circuitry such as, for example, baseband processor circuitry (BB) 1116A, central processing unit circuitry (CPU) 1116B, and graphics processing unit circuitry (GPU) 1116C.

[0169] The CN interface circuit 1106 can provide connectivity to a core network (e.g., a 5GC using a 5G core network (5GC) compatible network interface protocol, such as carrier Ethernet or some other suitable protocol). Network connectivity can be provided to / from access node 1100 via fiber optic or wireless backhaul. The CN interface circuit 1106 may include one or more dedicated processors or FPGAs for communicating using one or more of the aforementioned protocols. In some implementations, the CN interface circuit 1106 may include multiple controllers for providing connectivity to other networks using the same or different protocols.

[0170] As used herein, the terms "access node," "access point," etc., refer to equipment that provides radio baseband functionality for data and / or voice connectivity between a network and one or more users. An access node may also be referred to as a base station (BS), gNB, RAN node, eNB, NodeB, roadside unit (RSU), transmit and receive point (TRP), TRxP, etc. An access node may include a ground station (e.g., a terrestrial access point) or a satellite station that provides coverage within a geographic area (e.g., a cell). As used herein, the term "NGRAN node," etc., refers to access node 1100 operating in an NR or 5G system (e.g., a gNB), and the term "E-UTRAN node," etc., refers to access node 1100 operating in an LTE or 4G system (e.g., an eNB). Depending on various specific implementations, access node 1100 may be implemented as one or more of dedicated physical equipment such as a macro cell base station and / or a low-power base station for providing (compared to macro cells) smaller coverage areas, smaller user capacity, or higher bandwidth in femtocells, picocells, or other cells.

[0171] In some specific implementations, the access node 1100 may be implemented as one or more software entities running on a server computer as part of a virtual network, which may be referred to as a cloud RAN (CRAN) and / or a virtual baseband unit pool (vBBUP). In vehicle-to-everything (V2X) scenarios, the access node 1100 may be or serve as an RSU, which refers to any transport infrastructure entity used for V2X communication. An RSU may be implemented in or by a suitable RAN node or a stationary (or relatively stationary) UE, wherein an RSU implemented in or by a UE is referred to as a "UE-type RSU," an RSU implemented in or by an eNB is referred to as an "eNB-type RSU," an RSU implemented in or by a gNB is referred to as a "gNB-type RSU," and so on.

[0172] In the preceding description, various components are described as performing one or more tasks. Such descriptions should be interpreted as including the phrase “configured to”. Statements describing components as configured to perform one or more tasks are explicitly intended not to invoke the interpretation of 35 USC § 112(f) for that component.

[0173] In some implementations, one or more of the components described in the preceding figures may be configured to perform one or more operations, techniques, processes, and / or methods set forth in the Embodiments section below. For example, the baseband circuitry described in conjunction with one or more of the preceding figures may be configured to operate according to one or more embodiments described below. As another example, circuitry associated with a UE, access node, base station, or network element may be configured to operate according to one or more embodiments set forth below.

[0174] Example 1 is a method comprising: determining one or more resources to monitor for RACH adaptation indicators based on the connectivity state of the UE and the UE's ability to support RACH adaptation; and monitoring one or more resources to obtain RACH adaptation indicators.

[0175] Example 2 includes the method according to Example 1, wherein the connectivity state of the UE includes RRC connected state, RRC idle state, or RRC inactive state.

[0176] Example 3 includes the method according to any one of Examples 1 to 2, wherein monitoring one or more resources includes monitoring at least one PO per paging cycle or per system information modification period while the UE is in RRC connected state to obtain paging messages with RACH adaptive indicators.

[0177] Example 4 includes the method according to any one of Examples 1 to 3, and further includes: receiving a DCI format 1_0 having a PDCCH command including a RACH adaptive indicator.

[0178] Example 5 includes the method according to Example 4, further comprising: overwriting the RACH resource activation or deactivation status indicated by the DCI associated with P-RNTI.

[0179] Example 6 includes the method according to any one of Examples 1 to 5, further comprising: receiving SIB1 having bits indicating whether semi-static RACH adaptation is enabled or disabled.

[0180] Example 7 includes the method according to Example 6, wherein the reception of SIB1 occurs while the UE is in the RRC idle state.

[0181] Example 8 includes the method according to any one of Examples 6 to 7, wherein the reception of SIB1 occurs while the UE is in an RRC inactive state.

[0182] Example 9 includes the method according to any one of Examples 6 to 8, wherein semi-static RACH adaptation is enabled and the method further includes: discarding the RACH adaptation indicator from the paging DCI message when the bit is set to 1.

[0183] Example 10 includes the method according to any one of Examples 6 to 9, wherein semi-static RACH adaptation is disabled and the method further includes: monitoring paging DCI messages to obtain RACH adaptation indicators when the bit is set to 0.

[0184] Example 11 includes the method according to any one of Examples 6 to 10, wherein semi-static RACH adaptation is enabled and the method further includes: monitoring paging DCI messages to obtain RACH adaptation indicators, regardless of whether the bit is set to 0 or 1.

[0185] Example 12 includes the method according to Example 11, further comprising: identifying an unaligned activation or deactivation state between a semi-static RACH adaptive indicator and a dynamic RACH adaptive indicator in a paging DCI message; and overwriting the semi-static RACH adaptive indicator with the dynamic RACH adaptive indicator from the paging DCI message.

[0186] Example 13 includes the method according to any one of Examples 6 to 12, wherein monitoring one or more resources includes monitoring the next BCCH timing after receiving a paging short message to obtain an SIB1 update.

[0187] Example 14 includes the method according to any one of Examples 6 to 13, wherein monitoring one or more resources includes monitoring the current BCCH period to obtain SIB1 updates after receiving a paging short message when the bit indication semi-static RACH adaptation in SIB1 is enabled.

[0188] Example 15 includes the method according to any one of Examples 6 to 14, wherein monitoring one or more resources includes monitoring the current BCCH period to obtain SIB1 updates after receiving a paging short message that enables immediate acquisition of SIB1 updates.

[0189] Example 16 includes the method according to any one of Examples 6 to 15, wherein monitoring one or more resources includes monitoring the next BCCH period to obtain SIB1 updates after receiving a paging short message disabling immediate access to SIB1 updates.

[0190] Example 17 includes the method according to any one of Examples 1 to 16, further comprising: receiving SIB1 while the UE is in an RRC connection state, the SIB1 including a bit indicating whether semi-static RACH adaptation is enabled or disabled.

[0191] Example 18 includes the method according to Example 17, wherein monitoring one or more resources includes monitoring at least one PO per BCCH modification period or per paging cycle to obtain SIB1 updates when bit indication semi-static RACH adaptation in SIB1 is enabled.

[0192] Example 19 includes the method according to any one of Examples 1 to 18, further comprising: receiving a handover command having bits indicating whether RACH adaptation is enabled for the target cell.

[0193] Example 20 includes the method according to Example 19, and further includes: enabling RACH adaptation for the target cell during the handover period according to the handover command.

[0194] Example 21 includes the method according to any one of Examples 19 to 20, further comprising: receiving SIB1 via the target cell including bits indicating whether RACH adaptation is enabled for the target cell.

[0195] Example 22 includes the method according to Example 21, and further includes: enabling RACH adaptation for the target cell based on bits in the handover command and bits in SIB1.

[0196] Example 23 is a method comprising: receiving an indication of one or more triggering conditions to implement RACH adaptation; and enabling RACH adaptation for a UE in response to determining that one or more triggering conditions are met.

[0197] Example 24 includes the method according to Example 23, wherein receiving an indication for one or more triggering conditions includes receiving an SIB indicating a UAC threshold for enabling RACH adaptation.

[0198] Example 25 includes the method according to Example 24, wherein enabling RACH adaptation for the UE includes enabling RACH adaptation in response to determining that the UE's UAC access probability satisfies a UAC threshold indicated by the SIB.

[0199] Example 26 includes the method according to any one of Examples 24 to 25, wherein a set of UAC thresholds is configured for RACH adaptation, each UAC threshold corresponding to a specific combination of access class and access identity.

[0200] Example 27 includes the method according to any one of Examples 24 to 26, wherein a UAC threshold is configured for all access categories and access identities.

[0201] Example 28 includes the method according to any one of Examples 24 to 27, wherein the SIB further indicates the probability to be used to determine whether to activate RACH adaptation.

[0202] Example 29 includes the method according to any one of Examples 23 to 28, wherein determining that one or more triggering conditions are met includes determining that paging adaptation is enabled for the UE.

[0203] Example 30 includes the method according to Example 29, wherein RACH adaptation is disabled for the UE when paging adaptation is disabled.

[0204] Example 31 includes the method according to any one of Examples 23 to 30, wherein enabling RACH adaptation includes enabling RACH adaptation during the PF derived from the paging configuration of the UE.

[0205] Example 32 includes the method according to Example 31, wherein RACH adaptation is disabled in frames other than the PF derived from the paging configuration of the UE.

[0206] Example 33 includes the method according to any one of Examples 31 to 32, wherein RACH adaptation is enabled in several frames immediately following the PF derived from the paging configuration of the UE, and wherein the number of frames is configured by the SIB.

[0207] Example 34 includes the method according to any one of Examples 23 to 33, wherein determining that one or more triggering conditions are met includes determining that SSB or OD-SSB adaptation is enabled for the UE.

[0208] Example 35 includes the method according to Example 34, wherein RACH adaptation is disabled when SSB or OD-SSB adaptation is disabled for the UE.

[0209] Example 36 includes the method according to any one of Examples 23 to 35, wherein determining that one or more triggering conditions are met includes determining that the SSB period is less than a threshold configured by the network.

[0210] Example 37 includes the method according to Example 36, wherein RACH adaptation is disabled when the SSB period is greater than or equal to a threshold.

[0211] Example 38 includes the method according to any one of Examples 23 to 37, wherein determining that one or more triggering conditions are met includes determining that the number of RACH preamble retransmissions performed by the UE is greater than a threshold configured by the network.

[0212] Example 39 includes the method according to any one of Examples 23 to 38, further comprising: using a set of additional RACH resources configured for RACH adaptation when one or more triggering conditions are met.

[0213] Example 40 includes the method according to Example 39, wherein the UE cannot switch from the set of additional RACH resources to the default RACH resource after switching from the default RACH resource to the additional RACH resource.

[0214] Example 41 includes the method according to Example 40, and further includes: using a default RACH resource in a subsequent RACH procedure.

[0215] Example 42 includes the method according to any one of Examples 23 to 41, wherein receiving an indication for one or more triggering conditions includes receiving a MAC control element (MAC-CE) that triggers RACH adaptation and OD-SSB adaptation.

[0216] Example 43 includes the method according to Example 42, further comprising: disabling RACH adaptation after OD-SSB adaptation is disabled.

[0217] Example 44 includes the method according to Example 43, wherein OD-SSB adaptation is deactivated by receiving a second MAC-CE or after a threshold number of SSB adaptation opportunities have passed.

[0218] Example 45 includes the method according to any one of Examples 23 to 44, wherein receiving an indication for one or more triggering conditions includes receiving a group common DCI message that triggers RACH adaptation and SSB adaptation.

[0219] Example 46 includes the method according to Example 45, further comprising: disabling RACH adaptation after receiving a second set of public DCI messages to disable SSB adaptation.

[0220] Example 47 is a method comprising: determining one or more resources to be used for transmitting a RACH adaptation indicator based on the connectivity state of the UE and the UE's ability to support RACH adaptation; and transmitting a message including the RACH adaptation indicator via the one or more resources.

[0221] Example 48 includes the method according to Example 47, wherein the connectivity state of the UE includes an RRC connected state, an RRC idle state, or an RRC inactive state.

[0222] Example 49 includes the method according to any one of Examples 47 to 48, further comprising: sending a DCI format 1_0 having a PDCCH command including a RACH adaptive indicator.

[0223] Example 50 includes the method according to Example 49, further comprising: overwriting the RACH resource activation or deactivation state indicated by the DCI associated with the P-RNTI.

[0224] Example 51 includes the method according to any one of Examples 47 to 50, further comprising: sending SIB1 having bits indicating whether semi-static RACH adaptation is enabled or disabled.

[0225] Example 52 includes the method according to Example 51, wherein the transmission of SIB1 occurs while the UE is in the RRC idle state.

[0226] Example 53 includes the method according to any one of Examples 51 to 52, wherein the transmission of SIB1 occurs while the UE is in an RRC inactive state.

[0227] Example 54 includes the method according to any one of Examples 51 to 53, wherein sending a message via one or more resources includes sending an SIB1 update at the next BCCH timing after sending a paging short message.

[0228] Example 55 includes the method according to any one of Examples 51 to 54, wherein sending a message via one or more resources includes sending an SIB1 update at the current BCCH timing when the bit indication semi-static RACH adaptation in SIB1 is enabled.

[0229] Example 56 includes the method according to any one of Examples 51 to 55, wherein sending a message via one or more resources includes sending the SIB1 update at the current BCCH timing after sending a paging short message that enables immediate access to the SIB1 update.

[0230] Example 57 includes the method according to any one of Examples 51 to 56, wherein sending a message via one or more resources includes sending the SIB1 update at the next BCCH timing after sending a paging short message disabling immediate access to SIB1 updates.

[0231] Example 58 includes the method according to any one of Examples 47 to 57, further comprising: transmitting SIB1 while the UE is in an RRC connection state, the SIB1 including bits indicating whether semi-static RACH adaptation is enabled or disabled.

[0232] Example 59 includes the method according to any one of Examples 47 to 58, further comprising: sending a handover command having bits indicating whether RACH adaptation is enabled for the target cell.

[0233] Example 60 is a method comprising: configuring one or more triggering conditions to enable RACH adaptation; and enabling RACH adaptation for a UE in response to determining that one or more triggering conditions are met.

[0234] Example 61 includes the method according to Example 60, wherein configuring one or more triggering conditions includes sending an SIB indicating a UAC threshold for enabling RACH adaptation.

[0235] Example 62 includes the method according to Example 61, wherein a set of UAC thresholds is configured for RACH adaptation, each UAC threshold corresponding to a specific combination of access class and access identity.

[0236] Example 63 includes the method according to any one of Examples 61 to 62, wherein a UAC threshold is configured for all access categories and access identities.

[0237] Example 64 includes the method according to any one of Examples 61 to 63, wherein the SIB further indicates the probability for determining whether to activate RACH adaptation.

[0238] Example 65 includes the method according to any one of Examples 60 to 64, wherein determining that one or more triggering conditions are met includes determining that paging adaptation is enabled for the UE.

[0239] Example 66 includes the method according to Example 65, wherein RACH adaptation is disabled for the UE when paging adaptation is disabled.

[0240] Example 67 includes the method according to any one of Examples 60 to 66, wherein enabling RACH adaptation includes enabling RACH adaptation during the PF associated with the paging configuration of the UE.

[0241] Example 68 includes the method according to Example 67, wherein RACH adaptation is disabled in frames other than the PF associated with the paging configuration of the UE.

[0242] Example 69 includes the method according to any one of Examples 67 to 68, wherein RACH adaptation is enabled in several frames immediately following the PF associated with the paging configuration of the UE, and wherein the number of frames is configured by the SIB.

[0243] Example 70 includes the method according to any one of Examples 60 to 69, wherein determining that one or more triggering conditions are met includes determining that SSB or OD-SSB adaptation is enabled for the UE.

[0244] Example 71 includes the method according to Example 70, wherein RACH adaptation is disabled when SSB or OD-SSB adaptation is disabled for the UE.

[0245] Example 72 includes the method according to any one of Examples 60 to 71, wherein determining that one or more triggering conditions are met includes determining that the SSB period is less than a threshold configured by the network.

[0246] Example 73 includes the method according to Example 72, wherein RACH adaptation is disabled when the SSB period is greater than or equal to a threshold.

[0247] Example 74 includes the method according to any one of Examples 60 to 73, wherein determining that one or more triggering conditions are met includes determining that the number of RACH preamble retransmissions performed by the UE is greater than a threshold configured by the network.

[0248] Example 75 includes the method according to any one of Examples 60 to 74, wherein configuring one or more triggering conditions includes sending a MAC-CE that triggers RACH adaptation and OD-SSB adaptation.

[0249] Example 76 includes the method according to Example 75, further comprising: disabling RACH adaptation after OD-SSB adaptation is disabled.

[0250] Example 77 includes the method according to Example 76, wherein OD-SSB adaptation is deactivated by a second MAC-CE or after the threshold number of SSB adaptation opportunities has passed.

[0251] Example 78 includes the method according to any one of Examples 60 to 77, wherein configuring one or more triggering conditions includes sending a group common DCI message that triggers RACH adaptation and SSB adaptation.

[0252] Example 79 includes the method according to Example 78, further comprising: disabling RACH adaptation after sending a second set of public DCI messages to disable SSB adaptation.

[0253] Example 80 is an apparatus comprising: one or more processors; and a memory storing instructions that, when executed, cause the one or more processors to perform the method according to any one of Examples 1 to 75.

[0254] Example 81 is a baseband processor configured to perform the method according to any one of Examples 1 to 75.

[0255] Unless otherwise expressly stated, any of the above embodiments may be combined with any other embodiment (or combination of embodiments). The foregoing description of one or more specific embodiments provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise forms disclosed. In view of the teachings above, modifications and variations are possible, or modifications and variations may be obtained from practice of various embodiments.

[0256] Although the above embodiments have been described in considerable detail, many variations and modifications will become apparent to those skilled in the art once the above disclosure is fully understood. It is intended that the following claims be construed as encompassing all such variations and modifications.

[0257] As is widely recognized, the use of personally identifiable information should comply with privacy policies and practices that are generally accepted to meet or exceed industry or governmental requirements for protecting user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly explained to users.

Claims

1. A method, the method comprising: The one or more resources to be monitored for the RACH adaptation indicator are determined based at least on the connectivity status of the user equipment (UE) and the UE's ability to support random access channel (RACH) adaptation. as well as Monitor the one or more resources for the RACH adaptive indicator.

2. The method of claim 1, wherein monitoring the one or more resources includes monitoring at least one paging opportunity (PO) per system information modification period for paging messages with RACH adaptive indicators while the UE is in an RRC connected state.

3. The method according to claim 2, further comprising: Receive downlink control information (DCI) format 1_0 with physical downlink control channel (PDCCH) commands including the RACH adaptive indicator.

4. The method according to claim 3, further comprising: Overwrite the RACH resource activation or deactivation status indicated by the DCI associated with the Paging Radio Network Temporary Identifier (P-RNTI).

5. The method according to claim 1, further comprising: Receive the first system information block (SIB1) with bits indicating whether semi-static RACH adaptation is enabled or disabled.

6. The method of claim 5, wherein semi-static RACH adaptation is disabled, and the method further comprises: When the bit is set to 0, the paging DCI message is monitored for the RACH adaptive indicator.

7. The method of claim 5, wherein semi-static RACH adaptation is enabled, and the method further comprises: Monitor paging DCI messages using the RACH adaptive indicator.

8. The method of claim 5, wherein monitoring the one or more resources comprises monitoring one of the following: The timing of the next broadcast control channel (BCCH) update after receiving the paging short message, When the bit indication semi-static RACH adaptation in SIB1 is enabled, the current BCCH period used for SIB1 update after receiving a paging short message. The current BCCH period used for SIB1 updates after receiving a paging SMS message enabling immediate SIB1 updates, or The next BCCH period for SIB1 updates after receiving a paging short message disabling immediate SIB1 updates.

9. The method according to claim 1, further comprising: While the UE is in RRC connection state, it receives a first system information block (SIB1), the SIB1 including bits indicating whether semi-static RACH adaptation is enabled or disabled, and wherein monitoring the one or more resources includes: when the bits in the SIB1 indicate that semi-static RACH adaptation is enabled, monitoring at least one PO for each BCCH modification period or each paging cycle for SIB1 update.

10. The method according to claim 1, further comprising: Receive a handover command with bits indicating whether RACH adaptation is enabled for the target cell; as well as RACH adaptation is enabled for the target cell during the handover period according to the handover command.

11. The method of claim 10, further comprising: SIB1, including bits indicating whether RACH adaptation is enabled for the target cell, is received via the target cell; as well as RACH adaptation is enabled for the target cell based at least on the bits in the handover command and the bits in SIB1.

12. A method comprising: The one or more resources to be used for sending RACH adaptation indicators are determined based at least on the UE's connectivity state and the UE's ability to support RACH adaptation. as well as A message including the RACH adaptive indicator is sent via the one or more resources.

13. The method of claim 12, wherein the connectivity state of the UE includes an RRC connection state.

14. The method according to claim 12, further comprising: Send a DCI format 1_0 command with the RACH adaptive indicator.

15. The method according to claim 14, further comprising: Overwrite the RACH resource activation or deactivation status indicated by the DCI associated with P-RNTI.

16. The method according to claim 12, further comprising: Send SIB1 with bits indicating whether semi-static RACH adaptation is enabled or disabled, wherein the transmission of SIB1 occurs when the UE is in either an RRC idle state or an RRC inactive state.

17. The method of claim 16, wherein sending the message via the one or more resources comprises sending one of the following: After sending the paging message, the SIB1 update occurs at the next BCCH timing. When the bit indication semi-static RACH adaptation in SIB1 is enabled, SIB1 is updated during the current BCCH timing. After sending a paging SMS message enabling immediate SIB1 updates, the SIB1 update in the current BCCH timing, or After sending a paging message disabling immediate SIB1 updates, the SIB1 update occurs at the next BCCH timing.

18. The method according to claim 12, further comprising: While the UE is in RRC connection state, SIB1 is sent, which includes bits indicating whether semi-static RACH adaptation is enabled or disabled.

19. The method according to claim 12, further comprising: Send a handover command with bits indicating whether RACH adaptation is enabled for the target cell.

20. An apparatus comprising: One or more processors; as well as A memory that stores instructions, which, when executed, cause the one or more processors to perform operations including: The one or more resources to be monitored for the RACH adaptation indicator are determined based at least on the connectivity status of the user equipment (UE) and the UE's ability to support random access channel (RACH) adaptation. as well as Monitor the one or more resources for the RACH adaptive indicator.

21. The method of claim 20, wherein monitoring the one or more resources includes monitoring at least one paging opportunity (PO) per system information modification period for paging messages with RACH adaptive indicators while the UE is in an RRC connected state.

22. The method according to claim 21, further comprising: Receive downlink control information (DCI) format 1_0 with physical downlink control channel (PDCCH) commands including the RACH adaptive indicator.

23. The method according to claim 22, further comprising: Overwrite the RACH resource activation or deactivation status indicated by the DCI associated with the Paging Radio Network Temporary Identifier (P-RNTI).

24. The method according to claim 20, further comprising: Receive the first system information block (SIB1) with bits indicating whether semi-static RACH adaptation is enabled or disabled.

25. The method of claim 24, wherein monitoring the one or more resources comprises monitoring one of the following: The timing of the next broadcast control channel (BCCH) update after receiving the paging short message, When the bit indication semi-static RACH adaptation in SIB1 is enabled, the current BCCH period used for SIB1 update after receiving a paging short message. The current BCCH period used for SIB1 updates after receiving a paging SMS message enabling immediate SIB1 updates, or The next BCCH period for SIB1 updates after receiving a paging short message disabling immediate SIB1 updates.

26. The method according to claim 20, further comprising: While the UE is in RRC connection state, it receives a first system information block (SIB1), the SIB1 including bits indicating whether semi-static RACH adaptation is enabled or disabled, and wherein monitoring the one or more resources includes: when the bits in the SIB1 indicate that semi-static RACH adaptation is enabled, monitoring at least one PO for each BCCH modification period or each paging cycle for SIB1 update.

27. The method of claim 20, further comprising: Receive a handover command with bits indicating whether RACH adaptation is enabled for the target cell; as well as RACH adaptation is enabled for the target cell during the handover period according to the handover command. The method further includes: SIB1, including bits indicating whether RACH adaptation is enabled for the target cell, is received via the target cell; as well as RACH adaptation is enabled for the target cell based at least on the bits in the handover command and the bits in SIB1.

28. An apparatus comprising: One or more processors; as well as A memory that stores instructions, which, when executed, cause the one or more processors to perform operations including: The one or more resources to be used for sending RACH adaptation indicators are determined based at least on the UE's connectivity state and the UE's ability to support RACH adaptation. as well as A message including the RACH adaptive indicator is sent via the one or more resources.

29. The method of claim 28, wherein the connectivity state of the UE includes an RRC connection state.

30. The method of claim 28, further comprising: Send a DCI format 1_0 command with the RACH adaptive indicator included. as well as Overwrite the RACH resource activation or deactivation status indicated by the DCI associated with P-RNTI.

31. The method of claim 28, further comprising: Sending SIB1 with bits indicating whether semi-static RACH adaptation is enabled or disabled, wherein the transmission of SIB1 occurs when the UE is in either an RRC idle state or an RRC inactive state; and Sending the message via the one or more resources includes sending one of the following: After sending the paging message, the SIB1 update occurs at the next BCCH timing. When the bit indication semi-static RACH adaptation in SIB1 is enabled, SIB1 is updated during the current BCCH timing. After sending a paging SMS message enabling immediate SIB1 updates, the SIB1 update in the current BCCH timing, or After sending a paging message disabling immediate SIB1 updates, the SIB1 update occurs at the next BCCH timing.

32. The method according to claim 28, further comprising: Send a handover command with bits indicating whether RACH adaptation is enabled for the target cell.

Images