Patent Description:
The wireless communication networks have wireless access nodes which exchange wireless signals with the wireless user devices over radio frequency bands. The wireless signals use wireless network protocols like Fifth Generation New Radio (5GNR), Long Term Evolution (LTE), Institute of Electrical and Electronic Engineers (IEEE) <NUM> (WIFI), and Low-Power Wide Area Network (LP-WAN). The wireless access nodes exchange network signaling and user data with network elements that are often clustered together into wireless network cores. The network elements comprise Access and Mobility Management Functions (AMFs), Session Management Functions (SMFs), Interworking functions (IWFs), User Plane Functions (UPFs), Policy Control Functions (PCFs), Network Exposure Functions (NEFs), and the like.

A wireless network core determines user context to control the wireless data services for a wireless user device. The user context indicates information like user Identifier (ID), device ID, network ID, access node ID, service ID, session ID, and individual session data. The individual session data characterizes items like network address, Access Point Name (APN), Data Network Name (DNN), Slice ID, Quality-of-Service Class Indicator (QCI), Quality-of-Service Flow Indicator (QFI), or some other session parameter. The wireless network cores transfer the user context to the wireless access nodes to control the wireless data services.

As the wireless user devices move about, the wireless access nodes handover the wireless user devices among one another. The wireless user devices detach from their serving wireless access nodes and attach to their target wireless access nodes. Some of the serving wireless access nodes transfer user context to the target wireless access nodes. Unfortunately, some of the wireless access nodes do not effectively transfer the user context. Moreover, the network cores inefficiently re-determine network context after some handovers. "<NPL>, describes handover of a PDU Session procedure from 3GPP to untrusted non-3GPP access.

A wireless communication network hands-in inbound User Equipment (UE) from a source communication network to a non-Third Partnership Project (non-3GPP) access node. In the wireless communication network, a Network Exposure Function (NEF) receives inbound UE context from the source communication network. An Access and Mobility Management Function (AMF) detects when the inbound UE attaches to the non-3GPP access node to hand-in from the source communication network and responsively transfers a UE context request for the inbound UE to the NEF. The NEF transfers the inbound UE context to the AMF in response to the UE context request. The AMF transfers network signaling to one or more network functions to serve the inbound UE based on the inbound UE context.

According to a first aspect of the invention there is provided a method according to claim <NUM>. Optional features are provided at claims <NUM> to <NUM>. According to another aspect of the invention there is provided a wireless communication network according to claim <NUM>. Optional features are provided at claims <NUM> - <NUM>.

<FIG> illustrates wireless communication network <NUM> to handover User Equipment (UE) <NUM> from wireless communication network <NUM> to Non-Third Partnership Project (non-3GPP) access node <NUM> and to handover UE <NUM> from non-3GPP access node <NUM> to wireless communication network <NUM>. UEs <NUM>-<NUM> comprise computers, phones, vehicles, sensors, robots, or some other data appliances with wireless possibly wireline communication circuitry. Wireless communication networks <NUM> and <NUM> deliver services to UEs <NUM>-<NUM> like internet-access, machine-control, media-streaming, or some other data communications product. Wireless communication network <NUM> comprises non-3GPP access node <NUM>, network functions <NUM>, Access and Mobility Management Function (AMF) <NUM>, and Network Exposure Function (NEF) <NUM>.

Various examples of network operation and configuration are described herein. In some examples, UE <NUM> is initially linked to wireless communication network <NUM>, and UE <NUM> is initially linked to wireless communication network <NUM>. UEs <NUM>-<NUM> are moving in opposite directions. Wireless communication network <NUM> determines UE context for UE <NUM> and wirelessly serves UE <NUM> based on the UE context. The UE context indicates information like user Identifier (ID), UE ID, network ID, access node ID, service IDs, session IDs, and individual session data. The individual session data characterizes items like network addresses, Access Point Name (APN), Data Network Name (DNN), Slice ID, Quality-of-Service Class Indicator (QCI), Quality-of-Service Flow Indicator (QFI), or some other information like user Identifier (ID), UE ID, network ID, access node ID, service IDs, session IDs, and individual session data. The individual session data characterizes items like network addresses, Access Point Name (APN), Data Network Name (DNN), Slice ID, Quality-of-Service Class Indicator (QCI), Quality-of-Service Flow Indicator (QFI), or some other session parameter. As UE <NUM> moves away from wireless communication network <NUM> and toward non-3GPP access node <NUM>, UE <NUM> reports the poor signal strength from wireless communication network <NUM> and better signal strength from non-3GPP access node <NUM>. In response to the UE report, wireless communication network <NUM> detects that UE <NUM> is handing-out to non-3GPP access node <NUM> in wireless communication network <NUM>, and in response, wireless communication network <NUM> transfers the UE context to NEF <NUM>. UE <NUM> attaches to non-3GPP access node <NUM> and registers with AMF <NUM> over non-3GPP access node <NUM> and network functions <NUM>. UE <NUM> indicates the UE context to AMF <NUM> during the registration - although the UE context from a UE is not authorized. AMF <NUM> detects that UE <NUM> is handing-in from wireless communication network <NUM> to non-3GPP access node <NUM>, and in response, AMF <NUM> transfers a UE context request for UE <NUM> and network <NUM> to NEF <NUM>. NEF <NUM> transfers the UE context for UE <NUM> and network <NUM> to AMF <NUM> in response to the UE context request. AMF <NUM> processes the UE context and responsively generates network signaling. For example, AMF <NUM> may select a <NUM> network slice based on an LTE QCI. AMF <NUM> transfers the network signaling to network functions <NUM>. Network functions <NUM> serve UE <NUM> based on the network signaling. Network functions <NUM> may transfer corresponding network signaling to non-3GPP access node <NUM>, and node <NUM> may serve UE <NUM> based on the network signaling.

