Support of analytics for access gateway functions via network data analysis functions

Abstract

Embodiments of the present disclosure relate to supporting analysis for access gateway functions via network data analysis functions. A network device may establish a first interface with a Service Architecture (SBA)-based Network Data Analysis Function (NWDAF), and may establish a second interface with a 3rd Generation Partnership Project (3GPP) access device and a non-3GPP access device. The network device may provide, to the NWDAF and via the first interface, a definition of the analysis data generated by the NWDAF, and may provide, to the NWDAF and via the first interface, raw data of an operating state of the SBA to cause the NWDAF to calculate the analysis data based on the definition and the raw data of the operating state. The network device may receive analysis data from the NWDAF via the first interface and may perform one or more actions based on the analysis data.

Description

[0001] Cross-reference to related applications

[0002] This patent application claims priority to Indian Provisional Patent Application No. 202441045693, filed June 13, 2024, entitled “SUPPORTING ANALYTICS FOR ANACCESS GATEWAY FUNCTION VIA A NETWORK DATA ANALYTICS FUNCTION”, and U.S. Application No. US19 / 090,762, filed March 26, 2025. The disclosure of the earlier applications is considered part of this patent application and is incorporated herein by reference. Background Technology

[0003] The 3rd Generation Partnership Project (3GPP) defines a Service-Based Architecture (SBA), in which the control plane functions and public data repository of a fifth-generation (5G) network are delivered through interconnected sets of network functions (NFs), with each NF authorized to access the services of other NFs. Summary of the Invention

[0004] Some implementations described herein relate to a method. This method may include establishing a first interface with the Network Data Analysis Function (NWDAF) of the SBA, and a second interface with 3GPP access equipment and non-3GPP access equipment. The method may include providing the NWDAF with a definition of analysis data generated by the NWDAF via the first interface, and providing the NWDAF with raw data of the SBA's operational status via the first interface, so that the NWDAF calculates analysis data based on the definition and the raw data of the operational status. The method may include receiving analysis data from the NWDAF via the first interface, and performing one or more actions based on the analysis data.

[0005] Some implementations described herein relate to network devices. A network device may include one or more processors. These processors may be configured to establish a first interface with the NWDAF of the SBA, wherein the first interface is an SBA application programming interface, and to establish a second interface with 3GPP access equipment and non-3GPP access equipment. These processors may be configured to provide the NWDAF with definitions of analytics data generated by the NWDAF via the first interface, and to provide the NWDAF with raw data of the SBA's operational status via the first interface, so that the NWDAF can calculate analytics data based on the definitions and the raw data of the operational status. These processors may also be configured to receive analytics data from the NWDAF via the first interface, and to perform one or more actions based on the analytics data.

[0006] Some implementations described herein involve a non-transitory computer-readable medium storing an instruction set for a network device. When executed by one or more processors of the network device, the instruction set enables the network device to establish a first interface with an SBA-based NWDAF and a second interface with 3GPP access equipment and non-3GPP access equipment, wherein the second interface is a socket interface based on User Datagram Protocol / Internet Protocol. When executed by one or more processors of the network device, the instruction set enables the network device to provide the NWDAF with definitions of analytics data generated by the NWDAF via the first interface, and to provide the NWDAF with raw data of the SBA's operational status via the first interface, so that the NWDAF can compute analytics data based on the definitions and the raw data of the operational status. When executed by one or more processors of the network device, the instruction set enables the network device to receive analytics data from the NWDAF via the first interface and to perform one or more actions based on the analytics data. Attached Figure Description

[0007] Figures 1A to 1D This is a diagram illustrating an example related to analysis supported by the Network Data Analysis Function (NWDAF) for Access Gateway Functions (AGF).

[0008] Figure 2 This is a diagram illustrating an example environment in which the systems and / or methods described in this article can be implemented.

[0009] Figure 3 and Figure 4 yes Figure 2 A diagram illustrating example components of one or more devices.

[0010] Figure 5 This is a flowchart of an exemplary process for supporting analysis for AGF via NWDAF. Detailed Implementation

[0011] The specific implementation of the following example is shown in the accompanying drawings. The same reference numerals in different drawings can identify the same or similar elements.

[0012] SBA provides a cloud-native service framework in which mobile core network functions (e.g., authentication, mobility management, etc.) are supported by NFs (e.g., self-contained software applications running on hardware hosted in the cloud infrastructure). NFs interconnect on a logically shared infrastructure or service bus, providing accessible services to any other authorized NF through application programming interfaces (APIs) such as Service-Based Interfaces (SBIs). API specifications describe the services exposed by an NF to another NF, identifying the accessible service datasets and indicating authorized actions for the service data. Because NFs are loosely coupled and connected to API interfaces, they can be easily deployed anywhere as needed without affecting other NFs. New services or service instances can be published in a centralized repository (e.g., Network Repository Functions (NRFs)). These services can be made available to third-party applications through dedicated NFs (e.g., Network Open Functions (NEFs)). NEFs can provide secure APIs to external or internal applications for access to the core network services and functions supported by the NF.

[0013] Network Data Analysis Function (NWDAF) is designed to simplify the generation and consumption of core network data, generating insights and actions to enhance the end-user experience. NWDAF is a centralized data collection and source for real-time operational intelligence across network elements (NFs), unifying multiple tools into a single, logically centralized, distributed analytics solution. NWDAF can collect data from various NFs and application functions, Operations, Administration and Maintenance (OAM) systems, Operations Support Systems, and more. NWDAF extracts analytical insights from data (e.g., telemetry data, measurements, reference data, etc.) and uses them as analytical services for other NFs and OAM. The output of NWDAF can be consumed by other NFs to enable rapid, automated control loops. In current SBAs, NWDAF provides an interface to all NFs.

[0014] Non-3GPP access equipment may include Wired Access Gateway Function (W-AGF), Non-3GPP Interoperability Function (N3IWF), Trusted Non-3GPP Gateway Function (TNGF), Trusted Radio Local Area Network (WLAN) Interoperability Function (TWIF), etc. Non-3GPP access equipment and radio access networks (RAN) (e.g., 3GPP access equipment) may interface with the 5G control plane solely via the N2 interface with the Access and Mobility Management Function (AMF). Neither non-3GPP nor 3GPP access equipment has a direct interface to the 5G control plane that provides any telemetry data (e.g., for analytics) to the NWDAF. The AMF is unaware of the resources utilized by non-3GPP and 3GPP access equipment, which limits the analytics data exchanged between the AMF and NWDAF. Therefore, current technologies used to support data analytics in SBA consume computing resources (e.g., processing resources, memory resources, communication resources, etc.), network resources, etc., which are associated with the failure to provide an interface between non-3GPP and 3GPP access devices and NWDAF, the failure to generate analytics related to the resource utilization of non-3GPP and 3GPP access devices, and the provision of a poor user experience based on the failure to generate analytics related to the resource utilization of non-3GPP and 3GPP access devices.

[0015] Some implementations described herein involve network devices supporting analysis for AGFs (e.g., non-3GPP access devices and / or 3GPP access devices) via NWDAF. For example, a network device (e.g., an Access Network Data Function (ANDF)) can establish a first interface with the NWDAF of the SBA and a second interface with both 3GPP and non-3GPP access devices. The network device can provide the NWDAF with definitions of analysis data generated by the NWDAF via the first interface, and can also provide the NWDAF with raw data of the SBA's operational status via the first interface, so that the NWDAF can calculate analysis data based on the definitions and the raw data of the operational status. The network device can receive analysis data from the NWDAF via the first interface and can perform one or more actions based on the analysis data.

