Methods, apparatuses, and computer programs for traffic aggregation over 3GPP access and native non-3GPP access

Abstract

A terminal includes components for: sending a request to a 3GPP core network via a 3GPP access to establish or modify a data session, the request including an indication that the data session will support traffic aggregation, the traffic aggregation being the aggregation of traffic via the 3GPP access and traffic via native non-3GPP access; and an identifier for associating the data session via the 3GPP access with a tunnel via the native non-3GPP access; receiving from the 3GPP core network one or more rules for the aggregation of traffic via the 3GPP access and traffic via the native non-3GPP access, the one or more rules being associated with the identifier; and using the one or more rules to control the aggregation of uplink traffic from the terminal via the 3GPP access and via the native non-3GPP access to a traffic aggregator.

Description

[0001] Related applications This patent application claims priority to UK Patent Application No. 2317723.1 (filed on 20 November 2023), which is incorporated herein by reference in its entirety. Technical Field

[0002] This application relates to a method, apparatus, and computer program, and more particularly, but not exclusively, to a method, apparatus, and computer program for providing traffic aggregation. Background Technology

[0003] A communication system can be viewed as a facility capable of enabling communication between two or more entities (such as terminals or other nodes, or terminals and other nodes) or providing connectivity services to entities. Non-limiting examples of connectivity services provided by a communication system may include enhanced mobile broadband, ultra-reliable low-latency communication, mission-critical communication, massive Internet of Things (IoT) and multimedia services.

[0004] Communication systems and associated compatible terminals typically operate according to a given standard or specification that defines what the various network entities of the communication system are allowed to do and how they should be implemented. An example of a communication system is a so-called 5G or New Radio (NR) system (e.g., a communication system operating using 5G or NR radio access technology), which operates according to standards provided by the Third Generation Partnership Project (3GPP). Summary of the Invention

[0005] Some exemplary embodiments of this disclosure will be described with reference to certain aspects. These aspects are not intended to indicate key or essential features of the embodiments of this disclosure, nor are they intended to limit its scope. Other features, aspects, and elements will be apparent to those skilled in the art based on this disclosure.

[0006] According to one aspect, a terminal is provided, including at least one processor and at least one memory, the at least one memory storing instructions that, when executed by the at least one processor, cause the terminal to at least: send a request to a 3GPP core network via 3GPP access to establish or modify a data session, the request including an indication for indicating that the data session will support traffic aggregation via 3GPP access and traffic via native non-3GPP access, and an identifier used to associate the data session via 3GPP access with a tunnel via native non-3GPP access; receive from the 3GPP core network one or more rules for aggregating traffic via 3GPP access and traffic via native non-3GPP access, the one or more rules being associated with the identifier; and use the one or more rules to control the aggregation of uplink traffic from the terminal via 3GPP access and traffic via native non-3GPP access to a traffic aggregator.

[0007] The terminal can be enabled to execute one or more rules to control uplink traffic aggregation by routing uplink traffic to a traffic aggregator via one or both of 3GPP access and native non-3GPP access.

[0008] The terminal may be enabled to provide an identifier when performing the establishment of a tunnel to a traffic aggregator via native non-3GPP access. This identifier is used by the traffic aggregator to associate the tunnel with a data session established with the traffic aggregator via 3GPP access.

[0009] One or more rules may include one or more access traffic redirection, switching, or diversion rules, or one or more terminal rules.

[0010] A data session can be a protocol data unit session or a multiple access protocol data unit session.

[0011] The terminal can be enabled to perform session management functions from the 3GPP core network or to receive one or more rules from the user plane functions of the 3GPP core network.

[0012] One or more rules may depend on one or more network conditions and / or one or more traffic requirements.

[0013] One or more network conditions may include one or more link quality conditions.

[0014] A terminal may be made to perform updates to one or more rules depending on at least one of the following: one or more network conditions and / or one or more traffic requirements.

[0015] One or more rules in a rule may include one or more intent-driven rules.

[0016] The terminal may be enabled to perform a capability indication that provides the terminal with the ability to aggregate traffic between 3GPP access and native non-3GPP access.

[0017] According to another aspect, a terminal is provided, comprising: components for: sending a request to a 3GPP core network via 3GPP access to establish or modify a data session, the request including an indication for indicating that the data session will support traffic aggregation via 3GPP access and traffic via native non-3GPP access, and an identifier used to associate the data session via 3GPP access with a tunnel via native non-3GPP access; receiving from the 3GPP core network one or more rules for aggregating traffic via 3GPP access and traffic via native non-3GPP access, the one or more rules being associated with the identifier; and using the one or more rules to control the aggregation of uplink traffic from the terminal via 3GPP access and traffic via native non-3GPP access to a traffic aggregator.

[0018] According to another aspect, a method is provided, comprising: sending a request to a 3GPP core network via 3GPP access to establish or modify a data session, the request including an indication for indicating that the data session will support traffic aggregation via 3GPP access and traffic via native non-3GPP access, and an identifier used to associate the data session via 3GPP access with a tunnel via native non-3GPP access; receiving from the 3GPP core network one or more rules for aggregating traffic via 3GPP access and traffic via native non-3GPP access, the one or more rules being associated with the identifier; and using the one or more rules to control the aggregation of uplink traffic from a terminal via 3GPP access and traffic via native non-3GPP access to a traffic aggregator.

[0019] The method may include using one or more rules to control uplink traffic aggregation by routing uplink traffic to a traffic aggregator via one or both of 3GPP access and native non-3GPP access.

[0020] The method may include providing an identifier when establishing a tunnel to a traffic aggregator via native non-3GPP access, the identifier being used by the traffic aggregator to associate the tunnel with a data session established with the traffic aggregator via 3GPP access.

[0021] One or more rules may include one or more access traffic redirection, switching and offloading rules or one or more terminal rules.

[0022] A data session can be a protocol data unit session or a multiple access protocol data unit session.

[0023] The method may include receiving one or more rules from the session management function of the 3GPP core network or from the user plane function of the 3GPP core network.

[0024] One or more rules may depend on one or more network conditions and / or one or more traffic requirements.

[0025] One or more network conditions may include one or more link quality conditions.

[0026] The method may include updating one or more rules that depend on at least one of the following: one or more network conditions and / or one or more traffic requirements.

[0027] One or more rules in a rule may include one or more intent-driven rules.

[0028] The method may include providing a capability indication that the terminal supports traffic aggregation between 3GPP access and native non-3GPP access.

[0029] The method can be executed by the terminal.

[0030] According to one aspect, a traffic aggregator is provided, including at least one processor and at least one memory, the at least one memory storing instructions that, when executed by the at least one processor, cause the traffic aggregator to at least: receive an identifier for associating a) a data session between the traffic aggregator and a terminal via 3GPP access with b) a tunnel between the traffic aggregator and the terminal via native non-3GPP access; acquire one or more rules for the aggregation of traffic to the terminal via 3GPP access and traffic to the terminal via native non-3GPP access, the one or more rules being associated with the identifier; and use the one or more rules to control the aggregation of downlink traffic from the traffic aggregator to the terminal via 3GPP access and traffic to the terminal via native non-3GPP access.

[0031] Traffic aggregators can be enabled to execute one or more rules to control downlink traffic aggregation by routing downlink traffic to the endpoint via one or both of 3GPP access and native non-3GPP access.

[0032] Traffic aggregators can be made to receive identifiers from session management functions during the establishment of a data session with the endpoint.

[0033] Traffic aggregators can be enabled to perform tunneling between the traffic aggregator and user plane functions for traffic accessed via 3GPP between the traffic aggregator and the terminal.

[0034] Data sessions between traffic aggregators and terminals via 3GPP access may include tunnels between traffic aggregators and user plane functions.

[0035] The traffic aggregator can be made to receive connection requests from the user plane function to establish a tunnel between the traffic aggregator and the user plane function. The connection request includes an identifier.

[0036] One or more rules may include one or more multi-access rules or one or more multi-path proxy rules.

[0037] A data session can be a protocol data unit session or a multiple access protocol data unit session.

[0038] Traffic aggregators can be enabled to receive one or more rules from session management functions or user plane functions in the 3GPP core network.

[0039] One or more rules may depend on one or more network conditions and / or one or more traffic requirements.

[0040] One or more rules in a rule may include one or more intent-driven rules.

[0041] According to another aspect, a traffic aggregator is provided, comprising: components for: receiving an identifier for associating a) a data session between the traffic aggregator and a terminal via 3GPP access with b) a tunnel between the traffic aggregator and the terminal via native non-3GPP access; acquiring one or more rules for aggregating traffic to the terminal via 3GPP access and traffic to the terminal via native non-3GPP access, the one or more rules being associated with the identifier; and using the one or more rules to control the aggregation of downlink traffic from the traffic aggregator to the terminal via 3GPP access and traffic to the terminal via native non-3GPP access.

[0042] According to one aspect, a method is provided, comprising: receiving an identifier for associating a) a data session between a traffic aggregator and a terminal via 3GPP access with b) a tunnel between the traffic aggregator and the terminal via native non-3GPP access; obtaining one or more rules for the aggregation of traffic to the terminal via 3GPP access and traffic to the terminal via native non-3GPP access, the one or more rules being associated with the identifier; and using the one or more rules to control the aggregation of downlink traffic from the traffic aggregator to the terminal via 3GPP access and traffic to the terminal via native non-3GPP access.

