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), User Plane Functions (UPFs), Network Exposure Functions (NEFs), and the like. Some network elements like UPFs are grouped into wireless network slices. An individual wireless user device may request a specific wireless network slice.

Although network elements are often concentrated in the wireless network cores, network elements are also deployed in Edge Data Networks (EDNs) that are near the wireless access nodes. In particular, Edge Application Servers (EAS) in the EDNs interact with the wireless user devices over the wireless access nodes to serve hosted-computing, augmented reality, and other low-latency data services. A user application in a wireless user device is coupled to an EAS in the EDN, and communication performance between the user application and the EAS is monitored and controlled to maintain proper session quality for the use application.

In the EDNs, the EAS are controlled by Edge Enablement Servers (EES) that drive the EAS to deliver the low-latency data services. The wireless user devices have Edge Enablement Clients (EECs) that interact with the user applications and with the EES. The EES exposes the EAS to the EECs in the wireless user devices. The user applications then exchange user data with the EAS over the wireless access nodes under the control and support of the EECs in the wireless user devices and the EES in the EDNs. The EES monitors network performance to influence traffic through the NEFs in a similar manner to AFs. The EES also instantiates and controls the EAS. An Edge Configuration Server (ECS) may be used. The ECS helps pair the EECs in the wireless user devices with the EES in the EDN. The ECS may operate like an AF.

The EDNs feature reference points called EDGES. EDGE-<NUM> is between an EEC in a wireless user device and an EES in the EDN. EDGE-<NUM> supports EEC registration, EAS discovery, and EAS configuration. EDGE-<NUM> is between an EES in the EDN and a network function (NEF, SMF, PCF) in the network core. EDGE-<NUM> supports the discovery and subscription to 3GPP network capabilities like UE location and session quality. EDGE-<NUM> is between an EES and EAS in the EDN. EDGE-<NUM> supports EAS registration and session quality control. EDGE-<NUM> is between an EEC in the wireless user device and an ECS. EDGE-<NUM> supports EEC provisioning by the ECS and EEC info delivery to the ECS. EDGE-<NUM> is between an EEC in the wireless user device and the EES in the EDN. EDGE-<NUM> supports interactions between the user application and the EDN. EDGE-<NUM> is between an ECS and the EES. EDGE-<NUM> supports EES configuration and conveys EES information to the ECS. EDGE-<NUM> is between an EAS in the EDN and a network function (NEF, SMF, PCF) in the network core. EDGE-<NUM> supports the discovery and subscription to 3GPP network capabilities like UE location and session quality. EDGE-<NUM> is between an ECS and a Network Function (NEF, SMF, PCF) in the network core. EDGE-<NUM> supports the discovery and subscription to 3GPP network capabilities like UE location and session quality. EDGE-<NUM> is between two EES and supports service continuity during UE mobility.

Unfortunately, the EDNs lack effective security. Moreover, the EDNs inefficiently record EDN transactions. <CIT> describes edge discovery techniques in wireless communications systems. <NPL>, describes application architecture for enabling edge applications. <CIT> describes wireless network access for data appliances.

In a wireless communication network, an Edge Enablement Client (EEC) in a UE Gateway (GW) exchanges EDGE-<NUM> signaling with a user app and exchanges EDGE-<NUM> signaling with a Gateway Enablement Server (GES) in the GW. The GES exchanges EDGE-<NUM> signaling with an Edge Enablement Server (EES) in an Edge Data Network (EDN) and exchanges EDGE-<NUM> signaling with a Gateway Application Server (GAS) in the GW. The GAS exchanges user data between the user app and an Edge Application Server (EAS) in the EDN responsive to the EDGE-<NUM> signaling. The EES exchanges additional EDGE-<NUM> signaling with the EAS. The EAS exchanges the user data between the GAS and a network core responsive to the additional EDGE-<NUM> signaling. The network core exchanges the user data with the AS and transfers network information for the exchange to a Digital Ledger (DL) node. The DL node determines trust based on the network information.

<FIG> illustrates wireless communication network <NUM> to connect User Application (APP) <NUM> in User Equipment (UE) <NUM> to Application Server (AS) <NUM>. Wireless communication network <NUM> comprises UE <NUM>, UE gateway (GW) <NUM>, Radio Access Network (RAN) <NUM>, Edge Data Network (EDN) <NUM>, Core Network (CN) <NUM>, and AS <NUM>. UE <NUM> comprises a computer, phone, vehicle, sensor, robot, or some other data appliance with communication circuitry. Wireless communication network <NUM> delivers wireless data services to APP <NUM> in UE <NUM> like hosted-computing, augmented-reality, or some other edge-supported network product. Wireless communication network <NUM> is simplified and typically includes more UEs, RANs, EDNs, and AS than shown.

