Network controlled random access channel occasion prioritization rules for subband full duplex random access operation

Abstract

A method (200) performed by a user equipment, UE, (512, 700) for network-controlled Random Access Occasion, RO, prioritization for a Subband Full Duplex, SBFD, operation is provided. The method includes receiving (202), from a network node (510, 800), information indicating at least one UE for using at least one prioritized Random Access Channel, RACH, resource for the SBFD operation.

Description

[0001] ATTORNEY’S DOCKET PATENT APPLICATION 017997.4336 (P112649WO01)

[0002] 1 of 62

[0003] NETWORK CONTROLLED RANDOM ACCESS CHANNEL OCCASION PRIORITIZATION RULES FOR SUBBAND FULL DUPLEX RANDOM ACCESS OPERATION

[0004] TECHNICAL FIELD

[0005] The present disclosure relates, in general, to wireless communications and, more particularly, systems and methods for network controlled Random Access Channel Occasion (RO) prioritization rules for Subband Full Duplex (SBFD) Random Access (RA) operation.

[0006] BACKGROUND

[0007] Transmission and reception from a node such as, for example, a terminal in a cellular system, can be multiplexed in the frequency domain or in the time domain (or combinations thereof). Frequency Division Duplex (FDD) as illustrated to the left in FIGURE 1 implies that downlink (DL) and uplink (UL) transmission take place in different, sufficiently separated, frequency bands. Time Division Duplex (TDD), as illustrated to the right in FIGURE 1, implies that downlink and uplink transmission take place in different, non-overlapping time slots. Thus, TDD can operate in unpaired spectrum, whereas FDD requires paired spectrum.

[0008] Typically, the structure of the transmitted signal in a communication system is organized in the form of a frame structure.

[0009] In more detail, the following two information elements (IEs) are defined in current specifications. The TDD pattern is typically configured with at least the first IE and optionally the 2ndIE:

[0010] • TDD-DL-UL-ConfigCommon (cell-specific)

[0011] • TDD-DL-UL-ConfigDedicated (UE-specific)

[0012] The first IE is cell specific (common to all User Equipments (UEs)) and is provided by broadcast signaling. It provides the number of slots in the TDD pattern via a reference subcarrier spacing (SCS) and a periodicity such that the S-slot pattern repeats every S slots. This IE allows for very flexible configuration of the pattern characterized as follows:

[0013] • A number of full DL slots at the beginning of the pattern configured by the parameter nDownlinkSlots ATTORNEY’ S DOCKET PATENT APPLICATION 017997.4336 (P112649WO01)

[0014] 2 of 62

[0015] • A number of full UL slots at the end of the pattern configured by the parameter n UplinkSlots

[0016] • A number of DL ('D') symbols following the full DL slots configured by the parameter nDownlinkSymbols

[0017] • A number of UL ('U') symbols preceding the full DL slots configured by the parameter nUplinkSlots

[0018] • If there is a gap between the last DL symbol and the first UL symbol, then all symbols in the gap are characterized as flexible ('F'). A symbol classified as *F' can be used for DL or UL. A UE determines the direction in one of the following two ways:

[0019] o Detecting a Downlink Control Information (DCI) that schedules / triggers a DL signal / channel, e.g., Physical Downlink Shared Channel (PDSCH), Channel State Information-Reference Signal (CSI-RS) or schedules / triggers an UL signal / channel, e.g. Physical Uplink Shared Channel (PUSCH), Sounding Reference Signal (SRS), etc.

[0020] o By dedicated (UE-specific) signaling of the IE TDD-DL-UL- ConfigDedicated. This parameter overrides some or all of the 'F symbols in the pattern, thus providing a semi-static indication of whether a symbol is classified as 'D' or 'U'

[0021] • Optionally, a 2ndpattern that is concatenated to the first pattern can be configured as above. If a 2ndpattern is configured, the constraint is that the sum of the periodicities of the two patterns must evenly divide 20 ms.

[0022] FIGURE 2 shows an exemplary TDD DL / UL pattern configured by TDD-DL-UL-ConfigCommon. It consists of S = 5 slots. TDD-DL-UL-ConfigCommon configures the cellspecific pattern, and TDD-DL-UL-ConfigDedicated (if provided) UE-specifically configures the direction for some or all of the 'F symbols in the cell-specific pattern. More specifically, the TDD DL / UL pattern consists of 3 full 'D' slots, 1 full 'U' slot, with a mixed slot in between consisting of 4 'D' symbols and 3 'U' symbols. The remaining 7 symbols in the mixed slot are classified as 'F.'

[0023] If a UE is not configured with TDD-DL-UL-ConfigDedicated, then the pattern at the ATTORNEY’S DOCKET PATENT APPLICATION 017997.4336 (P112649WO01)

[0024] 3 of 62

[0025] top of the diagram is what it assumes. As stated above, the network can make use of the 'F' symbols flexibly, by scheduling / triggering either an UL or a DL signal / channel in a UE specific manner. This allows for very dynamic behavior: the direction is not known to the UE a priori; rather, the direction becomes known once the UE detects a DCI scheduling / triggering a particular DL or UL signal / channel.

[0026] In contrast, the DL / UL direction for some or all of the 'F' symbols in a particular slot can be provided to the UE in a semi-static manner by Radio Resource Control (RRC) configuring the UE with TDD-DL-UL-ConfigDedicated. The lower part of FIGURE 2 shows three exemplary configurations for overriding 'F' symbols in Slot 3. If the IE indicates 'allDownlink' or 'allUplink' for a particular slot (or slots), then all 'F' symbols in the slot are converted to either 'D' or 'U,' respectively. If the IE indicates 'explicit,' then a number of symbols at the beginning of the slot and / or a number of symbols at the end of the slot are indicated as 'D' and 'U,' respectively. In the example below, the first 7 and the last 5 are indicated as 'D' and 'U', which converts some of the 'F' symbols (but not all in this example) to D' and 'U.'

[0027] The key behavior in the above is that the UE-specific IE TDD-DL-UL-ConfigDedicated can only override (i.e., specify 'D' or 'U') for symbols that are configured as 'F' by the cell-specific IE TDD-DL-UL-ConfigCommon. In other words, a UE does not expect to have a 'D' symbol converted to 'U' or vice versa.

[0028] Subband Full Duplex

[0029] FIGURE 3 illustrates conventional TDD carrier or carrier systems. As described in the last section, in a conventional TDD system, entire carrier bandwidth (BW) or all carriers in the same frequency band need to be utilizing the same DL transmission or UL reception directions.

[0030] For the Release 18 evolution of the New Radio (NR) system, 3GPP has decided to study the technical feasibilities and potential benefits of subband full duplex (SBFD) systems. FIGURE 4 illustrates an example SBFD system.

[0031] • In such a system, a portion of a wide bandwidth carrier may be used for a different direction than that of the rest of the carrier. This is illustrated in the left-hand side of FIGURE 4. That is, unlike a conventional TDD system as ATTORNEY’S DOCKET PATENT APPLICATION 017997.4336 (P112649WO01)

[0032] 4 of 62

[0033] shown on the left-hand side of FIGURE 3 where the entire bandwidth is used for DL transmission in the first three slots, the center portion of the SBFD carrier is used for UL reception while the rest of the carrier continues to be used for DL transmission as shown in the left-hand side of FIGURE 4.

[0034] • Similarly, instead of utilizing all carriers for the same DL or UL directions in a conventional TDD system as shown in the right-hand side of FIGURE 3, some carriers in the SBFD system can be used for a different direction than that of the other carriers as shown in the right-hand side of FIGURE 4.

[0035] In the Third Generation Partnership Project (3GPP) Release 18 study, the scope has been limited such that in SBFD operation, only gNodeBs (gNBs) transmit DL and receive UL simultaneously. An individual UE is scheduled in only one direction (DL or UL) at a time.

[0036] In RANI #117, RANI agreed to support two options for Random Access Channel (RACH) configuration, a single RACH configuration and an additional RACH configuration. It was also agreed that a UE is not required to support both configurations, considering the scenarios for the different configurations are substantially different:

[0037] Agreement

[0038] Confirm the following working assumption.

[0039] Working Assumption

[0040] For SBFD-aware UEs in RRC CONNECTED state, both RACH configuration Option 1 with Alt 1-1 (i.e., use one single RACH configuration, and only based on the existing parameters of the single RACH configuration) and RACH configuration Option 2 (i.e., Use two separate RACH configurations, including one legacy RACH configuration and one additional RACH configuration) are supported. Enabling both options at the same time for a UE is not supported.

[0041] For Option 1 with Alt 1-1, FFS whether / how to reinterpret msgl- FrequencyStart in rach-ConfigCommon, RO validation rules and SSB- RO mapping rules, etc.

[0042] - For Option 2, FFS the RO validation rules, SSB-RO mapping rules, whether all the parameters currently in rach-ConfigCommon are necessary to be included in the additional RACH configuration, etc.

[0043] UE is not required to support both options.

[0044] The single RACH configuration i.e., RACH configuration Option 1 with Alt 1-1, may provide larger RACH capacity and lower latency. The second SBFD RACH configuration ATTORNEY’S DOCKET PATENT APPLICATION 017997.4336 (P112649WO01)

[0045] 5 of 62

[0046] i.e., RACH configuration Option 2, will provide increased coverage and range (and higher RACH capacity). Higher RACH capacity comes at the expense of increased overhead, in particular for requiring more ROs in already scarce UL resources, and adding even more ROs. In practice, a cell needs to provide both lower latency, and increased coverage and range, which is not reasonable.

[0047] There currently exist certain challenges. For example, for SBFD Work Item (WI) in Release 19, an SBFD aware UE in a cell capable of SBFD operation would be able to perform UL transmissions in both non-SBFD symbols (e.g., configured as UL or flexible by TDD-DL-UL common) and SBFD slots / symbols (i.e., configured as DL by TDD-DL-UL common).

[0048] For a SBFD aware UE, the UE can choose either legacy RO or SBFD RO for its RA operation. The issue on how to select ROs for the UE is being under discussion in 3GPP. RAN2 has made the below agreements in RAN2#128:

[0049] • For Future Study (FFS) on the following options

[0050] • Option 1:

[0051] • Upon initiation of RACH procedure for a SBFD-aware UE, network provides the indication on the prioritization of the additional ROs over legacy RO

[0052] • If there is no such indication from the network, FFS on the following mechanism:

[0053] • UE select legacy RO or SBFD RO based on Synchronization Signal Block (SSB) Reference Signal Received Power (RSRP), or

[0054] • UE select the legacy RO, or

[0055] • UE select the SBFD RO, or

[0056] • Other metrics than SSB RSRP.

[0057] • Option 2:

[0058] • UE select legacy RO or SBFD RO based on SSB RSRP if such condition is configured, and if not configured, then UE can prioritize one type of the ROs, FFS which one.

[0059] The difference between the two options is the need of network indication on the RO type. The common aspect between the two options is to introduce conditions for the UE to ATTORNEY’S DOCKET PATENT APPLICATION 017997.4336 (P112649WO01)

[0060] 6 of 62

[0061] determine how to select ROs between legacy ROs and SBFD ROs. Regardless of which option to be adopted, there are issues in below to be addressed:

[0062] One issue is that the two RACH configuration options (as described above) are designed for different use cases. The option 1 is aiming for RACH latency reduction or increasing RACH capacity, i.e., referring to as Case 1. While the option 2 is aiming for coverage extension (e.g., UEs in cell edge can improve its coverage with Option 2) or range extension (e.g., to limit additional RO correlation to extended ranges), i.e., referring to as Case 2. In other words, the targeted UE groups are different in both cases. For Case 1, application of SBFD RO may be more suitable to UEs in cell center to avoid CLI. While for Case 2, it may be beneficial to select SBFD RO for UEs in cell edge to improve coverage by applying mechanisms e.g., long PRACH preamble format. Therefore, it is important to study how to define conditions / thresholds to identify target UE groups in different cases accordingly. Solely using one RSRP threshold would not be feasible to identify different UE groups in all cases. In order to cate for different use cases (e.g., latency reduction, capacity increase, coverage enhancement or range extension), additional parameters would need to be introduced in the SBFD RACH configurations. Therefore, it is necessary to study the above issue and develop corresponding solutions.

[0063] SUMMARY

[0064] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. For example, methods and systems are disclosed that provide mechanisms for the gNB and / or the UE (group) to select the most suitable RACH occasions for the triggered random access procedures (by / forthe UE).

[0065] According to certain embodiments, a method by a UE for network-controlled RO prioritization for a SBFD operation includes receiving, from a network node, information indicating at least one UE for using at least one prioritized RACH resource for the SBFD operation.

[0066] According to certain embodiments, a method by a network node for network-controlled RO prioritization for a SBFD operation by at least one UE includes transmitting, to the at least one UE, information indicating at least one prioritized RACH resource for use by the at least one UE for the SBFD operation. ATTORNEY’S DOCKET PATENT APPLICATION 017997.4336 (P112649WO01)

[0067] 7 of 62

[0068] According to certain embodiments, a UE for network-controlled RO prioritization for a SBFD operation includes processing circuitry configured to receive, from a network node, information indicating at least one UE for using at least one prioritized RACH resource for the SBFD operation.

[0069] According to certain embodiments, a network node for network-controlled RO prioritization for a SBFD operation by at least one UE includes processing circuitry configured to transmit, to the at least one UE, information indicating at least one prioritized RACH resource for use by the at least one UE for the SBFD operation.

[0070] Certain embodiments may provide one or more of the following technical advantage(s). For example, certain embodiments may provide a technical advantages of providing feasible options to the gNB to configure / determine RACH occasion types at the cell level for different use cases / purposes (e.g., latency reduction, capacity increase, coverage improvement, or range extension).

[0071] As another example, certain embodiments may provide a technical advantage of providing feasible options to the UE(s) to determine / select RACH occasion types depending on configured conditions / thresholds for different use cases / purposes e.g., latency reduction, capacity increase, coverage improvement or range extension.

[0072] As yet another example, certain embodiments may provide a technical advantage of making it feasible to efficiently exploit benefits / merits of SBFD RACH operation.

[0073] As another example, certain embodiments may provide a technical advantage of achieving a good tradeoff between minimized cross link interference (CLI) and improved RACH performance with SBFD RA operation.

