Apparatus and method for analytics subscriptions in wireless networks

Abstract

Various aspects of this disclosure relate to receiving a message from a first device (802), the message including instructions identifying a service or application and instructions identifying analytics associated with the service or application; sending a request to a second device for a subscription to analytics (804); receiving a response associated with analytics from the second device (806); and sending a response associated with analytics to the first device (808).

Description

Technical Field

[0001] This disclosure relates to wireless communication, and more particularly, to analytics subscriptions in a wireless network.

Background Art

[0002] A wireless communication system may include one or more network communication devices, such as a base station, that can support wireless communication for one or more user communication devices, sometimes known as user equipment (UE) or other suitable terms. The wireless communication system can support wireless communication with one or more user communication devices by utilizing resources of the wireless communication system (e.g., time resources (e.g., symbols, slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers, etc.)). Additionally, the wireless communication system can support wireless communication across various wireless access technologies, including third-generation (3G) wireless access technology, fourth-generation (4G) wireless access technology, fifth-generation (5G) wireless access technology, among others, including suitable wireless access technologies beyond the fifth generation (5G) (e.g., sixth generation (6G)).

Summary of the Invention

Means for Solving the Problems

[0003] The article “a” preceding an element is unrestricted and is understood to refer to “at least one” or “one or more” of those elements. The terms “a,” “at least one,” “one or more,” and “at least one of one or more” may be interchangeable. When used herein, including in the claims, “or” in a list of items (for example, a list of items ending with a phrase such as “at least one of,” “one or more of,” or “one or both of”) indicates an inclusive list, such as a list of at least one of A, B, or C meaning A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Also, the phrase “based on” as used herein should not be interpreted as a reference to a closed set of conditions. For example, an exemplary step described as “based on condition A” may be based on both condition A and condition B without departing from the scope of this disclosure. In other words, the phrase “based on” as used herein should be interpreted similarly to the phrase “at least partially based on.” Furthermore, as used herein, including within the claims, “set” may include one or more elements.

[0004] Some implementations of the methods and apparatus described herein may further include receiving a message from a first device, the message comprising an instruction identifying a service or application and an instruction identifying analytics associated with the service or application; sending a request for a subscription to analytics to a second device; receiving a response associated with analytics from the second device; and sending a response associated with analytics to the first device. [Brief explanation of the drawing]

[0005] [Figure 1] This figure shows an example of a wireless communication system according to the embodiments of this disclosure. [Figure 2] This figure shows an example of the internal functional architecture of Application Data Analytics Enablement (ADAE) according to the aspects of this disclosure. [Figure 3] This figure shows an example of an ADAE procedure according to the aspects of this disclosure. [Figure 4] This figure shows an example of a uniform resource identifier (URI) structure for an ADAE service (ADAES) configuration application programming interface (API) according to the aspects of this disclosure. [Figure 5] This figure shows an example of a user equipment (UE) according to the aspects of this disclosure. [Figure 6] This figure shows an example of a processor according to the embodiments of this disclosure. [Figure 7] This figure shows an example of a network device (NE) according to the embodiments of this disclosure. [Figure 8] This is a flowchart of the method performed by the NE according to the aspects of this disclosure. [Modes for carrying out the invention]

[0006] Various aspects of this disclosure relate to systems that support analytics subscriptions. In some cases, the functional description of the ADAE layer may not be organized and / or defined for effective and efficient operation. To provide organization and / or definition, resource URIs may be defined to provide structure. The resource URI structure may identify ADAE services, analytics, and / or resource configurations to represent the functional description. Having defined resource URIs allows the ADAE layer to be used more efficiently in operation.

[0007] The ADAE layer may be configured or capable of supporting performance analytics for the application to provide insights into the application's behavior and performance, such as statistics or forecasts about parameters related to the application. In some implementations, the ADAE layer may be configured or capable of supporting network slice-specific performance analytics associated with the application to provide insights into the performance of the application (e.g., one or more VAL applications) when using network slices (e.g., from a list of subscribed network slices for a VAL customer). In some other implementations, the ADAE layer may be configured or capable of supporting inter-UE performance analytics associated with the application to forecast the performance of sessions between UEs (e.g., two or more VAL UEs within a service or group) and to track the derivation and publication of application layer analytics. This forecast may relate to application quality of service (QoS) attribute forecasts over time and area. In other implementations, the ADAE layer may be configured or operable to support location accuracy-related analytics to enable the VAL server to be notified, where the analytics may indicate whether location accuracy can be met for an application and, possibly, for the routes of a UE or group of UEs.

