Devices and methods for service data flow distribution for multi-connectivity

Abstract

A control plane entity (150) for controlling traffic to and / or from a user equipment, UE, application on a UE (110) via one or more base stations providing one or more access networks (120) and for each access network a plurality of data channels (DC1-DCn) in a mobile network (100) is disclosed. The control plane entity (150) is configured to obtain preference information representative of one or more preferred access networks and / or one or more preferred data channels for the traffic to and / or from the UE application. Moreover, the control plane entity (150) is configured to generate mapping data based on the preference information, wherein the mapping data defines a mapping between traffic to and / or from the UE application to one or more of the plurality of data channels (DC1-DCn) of the one or more access networks (120).

Description

[0001] DEVICES AND METHODS FOR SERVICE DATA FLOW DISTRIBUTION FOR MULTI-CONNECTIVITY

[0002] TECHNICAL FIELD

[0003] The present disclosure relates to wireless communications. More specifically, the present disclosure relates to devices and methods for distributing a plurality of Service Data Flows (also referred to as QoS flows) in a multi-connectivity scenario.

[0004] BACKGROUND

[0005] The heterogeneity in radio access technologies (LTE, 5G New Radio (NR), 6G THz, NTN, Wi-Fi) and their communication infrastructure equipment’s like the BS nodes, pose many challenges to enable seamless communication in a multiconnectivity scenario in mobile communication networks.

[0006] In the current 3GPP standards, there is no way to unify the various different access networks i.e., the data channels in and across access networks. During a PDU session establishment process, a QoS flow (herein also referred to as a Service Data Flow, SDF) is mapped to a single data channel provided by a dedicated access network node post configuration. The mapping of a QoS flow to a data channel remains fixed throughout the lifetime of a PDU session. Thus, packets from a QoS flow cannot be distributed on 2 or more data channels, even if the data channels were available (and capable of fulfilling the QoS) regardless, if the data channels belong to the same access network node or belong to other access nodes in the same access network or to access nodes in different access networks, possibly with even different technologies. The major drawbacks of such fixed assignment include in-efficient resource utilization, limited throughput, and latency.

[0007] PCT / EP2023 / 070879 discloses an approach for leveraging multi-connectivity in a mobile network and distributing the packets from a QoS flow on all available connections, thereby improving the throughput and latency experienced by UEs and improve the resource utilization in the network. However, traffic steering is applied in the Radio Access Network without considering the application’s requirements. In other words, applications cannot participate in the end-to-end allocation and use of the resources for optimally transporting the traffic of UEs. Moreover, applications lack knowledge of the UE’s radio capabilities and the network connections that are available to a UE.

[0008] SUMMARY

[0009] It is an objective of the present disclosure to provide improved devices and methods for distributing a plurality of Service Data Flows (also referred to as QoS flows) in a multi-connectivity scenario, in particular for enabling application / service participation in end-to-end traffic steering decisions for improving the Quality of Experience (QoE) of users by considering, for instance, the application’s preferences or requirements and the resource efficiency of networks.

[0010] The foregoing and other objectives are achieved by the subject matter of the independent claims. Further implementation forms are apparent from the dependent claims, the description and the figures.

[0011] According to a first aspect a control plane entity (herein also referred to as application agent, AA, entity or application agent) is provided for controlling traffic to and / or from a user equipment, UE, application running on a UE (herein also referred to as mobile terminal) via one or more base stations providing one or more access networks and for each access network a plurality of available data channels (herein also referred to as Service Data Flows, SDFs) in a mobile network, in particular a 3GPP 5G or 6G network. The control plane entity according to the first aspect is configured to obtain preference information representative of one or more preferred access networks of the one or more access networks and / or one or more preferred data channels of the plurality of data channels for the traffic to and / or from the UE application. Moreover, the control plane entity is configured to generate mapping data, in particular a plurality of traffic distribution markers, based on the preference information, wherein the mapping data, e.g. the plurality of traffic distribution markers defines a mapping between traffic to and / or from the UE application to one or more of the plurality of data channels of the one or more access networks. The control plane entity according to the first aspect allows traffic steering by means of the mapping data in a multi-connectivity scenario based on the preference information associated with an UE application running on the UE.

[0012] In a further possible implementation form, the control plane entity according to the first aspect is configured to provide the mapping data, e.g. the plurality of traffic distribution markers to a network function of a core network of the mobile network for including the mapping data in a data structure, wherein the network function is configured to provide the data structure to the UE, the one or more base stations and / or a user plane entity of the mobile network. This allows to efficiently generate and distribute the data structure including the mapping data within the mobile network.

[0013] In a further possible implementation form, the data structure is a table. This allows storing and accessing the mapping data in the data structure in an efficient manner.

[0014] In a further possible implementation form, the mapping data comprises a plurality of priority values, wherein each priority value assigns a priority to each of the plurality of data channels of the one or more access networks for mapping traffic to and / or from the UE application to one or more of the plurality of data channels of the one or more access networks. This allows to efficiently map traffic to and / or from the UE application to one or more of the plurality of data channels of the one or more access networks.

[0015] In a further possible implementation form, the control plane entity according to the first aspect is configured to receive a UE protocol data unit, PDU, session establishment trigger indicative of a UE PDU session and to generate the mapping data for the indicated UE PDU session. This allows for a seamless integration in an established communication structure of mobile networks.

[0016] In a further possible implementation form, the control plane entity according to the first aspect is configured to receive the UE PDU session establishment trigger from an Access and Mobility Management Function, AMF, of the mobile network. This allows for a seamless integration in an established communication structure of mobile networks.

[0017] In a further possible implementation form, the control plane entity according to the first aspect is configured to obtain the preference information from an application via an Application Function, AF, of the mobile network associated with the UE application. This allows for a seamless integration in an established communication structure of mobile networks.

[0018] In a further possible implementation form, the control plane entity according to the first aspect is configured to obtain the preference information from the AF associated with the UE application, in response to forwarding availability information to the AF associated with the UE application, wherein the availability information is representative of the one or more access networks and for each access network the plurality of available data channels. This allows for a seamless integration in an established communication structure of mobile networks. In a further possible implementation form, the control plane entity is configured to generate the mapping data based further on the availability information. This allows taking into account further information for generating the mapping data and thereby provides an even better mapping of the traffic.