[0016] In this way, network devices support analytics for AGF via NWDAF. For example, a network device (e.g., ANDF) may include an Application Function (AF) that uses SBA to interface with the NWDAF (e.g., similar to other NFs). The ANDF can define the analytics data to be generated by the NWDAF based on use cases and can provide the NWDAF with the necessary data to generate the defined analytics data. The ANDF can provide an Nxx socket interface between itself and each access device in both non-3GPP and 3GPP access devices. The Nxx socket interface can be based on User Datagram Protocol (UDP) / Internet Protocol (IP) and can be encrypted via Datagram Transport Layer Security (DTLS), Transport Layer Security (TLS), and / or IP Security (IPSec). Therefore, network equipment saves computing and network resources that would otherwise be consumed due to failure to provide an interface between non-3GPP and 3GPP access devices and NWDAF, failure to generate analyses related to the resource utilization of non-3GPP and 3GPP access devices, and providing a poor user experience based on the failure to generate analyses related to the resource utilization of non-3GPP and 3GPP access devices.

[0017] Figures 1A to 1D This is a diagram of Example 100 associated with analysis used for AGF via NWDAF support. (See diagram for example.) Figures 1A to 1DAs shown, Example 100 (e.g., Example SBA) includes a Unified Data Repository (UDR), Unstructured Data Storage Function (UDSF), Network Slice Selection Function (NSSF), Network Repository Function (NRF), NWDAF, Service Communication Agent (SCP), Binding Support Function (BSF), Secure Edge Protection Agent (SEPP), AF, NEF, Charging Function (CHF), Policy Control Function (PCF), Value-Added Services (VAS), Call Session Control Function (CSCF), ANDF, AMF, Short Message Service Function (SMSF), User Equipment Capability Management Function (UCMF), Session Management Function (SMF), Location Management Function (LMF), Gateway Mobility Location Center (GMLC), Device Identity Register (EIR), Authentication Server Function (AUSF), Unified Data Management (UDM), Home Subscriber Server (HSS), RAN, W-AGF, N3IWF, TNGF, TWIF, and User Plane Function (UPF). UDR and UDSF can provide shared data, while NSSF, NRF, and NWDAF can provide network resource management. SCP, BSF, and SEPP can provide signaling, while CHF and PCF can provide policy. VAS and CSCF can be part of the IP Multimedia Subsystem (IMS); RAN, W-AGF, N3IWF, TNGF, and TWIF can be parts of the access network; UPF can be part of the user data / packet gateway connected to the data network. Further details about UDR, UDSF, NSSF, NRF, NWDAF, SCP, BSF, SEPP, AF, NEF, CHF, PCF, VAS, CSCF, ANDF, AMF, SMSF, UCMF, SMF, LMF, GMLC, EIR, AUSF, UDM, HSS, RAN, W-AGF, N3IWF, TNGF, TWIF, UPF, and the data network are provided elsewhere in this document.

[0018] UDR may include data structures (e.g., databases, lists, tables, etc.) that store data grouped into different sets of information about subscriptions, such as subscription data, policy data, structured data for public access, application data, etc. UDSF may include data structures that support data storage for stateless network functions (e.g., user equipment (UE) context data). NSSF includes one or more devices that select network slice instances. By providing network slices, NSSF allows operators to deploy multiple largely independent end-to-end networks that may share the same infrastructure. In some implementations, each slice can be customized for different services.

[0019] The NRF may include a data structure that provides a centralized repository for all NFs and allows NFs to register and discover each other. The NWDAF may include a centralized data collection and source for real-time operational intelligence about NFs, and may collect data from various NFs and application functions, OAM systems, operations support systems, etc. The SCP may include NFs that enable communication and services in the SBA to be dynamically scaled and managed. The BSF may include one or more devices that allow PCFs to register, update, and delete binding information, and allow NF consumers to discover PCFs. The SEPP may include one or more devices that enable secure interconnection between 5G networks. The SEPP can ensure end-to-end confidentiality and / or integrity between all 5G interconnection roaming message source and destination networks.

[0020] An AF (Action Center) may include one or more devices that support application effects such as service routing, access to the NEF (Network Provider Framework), and policy control. A NEF (Network Provider Framework) may include one or more devices that support the opening of capabilities and / or events within a wireless telecommunications system to help other entities within the system discover network services. A CHF (Callable Credit Function) may include one or more devices that provide converged online and offline billing for services. A PCF (Policy Framework) may include one or more devices that provide a policy framework that incorporates network slicing, roaming, packet processing, and / or mobility management, among other examples. A VAS (Vehicle Application Server) may include one or more devices that provide customers with services beyond the core services offered by the SBA (Service Provider Framework). A CSCF (Customer Service Provider Framework) may include one or more devices that perform registration and session control for registered UEs and provide UE network location information at the HSS (Host Service).

[0021] The ANDF may include one or more devices that interface with the NWDAF using the SBA. The ANDF can define analytics data to be generated by the NWDAF based on use cases and can provide the NWDAF with the necessary data to generate the defined analytics data. The ANDF may provide an Nxx socket interface between itself and each access device in both non-3GPP and 3GPP access devices. The Nxx socket interface may be based on UDP / IP and may be encrypted via DTLS, TLS, and / or IPSec. The AMF may include one or more devices that serve as endpoints for Non-Access Stratum (NAS) signaling and / or mobility management. The SMSF may include one or more devices that send Short Message Service (SMS) messages between users and devices in the SBA and users and devices in other networks.

[0022] The UCMF may include one or more devices that store the capability dictionary of the connected UEs and provide this information to other NFs. The SMF may include one or more devices that support the establishment, modification, and release of communication sessions in a wireless telecommunications system. For example, the SMF may configure traffic redirection policies at the UPF and / or implement user equipment IP address allocation and policies, among other examples. The LMF may include one or more devices that provide positioning functionality to determine the geographic location of the UE based on downlink and uplink location measurements of radio signals. The GMLC may include one or more devices that provide the functionality required to support location-based services (LBS).

[0023] The EIR may include one or more devices that support checking the status of the UE's identity (e.g., checking where the UE is blacklisted). The AUSF may include one or more devices that act as an authentication server and support the process of authenticating the UE in the wireless telecommunications system. The UDM may include one or more devices that store user data and profiles in the wireless telecommunications system. The UDM device may be used for fixed access and / or mobile access in the core network. The HSS may include data structures that store information associated with network subscribers. The RAN may support, for example, Cellular Radio Access Technology (RAT) and may include one or more base stations and other network entities that can support wireless communication for the UE.

[0024] W-AGF may include one or more devices similar to RAN and relaying data services between the routing gateway and UPF. N3IWF may include one or more devices acting as a gateway for SBA and providing secure connectivity for UEs accessing the SBA via a non-3GPP access network. TNGF may include one or more devices providing trusted access to the SBA from a non-3GPP access network. TWIF may include one or more devices providing trusted access to the SBA from a non-3GPP access network. UPF may include one or more devices acting as an anchor point for mobility within and / or between RATs. UPF may apply rules to packets, such as rules related to packet routing, traffic reporting, and / or handling user plane quality of service (QoS), among other examples.

