WO2025212459A1

WO2025212459A1 - Power control channel ordered prach transmission in full duplex system

Info

Publication number: WO2025212459A1
Application number: PCT/US2025/022199
Authority: WO
Inventors: Gang Xiong; Sergey PANTELEEV
Original assignee: Intel Corp
Current assignee: Intel Corp
Priority date: 2024-04-05
Filing date: 2025-03-28
Publication date: 2025-10-09
Anticipated expiration: 2026-10-05

Abstract

This disclosure describes systems, methods, and devices related to enhanced duplex communication. A device may receive an indication for PRACH resources for subband non-overlapping full duplex (SBFD) operationin downlink control information with a Cyclic Redundancy Check (CRC). The device may determine a physical random access channel (PRACH) occasion based on the indication for PRACH resources for SBFD operation. The device may transmit a PRACH preamble on the determined PRACH occasion.

Description

POWER CONTROL CHANNEL ORDERED PRACH TRANSMISSION IN FULL DUPLEX SYSTEM

CROSS-REFERENCE TO RELATED APPLICATION(S)

This application claims the benefit of U.S. Provisional Application No. 63/643,813, filed May 7, 2024 and U.S. Provisional Application No. 63/575,208, filed April 5, 2024, the disclosure of which is incorporated herein by reference as if set forth in full.

BACKGROUND

Wireless networks are essential for modern communication, supporting diverse devices and applications. As data demands grow, these networks must enhance performance and reliability. Key advancements focus on optimizing data handling and network management.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGs. 1-4 depict illustrative schematic diagrams for enhanced duplex communication, in accordance with one or more example embodiments of the present disclosure.

FIG. 5 illustrates a flow diagram of illustrative process for an illustrative enhanced duplex communication system, in accordance with one or more example embodiments of the present disclosure.

FIG. 6 illustrates an example network architecture, in accordance with one or more example embodiments of the present disclosure.

FIG. 7 schematically illustrates a wireless network, in accordance with one or more example embodiments of the present disclosure.

FIG. 8 illustrates components of a computing device, in accordance with one or more example embodiments of the present disclosure.

FIG. 9 illustrates a network in accordance with various embodiments.

DETAILED DESCRIPTION

The following description and the drawings sufficiently illustrate specific embodiments to enable those skilled in the art to practice them. Other embodiments may incorporate structural, logical, electrical, process, algorithm, and other changes. Portions and features of some embodiments may be included in, or substituted for, those of other embodiments. Embodiments set forth in the claims encompass all available equivalents of those claims. Time Division Duplex (TDD) is now widely used in commercial NR deployments, where the time domain resource is split between downlink and uplink symbols. Allocation of a limited time duration for the uplink in TDD can result in reduced coverage and increased latency for a given target data rate. To improve the performance for uplink transmission in TDD system, simultaneous transmission/reception of downlink and uplink respectively, also referred to as “full duplex communication” can be considered. In this regard, the case of subband non-overlapping full duplex (SBFD) operation will be defined in Rel-19 in 3GPP.

For SBFD, within a carrier bandwidth, some bandwidth can be allocated as UL, while some bandwidth can be allocated as DL within the same symbol, however the UL and DL resources are non-overlapping in frequency domain. Under this operational mode, at a given symbol a gNB can simultaneously transmit DL signals and receive UL signals, while a UE may only transmit or receive at a time.

As defined in NR, when UE is out of synchronization with gNB and if gNB has downlink (DL) data to transmit to the UE, gNB may trigger random access (RACH) procedure by using physical downlink control channel (PDCCH) order. In particular, downlink control information (DCI) format l_0 with Cyclic Redundancy Check (CRC)scrambled by Cell - Radio Network Temporary Identifier (C-RNTI) is used initiate the PDCCH order. The DCI format includes the indication of physical random access channel (PRACH) preamble, synchronization signal block (SSB) index, and possible associated PRACH occasion for PRACH transmission.

For PDCCH order PRACH transmission, in order to reduce the PRACH detection complexity at gNB, it is more beneficial to align the common understanding on the transmission of PRACH in either SBFD or non-SBFD symbols. In this case, certain mechanisms may need to be defined to indicate resource for the PDCCH order PRACH transmission.

Example embodiments of the present disclosure relate to systems, methods, and devices for PDCCH ordered PRACH transmission in full duplex system.

Various embodiments herein provide systems and methods for PDCCH ordered PRACH transmission in full duplex system.

PDCCH ordered PRACH transmission for SBFD operation:

As mentioned above, in NR, when UE is out of synchronization with gNB and if gNB has downlink (DL) data to transmit to the UE, gNB may trigger random access (RACH) procedure by using physical downlink control channel (PDCCH) order. In particular, downlink control information (DCI) format l_0 with Cyclic Redundancy Check (CRC)scrambled by Cell - Radio Network Temporary Identifier (C-RNTI) is used initiate the PDCCH order. The DCI format includes the indication of physical random access channel (PRACH) preamble, synchronization signal block (SSB) index, and possible associated PRACH occasion for PRACH transmission.

Embodiments of PDCCH ordered PRACH transmission for SBFD operation are provided as follows:

In one embodiment, the following steps can be included in the procedure for PDCCH ordered PRACH transmissions for SBFD operations.

Step 1: UE receives an SBFD indication or indication for PRACH resources for SBFD operation in the DCI format l_0 with CRC scrambled by C-RNTI for PDCCH order RACH procedure.

Step 2: UE determines a PRACH occasion on either SBFD or non-SBFD symbols in accordance with the SBFD indication or indication for PRACH resources for SBFD operation.

Step 3: UE transmits the RPACH preamble on the determined PRACH occasion.

The above descriptions are for purposes of illustration and are not meant to be limiting. Numerous other examples, configurations, processes, algorithms, etc., may exist, some of which are described in greater detail below. Example embodiments will now be described with reference to the accompanying figures.

Time Division Duplex (TDD) is now widely used in commercial NR deployments, where the time domain resource is split between downlink and uplink symbols. Allocation of a limited time duration for the uplink in TDD can result in reduced coverage and increased latency for a given target data rate. To improve the performance for uplink transmission in TDD system, simultaneous transmission/reception of downlink and uplink respectively, also referred to as “full duplex communication” can be considered. In this regard, the case of subband non-overlapping full duplex (SBFD) operation will be defined in Rel-19 in 3GPP.

FIG. 1 illustrates one example of subband non-overlapping full duplex (SBFD) for NR system. In FIG. 1, in the SBFD symbols, part of carrier bandwidth is allocated for DL while remaining part of carrier bandwidth is allocated for UL.

FIG. 2 illustrates PDCCH ordered PRACH transmission for SBFD operations.

At block 202: UE receives an SBFD indication or indication for PRACH resources for SBFD operation in the DCI format l_0 with CRC scrambled by C-RNTI for PDCCH order RACH procedure.

At block 204: UE determines a PRACH occasion on either SBFD or non-SBFD symbols in accordance with the SBFD indication or indication for PRACH resources for SBFD operation.

At block 204: UE transmits the RPACH preamble on the determined PRACH occasion.

In one embodiment, one field may be explicitly included in the DCI format l_0 with CRC scrambled by C-RNTI for PDCCH order RACH procedure to indicate whether the PRACH occasions are within the SBFD or non-SBFD symbols.

In one option, 1 bit SBFD indicator or indication for PRACH resources for SBFD operation may be included in the DCI format l_0 with CRC scrambled by C-RNTI for PDCCH order RACH procedure, where bit “0” may be used to indicate that the PRACH occasions are within the non-SBFD symbols, while bit “1” may be used to indicate that the PRACH occasions are within the SBFD symbols.

In another option, whether the SBFD indication field or indication for PRACH resources for SBFD operation is present may be configured by higher layers via NR remaining minimum system information (RMSI), NR other system information (OSI) or dedicated radio resource control (RRC) signalling. If it is not configured, the SBFD indication field may not be present in the DCI format l_0 with CRC scrambled by C-RNTI for PDCCH order RACH procedure. In this case, UE may transmit the PRACH in a PRACH occasion in the non-SBFD symbols. Alternatively, UE may transmit the PRACH in a PRACH occasion in either SBFD or non-SBFD symbols.

In one example, the following text in Clause 7.3. 1.2.1 in TS38.212 [1] may be updated as shown below in bold. The changes exemplify introduction of 1-bit SBFD indication and respective change in the number of reserved bits.

If the CRC of the DCI format l_0 is scrambled by C-RNTI and the “Frequency domain resource assignment’’ field are of all ones, the DCI format l_0 is for random access procedure initiated by a PDCCH order, with all remaining fields set as follows:

Random Access Preamble index - 6 bits according to ra-Preamblelndex in Clause 5.1.2 of [8, TS38.321]

UL/SUL indicator - 1 bit. If the value of the “Random Access Preamble index” is not all zeros and if the UE is configured with supplementaryUplink in ServingCellConfig in the cell, this field indicates which UL carrier in the cell to transmit the PRACH according to Table 7.3.1.1.1-1; otherwise, this field is reserved

SS/PBCH index - 6 bits. If the value of the “Random Access Preamble index” is not all zeros, this field indicates the SS/PBCH that shall be used to determine the RACH occasion for the PRACH transmission; otherwise, this field is reserved.

PRACH Mask index - 4 bits. If the value of the “Random Access Preamble index” is not all zeros, this field indicates the RACH occasion associated with the SS/PBCH indicated by “SS/PBCH index” for the PRACH transmission, according to Clause 5.1.1 of [8, TS38.321]; otherwise, this field is reserved

Cell indicator - \log₂(C + 1)] bits indicating the cell for the corresponding PRACH transmission if the UE is configured with higher layer parameter EarlyUlSyncConfig, where C is the number of candidate cells configured with higher layer parameter EarlyUlSyncConfig; 0 bit otherwise. The bit field index 0 of the cell indicator field is mapped to the serving cell, and other bit field indexes are mapped to the candidate cells configured with higher layer parameter EarlyUlSyncConfig according to an ascending order of a candidate identity configured by Itm-Candidateld, with the bit field index 1 mapped to the candidate cell with the smallest candidate identity.

PRACH association indicator - 0 or 1 bit

Ibit if the UE is provided with tag-Id2, and the UE is not provided coresetPoolIndex or is provided coresetPoolIndex with value 0 for the first CORESETs, and is provided coresetPoolIndex with value 1 for the second CORESETs.

This field indicates the PCI associated with the PRACH transmission if the UE is provided SSB-MTC-AddtionalPCI. The bit field index 0 of this field is mapped to the PCI of the serving cell, and the bit field index 1 of this field is mapped to the active additional PCI.

This field indicates the PL-RS for the PRACH transmission if the UE is not provided SSB-MTC-AddtionalPCI. The bit field index 0 of this field is mapped to the DL RS that the DM-RS of the PDCCH order is quasi-collocated with, and the bit field index 1 of this field is mapped to the SS/PBCH indicated by the SS/PBCH index field in this DCI format.

0 bit otherwise.

PRACH retransmission indicator - 0 or 1 bit

Ibit if the UE is configured with higher layer parameter EarlyUlSyncConfig. This field indicates initial transmission or retransmission of PRACH according to Table 7.3.1.2.1-3 if the cell indicated by Cell indicator field is a candidate cell, and this field is reserved if the cell indicated by Cell indicator field is a serving cell but not a candidate cell.

0 bit otherwise.

SBFD indicator or indication for PRACH resources for SBFD operation - 0 or 1 bit

1 bit if the UE is configured with higher layer parameter SBFD PDCCH Order. This field indicates initial transmission or retransmission of PRACH in SBFD or non-SBFD symbols.

0 bit otherwise.

Reserved bits - a number of bits as determined by the following:

12 bits for operation in a cell with shared spectrum channel access in frequency range 1 or when the DCI format is monitored in common search space for operation in a cell in frequency range 2-2, and if the UE is not configured with higher layer parameter EarlyUlSyncConfig and if the UE is not configured with higher layer parameter SBFDPDCCHOrder; 11 bits for operation in a cell with shared spectrum channel access in frequency range 1 or when the DCI format is monitored in common search space for operation in a cell in frequency range 2-2, and if the UE is not configured with higher layer parameter EarlyUISyncConfig and if the UE is configured with higher layer parameter SBFDPDCCHOrder; l l-[log₂(C + 1)] bits for operation in a cell with shared spectrum channel access in frequency range 1 or when the DCI format is monitored in common search space for operation in a cell in frequency range 2-2, and if the UE is configured with higher layer parameter EarlyUISyncConfig and if the UE is not configured with higher layer parameter SBFDPDCCHOrder;

10- log₂ (C + 1)1 bits for operation in a cell with shared spectrum channel access in frequency range 1 or when the DCI format is monitored in common search space for operation in a cell in frequency range 2-2, and if the UE is configured with higher layer parameter EarlyUISyncConfig and if the UE is configured with higher layer parameter SBFDPDCCHOrder;

9-\log₂(C + 1)1 bits for operation in a cell without shared spectrum channel access in frequency range 1 or for operation in a cell in frequency range 2- 1 or when the DCI format is monitored in UE-specific search space for operation in a cell in frequency range 2-2, and if the UE is configured with higher layer parameter EarlyUISyncConfig and if the UE is not configured with higher layer parameter SBFD PDCCH Order;