For UE <NUM>, AMF <NUM> determines the UE context and signals the UE context for UE <NUM> to network functions <NUM>. As UE <NUM> moves away from non-3GPP access node <NUM> and toward wireless communication network <NUM>, UE <NUM> reports the poor signal strength from non-3GPP access node <NUM> and better signal strength from wireless communication network <NUM>. In response to the UE report, AMF <NUM> detects that UE <NUM> is handing-out to wireless communication network <NUM>, and in response, AMF <NUM> transfers the UE context to NEF <NUM>. NEF <NUM> transfers the UE context for UE <NUM> to wireless communication network <NUM>. UE <NUM> attaches to and registers with wireless communication network <NUM>. UE <NUM> indicates the UE context to wireless communication network <NUM> during the registration - although UE context from a UE is not authorized. Wireless communication network <NUM> serves UE <NUM> based on the UE context from wireless communication <NUM>.

In some examples, NEF <NUM> receives user instructions for UEs <NUM>-<NUM> from an Application Function (AF) that exerts external control for the user. NEF <NUM> transfers the user instructions for UE <NUM> to AMF <NUM> in response to the UE context request for UE <NUM>. AMF <NUM> transfers the user instructions to UE <NUM> in N1 signaling. NEF <NUM> transfers the user instructions for UE <NUM> to wireless communication network <NUM> in response to delivering the UE context for UE <NUM> to wireless communication network <NUM>.

Advantageously, NEF <NUM> effectively transfers the UE context between wireless communication networks <NUM> and <NUM> in response to handovers using non-3GPP access node <NUM>. Moreover, wireless communication networks <NUM> and <NUM> efficiently re-use the network context after the handovers.

UEs <NUM>-<NUM> communicate with wireless communication networks <NUM> and <NUM> over technologies like Fifth Generation New Radio (5GNR), Long Term Evolution (LTE), Low-Power Wide Area Network (LP-WAN), Institute of Electrical and Electronic Engineers (IEEE) <NUM> (WIFI), IEEE <NUM> (ENET), Bluetooth, Narrowband Internet-of-Things (NB-IoT), Internet Protocol (IP), and/or some other data networking protocol. The wireless communication technologies use electromagnetic frequencies in the low-band, mid-band, high-band, or some other portion of the electromagnetic spectrum. The communication links that support these technologies use metallic links, glass fibers, radio channels, or some other communication media. The communication links use ENET, Time Division Multiplex (TDM), Data Over Cable System Interface Specification (DOCSIS), IP, General Packet Radio Service Transfer Protocol (GTP), 3GPP, 5GNR, LTE, WIFI, IP, virtual switching, inter-processor communication, bus interfaces, and/or some other data communication protocols.

In some examples, non-3GPP access node <NUM> is untrusted, and network functions <NUM> comprise a non-3GPP Interworking Function (IWF) and User Plane Function (UPF). UEs <NUM>-<NUM> communicate with AMF <NUM> over an N1 link that traverses the untrusted access node and the IWF. UEs <NUM>-<NUM> communicate with external systems over an NWu/N3/N6 link that traverses the untrusted access node, IWF, and UPF. In other examples, non-3GPP access node <NUM> comprises a Trusted Network Access Point (TNAP), and network functions <NUM> comprise a Trusted Network Gateway Function (TNGF) and UPF. UEs <NUM>-<NUM> communicate with AMF <NUM> over an N1 link that traverses the TNAP and TNGF. UEs <NUM>-<NUM> communicate with external systems over an NWt/N3/N6 link that traverses the TNAP, TNGF, and UPF.

UEs <NUM>-<NUM>, wireless communication network <NUM>, and non-3GPP access node <NUM> comprise antennas, amplifiers, filters, modulation, analog/digital interfaces, microprocessors, software, memories, transceivers, bus circuitry, and the like. Functions <NUM>-<NUM> comprise microprocessors, software, memories, transceivers, bus circuitry, and the like. The microprocessors comprise Digital Signal Processors (DSP), Central Processing Units (CPU), Graphical Processing Units (GPU), Application-Specific Integrated Circuits (ASIC), and/or the like. The memories comprise Random Access Memory (RAM), flash circuitry, disk drives, and/or the like. The memories store software like operating systems, user applications, radio applications, and network functions. The microprocessors retrieve the software from the memories and execute the software to drive the operation of UEs <NUM>-<NUM>, network <NUM>, and network <NUM> as described herein.

<FIG> illustrates an exemplary operation of wireless communication network <NUM> to hand-in UE <NUM> to non-3GPP access node <NUM>. This operation is exemplary and may vary in other examples. NEF <NUM> receives UE context for UE <NUM> from wireless communication network <NUM> (<NUM>). AMF <NUM> registers UE <NUM> over non-3GPP access node <NUM> and network functions <NUM> (<NUM>). AMF <NUM> determines when UE <NUM> is handing-in from wireless communication network <NUM> (<NUM>). In response to the hand-in from network <NUM> to non-3GPP access node <NUM> (<NUM>), AMF <NUM> transfers a UE context request for UE <NUM> and network <NUM> to NEF <NUM> (<NUM>). NEF <NUM> transfers the UE context for UE <NUM> from network <NUM> to AMF <NUM> in response to the UE context request (<NUM>). AMF <NUM> processes the UE context and responsively generates network signaling (<NUM>). AMF <NUM> transfers the network signaling to network functions <NUM> (<NUM>). Network functions <NUM> serve UE <NUM> based on the network signaling (<NUM>). AMF <NUM> may use standard processing (<NUM>) when UE <NUM> is not handing-in from wireless communication network <NUM> (<NUM>).

