Login| Sign Up| Help| Contact|

Patent Searching and Data


Title:
DISTRIBUTED ANALYTICS IN 5GC
Document Type and Number:
WIPO Patent Application WO/2019/197467
Kind Code:
A1
Abstract:
Methods, devices and systems for providing distributed analytics to network functions are provided. Operations of methods, devices and systems include providing (705) a network data analytics function that is configured to collect on-line and/or offline data from a source network function and to generate analytical information for a consumer network function. Operations include generating (710) an instance of the network data analytics function that corresponds to the source network function and that is configured to provide near real-time analytics data corresponding to the source network function to the consumer network function.

Inventors:
ÖRTENBLAD HELEN (SE)
MATTSSON ULF (SE)
PUENTE PESTAÑA MIGUEL (ES)
MANZANO MACHO DAVID (ES)
PANCORBO MARCOS MARIA (ES)
INIESTA GONZALEZ ANTONIO (ES)
Application Number:
EP2019/059084
Publication Date:
October 17, 2019
Filing Date:
April 10, 2019
Export Citation:
Click for automatic bibliography generation   Help
Assignee:
ERICSSON TELEFON AB L M (SE)
International Classes:
H04L12/24; H04L12/26
Foreign References:
Other References:
HUAWEI ET AL: "Update on Architecture Assumption", vol. SA WG2, no. Montreal, Canada; 20180226 - 20180302, 20 February 2018 (2018-02-20), XP051408514, Retrieved from the Internet [retrieved on 20180220]
ERICSSON ET AL: "Moving Network Analytics functionality into 23.501", vol. SA WG2, no. Montreal, Canada; 20180226 - 20180302, 14 March 2018 (2018-03-14), XP051531753, Retrieved from the Internet [retrieved on 20180314]
"3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 5G System; Network Data Analytics Services; Stage 3 (Release 15)", 3GPP STANDARD; TECHNICAL SPECIFICATION; 3GPP TS 29.520, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. CT WG3, no. V0.4.0, 12 March 2018 (2018-03-12), pages 1 - 36, XP051450392
XP055512308
None
Attorney, Agent or Firm:
ERICSSON (SE)
Download PDF:
Claims:
Claims:

1. A method of providing distributed analytics to network functions, the method comprising:

providing (705) a network data analytics function that is configured to collect on-line and/or offline data from a source network function and to generate analytical information for a consumer network function; and

generating (710) an instance of the network data analytics function that corresponds to the source network function and that is configured to provide near real-time analytics data corresponding to the source network function to the consumer network function.

2. The method of Claim 1, further comprising registering (715) the instance of the network data analytics function in a network function repository function that is configured to receive a query from the consumer network function requesting service to support an analytic identifier and to use the analytic identifier to resolve which instance of the network data analytics function corresponds to the query.

3. The method of any of Claims 1-2, wherein the instance of the network data analytics function is co-located with the source network function.

4. The method of any of Claims 1-3, wherein the instance of the network data analytics function is configured to generate (720) analytical information based on network function logical events corresponding to the source network function and/or data from other sources and/or network functions.

5. The method of any of Claims 1-4, wherein the instance of the network data analytics function is configured to generate (720) analytical information based on historical event data that is provided from offline sources.

6. The method of any of Claims 1-5, wherein the instance of the network data analytics function is configured to generate (720) analytical information based on near real-time data that is provided from online sources.

7. The method of any of Claims 1-6, wherein the instance of the network data analytics function is configured to send (725) a request for near real-time data to the source network function responsive to determining that the near real-time data is an input for the network data analytics function.

8. The method of any of Claims 1-7, wherein the instance of the network data analytics function is configured to receive (730) a subscription request from the consumer network function that includes a network instance identifier, a periodicity value corresponding to notification frequency and/or a level threshold value corresponding to a threshold based notification, and

wherein, responsive to receiving the subscription request, the instance of the network data analytics function is further configured to send (735) a confirmation of the subscription to the consumer network function.

9. The method of Claim 8, wherein the instance of the network data analytics function is configured to receive (740) an unsubscribe request from the consumer network function that includes the network instance identifier, the periodicity value corresponding to notification frequency and/or the level threshold value corresponding to the threshold based notification, and

wherein, responsive to receiving the unsubscribe request, the instance of the network data analytics function is further configured to send (745) a confirmation of unsubscription to the consumer network function.

10. The method of any of Claims 8-9, wherein the instance of the network data analytics function is configured to send (750) a notification to the consumer network function responsive to an event that is generated based on the periodicity value and/or the level threshold value.

11. The method of any of Claims 1-7, wherein the instance of the network data analytics function is configured to receive a request (755) from the consumer network function for network function operator specific analytical information.

12. The method of Claim 1, wherein the network data analytics function comprises a decentralizing network data analytics function that includes a plurality of instances of network data analytics functions that correspond to a plurality of source network functions.

13. The method of any of Claims 1-12, wherein the network data analytics function is configured to operate internal to the source network function to generate the analytical information, and

wherein the source network function receives (760) a subscription request from the consumer network function and sends (765) a notification to the consumer network function, the notification being based on the analytical information.

14. A first communication node comprising:

a memory (605); and

a processor (603) coupled to the memory and configured to perform operations comprising:

providing a network data analytics function that is configured to collect on-line and/or offline data from a source network function and to generate analytical information for a consumer network function; and

generating an instance of the network data analytics function that corresponds to the source network function and that is configured to provide near real-time analytics data corresponding to the source network function to the consumer network function.

15. The first communication node of Claim 14, wherein the processor is adapted to perform operations according to any of Claims 2-13.

16. A core network node, wherein the first core network node includes respective modules adapted to perform according to any of Claims 1-13.

17. A method of operating a first communication node (600), the method comprising: providing (705) a network data analytics function that is configured to collect on-line and/or offline data from a source network function and to generate analytical information for a consumer network function; and

generating (710) an instance of an analytics function that is part of the source network function and that is configured to provide near real-time analytics data corresponding to the source network function to the consumer network function.

18. The method of Claim 17, further comprising registering (715) the instance of the analytics function in a network function repository function that is configured to receive a query from the consumer network function requesting service to support an analytic identifier and to use the analytic identifier to resolve which instance or service part of the analytics function corresponds to the query,

wherein if the registering is performed as a service of the corresponding source network function, then the query and a response thereto is part of a notify operation.

19. The method of any of Claims 17-18, wherein the instance of the network data analytics function is co-located with and/or internal to the source network function.

20. The method of any of Claims 17-19, wherein the instance of the network data analytics function is configured to generate (720) analytical information based on network function logical events corresponding to the source network function and/or events and/or data from other data sources and/or network functions.

21. The method of any of Claims 17-20, wherein the instance of the network data analytics function is configured to generate (720) analytical information based on historical event data that is provided from offline sources.

22. The method of any of Claims 17-21, wherein the instance of the network data analytics function is configured to generate (720) analytical information based on near real-time data that is provided from online sources.

23. The method of any of Claims 17-22, wherein the instance of the network data analytics function is configured to send (725) an internal request for near real-time data to the source network function responsive to determining that the near real-time data is an input for the network data analytics function, wherein the internal request is from the source network function.

24. The method of any of Claims 17-23, wherein the instance of the network data analytics function is configured to receive (730) a subscription request from the consumer network function that includes a network instance identifier, a periodicity value corresponding to notification frequency and/or a level threshold value corresponding to a threshold based notification, and

wherein, responsive to receiving the subscription request, the instance of the network data analytics function is further configured to send (735) a confirmation of the subscription to the consumer network function.

25. The method of Claim 24, wherein the instance of the network data analytics function is configured to receive (740) an unsubscribe request from the consumer network function that includes the network instance identifier, the periodicity value corresponding to notification frequency and/or the level threshold value corresponding to the threshold based notification, and

wherein, responsive to receiving the unsubscribe request, the instance of the network data analytics function is further configured to send (745) a confirmation of unsubscription to the consumer network function.

26. The method of any of Claims 24-25, wherein the instance of the network data analytics function is configured to send (750) a notification to the consumer network function responsive to an event that is generated based on the periodicity value and/or the level threshold value.

27. The method of any of Claims 17-24, wherein the instance of the network data analytics function is configured to receive (755) a request from the consumer network function for network function operator specific analytical information.

28. The method of Claim 17, wherein the network data analytics function comprises a decentralizing network data analytics function that includes a plurality of instances of network data analytics functions that correspond to a plurality of source network functions.

29. The method of any of Claims 17-28, wherein the network data analytics function is configured to operate internal to the source network function to generate the analytical information, and

wherein the source network function receives (760) a subscription request from the consumer network function and sends (765) a notification to the consumer network function, the notification being based on the analytical information.

Description:
DISTRIBUTED ANALYTICS IN 5GC

TECHN1CAL F1ELD

[0001 ] The present disclosure relates generally to communications, and more

particularly, to wireless communications and related wireless devices and network nodes.

BACKGROUND

[0002] Network Data Analytics Function (NWDAF) is a centralized Network Function

(NF) being standardized by the 3 rd Generation Partnership Project (3GPP) for 5GC. NWDAF represents operator managed network analytics logical function. NWDAF provides analytical information to consumers such as other NFs. FIG. 1 illustrates examples of NFs including NWDAF in 5G architecture.

SUMMARY

[0003] According to some embodiments, a method may be provided to distribute analytics to network functions. The method can include providing a network data analytics function that is configured to collect on-line and/or offline data from a source network function and to generate analytical information for a consumer network function. The method can further include generating an instance of the network data analytics function that corresponds to the source network function and that is configured to provide near real-time analytics data corresponding to the source network function to the consumer network function.

[0004] New use cases can demand near real-time data being available to support the processing of the analytical information. This can put real-time streaming requirements on the sources producing the input to the NWDAF or real-time data may be sent together with the request. Embodiments provided herein provide mechanisms to distribute the analytics or at least parts of the analytics. In some embodiments, the NWDAF is distributed into

decentralized instances. These instances can then either be co -located with other NFs or part of other NFs. In some examples, these mechanisms can include re-using the NWDA service to expose the analytical information to consumers. Distributing the analytics can reduce data transportation, introduce near real-time data, lower processing performed in a central location, and allow operators to produce leverage and share analytics among NFs in a more efficient process with a decentralized analytics processing structure.

[0005] Some embodiments include registering the instance of the network data analytics function in a network function repository function that is configured to receive a query from the consumer network function requesting service to support an analytic identifier and to use the analytic identifier to resolve which instance of the network data analytics function corresponds to the query. In some embodiments, the instance of the network data analytics function is co- located with the source network function.

[0006] In some embodiments, the instance of the network data analytics function is configured to generate analytical information based on network function logical events corresponding to the source network function and/or data from other sources and/or network functions. Some embodiments provide that the instance of the network data analytics function is configured to generate analytical information based on historical event data that is provided from offline sources.

[0007] In some embodiments, the instance of the network data analytics function is configured to generate analytical information based on near real-time data that is provided from online sources. Some embodiments provide that the instance of the network data analytics function is configured to send a request for near real-time data to the source network function responsive to determining that the near real-time data is an input for the network data analytics function.