8- log₂(C + 1)1 bits for operation in a cell without shared spectrum channel access in frequency range 1 or for operation in a cell in frequency range 2-1 or when the DCI format is monitored in UE-specific search space for operation in a cell in frequency range 2-2, and if the UE is configured with higher layer parameter EarlyUISyncConfig and if the UE is configured with higher layer parameter SBFD PDCCH Order;

9 bits otherwise.

This may apply for the case when separate RACH configurations are configured for PRACH transmission in SBFD and non-SBFD symbols.

In another embodiment, one of the existing fields in the DCI format l_0 with CRC scrambled by C-RNTI for PDCCH order RACH procedure may be repurposed to indicate whether the PRACH occasions are within the SBFD or non-SBFD symbols. In one option, some reserved states in PRACH Mask Index may be used to indicate whether the PRACH occasions are within the SBFD or non-SBFD symbols.

In one example, Table 1 in Clause 7.4 in TS38.321 [2] may be updated as shown below in bold. In the table, the reserved values can be used to indicate that the PRACH occasions are within the SBFD symbols. In some aspects, the values 0 - 10 are used to indicate that PRACH occasions are within the non-SBFD symbols.

Table 1. PRACH mask index values

In another embodiment, if UE supports the SBFD operation and when two RACH configurations are configured for SBFD symbols and non-SBFD symbols, respectively, and when gNB initiates PDCCH ordered PRACH transmissions, UE may determine a PRACH occasion in accordance with the indicated SSB index and PRACH mask index and as the first in time and/or frequency domain between the RACH configurations in SBFD and non-SBFD symbols. In some aspects, the determination of PRACH occasion may also need to meet the timeline requirements. In one option, the same timeline requirement is applicable to PRACH occasion determination regardless of whether SBFD or non-SBFD symbols are utilized. Alternatively, an adjusted timeline requirement by X symbols or milliseconds may be defined for the case of PRACH occasion determination for SBFD operation. FIG. 3 illustrates one example of determination of PRACH occasions for PDCCH ordered PRACH transmission for SBFD operations. In the figure, two PRACH occasions are configured for non-SBFD symbol in the first slot and one PRACH occasion is configured for SBFD symbol in the second slot. Based on this option, if the timeline requirement is satisfied, UE determines the RO that is determined in accordance with the indicated SSB index and PRACH mask index and as the first in time between the RACH configurations in SBFD and non-SBFD symbols. In the example, RO#0 may be used for the PDCCH ordered PRACH transmissions.

PRACH occasion validation for SBFD operation:

Embodiments on PRACH occasion validation for SBFD operation are provided as follows:

In one embodiment, when a separate PRACH configuration is configured for SBFD aware UEs, and when a PRACH occasion of the separate PRACH configuration in the non- SBFD symbols overlaps with the PRACH occasion that is configured for legacy UEs, the PRACH occasion of the separate PRACH configuration in the non-SBFD symbols for SBFD aware UEs is invalid.

In addition, the PRACH occasion of the separate PRACH configuration in the non- SBFD symbols that does not overlap with the PRACH occasion of the legacy PRACH configuration is valid.

In some aspects, this may apply for the PRACH configurations that are configured for 4-step RACH and/or 2-step RACH. In one example, when a separate PRACH configuration is configured for 4-step RACH for SBFD aware UEs, and when a PRACH occasion of the separate PRACH configuration overlaps with the PRACH occasion that is configured for the legacy UEs for 2-step RACH, the PRACH occasion of the separate PRACH configurations in the non-SBFD symbols for SBFD aware UEs is invalid.

FIG. 4 illustrates one example of PRACH occasion validation for SBFD operation. In the figure, the PRACH occasions for the additional configurations are configured in both non- SBFD symbols and SBFD symbols. Further, the PRACH occasion in the non-SBFD symbols overlaps with the PRACH occasion for the legacy configuration. Based on this option, the PRACH occasion of the separate PRACH configuration in the non-SBFD symbols is invalid for SBFD aware UEs.

In one or more embodiments, a enhanced duplex communication system may indicate, by gNodeB (gNB), a subband non-overlapping full duplex (SBFD) indication in the downlink control information (DCI) format l_0 with Cyclic Redundancy Check (CRC) scrambled by Cell - Radio Network Temporary Identifier (C-RNTI) for physical downlink control channel (PDCCH) order random access (RACH) procedure.

In one or more embodiments, a enhanced duplex communication system may determine, by UE, a physical random access channel (PRACH) occasion on either SBFD or non-SBFD symbols in accordance with the SBFD indication.

In one or more embodiments, a enhanced duplex communication system may transmit, by UE, the PRACH preamble on the determined RACH occasion. In one or more embodiments, a field may be explicitly included in the DCI format l_0 with CRC scrambled by C-RNTI for PDCCH order RACH procedure to indicate whether the PRACH occasions are within the SBFD or non-SBFD symbols. In one or more embodiments, a 1 bit SBFD indicator may be included in the DCI format l_0 with CRC scrambled by C-RNTI for PDCCH order RACH procedure, where bit “0” may be used to indicate that the PRACH occasions are within the non-SBFD symbols, while bit “1” may be used to indicate that the PRACH occasions are within the SBFD symbols. In one or more embodiments, a separate PRACH configuration may be configured for SBFD aware UEs, and when a PRACH occasion of the separate PRACH configuration in the non-SBFD symbols overlaps with the PRACH occasion that is configured for legacy UEs, the PRACH occasion of the separate PRACH configuration in the non-SBFD symbols for SBFD aware UEs may be invalid.

References:

[1]. 3GPP TS 38.212, V18.0.0: “NR: Multiplexing and channel coding”

[2], 3GPP TS 38.321, V18.0.0: “NR: Medium Access Control (MAC) protocol specification”

In some embodiments, the electronic device(s), network(s), system(s), chip(s) or component(s), or portions or implementations thereof, of the figures herein may be configured to perform one or more processes, techniques, or methods as described herein, or portions thereof. One such process is depicted in FIG. 5.

For example, the process may include, at 502, establishing a separate physical random access channel (PRACH) configuration for subband non-overlapping full duplex (SBFD) aware UEs.

The process further includes, at 504, validating PRACH occasions by determining whether a PRACH occasion in the separate configuration within non-SBFD symbols overlaps with a PRACH occasion configured for legacy UEs.

The process further includes, at 506, invalidating the PRACH occasion in the separate configuration when overlap with the legacy configuration is detected. The process further includes, at 508, applying this validation process to both 4-step and 2-step random access channel (RACH) procedures to ensure efficient operation for SBFD aware UEs.

For one or more embodiments, at least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and/or methods as set forth in the example section below. For example, the baseband circuitry as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below. For another example, circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below in the example section.

It is understood that the above descriptions are for purposes of illustration and are not meant to be limiting.

The figures described below illustrate illustrate various systems, devices, and components that may implement aspects of disclosed embodiments.

FIG. 6 illustrates an example network architecture 600 according to various embodiments. The network 600 may operate in a manner consistent with 3 GPP technical specifications for LTE or 5G/NR systems. However, the example embodiments are not limited in this regard and the described embodiments may apply to other networks that benefit from the principles described herein, such as future 3 GPP systems, or the like.

The network 600 includes a UE 602, which is any mobile or non-mobile computing device designed to communicate with a RAN 604 via an over-the-air connection. The UE 602 is communicatively coupled with the RAN 604 by a Uu interface, which may be applicable to both LTE and NR systems. Examples of the UE 602 include, but are not limited to, a smartphone, tablet computer, wearable computer, desktop computer, laptop computer, in- vehicle infotainment system, in-car entertainment system, instrument cluster, head-up display (HUD) device, onboard diagnostic device, dashtop mobile equipment, mobile data terminal, electronic engine management system, electronic/engine control unit, electronic/engine control module, embedded system, sensor, microcontroller, control module, engine management system, networked appliance, machine-type communication device, machine-to-machine (M2M), device-to-device (D2D), machine-type communication (MTC) device, Internet of Things (loT) device, and/or the like. The network 600 may include a plurality of UEs 602 coupled directly with one another via a D2D, ProSe, PCS, and/or sidelink (SL) interface. These UEs 602 may be M2M/D2D/MTC/IoT devices and/or vehicular systems that communicate using physical sidelink channels such as, but not limited to, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc. The UE 602 may perform blind decoding attempts of SL channels/links according to the various embodiments herein.

In some embodiments, the UE 602 may additionally communicate with an AP 606 via an over-the-air (OTA) connection. The AP 606 manages a WLAN connection, which may serve to offload some/all network traffic from the RAN 604. The connection between the UE 602 and the AP 606 may be consistent with any IEEE 802.11 protocol. Additionally, the UE 602, RAN 604, and AP 606 may utilize cellular-WLAN aggregation/integration (e.g., LWA/LWIP). Cellular-WLAN aggregation may involve the UE 602 being configured by the RAN 604 to utilize both cellular radio resources and WLAN resources.

The RAN 604 includes one or more access network nodes (ANs) 608. The ANs 608 terminate air-interface(s) for the UE 602 by providing access stratum protocols including RRC, PDCP, RLC, MAC, and PHY/L1 protocols. In this manner, the AN 608 enables data/voice connectivity between CN 620 and the UE 602. The ANs 608 may be a macrocell base station or a low power base station for providing femtocells, picocells or other like cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells; or some combination thereof. In these implementations, an AN 608 be referred to as a BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, etc.

One example implementation is a “CU/DU split” architecture where the ANs 608 are embodied as a gNB-Central Unit (CU) that is communicatively coupled with one or more gNB- Distributed Units (DUs), where each DU may be communicatively coupled with one or more Radio Units (RUs) (also referred to as RRHs, RRUs, or the like) (see e.g., 3GPP TS 38.401 vl6.1.0 (2020-03)). In some implementations, the one or more RUs may be individual RSUs. In some implementations, the CU/DU split may include an ng-eNB-CU and one or more ng- eNB-DUs instead of, or in addition to, the gNB-CU and gNB-DUs, respectively. The ANs 608 employed as the CU may be implemented in a discrete device or as one or more software entities running on server computers as part of, for example, a virtual network including a virtual Base Band Unit (BBU) or BBU pool, cloud RAN (CRAN), Radio Equipment Controller (REC), Radio Cloud Center (RCC), centralized RAN (C-RAN), virtualized RAN (vRAN), and/or the like (although these terms may refer to different implementation concepts). Any other type of architectures, arrangements, and/or configurations can be used.

The plurality of ANs may be coupled with one another via an X2 interface (if the RAN 604 is an LTE RAN or Evolved Universal Terrestrial Radio Access Network (E-UTRAN) 610) or an Xn interface (if the RAN 604 is a NG-RAN 614). The X2/Xn interfaces, which may be separated into control/user plane interfaces in some embodiments, may allow the ANs to communicate information related to handovers, data/context transfers, mobility, load management, interference coordination, etc.

The ANs of the RAN 604 may each manage one or more cells, cell groups, component carriers, etc. to provide the UE 602 with an air interface for network access. The UE 602 may be simultaneously connected with a plurality of cells provided by the same or different ANs 608 of the RAN 604. For example, the UE 602 and RAN 604 may use carrier aggregation to allow the UE 602 to connect with a plurality of component carriers, each corresponding to a Pcell or Scell. In dual connectivity scenarios, a first AN 608 may be a master node that provides an MCG and a second AN 608 may be secondary node that provides an SCG. The first/second ANs 608 may be any combination of eNB, gNB, ng-eNB, etc.

The RAN 604 may provide the air interface over a licensed spectrum or an unlicensed spectrum. To operate in the unlicensed spectrum, the nodes may use LAA, eLAA, and/or feLAA mechanisms based on CA technology with PCells/Scells. Prior to accessing the unlicensed spectrum, the nodes may perform medium/carrier-sensing operations based on, for example, a listen-before-talk (LBT) protocol.

In V2X scenarios the UE 602 or AN 608 may be or act as a roadside unit (RSU), which may refer to any transportation infrastructure entity used for V2X communications. An RSU may be implemented in or by a suitable AN or a stationary (or relatively stationary) UE. An RSU implemented in or by: a UE may be referred to as a “UE-type RSU”; an eNB may be referred to as an “eNB-type RSU”; a gNB may be referred to as a “gNB-type RSU”; and the like. In one example, an RSU is a computing device coupled with radio frequency circuitry located on a roadside that provides connectivity support to passing vehicle UEs. The RSU may also include internal data storage circuitry to store intersection map geometry, traffic statistics, media, as well as applications/software to sense and control ongoing vehicular and pedestrian traffic. The RSU may provide very low latency communications required for high speed events, such as crash avoidance, traffic warnings, and the like. Additionally or alternatively, the RSU may provide other cellular/WLAN communications services. The components of the RSU may be packaged in a weatherproof enclosure suitable for outdoor installation, and may include a network interface controller to provide a wired connection (e.g., Ethernet) to a traffic signal controller or a backhaul network.

