Apparatus and method for multi-connectivity traffic data flow distribution

Abstract

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

Description

Technical Field

[0001] This disclosure relates to wireless communications. More specifically, this disclosure relates to apparatus and methods for distributing multiple service data streams (also known as QoS streams) in a multi-connectivity scenario. Background Technology

[0002] The heterogeneity of wireless access technologies (LTE, 5G New Radio (NR), 6G THz, NTN, Wi-Fi) and their communication infrastructure equipment (such as BS nodes) poses many challenges to achieving seamless communication in multi-connectivity scenarios in mobile communication networks.

[0003] The current 3GPP standard cannot unify the data channels between different access networks. During PDU session establishment, QoS flows (also referred to as Service DataFlows (SDFs) in this document) are configured and mapped to a single data channel provided by a dedicated access network node. This mapping of QoS flows to data channels remains fixed throughout the PDU session's lifecycle. Therefore, even if a data channel is available (and satisfies QoS), packets from a QoS flow cannot be distributed to two or more data channels, regardless of whether the data channels belong to the same access network node, other access nodes within the same access network, or access nodes in different access networks, and may employ different technologies. The main disadvantages of this fixed allocation include low resource utilization, limited throughput, and latency.

[0004] PCT / EP2023 / 070879 discloses a method for leveraging multiple connections in a mobile network and distributing packets from QoS flows across all available connections, thereby improving throughput and latency experienced by the UE and enhancing resource utilization in the network. However, this applies traffic steering in the radio access network without considering the application's needs. In other words, the application cannot participate in end-to-end allocation and resource usage to achieve optimal transmission of UE traffic. Furthermore, the application lacks knowledge about the UE's radio capabilities and available network connections. Summary of the Invention

[0005] One object of this disclosure is to provide improved devices and methods for distributing multiple service data streams (also known as QoS streams) in multi-connectivity scenarios, particularly for enabling applications / services to participate in end-to-end traffic steering decisions to improve the user's Quality of Experience (QoE) by taking into account, for example, application preferences or needs and network resource efficiency.

[0006] The foregoing and other objectives are achieved through the subject matter of the independent claims. Other implementations will be apparent from the dependent claims, the specification, and the drawings.

[0007] According to the first aspect, a control plane entity (also referred to herein as an application agent (AA) entity or application agent) is provided for controlling traffic destined for and / or originating from UE applications running on user equipment (UE) (also referred to herein as a mobile terminal) via one or more base stations, the one or more base stations providing one or more access networks and providing multiple available data channels (also referred to herein as Service Data Flow (SDF)) for each access network in a mobile network, particularly in a 3GPP 5G or 6G network.

[0008] The control plane entity according to the first aspect is used to acquire preference information for traffic destined for and / or originating from the UE application, wherein the preference information represents one or more preferred access networks among the one or more access networks and / or one or more preferred data channels among the plurality of data channels. Furthermore, the control plane entity is used to generate mapping data based on the preference information, particularly a plurality of traffic distribution markers, wherein the mapping data, such as the plurality of traffic distribution markers, defines a mapping between the traffic destined for and / or originating from the UE application and one or more data channels among the plurality of data channels of the one or more access networks. The control plane entity according to the first aspect enables traffic routing via the mapping data in multi-connectivity scenarios based on preference information associated with a UE application running on the UE.

[0009] In another possible implementation, the control plane entity according to the first aspect is used to: provide the mapping data, such as the plurality of traffic distribution tags, to the network functions of the core network of the mobile network to include the mapping data in a data structure, wherein the network functions are used to provide the data structure to the UE, the one or more base stations, and / or the user plane entity of the mobile network. This enables the efficient generation and distribution of data structures including the mapping data within the mobile network.

[0010] In another possible implementation, the data structure is a table. This allows for the efficient storage and access of mapped data within the data structure.

[0011] In another possible implementation, the mapping data includes multiple priority values, wherein each priority value assigns a priority to each of the multiple data channels of the one or more access networks to map traffic destined for and / or originating from the UE application to one or more of the multiple data channels of the one or more access networks. This enables efficient mapping of traffic destined for and / or originating from the UE application to one or more of the multiple data channels of the one or more access networks.

[0012] In another possible implementation, the control plane entity according to the first aspect is used to receive a UE PDU session establishment trigger indicating a UE protocol data unit (PDU) session, and to generate the mapping data for the indicated UE PDU session. This enables seamless integration within the established communication infrastructure of the mobile network.

[0013] In another possible implementation, the control plane entity according to the first aspect is used to receive the UE PDU session establishment trigger from the Access and Mobility Management Function (AMF) of the mobile network. This enables seamless integration within the established communication infrastructure of the mobile network.

[0014] In another possible implementation, the control plane entity according to the first aspect is used to: obtain the preference information from the application via an application function (AF) of the mobile network associated with the UE application. This enables seamless integration within the established communication infrastructure of the mobile network.

[0015] In another possible implementation, 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 represents the one or more access networks and the plurality of available data channels of each access network. This enables seamless integration within the established communication architecture of the mobile network.

[0016] In another possible implementation, the control plane entity is used to further generate the mapping data based on the availability information. This allows for the consideration of other information used to generate the mapping data, thereby providing better traffic mapping.

[0017] In another possible implementation, the control plane entity according to the first aspect is further configured to acquire network traffic policy information representing one or more network traffic policies implemented by the mobile network, and the control plane entity is configured to further generate the mapping data based on the network traffic policy information. This allows for the consideration of other information used to generate the mapping data, thereby providing better traffic mapping.

[0018] According to a second aspect, a network function entity for a mobile network is provided, including the control plane entity as described in the first aspect. The network function entity according to the second aspect is configured to: obtain the mapping data from the control plane entity and include the mapping data in the data structure. Furthermore, 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 the user plane entity of the mobile network. This enables the efficient implementation of the control plane entity according to the first aspect as a component of the network functions of the mobile network.

