Server node, client node and methods in a wireless communications network

Abstract

NOT VISIBLE DUE TO STATUS OF PATENT

Description

[0001] SERVER NODE, CLIENT NODE AND METHODS IN A WIRELESS COMMUNICATIONS

[0002] NETWORK

[0003] TECHNICAL FIELD

[0004] Embodiments herein relate to a server node, a client node and methods performed therein regarding wireless communication. Furthermore, a computer program product and a computer-readable storage medium are also provided herein. Especially, embodiments herein relate to handling or enabling communication, such as managing data delivery, in a communication network.

[0005] BACKGROUND

[0006] In a typical wireless communication network, wireless devices, also known as wireless communication devices, mobile stations, stations (STA) and / or User Equipment (UE), communicate via a Wide Area Network or a Local Area Network such as a Wi-Fi network or a cellular network comprising a Radio Access Network (RAN) part and a Core Network (CN) part. The RAN covers a geographical area which is divided into service areas or cell areas, which may also be referred to as a beam or a beam group, with each service area or cell area being served by a radio network node such as a radio access node e.g., a Wi-Fi access point, a Base Station (BS) or a radio base station (RBS), which in some networks may also be denoted, for example, a Base Station (BS), a NodeB, eNodeB (eNB), or gNodeB (gNB) as denoted in Fifth Generation (5G) telecommunications. A service area or cell area is a geographical area where radio coverage is provided by the radio network node. The radio network node communicates over an air interface operating on a radio frequency with the wireless devices within the range of the radio network node.

[0007] 3rd Generation Partnership Project (3GPP) is the standardization body for specifying the standards for the cellular system evolution, e.g., including 3G, 4G, 5G and the future evolutions. Specifications for Evolved Universal Terrestrial Radio Access (E- UTRA) and Evolved Packet System (EPS) have been completed within the 3GPP. In 4G also called a Fourth Generation (4G) network, EPS is core network and E-UTRA is radio access network. In 5G, 5GC is core network, NR is radio access network. As a continued network evolution, the new release of 3GPP specifies a 5G network also referred to as 5G New Radio (NR) and 5G Core (5GC). Frequency bands for 5G NR are being separated into two different frequency ranges, Frequency Range 1 (FR1) and Frequency Range 2 (FR2). FR1 comprises sub-6 GHz frequency bands. Some of these bands are bands traditionally used by legacy standards but have been extended to cover potential new spectrum offerings from 410 MHz to 7125 MHz. FR2 comprises frequency bands from 24.25 GHz to 52.6 GHz. Bands in this millimeter wave range have shorter range but higher available bandwidth than bands in the FR1.

[0008] Multi-antenna techniques may significantly increase the data rates and reliability of a wireless communication system. For a wireless connection between a single user, such as UE, and a base station (BS), the performance is in particular improved if both the transmitter and the receiver are equipped with multiple antennas, which results in a Multiple-Input Multiple-Output (MIMO) communication channel. This may be referred to as Single-User (SU)-MIMO. In the scenario where MIMO techniques is used for the wireless connection between multiple users and the base station, MIMO enables the users to communicate with the base station simultaneously using the same time-frequency resources by spatially separating the users, which increases further the cell capacity. This may be referred to as Multi-User (MU)-MIMO. Note that MU-MIMO may benefit when each UE only has one antenna. The cell capacity can be increased linearly with respect to the number of antennas at the BS side. Due to that, more and more antennas are employed in BS. Such systems and / or related techniques are commonly referred to as massive MIMO.

[0009] In addition to faster peak Internet connection speeds, 5G planning aims at higher capacity than current 4G, allowing higher number of mobile broadband users per area unit, and allowing consumption of higher or unlimited data quantities in gigabyte per month and user. This would make it feasible for a large portion of the population to stream high-definition media many hours per day with their mobile devices, when out of reach of Wi-Fi hotspots. 5G research and development also aims at improved support of machine to machine communication, also known as the Internet of things, aiming at lower cost, lower battery consumption and lower latency than 4G equipment.

[0010] Service Architecture Enabler Layer (SEAL) is an architecture over 3GPP networks which exposes network capabilities for vertical applications, such as Vehicle to Anything (V2X), Unmanned Aireal Vehicle (UAV) and / or Industrial Internet of Things (lloT) applications. SEAL consists of a set of common services, e.g., group management, key management, network resource management, which can be used by vertical applications and ease the development.

[0011] The Service Enabler Architecture Layer Data Delivery (SEALDD) service is a new SEAL service introduced in 3GPP Release-18 to ease the data delivery demands for vertical applications. The Vertical Applications Layer (VAL) client / server may currently utilize the SEALDD service for the following services:

[0012] • SEALDD regular connection management,

[0013] • SEALDD enabled E2E redundant transmission,

[0014] • SEALDD server discovery and selection,

[0015] • SEALDD enabled data storage,

[0016] • SEALDD server relocation,

[0017] • SEALDD enabled data transmission quality measurement,

[0018] • SEALDD enabled rate control for VAL applications,

[0019] • SEALDD enabled data transmission quality guarantee, and

[0020] • SEALDD policy configuration.

[0021] An architectural overview of SEALDD is shown in Figure 1 , present as Figure 7.2- 3 in clause 7.2 of 3GPP TS 23.433 v19.0.0.

[0022] The SEALDD client and server may communicate through an interconnecting interface and thus ease the data delivery for the VAL client and VAL server. SEAL services can also utilize the SEAL-X interface to communicate with other SEAL services.

[0023] Similarly, the architecture of the SEAL service SEAL Network Resource Management (NRM) is shown in Figure 2, present as Figure 14.2.2.1-1 in clause 14.2.2.1 of 3GPP TS 23.434 v19.0.0.

[0024] The SEAL NRM supports a variety of procedures including the Background Data Transfer (BDT) configuration, described in clause 14.3.13 of 3GPP TS 23.434 v19.0.0, and the Unicast resource management, described in clause 14.3.3.3 of 3GPP TS 23.434 v19.0.0, which both are of interest.

[0025] The BDT configuration procedure consist of capabilities such as:

[0026] • “Request and Select Background Data Transfer Policy”,

[0027] • “Reselect Background Data Transfer Policy”,

[0028] • “BDT configuration get”,

[0029] • “BDT configuration update”, and

[0030] • “BDT configuration delete”.

[0031] The VAL server can request functionality related to the BDT flow and the SEAL NRM server performs the actions towards the 3GPP network. The “Unicast resource management” procedure also consists of a variety of capabilities, such as the “Network resource adaptation” The VAL server can then utilize the NRM server to enforce resource adaptations for certain traffic flows.

[0032] SUMMARY

[0033] As part of developing embodiments herein a problem was identified by the inventor and will first be discussed.

[0034] Currently, the only support for setting up BDT flows is when the VAL server requests this service from the SEAL NRM server, since the NRM server is able to negotiate BDT policies with the 3GPP network. The VAL server also has to negotiate the network resource adaptation with the SEAL NRM server and then after setting everything it is able to send the data at the negotiated time.

[0035] Using the existing technology, the VAL server is required to perform multiple steps before being able to send the BDT data. As the demands of the applications consumptions and transmitted data is growing, the mobile network needs to be simplified. The VAL applications also have diverse requirements which affects delivery of data and how the content should be distributed.

[0036] An object of embodiments herein is, thus, to provide a mechanism that improves the performance of a wireless communication network.

[0037] According to an aspect of embodiments herein, the object is achieved by a method performed by a server node, such as a SEALDD server, for handling data delivery in a wireless communication network.

[0038] The server node negotiates a background data transfer, BDT, configuration policy and / or network resource adaptation with a network resource management server, for data to be transferred.

[0039] The server node sends data in a BDT using the negotiated BDT configuration policy and / or network resource adaptation.

[0040] According to another aspect of embodiments herein, the object is achieved by a method performed by a requesting node, such as a SEALDD client or a VAL server, for handling data delivery in a wireless communication network.