In some embodiments, the RAN 604 may be an E-UTRAN 610 with one or more eNBs 612. The an E-UTRAN 610 provides an LTE air interface (Uu) with the following characteristics: SCS of 15 kHz; CP-OFDM waveform for DL and SC-FDMA waveform for UL; turbo codes for data and TBCC for control; etc. The LTE air interface may rely on CSI- RS for CSI acquisition and beam management; PDSCH/PDCCH DMRS for PDSCH/PDCCH demodulation; and CRS for cell search and initial acquisition, channel quality measurements, and channel estimation for coherent demodulation/detection at the UE. The LTE air interface may operating on sub- 6 GHz bands.

In some embodiments, the RAN 604 may be an next generation (NG)-RAN 614 with one or more gNB 616 and/or on or more ng-eNB 618. The gNB 616 connects with 5G-enabled UEs 602 using a 5G NR interface. The gNB 616 connects with a 5GC 640 through an NG interface, which includes an N2 interface or an N3 interface. The ng-eNB 618 also connects with the 5GC 640 through an NG interface, but may connect with a UE 602 via the Uu interface. The gNB 616 and the ng-eNB 618 may connect with each other over an Xn interface.

In some embodiments, the NG interface may be split into two parts, an NG user plane (NG-U) interface, which carries traffic data between the nodes of the NG-RAN 614 and a UPF 648 (e.g., N3 interface), and an NG control plane (NG-C) interface, which is a signaling interface between the nodes of the NG-RAN 614 and an AMF 644 (e.g., N2 interface).

The NG-RAN 614 may provide a 5G-NR air interface (which may also be referred to as a Uu interface) with the following characteristics: variable SCS; CP-OFDM for DL, CP- OFDM and DFT-s-OFDM for UL; polar, repetition, simplex, and Reed-Muller codes for control and LDPC for data. The 5G-NR air interface may rely on CSLRS, PDSCH/PDCCH DMRS similar to the LTE air interface. The 5G-NR air interface may not use a CRS, but may use PBCH DMRS for PBCH demodulation; PTRS for phase tracking for PDSCH; and tracking reference signal for time tracking. The 5G-NR air interface may operating on FR1 bands that include sub-6 GHz bands or FR2 bands that include bands from 24.25 GHz to 52.6 GHz. The 5G-NR air interface may include an SSB that is an area of a downlink resource grid that includes PSS/SSS/PBCH.

The 5G-NR air interface may utilize BWPs for various purposes. For example, BWP can be used for dynamic adaptation of the SCS. For example, the UE 602 can be configured with multiple BWPs where each BWP configuration has a different SCS. When a BWP change is indicated to the UE 602, the SCS of the transmission is changed as well. Another use case example of BWP is related to power saving. In particular, multiple BWPs can be configured for the UE 602 with different amount of frequency resources (e.g., PRBs) to support data transmission under different traffic loading scenarios. A BWP containing a smaller number of PRBs can be used for data transmission with small traffic load while allowing power saving at the UE 602 and in some cases at the gNB 616. A BWP containing a larger number of PRBs can be used for scenarios with higher traffic load.

The RAN 604 is communicatively coupled to CN 620 that includes network elements and/or network functions (NFs) to provide various functions to support data and telecommunications services to customers/subscribers (e.g., UE 602). The components of the CN 620 may be implemented in one physical node or separate physical nodes. In some embodiments, NEV may be utilized to virtualize any or all of the functions provided by the network elements of the CN 620 onto physical compute/storage resources in servers, switches, etc. A logical instantiation of the CN 620 may be referred to as a network slice, and a logical instantiation of a portion of the CN 620 may be referred to as a network sub-slice.

The CN 620 may be an LTE CN 622 (also referred to as an Evolved Packet Core (EPC) 622). The EPC 622 may include MME 624, SGW 626, SGSN 628, HSS 630, PGW 632, and PCRF 634 coupled with one another over interfaces (or “reference points”) as shown. The NFs in the EPC 622 are briefly introduced as follows.

The MME 624 implements mobility management functions to track a current location of the UE 602 to facilitate paging, bearer activation/deactivation, handovers, gateway selection, authentication, etc.

The SGW 626 terminates an SI interface toward the RAN 610 and routes data packets between the RAN 610 and the EPC 622. The SGW 626 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement.

The SGSN 628 tracks a location of the UE 602 and performs security functions and access control. The SGSN 628 also performs inter-EPC node signaling for mobility between different RAT networks; PDN and S-GW selection as specified by MME 624; MME 624 selection for handovers; etc. The S3 reference point between the MME 624 and the SGSN 628 enable user and bearer information exchange for inter-3GPP access network mobility in idle/active states.

The HSS 630 includes a database for network users, including subscription-related information to support the network entities’ handling of communication sessions. The HSS 630 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc. An S6a reference point between the HSS 630 and the MME 624 may enable transfer of subscription and authentication data for authenticating/authorizing user access to the EPC 620. The PGW 632 may terminate an SGi interface toward a data network (DN) 636 that may include an application (app)/content server 638. The PGW 632 routes data packets between the EPC 622 and the data network 636. The PGW 632 is communicatively coupled with the SGW 626 by an S5 reference point to facilitate user plane tunneling and tunnel management. The PGW 632 may further include a node for policy enforcement and charging data collection (e.g., PCEF). Additionally, the SGi reference point may communicatively couple the PGW 632 with the same or different data network 636. The PGW 632 may be communicatively coupled with a PCRF 634 via a Gx reference point.

The PCRF 634 is the policy and charging control element of the EPC 622. The PCRF 634 is communicatively coupled to the app/content server 638 to determine appropriate QoS and charging parameters for service flows. The PCRF 632 also provisions associated rules into a PCEF (via Gx reference point) with appropriate TFT and QCI.

The CN 620 may be a 5GC 640 including an AUSF 642, AMF 644, SMF 646, UPF 648, NSSF 650, NEF 652, NRF 654, PCF 656, UDM 658, and AF 660 coupled with one another over various interfaces as shown. The NFs in the 5GC 640 are briefly introduced as follows.

The AUSF 642 stores data for authentication of UE 602 and handle authentication- related functionality. The AUSF 642 may facilitate a common authentication framework for various access types..

The AMF 644 allows other functions of the 5GC 640 to communicate with the UE 602 and the RAN 604 and to subscribe to notifications about mobility events with respect to the UE 602. The AMF 644 is also responsible for registration management (e.g., for registering UE 602), connection management, reachability management, mobility management, lawful interception of AMF-related events, and access authentication and authorization. The AMF 644 provides transport for SM messages between the UE 602 and the SMF 646, and acts as a transparent proxy for routing SM messages. AMF 644 also provides transport for SMS messages between UE 602 and an SMSF. AMF 644 interacts with the AUSF 642 and the UE 602 to perform various security anchor and context management functions. Furthermore, AMF 644 is a termination point of a RAN-CP interface, which includes the N2 reference point between the RAN 604 and the AMF 644. The AMF 644 is also a termination point of NAS (Nl) signaling, and performs NAS ciphering and integrity protection.

AMF 644 also supports NAS signaling with the UE 602 over an N3IWF interface. The N3IWF provides access to untrusted entities. N3IWF may be a termination point for the N2 interface between the (R)AN 604 and the AMF 644 for the control plane, and may be a termination point for the N3 reference point between the (R)AN 614 and the 648 for the user plane. As such, the AMF 644 handles N2 signalling from the SMF 646 and the AMF 644 for PDU sessions and QoS, encapsulate/de-encapsulate packets for IPSec and N3 tunnelling, marks N3 user-plane packets in the uplink, and enforces QoS corresponding to N3 packet marking taking into account QoS requirements associated with such marking received over N2. N3IWF may also relay UL and DL control-plane NAS signalling between the UE 602 and AMF 644 via an N1 reference point between the UE 602and the AMF 644, and relay uplink and downlink user-plane packets between the UE 602 and UPF 648. The N3IWF also provides mechanisms for IPsec tunnel establishment with the UE 602. The AMF 644 may exhibit an Namf servicebased interface, and may be a termination point for an N14 reference point between two AMFs 644 and an N17 reference point between the AMF 644 and a 5G-EIR (not shown by FIG. 6).

The SMF 646 is responsible for SM (e.g., session establishment, tunnel management between UPF 648 and AN 608); UE IP address allocation and management (including optional authorization); selection and control of UP function; configuring traffic steering at UPF 648 to route traffic to proper destination; termination of interfaces toward policy control functions; controlling part of policy enforcement, charging, and QoS; lawful intercept (for SM events and interface to LI system); termination of SM parts of NAS messages; downlink data notification; initiating AN specific SM information, sent via AMF 644 over N2 to AN 608; and determining SSC mode of a session. SM refers to management of a PDU session, and a PDU session or “session” refers to a PDU connectivity service that provides or enables the exchange of PDUs between the UE 602 and the DN 636.

The UPF 648 acts as an anchor point for intra- RAT and inter-RAT mobility, an external PDU session point of interconnect to data network 636, and a branching point to support multihomed PDU session. The UPF 648 also performs packet routing and forwarding, packet inspection, enforces user plane part of policy rules, lawfully intercept packets (UP collection), performs traffic usage reporting, perform QoS handling for a user plane (e.g., packet filtering, gating, UL/DL rate enforcement), performs uplink traffic verification (e.g., SDF-to-QoS flow mapping), transport level packet marking in the uplink and downlink, and performs downlink packet buffering and downlink data notification triggering. UPF 648 may include an uplink classifier to support routing traffic flows to a data network.

The NSSF 650 selects a set of network slice instances serving the UE 602. The NSSF 650 also determines allowed NSSAI and the mapping to the subscribed S-NSSAIs, if needed. The NSSF 650 also determines an AMF set to be used to serve the UE 602, or a list of candidate AMFs 644 based on a suitable configuration and possibly by querying the NRF 654. The selection of a set of network slice instances for the UE 602 may be triggered by the AMF 644 with which the UE 602 is registered by interacting with the NSSF 650; this may lead to a change of AMF 644. The NSSF 650 interacts with the AMF 644 via an N22 reference point; and may communicate with another NSSF in a visited network via an N31 reference point (not shown).

