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

Abstract

A method performed by a server node, such as a SEALDD server, for handling data delivery in a wireless communication network is provided The server node receives (201) a data transmission request from a VAL server. The data transmission request comprises a multi-modal service identifier. allocating (202) at least one flow identifier, such as a SEALDD-S multi modal flow identifier, associated with the multi modal service identifier, The server node sends (205) a transmission quality measurement request to a first client node and a second client node, such as a SEALDD client. The request comprises a crossflow RTT measurement requirement, at least two client node identifiers and flow information, e.g., for uplink and downlink, associated with the multi modal identifier. The server node sends (207) a DL monitoring packet to a first client node, such as a SEALDD client. The DL monitoring packet comprises data transmitted by a second client node and a time T1 recorded by the second client node. The server node receives (208) a measurement report from the first client node. The report comprises a determined crossflow round trip time, RTT.

Description

SERVER NODE, CLIENT NODES AND METHODS IN A WIRELESSCOMMUNICATIONS NETWORKTECHNICAL FIELDEmbodiments herein relate to a server node, client nodes 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.BACKGROUNDIn 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.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-6GHz 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.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.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.The Service Architecture Enabler Layer Data Delivery (SEALDD) layer is used for Data Delivery for vertical applications. The SEALDD establishes the connections between client and server with the given QoS values.SUMMARYAs part of developing embodiments herein a problem was identified by the inventor and will first be discussed.The current implementation of the SEALDD layer does not support extended reality (XR) scenario, e.g., the Multi-Modal service handling and QoS / QoE measurementsThe current implementation of the SEALDD layer does not support XR scenario, e.g., the Multi-Modal service handling and QoS / QoE measurements An object of embodiments herein is, thus, to provide a mechanism that improves the performance of a wireless communication network.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.The server node receives a data transmission request from a VAL server. The data transmission request comprises a multi-modal service identifier.The server node allocates at least one flow identifier, such as a SEALDD-S multi modal flow identifier, associated with the multi modal service identifier.The server node sends a transmission quality measurement request to a first client node and a second client node, such as a SEALDD client. The request comprises a crossflow RTT measurement requirement, at least two client node identifiers and flow information, e.g., for uplink and downlink, associated with the multi modal identifier.The server node sends a DL monitoring packet to a first client node, such as a SEALDD client. The DL monitoring packet comprises data transmitted by a second client node and a time T 1 recorded by the second client node.The server node receives a measurement report from the first client node. The report comprises a determined crossflow round trip time, RTT.According to another aspect of embodiments herein, the object is achieved by a method performed by a client node, such as a first client node, such as a SEALDD client, for handling data delivery in a wireless communication network.The client node receives a transmission quality measurement request from a server node, such as a SEALDD server. The request comprises a crossflow RTT measurement requirement, at least two client node identifiers and flow information associated with a multi modal identifier.The client node receives a DL monitoring packet from the server node. The DL monitoring packet comprises data transmitted by a second client node and a time T 1 recorded by the second client node.The client node determines a crossflow RTT based on the time T 1 and a time T2. The T2 represents a time of reception of the DL monitoring packet.The client node sends a measurement report to the sever node. The report comprises a determined crossflow round trip time, RTT.According to another aspect of embodiments herein, the object is achieved by a method performed by a client node, such as a second client node, such as a SEALDD client, for handling data delivery in a wireless communication network.The client node receives a transmission quality measurement request from a server node, such as a SEALDD server. The request comprising a crossflow RTT measurement requirement, at least two client node identifiers and flow information associated with a multi modal identifier,The client node transmits data as an uplink packet on a second flow. The UL packet comprising the time T 1.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.The server node is configured to receive a data transmission request from a VAL server. The data transmission request adapted to comprise a multi-modal service identifier.The server node is configured to allocate at least one flow identifier, such as a SEALDD-S multi modal flow identifier, associated with the multi modal service identifier,The server node is configured to send a transmission quality measurement request to a first client node and a second client node, such as a SEALDD client. The request adapted to comprise a crossflow RTT measurement requirement, at least two client node identifiers and flow information, e.g., for uplink and downlink, associated with the multi modal identifier.The server node is configured to send a DL monitoring packet to a first client node, such as a SEALDD client. The DL monitoring packet is adapted to comprise data transmitted by a second client node and a time T 1 recorded by the second client node.The server node is configured to receive a measurement report from the first client node. The report is adapted to comprise a determined crossflow round trip time, RTT.According to another aspect of embodiments herein, the object is achieved by a client node, such as a first client node, such as a SEALDD client, configured to handle data delivery in a wireless communication network.The client node is configured to receive a transmission quality measurement request from a server node, such as a SEALDD server. The request adapted to comprise a crossflow RTT measurement requirement, at least two client node identifiers and flow information associated with a multi modal identifier.The client node is configured to receive a DL monitoring packet from the server node. The DL monitoring packet is adapted to comprise data transmitted by a second client node and a time T 1 recorded by the second client node.The client node is configured to determine a crossflow RTT based on the time T 1 and a time T2. T2 is adapted to represents a time of reception of the DL monitoring packet.The client node is configured to send a measurement report to the sever node. The report is adapted to comprise a determined crossflow round trip time, RTT.According to another aspect of embodiments herein, the object is achieved by a client node, such as a second client node, such as a SEALDD client, configured to handle data delivery in a wireless communication network.The client node is configured to receive a transmission quality measurement request from a server node, such as a SEALDD server. The request adapted to comprise a crossflow RTT measurement requirement, at least two client node identifiers and flow information associated with a multi modal identifier,The client node is configured to transmit data as an uplink packet on a second flow. The UL packet adapted to comprise the time T 1.It is herein proposed a solution that enables multi-modal service handling and QoS / QoE enhancements, e.g., for XR, in SEALDD. This will result in an improved performance of the wireless communication network.BRIEF DESCRIPTION OF THE DRAWINGSExamples of embodiments herein are described in more detail with reference to attached drawings in which:Figure 1 a schematic overview of a wireless communication network according to embodiments herein.Figure 2 is a flowchart depicting embodiments of a method in a server node.Figure 3 is a flowchart depicting embodiments of a method in a client node.Figure 4 is a flowchart depicting embodiments of a method in a client node.Figure 5 is an example according to embodiments herein.Figure 6 is a combined flowchart and signalling scheme according to embodiments herein.Figure 7 is a combined flowchart and signalling scheme according to embodiments herein.Figure 8 is a combined flowchart and signalling scheme according to embodiments herein.Figure 9 is a combined flowchart and signalling scheme according to embodiments herein.Figure 10 is a combined flowchart and signalling scheme according to embodiments herein.Figure 11 is a schematic block diagram illustrating embodiments of a server node.Figure 12 is a schematic block diagram illustrating embodiments of a client node.Figure 13 is a schematic block diagram illustrating embodiments of a client node.Figure 14 shows an example of a communication system QQ100 in accordance with some embodiments.Figure 15 shows a UE QQ200 in accordance with some embodiments.Figure 16 shows a network node QQ300 in accordance with some embodiments.Figure 17 is a block diagram of a host QQ400, which may be an embodiment of the host QQ116 of Figure 14, in accordance with various aspects described herein.Figure 18 is a block diagram illustrating a virtualization environment QQ500 in which functions implemented by some embodiments may be virtualized.Figure 19 shows a communication diagram of a host QQ602 communicating via a network node QQ604 with a UE QQ606 over a partially wireless connection in accordance with some embodiments.DETAILED DESCRIPTIONEmbodiments 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 technologiesand 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.According to embodiments herein, improvements to the SEALDD layer defined in 3GPP TS 23.433, is provided by e.g.,:The Application layer Multi-modal Service Identifier is included into the SEALDD enabled Regular transmission request in order to signal the multi-modal service in SEALDD layer;The handling of the Application layer Multi-modal Service Identifier is specified in SEALDD enabled regular data transmission connection establishment procedure; andThe Multi-Modal Flow information is included into the SEALDD enabled regular transmission response to signal the current status of the multi-modal service in SEALDD layer.The Multi-Modal Service Info is included into the SEALDD enabled data transmission quality measurement subscription request in order to support the multimodal service QoS monitoring in the SEALDD layer;The handling of the Multi-Modal Service Info is specified in Data transmission quality measurement; andFiner granularity of QoS measurement identifiers, i.e., UL / DL / E2E. Example: UL jitter.New multi-modal crossflows identifiers are proposed including Multi-Modal flows aggregation method. Examples: maximum crossflow average uplink PLR for X multimodal flows.Mapping between measured QoS and XR specific QoE metrics, e.g., Motion-to-Photon for edge deployed XR application.Embodiments herein may bring the advantage of a flexible configuration of the XR traffic in SEALDD layer, e.g. by: providing the Multi-Modal service ID in the transmission request to associate the SEALDD connection with XR traffic;SEALDD server can manage the multi-modal flows (each flow has a unique identifier assigned by the SEALDD layer).QoS metrics and measurements for XR traffic in SEALDD layer:The measurement can be requested for an individual and group of Multi- Modal flows for XR traffic.Finer granularity of the QoS metrics in the SEALDD layer, e.g., Uplink / Downlink / E2E for the measurement indexes.Methods for aggregation for multiple flow maximum crossflow average uplink PRL for X multi-modal flows.Mapping between measured QoS and XR specific QoE metrics, e.g., Motion-to-Photon for edge deployed XR application.Improvement of the QoS measurement procedure for multi-flow XR scenario.Support of the QoS measurement for XR ecosystem with multiple UEs scenario.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.Embodiments herein relate to wireless communication networks in general. Figure 1 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 100, 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 stationcapable of communicating using radio communication with a network node within an area served by the network node.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).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.The UE 120 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.Methods herein may be performed by the server node 111 and a client node 121 , such as a first client node 121 and / or a second client node 121. As an alternative, a Distributed Node (DN) and functionality, e.g. comprised in the cloud 190 as shown in Figure 1 , may be used for performing or partly performing the methods herein.A method according to embodiments herein will now be described from the view of the server node 111, together with Figure 2. Figure 2 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 2.Action 201The server node 111 receives a data transmission request from a VAL server 112. The data transmission request comprising a multi-modal service identifier. The multi-modal service identifier may also be referred to as an application layer multimodal service identifier. The data transmission request may be for establishing connection for transmitting data. The data transmission request may also be referred to as an Sdd RegularTransmission Requst. The data transmission request may e.g., further comprise one or more parameters associated with any one or more of the information elements indicated in table 9.2.3.1-1 below. The information elements indicated in table 9.2.3.1-1 may e.g., comprise a VAL server ID IE, a VAL service ID IE, a UE ID IE, a Multi-Modal Service ID IE, lEs related to a bandwidth limit and / or a Quality of Service information IE.Action 202The server node 111 allocates at least one flow identifier, such as a SEALDD-S multi modal flow identifier, associated with the multi modal service identifierAction 203In some embodiments, the server node 111 sends a data transmission response to the VAL server 112. The data transmission response comprises a total number of flows and the at least one allocated flow identifier associated with the multimodal service identifier. The data transmission request may also be referred to as an Sdd RegularTransmission Response. Each flow identifier is associated with a flow in the total number of flows. The data transmission response may e.g., further comprise one or more parameters associated with any one or more of the information elements indicated in table 9.2.3.2-1 below. The information elements indicated in table 9.2.3.1-1 may e.g., comprise a server connection information IE, a Multi-Modal Flow IE, and / or a cause IE.Action 204In some embodiments, the server node 111 receives a transmission quality measurement request from the VAL server 112. The request comprises a crossflow RTT measurement requirement, at least two client nodes 121 identifiers, such as identifiers for the first client node 121 and the second client node 121 , and flow information, e.g., for uplink and downlink, associated with the multi modal identifier. The flow information may e.g., comprise flow identifiers, such as multi-modal flow identifiers, for a first flow to first client node 121 and a second flow to the second client node 121. The transmission quality measurement request may also be referred to as a SEALDD transmission quality measurement subscription request. The request requests the client nodes, such as the first client node 121 and the second client node 121, to perform quality measurements, such as cross flow quality measurements. The crossflow RTT measurement requirement comprises determining the crossflow RTT between the flows indicated in the flow information. The crossflow quality measurements may e.g., comprise crossflow RTTmeasurements, e.g., UL / DL / E2E latency, LIL / DL crossflow bitrate, UL / BL / E2E crossflow packet loss rate and / or UL / DL / E2E crossflow jitter. The flow information may e.g., comprise flow identifiers, such as multi-modal flow identifiers, for a first flow to first client node 121 and a second flow to the second client node 121.Action 205The server node 111 sends a transmission quality measurement request, such as the transmission quality measurement request received from the VAL server 112, to a first client node 121 and a second client node 121, such as SEALDD clients. The request comprises a crossflow RTT measurement requirement, at least two client node 121 identifiers, such as identifiers for the first client node 121 and the second client node 121, and flow information, e.g., for uplink and downlink, associated with the multi modal identifier. The transmission quality measurement request may also be referred to as a SEALDD transmission quality measurement subscription request. The request requests the client nodes, such as the first client node 121 and the second client node 121, to perform quality measurements, such as cross flow quality measurements. The crossflow RTT measurement requirement comprises determining the crossflow RTT between the flows indicated in the flow information. The crossflow quality measurements may e.g., comprise crossflow RTT measurements, e.g., UL / DL / E2E latency, LIL / DL crossflow bitrate, UL / BL / E2E crossflow packet loss rate and / or UL / DL / E2E crossflow jitter.Action 206In some embodiments, the server node 111 receives, from the second client node 121 , data as an UL packet on a second flow. The UL packet comprises the time T 1. The second flow may be associated with flow identifier, such as multi-modal flow identifier, indicated in the flow information. T1 represents a time when the second client node 121 transmitted the data comprised in the UL packet.Action 207The server node 111 sends a DL monitoring packet to a first client node (121), such as a SEALDD client. The DL monitoring packet comprises data transmitted by a second client node (121) and a time T1 recorded by the second client node 121. T1 represents a time when the second client node 121 transmitted the data comprised in the DL monitoring packet. Thus, T1 may e.g., be used by the first client node 121 to determine e.g., a crossflow RTT. The server node 111 may send the DL monitoring packet on a first flow associated with a flow identifier indicated in the flow information comprised transmission quality measurement request. The first flow is different from the second flow on which the data was received from the second client node 121.Action 208The server node 111 receives a measurement report from the first client node 121.The report comprises a determined crossflow RTT. The crossflow RTT may e.g., comprise UL / DL / E2E latency. The measurement report may further comprise e.g., LIL / DL crossflow bitrate, UL / BL / E2E crossflow packet loss rate and / or UL / DL / E2E crossflow jitter. The measurement report may also be referred to as a SEALDD transmission quality measurement notification, and the measurements may e.g., be comprised in a measurement report list, such as a SEALDD transmission quality measurement report list, in the measurement report. The measurement report list may e.g., comprise any of the information elements in table 9.7.3.3-2 below.Action 209In some embodiments, the server node 111 receives a quality query request from the VAL server 112. The request comprises the multi-modal service identifier and / or multimodal service info. The request requests the server node 111 to provide quality measurement results, such as the quality measurment results in the measurement report in Action 208. The quality query request may also be referred to as a SEALDD transmission quality query request.In some embodiments, the server node 111 provides, such as sends, a quality query response to the VAL server 112. The response comprises the multi-modal service identifier and / or multi-modal service info. The comprises quality measurement results, such as the quality measurment results in the measurement report in Action 208. The quality query response may also be referred to as a SEALDD transmission quality query response.A method according to embodiments herein will now be described from the view of the client node 121 , such as the SEALDD client, e.g., the first client node 121 , together with Figure 3. Figure 3 depicts example embodiments of a method performed by the client node 121 , such as a SEALDD client, for 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 3.Action 301The client node 121 receives a transmission quality measurement request from the server node 111 , such as a SEALDD server. The request comprises a crossflow RTT measurement requirement, at least two client node 121 identifiers, such as identifiers forthe first client node 121 and the second client node 121 , and flow information, e.g., for uplink and downlink, associated with the multi modal identifier. The transmission quality measurement request may also be referred to as a SEALDD transmission quality measurement subscription request. The request requests the client nodes, such as the first client node 121 and the second client node 121, to perform quality measurements, such as cross flow quality measurements. The crossflow RTT measurement requirement comprises determining the crossflow RTT between the flows indicated in the flow information. The crossflow quality measurements may e.g., comprise crossflow RTT measurements, e.g., UL / DL / E2E latency, LIL / DL crossflow bitrate, UL / BL / E2E crossflow packet loss rate and / or UL / DL / E2E crossflow jitter.Action 302The client node 121 receives a DL monitoring packet from the server node 111. The DL monitoring packet comprises data transmitted by a second client node 121 and a time T 1 recorded by the second client node 121. T1 represents a time when the second client node 121 transmitted the data comprised in the DL monitoring packet. Thus, T1 may e.g., be used by the client node 121 to determine e.g., a crossflow RTT. The client node 121 may receive the DL monitoring packet on a first flow associated with a flow identifier indicated in the flow information comprised transmission quality measurement request. The first flow is different from the second flow on which the data was transmitted by the second client node 121.Receiving the DL monitoring packet may comprise recording a time T2 when the DL monitoring packet is received.Action 303The client node 121 determines a crossflow RTT based on the time T 1 and the time T2. T2 represents the time of reception of the DL monitoring packet. The crossflow RTT may e.g., comprise UL / DL / E2E latency. The client node 121 may further determine e.g., UL / DL crossflow bitrate, UL / BL / E2E crossflow packet loss rate and / or UL / DL / E2E crossflow jitter.Action 304The client node 121 sends a measurement report to the sever node. The report comprises a determined crossflow RTT. The crossflow RTT may e.g., comprise UL / DL / E2E latency. The measurement report may further comprise e.g., UL / DL crossflow bitrate, UL / BL / E2E crossflow packet loss rate and / or UL / DL / E2E crossflow jitter. The measurement report may also be referred to as a SEALDD transmission quality measurement notification, and the measurements may e.g., be comprised in ameasurement report list, such as a SEALDD transmission quality measurement report list, in the measurement report. The measurement report list may e.g., comprise any of the information elements in table 9.7.3.3-2 belowA method according to embodiments herein will now be described from the view of the client node 121 , such as a SEALDD client, e.g., the second client node 121 , together with Figure 4. Figure 4 depicts example embodiments of a method performed by the client node 121 , such as a SEALDD client, for 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.Action 401The client node 121 receives a transmission quality measurement request from the server node 111 , such as a SEALDD server. The request comprises a crossflow RTT measurement requirement, at least two client node 121 identifiers, such as identifiers for the first client node 121 and the second client node 121 , and flow information, e.g., for uplink and downlink, associated with the multi modal identifier. The transmission quality measurement request may also be referred to as a SEALDD transmission quality measurement subscription request. The request requests the client nodes, such as the first client node 121 and the second client node 121, to perform quality measurements, such as cross flow quality measurements. The crossflow RTT measurement requirement comprises determining the crossflow RTT between the flows indicated in the flow information. The crossflow quality measurements may e.g., comprise crossflow RTT measurements, e.g., UL / DL / E2E latency, UL / DL crossflow bitrate, UL / BL / E2E crossflow packet loss rate and / or UL / DL / E2E crossflow jitter.Action 402The client node 121 transmits data as an UL packet on a second flow, the UL packet comprising the time T1. T1 represents a time when the client node 121 transmitted the data comprised in the UL packet. Thus, T1 may e.g., be used by the client node 121, such as the first client node 121, to determine e.g., a crossflow RTT. The client node 121 may transmit the UL packet on a second flow associated with a flow identifier indicated in the flow information comprised transmission quality measurement request. The second flow is different from the first flow on which the data will be received by a client node 121 such as the first client node 121.Transmitting the data may comprise recording the time T2 when starting the transmission.The first client node 121 and the second client node 121 may in some examples be the same client node 121. In such examples, the actions described under Figure 3 and Figure 4 may be combined. In such examples the client node 121 transmits data on second flow and receives data on the first flow, which are different flows.Examples of embodiments herein may enable the XR support in SEALDD layer. In addition, the solution enables the more detailed procedure for the QoS measurement for XR scenario as shown in Figure 5:VAL server provides the monitoring requirement with a multi-modal service ID and an ordered list of flow IDs (typically a flow pair) over SEALDD-S. Then SEALDD server sends the monitoring configuration to SEALDD client with associated flows over SEALDD- UU.SEALDD client records T 1 when it sends a packet of the 1st flow (Uplink) to SEALDD server (such a packet may be the 1st packet in a PDU set, then SEALDD client doesn’t need to record timestamp for the rest packets in a set) , and records T2 when it later receives an initial packet of the 2nd flow (or the last packet of a PDU set). Then SEALDD client is able to calculate the crossflow RTT with (T2-T1) for the associated flows.NOTE: different data flows are carried in different SEALDD connections.Examples of embodiments herein may support QoS measurement for XR ecosystem with multiple UEs, e.g., when each UE (e.g. haptic glove, HMD) is installed with a SEALDD client.In this scenario, the 1st UE responsible for UL data sends T1 in UL SEALDD data to SEALDD server, and SEALDD server records T1 and sends T1 in DL SEALDD data to the 2nd UE.NOTE: For DL PDU set, SEALDD server identifies the last packet (i.e. end PDU) in the DL PDU set and sends T 1 along with the last DL packet to SEALDD client.If it is not the same SEALDD server for associated flows, inter-SEALDD server communication is needed to convey information. This information may take a form of the UE / flow sequence that shall be implemented by SEALDD server(s) in order to measure the QoS values in XR ecosystem scenarios.Below procedure describes how to measure crossflow RTT in clause 9.7.2.3 of 3GPP TS 23.433 v19.0.0, impacts underlined, assuming the same SEALDD server is used for XR application.9.7.2.3 Data transmission quality measurement reported by SEALDD clientFigure 9.7.2.3-1 illustrate the procedure for SEALDD enabled data transmission quality measurement for VAL traffic. The SEALDD client receives transmission quality measurement requirement, decides to start VAL data transmission monitoring and generates measurement reports.Figure 6: VAL data transmission quality measurement reported by SEALDD client1. An on-going regular data transmission connection is established according to clause 9.2.2.2.The transmission quality measurement can be triggered by VAL server or VAL client, which is described in step 2 to step 5 and step 6, correspondingly.The request may include two VAL UE IDs and corresponding flow information (e.g. [UE1 / UL flow, UE2 / DL flowl) associated in the same multi-modal service for crossflow RTT measurement.2. The VAL server sends a SEALDD transmission quality measurement subscription request to the SEALDD server. The request includes the identifiers of the application traffic (e.g. VAL service ID, VAL server ID), requirement of transmission quality measurement (e.g. latency jitter, bitrate) and measurement target UE (e.g. a single UE, a group of UEs or all UEs), and may also include reporting criteria, reporting frequency, spatial condition and temporal condition.NOTE 1 : The spatial and / or temporal condition can be used by SEALDD client to apply when and where the measurement is performed. For instance, the measurement is expected to be done for a group of VAL UEs with a scheduled route (from city A to city B via highway A2 and A3), from 9:00 a.m. to 11:00 a.m. on Tuesday and from 1:00 p.m. to 5:00 p.m. on Thursday.3. Upon receiving the request, the SEALDD server performs an authorization check. If authorization is successful, the SEALDD server responds to the VAL server.4-5. The SEALDD server sends a SEALDD transmission quality measurement subscription request to the SEALDD client and the SEALDD client responds to the SEALDD server. The SEALDD client, based on the received service quality guarantee policy including thresholds and action, can take corrective action as described in clause 9.7.2.3.If crossflow RTT measurement requirement is received from the VAL server, the SEALDD server identifies the SEALDD connections for the involved VAL UEs and sends to the SEALDD client(s) with crossflow RTT measurement requirement including corresponding UL / DL flow information.6. The VAL client triggers the SEALDD transmission quality measurement procedure to the SEALDD client, in order to collect the measurement report information.7. After SEALDD client determines to start measurement process, upon UL packet arrival, the SEALDD client initiates the UL packet delay measurement. The SEALDD client encapsulates the UL monitoring packet (i.e. UL SEALDD packet with SEALDD UL monitoring header and VAL traffic as pay load for VAL data transmission quality monitoring) with local time T1 when the SEALDD client sends out the UL monitoring packet. The SEALDD client considers the spatial and / or temporal conditions when starting / resuming the transmission quality measurement. If the conditions are not satisfied, the SEALDD client stops / suspends the transmission quality measurement.For crossflow RTT measurement, the SEALDD client received UL flow information starts recording local time T1 when sending out the 1stUL packet (or the 1stUL packet in a PDU set) matching the UL flow information to the SEALDD server. The T1 is sent in the encapsulated UL monitoring packet to the SEALDD server.8. The SEALDD server receives the UL monitoring packet, and records the local time T2.9. Similarly, the SEALDD server encapsulates the DL monitoring packet (i.e. DL SEALDD packet with SEALDD DL monitoring header and VAL traffic as payload, or dummy UL SEALDD packet generated for data transmission quality monitoring in case there is no DL VAL traffic for DL packet delay monitoring) with local time T2 recorded in step 8 and local time T3 when the SEALDD server sends out the DL monitoring packet.NOTE 2: When the SEALDD server sends the dummy UL packet as monitoring response to the SEALDD client depends on SEALDD server implementation.For crossflow RTT measurement, when the 1stDL packet (or the last DL packet in a PDU set) matching the received DL flow information is to be sent, the SEALDD server encapsulates the DL monitoring packet with previously received T1 and sends the DL monitoring packet to the SEALDD client.10. The SEALDD client records the local time T4 when the SEALDD client receives the DL monitoring packet and calculates the latency with Tl, T2, T3, T4. The SEALDD client can also calculate the bitrate and jitter over a certain period over a specific SEALDD connection by recording the status of the SEALDD monitoring packets. The SEALDD client also evaluates the reporting criteria if present in the SEALDD transmission quality measurement subscription request in order to generate the transmission quality measurement report.For crossflow RTT measurement, if Tl is received in the DL packet, the SEALDD client records local time T2 and calculates RTT based on Tl and T2,Depending on which entity triggers the data transmission quality measurement, step 11 and step 12 corresponds to step 2 to step 5, step 13 corresponds to step 6.11-12. The SEALDD client reports the data transmission quality measurement results (e.g. latency jitter, bitrate, crossflow RTT) to the VAL server via the SEALDD server.13. The SEALDD client reports the data transmission quality measurement results to the VAL client.When a VAL group ID or a list of VAL UE IDs or all VAL UEs indication is received in step 2, step 4 to step 11 is repeated for VAL UEs in the group / list or for all VAL UEs. The SEALDD server maps the VAL UE group ID to a list of VAL UE IDs if a VAL group ID is received. The SEALDD server identifies SEALDD connections corresponding to the desired VAL UE(s) to trigger measurement. And depending on the reporting requirement for multiple UEs, the SEALDD server collects and aggregates the needed report for the VAL server.Proposed in 3GPP 23.700-23 V0.1.0 in bold italic.7.1 Mapping of solutions to key issuesTable 7.1-1 Mapping of solutions to key issues7.x Solution #X: Support of QoS measurement for Multi- Modal traffic in SEALDD layer7.x.1 Architecture ImpactsThis solution is based on architecture of SEALDD as described in 3GPP TS 23.433

[23433] ,7.x.2 Solution descriptionThe solution improves the SEALDD layer defined in 3GPP TS 23.433, i.e.:1. The Multi-Modal Service Info is included into the SEALDD enabled data transmission quality measurement subscription request in order to signal the multi-modal service QoS request in SEALDD layer;2. The handling of the Multi-Modal Service Info is specified in Data transmission quality measurement; and3. Finer granularity of QoS measurement identifiers, i.e., UL / DL / E2E. Example: UL jitter.4. New multi-modal crossflows identifiers are proposed including Multi-Modal flows aggregation method. Examples: maximum crossflow average uplink PLR for X multi-modal flows.5. Mapping between measured QoS and XR specific QoE metrics, e.g., Motion-to-Photon for edge deployed XR application.7.X.2.2 Impact to existing SEALDD proceduresThe SEALDD procedures and information flows in 3GPP TS 23.433

[23433] can be enhanced (highlighted in bold italics) as follows.NOTE: SEALDD data transmission procedures with single SEALDD connection are described as typical example below.7.x.3 Solution evaluationThis solution addresses KI#1 to support:- what KPI the application enabling layer could provide that impact the QoS of the XR services.- how the KPI could be measured at the application enabling layer, and the enhancement of the SEALDD services.Proposed in 3GPP 23.700-23 VO.1.0 in bold italic.7.1 Mapping of solutions to key issuesTable 7.1-1 Mapping of solutions to key issues7.x Solution #x: Support of Multi-Modal traffic indication in SEALDD layer7.x.1 Architecture ImpactsThis solution is based on architecture of SEALDD as described in 3GPP TS 23.433

[23433] ,7.x.2 Solution description7.X.2.1 GeneralThis solution addesses the improvement of the SEALDD layer to support Multi-Modal service.The solution improves the SEALDD layer defined in 3GPP TS 23.433, i.e.:1. The Application layer Multi-modal Service Identifier is included into the SEALDD enabled Regular transmission request in order to signal the multi-modal service in SEALDD layer;2. The handling of the Application layer Multi-modal Service Identifier is specified in SEALDD enabled regular data transmission connection establishment procedure; and3. The Multi-Modal Flow information is included into the SEALDD enabled regular transmission response to signal the current status of the multi-modal service in SEALDD layer.7.X.2.2 Impact to existing SEALDD proceduresThe SEALDD procedures and information flows in 3GPP TS 23.433

[23433] can be enhanced (highlighted in bold italics) as follows.NOTE: SEALDD data transmission procedures with single SEALDD connection are described as typical example below.7.x.3 Solution evaluationThis solution addresses KI#2 for the following aspects:- Whether and how to support the interaction between the application enablement layer and 5G CN to manage E2E multi-modal communication flows between application clients and application servers?- Whether and how SEALDD may be enhanced to assist in managing E2E multi-modal communication flows between application clients and application servers involved in the same application service (e.g., support for multi-modal aware SEALDD flow management and policies)?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.The server node 111 may comprise an input and output interface 1100 configured to communicate with each other. The input and output interface1100 may comprise a receiver, e.g. wired and / or wireless, (not shown) and a transmitter, e.g. wired and / or wireless, (not shown).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.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.The server node 111 and / or the processor 1110 is configured to receive a data transmission request from a VAL server 112. The data transmission request adapted to comprise a multi-modal service identifier.The server node 111 and / or the processor 1110 is configured to allocate at least one flow identifier, such as a SEALDD-S multi modal flow identifier, associated with the multi modal service identifier.The server node 111 and / or the processor 1110 is configured to send a transmission quality measurement request to a first client node 121 and a second client node 121, such as a SEALDD client. The request is adapted to comprise a crossflow RTT measurement requirement, at least two client node 121 identifiers and flow information, e.g., for uplink and downlink, associated with the multi modal identifier.The server node 111 and / or the processor 1110 is configured to send a DL monitoring packet to a first client node 121 , such as a SEALDD client. The DL monitoring packet is adapted to comprise data transmitted by a second client node 121 and a time T 1 recorded by the second client node 121, andThe server node 111 and / or the processor 1110 is configured to receive a measurement report from the first client node 121. The report is adapted to comprise a determined crossflow RTT.In some embodiments, the server node 111 and / or the processor 1110 may further be configured to receive a transmission quality measurement subscription request from the VAL server 112. The request is adapted to comprise a crossflow RTT measurement requirement, at least two client node 121 identifiers and flow information associated with the multi modal identifier.In some embodiments, the DL monitoring packet is adapted to be transmitted on a first flow and the data was received from the second client node 121 on a second flow, different from the first flow.In some embodiments, the flow information indicates the first flow and the second flow. The crossflow RTT measurement requirement comprises to determine the crossflow RTT between the flows indicated in the flow information.In some embodiments, the server node 111 and / or the processor 1110 may further be configured to send a data transmission response to the VAL server 112. The data transmission response adapted to comprise a total number of flows and the at least one flow identifier associated with the multimodal service identifier.In some embodiments, the server node 111 and / or the processor 1110 may further be configured to receive, from the second client node 121, data as an UL packet on a second flow, the UL packet adapted to comprise the time T 1.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.The memory 1120 is arranged to be used to store instructions, data, configurations, identifiers, measurements, indications, notifications, resources, flows,policies, and applications to perform the methods herein when being executed in the server node 111.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.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.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.As will be readily understood by those familiar with communications design, that functions means or modules may be implemented using digital logic and / or one or more microcontrollers, microprocessors, or other digital hardware. In some embodiments, several or all of the various functions may be implemented together, such as in a single application-specific integrated circuit (ASIC), or in two or more separate devices with appropriate hardware and / or software interfaces between them. Several of the functions may be implemented on a processor shared with other functional components of a radio network node, for example.Alternatively, several of the functional elements of the processing means discussed may be provided through the use of dedicated hardware, while others are provided with hardware for executing software, in association with the appropriate software or firmware. Thus, the term “processor” or “controller” as used herein does not exclusively refer to hardware capable of executing software and may implicitly include, without limitation, digital signal processor (DSP) hardware, read-only memory (ROM) for storing software, random-access memory for storing software and / or program or application data, and non-volatile memory. Other hardware, conventional and / or custom, may also be included. Designers of communications receivers will appreciate the cost, performance, and maintenance trade-offs inherent in these design choices.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.To perform the method actions above, the client node 121, such as the first client node 121 , e.g., a SEALDD client, is configured to handle data delivery in the wireless communications network 100. The client node 121 may comprise an arrangement depicted in Figure 12.The client node 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).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 client node 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 client node 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 client node 121.The client node 121 , such as a first client node 121 , such as a SEALDD client, and / or processor 1210 is configured to handle data delivery in the wireless communication network 100.The client node 121 and / or processor 1210 is configured to receive a transmission quality measurement request from a server node 111 , such as a SEALDD server. The request adapted to comprise a crossflow RTT measurement requirement, at least two client node 121 identifiers and flow information associated with a multi modal identifier.The client node 121 and / or processor 1210 is configured to receive a DL monitoring packet from the server node 111. The DL monitoring packet is adapted to comprise data transmitted by a second client node 121 and a time T1 recorded by the second client node 121.The client node 121 and / or processor 1210 is configured to determine a crossflow RTT based on the time T 1 and a time T2. T2 is adapted to represent a time of reception of the DL monitoring packet.The client node 121 and / or processor 1210 is configured to send a measurement report to the sever node 111. The report is adapted to comprise a determined crossflow RTT.In some embodiments, the DL monitoring packet is adapted to be received on a first flow and the data was transmitted by the second client node 121 on a second flow.In some embodiments, the flow information is adapted to indicate the first flow and the second flow. The crossflow RTT measurement requirement comprises to determine the crossflow RTT between the flows indicated in the flow information.The client node 121 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 client node 121.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 client node 121.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 client node 121 to perform the actions above.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.Thus, embodiments herein may disclose the client node 121 configured to handle data delivery in the wireless communications network 100. The client node 121 comprises the processor 1210 and the memory 1220, said memory 1220 comprising instructionsexecutable by said processor 1210 whereby said client node 121 is operative to perform any of the methods herein.As will be readily understood by those familiar with communications design, that functions means or modules may be implemented using digital logic and / or one or more microcontrollers, microprocessors, or other digital hardware. In some embodiments, several or all of the various functions may be implemented together, such as in a single application-specific integrated circuit (ASIC), or in two or more separate devices with appropriate hardware and / or software interfaces between them. Several of the functions may be implemented on a processor shared with other functional components of a radio network node, for example.Alternatively, several of the functional elements of the processing means discussed may be provided through the use of dedicated hardware, while others are provided with hardware for executing software, in association with the appropriate software or firmware. Thus, the term “processor” or “controller” as used herein does not exclusively refer to hardware capable of executing software and may implicitly include, without limitation, digital signal processor (DSP) hardware, read-only memory (ROM) for storing software, random-access memory for storing software and / or program or application data, and non-volatile memory. Other hardware, conventional and / or custom, may also be included. Designers of communications receivers will appreciate the cost, performance, and maintenance trade-offs inherent in these design choices.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.To perform the method actions above, the client node 121 , such as the second client node 121 , e.g., as a SEALDD client, is configured to handle data delivery in the wireless communications network 100. The client node 121 may comprise an arrangement depicted in Figure 13.The client node 121 may comprise an input and output interface 1300 configured to communicate with each other. The input and output interface 1300 may comprise a receiver, e.g. wired and / or wireless, (not shown) and a transmitter, e.g. wired and / or wireless, (not shown).The embodiments herein may be implemented through a respective processor or one or more processors, such as at least one processor 1310 of a processing circuitry in the client node 121 depicted in Figure 13, 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 client node 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 client node 121.The client node 121 , such as a second client node 121, such as a SEALDD client, and / or processor 1310 is configured to handle data delivery in the wireless communication network 100.The client node 121 and / or processor 1310 is configured to receive a transmission quality measurement request from a server node 111 , such as a SEALDD server. The request is adapted to comprise a crossflow RTT measurement requirement, at least two client node 121 identifiers and flow information associated with a multi modal identifier, The client node 121 and / or processor 1310 is configured to transmit data as an uplink packet on a second flow. The UL packet is adapted to comprise the time T 1.The client node 121 may further comprise respective a memory 1320 comprising one or more memory units. The memory 1320 comprises instructions executable by the processor 1310 in the client node 121.The memory 1320 is arranged to be used to store instructions, data, configurations, identifiers, measurements, indications, notifications, resources, policies, and applications to perform the methods herein when being executed in the client node 121.In some embodiments, a computer program 1330 comprises instructions, which when executed by the at least one processor 1310, cause the at least one processor 1310 of the client node 121 to perform the actions above.In some embodiments, a respective carrier 1340 comprises the respective computer program 1330, wherein the carrier 1340 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.Thus, embodiments herein may disclose the client node 121 configured to handle data delivery in the wireless communications network 100. The client node 121 comprises the processor 1310 and the memory 1320, said memory 1320 comprising instructions executable by said processor 1310 whereby said client node 121 is operative to perform any of the methods herein.As will be readily understood by those familiar with communications design, that functions means or modules may be implemented using digital logic and / or one or more microcontrollers, microprocessors, or other digital hardware. In some embodiments, several or all of the various functions may be implemented together, such as in a single application-specific integrated circuit (ASIC), or in two or more separate devices with appropriate hardware and / or software interfaces between them. Several of the functions may be implemented on a processor shared with other functional components of a radio network node, for example.Alternatively, several of the functional elements of the processing means discussed may be provided through the use of dedicated hardware, while others are provided with hardware for executing software, in association with the appropriate software or firmware. Thus, the term “processor” or “controller” as used herein does not exclusively refer to hardware capable of executing software and may implicitly include, without limitation, digital signal processor (DSP) hardware, read-only memory (ROM) for storing software, random-access memory for storing software and / or program or application data, and non-volatile memory. Other hardware, conventional and / or custom, may also be included. Designers of communications receivers will appreciate the cost, performance, and maintenance trade-offs inherent in these design choices.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, whichmay 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.ADDITIONAL EXPLANATIONSome 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.Figure 14 shows an example of a communication system QQ100 in accordance with some embodiments.In the example, the communication system QQ100 includes a telecommunication network QQ102 that includes an access network QQ104, such as a radio access network RAN, and a core network QQ106, which includes one or more core network nodes QQ108 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 anynode in the telecommunication network QQ102, including one or more network nodes QQ110 and / or core network nodes QQ108.Examples of an ORAN network node include an open radio unit 0-Rll, an open distributed unit 0-Dll, an open central unit O-CU, including an O-CU control plane O-CU- CP or an O-CU user plane O-CU-UP, a RAN intelligent controller near-real time or non- real time hosting software or software plug-ins, such as a near-real time control application e.g., xApp or a non-real time control application e.g., rApp, or any combination thereof the adjective “open” designating support of an ORAN specification. The network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an A1, F1, W1, E1 , E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN access node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment described further below in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an 0-2 interface defined by the O-RAN Alliance or comparable technologies. The network nodes QQ110 facilitate direct or indirect connection of 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.Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system QQ100 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system QQ100 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.The UEs QQ112 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes QQ110 and other communication devices. Similarly, the network nodes QQ110 are arranged, capable, configured, and / or operable to communicate directlyor indirectly with the UEs QQ112 and / or with other network nodes or equipment in the telecommunication network QQ102 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunication network QQ102.In the depicted example, the core network QQ106 connects the network nodes QQ110 to one or more hosts, such as host QQ116. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network QQ106 includes one more core network nodes e.g., core network node QQ108 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.The host QQ116 may be under the ownership or control of a service provider other than an operator or provider of the access network QQ104 and / or the telecommunication network QQ102, and may be operated by the service provider or on behalf of the service provider. The host QQ116 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.As a whole, the communication system QQ100 of Figure 14 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 anyother appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access WiMax, Bluetooth, Z-Wave, Near Field Communication NFC ZigBee, LiFi, and / or any low-power wide-area network LPWAN standards such as LoRa and Sigfox.In some examples, the telecommunication network QQ102 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network QQ102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network QQ102. For example, the telecommunications network QQ102 may provide Ultra Reliable Low Latency Communication URLLC services to some UEs, while providing Enhanced Mobile Broadband eMBB services to other UEs, and / or Massive Machine Type Communication mMTC / Massive loT services to yet further UEs.In some examples, the UEs QQ112 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network QQ104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network QQ104. Additionally, a UE may be configured for operating in single- or multi- RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR New Radio and LTE, i.e. being configured for multi-radio dual connectivity MR-DC, such as E-UTRAN Evolved-UMTS Terrestrial Radio Access Network New Radio - Dual Connectivity EN-DC.In the example, the hub QQ114 communicates with the access network QQ104 to facilitate indirect communication between one or more UEs e.g., UE QQ112c and / or QQ112d and network nodes e.g., network node QQ110b. In some examples, the hub QQ114 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub QQ114 may be a broadband router enabling access to the core network QQ106 for the UEs. As another example, the hub QQ114 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes QQ110, or by executable code, script, process, or other instructions in the hub QQ114. As another example, the hub QQ114 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub QQ114 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub QQ114 may retrieve VR assets,video, audio, or other media or data related to sensory information via a network node, which the hub QQ114 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub QQ114 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.The hub QQ114 may have a constant / persistent or intermittent connection to the network node QQ110b. The hub QQ114 may also allow for a different communication scheme and / or schedule between the hub QQ114 and UEs e.g., UE QQ112c and / or QQ112d, and between the hub QQ114 and the core network QQ106. In other examples, the hub QQ114 is connected to the core network QQ106 and / or one or more UEs via a wired connection. Moreover, the hub QQ114 may be configured to connect to an M2M service provider over the access network QQ104 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes QQ110 while still connected via the hub QQ114 via a wired or wireless connection. In some embodiments, the hub QQ114 may be a dedicated hub - that is, a hub whose primary function is to route communications to / from the UEs from / to the network node QQ110b. In other embodiments, the hub QQ114 may be a 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.Figure 15 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.A UE may support device-to-device D2D communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-RangeCommunication DSRC, vehicle-to-vehicle V2V, vehicle-to-infrastructure V2I, or vehicle-to- everything V2X. In other examples, a UE may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user e.g., a smart sprinkler controller. Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user e.g., a smart power meter.The UE QQ200 includes processing circuitry QQ202 that is operatively coupled via a bus QQ204 to an input / output interface QQ206, a power source QQ208, a memory QQ210, a communication interface QQ212, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 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.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, forinstance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus USB port may be used to provide an input device and an output device.In some embodiments, the power source QQ208 is structured as a battery or battery pack. Other types of power sources, such as an external power source e.g., an electricity outlet, photovoltaic device, or power cell, may be used. The power source QQ208 may further include power circuitry for delivering power from the power source QQ208 itself, and / or an external power source, to the various parts of the UE QQ200 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source QQ208. Power circuitry may perform any formatting, converting, or other modification to the power from the power source QQ208 to make the power suitable for the respective components of the UE QQ200 to which power is supplied.The memory QQ210 may be or be configured to include memory such as random access memory RAM, read-only memory ROM, programmable read-only memory PROM, erasable programmable read-only memory EPROM, electrically erasable programmable 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 toaccess instructions, application programs and the like, stored on transitory or non- transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory QQ210, which may be or comprise a device-readable storage medium.The processing circuitry QQ202 may be configured to communicate with an access network or other network using the communication interface QQ212. The communication interface QQ212 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna QQ222. The communication interface QQ212 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication e.g., another UE or a network node in an access network. Each transceiver may include a transmitter QQ218 and / or a receiver QQ220 appropriate to provide network communications e.g., optical, electrical, frequency allocations, and so forth. Moreover, the transmitter QQ218 and receiver QQ220 may be coupled to one or more antennas e.g., antenna QQ222 and may share circuit components, software or firmware, or alternatively be implemented separately.In the illustrated embodiment, communication functions of the communication interface QQ212 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system GPS to determine a location, another like communication function, or any combination thereof. Communications may be implemented in according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access CDMA, Wideband Code Division Multiple Access WCDMA, GSM, LTE, New Radio NR, UMTS, WiMax, Ethernet, transmission control protocol / internet protocol TCP / IP, synchronous optical networking SONET, Asynchronous Transfer Mode ATM, QUIC, Hypertext Transfer Protocol HTTP, and so forth.Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface QQ212, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic e.g., once every 15 minutes if it reports the sensed temperature, random e.g., to even out the load from reporting from several sensors, in response to a triggering event e.g., whenmoisture is detected an alert is sent, in response to a request e.g., a user initiated request, or a continuous stream e.g., a live video feed of a patient.As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.A UE, when in the form of an Internet of Things loT device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a 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 15.As yet another specific example, in an loT scenario, a UE may represent a machine or other device that performs monitoring and / or measurements, and transmits the results of such monitoring and / or measurements to another UE and / or a network node. The UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3GPP NB-loT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’sspeed information obtained through a speed sensor to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone e.g. by controlling an actuator to increase or decrease the drone’s speed. The first and / or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.Figure 16 shows a network node QQ300 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunication network. Examples of network nodes include, but are not limited to, access points APs e.g., radio access points, base stations BSs e.g., radio base stations, Node Bs, evolved Node Bs eNBs and NR NodeBs gNBs, O-RAN nodes or components of an O-RAN node e.g., O-RU, O-DU, O-CU.Base stations may be categorized based on the amount of coverage they provide or, stated differently, their transmit power level and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more or all parts of a distributed radio base station such as centralized digital units, distributed units e.g., in an O-RAN access node and / or remote radio units RRUs, sometimes referred to as Remote Radio Heads RRHs. Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system DAS.Other examples of network nodes include multiple transmission point multi-TRP 5G access nodes, multi-standard radio MSR equipment such as MSR BSs, network controllers such as radio network controllers RNCs or base station controllers BSCs, base transceiver stations BTSs, transmission points, transmission nodes, multi-cell / multicast coordination entities MCEs, Operation and Maintenance O&M nodes, Operations Support System OSS nodes, Self-Organizing Network SON nodes, positioning nodes e.g., Evolved Serving Mobile Location Centers E-SMLCs, and / or Minimization of Drive Tests MDTs.The network node QQ300 includes a processing circuitry QQ302, a memoryQQ304, a communication interface QQ306, and a power source QQ308. The networknode QQ300 may be composed of multiple physically separate components e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc., which may each have their own respective components. In certain scenarios in which the network node QQ300 comprises multiple separate components e.g., BTS and BSC components, one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node QQ300 may be configured to support multiple radio access technologies RATs. In such embodiments, some components may be duplicated e.g., separate memory QQ304 for different RATs and some components may be reused e.g., a same antenna QQ310 may be shared by different RATs. The network node QQ300 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node QQ300, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification RFID or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node QQ300.The processing circuitry QQ302 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other network node QQ300 components, such as the memory QQ304, to provide network node QQ300 functionality.In some embodiments, the processing circuitry QQ302 includes a system on a chip SOC. In some embodiments, the processing circuitry QQ302 includes one or more of radio frequency RF transceiver circuitry QQ312 and baseband processing circuitry QQ314. In some embodiments, the radio frequency RF transceiver circuitry QQ312 and the baseband processing circuitry QQ314 may be on separate chips or sets of chips, boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry QQ312 and baseband processing circuitry QQ314 may be on the same chip or set of chips, boards, or units.The memory QQ304 may comprise any form of volatile or non-volatile computer- readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memoryRAM, read-only memory ROM, mass storage media for example, a hard disk, removable storage media for example, a flash drive, a Compact Disk CD or a Digital Video Disk DVD, and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry QQ302. The memory QQ304 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry QQ302 and utilized by the network node QQ300. The memory QQ304 may be used to store any calculations made by the processing circuitry QQ302 and / or any data received via the communication interface QQ306. In some embodiments, the processing circuitry QQ302 and memory QQ304 is integrated.The communication interface QQ306 is used in wired or wireless communication of 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.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 thecommunication interface QQ306. In still other embodiments, the communication interface QQ306 includes one or more ports or terminals QQ316, the radio front-end circuitry QQ318, and the RF transceiver circuitry QQ312, as part of a radio unit not shown, and the communication interface QQ306 communicates with the baseband processing circuitry QQ314, which is part of a digital unit not shown.The antenna QQ310 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna QQ310 may be coupled to the radio front-end circuitry QQ318 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna QQ310 is separate from the network node QQ300 and connectable to the network node QQ300 through an interface or port.The antenna QQ310, communication interface QQ306, and / or the processing circuitry QQ302 may be configured to perform any receiving operations and / or certain obtaining operations described herein as being performed by the network node. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna QQ310, the communication interface QQ306, and / or the processing circuitry QQ302 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.The power source QQ308 provides power to the various components of network node QQ300 in a form suitable for the respective components e.g., at a voltage and current level needed for each respective component. The power source QQ308 may further comprise, or be coupled to, power management circuitry to supply the components of the network node QQ300 with power for performing the functionality described herein. For example, the network node QQ300 may be connectable to an external power source e.g., the power grid, an electricity outlet via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source QQ308. As a further example, the power source QQ308 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.Embodiments of the network node QQ300 may include additional components beyond those shown in Figure 16 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionalitynecessary to support the subject matter described herein. For example, the network node QQ300 may include user interface equipment to allow input of information into the network node QQ300 and to allow output of information from the network node QQ300. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node QQ300.Figure 17 is a block diagram of a host QQ400, which may be an embodiment of the host QQ116 of Figure 14, in accordance with various aspects described herein. As used herein, the host QQ400 may be or comprise various combinations hardware and / or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm. The host QQ400 may provide one or more services to one or more UEs.The host QQ400 includes processing circuitry QQ402 that is operatively coupled via a bus QQ404 to an input / output interface QQ406, a network interface QQ408, a power source QQ410, and a memory QQ412. Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures 14 and 16, such that the descriptions thereof are generally applicable to the corresponding components of host QQ400.The memory QQ412 may include one or more computer programs including one or more host application programs QQ414 and data QQ416, which may include user data, e.g., data generated by a UE for the host QQ400 or data generated by the host QQ400 for a UE. Embodiments of the host QQ400 may utilize only a subset or all of the components shown. The host application programs QQ414 may be implemented in a container-based architecture and may provide support for video codecs e.g., Versatile Video Coding VVC, High Efficiency Video Coding HEVC, Advanced Video Coding AVC, MPEG, VP9 and audio codecs e.g., FLAG, Advanced Audio Coding AAC, MPEG, G.711 , including transcoding for multiple different classes, types, or implementations of UEs e.g., handsets, desktop computers, wearable display systems, heads-up display systems. The host application programs QQ414 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network. Accordingly, the host QQ400 may select and / or indicate a different host for over-the-top services for a UE. The host application programs QQ414 may support various protocols, such as the HTTP LiveStreaming HLS protocol, Real-Time Messaging Protocol RTMP, Real-Time Streaming Protocol RTSP, Dynamic Adaptive Streaming over HTTP MPEG-DASH, etc.Figure 18 is a block diagram illustrating a virtualization environment QQ500 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines VMs implemented in one or more virtual environments QQ500 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity e.g., a core network node or host, then the node may be entirely virtualized. In some embodiments, the virtualization environment QQ500 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an 0-2 interface.Applications QQ502 which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc. are run in the virtualization environment Q400 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.Hardware QQ504 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers QQ506 also referred to as hypervisors or virtual machine monitors VMMs, provide VMs QQ508a and QQ508b one or more of which may be generally referred to as VMs QQ508, and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer QQ506 may present a virtual operating platform that appears like networking hardware to the VMs QQ508.The VMs QQ508 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layerQQ506. Different embodiments of the instance of a virtual appliance QQ502 may be implemented on one or more of VMs QQ508, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization NFV. NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.In the context of NFV, a VM QQ508 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs QQ508, and that part of hardware QQ504 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs QQ508 on top of the hardware QQ504 and corresponds to the application QQ502.Hardware QQ504 may be implemented in a standalone network node with generic or specific components. Hardware QQ504 may implement some functions via virtualization. Alternatively, hardware QQ504 may be part of a larger cluster of hardware e.g. such as in a data center or CPE where many hardware nodes work together and are managed via management and orchestration QQ510, which, among others, oversees lifecycle management of applications QQ502. In some embodiments, hardware QQ504 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some 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.Figure 19 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 14 and / or UE QQ200 of Figure 15, network node such as network node QQ110a of Figure 14 and / or network node QQ300 of Figure 16, and host such as host QQ116 of Figure 14 and / or host QQ400 ofFigure 17 discussed in the preceding paragraphs will now be described with reference to Figure 19.Like host QQ400, embodiments of host QQ602 include hardware, such as a communication interface, processing circuitry, and memory. The host QQ602 also includes software, which is stored in or accessible by the host QQ602 and executable by the processing circuitry. The software includes a host application that may be operable to provide a service to a remote user, such as the UE QQ606 connecting via an over-the-top OTT connection QQ650 extending between the UE QQ606 and host QQ602. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection QQ650.The network node QQ604 includes hardware enabling it to communicate with the host QQ602 and UE QQ606. The connection QQ660 may be direct or pass through a core network like core network QQ106 of Figure 14 and / or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network may be a backbone network or the Internet.The UE QQ606 includes hardware and software, which is stored in or accessible by UE QQ606 and executable by the UE’s processing circuitry. The software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE QQ606 with the support of the host QQ602. In the host QQ602, an executing host application may communicate with the executing client application via the OTT connection QQ650 terminating at the UE QQ606 and host QQ602. In providing the service to the user, the UE's client application may receive request data from the host's host application and provide user data in response to the request data. The OTT connection QQ650 may transfer both the request data and the user data. The UE's client application may interact with the user to generate the user data that it provides to the host application through the OTT connection QQ650.The OTT connection QQ650 may extend via a connection QQ660 between the host QQ602 and the network node QQ604 and via a wireless connection QQ670 between the network node QQ604 and the UE QQ606 to provide the connection between the host QQ602 and the UE QQ606. The connection QQ660 and wireless connection QQ670, over which the OTT connection QQ650 may be provided, have been drawn abstractly to illustrate the communication between the host QQ602 and the UE QQ606 via the network node QQ604, without explicit reference to any intermediary devices and the precise routing of messages via these devices.As an example of transmitting data via the OTT connection QQ650, in step QQ608, the host QQ602 provides user data, which may be performed by executing a host application. In some embodiments, the user data is associated with a particular human user interacting with the UE QQ606. In other embodiments, the user data is associated with a UE QQ606 that shares data with the host QQ602 without explicit human interaction. In step QQ610, the host QQ602 initiates a transmission carrying the user data towards the UE QQ606. The host QQ602 may initiate the transmission responsive to a request transmitted by the UE QQ606. The request may be caused by human interaction with the UE QQ606 or by operation of the client application executing on the UE QQ606. The transmission may pass via the network node QQ604, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step QQ612, the network node QQ604 transmits to the UE QQ606 the user data that was carried in the transmission that the host QQ602 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step QQ614, the UE QQ606 receives the user data carried in the transmission, which may be performed by a client application executed on the UE QQ606 associated with the host application executed by the host QQ602.In some examples, the UE QQ606 executes a client application which provides user data to the host QQ602. The user data may be provided in reaction or response to the data received from the host QQ602. Accordingly, in step QQ616, the UE QQ606 may provide user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from the user via an input / output interface of the UE QQ606. Regardless of the specific manner in which the user data was provided, the UE QQ606 initiates, in step QQ618, transmission of the user data towards the host QQ602 via the network node QQ604. In step QQ620, in accordance with the teachings of the embodiments described throughout this disclosure, the network node QQ604 receives user data from the UE QQ606 and initiates transmission of the received user data towards the host QQ602. In step QQ622, the host QQ602 receives the user data carried in the transmission initiated by the UE QQ606.One or more of the various embodiments improve the performance of OTT services provided to the UE QQ606 using the OTT connection QQ650, in which the wireless connection QQ670 forms the last segment.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 videodata which may have been retrieved from a UE for use in creating maps. As another example, the host QQ602 may collect and analyze real-time data to assist in controlling vehicle congestion e.g., controlling traffic lights. As another example, the host QQ602 may store surveillance video uploaded by a UE. As another example, the host QQ602 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs. As other examples, the host QQ602 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services such as compiling diagrams etc. from data collected from remote devices, or any other function of collecting, retrieving, storing, analyzing and / or transmitting data.In some examples, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection QQ650 between the host QQ602 and UE QQ606, in response to variations in the measurement results. The measurement procedure and / or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host QQ602 and / or UE QQ606. In some embodiments, sensors not shown may be deployed in or in association with other devices through which the OTT connection QQ650 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software may compute or estimate the monitored quantities. The reconfiguring of the OTT connection QQ650 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node QQ604. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE 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.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 describedherein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally.When using the word "comprise" or “comprising” it shall be interpreted as nonlimiting, i.e. meaning "consist at least of".The embodiments herein are not limited to the preferred embodiments described above. Various alternatives, modifications and equivalents may be used.Abbreviation ExplanationBDT Background Data TransferDL DownlinkHoT Industrial Internet of ThingsSEAL Service enabler architecture layerSEALDD SEAL Data Delivery SEAL N RM SEAL Network Resource ManagementUE User EquipmentUL UplinkV2X Vehicle to EverythingVAL Vertical Application Layer 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: receiving (201) a data transmission request from a VAL server (112), the data transmission request comprising a multi-modal service identifier, allocating (202) at least one flow identifier, such as a SEALDD-S multi modal flow identifier, associated with the multi modal service identifier, sending (205) a transmission quality measurement request to a first client node (121) and a second client node (121), such as a SEALDD client, the request comprising a crossflow RTT measurement requirement, at least two client node (121) identifiers and flow information, e.g., for uplink and downlink, associated with the multi modal identifier, sending (207) a DL monitoring packet to a first client node (121), such as a SEALDD client, wherein the DL monitoring packet comprises data transmitted by a second client node (121) and a time T1 recorded by the second client node (121), and receiving (208) a measurement report from the first client node (121), which report comprises a determined crossflow round trip time, RTT.

2. The method according to claim 1 , further comprising: receiving (204) a transmission quality measurement subscription request from the VAL server (112), the request comprising a crossflow RTT measurement requirement, at least two client node (121) identifiers and flow information associated with the multi modal identifier.

3. The method according to any of claims 1-2, wherein the DL monitoring packet is transmitted on a first flow and the data was received from the second client node (121) on a second flow, different from the first flow.

4. The method according to claim 3, wherein the flow information indicates the first flow and the second flow, and wherein the crossflow RTT measurement requirement comprises determining the crossflow RTT between the flows indicated in the flow information.

5. The method according to any of claims 1-4, further comprising:sending (203) a data transmission response to the VAL server (112), the data transmission response comprising a total number of flows and the at least one flow identifier associated with the multimodal service identifier.

6. The method according to any of claims 1-5, further comprising: receiving (206), from the second client node (121), data as an UL packet on a second flow, the UL packet comprising the time T1.

7. 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-6.

8. A carrier (1140) comprising the computer program (1130) of claim 7, 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.

9. A method performed by a client node (121), such as a first client node (121), such as a SEALDD client, for handling data delivery in a wireless communication network (100), the method comprising: receiving (301) a transmission quality measurement request from a server node (111), such as a SEALDD server, the request comprising a crossflow RTT measurement requirement, at least two client node (121) identifiers and flow information associated with a multi modal identifier, receiving (302) a DL monitoring packet from the server node (111), wherein the DL monitoring packet comprises data transmitted by a second client node (121) and a time T1 recorded by the second client node (121). determining (303) a crossflow RTT based on the time T 1 and a time T2, wherein T2 represents a time of reception of the DL monitoring packet. sending (304) a measurement report to the sever node (111), which report comprises a determined crossflow round trip time, RTT.

10. The method according to claim 9, wherein the DL monitoring packet is received on a first flow and the data was transmitted by the second client node (121) on a second flow.11 . The method according to any of claims 9-10, wherein the flow information indicates the first flow and the second flow, and wherein the crossflow RTT measurement requirement comprises determining the crossflow RTT between the flows indicated in the flow information.

12. 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 9-11.

13. A carrier 1240 comprising the computer program (1230) of claim 12, 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.

14. A method performed by a client node (121), such as a second client node (121), such as a SEALDD client, for handling data delivery in a wireless communication network (100), the method comprising: receiving (401) a transmission quality measurement request from a server node (111), such as a SEALDD server, the request comprising a crossflow RTT measurement requirement, at least two client node (121) identifiers and flow information associated with a multi modal identifier, transmitting (402) data as an uplink packet on a second flow, the UL packet comprising the time T 1.

15. A computer program (1330) comprising instructions, which when executed by a processor (1310), causes the processor (1310) to perform actions according to claim 14.

16. A carrier (1340) comprising the computer program (1330) of claim 15, wherein the carrier (1340) 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.

17. 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:receive a data transmission request from a VAL server (112), the data transmission request adapted to comprise a multi-modal service identifier, allocate at least one flow identifier, such as a SEALDD-S multi modal flow identifier, associated with the multi modal service identifier, send a transmission quality measurement request to a first client node (121) and a second client node (121), such as a SEALDD client, the request adapted to comprise a crossflow RTT measurement requirement, at least two client node (121) identifiers and flow information, e.g., for uplink and downlink, associated with the multi modal identifier, send a DL monitoring packet to a first client node (121), such as a SEALDD client, wherein the DL monitoring packet is adapted to comprise data transmitted by a second client node (121) and a time T 1 recorded by the second client node (121), and receive a measurement report from the first client node (121), which report is adapted to comprise a determined crossflow round trip time, RTT.

18. The server node (111) according to claim 17, further being configured to: receive a transmission quality measurement subscription request from the VAL server (112), the request adapted to comprise a crossflow RTT measurement requirement, at least two client node (121) identifiers and flow information associated with the multi modal identifier.

19. The server node (111) according to any of claims 17-18, wherein the DL monitoring packet is adapted to be transmitted on a first flow and the data was received from the second client node (121) on a second flow, different from the first flow.

20. The server node (111) according to claim 19, wherein the flow information indicates the first flow and the second flow, and wherein the crossflow RTT measurement requirement comprises determining the crossflow RTT between the flows indicated in the flow information.

21. The server node (111) according to any of claims 17-20, further being configured to: send a data transmission response to the VAL server (112), the data transmission response adapted to comprise a total number of flows and the at least one flow identifier associated with the multimodal service identifier.

22. The server node (111) according to any of claims 17-21 , further being configured to: receive, from the second client node (121), data as an UL packet on a second flow, the UL packet adapted to comprise the time T 1.

23. A client node (121), such as a first client node (121), such as a SEALDD client, configured to handle data delivery in a wireless communication network (100), the client node further being configured to: receive a transmission quality measurement request from a server node (111), such as a SEALDD server, the request adapted to comprise a crossflow RTT measurement requirement, at least two client node (121) identifiers and flow information associated with a multi modal identifier, receive a DL monitoring packet from the server node (111), wherein the DL monitoring packet is adapted to comprise data transmitted by a second client node (121) and a time T 1 recorded by the second client node (121). determine a crossflow RTT based on the time T 1 and a time T2, wherein T2 is adapted to represents a time of reception of the DL monitoring packet. send a measurement report to the sever node (111), which report is adapted to comprise a determined crossflow round trip time, RTT.

24. The client node (121) according to claim 23, wherein the DL monitoring packet is adapted to be received on a first flow and the data was transmitted by the second client node (121) on a second flow.

25. The client node (121) according to any of claims 23-24, wherein the flow information is adapted to indicate the first flow and the second flow, and wherein the crossflow RTT measurement requirement comprises to determine the crossflow RTT between the flows indicated in the flow information.

26. A client node (121), such as a second client node (121), such as a SEALDD client, configured to handle data delivery in a wireless communication network (100), the client node (121) further being configured to: receive a transmission quality measurement request from a server node (111), such as a SEALDD server, the request adapted to comprise a crossflow RTTmeasurement requirement, at least two client node (121) identifiers and flow information associated with a multi modal identifier, transmit data as an uplink packet on a second flow, the UL packet adapted to comprise the time T1.

Images