Technique for handling multi-modal PDU sets

Abstract

A technique for handling multi-modal PDU sets is described. As to a method aspect of the technique performed by a wireless device, WD (100; 1700; 1991; 1992; 2030), wirelessly connected or connectable to an access network, AN (510), is provided. The method (300) comprises measuring (306) at the WD (100; 1700; 1991; 1992; 2030) at least one combined quality of service (QoS) parameter, and sending (310), to the AN (510), a report message (506) indicative of the measured (306) at least one combined QoS parameter. Each of the at least one combined QoS parameter is measured (306) for a combination of at least two PDU sets (750) in an uplink towards the AN (510). The at least two PDU sets (750) are mutually inter-dependent (760).

Description

[0001] Technique for handling multi-modal PDU sets

[0002] Technical Field

[0003] The present disclosure relates to a technique for handling multiple sets of packet data units (PDUs). More specifically, and without limitation, methods and devices are provided for handling multi-modal PDU sets.

[0004] Background

[0005] In the rapidly evolving landscape of telecommunications, the fifth generation (5G) of wireless technology specified by the Third Generation Partnership project (3GPP) has ushered in a new era of connectivity, promising unprecedented speeds, lower latency, and the capacity to support a burgeoning ecosystem of devices and applications. Among these, extended Reality (XR) services stand out as one of the most anticipated and demanding use cases, poised to transform the way we interact with digital content through immersive experiences that blend the physical and virtual worlds. As 5G networks continue to roll out globally, the potential for XR to revolutionize industries such as gaming, education, healthcare, and remote work is becoming increasingly tangible.

[0006] However, the delivery of XR services over 5G networks introduces complex challenges, particularly in terms of Quality of Service (QoS) management. XR applications often generate multiple, interdependent traffic flows— such as video, audio, and haptic feedback— that must be synchronized and delivered with stringent latency and reliability requirements. Ensuring a seamless and immersive user experience hinges on the network's ability to manage these flows effectively, a task made difficult by the dynamic nature of wireless environments and the diverse QoS demands of different XR modalities.

[0007] The existing technology, as standardized in 3GPP releases, has laid the groundwork for PDU Set based QoS handling, which allows for the grouping of Protocol Data Units (PDUs) carrying application payloads to be transmitted (e.g., sent) within the same QoS flow. However, this approach has its limitations, particularly when it comes to uplink transmission from User Equipment (UE) of multi-modal PDU sets to the network. The current standards do not provide a mechanism for the network to be aware of the QoS performance of interdependent PDU sets across multiple flows forming a multi-modal stream. This gap in the technology means that the network cannot optimize scheduling decisions and configurations, potentially compromising the QoS of XR services and, in turn, the end-user experience.

[0008] Summary

[0009] Accordingly, there is a need for a technique that enables handling multiple PDU sets, particularly for multi-modal services.

[0010] As to a first method aspect a method performed by a wireless device (WD), wirelessly connected or connectable to an access network (AN) is provided. The method comprises or initiates measuring at the WD at least one combined quality of service (QoS) parameter. Each of the at least one combined QoS parameter is measured for a combination of at least two PDU sets in an uplink towards the AN. The at least two PDU sets are mutually inter-dependent. The method further comprises or initiates sending, to the AN, a report message indicative of the measured at least one combined QoS parameter.

[0011] Herein the word transmit and send may be used interchangeably.

[0012] Embodiments can overcome the existing limitations, particularly when it comes to uplink transmission from the WD (e.g., a user equipment, UE) to the AN (e.g., a network node). The technique may enable modifying the standards to provide a mechanism for the AN to receive the combined QoS performance of interdependent PDU sets across multiple flows, such as a combined Packet Set Error Rate (PSER). Alternatively or in addition, the report message can enable the AN (e.g., the network node) to optimize scheduling decisions in the broadest sense, e.g. configurations. While the lack of such feedback has conventionally compromised the QoS of multi-modal services (e.g., XR services), same or further embodiments can ensure end-user experience by controlling the scheduling at the AN based on the at least one combined QoS parameter reported from the WD. Addressing this shortcoming is crucial for the successful deployment of XR over 5G networks and is the focus of the inventive efforts described herein.

[0013] At least some embodiments of the method enable the AN (e.g., the network node serving the WD) to take the reported one or more measured combined QoS parameters for a combination of at least two PDU sets into account when scheduling resources for the PDU sets. For example the at least two PDU sets may be handled in mutual concordance. The handling, i.e., the scheduling, may be performed or triggered at the AN (e.g., the RAN) or the core network (CN) serving the AN, e.g., in a fifth generation system (5GS) for optimal wireless (e.g., optical or radio) resource management (e.g., RRM). For example, embodiments can inform the gNB is not well informed of the one or more inter-dependencies.

[0014] The technique may be embodied by a method for the WD (e.g., a UE) to provide at least one combined QoS parameter for a combination of at least two PDU sets information of multi-modal flows.

[0015] According to an embodiment, the WD (e.g., a UE) reports "multi-modality" information (i.e., the report message), which indicates at least one combined QoS parameter for a combination of at least two PDU sets of multiple application flows (which may be implemented using the at least two PDU sets) to serve the same service. This information (i.e., the report message) may include a recommendation of mapping a group of QoS flow indicators (QFI) (e.g., corresponding to the at least two PDU sets) to a common data radio bearer (DRB). Alternatively or in addition, the report message may be indicative of a set of DRB indexes (e.g., to identify the inter-dependent PDU sets) and / or a set of application flow specific information (such as port numbers and IP addresses) determine the service that uses the at least two PDU sets. The signaling (i.e., the step of sending the report message) may be done by radio resource control (RRC) signaling, e.g., UE assistance information (UAI).

[0016] Herein, "combined QoS parameter" may refer to any one or each of the at least one combined QoS parameter.

[0017] The combined QoS parameter may be indicative of consistency or inconsistency (e.g. a difference or deviation) between QoS parameters of the inter-dependent at least two PDU sets. The inter-dependent at least two PDU sets may also be referred to as the mutually inter-dependent PDU sets or the combined PDU sets or the different PDU sets or briefly as the at least two PDU sets. The at least two inter-dependent PDU sets may serve the same service (e.g., the same application). For example, the same service may generate and / or receive and / or process the inter-dependent at least two PDU sets.

[0018] Herein, "inter-dependent" and "inter-dependency" may briefly be referred to as "dependent" and "dependency", respectively. The (optionally implicit) "inter-" may refer to a relationship between the different PDU sets (i.e., the inter-dependent at least two PDU sets), e.g. as opposed to an intra-dependency of PDUs within any one the PDU sets.

[0019] Since the combined QoS parameter is a measure for and / or relates to the interdependent at least two PDUs in combination, the combined QoS parameter may be referred to as inter-dependent QoS parameter or briefly dependent QoS parameter (D-QoS parameter, or briefly: D-QoS). The at least one combined QoS parameter for one combination of the inter-dependent at least two PDU sets may be collectively referred to as the combined QoS information or briefly the QoS information.

[0020] The combination of the at least two PDU sets may be referred to as the combined at least two PDU sets or briefly as the at least two PDU sets.

[0021] The report message may trigger or enable the AN (e.g., a network node of the AN) to prioritize and / or manage the (e.g. different) quality of service (QoS) requirements of the at least two PDU sets by scheduling, admission control, and / or resource allocation. The allocation of resources may refer to wireless resources (e.g., radio resources) of the uplink, e.g. in the time domain, the frequency domain, the spatial domain or a combination thereof. Alternatively or in addition, the report message may trigger or enable the AN (e.g., a network node of the AN) to discard all PDUs of the at least two PDU sets if the combined QoS parameter does not fulfil a predefined criterion (also referred to as combined QoS criterion). Herein, the terms requirement and criterion may be synonymous and / or interchangeable.

[0022] The at least two PDU sets being mutually inter-dependent may encompass discarding all PDUs of the at least two PDU sets if a PDU of one of the at least two PDU sets is lost (e.g., missing after a PDU packet delay budget) and / or if a PDU set of the at least two PDU sets is lost (e.g., missing or incomplete after a PDU set delay budget, PSDB) and / or if the combined QoS parameter does not fulfil the predefined combined QoS criterion.

[0023] The measurement may be referred to as combined QoS measurement. The combined QoS parameter measured at (e.g., in) the wireless device may be a measure of user experience. Each of the at least one combined QoS parameter may be measured for the interdependent at least two PDU sets in combination. The measured combined QoS parameter (e.g., for the user experience) may be dependent on the interdependency between the PDU sets. Alternatively or in addition, the combined QoS parameter (e.g., for the user experience) may be a function of a QoS parameter of each the at least two PDU sets. For example, the combined QoS parameter may be a minimum of the QoS parameters of the PDU sets.

[0024] Herein, an uplink "towards" the AN (e.g., "towards" the network node serving the WD) may relate to an uplink from the WD and / or may encompass that the WD attempts to transmit the at least two PDU sets. For example, the at least two PDU sets are not necessarily received (e.g., not all or not completely received) at the AN.

[0025] Each of the at least two PDU sets may comprise a plurality of PDUs. Furthermore, the PDUs may be data units (e.g., data packets) of a user plane (UP) PDU layer responsible for PDU session establishment and / or a radio network layer and / or above a transport network layer and / or an application layer. The PDU set may be processed together (e.g., as a whole) in the receiving application layer. The WD may measure the combined QoS parameter by processing the at least two PDU sets in combination.

[0026] Whenever referring to QoS, a corresponding feature and / or step is also disclosed and implementable by replacing QoS for any measure of user experience, e.g. a Quality of Experience (QoE).

[0027] The access network (AN) may be a wireless AN, e.g. a radio access network (RAN). Sending the report message may be referred to as reporting.

[0028] Different PDUs within one of the at least two PDU sets may relate to or comprise the same data type (i.e., the same data flow, which may herein be called traffic flow). Different inter-dependent PDU sets (e.g., different inter-dependent data flows) may form a multi-modal data stream (e.g., multi-modal traffic). Alternatively or in addition, different PDUs within each of the at least two PDU sets may relate to the same data source (e.g., service), e.g. of a multi-modal data stream. The different PDU sets (e.g., in the at least two PDU sets) may relate to different types of data within one multi-modal data stream. The multi-modal data stream may comprise multiple types of data according to the inter-dependent at least two PDU sets, e.g. images, text, audio, video, haptic sensors, etc. The different data types may be multiple modalities of the multi-modal data stream (e.g., multi-modal traffic).

[0029] The inter-dependent at least two PDU sets may have a semantic and / or causal relationship with each other, and / or provide complementary or contradictory information and / or are correlated and / or functionally dependent on one another. The functional dependency may comprise sensor fusion.

[0030] For example, a video stream may be considered as a multi-modal data stream that contains both visual data and audio data, which are related by temporal synchronization and / or the content of a scene. Another example may be a multimodal dataset for autonomous driving (e.g., including full-surround observations), which may comprise one or more camera images, one or more Light Detecting and Ranging (LiDAR) point clouds, satellite-based radio navigation system (e.g., GPS) coordinates, and / or vehicle states. These different types of data (e.g., different data streams) may be carried by respectively different PDU sets, which are interdependent, e.g. by a spatial alignment and / or a dynamic environment.

[0031] Alternatively or in addition, at least one of the WD and an application server, which may exchange the PDU sets through the AN, may provide or use an extended Reality (XR) service and / or a multi-modal machine learning (ML) model based on the inter-dependent at least two PDU sets. The service of the multimodal ML model may encompass a training phase of the multi-modal ML model and / or an inference phase of the multi-modal ML model. Alternatively or in addition, the service of the multi-modal ML model may encompass applications of deep multimodal learning and / or any (sub-)combination of computer vision, natural language processing, speech recognition, emotion recognition, humancomputer interaction.

[0032] Alternatively or in addition, the inter-dependency may relate to a handling (e.g., processing or rendering or analyzing) of the at least two PDU sets. The interdependency may imply a need for synchronization, coordination, and / or concurrent processing of these heterogeneous data types to ensure seamless communication and / or service delivery. Alternatively or in addition, data in the different PDU sets may be encoded according to different protocols. For example, video may be sent using a protocol that support streaming, such as Real-Time Transport Protocol (RTP), while sensor data may utilize a more lightweight protocol, e.g. MQTT or CoAP. Any one of the examples of the handling of the at least two PDUs may be implemented by edge computing (e.g., at the AN).

[0033] The different PDU sets, which are inter-dependent, may comprise different data types. Alternatively or in addition, the different PDU sets, which are interdependent, may originate from different physical sources and / or may be targeted to different physical outlets (e.g., displays and loudspeakers). Alternatively or in addition, the different PDU sets, which are inter-dependent, may originate from and / or be addressed to same network address (e.g., internet protocol, IP, address or medium access control, MAC, address). For example, the multi-modal data streams may originate from various sensors and devices, each capturing a different aspect of information. For example, a video stream may require high bandwidth and low latency to fulfil the predefined criterion (e.g., a required QoS parameter value, i.e., a threshold value), while sensor data might be small-sized packets that are sent at regular intervals or upon certain events and / or may require low jitter or low latency (e.g., for a haptic feedback).

[0034] For example, the AN may control network slicing in accordance the reported interdependency. With the advent of fifth generation (5G) networks or beyond 5G, network slicing may allow for the creation of multiple virtual networks on the same physical network infrastructure. Each slice may be tailored to meet the specific needs of different multi-modal data streams, ensuring the right balance of latency, throughput, and reliability. The AN may allocate the at least two PDU sets to the same network slice.

[0035] The measuring of the combined QoS parameter for the combination of the at least two PDU sets, which are mutually inter-dependent, may mean: measuring at least the combined QoS parameter for a combination of at least two data flows (e.g., QoS flows), which are inter-dependent. More specifically, the measuring of the combined QoS parameter for the combination of the at least two PDU sets, which are mutually inter-dependent, may mean measuring the combined QoS parameter for the combination of one or more PDU sets in a first data flow (e.g., a first QoS flow) and one or more PDU sets in a second data flow (e.g., a second QoS flow).

[0036] Alternatively or in addition, the inter-dependent at least two PDU sets may relate to simultaneously transmitted PDU sets or to PDU sets in different (e.g., coexisting) data flows (e.g., QoS flows) and / or to different sequences of PDU sets and / or not to subsequent PDU sets on the same data flow (e.g., the same QoS flow). Referring to the measured or reported combined QoS parameter may refer to a measured value or a reported value, respectively, of combined QoS parameter.

[0037] The at least two PDU sets in the uplink towards the AN may be sent towards (e.g., to) a first network node (e.g., a serving network node of the WD) of the AN.

[0038] Alternatively or in addition, the report message may be sent to the AN by sending the report message to a second network node (e.g., a serving network node of the WD) of the AN. The first and second nodes may be different or identical network nodes.

[0039] Herein, "combined QoS parameter" may refer to any one or each of the at least one combined QoS parameter.

[0040] The combined QoS parameter may be indicative of consistency or inconsistency (e.g. a difference or deviation) between QoS parameters of the inter-dependent at least two PDU sets. The inter-dependent at least two PDU sets may also be referred to as the mutually inter-dependent PDU sets or the combined PDU sets or the different PDU sets or briefly as the at least two PDU sets. The at least two inter-dependent PDU sets may serve the same service (e.g., the same application). For example, the same service may generate and / or receive and / or process the inter-dependent at least two PDU sets.

[0041] Herein, "inter-dependent" and "inter-dependency" may briefly be referred to as "dependent" and "dependency", respectively. The (optionally implicit) "inter-" may refer to a relationship between the different PDU sets (i.e., the interdependent at least two PDU sets), e.g. as opposed to an intra-dependency of PDUs within any one the PDU sets.

[0042] Since the combined QoS parameter is a measure for and / or relates to the interdependent at least two PDUs in combination, the combined QoS parameter may be referred to as inter-dependent QoS parameter or briefly dependent QoS parameter (D-QoS parameter, or briefly: D-QoS). The at least one combined QoS parameter for one combination of the inter-dependent at least two PDU sets may be collectively referred to as the combined QoS information or briefly the QoS information. The combination of the at least two PDU sets may be referred to as the combined at least two PDU sets or briefly as the at least two PDU sets.

[0043] The report message may trigger or enable the AN (e.g., a network node of the AN) to prioritize and / or manage the (e.g. different) quality of service (QoS) requirements of the at least two PDU sets by scheduling, admission control, and / or resource allocation. The allocation of resources may refer to wireless resources (e.g., radio resources) of the uplink, e.g. in the time domain, the frequency domain, the spatial domain or a combination thereof. Alternatively or in addition, the report message may trigger or enable the AN (e.g., a network node of the AN) to discard all PDUs of the at least two PDU sets if the combined QoS parameter does not fulfil a predefined criterion (also referred to as combined QoS criterion). Herein, the terms requirement and criterion may be synonymous and / or interchangeable.

[0044] The at least two PDU sets being mutually inter-dependent may encompass discarding all PDUs of the at least two PDU sets if a PDU of one of the at least two PDU sets is lost (e.g., missing after a PDU packet delay budget) and / or if a PDU set of the at least two PDU sets is lost (e.g., missing or incomplete after a PDU set delay budget, PSDB) and / or if the combined QoS parameter does not fulfil the predefined combined QoS criterion.

[0045] The measurement may be referred to as combined QoS measurement. The combined QoS parameter measured at (e.g., in) the wireless device may be a measure of user experience.

[0046] Each of the at least one combined QoS parameter may be measured for the interdependent at least two PDU sets in combination. The measured combined QoS parameter (e.g., for the user experience) may be dependent on the interdependency between the PDU sets. Alternatively or in addition, the combined QoS parameter (e.g., for the user experience) may be a function of a QoS parameter of each the at least two PDU sets. For example, the combined QoS parameter may be a minimum of the QoS parameters of the PDU sets.

[0047] Herein, an uplink "towards" the AN (e.g., "towards" the network node serving the WD) may relate to an uplink from the WD and / or may encompass that the WD attempts to transmit the at least two PDU sets. For example, the at least two PDU sets are not necessarily received (e.g., not all or not completely received) at the AN.

[0048] Each of the at least two PDU sets may comprise a plurality of PDUs. Furthermore, the PDUs may be data units (e.g., data packets) of a user plane (UP) PDU layer responsible for PDU session establishment and / or a radio network layer and / or above a transport network layer and / or an application layer. The PDU set may be processed together (e.g., as a whole) in the receiving application layer. The WD may measure the combined QoS parameter by processing the at least two PDU sets in combination.

[0049] Whenever referring to QoS, a corresponding feature and / or step is also disclosed and implementable by replacing QoS for any measure of user experience, e.g. a Quality of Experience (QoE).

[0050] The access network (AN) may be a wireless AN, e.g. a radio access network (RAN). Sending the report message may be referred to as reporting.

[0051] Different PDUs within one of the at least two PDU sets may relate to or comprise the same data type (i.e., the same data flow, which may herein be called traffic flow). Different inter-dependent PDU sets (e.g., different inter-dependent data flows) may form a multi-modal data stream (e.g., multi-modal traffic).

[0052] Alternatively or in addition, different PDUs within each of the at least two PDU sets may relate to the same data source (e.g., service), e.g. of a multi-modal data stream. The different PDU sets (e.g., in the at least two PDU sets) may relate to different types of data within one multi-modal data stream. The multi-modal data stream may comprise multiple types of data according to the interdependent at least two PDU sets, e.g. images, text, audio, video, haptic sensors, etc. The different data types may be multiple modalities of the multi-modal data stream (e.g., multi-modal traffic).

[0053] The inter-dependent at least two PDU sets may have a semantic and / or causal relationship with each other, and / or provide complementary or contradictory information and / or are correlated and / or functionally dependent on one another. The functional dependency may comprise sensor fusion.

[0054] For example, a video stream may be considered as a multi-modal data stream that contains both visual data and audio data, which are related by temporal synchronization and / or the content of a scene. Another example may be a multimodal dataset for autonomous driving (e.g., including full-surround observations), which may comprise one or more camera images, one or more Light Detecting and Ranging (LiDAR) point clouds, satellite-based radio navigation system (e.g., GPS) coordinates, and / or vehicle states. These different types of data (e.g., different data streams) may be carried by respectively different PDU sets, which are inter-dependent, e.g. by a spatial alignment and / or a dynamic environment.

[0055] Alternatively or in addition, at least one of the WD and an application server, which may exchange the PDU sets through the AN, may provide or use an extended Reality (XR) service and / or a multi-modal machine learning (ML) model based on the inter-dependent at least two PDU sets. The service of the multimodal ML model may encompass a training phase of the multi-modal ML model and / or an inference phase of the multi-modal ML model. Alternatively or in addition, the service of the multi-modal ML model may encompass applications of deep multimodal learning and / or any (sub-)combination of computer vision, natural language processing, speech recognition, emotion recognition, humancomputer interaction.

[0056] Alternatively or in addition, the inter-dependency may relate to a handling (e.g., processing or rendering or analyzing) of the at least two PDU sets. The interdependency may imply a need for synchronization, coordination, and / or concurrent processing of these heterogeneous data types to ensure seamless communication and / or service delivery. Alternatively or in addition, data in the different PDU sets may be encoded according to different protocols. For example, video may be sent using a protocol that support streaming, such as Real-Time Transport Protocol (RTP), while sensor data may utilize a more lightweight protocol, e.g. MQTT or CoAP. Any one of the examples of the handling of the at least two PDUs may be implemented by edge computing (e.g., at the AN).

[0057] The different PDU sets, which are inter-dependent, may comprise different data types. Alternatively or in addition, the different PDU sets, which are interdependent, may originate from different physical sources and / or may be targeted to different physical outlets (e.g., displays and loudspeakers). Alternatively or in addition, the different PDU sets, which are inter-dependent, may originate from and / or be addressed to same network address (e.g., internet protocol, IP, address or medium access control, MAC, address). For example, the multi-modal data streams may originate from various sensors and devices, each capturing a different aspect of information. For example, a video stream may require high bandwidth and low latency to fulfil the predefined criterion (e.g., a required QoS parameter value, i.e., a threshold value), while sensor data might be small-sized packets that are sent at regular intervals or upon certain events and / or may require low jitter or low latency (e.g., for a haptic feedback).

