Method, apparatus and computer program for traffic aggregation AVER 3GPP access and native non-3GPP access

Abstract

A terminal comprising: means for: sending, to a 3GPP core network over 3GPP access, a request to establish or modify a data session, the request comprising an indication that indicates that the data session is to support traffic aggregation of traffic via the 3GPP access and traffic via a native non-3GPP access, and an identifier which is used to associate 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 aggregation of uplink traffic from the terminal to a traffic aggregator via the 3GPP access and via the native non-3GPP access.

Description

[0001] METHOD, APPARATUS AND COMPUTER PROGRAM FOR TRAFFIC AGGREGATION AVER 3GPP ACCESS AND NATIVE NON-3GPP ACCESS

[0002] Related Applications

[0003] This patent application claims the benefit of priority of United Kingdom Patent Application No, 2317723.1 filed November 20, 2023, which is hereby incorporated by reference as if reproduced in its entirety.

[0004] Field

[0005] The present application relates to a method, apparatus, and computer program and in particular but not exclusively to methods, apparatus and computer programs for providing traffic aggregation.

[0006] Background

[0007] A communication system can be seen as a facility that enables communications between two or more entities, such as terminals or other nodes or terminals and other nodes or provides connected services to entities. Non-limiting examples of connected services provided by the communications system may comprise enhanced mobile broadband, ultra-reliable low latency communications, mission-critical communications, massive internet of things (loT), and multimedia services.

[0008] A communication system and associated compatible terminals typically operate in accordance with a given standard or specification which sets out what various network entities of the communication system are permitted to do and how that should be achieved. Examples of communication systems are so called 5G or New Radio (NR) systems (e.g., communication systems operating using 5G or NR radio access technology) operating in accordance with standards provided by the 3rd Generation Partnership Project (3GPP).

[0009] Summary

[0010] Some example embodiments of this disclosure will be described with respect 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 be used to limit the scope of thereof. Other features, aspects, and elements will be readily apparent to a person skilled in the art in view of this disclosure.

[0011] According to an aspect, there is provided a terminal comprising at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the terminal at least to perform: sending, to a 3GPP core network over 3GPP access, a request to establish or modify a data session, the request comprising an indication that indicates that the data session is to support traffic aggregation of traffic via the 3GPP access and traffic via a native non-3GPP access, and an identifier which is used to associate the data session via the 3GPP access with a tunnel via the native non-3GPP access; receiving, from the 3 GPP core network, one or more rules for the aggregation of traffic via the 3 GPP 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 aggregation of uplink traffic from the terminal to a traffic aggregator via the 3GPP access and via the native non-3GPP access. The terminal may be caused to perform using the one or more rules to control traffic aggregation of uplink traffic by routing the uplink traffic to the traffic aggregator via one or both of the 3 GPP access and native non-3GPP access.

[0012] The terminal may be caused to perform providing the identifier when establishing the tunnel to the traffic aggregator via the native non-3GPP access, said identifier being used by the traffic aggregator to associate the tunnel with the data session with the traffic aggregator established via the 3GPP access.

[0013] The one or more rules comprise one or more access traffic steering, switching, splitting rules or one or more terminal rules.

[0014] The data session may be a protocol data unit session or a multi-access protocol data unit session.

[0015] The terminal may be caused to perform receiving the one or more rules from a session management function of the 3 GPP core network or from a user plane function of the 3 GPP core network.

[0016] The one or more rules may be dependent on one or more network conditions and / or one or more traffic requirements.

[0017] The one or more network conditions may comprise one or more of link quality conditions. The terminal may be caused to perform updating the one or more rules dependent on the one or more network conditions and / or the one or more traffic requirements.

[0018] One or more of the rules may comprise one or more intent driven rules.

[0019] The terminal may be caused to perform providing a capability indication of a capability of the terminal to support traffic aggregation between the 3 GPP access and native non-3GPP access.

[0020] According to another aspect, there is provided a terminal comprising: means for: sending, to a 3GPP core network over 3GPP access, a request to establish or modify a data session , the request comprising an indication that indicates that the data session is to support traffic aggregation of traffic via the 3 GPP access and traffic via a native non-3GPP access, and an identifier which is used to associate the data session via the 3GPP access with a tunnel via the native non-3GPP access; receiving, from the 3 GPP core network, one or more rules for the aggregation of traffic via the 3 GPP 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 aggregation of uplink traffic from the terminal to a traffic aggregator via the 3 GPP access and via the native non-3GPP access.

[0021] According to another aspect, there is provided a method comprising: sending, to a 3GPP core network over 3GPP access, a request to establish or modify a data session, the request comprising an indication that indicates that the data session is to support traffic aggregation of traffic via the 3 GPP access and traffic via a native non-3GPP access, and an identifier which is used to associate the data session via the 3GPP access with a tunnel via the native non-3GPP access; receiving, from the 3 GPP core network, one or more rules for the aggregation of traffic via the 3 GPP 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 aggregation of uplink traffic from a terminal to a traffic aggregator via the 3 GPP access and via the native non-3GPP access.

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

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

[0024] The one or more rules comprise one or more access traffic steering, switching, and splitting rules or one or more terminal rules.

[0025] The data session may be a protocol data unit session or a multi-access protocol data unit session.

[0026] The method may comprise receiving the one or more rules from a session management function of the 3 GPP core network or from a user plane function of the 3 GPP core network. The one or more rules may be dependent on one or more network conditions and / or one or more traffic requirements.

[0027] The one or more network conditions may comprise one or more of link quality conditions. The method may comprise updating the one or more rules dependent on the one or more network conditions and / or the one or more traffic requirements.

[0028] One or more of the rules may comprise one or more intent driven rules.

[0029] The method may comprise providing a capability indication of a capability of the terminal to support traffic aggregation between the 3 GPP access and native non-3GPP access.

[0030] The method may be performed by the terminal.

[0031] According to an aspect, there is provided a traffic aggregator comprising at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the traffic aggregator at least to perform: receiving an identifier which is used to associate a) a data session between the traffic aggregator and a terminal via a 3GPP access with b) a tunnel between the traffic aggregator and the terminal via a native non- 3 GPP access; obtaining one or more rules for the aggregation of traffic to the terminal via the 3 GPP access and traffic to the terminal 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 aggregation of downlink traffic from the traffic aggregator to the terminal via the 3 GPP access and via the native non-3GPP access.

[0032] The traffic aggregator may be caused to perform using the one or more rules to control traffic aggregation of downlink traffic by routing the downlink traffic to the terminal via one or both of the 3 GPP access and native non-3GPP access.

[0033] The traffic aggregator may be caused to perform receiving from a session management function the identifier during a setting up of the data session with the terminal.,

[0034] The traffic aggregator may be caused to perform using a tunnel between the traffic aggregator and a user plane function for traffic between the traffic aggregator and the terminal via the 3GPP access.

[0035] The data session between the traffic aggregator and the terminal via the 3 GPP access may comprise a tunnel between the traffic aggregator and a user plane function.

[0036] The traffic aggregator may be caused to perform receiving a connection request from the user plane function for setting up the tunnel between the traffic aggregator and the user plane function, the connection request comprising the identifier. The one or more rules may comprise one or more multi access rules or one or more multipath proxy rules.

[0037] The data session may be a protocol data unit session or a multi-access protocol data unit session.

[0038] The traffic aggregator may be caused to perform receiving the one or more rules from a session management function or a user plane function of the 3 GPP core network.

[0039] The one or more rules may be dependent on one or more network conditions and / or one or more traffic requirements.

[0040] One or more of the rules may comprise one or more intent driven rules.

[0041] According to another aspect, there is provided a traffic aggregator comprising: means for: receiving an identifier which is used to associate a) a data session between the traffic aggregator and a terminal via a 3 GPP access with b) a tunnel between the traffic aggregator and the terminal via a native non-3GPP access; obtaining one or more rules for the aggregation of traffic to the terminal via the 3 GPP access and traffic to the terminal 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 aggregation of downlink traffic from the traffic aggregator to the terminal via the 3GPP access and via the native non-3GPP access.

[0042] According to an aspect, there is provided a method comprising: receiving an identifier which is used to associate a) a data session between a traffic aggregator and a terminal via a 3GPP access with b) a tunnel between the traffic aggregator and the terminal via a native non- 3 GPP access; obtaining one or more rules for the aggregation of traffic to the terminal via the 3 GPP access and traffic to the terminal 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 aggregation of downlink traffic from the traffic aggregator to the terminal via the 3 GPP access and via the native non-3GPP access.

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