<FIG> illustrates an exemplary operation of wireless communication network <NUM> to hand-in UE <NUM> to non-3GPP access node <NUM> and to hand-out UE <NUM> from non-3GPP access node <NUM>. This operation is exemplary and may vary in other examples. UE <NUM> and wireless communication network <NUM> exchange user data per UE context. The UE context indicates information like user ID, UE ID, network ID, access node ID, service IDs, session IDs, and individual session data for addresses, names, quality, and other session parameters.

Wireless communication network <NUM> identifies that UE <NUM> is handing-out to wireless communication network <NUM>, and in response, network <NUM> transfers the UE context to NEF <NUM>. UE <NUM> attaches to non-3GPP access node <NUM> and registers with AMF <NUM> over non-3GPP access node <NUM> and network functions <NUM>. UE <NUM> indicates UE context to AMF <NUM> during the registration. AMF <NUM> processes the context to detect that UE <NUM> is handing-in from wireless communication network <NUM> to non-3GPP access node <NUM>, and in response, AMF <NUM> transfers a UE context request (RQ) for UE <NUM> and network <NUM> to NEF <NUM>. NEF <NUM> transfers the UE context for UE <NUM> and network <NUM> to AMF <NUM> in response to the UE context request. AMF <NUM> processes the UE context and responsively transfers the network signaling to network functions <NUM>. UE <NUM> and network functions <NUM> exchange user data over non-3GPP access node <NUM> per the network signaling which is based on the UE context from wireless communication network <NUM>.

For UE <NUM>, AMF <NUM> determines the UE context and signals the UE context to network functions <NUM>. The UE context indicates information like user ID, UE ID, network ID, access node <NUM> ID, service ID, session IDs, and individual session data. As UE <NUM> moves away from non-3GPP access node <NUM> and toward wireless communication network <NUM>, UE <NUM> reports poor signal strength from non-3GPP access node <NUM> and better signal strength from wireless communication network <NUM>. In response to the UE report, AMF <NUM> detects that UE <NUM> is handing-out to wireless communication network <NUM>, and in response, AMF <NUM> transfers the UE context for UE <NUM> to NEF <NUM> for delivery to wireless communication network <NUM>. NEF <NUM> transfers the UE context for UE <NUM> to wireless communication network <NUM>. UE <NUM> and wireless communication network <NUM> exchange user data per the UE context from wireless communication network <NUM>.

<FIG> illustrates Fifth Generation (<NUM>) wireless communication network <NUM> to handover UEs <NUM>-<NUM> between Long Term Evolution Access Node (LTE AN) <NUM> and IEEE <NUM> Access Node (WIFI AN) <NUM>. <NUM> wireless communication network <NUM> comprises an example of wireless communication networks <NUM> and <NUM>, although networks <NUM> and <NUM> may vary from this example. <NUM> wireless communication network <NUM> comprises UEs <NUM>-<NUM>, LTE AN <NUM>, Mobility Management Entity (MME) <NUM>, Serving Gateway (SGW) <NUM>, Packet Data Network Gateway (PGW) <NUM>, Service Capability Exposure Function (SCEF) <NUM>, WIFI AN <NUM>, Non-3GPP Interworking Function (N3IWF) <NUM>, User Plane Function (UPF) <NUM>, Access and Mobility Management Function (AMF) <NUM>, Session Management Function (SMF) <NUM>, Application Function (AF) <NUM>, and Network Exposure Function (NEF) <NUM>.

Initially, SCEF <NUM> receives UE instructions (INST) from an external app server for UEs <NUM>-<NUM>. AF <NUM> also receives UE instructions for UEs <NUM>-<NUM> from the external app server and transfers the user instructions to NEF <NUM>. The UE instructions relate to hand-overs between LTE AN <NUM> to WIFI AN <NUM>.

UE <NUM> attaches to LTE AN <NUM> and registers with MME <NUM> over LTE AN <NUM>. MME <NUM> determines UE context for UE <NUM> like user ID, International Mobile Subscriber ID (IMSI), Public Land Mobile Network (PLMN) ID, Physical Cell ID (PCI), Access Point Names, (APNs), Quality-of-Service Class Indicators (QCIs), Internet Protocol (IP) addresses, IP Multimedia Subsystem (IMS) information, roaming policies, and/or some other networking data. MME <NUM> transfers S1-MME signaling to LTE AN <NUM> and transfers S11 signaling to SGW <NUM> to serve UE <NUM> per the UE context. LTE AN <NUM> transfers NAS signaling with the UE context to UE <NUM>. SGW <NUM> transfers S5 signaling to PGW <NUM> to serve UE <NUM> per the UE context. UE <NUM> and LTE AN <NUM> wirelessly exchange user data per the network signaling and the UE context. LTE AN <NUM> and SGW <NUM> exchange S1-U data per the network signaling and the UE context. SGW <NUM> and PGW <NUM> exchange S5 data per the network signaling and the UE context. PGW <NUM> and external systems exchange the SGi data per the network signaling and the UE context.