[0025] like Figure 1B As shown, and as indicated by reference numeral 105 in the attached figure, the ANDF can establish a first interface with the NWDAF. For example, the ANDF can be a new NF or AF that uses SBA to interface with the NWDAF, just like other NFs. In some implementations, a first interface (e.g., referred to as N) can be defined for the NF (e.g., including the NWDAF). ANDF The SBA API (interface) is used to interface with ANDF for analyzing data delivery and access. ANDFThe interface can also connect to NEF for secure communication between NFs.

[0026] like Figure 1B As further shown, and as indicated by reference numeral 110 in the accompanying drawings, the ANDF can establish a second interface with 3GPP access devices and non-3GPP access devices. For example, a second interface (e.g., an Nxx socket interface) can be provided between the ANDF and 3GPP access devices and non-3GPP access devices (e.g., RAN, W-AGF, N3IWF, TNGF, TWIF, etc.). The Nxx socket interface can be based on UDP / IP. The ANDF can utilize this second interface to receive telemetry data from 3GPP access devices and non-3GPP access devices, as described below.

[0027] like Figure 1C As shown, and as indicated by reference numeral 115 in the attached figure, the ANDF can provide the NWDAF with definitions of the analytics data to be generated by the NWDAF via a first interface. For example, the ANDF can define the analytics data to be generated by the NWDAF based on use cases associated with the SBA, and can generate definitions of the analytics data. In some implementations, the definitions can define analytics data such as network data analytics data, network function load analytics data, network performance analytics data, UE-related analytics data, congestion analytics data, quality of service (QoS) sustainability analytics data, session management congestion experience analytics data, redundant transmission experience-related analytics data, end-to-end data volume transmission time analytics data, protocol data unit (PDU) session service analytics data, etc. In some implementations, the ANDF can provide the definitions of the analytics data to the NWDAF using the first interface.

[0028] like Figure 1C As further shown in the figure, and as indicated by reference numeral 120, the ANDF can provide the NWDAF with raw data (e.g., SBA data) of the operational status associated with the SBA via a first interface. For example, the ANDF can receive raw operational status data from components of the SBA. In some implementations, the raw operational status data may include network data, network function load, network performance data, UE-related data, congestion data, QoS sustainability data, session management congestion experience data, redundant transmission experience-related data, end-to-end data volume transmission time data, PDU session service data, etc. The ANDF can provide the raw operational status data to the NWDAF using the first interface. The NWDAF can use the raw operational status data to generate defined analytical data.

[0029] like Figure 1CAs further shown in the figure, and as indicated by reference numeral 125, NWDAF can calculate analytical data based on raw data of defined and operational states. For example, NWDAF can also receive data from OAM systems, operation support systems, etc. NWDAF can process raw data of operational states and any additional data to calculate analytical data defined by the definition. In some implementations, NWDAF can calculate service experience-related network data analytical data (e.g., application, network slicing, UE, etc.), NF load analytical data, network performance analytical data, UE-related analytical data (e.g., mobility, communication, behavior-related, abnormal behavior-related, etc.), user congestion analytical data, QoS sustainability analytical data, session management congestion experience analytical data, redundant transmission experience-related analytical data, data network performance analytical data, end-to-end data volume transmission time analytical data, PDU session service analytical data, etc.

[0030] like Figure 1C As further shown in the figure, and as indicated by reference numeral 130, the ANDF can receive analysis data from the NWDAF via a first interface. For example, after calculating the analysis data, the NWDAF can provide the analysis data to the ANDF using the first interface. The ANDF can receive the analysis data via the first interface and can store the analysis data in a data structure (e.g., a database, table, list, etc.) associated with the ANDF.

[0031] like Figure 1C As further shown in the figure, and as indicated by reference numeral 135, the ANDF can perform one or more actions based on the analyzed data. For example, the ANDF can review the analyzed data and determine one or more actions to be performed based on the reviewed analyzed data. The ANDF can enable one or more actions to be performed within the SBA. In some implementations, performing one or more actions may include the ANDF calculating the service experience. For example, the ANDF can determine, based on the analyzed data, that the network function of the SBA is providing a poor service experience to the UE. The ANDF can identify solutions for the poor service experience and enable the network function to implement the solution.

[0032] In some implementations, performing one or more actions may include the ANDF adjusting the load on a network function. For example, the ANDF may determine, based on analytics data, that the load on a network function is too high and may instruct the network function to shift some load to another network function. In some implementations, performing one or more actions may include the ANDF correcting network performance problems. For example, the ANDF may determine, based on analytics data, that a network function is causing a network performance problem. The ANDF may then service or replace the network function to resolve the network performance problem. In some implementations, performing one or more actions may include the ANDF correcting UE performance problems. For example, the ANDF may identify UE performance problems based on analytics data and may provide the UE with a software update to resolve the UE performance problem.

[0033] In some implementations, performing one or more actions may include the ANDF handling network congestion. For example, based on analytics data, the ANDF can identify the portion of the SBA experiencing network congestion and redirect services away from that portion of the SBA. In some implementations, performing one or more actions may include the ANDF resolving QoS sustainability issues. For example, the ANDF can determine, based on analytics data, that the RAN is causing QoS sustainability issues and can servicing the RAN to resolve these issues. In some implementations, performing one or more actions may include the ANDF handling session management congestion. For example, based on analytics data, the ANDF can identify the portion of the SBA causing session management congestion and redirect services away from that portion of the SBA.

[0034] like Figure 1D As shown in the figure, and as indicated by reference numeral 140, the ANDF can receive telemetry data from 3GPP access devices and non-3GPP access devices via a second interface. For example, 3GPP access devices and non-3GPP access devices can generate telemetry data and provide it to the ANDF via the second interface (e.g., an Nxx socket interface). The ANDF can receive telemetry data via the second interface. In some implementations, the telemetry data can be generated as a protocol buffer structured message, and the data model (e.g., the OpenConfig data model) can generate the telemetry data as a structured message in a generic key / value format. In some implementations, remote procedure calls (e.g., RPCs) can be used to provide sensors and subscribe to and receive telemetry data from 3GPP access devices and non-3GPP access devices. In some implementations, when telemetry data is received, the ANDF can receive telemetry data in batches from 3GPP access devices and non-3GPP access devices, receive telemetry data in chunks from 3GPP access devices and non-3GPP access devices, or periodically receive portions of telemetry data from one or more settings of 3GPP access devices and non-3GPP access devices.

[0035] like Figure 1D Further, and as indicated by reference numeral 145 in the accompanying drawings, the ANDF can provide telemetry data to the NWDAF via the first interface. For example, when the ANDF receives telemetry data from a 3GPP access device and a non-3GPP access device, the ANDF can use the first interface to provide the telemetry data to the NWDAF. The NWDAF can use the telemetry data to generate additional analytics data, as described below.

[0036] like Figure 1D As further shown in the figure, and as indicated by reference numeral 150, NWDAF can calculate additional analytics data based on telemetry data. For example, NWDAF can process telemetry data as well as any additional data to calculate additional analytics data. In some implementations, the additional analytics data may include network data analytics data related to service experience (e.g., application, network slicing, UE, etc.), NF load analytics data, network performance analytics data, UE-related analytics data (e.g., mobility, communication, behavior-related, abnormal behavior-related, etc.), user congestion analytics data, QoS sustainability analytics data, session management congestion experience analytics data, redundant transmission experience-related analytics data, data network performance analytics data, end-to-end data volume transmission time analytics data, PDU session service analytics data, etc.

