[go: up one dir, main page]

WO2024193841A1 - Session de communication multi-accès - Google Patents

Session de communication multi-accès Download PDF

Info

Publication number
WO2024193841A1
WO2024193841A1 PCT/EP2023/080837 EP2023080837W WO2024193841A1 WO 2024193841 A1 WO2024193841 A1 WO 2024193841A1 EP 2023080837 W EP2023080837 W EP 2023080837W WO 2024193841 A1 WO2024193841 A1 WO 2024193841A1
Authority
WO
WIPO (PCT)
Prior art keywords
upf
access
network entity
rules
network
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/EP2023/080837
Other languages
English (en)
Inventor
Apostolis Salkintzis
Dimitris DIMOPOULOS
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Lenovo Singapore Pte Ltd
Original Assignee
Lenovo Singapore Pte Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Lenovo Singapore Pte Ltd filed Critical Lenovo Singapore Pte Ltd
Publication of WO2024193841A1 publication Critical patent/WO2024193841A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections
    • H04W76/16—Involving different core network technologies, e.g. a packet-switched [PS] bearer in combination with a circuit-switched [CS] bearer
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections

Definitions

  • the present disclosure relates to wireless communications, and more specifically to a multi-access communication session.
  • the present disclosure relates to a multi-access communication session involving multiple User-Plane Functions (UPFs) each operating as a protocol data unit (PDU) session anchor.
  • UPFs User-Plane Functions
  • PDU protocol data unit
  • a wireless communications system may include one or multiple network communication devices, such as base stations, which may support wireless communications for one or multiple user communication devices, which may be otherwise known as user equipment (UE), or other suitable terminology.
  • the wireless communications system may support wireless communications with one or multiple user communication devices by utilizing resources of the wireless communication system (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers, or the like).
  • the wireless communications system may support wireless communications across various radio access technologies including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, among other suitable radio access technologies beyond 5G (e.g., sixth generation (6G)).
  • a PDU (Protocol Data Unit) Session is a logical connection which enables the flow of data packets between a 5 G user equipment (UE) and a data network (DN) via the 5G network infrastructure.
  • UE User Equipment
  • DN data network
  • the 5G network creates a data path for it and configures the elements in the data path (aka user-plane functions) to provide the necessary Quality-of-Service (QoS) and routing behavior.
  • the elements in the data path of the PDU Session comprise the UE, radio network elements and one or more User-Plane Function network entities (UPFs) in the core network.
  • UPFs User-Plane Function network entities
  • PDU Session Anchor PSA
  • DN data network
  • PDU Session Anchor PSA
  • a PDU Session can support different types of data traffic such as Ethernet, Unstructured, and IPv4 or IPv6.
  • the phrase “based on” shall not be construed as a reference to a closed set of conditions.
  • an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure.
  • the phrase “based on” shall be constmed in the same manner as the phrase “based at least in part on.
  • a “set” may include one or more elements.
  • Some implementations of the method and apparatuses described herein may include a network entity for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the network entity to: receive a request message to establish a multi -access communication session for a user equipment (UE) and a data network; select a first user plane function (UPF) and a second UPF for the multi -access communication session, wherein the first UPF and the second UPF are configured to route data associated with the multi-access communication session and the data network; transmit first multi-access rules and forward-action rules to the first UPF; transmit second multi-access rules to the second UPF; and transmit a response message that indicates an acceptance to establish the multi-access communication session, wherein the response message comprises information that enables the UE to communicate with the first UPF.
  • UE user equipment
  • UPF user plane function
  • the at least one processor may be configured to cause the network entity to: transmit the second multi-access rules in a first session establishment request message, wherein the first session establishment request message comprises a request for information to enable the first UPF to communicate with the second UPF.
  • the information enabling the first UPF to communicate with the second UPF may comprise: (i) a multipath TCP (MPTCP) address associated with the second UPF; (ii) a MPTCP port number associated with the second UPF; and (iii) a MPTCP proxy type associated with the second UPF.
  • MPTCP multipath TCP
  • the information enabling the first UPF to communicate with the second UPF may comprise (i) a MPQUIC address associated with the second UPF; (ii) a MPQUIC port number associated with the second UPF; (iii) a MPQUIC proxy type associated with the second UPF.
  • the at least one processor may be configured to cause the network entity to: receive a first session establishment response message comprising the information to enable the first UPF to communicate with the second UPF.
  • the at least one processor may be configured to cause the network entity to: transmit the first multi-access rules and the forward-action rules to the first UPF in a second session establishment request message, wherein the second session establishment request message comprises the information to enable the first UPF to communicate with the second UPF.
  • the at least one processor may be configured to cause the network entity to: receive a second session establishment response message comprising the information to enable the UE to communicate with the first UPF.
  • the at least one processor may be configured to cause the network entity to create the first multi-access rules as rules to be used by the first UPF to select an access path of a plurality of access paths, for routing downlink data traffic received from the data network.
  • the at least one processor may be configured to cause the network entity to create the forward-action rules as rules to be used by the first UPF for the routing of uplink data traffic to the data network or the second UPF during the multi-access communication session.
  • the at least one processor may be configured to cause the network entity to create the second multi-access rules as rules to be used by the second UPF to select an access path of a plurality of access paths, for routing downlink data traffic received from the data network.
  • the response message may comprise one or more steering rules for the UE, wherein the steering rules are used to select an access path of a plurality of access paths for routing uplink data traffic of the multi-access communication session.
  • the information enabling the UE to communicate with the first UPF may comprise: (i) a MPTCP address associated with the first UPF; (ii) a MPTCP port number associated with the first UPF; and (iii) a MPTCP proxy type associated with the first UPF.
  • the information enabling the UE to communicate with the first UPF may comprise: (i) a MPQUIC address associated with the first UPF; (ii) a MPQUIC port number associated with the first UPF; and (iii) a MPQUIC proxy type associated with the first UPF.
  • the at least one processor may be configured to cause the network entity to create the first multi-access rules, the second multi-access rules and the forward-action rules based on policy information received from a policy control function network entity.
  • Some implementations of the method and apparatuses described herein may include a method performed by a network entity, the method comprising: receiving a request message to establish a multi-access communication session for a user equipment (UE) and a data network; selecting a first user plane function (UPF) and a second UPF for the multiaccess communication session, wherein the first UPF and second UPF are configured to route data associated with the multi-access communication session and the data network; transmitting first multi -access rules and forward-action rules to the first UPF; transmitting second multi-access rules to the second UPF; and transmitting a response that indicates an acceptance to establish the multi-access communication session, wherein the response comprises information that enables the UE to communicate with the first UPF.
  • UE user equipment
  • UPF user plane function
  • Some implementations of the method and apparatuses described herein may include a network entity for wireless communication, comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the network entity to: determine to add a first user plane function (UPF) to a multi -access communication session established for a user equipment (UE), a second UPF and a data network, wherein the first UPF and the second UPF are configured to route data associated with the multi-access communication session and the data network; transmit first multiaccess rules and forward-action rules to the first UPF; and transmit a message that comprises information that enables the UE to communicate with the first UPF.
  • UPF user plane function
  • the at least one processor may be configured to cause the network entity to transmit a session modification request message to the second UPF, and the session modification request comprises a request for information to enable the first UPF to communicate with the second UPF.
  • the at least one processor may be configured to cause the network entity to receive a session modification response message, the session modification response message comprising the information to enable the first UPF to communicate with the second UPF.
  • the at least one processor may be configured to cause the network entity to transmit the first multi-access rules and forward-action rules to the first UPF in a session establishment request message, the session establishment request message comprising the information to enable the first UPF to communicate with the second UPF.
  • the at least one processor may be configured to cause the network entity to receive a session establishment response message, the session establishment response message comprising the information to enable the UE to communicate with the first UE.
  • Figure 2 illustrates a multi -access PDU session with a single PSA.
  • Figure 3 illustrates the protocol layers involved in a multi-access PDU session with a single PSA.
  • Figure 4 illustrates an example of a wireless communications system in accordance with aspects of the present disclosure.
  • Figure 5 illustrates an example of a general architecture for ATSSS that is useful for understanding aspects of the present disclosure.
  • Figure 6 illustrates the protocol layers involved in a multi-access PDU session with multiple PSAs in accordance with aspects of the present disclosure.
  • Figure 7 illustrates an example of a process to establish a multi-access PDU Session with multiple PSAs in accordance with aspects of the present disclosure.
  • Figure 8 illustrates an example of a process to add a PSA to an existing multiaccess PDU Session in accordance with aspects of the present disclosure.
  • Figure 9 illustrates an example of user plane data flow with two PSAs when MPQUIC steering functionality is applied in a multi-access PDU Session in accordance with aspects of the present disclosure.
  • Figure 10 illustrates the protocol layers involved in the user-plane communication via a multi-access PDU Session with two PSAs in the example where the MPQUIC steering functionality is applied in accordance with aspects of the present disclosure.
  • Figure 11 illustrates an example of user plane data flow with two PSAs when MPTCP steering functionality is applied in the multi-access PDU Session in accordance with aspects of the present disclosure.
  • Figure 12 illustrates an example of a processor 1200 in accordance with aspects of the present disclosure.
  • Figure 13 illustrates an example of a network equipment (NE) 1300 in accordance with aspects of the present disclosure.
  • Figure 14 illustrate a flowcharts of method performed by a NE (e.g. a SMF) in accordance with aspects of the present disclosure.
  • a NE e.g. a SMF
  • Figure 15 illustrate a flowcharts of method performed by a NE (e.g. a SMF) in accordance with aspects of the present disclosure.
  • Figure 16 illustrate a flowcharts of method performed by a NE (e.g. a UMF) in accordance with aspects of the present disclosure.
  • Figure 17 illustrate a flowcharts of method performed by a NE (e.g. a UMF) in accordance with aspects of the present disclosure.
  • a NE e.g. a UMF
  • Figure 18 illustrate a flowcharts of method performed by a NE (e.g. a UMF) in accordance with aspects of the present disclosure
  • a NE e.g. a UMF
  • a PDU Session can have multiple PSAs, i.e., multiple UPFs that transfer data traffic to and from a data network via different N6 interfaces.
  • the use of multiple PSAs can optimize the routing of data traffic and can facilitate access to both edge-computing (local) services and traditional centralized (remote) services using the shortest data paths.
  • FIG. 1 The data path of an example PDU Session with two PSAs is shown in Figure 1.
  • This data path provides IP connectivity between the UE and a first user plane function network entity (UPF-1) and between UPF-1 and a second user plane function network entity (UPF- 2).
  • a Session Management Function network entity responsible for the session decides whether one or more PSAs should be included in the data path. If only one PSA is initially included (i.e., UPF-2), the SMF may later add an additional PSA in the data path (i.e., UPF-1).
  • UPF-1 does not only provide PSA functionality, but it also operates as an “uplink classifier” (UL CL). It is responsible for determining the routing of uplink data traffic, deciding whether it should be sent to the Data Network (DN) via its local N6 interface or forwarded to UPF-1. These routing choices are made based on guidelines provided by the SMF.
  • the PDU Session shown in Figure 1 is a single-access PDU Session because the UE utilizes a single access network for data communication; either a non-3GPP access network (e.g., WiFi), or a 3GPP access network (e.g., NR-RAN).
  • a non-3GPP access network e.g., WiFi
  • a 3GPP access network e.g., NR-RAN
  • the PDU Session provides a single data path between the UE and a 5G network.
  • 5G networks also support multi-access PDU Sessions that offer multiple different data paths between the UE and the 5G network.
  • An example of such session is shown in Figure 2, where data communication is supported via multiple access networks, typically one non-3GPP access network and one or more 3GPP access networks.
  • the capability to support multi-access PDU Sessions was introduced in the context of the Access Traffic Steering, Switching and Splitting (ATSSS) feature.
  • ATSSS Access Traffic Steering, Switching and Splitting
  • the ATSSS feature as defined in the Third Generation Partnership Project (3 GPP) Rel-18 specifications, provides enhanced data communication capabilities by allowing a UE to utilize multiple access paths simultaneously. This is achieved by establishing a multi -access communication session (referred to in the 3 GPP specifications as Multiaccess Packet Data Unit (MA PDU) Session) that supports two access paths, one 3GPP access path, using an access network defined by 3GPP, such a NG-RAN, and one non-3GPP access path, using an access network not defined by 3GPP, such as Wi-Fi.
  • 3GPP Third Generation Partnership Project
  • Wi-Fi Wireless Fidel-18
  • Every data packet that should be transmitted via the multi-access communication session is transmitted either over the 3 GPP access path or over the non-3 GPP access path, according to multi -access rules, which are provided to the UE and to a User Plane Function (UPF) during the establishment of the multi-access communication session.
  • multi -access rules which are provided to the UE and to a User Plane Function (UPF) during the establishment of the multi-access communication session.
  • UPF User Plane Function
  • a problem is that contrary to a single-access PDU Session, a multi-access (MA) PDU Session cannot support multiple PSAs.
  • an MA PDU Session may have multiple UPFs, only one of these UPFs (e.g. UPF-2 in Figure 2) can provide the PSA functionality and can route data traffic to the DN.
  • Other UPFs e.g. UPF-1 in Figure 2 may be included in the data path but cannot route data to the DN via their own N6 interfaces. Therefore, a MA PDU Session currently defined cannot support simultaneous access to both edge-computing (local) services and traditional centralized (remote) services.
  • FIG. 3 illustrates the protocol layers involved in a multi-access PDU session with a single PSA.
  • the UE and the PSA implement special functionality, called steering functionality, that is required to enable the multipath communication.
  • This steering functionality can be based on the QUIC protocol (as shown in Figure 3), or on the multipath TCP (MPTCP) protocol. It requires the UE to operate as a client and the PSA to operate as a proxy.
  • MPTCP multipath TCP
  • the steering functionality in the network can reside only in one UPF, so there can be only one proxy / PSA. Other UPFs may be included in the data path but they cannot operate as proxies / PSAs.
  • this disclosure proposes enhancements to the 5G network architecture that enables a MA PDU Session to have multiple PSAs, thus, making it feasible to simultaneously support (a) multipath communication between the UE and edgecomputing (local) services in a DN and (b) multipath communication between the UE and traditional centralized (remote) services in the same DN.
  • FIG. 4 illustrates an example of a wireless communications system 100 in accordance with aspects of the present disclosure.
  • the wireless communications system 100 may include one or more NE 102, one or more UE 104, and a core network (CN) 106.
  • the wireless communications system 100 may support various radio access technologies.
  • the wireless communications system 100 may be a 4G network, such as an LTE network or an LTE -Advanced (LTE-A) network.
  • LTE-A LTE -Advanced
  • the wireless communications system 100 may be a NR network, such as a 5G network, a 5G- Advanced (5G-A) network, or a 5G ultrawideband (5G-UWB) network.
  • the wireless communications system 100 may be a combination of a 4G network and a 5G network, or other suitable radio access technology including Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20.
  • IEEE Institute of Electrical and Electronics Engineers
  • Wi-Fi Wi-Fi
  • WiMAX IEEE 802.16
  • IEEE 802.20 The wireless communications system 100 may support radio access technologies beyond 5G, for example, 6G. Additionally, the wireless communications system 100 may support technologies, such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA), etc.
  • TDMA time division multiple access
  • FDMA frequency division multiple access
  • CDMA code division multiple access
  • the one or more NE 102 may be dispersed throughout a geographic region to form the wireless communications system 100.
  • One or more of the NE 102 described herein may be or include or may be referred to as a network node, a base station, a network element, a network function, a network entity, a radio access network (RAN), a NodeB, an eNodeB (eNB), a next-generation NodeB (gNB), or other suitable terminology.
  • An NE 102 and a UE 104 may communicate via a communication link, which may be a wireless or wired connection.
  • an NE 102 and a UE 104 may perform wireless communication (e.g., receive signaling, transmit signaling) over a Uu interface.
  • An NE 102 may provide a geographic coverage area for which the NE 102 may support services for one or more UEs 104 within the geographic coverage area.
  • an NE 102 and a UE 104 may support wireless communication of signals related to services (e.g., voice, video, packet data, messaging, broadcast, etc.) according to one or multiple radio access technologies.
  • an NE 102 may be moveable, for example, a satellite associated with a non-terrestrial network (NTN).
  • NTN non-terrestrial network
  • different geographic coverage areas 112 associated with the same or different radio access technologies may overlap, but the different geographic coverage areas may be associated with different NE 102.
  • the one or more UE 104 may be dispersed throughout a geographic region of the wireless communications system 100.
  • a UE 104 may include or may be referred to as a remote unit, a mobile device, a wireless device, a remote device, a subscriber device, a transmitter device, a receiver device, or some other suitable terminology.
  • the UE 104 may be referred to as a unit, a station, a terminal, or a client, among other examples.
  • the UE 104 may be referred to as an Internet-of- Things (loT) device, an Internet-of-Everything (loE) device, or machine-type communication (MTC) device, among other examples.
  • LoT Internet-of- Things
  • LoE Internet-of-Everything
  • MTC machine-type communication
  • a UE 104 may be able to support wireless communication directly with other UEs 104 over a communication link.
  • a UE 104 may support wireless communication directly with another UE 104 over a device-to-device (D2D) communication link.
  • D2D device-to-device
  • the communication link 114 may be referred to as a sidelink.
  • a UE 104 may support wireless communication directly with another UE 104 over a PC5 interface.
  • An NE 102 may support communications with the CN 106, or with another NE 102, or both.
  • an NE 102 may interface with other NE 102 or the CN 106 through one or more backhaul links (e.g., SI, N2, N2, or network interface).
  • the NE 102 may communicate with each other directly.
  • the NE 102 may communicate with each other or indirectly (e.g., via the CN 106.
  • one or more NE 102 may include subcomponents, such as an access network entity, which may be an example of an access node controller (ANC).
  • An ANC may communicate with the one or more UEs 104 through one or more other access network transmission entities, which may be referred to as a radio heads, smart radio heads, or transmission-reception points (TRPs).
  • TRPs transmission-reception points
  • the CN 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions.
  • the CN 106 may be an evolved packet core (EPC), or a 5G core (5GC), which may include a control plane entity that manages access and mobility (e.g., a mobility management entity (MME), an access and mobility management function network entity (AMF)) and a user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW), a Packet Data Network (PDN) gateway (P-GW), or a user plane function (UPF)).
  • EPC evolved packet core
  • 5GC 5G core
  • MME mobility management entity
  • AMF access and mobility management function network entity
  • S-GW serving gateway
  • PDN gateway Packet Data Network gateway
  • UPF user plane function
  • control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signal bearers, etc.) for the one or more UEs 104 served by the one or more NE 102 associated with the CN 106.
  • NAS non-access stratum
  • the CN 106 may communicate with a packet data network over one or more backhaul links (e.g., via an SI, N2, N2, or another network interface).
  • the packet data network may include an application server.
  • one or more UEs 104 may communicate with the application server.
  • a UE 104 may establish a session (e.g., a protocol data unit (PDU) session, or the like) with the CN 106 via an NE 102.
  • the CN 106 may route traffic (e.g., control information, data, and the like) between the UE 104 and the application server using the established session (e.g., the established PDU session).
  • the PDU session may be an example of a logical connection between the UE 104 and the CN 106 (e.g., one or more network functions of the CN 106).
  • the NEs 102 and the UEs 104 may use resources of the wireless communications system 100 (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communications).
  • the NEs 102 and the UEs 104 may support different resource structures.
  • the NEs 102 and the UEs 104 may support different frame structures.
  • the NEs 102 and the UEs 104 may support a single frame structure.
  • the NEs 102 and the UEs 104 may support various frame structures (i.e., multiple frame structures).
  • the NEs 102 and the UEs 104 may support various frame structures based on one or more numerologies.
  • One or more numerologies may be supported in the wireless communications system 100, and a numerology may include a subcarrier spacing and a cyclic prefix.
  • a first subcarrier spacing e.g., 15 kHz
  • a normal cyclic prefix e.g. 15 kHz
  • the first subcarrier spacing e.g., 15 kHz
  • a time interval of a resource may be organized according to frames (also referred to as radio frames).
  • Each frame may have a duration, for example, a 10 millisecond (ms) duration.
  • each frame may include multiple subframes.
  • each frame may include 10 subframes, and each subframe may have a duration, for example, a 1 ms duration.
  • each frame may have the same duration.
  • each subframe of a frame may have the same duration.
  • a time interval of a resource may be organized according to slots.
  • a subframe may include a number (e.g., quantity) of slots.
  • the number of slots in each subframe may also depend on the one or more numerologies supported in the wireless communications system 100.
  • Each slot may include a number (e.g., quantity) of symbols (e.g., OFDM symbols).
  • the number (e.g., quantity) of slots for a subframe may depend on a numerology.
  • a slot For a normal cyclic prefix, a slot may include 14 symbols.
  • a slot For an extended cyclic prefix (e.g., applicable for 60 kHz subcarrier spacing), a slot may include 12 symbols.
  • a first subcarrier spacing e.g. 15 kHz
  • an electromagnetic (EM) spectrum may be split, based on frequency or wavelength, into various classes, frequency bands, frequency channels, etc.
  • the wireless communications system 100 may support one or multiple operating frequency bands, such as frequency range designations FR1 (410 MHz - 7.125 GHz), FR2 (24.25 GHz - 52.6 GHz), FR3 (7.125 GHz - 24.25 GHz), FR4 (52.6 GHz - 114.25 GHz), FR4a or FR4-1 (52.6 GHz - 71 GHz), and FR5 (114.25 GHz - 300 GHz).
  • FR1 410 MHz - 7.125 GHz
  • FR2 24.25 GHz - 52.6 GHz
  • FR3 7.125 GHz - 24.25 GHz
  • FR4 (52.6 GHz - 114.25 GHz
  • FR4a or FR4-1 52.6 GHz - 71 GHz
  • FR5 114.25 GHz - 300 GHz
  • the NEs 102 and the UEs 104 may perform wireless communications over one or more of the operating frequency bands.
  • FR1 may be used by the NEs 102 and the UEs 104, among other equipment or devices for cellular communications traffic (e.g., control information, data).
  • FR2 may be used by the NEs 102 and the UEs 104, among other equipment or devices for short-range, high data rate capabilities.
  • FR1 may be associated with one or multiple numerologies (e.g., at least three numerologies).
  • FR2 may be associated with one or multiple numerologies (e.g., at least 2 numerologies).
  • Figure 5 illustrates an example of a general architecture 200 for ATSSS that is useful for understanding aspects of the present disclosure.
  • the general architecture 200 may be implemented in the context of Figure 4.
  • a remote unit 104 i.e., a UE
  • a CN network 106 e.g. a 5G core network
  • the first type of access network 120 uses a 3 GPP-defined type of wireless communication (e.g., NG-RAN comprising the cellular base unit 102a), while the second type of access network 130 uses a non-3 GPP-defined type of wireless communication (e.g., a wireless local area network (WLAN)AViFi, indicated by the access point 102b).
  • WLAN wireless local area network
  • the non-3 GPP access network 130 interfaces with the 5G core network via an interworking function 133 (N3IWF or TNGF) using the standard N2/N3 interfaces.
  • the multi-access data communication session may support additional access network types (such as non-terrestrial accesses), which are not shown.
  • the CN network 106 comprises a first user plane function network entity (UPF- 1) 141, a second user plane function network entity (UPF-2) 142, an AMF 143, an SMF 145, a policy control function network entity (PCF) 147 and a Unified Data Management network entity (UDM) 149.
  • UPF- 1 user plane function network entity
  • UPF-2 second user plane function network entity
  • AMF AMF
  • SMF policy control function network entity
  • UDM Unified Data Management network entity
  • the first type of access network 120 uses a 3GPP-defined type of wireless communication (e.g., NG-RAN comprising the cellular base unit 102a), while the second type of access network 130 uses a non-3 GPP-defined type of wireless communication (e.g., a wireless local area network (WLAN)AViFi.
  • a 3GPP-defined type of wireless communication e.g., NG-RAN comprising the cellular base unit 102a
  • a non-3 GPP-defined type of wireless communication e.g., a wireless local area network (WLAN)AViFi.
  • a multiaccess data connection 148 is established between the UE 104 and UPF-1 141 in the CN 106, which can support data communication using multiple access types simultaneously.
  • the multi-access data connection 148 supports two user-plane connections: one user-plane connection using communication over 3 GPP access 125 and another user-plane connection using communication over non-3 GPP access 135.
  • a MA PDU Session may have two or more user-plane connections, each one using communication over a different type of access network. Each user-plane connection creates an access path between the UE 104 and the UPF-1 141.
  • the PCF 147 creates steering rules for the Uplink (UL) traffic and steering rules for the Downlink (DL) traffic, which are forwarded to the UE 104 and to UPF-1 141, UPF-2 142, respectively.
  • the UL steering rules 108 are called ATSSS rules, and the DL steering rules 109 are called Multiaccess Access Rules (MAR).
  • MAR Multiaccess Access Rules
  • the steering rules specify how the UL traffic and how the DL traffic of the MA PDU Session is to be routed across the access paths of the MA PDU Session.
  • the UPF-1 141 is provided also with Forward Access Rules (FAR), which specify the uplink traffic that should be routed locally by UPF-1 141 (via its N6 interface) and the uplink traffic that should be forwarded to UPF-2 142.
  • FAR Forward Access Rules
  • the MA PDU Session enables the UE 104 to support multipath communication with a local host device 153 in a data network 150 and multipath communication with a remote host device 155 in the data network 150.
  • the local host device 153 may be located closer to the UE 104 than to the remote host device 155.
  • the local host device 153 may be an edge-computing computing device, whereas the remote host device 155 may be a centralized computing device.
  • Embodiments of the present disclosure enable MA PDU Sessions with multiple PSAs.
  • Such MA PDU Sessions can route data traffic to a DN via multiple N6 interfaces and, thus, enable (a) multi-access communication between the UE and edge-computing (local) services and (b) multipath communication between the UE and traditional centralized (remote) services.
  • FIG. 6 illustrates the protocol layers involved in a multi-access PDU session with multiple PSAs.
  • UPF-2 not only UPF-2, but also UPF-1 is enabled to function as a proxy and provide PSA functionality.
  • Both UPFs implement a steering functionality, for example, the QUIC-based steering functionality (as shown in Figure 6), or the MPTCP-based steering functionality.
  • the UE 104 is configured to send all data traffic of the MA PDU Session to the proxy (otherwise referred to herein as a proxy function) in UPF-1 141.
  • UPF-1 141 decides whether the received data traffic should be routed to the DN 150 via its local N6 interface, or whether it should be forwarded to the next proxy in UPF-2 142.
  • the UPF-1 141 makes these decisions based on information received from a SMF 145, which enable UPF-1 141 to operate also as an uplink classifier (UL CL).
  • UPF-1 141 is configured by the SMF 145 to know information about the proxy in UPF-2 142, such as its IP address, ports, etc.
  • the UE 104 establishes a number of multipath QUIC connections 602 with UPF-1 and UPF-1 establishes the same number of multipath QUIC connections 604 with UPF-2.
  • Each of these multipath QUIC connections carries the traffic of a particular QoS flow.
  • UPF-1 141 receives data traffic from UE via a multipath QUIC connection 602, it decides to either send it to the DN 150 via its local N6 interface, or to forward it to UPF-2 via an associated multipath QUIC connection 604.
  • the UE 104 establishes a MPTCP connection with UPF-1 141 for every TCP flow it wants to transmit via the MA PDU Session. If UPF-1 141 decides to forward a TCP flow to UPF-2 142, the UPF-1 141 establishes another MPTCP connection with UPF-2 142 and relays the TCP flow between these MPTCP connections. If UPF-1 141 decides to forward a TCP flow to its local N6 interface, then the MPTCP connection with UPF-2 142 is not required.
  • the UE 104 From the perspective of the UE 104, there is only one proxy (UPF-1). The UE 104 does not have visibility to, and does not need to, directly communicate with the proxy in UPF-2 142. The UE 104 does not need to know whether the MA PDU Session has one or multiple PSAs, hence, the UE behavior is not impacted by the enhancements in this disclosure.
  • control-plane procedures which define the exchange of signaling messages required to set up an MA PDU Session with multiple PSAs
  • user-plane procedures which define the exchange of data traffic after a MA PDU Session with multiple PSAs has been established.
  • Figure 7 illustrates a process 700 to establish a MA PDU Session with multiple PSAs (i.e. multiple UPFs).
  • the UE 104 registers with the 5G core network 106 over 3GPP access and/or over non-3GPP access using its 5GS credentials, stored in a USIM module.
  • the regular registration procedure is carried out.
  • an N1 connection is established over each access, and the UE 104 may securely exchange NAS messages with the AMF 143.
  • the UE 104 decides to establish a MA PDU Session.
  • the UE 104 transmits via the N1 connection an UL NAS Transport message to the AMF 143.
  • This message contains a PDU Session Establishment Request message to be forwarded to an SMF 145 comprising an MA PDU Session indication which indicates to AMF 143 this is a request for a multi -access (MA) PDU Session.
  • the UE 104 includes its ATSSS capabilities.
  • the UE 104 may include in the “5GSM capability” element that it supports traffic steering, switching, and splitting using the “MPQUIC-IP steering functionality” and/or the “MPTPC steering functionality”.
  • the access network that has been selected by the UE 104 to use for requesting the MA PDU Session i.e. either the 3GPP access network 120 or the non-3GPP access network 130
  • the AMF 143 selects an SMF 145 and transmits at step S708 a Create SM Context Request message to SMF 145, according to known techniques (see, e.g., 3GPP TS 23.502).
  • This message encapsulates the PDU Session Establishment Request provided by the UE 104. That is, at step S708, the SMF 145 receives a message requesting establishment of a multi-access communication session that supports data transmission between the UE 104 and data network 150 over a plurality of access paths. In response, at step S710 the SMF 145 sends a Create SM Context Response to the AMF 143.
  • the SMF 145 selects a PCF 147 and sends an SM Policy Control Create Request message to the PCF 147 for providing session management control information.
  • This message contains the MA PDU Request indication and the ATSSS capabilities of the UE 104, which were received by SMF 145 within the “5GSM capability” element.
  • the PCF 147 creates policy information e.g. one or more Policy and Charging Control (PCC rules) with “MA PDU Session Control” information indicating how the uplink traffic and how the downlink traffic should be routed across the various access paths of the MA PDU Session.
  • PCC rules Policy and Charging Control
  • a PCC rule may contain a Service Data Flow (SDF) Detection element that identifies the traffic matching this rule and additional elements indicating how the matching traffic should be handled.
  • SDF Service Data Flow
  • One of these additional elements is the “MA PDU Session Control” element, which identifies how the matching traffic should be routed across the various access paths of the MA PDU Session.
  • the PCF 147 takes into account the ATSSS capabilities of the UE 104 and the network policy.
  • the PCF 147 returns a SM Policy Control Create Response message to SMF 145 including the created PCC rules with MA PDU Session Control, which should be applied for the MA PDU Session.
  • the SMF 145 decides to select two PDU Session Anchors (PSAs) for the MA PDU Session, a first PSA and a second PSA.
  • PSAs PDU Session Anchors
  • the SMF may decide that, for example, because it wants the UE to be able to reach local services, via the first PSA, and remote services, via the second PSA, within the same DN 150.
  • the SMF 145 also selects an Uplink Classifier (UL CL), which will be receiving all uplink data flows from the UE 104 and will be forwarding each data flow either to the first PSA or to the second PSA.
  • UL CL Uplink Classifier
  • the SMF 145 typically selects two UPFs for the MA PDU Session.
  • the SMF 145 creates corresponding ATSSS rules for the UE 104, Multi-Access Rules (MAR) for UPF-2 142 and Multi- Access Rules (MAR) for UPF-1 141.
  • the ATSSS rules indicate to the UE 104 how to route uplink data traffic across the available accesses of the MA PDU Session.
  • the multi-access rules for UPF-2 indicate how UPF-2 should route the downlink data traffic arriving via its N6 interface across the available accesses of the MA PDU Session.
  • the multi-access rules for UPF-1 141 indicate how UPF-1 141 should route the downlink data traffic arriving via its N6 interface across the available accesses of the MA PDU Session. It is noted that when UPF-1 141 relays data traffic between the UE 104 and UPF-2 142, it does not take multi-access routing decisions, it just forwards the data traffic on the access type selected by the UE 104 or UPF-2 142.
  • the SMF 145 also creates Forward Action Rules (FAR) for UPF-1 141.
  • FAR Forward Action Rules
  • These rules are applied by the UL CL functionality in UPF-1 141 and indicate which uplink traffic should be forwarded to the N6 interface of UPF-1 (i.e., which traffic should not be relayed to UPF-2).
  • the forward action rules may be specified in accordance with 3GPP specifications (see e.g., TS 29.244).
  • the SMF 145 creates a Packet Forwarding Control Protocol (PFCP) session (also known as N4 session) with UPF-2 142 by sending a PFCP Session Establishment Request message (also referred to herein as a first session establishment request message) at step S722 that contains the created MAR for UPF-2 142, the DN Name (DNN) and a Provide ATSSS Control Information element.
  • PFCP Packet Forwarding Control Protocol
  • N4 session Packet Forwarding Control Protocol
  • the Provide ATSSS Control Information element indicates which ATSSS functionalities should be activated in UPF-2 142and information about each one. For example, it may indicate that the MPTCP functionality is required using a Transport Converter type of proxy, or that the MPQUIC functionality is required using a connect-udp or a connect-ip type of proxy. It may also indicate that the PMF functionality is required and that access performance measurements should be taken per QoS flow, including the identifiers for these QoS flows.
  • the PFCP Session Establishment Request message transmitted at step S722 contains (e.g., within the Provide ATSSS Control Information element) a new indication that indicates to UPF-2 that the allocated ATSSS resources will be used by another proxy (in UPF-1), not by the UE 104.
  • the message transmitted at step S722 requests information enabling UPF-1 141 to communicate withUPF- 142.
  • the indication included in the message transmitted at step S722 is need by UPF-2, for example, to allocate the appropriate IP addresses and ports so that the other proxy (in UPF-1) will be able to communicate with the proxy in UPF-2.
  • the UPF-2 142 accepts the request and responds at step S724 by transmitting a PFCP Session Establishment Response message (also referred to herein as a first session establishment response message) to the SMF 145, which includes an ATSSS Control Parameters element that comprises information to enable UPF-1 141 to communicate with UPF-2 142.
  • the ATSSS Control Parameters provides information about the ATSSS functionalities allocated in UPF-2 142.
  • the SMF 145 transmits a PFCP Session Establishment Request message (also referred to herein as a second session establishment request message) to UPF- 1 141, which will provide PSA functionality and the UL CL functionality.
  • This message contains the created MAR rules for UPF-1 141, the created Forward Action Rules (FAR) for UPF-1 142, the DN Name (DNN) and the Provide ATSSS Control Information element.
  • the Forward Action Rules (FAR) for UPF-1 141 indicate to UPF-1 141 which uplink traffic should be forwarded to its N6 interface (i.e., which traffic should not be relayed to UPF-2).
  • the PFCP Session Establishment Request message transmitted at step S726 also contains a data element which includes the information needed by UPF-1 141 to communicate UPF-2 142 with the proxy in UPF-2.
  • the UPF-1 implements a first proxy function
  • UPF-2 implements a second proxy function
  • the first proxy function communicates with the second proxy function using the information provided in the second session establishment request.
  • the first proxy function may comprise an MPTCP proxy and/or a MPQUIC proxy.
  • the second proxy function may comprise an MPTCP proxy and/or a MPQUIC proxy.
  • the data element may be created by the SMF 145 from the ATSSS Control Parameters provided by UPF-2 142 in step 724. After receiving the data element, the UPF-1 141 knows the IP addresses, the ports, the proxy type, and other information needed to communicate with the second proxy function implemented in UPF-2 142.
  • the UPF-1 141 accepts the PFCP Session Establishment Request message transmitted at step S726 and responds by transmitting a PFCP Session Establishment Response message (also referred to herein as a second session establishment response) to the SMF 145 at step S728.
  • the PFCP Session Establishment Response message includes its own ATSSS Control Parameters element that provides information about the ATSSS functionalities allocated in UPF-1 141The information in the ATSSS Control Parameters element will be provided to UE 104 so that it will be able to communicate with the first proxy function implemented in UPF-1.
  • the SMF 145 derives information, i.e.
  • UPF-1 Proxy Information which enables the UE 104 to communicate with the UPF-1 141 from the ATSSS Control Parameters element of the PFCP Session Establishment Response message received at step S728.
  • the UPF-1 Proxy Information contains the same parameters as those in the ATSSS Control Parameters element.
  • the ATSSS Control Parameters element provided by a UPF may contain: MPTCP Parameters, if the MPTCP steering functionality is enabled for the MA PDU Session. It contains: a. MPTCP Address Information: (a) the IP address for the MPTCP proxy in the UPF, (b) the port number of the MPTCP proxy in the UPF, and the type of MPTCP proxy in the UPF (i.e., Transport Converter). b. MPTCP Link-Specific IP Addresses: One IP address that the UE should be using for transmission over 3 GPP access and one IP address that the UE should be using for transmission over non-3GPP access. The UE uses these two IP addresses when transmitting data with MPTCP.
  • MPQUIC Parameters if the MPQUIC steering functionality is enabled for the MA PDU Session. It contains: c. MPQUIC Address Information: (a) the IP address for the MPQUIC proxy in the UPF, (b) the port number of the MPQUIC proxy in the UPF, and the type of MPQUIC proxy in the UPF (i.e., connect-ip or connect-upd). d. MPQUIC Link-Specific IP Addresses: One IP address that the UE should be using for transmission over 3 GPP access and one IP address that the UE should be using for transmission over non-3GPP access. The UE uses these two IP addresses when transmitting data with MPQUIC.
  • Performance Management Function Parameters, if Performance Measurements are enabled for the MA PDU Session. It contains: e. PMF Address Information: (a) the IP address for the PMF in the UPF, (b) the port number of PMF in the UPF to be used over 3GPP access, (c) the port number of PMF in the UPF to be used over non-3GPP access.
  • the ATSSS Control Parameters element provided by UPF-2 142 that are included in the PF CP Session Establishment Response message transmitted at step S724 includes the above elements.
  • the UPF-1 141 receives these parameters in PFCP Session Establishment Request message transmitted at step S726 and are used by UPF-1 to establish MPTCP/MPQUIC/PMF communication with UPF-2.
  • the MPTCP Address information, the MPQUIC Address information and the PMF Address information help the UPF-1 141 determine how to connect with the MPTCP, MPQUIC and PMF functionality in UPF-2 142, respectively.
  • the ATSSS Control Parameters element provided by UPF-1 141 that are included in the PFCP Session Establishment Response message transmitted at step S728 includes the above elements.
  • the UE 104 receives these parameters in the DL NAS Transport message transmitted at step S734 and are used by UE 104 to establish MPTCP/MPQUIC/PMF communication with UPF-1 141.
  • the MPTCP Address information, the MPQUIC Address information and the PMF Address information help the UE 104 determine how to connect with the MPTCP, MPQUIC and PMF functionality in UPF-1 141, respectively.
  • the SMF 145 creates a PDU Session Establishment Accept message for the UE 104 and encapsulates this message within an N1N2 Message Transfer Request, which is sent from the SMF 145 at step S730 to the AMF 143.
  • the PDU Session Establishment Accept message includes an ATSSS Container element that contains the created ATSSS rules and also contains Proxy Information (UPF-1 Proxy Information) that enables the UE 104 to communicate with the proxy in UPF-1.
  • Proxy Information UPF-1 Proxy Information
  • the AMF 143 requests from the access network (that has been selected by the UE 104 to use for requesting the MA PDU Session) to allocate the necessary resources for the MA PDU Session by transmitting, at step S732, a NGAP PDU Session Resource Setup Request message to the access network.
  • This message encapsulates a DL NAS Transport message to be sent to UE 104, which contains the PDU Session Establishment Accept message.
  • the MA PDU Session establishment procedure is completed by the UE 104 receiving the DL NAS Transport message transmitted, at step S734, from the AMF 143.
  • This message contains the PDU Session Establishment Accept message created by the SMF 145, which includes the ATSSS rules and Proxy Information (UPF-1 Proxy Information) that enables the UE 104 to communicate with the proxy in UPF-1.
  • Proxy Information UPF-1 Proxy Information
  • the UE 104 can start sending uplink data traffic to UPF-1 141, and UPF-2 142 can start sending downlink data traffic to UPF-1 141.
  • UPF-1 141 can start sending uplink data traffic to UPF-1 141.
  • UPF-2 142 can start sending downlink data traffic to UPF-1 141.
  • FIG 8 illustrates a process 800 to add a PSA to an existing MA PDU Session.
  • the MA PDU Session is initially established with one PSA (using known techniques)
  • embodiments of the present disclosure extend to the SMF 145 modifying the MA PDU Session so that a second PSA is added to the data path such that the MA PDU Session has multiple PSAs (i.e. multiple UPFs).
  • a known MA PDU Session establishment procedure is executed with one PSA using known techniques (see TS 23.502).
  • a MA PDU Session is established with UPF-2 142.
  • the SMF 145 determines to add a second PSA to the already established MA PDU Session. This determination may be based on the location of the UE 104. After this determination, the SMF 145 selects a UPF (UPF-1) which is going to implement the UE CL functionality and the second PSA functionality.
  • UPF UPF-1
  • the SMF 145 creates Multi-Access Rules (MAR) for UPF-1.
  • MAR Multi-Access Rules
  • step S808 the SMF 145 creates Forward Action Rules (FAR) for UPF-1.
  • FAR Forward Action Rules
  • the SMF 145 modifies the Packet Forwarding Control Protocol (PFCP) session (also known as N4 session) with UPF-2 142 by transmitting, at step S810, a PFCP Session Modification Request message to UPF-2 142.
  • PFCP Session Modification Request message comprises a Provide ATSSS Control Information element and, optionally, new Multi-Access Rules for UPF-2 if they should be updated.
  • the Provide ATSSS Control Information element indicates which ATSSS functionalities should be activated in UPF-2 and information about each one.
  • the PFCP Session Modification message contains (e.g., within the Provide ATSSS Control Information element) a new indication that indicates to UPF-2 that the allocated ATSSS resources will be used by another proxy (in UPF-1), not by the UE 104.
  • the message transmitted at step S810 requests information enabling UPF-1 141 to communicate with UPF- 142. This indication is need by UPF-2, for example, to allocate the appropriate IP addresses and ports so that the other proxy (in UPF-1) will be able to communicate with the proxy in UPF-2.
  • the UPF-2 accepts the PFCP Session Modification Request and responds by transmitting, at step S812, a PFCP Session Modification Response message to the SMF 145, which includes an ATSSS Control Parameters element.
  • the ATSSS Control Parameters element provides information about the ATSSS functionalities allocated in UPF-2. That is, PFCP Session Modification Response message comprises information enabling the UPF-1 141 to communicate with UPF-2 142.
  • the SMF 145 transmits a PFCP Session Establishment Request message to UPF-1 141, which will provide the second PSA functionality and the UL CL functionality.
  • the PFCP Session Establishment Request message contains the created MAR for UPF-1, the created Forward Action Rules (FAR) for UPF-1, the DN Name (DNN) and the Provide ATSSS Control Information element.
  • the Forward Action Rules (FAR) for UPF- 1 indicate to UPF-1 which uplink traffic should be forwarded to its N6 interface (i.e., which traffic should not be relayed to UPF-2).
  • the PFCP Session Establishment Request message transmitted at step S814 also contains a data element which includes the information needed by UPF - 1 141 to communicate with the proxy in UPF -2 142.
  • the data element may be created by the SMF 145 from the ATSSS Control Parameters provided by UPF-2 142 at step S812. After receiving the data element, the UPF-1 knows the IP addresses, the ports, the proxy type, and other information needed to communicate with the proxy in UPF-2 142.
  • the UPF-1 accepts the PFCP Session Establishment Request message transmitted at step S814 and responds by transmitting a PFCP Session Establishment Response message to the SMF 145 at step S816.
  • the PFCP Session Establishment Response message transmitted at step S816 includes information enabling the UE 104 to communicate with the UPF-1 141 e.g. by including its own ATSSS Control Parameters element that provides information about the ATSSS functionalities allocated in UPF-1 141.
  • the SMF 145 creates a PDU Session Modification Command message for the UE 104 and encapsulates this message within an N1N2 Message Transfer Request, that is sent from the SMF 145 at step S818 to the to the AMF 143.
  • the PDU Session Modification Command message contains Proxy Information (UPF-1 Proxy Information) that enables the UE 104 to communicate with the new proxy in UPF-1 141. That is, the PDU Session Modification Command message includes the information enabling the UE 104 to communicate with the UPF-1 141 received by the SMF 145 at step S816. It may also include an ATSSS Container element that contains updated ATSSS rules if there is need to update these rules.
  • the AMF 143 transmits to any of the available access networks a NGAP Downlink NAS Transport message, which encapsulates a DL NAS Transport message to be sent to the UE 104 that contains the PDU Session Modification Command.
  • the MA PDU Session modification procedure is completed by the UE 104 receiving, at step S822, the DL NAS Transport message from the AMF 143 via the access network.
  • the DL NAS Transport message contains the PDU Session Modification Command created by the SMF 145, which includes Proxy Information (UPF-1 Proxy Information) that enables the UE 104 to communicate with the proxy in UPF-1 141 and, optionally, the updated ATSSS rules.
  • Proxy Information UPF-1 Proxy Information
  • the UE 104 responds by transmitting at step S824 an UL NAS Transport message that contains a PDU Session Modification Complete message.
  • the access network 120,130 forwards the UL NAS Transport message to the AMF 143 within a NGAP Uplink NAS Transport message.
  • the AMF 143 transmits an Update SM Context Request message to the SMF 145.
  • This message encapsulates the PDU Session Modification Complete message provided by the UE 104. That is, the PDU Session Modification Complete message is relayed to the SMF 145 by the AMF 143.
  • the SMF 145 responds by transmitting an Update SM Context Response message to the AMF 143.
  • the UE 104 should stop using communication with UPF-2 and should initiate communication with UPF-1 using the information received at step S822 i.e. the proxy Information (UPF-1 Proxy Information) that enables the UE 104 to communicate with the proxy in UPF-1 141.
  • the proxy Information UPF-1 Proxy Information
  • Figure 9 illustrates user plane data flow with two PSAs when MPQUIC steering functionality is applied in the MA PDU Session using a connect-ip proxy so it can support all types of IP traffic (including IP/TCP, IP/UDP, etc.).
  • the MPQUIC steering functionality can be applied in the MA PDU Session using a connect-udp proxy so it can support only IP/UDP traffic (not shown in Figure 9).
  • a MA PDU Session with two PSAs is established.
  • the MA PDU Session with two PSAs may be established using any of the methods described herein.
  • the UE 104 requests the establishment of one or more multipath QUIC connections, as specified in the present 3GPP specifications (e.g., TS 23.501).
  • the UE 104 applies the proxy information received in the PDU Session Establishment Accept message, so the multipath QUIC connections are established between the UE 104 and UPF-1 141.
  • the UPF-1 141 establishes the same number of multipath QUIC connections with UPF-2 142 by applying its own proxy information (e.g. proxy information received at step S726.
  • proxy information e.g. proxy information received at step S726.
  • the UE 104 sends an HTTP CONNECT request in order to establish an IP tunnel over HTTP with the proxy in UPF-1 141.
  • the “:protocol” pseudo-header in this request is set to “connect-ip” as defined in draft-ietf-masque-connect-ip.
  • the UPF-1 receives an HTTP CONNECT request from the UE 104 over a multipath QUIC connection, at step S910 it sends another HTTP CONNECT request to UPF-2 141 over a corresponding multipath QUIC connection, in order to establish another IP tunnel over HTTP with the proxy in UPF-2 141.
  • UPF-2 141 If the IP tunnel is accepted by UPF-2 141, at step S912 UPF-2 141 responds with an HTTP 200 message, which triggers UPF-1 141 to accept the IP tunnel requested by the UE 104 and to respond by transmitting another HTTP 200 message, at step S914 to the UE 104.
  • a "communication tunnel” can be either an IP communication tunnel that supports all types of IP traffic (UDP, TCP, etc.), or a UDP communication tunnel that supports only UDP traffic.
  • the type of the communication tunnel depends on the type of proxy configured in UPF-1 and UPF-2 ("connect-udp" or "connect-ip” respectively).
  • the type of proxy for the communication session is determined by SMF 145 and can be indicated to UPF-1 and UPF-2 within the "Provide ATSSS Control Information" element in PFCP Session Establishment Request messages (e.g. transmitted at steps S722 and S726).
  • Each of the one or more multipath QUIC connections established at step S904 supports data communication between the UE 104 and UPF-1 141 overthe plurality of access paths (e.g. 3GPP access path 125 and non-3GPP access path 135).
  • each of the one or more multipath QUIC connections established at step S906 support data communication between UPF-1 141 and UPF-2 142 over a corresponding one of the plurality of access paths.
  • Data traffic received at UPF-1 141 from UE 104 via a multipath QUIC connection between the UE 104 and UPF-1 141 is forwarded to UPF-2 via the associated multipath QUIC connection in the second set.
  • UPF-1 141 data traffic received at UPF-1 141 from UPF- 2 142 via a multipath QUIC connection UPF-1 141 and UPF-2 142 is forwarded to UE 104 via the associated multipath QUIC connection between the UE 104 and UPF-1 141.
  • IP packet 1 IP packet 1
  • UPF-1 141 the UE 104 sends an IP packet (IP packet 1) to UPF-1 141 via the established IP tunnel over a multipath QUIC connection and encapsulated within a QUIC Datagram frame.
  • the UPF-1 decrypts and decapsulates the IP packet and applies its Forward Action Rules (FAR) to determine how to handle this packet.
  • FAR Forward Action Rules
  • the UPF-1 141 decides to forward the IP packet to its local N6 interface and at step S920 transmits the IP packet (IP packet 1) to the DN 150 (e.g. to a local host device 153).
  • the UE 104 sends another IP packet (IP packet 2) to UPF-1 141 via the established IP tunnel over a multipath QUIC connection and encapsulated within a QUIC Datagram frame.
  • the UPF-1 141 decrypts and decapsulates the IP packet and applies again its Forward Action Rules (FAR) to determine how to handle this packet.
  • FAR Forward Action Rules
  • the UPF-1 decides to forward the IP packet to the next proxy (UPF-2).
  • UPF-2 encapsulates the IP packet into another QUIC Datagram frame and at step S926 sends it to UPF-2 via the established IP tunnel over a corresponding multipath QUIC connection.
  • the UPF-2 decrypts and decapsulates the IP packet and at step S928 forwards it to its local N6 interface.
  • FIG. 9 illustrates how UPF-1 handles uplink traffic, but for completeness we also describe herein how UPF-1 handles downlink traffic.
  • the UPF-1 141 applies its Multi-Access Rules (MAR) to determine the access path (i.e., the N3 interface) over which it should be forwarded to UE 104. Based on these rules, the UPF-1 141 determines to forward the IP packet to the UE 104 either via an N3 interface associated with 3GPP access, or via an N3 interface associated with non-3GPP access.
  • MAR Multi-Access Rules
  • the UPF-2 applies its Multi- Access Rules (MAR) to determine the access path (i.e., the N9 interface) over which it should be forwarded to UPF-1 141.
  • MAR Multi- Access Rules
  • the UPF-1 receives the IP packet, it forwards it to the UE 104 via a corresponding access path. For example, if UPF-1 receives the IP packet over an N9 interface associated with 3GPP access, it forwards it to UE 104 via an N3 interface associated also with 3GPP access.
  • Figure 10 illustrates the protocol layers involved in the user-plane communication via a MA PDU Session with two PSAs in the example where the MPQUIC steering functionality is applied.
  • Figure 10 shows the one or more multipath QUIC connections 1002 established at step S904 between the UE 104 and UPF-1 141, and the one or more multipath QUIC connections 1004 established at step S906 between the UPF-1 141 to UPF-2 142
  • the UE 104 transmits two different IP flows (a first IP flow 1006 and a second IP flow 1008), each one composed of IP packets with the same 5 -tuple.
  • the first IP flow 1006 and the second IP flow 1008 may comprise IP packets comprising data of different data formats.
  • the first IP flow 1006 may comprise IP packets comprising audio data
  • the second IP flow 1008 may comprise IP packets comprising video data.
  • the first IP flow 1006 and the second IP flow 1008 may be destined for different destinations.
  • the first IP flow 1006 may be destined to a remote host device 155 in the DN 150 and the second IP flow 1008 may be destined to a local host device 153 in the DN 150.
  • the UPF-1 141 implements a first proxy function 1003 and the UPF-2 142 implements a second proxy function 1005.
  • the first proxy function 1003 is a connect-ip type of proxy and the second proxy function 1005 is also a connect-ip type of proxy.
  • the packets of each IP flow may be split across the two access paths, as shown in Figure 10.
  • some of the packets of first IP flow 1006 and some of the packets of the second IP flow 1008 may be transmitted over the non-3GPP access path (via the non- 3 GPP access network 130), and some of the packets of first IP flow 1006 and some of the packets of the second IP flow 1008 may be transmitted over the 3GPP access path (via the 3 GPP access network.
  • the QUIC layer in UPF-1 receives each of these IP packets (within a QUIC Datagram frame), and forwards them to the first proxy function 1003 (HTTP/3 proxy), which terminates the IP tunnel with the UE 104.
  • the UL CL layer 1006 in UPF-1 141 applies the Forward Action Rules (FAR) received from SMF 145 and determines how to forward each IP packet.
  • FAR Forward Action Rules
  • IP packet should be forwarded by UPF-1 141 to UPF-2 142, it enters again the QUIC layer where it is encapsulated into another QUIC Datagram frame and is sent to UPF-2 142 via a multipath QUIC connection 1004. If an IP packet should be forwarded by UPF-1 141 to DN 150 via the local N6 interface, it enters the protocol stack of the N6 interface. Similar operation applies for the IP flows in the downlink direction (IP flows received in the UE).
  • FIG 11 illustrates user plane data flow with two PSAs when MPTCP steering functionality is applied in the MA PDU Session either in addition to, or instead of, the MPQUIC steering functionality described above.
  • a MA PDU Session with two PSAs is established.
  • the MA PDU Session with two PSAs may be established using any of the methods described herein.
  • the UE 104 wants to establish a TCP connection with a device (e.g. Host 1) in the DN 150. Since the UE 104 is configured to use an MPTCP proxy in UPF-1 141, at step SI 102 the UE 104 sends a message to UPF-1 requesting a TCP connection to Host 1 in the DN 150. In particular, at step SI 102 the UE 104 transmits an IP packet to UPF-1 141 containing a TCP message with the SYN flag set, with a MPTCP option, and with identifiers of Host 1 in the data element.
  • a device e.g. Host 1
  • the identifiers associated with the device may be the IP address of the device and a target TCP port in the device. Instead of an IP address of the device (e.g. "192.2.3.4"), the TCP message may contain a domain name for the device (e.g. "www.example.com”).
  • the UPF-1 141 decides to establish the requested TCP connection with Host 1 directly via its N6 interface. For this purpose, at step SI 106 the UPF-1 sends to Host 1 another IP packet containing a TCP message with the SYN flag set and with the MPTCP option. The Host 1 accepts the TCP connection request and responds at step SI 108 with another IP packet containing a TCP message with the SYN and ACK flags set.
  • the UPF-1 141 transmits an IP packet containing a TCP message with the SYN and ACK flags set and with the MPTCP option.
  • UE 104 transmits an IP packet containing a TCP message with the ACK flag set to the UPF-1 141, which is relayed by the UPF-1 141 at step SI 114 to Host 1 in the DN 150.
  • a first MPTCP connection is established between the UE 104 and UPF-1 141
  • a second TCP connection is established between UPF- 1 141 and Host 1. These two TCP connections are bound together in UPF-1, which relays TCP messages between these connections.
  • the second TCP connection established between UPF-1 141 and Host 1 may or may not to be a MPTCP connection depending on the capabilities of Host 1.
  • the UE 104 wants to establish a TCP connection with a device (e.g. Host 2) in the DN 150. Since the UE 104 is configured to use an MPTCP proxy in UPF-1, at step SI 120 the UE 104 sends a message to UPF-1 requesting a TCP connection to Host 2 in the DN 150. In particular, at step SI 120 the UE 104 transmits an IP packet containing a TCP message with the SYN flag set, with the MPTCP option, and with the identifiers of Host 2 in the data element.
  • the identifiers associated with the device (Host 2) may be the IP address of the device and a target TCP port in the device. Instead of an IP address of the device (e.g. "192.2.3.4"), the TCP message may contain a domain name for the device (e.g. "www.example.com").
  • the UPF-1 decides to establish the requested TCP connection with Host 2 via the proxy in UPF-2 142.
  • the UPF-1 141 sends to UPF-2 142 another IP packet containing a TCP message with the SYN flag set, with the MPTCP option, and with the address and port of Host 2 in the data element.
  • UPF-2 sends to Host 2 another IP packet containing a TCP message with the SYN flag set and with the MPTCP option.
  • the Host 2 accepts the TCP connection request and responds at step SI 128 with another IP packet containing a TCP message with the SYN and ACK flags set.
  • the UPF-2 142 transmits an IP packet containing a TCP message with the SYN and ACK flags set and with the MPTCP option to UPF-1 141 which is then relayed to the UE 104 at step SI 132.
  • a first MPTCP connection is established between the UE 104 and UPF-1 141
  • a second MPTCP connection is established between UPF-1 141 and UPF-2 142
  • a third TCP connection is established between UPF-2 142 and Host 2 in the DN 150.
  • the first and the second MPTCP connections are bound together in UPF-1, while the second and the third TCP connections are bound together in UPF-2.
  • the first MPTCP connection and the second MPTCP connection are associated in that whatever data is received at the UPF-1 141 on one of them is forwarded on to the other.
  • FIG. 12 illustrates an example of a processor 1200 in accordance with aspects of the present disclosure.
  • the processor 1200 may be an example of a processor configured to perform various operations in accordance with examples as described herein.
  • the processor 1200 may include a controller 1202 configured to perform various operations in accordance with examples as described herein.
  • the processor 1200 may optionally include at least one memory 1204, which may be, for example, an L1/L2/L3 cache. Additionally, or alternatively, the processor 1200 may optionally include one or more arithmetic-logic units (ALUs) 1206.
  • ALUs arithmetic-logic units
  • One or more of these components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).
  • the processor 1200 may be a processor chipset and include a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) in accordance with examples as described herein.
  • a protocol stack e.g., a software stack
  • operations e.g., receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading
  • the processor chipset may include one or more cores, one or more caches (e.g., memory local to or included in the processor chipset (e.g., the processor 1200) or other memory (e.g., random access memory (RAM), read-only memory (ROM), dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), static RAM (SRAM), ferroelectric RAM (FeRAM), magnetic RAM (MRAM), resistive RAM (RRAM), flash memory, phase change memory (PCM), and others).
  • RAM random access memory
  • ROM read-only memory
  • DRAM dynamic RAM
  • SDRAM synchronous dynamic RAM
  • SRAM static RAM
  • FeRAM ferroelectric RAM
  • MRAM magnetic RAM
  • RRAM resistive RAM
  • flash memory phase change memory
  • PCM phase change memory
  • the controller 1202 may be configured to manage and coordinate various operations (e.g., signaling, receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) of the processor 1200 to cause the processor 1200 to support various operations in accordance with examples as described herein.
  • the controller 1202 may operate as a control unit of the processor 1200, generating control signals that manage the operation of various components of the processor 1200. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating timing of operations.
  • the controller 1202 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from the memory 1204 and determine subsequent instruct! on(s) to be executed to cause the processor 1200 to support various operations in accordance with examples as described herein.
  • the controller 1202 may be configured to track memory address of instructions associated with the memory 1204.
  • the controller 1202 may be configured to decode instructions to determine the operation to be performed and the operands involved.
  • the controller 1202 may be configured to interpret the instruction and determine control signals to be output to other components of the processor 1200 to cause the processor 1200 to support various operations in accordance with examples as described herein.
  • the controller 1202 may be configured to manage flow of data within the processor 1200.
  • the controller 1202 may be configured to control transfer of data between registers, arithmetic logic units (ALUs), and other functional units of the processor 1200.
  • ALUs arithmetic logic units
  • the memory 1204 may store computer-readable, computer-executable code including instructions that, when executed by the processor 1200, cause the processor 1200 to perform various functions described herein.
  • the code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory.
  • the controller 1202 and/or the processor 1200 may be configured to execute computer-readable instructions stored in the memory 1204 to cause the processor 1200 to perform various functions.
  • the processor 1200 and/or the controller 1202 may be coupled with or to the memory 1204, the processor 1200, the controller 1202, and the memory 1204 may be configured to perform various functions described herein.
  • the processor 1200 may include multiple processors and the memory 1204 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions herein.
  • One or more ALUs 1206 be configured with a variety of logical and arithmetic circuits, including adders, subtractors, shifters, and logic gates, to process and manipulate the data according to the operation. Additionally, or alternatively, the one or more ALUs 1206 may support logical operations such as AND, OR, exclusive-OR (XOR), not-OR (NOR), and not- AND (NAND), enabling the one or more ALUs 1206 to handle conditional operations, comparisons, and bitwise operations.
  • the processor 1200 may support wireless communication in accordance with examples as disclosed herein. The processor 1200 may be configured to or operable to support a means for performing the methods described herein.
  • the processor 1302, the memory 1304, the controller 1306, or the transceiver 1308, or various combinations or components thereof may be implemented in hardware (e.g., circuitry).
  • the hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.
  • DSP digital signal processor
  • ASIC application-specific integrated circuit
  • the processor 1302 may include an intelligent hardware device (e.g., a general- purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof). In some implementations, the processor 1302 may be configured to operate the memory 1304. In some other implementations, the memory 1304 may be integrated into the processor 1302. The processor 1302 may be configured to execute computer-readable instructions stored in the memory 1304 to cause the NE 1300 to perform various functions of the present disclosure. [0160] The memory 1304 may include volatile or non-volatile memory. The memory 1304 may store computer-readable, computer-executable code including instructions when executed by the processor 1302 cause the NE 1300 to perform various functions described herein.
  • an intelligent hardware device e.g., a general- purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof.
  • the processor 1302 may be configured to operate the memory 1304.
  • the memory 1304 may be integrated into the processor 1302.
  • the processor 1302 may be configured to
  • the code may be stored in a non-transitory computer-readable medium such the memory 1304 or another type of memory.
  • Computer-readable media includes both non- transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another.
  • a non-transitory storage medium may be any available medium that may be accessed by a general-purpose or specialpurpose computer.
  • the processor 1302 and the memory 1304 coupled with the processor 1302 may be configured to cause the NE 1300 to perform one or more of the functions described herein (e.g., executing, by the processor 1302, instructions stored in the memory 1304).
  • the processor 1302 may support wireless communication at the NE 1300 in accordance with examples as disclosed herein.
  • the NE 1300 may be configured to support a means for receiving a request message to establish a multiaccess communication session for a user equipment (UE) and a data network; selecting a first user plane function (UPF) and a second UPF for the multi-access communication session, wherein the first UPF and second UPF are configured to route data associated with the multiaccess communication session and the data network; transmitting first multi-access rules and forward -action rules to the first UPF; transmitting second multi-access rules to the second UPF; and transmitting a response that indicates an acceptance to establish the multi -access communication session, wherein the response comprises information that enables the UE to communicate with the first UPF.
  • UPF user plane function
  • the NE 1300 may be configured to support a means for determining to add a first user plane function (UPF) to a multi-access communication session established for a user equipment (UE), a second UPF and a data network, wherein the first UPF and the second UPF are configured to route data associated with the multi-access communication session and the data network; transmitting first multi -access rules and forward -action rules to the first UPF; and transmitting a message that comprises information that enables the UE to communicate with the first UPF.
  • UPF user plane function
  • the NE 1300 may be configured to support a means for establishing a multi-access communication session with a user equipment (UE) and a further user plane function network entity, the multi-access communication session supporting data transmission between the UE and a data network over a plurality of access paths; receiving a data message via a first access path for transmission to the data network; determining whether to transmit the data message directly to the data network or to the data network via the further user plane function network entity; and in response to a determination to transmit the data message to the data network via the further user plane function network entity, transmitting the data message to the further user plane function network entity via a second access path having the same access path type as the first access path.
  • UE user equipment
  • the NE 1300 may be configured to support a means for establishing a multi-access communication session with a user equipment (UE) and a further user plane function network entity, the multi-access communication session supporting data transmission between the UE and a data network over a plurality of access paths; receiving a data message via a first
  • the NE 1300 may be configured to support a means for establishing a multi-access communication session with a user equipment (UE) and a further user plane function network entity, the multi-access communication session supporting data transmission between the UE and a data network over a plurality of access paths; receiving a TCP message from the UE requesting a TCP connection to a device in the data network; determining to establish the TCP connection directly with the device in the data network; and in response to said determination, establishing a first TCP connection with the UE and establishing a second TCP connection with the device, wherein the first TCP connection supports multipath communication over the plurality of access paths.
  • UE user equipment
  • a further user plane function network entity the multi-access communication session supporting data transmission between the UE and a data network over a plurality of access paths
  • the NE 1300 may be configured to support a means for establishing a multi-access communication session with a user equipment (UE) and a further user plane function network entity, the multi-access communication session supporting data transmission between the UE and a data network over a plurality of access paths; receiving a message from the UE requesting a TCP connection to a device in the data network; determining to establish the TCP connection to the device in the data network via the further user plane function network entity; and in response to said determination, establishing a first multipath TCP connection with the user equipment and an associated second multipath TCP connection with the further user plane function network entity, wherein the first and the second multipath TCP connections support multipath communication over the plurality of access paths.
  • UE user equipment
  • a further user plane function network entity the multi-access communication session supporting data transmission between the UE and a data network over a plurality of access paths
  • the controller 1306 may manage input and output signals for the NE 1300.
  • the controller 1306 may also manage peripherals not integrated into the NE 1300.
  • the controller 1306 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems.
  • the controller 1306 may be implemented as part of the processor 1302.
  • the NE 1300 may include at least one transceiver 1308.
  • the NE 1300 may have more than one transceiver 1308.
  • the transceiver 1308 may represent a wireless transceiver.
  • the transceiver 1308 may include one or more receiver chains 1310, one or more transmitter chains 1312, or a combination thereof.
  • a receiver chain 1310 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium.
  • the receiver chain 1310 may include one or more antennas for receive the signal over the air or wireless medium.
  • the receiver chain 1310 may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal.
  • the receiver chain 1310 may include at least one demodulator configured to demodulate the receive signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal.
  • the receiver chain 1310 may include at least one decoder for decoding the processing the demodulated signal to receive the transmitted data.
  • a transmitter chain 1312 may be configured to generate and transmit signals (e.g., control information, data, packets).
  • the transmitter chain 1312 may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium.
  • the at least one modulator may be configured to support one or more techniques such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes like phase-shift keying (PSK) or quadrature amplitude modulation (QAM).
  • the transmitter chain 1312 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium.
  • the transmitter chain 1312 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.
  • Figure 14 illustrates a flowchart of a method in accordance with aspects of the present disclosure.
  • the operations of the method of Figure 14 may be implemented by a NE as described herein (e.g. a SMF 145).
  • the NE may execute a set of instructions to control the function elements of the NE to perform the described functions.
  • the method may include receiving a request message to establish a multiaccess communication session for a user equipment (UE) and a data network.
  • UE user equipment
  • the operations of 1402 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1402 may be performed by a NE as described with reference to Figure 13.
  • the method may include selecting a first user plane function (UPF) and a second UPF for the multi-access communication session, wherein the first UPF and the second UPF are configured to route data associated with the multi-access communication session and the data network.
  • the operations of 1404 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1404 may be performed by a NE as described with reference to Figure 13.
  • the method may include transmitting first multi -access rules and forward -action rules to the first UPF.
  • the operations of 1406 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1406 may be performed by a NE as described with reference to Figure 13.
  • the method may include transmitting second multi-access rules to the second UPF.
  • the operations of 1408 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1408 may be performed by a NE as described with reference to Figure 13.
  • the method may include transmitting a response message that indicates an acceptance to establish the multi-access communication session, wherein the response message comprises information that enables the UE to communicate with the first UPF.
  • the operations of 1410 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1410 may be performed by a NE as described with reference to Figure 13.
  • Figure 15 illustrates a flowchart of a method in accordance with aspects of the present disclosure.
  • the operations of the method of Figure 15 may be implemented by a NE as described herein (e.g. a SMF 145).
  • the NE may execute a set of instructions to control the function elements of the NE to perform the described functions.
  • the method may include determining to add a first user plane function (UPF) to a multi-access communication session established for a user equipment (UE), a second UPF and a data network, wherein the first UPF and the second UPF are configured to route data associated with the multi-access communication session and the data network.
  • UPF user plane function
  • the operations of 1502 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1502 may be performed by a NE as described with reference to Figure 13.
  • the method may include transmitting first multi -access rules and forward-action rules to the first UPF.
  • the operations of 1504 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1504 may be performed by a NE as described with reference to Figure 13.
  • the method may include transmitting a message that comprises information that enables the UE to communicate with the first UPF.
  • the operations of 1506 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1506 may be performed by a NE as described with reference to Figure 13.
  • Figure 16 illustrates a flowchart of a method in accordance with aspects of the present disclosure.
  • the operations of the method of Figure 16 may be implemented by a NE as described herein (e.g. UPF-1 141).
  • the NE may execute a set of instructions to control the function elements of the NE to perform the described functions.
  • the method may include establishing a multi-access communication session with a user equipment (UE) and a further user plane function network entity, the multi-access communication session supporting data transmission between the UE and a data network over a plurality of access paths.
  • UE user equipment
  • the operations of 1602 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1602 may be performed by a NE as described with reference to Figure 13.
  • the method may include receiving a data message via a first access path for transmission to the data network.
  • the operations of 1604 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1604 may be performed by a NE as described with reference to Figure 13.
  • the method may include determining whether to transmit the data message directly to the data network or to the data network via the further user plane function network entity.
  • the operations of 1606 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1606 may be performed by a NE as described with reference to Figure 13.
  • the method may include in response to a determination to transmit the data message to the data network via the further user plane function network entity, transmitting the data message to the further user plane function network entity via a second access path having the same access path type as the first access path.
  • the operations of 1608 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1608 may be performed by a NE as described with reference to Figure 13.
  • Figure 17 illustrates a flowchart of a method in accordance with aspects of the present disclosure.
  • the operations of the method of Figure 17 may be implemented by a NE as described herein (e.g. UPF-1 141).
  • the NE may execute a set of instructions to control the function elements of the NE to perform the described functions.
  • the method may include establishing a multi-access communication session with a user equipment (UE) and a further user plane function network entity, the multi-access communication session supporting data transmission between the UE and a data network over a plurality of access paths.
  • UE user equipment
  • the operations of 1702 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1702 may be performed by a NE as described with reference to Figure 13.
  • the method may include receiving a TCP message from the UE requesting a TCP connection to a device in the data network.
  • the operations of 1704 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1704 may be performed by a NE as described with reference to Figure 13.
  • the method may include determining to establish the TCP connection directly with the device in the data network.
  • the operations of 1706 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1706 may be performed by a NE as described with reference to Figure 13.
  • the method may include in response to said determination, establishing a first TCP connection with the UE and establish a second TCP connection with the device, wherein the first TCP connection supports multipath communication over the plurality of access paths.
  • the operations of 1708 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1708 may be performed by a NE as described with reference to Figure 13.
  • Figure 18 illustrates a flowchart of a method in accordance with aspects of the present disclosure.
  • the operations of the method of Figure 18 may be implemented by a NE as described herein (e.g. UPF-1 141).
  • the NE may execute a set of instructions to control the function elements of the NE to perform the described functions.
  • the method may include establishing a multi-access communication session with a user equipment (UE) and a further user plane function network entity, the multi-access communication session supporting data transmission between the UE and a data network over a plurality of access paths.
  • UE user equipment
  • the operations of 1802 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1802 may be performed by a NE as described with reference to Figure 13.
  • the method may include receiving a message from the UE requesting a TCP connection to a device in the data network.
  • the operations of 1804 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1804 may be performed by a NE as described with reference to Figure 13.
  • the method may include determining to establish the TCP connection to the device in the data network via the further user plane function network entity.
  • the operations of 1806 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1806 may be performed by a NE as described with reference to Figure 13.
  • the method may include in response to said determination, establishing a first multipath TCP connection with the user equipment and an associated second multipath TCP connection with the further user plane function network entity, wherein the first and the second multipath TCP connections support multipath communication over the plurality of access paths.
  • the operations of 1808 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1808 may be performed by a NE as described with reference to Figure 13.

Landscapes

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

Abstract

Divers aspects de la présente divulgation concernent une entité de réseau pour une communication sans fil, comprenant : au moins une mémoire; et au moins un processeur couplé à la ou aux mémoires et configuré pour amener l'entité de réseau à : recevoir un message de demande pour établir une session de communication multi-accès pour un équipement utilisateur (UE) et un réseau de données; sélectionner une première fonction de plan d'utilisateur (UPF) et une seconde UPF pour la session de communication multi-accès, la première UPF et la seconde UPF étant configurées pour acheminer des données associées à la session de communication multi-accès et au réseau de données; transmettre des premières règles multi-accès et des règles d'action directe à la première UPF; transmettre des secondes règles multi-accès à la seconde UPF; et transmettre un message de réponse qui indique une acceptation pour établir la session de communication multi-accès, le message de réponse comprenant des informations qui permettent à l'UE de communiquer avec la première UPF.
PCT/EP2023/080837 2023-10-11 2023-11-06 Session de communication multi-accès Pending WO2024193841A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
GR20230100832 2023-10-11
GR20230100832 2023-10-11

Publications (1)

Publication Number Publication Date
WO2024193841A1 true WO2024193841A1 (fr) 2024-09-26

Family

ID=88697852

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2023/080837 Pending WO2024193841A1 (fr) 2023-10-11 2023-11-06 Session de communication multi-accès

Country Status (1)

Country Link
WO (1) WO2024193841A1 (fr)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4236587A2 (fr) * 2017-07-10 2023-08-30 Motorola Mobility LLC Connexion de données à accès multiples dans un réseau mobile

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4236587A2 (fr) * 2017-07-10 2023-08-30 Motorola Mobility LLC Connexion de données à accès multiples dans un réseau mobile

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
3GPP SPECIFICATIONS (SEE E.G., TS 29.244
3GPP TS 23.502
APOSTOLIS SALKINTZIS ET AL: "Introduction of the MPQUIC Steering Functionality", vol. 3GPP SA 2, no. Online; 20230116 - 20230120, 9 January 2023 (2023-01-09), XP052232211, Retrieved from the Internet <URL:https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_154AHE_Electronic_2023-01/Docs/S2-2300742.zip S2-2300742_23501_ATSSS_Architecture_v4.docx> [retrieved on 20230109] *

Similar Documents

Publication Publication Date Title
WO2024094231A1 (fr) Procédés et appareils pour un mécanisme de découverte dans un boîtier de relais avec de multiples sauts
WO2024087745A1 (fr) Procédé et appareil de prise en charge de rapport de temps d&#39;arrivée de rafale (bat)
WO2024235491A1 (fr) Enregistrement d&#39;équipement utilisateur
WO2024245615A1 (fr) Établissement de session de données dans un réseau de communication sans fil
WO2024193841A1 (fr) Session de communication multi-accès
WO2024188482A1 (fr) Session de communication à accès multiples
US20250220736A1 (en) Techniques for sequence numbering with packet duplication and reordering for udp packets
WO2025123726A1 (fr) Procédés et appareils de mappage de qos et de réglage de qos pour nœud mwab
WO2025030889A1 (fr) Double connectivité dans une architecture basée sur un service
US20240406068A1 (en) Techniques for determining network support for ue policy sections over eps
US20250159581A1 (en) Ambient internet of things (iot) device integration
US20250358726A1 (en) Techniques for indirect network sharing
WO2024239681A1 (fr) Procédé et appareil de prise en charge de transmissions de données de liaison descendante
WO2025060464A1 (fr) Procédé et appareil de prise en charge d&#39;applications d&#39;intelligence artificielle (ia) dans des communications sans fil
WO2025030886A1 (fr) Élimination d&#39;ambiguïté dans un scénario de relais de liaison latérale à sauts multiples
WO2025150033A1 (fr) Techniques de numérotation de séquence avec duplication de paquets et réarrangement pour paquets d&#39;udp
WO2025118648A9 (fr) Sélection de fonction de plan utilisateur
US20250358586A1 (en) Method and apparatus for inter-edge data network based service continuity
US20250358703A1 (en) Method and apparatus for inter-network service continuity
WO2024175225A1 (fr) Procédé de sécurité de couche de strate d&#39;accès sélective pour quic
WO2024244485A1 (fr) Mappage de flux qos pour flux multimédias multiplexés
WO2024109199A1 (fr) Détermination de fonction de réseau
WO2024234699A1 (fr) Différenciation de qos pour dispositifs partagés
WO2025233006A1 (fr) Signalisation dans le plan de contrôle via un plan utilisateur dans un système de communication sans fil
WO2024146704A1 (fr) Connexion de données multi-accès dans un réseau de communication sans fil

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23801431

Country of ref document: EP

Kind code of ref document: A1