[0044] The method may comprise receiving from a session management function the identifier during a setting up of the data session with the terminal.

[0045] The method may comprise using a tunnel between the traffic aggregator and a user plane function for traffic between the traffic aggregator and the terminal via the 3 GPP access. The data session between the traffic aggregator and the terminal via the 3 GPP access may comprise a tunnel between the traffic aggregator and a user plane function.

[0046] The method may comprise receiving a connection request from the user plane function for setting up the tunnel between the traffic aggregator and the user plane function, the connection request comprising the identifier.

[0047] The one or more rules may comprise one or more multi access rules or one or more multipath proxy rules.

[0048] The data session may be a protocol data unit session or a multi-access protocol data unit session.

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

[0050] The one or more rules may be dependent on one or more network conditions and / or one or more traffic requirements.

[0051] One or more of the rules may comprise one or more intent driven rules.

[0052] The method may be performed by a traffic aggregator.

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

[0054] According to another aspect, there is provided an apparatus comprising at least one processor and at least one memory storing instructions of a user plane function that, when executed by the at least one processor, cause the apparatus at least to perform: receiving an address of a traffic aggregator, an identifier for a tunnel with a traffic aggregator, and information about one or more rules for user plane traffic of the data session; using the address of the traffic aggregator and the identifier to send a request for a tunnel to the traffic aggregator to establish the tunnel; and using the one or more rules to control sending of user plane traffic between the traffic aggregator via the tunnel and the terminal via a 3 GPP access and the user plane function.

[0055] The following examples may be used in conjunction with either of the preceding two aspects. The apparatus may be caused to perform providing to the terminal one or more rules for controlling traffic aggregation of uplink traffic from the terminal to the traffic aggregator via the 3GPP access and via a native non-3GPP access.

[0056] The apparatus may be caused to perform providing to the terminal the one or more rules using a performance measurement function protocol.

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

[0058] The one or more network conditions may comprise one or more of link quality conditions. The apparatus may be caused to perform updating the one or more rules provided to the terminal dependent on the one or more network conditions and / or the one or more traffic requirements.

[0059] The apparatus may be caused to perform providing to the traffic aggregator one or more rules for controlling traffic aggregation of downlink traffic from the traffic aggregator to the terminal via the 3GPP access and via a native non-3GPP access.

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

[0061] The one or more network conditions may comprise one or more of link quality conditions. The apparatus may be caused to perform updating the one or more rules provided to the traffic aggregator dependent on the one or more network conditions and / or the one or more traffic requirements.

[0062] According to another aspect, there is provided a provided an apparatus comprising: a user plane function configured for: receiving an address of a traffic aggregator, an identifier which is used to associate a) a data session between the traffic aggregator and a terminal via a 3 GPP access and via the user plane function with b) a tunnel between the traffic aggregator and the terminal via a native non-3GPP access, and information about one or more rules for user plane traffic of the data session; and using the one or more rules to control sending user plane traffic between the traffic aggregator and the terminal via the 3 GPP access and the user plane function. According to another aspect, there is provided a an apparatus comprising a user plane function configured for: receiving an address of a traffic aggregator, an identifier for a tunnel with a traffic aggregator, and information about one or more rules for user plane traffic of a data session; using the address of the traffic aggregator and the identifier to send a request for a tunnel to the traffic aggregator to establish the tunnel; and using the one or more rules to control sending of user plane traffic between the traffic aggregator via the tunnel and the terminal via a 3 GPP access and the user plane function.

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

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

[0065] The following examples may be used in conjunction with either of the preceding two aspects. The method may comprise providing to the terminal one or more rules for controlling traffic aggregation of uplink traffic from the terminal to the traffic aggregator via the 3 GPP access and via a native non-3GPP access.

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

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

[0068] The one or more network conditions may comprise one or more of link quality conditions. The method may comprise updating the one or more rules provided to the terminal dependent on the one or more network conditions and / or the one or more traffic requirements. The method may comprise providing to the traffic aggregator one or more rules for controlling traffic aggregation of downlink traffic from the traffic aggregator to the terminal via the 3 GPP access and via a native non-3GPP access.

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

[0070] The one or more network conditions may comprise one or more of link quality conditions. The method may comprise updating the one or more rules provided to the traffic aggregator dependent on the one or more network conditions and / or the one or more traffic requirements.

[0071] The method may be performed by a user plane function.

[0072] According to another aspect, there is provided a non-transitory computer readable medium comprising program instructions that, when executed by an apparatus, cause the apparatus to perform at least the method according to any of the preceding aspects.

[0073] In the above, many different embodiments have been described. It should be appreciated that further embodiments may be provided by the combination of any two or more of the embodiments described above.

[0074] List of abbreviations:

[0075] 3 GPP 3rdGeneration Partnership Project

[0076] 5GC 5G Core

[0077] 5GS 5G System

[0078] AMF Access and Mobility management function

[0079] AR Augmented Reality

[0080] ATSSS Access Traffic Steering, Switching, Splitting

[0081] ATSSS-LL ATSSS Lower Layer

[0082] DL Downlink

[0083] DNN Data Network Name

[0084] ETH Ethernet

[0085] FAR Forwarding Action Rule

[0086] FQDN Fully Qualified Domain Name

[0087] HTTP Hypertext Transfer Protocol

[0088] IP Internet Protocol MA Multi-Access

[0089] MAR Multi-Access Rule

[0090] MPDCCP Multipath Datagram Congestion Control Protocol

[0091] MPQUIC Multipath QUIC

[0092] MPTCP Multipath Transmission Control Protocol

[0093] N3GPP Non-3GPP

[0094] NAS Non-Access Stratum

[0095] NAT Network Address Translation

[0096] NAT -PT NAT - Port Translation

[0097] NG-RAN Next Generation Radio Access Network

[0098] NR New Radio

[0099] N3IWF Non-3GPP Interworking Function

[0100] PCF Policy Control Function

[0101] PCO Protocol Configuration Options

[0102] PDR Packet Detection Rule

[0103] PDU Protocol Data Unit

[0104] PF CP Packet Forwarding Control Protocol

[0105] PMF Performance Measurement Function

[0106] PSA PDU Session Anchor

[0107] RAT Radio Access Type

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

[0109] SMF Session Management Function

[0110] TCP Transmission Control Protocol

[0111] TLS Transport Layer Security

[0112] TNGF Trusted Non-3GPP Gateway Function

[0113] UDP User Datagram Protocol

[0114] UE User Equipment

[0115] UICC Universal Integrated Circuit Card

[0116] UL Uplink

[0117] UPF Use Plane Function

[0118] URR Usage Reporting Rules

[0119] URSP UE Route Selection Policy W-AGF Wireline Access Gateway Function

[0120] Description of Figures

[0121] Embodiments will now be described, by way of example only, with reference to the accompanying Figures in which:

[0122] Figure 1 shows a schematic representation of a 5G system;

[0123] Figure 2 shows a schematic representation of an apparatus for implementing a traffic aggregator or for implementing a user plane function;

[0124] Figure 3 shows a schematic representation of a terminal;

[0125] Figure 4 shows a schematic representation of 5G system implementing ATSSS using NG- RAN and non-3GPP (via N3IWF) accesses;

[0126] Figure 5 shows a schematic representation of architecture for traffic aggregation between 3 GPP and native non-3GPP access;

[0127] Figure 6 shows a signalling diagram representation of an example PDU session establishment procedure for traffic aggregation between 3 GPP and native non-3GPP access; Figure 7 shows a schematic representation of traffic handling rules for traffic aggregation between 3 GPP access and native non-3GPP access where a MA PDU session has been established;

[0128] Figure 8 shows a schematic representation of traffic handling rules for traffic aggregation between 3 GPP access and native non-3GPP access where a PDU session has been established;

[0129] Figure 9 shows a first method of some embodiments;

[0130] Figure 10 shows a second method of some embodiments; and

[0131] Figure 11 shows a third method of some embodiments.

[0132] Detailed description

[0133] Figure 1 shows a schematic representation of a wireless communication system 100. In a wireless communication system, such as the wireless communication system 100 shown in Figure 1, terminal devices 300 are provided wireless access via at least one base station (not shown) or similar wireless transmitting and / or receiving access node or access point. A terminal device 300 is provided with an appropriate receiving and transmitting apparatus for enabling communications, for example for enabling wireless (e.g., radio) communications with an access network or wireless or wired communications directly with other communication devices. The terminal device 300 (otherwise referred to as terminal 300 herein) may access a carrier signal provided by a base station or access point and transmit and / or receive communications modulated on the carrier signal.

