Network traffic distribution for multiple access sessions

Abstract

Methods, computer program products, and apparatus are provided for supporting low latency, low loss, and scalable throughput (LS4) for non-3rd generation partnership project (3GPP) access networks. In a multiple access (MA) protocol data unit (PDU) session, traffic is redistributed by a user equipment (UE) between access networks based on access traffic steering, handover, separation (ATSSS) rules, and / or explicit congestion notification (ECN). A user plane function (UPF) may update ECN information in a PDU of uplink traffic based on congestion information for L4S provided by an access network. The UPF redistributes traffic between the access networks based on congestion information received via one or more access networks, and ECN information transmitted in the PDU may be correspondingly updated.

Description

Technical Field

[0001] Example embodiments relate generally to communication networks and, more particularly, but not exclusively, to apparatus, methods, and computer programs for traffic distribution of multiple access sessions of a communication network. Background Art

[0002] A communication network enables communication between two or more communication devices, or provides communication devices access to a data network. The communication network may operate in accordance with standards such as those provided by 3GPP (3rd Generation Partnership Project) or ETSI (European Telecommunications Standards Institute). An example of a standard is the so-called 5G (fifth generation) standard provided by 3GPP. Previous 3rd Generation Partnership Project (3GPP) versions of the fifth generation core network (5GC) have addressed low latency, low loss, and scalable throughput within data networks. Summary of the invention

[0003] An apparatus is provided, the apparatus comprising components for receiving at least one of the following: (a) access traffic steering, switching, splitting (ATSSS) rules for distributing traffic for transmission to at least two nodes configured for access, the at least two nodes comprising: at least one node configured for non-third generation partnership project (non-3GPP) access, wherein the ATSSS rules are received from a session management function (SMF) and are based on information used for explicit congestion notification (ECN) information provided by a user plane function (UPF), or (b) ECN information in a protocol data unit (PDU) received via at least one node configured for non-3GPP access, and components for distributing traffic for transmission to the at least two nodes based on at least one of the ASSS rules or the ECN information.

[0004] The apparatus also includes: a component for updating explicit congestion notification (ECN) information in a downlink PDU, wherein the ECN information in the downlink PDU indicates: uplink congestion at one or more of the at least two nodes, and is based on one or more of the following items: (a) ECN information received via at least one node configured for non-3GPP access, or (b) traffic distribution performed by the apparatus, wherein the downlink PDU including the updated ECN information indicating uplink congestion is sent to the host. At least one of the following items is also based on one or more local conditions: (a) distribution of traffic, or (b) updating of ECN information, the one or more local conditions including at least one of the following items: local congestion, network interface availability, signal loss condition, or user preference.

[0005] According to certain embodiments, at least one of the following items is also based on ECN information received at at least another node of the at least two nodes: (a) distribution of traffic, or (b) update of ECN information. At least one of the following items is also based on combining ECN information received via at least two nodes: (a) distribution of traffic, or (b) update of ECN information. The apparatus also includes: a component for sending the following in a request for at least one of establishment or modification of a multiple access (MA) (PDU) session for transmission via at least two nodes: an indication that ATSSS and low latency, low loss, and scalable throughput (L4S) are enabled at least for a node configured as a non-3GPP access.

[0006] Also provided is an apparatus, the apparatus comprising: a user plane function (UPF) for a communication network, configured to perform: receiving congestion information for low latency, low loss, and scalable throughput (L4S) via a node configured for non-third generation partnership project (non-3GPP) access. The UPF is also configured to perform receiving a protocol data unit (PDU) via at least two nodes configured for access, wherein the at least two nodes include a node configured for non-3GPP access, and updating explicit congestion notification (ECN) information in the PDU based on at least the received congestion information for L4S. The UPF is also configured to send a PDU including updated ECN information to a host.

[0007] The congestion information for L4S includes: a percentage of packets that the device is directed to use for L4S. The updating of the ECN information is also based on: congestion information for L4S received via at least another node of the at least two nodes. The updating of the ECN information includes: combining the congestion information for L4S received via the at least two nodes to determine updated ECN information.

[0008] The UPF is also configured to perform: updating access traffic steering, switching and splitting (ATSSS) rule information based on received congestion information for L4S received at least via the non-3GPP access node, and providing updated ATSSS rule information to a user equipment (UE).

[0009] According to some embodiments, at least one of the updating of the ECN information or the updating of the ATSS rule information is further based on: at least one rule or at least one setting provided by a session management function (SMF).

[0010] A device is provided, which includes a user plane function (UPF) for a communication network, configured to perform: receiving congestion information for low latency, low loss, and scalable throughput (L4S) via a node configured for non-third generation partnership project (non-3GPP) access, and adjusting the traffic distribution of downlink protocol data units (PDUs) between at least two nodes configured for access based on at least the congestion information for L4S, wherein the at least two nodes include: a node configured for non-3GPP access.

[0011] The UPF is also configured to perform: updating explicit congestion notification (ECN) information in a downlink PDU based on at least the received congestion information for L4S and the adjustment of traffic distribution, wherein the downlink PDU including the updated ECN information is sent via at least one of the two nodes.

[0012] A device is provided, comprising: at least one processor, and at least one memory storing instructions, wherein the instructions, when executed by the at least one processor, cause the device to perform at least one of receiving at least one of the following items: (a) access traffic steering, switching, splitting (ATSSS) rules for distributing traffic between at least two nodes configured for access, the at least two nodes including: at least one node configured for non-third generation partnership project (non-3GPP) access, wherein the ATSSS rules are received from a session management function (SMF) and are based on information used for explicit congestion notification (ECN) information provided by a user plane function (UPF), or (b) ECN information in a protocol data unit (PDU) received via at least one node configured for non-3GPP access, and a component for distributing traffic between the at least two nodes based on at least one of the ASSSS rules or the ECN information.

[0013] The instructions, when executed by at least one processor, further cause the apparatus to at least perform: updating explicit congestion notification (ECN) information in a downlink PDU, wherein the ECN information in the downlink PDU indicates uplink congestion at one or more of the at least two nodes, and based on one or more of the following: (a) ECN information received via at least one node configured for non-3GPP access, or (b) traffic distribution performed by the apparatus, wherein the downlink PDU including the updated ECN information indicating uplink congestion is sent to the host. At least one of the following is also based on one or more local conditions: (a) distribution of traffic, or (b) updating of ECN information, the one or more local conditions including at least one of the following: local congestion, network interface availability, signal loss condition, or user preference.

[0014] According to certain embodiments, at least one of the following items is also based on ECN information received at at least another node of the at least two nodes: (a) distribution of traffic, or (b) update of ECN information. At least one of the following items is also based on combining ECN information received via at least two nodes: (a) distribution of traffic, or (b) update of ECN information. The instruction, when executed by at least one processor, also causes the device to perform: in a request for at least one of establishment or modification of a multiple access (MA) (PDU) session for transmission via at least two nodes, sending an indication that ATSSS and low latency, low loss, and scalable throughput (L4S) are enabled at least for a node configured for non-3GPP access.

[0015] A device is also provided, the device including a user plane function (UPF) for a communication network, the device including at least one processor, and at least one memory storing instructions, wherein the instructions, when executed by the at least one processor, cause the device to at least perform: receiving congestion information for low latency, low loss, and scalable throughput (L4S) via a node configured for non-third generation partnership project (non-3GPP) access. The instructions, when executed by the at least one processor, also cause the device to at least perform receiving a protocol data unit (PDU) via at least two nodes configured for access, wherein the at least two nodes include a node configured for non-3GPP access, and updating explicit congestion notification (ECN) information in the PDU based on at least the received congestion information for L4S. The instructions, when executed by the at least one processor, also cause the device to at least send a PDU including updated ECN information to a host.

[0016] The instruction, when executed by at least one processor, also causes the device to at least perform: updating access traffic steering, switching, and separation (ATSSS) rule information based on received congestion information for L4S received at least via a non-3GPP access node, and providing updated ATSSS rule information to a user equipment (UE).

