DEPLOYMENT OF A PRIVATE NETWORK USING INTEGRATION WITH A TRUSTED BACKUP NETWORK

Methods, systems, and devices for wireless communications are described. In some systems, a first network type may be integrated with a second network type during deployment of the second network type. The first network type may support communications of a first radio access technology (RAT) via unlicensed radio frequency (RF) bands and the second network type may support communications of a second RAT via unlicensed RF bands, licensed RF bands, or both. A gateway function of the first network type may establish an interface with a network intelligent controller of the second network type. The gateway function may receive a request to connect with a wireless device based on a failed connection between the device and the second network type. The gateway function may indicate the connection with the wireless device to the network intelligent controller. The network intelligent controller may perform a communication management operation based on the indication.

FIELD OF TECHNOLOGY

The following relates to wireless communications, including deployment of a private network using integration with a trusted backup network.

BACKGROUND

Some wireless communications systems may support a private network, which may be a non-public mobile network that may use licensed, unlicensed, or shared radio frequency (RF) spectrum bands. The private network may be intended for private (e.g., non-public use) by a customer or organization.

SUMMARY

The described techniques relate to improved methods, systems, devices, and apparatuses that support deployment of a private network using integration with a trusted backup network. For example, the described techniques provide for integration of a first network type with a second network type to facilitate deployment of the second network type. The first network type may support communications of a first radio access technology (RAT) via unlicensed radio frequency (RF) bands (e.g., a Wi-Fi network, or some other type of network). The second network type may support communications of a second RAT via unlicensed RF bands, licensed RF bands, or both (e.g., a 3rd Generation Partnership Project (3GPP) network, or some other type of network). A gateway function of the first network type may establish a first interface with a first network intelligent controller of the second network type. The gateway function may establish a second interface with a second network intelligent controller of the second network type. The first and second interfaces may be referred to as E2tr and O2t interfaces, respectively, in some examples.

The gateway function may receive a request to connect with a wireless device (e.g., a user equipment (UE)) based on a failed connection between the device and the second network type. The gateway function may establish a connection with the wireless device and indicate the connection with the wireless device to the first network intelligent controller. The first network intelligent controller may perform a communication management operation based on the indication. The gateway function of the first network type may continue to monitor one or more key performance indicators (KPIs) associated with a connection between the wireless device and the second network type. The gateway function may forward the KPIs to the second network intelligent controller periodically via the second interface. The second network intelligent controller may perform a communication management operation for one or more network entities of the second network type based on the KPIs. The communication management operations may adjust one or more parameters associated with the second network type to improve a subsequent connection attempt with the wireless device. The wireless device may subsequently re-connect to the second network type.

A method for wireless communication at a gateway function of a first network type is described. The method may include receiving a first message including a first request to establish, as part of a network integration, an interface between the gateway function of the first network type and a network intelligent controller of a second network type, where the first network type supports communications of a first RAT via unlicensed RF spectrum bands and the second network type supports communications of a second RAT via unlicensed RF spectrum bands, licensed RF spectrum bands, or both, the second RAT different than the first RAT, receiving, based on the network integration and a failed connection between a wireless device and the second network type, a second message including a second request to establish a connection with the wireless device in accordance with the first RAT, the failed connection associated with the second RAT, and transmitting, to the network intelligent controller of the second network type via the interface, a third message indicating that the connection between the gateway function of the first network type and the wireless device is established.

An apparatus for wireless communication at a gateway function of a first network type is described. The apparatus may include at least one processor, at least one memory coupled with the at least one processor, and instructions stored in the at least one memory. The instructions may be executable by the at least one processor to cause the apparatus to receive a first message including a first request to establish, as part of a network integration, an interface between the gateway function of the first network type and a network intelligent controller of a second network type, where the first network type supports communications of a first RAT via unlicensed RF spectrum bands and the second network type supports communications of a second RAT via unlicensed RF spectrum bands, licensed RF spectrum bands, or both, the second RAT different than the first RAT, receive, based on the network integration and a failed connection between a wireless device and the second network type, a second message including a second request to establish a connection with the wireless device in accordance with the first RAT, the failed connection associated with the second RAT, and transmit, to the network intelligent controller of the second network type via the interface, a third message indicating that the connection between the gateway function of the first network type and the wireless device is established.

Another apparatus for wireless communication at a gateway function of a first network type is described. The apparatus may include means for receiving a first message including a first request to establish, as part of a network integration, an interface between the gateway function of the first network type and a network intelligent controller of a second network type, where the first network type supports communications of a first RAT via unlicensed RF spectrum bands and the second network type supports communications of a second RAT via unlicensed RF spectrum bands, licensed RF spectrum bands, or both, the second RAT different than the first RAT, means for receiving, based on the network integration and a failed connection between a wireless device and the second network type, a second message including a second request to establish a connection with the wireless device in accordance with the first RAT, the failed connection associated with the second RAT, and means for transmitting, to the network intelligent controller of the second network type via the interface, a third message indicating that the connection between the gateway function of the first network type and the wireless device is established.

A non-transitory computer-readable medium storing code for wireless communication at a gateway function of a first network type is described. The code may include instructions executable by a processor to receive a first message including a first request to establish, as part of a network integration, an interface between the gateway function of the first network type and a network intelligent controller of a second network type, where the first network type supports communications of a first RAT via unlicensed RF spectrum bands and the second network type supports communications of a second RAT via unlicensed RF spectrum bands, licensed RF spectrum bands, or both, the second RAT different than the first RAT, receive, based on the network integration and a failed connection between a wireless device and the second network type, a second message including a second request to establish a connection with the wireless device in accordance with the first RAT, the failed connection associated with the second RAT, and transmit, to the network intelligent controller of the second network type via the interface, a third message indicating that the connection between the gateway function of the first network type and the wireless device is established.

In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, receiving the second message may include operations, features, means, or instructions for receiving an indication of a globally unique temporary identifier (GUTI), an international mobile subscriber identity (IMSI), a subscription permanent identifier (SUPI), public land mobile network identifier (PLMN), network slice assistance information (NSAI), or any combination thereof associated with the wireless device.

In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, receiving the second message may include operations, features, means, or instructions for receiving an early access protocol message that indicates an identifier (ID) of the wireless device and indicates the second request to establish the connection with the wireless device.

Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting, via the third message based on establishing the connection with the wireless device, an ID of the wireless device and an ID of an access point (AP) associated with the first network type.

Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for establishing a second interface between the gateway function of the first network type and a second network intelligent controller of the second network type.

Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for monitoring a registration between the wireless device and the second network type and transmitting, via the second interface, a fourth message that indicates the registration between the wireless device and the second network type may be successful, where the fourth message includes an ID of the wireless device and an ID of an AP associated with the first network type.

Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for measuring one or more KPIs associated with a second connection between the wireless device and the second network type and transmitting, via the second interface and in accordance with a periodicity, an indication of the one or more KPIs.

Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving, via the second interface, an indication that values of the one or more KPIs exceed a threshold, where the indication includes a trigger to disable the connection between the wireless device and the gateway function, disabling the connection between the wireless device and the gateway function based on the indication, and disabling the interface and the second interface based on the indication.

Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving a resource release request based on a quality of a second connection between the wireless device and the second network type exceeding a threshold quality, disabling the connection between the gateway function of the first network type and the wireless device based on the resource release request, and transmitting, based on disabling the connection, an acknowledgment message responsive to the resource release request.

Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for monitoring a registration between the wireless device and the second network type and transmitting, via the interface, a fourth message indicating that the registration between the wireless device and the second network type failed, where the fourth message includes an ID of the wireless device and an ID of an AP associated with the first network type.

In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, the first network type includes a trusted non-third generation partnership project (3GPP) network and the second network type includes a 3GPP network.

A method for wireless communication at a network intelligent controller of a second network type is described. The method may include transmitting a first message including a request to establish, as part of a network integration, an interface between the network intelligent controller of the second network type and a gateway function of a first network type, where the first network type supports communications of a first RAT via unlicensed RF spectrum bands and the second network type supports communications of a second RAT via unlicensed RF spectrum bands, licensed RF spectrum bands, or both, the second RAT different than the first RAT, receiving, via the interface, a second message indicating that a connection between the gateway function of the first network type and a wireless device is established in accordance with the first RAT, the connection between the gateway function and the wireless device established based on a failed connection between the wireless device and the second network type, the failed connection associated with the second RAT, and performing a communication management operation for one or more radio access network (RAN) components of the second network type based on the second message.

An apparatus for wireless communication at a network intelligent controller of a second network type is described. The apparatus may include at least one processor, at least one memory coupled with the at least one processor, and instructions stored in the at least one memory. The instructions may be executable by the at least one processor to cause the apparatus to transmit a first message including a request to establish, as part of a network integration, an interface between the network intelligent controller of the second network type and a gateway function of a first network type, where the first network type supports communications of a first RAT via unlicensed RF spectrum bands and the second network type supports communications of a second RAT via unlicensed RF spectrum bands, licensed RF spectrum bands, or both, the second RAT different than the first RAT, receive, via the interface, a second message indicating that a connection between the gateway function of the first network type and a wireless device is established in accordance with the first RAT, the connection between the gateway function and the wireless device established based on a failed connection between the wireless device and the second network type, the failed connection associated with the second RAT, and perform a communication management operation for one or more RAN components of the second network type based on the second message.

Another apparatus for wireless communication at a network intelligent controller of a second network type is described. The apparatus may include means for transmitting a first message including a request to establish, as part of a network integration, an interface between the network intelligent controller of the second network type and a gateway function of a first network type, where the first network type supports communications of a first RAT via unlicensed RF spectrum bands and the second network type supports communications of a second RAT via unlicensed RF spectrum bands, licensed RF spectrum bands, or both, the second RAT different than the first RAT, means for receiving, via the interface, a second message indicating that a connection between the gateway function of the first network type and a wireless device is established in accordance with the first RAT, the connection between the gateway function and the wireless device established based on a failed connection between the wireless device and the second network type, the failed connection associated with the second RAT, and means for performing a communication management operation for one or more RAN components of the second network type based on the second message.

A non-transitory computer-readable medium storing code for wireless communication at a network intelligent controller of a second network type is described. The code may include instructions executable by a processor to transmit a first message including a request to establish, as part of a network integration, an interface between the network intelligent controller of the second network type and a gateway function of a first network type, where the first network type supports communications of a first RAT via unlicensed RF spectrum bands and the second network type supports communications of a second RAT via unlicensed RF spectrum bands, licensed RF spectrum bands, or both, the second RAT different than the first RAT, receive, via the interface, a second message indicating that a connection between the gateway function of the first network type and a wireless device is established in accordance with the first RAT, the connection between the gateway function and the wireless device established based on a failed connection between the wireless device and the second network type, the failed connection associated with the second RAT, and perform a communication management operation for one or more RAN components of the second network type based on the second message.

Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving, via the interface, a third message indicating that a registration between the wireless device and the second network type failed, where the third message includes an ID of the wireless device and an ID of an AP associated with the first network type.

Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for performing a second communication management operation for the one or more RAN components of the second network type based on the third message.

Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting, to one or more network entities of the second network type based on the second message, a control request that indicates the connection between the gateway function and the wireless device may be established, where the control request indicates one or more network optimization parameters associated with the communication management operation.

Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for establishing, before receiving the second message, a first connection with the wireless device via the second network type in accordance with the second RAT, where the connection between the gateway function and the wireless device may be based on a failure of the first connection.

In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, performing the communication management operation may include operations, features, means, or instructions for modifying an allocation of one or more radio resources within the second network type, modifying one or more parameters associated with radio access control for the second network type, modifying one or more parameters associated with a connection management for the second network type, or modifying one or more parameters associated with a mobility management for the second network type.

In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, the first network type includes a trusted non-3GPP network and the second network type includes a 3GPP network.

In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, the network intelligent controller includes a near-real-time intelligent controller of a network entity of the second network type.

A method for wireless communication at a network intelligent controller of a second network type is described. The method may include establishing, as part of a network integration, an interface between the network intelligent controller and a gateway function of a first network type, where the first network type supports communications of a first RAT via unlicensed RF spectrum bands and the second network type supports communications of a second RAT via unlicensed RF spectrum bands, licensed RF spectrum bands, or both, the second RAT different than the first RAT, receiving, periodically via the interface, an indication of one or more KPIs associated with a connection between a wireless device and the second network type, and performing, based on the one or more KPIs, a communication management operation for one or more network entities of the second network type.

An apparatus for wireless communication at a network intelligent controller of a second network type is described. The apparatus may include at least one processor, at least one memory coupled with the at least one processor, and instructions stored in the at least one memory. The instructions may be executable by the at least one processor to cause the apparatus to establish, as part of a network integration, an interface between the network intelligent controller and a gateway function of a first network type, where the first network type supports communications of a first RAT via unlicensed RF spectrum bands and the second network type supports communications of a second RAT via unlicensed RF spectrum bands, licensed RF spectrum bands, or both, the second RAT different than the first RAT, receive, periodically via the interface, an indication of one or more KPIs associated with a connection between a wireless device and the second network type, and perform, based on the one or more KPIs, a communication management operation for one or more network entities of the second network type.

Another apparatus for wireless communication at a network intelligent controller of a second network type is described. The apparatus may include means for establishing, as part of a network integration, an interface between the network intelligent controller and a gateway function of a first network type, where the first network type supports communications of a first RAT via unlicensed RF spectrum bands and the second network type supports communications of a second RAT via unlicensed RF spectrum bands, licensed RF spectrum bands, or both, the second RAT different than the first RAT, means for receiving, periodically via the interface, an indication of one or more KPIs associated with a connection between a wireless device and the second network type, and means for performing, based on the one or more KPIs, a communication management operation for one or more network entities of the second network type.

A non-transitory computer-readable medium storing code for wireless communication at a network intelligent controller of a second network type is described. The code may include instructions executable by a processor to establish, as part of a network integration, an interface between the network intelligent controller and a gateway function of a first network type, where the first network type supports communications of a first RAT via unlicensed RF spectrum bands and the second network type supports communications of a second RAT via unlicensed RF spectrum bands, licensed RF spectrum bands, or both, the second RAT different than the first RAT, receive, periodically via the interface, an indication of one or more KPIs associated with a connection between a wireless device and the second network type, and perform, based on the one or more KPIs, a communication management operation for one or more network entities of the second network type.

Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving, via the interface, a message that indicates a successful registration between the wireless device and the second network type, where the message includes an ID of the wireless device and an ID of an AP associated with the first network type, and where periodically receiving the indication of the one or more KPIs may be based on the successful registration.

Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting, via the interface, an indication that values of the one or more KPIs exceed a threshold, where the indication includes a trigger to disable a second connection between the wireless device and the gateway function of the first network type.

In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, performing the communication management operation may include operations, features, means, or instructions for modifying one or more corrective network orchestration and optimization decisions for the one or more network entities of the second network type based on the one or more KPIs.

In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, the first network type includes a trusted non-3GPP network and the second network type includes a 3GPP network.

In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, the network intelligent controller includes a non-real-time intelligent controller of a network entity of the second network type.

DETAILED DESCRIPTION

Some wireless communications systems may support a private network. A private network may be a non-public mobile network that may support use of a licensed, unlicensed, or shared spectrum and that is intended for private use by an organization or company. In some examples, a private network may operate in accordance with or be based on 3rd Generation Partnership Project (3GPP) protocols, or some other type of network protocols. The private network may be referred to as a second network or may be referred to as being associated with a second network type. In some cases, it may take a relatively long time (e.g., one to two days) to deploy a private network due to, for example, radio frequency (RF) site surveying, network dimensioning, and onboarding of wireless devices, such as user equipments (UEs), among other complexities involved in setting up the private network associated with the second network type. Such deployment time may be relatively long compared to other types of network deployments, including a first network type (e.g., a Wi-Fi network).

Techniques, systems, and devices described herein provide for integration of a trusted backup network of a first network type with the private network of the second network type to improve deployment of the private mobile network. In some examples, the first network type may be a non-3GPP network that uses unlicensed frequency bands, such as a Wi-Fi network, and the second network type may be a 3GPP network. During deployment of the private network, some network nodes of the first network type may be deployed and set up, which may be referred to as a greenfield deployment. Additionally, or alternatively, preexisting network nodes of the first network type may be leveraged to generate a trusted backup network, which may be referred to as a brownfield deployment.