[0019] In a further possible implementation form, the control plane entity according to the first aspect is further configured to obtain network traffic policy information representative of one or more network traffic policies implemented by the mobile network, wherein the control plane entity is configured to generate the mapping data based further on the network traffic policy information. This allows taking into account further information for generating the mapping data and thereby provides an even better mapping of the traffic.

[0020] According to a second aspect a network function entity of a mobile network comprising a control plane entity according to the first aspect is provided. The network function entity according to the second aspect is configured to obtain the mapping data from the control plane entity and to include the mapping data in a data structure. Moreover, the network function entity according to the second aspect is configured to provide the data structure to the UE, the one or more base stations and / or a user plane entity of the mobile network. This allows to efficiently implement the control plane entity according to the first aspect as a component of a network function of the mobile network.

[0021] In a further possible implementation form, the network function entity according to the second aspect is an Access and Mobility Management Function, AMF, entity or a Policy Control Function, PCF, entity of the mobile network. This allows for a seamless integration in an established communication structure of mobile networks.

[0022] According to a third aspect a method is provided for operating a control plane entity, i.e. the application agent entity for controlling traffic to and / or from a user equipment, UE, application running on a UE via one or more base stations providing one or more access networks and for each access network a plurality of available data channels, i.e. Service Data Flows, SDFs, in a mobile network. The method according to the third aspect comprises the steps of: obtaining preference information representative of one or more preferred access networks of the one or more access networks and / or one or more preferred data channels of the plurality of data channels for the traffic to and / or from the UE application; and generating mapping data, in particular a plurality of traffic distribution markers, based on the preference information, wherein the mapping data, e.g. the plurality of traffic distribution markers defines a mapping between traffic to and / or from the UE application to one or more of the plurality of data channels of the one or more access networks.

[0023] The method according to the third aspect can be performed by the control plane entity according to the first aspect. Thus, further features of the method according to the third aspect result directly from the functionality of the control plane entity according to the first aspect as well as its different implementation forms described above and below.

[0024] According to a fourth aspect, a computer program product is provided, comprising a computer-readable storage medium for storing a program code which causes a computer or a processor to perform the method according to the third aspect, when the program code is executed by the computer or the processor.

[0025] Details of one or more embodiments are set forth in the accompanying drawings and the description below. Other features, objects, and advantages will be apparent from the description, drawings, and claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] In the following, embodiments of the present disclosure are described in more detail with reference to the attached figures and drawings, in which:

[0027] Fig. 1 is a schematic diagram illustrating a mobile telecommunication system comprising a UE and a control plane entity according to an embodiment for generating a mapping data structure for establishing multi-connectivity communication for the UE with a data network;

[0028] Fig. 2a is a schematic diagram illustrating operations and interactions of the control plane entity according to an embodiment with other network entities of a mobile network for a scenario, where a PDU Session Establishment Request is initiated by a UE;

[0029] Fig. 2b is a schematic diagram illustrating operations and interactions of the control plane entity according to an embodiment with other network entities of a mobile network for a scenario, where the UE network connections have changed;

[0030] Fig. 2c is a schematic diagram illustrating operations and interactions of the control plane entity according to an embodiment with other network entities of a mobile network for a scenario, where the operation conditions of an application server have changed;

[0031] Fig. 3 is a signalling diagram illustrating operations and interactions of the control plane entity according to an embodiment with other network entities of a mobile network for a scenario, where the control plane entity is implemented as a component of an AMF;

[0032] Fig. 4 is a signalling diagram illustrating operations and interactions of the control plane entity according to an embodiment with other network entities of a mobile network for a scenario, where the control plane entity is implemented as a component ofa PCF;

[0033] Fig. 5a is a schematic diagram illustrating the architecture of a mobile telecommunication system comprising a control plane entity according to an embodiment, wherein the control plane entity is implemented as a component of an AMF;

[0034] Fig. 5b is a schematic diagram illustrating the architecture of a mobile telecommunication system comprising a control plane entity according to an embodiment, wherein the control plane entity is implemented as a component of a PCF; and

[0035] Fig. 6 is a flow diagram illustrating a method for operating a control plane entity according to an embodiment for generating a mapping data structure for establishing multi-connectivity communication.

[0036] In the following, identical reference signs refer to identical or at least functionally equivalent features.

[0037] DETAILED DESCRIPTION OF THE EMBODIMENTS

[0038] In the following description, reference is made to the accompanying figures, which form part of the disclosure, and which show, by way of illustration, specific aspects of embodiments of the present disclosure or specific aspects in which embodiments of the present disclosure may be used. It is understood that embodiments of the present disclosure may be used in other aspects and comprise structural or logical changes not depicted in the figures. The following detailed description, therefore, is not to be taken in a limiting sense, and the scope of the present disclosure is defined by the appended claims.

[0039] For instance, it is to be understood that a disclosure in connection with a described method may also hold true for a corresponding device or system configured to perform the method and vice versa. For example, if one or a plurality of specific method steps are described, a corresponding device may include one or a plurality of units, e.g. functional units, to perform the described one or plurality of method steps (e.g. one unit performing the one or plurality of steps, or a plurality of units each performing one or more of the plurality of steps), even if such one or more units are not explicitly described or illustrated in the figures. Moreover, if a specific apparatus is described based on one or a plurality of units, e.g. functional units, a corresponding method may include one step to perform the functionality of the one or plurality of units (e.g. one step performing the functionality of the one or plurality of units, or a plurality of steps each performing the functionality of one or more of the plurality of units), even if such one or plurality of steps are not explicitly described or illustrated in the figures. Further, it is understood that the features of the various exemplary embodiments and / or aspects described herein may be combined with each other, unless specifically noted otherwise.

[0040] Before describing detailed embodiments for establishing multi-connectivity communication in a mobile network the following acronyms / abbreviations are defined:

[0041] 3rd Generation Partnership Project 3GPP

[0042] Access and Mobility Management Function AMF

[0043] Access Network AN

[0044] Access Traffic Steering, Switching & Splitting ATSSS

[0045] Artificial Reality AR

[0046] Base Station BS

[0047] Buffering Action Rules BAR

[0048] Control Plane CP

[0049] Core Network CN

[0050] Data Network DN