[0008] As an addition or alternative, the ADAE layer may be configured or operable to support service API analytics to enable VAL servers or any other consumers (e.g., API providers) to be informed about predicted and / or statistical availability and service levels for requested service API analytics. In some implementations, the ADAE layer may be configured or operable to support slice usage pattern analytics to provide network slice usage pattern analytics based at least partially on collected network slice performance and analytics, historical network slice status, and network performance, in order to help analytics consumers manage network slices. In some other implementations, the ADAE layer may be configured or operable to support edge load analytics to provide insights into the behavior and performance of edge domain names (EDNs), and in particular statistics or forecasts about parameters related to EAS / EES load for one or more edge application servers (EASs) / edge enabler servers (EESs), and / or edge platform load parameters. Edge platform load parameters may include load aggregation per EDN or per DN access identifier (DNAI) by edge support services and edge computing resources (e.g., load level). In other implementations, the ADAE layer may be configured or operable to support the collection of service experience information from one or more ADAE clients to support application performance analytics.

[0009] The aspects of this disclosure will be described in the context of wireless communication systems.

[0010] Figure 1 shows an example of a wireless communication system 100 according to an aspect of this disclosure. The wireless communication system 100 may include one or more NEs 102, one or more UEs 104, and a core network (CN) 106. The wireless communication system 100 may support various radio access technologies. In some implementations, the wireless communication system 100 may be a 4G network, such as an LTE network or an LTE Advanced (LTE-A) network. In some other implementations, the wireless communication system 100 may be a new radio (NR) network, such as a 5G network, a 5G Advanced (5G-A) network, or a 5G Ultra Wideband (5G-UWB) network. In other implementations, the wireless communication system 100 may be a combination of 4G and 5G networks, or other suitable radio access technologies, including IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20. The wireless communication system 100 may support wireless access technologies beyond 5G, such as 6G. In addition, the wireless communication system 100 may support technologies such as Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), or Code Division Multiple Access (CDMA).

[0011] One or more NE102s may be distributed across a geographical area to form a wireless communication system 100. One or more of the NE102s described herein may be, include, or be referred to as network nodes, base stations, network elements, network functions, network entities, radio access networks (RANs), node B, e-node B (eNB), next-generation node B (gNB), or other preferred terms. The NE102s and UE104s may communicate via a communication link, which may be wireless or wired. For example, the NE102s and UE104s may perform wireless communication over a Uu interface (e.g., receiving signaling, transmitting signaling).

[0012] NE102 may provide a geographic coverage area that allows NE102 to support services for one or more UE104 within the geographic coverage area. For example, NE102 and UE104 may support wireless communication of signals related to services (e.g., voice, video, packet data, messaging, broadcast, etc.) by one or more radio access technologies. In some implementations, NE102 may be mobile and, for example, a satellite associated with a non-terrestrial network (NTN). In some implementations, different geographic coverage areas associated with the same or different radio access technologies may overlap, but different geographic coverage areas may be associated with different NE102s.

[0013] One or more UE104 may be distributed across the entire geographical area of ​​the wireless communication system 100. UE104 may include, or be referred to as, a remote unit, mobile device, wireless device, remote device, subscriber device, transmitter device, receiver device, or any other preferred term. In some implementations, UE104 may be referred to as a unit, station, terminal, or client, among other examples. Additionally or alternatively, UE104 may be referred to as an Internet of Things (IoT) device, an Internet of Things (IoE) device, or a machine-type communications (MTC) device, among other examples.

[0014] A UE104 may be capable of supporting direct wireless communication with other UE104s over a communication link. For example, a UE104 may support direct wireless communication with another UE104 over a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-vehicle / vehicle-to-infrastructure (V2X) deployments, or cellular V2X deployments, the communication link may be called a sidelink. For example, a UE104 may support direct wireless communication with another UE104 over an inter-UE interface (PC5 interface).

[0015] An NE102 may support communication with a CN106, or with another NE102, or both. For example, an NE102 may interface with another NE102 or CN106 through one or more backhaul links (e.g., S1, N2, or network interfaces). In some implementations, NE102s may communicate directly with each other. In some other implementations, NE102s may communicate with each other or indirectly (e.g., via a CN106). In some implementations, one or more NE102s may include sub-components such as access network entities, which may be an example of an access node controller (ANC). An ANC may communicate with one or more UE104s through one or more other access network transmitting entities, which may be called radio heads, smart radio heads, or transmit / receive points (TRPs).

[0016] CN106 may support user authentication, access permission, tracking, connectivity, and other access, routing, or mobility functions. CN106 may be an advanced packet core (EPC) or 5G core (5GC) that includes control plane entities managing access and mobility (e.g., Mobility Management Entity (MME), Access and Mobility Management Function (AMF)) and user plane entities routing or interconnecting packets to external networks (e.g., Serving Gateway (S-GW), Packet Data Network (PDN) Gateway (P-GW), or User Plane Function (UPF)). In some implementations, the control plane entities may manage non-access layer (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signal bearers, etc.), for one or more UE104 serviced by one or more NE102 associated with CN106.

[0017] CN106 may communicate with a packet data network over one or more backhaul links (for example, via S1, N2, or another network interface). The packet data network may include an application server. In some implementations, one or more UE104s may communicate with the application server. UE104s may establish a session with CN106 (for example, a protocol data unit (PDU) session) via NE102. CN106 may use the established session (for example, an established PDU session) to route traffic (for example, control information, data, etc.) between UE104 and the application server. A PDU session may be an example of a logical connection between UE104 and CN106 (for example, one or more network functions of CN106).