The NEF 652 securely exposes services and capabilities provided by 3GPP NFs for third party, internal exposure/re-exposure, AFs 660, edge computing or fog computing systems (e.g., edge compute node, etc. In such embodiments, the NEF 652 may authenticate, authorize, or throttle the AFs. NEF 652 may also translate information exchanged with the AF 660 and information exchanged with internal network functions. For example, the NEF 652 may translate between an AF-Service-Identifier and an internal 5GC information. NEF 652 may also receive information from other NFs based on exposed capabilities of other NFs. This information may be stored at the NEF 652 as structured data, or at a data storage NF using standardized interfaces. The stored information can then be re-exposed by the NEF 652 to other NFs and AFs, or used for other purposes such as analytics.

The NRF 654 supports service discovery functions, receives NF discovery requests from NF instances, and provides information of the discovered NF instances to the requesting NF instances. NRF 654 also maintains information of available NF instances and their supported services. The NRF 654 also supports service discovery functions, wherein the NRF 654 receives NF Discovery Request from NF instance or an SCP (not shown), and provides information of the discovered NF instances to the NF instance or SCP.

The PCF 656 provides policy rules to control plane functions to enforce them, and may also support unified policy framework to govern network behavior. The PCF 656 may also implement a front end to access subscription information relevant for policy decisions in a UDR of the UDM 658. In addition to communicating with functions over reference points as shown, the PCF 656 exhibit an Npcf service-based interface.

The UDM 658 handles subscription-related information to support the network entities’ handling of communication sessions, and stores subscription data of UE 602. For example, subscription data may be communicated via an N8 reference point between the UDM 658 and the AMF 644. The UDM 658 may include two parts, an application front end and a UDR. The UDR may store subscription data and policy data for the UDM 658 and the PCF 656, and/or structured data for exposure and application data (including PFDs for application detection, application request information for multiple UEs 602) for the NEF 652. The Nudr servicebased interface may be exhibited by the UDR 221 to allow the UDM 658, PCF 656, and NEF 652 to access a particular set of the stored data, as well as to read, update (e.g., add, modify), delete, and subscribe to notification of relevant data changes in the UDR. The UDM may include a UDM-FE, which is in charge of processing credentials, location management, subscription management and so on. Several different front ends may serve the same user in different transactions. The UDM-FE accesses subscription information stored in the UDR and performs authentication credential processing, user identification handling, access authorization, registration/mobility management, and subscription management. In addition to communicating with other NFs over reference points as shown, the UDM 658 may exhibit the Nudm service-based interface.

AF 660 provides application influence on traffic routing, provide access to NEF 652, and interact with the policy framework for policy control. The AF 660 may influence UPF 648 (re)selection and traffic routing. Based on operator deployment, when AF 660 is considered to be a trusted entity, the network operator may permit AF 660 to interact directly with relevant NFs. Additionally, the AF 660 may be used for edge computing implementations,

The 5GC 640 may enable edge computing by selecting operator/3rd party services to be geographically close to a point that the UE 602 is attached to the network. This may reduce latency and load on the network. In edge computing implementations, the 5GC 640 may select a UPF 648 close to the UE 602 and execute traffic steering from the UPF 648 to DN 636 via the N6 interface. This may be based on the UE subscription data, UE location, and information provided by the AF 660, which allows the AF 660 to influence UPF (re)selection and traffic routing.

The data network (DN) 636 may represent various network operator services, Internet access, or third party services that may be provided by one or more servers including, for example, application (app)/content server 638. The DN 636 may be an operator external public, a private PDN, or an intra-operator packet data network, for example, for provision of IMS services. In this embodiment, the app server 638 can be coupled to an IMS via an S-CSCF or the I-CSCF. In some implementations, the DN 636 may represent one or more local area DNs (LADNs), which are DNs 636 (or DN names (DNNs)) that is/are accessible by a UE 602 in one or more specific areas. Outside of these specific areas, the UE 602 is not able to access the LADN/DN 636.

Additionally or alternatively, the DN 636 may be an Edge DN 636, which is a (local) Data Network that supports the architecture for enabling edge applications. In these embodiments, the app server 638 may represent the physical hardware systems/de vices providing app server functionality and/or the application software resident in the cloud or at an edge compute node that performs server function(s). In some embodiments, the app/content server 638 provides an edge hosting environment that provides support required for Edge Application Server’ s execution.

In some embodiments, the 5GS can use one or more edge compute nodes to provide an interface and offload processing of wireless communication traffic. In these embodiments, the edge compute nodes may be included in, or co-located with one or more RAN610, 614. For example, the edge compute nodes can provide a connection between the RAN 614 and UPF 648 in the 5GC 640. The edge compute nodes can use one or more NFV instances instantiated on virtualization infrastructure within the edge compute nodes to process wireless connections to and from the RAN 614 and UPF 648.

The interfaces of the 5GC 640 include reference points and service-based itnterfaces. The reference points include: N1 (between the UE 602 and the AMF 644), N2 (between RAN 614 and AMF 644), N3 (between RAN 614 and UPF 648), N4 (between the SMF 646 and UPF 648), N5 (between PCF 656 and AF 660), N6 (between UPF 648 and DN 636), N7 (between SMF 646 and PCF 656), N8 (between UDM 658 and AMF 644), N9 (between two UPFs 648), N10 (between the UDM 658 and the SMF 646), Ni l (between the AMF 644 and the SMF 646), N12 (between AUSF 642 and AMF 644), N13 (between AUSF 642 and UDM 658), N14 (between two AMFs 644; not shown), N15 (between PCF 656 and AMF 644 in case of a nonroaming scenario, or between the PCF 656 in a visited network and AMF 644 in case of a roaming scenario), N16 (between two SMFs 646; not shown), and N22 (between AMF 644 and NSSF 650). Other reference point representations not shown in FIG. 6 can also be used. The service-based representation of FIG. 6 represents NFs within the control plane that enable other authorized NFs to access their services. The service-based interfaces (SBIs) include: Namf (SBI exhibited by AMF 644), Nsmf (SBI exhibited by SMF 646), Nnef (SBI exhibited by NEF 652), Npcf (SBI exhibited by PCF 656), Nudm (SBI exhibited by the UDM 658), Naf (SBI exhibited by AF 660), Nnrf (SBI exhibited by NRF 654), Nnssf (SBI exhibited by NSSF 650), Nausf (SBI exhibited by AUSF 642). Other service-based interfaces (e.g., Nudr, N5g-eir, and Nudsf) not shown in FIG. 6 can also be used. In some embodiments, the NEF 652 can provide an interface to edge compute nodes 636x, which can be used to process wireless connections with the RAN 614. In some implementations, the system 600 may include an SMSF, which is responsible for SMS subscription checking and verification, and relaying SM messages to/from the UE 602 to/from other entities, such as an SMS-GMSC/IWMSC/SMS- router. The SMS may also interact with AMF 644 and UDM 658 for a notification procedure that the UE 602 is available for SMS transfer (e.g., set a UE not reachable flag, and notifying UDM 658 when UE 602 is available for SMS).

The 5GS may also include an SCP (or individual instances of the SCP) that supports indirect communication (see e.g., 3GPP TS 23.501 section 7.1.1); delegated discovery (see e.g., 3GPP TS 23.501 section 7.1.1); message forwarding and routing to destination NF/NF service(s), communication security (e.g., authorization of the NF Service Consumer to access the NF Service Producer API) (see e.g., 3GPP TS 33.501), load balancing, monitoring, overload control, etc.; and discovery and selection functionality for UDM(s), AUSF(s), UDR(s), PCF(s) with access to subscription data stored in the UDR based on UE’s SUPI, SUCI or GPSI (see e.g., 3GPP TS 23.501 section 6.3). Load balancing, monitoring, overload control functionality provided by the SCP may be implementation specific. The SCP may be deployed in a distributed manner. More than one SCP can be present in the communication path between various NF Services. The SCP, although not an NF instance, can also be deployed distributed, redundant, and scalable.

FIG. 7 schematically illustrates a wireless network 700 in accordance with various embodiments. The wireless network 700 may include a UE 702 in wireless communication with an AN 704. The UE 702 and AN 704 may be similar to, and substantially interchangeable with, like-named components described with respect to FIG. 6.

The UE 702 may be communicatively coupled with the AN 704 via connection 706. The connection 706 is illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols such as an LTE protocol or a 5G NR protocol operating at mmWave or sub-6GHz frequencies.

The UE 702 may include a host platform 708 coupled with a modem platform 710. The host platform 708 may include application processing circuitry 712, which may be coupled with protocol processing circuitry 714 of the modem platform 710. The application processing circuitry 712 may run various applications for the UE 702 that source/sink application data. The application processing circuitry 712 may further implement one or more layer operations to transmit/receive application data to/from a data network. These layer operations may include transport (for example UDP) and Internet (for example, IP) operations

The protocol processing circuitry 714 may implement one or more of layer operations to facilitate transmission or reception of data over the connection 706. The layer operations implemented by the protocol processing circuitry 714 may include, for example, MAC, RLC, PDCP, RRC and NAS operations. The modem platform 710 may further include digital baseband circuitry 716 that may implement one or more layer operations that are “below” layer operations performed by the protocol processing circuitry 714 in a network protocol stack. These operations may include, for example, PHY operations including one or more of HARQ acknowledgement (ACK) functions, scrambling/descrambling, encoding/decoding, layer mapping/de-mapping, modulation symbol mapping, received symbol/bit metric determination, multi-antenna port precoding/decoding, which may include one or more of space-time, space-frequency or spatial coding, reference signal generation/detection, preamble sequence generation and/or decoding, synchronization sequence generation/detection, control channel signal blind decoding, and other related functions.

The modem platform 710 may further include transmit circuitry 718, receive circuitry 720, RF circuitry 722, and RF front end (RFFE) 724, which may include or connect to one or more antenna panels 726. Briefly, the transmit circuitry 718 may include a digital-to-analog converter, mixer, intermediate frequency (IF) components, etc.; the receive circuitry 720 may include an analog-to-digital converter, mixer, IF components, etc.; the RF circuitry 722 may include a low-noise amplifier, a power amplifier, power tracking components, etc.; RFFE 724 may include filters (for example, surface/bulk acoustic wave filters), switches, antenna tuners, beamforming components (for example, phase-array antenna components), etc. The selection and arrangement of the components of the transmit circuitry 718, receive circuitry 720, RF circuitry 722, RFFE 724, and antenna panels 726 (referred generically as “transmit/receive components”) may be specific to details of a specific implementation such as, for example, whether communication is TDM or FDM, in mmWave or sub-6 gHz frequencies, etc. In some embodiments, the transmit/receive components may be arranged in multiple parallel transmit/receive chains, may be disposed in the same or different chips/modules, etc.

In some embodiments, the protocol processing circuitry 714 may include one or more instances of control circuitry (not shown) to provide control functions for the transmit/receive components.

A UE 702 reception may be established by and via the antenna panels 726, RFFE 724, RF circuitry 722, receive circuitry 720, digital baseband circuitry 716, and protocol processing circuitry 714. In some embodiments, the antenna panels 726 may receive a transmission from the AN 704 by receive-beamforming signals received by a plurality of antennas/antenna elements of the one or more antenna panels 726.

A UE 702 transmission may be established by and via the protocol processing circuitry 714, digital baseband circuitry 716, transmit circuitry 718, RF circuitry 722, RFFE 724, and antenna panels 726. In some embodiments, the transmit components of the UE 704 may apply a spatial filter to the data to be transmitted to form a transmit beam emitted by the antenna elements of the antenna panels 726.

Similar to the UE 702, the AN 704 may include a host platform 728 coupled with a modem platform 730. The host platform 728 may include application processing circuitry 732 coupled with protocol processing circuitry 734 of the modem platform 730. The modem platform may further include digital baseband circuitry 736, transmit circuitry 738, receive circuitry 740, RF circuitry 742, RFFE circuitry 744, and antenna panels 746. The components of the AN 704 may be similar to and substantially interchangeable with like-named components of the UE 702. In addition to performing data transmission/reception as described above, the components of the AN 708 may perform various logical functions that include, for example, RNC functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling.

FIG. 8 illustrates components of a computing device 800 according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein. Specifically, FIG. 8 shows a diagrammatic representation of hardware resources 801 including one or more processors (or processor cores) 810, one or more memory/storage devices 820, and one or more communication resources 830, each of which may be communicatively coupled via a bus 840 or other interface circuitry. For embodiments where node virtualization (e.g., NFV) is utilized, a hypervisor 802 may be executed to provide an execution environment for one or more network slices/sub- slices to utilize the hardware resources 801.

The processors 810 include, for example, processor 812 and processor 814. The processors 810 include circuitry such as, but not limited to one or more processor cores and one or more of cache memory, low drop-out voltage regulators (LDOs), interrupt controllers, serial interfaces such as SPI, I2C or universal programmable serial interface circuit, real time clock (RTC), timer-counters including interval and watchdog timers, general purpose I/O, memory card controllers such as secure digital/multi-media card (SD/MMC) or similar, interfaces, mobile industry processor interface (MIPI) interfaces and Joint Test Access Group (JTAG) test access ports. The processors 810 may be, for example, a central processing unit (CPU), reduced instruction set computing (RISC) processors, Acorn RISC Machine (ARM) processors, complex instruction set computing (CISC) processors, graphics processing units (GPUs), one or more Digital Signal Processors (DSPs) such as a baseband processor, Application-Specific Integrated Circuits (ASICs), an Field-Programmable Gate Array (FPGA), a radio-frequency integrated circuit (RFIC), one or more microprocessors or controllers, another processor (including those discussed herein), or any suitable combination thereof. In some implementations, the processor circuitry 810 may include one or more hardware accelerators, which may be microprocessors, programmable processing devices (e.g., FPGA, complex programmable logic devices (CPLDs), etc.), or the like.

The memory/storage devices 820 may include main memory, disk storage, or any suitable combination thereof. The memory/storage devices 820 may include, but are not limited to, any type of volatile, non-volatile, or semi- volatile memory such as random access memory (RAM), dynamic RAM (DRAM), static RAM (SRAM), synchronous DRAM (SDRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), Flash memory, solid-state storage, phase change RAM (PRAM), resistive memory such as magnetoresistive random access memory (MRAM), etc., and may incorporate three-dimensional (3D) cross-point (XPOINT) memories from Intel® and Micron®. The memory/storage devices 820 may also comprise persistent storage devices, which may be temporal and/or persistent storage of any type, including, but not limited to, nonvolatile memory, optical, magnetic, and/or solid state mass storage, and so forth.

The communication resources 830 may include interconnection or network interface controllers, components, or other suitable devices to communicate with one or more peripheral devices 804 or one or more databases 806 or other network elements via a network 808. For example, the communication resources 830 may include wired communication components (e.g., for coupling via USB, Ethernet, Ethernet, Ethernet over GRE Tunnels, Ethernet over Multiprotocol Label Switching (MPLS), Ethernet over USB, Controller Area Network (CAN), Local Interconnect Network (LIN), DeviceNet, ControlNet, Data Highway-i-, PROFIBUS, or PROFINET, among many others), cellular communication components, NFC components, Bluetooth® (or Bluetooth® Low Energy) components, WiFi® components, and other communication components. Network connectivity may be provided to/from the computing device 800 via the communication resources 830 using a physical connection, which may be electrical (e.g., a “copper interconnect”) or optical. The physical connection also includes suitable input connectors (e.g., ports, receptacles, sockets, etc.) and output connectors (e.g., plugs, pins, etc.). The communication resources 830 may include one or more dedicated processors and/or FPGAs to communicate using one or more of the aforementioned network interface protocols. Instructions 850 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 810 to perform any one or more of the methodologies discussed herein. The instructions 850 may reside, completely or partially, within at least one of the processors 810 (e.g., within the processor’s cache memory), the memory /storage devices 820, or any suitable combination thereof. Furthermore, any portion of the instructions 850 may be transferred to the hardware resources 801 from any combination of the peripheral devices 804 or the databases 806. Accordingly, the memory of processors 810, the memory /storage devices 820, the peripheral devices 804, and the databases 806 are examples of computer-readable and machine-readable media.

FIG. 9 illustrates a network 900 in accordance with various embodiments. The network 900 may operate in a matter consistent with 3GPP technical specifications or technical reports for 6G systems. In some embodiments, the network 900 may operate concurrently with network 600. For example, in some embodiments, the network 900 may share one or more frequency or bandwidth resources with network 600. As one specific example, a UE (e.g., UE 902) may be configured to operate in both network 900 and network 600. Such configuration may be based on a UE including circuitry configured for communication with frequency and bandwidth resources of both networks 600 and 900. In general, several elements of network 900 may share one or more characteristics with elements of network 600. For the sake of brevity and clarity, such elements may not be repeated in the description of network 900.

The network 900 may include a UE 902, which may include any mobile or non-mobile computing device designed to communicate with a RAN 908 via an over-the-air connection. The UE 902 may be similar to, for example, UE 602. The UE 902 may be, but is not limited to, a smartphone, tablet computer, wearable computer device, desktop computer, laptop computer, in-vehicle infotainment, in-car entertainment device, instrument cluster, head-up display device, onboard diagnostic device, dashtop mobile equipment, mobile data terminal, electronic engine management system, electronic/engine control unit, electronic/engine control module, embedded system, sensor, microcontroller, control module, engine management system, networked appliance, machine-type communication device, M2M or D2D device, loT device, etc.

Although not specifically shown in FIG. 9, in some embodiments the network 900 may include a plurality of UEs coupled directly with one another via a sidelink interface. The UEs may be M2M/D2D devices that communicate using physical sidelink channels such as, but not limited to, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc. Similarly, although not specifically shown in FIG. 9, the UE 902 may be communicatively coupled with an AP such as AP 606 as described with respect to FIG. 6. Additionally, although not specifically shown in FIG. 9, in some embodiments the RAN 908 may include one or more ANss such as AN 608 as described with respect to FIG. 6. The RAN 908 and/or the AN of the RAN 908 may be referred to as a base station (BS), a RAN node, or using some other term or name.

The UE 902 and the RAN 908 may be configured to communicate via an air interface that may be referred to as a sixth generation (6G) air interface. The 6G air interface may include one or more features such as communication in a terahertz (THz) or sub-THz bandwidth, or joint communication and sensing. As used herein, the term “joint communication and sensing” may refer to a system that allows for wireless communication as well as radar-based sensing via various types of multiplexing. As used herein, THz or sub-THz bandwidths may refer to communication in the 80 GHz and above frequency ranges. Such frequency ranges may additionally or alternatively be referred to as “millimeter wave” or “mmWave” frequency ranges.

The RAN 908 may allow for communication between the UE 902 and a 6G core network (CN) 910. Specifically, the RAN 908 may facilitate the transmission and reception of data between the UE 902 and the 6G CN 910. The 6G CN 910 may include various functions such as NSSF 650, NEF 652, NRF 654, PCF 656, UDM 658, AF 660, SMF 646, and AUSF 642. The 6G CN 910 may additional include UPF 648 and DN 636 as shown in FIG. 9.

Additionally, the RAN 908 may include various additional functions that are in addition to, or alternative to, functions of a legacy cellular network such as a 4G or 5G network. Two such functions may include a Compute Control Function (Comp CF) 924 and a Compute Service Function (Comp SF) 936. The Comp CF 924 and the Comp SF 936 may be parts or functions of the Computing Service Plane. Comp CF 924 may be a control plane function that provides functionalities such as management of the Comp SF 936, computing task context generation and management (e.g., create, read, modify, delete), interaction with the underlaying computing infrastructure for computing resource management, etc.. Comp SF 936 may be a user plane function that serves as the gateway to interface computing service users (such as UE 902) and computing nodes behind a Comp SF instance. Some functionalities of the Comp SF 936 may include: parse computing service data received from users to compute tasks executable by computing nodes; hold service mesh ingress gateway or service API gateway; service and charging policies enforcement; performance monitoring and telemetry collection, etc. In some embodiments, a Comp SF 936 instance may serve as the user plane gateway for a cluster of computing nodes. A Comp CF 924 instance may control one or more Comp SF 936 instances. Two other such functions may include a Communication Control Function (Comm CF) 928 and a Communication Service Function (Comm SF) 938, which may be parts of the Communication Service Plane. The Comm CF 928 may be the control plane function for managing the Comm SF 938, communication sessions creation/configuration/releasing, and managing communication session context. The Comm SF 938 may be a user plane function for data transport. Comm CF 928 and Comm SF 938 may be considered as upgrades of SMF 646 and UPF 648, which were described with respect to a 5G system in FIG. 6. The upgrades provided by the Comm CF 928 and the Comm SF 938 may enable service-aware transport. For legacy (e.g., 4G or 5G) data transport, SMF 646 and UPF 648 may still be used.

Two other such functions may include a Data Control Function (Data CF) 922 and Data Service Function (Data SF) 932 may be parts of the Data Service Plane. Data CF 922 may be a control plane function and provides functionalities such as Data SF 932 management, Data service creation/configuration/releasing, Data service context management, etc. Data SF 932 may be a user plane function and serve as the gateway between data service users (such as UE 902 and the various functions of the 6G CN 910) and data service endpoints behind the gateway. Specific functionalities may include include: parse data service user data and forward to corresponding data service endpoints, generate charging data, report data service status.

Another such function may be the Service Orchestration and Chaining Function (SOCF) 920, which may discover, orchestrate and chain up communication/computing/data services provided by functions in the network. Upon receiving service requests from users, SOCF 920 may interact with one or more of Comp CF 924, Comm CF 928, and Data CF 922 to identify Comp SF 936, Comm SF 938, and Data SF 932 instances, configure service resources, and generate the service chain, which could contain multiple Comp SF 936, Comm SF 938, and Data SF 932 instances and their associated computing endpoints. Workload processing and data movement may then be conducted within the generated service chain. The SOCF 920 may also responsible for maintaining, updating, and releasing a created service chain.

Another such function may be the service registration function (SRF) 914, which may act as a registry for system services provided in the user plane such as services provided by service endpoints behind Comp SF 936 and Data SF 932 gateways and services provided by the UE 902. The SRF 914 may be considered a counterpart of NRF 654, which may act as the registry for network functions.

Other such functions may include an evolved service communication proxy (eSCP) and service infrastructure control function (SICF) 926, which may provide service communication infrastructure for control plane services and user plane services. The eSCP may be related to the service communication proxy (SCP) of 5G with user plane service communication proxy capabilities being added. The eSCP is therefore expressed in two parts: eCSP-C 912 and eSCP- U 934, for control plane service communication proxy and user plane service communication proxy, respectively. The SICF 926 may control and configure eCSP instances in terms of service traffic routing policies, access rules, load balancing configurations, performance monitoring, etc.

Another such function is the AMF 944. The AMF 944 may be similar to 644, but with additional functionality. Specifically, the AMF 944 may include potential functional repartition, such as move the message forwarding functionality from the AMF 944 to the RAN 908.

Another such function is the service orchestration exposure function (SOEF) 918. The SOEF may be configured to expose service orchestration and chaining services to external users such as applications.

The UE 902 may include an additional function that is referred to as a computing client service function (comp CSF) 904. The comp CSF 904 may have both the control plane functionalities and user plane functionalities, and may interact with corresponding network side functions such as SOCF 920, Comp CF 924, Comp SF 936, Data CF 922, and/or Data SF 932 for service discovery, request/response, compute task workload exchange, etc. The Comp CSF 904 may also work with network side functions to decide on whether a computing task should be run on the UE 902, the RAN 908, and/or an element of the 6G CN 910.

The UE 902 and/or the Comp CSF 904 may include a service mesh proxy 906. The service mesh proxy 906 may act as a proxy for service-to-service communication in the user plane. Capabilities of the service mesh proxy 906 may include one or more of addressing, security, load balancing, etc.

For one or more embodiments, at least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and/or methods as set forth in the example section below. For example, the baseband circuitry as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below. For another example, circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below in the example section. Additional examples of the presently described embodiments include the following, non-limiting implementations. Each of the following non-limiting examples may stand on its own or may be combined in any permutation or combination with any one or more of the other examples provided below or throughout the present disclosure.

For one or more embodiments, at least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and/or methods as set forth in the example section below. For example, the baseband circuitry as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below. For another example, circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below.

The following examples pertain to further embodiments.

Example 1 may include a method of wireless communication (e.g., for a fifth generation (5G) or new radio (NR) system), the method comprising: receiving, by a UE from a gNodeB (gNB), a subband non-overlapping full duplex (SBFD) indication in the downlink control information (DCI) format l_0 with Cyclic Redundancy Check (CRC) scrambled by Cell - Radio Network Temporary Identifier (C-RNTI) for physical downlink control channel (PDCCH) order random access (RACH) procedure; determining, by the UE, a physical random access channel (PRACH) occasion on either SBFD or non-SBFD symbols in accordance with the SBFD indication; and transmitting, by the UE, the PRACH preamble on the determined RACH occasion.

Example 2 may include the method of example 1 and/or some other example herein, wherein one field may be explicitly included in the DCI format l_0 with CRC scrambled by C-RNTI for PDCCH order RACH procedure to indicate whether the PRACH occasions are within the SBFD or non-SBFD symbols.

Example 3 may include the method of example 1 and/or some other example herein, wherein 1 bit SBFD indicator may be included in the DCI format l_0 with CRC scrambled by C-RNTI for PDCCH order RACH procedure, where bit “0” may be used to indicate that the PRACH occasions are within the non-SBFD symbols, while bit “1” may be used to indicate that the PRACH occasions are within the SBFD symbols.

Example 4 may include the method of example 1 and/or some other example herein, wherein whether the SBFD indication field is present may be configured by higher layers via NR remaining minimum system information (RMSI), NR other system information (OSI) or dedicated radio resource control (RRC) signalling.

Example 5 may include the method of example 1 and/or some other example herein, wherein when the SBFD indication field is not present in the DCI format l_0 with CRC scrambled by C-RNTI for PDCCH order RACH procedure, UE may transmit the PRACH in a PRACH occasion in the non-SBFD symbols.

Example 6 may include the method of example 1 and/or some other example herein, wherein one of the existing fields in the DCI format l_0 with CRC scrambled by C-RNTI for PDCCH order RACH procedure may be repurposed to indicate whether the PRACH occasions are within the SBFD or non-SBFD symbols.

Example 7 may include the method of example 1 and/or some other example herein, wherein some reserved states in PRACH Mask Index may be used to indicate whether the PRACH occasions are within the SBFD or non-SBFD symbols.

Example 8 may include the method of example 1 and/or some other example herein, wherein if UE supports the SBFD operation and when two RACH configurations are configured for SBFD symbols and non-SBFD symbols, respectively, and when gNB initiates PDCCH ordered PRACH transmissions, UE may determine a PRACH occasion in accordance with the indicated SSB index and PRACH mask index and as the first in time and/or frequency domain between the RACH configurations in SBFD and non-SBFD symbols.

Example 9 may include the method of example 1 and/or some other example herein, wherein a separate PRACH configuration is configured for SBFD aware UEs, and when a PRACH occasion of the separate PRACH configuration in the non-SBFD symbols overlaps with the PRACH occasion that is configured for legacy UEs, the PRACH occasion of the separate PRACH configuration in the non-SBFD symbols for SBFD aware UEs is invalid.

Example 10 may include a method of a user equipment (UE), the method comprising: receiving a downlink control information with Cyclic Redundancy Check (CRC) scrambled by Cell - Radio Network Temporary Identifier (C-RNTI) for a physical downlink control channel (PDCCH) order random access (RACH) procedure, wherein the DCI includes a subband non-overlapping full duplex (SBFD) indication; determining a physical random access channel (PRACH) occasion in accordance with the SBFD indication; and transmitting a PRACH preamble on the determined PRACH occasion.

Example 11 may include the method of example 10 and/or some other example herein, wherein the DCI has a DCI format l_0. Example 12 may include the method of example 10-11 and/or some other example herein, wherein the PRACH occasion is on one or more SBFD symbols or non-SBFD symbols.

Example 13 may include the method of example 10-12 and/or some other example herein, wherein the SBFD indication is included in a field of the DCI to indicate whether PRACH occasions are in SBFD or non-SBFD symbols.

Example 14 may include the method of example 13 and/or some other example herein, wherein the SBFD indicator is one bit, wherein a first value (e.g., bit “0”) indicates that the PRACH occasions are within the non-SBFD symbols, and a second value (e.g., bit “1”) indicates that the PRACH occasions are within the SBFD symbols.

Example 15 may include the method of example 10-14 and/or some other example herein, further comprising receiving configuration information to indicate whether the DCI is to include a field for the SBFD indication.

Example 16 may include the method of example 15 and/or some other example herein, wherein the configuration information is received via NR remaining minimum system information (RMSI), NR other system information (OSI) or dedicated radio resource control (RRC) signalling.

Example 17 may include the method of example 10-16 and/or some other example herein, wherein an existing field in the DCI is repurposed to include the SBFD indication.

Example 18 may include the method of example 10-17 and/or some other example herein, wherein the SBFD indication is included in a PRACH Mask Index field of the DCI.

Example 19 may include the method of example 10-18 and/or some other example herein, further comprising receiving a first RACH configuration for SBFD symbols and a second RACH configuration for non-SBFD symbols; wherein the PRACH occasion is determined in accordance with an indicated SSB index and a PRACH mask index and as the first in time and/or frequency domain between the first and second RACH configurations.

Example 20 may include the method of example 10-19 and/or some other example herein, wherein a separate PRACH configuration is configured for SBFD aware UEs, and when a PRACH occasion of the separate PRACH configuration in the non-SBFD symbols overlaps with the PRACH occasion that is configured for legacy UEs, the PRACH occasion of the separate PRACH configuration in the non-SBFD symbols for SBFD aware UEs is invalid.

Example 21 may include an apparatus comprising means for performing any of the methods of examples 1-20. Example 22 may include a network node comprising a communication interface and processing circuitry connected thereto and configured to perform the methods of examples 1- 20.

Example 23 may include an apparatus comprising means to perform one or more elements of a method described in or related to any of examples 1-20, or any other method or process described herein.

Example 24 may include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of a method described in or related to any of examples 1-20, or any other method or process described herein.

Example 25 may include an apparatus comprising logic, modules, or circuitry to perform one or more elements of a method described in or related to any of examples 1-20, or any other method or process described herein.

Example 26 may include a method, technique, or process as described in or related to any of examples 1-20, or portions or parts thereof.

Example 27 may include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1-20, or portions thereof.

Example 28 may include a signal as described in or related to any of examples 1-20, or portions or parts thereof.

Example 29 may include a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of examples 1-20, or portions or parts thereof, or otherwise described in the present disclosure.

Example 30 may include a signal encoded with data as described in or related to any of examples 1-20, or portions or parts thereof, or otherwise described in the present disclosure.

Example 31 may include a signal encoded with a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of examples 1-20, or portions or parts thereof, or otherwise described in the present disclosure.

Example 32 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors is to cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1-20, or portions thereof. Example 33 may include a computer program comprising instructions, wherein execution of the program by a processing element is to cause the processing element to carry out the method, techniques, or process as described in or related to any of examples 1-20, or portions thereof.

Example 34 may include a signal in a wireless network as shown and described herein.

Example 35 may include a method of communicating in a wireless network as shown and described herein.

Example 36 may include a system for providing wireless communication as shown and described herein.

Example 37 may include a device for providing wireless communication as shown and described herein.

An example implementation is an edge computing system, including respective edge processing devices and nodes to invoke or perform the operations of the examples above, or other subject matter described herein. Another example implementation is a client endpoint node, operable to invoke or perform the operations of the examples above, or other subject matter described herein. Another example implementation is an aggregation node, network hub node, gateway node, or core data processing node, within or coupled to an edge computing system, operable to invoke or perform the operations of the examples above, or other subject matter described herein. Another example implementation is an access point, base station, road-side unit, street-side unit, or on-premise unit, within or coupled to an edge computing system, operable to invoke or perform the operations of the examples above, or other subject matter described herein. Another example implementation is an edge provisioning node, service orchestration node, application orchestration node, or multi-tenant management node, within or coupled to an edge computing system, operable to invoke or perform the operations of the examples above, or other subject matter described herein. Another example implementation is an edge node operating an edge provisioning service, application or service orchestration service, virtual machine deployment, container deployment, function deployment, and compute management, within or coupled to an edge computing system, operable to invoke or perform the operations of the examples above, or other subject matter described herein. Another example implementation is an edge computing system operable as an edge mesh, as an edge mesh with side car loading, or with mesh-to-mesh communications, operable to invoke or perform the operations of the examples above, or other subject matter described herein. Another example implementation is an edge computing system including aspects of network functions, acceleration functions, acceleration hardware, storage hardware, or computation hardware resources, operable to invoke or perform the use cases discussed herein, with use of the examples above, or other subject matter described herein. Another example implementation is an edge computing system adapted for supporting client mobility, vehicle-to-vehicle (V2V), vehicle-to-everything (V2X), or vehicle-to-infrastructure (V2I) scenarios, and optionally operating according to ETSI MEC specifications, operable to invoke or perform the use cases discussed herein, with use of the examples above, or other subject matter described herein. Another example implementation is an edge computing system adapted for mobile wireless communications, including configurations according to an 3GPP 4G/LTE or 5G network capabilities, operable to invoke or perform the use cases discussed herein, with use of the examples above, or other subject matter described herein. Another example implementation is a computing system adapted for network communications, including configurations according to an O-RAN capabilities, operable to invoke or perform the use cases discussed herein, with use of the examples above, or other subject matter described herein.

Any of the above-described examples may be combined with any other example (or combination of examples), unless explicitly stated otherwise. The foregoing description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of embodiments to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments.

TERMINOLOGY

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. As used herein, the singular forms “a,” “an” and “the” are intended to include plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specific the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operation, elements, components, and/or groups thereof.

For the purposes of the present disclosure, the phrase “A and/or B” means (A), (B), or (A and B). For the purposes of the present disclosure, the phrase “A, B, and/or C” means (A), (B), (C), (A and B), (A and C), (B and C), or (A, B and C). The description may use the phrases “in an embodiment,” or “In some embodiments,” which may each refer to one or more of the same or different embodiments. Furthermore, the terms “comprising,” “including,” “having,” and the like, as used with respect to embodiments of the present disclosure, are synonymous.

The terms “coupled,” “communicatively coupled,” along with derivatives thereof are used herein. The term “coupled” may mean two or more elements are in direct physical or electrical contact with one another, may mean that two or more elements indirectly contact each other but still cooperate or interact with each other, and/or may mean that one or more other elements are coupled or connected between the elements that are said to be coupled with each other. The term “directly coupled” may mean that two or more elements are in direct contact with one another. The term “communicatively coupled” may mean that two or more elements may be in contact with one another by a means of communication including through a wire or other interconnect connection, through a wireless communication channel or ink, and/or the like.

The term “circuitry” as used herein refers to, is part of, or includes hardware components such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) and/or memory (shared, dedicated, or group), an Application Specific Integrated Circuit (ASIC), a field-programmable device (FPD) (e.g., a field-programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high-capacity PLD (HCPLD), a structured ASIC, or a programmable SoC), digital signal processors (DSPs), etc., that are configured to provide the described functionality. In some embodiments, the circuitry may execute one or more software or firmware programs to provide at least some of the described functionality. The term “circuitry” may also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic system) with the program code used to carry out the functionality of that program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuitry.