As UE <NUM> moves away from LTE AN <NUM> and toward WIFI AN <NUM>, UE <NUM> detects a Service Set ID (SSID) for WIFI AN <NUM> and reports to MME <NUM> over LTE AN <NUM>. The report indicates poor signal strength from LTE AN <NUM> and better signal strength from WIFI AN <NUM> over the SSID. In response to the UE report, MME <NUM> detects the hand-over of UE <NUM> from LTE AN <NUM> to WIFI AN <NUM>, and in response to the handover, MME <NUM> transfers the UE context for UE <NUM> to SCEF <NUM> for delivery to NEF <NUM>. In response to the UE context transfer, SCEF <NUM> also transfers the user instructions from the app server to NEF <NUM> along with the UE context.

UE <NUM> attaches to WIFI AN <NUM>. UE <NUM> registers with AMF <NUM> over WIFI AN <NUM> and N3IWF <NUM>. UE <NUM> indicates the UE context to AMF <NUM> during the registration - although the UE context from UE <NUM> is authorized. AMF <NUM> transfers a UE context request for UE <NUM>, WIFI AN <NUM>, and LTE AN <NUM> to NEF <NUM>. NEF <NUM> translates the UE context and the UE instructions into a format suitable for AMF <NUM>. NEF <NUM> transfers the UE context and UE instructions for UE <NUM> to AMF <NUM>. The UE context from NEF <NUM> is authorized.

AMF <NUM> processes the UE context and UE instructions and responsively transfers the UE instructions to UE <NUM> over the N1 that traverses N3GPP IWF <NUM> and WIFI AN <NUM>. AMF <NUM> and SMF <NUM> exchange N11 signaling based on the UE context and UE instructions. AMF <NUM> and N3IWF <NUM> exchange N2 signaling based on the UE context and UE instructions. AMF <NUM> and UE <NUM> exchange N1 signaling based on the UE context and UE instructions over AN <NUM> and N3IWF <NUM>. SMF <NUM> and UPF <NUM> exchange N4 signaling based on the UE context and UE instructions. N3IWF <NUM> and WIFI AN <NUM> may exchange network signaling based on the UE context and instructions. UE <NUM> and WIFI AN <NUM> wirelessly exchange user data per the signaling which is based on the UE context and instructions. WIFI AN <NUM> and N3IWF <NUM> exchange user data per the signaling which is based on the UE context and instructions. N3IWF <NUM> and UPF <NUM> exchange N3 data per the signaling which is based on the UE context and instructions. UPF <NUM> and external systems exchange N6 data per the signaling which is based on the UE context and instructions.

UE <NUM> attaches to WIFI AN <NUM> and registers with AMF <NUM> over WIFI AN <NUM>. AMF <NUM> determines UE context for UE <NUM> like user ID, IMSI, PLMN ID, SSID, PCI, Data Network Names, (DNNs), slice IDs, Quality-of-Service Flow Indicators (QFIs), IP addresses, IMS information, roaming policies, and/or some other networking data. AMF <NUM> transfers N2 signaling to N3IWF <NUM> and transfers N11 signaling to SMF <NUM> to serve UE <NUM> per the UE context. N3IWF <NUM> may transfer network signaling to WIFI AN <NUM> to serve UE <NUM> per the UE context. AMF <NUM> transfers N1 signaling with the UE context to UE <NUM>. SMF <NUM> transfers N4 signaling to UPF <NUM> to serve UE <NUM> per the UE context. UE <NUM> and WIFI AN <NUM> wirelessly exchange user data per the network signaling and the UE context. WIFI AN <NUM> and IWF <NUM> exchange NWu data per the network signaling and the UE context. IWF <NUM> and UPF <NUM> exchange N3 data per the network signaling and the UE context. UPF <NUM> and external systems exchange the user data per the network signaling and the UE context.

As UE <NUM> moves away from WIFI AN <NUM> and toward LTE AN <NUM>, UE <NUM> detects a PCI for LTE AN <NUM> and reports to AMF <NUM> over WIFI AN <NUM> and N3IWF <NUM>. The report indicates poor signal strength from WIFI AN <NUM> and better signal strength from LTE AN <NUM> over the PCI. In response to the UE report, AMF <NUM> detects the hand-over of UE <NUM> from WIFI AN <NUM> to LTE AN <NUM>. In response to the handover, AMF <NUM> transfers the UE context to NEF <NUM> for delivery to SCEF <NUM>. In response to the UE context transfer, NEF <NUM> transfers the UE instructions from AF <NUM> to SCEF <NUM> along with the UE context.