[0134] The wireless communication system 100 shown in Figure 1 is a 5thgeneration wireless communication system (5GS). The wireless communication system 100 comprises a terminal 300. The 5GS also comprises a 5G radio access network (illustrated as a NG-RAN 106), a 5G core network (5GC) 104 comprising one or more network functions (NF). The wireless communication system 100 is connected to one or more application functions (AFs) 108, and one or more data networks (DNs) 110 via a N6 interface.

[0135] The NG-RAN 106 may comprise one or more base stations (otherwise referred to as RAN nodes). One or more of the base stations may comprise a gNodeB (gNB). A gNB may comprise one or more distributed units (DUs) connected to one or more gNodeB (gNB) centralized units (CUs).

[0136] As noted above, the 5GC 104 comprises one or more network functions, including an access and mobility management function (AMF) 112, a session management function (SMF) 114, an authentication server function (AUSF) 116, a unified data management (UDM) 118, a user plane function (UPF) 120, a network exposure function (NEF) 122, a policy control function (PCF) 125, and / or other NFs. The functionalities of the various network functions of the 5GC 104 are known to a person skilled in the art and hence are not described in detail. In a wireless communication system, such as the wireless communication system 100 shown in Figure 1, the terminal 300 is provided with wireless access to the 5GC 104 via at least one base station or similar wireless transmitting and / or receiving radio access network node or access point. In this document, the term “3GPP access” refers to an access of the terminal 300 to the 5GC via a 3GPP access network, for example the NG-RAN 106 (e.g., a base station of the NG-RAN 106). The terminal 300 may comprise a receiving and transmitting apparatus for enabling communications, for example enabling data communications with the data network 110 via the wireless communication system 100 (e.g., via at least one base station of the NG-RAN and the UPF 120 of the 5GC 104) or communications directly 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 transmit and / or receive communications on the carrier.

[0137] The terminal 300 can access the data networks (DNs) 110 via a non-3GPP access network 103. In this document, the term “non-3GPP access” refers to an access of the terminal 300 to the 5GC via a non-3GPP access network. The terminal 300 may communicate with the 5GC (e.g., send control plane signalling to and / or receive control plane signalling from the 5GC 104) via the non-3GPP access network 103 and an interworking function IF 105. The interworking function 105 may be a non-3GPP interworking function (NWIF), a Trusted Non-3GPP Gateway Function (TNGF) or a Wireline Access Gateway Function (W-AGF). The terminal 300 can access the data networks (DNs) 110 via a native non-3GPP access network 130. In this document, “native non-3GPP access” refers to any access of the terminal 300 via a native non-3GPP access network 130 that provides IP connectivity to the terminal 300 where 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 a terminal 300 over “native non-3GPP access” is not handled by an interworking function 105 but is forwarded by the native non-3GPP access network 130 to a multipath (MP) proxy 501. The MP proxy 501 as described herein can also be known as a traffic aggregator or multi-path traffic aggregator.

[0138] Wi-Fi™ is one example of access technology that supports “native non-3GPP access”. However, the access technology that supports the “native non-3GPP access” can be any suitable access that provides IP connectivity. In some embodiments, the native non-3GPP access network 130 may 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., Wi-Fi network) can be open (free Wi-Fi access can be provided by hotels or restaurants), authorized using Wi-Fi specific credentials (for example username and / or password or certificates) or authorized using 3GPP credentials (called Non-Seamless Wi-Fi Offload in 3GPP specifications). 3GPP credentials such as a shared key and the associated SUPI (Subscription Permanent Identifier) or SUCI (Subscription concealed Identifier) of a terminal are stored on the UICC. In any of these situations, 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 by the native non-3GPP access network (e.g., the Wi-Fi network) to the data network 110. The data network 110 may be the Internet or an Intranet. A terminal 300 can support (i.e., is capable of) registering with a 5GC of a wireless communication system over one or more accesses. When the terminal 300 requests registration with a 5GC over an access, the terminal 300 generates and sends a registration request over one of the one or more accesses to register the terminal 300 with the 5GC 104 over an access.

[0139] Some embodiments relate to employing traffic aggregation for user plane traffic (e.g., data) to send via multiple accesses to deliver an enhanced or more resilient end user experience. The term “traffic aggregation” as used in this document refers to one or more of traffic steering (e.g., steering user plane traffic to different accesses of multiple access), switching user plane traffic between different access of the multiple access, splitting user plane traffic between multiple accesses and / or duplicating user plane traffic for transmission over multiple accesses. Traffic aggregation may be provided in the UL direction and / or the DL direction. Some embodiments relate to the providing of rules to the terminal 300 and / or MP proxy 501 which control traffic aggregation in the UL and / or DL directions where at least one access is a native non-3GPP access and at least one access is one or more of a non-3GPP access and / or a 3GPP access.

[0140] Employing traffic aggregation for user plane traffic to be sent over native non-3GPP access and over 3GPP access (and / or non-3GPP access) may provide higher throughput and more reliable access for an end user of a terminal. This may be without additional costs as any native non-3GPP access (e.g., Wi-Fi™ access) (in the office, at home, airport, etc.) may be employed. Data session (e.g., PDU session or MA PDU session) continuity may be provided between native non-3GPP access (e.g., Wi-Fi access) and 3GPP access to attempt to produce a seamless user experience. This may further provide resilience to loss of a data connection over one of the 3 GPP access and the native non-3GPP access.

[0141] In some examples traffic aggregation can be carried out on all user plane traffic or for specific user plane traffic. For example, traffic aggregation may be carried out only on business user plane traffic such as user plane traffic of MS (Microsoft ™) Teams.

[0142] In some embodiments, the MP proxy 501 may employ traffic aggregation for user plane traffic from the DN 110 which is to be sent to the terminal via the MP proxy. The , wherein user plane traffic may be transmitted by the MP proxy 501 to the terminal over a data session (e.g., PDU session) via a 3GPP access and via at least one native non-3GPP access. In other words, traffic aggregation is employed for downlink user plane traffic that is handled by the 3GPP core network and for user plane traffic that by-passes the 3GPP core network via a native non 3GGP access.

[0143] In some embodiments, the terminal may employ traffic aggregation for user plane traffic to be sent to DN 110 via the MP proxy 501. The user plane traffic may be transmitted over the data session (e.g., PDU session) via a 3GPP access and via at least one native non- 3GPP access. In other words, traffic aggregation is employed for uplink user plane traffic that is handled by a 3 GPP core network and for user plane traffic that by-passes the 3 GPP core network via a native non 3GGP access.

[0144] The MP proxy 501 may reside in the core network. The MP proxy may be located between the 3GPP core network (e.g., the UPF 120 of 5GC) and the N6 interface that connects the 3 GPP core network to a data network (e.g., data network 110).

[0145] The MP proxy 501 may be responsible for splitting downlink (DL) user plane traffic that is destined for a terminal 300 (e.g., the terminal 300) for transmission over a data session (e.g., PDU session or MA PDU session) via one 3 GPP access (or one non-3GPP) and a native non-3GPP access. The MP proxy 501 may be responsible for merging uplink (UL) user plane traffic (e.g., data) received from a terminal 300 over a data session (e.g., a PDU session or a MA PDU session) via one 3 GPP access (or non-3GPP access) and the native non-3GPP access.

[0146] The traffic aggregation for UL user plane traffic is performed at the terminal 300.

[0147] The terminal 300 and / or the MP proxy may be configured to use multi-path protocols, such as MPTCP or MPQUIC. A multipath protocol may be used for controlling the traffic aggregation with respect to the different paths provided by the different accesses of the multiple accesses.

[0148] Access Traffic Steering, Switching and Splitting (or ATSSS) has been described in 3GPP TS 23.501 clause 5.32 and allows user plane traffic steering (e.g., steering of user plane traffic for transmission across multiple accesses) at a finer granularity than a PDU session, namely on service data flows. Service data flows are defined in TS 23.503 clause 3.1. ATSSS introduces the notion of Multi Access PDU session (MA-PDU session), a PDU session for which the user plane traffic (e.g., data) can be steered for transmission across more than one accesses (currently one 3GPP access and one non-3GPP access).

[0149] Figure 4 schematically shows an example where ATSSS rules are used. In Figure 4, a MA- PDU session has been established to connect a terminal 300 to one UPF 120 447144PCTfunctionality may be MPTCP, MPQUIC, ATSSS-LL or the like. In some embodiments a steering functionality 420 can also be implemented in the terminal. The steering functionality 420 in the terminal 300 is configured to steer, switch, split, and / or duplicate UL user plane traffic for transmission over the two accesses. The steering functionality 403 in the UPF 120 is configured to steer, switch, split, and / or duplicate DL user plane traffic for transmission over the two accesses. In some embodiments ATSSS rules are configured for use with native non-3GPP access.

