Method and apparatus for media application function exposure function

Abstract

Embodiments include methods and apparatus for media application function (AF) exposure functions. Various aspects can include receiving an access configuration message for a service or application provider, the access configuration message including an indication of one or more event types and parameters, one or more exposure levels, and aggregation rules. Various embodiments can include an AF server subscribing other computing devices to event types and parameters for a service or application based on exposure levels of the other computing devices.

Description

Background Technology

[0001] Long Term Evolution (LTE), 5G New Radio (5GNR), and other recently developed communication technologies allow wireless devices to transmit information at data rates (e.g., in gigabits per second) that are orders of magnitude greater than those available just a few years ago. Today's communication networks are also more secure, fault-tolerant to multipath fading, allow for lower network traffic latency, and provide better communication efficiency (e.g., in units of bandwidth used per second). These and other recent improvements have facilitated the emergence of new ways of delivering media and content to mobile wireless devices, including broadcast, multicast, and unicast media delivery technologies. Summary of the Invention

[0002] The aspects include methods and apparatus for Media Application Function (AF) opening functionality. The aspects may include methods executed by a processor of a service or application provider server for controlling access to logs associated with a service or application provided via a fifth-generation (5G) system (5GS) network. The aspects may include: determining one or more event types and parameters to enable information opening for service or application information for the service or application; determining one or more opening levels for the service or application; determining aggregation rules for each of the one or more event types and parameters under each of the one or more opening levels; generating an access configuration message for the service or application, the access configuration message including indications to the one or more event types and parameters, the one or more opening levels, and the aggregation rules; and sending the access configuration message to an AF server.

[0003] Some aspects may further include: receiving an authorization request associated with another computing device; determining whether the other computing device is authorized to access logs used for the service or application; in response to determining that the other computing device is authorized to access logs used for the service or application, determining a metric openness level for the other device, and sending an authorization confirmation indicating the openness level for the other computing device. In some aspects, the authorization confirmation may include a token for the other device, the token indicating the openness level for the other device. In some aspects, the other computing device may be a Network Data Analysis Function (NWDAF) server.

[0004] The various aspects include a method for controlling access to logs associated with a service or application, executed by a processor of an Application Function (AF) server of a fifth-generation (5G) system (5GS). The various aspects may include: receiving an access configuration message from a service or application provider, the access configuration message including indications for one or more event types and parameters, one or more open levels, and aggregation rules for the service or application; receiving a customization request for logs of the service or application from another computing device; determining an open level of the other computing device; determining event types and parameters for the service or application and aggregation rules for the event types and parameters, based at least in part on the access configuration message for the service or application and the open level of the other computing device; generating a customization response message for the other computing device, the customization response message indicating the event types and parameters for the service or application and the aggregation rules for the event types and parameters; and sending the customization response message to the other computing device.

[0005] Some aspects may further include: receiving reports for the service or application from one or more wireless devices consuming the service or application; receiving a request for available logs from the other computing device; authenticating the other computing device in response to receiving the request for available logs from the other computing device; determining an open level for the other device based on the authentication; generating a log report based on the reports for the service or application from the one or more wireless devices consuming the service or application; generating a log report according to the open level for the service or application associated with the determined access level of the other computing device; and sending the log report to the other device. In some aspects, determining the open level of the other computing device may include: authenticating a token for the other device indicating the open level for the other device.

[0006] In some aspects, aggregation rules may include aggregation functions, aggregation periods, and / or aggregation groups for the service or application. In some aspects, the aggregation functions may include one or more of the following: COUNT function, AVERAGE function, MEDIAN function, MINIMUM function, MAXIMUM function, or SUM function. In some aspects, the aggregation period may include a session or time period. In some aspects, the aggregation group may include an individual user, a user group, a user location, a content identifier, a subscribed service, a subscription type, or all users together. In some aspects, the one or more event types may include one or more of the following: content hosting event type, Quality of Service (QoS) / billing and network ancillary event type, consumption event type, or Quality of Experience (QoE) event type. In some aspects, the service or application may be a 5G Media Streaming (5GMS) service or application.

[0007] Another aspect may include a wireless device having a processor configured to perform one or more operations of the methods described above. A further aspect may include a non-transitory processor-readable storage medium having processor-executable instructions stored thereon, the processor-executable instructions being configured to cause the processor of the wireless device to perform the operations of the methods described above. A further aspect includes a wireless device having units for performing the functions of the methods described above. A further aspect includes a system-on-chip for use in a wireless device, comprising a processor configured to perform one or more operations of the methods described above. A further aspect includes a system-in-package comprising two systems-on-chips for use in a wireless device, each system-on-chip comprising a processor configured to perform one or more operations of the methods described above. A further aspect may include a network computing device having a processor configured to perform one or more operations of the methods described above. A further aspect may include a non-transitory processor-readable storage medium having processor-executable instructions stored thereon, the processor-executable instructions being configured to cause the processor of the network computing device to perform the operations of the methods described above. A further aspect includes a network computing device having units for performing the functions of the methods described above. Attached Figure Description

[0008] The accompanying drawings, which are incorporated herein and form part of this specification, illustrate exemplary embodiments of the claims and, together with the general description given above and the detailed description given below, serve to interpret the features of the claims.

[0009] Figure 1 This is a system block diagram illustrating an example communication system suitable for implementing any of the various embodiments.

[0010] Figure 2 This is a block diagram of components for an example computing and wireless modem system suitable for implementing any of the various embodiments.

[0011] Figure 3 This is a component block diagram illustrating a software architecture suitable for implementing any of the various embodiments, including a radio protocol stack for the user plane and control plane in wireless communication.

[0012] Figure 4A This is an architecture diagram illustrating the interaction and interface between an application function (AF) server and a wireless device for 5G media streaming, according to various embodiments.

[0013] Figure 4B This is an architecture diagram illustrating AF open interaction in a 5G system.

[0014] Figure 4C This is an architecture diagram illustrating the interaction of Network Data Analysis Function (NWDAF) in the 5G core network.

[0015] Figure 5A This is a process flowchart illustrating a method for controlling access to logs associated with a service or application, according to various embodiments.

[0016] Figure 5B These are example patterns of access configuration messages based on various embodiments.

[0017] Figure 6A This is a process flowchart illustrating a method for controlling access to logs associated with a service or application, according to various embodiments.

[0018] Figure 6B This is a process flowchart illustrating a method for controlling access to logs associated with a service or application, according to various embodiments.

[0019] Figure 6C This is a process flowchart illustrating a method for authorizing access to logs associated with a service or application, according to various embodiments.

[0020] Figure 7A This is a call flow diagram illustrating the interaction between the AF and NWDAF for log delivery according to various embodiments.

[0021] Figure 7B This is a call flowchart illustrating an interaction in a 5G system according to various embodiments for controlling access to logs associated with a service or application.

[0022] Figure 8 This is a component block diagram of a network computing device suitable for use with various embodiments.

[0023] Figure 9 This is a component block diagram suitable for use with various embodiments of a wireless device. Detailed Implementation

[0024] Various embodiments will be described in detail with reference to the accompanying drawings. Where possible, the same reference numerals will be used throughout the drawings to refer to the same or similar parts. References to specific examples and implementations are for illustrative purposes and are not intended to limit the scope of the claims.

[0025] Various embodiments include methods and apparatus for Media Application Function (AF) open functionality. Various embodiments include methods for controlling access to logs, such as logs of data (e.g., metrics, measurements, etc.) collected in association with a service or application executed by the processor of an Application Function (AF) server of a fifth-generation (5G) system (5GS). Various embodiments enable control over access levels to collected information for different network functions. Various embodiments enable application providers to protect user privacy. Various embodiments enable application providers to prevent the exposure of service-specific details to entities unauthorized to receive such information. Various embodiments can protect user and service privacy by allowing differentiated access to service and application log data and statistics. Various embodiments may be compatible with the 5G AF open framework. Various embodiments may be compatible with the 5G Media Streaming (also known as 5GMS) architecture.

[0026] The term "wireless device" as used herein refers to any or all of the following: wireless router devices, wireless home appliances, cellular phones, smartphones, portable computing devices, personal or mobile multimedia players, laptops, tablets, smartbooks, ultrabooks, PDAs, wireless email receivers, multimedia internet-driven cellular phones, medical devices and equipment, biometric sensors / devices, wearable devices including smartwatches, smart clothing, smart glasses, smart wristbands, smart jewelry (e.g., smart rings, smart bracelets, etc.), entertainment devices (e.g., wireless game controllers, music and video players, satellite wireless units, etc.), wireless network-driven Internet of Things (IoT) devices including smart meters / sensors, industrial manufacturing equipment, large and small machines and large and small home appliances for home or business use, wireless communication elements in autonomous and semi-autonomous vehicles, wireless devices attached to or incorporated into various mobile platforms, global positioning system devices, and similar electronic devices including memory, wireless communication components, and programmable processors.

[0027] The term "System-on-a-Chip" (SOC) is used herein to refer to a single integrated circuit (IC) chip containing multiple resources and / or processors integrated on a single substrate. A single SOC may contain circuitry for digital, analog, mixed-signal, and radio frequency functions. A single SOC may also include any number of general-purpose and / or special-purpose processors (digital signal processors, modem processors, video processors, etc.), memory blocks (e.g., ROM, RAM, flash memory, etc.), and resources (e.g., timers, voltage regulators, oscillators, etc.). A SOC may also include software for controlling the integrated resources and processors, as well as software for controlling peripheral devices.

[0028] The term "system-in-package" (SIP) may be used herein to refer to a single module or package containing multiple resources, computing units, cores, and / or processors on two or more IC chips, substrates, or SoCs. For example, a SIP may include a single substrate on which multiple IC chips or semiconductor dies are stacked in a vertical configuration. Similarly, a SIP may include one or more multi-chip modules (MCMs) on which multiple ICs or semiconductor dies are packaged into a unified substrate. A SIP may also include multiple independent SoCs coupled together via high-speed communication circuitry and packaged close together (e.g., on a single motherboard or in a single wireless device). The proximity of the SoCs facilitates high-speed communication and the sharing of memory and resources.

[0029] In this document, the term "multi-core processor" may be used to refer to a single integrated circuit (IC) chip or chip package containing two or more independent processing cores (e.g., CPU cores, Internet Protocol (IP) cores, graphics processing unit (GPU) cores, etc.) configured to read and execute program instructions. A System-on-a-Chip (SoC) may include multiple multi-core processors, and each processor in the SoC may be referred to as a core. The term "multi-processor" may be used in this document to refer to a system or device comprising two or more processing units configured to read and execute program instructions.