[0051] Down Link DL

[0052] Dual Connectivity DC

[0053] Edge Application Server EAS enhanced Mobile BroadBand eMBB

[0054] Forwarding Action Rules FAR

[0055] Geostationary Earth Orbit GEO

[0056] Guaranteed Bit Rate GBR

[0057] Eligh Altitude Platform Stations FLAPS

[0058] Internet Protocol version 4 IPv4

[0059] Internet Protocol version 6 IPv6

[0060] Long-Term Evolution LTE

[0061] Low Earth Orbit LEO massive Machine Type Communications mMTC

[0062] Master Cell Group MCG

[0063] Master Node MN

[0064] Media Access Control MAC

[0065] Mobile Network Operator MNO Multi Access MA

[0066] Multi Connectivity MC

[0067] Multipath Transmission Control Protocol MPTCP

[0068] Multi-Radio Dual Connectivity MR-DC

[0069] Network Data Analytics Function NWDAF

[0070] Network Exposure Function NEF

[0071] Network Function NF

[0072] New Radio NR

[0073] Next Generation Application Protocol NG-AP

[0074] Non-Access Stratum NAS

[0075] Non-Terrestrial Network NTN

[0076] Operating System OS

[0077] Packet Detection Rules PDR

[0078] Packet F orwarding Control Protocol PF CP

[0079] PDU Session Anchor PSA

[0080] Physical Layer PHY

[0081] Policy and Charging Control PCC

[0082] Policy Control Function PCF

[0083] Protocol Data Convergence Protocol PDCP

[0084] Protocol Data Unit PDU

[0085] Quality of Service QoS

[0086] Quality of Service Enforcement Rules QER

[0087] Quality of Service Flow Identifier QFI / QI

[0088] Radio Access Network RAN

[0089] Radio Link Control RLC

[0090] Radio Resource Control RRC

[0091] Reinforcement Learning RL

[0092] Secondary Cell Group SCG

[0093] Secondary Node SN

[0094] Service Based Architecture SBA

[0095] Service Based Interface SBI

[0096] Service Data Adaptation Protocol SDAP

[0097] Service Data Flow SDF

[0098] Service data flow Distribution Manager SDM

[0099] Service data flow Distribution Table SDT

[0100] Session Management Function SME

[0101] Single Network Slice Selection Assistance Information S-NSSAI

[0102] State of The Art SoTA

[0103] Terrestrial Network TN

[0104] Timing Advance TA

[0105] Traffic Flow Template TFT ultra-Reliable Low Latency Communications uRLLC

[0106] Unified Data Management UDM

[0107] Up Link UL

[0108] Uplink Classifier UL CL Usage Reporting Rules URR

[0109] User Equipment UE

[0110] User Plane UP

[0111] User Plane F unction UPF

[0112] Virtual Reality VR

[0113] Wireless Fidelity Wi-Fi

[0114] Figure 1 shows a schematic diagram illustrating a mobile telecommunication system 100 comprising at least one user equipment, UE, 110 according to an embodiment, at least one base station 120 according to an embodiment, and a network entity 130, for instance, in the form of a UPF 130, according to an embodiment. In an embodiment, the mobile telecommunication system 100 is a 3rd Generation Partnership Project (3GPP) mobile telecommunication system 100. As will be described in more detail below, the UE 110, the base station 120, and the network entity 130 are configured to make use of a mapping data structure 152, in particular a mapping table 152 (herein also referred to as Service data flow Distribution Table, SDT, 152) for establishing multi-connectivity communication between the UE 110 and an end-point Application 191 via the data network 190, such as the Internet 190.

[0115] As will be described in more detail below, the mapping data for the mapping table 152 is generated by a control plane entity 150 (herein also referred to as Application Agent, AA, 150), which, as illustrated in figure 1, may be implemented as a component of a control plane function 140. Generally, the control plane entity 150, i.e. AA 150 allows extending application and service providers requirements to the access networks of the mobile network 100 and thereby enable an application / service provider to extend their requirements end-to-end (as applications requirements are already considered in the mobile core network). More specifically, the control plane entity 150, i.e. AA 150 is configured to obtain preference information representative of one or more preferred access networks of the one or more access networks 120 of the mobile network 100 and / or one or more preferred data channels of a plurality of data channels DCi-DCnfor the traffic to and / or from a UE application running on the UE 110 (referred to as mobile terminal, MT, 110 in figure 1). Moreover, as will be described in more detail below, the control plane entity 150, i.e. AA 150 is configured to generate mapping data, in particular a plurality of traffic distribution markers, based on the preference information, wherein the mapping data, e.g. the plurality of traffic distribution markers defines a mapping between traffic to and / or from the UE application to one or more of the plurality of data channels DCi-DCnof the one or more access networks 120.

[0116] As alreadv mentioned above and illustrated in figure 1, according to embodiments disclosed herein the control plane entity 150, i.e. the AA functionality 150 may be implemented as a component of a suitable CP function 140 in the core network of the mobile network 100. In the embodiment illustrated in figure 1, the AA 150 receives a PDU session establishment / modification trigger from the MT 110, i.e. UE 110 (via an access management function, AMF, 160 in the core network) and requests the available connections for the MT 110 (from the AMF 160) and forwards this information to the AF 170. The application 191, which may run on an application server connected to a data network 190, can pre-configure its preferences, i.e. the preference information for the access network connections in the AF 170 or the AF 170 may request the application 191 to provide its preferences, i.e. the preference information when it receives the trigger from the AA 150. Additionally, the application 191 can also dynamically adjust its preferences during an ongoing PDU session based on the condition / status of its end-points, i.e. the UE 110 and / or the application server. Moreover, whenever there is any change in the MT’s connectivity, e.g., when the MT 110 connects to a new access network node, the AA 150 may send the trigger to the AF 170 with the current available connections for the MT 110 for the ongoing PDU session.