[0043] The method may include using one or more rules to control downlink traffic aggregation by routing downlink traffic to the terminal via one or both of 3GPP access and native non-3GPP access.

[0044] The method may include receiving an identifier from a session management function during the establishment of a data session with the terminal.

[0045] The method may include using a tunnel between the traffic aggregator and the user plane function for traffic accessed via 3GPP between the traffic aggregator and the terminal.

[0046] Data sessions between traffic aggregators and terminals via 3GPP access may include tunnels between traffic aggregators and user plane functions.

[0047] The method may include receiving a connection request from a user plane function to establish a tunnel between the traffic aggregator and the user plane function, the connection request including an identifier.

[0048] One or more rules may include one or more multi-access rules or one or more multi-path proxy rules.

[0049] A data session can be a protocol data unit session or a multiple access protocol data unit session.

[0050] The method may include receiving one or more rules from the session management function or user plane function of the 3GPP core network.

[0051] One or more rules may depend on one or more network conditions and / or one or more traffic requirements.

[0052] One or more rules in a rule may include one or more intent-driven rules.

[0053] The method can be executed by the traffic aggregator.

[0054] According to another aspect, an apparatus is provided, comprising at least one processor and at least one memory, the at least one memory storing instructions for a user plane function, which, when executed by the at least one processor, cause the apparatus to at least: receive an address and identifier of a traffic aggregator and information regarding one or more rules for user plane traffic used for a data session, the identifier being used to associate a) a data session between the traffic aggregator and a terminal via 3GPP access and via the user plane function with b) a tunnel between the traffic aggregator and the terminal via native non-3GPP access; and use one or more rules to control the transmission of user plane traffic between the traffic aggregator and the terminal via 3GPP access and the user plane function.

[0055] According to another aspect, an apparatus is provided, including at least one processor and at least one memory, the at least one memory storing instructions for user plane functions, which, when executed by the at least one processor, cause the apparatus to at least: receive an address of a traffic aggregator, an identifier for a tunnel with the traffic aggregator, and information about one or more rules for user plane traffic used in a data session; send a tunnel request to the traffic aggregator using the address and identifier of the traffic aggregator to establish a tunnel; and use one or more rules to control the transmission of user plane traffic between the traffic aggregator via the tunnel and the terminal via 3GPP access and user plane functions.

[0056] The following examples can be used in conjunction with either of the two aspects described above. The apparatus can be configured to provide one or more rules to the terminal, which are used to control the aggregation of uplink traffic from the terminal via 3GPP access and via native non-3GPP access to the traffic aggregator.

[0057] The device can be made to provide one or more rules to the terminal using a performance measurement function protocol.

[0058] One or more rules provided to the terminal may depend on one or more network conditions and / or one or more traffic requirements.

[0059] One or more network conditions may include one or more link quality conditions.

[0060] The device can be configured to update one or more rules provided to the terminal based on one or more network conditions and / or one or more traffic requirements.

[0061] The device can be configured to provide one or more rules to a traffic aggregator to control the aggregation of downlink traffic from the traffic aggregator to the terminal via 3GPP access and via native non-3GPP access.

[0062] One or more rules provided to the traffic aggregator may depend on one or more network conditions and / or one or more traffic requirements.

[0063] One or more network conditions may include one or more link quality conditions.

[0064] The device can be configured to update one or more rules provided to a traffic aggregator based on one or more network conditions and / or one or more traffic requirements.

[0065] According to another aspect, an apparatus is provided, comprising: a user plane function configured to: receive an address of a traffic aggregator, an identifier for associating a) a data session between the traffic aggregator and a terminal via 3GPP access and via the user plane function with b) a tunnel between the traffic aggregator and the terminal via native non-3GPP access, and information on one or more rules regarding user plane traffic of the data session; and use one or more rules to control the transmission of user plane traffic between the traffic aggregator and the terminal via 3GPP access and via the user plane function.

[0066] According to another aspect, an apparatus is provided, including a user plane function configured to: receive an address of a traffic aggregator, an identifier for a tunnel with the traffic aggregator, and information about one or more rules for user plane traffic used in a data session; send a request for a tunnel to the traffic aggregator using the address and identifier of the traffic aggregator to establish a tunnel; and use one or more rules to control the transmission of user plane traffic between the traffic aggregator via the tunnel and the terminal via 3GPP access and user plane functions.

[0067] According to another aspect, a method is provided, comprising: receiving an address of a traffic aggregator, an identifier for associating a) a data session between the traffic aggregator and a terminal via 3GPP access and via user plane functions with b) a tunnel between the traffic aggregator and the terminal via native non-3GPP access, and information about one or more rules regarding user plane traffic of the data session; and using one or more rules to control the transmission of user plane traffic between the traffic aggregator and the terminal via 3GPP access and user plane functions.

[0068] According to another aspect, a method is provided, comprising: receiving an address of a traffic aggregator, an identifier for a tunnel with the traffic aggregator, and information about one or more rules for user plane traffic used in a data session; sending a request for the tunnel to the traffic aggregator using the address and identifier of the traffic aggregator to establish the tunnel; and using one or more rules to control the transmission of user plane traffic between the traffic aggregator via the tunnel and the terminal via 3GPP access and user plane functions.

[0069] The following examples can be used in conjunction with either of the two aspects mentioned above.

[0070] The method may include providing one or more rules to the terminal for controlling the aggregation of uplink traffic from the terminal via 3GPP access and via native non-3GPP access to the traffic aggregator.

[0071] The method may include providing one or more rules to the terminal using a performance measurement function protocol.

[0072] One or more rules provided to the terminal may depend on one or more network conditions and / or one or more traffic requirements.

[0073] One or more network conditions may include one or more link quality conditions.

[0074] The method may include updating one or more rules provided to the endpoint based on one or more network conditions and / or one or more traffic requirements.

[0075] The method may include providing one or more rules to a traffic aggregator to control the aggregation of downlink traffic from the traffic aggregator to the terminal via 3GPP access and via native non-3GPP access.

[0076] One or more rules provided to the traffic aggregator may depend on one or more network conditions and / or one or more traffic requirements.

[0077] One or more network conditions may include one or more link quality conditions.

[0078] The method may include updating one or more rules provided to the traffic aggregator based on one or more network conditions and / or one or more traffic requirements.

[0079] The method can be executed by user plane functions.

[0080] According to another aspect, a non-transient computer-readable medium is provided, including program instructions that, when executed by a device, cause the device to perform at least the method according to any of the foregoing aspects.

[0081] Many different embodiments have been described above. It should be understood that further embodiments can be provided by combining any two or more of the above embodiments.

[0082] List of abbreviations: 3GPP Third Generation Partnership Project 5GC 5G Core Network 5GS 5G System AMF access and mobility management functions Augmented Reality (AR) ATSSS access traffic redirection, switching, and offloading ATSSS-LLATSSS Low Level DL downlink DNN data network name ETH Ethereum FAR forwarding action rules FQDN (Fully Qualified Domain Name) HTTP Hypertext Transfer Protocol IP Internet Protocol MA Multi-Access MAR Multi-Access Rules MPDCCP Multipath Datagram Congestion Control Protocol MPQUIC Multipath QUIC MPTCP Multipath Transmission Control Protocol N3GPP (Non-3GPP) NAS Non-Access Layer NAT (Network Address Translation) NAT-PTNAT - Port Translation NG-RAN Next Generation Radio Access Network NR New Radio N3IWF Non-3GPP Interoperability Function PCF strategy control function PCO Protocol Configuration Options PDR Grouping Detection Rules PDU Protocol Data Unit PFCP (Packet Forwarding Control Protocol) PMF performance measurement function PSAPDU Session Anchor RAT wireless access type S-NSSAI Single Network Slice Selection Auxiliary Information SMF Session Management Function TCP Transmission Control Protocol TLS transport layer security TNGF Trusted Non-3GPP Gateway Function UDP User Datagram Protocol UE User Equipment UICC Universal Integrated Circuit Card UL uplink UPF User Plane Functions URR Usage Reporting Rules URSPUE routing policy W-AGF wired access gateway function. Attached Figure Description

[0083] The embodiments will now be described by way of example only, with reference to the accompanying drawings, in which: Figure 1 A schematic diagram of a 5G system is shown; Figure 2 A schematic diagram of a device for implementing a traffic aggregator or for implementing user plane functionality is shown. Figure 3A schematic diagram of the terminal is shown; Figure 4 A schematic diagram of a 5G system implementing ATSSS using NG-RAN and non-3GPP (via N3IWF) access is shown. Figure 5 A schematic diagram of the architecture for traffic aggregation between 3GPP and native non-3GPP access is shown. Figure 6 A signaling diagram of an example PDU session establishment process for traffic aggregation between 3GPP and native non-3GPP access is shown. Figure 7 This diagram illustrates the traffic processing rules for traffic aggregation between 3GPP access and native non-3GPP access when an MA PDU session has been established. Figure 8 A schematic diagram illustrates the traffic processing rules for traffic aggregation between 3GPP access and native non-3GPP access when a PDU session has been established. Figure 9 A first method of some embodiments is shown; Figure 10 A second method is shown in some embodiments; and Figure 11 A third method is shown in some embodiments. Detailed Implementation