[0074] Other advantages may be readily apparent to one having skill in the art. Certain embodiments may have none, some, or all of the recited advantages.

[0075] BRIEF DESCRIPTION OF THE DRAWINGS

[0076] For a more complete understanding of the disclosed embodiments and their features and advantages, reference is now made to the following description, taken in conjunction with the accompanying drawings, in which:

[0077] FIGURE 1 illustrates FDD and TDD systems;

[0078] FIGURE 2 illustrates an exemplary TDD DL / UL pattern configured by TDD-DL-UL-ConfigCommon ATTORNEY’S DOCKET PATENT APPLICATION 017997.4336 (P112649WO01)

[0079] 8 of 62

[0080] FIGURE 3 illustrates conventional TDD carrier or carrier systems;

[0081] FIGURE 4 illustrates an example SBFD system;

[0082] FIGURE 5 illustrates an example method by a UE for network-controlled RO prioritization for a SBFD operation, according to certain embodiments;

[0083] FIGURE 6 illustrates another example method by a UE for network-controlled RO prioritization for a SBFD operation, according to certain embodiments;

[0084] FIGURE 7 illustrates an example method by a network node for network-controlled RO prioritization for a SBFD operation, according to certain embodiments;

[0085] FIGURE 8 illustrates another example method by a network node for network-controlled RO prioritization for a SBFD operation, according to certain embodiments;

[0086] FIGURE 9 illustrates an example communication system, according to certain embodiments;

[0087] FIGURE 10 illustrates another example of a communication system 600 according to some embodiments;

[0088] FIGURE 11 illustrates an example UE, according to certain embodiments;

[0089] FIGURE 12 illustrates an example network node, according to certain embodiments; and

[0090] FIGURE 13 illustrates a virtualization environment in which functions implemented by some embodiments may be virtualized, according to certain embodiments. ATTORNEY’S DOCKET PATENT APPLICATION 017997.4336 (P112649WO01)

[0091] 9 of 62

[0092] DETAILED DESCRIPTION

[0093] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0094] As used herein, ‘node’ can be a network node or a UE. Examples of network nodes are NodeB, base station (BS), multi-standard radio (MSR) radio node such as MSR BS, eNodeB (eNB), gNodeB (gNB), Master eNB (MeNB), Secondary eNB (SeNB), integrated access backhaul (IAB) node, network controller, radio network controller (RNC), base station controller (BSC), relay, donor node controlling relay, base transceiver station (BTS), Central Unit (e.g. in a gNB), Distributed Unit (e.g. in a gNB), Baseband Unit, Centralized Baseband, C-RAN, access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU), Remote Radio Head (RRH), nodes in distributed antenna system (DAS), core network node (e.g. Mobile Switching Center (MSC), Mobility Management Entity (MME), etc.), Operations & Maintenance (O& M), Operations Support System (OSS), Self-Organizing Network (SON), positioning node (e.g. E-SMLC), etc. The terms network node and radio network node are used interchangeably herein.

[0095] Another example of a node is user equipment (UE), which is a non-limiting term and refers to any type of wireless device communicating with a network node and / or with another UE in a cellular or mobile communication system. Examples of UE are target device, device to device (D2D) UE, vehicular to vehicular (V2V), machine type UE, MTC UE or UE capable of machine to machine (M2M) communication, Personal Digital Assistant (PDA), Tablet, mobile terminals, smart phone, laptop embedded equipment (LEE), laptop mounted equipment (LME), Unified Serial Bus (USB) dongles, etc.

[0096] The term radio access technology (RAT), may refer to any RAT such as, for example, Universal Terrestrial Radio Access Network (UTRA), Evolved Universal Terrestrial Radio Access Network (E-UTRA), narrow band internet of things (NB-IoT), WiFi, Bluetooth, next generation RAT, NR, 4G, 5G, etc. Any of the equipment denoted by the terms node, network node or radio network node may be capable of supporting a single or multiple RATs.

[0097] The term signal or radio signal used herein can be any physical signal or physical channel. Examples of downlink (DL) physical signals are reference signal (RS) such as Primary Synchronization Signal (PSS), Secondary Synchronization Signal (SSS), Channel State ATTORNEY’S DOCKET PATENT APPLICATION 017997.4336 (P112649WO01)

[0098] 10 of 62

[0099] Information-Reference Signal (CSI-RS), Demodulation Reference Signal (DMRS) signals in SS / PBCH block (SSB), discovery reference signal (DRS), Cell Specific Reference Signal (CRS), Positioning Reference Signal (PRS), etc. RS may be periodic. For example, RS occasions carrying one or more RSs may occur with certain periodicity (e.g., 20 ms, 40 ms, etc.). The RS may also be aperiodic.

[0100] Each SSB carries New Radio-Primary Synchronization Signal (NR-PSS), New Radio-Secondary Synchronization Signal (NR-SSS) and New Radio-Physical Broadcast Channel (NR-PBCH) in four successive symbols. One or multiple Synchronization Signal Blocks (SSBs) are transmitted in one SSB burst which is repeated with certain periodicity such as, for example, 5 ms, 10 ms, 20 ms, 40 ms, 80 ms, and 160 ms. The UE is configured with information about SSB on cells of certain carrier frequency by one or more SS / PBCH block measurement timing configuration (SMTC) configurations. The SMTC configuration comprising parameters such as SMTC periodicity, SMTC occasion length in time or duration, SMTC time offset with regard to reference time (e.g., serving cell’s SFN) etc. Therefore, SMTC occasion may also occur with certain periodicity (e.g., 5 ms, 10 ms, 20 ms, 40 ms, 80 ms, and 160 ms). Examples of uplink (UL) physical signals are reference signals such as Sounding Reference Signals (SRS), Demodulation Reference Signals (DMRS), etc. The term physical channel refers to any channel carrying higher layer information e.g. data, control etc. Examples of physical channels are Physical Broadcast Channel (PBCH), Physical Downlink Control Channel (PDCCH), Physical Downlink Shared Channel (PDSCH), Physical Uplink Shared Channel (PUSCH), Physical Uplink Control Channel (PUCCH), Physical Uplink Shared Channel (PUSCH), Short PUSCH (sPUCCH), Short PDSCH (sPDSCH), Short PUCCH (sPUCCH), Short PUSCH (sPUSCH), MTC PDCCH (MPDCCH), Narrowband PBCH (NPBCH), Narrowband PDCCH (NPDCCH), Narrowband PDSCH (NPDSCH), Narrowband PUSCH (NPUSCH), Enhanced PDCCH (E-PDCCH), etc.

[0101] The term time resource used herein may correspond to any type of physical resource or radio resource expressed in terms of length of time. Examples of time resources are symbol, time slot, subframe, radio frame, transmission time interval (TTI), interleaving time, slot, subslot, mini-slot, system frame number (SFN) cycle, hyper-SFN (H-SFN) cycle, etc.

[0102] As used herein, a SBFD aware UE means a UE that is capable of operating in a cell configured with SBFD feature, i.e., the cell / the gNB transmits DL and receive UL ATTORNEY’S DOCKET PATENT APPLICATION 017997.4336 (P112649WO01)

[0103] 11 of 62

[0104] simultaneously in SBFD slots and symbols within a carrier. The UE can be aware of SBFD configurations so that the UE knows which slots / symbols are SBFD capable, which are also referred to as SBFD slots / symbols. This doesn’t mean that the UE needs to support full duplex operation. The UE may or may not support full duplex operation. Such UE may also be capable of operating in a cell configured with legacy DL / UL allocation, i.e., non-SBFD feature and enable the switch between operate SBFD and legacy DL / ULL allocation, i.e., non-SBFD.

[0105] As used herein, a legacy RACH resource includes a RACH resource other than a prioritized RACH resource (i.e., a non-prioritized RACH resource).

[0106] The example embodiments described herein are applicable to SBFD aware UEs. As described herein, methods and systems are disclosed that provide mechanisms for the gNB and / or the UE (group) to select the most suitable RACH occasions for the triggered RA procedures (by / for the UE).

[0107] For example, according to certain embodiments, the gNB is able to provide cell specific configuration to guide UEs in the cell regarding RACH occasion selection. Such choice is beneficial to ensure the cell / system level performance for the targeted use case. The cell specific configuration is feasible especially when the cell / system load is in low or medium level. When the cell / system is congested due to RACH transmissions, it would be necessary to configure only a part of UEs (UE groups), rather than the cell specific configuration to apply SBFD RA operation. With properly configured settings / conditions / thresholds, only the UEs which really need to apply SBFD RA operation are selected.

[0108] For example, according to certain embodiments, in a CB RACH configuration configuring RACH resources for SBFD operation, a gNB provides information indicating the target UE group(s) that can use the CB RACH resources.

[0109] In a particular embodiment, the RACH resources may comprise at least one of the following:

[0110] • RACH occasions (ROs) which may be located in frequency domain and / or time domain;

[0111] • PRACH preambles and / or associated PRACH preamble formats; and • RACH power control parameters.

[0112] As a further particular embodiment, the information indicating the target UE group(s) may comprise at least one of: ATTORNEY’S DOCKET PATENT APPLICATION 017997.4336 (P112649WO01)

[0113] 12 of 62

[0114] • one or multiple group indices indicating the UE group(s) which are associated with the group indices;

[0115] • one or multiple UE indices associated with the target UEs;

[0116] • one or multiple beam IDs associated with the specific / target beams serving the target UEs, e.g.,

[0117] a. IDs of SS / PBCH block serving the target UEs

[0118] b. IDs of CSI-RSs associated with the beams serving the target UEs c. This may be only applicable to UEs in RRC CONNECTED d. IDs of TCI states associated with the target UEs

[0119] i. This may be only applicable to UEs in RRC CONNECTED;

[0120] • one RSRP threshold for indicating the target UEs:

[0121] a. In an example, the UEs that have measured SSB RSRP is above the RSRP threshold are the target UEs.

[0122] b. In an example, the UEs that have measured SSB RSRP is below the RSRP threshold are the target UEs.

[0123] c. In an example, the UEs that have measured CSI-RS RSRP is above the RSRP threshold are the target UEs.

[0124] d. In an example, the UEs that have measured CSI-RS RSRP is below the RSRP threshold are the target UEs.

[0125] As an additional embodiment, in the RACH configuration, one RSRP threshold plus one indicator are applied together to indicate the target UEs. The indicator indicates how the UE shall perform measurements of its DL RSRP towards the threshold.

[0126] In an example particular embodiment, the indicator with the value ‘ 1 ’ or ‘above’ means that the UE is one target UE when the UE’s RSRP is above the threshold, while the indicator with the value ‘0’ or ‘below’ means that the UEis one target UE when the UE’s RSRP is below the threshold.

[0127] In an example particular embodiment, the indicator with the value ‘ 1 ’ or ‘below’ means that the UE is one target UE when the UE’s RSRP is below the threshold, while the indicator with the value ‘0’ or ‘above’ means that the UE is one target UE when the UE’s RSRP is above the threshold. ATTORNEY’S DOCKET PATENT APPLICATION 017997.4336 (P112649WO01)

[0128] 13 of 62

[0129] As an additional particular embodiment, when the network doesn’t signal any RSRP threshold or any other indicators to indicate the group of UEs which can apply Contentionbased (CB) RACH resources (configured for SBFD RA operation), it is up to the UE implementation to determine to use SBFD RA resources or legacy RA resources (or non SBFD RA resources).

[0130] The embodiments are applicable to UEs in any RRC state unless otherwise stated. In a particular embodiment, the prioritization is related to the PRACH configuration according to a specification such that in case a single RACH configuration, common for both legacy ROs and additional ROs, is used, the UE initially prioritizes additional ROs whereas in case an additional RACH configuration, separate from the legacy RACH configuration, is used, the UE initially prioritizes legacy ROs, or vice versa.

[0131] In a particular embodiment, the UE group index may be associated with critical Quality of Service (QoS) requirements (e.g., a latency requirement), in which case a UE belonging to said group may prioritize the first available RO, regardless of said RO being a legacy RO or an additional RO. The group is established in a way to consider QoS requirements associated with UEs’ services / applications. A RA procedure triggered by / for a UE in the group is associated with critical QoS requirements (e.g., stringent latency requirement). Therefore, it is beneficial to apply the first available RO for the UE. Meanwhile, a RA procedure triggered by / for another UE not belonging to the group is assumed to be not associated with critical QoS requirements (e.g., delay insensitive). Therefore, the other UE may be not required to choose the first available RO.

[0132] In a particular embodiment, in case a preceding PRACH attempt has been deemed to be unsuccessful, a subsequent PRACH attempt may depend on the previous PRACH attempt, as provided in a specification or by a configuration, according to:

[0133] • the subsequent PRACH attempt is the same as the preceding unsuccessful PRACH attempt, or

[0134] • the subsequent PRACH attempt is different from the preceding unsuccessful PRACH attempt.

[0135] In a particular embodiment, following upon an unsuccessful preceding RACH procedure, according to a specification or a configuration: ATTORNEY’S DOCKET PATENT APPLICATION 017997.4336 (P112649WO01)

[0136] 14 of 62

[0137] • a subsequent RACH procedure may be the same as the unsuccessful previous RACH procedure, or

[0138] • a subsequent RACH procedure may be different from the unsuccessful previous RACH procedure.

[0139] In an example, the same RACH procedure implies using the same RACH configuration and a different procedure implies a procedure using a different RACH configuration. As another example, the same RACH procedure means RACH transmissions / attempts serving the same RACH trigger event, and a different procedure implies RACH transmissions / attempts serving a different RACH trigger event.

[0140] In a particular embodiment, the network signals cell specific indicators on the RO type for contention based RA procedures to UEs wherein the indicators indicates one of the below choices

[0141] • the legacy ROs

[0142] • the additional ROs

[0143] • the first available ROs

[0144] o the first available ROs may be either legacy ROs or additional ROs. In this option, the UE will select the first available ROs for its random access procedure regardless of its RO type.

[0145] Upon reception of the cell specific indicators, the UE selects the RO according to the indicators as described in the above meanwhile ignoring the signaling / indicator / condition / threshold configured for the UE group or the UE dedicatedly.

[0146] Examples of ASN.1 Code