[0117] As illustrated in figure 1, the AF 170 may reply to the AA 150 with its preferences, i.e. the preference information for the network connections for the UE 110, i.e. MT 110 during the PDU session. The preferences, i.e. the preference information of the application 191 for the preferred access networks may be based on many different criteria, e.g., to improve the QoE of users, load balancing, energy related considerations, such as preference for an access network that uses green energy sources, and the like. As further illustrated in figure 1, the AA 150 transforms this preference, i.e. the preference information from the application 190 into the plurality of traffic distribution markers, i.e. the mapping data, which in an embodiment may comprise a plurality of priorities for a data structure 152, preferably in the form of a table 152 (referred to as Service data flow Distribution Table, SDT, 152 herein). The CP entity 140 uses these Traffic Distribution Markers for generating one or more SDTs 152 for the UE 110, the RAN(s) 120 and the UP 130 and sends the SDT(s) 152 to the MT 110, the RAN(s) node(s) 120 and the UP node(s) 130. Once the PDU session is established and the MT 110 has received the SDT 152, it uses the Traffic Distribution Markers in the SDT 152 to distribute the UL traffic on the available connections, for instance, in the way described in PCT / EP2023 / 070879 . Similarly, the RAN(s) and UP nodes 120, 130 may distribute the Down Link (DL) packets to the MT 110 on the available connections and data channels based on the Traffic Distribution Markers in the SDT, for instance, in the way described in PCT / EP2023 / 070879.

[0118] As already mentioned above, the MT 110, the RAN(s) and UP nodes 120, 130 may be configured in the way described in PCT / EP2023 / 070879, which is fully incorporated herein by reference, for distributing traffic based on the SDT 152. More specifically, the SDT 152 may be used in the UE 110 and UP 130 (in Layer 2 or above) of the protocol stack to capture SDF / QoS / Traffic profile (e.g., mmtc, uRLLC, etc.) mapping to available networks and their corresponding data channels, e.g., provided by the operator. A Service data flow Distribution Manager (SDM) may be implemented in the UE 110 as a SDM-UE and UP 130 as a SDM-UP (in Layer 2 or above) to map the data packets from each SDF / QoS Flow to available network(s) and their corresponding data channels by querying the SDT 152.

[0119] The SDM-UE may be located in a layer-2 sublayer between the IP and above the SDAP sublayer in the 3GPP 5G (and beyond 5G) protocol stack. The SDM-UE may query the SDT 152 with a QoS Identifier (QI) and receives a list of Access Networks (ANs) and their corresponding data channels as the response. The SDM may select an AN and a corresponding data channel and may forward the packet to the corresponding SDAP entity in the next sublayer. There may be multiple SDAP entities in the SDAP layer, one each for every connected network (currently a 3GPP standard for 5G as of release 18). The SDAP may forward the packet to the selected AN over the selected data channel.

[0120] The SDM-UP may be located in a layer-2 sublayer between the IP and above the MAC / Ethemet sublayer in Core UP and above the SDAP sublayer in the 3GPP 5G (and beyond 5G) protocol stack. The UPF 130 and the RAN Base Stations (BSs) 120 receive the SDT 152 from the core network e.g., UPF may receive the SDT 152 from a SMF via N4 signaling during PDU session establishment. The UPF 130 may maintain multiple N3 tunnels with each AN node 120 that is available for the PDU session (informed by SMF or derived from the SDT 152). The UPF 130 may receive QoS markings (QI) from SMF and SDM-UP in UPF 130 may use the QI to query the SDT 152 and select an AN 120 to send the packet. The RAN 120 receives the packet and using the QI marking in the packet SDM-UP in RAN queries the SDT 152 and receives the data channel on which to forward the packet to UE 110. The RAN 120 forwards the packet to the UE 110 over the selected data channel.