As described herein, if a UE fails to connect to or onboard to the second network, the UE may be configured to establish a default or backup connection with the first network. The UE may transmit a registration request to a gateway function for the first (backup) network. The gateway function may forward an indication of the request from the UE and a connection established between the UE and the gateway function to the private network via an E2tr interface, which may be a new interface established between the gateway function and a first intelligent controller of the private network. The first intelligent controller may perform corrective action by adjusting one or more radio resource or mobility management parameters to improve the second network based on the indication. The gateway function may subsequently indicate, to a second intelligent controller of a service management and orchestration function (SMO) of the second network, one or more key performance indicators (KPIs) associated with a connection between the UE and the second network via the gateway function. The gateway function may indicate the KPIs to the second intelligent controller via a second new interface, referred to as an O1t interface. The UE may continue attempts to register with the second network iteratively until the private network is sufficiently optimized (e.g., meets or exceeds one or more metrics or performance target), at which point the connection between the UE and the private network may be established and the backup network may be disabled or deactivated. By integrating the backup network of the first network type with the second network, the second network may be deployed and may establish connections with client devices, such as the UE, more efficiently and reliably.

Aspects of the disclosure are initially described in the context of wireless communications systems. Additional aspects are described with reference to a network architecture, integrated network architectures, a greenfield deployment workflow, a brownfield deployment workflow, and process flows. Aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flowcharts that relate to deployment of a private network using integration with a trusted backup network.

In the case of the techniques described herein applied in the context of a disaggregated RAN architecture, one or more components of the disaggregated RAN architecture may be configured to support deployment of a private network using integration with a trusted backup network as described herein. For example, some operations described as being performed by a UE115or a network entity105(e.g., a base station140) may additionally, or alternatively, be performed by one or more components of the disaggregated RAN architecture (e.g., IAB nodes104, DUs165, CUs160, RUs170, RIC175, SMO180).

In some examples, the wireless communications system100may represent an example of a private network. A private network may be a non-public mobile network that may use a licensed, unlicensed, or shared RF spectrum and may be intended for non-public (e.g., private) use by, for example, an organization or company (e.g., for precision agriculture, construction and mining, digitized education, connected healthcare, connected cities, intelligent retail, smart manufacturing, and mobile experiences, among other examples). In some examples, the private network may leverage or be based on a second type of network protocols, such as 3GPP protocols, and may be referred to as a second type of network accordingly (e.g., a 3GPP network or a 5G network).

A time to deploy a private or enterprise network may be relatively long (e.g., one to two days, or some other deployment time) as compared with deployment times for other network types, such as a Wi-Fi network. The deployment of the private mobile network may include RF site surveying, network dimensioning, and onboarding of UEs115, among other deployment procedures. Reducing the deployment time for the private mobile network may be challenging as compared with other network types due to one or more characteristics and parameters associated with the private mobile network. These characteristics may include, for example, installation of a subscriber identity module (SIM) or an embedded SIM (E-SIM) on each UE115in the network, setup of multiple components on the access network and the core network that may comply with standards (e.g., O-RAN and/or 3GPP specific components), fine tuning coverage and power requirements of one or more components, such as an RU, one or more other characteristics, or any combination thereof. Use of a network design and/or network interfaces without sufficient testing may result in outages, deployment issues, interoperability issues, and degradation of quality of service, among other examples.

Techniques, systems, and devices described herein provide for improved deployment of a private mobile network by integrating the private mobile network with a trusted backup network. The trusted backup network may be of a first network type that is different than a second network type of the private mobile network. For example, the trusted backup network may be a non-3GPP network, such as a Wi-Fi network, or some other type of network. A network type may represent or correspond to a set of standards or protocols that are followed by the network. A backup network may be considered “trusted” if the network is in a same deployment as the primary network (e.g., a Non-Public Core). The described techniques may provide methods for using a trusted network as a backup network or standby access network at the start of a deployment process for a private mobile network.

The described techniques may be applied to multiple different types (e.g., classifications) of network deployment, including greenfield and brownfield deployments. A greenfield deployment may be a network deployment in a system in which there is no historic or previous wireless private network deployment. A brownfield deployment may be a network deployment that includes a replacement and/or addition to an existing wireless private network deployment. For example, a network of the first type (e.g., Wi-Fi-based private network) may be deployed, and a network of the second type may be deployed as an addition to or replacement of the network of the first type.

FIG.2shows an example of a network architecture200(e.g., a disaggregated base station architecture, a disaggregated RAN architecture) that supports deployment of a private network using integration with a trusted backup network in accordance with one or more aspects of the present disclosure. The network architecture200may illustrate an example for implementing one or more aspects of the wireless communications system100. The network architecture200may include one or more CUs160-athat may communicate directly with a core network130-avia a backhaul communication link120-a, or indirectly with the core network130-athrough one or more disaggregated network entities105(e.g., a near-RT RIC175-bvia an E2 link, or a non-RT RIC175-aassociated with an SMO180-a(e.g., an SMO Framework), or both). A CU160-amay communicate with one or more DUs165-avia respective midhaul communication links162-a(e.g., an F1 interface). The DUs165-amay communicate with one or more RUs170-avia respective fronthaul communication links168-a. The RUs170-amay be associated with respective coverage areas110-aand may communicate with UEs115-avia one or more communication links125-a. In some implementations, a UE115-amay be simultaneously served by multiple RUs170-a.

Each of the network entities105of the network architecture200(e.g., CUs160-a, DUs165-a, RUs170-a, non-RT RICs175-a, near-RT RICs175-b, SMOs180-a, Open Clouds (O-Clouds)205, Open eNBs (O-eNBs)210) may include one or more interfaces or may be coupled with one or more interfaces configured to receive or transmit signals (e.g., data, information) via a wired or wireless transmission medium. Each network entity105, or an associated processor (e.g., controller) providing instructions to an interface of the network entity105, may be configured to communicate with one or more of the other network entities105via the transmission medium. For example, the network entities105may include a wired interface configured to receive or transmit signals over a wired transmission medium to one or more of the other network entities105. Additionally, or alternatively, the network entities105may include a wireless interface, which may include a receiver, a transmitter, or transceiver (e.g., an RF transceiver) configured to receive or transmit signals, or both, over a wireless transmission medium to one or more of the other network entities105.

In some examples, a CU160-amay host one or more higher layer control functions. Such control functions may include RRC, PDCP, SDAP, or the like. Each control function may be implemented with an interface configured to communicate signals with other control functions hosted by the CU160-a. A CU160-amay be configured to handle user plane functionality (e.g., CU-UP), control plane functionality (e.g., CU-CP), or a combination thereof. In some examples, a CU160-amay be logically split into one or more CU-UP units and one or more CU-CP units. A CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface, such as an E1 interface when implemented in an O-RAN configuration. A CU160-amay be implemented to communicate with a DU165-a, as necessary, for network control and signaling.

A DU165-amay correspond to a logical unit that includes one or more functions (e.g., base station functions, RAN functions) to control the operation of one or more RUs170-a. In some examples, a DU165-amay host, at least partially, one or more of an RLC layer, a MAC layer, and one or more aspects of a PHY layer (e.g., a high PHY layer, such as modules for FEC encoding and decoding, scrambling, modulation and demodulation, or the like) depending, at least in part, on a functional split, such as those defined by the 3GPP. In some examples, a DU165-amay further host one or more low PHY layers. Each layer may be implemented with an interface configured to communicate signals with other layers hosted by the DU165-a, or with control functions hosted by a CU160-a.

In some examples, lower-layer functionality may be implemented by one or more RUs170-a. For example, an RU170-a, controlled by a DU165-a, may correspond to a logical node that hosts RF processing functions, or low-PHY layer functions (e.g., performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, or the like), or both, based at least in part on the functional split, such as a lower-layer functional split. In such an architecture, an RU170-amay be implemented to handle over the air (OTA) communication with one or more UEs115-a. In some implementations, real-time and non-real-time aspects of control and user plane communication with the RU(s)170-amay be controlled by the corresponding DU165-a. In some examples, such a configuration may enable a DU165-aand a CU160-ato be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

The SMO180-amay be configured to support RAN deployment and provisioning of non-virtualized and virtualized network entities105. For non-virtualized network entities105, the SMO180-amay be configured to support the deployment of dedicated physical resources for RAN coverage requirements which may be managed via an operations and maintenance interface (e.g., an O1 interface). For virtualized network entities105, the SMO180-amay be configured to interact with a cloud computing platform (e.g., an O-Cloud205) to perform network entity life cycle management (e.g., to instantiate virtualized network entities105) via a cloud computing platform interface (e.g., an O2 interface). Such virtualized network entities105can include, but are not limited to, CUs160-a. DUs165-a. RUs170-a, and near-RT RICs175-b. In some implementations, the SMO180-amay communicate with components configured in accordance with a 4G RAN (e.g., via an O1 interface). Additionally, or alternatively, in some implementations, the SMO180-amay communicate directly with one or more RUs170-avia an O1 interface. The SMO180-aalso may include a non-RT RIC175-aconfigured to support functionality of the SMO180-a.

The non-RT RIC175-amay be configured to include a logical function that enables non-real-time control and optimization of RAN elements and resources, Artificial Intelligence (AI) or Machine Learning (ML) workflows including model training and updates, or policy-based guidance of applications/features in the near-RT RIC175-b. The non-RT RIC175-amay be coupled with or communicate with (e.g., via an A1 interface) the near-RT RIC175-b. The near-RT RIC175-bmay be configured to include a logical function that enables near-real-time control and optimization of RAN elements and resources via data collection and actions over an interface (e.g., via an E2 interface) connecting one or more CUs160-a, one or more DUs165-a, or both, as well as an O-eNB210, with the near-RT RIC175-b.

In some examples, to generate AI/ML models to be deployed in the near-RT RIC175-b, the non-RT RIC175-amay receive parameters or external enrichment information from external servers. Such information may be utilized by the near-RT RIC175-band may be received at the SMO180-aor the non-RT RIC175-afrom non-network data sources or from network functions. In some examples, the non-RT RIC175-aor the near-RT RIC175-bmay be configured to tune RAN behavior or performance. For example, the non-RT RIC175-amay monitor long-term trends and patterns for performance and employ AI or ML models to perform corrective actions through the SMO180-a(e.g., reconfiguration via01) or via generation of RAN management policies (e.g., A1 policies).

In some examples, the network architecture200may represent an example of a private network, which may be a non-public mobile network that may use a licensed, unlicensed, or shared RF spectrum and may be intended for non-public (e.g., private) use by, for example, an organization or company (e.g., for precision agriculture, construction and mining, digitized education, connected healthcare, connected cities, intelligent retail, smart manufacturing, and mobile experiences, among other examples). In some examples, the private network may leverage or be based on a second type of network protocols, such as 3GPP protocols, and may be referred to as a second type of network accordingly (e.g., a 3GPP network or a 5G network).

Techniques, systems, and devices described herein provide for reduced latency and improved reliability and efficiency associated with deployment of a network of the second type of network by integrating the second type of network with a trusted network of a first type at least during deployment of the second network type. The first network type may be a different type of network than the second network type and may use an unlicensed spectrum. In some examples, the first network type may be referred to as a non-3GPP network type and may be, for example, a Wi-Fi network, or some other type of network.

The trusted non-3GPP gateway function (TNGF)220illustrated inFIG.2may represent an example of a gateway function associated with the first network type. That is, the TNGF220may be a network node of the first network type. The first network may include one or more other network nodes not illustrated inFIG.2. For example, the first network may include a trusted non-3GPP AP (TNAP), among one or more other nodes or components, as described in further detail elsewhere herein, including with reference toFIGS.3-12.

The TNGF220may communicate with one or more components of the second network via one or more interfaces, such as the E2tr interface and the O2t interface illustrated inFIG.2. The E2tr interface may represent an interface between the TNGF220and the near-RT RIC175-b, which may be included in or coupled with an O-cloud205, as illustrated inFIG.4. The O2t interface may represent an interface between the TNGF220and the SMO180-a. In some examples, the O2t interface may connect the TNGF220with the non-RT RIC175-awithin the SMO180-a. Although these are referred to as E2tr and O2t interfaces, it is to be understood that the E2tr and O2t interfaces may represent examples of any type of wired or wireless interface between a gateway function of a first network type and network intelligent controllers (e.g., the near-RT RIC175-band/or non-RT RIC175-a) of a second network type.

The first network may establish a connection with one or more wireless devices, such as a UE115-a, if a connection between the UE115-aand the second network type fails. That is, the first network may operate as a backup or standby access network for the second network while the second network is being set up and deployed. The described interfaces between the TNGF220of the first network and the various network nodes of the second network may facilitate relatively efficient and reliable transitions, by the UE115-a, between connections to the first network and connections to the second network, or vice versa. For example, the TNGF220may exchange one or more messages or signals with various components of the second network via the E2tr and O2t interfaces to indicate if the UE115-ahas connected to the TNGF220and facilitate adjustments to the second network type so the UE115-amay transition back to connecting with the second network. Such network integration techniques are described in further detail elsewhere herein, including with reference toFIGS.3-12.

FIG.3shows an example of an integrated network architecture300that supports deployment of a private network using integration with a trusted backup network in accordance with one or more aspects of the present disclosure. The integrated network architecture300may implement or be implemented by aspects of the wireless communications system100or the network architecture200, as described with reference toFIGS.1and2. For example, the integrated network architecture300illustrates a trusted backup network310that is integrated with a private network during deployment of the private network. The trusted backup network310, the private network, or a combination of the two networks, may provide mobile network services to a UE115-b, which may represent an example of a UE115as described with reference toFIGS.1and2.

As described with reference toFIGS.1and2, the trusted backup network310may operate as a temporary backup network for the private network or may operate as a standby access during deployment of the private network, or both. The trusted backup network310may be of a first network type that may be different than a second network type associated with the private network. The network type may represent a set of protocols, frequency bands, and/or standards that are used by the respective network. In some examples, the private network may be a 3GPP-based private network (e.g., a 5G network) and the trusted backup network310may be a Wi-Fi-based network, or some other types of networks. In some examples, the trusted backup network310may be referred to as a trusted non-3GPP access network (TNAN).

The trusted backup network310may include one or more network nodes. For example, the trusted backup network310may include a TNAP335, which may be an AP for the trusted backup network310. In some examples, the trusted backup network310may include multiple APs (not illustrated inFIG.3) the one or more TNAPs335may establish wireless connections or wireless communication links (e.g., Yt) with one or more UEs115-b, such that the UE115-bmay connect to the trusted backup network310via the TNAP335. The UEs115-bin this example may support multiple different RATs, including the RAT associated with the first network type and the RAT associated with the second network type (e.g., a Wi-Fi and 5G-capable UE115, for example).

The trusted backup network310may additionally, or alternatively, include a TNGF320, which may represent an example of a TNGF220, as described with reference toFIG.2. The TNGF320may be a gateway function for the trusted backup network310. The TNGF320may connect to the TNAP335via a backhaul link (e.g., Ta). Although the trusted backup network310is shown as including the TNAP335and the TNGF320inFIG.3, it is to be understood that a trusted backup network310as described herein may include any quantity of one or more network nodes or other components, including the network nodes illustrated inFIG.3, and/or one or more other network nodes or components that may not be illustrated inFIG.3. Other components in the integrated network architecture300may, in some examples, be included in or components of the private network.

The TNGF320may connect to a cloud associated with the second network type via one or more backhaul links (e.g., an N2 interface). The cloud, in this example, may include the AMF340, the UPF345, or both. In some examples, the cloud may be of a same network type as the private network, such as a 3GPP network type, or some other type of network. The cloud may represent an example of a core network130, as described with reference toFIGS.1and2. For example, the cloud may include at least one control plane entity, such as the AMF340, to manage access and mobility, and at least one user plane entity to route packets or interconnect external networks, such as the UPF345and/or the PDN350. The UPF345may connect with a PDN350, such as the internet. In some examples, the AMF340may manage signaling for the connection with the UE115-band the UPF345may manage data associated with the connection with the UE115-b.

The network entity105-bmay represent an AP for the private network (e.g., a 5G AP, or some other type of AP). The UE115-bmay establish a connection with the private network via the network entity105-b. The network entity105-bmay relay signaling from the UE115-bto the AMF340via a backhaul link (e.g., an N2 interface). That is, the AMF340may be connected with the network entity105-bassociated with the private network via a first N2 interface and with the TNGF320associated with the trusted backup network310via a second N2 interface. The UE115-bmay, additionally, or alternatively, communicate directly with the AMF340via an N1 interface or directly with the TNGF320via an Nwt interface, as shown by the dashed lines inFIG.3.

As described herein, the UE115-bmay represent a wireless device that is capable of connecting with more than one network type (e.g., a multi-RAT capability). For example, the UE115-bmay be capable of connecting with the AP of the trusted backup network310, which may support a first RAT, and the UE115-bmay be capable of connecting with an AP of the private network, which may support a second RAT. The first RAT may be associated with unlicensed RF spectrum bands (e.g., Wi-Fi) and the second RAT may be associated with unlicensed and/or licensed RF spectrum bands.