The term “processor circuitry” as used herein refers to, is part of, or includes circuitry capable of sequentially and automatically carrying out a sequence of arithmetic or logical operations, or recording, storing, and/or transferring digital data. Processing circuitry may include one or more processing cores to execute instructions and one or more memory structures to store program and data information. The term “processor circuitry” may refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, and/or any other device capable of executing or otherwise operating computer-executable instructions, such as program code, software modules, and/or functional processes. Processing circuitry may include more hardware accelerators, which may be microprocessors, programmable processing devices, or the like. The one or more hardware accelerators may include, for example, computer vision (CV) and/or deep learning (DL) accelerators. The terms “application circuitry” and/or “baseband circuitry” may be considered synonymous to, and may be referred to as, “processor circuitry.”

The term “memory” and/or “memory circuitry” as used herein refers to one or more hardware devices for storing data, including RAM, MRAM, PRAM, DRAM, and/or SDRAM, core memory, ROM, magnetic disk storage mediums, optical storage mediums, flash memory devices or other machine readable mediums for storing data. The term “computer-readable medium” may include, but is not limited to, memory, portable or fixed storage devices, optical storage devices, and various other mediums capable of storing, containing or carrying instructions or data.

The term “interface circuitry” as used herein refers to, is part of, or includes circuitry that enables the exchange of information between two or more components or devices. The term “interface circuitry” may refer to one or more hardware interfaces, for example, buses, I/O interfaces, peripheral component interfaces, network interface cards, and/or the like.