[0058] For example, the AN may control network slicing in accordance the reported inter-dependency. With the advent of fifth generation (5G) networks or beyond 5G, network slicing may allow for the creation of multiple virtual networks on the same physical network infrastructure. Each slice may be tailored to meet the specific needs of different multi-modal data streams, ensuring the right balance of latency, throughput, and reliability. The AN may allocate the at least two PDU sets to the same network slice.

[0059] The measuring of the combined QoS parameter for the combination of the at least two PDU sets, which are mutually inter-dependent, may mean: measuring at least the combined QoS parameter for a combination of at least two data flows (e.g., QoS flows), which are inter-dependent. More specifically, the measuring of the combined QoS parameter for the combination of the at least two PDU sets, which are mutually inter-dependent, may mean measuring the combined QoS parameter for the combination of one or more PDU sets in a first data flow (e.g., a first QoS flow) and one or more PDU sets in a second data flow (e.g., a second QoS flow).

[0060] Alternatively or in addition, the inter-dependent at least two PDU sets may relate to simultaneously transmitted PDU sets or to PDU sets in different (e.g., coexisting) data flows (e.g., QoS flows) and / or to different sequences of PDU sets and / or not to subsequent PDU sets on the same data flow (e.g., the same QoS flow).

[0061] Referring to the measured or reported combined QoS parameter may refer to a measured value or a reported value, respectively, of combined QoS parameter.

[0062] The at least two PDU sets in the uplink towards the AN may be sent towards (e.g., to) a first network node (e.g., a serving network node of the WD) of the AN. Alternatively or in addition, the report message may be sent to the AN by sending the report message to a second network node (e.g., a serving network node of the WD) of the AN. The first and second nodes may be different or identical network nodes.

[0063] Each of the at least two PDU sets (e.g., according to the first method aspect) may correspond to a distinctive sensor or data source or data type or a distinctive QoS flow, optionally a distinctive flow identifier within a QoS flow. Alternatively or in addition, each of the at least two PDU sets may correspond to a distinctive data radio bearer (DRBs), optionally a distinctive flow identifier within a DRB.

[0064] Alternatively or in addition, the combination of the at least two PDU sets may correspond to and / or originates from one service.

[0065] The different PDU sets of the inter-dependent at least two PDU sets may be associated with different QoS flows. Optionally, each QoS flow may (e.g., uniquely for the WD and / or the AN) be associated with and / or correspond to a QoS flow indicator (QFI).

[0066] The service may be an application. The service may comprise a server application (e.g., linked to the WD through the AN) and a client application performed by the WD. In a variant of any embodiment, the inter-dependency of the at least two PDU sets may be defined by the same service causing or using the at least two PDU sets.

[0067] The different PDU sets may be associated with different PDU set QoS requirements (also: PDU set QoS levels), e.g. even though the different PDU sets may serve the same service. Therefore, a user experience (e.g., at the WD) may be strongly related to an inter-dependent scheduling (e.g. at the AN, e.g. the network node of the AN, which is serving the WD) that is controlled by the interdependency (e.g., synchronization) and / or the measured combined QoS parameter and / or not by applying the same PDU set QoS level to each of the at least two PDU sets.

[0068] The different PDU sets of the inter-dependent at least two PDU sets may be associated with different QoS flows and / or different Internet Protocol (IP) flows.

[0069] In a variant of any embodiment, the inter-dependency of the at least two PDU sets may be defined by the IP flow. The at least two PDU sets may belong to the same IP flow. The IP flow may comprise all PDUs with the same pair of source socket address and / or target socket address. A socket address may comprise a triad of transport protocol, IP address, and port number.

[0070] At least one or each of the following four sentences may apply: Each PDU set may be associated with one QoS flow. Each QoS flow may comprise one or more PDU sets. In a 5G system (5GS), each QoS flow may be uniquely identified by a QFI. Each QoS flow may comprise one or more IP flows. Optionally, each IP flow may be associated with one QoS flows.

[0071] The at least two PDU sets (e.g., according to the first method aspect) may belong to different data flows and / or may correspond to at least two of the following data flows a video flow; an audio flow; one or more environmental information flow; a pose flow; a gesture flow; and a haptic flow.

[0072] The one or more QoS flows may also be referred to as multi-modal (e.g., multimodal communication) as they are corresponding (e.g., serving) the same service. For example, a video conference may be a multi-modal communication as it comprises at least two data flows (e.g., audio flow and video flow) serving the same service (e.g., video conference).

[0073] The inter-dependency (e.g., according to the first method aspect) of the at least two PDU sets may be obtained at the WD.

[0074] It may be up to the WD to determine (as an example of the obtainment) which PDU sets are inter-dependent and / or for which at least two PDU sets the (at least one) combined QoS parameter is to be measured. For example, the WD may determine based on a client application executed at the WD.

[0075] The inter-dependency of the at least two PDU sets (e.g., according to the first method aspect) may be received, optionally indicated in a configuration message, from at least one of the AN; a network node of the AN, optionally the network node serving the WD; and a core network (CN), serving the AN, optionally a user plane function (UPF) of the CN.

[0076] The combined QoS parameter (e.g., according to the first method aspect) may relate to the at least two PDU sets in combination. Alternatively or in addition, the combined QoS parameter may not be indicative of individual PDU sets of the at least two PDU sets. Alternatively or in addition, the combined QoS parameter may not be indicative of individual PDUs in the at least two PDU sets.

[0077] The combined QoS parameter may relate to the QoS for the at least two PDU sets in combination, e.g. may be not indicative of individual PDU sets (which may be measured in terms of PDU set QoS parameters) in the at least two PDU sets and not indicative of individual PDUs (which may be measured in terms of PDU QoS parameters) in any of the PDU sets.

[0078] The at least two PDU sets optionally the at least two of the QoS flows or DRBs (e.g., according to the first method aspect) may be inter-dependent because of at least one of a synchronization requirement between the at least two PDU sets, optionally between the at least two of the QoS flows or DRBs; a common internet protocol (IP) address and / or a common port number and / or a common medium access control (MAC) address of the at least two PDU sets, optionally of the at least two of the QoS flows or DRBs; a correlation between the at least two PDU sets, optionally between the at least two of the QoS flows or DRBs; and the service corresponding to or associated with the at least two PDU sets, optionally corresponding to or associated with the at least two of the QoS flows or DRBs.

[0079] The inter-dependent PDU sets may be or may comprise inter-dependent data flows of a multi-modal stream, for example, two synchronized data flows. For instance in a video conference, the audio flow and the video flow may need to be synchronized to fulfill a requirement for the quality of user experience.

[0080] Alternatively or in addition, the inter-dependent PDU sets (e.g., data flows) may originate from the same host source and / or may be targeted to the same destination host. Alternatively or in addition, the inter-dependent PDU sets (e.g., data flows) may be correlated across their different data types. The correlation may be measured in terms of a relative entropy or mutual information between the at least two PDU sets, e.g. between the at least two of the data flows.

[0081] The inter-dependency may be obtained (e.g., at the WD) by determining (e.g., measuring) if any of the afore-mentioned quantities or addresses or services for different PDU sets (e.g., in the uplink or to be transmitted in the uplink of the WD) fulfils an inter-dependency criterion. For example, the inter-dependency criterion may require the same service (e.g., an equal service application or process identifier) for the at least two PDU sets or a correlation that is greater than a predefined correlation threshold value. The report message (e.g., according to the first method aspect) may be indicative of a change and / or statistical information of the measured at least one combined QoS parameter for the at least two PDU sets. Alternatively or in addition, the report message may be indicative of at least one of an absolute or relative decrease per time period or since the last report message, an absolute or relative increase per time period or since the last report message, a minimum, a maximum, a median, an average, a variance, and a probability distribution of the measured at least one combined QoS parameter for the at least two PDU sets or a time sequence of thereof.

[0082] The "decrease" may be a decline in the combined QoS parameter. The "increase" may be an improvement of the combined QoS parameter.

[0083] The last report message may refer to the last indication of the combined QoS parameter for the at least two PDU sets.

[0084] The change (e.g., the increase or decrease) and / or the statistical information may relate to the change or difference of a PDU set QoS parameter of one PDU set of the at least two PDU sets relative to a PDU set QoS parameter of another PDU set of the at least two PDU sets. Alternatively or in addition, the change (e.g., the increase or decrease) and / or the statistical information may relate to the change or difference of a PDU QoS parameter of a PDU in one PDU set of the at least two PDU sets relative to a PDU QoS parameter of a PDU in another PDU set of the at least two PDU sets. For example, the at least one combined QoS parameter may comprise a delay. The delay may be defined as a relative timing offset between the at least two PDU sets. Alternatively or in addition, the delay may be a deviation from a synchronization between the at least two PDU sets. For example, the synchronization may correspond to a (e.g., equivalent or linear) relation between sequence numbers of the PDUs in the different PDU sets. The delay may correspond to a deviation from the relation in terms of the sequence numbers, e.g. for available PDUs of the different PDU sets. The available PDUs may be available for transmission (i.e., to be sent) from the WD towards the AN (e.g., towards the network node). Alternatively or in addition, the synchronization may be measured (e.g., at the WD) based on a timestamp in each of the PDUs in the different PDU sets. The delay may correspond to a deviation between (e.g., a spread of) the timestamps of PDUs available for UL transmission at WD. The combined QoS parameter may be a combination on the level of PDU sets.

[0085] The combined QoS parameter (e.g., according to the first method aspect) may be a function of and / or may comprise at least two PDU set QoS parameters for each or at least two of the inter-dependent at least two PDU sets. Alternatively or in addition, the combined QoS parameter may comprise one or more differences between two or more PDU set QoS parameters, each of the two or more PDU set QoS parameters relating to a different one of the inter-dependent at least two PDU sets. Alternatively or in addition, the combined QoS parameter may comprise a list of PDU set QoS parameters, each of the PDU set QoS parameters in the list relating to a different one of the inter-dependent at least two PDU sets.

[0086] The PDU set QoS parameters (e.g., according to the first method aspect), optionally for each of the inter-dependent at least two PDU sets, may comprise at least one of a PDU set error rate (PSER) of the respective PDU set among the inter-dependent at least two PDU sets; a PDU set delay budget (PSDB) of the respective PDU set among the inter-dependent at least two PDU sets; a PDU set integrated handling information ( PSI H I ) of the respective PDU set among the inter-dependent at least two PDU sets; a latency of the respective PDU set among the inter-dependent at least two PDU sets; a jitter of respective PDU set among the inter-dependent at least two PDU sets; a PDU set loss rate of the respective PDU set among the inter-dependent at least two PDU sets; a bit rate of respective PDU set among the inter-dependent at least two PDU sets; an indicator of fulfilment of a guaranteed flow bit rate (GFBR) of the respective PDU set among the inter-dependent at least two PDU sets; an indicator of fulfilment of a maximum flow bit rate (MFBR) of the respective PDU set among the interdependent at least two PDU sets; a PDU set queued time of the respective PDU set among the inter-dependent at least two PDU sets; a PDU set importance (PSI) of the respective PDU set for the inter-dependent at least two PDU sets; a PDU set dropping ration of the respective PDU set among the inter-dependent at least two PDU sets; and a PDU set priority level of the respective PDU set among the inter-dependent at least two PDU sets.

[0087] The PSI and / or PSIHI may be indicative of information related to one or more QoS parameters and their inter-relation. For example, the measured PSDB may comprise a delay of the respective PDU set (e.g., a maximum time or initial PSDB minus the delay). The measured PSDB may be positive (e.g., representing a remaining PSDB) or negative (e.g., indicating that the delay budget has been exceeded).

[0088] Each of the PDU set QoS parameters, e.g. any one of the above-listed examples of the PDU set QoS parameters, may be measured (e.g., in the measurement at the WD) for one or more PDU sets (e.g., as a statistical measure) in one of (e.g., coexisting) inter-dependent data flows (e.g., inter-dependent QoS flows) and / or in inter-dependent sequences of PDU sets and / or not for subsequent PDU sets in the same data flow (e.g., the same QoS flow). In other words, the interdependency may be defined for inter-dependent data flows (e.g., interdependent QoS flows) or the at least two PDU sets may be mutually interdependent because they are on inter-dependent data flows (e.g., interdependent QoS flows).

[0089] The combined QoS parameter (e.g., according to the first method aspect) may comprise at least one of a combined PDU set error rate (PSER) of the interdependent at least two PDU sets; a combined PDU set delay budget (PSDB) of the inter-dependent at least two PDU sets; a combined PDU set integrated handling information (PSI H I ) of the inter-dependent at least two PDU sets; a combined latency of the inter-dependent at least two PDU sets; a combined jitter of the inter-dependent at least two PDU sets; a combined PDU set loss rate of the respective PDU set among the inter-dependent at least two PDU sets; a combined bit rate of the inter-dependent at least two PDU sets; an indicator of combined fulfilment of a guaranteed flow bit rate (GFBR) of the inter-dependent at least two PDU sets; an indicator of combined fulfilment of a maximum flow bit rate (MFBR) of the inter-dependent at least two PDU sets; a combined PDU set queued time of the inter-dependent at least two PDU sets; a combined PDU set importance (PSI) of the inter-dependent at least two PDU sets; a combined PDU set dropping ration of the inter-dependent at least two PDU sets; and a combined PDU set priority level of the inter-dependent at least two PDU sets.

[0090] Since the above combined quantities may relate to inter-dependent PDU sets, they may also be referred to as dependent quantities (D-PDU set error rate or D- PSER, etc.) The at least two PDU sets (e.g., according to the first method aspect) may be received by an application layer of the WD and / or received from an application layer, optionally an application server, through a network node of the AN. Alternatively or in addition, the at least two PDU sets may be sent from an application layer of the WD and / or sent to an application layer, optionally an application server, through a network node of the AN.

[0091] The method (e.g., according to the first method aspect) may further comprise or initiate determining whether the measured at least one combined QoS parameter for the combination of the at least two PDU sets fulfils a predefined criterion, optionally wherein the report message may be indicative of whether or not the predefined criterion is fulfilled. Alternatively or in addition, the sending of the report message may be triggered if the predefined criterion is not fulfilled.

[0092] A predefined criterion (i.e., the combined QoS criterion) may specify a minimum quality of (e.g., user) experience (QoE) and / or QoS level for the combination of the inter-dependent at least two PDU sets and / or in terms of the (e.g., measured and / or reported) at least one combined QoS parameter. For example, the predefined criterion may comprise a maximum delay (e.g., a maximum relative timing offset) and / or the minimum guaranteed data bit rate.

[0093] The predefined criterion may be received (e.g., in a configuration message) from the AN, e.g., from a network node of the AN (e.g., from the first network node and / or the second network node).

[0094] The method (e.g., according to the first method aspect) may further comprise or initiate sending a capability message to the AN (510), optionally to a network node of the AN. Alternatively or in addition, the capability message may be indicative of at least one of a capability of the WD to measure the at least one combined QoS parameter for the combined at least two PDU sets in the uplink towards the AN; a capability of the WD to obtain the at least one interdependency between the at least two combined PDU sets; a capability of the WD to report a result of the measurement of the at least one combined QoS parameter for the combined at least two PDU sets to the AN; an interdependency criterion for determining the inter-dependency of the at least two PDU sets; one or more PDU set QoS parameters of the at least two PDU sets in the uplink towards the AN, which the WD is capable of measuring and / or sending; one or more combined QoS parameters of the combined at least two PDU sets in the uplink towards the AN, which the WD is capable of measuring and / or sending; a physical layer information of the WD; and a feature set indicator, optionally comprising radio protocol information.

[0095] The combined QoS parameter for the at least two the PDU sets may comprise the delay (e.g., the relative timing offset) (e.g. of all PDUs or all PDU sets or a maximum delay of the at least two PDU sets). The combined QoS parameter and / or the inter-dependency criterion for the at least two the PDU sets (e.g., for determining the inter-dependency between one or more PDU sets in a first data flow and one or more PDU sets in a second data flow) and / or the mutual information between the at least two the PDU sets.

[0096] The method (e.g., according to the first method aspect) may further comprise or initiate receiving a configuration message for the measuring or the sending from the AN, optionally from a network node of the AN, and / or from a core network serving the AN. Alternatively or in addition, the configuration message may be indicative of at least one of the inter-dependency between the at least two PDU sets; the inter-dependency criterion for determining the inter-dependency between the at least two PDU sets; the inter-dependent at least two PDU sets; one or more PDU set QoS parameters to be measured for the at least two PDU sets and / or to be combined for the measuring of the at least one combined QoS parameter; the at least one combined QoS parameter to be measured (306) for the at least two PDU sets; the predefined criterion, optionally a threshold value for the combined QoS parameter or a threshold value for the delay; an Internet Protocol flow (IP flow) associated with the at least two PDU sets; a QoS flow, optionally a QoS flow identifier (QFIs) associated with the at least two PDU sets; a data radio bearer (DRB), associated with the at least two PDU sets; PDU set identifiers of the at least two PDU sets; a cross-PDU set importance (cross-PSI) associated with the at least two PDU sets and / or indicative of an importance level of the inter-dependency; a set of QoS flow identifiers (QFIs) associated with the at least two PDU sets; a set of DRB indexes associated with the at least two PDU sets; an obtaining mode for the obtaining of the inter-dependency in the WD; a measuring mode of the measurement of at least one QoS parameter of the at least two PDU sets; a reporting mode for the sending of the report message; an obtainment window for the obtaining of the inter-dependency at the WD and / or for the measuring of the at least one combined QoS parameter of the inter-dependent at least two PDU sets at the WD; a periodicity for the measuring the at least one QoS parameter and / or the obtaining of the inter-dependency and / or the sending of the report message; and a deadline for the sending of the report message.

[0097] The at least two QoS flows (e.g., indicated by at least two QFIs) may be interdependent (e.g., as defined herein). Alternatively or in addition, the at least two DRBs (e.g., as indicated by the DRB indices) may be inter-dependent (e.g., as defined herein).

[0098] The configuration message may be received from a network node of the AN, optionally from the network node in communication with the WD or the first and / or second network node.

[0099] The configuration message from the AN may be based on and / or received responsive to the capability message sent to the AN.

[0100] The inter-dependency criterion may comprise (e.g., a set of) application flow specific information and / or one or more port numbers and / or IP addresses for determining the inter-dependent at least two PDU sets (e.g., for determining the inter-dependent QoS flows or DRBs). Alternatively or in addition, the interdependency criterion for determining the at least two PDU sets may be comprise matching information for matching the at least two PDU sets that are interdependent and / or a set of application flow specific information associated with all of the at least two PDU sets that are inter-dependent. Alternatively or in addition, the inter-dependency criterion may comprise a pattern for packet inspection (e.g., IP packet inspection or PDU inspection) to determine (e.g., at the WD) the at least two PDUs that are inter-dependent (e.g., that belong to the same service).

[0101] The method (e.g., according to the first method aspect), wherein a measuring mode for the measuring of the at least one combined QoS parameter of the at least two PDU sets and / or an obtaining mode for obtaining the inter-dependency of the at least two PDU sets and / or a reporting mode for the sending of the report message may comprise at least one of a periodic measuring, optionally a periodic determining, and / or a periodic obtaining and / or a periodic report message; an aperiodic measuring, optionally an aperiodic determining, and / or an aperiodic obtaining and / or an aperiodic report message; an event-triggered measuring, optionally an event-triggered determining, and / or an event-triggered obtaining, and / or an event-triggered report message; and on-demand measuring, optionally on-demand determining, and / or on-demand obtaining and / or an on- demand report message.

[0102] The event-triggered mode (e.g., the event-triggered measuring, optionally determining, and / or obtaining and / or reporting) may encompass the fulfilment or the non-fulfillment of the predefined criterion as the triggering event. The predefined criterion may be received from the AN, e.g., indicated in a configuration message.

[0103] Alternatively or in addition, the on-demand mode may comprise receiving a request message, e.g., receiving a request message from the AN (e.g., from the first or second network node).

[0104] The predefined criterion (e.g., according to the first method aspect) may comprise a threshold value for a threshold of the at least one combined QoS parameter, and / or a threshold value for a threshold of a variance of the at least one combined QoS parameter.

[0105] The report message (e.g., according to the first method aspect) may use or comprise at least one of Radio Resource control (RRC) signaling; UE Assistance Information (UAI); a Packet Data Convergence Protocol (PDCP) control PDU; and a Service Data Adaptation Protocol (SDAP) control PDU. Alternatively or in addition, the sending may comprise sending the report message in a control plane (CP) data unit using an RRC layer, a PDCP layer and / or an SDAP layer.

[0106] A layer 2 of a protocol stack for the wireless (e.g., radio) communication between the wireless device and the AN (e.g., for fifth generation new radio, 5G NR) may be split in sublayers including at least one of SDAP, PDCP, radio link control (RLC) and medium access control (MAC). In other words sending the report message may use the second layer or the RRC layer (which may be referred to as the third layer or network layer or a "higher" layer) of the protocol stack.

[0107] The method (e.g., according to the first method aspect), wherein all PDUs in one of the at least two PDU sets may be sent on the same QoS flow or with the same QoS level or on the same DRB or with the same QFI, optionally prior to the sending of the report message. Alternatively or in addition, PDUs of different ones of the at least two PDU sets are sent on different QoS flows or with different QoS levels or on different DRBs or with different QFIs, optionally prior to the sending of the report message. Alternatively or in addition, the report message may be indicative of, or includes a request for, mapping the at least two PDU sets to the same DRB. Alternatively or in addition, the report message may be indicative of, or may include a request for, mapping different QoS flows, optionally different QFIs, of the at least two PDU sets to the same DRB. Alternatively or in addition, all PDUs of the at least two PDU sets may be sent on the same DRB, optionally responsive to the sending of the report message.

[0108] The report message (e.g., according to the first method aspect) may be sent to a network node of the AN, optionally to a network node serving the WD.