[0147] An example of the ASN.1 code implementing the proposed RSRP threshold(s), in the RRC spec v 18.3.0 for IE RACH-ConfigCommon is provided below. In this example, two RSRP thresholds are defined in the IE, wherein one threshold (i.e., rsrp-ThresholdHigh-SBFDRO-r19) is used to identify the SBFD aware UEs in the cell center, which may be suitable to select the SBFD ROs when contention based random access procedures are triggered; the other threshold (i.e., rsrp-ThresholdLow-SBFDRO-r19) is used to identify the SBFD aware UEs in the cell edge, which may be suitable to select the SBFD ROs when contention based random access procedures are triggered. ATTORNEY’S DOCKET PATENT APPLICATION 017997.4336 (P112649WO01)

[0148] 15 of 62

[0149] - RACH-ConfigCommon

[0150] The IE RACH-ConfigCommon is used to specify the cell specific random-access parameters.

[0151] RACH-ConfigCommon information element

[0152] — ASN1START

[0153] — TAG-RACH-CONFI GCOMMON-START

[0154] RACH-ConfigCommon:: = SEQUENCE {

[0155] rach-ConfigGeneric RACH-ConfigGeneric,

[0156] totalNumberOfRA-Preambles INTEGER ( 1.. 63 )

[0157] OPTIONAL, — Need S

[0158] ssb-perRACH-OccasionAndCB-PreamblesPerSSB CHOICE {

[0159] oneEighth ENUMERATED { n4, n8, n12, n16, n20, n24, n28, n32, n36, n40, n44, n48, n52, n56, n60, n64 }, oneFourth ENUMERATED { n4, n8, n12, n16, n20, n24, n28, n32, n36, n40, n44, n48, n52, n56, n60, n64 }, oneHalf ENUMERATED { n4, n8, n12, n16, n20, n24, n28, n32, n36, n40, n44, n48, n52, n56, n60, n64 }, one ENUMERATED { n4, n8, n12, n16, n20, n24, n28, n32, n36, n40, n44, n48, n52, n56, n60, n64 }, two ENUMERATED { n4, n8, n12, n16, n20, n24, n28, n32 },

[0160] four INTEGER ( 1.. 16 ),

[0161] eight INTEGER ( 1.. 8 ),

[0162] sixteen INTEGER ( 1.. 4 )

[0163] } OPTIONAL, Need M

[0164] groupBConfigured SEQUENCE {

[0165] ra-Msg3SizeGroupA ENUMERATED { b56, b144, b208, b256, b282, b480, b640,

[0166] b800, b1000, b72, spare6, spared, spare4, spare3, spare2, sparel ),

[0167] messagePowerOffsetGroupB ENUMERATED { minusinfinity, dB0, dB5, dB8, dB10, dB12, dB15, dB18 },

[0168] numberOfRA-PreamblesGroupA INTEGER ( 1.. 64 )

[0169] } OPTIONAL, Need R

[0170] ra-ContentionResolutionTimer ENUMERATED { s f8, sf16, s f24, s f32, s f40, s f48, s f56, s f64 },

[0171] rsrp-ThresholdSSB RSRP-Range

[0172] OPTIONAL, — Need R

[0173] rsrp-ThresholdSSB-SUL RSRP-Range

[0174] OPTIONAL, — Cond SUL

[0175] prach-RootSequenceIndex CHOICE {

[0176] 1839 INTEGER ( 0.. 837 ),

[0177] 1139 INTEGER ( 0.. 137 ) ATTORNEY’S DOCKET PATENT APPLICATION 017997.4336 (P112649WO01)

[0178] 16 of 62

[0179] },

[0180] msg1-SubcarrierSpacing SubcarrierSpacing

[0181] OPTIONAL, — Cond L139

[0182] restrictedSetConfig ENUMERATED { unrestrictedSet, restrictedSetTypeA, restrictedSetTypeB },

[0183] msg3-transformPrecoder ENUMERATED { enabled}

[0184] OPTIONAL, — Need R

[0185] ra-PrioritizationForAccessIdentity-rl6 SEQUENCE {

[0186] ra-Prioritization-r16 RA-Prioritization,

[0187] ra-PrioritizationForAI-r16 BIT STRING ( SIZE (2 ) )

[0188] } OPTIONAL, Cond InitialBWP-Only

[0189] prach-RootSequenceIndex-r16 CHOICE {

[0190] 1571 INTEGER ( 0.. 569 ),

[0191] 11151 INTEGER ( 0..1149 )

[0192] } OPTIONAL — Need R

[0193] ] ],

[0194] [ [

[0195] ra-PrioritizationForSlicing-r17 RA-PrioritizationForSlicing-r17 OPTIONAL, — Cond InitialBWP-Only

[0196] featureCombinationPreamblesList-r17 SEQUENCE

[0197] ( SIZE ( 1..maxFeatureCombPreamblesPerRACHResource-rl7 ) ) OF FeatureCombinationPreambles-rl7 OPTIONAL -- Cond AdditionalRACH

[0198] ] ],

[0199] [ [

[0200] rsrp-ThresholdHigh-SBFDRO-rl9 RSRP -Range

[0201] OPTIONAL, — Cond SBFDCarrier

[0202] rsrp-ThresholdLow-SBFDRO-r19 RSRP -Range

[0203] OPTIONAL — Cond SBFDCarrier

[0204] H

[0205] }

[0206] — TAG-RACH-CONFIGCOMMON-STOP

[0207] — ASN1STOP

[0208] _ RACH-ConfigCommon field descriptions _ featureCombinationPreamblesList

[0209] Specifies a series of preamble partitions each associated to a combination of features and 4-step RA.

[0210] The network does not configure this list to have more than 16 entries. _ messagePowerOffsetGroupB

[0211] Threshold for preamble selection. Value is in dB. Value minusinfinity corresponds to -infinity. Value dB0 corresponds to 0 dB, dB5 corresponds to 5 dB and so on (see TS 38.321 [3], clause 5.1.2). This field is set to the same value for different repetition numbers associated with a specific

[0212] Feature Combination. _

[0213] msg1 -SubcarrierSpacing

[0214] Subcarrier spacing of PRACH (see TS 38.211

[0016] , clause 5.3.2).

[0215] Only the following values are applicable depending on the used frequency:

[0216] FR1: 15 or 30 kHz

[0217] FR2-1: 60 or 120 kHz

[0218]

[0219] FR2-2: 120, 480, or 960 kHz ATTORNEY’S DOCKET PATENT APPLICATION 017997.4336 (P112649WO01)

[0220] 17 of 62

[0221] If absent, the UE applies the SCS as derived from the prach-Configurationlndex in RACH- ConfigGeneric (see tables Table 6.3.3.1-1, Table 6.3.3.1-2, Table 6.3.3.2-2 and Table 6.3.3.2-3, TS 38.211

[0016] ). The value also applies to contention free random access (RACH-ConfigDedicated), to Sl- request and to contention-based beam failure recovery (CB-BFR). But it does not apply for contention free beam failure recovery (CF-BFR) (see BeamFailureRecoveryConfig).

[0222] msg3-transformPrecoder

[0223] Enables the transform precoder for Msg3 transmission according to clause 6.1.3 of TS 38.214

[0019] , If the field is absent, the UE disables the transformer precoder (see TS 38.213

[0013] , clause 8.3).

[0224] numberOfRA-PreamblesGroupA

[0225] The number of CB preambles per SSB in group A. This determines implicitly the number of CB preambles per SSB available in group B. (see TS 38.321 [3], clause 5.1.1). The setting should be consistent with the setting of ssb-perRACH-OccasionAndCB-PreamblesPerSSB.

[0226] prach-RootSequenceIndex

[0227] PRACH root sequence index (see TS 38.211

[0016] , clause 6.3.3.1). The value range depends on whether L=839 or L=139 or L=571 or L=1151. The length of the root sequence corresponding with the index indicated in this IE should be consistent with the one indicated in prach-Configurationlndex in the RACH-ConfigDedicated (if configured). If prach-RootSequenceIndex-r16 is signalled, UE shall ignore the prach-RootSequenceIndex (without suffix).

[0228] For FR2-2, only the following values are applicable depending on the used subcarrier spacing:

[0229] 120 kHz: L=139, L=571, and L=1151

[0230] 480 kHz: L=139, and L=571

[0231] 960 kHz: L=139

[0232] ra-ContentionResolutionTimer

[0233] The initial value for the contention resolution timer (see TS 38.321 [3], clause 5.1.5). Value sf8 corresponds to 8 subframes, value sf16 corresponds to 16 subframes, and so on.

[0234] ra-Msg3SizeGroupA

[0235] Transport Blocks size threshold in bits below which the UE shall use a contention-based RA preamble of group A (see TS 38.321 [3], clause 5.1.2). This field is set to the same value for different repetition numbers associated with a specific FeatureCombination.

[0236] ra-Prioritization

[0237] Parameters which apply for prioritized random access procedure on any UL BWP of SpCell for specific Access Identities (see TS 38.321 [3], clause 5.1.1a).

[0238] ra-PrioritizationForAI

[0239] Indicates whether the field ra-Prioritization-r16 applies for Access Identities. The first / leftmost bit corresponds to Access Identity 1, the next bit corresponds to Access Identity 2. Value 1 indicates that the field ra-Prioritization-r16 applies otherwise the field does not apply (see TS 23.501

[0032] ).

[0240] ra-PrioritizationForSlicing

[0241] Parameters which apply to configure prioritized CBRA 4-step random access type for slicing.

[0242] rach-ConfigGeneric

[0243] RACH parameters for both regular random access and beam failure recovery.

[0244] restrictedSetConfig

[0245] Configuration of an unrestricted set or one of two types of restricted sets, see TS 38.211

[0016] , clause 6.3.3.1.

[0246] rsrp-ThresholdHigh-SBFDRO

[0247] Threshold used by the SBFD aware UE for determining whether to select SBFD RO or legacy RO upon triggering of a random access procedure using contention-based random access preamble(s) when there is no RO type indicated by the gNB for random access procedures using contention-based random access preambles in this BWP. The SBFD aware UE selects SBFD ROs when its measured SSB RSRP is higher than the threshold, otherwise selects legacy ROs. This field is not configured together with rsrp-ThresholdLow-SBFDRO. If both this field and rsrp-ThresholdLow-SBFDRO are absent, it is up to the UE implementation to determine whether to select SBFD RO or legacy RO upon triggering of a random access procedure using contention-based random access preamble(s) when there is no RO type indicated by the gNB for random access procedures using contention-based random access preambles in this BWP.

[0248]

[0249] rsrp-ThresholdLow-SBFDRO ATTORNEY’S DOCKET PATENT APPLICATION 017997.4336 (P112649WO01)

[0250] 18 of 62

[0251] Threshold used by the SBFD aware UE for determining whether to select SBFD RO or legacy RO upon triggering of a random access procedure using contention-based random access preamble(s) when there is no RO type indicated by the gNB for random access procedures using contention-based random access preambles in this BWP. The SBFD aware UE selects SBFD ROs when its measured SSB RSRP is lower than the threshold, otherwise selects legacy ROs. This field is not configured together with rsrp-ThresholdHigh-SBFDRO. If both this field and rsrp-ThresholdHigh-SBFDRO are absent, it is up to the UE implementation to determine whether to select SBFD RO or legacy RO upon triggering of a random access procedure using contention-based random access preamble(s) when there is no RO type indicated by the gNB for random access procedures using contention-based random access preambles in this BWP.

[0252] rsrp-ThresholdSSB

[0253] UE may select the SS block and corresponding PRACH resource for path-loss estimation and (re)transmission based on SS blocks that satisfy the threshold (see TS 38.213

[0013] ).

[0254] rsrp-ThresholdSSB-SUL

[0255] The UE selects SUL carrier to perform random access based on this threshold (see TS 38.321 [3], clause 5.1.1). The value applies to all the BWPs and all RACH configurations.

[0256] ssb-perRACH-OccasionAndCB-PreamblesPerSSB

[0257] The meaning of this field is twofold: the CHOICE conveys the information about the number of SSBs per RACH occasion. Value oneEighth corresponds to one SSB associated with 8 RACH occasions, value oneFourth corresponds to one SSB associated with 4 RACH occasions, and so on. The ENUMERATED part indicates the number of Contention Based preambles per SSB. Value n4 corresponds to 4 Contention Based preambles per SSB, value n8 corresponds to 8 Contention Based preambles per SSB, and so on. The total number of CB preambles in a RACH occasion is given by CB- preambles-per-SSB * max(1, SSB-per-rach-occasion). See TS 38.213

[0013] ,

[0258] totalNumberOfRA-Preambles

[0259] Total number of preambles used for contention based and contention free 4-step or 2-step random access in the RACH resources defined in RACH-ConfigCommon, excluding preambles used for other purposes (e.g. for SI request). If the field is absent, all 64 preambles are available for RA. The setting should be consistent with the setting of ssb-perRACH-OccasionAndCB-PreamblesPerSSB, i.e. it

[0260]

[0261] should be a multiple of the number of SSBs per RACH occasion.

[0262] Conditional Presence Explanation

[0263] AdditionalRACH The field is mandatory present if the RACH-ConfigCommon is included in an AdditionalRACH-Config. When included in initialUplinkBWP- RedCap to indicate other feature(s) than redcap and eRedCap, this field is mandatory present with at least FeatureCombinationPreambles list entries: the list entry / entries indicating only redcap or eRedCap and the other(s) indicating both redcap or eRedCap and one or multiple other feature(s) (e.g., smallData, nsag or msg3-Repetitions). When included in initialUplinkBWP-RedCap to indicate eRedCap and RedCap separately, this field is mandatory present with at least two FeatureCombinationPreambles list entries: one list entry indicating only redcap and the other list entry indicating only eRedCap.

[0264] Otherwise, it is optional, Need R.

[0265] InitialBWP-Only This field is optionally present, Need R, if this BWP is the initial BWP of SpCell. Otherwise, the field is absent.

[0266] L139 The field is mandatory present if prach-RootSequenceIndex L=139, or if L=571 for FR2-2, otherwise the field is absent, Need S.

[0267] SBFDCarrier The field is optionally present for the carrier configured with SBFD operation, Need S, otherwise it is absent.

[0268] SUL The field is mandatory present in rach-ConfigCommon in initialUplinkBWP if supplementaryUplink is configured in ServingCellConfigCommonSIB or if supplementaryUplinkConfig is configured in ServingCellConfigCommon, otherwise, the field is absent.

[0269]

[0270] This field is not configured in additionalRACH-Config. ATTORNEY’S DOCKET PATENT APPLICATION 017997.4336 (P112649WO01)

[0271] 19 of 62

[0272] Another example of the ASN.1 code implementing the proposed RSRP threshold(s), in the RRC spec v 18.3.0 for IE RACH-ConfigCommon is disclosed below.

[0273] In this example, two fields / parameters are defined in the IE, wherein one threshold (i.e., rsrp-Threshold-SBFDRO-r19) is used to identify the SBFD aware UEs in the cell, which may be suitable to select the SBFD ROs when contention based random access procedures are triggered; the other parameter (i.e., rsrp-ComparisonInd-SBFD-rl9)' is used to indicate how the SBFD aware UE compares its measured SSB RSRP with rsrp-Threshold-SBFDRO. Value above means that the SBFD aware UE selects SBFD ROs upon triggering of a contention based random access procedure when its measured SSB RSRP is above rsrp-Threshold-SBFDRO, otherwise selects legacy ROs. Value below means that the SBFD aware UE selects SBFD ROs upon triggering of a contention based random access procedure when its measured SSB RSRP is below rsrp-Threshold-SBFDRO, otherwise selects legacy ROs.

[0274] In a variant of this embodiment, the SBFD aware UE is only configured with rsrp-Threshold-SBFDRO-r19 and not rsrp-ComparisonInd-SBFD-rl9. Instead, it determines how to compare its measured SSB RSRP with rsrp-Threshold-SBFDRO based on if it is configured with SBFD ROs using Option 1 (single RACH configuration) or Option 2 (two RACH configurations). In case the SBFD aware UE is configured using Option 1, it selects SBFD ROs upon triggering of a contention based random access procedure when its measured SSB RSRP is above rsrp-Threshold-SBFDRO, otherwise selects legacy ROs, i.e. as if rsrp-ComparisonInd-SBFD-rl9 would have had the value above. In one variant in case the SBFD aware UE is configured using Option 2, it selects SBFD ROs upon triggering of a contention based random access procedure when its measured SSB RSRP is below rsrp-Threshold-SBFDRO, otherwise selects legacy ROs, i.e. as if rsrp-ComparisonInd-SBFD-rl9 would have had the value below. In another variant the UE acts as if rsrp-ComparisonInd-SBFD-rl9 had the value below if it is configured with a longer preamble format in the second RACH configuration compared to the first RACH configuration.

[0275] - RACH-ConfigCommon

[0276] The IE RACH-ConfigCommon is used to specify the cell specific random-access parameters. ATTORNEY’S DOCKET PATENT APPLICATION 017997.4336 (P112649WO01)

[0277] 20 of 62

[0278] RACH-ConfigCommon information element — ASN1START

[0279] — TAG-RACH-CONFI GCOMMON-START

[0280] RACH-ConfigCommon:: = SEQUENCE {

[0281] rach-ConfigGeneric RACH-ConfigGeneric,

[0282] totalNumberOfRA-Preambles INTEGER ( 1.. 63 )

[0283] OPTIONAL, — Need S

[0284] ssb-perRACH-OccasionAndCB-PreamblesPerSSB CHOICE {

[0285] oneEighth ENUMERATED { n4, n8, n12, n16, n20, n24, n28, n32, n36, n40, n44, n48, n52, n56, n60, n64 }, oneFourth ENUMERATED { n4, n8, n12, n16, n20, n24, n28, n32, n36, n40, n44, n48, n52, n56, n60, n64 }, oneHalf ENUMERATED { n4, n8, n12, n16, n20, n24, n28, n32, n36, n40, n44, n48, n52, n56, n60, n64 }, one ENUMERATED { n4, n8, n12, n16, n20, n24, n28, n32, n36, n40, n44, n48, n52, n56, n60, n64 }, two ENUMERATED { n4, n8, n12, n16, n20, n24, n28, n32 },

[0286] four INTEGER ( 1.. 16 ),

[0287] eight INTEGER ( 1.. 8 ),

[0288] sixteen INTEGER ( 1.. 4 )

[0289] } OPTIONAL, Need M

[0290] groupBConfigured SEQUENCE {

[0291] ra-Msg3SizeGroupA ENUMERATED { b56, b144, b208, b256, b282, b480, b640,

[0292] b800, b1000, b72, spare6, spared, spare4, spare3, spare2, sparel ),

[0293] messagePowerOffsetGroupB ENUMERATED { minusinfinity, dB0, dB5, dB8, dB10, dB12, dB15, dB18 },

[0294] numberOfRA-PreamblesGroupA INTEGER ( 1.. 64 )

[0295] } OPTIONAL, Need R

[0296] ra-ContentionResolutionTimer ENUMERATED { s f8, sf16, s f24, s f32, s f40, s f48, s f56, s f64 },

[0297] rsrp-ThresholdSSB RSRP-Range

[0298] OPTIONAL, — Need R

[0299] rsrp-ThresholdSSB-SUL RSRP-Range

[0300] OPTIONAL, — Cond SUL

[0301] prach-RootSequenceIndex CHOICE {

[0302] 1839 INTEGER ( 0.. 837 ),

[0303] 1139 INTEGER ( 0.. 137 )

[0304] },

[0305] msg1-SubcarrierSpacing SubcarrierSpacing

[0306] OPTIONAL, — Cond L139 ATTORNEY’S DOCKET PATENT APPLICATION 017997.4336 (P112649WO01)

[0307] 21 of 62

[0308] restrictedSetConfig ENUMERATED { unrestrictedSet, restrictedSetTypeA, restrictedSetTypeB },

[0309] msg3-transformPrecoder ENUMERATED { enabled}

[0310] OPTIONAL, — Need R

[0311] ra-PrioritizationForAccessIdentity-rl6 SEQUENCE {

[0312] ra-Prioritization-r16 RA-Prioritization,

[0313] ra-PrioritizationForAI-r16 BIT STRING ( SIZE (2 ) )

[0314] } OPTIONAL, Cond InitialBWP-Only

[0315] prach-RootSequenceIndex-rl6 CHOICE {

[0316] 1571 INTEGER ( 0.. 569 ),

[0317] 11151 INTEGER ( 0..1149 )

[0318] } OPTIONAL — Need R

[0319] ] ],