[0121] In the embodiment shown in figure 2a, the control plane entity 150, i.e. the AA functionality 150 is implemented as a component of a suitable CP function 140 in the mobile core network for a scenario where the UE 110, i.e. MT 110 initiates a PDU session establishment request. When the user of the UE 110 wants to use an application over the mobile network 100, the UE 110, i.e. MT 110 requests the mobile network control plane to establish a PDU session for the UE 110 (step 1 of figure 2a). The PDU session establishment trigger is sent via a CP Access Manager Function 160, e.g. an AMF 160, to a Session Management Function 161, such as an SMF 161 (step 2&5 of figure 2a), which establishes the PDU session for the MT 110 based on the policies of the mobile network provider (step 9.2&10 of figure 2a). The CP Access Manager Function 160 also requests the MT’s radio capabilities, and authorizes connections for the MT 110. Based on the available connections, the CP Access Manager 160 obtains the traffic profile (Service Data Flow (SDF) mapping to radio resources (step 11.2 of figure 2a) for each connection (allocated by the RAN 120) and the traffic measurement report of the respective radio access nodes to which the MT 110 is connected (step 12.2 of figure 2a). According to an embodiment, the CP Access Manager 160 forwards the PDU session establishment trigger (step 3 of figure 2a), available connections for the MT 110 (step 6.2 of figure 2a), a traffic profile for each connection available to the MT 110 (step 11.3 of figure 2a), and a traffic policy (step 9.3 of figure 2a) to the control plane entity 150, e.g. AA 150. The control plane entity 150, e.g. AA 150 further forwards the PDU session establishment trigger (step 4.2 of figure 2a) and available connections of the MT 110 (step 7 of figure 2a) to the AF 170.

[0122] The end-point application 191 may pre-configure its preferences for the access network connections / resources to be utilized by a user in the AF 170 orthe AF 170 may request the application 191 to provide its preferences when it receives the PDU session establishment trigger from the control plane entity 150, e.g. AA 150. Upon receiving the PDU session establishment trigger from the control plane entity 150, e.g. AA 150 (step 4.2 of figure 2a), the AF 170 replies to the AA 150 with its preferences for the network connections to be utilized by the MT 110 during the PDU session (step 8 of figure 2a). The preferences from the applications for the preferred access networks (and or its resources) may be based on many different criteria, e.g., to improve the QoE of users, load balancing, energy related considerations like preference of the access network that uses green energy sources, and the like.

[0123] The control plane entity 150, e.g. AA 150 transforms these preferences from applications into Traffic Distribution Markers like priorities in the SDT 152 based on the operator’s policies (step 9.1,9.2, 9.3 and 13 of figure 2a). An exemplary algorithm to generate the Traffic Distribution Markers will be described further below. The CP function 140 uses these Traffic Distribution Markers (along with other information like Traffic measurement reports from the RAT nodes (step 12.2 and 13 of figure 2a) to create one or more SDTs 152 for the MT 110, the RAN(s) 120 and the UP 130 and sends the SDT(s) 152 to the MT 110, RAN(s) node(s) and UP node(s) (step 15 offigure 2a). Once the PDU session is established and the MT HO has received the SDT 152, it uses the Traffic Distribution Markers in the SDT 152 to distribute the UL traffic on the available connections. Similarly, RAN(s) 120 and UP nodes 130 distribute the Down Link (DL) packets to the MT 110, i.e. UE 110 on the available connections and data channels DCi-DCnbased on the Traffic Distribution Markers in the SDT 152.

[0124] In the embodiment shown in figure 2b, the control plane entity 150, e.g. the AA functionality 150 is implemented as a component of a suitable CP function 140 in the mobile core network for a scenario where there is a change in the access network connections of the MT 110, for instance, when due to its mobility the MT 110 connects to a new access network (step 1 of figure 2b). When the user of the MT 110 wants to use the application 191 over the mobile network 100, the MT 110 requests the mobile network control plane to establish a PDU session for the MT. The PDU session establishment trigger is sent via the CP Access Manager Function 160, e.g. the AMF 160 to a Session Management Function 161, e.g. the SME 161 which establishes the PDU session for the MT 110 based on the policies of the mobile network provider. Once a PDU session is established, any changes to the session are performed by generating a PDU session modification trigger (step 1&2 of figure 2b). The PDU session modification trigger can be generated by any authorized participating entity during the ongoing PDU session, for instance, by the MT 110 and the SMF 161. When the PDU session establishment or modification trigger is received by the mobile network core CP, the CP Access Manager Function 160, e.g. the AMF 160 also requests the MT’s radio capabilities, and authorizes connections for the MT 110 (step 1 of figure 2b). Based on the available connections (step 5&6.2 of figure 2b), the CP Access Manager 160, e.g. the AMF 160 obtains the traffic profile (Service Data Flow (SDF) mapping to radio resources) for each connection (allocated by the RAN) (step 11.2 of figure 2b) and the traffic measurement report of the respective radio access nodes to which the MT 110 is connected. According to an embodiment, the CP Access Manager 160, e.g. the AMF 160 forwards the PDU session establishment / modification trigger, available connections for the MT 110 (step 3 of figure 2b), a traffic profile for each connection available to the MT 110 (step 11.2 of figure 2b), and a traffic policy to the control plane entity 150, e.g. the AA 150 (step 9.2&9.3 of figure 2b). In response, the control plane entity 150, e.g. AA 150 further forwards the PDU session establishment / modification trigger and available connections of the MT 110 to the AF 170 (step 4.2&7 of figure 2b).

[0125] The end-point application 191 may pre-configure its considerations, i.e. preferences for the access network connections / resources to be utilized by the user of the MT 110 in the AF 170 or the AF 170 may request the application 191 to provide its preferences when it receives the PDU session establishment / modification trigger from the control plane entity 150, e.g. the AA 150. Moreover, whenever there is any change in the connectivity of the MT 110, i.e. UE 110, e.g., when the UE 110 connects to a new access network node, the control plane entity 150, e.g. the AA 150 may send the PDU session modification trigger to the AF 170 with the current available connections for the UE 110 for the ongoing PDU session (step 4.2&7 of figure 2b). Upon receiving the PDU session establishment / modification trigger from the control plane entity 150, i.e. AA 150, the AF 170 replies to the control plane entity 150, i.e. AA 150 with its preference(s) for the network connections to be utilized by the MT 110 during the PDU session (step 8 of figure 2b). The preferences of the application(s) 191 for the preferred access networks (and or its resources) may be based on many different criteria, e.g., to improve the QoE of users, load balancing, energy related considerations like preference for an access network that uses green energy source, and the like.

[0126] The control plane entity 150, i.e. AA 150 transforms the preference(s) ofthe applications) 190 into Traffic Distribution Markers defining priorities in the SDT 152 based on the operator’s policies (step 3.1,4.1,6.1,7,8,9.1,11.1,12.1 and 13 of figure 2b). An exemplary algorithm for generating the Traffic Distribution Markers according to an embodiment will be described further below. The CP uses these Traffic Distribution Markers (along with other information like Traffic measurement reports from the RAT nodes) to create SDT(s) 152 for the MT 110, RAN(s) 120 and UP 130 and sends them to the MT 110, RAN(s) node(s) 120 and UP node(s) 130 (step 15 of figure 2b). Once the PDU session is established / modified and the MT 110 has received the updated SDT 152, it uses the Traffic Distribution Markers, i.e. priorities in the SDT 152 to distribute the UL traffic on the available connections. Similarly, RAN(s) 120 and UP nodes 130 distribute the Down Link (DL) packets to the UE 110, i.e. MT 110 on the available connections and data channels DCi-DCnbased on the Traffic Distribution Markers in the SDT 152.

[0127] In the embodiment shown in figure 2c, the control plane entity 150, i.e. AA functionality 150 is implemented as a component of a suitable CP function 140 in the mobile core network for a scenario where there is a change in the Application end point server’s operating condition like e.g., the load on the application server 191 is high and hence the application wants the MT 110 to not overload the server with high UL traffic by utilizing a high-speed network (see step 1 of figure 2c). When the user ofthe MT 110, i.e. UE 110 wants to use an application 191 over the mobile network 100, the MT 110 requests the mobile network control plane to establish a PDU session for the MT 110. The PDU session establishment trigger is sent via a CP Access Manager Function 160, e.g. the AMF 160 to a Session Management Function 161, e.g. the SMF 161 which establishes the PDU session for the MT 110 based on the policies of the mobile network provider. Once a PDU session is established, any changes to the session may be performed by generating a PDU session modification trigger (step 2 of figure 2c). The PDU session modification trigger may be generated by any authorized participating entity during the ongoing PDU session, such as the MT 110 and the SMF 161. When the PDU session establishment or modification trigger is received by the mobile network core CP, the CP Access Manager Function 160, e.g. the AMF 160 also requests the MT’s radio capabilities, and authorizes connections for the MT 110. Based on the available connections, the CP Access Manager 160, e.g. the AMF 160 obtains the traffic profile (Service Data Flow (SDF) mapping to radio resources) for each connection (allocated by the RAN(s) 120) and the traffic measurement report of the respective radio access nodes to which the MT 110 is connected (step 11.2 of figure 2c). According to an embodiment, the CP Access Manager 160, e.g. the AMF 160 may forward the PDU session establishment / modification trigger, available connections for the MT 110, a traffic profile for each connection available to the MT 110, and a traffic policy to the control plane entity 150, i.e. the AA 150 (step 3, 6.2,11.3 and 9.3 of figure 2c). Further, the control plane entity 150, i.e. the AA 150 forwards the PDU session establishment / modification trigger and available connections of the MT 110 to the AF 170 (step 4.2&7 of figure 2c).

[0128] The end-point application 191 may pre-configure its considerations, i.e. preferences for the access network connections / resources to be utilized by the user in the AF 170 or the AF 170 may request the application 191 to provide its preference(s) when it receives the PDU session establishment / modification trigger from the control plane entity 150, i.e. AA 150. Additionally, the application 191 may also dynamically adjust its considerations, i.e. preferences during an ongoing PDU session based on the condition / status of its end-points, i.e. the application server and / or the MT 110 (step 1 of figure 2c). Whenever there is a change on the application’ s end, the application 191 may inform the AF 170 for updating its preference(s) accordingly (step 1 of figure 2c). The considerations, i.e. preferences from the applications) 191 for the preferred access networks (and or its resources) may be based on many different criteria, e.g., to improve the QoE of users, load balancing, energy related considerations like preference for an access network that uses green energy source, and the like.