[0037] like Figure 1D As further shown, and as indicated by reference numeral 155 in the accompanying drawings, the ANDF can receive additional analysis data from the NWDAF via a first interface. For example, after calculating the additional analysis data, the NWDAF can provide the additional analysis data to the ANDF using the first interface. The ANDF can receive the additional analysis data via the first interface and can store the additional analysis data in a data structure associated with the ANDF.

[0038] like Figure 1DAs further shown, and as indicated by reference numeral 160 in the accompanying drawings, the ANDF can perform one or more additional actions based on additional analytics data. For example, the ANDF can examine the additional analytics data and determine one or more additional actions to be performed based on the examined data. The ANDF can then perform one or more additional actions within the SBA. In some implementations, the one or more additional actions may include actions similar to those performed based on analytics data. In some implementations, the one or more additional actions may include actions to resolve any issues with 3GPP access devices and non-3GPP access devices, as identified by telemetry data received from the 3GPP access devices and non-3GPP access devices. For example, the ANDF can determine RAN traffic overload based on additional analytics data and can cause the RAN to offload some traffic to another RAN. In another example, the ANDF can determine that a non-3GPP access device is offline based on additional analytics data and can cause a technician to be dispatched to handle the offline non-3GPP access device.

[0039] In this way, network devices support analytics for AGF via NWDAF. For example, a network device (e.g., ANDF) may include an AF that interfaces with the NWDAF (e.g., similar to other NFs) using SBA. The ANDF can define analytics data generated by the NWDAF based on use case definitions and can provide the NWDAF with the necessary data to generate the defined analytics data. The ANDF can provide an Nxx socket interface between itself and each access device in both non-3GPP and 3GPP access devices. The Nxx socket interface can be based on UDP / IP. Therefore, network devices save computing and network resources that would otherwise be consumed by failing to provide an interface between non-3GPP and 3GPP access devices and the NWDAF, failing to generate analytics associated with the resource utilization of non-3GPP and 3GPP access devices, and providing a poor user experience based on the failure to generate analytics associated with the resource utilization of non-3GPP and 3GPP access devices.

[0040] As mentioned above, Figures 1A to 1D This is provided as an example. Other examples may differ from the one provided. Figures 1A to 1D The example described. Figures 1A to 1D The number and arrangement of the devices shown are provided as an example. In reality, with... Figures 1A to 1D Compared to the illustrated device, it can have additional equipment, fewer devices, different devices, or devices arranged differently. Furthermore, Figures 1A to 1D The two or more devices shown can be implemented within a single device, or Figures 1A to 1DThe single device shown can be implemented as multiple distributed devices. Additional or alternative locations, Figures 1A to 1D The set of devices shown (e.g., one or more devices) can perform actions described as being performed by Figures 1A to 1D One or more functions performed by another set of devices shown.

[0041] Figure 2 This is a diagram illustrating an example environment 200 in which the systems and / or methods described herein can be implemented. For example... Figure 2 As shown, example environment 200 may include non-3GPP access equipment 205, RAN 210, core network 215, and data network 280. The devices and / or networks of example environment 200 may be interconnected via wired connections, wireless connections, or a combination of wired and wireless connections.

[0042] Non-3GPP access equipment 205 may include one or more devices that access the core network 215 via Wi-Fi, WiMAX, etc. For example, non-3GPP access equipment 205 may include wired access gateway function (W-AGF), non-3GPP interoperability function (N3IWF), trusted non-3GPP gateway function (TNGF), trusted wireless local area network (WLAN) interoperability function (TWIF), etc.

[0043] RAN 210 may support, for example, a cellular RAT. RAN 210 may include one or more base stations (e.g., base transceivers, radio base stations, Node Bs, (multiple) eNodeBs (eNBs), (multiple) gNodeBs (gNBs), base station subsystems, cellular sites, cell towers, access points, transmit / receive points (TRPs), radio access nodes, macrocell base stations, microcell base stations, picocell base stations, femtocell base stations, or similar devices) and other network entities that can support wireless communication for the UE. RAN 210 can transmit services between the UE (e.g., using a cellular RAT), one or more base stations (e.g., using a radio interface or backhaul interface, such as a wired backhaul interface) and / or the core network 215. RAN 210 can provide one or more cells covering a geographic area.

[0044] In some implementations, RAN 210 can perform scheduling and / or resource management for UEs covered by RAN 210 (e.g., UEs covered by cells provided by RAN 210). In some implementations, RAN 210 can be controlled or coordinated by a network controller, which can perform load balancing, network-level configuration, and / or other operations. The network controller can communicate with RAN 210 via radio or wired backhaul. In some implementations, RAN 210 may include a network controller, an Ad Hoc Network (SON) module or component, or a similar module or component. In other words, RAN 210 can perform network control, scheduling, and / or network management functions (e.g., uplink, downlink, and / or sidelink communication for UEs covered by RAN 210).

[0045] In some implementations, core network 215 may include example functional architectures in which the systems and / or methods described herein can be implemented. For example, core network 215 may include an example architecture of a 5G next-generation (NG) core network included in a 5G wireless telecommunications system. Although Figure 2 The exemplary architecture of the core network 215 shown may be an example of a service-based architecture, but in some implementations, the core network 215 may be implemented as a reference point architecture and / or a 4G core network, among other examples.

[0046] like Figure 2 As shown, the core network 215 may include multiple functional elements. These functional elements may include, for example, a Network Slice Selection Function (NSSF) 220, a NEF 225, an Authentication Server Function (AUSF) 230, a UDM device 235, a PCF 240, an AF 245, an AMF 250, an SMF 255, a UPF 260, an NWDAF 265, and / or an ANDF 270. These functional elements can be communicatively connected via a message bus 275. Figure 2 Each of the functional elements shown can be implemented on one or more devices associated with a wireless telecommunications system. In some implementations, one or more functional elements can be implemented on physical devices such as access points, base stations, and / or gateways. In some implementations, one or more functional elements can be implemented on computing devices in a cloud computing environment.

[0047] The NSSF 220 includes one or more devices that select network slice instances for the UE. By providing network slices, the NSSF 220 allows operators to deploy multiple largely independent end-to-end networks that potentially have the same infrastructure. In some implementations, each slice can be customized for different services.

[0048] NEF 225 includes one or more devices that support capabilities and / or events in open wireless telecommunications systems to help other entities in the wireless telecommunications system discover network services.

[0049] AUSF 230 includes one or more devices that serve as authentication servers and support the process of authenticating UEs in wireless telecommunications systems.

[0050] UDM device 235 includes one or more devices that store user data and profiles in a wireless telecommunications system. UDM device 235 can be used for fixed access and / or mobile access in core network 215.

[0051] The PCF 240 includes one or more devices that provide a policy framework that combines network slicing, roaming, packet processing, and / or mobility management, among other examples.

[0052] AF 245 includes one or more devices that support application impacts on traffic routing, access to NEF 225 and / or policy control, as well as other examples.

[0053] The AMF 250 includes one or more devices that serve as endpoints for non-access stratum (NAS) signaling and / or mobility management, as well as other examples.

[0054] The SMF 255 includes one or more devices that support the establishment, modification, and release of communication sessions in a wireless telecommunications system. For example, the SMF 255 can configure traffic redirection policies and / or implement user equipment IP address allocation and policies at the UPF260, among other examples.

[0055] UPF 260 includes one or more devices that serve as anchors for mobility within and / or between RATs. UPF 260 can apply rules to packets, such as rules related to packet routing, traffic reporting, and / or handling user plane QoS, among other examples.