Various examples of network operation and configuration are described herein. In some examples, wireless communication network <NUM> connects APP <NUM> to AS <NUM> to deliver a service to UE <NUM> like hosted-computing or augmented reality. CN <NUM> exchanges EDGE-<NUM> signaling with ECS <NUM> to expose network capabilities. CN <NUM> exchanges EDGE-<NUM> signaling with GES <NUM> and EES <NUM> to expose network capabilities. CN <NUM> exchanges EDGE-<NUM> signaling with GAS <NUM> and EAS <NUM> to configure GAS <NUM> and EAS <NUM>. EEC <NUM> in GW <NUM> and ECS <NUM> in EDN <NUM> exchange EDGE-<NUM> signaling to provision EEC <NUM> with network information like EES, data network name, and slice identifier. GES <NUM> in GW <NUM> and ECS <NUM> in EDN <NUM> exchange EDGE-<NUM> signaling to configure GES <NUM> and convey GES information to ECS <NUM>. EES <NUM> and ECS <NUM> in EDN <NUM> exchange EDGE-<NUM> signaling to configure EES <NUM> and convey EES information to ECS <NUM>.

UE <NUM> executes APP <NUM>. APP <NUM> and EEC <NUM> in GW <NUM> exchange EDGE-<NUM> signaling to initiate service for APP <NUM> over GES <NUM> and EES <NUM>. EEC <NUM> and GES <NUM> in GW <NUM> exchange EDGE-<NUM> signaling to register UE <NUM> and discover GAS <NUM>, EAS <NUM>, and AS <NUM>. In addition, GES <NUM> and EES <NUM> exchange EDGE-<NUM> signaling to register UE <NUM> and discover GAS <NUM>, EAS <NUM>, and AS <NUM>. GES <NUM> and GAS <NUM> exchange EDGE-<NUM> signaling to set-up a user data session through GAS <NUM>. EES <NUM> and EAS <NUM> exchange EDGE-<NUM> signaling to set-up the user data session through EAS <NUM>. APP <NUM> and GAS <NUM> exchange user data responsive to the EDGE-<NUM> signaling from GES <NUM> and the EDGE-<NUM> signaling from EEC <NUM>. GAS <NUM> and EAS <NUM> exchange the user data responsive to the EDGE-<NUM> signaling from GES <NUM> and EES <NUM>. EAS <NUM> and CN <NUM> exchange the user data responsive to the EDGE-<NUM> signaling from EES <NUM>. CN <NUM> and AS <NUM> exchange the user data. Typically, GAS <NUM> performs the lowest-latency tasks to deliver service to APP <NUM> in UE <NUM>. EAS <NUM> performs additional low-latency tasks to deliver the service to APP <NUM> in UE <NUM>. AS <NUM> tasks that do not require low-latency to deliver service to APP <NUM> in UE <NUM>.

EES <NUM> and CN <NUM> exchange EDGE-<NUM> signaling to determine network information like identifiers and addresses that characterizes the data exchange between APP <NUM> to AS <NUM>. CN <NUM> transfers the network information to Digital Ledger (DL) <NUM>. DL <NUM> determines trust for the APP <NUM>, GW <NUM>, RAN <NUM>, EDN <NUM>, and CN <NUM> based on the network information. For example, DL <NUM> may match the UE Identifier (ID), GW ID, EDN ID, CN ID, and AS ID and their corresponding network addresses against authorized combinations of the IDs and addresses to determine trust. DL <NUM> may use Minimum Viable Consensus (MVC) to determine trust based on the network information. EAS <NUM> may exchange the user data with a wireless network slice in CN <NUM> that comprises a User Plane Function (UPF). EAS <NUM>, GAS <NUM>, and AS <NUM> may also be part of the same network slice. The slice identifier may be part of the network information that is used to determine trust.

CN <NUM> may transfer the network information to DL <NUM> over a Network Exposure Function (NEF) and a Security Control Function (SCF). A Network Exposure Function (NEF) in CN <NUM> may exchange the EDGE-<NUM> signaling, EDGE-<NUM> signaling, and EDGE-<NUM> signaling with EDN <NUM>. EDN <NUM> and GW <NUM> may comprise Mobile Edge Compute (MEC) platforms and applications that support GES <NUM>, GAS <NUM>, EES <NUM>, and EAS <NUM>.