[0008] In some embodiments, the instance of the network data analytics function is configured to receive a subscription request from the consumer network function that includes a network instance identifier, a periodicity value corresponding to notification frequency and/or a level threshold value corresponding to a threshold based notification and, responsive to receiving the subscription request, the instance of the network data analytics function is further configured to send a confirmation of the subscription to the consumer network function. In some embodiments, the instance of the network data analytics function is configured to receive an unsubscribe request from the consumer network function that includes the network instance identifier, the periodicity value corresponding to notification frequency and/or the level threshold value corresponding to the threshold based notification and, responsive to receiving the unsubscribe request, the instance of the network data analytics function is further configured to send a confirmation of unsubscription to the consumer network function.

[0009] Some embodiments provide that the instance of the network data analytics function is configured to send a notification to the consumer network function responsive to an event that is generated based on the periodicity value and/or the level threshold value.

[0010] In some embodiments, the instance of the network data analytics function is configured to receive a request from the consumer network function for network function operator specific analytical information.

[001 1 ] In some embodiments, the network data analytics function comprises a decentralizing network data analytics function that includes a plurality of instances of network data analytics functions that correspond to a plurality of source network functions.

[0012] Some embodiments provide that the network data analytics function is configured to operate internal to the source network function to generate the analytical information and the source network function receives a subscription request from the consumer network function and sends a notification to the consumer network function, the notification being based on the analytical information.

[0013] Some embodiments of the present inventive concept are directed to a first communication node that includes a memory and a processor coupled to the memory and configured to perform operations comprising providing a network data analytics function that is configured to collect on-line and/or offline data from a source network function and to generate analytical information for a consumer network function and generating an instance of the network data analytics function that corresponds to the source network function and that is configured to provide near real-time analytics data corresponding to the source network function to the consumer network function.

[0014] In some embodiments, the processor is adapted to perform operations according to any of the operations described herein. Some embodiments provide a core network node that includes respective modules adapted to perform according to any of the operations described herein.

[0015] Some embodiments of the present inventive concept include methods of operating a first communication node. Such methods include operations comprising providing a network data analytics function that is configured to collect on-line and/or offline data from a source network function and to generate analytical information for a consumer network function, and generating an instance of an analytics function that is part of the source network function and that is configured to provide near real-time analytics data corresponding to the source network function to the consumer network function.

[0016] Some embodiments include registering the instance of the analytics function in a network function repository function that is configured to receive a query from the consumer network function requesting service to support an analytic identifier and to use the analytic identifier to resolve which instance or service part of the analytics function corresponds to the query. In some embodiments, if the registering is performed as a service of the corresponding source network function, then the query and a response thereto is part of a notify operation.

[0017] In some embodiments, the instance of the network data analytics function is co- located with and/or internal to the source network function. Some embodiments provide that the instance of the network data analytics function is configured to generate analytical information based on network function logical events corresponding to the source network function and/or events and/or data from other data sources and/or network functions.

[0018] In some embodiments, the instance of the network data analytics function is configured to generate analytical information based on historical event data that is provided from offline sources. Some embodiments provide that the instance of the network data analytics function is configured to generate analytical information based on near real-time data that is provided from online sources.

[0019] Some embodiments provide that the instance of the network data analytics function is configured to send an internal request for near real-time data to the source network function responsive to determining that the near real-time data is an input for the network data analytics function, wherein the internal request is from the source network function.

[0020] In some embodiments, the instance of the network data analytics function is configured to receive a subscription request from the consumer network function that includes a network instance identifier, a periodicity value corresponding to notification frequency and/or a level threshold value corresponding to a threshold based notification. Some embodiments provide that, responsive to receiving the subscription request, the instance of the network data analytics function is further configured to send a confirmation of the subscription to the consumer network function. In some embodiments, the instance of the network data analytics function is configured to receive an unsubscribe request from the consumer network function that includes the network instance identifier, the periodicity value corresponding to notification frequency and/or the level threshold value corresponding to the threshold based notification and that, responsive to receiving the unsubscribe request, the instance of the network data analytics function is further configured to send a confirmation of unsubscription to the consumer network function.

[0021 ] In some embodiments, the instance of the network data analytics function is configured to send a notification to the consumer network function responsive to an event that is generated based on the periodicity value and/or the level threshold value. In some embodiments, the instance of the network data analytics function is configured to receive a request from the consumer network function for network function operator specific analytical information.

[0022] In some embodiments, the network data analytics function comprises a decentralizing network data analytics function that includes a plurality of instances of network data analytics functions that correspond to a plurality of source network functions.

[0023] Some embodiments provide that the network data analytics function is configured to operate internal to the source network function to generate the analytical information and that the source network function receives a subscription request from the consumer network function and sends a notification to the consumer network function, the notification being based on the analytical information.

[0024] According to some embodiments of inventive concepts, a mechanism can be provided to increase the speed and efficiency of near real-time data processing by distributing the processing.

BRIEF DESCRIPTION OF THE DRAWINGS

[0025] The accompanying drawings, which are included to provide a further

understanding of the disclosure and are incorporated in a constitute a part of this application, illustrate certain non-limiting embodiments of inventive concepts. In the drawings:

[0026] FIG. 1 is a block diagram illustrating an example of functions available in a 5G system;

[0027] FIG. 2 is a table illustrating an example of services offered by NWDAF; [0028] FIG. 3 is a block diagram illustrating an example of distributed analytics according to some embodiments of the present disclosure;

[0029] FIG. 4 is a block diagram illustrating another example of distributed analytics according to some embodiments of the present disclosure;

[0030] FIG. 5 is a block diagram illustrating an example of a wireless device UE according to some embodiments of the present disclosure;

[0031 ] FIG. 6 is a block diagram illustrating an example of a network node according to some embodiments of the present disclosure;

[0032] FIG. 7 is a flow chart illustrating an example of a process for providing distributed analytics to network functions according to some embodiments of the present disclosure;

[0033] FIG. 8 is a block diagram illustrating an example of a AMF according to some embodiments of the present disclosure;

[0034] FIG. 9 is a block diagram illustrating an example of a SMF according to some embodiments of the present disclosure;

[0035] Figure QQ1 is a block diagram of a wireless network in accordance with some embodiments;

[0036] Figure QQ2 is a block diagram of a user equipment in accordance with some embodiments

[0037] Figure QQ3 is a block diagram of a virtualization environment in accordance with some embodiments;

[0038] Figure QQ4 is a block diagram of a telecommunication network connected via an intermediate network to a host computer in accordance with some embodiments;

[0039] Figure QQ5 is a block diagram of a host computer communicating via a base station with a user equipment over a partially wireless connection in accordance with some embodiments;

[0040] Figure QQ6 is a block diagram of methods implemented in a communication system including a host computer, a base station, and a user equipment in accordance with some embodiments; [0041 ] Figure QQ7 is a block diagram of methods implemented in a communication system including a host computer, a base station, and a user equipment in accordance with some embodiments;

[0042] Figure QQ8 is a block diagram of methods implemented in a communication system including a host computer, a base station, and a user equipment in accordance with some embodiments; and

[0043] Figure QQ9 is a block diagram of methods implemented in a communication system including a host computer, a base station, and a user equipment in accordance with some embodiments.

DETAILED DESCRIPTION

[0044] FIG. 2 illustrates examples of services offered by NWDAF according to Rel. 15.

The NWDAF sits in the service based architecture (SBA). The Nnwdaf_EventsSubscription Service enables a consumer to subscribe/unsubscribe for load events notification of Network Slice instance. Periodic notification and notification upon threshold exceeded can be subscribed to by a consumer network function.

[0045] An example of a Nnwdaf EventsSubscription service operation is the

Nnwdaf_EventsSubscription_Subscribe service operation that can subscribe to NWDAF event with specific parameters. This service operation can require an identifier of a network slice instance as an input and can periodically receive a load level threshold value as input. This service can output confirmation of the subscription. Another example of a

Nnwdaf_EventsSubscription service operation is the Nnwdaf_EventsSubscription_Unsubscribe service operation that can unsubscribe to NWDAF event with specific parameters. This service operation can require an identifier of a network slice instance as an input and can periodically receive a load level threshold value as input. This service can output confirmation of the unsubscription. Another example of a Nnwdaf EventsSubscription service operation is the Nnwdaf_EventsSubscription_Notify service operation that can cause the NWDAF to notify the consumer instance of the event that has subscribed to the specific NWDAF service. Depending upon the type of subscription this notification is either on a periodic basis or triggered whenever a threshold is crossed. This service operation can require an identifier of a network slice instance and load level information of the network slice instance as input. This service can periodically receive a load level threshold value as input. This service can output confirmation of the unsubscription.

[0046] The Nnwdaf Analytics Info service can enable the consumer to request and get from NWDAF load level information of network slice instance. The request for load information can be for a particular network slice instance and can represent the information that has a meaning only in its network. The request can include an analytic ID identifying the load level information of a particular network slice instance with the identification information of the corresponding slice explicitly or implicitly. The response can be the requested analytic. An example of a Nnwdaf Analytics info service operation is the

Nnwdaf AnalyticsInfo Request service operation that allows the consumer to request

NWDAF operator specific analytics. This service operation can require an analytic ID identifying the requested load level information of a network slice instance. The request may include multiple parameters for the specific NWDAF service being requested including event parameters such as load level information with event filters that may include a network slice instance and/or a load level threshold value. This service can output analysis with multiple parameters. The output may include the Nwdaf EventsSubscription Notify service in which the consumer instance is notified of the event that has subscribed to the specific NWDAF service. Depending upon type of subscription this notification may be either on a periodic basis or triggered whenever a threshold is crossed. Inputs may include Event ID, Notification Target Address (+ Notification Correlation ID), Identifier of Network Slice instance, and/or Load level information of Network Slice instance, among others.

[0047] 5 th generation wireless systems (5G) and/or Next Generation (NG) Systems can include various components. For example, 5G architecture can include a user equipment (UE), a radio access network (RAN), a user plane function (UPF), an access and mobility management function (AMF), a session management function (SMF), a policy control function (PCF), and a user data repository (UDR). A UE can include a terminal where the front-end of the application runs and can be attached via radio channel to a base station. The RAN can be a radio access point and in EC scenarios, the RAN can host the EC platform allowing EC applications to be directly deployed and executed at the base station site. The UPF can be a gateway that routes the traffic towards the EC platform and the central DN. IT can be collocated with the base station or as a standalone component. The AMF can be an entity in charge of UE access and mobility management. The SMF can be an entity in charge of the session management for the UE communications. The SMF can establish, handle, and release the PDU sessions. The MF can select the UPF for the user traffic and provide the UPF with instructions for routing according to local or external policies (e.g., from a PCF). The PCF can support a unified policy framework to govern network behavior. The PCF can provide policy rules to the control plane function (CPF) so that they are enforced (e.g., charging, quality of service (QoS), or traffic steering policies). The UDR can be an entity in charge of storing the information of subscriber profiles, the authentication credential repository, etc. Additional description of 5G architecture can be found in TS 23.501 [1]

[0048] The Event Exposure Service, as defined in 3GPP TS 23.502 [3] and 3GPP TS

