WO2025165270A1 - Network nodes and methods for handling caching of data - Google Patents

Abstract

Embodiments herein relate to, for example, a method performed by a second network node (16) for handling data in a communication network (1). The second network node (16) adds data to be cached to a first message, and transmits to a first network node (15) the first message with the data to be cached. The second network node then receives from the first network node (15) a second message with the data of the first message and thereby stores and retrieves the data without using a local memory at the second network node.

Description

NETWORK NODES AND METHODS FOR HANDLING CACHING OF DATA

TECHNICAL FIELD

Embodiments herein relate to a first network node, a second network node and methods performed therein regarding communication. Furthermore, a computer program product and a computer readable storage medium are also provided herein. In particular, embodiments herein relate to handling data, e.g., caching of data, in a communication network.

BACKGROUND

In a typical communication network, user equipments (UE), also known as communication device, wireless communication devices, mobile stations, stations (STA) and/or wireless devices, communicate via a, access network, such as a Radio Access Network (RAN) with one or more core networks (CN). The RAN covers a geographical area which is divided into service areas or cells, with each service area or cell being served by a radio network node such as an access node, e.g., a Wi-Fi access point or a radio base station (RBS), which in some networks may also be called, for example, a NodeB, a gNodeB, or an eNodeB. The service area or cell is a geographical area where radio coverage is provided by the radio network node. The radio network node operates on radio frequencies to communicate over an air interface with the UEs within range of the radio network node. The radio network node communicates over a downlink (DL) to the UE and the UE communicates over an uplink (UL) to the radio network node.

A Universal Mobile Telecommunications System (UMTS) is a third generation (3G) telecommunication network, which evolved from the second generation (2G) Global System for Mobile Communications (GSM). The UMTS terrestrial radio access network (UTRAN) is essentially a RAN using wideband code division multiple access (WCDMA) and/or High-Speed Packet Access (HSPA) for communication with user equipment. In a forum known as the Third Generation Partnership Project (3GPP), telecommunications suppliers propose and agree upon standards for present and future generation networks and investigate e.g. enhanced data rate and radio capacity. In some RANs, e.g. as in UMTS, several radio network nodes may be connected, e.g., by landlines or microwave, to a controller node, such as a radio network controller (RNC) or a base station controller (BSC), which supervises and coordinates various activities of the plural radio network nodes connected thereto. The RNCs are typically connected to one or more core networks.

Specifications for the Evolved Packet System (EPS) have been completed within the 3GPP and coming 3GPP releases, such as New Radio (NR), are worked on. The EPS comprises the Evolved Universal Terrestrial Radio Access Network (E-UTRAN), also known as the Long-Term Evolution (LTE) radio access network, and the Evolved Packet Core (EPC), also known as System Architecture Evolution (SAE) core network. E-UTRAN/LTE is a 3GPP radio access technology wherein the radio network nodes are directly connected to the EPC core network. As such, the Radio Access Network (RAN) of an EPS has an essentially “flat” architecture comprising radio network nodes connected directly to one or more core networks.

With the emerging 5G technologies such as NR, the use of very many transmit- and receive-antenna elements may be of great interest as it makes it possible to utilize beamforming, such as transmit-side and receive-side beamforming. Transmit-side beamforming means that the transmitter can amplify the transmitted signals in a selected direction or directions, while suppressing the transmitted signals in other directions. Similarly, on the receive-side, a receiver can amplify signals from a selected direction or directions, while suppressing unwanted signals from other directions. NR is connected to the 5G Core Network (5GC) which comprises a number of Network Functions (NF) such as Session Management Function (SMF), User Plane Function (UPF), Access Management Function (AMF), Authentication Service Function (AUSF), Policy Control Function (PCF), Unified Data Manager (UDM), Network Repository Function (NRF), Network Exposure Function (NEF), just to mention some. In the 5GC, NFs can discover other NFs by using a discovery service provided by the Network Repository Function (NRF).

For session-based services all parts participating in a message exchange may generate data that is required to be cached i.e., data that was calculated or retrieved as part of the handling request/response and is not required to be sent to the other entity. Today the data that needs to be cached between two requests today have to be handled by the entity generating the data.

Caching of data has several issues, it requires secure storage, and that an interaction always reaches the same entity or at least to an entity that has access to the same cache or that the cache is distributed. When the data to be cached is large then the cost of storing it will be on par with the cost for securing and distributing it, but when there is only a small amount of data required to be stored the securing will be very costly comparing to the cost of storing it.

SUMMARY

An object of embodiments herein is to handle caching of data in a communication network in an efficient manner.

According to an aspect the object is achieved, according to some embodiments herein, by providing a method performed by a second network node for handling data in a communication network. The second network node adds data to be cached to a first message and transmits to the first network node the first message with the data to be cached. The second network node then receives from the first network node a second message with the data from the first message and thereby stores and retrieves the data without using a local memory at the second network node.

According to another aspect the object is achieved, according to some embodiments herein, by providing a method performed by a first network node for handling data in a communication network. The first network node receives from a second network node a first message with data to be cached. The first network node stores the data. Then the first network node adds the data of the first message into a second message; and transmits the second message to the second network node, wherein the second message comprises the data of the first message and thereby the data is stored and retrieved without using a local memory at the second network node.

It is furthermore provided herein a computer program comprising instructions, which, when executed on at least one processor, cause the at least one processor to carry out any of the methods herein, as performed by the first network node and the second network node, respectively. It is additionally provided herein a computer-readable storage medium, having stored thereon a computer program comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out the method according to any of the methods herein, as performed by the first network node and the second network node, respectively.

According to another aspect a first network node and a second network node are herein provided to be configured to perform the methods herein, respectively.

According to an aspect the object is achieved, according to some embodiments herein, by providing a second network node for handling data in a communication network. The second network node is configured to add data to be cached to a first message and to transmit to the first network node the first message with the data to be cached. The second network node is configured to receive, from the first network node, a second message with the data from the first message and thereby to store and retrieve the data without using a local memory at the second network node.

According to another aspect the object is achieved, according to some embodiments herein, by providing a first network node for handling data in a communication network. The first network node is configured to receive from a second network node, a first message with data to be cached. The first network node is configured to store the data, and then to add the data of the first message into a second message. The first network node is configured to transmit the second message to the second network node, wherein the second message comprises the data of the first message and thereby the data is stored and retrieved without using a local memory at the second network node.

Embodiments herein provide a solution for caching data without storing data locally at the second network node. Thus, the second network node provides a possibility to send the data needed to be cached to the first network node, such as a receiver of the message, and have the first network node to return the data in the next message. There are two ways of transporting cached data either in a header of the message or as payload in the message. The advantage with using a header is that intermediate network nodes, such as NF's like Service Communication proxy (SCP) and/or Security Edge Protection Proxy (SEPP), i.e., examples of the second network node, involved in the interaction may also use the header to cache data. The advantage with using the payload is that the data cached is more service specific and also that the header is not intended for carrying this type of data.

In both cases there may be a need for the first network node of the cached data to state how much data can be stored to limit the size and amount of data that needs to be handled as well as the amount of data that is transported.

The embodiments herein provide one or more of the following advantages: embodiments herein provide flexibility to cache data, e.g., information, in network nodes such as peer NFs, being examples of the first and second network nodes; embodiments herein allow the cache to be use case driven and not always required; embodiments herein allow intermediate stateless NFs, like SCP/SEPP/intermediate NFs like CHF, being examples of the second network node, to have an option to cache data using peer NF; embodiments herein allow NFs that require to keep a state to pass this around and by that become stateless; and embodiments herein allow multiple NFs involved to have their own section of the cache so that all NFs can cache the data they find necessary.