[0030] As used herein, the terms “SIM,” “SIM card,” and “Subscriber Identity Module” can interchangeably refer to a memory that may be an integrated circuit or embedded in a removable card, and that stores the International Mobile Subscriber Identity (IMSI), associated keys, and / or other information used to identify and / or authenticate wireless devices on a network and to enable communication services with the network. Examples of SIM include the Universal Subscriber Identity Module (USIM) provided in the Long Term Evolution (LTE) 3GPP standard, and the Removable Subscriber Identity Module (R-UIM) provided in the 3GPP standard. Universal Integrated Circuit Card (UICC) is another term for SIM card. Furthermore, SIM can also refer to a Virtual SIM (VSIM), which can be implemented as a remote SIM profile loaded into an application on a wireless device and implements the normal SIM functionality on the wireless device.

[0031] Because the information stored in a SIM enables a wireless device to establish a communication link with a specific network for one or more specific communication services, the term "SIM" is also used herein as an abbreviation for the communication service associated with and enabled by the information stored in a specific SIM, since the SIM, the communication network, and the services and subscriptions supported by that network are related to each other. Similarly, the term SIM can also be used as an abbreviation for the protocol stack and / or modem stack used and the communication process when establishing and conducting communication services with subscriptions and networks enabled by information stored in a specific SIM.

[0032] As used herein, the terms “multi-SIM wireless device,” “MS wireless device,” “dual-SIM wireless device,” and “DS wireless device” can be used interchangeably to describe a wireless device configured with more than one SIM. Examples of multi-SIM wireless devices include multi-SIM multi-standby (MSMS) wireless devices (such as dual-SIM (DS) dual-standby (DSDS) wireless devices) and multi-SIM multi-activity (MSMA) wireless devices (such as dual-SIM dual-activity (DSDA) wireless devices). An MSMS wireless device can be a wireless device configured with more than one SIM and allowing simultaneous idle mode operation on two subscriptions, and selective communication on one subscription while simultaneously performing idle mode operation on at least one other subscription. An MSMA wireless device can be a wireless device configured with more than one SIM and allowing simultaneous idle mode and / or active mode operation on two subscriptions using at least two different radio frequency (RF) resources (e.g., two different wireless transceivers).

[0033] The term "server" is used herein to describe the various embodiments to refer to any computing device capable of being used as a server, such as a primary exchange server, web server, mail server, document server, content server, or any other type of server. A server can be a dedicated computing device or a computing device that includes a server module (e.g., running an application that could cause the computing device to operate as a server). A server module (e.g., a server application) can be a full-featured server module or a lightweight or auxiliary server module configured to provide synchronization services between dynamic databases on the receiving device (e.g., a lightweight or auxiliary server application). A lightweight or auxiliary server can be a simplified version of the functionality of a server type, implemented on the receiving device, thereby enabling it to act as an internet server (e.g., an enterprise email server) only to the extent necessary to provide the functionality described herein.

[0034] As used herein, the terms “network,” “system,” “wireless network,” “cellular network,” and “wireless communication network” can interchangeably refer to part or all of a wireless network associated with wireless devices and / or custom-designed carriers on those devices. The techniques described herein can be used in a variety of wireless communication networks, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), FDMA, Orthogonal FDMA (OFDMA), Single Carrier FDMA (SC-FDMA), and others. Generally, any number of wireless networks can be deployed in a given geographic area. Each wireless network can support at least one radio access technology, which can operate on one or more frequencies or frequency ranges. For example, a CDMA network can implement Universal Terrestrial Radio Access (UTRA) (including the Wideband Code Division Multiple Access (WCDMA) standard), CDMA2000 (including the IS-2000, IS-95, and / or IS-856 standards), etc. In another example, a TDMA network can implement GSM Enhanced Data Rate (EDGE) for GSM evolution. In another example, OFDMA networks can implement Evolved UTRA (E-UTRA) (including the LTE standard), IEEE 802.11 (WiFi), IEEE 802.16 (WiMAX), IEEE 802.20, and Flash. Etc. Reference may be made to wireless networks using the LTE standard, and therefore the terms “Evolved Universal Terrestrial Radio Access,” “E-UTRAN,” and “eNodeB” may also be used interchangeably herein to refer to wireless networks. However, such references are provided as examples only and are not intended to exclude wireless networks using other communication standards. For example, while various third-generation (3G), fourth-generation (4G), and fifth-generation (5G) systems are discussed herein, these systems are cited only as examples and may be replaced by future generations of systems (e.g., sixth-generation (6G) or higher).

[0035] The terms “network operator,” “operator,” “mobile network operator,” “carrier,” and “service provider” are used interchangeably herein to describe a wireless communication service provider that owns or controls the elements that sell and deliver communication services to end users and provides the necessary supplies and credentials as a strategy implemented in user equipment customization.

[0036] As used herein, the term "RF resource" refers to the components in a communication device that transmit, receive, and decode radio frequency signals. RF resources typically include multiple components coupled together to transmit RF signals (referred to as a "transmit chain") and multiple components coupled together to receive and process RF signals (referred to as a "receive chain").

[0037] LTE is a mobile network standard for 4G wireless communication developed by 3GPP (3rd Generation Partnership Project) and specified in its Release 8 document series for high-speed data transmission. 5G systems (5GS) are a technology that improves upon 4G LTE and provides a new radio access technology (RAT) through the evolution of existing mobile communication network architectures. Current implementations referring to 5GS networks provide new radio (NR) (also known as 5G) support via NR base stations (such as next-generation NodeBs (gNodeBs or gNBs)). 5G systems and NR base stations offer flexibility in bandwidth scheduling and utilization. Future generations of systems (e.g., sixth-generation (6G) or higher systems) may offer the same or similar flexibility in bandwidth scheduling and utilization.

[0038] In LTE and / or 5G (or later) systems, network devices (such as base stations) can broadcast packets to radio devices in a cell. For ease of reference, the term "network device" or "network computing device" is used to refer to any of a variety of network elements that can perform the operations of the various embodiments, and non-limiting examples include base stations, eNodeBs, gNodeBs, application function (AF) servers, operations, administration and maintenance (OAM) servers, application servers, etc.

[0039] 5G media streaming (also known as 5GMS) is designed to enable specific third-party services or applications (such as uplink (UL) and / or downlink (DL) video streaming services) to be distributed using the 5GS network to fully leverage 5G features. For example, the 5GMS architecture allows application providers (APs) (e.g., service or application providers) to provision services to wireless devices (e.g., user equipment (UE)) via the M1 interface. Provisioning may include various parameters defined by the AP and / or the network, such as content hosting, Quality of Service (QoS) templates, consumption and Quality of Experience (QoE) reports, and billing policies. The network can collect and store data (e.g., metrics, measurements, status, statistics, other information, etc.) reported by wireless devices consuming services or applications. Wireless devices can send reports to the network including data (e.g., metrics, measurements, status, other information, etc.), and the network can generate logs reflecting the reported data (e.g., metrics, measurements, status, statistics, other information, etc.). As an example, a network can collect and store data such as bytes consumed by wireless devices, transmission rates reached during a session, cache hits, cache misses, QoS profile activation, guaranteed bit rate, session activation time, session deactivation time, location information, and QoE information. An access point (AP) (e.g., a service or application provider) can receive the collected data about the service (e.g., metrics, measurements, status, statistics, and other information), such as metrics associated with ongoing and past sessions. The network can share the collected data (e.g., metrics, measurements, status, statistics, and other information) among network entities (e.g., using Network Data Analysis Functions (NWDAF)). For example, the network can send log reports that include the collected data (e.g., metrics, measurements, status, statistics, and other information) to network entities (such as NWDAF).

[0040] Although there are 3GPP specifications (specifically, those related to the collection and reporting of data (e.g., metrics, measurements, status, statistics, other information, etc.) to support 5GS network implementation), the 3GPP specifications currently lack an appropriate framework to determine the access levels to the collected data (e.g., metrics, measurements, status, statistics, other information, etc.).

[0041] Currently, there is no defined level of access that different network functions can have to the information collected. For example, there is currently no mechanism for APs (e.g., service or application providers) to restrict or control the data that other entities can request related to the provisioning of services or applications through the 5GS network. As a concrete example, there is currently no mechanism to define that NWDAF should only be able to access the average rebuffered events per hour (not per UE / session statistics) across all sessions. Furthermore, the 3GPP specifications currently lack an appropriate framework for defining privacy. Application providers (APs) want to protect the privacy of their users, and APs do not want to reveal service-specific details, but there is currently no mechanism to establish such privacy controls for the collected data (e.g., metrics, measurements, status, statistics, other information, etc.).

[0042] Various embodiments include methods and apparatus for Media Application Function (AF) open functionality. Various embodiments include methods for controlling access to logs associated with a service or application executed by a processor of an Application Function (AF) server of a fifth-generation (5G) system (5GS). In various embodiments, the AF server may be configured to define a set of event types and corresponding parameters that can be logged and / or reported for a session of a service or application. In various embodiments, one or more open levels (or access levels) may be associated with event types and parameters. In various embodiments, the processor of an Application Provider (AP) server may define a set of aggregation rules for each event type and its corresponding parameters at each of the one or more open levels. The AP server may indicate the event types and parameters, one or more open levels, and aggregation rules to the AF server. In various embodiments, for each event type and parameter and for each of the defined levels, one or more aggregation functions, aggregation periods, and / or aggregation groups may be defined. As an example, aggregation dimensions may include user, session, and / or time. Various embodiments may provide a method for protecting user and service privacy by allowing differentiated access to data and statistics logged by services and applications. The various embodiments may be compatible with the AF open framework and / or with the 5GMS architecture. The various embodiments may enable the generation of parameter lists and instructions on how parameters are aggregated.

[0043] NWDAF enables data collection and measurement openness within 5GS networks. NWDAF can be a core network (CN) function used for data collection, data analysis, and data openness. NWDAF can receive data collected by various network functions (NFs) of the 5G core network (5GCN), such as Application Functions (AF), Access and Mobility Functions (AMF), Session Management Functions (SMF), Policy Control Functions (PCF), User Data Repository (UDR), Network Openness Functions (NEF), Operation, Management and Maintenance (OAM), etc. NWDAF supports data openness by providing on-demand analytics to NFs. The interface between NWDAF and AF can be a direct interface or through the Network Openness Function (NEF).