[0320] [ [

[0321] ra-PrioritizationForSlicing-r17 RA-PrioritizationForSlicing-r17 OPTIONAL, — Cond InitialBWP-Only

[0322] f eatureCombinationPreamblesList-r!7 SEQUENCE

[0323] ( SIZE ( 1..maxFeatureCombPreamblesPerRACHResource-rl7 ) ) OF FeatureCombinationPreambles-rl7 OPTIONAL -- Cond AdditionalRACH

[0324] ] ],

[0325] £[

[0326] rsrp-Indicators-SBFDRO-rl9 SEQUENCE {

[0327] _ rsrp-Threshold-SBFDRO-rl9 _ RSRP -Range,

[0328] > rsrp-ComparisonInd-SBFD-rl9 ENUMERATED {above, below}

[0329] _} OPTIONAL — Cond SBFDCarrier

[0330] H

[0331] }

[0332] — TAG-RACH-CONFIGCOMMON-STOP

[0333] — ASN1STOP

[0334] RACH-ConfigCommon field descriptions featureCombinationPreamblesList

[0335] Specifies a series of preamble partitions each associated to a combination of features and 4-step RA. The network does not configure this list to have more than 16 entries.

[0336] messagePowerOffsetGroupB

[0337] Threshold for preamble selection. Value is in dB. Value minusinfinity corresponds to -infinity. Value dB0 corresponds to 0 dB, dB5 corresponds to 5 dB and so on (see TS 38.321 [3], clause 5.1.2). This field is set to the same value for different repetition numbers associated with a specific

[0338] Feature Combination.

[0339] msg1 -SubcarrierSpacing

[0340] Subcarrier spacing of PRACH (see TS 38.211

[0016] , clause 5.3.2).

[0341] Only the following values are applicable depending on the used frequency:

[0342] FR1: 15 or 30 kHz

[0343] FR2-1: 60 or 120 kHz

[0344] FR2-2: 120, 480, or 960 kHz

[0345] If absent, the UE applies the SCS as derived from the prach-Configurationlndex in RACH- ConfigGeneric (see tables Table 6.3.3.1-1, Table 6.3.3.1-2, Table 6.3.3.2-2 and Table 6.3.3.2-3, TS

[0346]

[0347] 38.211

[0016] ). The value also applies to contention free random access (RACH-ConfigDedicated), to SI- ATTORNEY’S DOCKET PATENT APPLICATION 017997.4336 (P112649WO01)

[0348] 22 of 62

[0349] request and to contention-based beam failure recovery (CB-BFR). But it does not apply for contention free beam failure recovery (CF-BFR) (see BeamFailureRecoveryConfig).

[0350] msg3-transformPrecoder

[0351] Enables the transform precoder for Msg3 transmission according to clause 6.1.3 of TS 38.214

[0019] , If the field is absent, the UE disables the transformer precoder (see TS 38.213

[0013] , clause 8.3).

[0352] numberOfRA-PreamblesGroupA

[0353] The number of CB preambles per SSB in group A. This determines implicitly the number of CB preambles per SSB available in group B. (see TS 38.321 [3], clause 5.1.1). The setting should be consistent with the setting of ssb-perRACH-OccasionAndCB-PreamblesPerSSB.

[0354] prach-RootSequenceIndex

[0355] PRACH root sequence index (see TS 38.211

[0016] , clause 6.3.3.1). The value range depends on whether L=839 or L=139 or L=571 or L=1151. The length of the root sequence corresponding with the index indicated in this IE should be consistent with the one indicated in prach-Configurationlndex in the RACH-ConfigDedicated (if configured). If prach-RootSequenceIndex-r16 is signalled, UE shall ignore the prach-RootSequenceIndex (without suffix).

[0356] For FR2-2, only the following values are applicable depending on the used subcarrier spacing:

[0357] 120 kHz: L=139, L=571, and L=1151

[0358] 480 kHz: L=139, and L=571

[0359] 960 kHz: L=139

[0360] rsrp-Comparisonlnd-SBFD

[0361] Indicate how the SBFD aware UE compares its measured SSB RSRP with rsro-Threshold- SBFDRO. Value above means that the SBFD aware UE selects SBFD ROs upon triaaerina of a contention based random access procedure when its measured SSB RSRP is above rsrp- Threshold-SBFDRO, otherwise selects leqacv ROs. Value below means that the SBFD aware UE selects SBFD ROs upon triaaerina of a contention based random access procedure when its measured SSB RSRP is below rsro-Threshold-SBFDRO. otherwise selects leaacv ROs. ra-ContentionResolutionTimer

[0362] The initial value for the contention resolution timer (see TS 38.321 [3], clause 5.1.5). Value sf8 corresponds to 8 subframes, value sf16 corresponds to 16 subframes, and so on.

[0363] ra-Msg3SizeGroupA

[0364] Transport Blocks size threshold in bits below which the UE shall use a contention-based RA preamble of group A (see TS 38.321 [3], clause 5.1.2). This field is set to the same value for different repetition numbers associated with a specific FeatureCombination.

[0365] ra-Prioritization

[0366] Parameters which apply for prioritized random access procedure on any UL BWP of SpCell for specific Access Identities (see TS 38.321 [3], clause 5.1.1a).

[0367] ra-PrioritizationForAI

[0368] Indicates whether the field ra-Prioritization-r16 applies for Access Identities. The first / leftmost bit corresponds to Access Identity 1, the next bit corresponds to Access Identity 2. Value 1 indicates that the field ra-Prioritization-r16 applies otherwise the field does not apply (see TS 23.501

[0032] ).

[0369] ra-PrioritizationForSlicing

[0370] Parameters which apply to configure prioritized CBRA 4-step random access type for slicing.

[0371] rach-ConfigGeneric

[0372] RACH parameters for both regular random access and beam failure recovery.

[0373] restrictedSetConfig

[0374] Configuration of an unrestricted set or one of two types of restricted sets, see TS 38.211

[0016] , clause 6.3.3.1.

[0375] rsrp-lndicators-SBFDRO

[0376] Confiauration of RSRP based conditions which the SBFD aware UE uses to select SBFD RO or leaacv RO upon triaaerina of a random access procedure usina contention-based random access preamble(s) when there is no RO tvpe indicated bv the aNB for random access procedures usina contention-based random access preambles in this BWP. If this field is absent, it is up to the UE implementation to determine whether to select SBFD RO or leaacv RO upon triaaerina of a random access procedure usina contention-based random access preamble(s) when there is no RO tvpe indicated bv the aNB for random access procedures

[0377]

[0378] usina contention-based random access preambles in this BWP. ATTORNEY’S DOCKET PATENT APPLICATION 017997.4336 (P112649WO01)

[0379] 23 of 62

[0380] rsrp-ThresholdSSB

[0381] UE may select the SS block and corresponding PRACH resource for path-loss estimation and (re)transmission based on SS blocks that satisfy the threshold (see TS 38.213

[0013] ). _

[0382] rsrp-ThresholdSSB-SUL

[0383] The UE selects SUL carrier to perform random access based on this threshold (see TS 38.321 [3], clause 5.1.1). The value applies to all the BWPs and all RACH configurations. _

[0384] rsrp- Threshold-SBFDRO

[0385] Threshold used by the SBFD aware UE for determining whether to select SBFD RO or legacy RO upon triggering of a random access procedure using contention-based random access preamble(s) when there is no RO type indicated by the gNB for random access procedures using contention-based random access preambles in this BWP. ssb-perRACH-OccasionAndCB-PreamblesPerSSB

[0386] The meaning of this field is twofold: the CHOICE conveys the information about the number of SSBs per RACH occasion. Value oneEighth corresponds to one SSB associated with 8 RACH occasions, value oneFourth corresponds to one SSB associated with 4 RACH occasions, and so on. The ENUMERATED part indicates the number of Contention Based preambles per SSB. Value n4 corresponds to 4 Contention Based preambles per SSB, value n8 corresponds to 8 Contention Based preambles per SSB, and so on. The total number of CB preambles in a RACH occasion is given by CB- preambles-per-SSB * max(1, SSB-per-rach-occasion). See TS 38.213