[0041] The requesting node requests a server node, such as a SEALDD server, to perform a background data transfer, BDT. The request comprises any one or more out of: - one or more identifiers indicating recipients of the BDT data,

[0042] - data to be delivered in the BDT,

[0043] - an indication indicating a location of the data to be obtained and delivered in the BDT, and

[0044] - a storage expiration time indicating the expiration or time validity of the stored BDT data.

[0045] According to another aspect of embodiments herein, the object is achieved by a server node, such as a SEALDD server, configured to handle data delivery in a wireless communication network.

[0046] The server node is configured to negotiate a background data transfer, BDT, configuration policy and / or network resource adaptation with a network resource management server, for data to be transferred.

[0047] The server node is configured to send data in a BDT using the negotiated BDT configuration policy and / or network resource adaptation.

[0048] According to another aspect of embodiments herein, the object is achieved by a requesting node, such as a SEALDD client or a VAL server, configured to handle data delivery in a wireless communication network.

[0049] The requesting node is configured to request a server node, such as a SEALDD server, to perform a background data transfer, BDT. The request is adapted comprise any one or more out of:

[0050] - one or more identifiers adapted to indicate recipients of the BDT data,

[0051] - data to be delivered in the BDT,

[0052] - an indication adapted to indicate a location of the data to be obtained and delivered in the BDT, and

[0053] - a storage expiration time adapted to indicate the expiration or time validity of the stored BDT data.

[0054] It is herein proposed a solution where the SEALDD may offload the data delivery demands from the VAL client / server. The SEALDD server will handle the negotiation with SEAL NRM for BDT flows and network resource adaptation. The SEALDD may also offload the VAL client / server by receiving and storing the application data which shall be sent at a later stage. Thus, this will result in an improved performance of the wireless communication network. BRIEF DESCRIPTION OF THE DRAWINGS

[0055] Examples of embodiments herein are described in more detail with reference to attached drawings in which:

[0056] Figure 1 is a schematic overview of an Architecture for SEAL Data Delivery Service according to prior art.

[0057] Figure 2 is a schematic overview of a generic on-network functional model of SEAL according to prior art.

[0058] Figure 3 a schematic overview of a wireless communication network according to embodiments herein.

[0059] Figure 4 is a flowchart depicting embodiments of a method in a server node.

[0060] Figure 5 is a flowchart depicting embodiments of a method in a requesting node.

[0061] Figure 6 a combined flowchart and signalling scheme according to embodiments herein.

[0062] Figure 7 a combined flowchart and signalling scheme according to embodiments herein.

[0063] Figure 8 a combined flowchart and signalling scheme according to embodiments herein.

[0064] Figure 9 a combined flowchart and signalling scheme according to embodiments herein.

[0065] Figure 10 a combined flowchart and signalling scheme according to embodiments herein.

[0066] Figure 11 is a schematic block diagram illustrating embodiments of a server node.

[0067] Figure 12 is a schematic block diagram illustrating embodiments of a requesting node.

[0068] Figure 13 shows an example of a communication system QQ100 in accordance with some embodiments.

[0069] Figure 14 shows a UE QQ200 in accordance with some embodiments.

[0070] Figure 15 shows a network node QQ300 in accordance with some embodiments.

[0071] Figure 16 is a block diagram of a host QQ400, which may be an embodiment of the host QQ116 of Figure 13, in accordance with various aspects described herein.

[0072] Figure 17 is a block diagram illustrating a virtualization environment QQ500 in which functions implemented by some embodiments may be virtualized. Figure 18 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.

[0073] DETAILED DESCRIPTION

[0074] Embodiments herein are described within the context of 3GPP NR radio technology. It is understood that the problems and solutions described herein are equally applicable to wireless access networks and UEs implementing other access technologies and standards. NR is used as an example technology where embodiments are suitable, and using NR in the description therefore is particularly useful for understanding the problem and solutions solving the problem. In particular, embodiments are applicable also to 6G, 3GPP LTE, or 3GPP LTE and NR integration, also denoted as non-standalone NR.

[0075] According to embodiments herein, a new solution to enable the SEALDD functionality for SEALDD Background data transfer is provided. Examples of embodiments herein may provide new procedures for e.g.,:

[0076] • “SEALDD Background data transfer in DL direction” for DL centric data, the VAL server requests BDT flow with desired parameters and may either send the application data directly to the SEALDD server, and optionally store it, or inform the SEALDD server where to fetch the data. The SEALDD server negotiates BDT requirements, and network resource adaptation with the SEAL NRM server. The BDT data is then transferred to the VAL client.

[0077] • “SEALDD Background data transfer in UL direction” for UL centric data, the SEALDD client requests BDT flow with desired parameters and may inform the SEALDD server where to fetch the application data or send it at a later stage. The SEALDD server negotiates BDT and network resource adaptation with the SEAL NRM server. The BDT data is then transferred to the VAL server.

[0078] • “SEALDD Background data transfer subscription update”, the VAL server or SEALDD client can request to update the desired parameters for the BDT flow. The SEALDD server will negotiate the new parameters with the NRM server for the BDT flow(s) and network resource adaptation.

[0079] • “SEALDD Background data transfer unsubscribe”. The VAL server or SEALDD client request to delete a BDT flow. Further, examples of embodiments herein may provide new information flows, such as messages, e.g.,:

[0080] • “SEALDD Background data transfer in DL direction subscription request”,

[0081] • “SEALDD Background data transfer in UL direction subscription request”,

[0082] • “SEALDD Background data transfer subscription response”,

[0083] • “SEALDD Background data transfer notification”,

[0084] • “SEALDD Background data transfer update subscription request”,

[0085] • “SEALDD Background data transfer update subscription response”,

[0086] • “SEALDD Background data transfer unsubscribe request”,

[0087] • “SEALDD Background data transfer unsubscribe response”.

[0088] Further, examples of embodiments herein may provide new procedures for e.g.,:

[0089] • NRM service API for network resource adaptation is enhanced with BDT reference.

[0090] The solution according to embodiments herein introduces a combination of different existing capabilities to enhance BDT and add a new service for the SEALDD. The existing capabilities include support for BDT in SEAL NRM, Network resource adaptation in SEAL NRM, data storage in SEALDD and transmission quality monitoring. The solution combines these functionalities which gives the VAL server or VAL client a range of options to use BDT. The new solution enables the VAL server / client to utilize the data storage capability of SEALDD, and thus store the application data securely at the SEALDD before transmitting. The new solution also offloads the VAL client / server, as the SEALDD server will handle the BDT and Network resource negotiation with the SEAL NRM.

[0091] Embodiments herein may bring the advantage that the SEALDD may offload the data delivery demands from the VAL client / server. The SEALDD server will handle the negotiation with SEAL NRM for BDT flows and Network resource adaptation. The SEALDD may also offload the VAL client / server by receiving and storing the application data which shall be sent at a later stage.

