A user equipment and a method for multi-access data connection in a mobile network
By transmitting a single session management request for multiple access data connections, the method addresses inefficiencies in establishing dual PDU sessions, enabling simultaneous data bearers across 3GPP and non-3GPP networks for enhanced network performance.
Patent Information
- Application Number
- KR1020237008787
- Authority / Receiving Office
- KR · KR
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2017-07-10
- Publication Date
- 2026-11-11
- Estimated Expiration
- 2037-07-10
AI Technical Summary
Establishing multiple access data connections in 5G networks requires two separate UE-requested PDU sessions, which is inefficient and lacks a unified approach for managing data paths through different access networks.
A method for a UE to transmit a single session management request to establish a multiple access data connection through both a 3GPP and a non-3GPP access network, with data paths anchored in a common user plane function, enabling simultaneous data bearers for traffic transmission.
Facilitates efficient establishment of multi-access data connections by reducing the need for separate session requests and optimizing data path management across diverse networks, enhancing network flexibility and performance.
Smart Images

Figure 112023028552315-PAT00001_ABST
Abstract
Description
Technology Field
[0001] The subject matter disclosed in this specification generally relates to wireless communications, and more specifically to establishing data paths through multiple access networks for multiple access data access. Background Technology
[0002] The following abbreviations and acronyms are defined in this specification, at least some of which are mentioned in the following description.
[0003] 3GPP(Third Generation Partnership Project), ACK(Positive-Acknowledgment), AMF(Access and Mobility Management Function), BPSK(Binary Phase Shift Keying), CA(Carrier Aggregation), CCA(Clear Channel Assessment), CCE(Control Channel Element), CSI(Channel State Information), CSS(Common Search Space), DFT-S(Discrete Fourier Transform Spread), DCI(Downlink Control Information), DFT-S-OFDM(Discrete Fourier Transform Spread OFDM), DL(Downlink), DwPTS(Downlink Pilot Time Slot), eCCA(Enhanced Clear Channel Assessment), eMBB(Enhanced Mobile Broadband), eNB(Evolved Node B), ETSI(European Telecommunications Standards Institute), FBE(Frame Based Equipment), FDD(Frequency Division Duplex), FDMA(Frequency Division Multiple Access), GP(Guard Period), HARQ(Hybrid Automatic Repeat Request), IoT(Internet-of-Things), KPI(Key Performance Indicators), LAA(Licensed Assisted Access), LBE(Load Based Equipment), LBT(Listen-Before-Talk), LTE(Long Term Evolution), LTE-A(LTA Advanced), MAC(Medium Access Control),MA(Multiple Access), MCS(Modulation Coding Scheme), MTC(Machine Type Communication), mMTC(Massive MTC), MIMO(Multiple Input Multiple Output), MPTCP(Multipath TCP), MUSA(Multi User Shared Access), NB(Narrowband), NACK 또는 NAK(Negative-Acknowledgment), NF(Network Function), gNB(Next Generation Node B), NOMA(Non-Orthogonal Multiple Access), OFDM(Orthogonal Frequency Division Multiplexing), PCell(Primary Cell), PBCH(Physical Broadcast Channel), PDCCH(Physical Downlink Control Channel), PDSCH(Physical Downlink Shared Channel), PDMA(Pattern Division Multiple Access), PHICH(Physical Hybrid ARQ Indicator Channel), PRACH(Physical Random Access Channel), PRB(Physical Resource Block), PUCCH(Physical Uplink Control Channel), PUSCH(Physical Uplink Shared Channel), QoS(Quality of Service), QPSK(Quadrature Phase Shift Keying), RRC(Radio Resource Control), RACH(Random Access Procedure), RAR(Random Access Response), RS(Reference Signal), RSMA(Resource Spread Multiple Access), RTT(Round Trip Time),RX (Receive), SCMA (Sparse Code Multiple Access), SSF (Switching / Splitting Function), SR (Scheduling Request), SMF (Session Management Function), SRS (Sounding Reference Signal), SC-FDMA (Single Carrier Frequency Division Multiple Access), SCell (Secondary Cell), SCH (Shared Channel), SINR (Signal-to-Interference-Plus-Noise) Ratio), SIB (System Information Block), TB (Transport Block), TBS (Transport Block Size), TCP (Transmission Control Protocol), TDD (Time-Division Duplex), TDM (Time Division Multiplex), TRP (Transmission and Reception Point), TX (Transmit), UCI (Uplink Control Information), UDP (User Datagram Protocol), UE (User Entity / Equipment (Mobile Terminal)), UL (Uplink), UMTS (Universal Mobile Telecommunications System), UpPTS (Uplink Pilot Time Slot), URLLC (Ultra-reliability and There are Low-latency Communications), and WiMAX (Worldwide Interoperability for Microwave Access). As used herein, "HARQ-ACK" may collectively represent a positive acknowledgment ("ACK") and a negative acknowledgment ("NAK"). ACK signifies that the TB was received correctly, whereas NAK signifies that the TB was received incorrectly.
[0004] In 5G networks, the core network is intended to support multiple access PDU (MA-PDU) sessions between 3GPP access networks (including LTE, Advanced LTE, and New Radio) and non-3GPP (typically WLAN) access networks. An MA-PDU session refers to a data session consisting of two (and rarely more) PDU sessions established through different types of access networks (e.g., 3GPP AN and WLAN) that share the same attributes (e.g., same S-NSSAI, same SSC mode, same DNN, same type, same address / prefix, etc.). These PDU sessions established through different types of access networks terminate at the same UPF anchor (UPF-A).
[0005] However, establishing an MA-PDU session currently requires two separate UE-requested PDU sessions. First, an initial PDU session is established through one access, and then an additional PDU is also established through a different access. The additional PDU session is "associated" with the initial PDU session because it is established on the same APN and also includes a Network-based IP Flow Mobility ("NBIFOM") indication.
[0006] Methods for establishing a multiple access data connection are disclosed. Devices and systems also perform the functions of these methods. In some embodiments, a method of a session management function for establishing a multiple access data connection includes the step of receiving a first session management request through an access management function in a mobile communication network. Herein, the first session management request includes a second session management request transmitted by a remote unit communicating with the mobile communication network through a first access network and a second access network. The method includes the step of transmitting a first request to the access management function to establish a first data path for a multiple access data connection through the first access network in response to the first session management request. The method includes the step of transmitting a second request to the access management function to establish a second data path for a multiple access data connection through the second access network, wherein both the first data path and the second data path are anchored in a common user plane network function in the mobile communication network in response to the first session management request. In one embodiment, the second session management request is transmitted through the second access network.
[0007] In specific embodiments, a method of a UE for establishing a multi-access data connection comprises the steps of communicating with a mobile communication network through both a first access network and a second access network, and transmitting a request to establish a data connection through the second access network. The method comprises the steps of receiving a first request to set up a first data bearer for a data connection through the first access network in response to the request, and receiving a second request to set up a second data bearer for a data connection through the second access network in response to the request, wherein both the first data bearer and the second data bearer are used to carry traffic for the data connection. Brief explanation of the drawing
[0008] Further specific descriptions of the embodiments briefly described above will be made with reference to specific embodiments illustrated in the accompanying drawings. With the understanding that these drawings illustrate only some embodiments and are not to be considered as a limitation of scope, embodiments will be further described and explained in specific and detailed manner through the use of the accompanying drawings. FIG. 1 is a schematic block diagram showing an embodiment of a wireless communication system for establishing multiple access data connections. FIG. 2 is a block diagram illustrating an example of a network architecture for establishing multiple access data connections. FIG. 3 is a schematic block diagram showing an embodiment of a UE device for establishing a multiple access data connection. FIG. 4 is a schematic block diagram showing an embodiment of a session management device for establishing a multiple access data connection. FIG. 5a is a block diagram illustrating an example of a network procedure for establishing a multiple access data connection. Figure 5b is a continuation of the network procedure of Figure 5a. FIG. 6a is a block diagram illustrating an example of a network procedure for establishing a multiple access data connection. Figure 6b is a continuation of the network procedure of Figure 6a. FIG. 7 is a block diagram illustrating an example of a network procedure for establishing a multiple access data connection. FIG. 8 is a block diagram showing an embodiment of a UE having multiple access data connections. FIG. 9 is a schematic flowchart illustrating an embodiment of a method for establishing a multiple access data connection. FIG. 10 is a schematic flowchart illustrating another embodiment of a method for establishing a multiple access data connection. Specific details for implementing the invention
[0009] As would be understood by a person skilled in the art, aspects of the embodiments may be implemented as a system, device, method, or program product. Accordingly, the embodiments may take the form of entirely hardware embodiments, entirely software embodiments (including firmware, resident software, microcode, etc.), or embodiments combining software and hardware aspects.
[0010] For example, the disclosed embodiments may be implemented as hardware circuits comprising custom very-large-scale integration ("VLSI") circuits or gate arrays, standard semiconductors, such as logic chips, transistors, or other discrete components. The disclosed embodiments may also be implemented as programmable hardware devices, such as field-programmable gate arrays, programmable array logic, or programmable logic devices. As another example, the disclosed embodiments may include one or more physical or logical blocks of executable code that can be organized, for example, as objects, procedures, or functions.
[0011] Additionally, embodiments may take the form of a program product implemented in one or more computer-readable storage devices storing machine-readable code, computer-readable code, and / or program code, referred to hereinafter as code. The storage devices may be tangible, non-transient, and / or non-transmitting. The storage devices may not implement signals. In certain embodiments, the storage devices use only signals for accessing code.
[0012] Any combination of one or more computer-readable media may be used. A computer-readable medium may be a computer-readable storage medium. A computer-readable storage medium may be a storage device that stores code. A storage device may be, for example, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor system, device, or any suitable combination thereof, but is not limited thereto.
[0013] More specific examples of storage devices (a non-comprehensive list) will include electrical connections having one or more wires, portable computer diskettes, hard disks, random access memory (“RAM”), read-only memory (“ROM”), erasable programmable read-only memory (“EPROM”) or flash memory, portable compact disc read-only memory (“CD-ROM”), optical storage devices, magnetic storage devices, or any suitable combination thereof. In the context of this document, a computer-readable storage medium may be any tangible medium capable of containing or storing a program used by or in association with an instruction execution system, device, or device.
[0014] Throughout this specification, references to “one embodiment,” “an embodiment,” or similar language mean that a particular feature, structure, or characteristic described in relation to that embodiment is included in at least one embodiment. Accordingly, throughout this specification, appearances of phrases such as “in one embodiment,” “in an embodiment,” and similar language may all refer to the same embodiment, but are not necessarily so, and may mean “one or more but not all embodiments” unless explicitly stated otherwise. The terms “comprising,” “having,” and variations thereof mean “comprising but not limited thereto,” unless explicitly stated otherwise. Unless explicitly stated otherwise, an enumerated list of items does not imply that any or all of the items are mutually exclusive. The singular form also indicates “one or more” unless explicitly stated otherwise.
[0015] Furthermore, the described features, structures, or characteristics of the embodiments may be combined in any suitable manner. In the following description, numerous specific details, such as examples of programming, software modules, user choices, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., are provided to provide a thorough understanding of the embodiments. However, a person skilled in the art will recognize that the embodiments may be implemented without one or more of these specific details, or by other methods, components, materials, etc. In other cases, well-known structures, materials, or operations are not illustrated or described in detail to avoid obscurity of the aspects of the embodiments.
[0016] Aspects of the embodiments are described below with reference to 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 within the schematic flowcharts and / or schematic block diagrams, may be implemented by code. Such code may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing unit to create a machine that generates means for instructions executed through the processor of the computer or other programmable data processing unit to implement the functions / operations specified in the schematic flowcharts and / or schematic block diagrams.
[0017] Such code may also be stored in a storage device capable of instructing a computer, other programmable data processing unit, or other devices to function in a specific manner such that instructions stored in the storage device produce a manufactured article including instructions that implement the functions / operations specified in schematic flowcharts and / or schematic block diagrams.
[0018] Such code may also be loaded onto a computer, other programmable data processing device, or other devices to generate a process implemented by a computer, which causes code executed on a computer or other programmable device to provide processes for implementing functions / operations specified in schematic flowcharts and / or schematic block diagrams, thereby enabling a series of operation steps to be performed on the computer, other programmable device, or other devices.
[0019] The schematic flowcharts and / or schematic block diagrams in the drawings illustrate the architecture, function, and operation of possible implementations of devices, systems, methods, and program products according to various embodiments. In this regard, each block within the schematic flowcharts and / or schematic block diagrams may represent a module, segment, or part of code containing one or more executable instructions of code for implementing a specified logical function(s).
[0020] It should also be noted that in some alternative implementations, the functions shown in the blocks may occur in an order different from that shown in the drawings. For example, two consecutively drawn blocks may, in effect, be executed substantially simultaneously or, from time to time, in reverse order, depending on the functions included. Other steps and methods equivalent in function, logic, or effect for one or more of the blocks, or parts thereof, of the illustrated drawings may be conceived.
[0021] The descriptions of elements in each drawing may indicate elements in subsequent drawings. Similar numbers in all drawings indicate similar elements, including alternative embodiments of similar elements.
[0022] Methods, apparatuses, and systems are disclosed that enable a UE to establish a multiple access PDU (MA-PDU) session or other multiple access data access by transmitting a single session management (SM) request message to a mobile communication network. As described herein, the establishment of a multiple access data access may be initiated by the UE or by the network. While an MA-PDU session is generally used as an example to illustrate the establishment of a multiple access data access, other types of multiple access data access may be established using the disclosed methods, apparatuses, systems, and procedures.
[0023] FIG. 1 illustrates a wireless communication system (100) for establishing multiple access data access according to embodiments of the present disclosure. In one embodiment, the wireless communication system (100) includes at least one remote unit (105), a 3GPP access network (120) including at least one cellular base unit (125), a non-3GPP access network (130), 3GPP communication links (123), non-3GPP access communication links (133), and a mobile core network (140). Although a specific number of remote units (105), 3GPP access networks (120), base units (125), 3GPP communication links (123), non-3GPP access networks (130), non-3GPP communication links (133), and mobile core networks (140) are illustrated in FIG. 1, a person skilled in the art will recognize that any number of remote units (105), 3GPP access networks (120), base units (125), 3GPP communication links (123), non-3GPP access networks (130), non-3GPP communication links (133), and mobile core networks (140) may be included within the wireless communication system (100).
[0024] In one implementation, the wireless communication system (100) conforms to a 5G system as specified in 3GPP specifications. However, more generally, the wireless communication system (100) may implement some other open or proprietary communication networks, such as LTE or WiMAX among other networks. The present disclosure is not intended to be limited to the implementation of any specific wireless communication system architecture or protocol.
[0025] In one embodiment, the remote units (105) may include computing devices such as desktop computers, laptop computers, personal digital assistants ("PDAs"), tablet computers, smartphones, smart televisions (e.g., televisions connected to the Internet), smart devices (e.g., devices connected to the Internet), set-top boxes, game consoles, security systems (including security cameras), vehicle-mounted computers, network devices (e.g., routers, switches, modems), etc. In some embodiments, the remote units (105) include wearable devices such as smartwatches, fitness bands, optical head-mounted displays, etc. Additionally, the remote units (105) may be referred to as subscriber units, mobiles, mobile stations, users, terminals, mobile terminals, fixed terminals, subscriber stations, UE, user terminals, devices, or other terms used in the relevant technical field. Remote units (105) can communicate directly with one or more base units (125) via uplink ("UL") and downlink ("DL") communication signals. Additionally, UL and DL communication signals can be carried via 3GPP communication links (123). Similarly, remote units (105) can communicate with one or more non-3GPP access networks (130) via UL and DL communication signals carried by non-3GPP communication links (133).
[0026] In some embodiments, remote units (105) communicate with a remote host (155) via a network connection with a mobile core network (140). For example, the remote unit (105) may establish a PDU connection (or other data connection) with the mobile core network (140) using a 3GPP access network (120) and / or a non-3GPP access network (130). Subsequently, the mobile core network (140) relays traffic between the remote unit (105) and the remote host (155) using the PDU connection. In other embodiments, the remote unit (105) may communicate with the remote host (155) via a non-3GPP access network (130) without traffic passing through the mobile core network (140). This is referred to as direct offloading.
[0027] Base units (125) may be distributed across a geographical area. In certain embodiments, the base unit (125) may also be referred to as an access terminal, base, base station, node-B, eNB, gNB, home node-B, relay node, device, or any other term used in the relevant art. The base units (125) are part of a radio access network (“RAN”), such as a 3GPP access network (120), which may generally include one or more controllers communically coupled to one or more corresponding base units (125). These and other elements of the radio access network are not illustrated but are generally well known to a person skilled in the relevant art. The base units (125) connect to the mobile core network (140) through the 3GPP access network (120).
[0028] Base units (125) can serve multiple remote units (105) within a serving area, e.g., a cell or cell sector, via a wireless communication link. Base units (125) can communicate directly with one or more of the remote units (105) via communication signals. Generally, base units (125) transmit downlink ("DL") communication signals to serve the remote units (105) in the time, frequency, and / or spatial domains. Additionally, DL communication signals may be carried via 3GPP communication links (123). The 3GPP communication links (123) may be any suitable carrier in the licensed or unlicensed radio spectrum. The 3GPP communication links (123) facilitate communication between one or more remote units (105) and / or one or more base units (125).
[0029] Non-3GPP access networks (130) may be distributed across geographical areas. Each non-3GPP access network (130) may serve multiple remote units (105) as a serving area. Typically, the serving area of a non-3GPP access network (130) is smaller than the serving area of a base unit (125). Non-3GPP access networks (130) may communicate directly with one or more remote units (105) by receiving UL communication signals and transmitting DL communication signals to serve remote units (105) in time, frequency, and / or spatial domains. Both DL and UL communication signals are carried through non-3GPP communication links (133). The 3GPP communication links (123) and the non-3GPP communication links (133) may use different frequencies and / or different communication protocols. The non-3GPP access network (130) can communicate using unlicensed radio spectrum. The mobile core network (140) can provide services to the remote unit (105) through the non-3GPP access networks (130) as described in more detail in this specification.
[0030] In some embodiments, a non-3GPP access network (130) connects to a mobile core network (140) via a non-3GPP interoperability function ("N3IWF") (135). The N3IWF (135) provides interoperability between the non-3GPP AN (120) and the mobile core network (140) and supports connectivity via "N2" and "N3" interfaces. As illustrated, both the 3GPP access network (120) and the N3IWF (135) communicate with an AMF (145) using the "N2" interface and with UPFs (141, 142) using the "N3" interface.
[0031] In certain 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" if it is operated by a 3GPP operator or a trusted partner and supports certain security features such as strong public interface encryption. Although the N3IWF (135) is depicted as being located outside both the non-3GPP access network (130) and the core network (140), in other embodiments, the N3IWF (135) may be located co-located with the non-3GPP access network (130) or within the core network (140) (e.g., if the non-3GPP access network (130) is a trusted non-3GPP access network).
[0032] In one embodiment, the mobile core network (140) is a 5G core (“5GC”) or an advanced packet core (“EPC”) that can be coupled to other data networks, such as the Internet and private data networks, among other data networks. Each mobile core network (140) belongs to a single airborne terrestrial mobile network (“PLMN”). The present disclosure is not intended to be limited to the implementation of any particular wireless communication system architecture or protocol.
[0033] The mobile core network (140) includes several network functions ("NFs"). As illustrated, the mobile core network (140) includes a plurality of user plane functions ("UPFs"). Here, the mobile core network (140) includes a first UPF (141) serving a 3GPP access network (120), a second UPF (142) serving a non-3GPP access network (130), and an anchor UPF ("UPF-A") (143). The mobile core network (140) also includes a plurality of control plane functions, including, but not limited to, an access and mobility management function ("AMF") (145), a session management function ("SMF") (146), a policy control function ("PCF") (148), and an integrated data management function ("UDM") (149). Although specific numbers and types of network functions are illustrated in FIG. 1, a person skilled in the art will recognize that any number and type of network functions may be included in the mobile core network (140).
[0034] As illustrated, the remote unit (105) may be connected to both the base unit (125) within the 3GPP access network (120) and the base unit (not shown in FIG. 1) within the non-3GPP access network (130). The remote unit (105) may transmit a request to establish a data connection through either the 3GPP access network (120) or the non-3GPP access network (130). In some embodiments, this request includes an indication that a multiple access data connection will be established (e.g., a UE-initiated multiple access data connection). For example, the remote unit (105) may indicate that a multiple access data connection should be established by including a first session identifier (e.g., associated with the 3GPP access network (120)) and a second session identifier (e.g., associated with the non-3GPP access network (130)) in the establishment request. As another example, the remote unit (105) may indicate that a multi-access data connection should be established by including a session identifier and multi-access parameters in the request. In other embodiments, such a request does not include an indication that a multi-access data connection should be established (i.e., such a request is for a single-access data connection), but the SMF (146) receiving such a request decides to create a multi-access data connection (e.g., a network-initiated multi-access data connection).
[0035] After receiving a request to establish a data connection, the SMF (146) initiates a multiple access data connection by triggering the establishment of a data path (e.g., a child PDU session) through the non-3GPP access network (130) and the establishment of another data path (e.g., another child PDU session) through the 3GPP access network (120). For example, the SMF (146) may trigger the establishment of a data path by sending a session management ("SM") request to the AMF (145), as described below with reference to FIGS. 5 through 7. Note that the multiple access data connection is anchored in a common UPF (e.g., UPF-A (143)).
[0036] FIG. 2 illustrates a network architecture (200) used to establish multiple access data access according to embodiments of the present disclosure. The network architecture (200) may be a simplified embodiment of a wireless communication system (100). As illustrated, the network architecture (200) includes a UE (205) communicating with a mobile communication network (210) through both a 5G RAN (215) and a WLAN (220), such as a Wi-Fi RAN. As previously described, the 5G RAN (215) is an embodiment of a 3GPP access network (120), and the WLAN (220) is an embodiment of a non-3GPP access network (130). The mobile communication network (210) is an embodiment of the previously described core network (140) and includes a first UPF (141), a second UPF (142), an anchor UPF (143), an AMF (145), and an SMF (146). The WLAN (220) accesses a mobile communication network via an N3IWF (135), which, as described above, may be located jointly with the WLAN (220), located in a mobile core network, or located outside both the WLAN (220) and the mobile core network. The N3IWF (135) communicates with the AMF (145) via the "N2" interface and with the second UPF (142) via the "N3" interface. The 5G RAN (215) communicates with the AMF (145) via the "N2" interface and with the first UPF (141) via the "N3" interface.
[0037] As described herein, the UE (205) includes a protocol stack comprising an IP layer (201), a virtual interface layer (203), a WLAN interface (207), and a 5G radio interface (209). As described herein, after transmitting a single request to establish a data connection (e.g., an MA-PDU session), the UE (205) receives a request to establish a first data bearer (corresponding to a first child PDU session (225)) for a data connection over the 5G RAN (215) and a request to establish a second data bearer (corresponding to a second child PDU session (230)) for a data connection over the WLAN (220). These requests include one or more session identifiers included in the single request so that the UE (205) knows that they are all for the same MA-PDU session.
[0038] Accordingly, the UE (205) establishes a multi-access data connection (illustrated herein as an MA-PDU session) having two child PDU sessions: a first child PDU session (225) utilizing the 5G radio interface (209) and 5G RAN (215), and a second child PDU session (230) utilizing the WLAN interface (207) and WLAN (220) (e.g., a public Wi-Fi hotspot). The two child PDU sessions are connected to the UE at the "virtual interface" layer (203), which exposes a single IP interface to the upper layers (e.g., the IP layer (201)). Thus, the two child PDU sessions share the same IP address and constitute a multi-link data connection between the UE (205) and the UPF-A (143). FIG. 2 illustrates a scenario having three UPFs, namely a first UPF (141) interfacing with the 5G RAN (215), a second UPF (142) interfacing with the N3IWF (135), and an anchor UPF (143). However, in other scenarios, the UPFs (141, 142) may not be required, in which case, for example, the anchor UPF (143) can be directly interfaced with the 5G RAN (215) and the N3IWF (135).
[0039] FIG. 3 illustrates an embodiment of a UE device (300) that can be used to establish a multiple access data connection according to embodiments of the present disclosure. The UE device (300) may be an embodiment of a remote unit (105). Additionally, the UE device (300) may include a processor (305), a memory (310), an input device (315), a display (320), a first transceiver (325), and a second transceiver (330).
[0040] The first transceiver (325) communicates with a mobile communication network (e.g., a mobile core network (140)) through a first access network, while the second transceiver (330) communicates with a mobile communication network through a second access network. The first and second access networks facilitate communication between the mobile core network (140) and the UE device (300). In one embodiment, the first access network is a 5G RAN (215) or another 3GPP access network (120), and the second access network is a WLAN (220) or another non-3GPP access network (130). In another embodiment, the second access network is a 5G RAN (215) or another 3GPP access network (120), and the first access network is a WLAN (220) or another non-3GPP access network (130). In other embodiments, the first access network and the second access network may be access networks of different types, and the first access network is an access network of a different type from the second access network. Each transceiver (325, 330) may include at least one transmitter and at least one receiver. Additionally, the transceivers (325, 330) may support at least one network interface, such as a “Uu” interface used for communications between the remote unit (105) and the 3GPP access network (120).
[0041] In one embodiment, the processor (305) may include any known controller capable of executing computer-readable instructions and / or performing logical operations. For example, the processor (305) 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 (305) executes instructions stored in memory (310) to perform the methods and routines described herein. The processor (305) is communicably coupled to memory (310), an input device (315), a display (320), a first transceiver (325), and a second transceiver (330).
[0042] In some embodiments, the processor (305) transmits a request to establish a data connection. In certain embodiments, the request to establish a data connection includes an indication to establish a data connection through both the first and second access networks. In one embodiment, the indication to establish a data connection through both the first and second access networks includes a first session identifier associated with the first access network and a second session identifier associated with the second access network. In another embodiment, the indication to establish a data connection through both the first and second access networks includes a first session identifier and multiple access parameters. Here, the first session identifier is associated with both the first access network and the second access network.
[0043] In some embodiments, the processor (305) transmits a request to establish a data connection through a second access network. Additionally, the request to establish a data connection includes a session identifier associated with the second access network and does not include a session identifier associated with the first access network. In certain embodiments, the request to establish a data connection includes a mode parameter, and the mode parameter includes a requested mode of operation for a multi-access data connection.
[0044] In certain embodiments, the first access network is an access network not defined by 3GPP (“non-3GPP access”), and the second access network is an access network defined by 3GPP (“3GPP access”). In these embodiments, a request to establish a data connection may be a packet data unit (“PDU”) session request.
[0045] The processor (305) receives a first request to set up a first data bearer for data access through a first access network in response to the request, and also receives a second request to set up a second data bearer for data access through a second access network in response to the request. Here, both the first data bearer and the second data bearer are used to carry traffic for data access.
[0046] In certain embodiments, a request to establish a data connection includes a session identifier associated with a second access network and does not include an indication to establish a data connection through both the first and second access networks. Additionally, both a first request to establish a first data bearer for a data connection through the first access network and a second request to establish a second data bearer for a data connection through the second access network include a session identifier associated with the second access network. In these embodiments, the processor (305) determines that a request to establish a data connection through the second access network initiates the establishment of a multi-access data connection through the first access network and the second access network.
[0047] In one embodiment, memory (310) is a computer-readable storage medium. In some embodiments, memory (310) includes a volatile computer storage medium. For example, memory (310) may include RAM including dynamic RAM ("DRAM"), synchronous dynamic RAM ("SDRAM"), and / or static RAM ("SRAM"). In some embodiments, memory (310) includes a non-volatile computer storage medium. For example, memory (310) may include a hard disk drive, flash memory, or any other suitable non-volatile computer storage device. In some embodiments, memory (310) includes both volatile and non-volatile computer storage media. In some embodiments, memory (310) stores data regarding the establishment of multiple access data connections, such as session identifiers, protocol stacks, security keys, messages, etc. In some embodiments, the memory (310) also stores program code and related data, such as operating systems or other controller algorithms, that run on the UE device (300) and one or more software applications.
[0048] The input device (315) may, in one embodiment, include any known computer input device, such as a touch panel, a button, a keyboard, a stylus, a microphone, etc. In some embodiments, the input device (315) may be integrated with the display (320), for example, as a touchscreen or a similar touch-sensitive display. In some embodiments, the input device (315) includes a touchscreen on which text can be entered using a virtual keyboard displayed on the touchscreen and / or handwriting on the touchscreen. In some embodiments, the input device (315) includes two or more different devices, such as a keyboard and a touch panel.
[0049] In one embodiment, the display (320) may include any known electronically controllable display or display device. The display (320) may be designed to output visual, auditory, and / or tactile signals. In some embodiments, the display (320) includes an electronic display capable of outputting visual data to a user. For example, the display (320) 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 display (320) may include a wearable display such as a smart watch, smart glasses, or a head-up display. Additionally, the display (320) may be a component such as a smartphone, a personal information terminal, a television, a table computer, a laptop computer, a personal computer, or a vehicle dashboard.
[0050] In certain embodiments, the display (320) includes one or more speakers for generating sound. For example, the display (320) may generate an audible alarm or notification (e.g., a beep or a chime). In some embodiments, the display (320) includes one or more haptic devices for generating vibrations, motion, or other haptic feedback. In some embodiments, all or part of the display (320) may be integrated with an input device (315). For example, the input device (315) and the display (320) may form a touchscreen or a similar touch-sensitive display. In other embodiments, the display (320) may be located near the input device (315). In certain embodiments, the UE device (300) may not include any input device (315) and / or display (320).
[0051] As discussed above, the first transceiver (325) communicates with the mobile communication network through the first access network, while the second transceiver (330) communicates with the mobile communication network through the second access network. The transceivers (325 and 330) operate under the control of the processor (305) to transmit messages, data, and other signals, and also to receive messages, data, and other signals. For example, the processor (305) may selectively activate one or both of the transceivers (325, 330) (or parts thereof) at specific times to transmit and receive messages. The first transceiver (325) may include one or more transmitters and one or more receivers for communicating through the first access network. Similarly, the second transceiver (330) may include one or more transmitters and one or more receivers for communicating through the second access network. As discussed above, the first transceiver (325) and the second transceiver (330) may support one or more network interfaces to communicate with a mobile communication network.
[0052] FIG. 4 illustrates an embodiment of a session management device (400) that can be used to establish a multiple access data connection according to embodiments of the present disclosure. The session management device (400) may be an embodiment of an SMF (146). Additionally, the session management device (400) may include a processor (405), a memory (410), an input device (415), a display (420), and a transceiver (425). In some embodiments, the input device (415) and the display (420) are combined into a single device, such as a touchscreen. In certain embodiments, the session management device (400) may not include any input device (415) and / or display (420).
[0053] As described, the transceiver (425) includes at least one transmitter (430) and at least one receiver (435). Additionally, the transceiver (425) may support at least one network interface (440), such as a “Na” interface used for communications between the UE and the session management device (400). Here, the network interface (440) facilitates communication with network functions such as an AMF (145), a PCF (148), and / or a UDM (149). Additionally, at least one network interface (440) may include an “N11” interface used for communications with the AMF, an “N4” interface used for communication with the UDM, etc.
[0054] In one embodiment, the processor (405) may include any known controller capable of executing computer-readable instructions and / or performing logical operations. For example, the processor (405) 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 (405) executes instructions stored in memory (410) to perform the methods and routines described herein. The processor (405) is communicably coupled to memory (410), an input device (415), a display (420), and a transceiver (425).
[0055] In some embodiments, the processor (405) receives a first session management ("SM") request through an access management function. Here, the first SM request includes a second SM request transmitted by a remote unit (e.g., a second SM request embedded in the first SM request). The remote unit communicates with a mobile communication network through a first access network and a second access network, and has simultaneous accesses through both access networks. In one embodiment, the remote unit transmits a second SM message through the first access network. In another embodiment, the remote unit transmits a second SM message through the second access network. In one embodiment, the second SM message includes a mode parameter, and the mode parameter includes a requested operation mode for multiple access data access.
[0056] In response to a first session management request, the processor (405) transmits a first request to the access management function to establish a first data path for a multiple access data connection through a first access network. In some embodiments, the processor (405) decides to form a multiple access data connection based on the contents of the first SM request. For example, the first SM request may include multiple access parameters or specific requests for a multiple access data connection. As another example, the processor (405) may decide to form a multiple access data connection in response to the need to offload data traffic to a non-3GPP access network.
[0057] The processor (405) also sends a second request to the access management function to establish a second data path for multiple access data access through the second access network in response to the first session management request, and both the first data path and the second data path are anchored in the common user plane network function in the mobile communication network. In some embodiments, the establishment of the first and second data paths may occur simultaneously.
[0058] In the case of sequential establishment, the first established data path (in time) is determined based on the access network used by the remote unit to transmit the second SM request. For example, if the second SM message is transmitted through the first access network, the second data path through the second access network will be established before the first data path. As another example, if the second SM message is transmitted through the second access network, the first data path through the first access network will be established before the second data path.
[0059] In some embodiments, a first session management request (e.g., received from an AMF) includes an indication to establish a multi-access data connection to a remote unit through both a first access network and a second access network. For example, the indication to establish a multi-access data connection to a remote unit through both a first access network and a second access network may be a first session identifier associated with the first access network and a second session identifier associated with the second access network. As another example, the indication to establish a multi-access data connection to a remote unit through both a first access network and a second access network may be a multi-access parameter included with a (single) session identifier.
[0060] In certain embodiments, the processor (405) queries a policy control function for at least one of the multiple access routing rules and multiple access QoS rules associated with a remote unit. Here, the multiple access QoS rules include QoS rules for a first access network and QoS rules for a second access network. The multiple access routing rules indicate how to route traffic for multiple access data access across the first access network and the second access network. Additionally, the processor (405) may send a session establishment request to a common user plane function anchoring the first and second data paths, and the session establishment request includes multiple access routing rules and an indication that the first and second data paths are for multiple access data access.
[0061] In some embodiments, the second session management request is a request from a remote unit to establish a data connection over a single access network. Additionally, the first session management request may include an indication that the remote unit has simultaneous connections to both the first access network and the second access network. In these embodiments, the processor (405) may decide to establish a multi-access data connection in response to receiving the first session management request (and the indication that the remote unit has simultaneous connections to both the first access network and the second access network).
[0062] In certain embodiments, the processor (405) also queries a data management function (e.g., UDM (149)) in response to receipt of a first session management request to determine whether the remote unit's network join allows multiple access access. In these embodiments, the processor (405) may decide to establish multiple access data access based on the remote unit's network join. In certain embodiments, the processor (405) further queries a policy control function (e.g., PCF (148)) in response to receipt of a first session management request for at least one of the multiple access QoS rules and multiple access routing rules associated with the requested data access, wherein the processor decides to establish multiple access data access based on at least one of the multiple access routing rules and multiple access QoS rules received from the policy control function.
[0063] In some embodiments, the first access network is a non-3GPP access network (e.g., an access network not defined by 3GPP), and the second access network is a 3GPP network (e.g., an access network defined by 3GPP). Additionally, the second SM request (e.g., transmitted by a remote unit) may be a PDU session establishment request. In these embodiments, transmitting a first request to the AMF to establish a first data path for multiple access data access may include transmitting a third SM request to the AMF without an N1 session management container with a built-in processor (405), and the third SM request indicates that the AMF transmits the first request to the first access network.
[0064] Additionally, transmitting a second request to the AMF to establish a second data path for a multi-access data connection may include the processor (405) transmitting a response to the first SM request, and such response includes an embedded N1 session management container. Here, the embedded N1 session management container includes a response to the second SM message. Thus, the embedded N1 session management container is transmitted over the same access network used to transmit the second SM message by the remote unit. In one embodiment, the N1 session management container includes a PDU session establishment access message that includes multi-access routing rules and multi-access quality of service ("QoS") rules associated with the multi-access data connection.
[0065] In one embodiment, memory (410) is a computer-readable storage medium. In some embodiments, memory (410) includes a volatile computer storage medium. For example, memory (410) may include RAM including dynamic RAM ("DRAM"), synchronous dynamic RAM ("SDRAM"), and / or static RAM ("SRAM"). In some embodiments, memory (410) includes a non-volatile computer storage medium. For example, memory (410) may include a hard disk drive, flash memory, or any other suitable non-volatile computer storage device. In some embodiments, memory (410) includes both volatile and non-volatile computer storage media. In some embodiments, memory (410) stores data regarding the establishment of a multiple access data connection, such as session identifiers associated with a remote unit, protocol stacks, messages, security keys, multiple access policy rules, etc. In certain embodiments, the memory (410) also stores program code and related data, such as operating systems or other controller algorithms, that run on the session management device (400) and one or more software applications.
[0066] The input device (415) may, in one embodiment, include any known computer input device, such as a touch panel, a button, a keyboard, a stylus, a microphone, etc. In some embodiments, the input device (415) may be integrated with the display (420), for example, as a touchscreen or a similar touch-sensitive display. In some embodiments, the input device (415) includes a touchscreen on which text can be entered using a virtual keyboard displayed on the touchscreen and / or handwriting on the touchscreen. In some embodiments, the input device (415) includes two or more different devices, such as a keyboard and a touch panel.
[0067] In one embodiment, the display (420) may include any known electronically controllable display or display device. The display (420) may be designed to output visual, auditory, and / or tactile signals. In some embodiments, the display (420) includes an electronic display capable of outputting visual data to a user. For example, the display (420) 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 display (420) may include a wearable display such as a smart watch, smart glasses, or a head-up display. Additionally, the display (420) may be a component such as a smartphone, a personal information terminal, a television, a table computer, a laptop computer, a personal computer, or a vehicle dashboard.
[0068] In certain embodiments, the display (420) includes one or more speakers for generating sound. For example, the display (420) may generate an audible alarm or notification (e.g., a beep or a chime). In some embodiments, the display (420) includes one or more haptic devices for generating vibrations, motion, or other haptic feedback. In some embodiments, all or part of the display (420) may be integrated with an input device (415). For example, the input device (415) and the display (420) may form a touchscreen or a similar touch-sensitive display. In other embodiments, the display (420) may be located near the input device (415).
[0069] The transceiver (425) communicates with one or more network functions of a mobile communication network. The transceiver (425) operates under the control of the processor (405) to transmit messages, data, and other signals, and also to receive messages, data, and other signals. For example, the processor (405) may selectively activate the transceiver (or parts thereof) at specific times to transmit and receive messages. The transceiver (425) may include one or more transmitters (430) and one or more receivers (435). As discussed above, the transceiver (425) may support one or more network interfaces (440) to communicate with the base unit (125).
[0070] FIG. 5 illustrates a network procedure (500) for establishing a multiple access data connection according to embodiments of the present disclosure. The network procedure (500) is a UE initiation procedure for establishing a multiple access data connection from a single UE request to establish a data connection. The network procedure involves a UE (205), a 5G RAN (215), an N3IWF (135), an AMF (145), an SMF (146), a first UPF (141), a second UPF (142), an anchor UPF (143), and a PCF (148). Here, the UE (205) is simultaneously connected to a mobile communication network via a 3GPP access network (here, 5G RAN (215)) and a non-3GPP access network (e.g., a WLAN (220)).
[0071] Network procedure (500) begins as the UE (205) wishes to establish an MA-PDU session through both access networks and transmits a NAS message containing a "PDU session establishment request" to the AMF (145) (see operation (502)). In the embodiments of FIG. 5a, the NAS message is transmitted through the 5G RAN (215) (e.g., a 3GPP access network), but in other embodiments, the NAS message may be transmitted through a non-3GPP access network. The NAS message also includes two PDU session identities: a first PDU session identity (ID-1) associated with the 3GPP access network (e.g., including the 5G RAN (215)) and a second PDU session identity (ID-2) associated with the non-3GPP access network. This is in contrast to conventional NAS messages transmitted for PDU session establishment, which always include only one PDU session identity.
[0072] In certain embodiments, the UE (205) indicates that it wishes to establish an MA-PDU through both 3GPP and non-3GPP access networks by including two PDU session identities in the NAS message. The NAS message transmitted by the UE (205) may also include other information, such as the requested DNN (Data Network Name), the requested slice type, etc. In some embodiments, the “PDU Session Establishment Request” message may include a mode parameter indicating the requested mode of operation of the MA-PDU session. For example, the mode parameter may indicate that the UE (205) prefers the MA-PDU session to operate in an active / standby mode, such that the child PDU session through the non-3GPP access network becomes the “active” child and the child PDU session through the 3GPP access network becomes the “standby” child. As another example, the UE (205) may prefer that child PDU sessions through the 3GPP access network become "active" children and child PDU sessions through the non-3GPP access network become "waiting" children.
[0073] In active / standby mode, all traffic of the MA-PDU session is transmitted through the "active" child PDU session, while the other child PDU session ("standby" child) carries no traffic. When the "active" child PDU session becomes unavailable to the UE (205) (e.g., due to a lack of radio signal), it becomes the "standby" child, and the UE (205) transmits all traffic of the MA-PDU session to the other child PDU session that becomes the "active" child. When the network receives traffic from the UE (205) through the "standby" child PDU session, it changes this child PDU session to "active." When the MA-PDU session operates in active / standby mode, there is no need to apply any multiple access routing rules (discussed below).
[0074] Next, the AMF (145) selects the SMF (146) and sends an SM request (e.g., a first SM request) to the SMF (146) (see operation (504)). The SM request includes a "PDU session establishment request" received from the UE (205). The SM request further includes an access network type parameter. Here, this parameter has the value "Access Network Type = 3GPP" to indicate to the SMF (146) that the PDU session establishment request was received through a 3GPP access network (e.g., a 5G RAN (215)). If the PDU session establishment request is received through a non-3GPP access network, the value "Access Network Type = Non-3GPP" will be used. Additionally, the SM request includes two PDU session identities provided by the UE (205) to further indicate that the UE (205) wishes to establish an MA-PDU session. In certain embodiments, the SM request additionally includes a multiple access parameter to indicate whether a multiple access data connection (here, MA-PDU) will be established. Note that the multiple access parameter is duplicated when the UE (205) provides two PDU session identities.
[0075] The SMF (146) selects a PCF (here, PCF (148)) and normally establishes a new session with the selected PCF (148) (see operation (506)). Subsequently, the SMF (146) retrieves from the PCF (148) multiple access routing rules to be applied in the UE (205) and UPF-A (143) to determine how to route uplink and downlink traffic across two child PDU sessions, respectively. These multiple access routing rules are also known as "traffic coordination rules." As used herein, traffic coordination rules refer to rules provided to remote units (105) by the mobile core network (103). Traffic coordination rules are used by the UE (205) for access selection when initiating a new data flow. For example, a multi-access routing rule can indicate "selection of child PDU session #2 for app-x" or "selection of child PDU session #2 for non-IMS traffic between 9 AM and 5 PM". As another example, a multi-access routing rule can coordinate HTTP traffic for child PDU session #2 and VoIP traffic for child PDU session #1.
[0076] The SMF (146) can also retrieve multiple access QoS rules from the PCF (148). The multiple access QoS rules include QoS rules that must be applied through the 5G RAN (215) (e.g., 3GPP access network) and QoS rules that must be applied through a non-3GPP access network. The purpose of the QoS rules applied through one access network is to allow traffic on this access network to be transmitted with different QoS characteristics, such as different priorities, different guaranteed bit rates, etc.
[0077] After communicating with the PCF (148), the SMF (146) initiates the establishment of a user plane for a child PDU session using a non-3GPP access network (see operation (508)). Here, the SMF (146) sends a session establishment request (see operation (510)) to the second UPF (142) (serving N3IWF (135)) and receives an acknowledgment in response (see operation (512)). The SMF (146) also sends a session establishment request (see operation (514)) to the anchor UPF (143) and receives an acknowledgment in response (see operation (516)).
[0078] Next, the SMF (146) sends an SM request to the AMF (145) with the new parameter “Access Network Type = Non-3GPP” (see operation (518)) to indicate to the AMF (145) that the included N2 SM information should be sent to a non-3GPP access network (and not a 3GPP access network where the “PDU session establishment request” was received). Note that this SM request message does not contain a NAS message for the UE (205) (there is no N1 SM container). This is because the SM request message is not a response to the AMF’s previous SM request (e.g., a UE initiation request), but rather a new SM request initiated by the SMF (146).
[0079] The AMF (145) transmits N2 SM information, i.e., a PDU session request message, to the N3IWF (135) (see operation (520)). The PDU session request message contains QoS profile(s) to be applied through a non-3GPP access network, each of which is determined from QoS rules to be applied through a non-3GPP access network provided by the PCF (148) in operation (506). Additionally, the N3IWF (135) receives the PDU session ID-2 provided by the UE (205) in operation (502) and associated with the non-3GPP access network.
[0080] In response, N3IWF (135) establishes one or more IPsec child security associations (SAs) with UE (205) (see operation (522)). Each IPsec SA carries one or more QoS flows for a child PDU session established over a non-3GPP access network (e.g., a second child PDU session (230)). Each QoS flow is associated with a QoS profile received by N3IWF (135) in a PDU session request message. Next, N3IWF (135) sends a PDU session request acknowledgment message to AMF (145) (see operation (524)), and AMF (145) sends an SM request acknowledgment message to SMF (146) (see operation (526)). SMF (146) also sends a session modification request to the second UPF (142) (see operation (528)) and receives an acknowledgment message in response (see operation (530)).
[0081] Continuing from FIG. 5b, the SMF (146) initiates the establishment of a user plane for a child PDU session over 3GPP (e.g., a first child PDU session (225)) using a 3GPP access network (see operation (532)). Here, the SMF (146) sends a session establishment request (see operation (534)) to the first UPF (141) (serving the 5G RAN (215)) and receives an acknowledgment in response (see operation (536)).
[0082] SMF (146) also sends a second session establishment request to Anchor UPF (143) (see operation (538)) and receives a second acknowledgment in response (see operation (540)). Using the second session establishment request, SMF (146) provides multiple access routing rules to Anchor UPF (143) (see operation (538)). As previously described, Anchor UPF (143) uses the multiple access routing rules to determine how to route downlink traffic across two child PDU sessions. SMF (146) also provides Anchor UPF (143) with a "linked PDU session" parameter notifying it to associate the new PDU session with a previously established PDU session (e.g., in operation (514)). This parameter indicates that the anchor UPF (143) must consider the identified PDU sessions as child PDU sessions of the same MA-PDU session and apply multiple access routing rules to route downlink traffic across these child PDU sessions.
[0083] Next, in response to an SM request in operation (504), the SMF (146) sends an SM request acknowledgment message to the AMF (145) (see operation (542)). The SM request acknowledgment message includes N1 SM container containing a "PDU session establishment accepted" message and N2 SM information for the 5G RAN (215). Here, the "PDU session establishment accepted" message includes (a) multiple access QoS rules and (b) multiple access routing rules to be applied by the UE (205). FIG. 8 illustrates how these rules are applied by the UE (205).
[0084] Returning to FIG. 5b, the “Accept PDU Session Establishment” message is a response to the “Request PDU Session Establishment” message transmitted by the UE (205) in operation (502). In certain embodiments, the “Accept PDU Session Establishment” message may include a mode parameter indicating the negotiated mode of operation of the MA-PDU session. This mode may be the same as or different from the mode requested by the UE (205). For example, the UE (205) may request an active / standby mode where the “active” child is a child PDU session over a non-3GPP access network, but the network may decide to change the “active” child to a child PDU session over a 3GPP access network.
[0085] The AMF (145) transmits N2 SM information, i.e., a PDU session request message, to the 5G RAN (215) (see operation (544)). The PDU session request message contains QoS profile(s) to be applied through the 5G RAN (215) (e.g., a 3GPP access network), and each profile is determined from QoS rules to be applied through the 3GPP access network, as provided by the PCF (148) in operation (506). Additionally, the 5G RAN (215) receives PDU session ID-1, which was provided by the UE (205) in operation (502) and associated with the 3GPP access network.
[0086] In response, the 5G RAN (215) sends a "PDU session establishment accepted" message to the UE (205). Additionally, the 5G RAN (215) and the UE (205) establish one or more data radio bearers (DRBs), and each DRB is associated with one or more QoS rules (e.g., for transmitting traffic that matches these QoS rules). Each DRB carries one or more QoS flows for a child PDU session (e.g., a first child PDU session (225)) through the 3GPP access network. Each QoS flow is associated with a QoS profile transmitted to the 5G RAN (215).
[0087] Next, the 5G RAN (215) sends an acknowledgment message to the AMF (145) (see operation (548)), and the AMF (145) sends an SM request message containing N2 information to the SMF (146) (see operation (550)). Then, the SMF (146) sends a session modification request to the first UPF (141) (see operation (552)) and receives an acknowledgment message in response (see operation (554)). The SMF (146) procedure sends the SM request acknowledgment message to the AMF (145), and the network procedure (500) terminates.
[0088] Note that DRBs established through a 3GPP access network (e.g., 5G RAN (215)) serve the same purpose as child IPsec SAs established through a non-3GPP access network, that is, they all provide multiple communication bearers with different QoS characteristics. Also, while FIG. 5 illustrates the sequential establishment of child PDU sessions, in other embodiments, two child PDU sessions are established in parallel.
[0089] FIG. 6 illustrates a network procedure (600) for establishing multiple access data access from a single UE (205) request, according to embodiments of the present disclosure. The network procedure (600) is also a UE (205) initiation procedure and shares many similarities with the network procedure (500). The network procedure (600) involves the UE (205), 5G RAN (215), N3IWF (135), AMF (145), SMF (146), first UPF (141), second UPF (142), anchor UPF (143), and PCF (148). Again, the UE (205) is simultaneously connected to a mobile communication network via a 3GPP access network (here, 5G RAN (215)) and a non-3GPP access network (e.g., WLAN (220)).
[0090] Network procedure (600) begins as the UE (205) wishes to establish an MA-PDU session through both access networks and transmits a NAS message containing a "PDU session establishment request" to the AMF (145) (see operation (602)). In the embodiments of FIG. 6a, the NAS message is transmitted through the 5G RAN (215) (e.g., a 3GPP access network), but in other embodiments, the NAS message may be transmitted through a non-3GPP access network. The NAS message includes multiple access parameters and a single PDU session identity indicating that the UE (205) wishes to establish a multiple access PDU session. This is in contrast to conventional NAS messages transmitted for PDU session establishment without multiple access parameters.
[0091] The NAS message transmitted by the UE (205) may also include other information such as the requested DNN (Data Network Name), the requested slice type, etc. In some embodiments, the “PDU Session Establishment Request” message may include a mode parameter indicating the requested mode of operation of the MA-PDU session. For example, the mode parameter may indicate that the UE (205) prefers the MA-PDU session to operate in an active / standby mode, such that the child PDU session through the non-3GPP access network becomes the “active” child and the child PDU session through the 5G RAN (215) becomes the “standby” child. As another example, the UE (205) may prefer the child PDU session through the 5G RAN (215) becomes the “active” child and the child PDU session through the non-3GPP access network becomes the “standby” child.
[0092] In active / standby mode, all traffic of the MA-PDU session is transmitted through the "active" child PDU session, while the other child PDU session ("standby" child) carries no traffic. When the "active" child PDU session becomes unavailable to the UE (205) (e.g., due to a lack of radio signal), it becomes the "standby" child, and the UE (205) transmits all traffic of the MA-PDU session to the other child PDU session that becomes the "active" child. When the network receives traffic from the UE (205) through the "standby" child PDU session, it changes this child PDU session to "active." When the MA-PDU session operates in active / standby mode, there is no need to apply any multiple access routing rules (discussed below).
[0093] Next, the AMF (145) selects the SMF (146) and sends an SM request (e.g., a first SM request) to the SMF (146) (see operation (604)). The SM request includes a "PDU session establishment request" received from the UE (205). The SM request further includes an access network type parameter. Here, this parameter has a value "Access Network Type = 3GPP" to indicate to the SMF (146) that the PDU session establishment request was received through a 3GPP access network (e.g., a 5G RAN (215)). If the PDU session establishment request is received through a non-3GPP access network, the value "Access Network Type = Non-3GPP" will be used.
[0094] Additionally, the SM request includes a PDU session identity and a multiple access indicator provided by the UE (205). Note that in the network procedure (600), the same PDU session ID is used for both access networks. In certain embodiments, the SM request further includes multiple access parameters to indicate to the SMF (146) whether a multiple access data connection (here, MA-PDU) will be established.
[0095] SMF (146) selects and retrieves multiple access routing rules and multiple access QoS rules from PCF (148) as described in operation (506). SMF (146) also initiates the establishment of a user plane for a child PDU session using a non-3GPP access network (see operation (508)), sends a session establishment request (see operation (510)) to the second UPF (142) (serving N3IWF (135)), and receives an acknowledgment in response (see operation (512)). SMF (146) also sends a session establishment request (see operation (514)) to the anchor UPF (143) and receives an acknowledgment in response (see operation (516)).
[0096] Next, the SMF (146) sends an SM request to the AMF (145) with a new parameter "Access Network Type = Non-3GPP" (see operation (518)) to indicate to the AMF (145) that the included N2 SM information should be sent to the non-3GPP access network (and not the 3GPP access network where the NAS "PDU Session Establishment Request" was received). Again, since this SM request message is not a response to the AMF's previous SM request, it does not include a NAS message for the UE (205) (there is no N1 SM container).
[0097] The AMF (145) transmits N2 SM information to the N3IWF (135) as a PDU session request message (see operation (620)). The PDU session request message contains QoS profile(s) to be applied over a non-3GPP access network, each of which is determined from QoS rules to be applied over a non-3GPP access network provided by the PCF (148) in operation (506). Additionally, the N3IWF (135) receives a single PDU session ID provided by the UE (205) in operation (602).
[0098] In response, N3IWF (135) establishes one or more IPsec child security associations (SAs) with UE (205) (see operation (622)). Each IPsec SA carries one or more QoS flows for a child PDU session established over a non-3GPP access network (e.g., a second child PDU session (230)). Next, N3IWF (135) sends a PDU session request acknowledgment message to AMF (145) (see operation (524)), and AMF (145) sends an SM request acknowledgment message to SMF (146) (see operation (526)). SMF (146) also sends a session modification request to the second UPF (142) (see operation (528)) and receives an acknowledgment message in response (see operation (530)).
[0099] Continuing from FIG. 6b, the SMF (146) initiates the establishment of a user plane for a child PDU session over 3GPP (e.g., a first child PDU session (225)) using a 3GPP access network (see operation (532)). Here, the SMF (146) sends a session establishment request (see operation (534)) to the first UPF (141) (serving the 5G RAN (215)) and receives an acknowledgment in response (see operation (536)). The SMF (146) also sends a second session establishment request to the anchor UPF (143) (see operation (538)) and receives a second acknowledgment in response (see operation (540)).
[0100] Next, in response to an SM request in operation (504), the SMF (146) sends an SM request acknowledgment message to the AMF (145) (see operation (542)). The SM request acknowledgment message includes N1 SM container containing a NAS "Accept PDU Session Establishment" message and N2 SM information for the 5G RAN (215). Here, the NAS "Accept PDU Session Establishment" message includes (a) multiple access QoS rules and (b) multiple access routing rules to be applied by the UE (205). In certain embodiments, the "Accept PDU Session Establishment" message may include a mode parameter indicating the negotiated mode of operation for the MA-PDU session. This mode may be the same as or different from the mode requested by the UE (205). For example, UE (205) may request an active / standby mode where the “active” child is a child PDU session through a non-3GPP access network, but the network may decide to change the “active” child to a child PDU session through a 3GPP access network.
[0101] The AMF (145) transmits N2 SM information to the 5G RAN (215) as a PDU session request message (see operation (644)). The PDU session request message contains QoS profile(s) to be applied through the 5G RAN (215) (e.g., 3GPP access network), and each profile is determined from QoS rules to be applied through the 3GPP access network, as provided by the PCF (148) in operation (506). Additionally, the 5G RAN (215) receives a single PDU session ID provided by the UE (205).
[0102] In response, the 5G RAN (215) sends a NAS "Accept PDU Session Establishment" message to the UE (205). Additionally, the 5G RAN (215) and the UE (205) establish one or more data radio bearers (DRBs), and each DRB is associated with one or more QoS rules (e.g., for transmitting traffic that matches these QoS rules). Each DRB carries one or more QoS flows for a child PDU session (e.g., a first child PDU session (225)) through the 3GPP access network. Each QoS flow is associated with a QoS profile transmitted to the 5G RAN (215).
[0103] Next, the 5G RAN (215) sends an acknowledgment message to the AMF (145) (see operation (548)), and the AMF (145) sends an SM request message containing N2 information to the SMF (146) (see operation (550)). Then, the SMF (146) sends a session modification request to the first UPF (141) (see operation (552)) and receives an acknowledgment message in response (see operation (554)). The SMF (146) procedure sends the SM request acknowledgment message to the AMF (145), and the network procedure (600) terminates.
[0104] Note that DRBs established through a 3GPP access network (e.g., 5G RAN (215)) serve the same purpose as child IPsec SAs established through a non-3GPP access network, that is, they all provide multiple communication bearers with different QoS characteristics. Although FIGS. 6a and 6b illustrate the sequential establishment of child PDU sessions, in other embodiments, two child PDU sessions are established in parallel. Also note that since a single PDU session identity is shared by child PDU sessions, whenever the UE (205) or the network wants to perform an action on a child PDU session (e.g., changing the QoS rules of child PDU session #2), both the PDU session identity and the corresponding access network type must be provided to identify the appropriate child PDU session.
[0105] FIG. 7 illustrates a network procedure (700) for establishing a multiple access data connection according to embodiments of the present disclosure. The network procedure (700) is a network initiation procedure for establishing a multiple access data connection from a single request to establish a data connection. The network procedure involves a UE (205), a 5G RAN (215), an N3IWF (135), an AMF (145), an SMF (146), a first UPF (141), a second UPF (142), an anchor UPF (143), and a PCF (148). Here, the UE (205) is simultaneously connected to a mobile communication network through a 3GPP access network (here, 5G RAN (215)) and a non-3GPP access network (e.g., a WLAN (220)).
[0106] A network procedure (700) is initiated, and the UE (205) requests a normal (i.e., single access network) PDU session (see operation (702)). In the embodiments of FIG. 7, the NAS message is transmitted over the 5G RAN (215) (e.g., a 3GPP access network), but in other embodiments, the NAS message may be transmitted over a non-3GPP access network. The NAS message contains a single PDU session identity but does not contain any indication that the UE (205) wishes to establish a multi-access PDU session. The NAS message transmitted by the UE (205) may also contain other information, such as the requested DNN (data network name), the requested slice type, etc.
[0107] Next, the AMF (145) selects the SMF (146) and sends an SM request to the SMF (146) containing new multiple access parameters to indicate to the SMF (146) that the UE (205) is connected to both the 3GPP access network and the non-3GPP access network (704). The SM request includes a "PDU session establishment request" received from the UE (205). The SM request additionally includes an access network type parameter. Here, this parameter has a value "Access Network Type = 3GPP" to indicate to the SMF (146) that the PDU session establishment request was received through the 3GPP access network (e.g., 5G RAN (215)). If the PDU session establishment request is received through the non-3GPP access network, the value "Access Network Type = Non-3GPP" will be used.
[0108] Based on multiple access parameters and local information or policies, the SMF (146) decides to establish an MA-PDU session instead of a single access network PDU session requested by the UE (205) (see operation (706)). This decision may be made when the SMF (146) wants to offload, for example, part of the data traffic of the requested PDU session to a non-3GPP access network. For example, when the UE (205) requests in operation (702) to establish a PDU session to the Internet DNN (data network name) through the 3GPP access network, the SMF (146) may decide to establish an MA-PDU session to the Internet DNN so that some Internet traffic can be offloaded to a non-3GPP access network.
[0109] Before making this decision, the SMF (146) may interact with the UDM (149) to determine whether to allow the establishment of an MA-PDU session to the DNN where the UE (205) is requested to join. Additionally, the SMF (146) may decide to establish an MA-PDU session based on information retrieved from the PCF (148) in operation (708). In this case, the decision to establish an MA-PDU session (e.g., operation (706)) is made after operation (708).
[0110] As discussed, the SMF (146) can interact with the PCF (148) (e.g., establish a new PDU-CAN session) and retrieve multi-access routing rules to be applied in the UE (205) and anchor UPF (143) to determine how to route uplink and downlink traffic across two child PDU sessions, respectively (see operation (708)). The SMF (146) can also retrieve multi-access QoS rules from the PCF, namely QoS rules to be applied through the 3GPP access network and QoS rules to be applied through the non-3GPP access network.
[0111] Next, the SMF (146) begins establishing child PDU session #2 over the non-3GPP access network as described above in relation to operations (508-518). The AMF (145) transmits the QoS profile(s) to be applied over the non-3GPP access network to the N3IWF (135), each of which is determined from the QoS rules to be applied over the non-3GPP access network provided by the PCF. Additionally, the N3IWF (135) receives the single PDU session ID provided by the UE (205) in step 1.
[0112] Next, the UE (205) and N3IWF (135) establish one or more child IPsec SAs (see Operation (722)). Based on the received PDU session IDs, the UE (205) determines that these child IPsec SAs are part of the PDU session requested in Operation (702). That is, the UE (205) determines that the network has decided to establish an MA-PDU session instead of the requested single access network PDU session. Subsequently, N3IWF (135) sends a PDU session request acknowledgment message to AMF (145) (see Operation (524)), and AMF (145) sends an SM request acknowledgment message to SMF (146) (see Operation (526)). SMF (146) also sends a session modification request to the second UPF (142) (see Operation (528)) and receives an acknowledgment message in response (see Operation (530)).
[0113] Network procedure (700) continues by establishing a user plane for a child PDU session over 3GPP (e.g., a first child PDU session (225)) using a 3GPP access network as illustrated in FIG. 6b and as described above in relation to FIG. 6b. In summary, the SMF (146) transmits an SM request acknowledgment message to the AMF (145) (e.g., operation (542)), the AMF (145) transmits a PDU session request containing a single PDU session ID to the 5G RAN (215) (operation (644)), and the UE (205) and the 5G RAN (215) establish DRBs (operation (646)).
[0114] While the drawings illustrate the sequential establishment of child PDU sessions, in other embodiments, two child PDU sessions are established in parallel. Also, note that since a single PDU session identity is shared by the child PDU sessions, whenever the UE (205) or the network wants to perform an action on a child PDU session (e.g., changing the QoS rules of child PDU session #2), both the PDU session identity and the corresponding access network type must be provided to identify the appropriate child PDU session.
[0115] FIG. 8 illustrates a UE model (800) according to embodiments of the present disclosure. The UE model (800) represents a UE (205) after a multiple access data connection (e.g., an MA-PDU session) has been established. As illustrated, the IP layer (201) generates an uplink data (UL data) packet that is transmitted to the virtual interface layer (203). As previously described, the virtual interface layer (203) is a layer that exposes a single interface to upper layers, such as a single IP interface, to the IP layer (201), when the MA-PDU session is of IP type. The virtual interface layer (203) applies multiple access routing rules (803) received during the establishment of the MA-PDU session and determines whether the UL data packet should be routed through a child PDU session via 3GPP access or through a child PDU session via non-3GPP access.
[0116] As illustrated in FIG. 8, each child PDU session has its own QoS rules (e.g., QoS rules for non-3GPP (805) and QoS rules for 3GPP (807)). A UL data packet routed to a child PDU session is first matched against a QoS rule and associated with the QoS flow identifier (QFI) of the matched QoS rule. Subsequently, based on the associated QFI, it is routed to a corresponding DRB (for a 3GPP child PDU session) or a corresponding child IPsec SA (for a non-3GPP PDU session).
[0117] FIG. 9 illustrates a method (900) for establishing a multiple access data connection according to embodiments of the present disclosure. In some embodiments, the method (900) is performed by a device such as an SMF (146) and / or a session management device (400). In certain embodiments, the 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.
[0118] The method (900) begins with the step (905) of receiving a first session management request through an access management function in a mobile communication network. Here, the first session management request includes a second session management request transmitted by a remote unit communicating with the mobile communication network through a first access network and a second access network. In one embodiment, the second session management request is transmitted through the second access network.
[0119] In some embodiments, the first session management request includes an indication to establish a multi-access data connection to a remote unit through both the first access network and the second access network. In one embodiment, the indication to establish a multi-access data connection to a remote unit through both the first access network and the second access network includes a first session identifier associated with the first access network and a second session identifier associated with the second access network. In another embodiment, the indication to establish a multi-access data connection to a remote unit through both the first access network and the second access network includes a first session identifier and a multi-access parameter.
[0120] In some embodiments, the second session management request is a request from a remote unit to establish a data connection through a single access network, and the first session management request includes an indication that the remote unit has simultaneous connections to both the first access network and the second access network. In these embodiments, the step of receiving the first session management request (905) may include the step of deciding to establish a multi-access data connection in response to receiving the first session management request. In certain embodiments, the second session management request includes a mode parameter, and the mode parameter includes a requested mode of operation for the multi-access data connection.
[0121] In certain embodiments, the step of receiving a first session management request (905) includes the step of querying a policy control function for at least one of the multiple access routing rules and multiple access QoS rules associated with the remote unit. Here, the multiple access QoS rules include QoS rules for a first access network and QoS rules for a second access network. The multiple access routing rules indicate how to route traffic of multiple access data access across the first access network and the second access network.
[0122] In certain embodiments, the first access network is an access network not defined by 3GPP (“non-3GPP access”), and the second access network is an access network defined by 3GPP (“3GPP access”). In these embodiments, the second session management request may be a packet data unit (“PDU”) session establishment request.
[0123] The method (900) includes the step (910) of transmitting a first request to an access management function to establish a first data path for multiple access data access through a first access network in response to a first session management request. In certain embodiments, the step (910) of transmitting a first request to an access management function to establish a first data path for multiple access data access includes the step of transmitting a third session management request without an embedded N1 session management container. Here, the third session management request indicates that the access management function transmits the first request to the first access network.
[0124] In some embodiments, the step (910) of transmitting the first request to an access management function includes the step of transmitting a session establishment request to a common user plane function that anchors the first and second data paths, and the session establishment request includes multiple access routing rules and an indication that the first and second data paths are for multiple access data access.
[0125] In one embodiment, the step (910) of transmitting a first request to an access management function includes the step of querying a data management function to determine whether the network subscription of a remote unit allows a multiple access connection in response to the reception of a first session management request, and the step of deciding to establish a multiple access data connection based on the network subscription of the remote unit. In another embodiment, the step (910) of transmitting a first request to an access management function includes the step of querying a policy control function for at least one of multiple access routing rules and multiple access QoS rules associated with the requested data connection in response to the reception of a first session management request, and the step of deciding to establish a multiple access data connection based on at least one of the multiple access routing rules and multiple access QoS rules received from the policy control function.
[0126] The method (900) includes the step (915) of transmitting a second request to an access management function to establish a second data path for a multi-access data access through a second access network in response to a first session management request. Here, both the first data path and the second data path are anchored in a common user plane network function in a mobile communication network. In certain embodiments, the step (915) of transmitting a second request to an access management function to establish a second data path for a multi-access data access includes the step of transmitting a response to the first session management request, wherein the response includes an embedded N1 session management container. In one embodiment, the embedded N1 session management container includes a PDU session establishment access message containing multi-access routing rules and multi-access quality of service ("QoS") rules associated with the multi-access data access. The method (900) terminates.
[0127] FIG. 10 illustrates a method (1000) for establishing a multiple access data connection according to embodiments of the present disclosure. In some embodiments, the method (1000) is performed by a device such as a remote unit (105), a UE (205), and / or a UE device (300). In certain embodiments, the method (1000) may be performed by a processor executing program code, such as a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, an FPGA, etc.
[0128] The method (1000) begins with the step (1005) of communicating with a mobile communication network through both a first access network and a second access network. The method (1000) includes the step (1010) of transmitting a request to establish a data connection. In some embodiments, the first access network is an access network not defined by 3GPP (“non-3GPP access”), and the second access network is an access network defined by 3GPP (“3GPP access”). In these embodiments, the request to establish a data connection may be a PDU session establishment request. In certain embodiments, the request to establish a data connection includes a mode parameter, and the mode parameter includes a requested mode of operation for a multi-access data connection.
[0129] In some embodiments, a request to establish a data connection includes an indication to establish a data connection through both the first and second access networks. In one embodiment, the indication to establish a data connection through both the first and second access networks includes a first session identifier associated with the first access network and a second session identifier associated with the second access network. In another embodiment, the indication to establish a data connection through both the first and second access networks includes a first session identifier and multiple access parameters, wherein the first session identifier is associated with both the first access network and the second access network.
[0130] In certain embodiments, the step (1010) of transmitting a request to establish a data connection includes transmitting through a second access network. In certain embodiments, the request to establish a data connection includes a session identifier associated with the second access network and does not include a session identifier associated with the first access network.
[0131] The method (1000) includes the step (1015) of receiving a first request to establish a first data bearer for data access through a first access network in response to a request. In certain embodiments, the first request to establish a first data bearer for data access through a first access network includes a session identifier associated with a second access network. In additional embodiments, the step (1015) of receiving the first request to establish a first data bearer may include the step of determining that the establishment of a multi-access data access through a first access network and a second access network has commenced, wherein the request to establish a data access through a second access network is determined based on the first request, for example, the session identifier associated with the second access network.
[0132] The method (1000) includes the step (1020) of receiving a second request to set up a second data bearer for data access through a second access network in response to the request. Here, both the first data bearer and the second data bearer are used to carry traffic for data access. The method (1000) terminates.
[0133] The embodiments may be implemented in other specific forms. The described embodiments are to be considered in all aspects merely for illustrative purposes and without limitation. Accordingly, the scope of the invention is defined by the appended claims rather than by the foregoing description. All variations made within the meaning and scope of equivalents to the claims shall be included within such scope.
Claims
Claim 1 delete Claim 2 delete Claim 3 delete Claim 4 delete Claim 5 delete Claim 6 delete Claim 7 delete Claim 8 delete Claim 9 delete Claim 10 delete Claim 11 delete Claim 12 delete Claim 13 As a user equipment (UE) for wireless communication, at least one memory; A user device comprising at least one processor coupled with at least one memory, wherein the at least one processor is configured to cause the UE to: transmit a first request to establish a data connection through a first access network, wherein the first request includes a first session identifier associated with the first access network and does not include an indication to establish the data connection through the first access network and the second access network; receive a second request to set up a first data bearer for the data connection through the second access network in response to the first request, wherein the second request includes the first session identifier; receive a third request to set up a second data bearer for the data connection through the first access network in response to the first request, wherein the third request includes the first session identifier; and determine that the first request to establish a data connection has initiated the establishment of a multi-access data connection through the first access network and the second access network, wherein the first data bearer and the second data bearer are intended to carry data traffic associated with the data connection. Claim 14 In paragraph 13, the second access network is a non-3GPP access network, the first access network is a 3GPP access network, and the first request is a packet data unit ("PDU") session establishment request user equipment. Claim 15 In paragraph 13, the first request includes a mode parameter, and the mode parameter is a user device indicating an operation mode for multiple access data access. Claim 16 A method performed by a user device (UE), comprising: transmitting a first request to establish a data connection through a first access network, wherein the first request includes a first session identifier associated with a second access network and does not include an indication to establish the data connection through the first access network and the second access network; receiving a second request to set up a first data bearer for the data connection through the second access network in response to the first request, wherein the second request includes the first session identifier; receiving a third request to set up a second data bearer for the data connection through the first access network in response to the first request, wherein the third request includes the first session identifier; and determining that the first request to establish a data connection through the first access network has initiated the establishment of a multi-access data connection through the first access network and the second access network, wherein the first data bearer and the second data bearer are intended to carry data traffic associated with the data connection. Claim 17 A method according to paragraph 16, wherein the second access network is a non-3GPP access network, the first access network is a 3GPP access network, and the first request is a packet data unit ("PDU") session request. Claim 18 In paragraph 16, the above-mentioned first request includes a mode parameter, and the mode parameter indicates an operation mode for multiple access data access. Claim 19 delete Claim 20 delete