23.503 [6], is provided by the NFs. The event exposure service can allow consumer NFs to subscribe and unsubscribe for events (e.g., for a specific UE or PDU Session, a group of UEs or any UE). The event exposure service can notify consumer NFs with a corresponding

subscription about observed events on the PDU session.

[0049] Processing of near-real time data for the services offered by 5G architecture can be time and processing power intensive.

[0050] Inventive concepts will now be described more fully hereinafter with reference to the accompanying drawings, in which examples of embodiments of inventive concepts are shown. Inventive concepts may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of present inventive concepts to those skilled in the art. It should also be noted that these embodiments are not mutually exclusive. Components from one embodiment may be tacitly assumed to be present/used in another embodiment.

[0051 ] The following description presents various embodiments of the disclosed subject matter. These embodiments are presented as teaching examples and are not to be construed as limiting the scope of the disclosed subject matter. For example, certain details of the described embodiments may be modified, omitted, or expanded upon without departing from the scope of the described subject matter.

[0052] FIG. 5 is a block diagram illustrating elements of a UE, which can be

interchangeably called any one or more of a wireless terminal, a wireless communication device, wireless device, a wireless communication terminal, and a user equipment node/terminal/device without limitation on the operations thereof. The UE is configured to provide wireless communication according to embodiments of inventive concepts. As shown, UE may include at least one antenna 507, and at least one transceiver circuit 501 (also referred to as a transceiver) including a transmitter and a receiver configured to provide uplink and downlink radio communications with a base station eNB of a wireless communication network (also referred to as a radio access network RAN). UE may also include at least one processor circuit 503 (also referred to as a processor) coupled to the transceiver, and at least one memory circuit 505 (also referred to as memory) coupled to the processor. The memory 505 may include computer readable program code that when executed by the processor 503 causes the processor to perform operations according to embodiments disclosed herein. According to other embodiments, processor 503 may be defined to include memory so that a separate memory circuit is not required. UE may also include an interface (such as a user interface) coupled with processor 503, and/or wireless device UE may be an IoT and/or MTC device.

[0053] As discussed herein, operations of wireless device UE may be performed by processor 503 and/or transceiver 501. For example, processor 503 may control transceiver 501 to transmit uplink communications through transceiver 501 over a radio interface to a base station eNB of a wireless communication network and/or to receive downlink communications through transceiver 501 from a base station eNB of the wireless communication network over a radio interface. Moreover, modules may be stored in memory 505, and these modules may provide instructions so that when instructions of a module are executed by processor 503, processor 503 performs respective operations (e.g., operations discussed below with respect to Example Embodiments).

[0054] FIG. 6 is a block diagram illustrating elements of a node (also referred to as a network node, base station, eNB, eNodeB, etc.) of a wireless communication network (also referred to as a RAN) configured to provide cellular communication according to embodiments of inventive concepts. As shown, the network node may include at least one transceiver circuit 601 (also referred to as a transceiver) including a transmitter and a receiver configured to provide uplink and downlink radio communications with wireless devices. The network node may include at least one network interface circuit 607 (also referred to as a network interface) configured to provide communications with nodes (e.g., with other base stations and/or core network nodes). The network node may also include at least one processor circuit 603 (also referred to as a processor) coupled to the transceiver, and at least one memory circuit 605 (also referred to as memory) coupled to the processor. The memory 605 may include computer readable program code that when executed by the processor circuit 603 causes the processor to perform operations according to embodiments disclosed herein. According to other

embodiments, processor 603 may be defined to include memory so that a separate memory circuit is not required.

[0055] As discussed herein, operations of the network node may be performed by processor 603, network interface 607, and/or transceiver 601. For example, processor 603 may control transceiver 601 to transmit downlink communications through transceiver 601 over a radio interface to one or more UEs and/or to receive uplink communications through transceiver 601 from one or more UEs over a radio interface. Similarly, processor 603 may control network interface 607 to transmit communications through network interface 607 to one or more other network nodes and/or to receive communications through network interface from one or more other network nodes. Moreover, modules may be stored in memory 605, and these modules may provide instructions so that when instructions of a module are executed by processor 603, processor 603 performs respective operations (e.g., operations discussed below with respect to Example Embodiments).

[0056] FIG. 8 is a block diagram illustrating elements of an AMF configured to provide wireless communication according to embodiments of inventive concepts. As shown the AMF may include at least one network interface circuit 807 (also referred to as a network interface) configured to provide communications with nodes (e.g., with base stations and/or core network nodes). The AMF may also include at least one processor circuit 803 (also referred to as a processor) coupled to the transceiver, and at least one memory circuit 805 (also referred to as memory) coupled to the processor. The memory circuit 805 may include computer readable program code that when executed by the processor 803 causes the processor 803 to perform operations according to embodiments disclosed herein. According to other embodiments, processor 803 may be defined to include memory so that a separate memory circuit is not required.

[0057] As discussed herein, operations of the AMF may be performed by processor 803 and/or network interface 807. Modules may be stored in memory 805, and these modules may provide instructions so that when instructions of a module are executed by processor 803, processor 803 performs respective operations (e.g., operations discussed below with respect to Example Embodiments).

[0058] FIG. 9 is a block diagram illustrating elements of an SMF configured to provide wireless communication according to embodiments of inventive concepts. As shown the SMF may include at least one network interface circuit 907 (also referred to as a network interface) configured to provide communications with nodes (e.g., with base stations and/or core network nodes). The SMF may also include at least one processor circuit 903 (also referred to as a processor) coupled to the network interface, and at least one memory circuit 905 (also referred to as memory) coupled to the processor. The memory 905 may include computer readable program code that when executed by the processor 903 causes the processor to perform operations according to embodiments disclosed herein. According to other embodiments, processor 903 may be defined to include memory so that a separate memory circuit is not required.

[0059] As discussed herein, operations of the SMF may be performed by processor 903 and/or network interface 907. Modules may be stored in memory 905, and these modules may provide instructions so that when instructions of a module are executed by processor 903, processor 903 performs respective operations (e.g., operations discussed below with respect to Example Embodiments).

[0060] In some embodiments, the AMF and SMF may share one or more components.

For example, operations of the AMF and SMF may be performed by one or more shared processors. The processors may be included in one or more core nodes.

[0061 ] NWDAF as a central function can become a complex point for processing. For example, as a central function, NWDAF, can cause raw data to be sent up stream from several NF instances of various types. The raw data can be used for analytics treatment, training, and processing and can extensive effort may be exerted to determine patterns and insights for use by network analytics. In 3GPP Rel. 15, only one insight is provided by the NWDAF, but future releases may define new insights corresponding with new use cases. The new use cases can demand near real-time data being available to support the processing of the analytical information. This can put real-time streaming requirements on the sources producing the input to the NWDAF or real-time data may be sent together with the request. Not all consumers that send a request may have near real-time data. [0062] In some examples, transferring and collecting raw input data from the source

NFs to the central NWDAF may cause a significant impact in terms of processing and/or network bandwidth even if the sources have real-time capabilities. For example, processing and/or network bandwidth can be impacted if the input data to elaborate certain analytic insight comes from a single NF that is also the receiver/consumer of the analytic insights.

[0063] In some embodiments of the present disclosure, mechanisms are provided to distribute the analytics or at least parts of the analytics. In some embodiments, the NWDAF is distributed into decentralized instances. These instances can then either be co -located with other NFs or part of other NFs. In some examples, these mechanisms can include re-using the NWDA service to expose the analytical information to consumers. If Rel. 16 follows Rel. 15 then the parameter Analyticld can be used to distinguish what analytical information the requesting consumer wants. To find the NWDA service instance that processes the specific Analyticld and at the same time supports the targeted session, NRF can use the Analyticld, to point out the instance. In some examples, these mechanisms can require the possibility to extend the NWDAF to multiple instances. In Rel. 15 it is only one service in one central instance.

[0064] In additional or alternative embodiments, the analytics can be distributed as pure internal analytics in other NFs. In some examples, the NFs can generate internally the analytics result (with the input data already available in the NF) and expose them to other NFs with a new service/s similar to the ones already provided by the NWDAF, e.g.

Namf Analytics info. It would be something similar to existing event exposure provided by NFs but just used for analytics information instead of network events. An example of that option might be the AMF that generates internally mobility patterns for the subscribers handled by that AMF. The AMF uses the subscriber location information (also historical) available in the node to generate the pattern, so no input data are transferred to generate the analytics information. But one could also re-use the Event Exposure mechanism and add analytical information to be exposed to consumers. In some examples, these mechanisms can require the possibility to export the internal analytical information from the NF to other consuming NFs.

[0065] Distributing the processing of analytics close to where the raw data is produced, can lower the amount of raw data transportation and analytical information transportation. The distribution of analytics specifically well addresses the type of analytics limited in utilizing raw offline data produced by the NF, in which it is tended to be executed. The distribution can also prevent introducing delays in the analytics production process and create a more even architecture in the sense of network resource demands in analytics production. The locally produced analytical information in the NFs can be exposed to analytics consumers like NFs, NSSF and central NWDAF.

[0066] Distributing the analytics can reduce data transportation, introduce near real time data, lower processing performed in a central location, and allow operators to produce leverage and share analytics among NFs in a more efficient process with a decentralized analytics processing structure.

[0067] FIG. 3 depicts an example of a NWDAF distributed into decentralized instances.

In some examples the NWDAF can be included in or co-located with NFs. Some embodiments provide that the decentralized instances of the NWDAF may be run in the same data center and/or across multiple data centers. Some embodiments provide that the core network functions may run in virtualized environments in data centers. The NF consumer can find the instance of the NWDA service that supports the specific session and handle the analytics for a specific Analyticld. For example, the NF consumer can ask the NRF. Each NWDAF instance can register in the NRF including information about the Analyticlds supported and NF consumers can query NRF for NWDAF service supporting one (or a set of) Analyticld. NRF can use the AnalyticID to resolve which NWDAF instance. If the NF consumer is the same NF as the analytical instance then the procedure above may not be performed. Analytics can produce basic analytical information based on NF logical events (historical (offline) event data and potential near real-time event (online) data). In some examples, if near real-time data is needed and is not available in request nor in Analytics instance, Analytics can send a request for real-time data to NF logic.

[0068] FIG. 4 depicts analytics distributed as pure internal analytics in other NFs. The

NF consumer can know the NF that provides each specific analytics in a similar way that any NF can find the NF that has the service that supports the specific session. For example, the NF consumer can query the NRF. For the case of mobility patterns generated by the AMF, a NF consumer interested in the mobility patterns for a subscriber can address the AMF currently handling that subscriber. If the consumer is the same NF as the analytical instance then the procedure above may not be performed. If near real-time data is needed NF logic can add the real-time data to the internal request. Analytics can produce basic analytical information based on NF logical events (historical (offline) event data and near real-time event (online) data).

[0069] NWDA service can be exposed to consumers using the Event Exposure, in an

NF_EventExposure_Subscribe_Notify operation. As an example, the request/subscribe can contain a number indicating for how long a time from now the response/notify shall contain data and a pattern can be given from now to an indicated time.