[0019] In another possible implementation, the network function entity described in the second aspect is either the Access and Mobility Management Function (AMF) entity or the Policy Control Function (PCF) entity of the mobile network. This enables seamless integration within the established communication infrastructure of the mobile network.

[0020] According to a third aspect, a method is provided for operating a control plane entity (i.e., the application proxy entity), the control plane entity being used to control traffic destined for and / or originating from a UE application running on a user equipment (UE) via one or more base stations, wherein the one or more base stations provide one or more access networks, and provide multiple available data channels, i.e., Service Data Flows (SDFs), for each access network in the mobile network. The method according to the third aspect includes the following steps:

[0021] Obtain preference information for the traffic destined for and / or originating from the UE application, wherein the preference information represents one or more preferred access networks among the one or more access networks and / or one or more preferred data channels among the plurality of data channels; and

[0022] Based on the preference information, mapping data is generated, in particular multiple traffic distribution tags, wherein the mapping data (e.g., the multiple traffic distribution tags) defines the mapping between the traffic sent to and / or from the UE application and one or more of the multiple data channels of the one or more access networks.

[0023] The method described according to the third aspect can be executed by the control plane entity described according to the first aspect. Therefore, other features of the method described according to the third aspect are directly implemented by the functionality of the control plane entity described according to the first aspect and its various implementations described above and below.

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

[0025] The accompanying drawings and the following description illustrate details of one or more embodiments. Other features, objects, and advantages are clearly shown in the specification, drawings, and claims. Attached Figure Description

[0026] The embodiments of this disclosure will be described in detail below with reference to the accompanying drawings, in which:

[0027] Figure 1 This is a schematic diagram of a mobile telecommunications system including a UE and a control plane entity according to an embodiment, wherein the control plane entity is used to generate a mapping data structure to establish multi-connection communication between the UE and the data network.

[0028] Figure 2a This is a schematic diagram illustrating the operation of a control plane entity and its interaction with other network entities of the mobile network according to one embodiment, used in a scenario where a PDU session establishment request is initiated by the UE.

[0029] Figure 2b This is a schematic diagram illustrating the operation of a control plane entity and its interaction with other network entities of the mobile network according to one embodiment, for a scenario where the UE network connection has changed.

[0030] Figure 2c This is a schematic diagram illustrating the operation of a control plane entity and its interaction with other network entities in a mobile network according to one embodiment, for scenarios where the operating conditions of the application server have changed.

[0031] Figure 3 It is a signaling diagram of the operation of a control plane entity and its interaction with other network entities of the mobile network according to an embodiment, for scenarios where the control plane entity is implemented as a component of the AMF.

[0032] Figure 4 It is a signaling diagram of the operation of a control plane entity and its interaction with other network entities of the mobile network according to an embodiment, for a scenario where the control plane entity is implemented as a component of a PCF.

[0033] Figure 5a This is a schematic diagram of the architecture of a mobile telecommunications system including a control plane entity according to an embodiment, wherein the control plane entity is implemented as a component of the AMF;

[0034] Figure 5b This is a schematic diagram of the architecture of a mobile telecommunications system including a control plane entity according to an embodiment, wherein the control plane entity is implemented as a component of the PCF; and

[0035] Figure 6 This is a flowchart of a method for running a control plane entity according to one embodiment, the control plane entity being used to generate a mapping data structure to establish multi-connection communication.

[0036] In the following text, the same reference numerals refer to the same or at least functionally equivalent features. Detailed Implementation

[0037] In the following description, reference is made to the accompanying drawings, which form part of this disclosure, illustrating by way of description specific aspects of embodiments of this disclosure or aspects that may be used with respect to embodiments of this disclosure. It should be understood that embodiments of this disclosure may be used in other aspects and may include structural or logical variations not depicted in the drawings. Therefore, the following detailed description should not be construed in a limiting sense, and the scope of this disclosure is defined by the appended claims.

[0038] For example, it should be understood that the disclosure relating to the described method is also applicable to the corresponding device or system used with that method, and vice versa. For instance, if one or more specific method steps are described, the corresponding device may include one or more units, such as functional units, to perform the described one or more method steps (e.g., one unit performs one or more steps, or multiple units perform one or more of a plurality of steps respectively), even if such one or more units are not explicitly described or shown in the drawings. Furthermore, if a specific apparatus is described based on one or more units (e.g., functional units), the corresponding method may include a step to perform the function of one or more units (e.g., one step performs the function of one or more units, or multiple steps perform the function of one or more of a plurality of units respectively), even if such one or more steps are not explicitly described or shown in the drawings. Moreover, it should be understood that, unless otherwise expressly stated, features of the various exemplary embodiments and / or aspects described herein can be combined with each other.

[0039] Before describing detailed embodiments for establishing multi-connection communication in a mobile network, the following abbreviations are defined:

[0040] 3rd Generation Partnership Project (3GPP)

[0041] Access and Mobility Management Function (AMF)

[0042] Access Network (AN)

[0043] Access Traffic Steering, Switching & Splitting (ATSSS)

[0044] Artificial Reality (AR)

[0045] Base Station (BS)

[0046] Buffering Action Rule (BAR)

[0047] Control Plane (CP)

[0048] Core Network (CN)

[0049] Data Network (DN)

[0050] Downlink (DL)

[0051] Dual Connectivity DC

[0052] Edge Application Server (EAS)

[0053] Enhanced Mobile Broadband (eMBB)

[0054] Forwarding Action Rule (FAR)

[0055] Geostationary Earth Orbit (GEO)

[0056] Guaranteed Bit Rate (GBR)

[0057] High Altitude Platform Station (HAPS)

[0058] Internet Protocol version 6 (IPv4)

[0059] Internet Protocol version 6 (IPv6)

[0060] Long-Term Evolution (LTE)

[0061] Low Earth Orbit (LEO)

[0062] Massive Machine Type Communication (mMTC)

[0063] Master Cell Group (MCG)

[0064] Master Node (MN)

[0065] Media Access Control (MAC)

[0066] Mobile Network Operator (MNO)

[0067] Multi-Access MA

