Method, apparatus and computer program

Abstract

A central unit control plane (CU-CP) function receives 1204, from a session management function (SMF), packet classification information and quality of service (QoS) requirements relating to a data session established for user equipment (UE). The SMF may have received 1202 the packet classification information and QoS requirements from a policy control function (PCF). The CU-CP function (or, alternatively, the SMF) determines 1206 (or 1408 fig.14) configuration information for an access user plane function (AUPF) and configuration information for the UE based on the packet classification information and the QoS requirements, wherein the configuration information for the AUPF and the configuration information for the UE comprise a data radio bearer identifier of a data radio bearer to which data packets of a service data flow having certain QoS characteristic are to be mapped. The CU-CP function (or SMF) sends 1212 (or 1414 fig.14), to the UE, the configuration information for the UE and sends 1208 (or 1410 fig.14), to the AUPF, the configuration information for the AUPF.

Description

TECHNICAL FIELD Various example embodiments of this disclosure relate to a method, apparatus, system and computer program for a communication network and in particular but not exclusively to methods, apparatuses, and systems for mapping data packets comprised in one or more service data flows to a data radio bearer. BACKGROUND A 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 cellular communication network is one example of a communication network. A communication device may be provided with a service by an application server. Such communication networks operate in according 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 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. According to an aspect, there is provided an apparatus comprising means for providing a central unit control plane function configured to perform: receiving, from a session management function, packet classification information and one or more quality of service requirements relating to a data session established for a user equipment; determining configuration information for an access user plane function and configuration information for the user equipment based at least in part on the packet classification information and the one or more quality of service requirements, wherein the configuration information for the access user plane function and the configuration information for the user equipment comprise a data radio bearer identifier of a data radio bearer to which data packets of a service data flow having certain quality of service characteristic are to be mapped; sending, to the user equipment, the configuration information for the user equipment; and sending, to the access user plane function, the configuration information for the access user plane function. The configuration information for the user equipment may comprise the one or more quality of service rules. Each quality of service rule may comprise: the data radio bearer identifier of the data radio bearer to which the data packets of the service data flow having certain quality of service characteristic are to be mapped; a packet filter set identifying one or more service data flows; and a precedence value determining the order in which a quality of service rule shall be applied. The configuration information for the access user plane function may comprise: one or more packet detection rules; one or more forwarding action rules; one or more quality of service enforcement rules; user equipment context setup information; and data radio bearer context setup information. Each packet detection rule may comprise: packet detection information indicating an identifier of a data radio bearer to be used to detect a data packet associated with a certain quality of service characteristic; and information indicating one or more rules for decapsulation of a header of the data packet. Each forwarding action rule may comprise information indicating how to perform packet encapsulation. Each quality of service enforcement rule may comprise: the data radio bearer identifier of the data radio bearer to which the data packets of the service data flow having certain quality of service characteristic are to be mapped; and information indicating whether reflective quality of service mapping service data flow to data radio bearer is enabled at the user equipment. The data radio bearer context setup information may comprise context setup information for a data radio bearer identified by a data radio bearer identifier. According to an aspect there is provided an apparatus comprising means for providing a session management function configured to perform: receiving, from a policy control function, packet classification information and one or more quality of service requirements relating to a data session for a user equipment; receiving, from a central unit control plane function, data radio bearer context information and user equipment context information; deriving configuration information for an access user plane function based on the packet classification information, the one or more quality of service requirements, and the data radio bearer context information, wherein the configuration information for the access user plane function comprises a data radio bearer identifier of a data radio bearer to which data packets of a service data flow having certain quality of service characteristic are to be mapped; deriving configuration information for the user equipment based on the packet classification information, the one or more quality of service requirements, and the data radio bearer context information, wherein the configuration information for the user equipment comprises a data radio bearer identifier of a data radio bearer to which data packets of a service data flow having certain quality of service characteristic are to be mapped; sending, to the user equipment, the derived configuration information for the user equipment; and sending, to the access user plane function, the derived configuration information for the access user plane function and the user equipment context information. The configuration information for the user equipment may comprise the one or more quality of service rules. Each quality of service rule may comprise: the data radio bearer identifier of the data radio bearer to which the data packets of the service data flow having certain quality of service characteristic are to be mapped; a packet filter set identifying one or more service data flows; and a precedence value determining the order in which a quality of service rule shall be applied. The configuration information for the access user plane function may comprise: one or more packet detection rules; one or more forwarding action rules; one or more quality of service enforcement rules; user equipment context setup information; and data radio bearer context setup information. Each packet detection rule may comprise: packet detection information indicating an identifier of a data radio bearer to be used to detect a data packet associated with a certain quality of service characteristic; and information indicating one or more rules for decapsulation of a header of the data packet. Each forwarding action rule may comprise information indicating how to perform packet encapsulation. Each quality of service enforcement rule may comprise: the data radio bearer identifier of the data radio bearer to which the data packets of the service data flow having certain quality of service characteristic are to be mapped; and information indicating whether reflective quality of service mapping service data flow to data radio bearer is enabled at the user equipment. The data radio bearer context setup information may comprise context setup information for a data radio bearer identified by a data radio bearer identifier. According to an aspect there is provided a user equipment comprising means for: receiving, from a session management function or central unit control plane function, configuration information for the user equipment, wherein the configuration information for the user equipment comprises a data radio bearer identifier of a data radio bearer to which data packets of a service data flow having certain quality of service characteristic are to be mapped; and based on the received configuration information for the user equipment, mapping one or more data packets comprised in one or more service data flows to a data radio bearer for a data session for the user equipment. The configuration information for the user equipment may comprise one or more quality of service rule, wherein each quality of service rule may comprise: the data radio bearer identifier of the data radio bearer to which the data packets of the service data flow having certain quality of service characteristic are to be mapped; and a packet filter set identifying one or more service data flows; and a precedence value determining the order in which a quality of service rule shall be applied. According to an aspect there is provided an apparatus comprising means for providing an access user plane function configured to perform: receiving, from a session management function or central unit control plane function, configuration information for the access user plane function, wherein the configuration information for the access user plane function comprises a data radio bearer identifier of a data radio bearer to which data packets of a service data flow having certain quality of service characteristic are to be mapped; based on the received configuration information for the access user plane function, mapping one or more data packets comprised in one or more service data flows to a data radio bearer; and sending the one or more packets mapped to the data radio bearer to a user equipment. The configuration information for the access user plane function may comprise: one or more packet detection rules; one or more forwarding action rules; one or more quality of service enforcement rules; user equipment context setup information; and data radio bearer context setup information. Each packet detection rule may comprise: packet detection information comprising an identifier of the data radio bearer to be used to detect a data packet associated with a certain quality of service characteristic; and information indicating one or more rules for decapsulation of a header of the data packet. Each forwarding action rule may comprise information indicating how to perform packet encapsulation. Each quality of service enforcement rule may comprise: the data radio bearer identifier of the data radio bearer to which the data packets of the service data flow having certain quality of service characteristic are to be mapped; and information indicating whether reflective quality of service mapping service data flow to data radio bearer is enabled at the user equipment. The data radio bearer context setup information may comprise context setup information for a data radio bearer identified by a data radio bearer identifier. According to an aspect, there is provided an 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: receive, from a session management function, packet classification information and one or more quality of service requirements relating to a data session established for a user equipment; determine configuration information for an access user plane function and configuration information for the user equipment based at least in part on the packet classification information and the one or more quality of service requirements, wherein the configuration information for the access user plane function and the configuration information for the user equipment comprise a data radio bearer identifier of a data radio bearer to which data packets of a service data flow having certain quality of service characteristic are to be mapped; send, to the user equipment, the configuration information for the user equipment; and send, to the access user plane function, the configuration information for the access user plane function. The configuration information for the user equipment may comprise the one or more quality of service rules. Each quality of service rule may comprise: the data radio bearer identifier of the data radio bearer to which the data packets of the service data flow having certain quality of service characteristic are to be mapped; a packet filter set identifying one or more service data flows; and a precedence value determining the order in which a quality of service rule shall be applied. The configuration information for the access user plane function may comprise: one or more packet detection rules; one or more forwarding action rules; one or more quality of service enforcement rules; user equipment context setup information; and data radio bearer context setup information. Each packet detection rule may comprise: packet detection information indicating an identifier of a data radio bearer to be used to detect a data packet associated with a certain quality of service characteristic; and information indicating one or more rules for decapsulation of a header of the data packet. Each forwarding action rule may comprise information indicating how to perform packet encapsulation. Each quality of service enforcement rule may comprise: the data radio bearer identifier of the data radio bearer to which the data packets of the service data flow having certain quality of service characteristic are to be mapped; and information indicating whether reflective quality of service mapping service data flow to data radio bearer is enabled at the user equipment. The data radio bearer context setup information may comprise context setup information for a data radio bearer identified by a data radio bearer identifier. According to an aspect, there is provided an 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: receive, from a policy control function, packet classification information and one or more quality of service requirements relating to a data session for a user equipment; receive, from a central unit control plane function, data radio bearer context information and user equipment context information; derive configuration information for an access user plane function based on the packet classification information, the one or more quality of service requirements, and the data radio bearer context information, wherein the configuration information for the access user plane function comprises a data radio bearer identifier of a data radio bearer to which data packets of a service data flow having certain quality of service characteristic are to be mapped; derive configuration information for the user equipment based on the packet classification information, the one or more quality of service requirements, and the data radio bearer context information, wherein the configuration information for the user equipment comprises a data radio bearer identifier of a data radio bearer to which data packets of a service data flow having certain quality of service characteristic are to be mapped; send, to the user equipment, the derived configuration information for the user equipment; and send, to the access user plane function, the derived configuration information for the access user plane function and the user equipment context information. The configuration information for the user equipment may comprise the one or more quality of service rules. Each quality of service rule may comprise: the data radio bearer identifier of the data radio bearer to which the data packets of the service data flow having certain quality of service characteristic are to be mapped; a packet filter set identifying one or more service data flows; and a precedence value determining the order in which a quality of service rule shall be applied. The configuration information for the access user plane function may comprise: one or more packet detection rules; one or more forwarding action rules; one or more quality of service enforcement rules; user equipment context setup information; and data radio bearer context setup information. Each packet detection rule may comprise: packet detection information indicating an identifier of a data radio bearer to be used to detect a data packet associated with a certain quality of service characteristic; and information indicating one or more rules for decapsulation of a header of the data packet. Each forwarding action rule may comprise information indicating how to perform packet encapsulation. Each quality of service enforcement rule may comprise: the data radio bearer identifier of the data radio bearer to which the data packets of the service data flow having certain quality of service characteristic are to be mapped; and information indicating whether reflective quality of service mapping service data flow to data radio bearer is enabled at the user equipment. The data radio bearer context setup information may comprise context setup information for a data radio bearer identified by a data radio bearer identifier. According to an aspect, there is provided an 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: receive, from a session management function or central unit control plane function, configuration information for a user equipment, wherein the configuration information for the user equipment comprises a data radio bearer identifier of a data radio bearer to which data packets of a service data flow having certain quality of service characteristic are to be mapped; and based on the received configuration information for the user equipment, map one or more data packets comprised in one or more service data flows to a data radio bearer for a data session for the user equipment. The configuration information for the user equipment may comprise one or more quality of service rule, wherein each quality of service rule may comprise: the data radio bearer identifier of the data radio bearer to which the data packets of the service data flow having certain quality of service characteristic are to be mapped; and a packet filter set identifying one or more service data flows; and a precedence value determining the order in which a quality of service rule shall be applied. According to an aspect, there is provided an 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: receive, from a session management function or central unit control plane function, configuration information for an access user plane function, wherein the configuration information for the access user plane function comprises a data radio bearer identifier of a data radio bearer to which data packets of a service data flow having certain quality of service characteristic are to be mapped; based on the received configuration information for the access user plane function, map one or more data packets comprised in one or more service data flows to a data radio bearer; and send the one or more packets mapped to the data radio bearer to a user equipment. The configuration information for the access user plane function may comprise: one or more packet detection rules; one or more forwarding action rules; one or more quality of service enforcement rules; user equipment context setup information; and data radio bearer context setup information. Each packet detection rule may comprise: packet detection information comprising an identifier of the data radio bearer to be used to detect a data packet associated with a certain quality of service characteristic; and information indicating one or more rules for decapsulation of a header of the data packet. Each forwarding action rule may comprise information indicating how to perform packet encapsulation. Each quality of service enforcement rule may comprise: the data radio bearer identifier of the data radio bearer to which the data packets of the service data flow having certain quality of service characteristic are to be mapped; and information indicating whether reflective quality of service mapping service data flow to data radio bearer is enabled at the user equipment. The data radio bearer context setup information may comprise context setup information for a data radio bearer identified by a data radio bearer identifier According to an aspect, there is provided a method for a central unit control plane function, the method comprising: receiving, from a session management function, packet classification information and one or more quality of service requirements relating to a data session established for a user equipment; determining configuration information for an access user plane function and configuration information for the user equipment based at least in part on the packet classification information and the one or more quality of service requirements, wherein the configuration information for the access user plane function and the configuration information for the user equipment comprise a data radio bearer identifier of a data radio bearer to which data packets of a service data flow having certain quality of service characteristic are to be mapped; sending, to the user equipment, the configuration information for the user equipment; and sending, to the access user plane function, the configuration information for the access user plane function. The configuration information for the user equipment may comprise the one or more quality of service rules. Each quality of service rule may comprise: the data radio bearer identifier of the data radio bearer to which the data packets of the service data flow having certain quality of service characteristic are to be mapped; a packet filter set identifying one or more service data flows; and a precedence value determining the order in which a quality of service rule shall be applied. The configuration information for the access user plane function may comprise: one or more packet detection rules; one or more forwarding action rules; one or more quality of service enforcement rules; user equipment context setup information; and data radio bearer context setup information. Each packet detection rule may comprise: packet detection information indicating an identifier of a data radio bearer to be used to detect a data packet associated with a certain quality of service characteristic; and information indicating one or more rules for decapsulation of a header of the data packet. Each forwarding action rule may comprise information indicating how to perform packet encapsulation. Each quality of service enforcement rule may comprise: the data radio bearer identifier of the data radio bearer to which the data packets of the service data flow having certain quality of service characteristic are to be mapped; and information indicating whether reflective quality of service mapping service data flow to data radio bearer is enabled at the user equipment. The data radio bearer context setup information may comprise context setup information for a data radio bearer identified by a data radio bearer identifier. According to an aspect there is provided a method for a session management function, the method comprising: receiving, from a policy control function, packet classification information and one or more quality of service requirements relating to a data session for a user equipment; receiving, from a central unit control plane function, data radio bearer context information and user equipment context information; deriving configuration information for an access user plane function based on the packet classification information, the one or more quality of service requirements, and the data radio bearer context information, wherein the configuration information for the access user plane function comprises a data radio bearer identifier of a data radio bearer to which data packets of a service data flow having certain quality of service characteristic are to be mapped; deriving configuration information for the user equipment based on the packet classification information, the one or more quality of service requirements, and the data radio bearer context information, wherein the configuration information for the user equipment comprises a data radio bearer identifier of a data radio bearer to which data packets of a service data flow having certain quality of service characteristic are to be mapped; sending, to the user equipment, the derived configuration information for the user equipment; and sending, to the access user plane function, the derived configuration information for the access user plane function and the user equipment context information. The configuration information for the user equipment may comprise the one or more quality of service rules. Each quality of service rule may comprise: the data radio bearer identifier of the data radio bearer to which the data packets of the service data flow having certain quality of service characteristic are to be mapped; a packet filter set identifying one or more service data flows; and a precedence value determining the order in which a quality of service rule shall be applied. The configuration information for the access user plane function may comprise: one or more packet detection rules; one or more forwarding action rules; one or more quality of service enforcement rules; user equipment context setup information; and data radio bearer context setup information. Each packet detection rule may comprise: packet detection information indicating an identifier of a data radio bearer to be used to detect a data packet associated with a certain quality of service characteristic; and information indicating one or more rules for decapsulation of a header of the data packet. Each forwarding action rule may comprise information indicating how to perform packet encapsulation. Each quality of service enforcement rule may comprise: the data radio bearer identifier of the data radio bearer to which the data packets of the service data flow having certain quality of service characteristic are to be mapped; and information indicating whether reflective quality of service mapping service data flow to data radio bearer is enabled at the user equipment. The data radio bearer context setup information may comprise context setup information for a data radio bearer identified by a data radio bearer identifier. According to an aspect there is provided a method for a user equipment, the method comprising: receiving, from a session management function or central unit control plane function, configuration information for the user equipment, wherein the configuration information for the user equipment comprises a data radio bearer identifier of a data radio bearer to which data packets of a service data flow having certain quality of service characteristic are to be mapped; and based on the received configuration information for the user equipment, mapping one or more data packets comprised in one or more service data flows to a data radio bearer for a data session for the user equipment. The configuration information for the user equipment may comprise one or more quality of service rule, wherein each quality of service rule may comprise: the data radio bearer identifier of the data radio bearer to which the data packets of the service data flow having certain quality of service characteristic are to be mapped; and a packet filter set identifying one or more service data flows; and a precedence value determining the order in which a quality of service rule shall be applied. According to an aspect there is provided a method for an access user plane function, the method comprising: receiving, from a session management function or central unit control plane function, configuration information for the access user plane function, wherein the configuration information for the access user plane function comprises a data radio bearer identifier of a data radio bearer to which data packets of a service data flow having certain quality of service characteristic are to be mapped; based on the received configuration information for the access user plane function, mapping one or more data packets comprised in one or more service data flows to a data radio bearer; and sending the one or more packets mapped to the data radio bearer to a user equipment. The configuration information for the access user plane function may comprise: one or more packet detection rules; one or more forwarding action rules; one or more quality of service enforcement rules; user equipment context setup information; and data radio bearer context setup information. Each packet detection rule may comprise: packet detection information comprising an identifier of the data radio bearer to be used to detect a data packet associated with a certain quality of service characteristic; and information indicating one or more rules for decapsulation of a header of the data packet. Each forwarding action rule may comprise information indicating how to perform packet encapsulation. Each quality of service enforcement rule may comprise: the data radio bearer identifier of the data radio bearer to which the data packets of the service data flow having certain quality of service characteristic are to be mapped; and information indicating whether reflective quality of service mapping service data flow to data radio bearer is enabled at the user equipment. The data radio bearer context setup information may comprise context setup information for a data radio bearer identified by a data radio bearer identifier. According to an aspect, there is provided a computer readable medium comprising instructions which, when executed by an apparatus, cause the apparatus to perform at least the following: receiving, from a session management function, packet classification information and one or more quality of service requirements relating to a data session established for a user equipment; determining configuration information for an access user plane function and configuration information for the user equipment based at least in part on the packet classification information and the one or more quality of service requirements, wherein the configuration information for the access user plane function and the configuration information for the user equipment comprise a data radio bearer identifier of a data radio bearer to which data packets of a service data flow having certain quality of service characteristic are to be mapped; sending, to the user equipment, the configuration information for the user equipment; and sending, to the access user plane function, the configuration information for the access user plane function. The configuration information for the user equipment may comprise the one or more quality of service rules. Each quality of service rule may comprise: the data radio bearer identifier of the data radio bearer to which the data packets of the service data flow having certain quality of service characteristic are to be mapped; a packet filter set identifying one or more service data flows; and a precedence value determining the order in which a quality of service rule shall be applied. The configuration information for the access user plane function may comprise: one or more packet detection rules; one or more forwarding action rules; one or more quality of service enforcement rules; user equipment context setup information; and data radio bearer context setup information. Each packet detection rule may comprise: packet detection information indicating an identifier of a data radio bearer to be used to detect a data packet associated with a certain quality of service characteristic; and information indicating one or more rules for decapsulation of a header of the data packet. Each forwarding action rule may comprise information indicating how to perform packet encapsulation. Each quality of service enforcement rule may comprise: the data radio bearer identifier of the data radio bearer to which the data packets of the service data flow having certain quality of service characteristic are to be mapped; and information indicating whether reflective quality of service mapping service data flow to data radio bearer is enabled at the user equipment. The data radio bearer context setup information may comprise context setup information for a data radio bearer identified by a data radio bearer identifier. According to an aspect, there is provided a computer readable medium comprising instructions which, when executed by an apparatus, cause the apparatus to perform at least the following: receiving, from a policy control function, packet classification information and one or more quality of service requirements relating to a data session for a user equipment; receiving, from a central unit control plane function, data radio bearer context information and user equipment context information; deriving configuration information for an access user plane function based on the packet classification information, the one or more quality of service requirements, and the data radio bearer context information, wherein the configuration information for the access user plane function comprises a data radio bearer identifier of a data radio bearer to which data packets of a service data flow having certain quality of service characteristic are to be mapped; deriving configuration information for the user equipment based on the packet classification information, the one or more quality of service requirements, and the data radio bearer context information, wherein the configuration information for the user equipment comprises a data radio bearer identifier of a data radio bearer to which data packets of a service data flow having certain quality of service characteristic are to be mapped; sending, to the user equipment, the derived configuration information for the user equipment; and sending, to the access user plane function, the derived configuration information for the access user plane function and the user equipment context information. The configuration information for the user equipment may comprise the one or more quality of service rules. Each quality of service rule may comprise: the data radio bearer identifier of the data radio bearer to which the data packets of the service data flow having certain quality of service characteristic are to be mapped; a packet filter set identifying one or more service data flows; and a precedence value determining the order in which a quality of service rule shall be applied. The configuration information for the access user plane function may comprise: one or more packet detection rules; one or more forwarding action rules; one or more quality of service enforcement rules; user equipment context setup information; and data radio bearer context setup information. Each packet detection rule may comprise: packet detection information indicating an identifier of a data radio bearer to be used to detect a data packet associated with a certain quality of service characteristic; and information indicating one or more rules for decapsulation of a header of the data packet. Each forwarding action rule may comprise information indicating how to perform packet encapsulation. Each quality of service enforcement rule may comprise: the data radio bearer identifier of the data radio bearer to which the data packets of the service data flow having certain quality of service characteristic are to be mapped; and information indicating whether reflective quality of service mapping service data flow to data radio bearer is enabled at the user equipment. The data radio bearer context setup information may comprise context setup information for a data radio bearer identified by a data radio bearer identifier. According to an aspect, there is provided a computer readable medium comprising instructions which, when executed by a user equipment, cause the user equipment to perform at least the following: receiving, from a session management function or central unit control plane function, configuration information for the user equipment, wherein the configuration information for the user equipment comprises a data radio bearer identifier of a data radio bearer to which data packets of a service data flow having certain quality of service characteristic are to be mapped; and based on the received configuration information for the user equipment, mapping one or more data packets comprised in one or more service data flows to a data radio bearer for a data session for the user equipment. The configuration information for the user equipment may comprise one or more quality of service rule, wherein each quality of service rule may comprise: the data radio bearer identifier of the data radio bearer to which the data packets of the service data flow having certain quality of service characteristic are to be mapped; and a packet filter set identifying one or more service data flows; and a precedence value determining the order in which a quality of service rule shall be applied. According to an aspect, there is provided a computer readable medium comprising instructions which, when executed by an apparatus, cause the apparatus to perform at least the following: receiving, from a session management function or central unit control plane function, configuration information for an access user plane function, wherein the configuration information for the access user plane function comprises a data radio bearer identifier of a data radio bearer to which data packets of a service data flow having certain quality of service characteristic are to be mapped; based on the received configuration information for the access user plane function, mapping one or more data packets comprised in one or more service data flows to a data radio bearer; and sending the one or more packets mapped to the data radio bearer to a user equipment. The configuration information for the access user plane function may comprise: one or more packet detection rules; one or more forwarding action rules; one or more quality of service enforcement rules; user equipment context setup information; and data radio bearer context setup information. Each packet detection rule may comprise: packet detection information comprising an identifier of the data radio bearer to be used to detect a data packet associated with a certain quality of service characteristic; and information indicating one or more rules for decapsulation of a header of the data packet. Each forwarding action rule may comprise information indicating how to perform packet encapsulation. Each quality of service enforcement rule may comprise: the data radio bearer identifier of the data radio bearer to which the data packets of the service data flow having certain quality of service characteristic are to be mapped; and information indicating whether reflective quality of service mapping service data flow to data radio bearer is enabled at the user equipment. The data radio bearer context setup information may comprise context setup information for a data radio bearer identified by a data radio bearer identifier. 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. 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 Some example embodiments will now be described, by way of non-limiting and illustrative example only, with reference to the accompanying Figures (FIG.s) in which: FIG. 1 shows a schematic representation of a 5G communication system of a communication network; FIG. 2 illustrates example RAN architectures; FIG. 3 illustrates a procedure for classification and marking of QoS flows and mapping of QoS flows to RAN resources; FIG. 4 shows method performed by a CU-UP according to some examples; FIG. 5 shows a method performed by a SMF according to some examples; FIG. 6 shows a method performed by a UE according to some examples; FIG. 7 shows a method performed by a AUSF according to some examples; FIG.8 illustrates a communication network having a first example architecture; FIG. 9shows an example procedure for deriving configuration information involving entities of the communication network having the first example architecture; FIG. 10 shows an example procedure for deriving configuration information involving entities of a communication network having the first example architecture; FIG. 11 illustrates a communication network having a second example architecture; FIG. 12 shows an example procedure for configuring a UE and AUPF with configuration information involving entities of the communication network having the second example architecture; FIG. 13 illustrates a communication network having a third example architecture; FIG. 14 shows an example procedure for configuring a UE and AUPF with configuration information involving entities of the communication network having the third example architecture; FIG. 15 illustrates a communication network having a fourth example architecture; FIG. 16 shows an example procedure for configuring a UE and AUPF with configuration information involving entities of the communication network having the fourth example architecture; FIG. 17 illustrates an example of a communication device; FIG. 18 shows a schematic representation of non-volatile memory media according to some examples. DETAILED DESCRIPTION A non-exhaustive list of some abbreviations used throughout the present disclosure is provided below for reference: 5GS: 5G System AMBR: Aggregate Maximum Bit Rate AUPF: Access User Plane Function DRB: Data Radio Bearer gNB: gNodeB gNB-CU-CP: gNB-Central Unit-Control Plane gNB-CU-UP: gNB-Central Unit-User Plane gNB-DU: gNB-Distributed Unit GTP: GPRS Tunnelling Protocol PDCP: Packet Data Convergence Protocol PDR: Packet Detection Rule QER: QoS Enforcement Rule QFI: QoS Flow Indicator QoS: Quality of Service RAN: Radio Access Network RDI: Reflective QoS flow to DRB Mapping Indicator RQI: Reflective QoS Indicator RRC: Radio Resource Control (Protocol) RSARI: Reflective SDF to AN Resource Indicator SDAP: Service Data Adaptation Protocol SDF: Service Data Flow UE: User Equipment UPF: User Plane Function 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). 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). 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. 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. 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. 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-specific resource, 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. 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 RDM, 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. 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. 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). 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 cellular system because packet processing performed by the AUPF is simplified relative to the packet processing performed by both the CU-UP and the UPF. 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. As will be explained in more detail below, in order to enable the one-step mapping of SDF to DRB, the AUPF and UE need to be provided with the necessary information for one-step mapping of SDF to DRB. 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. FIG. 1 shows a schematic representation ofa5GS of a communication network (e.g., acellular 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). 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. 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. 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 - user planes (CU-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. FIG. 3 illustrates an example known procedure for classification and marking of QoS flows and mapping of QoS flows to RAN resources described in 3GPP TS 23.501, clause 5.7.1.5. As illustrated in FIG. 3, 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. The QoS configuration may be provided via E1 and N4 messages by the CU-CP 204 in the RAN 101 and SMF 109 in the core network, since the QoS handling is done by CU-UP 206 and UPF 110 separately. This may lead to overlapped configuration parameters, additional CP signalling to coordinate CU-UP 206 and UPF 110 QoS handling, complex configuration procedure, etc. As explained above, in some communication networks, a RAN-core converged network function that replaces and has the same or similar functionality as the CU-UP and UPF entities may be provided. A communication network that includes a RAN-core converged network function may be referred to as having a RAN-core converged architecture. The RAN-core converged network function (e.g., AUFP) may optimize QoS handling. However, the CP faces the challenge of configuring a unified QoS model (where SDF is mapped to DRB in one step), since QoS-related packet classification and DRB-related radio resource- information may not be originated from the same CP NF, for example where the QoS related packet classification information is available at SMF while the DRB-related radio resource is available at CU-CP. More specifically, the SMF 109 may have information relating to the application flows (SDFs) and may derive the associated QoS flows, but the SMF 109 may not have information relating to the DRBs; whereas the CU-CP 204 may have information relating to the radio resources and configures the DRBs accordingly, but the CU-CP 204 may not have information about the SDFs and their QoS. Therefore, neither SMF 109 nor CU-CP 204 can currently configure a one-step QoS mapping alone. New configuration information and procedures are needed to configure the unified QoS model. Some examples of the present disclosure provide mechanisms for providing the AUPF and UE with the configuration information for performing the mapping. In particular, the present disclosure presents four different control plane architectures and signalling procedures that may be utilized to configure the AUPF and UE with the configuration information. Reference is made to FIG. 4, which shows a flowchart of an example method performed by a CU-CP of a communication network, for example, CU-CP 204 of the communication network having a first example architecture as shown in FIG. 8 and described in detail below, CU-CP 204 of the communication network having a second example architecture as shown in FIG. 11 and described in, or the CU-CP 204 of the communication network having a third example architecture as shown in FIG. 13 and described in detail below. The method begins at 400. At 400, the CU-CP receives, from a session management function, packet classification information and one or more quality of service requirements relating to a data session established for a user equipment. At 402 the CU-CP determines configuration information for an access user plane function based at least in part on the packet classification information and the one or more quality of service requirements, wherein the configuration information for the access user plane function comprises a data radio bearer identifier of a data radio bearer to which data packets of a service data flow having certain quality of service characteristic are to be mapped. At 403, the CU-CP determines configuration information for the user equipment based at least in part on the packet classification information and the one or more quality of service requirements, wherein the configuration information for the data radio bearer identifier of a data radio bearer to which data packets of a service data flow having certain quality of service characteristic are to be mapped. At 404 the CU-CP sends, to the user equipment, the configuration information for the user equipment. At 406 the CU-CP sends, to the access user plane function, the configuration information for the access user plane function. Reference is now made to FIG. 5, which shows a flowchart of an example method performed by a SMF of a communication network, for example, SMF 109 to the communication network having a first example architecture as shown in FIG. 8 and described in detail below, SMF 109 of the communication network having a second architecture as shown in FIG. 11 and described in detail below, SMF 109 of the communication network having a third architecture as shown in FIG. 13 and described in detail below. The method begins at 500. At 502, the SMF receives, from a policy control function, packet classification information and one or more quality of service requirements relating to a data session for a user equipment. At 504 the SMF receives, from a central unit control plane function, data radio bearer context information and user equipment context information. At 506, the SMF derives configuration information for an access user plane function based on the packet classification information, the one or more quality of service requirements, and the data radio bearer context information, wherein the configuration information for the access user plane function comprises a data radio bearer identifier of a data radio bearer to which data packets of a service data flow having certain quality of service characteristic are to be mapped. At 508 the SMF derives configuration information for the user equipment based on the packet classification information, the one or more quality of service requirements, and the data radio bearer context information, wherein the configuration information for the user equipment comprises a data radio bearer identifier of a data radio bearer to which data packets of a service data flow having certain quality of service characteristic are to be mapped. At 510, the SMF sends, to the user equipment, the derived configuration information for the user equipment. At 512 the SMF sends, to the access user plane function, the derived configuration information for the access user plane function and the user equipment context information. Reference is now made to FIG. 6, which shows a flowchart of an example method performed by a UE that is communicating with a communication network, for example, UE 100 communicating with a communication network having a first example architecture as shown in FIG. 8 and described in detail below, UE 100 communicating with a communication network having a second example architecture as shown in FIG. 11 and described in detail below, UE 100 communicating with of a communication network having a third example architecture as shown in FIG. 13 and described in detail below., or UE 100 communicating with a communication network having a fourth example architecture as shown in FIG. 15 and described in detail below. The method begins at 602. At 602, the UE receives, from a session management function or central unit control plane function, configuration information for the user equipment, wherein the configuration information for the user equipment comprises a data radio bearer identifier of a data radio bearer to which data packets of a service data flow having certain quality of service characteristic are to be mapped. At 604, the UE, based on the received configuration information for the user equipment, maps one or more data packets comprised in one or more service data flows to a data radio bearer for a data session for the user equipment. Reference is now made to FIG.7, which shows a flowchart of an example method performed by an access user plane function (AUPF) of a communication network, for example, AUPF 300 of the communication network having a first example architecture as shown in FIG. 8 and described in detail below, AUPF 300 of the communication network having a second example architecture as shown in FIG.11 and described in detail below, AUPF 300 of the communication network having a third example architecture as shown in FIG. 12 and described in detail below, or AUPF 300 of the communication network having a fourth example architecture as shown in FIG. 8 and described in detail below At 702, the AUPF receives, from a session management function or central unit control plane function, configuration information for the access user plane function, wherein the configuration information for the access user plane function comprises a data radio bearer identifier of a data radio bearer to which data packets of a service data flow having certain quality of service characteristic are to be mapped. At 702, the AUPF, based on the received configuration information for the access user plane function, mapping one or more data packets comprised in one or more service data flows to a data radio bearer. At 704, the AUFP sends the one or more packets mapped to the data radio bearer to a user equipment. In some examples, a control plane network function (CP-NF) may obtain information (e.g., PDR, FAR, QER, UE context information and DRB configuration information) from one or more CP-NFs (e.g., PCF), so that the CP-NF can derive the configuration information for the AUPF 300 and UE 100 for performing one-step mapping of SDF to DRB. As will be described in further detail below, in some examples, at least one control plane network function may provide the UE 100 and AUPF 300 with the configuration information for performing the one-step mapping of SDF to DRB. The at least one control plane network function may comprise one of: SMF 109 and CU-CP 204; SMF 109; CU-CP 204; or a new CP-NF 1200. In the following, the naming of specific rules of the configuration information is partially borrowed from the information terminology in 5GS, such as PDR, FAR, and QER, because the rules of the configuration information may provide similar functions. It should be understood that this naming does not imply that the specific rules of the proposed configuration information must be based on the same rules as in 5GS. The configuration information as described herein is not limited to any specific interface between CP and UP, e.g., E1 or N4. In some examples, the configuration information for the AU PF 300 may comprise non-QoS related configuration information and / or QoS related configuration information. The non-QoS related configuration information may comprise one or more of: Usage Reporting Rules (URRs), Multi-Access Rules (MARs), and Session Reporting Rules (SRRs). URRs may comprise information that defines how traffic identified by PDR(s) are accounted as well as how certain measurements are reported. Multi-Access Rules (MAR) contains information on how to handle traffic steering, switching and splitting for a Multi-Access PDU Session. SRRs contains information to request the UP function to detect and report events for a PDU session that are not related to specific PDRs of the PDU session or that are not related to traffic usage measurement. The QoS related configuration information may comprise one or more of: A packet detection rule (PDR) for the unified QoS model; A forwarding action rule (FAR) for the unified QoS model; A QoS enforcement rule (QER) for the unified QoS model; UE context setup information for the unified QoS model; and DRB context setup information for the unified QoS model. The Packet Detection Rule (PDR) for the unified QoS model comprises information defining how to classify a packet arriving at the AUPF 300. Each PDR may be used to detect packets in a certain transmission direction, for example uplink or downlink. The PDR may define packet detection information indicating a DRB ID (instead of QoS Flow Identifier (QFI) as per existing 5G standards) to be used to detect a packet (e.g., an uplink packet received from a UE) associated with certain QoS characteristics. For example, the PDR may indicate that data packets associated with a first QoS characteristic value (e.g., a first bit error rate) are to be detected using a first DRB, while data packets associated with a second QoS characteristic value (e.g., a second bit error rate) are to be detected using a second DRB. In some examples, the data packets may comprise a SDAP packet header. In some examples, the PDR may comprise parameters / rules for the decapsulation of the SDAP packet header in the way of outer header removing (in contrast to the decapsulation of SDAP packet header being set separately, for example in a message received via the E1 interface as per existing 5G standards). The Forwarding Action Rule (FAR) for the unified QoS model comprises information defining how to perform packet encapsulation. In some examples, the FAR may comprise parameters / rules for encapsulation of the SDAP packet header in the way of outer header addition. The QoS Enforcement Rule (QER) for the unified QoS model comprises information defining how a packet is treated by the AUPF or UE in terms of limiting the bit rate, marking packets for QoS purposes, and selecting DRBs based on required QoS levels. In some examples, when packets of SDF arrive at the AUPF 300, they may be classified based on the PDR(s). The PDR(s) may indicate an associated QER that comprises a DRB ID of a DRB to be used according to that rule. In some examples, a packet filter set indicated in a PDR may be used to detect packets, without a determined DRB ID (since the DRB ID may not yet have been determined, for example the packets arrive at the AUPF 300 from the application / service layer). Once the packets are detected by the given packet filter set of a certain PDR, a list of QER ID(s) defined in the corresponding PDR can be determined. Among these QER listed in the determined QER ID(s) list, the QER with the highest precedence may be selected. The selected QER may comprise the DRB ID to which the packets are to be mapped. In some examples, packets that are linked to the same QER after matching with a certain PDR may require the same QoS requirements and may therefore share the same DRB. These matched packets may therefore be marked with the identical DRB ID. To realize the one-step QoS mapping, a DRB ID indicating a DRB to be mapped may be defined in the QER. In some examples, the DRB ID can be used to detect packets with certain QoS characteristic, such as when the QoS mapping of the packets has been done by another node (e.g., the UE) and a DRB ID has been inserted in the packets. For example, for the purpose of packet inspection, the DRB ID can be used to detect UL packets from UE, so that the AUPF 300 can inspect a packet with certain QoS characteristic (e.g., a certain DRB ID). Before the packets arrive at AUPF 300, the UE has mapped the UL packets to a certain DRB based on UE's QoS rules, and UE has inserted a DRB ID in the UL packets. As explained previously, in some cases reflective QoS may be enabled for the UE 100 to allow the UE 100 to map UL User Plane traffic to QoS Flows without QoS rules being provided by a control plane network function, for example, a CU-UP or a SMF. This may be achieved by creating UE derived QoS rules in the UE 100 based on the received DL traffic. However, with the introduction of a one-step mapping of SDF to DRB, modifications to existing reflective QoS mechanisms may be required. In some examples, the QER may indicate whether reflective QoS is enabled at the UE 100, for example by including an indicator in the header of data packets transmitted to the UE 100. The indicator may comprise a Reflective SDF to AN Resource Indicator (RSARI) parameter, for indicating that reflective mapping of SDF to AN resource may be performed by the UE 100. It is noted that the AN Resource Indicator is a generic term that includes but is not limited to the identifier of a DRB (generally referred to as DRB ID). The QER may define the configuration for DL marking to include the RSARI in the header of data packets transmitted to the UE 100. For example, the QER may indicate that an RSARI bit in the header of packets of a specific SDF should be set to 1 when reflective QoS is determined to be used for the specific SDF. Since a given PDU session may carry traffic from several SDFs, both QoS and Reflective QoS packets can co-exist within the same session. Accordingly, in such examples the Reflective QoS Indicator (RQI) and Reflective QoS DRB Indicator (RDI) as defined in existing 5G standards are not needed. In some examples the inclusion of the RSARI in the header may be performed by outer header removal or creation, which may be configured by a control plane network function (e.g., SMF, CU-CP, or control plane network function (CP-NF) including some or all of the functionality of the CU-CP and SMF) in the PDR and / or FAR. In some examples the QER may indicate if RSARI should be inserted in SDAP header or PDCP header with SDAP bypass when reflective QoS is enabled. For example, a header usage indicator bit can be set to 1 for using SDAP to insert the RSARI header. In some examples the usage of SDAP or PDCP for this purpose may be pre-defined. The UE Context Setup information for the unified QoS model comprises UE-related context information, such as security information, UE DL AMBR and other UE-related configuration information (e.g., information carried in the E1AP message defined in Clause 9.2.2.1 in TS 37.483, except for the “DRB to Setup List” and “PDU Session Resource to Setup List” lEs). The DRB Context Setup information for the unified QoS model comprises DRB context information for configuring the DRB. As mentioned previously, the DRB ID (instead of QFI) may be used to identify packet’s QoS requirement. In some examples the DRB context setup information may comprise information associated with header marking. For example, if the SDAP header is used for reflective QoS marking, RSARI insertion of SDAP may be configured in DRB Context Setup. If the SDAP is bypassed and PDCP header is used, RSARI insertion of PDCP may be configured in DRB Context Setup. Other PDCP configuration may also be indicated in the DRB Context Setup. In some examples the configuration information for the UE 100 may comprise one or more QoS rules comprising mapping information. The mapping information may indicate the association of SDF to DRB. The mapping information may comprise an identifier of the DRB, a packet filter set, and a precedence value. Each packet filter set may comprise one or more packet filters. The one or more packet filters define one or more characteristics (e.g., QoS characteristics) of an SDF. When SDFs with characteristics matching the one or more packet filters are received, the mapping information is such that the SDFs are mapped to a DRB corresponding to the DRB ID comprised in the rule. That is to say, the transmitter entity may, for each QoS rule, determine that characteristics of a given SDF match the characteristics defined by the packet filter set, and based on the determining the transmitter entity may map the given SDF to a DRB corresponding to the DRB ID comprised in the mapping information comprised in the respective QoS rule. The precedence value may determine the order in which a QoS rule shall be applied. When there is more than one mapping information, the application of the mapping information may be performed in increasing order of the precedence value. The configuration information for the UE 100 may be explicitly provided to the UE 100, e.g., during establishment of a PDU Session and / or during modification of an existing PDU session. The message used to send the configuration information for the UE 100 from control plane network function to UE 100 may in some examples be either NAS message or AS message. Whether the message is a NAS message or AS message may depend on whether a core CP NF or a RAN CP NF derives the configuration information for the one-step mapping. For example, when a core CP NF derives the configuration information for the UE 100, the configuration information for the UE may be provided to the UE 100 in a NAS message, whereas when a RAN CP NF derives the configuration information for the UE, the configuration information may be provided to the UE 100 in a AS message. In some examples the configuration information for the UE 100 may be pre-configured in the UE 100; or implicitly derived by the UE 100 by applying Reflective QoS based on the RSARI. In some examples, there may be a default configuration information for UE comprising an identifier of a default DRB (“default DRB ID”) which is used by the UE if none of the other mapping information included in the configuration information applies to a given packet. Example network architectures and procedures for configuring the AU PF 300 and configuring UE 100 with the configuration information for one-step mapping from SDF to DRB are described below in relation to FIGs. 8 to 16. FIG. 8 illustrates a communication network having a first example architecture. In the communication network shown in FIG. 8, CU-CP 204 and SMF 109 may both configure the AUPF 300 with at least part of the configuration information for the AUPF 300 (e.g., non-QoS related configuration information, such as the URRs, MARs, SSRs described previously, and QoS related configuration information, such as the PDR(s), FAR(s), QER(s), UE context setup information, DRB context setup information described previously). The CU-CP 204 and SMF 109 may convey the parts of the configuration information via two different interfaces to the AUPF 300 - for example the E1 interface for CU-CP 204 and N4 interface for the SMF 109. The dashed lines in FIG. 8 and subsequent FIGs. 13 and 15 represent interfaces for NAS messages, while the solid lines represent interfaces for control plane messages and user plane messages. There are two example procedures for deriving configuration information, depending on whether the CU-CP 204 or SMF 109 derives the QoS-related configuration information for the AUPF and UE are now described with reference to the communication network having the first example architecture. Reference is made to FIG. 9, which shows an example procedure for deriving configuration information involving entities of the communication network having the first example architecture. In the procedure in FIG. 9, the CU-CP 204 derives the QoS-related configuration information for the UE 100 and AUPF 300. At 900, the SMF 109 initiates the QoS configuration and sends a request to the PCF for QoS related information. The SMF 109 may initiate the QoS configuration as part of a PDU Session Establishment procedure or a PDU Session Modification procedure. For example, the SMF may initiate the QoS configuration at 900 when a session management policy modification is initiated during a PDU session establishment procedure or a PDU session modification procedure. At 902, the PCF may send a response to the request (received from SMF 109 at step 600) to the SMF 109. The response may comprise policy information including packet classification information and QoS requirements, e.g., QoS profile. At 904, the SMF 109 derives a first part of the configuration information forthe AUPF 300. The first part of the configuration information for the AUPF 300 may comprise non-QoS related configuration information, e.g., Usage Reporting Rules (URRs), Multi-Access Rules (MARs), Session Reporting Rules (SRRs). The SMF 109 may derive the first part of the configuration information for the AUPF 300 based at least in part on the policy information received from the PCF. In some examples the SMF 109 may receive further information from AMF 108 and derive the first part of the configuration information for the AUPF 300 based further on the further information. For example, the SMF 109 may receive, from the AMF 108, session management context information (e.g., via a session management context create / update message) and derive the first part of the configuration information for the AUPF 300 based further on the session management context information. At 906 the SMF 109 sends, to the AUPF 300, the first part of the configuration information (e.g., the non-QoS related configuration information, such as the URRs, MARs, SSRs described previously) for the AUPF 300. Optionally at 908, the AUPF 300 may respond with an acknowledgement of receipt of the first part of the configuration information for the AUPF 300. At 910, the SMF 109 sends, to the CU-CP 204, packet classification information and QoS requirements (received from the PCF). While not shown in FIG. 9, in some examples this may be sent from SMF 109 to CU-CP 204 via the AMF 108. At 912, the CU-CP 204 derives the configuration information forthe UE 100 and a second part of the configuration information for the AUPF 300. The configuration information for the UE 100 may comprise the one or more QoS rules as described previously. The second part of the configuration information for the AUPF 300 may comprise QERs with one-step mapping setup and optionally the marking definition (e.g., if SDAP or PDCP is used for reflective QoS marking, QoS remapping), PDRs, FARs, UE context setup information, and DRB context setup information as described previously. For example, the CU-CP 204 may derive the one or more QERs based on the QoS requirements received from the SMF 109. The CU-CP 204 may then derive the second part of the configuration information based on the one or more QERs, PDRs, FARs (derived by the CU-CP 204), and the UE context setup information and DRB context information (available at the CU-CP 204). At 914 the CU-CP 204 sends the second part of the configuration information for the AUPF 300 to the AUPF 300. Optionally at 916 the AUPF 300 may respond with an acknowledgement of receipt of the second part of the configuration information for the AUPF 300. At 918 the CU-CP 204 sends the configuration information for the UE 100 to the UE 100. In some examples the CU-CP 204 may send the configuration information for the UE to the UE 100 via AS protocol signalling. Optionally at 920 the UE 100 may respond with an acknowledgement of receipt of the configuration information for the UE 100. After step 918, the UE 100 is provided with configuration information for the UE 100, and the AUPF 300 is provided with the first and second parts of the configuration information for the AUPF 300. The UE 100 and AUPF 300 may at 922 communicate using the one-step mapping according to the configuration information. For example, the AUPF 300 may map SDFs to DRBs in one-step according to the configuration information for the AUPF; transmit data packets comprised in the SDFs via the mapped DRB(s) to the UE 100; and UE 100 may create a new derived QoS rule if reflective QoS applies based on the configuration information for the UE 100. Reference is made to FIG. 10, which shows an example procedure for deriving configuration information involving entities of a communication network having the first example architecture described above. In the procedure shown in FIG. 10, the SMF 109 defines the configuration information for the UE 100 and AUPF 300. At 1000, the SMF 109 initiates the QoS configuration and sends a request to the PCF for QoS related information. The SMF 109 may initiate the QoS configuration as part of a PDU Session Establishment procedure or a PDU Session Modification procedure. At 1002, the PCF may send a response to the request (received from SMF 109 at step 700) to the SMF 109. The response may comprise policy information including packet classification information and QoS requirements, e.g., QoS profile. At 1004, the SMF 109 sends a request to the CU-CP 204 for radio resource information, for example information identifying one or more candidate DRBs context information, UE context information. In some examples the request may be sent to the CU-CP 204 via the AMF 108. At 1006, in response to the request received at 704, the CU-CP 204 sends the requested radio resource information to the SMF 109. In some examples the response may be sent to the SMF 109 via the AMF 108. At 1008, the SMF 109 derives the configuration information for the UE 100 and a first part of the configuration information for the AUPF 300. The configuration information for the UE 100 may comprise the QoS rules as described previously. The first part of the configuration information for the AUPF 300 may comprise one or more PDRs, one or more FARs, one or more QERs as described previously, DRB Context Setup, and non-QoS related configuration information, e.g., Usage Reporting Rules (URRs), Multi-Access Rules (MARs), Session Reporting Rules (SRRs). The SMF 109 may derive the first part of the configuration information for the AUPF 300 based at least in part on the policy information received from the PCF and the radio resource information received from the CU-CP 204. At 1010 the SMF 109 sends, to the AUPF 300, the first part of the configuration information for the AUPF 300. Optionally at 1012, the AUPF 300 may respond with an acknowledgement of receipt of the first part of the configuration information for the AUPF 300. At 1014, the SMF 109 sends the configuration information for the UE 100 to the UE 100. Optionally at 716 the UE 100 may respond with an acknowledgement of receipt of the configuration information for the UE 100. At 1018, the CU-CP 204 derives a second part of the configuration information for the AUPF 300. The second part of the configuration information for the AUPF 300 may comprise UE context setup as described previously. At 1020, the CU-CP 204 sends the second part of the configuration information for the AUPF 300 to the AUPF 300. Optionally at 1022, the AUPF 300 may respond with an acknowledgement of receipt of the second part of the configuration information for the AUPF 300. After step 1022, the UE 100 is provided with configuration information for the UE 100, and the AUPF 300 is provided with the first and second parts of the configuration information for the AU PF 300. The UE 100 and AU PF 300 may at 1024 communicate using the one-step mapping according to the configuration information. For example, the AUPF 300 may map SDFs to DRBs in one-step according to the first and second parts of the configuration information for the AUPF; transmit data packets comprised in the SDFs via the mapped DRB(s) to the UE 100; and UE 100 may create a new derived QoS rule if reflective QoS applies based on the configuration information for the UE 100. FIG. 11 illustrates a communication network having a second example architecture. In the communication network having the second example architecture shown in FIG. 11, the CU-CP 204 configures the AUPF 300. The CU-CP 204 may provide the configuration information for the AUPF 300 to the AUPF 300 via the E1 interface. Reference is made to FIG. 12, which shows an example procedure for configuring the UE 100 and AUPF 300 with configuration information. The example of FIG. 12 involves entities of the communication network having the second example architecture. In the procedure shown in FIG. 12, the CU-CP 204 determines and provides the configuration information for the UE 100 and the AUPF 300. At 1200, the SMF 109 initiates the QoS configuration and sends a request to the PCF for QoS information relating to the PDU session of a UE 100. The SMF 109 may initiate the QoS configuration as part of a PDU Session Establishment procedure or a PDU Session Modification procedure. At 1202, the PCF may send a response to the request (received from SMF 109 at step 900) to the SMF 109. The response may comprise packet classification information and the requested QoS requirements, e.g., QoS profile, relating to the PDU session of the UE 100. At 1204, the SMF 109 sends core-related information to the CU-CP 204. The core-related information may comprise packet classification information and the one or more QoS requirements received from the PCF. In some examples the SMF 109 may send the corerelated information to the CU-CP 204 via the AMF 108. At 1206 the CU-CP 204 derives the configuration information for the AUPF 300 and the configuration information for the UE 100. The CU-CP 204 may derive the configuration information based on the core-related information received from the SMF 109 at step 1204 and radio-related information available at the CU-CP 204. For example, the CU-CP 204 may derive one or more PDRs, one or more FARs, and one or more QERs and DRB context setup information for the AUPF 300 based on packet classification information and QoS requirements (received from the SMF 109), and radio resource information (available at the CU-CP 204). UE context setup information may also be available at the CU-CP 204. The configuration information for the AUPF 300 and the configuration information for the UE 100 may be as described previously. At 1208 the CU-CP 204 sends the configuration information for the AUPF 300 to the AUPF 300. Optionally at 1210 the AUPF 300 may respond with an acknowledgement of receipt of the configuration information for the AUPF 300. At 1212 the CU-CP 204 sends the configuration information for the UE 100 to the UE 100. In some examples the CU-CP 204 may send the configuration information for the UE to the UE 100 via AS protocol signalling. Optionally at 914 the UE 100 may respond with an acknowledgement of receipt of the configuration information for the UE 100. After step 1212, the UE 100 is provided with configuration information for the UE 100, and the AUPF 300 is provided with the configuration information for the AUPF 300. The UE 100 and AUPF 300 may at 1216 communicate using the one-step mapping according to the configuration information. For example, the AUPF 300 may map SDFs to DRBs in one-step according to the first and second parts of the configuration information for the AUPF; transmit data packets comprised in the SDFs via the mapped DRB(s) to the UE 100; and UE 100 may create a new derived QoS rule if reflective QoS applies based on the configuration information for the UE 100. FIG. 13 illustrates a communication network having a third example architecture. In the communication network having the third example architecture shown in FIG. 13, the SMF 109 configures the AUPF 300. The SMF 109 may convey the configuration information via the N4 interface to the AUPF 300 and via NAS message to the UE 100. Reference is made to FIG. 14, which shows an example procedure for configuring the UE 100 and AUPF 300 with configuration information. The example of FIG. 11 involves entities of the communication network having the third example architecture. In the procedure shown in FIG. 14, the SMF 109 determines and provides the configuration information for the UE 100 and the AUPF 300. At 1400, the SMF 109 initiates the QoS configuration and sends a request to the PCF for QoS information relating to the PDU session of a UE 100. The SMF 109 may initiate the QoS configuration as part of a PDU Session Establishment procedure or a PDU Session Modification procedure. At 1402, the PCF may send a response to the request (received from SMF 109 at step 1100) to the SMF 109. The response may comprise policy information including packet classification information and QoS requirements, e.g., QoS profile. At 1404, the SMF 109 sends a request to the CU-CP 204 for radio resource information, for example information identifying one or more candidate DRBs context information, UE context information. In some examples the request may be sent to the CU-CP 204 via the AMF 108. At 1406, in response to the request received at 704, the CU-CP 204 sends the requested information the SMF 109. In some examples the response may be sent to the SMF 109 via the AMF 108. At 1408, the SMF 109 derives the configuration information for the UE 100 and the configuration information for the AU PF 300. The SMF 109 may derive the configuration information for the UE 100 and the configuration information for the AUPF 300 based on the information received from the PCF at 1402 and the information received from the CU-CP 204 at 1406. For example, the SMF 109 may derive one or more PDRs, one or more FARs, one or more QERs, and DRB context setup information for the AUPF 300 based on packet classification information and QoS requirements (received from the PCF) and radio resource information (received from the CU-CP 204). The SMF 109 may also receive UE context setup information as part of radio resource information received from the CU-CP 204. At 1410 the SMF 109 sends the configuration information for the AUPF 300 to the AUPF 300. Optionally at 1312 the AUPF 300 may respond with an acknowledgement of receipt of the configuration information for the AUPF 300. At 1414 the SMF 109 sends the configuration information for the UE 100 to the UE 100. Optionally at 1116 the UE 100 may respond with an acknowledgement of receipt of the configuration information for the UE 100. As shown in FIG. 14, in some examples the signalling at 1414 and 1416 may be via the AMF 108. After step 1416, the UE 100 is provided with configuration information for the UE 100, and the AUPF 300 is provided with the configuration information forthe AUPF 300. The UE 100 and AU PF 300 may at 1418 communicate using the one-step mapping according to the configuration information. For example, the AUPF 300 may map SDFs to DRBs in one-step according to the first and second parts of the configuration information for the AUPF; transmit data packets comprised in the SDFs via the mapped DRB(s) to the UE 100; and UE 100 may create a new derived QoS rule if reflective QoS applies based on the configuration information for the UE 100. FIG. 15 illustrates a communication network having a fourth example architecture. The communication network having the fourth example architecture shown in FIG. 12, includes a control plane network function (CP-NF 1200). The CP-NF 1200 may include some or all of the functionality of the CU-CP 204 and SMF 109. In some embodiments, the CP-NF 1200 may include the functionality of any other network functions that control the AUPF 300. The CP-NF 1200 may be configured to determine the configuration information for the AUPF 300 and the configuration information for the UE 100 and may send the configuration information forthe AUPF to the AUPF 300. In some embodiments, the CP-NF 1200 may send, to the UE 100, the configuration information for the UE 100 via NAS message or AS message when the CP-NF 1200 is deployed at a RAN node of the RAN 101. Advantageously, since the CP-NF 1200 is a network function that includes the functionality of the CU-CP 204 (which obtains radio resource information for the UE 100 and the RAN node of the RAN 101, such as data radio bearer information and UE related information) and SMF 109 (which obtains core-related information, such as packet classification information and QoS requirements), the CP-NF 1200 may be able to derive the configuration information forthe AUPF and / or the configuration information for the UE 100 with less signalling than the previous examples as signalling between the CU-CP and SMF may not be required (for example, the signalling of packet classification information and QoS requirements from SMF to CU-CP may not be required). Reference is made to FIG. 16, which shows an example procedure for configuring the UE 100 and AUPF 300 with configuration information. The example of FIG. 16 involves entities of the communication system having the fourth example architecture shown in FIG. 15 in which the CP-NF 1200 determines and provides the configuration information for the UE 100 and the configuration information for the AUPF 300. At 1600, the CP-NF 1200 initiates the QoS configuration and sends a request to the PCF for QoS information relating to the PDU session of a UE 100. The CP-NF 1200 may initiate the QoS configuration as part of a PDU Session Establishment procedure or a PDU Session Modification procedure. At 1602, the PCF may send a response to the request (received from the CP-NF 1200 at step 1600) to the CP-NF 1200. The response may comprise policy information including packet classification information and QoS requirements, e.g., QoS profile. At 1304, the CP-NF 1200 derives the configuration information for the UE 100 and the configuration information for the AU PF 300. The CP-NF 1200 may derive the configuration information for the UE 100 and the configuration information for the AUPF 300 based on the information received from the PCF at 1302 and based on radio resource information available at the CP-NF 1200. For example, the CP-NF 1200 may derive one or more PDRs, one or more FARs, one or more QERs , and DRB context information for the AUPF 300 based on packet classification information, QoS requirements (received from the PCF), and radio resource information (available at the CP-NF 1200). The UE context setup information is also available at the CP-NF 1200. The configuration information for the UE 100 and the configuration information for the AUPF 300 may be as described previously. At 1606 the CP-NF 1200 sends the configuration information for the AUPF 300 to the AUPF 300. Optionally at 1608 the AUPF 300 may respond with an acknowledgement of receipt of the configuration information for the AUPF 300. At 1610 the CP-NF 1200 sends the configuration information for the UE 100 to the UE 100. The CP-NF 1200 may send the configuration information for the UE 100 directly to the UE 100 by sending a AS message comprising the configuration information for the UE 100 when the CP-NF 1200 uses an AS protocol (e.g., RRC protocol) to communicate with the UE 100. Alternatively, the CP-NF 1200 may send the configuration information for the UE 100 via the AMF 108 by sending NAS message comprising the configuration information for the UE 100. Optionally at 1612 the UE 100 may respond with an acknowledgement of receipt of the configuration information for the UE 100. The acknowledgement may similarly be sent by the UE 100 directly to the CP-NF 1200 (iftheUE100 is using an AS protocol (e.g., RRC protocol) to communicate with the CP-NF 1200) or via the AMF 109 (if the UE 100 is using NAS signaling to communicate with the CP-NF 1200). After step 1612, the UE 100 is provided with configuration information for the UE 100, and the AUPF 300 is provided with the configuration information for the AUPF 300. At 1614, the UE 100 may communicate using the mapping information included in the configuration information for the UE and the AUPF 100 may communicate using the mapping information included configuration information for the AUPF 300. For example, the AUPF 300 may map SDFs to DRBs in one-step according to the first and second parts of the configuration information for the AUPF; transmit data packets comprised in the SDFs via the mapped DRB(s) to the UE 100; and UE 100 may create a new derived QoS rule if reflective QoS applies based on the configuration information for the UE 100. Various examples have been described where at least one control plane network function provides the UE 100 and AUPF 300 with a configuration information for performing one-step mapping of SDF to DRB. The at least one control plane network function may comprise one of: SMF 109 and CU-CP 204; SMF 109; CU-CP 204; or CP-NF 1200. The configuration information for the AUPF 300 and the configuration information for the UE 100 comprise a data radio bearer identifier of a data radio bearer to which data packets of a service data flow having certain quality of service characteristic are to be mapped. In some examples there is provided an apparatus comprising means for providing a central unit control plane function configured to perform: receiving, from a session management function, packet classification information and one or more quality of service requirements relating to a data session established for a user equipment; determining configuration information for an access user plane function and configuration information for the user equipment based at least in part on the packet classification information and the one or more quality of service requirements, wherein the configuration information for the access user plane function and the configuration information for the user equipment comprise a data radio bearer identifier of a data radio bearer to which data packets of a service data flow having certain quality of service characteristic are to be mapped; sending, to the user equipment, the configuration information for the user equipment; and sending, to the access user plane function, the configuration information for the access user plane function. In some examples there is provided an apparatus comprising means for providing a session management function configured to perform: receiving, from a policy control function, packet classification information and one or more quality of service requirements relating to a data session for a user equipment; receiving, from a central unit control plane function, data radio bearer context information and user equipment context information; deriving configuration information for an access user plane function based on the packet classification information, the one or more quality of service requirements, and the data radio bearer context information, wherein the configuration information for the access user plane function comprises a data radio bearer identifier of a data radio bearer to which data packets of a service data flow having certain quality of service characteristic are to be mapped; deriving configuration information for the user equipment based on the packet classification information, the one or more quality of service requirements, and the data radio bearer context information, wherein the configuration information for the user equipment comprises a data radio bearer identifier of a data radio bearer to which data packets of a service data flow having certain quality of service characteristic are to be mapped; sending, to the user equipment, the derived configuration information for the user equipment; and sending, to the access user plane function, the derived configuration information for the access user plane function and the user equipment context information. In some examples there is provided a user equipment comprising means for: receiving, from a session management function or central unit control plane function, configuration information for the user equipment, wherein the configuration information for the user equipment comprises a data radio bearer identifier of a data radio bearer to which data packets of a service data flow having certain quality of service characteristic are to be mapped; and based on the received configuration information for the user equipment, mapping one or more data packets comprised in one or more service data flows to a data radio bearer for a data session for the user equipment. In some examples there is provided an apparatus comprising means for providing an access user plane function configured to perform: receiving, from a session management function or central unit control plane function, configuration information for the access user plane function, wherein the configuration information for the access user plane function comprises a data radio bearer identifier of a data radio bearer to which data packets of a service data flow having certain quality of service characteristic are to be mapped; based on the received configuration information for the access user plane function, mapping one or more data packets comprised in one or more service data flows to a data radio bearer; and sending the one or more packets mapped to the data radio bearer to a user equipment. In some examples there is provided an 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: receive, from a session management function, packet classification information and one or more quality of service requirements relating to a data session established for a user equipment; determine configuration information for an access user plane function and configuration information for the user equipment based at least in part on the packet classification information and the one or more quality of service requirements, wherein the configuration information for the access user plane function and the configuration information for the user equipment comprise a data radio bearer identifier of a data radio bearer to which data packets of a service data flow having certain quality of service characteristic are to be mapped; send, to the user equipment, the configuration information for the user equipment; and send, to the access user plane function, the configuration information for the access user plane function. In some examples there is provided an 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: receive, from a policy control function, packet classification information and one or more quality of service requirements relating to a data session for a user equipment; receive, from a central unit control plane function, data radio bearer context information and user equipment context information; derive configuration information for an access user plane function based on the packet classification information, the one or more quality of service requirements, and the data radio bearer context information, wherein the configuration information for the access user plane function comprises a data radio bearer identifier of a data radio bearer to which data packets of a service data flow having certain quality of service characteristic are to be mapped; derive configuration information for the user equipment based on the packet classification information, the one or more quality of service requirements, and the data radio bearer context information, wherein the configuration information for the user equipment comprises a data radio bearer identifier of a data radio bearer to which data packets of a service data flow having certain quality of service characteristic are to be mapped; send, to the user equipment, the derived configuration information for the user equipment; and send, to the access user plane function, the derived configuration information for the access user plane function and the user equipment context information. In some examples there is provided an 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: receive, from a session management function or central unit control plane function, configuration information for a user equipment, wherein the configuration information for the user equipment comprises a data radio bearer identifier of a data radio bearer to which data packets of a service data flow having certain quality of service characteristic are to be mapped; and based on the received configuration information for the user equipment, map one or more data packets comprised in one or more service data flows to a data radio bearer for a data session for the user equipment. In some examples there is provided an 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: receive, from a session management function or central unit control plane function, configuration information for an access user plane function, wherein the configuration information for the access user plane function comprises a data radio bearer identifier of a data radio bearer to which data packets of a service data flow having certain quality of service characteristic are to be mapped; based on the received configuration information for the access user plane function, map one or more data packets comprised in one or more service data flows to a data radio bearer; and send the one or more packets mapped to the data radio bearer to a user equipment. FIG. 17 illustrates an example of a communication device 1400, such as the UE 100 illustrated in FIG. 1. The communication device 1400 may be any device capable of sending and receiving radio signals. Non-limiting examples of a communication device 1400 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 machine-type communications (MTC) device, an Internet of things (loT) type communication device or any combinations of these or the like. The communication device 1400 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. The communication device 1400 may receive wireless signals (e.g., radio signals) over an air or radio interface 1407 via appropriate apparatus for receiving and may transmit wireless signals via appropriate apparatus for transmitting radio signals. In FIG. 17 a transceiver is designated schematically by block 1406. The transceiver 1406 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. The communication device 1400 comprises at least one processor 1401, at least one memory ROM 1402a, at least one RAM 1402b and other possible components 1403 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 1401 is coupled to the RAM 1402b and the ROM 1402a. The at least one processor 1401 executes instructions of an appropriate software code 1408. Execution of the instructions of the software code 1408 causes the communication device 1400 (e.g., UE 100) to carry out or perform one or more operations of the communication device 1400, including the operations of the method 600 shown in FIG. 6. The software code 1408 may be stored in the ROM 1402a. The at least one processor 1401, the at least one ROM 1402a, and the at least one RAM 1402b, 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 reference 1404. The communication device 1400 may optionally have a user interface such as keypad 1405, 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. FIG. 18 illustrates an example of an apparatus 1800 for a communication network. The apparatus 1800 comprises or implements one or network functions illustrated in FIG. 1, including CU-CP204, SMF 109, and / or AUPF 300. Non-limiting examples of apparatus 1800 comprise a computing device, a distributed computing system, a cloud computing system. The apparatus 1800 may deployed in a RAN in instances the communication network has the first, second, third or fourth architecture described above. The apparatus 1800 may be deployed in a core network of a communication device in instances the communication network has the first architecture, or the fourth architecture described above, The communication device 1800 comprises at least one processor 1801, at least one memory ROM 1802a, at least one RAM 1802b. The at least one processor 1801 is coupled to the RAM 1802b and the ROM 1402a. The at least one processor 1801 executes instructions of software code 1808 of CU-CP 204, SMF 109, and / or AUPF 300. Execution of the instructions of the software code 1808 of the CU-CP causes the apparatus 1800 to carry out or perform the operations of the method 400 shown in FIG. 4. Execution of the instructions of the software code 1808 of SMF 109 cause the apparatus 1800 to carry out or perform the method 500 shown in FIG. 5. Execution of the instructions of the software code 1808 of the AUPF 300 causes the apparatus 1800 to carry out or perform the method 700 shown in FIG. 7. The software code 1808 may be stored in the ROM 1402a. FIG. 19 shows a schematic representation of non-volatile memory media 1500a (e.g., computer disc (CD) or digital versatile disc (DVD)) and 1500b (e.g. universal serial bus (USB) memory stick) storing instructions and / or parameters 1502 which when executed by a processor allow the processor to perform one or more of the steps of any of the methods described previously. It is understood that references in the above to various network functions (e.g., to an AMF, an SMF, 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. 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 / or reception. Although the apparatuses have been described as one entity, different modules and memory may be implemented in one or more physical or logical entities. 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. 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. 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. 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. 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.” 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. 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 computerexecutable 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. 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. 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). 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. 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. 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. 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 5 a combination of one or more example embodiments with any of the other example embodiments previously discussed.

Claims

1. A method for a central unit control plane function, the method comprising:receiving, from a session management function, packet classification information and one or more quality of service requirements relating to a data session established for a user equipment;determining configuration information for an access user plane function and configuration information for the user equipment based at least in part on the packet classification information and the one or more quality of service requirements, wherein the configuration information for the access user plane function and the configuration information for the user equipment comprise a data radio bearer identifier of a data radio bearer to which data packets of a service data flow having certain quality of service characteristic are to be mapped;sending, to the user equipment, the configuration information for the user equipment; andsending, to the access user plane function, the configuration information for the access user plane function.

2. The method of claim 1, wherein the configuration information for the user equipment comprises the one or more quality of service rules.

3. The method of claim 2, wherein each quality of service rule comprises:the data radio bearer identifier of the data radio bearer to which the data packets of the service data flow having certain quality of service characteristic are to be mapped;a packet filter set identifying one or more service data flows; anda precedence value determining the order in which a quality of service rule shall be applied.

4. The method of any of claims 1 to 3, wherein the configuration information for the access user plane function comprises:one or more packet detection rules;one or more forwarding action rules;one or more quality of service enforcement rules;user equipment context setup information; anddata radio bearer context setup information.

5. The method of claim 4, wherein each packet detection rule comprises:packet detection information indicating an identifier of a data radio bearer to be used to detect a data packet associated with a certain quality of service characteristic; andinformation indicating one or more rules for decapsulation of a header of the data packet.

6. The method of claims 4 or 5, wherein each forwarding action rule comprisesinformation indicating how to perform packet encapsulation.

7. The method of any of claims 4 to 6, wherein each quality of service enforcement rule comprises:the data radio bearer identifier of the data radio bearer to which the data packets of the service data flow having certain quality of service characteristic are to be mapped; andinformation indicating whether reflective quality of service mapping service data flow to data radio bearer is enabled at the user equipment.

8. The method of any of claims 4 to 7, wherein the data radio bearer context setup information comprises context setup information for a data radio bearer identified by a data radio bearer identifier.

9. A method for a session management function, the method comprising:receiving, from a policy control function, packet classification information and one or more quality of service requirements relating to a data session for a user equipment;receiving, from a central unit control plane function, data radio bearer context information and user equipment context information;deriving configuration information for an access user plane function based on the packet classification information, the one or more quality of service requirements, and the data radio bearer context information, wherein the configuration information for the access user plane function comprises a data radio bearer identifier of a data radio bearer to which data packets of a service data flow having certain quality of service characteristic are to be mapped;deriving configuration information for the user equipment based on the packet classification information, the one or more quality of service requirements, and the data radio bearer context information, wherein the configuration information for the user equipment comprises a data radio bearer identifier of a data radio bearer to which data packets of a service data flow having certain quality of service characteristic are to be mapped;sending, to the user equipment, the derived configuration information for the user equipment; andsending, to the access user plane function, the derived configuration information for the access user plane function and the user equipment context information.

10. The method of claim 9, wherein the configuration information for the user equipment comprises the one or more quality of service rules.

11. The method of claim 10, wherein each quality of service rule comprises:the data radio bearer identifier of the data radio bearer to which the data packets of the service data flow having certain quality of service characteristic are to be mapped;a packet filter set identifying one or more service data flows; anda precedence value determining the order in which a quality of service rule shall be applied.

12. The method of any of claims 9 to 11, wherein the configuration information for the access user plane function comprises:one or more packet detection rules;one or more forwarding action rules;one or more quality of service enforcement rules;user equipment context setup information; anddata radio bearer context setup information.

13. The method of claim 12, wherein each packet detection rule comprises:packet detection information indicating an identifier of a data radio bearer to be used to detect a data packet associated with a certain quality of service characteristic; andinformation indicating one or more rules for decapsulation of a header of the data packet.

14. The method of claims 12 or 13, wherein each forwarding action rule comprises: information indicating how to perform packet encapsulation.

15. The method of any of claims 12 to 14, wherein each quality of service enforcement rule comprises:the data radio bearer identifier of the data radio bearer to which the data packets of the service data flow having certain quality of service characteristic are to be mapped; andinformation indicating whether reflective quality of service mapping service data flow to data radio bearer is enabled at the user equipment.

16. The method of any of claims 12 to 15, wherein the data radio bearer context setup information comprises context setup information for a data radio bearer identified by a data radio bearer identifier.

17. A method for a user equipment, the method comprising:receiving, from a session management function or central unit control plane function, configuration information for the user equipment, wherein the configuration information for the user equipment comprises a data radio bearer identifier of a data radio bearer to which data packets of a service data flow having certain quality of service characteristic are to be mapped; andbased on the received configuration information for the user equipment, mapping one or more data packets comprised in one or more service data flows to a data radio bearer for a data session for the user equipment.

18. The method of claim 17, wherein the configuration information for the user equipment comprises one or more quality of service rule, wherein each quality of service rule comprises:the data radio bearer identifier of the data radio bearer to which the data packets of the service data flow having certain quality of service characteristic are to be mapped; anda packet filter set identifying one or more service data flows; anda precedence value determining the order in which a quality of service rule shall be applied.

19. A method for an access user plane function, the method comprising:receiving, from a session management function or central unit control plane function, configuration information for the access user plane function, wherein the configuration information for the access user plane function comprises a data radio bearer identifier of a data radio bearer to which data packets of a service data flow having certain quality of service characteristic are to be mapped;based on the received configuration information for the access user plane function, mapping one or more data packets comprised in one or more service data flows to a data radio bearer; andsending the one or more packets mapped to the data radio bearer to a user equipment.

20. The method of claim 19, wherein the configuration information for the access user plane function comprises:one or more packet detection rules;one or more forwarding action rules;one or more quality of service enforcement rules;user equipment context setup information; and data radio bearer context setup information.

21. The method of claim 20, wherein each packet detection rule comprises:packet detection information comprising an identifier of the data radio bearer to be used to detect a data packet associated with a certain quality of service characteristic; andinformation indicating one or more rules for decapsulation of a header of the data packet.

22. The method of claim 20 or 21, wherein each forwarding action rule comprises information indicating how to perform packet encapsulation.

23. The method of any of claims 20 to 22, wherein each quality of service enforcement rule comprises:the data radio bearer identifier of the data radio bearer to which the data packets of the service data flow having certain quality of service characteristic are to be mapped; and information indicating whether reflective quality of service mapping service data flow to data radio bearer is enabled at the user equipment.

24. The method of any of claims 20 to 23, wherein the data radio bearer context setup information comprises context setup information for a data radio bearer identified by a data radio bearer identifier.

25. An apparatus comprising means for providing a central unit control plane function configured to perform the method of any of claims 1 to 8.

26. An apparatus comprising means for providing a session management function configured to perform the method of any of claims 9 to 16.

27. A user equipment comprising means for performing the method of any of claims 17 or 18.

28. An apparatus comprising means for providing an access user plane function configured to perform the method of any of claims 19 to 24.

29. An 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 perform the method of any of claims 1 to 24.

Images