[0129] When the AF 170 receives an indication from the end-point application 191 regarding any change to its preference(s) for an ongoing PDU session, the AF 170 requests the currently available connections for the MT 110 from the control plane entity 150, i.e. the AA 150 and requests the control plane entity 150, i.e. the AA 150 to update the ongoing PDU session with the updated preference(s) of the application 191 (step 7&8 of figure 2c). Upon receiving the updates from the AF 170, the control plane entity 150, i.e. AA 150 transforms the preference(s) from the applications) 190 into Traffic Distribution Markers defining priorities in the SDT 152 based on the operator’s policies (step 13 of figure 2c). An exemplary algorithm for generating the Traffic Distribution Markers, i.e. priorities will be described below. The CP entity 140 uses these Traffic Distribution Markers (along with other information like Traffic measurement reports from the RAT nodes 120) to update the SDTs 152 for the MT 110, the RAN(s) 120 and the UP 130 and sends them respectively to the MT 110, the RAN(s) node(s) 120 and the UP node(s) 130 (step 15 of figure 2c). Once the MT 110 has received the updated SDT 152, it uses the Traffic Distribution Markers in the SDT 152 to distribute the UL traffic on the available connections. Similarly, the RAN(s) and UP nodes 120, 130 distribute the Down Link (DL) packets to the MT 110, i.e. UE 110 on the available connections and data channels DCi-DCnbased on the Traffic Distribution Markers in the SDT 152.

[0130] Figure 3 shows a signaling diagram illustrating the sequence of messages exchanged between the participating entities for an embodiment, where the control plane entity 150, i.e. the AA 150 is implemented as a component of the AMF 160 in the mobile core network control plane, and for the exemplary scenario, where the MT 110 requests the CP to establish a PDU session. When the MT 110 sends a PDU session establishment trigger, the RAT access node 120 forwards this request to the AMF 160 (step 301 of figure 3). The AMF 160 forwards this request to the SME 161 (step 303 of figure 3), and to the AA 150 inside the AMF 160. The AA 150 forwards the PDU session establishment trigger to the AF 170 (step 305 of figure 3). The AMF 160 receives the traffic management report from the RAT nodes 120 it is managing (step 307 of figure 3) and generates the available connections for each MT 110 and forwards this information to the AA 150 (step 309 of figure 3), which, in turn, forwards the information about the available connections to the AF 170 (step 311 of figure 3). In response, the AF 170 sends the application’s preferences for the MT 110 for the current / ongoing / to-be established PDU session to the AA 150 (step 313 of figure 3). The AMF 160 sends the traffic measurement report of the RAT nodes that are serving the MT 110 along with the traffic policies to the network function / module 140 that generates the SDT 152 (step 315 of figure 3). In this embodiment, the module 140 that generates the SDT 152 is also implemented as a component of the AMF 160 alongside the AA 150. The AMF 160 retrieves the traffic policy and traffic profile of the MT 110, i.e. UE 110 for the available connections (step 319 of figure 3) and the AA 150 generates the traffic distribution markers based on this information and the preferences received from the AF 170 (step 325 of figure 3). The AA 150 sends the traffic distribution markers to the network function / module 140 that generates the SDT 152, which in turn combines this information with the traffic measurement reports and traffic profile to generate the SDT 152 (steps 321, 323, 327 of figure 3). Once the SDTs 152 are generated, they are forwarded accordingly to the MT 110, the Radio Access Nodes 120, and User plane node 130, e.g. UPF 130 (steps 329, 331, 333, 335, 337 of figure 3).

[0131] Figure 4 shows a signaling diagram illustrating the sequence of messages exchanged between the participating entities for a further embodiment, where the control plane entity 150, i.e. the AA 150 is implemented as a component of the PCF 162 in the mobile core network control plane, and for the exemplary scenario, where the MT 110 requests the CP to establish a PDU session. When the MT 110 sends a PDU session establishment trigger, the RAT access node 120 forwards this request to the AMF 160 (step 401 of figure 4). The AMF 160 further forwards this request to the SMF 161, and to the AA 150 implemented as a component of the PCF 162 (steps 403, 405 of figure 4). The AA 150 forwards the PDU session establishment trigger to the AF 170 (step 409 of figure 4). The AMF 160 receives the traffic management report from the RAT nodes 120 it is managing (step 407 of figure 4) and generates the available connections for each MT 110 and forwards this information to the AA 150 inside the PCF 162 (step 411 of figure 4), which, in turn, forwards it to the AF 170 (step 413 of figure 4). In response, the AF 170 sends the application’s preferences for the MT 110 for the current / ongoing / to-be established PDU session to the AA 150 (step 415 of figure 4). The AA 150 receives the traffic policies from the PCF 162 (step 417 of figure 4) and sends the preferred connections to the PCF 162, which in turn forwards the traffic polices for the preferred connections to the AMF 160 (step 419 of figure 4). The AMF 160 responds by sending the traffic measurement reports of the RAT nodes 120 that are offering the preferred connections to the MT 110 to the network function / module 140 that generates the SDT 152 inside the PCF 162 (step 423 of figure 4). The AMF 160 also retrieves the traffic profile from these RAT nodes 120 for the MT 110 (step 421 of figure 4) and forwards this traffic profile to the network function / module 140 that generates the SDT 152 inside the PCF 162 (step 423 of figure 4). In the embodiment shown in figure 4, the module 140 for generating the SDT 152 is implemented as a component of the PCF 162 alongside the AA 150. The AA 150 generates the traffic distribution markers based on this information and the preferences received from the AF 170 (step 427 of figure 4). The AA 150 sends the traffic distribution markers to the network function / module 140 that generates the SDT 152, which in turn combines this information with the traffic measurement reports and traffic profile to generate the SDT 152 (steps 424, 425, 429 of figure 4). Once the SDTs 152 are generated, they are forwarded accordingly to the MT 110, the Radio Access Nodes 120, and the User plane node 130, e.g. the UPF 130 (steps 431, 433, 435, 437, 439 of figure 4).

