Method, apparatus and computer program

Abstract

There is provided a method performed by a transmitter entity, the method comprising: mapping, based on mapping information, one or more service data flows to a data radio bearer, wherein each of the one or more service data flows comprises a plurality of data packets; and transmitting, to a receiver entity, the data packets comprised in the one or more service data flows via the data radio bearer to which the one or more service data flows are mapped.

Description

METHOD, APPARATUS AND COMPUTER PROGRAMRELATED APPLICATIONS

[0001] This patent application claims the benefit of priority of United Kingdom Patent Application No. 2401765.9filed February 9, 2024, which is hereby incorporated by reference as if reproduced in its entirety.TECHNICAL FIELD

[0002] Various example embodiments of this disclosure relate to a method, apparatus, system and computer program and in particular but not exclusively to mapping data packets comprised in one or more service data flows to a data radio bearer.BACKGROUNDA communication network can be seen as a facility that enables communications between two or more communication devices or provides communication devices access to a data network. A mobile or wireless communication network is one example of a communication network. A communication device may be provided with a service by an application server.

[0003] Such communication networks operate in accordance with standards such as those provided by 3GPP (Third Generation Partnership Project) or ETSI (European Telecommunications Standards Institute). Examples of standards provided by 3GPP are the so-called 3GPP standards for cellular technology generations, such as 3GPP standards for 4G technology and 3GPP standards for 5G technology.SUMMARY

[0004] Some example embodiments of this disclosure will be described with respect to certain aspects. These aspects are not intended to indicate key or essential features of the embodiments of this disclosure, nor are they intended to be used to limit the scope of thereof. Other features, aspects, and elements will be readily apparent to a person skilled in the art in view of this disclosure.

[0005] According to an aspect, there is provided a transmitter entity comprising means for: mapping, based on mapping information, one or more service data flows to a data radio bearer, wherein each of the one or more service data flows comprises a plurality of data packets; and transmitting, to a receiver entity, the data packets comprised in the one or more service data flows via the data radio bearer to which the one or more service data flows are mapped.

[0006] The mapping information may comprise: one or more packet filter sets or one or more packet detection rules, each packet filter set or packet detection rule defining one or more characteristics of a service data flow; a data radio bearer identifier associated witheach packet filter set or packet detection rule; and a precedence value associated with each packet filter set or packet detection rule.

[0007] The mapping may comprise: determining that one or more characteristics of the data packets of a service data flow match the one or more characteristics defined by one of the one or more packet filter sets or one of the one or more packet detection rules comprised in the mapping information; and based on the determining, mapping the data packets of the service data flow to the data radio bearer corresponding to the data radio bearer identifier associated with the one of the one or more packet filter sets or the one of the one or more packet detection rules comprised in the mapping information.

[0008] The mapping information may comprise a plurality of packet filter sets or a plurality of packet detection rules, and wherein the plurality of packet filter sets or the plurality of packet detection rules may be applied in an order according to the precedence values associated with the plurality of packet filter sets or the plurality of packet detection rules comprised in the mapping information.

[0009] The mapping may comprise inserting, into each data packet, a header comprising the data radio bearer identifier of the data radio bearer to which the service data flow comprising packet is mapped.

[0010] The means may be further for: receiving, from a control plane network function, the mapping information.

[0011] The mapping may comprise mapping a first service data flow and a second service data flow to a same data radio bearer, wherein the first service data flow and second service data flow have the same or similar characteristics.

[0012] The mapping may comprise mapping a third service data flow and a fourth service data flow to different data radio bearers, wherein the third service data flow and fourth service data flow have different characteristics.

[0013] The transmitter entity may be an access user plane function and the receiver entity may be a user equipment.

[0014] The mapping information may comprise the one or more packet detection rules, a data radio bearer identifier associated each packet detection rule; and a precedence value associated with each packet detection rule.

[0015] The mapping may comprise receiving, from a control plane network function, information indicating that reflective service data flow to data radio bearer mapping is enabled for the user equipment; and inserting, into each of the plurality of data packets, a header comprising an indicator for enabling reflective service data flow to data radio bearer mapping at the user equipment.

[0016] The transmitter entity may be a user equipment and the receiver entity may be an access user plane function.

[0017] The mapping information may be comprised in one or more quality of service rules, wherein each quality of service rule may comprise a packet filter set, a data radio bearer identifier associated a packet filter set; and a precedence value associated with the packet filter set.

[0018] The means may be further for: receiving, from the access user plane function, one or more data packets comprising an indicator for enabling reflective service data flow to data radio bearer mapping at the user equipment; wherein the mapping may comprise applying one or more user equipment derived quality of service rules based on receiving the indicator for enabling reflective service data flow to data radio bearer mapping at the user equipment.

[0019] The means may be further for: based on receiving the one or more data packets comprising the indicator for enabling reflective service data flow to data radio bearer mapping, determining whether a user equipment derived quality of service rule comprising mapping information with a packet filter set defining characteristics corresponding to the characteristics of the received one or more data packet exists; and based on the determining whether the user equipment derived quality of service rule comprising the mapping information with the packet filter set defining characteristics corresponding to the characteristics of the received one or more data packets exists, creating or updating the user equipment derived quality of service rule comprising mapping information with a packet filter set defining characteristics corresponding to the characteristics of the received one or more data packets.

[0020] In response to determining that no user equipment derived quality of service rule comprising the mapping information with the packet filter set defining characteristics corresponding to the characteristics of the received one or more data packets exists, the creating or updating may comprise: creating a new user equipment derived quality of service rule comprising mapping information with a packet filter set defining characteristics corresponding to the characteristics of the received one or more data packets; and starting a timer associated with the new user equipment derived quality of service rule.

[0021] In response to determining that a user equipment derived quality of service rule comprising the mapping information with the packet filter set defining characteristics corresponding to the characteristics of the received one or more data packets exists, the creating or updating may comprise: restarting a timer associated with the user equipment derived quality of service rule comprising the mapping information with the packet filter set defining characteristics corresponding to the characteristics of the received one or moredata packets; determining whether the data radio bearer identifier associated with the received one or more data packets is different from the data radio bearer identifier associated with the user equipment derived quality of service rule comprising the mapping information with the packet filter set defining characteristics corresponding to the characteristics of the received one or more data packets; and updating the data radio bearer identifier associated with the user equipment derived quality of service rule comprising the mapping information with the packet filter set defining characteristics corresponding to the characteristics of the received one or more data packets based on the determining.

[0022] The means may be further for: determining that the timer associated with the user equipment quality of service mapping rule has expired; and in response to determining that the timer has expired, deleting the user equipment derived quality of service rule.

[0023] According to an aspect, there is provided a transmitter entity comprising at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the transmitter entity at least to: map, based on mapping information, one or more service data flows to a data radio bearer, wherein each of the one or more service data flows comprises a plurality of data packets; and transmit, to a receiver entity, the data packets comprised in the one or more service data flows via the data radio bearer to which the one or more service data flows are mapped.

[0024] The mapping information may comprise: one or more packet filter sets or one or more packet detection rules, each packet filter set or packet detection rule defining one or more characteristics of a service data flow; a data radio bearer identifier associated with each packet filter set or packet detection rule; and a precedence value associated with each packet filter set or packet detection rule.

[0025] The at least one processor may be configured to cause the transmitter entity to: determine that one or more characteristics of the data packets of a service data flow match the one or more characteristics defined by one of the one or more packet filter sets or one of the one or more packet detection rules comprised in the mapping information; and based on the determining, map the data packets of the service data flow to the data radio bearer corresponding to the data radio bearer identifier associated with the one of the one or more packet filter sets or the one of the one or more packet detection rules comprised in the mapping information.

[0026] The mapping information may comprise a plurality of packet filter sets or a plurality of packet detection rules, and wherein the plurality of packet filter sets or the plurality of packet detection rules may be applied in an order according to the precedence values associated with the plurality of packet filter sets or the plurality of packet detection rules comprised in the mapping information.

[0027] The at least one processor may be configured to cause the transmitter entity to: insert, into each data packet, a header comprising the data radio bearer identifier of the data radio bearer to which the service data flow comprising packet is mapped.

[0028] The at least one processor may be configured to cause the transmitter entity to: receive, from a control plane network function, the mapping information.

[0029] The at least one processor may be configured to cause the transmitter entity to map a first service data flow and a second service data flow to a same data radio bearer, wherein the first service data flow and second service data flow have the same or similar characteristics.

[0030] The at least one processor may be configured to cause the transmitter entity to map a third service data flow and a fourth service data flow to different data radio bearers, wherein the third service data flow and fourth service data flow have different characteristics.

[0031] The transmitter entity may be an access user plane function and the receiver entity may be a user equipment.

