Predictive analytics in network entities within a wireless communication network
By integrating AI/ML models within network functions for local predictive analytics, the wireless communication network can efficiently process performance measurements and KPIs, addressing the inefficiencies of centralized data processing and enhancing resource utilization.
Patent Information
- Application Number
- PCT/EP2024/057475
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2024-02-15
- Filing Date
- 2024-03-20
- Publication Date
- 2024-12-05
AI Technical Summary
Current wireless communication networks lack the ability to perform AI/ML-based predictions locally at network equipment, relying on centralized analytics nodes for complex data processing, which leads to inefficient use of resources and delayed analytics results.
Implementing AI/ML models and predictive analytics capabilities within network functions to enable local data-driven predictions, allowing for targeted and efficient processing of performance measurements and KPIs, and introducing new Event IDs and parameters for requesting and reporting predictive data.
This approach enables faster, more efficient, and cost-effective predictive analytics by processing data locally, reducing unnecessary data transmission and improving resource utilization within network functions.
Smart Images

Figure EP2024057475_05122024_PF_FP_ABST
Abstract
Description
PREDICTIVE ANALYTICS IN NETWORK ENTITIES WITHIN A WIRELESS COMMUNICATION NETWORKTECHNICAL FIELD
[0001] The subject matter disclosed herein relates generally to the field of implementing predictive analytics in network entities within a wireless communication network. In particular, this document defines a first network function, processors for wireless communication, a method performed by a first network function, a second network function and a method performed by a second network function.BACKGROUND
[0002] A wireless communications system may include one or multiple network communication devices, such as base stations, which may support wireless communications for one or multiple user communication devices, which may be otherwise known as user equipment (UE), or other suitable terminology. The wireless communications system may support wireless communications with one or multiple user communication devices by utilizing resources of the wireless communication system (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers, or the like). Additionally, the wireless communications system may support wireless communications across various radio access technologies including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, among other suitable radio access technologies beyond 5G (e.g., sixth generation (6G)).SUMMARY
[0003] An article “a” before an element is unrestricted and understood to refer to “at least one” of those elements or “one or more” of those elements. The terms “a,” “at least one,” “one or more,” and “at least one of one or more” may be interchangeable. As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of’ or “one or more of’ or “one or both of’) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C orAB or AC or BC or ABC (i.e., A and B and C). Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on. Further, as used herein, including in the claims, a “set” may include one or more elements.
[0004] There is provided herein a first network function for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the first network function to: receive, from a second network function, a request for a predictive analytic service; determine an analytics result for addressing the request for the predictive analytic service and based on locally obtained data; and transmit the analytics result to the second network function.
[0005] There is further provided a processor for wireless communication, comprising: at least one controller coupled with at least one memory and configured to cause the processor to: receive, from a second network function, a request for a predictive analytic service; determine an analytics result for addressing the request for the predictive analytic service and based on locally obtained data; and transmit the analytics result to the second network function.
[0006] There is further provided a method performed by a first network function, the method comprising: receiving, from a second network function, a request for a predictive analytic service; determining an analytics result for addressing the request for the predictive analytic service and based on locally obtained data; and transmitting the analytics result to the second network function.
[0007] There is further provided a second network function for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the second network function to: transmit, to a first network function, a request for a predictive analytic service; and receive an analytics result from the first network function.
[0008] There is further provided a processor for wireless communication, comprising: at least one controller coupled with at least one memory and configured to cause the processor to: transmit, to a first network function, a request for a predictive analytic service; and receive an analytics result from the first network function.
[0009] There is further provided a method performed by a second network function, the method comprising: transmitting, to a first network function, a request for a predictive analytic service; and receiving an analytics result from the first network function.BRIEF DESCRIPTION OF THE DRAWINGS
[0010] Figure 1 illustrates an example of a wireless communications system in accordance with aspects of the present disclosure.
[0011] Figure 2 illustrates an overview of Network Data Analytics Function (NWDAF) flavours, including potential input data sources and output consumers.
[0012] Figure 3 illustrates an overview of a process 300 for requesting and receiving predictive events.
[0013] Figure 4 illustrates an example of a user equipment (UE) 400 in accordance with aspects of the present disclosure.
[0014] Figure 5 illustrates an example of a processor 500 in accordance with aspects of the present disclosure.
[0015] Figure 6 illustrates an example of a network equipment (NE) 600 in accordance with aspects of the present disclosure.
[0016] Figure 7 illustrates a flowchart of a method 700 performed by a NE in accordance with aspects of the present disclosure.
[0017] Figure 8 illustrates a flowchart of a method 800 performed by a NE in accordance with aspects of the present disclosure.DETAILED DESCRIPTION
[0018] Network analytics predictions are complex and typically involve several input data collected at an analytics network node. The network node then produces a report that contains several predictive results.
[0019] Such an arrangement tends to provide a mechanism to enable predictive data analytics on network nodes for specific performance measurements, counters or Key Performance Indicators (KPIs) based on locally collected data. Predictions obtained by such network functions locally can be simple and targeted. Such simple and targeted predictions or analytics results avoid unnecessary production and transmission of results that they will not be used. This can result in more efficient use of network resources, including both communication bandwidth and processing resources within network functions. Further, such arrangements tend to deliver predictions or analytics results faster, since the data collection is locally obtained and processing is focused and so tends to be shorter. Focused data collection and processing may result in reduced cost of operation of the predictive analytic service.
[0020] Aspects of the present disclosure are described in the context of a wireless communications system.
[0021] Figure 1 illustrates an example of a wireless communications system 100 in accordance with aspects of the present disclosure. The wireless communications system 100 may include one or more NE 102, one or more UE 104, and a core network (CN) 106. The wireless communications system 100 may support various radio access technologies. In some implementations, the wireless communications system 100 may be a 4G network, such as an LTE network or an LTE-Advanced (LTE-A) network. In some other implementations, the wireless communications system 100 may be a NR network, such as a 5G network, a 5G-Advanced (5G-A) network, or a 5G ultrawideband (5G-UWB) network. In other implementations, the wireless communications system 100 may be a combination of a 4G network and a 5G network, or other suitable radio access technology including Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20. The wireless communications system 100 may support radio access technologies beyond 5G, for example, 6G. Additionally, the wirelesscommunications system 100 may support technologies, such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA), etc.
[0022] The one or more NE 102 may be dispersed throughout a geographic region to form the wireless communications system 100. One or more of the NE 102 described herein may be or include or may be referred to as a network node, a base station, a network element, a network function, a network entity, a radio access network (RAN), a NodeB, an eNodeB (eNB), a next-generation NodeB (gNB), or other suitable terminology. An NE 102 and a UE 104 may communicate via a communication link, which may be a wireless or wired connection. For example, an NE 102 and a UE 104 may perform wireless communication (e.g., receive signalling, transmit signalling) over a Uu interface.
[0023] An NE 102 may provide a geographic coverage area for which the NE 102 may support services for one or more UEs 104 within the geographic coverage area. For example, an NE 102 and a UE 104 may support wireless communication of signals related to services (e.g., voice, video, packet data, messaging, broadcast, etc.) according to one or multiple radio access technologies. In some implementations, an NE 102 may be moveable, for example, a satellite associated with a non-terrestrial network (NTN). In some implementations, different geographic coverage areas associated with the same or different radio access technologies may overlap, but the different geographic coverage areas may be associated with different NE 102.
[0024] The one or more UE 104 may be dispersed throughout a geographic region of the wireless communications system 100. A UE 104 may include or may be referred to as a remote unit, a mobile device, a wireless device, a remote device, a subscriber device, a transmitter device, a receiver device, or some other suitable terminology. In some implementations, the UE 104 may be referred to as a unit, a station, a terminal, or a client, among other examples. Additionally, or alternatively, the UE 104 may be referred to as an Internet-of-Things (loT) device, an Internet-of-Everything (loE) device, or machine-type communication (MTC) device, among other examples.
[0025] A UE 104 may be able to support wireless communication directly with other UEs 104 over a communication link. For example, a UE 104 may support wirelesscommunication directly with another UE 104 over a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular-V2X deployments, the communication link may be referred to as a sidelink. For example, a UE 104 may support wireless communication directly with another UE 104 over a PC5 interface.
[0026] An NE 102 may support communications with the CN 106, or with another NE 102, or both. For example, an NE 102 may interface with other NE 102 or the CN 106 through one or more backhaul links (e.g., SI, N2, N2, or network interface). In some implementations, the NE 102 may communicate with each other directly. In some other implementations, the NE 102 may communicate with each other or indirectly (e.g., via the CN 106. In some implementations, one or more NE 102 may include subcomponents, such as an access network entity, which may be an example of an access node controller (ANC). An ANC may communicate with the one or more UEs 104 through one or more other access network transmission entities, which may be referred to as a radio heads, smart radio heads, or transmission-reception points (TRPs).
[0027] The CN 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The CN 106 may be an evolved packet core (EPC), or a 5G core (5GC), which may include a control plane entity that manages access and mobility (e.g., a mobility management entity (MME), an access and mobility management functions (AMF)) and a user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW), a Packet Data Network (PDN) gateway (P-GW), or a user plane function (UPF)). In some implementations, the control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signal bearers, etc.) for the one or more UEs 104 served by the one or more NE 102 associated with the CN 106.
[0028] The CN 106 may communicate with a packet data network over one or more backhaul links (e.g., via an SI, N2, N2, or another network interface). The packet data network may include an application server. In some implementations, one or more UEs 104 may communicate with the application server. A UE 104 may establish a session (e.g., a protocol data unit (PDU) session, or the like) with the CN 106 via an NE 102. The CN 106may route traffic (e.g., control information, data, and the like) between the UE 104 and the application server using the established session (e.g., the established PDU session). The PDU session may be an example of a logical connection between the UE 104 and the CN 106 (e.g., one or more network functions of the CN 106).
[0029] In the wireless communications system 100, the NEs 102 and the UEs 104 may use resources of the wireless communications system 100 (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communications). In some implementations, the NEs 102 and the UEs 104 may support different resource structures. For example, the NEs 102 and the UEs 104 may support different frame structures. In some implementations, such as in 4G, the NEs 102 and the UEs 104 may support a single frame structure. In some other implementations, such as in 5G and among other suitable radio access technologies, the NEs 102 and the UEs 104 may support various frame structures (i.e., multiple frame structures). The NEs 102 and the UEs 104 may support various frame structures based on one or more numerologies.
[0030] One or more numerologies may be supported in the wireless communications system 100, and a numerology may include a subcarrier spacing and a cyclic prefix. A first numerology (e.g., / t=0) may be associated with a first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. In some implementations, the first numerology (e.g., / t=0) associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one slot per subframe. A second numerology (e.g., / / =1) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. A third numerology (e.g., g=2) may be associated with a third subcarrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth numerology (e.g., / t=3) may be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a normal cyclic prefix. A fifth numerology (e.g., / t=4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a normal cyclic prefix.
[0031] A time interval of a resource (e.g., a communication resource) may be organized according to frames (also referred to as radio frames). Each frame may have a duration, for example, a 10 millisecond (ms) duration. In some implementations, each frame may include multiple subframes. For example, each frame may include 10 subframes, and eachsubframe may have a duration, for example, a l ms duration. In some implementations, each frame may have the same duration. In some implementations, each subframe of a frame may have the same duration.
[0032] Additionally or alternatively, a time interval of a resource (e.g., a communication resource) may be organized according to slots. For example, a subframe may include a number (e.g., quantity) of slots. The number of slots in each subframe may also depend on the one or more numerologies supported in the wireless communications system 100. For instance, the first, second, third, fourth, and fifth numerologies (i.e., / t=0, / t=l, =2, jtz=3, =4) associated with respective subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz may utilize a single slot per subframe, two slots per subframe, four slots per subframe, eight slots per subframe, and 16 slots per subframe, respectively. Each slot may include a number (e.g., quantity) of symbols (e.g., OFDM symbols). In some implementations, the number (e.g., quantity) of slots for a subframe may depend on a numerology. For a normal cyclic prefix, a slot may include 14 symbols. For an extended cyclic prefix (e.g., applicable for 60 kHz subcarrier spacing), a slot may include 12 symbols. The relationship between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame for a normal cyclic prefix and an extended cyclic prefix may depend on a numerology. It should be understood that reference to a first numerology (e.g., / t=0) associated with a first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and slots.
[0033] In the wireless communications system 100, an electromagnetic (EM) spectrum may be split, based on frequency or wavelength, into various classes, frequency bands, frequency channels, etc. By way of example, the wireless communications system 100 may support one or multiple operating frequency bands, such as frequency range designations FR1 (410 MHz - 7.125 GHz), FR2 (24.25 GHz - 52.6 GHz), FR3 (7.125 GHz - 24.25 GHz), FR4 (52.6 GHz - 114.25 GHz), FR4a or FR4-1 (52.6 GHz - 71 GHz), and FR5 (114.25 GHz - 300 GHz). In some implementations, the NEs 102 and the UEs 104 may perform wireless communications over one or more of the operating frequency bands. In some implementations, FR1 may be used by the NEs 102 and the UEs 104, among other equipment or devices for cellular communications traffic (e.g., control information, data).In some implementations, FR2 may be used by the NEs 102 and the UEs 104, among other equipment or devices for short-range, high data rate capabilities.
[0034] FR1 may be associated with one or multiple numerologies (e.g., at least three numerologies). For example, FR1 may be associated with a first numerology (e.g., / t=0), which includes 15 kHz subcarrier spacing; a second numerology (e.g., / / =1), which includes 30 kHz subcarrier spacing; and a third numerology (e.g., g=2), which includes 60 kHz subcarrier spacing. FR2 may be associated with one or multiple numerologies (e.g., at least 2 numerologies). For example, FR2 may be associated with a third numerology (e.g., / z=2), which includes 60 kHz subcarrier spacing; and a fourth numerology (e.g., / t=3), which includes 120 kHz subcarrier spacing.
[0035] Network analytics may employ Artificial Intelligence and / or Machine Learning (AI / ML). Such network analytics may be deployed in a Fifth Generation (5G) core network via the introduction of NWDAF to consider the support of various analytics types as elaborated in 3GPP TS 23.288 vl 8.4.0 (Dec 2023) which is titled “Architecture enhancements for 5G System (5GS) to support network data analytics services”. Each NWDAF may support one or more Analytics identities (IDs) and may have the role of inference (and so called NWDAF Analytics Logical Function (AnLF)), or the role of training (and so called NWDAF Model Training Logical Function (MTLF)) or both. An AnLF that support a specific Analytics ID inference subscribes to a corresponding MTLF that is responsible for training.
[0036] Figure 2 illustrates an overview of NWDAF flavours, including the potential input data sources and output consumers. The various NWDAF flavours and their respective input data and output result consumers are illustrated. Output result consumers may include 5G core Network Functions (NFs), Application Functions (AFs), 5G core repositories, e.g., Network Repository Function (NRF), Unified Data Management (UDM), etc., and the Operations, Administration and Maintenance (0AM) (Management Service (MnS) Consumer or Management Function (MF)).
[0037] As illustrated in Figure 2, a first Data Collection Coordination Functionality (DCCF) 212 receives inputs from 5G Core Network Functions 202, Application Functions 204, untrusted application functions 204 via a network exposure function 206, 5G corerepositories 208, and 0AM data 210. The 5G Core Repositories 208 may comprise a NRF, a Binding Support Function (BSF), an Analytics Data Repository Function (ADRF), a UDM, and / or a Unified Data Repository (UDR). The 0AM 210 may comprise a MnS Producer or an MF that provides Performance Measurements, Key Performance indicators, Configuration Management, and Alarm information. Optionally, the first DCCF 212 may provide data to an NWDAF AnLF / MTLF 214, an NWDAF AnLF 216, and an NWDAF MTLF Server FL 218.
[0038] The NWDAF containing AnLF / MTLF 214, the NWDAF containing AnLF 216, and the NWDAF containing MTLF Server FL 218 may pass on data to the second DCCF 222. The second DCCF 222 may further provide data to the 5G Core Network Functions 224, Application Functions 228, untrusted application functions 228 via a network exposure function 226, 5G core repositories 230, and 0AM data 232. The 5G Core Repositories 230 may comprise an ADRF, a UDM, and / or a Unified Data Repository (UDR). The 0AM 232 may comprise a Management Services (MnS) Consumer or a Management Function (MF).
[0039] In operation, MTLF 218 and AnLF 216 may exchange AI / ML models. Such exchange may be performed by means of parameter exchange, serialization or containerization. Optionally, DCCF and MFAF may be involved in the AI / ML model exchange to distribute and collect repeated data towards or from various data sources.
[0040] 3GPP TS 23.288 vl 8.4.0 presents considerations of several analytics services identified by an Analytics ID. These analytics services rely on certain input data that needs to be collected and processed by an ML model residing in an NWDAF AnLF to derive the analytics output. Typically, Analytics IDs rely on at least two or more input data that is collected from different data sources. The NWDAF correlates different data inputs performing complex analytics that can be used as an insight by a consumer to assist in making decisions. The Analytics ID is related to user behaviour, communication patterns, mobility, service experience, NF load, slice load, etc.
[0041] Input data may be collected per Analytics ID or Event ID (associated with trigger events, i.e., triggers or thresholds, etc. for reporting information; triggers may be provided as a volume, time, or event to cater for the different charging / usage monitoringmodels). In the context of analytics, clause 5A.4 of 3GPP TS 23.288 vl8.4.0 provides processing instructions. The processing instructions may specify the parameter names, parameter values and the attributes to be determined and reported to the consumer. Data can be processed for inclusion in each notification sent to consumers considering processing instructions, which may include statistics and may also specify data aggregation. Data aggregation may comprise an aggregation level such as per-UEs, or per Area of Interest. Data aggregation may also comprise temporal aggregation such as per minute, or per hour.
[0042] A notion of statistics associated per Event ID, e.g., UserDataUsageTrends is specified in clause 5.2.26.2.1 of 3GPP TS 23.502 vl 8.4.0 (Dec 2023) and titled “Procedures for the 5G System (5GS)”. The data is prepared and processed at the source providing several different statistics including, e.g., averaging, aggregating, variance, maximum, minimum, etc. These types of statistics are produced faster than the ones produced by an analytics function (e.g., NWDAF), since the steps of collecting data from multiple sources and formatting it to feed the AI / ML model are no longer needed. So, in essence, producing statistics at the NF is in near real-time, whereas the ones produced in the NWDAF are non-real time, but of course the scope of analytics is different. In NF analytics there is a scope limitation per single measurement or KPI.
[0043] During connection, registration and mobility management procedures, the AMF may store and update the UE access behaviour trends as shown in Table 1 and the UE location trends in Table 2, as specified in clause 14.15.4 3GPP TS 23.502 vl8.4.0. Each metric is updated incrementally, e.g., using an exponential moving average.Table 1: UE access behaviour trends exposed by AMF.Table 2: UE location trends
[0044] During session management procedures, the SMF may store and update the UE access behaviour trends as shown in Table 3 and the UE communication trends illustrated in Table 4 as specified in clause 14.15.4 TS 23.502 vl8.4.0. Each metric is updated incrementally, e.g., by using exponential moving average.Table 3: UE session behaviour trends exposed by SMF.Table 4: UE communication trends.
[0045] Currently, there are no AI / ML based predictions related to a single data measurement or KPI, which can be determined locally at a specific network equipment. Such predictions provided by NFs can be based on locally obtained data or from data related to closely interworking neighbouring NFs, e.g., UPF and SMF. By way of example, a UPF handling data plane traffic may not always have the capacity to process and determine analytics. The arrangements presented herein tend to facilitate AI / ML predictions that can be obtained by NFs at least as quickly as the counterpart statistics.
[0046] The apparatus and methods described herein introduce prediction analytics at the level of network equipment, e.g., a NF. This tends to facilitate simple use cases that need a single target prediction based on existing measurements or KPIs. A representative use case can be the estimation of energy consumption of a UPF. Such a prediction relies on the prediction of data volume, which can be obtained from local data if the UPF supports prediction capabilities for this specific measurement.
[0047] To achieve prediction analytics at the level of network equipment, there is described herein the introduction of AI / ML models or indeed, other simpler models, locally in network equipment. The models implemented locally in network equipment, may be implemented in a network function. The models implemented locally may be responsible for providing predictions based on local data. These models may comprise any of exponential smoothing, an autoregressive integrated moving average (ARIMA) or other AI / ML models. By way of example, exponential smoothing may be performed using a simple model, Holt’s liner trend, Brown’s linear trend, a damped trend, or Winters’additive. The introduction of AI / ML or other predictive models in network equipment requires a set of enhancements related to the following areas.• Discovery process to enable other NF s, AFs, and the OAM identify where specific network equipment predictive analytics can be found. To enable this an NF may indicate its capabilities (e.g., predictive performance measurements) and supporting event services to the network repository, i.e., to the NRF. These new capabilities and events may indicate the supported predictive data.• Event request and reporting process to enable other NFs and the OAM to request and retrieve predictive data (i.e., predictive performance measurements and / or predictive events). This can be achieved by introducing extensions on the exposure capabilities, new predictive measurements or Event IDs introducing the means for requesting predictive data.• Exposure capability towards untrusted AFs, i.e., enabling 3rd parties, to request and retrieval of predictive NF data via the Network Exposure Function (NEF).
[0048] The notion of predictive data includes predictive Performance Measurements (PMs), predictive counters related to specific activities, i.e., predictive state transition, e.g., connect to idle, and predictive KPIs.
[0049] To address new predictive data there is a need to define:• new identifiers that would be related to predictive events and / or predictive PMs / counters / KPIs offered by NFs, considering existing and predictive PMs, predictive counters and predictive KPIs, e.g., UserDataUsagePrediction; and• new entries on the existing List of Event Parameter Name(s) and / or introducing new PMs, new counters and / or new KPIs.
[0050] The new entries on the existing List of Event Parameter Name(s) and / or new PMs, new counters and / or new KPIs introduced may including any of the following parameters.• the prediction identifier indicating that the request event is related to a prediction,• the desired future target interval, i.e., the time interval related to the requested prediction, e.g., for the next 30 secs, (this time interval can be a relatively small, fixed time interval regardless of the request or it can be customized per request),• the preferred accuracy related to the requested prediction, e.g., low, medium, high, indicating optionally the sampling rate,• granularity of the prediction, e.g., UE or UE group, PDU session, QoS flow, slice, etc.• the data sources, data range and other data statistics• a reporting threshold, e.g., report a prediction only if it is greater, lower, in between, or equal than a certain limit.• the usage context indicates the context of use of the analytics to select the most relevant ML model in case there is an option.
[0051] Predictive events or predictive PMs / counters / KPIs may use the parameters specified for other conventional events, e.g., filter information, reporting information, target of event reporting, etc., as per clause 4.15.1 TS 23.502 vl8.4.0. Predictive events can be offered per NF instance or per NF Set ID in where a certain NF member(s) can provide the predictive measurements or predictive events for the entire set.
[0052] New Event IDs and / or the new PMs / counters / KPIs and the new parameters related to prediction capabilities, can be registered in association with an NF used to the NRF allowing other NFs to discover and select the desired NF predictive capabilities. In addition, new Event IDs and / or the new PMs / counters / KPIs and / or parameters related to prediction capabilities can be used for enabling an event request by another NF consumer within the premisses of the mobile network operator or an untrusted AF via NEF.
[0053] The predictive event or predictive PMs / counter / KPI report may include at least one of the following pieces of information:• the event, PM / counter / KPI reporting data, e.g., predictive values,• a time stamp to indicate when the predictive event, PM / counter / KPI was computed,• the validity period that indicates until when the predictive event, PM / counter / KPI shall be used,• target object list if the prediction involves multiple different objects,• the confidence level related to a predictive event, PM / counter / KPI,• the correlation ID associated with an event, PM / counter / KPI subscription.
[0054] Figure 3 illustrates an overview of the process 300 for requesting and receiving predictive events. Process 300 is performed by an NF consumer 310 and an NF producer 320. Process 300 is an example wherein the NF producer 320 has already registered its predictive events or predictive measurements and capabilities in the NRF.
[0055] At 371, the NF consumer 310 discovers the NF producer 320 that can offer the desired predictive events or a predictive PMs / counters / KPIs by issuing a request to the NRF. Such discovery request may include the predictive event ID, the Performance Management (PM), a counter, and / or KPI identifier as well as the desired capabilities with respect to an area of interest such as slice, Data Network Name (DNN), etc.
[0056] If the NF consumer 310 is an untrusted AF, then the discover request (including the additional identifier and parameters) is handled by the NEF, which is responsible for authenticating the request and identifying as well as selecting the appropriate NF producer 320 by enquiring the NRF. Hence, the NEF exposure services need to be extended with the respective new identifier and parameters as well as with the new reporting capabilities.
[0057] At 372, once the NF consumer 310 receives the details of the NF producer 320, it issues a request (i.e., a single on-demand request) or a subscription for a predictive event or a predictive measurement by including the Event ID or PM / counter / KPI identifier and the related predictive parameters.
[0058] If the NF consumer 310 is an untrusted AF, then the request or subscription for predictive events or predictive PM / counter / KPI is handled by the NEF.
[0059] At 373, the NF producer 320 determines the requested predictive output results and provides a report including the details related to predictive information to the NFconsumer 310. The report is provided when the conditions indicated, e.g., time schedule or thresholds, etc., are met.
[0060] At 374, in case of a subscription, the NF producer 320 can regularly determine the requested predictive output results and provide a report including the details related to predictive information to the NF consumer 310 when the conditions indicated, e.g., time schedule or thresholds, are met.
[0061] It shall be noted that the request and response of the predictive event and / or predictive PM / counter / KPI can also be towards another node not necessarily the one that produces the local data, but a neighbouring one that has direct connectivity or correspondence (i.e., is inter-related) with the one that produces the local data, e.g., towards the SMF that has direct UPF correspondence, instead of the UPF.
[0062] Examples of the enhanced process may include:• Namf_EventExposure service as per clause 5.2.2.3 TS 23.502 vl8.4.0 introducing predictions related to, e.g., UEs moving out of an area of interest, UEs served by an AMF, access type changes, connectivity or registration state changes, reachability, mobility management transactions, etc.• Nnef_EventExposure service as per clause 5.2.6 TS 23.502 vl8.4.0 exposing predictive data to untrusted AFs related to the network nodes, besides the conventional NWDAF, of a mobile network operator.• Nsmf_EventExposure service as per clause 5.2.8 TS 23.502 vl8.4.0 introducing predictions related to, e.g., QoS, path changes, access changes, session and communication related issues, user data usage, etc.• Nsmf_EventExposure service as per clause 5.2.26 TS 23.502 vl8.4.0 introducing predictions related to, e.g., QoS monitoring, data volume, throughput, etc.
[0063] Depending on where the AI / ML model will be applied a different type of AI / ML may be employed. This choice may be made dependent on the available memory to store local data at the specific location.
[0064] For specific embodiments, predictive Event IDs can be used for enhancing UPF events. Such events may include any combination of the following.• Predictive QoS: This event provides predictive QoS Flow performance information. For example, an NF or AF can request predictive QoS for a specific QoS monitoring parameters related to service data flow(s).• User Data Usage Predictions: This event provides predictions related to user data usage of the User PDU Session. For example, this predictive event can be useful for the case of predicting energy consumption, which is relies on the data volume.• Throughput Predictive Measurement: This event provides predictions related to throughput with respect to a PDU Session or per application.
[0065] In the case of Predictive QoS, an NF or AF can request predictive QoS for at least one of the following QoS monitoring parameters.• Predictive UL packet delay, predictive DL packet delay, predictive round trip packet delay for a service data flow.• Predictive Congestion.• Predictive Data Rate.• Predictive Packet Delay Variation.• Predictive Round trip packet delay considering UL on a service data flow and DL of another service data flow.
[0066] When the UPF supports data exposure via the service-based interface, it registers its NF profile to the NRF including the UPF Event Exposure services and the related Event ID(s). An NF consumer may subscribe to the UPF Event Exposure service directly only for data collected for “any UE”, if the subscription is not including area of interest, traffic filtering, application ID, etc. For specific UE IDs predictive data can be collected from the SMF.
[0067] The SMF may store and update the predicted UE access behaviour as shown in Table 5 below and the predicted UE communication as illustrated in Table 6 (which isdifferent from the UE communication Analytics ID specified in clause 6.7.3 of 3GPP TS 23.288 vl 8.4.0), further below.Table 5: Predicted UE session behaviour exposed by SME.Table 6: Predicted UE communication.
[0068] It should be further noted that in an alternative arrangement, predictive Event IDs can be used for enhancing AMF events during connection, registration and mobility management procedures for specified UE IDs for predicting UE access behaviour. UE access behaviour prediction exposed by AMF is shown in table 7 and predicting UE location (which is different from the UE mobility Analytics ID specified in clause 6.7.2 3GPP TS 23.288 v!8.4.0) is illustrated in table 8.Table 7: UE access behaviour prediction exposed by AMF.Table 8: UE location prediction.
[0069] Figure 4 illustrates an example of a UE 400 in accordance with aspects of the present disclosure. The UE 400 may include a processor 402, a memory 404, a controller 406, and a transceiver 408. The processor 402, the memory 404, the controller 406, or the transceiver 408, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.
[0070] The processor 402, the memory 404, the controller 406, or the transceiver 408, or various combinations or components thereof may be implemented in hardware (e.g., circuitry). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), or other programmable logic device, or anycombination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.
[0071] The processor 402 may include an intelligent hardware device (e.g., a general- purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof). In some implementations, the processor 402 may be configured to operate the memory 404. In some other implementations, the memory 404 may be integrated into the processor 402. The processor 402 may be configured to execute computer-readable instructions stored in the memory 404 to cause the UE 400 to perform various functions of the present disclosure.
[0072] The memory 404 may include volatile or non-volatile memory. The memory 404 may store computer-readable, computer-executable code including instructions when executed by the processor 402 cause the UE 400 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such the memory 404 or another type of memory. Computer-readable media includes both non- transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general -purpose or special-purpose computer.
[0073] In some implementations, the processor 402 and the memory 404 coupled with the processor 402 may be configured to cause the UE 400 to perform one or more of the functions described herein (e.g., executing, by the processor 402, instructions stored in the memory 404). For example, the processor 402 may support wireless communication at the UE 400 in accordance with examples as disclosed herein.
[0074] The controller 406 may manage input and output signals for the UE 400. The controller 406 may also manage peripherals not integrated into the UE 400. In some implementations, the controller 406 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, the controller 406 may be implemented as part of the processor 402.
[0075] In some implementations, the UE 400 may include at least one transceiver 408. In some other implementations, the UE 400 may have more than one transceiver 408. Thetransceiver 408 may represent a wireless transceiver. The transceiver 408 may include one or more receiver chains 410, one or more transmitter chains 412, or a combination thereof.
[0076] A receiver chain 410 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain 410 may include one or more antennas for receive the signal over the air or wireless medium. The receiver chain 410 may include at least one amplifier (e.g., a low-noise amplifier (LN A)) configured to amplify the received signal. The receiver chain 410 may include at least one demodulator configured to demodulate the receive signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal. The receiver chain 410 may include at least one decoder for decoding the processing the demodulated signal to receive the transmitted data.
[0077] A transmitter chain 412 may be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 412 may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes like phase-shift keying (PSK) or quadrature amplitude modulation (QAM). The transmitter chain 412 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium. The transmitter chain 412 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.
[0078] Figure 5 illustrates an example of a processor 500 in accordance with aspects of the present disclosure. The processor 500 may be an example of a processor configured to perform various operations in accordance with examples as described herein. The processor 500 may include a controller 502 configured to perform various operations in accordance with examples as described herein. The processor 500 may optionally include at least one memory 504, which may be, for example, an L1 / L2 / L3 cache. Additionally, or alternatively, the processor 500 may optionally include one or more arithmetic-logic units (ALUs) 506. One or more of these components may be in electronic communication orotherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).
[0079] The processor 500 may be a processor chipset and include a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) in accordance with examples as described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory local to or included in the processor chipset (e.g., the processor 500) or other memory (e.g., random access memory (RAM), read-only memory (ROM), dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), static RAM (SRAM), ferroelectric RAM (FeRAM), magnetic RAM (MRAM), resistive RAM (RRAM), flash memory, phase change memory (PCM), and others).
[0080] The controller 502 may be configured to manage and coordinate various operations (e.g., signalling, receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) of the processor 500 to cause the processor 500 to support various operations in accordance with examples as described herein. For example, the controller 502 may operate as a control unit of the processor 500, generating control signals that manage the operation of various components of the processor 500. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating timing of operations.
[0081] The controller 502 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from the memory 504 and determine subsequent instruction(s) to be executed to cause the processor 500 to support various operations in accordance with examples as described herein. The controller 502 may be configured to track memory address of instructions associated with the memory 504. The controller 502 may be configured to decode instructions to determine the operation to be performed and the operands involved. For example, the controller 502 may be configured to interpret the instruction and determine control signals to be output to other components of the processor 500 to cause the processor 500 to support various operations in accordance with examples as described herein. Additionally, or alternatively, the controller 502 may be configured to manage flowof data within the processor 500. The controller 502 may be configured to control transfer of data between registers, arithmetic logic units (ALUs), and other functional units of the processor 500.
[0082] The memory 504 may include one or more caches (e.g., memory local to or included in the processor 500 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementations, the memory 504 may reside within or on a processor chipset (e.g., local to the processor 500). In some other implementations, the memory 504 may reside external to the processor chipset (e.g., remote to the processor 500).
[0083] The memory 504 may store computer-readable, computer-executable code including instructions that, when executed by the processor 500, cause the processor 500 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. The controller 502 and / or the processor 500 may be configured to execute computer-readable instructions stored in the memory 504 to cause the processor 500 to perform various functions. For example, the processor 500 and / or the controller 502 may be coupled with or to the memory 504, the processor 500, the controller 502, and the memory 504 may be configured to perform various functions described herein. In some examples, the processor 500 may include multiple processors and the memory 504 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions herein.
[0084] The one or more ALUs 506 may be configured to support various operations in accordance with examples as described herein. In some implementations, the one or more ALUs 506 may reside within or on a processor chipset (e.g., the processor 500). In some other implementations, the one or more ALUs 506 may reside external to the processor chipset (e.g., the processor 500). One or more ALUs 506 may perform one or more computations such as addition, subtraction, multiplication, and division on data. For example, one or more ALUs 506 may receive input operands and an operation code, which determines an operation to be executed. One or more ALUs 506 be configured with avariety of logical and arithmetic circuits, including adders, subtractors, shifters, and logic gates, to process and manipulate the data according to the operation. Additionally, or alternatively, the one or more ALUs 506 may support logical operations such as AND, OR, exclusive-OR (XOR), not-OR (NOR), and not- AND (NAND), enabling the one or more ALUs 506 to handle conditional operations, comparisons, and bitwise operations.
[0085] The processor 500 may support wireless communication in accordance with examples as disclosed herein. The processor 500 may be configured to or operable to support a means for receiving, from a second network function, a request for a predictive analytic service; determining an analytics result for addressing the request for the predictive analytic service and based on locally obtained data; and transmitting the analytics result to the second network function.
[0086] Further the processor 500 may be configured to or operable to support a means for transmitting, to a first network function, a request for a predictive analytic service; and receiving an analytics result from the first network function.
[0087] Figure 6 illustrates an example of a NE 600 in accordance with aspects of the present disclosure. The NE 600 may include a processor 602, a memory 604, a controller 606, and a transceiver 608. The processor 602, the memory 604, the controller 606, or the transceiver 608, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.
[0088] The processor 602, the memory 604, the controller 606, or the transceiver 608, or various combinations or components thereof may be implemented in hardware (e.g., circuitry). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.
[0089] The processor 602 may include an intelligent hardware device (e.g., a general- purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof). Insome implementations, the processor 602 may be configured to operate the memory 604. In some other implementations, the memory 604 may be integrated into the processor 602. The processor 602 may be configured to execute computer-readable instructions stored in the memory 604 to cause the NE 600 to perform various functions of the present disclosure.
[0090] The memory 604 may include volatile or non-volatile memory. The memory 604 may store computer-readable, computer-executable code including instructions when executed by the processor 602 cause the NE 600 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such the memory 604 or another type of memory. Computer-readable media includes both non- transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general -purpose or special-purpose computer.
[0091] In some implementations, the processor 602 and the memory 604 coupled with the processor 602 may be configured to cause the NE 600 to perform one or more of the functions described herein (e.g., executing, by the processor 602, instructions stored in the memory 604). For example, the processor 602 may support wireless communication at the NE 600 in accordance with examples as disclosed herein. The NE 600 may be configured to support a means for receiving, from a second network function, a request for a predictive analytic service; determining an analytics result for addressing the request for the predictive analytic service and based on locally obtained data; and transmitting the analytics result to the second network function.
[0092] Further, the NE 600 may be configured to support a means for transmitting, to a first network function, a request for a predictive analytic service; and receiving an analytics result from the first network function.
[0093] The controller 606 may manage input and output signals for the NE 600. The controller 606 may also manage peripherals not integrated into the NE 600. In some implementations, the controller 606 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, the controller 606 may be implemented as part of the processor 602.
[0094] In some implementations, the NE 600 may include at least one transceiver 608. In some other implementations, the NE 600 may have more than one transceiver 608. The transceiver 608 may represent a wireless transceiver. The transceiver 608 may include one or more receiver chains 610, one or more transmitter chains 612, or a combination thereof.
[0095] A receiver chain 610 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain 610 may include one or more antennas for receive the signal over the air or wireless medium. The receiver chain 610 may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain 610 may include at least one demodulator configured to demodulate the receive signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal. The receiver chain 610 may include at least one decoder for decoding the processing the demodulated signal to receive the transmitted data.
[0096] A transmitter chain 612 may be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 612 may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes like phase-shift keying (PSK) or quadrature amplitude modulation (QAM). The transmitter chain 612 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium. The transmitter chain 612 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.
[0097] Figure 7 illustrates a flowchart of a method 700 in accordance with aspects of the present disclosure. The operations of the method 700 may be implemented by a NE as described herein. In some implementations, the NE may execute a set of instructions to control the function elements of the NE to perform the described functions.
[0098] At 702, the method 700 may include receiving, from a second network function, a request for a predictive analytic service. The operations of 702 may be performed inaccordance with examples as described herein. In some implementations, aspects of the operations of 702 may be performed by a NE as described with reference to Figure 6.
[0099] At 704, the method 700 may include determining an analytics result for addressing the request for the predictive analytic service and based on locally obtained data. The operations of 704 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 704 may be performed by a NE as described with reference to Figure 6.
[0100] At 706, the method 700 may include transmitting the analytics result to the second network function. The operations of 706 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 706 may be performed a NE as described with reference to Figure 6.
[0101] Figure 8 illustrates a flowchart of a method 800 in accordance with aspects of the present disclosure. The operations of the method 800 may be implemented by a NE as described herein. In some implementations, the NE may execute a set of instructions to control the function elements of the NE to perform the described functions.
[0102] At 802, the method 800 may include transmitting, to a first network function, a request for a predictive analytic service. The operations of 802 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 802 may be performed by a NE as described with reference to Figure 6.
[0103] At 804, the method 800 may include receiving an analytics result from the first network function. The operations of 804 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 804 may be performed by a NE as described with reference to Figure 6.
[0104] There is provided herein a first network function for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the first network function to: receive, from a second network function, a request for a predictive analytic service; determine an analytics result for addressing the request for the predictive analytic service and based on locally obtained data; and transmit the analytics result to the second network function.
[0105] Such a first network function tends to provide a mechanism to enable predictive data analytics on network nodes for specific performance measurements, counters or KPIs based on locally collected data. Predictions obtained by such network functions locally can be simple and targeted. Such simple and targeted predictions or analytics results avoid unnecessary production and transmission of results that they will not be used. This can result in more efficient use of network resources, including both communication bandwidth and processing resources within network functions. Further, such arrangements tend to deliver predictions or analytics results faster, since the data collection and processing is focused and so tends to be shorter. Focused data collection and processing may result in reduced cost of operation of the predictive analytic service.
[0106] There are disclosed herein new Event IDs and / or PM / counter / KPI IDs and the related predictive parameters that can enable a consumer to request or subscribe and receive predictive analytics data from NFs based on locally collected data.
[0107] The first network function may be a Network Function Producer. The second network function may be an analytics consumer. The second network function may be a Network Function Consumer.
[0108] The locally obtained data may be locally measured data. The locally obtained data may be locally collected data. The collected data may comprise measurements taken by other network functions interrelated with the first network function.
[0109] The at least one processor may be further arranged to determine the analytics result by determining the analytics result based on one or more of an algorithm and / or learning model embedded in the first network function. The algorithm and / or learning model may comprise artificial intelligence and / or machine learning.
[0110] The first network function may comprise one or more of a network entity, a platform, a logical entity, an inter-related function, and / or a member of a set with a specified identifier.[OHl] The locally obtained data may be obtained via a third network function. The third network function may be local to the first network function. The third network function may be directly controlled by the first network function. The third networkfunction may be inter-related to the first network function. The obtained data is thus locally obtained data based on the third network function being local to the first network function.
[0112] The at least one processor may be further arranged to register information related to predictive analytics that are offered by the first network function. The registered information may comprise capabilities of the first network function, the capabilities of the first network function defining the capability of the first network function to perform predictive analytics. The registered information may comprise identifiers of predictive analytics, the identifiers of predictive analytics identifying predictive analytics that the first network function is capable of providing. The predictive analytics that the first network function is capable of providing may be referred to as offered predictive analytics.
[0113] The request for the predictive analytic service comprises at least one of the following: an identifier related to an event; an identifier related to a performance measurement; an identifier related to a counter; an identifier related to a key performance indicator; a target interval related to the collection of analytics results; a target schedule related to the reporting of analytics results; an accuracy level of analytics results; a granularity level of analytics results; a data source for analytics results; a data range for analytics results; a reporting threshold for analytics results; and / or a usage context related to analytics results.
[0114] The analytics result may include at least one of the following: an identifier related to an event; an identifier related to a performance measurement; an identifier related to a counter; an identifier related to a key performance indicator; a time stamp to indicate when the analytic result were determined; a validity period that indicates until when the analytics result shall be used; a target object list where the predictive analytic service involves multiple different objects; a confidence level related to the analytic results; and / or an identifier that associates the transmitted analytics result with the received request for a predictive analytic service.
[0115] There is further provided a processor for wireless communication, comprising: at least one controller coupled with at least one memory and configured to cause the processor to: receive, from a second network function, a request for a predictive analytic service; determine an analytics result for addressing the request for the predictive analyticservice and based on locally obtained data; and transmit the analytics result to the second network function.
[0116] There is further provided a method performed by a first network function, the method comprising: receiving, from a second network function, a request for a predictive analytic service; determining an analytics result for addressing the request for the predictive analytic service and based on locally obtained data; and transmitting the analytics result to the second network function.
[0117] Such an arrangement tends to provide a mechanism to enable predictive data analytics on network nodes for specific performance measurements, counters or KPIs based on locally collected data. Predictions obtained by such network functions locally can be simple and targeted. Such simple and targeted predictions or analytics results avoid unnecessary production and transmission of results that they will not be used. This can result in more efficient use of network resources, including both communication bandwidth and processing resources within network functions. Further, such arrangements tend to deliver predictions or analytics results faster, since the data collection and processing is focused and so tends to be shorter. Focused data collection and processing may result in reduced cost of operation of the predictive analytic service.
[0118] There are disclosed herein new Event IDs and / or PM / counter / KPI IDs and the related predictive parameters that can enable a consumer to request or subscribe and receive predictive analytics data from NFs based on locally collected data.
[0119] The first network function may be a Network Function Producer. The second network function may be an analytics consumer. The second network function may be a Network Function Consumer.
[0120] The locally obtained data may be locally measured data. The locally obtained data may be locally collected data. The collected data may comprise measurements taken by other network functions interrelated with the first network function.
[0121] Determining the analytics result may comprise determining the analytics result based on one or more of an algorithm and / or learning model embedded in the first networkfunction. The algorithm and / or learning model may comprise artificial intelligence and / or machine learning.
[0122] The first network function may comprise one or more of: a network entity, a platform, a logical entity, an inter-related function, and / or a member of a set with a specified identifier.
[0123] The locally obtained data may be data obtained via a third network function. The third network function may be local to the first network function. The third network function may be directly controlled by the first network function. The third network function may be inter-related to the first network function. The obtained data is thus locally obtained data based on the third network function being local to the first network function.
[0124] The method may further comprise registering information related to predictive analytics that are offered by the first network function. The registered information may comprise capabilities of the first network function, the capabilities of the first network function defining the capability of the first network function to perform predictive analytics. The registered information may comprise identifiers of predictive analytics, the identifiers of predictive analytics identifying predictive analytics that the first network function is capable of providing. The predictive analytics that the first network function is capable of providing may be referred to as offered predictive analytics.
[0125] The request for the predictive analytic service may comprise at least one of the following: an identifier related to an event; an identifier related to a performance measurement; an identifier related to a counter; an identifier related to a key performance indicator; a target interval related to the collection of analytics results; a target schedule related to the reporting of analytics results; an accuracy level of analytics results; a granularity level of analytics results; a data source for analytics results; a data range for analytics results; a reporting threshold for analytics results; and / or a usage context related to analytics results.
[0126] The analytics result may include at least one of the following: an identifier related to an event; an identifier related to a performance measurement; an identifier related to a counter; an identifier related to a key performance indicator; a time stamp to indicatewhen the analytic result were determined; a validity period that indicates until when the analytics result shall be used; a target object list where the predictive analytic service involves multiple different objects; a confidence level related to the analytic results; and / or an identifier that associates the transmitted analytics result with the received request for a predictive analytic service.
[0127] There is further provided a second network function for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the second network function to: transmit, to a first network function, a request for a predictive analytic service; and receive an analytics result from the first network function.
[0128] Such a second network function tends to provide a mechanism to request predictive data analytics on network nodes for specific performance measurements, counters or KPIs based on locally collected data. Predictions obtained by such network functions locally can be simple and targeted. Such simple and targeted predictions or analytics results avoid unnecessary production and transmission of results that they will not be used. This can result in more efficient use of network resources, including both communication bandwidth and processing resources within network functions. Further, such arrangements tend to deliver predictions or analytics results faster, since the data collection and processing is focused and so tends to be shorter. Focused data collection and processing may result in reduced cost of operation of the predictive analytic service.
[0129] The first network function may be a Network Function Producer. The first network function may be arranged to determine the analytics result required to address the predictive analytic service, the analytics determined based on locally obtained data. The analytics result may be determined by the first network function based on an algorithm embedded therein. The algorithm may comprise artificial intelligence and / or machine learning. The locally obtained data may be locally measured data. The locally obtained data may be locally collected data. The locally collected data may comprise measurements taken by other network functions.
[0130] The second network function may be an analytics consumer. The second network function may be a Network Function Consumer. The first network function maycomprise at least one of: a network entity, a platform, a logical entity, an inter-related function, and / or a member of a set with a specified identifier.
[0131] The at least one processor may be further arranged to discover the first network function that can provide the predictive analytics service. The discovery may be based on registered information related to the predictive analytics services offered by the first network function. If the second network function is a trusted node then the second network function can discover the first network function via direct communication.
[0132] The at least one processor may be further arranged to discover the first network function that can provide the predictive analytics service via an intermediate node. The intermediate node may authenticate the discovery on behalf of the second network function. The intermediate node may forward the results of the discovery from the first network function to the second network function. The intermediate node may comprise a NEF.
[0133] If the second network function is an untrusted application function, then the discovery, which may take the form of a discover request is handled by the NEF. The discover request may include an additional identifier and parameters. The NEF is responsible for authenticating the request and identifying as well as selecting the appropriate first network function. Hence, the NEF may expose to untrusted second network functions services that are to be extended with the respective new identifier and parameters as well as with the new reporting capabilities.
[0134] The request for a predictive analytic service may comprise at least one of the following: an identifier related to an event; an identifier related to a performance measurement; an identifier related to a counter; an identifier related to a key performance indicator; a target interval related to the collection of analytics results; a target interval related to the reporting of analytics results; an accuracy level of analytics results; a granularity level of analytics results; a data source for analytics results; a data range for analytics results; a reporting threshold for analytics results; and / or a usage context related to analytics results.
[0135] The analytics result received by the second network function may include at least one of the following: an identifier related to an event; an identifier related to aperformance measurement; an identifier related to a counter; an identifier related to a key performance indicator; a time stamp to indicate when the analytic result were determined; a validity period that indicates until when the analytics result shall be used; a target object list where the predictive analytic service involves multiple different objects; a confidence level related to the analytic results; and / or an identifier that associates the transmitted analytics result with the received request for a predictive analytic service.
[0136] There is further provided a processor for wireless communication, comprising: at least one controller coupled with at least one memory and configured to cause the processor to: transmit, to a first network function, a request for a predictive analytic service; and receive an analytics result from the first network function.
[0137] There is further provided a method performed by a second network function, the method comprising: transmitting, to a first network function, a request for a predictive analytic service; and receiving an analytics result from the first network function.
[0138] Such a method tends to provide a mechanism to enable predictive data analytics on network nodes for specific performance measurements, counters or KPIs based on locally collected data. Predictions obtained by such network functions locally can be simple and targeted. Such simple and targeted predictions or analytics results avoid unnecessary production and transmission of results that they will not be used. This can result in more efficient use of network resources, including both communication bandwidth and processing resources within network functions. Further, such arrangements tend to deliver predictions or analytics results faster, since the data collection and processing is focused and so tends to be shorter. Focused data collection and processing may result in reduced cost of operation of the predictive analytic service.
[0139] The first network function may be a Network Function Producer. The first network function may be arranged to determine the analytics result required to address the predictive analytic service; the analytics determined based on locally obtained data. The analytics result may be determined by the first network function based on an algorithm embedded therein. The algorithm may comprise artificial intelligence and / or machine learning. The locally obtained data may be locally measured data. The locally obtaineddata may be locally collected data. The locally collected data may comprise measurements taken by other network functions.
[0140] The second network function may be an analytics consumer. The second network function may be a Network Function Consumer. The first network function may comprise at least one of: a network entity, a platform, a logical entity, an inter-related function, and / or a member of a set with a specified identifier.
[0141] The method may further comprise discovering the first network function that can provide the predictive analytics service. The discovery may be based on registered information related to the predictive analytics services offered by the first network function. If the second network function is a trusted node, then the second network function can discover the first network function via direct communication.
[0142] The method may further comprise discovering the first network function that can provide the predictive analytics service via an intermediate node. The intermediate node may authenticate the discovery on behalf of the second network function. The intermediate node may forward the results of the discovery from the first network function to the second network function. The intermediate node may comprise a NEF.
[0143] If the second network function is an untrusted application function, then the discovery, which may take the form of a discover request is handled by the NEF. The discover request may include an additional identifier and parameters. The NEF is responsible for authenticating the request and identifying as well as selecting the appropriate first network function. Hence, the NEF may expose to untrusted second network functions services that are to be extended with the respective new identifier and parameters as well as with the new reporting capabilities.
[0144] The request for a predictive analytic service may comprise at least one of the following: an identifier related to an event; an identifier related to a performance measurement; an identifier related to a counter; an identifier related to a key performance indicator; a target interval related to the collection of analytics results; a target interval related to the reporting of analytics results; an accuracy level of analytics results; a granularity level of analytics results; a data source for analytics results; a data range foranalytics results; a reporting threshold for analytics results; and / or a usage context related to analytics results.
[0145] The analytics result received by the second network function may include at least one of the following: an identifier related to an event; an identifier related to a performance measurement; an identifier related to a counter; an identifier related to a key performance indicator; a time stamp to indicate when the analytic result were determined; a validity period that indicates until when the analytics result shall be used; a target object list where the predictive analytic service involves multiple different objects; a confidence level related to the analytic results; and / or an identifier that associates the transmitted analytics result with the received request for a predictive analytic service.
[0146] Network analytics predictions are complex involving several input data collected at an analytics network node (i.e., NWDAF), which produces a report that contains several predictive results. In known systems consumers of predictive data analytics have no option to obtain only specific performance measurements, counters or KPIs but are enforced to always receive a predetermined report that may contain unnecessary data for specific use cases, e.g., for predicting energy consumption, which only needs the data volume. In other words, there are no predictions related to single data measurements, counters or KPIs, which can be determined locally at a specific network node using local data.
[0147] There is described herein an apparatus and method introducing a mechanism to enable predictive data analytics on network nodes for specific performance measurements, counters or KPIs based on locally collected data. Predictions obtained by NFs locally can be simple, targeted, and not provide results that will not be used. Such predictions can be obtained quickly since the data collection and processing is shorter, and cheaper. To assist in the above, there are described herein new Event IDs and / or PM / counter / KPI IDs and the related predictive parameters that may enable a consumer to request or subscribe and receive predictive analytics data from NFs based on locally collected data.
[0148] Known systems do not consider any mechanism to enable predictive analytics on network nodes based on local data. The following arrangements are described herein:• Predictive analytic services on AMF introducing the related event and measurement identifiers as well as the respective parameters to enable a consumer to request predictive data.• Predictive analytic services on SMF introducing the related event and measurement identifiers as well as the respective parameters to enable a consumer to request predictive data.• Predictive analytic services on UPF introducing the related event and measurement identifiers as well as the respective parameters to enable a consumer to request predictive data.
[0149] Accordingly, there is described herein an apparatus and a method that allow a first network entity [such as an NF producer] to determine predictive analytics results using embedded intelligence based on locally collected data.
[0150] The first network entity can be: a network function or platform or a logical entity; an inter-related function; and / or a member of a set with a specified identifier.
[0151] The locally collected data can be data obtained from the first network entity and / or from another network entity that is directly controlled or inter-related to the first network entity.
[0152] The first network entity [such as an NF producer] may: receive a request for determining predictive analytic services, determine the request analytics based on locally obtained data, transmit the predictive analytics result to the analytics consumer.
[0153] The first network entity [such as an NF producer] may register information related to the offered predictive analytics.
[0154] The second network entity [such as an NF consumer] may discover a first network entity [such as an NF producer] that can provide predictive analytics, based register information related to the offered predictive analytics.
[0155] The second network entity [such as an NF consumer] may receive predictive analytics using exposure capabilities of an intermediate node, if the second network entity is an untrusted entity.
[0156] The information related to the offered predictive analytics may include at least one of the following: an identifier related to an event, and / or to a performance measurement, and / or to a counter and / and / or to a key performance indicator; the desired future target interval related to the prediction analytics; the preferred accuracy related to the prediction analytics; the granularity related to the prediction analytics; the data sources, and / or data range and / or other data statistics related to the prediction analytics; reporting threshold related to the prediction analytics; and / or the usage context related to the prediction analytics.
[0157] The information related to the transmitted predictive analytics may include at least one of the following: an identifier related to an event, and / or to a performance measurement, and / or to a counter and / and / or to a key performance indicator; a time stamp to indicate when the predictive analytics where determined; a validity period that indicates until when the predictive analytics shall be used; a target object list if the prediction involves multiple different objects; the confidence level related to the predictive analytics; and / or an identifier that associates the report with the request.
[0158] It should be noted that the method described herein describes a possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible.
[0159] The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.
[0160] The following abbreviations are relevant in the field addressed by this document: 3GPP, 3rd Generation Partnership Project; 5G, 5th Generation of Mobile Communication; AI / ML , Artificial Intelligence / Machine Learning ; ADRF, Analytical Data Repository Function; AF, Application Function; AMF, Access and Mobility Function; AnLF, Analytics Logical Function; BSF , Binding Support Function; CM, Configuration Management; CM-state, Connection Management-state; DCAF, Data Collection AF;DCCF, Data Collection Coordination Functionality; DL, Downlink; DNN , Data Network Name; KPI, Key Performance Indicator; MF , Management Function; MFAF, Messaging Framework Adaptor Function; MnS, Management Service; MTLF , Model Training Logical Function; NEF, Network Exposure Function; NF, Network Function; NRF, Network Repository Function ; NWDAF , Network Data Analytics Function; OAM, Operations, Administration and Maintenance; PDU, Protocol Data Unit; PLMN , Public Land Mobile Network; PM, Performance Measurement; QoS, Quality of Service; RM, Resource Management; SMF, Session Management Function; S-NSSAI , Single-Network Slice Selection Assistance Information; SUPI , Subscription Permanent Identifier; TAI , Tracking Area Identity; UDM, User Data manager ; UDR, User Data Repository; UL, Uplink; UPF, User Plane Function; and UE, User Equipment.
Claims
CLAIMSWhat is claimed is:
1. A first network function for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the first network function to: receive, from a second network function, a request for a predictive analytic service; determine an analytics result for addressing the request for the predictive analytic service and based on locally obtained data; and transmit the analytics result to the second network function.
2. The first network function of claim 1, wherein, to determine the analytics result, the at least one processor is configured to cause the first network function to determine the analytics result based on one or more of an algorithm and / or a learning model embedded in the first network function.
3. The first network function of claim 2, wherein the first network function comprises one or more of: a network entity, a platform, a logical entity, an inter-related function, and / or a member of a set with a specified identifier.
4. The first network function of any of claims 1 to 3, wherein the at least one processor is configured to cause the first network function to: obtain the locally obtained data via a third network function, wherein the third network function is local to the first network function.
5. The first network function of any of claims 1 to 4, wherein the at least one processor is configured to cause the first network function to register information related to predictive analytics offered by the first network function.
6. The first network function of any of claims 1 to 5, wherein the request for the predictive analytic service comprises at least one of the following: an identifier related to an event; an identifier related to a performance measurement; an identifier related to a counter; an identifier related to a key performance indicator; a target interval related to the collection of analytics results; a target schedule related to the reporting of analytics results; an accuracy level of analytics results; a granularity level of analytics results; a data source for analytics results; a data range for analytics results; a reporting threshold for analytics results; and / or a usage context related to analytics results.
7. The first network function of any of claims 1 to 6, wherein the analytics result includes at least one of the following: an identifier related to an event; an identifier related to a performance measurement; an identifier related to a counter; an identifier related to a key performance indicator; a time stamp to indicate when the analytic result were determined; a validity period that indicates until when the analytics result shall be used; a target object list where the predictive analytic service involves multiple different objects; a confidence level related to the analytic results; and / oran identifier that associates the transmitted analytics result with the received request for a predictive analytic service.
8. A processor for wireless communication, comprising: at least one controller coupled with at least one memory and configured to cause the processor to: receive, from a second network function, a request for a predictive analytic service; determine an analytics result for addressing the request for the predictive analytic service and based on locally obtained data; and transmit the analytics result to the second network function.
9. A method performed by a first network function, the method comprising: receiving, from a second network function, a request for a predictive analytic service; determining an analytics result for addressing the request for the predictive analytic service and based on locally obtained data; and transmitting the analytics result to the second network function.
10. The method of claim 9, wherein determining the analytics result comprises determining the analytics result based on one or more of an algorithm and / or a learning model embedded in the first network function.
11. The method of claim 10, wherein the first network function comprises one or more of: a network entity, a platform, a logical entity, an inter-related function, and / or a member of a set with a specified identifier.
12. The method of any of claims 9 to 11, further comprising obtaining the locally obtained data via a third network function, wherein the third network function is local to the first network function.
13. The method of any of claims 9 to 12, further comprising registering information related to predictive analytics that are offered by the first network function.
14. The method of any of claims 9 to 13, wherein the request for the predictive analytic service comprises at least one of the following: an identifier related to an event; an identifier related to a performance measurement; an identifier related to a counter; an identifier related to a key performance indicator; a target interval related to the collection of analytics results; a target schedule related to the reporting of analytics results; an accuracy level of analytics results; a granularity level of analytics results; a data source for analytics results; a data range for analytics results; a reporting threshold for analytics results; and / or a usage context related to analytics results.
15. A second network function for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the second network function to: transmit, to a first network function, a request for a predictive analytic service; and receive an analytics result from the first network function.
16. The second network function of claim 15, wherein the second network function is an analytics consumer.
17. The second network function of any of claims 15 and 16, wherein the at least one processor is further configured to cause the second network function to discover the first network function supporting the predictive analytics service.
18. The second network function of any of claims 15 to 16, wherein the at least one processor is further configured to cause the second network function to discover the first network function supporting the predictive analytics service via an intermediate node.
19. The second network function of any of claims 15 to 18, wherein the request for a predictive analytic service comprises at least one of the following: an identifier related to an event; an identifier related to a performance measurement; an identifier related to a counter; an identifier related to a key performance indicator; a target interval related to the collection of analytics results; a target interval related to the reporting of analytics results; an accuracy level of analytics results; a granularity level of analytics results; a data source for analytics results; a data range for analytics results; a reporting threshold for analytics results; and / or a usage context related to analytics results.
20. The second network function of any of claims 15 to 19, wherein the analytics result received by the second network function includes at least one of the following: an identifier related to an event; an identifier related to a performance measurement; an identifier related to a counter; an identifier related to a key performance indicator; a time stamp to indicate when the analytic result were determined;a validity period that indicates until when the analytics result shall be used; a target object list where the predictive analytic service involves multiple different objects; a confidence level related to the analytic results; and / or an identifier that associates the transmitted analytics result with the received request for a predictive analytic service.
Citation Information
Patent Citations
Network assistance information providing method and apparatus, electronic device, and computer-readable storage medium
US20220217514A1