Thus, embodiments herein handle caching of data in a communication network in an efficient manner.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments will now be described in more detail in relation to the enclosed drawings, in which:

Fig. 1 is a schematic overview depicting a communication network according to embodiments herein;

Fig. 2a is a combined flowchart and signalling scheme according to some embodiments herein;

Fig. 2b is a combined flowchart and signalling scheme according to some embodiments herein;

Fig. 3 is a schematic flowchart depicting a method performed by a second network node according to embodiments herein;

Fig. 4 is a schematic flowchart depicting a method performed by a first network node according to embodiments herein;

Fig. 5 is a combined flowchart and signalling scheme according to some embodiments herein; Fig. 6 is a combined flowchart and signalling scheme according to some embodiments herein;

Fig. 7 is a combined flowchart and signalling scheme according to some embodiments herein;

Fig. 8 is a combined flowchart and signalling scheme according to some embodiments herein;

Fig. 9 is an overview depicting grouping according to some embodiments herein;

Fig. 10 is a combined flowchart and signalling scheme according to some embodiments herein;

Fig. 11 is a combined flowchart and signalling scheme according to some embodiments herein;

Fig. 12 is a combined flowchart and signalling scheme according to some embodiments herein;

Fig. 13 is a block diagram depicting a second network node according to embodiments herein;

Fig. 14 is a block diagram depicting a first network node according to embodiments herein;

Fig. 15 shows an example of a communication system QQ100 in accordance with some embodiments;

Fig. 16 shows a UE QQ200 in accordance with some embodiments;

Fig. 17 shows a network node QQ300 in accordance with some embodiments;

Fig. 18 is a block diagram of a host QQ400, which may be an embodiment of the host QQ116 of Fig. 15, in accordance with various aspects described herein;

Fig. 19 is a block diagram illustrating a virtualization environment QQ500 in which functions implemented by some embodiments may be virtualized; and

Fig. 20 shows a communication diagram of a host QQ602 communicating via a network node QQ604 with a UE QQ606 over a partially wireless connection in accordance with some embodiments.

DETAILED DESCRIPTION

Embodiments herein relate to wireless communication networks in general. Fig. 1 is a schematic overview depicting a communication network 1. The communication network 1 comprises one or more access networks (AN) and one or more core networks (CN). The communication network 1 may use one or a number of different technologies, wired and/or wireless technologies. Embodiments herein relate to recent technology trends that are of particular interest in a New Radio (NR) context, however, embodiments are also applicable in further development of existing wireless communications systems such as e.g. LTE or Wideband Code Division Multiple Access (WCDMA). In the communication network 1 , one or more UEs such as a user equipment (UE) 10 exemplified herein as a wireless device such as a mobile station, a non-access point (non-AP) station (STA), a STA and/or a wireless terminal, are comprised communicating via e.g. one or more Access Networks (AN), e.g. radio access network (RAN), to one or more core networks (CN). It should be understood by the skilled in the art that “UE” is a non-limiting term which means any terminal, wireless communications terminal, user equipment, narrowband internet of things (NB- loT) device, Machine Type Communication (MTC) device, Device to Device (D2D) terminal, or node e.g. smart phone, laptop, mobile phone, sensor, relay, mobile tablets or even a small base station capable of communicating using radio communication with a radio network node within an area served by the radio network node.

The communication network 1 comprises a first radio network node 12, providing radio coverage over a geographical area, a first service area 11 or first cell, of a first radio access technology (RAT), such as NR, LTE, or similar. The first radio network node 12 may be a transmission and reception point such as an access node, an access controller, a base station, e.g. a radio base station such as a gNodeB (gNB), an evolved Node B (eNB, eNode B), a NodeB, a base transceiver station, a radio remote unit, an Access Point Base Station, a NG-RAN-CU-UP node, base station router, a Wireless Local Area Network (WLAN) access point or an Access Point Station (AP STA), a transmission arrangement of a radio base station, a stand-alone access point or any other network unit or node capable of communicating with a UE within the area served by the first radio network node depending e.g. on the first radio access technology and terminology used. The first radio network node may communicate with the UE 10 in form of DL transmissions to the UE 10 and UL transmissions from the UE 10.

The communication network 1 comprises a second radio network node 13, providing radio coverage over a geographical area, a second service area 14 or second cell, of a second radio access technology (RAT), such as NR, LTE, or similar. The second radio network node 13 may be a transmission and reception point such as an access node, an access controller, a base station, e.g. a radio base station such as a gNodeB (gNB), an evolved Node B (eNB, eNode B), a NodeB, a base transceiver station, a radio remote unit, an Access Point Base Station, a base station router, a Wireless Local Area Network (WLAN) access point or an Access Point Station (AP STA), a transmission arrangement of a radio base station, a stand-alone access point or any other network unit or node capable of communicating with a wireless device within the area served by the second radio network node depending e.g. on the first radio access technology and terminology used. The second radio network node communicates with the UE in form of DL transmissions to the UE and UL transmissions from the UE.

It should be noted that a service area may be denoted as cell, beam, beam group or similar to define an area of radio coverage. It should further be noted that with “RAN” it is indicated a RAN node, e.g., a gNB or base station, or a function of a RAN entity, e.g., a control plane functionality such as central unit (CU) control plane (CP). The first RAT may be the same RAT as the second RAT or the first RAT may be a different RAT than the second RAT.

The communication network 1 comprises a number of network nodes providing, for example, network functions (NF) or actually instantiations of NFs also referred to as NF instances, such as a first network node 15, for example, a NF such as a CHF, a SCP, a SMF, a PCF; a second network node 16, for example, another NF, such as a CHF, a SMF, a SCP, a PCF, and a third network node 17 such as a further NF, such as a CHF, SCP, SMF, PCF. The different NF instances may have same or different tasks. Other functions may be for LTE such as MME or similar. IT should further be noted that a network node may also be a RAN node in some cases.

The respective node may be a standalone server, a cloud-implemented server, a distributed server or processing resources in a server farm or same node. Embodiments herein may be implemented as physical bare metal, virtual or cloud native such as Kubernetes environment in, e.g., hyper-cloud networks.

The second network node 16 may comprise a provider network node, an intermediate network node between network nodes, or any network function node handling data communication in the communication network 1. The first network node 15 may comprise a consumer network node, or any network function node handling data communication in the communication network 1. A consumer network node may consume, such as subscribes to, a network service from a provider network node such as the second network node 16.

Embodiments herein provide means for storing data without using a local memory at the respective network node and/or also avoiding an external lookup or any complicated logics. For example, the second network node 16 adds data to be cached to a first message and transmits to the first network node 15 the first message with the data to be cached, may also be referred to as cache information or data. The second network node 16 then receives from the first network node 15 a second message with the data from the first message and thereby stores and retrieves the data without using a local memory at the second network node 16.

Fig. 2a is a combined signalling scheme and flowchart depicting some embodiments herein.

Action 201. The first network node 15 may transmit an original message, such as a request message or any message to the second network node 16.

Action 202. The second network node 16 may obtain data to be cached. For example, the second network node 16 may determine the data, be preconfigured with the data, and/or retrieve the data from within.

Action 203. The second network node 16 adds the data to be cached to a first message, such as a first response. The second network node 16 may add additional data to the first message. The additional data may indicate a limitation of how much data can be cached. Action 204. The second network node 16 transmits the first message with the data, to be cached, to the first network node 15. The first message may further comprise the additional data.