The term “user equipment” or “UE” as used herein refers to a device with radio communication capabilities and may describe a remote user of network resources in a communications network. The term “user equipment” or “UE” may be considered synonymous to, and may be referred to as, client, mobile, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc. Furthermore, the term “user equipment” or “UE” may include any type of wireless/wired device or any computing device including a wireless communications interface.

The term “network element” as used herein refers to physical or virtualized equipment and/or infrastructure used to provide wired or wireless communication network services. The term “network element” may be considered synonymous to and/or referred to as a networked computer, networking hardware, network equipment, network node, router, switch, hub, bridge, radio network controller, RAN device, RAN node, gateway, server, virtualized VNF, NFVI, and/or the like.

The term “computer system” as used herein refers to any type interconnected electronic devices, computer devices, or components thereof. Additionally, the term “computer system” and/or “system” may refer to various components of a computer that are communicatively coupled with one another. Furthermore, the term “computer system” and/or “system” may refer to multiple computer devices and/or multiple computing systems that are communicatively coupled with one another and configured to share computing and/or networking resources.

The term “appliance,” “computer appliance,” or the like, as used herein refers to a computer device or computer system with program code (e.g., software or firmware) that is specifically designed to provide a specific computing resource. A ’’virtual appliance” is a virtual machine image to be implemented by a hypervisor-equipped device that virtualizes or emulates a computer appliance or otherwise is dedicated to provide a specific computing resource. The term “element” refers to a unit that is indivisible at a given level of abstraction and has a clearly defined boundary, wherein an element may be any type of entity including, for example, one or more devices, systems, controllers, network elements, modules, etc., or combinations thereof. The term “device” refers to a physical entity embedded inside, or attached to, another physical entity in its vicinity, with capabilities to convey digital information from or to that physical entity. The term “entity” refers to a distinct component of an architecture or device, or information transferred as a payload. The term “controller” refers to an element or entity that has the capability to affect a physical entity, such as by changing its state or causing the physical entity to move.

The term “cloud computing” or “cloud” refers to a paradigm for enabling network access to a scalable and elastic pool of shareable computing resources with self-service provisioning and administration on-demand and without active management by users. Cloud computing provides cloud computing services (or cloud services), which are one or more capabilities offered via cloud computing that are invoked using a defined interface (e.g., an API or the like). The term “computing resource” or simply “resource” refers to any physical or virtual component, or usage of such components, of limited availability within a computer system or network. Examples of computing resources include usage/access to, for a period of time, servers, processor(s), storage equipment, memory devices, memory areas, networks, electrical power, input/output (peripheral) devices, mechanical devices, network connections (e.g., channels/links, ports, network sockets, etc.), operating systems, virtual machines (VMs), software/applications, computer files, and/or the like. A “hardware resource” may refer to compute, storage, and/or network resources provided by physical hardware element(s). A “virtualized resource” may refer to compute, storage, and/or network resources provided by virtualization infrastructure to an application, device, system, etc. The term “network resource” or “communication resource” may refer to resources that are accessible by computer devices/systems via a communications network. The term “system resources” may refer to any kind of shared entities to provide services, and may include computing and/or network resources. System resources may be considered as a set of coherent functions, network data objects or services, accessible through a server where such system resources reside on a single host or multiple hosts and are clearly identifiable. As used herein, the term “cloud service provider” (or CSP) indicates an organization which operates typically large-scale “cloud” resources comprised of centralized, regional, and edge data centers (e.g., as used in the context of the public cloud). In other examples, a CSP may also be referred to as a Cloud Service Operator (CSO). References to “cloud computing” generally refer to computing resources and services offered by a CSP or a CSO, at remote locations with at least some increased latency, distance, or constraints relative to edge computing.

As used herein, the term “data center” refers to a purpose-designed structure that is intended to house multiple high-performance compute and data storage nodes such that a large amount of compute, data storage and network resources are present at a single location. This often entails specialized rack and enclosure systems, suitable heating, cooling, ventilation, security, fire suppression, and power delivery systems. The term may also refer to a compute and data storage node in some contexts. A data center may vary in scale between a centralized or cloud data center (e.g., largest), regional data center, and edge data center (e.g., smallest).

As used herein, the term “edge computing” refers to the implementation, coordination, and use of computing and resources at locations closer to the “edge” or collection of “edges” of a network. Deploying computing resources at the network’s edge may reduce application and network latency, reduce network backhaul traffic and associated energy consumption, improve service capabilities, improve compliance with security or data privacy requirements (especially as compared to conventional cloud computing), and improve total cost of ownership). As used herein, the term “edge compute node” refers to a real-world, logical, or virtualized implementation of a compute-capable element in the form of a device, gateway, bridge, system or subsystem, component, whether operating in a server, client, endpoint, or peer mode, and whether located at an “edge” of an network or at a connected location further within the network. References to a “node” used herein are generally interchangeable with a “device”, “component”, and “sub-system”; however, references to an “edge computing system” or “edge computing network” generally refer to a distributed architecture, organization, or collection of multiple nodes and devices, and which is organized to accomplish or offer some aspect of services or resources in an edge computing setting. Additionally or alternatively, the term “Edge Computing” refers to a concept, as described in [6], that enables operator and 3rd party services to be hosted close to the UE’s access point of attachment, to achieve an efficient service delivery through the reduced end-to- end latency and load on the transport network. As used herein, the term “Edge Computing Service Provider” refers to a mobile network operator or a 3rd party service provider offering Edge Computing service. As used herein, the term “Edge Data Network” refers to a local Data Network (DN) that supports the architecture for enabling edge applications. As used herein, the term “Edge Hosting Environment” refers to an environment providing support required for Edge Application Server’s execution. As used herein, the term “Application Server” refers to application software resident in the cloud performing the server function.