[0070] In additional or alternative embodiments, offline data can be collected (from any

NF or other sources) and/or distributed Analytics produced analytical information, to for instance produce more advanced analytical information reports, where for instance data originating from different types of sources are needed. NWDAF can exchange analytics by using the

Subscribe/Notify or Request/Response service.

[0071 ] Operations of a communication node will now be discussed with reference to the flow chart of FIG. 7. For example, module may be stored in AMF memory 805 of FIG. 8 and these modules may provide instructions so that when the instructions of a module are executed by processor 803, processor 803 performs respective operations of the flow chart of FIG. 7. Although FIG. 7 is described below in relation to the AMF depicted in FIG. 8, the process could be executed by any node in a 5G network, for example, the UE depicted in FIG. 5, the eNodeB depicted in FIG. 6, or the SMF depicted in FIG. 9.

[0072] FIG. 7 depicts an example of AMF operations according to some embodiments.

At block 705, processor 803 provides a network data analytics function. The network data analytics function can be configured to collect on-line and/or offline data from a source network function and to generate analytical information for a consumer network function. At block 710, processor 803 generates an instance of the network data analytics functions. The instance of the network data analytics function can correspond to the source network function and that can be configured to provide near real-time analytics data corresponding to the source network function to the consumer network function.

[0073] At block 715, processor 803 registers the instance of the network data analytics function. The instance of the network data analytics function can be registered in a network function repository function that is configured to receive a query from the consumer network function requesting service to support an analytic identifier and to use the analytic identifier to resolve which instance of the network data analytics function corresponds to the query. In additional or alternative embodiments, the instance of the network data analytics function can be co-located with the source network function.

[0074] At block 720, processor 803 generates analytical information. In some examples, the network data analytics function can be configured to generate analytical information based on network function logical events corresponding to the source network function. In additional or alternative examples, the instance of the network data analytics function can be configured to generate analytical information based on historical event data that is provided from offline sources. In additional or alternative examples, the network data analytics function can be configured to generate analytical information based on near real-time data that is provided from online sources.

[0075] At block 725, processor 803 sends through network interface 807 a request for near real-time data. The request for near real-time data can be sent to the source network function responsive to determining that the near real-time data is an input for the network data analytics function.

[0076] At block 730, processor 803 receives through network interface 807 a

subscription request. The subscription request can be received from the consumer network function and can include a network instance identifier, a periodicity value corresponding to notification frequency, and/or a load level threshold value corresponding to a threshold based notification. At block 735, processor 803 sends through network interface 807 a confirmation of the subscription. The confirmation of the subscription can be sent to the consumer network function in response to receiving the subscription request.

[0077] At block 740, processor 803 receives through network interface 807 an unsubscribe request. The unsubscribe request can be received from the consumer network function and can include the network instance identifier, the periodicity value corresponding to notification frequency, and/or the load level threshold value corresponding to the threshold based notification. At block 745, processor 803 sends through network interface 807 a confirmation of unsubscription. The confirmation of the unsubscription can be sent to the consumer network function in response to receiving the unsubscribe request.

[0078] At block 750, processor 803 sends through network interface 807 a notification based on the periodicity value and/or the load level threshold value. The notification can be sent to the consumer network function in response to an event being generated based on the periodicity value and/or the load level threshold value. At block 755, processor 803 receives through network interface 807 a request for network function operator specific analytical information. The request can be received from the consumer network function for network function operator specific analytical information. In additional or alternative embodiments, the network data analytics function can include a decentralizing network data analytics function that includes a plurality of instances of network data analytics functions that correspond to a plurality of source network functions.

[0079] The network data analytics function can be configured to operate internal to the source network function to generate the analytical information. At block 760, processor 803 receives through network interface 807 a subscription request. The subscription request can be received from the consumer network function. At block 765, processor 803 receives through network interface 807 a notification based on the analytical information. The notification can be sent to the consumer network function and can be based on the analytical information.

[0080] Various operations from the flow chart of FIG. 7 may be optional with respect to some embodiments and related methods. Regarding methods of example embodiments 1 and 17 (set forth below), for example, operations of blocks 715, 720, 725, 730, 735, 740, 745, 750, 755, 760, and 765 of FIG. 7 may be optional. Additionally, the order of operations corresponding to blocks 715, 720, 725, 730, 735, 740, 745, 750, 755, 760, and 765 of FIG. 7 is merely an example order. As such, the operations corresponding to blocks 715, 720, 725, 730, 735, 740, 745, 750, 755, 760, and 765 of FIG. 7 may be performed in different orders other than what is illustrated.

[0081 ] In some embodiments, a first communication node can include a memory and a processor coupled to the memory and configured to perform operations. The operations can include providing a network data analytics function that is configured to collect on-line and/or offline data from a source network function and to generate analytical information for a consumer network function. The operations can further include generating an instance of the network data analytics function that corresponds to the source network function and that is configured to provide near real-time analytics data corresponding to the source network function to the consumer network function.

[0082] LISTING OF EXAMPLE EMBODIMENTS [0083] Example Embodiments are discussed below. Reference numbers/letters are provided in parenthesis by way of example/illustration without limiting example embodiments to particular elements indicated by reference numbers/letters.

1. A method of providing distributed analytics to network functions, the method comprising:

providing (705) a network data analytics function that is configured to collect on-line and/or offline data from a source network function and to generate analytical information for a consumer network function; and

generating (710) an instance of the network data analytics function that corresponds to the source network function and that is configured to provide near real-time analytics data corresponding to the source network function to the consumer network function.

2. The method of Embodiment 1, further comprising registering (715) the instance of the network data analytics function in a network function repository function that is configured to receive a query from the consumer network function requesting service to support an analytic identifier and to use the analytic identifier to resolve which instance of the network data analytics function corresponds to the query.

3. The method of Embodiments 1-2, wherein the instance of the network data analytics function is co-located with the source network function.

4. The method of Embodiments 1-3, wherein the instance of the network data analytics function is configured to generate (720) analytical information based on network function logical events corresponding to the source network function and/or data from other sources and/or network functions.

5. The method of Embodiments 1-4, wherein the instance of the network data analytics function is configured to generate (720) analytical information based on historical event data that is provided from offline sources. 6. The method of Embodiments 1-5, wherein the instance of the network data analytics function is configured to generate (720) analytical information based on near real-time data that is provided from online sources.

7. The method of Embodiments 1-6, wherein the instance of the network data analytics function is configured to send (725) a request for near real-time data to the source network function responsive to determining that the near real-time data is an input for the network data analytics function.

8. The method of Embodiments 1-7, wherein the instance of the network data analytics function is configured to receive (730) a subscription request from the consumer network function that includes a network instance identifier, a periodicity value corresponding to notification frequency and/or a level threshold value corresponding to a threshold based notification, and

wherein, responsive to receiving the subscription request, the instance of the network data analytics function is further configured to send (735) a confirmation of the subscription to the consumer network function.

9. The method of Embodiment 8, wherein the instance of the network data analytics function is configured to receive (740) an unsubscribe request from the consumer network function that includes the network instance identifier, the periodicity value corresponding to notification frequency and/or the level threshold value corresponding to the threshold based notification, and

wherein, responsive to receiving the unsubscribe request, the instance of the network data analytics function is further configured to send (745) a confirmation of unsubscription to the consumer network function.

10. The method of Embodiments 8-9, wherein the instance of the network data analytics function is configured to send (750) a notification to the consumer network function responsive to an event that is generated based on the periodicity value and/or the level threshold value. 11. The method of Embodiments 1-7, wherein the instance of the network data analytics function is configured to receive a request (755) from the consumer network function for network function operator specific analytical information.

12. The method of Embodiment 1, wherein the network data analytics function comprises a decentralizing network data analytics function that includes a plurality of instances of network data analytics functions that correspond to a plurality of source network functions.

13. The method of Embodiments 1-12, wherein the network data analytics function is configured to operate internal to the source network function to generate the analytical information, and

wherein the source network function receives (760) a subscription request from the consumer network function and sends (765) a notification to the consumer network function, the notification being based on the analytical information.

14. A first communication node comprising:

a memory; and

a processor coupled to the memory and configured to perform operations comprising: providing a network data analytics function that is configured to collect on-line and/or offline data from a source network function and to generate analytical information for a consumer network function; and

generating an instance of the network data analytics function that corresponds to the source network function and that is configured to provide near real-time analytics data corresponding to the source network function to the consumer network function.

15. The first communication node of Embodiment 14, wherein the processor is adapted to perform operations according to any of Embodiments 2-13.

16. A core network node, wherein the first core network node includes respective modules adapted to perform according to any of Embodiments 1-13. 17. A method of operating a first communication node, the method comprising:

providing (705) a network data analytics function that is configured to collect on-line and/or offline data from a source network function and to generate analytical information for a consumer network function; and

generating (710) an instance of an analytics function that is part of the source network function and that is configured to provide near real-time analytics data corresponding to the source network function to the consumer network function.

18. The method of Embodiment 17, further comprising registering (715) the instance of the analytics function in a network function repository function that is configured to receive a query from the consumer network function requesting service to support an analytic identifier and to use the analytic identifier to resolve which instance or service part of the analytics function corresponds to the query,

wherein if the registering is performed as a service of the corresponding source network function, then the query and a response thereto is part of a notify operation.

19. The method of Embodiments 17-18, wherein the instance of the network data analytics function is co-located with and/or internal to the source network function.

20. The method of Embodiments 17-19, wherein the instance of the network data analytics function is configured to generate (720) analytical information based on network function logical events corresponding to the source network function and/or events and/or data from other data sources and/or network functions.

21. The method of Embodiments 17-20, wherein the instance of the network data analytics function is configured to generate (720) analytical information based on historical event data that is provided from offline sources. 22. The method of Embodiments 17-21, wherein the instance of the network data analytics function is configured to generate (720) analytical information based on near real-time data that is provided from online sources.

23. The method of Embodiments 17-22, wherein the instance of the network data analytics function is configured to send (725) an internal request for near real-time data to the source network function responsive to determining that the near real-time data is an input for the network data analytics function, wherein the internal request is from the source network function.

24. The method of Embodiments 17-24, wherein the instance of the network data analytics function is configured to receive (730) a subscription request from the consumer network function that includes a network instance identifier, a periodicity value corresponding to notification frequency and/or a level threshold value corresponding to a threshold based notification, and

wherein, responsive to receiving the subscription request, the instance of the network data analytics function is further configured to send (735) a confirmation of the subscription to the consumer network function.

25. The method of Embodiment 24, wherein the instance of the network data analytics function is configured to receive (740) an unsubscribe request from the consumer network function that includes the network instance identifier, the periodicity value

corresponding to notification frequency and/or the level threshold value corresponding to the threshold based notification, and

wherein, responsive to receiving the unsubscribe request, the instance of the network data analytics function is further configured to send (745) a confirmation of unsubscription to the consumer network function.

26. The method of Embodiments 24-25, wherein the instance of the network data analytics function is configured to send (750) a notification to the consumer network function responsive to an event that is generated based on the periodicity value and/or the level threshold value.