[0132] In the following an exemplary algorithm will be described, which may be implemented by the control plane entity 150, i.e. the AA 150 according to an embodiment for generating the Traffic Distribution Markers, i.e. priorities for the SDT 152.

[0133] For a given state S = {X, R, T, A, DC} where,

[0134] X = set of all networks that MT 110 is connected to {ANi ... ANn}

[0135] R = set of all RAT nodes 120 of X networks {(n, ANi), ..., (rn, ANn)}

[0136] T = set of all traffic policies for R nodes 120 of X networks {(ti, ANi), ... ,(tn, ANn)} A = set of all preferred networks {ANi ... ANn} where A <= X

[0137] M = set of total traffic allowed on RAT nodes 120 based on measurement report {(n, mi), (n, mi), ... , (rn, mn)} TS = set of all traffic policies for R nodes ofA networks {(ti, ANi), ...,(tn, ANn)}

[0138] DC = set of all data channels offered by R nodes of A networks {(ANi, {di...dn}), (AN?, {di...dn}) ,(ANn, {di ...dn})} VANi where ANi e A and 0 < i < |X1|, ti e TS, mi e M, 0 < pi < 100 and 0 < i < | TV |

[0139] In the algorithm shown above, the AA 150 retrieves the information on the networks that an MT 110 is connected to, and the corresponding RAT nodes 120 and their traffic policies. Based on this the AA 150 then retrieves the preferred networks from the application 191 via AF 170. The AA 150 then retrieves the measurement report of the RAT nodes 120 from the preferred networks, their traffic profiles and their policies. Based on the received information, the AA 150 generates the priorities for the access network resources provided by the RAT nodes 120 i.e., assigns priorities to the Data Channels offered by the RAT nodes. The AA 150 forwards these priorities (Traffic Distribution Markers) to the respective CP feature that is responsible for creating / updating and managing the SDT. The CP feature, based on measurement reports of the RAT nodes 120, policies of the network and other factors creates / updates the SDT with the Traffic Distributions Markers (priorities) received from the AA 150 and forwards them accordingly to the MT 110, the Radio Access Nodes 120, and the User plane node 130, e.g. the UPF 130.

[0140] Figure 5a shows the architecture of the mobile network 100 including the control plane entity 150, i.e. AA 150 according to an embodiment in the form of a 3GPP system 100, such as a 5G or 6G system 100. As will be appreciated, the embodiment of the 3GPP system 100 shown in figure 5a differs from a conventional 3GPP system primarily in the following aspects. The embodiment of the 3GPP system 100 shown in figure 5a comprises the control plane entity 150, i.e. AA 150, which, as already described above, may be implemented as a component of a control plane network function, such as the AMF 160. In the embodiment of the 3GPP system 100 shown in figure 5a the AA 150 receives the PDU session establishment / modification trigger, available connections for the MT 110, and a traffic profile from the AMF 160, traffic policies from the PCF 162 and preferences of the application 191 on the available connections from the AF 170, as already described above in great detail. Based on the application’s preference, traffic policy and available connections, the AA 150 generates the Traffic Distribution Markers, i.e. priorities and sends them to the network function / module 140 that generates the SDT 152. Based on the Traffic Distribution Markers, traffic measurement reports, traffic profiles and network policies the responsible network function / module 140 generates the SDTs 152 and forwards them to the MT 110, the RAT nodes 120 and the UP node(s) 130, e.g. the UPF 130. As will be appreciated, the embodiment ofthe 3GPP system 100 shown in figure 5a may comprise the further entities and / or interfaces of a conventional 3GPP system, as illustrated in figure 5a, namely a NRF 163, a NWDAF 164, a NEF 165, and / or a UDM 166 with the corresponding interfaces.

[0141] Figure 5b shows the architecture of the mobile network 100 including the control plane entity 150, i.e. AA 150 according to a further embodiment in the form of a 3GPP system 100, such as a 5G or 6G system 100. As will be appreciated, the embodiment of the 3GPP system 100 shown in figure 5b differs from a conventional 3GPP system primarily in the following aspects. The embodiment of the 3GPP system 100 shown in figure 5b comprises the control plane entity 150, i.e. AA 150, which, as already described above, may be implemented as a component of a control plane network function, such as the PCF 162. The AA 150 receives the PDU session establishment / modification trigger, available connections for the MT 110, and traffic profile from the AMF 160, traffic policies from the PCF 162 and preferences of the application 191 on the available connections from the AF 170. Based on the application’s preferences, traffic policy and available connections, the AA 150 generates the Traffic Distribution Markers, i.e. priorities and sends them to the network function / module 140 that generates the SDT 152, as already described in great detail above. Based on the Traffic Distribution Markers, i.e. priorities, the traffic measurement reports, the traffic profiles and the network policies, the responsible network function / module 140 generates the SDTs 152 and forwards them to the MT 110, the RAT nodes 120 and the UP node(s) 130, e.g. the UPF 130. As will be appreciated, the embodiment of the 3GPP system 100 shown in figure 55 may comprise the further entities and / or interfaces of a conventional 3GPP system, as illustrated in figure 5b, namely a NRF 163, a NWDAF 164, a NEF 165, and / or a UDM 166 with the corresponding interfaces. Figure 6 shows a flow diagram showing steps of a method 600 for operating a control plane entity 150 for controlling traffic to and / or from a user equipment, UE, application on a UE 110 via one or more base stations providing one or more access networks 120 and for each access network a plurality of data channels DCi-DCnin a mobile network 100. The method 600 comprises a step 601 of obtaining preference information representative of one or more preferred access networks of the one or more access networks 120 and / or one or more preferred data channels of the plurality of data channels DCi-DCnfor the traffic to and / or from the UE application. Moreover, the method 600 comprises a step 603 of generating mapping data based on the preference information, wherein the mapping data defines a mapping between traffic to and / or from the UE application to one or more of the plurality of data channels DCi-DCn of the one or more access networks 120.