Action 205. The first network node 15 receives the first message from the second network node 16, stores the data to be cached.

Action 206. The first network node 15 adds the data of the first message into a second message, such as a second request.

Action 207. The first network node 15 may add its own data to be cached and /or add additional data, or change, and add the changed additional data to the second message. It may further be the first network node 15 that initially adds the additional data.

Action 208. The first network node 15 transmits the second message to the second network node 16. The second message comprises the data of the first message. The second message may comprise the additional or changed additional data. It should here be noted that the second message is sent at a time when there is a need to send the data. Hence, the first message may be received a first time to and then transmitted at a second time t1. The t1 may be performed a time interval after receiving the first message.

Action 209. The second network node 16 may receive the second message and process the second message taking the data in the second message into account.

The second network node 16 may also be used for caching data from the first network node 15, thus, the caching may be in any direction.

Hence, embodiments herein show a manner wherein the cached data is stored and retrieved without using a local memory at the second network node 16 (and/or the first network node 15 in the case of transmitting the own data).

Fig. 2b is a combined signalling scheme and flowchart depicting some embodiments herein. The second network node 16 may in this case be an intermediate node between other network nodes such as Peer nodes or NFs.

Action 200. The first network node 15 may transmit an original message, such as a request message or any message to the second network node 16 and/or the third network node 17.

Action 211. The second network node 16 may obtain data to be cached. For example, the second network node 16 may determine the data, retrieve the data from within, and/or receive from a message from the third network node 17. The data may be any type of data such as data related to a database lookup or similar.

Action 212. The second network node 16 adds the data to the first message.

Action 213. The second network node 16 transmits the first message, such as a first response, with the data to be cached to the first network node 15. Action 214. The first network node 15 receives the first message from the second network node 16, and stores the data, i.e. , the first network node 15 caches the data of the second network node 16.

Action 215. The first network node 15 adds the cached data of the first message into the second message, such as a second request. The first network node 15 may add additional data, or change and add the changed additional data to the second message.

Action 216. The first network node 15 transmits the second message to the second network node 16. The second message comprises the data of the first message.

Action 217. The second network node 16 may receive the second message and process or handle the second message taking the data, from the second network node 16, in the second message into account. The second network node 16 may, for example, route the message towards the third network node 17 as indicated by the data. Thus, the data is stored and retrieved without using a local memory at the second network node.

Embodiments herein add a possibility to send data needed to be cached to the first network node 15 such as a receiver of a message, and have the receiver return the information in the next message. There are two ways of transporting the cached data either in a message header such as an HTTP-header, or in the message payload such as an HTTP-body.

An advantage in using the header is that an intermediate NF's like SCP/SEPP involved in the interaction may use the header to cache its own data.

An advantage in using the message body is that the data cached is more service specific and also that the header is not intended for carrying this type of data.

In both cases the first network node 15 such as the receiver of the data to be cached may state or inform how much data that can be stored to limit the size and amount of data that needed to be handled as well as the amount that is transported.

Message header option:

When a first network node 15, such as a client, supports caching data in a header, the first network node 15 may include the header in a request with indication of a size of each cache that it allows. The second network node 16 may, such as a server, may indicate it’s support of caching data in the header by setting this in an NRF. Whenever there is a need to cache data, the second network node 16 may create or update a header and in the creation of the header, the second network node 16 may add a size restriction, and for the updating of the second network node 16 may check the current size restriction may only update this if it has a lower restriction. The respective network node may further add its own data such as NF type, unique id, and also the data to cache. The data to cache may be in any form, since this is not to be read by any other than the respective network node or an NF instance that works as a backup. This means that preferably the data to be cached may be packed if possible. 3gpp-Sbi-Nf-Cache-lnfo-Header = "3gpp-Sbi-Nf-Cache-lnfo:" OWS [“cachelimit=" 1*DIGIT] OWS 1*(“nftype=” nfType OWS [“nfinst=” nfinst OWS] “cachedinfo=” 1*(2HEXDIG) OWS) nfType = token

This should follow the 3GPP allowed NF Type or 3GGP allowed Custom NF Type. cachelimit: holds the limit size in octets i.e., two hex-digits cachedinfo: holds the data to be cached and can be packed, it shall consider the cache limit

Note: Header may include identity of the network node such as NF instance in case the value is specific to that network node and cannot be used by any network node of the same type. The identity may be a Universally Unique Identifier (UUID), a Globally Unique Identifier (GUID) or similar.

Examples of information in the header:

Value from one NF, such as the second network node 16, to be cached: 3gpp-Sbi-Nf-Cache-lnfo: cachelimit=2000 ; nftype=SCP ; nfinst=54804519-4191-46b3- 955c-ac631f953ed0 ; cached info=1A2B3C4E5F

Value from two NFs, such as the first and the second network node, to be cached: 3gpp-Sbi-Nf-Cache-lnfo: cachelimit=2000 ; nftype=SCP ; nfinst=54804519-4191-46b3- 955c-ac631f953ed0 ; cached info=1A2B3C4E5F, nftype=CHF ; cachedinfo=6A7B8C9E0F

Whenever there is a need to cache data of either source or target NF’s, being example of the first and second network node, one or more of the below message parameters may be used.

Table 1 Structure of InfoToCache

The information in the cachedinfo may be compressed and/or encoded if required.

The method actions performed by the second network node 16, such as an NF, for handling data in the communication network 1 according to embodiments will now be described with reference to a flowchart depicted in Fig. 3. The actions do not have to be taken in the order stated below but may be taken in any suitable order. Dashed boxes indicate optional features.

Action 301. The second network node 16 may receive an original message, such as a request message or any message from the first network node 15.

Action 302. The second network node 16 may obtain data to be cached. For example, the second network node 16 may determine the data, be preconfigured with the data, and/or retrieve the data from within.

Action 303. The second network node 16 adds the data to be cached to a first message. The second network node 16 may add additional data to the first message. The additional data may indicate a limitation of how much data can be cached. The additional information may comprise an indication of limitation of data amount to cache, identity of a network node, and/or a type of service.

Action 304. The second network node 16 transmits the first message with the data to be cached to the first network node 15. The first message may further comprise the additional data.

Action 305. The second network node 16 receives a second message with the data from the first message. Thus, the data is stored and retrieved without using a local memory at the second network node 16. The second message may further comprise changed additional data.

Action 306. It should be noted that the first network node 15 may send its own data to be cached in the second network node 16. Thus, the second network node 16 may cache data from the first network node 15. The second network node 16 may fetch and populate cached data to another message.

Action 307. The second network node 16 may then transmit to the first network node 15 the cached data (the own data of the first network node 15) in a third message such as a request/response.

Action 308. Additionally, or alternatively, the second network node 16 may process the second message taking the data in the second message into account. The second network node 16 may, for example, use for lookup, or route the message towards the third network node 17 as indicated by the data.

Thus, data in the second network node such as a peer NF’s may be cached remotely so that it can be used when received in further messages over that session. It improves efficiency and statelessness in many scenarios like routing, database (DB)-access etc., It is method commonly usable for intermediate, source and target NF’s and service independent as well.

The method actions performed by the first network node 15, such as an NF node, for handling data in the communication network 1 according to embodiments will now be described with reference to a flowchart depicted in Fig. 4. The actions do not have to be taken in the order stated below but may be taken in any suitable order. Dashed boxes indicate optional features. Action 401. The first network node 15 may transmit the original message, such as a request message or any message to the second network node 16.

Action 402. The first network node 15 receives the first message with the data from the second network node 16. The first message may comprise the additional data. The additional information may comprise an indication of limitation of data amount to cache, identity of a network node, and/or a type of service.

Action 403. The first network node 15 stores the data. The first network node 15 may thus receive the first message and store the data until a second message is to be transmitted at a later time.

Action 404. The first network node 15 adds the data of the first message into the second message. The first network node 15 may add the additional data, or change, and add the changed additional data to the second message. It may further be the first network node 15 that initially adds the additional data.

Action 405. The first network node 15 may add the additional data, or change and add the changed additional data to the second message.

Action 406. The first network node 15 may further add own data to the second message to be cached by the second network node 16.

Action 407. The first network node 15 transmits the second message to the second network node 16. The second message comprises the data of the first message and thereby the data is stored and retrieved without using a local memory at the second network node 16. The second message may comprise the additional or changed additional data.

Action 408. The first network node 15 may receive the third message from the second network node 16 carrying the own data. Thus, the first network node may further retrieve its own data by adding own data to the second message to be retrieved in the third message. Hence, the second network node 16 may be used for caching data from the first network node 15, thus, the caching may be in any direction.

Fig. 5 shows an example of embodiments wherein the first network node 15 is exemplified as an NFConsumer 15’, and the second network node 16 is exemplified as an NFProducer 16’.

Actions 501. The NFConsumer 15’ initiates a service request towards NFProducer 16’.

Actions 502. The NFProducer 16’ populates the key to be cached in NFConsumer. Thus adds its information to cache in the header with the information about its NF type.

Actions 503. The NFProducer 16’ responds with the data to cache in the header with the information about its NF type.

Actions 504. The NFConsumer 15’ stores the cache information.

Actions 505. The NFConsumer 15’ fetches and populates cached data. Actions 506. The NFConsumer 15’ then transmits in a next request the data in the HTTP header.

Actions 507. The NFProducer 16’ may when receiving the data that it cached in previous request use this when it processes the request.

Actions 508. The NFProducer 16’ may return a new or the same information in the response to the NFCosumer 15’.

Actions 509. The NFConsumer 15’ fetches and populates cached data.

Actions 510. The NFConsumer 15’ then transmits in a next request the data in the HTTP header.

Actions 511. The NFProducer 16’ may when receiving the data that it cached in previous request use this when it processes the request.

Actions 512. The NFProducer 16’ may update the header with a new parameter or value for old parameter.

Actions 513. The NFProducer 16’ may return the new parameter or value in a response to the NFCosumer 15’.

Actions 514. The NFConsumer 15’ stores the new cache information.

Note: The NFCosumer 15’ may add own data to cache in the request message which would then be returned by the NFProducer 16’. The flow and information would look similar for the message parameter option.

Fig. 6 shows an example of embodiments, e.g., an indirect communication with SCP (HTTP header option), wherein the first network node 15 is exemplified as an NFConsumer 15”, the second network node 16 is exemplified as SCP/SEPP 16”, and the third network node 17 is exemplified as an NFProducer 17”.

Actions 601. The NFConsumer 15” initiates a service request towards NFProducer 17” through the SCP/SEPP 16”.

Actions 602. The SCP/SEPP 16” forwards the message to the NFProducer.

Actions 603. The NFProducer 17” responds based on the request.

Actions 604. The SCP/SEPP 16” adds its data to cache in the header with the information about its NF type i.e. , SCP or SEPP.

Actions 605. The SCP/SEPP 16” forwards the response with the data to be cached.

Actions 606. The NFConsumer 15” stores the cache and fetches and populates cached data.

Actions 607. The NFConsumer 15” transmit a next request with the data in the HTTP header. Actions 608. The SCP/SEPP 16” may, when receiving the cached information, use this when it processes the request, before forwarding the request to the NFProducer 17”. It may remove its own cache before forwarding the request.

Actions 609. The SCP/SEPP 16” may thus forwards the request.

Actions 610. The NFProducer responds based on the request.

Actions 611. The SCP/SEPP 16” may thus forwards the response.

Note: The NFCosumer 15” and NFProducer 17” could add own data to cache in the request/response messages, and if there are more than one SCP/SEPP in the flow these could add individual information as well.

Fig. 7 shows an example of embodiments, e.g., communication between SMF and CHF (HTTP header option), wherein the first network node 15 is exemplified as an SMF 15”’, and the second network node 16 is exemplified as an CHF 16”’.

Action 701. The SMF 15’” initiates a service request towards CHF 16’”, with a cache limit of 4000 and data to cache by the CHF 16’”.

Action 702. The CHF 16’” caches the SMF data.

Action 703. The CHF 16’” fetches and populates cached data into the service response.

Action 704. The CHF 16’” responds with the cached data, adds its information to cache and sets a lower cache limits since it only supports 2000.

Action 705. The SMF 15’” stores the cache information, uses its own cached data.

Action 706. The SMF 15’” fetches and populates cached data into the service request.

Action 707. Thus, in a next request the SMF 15’” returns CHF cached information in the HTTP header.

Action 708. The CHF 16’” then uses the cached data received in the request.

Other considerations.

The support of the caching could be either as a feature and registered in the NRF, the client could indicate support by including either the header or the parameter in the request.

To have control on the limit of cache applicable for peer NF’s to store their data to avoid overconsumption. It can be controlled using the registered information in the NRF and as above be included in the request. The limit could be an overall limit or a per NF limit.

It is also possible to have a mix of header and parameter cache e.g., the end points uses the parameter while any intermediate uses the header.

It is herein provided methods for caching data in, e.g., peer NF’s so that it can be used for further messages over that session. It improves the efficiency and statelessness in many scenarios like routing, database-access etc., It is method commonly usable for intermediate, source and target NF’s and service independent as well. Use easel is illustrated in Fig. 8: CHF-to-CHF (MVNO Routing)

In Fig. 8 it is shown a scenario of a multiple Mobile Virtual Network Operator (MVNO) in a Mobile Network Operator (MNO) environment, there would be a hierarchy of CHF’s as shown wherein M NO-CH F 16”” will be stateless redirecting the traffic request to appropriate MVNO-CHF 17”” instance based on request information like Subscriber identities such as Subscription Permanent Identifier (SUPI), or Generic Public Subscription Identifier (GPSI), over a query or a lookup such as a database lookup. To avoid lookup for every request of a common session, relevant MVNO-CHF information say MVNO2 in this scenario can be sent over HTTP header in response to be cached in SMF 15”” which can be utilized when received in further request to perform redirection for routing to appropriate CHF. Action 801. The CTF 15”” transmits a service request. Action 802. The CHF 16”” determines the MVNO based on payload and internal information, e.g., SUPI, GPSI, MVNO information. This may require a lookup process in system such as a database query, domain name server (DNS) query. Action 803. The CHF 16”” transmit a service request to the MVNO 2. Action 804. The MVNO 2 responds with a service response. Action 805. The CHF 16”” transmits a service response with cached information such as identity of the MVNO 2. Action 806. The CTF 15”” responds with a service request comprising the cached information. Action 807. The CHF1 16”” may route the service request to MVNO 2 based on the cached information. Action 808. Thus, the CHF1 16”” transmits service request to the MVNO 2. Action 809. The MVNO 2 transmits a service response to the CHF1 16””. Action 810. The CHF 16”” transmits a service response with cached information such as identity of the MVNO 2.

Use case2 is illustrated in Figs. 9 and 10: Operator Specific SCP Routing

In a scenario of having multiple sites as shown in Figs. 9-10 if a segment (say Groupl) of the data of one site (say sitel) replicated to one site (say site2) and other data segment (say Group2) is replicated to another site (say site3) as shown in Fig. 9 in a Geo Distributed setup picture existing 3GPP specified routing/redirection methods is not workable. Instead if the segment information (say Group2) of the session is shared to NFConsumer via intermediate-node over NFProducer-response, it can be cached by NFConsumer as part of the session data. When NFConsumer shares the segment-information in further request of the session, then intermediate node will be capable of redirecting the request to relevant redundant site if the primary-site handling the session is not reachable as shown in call flow diagram. Thus, action 101, the NF consumer 16‘”” transmits a service request to the NF produced 15””’ via the intermediate node(SCP) 17’””. Action 102. The NF produced 15’”” transmits cached information indicating group 2. Action 103. The NF consumer 16””” transmits cached information indicating group 2 in the service request to the SCP 17’””. Action 103. The SCP 17’”” does not reach NFProduced handling the session. Action 104. The SCP 17’”” uses the cached information of produced 15’”” and routes to the alternate CHF when needed. Action 105. The SCP 17””’ transmit the service request to the NFproducer 3.

Use case 3 is illustrated in Fig. 11 : : E2E Tracing of Complete Session with common Reference (Server-side caching).

In a network, for a single session multiple network functions interact between each other to provide the service, in case of exceptions/issues for troubleshooting there is a need for end-to-end tracing so that it helps in determining the root cause. In a session level call flow, request can be initiated from any Network Function either NFConsumer 15* or NFProducer 16* based on needs in such a scenario we need a common correlating factor across the session level messages like sessionlD. For Notification requests, initiated from NFProducer 16* as shown Fig. 11 sessionlD is not part of the 3GPP Specification, e.g., CHF sent notification. In those cases as part of tracing to correlate these messages with session, cache HTTP-header can be used to share the sessionlD so that stateless intermediate-nodes will be capable of using it to correlate it with the session and use it for tracing.

Use case 4 is illustrated in Fig. 12: Client share the information of previous request.

In case the NFProducer 16** is stateless but it needs meagre piece of information from previous request handled by it, it can cache that piece of information over cache HTTP header in NFConsumer 15** as part of the response so that NFConsumer 15** shares that information in the next request to NFProducer 16**.

In scenario of Fig. 12, the stateless-NFProducer (CHF) 16** needs a timestamp value(tl) received in previous request while generating the CHF-CDR as part of handling the next request of the session. To achieve this, stateless-CHF 16** can send timestamp of previous request over the cache HTTP-header in response towards the stateful-NFConsumer (SMF) 15** as shown in call flow so that it shares the timestamp in the next request to be usable by CHF 16** while generating CHF-CDR as part of next request.

Note: NFProducer 16** can update the Timestamp value in second response so that it cached and shared in third request by NFConsumer 15**.

Fig. 13 shows a block diagram depicting the second network node 16 for handling data in the communication network.

The second network node 16 may comprise processing circuitry 1301 , e.g. one or more processors, configured to perform the methods herein.

The second network node 16 and/or the processing circuitry 1301 is configured to add the data to be cached to the first message.

The second network node 16 and/or the processing circuitry 1301 is configured to transmit to the first network node 15 the first message with the data to be cached. The second network node 16 and/or the processing circuitry 1301 is configured to receive from the first network node 15 the second message with the data from the first message and thereby store and retrieve the data without using a local memory at the second network node.

The first message and/or the second message may comprise additional information. The additional information may comprise the indication of limitation of data amount to cache, the identity of a network node, and/or the type of service.

The second message may comprise data, own data, from the first network node 15 to be cached by the second network node 16 and the second network node 16 and/or the processing circuitry 1301 may be configured to transmit the third message to the first network node 15 carrying the data from the first network node 15.

The second network node 16 and/or the processing circuitry 1301 may be configured to obtain the data to be cached by determining the data, being preconfigured with the data, retrieving the data from within, and/or receiving data from another network node.

The second network node 16 and/or the processing circuitry 1301 may be configured to process the second message by taking the data in the second message into account.

The data may be transported in a header or payload in respective message.

The second network node 16 further comprises a memory 1305. The memory comprises one or more units to be used to store data on, such as indications, data, additional data, cached data, messages, reconfiguration, applications to perform the methods disclosed herein when being executed, and similar. The second network node 16 comprises a communication interface 1306 comprising transmitter, receiver, transceiver and/or one or more antennas. Thus, it is herein provided the second network node 16 for handling data in a communication network, wherein the second network node 16 comprises processing circuitry and a memory, said memory comprising instructions executable by said processing circuitry whereby said second network node 16 is operative to perform any of the methods herein.

The methods according to the embodiments described herein for the second network node 16 are respectively implemented by means of e.g. a computer program product 1307 or a computer program product, comprising instructions, i.e. , software code portions, which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the second network node 16. The computer program product 1307 may be stored on a computer-readable storage medium 1308, e g. a universal serial bus (USB) stick, a disc or similar. The computer-readable storage medium 1308, having stored thereon the computer program product, may comprise the instructions which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the second network node 16. In some embodiments, the computer-readable storage medium may be a non-transitory or transitory computer-readable storage medium. Fig. 14 shows a block diagram depicting the first network node 15 for handling data in a communication network.

The first network node 15 may comprise processing circuitry 1401 , e.g. one or more processors, configured to perform the methods herein.

The first network node 15 and/or the processing circuitry 1401 is configured to receive from the second network node 16 the first message with data to be cached.

The first network node 15 and/or the processing circuitry 1401 is configured to store the data.

The first network node 15 and/or the processing circuitry 1401 is configured to add the data of the first message into a second message; and transmit the second message to the second network node 16. The second message comprises the data of the first message and thereby the data is stored and retrieved without using a local memory at the second network node.

The first message and/or the second message may comprise the additional information. The additional information may comprise the indication of limitation of data amount to cache, identity of a network node, and/or a type of service.

The first network node 15 and/or the processing circuitry 1401 may be configured to add the additional data, or changing, and adding the changed additional data to the second message.

The first network node 15 and/or the processing circuitry 1401 may be configured to add the own data to the second message to be cached by the second network node 16. The first network node 15 and/or the processing circuitry 1401 may be configured to receive the third message from the second network node 16 carrying the own data.

The data may be transported in a header or payload in respective message.

The first network node 15 further comprises a memory 1405. The memory comprises one or more units to be used to store data on, such as indications, data, additional data, cached data, messages, reconfiguration, applications to perform the methods disclosed herein when being executed, and similar. The first network node 15 comprises a communication interface 1406 comprising transmitter, receiver, transceiver and/or one or more antennas. Thus, it is herein provided the first network node 15 for handling data in a communication network, wherein the first network node 15 comprises processing circuitry and a memory, said memory comprising instructions executable by said processing circuitry whereby said first network node 15 is operative to perform any of the methods herein.

The methods according to the embodiments described herein for the first network node 15 are respectively implemented by means of e.g. a computer program product 1407 or a computer program product, comprising instructions, i.e., software code portions, which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the first network node 15. The computer program product 1407 may be stored on a computer-readable storage medium 1408, e.g. a universal serial bus (USB) stick, a disc or similar. The computer-readable storage medium 1408, having stored thereon the computer program product, may comprise the instructions which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the first network node 15. In some embodiments, the computer-readable storage medium may be a non-transitory or transitory computer-readable storage medium.

As will be readily understood by those familiar with communications design, that functions means or modules may be implemented using digital logic and/or one or more microcontrollers, microprocessors, or other digital hardware. In some embodiments, several or all of the various functions may be implemented together, such as in a single application-specific integrated circuit (ASIC), or in two or more separate devices with appropriate hardware and/or software interfaces between them. Several of the functions may be implemented on a processor shared with other functional components of a radio network node, for example.

Alternatively, several of the functional elements of the processing means discussed may be provided through the use of dedicated hardware, while others are provided with hardware for executing software, in association with the appropriate software or firmware. Thus, the term “processor” or “controller” as used herein does not exclusively refer to hardware capable of executing software and may implicitly include, without limitation, digital signal processor (DSP) hardware, read-only memory (ROM) for storing software, random-access memory for storing software and/or program or application data, and non-volatile memory. Other hardware, conventional and/or custom, may also be included. Designers of communications receivers will appreciate the cost, performance, and maintenance trade-offs inherent in these design choices.

Fig. 15 shows an example of a communication system QQ100 in accordance with some embodiments.

In the example, the communication system QQ100 includes a telecommunication network QQ102 that includes an access network QQ104, such as a radio access network (RAN), and a core network QQ106, which includes one or more core network nodes QQ108. The access network QQ104 includes one or more access network nodes, such as network nodes QQ110a and QQ110b (one or more of which may be generally referred to as network nodes QQ110) being examples of the first radio network node 12 and second radio network node 13, or any other similar 3^rd Generation Partnership Project (3GPP) access nodes or non- 3GPP access points. Moreover, as will be appreciated by those of skill in the art, a network node, being examples of the entities herein, is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunication network QQ102 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network QQ102 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other nodes to implement one or more functionalities of any node in the telecommunication network QQ102, including one or more network nodes QQ110 and/or core network nodes QQ108.

Examples of an ORAN network node include an open radio unit (0-Rll), an open distributed unit (0-Dll), an open central unit (O-CU), including an O-CU control plane (O-CU- CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). The network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an A1, F1, W1, E1 , E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN access node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an 0-2 interface defined by the O-RAN Alliance or comparable technologies. The network nodes QQ110 facilitate direct or indirect connection of the user equipment (UE) 10, such as by connecting UEs QQ112a, QQ112b, QQ112c, and QQ112d (one or more of which may be generally referred to as UEs QQ112) to the core network QQ106 over one or more wireless connections.

Example wireless communications over a wireless connection include transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system QQ100 may include any number of wired or wireless networks, network nodes, UEs, 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. The communication system QQ100 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system.

The UEs QQ112 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and/or operable to communicate wirelessly with the network nodes QQ110 and other communication devices. Similarly, the network nodes QQ110 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs QQ112 and/or with other network nodes or equipment in the telecommunication network QQ102 to enable and/or provide network access, such as wireless network access, and/or to perform other functions, such as administration in the telecommunication network QQ102.

In the depicted example, the core network QQ106 connects the network nodes QQ110 to one or more hosts, such as host QQ116. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network QQ106 includes one more core network nodes (e.g., core network node QQ108) such as network node 15 that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and/or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node QQ108. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (ALISF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and/or a User Plane Function (UPF).

The host QQ116 may be under the ownership or control of a service provider other than an operator or provider of the access network QQ104 and/or the telecommunication network QQ102, and may be operated by the service provider or on behalf of the service provider. The host QQ116 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio/video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

As a whole, the communication system QQ100 of Fig. 15 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and/or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and/or any low- power wide-area network (LPWAN) standards such as LoRa and Sigfox. In some examples, the telecommunication network QQ102 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network QQ102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network QQ102. For example, the telecommunications network QQ102 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and/or Massive Machine Type Communication (mMTC)/Massive loT services to yet further UEs.

In some examples, the UEs QQ112 are configured to transmit and/or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network QQ104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network QQ104. Additionally, a UE may be configured for operating in single- or multi-RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).

In the example, the hub QQ114 communicates with the access network QQ104 to facilitate indirect communication between one or more UEs (e.g., UE QQ112c and/or QQ112d) and network nodes (e.g., network node QQ110b). In some examples, the hub QQ114 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub QQ114 may be a broadband router enabling access to the core network QQ106 for the UEs. As another example, the hub QQ114 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes QQ110, or by executable code, script, process, or other instructions in the hub QQ114. As another example, the hub QQ114 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub QQ114 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub QQ114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub QQ114 then provides to the UE either directly, after performing local processing, and/or after adding additional local content. In still another example, the hub QQ114 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.

The hub QQ114 may have a constant/persistent or intermittent connection to the network node QQ110b. The hub QQ114 may also allow for a different communication scheme and/or schedule between the hub QQ114 and UEs (e.g., UE QQ112c and/or QQ112d), and between the hub QQ114 and the core network QQ106. In other examples, the hub QQ114 is connected to the core network QQ106 and/or one or more UEs via a wired connection. Moreover, the hub QQ114 may be configured to connect to an M2M service provider over the access network QQ104 and/or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes QQ110 while still connected via the hub QQ114 via a wired or wireless connection. In some embodiments, the hub QQ114 may be a dedicated hub - that is, a hub whose primary function is to route communications to/from the UEs from/to the network node QQ110b. In other embodiments, the hub QQ114 may be a nondedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node QQ110b, but which is additionally capable of operating as a communication start and/or end point for certain data channels.

Figure 16 shows a UE QQ200 in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle, vehiclemounted or vehicle embedded/integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including narrow band internet of things (NB-loT) UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.

A UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, a 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).