CN <NUM> comprises network elements like Access and Mobility Management Function (AMF), Session Management Function (SMF), Network Exposure Function (NEF), Network Slice Selection Function (NSSF), User-Plane Function (UPF), and Application Function (AF). GW <NUM> communicates with RAN <NUM> over technologies like Fifth Generation New Radio (5GNR), Long Term Evolution (LTE), Institute of Electrical and Electronic Engineers (IEEE) <NUM> (WIFI), Bluetooth, or some other wireless communication protocol. The various communication links in wireless communication network <NUM> are represented by dotted lines on <FIG> and use metallic wiring, glass fibers, radio channels, or some other communication media. These communication links use IEEE <NUM> (Ethernet), Time Division Multiplex (TDM), Data Over Cable System Interface Specification (DOCSIS), WIFI, 5GNR, LTE, Internet Protocol (IP), General Packet Radio Service Transfer Protocol (GTP), virtual switching, inter-processor communication, bus interfaces, and/or some other data communication protocols. UE <NUM> and GW <NUM> may communicate using one of the above protocols or some other protocol.

UE <NUM>, GW <NUM>, RAN <NUM>, EDN <NUM>, CN <NUM>, AS <NUM>, and DL <NUM> comprise microprocessors, software, memories, transceivers, bus circuitry, and the like. GW <NUM>, RAN <NUM>, and typically UE <NUM> also comprise radios. 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 wireless communication network <NUM> as described herein.

<FIG> illustrates an exemplary operation of wireless communication network <NUM> to connect APP <NUM> in UE <NUM> to AS <NUM>. The operation may vary in other examples. APP <NUM> and EEC <NUM> exchange EDGE-<NUM> signaling to initiate service for APP <NUM> over GES <NUM> (<NUM>). EEC <NUM> and GES <NUM> exchange EDGE-<NUM> signaling to register UE <NUM> and discover GAS <NUM>, EAS <NUM>, and AS <NUM> (<NUM>). GES <NUM> and EES <NUM> also exchange EDGE-<NUM> signaling to register UE <NUM> and discover GAS <NUM>, EAS <NUM>, and AS <NUM> (<NUM>). GES <NUM> and GAS <NUM> exchange EDGE-<NUM> signaling to set-up a user data session through GAS <NUM> for APP <NUM> (<NUM>). EES <NUM> and EAS <NUM> exchange EDGE-<NUM> signaling to set-up the user data session through EAS <NUM> for APP <NUM> (<NUM>). APP <NUM> and GAS <NUM> exchange user data responsive to the EDGE-<NUM> signaling from GES <NUM> and the EDGE-<NUM> signaling from EEC <NUM> (<NUM>). GAS <NUM> and EAS <NUM> exchange the user data responsive to the EDGE-<NUM> signaling from GES <NUM> and EES <NUM> (<NUM>). EAS <NUM> and CN <NUM> exchange the user data responsive to the EDGE-<NUM> signaling from EES <NUM> (<NUM>). CN <NUM> and AS <NUM> exchange the user data, and GAS <NUM>, EAS <NUM>, and AS <NUM> deliver a data service to APP <NUM> like hosted-computing (<NUM>). EES <NUM> and CN <NUM> exchange EDGE-<NUM> signaling to determine network information that characterizes the data exchange between APP <NUM> to AS <NUM> (<NUM>). CN <NUM> transfers the network information to Distributed Ledger (DL) <NUM> (<NUM>). DL <NUM> establishes trust with APP <NUM>, GW <NUM>, RAN <NUM>, EDN <NUM>, and CN <NUM> based on the network information (<NUM>).

<FIG> illustrates an exemplary operation of wireless communication network <NUM> to connect APP <NUM> in UE <NUM> to AS <NUM>. The operation may vary in other examples. CN <NUM> and ECS <NUM> exchange EDGE-<NUM> signaling to transfer ECS information to CN <NUM> and to expose network capabilities to ECS <NUM> like UE location reporting and session quality control. CN <NUM> and EES <NUM> exchange EDGE-<NUM> signaling to expose network capabilities to EES <NUM> and transfer EES information to CN <NUM>. EES <NUM> and GES <NUM> exchange EDGE-<NUM> signaling to expose network capabilities to GES <NUM> and transfer GES information to CN <NUM>. CN <NUM> and EAS <NUM> exchange EDGE-<NUM> signaling to configure EAS <NUM> and transfer EAS information to CN <NUM>. EAS <NUM> and GAS <NUM> exchange EDGE-<NUM> signaling to configure GAS <NUM> and transfer GAS information to CN <NUM>. EEC <NUM> in GW <NUM> and ECS <NUM> in EDN <NUM> exchange EDGE-<NUM> signaling to provision EEC <NUM> and to discover network information like EES, data network name, and slice from ECS <NUM>. EES <NUM> and ECS <NUM> in EDN <NUM> exchange EDGE-<NUM> signaling to configure EES <NUM> and transfer EES information to ECS <NUM>. GES <NUM> in GW <NUM> and ECS <NUM> in EDN <NUM> exchange EDGE-<NUM> signaling to configure GES <NUM> and transfer GES information to ECS <NUM>.