[0013] , _

[0387] totalNumberOfRA-Preambles

[0388] Total number of preambles used for contention based and contention free 4-step or 2-step random access in the RACH resources defined in RACH-ConfigCommon, excluding preambles used for other purposes (e.g. for SI request). If the field is absent, all 64 preambles are available for RA. The setting should be consistent with the setting of ssb-perRACH-OccasionAndCB-PreamblesPerSSB, i.e. it should be a multiple of the number of SSBs per RACH occasion.

[0389]

[0390] Conditional Presence Explanation

[0391] AdditionalRACH The field is mandatory present if the RACH-ConfigCommon is included in an AdditionalRACH-Config. When included in initialUplinkBWP-RedCap to indicate other feature(s) than redcap and eRedCap, this field is mandatory present with at least FeatureCombinationPreambles list entries: the list entry / entries indicating only redcap or eRedCap and the other(s) indicating both redcap or eRedCap and one or multiple other feature(s) (e.g., smallData, nsag or msg3-Repetitions). When included in initialUplinkBWP- RedCap to indicate eRedCap and RedCap separately, this field is mandatory present with at least two FeatureCombinationPreambles list entries: one list entry indicating only redcap and the other list entry indicating only eRedCap. Otherwise, it is optional, Need R.

[0392] InitialBWP-Only This field is optionally present, Need R, if this BWP is the initial BWP of SpCell. Otherwise, the field is absent.

[0393] L139 The field is mandatory present if prach-RootSeguencelndex L=139, or if L=571 for FR2-2, otherwise the field is absent, Need S.

[0394] SBFDCarrier The field is optionally present for the carrier confiaured with SBFD operation. Need S, otherwise it is absent.

[0395] SUL The field is mandatory present in rach-ConfigCommon in initialUplinkBWPif supplementaryUplink is configured in ServingCellConfigCommonSIB or if supplementaryUplinkConfig is configured in ServingCellConfigCommon; otherwise, the field is absent. This field is not configured in additionalRACH-

[0396]

[0397] Config.

[0398] FIGURE 5 illustrates an example method 100 by a UE for network-controlled RO prioritization for a SBFD operation, according to certain embodiments. In the illustrated embodiment, the method 100 includes a receiving step at 102. For example, at step 102, the ATTORNEY’S DOCKET PATENT APPLICATION 017997.4336 (P112649WO01)

[0399] 24 of 62

[0400] UE may receive, from a network node, information indicating at least one target UE for using at least one RACH resource for the SBFD operation.

[0401] In various particular embodiments, the UE may perform any of the operations and steps or include any of the features described with respect to the Group A and C Example Embodiments below or any other embodiments described herein.

[0402] FIGURE 6 illustrates another example method 200 by a UE for network-controlled RO prioritization for a SBFD operation, according to certain embodiments. In the illustrated embodiment, the method 100 includes a step 202 of receiving, from a network node, information indicating at least one UE for using at least one prioritized RACH resource for the SBFD operation.

[0403] In a particular embodiment, the at least one prioritized RACH resource comprises at least one CB RACH resource, and the information is received in and / or with a CB RACH configuration.

[0404] In a particular embodiment, the at least one prioritized RACH resource comprises at least one of: at least one RO in a frequency domain and / or time domain; at least one PRACH preamble and / or at least one associated PRACH preamble format; and at least one RACH power control parameter.

[0405] In a particular embodiment, the information indicating the at least one UE comprises information indicating at least one UE group for using the at least one prioritized RACH resource.

[0406] In a particular embodiment, based on the information received from the network node, the UE determines that the UE is in the UE group for using the at least one prioritized RACH resource. Based on the UE being in the UE group, the UE selects the at least one prioritized RACH resource for the SBFD operation.

[0407] In a further particular embodiment, based on the information received from the network node, the UE determines that the UE is not in the UE group for using the at least one prioritized RACH resource. Based on the UE not being in the UE group, the UE selects a legacy RACH resource for the SBFD operation. Thus the UE selects a RACH resource other than a prioritized RACH resource (i.e., a non-prioritized RACH resource).

[0408] In a particular embodiment, the information indicating the at least one UE for using the at least one prioritized RACH resource comprises a RSRP threshold. ATTORNEY’S DOCKET PATENT APPLICATION 017997.4336 (P112649WO01)

[0409] 25 of 62

[0410] In a further particular embodiment, the UE is in the UE group when: a measured RSRP of one or more SSB resources is above the RSRP threshold, a measured RSRP of one or more SSB resources is below the RSRP threshold, a measured RSRP of one or more CSI-RS resources is above the RSRP threshold, or a measured RSRP of one or more CSI-RS resources is below the RSRP threshold.

[0411] In a particular embodiment, the information indicating the at least one UE for using the at least one prioritized RACH resource comprises an indicator for applying the RSRP threshold, and the method comprises determining whether the UE is in the UE group based on the indicator and the RSRP threshold.

[0412] In a particular embodiment, when determining whether the UE is in the UE group, the UE determines:

[0413] • the UE is in the UE group when a value of the indicator is ‘ U or ‘above’ and the measured RSRP is above the RSRP threshold,

[0414] • the UE is not in the UE group when a value of the indicator is ‘I’ or ‘above’ and the measured RSRP is not above the RSRP threshold,

[0415] • the UE is in the UE group when a value of the indicator is ‘0’ or ‘below’ and the measured RSRP is below the RSRP threshold,

[0416] • the UE is not in the UE group when a value of the indicator is ‘0’ or ‘below’ and the measured RSRP is not below the RSRP threshold,

[0417] • the UE is in the UE group when a value of the indicator is ‘I’ or ‘below’ and the measured RSRP is below the RSRP threshold,

[0418] • the UE is not in the UE group when a value of the indicator is ‘1’ or ‘below’ and the measured RSRP is not below the RSRP threshold,

[0419] • the UE is in the UE group when a value of the indicator is ‘0’ or ‘above’ and the measured RSRP is above the RSRP threshold, or

[0420] • the UE is not in the UE group when a value of the indicator is ‘0’ or ‘above’ and the measured RSRP is not above the RSRP threshold.

[0421] In a particular embodiment, the UE determines whether the UE is in the UE group for using the at least one RACH resource based on the RSRP threshold and whether the UE is configured with a single RACH configuration comprising both prioritized RACH resources and legacy RACH resources or two RACH configurations wherein one RACH configuration ATTORNEY’S DOCKET PATENT APPLICATION 017997.4336 (P112649WO01)

[0422] 26 of 62

[0423] comprises prioritized RACH resources and one RACH configuration comprises legacy RACH resources.

[0424] In a particular embodiment, when determining whether the UE is in the UE group for using the at least one RACH resource, the UE determines:

[0425] • the UE is in the UE group when the UE is configured with a single RACH configuration and a measured RSRP is above the RSRP threshold, • the UE is not in the UE group when the UE is configured with a single RACH configuration and the measured RSRP is not above the RSRP threshold, • the UE is in the UE group when the UE is configured with a single RACH configuration and a measured RSRP is below the RSRP threshold, • the UE is not in the UE group when the UE is configured with a single RACH configuration and the measured RSRP is not below the RSRP threshold, • the UE is in the UE group when the UE is configured with two RACH configurations and the measured RSRP is below the RSRP threshold,

[0426] • the UE not in the UE group when the UE is configured with two RACH configurations and the measured RSRP is not below the RSRP threshold • the UE is in the UE group when the UE is configured with two RACH configurations and the measured RSRP is above the RSRP threshold, or • the UE not in the UE group when the UE is configured with two RACH configurations and the measured RSRP is not above the RSRP threshold. FIGURE 7 illustrates an example method 300 by a network node for network-controlled RO prioritization for a SBFD operation, according to certain embodiments. In the illustrated embodiment, the method 300 includes a transmitting step at 302. For example, at step 302, the network node may transmit, to a UE, information indicating at least one target UE for using at least one RACH resource for the SBFD operation.

[0427] In various particular embodiments, the network node may perform any of the operations and steps or include any of the features described with respect to the Group B and D Example Embodiments below or any other embodiments described herein.

[0428] FIGURE 8 illustrates another example method 400 by a network node for network-controlled RO prioritization for a SBFD operation, according to certain embodiments. In the illustrated embodiment, the method 400 includes a step 402 of transmitting, to the at least one ATTORNEY’S DOCKET PATENT APPLICATION 017997.4336 (P112649WO01)

[0429] 27 of 62

[0430] UE, information indicating at least one prioritized RACH resource for use by the at least one UE for the SBFD operation.

[0431] In a particular embodiment, the at least one prioritized RACH resource comprises at least one CB RACH resource, and the information is received in and / or with a CB RACH configuration.

[0432] In a particular embodiment, the at least one prioritized RACH resource comprises at least one of: at least one RO in a frequency domain and / or time domain; at least one PRACH preamble and / or at least one associated PRACH preamble format; and at least one RACH power control parameter.

[0433] In a particular embodiment, the information indicating the at least one UE comprises information indicating at least one UE group for using the at least one prioritized RACH resource.

[0434] In a particular embodiment, the network node configures the at least one UE to determine, based on the information received from the network node, that the UE is in the UE group for using the at least one prioritized RACH resource. The network node also configures the UE to select the at least one prioritized RACH resource for the SBFD operation based on the UE being in the UE group.

[0435] In a particular embodiment, the network node configures the at least one UE to determine, based on the information received from the network node, that the UE is in the UE group for using the at least one prioritized RACH resource. The network also configures the UE to select a legacy RACH resource for the SBFD operation based on the UE not being in the UE group.

[0436] In a particular embodiment, the information indicating the at least one UE comprises a RSRP threshold.

[0437] In a particular embodiment, the UE is the UE group when:

[0438] • a measured RSRP of one or more SSB resources is above the RSRP threshold, • a measured RSRP of one or more SSB resources is below the RSRP threshold, • a measured RSRP of one or more CSI-RS resources is above the RSRP threshold, or

[0439] • a measured RSRP of one or more CSI-RS resources is below the RSRP threshold. ATTORNEY’ S DOCKET PATENT APPLICATION 017997.4336 (P112649WO01)

[0440] 28 of 62

[0441] In a particular embodiment, the information indicating the at least one UE includes an indicator for applying the RSRP threshold.

[0442] In a particular embodiment, at least one of the following holds true:

[0443] • the UE is in the UE group when a value of the indicator is ‘ U or ‘above’ and the measured RSRP is above the RSRP threshold,

[0444] • the UE is not in the UE group when a value of the indicator is ‘I’ or ‘above’ and the measured RSRP is not above the RSRP threshold,

[0445] • the UE is in the UE group when a value of the indicator is ‘0’ or ‘below’ and the measured RSRP is below the RSRP threshold,

[0446] • the UE is not in the UE group when a value of the indicator is ‘0’ or ‘below’ and the measured RSRP is not below the RSRP threshold,

[0447] • the UE is in the UE group when a value of the indicator is ‘I’ or ‘below’ and the measured RSRP is below the RSRP threshold,

[0448] • the UE is not in the UE group when a value of the indicator is ‘1’ or ‘below’ and the measured RSRP is not below the RSRP threshold,

[0449] • the UE is in the UE group when a value of the indicator is ‘0’ or ‘above’ and the measured RSRP is above the RSRP threshold, or

[0450] • the UE is not in the UE group when a value of the indicator is ‘0’ or ‘above’ and the measured RSRP is not above the RSRP threshold.

[0451] In a particular embodiment, the UE is determined to be in the UE group for using the at least one prioritized RACH resource based on the RSRP threshold and whether the UE is configured with a single RACH configuration comprising both prioritized RACH resources and legacy RACH resources or two RACH configurations where one RACH configuration comprises prioritized RACH resources and one RACH configuration comprises legacy RACH resources.

[0452] In a further particular embodiment, one of the following holds true:

[0453] • the UE is in the UE group when the UE is configured with a single RACH configuration and a measured RSRP is above the RSRP threshold, • the UE is not in the UE group when the UE is configured with a single RACH configuration and the measured RSRP is not above the RSRP threshold, ATTORNEY’S DOCKET PATENT APPLICATION 017997.4336 (P112649WO01)

[0454] 29 of 62

[0455] • the UE is in the UE group when the UE is configured with a single RACH configuration and a measured RSRP is below the RSRP threshold, • the UE is not in the UE group when the UE is configured with a single RACH configuration and the measured RSRP is not below the RSRP threshold, • the UE is in the UE group when the UE is configured with two RACH configurations and the measured RSRP is below the RSRP threshold, r

[0456] • the UE not in the UE group when the UE is configured with two RACH configurations and the measured RSRP is not below the RSRP threshold, • the UE is in the UE group when the UE is configured with two RACH configurations and the measured RSRP is above the RSRP threshold, or • the UE not in the UE group when the UE is configured with two RACH configurations and the measured RSRP is not above the RSRP threshold. FIGURE 9 shows an example of a communication system 504 in accordance with some embodiments.

[0457] In the example, the communication system 500 includes a telecommunications network 502 that includes an access network 504, such as a radio access network (RAN), and a core network 506, which includes one or more core network nodes 508. The access network 504 includes one or more access network nodes or base stations of various types, access network nodes 510A and 510B are depicted (which may be collectively referred to as network nodes 510), or any other similar 3rdGeneration Partnership Project (3GPP) access nodes or non-3GPP access points (APs). Some embodiments of the access network 504 may include more than one access network technology. The network nodes 510 of access network 504 facilitate direct or indirect connection of wireless devices, also referred to as user equipments (UEs), such as by connecting UEs 512A, 512B, 512C, and 512D (one or more of which may be generally referred to as UEs 512) to the core network 506 over one or more wireless connections.

[0458] Moreover, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunications network 502 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a network node in the telecommunications network 502 that supports an ORAN specification (e.g., a specification ATTORNEY’S DOCKET PATENT APPLICATION 017997.4336 (P112649WO01)

[0459] 30 of 62

[0460] published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other network nodes to implement one or more functionalities of any network node in the telecommunications network 502, including one or more access network nodes 510 and / or core network nodes 508.

[0461] Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O-CU-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). An ORAN network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an Al, Fl, Wl, El, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN network node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an O-2 interface defined by the O-RAN Alliance or comparable technologies.

