[go: up one dir, main page]

WO2025237529A1 - Dispositifs et procédés d'ingénierie de trafic à connectivité multiple - Google Patents

Dispositifs et procédés d'ingénierie de trafic à connectivité multiple

Info

Publication number
WO2025237529A1
WO2025237529A1 PCT/EP2024/063549 EP2024063549W WO2025237529A1 WO 2025237529 A1 WO2025237529 A1 WO 2025237529A1 EP 2024063549 W EP2024063549 W EP 2024063549W WO 2025237529 A1 WO2025237529 A1 WO 2025237529A1
Authority
WO
WIPO (PCT)
Prior art keywords
control plane
entity
plane entity
traffic
network
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/EP2024/063549
Other languages
English (en)
Inventor
Sripriya Srikant ADHATARAO
Zoran Despotovic
Artur Hecker
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to PCT/EP2024/063549 priority Critical patent/WO2025237529A1/fr
Publication of WO2025237529A1 publication Critical patent/WO2025237529A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/72—Admission control; Resource allocation using reservation actions during connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/80—Actions related to the user profile or the type of traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5003—Managing SLA; Interaction between SLA and QoS
    • H04L41/5019—Ensuring fulfilment of SLA
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/82—Miscellaneous aspects
    • H04L47/822—Collecting or measuring resource availability data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/83—Admission control; Resource allocation based on usage prediction