UE <NUM> executes APP <NUM>. APP <NUM> and EEC <NUM> in GW <NUM> exchange EDGE-<NUM> signaling to initiate service for APP <NUM> over GES <NUM> in GW <NUM>. EEC <NUM> and GES <NUM> exchange EDGE-<NUM> signaling to register UE <NUM> and discover GAS <NUM>, EAS <NUM>, and AS <NUM>. In addition, GES <NUM> and EES <NUM> exchange EDGE-<NUM> signaling to register UE <NUM> and discover GAS <NUM>, EAS <NUM>, and AS <NUM>. GES <NUM> and GAS <NUM> exchange EDGE-<NUM> signaling to set-up a user data session through GAS <NUM>. EES <NUM> and EAS <NUM> exchange EDGE-<NUM> signaling to set-up the user data session through EAS <NUM>. APP <NUM> and GAS <NUM> exchange user data responsive to the EDGE-<NUM> signaling from GES <NUM> and the EDGE-<NUM> signaling from EEC <NUM>. GAS <NUM> and EAS <NUM> exchange the user data responsive to the EDGE-<NUM> signaling from GES <NUM> and EES <NUM>. EAS <NUM> and CN <NUM> exchange the user data responsive to the EDGE-<NUM> signaling from EES <NUM>. CN <NUM> and AS <NUM> exchange the user data. GAS <NUM>, EAS <NUM>, and AS <NUM> deliver a low-latency service to APP <NUM>.

EES <NUM> and CN <NUM> exchange EDGE-<NUM> signaling to determine network information that characterizes the data exchange between APP <NUM> to AS <NUM>. CN <NUM> transfers the network information to Distributed Ledger (DL) <NUM>. DL <NUM> starts in a zero trust state and transitions to an alpha trust state for APP <NUM>, GW <NUM>, RAN <NUM>, EDN <NUM>, and CN <NUM> based on the network information. For example, DL <NUM> may check a UE ID, GW ID, EDN ID, CN ID, and AS ID, and their corresponding network addresses against authorized combinations of the IDs and network addresses for the UE location and the network slices in use. DL <NUM> uses MVC across the DL nodes to transition from zero trust to alpha trust.

<FIG> illustrates Fifth Generation (<NUM>) wireless communication network <NUM> to connect user applications in UE <NUM> to AS <NUM>-<NUM> over UE GW <NUM>, RAN <NUM>, EDN <NUM>, and Core <NUM>. <NUM> wireless communication network <NUM> comprises an example of wireless communication network <NUM>, although network <NUM> may differ. <NUM> wireless communication network <NUM> comprises UE <NUM>, UE GW <NUM>, RAN <NUM>, EDN <NUM> and core <NUM>. RAN <NUM> comprises Radio Unit (RU) <NUM>, Distributed Unit (DU) <NUM>, and Centralized Unit (CU) <NUM>. Core <NUM> comprises control-plane <NUM>, user-plane <NUM>, security controller <NUM>, and DL node <NUM>.