[0017] Provided is a device, the device comprising a user plane function (UPF) for a communication network, the device comprising at least one processor, and at least one memory storing instructions, wherein the instructions, when executed by the at least one processor, cause the device to receive congestion information for low latency, low loss, and scalable throughput (L4S) at least via a node configured for non-third generation partnership project (non-3GPP) access, and adjust the traffic distribution of downlink protocol data units (PDUs) between at least two nodes configured for access based on at least the congestion information for L4S, wherein the at least two nodes include: a node configured for non-3GPP access. When the instructions are executed by the at least one processor, the device is also configured to: update explicit congestion notification (ECN) information in a downlink PDU based on at least the received congestion information for L4S and the adjustment of traffic distribution, wherein the downlink PDU including the updated ECN information is sent via at least one of the two nodes.

[0018] A method is provided, comprising: receiving at least one of the following: (a) access traffic steering, switching, splitting (ATSSS) rules for distributing traffic between at least two nodes configured for access, the at least two nodes including: at least one node configured for non-third generation partnership project (non-3GPP) access, wherein the ATSSS rules are received from a session management function (SMF) and are based on information used for explicit congestion notification (ECN) information provided by a user plane function (UPF), or (b) ECN information in a protocol data unit (PDU) received via at least one node configured for non-3GPP access, and distributing traffic between the at least two nodes based on at least one of the ASSS rules or the ECN information.

[0019] The method also includes: updating explicit congestion notification (ECN) information in a downlink PDU, wherein the ECN information in the downlink PDU indicates: uplink congestion at one or more of the at least two nodes, and based on one or more of the following items: (a) ECN information received via at least one node configured for non-3GPP access, or (b) traffic distribution, the downlink PDU including the updated ECN information indicating the uplink congestion is sent to the host.

[0020] The method also includes sending, in a request for at least one of establishment or modification of a multiple access (MA) (PDU) session for transmission via at least two nodes, an indication that ATSSS and low latency, low loss, and scalable throughput (L4S) are enabled at least for a node configured for non-3GPP access.

[0021] A method for a user plane function (UPF) of a communication network is provided, the method comprising: receiving, via a node configured for non-third generation partnership project (non-3GPP) access, congestion information for low latency, low loss, and scalable throughput (L4S), and receiving, via at least two nodes configured for access, a protocol data unit (PDU), wherein the at least two nodes include a node configured for non-3GPP access.

[0022] The method also includes: updating explicit congestion notification (ECN) information in the PDU based on at least the received congestion information for L4S, and sending the PDU including the updated ECN information to the host. The method also includes: updating access traffic steering, switching and splitting (ATSSS) rule information based on at least the received congestion information for L4S received via the non-3GPP access node, and providing the updated ATSSS rule information to the user equipment (UE).

[0023] A method for a user plane function (UPF) of a communication network is provided, the method comprising: receiving congestion information for low latency, low loss and scalable throughput (L4S) via a node configured for non-3rd Generation Partnership Project (non-3GPP) access, and adjusting traffic distribution of downlink protocol data units (PDUs) between at least two nodes configured for access based on at least the congestion information for L4S, wherein the at least two nodes include: a node configured for non-3GPP access. The method also includes: updating explicit congestion notification (ECN) information in a downlink PDU based on at least the received congestion information for L4S and the adjustment of traffic distribution, wherein the downlink PDU including the updated ECN information is sent via at least one of the two nodes.

[0024] A computer program product is provided, comprising at least one non-transitory computer-readable storage medium having computer-executable program code instructions stored therein, the computer-executable program code instructions including program code instructions to receive at least one of the following: (a) access traffic steering, switching, splitting (ATSSS) rules for distributing traffic between at least two nodes configured for access, the at least two nodes comprising: at least one node configured for non-third generation partnership project (non-3GPP) access, wherein the ATSSS rules are received from a session management function (SMF) and are based on information used for explicit congestion notification (ECN) information provided by a user plane function (UPF), or (b) ECN information in a protocol data unit (PDU) received via at least one node configured for non-3GPP access.

[0025] The computer executable program code instructions include program code instructions to distribute traffic between at least two nodes based on at least one of ATSSS rules or ECN information.

[0026] The computer executable program code instructions include program code instructions to update explicit congestion notification (ECN) information in a downlink PDU, wherein the ECN information in the downlink PDU indicates uplink congestion at one or more of the at least two nodes, and based on one or more of the following: (a) ECN information received via at least one node configured for non-3GPP access, or (b) traffic distribution, wherein the downlink PDU including the updated ECN information indicating uplink congestion is sent to the host. The computer executable program code instructions also include program code instructions to send an indication that ATSSS and low latency, low loss, and scalable throughput (L4S) are enabled at least for the node configured for non-3GPP access in a request for at least one of establishment or modification of a multi-access (MA) (PDU) session for transmission via the at least two nodes.

[0027] A computer program product is provided, comprising at least one non-transitory computer-readable storage medium having stored therein computer-executable program code instructions for a user plane function (UPF) of a communication network, the computer-executable program code instructions comprising program code instructions to receive congestion information for low latency, low loss, and scalable throughput (L4S) via a node configured for non-3rd Generation Partnership Project (non-3GPP) access.

[0028] The computer executable program code instructions include program code instructions to receive a protocol data unit (PDU) via at least two nodes configured for access, wherein the at least two nodes include a node configured for non-3GPP access, and update explicit congestion notification (ECN) information in the PDU based on at least received congestion information for L4S. The computer executable program code instructions include program code instructions to send the PDU including the updated ECN information to the host.

[0029] The computer executable program code instructions include program code instructions to update access traffic steering, switching and splitting (ATSSS) rule information based on received congestion information for L4S received at least via a non-3GPP access node, and provide updated ATSSS rule information to a user equipment (UE). At least one of the updating of ECN information or the updating of ATSSS rule information is also based on: at least one rule or at least one setting provided by a session management function (SMF).

[0030] A computer program product is provided, comprising at least one non-transitory computer-readable storage medium, wherein computer executable program code instructions for a user plane function (UPF) of a communication network are stored, the computer executable program code instructions including program code instructions to receive congestion information for low latency, low loss, and scalable throughput (L4S) via a node configured for non-third generation partnership project (non-3GPP) access. The computer executable program code instructions include program code instructions to adjust the flow distribution of downlink protocol data units (PDUs) between at least two nodes configured for access based on at least the congestion information for L4S, wherein the at least two nodes include: a node configured for non-3GPP access.

[0031] The computer executable program code instructions include program code instructions to update explicit congestion notification (ECN) information in a downlink PDU based on at least received congestion information for L4S and adjustment of traffic distribution, wherein the downlink PDU including the updated ECN information is sent via at least one of the two nodes.

[0032] The above content of the invention is only used for the purpose of summarizing some example embodiments of the present disclosure, so as to provide a basic understanding of some aspects of the present disclosure. Therefore, it should be understood that the above example embodiments are merely examples and should not be interpreted as narrowing the scope or spirit of the present disclosure in any way. It should be understood that the scope of the present disclosure covers many potential embodiments, some of which will be further described below in addition to the embodiments summarized here. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] Having generally described certain example embodiments of the present disclosure above, reference will now be made to the accompanying drawings, which are not necessarily drawn to scale, and in which:

[0034] Figure 1 is a diagram of an apparatus that may be specially configured in accordance with certain example embodiments;

[0035] Figure 2 is a diagram of a mobile network according to certain example embodiments;

[0036] Figure 3 is an illustration according to some example embodiments Figure 2 A diagram of the network functions and interfaces of a mobile network;

[0037] Figure 4 is an illustration according to some example embodiments Figure 2 A diagram of the network functions and interfaces of a mobile network;

[0038] Figure 5is a diagram illustrating network functions and interfaces for a MAPDU session utilizing a 3GPP access network and a non-3GPP access network, according to certain example embodiments;

[0039] Figure 6 is a diagram illustrating a process for network traffic distribution for MA PDU sessions utilizing 3GPP access networks and non-3GPP access networks, according to certain example embodiments;

[0040] Figure 7 and 8 is a flow diagram of operations that may be performed by a user plane function (UPF) according to certain example embodiments; and

[0041] Fig. 9 is a flow diagram of operations that may be performed by a user equipment (UE) according to certain example embodiments. DETAILED DESCRIPTION