[0044] NWDAF or other entities can request input data from the AF for data analysis, which can trigger the AF to collect and / or report data (e.g., metrics, measurements, status, statistics, other information, etc.) from the wireless device. The AF can provide a standardized interface to expose events related to applications or services. For example, the “Naf_EventExposure_Subscribe / Unsubscribe / Notify” operation can implement a subscription / notification framework. The exposed events can include specified event types and one or more parameters associated with those event types. Example event types include: “SVC_EXPERIENCE” for service data of the application; “UE_MOBILITY” for user equipment (UE) mobility information; “UE_COMM” for UE communication information; and “EXCEPTIONS” for exception information. Three types of event notification methods can exist: periodic, one-off, and event-based detection. Entities such as NWDAF, AP, etc., can subscribe to events exposed to the AF, and the AF can respond to subscriptions using a list of supported event types and parameters. After subscribing to an AF, entities such as NWDAF, AP, etc., can request periodic notifications (or reports) associated with one or more available events, on-demand (e.g., one-time) notifications (or reports) associated with one or more available events, and / or automatic (e.g., per event detection / occurrence) notifications (or reports) from the AF. The AF can provide the requested data (e.g., metrics, measurements, status, statistics, other information, etc.) to entities such as NWDAF, AP, etc., in the form of log reports, which include data (e.g., metrics, measurements, status, statistics, other information, etc.).

[0045] Various embodiments enable the AP server to control the customization of logs for data (e.g., metrics, measurements, status, statistics, other information, etc.) collected by the AF server for a service or application. The AP server can generate access configuration messages for the service or application, including indications for one or more event types and parameters, one or more open levels, and one or more aggregation rules. The access configuration message can indicate the event types and / or parameters regarding the AP server authorizing the AF to allow entities to customize logs for receiving data (e.g., metrics, measurements, status, statistics, other information, etc.) collected by the service or application.

[0046] An open level (or access level) can be a different tiered access level that the AP server is granting to other entities. Multiple different open levels (or access levels) can be associated with event types and / or parameters. For example, 1, 2, 3, 4, or more open levels (or access levels) can be indicated. Each access level (or open level) can be associated with one or more aggregation rules applicable to that access level (or open level).

[0047] Aggregation rules define the granularity level at which data (e.g., metrics, measurements, status, statistics, other information, etc.) is provided to entities associated with a specific openness level (or access level). Specifically, aggregation rules define the granularity level of logs containing data (e.g., metrics, measurements, status, statistics, other information, etc.) that can be provided to entities associated with a specific openness level (or access level). By configuring aggregation rules, the AP server can configure the log composition of data collection settings for specific data (e.g., metrics, measurements, status, statistics, other information, etc.) for other entities and / or data received by other entities based on the openness (or access) level assigned to that other entity. Aggregation rules can define user aggregation (or anonymization) processes that must be applied before data (e.g., metrics, measurements, status, statistics, other information, etc.) can be reported, such as none, user data averaging, user data summing, etc. Aggregation rules can define time aggregation (or anonymization) processes that must be applied before data (e.g., metrics, measurements, status, statistics, other information, etc.) can be reported, such as none, time period averaging, time period summing, etc. Aggregation rules can define session aggregation (or anonymization) processes that must be applied before data (e.g., metrics, measurements, status, statistics, other information) can be reported, such as none, session averaging, session summation, etc. Aggregation rules can define that all user data for each user can be available, or they can define that user data needs to be grouped to further restrict (or anonymize) before reporting to other entities, such as by limiting reporting to a time period, to users in a specific location, to user groups, by content identifiers (IDs), by subscription types, etc.