[0084] Figure 1 A schematic diagram of a wireless communication system 100 is shown. In a wireless communication system, for example... Figure 1 The wireless communication system 100 shown provides wireless access to a terminal device 300 via at least one base station (not shown) or a similar wireless transmitting and / or receiving access node or access point. The terminal device 300 is equipped with suitable receiving and transmitting means to enable communication, such as wireless (e.g., radio) communication with an access network, or direct wireless or wired communication with other communication devices. The terminal device 300 (also referred to herein as terminal 300) can access carrier signals provided by the base station or access point and transmit and / or receive modulated communication on said carrier signals.

[0085] Figure 1 The wireless communication system 100 shown is a 5th generation wireless communication system (5GS). The wireless communication system 100 includes a terminal 300. The 5GS also includes a 5G radio access network (shown as NG-RAN 106) and a 5G core network (5GC) 104 including one or more network functions (NFs). The wireless communication system 100 is connected via an N6 interface to one or more application functions (AFs) 108 and one or more data networks (DNs) 110.

[0086] The NG-RAN 106 may include one or more base stations (also referred to as RAN nodes). One or more of the one or more base stations may include gNodeBs (gNBs). A gNB may include one or more distributed units (DUs) connected to one or more gNodeB (gNB) centralized units (CUs).

[0087] As described above, the 5GC 104 includes one or more network functions, including Access and Mobility Management Function (AMF) 112, Session Management Function (SMF) 114, Authentication Server Function (AUSF) 116, Unified Data Management (UDM) 118, User Plane Function (UPF) 120, Network Openness Function (NEF) 122, Policy Control Function (PCF) 125, and / or other NFs. The functions of the various network functions of the 5GC 104 are known to those skilled in the art and therefore will not be described in detail.

[0088] In wireless communication systems, for example Figure 1 The wireless communication system 100 shown provides wireless access to the 5GC 104 via at least one base station or similar wireless transmission and / or reception radio access network node or access point. In this document, the term "3GPP access" refers to the terminal 300's access to the 5GC via a 3GPP access network (e.g., NG-RAN 106 (e.g., a base station of the NG-RAN 106)). The terminal 300 may include receiving and transmitting means for implementing communication, such as data communication with the data network 110 via the wireless communication system 100 (e.g., via at least one base station of the NG-RAN and UPF 120 of the 5GC 104), or direct communication with other terminals via, for example, a sidelink. The terminal 300 may be configured to access a carrier provided by a base station or access point and to transmit and / or receive communication on that carrier.

[0089] The terminal 300 can access the data network (DN) 110 via a non-3GPP access network 103. In this document, the term "non-3GPP access" refers to the terminal 300's access to the 5GC via a non-3GPP access network. The terminal 300 can communicate with the 5GC via the non-3GPP access network 103 and an interoperability function IF 105 (e.g., sending control plane signaling to and / or receiving control plane signaling from the 5GC 104). The interoperability function 105 can be a non-3GPP interoperability function (N3IWF), a trusted non-3GPP gateway function (TNGF), or a wired access gateway function (W-AGF).

[0090] The terminal 300 can access the data network (DN) 110 via a native non-3GPP access network 130. In this document, "native non-3GPP access" refers to any access by the terminal 300 via the native non-3GPP access network 130, which provides IP connectivity to the terminal 300, wherein user plane traffic (e.g., data) is sent and / or received via the native non-3GPP access network 130 and bypasses the 3GPP core network (e.g., 5GC 104). In other words, the user plane traffic (e.g., data) does not traverse the user plane of the 3GPP core network (e.g., UPF 120 of the 5GC 104). Instead, user plane traffic sent by the terminal 300 via "native non-3GPP access" is not processed by the interworking function 105, but is forwarded by the native non-3GPP access network 130 to a multipath (MP) proxy 501. The MP proxy 501 described herein may also be referred to as a traffic aggregator or a multipath traffic aggregator.

[0091] Wi-Fi™ is one example of an access technology that supports "native non-3GPP access". However, any suitable access technology that supports "native non-3GPP access" can provide IP connectivity. In some embodiments, the native non-3GPP access network 130 can be, for example, a Wi-Fi network. The native non-3GPP access network 130 can be deployed in hotspots, hotels, residential environments, or office environments, where access to the native non-3GPP access network (e.g., a Wi-Fi network) can be open (hotels or restaurants may offer free Wi-Fi access), authorized using Wi-Fi-specific credentials (e.g., username and / or password or certificate), or authorized using 3GPP credentials (referred to as non-seamless Wi-Fi offloading in the 3GPP specification). 3GPP credentials (e.g., shared keys and the associated SUPI (Subscription Persistent Identifier) ​​or SUCI (Subscription Hidden Identifier) ​​of the terminal) are stored on the UICC. In any of these cases, user plane traffic does not traverse the 5GC 104 (e.g., the traffic is not sent to the UPF 120, and the traffic is not sent by the UPF 120), but can be sent directly to the data network 110 from the native non-3GPP access network (e.g., the Wi-Fi network). The data network 110 can be the Internet or an intranet.

[0092] Terminal 300 can support (i.e., be able to) register with the 5GC of the wireless communication system through one or more access points. When terminal 300 requests to register with the 5GC through an access point, terminal 300 generates and sends a registration request through one of the one or more access points to register terminal 300 with the 5GC 104 through an access point.

[0093] Some embodiments involve employing traffic aggregation to enable user plane traffic (e.g., data) to be transmitted via multiple accesses to provide an enhanced or more resilient end-user experience. As used herein, the term "traffic aggregation" refers to one or more of the following: traffic redirection (e.g., directing user plane traffic to different accesses among multiple accesses), switching user plane traffic between different accesses among multiple accesses, splitting user plane traffic among multiple accesses, and / or replicating user plane traffic for transmission over multiple accesses. Traffic aggregation can be provided in the UL direction and / or DL ​​direction. Some embodiments involve providing rules to the terminal 300 and / or MP agent 501 that control traffic aggregation in the UL and / or DL ​​directions, wherein at least one access is a native non-3GPP access, and at least one access is one or more of non-3GPP and / or 3GPP accesses.

[0094] Using traffic aggregation to enable user plane traffic to be sent via native non-3GPP access and via 3GPP access (and / or non-3GPP access) can provide end users with higher throughput and more reliable access. This can be done without additional cost, as any native non-3GPP access (e.g., Wi-Fi™ access) can be used (in offices, homes, airports, etc.). Data session continuity (e.g., PDU sessions or MA PDU sessions) can be provided between native non-3GPP access (e.g., Wi-Fi access) and 3GPP access to attempt to produce a seamless user experience. This can further provide resilience to the loss of data connectivity via either the 3GPP access or the native non-3GPP access.

[0095] In some examples, traffic aggregation can be performed on all user plane traffic or on specific user plane traffic. For instance, traffic aggregation can be performed only on business user plane traffic, such as user plane traffic for MS (Microsoft™) Teams.

[0096] In some embodiments, MP proxy 501 can perform traffic aggregation on user plane traffic from DN 110 that is to be sent to the terminal via the MP proxy. The user plane traffic can be transmitted to the terminal by MP proxy 501 via 3GPP access via data sessions (e.g., PDU sessions) and via at least one native non-3GPP access. In other words, traffic aggregation is used for downlink user plane traffic processed by the 3GPP core network and for user plane traffic bypassing the 3GPP core network via native non-3GPP access.

[0097] In some embodiments, the terminal may employ traffic aggregation for user plane traffic destined for DN 110 via MP Proxy 501. User plane traffic may be transmitted via 3GPP access via data sessions (e.g., PDU sessions) and via at least one native non-3GPP access. In other words, traffic aggregation is used for uplink user plane traffic processed by the 3GPP core network, and for user plane traffic bypassing the 3GPP core network via native non-3GPP access.

[0098] MP Agent 501 can reside in the core network. The MP agent can be located between the 3GPP core network (e.g., UPF120 of 5GC) and the N6 interface that connects the 3GPP core network to the data network (e.g., data network 110).

[0099] MP Proxy 501 can be responsible for segmenting downlink (DL) user plane traffic destined for terminal 300 (e.g., terminal 300) for transmission via a data session (e.g., a PDU session or an MA PDU session) through a 3GPP access (or a non-3GPP access) and a native non-3GPP access. MP Proxy 501 can be responsible for merging uplink (UL) user plane traffic (e.g., data) received from terminal 300 via a data session (e.g., a PDU session or an MA PDU session) through a 3GPP access (or a non-3GPP access) and a native non-3GPP access.

[0100] Traffic aggregation for UL user plane traffic is performed at terminal 300.

[0101] Terminal 300 and / or MP proxy can be configured to use a multipath protocol, such as MPTCP or MPQUIC. Multipath protocols can be used to control traffic aggregation about different paths provided by different access points from multiple access points.

[0102] Access traffic steering, handover, and offloading (or ATSSS) is described in Clause 5.32 of 3GPP TS 23.501 and allows user plane traffic steering (e.g., steering user plane traffic for transmission across multiple accesses) to be performed at a finer granularity than a PDU session, i.e., on the service data stream. The service data stream is defined in Clause 3.1 of TS 23.503. ATSSS introduces the concept of a multi-access PDU session (MA-PDU session), which is a PDU session in which user plane traffic (e.g., data) can be steering for transmission across more than one access (currently one 3GPP access and one non-3GPP access).