[0018] In the wireless communication system 100, the NE102 and UE104 can perform various operations (e.g., wireless communication) using the resources of the wireless communication system 100 (e.g., time resources (e.g., symbols, slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)). In some implementations, the NE102 and UE104 may support different resource structures. For example, the NE102 and UE104 may support different frame structures. In some implementations, such as in 4G, the NE102 and UE104 may support a single frame structure. In some other implementations, such as in 5G and in other suitable radio access technologies, the NE102 and UE104 may support various frame structures (i.e., multiple frame structures). The NE102 and UE104 may support various frame structures based on one or more numerologies.

[0019] One or more numerologies may be supported within the wireless communication system 100, and a numerology may include a subcarrier spacing and a cyclic prefix. A first numerology (e.g., μ = 0) may be associated with a first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. In some implementations, the first numerology (e.g., μ = 0) associated with the first subcarrier spacing (e.g., 15 kHz) may utilize 1 slot per subframe. A second numerology (e.g., μ = 1) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. A third numerology (e.g., μ = 2) may be associated with a third subcarrier spacing (e.g., 60 kHz), and a normal cyclic prefix or an extended cyclic prefix. A fourth numerology (e.g., μ = 3) may be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a normal cyclic prefix. A fifth numerology (e.g., μ = 4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a normal cyclic prefix.

[0020] The time interval of a resource (e.g., a communication resource) may be organized according to a frame (also referred to as a radio frame). Each frame may have a duration, e.g., a 10 millisecond (ms) duration. In some implementations, each frame may include a plurality of subframes. For example, each frame may include 10 subframes, and each subframe may have a duration, e.g., a 1 ms duration. In some implementations, each frame may have the same duration. In some implementations, each subframe of a frame may have the same duration.

[0021] As an addition or alternative, the time intervals of resources (e.g., communication resources) may be organized according to slots. For example, a subframe may contain a certain number (e.g., a quantity) of slots. The number of slots in each subframe may also depend on one or more numerologies supported in the wireless communication system 100. For example, the first, second, third, fourth, and fifth numerologies (i.e., μ=0, μ=1, μ=2, μ=3, μ=4) associated with the respective subcarrier intervals of 15kHz, 30kHz, 60kHz, 120kHz, and 240kHz may utilize a single slot per subframe, two slots per subframe, four slots per subframe, eight slots per subframe, and sixteen slots per subframe, respectively. Each slot may contain a certain number (e.g., a quantity) of symbols (e.g., orthogonal frequency division multiplexing (OFDM) symbols). In some implementations, the number of slots (e.g., quantity) for a subframe may depend on the numerology. For a normal cyclic prefix, a slot may contain 14 symbols. For an extended cyclic prefix (e.g., applicable for a 60 kHz subcarrier interval), a slot may contain 12 symbols. The relationship between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame for both normal and extended cyclic prefixes may depend on the numerology. It should be understood that a reference to a first numerology (e.g., μ=0) associated with a first subcarrier interval (e.g., 15 kHz) can be used interchangeably between subframes and slots.

[0022] In the wireless communication system 100, the electromagnetic (EM) spectrum can be divided into various classes, frequency bands, frequency channels, etc. based on frequency or wavelength. As an example, the wireless communication system 100 can support one or more operating frequency bands such as frequency range designations FR1 (410 MHz to 7.125 GHz), FR2 (24.25 GHz to 52.6 GHz), FR3 (7.125 GHz to 24.25 GHz), FR4 (52.6 GHz to 114.25 GHz), FR4a or FR4-1 (52.6 GHz to 71 GHz), and FR5 (114.25 GHz to 300 GHz). In some implementations, the NE102 and the UE104 can perform wireless communication on one or more of the operating frequency bands. In some implementations, FR1 can be used by the NE102 and the UE104 among other devices or apparatuses for cellular communication traffic (e.g., control information, data). In some implementations, FR2 can be used by the NE102 and the UE104 among other devices or apparatuses for short-range, high data rate capabilities.

[0023] FR1 can be associated with one or more numerologies (e.g., at least three numerologies). For example, FR1 can be associated with a first numerology (e.g., μ = 0) including a 15 kHz subcarrier spacing, a second numerology (e.g., μ = 1) including a 30 kHz subcarrier spacing, and a third numerology (e.g., μ = 2) including a 60 kHz subcarrier spacing. FR can be associated with one or more numerologies (e.g., at least two numerologies). For example, FR2 can be associated with a third numerology (e.g., μ = 2) including a 60 kHz subcarrier spacing and a fourth numerology (e.g., μ = 3) including a 120 kHz subcarrier spacing.

[0024] To implement the functional description of the ADAE layer, resource URIs can be defined using a general structure. The resource URI structure can identify ADAE services, analytics, and / or resource configurations. NE102 and / or UE104 can execute a set of instructions to perform the described functionality.

[0025] Figure 2 shows an example of an ADAE architecture according to the embodiments of this disclosure. The ADAE architecture implements, or may implement, one or more embodiments of the wireless communication system 100. The ADAE architecture may be an example of an internal functional architecture for ADAE. In some implementations, the ADAE architecture may be a functional model for ADAE when implementing the Third Generation Partnership Project (3GPP®) Network Data Analytics Model. In the example of Figure 2, system 200 may include a data network / edge data network 202, which includes an application layer-analytical data repository function (A-ADRF) 204, an ADAE server 206, an application layer-data collection and coordination function (A-DCCF) 208, and a data source 210. System 200 may also include a consumer 212 (e.g., a vertical application layer (VAL) server).

[0026] Consumer 212 may submit a request for data (e.g., data analytics for a VAL application) via, for example, ADAE Server 206. A-DCCF208 may be configured to coordinate the collection and distribution of data requested by the consumer (e.g., ADAE Server 206). Data collection coordination is supported by A-DCCF208. ADAE Server 206 may be configured or operable to send requests for data to A-DCCF208, and A-DCCF208 may retrieve the requested data from data source 210. Thus, ADAE Server 206 may indirectly send requests for data to data source 210 via A-DCCF208 rather than directly to data source 210. A-DCCF208 may also perform data processing, data abstraction, and / or data preparation, at least in part, based on the requirements of consumer 212 (e.g., VAL Server).

[0027] The A-ADRF204 may be configured or capable of storing historical data and / or analytics (e.g., data and / or analytics relating to a previous period and acquired by a consumer (e.g., ADAE server 206)). After the consumer acquires the data and / or analytics, the consumer may store the historical data and / or analytics in a repository associated with the A-ADRF204 (e.g., a buffer, memory, or database). Whether the consumer directly interacts with the A-ADRF204 or communicates via the A-DCCF208 depends at least partially on the configuration.

[0028] The data source 210 may be a 5G system (5GS) data source (e.g., 5G core (5GC), operations and management (OAM)), or an enabler layer data source (e.g., service enabler architecture layer (SEAL), edge enabler layer (EEL)), or an external data source on the data network (DN) side (e.g., VAL server and / or EAS) and in the VAL UE. A-DCCF208 and A-ADRF204 may enable communication using several data sources (e.g., 5GC, OAM) at least partially based on their configuration. For example, A-DCCF208 and A-ADRF204 may allow a system including consumer 212 to communicate with these data sources to retrieve, receive, read, acquire, store, transmit, or any combination thereof. Additionally, A-DCCF208 and A-ADRF204 may have no interaction with the VAL.

[0029] Figure 3 shows an example of an ADAE procedure 300 according to an aspect of this disclosure. The ADAE procedure 300 implements, or may implement, one or more aspects of the wireless communication system 100. The ADAE procedure 300 may include an analytics consumer 302, an ADAE server (ADAE-S) 304, an ADAE client (ADAE-C) 306, and an A-ADRF 308. The operations between the analytics consumer 302, ADAE-S 304, ADAE-C 306, and / or A-ADRF 308 may occur in a different order or at different times than those shown. Some operations may be omitted from the ADAE procedure 300, and other operations may be added to the ADAE procedure 300.

[0030] In the example in Figure 3, analytics consumer 302 may request an analytics subscription or request analytics without a subscription. The subscription or request may be for analytics associated with the current session. Additionally or alternatively, the subscription or request may be for historical analytics associated with a previous session.

[0031] In 310, the analytics consumer 302 may submit a request to ADAE-S304 for analytics of the service. Alternatively, in 310, the analytics consumer 302 may subscribe to ADAE-S304 for analytics of the service. In 312, ADAE-S304 may evaluate whether the request for analytics, or its subscription, is for the current session (e.g., current analytics data) or for a previous session (e.g., historical analytics data).

[0032] In 314, ADAE-S304 may send or output a request for analytics for a service to ADAE-C306, at least in part on the determination that, for example, the request for analytics or its subscription is for the current session. The request may be for an analytics subscription. In some implementations, ADAE-C306 may send or output analytics data to ADAE-S304 in response to the satisfaction of a condition (e.g., a threshold for a certain amount of data or interval), which may be a trigger (e.g., an instruction) to ADAE-C306 to notify ADAE-S304. In 316, ADAE-C306 may determine that a condition is satisfied and send or output analytics data to ADAE-S304 in response to the satisfaction of the condition.

[0033] Alternatively, in 318, ADAE-S304 may send or output a request for historical analytics to A-ADRF308, at least in part, based on a determination that the request for analytics, or its subscription, is for a previous session. In some implementations, A-ADRF308 may send or output historical analytics data to ADAE-S304 in response to the satisfaction of a condition (e.g., being met), which may be a trigger (e.g., an instruction) to A-ADRF308 to notify ADAE-S304 of the historical analytics data.

[0034] In 320, A-ADRF308 may collect (e.g., receive, retrieve, obtain) historical analytics data from ADAE-C306. Note that A-ADRF308 may collect historical analytics data independently of (e.g., without receiving) a request for historical analytics data from ADAE-S304. In 322, A-ADRF308 may output or transmit historical analytics data to ADAE-S304, at least partially based on the satisfaction of the conditions.

[0035] In 324, upon receiving analytics data or historical analytics data, ADAE-S304 may send analytics to the analytics consumer 302. In some implementations, ADAE-S304 may decide whether or not to send analytics to the analytics consumer 302, and may send analytics to the analytics consumer 302 based at least in part on that decision.

[0036] Figure 4 shows an example of the URI structure 400 of the ADAES configuration API according to the embodiments of this disclosure.

[0037] The resource URI can be used as an HTTP URI in the Hypertext Transfer Protocol (HTTP) protocol for ADAE services, with the resource URI structure shown in Figure 4, where {apiRoot} is set to the value "adaes", and therefore {apiRoot} / adaes / <apiversion>The directory / data-event / {dataEventId} / configurations / {configurationId} exists, where a) "dataEventId" is set to the event identifier for ADAE services (e.g., ADAES), and b) "configurationID" is set to the resource configuration identifier.

