Use multiple bootstrapping connections to access service bootstrapping over different access networks

Abstract

Apparatus, methods, and systems for steering traffic of a multi-access data connection over multiple steering connections are disclosed. An apparatus 600 includes a transceiver 625 and a processor 605 that transmits 805 a first message to establish a multi-access data connection over a first access network and a second access network, where the first message indicates that the apparatus supports a first type of steering functionality for creating multiple steering connections over each access network. The processor 605 receives 810 a second message that includes rules indicating how to route a first data packet across the first and second access networks and how to route the first data packet across the multiple steering connections. The processor 605 establishes 815 multiple steering connections over each access network in response to the second message and applies 820 the rules to steer traffic of the multi-access data connection.

Description

Technical Field

[0001] The subject matter disclosed herein generally relates to wireless communications, and more particularly to using the QUIC protocol for low-layer access network service bootstrapping. Background Art

[0002] The following abbreviations and acronyms are defined herein, and at least some of them are referenced in the following description.

[0003] Third Generation Partnership Project (“3GPP”), Fifth Generation Core (“5GC”), Access and Mobility Management Function (“AMF”, a network function in 5GC), Access Point Name (“APN”), Access Stratum (“AS”), Access Network Information (“ANT”), Application Programming Interface (“API”), Data Network Name (“DNN”), Downlink (“DL”), Enhanced Mobile Broadband (“eMBB”), Evolved Node B (“eNB”), Evolved Packet Core (“EPC”), Evolved UMTS Terrestrial Radio Access Network (“E-UTRAN”), Home Subscriber Server (“HSS”), IP Multimedia Subsystem (“IMS”, also known as “IP Multimedia Core Network Subsystem”), Internet Protocol (“IP”), Long Term Evolution (“LTE”), Advanced LTE (“LTE-A”), Media Access Control (“MAC”), Mobile Network Operator (“MNO”), Mobility Management Entity (“MME”), Non-Access Stratum (“NAS”), Narrowband (“NB”), Network Function (“NF”), Network Access Identifier (“NAI”), Next Generation (e.g., 5G) Node B (“gNB”), Next Generation Radio Access Network (“NG-RAN”), New Radio (“NR”), Policy Control Function (“PCF”, a network function in 5GC), Packet Data Network (“PDN”), Packet Data Unit (“PDU”), PDN Gateway (“PGW”), Public Land Mobile Network (“PLMN”), Quality of Service (“QoS”), Radio Access Network (“RAN”), Radio Access Technology (“RAT”), Radio Resource Control (“RRC”), Receive (“Rx”), Single Network Slice Selection Assistance Information (“S-NSSAI”), Serving Gateway (“SGW”), Session Management Function (“SMF”, a network function in 5GC), Transmission Control Protocol (“TCP”), Transmit (“Tx”), Unified Data Management (“UDM”, a network function in 5GC), User Entity / Device (mobile terminal) (“UE”), Uplink (“UL”), User Plane (“UP”), User Plane Function (“UPF”, a network function in 5GC), Universal Mobile Telecommunications System (“UMTS”), User Datagram Protocol (“UDP”), User Location Information (“ULI”), Wireless Local Area Network (“WLAN”), and Worldwide Interoperability for Microwave Access (“WiMAX”).

[0004] Some wireless systems support a feature called Access Traffic Steering, Switching, and Splitting (“ATSSS”), which enables the establishment of a multi-access PDU (“MA PDU”) session between a UE and a UPF, as well as the policy-controlled routing of MA PDU session traffic across two access networks. In essence, an MA PDU session is a data connection between a UE and a UPF that can transfer data traffic using both 3GPP access networks (e.g., NR access or E-UTRA access) and non-3GPP access networks (e.g., Wi-Fi or wired access). SUMMARY OF THE INVENTION

[0005] Methods for steering traffic of a multi-access data connection across multiple steering connections are disclosed. Apparatus and systems also perform the functions of these methods.

[0006] One method for a UE to steer traffic of a multi-access data connection across multiple steering connections includes sending a first message to establish a multi-access data connection with a mobile communication network via a first access network and a second access network, where the first message indicates that the device supports a first type of steering functionality for creating multiple steering connections on each of the first access network and the second access network. The method includes receiving a second message that includes a first rule set and a second rule set, where the first rule set indicates how to route a first data packet of the UE's multi-access data connection across the first access network and the second access network using the first type of steering functionality, and the second rule set indicates how to route the first data packet across multiple steering connections. The method includes establishing multiple steering connections on each of the first access network and the second access network in response to receiving the second message and applying the first rule set and the second rule set to steer the traffic of the multi-access data connection.

[0007] One method for a UPF to steer traffic of a multi-access data connection across multiple steering connections includes communicating with a UE via a first access network and via a second access network, where the remote unit supports a first type of steering functionality for creating multiple steering connections on each of the first access network and the second access network and receiving at the UPF a first message that includes a first rule set and a second rule set, where the first rule set indicates how to route a first data packet of the UE's multi-access data connection across the first access network and the second access network using the first type of steering functionality, and the second rule set indicates how to route the first data packet of the multi-access data connection across multiple steering connections. The method includes receiving multiple steering connection requests from the UE, where each request is received via one of the first access network and the second access network, and in response to accepting the multiple steering connections, applying the first rule set and the second rule set to steer the traffic of the multi-access data connection.

[0008] A method for a SMF to orchestrate the service of a multi-access data connection over multiple bootstrap connections includes receiving, via an AMF, a first message to establish a multi-access data connection between a UE and a UPF in a mobile communication network via a first access network and a second access network. Here, the first message indicates that the UE supports a first type of bootstrap functionality for creating multiple bootstrap connections on each of the first access network and the second access network. In one embodiment, the first message includes a PDU session establishment request and the first type of bootstrap functionality is the QUIC-LL functionality described herein. The method includes sending a second message to a PCF. Here, the second message indicates that the remote unit supports the first type of bootstrap functionality. In one embodiment, the second message includes a SM policy control creation request. A processor receives a first rule set containing multi-access data connection control information, the multi-access data connection control information including the first type of bootstrap functionality and a bootstrap mode. The method includes determining a second rule set from the first rule set and determining a third rule set from the first rule set. The second rule set indicates how to route uplink data packets across the first access network and the second access network and how to route uplink data packets across multiple bootstrap connections and the third rule set indicates how to route downlink data packets across the first access network and the second access network and how to route downlink packets across multiple bootstrap connections. The method includes selecting a UPF that supports the first type of bootstrap functionality, sending the second rule set to the remote unit via the AMF, and sending the third rule set to the selected UPF. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] A more particular description of the embodiments briefly described above will be presented by reference to specific embodiments illustrated in the accompanying drawings. It should be understood that these drawings depict only some embodiments and should not be considered as limiting the scope. The embodiments will be described and explained with additional specificity and detail by using the drawings, in which:

[0010] Figure 1 is a diagram illustrating an embodiment of a wireless communication system for orchestrating the service of a multi-access data connection over multiple bootstrap connections;

[0011] Figure 2 is a diagram illustrating an embodiment of a network deployment for orchestrating the service of a multi-access data connection over multiple bootstrap connections;

[0012] Figure 3A is a signal flow diagram illustrating an embodiment of a process for establishing a QUIC connection for access service orchestration;

[0013] Figure 3B is Figure 3A a continuation of the process described in

[0014] Figure 4is a block diagram illustrating the derivation of the ATSSS rule and the QUIC connection rule;

[0015] Figure 5 is a block diagram illustrating the derivation of the ATSSS rule using QUIC connection selection information;

[0016] Figure 6 is a block diagram illustrating an embodiment of a user equipment device for a service that guides a multi-access data connection over multiple pilot connections;

[0017] Figure 7 is a block diagram illustrating an embodiment of a network device device for a service that guides a multi-access data connection over multiple pilot connections;

[0018] Figure 8 is a flowchart illustrating an embodiment of a first method for a service that guides a multi-access data connection over multiple pilot connections;

[0019] Figure 9 is a flowchart illustrating an embodiment of a second method for a service that guides a multi-access data connection over multiple pilot connections; and

[0020] Figure 10 is a flowchart illustrating an embodiment of a third method for a service that guides a multi-access data connection over multiple pilot connections. Detailed implementation

[0021] As those skilled in the art will understand, aspects of the embodiments can be embodied as a system, apparatus, method, or program product. Thus, the embodiments can take the form of a complete hardware embodiment, a complete software embodiment (including firmware, resident software, microcode, etc.), or an embodiment combining software and hardware aspects.

[0022] For example, the disclosed embodiments can be implemented as a hardware circuit including custom very large scale integration ("VLSI") circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. The disclosed embodiments can also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices, etc. As another example, the disclosed embodiments can include one or more physical or logical blocks of executable code, which can be organized, for example, as objects, procedures, or functions.

[0023] In addition, an embodiment may take the form of a program product embodied in one or more computer-readable storage devices storing machine-readable code, computer-readable code, and / or program code hereinafter referred to as code. The storage device may be tangible, non-transitory, and / or non-transmission. The storage device may not embody a signal. In one embodiment, the storage device only takes the form of a signal for accessing the code.

[0024] Any combination of one or more computer-readable media may be utilized. The computer-readable media may be a computer-readable storage medium. The computer-readable storage medium may be a storage device storing the code. The storage device may be, by way of example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micro-mechanical, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.

[0025] More specific examples (a non-exhaustive list) of the storage device will include the following: an electrical connection having one or more wires, a portable computer disk, a hard disk, a random access memory (“RAM”), a read-only memory (“ROM”), an erasable programmable read-only memory (“EPROM” or flash memory), a portable compact disk read-only memory (“CD-ROM”), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer-readable storage medium may be any tangible medium that can contain or store a program for use by or in connection with an instruction execution system, apparatus, or device.

[0026] References in this specification to “one embodiment,” “an embodiment,” or similar language mean that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. Thus, unless otherwise expressly specified, appearances of the phrases “in one embodiment,” “in an embodiment,” and similar language throughout this specification may, but do not necessarily, all refer to the same embodiment, but rather mean “one or more but not all embodiments.” Unless otherwise expressly specified, the terms “comprising,” “including,” “having,” and variations thereof mean “including but not limited to.” Unless otherwise expressly specified, a list of recited items does not imply that any or all of the items are mutually exclusive. Unless otherwise expressly specified, the terms “a,” “an,” and “the” also refer to “one or more.”

[0027] As used herein, a list joined by “and / or” includes any single item in the list or a combination of items in the list. For example, the list of A, B, and / or C includes only A, only B, only C, the combination of A and B, the combination of B and C, the combination of A and C, or the combination of A, B, and C. As used herein, a list using the term “one or more of” includes any single item in the list or a combination of items in the list. For example, one or more of A, B, and C includes only A, only B, only C, the combination of A and B, the combination of B and C, the combination of A and C, or the combination of A, B, and C. As used herein, a list using the term “one of” includes one and only one of any single item in the list. For example, “one of A, B, and C” includes only A, only B, or only C and excludes the combination of A, B, and C. As used herein, “a member selected from the group consisting of A, B, and C” includes one and only one of A, B, or C and excludes the combination of A, B, and C. As used herein, “a member selected from the group consisting of A, B, and C and their combinations” includes only A, only B, only C, the combination of A and B, the combination of B and C, the combination of A and C, or the combination of A, B, and C.