[0109] The method (e.g., according to the first method aspect) may further comprise or initiate sending to the AN, optionally to the serving network node, a request message indicative of, or including a request for, mapping the at least two PDU sets to the same DRB and / or indicative of, or including a request for, mapping different QoS flows, optionally different QFIs, of the at least two PDU sets to the same DRB. Alternatively or in addition, sending to the AN, optionally to the serving network node, a confirmation message, optionally an RRC- Reconfiguration-Complete message indicative of adapting a reconfiguration, optionally confirming an adaptation to a changed mapping of the at least two PDU sets to the same DRB and / or mapping different QoS flows, optionally different QFIs, of the at least two PDU sets to the same DRB and / or in response to the receiving of the configuration message.

[0110] The report message and / or the request message and / or the RRC- Reconfiguration-Complete message may be indicative of adapting (or adopting) a reconfiguration, e.g. for scheduling resources in the uplink of the WD.

[0111] As to a second method aspect a method performed by a network node of an access network (AN) is provided. The method comprises or initiates receiving a report message from a WD wirelessly connected to the AN. The report message is indicative of at least one combined QoS parameter for a combination of at least two PDU sets measured at the WD in an uplink towards the AN. The at least two PDU sets are mutually inter-dependent. The method further comprises or initiates scheduling resources for the uplink of the WD based on the received report message. The second method aspect may further comprise any feature and / or any step disclosed in the context of the first method aspect, or a feature and / or step corresponding thereto, e.g., a receiver counterpart to a transmitter feature or step.

[0112] Embodiments of any one of the first and second method aspects can enhance the management of Quality of Service (QoS) for multi-modal (e.g., uplink) communication in wireless networks.

[0113] Embodiments of the method enable a wireless device (WD) to obtain (e.g., measure) a relationship (e.g., inter-dependency) between Packet Data Unit (PDU) sets (e.g., in the uplink direction towards the access network, AN) and subsequently send a report message to the AN indicating the results of this obtaining step (e.g., measurement or observation or packet inspection).

[0114] When the WD (e.g., a UE) reports the at least one measured QoS parameters of the at least two PDU sets, the AN (e.g., the gNB) may use this information to optimize network performance or network resources. For example, the network node may determine, or the report message may be indicative of, whether the predefined criterion (e.g., a requirement) for the at least one combined QoS parameter is fulfilled. Optionally, if the predefined criterion is not fulfilled, the network node may increase (e.g., wireless communication) resources allocated to the WD in the scheduling step (e.g., for at least one of the at least two PDU sets). Alternatively or in addition, if the predefined criterion is not fulfilled, the network node may discard all (e.g., PDUs) of the at least two PDU sets.

[0115] Embodiments can improve scheduling decisions at the AN. For example, with up- to-date inter-dependency and / or an up-to-date value for the combined QoS parameter, the AN (e.g., the first and / or second network node, preferably a gNB) can make better-informed scheduling decisions, e.g., map one or more DRB to the one or more QoS flows of the at least two PDU sets and / or balance prioritizing traffic of the mutually dependent at least two PDU sets that are sensitive to delay or errors and / or can manage congestion more effectively.

[0116] The method may be performed by a network node of the AN, e.g., the network node serving the WD or the fore-mentioned first and / or second network node. Alternatively or in addition, the method may be performed by a gNodeB (gNB) (e.g., a base station in a 5G network as the AN), which wirelessly interfaces with the WD (e.g., a user equipment (U E)) and which interfaces (e.g., in a wired manner or wirelessly) with a core network (e.g., a 5G core network, 5GC).

[0117] By scheduling resources based on the received report message, embodiments of the AN (e.g., gNB) can leverage the at least two combined PDU sets reported by the WD (e.g., UE) to optimize a performance of the AN, and / or ensuring that user experiences are consistent with the QoS profiles defined for various services. This can be critical in 5G ANs, wherein a wide range of services with diverse QoS requirements must be supported simultaneously.

[0118] The scheduling may comprise scheduling resources for at least two different data flows (e.g., QoS flows) that are inter-dependent (e.g., as defined herein, inter alia for the at least two PDU sets) in the uplink of the WD. The at least two PDU sets may be associated with and / or sent on the at least two data flows, respectively.

[0119] The scheduling may comprise configuring the WD with radio resources for the uplink. Alternatively or in addition, the scheduling may comprise setting one or more AN parameters related to the WD and / or the at least two PDU sets, e.g. at least one of a QoS parameters, and the predefined criterion for at least one QoS parameter. Alternatively or in addition, upon reception of the report message, the AN may use the information to configure (e.g., reconfigure) enhanced scheduling mechanism, such as a configured grant (CG), discontinuous reception (DRX), and pre-scheduling or semi-persistent scheduling (SPS).

[0120] The receiving of the report message may comprise analyzing the report. For example, the AN (e.g., the gNB) may process the received one or more report messages to determine the inter-dependency and / or a current QoS performance (e.g., a value of the at least one combined QoS parameter) for the at least two PDU sets and / or for each WD (e.g., UE). This may involve analyzing the at least one combined QoS parameter of the at least two PDU sets and / or PDU set QoS parameters of the individual PDU sets in the at least two PDU sets according to at least one QoS parameter (e.g., related to error rate, delay, and throughput according to a service).

[0121] Herein, a combined QoS requirement of the at least two PDU sets (e.g., in terms of the at least one combined QoS parameter) and the predefined criterion for the at least two PDU sets may be equivalent and / or these terms may be used interchangeably. The combined QoS requirement for the at least two PDU sets may be, or may be derived from, a service level agreement (SLA) for the service (e.g., application) underlying the at least two PDU sets.

[0122] Alternatively or in addition, the receiving of the report message may comprise assessing whether or not the at least two PDU sets fulfil the inter-dependency criterion and / or fulfil the predefined criterion in terms of the at least one combined QoS parameter (e.g., as a requirement for user experience assessment) based on the report message.

[0123] Herein, a network may comprise the AN, and optionally a core network (CN) serving the AN.

[0124] Same or further embodiments can achieve real-time performance monitoring. The ability to measure and report at least one combined QoS parameters for a combination of at least two PDU sets, e.g. in real-time, enables the AN to dynamically monitor the performance of the (e.g., uplink or downlink) connection. This can be particularly important for applications with multiple streams each requiring stringent QoS levels, such as extended reality (XR) services, wherein even small deviations in QoS can significantly impact user experience.

[0125] Same or further embodiments can enhance network responsiveness. With timely report messages from the WD, the AN can quickly respond to changing network conditions or service requirements, e.g. implementing adjustments to maintain or improve the QoS for active PDU sets.

[0126] Same or further embodiments can use AN resource more efficiently or more effectively. The information provided by the WD can assist the AN optimize the use of available radio resources, leading to more efficient network operation and / or higher overall throughput. For example, smaller margins in the resource allocation of the multiple PDU set can be controlled by virtue of the measurement report.

[0127] Same or further embodiments can address or resolve AN issues preemptively. By identifying QoS degradation early in one of the inter-dependent PDU sets, the AN can proactively take corrective actions before service quality is noticeably impacted, thus maintaining high service reliability and user satisfaction and avoiding interruption of the entire service. Same or further embodiments can tailor QoS policies. The AN can use the reported QoS measurements to configure QoS policies (e.g., mapping rules or scheduling rules) for groups of PDU sets (e.g., groups of QoS flows), e.g. ensuring that each type of data traffic receives the appropriate QoS based on its specific characteristics and requirements.

[0128] Alternatively or in addition, the wireless device may be a remote wireless device that is wirelessly connected to the AN through relay wireless device. For example, in the transmitting step, the report message may be forwarded (e.g., on behalf of the wireless device or as a report message of the relay wireless device itself) to the AN.

[0129] The AN may be a radio access network (RAN). The RAN may comprise one or more network nodes (e.g., base stations), e.g., performing the second method aspect. Alternatively or in addition, the AN may be a vehicular, ad hoc and / or mesh network comprising two or more radio devices, e.g., acting as remote radio device and / or relay radio device.

[0130] Any wireless device may be a radio device, e.g. a 3GPP user equipment (UE) or a Wi-Fi station (STA). The wireless device may be a mobile or portable station, a device for machine-type communication (MTC), a device for narrowband Internet of Things (NB-loT) or a combination thereof. Examples for the UE and the mobile station include a mobile phone, a tablet computer and a self-driving vehicle. Examples for the portable station include a laptop computer and a television set. Examples for the MTC device or the NB-loT device include robots, sensors and / or actuators, e.g., in manufacturing, automotive communication and home automation. The MTC device or the NB-loT device may be implemented in a manufacturing plant, household appliances and consumer electronics.

[0131] Whenever referring to the AN, the AN may be implemented by one or more network nodes (e.g., base stations such as optical or radio base stations).

[0132] The term network node may encompass any station that is configured to provide wireless access (e.g., radio access) to any of the wireless devices. The base stations may also be or may comprise or may define a cell, a transmission and reception point (TRP), a radio access node or access point (AP). Examples for the network node (e.g., base station) may include a 3G base station or Node B (NB), 4G base station or eNodeB (eNB), a 5G base station or gNodeB (gNB), a Wi-Fi AP, and a network controller (e.g., according to Bluetooth, ZigBee or Z-Wave).

[0133] The AN (e.g., the network node serving the wireless device) may provide a data link from the wireless device to a host computer, e.g. providing a PDU set (e.g., carrying user data) in the DL and / or receiving the PDU set (e.g., carrying user data) from the wireless device in the UL.

[0134] The AN (e.g., the RAN) may be implemented according to the Global System for Mobile Communications (GSM), the Universal Mobile Telecommunications System (UMTS), 3GPP Long Term Evolution (LTE) and / or 3GPP New Radio (NR).

[0135] Any aspect of the technique may be implemented on a Physical Layer (PHY), a Medium Access Control (MAC) layer, a Radio Link Control (RLC) layer, a packet data convergence protocol (PDCP) layer, a Radio Resource Control (RRC) layer and / or a Service Data Adaptation Protocol (SDAP) layer of a protocol stack for the wireless (e.g., radio) communication. When referring to the first method aspect performed by the wireless device (e.g., a UE), the steps may be performed by one or more entities of one or more protocol layer at the wireless device. When referring to a second method aspect performed by the AN (e.g., the network node such as a gNB or eNB), the steps may be performed by one or more entities of a protocol layer at the AN. Any one of the method aspects may be performed by a combination of different layers. E.g. the SDAP layer in the user plane may be responsible for defining the QoS requirements and / or mapping of QFI to DRBs and / or the PDCP layer or the RRC layer may be responsible for processing (e.g., sending or receiving) the report message.

[0136] Independently of, or in combination with, any aspect or embodiment disclosed herein, a wireless device (e.g., a UE) may be configured (e.g., by receiving a configuration message at the wireless device from the AN in the first method aspect and / or by sending a configuration message from the AN to the wireless device in the second method aspect) to report (e.g., to send) uplink (UL) interdependency information (e.g., in the report message), optionally over the RRC or PDCP or SDAP protocol layers. The report message may be dynamically reported, e.g. either periodically, aperiodic, or upon a request from the AN.

[0137] Herein, referring to a protocol of a layer may refer to the corresponding layer in the protocol stack or a method performed by said layer. Vice versa, referring to a layer of the protocol stack may also refer to the corresponding protocol of the layer. Any protocol may be implemented by a corresponding method.

[0138] As to another aspect, a computer program product is provided. The computer program product comprises program code portions for performing any one of the steps of the method aspect disclosed herein when the computer program product is executed by one or more computing devices. The computer program product may be stored on a computer-readable recording medium. The computer program product may also be provided for download, e.g., via the radio network, the RAN, the Internet and / or the host computer. Alternatively, or in addition, the method may be encoded in a Field-Programmable Gate Array (FPGA) and / or an Application-Specific Integrated Circuit (ASIC), or the functionality may be provided for download by means of a hardware description language.

[0139] When the WD (e.g., a UE) reports the at least one measured QoS parameters of the at least two PDU sets, the AN (e.g., the gNB) may use this information to optimize network performance or network resources. For example, the network node may determine, or the report message may be indicative of, whether the predefined criterion (e.g., a requirement) for the at least one combined QoS parameter is fulfilled. Optionally, if the predefined criterion is not fulfilled, the network node may increase (e.g., wireless communication) resources allocated to the WD in the scheduling step (e.g., for at least one of the at least two PDU sets). Alternatively or in addition, if the predefined criterion is not fulfilled, the network node may discard all (e.g., PDUs) of the at least two PDU sets.

[0140] Embodiments can improve scheduling decisions at the AN. For example, with up- to-date inter-dependency and / or an up-to-date value for the combined QoS parameter, the AN (e.g., the first and / or second network node, preferably a gNB) can make better-informed scheduling decisions, e.g., map one or more DRB to the one or more QoS flows of the at least two PDU sets and / or balance prioritizing traffic of the mutually dependent at least two PDU sets that are sensitive to delay or errors and / or can manage congestion more effectively.

[0141] The method may be performed by a network node of the AN, e.g., the network node serving the WD or the fore-mentioned first and / or second network node. Alternatively or in addition, the method may be performed by a gNodeB (gNB) (e.g., a base station in a 5G network as the AN), which wirelessly interfaces with the WD (e.g., a user equipment (U E)) and which interfaces (e.g., in a wired manner or wirelessly) with a core network (e.g., a 5G core network, 5GC).

[0142] By scheduling resources based on the received report message, embodiments of the AN (e.g., gNB) can leverage the at least two combined PDU sets reported by the WD (e.g., UE) to optimize a performance of the AN, and / or ensuring that user experiences are consistent with the QoS profiles defined for various services. This can be critical in 5G ANs, wherein a wide range of services with diverse QoS requirements must be supported simultaneously.

[0143] The scheduling may comprise scheduling resources for at least two different data flows (e.g., QoS flows) that are inter-dependent (e.g., as defined herein, inter alia for the at least two PDU sets) in the uplink of the WD. The at least two PDU sets may be associated with and / or sent on the at least two data flows, respectively.

[0144] The scheduling may comprise configuring the WD with radio resources for the uplink. Alternatively or in addition, the scheduling may comprise setting one or more AN parameters related to the WD and / or the at least two PDU sets, e.g. at least one of a QoS parameters, and the predefined criterion for at least one QoS parameter. Alternatively or in addition, upon reception of the report message, the AN may use the information to configure (e.g., reconfigure) enhanced scheduling mechanism, such as a configured grant (CG), discontinuous reception (DRX), and pre-scheduling or semi-persistent scheduling (SPS).

[0145] The receiving of the report message may comprise analyzing the report. For example, the AN (e.g., the gNB) may process the received one or more report messages to determine the inter-dependency and / or a current QoS performance (e.g., a value of the at least one combined QoS parameter) for the at least two PDU sets and / or for each WD (e.g., UE). This may involve analyzing the at least one combined QoS parameter of the at least two PDU sets and / or PDU set QoS parameters of the individual PDU sets in the at least two PDU sets according to at least one QoS parameter (e.g., related to error rate, delay, and throughput according to a service).

[0146] Herein, a combined QoS requirement of the at least two PDU sets (e.g., in terms of the at least one combined QoS parameter) and the predefined criterion for the at least two PDU sets may be equivalent and / or these terms may be used interchangeably. The combined QoS requirement for the at least two PDU sets may be, or may be derived from, a service level agreement (SLA) for the service (e.g., application) underlying the at least two PDU sets.

[0147] Alternatively or in addition, the receiving of the report message may comprise assessing whether or not the at least two PDU sets fulfil the inter-dependency criterion and / or fulfil the predefined criterion in terms of the at least one combined QoS parameter (e.g., as a requirement for user experience assessment) based on the report message.

[0148] Herein, a network may comprise the AN, and optionally a core network (CN) serving the AN.

[0149] The method (e.g., according to the second method aspect), wherein the scheduling of the resources may comprise at least one of adjusting a resource allocation of the at least two PDU sets, optionally if the received report message is indicative of one of the at least two PDU sets fulfilling its QoS requirement while another one of the at least two PDU sets does not fulfill its QoS requirement, and / or wherein the resource allocation for the WD is adjusted by changing the resource allocation of temporal resources, frequency resources and / or spatial resources of the AN and / or a transmit power control setting; configuring one or more functions of the AN, optionally of the network node, based on the received report message, optionally Hybrid Automatic Repeat Request (HARQ) settings are reconfigured or a modulation and coding scheme, MCS, is reconfigured or a retransmission strategy is reconfigured; updating PDU set handling at the AN for the inter-dependent at least two PDU sets; adapting to a dynamic traffic patterns, optionally wherein the AN uses the received report message as dynamic QoS performance information to adapt to changing traffic patterns and / or wherein a service or an application underlying the at least two PDU sets uses variable bit rates or burst-like traffic; and sending a feedback to a core network serving the AN, optionally wherein sending the feedback to the core network is indicative of a QoS performance of the service based on the combination of the at least two PDU sets and the received report message, preferably to update policies and / or rules for traffic management and / or PDU session establishment.

[0150] The method (e.g., according to the second method aspect) may further comprise or initiate receiving a capability message from the WD. Alternatively or in addition, the capability message may be indicative of at least one of a capability of the WD to measure the at least one combined QoS parameter for the combined at least two PDU sets in the uplink towards the AN; a capability of the WD to obtain the at least one inter-dependency between the at least two combined PDU sets; a capability of the WD to report a result of the measurement of the at least one combined QoS parameter for the combined at least two PDU sets to the AN; an inter-dependency criterion for determining the interdependency of the at least two PDU sets; one or more PDU set QoS parameters of the at least two PDU sets in the uplink towards the AN, which the WD may be capable of measuring and / or sending; one or more combined QoS parameters of the combined at least two PDU sets in the uplink towards the AN, which the WD may be capable of measuring and / or sending; a physical layer information of the WD; and a feature set indicator, optionally comprising radio protocol information.

[0151] The method (e.g., according to the second method aspect) may further comprise or initiate sending a configuration message to the WD, optionally the configuration message being indicative of at least one of an inter-dependency between the at least two PDU sets; an inter-dependency criterion for determining the inter-dependency between the at least two PDU sets; the interdependent at least two PDU sets; one or more PDU set QoS parameters to be measured for the at least two PDU sets and / or to be combined for the measuring of the at least one combined QoS parameter; the at least one combined QoS parameter to be measured for the at least two PDU sets; the predefined criterion, optionally a threshold value for the combined QoS parameter or a threshold value for the delay; an Internet Protocol flow (IP flow) associated with the at least two PDU sets; a QoS flow, optionally a QoS flow identifier (QFIs) associated with the at least two PDU sets; a data radio bearer (DRB), associated with the at least two PDU sets; PDU set identifiers of the at least two PDU sets; a cross-PDU set importance (cross-PSI) associated with the at least two PDU sets and / or indicative of an importance level of the inter-dependency; a set of QoS flow identifiers (QFIs) associated with the at least two PDU sets; a set of DRB indexes associated with the at least two PDU sets; an obtaining mode for the obtaining of the inter-dependency in the WD; a measuring mode of the measurement of at least one QoS parameter of the at least two PDU sets; a reporting mode for the sending of the report message; an obtainment window for the obtaining of the inter-dependency at the WD and / or for the measuring of the at least one combined QoS parameter of the inter-dependent at least two PDU sets at the WD; a periodicity for the measuring the at least one QoS parameter and / or the obtaining of the inter-dependency and / or the sending of the report message; and a deadline for the sending of the report message.

[0152] The scheduling (e.g., according to the second method aspect) may comprise changing a mapping of one or more data radio bearers (DRBs), to at least one or two QoS flows or QFIs used by the at least two PDU sets in response to the receiving of the report message; and / or changing a mapping of at least one or two QoS flows or QFIs used by the at least two PDU sets to one or more data radio bearers (DRBs), in response to the receiving of the report message.

[0153] In fourth generation (4G) LTE (Long Term Evolution) and fifth generation (5G) NR (New Radio), a Data Radio Bearer (DRB) may be a service provided by the radio protocol architecture to transfer user data between the WD (e.g., a UE) and the AN (e.g., a RAN). The DRB may be responsible for the transfer of user plane data. The DRB may be technically characterized by several parameters that define how data is handled and transmitted over the radio interface.

[0154] The scheduling may comprise changing at least one of these parameters, e.g. for each or at least one of the inter-dependent at least two PDU sets. For example, the scheduling may comprise changing at least one of these parameters so as to align the parameters for the inter-dependent at least two PDU sets.

[0155] Each DRB may be associated with a specific QoS profile, which defines the treatment that the data flowing over this bearer will receive. This may include parameters such as priority, packet delay budget, packet error loss rate, and bit rates (GBR, MBR, etc.) of the level of individual PDUs, which can be controlled by the AN as opposed to the reported QoS parameters on the level of the PDU set, which cannot be measured at (e.g., the lower layers) of the AN. The QoS profile may ensure the required level of service for various types of traffic such as voice over IP (VoIP), real-time video, or best-effort data transfer.

[0156] The DRB may be mapped to a Logical Channel, which is an abstract concept defining the type of information being transferred. For example, a dedicated traffic channel (DTCH) may be used for user plane data transfer.

[0157] A radio link control (RLC) protocol may be operated for the PDU set in one of three modes: transparent mode (TM), unacknowledged mode (UM), and acknowledged mode (AM). Each DRB may be associated with an RLC entity that operates in one of these modes, defining the level of reliability for the data transfer. The scheduling may comprise changing the mode. For example, transparent mode does not provide error correction, unacknowledged mode may provide partial error correction, and acknowledged mode may use an Automatic Repeat Request (ARQ) mechanism for full error correction.

[0158] The scheduling may comprise changing a configuration of a packet data convergence protocol (PDCP). The PDCP may provide header compression, decompression, and ciphering functionalities to reduce overhead and secure the data. The PDCP configuration for a DRB may define how the data should be processed by the PDCP layer.

[0159] The scheduling may comprise establishing, modifying, or releasing a radio bearer setup by signaling procedures between the WD (e.g., UE) and the AN. These procedures may define the properties of the one or more DRBs and how data is to be managed over them.

[0160] The scheduling may comprise changing a security of the PDU set on the one or more DRBs, which may be encrypted and / or integrity-protected to ensure privacy and prevent tampering.

[0161] The scheduling may comprise mobility handling of the PDU set. The one or more DRBs may be configured to support seamless handovers when the WD (e.g., a UE) moves from one cell to another. This can ensure that all PDUs in the PDU set are continuously transferred despite the mobility of the WD.