[0038] When a consumer subscribes to analytics for the service, Table 1 provides an overview of the resources and applicable HTTP methods for the resource URI "{apiRoot} / {adaes} / data-event / {dataEventId} / configurations / {configurationId}", where "dataEventId" identifies the event identifier for analytics and "configurationId" identifies the resource.

[0039] [Table 1]

[0040] The resource can be determined by the ADAE service identification information. Table 2 provides an example of parameters supported by the HTTP POST request payload for subscribing to analytics.

[0041] [Table 2]

[0042] Table 3 shows possible responses to HTTP POST requests for analytics subscriptions.

[0043] [Table 3]

[0044] The resource URI can be used as a CoAP URI in the Constrained Application Protocol (CoAP) protocol for ADAE services, with the resource URI structure shown in Figure 4, where {apiRoot} is set to the value "adaes", and therefore {apiRoot} / adaes / <apiversion>The directory / data-event / {dataEventId} / configurations / {configurationId} exists, where a) "dataEventId" is set to the event identifier for ADAE services (e.g., ADAES), and b) "configurationID" is set to the resource configuration identifier.

[0045] When a consumer subscribes to analytics for the service, Table 4 provides an overview of the resources and applicable CoAP methods for the resource URI "{apiRoot} / {adaes} / data-event / {dataEventId} / configurations / {configurationId}", where "dataEventId" identifies the event identifier for analytics and "configurationId" identifies the resource.