Techniques, systems, and devices described herein provide for improved utilization of the trusted backup network310during deployment of the private network by defining one or more interfaces between the TNGF320of the trusted backup network310and one or more network intelligent controllers of the private network. Such interfaces may be utilized to exchange messages and signaling between the two network types to facilitate an improved connection between the UE115-band the private network, as described in further detail elsewhere herein, including with reference toFIGS.4-12.

FIG.4shows an example of an integrated network architecture400that supports deployment of a private network using integration with a trusted backup network in accordance with one or more aspects of the present disclosure. The integrated network architecture400may implement or be implemented by aspects of the wireless communications system100, the network architecture200, and the integrated network architecture300, as described with reference toFIGS.1-3. For example, the integrated network architecture400illustrates a trusted backup network (e.g., the TNAN410) that is integrated with a private network (e.g., the core network430and corresponding network nodes) during deployment of the private network. The TNAN410may be integrated with the private network via one or more interfaces, as described herein.

The TNAN410may include a TNAP435and a TNGF420, which may represent examples of the TNAP335and the TNGF320, as described with reference toFIG.3. The TNAP435and the TNGF420may be connected via a wireless backhaul link, such as the Ta interface illustrated inFIG.4. In some examples, the TNAP435may establish a wireless connection (e.g., a Yt connection) with a UE115-c.

The private network may include a core network430, which may manage multiple network nodes or controllers. For example, the private network may include an RU470(e.g., an O-RAN RU (O-RU)), which may connect with and communicate with wireless devices, such as the UE115-b, via one or more communication links (e.g., Uu links). The RU470may, in some examples, be connected with a fronthaul multiplexer (FHM)485, which may be operable to split and/or combine multiple radio signals on the fronthaul. The RU470may also be connected (e.g., directly or via the FHM485) with one or more network nodes within an O-cloud205-a. The network nodes, which may be referred to as E2 nodes in some examples, may include a DU465and one or more CUs460(e.g., a control plane CU460, a user plane CU460, or both), which may be distributed nodes within the O-cloud205-a(e.g., an O-RAN CU (O-CU) and an O-RAN DU (O-DU)). The O-cloud205-amay include the DU465, the CU460, a near-RT RIC475-b, a disaggregated network entity (e.g., an O-eNB), other network nodes or components, or any combination thereof. The near-RT RIC475-bmay connect with the various network nodes, such as the DU465and the CU460, via an E2 interface. The RU470, DU465, CU460, O-cloud205-a, and the near-RT RIC475-bmay represent examples of corresponding devices and components as described with reference toFIGS.1and2.

The private network may include an SMO180-b(e.g., an SMO framework). The SMO180-bmay represent an example of the SMO180-adescribed with reference toFIG.2. For example, the SMO180-bmay represent an operation support system (OSS) that may provide an automation platform for the private network (e.g., the RAN). The SMO180-bmay support or facilitate a fault, configuration, accounting, performance, and security (FCAPS) network management framework. For example, the SMO180-bmay support FCAPS for the private network. The SMO180-bmay additionally, or alternatively, manage one or more PHY layer functions.

The SMO180-bmay interface with other entities in the private network via an O1 interface to provide the service and management functionalities. For example, the SMO180-bmay interface with the DU465, the CU460, and the near-RT RIC475-bvia O1 interfaces. The SMO180-bmay interface with the RU470and the FHM485, among other components, via the O1 interfaces and/or a management plane (M-Plane).

The SMO180-bmay include or be coupled with a non-RT RIC475-a, which may represent an example of the non-RT RIC175-adescribed with reference toFIG.2. The non-RT RIC475-aand the near-RT RIC475-bmay represent examples of network intelligent controllers that may manage operation of the network entities, such as the DU465and the CU460. The non-RT RIC475-aand the near-RT RIC475-bmay use different timings to decide optimization and automation decisions for the network entities. In some examples, decisions on policy and changes to the RAN may be made by the non-RT RIC475-ain a time period that is greater than or equal to one second, or some other time period. Decisions on policy and changes to the RAN may be made by the near-RT RIC475-bin a time period that is greater than or equal to 10 milliseconds and less than or equal to one second, or some other time period that is shorter than the time period associated with decisions by the non-RT RIC475-a(e.g., the near-RT RIC475-bmay operate in near-real time).

Each network entity may be managed by both the non-RT RIC475-aand the near-RT RIC475-bto achieve the different timings, which may improve reliability and efficiency of the FCAPS services. For example, the near-RT RIC475-bmay, in some examples, facilitate radio resource management and mobility management, which may be associated with relatively strict latency requirements, and the non-RT RIC475-amay facilitate other decisions for the RAN that may be able to wait longer periods of time for more robust data sets, for a result of a machine learning algorithm, or the like.

As described herein, to improve integration between the TNAN410and the private network, one or more interfaces may be established between the TNGF420and various network intelligent controllers within the private network. As described with reference toFIG.3, the TNGF420may be connected with the core network430. For example, the TNGF420may be connected with an AMF and/or a UPF of the core network430via one or more backhaul links. The described techniques include an extension of the O1 and E2 interfaces between the network nodes and the non-RT RIC475-aor the near-RT RIC475-b, respectively. For example, the TNGF420may establish an interface (e.g., the O1t interface) with the non-RT RIC475-a. The TNGF420may establish another interface (e.g., the E2tr interface) with the near-RT RIC475-b. The TNGF420may communicate KPIs or other metrics associated with the TNAN410to the non-RT RIC475-aand the near-RT RIC475-bto facilitate integration between the TNAN410and the private network.

Examples of signaling that may be exchanged via the interfaces defined herein may be described in further detail elsewhere herein, including with reference toFIGS.5-12.

FIG.5shows an example of a greenfield deployment workflow500that supports deployment of a private network using integration with a trusted backup network in accordance with one or more aspects of the present disclosure. The greenfield deployment workflow500may implement or be implemented by aspects of the wireless communications system100, the network architecture200, and the integrated network architectures300and400, as described with reference toFIGS.1-4. For example,FIG.5illustrates actions performed by a client device (e.g., a UE115), a TNAP, a TNGF, a near-RT RIC, and a non-RT RIC, among other devices, as part of deployment of a private network of a second type (e.g., 3GPP) using integration of a first network type (e.g., non-3GPP). The devices and components described with reference toFIG.5may represent examples of corresponding devices and components as described with reference toFIGS.1-4. Additionally,FIG.5illustrates actions performed by a network operator, a network planner, or a network engineer.

The greenfield deployment workflow500illustrates an example of deployment of a private network of the second type (e.g., 3GPP) using integration with the second network type (e.g., Wi-Fi). In this example, the deployment may be an example of a greenfield deployment, which may correspond to network deployment in a system in which there is no historic or previous wireless private network deployment, as described with reference toFIG.1. For example, a client may build a new stadium that may support (e.g., exclusively) private network coverage using the second network type without any pre-existing network coverage.

In the following description of greenfield deployment workflow500, the operations described may be performed in a different order than the order shown, or other operations may be added or removed from the greenfield deployment workflow500. Specific operations may also be left out of the greenfield deployment workflow500or may be performed in different orders or at different times. Further, although some operations or signaling may be shown to occur at different times for discussion purposes, these operations may actually occur at the same time.

At505, private network dimensioning may occur based on customer requirements, such as the features and functions required to meet the needs, business goals, and technical requirements identified by the customer. At510, RF planning may occur. For example, site locations of the second network type (e.g., 5G, 3GPP, or the like) may be identified and customer profiles may be created or determined for each site location. The network dimensioning and RF planning may be performed to determine proper dimensions for a planned private network that may serve one or more clients on licensed frequency bands, unlicensed frequency bands, or both.

At515, the network sites of the second network type, the first network type, or both may be mounted at one or more desired physical locations. An AP module of a trusted backup network of the first network type (e.g., Wi-Fi) may additionally, or alternatively, be mounted. In some examples, the trusted backup network AP module may be inherent, detachable, or both.

At520, one or more additional network sites may be mounted at intermediate locations (e.g., physical locations). The additional network sites may be exclusive to the first network type, in some examples. For example, if the network sites of the second network type identified at510have wider coverage than the respective or corresponding network sites of the first network type, additional site mounting may be beneficial.

At525, zero-touch provisioning may occur to discover and configure the network sites of the first and/or second network types (e.g., unlicensed and/or licensed). For example, wireless devices within the networks may be configured using a switch feature to automatically update operating systems, deploy patches or bug fixes, and implement features prior to connection.

At530, the network sites of the first and/or second network types may be activated with a quality assurance process (e.g., acceptance testing). In some examples, each network site of the second network type may be activated, or each network site of the first network type may be activated, or both. In other examples, a subset of selected network sites of the second network type or selected network sites of the first network type may be activated. The acceptance testing may determine the degree to which the deployment meets the customer needs and approval, and may include beta testing, application testing, field testing, or end-user testing.

At535, the network sites of the first and second network types may be activated and tuned. The tuning may be performed according to the respective profiles of each network site of the first and second types.

At540, one or more wireless devices to be served by the private network (e.g., client devices) may be installed with a chipset that supports the second network type (e.g., a 5G chipset), a chipset that supports the first network type (e.g., a Wi-Fi chipset), and/or a subscriber identity module (SIM). The wireless devices may be powered on. The wireless devices may be configured to (e.g., set) with a default network preference setting, which may indicate a preferred network type for the wireless device. In this example, the preferred network type may be the second network type (e.g., a “prefer licensed network” or “prefer 5G” option), such that the device utilizes the first network type (e.g., Wi-Fi) only when there is no (or limited) network coverage for the second network type. In some examples, one or more of the described actions for deployment of the network may be performed by a network operator or planner, or by one or more other network entities or components.

At545, the one or more devices, one or more networks, one or more network sites of the second network type, and one or more network sites of the first network type may be monitored (e.g., relatively continuous and aggressive monitoring). In some examples, data may be collected and analyzed. The monitoring, data collection, and analysis may be performed autonomously (e.g., by using the deployed network entities).

At550, one or more insufficiencies (e.g., access management issues, connection management issues, or mobility management issues) of the RAN of the second network type may be learned via at least one of an arrival of registration requirements at an AMF via the gateway function (e.g., the TNGF, as described with reference toFIG.2) or KPI monitoring related to the network of the first network type. In some examples, the registration requirements may be fed, via the TNGF, to the near-RT RIC via the E2tr interface. In some examples, the KPI monitoring may be performed by the TNGF and a non-RT RIC. For example, the non-RT RIC may perform a communication management operation and may collect KPIs from the TNGF, as described further with reference toFIG.7.

At555, the network RAN of the second network type may be optimized to meet service level agreements (SLAs) and/or the agreed upon KPIs. Network RAN optimization may include revisions to the basic RAN plan based on insufficiencies, if any, identified at550.

At560, in some examples, once a desired optimization is reached, network APs and modules of the first network type may optionally be powered off and/or detached in devices. In some other examples, the network APs and modules of the first network type may remain as a backup in case the network of the second network type experiences issues again (e.g., via an integrated USB-based interface or connection).

At565, private network deployment may be successful, and KPI monitoring and analysis may continue to maintain a stable and reliable network connection for the one or more customers.

Examples of signaling that may be exchanged via the interfaces defined herein may be described in further detail elsewhere herein, including with reference toFIGS.6-12

FIG.6shows an example of a brownfield deployment workflow600that supports deployment of a private network using integration with a trusted backup network in accordance with one or more aspects of the present disclosure. The brownfield deployment workflow600may implement or be implemented by aspects of the wireless communications system100, the network architecture200, and the integrated network architectures300and400, as described with reference toFIGS.1-4. For example,FIG.6illustrates actions performed by a client device (e.g., a UE115), a TNAP, a TNGF, a near-RT RIC, and a non-RT RIC, among other devices, as part of deployment of a private network of a second type (e.g., 3GPP) using integration of a first network type (e.g., non-3GPP). The devices and components described with reference toFIG.6may represent examples of corresponding devices and components as described with reference toFIGS.1-4. Additionally,FIG.6illustrates actions performed by a network operator, a network planner, or network engineer.

The brownfield deployment workflow600illustrates an example of deployment of a private network of the second type (e.g., 3GPP) using integration with the first network type (e.g., Wi-Fi). In this example, the deployment may be an example of a brownfield deployment, which may correspond to network deployment in a system in which there is a previous wireless private network deployment, as described with reference toFIG.1. For example, a client with an office building which already uses the first network type (e.g., Wi-Fi) may implement a second network type (e.g., for increase security). In another example, a factory may implement a second network type on top of an existing first network type in the factory to support relatively high-speed and low-latency operations to meet the growing demands of automation.

In the following description of brownfield deployment workflow600, the operations described may be performed in a different order than the order shown, or other operations may be added or removed from the brownfield deployment workflow600. Specific operations may also be left out of the brownfield deployment workflow600or may be performed in different orders or at different times. Further, although some operations or signaling may be shown to occur at different times for discussion purposes, these operations may actually occur at the same time.

At605, private network dimensioning may occur based on customer requirements, such as the features and functions required to meet the needs, business goals, and technical requirements identified by the customer.

At610, RF planning occurs. For example, site locations of the second network type (e.g., 5G, 3GPP, or the like) may be identified and customer profiles may be created or determined for each site location. The network dimensioning and RF planning may be performed to determine proper dimensions for a planned private network that may serve one or more clients on licensed frequency bands, unlicensed frequency bands, or both.

At615, the network sites may be mounted at one or more desired physical locations. An AP module of a trusted backup network of a first network type (e.g., Wi-Fi) may additionally, or alternatively, be mounted. In some examples, the trusted backup network AP module may be inherent, detachable, or both.

At620, zero-touch provisioning may occur to discover and configure the network sites of the first and/or second network types (e.g., unlicensed and/or licensed). For example, wireless devices within the networks may be configured using a switch feature to automatically update operating systems, deploy patches or bug fixes, and implement features prior to connection.

At625, any existing network APs of the first network type may be integrated as a trusted WLAN (TWAN) via the gateway function (e.g., the TNGF) to the private network core of the second network type. The one or more APs may be routed to the second network core via the TNGF of the first network type as a trusted device. The one or more APs may thereby be leveraged during deployment of the private network (e.g., the 5G RAN).

At630, the network sites of the first and/or second network types may be activated with a quality assurance process (e.g., acceptance testing). In some examples, each network site of the second network type may be activated, or each network site of the first network type may be activated, or both. In other examples, a subset of selected network sites of the second network type or selected network sites of the first network type may be activated. The acceptance testing may determine the degree to which the deployment meets the customer needs and approval, and may include beta testing, application testing, field testing, or end-user testing.

At635, the network sites of the first and second network types may be activated and tuned. The tuning may be performed according to the respective profiles of each network site of the first and second types.

At640, one or more wireless devices to be served by the private network (e.g., client devices) may be installed with a chipset that supports the second network type (e.g., a 5G chipset), a chipset that supports the first network type (e.g., a Wi-Fi chipset), and/or a SIM. The wireless devices may be powered on. The wireless devices may be configured to (e.g., set) with a default network preference setting, which may indicate a preferred network type of the wireless device. In this example, the preferred network type may be the second network type (e.g., a “prefer licensed network” or “prefer 5G” option), such that the device utilizes the first network (e.g., Wi-Fi) only when there is no network coverage for the second network type. In some examples, one or more of the described actions for deployment of the network may be performed by a network operator or planner, or by one or more other network entities or components.

At645, the one or more devices, one or more networks, one or more network sites of the second network type, and one or more network sites of the first network type may be monitored (e.g., relatively aggressive and continuous monitoring). In some examples, data may be collected and analyzed. The monitoring, data collection, and analysis may be performed autonomously (e.g., by using the deployed network entities).

At650, one or more insufficiencies of the RAN of the second network type may be learned via at least one of an arrival of registration requirements at an AMF via the gateway function (e.g., the TNGF) or KPI monitoring related to the network of the first type. In some examples, the KPI monitoring may be performed by the TNGF and a non-RT RIC of the second network type. For example, the non-RT RIC may perform a communication management operation and may collect KPIs from the TNGF, as described further with reference toFIG.7.

At655, the network RAN of the second network type may be optimized to meet SLAs and/or the agreed upon KPIs. Network RAN optimization may include revisions to the basic RAN plan based on insufficiencies identified at650.

At660, in some examples, once a desired optimization is reached, network APs and modules of the first network type may optionally be powered off in devices. In some other examples, the network APs and modules of the first network type may remain as a backup in case the network of the second network type experiences issues again (e.g., via an integrated USB-based interface or connection).

At665, private network deployment may be successful, and KPI monitoring and analysis may continue to maintain a stable network connection for the customers (e.g., users of the private network).

Examples of signaling that may be exchanged via the interfaces defined herein may be described in further detail elsewhere herein, including with reference toFIGS.7-12.