[0150] Thus, for example with respect to control plane communication 400, the terminal 300 can be configured to communicate via 3 GPP access provided via a 3 GPP access network (e.g., NG-RAN 106) with the AMF 112, and also via the non-3GPP access provided via the non- 3GPP access network 103 and the N3IWF 105 with the AMF 112. The AMF 112 can communicate with the SMF 114, and the SMF 114 can communicate with the UPF 120 via service-based interfaces.

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

[0152] Figure 5 schematically illustrates traffic aggregation of user plane traffic (e.g., data) between a 3GPP access and a native non-3GPP access. The MP proxy 501 is deployed between the 5GC 104 and the N6 interface that connects the 5GC 104 to the data network 110. The terminal 300 has a steering functionality 420’ as further described below. The steering functionality 420’ may be configured to control the traffic aggregation over two accesses. In this example, the steering functionality controls the traffic aggregation in the UL.

[0153] In this example with respect to control plane 400 the terminal 300 can be configured to communicate via 3 GPP access provided via a 3 GPP access network 106 (e.g., NG-RAN 106) with the AMF 112. Additionally, the AMF 112 can communicate with the SMF 114, and the SMF 114 can communicate with the UPF 120 and a multi-path proxy function 501. With respect to the user plane 402 the terminal 300 can be configured to send user plane traffic via the 3GPP access network (e.g., NG-RAN 106) to the UPF 120 and receive via the 3GPP access network (e.g., NG-RAN 106) user plane traffic from the UPF 120. The UPF 120 may be configured to send or forward the user plane traffic to the multi-path proxy 501.

[0154] The multi path proxy (MP proxy) function 501 may alternatively be referred to as a traffic aggregator. The MP proxy function 501 operates as a proxy for servers in the data network 110. The MP proxy function implements multi-path traffic aggregation functions and performs ATSSS operations with respect to user plane traffic (e.g., data) to be transmitted over at least one native non-3GPP access network 130 and at least one 3 GPP access network 106.

[0155] The MP proxy 501 has a steering functionality 403’. The steering functionality 403’ is configured to steer, switch, split, and / or duplicate DL user plane traffic for transmission over the two accesses. Thus, the steering functionality 403’ of the multipath proxy function 501 or traffic aggregator is configured to perform traffic aggregation with respect to downlink user plane traffic (e.g., data) between the 3 GPP access and the native non-3GPP access.

[0156] The 3 GPP access may be using a MA PDU session or a PDU session. The native non- 3GPP access may be using IP connectivity based on, for example, MPQUIC, MPTCP, or another suitable multi-path protocol.

[0157] With respect to the user plane 402, the terminal 300 may also send user plane traffic to the MP proxy 501 via the native non-3GPP access provided by the native non-3GPP access network 130 and receive user plane traffic from the MP proxy 501 and the native non- 3GPP access network 130.

[0158] With respect to the user plane 402, the MP proxy 501 is also able to send user plane traffic to and receive user plane traffic from the data network DN 110.

[0159] The steering function 420’ of the terminal 300 is configured to steer, switch, split, and / or duplicate UL user plane traffic for transmission to the MP proxy 501 via the native non- 3 GPP access and via the 3 GPP access.

[0160] In Figure 5, the MP proxy 501 is shown as a standalone entity but in some embodiments can be collocated with the UPF 120 or with the IF 105 such as the N3IWF by, for example, including the steering functionality 403’ in a UPF 120.

[0161] Figure 6 shows one example of a procedure for enabling traffic aggregation between 3GPP and native non-3GPP access and establishment of secure data session between a terminal 300 and a MP proxy 501. At 601, the terminal 300 sends a request for establishment of a PDU Session over 3GPP access. The PDU session may be a MA PDU session or a PDU session. The request for establishment of a PDU session over 3GPP access may include an indication that indicates that the data session is to support traffic aggregation between the 3GPP access and native non-3GPP access. The request for establishment of a PDU session over 3GPP access may also include an indication that the terminal 300 has a capability to support 3GPP access and native non-3GPP access traffic aggregation. The terminal 300 may provide the identifier for secure connections provided by a tunnel of the 3 GPP access and a tunnel of the native non-3GPP access. The tunnels will be discussed in more detail later.

[0162] Alternatively, the SMF 114 may provide the identifier for secure connections. The identifier for secure connections is used to couple a tunnel of the 3GPP access and a tunnel of the native non-3GPP access (e.g. the XI and X2 tunnels discussed later) in the MP proxy 501 The identifier for secure connections may be for example, a correlation identifier or in the case of MA PDU, the MA PDU session may provide the coupling of the tunnel of the 3 GPP access and the tunnel of the native non-3GPP access.

[0163] Although Figure 6 shows the terminal 300 sending a request for establishment of a PDU session at 601, the terminal 300 may send a request for modification of the PDU session at 601 rather than a request for establishment of the PDU session.