UE <NUM> uses GW <NUM>, RAN <NUM>, EDN <NUM>, and core <NUM> to communicate with AS <NUM>-<NUM>. Security controller <NUM> receives related network data for UE <NUM>, UE GW <NUM>, RU <NUM>, DU <NUM>, CU <NUM>, EDN <NUM>, control plane <NUM>, user plane <NUM>, and AS <NUM>-<NUM>. The network data comprises hardware IDs and network addresses that are typically hashed for security. In some examples, security controller <NUM> receives digital trust certificates from the elements that were obtained from a different security system. Security controller <NUM> transfers the network data to DL node <NUM> for trust determination. DL node <NUM> interacts with DL <NUM> to determine trust through Minimum Viable Consensus (MVC). DL node <NUM> and the other nodes in DL <NUM> match the hardware identifiers, network addresses, and/or digital trust certificates to expected values (or value prefixes) given the UE location and slice to establish trust using MVC. If any UE of slice fails hardware trust, then DL node <NUM> indicates the failing UE or slice to security controller <NUM>. Security controller <NUM> drives core <NUM>, EDN <NUM>, RAN <NUM>, GW <NUM>, and UE <NUM> to isolate the failed UE or slice. DL node <NUM> and DL <NUM> maintain a blockchain record of the network information and the trust status for slices <NUM> and <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> comprises <NUM> New Radio (5GNR) radio <NUM>, user circuitry <NUM>, and user components <NUM>. User components <NUM> comprise sensors, controllers, displays, or some other user apparatus that consumes wireless data service. 5GNR radio <NUM> comprises antennas, amplifiers, filters, modulation, analog-to-digital interfaces, DSP, memory, and transceivers that are coupled over bus circuitry. User circuitry <NUM> comprises memory, CPU, user interfaces and components, and transceivers that are coupled over bus circuitry. The memory in user circuitry <NUM> stores operating system (OS) <NUM>, WIFI interface <NUM>, <NUM> interface <NUM>, user applications (APPs) <NUM>-<NUM>. WIFI interface <NUM> comprises components like Physical Layer (PHY), Media Access Control (MAC), and Radio Link Control (RLC). <NUM> interface <NUM> comprises components like PHY, MAC, RLC, Packet Data Convergence Protocol (PDCP), Service Data Adaption Protocol (SDAP), and Radio Resource Control (RRC). The antennas in WIFI radio <NUM> are wirelessly coupled to UE GA <NUM> over a WIFI link. Transceivers (XCVRs) in WIFI radio <NUM> are coupled to transceivers in user circuitry <NUM>. Transceivers in user circuitry <NUM> are coupled to user components <NUM>. The CPU in user circuitry <NUM> executes the operating system, interfaces, and user applications to exchange network signaling and user data with UE GW <NUM>.

<FIG> illustrates UE Gateway <NUM> in <NUM> wireless communication network <NUM>. UE GW <NUM> comprises an example of UE GW <NUM>, although UE GW <NUM> may differ. UE GW <NUM> comprises WIFI radio <NUM>, 5GNR radio <NUM>, and GW circuitry <NUM>. Radios <NUM>-<NUM> comprise antennas, amplifiers, filters, modulation, analog-to-digital interfaces, DSP, memory, and transceivers that are coupled over bus circuitry. GW circuitry <NUM> comprises memory, CPU, user interfaces and components, and transceivers that are coupled over bus circuitry. The memory in GW circuitry <NUM> stores an OS <NUM>, WIFI interface <NUM>, <NUM> interface <NUM>, GAS application <NUM>, GES application <NUM>, EEC application <NUM>, Mobile Edge Compute (MEC) application <NUM>, and MEC platform <NUM>. WIFI interface <NUM> comprises components like PHY, MAC, and RLC. 5GNR interface <NUM> comprises components like PHY, MAC, RLC, PDCP, SDAP, and RRC. The antennas in WIFI radio <NUM> are wirelessly coupled to UE <NUM> over a WIFI link. The antennas in 5GNR radio <NUM> are wirelessly coupled to RAN <NUM> over a 5GNR link. Transceivers (XCVRs) in radios <NUM>-<NUM> are coupled to transceivers in GW circuitry <NUM>. The CPU in user circuitry <NUM> executes OS <NUM>, WIFI <NUM>, <NUM> <NUM>, GAS <NUM>, GES <NUM>, EEC <NUM>, MEC application <NUM>, and MEC platform <NUM> to exchange network signaling and user data between UE <NUM> and RAN <NUM>.