[0068] Multi Connectivity MC

[0069] Multipath Transmission Control Protocol (MPTCP)

[0070] Multi-Radio Dual Connectivity MR-DC

[0071] Network Data Analytics Function (NWDAF)

[0072] Network Exposure Function (NEF)

[0073] Network Function (NF)

[0074] New Radio (NR)

[0075] Next Generation Application Protocol (NG-AP)

[0076] Non-Access Stratum NAS

[0077] Non-Terrestrial Network (NTN)

[0078] Operating System (OS)

[0079] Packet Detection Rule (PDR)

[0080] Packet Forwarding Control Protocol (PFCP)

[0081] PDU Session Anchor (PSA)

[0082] Physical Layer (PHY)

[0083] Policy and Charging Control (PCC)

[0084] Policy Control Function (PCF)

[0085] Protocol Data Convergence Protocol (PDCP)

[0086] Protocol Data Unit (PDU)

[0087] Quality of Service (QoS)

[0088] Quality of Service Enforcement Rule (QER)

[0089] Quality of Service Flow Identifier (QFI / QI)

[0090] Radio Access Network (RAN)

[0091] Radio Link Control (RLC)

[0092] Radio Resource Control (RRC)

[0093] Reinforcement Learning (RL)

[0094] Secondary Cell Group (SCG)

[0095] Secondary Node (SN)

[0096] Service-Based Architecture (SBA)

[0097] Service Based Interface (SBI)

[0098] Service Data Adaptation Protocol (SDAP)

[0099] Service Data Flow (SDF)

[0100] Service Data Flow Distribution Manager (SDM)

[0101] Service data flow distribution table (SDT)

[0102] Session Management Function (SMF)

[0103] Single Network Slice Selection Assistance Information (S-NSSAI)

[0104] State of the Art (SoTA)

[0105] Terrestrial Network (TN)

[0106] Timing Advance (TA)

[0107] Traffic Flow Template (TFT)

[0108] Ultra-Reliable Low Latency Communications (uRLLC)

[0109] Unified Data Management (UDM)

[0110] Uplink UL

[0111] Uplink Classifier (UL CL)

[0112] Usage Reporting Rule (URR)

[0113] User Equipment (UE)

[0114] User Plane UP

[0115] User Plane Function (UPF)

[0116] Virtual Reality (VR)

[0117] Wireless Fidelity Wi-Fi

[0118] Figure 1This is a schematic diagram of a mobile telecommunications system 100, which includes at least one user equipment (UE) 110 according to one embodiment, at least one base station 120 according to one embodiment, and a network entity 130 (e.g., in the form of a UPF 130) according to one embodiment. In one embodiment, the mobile telecommunications system 100 is a 3rd Generation Partnership Project (3GPP) mobile telecommunications system 100. As will be described in more detail below, the UE 110, base station 120, and network entity 130 are used to: establish multi-connection communication between the UE 110 and endpoint application 191 via a data network 190 (e.g., the Internet 190) using a mapping data structure 152, in particular a mapping table 152 (also referred to herein as a Service data flow Distribution Table (SDT) 152).