[0056] NWDAF 265 includes one or more devices that collect data from the core network 215, cloud computing environment, edge network, etc., from UE, network function, operation, management and maintenance (OAM) system, etc., and use the data for analysis.

[0057] ANDF 270 includes one or more devices that support analysis generated by NWDAF 265 for AGF (e.g., non-3GPP access device 205 and / or RAN 210).

[0058] Message bus 275 represents a communication structure used for communication between functional elements. In other words, message bus 275 can allow communication between two or more functional elements.

[0059] Data network 280 includes one or more wired and / or wireless data networks. For example, data network 280 may include IP Multimedia Subsystem (IMS), Public Land Mobile Network (PLMN), Local Area Network (LAN), Wide Area Network (WAN), Metropolitan Area Network (MAN), private networks such as corporate intranets, self-organizing networks, the Internet, fiber-optic networks, cloud computing networks, third-party service networks, operator service networks, and / or combinations of these or other types of networks.

[0060] Figure 2 The number and arrangement of devices and networks shown are provided as examples. In reality, there may be additional devices and / or networks, fewer devices and / or networks, different devices and / or networks, or [other arrangements]. Figure 2 The devices and / or networks shown are arranged differently. Furthermore, Figure 2 The two or more devices shown can be implemented within a single device, or Figure 2 The single device shown can be implemented as multiple distributed devices. Additionally or alternatively, the set of devices in example environment 200 (e.g., one or more devices) can perform one or more functions described as being performed by another set of devices in example environment 200.

[0061] Figure 3 This is a diagram illustrating example components of device 300, which may correspond to non-3GPP access devices 205, RAN 210, NSSF 220, NEF 225, AUSF 230, UDM device 235, PCF 240, AF 245, AMF 250, SMF 255, UPF 260, NWDAF 265, and / or ANDF 270. In some implementations, non-3GPP access devices 205, RAN 210, NSSF 220, NEF 225, AUSF 230, UDM device 235, PCF 240, AF 245, AMF 250, SMF 255, UPF 260, NWDAF 265, and / or ANDF 270 may include one or more devices 300 and / or one or more components of device 300. Figure 3 As shown, device 300 may include bus 310, processor 320, memory 330, input component 340, output component 350 and communication component 360.

[0062] Bus 310 includes one or more components that enable wired and / or wireless communication between components of device 300. Bus 310 can... Figure 3Two or more components are coupled together, such as via operational coupling, communication coupling, electronic coupling, and / or electrical coupling. Processor 320 includes a central processing unit (CPU), graphics processing unit (GPU), accelerated processing unit (APU), microprocessor, controller, microcontroller, digital signal processor (DSP), field-programmable gate array (FPGA), application-specific integrated circuit (ASIC), and / or other types of processing components. Processor 320 is implemented in hardware, firmware, or a combination of hardware and software. In some implementations, processor 320 includes one or more processors capable of being programmed to perform one or more operations or processes described elsewhere herein.

[0063] Memory 330 includes volatile and / or non-volatile memory. For example, memory 330 may include random access memory (RAM), read-only memory (ROM), hard disk drive, and / or other types of memory (e.g., flash memory, magnetic storage, and / or optical storage). Memory 330 may include internal memory (e.g., RAM, ROM, or hard disk drive) and / or removable memory (e.g., removable memory connected via a universal serial bus). Memory 330 may be a non-transitory computer-readable medium. Memory 330 stores information, instructions, and / or software (e.g., one or more software applications) related to the operation of device 300. In some implementations, memory 330 includes one or more memories, such as those coupled to one or more processors (e.g., processor 320) via bus 310.

[0064] Input component 340 enables device 300 to receive input, such as user input and / or sensed input. For example, input component 340 may include a touchscreen, keyboard, keypad, mouse, button, microphone, switch, sensor, GPS sensor, accelerometer, gyroscope, and / or actuator. Output component 350 enables device 300 to provide output, for example, via a display, speaker, and / or light-emitting diode. Communication component 360 enables device 300 to communicate with other devices via wired and / or wireless connections. For example, communication component 360 may include a receiver, transmitter, transceiver, modem, network interface card, and / or antenna.

[0065] Device 300 can perform one or more operations or procedures described herein. For example, a non-transitory computer-readable medium (e.g., memory 330) can store a set of instructions (e.g., one or more instructions or code) that can be executed by processor 320. Processor 320 can execute the set of instructions to perform one or more operations or procedures described herein. In some implementations, execution of the set of instructions by one or more processors 320 causes one or more processors 320 and / or device 300 to perform one or more operations or procedures described herein. In some implementations, hardwired circuitry may be used in place of or in combination with instructions to perform one or more operations or procedures described herein. Additionally or alternatively, processor 320 may be configured to perform one or more operations or procedures described herein. Therefore, the implementations described herein are not limited to any particular combination of hardware circuitry and software.

[0066] Figure 3 The number and arrangement of components shown are provided as an example. Device 300 may include... Figure 3 The components shown are fewer, different, or arranged differently compared to additional components. Additionally or alternatively, the set of components of device 300 (e.g., one or more components) can perform one or more functions described as being performed by another set of components of device 300.

[0067] Figure 4 yes Figure 2 A diagram illustrating example components of one or more devices. Example components may be included in device 400. Device 400 may correspond to non-3GPP access device 205 and / or ANDF 270. In some implementations, non-3GPP access device 205 and / or ANDF 270 may include one or more devices 400 and / or one or more components of device 400. Figure 4 As shown, device 400 may include one or more input components 410-1 to 410-B (B≥1) (hereinafter collectively referred to as input components 410, and individually referred to as input components 410), switching component 420, one or more output components 430-1 to 430-C (C≥1) (hereinafter collectively referred to as output components 430, and individually referred to as output components 430), and controller 440.

[0068] Input component 410 may be one or more connection points for a physical link and one or more entry points for input services (e.g., packets). Input component 410 may process input services, for example, by performing data link layer encapsulation or decapsulation. In some implementations, input component 410 may transmit and / or receive packets. In some implementations, input component 410 may include an input line card that includes one or more packet processing components (e.g., in the form of an integrated circuit), such as one or more interface cards (IFCs), packet forwarding components, line card controller components, input ports, processors, memory, and / or input queues. In some implementations, device 400 may include one or more input components 410.

[0069] Switching component 420 interconnects input component 410 with output component 430. In some implementations, switching component 420 may be implemented via one or more crossbar switches, via a bus, and / or utilizing shared memory. Shared memory may be used as a temporary buffer to store packets from input component 410 before final scheduling packets for delivery to output component 430. In some implementations, switching component 420 may enable input component 410, output component 430, and / or controller 440 to communicate with each other.

[0070] Output component 430 can store packets and schedule packets for transmission on the output physical link. Output component 430 can support data link layer encapsulation or decapsulation, and / or various higher-layer protocols. In some implementations, output component 430 can transmit and / or receive packets. In some implementations, output component 430 may include an output line card that includes one or more packet processing components (e.g., in the form of integrated circuits), such as one or more IFCs, packet forwarding components, line card controller components, output ports, processors, memory, and / or output queues. In some implementations, device 400 may include one or more output components 430. In some implementations, input component 410 and output component 430 may be implemented from the same set of components (e.g., the input / output component may be a combination of input component 410 and output component 430).