[0162] A Quality of Service flow (QoS flow) in the context of 3GPP specifications, particularly for 5G networks (5G NR), may encompass any concept defined in a service-based architecture of the AN and / or the core network (CN) serving the AN to manage and / or ensure the delivery of all PDUs in the PDU set with the required service quality.

[0163] Each QoS flow may be identified by a QoS Flow Identifier (QFI). The QFI may be unique for the WD and / or within a PDU session of the WD. The QFI may be used for mapping between the 5G Core (5GC) as the CN and the Radio Access Network (RAN) as the AN. The QFI may be carried in the protocol headers to differentiate between different QoS flows. The scheduling of resources for the PDU set may comprise changing at least one parameter in a set of parameters associated with each QoS flow to define the required treatment by the network. These parameters include QoS Class Identifier (5QI), Allocation and Retention Priority (ARP), Guaranteed Bit Rate (GBR) for data flows requiring a certain minimum bit rate, Maximum Data Burst Volume (MDBV) for GBR flows, and Non-Dynamic 5QI. The 5QI may be an index defining a scalar QoS characteristics of IP packets transferred in the PDUs of the PDU set, which are reference to the level of guarantee to be provided for packet delivery. The ARP may be used for ensuring resources in congested situations and has a priority level, preemption capability, and preemption vulnerability. The GBR and the non-GBR may be two types of QoS flows. In the GBR, the QoS flow is allocated a certain amount of network resources, while a non-GBR QoS flow shares resources with other flows.

[0164] The scheduling may comprise changing QoS rules of the level of PDUs. The QoS may be defined by rules that govern how certain types of traffic are treated within the AN or the CN or the network. These rules may be used to determine how packets are forwarded in a QoS flow and / or include QoS rule identifiers, precedence, and segregation and aggregation rules.

[0165] The scheduling may comprise changing a traffic flow template. For mapping between the user traffic and the QoS flows, one or more traffic flow templates (TFTs) may be used. These templates classify PDUs in the PDU set based on parameters such as source and destination IP addresses, source and destination ports, protocol identifiers, and more. For the PDU set, the AN may apply the changed template to all PDUs in the PDU set.

[0166] The scheduling may comprise QoS flow level signaling or any signaling procedures for establishing, modifying, or releasing the QoS flows between the WD and the network (e.g., the AN or the CN). For example, the scheduling may comprise protocols and procedures for the QoS flow setup during the establishment of the PDU session.

[0167] The scheduling of the resources responsive to received report message may comprise a deviation from reflective QoS and / or reflective mapping of DRBs to QFIs. For example, in a first state, the AN may use for the uplink the same QoS treatment and / or mapping as the corresponding downlink flow without explicit signaling from the WD. In a second state, the AN may use for the uplink the a QoS treatment and / or mapping the is different from the corresponding downlink flow based on the received report message.

[0168] The scheduling may control an operation of the AN to ensure that all PDUs of the PDU set associated with a QoS flow are handled in the network, complying with the predefined criterion (e.g., a QoS requirement of the PDU set). Embodiments, especially in 5G networks, can support diverse services with different QoS requirements for their PDU sets, such as enhanced mobile broadband (eMBB), ultra-reliable and low latency communications (URLLC), and massive machine type communications (mMTC).

[0169] The method (e.g., according to the second method aspect) may further comprise any one of the steps or features of the first method aspect.

[0170] As to a device aspect a computer program product is provided. The computer program product comprises program code portions for performing any one of the steps of the first method aspect or the second method aspect when the computer program product is executed on one or more computing devices, optionally stored on a computer-readable recording medium.

[0171] As to a first device aspect a wireless device (WD), wirelessly connected or connectable to an access network (AN) is provided. The WD comprising memory operable to store instructions and processing circuitry operable to execute the instructions, such that the WD is operable to measure at the WD at least one combined quality of service, QoS, parameter. Each of the at least one combined QoS parameter is measured for a combination of at least two PDU sets in an uplink towards the AN. The at least two PDU sets are mutually inter-dependent. The WD is further operable to send, to the AN, a report message indicative of the measured at least one combined QoS parameter.

[0172] As to a first device aspect, a wireless device according to the first method aspect is provided. The wireless device comprises processing circuitry (e.g., at least one processor and a memory). Said memory comprises instructions executable by said at least one processor whereby the wireless device is operative to perform any one of the steps of the first method aspect. Alternatively or in addition, the wireless device is configured to perform any one of the steps of the first method aspect. The WD (e.g., according to the first device aspect) may further comprise any one of the features or being operable to perform any one of the steps of the first method aspect.

[0173] As to another first device aspect a wireless device (WD), wirelessly connected or connectable to an access network (AN) is provided. The WD is configured to measure at the WD at least one combined quality of service (QoS) parameter. Each of the at least one combined QoS parameter is measured for a combination of at least two PDU sets in an uplink towards the AN. The at least two PDU sets are mutually inter-dependent. The WD is further configured to send, to the AN, a report message indicative of the measured at least one combined QoS parameter.

[0174] The WD (e.g., according to the other first device aspect) may further comprise the features or being configured to perform any one of the steps of the first method aspect.

[0175] As to a second device aspect a network node of an access network (AN) is provide. The network node comprises memory operable to store instructions and processing circuitry operable to execute the instructions, such that the network node is operable to receive a report message from a WD wirelessly connected to the AN. The report message is indicative of at least one combined QoS parameter for a combination of at least two PDU sets measured at the WD in an uplink towards the AN. The at least two PDU sets are mutually inter-dependent. The network node is further operable to schedule resources for the uplink of the WD based on the received report message.

[0176] As to a second device aspect, a network node according to the second method aspect is provided. The network node comprises processing circuitry (e.g., at least one processor and a memory). Said memory comprises instructions executable by said at least one processor whereby the network node is operative to perform any one of the steps of the second method aspect. Alternatively or in addition, the network node is configured to perform any one of the steps of the second method aspect.

[0177] The network node (e.g., according to the second device aspect) may be further operable to perform any one of the steps of the second method aspect. As to another device aspect a network node of an access network (AN) is provide. The network node is configured to receive a report message from a WD wirelessly connected to the AN. The report message is indicative of at least one combined QoS parameter for a combination of at least two PDU sets measured at the WD in an uplink towards the AN. The at least two PDU sets are mutually inter-dependent. The network node is further configured to schedule resources for the uplink of the WD based on the received report message.

[0178] The network node (e.g., according to the other second device aspect) may be further configured to perform any one of the steps of the second method aspect.

[0179] As to a system aspect a communication system including a host computer is provided. The communication system comprises processing circuitry configured to provide user data; and a communication interface configured to forward user data to a cellular or ad hoc radio network for transmission to a user equipment, UE. The UE comprises a radio interface and processing circuitry, the processing circuitry of the UE being configured to execute any one of the steps the first method aspect.

[0180] The communication system (e.g., according to the system aspect) may further including the UE.

[0181] The radio network (e.g., according to the system aspect) may further comprise a base station, or a radio device functioning as a gateway, which is configured to communicate with the UE.

[0182] The communication system (e.g., according to the system aspect), wherein the base station, or the radio device functioning as a gateway, may comprise processing circuitry, which is configured to execute any one of the steps of the second method aspect.

[0183] The communication system (e.g., according to the system aspect), wherein the processing circuitry of the host computer may be configured to execute a host application, thereby providing the user data; and the processing circuitry of the UE may be configured to execute a client application associated with the host application. As to a still further aspect, a communication system including a host computer is provided. The host computer comprises a processing circuitry configured to provide or receive user data, e.g., included in the at least two PDU sets. The host computer may comprise a communication interface configured to receive the PDU set from a cellular network (e.g., the AN and / or the network node serving the wireless device) from the wireless device (e.g., a UE). A processing circuitry of the cellular network is configured to execute any one of the steps of the first and / or second method aspects. Alternatively or in addition, the UE comprises a radio interface and processing circuitry, which is configured to execute any one of the steps of the first and / or second method aspects.

[0184] The communication system may further include the UE. Alternatively, or in addition, the cellular network may further include one or more base stations configured for radio communication with the UE and / or to provide a data link between the UE and the host computer using the first and / or second method aspects.

[0185] The processing circuitry of the host computer may be configured to execute a host application, thereby providing the first and / or second data and / or any host computer functionality described herein. Alternatively, or in addition, the processing circuitry of the UE may be configured to execute a client application associated with the host application.

[0186] Any one of the devices, the UE, the base station, the communication system or any node or station for embodying the technique may further include any feature disclosed in the context of the method aspect, and vice versa. Particularly, any one of the units and modules disclosed herein may be configured to perform or initiate one or more of the steps of the method aspect.

[0187] Any one of the devices, the transmitting node, the receiving node, the user equipment (UE), the network node, the base station, the communication system or any node or station for embodying the technique may further include any feature disclosed in the context of the method aspect, and vice versa the method aspect may comprise any step or feature disclosed in the context of the device aspects. Particularly, any one of the units and modules disclosed herein may be configured to perform or initiate one or more of the steps of the method aspect, and the devices may comprise a unit or a module performing any of the steps of the method aspect. Brief Description of the Drawings

[0188] Further details of embodiments of the technique are described with reference to the enclosed drawings, wherein:

[0189] Fig. 1 shows a schematic block diagram of a device embodiment of a first aspect for handling multiple PDU sets;

[0190] Fig. 2 shows a schematic block diagram of a device embodiment of a second aspect for handling a PDU set;

[0191] Fig. 3 shows a flowchart for a method embodiment of a first aspect for handling multiple PDU sets, which method may be implementable by the device of Fig. 1;

[0192] Fig. 4 shows a flowchart for a method embodiment of a second aspect for handling multiple PDU sets, which method may be implementable by the device of Fig. 2;

[0193] Fig. 5 schematically illustrates a first example of an access network comprising first embodiments of the devices of Figs. 1 and 2 for performing the methods of Figs. 3 and 4, respectively;

[0194] Fig. 6 schematically illustrates an existing downlink network architecture, which may be combined with an uplink network architecture according to any of the embodiments of Figs. 1 to 4;

[0195] Fig. 7 schematically illustrates a second example of an access network and a downlink network architecture comprising second embodiments of the devices of Figs. 1 and 2 for performing the methods of Figs. 3 and 4, respectively;

[0196] Fig. 8 schematically illustrates data traffic flows for different PDU sets, which are related by common services;

[0197] Fig. 9 schematically illustrates the second example from an aggregated point of view of the multi-modal data implemented by the at least two PDU sets; Fig. 10 schematically illustrates a third example of an AN 510 comprising a third embodiments of the devices 100 and 200 for performing the methods 300 and 400, respectively;

[0198] Fig. 11 schematically illustrates a block diagram of protocol sublayers for performing the method of Fig. 3 or 4 according to a third embodiment;

[0199] Fig. 12 schematically illustrates a block diagram of protocol entities for performing the method of Fig. 3 or 4 according to a fourth embodiment;

[0200] Fig. 13 schematically illustrates a block diagram of protocol entities for performing the method of Fig. 3 or 4 according to a fifth embodiment;

[0201] Fig. 14 schematically illustrates a block diagram of protocol sublayers for performing the method of Fig. 3 or 4 according to a sixth embodiment;

[0202] Fig. 15 schematically illustrates an overview of a communication system 500 comprising devices 100 and 200 for performing the methods 300 and 400, respectively;

[0203] Fig. 16 schematically illustrates a signaling diagram resulting from devices of Figs. 1 and 2 performing the method of Fig. 3 or 4 according to a seventh embodiment;

[0204] Fig. 17 shows a schematic block diagram of a wireless device embodying the device of Fig. 1;

[0205] Fig. 18 shows a schematic block diagram of a network node embodying the device of Fig. 2;

[0206] Fig. 19 schematically illustrates an example telecommunication network connected via an intermediate network to a host computer;

[0207] Fig. 20 shows a generalized block diagram of a host computer communicating via a base station or radio device functioning as a gateway with a user equipment over a partially wireless connection; and Figs. 21 and 22 show flowcharts for methods implemented in a communication system including a host computer, a base station or radio device functioning as a gateway and a user equipment.

[0208] Detailed Description

[0209] In the following description, for purposes of explanation and not limitation, specific details are set forth, such as a specific network environment in order to provide a thorough understanding of the technique disclosed herein. It will be apparent to one skilled in the art that the technique may be practiced in other embodiments that depart from these specific details. Moreover, while the following embodiments are primarily described for a New Radio (NR) or 5G implementation, it is readily apparent that the technique described herein may also be implemented for any other radio communication technique, including a Wireless Local Area Network (WLAN) implementation according to the standard family IEEE 802.11, 3GPP LTE (e.g., LTE-Advanced or a related radio access technique such as MulteFire), for Bluetooth according to the Bluetooth Special Interest Group (SIG), particularly Bluetooth Low Energy, Bluetooth Mesh Networking and Bluetooth broadcasting, for Z-Wave according to the Z-Wave Alliance or for ZigBee based on IEEE 802.15.4.

[0210] Moreover, those skilled in the art will appreciate that the functions, steps, units and modules explained herein may be implemented using software functioning in conjunction with a programmed microprocessor, an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), a Digital Signal Processor (DSP) or a general purpose computer, e.g., including an Advanced RISC Machine (ARM). It will also be appreciated that, while the following embodiments are primarily described in context with methods and devices, the invention may also be embodied in a computer program product as well as in a system comprising at least one computer processor and memory coupled to the at least one processor, wherein the memory is encoded with one or more programs that may perform the functions and steps or implement the units and modules disclosed herein. Each of the disclosed embodiments may be combined with any other embodiment.

[0211] Fig. 1 schematically illustrates a block diagram of an embodiment of a device for handling multiple PDU sets according to a first aspect of the subject technique. The device is generically referred to by reference sign 100. The device 100 is wirelessly connected or connectable to an access node (AN). The device 100 may be capable of handling (e.g., identifying and reporting) related PDU sets, such as a wireless device, e.g. a user equipment (UE) in a telecommunication network.

[0212] The device 100 for handling PDU sets comprises a combined QoS parameter measurement module 106 and a report sending module 110. The combined QoS parameter measurement module 106 is responsible for measuring (e.g., determining or inspecting) at least one combined QoS parameter for a combination of at least two PDU sets in an uplink towards the AN. The combination of the at least two PDU sets may be mutually inter-dependent, e.g., the at least two PDU sets may be corresponding to and / or originating from one service. The at least one combined QoS parameter for the at least two PDU sets may be measured. The at least one combined QoS parameter may be measured for the at least two PDU sets individually and / or in combination (e.g., relative difference of the combined QoS parameter).

[0213] Adjacent to this module 106, the report sending 110 facilitates sending a report message indicative of the measurement results to the access network 510 (AN, e.g. a RAN). Specifically, this module 110 oversees creating and dispatching the report message, which may be an RRC control message (e.g., an information element, IE, and / or UE assistance information, UAI), a PDCP control PDU or an SDAP control PDU. The report message may carry information such as result of the measurement of the combined QoS parameters individually for the combined at least PDU sets and / or a relative measurement of the combined QoS parameters for the combined at least PDU sets.

[0214] The measuring and / or reporting may be triggered by an event, such as receiving a message from the AN indicating at least two PDU sets are mutually interdependent and / or obtaining in the wireless device 100 that at least two PDU sets are mutually inter-dependent. The reporting to the AN 510 may be triggered by an event such as fulfilling a predefined criterion (e.g., in combined QoS parameter measurement).

[0215] This can enable the AN to control the scheduling to steer the QoS for all related PDU sets within a margin above the QoS requirements of the service underlying the PDU set, or to decide that the service cannot be maintained as a whole by removing all inter-dependent PDU sets. Without the report message 506 from the wireless device 100 or means to measure whether the UL requirement are met it makes it impossible for network node 200 to know the QoS impacts of configuring UL PDU Set handling in the wireless device 100 for multi-modality services with dependencies between flows. Thus, the advantage is for the network (e.g., AN) to make better configurations of the UL PDU Set handling features and to make better scheduling decisions to improve the performance with respect to dependent QoS requirements.

[0216] Any of the modules of the device 100 may be implemented by units configured to provide the corresponding functionality.

[0217] The device 100 may also be referred to as, or may be embodied by, the wireless device (or briefly: UE). The wireless device 100 and the AN may be in direct radio communication, e.g., at least for sending the report message from the wireless device 100 to the AN. The AN may be embodied by the device 200, e.g. a base station or network node.

[0218] Fig. 2 schematically illustrates a block diagram of an embodiment of a device for handling multiple Packet Data Unit (PDU) sets according to a second aspect of the subject technique. The device is generically referred to by reference sign 200. The device 200 depicted in Fig. 2 may be a network node designed for handling multimodal PDU sets. This device can be embodied by a gNB, which is an element within an access network (AN) such as a 5G network responsible for communicating with wireless devices like user equipment (UE), e.g. the device 100.

[0219] A report reception module 210 of the device 200 is tasked with receiving report messages from one or more wireless devices 100. These report messages indicate the measured at least one combined QoS parameter, optionally contain results or consequences in terms of at least one combined QoS parameters measured for the combination of at least two PDU sets, e.g. that were conducted by the wireless devices in the uplink towards the AN (e.g., the gNB). By processing this incoming information, the report reception module 210 plays a critical role in ensuring that the AN can assess and respond to the quality of service of inter-dependent PDU sets and / or QoS situation observed at the wireless devices as well as the interdependency and QoS needs of the services used by the wireless devices.

[0220] Complementing the report reception module 210 is a resource scheduling module 212. This module 212 takes into account the measured at least one combined QoS parameter for the at least two inter-dependent PDU sets received from the one or more wireless devices 100 and schedules resources accordingly for the at least two PDU sets. For example, it uses the report message to allocate the necessary uplink resources to meet or balance the QoS requirements for the different PDU sets constituting one service. It may also be responsible for managing any necessary adjustments or reconfigurations to the network's uplink scheduling strategies in order to optimize or balance performance and adhere to service level agreements.

[0221] Any of the modules of the device 200 may be implemented by units configured to provide the corresponding functionality.

[0222] The device 200 may also be referred to as, or may be embodied by, the AN or a network node of the AN (or briefly: gNB). The network node 200 and the wireless device may be in direct radio communication, e.g., at least for exchanging the report message from the wireless device to the network node 200. The wireless device may be embodied by the device 100.

[0223] In 3GPP Release 18, the System Architecture and Services working group 2 (SA2) standardized 5G system support of Packet Data Unit (PDU) sets (e.g., as specified partly below). With the introduction of the PDU set, new requirements including PDU set Quality of Service Parameters and PDU set information were introduced to support PDU set handling, e.g. each of which three features are exemplified below. At the same time, the Radio Layer 2 and Radio Layer 3 RRC working group (RAN2) introduced UE features to support PDU set handling in the uplink. RAN2 agreed that a UE can identify PDU sets and related PDU set information for PDU set handling.

[0224] In a further work item description (WID) for 3GPP Release 19, 3GPP has agreed to continue the study to better support, e.g., extended Reality (XR), uplink scheduling potentially introducing further PDU set features.

[0225] Herein, a PDU set may comprise one or more PDUs carrying the payload of one unit of information generated at the application level, e.g. one or more frames or one or more video slices, etc., e.g. for extended Reality (XR) services. All the PDUs of a PDU set are transmitted within the same Quality of Service (QoS) flow.

[0226] Any embodiment of any aspect may be implemented based on general information provided by the 3GPP TS 23.501, version 18.4.0 or later. For example, PDU set QoS Parameters (as examples of the QoS parameter) are used to support PDU set based QoS handling in the Next Generation RNA (NG- RAN) or 5G System (5GS). At least one PDU set QoS Parameter shall be sent to the NG-RAN to enable PDU set based QoS handling.

[0227] Any embodiment may use at least one of the following PDU set combined QoS parameters, e.g. as specified in any of the above-mentioned 3GPP documents:

[0228] 1. a combined PDU set Delay Budget (PSDB).

[0229] 2. a combined PDU set Error Rate (PSER).

[0230] 3. a combined PDU set Integrated Handling Information (PSI HI).

[0231] 4. a combined latency of the inter-dependent at least two PDU sets.

[0232] 5. a combined jitter of the inter-dependent at least two PDU sets.

[0233] 6. a combined PDU set loss rate of the respective PDU set among the interdependent at least two PDU sets.

[0234] 7. a combined bit rate of the inter-dependent at least two PDU sets.

[0235] 8. an indicator of combined fulfilment of a guaranteed flow bit rate (GFBR) of the inter-dependent at least two PDU sets.

[0236] 9. an indicator of combined fulfilment of a maximum flow bit rate (MFBR) of the inter-dependent at least two PDU sets.

[0237] 10. a combined PDU set queued time of the inter-dependent at least two PDU sets.

[0238] 11. a combined PDU set importance (PSI) of the inter-dependent at least two PDU sets.

[0239] 12. a combined PDU set dropping ration of the inter-dependent at least two PDU sets.

[0240] 13. a combined PDU set priority level of the inter-dependent at least two PDU sets.

[0241] Alternatively or in addition, the above mentioned combined QoS parameters may also to be referred as QoS parameters. In other words the "combined" word may be referred to the same QoS parameter that may be measured for a combination of at least two PDU sets.

[0242] A QoS profile may include the PDU set combined QoS parameters (e.g., Qos parameters) described herein. The Policy Control Function (PCF) may determine the one or more PDU set QoS parameters based on information provided by an Application Function (AF) and / or a local configuration. The PDU set QoS parameters are sent to the Session Management Function (SMF) as part of a policy and charging control rule (PCC rule). The Session Management Function (SMF) sends them to the AN (e.g., a Next Generation Radio Access Network, NG-RAN) as part of the QoS profile.

[0243] If the AN (e.g., NG-RAN) receives the measured combined QoS parameters for the combined at least two PDU sets and supports them, it enables the PDU set based QoS handling and applies PDU set QoS Parameters as described herein.

[0244] Any embodiment of any aspect may use the PDU set error rate as an example of the combined QoS parameter.