The UE QQ200 includes processing circuitry QQ202 that is operatively coupled via a bus QQ204 to an input/output interface QQ206, a power source QQ208, a memory QQ210, a communication interface QQ212, and/or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 16. 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. The processing circuitry QQ202 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory QQ210. The processing circuitry QQ202 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, 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 QQ202 may include multiple central processing units (CPUs).

In the example, the input/output interface QQ206 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and/or output devices. Examples of an output device include 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. An input device may allow a user to capture information into the UE QQ200. Examples of an input device 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, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

In some embodiments, the power source QQ208 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source QQ208 may further include power circuitry for delivering power from the power source QQ208 itself, and/or an external power source, to the various parts of the UE QQ200 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source QQ208. Power circuitry may perform any formatting, converting, or other modification to the power from the power source QQ208 to make the power suitable for the respective components of the UE QQ200 to which power is supplied.

The memory QQ210 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable readonly memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory QQ210 includes one or more application programs QQ214, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data QQ216. The memory QQ210 may store, for use by the UE QQ200, any of a variety of various operating systems or combinations of operating systems.

The memory QQ210 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), 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 tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and/or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUlCC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory QQ210 may allow the UE QQ200 to access instructions, application programs and 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 as or in the memory QQ210, which may be or comprise a device-readable storage medium.