[0071] Controller 440 includes processors in the form of, for example, CPUs, GPUs, APUs, microprocessors, microcontrollers, DSPs, FPGAs, ASICs, and / or other types of processors. The processor is implemented in hardware, firmware, or a combination of hardware and software. In some implementations, controller 440 may include one or more processors that can be programmed to perform functions.

[0072] In some implementations, controller 440 may include RAM, ROM, and / or another type of dynamic or static storage device (e.g., flash memory, magnetic storage, optical storage, etc.) that stores information and / or instructions used by controller 440.

[0073] In some implementations, controller 440 can communicate with other devices, networks, and / or systems connected to device 400 to exchange information about the network topology. Controller 440 can create routing tables based on the network topology information, create forwarding tables based on the routing tables, and forward the forwarding tables to input component 410 and / or output component 430. Input component 410 and / or output component 430 can use the forwarding tables to perform route looks for input and / or output packets.

[0074] Controller 440 may execute one or more processes described herein. Controller 440 may execute these processes in response to executing software instructions stored in a non-transitory computer-readable medium. A computer-readable medium is defined herein as a non-transitory storage device. A memory device includes memory space within a single physical storage device or memory space distributed across multiple physical storage devices.

[0075] Software instructions may be read from another computer-readable component or from another device via a communication component into memory and / or storage components associated with controller 440. When executed, the software instructions stored in the memory and / or storage components associated with controller 440 may cause controller 440 to perform one or more processes described herein. Additionally or alternatively, hard-wired circuitry may be used in place of or in conjunction with the software instructions to perform one or more processes described herein. Therefore, the implementation described herein is not limited to any particular combination of hardware circuitry and software.

[0076] Figure 4 The number and arrangement of components shown are provided as an example. In practice, device 400 may include components with... Figure 4 The components shown may be additional components, fewer components, different components, or components with different arrangements. Additionally or alternatively, the set of components of device 400 (e.g., one or more components) may perform one or more functions described as being performed by another set of components of device 400.

[0077] Figure 5 This is a flowchart of an exemplary process 500 for supporting analysis for AGF via NWDAF. In some implementations, Figure 5 One or more processing blocks can be executed by a network device (e.g., ANDF 270). In some implementations, Figure 5One or more processing blocks can be executed by another device or a group of devices that are separate from or include the network device, such as a non-3GPP access device (e.g., non-3GPP access device 205), a RAN (e.g., RAN 210), etc. Additionally or alternatively, Figure 5 One or more processing blocks can be executed by one or more components of device 300, such as processor 320, memory 330, input component 340, output component 350, and / or communication component 360. Additionally or alternatively, Figure 5 One or more processing blocks can be executed by one or more components of the device 400, such as input component 410, switching component 420, output component 430 and / or controller 440.

[0078] like Figure 5 As shown, process 500 may include establishing a first interface with the SBA's NWDAF (block 510). For example, as described above, the network device may establish a first interface with the SBA's NWDAF. In some implementations, the first interface is the SBA application programming interface. In some implementations, the network device is an ANDF (Application Programming Interface).

[0079] like Figure 5 As further shown, process 500 may include establishing a second interface with 3GPP access devices and non-3GPP access devices (block 520). For example, as described above, the network device may establish a second interface with 3GPP access devices and non-3GPP access devices. In some implementations, the second interface is a socket interface based on User Datagram Protocol / Internet Protocol. In some implementations, the 3GPP access devices and non-3GPP access devices include one or more access devices selected from RAN, W-AGF, N3IWF, TNGF, or TWIF.

[0080] like Figure 5 As further shown, process 500 may include providing the definition of analytics data generated by the NWDAF to the NWDAF and via a first interface (block 530). For example, as described above, the network device may provide the definition of analytics data generated by the NWDAF to the NWDAF and via a first interface. In some implementations, the analytics data includes one or more of the following: network data analytics data, network function load analytics data, network performance analytics data, user equipment-related analytics data, congestion analytics data, quality of service sustainability analytics data, session management congestion experience analytics data, redundant transmission experience-related analytics data, end-to-end data volume transmission time analytics data, or protocol data unit session service analytics data. In some implementations, the definition of the analytics data is based on use cases associated with the SBA.

[0081] like Figure 5As further shown, process 500 may include providing raw data of the SBA's operational status to the NWDAF and via a first interface, so that the NWDAF can calculate analytical data based on the definition and the raw data of the operational status (block 540). For example, the network device may provide raw data of the SBA's operational status to the NWDAF and via a first interface, so that the NWDAF can calculate analytical data based on the definition and the raw data of the operational status, as described above.

[0082] like Figure 5 As further shown, process 500 may include receiving analysis data from the NWDAF and via a first interface (block 550). For example, as described above, the network device may receive analysis data from the NWDAF via the first interface.

[0083] like Figure 5 As further shown, process 500 may include performing one or more actions based on the analyzed data (box 560). For example, as described above, the network device may perform one or more actions based on the analyzed data. In some implementations, performing one or more actions includes calculating service experience, adjusting load on network functions, correcting network performance problems, correcting user equipment performance problems, handling network congestion, resolving quality of service sustainability issues, or handling session management congestion, among other things.

[0084] In some implementations, process 500 includes receiving telemetry data from a 3GPP access device and a non-3GPP access device via a second interface, providing the telemetry data to the NWDAF and via a first interface to enable the NWDAF to calculate additional analytics data based on the telemetry data, receiving the additional analytics data from the NWDAF and via the first interface, and performing one or more additional actions based on the additional analytics data. In some implementations, the telemetry data includes protocol buffer structured messages in a generic key / value format. In some implementations, receiving telemetry data from a 3GPP access device and a non-3GPP access device includes one of the following: receiving telemetry data in batches from a 3GPP access device and a non-3GPP access device, receiving telemetry data in chunks from a 3GPP access device and a non-3GPP access device, or receiving telemetry data periodically from one or more of the 3GPP access devices and non-3GPP access devices.

[0085] In some implementations, the additional analytical data includes one or more of the following: network data analysis data, network function load analysis data, network performance analysis data, user equipment-related analysis data, congestion analysis data, quality of service sustainability analysis data, session management congestion experience analysis data, redundant transmission experience-related analysis data, end-to-end data volume transmission time analysis data, or protocol data unit session service analysis data. In some implementations, procedure 500 includes establishing a first interface with the SBA's NEF.

[0086] Although Figure 5 The example box for process 500 is shown, but in some implementations, process 500 may include... Figure 5 The blocks depicted in the diagram are compared to additional boxes, fewer boxes, different boxes, or boxes with different arrangements. Alternatively, two or more boxes in process 500 can be executed in parallel.

[0087] The foregoing disclosure provides illustrations and descriptions, but is not intended to be exhaustive or to limit implementations to the precise forms disclosed. Modifications may be made based on the foregoing disclosure, or modifications may be derived from practical implementations.

[0088] As used herein, the term "component" is intended to be broadly interpreted as hardware, firmware, or a combination of hardware and software. Clearly, the systems and / or methods described herein can be implemented in various forms of hardware, firmware, and / or combinations of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods is not a limitation on the implementation. Therefore, this document describes the operation and behavior of the systems and / or methods without reference to any specific software code—it should be understood that software and hardware can be used to implement the systems and / or methods based on the description herein.

[0089] Although specific combinations of features are recited in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various implementations. In fact, many of these features can be combined in ways not specifically listed in the claims and / or disclosed in the specification. While each dependent claim listed below may directly depend on only one claim, the disclosure of various implementations includes every dependent claim in combination with all other claims in the claim set.