[0245] The PDU set Error Rate (PSER) defines an upper bound for the rate of PDU sets that have been processed by the sender of a link layer protocol (e.g. RLC in RAN of a 3GPP access) but that are not successfully delivered by the corresponding receiver to the upper layer (e.g. Packet Data Convergence Protocol (PDCP) in RAN of a 3GPP access). Thus, the PSER defines an upper bound for a rate of non-congestion related PDU set losses. The purpose of the PSER is to allow for appropriate link layer protocol configurations (e.g. RLC and HARQ in RAN of a 3GPP access).

[0246] It is noted that in any embodiment (e.g., in accordance with 3GPP Release 18), a PDU set may be considered as successfully delivered only when all PDUs of a PDU set are delivered successfully. Optionally, the PDU set may comprise at least two PDUs.

[0247] It is further noted that how the AN (e.g., RAN) enforces PSER is up to RAN implementation.

[0248] A QoS flow may be associated with only one PDU set error rate. PSER is an optional parameter. If the PSER is available, the PSER supersedes the PER. The value of the PDU set error rate is the same in UL and DL.

[0249] Any embodiment of any aspect may use the PDU set delay budget as an example of the combined QoS parameter, e.g. including any one of the following features.

[0250] The PDU set delay budget (PSDB) may define an upper bound for the delay that a PDU set may experience for the transfer between the UE 100 and the N6 termination point at the UPF (e.g., below reference sign 522), i.e. the duration between the reception time of the first PDU (at the N6 termination point for DL or the UE for UL) and the time when all PDUs of a PDU set have been successfully received (at the UE for DL or N6 termination point for UL).

[0251] The (e.g., same) PSDB may apply to the DL PDU set received by the PDU Session Anchor (PSA) UPF over the N6 interface and / or to the UL PDU set sent by the UE 100.

[0252] It is noted that to enable support for PSDB, it is required that a maximum inter arrival time between the first received PDU and the last received PDU of a PDU set complies with Service Level Agreement (SLA). This maximum inter arrival time does not exceed PSDB. NG-RAN behavior when the SLA is not fulfilled is out of scope of this specification.

[0253] A QoS Flow is associated with only one PDU set delay budget. The value of the PDU set delay budget is the same in UL and DL. PSDB is an optional parameter that may be provided by the Policy Control Function (PCF). The provided PSDB can be used by the NG-RAN to support the configuration of scheduling and link layer functions.

[0254] When the PSDB is available, the PSDB supersedes a packet delay budget (PDB) for the given QoS Flow.

[0255] An AN PSDB (i.e., the PSDB of the access network, AN) may be derived at NG-RAN by subtracting a CN PDB (i.e. a packet delay budget or a PDU set delay budget of the core network, CN, e.g., as described herein or in clause 5.7.3.4 of aforementioned 3GPP document TS 23.501) from the PSDB.

[0256] Any aspect of any embodiment may include PDU set based handling (or handling of the combined at least two PDU sets as a whole) as a combined QoS parameter of the at least two PDU sets or as a control item of the scheduling based on the report message.

[0257] A PDU set may be comprised of one or more PDUs carrying an application layer payload such as, e.g. a video frame or video slice. The PDU set based QoS handling by the NG-RAN is determined by PDU set QoS Parameters in the QoS profile of the QoS Flow (specified in clause 5.7.7 of the afore-mentioned 3GPP document TS 23.501) and PDU set information provided by the PSA UPF via N3 / N9 interface (e.g., as described in clause 5.37.5.2 loc. cit.). The PDU set based QoS Handling can be applied for Guaranteed Bit Rate (GBR) and non-GBR QoS Flows.

[0258] In addition to the PDU related service information, the AF may provide PDU set related assistance information for dynamic Policy and Charging Control (PCC) control. One or more of the following PDU set related assistance information may be provided to the NEF / PCF using the AF session with required QoS procedures (e.g., in clauses 4.15.6.6 and 4.15.6.6a of the 3GPP document TS 23.502, version 18.4.0):

[0259] PDU set QoS Parameters as described in clause 5.7.7 of 3GPP document TS 23.502, version 18.4.0.

[0260] Protocol Description: Indicates transport protocol (e.g. RTP, SRTP), transport protocol header extensions (e.g. RTP Header Extension for PDU set marking as defined in 3GPP document TS 26.522, version 0.2.0), payload type and format (e.g. H.264, H.265), and format parameters (e.g. H.264 profile level and packetization mode) used by the service data flow.

[0261] The PDU set QoS Parameters and / or Protocol Description may be provided by the CN, e.g. by the AF and / or may be used in determining PCC Rules by the PCF as defined in clause 6.1.3.27.4 of 3GPP document TS 23.503, version 18.4.0, and the Protocol Description may be used for identifying the PDU set information by the Presence Reporting Area (PSA) UPF.

[0262] When the SMF receives a PCC rule containing one or more measured combined QoS parameters (e.g., PSER, PSDB, PSI H I, etc), the SMF may add these measured combined QoS parameters to the QoS Profile of the QoS Flow as described in clause 6.2.2.4 of the 3GPP document TS 23.503. Alternatively, the SMF may be configured to support PDU set based QoS Handling without receiving PCC rules from a PCF.

[0263] For the downlink direction, the PSA UPF identifies PDUs that belong to PDU sets and marks them accordingly as described in clause 5.37.5.2. If the UPF receives a PDU that does not belong to a PDU set based on Protocol Description for PDU set identification, then the UPF still maps it to a PDU set and determines the PDU set Information as described in said clause 5.37.5.2. It is noted that, if the PSA UPF receives a PDU that does not belong to a PDU set, then it is assumed that the UPF determines the PDU set importance value based on pre-configuration.

[0264] Any embodiment of any aspect may use PDU set Information and / or Identification as an example of the QoS parameter, e.g. including any one of the following features.

[0265] To support PDU set based QoS handling, the PSA UPF identifies PDUs that belong to PDU sets and determines the below PDU set information which it sends to the NG-RAN in the GPRS Tunneling Protocol (GTP-U) header. The PDU set information is used by the NG-RAN for PDU set based QoS handling as described above.

[0266] The PDU set information comprises:

[0267] PDU set sequence number.

[0268] Indication of end PDU of the PDU set (i.e., the last PDU in the PDU set).

[0269] PDU sequence number within a PDU set.

[0270] PDU set size in bytes.

[0271] PDU set importance, which identifies the relative importance of a PDU set compared to other PDU sets within a QoS Flow.

[0272] The NG-RAN may use the Priority Level (e.g. according to clause 5.7.3.3 of said 3GPP document 23.501) across QoS Flows and PDU set importance within a QoS Flow for PDU set level packet discarding in presence of congestion.

[0273] It is noted that in addition to considering the PDU set Importance within a QoS Flow, NG-RAN could also consider the relative PDU set Importance across QoS Flows of the same Priority Level when determining which PDU set needs to be discarded, which is up to implementation and configuration of operator.

[0274] It is further noted that the PDU set Information can be different for different PDU sets within a QoS Flow.

[0275] It is noted that the at least two mutually inter-dependent PDU sets may have same importance within a QoS Flow. Alternatively or in addition, the at least two mutually inter-dependent PDU sets may correspond to different QFIs.

[0276] The PDU set may have XR traffic characteristics, e.g. as described below. XR applications typically generate traffic flows which are in principle periodic, e.g. video traffic with 30, 60, 90, or 120 fps. However, the traffic arrival moment at the RAN is affected by jitter around the periodicity value, due to processing of the frames at the application (e.g. for compression) and the capabilities of the platform used by the application, as well as transmission through the Core Network. This is modelled in 3GPP document TR 38.838, by assuming that each data frame arriving at the RAN has a random jitter of [-4; +4] ms (optionally [-5; +5] ms) around the main periodicity. The probability of the jitter value within this interval is given by a truncated Gaussian distribution with mean 0 ms and standard deviation 2 ms.

[0277] XR traffic has strict delay requirements, in terms of packet delay budget (PDB). This is the maximum tolerable delay for a packet to be transmitted from a gNB to a UE. The PDB value depends on the XR traffic type and is overall between 5 ms and 30 ms. The XR traffic may comprise the at least two PDU sets 750.

[0278] Any embodiment of any aspect may relate to reporting QoS performance status information in the report message, e.g., dynamically, using control PDUs sent between RRC and / or SDAP and / or PDCP layers.

[0279] Below reference to reference signs in figures after Fig. 4 serve for illustration and do not limit the steps.

[0280] Fig. 3 shows an example flowchart for a method 300 of handling multiple PDU sets, e.g. by a device depicted in Fig. 1. The method 300 may begin with an optional step 302 wherein the wireless device 100 sends a capability message 502 to the AN 510.

[0281] In the method 300, a wireless device 100 performs a series of steps to handle multiple PDU sets 750 within an access network 510. Initially, the wireless device 100 may send 302 a capability message 502 to the access network 510. This capability message 502 conveys information about the wireless device's 100 ability to process and / or measure certain combined QoS parameters for a combination of the at least PDU sets 750, which are mutually inter-dependent 760.

[0282] The capability message 502 may be indicative of at least one of a capability of the WD 100 to measure 306 the at least one combined QoS parameter for the combined at least two PDU sets 750 in the uplink towards the AN 510; a capability of the WD 100 to obtain the at least one inter-dependency 760 between the at least two combined PDU sets 750; a capability of the WD 100 to report 310 a result of the measurement 306 of the at least one combined QoS parameter for the combined at least two PDU sets 750 to the AN 510; an inter-dependency criterion for determining the inter-dependency 760 of the at least two PDU sets 750; one or more PDU set QoS parameters of the at least two PDU sets 750 in the uplink towards the AN 510, which the WD 100 is capable of measuring 306 and / or sending 310; one or more combined QoS parameters of the combined at least two PDU sets 750 in the uplink towards the AN 510, which the WD 100 is capable of measuring 306 and / or sending 310; a physical layer information of the WD 100; and a feature set indicator, optionally comprising radio protocol information.

[0283] Subsequently, the wireless device 100 may optionally receive 304 a configuration message 504 from the access network 510, which provides guidance on how to measure 306 the at least one combined QoS parameter for the combined at least two PDU sets 750 and potentially other parameters related to the handling of these PDU sets 750. Based on this configuration, the wireless device 100 measures 306 the combined QoS parameter for the combined at least two PDU sets 750.

[0284] The configuration message 504 being indicative of at least one of the interdependency 760 between the at least two PDU sets 750; the inter-dependency criterion for determining the inter-dependency 760 between the at least two PDU sets 750; the inter-dependent at least two PDU sets 750; one or more PDU set QoS parameters to be measured for the at least two PDU sets 750 and / or to be combined for the measuring 306 of the at least one combined QoS parameter; the at least one combined QoS parameter to be measured 306 for the at least two PDU sets 750; the predefined criterion, optionally a threshold value for the combined QoS parameter or a threshold value for the delay; an Internet Protocol flow (IP flow) associated with the at least two PDU sets 750; a QoS flow 724, optionally a QoS flow identifier (QFIs) associated with the at least two PDU sets 750; a data radio bearer (DRB) 714, associated with the at least two PDU sets 750; PDU set identifiers of the at least two PDU sets 750; a cross-PDU set importance, cross-PSI, associated with the at least two PDU sets 750 and / or indicative of an importance level of the inter-dependency 760; a set of QFIs associated with the at least two PDU sets 750; a set of DRB indexes associated with the at least two PDU sets 750; an obtaining mode for the obtaining of the inter-dependency 760 in the WD 100; a measuring mode of the measurement 306 of at least one QoS parameter of the at least two PDU sets 750; a reporting mode for the sending 310 of the report message 506; an obtainment window for the obtaining of the interdependency 760 at the WD 100 and / or for the measuring 306 of the at least one combined QoS parameter of the inter-dependent 760 at least two PDU sets 750 at the WD 100; a periodicity for the measuring 306 the at least one QoS parameter and / or the obtaining of the inter-dependency 760 and / or the sending 310 of the report message; and a deadline for the sending 310 of the report message 506.

[0285] Optionally, the wireless device 100 may determine 308 whether the measured 306 at least one combined QoS parameter for the combination of the at least two PDU sets 750 fulfils a predefined criterion. Alternatively or in addition, the report message 506 may be indicative of whether or not the predefined criterion is fulfilled and / or wherein the sending 310 of the report message 506 may be triggered if the predefined criterion is not fulfilled.

[0286] The wireless device 100 sends 310 a report message 506 to the AN 510, indicating the measured 306 at least one combined QoS parameter for a combination of at least two PDU sets 750. The report message 506 allows the access network 510 to make informed decisions regarding resource scheduling and prioritization based on the information provided by the wireless device 100.

[0287] Optionally, the wireless device 100 may send 312 to the AN 510, optionally to a serving network node 200, a request message 508 indicative of, or including a request for, mapping the at least two PDU sets 750 to the same DRB 714 and / or indicative of, or including a request for, mapping different QoS flows, optionally different QFIs, of the at least two PDU sets 750 to the same DRB 714. Alternatively or in addition, the wireless device 100 may send 314 to the AN 510, optionally to a serving network node 200, a confirmation message 512, optionally an RRC- Reconfiguration-Complete message indicative of adapting a reconfiguration, optionally confirming an adaptation to a changed mapping of the at least two PDU sets 750 to the same DRB 714 and / or mapping different QoS flows, optionally different QFIs, of the at least two PDU sets 750 to the same DRB 714 and / or in response to the receiving 304 of the configuration message 504.

[0288] It should be noted that certain steps in the method 300 are optional, as indicated by the dotted boxes. These optional steps may include additional parameters or considerations that enhance the wireless device's 100 ability to accurately report the measured combined QoS parameter of the combined at least two PDU sets 750 to the access network 510.

[0289] In other words the method 300 enables the wireless device 100 to measure, trigger and report dependent UL QoS performance which is based on combining QoS parameters (e.g., PSER, PSDB or any other QoS measure of individual traffic flow). The method 300 further enables the wireless device 100 to dynamically report dependent UL QoS measurement information over the PDCP or SDAP protocol layers.

[0290] The device 100 may comprise modules 1XY for performing the steps 3XY.

[0291] Fig. 4 illustrates the steps of a method 400 according to a second aspect for handling multiple PDU sets by a device, e.g., the device 200. The method 400 encompasses scheduling resources 412 for a wireless device 100 based on a report message 506 received from the wireless device 100. The report message 506 is indicative of at least one measured 306 combined QoS parameter for a combined at least two PDU sets 750 that are mutually inter-dependent.

[0292] Optionally, the network node 200 initiates the method 400 by receiving 402 a capability message from the wireless device 100. The capability message 502 may be indicative of various capabilities of the wireless device 100, such as its ability to measure at least one combined QoS parameters for a combination of at least two PDU sets 750 that are mutually inter-dependent 760, obtain inter-dependencies 760, report results to the access network 510, and possible features and physical layer information specific to the wireless device 100.

[0293] Subsequently, the network node 200 may optionally send 404 a configuration message to the wireless device 100. This configuration message 504 can include a range of configuration directives, including but not limited to the at least one combined QoS parameters to be measured, predefined criteria or thresholds, QoS flows 724 or identifiers, DRB indexes, potential mappings between PDU sets 750 and DRBs 714, and possibly certain QoS flow identifiers (QFIs). It may also specify modes for obtaining inter-dependency 760 and for reporting, as well as define obtainment windows, periodicities, and deadlines for sending report messages 506. The received 410 report message 506 enables the network node 200 to understand the quality of service (e.g., quality of performance) of a combination of at least two PDU sets 750 as experienced by the wireless device 100. Based on this understanding, the network node 200 schedules resources 412 appropriately. The scheduling of resources 412 by the network node 200 may include a range of actions such as reconfigurations to align with QoS requirements, handling dynamic traffic patterns, or sending feedback to the core network 520 regarding QoS performance.

[0294] Optionally, the network node 200 can adapt QoS flows 724 or QFIs associated with the PDU sets 750 based on the report message 506, potentially aiming for mapping different QFIs to a single DRB 714. This scheduling step 412 allows for an optimized management of uplink or downlink resource allocation in response to changing traffic demands, keeping in line with the predefined QoS criteria and enhancing overall network performance.

[0295] The device 200 may comprise modules 2XY for performing the steps 4XY.

[0296] Herein below, the wireless device 100 is described with reference to an exemplary UE 100 and the network node 200 is described with reference to an exemplary gNB 200 in a 5G setting for illustration. The skilled person will appreciate that this illustration is not limiting, and that the corresponding features and steps can be implemented beyond 5G and / or for an optical data link.

[0297] Fig. 5 schematically illustrates a first example of an access network comprising first embodiments of the devices 100 and 200 for performing corresponding first embodiments of the methods 300 and 400, respectively.

[0298] Fig. 5 depicts a schematic illustration of an example of a telecommunication network 500, emphasizing how it integrates devices for handling Packet Data Unit (PDU) sets. The example features two wireless devices, labeled generically as UE 100, each situated within distinct cells or beams 201 of network nodes, labeled as gNB 200. Each UE 100 operates within the scope of a gNB 200, representing its connection to the broader access network (AN) 510.

[0299] The illustration captures a moment of communication wherein each UE 100 sends a report message 506 to its respectively serving gNB 200. This exchange of the report message is denoted by directed arrows, symbolizing the sending 310 and receiving 410 of control signaling. The report messages 506 result from the internal processes 300 of the UEs 100 concerning PDU sets, which are transmitted in the uplink, e.g. direction toward the gNB 200.

[0300] At the network's periphery, the illustration shows a core network (CN) 520, interfaced with the AN 510. While not directly involved with the immediate interactions 310 and 410 between UEs 100 and gNBs 200, the CN 520 may serve as the backbone, interfacing with external networks or services and relaying information into and out of the AN 510. For example, the CN 520 or an application server may signal QoS requirements and / or inter-dependencies of the PDU sets to the AN 510, while the report message 506 provides the actual observations and / or measurement values of the inter-dependencies and / or QoS parameters at the UE 100.

[0301] Fig. 5 accentuates how individual components within a telecommunication network — e.g., UEs 100, gNBs 200, and the core network 520 — collaborate to manage and convey QoS-related information pertaining to PDU sets in a wireless communication environment.

[0302] Fig. 6 schematically illustrates an existing downlink network architecture, which may be combined with an uplink network architecture according to any of the embodiments of the devices 100 and 200 and the methods 300 and 400.

[0303] Fig. 6 presents a schematic overview of an example of the downlink network architecture. The devices 100 and 200 may inherit any feature of the devices 10 and 20, respectively. The UE 10 interfaces with the gNB 20, which serves as a connection point within the access network to manage PDU sessions and QoS flows. A feature of the architecture is the delineation of a PDU session, which encompasses the entirety of the QoS flow and interfaces with an N3 Tunnel connecting to a UPF. The UPF, in turn, provides connectivity to an Application Server (AS) within a Data Network (DN), establishing a comprehensive channel from the user applications to the network infrastructure.

[0304] Within the UE 10 and the gNB 20, data radio bearers (DRBs) play a crucial role in handling QoS flows, which are mapped to the DRBs. This mapping ensures that the appropriate level of quality is attributed to different types of traffic, as defined by the QoS flow. QoS flows fall into two main categories: those with Guaranteed Bit Rate (e.g., here QFI=4 or QFI=3) and those without (e.g., here Non-GBR, QFI=6), reflecting the diversity of service requirements within the network. The Data Network addresses the service routing by imposing QoS policies for Service Data Flows (SDF), such as SDF1, SDF2, SDF3, and SDF4, each corresponding to specific IP flow characteristics such as flow 1, flow 2, flow 3, flow 4, and flow 5, which are ultimately realized in the user applications.

[0305] An essential aspect of this communication system 50 is the implementation of QFI Insertion at various stages of the PDU session to precisely steer the data packets according to their predetermined QoS requirements. This fine-grained control, supported by additional network protocols like the Internet Protocol (IP), solidifies the QoS enforcement mechanisms integral to the network performance and the user experience.

[0306] Concurrently, the option of TFT / SPDF Template filtering at a Data Network (DN), user plane function (UPF), and application server (AS) junction provides a supplementary means to refine and optimize traffic flow management based on complex rules and conditions that govern the passage of data packets through the network.

[0307] Any concept illustrated or described by Fig. 6 for the ability of the network 50 to deliver differential QoS levels in the DL may be applied to the subject technique in the UL and / or controlled by the report message, e.g., ensuring that the diverse service requirements of modern telecommunication networks are met with precision and efficiency in both UL and DL.

[0308] For example, conventional reflective QoS is an optional feature for the UE 10 that allows the UE 10 to deduce the uplink (UL) mapping between QoS flows and radio bearers from the downlink (DL) mapping, e.g., if QoS Flow Identifier (QFI) X is mapped to DRB Y in the DL, then it is the same in UL.

[0309] Fig. 7 schematically illustrates a second example of an access network (AN) 510 (e.g. a downlink network architecture of the AN 510) comprising second embodiments of the devices 100 and 200 for performing the methods 300 and 400, respectively. Herein, while the first, second, etc. embodiments may be realized independently, the embodiments are combined in a variant of such embodiments. For example, any equal reference signs may relate to identical, equivalent or inter-changeable features and steps. Fig. 7 schematically illustrates an example of an access network (AN) 510 and a downlink network architecture encompassing second embodiments of devices for handling a PDU set 750.

[0310] In this architecture, the wireless device 100 is capable of handling PDU sets such as those in an uplink towards the AN 510, e.g. a network node 200, which can be a components of broader telecommunication systems that manage various data flows and network efficiencies.

[0311] The architecture also includes the network node 200 (e.g., a gNB) designed to handle the PDU sets within the access network 510. This network node may manage and / or optimize the flow of PDUs, especially the PDU sets 750, between the wireless device 100 and the core network (CN) 520. The CN 520 is a part of the telecommunication network 500 that provides a multitude of services and connectivity to other networks or services, interfacing with the access network 510 and transmitting data to and from an application server (AS) located in or beyond a data network DN (e.g., the Internet).

[0312] Central to the efficiency of the system 500, the wireless device 100 employs an Obtainment Module 106 and a Report Transmission Module 110 for the uplink PDU set 750. The PDCP layer 710 of the wireless device 100 is responsible for key functions like header compression, encryption, and ensuring data integrity. As part of the wireless device's features, Radio Bearers 714 facilitate the transfer of data radio bearers from applications within the wireless device 100.