[0462] The network nodes 510 facilitate direct or indirect connection of one or more UEs 512 to the core network 506 over one or more wireless connections. Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 500 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system 500 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system. ATTORNEY’S DOCKET PATENT APPLICATION 017997.4336 (P112649WO01)

[0463] 31 of 62

[0464] The UEs 512 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes 510 and other communication devices. Similarly, the network nodes 508, 510 are arranged, capable, configured, and / or operable to communicate directly or indirectly (e.g., via other devices of telecommunications network 502) with the UEs 512 and / or with other network nodes or equipment in the telecommunications network 502 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunications network 502. More specifically, UEs 512 may send messages, data, and / or other signals to network nodes 508, 510 or other elements of the telecommunications network 502 by transmitting such signals to the relevant device directly without the signals passing through any intervening devices or by transmitting such signals to the relevant device indirectly through an intervening device (or multiple intervening devices) that then transmit the signal to the relevant device. Similarly, network nodes 508, 510 may send messages, data, and other signals to UEs 512, other network nodes 508, 510, and other devices in telecommunications network 502 directly or indirectly. As one specific example, a core network node 108 may transmit a particular message to a UE 512 by transmitting the message to an access network node 510 that will then transmit the message to the intended UE 512. Similarly, a core network node 108 may receive a particular message from a UE 512 by receiving the message from an access network node 510 that itself received the message from the UE 512.

[0465] In the depicted example, the core network 506 connects elements of the access network 504 (e.g., one or more of the network nodes 510) to one or more host computing systems, such as host 516. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 506 includes one or more core network nodes (e.g., core network node 508) of various types, one or more of which may be generally referred to as network nodes 508. Network nodes 508 are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, access network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 508. Example core network nodes provide functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home ATTORNEY’S DOCKET PATENT APPLICATION 017997.4336 (P112649WO01)

[0466] 32 of 62

[0467] Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0468] The host 516 may be under the ownership or control of a service provider other than an operator or provider of the access network 504 and / or the telecommunications network 502. The host 516 may be operated by the service provider or on behalf of the service provider. The host 516 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

[0469] As a whole, the communication system 500 of FIGURE 9 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system 500 may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (Wi-Fi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (Wi-Max), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, Li-Fi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox. Moreover, the communication system 500 may be configured to support multiple different standards, protocols, or other rule sets, with individual components supporting all of the relevant rule sets or with different components or sub-systems within the communication system 500 supporting different standards, protocols, or rule sets.

[0470] As one example, in certain embodiments, access network 504 may contain some access network nodes 510 that support 3GPP radio access technologies (RAT), such as LTE or NR, while other access network nodes 510 support (or the same access network nodes 510 ATTORNEY’S DOCKET PATENT APPLICATION 017997.4336 (P112649WO01)

[0471] 33 of 62

[0472] additionally support) non-3GPP RATs, such as Wi-Fi or a proprietary RAT. As another example, telecommunications network 502 may support multiple generations of related communication standards (e.g., 4G and 5G 3GPP communication standards) and, as a result, may include an access network 104 and / or a core network 506 that supports multiple different standard generations or may include multiple access networks 504 and / or multiple core networks 106 with individual networks 504, 506 supporting different standard generations.

[0473] Telecommunications network 502 may support network slicing to provide different logical networks to different devices that are connected to the telecommunications network 502. For example, the telecommunications network 502 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC) / Massive IoT services to yet further UEs.

[0474] In some examples, one or more of the UEs 512 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 504 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 504. Additionally, a UE may be configured for operating in single- or multi-RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi -radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).

[0475] In the example, the hub 514 communicates with the access network 504 to facilitate indirect communication between one or more UEs (e.g., UE 512C and / or 512D) and network nodes (e.g., network node 510B). In some examples, the hub 514 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 514 may be a broadband router enabling access to the core network 506 for the UEs. As another example, the hub 514 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 510, or by executable code, script, process, or other instructions in the hub 514.

[0476] As another example, the hub 514 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. ATTORNEY’S DOCKET PATENT APPLICATION 017997.4336 (P112649WO01)

[0477] 34 of 62

[0478] As another example, the hub 514 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 514 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 514 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 514 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.

[0479] The hub 514 may have a constant / persistent or intermittent connection to the network node 510B. The hub 514 may also allow for a different communication scheme and / or schedule between the hub 514 and UEs (e.g., UE 512C and / or 512D), and between the hub 514 and the core network 506. In other examples, the hub 514 is connected to the core network 506 and / or one or more UEs via a wired connection. Moreover, the hub 514 may be configured to connect to an M2M service provider over the access network 504 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 510 while still connected via the hub 514 via a wired or wireless connection. In some embodiments, the hub 514 may be a dedicated hub - that is, a hub whose primary function is to route communications to / from the UEs from / to the network node 510B. In other embodiments, the hub 514 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 510B, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0480] FIGURE 10 is another example of a communication system 600 according to some embodiments. As used herein, the communication system 600 includes multiple access points (APs) 610 (with four exemplary APs 610A, 610B, 610C, and 610D being depicted) and multiple wireless devices, referred to in the context of communication system 600 as stations (STAs) 612 (referred to individually as STA 612A, STA 612B, STA 612C, STA 612D, and STA 612E). STA 612A is served by AP 610A in a first basic service set (BSS) 620A. STA 610B and STA 610C are served by AP 610B in a second BSS, BSS 620B. STA 612D is served by AP 610C in a third BSS, BSS 620C. STA 612Eis served by AP 610D in a fourth BSS, BSS 620D. Stations 612 may be non-AP STAs and correspond to various kinds of wireless devices, for example, user terminals, such as mobile or stationary computing devices like smartphones, ATTORNEY’S DOCKET PATENT APPLICATION 017997.4336 (P112649WO01)

[0481] 35 of 62

[0482] laptop computers, desktop computers, tablet computers, gaming devices, head-mounted displays (HMDs) for Augmented Reality (AR) or Virtual Reality (VR), or the like. Further, stations 612 could, for example, correspond to other kinds of equipment like smart home devices, printers, multimedia devices, data storage devices, or the like.

[0483] Each of STAs 612 may connect through a radio link to one of APs 610. For example, depending on location or channel conditions experienced by a given STA 612, the STA may select an appropriate AP and BSS for establishing the radio link. The radio link may be based on one or more orthogonal frequency-division multiplexing (OFDM) carriers from a frequency spectrum that is shared on the basis of a contention-based mechanism, e.g., an unlicensed or license exempt band like 2.4 GHz Industrial, Scientific, and Medical (ISM) band, the 5 GHz band, the 6 GHz band, or the 60 GHz band.

[0484] Each AP 610 may provide data connectivity to STAs 612 connected to a particular AP 610. As illustrated, APs 610 may be connected to a data network 630. In this way, APs 610 may also provide data connectivity between STAs 612 and other entities, e.g., to one or more servers, service providers, data sources, data sinks, user terminals, or the like. Accordingly, the radio link established between a given STA 612 and its serving AP 610 may be used for providing various kinds of services to STA 612, e.g., a voice service, a multimedia service, or other data service. Such services may be based on applications that are executed on STA 612 and / or on a device linked to STA 612. By way of example, FIGURE 10 illustrates an application service platform 632 provided in data network 630. The application(s) executed on STA 612 and / or on one or more other devices linked to STA 612 may use the radio link for data communication with one or more other STA 612 and / or the application service platform 632, thereby enabling utilization of the corresponding service(s) at STA 612.

[0485] FIGURE 11 shows a UE 700, which may be an embodiment of the UE 512 of FIGURE 9, in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless ATTORNEY’S DOCKET PATENT APPLICATION 017997.4336 (P112649WO01)

[0486] 36 of 62

[0487] customer-premise equipment (CPE), vehicle-mounted or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0488] A UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).

[0489] The UE 700 includes processing circuitry 702 that is operatively coupled via a bus 704 to an input / output interface 706, a power source 708, a memory 710, a communication interface 712, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in FIGURE 11. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0490] The processing circuitry 702 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 710. The processing circuitry 702 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 702 may include multiple central processing units (CPUs). ATTORNEY’S DOCKET PATENT APPLICATION 017997.4336 (P112649WO01)

[0491] 37 of 62

[0492] In the example, the input / output interface 706 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into the UE 700. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

[0493] In some embodiments, the power source 708 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source 708 may further include power circuitry for delivering power from the power source 708 itself, and / or an external power source, to the various parts of the UE 700 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 708. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 708 to make the power suitable for the respective components of the UE 700 to which power is supplied.

[0494] The memory 710 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 710 includes one or more application programs 714, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 716. The memory 710 may store, for use by the UE 700, any of a variety of various operating systems or combinations of operating systems. ATTORNEY’S DOCKET PATENT APPLICATION 017997.4336 (P112649WO01)

[0495] 38 of 62

[0496] The memory 710 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 710 may allow the UE 700 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 710, which may be or comprise a device-readable storage medium.

[0497] The processing circuitry 702 may be configured to communicate with an access network or other network using the communication interface 712. The communication interface 712 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 722. The communication interface 712 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter 718 and / or a receiver 720 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 718 and receiver 720 may be coupled to one or more antennas (e.g., antenna 722) and may share circuit components, software or firmware, or alternatively be implemented separately.

[0498] In the illustrated embodiment, communication functions of the communication interface 712 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, ATTORNEY’S DOCKET PATENT APPLICATION 017997.4336 (P112649WO01)

[0499] 39 of 62

[0500] another like communication function, or any combination thereof. Communications may be implemented in according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / internet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0501] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 712, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

[0502] As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.

[0503] A UE, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented ATTORNEY’S DOCKET PATENT APPLICATION 017997.4336 (P112649WO01)

[0504] 40 of 62

[0505] Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an loT device comprises circuitry and / or software in dependence of the intended application of the loT device in addition to other components as described in relation to the UE 700 shown in FIGURE 11.

[0506] As yet another specific example, in an loT scenario, a UE may represent a machine or other device that performs monitoring and / or measurements, and transmits the results of such monitoring and / or measurements to another UE and / or a network node. The UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3GPP NB-IoT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.

[0507] In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed. The first and / or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

[0508] FIGURE 12 shows a network node 800, which may be an embodiment of the network node 510 of FIGURE 9, in accordance with some embodiments.

[0509] As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunications network. In accordance with respective embodiments, network node 800 may be configured to operate in communication system 500 of FIGURE 9, like network nodes 508 or 510, or in communication system 600 of FIGURE 10, like an AP 610 or a station 612. Examples of network nodes include, but are not limited to, access points ATTORNEY’S DOCKET PATENT APPLICATION 017997.4336 (P112649WO01)

[0510] 41 of 62

[0511] (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)), O-RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU).

[0512] Network nodes 800 may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. Network node 800 may be a relay node or a relay donor node controlling a relay. Network nodes 800 may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., in an O-RAN access node) and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

[0513] Other examples of network nodes 800 include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), Operation and Maintenance (O& M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).

[0514] In particular embodiments, network node 800 includes a processing circuitry 802, a memory 804, a communication interface 806, and a power source 808. In general, in a particular embodiment of network node 800, processing circuitry 802, memory 804, communication interface 806, and power source 808 may, in whole or in part, represent or include physical components common to or shared by one or more of the other elements of network node 800.

[0515] The network node 800 may be composed of multiple distinct network entities (e.g., a NodeB entity and a RNC entity, or a BTS entity and a BSC entity, etc.), which may each have or utilize their own respective physical components. In certain scenarios in which the network node 800 comprises multiple such entities (e.g., BTS and BSC), one or more of the separate entities may be shared among several network nodes. For example, a single RNC may control ATTORNEY’S DOCKET PATENT APPLICATION 017997.4336 (P112649WO01)

[0516] 42 of 62

[0517] multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 800 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memories 804 or portions of memory 804 for different RATs) and some components may be reused (e.g., a same antenna 810 may be shared by different RATs). The network node 800 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 800, for example GSM, WCDMA, LTE, NR, Wi-Fi (e.g., according to an IEEE 802.11 family standard), Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 800.

[0518] The processing circuitry 802 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other components, such as the memory 804, to provide network node 800 functionality.

[0519] In some embodiments, the processing circuitry 802 includes a system on a chip (SOC). In some embodiments, the processing circuitry 802 includes one or more of radio frequency (RF) transceiver circuitry 812 and baseband processing circuitry 814. In some embodiments, the RF transceiver circuitry 812 and the baseband processing circuitry 814 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 812 and baseband processing circuitry 814 may be on the same chip or set of chips, boards, or units.

[0520] The memory 804 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processing ATTORNEY’S DOCKET PATENT APPLICATION 017997.4336 (P112649WO01)

[0521] 43 of 62

[0522] circuitry 802. The memory 804 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry 802 and utilized by the network node 800. The memory 804 may be used to store any calculations made by the processing circuitry 802 and / or any data received via the communication interface 806. In some embodiments, the processing circuitry 802 and memory 804 is integrated.

[0523] The communication interface 806 is used in wired or wireless communication of signaling and / or data with UEs, other network nodes, and / or any other network equipment. In the illustrated embodiment, communication interface 806 comprises port(s) / terminal(s) 816 to send and receive data, for example to and from a network over a wired connection. In particular embodiments, network node 700 may be capable of wireless communication and communication interface 806 may also include radio front-end circuitry 818 that may be coupled to, or in certain embodiments a part of, an antenna 810. Particular embodiments of radio front-end circuitry 818 include filter(s) 820 and amplifier(s) 822. The radio front-end circuitry 818 may be connected to an antenna 810 and processing circuitry 802. The radio frontend circuitry may be configured to condition signals communicated between antenna 810 and processing circuitry 802. The radio front-end circuitry 818 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 818 may convert the digital data into a radio signal(s) having the appropriate channel and bandwidth parameters using a combination of filters 820 and / or amplifiers 822. The radio signal(s) may then be transmitted via the antenna 810. Similarly, when receiving data, the antenna 810 may collect radio signals which are then converted into digital data by the radio front-end circuitry 818. The digital data may be passed to the processing circuitry 802. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0524] In certain alternative embodiments, network node 800 may be capable of wireless communication but does not include separate radio front-end circuitry 818, instead, the processing circuitry 802 includes radio front-end circuitry and is connected to the antenna 810. Similarly, in some embodiments, all or some of the RF transceiver circuitry 812 is part of the communication interface 806. In still other embodiments, the communication interface 806 ATTORNEY’S DOCKET PATENT APPLICATION 017997.4336 (P112649WO01)