The processing circuitry QQ202 may be configured to communicate with an access network or other network using the communication interface QQ212. The communication interface QQ212 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna QQ222. The communication interface QQ212 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter QQ218 and/or a receiver QQ220 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter QQ218 and receiver QQ220 may be coupled to one or more antennas (e.g., antenna QQ222) and may share circuit components, software or firmware, or alternatively be implemented separately.

In the illustrated embodiment, communication functions of the communication interface QQ212 may include cellular communication, Wi-Fi communication, LPWAN communication, 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. Communications may be implemented in according to one or more communication protocols and/or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol/internet protocol (TCP/IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface QQ212, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.

A UE, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door/window sensor, a flood/moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smartwatch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an loT device comprises circuitry and/or software in dependence of the intended application of the loT device in addition to other components as described in relation to the UE QQ200 shown in Figure 16.

As yet another specific example, in an loT scenario, a UE 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 UE and/or a network node. The UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3GPP NB-loT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation.

In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed. The first and/or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

Figure 17 shows a network node QQ300 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a UE and/or with other network nodes or equipment, in a telecommunication 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)), O-RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU).

Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may 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, distributed units (e.g., in an O-RAN access node) 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).

Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, 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), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and/or Minimization of Drive Tests (MDTs). The network node QQ300 includes a processing circuitry QQ302, a memory QQ304, a communication interface QQ306, and a power source QQ308. The network node QQ300 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 the network node QQ300 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 NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node QQ300 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory QQ304 for different RATs) and some components may be reused (e.g., a same antenna QQ310 may be shared by different RATs). The network node QQ300 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node QQ300, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) 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 QQ300.