[0042] Some embodiments of the present disclosure will now be described more fully below with reference to the accompanying drawings, in which some, but not all, embodiments of the present disclosure are shown. In fact, various embodiments of the present disclosure may be embodied in many different forms and should not be construed as being limited to the embodiments described herein; on the contrary, these embodiments are provided so that the present disclosure will satisfy applicable legal requirements. Similar reference numerals always refer to similar elements. As used herein, the terms "data," "content," "information," and similar terms may be used interchangeably to refer to data that can be sent, received, and / or stored according to embodiments of the present disclosure. Therefore, the use of any such terms should not be viewed as limiting the spirit and scope of the embodiments of the present disclosure.

[0043] In addition, as used herein, the term "circuitry" refers to (a) a hardware circuit implementation only (e.g., an implementation in analog circuitry and / or digital circuitry); (b) a combination of circuitry and (multiple) computer program products, including software and / or firmware instructions stored on one or more computer-readable memories, which work together to cause the device to perform one or more functions described herein; and (c) circuitry, such as, for example, (multiple) microprocessors or a portion of (multiple) microprocessors, which requires software or firmware to operate even if the software or firmware is not physically present. This definition of "circuitry" applies to all uses of the term herein, including in any claims. As a further example, the term "circuitry" as used herein also includes an implementation including one or more processors and / or (multiple) portions thereof and accompanying software and / or firmware. As another example, the term "circuitry" as used herein also includes, for example, a baseband integrated circuit or application processor integrated circuit for a mobile phone or a similar integrated circuit in a server, a cellular network device, other network equipment (such as a core network device), a field programmable gate array, and / or other computing devices. The development of new communication technologies, such as fifth generation (5G) and sixth generation (6G), has improved upon existing technologies, such as second generation (2G) technology, third generation (3G) technology, fourth generation (4G) technology, and long term evolution (LTE) technology, resulting in improved network connectivity.

[0044] The increased use and development of latency-sensitive applications, including but not limited to extended reality (ER), extended reality and media services (ERM), virtual reality, mixed reality, augmented reality, real-time cloud gaming, etc., have placed increased demands on the performance of communication networks, especially communication networks operating according to 3GPP standards. Low Latency, Low Loss, and Scalable Throughput (L4S) marking of an Explicit Congestion Notification (ECN) bit indicating congestion is specified in Release 18 of 3GPP Technical Specification (TS) 23.501. L4S is described in Internet Engineering Task Force (IETF) Change Request (RFC) 9330

[159] , IETF RFC 9331

[160] , and IETF RFC 9332

[161] . Fifth Generation System (5GS) communication networks can expose congestion information by marking the ECN bit in the Internet Protocol (IP) header of user plane IP packets sent between user equipment (UE) and application servers. The L4S marking or ECN information can trigger application layer rate adaptation by hosts that support L4S.

[0045] In 5GS, ECN marking for L4S is enabled per quality of service (QoS) flow in the uplink and / or downlink direction and can be used for guaranteed bit rate (GBR) and non-GBR QoS flows. The protocol data unit (PDU) session anchor (PSA) user location function (UPF) for the next generation radio access network (NG-RAN) or for 3GPP access supports ECN marking for L4S in the IP header. In the case of ECN marking for L4S by the UPF, the radio access network (RAN) reports congestion information to the UPF using the general packet radio service (GPRS) tunneling protocol user (GTP-U) header of the uplink PDU. The UPF uses this information to determine the L4S ECN packet marking.

[0046] 3GPP TS23.501, clause 5.32, describes Access Traffic Steering, Switching, Splitting (ATSSS). Access traffic steering involves selecting an access network for a new data flow and sending the traffic for this data flow on the selected access network. Access traffic switching involves moving all traffic for an ongoing data flow from one access network to another access network in a manner that maintains the continuity of the data flow. Access traffic splitting involves splitting the traffic of a data flow across multiple access networks. When traffic splitting is applied to a data flow, some traffic of the data flow is transmitted via one access, while some other traffic of the same data flow is transmitted via another access.

[0047] When a UE has a multi-access (MA) PDU session terminated in one MA PSA UPF, the UE is connected by two accesses simultaneously. A UE and / or UPF supporting ATSSS includes a multipath transmission control protocol (TCP) (MPTCP) agent, a multipath QUIC (MPQUIC) agent, and an ATSSS lower layer (ATSSS-LL). MPTCP and MPQUIC are considered higher layer bootstrap functions and are constrained by IETF standards (IETF RFC 8684 for MPTCP and IETF RFC 9000 / 9001 / 9002 for MPQUIC and multipath extensions). ATSSS-LL is applicable to a variety of data traffic types, including TCP traffic, User Datagram Protocol (UDP) traffic, or Ethernet traffic.

[0048] For uplink traffic, the UE applies network-provided policies (ATSSS rules) and takes into account local conditions to decide how the traffic will be distributed across the two access networks. MA PSA UPF similarly applies network policies and feedback from the UE to decide how to distribute downlink traffic between the N3 and / or N9 tunnels associated with the two access networks.

[0049] ATSSS supports the following steering modes, which are specified in the ATSSS rules sent to the UE and the N4 multi-access rules sent to the UPF: "Active-Standby", "Minimum Delay", "Load Balancing", or "Priority-based" or "Redundant". In the case of "Load Balancing", the Service Data Flow (SDF) traffic is separated between the two accesses. The separation is specified in the ATSSS rules sent to the UE. In this regard, the rules contain the percentage of SDF traffic that should be sent over the 3GPP access and the non-3GPP access. In the case of "Priority-based", all traffic for the SDF is directed to the high priority access until the access is determined to be congested. In addition, the "Steering Mode Indicator" indicates whether the UE can adjust the traffic steering based on its own decision (for example, the UE can perform autonomous load balancing).

[0050] 3GPP TS23.501, TS23.502 and TS23.503 describe the stage 2 architecture, procedures and policies for both L4S and ASSS. However, the procedures and policies for L4S and ASSS function independently of each other.

[0051] The L4S ECN marks the L4S provided by the NG-RAN or UPF of the 5GS to indicate that congestion has occurred on the 3GPP access and allows applications and / or application hosts to adjust the amount of traffic being sent. There is no consideration that backup access (e.g., non-3GPP access) can be used to redistribute traffic. According to the example embodiments provided herein, redistribution of traffic between access nodes (including non-3GPP access nodes) is enabled and can assist applications and / or application hosts in improving their congestion management to achieve low latency and low loss.

[0052] The non-3GPP access network (AN) may include, as non-limiting examples, an untrusted non-3GPP access network, a trusted non-3GPP access network, a wired access network, where the wired access may be a wired 5G cable access network or a wired Broadband Forum (BBF) access network, a wireless local area network, etc.

[0053] Example embodiments provided herein relate to a PSA UPF and / or UE that enables traffic distribution among multiple access nodes including a 3GPP access node (e.g., an access node configured for 3GPP access). According to an example embodiment, a MA PDU session for ATSSS is activated for an SDF, and L4S is activated for at least one access. According to an example embodiment, a RAN node and / or an access node: (a) reports uplink (UL) or downlink (DL) congestion information for L4S to a UPF (e.g., provided in a GTP-U header), or (b) provides an L4S-tagged PDU for UL or DL ​​traffic to a UPF or UE.

[0054] According to an example embodiment, if L4S is activated for more than one access, the UPF or UE uses the relative L4S marking and / or relative congestion information received from the corresponding access node to adjust the traffic separation, switching or steering between the accesses. Performance measurements (see TS23.501, clause 5.32.5) can also be used to determine congestion. The UPF also notifies the session management function (SMF) / policy management function (PCF), and the SMF provides updated ATSSS rules for separating, switching and directing traffic through the uplink to the UE. The UE uses the updated ATSSS rules to update its way of directing, switching and separating traffic. Alternatively, the UE can also separate, switch or direct traffic based on the L4S marking in the UP packet received from the RAN / AN or UPF, or simply based on the congestion it experiences and the L4S marking it intends to provide to the application layer. Before forwarding the PDU to the application / host, the UPF or UE may adjust the L4S marking of the PDU based on one or more of the congestion information for L4S received on each access (e.g., the percentage of packets to be marked as L4S) and the revised traffic distribution on the access.