[0164] An indication of a type of a PDU session or information indicating the type of PDU session may be included in the request for establishment of a PDU session and / or request for modification of a PDU session. A type of a PDU session indicates a type of PDU session that is being requested or modified. However, in some embodiments a new type of PDU session can be established or modified (for example the PDU session type as proposed in S2-2306692 (which can be found in https: / / www.3gpp.org / ftp / tsg_sa / WG2_Arch / TSGS2_157_Berlin_2023-05 / docs / S2- 2306692.zip).

[0165] The request for PDU session establishment that includes an indication that the PDU session is to support traffic aggregation between the 3GPP access and native non-3GPP access is provided to the selected SMF. The capability of the UE to support 3GPP access and native non-3GPP access traffic aggregation may be provided to the SMF.

[0166] At 603, the SMF 114 identifies available MP Proxies and furthermore obtains the address(es) of the available MP -Proxies (generally referred to a MP proxy addresses). The SMF 114 may select one of the available MP proxies (e.g., MP proxy 501). The MP proxy selected by the SMF 114 may be an available MP proxy that is co-located with the UPF 120 that interfaces the data network 110 or may be a standalone MP proxy 501.

[0167] To identify available MP Proxies, the SMF 114 may use local configuration information stored in the SMF, UPF capability retrieved from NRF 140 or from the UPF 120 itself or use the NRF (Network Repository Function) in which UPF 120 with co-located MP proxy 501 and stand-alone MP proxies 501 may have registered. This assumes that MP proxy 501 or UPF 120 with MP proxy capability can register onto NRF 140 possibly indicating its capabilities (such as supported steering functionalities, such as MPTCP, MPQUIC) and / or its N6 address (allowing e.g., the SMF 114 to select a stand-alone MP proxy close to the UPF 120 selected for a PDU Session)

[0168] At 605, the SMF 114 may get (e.g., obtain) information (e.g., security information) from the MP proxy 501 to build proxy information. The SMF 114 may also establish a new context for the PDU session in the MP proxy 501 and may provide the MP proxy 501 the identifiers for secure connections, e.g., the correlation identifier, from the terminal 300 and UPF 120 together with the related MA rules for the downlink direction and with an IP address allocated to the terminal 300 for the PDU session over the 3 GPP access. The newcontext for the PDU session may be a placeholder of the tunnel of the 3 GPP access and the tunnel of the native non-3GPP access tunnels to be created.

[0169] At 607, the MP proxy 501 is aware that establishment of the context has been completed. The MP proxy 501 stores the identifier(s) and the IP address of the terminal 300 for new requests for a secure connection to establish secure connections (e.g., tunnels XI (from the UPF 120) and X2 (from the terminal 300)). The MP proxy is now ready to process such new requests for a secure connection. The XI tunnel is between the UPF 120 and the MP proxy 501. The X2 tunnel is between the terminal 300 and the MP proxy 501. The MP proxy 501 stores MA rules which control, for example, which one or more of the XI and X2 tunnels are used for user plane data. The MA rules are used when the secure connections are established for controlling the traffic aggregation.

[0170] At 609, the SMF 114 provides the UPF 120 with an address of the MP proxy 501 and the proxy information. The SMF 114 may provide the UPF 120 with an address of the MP proxy 501 and the proxy information. This may be achieved by sending a message with a N4 rule update. The message that includes the N4 rule update may include the address of the MP proxy 501 and the proxy information.

[0171] At 611, the UPF 120 sends to the MP proxy 501, a request for a secure connection to establish a secure connection with the MP proxy 501. The request for a secure connection comprises at least some of the proxy information. In other words, the request for a secure connection comprises a subset of the information included in the proxy information received from the SMF 114. The MP proxy 501 having received the request for a secure connection comprising proxy information verifies that the MP proxy 501 has an existing context (as the result of 607), e.g., based on the identifiers of the existing context and the received request for a secure connection. Once the verification has passed, the MP proxy 501 can establish the secure connection between the UPF 120 and the MP proxy 501 based on the proxy information. The MP proxy 501 can generate and send a response to the request for a secure connection (e.g., a secure connection response) back to the UPF 120 indicating that the secure connection has been established. Both the UPF 120 and the MP proxy 501 have their tunnel endpoints created and the tunnel (XI) is ready to forward user plane traffic (e.g., data). At 613, the SMF 114 provides the terminal 300 with an address of the MP proxy 501 and the proxy information. The SMF 114 may provide the terminal 300 with an address of the MP proxy 501 and the proxy information by sending a message accepting the request for the PDU session establishment (e.g., a PDU session establishment accept message). The message accepting the request for the PDU session establishment may include the address of the MP proxy 501 and the proxy information. The message accepting the request for the PDU session establishment indicates the PDU session between the terminal 300 and the MP proxy 501 via the UPF 120 has been completed.

[0172] At 615, the terminal 300 is aware that establishment of the PDU session (over the 3GPP access provided via the 3 GPP access network (e.g., NG RAN 106) has been completed and the terminal 300 stores the address of the MP proxy and the proxy information received from SMF 114.

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

[0174] In some embodiments, if the SMF 114 did not provide MA Rules at 605 to the MP proxy 501, then the MP proxy 501 can retrieve MA Rules by using the identifier of the context (created in 607) from the SMF 114 after 617 to finalize tunnel endpoints.

[0175] The MP proxy 501 is aware of both IP addresses the terminal 300 is using over native non- 3 GPP access and over 3 GPP access and both accesses can be used to steer, switch, split and duplicate traffic according to the rules that are configured in the terminal 300 and in the MP proxy 501. This is described in more detail with reference to the examples shown in Figures 7 and 8.

[0176] In some embodiments the proxy information comprises at least one of the following:

[0177] - Information indicative of a lifetime of the user plane traffic (e.g., data);

[0178] - Access credentials like security keys or certificates to be used for authentication and encryption of user plane traffic;

[0179] - Protocol to be used to establish a secure connection between the terminal 300 and the MP proxy 501, for example: MPTCP, MPQUIC, MPDCCP, or the like;

[0180] - An indication of Tunnel type (e.g., an indication of a type of tunnel to be created): UDP, TCP, IP, or ETH;

[0181] - MP proxy address: IP address(es), port numbers, FQDNs;

[0182] - Remote host address: IP addresses and port numbers, FQDNs (optional); and

[0183] - Correlation Identifier (CorrlD) to correlate PDU session over 3 GPP access with native non-3GPP access (optional). In embodiments where the UPF 120 and MP proxy 501 are not collocated (such as shown in Figure 5), the 3GPP core network (e.g., SMF 114 or UPF 120 of the 5GC 104) or an external server may assign an IP address to the terminal 300 during MA PDU session establishment or during PDU session establishment. The MP proxy 501, in some embodiments, can be configured to use NAT and / or NAT -PT to replace the source IP address in user plane traffic received from the terminal 300 with its own IP address before forwarding user plane traffic to the remote host (e.g., over the data network 110).

[0184] The uplink traffic (UU) from the terminal 300 destined for the data network 110 via the 5GC 104 (e.g., the UPF 120 and the N6 interface) can be steered, switched, split, and / or duplicated by the terminal 300 between 3GPP access using the MA PDU or PDU session and the native non-3GPP access using available IP connectivity based on MPQUIC, MPTCP or another suitable multi-path protocol and considering rules that are provided to the terminal 300 by the 5GC 104 (e.g., the SMF 114) and controlled by the steering functionality 420.

[0185] In some embodiments the downlink (DL) user plane traffic can be steered, switched, split, and / or duplicated by the MP proxy 501 between 3GPP access using the MA PDU or PDU session and the native non-3GPP access using available IP connectivity based on MPQUIC, MPTCP or another suitable multi-path protocol and considering rules that are provided to the MP proxy 501 by the 5GC 104 (e.g., the SMF 114).

[0186] Reference is made to Figure 7 which schematically illustrates the setting up of traffic handling rules for traffic aggregation between 3GPP access and native non-3GPP access. This example is based on a MA PDU session with the use of the ATSSS. In some embodiments, ATSSS is used with the native non-3GPP access.

[0187] In this example, the terminal 300 has requested establishment of a MA PDU session. In some embodiments, this request for establishment of a MA PDU session is a request to establish a MA PDU session over the 3 GPP access. In other embodiments, the request for establishment of a MA PDU session may be sent over the non-3GPP access. However, in some embodiments, the core network is not able to establish a MA PDU session via the native non-3GPP access. The MA PDU session may be triggered by configured information. For example, URSP (UE route selection policy) rules in the terminal can indicate that for a certain DNN / S-NSSAI a give type of PDU session is to be established. In this example a MA PDU session is established. The MA PDU session is initially established with no explicit resources reserved on the native non-3GPP access leg. The MA PDU session set via the 3GPP access provides a MA PDU session 510 between the terminal 300 and the UPF 120. A secure tunnel 512 is provided between the UPF 120 and the MP proxy 501. Data is passed between the terminal 300 and the MP proxy 501 via the MA PDU session 510 and the secure tunnel 512. The setting up of the MA PDU session may be as discussed in relation to Figure 6.

[0188] A request for establishment of a MA PDU session sent by the terminal 300 triggers the establishment of MA PDU session. The request may comprise an indication that the MA PDU session is used for traffic aggregation between 3GPP access and native non-3GPP access. This indication may use a defined access type - “native non-3GPP access”.

[0189] If the terminal 300 is connected via a native non-3GPP access, the terminal 300 establishes a secure (HTTP) tunnel 514 to the MP proxy 501 to provide a MA PDU session secure tunnel. This may be as described in relation to Figure 6. As no PDU session can be established over the native non-3GPP access, the secure tunnel 514 to the MP proxy 501 is over native non-3GPP access is set up.

[0190] An identifier may be used to associate the MA PDU session over 3 GPP access with the secure tunnel over native non-3GPP access. The identifier may be the correlation identifier. The terminal 300 may include this identifier in the MA PDU session request sent to the SMF. The identifier is used when establishing the secure tunnel to the MP proxy 501 to thereby associate the MA PDU session over 3 GPP access with the secure tunnel over 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 proxy when establishing the secure HTTP tunnel.

[0191] The SMF provides ATSSS rules 516 to the terminal. The ATSSS rules 516 may be provided via 3GPP access. The ATSSS rules 516 are such that these ATSSS rules 516 are for traffic aggregation between 3GPP and native non-3GPP access. The ATSSS rules 516 may be provided with an indication that the ATSSS rules 516 are for traffic aggregation between 3 GPP and native non-3GPP access.

[0192] The SMF provides N4 rules 518 to the UPF 120 and MA rules 520 to the MP proxy 501. If the MP proxy and the UPF are collocated, the MA rules may be part of N4 rules. The identifier used to associate the MA PDU session over 3 GPP access with the secure tunnel over native non-3GPP access may be provided with the MA rules. The ATSSS rules 516 in the terminal 300 and N4 rules in UPF 120 and / or the MA rules 520 in MP proxy 501 are associated with the MA PDU session 510 in UPF 120 and with the secure tunnel 514 in the MP proxy 501 using the identifier used to associate the MA PDU session over 3 GPP access with the secure tunnel over native non-3GPP access.

[0193] In contrast to the current ATSSS framework, the handling of MA rules 520 is moved from the UPF to the MP proxy where tunnels from / to the terminal 300 are terminated. The MP proxy 501 is where steer, switch, split, and duplicate operations are applied for DL traffic to the terminal. The MP proxy 501 provides traffic aggregation in accordance with the MA rules. The terminal is where steer, switch, split, and duplicate operations are applied for UU traffic to the MP proxy 501. The terminal 300 employs traffic aggregation in accordance with the ATSSS rules. The UPF is responsible for relaying user plane traffic between the MA PDU session 510 and the secure tunnel 512.

[0194] Reference is made to Figure 8 which schematically illustrates traffic handling rules for traffic aggregation between 3GPP access and native non-3GPP access. This example is based on a PDU session (and not a MA PDU session).

[0195] In this example, a PDU session has been established between the terminal 300 and the MP proxy 501. In some embodiments, a PDU session between the terminal 300 and the MP proxy 501 is established over the 3GPP access. In other embodiments, a PDU session has been established over the non-3GPP access. However, in some embodiments, the PDU session is not able to be established via the native non-3GPP access. The PDU session may be triggered by configured information. For example, URSP (UE route selection policy) rules in the terminal 300 can indicate that for a certain data network identified by a data network name (DNN) and / or a network slice identified by a S-NSSAI a PDU session shall be established. The PDU session is initially established with no explicit resources reserved for the native non-3GPP access. The PDU session established over the 3GPP access provides a PDU session 528 between the terminal 300 and the UPF 120. A secure tunnel 530 is provided between the UPF 120 and the MP proxy 501. User plane traffic (e.g., data) is communicated between the terminal 300 and the MP proxy 501 via the PDU session 528 and the secure tunnel 530.

[0196] A request for establishment of a PDU session from the terminal triggers the establishment of PDU session. The request for establishment of a PDU session may comprise an indication that the PDU session can be used for traffic aggregation between 3 GPP access and native non-3GPP access. The indication may that the PDU session can be used for traffic aggregation between 3 GPP access and native non-3GPP access indicate 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 3 GPP access and native non-3GPP access.

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

[0198] The terminal 300 may be provided with traffic handling rules allowing the terminal 300to route traffic sent from the terminal 300 to the MP proxy 501 either via the PDU session 528 or via the HTTP tunnel 532. These traffic handling rules for the terminal 300 are associated with the PDU session and the HTTP tunnel.

[0199] The MP proxy 501 may be provided with traffic handling rules allowing them to route traffic sent from MP proxy 501 to the terminal either via the PDU session 528 or via the HTTP tunnel 532. These traffic handling rules for the MP proxy 501 are associated with the PDU session and the HTTP tunnel.

[0200] As the terminal 300 or SMF indicates during PDU session establishment that the PDU session can be used for traffic aggregation between 3 GPP and native non-3GPP access, terminal rules 522 are provided to the terminal. The terminal rules define how the terminal should handle traffic aggregation in relation to UL user plane traffic.

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

[0202] In other embodiments, the UPF may provide the terminal rules 522 to the terminal 300 via the user plane. The UPF may provide the terminal rules 522 over the user plane by using a PMF protocol (PMFP) or an enhancement to that protocol. The PMFP may be used to communicate new and / or modified rules from the UPF to the terminal 300. For the support of the PMFP, the UPF supports PMFP request-response messaging over the user plane.

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

[0204] Alternatively or additionally the terminal rules 522 may be dynamically generated rules. The terminal rules 522 may be generated in the UE and / or the UPF. For example the terminal rules 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 a 3GPP access network node (referred to herein a link quality conditions). The link quality conditions may be determined based on PMF measurements or measurement results from TCP or QUIC. The quality of the link may be a measure of how well and / or how much transmitted data is received. A link quality condition may be provided by one or more of a bit error ratio, round trip time, packet loss rate, packet error rate, a signal to interference noise ratio, and / or the like. In some embodiments, the terminal rules 522 may be dynamically generated based on, input from an analytics function. A traffic requirement may for example be a required QoS (quality of service) or a required data rate or a required delay.

[0205] Likewise, as the terminal 300 or SMF indicates during PDU session establishment that that this PDU session can be used for traffic aggregation between 3GPP and native non-3GPP access, UPF rules 524 are provided to the UPF and MP rules 526 are provided to proxy 526. The MP rules 526 rules define how the MP proxy should handle traffic aggregation in relation to DL traffic. The UPF rules may comprise rules for the traffic between the UPF and the terminal and rules for the traffic between the UPF and the MP proxy 501.

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

[0207] Alternatively or additionally the MP rules 526 may be dynamically generated rules. The rules may be generated in the UE and / or the UPF. For example the rules 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 measurement results from TCP or QUIC. In some embodiments, the rules may be dynamically generated based on, input from an analytics function. A traffic requirement may for example be a required QoS (quality of service) or a required data rate or a required delay.

[0208] In contrast to the current ATSSS framework, the handling of MP rules 526 is moved from the UPF to the MP proxy 501 where tunnels from / to the terminal 300 are terminated. The MP proxy 501 is where traffic aggregation (e.g., steer, switch, split, and duplicate operations) are performed for DL user plane traffic destined for the terminal 300. The MP proxy 501 performs traffic aggregation in accordance with the MP rules 526.

[0209] For DL traffic, when the MP proxy 501 receives a data packet destined for the terminal 300, the MP proxy 501 associates the data packet with a terminal specific tunnel (e.g. tunnel 530 or tunnel 532). The terminal specific tunnel is associated with MP rules 526 which are enforced by the MP proxy 501. Based on the MP rules 526, user plane traffic is forwarded to the local IP address of the terminal 300 allocated by the native non-3GPP access via the tunnel 532 or to the IP address of the terminal 300 allocated by the UPF and associated with the PDU session.

[0210] The terminal 300 performs traffic aggregation (e.g., performs steer, switch, split, and duplicate operations) for UL user plane traffic destined for the MP proxy 501. The terminal 300 performs traffic aggregation in accordance with the terminal rules 522.

[0211] When the MP proxy 501 receives the UL user plane traffic (e.g., data) from the terminal 300, the MP proxy 502 decapsulates the user plane traffic (e.g., data) and sends the user plane traffic (e.g., data) packet towards a remote endpoint.

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

[0213] In some embodiments, one or more of the rules discussed in relation to Figure 7 or Figure 8 may be intent driven rules. An intent driven rule is one which defines a desired outcome or intent. The intent is supported by intent supporting capability in the entity enforcing the rules, that is the terminal or the MP proxy. For example, the intent supporting capability may be provided by an AI / ML function or a heuristic model.

[0214] The intent driven rules may define the desired UE behaviour and / or the desired MP proxy behaviour. One example of an intent-driven rule can be: “use native non-3GPP access for Internet traffic, for video streaming or for AR applications and use 3GPP access for all other traffic”.

[0215] The PCF 125 (see Figure 1) defines intent driven rules where the traffic descriptor of a PCC (policy and charging control) rule can refer to an abstract traffic target. That is the traffic target may not be identified by an explicit IP 5-tuple (which consists of source IP address, source port number, destination IP address, destination port number, transport protocol). The abstract traffic target may correspond to standard defined application ID(s) or to free-floating strings.

[0216] Such PCC rules may be translated by the SMF into ATSSS rules, or similar kind of rules. The ATSSS rules (or similar kind of rules) may be sent to the terminal 300. The ATSSS rules may refer to an abstract traffic target expressed in terms of application ID(s) or free- floating strings.

[0217] Alternatively or additionally intent driven rules may be provided to the MP proxy.

[0218] The interpretation of intent-driven rules may be performed in the terminal and / or MP proxy by either determining application ID(s), if applicable, or by using AI / ML or heuristic models or other methods to associate ongoing traffic with one of the rules.

[0219] Figure 2 illustrates an example of an apparatus 200. The apparatus may comprise or implement a MP proxy 501 or traffic aggregator. Alternatively, the apparatus may implement a user plane function 120. The apparatus 200 comprises at least one memory (for example 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 the RAM 211a and the ROM 211b. The at least one processor 212, 213 may be configured to execute an appropriate software code 215. The software code 215 may be stored in the ROM 211b.

[0220] The software code 215 may comprise software code of the MP proxy 501 or traffic aggregator. In embodiments where the software code 215 comprises software code of the MP proxy 501 or traffic aggregator. When the software code of the MP proxy 501 or traffic aggregator is executed by the at least one processor 212, 213, the apparatus 200 may perform the traffic aggregation in accordance with the present aspects or examples described herein. The apparatus 200 may comprise one or more circuits, or circuitry (not shown) which may be configured to perform traffic aggregation in accordance with the present aspects or examples.

[0221] In some embodiments, the software code 215 may comprise the software code of the UPF 120. When the software code of the UPF 120 is executed by the at least one processor 212, 213, the apparatus 200 may perform the methods described herein, for example, the methods described with respect to Figure 11. The apparatus 200 may comprise one or more circuits, or circuitry (not shown) which may be configured to perform one or more of the present aspects or examples. Figure 3 illustrates an example of a terminal 300. The terminal 300 may be any communication device capable of sending and receiving wireless signals, including radio signals. Non-limiting examples of a terminal 300 are a user equipment, a mobile station (MS) or mobile device such as a mobile phone or what is known as a ’smart phone’, a computer provided with a wireless interface card or other wireless interface facility (e.g., USB dongle), a personal data assistant (PDA) or a tablet provided with wireless communication capabilities, a machine-type communications (MTC) device, a Cellular Internet of things (CIoT) device or any combinations of these or the like. The terminal 300 may provide, for example, signals for carrying communications. The communications may be one or more of voice, electronic mail (email), text message, multimedia, data, machine data and so on.

[0222] The terminal 300 may receive signals over an air or radio interface 307 via appropriate apparatus for receiving radio signals and may transmit signals via appropriate apparatus for transmitting radio signals. In Figure 3, a transceiver apparatus is designated schematically by block 306. The transceiver apparatus 306 may be provided for example by means of a radio part and associated antenna arrangement. The antenna arrangement may be arranged internally or externally to the mobile device. The antenna arrangement may comprise an antenna array that includes one or more antenna elements.

[0223] The terminal 300 may be provided with or comprise at least one processor 301, at least one memory (for example at least one ROM 302a and at least one RAM 302b) and other possible components 303 for use in software and hardware aided execution of tasks it is designed to perform, including control of access to and communications with access networks of a wireless communication system (e.g., the wireless communication system 100) and other terminals. The at least one processor 301 is coupled to the RAM 302b and the ROM 302a. The at least one processor 301 may be configured to execute an appropriate software code 308. The software code 308 may for example allow to perform traffic aggregation in accordance with the present aspects or examples described herein. The software code 308 may be stored in the ROM 302a. The terminal 300 may comprise one or more circuits, or circuitry (not shown) which may be configured to perform traffic aggregation in accordance with the present aspects or examples described herein.

[0224] The processor, storage and other relevant control apparatus may be provided on an appropriate circuit board and / or in chipsets. This feature is denoted by reference 304. The device may optionally have a user interface such as keypad 305, touch sensitive screen or pad, combinations thereof or the like. Optionally one or more of a display, a speaker and a microphone may be provided depending on the type of the device.

[0225] Reference is made to Figure 9 which shows a method of some embodiments.

[0226] This method may be performed by an apparatus. The apparatus may be a terminal.

[0227] The apparatus may comprise suitable means, such as circuitry for providing the method. Alternatively or additionally, the apparatus may comprise at least one processor and at least one memory storing instructions that, when executed by the at least one processor cause the apparatus at least to provide the method below.

[0228] Alternatively or additionally, the apparatus may be such as discussed in relation to Figure 3. The method may be provided by computer program code or computer executable instructions.

[0229] The method may comprise as referenced Al, sending, to a 3GPP core network over 3GPP access, a request to establish or modify a data session, the request comprising an indication that indicates that the data session is to support traffic aggregation of traffic via the 3GPP access and traffic via a native non-3GPP access, and an identifier which is used to associate the data session via the 3 GPP access with a tunnel via the native non-3GPP access.

[0230] The method may comprise as referenced A2, receiving, from the 3 GPP core network, one or more rules for the aggregation of traffic via the 3 GPP access and traffic via the native non- 3 GPP access, the one or more rules being associated with the identifier.

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

[0232] It should be appreciated that the method outlined in Figure 9 may be modified to include any of the previously described features.

[0233] Reference is made to Figure 10 which shows a method of some embodiments.

[0234] This method may be performed by an apparatus, such as apparatus 200. The apparatus may comprise or implement a traffic aggregator or MP proxy, such as MP proxy 501.

[0235] The apparatus may comprise suitable means, such as circuitry for providing a traffic aggregator or MP proxy.

[0236] Alternatively or additionally, the apparatus may comprise at least one processor and at least one memory storing instructions of software code of a traffic aggregator or MP proxy that, when executed by the at least one processor cause the apparatus at least to provide the method below.

[0237] Alternatively or additionally, the apparatus may be such as discussed in relation to Figure 2. The method may be provided by computer program code or computer executable instructions.

[0238] The method may comprise as referenced Bl, receiving an identifier which is used to associate a) a data session between the traffic aggregator and a terminal via a 3 GPP access with b) a tunnel between the traffic aggregator and the terminal via a native non-3GPP access.

[0239] The method may comprise as referenced B2, obtaining one or more rules for the aggregation of traffic to the terminal via the 3 GPP access and traffic to the terminal via the native non- 3 GPP access, the one or more rules being associated with the identifier.

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

[0241] It should be appreciated that the method outlined in Figure 10 may be modified to include any of the previously described features.

[0242] Reference is made to Figure 11 which shows a method of some embodiments.

[0243] This method may be performed by an apparatus. The apparatus may comprise or implement a user plane function.

[0244] The apparatus may comprise suitable means, such as circuitry for providing the user plane function.

[0245] Alternatively or additionally, the apparatus may comprise at least one processor and at least one memory storing instructions of a user plane function that, when executed by the at least one processor cause the apparatus at least to provide the method below.

[0246] Alternatively or additionally, the apparatus may be such as discussed in relation to Figure 2. The method may be provided by computer program code or computer executable instructions.

[0247] The method may comprise as referenced Cl, receiving an address of a traffic aggregator, an identifier for a secure connection with a traffic aggregator, and information about one or more rules for user plane traffic of a data session. The method may comprise as referenced C2, using the address of the traffic aggregator and the identifier to send a request for a secure connection to the traffic aggregator to establish the secure connection.

[0248] The method may comprise as referenced C3, using the address of the traffic aggregator and the identifier to send a request for a secure connection to the traffic aggregator to establish the secure connection.

[0249] It should be appreciated that the method outlined in Figure 11 may be modified to include any of the previously described features.

[0250] It is noted that while the above describes example embodiments, there are several variations and modifications which may be made to the disclosed solution without departing from the scope of the present invention.

[0251] Some of the example embodiments have been described in relation to a wireless communication system operation in accordance with 3 GPP standards for NR. However, some example embodiments of the present disclosure may also be applicable to a wireless communication system that operates in accordance with 3GPP standards for 5G-advanced, or other future 3 GPP standards such as 3 GPP standards for 6G and beyond.

[0252] In the discussed examples there is one native non-3GPP access provided via a native non- 3GPP access network 130 network and one 3GPP access provided via a 3GPP access network (e.g., NG-RAN 106). However, it would be understood that embodiments can be implemented where there are: one or more native non-3GPP accesses provided via respective native non-3GPP access networks: and one or more accesses provided by one or more of one or more 3GPP accesses provided via respective 3GPP access networks and / or one or more non-3GPP accesses provided via respective non-3GGP access networks.

[0253] The examples may thus vary within the scope of the attached claims. In general, some embodiments may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. For example, some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device, although embodiments are not limited thereto. While various embodiments may be illustrated and described as block diagrams, flow charts, or using some other pictorial representation, it is well understood that these blocks, apparatus, systems, techniques or methods described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.

[0254] The examples may be implemented by computer software stored in a memory and executable by at least one data processor of the involved entities or by hardware, or by a combination of software and hardware. Further in this regard it should be noted that any procedures may represent program steps, or interconnected logic circuits, blocks and functions, or a combination of program steps and logic circuits, blocks and functions. The software may be stored on such physical media as memory chips, or memory blocks implemented within the processor, magnetic media such as hard disk or floppy disks, and optical media such as for example DVD and the data variants thereof, CD.

[0255] The term “non-transitory”, as used herein, is a limitation of the medium itself (i.e., tangible, not a signal) as opposed to a limitation on data storage persistency (e.g., RAM vs ROM).

[0256] As used herein, “at least one of the following:” and “at least one of: ” and similar wording, where the list of two or more elements are joined by “and”, or “or”, mean at least any one of the elements, or at least any two or more of the elements, or at least all of the elements.

[0257] The memory may be of any type suitable to the local technical environment and may 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 processors may be of any type suitable to the local technical environment, and may include one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs), application specific integrated circuits (ASIC), gate level circuits and processors based on multi core processor architecture, as non-limiting examples.

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