The processing circuitry QQ302 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 QQ300 components, such as the memory QQ304, to provide network node QQ300 functionality.

In some embodiments, the processing circuitry QQ302 includes a system on a chip (SOC). In some embodiments, the processing circuitry QQ302 includes one or more of radio frequency (RF) transceiver circuitry QQ312 and baseband processing circuitry QQ314. In some embodiments, the radio frequency (RF) transceiver circuitry QQ312 and the baseband processing circuitry QQ314 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 QQ312 and baseband processing circuitry QQ314 may be on the same chip or set of chips, boards, or units.

The memory QQ304 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 the processing circuitry QQ302. The memory QQ304 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and/or other instructions capable of being executed by the processing circuitry QQ302 and utilized by the network node QQ300. The memory QQ304 may be used to store any calculations made by the processing circuitry QQ302 and/or any data received via the communication interface QQ306. In some embodiments, the processing circuitry QQ302 and memory QQ304 is integrated.

The communication interface QQ306 is used in wired or wireless communication of signalling and/or data between a network node, access network, and/or UE. As illustrated, the communication interface QQ306 comprises port(s)/terminal(s) QQ316 to send and receive data, for example to and from a network over a wired connection. The communication interface QQ306 also includes radio front-end circuitry QQ318 that may be coupled to, or in certain embodiments a part of, the antenna QQ310. Radio front-end circuitry QQ318 comprises filters QQ320 and amplifiers QQ322. The radio front-end circuitry QQ318 may be connected to an antenna QQ310 and processing circuitry QQ302. The radio front-end circuitry may be configured to condition signals communicated between antenna QQ310 and processing circuitry QQ302. The radio front-end circuitry QQ318 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry QQ318 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters QQ320 and/or amplifiers QQ322. The radio signal may then be transmitted via the antenna QQ310. Similarly, when receiving data, the antenna QQ310 may collect radio signals which are then converted into digital data by the radio front-end circuitry QQ318. The digital data may be passed to the processing circuitry QQ302. In other embodiments, the communication interface may comprise different components and/or different combinations of components.

In certain alternative embodiments, the network node QQ300 does not include separate radio front-end circuitry QQ318, instead, the processing circuitry QQ302 includes radio front-end circuitry and is connected to the antenna QQ310. Similarly, in some embodiments, all or some of the RF transceiver circuitry QQ312 is part of the communication interface QQ306. In still other embodiments, the communication interface QQ306 includes one or more ports or terminals QQ316, the radio front-end circuitry QQ318, and the RF transceiver circuitry QQ312, as part of a radio unit (not shown), and the communication interface QQ306 communicates with the baseband processing circuitry QQ314, which is part of a digital unit (not shown).

The antenna QQ310 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. The antenna QQ310 may be coupled to the radio front- end circuitry QQ318 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In certain embodiments, the antenna QQ310 is separate from the network node QQ300 and connectable to the network node QQ300 through an interface or port.

The antenna QQ310, communication interface QQ306, and/or the processing circuitry QQ302 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by the network node. Any information, data and/or signals may be received from a UE, another network node and/or any other network equipment. Similarly, the antenna QQ310, the communication interface QQ306, and/or the processing circuitry QQ302 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and/or signals may be transmitted to a UE, another network node and/or any other network equipment.

The power source QQ308 provides power to the various components of network node QQ300 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source QQ308 may further comprise, or be coupled to, power management circuitry to supply the components of the network node QQ300 with power for performing the functionality described herein. For example, the network node QQ300 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source QQ308. As a further example, the power source QQ308 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

Embodiments of the network node QQ300 may include additional components beyond those shown in Figure 17 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, the network node QQ300 may include user interface equipment to allow input of information into the network node QQ300 and to allow output of information from the network node QQ300. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node QQ300.

Figure 18 is a block diagram of a host QQ400, which may be an embodiment of the host QQ116 of Figure 15, in accordance with various aspects described herein. As used herein, the host QQ400 may be or comprise various combinations hardware and/or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm. The host QQ400 may provide one or more services to one or more UEs.

The host QQ400 includes processing circuitry QQ402 that is operatively coupled via a bus QQ404 to an input/output interface QQ406, a network interface QQ408, a power source QQ410, and a memory QQ412. Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures 16 and 17, such that the descriptions thereof are generally applicable to the corresponding components of host QQ400.

The memory QQ412 may include one or more computer programs including one or more host application programs QQ414 and data QQ416, which may include user data, e.g., data generated by a UE for the host QQ400 or data generated by the host QQ400 for a UE. Embodiments of the host QQ400 may utilize only a subset or all of the components shown. The host application programs QQ414 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (WC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAG, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems). The host application programs QQ414 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network. Accordingly, the host QQ400 may select and/or indicate a different host for over- the-top services for a UE. The host application programs QQ414 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG- DASH), etc.

Figure 19 is a block diagram illustrating a virtualization environment QQ500 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 any device described herein, 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. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments QQ500 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment QQ500 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an 0-2 interface. Applications QQ502 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein.

Hardware QQ504 includes processing circuitry, memory that stores software and/or instructions executable by hardware processing circuitry, and/or other hardware devices as described herein, such as a network interface, input/output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers QQ506 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs QQ508a and QQ508b (one or more of which may be generally referred to as VMs QQ508), and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein. The virtualization layer QQ506 may present a virtual operating platform that appears like networking hardware to the VMs QQ508.

The VMs QQ508 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer QQ506. Different embodiments of the instance of a virtual appliance QQ502 may be implemented on one or more of VMs QQ508, and the implementations may be made in different ways. 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.

In the context of NFV, a VM QQ508 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 the VMs QQ508, and that part of hardware QQ504 that executes that VM, be it hardware dedicated to that VM and/or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs QQ508 on top of the hardware QQ504 and corresponds to the application QQ502.

Hardware QQ504 may be implemented in a standalone network node with generic or specific components. Hardware QQ504 may implement some functions via virtualization. Alternatively, hardware QQ504 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration QQ510, which, among others, oversees lifecycle management of applications QQ502. In some embodiments, hardware QQ504 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes 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. In some embodiments, some signalling can be provided with the use of a control system QQ512 which may alternatively be used for communication between hardware nodes and radio units.

Figure 20 shows a communication diagram of a host QQ602 communicating via a network node QQ604 with a UE QQ606 over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE (such as a UE QQ112a of Figure 15 and/or UE QQ200 of Figure 16), network node (such as network node QQ110a of Figure 15 and/or network node QQ300 of Figure 17), and host (such as host QQ116 of Figure 15 and/or host QQ400 of Figure 18) discussed in the preceding paragraphs will now be described with reference to Figure 20.