[0032] The mapping information may comprise the one or more packet detection rules, a data radio bearer identifier associated each packet detection rule; and a precedence value associated with each packet detection rule.

[0033] The at least one processor may be configured to cause the transmitter entity to: receive, from a control plane network function, information indicating that reflective service data flow to data radio bearer mapping is enabled for the user equipment; and insert, into each of the plurality of data packets, a header comprising an indicator for enabling reflective service data flow to data radio bearer mapping at the user equipment.

[0034] The transmitter entity may be a user equipment and the receiver entity may be an access user plane function.

[0035] The mapping information may be comprised in one or more quality of service rules, wherein each quality of service rule may comprise a packet filter set, a data radio bearer identifier associated a packet filter set; and a precedence value associated with the packet filter set.

[0036] The at least one processor may be configured to cause the transmitter entity to: receive, from the access user plane function, one or more data packets comprising an indicator for enabling reflective service data flow to data radio bearer mapping at the user equipment; wherein the at least one processor may be configured to cause the transmitter entity to apply one or more user equipment derived quality of service rules based onreceiving the indicator for enabling reflective service data flow to data radio bearer mapping at the user equipment.

[0037] The at least one processor may be configured to cause the transmitter entity to: based on receiving the one or more data packets comprising the indicator for enabling reflective service data flow to data radio bearer mapping, determine whether a user equipment derived quality of service rule comprising mapping information with a packet filter set defining characteristics corresponding to the characteristics of the received one or more data packet exists; and based on the determining whether the user equipment derived quality of service rule comprising the mapping information with the packet filter set defining characteristics corresponding to the characteristics of the received one or more data packets exists, create or update the user equipment derived quality of service rule comprising mapping information with a packet filter set defining characteristics corresponding to the characteristics of the received one or more data packets.

[0038] In response to determining that no user equipment derived quality of service rule comprising the mapping information with the packet filter set defining characteristics corresponding to the characteristics of the received one or more data packets exists, the at least one processor may be configured to cause the transmitter entity to: create a new user equipment derived quality of service rule comprising mapping information with a packet filter set defining characteristics corresponding to the characteristics of the received one or more data packets; and start a timer associated with the new user equipment derived quality of service rule.

[0039] In response to determining that a user equipment derived quality of service rule comprising the mapping information with the packet filter set defining characteristics corresponding to the characteristics of the received one or more data packets exists, the at least one processor may be configured to cause the transmitter entity to: restart a timer associated with the user equipment derived quality of service rule comprising the mapping information with the packet filter set defining characteristics corresponding to the characteristics of the received one or more data packets; determine whether the data radio bearer identifier associated with the received one or more data packets is different from the data radio bearer identifier associated with the user equipment derived quality of service rule comprising the mapping information with the packet filter set defining characteristics corresponding to the characteristics of the received one or more data packets; and update the data radio bearer identifier associated with the user equipment derived quality of service rule comprising the mapping information with the packet filter set defining characteristics corresponding to the characteristics of the received one or more data packets based on the determining.

[0040] The at least one processor may be configured to cause the transmitter entity to: determine that the timer associated with the user equipment quality of service mapping rule has expired; and in response to determining that the timer has expired, delete the user equipment derived quality of service rule.

[0041] According to an aspect, there is provided a method performed by a transmitter entity, the method comprising: mapping, based on mapping information, one or more service data flows to a data radio bearer, wherein each of the one or more service data flows comprises a plurality of data packets; and transmitting, to a receiver entity, the data packets comprised in the one or more service data flows via the data radio bearer to which the one or more service data flows are mapped.

[0042] The mapping information may comprise: one or more packet filter sets or one or more packet detection rules, each packet filter set or packet detection rule defining one or more characteristics of a service data flow; a data radio bearer identifier associated with each packet filter set or packet detection rule; and a precedence value associated with each packet filter set or packet detection rule.

[0043] The mapping may comprise: determining that one or more characteristics of the data packets of a service data flow match the one or more characteristics defined by one of the one or more packet filter sets or one of the one or more packet detection rules comprised in the mapping information; and based on the determining, mapping the data packets of the service data flow to the data radio bearer corresponding to the data radio bearer identifier associated with the one of the one or more packet filter sets or the one of the one or more packet detection rules comprised in the mapping information.

[0044] The mapping information may comprise a plurality of packet filter sets or a plurality of packet detection rules, and wherein the plurality of packet filter sets or the plurality of packet detection rules may be applied in an order according to the precedence values associated with the plurality of packet filter sets or the plurality of packet detection rules comprised in the mapping information.

[0045] The mapping may comprise inserting, into each data packet, a header comprising the data radio bearer identifier of the data radio bearer to which the service data flow comprising packet is mapped.

[0046] The method may further comprise receiving, from a control plane network function, the mapping information.

[0047] The mapping may comprise mapping a first service data flow and a second service data flow to a same data radio bearer, wherein the first service data flow and second service data flow have the same or similar characteristics.

[0048] The mapping may comprise mapping a third service data flow and a fourth service data flow to different data radio bearers, wherein the third service data flow and fourth service data flow have different characteristics.

[0049] The transmitter entity may be an access user plane function and the receiver entity may be a user equipment.

[0050] The mapping information may comprise the one or more packet detection rules, a data radio bearer identifier associated each packet detection rule; and a precedence value associated with each packet detection rule.

[0051] The mapping may comprise receiving, from a control plane network function, information indicating that reflective service data flow to data radio bearer mapping is enabled for the user equipment; and inserting, into each of the plurality of data packets, a header comprising an indicator for enabling reflective service data flow to data radio bearer mapping at the user equipment.

[0052] The transmitter entity may be a user equipment and the receiver entity may be an access user plane function.

[0053] The mapping information may be comprised in one or more quality of service rules, wherein each quality of service rule may comprise a packet filter set, a data radio bearer identifier associated a packet filter set; and a precedence value associated with the packet filter set.

[0054] The method may further comprise: receiving, from the access user plane function, one or more data packets comprising an indicator for enabling reflective service data flow to data radio bearer mapping at the user equipment; wherein the mapping may comprise applying one or more user equipment derived quality of service rules based on receiving the indicator for enabling reflective service data flow to data radio bearer mapping at the user equipment.

[0055] The method may further comprise: based on receiving the one or more data packets comprising the indicator for enabling reflective service data flow to data radio bearer mapping, determining whether a user equipment derived quality of service rule comprising mapping information with a packet filter set defining characteristics corresponding to the characteristics of the received one or more data packet exists; and based on the determining whether the user equipment derived quality of service rule comprising the mapping information with the packet filter set defining characteristics corresponding to the characteristics of the received one or more data packets exists, creating or updating the user equipment derived quality of service rule comprising mapping information with a packet filter set defining characteristics corresponding to the characteristics of the received one or more data packets.

[0056] In response to determining that no user equipment derived quality of service rule comprising the mapping information with the packet filter set defining characteristics corresponding to the characteristics of the received one or more data packets exists, the creating or updating may comprise: creating a new user equipment derived quality of service rule comprising mapping information with a packet filter set defining characteristics corresponding to the characteristics of the received one or more data packets; and starting a timer associated with the new user equipment derived quality of service rule.

[0057] In response to determining that a user equipment derived quality of service rule comprising the mapping information with the packet filter set defining characteristics corresponding to the characteristics of the received one or more data packets exists, the creating or updating may comprise: restarting a timer associated with the user equipment derived quality of service rule comprising the mapping information with the packet filter set defining characteristics corresponding to the characteristics of the received one or more data packets; determining whether the data radio bearer identifier associated with the received one or more data packets is different from the data radio bearer identifier associated with the user equipment derived quality of service rule comprising the mapping information with the packet filter set defining characteristics corresponding to the characteristics of the received one or more data packets; and updating the data radio bearer identifier associated with the user equipment derived quality of service rule comprising the mapping information with the packet filter set defining characteristics corresponding to the characteristics of the received one or more data packets based on the determining.

[0058] The method may further comprise determining that the timer associated with the user equipment quality of service mapping rule has expired; and in response to determining that the timer has expired, deleting the user equipment derived quality of service rule.

[0059] According to an aspect, there is provided a computer readable medium comprising instructions which, when executed by a transmitter entity, cause the transmitter entity to perform at least the following: mapping, based on mapping information, one or more service data flows to a data radio bearer, wherein each of the one or more service data flows comprises a plurality of data packets; and transmitting, to a receiver entity, the data packets comprised in the one or more service data flows via the data radio bearer to which the one or more service data flows are mapped.

[0060] The mapping information may comprise: one or more packet filter sets or one or more packet detection rules, each packet filter set or packet detection rule defining one or more characteristics of a service data flow; a data radio bearer identifier associated with each packet filter set or packet detection rule; and a precedence value associated with each packet filter set or packet detection rule.