[0103] Figure 4 An example of using ATSSS rules is illustrated schematically. Figure 4In this configuration, an MA-PDU session has been established to connect terminal 300 to a UPF 120. The 447144PCT function can be MPTCP, MPQUIC, ATSSS-LL, etc. In some embodiments, redirection function 420 can also be implemented in the terminal. The redirection function 420 in terminal 300 is configured to redirect, switch, offload, and / or copy UL user plane traffic for transmission via both access points. The redirection function 403 in UPF 120 is configured to redirect, switch, offload, and / or copy DL user plane traffic for transmission via both access points. In some embodiments, ATSSS rules are configured for use with native non-3GPP access.

[0104] Therefore, for example, regarding control plane communication 400, terminal 300 can be configured to communicate with AMF 112 via 3GPP access (provided through a 3GPP access network (e.g., NG-RAN 106)) and also via non-3GPP access (provided through non-3GPP access networks 103 and N3IWF 105). AMF 112 can communicate with SMF 114, and SMF 114 can communicate with UPF 120 via a service-based interface.

[0105] Regarding user plane communication 402, terminal 300 can be configured to communicate with UPF 120 via NG-RAN 106, and also via non-3GPP access network 103 and N3IWF 105. UPF 120 can communicate with DN 110 via N6 interface.

[0106] Figure 5 The diagram schematically illustrates traffic aggregation of user plane traffic (e.g., data) between a 3GPP access and a native non-3GPP access. An MP agent 501 is deployed between 5GC 104 and the N6 interface connecting 5GC 104 to data network 110. Terminal 300 has a redirection function 420', as further described below. The redirection function 420' can be configured to control traffic aggregation via both accesses. In this example, the redirection function controls traffic aggregation in the UL.

[0107] In this example, regarding control plane 400, terminal 300 can be configured to communicate with AMF 112 via 3GPP access (provided through 3GPP access network 106 (e.g., NG-RAN 106)). Furthermore, AMF 112 can communicate with SMF 114, and SMF 114 can communicate with UPF 120 and multipath proxy function 501.

[0108] Regarding user plane 402, terminal 300 can be configured to send user plane traffic to UPF 120 via a 3GPP access network (e.g., NG-RAN 106) and receive user plane traffic from UPF 120 via a 3GPP access network (e.g., NG-RAN 106). UPF 120 can be configured to send or forward user plane traffic to multipath agent 501.

[0109] The multipath proxy (MP proxy) function 501 can also be referred to as a traffic aggregator. The MP proxy function 501 operates as a proxy for the server in the data network 110. The MP proxy function implements multipath traffic aggregation and performs ATSSS operations on user plane traffic (e.g., data) to be transmitted via at least one native non-3GPP access network 130 and at least one 3GPP access network 106.

[0110] MP Proxy 501 has a redirection function 403'. The redirection function 403' is configured to direct, switch, offload, and / or replicate DL user plane traffic for transmission via two access points. Therefore, the redirection function 403' of the multipath proxy function 501 or the traffic aggregator is configured to perform traffic aggregation for downlink user plane traffic (e.g., data) between 3GPP access and native non-3GPP access.

[0111] 3GPP access can use MA PDU sessions or PDU sessions. Native non-3GPP access can use IP connections based on, for example, MPQUIC, MPTCP, or another suitable multipath protocol.

[0112] Regarding user plane 402, terminal 300 can also send user plane traffic to MP proxy 501 via native non-3GPP access provided by native non-3GPP access network 130, and receive user plane traffic from MP proxy 501 and native non-3GPP access network 130.

[0113] Regarding user plane 402, MP agent 501 is also capable of sending user plane traffic to and receiving user plane traffic from data network DN 110.

[0114] The redirection function 420' of terminal 300 is configured to guide, switch, offload, and / or replicate UL user plane traffic for transmission to MP agent 501 via native non-3GPP access and via 3GPP access.

[0115] exist Figure 5 In this context, MP agent 501 is shown as a standalone entity, but in some embodiments it may be co-located with UPF 120 or with IF105 (e.g., N3IWF), for example by including steering function 403' in UPF 120.

[0116] Figure 6 An example of the process for enabling traffic aggregation between 3GPP and native non-3GPP access and establishing a secure data session between terminal 300 and MP agent 501 is shown.

[0117] At 601, terminal 300 sends a request to establish a PDU session via 3GPP access. The PDU session can be an MA PDU session or a PDU session. The request to establish a PDU session via 3GPP access may include an indication that the data session should support traffic aggregation between 3GPP access and native non-3GPP access. The request to establish a PDU session via 3GPP access may also include an indication that terminal 300 has the capability to support traffic aggregation between 3GPP access and native non-3GPP access. Terminal 300 may provide an identifier for a secure connection provided by the tunnels of 3GPP access and native non-3GPP access. The tunnels will be discussed in more detail later. Alternatively, SMF 114 may provide an identifier for a secure connection. The identifier for a secure connection is used to couple the tunnels of 3GPP access and native non-3GPP access in MP agent 501 (e.g., X1 and X2 tunnels discussed later). The identifier for a secure connection may be, for example, an association identifier, or, in the case of an MA PDU, the MA PDU session may provide the coupling between the tunnels of 3GPP access and native non-3GPP access.

[0118] although Figure 6 The diagram shows that terminal 300 sends a request to establish a PDU session at 601, but terminal 300 can send a request to modify the PDU session at 601 instead of a request to establish a PDU session.

[0119] The indication of the PDU session type, or information indicating the PDU session type, may be included in the request to establish a PDU session and / or the request to modify a PDU session. The PDU session type indicates the type of PDU session being requested or modified. However, in some embodiments, new types of PDU sessions may be established or modified (e.g., PDU session types as proposed in S2-2306692, which can be found at https: / / www.3gpp.org / ftp / tsg_sa / WG2_Arch / TSGS2_157_Berlin_2023-05 / docs / S2-2306692.zip).

[0120] A PDU session establishment request, including an indication that the PDU session should support traffic aggregation between 3GPP access and native non-3GPP access, is provided to the selected SMF. The UE's ability to support traffic aggregation between 3GPP access and native non-3GPP access can be provided to the SMF.

[0121] At 603, SMF 114 identifies the available MP proxies and also obtains the addresses of the available MP proxies (commonly referred to as MP proxies addresses). SMF 114 can select one of the available MP proxies (e.g., MP proxies 501). The MP proxies selected by SMF 114 can be available MP proxies co-located with UPF 120 on the data network 110 interface, or they can be independent MP proxies 501.

[0122] To identify available MP proxies, the SMF114 can use local configuration information stored in the SMF, UPF capabilities retrieved from the NRF140 or from the UPF120 itself, or the NRF (Network Repository Function), where the UPF120 with co-located MP proxy 501 and the standalone MP proxy 501 may be registered. This assumes that MP proxy 501 or a UPF120 with MP proxy capabilities can register with the NRF140, possibly indicating its capabilities (e.g., supported redirection functions such as MPTCP, MPQUIC) and / or its N6 address (allowing, for example, the SMF 114 to select, a standalone MP proxy closer to the UPF 120 selected for the PDU session). At 605, SMF 114 can obtain (e.g., acquire) information (e.g., security information) from MP agent 501 to construct agent information. SMF 114 can also establish a new context for the PDU session in MP agent 501 and can provide MP agent 501 with identifiers for secure connections, such as association identifiers from terminal 300 and UPF 120, along with relevant MA rules (for downlink direction) and an IP address assigned to terminal 300 for the PDU session accessing via 3GPP. The new context for the PDU session can be a placeholder for a 3GPP access tunnel to be created and a native non-3GPP access tunnel.

[0123] At 607, MP agent 501 knows that context establishment is complete. MP agent 501 stores identifiers and the IP address of terminal 300 for new secure connection requests to establish secure connections (e.g., tunnels X1 (from UPF 120) and X2 (from terminal 300)). MP agent 501 is now ready to process such new secure connection requests. Tunnel X1 is between UPF 120 and MP agent 501. Tunnel X2 is between terminal 300 and MP agent 501. MP agent 501 stores MA rules that control, for example, which one or more of tunnels X1 and X2 are used for user plane data. When a secure connection is established, the MA rules are used to control traffic aggregation.

[0124] At position 609, SMF 114 provides UPF 120 with the address and proxy information of MP proxy 501. SMF 114 can provide UPF 120 with the address and proxy information of MP proxy 501. This can be achieved by sending a message containing N4 rule updates. The message containing N4 rule updates can include the address and proxy information of MP proxy 501.

[0125] At 611, UPF 120 sends a secure connection request to MP agent 501 to establish a secure connection. The secure connection request includes at least some agent information. In other words, the secure connection request includes a subset of the information contained in the agent information received from SMF 114. Upon receiving the secure connection request including the agent information, MP agent 501 verifies that MP agent 501 has an existing context (as a result of 607), such as an identifier based on the existing context and the received secure connection request. Once the verification is successful, MP agent 501 can establish a secure connection between UPF 120 and MP agent 501 based on the agent information. MP agent 501 can generate and send a response to the secure connection request (e.g., a secure connection response) to UPF 120, indicating that the secure connection has been established. Both UPF 120 and MP agent 501 have created their tunnel endpoints, and the tunnel (X1) is ready to forward user plane traffic (e.g., data).

[0126] At 613, SMF 114 provides the terminal 300 with the address and proxy information of MP agent 501. SMF 114 can provide the address and proxy information of MP agent 501 to the terminal 300 by sending a message accepting a request to establish a PDU session (e.g., a PDU session establishment accept message). The message accepting the PDU session establishment request may include the address and proxy information of MP agent 501. The message accepting the PDU session establishment request indicates that the PDU session between the terminal 300 and the MP agent 501 via UPF 120 has been completed.