<FIG> illustrates RAN <NUM> in <NUM> wireless communication network <NUM>. <NUM> RAN <NUM> comprises an example of RAN <NUM>, although RAN <NUM> may differ. RAN <NUM> comprises RU <NUM>, DU <NUM>, and CU <NUM>. RU <NUM> comprises 5GNR antennas, amplifiers, filters, modulation, analog-to-digital interfaces, DSP, memory, and transceivers that are coupled over bus circuitry. DU <NUM> comprises memory, CPU, user interfaces and components, and transceivers that are coupled over bus circuitry. The memory in DU <NUM> stores an OS <NUM> and <NUM> interface <NUM>. 5GNR interface <NUM> comprises components like PHY, MAC, and RLC. CU <NUM> comprises memory, CPU, user interfaces and components, and transceivers that are coupled over bus circuitry. The memory in CU <NUM> stores an OS <NUM> and <NUM> interface <NUM>. <NUM> interface <NUM> comprises components like PDCP, SDAP, and RRC. The antennas in RU <NUM> are wirelessly coupled to UE GW <NUM> over a 5GNR link. Transceivers in RU <NUM> are coupled to transceivers in DU <NUM>. Transceivers in DU <NUM> are coupled to transceivers in CU <NUM>. Transceivers in CU <NUM> are coupled to EDN <NUM> and core <NUM>. The CPU in RAN <NUM> execute OS <NUM>, <NUM> <NUM>, OS <NUM>, and <NUM> <NUM> to exchange network signaling and user data with UE GW <NUM>, EDN <NUM>, and core <NUM>. In particular, MEC application <NUM> is controlled by core <NUM> to support the execution of GAS <NUM> in GW <NUM>. MEC platform <NUM> is controlled by core <NUM> to support the execution of GES <NUM> in GW <NUM>.

<FIG> illustrates EDN <NUM> in <NUM> wireless communication network <NUM>. EDN <NUM> comprises an example of EDN <NUM>, although EDN <NUM> may differ. EDN <NUM> comprises Network Function Virtualization Infrastructure (NFVI) hardware <NUM>, NFVI hardware drivers <NUM>, NFVI operating systems <NUM>, NFVI virtual layer <NUM>, and 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, and the like. NFVI virtual layer <NUM> comprises vNIC, vCPU, vRAM, vDRIVE, and vSW. VNFs <NUM> comprise EAS VNF <NUM>, EES VNF <NUM>, ECS VNF <NUM>. MEC Application VNF <NUM>, and MEC platform VNF <NUM>. EDN <NUM> may be located at a single site or be distributed across multiple geographic locations. The NIC transceivers in NFVI hardware <NUM> are coupled to CU <NUM> and core <NUM>. NFVI hardware <NUM> executes NFVI hardware drivers <NUM>, NFVI operating systems <NUM>, NFVI virtual layer <NUM>, and VNFs <NUM> to form and operate an EAS, EES, ECS, MEC Application, and MEC Platform. In particular, MEC application <NUM> is controlled by core <NUM> to support the execution of EAS VNF <NUM> in EDN <NUM>. MEC platform <NUM> is controlled by core <NUM> to support the execution of EES VNF <NUM> in EDN <NUM>.

<FIG> illustrates wireless network core <NUM> in <NUM> wireless communication network <NUM>. Wireless network core <NUM> comprises an example of core <NUM>, although core <NUM> may differ. Wireless network core <NUM> comprises NFVI hardware <NUM>, NFVI hardware drivers <NUM>, NFVI operating systems <NUM>, NFVI virtual layer <NUM>, VNFs <NUM>, Management and Orchestration (MANO) and Mobile Edge Compute (MEC) <NUM>. NFVI hardware <NUM> comprises NICs, CPU, RAM, DRIVE, and 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, and the like. NFVI virtual layer <NUM> comprises vNIC, vCPU, vRAM, vDRIVE, and vSW. VNFs <NUM> comprise Access and Mobility Management Function (AMF) VNF <NUM>, Session Management Function VNF <NUM>, Policy Control Function (PCF) VNF <NUM>, Unified Data Management (UDM) VNF <NUM>, Network Exposure Function (NEF) VNF <NUM>, User Plane Function (UPF) VNF <NUM>, Security Control Function (SCF) VNF <NUM>, and Distributed Ledger (DL) VNF <NUM>. Other VNFs like Network Repository Function (NRF) and Network Slice Selection Function (NSSF) are typically present but omitted for clarity. Wireless network core <NUM> may be located at a single site or be distributed across multiple geographic locations. The NIC transceivers in NFVI hardware <NUM> are coupled to RAN <NUM>, EDN <NUM>, AS <NUM>-<NUM>, and DL <NUM>. NFVI hardware <NUM> executes NFVI hardware drivers <NUM>, NFVI operating systems <NUM>, NFVI virtual layer <NUM>, and VNFs <NUM> to form and operate an AMF, SMF, PCF, UDM, NEF, UPF, SCF, and DL node. Control plane <NUM> on <FIG> comprises an AMF, SMF, PCF, UDM, and NEF in core <NUM>. User plane <NUM> on <FIG> comprises a UPF in core <NUM>. MANO and MEC <NUM> control the MEC Applications and MEC Platforms in EDN <NUM>.