[0061] The mapping may comprise: determining that one or more characteristics of the data packets of a service data flow match the one or more characteristics defined by one of the one or more packet filter sets or one of the one or more packet detection rules comprised in the mapping information; and based on the determining, mapping the data packets of the service data flow to the data radio bearer corresponding to the data radio bearer identifier associated with the one of the one or more packet filter sets or the one of the one or more packet detection rules comprised in the mapping information.

[0062] The mapping information may comprise a plurality of packet filter sets or a plurality of packet detection rules, and wherein the plurality of packet filter sets or the plurality of packet detection rules may be applied in an order according to the precedence values associated with the plurality of packet filter sets or the plurality of packet detection rules comprised in the mapping information.

[0063] The mapping may comprise inserting, into each data packet, a header comprising the data radio bearer identifier of the data radio bearer to which the service data flow comprising packet is mapped.

[0064] The instructions, when executed by the transmitter entity, may cause the transmitter entity to further perform receiving, from a control plane network function, the mapping information.

[0065] The mapping may comprise mapping a first service data flow and a second service data flow to a same data radio bearer, wherein the first service data flow and second service data flow have the same or similar characteristics.

[0066] The mapping may comprise mapping a third service data flow and a fourth service data flow to different data radio bearers, wherein the third service data flow and fourth service data flow have different characteristics.

[0067] The transmitter entity may be an access user plane function and the receiver entity may be a user equipment.

[0068] The mapping information may comprise the one or more packet detection rules, a data radio bearer identifier associated each packet detection rule; and a precedence value associated with each packet detection rule.

[0069] The mapping may comprise: receiving, from a control plane network function, information indicating that reflective service data flow to data radio bearer mapping is enabled for the user equipment; and inserting, into each of the plurality of data packets, a header comprising an indicator for enabling reflective service data flow to data radio bearer mapping at the user equipment.

[0070] The transmitter entity may be a user equipment and the receiver entity may be an access user plane function.

[0071] The mapping information may be comprised in one or more quality of service rules, wherein each quality of service rule may comprise a packet filter set, a data radio bearer identifier associated a packet filter set; and a precedence value associated with the packet filter set.

[0072] The instructions, when executed by the transmitter entity, may cause the transmitter entity to further perform: receiving, from the access user plane function, one or more data packets comprising an indicator for enabling reflective service data flow to data radio bearer mapping at the user equipment; wherein the mapping may comprise applying one or more user equipment derived quality of service rules based on receiving the indicator for enabling reflective service data flow to data radio bearer mapping at the user equipment.

[0073] The instructions, when executed by the transmitter entity, may cause the transmitter entity to further perform: based on receiving the one or more data packets comprising the indicator for enabling reflective service data flow to data radio bearer mapping, determining whether a user equipment derived quality of service rule comprising mapping information with a packet filter set defining characteristics corresponding to the characteristics of the received one or more data packet exists; and based on the determining whether the user equipment derived quality of service rule comprising the mapping information with the packet filter set defining characteristics corresponding to the characteristics of the received one or more data packets exists, creating or updating the user equipment derived quality of service rule comprising mapping information with a packet filter set defining characteristics corresponding to the characteristics of the received one or more data packets.

[0074] In response to determining that no user equipment derived quality of service rule comprising the mapping information with the packet filter set defining characteristics corresponding to the characteristics of the received one or more data packets exists, the creating or updating may comprise: creating a new user equipment derived quality of service rule comprising mapping information with a packet filter set defining characteristics corresponding to the characteristics of the received one or more data packets; and starting a timer associated with the new user equipment derived quality of service rule.

[0075] In response to determining that a user equipment derived quality of service rule comprising the mapping information with the packet filter set defining characteristics corresponding to the characteristics of the received one or more data packets exists, the creating or updating may comprise: restarting a timer associated with the user equipment derived quality of service rule comprising the mapping information with the packet filter set defining characteristics corresponding to the characteristics of the received one or more data packets; determining whether the data radio bearer identifier associated with the received one or more data packets is different from the data radio bearer identifierassociated with the user equipment derived quality of service rule comprising the mapping information with the packet filter set defining characteristics corresponding to the characteristics of the received one or more data packets; and updating the data radio bearer identifier associated with the user equipment derived quality of service rule comprising the mapping information with the packet filter set defining characteristics corresponding to the characteristics of the received one or more data packets based on the determining.

[0076] The instructions, when executed by the transmitter entity, may cause the transmitter entity to further perform: determining that the timer associated with the user equipment quality of service mapping rule has expired; and in response to determining that the timer has expired, deleting the user equipment derived quality of service rule.

[0077] According to an aspect, there is provided a non-transitory computer readable medium comprising program instructions that, when executed by an apparatus, cause the apparatus to perform at least the method according to any of the preceding aspects.

[0078] In the above, many different embodiments have been described. It should be appreciated that further embodiments may be provided by the combination of any two or more of the embodiments described above.DESCRIPTION OF FIGURES

[0079] Some example embodiments will now be described, by way of non-limiting and illustrative example only, with reference to the accompanying Figures (FIGs.) in which:

[0080] FIG. 1 shows a schematic representation of a 5G communication system of a communication network;

[0081] FIG. 2 illustrates example RAN architectures;

[0082] FIG. 3 illustrates two example architectures including an AUPF;

[0083] FIG. 4 illustrates an example known procedure for classification and marking of QoS flows and mapping to RAN resources;

[0084] FIG. 5 shows a further illustration of a known QoS mapping procedure;

[0085] FIG. 6 illustrates an example procedure for classification and marking of SDFs and mapping to RAN resources according to some examples;

[0086] FIG. 7 shows a further illustration of a mapping procedure according to some examples;

[0087] FIG. 8 shows a method according to some examples;

[0088] FIG. 9 shows example header structures where the header insertion is performed at the SDAP;

[0089] FIG. 10 shows example header structures where the header insertion is performed at the PDCP;

[0090] FIG. 11 shows a method performed by an ALIPF for the DL direction according to some examples;

[0091] FIG. 12 shows a method performed by the UE for the DL direction according to some examples;

[0092] FIG. 13 shows an example method for creating and / or updating one or more UE derived QoS rules;

[0093] FIG. 14 shows a method performed by the UE for the UL direction according to some examples;

[0094] FIG. 15 shows a method performed by the AUPF for the UL direction according to some examples;

[0095] FIG. 16 illustrates an example of a communication device; and

[0096] FIG. 17 shows a schematic representation of non-volatile memory media according to some examples.DETAILED DESCRIPTION

[0097] A non-exhaustive list of some abbreviations used throughout the present disclosure is provided below for reference:

[0098] 5GS: 5G System

[0099] AMBR: Aggregate Maximum Bit Rate

[0100] AUPF: Access User Plane Function

[0101] DRB: Data Radio Bearer

[0102] gNB: gNodeB

[0103] gNB-CU-CP: gNB-Central Unit-Control Plane

[0104] gNB-CU-UP: gNB-Central Unit-User Plane

[0105] gNB-DU: gNB-Distributed Unit

[0106] GTP: GPRS Tunnelling Protocol

[0107] PDCP: Packet Data Convergence Protocol

[0108] PDR: Packet Detection Rule

[0109] QER: QoS Enforcement Rule

[0110] QFI: QoS Flow Indicator

[0111] QoS: Quality of Service

[0112] RAN: Radio Access Network

[0113] RDI: Reflective QoS flow to DRB Mapping Indicator

[0114] RQI: Reflective QoS Indicator

[0115] RRC: Radio Resource Control (Protocol)

[0116] RSARI: Reflective SDF to AN Resource Indicator

[0117] SDAP: Service Data Adaptation Protocol

[0118] SDF: Service Data Flow

[0119] LIE: User Equipment

[0120] UPF: User Plane Function