[0048] In various embodiments, while the AP can provide full access to the user data of users consuming the service, the AP can restrict other entities, such as NWDAF, to an access level assigned only by the AP, and thus restrict the data available to other entities. For example, an AP providing a movie streaming subscription service (e.g., An AP (e.g., an API) may not want to share information with the NWDAF about users and / or about specific content that a particular subscriber is watching at a given time, and the AP can set an openness level (or access level) for the NWDAF and aggregation rules for that openness level so that the NWDAF cannot receive collected information identifying specific content that a particular user is watching at a given time. Furthermore, the AP may only want to share information based on subscription service or subscription type (or level) (rather than per-user). For example, the AP can set subscription types (such as "Premium," "Basic," "Free," "Trial," etc.) for aggregation groups to differentiate users based on subscription type or level. As another example, the AP can set specific subscription services (e.g., ...) for aggregation groups. (etc.) to differentiate between users who pay and those who access specific customized streaming services. In this way, AP can enable NWDAF to collect information about specific types of subscribers (e.g., "trials") and / or customized services (e.g., ...). Information such as (e.g., premium pricing) can be collected, while limiting the collection of information for other subscription types (e.g., "premium pricing") and / or other customized services. Similarly, some applications may be or include subscription features, in which case the AP may enable the NWDAG to collect information about subscribers of specific application types.

[0049] As an example implementation of various embodiments, the event type can be QoE, and the parameter can be rebuffering (also simply referred to as a rebuffered event). Three access levels can be defined for the rebuffered event parameter: Access Level 1, Access Level 2, and Access Level 3. Access Level 1 can be associated with rules that do not aggregate over time or user. The caller can access all events from all users (when they occur). For users with "NONE" per session, the indication can be "NONE," meaning that aggregation over time or user is not required, and each user and each user's events (when they occur) can be reported individually. Access Level 1 can also have all permissions / features at a lower level. Access Level 2 can have an aggregation function NONE for users (i.e., individually for each user) and a COUNT per session. Access Level 2 can also have all permissions / features at a lower level. Access Level 3 can have an aggregation function AVERAGE over all users and an AVERAGE per session over the COUNT per session hour. In this way, different access levels can be used to generate different logs of the collected data (e.g., metrics, measurements, status, statistics, other information, etc.).

[0050] In various embodiments, an event type may be associated with one or more parameters. In some embodiments, parameters may include content hosting event type parameters, Quality of Service (QoS) / Accounting and Network Ancillary event type parameters, Consumption event type parameters, and / or Quality of Experience (QoE) event type parameters. As an example, a content hosting event type may include parameters such as: downlink bytes; start bytes; transfer rate; cache hit; cache miss; request; success response; and / or error response. As an example, a QoS / Accounting and Network Ancillary event type may include parameters such as: QoS profile activation; QoS profile deactivation; maximum bit rate downlink / uplink; guaranteed bit rate downlink / uplink; guaranteed packet loss rate (PLR) downlink / uplink; guaranteed latency; and / or sponsor identifier (Id). As an example, a consumption event type may include parameters such as: session activation; session termination; location; entry point Uniform Resource Locator (URL) or session or content identifier. As an example, a QoE event type may include parameters: a QoE metric defined by the application provider; an aggregation of requests performed by the AF; and / or an extensible pattern for QoE parameters with associated aggregation functions.

[0051] In some embodiments, the event type and / or parameters associated with the event type may be associated with the following: periodically reported wireless device data (e.g., data reported every 5 seconds, etc.), on-demand reported wireless device data (e.g., data reported in response to a reporting request), and / or event-based wireless device data (e.g., data reported when an event occurs (such as session start, stop, etc.).

[0052] In some embodiments, aggregate functions may be provided as an index table. In some embodiments, aggregate functions may include the COUNT function, AVERAGE function, MEDIAN function, MINIMUM function, MAXIMUM function, and / or SUM function.

[0053] While this document discusses various examples based on event types and associated parameters, event types and parameters are merely one example of how they can define patterns in data (e.g., metrics, measurements, status, statistics, other information, etc.) collection operations, serving to illustrate various embodiments. An event type or parameter itself may be associated with an openness level (or access level), and in various embodiments, such a single event type or parameter may be substituted. Furthermore, although various levels of user data are discussed herein, the level of user identification and / or anonymization may differ across different networks, for example, based on local laws or policies in which the network may be situated. Accordingly, full access to user data, as discussed herein, may mean full access to the details of user data authorized by local laws or policies.

[0054] Figure 1 This is a system block diagram illustrating an example communication system 100 suitable for implementing any of the various embodiments. Communication system 100 may be a 5G New Radio (NR) network, or any other suitable network such as a Long Term Evolution (LTE) network.

[0055] Communication system 100 may include a core network 140 and various mobile devices (shown as follows). Figure 1 The communication system 100 is a heterogeneous network architecture for wireless devices 120a-120e. It may also include multiple base stations (shown as BS110a, BS110b, BS110c, and BS110d) and other network entities. A base station is an entity that communicates with wireless devices (mobile devices) and may also be referred to as a Node B, Node B, LTE Evolved Node B (eNB), Access Point (AP), Radio Headend, Transmit / Receive Point (TRP), New Radio Base Station (NR BS), 5G Node B (NB), Next Generation Node B (gNB), etc. Each base station can provide communication coverage for a specific geographic area. In 3GPP, depending on the context in which the terminology is used, the term "cell" can refer to the coverage area of ​​a base station, a base station subsystem serving that coverage area, or a combination thereof.

[0056] Base stations 110a-110d can provide communication coverage for macrocells, picocells, femtocells, another type of cell, or combinations thereof. Macrocells can cover a relatively large geographic area (e.g., a radius of several kilometers) and allow unrestricted access by mobile devices with service subscriptions. Picocells can cover a relatively small geographic area and allow unrestricted access by mobile devices with service subscriptions. Femtocells can cover a relatively small geographic area (e.g., a residential area) and allow restricted access by mobile devices associated with the femtocell (e.g., mobile devices in a closed user group (CSG)). A base station used for macrocells can be called a macro BS. A base station used for picocells can be called a pico BS. A base station used for femtocells can be called a femtocell BS or a home BS. Figure 1 In the example shown, base station 110a can be a macro BS for macro cell 102a, base station 110b can be a pico BS for pico cell 102b, and base station 110c can be a femto BS for femto cell 102c. Base stations 110a-110d can support one or more (e.g., three) cells. The terms “eNB,” “base station,” “NR BS,” “gNB,” “TRP,” “AP,” “Node B,” “5G NB,” and “cell” can be used interchangeably herein.

[0057] In some examples, the cell may not be stationary, and the geographical area of ​​the cell may move depending on the location of the mobile base station. In some examples, base stations 110a-110d may interconnect with each other via various types of backhaul interfaces (such as direct physical connections, virtual networks, or combinations thereof) using any suitable transport network, and interconnect with one or more other base stations or network nodes (not shown) in the communication system 100.

[0058] Base stations 110a-110d can communicate with the core network 140 via a wired communication link or a wireless communication link 126. Wireless devices 120a-120e can communicate with base stations 110a-110d via a wireless communication link 122.

[0059] The wired communication link 126 can use various wired networks (e.g., Ethernet, TV cable, telephone, fiber optic, and other forms of physical network connections), which can use one or more wired communication protocols, such as Ethernet, point-to-point protocol, advanced data link control (HDLC), improved data communication control protocol (ADCCP), and transmission control protocol / Internet protocol (TCP / IP).

[0060] The communication system 100 may also include a relay station (e.g., relay BS110d). A relay station is an entity that can receive data transmissions from an upstream station (e.g., a base station or mobile device) and transmit data to a downstream station (e.g., a wireless device or base station). A relay station may also be a mobile device capable of relaying transmissions to other wireless devices. Figure 1 In the example shown, relay station 110d can communicate with macro base station 110a and wireless device 120d to facilitate communication between base station 110a and wireless device 120d. A relay station can also be referred to as a relay base station, relay base station, repeater, etc.

[0061] The communication system 100 can be a heterogeneous network comprising different types of base stations (e.g., macro base stations, pico base stations, femto base stations, relay base stations, etc.). These different types of base stations can have different transmit power levels, different coverage areas, and different effects on interference in the communication system 100. For example, macro base stations can have high transmit power levels (e.g., 5 watts to 40 watts), while pico base stations, femto base stations, and relay base stations can have low transmit power levels (e.g., 0.1 watts to 2 watts).

[0062] Network controller 130 can be coupled to a collection of base stations and can provide coordination and control for these base stations. Network controller 130 can communicate with the base stations via backhaul. Base stations can also communicate with each other directly or indirectly, for example, via wireless or wired backhaul.

[0063] Wireless devices 120a, 120b, and 120c can be distributed throughout the communication system 100, and each wireless device can be stationary or mobile. Wireless devices can also be referred to as access terminals, terminals, mobile stations, user units, stations, etc.

[0064] Macro base station 110a can communicate with communication network 140 on wired or wireless communication link 126. Wireless devices 120a, 120b, and 120c can communicate with base stations 110a-110d on wireless communication link 122. Core network 140 can connect to other devices, such as application provider (AP) server 141. In this way, via the connection to core network 140, AP server 141 can make services or applications such as 5GMS services or applications (e.g., from core network 140 via link 126 and from base stations 110a-110d via link 122) available to wireless devices 120a-e.

[0065] Wireless communication links 122 and 124 may include multiple carrier signals, frequencies, or frequency bands, each of which may include multiple logical channels. Wireless communication links 122 and 124 may utilize one or more radio access technologies (RATs). Examples of RATs that can be used in wireless communication links include 3GPP LTE, 3G, 4G, 5G (e.g., NR), GSM, Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Global System for Microwave Access Interoperability (WiMAX), Time Division Multiple Access (TDMA), and other mobile phone communication technology cellular RATs. Further examples of RATs that can be used in one or more of the various wireless communication links 122 and 124 within the communication system 100 include medium-range protocols such as Wi-Fi, LTE-U, LTE-Direct, LAA, and MuLTEfire, and relatively short-range RATs such as Wi-Fi, Bluetooth, and Bluetooth Low Energy (LE).

[0066] Some wireless networks (e.g., LTE) utilize Orthogonal Frequency Division Multiplexing (OFDM) on the downlink and Single-Carrier Frequency Division Multiplexing (SC-FDM) on the uplink. OFDM and SC-FDM divide the system bandwidth into multiple (K) orthogonal subcarriers, which are also commonly referred to as tones, frequency bands, etc. Each subcarrier can be modulated using data. Generally, modulation symbols are transmitted in the frequency domain using OFDM and in the time domain using SC-FDM. The spacing between adjacent subcarriers can be fixed, and the total number of subcarriers (K) can depend on the system bandwidth. For example, the subcarrier spacing can be 15 kHz, and the minimum resource allocation (called a "resource block") can be 12 subcarriers (or 180 kHz). Therefore, for system bandwidths of 1.25 MHz, 2.5 MHz, 5 MHz, 10 MHz, or 20 MHz, the nominal Fast File Transfer (FFT) size can be 128, 256, 512, 1024, or 2048, respectively. The system bandwidth can also be divided into subbands. For example, a subband can cover 1.08 MHz (i.e., 6 resource blocks), and for system bandwidths of 1.25 MHz, 2.5 MHz, 5 MHz, 10 MHz, or 20 MHz, there can be 1, 2, 4, 8, or 16 subbands, respectively.

[0067] While the description of some embodiments may use terminology and examples associated with LTE technology, various embodiments may be applicable to other wireless communication systems, such as New Radio (NR) or 5G networks. NR can utilize OFDM with CP on both the uplink (UL) and downlink (DL), and include support for half-duplex operation using Time Division Multiplexing (TDD). A single component carrier bandwidth of 100 MHz can be supported. An NR resource block can span 12 subcarriers with a subcarrier bandwidth of 75 kHz over a duration of 0.1 milliseconds (ms). Each radio frame may contain 50 subframes of 10 ms each. Therefore, each subframe can have a length of 0.2 ms. Each subframe can indicate the link direction for data transmission (i.e., DL or UL), and the link direction of each subframe can be dynamically switched. Each subframe may include DL / UL data and DL / UL control data. Beamforming can be supported, and beam direction can be dynamically configured. Multiple-input multiple-output (MIMO) transmission with precoding can also be supported. MIMO configurations in DL can support up to 8 transmit antennas, up to 8 multi-layer DL transmissions, and up to two streams per radio device. Multi-layer transmissions with up to 2 streams per radio device are also supported. Aggregation of multiple cells from up to eight serving cells can be supported. Alternatively, NR can support a different air interface than an OFDM-based air interface.

[0068] Some mobile devices can be considered machine-type communication (MTC) mobile devices or evolved or enhanced machine-type communication (eMTC) mobile devices. MTC and eMTC mobile devices include, for example, robots, drones, remote devices, sensors, meters, monitors, location tags, etc., which can communicate with base stations, another device (e.g., a remote device), or other entities. For example, a wireless node can provide or supply connectivity to a network (e.g., a wide area network such as the Internet or cellular networks) via wired or wireless communication links. Some mobile devices can be considered Internet of Things (IoT) devices, or can be implemented as NB-IoT (Narrowband Internet of Things) devices. Wireless devices 120a-e can be contained within a housing that houses the components of the wireless device (e.g., processor components, memory components, similar components, or combinations thereof).

[0069] Generally, any number of communication systems and wireless networks can be deployed in a given geographical area. Each communication system and wireless network can support a specific Radio Access Technology (RAT) and can operate on one or more frequencies. A RAT can also be referred to as a radio technology, air interface, etc. A frequency can also be referred to as a carrier, frequency channel, etc. Each frequency can support a single RAT in a given geographical area to avoid interference between communication systems using different RATs. In some cases, NR or 5G RAT networks can be deployed.

[0070] In some implementations, (e.g., without using base station 110 as an intermediary for communication) two or more mobile devices 120a-e (e.g., shown as wireless device 120a and wireless device 120e) can communicate directly using one or more sidelink channels 124. For example, wireless devices 120a-e can communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or similar protocols), mesh networks, or similar networks, or combinations thereof. In this case, wireless devices 120a-e can perform scheduling operations, resource selection operations, and other operations described elsewhere herein as being performed by base station 110a.

[0071] Figure 2 This is a component block diagram illustrating an example computing and wireless modem system 200 suitable for implementing any of the various embodiments. The various embodiments may be implemented on a number of single-processor and microprocessor computer systems (including system-on-chip (SOC) or system-in-package (SIP)).

[0072] Reference Figure 1 and Figure 2 The illustrated example wireless device 200 (which may be a SIP in some embodiments) includes two SOCs 202, 204 coupled to a clock 206, a voltage regulator 208, at least one SIM 268 and / or SIM interface, and a wireless transceiver 266 configured to transmit and receive wireless communications from a network wireless device (e.g., base station 110a) via an antenna (not shown). In some embodiments, the first SOC 202 operates as a central processing unit (CPU) in a wireless device that implements instructions for a software application by executing arithmetic, logic, control, and input / output (I / O) operations specified by instructions. In some embodiments, the second SOC 204 may operate as a dedicated processing unit. For example, the second SOC 204 may operate as a dedicated 5G processing unit responsible for managing high-capacity, high-speed (e.g., 5Gbps) and / or very high frequency short wavelength length (e.g., 28GHz millimeter wave spectrum) communications.

[0073] The first SOC 202 may include a digital signal processor (DSP) 210, a modem processor 212, a graphics processor 214, an application processor (AP) 216, one or more coprocessors 218 (e.g., vector coprocessors) connected to one or more processors in the processor, memory 220, custom circuitry 222, system components and resources 224, an interconnect / bus module 226, one or more temperature sensors 230, a thermal management unit 232, and a thermal power encapsulation (TPE) assembly 234. The second SOC 204 may include a 5G modem processor 252, a power management unit 254, an interconnect / bus module 264, multiple millimeter-wave (mmWave) transceivers 256, memory 258, and various additional processors 260, such as application processors, packet processors, etc.

[0074] Each processor 210, 212, 214, 216, 218, 252, 260 may include one or more cores, and each processor / core may perform operations independent of other processors / cores. For example, the first SOC 202 may include a processor running a first type of operating system (e.g., FreeBSD, LINUX, OS X, etc.) and a processor running a second type of operating system (e.g., MICROSOFT WINDOWS 10). Furthermore, any or all of the processors 210, 212, 214, 216, 218, 252, 260 may be included as part of a processor cluster architecture (e.g., synchronous processor cluster architecture, asynchronous or heterogeneous processor cluster architecture, etc.).

[0075] The first SOC 202 and the second SOC 204 may include various system components, resources, and custom circuitry for managing sensor data, analog-to-digital conversion, wireless data transmission, and performing other specialized operations, such as decoding and processing data packets for encoded audio and video signals to be presented in a web browser. For example, the system components and resources 224 of the first SOC 202 may include power amplifiers, voltage regulators, oscillators, phase-locked loops, peripheral bridges, data controllers, memory controllers, system controllers, access ports, timers, and other similar components for supporting processors and software clients running on wireless devices. The system components and resources 224 and / or custom circuitry 222 may also include circuitry for connecting to peripheral devices, such as cameras, electronic displays, wireless communication devices, external memory chips, etc.

[0076] The first SOC 202 and the second SOC 204 can communicate via interconnect / bus module 250. Various processors 210, 212, 214, 216, and 218 can be interconnected via interconnect / bus module 226 to one or more memory elements 220, system components and resources 224, as well as custom circuitry 222 and thermal management unit 232. Similarly, processor 252 can be interconnected via interconnect / bus module 264 to power management unit 254, millimeter-wave transceiver 256, memory 258, and various additional processors 260. Interconnect / bus modules 226, 250, and 264 can include arrays of reconfigurable logic gates and / or implement bus architectures (e.g., CoreConnect, AMBA, etc.). Communication can be provided via improved interconnects (e.g., high-performance on-chip networks (NoC)).

[0077] The first SOC 202 and / or the second SOC 204 may further include input / output modules (not shown) for communicating with resources outside the SOC, such as clock 206, voltage regulator 208, one or more wireless transceivers 266, and at least one SIM 268 and / or SIM interface (i.e., an interface for receiving one or more SIM cards)). Resources outside the SOC (e.g., clock 206, voltage regulator 208) may be shared by two or more internal SOC processors / cores. The at least one SIM 268 (or one or more SIM cards coupled to one or more SIM interfaces) may store information supporting multiple customizations, including a first 5G NR customization and a second 5G NR customization, etc.