[0090] The elements, actions, or instructions used herein should not be construed as critical or necessary unless explicitly stated otherwise. Furthermore, as used herein, the articles “a” and “one” are intended to include one or more items and may be used interchangeably with “one or more.” Furthermore, as used herein, the article “the” is intended to include one or more items associated with the article “the” and may be used interchangeably with “the one or more.” Furthermore, as used herein, the term “set” is intended to include one or more items (e.g., related items, unrelated items, a combination of related and unrelated items, etc.) and may be used interchangeably with “one or more.” Where only one item is intended, the phrase “only one” or similar language is used. Furthermore, as used herein, the terms “having,” “possessing,” “having,” etc., are intended to be open-ended terms. Furthermore, the phrase “based on” is intended to mean “at least partially based on” unless explicitly stated otherwise. Furthermore, as used herein, the term “or this” when used serially is intended to be inclusive and may be used interchangeably with “and / or” unless explicitly stated otherwise (e.g., if used in combination with “any” or “only one”).

[0091] Various exemplary embodiments have been described in the foregoing description with reference to the accompanying drawings. However, it is clear that various modifications and changes can be made thereto, and additional embodiments can be implemented without departing from the wider scope of the invention as set forth in the following claims. Therefore, the description and drawings are to be considered illustrative rather than restrictive.

[0092] The following embodiments are disclosed:

[0093] Example 1. A method comprising:

[0094] The first interface between the network device and the Network Data Analysis Function (NWDAF) based on Service Architecture (SBA) is established;

[0095] The network equipment establishes a second interface with 3GPP access devices and non-3GPP access devices.

[0096] The network device provides the definition of the analysis data generated by the NWDAF to the NWDAF and via the first interface;

[0097] The network device provides the NWDAF with raw data on the operational status of the SBA via the first interface, so that the NWDAF can calculate the analysis data based on the definition and the raw data on the operational status;

[0098] The network device receives the analysis data from the NWDAF and via the first interface; and

[0099] The network device performs one or more actions based on the analyzed data.

[0100] Example 2. The method according to Example 1 further includes:

[0101] Telemetry data is received from the 3GPP access device and the non-3GPP access device via the second interface;

[0102] The telemetry data is provided to the NWDAF and via the first interface, so that the NWDAF calculates additional analytical data based on the telemetry data;

[0103] Receive the additional analysis data from the NWDAF and via the first interface; and

[0104] One or more additional actions are performed based on the additional analytical data.

[0105] Example 3. The method according to Example 2, wherein the telemetry data includes a protocol buffer structured message in a general key / value format.

[0106] Example 4. The method according to Example 2, wherein receiving the telemetry data from the 3GPP access device and the non-3GPP access device includes one of the following:

[0107] The telemetry data is received in batches from the 3GPP access device and the non-3GPP access device.

[0108] The telemetry data is received in blocks from the 3GPP access device and the non-3GPP access device; or

[0109] A portion of the telemetry data is periodically received from one or more of the 3GPP access devices and the non-3GPP access devices.

[0110] Example 5. The method according to Example 2, wherein the additional analytical data includes one or more of the following:

[0111] Network analysis data,

[0112] Network function load analysis data,

[0113] Network performance analysis data,

[0114] Analysis data related to user equipment

[0115] Congestion analysis data,

[0116] Service quality sustainability analysis data,

[0117] Session management congestion experience analysis data,

[0118] Analysis data related to redundant transmission experience

[0119] End-to-end data volume and transmission time analysis data, or

[0120] Protocol data unit session service analysis data.

[0121] Example 6. The method according to Example 1, wherein the first interface is an SBA application programming interface.

[0122] Example 7. The method according to Example 1 further includes:

[0123] Establish the first interface with the network open function of the SBA.

[0124] Example 8. A network device, comprising:

[0125] One or more memories; and

[0126] One or more processors in:

[0127] Establish the first interface with the Network Data Analysis Function (NWDAF) based on Service Architecture (SBA).

[0128] The first interface is the SBA application programming interface;

[0129] Establish a second interface with 3GPP access equipment and non-3GPP access equipment under the 3rd Generation Partnership Project;

[0130] Provide the definition of the analysis data generated by the NWDAF to the NWDAF and via the first interface;

[0131] The raw data of the SBA's operational status is provided to the NWDAF and via the first interface, so that the NWDAF can calculate the analysis data based on the definition and the raw data of the operational status;

[0132] Receive the analysis data from the NWDAF and via the first interface; and

[0133] One or more actions are performed based on the analyzed data.

[0134] Example 9. The network device according to Example 8, wherein the second interface is a socket interface based on User Datagram Protocol / Internet Protocol.

[0135] Example 10. The network device according to Example 8, wherein the 3GPP access device and the non-3GPP access device include one or more of the following:

[0136] Radio access network,

[0137] Wired access gateway function,

[0138] Non-3GPP interoperability function.

[0139] Granting access to non-3GPP gateway functions, or

[0140] Enables wireless LAN interconnection functionality.

[0141] Example 11. The network device according to Example 8, wherein the analysis data includes one or more of the following:

[0142] Network analysis data,

[0143] Network function load analysis data,

[0144] Network performance analysis data,

[0145] Analysis data related to user equipment

[0146] Congestion analysis data,

[0147] Service quality sustainability analysis data,

[0148] Session management congestion experience analysis data,

[0149] Analysis data related to redundant transmission experience

[0150] End-to-end data volume and transmission time analysis data, or

[0151] Protocol data unit session service analysis data.

[0152] Example 12. The network device according to Example 8, wherein the one or more processors are configured to perform the one or more actions, the one or more actions being performed for one or more of the following:

[0153] Computing service experience;

[0154] Adjust the load on network functions;

[0155] Correcting network performance issues

[0156] Correcting user equipment performance issues,

[0157] Handling network congestion,

[0158] Solving the problem of service quality sustainability, or

[0159] Handling session management congestion.

[0160] Example 13. The network device according to Example 8, wherein the network device is an access network data function.

[0161] Example 14. The network device according to Example 8, wherein the definition of the analytical data is based on a use case associated with the SBA.

[0162] Example 15. A non-transitory computer-readable medium storing an instruction set, the instruction set comprising:

[0163] One or more instructions, when executed by one or more processors of the network device, cause the network device to:

[0164] Establish the first interface with the Network Data Analysis Function (NWDAF) based on Service Architecture (SBA);

[0165] Establish a second interface with 3GPP access equipment and non-3GPP access equipment under the 3GPP Partnership Program.

[0166] The second interface is a socket interface based on User Datagram Protocol / Internet Protocol.

[0167] Provide the definition of the analysis data generated by the NWDAF to the NWDAF and via the first interface;

[0168] The raw data of the SBA's operational status is provided to the NWDAF and via the first interface, so that the NWDAF can calculate the analysis data based on the definition and the raw data of the operational status;

[0169] Receive the analysis data from the NWDAF and via the first interface; and

[0170] One or more actions are performed based on the analyzed data.

[0171] Example 16. The non-transitory computer-readable medium according to Example 15, wherein one or more instructions further cause the network device to:

[0172] Telemetry data is received from the 3GPP access device and the non-3GPP access device via the second interface;

[0173] The telemetry data is provided to the NWDAF and via the first interface, so that the NWDAF calculates additional analytical data based on the telemetry data;