UE <NUM> attaches to LTE AN <NUM>. UE <NUM> registers with MME <NUM> over LTE AN <NUM>. UE <NUM> indicates the UE context to MME <NUM> during the registration - although the UE context from UE <NUM> is not authorized. MME <NUM> transfers a UE context request for UE <NUM>, LTE AN <NUM>, and WIFI AN <NUM> to SCEF <NUM>. SCEF <NUM> translates the UE context and the UE instructions into a format suitable for MME <NUM>. SCEF <NUM> transfers the UE context and UE instructions for UE <NUM> to MME <NUM>. The UE context from SCEF <NUM> is authorized. MME <NUM> processes the UE context and UE instructions and responsively transfers the UE instructions to UE <NUM> over LTE AN <NUM>. MME <NUM> and SGW <NUM> exchange S11 signaling based on the UE context and UE instructions. MME <NUM> and LTE AN <NUM> exchange S1-MME signaling based on the UE context and UE instructions. MME <NUM> and UE <NUM> exchange NAS signaling based on the UE context and UE instructions over LTE AN <NUM>. SGW <NUM> and PGW <NUM> exchange S5 signaling based on the UE context and UE instructions. UE <NUM> and LTE AN <NUM> wirelessly exchange user data per the signaling which is based on the UE context and instructions. LTE AN <NUM> and SGW <NUM> exchange the S1-U data per the signaling which is based on the UE context and instructions. SGW <NUM> and PGW <NUM> exchange S5 data per the signaling which is based on the UE context and instructions. PGW <NUM> and external systems exchange SGi data per the signaling which is based on the UE context and instructions.

WIFI AN <NUM> is untrusted in this example. In other examples, WIFI AN <NUM> may comprise a Trusted Network Access Point (TNAP) that communicates with a Trusted Network Gateway Function (TNGF). The TNGF would operate and interact with WIFI AN <NUM>, UPF <NUM> and AMF <NUM> in a similar manner to N3IWF <NUM>.

<FIG> illustrates UE <NUM> in <NUM> wireless communication network <NUM>. UE <NUM> comprises an example of UE <NUM>, although UE <NUM> may differ. UE <NUM> could be similar to UE <NUM>. UE <NUM> comprises LTE radio <NUM>, WIFI radio <NUM>, processing circuitry <NUM>, and user components <NUM>. Radios <NUM>-<NUM> comprise antennas, amplifiers, filters, modulation, analog-to-digital interfaces, DSP, memory, and transceivers that are coupled over bus circuitry. Processing circuitry <NUM> comprises memory, CPU, user interfaces and components, and transceivers that are coupled over bus circuitry. The memory in processing circuitry <NUM> stores an operating system, user applications (USER), and network applications for IP, 3GPP, WIFI, and LTE. The network applications include physical layer, media access control, link control, convergence and adaption, radio resource control, and the like. The antennas in LTE radio <NUM> are wirelessly coupled to LTE AN <NUM> over an LTE link that supports RRC and N1. The antennas in WIFI radio <NUM> are wirelessly coupled to WIFI AN <NUM> over a WIFI link that supports NWu and N1. Transceivers (XCVRs) in radios <NUM>-<NUM> are coupled to transceivers in processing circuitry <NUM>. Transceivers in processing circuitry <NUM> are coupled to user components <NUM> like displays, controllers, and memory. The CPU in processing circuitry <NUM> executes the operating system, user applications, and network applications to exchange network signaling and user data with ANs <NUM> and <NUM> over respective radios <NUM>-<NUM>.

<FIG> illustrates IEEE <NUM> (WIFI) access node <NUM> in <NUM> wireless communication network <NUM>. WIFI AN <NUM> comprises an example of non-3GPP access node <NUM>, although access node <NUM> may differ. WIFI AN <NUM> also comprises an example of an access point in wireless communication network <NUM>, although network <NUM> may differ. WIFI AN <NUM> comprises WIFI radio <NUM> and node circuitry <NUM>. Radio <NUM> comprises antennas, amplifiers, filters, modulation, analog-to-digital interfaces, DSP, memory, and transceivers that are coupled over bus circuitry. Node circuitry <NUM> comprises memory, CPU, and transceivers that are coupled over bus circuitry. The memory in node circuitry <NUM> stores operating systems and network applications for IP, WIFI, and 3GPP like physical layer, media access control, link control, and the like. The antennas in WIFI radio <NUM> are wirelessly coupled to UEs <NUM>-<NUM> over wireless links that support NWu and N1. Transceivers in WIFI radio <NUM> are coupled to transceivers in node circuitry <NUM>, and transceivers in node circuitry <NUM> are coupled to transceivers in N3IWF <NUM> over links that support NWu and N1. The CPU in node circuitry <NUM> executes the operating system and network applications to exchange data and signaling with UEs <NUM>-<NUM> and to exchange data and signaling with N3IWF <NUM>. WIFI AN <NUM> could be configured with additional 3GPP trust software to comprise a TNAP.

<FIG> illustrates LTE access node <NUM> in <NUM> wireless communication network <NUM>. LTE access node <NUM> comprises an example of an access node in wireless communication network <NUM>, although network <NUM> may differ. LTE access node <NUM> comprises LTE Radio Unit (RU) <NUM>, 3GPP Distributed Unit (DU) <NUM>, and 3GPP Centralized Unit (CU) <NUM>. LTE RU <NUM> comprises antennas, amplifiers, filters, modulation, analog-to-digital interfaces, DSP, memory, and transceivers that are coupled over bus circuitry. DU <NUM> comprises memory, CPU, and transceivers that are coupled over bus circuitry. The memory in DU <NUM> stores operating systems and LTE network applications that include physical layer, media access control, radio link control, and the like. CU <NUM> comprises memory, CPU, and transceivers that are coupled over bus circuitry. The memory in CU <NUM> stores an operating system and network applications for IP and LTE that include packet data convergence protocol, service data adaptation protocol, radio resource control, and the like. The antennas in RU <NUM> are wirelessly coupled to UEs <NUM>-<NUM> over LTE links that support RRC and N1. Transceivers in RU <NUM> are coupled to transceivers in DU <NUM> over fronthaul links like enhanced Common Public Radio Interface (eCPRI). Transceivers in DU <NUM> coupled to transceivers in CU <NUM> over mid-haul links. Transceivers in CU <NUM> are coupled to MME <NUM> and SGW <NUM> over backhaul links. The CPU in DU <NUM> executes an operating system and network applications to exchange LTE data units with RU <NUM> and to exchange LTE data units with CU <NUM>. The CPU in CU <NUM> executes an operating system and network applications to exchange the LTE data units with DU <NUM>, exchange S1-MME signaling with AMF <NUM>, and exchange S1-U data with SGW <NUM>.