[0055] According to an example embodiment, if L4S is active for only one access, the UPF or UE adjusts the traffic separation, switching or steering between the accesses based on access network performance measurements (see TS23.501, clause 5.32.5) and L4S marking and / or congestion information for L4S received from one of the accesses. Before forwarding the PDU to the application and / or application host, the UPF or UE may adjust the L4S marking of the PDU based on the congestion information for L4S received from the access node configured for the access, and adjust the distribution of traffic between the accesses.

[0056] When adjusting traffic distribution, according to an example embodiment, the UPF or UE may decide to switch traffic of a data flow sent by one access to another access, or may decide to change the way in which data flows are separated between accesses. When adjusting traffic distribution, the UPF may adjust the distribution of service flows or other data flows for which L4S marking is being executed. When the ATSSS steering mode is set to certain modes (such as but not limited to "load balancing", "minimum delay" or "priority-based"), the example embodiments may adjust traffic distribution as described herein.

[0057] It will be understood that as used herein, the terms "3GPP access" and "non-3GPP access" may be used to refer to any (multiple) nodes of an access network, any (multiple) nodes being access points, any (multiple) nodes supporting an access network, any (multiple) nodes configured for access, and / or any interworking functions of an access network. Thus, references to nodes configured for access may refer to any (multiple) of the above-mentioned nodes of an access network. For example, in the case of a non-trusted non-3GPP access network, congestion information and / or ECN marking may be provided by a non-3GPP interworking function (N3IWF). In the case of a trusted non-3GPP access network, congestion information and / or ECN marking are provided by a trusted non-3GPP gateway function (TNGF). In the case of a wired access network, congestion information and / or ECN marking are provided by a wired access gateway function (W-AGF). In the case of a WLAN access, congestion information and / or ECN marking are provided by a trusted WLAN interworking function (TWIF).

[0058] refer to Figure 1 , an apparatus 10 for a communication system, such as Figures 2 to 5 The communication system 100 shown in and described in further detail below. In some embodiments, the device 10 may include or implement network functions of the communication system 100 (e.g., network functions of a core network, such as UPF, PCF, SMF, etc.). In some embodiments, the device 10 may be used to control (multiple) nodes of an access network (e.g., a 3GPP access network and / or a non-3GPP access network), to control (multiple) any nodes that are access points to the access network, to support any (multiple) nodes of the access network, to control any (multiple) nodes configured to enable user equipment to access the communication system, and / or to implement interworking functions of the access network that enable the access network to communicate with the core network of the communication system. In some embodiments, the device 10 may be a UE.

[0059] like Figure 1As shown, the apparatus 10 includes a processing circuit system 20 (generally referred to herein as a processor), a memory device 60 (generally referred to herein as a memory), and a communication interface 40. The processing circuit system 20 can communicate with the memory device 60 via a bus for transferring information between the processing circuit system 40 and the memory 60 of the apparatus 10. The memory 60 can be non-transient and can include, for example, one or more volatile and / or non-volatile memories. In other words, for example, the memory device 60 can be an electronic storage device (e.g., a computer-readable storage medium) including a gate configured to store data (e.g., bits) that can be retrieved by a machine (e.g., a computing device such as a processing circuit system). The memory device 60 can be configured to store information, data, content, applications, instructions, etc., so that the apparatus can perform various operations according to the exemplary embodiments of the present disclosure. For example, the memory device 60 can be configured to buffer input data for processing by the processing circuit system 20. Additionally or alternatively, the memory device 60 can be configured to store instructions for execution by the processing circuit system 20.

[0060] In some embodiments, the device 10 may be embodied in various computing devices as described above. However, in some embodiments, the device may be embodied as a chip or a chipset. In other words, the device may include one or more physical packages (e.g., chips), including materials, components and / or wires on a structural component (e.g., a substrate). The structural component may provide physical strength, size savings and / or electrical interaction limitations for the component circuit system included thereon. Therefore, in some cases, the device may be configured to implement an embodiment of the present disclosure on a single chip or as a single "system on a chip". Therefore, in some cases, a chip or a chipset may constitute a component for performing one or more operations to provide the functions described herein. In an embodiment in which the device 10 implements or includes a network function of a communication system, it may be a computing device, such as a stand-alone computer, a distributed computing system, or a cloud computing system. In some embodiments, the network function of the communication system may be a virtualized network function implemented by the device 10, or a cloud native network function implemented on the device 10 (e.g., when the device 10 is a cloud computing system).

[0061] The processing circuit system 20 can be embodied in a variety of different ways. For example, the processing circuit system 20 can be embodied as one or more of various hardware processing components, such as a coprocessor, a microprocessor, a controller, a digital signal processor (DSP), a processing element with or without an accompanying DSP, or various other circuit systems, including integrated circuits, such as, for example, application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), microcontroller units (MCUs), central processing units (CPUs), multi-core CPUs, graphics processing units (GPUs), tensor processing units (TPUs), hardware accelerators, special computer chips, etc. Therefore, in some embodiments, the processing circuit system may include one or more processing cores configured to execute independently. The multi-core processing circuit system can implement multi-processing within a single physical package. In addition or alternatively, the processing circuit system may include one or more processors configured in series via a bus to enable independent execution, pipelining, and / or multi-threading of instructions.

[0062] In an example embodiment, the processing circuit system 20 may be configured to execute instructions stored in the memory device 60 or otherwise accessible to the processing circuit system 20. Alternatively or additionally, the processing circuit system may be configured to perform hard-coded functions. Therefore, whether configured by hardware or software methods, or by a combination of the two, the processing circuit system may represent an entity (e.g., physically embodied in a circuit system) that is capable of performing operations according to embodiments of the present disclosure while being configured accordingly. Therefore, for example, when the processing circuit is embodied as an ASIC, FPGA, etc., the processing circuit system may be specially configured hardware for performing the operations described herein. Alternatively, as another example, when the processing circuit system 20 is embodied as an executor of instructions, the instructions may specifically configure the processor to perform the algorithms and / or operations described herein when the instructions are executed. However, in some cases, the processing circuit system 20 may be a processor of a specific device (e.g., an extended reality system) that is configured to employ embodiments of the present disclosure by further configuration of the processing circuit system by instructions for performing the algorithms and / or operations described herein. Processing circuitry 20 may include, among other things, a clock, an arithmetic logic unit (ALU), and logic gates configured to support the operation of the processing circuitry.

[0063] The communication interface 40 can be any component, such as a device or circuit system embodied in hardware or a combination of hardware and software, configured to receive and / or send data, including media content in the form of video or image files, one or more audio tracks, etc. In this regard, the communication interface 40 may include, for example, an antenna (or multiple antennas) and support hardware and / or software for enabling wireless communication. Additionally or alternatively, the communication interface may include a circuit system for interacting with (multiple) antennas to cause the transmission of wireless or radio signals via (multiple) antennas or the reception of wireless or radio signals received via (multiple) antennas. In some environments, the communication interface may alternatively or also support wired communication. Therefore, for example, the communication interface may include a communication modem and / or other hardware / software for supporting communication via cable, digital subscriber line (DSL), universal serial bus (USB) or other mechanisms.

[0064] According to an example embodiment, the apparatus 10 may implement the example embodiments disclosed herein and / or components thereof.