[0046] [Table 4]

[0047] The resource can be determined by the ADAE service identification information. Table 5 provides an example of attributes supported by the POST request payload for subscribing to analytics.

[0048] [Table 5]

[0049] Table 6 provides possible responses to CoAP POST requests for analytics subscriptions.

[0050] [Table 6]

[0051] Figure 5 shows an example of a UE500 according to an aspect of the present disclosure. The UE500 may include a processor 502, a memory 504, a controller 506, and a transceiver 508. The processor 502, the memory 504, the controller 506, or the transceiver 508, or various combinations thereof, or various components thereof, may be examples of means for performing various aspects of the present disclosure described herein. These components may be coupled (for example, operationally, communicatively, functionally, electronically, or electrically) via one or more interfaces.

[0052] The processor 502, memory 504, controller 506, or transceiver 508, or various combinations or components thereof, may be implemented in hardware (e.g., circuitry). The hardware may include any combination thereof, which is configured as a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), or other programmable logic device, or a means for performing, or possibly supporting, the functions described herein.

[0053] The processor 502 may include an intelligent hardware device (e.g., a general-purpose processor, DSP, CPU, ASIC, field-programmable gate array (FPGA), or any combination thereof). In some implementations, the processor 502 may be configured to operate the memory 504. In some other implementations, the memory 504 may be integrated into the processor 502. The processor 502 may be configured to execute computer-readable instructions stored in the memory 504 in order to cause the UE 500 to perform various functions of this disclosure.

[0054] Memory 504 may include volatile or non-volatile memory. Memory 504 may store computer-readable, computer-executable code, which, when executed by processor 502, causes UE 500 to perform various functions described herein. The code may be stored in a non-temporary computer-readable medium, such as memory 504 or another type of memory. The computer-readable medium includes both non-temporary computer storage media and communication media, including any medium that enables the transfer of computer programs from one location to another. The non-temporary storage medium may be any available medium that can be accessed by a general-purpose or dedicated computer.

[0055] In some implementations, the processor 502 and the memory 504 coupled to the processor 502 may be configured to cause the UE 500 to perform one or more of the functions described herein (for example, by having the processor 502 execute instructions stored in the memory 504). For example, the processor 502 may support wireless communication in the UE 500, as illustrated in the examples disclosed herein.