[0028] In addition, the features, structures, or characteristics of the described embodiments may be combined in any suitable manner. In the following description, numerous specific details are provided, such as examples of programming, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., to provide a thorough understanding of the embodiments. However, those skilled in the relevant art will recognize that the embodiments may be practiced without one or more of the specific details, or with other methods, components, materials, etc. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of the embodiments.

[0029] Aspects of the embodiments are described below with reference to the schematic flowcharts and / or schematic block diagrams of methods, apparatuses, systems, and program products according to the embodiments. It will be understood that each block of the schematic flowcharts and / or schematic block diagrams, and combinations of blocks in the schematic flowcharts and / or schematic block diagrams, can be implemented by code. This code can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device to produce a machine such that the instructions executed by the processor of the computer or other programmable data processing device create a device for implementing the functions / actions specified in the schematic flowcharts and / or schematic block diagrams.

[0030] The code can also be stored in a storage device that can direct a computer, other programmable data processing apparatus, or other devices to operate in a particular manner, such that the instructions stored in the storage device produce an article of manufacture including the instructions that implement the functions / actions specified in the schematic flowchart and / or schematic block diagram.

[0031] The code can also be loaded onto a computer, other programmable data processing apparatus, or other devices, such that a series of operational steps are performed on the computer, other programmable apparatus, or other devices to produce a computer-implemented process, such that the code executed on the computer or other programmable apparatus provides a process for implementing the functions / actions specified in the schematic flowchart and / or schematic block diagram.

[0032] The schematic flowcharts and / or schematic block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatus, systems, methods, and program products according to various embodiments. In this regard, each block in the schematic flowchart and / or schematic block diagram can represent a module, segment, or portion of code that includes one or more executable instructions for implementing the specified logical function(s).

[0033] It should also be noted that in some alternative implementations, the functions noted in the blocks may occur out of the order noted in the figures. For example, two blocks shown in succession may in fact be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. Other steps and methods may be envisioned that are equivalent in function, logic, or effect to one or more blocks or portions thereof shown in the figures.

[0034] The description of the elements in each figure may refer to the elements of the previous figures. In all the figures, like reference numerals refer to like elements, including alternative embodiments of the same elements.

[0035] Methods, apparatus, and systems are disclosed for guiding traffic of a multi-access data connection via a plurality of guiding connections. The 3GPP specifications in Release 16 define features called Access Traffic Steering, Switching and Splitting (ATSSS) that enable the establishment of a multi-access PDU ("MA PDU") session between a UE and a UPF, and the policy control routing of MA PDU session traffic via two access networks. In essence, an MA PDU session is a data connection between a UE and a UPF that can transfer data traffic by using both 3GPP access networks (e.g., NR access or E-UTRA access) and non-3GPP access networks (e.g., Wi-Fi or wired line access). How to route data traffic across two access networks is defined by the steering functionality and the steering mode.

[0036] Currently, two bootstrapping functionalities are defined in TS 23.501: (a) Multipath TCP (MPTCP) bootstrapping functionality and (b) ATSSS-Lower Layer (ATSSS-LL) bootstrapping functionality. However, both MPTCP and ATSSS-LL suffer from several limitations. For example, the MPTCP bootstrapping functionality can only be applied to bootstrap services for TCP traffic, but cannot be applied to bootstrap services for non-TCP traffic. Additionally, the ATSSS-LL bootstrapping functionality is very simple but cannot measure the transmission latency of two accesses, so unless an additional protocol is defined for latency measurement, it cannot direct traffic to the access with the minimum latency. Although such a measurement protocol has been defined in 3GPP and is called the Performance Measurement Functionality (PMF), the additional protocol introduces many complexities and transmission overheads.

[0037] To overcome these limitations and improve performance, the present disclosure specifies a new ATSSS lower layer bootstrapping functionality based on the QUIC protocol specified in draft-ietf-quic-transport-25 with amendments to support sending and receiving unreliable datagrams specified in draft-pauly-quic-datagram-05. This new bootstrapping functionality is called QUIC-Lower Layer (QUIC-LL). The QUIC protocol is used between the UE and the UPF and it creates multiple QUIC connections over each access network, each QUIC connection for carrying data traffic of a QoS flow.

[0038] Figure 1 A wireless communication system 100 for measuring RTT according to an embodiment of the present disclosure is depicted. In one embodiment, the wireless communication system 100 includes at least one remote unit 105, a 5G-RAN 115, and a mobile core network 140. The 5G-RAN 115 and the mobile core network 140 form a mobile communication network. The 5G-RAN 115 may be composed of a 3GPP access network 120 including at least one cellular base station unit 121 and / or a non-3GPP access network 130 including at least one access point 131. The remote unit communicates with the 3GPP access network 120 using a 3GPP communication link 123 and communicates with the non-3GPP access network 130 using a non-3GPP communication link 133. Even though a specific number of remote units 105, 3GPP access networks 120, cellular base station units 121, 3GPP communication links 123, non-3GPP access networks 130, access points 131, non-3GPP communication links 133, and mobile core networks 140 are shown in Figure 1Depicted in, those skilled in the art will recognize that any number of remote units 105, 3GPP access networks 120, cellular base station units 121, 3GPP communication links 123, non-3GPP access networks 130, access points 131, non-3GPP communication links 133, and mobile core networks 140 may be included in the wireless communication system 100.

[0039] In one implementation, the wireless communication system 100 conforms to the 5G system specified in the 3GPP specifications. However, more generally, the wireless communication system 100 may implement some other open or proprietary communication networks, such as LTE or WiMAX, as well as other networks. The present disclosure is not intended to be limited to the implementation of any particular wireless communication system architecture or protocol.

[0040] In one embodiment, the remote unit 105 may include a computing device, such as a desktop computer, laptop computer, personal digital assistant ("PDA"), tablet computer, smart phone, smart TV (e.g., a TV connected to the Internet), smart appliance (e.g., an appliance connected to the Internet), set-top box, game console, security system (including security cameras), in-vehicle computer, network device (e.g., router, switch, modem), etc. In some embodiments, the remote unit 105 includes a wearable device, such as a smart watch, fitness band, optical head-mounted display, etc. Additionally, the remote unit 105 may be referred to as a UE, subscriber unit, mobile device, mobile station, user, terminal, mobile terminal, fixed terminal, subscriber station, user terminal, wireless transmit / receive unit ("WTRU"), device, or by other terms used in the art.

[0041] The remote unit 105 may communicate directly with one or more cellular base station units 121 in the 3GPP access network 120 via uplink ("UL") and downlink ("DL") communication signals. Additionally, the UL and DL communication signals may be carried over the 3GPP communication link 123. Similarly, the remote unit 105 may communicate with one or more access points 131 in the non-3GPP access network 130 via UL and DL communication signals carried over the non-3GPP communication link 133. Here, the access networks 120 and 130 are intermediate networks that provide the remote unit 105 with access to the mobile core network 140.

[0042] In some embodiments, the remote unit 105 communicates with the remote host 155 via a network connection to the mobile core network 140. For example, an application in the remote unit 105 (e.g., a web browser, a media client, a phone / VoIP application) may trigger the remote unit 105 to establish a PDU session (or other data connection) using the 5G-RAN 115 (e.g., the 3GPP access network 120 and / or the non-3GPP access network 130). The mobile core network 140 then relays traffic between the remote unit 105 and the data network 150 (e.g., the remote host 155) using the PDU session. Note that the remote unit 105 may establish one or more PDU sessions (or other data connections) with the mobile core network 140. In this way, the remote unit 105 may have at least one PDU session for communicating with the data network 150. The remote unit 105 may establish additional PDU sessions for communicating with other data networks and / or other remote hosts.

[0043] In addition, the remote unit 105 may establish a multi-access PDU session (i.e., a multi-access data connection) with the mobile core network 140, whereby traffic of the multi-access PDU session is steered over one or both of the 3GPP access network 120 and / or the non-3GPP access network 130 according to steering rules. Additionally, a QUIC tunnel 127 including a plurality of QUIC steering connections may be established over the 3GPP access network 120 for handling traffic of the multi-access PDU session. Similarly, a QUIC tunnel 137 including a plurality of QUIC steering connections may be established over the non-3GPP access network 130 for handling traffic of the multi-access PDU session. Accordingly, the remote unit 105 may be configured with a steering policy 110 having QUIC rules for steering traffic to a particular one of the QUIC tunnels 127, 137.

[0044] The cellular base station units 121 may be distributed over a geographical area. In certain embodiments, the cellular base station units 121 may also be referred to as access terminals, bases, base stations, Node Bs, eNBs, gNBs, home Node Bs, relay nodes, devices, or by any other term used in the art. The cellular base station units 121 are generally part of a radio access network (“RAN”) such as the 3GPP access network 120, which may include one or more controllers communicatively coupled to one or more corresponding cellular base station units 121. These and other elements of the radio access network are not shown but are generally known to those of ordinary skill in the art. The cellular base station units 121 are connected to the mobile core network 140 via the 3GPP access network 120.

[0045] The cellular base station unit 121 can serve multiple remote units 105 within a service area such as a cell or a cell sector via a 3GPP communication link 123. The cellular base station unit 121 can communicate directly with one or more remote units 105 via communication signals. Generally, the cellular base station unit 121 transmits DL communication signals to serve the remote units 105 in the time domain, frequency domain, and / or spatial domain. Additionally, the DL communication signals can be carried on the 3GPP communication link 123. The 3GPP communication link 123 can be any suitable carrier in the licensed or unlicensed radio spectrum. The 3GPP communication link 123 facilitates communication between one or more remote units 105 and / or one or more cellular base station units 121.

[0046] The non-3GPP access network 130 can be distributed over a geographical area. Each non-3GPP access network 130 can serve multiple remote units 105 having a service area. An access point 131 in the non-3GPP access network 130 can communicate directly with one or more remote units 105 by receiving UL communication signals and transmitting DL communication signals to serve the remote units 105 in the time domain, frequency domain, and / or spatial domain. Both the DL and UL communication signals are carried over the non-3GPP communication link 133. The 3GPP communication link 123 and the non-3GPP communication link 133 can employ different frequencies and / or different communication protocols. In various embodiments, the access point 131 can communicate using the unlicensed radio spectrum. The mobile core network 140 can provide services to the remote units 105 via the non-3GPP access network 130, as described in more detail herein.