[0313] The network node 200 leverages a Report Reception Module 210 to handle incoming reports and a PDU Resource Scheduling Module 212 to manage resources optimally for the at least two PDU sets. It utilizes PDCP 710 and / or SDAP 720 layers for protocol functionality, which handle tasks such as mapping QoS flows to DRBs and marking QoS flow IDs in data packets, e.g. based on the report message 506.

[0314] Integral to network operations, the QoS flows 724 are associated with specific quality of service metrics, such as guaranteed bit rates, delays, and priority levels. These flows are critical for ensuring that the network can meet various service level agreements and user expectations for data transmission quality. The PDU set 750 is the focal point of these interactions, being the collection of PDUs that are transmitted as a unit of data at the application level. The entire set of PDUs is transmitted within the same QoS flow 724, ensuring consistent handling across the network.

[0315] For example, at the network node 200, a mapping function or PDU session 702 works in conjunction with an N3 Tunnel 704 to at least one of these layers 710 and / or 720 to the CN 520. This tunneling facility is a critical part of ensuring secure and reliable data transfer from the AN 510 (e.g., a Radio AN, i.e. RAN) to the CN 520 part of the telecommunication system 500.

[0316] The interaction between the wireless device 100 and the network node 200 is signified by the exchange of report messages 506, which are crucial for conveying information about the performance and requirements of the PDU set 750. These report messages 506 can be indicators of QoS parameters such as PDU set error rate, delay budget, and / or importance for each respective device's scheduling and handling of data flows.

[0317] Any feature, e.g. for the network node reaction in the step 412, may be based on or extend, any 3GPP features (e.g., as discussed herein) and / or may involve alternative or additional configurations, features, or communication protocols that can be implemented to enhance or modify the standard data handling procedures of the PDU set 750 in the wireless device 100 and / or the network node 200 within the access network 510.

[0318] Optionally, the UE 100 may decide the mapping between QoS flows and radio bearers in the UL. The gNB 200 may reflect that mapping in the UL. The report message may comprise instructions to overrule the reflective mapping.

[0319] Alternatively or in addition, the gNB 200 may change the

[0320] In a variant of any embodiment, the report message may trigger or change in the PDCP and / or SDAP layer (e.g., by using an PDCP or SDAP control PDU as the report message) the mapping between QFI and DRB. Alternatively or in addition, the PDCP or SDAP may signal to lower layers of the radio protocol stack (e.g., the medium access control layer, MAC layer, or the physical layer, PHY layer) for performing scheduling Another advantage of using SDAP or PDCP control PDUs for the report message is that these PDUs are carried over the same DRB as the user data. This means they receive the same priority as the user data (e.g., the PDUs of the PDU set).

[0321] In a variant of any embodiment, the report message may be sent using assistance information, e.g. to have the report reach the layer that is most relevant for the mapping or scheduling.

[0322] When sending the report message using the UE Assistance Information (UAI) message it will be a part of radio resource control (RRC) signaling, which require additional overhead and potential service interruption as it has the highest transmission priority in the UE, which can be avoided using the PDCP and / or the SDAP layer for sending the report message.

[0323] How the gNB 200 responds in the step 410 to the report message received in the step 406 may up to gNB implementation. For example, the SDAP or PDCP layer in the gNB 200 may simply receive 406 the report message and forward it to the corresponding implemented function, e.g. that does the bookkeeping of the QoS for each UE 100 in the gNB 200. The reported message may be indicative a result of the measurement or a value QoS parameter for the PDU set that triggers a control reaction, e.g. by activating feature X in layer Y or reconfigure DRB mapping.

[0324] Any one or more steps of the method 300 and / or 400 may be implemented at or using a Service Data Adaptation Protocol (SDAP), e.g. as described below.

[0325] The objective is to describe the SDAP architecture and the SDAP entity from a functional point of view. The specified functionality only applies to UE 100 with connection to the 5G-CN 520 and UE 100 in NR sidelink (SL) communication.

[0326] Any embodiment of any aspect may implement at least one of the following features of a structure of the SDAP layer 720.

[0327] Fig. 8 schematically illustrates services 1 to 3 causing inter-dependencies between PDU sets used for the multi-modal (e.g., interactive system) input and outputs (e.g., multi-modal communication).

[0328] Multi-modality services may refer to applications that generates multiple traffic flows on a network. In one non limiting example an XR service may comprise of multiple different flows constituting different modalities e.g. a video flow, an audio flow, a pose flow or a haptic flow for an acceptable end user experience, it is of great importance that the flows / modalities are synchronized and consumed at right moment by the application. For example, it is typically desirable that video and audio are synchronized during video conferencing. In another example state of the art haptics e.g. haptic gloves or body suit require close synchronization with both audio and video.

[0329] The tactile and multi-modal communication service can be applied in multiple fields, e.g. industry, robotics and telepresence, virtual reality, augmented reality, healthcare, road traffic, serious gaming, education, culture and smart grid. These services support applications enabling input from more than one sources and / or output to more than one destinations to convey information more effectively. As Fig. 8 illustrates, the input and output can be different modalities including:

[0330] Video / Audio media;

[0331] Information received by sensors about the environment, e.g. brightness, temperature, humidity, etc.;

[0332] Haptic data: can be feelings when touching a surface (e.g., pressure, texture, vibration, temperature), or kinaesthetic senses (e.g. gravity, pull forces, sense of position awareness).

[0333] For immersive multi-modal VR applications, synchronization between different media components is critical in order to avoid having a negative impact on the user experience (i.e. viewers detecting lack of synchronization), particularly when the synchronization threshold between two or more modalities is less than the latency key performance indicators (KPI) for the application (e.g., a service). Example synchronization thresholds are summarized in below Table 1.

[0334] Table 1 Typical synchronization thresholds for immersive multi-modality VR applications

[0335] Any embodiment may be implemented to achieve the following requirements. The 5G system shall enable an authorized 3rd party to provide one or more policies for flows associated with an application. The policy may contain e.g. the set of UEs and data flows, the expected QoS handling and associated triggering events, other coordination information.

[0336] The 5G system shall support a means to apply 3rd party provided policy(ies) for flows associated with an application. The policy may contain e.g. the set of UEs and data flows, the expected QoS handling and associated triggering events, other coordination information.

[0337] It is noted that the policy may be used by a 3rd party application for coordination of the transmission of multiple UEs' flows (e.g., haptic, audio and video) of a multimodal communication session.

[0338] Any embodiment may be implemented to comply with a new work item description (WID) for 3GPP Release 19, which agreed to the following objective for XR enhancements:

[0339] "Study and if justified, specify aspects related to multi-modality (intra-UE) (with coordination with SA2 / SA4 as needed by LS request). Aim to facilitate efficient and effective support for XR application with Multiple QoS flows with multi-modal inter-dependencies, meeting multi-modal QoS requirements, e.g. synchronization and / or coordination. Efficiency enhancements are expected to be visible in terms of capacity or power consumption. [RAN2]."

[0340] The report message may enable the UE 100 to report inter-dependency information between multi-modal flows (i.e., corresponding PDU sets), e.g. through RRC and / or MAC signaling.

[0341] The following detailed embodiments may be implemented as described or in combination with any of the above-mentioned embodiments or the embodiments in the list of embodiments.

[0342] A UE 100 may report in the step 310, e.g. using UAI, a recommendation in the report message 506 to the network that the current QFI-DRB mapping is insufficient i.e., that a new DRB could be established or that existing QFI-DRB mapping needs modification. The UE 100 may report in UAI that a group of QoS Flow Identifiers (Q.FI) X,Y,Z should be mapped to one or more DRB, and the suggested corresponding mapping between QFIs and DRBs. In another example the UE reports that a single Q.FI X should be mapped to single DRB A or the set of suitable DRBs. The report message 506 may also include QFI-to-DRB mapping also includes a PDU Session ID of which the one or more QFIs are associated with.

[0343] Besides of the QFI-DRB recommendation outlined above, the UE could also add to the Flow Type being the flow type information about the service type of flow e.g. audio, video, pose, etc.

[0344] When receiving a status report the gNB may accept or decline the UE recommendation, or provide a new configuration by generating a new control PDU. Such control PDU may be sent and received from either SDAP, PDCP, RLC or MAC layer.

[0345] Additionally the UE 100 may also indicate in the report message 506 through a SDAP and / or PDCP and / or RLC and / or MAC control PDU that the UE 100 wants to request a new DRB to be established for a particular PDU Session ID and selected QFIs. A gNB 200 may respond by either sending an RRCreconfiguration or a using a SDAP and / or PDCP and / or RLC and / or MAC control PDU to either accept or decline the request.

[0346] In another embodiment, instead of the explicit recommendation of the mapping, a UE 100 only reports in the report message 506 the generic inter-dependency of multiple DRBs (e.g., corresponding to the at least two PDU sets) for the same service. The inter-dependency will be a set of indexes of DRBs that are associated for the same service if a DBR is already configured. This information (i.e., the report message 506) can be signaled 310 by UAI since a connection was established already. Alternatively or in addition, when the report message 506 from the UE 100 includes the inter-dependency information, it may also include associated service identify information so that a network 510 or the network node 200 is enabled to determine in the step 412 which one or more DRBs 714 are related with which one or more services.

[0347] The UE 100 can also report application flow information (in the report message 506 or a further report message 506) that are inter-dependent, e.g., that enable identifying PDU sets that are inter-dependent. One example is that a UE 100 reports port numbers or IP addresses, which are marked with same service identity, e.g. which are the same for all packets from the indicated port numbers of IP addresses. This information can be signaled as RRC messages 506 before DRB configuration.

[0348] The gNB 200 and / or RAN 510 may also provide a configuration 504 for the UE 100 to trigger a report of the information outlined above. Such configuration 504 may include rules for measurements in the step 306, thresholds and timers. When a measurement configured by the network 510 trespasses the configured threshold, the UE 100 may send a report 506 including the QFI-DRB recommendation and the measured results for the parameter which triggered the report, or it may include all measured results for all configured measurements. Further, the UE 100 may report the measurement results for other current QFI-DRB pairs if they are available. Additionally, after a report has been sent the network can configure a prohibition timer that restrict an additional report for as long as the timer is running.

[0349] In another embodiment, a UE 100 may trigger a report 506 of all above "multimodality" information when any of existing application flow is terminated or new application flow starts, e.g. which may require any update of a DRB configuration (e.g., at the network node 200). It is also possible that a network 510 or network node 200 initiates the UE report 506 by sending a multi-modality information report request.

[0350] The technique may be applied to uplink (UL), downlink (DL) or direct communications between radio devices, e.g., device-to-device (D2D) communications or sidelink (SL) communications.

[0351] Each of the transmitting station 100 and receiving station 200 may be a radio device or a base station. Herein, any radio device may be a mobile or portable station and / or any radio device wirelessly connectable to a base station or RAN, or to another radio device. For example, the radio device may be a user equipment (UE), a device for machine-type communication (MTC) or a device for (e.g., narrowband) Internet of Things (loT). Two or more radio devices may be configured to wirelessly connect to each other, e.g., in an ad hoc radio network or via a 3GPP SL connection. Furthermore, any base station may be a station providing radio access, may be part of a radio access network (RAN) and / or may be a node connected to the RAN for controlling the radio access. For example, the base station may be an access point, for example a Wi-Fi access point. Fig. 9 schematically illustrates the second example from an aggregated point of view of the multi-modal data implemented by the at least two PDU sets.

[0352] In prior art if there is dependency between packets in different flows there is also a combined PSER value that is potentially of higher interest for the network to know, i.e. the combined PSER for dependent packets from each flow. Such a combined PSER could not be calculated based on the individual PSER values for each flow since the combined PSER can only be evaluated on a PDU Set level. For example if there is a PDU Set A from flow 1 and PDU Set B from flow 2 that are dependent on each other but not dependent on PDU Set C from flow 2 the success of PDU Set A and B must be evaluated together to find out the dependent success ratio, but this evaluation is not impacted of the success of PDU Set C.

[0353] Therefore since PDU Set information is not visible for network in prior art in the UL there is no possibility for the network to calculate any combined PSER value. With legacy solutions of only reporting the individual PSER values the network would not have the possibility to calculate such dependent PSER value even with other solutions for multi-modality. This would be the case even if the dependency between flows and induvial PSER values would be reported to the RAN node.

[0354] Combined PSER can only be calculated on PDU Set level and thus cannot be based on flow information.

[0355] Fig. 10 schematically illustrates a third example of an access network (AN) 510 (e.g. a downlink network architecture of the AN 510) comprising a third embodiments of the devices 100 and 200 for performing the methods 300 and 400, respectively. The third embodiment may be combined with other embodiments. For example, any equal reference signs may relate to identical, equivalent or inter-changeable features and steps.

[0356] The PDU sets 750 may be received in wireless device 100 from the network node 200 via different QFIs 724 in downlink. The QFIs 724 may comprise one or more PDU sets 750. The network node 200 may send a configuration message 504 indicative of inter-dependency 760 between at least two PDU sets 750. Herein shows inter-dependency between pair of PDU sets, but the inter-dependency 760 may be between more than two PDU sets 750 (not shown here).The interdependency 760 between the at least two PDU sets 750 may be a number and / or an index. For example the index may be zero or "None" for not inter-dependent PDU sets 750 and a non-zero number (e.g., index) for at least two inter-dependent 760 PDU sets 750.

[0357] The wireless device 100 may receive 304 the configuration message 504 indicative of the inter-dependencies 760 of the at least two PDU sets 750 and perform a measurement 306 on at least one combined QoS parameter for a combination of PDU sets 750 (e.g., for inter-dependent PDU sets 750).

[0358] Fig. 11 schematically illustrates one possible structure for the SDAP sublayer 720.

[0359] It should not restrict an implementation of the SDAP sublayer 720. Alternatively or in addition, the SDAP sublayer may be implemented according to the radio interface protocol architecture defined in 3GPP document TS 38.300, version 18.0.0, e.g. Figure 4.2.1-1 therein, which provides an SDAP sublayer structure view.

[0360] The SDAP sublayer may be configured for DRBs by RRC, e.g. according to 3GPP document TS 38.331, version 18.0.0. The SDAP sublayer 720 maps QoS flows to DRBs. One or more QoS flows may be mapped onto one DRB. One QoS flow is mapped onto only one DRB at a time in the UL.

[0361] The SDAP sublayer may be configured for Multicast / Broadcast Service (MBS) Radio Bearers (MRBs) by RRC, e.g. according to 3GPP document TS 38.331, version 18.0.0. The SDAP sublayer maps MBS QoS flows to MRBs. One or more MBS QoS flows may be mapped onto one MRB.

[0362] In NR sidelink communication, the SDAP sublayer maps PC5 QoS flows to SL-DRBs. One or more PC5 QoS flows may be mapped onto one SL-DRB. One PC5 QoS flow is mapped onto only one SL-DRB at a time in the NR sidelink for transmission.

[0363] Any embodiment of any aspect may implement at least one of the following features of SDAP entities 722.

[0364] The SDAP entities 722 are located in the SDAP sublayer 720 (also: layer). Several SDAP entities 722 may be defined for a UE 100. There is an SDAP entity 722 configured for each individual PDU session or MBS session for NR Uu. For NR sidelink, an SDAP entity 722 may be configured per Destination Layer-2 ID and cast type in the UE 100. An SDAP entity 722 receives and / or delivers SDAP service data units (SDUs) from and / or to upper layers and / or submits and / or receives SDAP data packet data units (PDUs) to and / or from its peer SDAP entity 722 via lower layers. At the transmitting side, when an SDAP entity 722 receives an SDAP SDU from upper layers, it constructs the corresponding SDAP data PDU and submits it to lower layers. At the receiving side, when an SDAP entity 722 receives an SDAP data PDU from lower layers, it retrieves the corresponding SDAP SDU and delivers it to upper layers.

[0365] The function of an SDAP entity 722 for the SDAP sublayer 720 may be implemented according to the functional view of Fig. 12 and / or the SDAP layer functional view of Figure 4.2.2-1 in 3GPP document TS 38.300, version 18.0.0.

[0366] These example should not restrict an implementation of the SDAP sublayer 720. The figure is based on the radio interface protocol architecture defined in 3GPP document TS 38.300, version 18.0.0.

[0367] Reflective QoS flow to DRB mapping may be performed at the UE 100, e.g. as specified in the clause 5.3.2, if DL SDAP header is configured.

[0368] Typically, reflective mapping of a QoS flow to an MRB (i.e., Multicast / Broadcast Service Radio Bearer) is not supported. E.g., there may be no SDAP header for MRB. Alternatively or in addition, reflective PC5 QoS flow to SL-DRB mapping is not supported for NR sidelink (SL) communication.

[0369] Any embodiment of any aspect may implement at least one of the following features and steps of services provided to upper layers.

[0370] The SDAP sublayer 720 provides its service to the user plane upper layers. An example service provided by the SDAP sublayer 720 to upper layers is transfer of user plane data.

[0371] Any embodiment of any aspect may implement at least one of the following features and steps of services expected from lower layers. An SDAP entity 722 may expect from lower layers at least one of the following services: user plane data transfer service; in-order delivery except when out of order delivery is configured by RRC (e.g., according to 3GPP document TS 38.331, version 18.0.0).

[0372] Any embodiment of any aspect may implement at least one of the following functional features of the SDAP sublayer: transfer of user plane data; mapping between a QoS flow and a DRB for both DL and UL; mapping between an MBS QoS flow and an MRB for DL; mapping between a PC5 QoS flow and a SL-DRB for NR sidelink communication; marking QoS flow ID in both DL and UL packets; marking PC5 QoS flow ID in unicast of NR sidelink communication packets; and reflective QoS flow to DRB mapping for the UL SDAP data PDUs.

[0373] Alternatively or in addition, any step of the methods 300 and / or 400 may be implemented at or using a Packet Data Convergence Protocol (PDCP) layer 710.

[0374] The PDCP layer 710 may support at least one of the following functions: transfer of data (user plane or control plane); maintenance of PDCP SNs; header compression and decompression using the ROHC protocol; header compression and decompression using the EHC protocol; uplink data compression and decompression using the UDC protocol; ciphering and deciphering; integrity protection and integrity verification; timer based SDU discard; for split bearers and DAPS bearer, routing; duplication; reordering and in-order delivery; out-of-order delivery; duplicate discarding.

[0375] Fig. 13 provides a functional view of the PDCP layer 710. The gNB 200 may comprise dedicated logic in the PDCP layer to respond to the QoS report message, e.g. trigger discarding of more or less packets in the PDCP layer 710, as an example of the step 410.

[0376] The PDCP entities are located in the PDCP sublayer. Several PDCP entities may be defined for a UE. Each PDCP entity is carrying the data of one radio bearer. A PDCP entity is associated either to the control plane or the user plane depending on which radio bearer it is carrying data for.

[0377] Fig. 14 provides a schematic structural view of the PDCP layer 710.

[0378] The PDCP entity 712 receiving 410 the report message may control the RLC (or further lower layers) for the changing the scheduling of radio resources, e.g. by scheduling less resources when there is a predefined margin between the measure QoS parameters for the PDU set and the QoS requirements, or by scheduling more resources when the margin falls below a predefined threshold or if the QoS requirement is not fulfilled.

[0379] The following detailed embodiments may be implemented as describe below or in combination with any of the above embodiments and / or any of the embodiments in the list of embodiments. For brevity, the AN 510 may be referred to as the network.

[0380] The network 510 (e.g., the gNB 200) provides a configuration (e.g., in the steps 304 and 404) for the UE 100 to measure generic QoS related information (i.e., the QoS parameters), e.g. PSDB, PSER, minimum and / or maximum and / or average PDU set queued time, or PDU set dropping ratio. The configuration may be compound of one or more of the following elements: measured parameter, one or more thresholds for the said parameter, measurement window, measurement periodicity, QFI, DRB. If the network provides the QFI or DRB, it limits the measurements to the PDU sets matching the QFI and / or DRB.

[0381] The UE 100 reporting in the steps 310 and 410 may be event-based, e.g. when the measured value is above or below the configured threshold, periodic-based e.g. measured value is reported periodically, or on-request e.g. the network requests the UE to report the last measured value or to start a measurement and report it to the network. When more than one option is available, the network may be able to configure the one or more reporting methods the UE 100 should follow. When the UE 100 is configured with multiple parameters to measure and / or multiple QFIs, DRBs, or PSIs are indicated, the following reporting options are possible:

[0382] A first option includes an event trigger: the report message 506 only contains the measured value which triggered the report in the corresponding DRB, QFI, and / or PSI. The report message 506 may then indicate to which DRB, Q.FI, and / or PSI corresponds (e.g., fails to meet a predefined criterium). Alternatively, the UE 100 reports 310 the measured value which triggers the report message 506 and the value of the parameter for other DRBs, QF Is, and / or PSIs. Alternatively, the UE 100 may report all measured values for the configured DRBs, QF Is, and / or PSIs.

[0383] A second option includes a periodic trigger: the UE 100 may report all measured values for the configured QoS parameters, e.g. DRBs, QFIs, and / or PSIs.

[0384] A third option includes an on-demand reporting: the UE 100 reports 310 the measurements 306 of the one or more requested QoS parameters. The report message 506 may include values for the DRBs, QFIs, and / or PSIs provided in the configuration or in the "on-demand" measurement request sent by the network to the UE 100.

[0385] If the SDAP or PDCP is used to provide the report, the UE reports the measured parameter value e.g. UL PSER status inside a SDAP / PDCP control PDU. Report may carry measured results for one or multiple QoS flows (QFIs) and / or DRBs and / or PSI levels. Measured results could also be carried in a PDCP Control PDU.

[0386] In a related embodiment, the UE 100 is configured through RRC to either report periodically with time interval X or a-periodically. In the a-periodical case the PDCP or SDAP layer triggers a UL PSER report when requested by gNB through a SDAP or PDCP control PDU. Additionally, the UE can be configured to either continuously measure the UL PSER status or only start the measurement upon request from an SDAP or PDCP control PDU.