Like host QQ400, embodiments of host QQ602 include hardware, such as a communication interface, processing circuitry, and memory. The host QQ602 also includes software, which is stored in or accessible by the host QQ602 and executable by the processing circuitry. The software includes a host application that may be operable to provide a service to a remote user, such as the UE QQ606 connecting via an over-the-top (OTT) connection QQ650 extending between the UE QQ606 and host QQ602. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection QQ650.

The network node QQ604 includes hardware enabling it to communicate with the host QQ602 and UE QQ606. The connection QQ660 may be direct or pass through a core network (like core network QQ106 of Figure 15) and/or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network may be a backbone network or the Internet.

The UE QQ606 includes hardware and software, which is stored in or accessible by UE QQ606 and executable by the UE’s processing circuitry. The software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE QQ606 with the support of the host QQ602. In the host QQ602, an executing host application may communicate with the executing client application via the OTT connection QQ650 terminating at the UE QQ606 and host QQ602. In providing the service to the user, the UE's client application may receive request data from the host's host application and provide user data in response to the request data. The OTT connection QQ650 may transfer both the request data and the user data. The UE's client application may interact with the user to generate the user data that it provides to the host application through the OTT connection QQ650.

The OTT connection QQ650 may extend via a connection QQ660 between The host QQ602 and the network node QQ604 and via a wireless connection QQ670 between the network node QQ604 and the UE QQ606 to provide the connection between the host QQ602 and the UE QQ606. The connection QQ660 and wireless connection QQ670, over which the OTT connection QQ650 may be provided, have been drawn abstractly to illustrate the communication between the host QQ602 and the UE QQ606 via the network node QQ604, without explicit reference to any intermediary devices and the precise routing of messages via these devices.

As an example of transmitting data via the OTT connection QQ650, in step QQ608, the host QQ602 provides user data, which may be performed by executing a host application. In some embodiments, the user data is associated with a particular human user interacting with the UE QQ606. In other embodiments, the user data is associated with a UE QQ606 that shares data with the host QQ602 without explicit human interaction. In step QQ610, the host QQ602 initiates a transmission carrying the user data towards the UE QQ606. The host QQ602 may initiate the transmission responsive to a request transmitted by the UE QQ606. The request may be caused by human interaction with the UE QQ606 or by operation of the client application executing on the UE QQ606. The transmission may pass via the network node QQ604, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step QQ612, the network node QQ604 transmits to the UE QQ606 the user data that was carried in the transmission that the host QQ602 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step QQ614, the UE QQ606 receives the user data carried in the transmission, which may be performed by a client application executed on the UE QQ606 associated with the host application executed by the host QQ602.

In some examples, the UE QQ606 executes a client application which provides user data to the host QQ602. The user data may be provided in reaction or response to the data received from the host QQ602. Accordingly, in step QQ616, the UE QQ606 may provide user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from the user via an input/output interface of the UE QQ606. Regardless of the specific manner in which the user data was provided, the UE QQ606 initiates, in step QQ618, transmission of the user data towards the host QQ602 via the network node QQ604. In step QQ620, in accordance with the teachings of the embodiments described throughout this disclosure, the network node QQ604 receives user data from the UE QQ606 and initiates transmission of the received user data towards the host QQ602. In step QQ622, the host QQ602 receives the user data carried in the transmission initiated by the UE QQ606.

One or more of the various embodiments improve the performance of OTT services provided to the UE QQ606 using the OTT connection QQ650, in which the wireless connection QQ670 forms the last segment. More precisely, the teachings of these embodiments may improve caching of data and thereby provide benefits such as reduced user waiting time, better responsiveness, and/or extended battery lifetime.

In an example scenario, factory status information may be collected and analyzed by the host QQ602. As another example, the host QQ602 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, the host QQ602 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, the host QQ602 may store surveillance video uploaded by a UE. As another example, the host QQ602 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs. As other examples, the host QQ602 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing and/or transmitting data.

In some examples, 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 the OTT connection QQ650 between the host QQ602 and UE QQ606, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host QQ602 and/or UE QQ606. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection QQ650 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 may compute or estimate the monitored quantities. The reconfiguring of the OTT connection QQ650 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node QQ604. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signalling that facilitates measurements of throughput, propagation times, latency and the like, by the host QQ602. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection QQ650 while monitoring propagation times, errors, etc.

Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information 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. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and/or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.

In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer- readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry 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 non-transitory computer- readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and/or by end users and a wireless network generally.

It will be appreciated that the foregoing description and the accompanying drawings represent non-limiting examples of the methods and apparatus taught herein. As such, the apparatus and techniques taught herein are not limited by the foregoing description and accompanying drawings. Instead, the embodiments herein are limited only by the following claims and their legal equivalents.

Claims

1. A method performed by a second network node (16) for handling data in a communication network (1), the method comprising: adding (303) data to be cached to a first message; transmitting (304) to a first network node (15) the first message with the data to be cached; and receiving (305) from the first network node (15) a second message with the data from the first message and thereby store and retrieve the data without using a local memory at the second network node.

2. The method according to claim 1, wherein the first message and/or the second message comprises additional information.

3. The method according to claim 2, wherein the additional information comprises an indication of limitation of data amount to cache, identity of a network node, and/or a type of service.

4. The method according to any of the claims 1-3, wherein the second message comprises data from the first network node (15) to be cached by the second network node (16) and the method further comprises transmitting (307) a third message to the first network node (15) carrying the data from the first network node (15).

5. The method according to any of the claims 1-4, further comprising obtaining (302) the data to be cached by determining the data, being preconfigured with the data, retrieving the data from within, and/or receiving data from another network node.

6. The method according to any of the claims 1-5, further comprising processing (307) the second message taking the data in the second message into account.

7. The method according to any of the claims 1-6, wherein the data is transported in a header or payload in respective message.

8. A method performed by a first network node (15) for handling data in a communication network (1), the method comprising: receiving (402) from a second network node (16) a first message with data to be cached; storing (403) the data; adding (404) the data of the first message into a second message; and transmitting (405) the second message to the second network node 16, wherein the second message comprises the data of the first message and thereby the data is stored and retrieved without using a local memory at the second network node.

9. The method according to claim 8, wherein the first message and/or the second message comprises additional information.

10. The method according to claim 9, wherein the additional information comprises an indication of limitation of data amount to cache, identity of a network node, and/or a type of service.

11. The method according to any of the claims 9-10, further comprising adding (404) the additional data, or changing, and adding the changed additional data to the second message.

12. The method according to any of the claims 8-11 , further comprising adding (405) own data to the second message to be cached by the second network node (16); and receiving (407) a third message from the second network node (16) carrying the own data.

13. The method according to any of the claims 8-12, wherein data is transported in a header or payload in respective message.

14. A second network node (16) for handling data in a communication network (1), wherein the second network node is configured to: add data to be cached to a first message; transmit to a first network node (15) the first message with the data to be cached; and receive from the first network node (15) a second message with the data from the first message and thereby store and retrieve the data without using a local memory at the second network node.

15. A first network node (15) for handling data in a communication network (1), wherein the first network node is configured to: receive from a second network node (16) a first message with data t be cached; store the data; add the data of the first message into a second message; and transmit the second message to the second network node (16), wherein the second message comprises the data of the first message and thereby the data is stored and retrieved without using a local memory at the second network node.

16. A computer program product comprising instructions, which, when executed on at least one processor, cause the at least one processor to carry out any of the methods according to any of the claims 1-13, as performed by the first network node and the second network node, respectively.

17. A computer-readable storage medium, having stored thereon a computer program comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out the method according to any of the claims 1-13, as performed by the first network node and the second network node, respectively.