[0174] Receive the additional analysis data from the NWDAF and via the first interface; and

[0175] One or more additional actions are performed based on the additional analytical data.

[0176] Example 17. The non-transitory computer-readable medium according to Example 16, wherein the telemetry data includes protocol buffer structured messages in a general key / value format.

[0177] Example 18. The non-transitory computer-readable medium according to Example 16, wherein the one or more instructions that cause the network device to receive the telemetry data from the 3GPP access device and the non-3GPP access device cause the network device to perform one of the following:

[0178] The telemetry data is received in batches from the 3GPP access device and the non-3GPP access device.

[0179] The telemetry data is received in blocks from the 3GPP access device and the non-3GPP access device; or

[0180] A portion of the telemetry data is periodically received from one or more of the 3GPP access devices and the non-3GPP access devices.

[0181] Example 19. The non-transitory computer-readable medium according to Example 15, wherein one or more instructions further cause the network device to:

[0182] Establish the first interface with the network open function of the SBA.

[0183] Example 20. A non-transitory computer-readable medium according to Example 15, wherein the one or more instructions that cause the network device to perform the one or more actions cause the network device to perform one or more of the following:

[0184] Computing service experience;

[0185] Adjust the load on network functions;

[0186] Correcting network performance issues

[0187] Correcting user equipment performance issues,

[0188] Handling network congestion,

[0189] Solving the problem of service quality sustainability, or

[0190] Handling session management congestion.

Claims

1. A method comprising: establishing, by a network device, a first interface with a service based architecture, SBA, network data analytics function, NWDAF; establishing, by the network device, a second interface with third generation partnership project, 3GPP, access devices and non-3GPP access devices; providing, by the network device to the NWDAF and via the first interface, a definition of analytics data generated by the NWDAF; providing, by the network device to the NWDAF and via the first interface, raw data of operational states of the SBA to cause the NWDAF to compute the analytics data based on the definition and the raw data of operational states; receiving, by the network device from the NWDAF and via the first interface, the analytics data; and performing, by the network device, one or more actions based on the analytics data.

2. The method of claim 1, further comprising: receiving, via the second interface, telemetry data from the 3GPP access devices and the non-3GPP access devices; providing, to the NWDAF and via the first interface, the telemetry data to cause the NWDAF to compute additional analytics data based on the telemetry data; receiving, from the NWDAF and via the first interface, the additional analytics data; and performing one or more additional actions based on the additional analytics data.

3. The method of claim 2, wherein the telemetry data comprises protocol buffer structured messages in a generic key / value format.

4. The method of claim 2, wherein receiving the telemetry data from the 3GPP access devices and the non-3GPP access devices comprises one of: batch receiving the telemetry data from the 3GPP access devices and the non-3GPP access devices; chunked receiving the telemetry data from the 3GPP access devices and the non-3GPP access devices; or periodically receiving portions of the telemetry data from one or more of the 3GPP access devices and the non-3GPP access devices.

5. The method of claim 2, wherein the additional analytics data comprises one or more of: network analytics data, network function load analytics data, network performance analytics data, user equipment related analytics data, congestion analytics data, quality of service sustainability analytics data, session management congestion experience analytics data, redundant transmission experience related analytics data, end-to-end data volume transmission time analytics data, or protocol data unit session traffic analytics data.

6. The method of claim 1, wherein the first interface is an SBA application programming interface.

7. The method of claim 1, further comprising: establishing the first interface with a network exposure function of the SBA.

8. A network device comprising: one or more memories; and one or more processors to: establish a first interface with a service based architecture, SBA, network data analytics function, NWDAF, wherein the first interface is an SBA application programming interface; ​ ​ ​ ​ establishing a second interface with third generation partnership project, 3GPP, access equipment and non-3GPP access equipment; providing, to the NWDAF and via the first interface, a definition of analytics data generated by the NWDAF; providing, to the NWDAF and via the first interface, raw data of operational states of the SBA to cause the NWDAF to compute the analytics data based on the definition and the raw data of operational states; receiving, from the NWDAF and via the first interface, the analytics data; and performing one or more actions based on the analytics data.

9. The network device of claim 8, wherein the second interface is a user datagram protocol / internet protocol-based socket interface.

10. The network device of claim 8, wherein the 3GPP access equipment and the non-3GPP access equipment comprise one or more of: a radio access network, a wired access gateway function, a non-3GPP interworking function, a trusted non-3GPP gateway function, or a trusted wireless local area network interworking function.

11. The network device of claim 8, wherein the analytics data comprises one or more of: network analytics data, network function load analytics data, network performance analytics data, user equipment related analytics data, congestion analytics data, quality of service sustainability analytics data, session management congestion experience analytics data, redundant transmission experience related analytics data, end-to-end data volume transmission time analytics data, or protocol data unit session traffic analytics data.

12. The network device of claim 8, wherein the one or more processors are to perform the one or more actions for one or more of: computing service experience; adjusting load on a network function; correcting network performance issues, correcting user equipment performance issues, handling network congestion, addressing quality of service sustainability issues, or handling session management congestion.

13. The network device of claim 8, wherein the network device is an access network data function.

14. The network device of claim 8, wherein the definition of analytics data is based on a use case associated with the SBA.

15. A non-transitory computer-readable medium storing a set of instructions, the set of instructions comprising: one or more instructions that, when executed by one or more processors of a network device, cause the network device to: establish a first interface with a service based architecture, SBA, network data analytics function, NWDAF; establish a second interface with third generation partnership project, 3GPP, access equipment and non-3GPP access equipment, wherein the second interface is a user datagram protocol / internet protocol-based socket interface; provide, to the NWDAF and via the first interface, a definition of analytics data generated by the NWDAF; provide, to the NWDAF and via the first interface, raw data of operational states of the SBA to cause the NWDAF to compute the analytics data based on the definition and the raw data of operational states; ​ receive, from the NWDAF and via the first interface, the analytics data; and perform one or more actions based on the analytics data.

16. The non-transitory computer-readable medium of claim 15, wherein the one or more instructions further cause the network device to: receive, from the 3GPP access device and the non-3GPP access device via the second interface, telemetry data; provide, to the NWDAF and via the first interface, the telemetry data to cause the NWDAF to compute additional analytics data based on the telemetry data; receive, from the NWDAF and via the first interface, the additional analytics data; and perform one or more additional actions based on the additional analytics data.

17. The non-transitory computer-readable medium of claim 16, wherein the telemetry data comprises protocol buffer structured messages in a generic key / value format.

18. The non-transitory computer-readable medium of claim 16, wherein the one or more instructions that cause the network device to receive the telemetry data from the 3GPP access device and the non-3GPP access device cause the network device to perform one of: receive the telemetry data in bulk from the 3GPP access device and the non-3GPP access device; receive the telemetry data in chunks from the 3GPP access device and the non-3GPP access device; or receive portions of the telemetry data periodically from one or more of the 3GPP access device and the non-3GPP access device.

19. The non-transitory computer-readable medium of claim 15, wherein the one or more instructions further cause the network device to: establish the first interface with a network exposure function of the SBA.

20. The non-transitory computer-readable medium of claim 15, wherein the one or more instructions that cause the network device to perform the one or more actions cause the network device to perform one or more of: compute service experience; adjust load on network functions; correct network performance problems, correct user equipment performance problems, handle network congestion, address quality of service sustainability problems, or handle session management congestion.

Images