<FIG> illustrates wireless network core <NUM> in <NUM> wireless communication network <NUM>. Network core <NUM> comprises an example of wireless communication network <NUM>, NEF <NUM>, AMF <NUM>, and network functions <NUM>, although network <NUM>, NEF <NUM>, AMF <NUM>, and functions <NUM> may differ. Network core <NUM> comprises Network Function Virtualization Infrastructure (NFVI) hardware <NUM>, NFVI hardware drivers <NUM>, NFVI operating systems <NUM>, NFVI virtual layer <NUM>, and NFVI Virtual Network Functions (VNFs) <NUM>. NFVI hardware <NUM> comprises Network Interface Cards (NICs), CPU, RAM, Flash/Disk Drives (DRIVE), and Data Switches (SW). NFVI hardware drivers <NUM> comprise software that is resident in the NIC, CPU, RAM, DRIVE, and SW. NFVI operating systems <NUM> comprise kernels, modules, applications, containers, hypervisors, and the like. NFVI virtual layer <NUM> comprises vNIC, vCPU, vRAM, vDRIVE, and vSW. NFVI VNFs <NUM> comprise Mobility Management Entity (MME) <NUM>, Serving Gateway (SGW) <NUM>, Packet Data Network Gateway (PGW) <NUM>, Service Capability Exposure Function (SCEF) <NUM>, Non-3GPP Interworking Function (N3IWF) <NUM>, User Plane Function (UPF) <NUM>, Access and Mobility Management Function (AMF) <NUM>, Session Management Function (SMF) <NUM>, Application Function (AF) <NUM>, and Network Exposure Function (NEF) <NUM>. Other VNFs like Authentication Server Function (AUSF) and Network Repository Function (NRF) are typically present but are omitted for clarity. Network core <NUM> may be located at a single site or be distributed across multiple geographic locations. The NIC in NFVI hardware <NUM> are coupled to ANs <NUM> and <NUM> over data links that support S1, NWu, and N1. NFVI hardware <NUM> executes NFVI hardware drivers <NUM>, NFVI operating systems <NUM>, NFVI virtual layer <NUM>, and NFVI VNFs <NUM> to form and operate MME <NUM>, SGW <NUM>, PGW <NUM>, SCEF <NUM>, N3IWF <NUM>, UPF <NUM>, AMF <NUM>, SMF <NUM>, AF <NUM>, and NEF <NUM>. In some examples, VNFs <NUM> include a TNGF VNF that is executed to form and operate a TNGF that communicates with a TNAP.

<FIG> further illustrates wireless network core <NUM> in <NUM> wireless communication network <NUM>. IWF <NUM> performs Y2 termination, N2 termination, NWu termination, and N1 transfer. UPF <NUM> performs packet routing & forwarding, packet inspection and policy, QoS handling and lawful intercept, PDU interconnection, and mobility anchoring. AMF <NUM> performs N1 termination, N2 termination, UE ciphering & integrity protection, UE registration and connection, UE mobility and reachability, UE authentication and authorization, and UE context forwarding. SMF <NUM> performs N1 termination, session establishment/management, UPF selection and control, policy and charging control, and traffic steering and routing. AF <NUM> performs interactions with external app servers, and NEF interaction over the Northbound Application Programming Interface (API). NEF <NUM> performs capability and event exposure, data translation/abstraction, control-plane management, AF interaction over the northbound API, and UE context forwarding.

<FIG> further illustrates wireless network core <NUM> in <NUM> wireless communication network <NUM>. MME <NUM> performs S1 termination, Non-Access Stratum (NAS) termination, UE ciphering & integrity protection, UE registration and connection, UE mobility and reachability, UE authentication and authorization, session establishment/management, GW selection and control, and UE context forwarding. SGW <NUM> performs packet routing & forwarding, QoS handling, and PDU interconnection. PGW <NUM> performs packet routing & forwarding, packet inspection and policy, QoS handling and lawful intercept, PDU interconnection, and mobility anchoring. SCEF <NUM> performs capability and event exposure, data translation/abstraction, control-plane management, NEF interaction, and UE context forwarding.

<FIG> illustrates an exemplary operation of <NUM> wireless communication network <NUM> to handover UE <NUM> from LTE access node <NUM> to WIFI access node <NUM>. The operation may vary in other examples. SCEF <NUM> receives UE instructions (INST) from an external app server for UEs <NUM>-<NUM>. AF <NUM> also receives UE instructions for UEs <NUM>-<NUM> from the external app server and transfers the user instructions to NEF <NUM>. The UE instructions relate to hand-overs between LTE AN <NUM> to WIFI AN <NUM>. UE <NUM> attaches to LTE AN <NUM> and registers with MME <NUM> over LTE AN <NUM>.