<FIG> illustrates an exemplary operation of <NUM> wireless communication network <NUM> to connect APP <NUM> in UE <NUM> to AS <NUM>. <FIG> respectively describe the core-control plane, edge control-plane, and user-plane operations in more detail. Referring to <FIG>, APP <NUM> in UE <NUM> communicates with AS <NUM> over WIFI <NUM> in UE <NUM>, WIFI <NUM> in GW <NUM>, GAS <NUM> in GW <NUM>, <NUM> <NUM> in GW <NUM>, <NUM> <NUM> in DU <NUM>, <NUM> <NUM> in CU <NUM>, EAS VNF <NUM> in EDN <NUM>, and UPF VNF <NUM> in core <NUM>. GES <NUM> transfers related network data (and possibly digital certificates) to EES VNF <NUM>. EES VNF <NUM> transfers related network data (and possibly digital certificates) to NEF VNF <NUM> over EDGE-<NUM>. NEF VNF <NUM> signals the related network data (and possibly digital certificates) to SCF VNF <NUM>. SCF VNF <NUM>. SCF VNF <NUM> transfers the related network data (and possibly digital certificates) to DL VNF <NUM>. The network data comprises hardware identifiers, network addresses, and possibly digital certificates for APP <NUM>, GAS <NUM>, EAS VNF <NUM>, UPF VNF <NUM>, AS <NUM>, and possibly other components. DL VNF <NUM> interacts with DL <NUM> to determine trust based on the hardware identifiers, network addresses, and possibly digital certificates using MVC and expected value ranges.

<FIG> illustrates an exemplary operation of the network control-plane in <NUM> wireless communication network to connect the user application in the UE to the AS. The operation may vary in other examples. <NUM> <NUM> (RRC) in GW <NUM> attaches to <NUM> <NUM> (RRC) in CU <NUM> over <NUM> <NUM> in DU <NUM>. WIFI <NUM> in UE <NUM> attaches to WIFI <NUM> in GW <NUM>. <NUM> <NUM> in UE <NUM> (RRC) attaches to <NUM> <NUM> (RRC) in CU <NUM>. <NUM> <NUM> (RRC) registers with AMF VNF <NUM>. AMF VNF <NUM> authenticates UE <NUM> and selects slices and policies for UE <NUM>. The slices comprise GAS, EAS, UPF, and AS. AMF VNF <NUM> signals the slices and policies for UE <NUM> to SMF VNF <NUM>. SMF VNF <NUM> drives UPF VNF <NUM> (and possibly other UPFs) to serve UE <NUM> per the slices and policies. AMF VNF <NUM> signals the slices and policies for UE <NUM> to EDN <NUM> - possibly over NEF VNF <NUM>. AMF VNF <NUM> signals the slices and policies for UE <NUM> to <NUM> <NUM> in CU <NUM> for delivery to <NUM> <NUM> in DU <NUM>, <NUM> <NUM> GW <NUM>, and <NUM> <NUM> UE <NUM>.

<FIG> illustrates an exemplary operation of the edge control-plane in <NUM> wireless communication network <NUM> to connect user application <NUM> in UE <NUM> to AS <NUM>. The operation may vary in other examples. NEF VNF <NUM> in core <NUM> and ECS VNF <NUM> in EDN <NUM> exchange EDGE-<NUM> signaling to expose network capabilities like UE location and session quality. NEF VNF <NUM> and EES VNF <NUM> in EDN <NUM> exchange EDGE-<NUM> signaling to expose network capabilities to EES VNF <NUM>. EES VNF <NUM> and GES <NUM> in GW <NUM> exchange EDGE-<NUM> signaling to expose the network capabilities. NEF VNF <NUM> and EAS VNF <NUM> exchange EDGE-<NUM> signaling to configure EAS VNF <NUM> and transfer EAS information to NEF VNF <NUM>. EAS VNF <NUM> and NEF VNF <NUM> exchange EDGE-<NUM> signaling to configure GAS <NUM> and transfer GAS information to NEF VNF <NUM>. EEC <NUM> in GW <NUM> and ECS VNF <NUM> in EDN <NUM> exchange EDGE-<NUM> signaling to provision EEC <NUM> and to discover network information like EES, data network name, and slice from ECS VNF <NUM>. EES VNF <NUM> and ECS VNF <NUM> in EDN <NUM> exchange EDGE-<NUM> signaling to configure EES VNF <NUM> and transfer EES information to ECS VNF <NUM>. GES <NUM> in GW <NUM> and ECS VNF <NUM> in EDN <NUM> exchange EDGE-<NUM> signaling to configure GES <NUM> and transfer GES information to ECS VNF <NUM>.