[0127] At 615, terminal 300 knows that the establishment of the PDU session (3GPP access provided via the 3GPP access network (e.g., NG_RAN 106)) has been completed, and terminal 300 stores the address and agent information of the MP agent received from SMF 114.

[0128] At 617, terminal 300 sends a secure connection request (e.g., a secure connection request) to MP agent 501 via native non-3GPP access network 103 to establish a secure connection with MP agent 501. The secure connection request includes at least some proxy information. In other words, the secure connection request includes a subset of the information included in the proxy information received from SMF 114. In some embodiments, terminal 300 may also send a secure connection request to a 3GPP access network (e.g., NG-RAN 106) to establish a secure connection via a data session on the 3GPP access of MP agent 501. Upon receiving the secure connection request including proxy information, MP agent 501 verifies that MP agent 501 has an existing context (as a result of 607), for example, based on an identifier of the existing context and the received secure connection request. Once verification is successful, MP agent 501 can establish a secure connection between terminal 300 and MP agent 501 based on the proxy information. MP agent 501 can generate and send a response to the secure connection request (e.g., a secure connection response) back to terminal 300, indicating that the secure connection has been established. Terminal 300 and MP agent 501 have both created their tunnel endpoints, and the tunnel (X2) is ready to forward data.

[0129] In some embodiments, if SMF 114 does not provide MA rules to MP agent 501 at 605, MP agent 501 may retrieve MA rules from SMF 114 after 617 by using the context identifier (created in 607) to complete the tunnel endpoint.

[0130] MP Proxy 501 knows two IP addresses used by Terminal 300 on native non-3GPP access and on 3GPP access, and both access methods can be used to bootstrap, switch, offload, and replicate traffic according to rules configured in Terminal 300 and MP Proxy 501. This will refer to Figure 7 and 8 The example shown will be described in more detail.

[0131] In some embodiments, the agent information includes at least one of the following: - Information indicating the lifetime of user plane traffic (e.g., data); - Access credentials, such as security keys or certificates used for authentication and encryption of user plane traffic; - A protocol used to establish a secure connection between terminal 300 and MP agent 501, such as MPTCP, MPQUIC, MPDCCP or similar protocols; - Indication of tunnel type (e.g., indication of the type of tunnel to be created): UDP, TCP, IP, or ETH; - MP proxy address: IP address, port number, FQDN; - Remote host address: IP address and port number, FQDN (optional); and - CorrID, used to associate a PDU session on a 3GPP access with a native non-3GPP access (optional).

[0132] In embodiments where UPF 120 and MP agent 501 are not co-located (e.g.) Figure 5 As shown), the 3GPP core network (e.g., SMF 114 or UPF 120 of 5GC104) or an external server may assign an IP address to terminal 300 during MA PDU session establishment or PDU session establishment. In some embodiments, MP agent 501 may be configured to use NAT and / or NAT-PT to replace the source IP address in user plane traffic received from terminal 300 with its own IP address before forwarding the user plane traffic to a remote host (e.g., via data network 110).

[0133] Uplink traffic (UL) from terminal 300 to data network 110 via 5GC 104 (e.g., UPF 120 and N6 interfaces) can be guided, switched, offloaded and / or replicated by terminal 300 between 3GPP access using MA PDU or PDU sessions and native non-3GPP access using available IP connections based on MPQUIC, MPTCP or another suitable multipath protocol, taking into account the rules provided to terminal 300 by 5GC 104 (e.g., SMF 114) and controlled by bootstrapping function 420.

[0134] In some embodiments, downlink (DL) user plane traffic can be bootstrapped, switched, offloaded, and / or replicated by MP agent 501 between 3GPP access using MA PDU or PDU sessions and native non-3GPP access using available IP connections based on MPQUIC, MPTCP, or another suitable multipath protocol, taking into account the rules provided to MP agent 501 by 5GC 104 (e.g., SMF 114).

[0135] refer to Figure 7 This illustration schematically demonstrates the setup of traffic processing rules for traffic aggregation between 3GPP access and native non-3GPP access. The example is based on an MA PDU session using ATSSS. In some embodiments, ATSSS is used with native non-3GPP access.

[0136] In this example, terminal 300 has requested the establishment of an MA PDU session. In some embodiments, this MA PDU session establishment request is a request to establish an MA PDU session on a 3GPP access. In other embodiments, the MA PDU session establishment request can be sent on a non-3GPP access. However, in some embodiments, the core network cannot establish an MA PDU session via a native non-3GPP access. The MA PDU session can be triggered by configured information. For example, URSP (UE Routing Policy) rules in the terminal can indicate that a PDU session of a given type should be established for a certain DNN / S-NSSAI. In this example, a MA PDU session is established. The MA PDU session is initially established without reserving explicit resources on the native non-3GPP access branch. The MA PDU session set up via the 3GPP access provides an MA PDU session 510 between terminal 300 and UPF 120. A secure tunnel 512 is provided between UPF 120 and MP agent 501. Data is transmitted between terminal 300 and MP agent 501 via MA PDU session 510 and secure tunnel 512. The settings for the MA PDU session can be found as follows: Figure 6 As discussed.

[0137] The establishment of an MA PDU session is triggered by an MA PDU session establishment request sent by terminal 300. The request may include an indication that the MA PDU session is used for traffic aggregation between 3GPP access and native non-3GPP access. This indication may use the defined access type – "Native Non-3GPP Access".

[0138] If terminal 300 is connected via a native non-3GPP access connection, terminal 300 establishes a secure (HTTP) tunnel 514 to MP proxy 501 to provide a secure MA PDU session tunnel. This can be described as follows: Figure 6 As described. Since PDU sessions cannot be established on native non-3GPP access, a secure tunnel 514 is set up to MP agent 501 via native non-3GPP access.

[0139] An identifier can be used to associate a MA PDU session on a 3GPP access with a secure tunnel on a native non-3GPP access. This identifier can be an association identifier. Terminal 300 may include this identifier in an MA PDU session request sent to the SMF. This identifier is used when establishing a secure tunnel to MP agent 501, thereby associating the MA PDU session on the 3GPP access with a secure tunnel on a native non-3GPP access. Alternatively, the SMF provides the identifier to the terminal during MA PDU session establishment. The terminal provides the identifier to the MA agent when establishing a secure HTTP tunnel.

[0140] SMF provides ATSSS rule 516 to the terminal. The ATSSS rule 516 can be provided via 3GPP access. The ATSSS rule 516 enables traffic aggregation between 3GPP and native non-3GPP access. The ATSSS rule 516 can be provided together with an indication that the ATSSS rule 516 is used for traffic aggregation between 3GPP and native non-3GPP access.

[0141] The SMF provides N4 rule 518 to the UPF 120 and MA rule 520 to the MP agent 501. If the MP agent and UPF are co-located, the MA rule can be part of the N4 rule. Identifiers used to associate MA PDU sessions on 3GPP access with secure tunnels on native non-3GPP access can be provided along with the MA rule.

[0142] The ATSSS rule 516 in terminal 300, the N4 rule in UPF120, and / or the MA rule 520 in MP agent 501 use identifiers to associate the MA PDU session on 3GPP access with the secure tunnel on native non-3GPP access with the MA PDU session 510 in UPF120 and the secure tunnel 514 in MP agent 501.

[0143] Compared to the current ATSSS framework, the processing of MA rule 520 is moved from the UPF to the MP agent at the tunnel termination point from / to terminal 300. MP agent 501 is where bootstrapping, switching, routing, and replication operations are applied to DL traffic destined for the terminal. MP agent 501 provides traffic aggregation according to the MA rule. The terminal is where bootstrapping, switching, routing, and replication operations are applied to UL traffic destined for MP agent 501. Terminal 300 performs traffic aggregation according to the ATSSS rule. The UPF is responsible for relaying user plane traffic between MA PDU session 510 and secure tunnel 512.

[0144] refer to Figure 8 This example schematically illustrates the traffic processing rules for traffic aggregation between 3GPP access and native non-3GPP access. The example is based on a PDU session (not a MA PDU session).

[0145] In this example, a PDU session has been established between terminal 300 and MP agent 501. In some embodiments, the PDU session between terminal 300 and MP agent 501 is established on a 3GPP access. In other embodiments, the PDU session has been established on a non-3GPP access. However, in some embodiments, the PDU session cannot be established via native non-3GPP access. The PDU session can be triggered by configured information. For example, URSP (UE Routing Policy) rules in terminal 300 can instruct that a PDU session should be established for a data network identified by a data network name (DNN) and / or a network slice identified by S-NSSAI. The PDU session is initially established without reserving explicit resources for native non-3GPP access. The PDU session established on the 3GPP access provides a PDU session 528 between terminal 300 and UPF 120. A secure tunnel 530 is provided between UPF 120 and MP agent 501. User plane traffic (e.g., data) communicates between terminal 300 and MP agent 501 via PDU session 528 and secure tunnel 530.

[0146] A PDU session establishment request from the terminal triggers the establishment of a PDU session. The PDU session establishment request may include an indication that the PDU session can be used for traffic aggregation between 3GPP access and native non-3GPP access. This indication can specify a defined access type – "native non-3GPP access". Alternatively, during PDU session establishment, the SMF may indicate that the PDU session can be used for traffic aggregation between 3GPP access and native non-3GPP access.