[0119] As will be described in more detail below, the mapping data for mapping table 152 is generated by control plane entity 150 (also referred to herein as Application Agent (AA) 150), such as Figure 1 As shown, this control plane entity can be implemented as a component of control plane function 140. Typically, control plane entity 150 (i.e., AA 150) supports extending the needs of applications and service providers to the access network of mobile network 100, enabling applications / service providers to extend their needs end-to-end (because application needs are already considered in the mobile core network). More specifically, control plane entity 150, i.e., AA 150, is used to acquire information sent to and / or from UE 110 (in... Figure 1 The traffic preference information of a UE application running on a mobile terminal (MT) 110, wherein the preference information represents one or more preferred access networks and / or multiple data channels of one or more access networks 120 of the mobile network 100. to One or more preferred data channels in the network. Furthermore, as will be described in more detail below, control plane entity 150, i.e., AA 150, is used to generate mapping data based on preference information, specifically multiple traffic distribution markers, wherein the mapping data, such as the multiple traffic distribution markers, defines traffic destined for and / or originating from UE applications and multiple data channels of one or more access networks 120. to Mapping between one or more data channels in the system.

[0120] As described above and as Figure 1As shown, according to the embodiments disclosed herein, control plane entity 150, i.e., AA function 150, can be implemented as a component of a suitable CP function 140 in the core network of mobile network 100. Figure 1 In the illustrated embodiment, AA 150 receives a PDU session establishment / modification trigger from MT 110, i.e., UE 110 (via access management function (AMF) 160 in the core network), requests an available connection from MT 110 (from AMF 160), and forwards this information to AF 170. Application 191 can run on an application server connected to data network 190. Application 191 can pre-configure its preferences, i.e., access network connection preferences, in AF 170, or AF 170 can request application 191 to provide its preferences, i.e., preference information, when AF 170 receives a trigger from AA 150. Furthermore, application 191 can dynamically adjust its preferences during an ongoing PDU session based on the conditions / state of its endpoint, i.e., UE 110 and / or application server. In addition, whenever any changes occur to the MT's connectivity, for example when the MT 110 connects to a new access network node, the AA 150 can send the trigger and the MT110's currently available connectivity to the AF 170 for use in an ongoing PDU session.

[0121] like Figure 1 As shown, AF 170 can use its preference response to AA 150, which is the network connection preference information of UE 110 (i.e., MT110) during the PDU session. Preferences, i.e., the preference information of Application 191 for the preferred access network, can be based on various different criteria, such as improving the user's QoE, load balancing, and energy-related considerations, such as prioritizing access networks using green energy. Figure 1As further shown, AA 150 converts the preference, i.e., the preference information of application 190, into multiple traffic distribution tags, i.e., mapping data. In one embodiment, the multiple traffic distribution tags may include multiple priorities of data structure 152, preferably in the form of table 152, referred to as Service data flow distribution table (SDT) 152. CP entity 140 uses these traffic distribution tags to generate one or more SDTs 152 for UE 110, one or more RAN nodes 120, and one or more UP nodes 130, and sends one or more SDTs 152 to MT 110, one or more RAN nodes 120, and one or more UP nodes 130. Once a PDU session is established and MT 110 has received the SDT 152, it distributes UL traffic on available connections using the traffic distribution tags in SDT 152, for example, in the manner described in PCT / EP2023 / 070879. Similarly, one or more RAN nodes 120 and UP nodes 130 may, for example, distribute downlink (DL) packets to MT 110 on available connections and data channels based on traffic distribution markings in the SDT, in a manner described in PCT / EP2023 / 070879.

[0122] As described above, MT 110, one or more RAN nodes 120, and UP node 130 can be configured as described in PCT / EP2023 / 070879 (entirely incorporated herein by reference) for distributing traffic based on SDT 152. More specifically, SDT 152 can be used in the protocol stack (Layer 2 or higher) of UE 110 and UP 130 to capture SDF / QoS / traffic profiles (e.g., mmtc, uRLLC, etc.) mapped to (e.g., provided by the operator) available networks and their corresponding data channels. The Service data flow Distribution Manager (SDM) can be implemented as SDM-UE in UE 110 and as SDM-UP (Layer 2 or higher) in UP 130 to map packets from each SDF / QoS flow to one or more available networks and their corresponding data channels by querying SDT 152.

[0123] The SDM-UE can reside in Layer 2 of the 3GPP 5G (and above) protocol stack, between the IP layers and above the SDAP sublayer. The SDM-UE can use a QoS Identifier (QI) to query SDT 152 and receive a list of Access Networks (ANs) and their corresponding data channels in response. The SDM can select an AN and its corresponding data channel and forward packets to the corresponding SDAP entity in the next sublayer. Multiple SDAP entities may exist in the SDAP layer, with one SDAP entity for each connected network (currently the 3GPP standard for 5G, as of version 18). SDAP can forward packets to the selected AN through the selected data channel.

[0124] The SDM-UP can reside at a Layer 2 sublayer, above the IP layer, the MAC / Ethernet sublayer, and the SDAP sublayer in the core UP of the 3GPP 5G (and above) protocol stack. The UPF 130 and RAN base station (BS) 120 receive SDT 152 from the core network. For example, the UPF can receive SDT 152 from the SMF via N4 signaling during PDU session establishment. The UPF 130 can maintain multiple N3 tunnels with each AN node 120 available for the PDU session (either notified by the SMF or derived from SDT 152). The UPF 130 can receive QoS tags (QIs) from the SMF, and the SDM-UP in the UPF 130 can use the QI to query SDT 152 and select AN 120 to send data packets. The RAN 120 receives the data packet, queries SDT 152 using the QI tag in the SDM-UP within the RAN, and receives the data channel for forwarding the data packet to UE 110. RAN 120 forwards data packets to UE 110 through the selected data channel.

[0125] exist Figure 2a In the illustrated embodiment, control plane entity 150, i.e., AA function 150, is implemented as a component of appropriate CP function 140 in the mobile core network for scenarios where UE 110, i.e., MT 110, initiates a PDU session establishment request. When a user of UE 110 wishes to use an application through mobile network 100, UE 110, i.e., MT 110, requests the mobile network control plane to establish a PDU session for UE 110. Figure 2a Step 1 in the process). PDU session establishment trigger is sent to session management function 161, such as SMF 161, via CP access management function 160, e.g., AMF 160. Figure 2a In steps 2 and 5), the session management function 161 establishes a PDU session for the MT 110 based on the mobile network provider's policy. Figure 2a (Steps 9.2 and 10 in the original text). The CP Access Management function 160 also requests the radio capabilities of the MT and authorizes connections for the MT 110. Based on available connections, the CP Access Manager 160 obtains a traffic profile (mapped to the Service Data Flow (SDF) of the radio resources) for each connection (assigned by the RAN 120). Figure 2a Step 11.2) and the traffic measurement report of the corresponding wireless access node connected to the MT 110 ( Figure 2a Step 12.2 in the document). According to one embodiment, the CP access manager 160 triggers the PDU session establishment ( Figure 2a Step 3), available connections for MT110 ( Figure 2a Step 6.2 in the text), the traffic profile available for each connection on the MT 110 ( Figure 2a Step 11.3) and traffic strategy ( Figure 2a Step 9.3) is forwarded to control plane entity 150, such as AA 150. Control plane entity 150, such as AA 150, also triggers the PDU session establishment ( Figure 2a Step 4.2 in the above) and the available connection of MT 110 ( Figure 2a (Step 7) Forward to AF 170.

[0126] Endpoint application 191 can pre-configure its preferences for the access network connection / resources to be used by the user in AF 170, or AF 170 can request application 191 to provide its preferences when AF 170 receives a PDU session establishment trigger from control plane entity 150, such as AA 150. Figure 2a After step 4.2), AF 170 replies to AA 150 with its preference for the network connection to be used by MT 110 during the PDU session. Figure 2a (Step 8 in the process). An application's preference for a preferred access network (and / or its resources) can be based on a variety of different criteria, such as improving the user's QoE, load balancing, energy-related considerations, such as prioritizing access networks that use green energy.

[0127] Control plane entity 150, such as AA 150, translates these applied preferences into traffic distribution tags in SDT152, such as priority, based on the operator's policies. Figure 2a Steps 9.1, 9.2, 9.3, and 13 in the above. An exemplary algorithm for generating traffic distribution tags will be further described below. CP function 140 uses these traffic distribution tags (along with other information such as traffic measurement reports from RAT nodes) Figure 2aSteps 12.2 and 13 in the process create one or more SDTs 152 for MT 110, one or more RAN nodes 120 and UP 130, and send one or more SDTs 152 to MT 110, one or more RAN nodes and one or more UP nodes. Figure 2a (Step 15 in the original text). Once the PDU session is established and MT 110 has received SDT 152, it will distribute UL traffic on available connections using the traffic distribution marker in SDT 152. Similarly, one or more RAN nodes 120 and UP nodes 130, based on the traffic distribution marker in SDT 152, distribute UL traffic on available connections and data channels. to The downlink (DL) data packets are distributed to MT 110, i.e. UE 110.