[0065] Figures 2 to 5 Various examples of a communication network 100 (e.g., a mobile network or a telecommunications network) are shown. The communication network 100 is configured to enable a user device 102 to connect to an application server 112 via an access network 104 and a core network 101 (which together form a communication system (e.g., 5GS) of the communication network 100) and a data network 116. In some embodiments, the communication network 100 may include any suitable configuration, number, orientation, location and / or size of components and dedicated equipment configured to provide an air interface (e.g., New Radio (NR)) for communication or connection between a user equipment 102 (UE 102) and the access network 104. As shown in FIG. Figure 2As shown, UE 102 is in operable communication with access network 104, and in some embodiments, access network 104 is a 5G access network (5G-AN) (e.g., 3GPP AN, non-3GPP AN). In some embodiments, UE 102 can be in operable communication with another access network (AN) (not shown) connected to core network 101. Examples of other ANs include non-3GPP access networks (ANs), such as non-trusted non-3GPP access networks terminated at N3IWF, trusted non-3GPP access networks, wired access networks terminated at W-AGF (wherein the wired access can be a wired 5G cable access network or a wired Broadband Forum (BBF) access network), wireless local area network (WLAN), etc. The access network may include one or more nodes (e.g., base stations, access points, access network nodes, etc.). In some embodiments, access network 104 may communicate with CN 101 or a network entity or network function of CN 101 using a reference point. In some embodiments, CN 101 may establish a data connection (e.g., a PDU session) between UE 102 and the UPF of CN 101. However, it should be understood that while the embodiments are described in conjunction with 5G-AN (e.g., RAN), R(AN), and 5G, the communication system 100 may include other types of access networks that may be developed in the future.

[0066] In some embodiments, an application server (AS) or application function (AF) 112 hosted on the AS may communicate with the CN 101. The AN 104, CN 101, DN 116, and / or AS / AF 112 may be associated with a network repository function (NRF) 124, a secure copy protocol (SCP), a secure edge protection proxy (SEPP), a policy control function (PCF) 114, etc., or any combination thereof.

[0067] The communication network 100 may include a series of connected network devices and dedicated hardware distributed throughout a service area, state, province, city, or country, and one or more network entities, which may be stored at and / or hosted by one or more connected network devices or dedicated hardware. In some embodiments, the UE 102 may be connected to the AN 104, which may then relay communications between the UE 102 and the CN 101, which may be connected to the DN 116, which may communicate with one or more ASs (or AFs 112 hosted on the AS). In some embodiments, the UE 102 may communicate with the (R)AN 104 depicting any 5G-AN, which may act as a relay between the UE 102 and other components or services of the CN 101. For example, in some embodiments, the UE 102 may communicate with the (R)AN 104, which in turn may communicate with the access and mobility management function 108 (AMF 108). In other instances or embodiments, the UE 102 may communicate directly with the AMF 108. In some embodiments, the AMF 108 may communicate with one or more network functions (NFs) such as the authentication server function 120 (AUSF 120), the network slice selection function 122 (NSSF 122), the network repository function 124 (NRF 124), the policy control function 114 (PCF 114), the network data analysis function 126 (NWDAF 126), the unified data management function 118 (UDM 118), the AS / AF 112, the session management function 110 (SMF 110), etc. using a service-based interface.

[0068] In some embodiments, the SMF 110 may communicate with one or more user plane functions 106 (UPF 106, UPF 106a, UPF 106b, collectively referred to as "UPF 106"). By way of example only, in some embodiments, the UPF 106 may communicate with the (R)AN 104 and the DN 116. In other embodiments, the DN 116 may communicate with the first UPF 106a, and the (R)AN 104 may communicate with the second UPF 106b, while the SMF 110 communicates with both the first UPF 106a and the second UPF 106b, and the first UPF 106a and the second UPF 106b communicate with each other.

[0069] In some embodiments, the UE 102 may include a single mode or dual mode device, so that the UE 102 can connect to one or more access networks (AN) 104. In some embodiments, where the AN is a (R)AN, the R(AN) may be configured to implement one or more radio access technologies (RATs), such as Bluetooth, Wi-Fi, Global System for Mobile Communications (GSM), Universal Mobile Telecommunications Service (UMTS), LTE, or 5G NR, etc., which may be used to communicate with the UE 102 and the CN 101. In some embodiments, the (R)AN 104 may implement one or more base stations for control plane communications between the UE 102 and the AMF 108 of the CN 101.

[0070] In some embodiments, the mobile network 100 or its components (e.g., base stations, towers, etc.) may be configured to communicate with a communication device (e.g., UE 102) via multiple different frequency bands (e.g., FR1 (below 6 GHz), FR2 (mm wave), other suitable frequency bands, sub-bands thereof, etc.). In some embodiments, the communication network 100 may include or employ massive multiple-input multiple-output (massive MIMO) antennas. In some embodiments, the UE 102 and / or the RAN 104 may include multi-user MIMO (MU-MIMO) antennas. In some embodiments, the communication network 100 may employ edge computing so that the computing system of the data network 116 is closer to the communication system (e.g., UPF of the core network 101) in terms of communication, physics, computing, and / or time to reduce latency and data traffic congestion. In some embodiments, the (R)AN 104 may employ other technologies, devices, or techniques, such as small cells, low-power (R)ANs, beamforming of radio waves, WIFI-cellular convergence, non-orthogonal multiple access (NOMA), channel coding, etc.

[0071] like Figure 4As shown, a service-based architecture of CN 101 is shown, wherein UE 102 may be configured to communicate with AN 104 via an N1 interface, for example, using non-access stratum (NAS) signaling or messages. In certain embodiments, such as those in which AN 104 is a (R)AN, the (R)AN may be configured to communicate with CN 101 or its network entity or network function (e.g., AMF 108) via an N2 interface, for example, between a node of (R)AN 104 and AMF 108. The N1 and N2 interfaces are control plane interfaces (otherwise referred to as reference points). In some embodiments, AN 104 may be configured to communicate with UPF 106 via an N3 interface, for example, in a user plane. In some embodiments, AMF 108 and / or SMF 110 may be configured to communicate with other network entities or network functions of CN 101 using different interfaces (e.g., service-based interfaces) and / or according to various different protocols. For example, in some embodiments, the AMF 108 and / or SMF 110 may be configured to communicate with the AUSF 120 using the Nausf interface or via the N12 interface. In some embodiments, the AMF 108 and / or SMF 110 may be configured to communicate with the NSSF 122 using the Nnssf interface. In some embodiments, the AMF 108 and / or SMF 110 may be configured to communicate with the NRF 124 using the Nnrf interface. In some embodiments, the AMF 108 and / or SMF 110 may be configured to communicate with the PCF 114 using the Npcf interface or via the N7 interface. In some embodiments, the AMF 108 and / or SMF 110 may be configured to communicate with the NWDAF 126 using the Nnwdaf interface. In some embodiments, the AMF 108 and / or SMF 110 may be configured to communicate with the UDM 118 using the Nudm interface, via the N8 interface, or via the N10 interface. In some embodiments, the AMF 108 and / or SMF 110 may be configured to communicate with the AS / AF 112 using a Naf interface. In some embodiments, the SMF 110 may be configured to communicate with the UPF 106 via an N4 interface, which may act as a bridge between the control plane and the user plane, such as acting as a conduit for a protocol data unit (PDU) session during which information is sent between, for example, the UE 102 and the CN 101 or its components / services.

[0072] Figure 51 is a diagram illustrating network functions and interfaces for an MA PDU session established via a 3GPP AN 104a (e.g., (R)AN) and a non-3GPPAN 104b, according to certain example embodiments. The UE 102 is configured to communicate with the AMF 112 via a 3GPP access 104a or a non-3GPP access 104b over an N1 or N2 interface. The 3GPP access 104a and the non-3GPP access 104b are configured to communicate with the UPF 106 over an N3 interface.

[0073] It should be appreciated that certain example embodiments described herein occur in the context of telecommunications networks, including but not limited to telecommunications networks that conform to and / or otherwise include aspects of fifth generation (5G) architecture. Figures 2 to 5 Various configurations and / or components of an example architecture of the communication network 100 are shown, but many other systems, system configurations, networks, network entities, and paths / protocols for communicating therein are contemplated and considered within the scope of the present disclosure.

[0074] Although the methods, devices / apparatus and computer program products / codes described herein are described in the context of a communication network including a fifth generation communication system, such as Figures 2 to 5 As shown and described above, the described methods, apparatus and computer program products may still be applied in a broader context within any suitable telecommunication network, network, standard and / or protocol. It will be understood that the described methods, apparatus and computer program products may also be applied to future networks and systems that have not yet been developed, as will be apparent to those skilled in the art from this disclosure.

[0075] Figure 6 is a diagram illustrating a process for traffic distribution for MA PDU sessions over 3GPP access and non-3GPP access, according to certain example embodiments.