[0121] The performance of a communication network (e.g., a cellular network) may be described in terms of the Quality of Service (QoS) provided by the network. QoS comprises requirements on aspects of a data session (e.g., a protocol data unit (PDU session), including but not limited to the service response time, packet loss, throughput, latency, availability, jitter, etc. The 5G QoS model is based on QoS Flows. The 5G QoS model supports both QoS Flows that require guaranteed flow bit rate (GBR QoS Flows) and QoS Flows that do not require guaranteed flow bit rate (Non-GBR QoS Flows).

[0122] A QoS Flow is the finest granularity of QoS differentiation in a protocol data unit (PDU) Session. A QoS Flow ID (QFI) is used to identify a QoS Flow in the 5G System. User Plane traffic with the same QFI within a PDU Session receives the same traffic forwarding treatment (e.g., scheduling, admission threshold). The QFI is carried in an encapsulation header on N3 (and N9), i.e. , without any changes to the E2E packet header. The QFI may be dynamically assigned or may be equal to a 5G QoS identifier (5QI).

[0123] Within the 5GS, a QoS Flow is controlled by the session management function (SMF) and may be preconfigured, or established during establishment of a data session (e.g., PDU Session) between a UE and UPF of the 5GS, or the PDU Session Modification procedure.

[0124] Any QoS Flow is characterized by:• A QoS profile provided by the SMF to the access node (AN) via the access and mobility management function (AMF) over the N2 reference point or preconfigured in the AN;• One or more QoS rule(s) and optionally QoS Flow level QoS parameters associated with these QoS rule(s) which can be provided by the SMF to the UE via the AMF over the N1 reference point and / or derived by the UE by applying Reflective QoS control; and• One or more UL and DL PDR(s) provided by the SMF to the UPF.

[0125] Packet filters at the non-access stratum (NAS) layer of a RAN node (e.g., gNB) are responsible for mapping data packets to QoS Flows in the downlink and uplink for the UPF and UE respectively. The packet filter configuration is provided by Packet Detection Rules (PDRs) in case of the UPF, while QoS rules in the UE assist the UE with mapping data packets to QoS Flows in the uplink.

[0126] For a given UE, a specific PDU session may be characterized by one or more QoS Flows, and for each PDU session, the RAN establishes at least one access-specificresource, i.e., data radio bearer (DRB). Consequently, the RAN node maps packets belonging to different QoS Flows within PDU sessions to the DRBs associated with that PDU session. The mapping of a QoS Flow to a DRB is done by the RAN node (e.g., gNB) based on the QFI and the associated QoS profiles. Separate DRBs may be established for QoS flows requiring different packet forwarding treatment, or several QoS Flows belonging to the same PDU session can be multiplexed in the same DRB. Furthermore, the 5GS can also enforce an aggregate maximum bitrate across all flows associated with a PDU sessions, i.e., the session AMBR.

[0127] The 5G QoS model also supports Reflective QoS. Reflective QoS enables the UE to map UL User Plane traffic to QoS Flows without SMF provided QoS rules. This is achieved by creating UE derived QoS rules in the UE based on the received DL traffic. To enable Reflective QoS, the DL SDAP header includes a 1 -bit RDI (Reflective QoS flow to DRB mapping Indication) and a 1-bit RQI (Reflective QoS Indication). When RDI=1 , UE updates QoS flow to DRB mapping for uplink. When RQI=1 , UE informs NAS that Service Data Flow (SDF) to QoS mapping information have been updated.

[0128] In summary, the 5G QoS Model provides a two-step QoS handling approach which includes — (1) mapping from data packets (carried in Service Data Flows (SDFs)) to QoS Flows (in the UPF) and (2) mapping from QoS Flows to Data Radio Bearers (DRBs) (in the gNB). Furthermore, the use of Reflective QoS allows the UE to implicitly derive QoS Rules from the DL data traffic.

[0129] In some networks, a gNB central unit - user plane (CU-UP) and user plane function (UPF) may be co-located (e.g., deployed on a same computing system). However, due to overlapping functionality between both entities (e.g., GTP encapsulation, GTP decapsulation and / or packet processing), collocating the CU-UP and UPF (e.g., collocating overlapping functionalities of the CU-UP and the UPF in a single NF) may not be efficient due to the duplication of the overlapping functionality (e.g., GTP encapsulation, GTP decapsulation and / or packet processing).

[0130] In some examples, a RAN-core converged network function that replaces or otherwise performs similar operations and / or includes similar functionality as the CU-UP and UPF may be provided. As used herein, this RAN-core converged network function may be interchangeably referred to as an Access User Plane Function (AUPF). In some examples, the AUPF may have the similar functionalities as the CU-UP and the UPF and may perform similar operations as both the CU-UP and UPF perform. However, the AUPF does not include perform N3 interface- related processing (such as the GTPU encapsulation and decapsulation). Thus the AUPF may provide benefits such as reducing packet forwarding latency in the cellular system and reducing the power consumed by the cellularsystem because packet processing performed by the AU PF is simplified relative to the packet processing performed by both the CU-UP and the UPF.

[0131] The convergence of the CU-UP and UPF into an AUPF may enable further developments in how QoS mapping (e.g., the mapping of data packets carried in SDFs to QoS Flows and / or the mapping from QoS Flows to DRBs) and QoS handling and packet processing (e.g., how data packets with a given QoS are handled and / or processed) are performed. For example, a one-step mapping of SDF to DRB may be enabled, which may be faster and more efficient than existing QoS handling methods, and which may reduce signalling sent between entities of a communication network and therefore reduce power consumption of the communication network.

[0132] Prior to describing the examples of the present disclosure, certain aspects of a 5G communication system (5GS) are described in relation to FIG. 1 to facilitate explanation of the various examples.

[0133] FIG. 1 shows a schematic representation of a 5GS of a communication network (e.g., a cellular network). The 5GS may comprise a user equipment (UE) 100, an access network such as a 5G radio access network (5G-RAN) 101 or next generation radio access network (NG-RAN), a 5G core network 102, and one or more application functions 103. An application function 103 may be deployed in the 5GS as trusted application function or may be deployed or host on one or more application servers of the data network (DN) 104. Such application functions are untrusted application functions. The 5GS connects the UE to a data network the access network and the 5GC 102 (e.g., a UPF of the 5GC).

[0134] The 5G-RAN 101 may comprise one or more radio access nodes, such as gNodeB (gNB). A gNB may include one or more centralized units (CUs) connected to one or more Distributed Units (DUs), which in turn may be connected to one or more Radio Units (RUs). In some examples, the DU and RU may be combined. An example RAN architecture is described below in relation to FIG. 2.

[0135] The 5GC may comprise the following network functions: Network Slice Selection Function (NSSF); Network Exposure Function (NEF) 105; Network Repository Function (NRF); Policy Control Function (PCF); Unified Data Management (UDM) 106; Application Function (AF) 103; Authentication Server Function (AUSF) 107; an Access and Mobility Management Function (AMF) 108; Session Management Function (SMF) 109; and a user plane function (UPF) 110. FIG. 1 also shows the various interfaces (N1 , N2 etc.) that may be implemented between the various elements of the system.

[0136] FIG. 2 illustrates example RAN architectures according to existing standards (e.g., 3GPP TS 138.401), where the RAN 101 is disaggregated into one or more distributed units (DUs) 202, a central unit - control plane (CU-CP) 204, and one or more central unit - userplanes (ClI-UPs) 206a-c. While not shown in FIG. 2, each DU 202 may be connected to a Radio Unit (RU), or the DU may comprise the RU. The CU-CP 204 may be connected to the DUs 202 via the F1-C interface. Each CU-UP 206 may be connected to one or more DUs 202 via the F1-U interface. Each CU-UP 206 may be connected to the CU-CP 204 through the E1 interface.

[0137] As explained above, the CU-UP 206 and UPF 110 may be converged into an AUPF 300. FIG. 3 illustrates two example architectures including the AUPF 300. The AUPF 300 may be controlled by a CP function 302. In the example of FIG. 3a, the AUPF 300 is logically separate from the DU / RU 202, whereas in the example of FIG. 3b the AUPF 300 and DU / RU 202 are combined. It should be understood that in other examples different architectures including the AUPF 300 may be provided.

[0138] FIG. 4 illustrates an example known procedure for classification and marking of QoS flows and mapping to RAN resources described in 3GPP TS 23.501 , clause 5.7.1.5).

[0139] As illustrated in FIG. 4, data packets are generated by applications at the application / service layer. The data packets may be comprised in one or more SDFs. The SMF 109 configures the UE 100 or UPF 110 to map the one or more SDFs to QoS flows by marking each packet in an SDF with a QoS Flow Indicator (QFI) based on one or more QoS rules, such as PDR and QER. The QFI and an optional Reflective QoS Indicator (RQI) are encapsulated in the GTP-U header and shared to the RAN 101 via the N3 interface. The RAN 101 , and more specifically the CU-UP 206, maps the QoS flows to the Data Radio Bearers (DRBs) based on a message from the CU-CP 204 via the E1 interface. The QoS- related marking, such as QFI, RQI, and reflective QoS DRB indicator (RDI), can be optionally added to the SDAP header to be shared to the UE in the case of reflective QoS. The data packets are then transmitted between the UE 100 and RAN 101 via the resources to which the QoS flows comprising the packets have been mapped.

[0140] A further illustration of a QoS mapping procedure according to existing 5GS standards (e.g., 3GPP TS 23.501) is shown in FIG. 5, where SDFs are first mapped to QoS flows, and then the QoS flows are mapped to DRBs.