[0387] Assuming the UE 100 is capable of providing reports through SDAP or PDCP, the gNB may be unaware of this capability. Thus the UE may trigger the sending of a control PDU indicating to gNB that it supports a status report from respective layer. In a different scenario the gNB may probe the UE for this capability. In this case it is the gNB that sends a control PDU to the UE for which the UE may respond with its own control PDU indicating its support or not. In case it does not support status reporting, the UE can also ignore this control PDU. This mechanism will also enable the UE to update its capability dynamically, in case the traffic pattern and / or requirements of the service has changed.

[0388] Fig. 15 schematically illustrates an overview of a communication system 500 comprising a wireless device 100 (e.g., UE), a network node 200 and an AN 510. Fig. 15 shows layer 2 of the wireless communication architecture comprising an SDAP layer, a PDCP layer and an RRC layer. The report message 506 indicating at least one measured 306 combined QoS parameters for a combination of at least two PDU sets 750. Herein the exemplary combined QoS parameters are a dependent PSDB (D-PSDB) and a dependent PSER (D-PSER).

[0389] The wireless device 100 sends 310 the report message 506 to the network node 200 and / or the AN 510. The network node 200 and / or the AN 510 may further process the received report message 506 for handling the PDU sets 750 and / or scheduling resources for the uplink of the wireless device 100.

[0390] The network node 200 provides a configuration message 504 for the wireless device 100 to measure 306 dependent QoS related information e.g. Dependent- PSER (D-PSER), min / max / average / X percentile Dependent-PDU Set (D-PDU Set) queued time, or D-PDU Set dropping ratio. The network node 200 either configures which dependent QFI, DRB, or flow IDs (there may be multiple flows within a QFI or DRB) the dependent QoS information should be measuring on or leave this up for the wireless device 100 to decide on its own. The configuration message 504 may comprise details on how the dependent information should be evaluated by the wireless device 100, e.g. a threshold of how many individual PDU Sets that may be received for each D-PDU Set to be counted as successfully received.

[0391] When the wireless device 100 is configured with the dependent QoS measuring 306 the wireless device 100 should measure 306 on a PDU Set (or per packet) basis simultaneously for all dependent QFIs / DRBs / flow IDs, i.e. for every metric wireless device 100 may evaluate the dependent packets together. As an example when calculating the D-PSER there may be an addition of an error if any of the PDU Sets that are dependent on each other experience an error and only counted as a success if all of the D-PDU Sets are successfully transmitted. Similarly, dependent PDU set delay may be measured 306 from the time that the PDU set X that is first generated from any flows among PDU sets that have same dependency to the time that PDU set Y that is last successfully delivered among PDU sets that have same dependency.

[0392] Instead of dependent QoS related information, a wireless device 100 may also indicate a network 'dependent QoS failure' (DQF). This indication may be a new RRC message transmitted to the access network, or it could be placed in an existing UL RRC message e.g. Uplink Assistance Information (UAI). The indication comprises the information of dependent QFI / DBR / flow ID which may not meet relevant dependent QoS. For example, if a wireless device 100 measures D-PSER or D-PDU set queued time and any of these cannot meet dependent QoS requirement for a period of time (as per configuration), it reports DQF to the network. It is also possible that a wireless device 100 measure common radio performance that affects jointly dependent QFI / DRB performance. A wireless device 100 specific RSSI, RSRP, RSRQ, measured data rate or any combination of those to reflect radio link performance which may affect all dependent QoS performance may be considered. For example, if any of those radio performance does not fulfill a certain requirement, a wireless device 100 may consider dependent QoS may not be met and it may report DQF. DQF may also allow multiple indication if there is more than one dependent QFI / DBR in a wireless device 100.

[0393] The wireless device 100 reporting may be event-based e.g. when the measured value is above or below a configured threshold. This configured threshold may also indicate individual QFIs / DRBs. For example if one QFI / DRBs is the reason that the D-PSER exceeds a certain threshold then the wireless device 100 may also indicate problems with that specific QFI in the report. Reports may also indicate the relative impact each QFI has on the D-PSER. This may be used for the network to single out which QFI flow that would need special treatment, e.g. configuring CG resources for those periodicities.

[0394] In the case of event-based reporting, the access network may configure a prohibition-timer to limit a new report to be immediately triggered in-case the D- PSER is changing to rapidly. For example the network node 200 of the AN may configure a timer of X ms that is started when the D-PSER report is transmitted. The wireless device 100 may be only allowed to send another measurement reports once the timer has expired. Such a timer may be useful when the radio channel is fluctuating by a lot and the network cannot adapt quickly enough in any case.

[0395] Alternatively, the reporting / measurement of D-PSER may be configured periodically to occur with some configured interval. It may also be triggered on the request of the network, i.e. network may indicate through a signal to start a measurement of the D-PSER.

[0396] Fig. 16 schematically illustrates a signaling diagram resulting from devices 100 and 200 performing the methods 300 and 400 according to a seventh embodiment.

[0397] The signaling diagram illustrates the interplay between various components during the execution of a method for handling a Packet Data Unit (PDU) set within a telecommunications network. The signaling diagram illustrates the interaction between a wireless device 100 (e.g., UE) and a network node 200 (e.g., gNB) of an access network AN, along with the core network 520. The signaling diagram further illustrates internal signaling within the wireless device 100 and the network node 200 and the core node 520.

[0398] The wireless device 100 may proceed to measure 306 the combined QoS parameter for at least two inter-dependent PDU sets 750 at various intervals denoted as a loop and optionally assess the reporting criteria the step 308.

[0399] Following the measurements 306 the wireless device 100 reports 310 the result of the measurement 306 and / or the determining 308. For example, the wireless device 100 evaluates whether the measured PDU set matches preset criteria, potentially triggering a report. If the determination 308 results in the need to report, the wireless device 100 sends 310 a report message 506 back to the network node 200. The report message 506 may be event-based, periodic, or on- demand, as indicated by the multiple exit points from the sending 310 to the network node 200.

[0400] Optionally, the network node 200 and / or the core node 520 may configure the wireless device 100 by sending a configuration message 504, which provides specific instructions for QoS measurements of the PDU set, according to the step 404 or 304. The configuration message 504 from the network node 200 and / or the core node 520 to the wireless device 100 may be indicative of scheduling resources 412. The configuration message may further be indicative of a third party policies for flows.

[0401] The network node 200 is poised to respond by either waiting 410 for periodical QoS measurement reports from the wireless device or by sending a request for QoS measurement to the wireless device, depicted by the vertical flow of communication from and to the network node 200 (e.g., gNB). As the network node 200 receives the report message 506 indicative of the QoS measurement results, it takes suitable action by updating its configuration, scheduling, or general resource allocation for the wireless device 100, e.g., to align DRB and / or the QoS for the at least two PDU sets according to the step 412.

[0402] Optionally, the measurements 306 at the UE 100 for the inter-dependent PDU sets may (e.g., partly) be based on lower layer measurements involving indirect QoS parameters such as noise or a signal-to-noise ratio (SNR), or interference or a signal-to-interference-and-noise ratio (SINR).

[0403] Fig. 17 shows a schematic block diagram for an embodiment of the device 100. The device 100 comprises processing circuitry, e.g., one or more processors 1704 for performing the method 300 and memory 1706 coupled to the processors 1704.

[0404] For example, the memory 1706 may be encoded with instructions that implement at least one of the modules 106 and 110.

[0405] The one or more processors 1704 may be 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, microcode and / or encoded logic operable to provide, either alone or in conjunction with other components of the device 100, such as the memory 1706, wireless device functionality. For example, the one or more processors 1704 may execute instructions stored in the memory 1706. Such functionality may include providing various features and steps discussed herein, including any of the benefits disclosed herein. The expression "the device being operative to perform an action" may denote the device 100 being configured to perform the action.

[0406] As schematically illustrated in Fig. 17, the device 100 may be embodied by a wireless device 1700, e.g., functioning as a radio device or a transmitting UE. The wireless device 1700 comprises a wireless (e.g., radio) interface 1702 coupled to the device 100 for radio communication with one or more receiving stations, e.g., functioning as a receiving base station or a receiving UE.

[0407] Fig. 18 shows a schematic block diagram for an embodiment of the device 200. The device 200 comprises processing circuitry, e.g., one or more processors 1804 for performing the method 400 and memory 1806 coupled to the processors 1804.

[0408] For example, the memory 1806 may be encoded with instructions that implement at least one of the modules 202, 204 and 206.

[0409] The one or more processors 1804 may be 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, microcode and / or encoded logic operable to provide, either alone or in conjunction with other components of the device 200, such as the memory 1806, network node functionality. For example, the one or more processors 1804 may execute instructions stored in the memory 1806. Such functionality may include providing various features and steps discussed herein, including any of the benefits disclosed herein. The expression "the device being operative to perform an action" may denote the device 200 being configured to perform the action.

[0410] As schematically illustrated in Fig. 18, the device 200 may be embodied by a network node 1800, e.g., functioning as a gNB or a receiving UE. The network node 1800 comprises a wireless (e.g., radio) interface 1802 coupled to the device 200 for radio communication with one or more transmitting stations, e.g., functioning as a transmitting base station or a transmitting UE.

[0411] With reference to Fig. 19, in accordance with an embodiment, a communication system 1900 includes a telecommunication network 1910, such as a 3GPP-type cellular network, which comprises an access network 1911, such as a radio access network, and a core network 1914. The access network 1911 comprises a plurality of base stations 1912a, 1912b, 1912c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 1913a, 1913b, 1913c. Each base station 1912a, 1912b, 1912c is connectable to the core network 1914 over a wired or wireless connection 1915. A first user equipment (UE) 1991 located in coverage area 1913c is configured to wirelessly connect to, or be paged by, the corresponding base station 1912c. A second UE 1992 in coverage area 1913a is wirelessly connectable to the corresponding base station 1912a. While a plurality of UEs 1991, 1992 are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station 1912.

[0412] Any of the base stations 1912 may embody the device 200. Alternatively or in addition, any of the UEs 1991 and 1992 may embody the device 100.

[0413] The telecommunication network 1910 is itself connected to a host computer 1930, which may be embodied in the hardware and / or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm. The host computer 1930 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider. The connections 1921, 1922 between the telecommunication network 1910 and the host computer 1930 may extend directly from the core network 1914 to the host computer 1930 or may go via an optional intermediate network 1920. The intermediate network 1920 may be one of, or a combination of more than one of, a public, private or hosted network; the intermediate network 1920, if any, may be a backbone network or the Internet; in particular, the intermediate network 1920 may comprise two or more sub-networks (not shown).

[0414] The communication system 1900 of Fig. 19 as a whole enables connectivity between one of the connected UEs 1991, 1992 and the host computer 1930. The connectivity may be described as an over-the-top (OTT) connection 1950. The host computer 1930 and the connected UEs 1991, 1992 are configured to communicate data and / or signaling via the OTT connection 1950, using the access network 1911, the core network 1914, any intermediate network 1920 and possible further infrastructure (not shown) as intermediaries. The OTT connection 1950 may be transparent in the sense that the participating communication devices through which the OTT connection 1950 passes are unaware of routing of uplink and downlink communications. For example, a base station 1912 need not be informed about the past routing of an incoming downlink communication with data originating from a host computer 1930 to be forwarded (e.g., handed over) to a connected UE 1991. Similarly, the base station 1912 need not be aware of the future routing of an outgoing uplink communication originating from the UE 1991 towards the host computer 1930. By virtue of the method 300 being performed by any one of the UEs 1991 or 1992 and / or the method 400 being performed by any one of the base stations 1912, the performance or range of the OTT connection 1950 can be improved, e.g., in terms of increased throughput and / or reduced latency. More specifically, the host computer 1930 may indicate to the RAN 510 or the radio device 100 (e.g. a relay radio device or a remote radio device), optionally on an application layer, the QoS of the traffic.

[0415] Example implementations, in accordance with an embodiment of the UE, base station and host computer discussed in the preceding paragraphs, will now be described with reference to Fig. 20. In a communication system 2000, a host computer 2010 comprises hardware 2015 including a communication interface 2016 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of the communication system 2000. The host computer 2010 further comprises processing circuitry 2018, which may have storage and / or processing capabilities. In particular, the processing circuitry 2018 may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. The host computer 2010 further comprises software 2011, which is stored in or accessible by the host computer 2010 and executable by the processing circuitry 2018. The software 2011 includes a host application 2012. The host application 2012 may be operable to provide a service to a remote user, such as a UE 2030 connecting via an OTT connection 2050 terminating at the UE 2030 and the host computer 2010. In providing the service to the remote user, the host application 2012 may provide user data, which is transmitted using the OTT connection 2050. The user data may depend on the location of the UE 2030. The user data may comprise auxiliary information or precision advertisements (also: ads) delivered to the UE 2030. The location may be reported by the UE 2030 to the host computer, e.g., using the OTT connection 2050, and / or by the base station 2020, e.g., using a connection 2060.

[0416] The communication system 2000 further includes a base station 2020 provided in a telecommunication system and comprising hardware 2025 enabling it to communicate with the host computer 2010 and with the UE 2030. The hardware 2025 may include a communication interface 2026 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of the communication system 2000, as well as a radio interface 2027 for setting up and maintaining at least a wireless connection 2070 with a UE 2030 located in a coverage area (not shown in Fig. 20) served by the base station 2020. The communication interface 2026 may be configured to facilitate a connection 2060 to the host computer 2010. The connection 2060 may be direct, or it may pass through a core network (not shown in Fig. 20) of the telecommunication system and / or through one or more intermediate networks outside the telecommunication system. In the embodiment shown, the hardware 2025 of the base station 2020 further includes processing circuitry 2028, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. The base station 2020 further has software 2021 stored internally or accessible via an external connection.

[0417] The communication system 2000 further includes the UE 2030 already referred to. Its hardware 2035 may include a radio interface 2037 configured to set up and maintain a wireless connection 2070 with a base station serving a coverage area in which the UE 2030 is currently located. The hardware 2035 of the UE 2030 further includes processing circuitry 2038, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. The UE 2030 further comprises software 2031, which is stored in or accessible by the UE 2030 and executable by the processing circuitry 2038. The software 2031 includes a client application 2032. The client application 2032 may be operable to provide a service to a human or non-human user via the UE 2030, with the support of the host computer 2010. In the host computer 2010, an executing host application 2012 may communicate with the executing client application 2032 via the OTT connection 2050 terminating at the UE 2030 and the host computer 2010. In providing the service to the user, the client application 2032 may receive request data from the host application 2012 and provide user data in response to the request data. The OTT connection 2050 may transfer both the request data and the user data. The client application 2032 may interact with the user to generate the user data that it provides.

[0418] It is noted that the host computer 2010, base station 2020 and UE 2030 illustrated in Fig. 20 may be identical to the host computer 1930, one of the base stations 1912a, 1912b, 1912c and one of the UEs 1991, 1992 of Fig. 19, respectively. This is to say, the inner workings of these entities may be as shown in Fig. 20, and, independently, the surrounding network topology may be that of Fig. 19. In Fig. 20, the OTT connection 2050 has been drawn abstractly to illustrate the communication between the host computer 2010 and the UE 2030 via the base station 2020, without explicit reference to any intermediary devices and the precise routing of messages via these devices. Network infrastructure may determine the routing, which it may be configured to hide from the UE 2030 or from the service provider operating the host computer 2010, or both. While the OTT connection 2050 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).

[0419] The wireless connection 2070 between the UE 2030 and the base station 2020 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to the UE 2030 using the OTT connection 2050, in which the wireless connection 2070 forms the last segment. More precisely, the teachings of these embodiments may reduce the latency and improve the data rate and thereby provide benefits such as better responsiveness and improved QoS.

[0420] A measurement procedure may be provided for the purpose of monitoring data rate, latency, QoS and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection 2050 between the host computer 2010 and UE 2030, in response to variations in the measurement results. The measurement procedure and / or the network functionality for reconfiguring the OTT connection 2050 may be implemented in the software 2011 of the host computer 2010 or in the software 2031 of the UE 2030, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which the OTT connection 2050 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 2011, 2031 may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 2050 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect the base station 2020, and it may be unknown or imperceptible to the base station 2020. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling facilitating the host computer's 2010 measurements of throughput, propagation times, latency and the like. The measurements may be implemented in that the software 2011, 2031 causes messages to be transmitted, in particular empty or "dummy" messages, using the OTT connection 2050 while it monitors propagation times, errors etc.

[0421] Fig. 21 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to Figs. 19 and 20. For simplicity of the present disclosure, only drawing references to Fig. 21 will be included in this paragraph. In a first step 2110 of the method, the host computer provides user data. In an optional substep 2111 of the first step 2110, the host computer provides the user data by executing a host application. In a second step 2120, the host computer initiates a transmission carrying the user data to the UE. In an optional third step 2130, the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In an optional fourth step 2140, the UE executes a client application associated with the host application executed by the host computer.

[0422] Fig. 22 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to Figs. 19 and 20. For simplicity of the present disclosure, only drawing references to Fig. 22 will be included in this paragraph. In a first step 2210 of the method, the host computer provides user data. In an optional substep (not shown) the host computer provides the user data by executing a host application. In a second step 2220, the host computer initiates a transmission carrying the user data to the UE. The transmission may pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure. In an optional third step 2230, the UE receives the user data carried in the transmission.

[0423] Without feedback from the UE or knowledge of a relationship between PDU sets, the conventional network cannot or can hardly know the QoS impacts of handling multi-modal PDU sets. As has become apparent from above description, at least some embodiments of the technique enable the gNB to rapidly adapt radio resource management to dynamic application requirements. Reference signs have the technical meaning specified in the context of the respective description or may other have the following meaning.

[0424] 10 Existing UE

[0425] 20 Existing gNB

[0426] 50 Existing downlink architecture for a telecommunication network

[0427] 100 Wireless device for handling PDU sets, e.g. user equipment (UE)

[0428] 106 PDU Set Measurement Module

[0429] 110 Report Transmission Module

[0430] 200 Network node for handling PDU sets, e.g. gNB

[0431] 201 Cell or beam of the network node

[0432] 210 Report Reception Module

[0433] 212 PDU Set Scheduling Module

[0434] 300 First method aspect of handling a PDU set

[0435] 302 Sending capability message step

[0436] 304 Receiving configuration message step

[0437] 306 Obtaining inter-dependency step

[0438] 308 Determining criterion step

[0439] 310 Sending report message step

[0440] 400 Second method aspect of handling a PDU set

[0441] 402 Receiving capability message step

[0442] 404 Sending configuration message step

[0443] 410 Receiving report message step

[0444] 412 Scheduling step, e.g. changing DRP-QFI mapping

[0445] 500 Telecommunication network

[0446] 502 Capability message

[0447] 504 Configuration message

[0448] 506 Report message, e.g. indicative of PDU Set Delay Budget (PSDB), PDU Set Error Rate (PSER), or PDU Set Importance (PSI)

[0449] 510 Access network (AN)

[0450] 520 Core network (CN), e.g. 5G Core Network (5GC) 522 User plane function (UPF) of the CN

[0451] 702 PDU Session

[0452] 704 N3 Tunnel

[0453] 710 Packet Data Convergence Protocol (PDCP) (sub-)layer

[0454] 712 PDCP entity

[0455] 714 Data Radio Bearer (DRB)

[0456] 720 Service Data Adaptation Protocol (SDAP) (sub-)layer

[0457] 722 SDAP entity

[0458] 724 Quality of Service (QoS) flow, e.g. QoS flow identifier (QFI)

[0459] 726 Service

[0460] 728 Sensors

[0461] 730 Sources of data

[0462] 732 Multi-modal data stream

[0463] 734 Data types (e.g., data flows) of a multi-modal data stream

[0464] 750 Packet data unit set (PDU set)

[0465] 1700 Wireless device embodiment

[0466] 1704 Computing devices of the wireless device

[0467] 1706 Computer-readable recording medium of the wireless device

[0468] 1800 Network node embodiment

[0469] 1804 Computing devices of the network node

[0470] 1806 Computer-readable recording medium of the wireless device

[0471] 1900 Communication system embodiment, e.g. telecommunication network

[0472] 1910 Cellular or ad hoc radio network as an example of the AN

[0473] 1912 Network node embodiment

[0474] 1930 Host computer

[0475] 1940 Communication interface

[0476] 1991 Wireless device embodiment

[0477] 1992 A wireless device embodiment

[0478] 2000 Communication system embodiment, e.g. telecommunication network

[0479] 2010 Host computer

[0480] 2012 Host application, e.g. receiving the PDU set

[0481] 2016 Communication interface 2018 Processing circuitry

[0482] 2020 Network node embodiment

[0483] 2028 Processing circuitry

[0484] 2030 Wireless device embodiment

[0485] 2032 Client application, e.g. generating the PDU set, e.g. extended Reality (XR)

[0486] 2037 Radio interface

[0487] 2038 Processing circuitry

[0488] Many advantages of the present invention will be fully understood from the foregoing description, and it will be apparent that various changes may be made in the form, construction and arrangement of the units and devices without departing from the scope of the invention and / or without sacrificing all of its advantages. Since the invention can be varied in many ways, it will be recognized that the invention should be limited only by the scope of the following claims.

Claims

List of Claims1. A method (300) performed by a wireless device, WD (100; 1700; 1991; 1992; 2030), wirelessly connected or connectable to an access network, AN (510), the method (300) comprising or initiating: measuring (306) at the WD (100; 1700; 1991; 1992; 2030) at least one combined quality of service, QoS, parameter, wherein each of the at least one combined QoS parameter is measured (306) for a combination of at least two PDU sets (750) in an uplink towards the AN (510), wherein the at least two PDU sets (750) are mutually inter-dependent (760); and sending (310), to the AN (510), a report message (506) indicative of the measured (306) at least one combined QoS parameter.

2. The method (300) of claim 1, wherein each of the at least two PDU sets (750) corresponds to a distinctive sensor (728) or data source (730) or data type (734) or a distinctive QoS flow (724), optionally a distinctive flow identifier within a QoS flow (724); and / or wherein each of the at least two PDU sets (750) corresponds to a distinctive data radio bearer, DRBs (714), optionally a distinctive flow identifier within a DRB (714); and / or wherein the combination of the at least two PDU sets (750) corresponds to and / or originates from one service.