The term “Internet of Things” or “loT” refers to a system of interrelated computing devices, mechanical and digital machines capable of transferring data with little or no human interaction, and may involve technologies such as real-time analytics, machine learning and/or Al, embedded systems, wireless sensor networks, control systems, automation (e.g., smarthome, smart building and/or smart city technologies), and the like. loT devices are usually low-power devices without heavy compute or storage capabilities. “Edge loT devices” may be any kind of loT devices deployed at a network’s edge.

As used herein, the term “cluster” refers to a set or grouping of entities as part of an edge computing system (or systems), in the form of physical entities (e.g., different computing systems, networks or network groups), logical entities (e.g., applications, functions, security constructs, containers), and the like. In some locations, a “cluster” is also referred to as a “group” or a “domain”. The membership of cluster may be modified or affected based on conditions or functions, including from dynamic or property-based membership, from network or system management scenarios, or from various example techniques discussed below which may add, modify, or remove an entity in a cluster. Clusters may also include or be associated with multiple layers, levels, or properties, including variations in security features and results based on such layers, levels, or properties.

The term “application” may refer to a complete and deploy able package, environment to achieve a certain function in an operational environment. The term “AI/ML application” or the like may be an application that contains some AI/ML models and application-level descriptions. The term “machine learning” or “ML” refers to the use of computer systems implementing algorithms and/or statistical models to perform specific task(s) without using explicit instructions, but instead relying on patterns and inferences. ML algorithms build or estimate mathematical model(s) (referred to as “ML models” or the like) based on sample data (referred to as “training data,” “model training information,” or the like) in order to make predictions or decisions without being explicitly programmed to perform such tasks. Generally, an ML algorithm is a computer program that learns from experience with respect to some task and some performance measure, and an ML model may be any object or data structure created after an ML algorithm is trained with one or more training datasets. After training, an ML model may be used to make predictions on new datasets. Although the term “ML algorithm” refers to different concepts than the term “ML model,” these terms as discussed herein may be used interchangeably for the purposes of the present disclosure.

The term “machine learning model,” “ML model,” or the like may also refer to ML methods and concepts used by an ML-assisted solution. An “ML-assisted solution” is a solution that addresses a specific use case using ML algorithms during operation. ML models include supervised learning (e.g., linear regression, k-nearest neighbor (KNN), decision tree algorithms, support machine vectors, Bayesian algorithm, ensemble algorithms, etc.) unsupervised learning (e.g., K- means clustering, principle component analysis (PCA), etc.), reinforcement learning (e.g., Q-leaming, multi-armed bandit learning, deep RL, etc.), neural networks, and the like. Depending on the implementation a specific ML model could have many sub-models as components and the ML model may train all sub-models together. Separately trained ML models can also be chained together in an ML pipeline during inference. An “ML pipeline” is a set of functionalities, functions, or functional entities specific for an ML-assisted solution; an ML pipeline may include one or several data sources in a data pipeline, a model training pipeline, a model evaluation pipeline, and an actor. The “actor” is an entity that hosts an ML assisted solution using the output of the ML model inference). The term “ML training host” refers to an entity, such as a network function, that hosts the training of the model. The term “ML inference host” refers to an entity, such as a network function, that hosts model during inference mode (which includes both the model execution as well as any online learning if applicable). The ML -host informs the actor about the output of the ML algorithm, and the actor takes a decision for an action (an “action” is performed by an actor as a result of the output of an ML assisted solution). The term “model inference information” refers to information used as an input to the ML model for determining inference(s); the data used to train an ML model and the data used to determine inferences may overlap, however, “training data” and “inference data” refer to different concepts.

The terms “instantiate,” “instantiation,” and the like as used herein refers to the creation of an instance. An “instance” also refers to a concrete occurrence of an object, which may occur, for example, during execution of program code. The term “information element” refers to a structural element containing one or more fields. The term “field” refers to individual contents of an information element, or a data element that contains content. As used herein, a “database object”, “data structure”, or the like may refer to any representation of information that is in the form of an object, attribute-value pair (AVP), key-value pair (KVP), tuple, etc., and may include variables, data structures, functions, methods, classes, database records, database fields, database entities, associations between data and/or database entities (also referred to as a “relation”), blocks and links between blocks in block chain implementations, and/or the like.

An “information object,” as used herein, refers to a collection of structured data and/or any representation of information, and may include, for example electronic documents (or “documents”), database objects, data structures, files, audio data, video data, raw data, archive files, application packages, and/or any other like representation of information. The terms “electronic document” or “document,” may refer to a data structure, computer file, or resource used to record data, and includes various file types and/or data formats such as word processing documents, spreadsheets, slide presentations, multimedia items, webpage and/or source code documents, and/or the like. As examples, the information objects may include markup and/or source code documents such as HTML, XML, JSON, Apex®, CSS, JSP, MessagePack™, Apache® Thrift™, ASN.l, Google® Protocol Buffers (protobuf), or some other document(s)/format(s) such as those discussed herein. An information object may have both a logical and a physical structure. Physically, an information object comprises one or more units called entities. An entity is a unit of storage that contains content and is identified by a name. An entity may refer to other entities to cause their inclusion in the information object. An information object begins in a document entity, which is also referred to as a root element (or “root”). Logically, an information object comprises one or more declarations, elements, comments, character references, and processing instructions, all of which are indicated in the information object (e.g., using markup).

The term “data item” as used herein refers to an atomic state of a particular object with at least one specific property at a certain point in time. Such an object is usually identified by an object name or object identifier, and properties of such an object are usually defined as database objects (e.g., fields, records, etc.), object instances, or data elements (e.g., mark-up language elements/tags, etc.). Additionally or alternatively, the term “data item” as used herein may refer to data elements and/or content items, although these terms may refer to difference concepts. The term “data element” or “element” as used herein refers to a unit that is indivisible at a given level of abstraction and has a clearly defined boundary. A data element is a logical component of an information object (e.g., electronic document) that may begin with a start tag (e.g., “<element>“) and end with a matching end tag (e.g., “</element>“), or only has an empty element tag (e.g., “<element />“). Any characters between the start tag and end tag, if any, are the element’s content (referred to herein as “content items” or the like).

The content of an entity may include one or more content items, each of which has an associated datatype representation. A content item may include, for example, attribute values, character values, URls, qualified names (qnames), parameters, and the like. A qname is a fully qualified name of an element, attribute, or identifier in an information object. A qname associates a URI of a namespace with a local name of an element, attribute, or identifier in that namespace. To make this association, the qname assigns a prefix to the local name that corresponds to its namespace. The qname comprises a URI of the namespace, the prefix, and the local name. Namespaces are used to provide uniquely named elements and attributes in information objects. Content items may include text content (e.g., “<element>content item</element>“), attributes (e.g., “<element attribute=“attributeValue”>“), and other elements referred to as “child elements” (e.g., “<elementlxelement2>content item</element2x/elementl>“). An “attribute” may refer to a markup construct including a name-value pair that exists within a start tag or empty element tag. Attributes contain data related to its element and/or control the element’ s behavior.

The term “resource” as used herein refers to a physical or virtual device, a physical or virtual component within a computing environment, and/or a physical or virtual component within a particular device, such as computer devices, mechanical devices, memory space, processor/CPU time, processor/CPU usage, processor and accelerator loads, hardware time or usage, electrical power, input/output operations, ports or network sockets, channel/link allocation, throughput, memory usage, storage, network, database and applications, workload units, and/or the like. A “hardware resource” may refer to compute, storage, and/or network resources provided by physical hardware element(s). A “virtualized resource” may refer to compute, storage, and/or network resources provided by virtualization infrastructure to an application, device, system, etc. The term “network resource” or “communication resource” may refer to resources that are accessible by computer devices/systems via a communications network. The term “system resources” may refer to any kind of shared entities to provide services, and may include computing and/or network resources. System resources may be considered as a set of coherent functions, network data objects or services, accessible through a server where such system resources reside on a single host or multiple hosts and are clearly identifiable.The term “channel” as used herein refers to any transmission medium, either tangible or intangible, which is used to communicate data or a data stream. The term “channel” may be synonymous with and/or equivalent to “communications channel,” “data communications channel,” “transmission channel,” “data transmission channel,” “access channel,” “data access channel,” “link,” “data link,” “carrier,” “radiofrequency carrier,” and/or any other like term denoting a pathway or medium through which data is communicated. Additionally, the term “link” as used herein refers to a connection between two devices through a RAT for the purpose of transmitting and receiving information. As used herein, the term “radio technology” refers to technology for wireless transmission and/or reception of electromagnetic radiation for information transfer. The term “radio access technology” or “RAT” refers to the technology used for the underlying physical connection to a radio based communication network. As used herein, the term “communication protocol” (either wired or wireless) refers to a set of standardized rules or instructions implemented by a communication device and/or system to communicate with other devices and/or systems, including instructions for packetizing/depacketizing data, modulating/demodulating signals, implementation of protocols stacks, and/or the like.

As used herein, the term “radio technology” refers to technology for wireless transmission and/or reception of electromagnetic radiation for information transfer. The term “radio access technology” or “RAT” refers to the technology used for the underlying physical connection to a radio based communication network. As used herein, the term “communication protocol” (either wired or wireless) refers to a set of standardized rules or instructions implemented by a communication device and/or system to communicate with other devices and/or systems, including instructions for packetizing/depacketizing data, modulating/demodulating signals, implementation of protocols stacks, and/or the like. Examples of wireless communications protocols may be used in various embodiments include a Global System for Mobile Communications (GSM) radio communication technology, a General Packet Radio Service (GPRS) radio communication technology, an Enhanced Data Rates for GSM Evolution (EDGE) radio communication technology, and/or a Third Generation Partnership Project (3GPP) radio communication technology including, for example, 3GPP Fifth Generation (5G) or New Radio (NR), Universal Mobile Telecommunications System (UMTS), Freedom of Multimedia Access (FOMA), Long Term Evolution (LTE), LTE- Advanced (LTE Advanced), LTE Extra, LTE-A Pro, cdmaOne (2G), Code Division Multiple Access 2000 (CDMA 2000), Cellular Digital Packet Data (CDPD), Mobitex, Circuit Switched Data (CSD), High-Speed CSD (HSCSD), Universal Mobile Telecommunications System (UMTS), Wideband Code Division Multiple Access (W-CDM), High Speed Packet Access (HSPA), HSPA Plus (HSPA+), Time Division-Code Division Multiple Access (TD-CDMA), Time Division-Synchronous Code Division Multiple Access (TD-SCDMA), LTE LAA, MuLTEfire, UMTS Terrestrial Radio Access (UTRA), Evolved UTRA (E-UTRA), Evolution- Data Optimized or Evolution-Data Only (EV-DO), Advanced Mobile Phone System (AMPS), Digital AMPS (D-AMPS), Total Access Communication System/Extended Total Access Communication System (TACS/ETACS), Push-to-talk (PTT), Mobile Telephone System (MTS), Improved Mobile Telephone System (1MTS), Advanced Mobile Telephone System (AMTS), Cellular Digital Packet Data (CDPD), DataTAC, Integrated Digital Enhanced Network (iDEN), Personal Digital Cellular (PDC), Personal Handy-phone System (PHS), Wideband Integrated Digital Enhanced Network (WiDEN), iBurst, Unlicensed Mobile Access (UMA), also referred to as also referred to as 3GPP Generic Access Network, or GAN standard), Bluetooth®, Bluetooth Low Energy (BLE), IEEE 802.15.4 based protocols (e.g., IPv6 over Low power Wireless Personal Area Networks (6L0WPAN), WirelessHART, MiWi, Thread, 802.11a, etc.) WiFi-direct, ANT/ANT+, ZigBee, Z-Wave, 3GPP device-to-device (D2D) or Proximity Services (ProSe), Universal Plug and Play (UPnP), Low-Power Wide- Area-Network (LPWAN), Long Range Wide Area Network (LoRA) or LoRaWAN™ developed by Semtech and the LoRa Alliance, Sigfox, Wireless Gigabit Alliance (WiGig) standard, Worldwide Interoperability for Microwave Access (WiMAX), mmWave standards in general (e.g., wireless systems operating at 10-300 GHz and above such as WiGig, IEEE 802. Had, IEEE 802. Hay, etc.), V2X communication technologies (including 3GPP C-V2X), Dedicated Short Range Communications (DSRC) communication systems such as Intelligent- Transport-Systems (ITS) including the European ITS-G5, ITS-G5B, ITS-G5C, etc. In addition to the standards listed above, any number of satellite uplink technologies may be used for purposes of the present disclosure including, for example, radios compliant with standards issued by the International Telecommunication Union (ITU), or the European Telecommunications Standards Institute (ETSI), among others. The examples provided herein are thus understood as being applicable to various other communication technologies, both existing and not yet formulated.

The term “access network” refers to any network, using any combination of radio technologies, RATs, and/or communication protocols, used to connect user devices and service providers. In the context of WLANs, an “access network” is an IEEE 802 local area network (LAN) or metropolitan area network (MAN) between terminals and access routers connecting to provider services. The term “access router” refers to router that terminates a medium access control (MAC) service from terminals and forwards user traffic to information servers according to Internet Protocol (IP) addresses.