[0259] As used in this application, the term “circuitry” may refer to one or more or all of the following: (a) hardware-only circuit(s) (such as analogue and / or digital circuit(s));

[0260] (b) combinations of hardware circuits and software, such as:

[0261] (i) a combination of analogue and / or digital circuit(s) with software and / or firmware and

[0262] (ii) any portions of hardware processor(s) with software (including digital signal processor(s)), software, and memory(ies) that work together to cause an apparatus, such as the terminal 300 or a base station to perform the various functions previously described; and

[0263] (c) hardware circuit(s) and or processor(s), such as a microprocessor(s) or a portion of a microprocessor(s), that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation.

[0264] This definition of circuitry applies to all uses of the term “circuitry” in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term circuitry also covers, for example integrated device. The term circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in a server, a cellular network device, or other computing or network device.

[0265] The foregoing description has provided by way of exemplary and non-limiting examples a full and informative description of some embodiments. However, various modifications and adaptations may become apparent to those skilled in the relevant arts in view of the foregoing description, when read in conjunction with the accompanying drawings and the appended claims. However, all such and similar modifications of the teachings will still fall within the scope as defined in the appended claims.

Claims

Claims:

1. A terminal comprising: at least one processor; at least one memory storing instructions which, when executed by the at least one processor, cause the terminal to perform operations, the operations comprising: sending, to a 3GPP core network over 3GPP access, a request to establish or modify a data session, the request comprising an indication that indicates that the data session is to support traffic aggregation of traffic via the 3 GPP access and traffic via a native non-3GPP access, and an identifier which is used to associate the data session via the 3GPP access with a tunnel via the native non-3GPP access; receiving, from the 3 GPP core network, one or more rules for the aggregation of traffic via the 3 GPP 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 aggregation of uplink traffic from the terminal to a traffic aggregator via the 3 GPP access and via the native non-3GPP access.