FIG.7shows an example of a flow chart700that supports deployment of a private network using integration with a trusted backup network in accordance with one or more aspects of the present disclosure. The flow chart700may implement or be implemented by aspects of the wireless communications system100, the network architecture200, and the integrated network architectures300and400, as described with reference toFIGS.1-4. For example, the flow chart700illustrates actions performed by a client device (e.g., a UE115), a TNAP, a TNGF, a near-RT RIC, and a non-RT RIC, among other devices, as part of deployment of a private network of a second type (e.g., 3GPP) using integration of a first network type (e.g., non-3GPP). The devices and components described with reference toFIG.7may represent examples of corresponding devices and components as described with reference toFIGS.1-4.

In the following description of the flow chart700, the operations described may be performed in a different order than the order shown, or other operations may be added or removed from the flow chart700. Specific operations may also be left out of the flow chart700or may be performed in different orders or at different times. Further, although some operations or signaling may be shown to occur at different times for discussion purposes, these operations may actually occur at the same time.

At705, a client (e.g., a UE) may connect to the network of the first type. For example, a wireless device, such as a UE, may connect to the first network type by establishing a connection with or requesting to establish a connection with a TNAP or other AP of the first network type. In some examples, the UE may connect to the TNAP in response to or based on a failed connection or connection attempt with the second network type based on, for example, dead spots or mobility issues with the network of the second network type, among other potential scenarios in which a connection may fail.

At710, the gateway function (e.g., the TNGF220,320, or420, as described with reference toFIGS.2-4) may receive a message (e.g., a radius message, or some other type of message) that includes an extensible authentication protocol (EAP) response from the UE. The message may be relayed to the TNFG via the TNAP, in some examples. The EAP response may include an EAP identity that conveys one or more IDs associated with the UE (e.g., a licensed network globally unique temporary identifier (GUTI), a licensed network subscription concealed identifier (SUCI), or a network access identifier (NAI)).

At715, The TNGF may inform the near-RT RIC of the new registration request from the UE. For example, the TNGF may establish an interface between the TNGF and the near-RT RIC of the second network type. The interface may be referred to as an E2tr interface, as described with reference toFIGS.2-4. The TNGF may transmit, to the near-RT RIC via the E2tr interface, a message that indicates the connection between the TNGF and the UE. In some examples, the message may include one or more IDs, such as client-level and/or TNAP IDs, which may be presented as inputs.

At720, the near-RT RIC (e.g., a network intelligent controller) may perform corrective traffic steering optimization on licensed network RAN sites (e.g., co-located sites). For example, radio resource allocation (e.g., resource management), radio access control, connection management, and mobility management may be improved, as discussed elsewhere in the present disclosure. In some examples, corrective traffic steering optimization may include corrective actions such as antenna adjustments (e.g., antenna orientation, azimuth, or elevation changes on the RU), beamforming changes (e.g., on the transmitter or receiver), power control (e.g., for uplink, downlink, or both), optimization based on client capabilities and use cases (e.g., dynamic beacon intervals for IoT devices), or any combination thereof. Decisions on policy and changes to the RAN may be made by the near-RT RIC in a time period that is greater than or equal to 10 milliseconds and less than or equal to one second, or some other time period that is shorter than the time period associated with decisions by the non-RT RIC475-a. For example, at715, the TNGF may transmit a message to the near-RT RIC via the E2tr interface, and the near-RT RIC may perform corrective actions within 10 milliseconds of receiving the message.

At725, the TNGF may monitor the EAP registration between the UE and the private network core of the second network type. In some examples, the TNGF may determine that the EAP registration was not successful. In some other examples, the TNGF may determine that the EAP registration was successful.

At730, if the EAP authentication with the core network was not successful, the TNGF may inform the near-RT RIC of registration failure. In some examples, the TNGF may present the client-level ID, the AP ID (e.g., the TWAN identifier (ID)), or both as inputs. At735, the near-RT RIC may perform a corrective communication management operation based on receiving the indication of registration failure (e.g., within 10 milliseconds of receiving the indication of registration failure). For example, the near-RT RIC may perform a reversive traffic steering optimization on co-located licensed RAN sites, which may include, for example, switching from one network type to another network type according to dynamic network and traffic environments. In some examples, this operation may be the same as, similar to, or different than the optimization performed by the near-RT RIC in step720.

At740, if the authentication with the core network was successful, the TNGF may inform the non-RT RIC (e.g., within the SMO) of the new registration request from the UE (e.g., within one second of determining that the authentication was successful). For example, the TNGF may establish an interface between the TNGF and the non-RT RIC of the second network type. The interface may be referred to as an O1t interface, as described with reference toFIGS.2-4. The TNGF may transmit, to the non-RT RIC via the O1t interface, a message that indicates the connection between the TNGF and the UE. In some examples, the message may include one or more IDs, such as a client-level ID, an AP ID (e.g., a TNAP ID), or both as inputs via the O1t interface.

Additionally, or alternatively, the AMF may inform the non-RT RIC (e.g., within the SMO) of the new registration request from the UE. For example, the AMF may transmit, to the non-RT RIC, a message that indicates the connection between the AMF and the UE is established. In some examples, the message may include one or more IDs, such as a client-level ID, an AP ID (e.g., a TNAP ID), or both as inputs.

At745. The non-RT RIC may perform a communication management operation. For example, the non-RT RIC may determine how well the private network meets customer integration requirements, priorities, and goals and perform actions to mitigate any deficiencies. In some examples, the non-RT RIC may identify and update to appropriate software versions, provide critical bug analysis, implement system confirmation improvements, and generate reports on KPIs and critical success factors (CSFs). That is, the non-RT RIC may perform course-corrective network orchestration and optimization via the O1 interface towards a CU or a DU. In some examples, the non-RT RIC may perform network orchestration and optimization via the M-plane towards an RU.

At750, the TNGF may continue to monitor the connection (e.g., the registration) between the UE and the network core of the second network type. In some examples, the TNGF may measure (e.g., collect) one or more KPIs associated with the connection between the UE and the network core of the second network type. In some examples, KPI collection may occur at the device or AP level. The TNGF may, in some examples, transmit a message containing and/or indicating the KPIs to the non-RT RIC (e.g., via the O1t interface). In some examples, KPI collection and/or transmission may occur at regular intervals (e.g., a periodicity greater than one second).

At755, the non-RT RIC or some other device or component may determine whether the desired private network optimization has been reached. For example, the non-RT RIC may compare the metrics (e.g., KPI) received from the TNGF to a threshold quality of the connection between the UE and the second network type. If the desired optimization has not been reached (e.g., the received KPI is below the threshold quality), the non-RT RIC may repeat steps745and750(e.g., the non-RT RIC may continue to collect KPIs and perform corrective operations).

At760, in some examples, if the desired optimization has been reached, the first network type may optionally be removed or disabled to, for example, reduce operational expenditures and improve power efficiency. For example, one or more modules and/or devices and APs of the second network type may be turned off or removed. In some examples, the TNGF entity may be removed or disabled. Techniques for disabling the first network type may be described in further detail elsewhere herein, including with reference toFIGS.8-12. Additionally, or alternatively, in some examples, the first network type may remain integrated with the second network type after the desired optimization or threshold quality has been achieved. In such examples, the TNGF may continue monitoring and measuring KPIs associated with the connection between the UE and the second network type.

A first network type may thereby be integrated with a second network type via one or more interfaces to improve deployment of the second network type. By exchanging signaling via the interfaces during the deployment and setup of the second network type, the first network type may support improved deployment efficiency and reliability. Examples of signaling that may be exchanged via the interfaces defined herein may be described in further detail elsewhere herein, including with reference toFIGS.8-12.

FIG.8shows an example of a process flow800that supports deployment of a private network using integration with a trusted backup network in accordance with one or more aspects of the present disclosure. The process flow800shows how a UE115-dmay register with a trusted backup network (e.g., a TNAN), which may include a TNAP835and a TNGF820based on a failed registration attempt with a private network. The process flow800may implement or be implemented by aspects of the wireless communications system100, the network architecture200, and the integrated network architectures300and400, as described with reference toFIGS.1-4. For example, the process flow800illustrates actions performed by a client device (e.g., the UE115-d), the TNAP835, the TNGF820, an AMF840, a near-RT RIC175-c, and surrounding cells805(e.g., a gNB, a CU, or a DU), among other devices, as part of deployment of a private network of a second type (e.g., 3GPP) using integration with a first network type (e.g., non-3GPP). The devices and components described with reference toFIG.8may represent examples of corresponding devices and components as described with reference toFIGS.1-7.

In the following description of the process flow800, the operations described may be performed in a different order than the order shown, or other operations may be added or removed from the process flow800. Specific operations may also be left out of the process flow800or may be performed in different orders or at different times. Further, although some operations or signaling may be shown to occur at different times for discussion purposes, these operations may actually occur at the same time.

At845, the near-RT RIC175-cmay transmit, and the TNGF820may receive, a RIC subscription request. The RIC subscription request may be an E2AP RIC subscription request and, in some examples, may be based on a trigger. For example, the RIC subscription request transmission and/or the generation or transmission of a report may be triggered by the arrival of a registration request from the first network type (e.g., the trusted backup network). In some examples, the subscription request may represent an example of a request for the TNGF820to establish an interface between the TNGF820and the near-RT RIC175-c. The interface may represent an example of the E2tr interface, as described with reference toFIGS.2-7.

At850, the TNGF820may transmit, and the near-RT RIC175-cmay receive, a RIC subscription acknowledgment (ACK). The RIC subscription ACK may indicate to the near-RT RIC175-cthat the RIC subscription request was received. In some examples, the RIC subscription ACK may indicate successful establishment of the E2tr interface. Additionally, or alternatively, the TNGF820may establish communication with the near-RT RIC175-cvia the E2tr interface subsequent to transmitting the subscription ACK.

At855, the UE115-dmay transmit, and the TNGF820may receive, a registration request. The registration request may request registration with the first network type. The UE115-dmay transmit the registration request and attempt to connect to the first network type, for example, due to decreased or lost coverage of the second network type at the UE115-d. For example, if a connection between the UE115-dand the second network type is unreliable or disconnected, the UE115-dmay attempt to connect to the first network type, which may be the trusted backup network. The registration request may include an EAP response and one or more access network (AN) parameters. The one or more AN parameters may include a UE ID (e.g., an international mobile subscriber ID (IMSI), a subscription permanent ID (SUPI), or a GUTI), a selected public land mobile network (PLMN) ID, requested network slice assistance information (NSAI), an establishment cause (e.g., a lost connection to the network of the second network type), an indication of a non-access stratum (NAS) protocol data unit (PDU), or any combination thereof.

At860, the TNGF820may transmit, and the near-RT RIC175-cmay receive, a RIC indication (e.g., an E2AP RIC indication) via the E2tr interface. The RIC indication may indicate that the connection between the TNGF820and the UE115-dis established, as described, for example, with reference to step715inFIG.7. For example, the TNGF820may establish a connection for communications with the UE115-din accordance with the first network type in response to the request from the UE115-d. The TNGF820may transmit the RIC indication to inform the near-RT RIC175-cthat the UE115-dconnected to the first network type. The RIC indication may implicitly or explicitly indicate that the UE115-dattempted to connect to the first network type based on a failed connection with the second network type, in some examples.

At865, the near-RT RIC175-cmay prepare RRC and mobility control policies. For example, the near-RT RIC may prepare an idle mode and a connected mode for the surrounding cells805, which may be target cells for connection with the UE115-dthat surround the TNAP (e.g., a collocated cell). Preparing the RRC and mobility control policies may be referred to as performing a communication management operation or a corrective traffic steering optimization process in some examples herein. That is, the near-RT RIC175-cmay adjust one or more communication management parameters for one or more network entities associated with the second network type. The near-RT RIC175-cmay perform the communication management operation based on the RIC indication received from the TNGF820. The near-RT RIC175-cmay perform the communication management operation in an attempt to improve conditions within the second network type to improve future connections with the UE115-d.

At870, the UE115-dmay register with (e.g., connect to) the second network type. For example, an AMF840may be selected for the connection with the UE115-d, and the UE115-dand may subsequently perform a registration procedure with the core network of the second network type via the TNGF820and the AMF840. The UE115-dmay connect to the second network type based on the optimizations performed by the near-RT RIC175-cat865, in some examples. Additionally, or alternatively, the UE115-dmay be configured to prioritize a connection with the second network type over a connection with the first network type, and the UE115-dmay attempt to connect to the second network periodically or at various time instances.

At875, the near-RT RIC175-cmay transmit, and the surrounding cells805may receive, a message including a RIC control request (e.g., an E2AP RIC control request via an E2 interface). The near-RT RIC175-cmay, in some examples, transmit the message in response to receiving the RIC indication that indicates the connection between the UE115-dand the TNGF820at860. In some examples, the message may include an indication of one or more network optimization parameters to be used by the surrounding cells805, which may improve network efficiency and reliability across the surrounding cells805. The message may be associated with the communication management operation described in more detail with reference to step735ofFIG.7and to step1240ofFIG.12.

At880, the surrounding cells805may change one or more parameters in accordance with or based on the RIC control request received from the near-RT RIC175-cat875. For example, a gNB CU or DU, or some other network entity in each of the one or more surrounding cells805, may change radio resource management (RRM) parameters and/or mobility management parameters to optimize coverage.

At885, the surrounding cells805may transmit, and the near-RT RIC175-cmay receive, a RIC control ACK (e.g., via the E2 interface or some other interface), which may indicate that the RIC control request was received at875. In some examples, the RIC control ACK may include an indication of the parameters changed at880. In some examples, the near-RT RIC may transmit the RIC control request and/or receive the RIC control ACK within a 10-millisecond timeframe.

At890, the TNAN session may be torn down. For example, the TNGF820, the TNAP835, and one or more other devices or components associated with the first network type may be disabled or disconnected to conserve power and costs. The first network may be disabled based on the connection between the UE115-dand the second network type being successful or associated with at least a threshold connection quality. The deconstruction or removal of the first network type may be initiated by one or more devices in the second network type, the first network type, or both.

In a first example, the UE115-dmay initiate a TNAN session teardown in response to detecting improved conditions associated with the connection between the UE115-dand the second network type. In some instances, the correction and optimization procedures performed by the near-RT RIC175-cand/or one or more other entities within the second network (e.g., profile tuning) may improve the network conditions for the second network type. The UE115-dmay be configured with a preference to connect with the second network type over the first network type when conditions support such a connection, such that the UE115-dmay initiate the disconnection of the backup network after the UE115-ddetermines the connection with the second network type is stable and reliable. UE-initiated TNAN session teardown may be described in more detail elsewhere herein, including with reference toFIG.9.

In a second example, the network core of the second network type may initiate the TNAN session teardown. For example, the network core of the second network type may determine to disable the first network type based on receiving KPIs from surrounding cells805that meet KPI criteria or exceed a threshold. Network core-initiated TNAN session teardown may be described in more detail elsewhere herein, including with reference toFIG.10.

In a third example, the non-RT RIC may initiate the TNAN session teardown. For example, the non-RT RIC may receive machine learning data and/or KPIs over a period of time from the surrounding cells805(which may be private network gNBs). If the indicated KPIs meet or exceed a threshold, the non-RT RIC may initiate the TNAN session teardown. Non-RT RIC-initiated TNAN session teardown may be described in more detail elsewhere herein, including with reference toFIG.11.

FIG.9shows an example of a process flow900that supports deployment of a private network using integration with a trusted backup network in accordance with one or more aspects of the present disclosure. The process flow900shows a UE115-einitiating a TNAN session disconnection based on a successful registration between the UE115-eand the second network type. The process flow900may implement or be implemented by aspects of the wireless communications system100, the network architecture200, and the integrated network architectures300and400, as described with reference toFIGS.1-8. For example, the process flow900illustrates actions performed by a client device (e.g., the UE115-e), the TNAP935, the TNGF920, an AMF940, a near-RT RIC175-d, and surrounding cells905(e.g., a gNB, a CU, or a DU), among other devices, as part of deployment of a private network of a second type (e.g., 3GPP) using integration with a first network type (e.g., non-3GPP). The devices and components described with reference toFIG.9may represent examples of corresponding devices and components as described with reference toFIGS.1-8.

In the following description of the process flow900, the operations described may be performed in a different order than the order shown, or other operations may be added or removed from the process flow900. Specific operations may also be left out of the process flow900or may be performed in different orders or at different times. Further, although some operations or signaling may be shown to occur at different times for discussion purposes, these operations may actually occur at the same time.

In this example, the UE115-emay connect to a trusted backup network via the TNGF920based on a failed connection with the second network type. For example, at945, a connection may be activated between the UE115-eand the TNAN, which may include the TNAP935and the TNGF920. At950, the UE115-emay establish a PDU session via the TNAN based on the connection. The connection between the UE115-eand the backup network (e.g., first network) after a failed connection with the second network may be described in further detail elsewhere herein, including with reference to steps845-860inFIG.8.