[0078] In addition to the example SIP 200 discussed above, various embodiments can be implemented in a wide variety of computing systems, which may include a single processor, multiple processors, multi-core processors, or any combination thereof.

[0079] Figure 3 This is a component block diagram illustrating a software architecture 300, which includes a wireless protocol stack for the user plane and control plane in wireless communication suitable for implementing any of the various embodiments. (Refer to...) Figures 1-3 Wireless device 120 can implement software architecture 300 to facilitate communication between wireless device 120 (e.g., wireless devices 120a-120e, 200) and base station 350 (e.g., base station 110a) in a communication system (e.g., 100). In various embodiments, layers in software architecture 300 can form logical connections with corresponding layers in the software of base station 350. Software architecture 300 can be distributed across one or more processors (e.g., processors 212, 214, 216, 218, 252, 260). Although shown relative to a single wireless protocol stack, in a multi-SIM (Subscriber Identity Module) wireless device, software architecture 300 can include multiple protocol stacks, each of which can be associated with different SIMs (e.g., two protocol stacks associated with two SIMs respectively in a dual-SIM wireless communication device). Although described below with reference to the LTE communication layer, software architecture 300 can support any of a variety of standards and protocols for wireless communication, and / or can include additional protocol stacks supporting any of a variety of standard and protocol wireless communication.

[0080] Software architecture 300 may include a Non-Access Stratum (NAS) 302 and an Access Stratum (AS) 304. NAS 302 may include functions and protocols for supporting packet filtering, security management, mobility control, session management, and services and signaling between a radio device's SIM (e.g., SIM 204) and its core network 140. AS 304 may include functions and protocols for supporting communication between the SIM (e.g., SIM 204) and entities of the supported access network (e.g., base stations). In particular, AS 304 may include at least three layers (Layer 1, Layer 2, and Layer 3), each of which may contain various sublayers.

[0081] In the user plane and control plane, Layer 1 (L1) of AS 304 can be Physical Layer (PHY) 306, which can supervise the implementation of transmission and / or reception functions via the air interface. Examples of such Physical Layer 306 functions may include Cyclic Redundancy Check (CRC) attachment, block decoding, scrambling and descrambling, modulation and demodulation, signal measurement, MIMO, etc. The Physical Layer may include various logical channels, including the Physical Downlink Control Channel (PDCCH) and the Physical Downlink Shared Channel (PDSCH).

[0082] In the user plane and control plane, Layer 2 (L2) of AS 304 can be responsible for the link between wireless device 120 and base station 350 via physical layer 306. In various embodiments, Layer 2 may include a Media Access Control (MAC) sublayer 308, a Radio Link Control (RLC) sublayer 310, and a Packet Data Convergence Protocol (PDCP) sublayer 312, each of which forms a logical connection that terminates at base station 350.

[0083] In the control plane, Layer 3 (L3) of AS 304 may include a Radio Resource Control (RRC) sublayer 3. Although not shown, software architecture 300 may include additional Layer 3 sublayers and various upper layers above Layer 3. In various embodiments, RRC sublayer 313 may provide functions including broadcasting system information, paging, and establishing and releasing RRC signaling connections between radio device 120 and base station 350.

[0084] In various embodiments, PDCP sublayer 312 can provide uplink functions including multiplexing between different radio bearers and logical channels, sequence numbering, handover data processing, integrity protection, encryption, and header compression. In the downlink, PDCP sublayer 312 can provide functions including in-order delivery of data packets, duplicate data packet detection, integrity verification, decryption, and header decompression.

[0085] In the uplink, RLC sublayer 310 can provide segmentation and concatenation of upper-layer data packets, retransmission of lost data packets, and Automatic Repeat Request (ARQ). However, in the downlink, RLC sublayer 310 functions may include reordering data packets to compensate for out-of-order reception, reassembly of upper-layer data packets, and ARQ.

[0086] In the uplink, MAC sublayer 308 can provide functions including multiplexing between logical and transport channels, random access procedures, logical channel prioritization, and hybrid ARQ (HARQ) operations. In the downlink, MAC layer functions can include intra-cell channel mapping, demultiplexing, discontinuous reception (DRX), and HARQ operations.

[0087] While the software architecture 300 can provide functionality for transmitting data over a physical medium, it may further include at least one host layer 314 to provide data delivery services to various applications within the wireless device 120. In some embodiments, application-specific functionality provided through at least one host layer 314 can provide an interface between the software architecture and the general-purpose processor 206.

[0088] In other embodiments, software architecture 300 may include one or more higher logical layers (e.g., transport, session, presentation, application, etc.) that provide host layer functionality. For example, in some embodiments, software architecture 300 may include a network layer (e.g., IP layer) where logical connections terminate at a packet data network (PDN) gateway (PGW). In some embodiments, software architecture 300 may include an application layer where logical connections terminate at another device (e.g., end-user equipment, server, etc.). In some embodiments, software architecture 300 may further include a hardware interface 316 in AS 304 between physical layer 306 and communication hardware (e.g., one or more radio frequency (RF) transceivers).

[0089] Figure 4A This is an architecture diagram illustrating the interaction and interface between the Application Function (AF) server 402 and the wireless device 120 for 5G Media Streaming (5GMS) according to various embodiments. (Refer to...) Figure 4A , Figure 4AAn example interface for 5GMS service provisioning is shown. For example, the 5GMS architecture allows an Application Provider (AP) server 403 (e.g., AP server 141) to provision services to wireless devices (e.g., User Equipment (UE)) such as wireless device 120 on the M1 interface. AP server 403 interacts with AF server 402 to provision services, and AF server 402 interacts with a media session handler on wireless device 120 to provide services to wireless device 120 and receive data reported from wireless device 120 (e.g., metrics, measurements, status, statistics, other information, etc.), such as data associated with consuming services. Provisioning may include various parameters defined by the AP and / or the network, such as content hosting, QoS templates, consumption and QoE reporting, and billing policies. The network can collect data about the service (e.g., metrics, measurements, status, statistics, other information, etc.) from the wireless device consuming the service. For example, the wireless device consuming the service may send a report to the network that includes data about its consumption of the service (e.g., metrics, measurements, status, statistics, other information, etc.). AP server 403 (e.g., a service or application provider) can receive collected data about the service (e.g., metrics, measurements, status, statistics, other information, etc.), such as data associated with ongoing and past sessions. AF server 402 can share the collected data (e.g., metrics, measurements, status, statistics, other information, etc.) among network entities, for example, by utilizing Network Data Analysis Functions (NWDAF). For instance, AF server 402 can send logs of the collected data (e.g., metrics, measurements, status, statistics, other information, etc.) to network entities (such as NWDAF) via log reports.

[0090] Figure 4B This is an architecture diagram illustrating open interaction (AF) in a 5G system. (Refer to...) Figure 4BThe NWDAF 404 can request some input data for data analysis from the AF server 402, which can trigger the AF 402 to collect data (e.g., metrics, measurements, status, statistics, other information, etc.) from wireless devices (e.g., wireless devices 120, 120a-e, 200). The AF server (such as AF server 402) can provide the AF with a standardized interface for events related to applications or services. For example, the "Naf_EventExposure_Subscribe / Unsubscribe / Notify" operation can implement a subscription / notification framework. Example event types include: "SVC_EXPERIENCE" for service data of an application; "UE_MOBILITY" for UE mobility information; "UE_COMM" for UE communication information; and "EXCEPTIONS" for anomaly information. Three types of event notification methods can exist, including periodic, one-off, and event-based detection. Entities such as NWDAF 404 can subscribe to AF server 402 to receive logs from AF server 402, such as logs of collected data (e.g., metrics, measurements, status, statistics, other information, etc.).

[0091] Figure 4C This is an architecture diagram illustrating the interaction of Network Data Analysis Function (NWDAF) in the 5G core network. (Refer to...) Figure 4C The NWDAF 404 enables open data collection and measurement within a 5GS network. The NWDAF 404 can be a core network (CN) function for data collection, data analysis, and data openness. The NWDAF 404 can receive data collected by various network functions (NFs) of the 5G core network (5GCN), such as application functions (AFs) (e.g., AF server 402), access and mobility functions (AMF), session management functions (SMF), policy control functions (PCF), user data repository (UDR), network openness functions (NEF), operation, management, and maintenance (OAM), etc. The NWDAF 404 supports data openness by providing on-demand analysis to the NFs. The interface between the NWDAF 404 and the AF server 402 can be a direct interface or via the NEF.

[0092] Figure 5A This is a process flowchart of a method 500 for controlling access to logs associated with a service or application, according to various embodiments. (Refer to...) Figure 5AThe operation of method 500 can be implemented by a processor of a network computing device (such as an AP server (e.g., AP server 141, 403)). The operation of method 500 can enable the AP server to control access to logs associated with services or applications provided through the 5GS network. As an example, the operation of method 500 can be performed for uplink 5G media streaming services and / or downlink 5G media streaming services.

[0093] In block 502, the processor may perform operations including determining one or more event types and parameters to be enabled for information disclosure for a service or application. In various embodiments, the one or more event types may include content hosting event types, Quality of Service (QoS) / charging and network ancillary event types, consumption event types, and / or Quality of Experience (QoE) event types. For example, a content hosting event type may include parameters such as: downlink bytes; start bytes; transmission rate; cache hit; cache miss; request; success response; and / or error response. As an example, a QoS / charging and network ancillary event type may include parameters such as: QoS profile activation; QoS profile deactivation; maximum bit rate downlink / uplink; guaranteed bit rate downlink / uplink; guaranteed packet loss rate (PLR) downlink / uplink; guaranteed latency; and / or sponsor identifier (Id). As an example, a consumption event type may include parameters such as: session activation; session termination; location; entry point Uniform Resource Locator (URL) or session or content identifier. As an example, a QoE event type may include parameters: QoE metrics defined by the application provider; aggregation of requests performed by AF only; and / or extensible patterns for QoE parameters that utilize associated aggregation functions.

[0094] In box 504, the processor may perform operations including determining one or more open levels for a service or application. An open level (or access level) can be a different tiered access level that the AP server is granting to other entities. Multiple different open levels (or access levels) can be associated with event types and / or parameters. For example, 1, 2, 3, 4, or more open levels (or access levels) can be indicated. Each access level (or open level) can be associated with one or more aggregation rules applicable to that access level (or open level).