MME <NUM> determines UE context for UE <NUM> like user ID, IMSI, PLMN ID, PCI, APNs, QCIs, IP addresses, IMS information, roaming policies, and/or some other networking data. MME <NUM> transfers S1-MME signaling to LTE AN <NUM> and transfers S11 signaling to SGW <NUM> to serve UE <NUM> per the UE context. LTE AN <NUM> transfers RRC signaling with the UE context to UE <NUM>. SGW <NUM> transfers S5 signaling to PGW <NUM> to serve UE <NUM> per the UE context. UE <NUM> and LTE AN <NUM> wirelessly exchange RRC data per the network signaling and the UE context. LTE AN <NUM> and SGW <NUM> exchange S1-U data per the network signaling and the UE context. SGW <NUM> and PGW <NUM> exchange S5 data per the network signaling and the UE context. PGW <NUM> and external systems exchange SGi data per the network signaling and the UE context.

UE <NUM> detects a Service Set ID (SSID) for WIFI AN <NUM> and reports to MME <NUM> over LTE AN <NUM>. The report indicates poor signal strength from LTE AN <NUM> and better signal strength from WIFI AN <NUM> over the SSID. In response to the UE report, MME <NUM> detects the hand-over of UE <NUM> from LTE AN <NUM> to WIFI AN <NUM>, and in response to the handover, MME <NUM> transfers the UE context for UE <NUM> to SCEF <NUM> for delivery to NEF <NUM>. SCEF <NUM> transfers the user instructions from the app server to NEF <NUM> along with the UE context.

UE <NUM> attaches to WIFI AN <NUM>. UE <NUM> registers with AMF <NUM> over WIFI AN <NUM> and N3IWF <NUM>. UE <NUM> indicates the UE context to AMF <NUM> during the registration - although the UE context from UE <NUM> is not authorized. AMF <NUM> transfers a UE context request for UE <NUM>, WIFI AN <NUM>, and LTE AN <NUM> to NEF <NUM>. NEF <NUM> translates the UE context and the UE instructions into a format suitable for AMF <NUM>. NEF <NUM> transfers the UE context and UE instructions for UE <NUM> to AMF <NUM>. The UE context from NEF <NUM> is authorized.

AMF <NUM> processes the UE context and UE instructions and responsively transfers the UE instructions to UE <NUM> over N3GPP IWF <NUM> and WIFI AN <NUM>. AMF <NUM> and SMF <NUM> exchange N11 signaling based on the UE context and UE instructions. AMF <NUM> and N3IWF <NUM> exchange N2 signaling based on the UE context and UE instructions. AMF <NUM> and UE <NUM> exchange N1 signaling based on the UE context and UE instructions over AN <NUM> and N3IWF <NUM>. SMF <NUM> and UPF <NUM> exchange N4 signaling based on the UE context and UE instructions. N3IWF <NUM> and WIFI AN <NUM> may exchange network signaling based on the UE context and instructions. UE <NUM> and WIFI AN <NUM> wirelessly exchange WIFI data per the signaling which is based on the UE context and instructions. WIFI AN <NUM> and N3IWF <NUM> exchange NWu data per the signaling which is based on the UE context and instructions. N3IWF <NUM> and UPF <NUM> exchange N3 data per the signaling which is based on the UE context and instructions. UPF <NUM> and external systems exchange N6 data per the signaling which is based on the UE context and instructions.

<FIG> illustrates an exemplary operation of <NUM> wireless communication network <NUM> to handover UE <NUM> from WIFI access node <NUM> to LTE access node <NUM>. The operation may vary in other examples. UE <NUM> attaches to WIFI AN <NUM> and registers with AMF <NUM> over WIFI AN <NUM>. AMF <NUM> determines UE context for UE <NUM> like user ID, IMSI, PLMN ID, SSID, PCI, Data Network Names, (DNNs), slice IDs, Quality-of-Service Flow Indicators (QFIs), IP addresses, IMS information, roaming policies, and/or some other networking data. AMF <NUM> transfers N2 signaling to N3IWF <NUM> and transfers N11 signaling to SMF <NUM> to serve UE <NUM> per the UE context. N3IWF <NUM> may transfer network signaling to WIFI AN <NUM> to serve UE <NUM> per the UE context. AMF <NUM> transfers N1 signaling with the UE context to UE <NUM>. SMF <NUM> transfers N4 signaling to UPF <NUM> to serve UE <NUM> per the UE context. UE <NUM> and WIFI AN <NUM> wirelessly exchange WIFI data per the network signaling and the UE context. WIFI AN <NUM> and IWF <NUM> exchange NWu data per the network signaling and the UE context. IWF <NUM> and UPF <NUM> exchange N3 data per the network signaling and the UE context. UPF <NUM> and external systems exchange the user data per the network signaling and the UE context.

UE <NUM> detects a PCI for LTE AN <NUM> and reports to AMF <NUM> over WIFI AN <NUM> and N3IWF <NUM>. The report indicates poor signal strength from WIFI AN <NUM> and better signal strength from LTE AN <NUM> over the PCI. In response to the UE report, AMF <NUM> detects the hand-over of UE <NUM> from WIFI AN <NUM> to LTE AN <NUM>. In response to the handover to LTE AN <NUM>, AMF <NUM> transfers the UE context to NEF <NUM> for delivery to SCEF <NUM>. NEF <NUM> transfers the UE instructions from AF <NUM> and the UE context to SCEF <NUM>.