[0056] The controller 506 can manage input and output signals for the UE500. The controller 506 can also manage peripheral devices not integrated with the UE500. In some implementations, the controller 506 may utilize an operating system, such as iOS®, Android®, Windows®, or other operating systems. In some implementations, the controller 506 may be implemented as part of the processor 502.

[0057] In some implementations, the UE500 may include at least one transceiver 508. In some other implementations, the UE500 may have two or more transceivers 508. A transceiver 508 may represent a wireless transceiver. A transceiver 508 may include one or more receiver chains 510, one or more transmitter chains 512, or a combination thereof.

[0058] The receiver chain 510 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain 510 may include one or more antennas for receiving signals over the air or over a wireless medium. The receiver chain 510 may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain 510 may include at least one demodulator configured to demodulate the received signal and obtain transmitted data by inverting the modulation technique applied during the transmission of the signal. The receiver chain 510 may include at least one decoder for decoding the demodulated signal and receiving transmitted data.

[0059] The transmitter chain 512 may be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 512 may include at least one modulator for modulating data onto a carrier signal and preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques, such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes such as phase-shift keying (PSK) or quadrature amplitude modulation (QAM). The transmitter chain 512 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over a wireless medium. The transmitter chain 512 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.

[0060] Figure 6 shows an example of a processor 600 according to an aspect of the present disclosure. The processor 600 may be an example of a processor configured to perform various operations according to the examples described herein. The processor 600 may include a controller 602 configured to perform various operations according to the examples described herein. The processor 600 may optionally include at least one memory 604, which may be, for example, an L1 / L2 / L3 cache. In addition or alternatively, the processor 600 may optionally include one or more arithmetic logic units (ALUs) 606. One or more of these components may be communicating electronically or otherwise coupled (for example, operationally, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).

[0061] The processor 600 may be a processor chipset and may include a protocol stack (e.g., a software stack) that is executed by the processor chipset to perform various operations as illustrated in the examples described herein (e.g., receiving, acquiring, retrieving, transmitting, outputting, transferring, storing, determining, identifying, accessing, writing, reading). The processor chipset may include one or more cores and one or more caches (e.g., memory local to or contained within the processor chipset (e.g., processor 600), or other memory (e.g., random access memory (RAM), read-only memory (ROM), dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), static RAM (SRAM), ferroelectric RAM (FeRAM), magnetic RAM (MRAM), resistive RAM (RRAM), flash memory, phase-change memory (PCM), etc.)).

[0062] The controller 602 may be configured to manage and coordinate various operations of the processor 600 (e.g., signaling, receiving, acquiring, retrieving, transmitting, outputting, transferring, storing, determining, identifying, accessing, writing, and reading) in order to enable the processor 600 to support various operations as illustrated in the examples described herein. For example, the controller 602 may act as a control unit of the processor 600, generating control signals that manage the operation of various components of the processor 600. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating the timing of operations.

[0063] The controller 602 may be configured to fetch (e.g., acquire, retrieve, receive) instructions from memory 604 and determine subsequent instructions to be executed in order to enable the processor 600 to support various operations as illustrated in the examples described herein. The controller 602 may be configured to track the memory address of the instruction associated with memory 604. The controller 602 may be configured to decode instructions in order to determine the operation to be performed and the operands involved. For example, the controller 602 may be configured to interpret instructions and determine control signals to be output to other components of the processor 600 in order to enable the processor 600 to support various operations as illustrated in the examples described herein. Additionally or alternatively, the controller 602 may be configured to manage the flow of data within the processor 600. The controller 602 may be configured to control the transfer of data between the registers of the processor 600, the arithmetic logic unit (ALU), and other functional units.

[0064] Memory 604 may contain one or more caches (for example, memory local to or contained within the processor 600, or other memory such as RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc.). In some implementations, memory 604 may reside within or on the processor chipset (for example, locally with the processor 600). In some other implementations, memory 604 may reside outside the processor chipset (for example, remotely with the processor 600).

[0065] Memory 604 may store computer-readable, computer-executable code, which, when executed by the processor 600, includes instructions that cause the processor 600 to perform various functions described herein. The code may be stored in a non-temporary computer-readable medium, such as system memory or another type of memory. The controller 602 and / or the processor 600 may be configured to execute the computer-readable instructions stored in memory 604 in order to cause the processor 600 to perform various functions. For example, the processor 600 and / or the controller 602 may be coupled with or to memory 604, the processor 600, the controller 602, and memory 604 may be configured to perform various functions described herein. In some examples, the processor 600 may include multiple processors, and memory 604 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may be configured individually or collectively to perform various functions described herein.

[0066] One or more ALU606s may be configured to support various operations as illustrated in the examples described herein. In some implementations, one or more ALU606s may reside within or on a processor chipset (e.g., processor 600). In some other implementations, one or more ALU606s may reside outside of a processor chipset (e.g., processor 600). One or more ALU606s may perform one or more calculations on data, such as addition, subtraction, multiplication, and division. For example, one or more ALU606s may receive input operands and arithmetic codes that determine the operation to be performed. One or more ALU606s may be configured with various logic and arithmetic circuits, including adders, subtractors, shifters, and logic gates, to process and manipulate data according to the operation. As an addition or alternative, one or more ALU606s may support logical operations such as AND, OR, exclusive OR (XOR), not-OR (NOR), and not-AND (NAND), enabling one or more ALU606s to handle conditional operations, comparisons, and bitwise operations.