2. The terminal as claimed in claim 1, wherein the means is for using the one or more rules to control traffic aggregation of uplink traffic by routing the uplink traffic to the traffic aggregator via one or both of the 3 GPP access and native non-3GPP access.

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

4. The terminal as claimed in any of claims 1 to 3, wherein the one or more rules comprise one or more access traffic steering, switching, splitting rules or one or more terminal rules.

5. The terminal as claimed in any of claims 1 to 4, wherein the data session is a protocol data unit session or a multi-access protocol data unit session.

6. The terminal as claimed in any of claims 1 to 5, further comprising: means for receiving the one or more rules from a session management function of the 3 GPP core network or from a user plane function of the 3 GPP core network.

7. The terminal as claimed in any one of claims 1 to 6, wherein the one or more rules are dependent on one or more network conditions and / or one or more traffic requirements.

8. The terminal as claimed in claim 7, wherein the one or more network conditions comprise one or more of link quality conditions.

9. The terminal as claimed in claim 7 or 8, wherein the updating the one or more rules dependent on at least one of: the one or more network conditions; or the one or more traffic requirements10. The terminal as claimed in any of claims 1 to 9, wherein one or more of the rules comprise one or more intent driven rules.

11. The terminal as claimed in any of claims 1 to 10, further comprising: means for providing a capability indication of a capability of the terminal to support traffic aggregation between the 3 GPP access and native non-3GPP access.

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