27. The method of Embodiments 17-24, wherein the instance of the network data analytics function is configured to receive (755) a request from the consumer network function for network function operator specific analytical information.

28. The method of Embodiment 17, wherein the network data analytics function comprises a decentralizing network data analytics function that includes a plurality of instances of network data analytics functions that correspond to a plurality of source network functions.

29. The method of Embodiments 17-28, wherein the network data analytics function is configured to operate internal to the source network function to generate the analytical information, and

wherein the source network function receives (760) a subscription request from the consumer network function and sends (765) a notification to the consumer network function, the notification being based on the analytical information.

[0084] Explanations for abbreviations from the above disclosure are provided below.

Abbreviation Explanation

3 GPP 3 rd Generation Partnership Project

5G 5 th Generation Wireless Systems

NG Next Generation

IoT Internet of Things

AKA Authentication and Key Agreement

UICC Universal Integrated Circuit Card

SA2 3 GPP architecture working group

SA3 3 GPP security group

UP User Plane

LTE Long Term Evolution (4 th Generation Wireless System)

CP Control Plane AS Access Stratum

eNB Evolved Node B

UE User Equipment or End User Device

SMC Security Mode Command

RRC Radio Resource Control

PDCP Packet Data Convergence Protocol

RAN Radio Access Network

CN Core Network

PDU Packet Data Unit

DRB Data Radio Bearer

AN Access Network

(R)AN Both 3 GPP and non-3GPP Access Networks

NAS Network Access Stratum

AMF Access and Mobility Management Function

NF Network Function

UDM Unified Data Management

PCF Policy Control Function

DRB-IP Data Radio Bearer Integrity Protected

IE Information Element

QoS Quality of Service

gNB Base Station in 5G

NEF Network Exposure Function

NWDAF Network Data Analytics Function

PCF Policy Control Function

UDM Unified Data Management

UPF User Plane Function

[0085] Citations for references from the above disclosure are provided below.

[0086] Reference [1]: 3GPP TS 23.501 VI 5.1.0 (2018-03), Technical Specification

Group Services and System Aspects; System Architecture for the 5G System; Stage 2 (Release 15) Reference [3]: TS 23.502

Reference [6]: TS 23.503

[0087] Further definitions and embodiments are discussed below.

[0088] In the above-description of various embodiments of present inventive concepts, it is to be understood that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of present inventive concepts. Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which present inventive concepts belong. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

[0089] When an element is referred to as being "connected", "coupled", "responsive", or variants thereof to another element, it can be directly connected, coupled, or responsive to the other element or intervening elements may be present. In contrast, when an element is referred to as being "directly connected", "directly coupled", "directly responsive", or variants thereof to another element, there are no intervening elements present. Like numbers refer to like elements throughout. Furthermore, "coupled", "connected", "responsive", or variants thereof as used herein may include wirelessly coupled, connected, or responsive. As used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. Well-known functions or constructions may not be described in detail for brevity and/or clarity. The term "and/or" includes any and all combinations of one or more of the associated listed items.

[0090] It will be understood that although the terms first, second, third, etc. may be used herein to describe various elements/operations, these elements/operations should not be limited by these terms. These terms are only used to distinguish one element/operation from another element/operation. Thus, a first element/operation in some embodiments could be termed a second element/operation in other embodiments without departing from the teachings of present inventive concepts. The same reference numerals or the same reference designators denote the same or similar elements throughout the specification. [0091 ] As used herein, the terms "comprise", "comprising", "comprises", "include",

"including", "includes", "have", "has", "having", or variants thereof are open-ended, and include one or more stated features, integers, elements, steps, components, or functions but does not preclude the presence or addition of one or more other features, integers, elements, steps, components, functions, or groups thereof. Furthermore, as used herein, the common

abbreviation "e.g.", which derives from the Latin phrase "exempli gratia," may be used to introduce or specify a general example or examples of a previously mentioned item, and is not intended to be limiting of such item. The common abbreviation "i.e.", which derives from the Latin phrase "id est," may be used to specify a particular item from a more general recitation.

[0092] Example embodiments are described herein with reference to block diagrams and/or flowchart illustrations of computer-implemented methods, apparatus (systems and/or devices) and/or computer program products. It is understood that a block of the block diagrams and/or flowchart illustrations, and combinations of blocks in the block diagrams and/or flowchart illustrations, can be implemented by computer program instructions that are performed by one or more computer circuits. These computer program instructions may be provided to a processor circuit of a general purpose computer circuit, special purpose computer circuit, and/or other programmable data processing circuit to produce a machine, such that the instructions, which execute via the processor of the computer and/or other programmable data processing apparatus, transform and control transistors, values stored in memory locations, and other hardware components within such circuitry to implement the functions/acts specified in the block diagrams and/or flowchart block or blocks, and thereby create means (functionality) and/or structure for implementing the functions/acts specified in the block diagrams and/or flowchart block(s).

[0093] These computer program instructions may also be stored in a tangible computer- readable medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable medium produce an article of manufacture including instructions which implement the functions/acts specified in the block diagrams and/or flowchart block or blocks. Accordingly, embodiments of present inventive concepts may be embodied in hardware and/or in software (including firmware, resident software, micro-code, etc.) that runs on a processor such as a digital signal processor, which may collectively be referred to as "circuitry," "a module" or variants thereof. [0094] It should also be noted that in some alternate implementations, the functions/acts noted in the blocks may occur out of the order noted in the flowcharts. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality/acts involved. Moreover, the functionality of a given block of the flowcharts and/or block diagrams may be separated into multiple blocks and/or the functionality of two or more blocks of the flowcharts and/or block diagrams may be at least partially integrated. Finally, other blocks may be added/inserted between the blocks that are illustrated, and/or blocks/operations may be omitted without departing from the scope of inventive concepts. Moreover, although some of the diagrams include arrows on communication paths to show a primary direction of

communication, it is to be understood that communication may occur in the opposite direction to the depicted arrows.

[0095] Many variations and modifications can be made to the embodiments without substantially departing from the principles of the present inventive concepts. All such variations and modifications are intended to be included herein within the scope of present inventive concepts. Accordingly, the above disclosed subject matter is to be considered illustrative, and not restrictive, and the examples of embodiments are intended to cover all such modifications, enhancements, and other embodiments, which fall within the spirit and scope of present inventive concepts. Thus, to the maximum extent allowed by law, the scope of present inventive concepts are to be determined by the broadest permissible interpretation of the present disclosure including the examples of embodiments and their equivalents, and shall not be restricted or limited by the foregoing detailed description.

[0096] Additional explanation is provided below.

[0097] Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and/or is implied from the context in which it is used. All references to a/an/the element, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and/or where it is implicit that a step must follow or precede another step. Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments may apply to any other embodiments, and vice versa.

Other objectives, features and advantages of the enclosed embodiments will be apparent from the following description.

[0098] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Other embodiments, however, are contained within the scope of the subject matter disclosed herein, the disclosed subject matter should not be construed as limited to only the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0099] Figure QQ 1 : A wireless network in accordance with some embodiments.

[00100] Although the subject matter described herein may be implemented in any appropriate type of system using any suitable components, the embodiments disclosed herein are described in relation to a wireless network, such as the example wireless network illustrated in Figure QQ1. For simplicity, the wireless network of Figure QQ1 only depicts network QQ106, network nodes QQ160 and QQl60b, and WDs QQ110, QQ1 lOb, and QQ1 lOc (also referred to as mobile terminals). In practice, a wireless network may further include any additional elements suitable to support communication between wireless devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or end device. Of the illustrated components, network node QQ160 and wireless device (WD) QQ110 are depicted with additional detail. The wireless network may provide communication and other types of services to one or more wireless devices to facilitate the wireless devices’ access to and/or use of the services provided by, or via, the wireless network.

[00101 ] The wireless network may comprise and/or interface with any type of

communication, telecommunication, data, cellular, and/or radio network or other similar type of system. In some embodiments, the wireless network may be configured to operate according to specific standards or other types of predefined rules or procedures. Thus, particular

embodiments of the wireless network may implement communication standards, such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and/or other suitable 2G, 3G, 4G, or 5G standards; wireless local area network (WLAN) standards, such as the IEEE 802.11 standards; and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave and/or ZigBee standards.

[00102] Network QQ106 may comprise one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTNs), packet data networks, optical networks, wide-area networks (WANs), local area networks (LANs), wireless local area networks

(WLANs), wired networks, wireless networks, metropolitan area networks, and other networks to enable communication between devices.

[00103] Network node QQ160 and WD QQ110 comprise various components described in more detail below. These components work together in order to provide network node and/or wireless device functionality, such as providing wireless connections in a wireless network. In different embodiments, the wireless network may comprise any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections.

[00104] As used herein, network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a wireless device and/or with other network nodes or equipment in the wireless network to enable and/or provide wireless access to the wireless device and/or to perform other functions (e.g., administration) in the wireless network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)). Although described herein in the context of network nodes, operations and structures described herein may be application to core network nodes. Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and may then also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS). Yet further examples of network nodes include multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs), core network nodes (e.g., MSCs, MMEs), O&M nodes, OSS nodes, SON nodes, positioning nodes (e.g., E-SMLCs), and/or MDTs. As another example, a network node may be a virtual network node as described in more detail below. More generally, however, network nodes may represent any suitable device (or group of devices) capable, configured, arranged, and/or operable to enable and/or provide a wireless device with access to the wireless network or to provide some service to a wireless device that has accessed the wireless network.

[00105] In Figure QQ1, network node QQ160 includes processing circuitry QQ170, device readable medium QQ180, interface QQ190, auxiliary equipment QQ184, power source QQ186, power circuitry QQ187, and antenna QQ162. Although network node QQ160 illustrated in the example wireless network of Figure QQ1 may represent a device that includes the illustrated combination of hardware components, other embodiments may comprise network nodes with different combinations of components. It is to be understood that a network node comprises any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein. Moreover, while the components of network node QQ160 are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, a network node may comprise multiple different physical components that make up a single illustrated component (e.g., device readable medium QQ180 may comprise multiple separate hard drives as well as multiple RAM modules).

[00106] Similarly, network node QQ160 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which network node QQ160 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeB’s. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, network node QQ160 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate device readable medium QQ180 for the different RATs) and some components may be reused (e.g., the same antenna QQ162 may be shared by the RATs). Network node QQ160 may also include multiple sets of the various illustrated components for different wireless

technologies integrated into network node QQ160, such as, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node QQ160.

[00107] Processing circuitry QQ170 is configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being provided by a network node. These operations performed by processing circuitry QQ170 may include processing information obtained by processing circuitry QQ170 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.

[00108] Processing circuitry QQ170 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node QQ160 components, such as device readable medium QQ180, network node QQ160 functionality. For example, processing circuitry QQ170 may execute instructions stored in device readable medium QQ180 or in memory within processing circuitry QQ170. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, processing circuitry QQ170 may include a system on a chip (SOC).