[0067] The processor 600 may support wireless communication as illustrated herein. The processor 600 may be configured or operable to support means for receiving a message from a first device, the message comprising instructions identifying a service or application and instructions identifying analytics associated with the service or application; sending a request to a second device for a subscription to analytics; receiving a response associated with analytics from the second device; and sending a response associated with analytics to the first device.

[0068] Figure 7 shows an example of an NE700 according to an aspect of the present disclosure. The NE700 may include a processor 702, a memory 704, a controller 706, and a transceiver 708. The processor 702, the memory 704, the controller 706, or the transceiver 708, or various combinations thereof, or various components thereof, may be examples of means for performing various aspects of the present disclosure described herein. These components may be coupled (for example, operationally, communicatively, functionally, electronically, or electrically) via one or more interfaces.

[0069] The processor 702, memory 704, controller 706, or transceiver 708, or various combinations or components thereof, may be implemented in hardware (e.g., circuitry). The hardware may include any combination thereof, which is configured as a processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), or other programmable logic device, or a means for performing, or possibly supporting, the functions described herein.

[0070] The processor 702 may include an intelligent hardware device (e.g., a general-purpose processor, DSP, CPU, ASIC, FPGA, or any combination thereof). In some implementations, the processor 702 may be configured to operate the memory 704. In some other implementations, the memory 704 may be integrated into the processor 702. The processor 702 may be configured to execute computer-readable instructions stored in the memory 704 in order to cause the NE700 to perform various functions of this disclosure.

[0071] Memory 704 may include volatile or non-volatile memory. Memory 704 may store computer-readable, computer-executable code, which, when executed by processor 702, causes NE700 to perform various functions described herein. The code may be stored in a non-temporary computer-readable medium, such as memory 704 or another type of memory. The computer-readable medium includes both non-temporary computer storage media and communication media, including any medium that enables the transfer of computer programs from one location to another. The non-temporary storage medium may be any available medium that can be accessed by a general-purpose or dedicated computer.

[0072] In some implementations, the processor 702 and the memory 704 coupled with the processor 702 may be configured to cause the NE700 to perform one or more of the functions described herein (for example, by executing instructions stored in the memory 704 by the processor 702). For example, the processor 702 may support wireless communication in the NE700 as illustrated in the examples disclosed herein. The NE700 may be configured to support means for receiving a message from a first device, the message comprising instructions identifying a service or application and instructions identifying analytics associated with the service or application; sending a request to a second device for a subscription to analytics; receiving a response associated with analytics from the second device; and sending a response associated with analytics to the first device.

[0073] The controller 706 can manage input and output signals for the NE700. The controller 706 can also manage peripheral devices not integrated into the NE700. In some implementations, the controller 706 may utilize an operating system, such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, the controller 706 may be implemented as part of the processor 702.

[0074] In some implementations, the NE700 may include at least one transceiver 708. In some other implementations, the NE700 may have two or more transceivers 708. A transceiver 708 may represent a wireless transceiver. A transceiver 708 may include one or more receiver chains 710, one or more transmitter chains 712, or a combination thereof.

[0075] The receiver chain 710 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain 710 may include one or more antennas for receiving signals over the air or over a wireless medium. The receiver chain 710 may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain 710 may include at least one demodulator configured to demodulate the received signal and obtain transmitted data by inverting the modulation technique applied during the transmission of the signal. The receiver chain 710 may include at least one decoder for decoding the demodulated signal and receiving transmitted data.

[0076] The transmitter chain 712 may be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 712 may include at least one modulator for modulating data onto a carrier signal and preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques, such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes such as phase-shift keying (PSK) or quadrature amplitude modulation (QAM). The transmitter chain 712 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over a wireless medium. The transmitter chain 712 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.

[0077] Figure 8 shows a flowchart of Method 800 according to an aspect of the present disclosure. The operation of Method 800 can be carried out by an NE as described herein. In some implementations, the NE may execute a set of instructions to control the functional elements of the NE in order to perform the described function.

[0078] In 802, the method may include receiving a message from a first device, wherein the message comprises instructions identifying a service or application and instructions identifying analytics associated with the service or application. The operation of 802 may be performed according to the examples described herein. In some implementations, the operation of 802 may be performed by the NE described with reference to Figure 7.

[0079] In 804, the method may include sending a request for an analytics subscription to a second device. The operation of 804 may be performed according to the examples described herein. In some implementations, the operation of 804 may be performed by the NE described with reference to Figure 7.

[0080] In 806, the method may include receiving a response associated with analytics from a second device. The operation of 806 may be performed according to the examples described herein. In some implementations, the operation of 806 may be performed by the NE described with reference to Figure 7.