[0047] In some embodiments, the non-3GPP access network 130 is connected to the mobile core network 140 via an interworking function 135. The interworking function 135 provides interworking between the remote unit 105 and the mobile core network 140. In some embodiments, the interworking function 135 is a non-3GPP interworking function (“N3IWF”), and in other embodiments, it is a trusted non-3GPP gateway function (“TNGF”). The N3IWF supports connecting an “untrusted” non-3GPP access network to the mobile core network (e.g., 5GC), while the TNGF supports connecting a “trusted” non-3GPP access network to the mobile core network. The interworking function 135 supports connecting to the mobile core network 140 via “N2” and “N3” interfaces, and it relays “N1” signaling between the remote unit 105 and the AMF 143. Both the 3GPP access network 120 and the interworking function 135 use the “N2” interface to communicate with the AMF 143. The interworking function 135 also uses the “N3” interface to communicate with the UPF 141.

[0048] In some embodiments, the non-3GPP access network 130 may be controlled by the operator of the mobile core network 140 and may have direct access to the mobile core network 140. Such a non-3GPP AN deployment is referred to as a "trusted non-3GPP access network." The non-3GPP access network 130 is considered "trusted" when operated by a 3GPP operator or a trusted partner and supports certain security features, such as strong air interface encryption. In contrast, a non-3GPP AN deployment that is not controlled by the operator of the mobile core network 140 (or a trusted partner), does not have direct access to the mobile core network 140, or does not support certain security features, is referred to as an "untrusted" non-3GPP access network.

[0049] In one embodiment, the mobile core network 140 is a 5G Core ("5GC") or an Evolved Packet Core ("EPC"), which may be coupled to a data network (e.g., data network 150, such as the Internet and private data networks, and other data networks). The remote unit 105 may have a subscription or other account with the mobile core network 140. Each mobile core network 140 belongs to a single Public Land Mobile Network ("PLMN"). The present disclosure is not intended to be limited to the implementation of any particular wireless communication system architecture or protocol.

[0050] The mobile core network 140 includes a number of network functions ("NFs"). As depicted, the mobile core network 140 includes at least a UPF 141 that serves both the 3GPP access network 120 and the non-3GPP access network 130. Note that in some embodiments, the mobile core network may include one or more intermediate UPFs, e.g., a first intermediate UPF that serves the non-3GPP access network 130 and a second intermediate UPF that serves the 3GPP access network 120. In such an embodiment, the UPF 141 will be the anchor UPF that receives the UP traffic from the two intermediate UPFs.

[0051] The mobile core network 140 also includes a number of control plane functions, including but not limited to an Access and Mobility Management Function ("AMF") 143, a Session Management Function ("SMF") 145, a Policy Control Function ("PCF") 147, and a Unified Data Management Function ("UDM") 149 that serve both the 3GPP access network 120 and the non-3GPP access network 130. In some embodiments, the mobile core network 140 may also include an Authentication Server Function ("AUSF"), a Network Repository Function ("NRF") (used by various NFs to discover and communicate with each other via APIs), or other NFs defined for the 5GC. In various embodiments, the mobile core network 140 may include a PMF (not shown) to assist the remote unit 105 and / or the UPF 141 in performing performance measurements for the two accesses, including latency measurements. In one embodiment, the PMF may coexist with the UPF 141.

[0052] In various embodiments, the mobile core network 140 supports different types of mobile data connections and different types of network slices, where each mobile data connection utilizes a specific network slice. Here, a "network slice" refers to a portion of the mobile core network 140 that is optimized for a specific service type or communication service. Each slice can be identified using an S-NSSAI. In certain embodiments, the various network slices can include separate instances of network functions, such as SMF 145 and UPF 141. In some embodiments, different network slices can share some common network functions, such as AMF 143. For ease of illustration, different network slices are not shown in Figure 1 but their support is assumed.

[0053] Although Figure 1 a specific number and type of network functions are depicted, those skilled in the art will recognize that any number and type of network functions can be included in the mobile core network 140. Additionally, in the case where the mobile core network 140 is an EPC, the depicted network functions can be replaced with appropriate EPC entities, such as MME, S-GW, P-GW, HSS, etc.

[0054] As depicted, the remote unit 105 (e.g., UE) can connect to the mobile core network (e.g., connect to a 5G mobile communication network) via two types of access: (1) via a 3GPP access network 120 and (2) via a non-3GPP access network 130. The first type of access (e.g., 3GPP access network 120) uses a type of wireless communication defined by 3GPP (e.g., NG-RAN), while the second type of access (e.g., non-3GPP access network 130) uses a non-3GPP defined type of wireless communication (e.g., WLAN). 5G-RAN 115 refers to any type of 5G access network capable of providing access to the mobile core network 140, including 3GPP access networks 120 and non-3GPP access networks 130.

[0055] To improve bootstrapping functionality, the remote unit 105 can implement the ATSSS lower layer bootstrapping functionality based on the QUIC protocol specified in draft-ietf-quic-transport-25 and the extended functionality specified in draft-pauly-quic-datagram-05 that supports unreliable datagram transport over a QUIC connection. This new bootstrapping functionality is referred to herein as "QUIC-Lower Layer" or "QUIC-LL". In contrast to higher layer bootstrapping functionality (such as MPTCP) that operates above the IP layer, the term "lower layer" emphasizes the fact that QUIC-LL operates below the IP layer.

[0056] The remote unit 105 can thus use the QUIC-LL bootstrapping functionality to establish a MA PDU session with the UPF 141 for service bootstrapping across 3GPP access and non-3GPP access (in short, a MA PDU session using QUIC-LL). Additionally, after using QUIC-LL to establish a MA PDU session, a bootstrapping policy 110 with QUIC rules (and corresponding multi-access rules with QUIC rules at the UPF 141) can be used to bootstrap the data traffic exchanged between the remote unit 105 and the UPF 141 across 3GPP access and non-3GPP access.

[0057] Figure 2 Depicts a first network deployment 200 in which data traffic is exchanged between a UE 205 (e.g., an embodiment of the remote unit 105) and a UPF 250 (e.g., an embodiment of the UPF 141) via a MA PDU session using QUIC-LL. In essence, the MA PDU session using QUIC-LL 211 creates two QUIC tunnels between the UE and the UPF: one QUIC tunnel 225 via 3GPP access and another QUIC tunnel 227 via non-3GPP access. Each QUIC tunnel consists of one or more QUIC connections and each QUIC connection is used to carry traffic for a specific QoS flow. The QUIC connections are established via each access right after the establishment of the MA PDU session 211, assuming the UE 205 is registered via both accesses.

[0058] After using QUIC-LL 211 to establish a MA PDU session, three types of rules are supplied to the UE 205: ATSSS rules, QUIC rules, and QoS rules. The QUIC rules can be separate from the ATSSS rules (as described below with reference to Figure 4 ), or they can be combined with the ATSSS rules (as described below with reference to Figure 5 ). For the purposes of the following discussion, the QUIC rules are considered separate from the ATSSS rules.

[0059] When an IP packet 209 (or generally, a packet data unit (“PDU”)) is generated in the UE 205 and forwarded to the MA PDU session using QUIC-LL 211 (as Figure 2 shown), the packet 209 first undergoes an access selection 213 performed based on the ATSSS rules. During this access selection 213, it is determined whether the IP packet 209 should be sent to the UPF 250 via 3GPP access 221 or via non-3GPP access 223.

[0060] Next, the IP packet 209 goes through the QUIC connection selection 215, where it is mapped to a QUIC connection on the selected access. In the depicted embodiment, the UE 205 selects the non-3GPP access 223, for example, based on the ATSSS rules. Note that there are the same number of QUIC connections in each access and these QUIC connections are established right after the MA PDU session is set up. Each QUIC connection is used to carry traffic for a specific QoS flow. Thus, when N QoS flows are assigned to the MA PDU session, the UE will request N QUIC connections via the 3GPP access and N QUIC connections via the non-3GPP access. The QUIC connection selection is based on the QUIC rules. In the depicted embodiment, the QUIC tunnel 225 via the 3GPP access includes a first QUIC connection 229 that carries the first QoS flow (QoS flow 1) and a second QUIC connection 231 that carries the second QoS flow (QoS flow 2). Similarly, the QUIC tunnel 227 via the non-3GPP access includes a first QUIC connection 233 that carries the first QoS flow (QoS flow 1) and a second QUIC connection 235 that carries the second QoS flow (QoS flow 2).

[0061] After the QUIC connection is selected, the IP packet 209 is forwarded to this QUIC connection and goes through the normal processing of the QUIC protocol (e.g., at the QUIC protocol layer 215). In the depicted embodiment, the UE 205 selects the first QoS flow 233 of the QUIC tunnel 227 via the non-3GPP access. During this processing of the QUIC protocol, the IP packet 209 is encapsulated in a QUIC datagram frame (specified in draft-pauly-quic-datagram-05) that is further included in the QUIC packet 237. Note that each QUIC packet can carry one or more QUIC datagram frames and / or other QUIC frame types as specified in draft-ietf-quic-transport-25. Each QUIC packet is encapsulated in another IP packet with a specific IP address and UDP port that is forwarded to the UPF 250 (e.g., at the UDP / IP layer 219). Note that each QUIC connection can be identified by an IP address and a UDP port.

[0062] Finally, the created QUIC packet 237 is sent to the selected access interface (3GPP or non-3GPP), where it is mapped to the QoS flow based on the received QoS rules.

[0063] Note that the UPF 250 includes a GPRS tunneling protocol (GTP) tunnel 239 that receives IP packets containing QUIC packets 237 therein. The QUIC packet 237 is unpacked from the IP packet at the UDP / IP layer 241 and the IP packet 209 is unpacked from the QUIC packet 237 at the QUIC protocol layer 243, after which it is delivered to the IP layer 247 and its data is delivered to the upper layer 249.

[0064] Figures 3A - 3B Depicts a process 300 for guiding the service of a multi-access data connection through multiple bootstrap connections according to an embodiment of the present disclosure. The process 300 involves the UE 205, a 5G access network (“5G-AN”) 301, an AMF 303 (e.g., an embodiment of the AMF 143), an SMF 305 (e.g., an embodiment of the SMF 145), a UDM 307 (e.g., an embodiment of the UDM 149), a PCF 309 (e.g., an embodiment of the PCF 147), and the UPF 250.

[0065] Reference Figure 3A , the process 300 starts at step 1a when, in order to request the establishment of a MA PDU session, the UE 205 sends a UL NAS transport message with a request type = MA PDU request and an embedded PDU session establishment request message that includes the ATSSS capabilities of the UE 205 in the 5GSM capabilities information element (see message transfer 311).

[0066] As an example, the ATSSS capabilities of the UE 205 may indicate that the UE 205 supports the ATSSS-LL bootstrap functionality and / or the new QUIC-LL bootstrap functionality defined in TS 23.501. In other examples, the UE 205 may also indicate that it supports the MPTCP bootstrap functionality defined in TS23.501. At step 1b, the UL NAS transport message is forwarded by the 5G access network to the AMF within the NGAP uplink NAS transport message (see message transfer 313).

[0067] At step 2, based on the request type = MA PDU request, the AMF 303 determines that this is a request for a MA PDU session and selects an SMF 305 that supports the MA PDU session. Subsequently, the AMF 303 sends a create SM context request message to the selected SMF 305, which contains the received PDU session establishment request including the 5GSM capabilities information element (see message transfer 315).