[0092] Embodiments herein relate to wireless communication networks in general. Fig. 3 is a schematic overview depicting a wireless communication network 100. The wireless communication network 100 comprises one or more RANs and one or more CNs. The wireless communication network 100 may use one or a number of different technologies. Embodiments herein relate to recent technology trends that are of particular interest in a NR context, however, embodiments are also applicable in further developments of existing wireless communications systems such as e.g. 6G, LTE or WCDMA. In the wireless communication network 1 , a user equipment (UE) 121, such as a mobile station, a wireless device, a non-access point (non-AP) STA, a STA, and / or a wireless terminal, is communicating via, e.g., one or more Access Networks (AN), e.g., RAN, to one or more CNs. It should be understood by the skilled in the art that “UE” is a non-limiting term which means any terminal, wireless communications terminal or device, user equipment, narrowband (NB)- internet of things (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 network node within an area served by the network node.

[0093] The wireless communication network 10 comprises a radio network node 101 , e.g., 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 stand-alone access point, or any other network unit or node capable of communicating with a UE within a service area 11 , such as a cell, served by the network node 101 depending e.g., on a radio access technology and terminology used. The service area 11 may also be referred to as a cell, a beam or a beam group of a first radio access technology (RAT), such as 6G, 5G, LTE, Wi-Fi, or similar. The radio network node 101 may be associated with a first Public Land Mobile Network (PLMN) and / or a first NonPublic Network (NPN).

[0094] The wireless communication network 100 further comprises a network node 110 handling service data. The network node 110 may comprise a VAL server 112 and a SEALDD server, also referred to as server node 111. It should be understood that these nodes may be separated nodes or co-located nodes.

[0095] The UE 10 may comprise a VAL client 122 and a SEALDD client, also referred to as a client node 121. It should be understood that these clients may be separated clients or co-located clients.

[0096] The wireless communications network 100 further comprises a network resource manager server 130. The network resource manager server 130

[0097] Methods herein may be performed by the server node 121 and a requesting node 112, 121 . The requesting node 112, 121 may comprise any one of a SEALDD client such as the client node 121 or the VAL server 112. As an alternative, a Distributed Node (DN) and functionality, e.g. comprised in the cloud 190 as shown in Figure 3, may be used for performing or partly performing the methods herein.

[0098] A method according to embodiments herein will now be described from the view of the server node 111 , together with Figure 4. Figure 4 depicts example embodiments of a method performed by the server node 111 , such as SEALDD server, handling data delivery in the wireless communication network 100. The method comprises the following actions, which actions may be taken in any suitable order. Actions that are optional are presented in dashed boxes in Figure 4.

[0099] Action 401

[0100] In some embodiments, the server node 111 receives a BDT request for a BDT. The BDT request is received from any one out of the VAL server 112, or the client node 121. The BDT request may also be referred to a SEALDD BDT subscription request. The BDT request may be for BDT in the DL direction, e.g., when received from the VAL server 112. Alternatively, the BDT request may be for BDT in the UL direction, e.g., when received from the client node 121 .

[0101] The BDT request comprises any one or more out of one or more identifiers indicating recipients of the BDT data, data to be delivered in the BDT, an indication indicating a location of the data to be obtained and delivered in the BDT, and a storage expiration time indicating the expiration or time validity of the stored BDT data. Further, the BDT request may comprise any one or more of the information elements (IE) indicated in table 9.X.3.1-1 below. The information elements indicated in table 9.X.3.1-1 may e.g., comprise a VAL service ID IE, a list of VAL UE IDs IE, a VAL group ID IE, a desired time window IE, a desired area information IE, a policy selection guidance IE, data length IE, a storage expiration time IE, an application payload address IE and / or an application payload IE.

[0102] Action 402

[0103] The server node 111 negotiates a BDT configuration policy, such as BDT requirements, and / or network resource adaptation with the resource management server 130, for data to be transferred.

[0104] Action 403

[0105] In some embodiments, the server node 111 sends a BDT response in response to the BDT request. The BDT response may comprise any one or more out of a BDT subscription identifier, and a granted time window for the BDT. Further, the BDT response may comprise a result associated negotiation. The server node 111 may e.g., send the BDT response when the negotiation is completed. The BDT response may also be referred to a SEALDD BDT subscription response. The BDT response may be sent to the VAL server 112 or the client node 121. This based on whether the BDT request was received from the VAL server 112 or the client node 121.

[0106] Action 404

[0107] In some embodiments, the first server node 111 obtains data to be transfer in the BDT from a location indicated in the BDT request. The location may e.g., be the VAL server 112, the client node 121 or another server or node in the wireless communication network 100, or at least connected to the wireless communication network 100.

[0108] Action 405

[0109] The server node 111 sends data in a BDT using or applying the negotiated BDT configuration policy, such as BDT requirements, and / or network resource adaptation. The data may be sent to a recipient comprising any one out of the VAL client 122, or the VAL server 112.

[0110] Action 406

[0111] In some embodiments, the server node 111 sends a BDT notification, e.g., after performing the BDT. The BDT notification may comprise any one or more out of a BDT subscription identifier, an executed time window, one or more identifiers indicating recipients of the BDT data, and a BDT transmission quality. The BDT notification may also be referred to a SEALDD BDT notification. The BDT notification may be sent to the VAL server 112 or the client node 121. This based on whether the BDT request was received from the VAL server 112 or the client node 121.

[0112] Action 407

[0113] In some embodiments, the server node 111 receives an update request to update the negotiated BDT configuration policy, such as BDT requirements, and / or network resource adaptation. The update request may also be referred to a SEALDD BDT subscription update request. The update request may, be received from the VAL server 112 or the client node 121 . This based on whether the BDT request was received from the VAL server 112 or the client node 121 . The update request may e.g., comprise one or more parameters associated with any one or more of the information elements indicated in table 9.X.3.5-1 below. The information elements indicated in table 9.X.3.5-1 may e.g., comprise a BDT subscription identifier IE, a desired time window IE, a desired area information IE, a policy guidance selection IE, a data length IE and / or a storage expiration time IE.

[0114] Action 408 In some embodiments, the server node 111 renegotiates the BDT configuration policy, such as BDT requirements, and / or network resource adaptation with a network resource management server. The renegotiation may e.g., take any parameter comprised in the update request into account.

[0115] The server node 111 may send an update response when the renegotiation is complete. The update response may also be referred to a SEALDD BDT subscription update response. The update response may be sent to the VAL server 112 or the client node 121. This based on whether the update request was received from the VAL server 112 or the client node 121 . The update response may comprise any one or more out of the BDT subscription identifier, and a granted time window for the BDT. Further, the update response may comprise a result associated with the request.

[0116] Action 409

[0117] In some embodiments, the server node 111 receives an unsubscribe request to unsubscribe from the BDT configuration policy. The unsubscribe request may also be referred to a SEALDD BDT unsubscribe request. The unsubscribe request may be received from the VAL server 112 or the client node 121. This based on whether the BDT request was received from the VAL server 112 or the client node 121. The update request may e.g., comprise the BDT subscription identifier.

[0118] Action 410

[0119] In some embodiments, the server node 111 renegotiates the BDT configuration policy, such as BDT requirements, with the network resource management server 130. The renegotiation comprises deleting the BDT configuration.

[0120] The server node 111 may send an unsubscribe response when the renegotiation is complete. The unsubscribe response may also be referred to a SEALDD BDT unsubscribe response. The unsubscribe response may be sent to the VAL server 112 or the client node 121 . This based on whether the unsubscribe request was received from the VAL server 112 or the client node 121 .

[0121] A method according to embodiments herein will now be described from the view of the requesting node 112, 121 , together with Figure 5. Figure 5 depicts example embodiments of a method performed by the requesting node 112, 121 , such as a SEALDD client or a VAL server, handling data delivery in the wireless communication network 100. The requesting node 112, 121 may e.g., comprise any one out of the VAL server 112 or the client node 121 , such as a SEALDD client. The method comprises the following actions, which actions may be taken in any suitable order. Actions that are optional are presented in dashed boxes in Figure 5.

[0122] Action 501

[0123] The requesting node 112, 121 requests the server node 111 , such as a SEALDD server, to perform a BDT, e.g., by sending a BDT request. The request comprises any one or more out of one or more identifiers indicating recipients of the BDT data, data to be delivered in the BDT, an indication indicating a location of the data to be obtained and delivered in the BDT, and a storage expiration time indicating the expiration or time validity of the stored BDT data. Further, the BDT request may comprise any one or more of the IE indicated in table 9.X.3.1-1 below. The information elements indicated in table 9.X.3.1-1 may e.g., comprise a VAL service ID IE, a list of VAL UE IDs IE, a VAL group ID IE, a desired time window IE, a desired area information IE, a policy selection guidance IE, data length IE, a storage expiration time IE, an application payload address IE and / or an application payload IE. The BDT request may also be referred to a SEALDD BDT subscription request. The BDT request may be for BDT in the DL direction, e.g., when the requesting node 112, 121 comprises the VAL server 112. Alternatively, the BDT request may be for BDT in the UL direction, e.g., when the requesting node 112, 121 comprises the client node 121.

[0124] The recipient may comprise any one out of the VAL client 122, or the VAL server 112.

[0125] Action 502

[0126] In some embodiments, the requesting node 112, 121 receives, from the server node 111 , a BDT response in response to the BDT request. The BDT response may comprise any one or more out of a BDT subscription identifier, and a granted time window for the BDT. Further, the BDT response may comprise a result associated with a negotiation for a BDT configuration policy, such as BDT requirements, and / or network resource adaptation performed by the server node 111 in response to the BDT request. The requesting node 112, 121 may e.g., receive the BDT response when the negotiation is completed. The BDT response may also be referred to a SEALDD BDT subscription response.

[0127] Action 503

[0128] In some embodiments, the requesting node 112, 121 receives a BDT notification from the server node. The BDT notification may comprise any one or more out of a BDT subscription identifier, an executed time window, one or more identifiers indicating recipients of the BDT data, and a BDT transmission quality. The BDT notification may also be referred to a SEALDD BDT notification. The BDT notification may be received when the BDT data delivery has been performed by the server node 111 , such as when the sever node has sent the BDT data.

[0129] Action 504

[0130] In some embodiments, the requesting node 112, 121 requests the server node 111 to perform an update to the negotiated BDT configuration policy, such as BDT requirements, and / or network resource adaptation, such as sending an update request to the server node 111. The update request may also be referred to a SEALDD BDT subscription update request. The update request may e.g., comprise one or more parameters associated with any one or more of the information elements indicated in table 9.X.3.5-1 below. The information elements indicated in table 9.X.3.5-1 may e.g., comprise a BDT subscription identifier IE, a desired time window IE, a desired area information IE, a policy guidance selection IE, a data length IE and / or a storage expiration time IE.

[0131] The requesting node 112, 121 may receive an update response from the server node 111 in response to the update request. The update response may comprise any one or more out of the BDT subscription identifier, and a granted time window for the BDT. Further, the update response may comprise a result associated with the update request, such as a result associated with a renegotiation for the BDT configuration policy, such as BDT requirements, and / or network resource adaptation performed by the server node 111 in response to the update request. The update response may also be referred to a SEALDD BDT subscription update response.

[0132] Action 505

[0133] In some embodiments, the requesting node 112, 121 requests the server node 111 to unsubscribe the requesting node 112, 121 from the negotiated BDT configuration policy, such as BDT requirements, such as sending an unsubscribe request to the server node 111. The unsubscribe request may also be referred to a SEALDD BDT unsubscribe request.

[0134] The requesting node 112, 121 may receive an unsubscribe response from the server node 111 in response to the unsubscribe request, e.g., when a renegotiation for the BDT configuration policy, such as BDT requirements, and / or network resource adaptation performed by the server node 111 is complete. The unsubscribe response may also be referred to a SEALDD BDT unsubscribe response.

[0135] Proposed changes in 3GPP TS 23.434 underlined: 14.3.2.1 Network resource adaptation request

[0136] Table 14.3.2.1-1 describes the information flow network resource adaptation request from the VAL / SEALDD server to the NRM server.

[0137] Table 14.3.2.1-1 : Network resource adaptation request

[0138] 14.3.3.3.1.2 Procedure

[0139] Figure 6: Procedure for the network resource adaptation

[0140] 1. The VAL server (or SEALDD server) sends a network resource adaptation request to the NRM server for one or more users belonging to one or more VAL services, and may comprise one or more VAL UEs that will have updated resource requirement. This requirement may be in the form of exact resources / resource pools to be used or indication of bandwidth increase / decrease for the corresponding VAL UEs or set of VAL UEs. The BDT Reference ID may also be included for setting BDT policies.

[0141] 2. The NRM server processes the request and applies / enforces the resource adaptation per VAL UE.

[0142] 3. The NRM server retrieves UE IP address by using event monitoring capability for PDU session status (or PDN connectivity status) and initiates the PCC procedures for each VAL UE.

[0143] 4. The NRM server provides a network resource adaptation response to the VAL server (or SEALDD server), providing information on the fulfilment of the network resource adaptation request. This will include information either per VAL UE or per set of VAL UEs, as indicated by the request of the VAL server in step 1.

[0144] Proposed changes in 3GPP TS 23.433 underlined: 9.x SEALDD Background data transfer

[0145] 9.x.1 General

[0146] The following clauses specify procedures and information flow for SEALDD Background data transfer (BDT'). The SEALDD supports BDT in downlink (DL') direction, e.g.. streaming a video clip to the VAL client, and in uplink (UL') direction, e.g.. uploading drone captured data to the VAL server.

[0147] 9.x.2 Procedures

[0148] 9.X.2.1 _ SEALDD Background data transfer in DL direction

[0149] Figure 9.X.2.1-1 illustrates the procedure for SEALDD Background data transfer in DL direction.

[0150] Figure 7: SEALDD Background data transfer in DL direction

[0151] 1. The VAL server sends a SEALDD Background data transfer in DL direction subscription request to the SEALDD server. The request includes the VAL service ID and list of VAL UE IDs or VAL group ID and may also include desired time window, desired area information (e.g.. when a UE enters a geographical areal. Policy Selection Guidance, data length, and storage expiration time. The VAL server may include the application data directly in the request or specify where the SEALDD server can fetch the data.

[0152] 2. The SEALDD server authorizes the request from the VAL server and stores the payload received securely or fetches the payload, based on parameters received in step 1.

[0153] NOTE 1 : The VAL payload can be encrypted when stored in DD layer, in cases the VAL and the DD layers are provided by different vendors. Security requirements for storing data in the DD layer are within SA3 scope.

[0154] 3. The SEALDD server starts the BDT configuration negotiation with the SEAL NRM server as described in clause 14.3.13 of TS 23.434(41. The SEALDD server performs Network resource adaptation negotiation with the SEAL NRM server as described in clause 14.3.3.3 of TS 23.434(4]. Policies are set for the BDT data transfer using the previously negotiated BDT Reference ID

[0155] NOTE 2: The BDT policy can also be set for a future session via NEF ApplyPolicy by SEALDD server at the end of the BDT negotiation.

[0156] NOTE 3 : If there is any change in the network impacting the current BDT policy ( i.e. BDT warning notification from CN or trigger from the VAL server'). SEALDD server attempts to perform BDT re- selection with the SEAL NRM server using the procedure described in cl 14.3.13.3 of TS 23.434(41.

[0157] 4. The SEALDD server sends the SEALDD Background data transfer subscription response, containing the result of the operation which includes the result and may include the BDT subscription identifier.

[0158] 5. The SEALDD server sends the BDT data to the SEALDD client. During the transmission, the SEALDD server monitors the quality, e.g.. latency, jitter, bitrate, packet loss rate, of the transmission. The SEALDD client forwards the BDT data received to the VAL client.

[0159] 6. The SEALDD server notifies the VAL server about the delivery result by sending the SEALDD Background data transfer notification including the BDT subscription identifier and optionally the list of VAL UEs which received the BDT data, the executed time window and quality of the BDT data transmission based on the measurements in step 5.

[0160] 9.X.2.2 SEALDD Background data transfer in UL direction

[0161] Figure 9.X.2.2-1 illustrates the procedure for SEALDD Background data transfer in UL direction. Figure 8: SEALDD Background data transfer in UL direction

[0162] 0. The VAL client provides the SEALDD client with the needed information for BDT.

[0163] 1. The SEALDD client sends a SEALDD Background data transfer in UL direction subscription request to the SEALDD server. The request includes the VAL service ID. VAL server ID and may also include desired time window, desired area information (e.g.. when a UE enters a geographical areal. Policy Selection Guidance, data length, and storage expiration time.

[0164] 2. The SEALDD server authorizes the request from the SEALDD client and may fetch application data, based on parameters received in step 1.

[0165] NOTE 1 : The VAL payload can be encrypted when stored in DD layer, in cases the VAL and the DD layers are provided by different vendors. Security requirements for storing data in the DD layer are within SA3 scope.

[0166] 3. The SEALDD server starts the BDT configuration negotiation with the SEAL NRM server as described in clause 14.3.13 of TS 23.434(41. The SEALDD server performs Network resource adaptation negotiation with the SEAL NRM server as described in clause 14.3.3.3 of TS 23.434(41. Policies are set for the BDT data transfer using the previously negotiated BDT Reference ID

[0167] NOTE 2: The BDT policy can also be set for a future session via NEF ApplyPolicy by SEALDD server at the end of the BDT negotiation.

[0168] NOTE 3 : If there is any change in the network impacting the current BDT policy ( i.e. BDT warning notification from CN or trigger from the VAL server'). SEALDD server attempts to perform BDT re- selection with the SEAL NRM server using the procedure described in cl 14.3.13.3 of TS 23.434(41.

[0169] 4. The SEALDD server sends the SEALDD Background data transfer subscription response, containing the result of the operation and may include the BDT subscription identifier and allocated time window of the background data transfer policy to the SEALDD client.

[0170] 5. The VAL client sends the BDT data to the SEALDD client, which forwards the data to the SEALDD server. During the transmission, the SEALDD server monitors the quality, e.g.. latency, jitter, bitrate, packet loss rate, of the transmission and forwards the data to the VAL server according to the configuration.

[0171] NOTE 4: The VAL client can also send the BDT data to the SEAL client in step 0. then the BDT data is transmitted from SEALDD client to the SEALDD server in step 5.

[0172] 6. The SEALDD server notifies the SEALDD client about the delivery result by sending the SEALDD downlink background data transfer notification including the BDT subscription identifier and may include the executed time window and quality of the BDT data transmission based on the measurements in step 5.

[0173] 9.X.2.3 _ SEALDD Background data transfer subscription update

[0174] Figure 9.X.2.3-1 illustrates the procedure for SEALDD Background data transfer subscription update from either the SEALDD client or VAL server to the SEALDD server.

[0175] Pre-condition:

[0176] - The SEALDD Background data transfer in DL direction or SEALDD Background data transfer in UL direction procedure has been performed.

[0177] Figure 9: SEALDD Background data transfer subscription update la. The VAL server can trigger a BDT update by sending a SEALDD Background data transfer subscription update request. The request contains BDT subscription identifier and may contain desired time window, desired area information (e.g.. when a UE enters a geographical areal Policy Selection Guidance, data length, and storage expiration time. lb. The SEALDD client can trigger a BDT update (e.g. due to VAL client sent update! by sending a SEALDD Background data transfer subscription update request to the SEALDD server. The request contains BDT subscription identifier and may contain desired time window, desired area information (e.g.. when a UE enters a geographical areal Policy Selection Guidance, data length, and storage expiration time.

[0178] 2. The SEALDD server starts a new BDT configuration negotiation with the SEAL NRM server as described in clause 14.3.13.5 of TS 23.434(41. The SEALDD also performs Network resource adaptation negotiation with the SEAL NRM server as described in clause 14.3.3.3 of TS 23.434141 for the new BDT transmission.

[0179] 3a. The SEALDD server sends the SEALDD Background data transfer subscription update response to the VAL server, containing result and optionally the BDT subscription identifier.

[0180] 3b. The SEALDD server sends the SEALDD Background data transfer subscription update response to the SEALDD client, containing result. BDT subscription identifier and may contain granted time window.

[0181] 9.X.2.4 SEALDD Background data transfer unsubscribe

[0182] Figure 9.X.2.4-1 illustrates the procedure for SEALDD Background data transfer unsubscribe from either the SEALDD client or VAL server to the SEALDD server.

[0183] Pre-condition:

[0184] - The SEALDD Background data transfer in DL direction or SEALDD Background data transfer in UL direction procedure has been performed.

[0185] Figure 10: SEALDD Background data transfer unsubscribe la. The VAL server can trigger a BDT deletion by sending a SEALDD Background data transfer unsubscribe request to the SEALDD server. The request contains the BDT subscription identifier. lb. The SEALDD client can trigger a BDT deletion by sending a SEALDD Background data transfer unsubscribe request to the SEALDD server. The request contains the BDT subscription identifier.

[0186] 2. The SEALDD server negotiates the BDT configuration with the SEAL NRM server as described in clause 14.3.13.6 of TS 23.434(4] and deletes any stored application data related to the BDT subscription identifier.

[0187] 3a. The SEALDD server sends the SEALDD Background data transfer unsubscribe response to the VAL server, containing result of the operation.

[0188] 3b. The SEALDD server sends the SEALDD Background data transfer unsubscribe response to the SEALDD client, containing result of the operation.

[0189] 9.x.3 Information flows

[0190] 9.X.3.1 SEALDD Background data transfer in DL direction subscription reguest

[0191] Table 9.X.3.1-1 describes the information flow from the VAL server to the SEALDD server for requesting the SEALDD background data transfer in DL direction request. Table 9.X.3.1-1 : SEALDD Background data transfer in DL direction subscription request

[0192] 9.X.3.2 SEALDD Background data transfer in UL direction subscription request Table 9.X.3.2-1 describes the information flow from the SEALDD client in UL direction to the SEALDD server for requesting the SEALDD background data transfer in UL direction subscription request.

[0193] Table 9.X.3.2-1 : SEALDD Background data transfer in UL direction subscription request 9.X.3.3 SEALDD Background data transfer subscription response

[0194] Table 9.X.3.3-1 describes the information flow from the SEALDD server to the VAL server in DL direction and from the SEALDD client in UL direction. It is used for responding to the SEALDD Background data transfer in DL direction subscription request or the SEALDD Background data transfer in UL direction subscription request.

[0195] Table 9.X.3.3-1 : SEALDD Background data transfer subscription response

[0196] 9.X.3.4 SEALDD Background data transfer notification

[0197] Table 9.X.3.2-1 describes the information flow from the SEALDD server to the VAL server in DL direction or to the SEALDD client in UL direction. Table 9.X.3.4-1 : SEALDD Background data transfer notification

[0198] 9.X.3.5 SEALDD Background data transfer update subscription reguest

[0199] Table 9.x.3.1-1 describes the information flow from the VAL server in DL direction or the SEALDD client in UL direction to the SEALDD server for sending the SEALDD background data transfer update subscription request. Table 9.X.3.5-1: SEALDD Background data transfer update subscription reouest 9.X.3.6 SEALDD Background data transfer update subscription response

[0200] Table 9.X.3.6-1 describes the information flow from the SEALDD server to the VAL server in DL direction or SEALDD client in UL direction for responding to the SEALDD Background data transfer update subscription request.

[0201] Table 9.X.3.6-1 : SEALDD Background data transfer update subscription response

[0202] 9.X.3.7 SEALDD Background data transfer unsubscribe request

[0203] Table 9.x.3.1-1 describes the information flow from the VAL server in DL direction or the SEALDD client in UL direction to the SEALDD server for requesting the SEALDD background data transfer unsubscribe request.

[0204] Table 9.X.3.7-1 : SEALDD Background data transfer unsubscribe request

[0205] 9.X.3.8 SEALDD Background data transfer unsubscribe response

[0206] Table 9.X.3.2-1 describes the information flow from the SEALDD server to the VAL server in DL direction or SEALDD client in UL direction for responding to the SEALDD Background data transfer unsubscribe response.

[0207] Table 9.X.3.8-1 : SEALDD Background data transfer unsubscribe response

[0208] 9.X.4 APIs

[0209] 9.X.4.1 General

[0210] Table 9.X.4.1-1 illustrates the APIs exposed by SEALDD server for background data transfer.

[0211] Table 9.X.4.1-1: List of SEALDD server APIs for background data transfer 9.X.4.2 _ Sdd BDT DL Subscription Request operation

[0212] API operation name: Sdd BDT DL Subscription Request

[0213] Description: The consumer requests for a Background data transfer service in the DL direction.

[0214] Inputs: See clause 9.X.3.I.

[0215] Outputs: See clause 9.x.3.2.

[0216] See clause 9.X.2.1 for details of usage of this operation.

[0217] 9.X.4.3 _ Sdd BDT UL Subscription Request operation

[0218] API operation name: Sdd BDT UL Subscription Request

[0219] Description: The consumer requests for a Background data transfer service in the UL direction.

[0220] Inputs: See clause 9.X.3.3.

[0221] Outputs: See clause 9.x.3.2.

[0222] See clause 9.X.2.2 for details of usage of this operation.

[0223] 9.X.4.4 _ Sdd BDT Notify operation

[0224] API operation name: Sdd BackgroundDataTransfer Notify

[0225] Description: The consumer requests for one time for transmission quality query.

[0226] Inputs: None

[0227] Outputs: See clause 9.x.3.5.

[0228] See clause 9.X.2.2. clause 9.x.2.1 for details of usage of this operation.

[0229] 9.2.4.5 _ Sdd BDT Subscription Update operation

[0230] API operation name: Sdd BDT Subscription Update

[0231] Description: The consumer requests to update the SEALDD Background data transfer configuration.

[0232] Inputs: See clause 9.2.3.5.

[0233] Outputs: See clause 9.2.3.6.

[0234] See clause 9.2.2.3 for details of usage of this operation.

[0235] 9.2.4.6 _ Sdd BDT Unsubscribe operation

[0236] API operation name: Sdd BDT Unsubscribe

[0237] Description: The consumer requests to delete the SEALDD Background data transfer configuration.

[0238] Inputs: See clause 9.2.3.7.

[0239] Outputs: See clause 9.2.3.8.

[0240] See clause 9.2.2.4 for details of usage of this operation. To perform the method actions above, the server node 111 , such as a SEALDD server, configured to handle data delivery in a wireless communication network 100. The server node 111 may comprise an arrangement depicted in Figure 11.

[0241] The server node 111 may comprise an input and output interface 1100 configured to communicate with each other. The input and output interfacel 100 may comprise a receiver, e.g. wired and / or wireless, (not shown) and a transmitter, e.g. wired and / or wireless, (not shown).

[0242] The embodiments herein may be implemented through a respective processor or one or more processors, such as at least one processor 1110 of a processing circuitry in the server node 111 depicted in Figure 11 , together with computer program code for performing the functions and actions of the embodiments herein. The program code mentioned above may also be provided as a computer program product, for instance in the form of a data carrier carrying computer program code for performing the embodiments herein when being loaded into the server node 111. One such carrier may be in the form of a CD ROM disc. It is however feasible with other data carriers such as a memory stick. The computer program code may furthermore be provided as pure program code on a server and downloaded to the server node 111.

[0243] The server node 111 , such as a SEALDD server, and / or the processor 1110 is configured to handle data delivery in the wireless communication network 100.

[0244] The server node 111 and / or the processor 1110 is configured to negotiate a BDT configuration policy and / or network resource adaptation with the network resource management server 130, for data to be transferred.

[0245] The server node 111 and / or the processor 1110 is configured to send data in a BDT using the negotiated BDT configuration policy and / or network resource adaptation.

[0246] In some embodiments, the server node 111 and / or the processor 1110 may further be configured to receive a BDT request for the BDT from any one out of a:

[0247] - a VAL server 112, or

[0248] - a client node 121 , such as a SEALDD client.

[0249] In some embodiments, the BDT request is adapted to comprise any one or more out of:

[0250] - a one or more identifiers adapted to indicate recipients of the BDT data

[0251] - data to be delivered in the BDT, or

[0252] - an indication adapted to indicate a location of the data to be obtained and delivered in the BDT, and - a storage expiration time adapted to indicate the expiration or time validity of the stored BDT data.

[0253] In some embodiments, the server node 111 and / or the processor 1110 may further be configured to obtain data to be transferred in the BDT from a location indicated in a BDT request.

[0254] In some embodiments, the data is sent to a recipient adapted to comprise any one out of:

[0255] - a VAL client 122, or

[0256] - a VAL server 112.

[0257] In some embodiments, the server node 111 and / or the processor 1110 may further be configured to send a BDT response in response to the BDT request. The BDT response is adapted to comprise any one or more out of:

[0258] - a BDT subscription identifier, and

[0259] - a granted time window for the BDT.

[0260] In some embodiments, the server node 111 and / or the processor 1110 may further be configured to send a BDT notification. The BDT notification is adapted to comprise any one or more out of:

[0261] - a BDT subscription identifier, and

[0262] - an executed time window,

[0263] - one or more identifiers adapted to indicate recipients of the BDT data, and

[0264] - a BDT transmission quality.

[0265] In some embodiments, the server node 111 and / or the processor 1110 may further be configured to receive an update request to update the negotiated BDT configuration policy and / or network resource adaptation.

[0266] In some embodiments, the server node 111 and / or the processor 1110 may further be configured to renegotiate the BDT configuration policy and / or network resource adaptation with the network resource management server 130.

[0267] In some embodiments, the server node 111 and / or the processor 1110 may further be configured to receive an unsubscribe request to unsubscribe from the BDT configuration policy.

[0268] In some embodiments, the server node 111 and / or the processor 1110 may further be configured to renegotiate the BDT configuration policy with the network resource management server 130. The renegotiation comprises deleting the BDT configuration.

[0269] In some embodiments, the update request and / or the unsubscribe request is adapted to be received from any one out of: - a VAL server 112, or

[0270] - a client node 121 , such as a SEALDD client.

[0271] The server node 111 may further comprise respective a memory 1120 comprising one or more memory units. The memory 1120 comprises instructions executable by the processor 1110 in the server node 111.

[0272] The memory 1120 is arranged to be used to store instructions, data, configurations, identifiers, indications, notifications, resources, flows, policies, and applications to perform the methods herein when being executed in the server node 111.

[0273] In some embodiments, a computer program 1130 comprises instructions, which when executed by the at least one processor 1110, cause the at least one processor 1110 of the server node 111 to perform the actions above.

[0274] In some embodiments, a respective carrier 1140 comprises the respective computer program 1130, wherein the carrier 1140 is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.

[0275] Thus, embodiments herein may disclose the server node 111 configured to handle data delivery in the wireless communications network 100. The server node 111 comprises the processor 1110 and the memory 1120, said memory 1120 comprising instructions executable by said processor 1110 whereby said server node 111 is operative to perform any of the methods herein.

[0276] 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.

[0277] 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.

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

[0279] To perform the method actions above, the requesting node 112, 121 , such as a SEALDD client or a VAL server, is configured to handle data delivery in the wireless communications network 100. The requesting node 112, 121 may comprise an arrangement depicted in Figure 12.

[0280] The requesting node 112, 121 may comprise an input and output interface 1200 configured to communicate with each other. The input and output interface 1200 may comprise a receiver, e.g. wired and / or wireless, (not shown) and a transmitter, e.g. wired and / or wireless, (not shown).

[0281] The embodiments herein may be implemented through a respective processor or one or more processors, such as at least one processor 1210 of a processing circuitry in the requesting node 112, 121 depicted in Figure 12, together with computer program code for performing the functions and actions of the embodiments herein. The program code mentioned above may also be provided as a computer program product, for instance in the form of a data carrier carrying computer program code for performing the embodiments herein when being loaded into the requesting node 112, 121. One such carrier may be in the form of a CD ROM disc. It is however feasible with other data carriers such as a memory stick. The computer program code may furthermore be provided as pure program code on a server and downloaded to the requesting node 112, 121.

[0282] The requesting node 112, 121 , such as a SEALDD client or a AL server, and / or processor 1210 is configured to handle data delivery in the wireless communication network 100.

[0283] The requesting node 112, 121 and / or processor 1210 is configured to request a server node 111 , such as a SEALDD server, to perform a BDT. wherein the request is adapted comprise any one or more out of:

[0284] - one or more identifiers adapted to indicate recipients of the BDT data,

[0285] - data to be delivered in the BDT,

[0286] - an indication adapted to indicate a location of the data to be obtained and delivered in the BDT, and

[0287] - a storage expiration time adapted to indicate the expiration or time validity of the stored BDT data.

[0288] In some embodiments, the requesting node 112, 121 and / or processor 1210 may further be configured to request the server node 111 to perform an update to the negotiated BDT configuration policy and / or network resource adaptation.

[0289] In some embodiments, the requesting node 112, 121 and / or processor 1210 may further be configured to request the server node 111 to unsubscribe the requesting node 112, 121 from the negotiated BDT configuration policy.

[0290] In some embodiments, the requesting node 112, 121 and / or processor 1210 may further be configured to receive, from the server node 111 , a BDT response in response to the BDT request. The BDT response is adapted to comprise any one or more out of:

[0291] - a BDT subscription identifier, and

[0292] - a granted time window for the BDT.

[0293] In some embodiments, the requesting node 112, 121 and / or processor 1210 may further be configured to receive a BDT notification from the server node 111. The BDT notification is adapted to comprise any one or more out of:

[0294] - a BDT subscription identifier,

[0295] - an executed time window,

[0296] - one or more identifiers adapted to indicate recipients of the BDT data, and

[0297] - a BDT transmission quality.

[0298] In some embodiments, the requesting node 112, 121 is adapted to be any one out of: - a VAL server 112, or

[0299] - a client node 121 , such as a SEALDD client.

[0300] In some embodiments, the recipient is adapted to comprise any one out of:

[0301] - a VAL client 122, or

[0302] - a VAL server 112.

[0303] The network node 130 may further comprise respective a memory 1220 comprising one or more memory units. The memory 1220 comprises instructions executable by the processor 1210 in the requesting node 112, 121.

[0304] The memory 1220 is arranged to be used to store instructions, data, configurations, identifiers, indications, notifications, resources, policies, and applications to perform the methods herein when being executed in the requesting node 112, 121 .

[0305] In some embodiments, a computer program 1230 comprises instructions, which when executed by the at least one processor 1210, cause the at least one processor 1210 of the requesting node 112, 121 to perform the actions above.

[0306] In some embodiments, a respective carrier 1240 comprises the respective computer program 1230, wherein the carrier 1240 is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.

[0307] Thus, embodiments herein may disclose the requesting node 112, 121 configured to handle data delivery in the wireless communications network 100. The requesting node 112, 121 comprises the processor 1210 and the memory 1220, said memory 1220 comprising instructions executable by said processor 1210 whereby said requesting node 112, 121 is operative to perform any of the methods herein.

[0308] 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.

[0309] 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.

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

[0311] ADDITIONAL EXPLANATION

[0312] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0313] Figure 13 shows an example of a communication system QQ100 in accordance with some embodiments.

[0314] 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 being examples of the IMS AS 110. 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 network node 130, or any other similar 3rd 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 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.

[0315] Examples of an ORAN network node include an open radio unit O-RU, an open distributed unit O-DU, 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 O-2 interface defined by the O-RAN Alliance or comparable technologies. The network nodes QQ110 facilitate direct or indirect connection of user equipment UE, such as by connecting UEs QQ112a, QQ112b, QQ112c, and QQ112d one or more of which may be generally referred to as UEs QQ112 being examples of a UE 121 to the core network QQ106 over one or more wireless connections.

[0316] 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.

[0317] 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.

[0318] 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 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 AUSF, Subscription Identifier Deconcealing function SIDF, Unified Data Management UDM, Security Edge Protection Proxy SEPP, Network Exposure Function NEF, and / or a User Plane Function UPF.

[0319] 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.

[0320] As a whole, the communication system QQ100 of Figure 13 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.

[0321] 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.

[0322] 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.

[0323] 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.

[0324] 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 non-dedicated 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.

[0325] Figure 14 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 customerpremise equipment CPE, vehicle, vehicle-mounted or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project 3GPP, including a narrow band internet of things NB-loT UE, a machine type communication MTC UE, and / or an enhanced MTC eMTC UE.

[0326] 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.

[0327] 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 QQ2. 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.

[0328] 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.

[0329] 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.

[0330] 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 read-only 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.

[0331] 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.

[0332] 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.

[0333] 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.

[0334] 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.

[0335] 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 smart watch, 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 QQ2. 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.

[0336] 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.

[0337] Figure 15 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.

[0338] 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.

[0339] 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.

[0340] 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.

[0341] 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.

[0342] The communication interface QQ306 is used in wired or wireless communication of signaling and / or data between a network node, access network, and / or UE. As illustrated, the communication interface QQ306 comprises ports / terminals 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.

[0343] 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.

[0344] 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.

[0345] 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.

[0346] 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.

[0347] Embodiments of the network node QQ300 may include additional components beyond those shown in Figure 15 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.

[0348] Figure 16 is a block diagram of a host QQ400, which may be an embodiment of the host QQ116 of Figure 13, 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.

[0349] 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 14 and QQ3, such that the descriptions thereof are generally applicable to the corresponding components of host QQ400.

[0350] 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., FLAC, 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.

[0351] Figure 17 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.

[0352] 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.

[0353] 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.

[0354] 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.

[0355] 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.

[0356] 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 signaling can be provided with the use of a control system QQ512 which may alternatively be used for communication between hardware nodes and radio units.

[0357] Figure 18 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 13 and / or UE QQ200 of Figure QQ2, network node such as network node QQ110a of Figure 13 and / or network node QQ300 of Figure 15, and host such as host QQ116 of Figure 13 and / or host QQ400 of Figure 16 discussed in the preceding paragraphs will now be described with reference to Figure 18.

[0358] 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.

[0359] 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 QQ1 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.

[0360] 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.

[0361] 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.

[0362] 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.

[0363] 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.

[0364] 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.

[0365] 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.

[0366] 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 signaling 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.

[0367] 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.

[0368] 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.

[0369] When using the word "comprise" or “comprising” it shall be interpreted as nonlimiting, i.e. meaning "consist at least of'.

[0370] The embodiments herein are not limited to the preferred embodiments described above. Various alternatives, modifications and equivalents may be used.

[0371] Abbreviation Explanation

[0372] BDT Background Data Transfer

[0373] DL Downlink lloT Industrial Internet of Things

[0374] SEAL Service enabler architecture layer

[0375] SEALDD SEAL Data Delivery

[0376] SEAL NRM SEAL Network Resource Management

[0377] UE User Equipment

[0378] UL Uplink

[0379] V2X Vehicle to Everything

[0380] VAL Vertical Application Layer

[0381] UAV Unmanned Aerial Vehicle

Claims

CLAIMS1. A method performed by a server node (111), such as a SEALDD server, for handling data delivery in a wireless communication network (100), the method comprising: negotiating (402) a background data transfer, BDT, configuration policy and / or network resource adaptation with a network resource management server (130), for data to be transferred, sending (405) data in a BDT using the negotiated BDT configuration policy and / or network resource adaptation.

2. The method according to claim 1 , further comprising: receiving (401) a BDT request for the BDT from any one out of a:- a VAL server (112), or- a client node (121), such as a SEALDD client.

3. The method according to claim 2, wherein the BDT request comprises any one or more out of:- a one or more identifiers indicating recipients of the BDT data- data to be delivered in the BDT, or- an indication indicating a location of the data to be obtained and delivered in the BDT, and- a storage expiration time indicating the expiration or time validity of the stored BDT data.

4. The method according to any of claims 1-3, further comprising: obtaining (404) data to be transferred in the BDT from a location indicated in a BDT request.

5. The method according to any of claims 1-4, wherein the data is sent to a recipient comprising any one out of:- a VAL client (122), or- a VAL server (112).

6. The method according to any of claims 1-5 further comprising:sending (403) a BDT response in response to the BDT request, wherein the BDT response comprises any one or more out of:- a BDT subscription identifier, and- a granted time window for the BDT.

7. The method according to any of claims 1-6 further comprising: sending (406) a BDT notification, wherein the BDT notification comprises any one or more out of:- a BDT subscription identifier, and- an executed time window,- one or more identifiers indicating recipients of the BDT data, and- a BDT transmission quality.

8. The method according to any of claims 1-7, further comprising: receiving (407) an update request to update the negotiated BDT configuration policy and / or network resource adaptation, and renegotiating (408) the BDT configuration policy and / or network resource adaptation with a network resource management server (130).

9. The method according to any of claims 1-8, further comprising: receiving (409) an unsubscribe request to unsubscribe from the BDT configuration policy, and renegotiating (410) the BDT configuration policy with the network resource management server (130), wherein the renegotiation comprises deleting the BDT configuration.

10. The method according to any of claims 8-9, wherein the update request and / or the unsubscribe request is received from any one out of:- a VAL server (112), or- a client node (121), such as a SEALDD client.

11. A computer program 1130 comprising instructions, which when executed by a processor 1110, causes the processor 1110 to perform actions according to any of the claims 1-10.

12. A carrier 1140 comprising the computer program 1130 of claim 11 , wherein the carrier 1140 is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer- readable storage medium.

13. A method performed by a requesting node (112, 121), such as a SEALDD client or a VAL server, for handling data delivery in a wireless communication network (100), the method comprising: requesting (501) a server node (111), such as a SEALDD server, to perform a background data transfer, BDT, wherein the request comprises any one or more out of:- a one or more identifiers indicating recipients of the BDT data- data to be delivered in the BDT, or- an indication indicating a location of the data to be obtained and delivered in the BDT, and- a storage expiration time indicating the expiration or time validity of the stored BDT data.

14. The method according to claim 13, further comprising: requesting (504) the server node (111) to perform an update to the negotiated BDT configuration policy and / or network resource adaptation, and15. The method according to any of claims 13-14, further comprising: requesting (506) the server node (111) to unsubscribe the requesting node (112,121) from the negotiated BDT configuration policy.

16. The method according to any of claims 13-15, further comprising: receiving (502), from the server node (111), a BDT response in response to the BDT request, wherein the BDT response comprises any one or more out of:- a BDT subscription identifier, and- a granted time window for the BDT.

17. The method according to any of claims 13-16, further comprising: receiving (503) a BDT notification from the server node (111), wherein the BDT notification comprises any one or more out of:- a BDT subscription identifier, and- an executed time window,- one or more identifiers indicating recipients of the BDT data, and- a BDT transmission quality.

18. The method according to any of claims 13-17, wherein the requesting node (112, 121) is any one out of:- a VAL server (112), or- a client node (121), such as a SEALDD client.

19. The method according to any of claims 13-18, wherein the recipient comprises any one out of:- a VAL client (122), or- a VAL server (112).

20. A computer program 1230 comprising instructions, which when executed by a processor 1210, causes the processor 1210 to perform actions according to any of the claims 13-19.21 . A carrier 1240 comprising the computer program 1230 of claim 20, wherein the carrier 1240 is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer- readable storage medium.

22. A server node (111), such as a SEALDD server, configured to handle data delivery in a wireless communication network (100), the server node (111) further being configured to: negotiate a background data transfer, BDT, configuration policy and / or network resource adaptation with a network resource management server (130), for data to be transferred, send data in a BDT using the negotiated BDT configuration policy and / or network resource adaptation.

23. The server node (111) according to claim 22, further being configured to: receive a BDT request for the BDT from any one out of a:- a VAL server (112), or- a client node (121), such as a SEALDD client.

24. The server node (111) according to claim 23, wherein the BDT request is adapted to comprise any one or more out of:- a one or more identifiers adapted to indicate recipients of the BDT data- data to be delivered in the BDT, or- an indication adapted to indicate a location of the data to be obtained and delivered in the BDT, and- a storage expiration time adapted to indicate the expiration or time validity of the stored BDT data.

25. The server node (111) according to any of claims 22-24, further being configured to: obtain data to be transferred in the BDT from a location indicated in a BDT request.

26. The server node (111) according to any of claims 22-25, wherein the data is sent to a recipient adapted to comprise any one out of:- a VAL client (122), or- a VAL server (112).

27. The server node (111) according to any of claims 22-26, further being configured to: send a BDT response in response to the BDT request, wherein the BDT response is adapted to comprise any one or more out of:- a BDT subscription identifier, and- a granted time window for the BDT.

28. The server node (111) according to any of claims 22-27, further being configured to: send a BDT notification, wherein the BDT notification is adapted to comprise any one or more out of:- a BDT subscription identifier, and- an executed time window,- one or more identifiers adapted to indicate recipients of the BDT data, and- a BDT transmission quality.

29. The server node (111) according to any of claims 22-28, further being configured to: receive an update request to update the negotiated BDT configuration policy and / or network resource adaptation, and renegotiate the BDT configuration policy and / or network resource adaptation with the network resource management server (130).

30. The server node (111) according to any of claims 22-29, further being configured to: receive an unsubscribe request to unsubscribe from the BDT configuration policy, and renegotiate the BDT configuration policy with the network resource management server (130), wherein the renegotiation comprises deleting the BDT configuration.

31. The server node (111) according to any of claims 29-30, wherein the update request and / or the unsubscribe request is adapted to be received from any one out of:- a VAL server (112), or- a client node (121), such as a SEALDD client.

32. A requesting node (112, 121), such as a SEALDD client or a VAL server, configured to handle data delivery in a wireless communication network (100), the requesting node (112, 121) further being configured to: request a server node (111), such as a SEALDD server, to perform a background data transfer, BDT, wherein the request is adapted comprise any one or more out of:- a one or more identifiers adapted to indicate recipients of the BDT data- data to be delivered in the BDT, or- an indication adapted to indicate a location of the data to be obtained and delivered in the BDT, and- a storage expiration time adapted to indicate the expiration or time validity of the stored BDT data.

33. The requesting node (112, 121) according to claim 32, further being configured to:request the server node (111) to perform an update to the negotiated BDT configuration policy and / or network resource adaptation, and34. The requesting node (112, 121) according to any of claims 32-33, further being configured to: request the server node (111) to unsubscribe the requesting node (112, 121) from the negotiated BDT configuration policy.

35. The requesting node (112, 121) according to any of claims 32-34, further being configured to: receive, from the server node (111), a BDT response in response to the BDT request, wherein the BDT response is adapted to comprise any one or more out of:- a BDT subscription identifier, and- a granted time window for the BDT.

36. The requesting node (112, 121) according to any of claims 32-35, further being configured to: receive a BDT notification from the server node (111), wherein the BDT notification is adapted to comprise any one or more out of:- a BDT subscription identifier, and- an executed time window,- one or more identifiers adapted to indicate recipients of the BDT data, and- a BDT transmission quality.

37. The requesting node (112, 121) according to any of claims 32-36, wherein the requesting node (112, 121) is adapted to be any one out of:- a VAL server (112), or- a client node (121), such as a SEALDD client.

38. The requesting node (112, 121) according to any of claims 32-37, wherein the recipient is adapted to comprise any one out of:- a VAL client (122), or- a VAL server (112).