At955, the UE115-emay detect a network signal of the second network type and successful registration with one or more surrounding cells905of the second network type. At960, the UE115-emay successfully establish a PDU session via at least one surrounding cell905of the second network type. That is, the TNGF920and the second network may communicate via one or more interfaces to improve connection parameters of the second network. For example, the one or more interfaces may represent examples of the E2tr interface, as described with reference toFIGS.2-8. The UE115-emay attempt to re-connect to the second network based on the improved connection parameters. The UE115-emay transfer from a connection with the backup network of the first type to a connection with the second network type, as described in further detail elsewhere herein, including with reference toFIG.7and steps860-885ofFIG.8.

The UE115-emay detect at least one signal from the second network and determine that registration was successful with a network entity of the second network. The UE115-emay establish the PDU session based on determining the registration was successful. In some examples, if a quality of the connection between the UE115-eand the second network exceeds a threshold quality, the UE115-emay initiate a disconnection of the first network, which may be referred to as a TNAN session teardown or disconnection, as described with reference toFIG.8. That is, in this example, the TNAN session disconnection as described with reference toFIG.8may be initiated by the UE115-c.

At965, the AMF940may transmit, and the TNGF920may receive, an N2 resource release request. For example, the N2 resource release request may request the release of TNGF resources. That is, the resource release request may request for a connection between the TNGF920and the second network to be disabled. In some examples, the AMF940may transmit the N2 resource release request based on the UE115-econnecting to the second network type. Additionally, or alternatively, the UE115-emay transmit a signal or indication to the AMF940that triggers the AMF940to transmit the N2 resource release request. In some other examples, one or more measurements or parameters associated with the connection between the UE115-eand the second network may exceed a threshold quality, and the AMF940may transmit the resource release request based on the connection exceeding the threshold quality.

At970, the TNGF920may transmit, and the UE115-emay receive, information, such as an indication or request to delete a payload (e.g., a request to release AN resources corresponding to the PDU session with the backup network, the PDU session ID, or the like). In some examples, the information may be transmitted via an RRC message. In some examples, the TNGF920may include information from the N2 resource release request received at965. At975, the UE115-emay transmit, and the TNGF920may receive, information, such as an acknowledgment of the request to delete a payload, a message confirming that the payload was deleted, indicating the PDU session ID, or the like.

At980, the TNGF920may transmit, and the AMF940may receive, an N2 resource release ACK. For example, the N2 resource release ACK may acknowledge that the TNGF resources have been released, or the N2 resource release ACK may indicate that the TNGF resources will be released. That is, the resource release ACK may indicate that the connection between the TNGF920and the second network type is disabled.

At985, the UE115-emay disconnect from the TNAP935. That is, the TNAN session may be torn down. For example, the TNGF920, the TNAP935, and one or more other devices or components associated with the first network type may be disabled or disconnected to conserve power and costs. In this example, the UE115-emay trigger or initiate the first network disablement based on the connection between the UE115-eand the second network type being successful or associated with at least a threshold connection quality. In some examples, the UE115-emay continue to use the network of the second network type until second network type coverage is lost or drops below a threshold connection quality.

At990, the AMF940may communicate with a session management function (SMF). For example, the AMF940may transmit, and the SMF may receive, N2 SM resource release acknowledgment, secondary RAT usage data, user location information, and the like. In some examples, the SMF may transmit, and the AMF940may receive, a response to the information transmitted by the AMF940.

In this example, the UE115-emay thereby initiate a disconnection from the first network type after using the first network type as a backup network during deployment of the second network type. In some other examples, the disconnection of the first network type may be initiated by one or more other entities, as described in further detail elsewhere herein, including with reference toFIGS.10and11.

FIG.10shows an example of a process flow1000that supports deployment of a private network using integration with a trusted backup network in accordance with one or more aspects of the present disclosure. The process flow1000shows a network core of the second network type (e.g., an AMF1040) initiating a TNAN session disconnection (that is, disabling the first network type) based on receiving KPIs from surrounding cells1005that meet KPI criteria or exceed a threshold. The process flow1000may implement or be implemented by aspects of the wireless communications system100, the network architecture200, and the integrated network architectures300and400, as described with reference toFIGS.1-9. For example, the process flow1000illustrates actions performed by a client device (e.g., the UE115-f), the TNAP1035, the TNGF1020, an AMF1040, a near-RT RIC175-e, and surrounding cells1005(e.g., a gNB, a CU, or a DU), among other devices, as part of deployment of a private network of a second type (e.g., 3GPP) using integration with a first network type (e.g., non-3GPP). The devices and components described with reference toFIG.10may represent examples of corresponding devices and components as described with reference toFIGS.1-9.

In the following description of the process flow1000, the operations described may be performed in a different order than the order shown, or other operations may be added or removed from the process flow1000. Specific operations may also be left out of the process flow1000or may be performed in different orders or at different times. Further, although some operations or signaling may be shown to occur at different times for discussion purposes, these operations may actually occur at the same time.

In this example, the UE115-fmay connect to a trusted backup network via the TNGF1020based on a failed connection with the second network type. For example, at1045, a connection may be activated between the UE115-fand the TNAN, which may include the TNAP1035and the TNGF1020.

At1050, the UE115-fmay establish a PDU session via the TNAN based on the connection. The connection between the UE115-fand the backup network (e.g., first network) after a failed connection with the second network may be described in further detail elsewhere herein, including with reference to steps845-860inFIG.8.

At1055, the AMF1040(e.g., the core network of the second network type) may trigger the TNAN session disconnection based on successful registration between the UE115-fand the second network type. For example, the AMF1040may monitor KPIs associated with the connection between the UE115-fand the second network type (e.g., the surrounding cells1005), as described in more detail with reference toFIGS.11and12. The AMF1040may initiate the TNAN session disconnection based on identifying that the monitored KPIs indicate that a quality of the second network connection meets or exceeds a threshold quality.

At1060, the AMF1040may transmit, and the TNGF1020may receive, an N2 resource release request as part of the TNAN session disconnection initiated by the AMF1040. For example, the N2 resource release request may request the release of TNGF resources. That is, the resource release request may request for a connection between the TNGF1020and the second network to be disabled. In some examples, the AMF1040may transmit the N2 resource release request based on receiving KPI associated with the connection between the UE115-fand the second network type that exceed a threshold. Additionally, or alternatively, the AMF1040may identify that one or more other measurements or parameters associated with the connection between the UE115-fand the second network may exceed a threshold quality, and the AMF1040may transmit the resource release request based on the connection exceeding the threshold quality.

At1065, the TNGF1020may transmit, and the UE115-fmay receive, information, such as an indication or request to delete a payload (e.g., a request to release AN resources corresponding to the PDU session with the backup network, the PDU session ID, or the like). In some examples, the information may be transmitted via an RRC message. In some examples, the TNGF1020may include information from the N2 resource release request received at1060. At1070, the UE115-fmay transmit, and the TNGF1020may receive information, such as an acknowledgment of the request to delete a payload, a message confirming that the payload was deleted, indicating the PDU session ID, or the like.

At1075, the TNGF1020may transmit, and the AMF1040may receive, an N2 resource release ACK. For example, the N2 resource release ACK may acknowledge that the TNGF resources have been released, or the N2 resource release ACK may indicate that the TNGF resources will be released. That is, the resource release ACK may indicate that the connection between the TNGF1020and the second network type is disabled.

At1080, the UE115-fmay disconnect from the TNAP1035. That is, the TNAN session may be torn down. For example, the TNGF1020, the TNAP1035, and one or more other devices or components associated with the first network type may be disabled or disconnected to conserve power and costs. In this example, the AMF1040may trigger or initiate the first network disablement based on the connection between the UE115-fand the second network type being successful or associated with at least a threshold connection quality. In some examples, the UE115-fmay continue to use the network of the second network type until second network type coverage is lost or drops below a threshold connection quality.

At1085, the AMF1040may communicate with an SMF. For example, the AMF1040may transmit, and the SMF may receive, an N2 SM resource release acknowledgment, secondary RAT usage data, user location information, and the like. In some examples, the SMF may transmit, and the AMF1040may receive, a response to the information transmitted by the AMF1040.

In this example, the AMF1040may thereby initiate a disconnection of the first network type after using the first network type as a backup network during deployment of the second network type. In some other examples, the disconnection of the first network type may be initiated by one or more other entities, as described in further detail elsewhere herein, including with reference toFIGS.9and11.

FIG.11shows an example of a process flow1100that supports deployment of a private network using integration with a trusted backup network in accordance with one or more aspects of the present disclosure. The process flow1100shows a non-RT RIC175-g(e.g., a node or component of an SMO) initiating a TNAN session disconnection. The process flow1100may implement or be implemented by aspects of the wireless communications system100, the network architecture200, and the integrated network architectures300and400, as described with reference toFIGS.1-10. For example, the process flow1100illustrates actions performed by a client device (e.g., the UE115-g), the TNAP1135, the TNGF1120, an AMF1140, a near-RT RIC175-f, surrounding cells1105(e.g., a gNB, a CU, or a DU), and a non-RT RIC175-g, among other devices, as part of deployment of a private network of a second type (e.g., 3GPP) using integration of a first network type (e.g., non-3GPP). The devices and components described with reference toFIG.11may represent examples of corresponding devices and components as described with reference toFIGS.1-10.

In the following description of the process flow1100, the operations described may be performed in a different order than the order shown, or other operations may be added or removed from the process flow1100. Specific operations may also be left out of the process flow1100or may be performed in different orders or at different times. Further, although some operations or signaling may be shown to occur at different times for discussion purposes, these operations may actually occur at the same time.

In this example, the UE115-gmay connect to a trusted backup network via the TNGF1120based on a failed connection with the second network type. For example, at1145, a connection may be activated between the UE115-gand the TNAN, which may include the TNAP1135and the TNGF1120.

At1150, the UE115-gmay establish a PDU session via the TNAN based on the connection. The connection between the UE115-gand the backup network (e.g., first network) after a failed connection with the second network may be described in further detail elsewhere herein, including with reference to steps845-860inFIG.8.

At1155, the TNGF1120may transmit, and the non-RT RIC175-g(e.g., the SMO) may receive, indications of KPI associated with the connection between the UE115-gand the second network type (e.g., the surrounding cells1105, which may be associated with one or more private network gNBs). The TNGF1120may transmit the KPI indications periodically or semi-statically over time. In some examples, the non-RT RIC175-gmay also receive machine learning data from the TNGF1120.

At1160, the non-RT RIC175-gmay determine that the received KPI indications indicate a quality of the second network connection meets or exceeds a threshold quality. Additionally, or alternatively, in some examples, the non-RT RIC175-gmay input the KPIs and one or more other parameters into a machine learning algorithm, and the machine learning algorithm may output an indication of the connection between the UE115-fand the second network type exceeding a threshold quality. Based on determining that the threshold has been met or exceeded or based on the machine learning output, in some examples, the non-RT RIC175-gmay transmit, and the TNGF1120may receive, an indication to disconnect the TNAN session. In some examples, the TNAN session disconnection indication may be transmitted via an interface, such as the O1t interface, as described with reference toFIGS.4and7.

At1165, the TNGF1120may transmit, and the UE115-gmay receive, information, such as an indication or request to delete a payload (e.g., a request to release AN resources corresponding to the PDU session with the backup network, the PDU session ID, or the like). In some examples, the information may be transmitted via an RRC message. In some examples, the TNGF1120may include information from the TNAN session disconnection indication received at1160. Additionally, or alternatively, the TNGF1120may transmit a message instructing the TNAP1135to perform MAC-based kick-off for a configurable duration to give the UE115-gsufficient time (e.g., sufficient retries) to perform successful registration & session establishment with the second network.

At1170, the UE115-gmay transmit, and the TNGF1120may receive, information, such as an acknowledgment of the request to delete a payload, a message confirming that the payload was deleted, indicating the PDU session ID, or the like.

At1175, the UE115-gmay disconnect from the TNAP1135. That is, the TNAN session may be torn down. For example, the TNGF1120, the TNAP1135, and one or more other devices or components associated with the first network type may be disabled or disconnected to conserve power and costs. One or more interfaces may be disabled in response to the non-RT RIC175-gdetermining that a threshold connection quality is reached, e.g., the O1t and E2tr interfaces described with reference toFIGS.2-10. In some examples, the UE115-gmay continue to use the network of the second network type until second network type coverage is lost.

At1180, the TNGF1120and the AMF1140may terminate the PDU session via at least one surrounding cell1105of the second network type. That is, based on the non-RT RIC175-gdetermining that a threshold connection quality is reached between the UE115-gand the second network type, the PDU session connecting the UE115-gto the first network type may be disconnected.

In this example, the non-RT RIC175-gmay thereby initiate a disconnection between the UE and the first network type after using the first network type as a backup network during deployment of the second network type. In some other examples, the disconnection of the first network type may be initiated by one or more other entities, as described in further detail elsewhere herein, including with reference toFIGS.9and10.

FIG.12shows an example of a process flow1200that supports deployment of a private network using integration with a trusted backup network in accordance with one or more aspects of the present disclosure. The process flow1200may implement or be implemented by aspects of the wireless communications system100, the network architecture200, and the integrated network architectures300and400, as described with reference toFIGS.1-11. For example, the process flow1200illustrates actions performed by one or more devices of a first network type1205(e.g., non-3GPP) and one or more devices of a second network type1210(e.g., 3GPP), among other devices (such as a wireless device), as part of deployment of a private network of the second type using integration of the first network type. The devices and components described with reference toFIG.12may represent examples of corresponding devices and components as described with reference toFIGS.1-11. For example, a gateway function1220of the first network type1205may be an example of a TNGF, a network intelligent controller1215-aof the second network type1210may be an example of a near-RT RIC, and a network intelligent controller1215-bmay be an example of a non-RT RIC or SMO, as described with reference toFIGS.1-11

In the following description of the process flow1200, the operations described may be performed in a different order than the order shown, or other operations may be added or removed from the process flow1200. Specific operations may also be left out of the process flow1200or may be performed in different orders or at different times. Further, although some operations or signaling may be shown to occur at different times for discussion purposes, these operations may actually occur at the same time.

At1225, the network intelligent controller1215-amay transmit, and the gateway function1220may receive, a message including a request to establish an interface between the gateway function1220and the network intelligent controller1215-a. The message may represent an example of an E2AP RIC subscription request, or some other type of message, and the interface may represent an E2tr interface, or some other type of interface as described herein.

At1230, a wireless device (e.g., a client device, such as a UE115as described with reference toFIGS.1-11) may transmit, and the gateway function1220may receive, a message (e.g., an early access protocol message) including a request to establish a connection with between wireless device and the gateway function1220in accordance with the first network type1205. The connection request message may be transmitted based on a failed connection between the wireless device and the second network type1210. The message may also convey an ID associated with the wireless device.

At1235, the gateway function1220may transmit, and the network intelligent controller1215-amay receive (e.g., via the E2tr interface), a message including an indication that the connection between the wireless device and the gateway function1220is established, as described with reference to step740ofFIG.7. The message may include an ID of the wireless device and/or an ID of an AP associated with the first network type1205.

At1240, the network intelligent controller1215-amay perform a communication management operation for one or more RAN components of the second network type1210based on receiving the message at1235. Performing the communication management operation may include, for example, modifying an allocation of one or more radio resources within the second network type1210, modifying one or more parameters associated with radio access control for the second network type1210, modifying one or more parameters associated with a connection management for the second network type1210, modifying one or more parameters associated with a mobility management for the second network type1210, or any combination thereof. In some examples, the network intelligent controller1215-amay transmit and one or more network entities of the second network type1210may receive, a control request that indicates the connection between the gateway function1220ad the wireless device is established. In such examples, the control request may indicate one or more network optimization parameters associated with the communication management operation.

At1245, the network intelligent controller1215-bmay establish, as part of network integration, an interface (e.g., an O1t interface, as described with reference toFIGS.1-11) between the network intelligent controller1215-band the gateway function1220. In some examples, the network intelligent controller1215-bmay receive (e.g., via the O1t interface) a message indicating a successful registration between the wireless device and the second network type1210. The message may include an ID of the wireless device and an ID of an AP associated with the first network type1205.

At1250, the gateway function1220may transmit, and the network intelligent controller1215-bmay receive, an indication of one or more KPIs associated with the connection between the wireless device and the second network type1210. In some examples, the KPIs may be transmitted periodically via the interface established at1245. In some examples, the network intelligent controller1215-bmay receive the KPIs based on the successful registration indicated at1245.