[0128] exist Figure 2b In the illustrated embodiment, control plane entity 150, such as AA function 150, is implemented as a component of appropriate CP function 140 in the mobile core network for scenarios where the access network connectivity of MT 110 changes, for example, when MT 110 connects to a new access network due to its mobility. Figure 2b Step 1 in the process. When a user of MT 110 wishes to use application 191 via mobile network 100, MT 110 requests the mobile network control plane to establish a PDU session for the MT. The PDU session establishment trigger is sent via CP access management function 160, such as AMF 160, to session management function 161, such as SMF 161, which establishes a PDU session for MT 110 based on the mobile network provider's policy. Once the PDU session is established, any changes to the session are executed by generating a PDU session modification trigger. Figure 2b Steps 1 and 2 in the process). The PDU session modification trigger can be generated by any authorized participating entity during an ongoing PDU session, for example, by MT 110 and SMF 161. When the mobile network core CP receives a PDU session establishment or modification trigger, the CP access management function 160, such as AMF 160, also requests the radio capabilities of the MT and authorizes a connection for the MT 110 ( Figure 2b Step 1 in the process). Based on available connections ( Figure 2b In steps 5 and 6.2), the CP Access Manager 160, such as the AMF 160, obtains a traffic profile (mapped to the Service Data Flow (SDF) of the radio resource) for each connection (assigned by the RAN). Figure 2bStep 11.2) and the traffic measurement report of the corresponding wireless access node connected to MT 110. According to one embodiment, CP access manager 160, such as AMF 160, triggers PDU session establishment / modification, and the available connections of MT 110 ( Figure 2b Step 3 in the process), the traffic profile available for each connection on the MT 110 ( Figure 2b Step 11.2) and the traffic policy are forwarded to control plane entity 150, such as AA 150 ( Figure 2b (Steps 9.2 and 9.3 in the original text). In response, control plane entity 150, such as AA 150, also forwards the PDU session establishment / modification trigger and the available connection of MT 110 to AF 170 ( Figure 2b (Steps 4.2 and 7 in the text).

[0129] Endpoint application 191 can pre-configure its considerations in AF 170, namely its preferences for access network connections / resources to be used by the user of MT 110, or when AF 170 receives a PDU session establishment / modification trigger from control plane entity 150, such as AA 150, AF 170 can request application 191 to provide its preferences. Furthermore, whenever there is any change in the connection of MT 110, i.e., UE 110, for example when UE 110 connects to a new access network node, control plane entity 150, such as AA 150, can send a PDU session modification trigger along with the currently available connections of UE 110 to AF 170 for use in ongoing PDU sessions. Figure 2b Steps 4.2 and 7 in the table). After receiving a PDU session establishment / modification trigger from control plane entity 150, i.e., AA 150, AF170 replies to control plane entity 150, i.e., AA 150, with one or more preferences for the network connections to be used by MT 110 during the PDU session. Figure 2b (Step 8 in the process). One or more applications 191 may have a preference for a preferred access network (and / or its resources) based on a variety of different criteria, such as improving the user's QoE, load balancing, energy-related considerations, such as prioritizing access networks that use green energy.

[0130] Control plane entity 150, or AA 150, based on operator policies, translates one or more preferences of one or more applications 190 into traffic distribution tags that define priorities in SDT 152. Figure 2bSteps 3.1, 4.1, 6.1, 7, 8, 9.1, 11.1, 12.1, and 13 in the above steps. An exemplary algorithm for generating traffic distribution tags according to one embodiment will be further described below. The CP uses these traffic distribution tags (along with other information such as traffic measurement reports from RAT nodes) to create one or more SDT152s for MT 110, one or more RAN 120s, and UP 130, and sends them to MT 110, one or more RAN nodes 120, and one or more UP nodes 130 (…). Figure 2b (Step 15 in the process). Once the PDU session is established / modified and MT 110 has received the updated SDT 152, it will use the traffic distribution markers in SDT 152, i.e., the priority, to distribute UL traffic on available connections. Similarly, one or more RAN nodes 120 and UP nodes 130, based on the traffic distribution markers in SDT 152, distribute UL traffic on available connections and data channels. to The downlink (DL) data packets are distributed to UE 110, i.e., MT 110.

[0131] exist Figure 2c In the illustrated embodiment, control plane entity 150, i.e., AA function 150, is implemented as a component of appropriate CP function 140 in the mobile core network for scenarios where the operating conditions of the application endpoint server change. For example, the load on application server 191 is high, and therefore the application wants MT 110 not to generate high UL traffic using the high-speed network to avoid overloading the server (see...). Figure 2c Step 1 in the process. When the user of MT 110, i.e., UE 110, wishes to use application 191 through mobile network 100, MT 110 requests the mobile network control plane to establish a PDU session for MT 110. The PDU session establishment trigger is sent to session management function 161, such as SMF 161, through CP access management function 160, such as AMF 160, which establishes a PDU session for MT 110 based on the mobile network provider's policy. Once the PDU session is established, any changes to the session can be executed by generating a PDU session modification trigger. Figure 2c(Step 2 in the process). The PDU session modification trigger can be generated by any authorized participating entity during an ongoing PDU session, for example, by MT 110 and SMF 161. When the mobile network core CP receives a PDU session establishment or modification trigger, the CP access management function 160, such as AMF 160, also requests the radio capabilities of the MT and authorizes a connection for the MT 110. Based on the available connections, the CP access manager 160, such as AMF 160, obtains a traffic profile (mapped to the Service DataFlow (SDF) of the radio resources) and a traffic measurement report of the corresponding radio access node to which the MT 110 is connected for each connection (assigned by one or more RAN 120s). Figure 2c Step 11.2 in the document). According to one embodiment, the CP access manager 160, such as AMF 160, forwards the PDU session establishment / modification trigger, the available connections of MT 110, the traffic profiles for each available connection of MT 110, and the traffic policies to the control plane entity 150, namely AA 150. Figure 2c (Steps 3, 6.2, 11.3, and 9.3 in the original text). Additionally, control plane entity 150, i.e., AA 150, forwards the PDU session establishment / modification trigger and the available connection of MT 110 to AF 170 (…). Figure 2c (Steps 4.2 and 7 in the text).