[0525] 44 of 62

[0526] includes one or more ports or terminals 816, the radio front-end circuitry 818, and the RF transceiver circuitry 812, as part of a radio unit (not shown), and the communication interface 806 communicates with the baseband processing circuitry 814, which is part of a digital unit (not shown).

[0527] The antenna 810 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 810 may be coupled to the radio front-end circuitry 818 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 810 is separate from the network node 800 and connectable to the network node 800 through one or more interfaces or ports.

[0528] The antenna 810, communication interface 806, and / orthe processing circuitry 802 may be configured to perform some or all of the receiving operations and / or obtaining operations described herein as being performed by the network node 800. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna 810, the communication interface 806, and / or the processing circuitry 802 may be configured to perform some or all of the transmitting or sending operations described herein as being performed by the network node 800. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.

[0529] The power source 808 provides power to the various components of network node 800 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 808 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 800 with power for performing the functionality described herein. For example, the network node 800 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 808. As a further example, the power source 808 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

[0530] Embodiments of the network node 800 may include additional components beyond those shown in FIGURE 12 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to ATTORNEY’S DOCKET PATENT APPLICATION 017997.4336 (P112649WO01)

[0531] 45 of 62

[0532] support the subject matter described herein. For example, the network node 800 may include user interface equipment to allow input of information into the network node 800 and to allow output of information from the network node 800. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 800.

[0533] FIGURE 13 is a block diagram illustrating a virtualization environment 900 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 900 hosted by one or more of hardware nodes, such as a hardware computing device that operates as an access network node, UE, core network node, or host. Further, in embodiments in which a virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment 900 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an O-2 interface.

[0534] Applications 902 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment 900 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0535] Hardware 904 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 906 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VM 908A and VM 908B (which may be collectively referred to as VMs 908), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described ATTORNEY’S DOCKET PATENT APPLICATION 017997.4336 (P112649WO01)

[0536] 46 of 62

[0537] herein. The virtualization layer 906 may present a virtual operating platform that appears like networking hardware to one or more of the VMs 908.

[0538] The VMs 908 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by virtualization layer 906. Different embodiments of the instance of a virtual appliance 902 may be implemented on one or more of VMs 908, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

[0539] In the context of NFV, each of the VMs 908 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 908, and that part of hardware 904 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more of the VMs 908 on top of the hardware 904 and corresponds to an application 902.

[0540] Hardware 904 may be implemented in a standalone network node with generic or specific components. Hardware 904 may implement some functions via virtualization. Alternatively, hardware 904 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 910, which, among others, oversees lifecycle management of applications 902. In some embodiments, hardware 904 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 912 which may alternatively be used for communication between hardware nodes and radio units.

[0541] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may ATTORNEY’S DOCKET PATENT APPLICATION 017997.4336 (P112649WO01)

[0542] 47 of 62

[0543] comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.

[0544] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally. ATTORNEY’S DOCKET PATENT APPLICATION 017997.4336 (P112649WO01)

[0545] 48 of 62

[0546] EXAMPLE EMBODIMENTS

[0547] Group A Example Embodiments

[0548] Example Embodiment 1. A method performed by a user equipment (UE) for network-controlled RO prioritization for a SBFD operation, the method comprising: receiving, from a network node, information indicating at least one target UE for using at least one RACH resource for the SBFD operation.

[0549] Example Embodiment 2. The method of Example Embodiment 1, wherein: the at least one RACH resource comprises at least one contention-based (CB) RACH resource, and the information is received in and / or with a CB RACH configuration.

[0550] Example Embodiment 3. The method of any one of Example Embodiments 1 to 2, wherein the at least one RACH resource comprises at least one of: at least one RO in a frequency domain and / or time domain; at least one PRACH preamble and / or at least one associated PRACH preamble format; and at least one RACH power control parameter.

[0551] Example Embodiment 4. The method of any one of Example Embodiments 1 to 3, wherein the information indicating the at least one target UE comprises information indicating at least one target UE group for using the at least one RACH resource.

[0552] Example Embodiment 5. The method of any one of Example Embodiments 1 to 4, wherein the information indicating the at least one target UE comprises at least one of: at least one group indices indicating at least one target UE group associated with the at least one group indices; and at least one UE indices associated with at least one target UE.

[0553] Example Embodiment 6. The method of any one of Example Embodiments 1 to 5, wherein the information indicating the at least one target UE comprises at least one beam identifier associated with at least one beam serving the least one target UE.

[0554] Example Embodiment 7. The method of Example Embodiment 6, wherein the at least one beam identifier comprises at least one of: at least one identifier of at least one SS / PBCH block serving the at least one target UE; at least one identifier of at least one CSI-RS associated with the at least one beam serving the at least one target UE; and at least one identifier of at least one TCI state associated with the at least one target UE.

[0555] Example Embodiment 8. The method of any one of Example Embodiments 1 to 7, comprises: based on the information received from the network node, determining that the UE ATTORNEY’S DOCKET PATENT APPLICATION 017997.4336 (P112649WO01)

[0556] 49 of 62

[0557] is a target UE for using the at least one RACH resource; and based on the UE being a target UE, selecting the at least one RACH resource for the SBFD operation.

[0558] Example Embodiment 9. The method of any one of Example Embodiments 1 to 7, comprises: based on the information received from the network node, determining that the UE is not a target UE for using the at least one RACH resource; and based on the UE not being a target UE, selecting a legacy RACH resource for the SBFD operation.

[0559] Example Embodiment 10. The method of any one of Example Embodiments 1 to 7, comprises: based on the information received from the network node, determining that the UE is a target UE for using the at least one RACH resource; based on a quality of service requirement associated with at least one service and / or application of the UE, determining to use a first available RACH resource; and selecting the at least one RACH resource for the SBFD operation if the at least one RACH resource occurs before at least one legacy RACH resource, otherwise selecting the at least one legacy RACH resource for the SBFD operation.

[0560] Example Embodiment 11. The method of any one of Example Embodiments 1 to 10, wherein the information indicating the at least one target UE comprises a RSRP threshold.

[0561] Example Embodiment 12. The method of Example Embodiment 11, wherein the UE is the at least one target UE when at least one of: a measured RSRP of a SSB is below the RSRP threshold, a measured RSRP of a CSI-RS is above the RSRP threshold, and a measured RSRP of a CSI-RS is below the RSRP threshold.

[0562] Example Embodiment 13. The method of Example Embodiment 11, wherein the information indicating the at least one target UE comprises an indicator for applying the RSRP threshold, and the method comprises determining whether the UE is a target UE based on the indicator and the RSRP threshold.

[0563] Example Embodiment 14. The method of Example Embodiment 13, wherein determining whether the UE is the target UE for using the at least one RACH resource comprises: determining that the UE is a target UE when a value of the indicator is ‘ 1 ’ or above and the measured RSRP is above the RSRP threshold, determining that the UE is not a target UE when a value of the indicator is ‘ 1 ’ or above and the measured RSRP is not above the RSRP threshold, determining that the UE is a target UE when a value of the indicator is ‘0’ or below and the measured RSRP is below the RSRP threshold, determining that the UE is not a target UE when a value of the indicator is ‘0’ or below and the measured RSRP is not below the ATTORNEY’S DOCKET PATENT APPLICATION 017997.4336 (P112649WO01)

[0564] 50 of 62

[0565] RSRP threshold, determining that the UE is a target UE when a value of the indicator is ‘ 1 ’ or below and the measured RSRP is below the RSRP threshold, determining that the UE is not a target UE when a value of the indicator is ‘ 1 ’ or below and the measured RSRP is not below the RSRP threshold, determining that the UE is a target UE when a value of the indicator is ‘0’ or above and the measured RSRP is above the RSRP threshold, or determining that the UE is not a target UE when a value of the indicator is ‘0’ or above and the measured RSRP is not above the RSRP threshold.

[0566] Example Embodiment 15. The method of Example Embodiments 14, comprising: selecting the at least one RACH resource for the SBFD operation when the UE determines that the UE is a target UE, or selecting a legacy RACH resource for the SBFD operation when the UE determines that the UE is not a target UE.

[0567] Example Embodiment 16. The method of any one of Example Embodiments 13 to 15, wherein the indicator and the RSRP threshold are within an information element of a RACH-ConfigCommon.

[0568] Example Embodiment 17. The method of any one of Example Embodiments 13 to 15, wherein the indicator is in a first information element and the RSRP threshold is within a second information element oi RACH-ConfigCommon.

[0569] Example Embodiment 18. The method of Example Embodiment 11, comprising determining whether the UE is a target UE for using the at least one RACH resource based on the RSRP threshold and whether the UE is configured with a single RACH configuration or two RACH configurations.

[0570] Example Embodiment 19. The method of Example Embodiment 18, wherein determining whether the UE is a target UE for using the at least one RACH resource comprises: determining that the UE is a target UE when the UE is configured with a single RACH configuration and a measured RSRP is above the RSRP threshold, determining that the UE is not a target UE when the UE is configured with a single RACH configuration and the measured RSRP is not above the RSRP threshold, determining that the UE is a target UE when the UE is configured with two RACH configurations and the measured RSRP is below the RSRP threshold, or determining that the UE not a target UE when the UE is configured with two RACH configurations and the measured RSRP is not below the RSRP threshold. ATTORNEY’S DOCKET PATENT APPLICATION 017997.4336 (P112649WO01)

[0571] 51 of 62

[0572] Example Embodiment 20. The method of any one of Example Embodiments 19, comprising: selecting the at least one RACH resource for the SBFD operation when the UE determines that the UE is a target UE, or selecting a legacy RACH resource for the SBFD operation when the UE determines that the UE is not a target UE.

[0573] Group B Example Embodiments

[0574] Example Embodiment 21. A method performed by a network node for network-controlled RO prioritization for a SBFD operation by a UE, the method comprising: transmitting, to the UE, information indicating at least one target UE for using at least one RACH resource for the SBFD operation.

[0575] Example Embodiment 22. The method of Example Embodiment 21, wherein: the at least one RACH resource comprises at least one contention-based (CB) RACH resource, and the information is received in and / or with a CB RACH configuration.

[0576] Example Embodiment 23. The method of any one of Example Embodiments 21 to 22, wherein the at least one RACH resource comprises at least one of: at least one RO in a frequency domain and / or time domain; at least one PRACH preamble and / or at least one associated PRACH preamble format; and at least one RACH power control parameter.

[0577] Example Embodiment 24. The method of any one of Example Embodiments 21 to 23, wherein the information indicating the at least one target UE comprises information indicating at least one target UE group for using the at least one RACH resource.

[0578] Example Embodiment 25. The method of any one of Example Embodiments 21 to 24, wherein the information indicating the at least one target UE comprises at least one of: at least one group indices indicating at least one target UE group associated with the at least one group indices; and at least one UE indices associated with at least one target UE.

[0579] Example Embodiment 26. The method of any one of Example Embodiments 21 to 25, wherein the information indicating the at least one target UE comprises at least one beam identifier associated with at least one beam serving the least one target UE.

[0580] Example Embodiment 27. The method of Example Embodiment 26, wherein the at least one beam identifier comprises at least one of: at least one identifier of at least one SS / PBCH block serving the at least one target UE; at least one identifier of at least one CSI-RS associated ATTORNEY’S DOCKET PATENT APPLICATION 017997.4336 (P112649WO01)

[0581] 52 of 62

[0582] with the at least one beam serving the at least one target UE; and at least one identifier of at least one TCI state associated with the at least one target UE.

[0583] Example Embodiment 28. The method of any one of Example Embodiments 21 to 27, comprising configuring the UE to perform at least one of: based on the information received from the network node, determining that the UE is a target UE for using the at least one RACH resource; and based on the UE being a target UE, selecting the at least one RACH resource for the SBFD operation.

[0584] Example Embodiment 29. The method of any one of Example Embodiments 21 to 27, comprising configuring the UE to perform at least one of: based on the information received from the network node, determining that the UE is not a target UE for using the at least one RACH resource; and based on the UE not being a target UE, selecting a legacy RACH resource for the SBFD operation.

[0585] Example Embodiment 30. The method of any one of Example Embodiments 21 to 27, comprising configuring the UE to perform at least one of: based on the information received from the network node, determining that the UE is a target UE for using the at least one RACH resource; based on a quality of service requirement associated with at least one service and / or application of the UE, determining to use a first available RACH resource; and selecting the at least one RACH resource for the SBFD operation if the at least one RACH resource occurs before at least one legacy RACH resource, otherwise selecting the at least one legacy RACH resource for the SBFD operation.

[0586] Example Embodiment 31. The method of any one of Example Embodiments 21 to 30, wherein the information indicating the at least one target UE comprises a RSRP threshold.

[0587] Example Embodiment 32. The method of Example Embodiment 31, wherein the UE is the at least one target UE when at least one of: a measured RSRP of a SSB is below the RSRP threshold, a measured RSRP of a CSI-RS is above the RSRP threshold, and a measured RSRP of a CSI-RS is below the RSRP threshold.

[0588] Example Embodiment 33. The method of Example Embodiment 31, wherein the information indicating the at least one target UE comprises an indicator for applying the RSRP threshold, and the UE is configured to determine whether the UE is a target UE based on the indicator and the RSRP threshold. ATTORNEY’S DOCKET PATENT APPLICATION 017997.4336 (P112649WO01)

[0589] 53 of 62