At1255, the network intelligent controller1215-bmay perform a communication management operation for one or more network entities of the second network type1210based on the one or more KPIs received at1250(as described in more detail with reference toFIG.7). If a desired optimization has not been reached (e.g., the received KPIs are below a threshold value), the network intelligent controller1215-bmay perform course-corrective network orchestration and optimization. If a desired optimization has been reached (e.g., the received KPIs are at or exceed a threshold value), the network intelligent controller1215-b, the wireless device, the network core of the second network type1210, or any combination thereof may initiate a TNAN session teardown or disconnection in response to improved conditions associated with the connection between the UE115-dand the second network type, as described with reference toFIGS.9-11.

The gateway function1220, among other components and devices of the first network type1205, may thereby be integrated with one or more components of the second network type1210to facilitate efficient and reliable deployment of the second network type1210. By using the first network type1205as a backup network, the second network type1210may be able to adjust network parameters and establish a reliable connection with a wireless device more efficiently than if the second network type1210did not use the first network type1205.

FIG.13shows a block diagram1300of a device1305that supports deployment of a private network using integration with a trusted backup network in accordance with one or more aspects of the present disclosure. The device1305may be an example of aspects of a gateway function as described herein. The device1305may include a receiver1310, a transmitter1315, and a communications manager1320. The device1305may also include at least one processor. Each of these components may be in communication with one another (e.g., via one or more buses).

The transmitter1315may provide a means for transmitting signals generated by other components of the device1305. For example, the transmitter1315may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to deployment of a private network using integration with a trusted backup network). In some examples, the transmitter1315may be co-located with a receiver1310in a transceiver module. The transmitter1315may utilize a single antenna or a set of multiple antennas.

The communications manager1320, the receiver1310, the transmitter1315, or various combinations thereof or various components thereof may be examples of means for performing various aspects of deployment of a private network using integration with a trusted backup network as described herein. For example, the communications manager1320, the receiver1310, the transmitter1315, or various combinations or components thereof may support a method for performing one or more of the functions described herein.

In some examples, the communications manager1320may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver1310, the transmitter1315, or both. For example, the communications manager1320may receive information from the receiver1310, send information to the transmitter1315, or be integrated in combination with the receiver1310, the transmitter1315, or both to obtain information, output information, or perform various other operations as described herein.

Additionally, or alternatively, the communications manager1320may support wireless communication at a gateway function of a first network type in accordance with examples as disclosed herein. For example, the communications manager1320is capable of, configured to, or operable to support a means for receiving a first message including a first request to establish, as part of a network integration, an interface between the gateway function of the first network type and a network intelligent controller of a second network type, where the first network type supports communications of a first RAT via unlicensed RF spectrum bands and the second network type supports communications of a second RAT via unlicensed RF spectrum bands, licensed RF spectrum bands, or both, the second RAT different than the first RAT. The communications manager1320is capable of, configured to, or operable to support a means for receiving, based on the network integration and a failed connection between a wireless device and the second network type, a second message including a second request to establish a connection with the wireless device in accordance with the first RAT, the failed connection associated with the second RAT. The communications manager1320is capable of, configured to, or operable to support a means for transmitting, to the network intelligent controller of the second network type via the interface, a third message indicating that the connection between the gateway function of the first network type and the wireless device is established.

By including or configuring the communications manager1320in accordance with examples as described herein, the device1305(e.g., at least one processor controlling or otherwise coupled with the receiver1310, the transmitter1315, the communications manager1320, or a combination thereof) may support techniques for reduced processing, reduced power consumption, and more efficient utilization of communication resources during deployment of a network, among other possibilities.

FIG.14shows a block diagram1400of a device1405that supports deployment of a private network using integration with a trusted backup network in accordance with one or more aspects of the present disclosure. The device1405may be an example of aspects of a device1305or a gateway function as described herein. The device1405may include a receiver1410, a transmitter1415, and a communications manager1420. The device1405may also include at least one processor. Each of these components may be in communication with one another (e.g., via one or more buses).

The transmitter1415may provide a means for transmitting signals generated by other components of the device1405. For example, the transmitter1415may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to deployment of a private network using integration with a trusted backup network). In some examples, the transmitter1415may be co-located with a receiver1410in a transceiver module. The transmitter1415may utilize a single antenna or a set of multiple antennas.

The device1405, or various components thereof, may be an example of means for performing various aspects of deployment of a private network using integration with a trusted backup network as described herein. For example, the communications manager1420may include an interface component1425, a connection request component1430, a connection indication component1435, or any combination thereof. The communications manager1420may be an example of aspects of a communications manager1320as described herein. In some examples, the communications manager1420, or various components thereof, may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver1410, the transmitter1415, or both. For example, the communications manager1420may receive information from the receiver1410, send information to the transmitter1415, or be integrated in combination with the receiver1410, the transmitter1415, or both to obtain information, output information, or perform various other operations as described herein.

The communications manager1420may support wireless communication at a gateway function of a first network type in accordance with examples as disclosed herein. The interface component1425is capable of, configured to, or operable to support a means for receiving a first message including a first request to establish, as part of a network integration, an interface between the gateway function of the first network type and a network intelligent controller of a second network type, where the first network type supports communications of a first RAT via unlicensed RF spectrum bands and the second network type supports communications of a second RAT via unlicensed RF spectrum bands, licensed RF spectrum bands, or both, the second RAT different than the first RAT. The connection request component1430is capable of, configured to, or operable to support a means for receiving, based on the network integration and a failed connection between a wireless device and the second network type, a second message including a second request to establish a connection with the wireless device in accordance with the first RAT, the failed connection associated with the second RAT. The connection indication component1435is capable of, configured to, or operable to support a means for transmitting, to the network intelligent controller of the second network type via the interface, a third message indicating that the connection between the gateway function of the first network type and the wireless device is established.

FIG.15shows a block diagram1500of a communications manager1520that supports deployment of a private network using integration with a trusted backup network in accordance with one or more aspects of the present disclosure. The communications manager1520may be an example of aspects of a communications manager1320, a communications manager1420, or both, as described herein. The communications manager1520, or various components thereof, may be an example of means for performing various aspects of deployment of a private network using integration with a trusted backup network as described herein. For example, the communications manager1520may include an interface component1525, a connection request component1530, a connection indication component1535, an identity indication component1540, a resource release component1545, a registration component1550, a KPI component1555, or any combination thereof. Each of these components may communicate, directly or indirectly, with one another (e.g., via one or more buses).

Additionally, or alternatively, the communications manager1520may support wireless communication at a gateway function of a first network type in accordance with examples as disclosed herein. The interface component1525is capable of, configured to, or operable to support a means for receiving a first message including a first request to establish, as part of a network integration, an interface between the gateway function of the first network type and a network intelligent controller of a second network type, where the first network type supports communications of a first RAT via unlicensed RF spectrum bands and the second network type supports communications of a second RAT via unlicensed RF spectrum bands, licensed RF spectrum bands, or both, the second RAT different than the first RAT. The connection request component1530is capable of, configured to, or operable to support a means for receiving, based on the network integration and a failed connection between a wireless device and the second network type, a second message including a second request to establish a connection with the wireless device in accordance with the first RAT, the failed connection associated with the second RAT. The connection indication component1535is capable of, configured to, or operable to support a means for transmitting, to the network intelligent controller of the second network type via the interface, a third message indicating that the connection between the gateway function of the first network type and the wireless device is established.

In some examples, to support receiving the second message, the identity indication component1540is capable of, configured to, or operable to support a means for receiving an indication of a GUTI, an IMSI, a SUPI, PLMN ID, NSAI, or any combination thereof associated with the wireless device.

In some examples, to support receiving the second message, the identity indication component1540is capable of, configured to, or operable to support a means for receiving an early access protocol message that indicates an ID of the wireless device and indicates the second request to establish the connection with the wireless device.

In some examples, the identity indication component1540is capable of, configured to, or operable to support a means for transmitting, via the third message based on establishing the connection with the wireless device, an ID of the wireless device and an ID of an AP associated with the first network type.

In some examples, the interface component1525is capable of, configured to, or operable to support a means for establishing a second interface between the gateway function of the first network type and a second network intelligent controller of the second network type.

In some examples, the registration component1550is capable of, configured to, or operable to support a means for monitoring a registration between the wireless device and the second network type. In some examples, the registration component1550is capable of, configured to, or operable to support a means for transmitting, via the second interface, a fourth message that indicates the registration between the wireless device and the second network type is successful, where the fourth message includes an ID of the wireless device and an ID of an AP associated with the first network type.

In some examples, the KPI component1555is capable of, configured to, or operable to support a means for measuring one or more KPIs associated with a second connection between the wireless device and the second network type. In some examples, the KPI component1555is capable of, configured to, or operable to support a means for transmitting, via the second interface and in accordance with a periodicity, an indication of the one or more KPIs.

In some examples, the KPI component1555is capable of, configured to, or operable to support a means for receiving, via the second interface, an indication that values of the one or more KPIs exceed a threshold, where the indication includes a trigger to disable the connection between the wireless device and the gateway function. In some examples, the connection indication component1535is capable of, configured to, or operable to support a means for disabling the connection between the wireless device and the gateway function based on the indication. In some examples, the interface component1525is capable of, configured to, or operable to support a means for disabling the interface and the second interface based on the indication.

In some examples, the resource release component1545is capable of, configured to, or operable to support a means for receiving a resource release request based on a quality of a second connection between the wireless device and the second network type exceeding a threshold quality. In some examples, the resource release component1545is capable of, configured to, or operable to support a means for disabling the connection between the gateway function of the first network type and the wireless device based on the resource release request. In some examples, the resource release component1545is capable of, configured to, or operable to support a means for transmitting, based on disabling the connection, an acknowledgment message responsive to the resource release request.

In some examples, the registration component1550is capable of, configured to, or operable to support a means for monitoring a registration between the wireless device and the second network type. In some examples, the registration component1550is capable of, configured to, or operable to support a means for transmitting, via the interface, a fourth message indicating that the registration between the wireless device and the second network type failed, where the fourth message includes an ID of the wireless device and an ID of an AP associated with the first network type.

In some examples, the first network type includes a trusted non-third generation partnership project (3GPP) network and the second network type includes a 3GPP network.

FIG.16shows a diagram of a system1600including a device1605that supports deployment of a private network using integration with a trusted backup network in accordance with one or more aspects of the present disclosure. The device1605may be an example of or include the components of a device1305, a device1405, or a gateway function as described herein. The device1605may include components for bi-directional voice and data communications including components for transmitting and receiving communications, such as a communications manager1620, an I/O controller1610, a transceiver1615, an antenna1625, at least one memory1630, code1635, and at least one processor1640. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus1645).

The I/O controller1610may manage input and output signals for the device1605. The I/O controller1610may also manage peripherals not integrated into the device1605. In some cases, the I/O controller1610may represent a physical connection or port to an external peripheral. In some cases, the I/O controller1610may utilize an operating system such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS/2®, UNIX®, LINUX®, or another known operating system. Additionally, or alternatively, the I/O controller1610may represent or interact with a modem, a keyboard, a mouse, a touchscreen, or a similar device. In some cases, the I/O controller1610may be implemented as part of at least one processor, such as the at least one processor1640. In some cases, a user may interact with the device1605via the I/O controller1610or via hardware components controlled by the I/O controller1610.

In some cases, the device1605may include a single antenna1625. However, in some other cases, the device1605may have more than one antenna1625, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver1615may communicate bi-directionally, via the one or more antennas1625, wired, or wireless links as described herein. For example, the transceiver1615may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver1615may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas1625for transmission, and to demodulate packets received from the one or more antennas1625. The transceiver1615, or the transceiver1615and one or more antennas1625, may be an example of a transmitter1315, a transmitter1415, a receiver1310, a receiver1410, or any combination thereof or component thereof, as described herein.

The at least one memory1630may include RAM and ROM. The at least one memory1630may store computer-readable, computer-executable code1635including instructions that, when executed by the at least one processor1640, cause the device1605to perform various functions described herein. The code1635may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, the code1635may not be directly executable by the at least one processor1640but may cause a computer (e.g., when compiled and executed) to perform functions described herein. In some cases, the at least one memory1630may contain, among other things, a BIOS which may control basic hardware or software operation such as the interaction with peripheral components or devices.

The at least one processor1640may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the at least one processor1640may be configured to operate at least one memory array using at least one memory controller. In some other cases, at least one memory controller may be integrated into the at least one processor1640. The at least one processor1640may be configured to execute computer-readable instructions stored in at least one memory (e.g., the at least one memory1630) to cause the device1605to perform various functions (e.g., functions or tasks supporting deployment of a private network using integration with a trusted backup network). For example, the device1605or a component of the device1605may include at least one processor1640and memory1630coupled with or to the at least one processor1640, the at least one processor1640and the at least one memory1630configured to perform various functions described herein.

Additionally, or alternatively, the communications manager1620may support wireless communication at a gateway function of a first network type in accordance with examples as disclosed herein. For example, the communications manager1620is capable of, configured to, or operable to support a means for receiving a first message including a first request to establish, as part of a network integration, an interface between the gateway function of the first network type and a network intelligent controller of a second network type, where the first network type supports communications of a first RAT via unlicensed RF spectrum bands and the second network type supports communications of a second RAT via unlicensed RF spectrum bands, licensed RF spectrum bands, or both, the second RAT different than the first RAT. The communications manager1620is capable of, configured to, or operable to support a means for receiving, based on the network integration and a failed connection between a wireless device and the second network type, a second message including a second request to establish a connection with the wireless device in accordance with the first RAT, the failed connection associated with the second RAT. The communications manager1620is capable of, configured to, or operable to support a means for transmitting, to the network intelligent controller of the second network type via the interface, a third message indicating that the connection between the gateway function of the first network type and the wireless device is established.

By including or configuring the communications manager1620in accordance with examples as described herein, the device1605may support techniques for improved communication reliability, improved user experience related to reduced processing, reduced power consumption, and more efficient utilization of communication resources during deployment of a network, among other possibilities.

In some examples, the communications manager1620may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the transceiver1615, the one or more antennas1625, or any combination thereof. Although the communications manager1620is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager1620may be supported by or performed by the at least one processor1640, the at least one memory1630, the code1635, or any combination thereof. For example, the code1635may include instructions executable by the at least one processor1640to cause the device1605to perform various aspects of deployment of a private network using integration with a trusted backup network as described herein, or the at least one processor1640and the at least one memory1630may be otherwise configured to perform or support such operations.

FIG.17shows a block diagram1700of a device1705that supports deployment of a private network using integration with a trusted backup network in accordance with one or more aspects of the present disclosure. The device1705may be an example of aspects of a network intelligent controller as described herein. The device1705may include a receiver1710, a transmitter1715, and a communications manager1720. The device1705may also include at least one processor. Each of these components may be in communication with one another (e.g., via one or more buses).

The transmitter1715may provide a means for outputting (e.g., transmitting, providing, conveying, sending) information generated by other components of the device1705. For example, the transmitter1715may output information such as user data, control information, or any combination thereof (e.g., I/Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). In some examples, the transmitter1715may support outputting information by transmitting signals via one or more antennas. Additionally, or alternatively, the transmitter1715may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter1715and the receiver1710may be co-located in a transceiver, which may include or be coupled with a modem.

The communications manager1720, the receiver1710, the transmitter1715, or various combinations thereof or various components thereof may be examples of means for performing various aspects of deployment of a private network using integration with a trusted backup network as described herein. For example, the communications manager1720, the receiver1710, the transmitter1715, or various combinations or components thereof may support a method for performing one or more of the functions described herein.

In some examples, the communications manager1720, the receiver1710, the transmitter1715, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry). The hardware may include at least one processor, a DSP, a CPU, an ASIC, an FPGA or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure. In some examples, at least one processor and at least one memory coupled with the at least one processor may be configured to perform one or more of the functions described herein (e.g., by executing, by the at least one processor, instructions stored in the at least one memory).

In some examples, the communications manager1720may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver1710, the transmitter1715, or both. For example, the communications manager1720may receive information from the receiver1710, send information to the transmitter1715, or be integrated in combination with the receiver1710, the transmitter1715, or both to obtain information, output information, or perform various other operations as described herein.

Additionally, or alternatively, the communications manager1720may support wireless communication at a network intelligent controller of a second network type in accordance with examples as disclosed herein. For example, the communications manager1720is capable of, configured to, or operable to support a means for transmitting a first message including a request to establish, as part of a network integration, an interface between the network intelligent controller of the second network type and a gateway function of a first network type, where the first network type supports communications of a first RAT via unlicensed RF spectrum bands and the second network type supports communications of a second RAT via unlicensed RF spectrum bands, licensed RF spectrum bands, or both, the second RAT different than the first RAT. The communications manager1720is capable of, configured to, or operable to support a means for receiving, via the interface, a second message indicating that a connection between the gateway function of the first network type and a wireless device is established in accordance with the first RAT, the connection between the gateway function and the wireless device established based on a failed connection between the wireless device and the second network type, the failed connection associated with the second RAT. The communications manager1720is capable of, configured to, or operable to support a means for performing a communication management operation for one or more RAN components of the second network type based on the second message.