[0076] At operation 1, a MA PDU session for ATSSS and L4S (e.g., enabling ASSSS and L4S) is established or an existing MA PDU session is modified for ATSSS and L4S. After the MA PDU session for ATSSS and L4S is established (or an existing MA PDU session is modified for ASSSS and L4S), UL traffic (e.g., PDU) received by UPF 106 from UE 102 is sent to AF 112, and DL data (e.g., PDU) destined for UE 102 is sent by AF 112 to UPF 106, as shown in operation 2. As shown in operation 3, UE 102 and UPF 106 determine how to separate application traffic for transmission over 3GPP and non-3GPP access. As shown in operations 4a and 4b, UL and DL traffic is sent between UE 102 and UPF 106 via 3GPP access and non-3GPP access.

[0077] According to certain embodiments provided herein, if the UPF 106 is performing ECN marking for L4S, then at corresponding operations 5a and 5b, congestion information for L4S is received from a node configured for 3GPP access (e.g., 3GPP access node 104a) and a node configured for non-3GPP access (e.g., non-3GPP access node 104b).

[0078] If the node configured for 3GPP and / or non-3GPP access is performing ECN marking for L4S, then at corresponding operations 6b and 6a, the node configured for 3GPP and / or non-3GPP access independently determines the ECN marking (without knowledge of the other access). UL and DL traffic (e.g., PDUs) with ECN marking for L4S are exchanged between the UE 102 and the UPF 106 over the 3GPP and non-3GPP accesses (e.g., via the node configured for 3GPP access and the node configured for non-3GPP access), as shown in operations 7a and 7b.

[0079] In accordance with certain embodiments, at operation 8a, based on congestion information for UL flows provided by nodes configured for 3GPP and non-3GPP access in operations 5a and / or 5b, the UPF 106 provides (via the SMF 110) updated ATSS rules to the UE 102 to separate UL traffic for transmission between the 3GPP access 104a and the non-3GPP access 104b.

[0080] According to certain embodiments, as shown in operation 8b, based on the at least one ATSS rule received in step 8a and the ECN markings for UL traffic received from the 3GPP and non-3GPP accesses in operations 6a and 6b, the UE 102 redistributes traffic (e.g., PDUs) for transmission between the 3GPP access 104a and the non-3GPP access 104b, and updates the ECN markings sent to applications and / or application hosts.

[0081] As shown in operation 8c, based on the congestion information provided at operations 5a and / or 5b, and / or the L4S ECN marking received from the access network, the UPF adjusts the distribution of traffic between 3GPP and non-3GPP accesses, and optionally updates the ECN marking sent to the application and / or application host.

[0082] Figure 7 and Figure 8 is a flow diagram of operations that may be performed by a user plane function (UPF) (eg, a device including, embodying, or implementing a UPF, such as device 10), according to certain example embodiments. Figure 7 including operations related to uplink communications, and Figure 8 including operations related to downlink communications, but it should be understood that a UPF (such as UPF 106) may perform Figure 7 and Figure 8 One or both of the operations.

[0083] At operation 700, the apparatus 10 embodied by a UPF (such as UPF 106) or the like may include components (such as processing circuitry 20, communication interface 40, memory 60, etc.) for receiving congestion information for low latency, low loss, and scalable throughput (L4S) via a node configured for non-3rd Generation Partnership Project (non-3GPP) access. For example, see Figure 6 Operation 5b in .

[0084] At operation 702, the apparatus 10 embodied by the UPF (such as the UPF 106, etc.) may include components (such as the processing circuit system 20, the communication interface 40, the memory 60, etc.) for receiving a protocol data unit (PDU) via at least two nodes configured for access, wherein the at least two nodes include nodes configured for non-3GPP access. For example, see Figure 6 At least operations 4a and 4b.

[0085] At operation 704, the apparatus 10 embodied by the UPF (such as the UPF 106, etc.) may include means (such as the processing circuit system 20, the communication interface 40, the memory 60, etc.) for updating the explicit congestion notification (ECN) information in the PDU based on at least the received congestion information for the L4S. See, e.g. Figure 6 Operation 8c. The congestion information for L4S may include a percentage of packets that the device is directed to use for L4S. According to some embodiments, the updating of the ECN information is also based on: congestion information for L4S received via at least another node of the at least two nodes. According to some embodiments, updating the ECN information is also based on: at least one rule or at least one setting provided by a session management function (SMF). In this regard, rules related to multi-access (MA) are sent to the UPF (from the SMF) and affect how PDUs are sent through multi-access. Parameter settings therein (such as guidance modes such as "load balancing", "priority-based", etc.) may affect the updating of the ECN information.

[0086] At operation 706, the apparatus 10 embodied by the UPF (such as the UPF 106) may include means (such as the communication interface 40) for sending a PDU including updated ECN information to the host. See, e.g. Figure 6 Operation 2 of FIG. 1 shows traffic sent to a host and / or application.

[0087] At operation 708, the apparatus 10 embodied by the UPF (such as the UPF 106, etc.) may include means (such as the processing circuit system 20, the communication interface 40, the memory 60, etc.) for updating access traffic steering, switching and splitting (ATSSS) rule information based on at least the received congestion information for L4S received via the non-3GPP access node. Figure 6 At least operation 8a. According to some embodiments, updating the ATSSS rule information is also based on: at least one rule or at least one setting provided by a session management function (SMF). In this regard, rules related to multiple access (MA) are sent to the UPF (from the SMF) and affect how the PDU is sent through multiple access. The parameter settings therein (such as "load balancing", "priority-based", etc.) may affect the update of the ASSSS rule information. The rule information is used by the SMF to update the ASSS rules sent to the UE 102, so that the UE 102 can update its traffic distribution accordingly.

[0088] At operation 710, the component 10 embodied by the UPF (such as UPF 106, etc.) may include a component (such as processing circuit system 20, communication interface 40, memory 60, etc.) for providing updated ATSSS rule information to a user equipment (UE). Figure 6At least operation 8a.

[0089] Go to Figure 8 At operation 800, the apparatus 10 embodied by the UPF (such as the UPF 106) may include components (such as the processing circuit system 20, the communication interface 40, the memory 60, etc.) for receiving congestion information for low latency, low loss, and scalable throughput (L4S) via a node configured for non-3rd Generation Partnership Project (non-3GPP) access. See, e.g. Figure 6 At least operation 5b in. According to some embodiments, the congestion information for L4S includes a percentage of packets that the device (such as UPF 106) is directed to use for L4S.

[0090] At operation 802, the apparatus 10 embodied by the UPF (such as the UPF 106, etc.) may include components (such as the processing circuit system 20, the communication interface 40, the memory 60, etc.) for adjusting the flow distribution of downlink protocol data units (PDUs) between at least two nodes configured for access based on at least congestion information for L4S, wherein the at least two nodes include nodes configured for non-3GPP access. For example, see Figure 6 At least operation 8c.

[0091] At operation 804, the apparatus 10 embodied by the UPF (such as the UPF 106, etc.) may include means (such as the processing circuit system 20, the communication interface 40, the memory 60, etc.) for updating explicit congestion notification (ECN) information in a downlink PDU based on at least the received congestion information and the adjustment of the traffic distribution for the L4S, wherein the downlink PDU including the updated ECN information is sent via at least one of the two nodes. See, for example, Figure 6 See also operations 4a and 4b regarding transmission of the PDU via at least one of the nodes configured for access. According to some embodiments, the updating of the ECN information is further based on: congestion information for L4S received via at least another node of the at least two nodes. For example, see Figure 6Operations 5a and 5b. In this regard, according to some embodiments, the updating of the ECN information includes combining congestion information for L4S received via at least two nodes to determine updated ECN information. For example, combining the congestion information for L4S can be performed via one or more of a harmonic mean, an arithmetic mean, or a weighted mean. According to some embodiments, updating the ECN information is also based on: at least one rule or at least one setting provided by a session management function (SMF). In this regard, rules related to multi-access (MA) are sent to the UPF (from the SMF) and affect how the PDU is sent through multi-access. The parameter settings therein, such as the boot mode of "load balancing", "priority-based", etc., may affect the updating of the ECN information.