[0068] At step 3, the SMF 305 performs a regular interaction with the UDM 307, e.g., to receive session management (SM) subscription data for the UE (see messaging 317) and to register itself as the serving SMF 305 for the requested PDU session (see messaging 319).

[0069] At step 4, the SMF 305 creates the SM context requested in step 2 and returns a response to the AMF 303 (see messaging 321).

[0070] At step 5, the SMF 305 selects the PCF 309 and initiates the establishment of an SM policy association by sending an SM policy control creation request to the selected PCF 309 (see messaging 323). This request triggers the PCF 309 to create an SM policy for the PDU session, i.e., rules (referred to as PCC rules) that define how the various data flows of the PDU session will be charged, what QoS they will experience, how they will be routed across 3GPP access and non-3GPP access, etc. In the depicted embodiment, the SM policy control creation request includes the MA PDU indication, and the ATSSS capabilities of the UE received by the SMF 305 in step 2 (e.g., support for ATSSS-LL and / or support for QUIC-LL).

[0071] The PCF 309 determines whether the requested MA PDU session is allowed, and if allowed, it determines how the various data flows transferred on the PDU session will be routed across 3GPP access and non-3GPP access. In one example, the PCF 309 determines to route the data flows across 3GPP access and non-3GPP access by applying the QUIC-LL steering functionality supported by the UE 205. In this case, the PCF 309 may provide the SMF 305 with a PCC rule (in step 5b) that includes MA PDU session control information, such as the following rule in Table 1:

[0072] Table 1

[0073]

[0074] At step 6, based on the PCC rule received by the PCF 309, the SMF 305 derives rules for the UE 205 (see block 329). Here, the rules for the UE 205 include: (a) ATSSS rules, (b) QUIC rules, and (c) QoS rules, as discussed below with reference to Figure 4 discussed; or (a) ATSSS rules QUIC connection selection information and (b) QoS rules, as discussed below with reference to Figure 5As discussed. Additionally, the SMF 305 uses PCC rules to derive rules for the UPF 250, which are referred to as N4 rules that include QUIC connection selection information (see box 331).

[0075] The rules for the UE 205 are used by the UE 205 to determine (a) how to route uplink data packets across 3GPP access and non-3GPP access (ATSSS rules), (b) how to select the QUIC connection that should be used to transfer the uplink data packets (QUIC rules), and (c) the QoS flow that should be used to transfer the uplink data packets (QoS rules). The N4 rules include multi-access rules (MARs) used by the UPF 250 to determine the same information but for downlink packets. The N4 rules are enhanced (on top of the current N4 rules) to also include a QUIC connection selection rule (referred to as the QUIC rule) for selecting the QUIC connection that should be used to transfer downlink data packets.

[0076] Continue Figure 3B At step 7, the SMF 305 selects the UPF 250 and creates an N4 session with this UPF 250. In the N4 session establishment request message, the SMF 305 includes the derived N4 rules that include QUIC rules, which are used to select a QUIC connection for each downlink data packet (see message transfer 333). As pointed out above, the pair [IP address, UDP port] that identifies the QUIC connection refers to the IP address and UDP port on the UPF side. This pair for each QUIC connection is assigned by the SMF 305, or assigned by the UPF 250 itself and provided to the SMF 305 in step 7b (see message transfer 335). In the latter case, the SMF 305 derives the QUIC rules after step 7 is completed.

[0077] At step 8a, the SMF 305 creates a PDU session establishment acceptance message for the UE 205 and encapsulates this message into an N1N2 message transfer request that is sent to the AMF 303 (see message transfer 337). The PDU session establishment acceptance includes the QoS rules derived by the SMF 305 and an ATSSS container (defined in TS 24.501), and this ATSSS container contains (a) individual ATSSS rules and QUIC rules (as Figure 4 shown), or (b) an ATSSS rule with QUIC connection selection information (as Figure 5 shown). The AMF 303 sends the N1N2 message transfer request (see message transfer 339).

[0078] At step 9a, a normal NGAP PDU session resource setup procedure runs between the AMF 303 and the 5G-AN 301. The PDU session establishment acceptance message is embedded in the NGAP PDU session resource setup request message (see Message Transfer 341).

[0079] At step 9b, a DL NAS transport message containing the PDU session establishment acceptance message is sent to the UE 205 (see Message Transfer 343). Since the UE 205 receives an ATSSS container including ATSSS rules (with or without separate QUIC rules), the UE 205 determines that its MA PDU session establishment request has been accepted by the network. The 5G-AN 301 completes the NGAP PDU session resource setup procedure by sending an NGAP PDU session resource setup response message to the AMF 303 (see Message Transfer 345).

[0080] At step 10a, the AMF 303 forwards the N2 SM information received from the 5G-AN 301 (e.g., PDU session ID, AN tunnel information, list of accepted / rejected QFIs, etc.) to the SMF 305 (see Message Transfer 347). At step 10b, the SMF 305 initiates an N4 session modification procedure to the UPF 250 (see Message Transfer 349). The SMF 305 provides the AN tunnel information and the corresponding forwarding rules to the UPF 250. At step 10c, the UPF 250 provides an N4 session modification response to the SMF 305 (see Message Transfer 351). After this step, the UPF 250 delivers any downlink packets that may have been buffered for this PDU session to the UE 205. At step 10d, the SMF 305 sends an UpdateSMContext Response to the AMF 303 (see the message in 353). Here, the SMF 305 may subscribe to UE mobility event notifications from the AMF 303.

[0081] At step 11a, the UE 205 initiates the establishment of N QUIC connections with the UPF 250 via 3GPP access (see box 355). At step 11b, the UE 205 initiates the establishment of N QUIC connections with the UPF 250 via non-3GPP access (see box 357). Refer to Figure 2 , Figure 2Depict a QUIC tunnel over 3GPP access and another QUIC tunnel over non-3GPP access, where each QUIC tunnel consists of one or more QUIC connections and each QUIC connection is used to carry traffic for a specific QoS flow. The number of QUIC connections (N) is determined from the received QUIC rules (e.g., one QUIC connection per QUIC rule) or from the received ATSSS rules with QUIC connection selection information. Each QUIC connection is initiated towards a specific [IP address, UDP port] pair.

[0082] After establishing the MA PDU session using QUIC-LL, UE 205 applies the received rules (in step 9b) to perform the user plane procedures discussed above with reference to Figure 2 In particular, UE 205 applies the rules received in the ATSSS container to determine, for each uplink data packet that must be sent via the established MA PDU session, (a) the access through which the data packet should be sent and (b) the QUIC connection through which the data packet should be sent. Additionally, UE 205 applies the received QoS rules to determine the QoS flow through which the data packet should be sent. Note that UPF 250 applies the rules received in the N4 rules to determine, for each downlink packet that must be sent via the established MA PDU session, (a) the access through which the data packet should be sent and (b) the QUIC connection through which the data packet should be sent.

[0083] Figure 4 Depict a first derivation 400 of a steering policy including QUIC rules by SMF 305. SMF 305 receives a PCC rule 405 from the PCF (e.g., PCF 309), as discussed above with reference to Figure 2 Step 5b. SMF 305 then derives an ATSSS rule 410, a QUIC rule 415, and a QoS rule 420 from the PCC rule 405. As depicted, each PCC rule 405 includes an indication 407 of the type of steering functionality and an indication 409 of the steering mode.

[0084] Each ATSSS rule 410 has a service descriptor component that identifies the data service matching this rule and an access selection descriptor component that identifies how the data service should be routed across 3GPP access and non-3GPP access (e.g., AN selection rule 411). The access selection descriptor indicates the steering functionality and the steering mode that should be used. The steering functionality identifies the function that should be used for data service steering (or routing), such as QUIC-LL defined in this disclosure, while the steering mode identifies how the data service should be steered, e.g., it should be steered to the active access (if available), or to the access with the minimum latency, etc.

[0085] Each QUIC rule 415 has a service descriptor component that identifies the data service matching this rule and a QUIC connection selection descriptor component that identifies the QUIC connection via which the data service should be sent (e.g., QUIC connection selection rule 417). The QUIC connection itself is identified by a pair [IP address, UDP port], i.e., by the IP address and UDP port on the UPF side where the QUIC connection is established. Alternatively, the QUIC connection can be identified by other means such as a QUIC connection identifier.

[0086] Each QoS rule 420 has a packet filtering list component that identifies the data service matching this rule and a QoS flow identifier (QFI) component that identifies the QoS flow (i.e., QoS parameters) that should be used to transfer this data service. Figure 4 Note that each QoS rule matches the data service of a single QUIC connection via a pair [IP address, UDP port], and thus, one QoS flow is used to transfer the traffic of one QUIC connection. In other words, there is a one-to-one mapping between the QoS flow and the QUIC connection.

[0087] Figure 5 Depict a second derivation 500 of a steering policy including QUIC rules by the SMF 305. The SMF 305 receives the PCC rule 405 from the PCF (e.g., PCF 309), as discussed above with reference to Figure 2 step 5b. The SMF 305 then derives the combined ATSSS and QUIC rules and the QoS rule 420 from the PCC rule 405.

[0088] With Figure 4In contrast, in the second derivation 500, the SMF 305 combines the ATSSS rule 410 and the QUIC rule 415 into a common rule set, referred to as the ATSSS rule 505 with QUIC connection selection information. This is possible because both the ATSSS rule 410 and the QUIC rule 415 have the same service descriptor. An example showing how the SMF 305 derives the ATSSS rule 505 with QUIC connection selection information and the QoS rule 420 is shown in Figure 5 . In the depicted embodiment, the ATSSS rule 505 with QUIC connection selection information includes the existing components of the ATSSS rule defined in TS 23.501 (i.e., the service descriptor and the access selection descriptor (e.g., the AN selection rule 411)) plus a new component, the QUIC connection selection descriptor (e.g., the QUIC connection selection rule 417), which identifies the QUIC connection that should be used to carry the data service matching the service descriptor. The QUIC connection itself is identified by a pair [IP address, UDP port], i.e., by the IP address and UDP port on the UPF side where the QUIC connection is established. Alternatively, the QUIC connection can be identified by other means such as a QUIC connection identifier.

[0089] The ATSSS rule 505 with QUIC connection selection information specifies how to route uplink data packets across 3GPP access and non-3GPP access and how to select a QUIC connection for this uplink data packet, whereas the QoS rule specifies the QoS flow (i.e., the QoS parameters) that should be used to transfer the uplink data packet; see QoS flow identifier (“QFI”).

[0090] Figure 6 An embodiment of a user equipment device 600 for services that can be used to bootstrap a multi-access data connection over multiple bootstrap connections according to an embodiment of the present disclosure is depicted. The user equipment device 600 can be an embodiment of the remote unit 105 and / or the UE 205. In addition, the user equipment device 600 can include a processor 605, a memory 610, an input device 615, an output device 620, and a transceiver 625. In some embodiments, the input device 615 and the output device 620 are combined into a single device, such as a touch screen. In certain embodiments, the user equipment device 600 does not include any input device 615 and / or output device 620.