[00109] In some embodiments, processing circuitry QQ170 may include one or more of radio frequency (RF) transceiver circuitry QQ172 and baseband processing circuitry QQ174. In some embodiments, radio frequency (RF) transceiver circuitry QQ172 and baseband processing circuitry QQ174 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry QQ172 and baseband processing circuitry QQ174 may be on the same chip or set of chips, boards, or units. [001 10] In certain embodiments, some or all of the functionality described herein as being provided by a network node, base station, eNB or other such network device may be performed by processing circuitry QQ170 executing instructions stored on device readable medium QQ180 or memory within processing circuitry QQ170. In alternative embodiments, some or all of the functionality may be provided by processing circuitry QQ170 without executing instructions stored on a separate or discrete device readable medium, such as in a hard-wired manner. In any of those embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry QQ170 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry QQ170 alone or to other components of network node QQ160, but are enjoyed by network node QQ160 as a whole, and/or by end users and the wireless network generally.

[001 1 1 ] Device readable medium QQ180 may comprise any form of volatile or non volatile computer readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computer- executable memory devices that store information, data, and/or instructions that may be used by processing circuitry QQ170. Device readable medium QQ180 may store any suitable

instructions, data or information, including a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry QQ170 and, utilized by network node QQ160. Device readable medium QQ180 may be used to store any calculations made by processing circuitry QQ170 and/or any data received via interface QQ190. In some embodiments, processing circuitry QQ170 and device readable medium QQ180 may be considered to be integrated.

[001 12] Interface QQ190 is used in the wired or wireless communication of signalling and/or data between network node QQ160, network QQ106, and/or WDs QQ110. As illustrated, interface QQ190 comprises port(s)/terminal(s) QQ194 to send and receive data, for example to and from network QQ106 over a wired connection. Interface QQ190 also includes radio front end circuitry QQ192 that may be coupled to, or in certain embodiments a part of, antenna QQ162. Radio front end circuitry QQ192 comprises filters QQ198 and amplifiers QQ196. Radio front end circuitry QQ192 may be connected to antenna QQ162 and processing circuitry QQ170. Radio front end circuitry may be configured to condition signals communicated between antenna QQ162 and processing circuitry QQ170. Radio front end circuitry QQ192 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry QQ192 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters QQ198 and/or amplifiers QQ196. The radio signal may then be transmitted via antenna QQ162.

Similarly, when receiving data, antenna QQ162 may collect radio signals which are then converted into digital data by radio front end circuitry QQ192. The digital data may be passed to processing circuitry QQ170. In other embodiments, the interface may comprise different components and/or different combinations of components.

[001 13] In certain alternative embodiments, network node QQ160 may not include separate radio front end circuitry QQ192, instead, processing circuitry QQ170 may comprise radio front end circuitry and may be connected to antenna QQ162 without separate radio front end circuitry QQ192. Similarly, in some embodiments, all or some of RF transceiver circuitry QQ172 may be considered a part of interface QQ190. In still other embodiments, interface QQ190 may include one or more ports or terminals QQ194, radio front end circuitry QQ192, and RF transceiver circuitry QQ172, as part of a radio unit (not shown), and interface QQ190 may communicate with baseband processing circuitry QQ174, which is part of a digital unit (not shown).

[001 14] Antenna QQ162 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. Antenna QQ162 may be coupled to radio front end circuitry QQ190 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In some embodiments, antenna QQ162 may comprise one or more omni-directional, sector or panel antennas operable to transmit/receive radio signals between, for example, 2 GHz and 66 GHz. An omni-directional antenna may be used to transmit/receive radio signals in any direction, a sector antenna may be used to transmit/receive radio signals from devices within a particular area, and a panel antenna may be a line of sight antenna used to transmit/receive radio signals in a relatively straight line. In some instances, the use of more than one antenna may be referred to as MIMO. In certain embodiments, antenna QQ162 may be separate from network node QQ160 and may be connectable to network node QQ160 through an interface or port.

[001 15] Antenna QQ162, interface QQ190, and/or processing circuitry QQ170 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by a network node. Any information, data and/or signals may be received from a wireless device, another network node and/or any other network equipment. Similarly, antenna QQ162, interface QQ190, and/or processing circuitry QQ170 may be configured to perform any transmitting operations described herein as being performed by a network node. Any information, data and/or signals may be transmitted to a wireless device, another network node and/or any other network equipment.