[0132] Endpoint application 191 can pre-configure its considerations, i.e., preferences for the access network connection / resources to be used by the user, in AF 170, or when AF 170 receives a PDU session establishment / modification trigger from control plane entity 150, i.e., AA 150, AF 170 can request application 191 to provide one or more of its preferences. Furthermore, application 191 can also dynamically adjust its considerations, i.e., preferences during the ongoing PDU session, based on the conditions / state of its endpoint, i.e., the application server and / or MT 110. Figure 2c Step 1 in the process. Whenever a change occurs on the application side, application 191 can notify AF 170 to update one or more of its preferences accordingly. Figure 2c (Step 1 in the process). These considerations, namely the preferences of one or more applications 191 for preferred access networks (and / or their resources), can be based on a variety of different criteria, such as improving the user's QoE, load balancing, energy-related considerations, such as prioritizing access networks that use green energy.

[0133] When AF 170 receives an indication from endpoint application 191 regarding any changes to one or more preferences for the ongoing PDU session, AF 170 requests the currently available connection of MT 110 from control plane entity 150, i.e., AA 150, and requests control plane entity 150, i.e., AA 150, to update the ongoing PDU session with the updated one or more preferences from application 191. Figure 2c Steps 7 and 8 in the process). Upon receiving an update from AF 170, control plane entity 150, i.e. AA150, based on the operator's policy, converts one or more preferences of one or more applications 190 into traffic distribution tags that define priorities in SDT 152 ( Figure 2c Step 13 in the document. An exemplary algorithm for generating traffic distribution tags, i.e., priorities, will be described below. CP entity 140 uses these traffic distribution tags (along with other information such as traffic measurement reports from RAT node 120) to update SDT 152 for MT 110, one or more RAN nodes 120, and UP 130, and sends them to MT 110, one or more RAN nodes 120, and one or more UP nodes 130, respectively. Figure 2c (Step 15 in the original text). Once MT 110 has received the updated SDT 152, it distributes UL traffic on available connections using the traffic distribution markers in SDT 152. Similarly, one or more RAN nodes 120 and UP nodes 130 distribute UL traffic on available connections and data channels based on the traffic distribution markers in SDT 152. to The downlink (DL) data packets are distributed to MT 110, i.e. UE 110.

[0134] Figure 3 A signaling diagram illustrating the message sequence exchanged between participating entities in one embodiment is shown, wherein control plane entity 150, or AA 150, is implemented as a component of AMF 160 in the mobile core network control plane, for an exemplary scenario where MT 110 requests CP to establish a PDU session. When MT 110 sends a PDU session establishment trigger, RAT access node 120 forwards the request to AMF 160 (…). Figure 3 Step 301 in the process). AMF 160 forwards the request to SMF 161 ( Figure 3 Step 303 in the process), and forwards it to AA 150 within AMF 160. AA 150 forwards the PDU session establishment trigger to AF 170 ( Figure 3 Step 305 in the process). AMF160 receives a traffic management report from the RAT node 120 it is managing ( Figure 3Step 307 in the process generates an available connection for each MT 110 and forwards this information to AA 150 ( Figure 3 In step 309), the AA 150 then forwards the available connection information to the AF 170 ( Figure 3 Step 311 in the process). In response, AF 170 sends the application's preference for MT 110 to AA 150 for the current / ongoing / pending PDU session ( Figure 3 Step 313 in the process). AMF 160 sends the traffic measurement report of the RAT node serving MT 110, along with the traffic policy, to the network function / module 140 that generates SDT 152 ( Figure 3 Step 315 in the process). In this embodiment, module 140, which generates SDT 152, is implemented together with AA 150 as a component of AMF 160. AMF 160 retrieves the traffic policy and traffic profile of MT 110, i.e., UE 110, for available connections. Figure 3 In step 319), AA 150 generates a traffic distribution tag based on this information and the preferences received from AF 170. Figure 3 Step 325 in the process. AA150 sends a traffic distribution tag to network function / module 140, which generates SDT 152. Network function / module 140 then combines this information with a traffic measurement report and a traffic profile to generate SDT 152. Figure 3 Steps 321, 323, and 327 in the process. Once SDT 152 is generated, it is forwarded accordingly to MT 110, Radio Access Node 120, and User Plane Node 130, such as UPF 130 ( Figure 3 Steps 329, 331, 333, 335, and 337 in the process.

[0135] Figure 4 A signaling diagram illustrating the message sequence exchanged between participating entities for another embodiment is shown, wherein control plane entity 150, or AA 150, is implemented as a component of PCF 162 in the mobile core network control plane, for an exemplary scenario where MT 110 requests CP to establish a PDU session. When MT 110 sends a PDU session establishment trigger, RAT access node 120 forwards the request to AMF 160 (…). Figure 4 Step 401 in the process). AMF 160 also forwards the request to SMF 161, and to AA 150 (implemented as PCF 162). Figure 4 Steps 403 and 405 in the process). AA 150 forwards the PDU session establishment trigger to AF170 ( Figure 4Step 409 in the process). AMF 160 receives a traffic management report from the RAT node 120 it is managing ( Figure 4 In step 407), an available connection is generated for each MT 110, and this information is forwarded to AA 150 within PCF 162. Figure 4 In step 411), the AA 150 then forwards it to the AF 170 ( Figure 4 Step 413 in the process). In response, AF 170 sends the application preference for MT110 to AA 150 for the current / ongoing / pending PDU session ( Figure 4 Step 415 in the process. AA150 receives the traffic policy from PCF 162 ( Figure 4 Step 417), and sends a preferred connection to PCF 162, which then forwards the traffic policy used for the preferred connection to AMF 160 ( Figure 4 Step 419 in the process). AMF 160 responds by sending a traffic measurement report from RAT node 120, which provides preferred connectivity to MT 110, to network function / module 140, which generates SDT 152 within PCF 162. Figure 4 Step 423 in the process). AMF 160 also retrieves traffic profiles from these RAT nodes 120 for MT 110 ( Figure 4 Step 421 in the process), and forward the traffic profile to the network function / module 140 that generates SDT 152 within PCF 162 ( Figure 4 Step 423 in the middle). Figure 4 In the illustrated embodiment, module 140 for generating SDT 152 is implemented together with AA 150 as a component of PCF 162. AA 150 generates a traffic distribution tag based on this information and preferences received from AF 170. Figure 4 Step 427 in the process. AA 150 sends a traffic distribution tag to network function / module 140, which generates SDT 152. Network function / module 140 then combines this information with a traffic measurement report and a traffic profile to generate SDT 152. Figure 4 Steps 424, 425, and 429 in the process. Once SDT 152 is generated, it is forwarded accordingly to MT 110, Radio Access Node 120, and User Plane Node 130, such as UPF 130 (…). Figure 4 Steps 431, 433, 435, 437, and 439 in the process.