[0147] If the terminal is connected via a native non-3GPP access connection, the terminal 300 requests to establish a secure (HTTP) tunnel 532 to the MP proxy 501.

[0148] Traffic processing rules can be provided to terminal 300, allowing terminal 300 to route traffic sent from terminal 300 to MP agent 501 via PDU session 528 or via HTTP tunnel 532. These traffic processing rules for terminal 300 are associated with PDU session and HTTP tunnel.

[0149] Traffic processing rules can be provided to MP agent 501 to allow traffic sent from MP agent 501 to the terminal to be routed via PDU session 528 or via HTTP tunnel 532. These traffic processing rules for MP agent 501 are associated with PDU session and HTTP tunnel.

[0150] Because terminal 300 or SMF indicates during PDU session establishment that the PDU session can be used for traffic aggregation between 3GPP and native non-3GPP access, terminal rule 522 is provided to the terminal. This terminal rule defines how the terminal should handle traffic aggregation related to UL user plane traffic.

[0151] In some embodiments, the SMF may provide terminal rule 522 to terminal 300 using control plane signaling. The SMF may provide the terminal rule to terminal 300 via NAS signaling.

[0152] In other embodiments, the UPF may provide terminal rule 522 to terminal 300 via the user plane. The UPF may provide terminal rule 522 on the user plane using the PMF protocol (PMFP) or an enhanced version of that protocol. The PMFP may be used to transmit new and / or modified rules from the UPF to terminal 300. To support PMFP, the UPF supports PMFP request-response messaging on the user plane.

[0153] The terminal rules may be similar to or the same as the ATSSS rules discussed in relation to the previous example.

[0154] Alternatively or additionally, terminal rule 522 may be a dynamically generated rule. Terminal rule 522 may be generated in the UE and / or UPF. For example, terminal rule 522 may be dynamically generated based on one or more network-related conditions and / or one or more traffic requirements. For example, the one or more network-related conditions may be one or more conditions related to the quality of the radio link between the terminal and the 3GPP access network node (referred to herein as link quality conditions). The link quality conditions may be determined based on PMF measurements or measurements from TCP or QUIC. The quality of the link may be a measure of the quality and / or quantity of transmitted data received. Link quality conditions may be provided by one or more of the following parameters: bit error rate, round-trip time, packet loss rate, signal-to-noise ratio, and / or similar parameters. In some embodiments, terminal rule 522 may be dynamically generated based on input from an analysis function. Traffic requirements may be, for example, the required QoS (Quality of Service), the required data rate, or the required latency.

[0155] Similarly, since terminal 300 or SMF indicates during PDU session establishment that the PDU session can be used for traffic aggregation between 3GPP and native non-3GPP access, UPF rule 524 is provided to UPF and MP rule 526 is provided to agent 526. MP rule 526 defines how the MP agent should handle traffic aggregation related to DL traffic. The UPF rule may include rules for traffic between the UPF and the terminal, and rules for traffic between the UPF and MP agent 501.

[0156] The MP rule 526 may be similar to or the same as the MA rule discussed in relation to the previous example.

[0157] Alternatively or additionally, MP rule 526 may be a dynamically generated rule. The rule may be generated in the UE and / or UPF. For example, the rule may be dynamically generated based on one or more network-related conditions and / or one or more traffic requirements. For example, the one or more network-related conditions may be one or more link quality conditions. The link quality conditions may be determined based on PMF measurements or measurements from TCP or QUIC. In some embodiments, the rule may be dynamically generated based on input from analytics functions. Traffic requirements may, for example, be a required QoS (Quality of Service), a required data rate, or a required latency.

[0158] Compared to the current ATSSS framework, the processing of MP rule 526 has been moved from UPF to MP agent 501, where tunnels from / to terminal 300 are terminated.

[0159] MP Proxy 501 is where traffic aggregation (e.g., bootstrapping, switching, splitting, and replication operations) is performed on DL user plane traffic destined for Terminal 300. MP Proxy 501 performs traffic aggregation according to MP rule 526.

[0160] For DL ​​traffic, when MP agent 501 receives a data packet destined for terminal 300, MP agent 501 associates the data packet with a terminal-specific tunnel (e.g., tunnel 530 or tunnel 532). This terminal-specific tunnel is associated with MP rule 526, which is executed by MP agent 501. Based on MP rule 526, user plane traffic is forwarded to a local IP address assigned to terminal 300 by native non-3GPP access (via tunnel 532) or to an IP address assigned to terminal 300 by UPF and associated with the PDU session.

[0161] Terminal 300 performs traffic aggregation (e.g., performs bootstrapping, switching, splitting, and replication operations) on UL user plane traffic destined for MP agent 501. Terminal 300 performs traffic aggregation according to terminal rule 522.

[0162] When MP agent 501 receives UL user plane traffic (e.g., data) from terminal 300, MP agent 502 decapsulates the user plane traffic (e.g., data) and packets the user plane traffic (e.g., data) and sends it to the remote endpoint.

[0163] UPF is responsible for relaying user plane traffic between PDU session 528 and secure tunnel 532.

[0164] In some embodiments, with Figure 7 or Figure 8 One or more rules discussed in this context can be intent-driven rules. Intent-driven rules are rules that define a desired outcome or intent. This intent is supported by intent-supporting capabilities in the entity executing the rule (i.e., the terminal or MP agent). For example, these intent-supporting capabilities can be provided by AI / ML functions or heuristic models.

[0165] The intent-driven rules can define desired UE behavior and / or desired MP proxy behavior. An example of an intent-driven rule could be: "Use native non-3GPP access for Internet traffic, video streaming, or AR applications, and use 3GPP access for all other traffic."

[0166] PCF125 (see also) Figure 1 This defines intent-driven rules, where the traffic descriptor of a PCC (Policy and Charging Control) rule can reference an abstract traffic target. That is, the traffic target may not be identified by an explicit IP 5-tuple (consisting of source IP address, source port number, destination IP address, destination port number, and transport protocol). The abstract traffic target can correspond to a standard-defined application ID or a free-floating string.

[0167] Such PCC rules can be converted from SMF to ATSSS rules or similar rules. The ATSSS rules (or similar rules) can be sent to terminal 300. The ATSSS rules can reference abstract traffic targets represented by application IDs or free-floating strings.

[0168] Alternatively or additionally, intent-driven rules can be provided to the MP agent.

[0169] The interpretation of intent-driven rules can be performed in the endpoint and / or MP agent by determining the application ID (if applicable) or by associating ongoing traffic with one of the rules using AI / ML or heuristic models or other methods.

[0170] Figure 2An example of device 200 is shown. The device may include or implement an MP agent 501 or a traffic aggregator. Alternatively, the device may implement user plane functionality 120. Device 200 includes at least one memory (e.g., at least one random access memory (RAM) 211a and at least one read-only memory (ROM) 211b), at least one processor 212, 213, and an input / output interface 214. The at least one processor 212, 213 is coupled to RAM 211a and ROM 211b. The at least one processor 212, 213 may be configured to execute appropriate software code 215. The software code 215 may be stored in ROM 211b.

[0171] The software code 215 may include software code for the MP agent 501 or a traffic aggregator. In embodiments where the software code 215 includes software code for the MP agent 501 or a traffic aggregator, when the software code for the MP agent 501 or the traffic aggregator is executed by the at least one processor 212, 213, the apparatus 200 may perform traffic aggregation according to the aspects or examples described herein. The apparatus 200 may include one or more circuits or circuit systems (not shown) that may be configured to perform traffic aggregation according to the aspects or examples herein.

[0172] In some embodiments, software code 215 may include software code for UPF 120. When the software code for UPF 120 is executed by the at least one processor 212, 213, the apparatus 200 may perform the methods described herein, for example, regarding... Figure 11 The method described. The apparatus 200 may include one or more circuits or circuit systems (not shown) that may be configured to perform one or more of the aspects or examples described herein.

[0173] Figure 3 An example of terminal 300 is shown. Terminal 300 can be any communication device capable of sending and receiving wireless signals (including radio signals). Non-limiting examples of terminal 300 include user equipment, mobile station (MS) or mobile device (e.g., mobile phone or so-called "smartphone"), computer equipped with a wireless interface card or other wireless interface facility (e.g., USB dongle), personal data assistant (PDA) or tablet computer equipped with wireless communication capabilities, machine-type communication (MTC) device, cellular Internet of Things (CIoT) device, or any combination of these devices. Terminal 300 may, for example, provide signals for carrying communication. The communication can be one or more of voice, email, text messages, multimedia, data, machine data, etc.

[0174] Terminal 300 can receive signals via air or radio interface 307 through appropriate means for receiving radio signals, and can transmit signals via appropriate means for transmitting radio signals. Figure 3 In the diagram, the transceiver device is schematically represented by block 306. The transceiver device 306 can be provided, for example, via a radio section and an associated antenna arrangement. The antenna arrangement can be located inside or outside the mobile device. The antenna arrangement can include an antenna array comprising one or more antenna elements.