[0590] Example Embodiment 34. The method of Example Embodiment 33, wherein: the UE is a target UE when a value of the indicator is ‘ 1 ’ or above and the measured RSRP is above the RSRP threshold, the UE is not a target UE when a value of the indicator is ‘ 1 ’ or above and the measured RSRP is not above the RSRP threshold, the UE is a target UE when a value of the indicator is ‘0’ or below and the measured RSRP is below the RSRP threshold, the UE is not a target UE when a value of the indicator is ‘0’ or below and the measured RSRP is not below the RSRP threshold, the UE is a target UE when a value of the indicator is ‘ 1 ’ or below and the measured RSRP is below the RSRP threshold, the UE is not a target UE when a value of the indicator is ‘ 1 ’ or below and the measured RSRP is not below the RSRP threshold, the UE is a target UE when a value of the indicator is ‘0’ or above and the measured RSRP is above the RSRP threshold, or the UE is not a target UE when a value of the indicator is ‘0’ or above and the measured RSRP is not above the RSRP threshold.

[0591] Example Embodiment 35. The method of Example Embodiments 34, comprising configuring the UE to perform at least one of: select the at least one RACH resource for the SBFD operation when the UE determines that the UE is a target UE, and select a legacy RACH resource for the SBFD operation when the UE determines that the UE is not a target UE.

[0592] Example Embodiment 36. The method of any one of Example Embodiments 33 to 35, wherein the indicator and the RSRP threshold are within an information element of a RACH-ConfigCommon.

[0593] Example Embodiment 37. The method of any one of Example Embodiments 33 to 35, wherein the indicator is in a first information element and the RSRP threshold is within a second information element oi RACH-ConfigCommon.

[0594] Example Embodiment 38. The method of Example Embodiment 31, comprising configuring the UE to determine whether the UE is a target UE for using the at least one RACH resource based on the RSRP threshold and whether the UE is configured with a single RACH configuration or two RACH configurations.

[0595] Example Embodiment 39. The method of Example Embodiment 38, wherein: the UE is a target UE when the UE is configured with a single RACH configuration and a measured RSRP is above the RSRP threshold, the UE is not a target UE when the UE is configured with a single RACH configuration and the measured RSRP is not above the RSRP threshold, the UE is a target UE when the UE is configured with two RACH configurations and the measured ATTORNEY’S DOCKET PATENT APPLICATION 017997.4336 (P112649WO01)

[0596] 54 of 62

[0597] RSRP is below the RSRP threshold, or the UE not a target UE when the UE is configured with two RACH configurations and the measured RSRP is not below the RSRP threshold.

[0598] Example Embodiment 40. The method of any one of Example Embodiments 39, comprising configuring the UE to perform at least one of: selecting the at least one RACH resource for the SBFD operation when the UE determines that the UE is a target UE, and selecting a legacy RACH resource for the SBFD operation when the UE determines that the UE is not a target UE.

[0599] Group C Example Embodiments

[0600] Example Embodiment 41. A user equipment comprising processing circuitry configured to perform any of the steps of any of the Group A Example Embodiments.

[0601] Example Embodiment 42. A user equipment configured to perform any of the steps of any of the Group A Example Embodiments.

[0602] Example Embodiment 43. A wireless device comprising processing circuitry configured to perform any of the steps of any of the Group A Example Embodiments.

[0603] Example Embodiment 44. A network node comprising processing circuitry configured to perform any of the steps of any of the Group B Example Embodiments.

[0604] Example Embodiment 45. A network node configured to perform any of the steps of any of the Group B Example Embodiments.

[0605] Example Embodiment 46. A computer program comprising instructions which when executed on a computer perform any of the steps of any of the Group A and B Example Embodiments.

[0606] Example Embodiment 47. A computer program product comprising computer program, the computer program comprising instructions which when executed on a computer perform any of the steps of any of the Group A and B Example Embodiments.

[0607] Example Embodiment 48. A non-transitory computer readable medium storing instructions which when executed by a computer perform any of the steps of any of the Group A and B Example Embodiments.

Claims

ATTORNEY’S DOCKET PATENT APPLICATION 017997.4336 (P112649WO01)55 of 62CLAIMS1. A method (200) performed by a user equipment, UE, (512, 700) for network-controlled Random Access Occasion, RO, prioritization for a Subband Full Duplex, SBFD, operation, the method comprising:receiving (202), from a network node (510, 800), information indicating at least one UE for using at least one prioritized Random Access Channel, RACH, resource for the SBFD operation.

2. The method of Claim 1, wherein:the at least one prioritized RACH resource comprises at least one contention-based, CB, RACH resource, andthe information is received in and / or with a CB RACH configuration.

3. The method of any one of Claims 1 to 2, wherein the at least one prioritized RACH resource comprises at least one of:at least one RO in a frequency domain and / or time domain;at least one Physical Random Access Channel, PRACH, preamble and / or at least one associated PRACH preamble format; andat least one RACH power control parameter.

4. The method of any one of Claims 1 to 3, wherein the information indicating the at least one UE comprises information indicating at least one UE group for using the at least one prioritized RACH resource.

5. The method of Claim 4, comprises:based on the information received from the network node, determining that the UE is in the UE group for using the at least one prioritized RACH resource; andbased on the UE being in the UE group, selecting the at least one prioritized RACH resource for the SBFD operation.ATTORNEY’S DOCKET PATENT APPLICATION 017997.4336 (P112649WO01)56 of 626. The method of Claim 4, comprises:based on the information received from the network node, determining that the UE is not in the UE group for using the at least one prioritized RACH resource; andbased on the UE not being in the UE group, selecting a legacy RACH resource for the SBFD operation.

7. The method of any one of Claims 4 to 6, wherein the information indicating the at least one UE for using the at least one prioritized RACH resource comprises a RSRP threshold.

8. The method of Claim 7, wherein the UE is in the UE group when:a measured RSRP of one or more SSB resources is above the RSRP threshold, a measured RSRP of one or more SSB resources is below the RSRP threshold, a measured RSRP of one or more CSI-RS resources is above the RSRP threshold, or a measured RSRP of one or more CSI-RS resources is below the RSRP threshold.

9. The method of Claim 8, wherein the information indicating the at least one UE for using the at least one prioritized RACH resource comprises an indicator for applying the RSRP threshold, and the method comprises determining whether the UE is in the UE group based on the indicator and the RSRP threshold.

10. The method of Claim 9, wherein determining whether the UE is in the UE group comprises:determining that the UE is in the UE group when a value of the indicator is ‘ 1 ’ or ‘above’ and the measured RSRP is above the RSRP threshold,determining that the UE is not in the UE group when a value of the indicator is ‘ 1 ’ or ‘above’ and the measured RSRP is not above the RSRP threshold,determining that the UE is in the UE group when a value of the indicator is ‘0’ or ‘below’ and the measured RSRP is below the RSRP threshold,determining that the UE is not in the UE group when a value of the indicator is ‘0’ or ‘below’ and the measured RSRP is not below the RSRP threshold,ATTORNEY’S DOCKET PATENT APPLICATION 017997.4336 (P112649WO01)57 of 62determining that the UE is in the UE group when a value of the indicator is ‘ 1 ’ or ‘below’ and the measured RSRP is below the RSRP threshold,determining that the UE is not in the UE group when a value of the indicator is ‘ 1 ’ or ‘below’ and the measured RSRP is not below the RSRP threshold,determining that the UE is in the UE group when a value of the indicator is ‘0’ or ‘above’ and the measured RSRP is above the RSRP threshold, ordetermining that the UE is not in the UE group when a value of the indicator is ‘0’ or ‘above’ and the measured RSRP is not above the RSRP threshold.

11. The method of Claim 7 comprising determining whether the UE is in the UE group for using the at least one RACH resource based on the RSRP threshold and whether the UE is configured with a single RACH configuration comprising both prioritized RACH resources and legacy RACH resources or two RACH configurations wherein one RACH configuration comprises prioritized RACH resources and one RACH configuration comprises legacy RACH resources.

12. The method of Claim 11, wherein determining whether the UE is in the UE group for using the at least one RACH resource comprises:determining that the UE is in the UE group when the UE is configured with a single RACH configuration and a measured RSRP is above the RSRP threshold,determining that the UE is not in the UE group when the UE is configured with a single RACH configuration and the measured RSRP is not above the RSRP threshold, determining that the UE is in the UE group when the UE is configured with a single RACH configuration and a measured RSRP is below the RSRP threshold,determining that the UE is not in the UE group when the UE is configured with a single RACH configuration and the measured RSRP is not below the RSRP threshold, determining that the UE is in the UE group when the UE is configured with two RACH configurations and the measured RSRP is below the RSRP threshold,determining that the UE not in the UE group when the UE is configured with two RACH configurations and the measured RSRP is not below the RSRP thresholdATTORNEY’S DOCKET PATENT APPLICATION 017997.4336 (P112649WO01)58 of 62determining that the UE is in the UE group when the UE is configured with two RACH configurations and the measured RSRP is above the RSRP threshold, ordetermining that the UE not in the UE group when the UE is configured with two RACH configurations and the measured RSRP is not above the RSRP threshold.

13. A method (400) performed by a network node (510, 800) for network-controlled Random Access Occasion, RO, prioritization for a Subband Full Duplex, SBFD, operation by at least one User Equipment, UE, the method comprising:transmitting (402), to the at least one UE (512,700), information indicating at least one prioritized Random Access Channel, RACH, resource for use by the at least one UE for the SBFD operation.

14. The method of Claim 13, wherein:the at least one prioritized RACH resource comprises at least one contention-based (CB) RACH resource, andthe information is received in and / or with a CB RACH configuration.

15. The method of any one of Claims 13 to 14, wherein the at least one prioritized RACH resource comprises at least one of:at least one RO in a frequency domain and / or time domain;at least one Physical Random Access Channel, PRACH, preamble and / or at least one associated PRACH preamble format; andat least one RACH power control parameter.

16. The method of any one of Claims 13 to 15, wherein the information indicating the at least one UE comprises information indicating at least one UE group for using the at least one prioritized RACH resource.

17. The method of Claim 16, comprising configuring the at least one UE to:based on the information received from the network node, determine that the UE is in the UE group for using the at least one prioritized RACH resource; andATTORNEY’S DOCKET PATENT APPLICATION 017997.4336 (P112649WO01)59 of 62based on the UE being in the UE group, select the at least one prioritized RACH resource for the SBFD operation.

18. The method of Claim 16, comprising configuring the at least one UE to:based on the information received from the network node, determine that the UE is in the UE group for using the at least one prioritized RACH resource; andbased on the UE not being in the UE group, selecting a legacy RACH resource for the SBFD operation.

19. The method of any one of Claimsl6 to 18, wherein the information indicating the at least one UE comprises a RSRP threshold.

20. The method of Claim 19, wherein the UE is the UE group when:a measured RSRP of one or more SSB resources is above the RSRP threshold, a measured RSRP of one or more SSB resources is below the RSRP threshold, a measured RSRP of one or more CSI-RS resources is above the RSRP threshold, or a measured RSRP of one or more CSI-RS resources is below the RSRP threshold.

21. The method of Claim 20, wherein the information indicating the at least one UE comprises an indicator for applying the RSRP threshold.

22. The method of Claim 21, wherein:the UE is in the UE group when a value of the indicator is ‘I’ or ‘above’ and the measured RSRP is above the RSRP threshold,the UE is not in the UE group when a value of the indicator is ‘1’ or ‘above’ and the measured RSRP is not above the RSRP threshold,the UE is in the UE group when a value of the indicator is ‘0’ or ‘below’ and the measured RSRP is below the RSRP threshold,the UE is not in the UE group when a value of the indicator is ‘0’ or ‘below’ and the measured RSRP is not below the RSRP threshold,ATTORNEY’S DOCKET PATENT APPLICATION 017997.4336 (P112649WO01)60 of 62the UE is in the UE group when a value of the indicator is ‘I’ or ‘below’ and the measured RSRP is below the RSRP threshold,the UE is not in the UE group when a value of the indicator is ‘I’ or ‘below’ and the measured RSRP is not below the RSRP threshold,the UE is in the UE group when a value of the indicator is ‘0’ or ‘above’ and the measured RSRP is above the RSRP threshold, orthe UE is not in the UE group when a value of the indicator is ‘0’ or ‘above’ and the measured RSRP is not above the RSRP threshold.

23. The method of Claim 19, wherein the UE is determined to be in the UE group for using the at least one prioritized RACH resource based on the RSRP threshold and whether the UE is configured with a single RACH configuration comprising both prioritized RACH resources and legacy RACH resources or two RACH configurations where one RACH configuration comprises prioritized RACH resources and one RACH configuration comprises legacy RACH resources.

24. The method of Claim 23, wherein:the UE is in the UE group when the UE is configured with a single RACH configuration and a measured RSRP is above the RSRP threshold,the UE is not in the UE group when the UE is configured with a single RACH configuration and the measured RSRP is not above the RSRP threshold,the UE is in the UE group when the UE is configured with a single RACH configuration and a measured RSRP is below the RSRP threshold,the UE is not in the UE group when the UE is configured with a single RACH configuration and the measured RSRP is not below the RSRP threshold,the UE is in the UE group when the UE is configured with two RACH configurations and the measured RSRP is below the RSRP threshold, rthe UE not in the UE group when the UE is configured with two RACH configurations and the measured RSRP is not below the RSRP threshold,the UE is in the UE group when the UE is configured with two RACH configurations and the measured RSRP is above the RSRP threshold, orATTORNEY’S DOCKET PATENT APPLICATION 017997.4336 (P112649WO01)61 of 62the UE not in the UE group when the UE is configured with two RACH configurations and the measured RSRP is not above the RSRP threshold.

25. A User Equipment, UE, (512, 700) for network -controlled Random Access Occasion, RO, prioritization for a Subband Full Duplex, SBFD, operation, the UE comprising processing circuitry (702) configured to:receive, from a network node (510, 800), information indicating at least one UE for using at least one prioritized RACH resource for the SBFD operation.

26. The UE of Claim 25, wherein the processing circuitry is configured to perform any of the steps of any of Claims 2 to 12.

27. A network node (510, 800) for network -controlled Random Access Occasion, RO, prioritization for a Subband Full Duplex, SBFD, operation by a User Equipment, UE (512, 700), the network node comprising processing circuitry (802) configured to:transmit, to the UE (512, 700), information indicating at least one UE for using at least one prioritized Random Access Channel, RACH, resource for the SBFD operation.

28. The network node of Claim 27, wherein the processing circuitry is configured to perform any of the steps of any of Claims 14 to 24.

Images