APP <NUM><NUM> and EEC <NUM> exchange EDGE-<NUM> signaling to initiate service for APP <NUM> over GES <NUM>. EEC <NUM> and GES <NUM> exchange EDGE-<NUM> signaling to register UE <NUM> and discover GAS <NUM>, EAS VNF <NUM>, and AS <NUM>. In addition, GES <NUM> and EES VNF <NUM> exchange EDGE-<NUM> signaling to register UE <NUM> and discover GAS <NUM>, EAS VNF <NUM>, and AS <NUM>. GES <NUM> and GAS <NUM> exchange EDGE-<NUM> signaling to set-up a user data session through GAS <NUM>. EES VNF <NUM> and EAS VNF <NUM> exchange EDGE-<NUM> signaling to set-up the user data session through EAS VNF <NUM>. EES VNF <NUM> and NEF VNF <NUM> exchange EDGE-<NUM> signaling to transfer the network information and possibly digital certificates that characterize the data exchange.

Referring back to <FIG>, SCF VNF <NUM> transfers the network information to DL VNF <NUM>. DL VNF <NUM> starts in a zero trust state and transitions to an alpha trust state for APP <NUM>, GW <NUM>, RAN <NUM>, EDN <NUM>, core <NUM>, and AS <NUM> based on the network information. For example, DL VNF <NUM><NUM> may check a UE ID, GW ID, EDN ID, UPF ID, and AS ID, and their corresponding network addresses against authorized combinations of the IDs and network addresses for the UE location and network slices in use. DL VNF <NUM> uses MVC to transition from zero trust to alpha trust when the network information falls within expected value ranges.

<FIG> illustrates an exemplary operation of the user-plane <NUM> wireless communication network <NUM> to connect APP <NUM> in UE <NUM> to AS <NUM>. The operation may vary in other examples. APP <NUM> and GAS <NUM> exchange user data over WIFI <NUM> and WIFI <NUM> responsive to the EDGE-<NUM> signaling and the EDGE-<NUM> signaling. GAS <NUM> and EAS VNF <NUM> exchange the user data over <NUM> <NUM> and <NUM> <NUM> responsive to EDGE-<NUM> signaling. EAS VNF <NUM> and UPF VNF <NUM> exchange the user data responsive to EDGE-<NUM> signaling and network signaling. UPF VNF <NUM> and AS <NUM> exchange the user data response to network signaling. AS <NUM>, EAS VNF <NUM>, and GAS <NUM> deliver a low-latency service to APP <NUM>.

The wireless data network circuitry described above comprises computer hardware and software that form special-purpose networking circuitry to connect user applications in UEs to AS. 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 networking circuitry to connect user applications in UEs to AS.

Claim 1:
A method of operating a wireless communication network to connect a User Application, APP, (<NUM>) in a User Equipment, UE, (<NUM>) to an Application Server, AS, (<NUM>) the method comprising:
an Edge Enablement Client, EEC, (<NUM>) in a UE Gateway, GW, (<NUM>) exchanging EDGE-<NUM> signaling with the APP in the UE and exchanging EDGE-<NUM> signaling with a Gateway Enablement Server, GES, (<NUM>) in the GW;
the GES exchanging the EDGE-<NUM> signaling with the EEC, exchanging EDGE-<NUM> signaling with an Edge Enablement Server, EES, (<NUM>) in an Edge Data Network, EDN, (<NUM>) and exchanging EDGE-<NUM> signaling with a Gateway Application Server, GAS, (<NUM>) in the GW;
the GAS exchanging the EDGE-<NUM> signaling with the GES and exchanging user data between the APP and an Edge Application Server, EAS, (<NUM>) in the EDN responsive to the EDGE-<NUM> signaling, wherein the APP exchanges the user data responsive to the EDGE-<NUM> signaling;
the EES exchanging the EDGE-<NUM> signaling with the GES and exchanging additional EDGE-<NUM> signaling with the EAS;
the EAS exchanging the additional EDGE-<NUM> signaling with the EES and exchanging the user data between the GAS and a core network, CN, (<NUM>) responsive to the additional EDGE-<NUM> signaling;
the CN exchanging the user data with the EAS, exchanging the user data with the AS, and transferring network information that characterizes the exchange of the user data to a Digital Ledger, DL, node (<NUM>); and
the DL node receiving the network information from the CN and determining trust for the APP, the GW, the EDN, and the CN based on the network information.