Definitions

  • the present disclosure relates to wireless communications. More specifically, the present disclosure relates to devices and methods for leveraging multi -connectivity to perform traffic engineering in a mobile communication system, in particular a 3 GPP mobile communication system.
  • 5G and a communication network in the future are expected to provide various services to billions of globally distributed users, including machines, loT devices and sophisticated (future) mobile end-devices from applications like Artificial Reality (AR)/Virtual Reality (VR), holographic communications, and the like, with stringent performance requirements.
  • AR Artificial Reality
  • VR Virtual Reality
  • holographic communications and the like, with stringent performance requirements.
  • 3GPP 3rd Generation Partnership Project
  • UEs are equipped with multiple network interfaces e.g., 4G (LTE), 5G and Wireless Fidelity (Wi-Fi), and will most-likely be extended to include interface for communication network in the future and NTN related interfaces. Due to the availability of multiple access technologies in 5G and communication network in the future, interoperation among them is deemed imperative. Multi-connectivity has the potential to improve reliability, scalability, and throughput along with a noticeable reduction in latency experienced by current end users.
  • LTE Long Term Evolution
  • Wi-Fi Wireless Fidelity
  • the current cellular network standard namely, 3GPP permits the User Equipment (UE) to a maximum of two to three simultaneous connections (4G and 5G) in Dual Connectivity (DC), Multi Radio Dual Connectivity (MR-DC) and Access Traffic Steering, Switching & Splitting (ATSSS) (5G and Wi-Fi) solutions.
  • UE User Equipment
  • DC Dual Connectivity
  • MR-DC Multi Radio Dual Connectivity
  • ATSSS Access Traffic Steering, Switching & Splitting
  • a QoS flow is mapped to a single data channel provided by a dedicated access network node (post registration and as per operator’s configurations).
  • the mapping of a QoS flow to a data channel remains fixed throughout the lifetime of a PDU session or until the connection is available to the UE from that access node. Except in the case of ATSSS, where the traffic from a QoS Flow can be split (not distributed!) on the data channel provided by the 3GPP access node and on the Wi-Fi node.
  • traffic steering is applied for the uplink traffic in Core Network to direct traffic to a pre-configured DNAI while traffic steering in ATSSS splits the traffic between 3GPP and non-3GPP network.
  • the load in the Radio Access Network (RAN) is balanced via handovers between neighboring Base Stations and via offloading the mobile IP traffic to traditional IP networks.
  • RAN Radio Access Network
  • 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 of, 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 drawback of such fixed assignment includes in-efficient resource utilization, limited throughput, scalability, latency and non-seamless connectivity during mobility.
  • a control plane entity for controlling traffic (herein also referred to as traffic engineering) to and/or from a user equipment, UE, application on a UE via one or more base stations associated with one or more access networks and for each access network a plurality of data channels in a mobile network.
  • the control plane entity according to the first aspect is configured to obtain, for each of the plurality of data channels, traffic information indicative of the past and/or current traffic via each of the plurality of data channels.
  • control plane entity according to the first aspect is configured to generate mapping data based on the traffic information for each of the plurality of data channels, 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 of the one or more access networks.
  • mapping data 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.
  • control plane entity is configured to provide the mapping data to a network function 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.
  • the data structure is a table. This allows to provide the mapping in an efficient manner to the UE, the one or more base stations and/or a user plane entity of the mobile network.
  • the mapping data comprises a plurality of weights (herein also referred to as traffic distribution markers), wherein each weight assigns a weight 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.
  • each weight assigns a weight 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.
  • the control plane entity 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. This allows the control plane entity according to the first aspect to dynamically distribute the traffic for a UE PDU session in a mobile network leveraging the available information for using the heterogeneous resources of a mobile network more efficiently.
  • control plane entity is configured to receive the UE PDU session establishment trigger from an Access and Mobility Management Function, AMF, of the mobile network. This allows to seamlessly integrate the control plane entity according to the first aspect in a 5G mobile network.
  • AMF Access and Mobility Management Function
  • control plane entity is configured to generate the mapping data based further on availability information, wherein the availability information is indicative of which of the plurality of data channels is currently available. In other words, based on the availability information the control plane entity may determine which data channels are currently available fortransporting traffic to and/or from the UE. This allows the control plane entity according to the first aspect to generate more accurate mapping data.
  • control plane entity is configured to obtain the availability information from an Access and Mobility Management Function, AMF, of the mobile network. This allows to seamlessly integrate the control plane entity according to the first aspect in a 5G mobile network.
  • AMF Access and Mobility Management Function
  • control plane entity is configured to generate the mapping data based further on policy information, wherein the policy information is indicative of one or more policy goals, i.e. policy constraints, to be achieved by the mapping between the traffic to and/or from the UE application to the one or more of the plurality of data channels of the one or more access networks.
  • policy goals may comprise one or more policy constraints, such as a maximum bandwidth of a data channel, that should be met by the traffic resulting from the mapping data. This allows the control plane entity according to the first aspect to generate more accurate mapping data.
  • control plane entity is configured to obtain the policy information from a Policy Control Function, PCF, of the mobile network.
  • PCF Policy Control Function
  • control plane entity is configured to obtain the current traffic information from one or more user plane entities of the mobile network. This allows to seamlessly integrate the control plane entity according to the first aspect in a 5G mobile network.
  • a network function entity of a mobile network comprising a control plane entity according to the first aspect.
  • the network function entity is configured to obtain the mapping data from the control plane entity and to include the mapping data in a data structure, in particular in the form of a table.
  • the network function entity is further 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.
  • the network function entity is an Access and Mobility Management Function, AMF, of the mobile network.
  • AMF Access and Mobility Management Function
  • the method according to the third aspect comprises: obtaining, for each of the plurality of data channels, traffic information indicative of the previous and/or current traffic via each of the plurality of data channels; and generating mapping data based on the traffic information for each of the plurality of data channels, 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 of the one or more access networks.
  • the method according to the third aspect can be performed by the control plane entity according to the first aspect.
  • 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.
  • a computer program product 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.
  • Fig. 1 is a schematic diagram illustrating a mobile telecommunication system comprising a control plane entity according to an embodiment for generating mapping data for establishing and using multi-connectivity communication for a UE with a data network;
  • Fig. 2 is a schematic diagram illustrating a network congestion scenario as an exemplary use case for a control plane entity according to an embodiment for generating mapping data for establishing multi-connectivity communication for a UE with a data network;
  • Fig. 3 is a schematic diagram illustrating in more detail an algorithm implemented by a control plane entity according to an embodiment for generating mapping data for establishing and using multi-connectivity communication for a UE with a data network;
  • Fig. 4 is a signalling diagram illustrating operations and interactions of a control plane entity according to an embodiment with other network entities of a mobile network for generating mapping data for establishing and using multi-connectivity communication for a UE with a data network;
  • Fig. 5 is a signalling diagram illustrating operations and interactions of a control plane entity according to a further embodiment with other network entities of a mobile network for generating mapping data for establishing and using multiconnectivity communication for a UE with a data network
  • Fig. 6 is a signalling diagram illustrating operations and interactions of a control plane entity according to a further embodiment with other network entities of a mobile network for generating mapping data for establishing and using multiconnectivity communication for a UE with a data network;
  • Fig. 7a is a schematic diagram illustrating the architecture of a mobile telecommunication system comprising a control plane entity according to an example, wherein the control plane entity is implemented as a component of a network function;
  • Fig. 7b is a schematic diagram illustrating the architecture of a mobile telecommunication system comprising a control plane entity according to an example, wherein the control plane entity is implemented as a component of an AMF;
  • Fig. 7c is a schematic diagram illustrating the architecture of a mobile telecommunication system comprising a control plane entity according to an example, wherein the control plane entity is implemented as a stand-alone entity;
  • Fig. 7d is a schematic diagram illustrating the architecture of a mobile telecommunication system comprising a control plane entity according to a further example, wherein the control plane entity is implemented as a stand-alone entity;
  • Fig. 8 is a flow diagram illustrating a method for operating a control plane entity according to an example for generating mapping data for establishing and using multi-connectivity communication for a UE with a data network.
  • 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.
  • 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.
  • a specific apparatus is described based on one or a plurality of units, e.g.
  • 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.
  • AMF Access and Mobility Management Function
  • NWDAF Network Data Analytics Function
  • Non-Terrestrial Network NTN NTN
  • Radio Access Network RAN Radio Access Network
  • Radio Access Technology RAT Radio Access Technology
  • FIG 1 shows a schematic diagram illustrating a mobile telecommunication system 100 (also referred to as mobile network 100) comprising a control plane entity 141 (referred to as Multi-Access Traffic Engineering, MATE, entity in figure 1) according to an embodiment for controlling traffic (herein also referred to as traffic engineering) to and/or from a user equipment, UE, application on a UE 110 via one or more base stations associated with one or more access networks 120 and for each access network 120 a plurality of data channels in the mobile communication system 100.
  • the control plane entity 141 i.e. MATE entity 141 is configured to obtain, for each of the plurality of data channels, traffic information indicative of the past and/or current traffic via each of the plurality of data channels.
  • the mobile telecommunication system 100 is a 3rd Generation Partnership Project (3GPP) mobile telecommunication system 100.
  • 3GPP 3rd Generation Partnership Project
  • the UE 110, the base stations 120, i.e. the access network nodes 120, and the network entity 130 are configured to make use of a mapping data structure 142, in particular a mapping table 142 (herein also referred to as Service data flow Distribution Table, SDT, 142) for establishing and using multi -connectivity communication between the UE 110 and, for instance, an end-point application via the data network 170, such as the Internet 170.
  • the control plane entity 141 i.e. MATE entity 141 may receive the traffic information periodically or dynamically in the form of traffic measurement reports from the access network nodes 120 and/or user plane entities 130, e.g. user plane functions 130 along communication paths between the UE 110 and a data network 170.
  • control plane entity 141 i.e. MATE entity 141 is further configured to generate mapping data based on the traffic information for each of the plurality of data channels, wherein he mapping data defines a mapping between traffic to and/or from the UE application running on the UE 110 to one or more of the plurality of data channels of the one or more access networks 120.
  • mapping data the control plane entity 141, i.e. MATE entity 141 allows supporting the dynamic distribution of traffic in the mobile network 100 leveraging the available information for using the heterogeneous resources of the mobile network 100 more efficiently.
  • the control plane entity 141 i.e. MATE entity 141 may support dynamically distributing the traffic so that the network congestion is reduced.
  • the UE 110 is configured to establish 1 or more connections with a single or multiple access nodes 120 of similar or different technologies simultaneously and to initiate the data transfer through establishing the required connections for its data transfer session.
  • the UE 110 may begin with sending a PDU session establishment request indicating in its request whether a single access or multiple access connection(s) should be established.
  • the responsible control plane entity 141 may establish the requested connection(s) over available access networks 120 based on the policy of the network 100 and UE’s subscriptions and radio capabilities.
  • the responsible control plane network entity like an access manager e.g., AMF 150 may retrieve the traffic measurement report from the access nodes 120 and the traffic profile which provides the details on the radio resources allocated for the UE 110 on the respective access node 120.
  • the traffic profile may contain a mapping of the SDF flows to the radio resources for creating the SDT.
  • the access manager forwards to the control plane entity 141, i.e. MATE entity 141 according to an embodiment the information regarding the connections available for the UE 110, the measurement reports from the respective access nodes 120 and their traffic profiles for the session of the UE 110.
  • the control plane entity 141 i.e. MATE entity 141 according to an embodiment also retrieves the traffic policy for each of the available connections for the UE 110, the UE specific policies and the traffic report from corresponding Core Network User Plane node(s) 130 that are serving the UE’s PDU session.
  • the control plane entity 141 i.e. MATE entity 141 according to an embodiment may use an algorithm to generate the mapping data in the form of weights (herein referred to as Traffic Distribution Markers) that reflect the desired traffic flow on the available resources in the network 100.
  • the control plane entity 141 i.e. MATE entity 141 according to an embodiment receives the measurement reports in a stage 311 and is configured to request the available connections for the UE 110 in a stage 312.
  • the control plane entity 141, i.e. MATE entity 141 is configured to request the network traffic policy for the selected RAT.
  • control plane entity 141 i.e. MATE entity 141 according to an embodiment is configured to request SDF Flow to RAT node resource mapping.
  • control plane entity 141 i.e. MATE entity 141 according to an embodiment is configured to generate the mapping data, e.g. the traffic distribution weights using the algorithm described below.
  • the traffic distribution weights are included in the SDT(s) 142.
  • the SDT(s) are provided to the UE 110, the RAN(s) 120 and the UP entities 130.
  • the control plane entity 141 i.e.
  • MATE entity 141 receives the AN traffic measurement reports from the RAT nodes 120, the availability information from a CP access manager 150, for instance, the AMF 150, the traffic policy from a CP policy manager 152, for instance, the PCF 152, and the UP traffic measurement reports from the UP node(s) 130 and a CP session manager 151, for instance, the SMF 151.
  • control plane entity 141 i.e. MATE entity 141 may be configured to implement an algorithm of the following kind for generating the weights, i.e. Traffic Distribution Markers:
  • W total traffic per SDF carried over N data channels of X AN nodes
  • the amount of traffic per SDF carried over a data channel dci of an AN node xj (where xj e X, 0 ⁇ x ⁇ dci e (xj, ⁇ dci, dc2,...dcn ⁇ ), 0 ⁇ i ⁇
  • control plane entity 141 i.e. MATE entity 141 uses the Traffic Distribution Markers to create one or more data structures 142, in particular one or more tables 142 (herein referred to as SDTs 142) for the UE 110, the access network nodes 120 and Core Networks UPs 130 and forwards the SDTs 142 respectively to the UE 110, RAN(s) UP node(s) 120 and Core Networks UP node(s) 130.
  • SDTs 142 the Traffic Distribution Markers
  • the UE 110 uses the Traffic Distribution Markers i.e., weights in the SDT 142 to distribute the Uplink (UL) traffic on the available connections e.g., send more traffic on the links with higher weights.
  • the UP nodes 120, 130 in RAN(s) and Core Network distribute the Down Link (DL) traffic to UE110 on the available connections and data channels DCi-DCn based on the weights in their SDT 142s.
  • the traffic reports, traffic profiles and network policies may be received by the control plane entity 141, i.e.
  • the MATE entity 141 to dynamically update the corresponding SDTs 142 for the UE 110, the RAN nodes 120 and Core Network UP nodes 130 such that the traffic is always uniformly distributed on the available resources reflecting the operational state of the network 100. Further details about how the UE 110, access nodes 120 and Core Network UP nodes 130 may use the SDTs 142 for distributing traffic are described in PCT/EP2023/070879, which is fully incorporated herein by reference.
  • Figure 4 is a signaling diagram illustrating operations and interactions of the control plane entity 141, i.e. the MATE entity 141 according to an embodiment with other network entities of the mobile network 100 for generating mapping data for establishing multi-connectivity communication for the UE 110 with the data network 170.
  • the control plane entity 141 i.e. the MATE entity 141 according to an embodiment with other network entities of the mobile network 100 for generating mapping data for establishing multi-connectivity communication for the UE 110 with the data network 170.
  • step 1 of figure 4 the UE 110 issues a PDU session establishment request for either a single access or for multiple accesses, MA, and forwards the request to the network 100, in particular the control plane entity 141, i.e. the MATE entity 141.
  • control plane entity 141 While establishing the requested PDU session for the UE 110, the control plane entity 141 implementing the MATE functionality retrieves in step 2 of figure 4 the network configurations indicating the allocated connections for the UE 110 from the responsible network entity 160.
  • control plane entity 141 retrieves the network policies for traffic distribution and policies applicable for the UE 110 and its requested PDU session.
  • control plane entity 141 implementing the MATE functionality retrieves the information on the available access connections from the Core Network User Plane 130 which provides information regarding the active connections between the Core Network and Access Network nodes 120 in the user plane.
  • control plane entity 141 implementing the MATE functionality retrieves the traffic filters (traffic profiles) for the UE’s requested PDU session from the Access Network node(s) 120.
  • control plane entity 141 implementing the MATE functionality retrieves the traffic measurement report from the Core Network User Plane 130.
  • control plane entity 141 implementing the MATE functionality retrieves the traffic measurement report from the Access Network nodes 120.
  • step 8 of figure 4 the control plane entity 141 implementing the MATE functionality generates the traffic distribution markers in the form of weights.
  • control plane entity 141 implementing the MATE functionality creates the SDT 142 with the weights for the UE 110, the access nodes 120 and the user plane nodes 130.
  • control plane entity 141 implementing the MATE functionality sends the SDT 142 to the access nodes 120, the UE 110 and the core network user plane nodes 130.
  • FIG. 5 is a signaling diagram illustrating operations and interactions of the control plane entity 141, i.e. the MATE entity 141 according to a further embodiment with other network entities of the mobile network 100 for generating mapping data for establishing multi-connectivity communication for the UE 110 with the data network 170.
  • the MATE entity 141 is implemented as a component of the MAF entity 140.
  • step 1 of figure 5 the UE 110 issues a PDU session establishment request for either a single access or for multiple accesses and forwards the request to the network, in particular the MATE entity 141 and the MAF entity 140.
  • the MAF entity 140 retrieves the network configurations indicating the allocated connections for the UE 110 from the responsible network entity, e.g. the AMF 150 and forwards it to the control plane entity MATE entity 141, which, as already mentioned above, in this embodiment is implemented as a component of the MAF entity 140.
  • the responsible network entity e.g. the AMF 150
  • the control plane entity MATE entity 141 which, as already mentioned above, in this embodiment is implemented as a component of the MAF entity 140.
  • the MATE entity 141 requests the MAF entity 140 to retrieve the network policies for traffic distribution and policies applicable for the UE 110 and its requested PDU session and receives the requested information from the responsible network entity, e.g. a PCF 151 via the MAF entity 140.
  • the responsible network entity e.g. a PCF 151
  • the MATE entity 141 requests the MAF entity 140 to retrieve the information on the available access connections from the Core Network User Plane 130 which provides information regarding the active connections between the Core Network and Access Network nodes 120 in the user plane and receives the requested information from the Core Network User Plane 130 via the MAF entity 140.
  • step 5 of figure 5 the MATE entity 141 retrieves via the MAF entity 140 the traffic measurement report from the Core Network User Plane 130.
  • the MATE entity 141 requests the MAF entity 140 to retrieve the traffic filters (traffic profiles) for the UE’s requested PDU session from the Access Network node(s) 120.
  • the MAF entity 140 requests the responsible network entity, e.g. the AMF 150 of the mobile network 100, to retrieve the traffic filters and forwards it to the MATE entity 141.
  • the MATE entity 141 retrieves via the MAF entity 140 the traffic measurement report from the access network nodes 120.
  • the MATE entity 141 generates the traffic distribution markers in the form of weights and provides the weights to the MAF entity 140 for creating the one or more SDTs 142.
  • the MAF entity 140 creates the one or more SDTs 142 with the weights for the UE 110, the access nodes 120 and the user plane nodes 130.
  • the MAF entity 140 sends the one or more SDTs 142 to the access nodes 120, the UE 110, and the core network user plane nodes 130.
  • Figure 6 is a signaling diagram illustrating operations and interactions of the control plane entity 141, i.e. the MATE entity 141 according to a further embodiment with other network entities of the mobile network 100 for generating mapping data for establishing multi-connectivity communication for the UE 110 with the data network 170.
  • the MATE entity 141 and the MAF entity 140 are implemented as a component of the AMF 150 of the mobile network 100.
  • step 1 of figure 6 the UE 110 issues a PDU session establishment request for either a single access or for multiple accesses and forwards the request to the network, in particular the AMF 150 including the MATE entity 141 and the MAF entity 140.
  • the AMF 150 retrieves the network configurations indicating the allocated connections for the UE 110 and forwards it to the MATE entity 141, which is implemented as a component of the AMF 150.
  • step 3 of figure 6 the MATE entity 141 requests the AMF 150 to retrieve the network policies for traffic distribution and policies applicable for the UE 110 and its requested PDU session and receives the requested information from the responsible network entity via the AMF 150.
  • the MATE entity 141 requests the AMF 150 to retrieve the information on the available access connections from the Core Network User Plane 130 which provides information regarding the active connections between the Core Network and Access Network nodes 120 in the user plane and receives the requested information from the Core Network User Plane 130 via the AMF 150.
  • step 5 of figure 6 the MATE entity 141 retrieves via the AMF 150 the traffic measurement report from the Core Network User Plane 130.
  • the MATE entity 141 requests the AMF 150 to retrieve the traffic filters (traffic profiles) forthe UE’s requested PDU session from the Access Network node(s) 120.
  • the AMF 150 retrieves the traffic filters from the respective access nodes 120 and forwards it to the MATE entity 141.
  • step 7 of figure 6 the MATE entity 141 retrieves via the AMF 150 the traffic measurement report from the access network nodes 120.
  • the MATE entity 141 In step 8 of figure 6, the MATE entity 141 generates the traffic distribution markers in the form of weights and provides the weights to the MAF entity 140 for creating the one or more SDTs 142. In step 9 of figure 6, the MAF entity 140 creates the one or more SDTs 142 with the weights for the UE 110, the access nodes 120 and the user plane nodes 130.
  • the MAF entity 140 sends the one or more SDTs 142 to the access nodes 120, the UE 110, and the core network user plane nodes 130.
  • FIGS 7a-d are schematic diagrams illustrating different architectures of the mobile telecommunication system 100 for implementing the control plane entity 141, i.e. MATE entity 141 according to an embodiment.
  • the mobile network 100 may comprise one or more of the following network functions: AMF 150, SMF 151, PCF 152, UDM 153.
  • control plane entity 141 i.e. MATE entity 141 is implemented as a component of the MAF (Multi-Access Traffic Engineering) entity 140, which itself may be implemented as a control plane function.
  • MATE entity 141 and/or the MAF entity 140 are configured to: retrieve traffic information from access network nodes 120 and core network user plane nodes 130 e.g., current traffic load; retrieve Traffic Filters from the access network nodes 120; retrieve access availability information from the core network user plane nodes 130; retrieve any Traffic related Policies from Management Plane and/or Core Network Control Plane; generate Traffic Distribution configurations for SDT 142, e.g., weights; and/or send the weights to MAF entity 140, wherein the MAF entity creates the SDT(s) 142 with the weights and sends the SDT(s) 142 to the UE 11 '0, (R)AN and Core Network user plane nodes 120, 130.
  • MAF Multi-Access Traffic Engineering
  • control plane entity 141 i.e. MATE entity 141 and the MAF entity 140 are implemented as components of the AMF 150 of the mobile network 100.
  • control plane entity 141 i.e. MATE entity 141 and the MAF entity 140 are implemented as components of the AMF 150 of the mobile network 100.
  • control plane entity 141 i.e. MATE entity 141 and the MAF entity 140 are implemented as components of the AMF 150 of the mobile network 100.
  • control plane entity 141 i.e.
  • MATE entity 141 and the MAF entity 140 as components of the AMF 150 are configured to: retrieve the traffic information from access network nodes 120 and core network user plane nodes 130 e.g., current traffic load via the AMF 150; retrieve Traffic Filters from the access network nodes 120 via the AMF 150; retrieve Access Availability Information from the core network user plane nodes 130; retrieve any Traffic related Policies from Management Plane and/or Core Network Control Plane; generate Traffic Distribution configurations for the SDT(s) 142, e.g., weights; and/or send the weights to MAF entity 140, wherein the MAF entity creates the SDT(s) 142 with the weights and sends the SDT(s) 142 to the UE 11 '0, (R)AN and Core Network user plane nodes 120, 130.
  • the MAF entity creates the SDT(s) 142 with the weights and sends the SDT(s) 142 to the UE 11 '0, (R)AN and Core Network user plane nodes 120, 130.
  • control plane entity 141 i.e. MATE entity 141 is implemented as a stand-alone network function 141.
  • the control plane entity 141 i.e. MATE entity 141 is configured to: retrieve traffic information from access network nodes 120 and core network user plane nodes 130 e.g., current traffic load; retrieve Traffic Filters from access network nodes 120; retrieve Access Availability Information from core network user plane nodes 130; retrieve any Traffic related Policies from Management Plane and/or Core Network Control Plane; generate Traffic Distribution configurations for the SDT(s) 142, e.g., weights; create the SDT(s) 142 with the weights; and/or send the SDT(s) 142 to the UE 110, the (R)AN nodes 120 and the UP nodes 130.
  • control plane entity 141 i.e. MATE entity 141 is implemented as a stand-alone network function 141 in communication with a management plane, MP, entity 180 of the mobile network.
  • control plane entity 141 i.e. MATE entity 141 is implemented as a stand-alone network function 141 in communication with a management plane, MP, entity 180 of the mobile network.
  • control plane entity 141 i.e. MATE entity 141 is implemented as a stand-alone network function 141 in communication with a management plane, MP, entity 180 of the mobile network.
  • MP management plane
  • MATE entity 141 is configured to: retrieve traffic information of access network nodes 120 and core network user plane nodes 130 from the MP entity 180 ; retrieves Traffic Filters from access network nodes 120; retrieve Access Availability Information from core network user plane nodes 130; retrieve any Traffic related Policies from the MP entity 180 and/or Core Network Control Plane; generate Traffic Distribution configurations for the SDT(s) 142, e.g., weights; create the SDT(s) 142 with the weights; and/or send the SDT(s) 142 to the UE 110, the (R)AN nodes 120 and the UP nodes 130.
  • SDT(s) 142 e.g., weights
  • Figure 8 is a flow diagram illustrating a method 800 for operating the control plane entity 141 according to an embodiment for generating mapping data for establishing multi-connectivity communication for a UE 110 with a data network 170, i.e. for controlling traffic to and/or from a user equipment, UE, application on the UE 110 via one or more base stations 120 associated with one or more access networks and for each access network a plurality of data channels in the mobile network 100.
  • the method 800 comprises a step 801 of obtaining, for each of the plurality of data channels, traffic information indicative of the previous and/or current traffic via each of the plurality of data channels.
  • the method 800 comprises a step 803 of generating mapping data based on the traffic information for each of the plurality of data channels, 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 of the one or more access networks.
  • the method 800 shown in figure 8 can be performed by the control plane entity 141 according to an embodiment.
  • further features of the method 800 shown in figure 8 result directly from the functionality of the control plane entity 141 as well as the different embodiments thereof described above and below.
  • the disclosed system, apparatus, and method may be implemented in other manners.
  • the described embodiment of an apparatus is merely exemplary.
  • the unit division is merely a logical function division and may be another division in an actual implementation.
  • a plurality of units or components may be combined or integrated into another system, or some features may be ignored or not performed.
  • 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.
  • 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Est divulguée une entité de plan de contrôle (141) pour commander le trafic vers et/ou depuis une application d'équipement utilisateur (UE) sur un UE (110) par l'intermédiaire de stations de base associées à des réseaux d'accès (120) et pour chaque réseau d'accès (120), une pluralité de canaux de données dans un réseau mobile (100). L'entité de plan de contrôle (141) obtient, pour chaque canal de données de la pluralité de canaux de données, des informations de trafic indiquant un trafic précédent et/ou actuel par l'intermédiaire de chaque canal de données de la pluralité de canaux de données. De plus, l'entité de plan de contrôle (141) génère des données de mappage sur la base des informations de trafic pour chaque canal de données de la pluralité de canaux de données, les données de mappage définissant un mappage entre le trafic vers et/ou depuis l'application d'UE vers au moins un canal de données de la pluralité de canaux de données de l'au moins un réseau d'accès (120). L'entité de plan de contrôle (141) permet de mettre en œuvre une solution d'ingénierie de trafic efficace exploitant une connectivité multiple dans des réseaux mobiles.
PCT/EP2024/063549 2024-05-16 2024-05-16 Dispositifs et procédés d'ingénierie de trafic à connectivité multiple Pending WO2025237529A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/EP2024/063549 WO2025237529A1 (fr) 2024-05-16 2024-05-16 Dispositifs et procédés d'ingénierie de trafic à connectivité multiple

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2024/063549 WO2025237529A1 (fr) 2024-05-16 2024-05-16 Dispositifs et procédés d'ingénierie de trafic à connectivité multiple

Publications (1)

Publication Number Publication Date
WO2025237529A1 true WO2025237529A1 (fr) 2025-11-20

Family

ID=91186580

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2024/063549 Pending WO2025237529A1 (fr) 2024-05-16 2024-05-16 Dispositifs et procédés d'ingénierie de trafic à connectivité multiple

Country Status (1)

Country Link
WO (1) WO2025237529A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022214158A1 (fr) * 2021-04-06 2022-10-13 Lenovo (Singapore) Pte. Ltd. Sélection de qualité de flux de service pour une connexion de données à accès multiple
US20230189058A1 (en) * 2020-07-02 2023-06-15 Intel Corporation Ran-aware traffic distribution rules and ran measurements for enhanced access traffic steering switching and splitting

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20230189058A1 (en) * 2020-07-02 2023-06-15 Intel Corporation Ran-aware traffic distribution rules and ran measurements for enhanced access traffic steering switching and splitting
WO2022214158A1 (fr) * 2021-04-06 2022-10-13 Lenovo (Singapore) Pte. Ltd. Sélection de qualité de flux de service pour une connexion de données à accès multiple

Similar Documents

Publication Publication Date Title
US20250193773A1 (en) Method and device for providing service to user device by using network slice in communication system
US11057799B2 (en) Devices and methods for slice-compliant handover control
US11304060B2 (en) Network resource deployment method and device, and network resource assessment method and device
US11601849B2 (en) Method for determining background traffic transfer policy and apparatus
EP3675405B1 (fr) Procédé de sélection de mode de plan utilisateur, procédé de réglage, dispositif, équipement et support
KR20200113268A (ko) 중앙집중형 유닛-분산형 유닛 아키텍처에서의 통신 방법 및 통신 디바이스
US8355730B2 (en) Radio network controller, mobile communication system, and method for avoiding a reduction in a call connection completion ratio for use therein
CN109561450B (zh) 负载信息的交互方法及装置
WO2010121560A1 (fr) Procédé de partage de charge, dispositif et système associés
UA82114C2 (uk) Спосіб, система та пристрій для отримання послуг (варіанти) та мережа для передачі послуг
EP4140122B1 (fr) Équilibrage de charge et sélection de service dans des réseaux mobiles
WO2009048710A2 (fr) Système de communication cellulaire et son procédé de fonctionnement
US20180070350A1 (en) Methods and nodes for transferring a service identifier from a packet core network to a radio network
US20230037402A1 (en) Communication method, apparatus, and system
CN111082954A (zh) 一种网元负载均衡方法及网络设备
WO2025049329A1 (fr) Modèle flexible pour fournir des services de communication sans fil dans des zones de suivi de fonction de plan utilisateur primaire et secondaire
KR20140045887A (ko) 무선 통신시스템의 셀 부하 분산 방법 및 장치
US20250056320A1 (en) Flexible model to provision wireless communication services in overlapping user plane function tracking areas
WO2025237529A1 (fr) Dispositifs et procédés d'ingénierie de trafic à connectivité multiple
JP4737459B2 (ja) 移動通信システム、無線ネットワーク制御装置、および負荷分散方法
US12425856B2 (en) Universal unlock microservice system and method
WO2025124725A1 (fr) Dispositifs et procédés de répartition de flux de données de service pour multi-connectivité
KR20210039889A (ko) 무선 통신 시스템의 네트워크 슬라이스에서 데이터 속도 제어를 위한 방법 및 장치
US20240292263A1 (en) Apparatus, methods and computer programs supporting different quality of experience levels
US20250294433A1 (en) Network data analytics function slice load enhancement