[0141] In the example of FIG. 5, three SDFs 500a-c are first mapped to a QoS flow 502a, and SDF 500d is mapped to QoS flow 502b. Then, two QoS flows 502a-b are then mapped to a DRB 504. In general, M SDF flows may be mapped to a QoS flow, and N QoS flows may be mapped to a DRB, where M and N a both integers greater than or equal to one. In some examples, the mapping of SDFs to QoS flows may be performed by a UPF 110, while the mapping of QoS flows to DRBs may be performed by the RAN 101 (and more specifically the CU-UP 206).

[0142] More specifically, the II PF 110 may be configured by the SMF 109 to map SDFs to QoS flows by marking each data packet comprised in the SDF with a QoS Flow Identifier (QFI) based on a PDR and QER of an N4 message (that is, a message received at the UPF 110 from SMF 109 via the N4 interface). The UPF 110 may then encapsulate the QFI (and optionally a Reflective QoS Indicator (RQI) if Reflective QoS is enabled) in GTP-U header of the packets which are then sent as a QoS flow to the RAN 110 via the N3 interface.

[0143] The RAN 110, and in some examples more specifically the CU-UP 206, then maps the QoS flows to the Data Radio Bearers (DRBs) based on a message (e.g. a message sent via an E1 interface) received at the RAN 110 from the CU-CP 204. The QoS-related marking, such as QFI, RQI, (and reflective QoS DRB indicator (RDI) if Reflective QoS is enabled), can be optionally added to the SDAP header to be shared to the UE 100 in the case of reflective QoS.

[0144] As explained above, in some communication networks, a RAN-core converged network function that replaces and performs the same or similar functions as the CU-UP and UPF entities may be provided. Such communication networks may be referred to as having a RAN-core converged architecture. The RAN-core converged network function (e.g., AUFP) may optimize QoS handling. In some examples, the RAN-core converged network function may enable a one-step mapping of SDFs to DRBs, without first mapping the SDFs to QoS flows.

[0145] FIG. 6 illustrates an example procedure for classification and marking of SDFs and mapping to RAN resources according to some examples of the present disclosure. In the example of FIG. 6, the AUPF 300 and DU / RU 202 are shown as separate entities. However, as explained above in relation to FIG. 3, in some examples the AUPF 300 and DU / RU 202 may be functionally combined or collocated.

[0146] As illustrated in FIG. 6, data packets are generated by applications at the application / service layer. The data packets are grouped in one or more SDFs, which together may form a PDU session. The SDFs are mapped to RAN resources (i.e. , to DRBs) either in the UE 100 or the AUPF 300. The data packets are then transmitted between the UE 100 and DU / RU 202 via the resources (DRBs) to which the SDFs comprising the packets have been mapped.

[0147] A further illustration of a mapping procedure according to some examples of the present disclosure is shown in FIG. 7, where SDFs are mapped to DRBs in a single step.

[0148] In the example of FIG. 7, the SDFs are mapped to DRBs in a single step. Such single step mapping may be enabled by the convergence of the UPF 110 and CU-UP into a single logical entity, e.g., AUPF 300.

[0149] In the example of FIG. 7, four SDFs 700a-d are mapped to DRB 702 in a single step. In general, M SDFs may be mapped to the same DRB. In some examples the mapping of SDFs to DRBs may be performed in the ALIPF 300. As will be explained in further detail below, the one step mapping of SDFs to DRBs may be enabled by various modifications to the QoS model as described in existing standards (e.g. 3GPP TS 23.501).

[0150] As will be described in further detail below, a similar one-step mapping may be implemented at the UE-side, which may be enabled by various modifications to UE-side QoS rules, and may result in lower processing overhead for the UE.

[0151] Reference is made to Figure 8, which shows methods according to some examples.

[0152] In some examples there is provided a method as shown in Figure 8a. The method of Figure 8a may in some examples be performed by a transmitter entity.

[0153] At 800, the method comprises mapping, based on mapping information, one or more service data flows to one or more data radio bearers, wherein each of the one or more service data flows comprises a plurality of data packets.

[0154] At 802, the method comprises transmitting, to a receiver entity, the data packets comprised in the one or more service data flows via the one or more data radio bearers to which the one or more service data flows are mapped.

[0155] In some examples the transmitter entity may be a RAN-core converged network function, such as an Access User Plane Function (AUPF 300) and the receiver entity may be a UE 100. In some examples the transmitter entity may be a UE 100 and the receiver entity may be an AUPF 300.

[0156] The mapping information may indicate the association of SDF to DRB. The mapping information may comprise one or more packet filter sets or one or more packet detection rules; a DRB identifier associated with each of the one or more packet filter sets or one or more packet detection rules; and a precedence value associated with each of the one or more packet filter sets or one or more packet detection rules. Each packet filter set may comprise one or more packet filters. The one or more packet filters and one or more packet detection rules may define one or more characteristics (e.g., QoS characteristics) of an SDF. When SDFs with characteristics matching one of the one or more packet filters or one of the one or more packet detection rules are received, the mapping information is such that the SDFs are mapped to a DRB corresponding to the DRB identifier associated with the one of the one or more packet filters or the one of the one or more packet detection rules comprised in the mapping information. That is to say, the transmitter entity may, for each packet detection rule or packet filter set, determine that characteristics of a given SDF match the characteristics defined by the packet detection rule or packet filter set, and based on the determining the transmitter entity may map the given SDF to a DRB corresponding tothe associated DRB ID. When there is more than one packet detection rule or packet filter set, the transmitter entity may apply the packet detection rules or packet filter sets in order of precedence value.

[0157] For example, a first SDF and second SDF may both have the same or similar characteristics (e.g., they may have a same or similar latency requirement). As such, when performing the mapping at 800, the transmitter entity may map the first SDF and second SDF to the same DRB corresponding to the DRB ID in the mapping information.

[0158] As a further example, a third SDF and fourth SDF may have different characteristics (e.g., they may have different latency requirements). As such, when performing the mapping at 800, the transmitter entity may map the third SDF and fourth SDF to different DRBs (as identified by the DRB IDs in the mapping information).

[0159] It should be understood that the specifics of the mapping, in terms of how similar or different SDF characteristics are to result in the mapping to a same / different DRB, may be implementation specific.

[0160] In some examples, the mapping information may be comprised in one or more QoS rules or one or more reflective QoS rules.

[0161] In some examples, there may be a default QoS rule, where the mapping information comprised in the default QoS rule identifies a default DRB. In some examples, when the characteristics of an SDF do not match the characteristics of a packet filter set of any of the other QoS rules, the SDF may be mapped to the DRB ID comprised in the mapping information comprised in the default QoS rule.

[0162] In some examples, the QoS rules comprising the mapping information may be received by the transmitter entity from a control plane network function, which may for example be comprised in the core network. The control plane network function that provides the QoS rules may for example comprise the SMF 109. However, in some examples of the present disclosure, other control plane network functions may provide the QoS rules. In general, the control plane network function that provides the QoS rules to the transmitter entity may be implementation specific.

[0163] In some examples, the mapping may comprise inserting, by the transmitter entity, a packet header into each of the data packets. The header insertion may be performed at the SDAP or PDCP layers.

[0164] In the case of Reflective QoS being enabled for the UE 100, in the DL the AU PF 300 (as transmitter entity) may insert an indicator into the header to indicate that the UE 100 may perform reflective SDF to access node resource (e.g., DRB) mapping. As used herein, the term “reflective SDF to access node resource mapping” may be used interchangeably with the term “reflective SDF to DRB mapping”. The indicator may comprisea Reflective SDF to AN Resource Indicator (RSARI), as shown in FIGs. 9 and 10. It should be understood that this indicator may be present only in the DL direction, and that in the UL direction, as shown in FIG. 9, no RSARI (or equivalent indicator) is included. The ALIPF 300 may receive information from the control plane network function along with the mapping information, as described previously.

[0165] FIG. 9 shows example header structures where the header insertion (where the header is comprised in octet 1 , Octi) is performed at the SDAP, with 900 showing the case for downlink (DL) packets and 902 showing the case for uplink (UL) packets.

[0166] As shown in FIG. 9, the header may comprise a DRB ID 904. The DRB ID 904 may refer to the access-specific resource identifier. The DRB ID 904 may comprise 6 bits, which may help maintain backward compatibility with legacy SDAP packet structure (wherein the QFI uses 6 bits, and as such the DRB ID 904 may replace the QFI in the legacy SDAP structure without further modification) and may allow for future extensions in the number of DRBs supported by the RAN. It should be understood that in some examples the accessspecific resource identifier may not be required to be signalled as part of the SDAP header, and therefore the DRB ID 904 shown in FIG. 9 is optional.