[0136] An exemplary algorithm, which can be implemented by a control plane entity 150, or AA 150, according to one embodiment, is described below for generating traffic distribution tags, or priorities, for SDT 152.

[0137] For a given state ,in:

[0138] =The set of all networks connected to the MT 110 .

[0139] =The set of all 120 RAT nodes in X networks .

[0140] =The set of all traffic strategies for R nodes (120) in X networks. .

[0141] =The set of all preferred networks ,in, .

[0142] =The set of total allowed traffic on RAT node 120 based on measurement reports .

[0143] =The set of all traffic strategies for R nodes in A networks .

[0144] =The set of all data channels provided by R nodes in A networks .

[0145] ,in, and .

[0146] from Get from ,in, , and .

[0147] Get from ,in, and .

[0148] from and Get from ,in .

[0149] Generate P, where ,in , , and .

[0150] In the algorithm described above, AA 150 retrieves information about the network to which MT 110 is connected and the corresponding RAT node 120 and its traffic policies. Based on this, AA 150 then retrieves preferred networks from application 191 via AF 170. AA 150 then retrieves the measurement reports of RAT node 120 from the preferred networks, their traffic profiles, and their policies. Based on the received information, AA 150 generates priorities for the access network resources provided by RAT node 120, that is, assigns priorities to the data channels provided by RAT node. AA 150 forwards these priorities (traffic distribution tags) to the corresponding CP features responsible for creating / updating and managing SDTs. The CP features create / update SDTs with traffic distribution tags (priorities) received from AA 150 based on the measurement reports of RAT node 120, network policies, and other factors, and forward them accordingly to MT 110, radio access node 120, and user plane node 130, such as UPF 130.

[0151] Figure 5a The architecture of a mobile network 100 including a control plane entity 150, i.e., AA 150, according to one embodiment is shown. This architecture adopts a 3GPP system 100, such as a 5G or 6G system 100. As can be understood, Figure 5a The main differences between the 3GPP system 100 shown in this embodiment and the traditional 3GPP system are as follows. Figure 5a The illustrated embodiment of the 3GPP system 100 includes a control plane entity 150, namely AA 150. As described above, this control plane entity 150 can be implemented as a control plane network function, such as a component of AMF 160. Figure 5aIn the embodiment of the 3GPP system 100 shown, AA 150 receives PDU session establishment / modification triggers, available connections of MT 110, and traffic profiles from AMF 160, traffic policies from PCF 162, and application 191's preferences for available connections from AF 170, as described in detail above. Based on the application's preferences, traffic policies, and available connections, AA 150 generates traffic distribution tags, i.e., priorities, and sends them to the network function / module 140 that generates SDT 152. Based on the traffic distribution tags, traffic measurement reports, traffic profiles, and network policies, the responsible network function / module 140 generates SDT 152 and forwards them to MT 110, RAT node 120, and one or more UP nodes 130, such as UPF 130. As can be understood, Figure 5a The illustrated embodiment of the 3GPP system 100 may include other entities and / or interfaces of a conventional 3GPP system, such as Figure 5a As shown, these are NRF 163, NWDAF 164, NEF 165 and / or UDM 166, which have the corresponding interfaces.

[0152] Figure 5b An architecture of a mobile network 100 including a control plane entity 150, namely AA 150, according to another embodiment is shown. This architecture adopts the form of a 3GPP system 100, such as a 5G or 6G system 100. As can be understood, Figure 5b The main differences between the 3GPP system 100 shown in this embodiment and the traditional 3GPP system are as follows. Figure 5b The illustrated embodiment of the 3GPP system 100 includes a control plane entity 150, namely AA 150. As described above, this control plane entity 150 can be implemented as a component of a control plane network function, such as PCF 162. AA 150 receives PDU session establishment / modification triggers, available connections of MT 110, and traffic profiles from AMF 160, traffic policies from PCF 162, and application 191's preferences for available connections from AF 170. Based on the application's preferences, traffic policies, and available connections, AA 150 generates traffic distribution tags, i.e., priorities, and sends them to the network function / module 140 that generates SDT 152, as described in detail above. Based on the traffic distribution tags, i.e., priorities, traffic measurement reports, traffic profiles, and network policies, the responsible network function / module 140 generates SDT 152 and forwards them to MT 110, RAT node 120, and one or more UP nodes 130, such as UPF 130. As will be understood, the embodiment of the 3GPP system 100 shown in Figure 55 may include other entities and / or interfaces of conventional 3GPP systems, such as Figure 5bAs shown, these are NRF 163, NWDAF 164, NEF 165 and / or UDM 166, which have the corresponding interfaces.