[0091] As depicted, transceiver 625 includes at least one transmitter 630 and at least one receiver 635. Here, transceiver 625 communicates with a mobile core network (e.g., 5GC) via one or more access networks. Additionally, transceiver 625 may support at least one network interface 640. Here, at least one network interface 640 facilitates communication with an eNB or gNB (e.g., using the "Uu" interface). Additionally, at least one network interface 640 may include interfaces for communicating with an AMF, SMF, and / or UPF.

[0092] In some embodiments, transceiver 625 includes a first transceiver that communicates with a mobile communication network via a first access network and a second transceiver that communicates with the mobile communication network via a second access network. In other embodiments, transceiver 625 includes a first functionality (e.g., a modem) for communicating with a mobile communication network via a first access network and a second functionality (e.g., a modem) for communicating with the mobile communication network via a second access network.

[0093] In one embodiment, processor 605 may include any known controller capable of executing computer-readable instructions and / or capable of performing logical operations. For example, processor 605 may be a microcontroller, a microprocessor, a central processing unit ("CPU"), a graphics processing unit ("GPU"), a co-processing unit, a field programmable gate array ("FPGA"), or a similar programmable controller. In some embodiments, processor 605 executes instructions stored in memory 610 to perform the methods and routines described herein. Processor 605 is communicatively coupled to memory 610, input device 615, output device 620, and transceiver 625.

[0094] In various embodiments, processor 605 sends a first message (e.g., a PDU session establishment request) to establish a multi-access data connection with a mobile communication network via a first access network and a second access network, where the first message indicates that the device supports a first type of bootstrapping functionality (e.g., QUIC-LL) for creating multiple bootstrapping connections (e.g., QUIC connections) on each of the first access network and the second access network.

[0095] The processor 605 receives a second message (e.g., PDU session establishment, acceptance message) that includes a first rule set (e.g., ATSSS rules) and a second rule set (e.g., QUIC rules), where the first rule set indicates how to route a first data packet across a first access network and a second access network by using a first type of bootstrapping functionality, and the second rule set indicates how to route the first data packet across multiple bootstrapping connections. Alternatively, the processor 605 may receive a combined rule set formed by the first rule set and the second rule set (e.g., see "ATSSS rule 505 with QUIC connection selection information" described above). Here, the rules in the combined rule set include a bootstrapping mode (e.g., QUIC-LL) and indicate which bootstrapping connection the first data packet will be routed via. The bootstrapping mode indicates which access network the first data packet will be routed via.

[0096] The processor 605 establishes a plurality of bootstrapping connections (e.g., QUIC connections) on each of the first access network and the second access network in response to receiving the second message, and the processor 605 applies the first rule set and the second rule set for the traffic of bootstrapping a multi-access data connection. In some embodiments, the traffic of bootstrapping a multi-access data connection includes selecting an access network using the first rule set and selecting a bootstrapping connection on the selected access network using the second rule set. In the case of receiving a combined rule set, the processor 605 applies the combined rule set to bootstrap the traffic of the multi-access data connection. Here, the processor 605 bootstraps the traffic of the multi-access data connection by selecting an access network and selecting a bootstrapping connection on the selected access network using the combined rule set.

[0097] In certain embodiments, the processor 605 encapsulates the traffic of the multi-access data connection within a QUIC datagram frame in response to selecting a bootstrapping connection. In some embodiments, each bootstrapping connection is associated with a QoS flow.

[0098] In some embodiments, each bootstrapping connection terminates at a common UPF. In certain embodiments, each bootstrapping connection uses a different UDP port at the common UPF. In certain embodiments, each bootstrapping connection uses a different IP address of the common UPF. In some embodiments, the first type of bootstrapping functionality is based on the QUIC protocol, where each of the plurality of bootstrapping connections corresponds to a different QUIC connection between the device and the common UPF.

[0099] In some embodiments, the bootstrapping connections are established according to the information in the second rule set. In various embodiments, the rules in the first rule set include a bootstrapping mode that indicates which access network the first data packet will be routed via, and where the rules in the second rule set indicate which bootstrapping connection the first data packet will be routed via.

[0100] In one embodiment, the memory 610 is a computer-readable storage medium. In some embodiments, the memory 610 includes volatile computer storage media. For example, the memory 610 may include RAM, including dynamic RAM ("DRAM"), synchronous dynamic RAM ("SDRAM"), and / or static RAM ("SRAM"). In some embodiments, the memory 610 includes non-volatile computer storage media. For example, the memory 610 may include a hard disk drive, a flash memory, or any other suitable non-volatile computer storage device. In some embodiments, the memory 610 includes both volatile and non-volatile computer storage media. In some embodiments, the memory 610 stores data related to services for booting a multi-access data connection over multiple boot connections, such as storing ANI, IP addresses, and the like. In certain embodiments, the memory 610 also stores program code and related data, such as an operating system ("OS") or other controller algorithms running on the user device 600, as well as one or more software applications.

[0101] In one embodiment, the input device 615 may include any known computer input device, including a touch panel, buttons, a keyboard, a stylus, a microphone, etc. In some embodiments, the input device 615 may be integrated with the output device 620, for example, as a touch screen or a similar touch-sensitive display. In some embodiments, the input device 615 includes a touch screen such that a virtual keyboard displayed on the touch screen and / or text can be input by handwriting on the touch screen. In some embodiments, the input device 615 includes two or more different devices, such as a keyboard and a touch panel.

[0102] In one embodiment, the output device 620 may include any known electronically controllable display or display device. The output device 620 may be designed to output visual, auditory, and / or tactile signals. In some embodiments, the output device 620 includes an electronic display capable of outputting visual data to a user. For example, the output device 620 may include, but is not limited to, an LCD display, an LED display, an OLED display, a projector, or a similar display device capable of outputting images, text, etc. to a user. As another non-limiting example, the output device 620 may include a wearable display, such as a smart watch, smart glasses, a head-up display, etc. In addition, the output device 620 may be a component of a smart phone, a personal digital assistant, a television, a desktop computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, etc.

[0103] In some embodiments, output device 620 includes one or more speakers for generating sound. For example, output device 620 can generate an audible alert or notification (e.g., beep or ringtone). In some embodiments, output device 620 includes one or more haptic devices for generating vibration, movement, or other tactile feedback. In some embodiments, all or part of output device 620 can be integrated with input device 615. For example, input device 615 and output device 620 can form a touchscreen or similar touch-sensitive display. In other embodiments, all or part of output device 620 can be located near input device 615.

[0104] As described above, transceiver 625 communicates with one or more network functions of a mobile communication network via one or more access networks. Transceiver 625 operates under the control of processor 605 to transmit messages, data, and other signals and also to receive messages, data, and other signals. For example, processor 605 can selectively activate transceiver (or a portion thereof) at a particular time to send and receive messages.

[0105] Transceiver 625 can include one or more transmitters 630 and one or more receivers 635. Although only one transmitter 630 and one receiver 635 are illustrated, user equipment device 600 can have any suitable number of transmitters 630 and receivers 635. Transmitters 630 and receivers 635 can be any suitable type of transmitter and receiver. In one embodiment, transceiver 625 includes a first transmitter / receiver pair for communicating with a mobile communication network over an authorized radio spectrum and a second transmitter / receiver pair for communicating with a mobile communication network over an unlicensed radio spectrum.

[0106] In some embodiments, the first transmitter / receiver pair for communicating with a mobile communication network over an authorized radio spectrum and the second transmitter / receiver pair for communicating with a mobile communication network over an unlicensed radio spectrum can be combined into a single transceiver unit, such as a single chip that performs functions for both the authorized and unlicensed radio spectrums. In some embodiments, the first transmitter / receiver pair and the second transmitter / receiver pair can share one or more hardware components. For example, certain transceivers 625, transmitters 630, and receivers 635 can be implemented as physically separate components that access shared hardware resources and / or software resources, such as network interface 640.

[0107] In various embodiments, one or more transmitters 630 and / or one or more receivers 635 may be implemented and / or integrated into a single hardware component, such as a multi-transceiver chip, a system-on-chip, an ASIC, or other types of hardware components. In certain embodiments, one or more transmitters 630 and / or one or more receivers 635 may be implemented and / or integrated into a multi-chip module. In some embodiments, other components such as network interface 640 or other hardware components / circuits may be integrated with any number of transmitters 630 and / or receivers 635 into a single chip. In such embodiments, the transmitters 630 and receivers 635 may be logically configured as a transceiver 625 using a more common control signal or as modular transmitters 630 and receivers 635 implemented in the same hardware chip or multi-chip module.

[0108] Figure 7 An embodiment of a network device apparatus 700 is depicted that can be used to steer traffic for a multi-access data connection over multiple bearer connections. In some embodiments, the network device apparatus 700 may implement a UPF. In other embodiments, the network device apparatus 700 may implement an SMF. Additionally, the network device apparatus 700 may include a processor 705, a memory 710, an input device 715, an output device 720, and a transceiver 725. In some embodiments, the input device 715 and the output device 720 are combined into a single device, such as a touch screen. In certain embodiments, the network device apparatus 700 does not include any input device 715 and / or output device 720.

[0109] As depicted, the transceiver 725 includes at least one transmitter 730 and at least one receiver 735. Here, the transceiver 725 communicates with one or more remote units 105. Additionally, the transceiver 725 may support at least one network interface 740. In some embodiments, the transceiver 725 supports a first interface for communicating with a RAN node, a second interface for communicating with one or more network functions in a mobile core network (e.g., 5GC), and a third interface for communicating with a remote unit (e.g., UE).

[0110] In one embodiment, the processor 705 may include any known controller capable of executing computer-readable instructions and / or capable of performing logical operations. For example, the processor 705 may be a microcontroller, a microprocessor, a central processing unit ("CPU"), a graphics processing unit ("GPU"), an auxiliary processing unit, a field-programmable gate array ("FPGA"), or a similar programmable controller. In some embodiments, the processor 705 executes instructions stored in the memory 710 to perform the methods and routines described herein. The processor 705 is communicatively coupled to the memory 710, the input device 715, the output device 720, and the first transceiver 725.

[0111] In various embodiments, the network device apparatus 700 operates as a UPF. In such embodiments, the processor 705 communicates with the UE via different access networks, namely via a first access network and a second access network. Here, the UE supports a first type of bootstrapping functionality (e.g., QUIC-LL) for creating multiple bootstrapping connections (e.g., QUIC connections) via each of the first access network and the second access network, and receives a first message (e.g., N4 session establishment request) including a first rule set (e.g., AN selection rule) and a second rule set (e.g., QUIC connection selection rule). Here, the first rule set (e.g., multi-access rule, MAR) indicates how to route the (e.g., downlink) traffic of the multi-access data connection of the remote unit across the first access network and the second access network by using the first type of bootstrapping functionality. Note that the ATSSS rules are only sent to the UE. The relevant rules sent to the UPF are called MAR. The second rule set (e.g., QUIC rule) indicates how to route the (e.g., downlink) traffic of the multi-access data connection across multiple bootstrapping connections (e.g., QUIC connections).