[0167] FIG. 10 shows example header structures where the header insertion is performed at the PDCP. Since PDCP entities are DRB-specific, the DRB ID is already known during PDCP-related processing and does not need to be explicitly signalled in the header. By removing the SDAP header and preserving the existing PDCP Data PDU size, some examples may allow for reduced processing burden, and an increase in throughput due to lower overhead, which while beneficial for the network, also benefits the UE simultaneously. In FIG. 10, 1000 shows an example format with 12 bits PDCP SN, while 1002 shows an example format with 18 bits PDCP SN. Only the header is shown in FIG. 10 - it should be understood that the packet may further comprise data in the other octets, for example as shown in octets 2-N for FIG. 9.

[0168] In some examples, the UL PDCP Data PDUs may follow the legacy PDCP PDU structure (e.g., as per 3GPP TS 38.323, Clause 6.2.2).

[0169] In some examples, the transmitter entity may be the AU PF 300, and the receiver may be a UE 100. Such examples may be referred to herein as being in the downlink (DL) direction.

[0170] Reference is made to FIG. 11 , which shows a method performed by the AUPF 300 for the DL direction according to some examples - that is to say the AUPF 300 is acting as the transmitter entity.

[0171] At 1100, the ALIPF 300 may receive user plane traffic from the data network. The user plane traffic may comprise one or more SDFs, each SDF comprising a plurality of data packets.

[0172] At 1102, the ALIPF 300 may map the SDFs to DRBs. The mapping may be performed based on the mapping information as described previously. For example, the mapping may be based on one or more packet detection rules, a data radio bearer identifier associated each packet detection rule; and a precedence value associated with each packet detection rule.

[0173] If session-AMBR enforcement is to be performed (which may be implementation specific), at 1104, the ALIPF 300 may perform session-AMBR enforcement. For example the ALIPF 300 may monitor and control the aggregate bit rate of the data traffic within an AMBR limit for the session.

[0174] If the ALIPF 300 determines that reflective SDF to access node resource is enabled for the PDU session of the UE 100, then at 1106, the ALIPF 300 may determine how to perform RSARI insertion into the header of the data packets to indicate that the UE 100 may perform reflective SDF to access node resource (e.g., DRB) mapping for the PDU session. For example, the AUPF 300 may determine whether to perform SDAP or PDCP packet processing for inserting the RSARI into the data packet header. In some examples, the AUPF 300 may receive, from the control plane network function, configuration information indicating how to insert the indicator. The determination at 1106 may be based on the configuration information.

[0175] At 1108, based on the determination at 1106, the AUPF 300 may perform processing on the resulting packets at the PDCP or SDAP layers. In some examples, the processing at PDCP or SDAP layers may comprise inserting a header, for example as described above in relation to FIG. 9 and 10, into each of the packets.

[0176] At 1110, the AUPF 300 transmits the processed data packets to the UE 100 via the DRB(s) to which the SDFs comprising the packets have been mapped at 1102.

[0177] Reference is made to FIG. 12, which shows a method performed by the UE 100 for the DL direction according to some examples - that is to say the UE 100 is acting as the receiver entity.

[0178] At 1200, the UE 100 receives one or more data packets from the AUPF 300 via one or more DRBs.

[0179] At 1202, the UE 100 determines whether the QoS handling entity is the SDAP or PDCP, and based on the determination at 1204 performs SDAP processing or at 1206 performs PDCP processing.

[0180] In some examples, the SDAP processing may comprise determining whether a reflective SDF to access node resource indicator (e.g., RSARI) is present. The SDAP processing may further comprise retrieving the data from the data packet, for example may removing the header from the packet structure described above in relation to FIG. 9.

[0181] In the case of the QoS handling being performed at the PDCP, the PDCP processing may comprise determining whether a reflective SDF to access node resource indicator (e.g., RSARI) is present. The PDCP processing may further comprise retrieving the data from the data packet, for example may removing the header from the packet structure described above in relation to FIG. 10.

[0182] The SDAP or PDCP may then inform the upper layers (e.g., NAS) about the DRB ID, and reflective SDF to access node resource indicator (e.g. RSARI) if present, based on the processing at step 1204 or 1206.

[0183] At 1208, if the reflective SDF to access node resource indicator is present, the UE 100 (e.g., the upper layers, such as NAS) creates or updates one or more UE derived QoS rules accordingly. The creation or updating of one or more UE derived QoS rules is described in further detail below with reference to FIG. 13.

[0184] At 1210, the UE 100 (e.g., upper layers) processes the data retrieved from the data packets at 1202.

[0185] Reference is made to FIG. 13, which shows an example method for creating and / or updating one or more UE derived QoS rules that may for example be performed by the UE 100 at step 1208. In some examples, the steps shown in FIG. 13 may be performed by the upper layers, such as the NAS layer.

[0186] At 1300, the UE 100 determines whether a UE derived QoS rule comprising mapping information with a packet filter set defining characteristics corresponding to the characteristics of a received data packet exists. The mapping information may be as described previously (e.g., DRB ID, Packet Filter Set, Precedence value).

[0187] When the UE 100 determines at 1300 that no UE derived QoS rule comprising mapping information with a packet filter set defining characteristics corresponding to the characteristics of a received data packet exists, then at 1302 the UE 100 creates a new UE derived QoS rule comprising mapping information with a packet filter set defining characteristics corresponding to the characteristics of the received data packet.

[0188] At 1304, the UE 100 starts a timer associated with the UE derived QoS rule created at 1302. The timer may have a timer value that is configured by the network. Upon expiry of the timer, the UE 100 may delete the associated QoS rule.

[0189] When the UE 100 determines that a UE derived QoS rule comprising mapping information with a packet filter set defining characteristics corresponding to thecharacteristics of a received data packet exists at 1300, then at 1306 the UE restarts the timer associated with that UE derived QoS rule.

[0190] At 1308, after restarting the timer, the UE 100 determines whether the DRB ID associated with the received packet is different from the DRB ID associated with the existing UE derived QoS rule.

[0191] When the UE 100 determines at 1308 that the DRB ID associated with the received packet is different from the DRB ID associated with the existing UE derived QoS rule, at 1310 the UE updates the UE derived QoS rule with the DRB ID associated with the received packet.

[0192] In some examples, the transmitter entity may be the UE 100, and the receiver may be the AUPF 300. Such examples may be referred to herein as being in the downlink (UL) direction.

[0193] Reference is made to FIG. 14, which shows a method performed by the UE 100 for the UL direction according to some examples - that is to say the UE 100 is acting as the transmitter entity.

[0194] At 1400, the UE 100 may obtain user plane traffic generated by an application run on the UE 100. The user plane traffic may comprise one or more SDFs, each SDF comprising a plurality of data packets.

[0195] At 1402, the UE 100 may map the SDFs to DRBs. The mapping may be performed based on mapping information comprised in one or more QoS rules, for example as described previously. For example, the mapping may be based on the one or more QoS rules wherein each quality of service rule comprises a packet filter set, a data radio bearer identifier associated a packet filter set; and a precedence value associated with the packet filter set. The one or more QoS rules may be QoS rules received from the network or may be one or more UE derived QoS rules in the case of reflective SDF to access node resource being enabled (e.g., as indicated by the RSARI comprised in the header of DL data packets if previously received from the AUPF 300).

[0196] If session-AMBR enforcement is to be performed (which may be implementation specific), at 1404, the UE 100 may perform session-AMBR enforcement. For example the UE 100 may monitor and control the aggregate bit rate of the data traffic within an AMBR limit for the session.

[0197] At 1406, the UE 100 may perform processing on the resulting packets at the PDCP or SDAP layers. In some examples, the processing at PSCP or SDAP layers may comprise the header insertion described previously.

[0198] At 1408 the UE 100 may transmit the processed data packets to the ALIPF 300 via the DRB(s) to which the SDFs comprising the packets have been mapped at 1402.

[0199] Reference is made to FIG. 15, which shows a method performed by the ALIPF 300 for the UL direction according to some examples - that is to say the AU PF 300 is acting as the receiver entity.

[0200] At 1500 the AU PF 300 receives one or more data packets from the UE 100 via one or more DRBs. The one or more data packets may comprise the headers described previously.

[0201] At 1502, the AUPF 300 determines whether the QoS handling entity is the SDAP or PDCP, and based on the determination at 1504 performs SDAP processing or at 1506 performs PDCP processing.

[0202] In some examples, the SDAP processing may comprise retrieving the data from the data packet, for example may removing the header from the packet structure described above in relation to FIG. 9. The PDCP processing may further comprise retrieving the data from the data packet, for example may removing the header from the packet structure described above in relation to FIG. 10.

[0203] At 1508 the AUPF 300 determines whether the DRB IDs in the headers of the packets are aligned with the mapping information comprised in the one or more QoS rules provided to the UE 100, or one or more QoS rules derived by the UE 100 in the case of reflective QoS being enabled.