Additionally, or alternatively, the communications manager1720may support wireless communication at a network intelligent controller of a second network type in accordance with examples as disclosed herein. For example, the communications manager1720is capable of, configured to, or operable to support a means for establishing, as part of a network integration, an interface between the network intelligent controller and a gateway function of a first network type, where the first network type supports communications of a first RAT via unlicensed RF spectrum bands and the second network type supports communications of a second RAT via unlicensed RF spectrum bands, licensed RF spectrum bands, or both, the second RAT different than the first RAT. The communications manager1720is capable of, configured to, or operable to support a means for receiving, periodically via the interface, an indication of one or more KPIs associated with a connection between a wireless device and the second network type. The communications manager1720is capable of, configured to, or operable to support a means for performing, based on the one or more KPIs, a communication management operation for one or more network entities of the second network type.

By including or configuring the communications manager1720in accordance with examples as described herein, the device1705(e.g., at least one processor controlling or otherwise coupled with the receiver1710, the transmitter1715, the communications manager1720, or a combination thereof) may support techniques for reduced processing, reduced power consumption, and more efficient utilization of communication resources during deployment of a network, among other possibilities.

FIG.18shows a block diagram1800of a device1805that supports deployment of a private network using integration with a trusted backup network in accordance with one or more aspects of the present disclosure. The device1805may be an example of aspects of a device1705or a network intelligent controller as described herein. The device1805may include a receiver1810, a transmitter1815, and a communications manager1820. The device1805may also include at least one processor. Each of these components may be in communication with one another (e.g., via one or more buses).

The transmitter1815may provide a means for outputting (e.g., transmitting, providing, conveying, sending) information generated by other components of the device1805. For example, the transmitter1815may output information such as user data, control information, or any combination thereof (e.g., I/Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). In some examples, the transmitter1815may support outputting information by transmitting signals via one or more antennas. Additionally, or alternatively, the transmitter1815may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter1815and the receiver1810may be co-located in a transceiver, which may include or be coupled with a modem.

The device1805, or various components thereof, may be an example of means for performing various aspects of deployment of a private network using integration with a trusted backup network as described herein. For example, the communications manager1820may include an interface component1825, a connection indication component1830, a communication management component1835, a KPI component1840, or any combination thereof. The communications manager1820may be an example of aspects of a communications manager1720as described herein. In some examples, the communications manager1820, or various components thereof, may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver1810, the transmitter1815, or both. For example, the communications manager1820may receive information from the receiver1810, send information to the transmitter1815, or be integrated in combination with the receiver1810, the transmitter1815, or both to obtain information, output information, or perform various other operations as described herein.

The communications manager1820may support wireless communication at a network intelligent controller of a second network type in accordance with examples as disclosed herein. The interface component1825is capable of, configured to, or operable to support a means for transmitting a first message including a request to establish, as part of a network integration, an interface between the network intelligent controller of the second network type and a gateway function of a first network type, where the first network type supports communications of a first RAT via unlicensed RF spectrum bands and the second network type supports communications of a second RAT via unlicensed RF spectrum bands, licensed RF spectrum bands, or both, the second RAT different than the first RAT. The connection indication component1830is capable of, configured to, or operable to support a means for receiving, via the interface, a second message indicating that a connection between the gateway function of the first network type and a wireless device is established in accordance with the first RAT, the connection between the gateway function and the wireless device established based on a failed connection between the wireless device and the second network type, the failed connection associated with the second RAT. The communication management component1835is capable of, configured to, or operable to support a means for performing a communication management operation for one or more RAN components of the second network type based on the second message.

Additionally, or alternatively, the communications manager1820may support wireless communication at a network intelligent controller of a second network type in accordance with examples as disclosed herein. The interface component1825is capable of, configured to, or operable to support a means for establishing, as part of a network integration, an interface between the network intelligent controller and a gateway function of a first network type, where the first network type supports communications of a first RAT via unlicensed RF spectrum bands and the second network type supports communications of a second RAT via unlicensed RF spectrum bands, licensed RF spectrum bands, or both, the second RAT different than the first RAT. The KPI component1840is capable of, configured to, or operable to support a means for receiving, periodically via the interface, an indication of one or more KPIs associated with a connection between a wireless device and the second network type. The communication management component1835is capable of, configured to, or operable to support a means for performing, based on the one or more KPIs, a communication management operation for one or more network entities of the second network type.

FIG.19shows a block diagram1900of a communications manager1920that supports deployment of a private network using integration with a trusted backup network in accordance with one or more aspects of the present disclosure. The communications manager1920may be an example of aspects of a communications manager1720, a communications manager1820, or both, as described herein. The communications manager1920, or various components thereof, may be an example of means for performing various aspects of deployment of a private network using integration with a trusted backup network as described herein. For example, the communications manager1920may include an interface component1925, a connection indication component1930, a communication management component1935, a KPI component1940, a registration component1945, a connection establishment component1950, a parameter modification component1955, or any combination thereof. Each of these components may communicate, directly or indirectly, with one another (e.g., via one or more buses).

Additionally, or alternatively, the communications manager1920may support wireless communication at a network intelligent controller of a second network type in accordance with examples as disclosed herein. The interface component1925is capable of, configured to, or operable to support a means for transmitting a first message including a request to establish, as part of a network integration, an interface between the network intelligent controller of the second network type and a gateway function of a first network type, where the first network type supports communications of a first RAT via unlicensed RF spectrum bands and the second network type supports communications of a second RAT via unlicensed RF spectrum bands, licensed RF spectrum bands, or both, the second RAT different than the first RAT. The connection indication component1930is capable of, configured to, or operable to support a means for receiving, via the interface, a second message indicating that a connection between the gateway function of the first network type and a wireless device is established in accordance with the first RAT, the connection between the gateway function and the wireless device established based on a failed connection between the wireless device and the second network type, the failed connection associated with the second RAT. The communication management component1935is capable of, configured to, or operable to support a means for performing a communication management operation for one or more RAN components of the second network type based on the second message.

In some examples, the registration component1945is capable of, configured to, or operable to support a means for receiving, via the interface, a third message indicating that a registration between the wireless device and the second network type failed, where the third message includes an ID of the wireless device and an ID of an AP associated with the first network type.

In some examples, the communication management component1935is capable of, configured to, or operable to support a means for performing a second communication management operation for the one or more RAN components of the second network type based on the third message.

In some examples, the connection indication component1930is capable of, configured to, or operable to support a means for transmitting, to one or more network entities of the second network type based on the second message, a control request that indicates the connection between the gateway function and the wireless device is established, where the control request indicates one or more network optimization parameters associated with the communication management operation.

In some examples, the connection establishment component1950is capable of, configured to, or operable to support a means for establishing, before receiving the second message, a first connection with the wireless device via the second network type in accordance with the second RAT, where the connection between the gateway function and the wireless device is based on a failure of the first connection.

In some examples, to support performing the communication management operation, the parameter modification component1955is capable of, configured to, or operable to support a means for modifying an allocation of one or more radio resources within the second network type. In some examples, to support performing the communication management operation, the parameter modification component1955is capable of, configured to, or operable to support a means for modifying one or more parameters associated with radio access control for the second network type. In some examples, to support performing the communication management operation, the parameter modification component1955is capable of, configured to, or operable to support a means for modifying one or more parameters associated with a connection management for the second network type. In some examples, to support performing the communication management operation, the parameter modification component1955is capable of, configured to, or operable to support a means for modifying one or more parameters associated with a mobility management for the second network type.

In some examples, the first network type includes a trusted non-3GPP network and the second network type includes a 3GPP network.

In some examples, the network intelligent controller includes a near-RT intelligent controller of a network entity of the second network type.

Additionally, or alternatively, the communications manager1920may support wireless communication at a network intelligent controller of a second network type in accordance with examples as disclosed herein. In some examples, the interface component1925is capable of, configured to, or operable to support a means for establishing, as part of a network integration, an interface between the network intelligent controller and a gateway function of a first network type, where the first network type supports communications of a first RAT via unlicensed RF spectrum bands and the second network type supports communications of a second RAT via unlicensed RF spectrum bands, licensed RF spectrum bands, or both, the second RAT different than the first RAT. The KPI component1940is capable of, configured to, or operable to support a means for receiving, periodically via the interface, an indication of one or more KPIs associated with a connection between a wireless device and the second network type. In some examples, the communication management component1935is capable of, configured to, or operable to support a means for performing, based on the one or more KPIs, a communication management operation for one or more network entities of the second network type.

In some examples, the registration component1945is capable of, configured to, or operable to support a means for receiving, via the interface, a message that indicates a successful registration between the wireless device and the second network type, where the message includes an ID of the wireless device and an ID of an AP associated with the first network type, and where periodically receiving the indication of the one or more KPIs is based on the successful registration.

In some examples, the KPI component1940is capable of, configured to, or operable to support a means for transmitting, via the interface, an indication that values of the one or more KPIs exceed a threshold, where the indication includes a trigger to disable a second connection between the wireless device and the gateway function of the first network type.

In some examples, to support performing the communication management operation, the KPI component1940is capable of, configured to, or operable to support a means for modifying one or more corrective network orchestration and optimization decisions for the one or more network entities of the second network type based on the one or more KPIs.

In some examples, the first network type includes a trusted non-third generation partnership project (3GPP) network and the second network type includes a 3GPP network.

In some examples, the network intelligent controller includes a non-RT intelligent controller of a network entity of the second network type.

FIG.20shows a diagram of a system2000including a device2005that supports deployment of a private network using integration with a trusted backup network in accordance with one or more aspects of the present disclosure. The device2005may be an example of or include the components of a device1705, a device1805, or a network intelligent controller as described herein. The device2005may include components for bi-directional voice and data communications including components for transmitting and receiving communications, such as a communications manager2020, a transceiver2010, an antenna2015, at least one memory2025, code2030, and at least one processor2035. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus2040).

The transceiver2010may support bi-directional communications via wired links, wireless links, or both as described herein. In some examples, the transceiver2010may include a wired transceiver and may communicate bi-directionally with another wired transceiver. Additionally, or alternatively, in some examples, the transceiver2010may include a wireless transceiver and may communicate bi-directionally with another wireless transceiver. In some examples, the device2005may include one or more antennas2015, which may be capable of transmitting or receiving wireless transmissions (e.g., concurrently). The transceiver2010may also include a modem to modulate signals, to provide the modulated signals for transmission (e.g., by one or more antennas2015, by a wired transmitter), to receive modulated signals (e.g., from one or more antennas2015, from a wired receiver), and to demodulate signals. In some implementations, the transceiver2010may include one or more interfaces, such as one or more interfaces coupled with the one or more antennas2015that are configured to support various receiving or obtaining operations, or one or more interfaces coupled with the one or more antennas2015that are configured to support various transmitting or outputting operations, or a combination thereof. In some implementations, the transceiver2010may include or be configured for coupling with one or more processors or memory components that are operable to perform or support operations based on received or obtained information or signals, or to generate information or other signals for transmission or other outputting, or any combination thereof. In some implementations, the transceiver2010, or the transceiver2010and the one or more antennas2015, or the transceiver2010and the one or more antennas2015and one or more processors or memory components (for example, the at least one processor2035, or the at least one memory2025, or both), may be included in a chip or chip assembly that is installed in the device2005. In some examples, the transceiver may be operable to support communications via one or more communications links (e.g., a communication link125, a backhaul communication link120, a midhaul communication link162, a fronthaul communication link168).

The at least one memory2025may include RAM and ROM. The at least one memory2025may store computer-readable, computer-executable code2030including instructions that, when executed by the at least one processor2035, cause the device2005to perform various functions described herein. The code2030may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, the code2030may not be directly executable by the at least one processor2035but may cause a computer (e.g., when compiled and executed) to perform functions described herein. In some cases, the at least one memory2025may contain, among other things, a BIOS which may control basic hardware or software operation such as the interaction with peripheral components or devices.

The at least one processor2035may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA, a microcontroller, a programmable logic device, discrete gate or transistor logic, a discrete hardware component, or any combination thereof). In some cases, the at least one processor2035may be configured to operate at least one memory array using at least one memory controller. In some other cases, at least one memory controller may be integrated into the at least one processor2035. The at least one processor2035may be configured to execute computer-readable instructions stored in at least one memory (e.g., the at least one memory2025) to cause the device2005to perform various functions (e.g., functions or tasks supporting deployment of a private network using integration with a trusted backup network). For example, the device2005or a component of the device2005may include at least one processor2035and at least one memory2025coupled with the at least one processor2035, the at least one processor2035and the at least one memory2025configured to perform various functions described herein. The at least one processor2035may be an example of a cloud-computing platform (e.g., one or more physical nodes and supporting software such as operating systems, virtual machines, or container instances) that may host the functions (e.g., by executing code2030) to perform the functions of the device2005. The at least one processor2035may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in the device2005(such as within the at least one memory2025). In some implementations, the at least one processor2035may be a component of a processing system. A processing system may generally refer to a system or series of machines or components that receives inputs and processes the inputs to produce a set of outputs (which may be passed to other systems or components of, for example, the device2005). For example, a processing system of the device2005may refer to a system including the various other components or subcomponents of the device2005, such as the at least one processor2035, or the transceiver2010, or the communications manager2020, or other components or combinations of components of the device2005. The processing system of the device2005may interface with other components of the device2005, and may process information received from other components (such as inputs or signals) or output information to other components. For example, a chip or modem of the device2005may include a processing system and one or more interfaces to output information, or to obtain information, or both. The one or more interfaces may be implemented as or otherwise include a first interface configured to output information and a second interface configured to obtain information, or a same interface configured to output information and to obtain information, among other implementations. In some implementations, the one or more interfaces may refer to an interface between the processing system of the chip or modem and a transmitter, such that the device2005may transmit information output from the chip or modem. Additionally, or alternatively, in some implementations, the one or more interfaces may refer to an interface between the processing system of the chip or modem and a receiver, such that the device2005may obtain information or signal inputs, and the information may be passed to the processing system. A person having ordinary skill in the art will readily recognize that a first interface also may obtain information or signal inputs, and a second interface also may output information or signal outputs.

In some examples, a bus2040may support communications of (e.g., within) a protocol layer of a protocol stack. In some examples, a bus2040may support communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communications performed within a component of the device2005, or between different components of the device2005that may be co-located or located in different locations (e.g., where the device2005may refer to a system in which one or more of the communications manager2020, the transceiver2010, the at least one memory2025, the code2030, and the at least one processor2035may be located in one of the different components or divided between different components).

Additionally, or alternatively, the communications manager2020may support wireless communication at a network intelligent controller of a second network type in accordance with examples as disclosed herein. For example, the communications manager2020is capable of, configured to, or operable to support a means for transmitting a first message including a request to establish, as part of a network integration, an interface between the network intelligent controller of the second network type and a gateway function of a first network type, where the first network type supports communications of a first RAT via unlicensed RF spectrum bands and the second network type supports communications of a second RAT via unlicensed RF spectrum bands, licensed RF spectrum bands, or both, the second RAT different than the first RAT. The communications manager2020is capable of, configured to, or operable to support a means for receiving, via the interface, a second message indicating that a connection between the gateway function of the first network type and a wireless device is established in accordance with the first RAT, the connection between the gateway function and the wireless device established based on a failed connection between the wireless device and the second network type, the failed connection associated with the second RAT. The communications manager2020is capable of, configured to, or operable to support a means for performing a communication management operation for one or more RAN components of the second network type based on the second message.

Additionally, or alternatively, the communications manager2020may support wireless communication at a network intelligent controller of a second network type in accordance with examples as disclosed herein. For example, the communications manager2020is capable of, configured to, or operable to support a means for establishing, as part of a network integration, an interface between the network intelligent controller and a gateway function of a first network type, where the first network type supports communications of a first RAT via unlicensed RF spectrum bands and the second network type supports communications of a second RAT via unlicensed RF spectrum bands, licensed RF spectrum bands, or both, the second RAT different than the first RAT. The communications manager2020is capable of, configured to, or operable to support a means for receiving, periodically via the interface, an indication of one or more KPIs associated with a connection between a wireless device and the second network type. The communications manager2020is capable of, configured to, or operable to support a means for performing, based on the one or more KPIs, a communication management operation for one or more network entities of the second network type.

By including or configuring the communications manager2020in accordance with examples as described herein, the device2005may support techniques for improved communication reliability, improved user experience related to reduced processing, reduced power consumption, and more efficient utilization of communication resources during deployment of a network, among other possibilities.