[001 16] Power circuitry QQ187 may comprise, or be coupled to, power management circuitry and is configured to supply the components of network node QQ160 with power for performing the functionality described herein. Power circuitry QQ187 may receive power from power source QQ186. Power source QQ186 and/or power circuitry QQ187 may be configured to provide power to the various components of network node QQ160 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source QQ186 may either be included in, or external to, power circuitry QQ187 and/or network node QQ160. For example, network node QQ160 may be connectable to an external power source (e.g., an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry QQ187.

As a further example, power source QQ186 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry QQ187. The battery may provide backup power should the external power source fail. Other types of power sources, such as photovoltaic devices, may also be used.

[001 17] Alternative embodiments of network node QQ160 may include additional components beyond those shown in Figure QQ1 that may be responsible for providing certain aspects of the network node’s functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein. For example, network node QQ160 may include user interface equipment to allow input of information into network node QQ160 and to allow output of information from network node QQ160. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for network node QQ160.

[001 18] As used herein, wireless device (WD) refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other wireless devices. Unless otherwise noted, the term WD may be used interchangeably herein with user equipment (UE). Communicating wirelessly may involve transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information through air. In some embodiments, a WD may be configured to transmit and/or receive information without direct human interaction. For instance, a WD may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the network. Examples of a WD include, but are not limited to, a smart phone, a mobile phone, a cell phone, a voice over IP (VoIP) phone, a wireless local loop phone, a desktop computer, a personal digital assistant (PDA), a wireless cameras, a gaming console or device, a music storage device, a playback appliance, a wearable terminal device, a wireless endpoint, a mobile station, a tablet, a laptop, a laptop-embedded equipment (LEE), a laptop-mounted equipment (LME), a smart device, a wireless customer-premise equipment (CPE) a vehicle -mounted wireless terminal device, etc. A WD may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, vehicle-to-vehicle (V2V), vehicle- to-inffastructure (V2I), vehicle -to-everything (V2X) and may in this case be referred to as a D2D communication device. As yet another specific example, in an Internet of Things (IoT) scenario, a WD may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another WD and/or a network node. The WD may in this case be a machine -to-machine (M2M) device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the WD may be a UE implementing the 3GPP narrow band internet of things (NB-IoT) standard. Particular examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances (e.g. refrigerators, televisions, etc.) personal wearables (e.g., watches, fitness trackers, etc.). In other scenarios, a WD may represent a vehicle or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation. A WD as described above may represent the endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal. Furthermore, a WD as described above may be mobile, in which case it may also be referred to as a mobile device or a mobile terminal.

[001 19] As illustrated, wireless device QQ110 includes antenna QQ111, interface QQ114, processing circuitry QQ120, device readable medium QQ130, user interface equipment QQ132, auxiliary equipment QQ134, power source QQ136 and power circuitry QQ137. WD QQ110 may include multiple sets of one or more of the illustrated components for different wireless technologies supported by WD QQ110, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, just to mention a few. These wireless technologies may be integrated into the same or different chips or set of chips as other components within WD QQ110.

[00120] Antenna QQ111 may include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface QQ114. In certain alternative embodiments, antenna QQ111 may be separate from WD QQ110 and be connectable to WD QQ110 through an interface or port. Antenna QQ111, interface QQ114, and/or processing circuitry QQ120 may be configured to perform any receiving or transmitting operations described herein as being performed by a WD. Any information, data and/or signals may be received from a network node and/or another WD. In some embodiments, radio front end circuitry and/or antenna QQ111 may be considered an interface.

[00121 ] As illustrated, interface QQ114 comprises radio front end circuitry QQ112 and antenna QQ111. Radio front end circuitry QQ112 comprise one or more filters QQ118 and amplifiers QQ116. Radio front end circuitry QQ114 is connected to antenna QQ111 and processing circuitry QQ120, and is configured to condition signals communicated between antenna QQ111 and processing circuitry QQ120. Radio front end circuitry QQ112 may be coupled to or a part of antenna QQ111. In some embodiments, WD QQ110 may not include separate radio front end circuitry QQ112; rather, processing circuitry QQ120 may comprise radio front end circuitry and may be connected to antenna QQ111. Similarly, in some embodiments, some or all of RF transceiver circuitry QQ122 may be considered a part of interface QQ114. Radio front end circuitry QQ112 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry QQ112 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters QQ118 and/or amplifiers QQ116. The radio signal may then be transmitted via antenna QQ111. Similarly, when receiving data, antenna QQ111 may collect radio signals which are then converted into digital data by radio front end circuitry QQ112. The digital data may be passed to processing circuitry QQ120. In other embodiments, the interface may comprise different components and/or different combinations of components.

[00122] Processing circuitry QQ120 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and/or encoded logic operable to provide, either alone or in conjunction with other WD QQ110 components, such as device readable medium QQ130, WD QQ110 functionality. Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, processing circuitry QQ120 may execute instructions stored in device readable medium QQ130 or in memory within processing circuitry QQ120 to provide the functionality disclosed herein.

[00123] As illustrated, processing circuitry QQ120 includes one or more of RF transceiver circuitry QQ122, baseband processing circuitry QQ124, and application processing circuitry QQ126. In other embodiments, the processing circuitry may comprise different components and/or different combinations of components. In certain embodiments processing circuitry QQ120 of WD QQ110 may comprise a SOC. In some embodiments, RF transceiver circuitry QQ122, baseband processing circuitry QQ124, and application processing circuitry QQ126 may be on separate chips or sets of chips. In alternative embodiments, part or all of baseband processing circuitry QQ124 and application processing circuitry QQ126 may be combined into one chip or set of chips, and RF transceiver circuitry QQ122 may be on a separate chip or set of chips. In still alternative embodiments, part or all of RF transceiver circuitry QQ122 and baseband processing circuitry QQ124 may be on the same chip or set of chips, and application processing circuitry QQ126 may be on a separate chip or set of chips. In yet other alternative embodiments, part or all of RF transceiver circuitry QQ122, baseband processing circuitry QQ124, and application processing circuitry QQ126 may be combined in the same chip or set of chips. In some embodiments, RF transceiver circuitry QQ122 may be a part of interface QQ114. RF transceiver circuitry QQ122 may condition RF signals for processing circuitry QQ120. [00124] In certain embodiments, some or all of the functionality described herein as being performed by a WD may be provided by processing circuitry QQ120 executing instructions stored on device readable medium QQ130, which in certain embodiments may be a computer- readable storage medium. In alternative embodiments, some or all of the functionality may be provided by processing circuitry QQ120 without executing instructions stored on a separate or discrete device readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry QQ120 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry QQ120 alone or to other components of WD QQ110, but are enjoyed by WD QQ110 as a whole, and/or by end users and the wireless network generally.

[00125] Processing circuitry QQ120 may be configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being performed by a WD. These operations, as performed by processing circuitry QQ120, may include processing information obtained by processing circuitry QQ120 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD QQ110, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.

[00126] Device readable medium QQ130 may be operable to store a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry QQ120. Device readable medium QQ130 may include computer memory (e.g., Random Access Memory (RAM) or Read Only Memory (ROM)), mass storage media (e.g., a hard disk), removable storage media (e.g., a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computer executable memory devices that store information, data, and/or instructions that may be used by processing circuitry QQ120. In some embodiments, processing circuitry QQ120 and device readable medium QQ130 may be considered to be integrated. User interface equipment QQ132 may provide components that allow for a human user to interact with WD QQ110. Such interaction may be of many forms, such as visual, audial, tactile, etc. User interface equipment QQ132 may be operable to produce output to the user and to allow the user to provide input to WD QQ110. The type of interaction may vary depending on the type of user interface equipment QQ132 installed in WD QQ110.

For example, if WD QQ110 is a smart phone, the interaction may be via a touch screen; if WD QQ110 is a smart meter, the interaction may be through a screen that provides usage (e.g., the number of gallons used) or a speaker that provides an audible alert (e.g., if smoke is detected). User interface equipment QQ132 may include input interfaces, devices and circuits, and output interfaces, devices and circuits. User interface equipment QQ132 is configured to allow input of information into WD QQ110, and is connected to processing circuitry QQ120 to allow processing circuitry QQ120 to process the input information. User interface equipment QQ132 may include, for example, a microphone, a proximity or other sensor, keys/buttons, a touch display, one or more cameras, a USB port, or other input circuitry. User interface equipment QQ132 is also configured to allow output of information from WD QQ110, and to allow processing circuitry QQ120 to output information from WD QQ110. User interface equipment QQ132 may include, for example, a speaker, a display, vibrating circuitry, a USB port, a headphone interface, or other output circuitry. Using one or more input and output interfaces, devices, and circuits, of user interface equipment QQ132, WD QQ110 may communicate with end users and/or the wireless network, and allow them to benefit from the functionality described herein.

[00127] Auxiliary equipment QQ134 is operable to provide more specific functionality which may not be generally performed by WDs. This may comprise specialized sensors for doing measurements for various purposes, interfaces for additional types of communication such as wired communications etc. The inclusion and type of components of auxiliary equipment QQ134 may vary depending on the embodiment and/or scenario.

[00128] Power source QQ136 may, in some embodiments, be in the form of a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic devices or power cells, may also be used. WD QQ110 may further comprise power circuitry QQ137 for delivering power from power source QQ136 to the various parts of WD QQ110 which need power from power source QQ136 to carry out any functionality described or indicated herein. Power circuitry QQ137 may in certain embodiments comprise power management circuitry. Power circuitry QQ137 may additionally or alternatively be operable to receive power from an external power source; in which case WD QQ110 may be connectable to the external power source (such as an electricity outlet) via input circuitry or an interface such as an electrical power cable. Power circuitry QQ137 may also in certain embodiments be operable to deliver power from an external power source to power source QQ136. This may be, for example, for the charging of power source QQ136. Power circuitry QQ137 may perform any formatting, converting, or other modification to the power from power source QQ136 to make the power suitable for the respective components of WD QQ110 to which power is supplied.

[00129] Figure QQ2: User Equipment in accordance with some embodiments

[00130] Figure QQ2 illustrates one embodiment of a UE in accordance with various aspects described herein. As used herein, a user equipment or UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter). UE QQ2200 may be any UE identified by the 3rd Generation Partnership Project (3GPP), including a NB-IoT UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE. UE QQ200, as illustrated in Figure QQ2, is one example of a WD configured for communication in accordance with one or more communication standards promulgated by the 3rd Generation Partnership Project (3GPP), such as 3GPP’s GSM, UMTS, LTE, and/or 5G standards. As mentioned previously, the term WD and UE may be used interchangeable. Accordingly, although Figure QQ2 is a UE, the components discussed herein are equally applicable to a WD, and vice-versa.

[00131 ] In Figure QQ2, UE QQ200 includes processing circuitry QQ201 that is operatively coupled to input/output interface QQ205, radio frequency (RF) interface QQ209, network connection interface QQ211, memory QQ215 including random access memory (RAM) QQ217, read-only memory (ROM) QQ219, and storage medium QQ221 or the like,

communication subsystem QQ231, power source QQ233, and/or any other component, or any combination thereof. Storage medium QQ221 includes operating system QQ223, application program QQ225, and data QQ227. In other embodiments, storage medium QQ221 may include other similar types of information. Certain UEs may utilize all of the components shown in Figure QQ2, or only a subset of the components. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[00132] In Figure QQ2, processing circuitry QQ201 may be configured to process computer instructions and data. Processing circuitry QQ201 may be configured to implement any sequential state machine operative to execute machine instructions stored as machine- readable computer programs in the memory, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logic together with appropriate firmware; one or more stored program, general-purpose processors, such as a microprocessor or Digital Signal Processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry QQ201 may include two central processing units (CPUs). Data may be information in a form suitable for use by a computer.

[00133] In the depicted embodiment, input/output interface QQ205 may be configured to provide a communication interface to an input device, output device, or input and output device. UE QQ200 may be configured to use an output device via input/output interface QQ205. An output device may use the same type of interface port as an input device. For example, a USB port may be used to provide input to and output from UE QQ200. The output device may be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. UE QQ200 may be configured to use an input device via input/output interface QQ205 to allow a user to capture information into UE QQ200. The input device may include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, another like sensor, or any combination thereof. For example, the input device may be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.

[00134] In Figure QQ2, RF interface QQ209 may be configured to provide a

communication interface to RF components such as a transmitter, a receiver, and an antenna. Network connection interface QQ211 may be configured to provide a communication interface to network QQ243a. Network QQ243a may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network QQ243a may comprise a Wi-Fi network. Network connection interface QQ211 may be configured to include a receiver and a transmitter interface used to communicate with one or more other devices over a communication network according to one or more communication protocols, such as Ethernet, TCP/IP, SONET, ATM, or the like. Network connection interface QQ211 may implement receiver and transmitter functionality appropriate to the communication network links (e.g., optical, electrical, and the like). The transmitter and receiver functions may share circuit components, software or firmware, or alternatively may be implemented separately.

[00135] RAM QQ217 may be configured to interface via bus QQ202 to processing circuitry QQ201 to provide storage or caching of data or computer instructions during the execution of software programs such as the operating system, application programs, and device drivers. ROM QQ219 may be configured to provide computer instructions or data to processing circuitry QQ201. For example, ROM QQ219 may be configured to store invariant low-level system code or data for basic system functions such as basic input and output (I/O), startup, or reception of keystrokes from a keyboard that are stored in a non-volatile memory. Storage medium QQ221 may be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, or flash drives. In one example, storage medium QQ221 may be configured to include operating system QQ223, application program QQ225 such as a web browser application, a widget or gadget engine or another application, and data file QQ227. Storage medium QQ221 may store, for use by UE QQ200, any of a variety of various operating systems or combinations of operating systems.

[00136] Storage medium QQ221 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), floppy disk drive, flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro- DIMM SDRAM, smartcard memory such as a subscriber identity module or a removable user identity (SIM/RUIM) module, other memory, or any combination thereof. Storage medium QQ221 may allow UE QQ200 to access computer-executable instructions, application programs or the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied in storage medium QQ221, which may comprise a device readable medium.

[00137] In Figure QQ2, processing circuitry QQ201 may be configured to communicate with network QQ243b using communication subsystem QQ231. Network QQ243a and network QQ243b may be the same network or networks or different network or networks.

Communication subsystem QQ231 may be configured to include one or more transceivers used to communicate with network QQ243b. For example, communication subsystem QQ231 may be configured to include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication such as another WD, UE, or base station of a radio access network (RAN) according to one or more communication protocols, such as IEEE 802.QQ2, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like. Each transceiver may include transmitter QQ233 and/or receiver QQ235 to implement transmitter or receiver functionality, respectively, appropriate to the RAN links (e.g., frequency allocations and the like). Further, transmitter QQ233 and receiver QQ235 of each transceiver may share circuit components, software or firmware, or alternatively may be implemented separately.

[00138] In the illustrated embodiment, the communication functions of communication subsystem QQ231 may include data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. For example, communication subsystem QQ231 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. Network QQ243b may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network QQ243b may be a cellular network, a Wi-Fi network, and/or a near-field network. Power source QQ213 may be configured to provide alternating current (AC) or direct current (DC) power to components of UE QQ200.

[00139] The features, benefits and/or functions described herein may be implemented in one of the components of UE QQ200 or partitioned across multiple components of UE QQ200. Further, the features, benefits, and/or functions described herein may be implemented in any combination of hardware, software or firmware. In one example, communication subsystem QQ231 may be configured to include any of the components described herein. Further, processing circuitry QQ201 may be configured to communicate with any of such components over bus QQ202. In another example, any of such components may be represented by program instructions stored in memory that when executed by processing circuitry QQ201 perform the corresponding functions described herein. In another example, the functionality of any of such components may be partitioned between processing circuitry QQ201 and communication subsystem QQ231. In another example, the non-computationally intensive functions of any of such components may be implemented in software or firmware and the computationally intensive functions may be implemented in hardware.

[00140] Figure QQ3: Virtualization environment in accordance with some embodiments [00141 ] Figure QQ3 is a schematic block diagram illustrating a virtualization environment QQ300 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to a node (e.g., a virtualized base station or a virtualized radio access node) or to a device (e.g., a UE, a wireless device or any other type of

communication device) or components thereof and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components (e.g., via one or more applications, components, functions, virtual machines or containers executing on one or more physical processing nodes in one or more networks).

[00142] In some embodiments, some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments QQ300 hosted by one or more of hardware nodes QQ330. Further, in embodiments in which the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node), then the network node may be entirely virtualized.

[00143] The functions may be implemented by one or more applications QQ320 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operative to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein. Applications QQ320 are run in virtualization environment QQ300 which provides hardware QQ330 comprising processing circuitry QQ360 and memory QQ390. Memory QQ390 contains instructions QQ395 executable by processing circuitry QQ360 whereby application QQ320 is operative to provide one or more of the features, benefits, and/or functions disclosed herein.

[00144] Virtualization environment QQ300, comprises general-purpose or special-purpose network hardware devices QQ330 comprising a set of one or more processors or processing circuitry QQ360, which may be commercial off-the-shelf (COTS) processors, dedicated

Application Specific Integrated Circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special purpose processors. Each hardware device may comprise memory QQ390-1 which may be non-persistent memory for temporarily storing instructions QQ395 or software executed by processing circuitry QQ360. Each hardware device may comprise one or more network interface controllers (NICs) QQ370, also known as network interface cards, which include physical network interface QQ380. Each hardware device may also include non-transitory, persistent, machine -readable storage media QQ390-2 having stored therein software QQ395 and/or instructions executable by processing circuitry QQ360. Software QQ395 may include any type of software including software for instantiating one or more virtualization layers QQ350 (also referred to as hypervisors), software to execute virtual machines QQ340 as well as software allowing it to execute functions, features and/or benefits described in relation with some embodiments described herein.