[0175] Terminal 300 may be provided with or include at least one processor 301, at least one memory (e.g., at least one ROM 302a and at least one RAM 302b), and other possible components 303 for software and hardware assistance in performing the tasks it is designed to perform, including controlling access to and communication with an access network of a wireless communication system (e.g., wireless communication system 100) and other terminals. The at least one processor 301 is coupled to RAM 302b and ROM 302a. The at least one processor 301 may be configured to execute appropriate software code 308. The software code 308 may, for example, allow traffic aggregation to be performed according to this aspect or the examples described herein. The software code 308 may be stored in ROM 302a. Terminal 300 may include one or more circuits or circuit systems (not shown) that may be configured to perform traffic aggregation according to this aspect or the examples described herein.

[0176] The processor, memory, and other related control devices can be housed on a suitable circuit board and / or in a chipset. This feature is indicated by reference numeral 304. The device may optionally have a user interface, such as a keyboard 305, a touch-sensitive screen or touchpad, or combinations thereof. Optionally, depending on the type of device, one or more of a display, speaker, and microphone may be provided.

[0177] refer to Figure 9 It illustrates methods of some embodiments.

[0178] This method can be executed by a device. The device can be a terminal.

[0179] The apparatus may include suitable components, such as a circuit system for providing the method.

[0180] Alternatively or additionally, the apparatus may include at least one processor and at least one memory, the memory storing instructions that, when executed by the at least one processor, cause the apparatus to provide at least the following methods.

[0181] Alternatively or additionally, the device may be as described regarding Figure 3 As discussed.

[0182] The method may be provided by computer program code or computer executable instructions.

[0183] The method may include, as referenced in A1, sending a request to the 3GPP core network via 3GPP access to establish or modify a data session. The request includes an indication that the data session will support traffic aggregation of traffic via 3GPP access and traffic via native non-3GPP access, and an identifier used to associate the data session via the 3GPP access with the tunnel of the native non-3GPP access.

[0184] The method may include, as referenced in A2, receiving from the 3GPP core network one or more rules for aggregating traffic accessed via 3GPP and traffic accessed via native non-3GPP, the one or more rules being associated with an identifier.

[0185] The method may include, as referenced in A3, using one or more rules to control the aggregation of uplink traffic from the terminal to the traffic aggregator via the 3GPP access and via native non-3GPP access.

[0186] It should be understood that Figure 9 The methods outlined herein can be modified to include any of the aforementioned features.

[0187] refer to Figure 10 It illustrates methods of some embodiments.

[0188] This method can be performed by a device, such as device 200. The device may include or implement a traffic aggregator or MP agent, such as MP agent 501.

[0189] The device may include suitable components, such as circuitry, for providing a traffic aggregator or MP agent.

[0190] Alternatively or additionally, the apparatus may include at least one processor and at least one memory storing instructions, which are instructions of software code for a traffic aggregator or MP agent, which, when executed by the at least one processor, cause the apparatus to provide at least the following methods.

[0191] Alternatively or additionally, the device may be as described regarding Figure 2 As discussed.

[0192] The method may be provided by computer program code or computer executable instructions.

[0193] The method may include, as referenced in B1, a receive identifier used to associate a) a data session between the traffic aggregator and the terminal via 3GPP access with b) a tunnel between the traffic aggregator and the terminal via native non-3GPP access.

[0194] The method may include, as referenced in B2, obtaining one or more rules for the aggregation of traffic to the terminal via 3GPP access and traffic to the terminal via native non-3GPP access, wherein the one or more rules are associated with an identifier.

[0195] The method may include, as referenced in B3, using one or more rules to control the aggregation of downlink traffic from the traffic aggregator to the terminal via 3GPP access and via native non-3GPP access.

[0196] It should be understood that Figure 10 The methods outlined herein can be modified to include any of the aforementioned features.

[0197] refer to Figure 11 It illustrates methods of some embodiments.

[0198] This method can be performed by a device. The device may include or implement user plane functionality.

[0199] The device may include suitable components, such as circuitry for providing the user plane functionality.

[0200] Alternatively or additionally, the apparatus may include at least one processor and at least one memory storing instructions, the instructions being instructions for user plane functions, which, when executed by the at least one processor, cause the apparatus to provide at least the following methods.

[0201] Alternatively or additionally, the device may be as described regarding Figure 2 As discussed.

[0202] The method may be provided by computer program code or computer executable instructions.

[0203] The method may include, as referenced in C1, the address of the traffic aggregator, an identifier for a secure connection to the traffic aggregator, and information about one or more rules for user plane traffic used in data sessions.

[0204] The method may include, as referenced in C2, sending a request for a secure connection to the traffic aggregator using the traffic aggregator's address and identifier to establish a secure connection.

[0205] The method may include, as referenced in C3, sending a secure connection request to the traffic aggregator using the traffic aggregator's address and identifier to establish a secure connection.

[0206] It should be understood that Figure 11 The methods outlined herein can be modified to include any of the aforementioned features.

[0207] It should be noted that although exemplary embodiments have been described above, several variations and modifications can be made to the disclosed solutions without departing from the scope of the invention.

[0208] Some example embodiments have been described with respect to wireless communication systems operating according to 3GPP standards for NR. However, some example embodiments of this disclosure may also be applied to wireless communication systems operating according to 3GPP standards for 5G-advanced or other future 3GPP standards (e.g., 3GPP standards for 6G and later versions).

[0209] In the example discussed, there is a native non-3GPP access provided via a native non-3GPP access network 130 and a 3GPP access provided via a 3GPP access network (e.g., NG-RAN 106). However, it should be understood that embodiments can be implemented in the following ways: One or more native non-3GPP accesses are provided via the corresponding native non-3GPP access network; and One or more of the following are provided: one or more 3GPP accesses provided via the corresponding 3GPP access network and / or one or more non-3GPP accesses provided via the corresponding non-3GPP access network.

[0210] Therefore, these examples can vary within the scope of the appended claims. Generally, some embodiments can be implemented using hardware or dedicated circuitry, software, logic, or any combination thereof. For example, some aspects can be implemented in hardware, while others can be implemented using firmware or software executable by a controller, microprocessor, or other computing device, although the embodiments are not limited thereto. While various embodiments may be illustrated and described as block diagrams, flowcharts, or using some other graphical representation, it should be understood that the blocks, apparatuses, systems, techniques, or methods described herein can be implemented as non-limiting examples using hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware or controllers or other computing devices, or some combination thereof.

[0211] These examples can be implemented by computer software stored in memory and executable by at least one data processor of the entity involved, or by hardware, or by a combination of software and hardware. It should also be noted in this regard that any process can represent program steps, or interconnected logic circuits, blocks and functions, or combinations of program steps and logic circuits, blocks and functions. Software can be stored on memory blocks such as memory chips or implemented within a processor, magnetic media such as hard disks or floppy disks, and optical media such as, for example, DVDs and their data variants, and CDs.

[0212] As used herein, the term "non-transient" refers to a limitation on the medium itself (i.e., tangible, not a signal) rather than a limitation on the persistence of data storage (e.g., RAM vs. ROM).

[0213] As used herein, "at least one of the following: " and "at least one of the following: " and similar wording, wherein the list of two or more elements is connected by "and" or "or", means any one of the elements, or any two or more of the elements, or at least all of the elements.

[0214] The memory can be of any type suitable for the local technical environment and can be implemented using any suitable data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory. The data processor can be of any type suitable for the local technical environment and, by way of non-limiting example, can include one or more of a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a gate-level circuit, and a processor based on a multi-core processor architecture.

[0215] Alternatively or additionally, some examples may be implemented using circuitry. The circuitry may be configured to perform one or more of the previously described functional and / or method steps. The circuitry may be located in the base station and / or terminal 300.

[0216] As used in this application, the term "circuit" may refer to one or more of the following: (a) Pure hardware circuits (e.g., analog and / or digital circuits); (b) A combination of hardware circuitry and software, for example: (i) A combination of analog and / or digital circuitry with software and / or firmware, and (ii) Any part of the hardware processor works in conjunction with software (including digital signal processors), software, and memory to enable the device (e.g., terminal 300 or base station) to perform the various functions previously described; and (c) Hardware circuitry and / or processors, such as microprocessors or a portion thereof, which require software (e.g. firmware) to operate, but may be absent when operation is not required.

[0217] This definition of "circuit" applies to all uses of the term "circuit" in this application, including in any claim. As a further example, as used herein, the term "circuit" also encompasses only hardware circuitry or a processor (or multiple processors), or a portion of hardware circuitry or a processor, and its accompanying software and / or firmware implementation. The term "circuit" also encompasses, for example, integrated devices. The term "circuit" further encompasses, for example and if applicable to a particular claim element, baseband integrated circuits or processor integrated circuits for mobile devices, or similar integrated circuits in servers, cellular network devices, or other computing or network devices.

[0218] The foregoing description provides a complete and informative description of some embodiments by way of exemplary and non-limiting examples. However, in view of the foregoing description, various modifications and adjustments may occur to those skilled in the art when read in conjunction with the accompanying drawings and the appended claims. Nevertheless, all such teaching modifications, and similar variations, will still fall within the scope defined in the appended claims.

Claims

1. A terminal, comprising: At least one processor; At least one memory stores instructions that, when executed by the at least one processor, cause the terminal to perform an operation, the operation including: Sending a request to the 3GPP core network via 3GPP access to establish or modify a data session, the request includes an indication that the data session will support traffic aggregation of traffic via the 3GPP access and traffic via native non-3GPP access, and an identifier used to associate the data session via the 3GPP access with a tunnel via the native non-3GPP access. Receive from the 3GPP core network one or more rules for aggregating traffic accessed via the 3GPP and traffic accessed via native non-3GPP, the one or more rules being associated with the identifier; and One or more of the rules are used to control the aggregation of uplink traffic from the terminal to the traffic aggregator via the 3GPP access and via the native non-3GPP access.