[0112] Alternatively, the processor 705 may receive a combined rule set, i.e., a multi-access rule (MAR) containing QUIC connection selection information (these combined rule sets are similar to the above-mentioned "ATSSS rule 505 with QUIC connection selection information"). Here, the rules in the combined rule set include a bootstrapping mode (e.g., QUIC-LL) and also indicate through which bootstrapping connection the first data packet is to be routed. The bootstrapping mode indicates through which access network the first data packet is to be routed. In such embodiments, bootstrapping the traffic of the multi-access data connection includes selecting an access network and using the combined rule set to select a bootstrapping connection through the selected access network.

[0113] The processor 705 receives multiple boot connection requests (e.g., QUIC connection requests) from the UE, where each request is received via one of the first access network and the second access network. The processor 705 applies a first rule set and a second rule set in response to accepting the multiple boot connections to steer the traffic of the multi-access data connection.

[0114] In some embodiments, steering the traffic of the multi-access data connection includes using the first rule set to select an access network and using the second rule set to select a boot connection through the selected access network. In such embodiments, the processor 705 encapsulates the traffic of the multi-access data connection within a QUIC datagram frame in response to selecting the boot connection. In some embodiments, each boot connection is associated with a QoS flow.

[0115] In some embodiments, the first type of boot functionality is based on the QUIC protocol, where each of the multiple boot connections corresponds to a different QUIC connection between the network device 700 and the UE. In some embodiments, each boot connection uses a different UDP port at the network device 700. In some embodiments, each boot connection uses a different IP address of the network device 700.

[0116] In some embodiments, the processor 705 assigns a UDP port and an IP address to each of the multiple boot connections in response to receiving a first message. Alternatively, the SMF may assign the UDP port and the IP address for each QUIC connection. Here, each UDP port and IP address indicate the destination of each QUIC connection on the UPF side.

[0117] In some embodiments, the boot connection is established according to the information in the second rule set. Here, the QUIC rules sent to the UE include the UDP port / IP address for each QUIC connection, so the UE knows how to establish each QUIC connection.

[0118] In some embodiments, the rules in the first rule set include a boot mode that indicates through which access network the first data packet is to be routed, and where the rules in the second rule set indicate through which boot connection the first data packet is to be routed.

[0119] In various embodiments, network device 700 operates as an SMF. In such embodiments, transceiver 725 supports a first network interface for communicating with an AMF in a mobile communication network and a second network interface for communicating with a PCF in a mobile communication network. Via transceiver 725, processor 705 receives a first message via the AMF to establish a multi-access data connection between a UE and a UPF in a mobile communication network via a first access network and a second access network. Here, the first message indicates that the UE supports a first type of boot functionality for creating multiple boot connections (e.g., QUIC connections) via each of the first access network and the second access network. In one embodiment, the first message includes a PDU session establishment request and the first type of boot functionality is the QUIC-LL functionality described herein.

[0120] Processor 705 sends a second message (i.e., using transceiver 725) to the PCF. Here, the second message indicates that the remote unit supports the first type of boot functionality. In one embodiment, the second message includes an SM policy control creation request. Via transceiver 725, processor 705 receives a first rule set (e.g., a PCC rule) containing multi-access data connection control information, which includes the first type of boot functionality and a boot mode.

[0121] Processor 705 determines a second rule set (e.g., rules for the UE) from the first rule set and determines a third rule set (e.g., rules for the UPF) from the first rule set. The second rule set indicates how to route uplink data packets across the first access network and the second access network and how to route uplink data packets across multiple boot connections, and the third rule set indicates how to route downlink data packets across the first access network and the second access network and how to route downlink packets across multiple boot connections. Processor 705 selects a UPF that supports the first type of boot functionality and controls transceiver 725 to send the second rule set to the remote unit via the AMF and send the third rule set to the selected UPF.

[0122] In some embodiments, each boot connection is associated with a QoS flow. In some embodiments, each boot connection uses a different IP address of the selected UPF. In some embodiments, the rules in the first rule set include a boot mode that indicates which access network to route a first data packet via and which boot connection to route the first data packet via.

[0123] In one embodiment, the memory 710 is a computer-readable storage medium. In some embodiments, the memory 710 includes volatile computer storage media. For example, the memory 710 may include RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and / or static RAM (“SRAM”). In some embodiments, the memory 710 includes non-volatile computer storage media. For example, the memory 710 may include a hard disk drive, flash memory, or any other suitable non-volatile computer storage device. In some embodiments, the memory 710 includes both volatile and non-volatile computer storage media. In some embodiments, the memory 710 stores data related to services for booting multi-access data connections over multiple boot connections, such as storing ANI, IP addresses, UE context, etc. In certain embodiments, the memory 710 also stores program code and related data, such as an operating system (“OS”) or other controller algorithms running on the network device apparatus 700, as well as one or more software applications.

[0124] In one embodiment, the input device 715 may include any known computer input device, including a touch panel, buttons, a keyboard, a stylus, a microphone, etc. In some embodiments, the input device 715 may be integrated with the output device 720, for example, as a touch screen or a similar touch-sensitive display. In some embodiments, the input device 715 includes a touch screen such that text can be input using a virtual keyboard displayed on the touch screen and / or by handwriting on the touch screen. In some embodiments, the input device 715 includes two or more different devices, such as a keyboard and a touch panel.

[0125] In one embodiment, the output device 720 may include any known electronically controllable display or display device. The output device 720 may be designed to output visual, auditory, and / or tactile signals. In some embodiments, the output device 720 includes an electronic display capable of outputting visual data to a user. For example, the output device 720 may include, but is not limited to, an LCD display, an LED display, an OLED display, a projector, or a similar display device capable of outputting images, text, etc. to a user. As another non-limiting example, the output device 720 may include a wearable display, such as a smartwatch, smart glasses, a heads-up display, etc. Additionally, the output device 720 may be a component of a smart phone, a personal digital assistant, a television, a desktop computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, etc.

[0126] In some embodiments, output device 720 includes one or more speakers for generating sound. For example, output device 720 can generate an audible alert or notification (e.g., beep or ringtone). In some embodiments, output device 720 includes one or more haptic devices for generating vibration, movement, or other tactile feedback. In some embodiments, all or part of output device 720 can be integrated with input device 715. For example, input device 715 and output device 720 can form a touchscreen or similar touch-sensitive display. In other embodiments, all or part of output device 720 can be located near input device 715.

[0127] As described above, transceiver 725 can communicate with one or more remote units and / or with one or more interworking functions that provide access to one or more PLMNs. Transceiver 725 can also communicate with one or more network functions (e.g., in mobile core network 140). Transceiver 725 operates under the control of processor 705 to transmit messages, data, and other signals and also to receive messages, data, and other signals. For example, processor 705 can selectively activate transceiver (or a portion thereof) at a particular time to send and receive messages.

[0128] Transceiver 725 can include one or more transmitters 730 and one or more receivers 735. In certain embodiments, one or more transmitters 730 and / or one or more receivers 735 can share transceiver hardware and / or circuitry. For example, one or more transmitters 730 and / or one or more receivers 735 can share an antenna, antenna tuner, amplifier, filter, oscillator, mixer, modulator / demodulator, power supply, etc. In one embodiment, transceiver 725 implements multiple logical transceivers using different communication protocols or protocol stacks while using common physical hardware.

[0129] Figure 8 Method 800 for steering traffic of a multi-access data connection over multiple steering connections is depicted in accordance with embodiments of the present disclosure. In some embodiments, method 800 is performed by a UE, such as remote unit 105, UE 205, and / or user equipment device 600. In certain embodiments, method 800 can be performed by a processor executing program code, e.g., a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, etc.

[0130] Method 800 begins and sends 805 a first message (e.g., PDU session establishment request) to establish a multi-access data connection with a mobile communication network via a first access network and a second access network, where the first message indicates that the device supports a first type of bootstrapping functionality (e.g., QUIC-LL) for creating multiple bootstrapping connections (e.g., QUIC connections) on each of the first access network and the second access network.

[0131] Method 800 includes receiving 810 a second message (e.g., PDU session establishment accept message) including a first rule set (e.g., ATSSS rules) and a second rule set (e.g., QUIC rules), where the first rule set indicates how to route a first data packet in the first access network and the second access network by using the first type of bootstrapping functionality, and the second rule set indicates how to route the first data packet across multiple bootstrapping connections.

[0132] Method 800 includes establishing 815 multiple bootstrapping connections on each of the first access network and the second access network in response to receiving the second message. Method 800 includes applying 820 the first rule set and the second rule set to direct the traffic of the multi-access data connection. Method 800 ends.

[0133] Figure 9 Method 900 for directing the traffic of a multi-access data connection over multiple bootstrapping connections according to an embodiment of the present disclosure is depicted. In some embodiments, method 900 is performed by a user plane network function, such as UPF 141, UPF250, and / or network device 700. In certain embodiments, method 900 may be performed by a processor executing program code, e.g., a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, an FPGA, etc.

[0134] Method 900 begins and communicates 905 with a UE via a first access network and via a second access network, where the remote unit supports a first type of bootstrapping functionality (e.g., QUIC-LL) for creating multiple bootstrapping connections (e.g., QUIC connections) on each of the first access network and the second access network.

[0135] Method 900 includes receiving 910 at the UPF a first message (e.g., N4 session establishment request), the first message including a first rule set (e.g., multi-access rules) and a second rule set (e.g., QUIC rules), where the first rule set indicates how to route the traffic of the UE's multi-access data connection across the first access network and the second access network by using the first type of bootstrapping functionality and the second rule set indicates how to route the traffic of the multi-access data connection across multiple bootstrapping connections.

[0136] Method 900 includes receiving 915 at the UE multiple boot connection requests (e.g., QUIC connection requests), where each request is received via one of a first access network and a second access network. Method 900 includes applying 920 a first rule set and a second rule set in response to accepting the multiple boot connections to steer traffic of a multi-access data connection. Method 900 ends.

[0137] Figure 10 Method 1000 for steering traffic of a multi-access data connection over multiple boot connections according to an embodiment of the present disclosure is depicted. In some embodiments, method 1000 is performed by a session management network function, such as SMF 145, SMF 305, and / or network device 700. In certain embodiments, method 1000 may be performed by a processor executing program code, e.g., a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, an FPGA, etc.

[0138] Method 1000 begins and receives 1005 a first message via the AMF to establish a multi-access data connection between a UE and a UPF in a mobile communication network via a first access network and a second access network. Here, the first message indicates that the UE supports a first type of boot functionality for creating multiple boot connections (e.g., QUIC connections) via each of the first access network and the second access network. In one embodiment, the first message includes a PDU session establishment request and the first type of boot functionality is the QUIC-LL functionality described herein.

[0139] Method 1000 includes sending 1010 a second message to the PCF. Here, the second message indicates that the remote unit supports the first type of boot functionality. In one embodiment, the second message includes an SM policy control creation request.

[0140] Method 1000 includes receiving 1015 a first rule set (e.g., a PCC rule) containing multi-access data connection control information, the multi-access data connection control information including the first type of boot functionality and a boot mode.