The term “SMTC” refers to an SSB-based measurement timing configuration configured by SSB-MeasurementTimingConfiguration. The term “SSB” refers to a synchronization signal/Physical Broadcast Channel (SS/PBCH) block, which includes a Primary Syncrhonization Signal (PSS), a Secondary Syncrhonization Signal (SSS), and a PBCH. The term “a “Primary Cell” refers to the MCG cell, operating on the primary frequency, in which the UE either performs the initial connection establishment procedure or initiates the connection re-establishment procedure. The term “Primary SCG Cell” refers to the SCG cell in which the UE performs random access when performing the Reconfiguration with Sync procedure for DC operation. The term “Secondary Cell” refers to a cell providing additional radio resources on top of a Special Cell for a UE configured with CA. The term “Secondary Cell Group” refers to the subset of serving cells comprising the PSCell and zero or more secondary cells for a UE configured with DC. The term “Serving Cell” refers to the primary cell for a UE in RRC_CONNECTED not configured with CA/DC there is only one serving cell comprising of the primary cell. The term “serving cell” or “serving cells” refers to the set of cells comprising the Special Cell(s) and all secondary cells for a UE in RRC_CONNECTED configured with CA. The term “Special Cell” refers to the PCell of the MCG or the PSCell of the SCG for DC operation; otherwise, the term “Special Cell” refers to the Pcell.

The term “Al policy” refers to a type of declarative policies expressed using formal statements that enable the non-RT RIC function in the SMO to guide the near-RT RIC function, and hence the RAN, towards better fulfilment of the RAN intent.

The term “Al Enrichment information” refers to information utilized by near-RT RIC that is collected or derived at SMO/non-RT RIC either from non-network data sources or from network functions themselves.

The term “Al-Policy Based Traffic Steering Process Mode” refers to an operational mode in which the Near-RT RIC is configured through Al Policy to use Traffic Steering Actions to ensure a more specific notion of network performance (for example, applying to smaller groups of E2 Nodes and UEs in the RAN) than that which it ensures in the Background Traffic Steering.

The term “Background Traffic Steering Processing Mode” refers to an operational mode in which the Near-RT RIC is configured through 01 to use Traffic Steering Actions to ensure a general background network performance which applies broadly across E2 Nodes and UEs in the RAN. The term “Baseline RAN Behavior” refers to the default RAN behavior as configured at the E2 Nodes by SMO

The term “E2” refers to an interface connecting the Near-RT RIC and one or more O- CU-CPs, one or more O-CU-UPs, one or more O-DUs, and one or more O-eNBs.

The term “E2 Node” refers to a logical node terminating E2 interface. In this version of the specification, ORAN nodes terminating E2 interface are: for NR access: O-CU-CP, O- CU-UP, O-DU or any combination; and for E-UTRA access: O-eNB.

The term “Intents”, in the context of O-RAN systems/implementations, refers to declarative policy to steer or guide the behavior of RAN functions, allowing the RAN function to calculate the optimal result to achieve stated objective.

The term “O-RAN non-real-time RAN Intelligent Controller” or “non-RT RIC” refers to a logical function that enables non-real-time control and optimization of RAN elements and resources, AI/ML workflow including model training and updates, and policy-based guidance of applications/features in Near-RT RIC.

The term “Near-RT RIC” or “O-RAN near-real-time RAN Intelligent Controller” refers to a logical function that enables near-real-time control and optimization of RAN elements and resources via fine-grained (e.g., UE basis, Cell basis) data collection and actions over E2 interface.

The term “O-RAN Central Unit” or “O-CU” refers to a logical node hosting RRC, SDAP and PDCP protocols.

The term “O-RAN Central Unit - Control Plane” or “O-CU-CP” refers to a logical node hosting the RRC and the control plane part of the PDCP protocol.

The term “O-RAN Central Unit - User Plane” or “O-CU-UP” refers to a logical node hosting the user plane part of the PDCP protocol and the SDAP protocol

The term “O-RAN Distributed Unit” or “O-DU” refers to a logical node hosting RLC/MAC/High-PHY layers based on a lower layer functional split.

The term “O-RAN eNB” or “O-eNB” refers to an eNB or ng-eNB that supports E2 interface.

The term “O-RAN Radio Unit” or “O-RU” refers to a logical node hosting Low-PHY layer and RF processing based on a lower layer functional split. This is similar to 3GPP’s “TRP” or “RRH” but more specific in including the Low-PHY layer (FFT/iFFT, PRACH extraction).

The term “01” refers to an interface between orchestration & management entities (Orchestration/NMS) and O-RAN managed elements, for operation and management, by which FCAPS management, Software management, File management and other similar functions shall be achieved.

The term “RAN UE Group” refers to an aggregations of UEs whose grouping is set in the E2 nodes through E2 procedures also based on the scope of Al policies. These groups can then be the target of E2 CONTROL or POLICY messages.

The term “Traffic Steering Action” refers to the use of a mechanism to alter RAN behavior. Such actions include E2 procedures such as CONTROL and POLICY.

The term “Traffic Steering Inner Loop” refers to the part of the Traffic Steering processing, triggered by the arrival of periodic TS related KPM (Key Performance Measurement) from E2 Node, which includes UE grouping, setting additional data collection from the RAN, as well as selection and execution of one or more optimization actions to enforce Traffic Steering policies.

The term “Traffic Steering Outer Loop” refers to the part of the Traffic Steering processing, triggered by the near-RT RIC setting up or updating Traffic Steering aware resource optimization procedure based on information from Al Policy setup or update, Al Enrichment Information (El) and/or outcome of Near-RT RIC evaluation, which includes the initial configuration (preconditions) and injection of related Al policies, Triggering conditions for TS changes.

The term “Traffic Steering Processing Mode” refers to an operational mode in which either the RAN or the Near-RT RIC is configured to ensure a particular network performance. This performance includes such aspects as cell load and throughput, and can apply differently to different E2 nodes and UEs. Throughout this process, Traffic Steering Actions are used to fulfill the requirements of this configuration.

The term “Traffic Steering Target” refers to the intended performance result that is desired from the network, which is configured to Near-RT RIC over 01.

Furthermore, any of the disclosed embodiments and example implementations can be embodied in the form of various types of hardware, software, firmware, middleware, or combinations thereof, including in the form of control logic, and using such hardware or software in a modular or integrated manner. Additionally, any of the software components or functions described herein can be implemented as software, program code, script, instructions, etc., operable to be executed by processor circuitry. These components, functions, programs, etc., can be developed using any suitable computer language such as, for example, Python, PyTorch, NumPy, Ruby, Ruby on Rails, Scala, Smalltalk, Java™, C++, C#, “C”, Kotlin, Swift, Rust, Go (or “Golang”), EMCAScript, JavaScript, TypeScript, Jscript, ActionScript, Server- Side JavaScript (SSJS), PHP, Pearl, Lua, Torch/Lua with Just-In Time compiler (LuaJIT), Accelerated Mobile Pages Script (AMPscript), VBScript, JavaServer Pages (JSP), Active Server Pages (ASP), Node.js, ASP.NET, JAMscript, Hypertext Markup Language (HTML), extensible HTML (XHTML), Extensible Markup Language (XML), XML User Interface Language (XUL), Scalable Vector Graphics (SVG), RESTful API Modeling Language (RAML), wiki markup or Wikitext, Wireless Markup Language (WML), Java Script Object Notion (JSON), Apache® MessagePack™, Cascading Stylesheets (CSS), extensible stylesheet language (XSL), Mustache template language, Handlebars template language, Guide Template Language (GTL), Apache® Thrift, Abstract Syntax Notation One (ASN.l), Google® Protocol Buffers (protobuf), Bitcoin Script, EVM® bytecode, Solidity™, Vyper (Python derived), Bamboo, Lisp Like Language (LLL), Simplicity provided by Blockstream™, Rholang, Michelson, Counterfactual, Plasma, Plutus, Sophia, Salesforce® Apex®, and/or any other programming language or development tools including proprietary programming languages and/or development tools. The software code can be stored as a computer- or processorexecutable instructions or commands on a physical non-transitory computer-readable medium. Examples of suitable media include RAM, ROM, magnetic media such as a hard-drive or a floppy disk, or an optical medium such as a compact disk (CD) or DVD (digital versatile disk), flash memory, and the like, or any combination of such storage or transmission devices.

ABBREVIATIONS

Unless used differently herein, terms, definitions, and abbreviations may be consistent with terms, definitions, and abbreviations defined in 3GPP TR 21.905 vl6.0.0 (2019-06). For the purposes of the present document, the following abbreviations may apply to the examples and embodiments discussed herein.

Table XIX Abbreviations:

The foregoing description provides illustration and description of various example embodiments, but is not intended to be exhaustive or to limit the scope of embodiments to the precise forms disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments. Where specific details are set forth in order to describe example embodiments of the disclosure, it should be apparent to one skilled in the art that the disclosure can be practiced without, or with variation of, these specific details. It should be understood, however, that there is no intent to limit the concepts of the present disclosure to the particular forms disclosed, but on the contrary, the intention is to cover all modifications, equivalents, and alternatives consistent with the present disclosure and the appended claims.

Claims

CLAIMS What is claimed is:

1. An apparatus for user equipment (UE) comprising: processing circuitry configured to: receive an indication for PRACH resources for subband non-overlapping full duplex (SBFD) operation in downlink control information with a Cyclic Redundancy Check (CRC); determine a physical random access channel (PRACH) occasion based on the indication for PRACH resources for SBFD operation; and transmit a PRACH preamble on the determined PRACH occasion; and a memory to store the SBFD indication.

2. The apparatus of claim 1 , wherein the processing circuitry is further configured to scramble the CRC by a Cell - Radio Network Temporary Identifier (C-RNTI) for a physical downlink control channel (PDCCH) order random access (RACH) procedure.

3. The apparatus of claim 1, wherein the indication for PRACH resources for SBFD operationcomprises a 1-bit indicator, where bit “0” indicates PRACH occasions within non- SBFD symbols, and bit “1” indicates PRACH occasions within SBFD symbols.

4. The apparatus of claim 1, wherein a separate PRACH configuration is provided for SBFD aware user equipment.

5. The apparatus of claim 4, wherein the separate PRACH configuration in non-SBFD symbols is invalid when overlapping with a PRACH occasion configured for legacy UEs.

6. The apparatus of claim 1, wherein the downlink control information is in format l_0 and includes a field to indicate whether the PRACH occasions are within SBFD or non- SBFD symbols.

7. The apparatus of claim 1, wherein the processing circuitry is further configured to process both SBFD and non-SBFD symbols.

8. The apparatus of claim 1, wherein the processing circuitry is further configured to determine the indication for PRACH resources for SBFD operationto identify whether the PRACH occasion falls within SBFD or non-SBFD symbols.

9. The apparatus of any one of claims 1-8, wherein the processing circuitry is further configured to select an appropriate PRACH occasion based on the determined indication for PRACH resources for SBFD operation.

10. A computer-readable medium storing computer-executable instructions which when executed by one or more processors result in performing operations comprising: receiving an indication for PRACH resources for subband non-overlapping full duplex (SBFD) operationin downlink control information with a Cyclic Redundancy Check (CRC); determining a physical random access channel (PRACH) occasion based on the indication for PRACH resources for SBFD operation; and transmitting a PRACH preamble on the determined PRACH occasion.

11. The computer-readable medium of claim 10, wherein the operations further comprise scrambling the CRC by a Cell - Radio Network Temporary Identifier (C-RNTI) for a physical downlink control channel (PDCCH) order random access (RACH) procedure.

12. The computer-readable medium of claim 10, wherein the indication for PRACH resources for SBFD operationcomprises a 1 -bit indicator, where bit “0” indicates PRACH occasions within non-SBFD symbols, and bit “1” indicates PRACH occasions within SBFD symbols.

13. The computer-readable medium of claim 10, wherein a separate PRACH configuration is provided for SBFD aware user equipment.

14. The computer-readable medium of claim 13, wherein the separate PRACH configuration in non-SBFD symbols is invalid when overlapping with a PRACH occasion configured for legacy UEs.

15. The computer-readable medium of claim 10, wherein the downlink control information is in format l_0 and includes a field to indicate whether the PRACH occasions are within SBFD or non-SBFD symbols.

16. The computer-readable medium of claim 10, wherein the operations further comprise processing both SBFD and non-SBFD symbols.

17. The computer-readable medium of claim 10, wherein the operations further comprise determining the indication for PRACH resources for SBFD operationto identify whether the PRACH occasion falls within SBFD or non-SBFD symbols.

18. The computer-readable medium of any one of claims 10-17, wherein the operations further comprise selecting an appropriate PRACH occasion based on the determined indication for PRACH resources for SBFD operation.

19. A method comprising: receiving an indication for PRACH resources for subband non-overlapping full duplex (SBFD) operation in downlink control information with a Cyclic Redundancy Check (CRC); determining a physical random access channel (PRACH) occasion based on the indication for PRACH resources for SBFD operation; and transmitting a PRACH preamble on the determined PRACH occasion.

20. The method of claim 19, further comprising scrambling the CRC by a Cell - Radio Network Temporary Identifier (C-RNTI) for a physical downlink control channel (PDCCH) order random access (RACH) procedure.