2. The terminal of claim 1, wherein the component is configured to control uplink traffic aggregation by using the one or more rules to route the uplink traffic to the traffic aggregator via one or both of the 3GPP access and native non-3GPP access.

3. The terminal according to claim 1 or 2, further comprising: A component for providing the identifier when establishing the tunnel to the traffic aggregator via the native non-3GPP access, the identifier being used by the traffic aggregator to associate the tunnel with a data session established with the traffic aggregator via the 3GPP access.

4. The terminal according to any one of claims 1 to 3, wherein the one or more rules include one or more access traffic redirection, switching, diversion rules or one or more terminal rules.

5. The terminal according to any one of claims 1 to 4, wherein the data session is a protocol data unit session or a multiple access protocol data unit session.

6. The terminal according to any one of claims 1 to 5, further comprising: A component for receiving one or more rules from the session management function of the 3GPP core network or from the user plane function of the 3GPP core network.

7. The terminal according to any one of claims 1 to 6, wherein the one or more rules depend on one or more network conditions and / or one or more traffic requirements.

8. The terminal according to claim 7, wherein the one or more network conditions include one or more link quality conditions.

9. The terminal according to claim 7 or 8, wherein updating the one or more rules depends on at least one of the following: the one or more network conditions; or the one or more traffic requirements.

10. The terminal according to any one of claims 1 to 9, wherein one or more of the rules comprise one or more intent-driven rules.

11. The terminal according to any one of claims 1 to 10, further comprising: A component for providing a capability indication of the terminal's ability to support traffic aggregation between 3GPP access and native non-3GPP access.

12. A traffic aggregator, comprising: A component for receiving an identifier, which is used to associate a) a data session between the traffic aggregator and the terminal via 3GPP access with b) a tunnel between the traffic aggregator and the terminal via native non-3GPP access. A component for acquiring one or more rules for aggregating traffic to the terminal via the 3GPP access and traffic to the terminal via the native non-3GPP access, the one or more rules being associated with the identifier; as well as A component for using one or more rules to control the aggregation of downlink traffic from the traffic aggregator to the terminal via the 3GPP access and via the native non-3GPP access.

13. The traffic aggregator of claim 12, wherein the component for controlling downlink traffic aggregation from the traffic aggregator to the terminal via the 3GPP access and via the native non-3GPP access using the one or more rules comprises: A component for routing the downlink traffic to the terminal via one or both of the 3GPP access and native non-3GPP access.

14. The traffic aggregator according to any one of claims 12 or 13, wherein the receiving component includes a component for receiving the identifier from a session management function during the establishment of the data session with the terminal.

15. The traffic aggregator according to any one of claims 12 to 14, wherein the data session between the traffic aggregator and the terminal via the 3GPP access includes a tunnel between the traffic aggregator and the user plane function.

16. The flow aggregator according to claim 15, further comprising: A component for receiving a connection request from the user plane function for establishing the tunnel between the traffic aggregator and the user plane function, the connection request including the identifier.

17. The traffic aggregator according to any one of claims 12 to 16, wherein the one or more rules include one or more multi-access rules or one or more multi-path proxy rules.

18. The traffic aggregator according to any one of claims 12 to 17, wherein the data session is a protocol data unit session or a multiple access protocol data unit session.

19. The flow aggregator according to any one of claims 12 to 18, further comprising: A component for receiving one or more rules from the session management function or user plane function of the 3GPP core network.

20. The traffic aggregator according to any one of claims 12 to 19, wherein the one or more rules depend on one or more network conditions and / or one or more traffic requirements.

21. The traffic aggregator according to any one of claims 12 to 20, wherein one or more of the rules comprise one or more intent-driven rules.

22. An apparatus comprising: The user plane functionality is configured as follows: Receive the address of the traffic aggregator, the identifier of the tunnel to the traffic aggregator, non-3GPP information, and one or more rules regarding user plane traffic used for data sessions; Send a request for a tunnel to the traffic aggregator using the address and the identifier of the traffic aggregator to establish the tunnel; as well as The one or more rules are used to control the transmission of user plane traffic between the traffic aggregator via the tunnel and the terminal via 3GPP access and the user plane function.

23. A method for a terminal, the method comprising: Sending a request to the 3GPP core network via 3GPP access to establish or modify a data session, the request includes an indication that the data session will support traffic aggregation of traffic via the 3GPP access and traffic via native non-3GPP access, and an identifier used to associate the data session via the 3GPP access with a tunnel via the native non-3GPP access. Receive one or more rules from the 3GPP core network for aggregating traffic accessed via the 3GPP and traffic accessed via native non-3GPP, the one or more rules being associated with the identifier; as well as One or more of the rules are used to control the aggregation of uplink traffic from the terminal to the traffic aggregator via the 3GPP access and via the native non-3GPP access.

24. The method of claim 23, wherein using the one or more rules to control uplink traffic aggregation includes routing the uplink traffic to the traffic aggregator via one or both of the 3GPP access and native non-3GPP access.

25. The method according to claim 23 or 24, further comprising: The identifier is provided when establishing the tunnel to the traffic aggregator via the native non-3GPP access, and the identifier is used by the traffic aggregator to associate the tunnel with a data session with the traffic aggregator established via the 3GPP access.

26. The method according to any one of claims 23 to 25, wherein the one or more rules include one or more access traffic redirection, switching, diversion rules or one or more terminal rules.

27. The method according to any one of claims 23 to 26, wherein the data session is a protocol data unit session or a multiple access protocol data unit session.

28. The method according to any one of claims 23 to 27, further comprising: The rules are received from the session management function of the 3GPP core network or from the user plane function of the 3GPP core network.

29. The method according to any one of claims 23 to 28, wherein the one or more rules depend on one or more network conditions and / or one or more traffic requirements.

30. The method of claim 29, wherein the one or more network conditions include one or more link quality conditions.

31. The method of claim 29 or 30, wherein updating the one or more rules depends on at least one of the following: the one or more network conditions; or the one or more traffic requirements.

32. The method according to any one of claims 23 to 31, wherein one or more of the rules comprise one or more intent-driven rules.

33. The method according to any one of claims 23 to 32, further comprising: Provides an indication of the terminal's ability to support traffic aggregation between 3GPP access and native non-3GPP access.

34. A method for a traffic aggregator, the method comprising: A receive identifier is used to associate a) a data session between the traffic aggregator and the terminal via 3GPP access with b) a tunnel between the traffic aggregator and the terminal via native non-3GPP access. Obtain one or more rules for aggregating traffic to the terminal via the 3GPP access and traffic to the terminal via the native non-3GPP access, the one or more rules being associated with the identifier; as well as The one or more rules are used to control the aggregation of downlink traffic from the traffic aggregator to the terminal via the 3GPP access and via the native non-3GPP access.

35. The method of claim 34, wherein using the one or more rules to control downlink traffic aggregation from the traffic aggregator to the terminal via the 3GPP access and via the native non-3GPP access comprises: A component for routing the downlink traffic to the terminal via one or both of the 3GPP access and native non-3GPP access.

36. The method of any one of claims 34 or 35, wherein receiving includes receiving the identifier from a session management function during the establishment of the data session with the terminal.

37. The method of any one of claims 34 to 36, wherein the data session between the traffic aggregator and the terminal via the 3GPP access includes a tunnel between the traffic aggregator and the user plane function.

38. The method of claim 37, further comprising: The user plane function receives a connection request for establishing the tunnel between the traffic aggregator and the user plane function, the connection request including the identifier.

39. The method according to any one of claims 34 to 38, wherein the one or more rules comprise one or more multi-access rules or one or more multi-path proxy rules.

40. The method according to any one of claims 34 to 39, wherein the data session is a protocol data unit session or a multiple access protocol data unit session.

41. The method according to any one of claims 34 to 40, further comprising: Receive one or more rules from the session management function or user plane function of the 3GPP core network.

42. The method according to any one of claims 34 to 41, wherein the one or more rules depend on one or more network conditions and / or one or more traffic requirements.

43. The method according to any one of claims 34 to 42, wherein one or more of the rules comprise one or more intent-driven rules.

44. A method for user plane functionality, the method comprising: Receive the address of the traffic aggregator, the identifier of the tunnel to the traffic aggregator, and information about one or more rules for user plane traffic used in the data session; Send a request for a tunnel to the traffic aggregator using the address and the identifier of the traffic aggregator to establish the tunnel; as well as The one or more rules are used to control the transmission of user plane traffic between the traffic aggregator via the tunnel and the terminal via 3GPP access and the user plane function.

45. A computer program comprising instructions, wherein when the computer program is executed by a terminal, the terminal is caused to perform the method according to any one of claims 23 to 33.

46. ​​A computer-readable medium comprising instructions that, when executed by at least one processor of a terminal, cause the terminal to perform the method according to any one of claims 23 to 33.

47. A computer program comprising instructions, wherein when the computer program is executed by a means, the means is caused to perform the method according to any one of claims 34 to 43.

48. A computer-readable medium comprising instructions that, when executed by at least one processor of a device, cause the device to perform the method according to any one of claims 34 to 43.

Images