[0153] Figure 6 A flowchart illustrating the steps of a method 600 for operating a control plane entity 150, which controls traffic destined for and / or originating from user equipment (UE) applications on a user equipment (UE) 110 via one or more base stations, wherein the one or more base stations provide one or more access networks 120, and provide multiple data channels for each access network in the mobile network 100. to Method 600 includes step 601: obtaining preference information for traffic destined for and / or originating from a UE application, wherein the preference information represents one or more preferred access networks and / or multiple data channels in one or more access networks 120. to One or more preferred data channels in the network. Furthermore, method 600 includes step 603: generating mapping data based on preference information, wherein the mapping data defines traffic destined for and / or originating from a UE application and multiple data channels of one or more access networks 120. to Mapping between one or more data channels in the system.

[0154] Method 600 can be performed by control surface entity 150 according to one embodiment. Therefore, other features of method 600 come directly from the functionality of control surface entity 150 and its various embodiments described above and below.

[0155] Those skilled in the art will understand that the “blocks” (“units”) in the various drawings (methods and apparatuses) represent or describe the functionality of embodiments of this disclosure (and are not necessarily separate “units” in hardware or software), and thus equally describe the functionality or features (units equivalent to steps) of apparatus embodiments and method embodiments.

[0156] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the described apparatus embodiments are merely exemplary. For example, the unit division is only a logical functional division, and other division methods may be used in actual implementation. For example, multiple units or components may be merged or integrated into another system, or some features may be ignored or not performed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed can be implemented through some interfaces. Indirect coupling or communication connection between devices or units can be implemented electronically, mechanically, or otherwise.

[0157] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of the embodiment solution according to actual needs.

[0158] Furthermore, the functional units in the embodiments of this disclosure can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

Claims

1. A control surface entity (150), characterized in that, For controlling traffic sent to and / or from user equipment (UE) applications (110) via one or more base stations, wherein the one or more base stations provide one or more access networks (120), and provide multiple data channels for each access network in the mobile network (100). to The control surface entity (150) is used for: Obtain preference information for the traffic destined for and / or originating from the UE application, wherein the preference information represents one or more preferred access networks among the one or more access networks (120) and / or the plurality of data channels ( to One or more preferred data channels in ) and Mapping data is generated based on the preference information, wherein the mapping data defines the traffic destined for and / or originating from the UE application and the plurality of data channels of the one or more access networks (120). to Mapping between one or more data channels in ().

2. The control surface entity (150) according to claim 1, characterized in that, The control plane entity (150) is used to: provide the mapping data to the network functions (140, 160, 162) of the mobile network (100) to include the mapping data in a data structure (152), wherein the network functions (140, 160, 162) are used to provide the data structure (152) to the UE (110), the one or more base stations and / or the user plane entity (130) of the mobile network (100).

3. The control surface entity (150) according to claim 2, characterized in that, The data structure (152) is table (152).

4. The control surface entity (150) according to any one of the preceding claims, characterized in that, The mapping data includes multiple priority values, wherein each priority value is the multiple data channels (DC1 to DC2) of the one or more access networks (120). Each data channel in the network is prioritized to map the traffic destined for and / or originating from the UE application to the plurality of data channels of the one or more access networks (120). to One or more data channels in ).

5. The control surface entity (150) according to any one of the preceding claims, characterized in that, The control plane entity (150) is used to receive a UE PDU session establishment trigger that indicates a UE Protocol Data Unit (PDU) session, and to generate the mapping data for the UE PDU session.

6. The control surface entity (150) according to claim 5, characterized in that, The control plane entity (150) is used to receive the UE PDU session establishment trigger from the Access and Mobility Management Function (AMF) (160) of the mobile network (100).

7. The control surface entity (150) according to any one of the preceding claims, characterized in that, The control plane entity (150) is used to: obtain the preference information from the application (191) through the application function AF (170) of the mobile network (100) associated with the UE application.

8. The control surface entity (150) according to claim 6, characterized in that, The control plane entity (150) is configured to: in response to forwarding availability information to the AF (170) associated with the UE application, obtain the preference information from the AF (170) associated with the UE application, wherein the availability information represents the one or more access networks (120) and the plurality of data channels of each access network (…). to ).

9. The control surface entity (150) according to claim 8, characterized in that, The control plane entity (150) is used to further generate the mapping data based on the availability information.

10. The control surface entity (150) according to any one of the preceding claims, characterized in that, The control plane entity (150) is also used to obtain network traffic policy information representing one or more network traffic policies implemented by the mobile network (100), and the control plane entity (150) is used to further generate the mapping data based on the network traffic policy information.

11. A network function entity (140, 160, 161) of a mobile network (100), characterized in that, Includes a control plane entity (150) according to any one of the preceding claims, wherein the network function entities (140, 160, 161) are used for: The mapping data is obtained from the control surface entity (150); The mapping data is included in data structure (152); and The data structure (152) is provided to the UE (110), the one or more base stations and / or the user plane entity (130) of the mobile network (100).

12. The network functional entities (140, 160, 161) according to claim 11, characterized in that, The network function entities (140, 160, 161) are the Access and Mobility Management Function (AMF) entity (160) or the Policy Control Function (PCF) entity (161) of the mobile network (100).

13. A method (600) for operating a control surface entity (150), characterized in that, The control plane entity (150) is used to control traffic destined for and / or originating from user equipment (UE) applications (110) via one or more base stations, wherein the one or more base stations provide one or more access networks (120) and provide multiple data channels for each access network in the mobile network (100). to The method (600) includes: Obtain (601) preference information of the traffic sent to and / or from the UE application, wherein the preference information represents one or more preferred access networks (120) and / or the plurality of data channels ( to One or more preferred data channels in ) and Based on the preference information, mapping data (603) is generated, wherein the mapping data defines the traffic destined for and / or originating from the UE application and the plurality of data channels of the one or more access networks (120). to Mapping between one or more data channels in ().

14. A computer program product, characterized in that, Includes a computer-readable storage medium for storing program code, which, when executed by a computer or processor, causes the computer or processor to perform the method (600) according to claim 13.

Images