[0095] In block 506, the processor may perform operations including determining aggregation rules for parameters for each of one or more event types and for each of one or more open levels. In various embodiments, aggregation rules include aggregation functions, aggregation periods, and / or aggregation groups for a service or application. In some embodiments, aggregation functions may include one or more of the following: COUNT function, AVERAGE function, MEDIAN function, MINIMUM function, MAXIMUM function, and / or SUM function. In some embodiments, aggregation periods may include sessions or time periods. In some embodiments, aggregation groups may include individual users, user groups, user locations, content identifiers, subscription types, or all users together. In some embodiments, metric aggregation rules may be determined based on each open level, such that different open levels can be associated with different aggregation rules. In some embodiments, aggregation rules may be based on subscriptions sold to data collected by the AP. For example, different subscription levels can support different aggregation groups, where entities with data-specific subscriptions to the AP can access data about individual users (albeit potentially anonymized), while entities without data-specific subscriptions to the AP can only access averaged or summed data at the user level. In this way, entities with AP subscriptions can have higher or more granular access to aggregation groups compared to entities without AP subscriptions.

[0096] In block 508, the processor may perform operations including: generating an access configuration message for a service or application, the access configuration message including indications for one or more event types and parameters, one or more open levels, and aggregation rules. The access configuration message may associate event types with one or more parameters. The access configuration message may associate the indicated event types and / or parameters with one or more access levels. One or more access levels may each be associated with their respective aggregation rules in the access configuration message. In some embodiments, the access configuration message may include authentication information for the access level, such as a Uniform Resource Locator (URL) for an authentication server.

[0097] In block 510, the processor may perform operations including sending an access configuration message to the Application Function (AF) server. For example, the access configuration message may be sent to the AF server via the M1 interface.