UE <NUM> attaches to LTE AN <NUM>. UE <NUM> registers with MME <NUM> over LTE AN <NUM>. UE <NUM> indicates the UE context to MME <NUM> during the registration - although this UE context is not authorized. MME <NUM> transfers a UE context request for UE <NUM>, LTE AN <NUM>, and WIFI AN <NUM> to SCEF <NUM>. SCEF <NUM> translates the UE context and the UE instructions into a format suitable for MME <NUM>. SCEF <NUM> transfers the UE context and UE instructions for UE <NUM> to MME <NUM>. The UE context from SCEF <NUM> is authorized. MME <NUM> processes the UE context and UE instructions and responsively transfers the UE instructions to UE <NUM> over LTE AN <NUM>. MME <NUM> and SGW <NUM> exchange S11 signaling based on the UE context and UE instructions. MME <NUM> and LTE AN <NUM> exchange S1-MME signaling based on the UE context and UE instructions. MME <NUM> and UE <NUM> exchange NAS signaling based on the UE context and UE instructions over LTE AN <NUM>. SGW <NUM> and PGW <NUM> exchange S5 signaling based on the UE context and UE instructions. UE <NUM> and LTE AN <NUM> wirelessly exchange RRC data per the signaling which is based on the UE context and instructions. LTE AN <NUM> and SGW <NUM> exchange S1-U data per the signaling which is based on the UE context and instructions. SGW <NUM> and PGW <NUM> exchange S5 data per the signaling which is based on the UE context and instructions. PGW <NUM> and external systems exchange SGi data per the signaling which is based on the UE context and instructions.

<FIG> illustrates <NUM> wireless communication network <NUM> to handover UE <NUM> from LTE access node <NUM> to Trusted Network Access Point (TNAP) <NUM>. In this example, a WIFI AN like AN <NUM> is configured with a 3GPP TNAP application to form TNAP <NUM>. A Trusted Network Gateway Function (TNGF) is executed by network core <NUM> to form and operate TNGF <NUM>. For handovers, TNAP <NUM> and TNGF <NUM> operate and interact with UEs <NUM>-<NUM>, UPF <NUM>, and AMF <NUM> in a similar manner to WIFI AN <NUM> and N3IWF <NUM>.

<FIG> illustrates <NUM> wireless communication network <NUM> to handover UE <NUM> between WIFI AN <NUM> and WIFI AN <NUM>. For handovers, WIFI AN <NUM>, N3IWF <NUM>, UPF <NUM>, AMF <NUM>, SMF <NUM>, and NEF <NUM> are configured and operate like corresponding WIFI AN <NUM>, N3IWF <NUM>, UPF <NUM>, AMF <NUM>, SMF <NUM>, and NEF <NUM>. NEF <NUM> and NEF <NUM> exchange UE context for handovers between the two non-3GPP access nodes - WIFI AN <NUM> and WIFI AN <NUM>. Other non-3GPP AN types could be used like bluetooth and ethernet instead of WIFI AN <NUM> and/or WIFI AN <NUM>.

The wireless data network circuitry described above comprises computer hardware and software that form special-purpose network circuitry to handover UEs with non-3GPP access nodes. The computer hardware comprises processing circuitry like CPUs, DSPs, GPUs, transceivers, bus circuitry, and memory. To form these computer hardware structures, semiconductors like silicon or germanium are positively and negatively doped to form transistors. The doping comprises ions like boron or phosphorus that are embedded within the semiconductor material. The transistors and other electronic structures like capacitors and resistors are arranged and metallically connected within the semiconductor to form devices like logic circuitry and storage registers. The logic circuitry and storage registers are arranged to form larger structures like control units, logic units, and Random-Access Memory (RAM). In turn, the control units, logic units, and RAM are metallically connected to form CPUs, DSPs, GPUs, transceivers, bus circuitry, and memory.

In the computer hardware, the control units drive data between the RAM and the logic units, and the logic units operate on the data. The control units also drive interactions with external memory like flash drives, disk drives, and the like. The computer hardware executes machine-level software to control and move data by driving machine-level inputs like voltages and currents to the control units, logic units, and RAM. The machine-level software is typically compiled from higher-level software programs. The higher-level software programs comprise operating systems, utilities, user applications, and the like. Both the higher-level software programs and their compiled machine-level software are stored in memory and retrieved for compilation and execution. On power-up, the computer hardware automatically executes physically-embedded machine-level software that drives the compilation and execution of the other computer software components which then assert control. Due to this automated execution, the presence of the higher-level software in memory physically changes the structure of the computer hardware machines into special-purpose network circuitry to handover UEs with non-3GPP access nodes.

Claim 1:
A method of operating a wireless communication network to hand-in inbound User Equipment, UE, (<NUM>) from a source communication network to a non-Third Generation Partnership Project, non-3GPP, access node (<NUM>), the method comprising:
a Network Exposure Function, NEF, (<NUM>) receiving inbound UE context from the source communication network when the source communication network identifies that the UE is handing over to the non-3GPP access node;
an Access and Mobility Management Function, AMF, (<NUM>) detecting when the inbound UE attaches to the non-3GPP access node to hand-in from the source communication network, wherein the UE attaches to the non-3GPP access node and registers with AMF over non-3GPP access node, and in response, transferring a UE context request for the inbound UE to the NEF;
the NEF transferring the inbound UE context to the AMF in response to the UE context request; and
the AMF receiving the inbound UE context and transferring network signaling to one or more network functions (<NUM>) to serve the inbound UE based on the inbound UE context.