[0141] Method 1000 includes determining 1020 a second rule set (e.g., rules for the UE) from the first rule set. Here, the second rule set indicates how to route uplink data packets across the first access network and the second access network and how to route uplink data packets across multiple boot connections.

[0142] Method 1000 includes determining 1025 a third rule set (e.g., rules for the UPF) from the first rule set. Here, the third rule set indicates how to route downlink data packets across the first access network and the second access network and how to route downlink packets across multiple boot connections.

[0143] The third method includes selecting 1030 a UPF that supports the first type of bootstrapping functionality. The third method includes sending 1035 a second rule set to the remote unit via the AMF. The third method includes sending 1040 a third rule set to the selected UPF. Method 1000 ends.

[0144] Disclosed herein is a first apparatus for bootstrapping traffic of a multi-access data connection via a plurality of bootstrapping connections, according to an embodiment of the present disclosure. The first apparatus may be implemented by a UE such as the remote unit 105, the UE 205, and / or the user equipment apparatus 600. The first apparatus includes a first transceiver that communicates with a mobile communication network via a first access network and a second transceiver that communicates with the mobile communication network via a second access network. In some embodiments, the first transceiver and the second transceiver are combined into a single transceiver. The first apparatus includes a processor that sends a first message (e.g., a PDU session establishment request) to establish a multi-access data connection with the mobile communication network via the first access network and the second access network, where the first message indicates that the apparatus supports a first type of bootstrapping functionality (e.g., QUIC-LL) for creating a plurality of bootstrapping connections (e.g., QUIC connections) via each of the first access network and the second access network.

[0145] The processor receives a second message (e.g., a PDU session establishment acceptance message) that includes a first rule set (e.g., an ATSSS rule) and a second rule set (e.g., a QUIC rule), where the first rule set indicates how to route a first data packet across the first access network and the second access network by using the first type of bootstrapping functionality and the second rule set indicates how to route the first data packet across a plurality of bootstrapping connections. Alternatively, the processor may receive a combined rule set formed from the first rule set and the second rule set (e.g., see the above “ATSSS rule 505 with QUIC connection selection information”). Here, the rules in the combined rule set include a bootstrapping mode (e.g., QUIC-LL) and indicate which bootstrapping connection to route the first data packet via. The bootstrapping mode indicates which access network to route the first data packet via.

[0146] The processor establishes a plurality of bootstrapping connections (e.g., QUIC connections) via each of the first access network and the second access network in response to receiving the second message and the processor applies the first rule set and the second rule set to bootstrap the traffic of the multi-access data connection.

[0147] In some embodiments, bootstrapping the traffic of the multi-access data connection includes using the first rule set to select an access network and using the second rule set to select a bootstrapping connection via the selected access network. Alternatively, the processor bootstraps the traffic of the multi-access data connection by selecting an access network and using the combined rule set to select a bootstrapping connection via the selected access network.

[0148] In some embodiments, the processor encapsulates the traffic of the multi-access data connection within a QUIC datagram frame in response to selecting a boot connection. In some embodiments, each boot connection is associated with a QoS flow.

[0149] In some embodiments, each boot connection terminates at a common UPF. In certain embodiments, each boot connection uses a different UDP port at the common UPF. In some embodiments, each boot connection uses a different IP address of the common UPF. In some embodiments, the first type of boot functionality is based on the QUIC protocol, wherein each of the plurality of boot connections corresponds to a different QUIC connection between the device and the common UPF.

[0150] In some embodiments, the boot connection is established according to the information in the second rule set. In various embodiments, the rules in the first rule set include a boot mode that indicates via which access network to route the first data packet, and wherein the rules in the second rule set indicate via which boot connection to route the first data packet.

[0151] Disclosed herein is a first method for guiding the traffic of a multi-access data connection through a plurality of boot connections. The first method may be performed by a UE such as remote unit 105, UE 205, and / or user equipment device 600. The first method includes sending a first message (e.g., PDU session establishment request) to establish a multi-access data connection with a mobile communication network through a first access network and a second access network, wherein the first message indicates that the device supports a first type of boot functionality (e.g., QUIC-LL) for creating a plurality of boot connections (e.g., QUIC connections) through each of the first access network and the second access network.

[0152] The first method includes receiving a second message (e.g., PDU session establishment acceptance message) including a first rule set (e.g., ATSSS rules) and a second rule set (e.g., QUIC rules), wherein the first rule set indicates how to route the first data packet across the first access network and the second access network by using the first type of boot functionality and the second rule set indicates how to route the first data packet across the plurality of boot connections. Alternatively, the second message may include a combined rule set formed from the first rule set and the second rule set (e.g., see the above "ATSSS rule 505 with QUIC connection selection information"). Here, the rules in the combined rule set include a boot mode (e.g., QUIC-LL) and indicate via which boot connection to route the first data packet. The boot mode indicates via which access network to route the first data packet.

[0153] The first method includes establishing a plurality of pilot connections through each of a first access network and a second access network in response to receiving a second message and applying a first rule set and a second rule set to pilot the traffic of a multi-access data connection.

[0154] In some embodiments, piloting the traffic of a multi-access data connection may include using the first rule set to select an access network and using the second rule set to select a pilot connection through the selected access network. Alternatively, piloting the traffic of a multi-access data connection may include selecting an access network and using a combined rule set to select a pilot connection through the selected access network.

[0155] In certain embodiments, the first method includes encapsulating the traffic of a multi-access data connection in a QUIC datagram frame in response to selecting a pilot connection. In some embodiments, each pilot connection is associated with a QoS flow.

[0156] In some embodiments, each pilot connection terminates at a common UPF. In certain embodiments, each pilot connection uses a different UDP port at the common UPF. In certain embodiments, each pilot connection uses a different IP address of the common UPF. In some embodiments, the first type of pilot functionality is based on the QUIC protocol, wherein each of the plurality of pilot connections corresponds to a different QUIC connection between the device and the common UPF.

[0157] In some embodiments, the pilot connections are established according to the information in the second rule set. In various embodiments, the rules in the first rule set include a pilot mode that indicates through which access network the first data packet is to be routed, and wherein the rules in the second rule set indicate through which pilot connection the first data packet is to be routed.

[0158] Disclosed herein is a second apparatus for guiding the traffic of a multi-access data connection through a plurality of guiding connections according to an embodiment of the present disclosure. The second apparatus may be implemented by a UPF such as UPF 141, UPF 250, and / or network device apparatus 700. The second apparatus includes a processor and a memory that stores code executable by the processor to: A) communicate with a remote unit via a first access network, B) communicate with the remote unit via a second access network, wherein the remote unit supports a first type of guiding functionality (e.g., QUIC-LL) for creating a plurality of guiding connections (e.g., QUIC connections) through each of the first access network and the second access network, C) receive a first message (e.g., N4 session establishment request) including a first rule set (e.g., multi-access rule) and a second rule set (e.g., QUIC rule), wherein the first rule set indicates how to route the traffic of the multi-access data connection of the remote unit across the first access network and the second access network by using the first type of guiding functionality and the second rule set indicates how to route the traffic of the multi-access data connection across the plurality of guiding connections, D) receive a plurality of guiding connection requests (e.g., QUIC connection requests) from the remote unit, wherein each request is received through one of the first access network and the second access network, and E) apply the first rule set and the second rule set in response to accepting the plurality of guiding connections to guide the traffic of the multi-access data connection.

[0159] In some embodiments, the first message includes a combined rule set formed from the first rule set and the second rule set (e.g., see the above “ATSSS rule with QUIC connection selection information” 505). Here, the rules in the combined rule set include a guiding mode (e.g., QUIC-LL) and indicate through which guiding connection the first data packet is to be routed. The guiding mode indicates through which access network the first data packet is to be routed. In such embodiments, guiding the traffic of the multi-access data connection includes selecting an access network and using the combined rule set to select a guiding connection through the selected access network.

[0160] In certain embodiments, guiding the traffic of the multi-access data connection includes using the first rule set to select an access network and using the second rule set to select a guiding connection through the selected access network. In such embodiments, the processor encapsulates the traffic of the multi-access data connection in a QUIC datagram frame in response to selecting the guiding connection. In certain embodiments, each guiding connection is associated with a QoS flow.

[0161] In some embodiments, the first type of bootstrapping functionality is based on the QUIC protocol, where each of the plurality of bootstrapping connections corresponds to a different QUIC connection between the device and the remote unit. In certain embodiments, each bootstrapping connection uses a different UDP port at the device. In certain embodiments, each bootstrapping connection uses a different IP address of the device.

[0162] In some embodiments, in response to receiving a first message, the processor assigns a UDP port and an IP address to each of the plurality of bootstrapping connections. Alternatively, the SMF may assign the UDP port and the IP address for each QUIC connection. Here, each UDP port and IP address indicates the destination of each QUIC connection on the UPF side.

[0163] In some embodiments, the bootstrapping connections are established according to the information in the second rule set. Here, the QUIC rules sent to the UE include the UDP port / IP address of each QUIC connection, so the UE knows how to establish each QUIC connection.

[0164] In some embodiments, the rules in the first rule set include a bootstrapping mode that indicates through which access network to route the first data packet, and where the rules in the second rule set indicate through which bootstrapping connection to route the first data packet.

[0165] Disclosed herein is a second method for guiding the service of a multi-access data connection through a plurality of bootstrapping connections according to an embodiment of the present disclosure. The second method may be executed by a UPF such as UPF 141, UPF 250, and / or the network device apparatus 700. The second method includes: communicating with the UE via a first access network and via a second access network, where the remote unit supports a first type of bootstrapping functionality (e.g., QUIC-LL) for creating a plurality of bootstrapping connections (e.g., QUIC connections) through each of the first access network and the second access network; and receiving, at the UPF, a first message (e.g., an N4 session establishment request) that includes a first rule set (e.g., a multi-access rule) and a second rule set (e.g., a QUIC rule), where the first rule set indicates how to route the service of the multi-access data connection of the UE across the first access network and the second access network by using the first type of bootstrapping functionality and the second rule set indicates how to route the service of the multi-access data connection across the plurality of bootstrapping connections.

[0166] The second method includes: receiving, from the UE, a plurality of bootstrapping connection requests (e.g., QUIC connection requests), where each request is received through one of the first access network and the second access network; and applying the first rule set and the second rule set in response to accepting the plurality of bootstrapping connections to guide the service of the multi-access data connection.

[0167] In some embodiments, the first message includes a combined rule set formed from a first rule set and a second rule set (e.g., see the "ATSSS Rule with QUIC Connection Selection Information" 505 above). Here, the rules in the combined rule set include a bootstrapping mode (e.g., QUIC-LL) and indicate through which bootstrapping connection to route the first data packet. The bootstrapping mode indicates through which access network to route the first data packet. In such embodiments, the operation of bootstrapping a multi-access data connection includes selecting an access network and using the combined rule set to select a bootstrapping connection through the selected access network.

[0168] In certain embodiments, the operation of bootstrapping a multi-access data connection includes using the first rule set to select an access network and using the second rule set to select a bootstrapping connection through the selected access network. In such embodiments, the processor encapsulates the operation of the multi-access data connection within a QUIC datagram frame in response to selecting the bootstrapping connection. In certain embodiments, each bootstrapping connection is associated with a QoS flow.