In some examples, the communications manager2020may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the transceiver2010, the one or more antennas2015(e.g., where applicable), or any combination thereof. Although the communications manager2020is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager2020may be supported by or performed by the transceiver2010, the at least one processor2035, the at least one memory2025, the code2030, or any combination thereof. For example, the code2030may include instructions executable by the at least one processor2035to cause the device2005to perform various aspects of deployment of a private network using integration with a trusted backup network as described herein, or the at least one processor2035and the at least one memory2025may be otherwise configured to perform or support such operations.

FIG.21shows a flowchart illustrating a method2100that supports deployment of a private network using integration with a trusted backup network in accordance with aspects of the present disclosure. The operations of the method2100may be implemented by a gateway function or its components as described herein. For example, the operations of the method2100may be performed by a gateway function as described with reference toFIGS.1through16. In some examples, a gateway function may execute a set of instructions to control the functional elements of the gateway function to perform the described functions. Additionally, or alternatively, the gateway function may perform aspects of the described functions using special-purpose hardware.

At2105, the method may include receiving a first message including a first request to establish, as part of a network integration, an interface between the gateway function of the first network type and a network intelligent controller of a second network type, where the first network type supports communications of a first RAT via unlicensed RF spectrum bands and the second network type supports communications of a second RAT via unlicensed RF spectrum bands, licensed RF spectrum bands, or both, the second RAT different than the first RAT. The operations of block2105may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of2105may be performed by an interface component1525as described with reference toFIG.15.

At2110, the method may include receiving, based on the network integration and a failed connection between a wireless device and the second network type, a second message including a second request to establish a connection with the wireless device in accordance with the first RAT, the failed connection associated with the second RAT. The operations of block2110may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of2110may be performed by a connection request component1530as described with reference toFIG.15.

At2115, the method may include transmitting, to the network intelligent controller of the second network type via the interface, a third message indicating that the connection between the gateway function of the first network type and the wireless device is established. The operations of block2115may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of2115may be performed by a connection indication component1535as described with reference toFIG.15.

FIG.22shows a flowchart illustrating a method2200that supports deployment of a private network using integration with a trusted backup network in accordance with aspects of the present disclosure. The operations of the method2200may be implemented by a gateway function or its components as described herein. For example, the operations of the method2200may be performed by a gateway function as described with reference toFIGS.1through16. In some examples, a gateway function may execute a set of instructions to control the functional elements of the gateway function to perform the described functions. Additionally, or alternatively, the gateway function may perform aspects of the described functions using special-purpose hardware.

At2205, the method may include receiving a first message including a first request to establish, as part of a network integration, an interface between the gateway function of the first network type and a network intelligent controller of a second network type, where the first network type supports communications of a first RAT via unlicensed RF spectrum bands and the second network type supports communications of a second RAT via unlicensed RF spectrum bands, licensed RF spectrum bands, or both, the second RAT different than the first RAT. The operations of block2205may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of2205may be performed by an interface component1525as described with reference toFIG.15.

At2210, the method may include receiving, based on the network integration and a failed connection between a wireless device and the second network type, a second message including a second request to establish a connection with the wireless device in accordance with the first RAT, the failed connection associated with the second RAT. The operations of block2210may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of2210may be performed by a connection request component1530as described with reference toFIG.15.

At2215, the method may include transmitting, to the network intelligent controller of the second network type via the interface, a third message indicating that the connection between the gateway function of the first network type and the wireless device is established. The operations of block2215may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of2215may be performed by a connection indication component1535as described with reference toFIG.15.

At2220, the method may include establishing a second interface between the gateway function of the first network type and a second network intelligent controller of the second network type. The operations of block2220may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of2220may be performed by an interface component1525as described with reference toFIG.15.

FIG.23shows a flowchart illustrating a method2300that supports deployment of a private network using integration with a trusted backup network in accordance with aspects of the present disclosure. The operations of the method2300may be implemented by a network intelligent controller or its components as described herein. For example, the operations of the method2300may be performed by a network intelligent controller as described with reference toFIGS.1through12and17through20. In some examples, a network intelligent controller may execute a set of instructions to control the functional elements of the network intelligent controller to perform the described functions. Additionally, or alternatively, the network intelligent controller may perform aspects of the described functions using special-purpose hardware.

At2305, the method may include transmitting a first message including a request to establish, as part of a network integration, an interface between the network intelligent controller of the second network type and a gateway function of a first network type, where the first network type supports communications of a first RAT via unlicensed RF spectrum bands and the second network type supports communications of a second RAT via unlicensed RF spectrum bands, licensed RF spectrum bands, or both, the second RAT different than the first RAT. The operations of block2305may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of2305may be performed by an interface component1925as described with reference toFIG.19.

At2310, the method may include receiving, via the interface, a second message indicating that a connection between the gateway function of the first network type and a wireless device is established in accordance with the first RAT, the connection between the gateway function and the wireless device established based on a failed connection between the wireless device and the second network type, the failed connection associated with the second RAT. The operations of block2310may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of2310may be performed by a connection indication component1930as described with reference toFIG.19.

At2315, the method may include performing a communication management operation for one or more RAN components of the second network type based on the second message. The operations of block2315may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of2315may be performed by a communication management component1935as described with reference toFIG.19.

FIG.24shows a flowchart illustrating a method2400that supports deployment of a private network using integration with a trusted backup network in accordance with aspects of the present disclosure. The operations of the method2400may be implemented by a network intelligent controller or its components as described herein. For example, the operations of the method2400may be performed by a network intelligent controller as described with reference toFIGS.1through12and17through20. In some examples, a network intelligent controller may execute a set of instructions to control the functional elements of the network intelligent controller to perform the described functions. Additionally, or alternatively, the network intelligent controller may perform aspects of the described functions using special-purpose hardware.

At2405, the method may include establishing, as part of a network integration, an interface between the network intelligent controller and a gateway function of a first network type, where the first network type supports communications of a first RAT via unlicensed RF spectrum bands and the second network type supports communications of a second RAT via unlicensed RF spectrum bands, licensed RF spectrum bands, or both, the second RAT different than the first RAT. The operations of block2405may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of2405may be performed by an interface component1925as described with reference toFIG.19.

At2410, the method may include receiving, periodically via the interface, an indication of one or more KPIs associated with a connection between a wireless device and the second network type. The operations of block2410may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of2410may be performed by a KPI component1940as described with reference toFIG.19.

At2415, the method may include performing, based on the one or more KPIs, a communication management operation for one or more network entities of the second network type. The operations of block2415may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of2415may be performed by a communication management component1935as described with reference toFIG.19.

FIG.25shows a flowchart illustrating a method2500that supports deployment of a private network using integration with a trusted backup network in accordance with aspects of the present disclosure. The operations of the method2500may be implemented by a network intelligent controller or its components as described herein. For example, the operations of the method2500may be performed by a network intelligent controller as described with reference toFIGS.1through12and17through20. In some examples, a network intelligent controller may execute a set of instructions to control the functional elements of the network intelligent controller to perform the described functions. Additionally, or alternatively, the network intelligent controller may perform aspects of the described functions using special-purpose hardware.

At2505, the method may include establishing, as part of a network integration, an interface between the network intelligent controller and a gateway function of a first network type, where the first network type supports communications of a first RAT via unlicensed RF spectrum bands and the second network type supports communications of a second RAT via unlicensed RF spectrum bands, licensed RF spectrum bands, or both, the second RAT different than the first RAT. The operations of block2505may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of2505may be performed by an interface component1925as described with reference toFIG.19.

At2510, the method may include receiving, via the interface, a message that indicates a successful registration between the wireless device and the second network type, where the message includes an ID of the wireless device and an ID of an AP associated with the first network type. The operations of block2510may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of2510may be performed by a registration component1945as described with reference toFIG.19.

At2515, the method may include receiving, periodically via the interface, an indication of one or more KPIs associated with a connection between a wireless device and the second network type, where periodically receiving the indication of the one or more KPIs is based on the successful registration. The operations of block2515may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of2515may be performed by a KPI component1940as described with reference toFIG.19.

At2520, the method may include performing, based on the one or more KPIs, a communication management operation for one or more network entities of the second network type. The operations of block2520may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of2520may be performed by a communication management component1935as described with reference toFIG.19.

Aspect 1: A method for wireless communication at a gateway function of a first network type, comprising: receiving a first message comprising a first request to establish, as part of a network integration, an interface between the gateway function of the first network type and a network intelligent controller of a second network type, wherein the first network type supports communications of a first RAT via unlicensed RF spectrum bands and the second network type supports communications of a second RAT via unlicensed RF spectrum bands, licensed RF spectrum bands, or both, the second RAT different than the first RAT; receiving, based at least in part on the network integration and a failed connection between a wireless device and the second network type, a second message comprising a second request to establish a connection with the wireless device in accordance with the first RAT, the failed connection associated with the second RAT; and transmitting, to the network intelligent controller of the second network type via the interface, a third message indicating that the connection between the gateway function of the first network type and the wireless device is established.

Aspect 2: The method of aspect 1, wherein receiving the second message comprises: receiving an indication of a GUTI, an IMSI, a SUPI, PLMN ID, NSAI, or any combination thereof associated with the wireless device.

Aspect 3: The method of any of aspects 1 through 2, wherein receiving the second message comprises: receiving an EAP message that indicates an ID of the wireless device and indicates the second request to establish the connection with the wireless device.

Aspect 4: The method of any of aspects 1 through 3, further comprising: transmitting, via the third message based at least in part on establishing the connection with the wireless device, an ID of the wireless device and an ID of an AP associated with the first network type.

Aspect 5: The method of any of aspects 1 through 4, further comprising: establishing a second interface between the gateway function of the first network type and a second network intelligent controller of the second network type.

Aspect 6: The method of aspect 5, further comprising: monitoring a registration between the wireless device and the second network type; and transmitting, via the second interface, a fourth message that indicates the registration between the wireless device and the second network type is successful, wherein the fourth message comprises an ID of the wireless device and an ID of an AP associated with the first network type.

Aspect 7: The method of any of aspects 5 through 6, further comprising: measuring one or more KPIs associated with a second connection between the wireless device and the second network type; and transmitting, via the second interface and in accordance with a periodicity, an indication of the one or more KPIs.

Aspect 8: The method of aspect 7, further comprising: receiving, via the second interface, an indication that values of the one or more KPIs exceed a threshold, wherein the indication comprises a trigger to disable the connection between the wireless device and the gateway function; disabling the connection between the wireless device and the gateway function based at least in part on the indication; and disabling the interface and the second interface based at least in part on the indication.

Aspect 9: The method of any of aspects 1 through 8, further comprising: receiving a resource release request based at least in part on a quality of a second connection between the wireless device and the second network type exceeding a threshold quality; disabling the connection between the gateway function of the first network type and the wireless device based at least in part on the resource release request; and transmitting, based at least in part on disabling the connection, an acknowledgment message responsive to the resource release request.

Aspect 10: The method of any of aspects 1 through 9, further comprising: monitoring a registration between the wireless device and the second network type; and transmitting, via the interface, a fourth message indicating that the registration between the wireless device and the second network type failed, wherein the fourth message comprises an ID of the wireless device and an ID of an AP associated with the first network type.

Aspect 11: The method of any of aspects 1 through 10, wherein the first network type comprises a trusted non-3GPP network and the second network type comprises a 3GPP network.

Aspect 12: A method for wireless communication at a network intelligent controller of a second network type, comprising: transmitting a first message comprising a request to establish, as part of a network integration, an interface between the network intelligent controller of the second network type and a gateway function of a first network type, wherein the first network type supports communications of a first RAT via unlicensed RF spectrum bands and the second network type supports communications of a second RAT via unlicensed RF spectrum bands, licensed RF spectrum bands, or both, the second RAT different than the first RAT; receiving, via the interface, a second message indicating that a connection between the gateway function of the first network type and a wireless device is established in accordance with the first RAT, the connection between the gateway function and the wireless device established based at least in part on a failed connection between the wireless device and the second network type, the failed connection associated with the second RAT; and performing a communication management operation for one or more RAN components of the second network type based at least in part on the second message.

Aspect 13: The method of aspect 12, further comprising: receiving, via the interface, a third message indicating that a registration between the wireless device and the second network type failed, wherein the third message comprises an ID of the wireless device and an ID of an AP associated with the first network type.

Aspect 14: The method of aspect 13, further comprising: performing a second communication management operation for the one or more RAN components of the second network type based at least in part on the third message.

Aspect 15: The method of any of aspects 12 through 14, further comprising: transmitting, to one or more network entities of the second network type based at least in part on the second message, a control request that indicates the connection between the gateway function and the wireless device is established, wherein the control request indicates one or more network optimization parameters associated with the communication management operation.

Aspect 16: The method of any of aspects 12 through 15, further comprising: establishing, before receiving the second message, a first connection with the wireless device via the second network type in accordance with the second RAT, wherein the connection between the gateway function and the wireless device is based at least in part on a failure of the first connection.

Aspect 17: The method of any of aspects 12 through 16, wherein performing the communication management operation comprises: modifying an allocation of one or more radio resources within the second network type; modifying one or more parameters associated with radio access control for the second network type; modifying one or more parameters associated with a connection management for the second network type; or modifying one or more parameters associated with a mobility management for the second network type.

Aspect 18: The method of any of aspects 12 through 17, wherein the first network type comprises a trusted non-3GPP network and the second network type comprises a 3GPP network.

Aspect 19: The method of any of aspects 12 through 18, wherein the network intelligent controller comprises a near-RT intelligent controller of a network entity of the second network type.

Aspect 20: A method for wireless communication at a network intelligent controller of a second network type, comprising: establishing, as part of a network integration, an interface between the network intelligent controller and a gateway function of a first network type, wherein the first network type supports communications of a first RAT via unlicensed RF spectrum bands and the second network type supports communications of a second RAT via unlicensed RF spectrum bands, licensed RF spectrum bands, or both, the second RAT different than the first RAT; receiving, periodically via the interface, an indication of one or more KPIs associated with a connection between a wireless device and the second network type; and performing, based at least in part on the one or more KPIs, a communication management operation for one or more network entities of the second network type.

Aspect 21: The method of aspect 20, further comprising: receiving, via the interface, a message that indicates a successful registration between the wireless device and the second network type, wherein the message comprises an ID of the wireless device and an ID of an AP associated with the first network type, and wherein periodically receiving the indication of the one or more KPIs is based at least in part on the successful registration.

Aspect 22: The method of any of aspects 20 through 21, further comprising: transmitting, via the interface, an indication that values of the one or more KPIs exceed a threshold, wherein the indication comprises a trigger to disable a second connection between the wireless device and the gateway function of the first network type.

Aspect 23: The method of any of aspects 20 through 22, wherein performing the communication management operation comprises: modifying one or more corrective network orchestration and optimization decisions for the one or more network entities of the second network type based at least in part on the one or more KPIs.

Aspect 24: The method of any of aspects 20 through 23, wherein the first network type comprises a trusted non-3GPP network and the second network type comprises a 3GPP network.

Aspect 25: The method of any of aspects 20 through 24, wherein the network intelligent controller comprises a non-RT intelligent controller of a network entity of the second network type.

Aspect 26: An apparatus for wireless communication at a gateway function of a first network type, comprising at least one processor; at least one memory coupled with the at least one processor; and instructions stored in the at least one memory and executable by the at least one processor to cause the apparatus to perform a method of any of aspects 1 through 11.

Aspect 27: An apparatus for wireless communication at a gateway function of a first network type, comprising at least one means for performing a method of any of aspects 1 through 11.

Aspect 28: A non-transitory computer-readable medium storing code for wireless communication at a gateway function of a first network type, the code comprising instructions executable by a processor to perform a method of any of aspects 1 through 11.

Aspect 29: An apparatus for wireless communication at a network intelligent controller of a second network type, comprising at least one processor; at least one memory coupled with the at least one processor; and instructions stored in the at least one memory and executable by the at least one processor to cause the apparatus to perform a method of any of aspects 12 through 19.

Aspect 30: An apparatus for wireless communication at a network intelligent controller of a second network type, comprising at least one means for performing a method of any of aspects 12 through 19.

Aspect 31: A non-transitory computer-readable medium storing code for wireless communication at a network intelligent controller of a second network type, the code comprising instructions executable by a processor to perform a method of any of aspects 12 through 19.

Aspect 32: An apparatus for wireless communication at a network intelligent controller of a second network type, comprising at least one processor; at least one memory coupled with the at least one processor; and instructions stored in the at least one memory and executable by the at least one processor to cause the apparatus to perform a method of any of aspects 20 through 25.

Aspect 33: An apparatus for wireless communication at a network intelligent controller of a second network type, comprising at least one means for performing a method of any of aspects 20 through 25.

Aspect 34: A non-transitory computer-readable medium storing code for wireless communication at a network intelligent controller of a second network type, the code comprising instructions executable by a processor to perform a method of any of aspects 20 through 25.