[0098] Figure 5B This is an example pattern of access configuration message 550 according to various embodiments. See reference. Figure 5B Access configuration message 550 can be based on method 500 ( Figure 5AAccess configuration messages generated by operations of [the specified method]. Access configuration message 550 may include indications for one or more event types 552. Access configuration message 550 may include indications for one or more parameters 554. Access configuration message 550 may include indications for one or more access levels 556. Access configuration message 550 may include indications for one or more aggregation rules, such as indications for one or more aggregation functions 558 and one or more aggregation groups 560. Access configuration message 550 may include indications for authorization information 562.

[0099] As a non-limiting example, event type 552 could be a managed event type, and parameter 554 could be "Downlink_bytes". In this way, access configuration message 550 could represent a log of data (e.g., metrics, measurements, status, statistics, other information, etc.) reporting configuration settings from AP servers (e.g., AP servers 141, 403) to AF servers (141, 402), which governs how AF servers (141, 402) will provide the data (e.g., metrics, measurements, status, statistics, other information, etc.) used for service to the requesting entity.

[0100] In this non-restrictive example, access configuration message 550 can define three access levels 556: level "1", level "2", and "default". In this example, aggregation function 558 can be defined as follows: For level "1": aggregation of user information can be not applied ("None") (e.g., for level "1", allowing granularity for a single user), aggregated on the average of all users ("average"), or aggregated as the sum of all users ("sum"); aggregation of time information can be not applied ("None") (e.g., for level "1", allowing granularity for any time period), or aggregated as the sum of all times ("sum"); and aggregation of session information can be not applied ("None") (e.g., for level "1", allowing granularity for a single session), aggregated on the average of sessions ("average"), or aggregated as the sum of all sessions ("sum"). In some implementations, the ability to use different granularity levels (such as "None", "Average", or "Sum") can be controlled through customization between the entity requesting data and the AP server generating the access configuration message. This allows even if the entity is a Level "1" entity, additional customization with the AP server can be requested to enable a single granularity for Level "1", and a Level "1" entity without additional customization can simply receive logs based on "average" or "sum". In this example, aggregation function 558 can be defined as follows: For Level "2": aggregation of user information can be aggregated above the average of all users ("average") or aggregated as the sum of all users ("sum"); aggregation of time information can be not applied ("None") (e.g., for Level "2", granularity about any time period is allowed) or aggregated as the sum of all times ("sum"); and aggregation of session information can be aggregated above the average of sessions ("average") or aggregated as the sum of all sessions ("sum"). In this example, aggregation function 558 can be defined as follows: for the level "default": aggregation of user information can be aggregated above the average of all users ("average") or aggregated as the sum of all users ("sum"); aggregation of time information can be aggregated as the sum of all times ("sum"); and aggregation of session information can be aggregated as the sum of all sessions ("sum").

[0101] In this non-restrictive example, access configuration message 550 can define aggregation groups 560 for each of the three access levels 556 (Level "1", Level "2", and "Default"). For Level "1", any grouping of user / user data can be allowed (e.g., "All"). For Level "2", user / user data groups can be allowed by time period, location, user group, or content ID. For the "Default" level, user / user data groups can be allowed by time period and user group.

[0102] In this non-restrictive example, access configuration message 550 may define authorization information 562 for each of the three access levels 556 (Level "1", Level "2", and "Default"). For Level "1", a URL for the authorization server may be provided. The URL may be the address of a server to which the AF server may redirect subscription and / or reporting requests to authenticate and / or verify the access level (or open level) for an entity. The URL may point to the AP server itself (e.g., AP server 141, 403) or another entity (such as a third-party authentication server). For Level "2", a URL for the authorization server is provided. The URL may be the address of a server to which the AF server may redirect subscription and / or reporting requests to authenticate and / or verify the access level (or open level) for an entity. The URL may point to the AP server itself (e.g., AP server 141, 403) or another entity (such as a third-party authentication server). For Level "Default", no authentication may be required (or performed) ("None").

[0103] Figure 5B Access configuration message 550 is merely an example of a pattern for supporting AF open functionality, and other access configuration message structures and elements may be substituted in various embodiments. In some embodiments, other access configuration messages may include more event types, or may not indicate event types. In some embodiments, other access configuration messages may include multiple parameters, or may not indicate parameters. In some embodiments, other access configuration messages may include more or fewer open levels. In some embodiments, a default open level may not be defined, such that entities without an assigned access level may not receive any data logs for the service. In some embodiments, other access configuration messages may include more or fewer aggregation rules. In some embodiments, other access configuration messages may not include authorization information.

[0104] Figure 6A This is a process flowchart illustrating a method 600 for controlling access to logs associated with a service or application, according to various embodiments. (Refer to...) Figure 6AThe operation of method 600 can be implemented by a processor of a network computing device (such as an AF server (e.g., 402)). As an example, the operation of method 600 can be performed for uplink 5G media streaming services and / or downlink 5G media streaming services. In various embodiments, the operation of method 600 can be combined with method 500 ( Figure 5A The operation is carried out in cooperation with each other.

[0105] In block 602, the processor may perform operations including receiving an access configuration message from a service or application provider, the access configuration message including indications for the following items for the service or application: one or more event types and parameters, one or more open levels, and aggregation rules. In various embodiments, the access configuration message may be received from an AP server (e.g., AP servers 141, 403). For example, the access configuration message may be received via an M1 interface. In some embodiments, the access configuration message may be generated by the AP server according to method 500 (…). Figure 5A The access configuration message generated by the operation. In some embodiments, the access configuration message may be access configuration message 550, as shown in reference... Figure 5B As described.

[0106] In block 604, the processor may perform operations including receiving a subscription request for a service or application log from another computing device. In some embodiments, the subscription request may be a Network Application Function (NAF) event open subscription received from an NWDAF (e.g., NWDAF 404), such as a "Naf_MetricsInfo_Subscribe" request. The service log may be a log of reports or collected data (e.g., metrics, measurements, status, statistics, other information, etc.) received from a wireless device consuming the service or application.

[0107] In block 606, the processor may perform operations including determining the open level of another computing device. In some embodiments, the open level (or access level) may be indicated by the other computing device. For example, the other computing device may indicate the access level in a subscription request. In some embodiments, the open level (or access level) may be indicated by the type of the other computing device. For example, an AP server may be associated with a specific access level (such as level "1"), an NWDAF may be associated with a different specific access level (such as level "2"), and other entities may be associated with a default access level (such as "default").

[0108] In some embodiments, the open level (or access level) may be determined as part of the authentication process for a customized computing device. Authentication can occur in any manner, and as part of the authentication, the open level (or access level) may be assigned to and / or determined by the AF server. In some embodiments, the AF server may redirect the customized entity to an AP server or another authentication server for authentication and receive a token associated with the open level (or access level) assigned to the customized entity. In some embodiments, the customized entity may provide its token to the AF server, and based on that token, the AF server may determine the customized entity's open level (or access level).

[0109] In block 608, the processor may perform operations including: determining event types and parameters for the service or application, and aggregation rules for the event types and parameters, based at least in part on an access configuration message for the service or application and the open level of the other computing device. In some embodiments, the processor may parse the access configuration message to determine all event types and parameters for the service with a customized entity's open level (or access level), and may determine aggregation rules associated with those event types and parameters under the customized entity's open level (or access level).

[0110] In block 610, the processor may perform operations including generating a customized response message for the other computing device, the customized response message indicating event types and parameters for a service or application, and aggregation rules for the event types and parameters. In some embodiments, the customized response message may be a list of all authorized event types and parameters for an open level (or access level) for a customized entity, and aggregation rules to be followed for each of these event types and parameters. In this way, the customized response message may only indicate processing rules and available event types and parameters for the access level assigned to the customized entity.

[0111] In block 611, the processor may perform an operation including sending a customized response message to the other computing device. In some embodiments, the customized response message may be sent in an NAF response (such as "Naf_MetricsProcessingRules_Provision").

[0112] Figure 6B This is a process flowchart of method 612 for controlling access to logs associated with a service or application, according to various embodiments. (Refer to...) Figure 6BThe operation of method 612 can be implemented by a processor of a network computing device (such as an AF server (e.g., 402)). As an example, the operation of method 612 can be performed for uplink 5G media streaming services and / or downlink 5G media streaming services. In some embodiments, the operation of method 612 can be combined with method 500 ( Figure 5A ) and / or 600 ( Figure 6A The operation of method 612 can be performed in response to the operation of method 600. As an optional example, the operation of method 612 can be performed in response to the operation of method 600. Figure 6A In box 611, a customized response message is sent to another computing device to perform the operation.

[0113] In block 614, the processor may perform operations including receiving reports on a service or application from one or more wireless devices consuming the service or application. The reports may include data (e.g., metrics, measurements, status, statistics, other information, etc.) associated with the consumption of the service or application by the one or more wireless devices.

[0114] In block 616, the processor may perform an operation including receiving a request for available logs from another computing device. In some embodiments, the other computing device may be an NWDAF server (e.g., NWDAF 404). The available logs may be logs of reports or collected data (e.g., metrics, measurements, status, statistics, other information, etc.) received from one or more wireless devices in relation to consumption of a service or application.

[0115] In block 617, the processor may perform operations including authenticating another computing device in response to receiving a request for available logs from another device. In some embodiments, authenticating the other device may include verifying a token from the other device with a service or application provider. As part of authenticating the other computing device, the AF server may send an authorization request to the AP server (e.g., 141, 403), or may redirect the other computing device to send an authorization request to the AP server.

[0116] In block 618, the processor may perform operations including determining the open level (access level) of another device based on authentication. In some embodiments, authentication may result in indicating the open level (or access level) to the AF server. For example, an authentication message may indicate an assigned open (or access) level. As another example, failure to authenticate another computing device may indicate that the other computing device will be considered to have a default open (or access) level.

[0117] In box 620, the processor may perform operations including generating a log report based on reported data for a service or application (e.g., metrics, measurements, status, statistics, other information, etc.) and an openness level for the service or application associated with an access level determined for another computing device. For example, the log report may include one or more logs of data (e.g., metrics, measurements, status, statistics, other information, etc.) collected according to the openness (or access) level of another computing device and corresponding to event types and parameter settings configured by the AP server for that openness (or access) level.

[0118] In box 622, the processor can perform operations including sending a log report to another device.

[0119] Figure 6C This is a process flowchart illustrating method 520 for authorizing access to logs associated with a service or application, according to various embodiments. (Refer to...) Figure 6C The operation of method 520 can be implemented by a processor of a network computing device (such as an AP server (e.g., 141, 403)). As an example, the operation of method 520 can be performed for uplink 5G media streaming services and / or downlink 5G media streaming services. In some embodiments, the operation of method 520 can be combined with method 500 ( Figure 5A ), 600 Figure 6A ) and / or 612 ( Figure 6B The operation of method 520 is performed in response to the operation of method 500. In some embodiments, the operation of method 520 may be performed in response to the operation of method 500. Figure 5A In box 510, an access configuration message is sent to the AF server to perform the operation.

[0120] In block 522, the processor may perform operations including receiving an authorization request associated with another computing device. The authorization request may be from an AF server or another computing device (e.g., NWDAF). The authorization request may identify the other computing device.

[0121] In determination block 524, the processor may perform operations including determining whether another computing device is authorized for access. In some embodiments, the AP server may determine whether the other computing device is associated with a third party that has access to the data (e.g., metrics, measurements, status, statistics, other information, etc.) of the authorized access service, the type of the other computing device, or any other attribute that can distinguish an authorized device from an unauthorized device.

[0122] In response to determining that the device is not authorized (i.e., determining block 530 = "No"), in block 530, the processor may perform an operation including sending an authorization failure indication. The authorization failure indication may indicate the default level at which the device is authorized to access data used for services (e.g., metrics, measurements, status, statistics, other information, etc.), or it may indicate that the device is not authorized to receive any data used for services.

[0123] In response to determining that the device is authorized (i.e., determining block 530 = "Yes"), in block 526, the processor may perform an operation including determining an access level for the other device. In some embodiments, the access level may be based on settings at the AP server, the attributes of the other device, and / or service protocols.

[0124] In block 528, the processor may send an authorization confirmation indicating an open level. In some embodiments, the authorization confirmation may be a message sent to the AF server indicating an open level (or access level) assigned to another computing device. In some embodiments, the authorization confirmation may be a message sent to another computing device, such as a message including a token.

[0125] Figure 7A This is a call flow diagram illustrating the interaction for log delivery between the AF and NWDAF according to various embodiments. (Refer to...) Figure 7A , Figure 7APhase 2 (SA2 task) and Phase 3 (CT1 task) can be shown to specify the Nx reference point corresponding to the Naf service-based interface between the AF (e.g., AF server 402) and NWDAF (e.g., NWDAF 404). In step 1, NWDAF 404 can subscribe to the AF server 402 for receiving information notifications about data (e.g., metrics, measurements, status, statistics, other information, etc.). For example, NWDAF 404 can send a Naf_MetricsInfo_Subscribe message to the AF server 402. In step 2, the AF server 402 can supply the event types and parameters for the open level (access level) of NWDAF 404 according to post-processing rules regarding the data (e.g., metrics, measurements, status, statistics, other information, etc.). For example, the AF server 402 can indicate the available logs based on the open level (or access level) of NWDAF 404. In step 3, AF server 402 may send a notification to NWDAF 404 regarding the availability of newly available data information (e.g., newly available logs). In step 4, NWDAF 404 may send a request to AF server for the delivery of log reports generated based on processing rules according to various embodiments. In step 5, a response of delivery of the requested log reports may be sent from AF server 402 to NWDAF 404 according to the aggregation rules for the open level used by NWDAF 404.

[0126] Figure 7B This is a call flowchart illustrating the interactions used to control access to logs associated with a service or application in a 5G system, according to various embodiments. (Refer to...) Figure 7BThe access authorization process may include the interactions shown between the application provider (e.g., AP server 403), the 5GMS AF (e.g., AF server 402), the NWDAF (e.g., NWDAF 404), the 5GMS Application Service (AS), and the UE (e.g., wireless device 120). AP server 403 may provide AF server 402 with an open level configuration and an authorization URL based on each open level in an access configuration message. Wireless device 120 may report data (e.g., metrics, measurements, status, statistics, other information, etc.) to AF server 402. NWDAF 404 may log data (e.g., metrics, measurements, status, statistics, other information, etc.) to AF server 402. AF server 402 may redirect NWDAF 404 to the authentication URL. NWDAF 404 may authenticate itself to AP server 403 and receive a token from AP server 403. NWDAF 404 can use a token to subscribe to AF server 402, AF server 402 can verify the token with AP server 403, and NWDAF 404 can successfully subscribe during authentication. Although Figure 7B Various authentication operations are shown, but these are merely examples, and other authentication operations (e.g., OAuth 2.0, other authorization protocol operations, etc.) can be substituted. Figure 7B Operations within this framework may not require authentication, such as for lower levels of authorization or the default open level.

[0127] Figure 8 This is a component block diagram of a network computing device 800 suitable for use with various embodiments. Such a network computing device may include at least... Figure 8 The components shown in the image. (Refer to...) Figure 1-8The network computing device 800 (e.g., AF server 402, AP servers 141, 403, NWDAF 404, etc.) may include a processor 801 coupled to volatile memory 802 and mass non-volatile memory (such as disk drive 803). The network computing device 800 may also include peripheral memory access devices, such as floppy disk drives, compact optical disc (CD) or digital video optical disc (DVD) drives 806 coupled to the processor 801. The network computing device 800 may also include a network access port 804 (or interface) coupled to the processor 801 for establishing a data connection to a network (such as the Internet and / or a local area network coupled to other system computers and servers). The network computing device 800 may include one or more antennas 807 for transmitting and receiving electromagnetic radiation that can be connected to a wireless communication link. The network computing device 800 may include additional access ports for coupling to peripheral devices, external memory, or other devices, such as USB, Firewire, Thunderbolt, etc.

[0128] Figure 9 This is a component block diagram of a wireless device 900 suitable for use with various embodiments. (Refer to...) Figure 1-9 The various embodiments can be implemented on various wireless devices 900 (e.g., wireless devices 120, 120a-120e, 200), examples of which are shown in Figure 9 The wireless device 900 is illustrated as a smartphone. It may include a first SOC 202 (e.g., an SOC-CPU) coupled to a second SOC 204 (e.g., a 5G-capable SOC). The first SOC 202 and the second SOC 204 may be coupled to internal memories 906, 916, a display 912, and a speaker 914. Additionally, the wireless device 900 may include an antenna 904 for transmitting and receiving electromagnetic radiation, which may be connected to a wireless data link and / or a cellular transceiver 266 coupled to one or more processors in the first SOC 202 and / or the second SOC 204. The wireless device 900 may also include menu selection buttons or a rocker switch 920 for receiving user input.

[0129] The wireless device 900 may also include a voice encoding / decoding (CODEC) circuitry 910, which digitizes sound received from a microphone into data packets suitable for wireless transmission, and decodes the received voice data packets to generate an analog signal that is provided to a speaker to produce sound. Additionally, one or more processors in the first SOC 202 and the second SOC 204, the wireless transceiver 266, and the CODEC 910 may include digital signal processor (DSP) circuitry (not shown separately).

[0130] The processors of the wireless network computing device 900 and the wireless device 900 can be any programmable microprocessor, microcomputer, or multiprocessor chip, or a chip that can be configured to perform various functions, including those of the various embodiments described below, via software instructions (applications). In some mobile devices, multiple processors may be provided, such as one processor within SOC 204 dedicated to wireless communication functions and another processor within SOC 202 dedicated to running other applications. Software applications may be stored in memories 906 and 916 prior to their access and loading to the processor. The processor may include internal memory sufficient to store application software instructions.

[0131] As used in this application, the terms "component," "module," "system," etc., are intended to include computer-related entities, such as, but not limited to, hardware, firmware, combinations of hardware and software, software, or software in execution, configured to perform specific operations or functions. For example, a component can be, but is not limited to, a process running on a processor, a processor, an object, an executable file, a thread of execution, a program, and / or a computer. By way of illustration, both an application running on a wireless device and the wireless device itself can be referred to as a component. One or more components may reside within a process and / or a thread of execution, and components may reside on a single processor or core and / or be distributed across two or more processors or cores. Furthermore, these components can be executed from various non-transitory computer-readable media having various instructions and / or data structures stored thereon. Components can communicate via local and / or remote processes, function or procedure calls, electronic signals, data packets, memory read / write, and other known network, computer, processor, and / or process-related communication methods.

[0132] Multiple different cellular and mobile communication services and standards are available or anticipated in the future, and all of these services and standards can be implemented and benefit from various embodiments. Such services and standards include, for example, the 3rd Generation Partnership Project (3GPP), Long Term Evolution (LTE) systems, 3rd Generation Wireless (3G), 4th Generation Wireless (4G), 5th Generation Wireless (5G), Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), 3GSM, General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA) systems (e.g., cdmaOne, CDMA1020TM), Enhanced Data Rate GSM Evolution (EDGE), Improved Mobile Phone Systems (AMPS), Digital AMPS (IS-136 / TDMA), Evolved Data Optimized (EV-DO), Digital Enhanced Cordless Telecommunications (DECT), Global Microwave Access Interoperability (WiMAX), Wireless Local Area Networks (WLAN), Wi-Fi Protected Access I&II (WPA, WPA2), and Integrated Digital Enhanced Network (iDEN). For example, each of these technologies relates to the transmission and reception of voice, data, signaling, and / or content messages. It should be understood that any references to terms and / or technical details relating to a single telecommunications standard or technology are for illustrative purposes only and are not intended to limit the scope of the claims to a particular communication system or technology unless expressly stated in the language of the claims.

[0133] The various embodiments shown and described are provided by way of example only to illustrate the various features in the claims. However, the features shown and described with respect to any given embodiment are not necessarily limited to the associated embodiment, and may be used or combined with other embodiments shown and described. Furthermore, the claims are not intended to be limiting by any single exemplary embodiment.

[0134] The foregoing method descriptions and process flowcharts are provided merely as illustrative examples and are not intended to require or imply that the operations of the various embodiments must be performed in the given order. As those skilled in the art will appreciate, the order of operations in the foregoing embodiments can be performed in any order. Words such as “afterward,” “following,” and “next” are not intended to limit the order of operations; these words are used to guide the reader through the description of the method. Furthermore, any reference to an element of the claim in the singular form (e.g., using the articles “a,” “an,” or “the”) should not be construed as limiting that element to the singular.

[0135] The various illustrative logic blocks, modules, components, circuits, and algorithmic operations described in conjunction with the embodiments disclosed herein can be implemented as electronic hardware, computer software, or a combination of both. To clearly illustrate this interchangeability between hardware and software, the various illustrative components, blocks, modules, circuits, and operations have been generally described above regarding their functionality. Whether such functionality is implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system. Those skilled in the art can implement the described functionality in varying ways for each specific application; however, such implementation decisions should not be construed as causing a departure from the scope of the claims.

[0136] Hardware for implementing the various illustrative logics, logic blocks, modules, and circuits described in conjunction with the embodiments disclosed herein can be implemented or executed using a general-purpose processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. The general-purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of receiver intelligent objects, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors cooperating with a DSP core, or any other such configuration. Alternatively, some operations or methods may be performed by circuitry specific to a given function.

[0137] In one or more embodiments, the described functionality may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functionality may be stored as one or more instructions or code on a non-transitory computer-readable storage medium or a non-transitory processor-readable storage medium. The operation of the methods or algorithms disclosed herein may be embodied in a processor-executable software module or processor-executable instructions, which may reside on a non-transitory computer-readable or processor-readable storage medium. A non-transitory computer-readable or processor-readable storage medium may be any storage medium accessible by a computer or processor. By way of example, and not limitation, such a non-transitory computer-readable or processor-readable storage medium may include RAM, ROM, EEPROM, flash memory, CD-ROM or other optical disc storage, disk storage or other magnetic storage smart objects, or any other medium that may be used to store desired program code in the form of instructions or data structures and is accessible by a computer. As used herein, disks and optical discs include compact optical discs (CDs), laser optical discs, optical discs, digital versatile optical discs (DVDs), floppy disks, and Blu-ray discs, wherein disks typically magnetically copy data, while optical discs optically copy data using lasers. The combinations described above are also included within the scope of non-transitory computer-readable and processor-readable media. Additionally, the operation of a method or algorithm may be as one or any combination of code and / or instructions, or code and / or instructions may reside on a non-transitory processor-readable and / or computer-readable storage medium, which may be incorporated into a computer program product.

[0138] The above description of the disclosed embodiments enables any person skilled in the art to implement or use the claims. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein can be applied to other embodiments without departing from the scope of the claims. Therefore, this disclosure is not intended to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the appended claims and the principles and novel features disclosed herein.

Claims

1. A method performed by a processor of a service or application provider server for controlling access to analytics data associated with a service or application provisioned over a Fifth Generation, 5G, System, 5GS, network, comprising: determining one or more event types and parameters for which enablement of exposure of information for a service or application is to be opened; determining one or more exposure levels for the service or application; determining aggregation rules for parameters under each of the one or more exposure levels and for each of the one or more event types, the aggregation rules defining a level of granularity of analytics data provided to an entity associated with a respective exposure level for each respective exposure level; generating an access configuration message for the service or application, the access configuration message including indications of the one or more event types and parameters, the one or more exposure levels, and the aggregation rules; and sending the access configuration message to an application function, AF, server.

2. The method of claim 1, further comprising: receiving an authorization request associated with another computing device; determining whether the other computing device is authorized to access analytics data for the service or application; in response to determining that the other computing device is authorized to access analytics data for the service or application, determining an exposure level for the other computing device; and sending an authorization confirmation indicating the exposure level for the other computing device.

3. The method of claim 2, wherein, the authorization confirmation includes a token for the other computing device, the token indicating the exposure level for the other computing device.

4. The method of claim 2, wherein, the other computing device is a network data analytics function, NWDAF, server.

5. The method of claim 1, wherein, the aggregation rules include an aggregation function, an aggregation period, and an aggregation group for the service or application.

6. The method of claim 5, wherein: the aggregation function includes one or more of a COUNT function, an AVERAGE function, a MEDIAN function, a MINIMUM function, a MAXIMUM function, or a SUM function; the aggregation period includes a session or a time period; and the aggregation group includes individual users, a group of users, a user location, a content identifier, a subscription service, a subscription type, or all users together.

7. The method of claim 1, wherein, the one or more event types include one or more of a content hosting event type, a quality of service, QoS, / charging and network assistance event type, a consumption event type, or a quality of experience, QoE, event type.

8. The method of claim 1, wherein, the service or application is a 5G media streaming, 5GMS, service or application.

9. A method performed by a processor of an application function, AF, server of a Fifth Generation, 5G, System, 5GS, network for controlling access to analytics data associated with a service or application, comprising: receive an access configuration message from a service or application provider, the access configuration message including data representing one or more event types and parameters and aggregation rules for the analytics data, the aggregation rules defining a level of granularity of analytics data provided to an entity associated with each respective level of openness for each respective level of openness; receive a subscription request from a computing device for analytics data for a service or application; determine a level of openness of the computing device; determine the event types and parameters for the service or application and aggregation rules for the event types and parameters based at least in part on the access configuration message and the level of openness of the computing device; generate a subscription response message for the computing device, the subscription response message indicating the event types and parameters for the service or application and the aggregation rules for the event types and parameters; and send the subscription response message to the computing device.

10. The method of claim 9, further comprising: receive reports for the service or application from one or more wireless devices consuming the service or application; receive a request from the computing device for available analytics data; authenticate the computing device in response to receiving the request from the computing device for the available analytics data; determine a level of openness of the computing device based on the authentication; generate a log report from the reports for the service or application from the one or more wireless devices consuming the service or application according to the level of openness for the service or application associated with the determined level of access of the computing device; and send the log report to the computing device.

11. The method of claim 9, wherein, Determining the level of openness of the computing device includes authenticating a token for the computing device indicating the level of openness for the computing device.

12. The method of claim 9, wherein, The computing device is a network data analytics function, NWDAF, server.

13. The method of claim 9, wherein, The aggregation rules include an aggregation function, an aggregation period, or an aggregation group for the service or application.

14. The method of claim 13, wherein: The aggregation function includes one or more of a COUNT function, an AVERAGE function, a MEDIAN function, a MINIMUM function, a MAXIMUM function, or a SUM function; The aggregation period includes a session or a time period; and The aggregation group includes individual users, a group of users, a user location, a content identifier, a subscription service, a subscription type, or all users together.

15. The method of claim 9, wherein, The one or more event types include one or more of a content hosting event type, a quality of service, QoS, / charging and network assistance event type, a consumption event type, or a quality of experience, QoE, event type.

16. The method of claim 9, wherein, The service or application is a 5G media streaming, 5GMS, service or application.

17. A server device for controlling access to analytics data, the server device comprising: a processing system implemented in circuitry and configured to: determine one or more event types and parameters for which enablement of exposure of information for a service or application is to be determined; determine one or more exposure levels for the service or application; determine aggregation rules for parameters in each of the one or more event types and at each of the one or more exposure levels, the aggregation rules defining, for each respective exposure level, a level of granularity of analytics data provided to an entity associated with the respective exposure level; generate an access configuration message for the service or application, the access configuration message including an indication of: the one or more event types and parameters, the one or more exposure levels, and the aggregation rules; and send the access configuration message to an application function, AF, server.

18. The server device of claim 17, wherein, the processing system is further configured to: receive an authorization request associated with another computing device; determine whether the other computing device is authorized to access analytics data for the service or application; determine an exposure level for the other computing device in response to determining that the other computing device is authorized to access the analytics data for the service or application; and send an authorization confirmation indicating the exposure level for the other computing device.

19. The server device of claim 18, wherein, the authorization confirmation includes a token for the other computing device, the token indicating the exposure level for the other computing device.

20. The server device of claim 17, wherein, the aggregation rules include one or more of an aggregation function, an aggregation period, or an aggregation group for the service or application.

21. The server device of claim 20, wherein: the aggregation function includes one or more of: a COUNT function, an AVERAGE function, a MEDIAN function, a MINIMUM function, a MAXIMUM function, or a SUM function; the aggregation period includes a session or a time period; and the aggregation group includes an individual user, a group of users, a user location, a content identifier, a subscription type, or all users together.

22. The server device of claim 17, wherein, the one or more event types include one or more of: a content hosting event type, a quality of service, QoS, / charging and network assistance event type, a consumption event type, or a quality of experience, QoE, event type.

23. The server device of claim 17, wherein, the service or application is a 5G media streaming, 5GMS, service or application.

24. An application function, AF, server of a fifth generation, 5G, system, 5GS, network, comprising: a processing system implemented in circuitry and configured to: receive an access configuration message from a service or application provider, the access configuration message including data representing one or more event types and parameters and aggregation rules for analytics data, the aggregation rules defining, for each respective exposure level, a level of granularity of analytics data provided to an entity associated with the respective exposure level; receive a subscription request from a computing device for analytics data for a service or application; determine an exposure level for the computing device; The event types and parameters for the service or application, as well as the aggregation rules for the event types and parameters, are determined at least in part based on the access configuration message and the openness level of the computing device. Generate a customized response message for the computing device, the customized response message indicating the event type and parameters for the service or application, and the aggregation rules for the event type and parameters; and Send the customized response message to the computing device.

25. The AF server of claim 24, wherein, The processing system is also configured to perform the following operations: Receive reports about the service or application from one or more wireless devices consuming the service or application; Receive a request for available analytical data from the computing device; In response to receiving the request for the available analytics data from the computing device, the computing device is authenticated; The openness level of the computing device is determined based on the certification. Based on the report for the service or application, a log report is generated according to the open level for the service or application associated with the determined access level of the computing device; as well as Send the log report to the computing device.

26. The AF server of claim 24, wherein, The processing system is also configured to determine the openness level of the computing device by authenticating a token for the computing device that indicates the openness level of the computing device.

27. The AF server of claim 24, wherein, The aggregation rules include one of the aggregation functions, aggregation periods, or aggregation groups used for the service or application.

28. The AF server according to claim 27, wherein: The aggregation functions include one or more of the following: COUNT function, AVERAGE function, MEDIAN function, MINIMUM function, MAXIMUM function, or SUM function; The aggregated time period includes sessions or time periods; and The aggregation group includes individual users, user groups, user locations, content identifiers, subscription types, or all users together.

29. The AF server of claim 24, wherein, The one or more event types include one or more of the following: content hosting event type, quality of service (QoS) / billing and network assistance event type, consumption event type, or quality of experience (QoE) event type.

30. The AF server of claim 24, wherein, The service or application mentioned is a 5G media streaming 5GMS service or application.

Images