3. The method (300) of claim 1 or 2, wherein the inter-dependency (760) of the at least two PDU sets (750) is obtained at the WD (100; 1700; 1991; 1992; 2030).

4. The method (300) of any one of claims 1 to 3, wherein the combined QoS parameter relates to the at least two PDU sets (750) in combination, and / or wherein the combined QoS parameter is not indicative of individual PDU sets (750) of the at least two PDU sets (750), and / or wherein the combined QoS parameter is not indicative of individual PDUs in the at least two PDU sets (750).

5. The method (300) of any one of claims 1 to 4, wherein the report message (506) is indicative of a change and / or statistical information of the measured (306) at least one combined QoS parameter for the at least two PDU sets (750),optionally wherein the report message (506) is indicative of at least one of an absolute or relative decrease per time period or since the last report message (506), an absolute or relative increase per time period or since the last report message (506), a minimum, a maximum, a median, an average, a variance, and a probability distribution of the measured (306) at least one combined QoS parameter for the at least two PDU sets (750) or a time sequence of thereof.

6. The method (300) of any one of claims 1 to 5, wherein the combined QoS parameter is a function of and / or comprises at least two PDU set QoS parameters for each or at least two of the inter-dependent at least two PDU sets (750); and / or wherein the combined QoS parameter comprises one or more differences between two or more PDU set QoS parameters, each of the two or more PDU set QoS parameters relating to a different one of the inter-dependent at least two PDU sets (750); and / or wherein the combined QoS parameter comprises a list of PDU set QoS parameters, each of the PDU set QoS parameters in the list relating to a different one of the inter-dependent at least two PDU sets (750).

7. The method (300) of claim 6, wherein the PDU set QoS parameters, optionally for each of the inter-dependent at least two PDU sets (750), comprises at least one of: a PDU set error rate, PSER, of the respective PDU set (750) among the interdependent at least two PDU sets (750); a PDU set delay budget, PSDB, of the respective PDU set (750) among the inter-dependent at least two PDU sets (750); a PDU set integrated handling information, PSIHI, of the respective PDU set (750) among the inter-dependent at least two PDU sets (750); a latency of the respective PDU set (750) among the inter-dependent at least two PDU sets (750); a jitter of respective PDU set (750) among the inter-dependent at least two PDU sets (750); a PDU set loss rate of the respective PDU set (750) among the interdependent at least two PDU sets (750); a bit rate of respective PDU set (750) among the inter-dependent at least two PDU sets (750); an indicator of fulfilment of a guaranteed flow bit rate, GFBR, of the respective PDU set (750) among the inter-dependent at least two PDU sets (750);an indicator of fulfilment of a maximum flow bit rate, MFBR, of the respective PDU set (750) among the inter-dependent at least two PDU sets (750); a PDU set (750) queued time of the respective PDU set (750) among the inter-dependent at least two PDU sets (750); a PDU set (750) importance, PSI, of the respective PDU set (750) for the inter-dependent at least two PDU sets (750); a PDU set (750) dropping ration of the respective PDU set (750) among the inter-dependent at least two PDU sets (750); and a PDU set (750) priority level of the respective PDU set (750) among the inter-dependent at least two PDU sets (750).

8. The method (300) of any one of claims 1 to 7, wherein the combined QoS parameter comprises at least one of: a combined PDU set error rate, PSER, of the inter-dependent at least two PDU sets (750); a combined PDU set delay budget, PSDB, of the inter-dependent at least two PDU sets (750); a combined PDU set integrated handling information, PSIHI, of the interdependent at least two PDU sets (750); a combined latency of the inter-dependent at least two PDU sets (750); a combined jitter of the inter-dependent at least two PDU sets (750); a combined PDU set loss rate of the respective PDU set (750) among the inter-dependent at least two PDU sets (750); a combined bit rate of the inter-dependent at least two PDU sets (750); an indicator of combined fulfilment of a guaranteed flow bit rate, GFBR, of the inter-dependent at least two PDU sets (750); an indicator of combined fulfilment of a maximum flow bit rate, MFBR, of the inter-dependent at least two PDU sets (750); a combined PDU set (750) queued time of the inter-dependent at least two PDU sets (750); a combined PDU set (750) importance, PSI, of the inter-dependent at least two PDU sets (750); a combined PDU set (750) dropping ration of the inter-dependent at least two PDU sets (750); and a combined PDU set (750) priority level of the inter-dependent at least two PDU sets (750).

9. The method (300) of any one of claims 1 to 8, further comprising or initiating: determining (308) whether the measured (306) at least one combined QoS parameter for the combination of the at least two PDU sets (750) fulfils a predefined criterion, optionally wherein the report message (506) is indicative of whether or not the predefined criterion is fulfilled and / or wherein the sending (310) of the report message (506) is triggered if the predefined criterion is not fulfilled.

10. The method (300) of any one of claims 1 to 9, further comprising or initiating: sending (302) a capability message (502) to the AN (510), optionally to a network node (200; 1800; 1912; 2020) of the AN (510), optionally wherein the capability message (502) is indicative of at least one of: a capability of the WD (100; 1700; 1991; 1992; 2030) to measure (306) the at least one combined QoS parameter for the combined at least two PDU sets (750) in the uplink towards the AN (510); a capability of the WD (100; 1700; 1991; 1992; 2030) to obtain the at least one inter-dependency (760) between the at least two combined PDU sets (750); a capability of the WD (100; 1700; 1991; 1992; 2030) to report (310) a result of the measurement (306) of the at least one combined QoS parameter for the combined at least two PDU sets (750) to the AN (510); an inter-dependency criterion for determining the inter-dependency (760) of the at least two PDU sets (750); one or more PDU set QoS parameters of the at least two PDU sets (750) in the uplink towards the AN (510), which the WD (100; 1700; 1991; 1992; 2030) is capable of measuring (306) and / or sending (310); one or more combined QoS parameters of the combined at least two PDU sets (750) in the uplink towards the AN (510), which the WD (100; 1700; 1991; 1992; 2030) is capable of measuring (306) and / or sending (310); a physical layer information of the WD (100; 1700; 1991; 1992; 2030); and a feature set indicator, optionally comprising radio protocol information.

11. The method (300) of any one of claims 1 to 10, further comprising or initiating:receiving (304) a configuration message (504) for the measuring (306) or the sending (310) from the AN (510), optionally from a network node (200; 1800; 1912; 2020) of the AN (510), and / or from a core network (520) serving the AN (510), optionally the configuration message (504) being indicative of at least one of: the inter-dependency (760) between the at least two PDU sets (750); the inter-dependency criterion for determining the inter-dependency (760) between the at least two PDU sets (750); the inter-dependent at least two PDU sets (750); one or more PDU set QoS parameters to be measured for the at least two PDU sets (750) and / or to be combined for the measuring (306) of the at least one combined QoS parameter; the at least one combined QoS parameter to be measured (306) for the at least two PDU sets (750); the predefined criterion, optionally a threshold value for the combined QoS parameter or a threshold value for the delay; an Internet Protocol flow, IP flow, associated with the at least two PDU sets (750); a QoS flow (724), optionally a QoS flow identifier, QFIs, associated with the at least two PDU sets (750); a data radio bearer, DRB (714), associated with the at least two PDU sets (750);PDU set identifiers of the at least two PDU sets (750); a cross-PDU set importance, cross-PSI, associated with the at least two PDU sets (750) and / or indicative of an importance level of the inter-dependency (760); a set of QoS flow identifiers, QFIs, associated with the at least two PDU sets (750); a set of DRB indexes associated with the at least two PDU sets (750); an obtaining mode for the obtaining of the inter-dependency (760) in the WD (100; 1700; 1991; 1992; 2030); a measuring mode of the measurement (306) of at least one QoS parameter of the at least two PDU sets (750); a reporting mode for the sending (310) of the report message (506); an obtainment window for the obtaining of the inter-dependency (760) at the WD (100; 1700; 1991; 1992; 2030) and / or for the measuring (306) of the at least one combined QoS parameter of the inter-dependent (760) at least two PDU sets (750) at the WD (100; 1700; 1991; 1992; 2030);a periodicity for the measuring (306) the at least one QoS parameter and / or the obtaining of the inter-dependency (760) and / or the sending (310) of the report message; and a deadline for the sending (310) of the report message (506).

12. The method (300) of claims 11, wherein a measuring mode for the measuring (306) of the at least one combined QoS parameter of the at least two PDU sets (750) and / or an obtaining mode for obtaining the inter-dependency (760) of the at least two PDU sets (750) and / or a reporting mode for the sending (310) of the report message (506) comprises at least one of: a periodic measuring (306), optionally a periodic determining (308), and / or a periodic obtaining and / or a periodic report message (506); an aperiodic measuring (306), optionally an aperiodic determining (308), and / or an aperiodic obtaining and / or an aperiodic report message (506); an event-triggered measuring (306), optionally an event-triggered determining (308), and / or an event-triggered obtaining, and / or an event-triggered report message (506).

13. The method (300) of any one of claims 9 to 12, wherein the predefined criterion comprises a threshold value for a threshold of the at least one combined QoS parameter, and / or a threshold value for a threshold of a variance of the at least one combined QoS parameter.

14. The method (300) of any one of claims 1 to 13, wherein the report message (506) uses or comprises at least one of Radio Resource control, RRC, signaling; UE Assistance Information, UAI; a Packet Data Convergence Protocol, PDCP, control PDU; and a Service Data Adaptation Protocol, SDAP, control PDU; and / or wherein the sending (310) comprises sending the report message (506) in a control plane, CP, data unit using an RRC layer, a PDCP layer and / or an SDAP layer.

15. The method (300) of any one of claims 1 to 14, wherein the report message (506) is sent (310) to a network node (200; 1800; 1912; 2020) of the AN (510), optionally to a network node (200; 1800; 1912; 2020) serving the WD (100; 1700; 1991; 1992; 2030).

16. The method (300) of any one of claims 1 to 15, wherein the at least two PDU sets (750) belong to different data flows and / or correspond to at least two of the following data flows:a video flow; an audio flow; one or more environmental information flow; a pose flow; a gesture flow; and a haptic flow.

17. The method (300) of any one of claims 1 to 16, wherein the at least two PDU sets (750), optionally the at least two of the QoS flows (724) or DRBs (714), are inter-dependent (760) because of at least one of: a synchronization requirement between the at least two PDU sets (750), optionally between the at least two of the QoS flows (724) or DRBs (714); a common internet protocol, IP, address and / or a common port number and / or a common medium access control, MAC, address of the at least two PDU sets (750), optionally of the at least two of the QoS flows (724) or DRBs (714); a correlation between the at least two PDU sets (750), optionally between the at least two of the QoS flows (724) or DRBs (714); and the service corresponding to or associated with the at least two PDU sets (750), optionally corresponding to or associated with the at least two of the QoS flows (724) or DRBs (714).

18. The method (300) of any one of claims 1 to 17, wherein the at least two PDU sets (750) are received by an application layer of the WD (100; 1700; 1991; 1992; 2030) and / or received from an application layer, optionally an application server, through a network node (200; 1800; 1912; 2020) of the AN (510); and / or wherein the at least two PDU sets (750) are sent from an application layer of the WD (100; 1700; 1991; 1992; 2030) and / or sent to an application layer, optionally an application server, through a network node (200; 1800; 1912; 2020) of the AN (510).

19. A method (400) performed by a network node (200; 1800; 1912; 2020) of an access network, AN (510), the method (400) comprising or initiating: receiving (410) a report message (506) from a WD (100; 1700; 1991; 1992; 2030) wirelessly connected to the AN (510), wherein the report message (506) is indicative of at least one combined QoS parameter for a combination of at least two PDU sets (750) measured at the WD (100; 1700; 1991; 1992; 2030) in an uplink towards the AN (510), wherein the at least two PDU sets (750) are mutually interdependent (760); andscheduling (412) resources for the uplink of the WD (100; 1700; 1991; 1992; 2030) based on the received (410) report message (506).

20. The method (400) of claim 19, wherein the scheduling (412) of the resources comprises at least one of: adjusting a resource allocation of the at least two PDU sets (750), optionally if the received (410) report message (506) is indicative of one of the at least two PDU sets (750) fulfilling its QoS requirement while another one of the at least two PDU sets (750) does not fulfill its QoS requirement, and / or wherein the resource allocation for the WD (100; 1700; 1991; 1992; 2030) is adjusted by changing the resource allocation of temporal resources, frequency resources and / or spatial resources of the AN (510) and / or a transmit power control setting; configuring one or more functions of the AN (510), optionally of the network node (200; 1800; 1912; 2020), based on the received (410) report message (506), optionally Hybrid Automatic Repeat Request (HARQ) settings are reconfigured or a modulation and coding scheme, MCS, is reconfigured or a retransmission strategy is reconfigured; updating PDU set handling at the AN (510) for the inter-dependent at least two PDU sets; adapting to a dynamic traffic patterns, optionally wherein the AN (510) uses the received (410) report message (506) as dynamic QoS performance information to adapt to changing traffic patterns and / or wherein a service or an application underlying the at least two PDU sets uses variable bit rates or burst-like traffic; and sending a feedback to a core network (520) serving the AN (510), optionally wherein sending the feedback to the core network (520) is indicative of a QoS performance of the service based on the combination of the at least two PDU sets and the received (410) report message (506), preferably to update policies and / or rules for traffic management and / or PDU session establishment.

21. The method (400) of claim 19 or 20, further comprising or initiating: receiving (402) a capability message (502) from the WD (100; 1700; 1991;1992; 2030), optionally wherein the capability message (502) is indicative of at least one of: a capability of the WD (100; 1700; 1991; 1992; 2030) to measure (306) the at least one combined QoS parameter for the combined at least two PDU sets (750) in the uplink towards the AN (510);a capability of the WD (100; 1700; 1991; 1992; 2030) to obtain the at least one inter-dependency (760) between the at least two combined PDU sets (750); a capability of the WD (100; 1700; 1991; 1992; 2030) to report (310) a result of the measurement (306) of the at least one combined QoS parameter for the combined at least two PDU sets (750) to the AN (510); an inter-dependency criterion for determining the inter-dependency (760) of the at least two PDU sets (750); one or more PDU set QoS parameters of the at least two PDU sets (750) in the uplink towards the AN (510), which the WD (100; 1700; 1991; 1992; 2030) is capable of measuring (306) and / or sending (310); one or more combined QoS parameters of the combined at least two PDU sets (750) in the uplink towards the AN (510), which the WD (100; 1700; 1991; 1992; 2030) is capable of measuring (306) and / or sending (310); a physical layer information of the WD (100; 1700; 1991; 1992; 2030); and a feature set indicator, optionally comprising radio protocol information.

22. The method (400) of any one of claims 19 to 21, further comprising or initiating: sending (404) a configuration message (504) to the WD (100; 1700; 1991;1992; 2030), optionally the configuration message (504) being indicative of at least one of: an inter-dependency (760) between the at least two PDU sets (750); an inter-dependency criterion for determining the inter-dependency (760) between the at least two PDU sets (750); the inter-dependent at least two PDU sets (750); one or more PDU set QoS parameters to be measured for the at least two PDU sets (750) and / or to be combined for the measuring (306) of the at least one combined QoS parameter; the at least one combined QoS parameter to be measured (306) for the at least two PDU sets (750); the predefined criterion, optionally a threshold value for the combined QoS parameter or a threshold value for the delay; an Internet Protocol flow, IP flow, associated with the at least two PDU sets (750); a QoS flow (724), optionally a QoS flow identifier, QFIs, associated with the at least two PDU sets (750);a data radio bearer, DRB (714), associated with the at least two PDU sets(750);PDU set identifiers of the at least two PDU sets (750); a cross-PDU set importance, cross-PSI, associated with the at least two PDU sets (750) and / or indicative of an importance level of the inter-dependency (760); a set of QoS flow identifiers, QFIs, associated with the at least two PDU sets (750); a set of DRB indexes associated with the at least two PDU sets (750); an obtaining mode for the obtaining of the inter-dependency (760) in the WD (100; 1700; 1991; 1992; 2030); a measuring mode of the measurement (306) of at least one QoS parameter of the at least two PDU sets (750); a reporting mode for the sending (310) of the report message (506); an obtainment window for the obtaining of the inter-dependency (760) at the WD (100; 1700; 1991; 1992; 2030) and / or for the measuring (306) of the at least one combined QoS parameter of the inter-dependent (760) at least two PDU sets (750) at the WD (100; 1700; 1991; 1992; 2030); a periodicity for the measuring (306) the at least one QoS parameter and / or the obtaining of the inter-dependency (760) and / or the sending (310) of the report message; and a deadline for the sending (310) of the report message (506).

23. The method (400) of any one of claims 19 to 22, wherein the scheduling (412) comprises: changing a mapping of one or more data radio bearers, DRBs (714), to at least one or two QoS flows or QFIs (724) used by the at least two PDU sets (750) in response to the receiving (410) of the report message (506); and / or changing a mapping of at least one or two QoS flows or QFIs (724) used by the at least two PDU sets (750) to one or more data radio bearers, DRBs (714), in response to the receiving (410) of the report message (506).

24. The method (400) of any one of claims 19 to 23, further comprising the steps or features of any one of claims 2 to 18 or any step corresponding thereto.

25. A computer program product comprising program code portions for performing the steps of any one of the claims 1 to 18 or 19 to 24 when the computer program product is executed on one or more computing devices (1304; 1404), optionally stored on a computer-readable recording medium (1306; 1406).

26. A wireless device, WD (100; 1700; 1991; 1992; 2030), wirelessly connected or connectable to an access network, AN (510), the WD (100; 1700; 1991; 1992; 2030) comprising memory operable to store instructions and processing circuitry operable to execute the instructions, such that the WD (100; 1700; 1991; 1992; 2030) is operable to: measure at the WD (100; 1700; 1991; 1992; 2030) at least one combined quality of service, QoS, parameter, wherein each of the at least one combined QoS parameter is measured for a combination of at least two PDU sets (750) in an uplink towards the AN (510), wherein the at least two PDU sets (750) are mutually inter-dependent (760); and send, to the AN (500), a report message (506) indicative of the measured at least one combined QoS parameter.

27. The WD (100; 1700; 1991; 1992; 2030) of claim 26, further comprising the features or being operable to perform the steps of any one of claims 2 to 18.

28. A wireless device, WD (100; 1700; 1991; 1992; 2030), wirelessly connected or connectable to an access network, AN (510), the WD (100; 1700; 1991; 1992; 2030) being configured to: measure at the WD (100; 1700; 1991; 1992; 2030) at least one combined quality of service, QoS, parameter, wherein each of the at least one combined QoS parameter is measured for a combination of at least two PDU sets (750) in an uplink towards the AN (510), wherein the at least two PDU sets (750) are mutually inter-dependent (760); and send, to the AN (500), a report message (506) indicative of the measured at least one combined QoS parameter.

29. The WD (100; 1700; 1991; 1992; 2030) of claim 28, further comprising the features or being configured to perform the steps of any one of claims 2 to 18.

30. A network node (200; 1800; 1912; 2020) of an access network, AN (510), the network node (200; 1800; 1912; 2020) comprising memory operable to store instructions and processing circuitry operable to execute the instructions, such that the network node (200; 1800; 1912; 2020) is operable to:receive a report message (506) from a WD (100; 1700; 1991; 1992; 2030) wirelessly connected to the AN (510), wherein the report message (506) is indicative of at least one combined QoS parameter for a combination of at least two PDU sets (750) measured at the WD (100; 1700; 1991; 1992; 2030) in an uplink towards the AN (510), wherein the at least two PDU sets (750) are mutually interdependent (760); and schedule resources for the uplink of the WD (100; 1700; 1991; 1992; 2030) based on the received report message (506).

31. The network node (200; 1800; 1912; 2020) of claim 30, further operable to perform any one of the steps of any one of claims 19 to 24.

32. A network node (200; 1800; 1912; 2020) of an access network, AN (510), the network node (200; 1800; 1912; 2020) being configured to: receive a report message (506) from a WD (100; 1700; 1991; 1992; 2030) wirelessly connected to the AN (510), wherein the report message (506) is indicative of at least one combined QoS parameter for a combination of at least two PDU sets (750) measured at the WD (100; 1700; 1991; 1992; 2030) in an uplink towards the AN (510), wherein the at least two PDU sets (750) are mutually interdependent (760); and schedule resources for the uplink of the WD (100; 1700; 1991; 1992; 2030) based on the received report message (506).

33. The network node (200; 1800; 1912; 2020) of claim 32, further configured to perform the steps of any one of claim 20 to 23.

34. A communication system (500; 1900; 2000) including a host computer (1930; 2010) comprising: processing circuitry (2018) configured to provide user data; and a communication interface (2016) configured to forward user data to a cellular or ad hoc radio network (510; 1910) for transmission to a user equipment, UE (100; 1700; 1991; 1992; 2030), wherein the UE (100; 1700; 1991; 1992; 2030) comprises a radio interface (1702; 2037) and processing circuitry (1704; 2038), the processing circuitry (1704; 2038) of the UE (100; 1700; 1991; 1992; 2030) being configured to execute the steps of any one of claims 1 to 18.

35. The communication system (500; 1900; 2000) of claim 34, further including the UE (100; 1700; 1991; 1992; 2030).

36. The communication system (500; 1900; 2000) of claim 34 or 35, wherein the radio network (510; 1910) further comprises a base station (200; 1800; 1912;2020), or a radio device (100; 1700; 1991; 1992; 2030) functioning as a gateway, which is configured to communicate with the UE (100; 1700; 1991; 1992; 2030).

37. The communication system (500; 1900; 2000) of claim 36, wherein the base station (200; 1800; 1912; 2020), or the radio device (100; 1700; 1991; 1992; 2030) functioning as a gateway, comprises processing circuitry (1404; 1628), which is configured to execute the steps of any one of claims 18 to 23.

38. The communication system (500; 1900; 2000) of any one of claims 34 to 37, wherein: the processing circuitry (1804; 2018) of the host computer (1930; 2010) is configured to execute a host application (2012), thereby providing the user data; and the processing circuitry (1704; 2038) of the UE (100; 1700; 1991; 1992;2030) is configured to execute a client application (2032) associated with the host application (2012).

Images