[0169] In some embodiments, the first type of bootstrapping functionality is based on the QUIC protocol, where each of the plurality of bootstrapping connections corresponds to a different QUIC connection between the device and the remote unit. In certain embodiments, each bootstrapping connection uses a different UDP port at the device. In certain embodiments, each bootstrapping connection uses a different IP address of the device.

[0170] In some embodiments, the second method further includes assigning a UDP port and an IP address to each of the plurality of bootstrapping connections in response to receiving the first message. Alternatively, the SMF may assign the UDP port and IP address for each QUIC connection. Here, each UDP port and IP address indicates the destination of each QUIC connection on the UPF side.

[0171] In some embodiments, the bootstrapping connection is established according to the information in the second rule set. Here, the QUIC rules sent to the UE include the UDP port / IP address for each QUIC connection, so the UE knows how to establish each QUIC connection.

[0172] In some embodiments, the rules in the first rule set include a bootstrapping mode that indicates through which access network to route the first data packet, and where the rules in the second rule set indicate through which bootstrapping connection to route the first data packet.

[0173] Disclosed herein is a third apparatus for guiding the service of a multi-access data connection through a plurality of guiding connections according to an embodiment of the present disclosure. The third apparatus may be implemented by an SMF such as SMF 145, SMF 305, and / or network device apparatus 700. The third apparatus includes a first network interface for communicating with an AMF in a mobile communication network and a second network interface for communicating with a PCF in the mobile communication network. The third apparatus includes a processor that receives, via the AMF, a first message to establish a multi-access data connection between a UE and a UPF in the mobile communication network through a first access network and a second access network. Here, the first message indicates that the UE supports a first type of guiding functionality for creating a plurality of guiding connections (e.g., QUIC connections) through each of the first access network and the second access network. In one embodiment, the first message includes a PDU session establishment request and the first type of guiding functionality is the QUIC-LL functionality described herein.

[0174] The processor sends a second message to the PCF. Here, the second message indicates that the remote unit supports the first type of guiding functionality. In one embodiment, the second message includes an SM policy control creation request. The processor receives a first rule set (e.g., a PCC rule) containing multi-access data connection control information, and the multi-access data connection control information includes the first type of guiding functionality and a guiding mode.

[0175] The processor determines a second rule set (e.g., a rule for the UE) from the first rule set and determines a third rule set (e.g., a rule for the UPF) from the first rule set. The second rule set indicates how to route uplink data packets across the first access network and the second access network and how to route uplink data packets across a plurality of guiding connections, and the third rule set indicates how to route downlink data packets across the first access network and the second access network and how to route downlink packets across a plurality of guiding connections. The processor selects a UPF that supports the first type of guiding functionality, sends the second rule set to the remote unit via the AMF, and sends the third rule set to the selected UPF.

[0176] In some embodiments, each guiding connection is associated with a QoS flow. In some embodiments, each guiding connection uses a different IP address of the selected UPF. In some embodiments, the rules in the first rule set include a guiding mode that indicates through which access network the first data packet is to be routed and also indicates through which guiding connection the first data packet is to be routed.

[0177] In some embodiments, in response to receiving a first message, the processor assigns a UDP port and an IP address to each of a plurality of bootstrap connections. Alternatively, the UPF may assign the UDP port and the IP address for each QUIC connection. Here, each UDP port and IP address indicates the destination of each QUIC connection on the UPF side. The QUIC rules sent to the UE include the UDP port / IP address for each QUIC connection, so the UE knows how to establish each of them.

[0178] Disclosed herein is a third method for guiding the service of a multi-access data connection through a plurality of bootstrap connections according to embodiments of the present disclosure. The third method may be performed by an SMF such as SMF 145, SMF 305, and / or the network device apparatus 700. The third method includes receiving, via the AMF, a first message to establish a multi-access data connection between a UE and a UPF in a mobile communication network through a first access network and a second access network. Here, the first message indicates that the UE supports a first type of bootstrap functionality for creating a plurality of bootstrap connections (e.g., QUIC connections) through each of the first access network and the second access network. In one embodiment, the first message includes a PDU session establishment request and the first type of bootstrap functionality is the QUIC-LL functionality described herein.

[0179] The third method includes sending a second message to the PCF. Here, the second message indicates that the remote unit supports the first type of bootstrap functionality. In one embodiment, the second message includes an SM policy control creation request. The processor receives a first rule set (e.g., a PCC rule) containing multi-access data connection control information, and the multi-access data connection control information includes the first type of bootstrap functionality and a bootstrap mode.

[0180] The third method includes determining a second rule set (e.g., rules for the UE) from the first rule set and determining a third rule set (e.g., rules for the UPF) from the first rule set. The second rule set indicates how to route uplink data packets across the first access network and the second access network and how to route uplink data packets across a plurality of bootstrap connections, and the third rule set indicates how to route downlink data packets across the first access network and the second access network and how to route downlink packets across a plurality of bootstrap connections. The third method includes selecting a UPF that supports the first type of bootstrap functionality, sending the second rule set to the remote unit via the AMF, and sending the third rule set to the selected UPF.

[0181] In some embodiments, each bootstrapping connection is associated with a QoS flow. In some embodiments, each bootstrapping connection uses a different IP address of a selected UPF. In some embodiments, the rules in the first rule set include a bootstrapping mode that indicates which access network to route the first data packet through, and the rule also indicates which bootstrapping connection to route the first data packet through.

[0182] Embodiments may be practiced in other specific forms. The described embodiments are to be considered in all respects only as illustrative and not restrictive. Thus, the scope of the invention is indicated by the appended claims rather than by the foregoing description. All changes that come within the meaning and range of equivalency of the claims are to be embraced within their scope.

Claims

1. A user equipment (UE) for wireless communication, comprising: at least one memory; and at least one processor, the at least one processor being coupled to the at least one memory and configured to cause the UE to: send a first message to establish a multi-access data connection via a first access network and a second access network, wherein the first message indicates that the UE supports a type of boot functionality corresponding to multiple boot connections via the first access network and the second access network; receive a second message, the second message indicating a first rule set for routing traffic via the first access network and the second access network using the type of boot functionality, and a second rule set for routing the traffic via the multiple boot connections; establish the multi-access data connection via the first access network and the second access network, wherein the multi-access data connection is associated with multiple quality of service (QoS) flows; establish the multiple boot connections via the first access network and the second access network in response to the first message, the second message, or both, wherein the multiple boot connections include a first set of boot connections via the first access network and a second set of boot connections via the second access network, and wherein each boot connection in the first set of boot connections corresponds to one of the multiple QoS flows, and wherein each boot connection in the second set of boot connections corresponds to one of the multiple QoS flows; and apply the first rule set and the second rule set to route the traffic of the multi-access data connection.

2. The UE according to claim 1, wherein: the first rule set, the second rule set, or both indicate a boot mode, the boot mode indicates the first access network or the second access network for routing the traffic, and the boot mode further indicates a boot connection among the multiple boot connections for routing the traffic.

3. The UE according to claim 1, wherein, The at least one processor is configured to cause the UE to: select the first access network or the second access network based on the first rule set; select a boot connection among the multiple boot connections based on the second rule set, wherein the boot connection is associated with the selected first access network or the selected second access network; and route the traffic of the multi-access data connection based on the selected first access network or the selected second access network and the selected boot connection.

4. The UE according to claim 1, wherein The at least one processor is configured to cause the UE to: encapsulate the traffic in a datagram frame according to a transport protocol.

5. The UE according to claim 1, wherein Each of the multiple boot connections terminates at a common user plane function ("UPF").

6. The UE according to claim 5, wherein each of the multiple boot connections corresponds to a different QUIC connection between the UE and the common UPF.

7. The UE according to claim 5, wherein, Each of the multiple boot connections is associated with a different user datagram protocol ("UDP") port.

8. The UE according to claim 5, wherein Each of the plurality of bootstrap connections is associated with a different Internet Protocol (IP) address.

9. The UE according to claim 1, wherein The at least one processor is configured to cause the UE to establish the plurality of bootstrap connections in accordance with the second rule set.

10. The UE according to claim 1, wherein The first rule set indicates a bootstrap mode; The bootstrap mode indicates the first access network or the second access network for routing the traffic; and The second rule set indicates the bootstrap connections for routing the traffic.

11. A method performed by a user equipment (UE), the method comprising: Sending a first message to establish a multi-access data connection via a first access network and a second access network, wherein the first message indicates that the UE supports a type of bootstrap functionality corresponding to a plurality of bootstrap connections via the first access network and the second access network; Receiving a second message indicating a first rule set for routing traffic via the first access network and the second access network using the type of bootstrap functionality, and a second rule set for routing the traffic via the plurality of bootstrap connections; Establishing the multi-access data connection via the first access network and the second access network, wherein the multi-access data connection is associated with a plurality of Quality of Service (QoS) flows; Establishing the plurality of bootstrap connections via the first access network and the second access network in response to the first message, the second message, or both, wherein the plurality of bootstrap connections includes a first set of bootstrap connections via the first access network and a second set of bootstrap connections via the second access network, and wherein each bootstrap connection in the first set of bootstrap connections corresponds to one of the plurality of QoS flows, and wherein each bootstrap connection in the second set of bootstrap connections corresponds to one of the plurality of QoS flows; and Applying the first rule set and the second rule set to route the traffic of the multi-access data connection.

12. The method according to claim 11, wherein: The first rule set, the second rule set, or both indicate a bootstrap mode, The bootstrap mode indicates the first access network or the second access network for routing the traffic, and The bootstrap mode further indicates a bootstrap connection among the plurality of bootstrap connections for routing the traffic.

13. The method according to claim 11, further comprising: Selecting the first access network or the second access network based on the first rule set; Selecting a bootstrap connection among the plurality of bootstrap connections based on the second rule set, wherein the bootstrap connection is associated with the selected first access network or the selected second access network; and And Routing the traffic of the multi-access data connection based on the selected first access network or the selected second access network and the selected bootstrap connection.

14. The method according to claim 11 further comprises: Encapsulating the traffic in a datagram frame according to a transport protocol.

15. The method according to claim 11, wherein, Each of the plurality of bootstrap connections terminates at a common user plane function ("UPF").

16. The method according to claim 15, wherein each of the plurality of bootstrap connections corresponds to a different QUIC connection between the UE and the public UPF.

17. The method according to claim 15, wherein, Each of the plurality of bootstrap connections is associated with a different User Datagram Protocol ("UDP") port.

18. The method according to claim 15, wherein, Each of the plurality of bootstrap connections is associated with a different Internet Protocol (IP) address.

19. The method according to claim 11, further comprising: The plurality of bootstrap connections are established according to the second rule set.

20. The method according to claim 11, wherein: The first rule set indicates a bootstrap mode; The bootstrap mode indicates the first access network or the second access network for routing the traffic; and The second rule set indicates the bootstrap connections for routing the traffic.

Images