[0204] The QoS rules may be as described previously. The QoS rules may be provided to the UE 100 by a control plane network function, which may for example be comprised in the core network. The control plane network function may provide the same QoS rules to the AUPF 300. In the case of reflective QoS, the AUPF 300 may determine the expected UE behaviour (e.g., in terms of expected UE derived QoS rules). The AUPF 300 may then, based on the QoS rules (either provided to the UE or expected UE derived QoS rules) determine whether the DRB IDs in the packet headers provided by the UE are aligned with the QoS rules. The DRBs may be considered aligned with the QoS rules if the DRB ID of the DRB via which a packet is received matches the DRB ID to which the AUPF 300 would have mapped the packet based on the mapping information comprised in the one or more QoS rules. For example, if the AUPF 300 would map a first packet (packet #1) to a first DRB (DRB#1), and packet#1 is received from the UE via DRB#1 , the packet is considered aligned with the mapping information comprised in the QoS rules. However, if packet#1 was received via a second DRB (DRB#2) but the AUPF 300 would have mapped packet#1 to DRB#1 , then the packet is not considered aligned with the mapping information comprised in the QoS rules.

[0205] If session-AMBR enforcement is to be performed (which may be implementation specific), at 1510 the ALIPF 300 performs session-AMBR enforcement, for example as described previously.

[0206] At 1512, the ALIPF 300 processes the data retrieved from the data packets at 1504 or 1506.

[0207] Examples have been described above in which a transmitter entity, such as a UE 100 or ALIPF 300, performs one step mapping of SDF to DRB. The mapping may be based on mapping information. The mapping information may comprise one or more packet filter sets or one or more packet detection rules, each packet filter set or packet detection rule defining one or more characteristics of a service data flow; a data radio bearer identifier associated with each packet filter set or packet detection rule; and a precedence value associated with each packet filter set or packet detection rule. The mapping information may be provided by a control plane network function or derived by the UE 100 (e.g., in the case of reflective SDF to AN resource mapping being enabled). Some examples may enable faster and more efficient mapping compared to existing QoS handling methods. Some examples may reduce signalling overhead and resource wastage in the system.

[0208] In some examples there is provided a transmitter entity comprising means for: mapping, based on mapping information, one or more service data flows to a data radio bearer, wherein each of the one or more service data flows comprises a plurality of data packets; and transmitting, to a receiver entity, the data packets comprised in the one or more service data flows via the data radio bearer to which the one or more service data flows are mapped.

[0209] In some examples the transmitter entity may comprise an AU PF 300. In some examples there is provided an apparatus comprising means for providing an AUPF 300 configured to perform: mapping, based on mapping information, one or more service data flows to a data radio bearer, wherein each of the one or more service data flows comprises a plurality of data packets; and transmitting, to a receiver entity, the data packets comprised in the one or more service data flows via the data radio bearer to which the one or more service data flows are mapped.

[0210] In some examples the transmitter entity may be a UE. In some examples there is provided a UE comprising means for: mapping, based on mapping information, one or more service data flows to a data radio bearer, wherein each of the one or more service data flows comprises a plurality of data packets; and transmitting, to a receiver entity, the data packets comprised in the one or more service data flows via the data radio bearer to which the one or more service data flows are mapped.

[0211] In some examples there is provided a transmitter entity comprising at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the transmitter entity at least to: map, based on mapping information, one or more service data flows to a data radio bearer, wherein each of the one or more service data flows comprises a plurality of data packets; and transmit, to a receiver entity, the data packets comprised in the one or more service data flows via the data radio bearer to which the one or more service data flows are mapped.

[0212] In some examples the transmitter entity may comprise an apparatus for providing an ALIPF 300. In some examples there is provided an apparatus for providing an ALIPF, the apparatus comprising at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: map, based on mapping information, one or more service data flows to a data radio bearer, wherein each of the one or more service data flows comprises a plurality of data packets; and transmit, to a receiver entity, the data packets comprised in the one or more service data flows via the data radio bearer to which the one or more service data flows are mapped.

[0213] In some examples the transmitter entity may comprise a UE. In some examples there is provided a user equipment comprising at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the user equipment at least to: map, based on mapping information, one or more service data flows to a data radio bearer, wherein each of the one or more service data flows comprises a plurality of data packets; and transmit, to a receiver entity, the data packets comprised in the one or more service data flows via the data radio bearer to which the one or more service data flows are mapped.

[0214] FIG. 16 illustrates an example of a communication device 1600, such as the UE 100 illustrated on FIG. 1. The communication device 1600 may be provided by any device capable of sending and receiving radio signals. Non-limiting examples of a communication device 1600 comprise a user equipment, a mobile station (MS) or mobile device such as a mobile phone or what is known as a ’smart phone’, a computer provided with a wireless interface card or other wireless interface facility (e.g., USB dongle), a personal data assistant (PDA) or a tablet provided with wireless communication capabilities, a machinetype communications (MTC) device, an Internet of things (loT) type communication device or any combinations of these or the like. The communication device 1600 may comprise a transceiver for transmitting and / or receiving, for example, wireless signals carrying communications, for example radio signals. The communications may be one or more of voice, electronic mail (email), text messages, multimedia data, machine data and so on.

[0215] The communication device 1600 may receive wireless signals (e.g., radio signals) over an air or radio interface 1607 via appropriate apparatus for receiving and may transmit wireless signals via appropriate apparatus for transmitting radio signals. In FIG. 16 transceiver is designated schematically by block 1606. The transceiver 1606 may comprise, for example, a radio part and associated antenna arrangement. The antenna arrangement may be arranged internally or externally to the mobile device and may comprise one or more antenna elements. The antenna arrangement may be a multi-input multi output (MIMO) antenna.

[0216] The communication device 1600 may be provided with at least one processor 1601 , at least one memory ROM 1602a, at least one RAM 1602b and other possible components 1603 for use in software and hardware aided execution of tasks it is designed to perform, including control of access to and communications with access networks (e.g., the 5G-RAN or NG-RAN 101 illustrated in FIG. 1) and other communication devices. The at least one processor 1601 is coupled to the RAM 1602b and the ROM 1602a. The at least one processor 1601 may be configured to execute an appropriate software code 1608. The software code 1608 may for example allow to perform one or more operations of the communication device. The software code 1608 may be stored in the ROM 1602a.

[0217] The processor, the ROM, and the RAM, the transceiver and other circuitry of the communication device (e.g., a modem) can be provided on a circuit board, in chipsets, or in a system on chip. The circuit board, chipsets or system on chip is denoted by reference1604. The communication device 1600 may optionally have a user interface such as keypad1605, touch sensitive screen or pad, combinations thereof or the like. Optionally one or more of a display, a speaker and a microphone may be provided depending on the type of communication device.

[0218] FIG. 17 shows a schematic representation of non-volatile memory media 1700a (e.g., computer disc (CD) or digital versatile disc (DVD)) and 1700b (e.g., universal serial bus (USB) memory stick) storing instructions and / or parameters 1702 which when executed by a processor allow the processor to perform one or more of the steps of any of the methods described previously.

[0219] It is understood that references in the above to various network functions (e.g., to an AMF, an SMF, TNF etc.) may comprise apparatus that perform at least some of the functionality associated with those network functions. Further, an apparatus comprising a network function may comprise a virtual network function instance of that network function.

[0220] It should be understood that the apparatuses may comprise or be coupled to other units or modules etc., such as radio parts or radio heads, used in or for transmission and / orreception. Although the apparatuses have been described as one entity, different modules and memory may be implemented in one or more physical or logical entities.

[0221] It is noted that whilst some embodiments have been described in relation to 5G networks, similar principles can be applied in relation to other networks and communication systems. Therefore, although certain embodiments were described above by way of example with reference to certain example architectures for wireless networks, technologies and standards, embodiments may be applied to any other suitable forms of communication systems than those illustrated and described herein.

[0222] It is also noted herein that while the above describes example embodiments, there are several variations and modifications which may be made to the disclosed solution without departing from the scope of the present invention.

[0223] As used herein, “at least one of the following: ” and “at least one of ” and similar wording, where the list of two or more elements are joined by “and” or “or”, mean at least any one of the elements, or at least any two or more of the elements, or at least all the elements.

[0224] In general, the various embodiments may be implemented in hardware or special purpose circuitry, software, logic or any combination thereof. Some aspects of the disclosure may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device, although the disclosure is not limited thereto. While various aspects of the disclosure may be illustrated and described as block diagrams, flow charts, or using some other pictorial representation, it is well understood that these blocks, apparatus, systems, techniques or methods described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.

[0225] As used herein, the term “circuitry” may refer to one or more or all of the following:(a) hardware-only circuit implementations (such as implementations in only analog and / or digital circuitry) and(b) combinations of hardware circuits and software, such as (as applicable):(i) a combination of analog and / or digital hardware circuit(s) with software / firmware and(ii) any portions of hardware processor(s) with software (including digital signal processor(s)), software, and memory(ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions) and(c) hardware circuit(s) and or processor(s), such as a microprocessor(s) or a portion of a microprocessor(s), that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation.”

[0226] This definition of circuitry applies to all uses of this term herein, including in any claims. As a further example, as used herein, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.

[0227] The embodiments of this disclosure may be implemented by computer software executable by a data processor of the mobile device, such as in the processor entity, or by hardware, or by a combination of software and hardware. Computer software or program, also called program product, including software routines, applets and / or macros, may be stored in any apparatus-readable data storage medium and they comprise program instructions to perform particular tasks. A computer program product may comprise one or more computer-executable components which, when the program is run, are configured to carry out embodiments. The one or more computer-executable components may be at least one software code or portions of it.

[0228] Further in this regard it should be noted that any blocks of the logic flow as in the FIG.s may represent program steps, or interconnected logic circuits, blocks and functions, or a combination of program steps and logic circuits, blocks and functions. The software may be stored on such physical media as memory chips, or memory blocks implemented within the processor, magnetic media such as hard disk or floppy disks, and optical media such as for example DVD and the data variants thereof, CD. The physical media is a non- transitory media.

[0229] The term “non-transitory,” as used herein, is a limitation of the medium itself (i.e., tangible, not a signal ) as opposed to a limitation on data storage persistency (e.g., RAM vs. ROM).

[0230] The memory may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as semiconductor based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory. The data processors may be of any type suitable to the local technical environment, and may comprise one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors(DSPs), application specific integrated circuits (ASIC), FPGA, gate level circuits and processors based on multi core processor architecture, as non-limiting examples.

[0231] Various example embodiments of the disclosure may be practiced in various components such as integrated circuit modules. The design of integrated circuits is by and large a highly automated process. Complex and powerful software tools are available for converting a logic level design into a semiconductor circuit design ready to be etched and formed on a semiconductor substrate.

[0232] The scope of protection sought for various example embodiments of the disclosure is set out by the independent claims. The example embodiments and features thereof, if any, described in this disclosure that do not fall under the scope of the independent claims are to be interpreted as examples useful for understanding various example embodiments of the disclosure.

[0233] The foregoing description has provided, by way of non-limiting and illustrative examples, a full and informative description of the various example embodiments of this disclosure. However, various modifications and adaptations may become apparent to those skilled in the relevant arts in view of the foregoing description, when read in conjunction with the accompanying drawings and the claims. However, all such and similar modifications of the teachings will still fall within the various example embodiments of the disclosure as set forth in the claims. By way of non-limiting and illustrative example, there is a further example embodiment comprising a combination of one or more example embodiments with any of the other example embodiments previously discussed.

Claims

CLAIMS1 . A method performed by a transmitter entity, the method comprising: mapping, based on mapping information, one or more service data flows to a data radio bearer, wherein each of the one or more service data flows comprises a plurality of data packets; and transmitting, to a receiver entity, the data packets comprised in the one or more service data flows via the data radio bearer to which the one or more service data flows are mapped.

2. The method of claim 1 , wherein the mapping information comprises: one or more packet filter sets or one or more packet detection rules, each packet filter set or packet detection rule defining one or more characteristics of a service data flow; a data radio bearer identifier associated with each packet filter set or packet detection rule; and a precedence value associated with each packet filter set or packet detection rule.

3. The method of claim 2, wherein the mapping comprises: determining that one or more characteristics of the data packets of a service data flow match the one or more characteristics defined by one of the one or more packet filter sets or one of the one or more packet detection rules comprised in the mapping information; and based on the determining, mapping the data packets of the service data flow to the data radio bearer corresponding to the data radio bearer identifier associated with the one of the one or more packet filter sets or the one of the one or more packet detection rules comprised in the mapping information.

4. The method of claim 2 or 3, wherein the mapping information comprises a plurality of packet filter sets or a plurality of packet detection rules, and wherein the plurality of packet filter sets or the plurality of packet detection rules are applied in an order according to the precedence values associated with the plurality of packet filter sets or the plurality of packet detection rules comprised in the mapping information.

5. The method of any of claims 2 to 4, wherein the mapping comprises: inserting, into each data packet, a header comprising the data radio bearer identifier of the data radio bearer to which the service data flow comprising packet is mapped.

6. The method of any preceding claim, further comprising: receiving, from a control plane network function, the mapping information.

7. The method of any preceding claim, wherein the mapping comprises mapping a first service data flow and a second service data flow to a same data radio bearer, wherein the first service data flow and second service data flow have the same or similar characteristics.

8. The method of any preceding claim, wherein the mapping comprises mapping a third service data flow and a fourth service data flow to different data radio bearers, wherein the third service data flow and fourth service data flow have different characteristics.

9. The method of any preceding claim, wherein: the transmitter entity is an access user plane function and the receiver entity is a user equipment.

10. The method of claim 9, when dependent on claim 2, wherein the mapping information comprises the one or more packet detection rules, a data radio bearer identifier associated each packet detection rule; and a precedence value associated with each packet detection rule.11 . The method of claim 9 or 10, wherein the mapping comprises: receiving, from a control plane network function, information indicating that reflective service data flow to data radio bearer mapping is enabled for the user equipment; and inserting, into each of the plurality of data packets, a header comprising an indicator for enabling reflective service data flow to data radio bearer mapping at the user equipment.

12. The method of any of claims 1 to 8, wherein: the transmitter entity is a user equipment and the receiver entity is an access user plane function.

13. The method of claim 12 when dependent on claim 2, wherein the mapping information is comprised in one or more quality of service rules, wherein each quality of service rule comprises a packet filter set, a data radio bearer identifier associated a packet filter set; and a precedence value associated with the packet filter set.

14. The method of claim 13, wherein the method further comprises: receiving, from the access user plane function, one or more data packets comprising an indicator for enabling reflective service data flow to data radio bearer mapping at the user equipment; wherein the mapping comprises applying one or more user equipment derived quality of service rules based on receiving the indicator for enabling reflective service data flow to data radio bearer mapping at the user equipment.

15. The method of claim 14, further comprising: based on receiving the one or more data packets comprising the indicator for enabling reflective service data flow to data radio bearer mapping, determining whether a user equipment derived quality of service rule comprising mapping information with a packet filter set defining characteristics corresponding to the characteristics of the received one or more data packet exists; and based on the determining whether the user equipment derived quality of service rule comprising the mapping information with the packet filter set defining characteristics corresponding to the characteristics of the received one or more data packets exists, creating or updating the user equipment derived quality of service rule comprising mapping information with a packet filter set defining characteristics corresponding to the characteristics of the received one or more data packets.

16. The method of claim 15, wherein, in response to determining that no user equipment derived quality of service rule comprising the mapping information with the packet filter set defining characteristics corresponding to the characteristics of the received one or more data packets exists, the creating or updating comprises: creating a new user equipment derived quality of service rule comprising mapping information with a packet filter set defining characteristics corresponding to the characteristics of the received one or more data packets; and starting a timer associated with the new user equipment derived quality of service rule.

17. The method of claim 15, wherein, in response to determining that a user equipment derived quality of service rule comprising the mapping information with the packet filter set defining characteristics corresponding to the characteristics of the received one or more data packets exists, the creating or updating comprises:restarting a timer associated with the user equipment derived quality of service rule comprising the mapping information with the packet filter set defining characteristics corresponding to the characteristics of the received one or more data packets; determining whether the data radio bearer identifier associated with the received one or more data packets is different from the data radio bearer identifier associated with the user equipment derived quality of service rule comprising the mapping information with the packet filter set defining characteristics corresponding to the characteristics of the received one or more data packets; and updating the data radio bearer identifier associated with the user equipment derived quality of service rule comprising the mapping information with the packet filter set defining characteristics corresponding to the characteristics of the received one or more data packets based on the determining.

18. The method of claim 16 or 17, further comprising: determining that the timer associated with the user equipment quality of service mapping rule has expired; and in response to determining that the timer has expired, deleting the user equipment derived quality of service rule.

19. A transmitter entity comprising means for performing the method of any of claims 1 to 18.

20. A transmitter entity comprising at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the transmitter entity to perform the method of any of claims 1 to 18.21 . A transmitter entity comprising circuitry configured to perform the method of any of claims 1 to 18.

22. A computer program comprising instructions, wherein when the computer program is run on a transmitter entity, the transmitter entity is caused to perform the method of any of claims 1 to 18.

23. A computer-readable medium comprising instructions that, when executed by at least one processor of a transmitter entity, cause the transmitter entity to perform the method of any of claims 1 to 18.

Images