13. The traffic aggregator as claimed in claim 12, wherein the means for using the one or more rules to control traffic aggregation of downlink traffic from the traffic aggregator to the terminal via the 3GPP access and via the native non-3GPP access comprises means for routing the downlink traffic to the terminal via one or both of the 3 GPP access and native non-3GPP access.

14. The traffic aggregator as claimed in any of claims 12 or 13, wherein the means for receiving comprises means for receiving, from a session management function, the identifier during a setting up of the data session with the terminal.

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

16. The traffic aggregator as claimed in claim 15, further comprising: means for receiving a connection request from the user plane function for setting up the tunnel between the traffic aggregator and the user plane function, the connection request comprising the identifier.

17. The traffic aggregator as claimed in any of claims 12 to 16, wherein the one or more rules comprise one or more multi access rules or one or more multipath proxy rules.

18. The traffic aggregator as claimed in any of claims 12 to 17, wherein the data session is a protocol data unit session or a multi-access protocol data unit session.

19. The traffic aggregator as claimed in any of claims 12 to 18, further comprising: means for receiving the one or more rules from a session management function or a user plane function of the 3 GPP core network.

20. The traffic aggregator as claimed in any one of claims 12 to 19, wherein the one or more rules are dependent on one or more network conditions and / or one or more traffic requirements.

21. The traffic aggregator as claimed in 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: a user plane function configured for: receiving an address of a traffic aggregator, an identifier for a tunnel with a traffic aggregator, non-3GPP, and information about one or more rules for user plane traffic of the data session; using the address of the traffic aggregator and the identifier to send a request for a tunnel to the traffic aggregator to establish the tunnel; and using the one or more rules to control sending of user plane traffic between the traffic aggregator via the tunnel and the terminal via a 3 GPP access and the user plane function.

23. A method for a terminal, the method comprising: sending, to a 3GPP core network over 3GPP access, a request to establish or modify a data session, the request comprising an indication that indicates that the data session is to support traffic aggregation of traffic via the 3 GPP access and traffic via a native non-3GPP access, and an identifier which is used to associate the data session via the 3 GPP access with a tunnel via the native non-3GPP access; receiving, from the 3 GPP core network, one or more rules for the aggregation of traffic via the 3 GPP access and traffic via the native non-3GPP access, the one or more rules being associated with the identifier; andusing the one or more rules to control aggregation of uplink traffic from a terminal to a traffic aggregator via the 3GPP access and via the native non-3GPP access.

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

25. The method as claimed in claim 23 or 24, further comprising: providing the identifier when establishing the tunnel to the traffic aggregator via the native non-3GPP access, said identifier being used by the traffic aggregator to associate the tunnel with the data session with the traffic aggregator established via the 3GPP access.

26. The method as claimed in any of claims 23 to 25, wherein the one or more rules comprise one or more access traffic steering, switching, splitting rules or one or more terminal rules.

27. The method as claimed in any of claims 23 to 26, wherein the data session is a protocol data unit session or a multi-access protocol data unit session.

28. The method as claimed in any of claims 23 to 27, further comprising: receiving the one or more rules from a session management function of the 3 GPP core network or from a user plane function of the 3 GPP core network.

29. The method as claimed in any one of claims 23 to 28, wherein the one or more rules are dependent on one or more network conditions and / or one or more traffic requirements.

30. The method as claimed in claim 29, wherein the one or more network conditions comprise one or more of link quality conditions.

31. The method as claimed in claim 29 or 30, wherein the updating the one or more rules dependent on at least one of: the one or more network conditions; or the one or more traffic requirements32. The method as claimed in any of claims 23 to 31, wherein one or more of the rules comprise one or more intent driven rules.

33. The method as claimed in any of claims 23 to 32, further comprising: providing a capability indication of a capability of the terminal to support traffic aggregation between the 3 GPP access and native non-3GPP access.

34. A method for a traffic aggregator, the method comprising: receiving an identifier which is used to associate a) a data session between a traffic aggregator and a terminal via a 3 GPP access with b) a tunnel between the traffic aggregator and the terminal via a native non-3GPP access; obtaining one or more rules for the aggregation of traffic to the terminal via the 3 GPP access and traffic to the terminal 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 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 as claimed in claim 34, wherein the using the one or more rules to control traffic aggregation of downlink traffic from the traffic aggregator to the terminal via the 3 GPP access and via the native non-3GPP access comprises means for routing the downlink traffic to the terminal via one or both of the 3GPP access and native non-3GPP access.

36. The method as claimed in any of claims 34 or 35, wherein the receiving comprises receiving, from a session management function, the identifier during a setting up of the data session with the terminal.

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

38. The method as claimed in claim 37, further comprising:receiving a connection request from the user plane function for setting up the tunnel between the traffic aggregator and the user plane function, the connection request comprising the identifier.

39. The method as claimed in any of claims 34 to 38, wherein the one or more rules comprise one or more multi access rules or one or more multipath proxy rules.

40. The method as claimed in any of claims 34 to 39, wherein the data session is a protocol data unit session or a multi-access protocol data unit session.

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

42. The method as claimed in any one of claims 34 to 41, wherein the one or more rules are dependent on one or more network conditions and / or one or more traffic requirements.

43. The method as claimed in 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 a user plane function, the method comprising: receiving an address of a traffic aggregator, an identifier for a tunnel with a traffic aggregator, and information about one or more rules for user plane traffic of a data session; using the address of the traffic aggregator and the identifier to send a request for a tunnel to the traffic aggregator to establish the tunnel; and using the one or more rules to control sending of user plane traffic between the traffic aggregator via the tunnel and the terminal via a 3 GPP 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 as claimed in any of clams 23 to 33.

46. A computer-readable medium comprising instructions which, when executed by at least one processor of a terminal, cause the terminal to perform the method as claimed in any of clams 23 to 33.

47. A computer program comprising instructions, wherein when the computer program is executed by an apparatus, the apparatus is caused to perform the method as claimed in any of clams 34 to 43.

48. A computer-readable medium comprising instructions which, when executed by at least one processor of an apparatus, cause the apparatus to perform the method as claimed in any of clams 34 to 43.

Images