[0092] Fig. 9 is a flow chart of operations that may be performed by apparatus 10 embodied by UE 102 according to certain embodiments. At operation 900, apparatus 10 embodied by a UE (such as UE 102) may include means (such as processing circuitry 20, communication interface 40, memory 60, etc.) for sending, in a request for at least establishment or modification of a multiple access (MA) (PDU) session, an indication that ATSSS and low latency, low loss, and scalable throughput (L4S) are enabled for at least nodes configured for non-3GPP access. See Figure 6 At least 1 operation.

[0093] At operation 902, the apparatus 10 embodied by a UE (such as UE 102, etc.) may include means (such as processing circuitry 20, communication interface 40, memory 60, etc.) for receiving at least one of the following: (a) access traffic steering, switching, splitting (ATSSS) rules for distributing traffic between at least two nodes configured for access, the at least two nodes including: at least one node configured for non-3rd Generation Partnership Project (non-3GPP) access, wherein the ATSSS rules are received from a session management function (SMF) and are based on information used for explicit congestion notification (ECN) information provided by a user plane function (UPF) - see Figure 6 At least operation 8a in (b) receiving ECN information in a protocol data unit (PDU) via at least one node configured for non-3GPP access (see Figure 6 At least operations 7a and 7b).

[0094] At operation 904, the apparatus 10 embodied by a UE (such as UE 102) may include a method for distributing traffic between at least two nodes based on at least one of the ATSS rules or the ECN information (see Figure 58b) of the at least one node (such as the processing circuit system 20, the communication interface 40, the memory 60, etc.). According to some embodiments, distributing the traffic is also based on one or more local conditions, including at least one of local congestion, network interface availability, signal loss conditions, or user preferences. According to some embodiments, distributing the traffic is also based on: ECN information received via at least another node of the at least two nodes (see, for example, regarding Figure 6 For example, UE 102, such as UE 102 having processing circuit system 20, may combine ECN information received via at least two nodes by one or more of a harmonic mean, an arithmetic mean, or a weighted mean.

[0095] At operation 906, the apparatus 10 embodied by a UE (such as UE 102, etc.) may include components (such as processing circuit system 20, communication interface 40, memory 60, etc.) for updating explicit congestion notification (ECN) information in a downlink PDU, wherein the ECN information in the downlink PDU indicates uplink congestion at one or more of the at least two nodes, and is based on one or more of the following items: (a) ECN information received via at least one node configured for non-3GPP access, or (b) traffic distribution performed by the apparatus, wherein the downlink PDU including the updated ECN information indicating uplink congestion is sent to the host. According to some embodiments, updating the ECN information is also based on one or more local conditions, including at least one of local congestion, network interface availability, signal loss condition, or user preference. According to some embodiments, updating the ECN information is also based on: ECN information received via at least another node of the at least two nodes. For example, UE 102 (such as with processing circuitry 20 ) may combine ECN information received via at least two nodes via one or more of a harmonic mean, an arithmetic mean, or a weighted mean.

[0096] The example embodiments disclosed herein provide many improvements to the network, such as improving the ability of UE 102 and / or UPF 106 to redistribute network traffic in a manner that reduces latency and packet loss. The example embodiments enable the network to redistribute traffic to any of at least two accesses in a multi-access session, including non-3GPP accesses, and also enable marking by access congestion information to enable further adjustment of traffic distribution.

[0097] Figures 6 to 9Message flows, call flows, or signal diagrams according to certain example embodiments of the present disclosure are shown. It will be understood that each block of the process can be implemented in various ways, such as hardware, firmware, processors, circuit systems, and / or other communication devices associated with the execution of software including one or more computer program instructions. For example, one or more of the above processes can be embodied by computer program instructions. In this regard, the computer program instructions embodying the above processes can be stored by the memory device 60 of the device 10 using an embodiment of the present disclosure, and executed by the processing circuit system 20. It should be understood that any such computer program instructions can be loaded onto a computer or other programmable device (e.g., hardware) to produce a machine so that the generated computer or other programmable device implements the functions specified in the figure. These computer program instructions can also be stored in a computer-readable memory, which can instruct a computer or other programmable device to operate in a specific manner so that the instructions stored in the computer-readable memory produce a manufactured product, the execution of which implements the functions specified in the figure. The computer program instructions can also be loaded onto a computer or other programmable device so that a series of operations are performed on the computer or other programmable device to produce a computer-implemented process, so that the instructions executed on the computer or other programmable device provide operations for implementing the functions specified in the figure.

[0098] Therefore, the blocks of the diagram and the flow chart support the combination of components for performing the specified functions and the combination of operations for performing the specified functions. It will also be understood that one or more blocks in the diagram and the combination of blocks in the diagram can be implemented by a special-purpose hardware computer system or a combination of special-purpose hardware and computer instructions that perform the specified functions.

[0099] Many modifications and other embodiments of the disclosure described herein will occur to those skilled in the art with the benefit of the teachings presented in the foregoing description and the associated drawings. Therefore, it should be understood that the disclosure is not limited to the specific embodiments disclosed, and modifications and other embodiments are intended to be included within the scope of the appended claims.

[0100] In addition, although the foregoing description and the associated drawings describe example embodiments in the context of certain example combinations of elements and / or functions, it should be understood that different combinations of elements and / or functions may be provided by alternative embodiments without departing from the scope of the appended claims. In this regard, for example, elements and / or functional combinations different from those explicitly described above are also contemplated, as may be set forth in certain appended claims. Although specific terms are employed herein, they are used only in a general and descriptive sense, and not for limiting purposes.

[0101] Although several variations have been described in detail above, other modifications or additions are possible. In addition to those features and / or variations set forth herein, additional features and / or variations may also be provided. In addition, the above implementations may be directed to various combinations and subcombinations of the disclosed features and / or combinations and subcombinations of several additional features disclosed above. Other embodiments may be within the scope of the following claims.

[0102] If desired, the different functions discussed herein may be performed in a different order and / or concurrently with each other. In addition, if desired, one or more of the above functions may be optional or combinable. Although various aspects of some embodiments are set forth in the independent claims, other aspects of some embodiments include other combinations of features from the embodiments and / or dependent claims with features of the independent claims, rather than just the combinations explicitly set forth in the claims. It should also be noted herein that although example embodiments are described above, these descriptions should not be considered restrictive. On the contrary, there may be various variations and modifications without departing from the scope of some embodiments as defined in the appended claims. Other embodiments may be within the scope of the following claims. The term "based on" includes "at least based on". Unless otherwise stated, the use of the phrase "such as" means "such as, for example".

[0103] Therefore, it should be emphasized again that the various embodiments described herein are presented only by way of illustrative examples and should not be interpreted as limiting the scope of the claims. For example, alternative embodiments may utilize different communication system configurations, user equipment configurations, base station configurations, identity request procedures, message protocols, and message formats than those described in the context of the above illustrative embodiments. These and many other alternative embodiments within the scope of the appended claims will be readily apparent to those skilled in the art.

[0104] As used herein, “at least one of: ” and “at least one of ” and similar expressions, where a list of two or more elements is connected by “and” or “or”, mean at least any one element, or at least any two or more elements, or at least all elements.

Claims

1. A device for a communication network, the device comprising: Means for receiving at least one of: (a) access traffic steering, switching, splitting (ATSSS) rules for distributing traffic for transmission to at least two nodes configured for access, the at least two nodes comprising: at least one node configured for non-3rd Generation Partnership Project (non-3GPP) access, wherein the ATSSS rules are received from a session management function (SMF) and are based on information used for explicit congestion notification (ECN) information provided by a user plane function (UPF), or (b) ECN information in a protocol data unit (PDU) received via the at least one node configured for non-3GPP access; and Means for distributing traffic for transmission to the at least two nodes based on at least one of the ATSSS rule or the ECN information.

2. The apparatus according to claim 1, further comprising: Components for updating explicit congestion notification (ECN) information in a downlink PDU, wherein the ECN information in the downlink PDU indicates uplink congestion at one or more of the at least two nodes, and based on one or more of: (a) the ECN information received via the at least one node configured for non-3GPP access, or (b) traffic distribution performed by the device, wherein the downlink PDU including the updated ECN information indicating the uplink congestion is sent to an application host.

3. The apparatus of claim 1 , wherein at least one of the following items is also based on one or more local conditions: (a) the distribution of the traffic, or (b) the updating of the ECN information, the one or more local conditions comprising at least one of the following items: local congestion, network interface availability, signal loss condition, or user preference.

4. The apparatus of claim 1 , wherein at least one of the following items is also based on ECN information received at at least another node of the at least two nodes: (a) the distribution of the traffic, or (b) the updating of the ECN information.

5. The apparatus of claim 4, wherein at least one of the following is further based on combining the ECN information received via the at least two nodes: (a) the distribution of the traffic, or (b) the updating of the ECN information.

6. The device according to any one of claims 1 to 5, further comprising: Component for sending, in a request for at least one of establishment or modification of a multiple access (MA) (PDU) session for transmission via said at least two nodes, an indication that ATSSS and low latency, low loss, and scalable throughput (L4S) are enabled for at least said node configured for non-3GPP access.

7. A device for a communication network, the device comprising: A User Plane Function (UPF) for a communications network, configured to perform: receiving congestion information for low latency, low loss, and scalable throughput (L4S) via a node configured for non-3rd Generation Partnership Project (non-3GPP) access; receiving, via at least two nodes configured for access, a protocol data unit (PDU), wherein the at least two nodes include the node configured for non-3GPP access; updating explicit congestion notification (ECN) information in the PDU based on at least the received congestion information for L4S; as well as The PDU including the updated ECN information is sent to a host.

8. The apparatus of claim 7, wherein the congestion information for L4S comprises: The device is directed to use a percentage of packets for L4S.

9. The apparatus of claim 7, wherein the updating of the ECN information is further based on congestion information for L4S received via at least another node of the at least two nodes.

10. The apparatus of claim 9, wherein the updating of the ECN information comprises: The congestion information for L4S received via the at least two nodes is combined to determine the updated ECN information.

11. The apparatus of claim 7, wherein the UPF is further configured to perform: updating access traffic steering, switching and splitting (ATSSS) rule information based on the received congestion information for L4S received at least via the non-3GPP access node; and The updated ATSSS rule information is provided to a user equipment (UE).

12. The apparatus according to any one of claims 7 to 11, wherein at least one of the updating of the ECN information or the updating of the ATSS rule information is also based on: at least one rule or at least one setting provided by a session management function (SMF).

13. An apparatus for a communication network, the apparatus comprising: A User Plane Function (UPF) for a communications network, configured to perform: receiving congestion information for low latency, low loss, and scalable throughput (L4S) via a node configured for non-3rd Generation Partnership Project (non-3GPP) access; as well as Based on the congestion information at least for L4S, traffic distribution of downlink protocol data units (PDUs) is adjusted between at least two nodes configured for access, wherein the at least two nodes include: the node configured for non-3GPP access.

14. The apparatus of claim 13, wherein the UPF is further configured to perform: Based on at least the received congestion information for L4S and the adjustment of the traffic distribution, explicit congestion notification (ECN) information in the downlink PDU is updated, wherein the downlink PDU including the updated ECN information is sent via at least one of the two nodes.

15. The apparatus of claim 13, wherein the congestion information for L4S comprises: The device is directed to use a percentage of packets for L4S.

16. The apparatus of claim 14, wherein the updating of the ECN information is further based on congestion information for L4S received via at least another node of the at least two nodes.

17. The apparatus of claim 16, wherein the updating of the ECN information comprises: The congestion information for L4S received via the at least two nodes is combined to determine the updated ECN information.

18. The apparatus according to any one of claims 14 to 17, wherein the updating of the ECN information is further based on: at least one rule or at least one setting provided by a session management function (SMF).

19. A method for communication, the method comprising: Receiving at least one of: (a) access traffic steering, switching, splitting (ATSSS) rules for distributing traffic between at least two nodes configured for access, the at least two nodes comprising: at least one node configured for non-third generation partnership project (non-3GPP) access, wherein the ATSSS rules are received from a session management function (SMF) and are based on information used for explicit congestion notification (ECN) information provided by a user plane function (UPF), or (b) ECN information in a protocol data unit (PDU) received via the at least one node configured for non-3GPP access; and Distribute traffic between the at least two nodes based on the at least one of the ATSSS rule or the ECN information.

20. The method according to claim 19, further comprising: updating explicit congestion notification (ECN) information in a downlink PDU, wherein the ECN information in the downlink PDU indicates uplink congestion at one or more of the at least two nodes, and based on one or more of: (a) the ECN information received via at least one node configured for non-3GPP access, or (b) traffic distribution, wherein the downlink PDU including the updated ECN information indicating the uplink congestion is sent to a host.

21. The method of claim 19, wherein at least one of the following items is also based on one or more local conditions: (a) the distribution of the traffic, or (b) the updating of the ECN information, the one or more local conditions comprising at least one of the following items: local congestion, network interface availability, signal loss conditions, or user preferences.

22. The method of claim 19, wherein at least one of the following is further based on ECN information received via at least another node of the at least two nodes: (a) the distribution of the traffic, or (b) the updating of the ECN information.

23. The method of claim 22, wherein at least one of the following is further based on combining the ECN information received via the at least two nodes: (a) the distribution of the traffic, or (b) the updating of the ECN information.

24. The method of claim 19, further comprising: In a request for at least one of establishment or modification of a multiple access (MA) (PDU) session for transmission via the at least two nodes, an indication is sent that ATSSS and low latency, low loss, and scalable throughput (L4S) are enabled for at least the node configured for non-3GPP access.

25. A method of a user plane function (UPF) of a communication network, the method comprising: receiving congestion information for low latency, low loss, and scalable throughput (L4S) via a node configured for non-3rd Generation Partnership Project (non-3GPP) access; as well as receiving, via at least two nodes configured for access, a protocol data unit (PDU), wherein the at least two nodes include the node configured for non-3GPP access; updating explicit congestion notification (ECN) information in the PDU based on at least the received congestion information for L4S; as well as The PDU including the updated ECN information is sent to a host.

26. The method of claim 25, wherein the congestion information for L4S comprises: UPF is directed to the percentage of packets used for L4S.

27. The method of claim 25, wherein the updating of the ECN information is further based on congestion information for L4S received via at least another node of the at least two nodes.

28. The method of claim 27, wherein the updating of the ECN information comprises: The congestion information for L4S received via the at least two nodes is combined to determine the updated ECN information.

29. The method of claim 25, wherein the method further comprises: updating access traffic steering, switching and splitting (ATSSS) rule information based on the received congestion information for L4S received at least via the non-3GPP access node; as well as The updated ATSSS rule information is provided to a user equipment (UE).

30. The method of claim 25, wherein at least one of the updating of the ECN information or the updating of the ATSS rule information is further based on: at least one rule or at least one setting provided by a session management function (SMF).

31. A method of a user plane function (UPF) of a communication network, the method comprising: receiving congestion information for low latency, low loss, and scalable throughput (L4S) via a node configured for non-3rd Generation Partnership Project (non-3GPP) access; as well as Based on the congestion information at least for L4S, traffic distribution of downlink protocol data units (PDUs) is adjusted between at least two nodes configured for access, wherein the at least two nodes include: the node configured for non-3GPP access.

32. The method of claim 31, wherein the method further comprises: Based on at least the received congestion information for L4S and the adjustment of the traffic distribution, explicit congestion notification (ECN) information in the downlink PDU is updated, wherein the downlink PDU including the updated ECN information is sent via at least one of the two nodes.

33. The method of claim 31 , wherein the congestion information for L4S comprises: The method is directed to a percentage of packets used for L4S.

34. The method of claim 32, wherein the updating of the ECN information is further based on congestion information for L4S received via at least another node of the at least two nodes.

35. The method of claim 34, wherein the updating of the ECN information comprises: The congestion information for L4S received via the at least two nodes is combined to determine the updated ECN information.

36. The method of claim 32, wherein the updating of the ECN information is further based on: at least one rule or at least one setting provided by a session management function (SMF).

37. A computer readable medium storing instructions which, when executed by at least one processor of a device, cause the device to perform the method according to any one of claims 19 to 39.

Images