[0142] The method 600 can be performed by the control plane entity 150 according to an embodiment. Thus, further features of the method 600 result directly from the functionality of the control plane entity 150 as well as the different embodiments thereof described above and below.

[0143] The person skilled in the art will understand that the "blocks" ("units") of the various figures (method and apparatus) represent or describe functionalities of embodiments of the present disclosure (rather than necessarily individual "units" in hardware or software) and thus describe equally functions or features of apparatus embodiments as well as method embodiments (unit = step).

[0144] In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus, and method may be implemented in other manners. For example, the described embodiment of an apparatus is merely exemplary. For example, the unit division is merely a logical function division and may be another division in an actual implementation. For example, a plurality of units or components may be combined or integrated into another system, or some features may be ignored or not performed. In addition, the displayed or discussed mutual couplings or direct couplings or communication connections may be implemented by using some interfaces. The indirect couplings or communication connections between the apparatuses or units may be implemented in electronic, mechanical, or other forms.

[0145] The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one position, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.

[0146] In addition, functional units in the embodiments of the disclosure may be integrated into one processing unit, or each of the units may exist alone physically, or two or more units may be integrated into one unit.

Claims

CLAIMS1. A control plane entity (150) for controlling traffic to and / or from a user equipment, UE, application on a UE (110) via one or more base stations providing one or more access networks (120) and for each access network a plurality of data channels (DCi-DCn) in a mobile network (100), wherein the control plane entity (150) is configured to: obtain preference information representative of one or more preferred access networks of the one or more access networks (120) and / or one or more preferred data channels of the plurality of data channels (DCi-DCn) for the traffic to and / or from the UE application; and generate mapping data based on the preference information, wherein the mapping data defines a mapping between traffic to and / or from the UE application to one or more of the plurality of data channels (DCi-DCn) of the one or more access networks (120).

2. The control plane entity (150) of claim 1, wherein the control plane entity (150) is configured to provide the mapping data to a network function (140; 160; 162) of the mobile network (100) for including the mapping data in a data structure (152), wherein the network function (140; 160; 162) is configured to provide the data structure (152) to the UE (110), the one or more base stations and / or a user plane entity (130) of the mobile network (100).

3. The control plane entity ( 150) of claim 2, wherein the data structure ( 152) is a table (152).

4. The control plane entity (150) of any one of the preceding claims, wherein the mapping data comprises a plurality of priority values, wherein each priority value assigns a priority to each of the plurality of data channels (DCi-DCn) of the one or more access networks (120) for mapping traffic to and / or from the UE application to one or more of the plurality of data channels (DCi-DCn) of the one or more access networks (120).

5. The control plane entity (150) of any one of the preceding claims, wherein the control plane entity (150) is configured to receive a UE protocol data unit, PDU, session establishment trigger indicative of a UE PDU session and to generate the mapping data for the UE PDU session.

6. The control plane entity (150) of claim 5, wherein the control plane entity (150) is configured to receive the UE PDU session establishment trigger from an Access and Mobility Management Function, AMF, (160) of the mobile network (100).

7. The control plane entity (150) of any one of the preceding claims, wherein the control plane entity (150) is configured to obtain the preference information from an application (191) via an Application Function, AF, (170) of the mobile network (100) associated with the UE application.

8. The control plane entity (150) of claim 6, wherein the control plane entity (150) is configured to obtain the preference information from the AF (170) associated with the UE application, in response to forwarding availability information to the AF (170) associated with the UE application, wherein the availability information is representative of the one or more access networks (120) and for each access network the plurality of data channels (DCi-DCn).

9. The control plane entity (150) of claim 8, wherein the control plane entity (150) is configured to generate the mapping data based further on the availability information.

10. The control plane entity (150) of any one of the preceding claims, wherein the control plane entity (150) is further configured to obtain network traffic policy information representative of one or more network traffic policies implemented by the mobile network (100) and wherein the control plane entity (150) is configured to generate the mapping data based further on the network traffic policy information.

11. A network function entity (140; 160; 161 ) of a mobile network (100) comprising a control plane entity (150) according to any one of the preceding claims, wherein the network function entity (140; 160; 161) is configured to: obtain the mapping data from the control plane entity (150); include the mapping data in a data structure (152); and provide the data structure (152) to the UE (110), the one or more base stations and / or a user plane entity (130) of the mobile network (100).

12. The network function entity (140; 160; 161) of claim 11, wherein the network function entity (140; 160; 161) is an Access and Mobility Management Function, AMF, entity (160) or a Policy Control Function, PCF, entity (161) of the mobile network (100).

13. A method (600) for operating a control plane entity (150) for controlling traffic to and / or from a user equipment, UE, application on a UE (110) via one or more base stations providing one or more access networks (120) and for each access network a plurality of data channels (DCi-DCn) in a mobile network (100), wherein the method (600) comprises: obtaining (601) preference information representative of one or more preferred access networks of the one or more access networks (120) and / or one or more preferred data channels of the plurality of data channels (DCi-DCn) for the traffic to and / or from the UE application; and generating (603) mapping data based on the preference information, wherein the mapping data defines a mapping between traffic to and / or from the UE application to one or more of the plurality of data channels (DCi-DCn) of the one or more access networks (120).

14. A computer program product comprising a computer-readable storage medium for storing program code which causes a computer or a processor to perform the method (600) of claim 13, when the program code is executed by the computer or the processor.

Images