[00145] Virtual machines QQ340, comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer QQ350 or hypervisor. Different embodiments of the instance of virtual appliance QQ320 may be implemented on one or more of virtual machines QQ340, and the implementations may be made in different ways. [00146] During operation, processing circuitry QQ360 executes software QQ395 to instantiate the hypervisor or virtualization layer QQ350, which may sometimes be referred to as a virtual machine monitor (VMM). Virtualization layer QQ350 may present a virtual operating platform that appears like networking hardware to virtual machine QQ340.

[00147] As shown in Figure QQ3, hardware QQ330 may be a standalone network node with generic or specific components. Hardware QQ330 may comprise antenna QQ3225 and may implement some functions via virtualization. Alternatively, hardware QQ330 may be part of a larger cluster of hardware (e.g. such as in a data center or customer premise equipment (CPE)) where many hardware nodes work together and are managed via management and orchestration (MANO) QQ3100, which, among others, oversees lifecycle management of applications QQ320.

[00148] Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

[00149] In the context of NFV, virtual machine QQ340 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non- virtualized machine. Each of virtual machines QQ340, and that part of hardware QQ330 that executes that virtual machine, be it hardware dedicated to that virtual machine and/or hardware shared by that virtual machine with others of the virtual machines QQ340, forms a separate virtual network elements (VNE).

[00150] Still in the context of NFV, Virtual Network Function (VNF) is responsible for handling specific network functions that run in one or more virtual machines QQ340 on top of hardware networking infrastructure QQ330 and corresponds to application QQ320 in Figure QQ3.

[00151 ] In some embodiments, one or more radio units QQ3200 that each include one or more transmitters QQ3220 and one or more receivers QQ3210 may be coupled to one or more antennas QQ3225. Radio units QQ3200 may communicate directly with hardware nodes QQ330 via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. [00152] In some embodiments, some signalling can be effected with the use of control system QQ3230 which may alternatively be used for communication between the hardware nodes QQ330 and radio units QQ3200.

[00153] Figure QQ4: Telecommunication network connected via an intermediate network to a host computer in accordance with some embodiments.

[00154] With reference to FIGURE QQ4, in accordance with an embodiment, a communication system includes telecommunication network QQ410, such as a 3GPP-type cellular network, which comprises access network QQ411, such as a radio access network, and core network QQ414. Access network QQ411 comprises a plurality of base stations QQ4l2a, QQ4l2b, QQ4l2c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area QQ4l3a, QQ4l3b, QQ4l3c. Each base station QQ4l2a, QQ4l2b, QQ4l2c is connectable to core network QQ414 over a wired or wireless connection QQ415. A first UE QQ491 located in coverage area QQ4l3c is configured to wirelessly connect to, or be paged by, the corresponding base station QQ4l2c. A second UE QQ492 in coverage area QQ4l3a is wirelessly connectable to the corresponding base station QQ4l2a. While a plurality of UEs QQ491, QQ492 are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station QQ412.

[00155] Telecommunication network QQ410 is itself connected to host computer QQ430, which may be embodied in the hardware and/or software of a standalone server, a cloud- implemented server, a distributed server or as processing resources in a server farm. Host computer QQ430 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider. Connections QQ421 and QQ422 between telecommunication network QQ410 and host computer QQ430 may extend directly from core network QQ414 to host computer QQ430 or may go via an optional intermediate network QQ420. Intermediate network QQ420 may be one of, or a combination of more than one of, a public, private or hosted network; intermediate network QQ420, if any, may be a backbone network or the Internet; in particular, intermediate network QQ420 may comprise two or more sub-networks (not shown).

[00156] The communication system of Figure QQ4 as a whole enables connectivity between the connected UEs QQ491, QQ492 and host computer QQ430. The connectivity may be described as an over-the-top (OTT) connection QQ450. Host computer QQ430 and the connected UEs QQ491, QQ492 are configured to communicate data and/or signaling via OTT connection QQ450, using access network QQ411, core network QQ414, any intermediate network QQ420 and possible further infrastructure (not shown) as intermediaries. OTT connection QQ450 may be transparent in the sense that the participating communication devices through which OTT connection QQ450 passes are unaware of routing of uplink and downlink communications. For example, base station QQ412 may not or need not be informed about the past routing of an incoming downlink communication with data originating from host computer QQ430 to be forwarded (e.g., handed over) to a connected UE QQ491. Similarly, base station QQ412 need not be aware of the future routing of an outgoing uplink communication originating from the UE QQ491 towards the host computer QQ430.

[00157] Figure QQ5 : Host computer communicating via a base station with a user equipment over a partially wireless connection in accordance with some embodiments.

[00158] Example implementations, in accordance with an embodiment, of the UE, base station and host computer discussed in the preceding paragraphs will now be described with reference to Figure QQ5. In communication system QQ500, host computer QQ510 comprises hardware QQ515 including communication interface QQ516 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of communication system QQ500. Host computer QQ510 further comprises processing circuitry QQ518, which may have storage and/or processing capabilities. In particular, processing circuitry QQ518 may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. Host computer QQ510 further comprises software QQ511, which is stored in or accessible by host computer QQ510 and executable by processing circuitry QQ518. Software QQ511 includes host application QQ512. Host application QQ512 may be operable to provide a service to a remote user, such as UE QQ530 connecting via OTT connection QQ550 terminating at UE QQ530 and host computer QQ510. In providing the service to the remote user, host application QQ512 may provide user data which is transmitted using OTT connection QQ550.

[00159] Communication system QQ500 further includes base station QQ520 provided in a telecommunication system and comprising hardware QQ525 enabling it to communicate with host computer QQ510 and with UE QQ530. Hardware QQ525 may include communication interface QQ526 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system QQ500, as well as radio interface QQ527 for setting up and maintaining at least wireless connection QQ570 with UE QQ530 located in a coverage area (not shown in Figure QQ5) served by base station QQ520.

Communication interface QQ526 may be configured to facilitate connection QQ560 to host computer QQ510. Connection QQ560 may be direct or it may pass through a core network (not shown in Figure QQ5) of the telecommunication system and/or through one or more

intermediate networks outside the telecommunication system. In the embodiment shown, hardware QQ525 of base station QQ520 further includes processing circuitry QQ528, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. Base station QQ520 further has software QQ521 stored internally or accessible via an external connection.

[00160] Communication system QQ500 further includes UE QQ530 already referred to.

Its hardware QQ535 may include radio interface QQ537 configured to set up and maintain wireless connection QQ570 with a base station serving a coverage area in which UE QQ530 is currently located. Hardware QQ535 of UE QQ530 further includes processing circuitry QQ538, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. UE QQ530 further comprises software QQ531, which is stored in or accessible by UE QQ530 and executable by processing circuitry QQ538. Software QQ531 includes client application QQ532. Client application QQ532 may be operable to provide a service to a human or non-human user via UE QQ530, with the support of host computer QQ510. In host computer QQ510, an executing host application QQ512 may communicate with the executing client application QQ532 via OTT connection QQ550 terminating at UE QQ530 and host computer QQ510. In providing the service to the user, client application QQ532 may receive request data from host application QQ512 and provide user data in response to the request data. OTT connection QQ550 may transfer both the request data and the user data. Client application QQ532 may interact with the user to generate the user data that it provides. [00161 ] It is noted that host computer QQ510, base station QQ520 and UE QQ530 illustrated in Figure QQ5 may be similar or identical to host computer QQ430, one of base stations QQ4l2a, QQ4l2b, QQ4l2c and one of UEs QQ491, QQ492 of Figure QQ4, respectively. This is to say, the inner workings of these entities may be as shown in Figure QQ5 and independently, the surrounding network topology may be that of Figure QQ4.

[00162] In Figure QQ5, OTT connection QQ550 has been drawn abstractly to illustrate the communication between host computer QQ510 and UE QQ530 via base station QQ520, without explicit reference to any intermediary devices and the precise routing of messages via these devices. Network infrastructure may determine the routing, which it may be configured to hide from UE QQ530 or from the service provider operating host computer QQ510, or both. While OTT connection QQ550 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).

[00163] Wireless connection QQ570 between UE QQ530 and base station QQ520 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments may improve the performance of OTT services provided to UE QQ530 using OTT connection QQ550, in which wireless connection QQ570 forms the last segment. More precisely, the teachings of these embodiments may improve the deblock filtering for video processing and thereby provide benefits such as improved video encoding and/or decoding.

[00164] A measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring OTT connection QQ550 between host computer QQ510 and UE QQ530, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring OTT connection QQ550 may be implemented in software QQ511 and hardware QQ515 of host computer QQ510 or in software QQ531 and hardware QQ535 of UE QQ530, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which OTT connection QQ550 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software QQ511, QQ531 may compute or estimate the monitored quantities. The reconfiguring of OTT connection QQ550 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect base station QQ520, and it may be unknown or imperceptible to base station QQ520. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling facilitating host computer QQ5lO’s measurements of throughput, propagation times, latency and the like. The measurements may be implemented in that software QQ511 and QQ531 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using OTT connection QQ550 while it monitors propagation times, errors etc.

[00165] Figure QQ6: Methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments.

[00166] Figure QQ6 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to Figures QQ4 and QQ5. For simplicity of the present disclosure, only drawing references to Figure QQ6 will be included in this section. In step QQ610, the host computer provides user data. In substep QQ611 (which may be optional) of step QQ610, the host computer provides the user data by executing a host application. In step QQ620, the host computer initiates a transmission carrying the user data to the UE. In step QQ630 (which may be optional), the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step QQ640 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

[00167] Figure QQ7 : Methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments.

[00168] Figure QQ7 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to Figures QQ4 and QQ5. For simplicity of the present disclosure, only drawing references to Figure QQ7 will be included in this section. In step QQ710 of the method, the host computer provides user data.

In an optional substep (not shown) the host computer provides the user data by executing a host application. In step QQ720, the host computer initiates a transmission carrying the user data to the UE. The transmission may pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure. In step QQ730 (which may be optional), the UE receives the user data carried in the transmission.

[00169] Figure QQ8: Methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments.

[00170] Figure QQ8 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to Figures QQ4 and QQ5. For simplicity of the present disclosure, only drawing references to Figure QQ8 will be included in this section. In step QQ810 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step QQ820, the UE provides user data. In substep QQ821 (which may be optional) of step QQ820, the UE provides the user data by executing a client application. In substep QQ811 (which may be optional) of step QQ810, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer. In providing the user data, the executed client application may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the UE initiates, in substep QQ830 (which may be optional), transmission of the user data to the host computer. In step QQ840 of the method, the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.

[00171 ] Figure QQ9: Methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments.

[00172] Figure QQ9 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to Figures QQ4 and QQ5. For simplicity of the present disclosure, only drawing references to Figure QQ9 will be included in this section. In step QQ910 (which may be optional), in accordance with the teachings of the embodiments described throughout this disclosure, the base station receives user data from the UE. In step QQ920 (which may be optional), the base station initiates transmission of the received user data to the host computer. In step QQ930 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

[00173] Any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses. Each virtual apparatus may comprise a number of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory (RAM), cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more

embodiments of the present disclosure.

[00174] The term unit may have conventional meaning in the field of electronics, electrical devices and/or electronic devices and may include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.