[0081] In 808, the method may include sending a response associated with analytics to the first device. The operation of 808 may be performed according to the examples described herein. In some implementations, the operation of 808 may be performed by the NE described with reference to Figure 7.

[0082] It should be noted that the methods described herein are described in terms of possible implementations, and that the operations and steps may be rearranged or otherwise modified, and that other implementations are possible.

[0083] The descriptions herein are provided to enable those skilled in the art to create or use this disclosure. Various modifications of this disclosure will become apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of this disclosure. Accordingly, this disclosure is not limited to the examples and designs described herein and should be given the broadest scope that is consistent with the principles and novel features disclosed herein. [Explanation of symbols]

[0084] 100 Wireless Communication Systems 102,700 NE 104,500 UE 106 Core Network (CN), CN 200 Systems 202 Data Networks / Edge Data Networks 204 Application Layer Analysis Data Repository Function (A-ADRF), A-ADRF 206 ADAE Server 208 Application Layer Data Acquisition and Coordination Function (A-DCCF), A-DCCF 210 data sources 212 Consumer 302 Analytics Consumer 304 ADAE Server (ADAE-S), ADAE-S 306 ADAE Client (ADAE-C), ADAE-C 308 A-ADRF 400 URI structure 502, 600, 702 processors 504, 604, 704 memory 506, 602, 706 controllers 508, 708 transceivers 510, 710 receiver chain 512, 712 Transmitter Chain 606 Arithmetic logic unit (ALU), ALU< / apiversion> < / apiversion>

Claims

1. A device for performing network functions, wherein the device is At least one memory, At least one processor coupled to the at least one memory and The device includes, and the at least one processor provides the device, Receiving a message from the first device, wherein the message is Instructions to identify the service or application, Instructions to identify analytics associated with the aforementioned service or application It is equipped with the ability to receive, To send a request for the analytics subscription to the second device, Receiving responses associated with the analytics from the second device, To transmit the response associated with the analytics to the first device. A device configured to perform a certain action.

2. The apparatus according to claim 1, wherein the message further comprises instructions identifying a configuration for a resource.

3. The apparatus according to claim 2, wherein the configuration for the resource comprises one or more parameters supported by a protocol.

4. The aforementioned protocol, Hypertext Transfer Protocol (HTTP), or Constrained Application Protocol (CoAP) The apparatus according to claim 3, comprising:

5. The apparatus according to claim 1, wherein the second device comprises a network entity, a client device, or a combination thereof.

6. The apparatus according to claim 1, wherein the first device comprises an analytics consumer.

7. The device includes an Application Data Analytics Activation (ADAE) server that performs the network function, The apparatus according to claim 1, wherein the second device comprises an Application Layer Analysis Data Repository (A-ADRF) function or an ADAE client.

8. A method for performing a network function, wherein the method is A step of receiving a message from a first device, wherein the message is Instructions to identify the service or application, Instructions to identify analytics associated with the aforementioned service or application It has steps, The steps include sending a request for the analytics subscription to a second device, The steps include receiving a response associated with the analytics from the second device, The steps include: transmitting the response associated with the analytics to the first device; Methods that include...

9. The method according to claim 8, wherein the message further comprises instructions identifying a configuration for a resource.

10. The method according to claim 9, wherein the configuration for the resource comprises one or more parameters supported by a protocol method.

11. The aforementioned protocol method Hypertext Transfer Protocol (HTTP) method, or Constrained Application Protocol (CoAP) methods The method according to claim 10, comprising:

12. The method according to claim 8, wherein the second device comprises a network entity, a client device, or a combination thereof.

13. The method according to claim 8, wherein the first device comprises an analytics consumer.

14. The Application Data Analytics Enablement (ADAE) server executes the aforementioned network functions. The method according to claim 8, wherein the second device comprises an Application Layer Analysis Data Repository (A-ADRF) or an ADAE client.

15. A device for performing network functions, wherein the device is At least one memory, At least one processor coupled to the at least one memory and The device includes, and the at least one processor provides the device, Sending a message, wherein the message is Instructions to identify the service or application, Instructions to identify analytics associated with the aforementioned service or application It includes the ability to transmit, Receiving the response associated with the aforementioned analytics and A device configured to perform a certain action.

16. The apparatus according to claim 15, wherein the message further comprises instructions for identifying a configuration for a resource.

17. The apparatus according to claim 16, wherein the configuration for the resource comprises one or more parameters supported by a protocol.

18. The aforementioned protocol, Hypertext Transfer Protocol (HTTP), or Constrained Application Protocol (CoAP) The apparatus according to claim 17, comprising:

19. The apparatus according to claim 15, wherein the apparatus comprises an analytics consumer.

20. A method for performing a network function, wherein the method is A step of sending a message, wherein the message is Instructions to identify the service or application, Instructions to identify analytics associated with the aforementioned service or application It has steps, The steps include receiving a response associated with the aforementioned analytics and Methods that include...

Images