Method and apparatus for efficient handover of multiple access (MA) traffic between non-3GPP access paths regarding communication of path switching capability information between network device and UE device

Abstract

Methods and apparatus are described that support efficient handover of data paths corresponding to communication sessions between different non-3GPP access networks, such as networks including WiFi access points, using network core functions. The present invention describes a novel enrollment process that exchanges UE and AMF capability information at an early stage in the enrollment process. An initial registration request message from a UE over a 3GPP or N3GPP access network may, but does not need to indicate whether the UE supports path switching for MA PDU sessions between N3GPP access paths. A registration accept message sent to the UE identifies an access and mobility management function (AMF) selected to support a first UE communication session, and includes AMF path switch capability information indicative of a path switch support capability of the identified AMF, such that the UE is aware of path switches supported by the AMF.

Description

Technical Field

[0001] The present application relates to supporting communications using multiple networks, and more specifically, to exchanging capability information between UE and 5GC to support efficient switching of communication volume corresponding to a communication session between network access paths (e.g., between multiple non-3GPP (N3GPP) access paths such as access paths using WiFi access points of different networks). Background Art

[0002] The 5G system architecture is designed to support multiple connection networks, including wired or wireless access networks. 3GPP Rel-18 has a study item related to data path switching between two non-3GPP access paths.

[0003] A key issue is how to support the handover of traffic of a multiple access protocol data unit (MAPDU) session between two non-3GPP access paths. Specifically, a method and apparatus are needed to allow a UE to register with a 5GC and support handover of traffic from the UE from one non-3GPP access path to another non-3GPP access path.

[0004] Potential procedures related to supporting data path switching between two non-3GPP access paths are proposed in 3GPP TR 23.700-53 V0.2.0 (April 2022) clauses 6.7, 6.9 and 6.10.

[0005] The process discussed in clause 6.9 specifies how the data traffic of an MA PDU session will be switched between two non-3GPP access paths using the same PLMN. The process described in clause 6.9 of TR 23.700-53 uses the following principles to switch the data traffic of an MA PDU session between two non-3GPP access paths:

[0006] a. The UE registers with the 5GC via a non-3GPP access network (e.g., an untrusted non-3GPP access network) using existing procedures. Optionally, the UE may also register with the 5GC via a 3GPP access network (e.g., via NG-RAN).

[0007] b. Establish an MA PDU session using the existing procedures specified in 3GPP TS 23.502 V17.4.0 (March 2022) clause 4.22.2, and transmit data traffic over the path of the MA PDU session.

[0008] c. The UE discovers a new non-3GPP access network (e.g. a trusted non-3GPP access network) and registers to the 5GC through this access network with a new registration type = "non-3GPP path switch". This allows the AMF to temporarily maintain two registrations through the two non-3GPP accesses until the path switch is completed.

[0009] d. The UE initiates a path switch by sending an MA PDU session establishment request (using the same PDU session ID) via a new non-3GPP access network.

[0010] The PDU Session Establishment Request triggers the SMF to establish user plane resources for the MA PDU session over the new non-3GPP access network.

[0011] e. When establishing user plane resources for the MA PDU session over the new non-3GPP access network, the SMF triggers the AMF to de-register the UE from the old non-3GPP access network (e.g. an untrusted non-3GPP access network).

[0012] f. When the UE triggers the path switching procedure is based on the UE implementation.

[0013] Figure 1 include Figure 1A and Figure 1B combination. Figure 1 Yes Figure 1A The steps 100 and Figure 1B An illustration of step 101 is shown in FIG. Figure 1 Depicted are the steps of a path switching process that allows the data traffic of an MA PDU session to be switched from a non-3GPP access path using N3IWF to a non-3GPP access path using TNGF. The same steps can be used to switch the data traffic of an MA PDU session between any non-3GPP access paths (using N3IWF or TNGF). Diagram 100 includes a user equipment (UE) 102, a non-3GPP radio access network (NG-RAN) 104, an access and mobility management function (AMF) 106, a user data management (UDM) 108, a session management function (SMF) 110, a non-3GPP interworking function (N3IWF) 112, and a trusted network gateway function (TNGF) 114.

[0014] exist Figure 1 The procedure shown in the diagram 100 of includes the following steps: step 1, step 2, step 3, step 4, step 5, step 6, step 7, step 8 and step 9. Each step (step 1, step 2, step 3, step 4, step 5, step 6, step 7, step 8, step 9) includes one or more operations.

[0015] Step 1 will now be described. Optionally, the UE 102 performs an initial 5G registration via 3GPP access in the PLMN. The selected AMF 106 registers with the UDM 108 for 3GPP access and provides its GUAMI and RAT type = NR.

[0016] Step 2 will now be described. UE 102 selects N3IWF and performs initial 5G registration over untrusted non-3GPP access in the same PLMN. The same AMF as in the previous step is selected. AMF 106 registers with UDM 108 for non-3GPP access and provides its GUAMI and RAT type = virtual or WLAN. AMF 106 can indicate to UE 102 whether it supports registration for non-3GPP path switching.

[0017] Step 3 will now be described. As specified in TS 23.502 clause 4.22.2, the UE 102 requests a MA PDU session. User plane resources are established over a 3GPP access and over an untrusted non-3GPP access. Data traffic over the MA PDU session is exchanged between the UE and the UPF using both accesses.

[0018] Step 3 will now be described in more detail. The UE 102 initiates an MA PDU session establishment and sends an UL NAS transport message 3a to the AMF 106. The UE NAS transport message 3a includes PDU Session Id-X, S-NSSAI, DNN, Request Type=MA PDU Request, PDU Session Establishment Request(). The AMF 106 sends a Create Session Management (SM) Context Request message 3b to the SMF 110. The Create SM Context Request message 3b includes SUPI, PDU Session Id=X, S-NSSAI, DNN, MA Request Indication, AN Type=Non-3GPP, Additional AN Type=3GPP, RAT Type=Virtual, PDU Session Establishment Request(). The SMF 110 sends a UECM Registration Request message 5c to the UDM 108. The UECM Registration Request 5c includes PDU Session Id=X, DNN, SUPI, SMF UUID. Additional step 3d is implemented to complete the MA PDU session establishment and establish user plane resources over both accesses.

[0019] Step 4 will now be described. UE 102 detects a trusted non-3GPP access network that supports 5G connections to the same PLMN. UE 102 decides to switch the data traffic transmitted through the untrusted non-3GPP access of the MA PDU session to the detected trusted non-3GPP access network. To this end, UE 102 initiates 5G registration through the trusted non-3GPP access and sets the registration type to "non-3GPP path switch". The registration type indicates that registration through a trusted non-3GPP access is required to switch the data traffic of the MA PDU session from one non-3GPP access path to another non-3GPP access path. After registering UE 102 through the trusted non-3GPP access with the registration type "non-3GPP path switch", AMF 106 does not release the existing registration through the untrusted non-3GPP access. AMF 106 can start a timer and maintain two registrations through the non-3GPP access until the path switch is completed or until the timer expires. As shown below (see step 9), when the timer expires, the AMF 106 initiates de-registration through the TNGF 114.

[0020] Step 5 will now be described. The UE 102 initiates a non-3GPP path handover by requesting user plane resources via a trusted non-3GPP access. To request these user plane resources, the UE 102 sends a PDU Session Establishment Request in a UL NAS transmission 5a over the TNGF 114 containing a Request Type = MA PDU Request and the identity of an existing MA PDU Session.

[0021] AMF 106 sends an Update SM Context Request 5b to SMF 110, which contains a "Non-3GPP Path Switch Indication". This indication notifies SMF 110 that a PDU Session Establishment Request is sent to allow a path switch from an existing non-3GPP access to a new non-3GPP access for an MA PDU session. Since UE 102 is registered as having the type "Non-3GPP Path Switch" (see step 4), AMF 106 inserts the "Non-3GPP Path Switch Indication" in the Update SM Context Request 5b.

[0022] The SMF 110 initiates the establishment of user plane resources over the trusted non-3GPP access. An additional step 5c is performed to complete the establishment of user plane resources over the trusted non-3GPP access.

[0023] Step 6 including steps 6a and 6b will now be described. After establishing the user plane resources over the trusted non-3GPP access, the UE 102 switches all uplink MA PDU session traffic from the untrusted non-3GPP access to the trusted non-3GPP access in step 6a. Similarly, in step 6b, the UPF switches all downlink MA PDU session traffic from the untrusted non-3GPP access to the trusted non-3GPP access (for this purpose, the SMF 110 modifies the existing N4 connection).

[0024] Step 7 will now be described. The SMF 110 sends an SM context status notification message 7a to the AMF 106 to indicate that the non-3GPP path switch has been completed.

[0025] Step 8 will now be described. After receiving the SM context status notification message 7a, the AMF 106 updates the UDM 108 with RAT type = Trusted_WLAN for non-3GPP access. The AMF 106 initiates the deregistration procedure for untrusted non-3GPP access (see TS 23.502 Section 4.12.3). In addition, the AMF 106 stops the timer started in step 4. After this step, the UE 102 has only one 5G registration through non-3GPP access.

[0026] Step 9 will now be described. If the AMF timer started in step 4 expires, the AMF 106 deregisters the UE 102 through the trusted non-3GPP access. After this step, the UE 102 has only one 5G registration through the non-3GPP access.

[0027] The described path switch handling has the following impacts on the UE: i) it triggers the switch from one N3GPP path to another N3GPP path based on the UE implementation; and ii) it involves the use of a new registration type when performing the switch during the registration procedure over another non-3GPP path.

[0028] The described path switch processing has the following impact on the AMF: i) It requires the AMF to indicate to the SMF that a non-3GPP path switch is required for the MA PDU session.

[0029] The described path switching process has the following impact on SMF / UPF: it requires the SMF and UPF to implement traffic switching from untrusted N3GPP access to trusted N3GPP access or vice versa.

[0030] The described path switch process has the following impact on UDM: UDM is expected to be updated with new RAT type information only after a path switch is successfully performed (eg from Virtual / WLAN to Trusted_WLAN).

[0031] Although the various operations to be implemented by the AMF and / or SMF are known from the described process of supporting path switching, some AMFs and / or SMFs may not support the required functionality. It should be appreciated that if the AMF / SMF does not support non-3GPP path switching and the UE is not notified until the UE attempts to use this capability, a situation may be encountered where the UE needs to deregister from the first non-3GPP path before establishing a new non-3GPP path. Methods and / or apparatus are needed for efficiently communicating UE and / or network device capabilities and assigning UEs to devices that support the capabilities of the UE. For example, it is necessary to efficiently assign UEs that support path switching to AMFs and / or SMFs that support such capabilities to reduce the risk of inadvertently interrupting sessions due to lack of path switching support. Summary of the invention

[0032] In various embodiments, when the UE first performs a registration procedure using one of the non-3GPP accesses, the AMF provides whether it can support non-3GPP path switching. However, it should be recognized that the UE can first register using a 3GPP access. According to one feature, the AMF provides the UE with its ability to support non-3GPP path switching regardless of the access type on which it performs registration.

[0033] In various embodiments, when the UE performs a registration procedure with the AMF for the first time (e.g., using an initial type registration message), the UE indicates to the AMF whether it is capable of supporting non-3GPP path switching.

[0034] This is different from previous approaches where such information was not provided to the AMF as part of the initial registration. Therefore, unlike prior art approaches where the AMF was unaware of whether the UE was capable of supporting non-3GPP path switching at the time of registration, in various embodiments, such information is made available to the AMF as such information is incorporated into the initial registration message in accordance with a feature of the present invention. Making such UE capabilities known to the AMF allows selection of appropriate network functionality, such as redirection to another AMF if the AMF to which the UE is initially assigned / connected does not support the same level of path switching capabilities as the UE. Furthermore, by quickly making an appropriate SMF selection during MAPDU session establishment, the AMF to which the UE is assigned is able to quickly select an SMF that is able to support the capabilities of the UE. This avoids the risk of having to select a different SMF at a later time due to the selected SMF being unable to support all or some of the path switching capabilities of the UE to be served.

[0035] According to the present invention, the UE exchanges capabilities with the 5GC to implement an efficient solution for data path switching between two non-3GPP access paths.

[0036] It should be noted that capability exchange may also occur during registration with 3GPP access networks as defined in clause 4.2.2.2.2 of TS 23.502 and other non-3GPP access types (i.e. trusted non-3GPP access in clause 4.12a.2.2 of TS 23.502, wired non-3GPP access in clause 7.2.1 of TS 23.316 V17.2.0 (December 2021)).

[0037] The exchange of non-3GPP path switching capability information between the UE and 5GC during registration has the following benefits compared to methods that do not include such capability information exchange: i) it has the potential to reduce signaling in the network and on the device; and ii) it facilitates rapid selection of the appropriate network function (e.g. AMF, SMF).

[0038] Although discussed in 5G terms, it should be appreciated that the methods and apparatus may be used with other communication standards and systems supporting the same or similar functionality.

[0039]

[0013] Many variations of the methods and embodiments described above will be discussed in the detailed description that follows. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] Figure 1A is the first part of a diagram showing known procedures for implementing data traffic handover between two non-3GPP access paths.

[0041] Figure 1B is the second part of a diagram showing known procedures for implementing data traffic handover between two non-3GPP access paths.

[0042] Figure 1 include Figure 1A and Figure 1B combination.

[0043] Figure 2 is a diagram of an exemplary communication system in accordance with an exemplary embodiment.

[0044] Figure 3 is a diagram illustrating exemplary signaling and operation of an exemplary communication method.

[0045] Figure 4 is a diagram of an exemplary user equipment (UE) according to an exemplary embodiment.

[0046] Figure 5is a diagram of an exemplary access network device, such as a 3GPP NG-RAN gNB base station, an untrusted N3GPP access point, or a trusted N3GPP access point (TNAP), according to an exemplary embodiment.

[0047] Figure 6 is an illustration of an exemplary network interface device, such as a Non-3GPP Interworking Function (N3IWF) device, a Trusted Non-3GPP Gateway Function (TNGF) device, or another gateway device, according to an exemplary embodiment.

[0048] Figure 7 is an illustration of an exemplary access and mobility management function (AMF), such as an AMF server, according to an exemplary embodiment.

[0049] Figure 8 is an illustration of an exemplary system according to an exemplary embodiment, such as a server- or cloud-based processing system including an access and mobility management function (AMF), a session management function (SMF), a unified data management (UDM), a policy control function (PCF), and / or a user plane function (UPF) with ATSSS functionality, or a data network (DN) server that may be part of a PLMN or implement PLMN functionality.

[0050] Fig. 9A is a first part of a signaling diagram illustrating signals and operations of a registration method over an untrusted non-3GPP access according to an exemplary embodiment.

[0051] Fig. 9B is a second part of a signaling diagram illustrating signals and operations of a registration method over an untrusted non-3GPP access according to an exemplary embodiment.

[0052] Fig. 9 include Fig. 9A and Fig. 9B combination.

[0053] Fig.10 is an illustration of an exemplary assembly of components that may be included in a user equipment (UE) according to an exemplary embodiment.

[0054] Fig.11 is an illustration of an exemplary assembly of components that may be included in a network interface device according to an exemplary embodiment.

[0055] Fig.12 is an illustration of an exemplary assembly of components that may be included in an access and mobility management function (AMF) according to an exemplary embodiment.

[0056] Fig.13 is a flow chart of an exemplary method of operating a first UE device according to an exemplary embodiment.

[0057] Fig.14 is a flow chart of another exemplary method of operating a first UE device according to an exemplary embodiment. DETAILED DESCRIPTION

[0058] Figure 2 2 is a diagram of an exemplary communication system 200 according to an exemplary embodiment. As shown, the exemplary communication system 200 includes the following items coupled together: a UE 202 with access traffic steering, switching and splitting (ATSSS) functionality, a third generation partnership project (3GPP) radio access network (RAN) 204, a first non-3GPP (N3GPP) radio access network as N3GPP radio access network #A 206, a second N3GPP radio access network as N3GPP radio access network #B ​​208, a first access and mobility management function (AMF) as AMF 1 221, a second AMF as AMF 2 222, a unified data management (UDM) 223, a first session management function (SMF) as SMF 1 225, a second SMF as SMF 2 224, a PCF 226, a user plane function (UPF) 228 with ASSS functionality, and a data network (DN) 230. AMF 1 221 does not include the capability to support path switching of MA PDU sessions between N3GPP access paths. AMF 2 222 includes the capability to support path switching of MA PDU sessions between N3GPP access paths. SMF 1 225 does not include the capability to support path switching of MA PDU sessions between N3GPP access paths. SMF 2 224 includes the capability to support path switching of MA PDU sessions between N3GPP access paths.

[0059] The 3GPP radio access network 204 includes, for example, the NG-RAN 110 including a gNB base station. The N3GPP radio access network #A 206 includes an access point (AP) 212, such as an untrusted WiFi AP, coupled to a non-3GPP interworking function (N3IWF) 214. The N3GPP radio access network #B ​​208 includes a trusted non-3GPP access network (TNAN) 216, which includes a trusted non-3GPP access point (TNAP) 218 ​​and a trusted non-3GPP gateway function (TNGF) 220.

[0060] The dashed arrow 290A indicates that a message, such as an IKE_Auth request message including an initial registration request message, is sent from the UE 202 to the N3GPP radio access network #A 206, including an indicator indicating that the UE 202 supports path switching of MAPDU sessions between N3GPP access paths and requests to discover an AMF that supports path switching of MA PDU sessions between N3GPP access paths. The dashed arrow 290B indicates that an initial registration request message is sent from the N3IWF 214 to the AMF 1 221 as the AMF selected by the N3IWF 214, such as based on access network (AN) parameters and local rules. The message includes an indicator indicating that the UE 202 supports path switching of MA PDU sessions between N3GPP access paths and requests to discover an AMF that supports path switching of MAPDU sessions between N3GPP access paths. In this case, AMF 1 221 receives the initial registration request message and recovers the conveyed information indicating that UE 221 requests an AMF that supports path switching of MA PDU sessions between N3GPP access paths, and since AMF 1 221 does not satisfy the request, AMF 1 221 searches for another AMF that will satisfy the request. AMF 1 221 discovers AMF 2 222 that supports path switching of MA PDU sessions between N3GPP access paths, and AMF 1 221 sends (e.g., forwards) the received initial registration request as an initial registration request message 290C to AMF 2 222, and AMF 2 222 receives the initial registration request from UE 202. Since AMF 2 222 can satisfy the request, AMF 2 222 registers with UDM 223 and sends a registration accept message to UE 202 through N3GPP access network 206. The registration accept message includes a globally unique AMF identifier (GUAMI) corresponding to AMF 2 222 and an indicator indicating that AMF 2 222 supports path switching of MA PDU sessions between N3GPP access paths. UE 202 uses the received GUAMI corresponding to AMF 2222 for further communications, such as subsequent registration requests for other access networks.

[0061] UE 202 is coupled to 3GPP radio access network 204 via wireless path #3 232. UE 202 is coupled to N3GPP radio access network #A 206 via wireless path #1 238. UE 202 is coupled to N3GPP radio access network #B ​​208 via wireless path #2 242. N3 tunnel 234 couples 3GPP radio access network 204 to UPF 228. N3 tunnel 240 couples N3GPP radio access network #A 206 to UPF 228. N3 tunnel 244 couples N3GPP radio access network #B ​​208 to UPF 228.

[0062] 224. N1 connection 236 couples UE 202 to AMF 222 via 3GPP radio access network 204. N1 connection 239 couples UE 202 to AMF 222 via N3GPP radio access network #A 206. N1 connection 246 couples UE 202 to AMF 222 via N3GPP radio access network #B ​​208. N11 connection 248 couples AMF 222 to SMF 224. N7 connection 252 couples SMF 224 to PCF 226. N10 connection 249 couples UDM 223 to SMF 224. N4 connection 250 couples SMF 224 to UPF 228. N6 connection 254 couples UPF 228 to data network 230.

[0063] The 3GPP radio access network 204 , AMF 1 221 , AMF 2 222 , UDM 223 , SMF 1 225 , SMF 2 224 , PCF 226 , UPF 228 , and data network 230 are part of the same public land mobile network (PLMN) 256 .

[0064] According to the exemplary embodiment, large arrow 260 indicates that while maintaining an ongoing multiple access (MA) communication session including path #3 (corresponding to 3GPP access network 204), the access path for communication traffic data can and sometimes is switched between path #1 238 (corresponding to the first N3GPP access network) and path #2 242 (corresponding to the second N3GPP access network).

[0065] Figure 3300 is a diagram illustrating exemplary operations of exemplary elements, exemplary signaling, and exemplary communication methods of an exemplary communication system according to an exemplary embodiment. Diagram 300 includes UE 202, a 3GPP or N3GPP access network 301 including an access network device or a collection of access network devices, a network interface device 303, AMF 1 221, AMF 2 222, UDM 223, SMF 1 225, and SMF 2 224. UE 202, AMF 1 221, AMF 2 222, UDM 223, SMF 1 225, and SMF 2 224 are Figure 2 The 3GPP or N3GPP access network 301 is, for example, one of the following: Figure 2 The 3GPP access network 204 of the system 200, Figure 2 The untrusted N3GPP access network 206 of the system 200, or Figure 2 The trusted N3GPP access network 208 of the system 200. The network interface device 303 is, for example, one of the following: Figure 2 NG-RAN gNB base station 210, N3IWF 214 or TNGP 220 of system 200. NG-RAN gNB base station 210 is part of 3GPP access network 204. N3IWF 214 is coupled to AP 212 of N3GPP access network 206. TNGF 216 is part of N3GPP access network 208. In this example, UE 202 is a UE with ASSS function that supports path switching of MA PDU sessions between N3GPP access paths. AMF2 222 and SMF 2 224 support path switching of MA PDU sessions between N3GPP access paths. AMF 1 221 and SMF 1 225 do not support path switching of MA PDU sessions between N3GPP access paths.

[0066] In step 302, UE 202 generates and sends a message 304 including an initial registration request message to a network interface device 303. In an exemplary embodiment, message 304 is an IKE_Authorization request message including AN parameters and an initial registration request message; and the network interface device 303 is N3IWF 214. The initial registration request message includes path switching capability information indicating whether UE 202 supports path switching of MA PDU sessions between N3GPP access paths. In this example, the initial registration request message includes an indicator indicating that UE 202 supports path switching of MA PDU sessions between N3GPP access paths and requests discovery of an AMF that supports path switching of MA PDU sessions between N3GPP access paths. In various embodiments, the initial registration message includes registration type=initial.

[0067] In step 308, the network interface device 303 receives the message 304. In step 310, the network interface device 303 selects AMF 1 221 as the host AMF, for example based on the received access network parameters and local policies. In various embodiments, the network interface device 303 does not consider the path switching capability of the UE 202 when making the initial AMF selection of step 310, for example because the network interface device 303 cannot access the path switching information included in the initial registration request message, but the path switching information in the initial registration request message can be accessed by the AMF.

[0068] In step 312, the network interface device 303 sends a message 314 to the AMF 1 221. The message 314 is an initial registration message including an indicator indicating that the UE supports path switching of MA PDU sessions between N3GPP access paths and requests discovery of an AMF supporting path switching capability.

[0069] In various embodiments, the initial registration request message is included in the message 304 as part of the payload of the message 304, and the content of the initial registration message is not fully accessible to the network interface device 303, but is accessible to one or more AMFs for which the initial registration message is communicated.

[0070] In step 316, AMF 1 receives message 314 and recovers the communicated information. In step 318, AMF 1 221 determines whether the host AMF (i.e., AMF 1 221) can support the path switching capability level supported by UE 202 as indicated by the path switching capability information included in the initial registration message. In step 318, AMF 1 221 determines that AMF 1 221 is not suitable for supporting UE 202 because the path switching information communicated in the initial registration message indicates that UE 202 supports path switching for MA PDU sessions for N3GPP access paths, UE 202 is requesting an AMF that supports path switching, and AMF1 221 does not have the capability. In step 320, AMF 1 221 performs a discovery search for (multiple) other AMFs that support path switching of MA PDU sessions between N3GPP access paths and are suitable for UE 202, identifies one or more candidate AMFs that support path switching of MA PDU sessions for N3GPP access paths, and selects AMF 2 222 as one of the candidates supporting path switching. In step 322, AMF 1 221 sends (e.g., forwards) the received initial registration request message including the path switching indicator to AMF 2 222 as message 324.

[0071] In step 328, AMF 2 222 receives the initial registration request message 324, recovers the information conveyed, and determines that AMF 2 222 will satisfy UE 202 because AMF2 222 supports path switching. In step 328, AMF 2 222 generates and sends a registration message 330 to UDM 223. In step 332, UDM 223 receives the registration message 332 and implements the registration operation. In step 334, UDM 223 stores registration information 334 corresponding to UE 202 and AMF 222. In step 336, AMF 2222 generates and sends a registration accept message 338 to the network interface device 303. The registration accept message 338 includes a globally unique AMF identifier (GUAMI) corresponding to AMF2 222 and an indicator indicating that AMF 2 222 supports path switching of MA PDU sessions between N3GPP access paths.

[0072] In step 344, the network interface device 303 receives the registration accept message 338. In step 346, the network interface device 303 generates and sends a registration accept message 348 to the UE 202. The message 348 includes the GUAMI 340 and an indicator 342 indicating that the AMF 2 supports path switching. In step 354, the UE 202 receives the registration accept message 348 and recovers the communicated information. In step 356, the UE 202 stores the recovered information including the GUAMI indicating that the AMF 2 222 is the AMF supporting the UE 202 and that the AMF 2 222 supports path switching of the MA PDU session between the N3GPP access paths.

[0073] In step 358, UE 202 generates and sends a message 360 ​​to initiate an MA PDU session to AMF 2 222. In step 362, AMF 2 222 receives the message 360. In step 364, AMF 2 222 selects an SMF that supports path switching capability from a plurality of alternative SMFs, some of which do not support path switching (e.g., SMF 1 225) and some of which support path switching (e.g., SMF 2 224), such as SMF 2 224. In step 366, AMF 2 222 generates and sends a create SM context request message 368 to SMF 2 224 to create a context for UE 202 at SMF 2 224. In step 370 , SMF 224 receives Create SM Context Request 368 , and in response, in step 372 , SMF 2 224 generates and sends UE CM Registration Request 374 to UDM 223 .

[0074] Figure 4 FIG. 4 is a diagram of an exemplary user equipment (UE) 400 having ATSSS functionality according to an exemplary embodiment. UE 400 is, for example, Figure 2 UE 202 of system 200. UE 400 includes a processor 402 (e.g., CPU), a wireless interface 404, a network interface 406, an I / O interface 408, a GPS receiver 410, a memory 412, and a hardware component assembly 414 (e.g., a circuit assembly) coupled together via a bus 416. UE 400 also includes a plurality of I / O devices (microphone 456, speaker 458, camera 460, display 462 (e.g., touch screen display), switch 464, keypad 466, mouse 468) coupled to I / O interface 408, and the I / O interface 408 couples the I / O devices to bus 416 and other components within UE 400.

[0075] The wireless interface 404 includes a 3GPP wireless interface 422 (e.g., a gNB wireless interface), a first WiFi interface 436, and a second WiFi interface 450. The 3GPP wireless interface 422 includes a wireless receiver 424 coupled to one or more receiving antennas (428...430), through which the UE 400 receives cellular signals, such as from a gNB base station. The 3GPP wireless interface 422 also includes a wireless transmitter 426 coupled to one or more transmitting antennas (432...434), through which the UE 400 transmits cellular signals, such as to a gNB base station. The first WiFi interface 436 includes a wireless receiver 438 coupled to one or more receiving antennas (442...444), through which the UE 400 receives WiFi signals, such as from a first N3GPP access point. The first WiFi interface 436 also includes a wireless transmitter 440 coupled to one or more transmitting antennas (446...448), through which the UE 400 transmits WiFi signals, such as to a first N3GPP AP. The second WiFi interface 450 includes a wireless receiver 452 coupled to one or more receiving antennas (456 ... 458), through which the UE 400 receives, for example, WiFi signals from a second N3GPP access point. The second WiFi interface 450 also includes a wireless transmitter 454 coupled to one or more transmitting antennas (460 ... 462), through which the UE 400 transmits WiFi signals, for example, to a second N3GPP AP. In some embodiments, the same one or more antennas are used for transmission and reception, for example in a time division duplex embodiment. In some embodiments, the same WiFi interface is used to communicate with multiple WiFi APs. In some embodiments, different WiFi interfaces correspond to different frequency bands.

[0076] The network interface 406 (e.g., a wired or optical interface) includes a receiver 418 and a transmitter 420 coupled to a connector 422, which can and sometimes couples the UE 400 to other network nodes and / or the Internet via a wired or optical connection, such as when the UE 400 is in a location where a wired or optical connection is available.

[0077] The memory 412 includes, for example, control routines 470 for controlling the UE 400 to implement basic functions, such as memory access operations, I / O device control, receiver control, etc., as well as component assemblies 472 (e.g., software component assemblies) and data / information 474. The component assemblies include, for example, routines, subroutines, software modules and / or applications, which, when executed by the processor 402, control the UE 400 to implement various steps of the exemplary method implemented by the UE 202, such as Figure 3The data / information 474 includes a generated message 476, which includes an initial registration request message, including an indicator indicating that the UE supports path switching of MA PDU sessions between N3GPP access paths, and a discovery request for an AMF that supports path switching capabilities of MAPDU sessions between N3GPP access paths; a received registration accept message 482, including the GUAMI 484 of the AMF and an indicator 486 indicating that the AMF supports path switching capabilities of MA PDU sessions between N3GPP access paths; and a generated message 488 to initiate MA PDU session establishment, which will be sent to the AMF identified by the GUAMI in the received registration accept message.

[0078] Figure 5 2 is a diagram of an exemplary access network (AN) device 500, such as a 3GPP NG-RANgNB base station, an untrusted N3GPP access point (e.g., AP 212), or a trusted N3GPP AP (TNAP) 118, according to an exemplary embodiment. In some embodiments, the AN device 500 is Figure 3 The exemplary access network device 500 includes a processor 502 (e.g., a CPU), a wireless interface 504 (e.g., a cellular or WiFi interface), a network interface 506 (e.g., a wired or optical interface), a hardware component assembly 508 (e.g., a circuit assembly), and a memory 510 coupled together via a bus 511, and various units exchange data and information via the bus 511.

[0079] The wireless interface 504 includes a wireless receiver 512 coupled to a plurality of receiving antennas (520 ... 522) and a wireless transmitter 514 coupled to one or more transmitting antennas (524 ... 526), ​​through which the access network device 500 receives wireless signals from the UE, and through which the access network device 500 transmits wireless signals to the UE. In some embodiments, the receiver 512 and the transmitter 514 are part of a transceiver 505 (e.g., a cellular or WiFi transceiver). In some embodiments, one or more antennas are used for reception and transmission, for example in a TDD embodiment.

[0080] The network interface 506 includes a receiver 516 and a transmitter 518 coupled to a connector 519, which couples the access network device 500 to other network nodes (e.g., other APs), base stations, various servers or devices including AMF, SMF, UDM, PCF and / or UPF with ATSSS function, data network (DN) servers, various core network devices, routers, etc. and / or the Internet. The memory 510 includes a control routine 528 and a component 530 assembly (e.g., a software component assembly) and data / information 532.

[0081] The data / information 532 includes: a message 534 received from the UE, which includes an initial registration request message, including an indicator indicating that the UE supports path switching of MA PDU sessions between N3GPP access paths, and a discovery request for AMFs that support path switching capabilities; information 536 indicating the AMF selected as the host AMF based on access network parameters and local policies; an initial registration request message 538 to be sent to the selected AMF, including an indicator indicating that the UE supports path switching of MA PDU sessions between N3GPP access paths, and a discovery request for AMFs that support path switching capabilities; a registration acceptance message 540 received from the AMF that meets the UE's requirements and to be sent to the UE. The registration acceptance message 540 includes a globally unique AMF identifier (GUAMI) 542 and an indicator 544 indicating that the AMF identified by the identifier supports path switching. The data / information 532 also includes a generated registration acceptance message 546 to be sent to the UE, including the GUAMI 542 and the indicator information 544.

[0082] Figure 6 6 is a diagram of an exemplary network interface device 600, such as a non-3GPP interworking function (N3IWF) device, a trusted non-3GPP gateway function (TNGF) device, or another gateway device, according to an exemplary embodiment. Figure 2 The N3IWF device 214 of the system 200, Figure 2 The TNGF device 120 of the system 200, or Figure 3 The network interface device 303.

[0083] The exemplary network interface device 600 includes a processor 602 (e.g., a CPU), a first network interface 604 (e.g., a wired or optical interface), a second network interface 606 (e.g., a wired or optical interface), a hardware component assembly 608 (e.g., a circuit assembly), and a memory 610 coupled together via a bus 611, and various units exchange data and information via the bus 611.

[0084] The first network interface 604 includes a receiver 612 and a transmitter 614 coupled to a connector 615 that couples the network interface device 600 to an AP, a network node, and / or the Internet.

[0085] The second network interface 606 includes a receiver 616 and a transmitter 618 coupled to a connector 619, wherein the connector 619 couples the network interface device 600 to a core network device (e.g., AMF, SMF, UDM, PCF, and / or UPF with ATSSS function), a data network (DN) server, various core network devices, routers, etc. and / or the Internet. The memory 610 includes a control routine 628 and a component assembly 630 (e.g., a software component assembly) and data / information 632.

[0086] The data / information 632 includes: a message 634 received from the UE including an initial registration request message, including an indicator indicating that the UE supports path switching for MA PDU sessions between N3GPP access paths, and a discovery request for AMFs that support path switching capabilities; information 636 indicating the AMF selected as the host AMF, for example based on access network parameters and local policies; an initial registration request message 638 to be sent to the selected AMF, including an indicator indicating that the UE supports path switching for MA PDU sessions between N3GPP access paths, and a discovery request for AMFs that support path switching capabilities; a registration acceptance message 640 received from the AMF that meets the UE's requirements and to be sent to the UE. The registration acceptance message 640 includes a globally unique AMF identifier (GUAMI) 642 and an indicator 644 indicating that the AMF identified by the identifier supports path switching. The data / information 632 also includes a generated registration acceptance message 646 to be sent to the UE, including the GUAMI 642 and the path switching indicator information 644.

[0087] Figure 7 7 is a diagram of an exemplary access and mobility management function (AMF) 700 (e.g., an AMF server) according to an exemplary embodiment. The AMF 700 is, for example, Figure 2 or Figure 3 AMF 1 221 or AMF 2 222 of system 200.

[0088] AMF 700 includes a processor 702 (eg, a CPU), a network interface 704 (eg, a wired or optical interface), a hardware component assembly 708 (eg, a circuit assembly), and a memory 710 coupled together via a bus 711 , through which various units exchange data and information.

[0089] The network interface 704 includes a receiver 712 and a transmitter 714 coupled to a connector 716, wherein the connector 716 couples the AMF 700 to a base station (such as a 3GPP gNB), an N3IWF device, a TNGF device, a network node, a core network device (such as other AMFs, SMFs, UDMs, PCFs and / or UPFs with ATSSS functionality), a data network (DN) server, various other core network devices, routers, etc. and / or the Internet.

[0090] The memory 708 includes a control routine 718, a component assembly 720 (e.g., a software component assembly), and data / information 722. The data / information 722 includes: information 724 indicating whether the AMF 700 supports path switching for MA PDU sessions between N3GPP access paths; and an initial registration request message received from a UE, including information indicating whether the UE supports path switching for MA PDU sessions between N3GPP access paths. In some embodiments, such as in embodiments where the AMF 700 supports path switching, the data information 722 includes a generated registration accept message 728, including a GUAMI 730 identifying the AMF 700 and an indicator 732 indicating that the AMF 700 supports path switching for MA PDU sessions between N3GPP access paths. In some embodiments, such as in embodiments where the AMF 700 does not support path switching, the data information 722 includes information 734 identifying a selected AMF that supports path switching, and a generated message 736 forwarding the received initial registration request message to the identified AMF.

[0091] Figure 8 8 is a diagram of an exemplary system 800 according to an exemplary embodiment, such as a server or cloud network including interfaces and one or more processors providing AMF, SMF, UDM, PCF and / or UPF with ASSS functions, or a data network (DN) server. The exemplary system 800 includes a processor 802 (e.g., a CPU), a network interface 804 (e.g., a wired or optical interface), a hardware component assembly 806 (e.g., a circuit assembly), and a memory 808 coupled together by a bus 810, and the various units exchange data and information through the bus 810.

[0092] The network interface 804 includes a receiver 812 and a transmitter 814 coupled to a connector 816, which couples the server 800 to other network nodes (e.g., other servers), core network devices, routers, etc. and / or the Internet. The memory 808 includes a control routine 818 and a component assembly 820 (e.g., a software component assembly) and data / information 822.

[0093] Various aspects and / or features of some embodiments of the invention are described below.

[0094] Now refer to Fig. 9 Registration procedures for untrusted non-3GPP access are discussed. Fig. 9 include Fig. 9A and Fig. 9B combination. Fig. 9A The signaling process 900 shown in Fig. 9B The signaling flow 901 shown in the combination shows a novel registration process through an untrusted non-3GPP access, in which UE and AMF capability information are exchanged at an early stage in the registration process. The figure specifically shows the steps performed between the UE and the N3IWF.

[0095] Fig. 9 Diagram 900 shows an exemplary registration via an untrusted non-3GPP access. Diagram 900 shows an exemplary UE 951, an exemplary untrusted non-3GPP access network 952, an exemplary non-3GPP interworking function (N3IWF) 952, an exemplary access and mobility management function (AMF) 954, and an exemplary authentication server function (AUSF) 955. Diagram 900 shows exemplary steps 901, 902, 903, 904, 905, 906, 907, 908, 909, 910, 911, 912, and 913, each of which corresponds to one or more operations.

[0096] Step 901, UE 951 connects to untrusted non-3GPP access network 952 through any appropriate authentication procedure and is assigned an IP address. For example, non-3GPP authentication methods may be used, such as no authentication (in the case of free WLAN), EAP with pre-shared keys, username / password, etc. As described in clause 6.3.6 of 3GPP TS 23.501 V17.4.0 (March 2022), when UE 951 decides to attach to the 5GC network, UE 951 selects N3IWF953 in the 5G PLMN.

[0097] Step 902: According to IETF RFC 7296 (ISSN: 2070-1721, October 2014), by initiating IKE initial exchange 902a, UE 951 continues to establish an IPsec security association (SA) with the selected N3IWF 953. After step 902, all subsequent IKE messages are encrypted and integrity protected by the IKE SA established in this step.

[0098] Step 903, UE 951 will initiate an IKE_AUTH exchange by sending an IKE_AUTH request message 903a. The AUTH payload is not included in the IKE_AUTH request message 903a, indicating that the IKE_AUTH exchange will use EAP signaling (in this case, EAP-5G signaling). As specified in IETF RFC 4555 (June 2006), if UE 951 supports MOBIKE, a Notification payload will be included in the IKE_AUTH request 903a to indicate support for MOBIKE. In addition, as specified in 3GPPTS 33.501 V17.5.0 (March 2022), if UE 951 specifies a N3IWF root certificate, a CERTREQ payload will be included in the IKE_AUTH request message 903a to request the N3IWF's certificate.

[0099] Step 904, N3IWF 953 responds with an IKE_AUTH response message 904a including an EAP request / 5G start packet. The EAP request / 5G start packet notifies UE 951 to initiate an EAP-5G session, i.e., to start a NAS message encapsulated in an EAP-5G packet. If N3IWF 953 receives a CERTREQ payload from UE 951, N3IWF 953 will include a CERT payload in the IKE_AUTH response message 904a containing the certificate of N3IWF. How UE 951 uses the certificate of N3IWF is specified in TS 33.501.

[0100] Step 905, UE 951 will send an IKE_AUTH request 905a including an EAP response / 5G-NAS packet, which contains access network parameters (AN parameters) and a registration request message. The AN parameters contain information used by N3IWF 953 to select the AMF in the 5G core network. This information includes, for example, GUAMI, the selected PLMN ID (or PLMN ID and NID, see clause 5.30 of TS 23.501), the requested NSSAI and the establishment reason. The establishment reason provides the reason for requesting a signaling connection with the 5GC. Whether and how UE 951 includes the requested NSSAI as part of the AN parameters depends on the value of the access layer connection establishment NSSAI including mode parameter as specified in clause 5.15.9 of TS23.501.

[0101] Note 1: Since the UE 951 includes its identity in the first IKE_AUTH, the N3IWF 953 does not send an EAP Identity Request. This is consistent with RFC 7296 clause 3.16.

[0102] Step 906, as specified in clause 6.3.5 of TS 23.501, N3IWF 953 will select (906a) AMF based on the received AN parameters and local policy. In the registration request message in the previous step 905, as indicated by box 905b, UE 951 indicates that it supports "non-3GPP path switching".

[0103] The "Non-3GPP Path Switching" indication indicates that the UE 951 is capable of switching the traffic of the MAPDU session between two non-3GPP access paths and requests to discover an AMF that supports this capability.

[0104] The registration request indicates a request for registration through a non-3GPP access to switch data traffic of an MA PDU session from one non-3GPP access path to another non-3GPP access path.

[0105] The N3IWF 953 then forwards the registration request received from the UE 951 to the selected AMF, such as AMF 954, within the N2 message 906b.

[0106] If the host AMF does not support the "non-3GPP path switching" capability, other AMFs may be discovered using the NF discovery and selection procedure (as indicated by block 906c).

[0107] The message contains N2 parameters including the selected PLMN ID and establishment reason.

[0108] Step 907, the selected AMF 954 may decide to request SUCI by sending a NAS Identity Request message to the UE 951 (see N2 message 907a conveying the Identity Request message from the AMF 954 to the N3IWF 953, and IKE_Auth Request message 907b conveying the Identity Request message from the N3IWF 953 to the UE 951). This NAS message and all subsequent NAS messages are encapsulated in an EAP / 5G-NAS packet and sent to the UE 951.

[0109] Step 908, AMF 954 may decide to authenticate UE 951 by invoking AUSF. In this case, AMF 954 will select AUSF 955 based on the SUPI or SUCI sent from AMF 954 to AUSF 955 in AAA Key Request message 908a as specified in clause 6.3.4 of TS 23.501.

[0110] The AUSF 955 performs authentication of the UE 951 as specified in TS 33.501

[15] . The AUSF 955 selects the UDM as described in clause 6.3.8 of TS 23.501 [2] and obtains authorization data from the UDM. The authentication packet is encapsulated within a NAS authentication message, and the NAS authentication message is encapsulated within an EAP / 5G-NAS packet. Messages 908b, 908c, 908d, 908e, 908f, and 908h are part of the authentication process. After successful authentication:

[0111] The AUSF 955 will send an anchor key (SEAF key) to the AMF 954 in the AAA Key Response message 908h, which is used by the AMF 954 to derive NAS security keys and security keys (N3IWF keys) for the N3IWF 953. The UE 951 also derives the anchor key (SEAF key), and derives NAS security keys and security keys (N3IWF keys) for the N3IWF from it. The N3IWF key is used by the UE 951 and the N3IWF to establish an IPsec security association (in step 911).

[0112] If the AMF 954 provides the SUCI in the AAA Key Request message 908a to the AUSF 955, the AUSF 955 also includes the SUPI in the AAA Key Response message 908h.

[0113] NOTE 2: As specified in TS 33.501, EAP-AKA' or 5G-AKA is allowed for UE authentication over non-3GPP access. Figure 4 .12.2.2-1 only shows the authentication process using EAP-AKA'. As specified in Annex I of TS 33.501, authentication methods other than EAP-AKA' or 5G-AKA are also allowed for UE to access SNPN services through PLMN.

[0114] Step 909a, AMF 954 will send a NAS Security Mode Command to UE 951 to activate NAS security (see N2 message 909a1 conveying NAS Security Mode Command from AMF 954 to N3IWF 953). If EAP-AKA' authentication is successfully performed in step 908, AMF 954 will encapsulate the EAP Success received from AUSF 955 in the NAS Security Mode Command message.

[0115] Step 909b, N3IWF 953 will forward the NAS security mode command message to UE 951 in the EAP / 5G-NAS packet of the IKE_AUTH response message 909b1.

[0116] Step 909c, UE 951 completes EAP-AKA' authentication (if initiated in step 908), creates NAS security context and N3IWF key, and sends a NAS security mode complete message to N3IWF 953 within the EAP / 5G-NAS packet of IKE_AUTH request message 909c1.

[0117] Step 909d, N3IWF 953 relays the NAS security mode completion message to AMF 954 via N2 message 909d1.

[0118] Step 910a, upon receiving the NAS security mode completion, the AMF 954 will send an NGAP initial context setup request message 910a1 including the N3IWF key to the N3IWF 953.

[0119] Step 910b, this triggers the N3IWF 953 to send an EAP Success in an IKE_AUTH Response message 910b 1 to the UE 951, thereby completing the EAP-5G session. No further EAP-5G packets are exchanged.

[0120] Step 911, establish an IPsec SA between UE 951 and N3IWF 953 by using the common N3IWF key created by UE 951 in step 909c and received by N3IWF 953 in step 910a. This IPsec SA is called "signaling IPsec SA". After the establishment of the signaling IPsec SA, N3IWF 953 notifies AMF 954 that the UE context (including AN security) has been created by sending an NGAP Initial Context Setup Response. The signaling IPsec SA will be configured to operate in tunnel mode, and N3IWF 953 will assign an "inside" IP address to UE 951. As specified in RFC 4555, if the N3IWF 953 receives an indication that the UE 951 supports MOBIKE (see step 903), the N3IWF 953 will include a notification payload in the IKE_AUTH response message 911a1 sent in step 911a to indicate that MOBIKE will be supported.

[0121] Subsequent NAS messages exchanged between UE 951 and N3IWF 953 will be sent over the signaling IPsec SA and will be carried over TCP / IP. UE 951 will send NAS messages within TCP / IP packets whose source address is the "internal" IP address of UE 951 and whose destination address is the NAS_IP_ADDRESS received in step 911a. N3IWF 953 will send NAS messages within TCP / IP packets whose source address is the NAS_IP_ADDRESS and whose destination address is the "internal" IP address of UE. Immediately after establishing the signaling IPsec SA in step 911a, a TCP connection for reliable NAS transport between UE 951 and N3IWF 953 will be initiated by UE 951. UE 951 will send a TCP connection request to NAS_IP_ADDRESS and to the TCP port number specified in 3GPP TS 24.502 V17.5.0 (March 2022).

[0122] Step 912: AMF 954 sends a NAS registration accept message 912a to N3IWF 953. N2 message 912a includes the NSSAI allowed for the access type of UE 951.

[0123] As indicated by block 912b, the AMF 954 indicates to the UE 951 whether it supports non-3GPP path switching.

[0124] Step 913, N3IWF 953 forwards the NAS Registration Accept message via message 913a to UE 951 through the established signaling IPsec SA. If the NAS Registration Accept message is received by N3IWF 953 before the IPsec SA is established, N3IWF 953 stores it and forwards it to UE 951 only after the establishment of the signaling IPsec SA.

[0125] When registering with UDM, AMF 954 will provide the access type set to "Non-3GPP Access" to UDM.

[0126] Note 3: Even when the UE accesses the SNPN service via the PLMN through 3GPP access, the access type is set to "Non-3GPP access".

[0127] The benefit of the described processing is providing a non-3GPP path switching capability between the UE and the 5GC during registration, thereby reducing signaling in the network and on the device compared to systems that do not include such capability exchange.

[0128] Furthermore, the selection of appropriate network functions (e.g. AMF, SMF) is facilitated through the exchange of capability information.

[0129] Fig.10 is a diagram of an exemplary assembly 1000 of components that may be included in a user equipment (UE) according to an exemplary embodiment. According to an exemplary embodiment, the assembly 1000 of components may be included, for example, in Figure 2 UE 202 of system 200, Figure 3 UE 202 and / or Figure 4 In the UE 400.

[0130] The components in component assembly 1000 can and in some embodiments are fully implemented in hardware within a processor (e.g., processor 402), for example, as individual circuits. The components in component assembly 1000 can and in some embodiments are fully implemented in hardware within hardware component assembly 414, for example, as individual circuits corresponding to different components. In other embodiments, some of the components are implemented within processor 402, for example, as circuits, and other components are implemented outside of processor 402 and coupled to processor 402, for example, as circuits within component assembly 414. It should be recognized that the integration of components on the processor and / or some components being outside the processor can be one of design choices. Alternatively, instead of being implemented as circuits, all or some of the components can be implemented in software and stored in the memory 412 of UE 400, where when the components are executed by a processor (e.g., processor 402), the components control the operation of UE 400 to implement the functions corresponding to the components. In some such embodiments, component assembly 1000 is included in memory 412 as part of software component assembly 472. In other embodiments, various components in component assembly 1000 are implemented as a combination of hardware and software, such as another circuit external to the processor provides input to processor 402, which then operates under software control to implement a portion of the component's functionality.

[0131] When implemented in software, the components include code that, when executed by a processor (e.g., processor 402), configures the processor to implement a function corresponding to the component. In an embodiment where component assembly 1000 is stored in memory 412, memory 412 is a computer program product including a computer-readable medium including code for causing at least one computer (e.g., processor 402) to implement the function corresponding to the component, such as a separate code for each component.

[0132] Components that are completely hardware-based or completely software-based may be used. However, it should be appreciated that any combination of software and hardware (e.g., circuit-implemented components) may be used to implement the described functionality. Fig.10 The components shown in the figure control and / or configure the UE 400 or the units therein (such as the processor 402) to implement the functions of the corresponding steps shown and / or described in the method of one or more flowcharts, signaling diagrams described with respect to any of the figures. Therefore, the component assembly 1000 includes one or more corresponding steps described and / or shown (such as Figure 3 Various components of the functionality of the signaling diagram 300 (method steps).

[0133] Component assembly 1000 includes: a component 1002 configured to generate an initial registration request message including UE capability information, wherein the UE capability information includes an indicator indicating whether the UE supports path switching of MA PDU sessions between N3GPP access paths; and a component 1004 configured to operate the UE, for example, to send a message including the generated initial registration request message to a network interface device, wherein the initial registration request message includes the UE capability information.

[0134] The component assembly 1000 also includes: a component 1006 configured to operate the UE to receive a registration acceptance message from the AMF, wherein the registration acceptance message includes a globally unique AMF identifier (GUAMI) and information indicating whether the AMF identified by the GUAMI supports path switching of MA PDU sessions between access paths; and a component 1008 configured to operate the UE to send a message to the AMF identified by the received GUAMI to initiate MA PDU session establishment.

[0135] Component assembly 1000 also includes: component 1010 configured to operate the UE to participate in a first MA PDU session, wherein the participation in the first MA PDU session includes communication through a first access path, and the first access path includes a first N3GPP access device; component 1012 configured to operate the UE to implement path switching of the first MA PDU session from the first access path to a second access path, and the second access path includes a second N3GPP access device, the second access path is different from the first access path, and the second access device is different from the first access device; and component 1014 configured to operate the UE to continue to participate in the first MA PDU session, and the continued participation in the first MA PDU session includes communication through the first access path.

[0136] Fig.11is a diagram of an exemplary component assembly 1100 that may be included in a network interface device according to an exemplary embodiment. According to an exemplary embodiment, the component assembly 1100 is, for example, included in Figure 2 In the NG-RAN gNB base station 210 of the system 200, Figure 2 In the N3IWF 214 of the system 200, Figure 2 In the TNGF 220 of the system 200, Figure 3 In the network interface device 303, Figure 5 The access network device 500, and / or Figure 6 In the network interface device 600.

[0137] The components in component assembly 1100 can and in some embodiments are fully implemented in hardware within a processor (e.g., processor 602), for example, as individual circuits. The components in component assembly 1100 can and in some embodiments are fully implemented in hardware within hardware component assembly 608, for example, as individual circuits corresponding to different components. In other embodiments, some of the components are implemented within processor 602, for example, as circuits, and other components are implemented outside of processor 602 and coupled to processor 602, for example, as circuits within component assembly 608. It should be recognized that the integration of components on the processor and / or some components being outside the processor can be one of design choices. Alternatively, instead of being implemented as circuits, all or some of the components can be implemented in software and stored in the memory 610 of the network interface device 600, wherein when the components are executed by a processor (e.g., processor 602), the components control the operation of the network interface device 600 to implement the functions corresponding to the components. In some such embodiments, component assembly 1100 is included in memory 610 as part of software component assembly 630. In other embodiments, various components in component assembly 1100 are implemented as a combination of hardware and software, such as another circuit external to the processor provides input to processor 602, which then operates under software control to implement a portion of the component's functionality.

[0138] When implemented in software, the components include code that, when executed by a processor (e.g., processor 602), configures the processor to implement a function corresponding to the component. In an embodiment where component assembly 1100 is stored in memory 610, memory 610 is a computer program product including a computer-readable medium including code for causing at least one computer (e.g., processor 602) to implement the function corresponding to the component, such as a separate code for each component.

[0139] Components that are completely hardware-based or completely software-based may be used. However, it should be appreciated that any combination of software and hardware (e.g., circuit-implemented components) may be used to implement the described functionality. Fig.11 The components shown in the figure control and / or configure the network interface device 600 or the units therein (such as the processor 602) to implement the functions of the corresponding steps shown and / or described in the method of one or more flowcharts, signaling diagrams described with respect to any of the figures. Therefore, the component assembly 1100 includes implementing one or more corresponding steps described and / or shown in the exemplary method (such as Figure 3 Various components of the functionality of the signaling diagram 300 (method steps).

[0140] Component assembly 1100 includes: a component configured to operate a network interface device to receive a message including an initial registration request message, wherein the initial registration request message includes UE capability information, and the UE capability information indicates whether the UE supports path switching of MA PDU sessions between N3GPP access paths; a component 1104 configured to select an AMF from multiple AMFs as a host AMF, for example based on access network parameters and local policies; and a component 1106 configured to send the received initial registration request message including UE capability information to the selected AMF.

[0141] The component assembly 1100 also includes: a component 1108 configured to receive a registration accept message from the AMF, wherein the registration accept message includes a globally unique AMF identifier (GUAMI) and information indicating whether the AMF identified by the GUAMI supports path switching of MA PDU sessions between N3GPP access paths; and a component 1110 configured to send a forward copy of the registration accept message received from the AMF to the UE, wherein the registration accept message includes a globally unique AMF identifier (GUAMI) and information indicating whether the AMF identified by the GUAMI supports path switching of MA PDU sessions between N3GPP access paths.

[0142] Fig.12 is a diagram of an exemplary assembly of components that may be included in an access and mobility management function (AMF) according to an exemplary embodiment. According to an exemplary embodiment, the component assembly 1200 is, for example, included in Figure 2 The AMF 1221 of the system 200 includes Figure 2 The AMF 2 222 of the system 200 includes Figure 3 AMF 1 221, including Figure 3 AMF 2222, and / or included in Figure 7 AMF 700.

[0143] The components in component assembly 1200 can and in some embodiments are fully implemented in hardware within a processor (e.g., processor 702), for example, as individual circuits. The components in component assembly 1200 can and in some embodiments are fully implemented in hardware within hardware component assembly 706, for example, as individual circuits corresponding to different components. In other embodiments, some of the components are implemented within processor 702, for example, as circuits, and other components are implemented outside of processor 702 and coupled to processor 702, for example, as circuits within component assembly 706. It should be recognized that the integration of components on the processor and / or some components being outside the processor can be one of the design choices. Alternatively, instead of being implemented as circuits, all or some of the components can be implemented in software and stored in memory 708 of AMF 700, where when the components are executed by a processor (e.g., processor 702), the components control the operation of AMF 700 to implement the functions corresponding to the components. In some such embodiments, component assembly 1200 is included in memory 708 as part of software component assembly 720. In other embodiments, various components in component assembly 1200 are implemented as a combination of hardware and software, such as another circuit external to the processor provides input to processor 702, which then operates under software control to implement a portion of the component's functionality.

[0144] When implemented in software, the components include code that, when executed by a processor (e.g., processor 702), configures the processor to implement the functionality corresponding to the components. In an embodiment where component assembly 1200 is stored in memory 708, memory 708 is a computer program product including a computer-readable medium including code for causing at least one computer (e.g., processor 702) to implement the functionality corresponding to the components, such as separate code for each component.

[0145] Components that are completely hardware-based or completely software-based may be used. However, it should be appreciated that any combination of software and hardware (e.g., circuit-implemented components) may be used to implement the described functionality. Fig.12 The components shown in the figure control and / or configure the AMF 700 or the units therein (such as the processor 702) to implement the functions of the corresponding steps shown and / or described in the method of one or more flowcharts, signaling diagrams described with respect to any of the figures. Therefore, the component assembly 1200 includes implementing one or more corresponding steps described and / or shown in the exemplary method (such as Figure 3 Various components of the functionality of the signaling diagram 300 (method steps).

[0146] The component assembly 1200 includes: a component 1202 configured to operate the AMF to receive an initial registration request message from a network interface device or from another AMF, the initial registration request message including UE capability information, the UE capability information indicating whether the UE supports path switching of MA PDU sessions between N3GPP access paths; a component 1204 configured to determine whether the path switching capability of the AMF is suitable for supporting the path switching capability of the UE indicated in the initial registration request message; a component 1206 configured to operate the AMF to send a registration message to the UDM in response to determining that the AMF capability is suitable for supporting the path switching capability of the UE indicated in the received initial registration request message, so as to register the UE and associate the UE with the AMF; a component 1208 configured to generate a registration acceptance message in response to determining that the AMF capability is suitable for supporting the UE path switching capability, the registration acceptance message including a globally unique AMF identifier (GUAMI) corresponding to the AMF and indicating whether the AMF indicated by the GUAMI supports MA between N3GPP access paths. An identifier for a path switch of a PDU session; and a component 1210 configured to send a generated registration acceptance message to a network interface device for delivery to the UE, wherein the registration acceptance message includes a GUAMI and information indicating whether the AMF supports path switching of MA PDU sessions between N3GPP access paths.

[0147] Component assembly 1200 also includes component 1212, which is configured to search for one or more other AMFs having path switching capabilities suitable for supporting UE path switching capabilities in response to determining that its AMF capabilities are not suitable for supporting UE path switching capabilities. Component 1212 includes component 1214, which is configured to identify one or more other AMFs having path switching capabilities suitable for supporting UE path switching capabilities (e.g., supporting path switching of MA PDU sessions between N3GPP access paths). Component assembly 1200 also includes component 1216 configured to operate the AMF to select an AMF from one or more AMFs identified that meet the UE path switching requirements, and component 1218 configured to operate the AMF to send (e.g., forward) the received initial registration request message including UE path switching capability information to the selected AMF. Component assembly 1200 also includes component 1220 configured to operate the AMF to receive a message from the UE for initiating MA PDU session establishment, and component 1222 configured to select an SMF from a plurality of SMFs including UE capabilities supporting path switching for MA PDU sessions between N3GPP access paths.

[0148] Fig.131300 is a flowchart of an exemplary method of operating a first user equipment (UE) device according to an exemplary embodiment. The first UE device implementing the method of flowchart 1300 is, for example, any one of the following: Figure 2 or Figure 3 UE202, Figure 4 UE 400, Fig. 9 UE 951, and / or including Fig.10 The components of the UE 1000 are assembled. Operation of the exemplary method begins at step 1302, where a first UE device is powered on and initialized. Operation proceeds from step 1302 to step 1304.

[0149] In step 1304, the first UE device is operated to send a first message to a first network interface device (303) (e.g., a 3GPP Next Generation Radio Access Network (NG-RAN) device (e.g., a gNB), a non-3GPP interworking function (N3IWF), or a trusted network gateway function (TNGF)), wherein the first message includes an initial registration request message, and the initial registration request message includes path switching capability information indicating whether the first UE device supports path switching of MA PDU sessions between N3GPP access paths.

[0150] In some embodiments, the initial registration request message includes a message type indicator indicating the initial registration type. In some embodiments, the path switching capability information included in the initial registration request message indicates that the first UE device supports path switching of MA PDU sessions between N3GPP access paths. In some embodiments, the initial registration request message is included in the first message as part of a payload of the first message, and the content of the initial registration message is not fully accessible by the first network interface device, but is accessible by one or more AMFs to which the first network interface device sends the initial registration request message.

[0151] In some embodiments, the first network interface device (e.g., device 303) is a 3GPP Next Generation Radio Access Network (NG-RAN) device, such as NG-RAN 210. In some such embodiments, the first network interface device is a gNB base station. In some embodiments, the first network interface device is a non-3GPP interworking function (N3IWF), such as N3IWF 214. In some embodiments, the first network interface device is a trusted network gateway function (TNGF), such as TNGF 220. Operation proceeds from step 1304 to step 1306.

[0152] In step 1306, the first UE device is operated to receive (in response to the initial registration request message) a registration acceptance message from the first network interface device, the registration acceptance message including the GUAMI of the AMF identifying the AMF selected as the AMF supporting the communication session of the first UE device. In some embodiments, the registration acceptance message includes AMF switching capability information indicating the path switching capability of the identified AMF (i.e., the AMF identified by the GUAMI included in the registration acceptance message). In some embodiments, the AMF path switching capability information is conveyed via a mandatory field of the registration acceptance message.

[0153] In some embodiments, the path switching capability information in the registration accept message indicates that the identified AMF (e.g., AMF 221) does not support path switching of MA PDU sessions between N3GPP access paths.

[0154] In some embodiments, the path switching capability information in the registration accept message indicates that the identified AMF (eg, AMF 222) supports path switching of MA PDU sessions between N3GPP access paths. Operation proceeds from step 1306 to step 1308.

[0155] In step 1308, the first UE device is operated to participate in a first MA PDU session, wherein the participation in the first MA PDU session includes communicating over a first path (first access path), wherein the first path includes a first N3GPP access device, such as AP 212 of N3GPP access network #A 206. Operations may and sometimes (e.g., for embodiments in which the first UE 202 and AMF 222 support N3GPP MA PDU path switching) continue from step 1308 to step 1310.

[0156] In step 1310, the first UE device is operated to implement a path switch of the first MA PDU session from the first path to the second path (second access path), the second path including a second N3GPP access device, such as TNAP 218 of N3GPP access network #B ​​208. Operation proceeds from step 1310 to step 1312.

[0157] In step 1312, the first UE device is operated to continue to participate in the first MA PDU session, wherein continuing to participate in the first MA PDU session includes communicating through a second path.

[0158] Fig.14 1400 is a flowchart of an exemplary method of operating a first user equipment (UE) device according to an exemplary embodiment. The first UE device implementing the method of flowchart 1400 is, for example, any one of the following: Figure 2 or Figure 3UE202, Figure 4 UE 400, Fig. 9 UE 951, and / or including Fig.10 The components of the UE 1000 are assembled. Operation of the exemplary method begins at step 1402, where a first UE device is powered on and initialized. Operation proceeds from step 1402 to step 1404.

[0159] In step 1404, the first UE device is operated to send a first message to a first network interface device (303) (e.g., a 3GPP Next Generation Radio Access Network (NG-RAN) device (e.g., a gNB), a non-3GPP interworking function (N3IWF), or a trusted network gateway function (TNGF)), wherein the first message includes an initial registration request message. In some embodiments, the first network interface device (e.g., device 303) is a 3GPP Next Generation Radio Access Network (NG-RAN) device, such as NG-RAN 210. In some such embodiments, the first network interface device is a gNB base station. In some embodiments, the first network interface device is a non-3GPP interworking function (N3IWF), such as N3IWF 214. In some embodiments, the first network interface device is a trusted network gateway function (TNGF), such as TNGF 220.

[0160] In some embodiments, the initial registration request message includes path switching capability information indicating whether the first UE device supports path switching of MA PDU sessions between N3GPP access paths. Operation continues from step 1404 to step 1406.

[0161] In step 1406, the first UE device is operated to receive (in response to the initial registration request) a registration acceptance message from the first network interface device, wherein the registration acceptance message includes the GUAMI of the AMF identifying the AMF selected as the AMF supporting the communication session of the first UE device, and includes AMF path switching capability information indicating the path switching support capability of the identified AMF (i.e., the AMF identified by the GUAMI in the registration acceptance message).

[0162] In some embodiments, the AMF path switching capability information is conveyed via a mandatory field.

[0163] In some embodiments, the path switching capability information in the registration accept message indicates that the identified AMF (e.g., AMF 221) does not support path switching of MA PDU sessions between N3GPP access paths.

[0164] In some embodiments, the path switching capability information in the registration accept message indicates that the identified AMF (eg, AMF 222) supports path switching of MA PDU sessions between N3GPP access paths. Operation proceeds from step 1406 to step 1408.

[0165] In step 1408, the first UE device is operated to participate in a first MA PDU session, wherein the participation in the first MA PDU session includes communicating over a first path (first access path), wherein the first path includes a first N3GPP access device, such as AP 212 of N3GPP access network #A 206. Operations may and sometimes (e.g., for embodiments in which the first UE 202 and the identified AMF 222 support N3GPP MA PDU path switching) continue from step 1408 to step 1410.

[0166] In step 1410, the first UE device is operated to implement a path switch of the first MA PDU session from the first path to the second path (second access path), the second path including a second N3GPP access device, such as TNAP 218 of N3GPP access network #B ​​208. Operation proceeds from step 1410 to step 1412.

[0167] In step 1412, the first UE device is operated to continue to participate in the first MA PDU session, wherein continuing to participate in the first MA PDU session includes communicating through a second path.

[0168] First Numbered List of Exemplary Method Embodiments:

[0169] Method embodiment 1. A communication method, the method comprising: operating a network interface device (303) (e.g., a 3GPP next generation radio access network (NG-RAN) device (e.g., a gNB base station), a non-3GPP interworking function (N3IWF), or a trusted network gateway function (TNGF)) to receive (308) a first message from a first user equipment (UE) (202) (e.g., a first UE device), the first message comprising an initial registration request message, the initial registration request message comprising path switching capability information indicating whether the first UE supports path switching of MA PDU sessions between N3GPP access paths; operating the network interface device to make (310) an initial AMF selection in response to receiving the first message to select a first AMF (221) to act as a host AMF for the first UE (202); and operating the network interface device to communicate (312) the initial registration request message to the first AMF (221).

[0170] Method embodiment 1A. The method of method embodiment 1, wherein the initial registration message includes a message type indicator indicating an initial registration type.

[0171] The method of method embodiment 1B and method embodiment 1A, wherein the initial registration request message is included in the first message as part of the payload of the first message, and the content of the initial registration message is not fully accessible by the network interface device, but is accessible by one or more AMFs to which the initial registration message is conveyed.

[0172] The method of method embodiment 2 and method embodiment 1 also includes: operating the first AMF to determine (318) whether the host AMF can support the path switching capability level supported by the first UE as indicated by the path switching capability information included in the initial registration request message.

[0173] Method embodiment 3, the method of method embodiment 2, wherein the network interface device does not consider the path switching capability of the first UE when making the initial AMF selection (this is, for example, because the path switching information included in the initial registration request message cannot be accessed, but the path switching information can be accessed by the AMF).

[0174] Method embodiment 4, the method of method embodiment 2, wherein the path switching capability information included in the initial registration request message indicates that the first UE supports path switching of MA PDU sessions between N3GPP access paths; wherein the first AMF does not support path switching of MA PDU sessions between N3GPP access paths; wherein operating the first AMF to determine (318) whether the host AMF can support the path switching capability level supported by the first UE as indicated by the path switching capability information included in the initial registration request message includes: determining that the first AMF cannot support the path switching capability level supported by the first UE; and wherein the method also includes: operating the first AMF to select (320) a second AMF (222) that can support the path switching capability level supported by the first UE to act as a host for the first UE (for example, different from AMF 1, AMF 2 supports path switching of MA PDU sessions between N3GPP access paths).

[0175] The method of method embodiment 5 and method embodiment 4 also includes: operating the first AMF to send (322) an initial registration request message path switching capability information to the second AMF, indicating that the first UE supports path switching of MA PDU sessions between N3GPP access paths.

[0176] Method Embodiment 6 - The method of Method Embodiment 5 also includes: operating the second AMF (AMF 2) to receive (326) an initial registration request message corresponding to the first UE; and operating the second AMF (AMF 2) to send (336) a registration acceptance message to the network interface device (for example, after determining that it supports the path switching level supported by the first UE) to indicate that the second AMF accepts the initial registration request issued by the first UE.

[0177] Method embodiment 6A, the method of method embodiment 6, wherein the registration acceptance message includes the GUAMI (globally unique AMF identifier) ​​of the second AMF and an indicator indicating that the second AMF supports path switching of MA PDU sessions between N3GPP access paths.

[0178] The method of method embodiment 7 and method embodiment 6 also includes: operating the second AMF to select (364) an SMF (SMF 2) that supports path switching of MA PDU sessions between N3GPP access paths to support communication with the first UE (for example, making the selection from multiple available SMFs, some of which do not support path switching (for example, SMF 1), and some of which support path switching (for example, SMF 2)).

[0179] Method embodiment 7A, the method of method embodiment 7, also includes: operating the second AMF (AMF 2) to send (366) a create SM context request to the selected SMF to create an SM context for the first UE at the selected SMF (SMF 2).

[0180] The method of method embodiment 8 and method embodiment 7 also includes: operating the network interface device to send (346) a registration acceptance message to the first UE, which includes the GUAMI of the second AMF and information indicating that the AMF supports path switching of MAPDU sessions between N3GPP access paths; and operating the second AMF to receive (362) an initiate MA PDU session establishment message from the first UE.

[0181] Method embodiment 8A, the method of method embodiment 8, wherein sending (366) a create SM context request is sent by the selected SMF as part of establishing an MA PDU session for the first UE in response to an initiate MA PDU session establishment message received from the first UE.

[0182] The method of method embodiment 9 and method embodiment 8 further includes: operating the UE to communicate with another network interface device through the MA PDU path established in response to initiating the MA PDU session establishment message.

[0183] First Numbered List of Exemplary System Embodiments:

[0184] System embodiment 1, a communication system (200), comprising: a network interface device (303 or 214 or 220 or 210 or 600) (e.g., 3GPP next generation radio access network (NG-RAN) equipment (e.g., gNB base station), non-3GPP interworking function (N3IWF) or trusted network gateway function (TNGF)), comprising: a first receiver (612); a first transmitter (618); and a first processor (602), configured to: operate the network interface device (303) (through the first receiver) to receive (308) a first message from a first user equipment (UE) (202) (e.g., a first UE device), the first message comprising an initial registration request message, the initial registration request message comprising an indication of whether the first UE supports MA between N3GPP access paths The method comprises: providing a network interface device (303) and a receiver (204) for transmitting an initial registration request message to the first AMF (221) and transmitting the initial registration request message to the first AMF (221).

[0185] System embodiment 1A. The communication system (200) of system embodiment 1, wherein the initial registration message includes a message type indicator indicating the initial registration type.

[0186] The communication system (200) of system embodiment 1B and system embodiment 1A, wherein the initial registration request message is included in the first message as part of the payload of the first message, and the content of the initial registration message is not fully accessible by the network interface device (303), but is accessible by one or more AMFs (221, 222) to which the initial registration message is conveyed.

[0187] System embodiment 2, the communication system (200) of system embodiment 1, further includes: the first AMF (221 or 700), including: a second processor (702), configured to: operate the first AMF (221) to determine (318) whether the host AMF can support the path switching capability level supported by the first UE (202) as indicated by the path switching capability information included in the initial registration request message.

[0188] System embodiment 3, the communication system (200) of system embodiment 2, wherein the network interface device (303) does not consider the path switching capability of the first UE (202) when making an initial AMF selection (this is, for example, because the path switching information included in the initial registration request message cannot be accessed, but the path switching information can be accessed by the AMF).

[0189] System embodiment 4, the communication system (200) of system embodiment 2, wherein the path switching capability information included in the initial registration request message indicates that the first UE (202) supports path switching of MA PDU sessions between N3GPP access paths; wherein the first AMF (221) does not support path switching of MA PDU sessions between N3GPP access paths; and wherein the second processor (702 of AMF 221) is further configured to: as part of being configured to operate the first AMF (221) to determine (318) whether the host AMF can support the path switching capability level supported by the first UE (202) as indicated by the path switching capability information included in the initial registration request message, determine that the first AMF (221) cannot support the path switching capability level supported by the first UE (202); operate the first AMF (221) to select (320) a second AMF (222) that can support the path switching capability level supported by the first UE to act as a host for the first UE (e.g., different from AMF 1 (221), AMF 2(222) supports path switching of MA PDU sessions between N3GPP access paths).

[0190] System embodiment 5, the communication system (200) of system embodiment 4, wherein the first AMF (221) further includes a second transmitter (AMF 221's 714) configured to implement the following operations: operate the first AMF (221) (through the second transmitter 714) to send (322) to the second AMF an initial registration request message path switching capability information indicating that the first UE supports path switching of MA PDU sessions between N3GPP access paths.

[0191] The communication system (200) of system embodiment 6 and system embodiment 5 also includes: the second AMF (222 or 700), including: a second receiver (712 of 222); a third transmitter (714 of 222); and a third processor (702 of 222), configured to: operate the second AMF (AMF 2 222) (via the second receiver (712 of 222)) to receive (326) an initial registration request message corresponding to the first UE (202); and operate the second AMF (AMF 2 222) (via the third transmitter (714 of 222)) to send (336) a registration acceptance message to the network interface device (for example, after determining that it supports the path switching level supported by the first UE) to indicate that the second AMF (222) accepts the initial registration request issued by the first UE (202).

[0192] System embodiment 6A, the communication system (200) of system embodiment 6, wherein the registration acceptance message includes the GUAMI (globally unique AMF identifier) ​​of the second AMF (222) and an indicator indicating that the second AMF (222) supports path switching of MAPDU sessions between N3GPP access paths.

[0193] The communication system (200) of system embodiment 7 and system embodiment 6, wherein the third processor (702 of 222) is further configured to: operate the second AMF (222) to select (364) an SMF (SMF 2 224) that supports path switching of MA PDU sessions between N3GPP access paths to support communication with the first UE (e.g., making the selection from a plurality of available SMFs, some of which do not support path switching (e.g., SMF 1 225), and some of which support path switching (e.g., SMF 2 224)).

[0194] The communication system (200) of system embodiment 7A and method embodiment 7, wherein the third processor (702 of 222) is further configured to: operate the second AMF (AMF 2 222) (via the third transmitter (714 of 222)) to send (366) a create SM context request to the selected SMF (224) to create an SM context for the first UE (202) at the selected SMF (SMF 2 224).

[0195] System embodiment 8, the communication system (200) of system embodiment 7, wherein the first processor (602) is further configured to: operate the network interface device (303) to send (346) a registration acceptance message to the first UE (202), including the GUAMI of the second AMF (222) and information indicating that the second AMF (222) supports path switching of MA PDU sessions between N3GPP access paths; and wherein the third processor (702 of 222) is further configured to: operate the second AMF (222) to receive (362) an initiate MA PDU session establishment message from the first UE (202).

[0196] System embodiment 8A, the communication system (200) of system embodiment 8, wherein, as part of establishing an MA PDU session for a first UE (202) in response to an initiate MA PDU session establishment message received from the first UE (202), a create SM content request is sent by the selected SMF (224).

[0197] The communication system (200) of system embodiment 9 and system embodiment 8 also includes: the first UE (202 or 400), including: a first wireless receiver (438); a first wireless transmitter (440); and a fourth processor (402), configured to: operate the first UE (202) to communicate with another network interface device through the MA PDU path established in response to initiating an MA PDU session establishment message (for example, sending signals through the first wireless transmitter (438) and / or receiving signals through the first wireless transmitter (440)).

[0198] First Numbered List of Exemplary Non-Transitory Computer Readable Medium Embodiments:

[0199] Non-transitory computer-readable medium embodiment 1. A non-transitory computer-readable medium (610) comprising computer-executable instructions, wherein the computer-executable instructions, when executed by a processor (602) of a network interface device (303 or 214 or 220 or 210 or 600 or 602), cause the network interface device to implement the following steps: operate the network interface device (e.g., a 3GPP next generation radio access network (NG-RAN) device (e.g., a gNB base station), a non-3GPP interworking function (N3IWF), or a trusted network gateway function (TNGF)) to receive (308) a first message from a first user equipment (UE) (202) (e.g., a first UE device), wherein the first message comprises an initial registration request message, wherein the initial registration request message comprises a message indicating whether the first UE supports MA between N3GPP access paths. The invention relates to a method for operating a network interface device to provide a path switching capability information for a path switching of a PDU session; operating a network interface device to make (310) an initial AMF selection in response to receiving a first message to select a first AMF (221) to act as a host AMF for a first UE (202); and operating the network interface device to communicate (312) an initial registration request message to the first AMF (221).

[0200] Second Numbered List of Exemplary Method Embodiments:

[0201] Method embodiment 1. A communication method, the method comprising: operating a network interface device (303) (e.g., a 3GPP next generation radio access network (NG-RAN) device (e.g., a gNB base station), a non-3GPP interworking function (N3IWF), or a trusted network gateway function (TNGF)) to receive (308) a first message from a first user equipment (UE) (202), the first message comprising an initial registration request message; and operating the network interface device to send (346) a registration acceptance message to the first UE, the registration acceptance message comprising a GUAMI of an AMF that identifies the AMF selected to support a communication session of the first UE, and comprising AMF path switching capability information indicating the path switching support capability of the identified AMF (i.e., the AMF identified by the GUAMI included in the registration acceptance message).

[0202] Method embodiment 1A - The method of method embodiment 1, wherein the network interface device (303) is one of a 3GPP next generation radio access network (NG-RAN) device (e.g., a gNB base station), a non-3GPP interworking function (N3IWF), or a trusted network gateway function (TNGF).

[0203] Method embodiment 1B, the method of method embodiment 1, wherein the AMF path switching capability information is conveyed through a mandatory field.

[0204] Method embodiment 2: the method of method embodiment 1, wherein the path switching capability information in the registration acceptance message indicates that the identified AMF does not support path switching of MA PDU sessions between N3GPP access paths.

[0205] Method embodiment 3: The method of method embodiment 2, wherein the path switching capability information in the registration acceptance message indicates that the identified AMF supports path switching of MA PDU sessions between N3GPP access paths.

[0206] The method of method embodiment 4 and method embodiment 3 further includes: operating the identified AMF to receive (362) an MA PDU session establishment message initiated from the first UE.

[0207] The method of method embodiment 5 and method embodiment 4 also includes: operating the identified AMF (222) to select (364) an SMF (SMF 2 224) that supports path switching of MA PDU sessions between N3GPP access paths to support communication with the first UE (for example, making the selection from multiple available SMFs, some of which do not support path switching (for example, SMF1 225), and some of which support path switching (for example, SMF 2224)).

[0208] The method of method embodiment 6 and method embodiment 5 also includes: operating the identified AMF (AMF 2 222) (through the third transmitter (714 of 222)) to send (366) a create SM context request to the selected SMF (SMF 2 224) to create an SM context for the first UE (202) at the selected SMF (SMF 2 224).

[0209] Method embodiment 7, the method of method embodiment 6, wherein sending (366) a create SM content request is sent by the selected SMF as part of establishing an MA PDU session for the first UE in response to an initiate MA PDU session establishment message received from the first UE.

[0210] The method of method embodiment 8 and method embodiment 7 further include: operating another network interface device to communicate with the UE through the MA PDU path established in response to initiating the MA PDU session establishment message.

[0211] Second Numbered List of Exemplary System Embodiments:

[0212] System embodiment 1, a communication system (200), comprising: a network interface device (303 or 214 or 220 or 210 or 600) (e.g., a 3GPP next generation radio access network (NG-RAN) device (e.g., a gNB base station), a non-3GPP interworking function (N3IWF), or a trusted network gateway function (TNGF)), comprising: a first receiver (612); a first transmitter (618); and a first processor (602), configured to: operate the network interface device (303) (through the first receiver) from a first user equipment ( A first UE (202) (e.g., a first UE device) receives a first message, the first message comprising an initial registration request message; and an operation network interface device (303) sends (346) a registration acceptance message to the first UE (202), the registration acceptance message comprising a GUAMI of an AMF that identifies the AMF (221 or 222) selected to support the first UE communication session, and comprising AMF path switching capability information indicating the path switching support capability of the identified AMF (i.e., the AMF identified by the GUAMI included in the registration acceptance message).

[0213] System embodiment 1A, the communication system (200) of system embodiment 1, wherein the network interface device (303) is one of the 3GPP next generation radio access network (NG-RAN) devices (e.g., a gNB base station) or a trusted network gateway function (TNGF).

[0214] System embodiment 1B, the communication system (200) of system embodiment 1, wherein the AMF path switching capability information is conveyed via a mandatory field.

[0215] System embodiment 2, the communication system (200) of system embodiment 1, wherein the path switching capability information in the registration acceptance message indicates that the identified AMF (221) does not support path switching of MA PDU sessions between N3GPP access paths.

[0216] System embodiment 3, the communication system (200) of system embodiment 2, wherein the path switching capability information in the registration acceptance message indicates that the identified AMF (222) supports path switching of MA PDU sessions between N3GPP access paths.

[0217] The communication system (200) of system embodiment 4 and system embodiment 3 further includes: the identified AMF (222), including: a second receiver (712); and a second processor (702), configured to: operate the identified AMF (222) (via the second receiver (712)) to receive an MA PDU session establishment message initiated from the first UE (202).

[0218] System embodiment 5, the communication system (200) of system embodiment 4, wherein the second processor (702) is further configured to: operate the identified AMF (222) to select (364) an SMF (SMF 2 224) that supports path switching of MA PDU sessions between N3GPP access paths to support communication of the first UE (for example, making the selection from a plurality of available SMFs, some of which do not support path switching (for example, SMF 1 225), and some of which support path switching (for example, SMF 2 224)).

[0219] The communication system (200) of system embodiment 6 and system embodiment 5, wherein the identified AMF (222) further includes a second transmitter (714); and wherein the second processor (702) is further configured to: operate the identified AMF (AMF2 222) (via the second transmitter (714 of 222)) to send (366) a create SM context request to the selected SMF (SMF 2 224) to create an SM context for the first UE (202) at the selected SMF (SMF 2 224).

[0220] System embodiment 7, the communication system (200) of system embodiment 6, wherein sending (366) a create SM content request is sent by the selected SMF (224) as part of establishing a MAPDU session for the first UE (202) in response to receiving an initiate MAPDU session establishment message from the first UE (202).

[0221] The communication system (200) of system embodiment 8 and system embodiment 7 also includes: another network interface device (303' or 214 or 220 or 210 or 600'), including: a third receiver (612'); a third transmitter (614'); and a third processor (602'), configured to: operate the other network interface device (303') to communicate with the UE (202) through the MA PDU path established in response to the initiation of the MA PDU session establishment message.

[0222] Second Numbered List of Exemplary Non-Transitory Computer Readable Medium Embodiments:

[0223] Non-transitory computer-readable medium embodiment 1. A non-transitory computer-readable medium (610) comprising computer-executable instructions, which, when executed by a processor (602) of a network interface device (303 or 214 or 220 or 210 or 600 or 602), cause the network interface device to implement the following steps: operate the network interface device (e.g., a 3GPP next generation radio access network (NG-RAN) device (e.g., a gNB base station), a non-3GPP interworking function (N3IWF), or a trusted network gateway function (TNGF)) to receive (308) a first message from a first user equipment (UE) (202) (e.g., a first UE device), the first message comprising an initial registration request message; and operate the network interface device to send (346) a registration acceptance message to the first UE, the registration acceptance message comprising a GUAMI of an AMF that identifies the AMF selected to support the first UE communication session, and comprising AMF path switching capability information indicating the path switching support capability of the identified AMF (i.e., the AMF identified by the GUAMI included in the registration acceptance message).

[0224] Third Numbered List of Exemplary Method Embodiments:

[0225] Method embodiment 1. A method for operating a first user equipment (UE) device, the method comprising: operating (1304) the first UE device to send a first message to a first network interface device (303) (e.g., a 3GPP next generation radio access network (NG-RAN) device (e.g., a gNB base station), a non-3GPP interworking function (N3IWF), or a trusted network gateway function (TNGF)), the first message comprising an initial registration request message, the initial registration request message comprising path switching capability information indicating whether the first UE device supports path switching of an MA PDU session between N3GPP access paths; and operating (1306) the first UE device (in response to the initial registration request message) to receive a registration acceptance message from the first network interface device, the registration acceptance message comprising a GUAMI identifying the AMF selected as the AMF supporting the communication session of the first UE device.

[0226] Method embodiment 1A. The method of method embodiment 1, wherein the initial registration message includes a message type indicator indicating an initial registration type.

[0227] Method embodiment 1AA, the method of method embodiment 1, wherein the path switching capability information included in the initial registration request message indicates that the first UE device supports path switching of MA PDU sessions between N3GPP access paths.

[0228] The method of method embodiment 1B and method embodiment 1A, wherein the initial registration request message is included in the first message as part of the payload of the first message, and the content of the initial registration message is not fully accessible by the first network interface device, but is accessible by one or more AMFs to which the first network interface device (303) sends the initial registration message.

[0229] Method embodiment 2: The method of method embodiment 1, wherein the first network interface device (303) is a 3GPP Next Generation Radio Access Network (NG-RAN) device.

[0230] Method embodiment 2A. The method of method embodiment 2, wherein the first network interface device is a gNB base station.

[0231] Method embodiment 3: The method of method embodiment 1, wherein the first network interface device is a non-3GPP interworking function (N3IWF).

[0232] Method embodiment 4: The method of method embodiment 1, wherein the first network interface device is a trusted network gateway function (TNGF).

[0233] Method embodiment 5. The method of method embodiment 1, wherein the registration acceptance message includes AMF path switching capability information indicating the path switching support capability of the identified AMF (i.e., the AMF identified by the GUAMI included in the registration acceptance message).

[0234] Method Example 6: The method of Method Example 5, wherein the AMF path switching capability information is conveyed through the mandatory field of the registration acceptance message.

[0235] Method embodiment 7. The method of method embodiment 5, wherein the path switching capability information in the registration acceptance message indicates that the identified AMF (221) does not support path switching of MA PDU sessions between N3GPP access paths.

[0236] Method embodiment 8. The method of method embodiment 5, wherein the path switching capability information in the registration acceptance message indicates that the identified AMF (222) supports path switching of MA PDU sessions between N3GPP access paths.

[0237] The method of method embodiment 9 and method embodiment 8 also includes: operating (1306) the first UE device to participate in the first MA PDU session, wherein the participation in the first MA PDU session includes communication through a first path (first access path), and the first path includes a first N3GPP access device (e.g., AP 212); operating (1308) the first UE device to implement path switching of the first MA PDU session from the first path to a second path (second access path), and the second path includes a second N3GPP access device (e.g., TNAP 218); and operating (1310) the first UE device to continue to participate in the first MA PDU session, and the continued participation in the first MA PDU session includes communication through the second path.

[0238] Method embodiment 10: The method of method embodiment 9, wherein the identified AMF (222) supports path switching between the first and second paths.

[0239] First numbered list of exemplary apparatus embodiments:

[0240] Apparatus embodiment 1, a first user equipment (UE) device (202 or 400 or 951), comprising: a wireless transmitter (426 or 440 or 454); a wireless receiver (424 or 438 or 452); and a processor (402), configured to: operate (1304) the first UE device (via the wireless transmitter) to send a first message to a first network interface device (303) (e.g., a 3GPP next generation radio access network (NG-RAN) device (e.g., a gNB base station), a non-3GPP interworking function (N3IWF), or a trusted network gateway function (TNGF)), wherein the first message comprises an initial registration request message, wherein the initial registration request message comprises an indication of whether the first UE device supports MA between N3GPP access paths Path switching capability information for path switching of a PDU session; and operation (1306) the first UE device (via a wireless receiver) (in response to an initial registration request message) receives a registration acceptance message from the first network interface device, wherein the registration acceptance message includes a GUAMI identifying the AMF (221 or 222) selected to support the communication session of the first UE device.

[0241] Apparatus embodiment 1A, a first UE device of apparatus embodiment 1, wherein the initial registration message includes a message type indicator indicating an initial registration type.

[0242] Apparatus embodiment 1AA, the first UE device of apparatus embodiment 1, wherein the path switching capability information included in the initial registration request message indicates that the first UE device supports path switching of MA PDU sessions between N3GPP access paths.

[0243] The first UE device of apparatus embodiment 1B and apparatus embodiment 1A, wherein the initial registration request message is included in the first message as part of the payload of the first message, and the content of the initial registration message is not fully accessible by the first network interface device, but is accessible by one or more AMFs to which the first network interface device (303) sends the initial registration message.

[0244] Apparatus embodiment 2: The first UE device of apparatus embodiment 1, wherein the first network interface device (303) is a 3GPP Next Generation Radio Access Network (NG-RAN) device (210).

[0245] Apparatus embodiment 2A, the first UE device of apparatus embodiment 2, wherein the first network interface device (303) is a gNB base station (210).

[0246] Apparatus embodiment 3, the first UE device of apparatus embodiment 1, wherein the first network interface device (303) is a non-3GPP interworking function (N3IWF) (214).

[0247] Apparatus embodiment 4: the first UE device of apparatus embodiment 1, wherein the first network interface device (303) is a trusted network gateway function (TNGF) (220).

[0248] Apparatus embodiment 5, the first UE device of apparatus embodiment 1, wherein the registration acceptance message includes AMF path switching capability information indicating the path switching support capability of the identified AMF (i.e., the AMF identified by the GUAMI included in the registration acceptance message).

[0249] Apparatus embodiment 6, the first UE device of apparatus embodiment 5, wherein the AMF path switching capability information is conveyed through the mandatory field of the registration acceptance message.

[0250] Apparatus embodiment 7, the first UE device of apparatus embodiment 5, wherein the path switching capability information in the registration acceptance message indicates that the identified AMF (221) does not support path switching of MA PDU sessions between N3GPP access paths.

[0251] Apparatus embodiment 8, the first UE device of apparatus embodiment 5, wherein the path switching capability information in the registration acceptance message indicates that the identified AMF (222) supports path switching of MA PDU sessions between N3GPP access paths.

[0252] The first UE device of apparatus embodiment 9 and apparatus embodiment 8, wherein the processor (402) is further configured to: operate (1306) the first UE device to participate in a first MA PDU session, wherein the participation in the first MA PDU session includes communication through a first path (first access path), wherein the first path includes a first N3GPP access device (e.g., AP 212); operate (1308) the first UE device to implement a path switch of the first MA PDU session from the first path to a second path (second access path), wherein the second path includes a second N3GPP access device (e.g., TNAP 218); and operate (1310) the first UE device to continue to participate in the first MA PDU session, wherein the continued participation in the first MA PDU session includes communication through the second path.

[0253] The first UE device of apparatus embodiment 10 and apparatus embodiment 9, wherein the identified AMF (222) supports path switching between the first and second paths.

[0254] Third Numbered List of Exemplary Non-Transitory Computer Readable Medium Embodiments:

[0255] Non-transitory computer-readable medium embodiment 1. A non-transitory computer-readable medium (412) comprising computer-executable instructions, which, when executed by a processor (402) of a first user equipment (UE) device (202 or 400 or 951), cause the first UE device to implement the following steps: operation (1304) the first UE device sends a first message to a first network interface device (303) (e.g., a 3GPP next generation radio access network (NG-RAN) device (e.g., a gNB base station), a non-3GPP interworking function (N3IWF), or a trusted network gateway function (TNGF)), the first message comprising an initial registration request message, the initial registration request message comprising path switching capability information indicating whether the first UE device supports path switching of a MAPDU session between N3GPP access paths; and operation (1306) the first UE device (in response to the initial registration request message) receives a registration acceptance message from the first network interface device, the registration acceptance message comprising a GUAMI identifying the AMF selected as the AMF supporting the communication session of the first UE device.

[0256] Fourth Numbered List of Exemplary Method Embodiments:

[0257] Method embodiment 1. A method for operating a first user equipment (UE) device (202), the method comprising: operating (1404) the first UE device to send a first message to a first network interface device (303) (e.g., a 3GPP next generation radio access network (NG-RAN) device (e.g., a gNB base station), a non-3GPP interworking function (N3IWF), or a trusted network gateway function (TNGF)) (via a wireless transmitter), the first message comprising an initial registration request message; and operating (1406) the first UE device (in response to the initial registration request) to receive a registration acceptance message (via a wireless receiver), the registration acceptance message comprising a GUAMI of an AMF (221 or 222) that identifies the AMF (221 or 222) selected to support a communication session of the first UE device, and comprising AMF path switching capability information indicating the path switching support capability of the identified AMF (i.e., the AMF identified by the GUAMI included in the registration acceptance message).

[0258] Method embodiment 1A. The method of method embodiment 1, wherein the initial registration request message includes path switching capability information indicating whether the first UE device supports path switching of MA PDU sessions between N3GPP access paths.

[0259] Method embodiment 2, the method of method embodiment 1, wherein the first network interface device (303) is a 3GPP next generation radio access network (NG-RAN) device, such as a gNB base station.

[0260] Method embodiment 3: The method of method embodiment 1, wherein the first network interface device is a non-3GPP interworking function (N3IWF).

[0261] Method embodiment 4: The method of method embodiment 1, wherein the first network interface device is a trusted network gateway function (TNGF).

[0262] Method embodiment 5: The method of method embodiment 1, wherein the AMF path switching capability information is conveyed through a mandatory field.

[0263] Method embodiment 6. The method of method embodiment 1, wherein the path switching capability information in the registration acceptance message indicates that the identified AMF (221) does not support path switching of MA PDU sessions between N3GPP access paths.

[0264] Method embodiment 7: The method of method embodiment 1, wherein the path switching capability information in the registration acceptance message indicates that the identified AMF (222) supports path switching of MA PDU sessions between N3GPP access paths.

[0265] Method embodiment 8: The method of method embodiment 7, wherein the initial registration request message includes path switching capability information indicating whether the first UE device supports path switching of MA PDU sessions between N3GPP access paths.

[0266] Method embodiment 8A. The method of method embodiment 8, wherein the path switching capability information in the initial registration request message indicates that the first UE device supports path switching of MA PDU sessions between N3GPP access paths.

[0267] The method of method embodiment 9 and method embodiment 7 also includes: operating (1408) the first UE device to participate in a first MAPDU session, wherein the participation includes communication through a first path (first access path), and the first path includes a first N3GPP access device (e.g., AP 212); operating (1410) the first UE device to implement a path switching of the first MA PDU session from the first path to a second path (second access path), and the second path includes a second N3GPP access device (e.g., TNAP218); and operating (1412) the first UE device to continue to participate in the first MA PDU session, and the continued participation in the first MA PDU session includes communication through the second path.

[0268] Method embodiment 10: The method of method embodiment 9, wherein the identified AMF (222) supports path switching between the first and second paths.

[0269] Second Numbered List of Exemplary Apparatus Embodiments:

[0270] Apparatus embodiment 1, a first user equipment (UE) device (202 or 400 or 951), comprising: a wireless transmitter (426 or 440 or 454); a wireless receiver (424 or 438 or 452); and a processor (402), configured to: operate (1404) the first UE device to a first network interface device (303) (e.g., a 3GPP next generation radio access network (NG-RAN) device (e.g., a gNB base station), a non-3GPP interworking function (N3IWF), or a trusted network gateway function (TNGF) )) sends a first message, the first message including an initial registration request message; and operation (1406) the first UE device (in response to the initial registration request) receives a registration acceptance message, the registration acceptance message including the GUAMI of the AMF (221 or 222) that identifies the AMF (221 or 222) selected to support the communication session of the first UE device, and including AMF path switching capability information indicating the path switching support capability of the identified AMF (i.e., the AMF identified by the GUAMI included in the registration acceptance message).

[0271] Apparatus embodiment 1A, the first UE device of apparatus embodiment 1, wherein the initial registration request message includes path switching capability information indicating whether the first UE device supports path switching of MA PDU sessions between N3GPP access paths.

[0272] Apparatus embodiment 2, the first UE device of apparatus embodiment 1, wherein the first network interface device (303) is a 3GPP next generation radio access network (NG-RAN) device, such as a gNB base station.

[0273] Apparatus embodiment 3, the first UE device of apparatus embodiment 1, wherein the first network interface device (303) is a non-3GPP interworking function (N3IWF) (214).

[0274] Apparatus embodiment 4: the first UE device of apparatus embodiment 1, wherein the first network interface device (303) is a trusted network gateway function (TNGF) (220).

[0275] Apparatus embodiment 5, the first UE device of apparatus embodiment 1, wherein the AMF path switching capability information is conveyed via a mandatory field.

[0276] Apparatus embodiment 6, the first UE device of apparatus embodiment 1, wherein the path switching capability information in the registration acceptance message indicates that the identified AMF (221) does not support path switching of MA PDU sessions between N3GPP access paths.

[0277] Apparatus embodiment 7, the first UE device of apparatus embodiment 1, wherein the path switching capability information in the registration acceptance message indicates that the identified AMF (222) supports path switching of MA PDU sessions between N3GPP access paths.

[0278] Apparatus embodiment 8, the UE device of apparatus embodiment 7, wherein the initial registration request message includes path switching capability information indicating whether the first UE device supports path switching of MA PDU sessions between N3GPP access paths.

[0279] Apparatus embodiment 8A, UE device of apparatus embodiment 8, wherein the path switching capability information in the initial registration request message indicates that the first UE device supports path switching of MA PDU sessions between N3GPP access paths.

[0280] The first UE device of apparatus embodiment 9 and apparatus embodiment 7, wherein the processor (402) is further configured to: operate (1408) the first UE device to participate in a first MA PDU session, wherein the participation includes communication through a first path (first access path), wherein the first path includes a first N3GPP access device (e.g., AP 212); operate (1410) the first UE device to implement a path switch of the first MA PDU session from the first path to a second path (second access path), wherein the second path includes a second N3GPP access device (e.g., TNAP 218); and operate (1412) the first UE device to continue to participate in the first MA PDU session, wherein the continued participation in the first MA PDU session includes communication through the second path.

[0281] The first UE device of apparatus embodiment 10 and apparatus embodiment 9, wherein the identified AMF (222) supports path switching between the first and second paths.

[0282] Fourth Numbered List of Exemplary Non-Transitory Computer Readable Medium Embodiments:

[0283] Non-transitory computer-readable medium embodiment 1. A non-transitory computer-readable medium (412) comprising computer-executable instructions, wherein the computer-executable instructions, when executed by a processor (402) of a first user equipment (UE) device (202 or 400 or 951), cause the first UE device to implement the following steps: operate (1404) the first UE device (via a wireless transmitter) to send a first network interface device (303) (e.g., a 3GPP next generation radio access network (NG-RAN) device (e.g., a gNB base station), a non-3GPP interworking function (N3IWF), or a trusted network The method further comprises: sending a first message to a wireless network gateway function (TNGF) including an initial registration request message; and operation (1406) the first UE device (in response to the initial registration request) receiving (through a wireless receiver) a registration acceptance message, the registration acceptance message including a GUAMI of an AMF (221 or 222) identifying the AMF (221 or 222) selected to support the communication session of the first UE device, and including AMF path switching capability information indicating the path switching support capability of the identified AMF (i.e., the AMF identified by the GUAMI included in the registration acceptance message).

[0284] Various embodiments relate to apparatuses, such as UEs, access points, devices including AMFs, devices including UDMs, devices including SMFs, devices including PCFs, devices including UPFs, servers, devices including N3IWFs, devices including TNGFs, base stations, such as sector base stations supporting beamforming (such as gNBs, ng-eNBs, eNBs, etc.), UEs, base stations supporting massive MIMO (such as CBSDs supporting massive MIMO), network management nodes, access points (APs), such as WiFi APs, base stations such as NRU gNB base stations, user devices such as stations (STAs), such as WiFi STAs, user equipment (UE) devices, LTE LAA devices, various types of RLAN devices, etc., other network communication devices such as routers and switches, mobile network operator (MNO) base stations (macro cell base stations and small cell base stations), such as evolved Node Bs (eNBs), gNBs or ng-eNBs, mobile virtual network operators (MVNO) base stations such as civil broadband radio service devices (CBSDs), network nodes, MNOs and MVNOs HSS equipment, relay equipment, such as mobility management entity (MME), AFC system, access and mobility management function (AMF) equipment, server, customer premises equipment, cable TV system, network node, gateway, cable TV head end and / or hub site, network monitoring node and / or server, cluster controller, cloud node, production node, cloud service server and / or network equipment. Various embodiments also relate to methods, such as methods for controlling and / or operating the following: UE, access point, device including AMF, device including UDM, device including SMF, device including PCF, device including UPF, server, device including N3IWF, device including TNGF, base station, such as sector base station supporting beamforming (such as gNB, ng-eNB, eNB, etc.), UE, base station supporting massive MIMO (such as CBSD supporting massive MIMO), network management node, access point (AP), such as WiFi AP, base station such as NRU gNB base station, user equipment such as station (STA), such as WiFi STA, user equipment (UE) device, LTE LAA device, various types of RLAN equipment, network communication equipment such as routers, switches, user equipment, base station, such as eNB and CBSD, gateway, server (HSS server), MME, AFC system, cable TV network, cloud network, node, server, cloud service server, customer premises equipment device, controller, network monitoring node and / or server and / or cable TV or network equipment device. Various embodiments relate to communication networks as partners, such as an MVNO network and an MNO network.Various embodiments also relate to a machine, such as a computer-readable medium, such as a ROM, RAM, CD, hard disk, etc., which includes machine-readable instructions for controlling the machine to implement one or more method steps. The computer-readable medium is, for example, a non-transitory computer-readable medium.

[0285] It should be understood that the specific order and hierarchy of steps in the disclosed processes and methods are examples of exemplary methods. Based on design preferences, it should be understood that the specific order or hierarchy of steps in the processes and methods can be rearranged while remaining within the scope of the present disclosure. The attached method claims present the elements of the various steps in a sample order, but should not be limited to the specific order or hierarchy presented. In some embodiments, one or more processors are used to implement one or more steps of each described method.

[0286] In various embodiments, one or more processors are used to implement each method step or element. In some embodiments, a hardware circuit is used to implement each element or step.

[0287] In various embodiments, one or more components are used to implement the nodes and / or elements described herein to implement the steps corresponding to one or more methods, such as message reception, message generation, signal generation, signal processing, sending, comparison, determination and / or transmission steps. Therefore, various features are implemented using components in some embodiments, or various features are implemented using logic such as logic circuits in some embodiments. Such components can be implemented using software, hardware, or a combination of software and hardware. Equipment can and sometimes is implemented as a collection of separate units or processors that work together to implement the functions assigned to equipment. In some embodiments, one or more functions of equipment can be implemented using a cloud-based processing system.

[0288] Many of the methods or method steps described above can be implemented using machine-executable instructions (such as software) included in a machine-readable medium (such as a memory device such as a RAM, a floppy disk, etc.) to control a machine (such as a general-purpose computer with or without additional hardware) to implement all or part of the methods described above, for example, in one or more nodes. Accordingly, various embodiments particularly relate to a machine-readable medium, such as a non-transitory computer-readable medium, including machine-executable instructions, which are used to cause a machine (such as a processor and associated hardware) to implement one or more steps of the method (s) described above. Some embodiments relate to devices, such as UE, access points, devices including AMF, devices including UDM, devices including SMF, devices including PCF, devices including UPF, servers, devices including N3IWF, devices including TNGF, base stations, such as sector base stations supporting beamforming (such as gNB, ng-eNB, eNB, etc.), UE, base stations supporting massive MIMO (such as CBSD supporting massive MIMO), network management devices, access points (APs), such as WiFi APs, base stations such as NRU gNB base stations, user devices such as stations (STAs), such as WiFi STAs, user equipment (UE) devices, LTE LAA devices, etc., RLAN devices, other network communication devices, network communication devices such as routers and switches, MVNO base stations such as CBRS base stations, such as CBSDs, devices such as cellular base stations, such as eNBs, MNO HSS servers, MVNO HSS servers, UE devices, relay devices, such as MMEs, AFC systems, etc., and the devices include processors configured to implement one, multiple or all steps of one or more methods of the present invention.

[0289] In some embodiments, one or more processors (e.g., CPUs) of one or more devices are configured to implement the method steps described as being implemented by a communication node (e.g., a controller), and the devices are, for example, UEs, access points, devices including AMFs, devices including UDMs, devices including SMFs, devices including PCFs, devices including UPFs, servers, devices including N3IWFs, devices including TNGFs, base stations, for example, sector base stations supporting beamforming (such as gNBs, ng-eNBs, eNBs, etc.), UEs, base stations supporting massive MIMO (such as CBSDs supporting massive MIMO), network management devices, communication nodes, such as access points (APs), for example, WiFi APs, base stations such as NRU gNB base stations, user devices such as stations (STAs), for example, WiFi STAs, user equipment (UE) devices, LTE LAA devices, etc., various RLAN devices, network communication devices such as routers and switches, MVNO base stations such as CBRS base stations, for example, CBSDs, devices such as cellular base stations, for example, eNBs, MNO HSS servers, MVNO HSS servers, UE devices, relay devices, for example, MMEs, AFC systems. Configuration of the processor may be achieved using one or more components (eg, software components) to control the processor configuration and / or by including hardware (eg, hardware components) in the processor to perform the steps and / or control the processor configuration.

[0290] Accordingly, some but not all embodiments relate to a device including components corresponding to each of one or more steps of the various described methods implemented by a device including a processor therein, such as a UE, an access point, a device including an AMF, a device including a UDM, a device including an SMF, a device including a PCF, a device including a UPF, a server, a device including an N3IWF, a device including a TNGF, a base station, such as a sector base station supporting beamforming (such as a gNB, ng-eNB, eNB, etc.), a UE, a base station supporting massive MIMO (such as a CBSD supporting massive MIMO), a network management device, an access point (AP), such as a WiFi AP, a base station such as an NRU gNB base station, a user device such as a station (STA), such as a WiFi STA, a user equipment (UE) device, an LTE LAA device, etc., an RLAN device, a network communication device such as a router, a switch, etc., an administrator device, a security device, an MVNO base station such as a CBRS base station, such as a CBSD, a device such as a cellular base station, such as an eNB, an MNO HSS server, an MVNO HSS server, a UE device, a relay device, such as an MME. In some but not all embodiments, the device includes a controller corresponding to each step of the various described methods implemented by a device including a processor therein, wherein the device is, for example, a communication node, such as a UE, an access point, a device including an AMF, a device including a UDM, a device including an SMF, a device including a PCF, a device including a UPF, a server, a device including an N3IWF, a device including a TNGF, a base station, such as a sector base station supporting beamforming (such as a gNB, ng-eNB, eNB, etc.), a UE, a base station supporting massive MIMO (such as a CBSD supporting massive MIMO), a network management device, an access point (AP), such as a WiFi AP, a base station such as an NRU gNB base station, a user device such as a station (STA), such as a WiFi STA, a user equipment (UE) device, an LTE LAA device, etc., an RLAN device, a router, a switch, etc., an administrator device, a security device, an AFC system, an MVNO base station such as a CBRS base station, such as a CBSD, a device such as a cellular base station, such as an eNB, an MNO HSS server, an MVNO HSS device server, a UE device, a relay device, such as an MME. The components may be implemented using software and / or hardware.

[0291] Some embodiments relate to a computer program product including a computer-readable medium (eg, a non-transitory computer-readable medium) including code for causing one or more computers to implement various functions, steps, actions, and / or operations (eg, one or more of the steps described above).

[0292] Depending on the embodiment, the computer program product may and sometimes includes different codes for implementing each step. Therefore, the computer program product may and sometimes includes a code for each individual step of a method (e.g., a control method of a controller or a node). The code may be in the form of a machine (e.g., a computer) executable instruction stored on a computer-readable medium, and the computer-readable medium is, for example, a non-transient computer-readable medium, such as a RAM (random access memory), a ROM (read-only memory), or other types of storage devices. In addition to relating to a computer program product, some embodiments also relate to one or more processors configured to implement the various functions, steps, actions, and / or operations of one or more of the methods described above. Accordingly, some embodiments relate to a processor, such as a CPU, configured to implement some or all steps of the method described herein. The processor may be used in, for example, UE, access point, device including AMF, device including UDM, device including SMF, device including PCF, device including UPF, server, device including N3IWF, device including TNGF, base station, for example, sector base station supporting beamforming (such as gNB, ng-eNB, eNB, etc.), UE, base station supporting massive MIMO (such as CBSD supporting massive MIMO), network management device or device, communication device such as communication node, such as UE, access point, device including AMF, device including UDM, device including SMF, device including PCF, device including UPF, server, device including N3IWF, device including TNGF, access point (AP), for example, WiFi AP, base station such as NRU gNB base station, user equipment such as station (STA), for example, WiFi STA, user equipment (UE) device, LTE LAA devices, etc., RLAN devices, network communication devices such as routers, switches, etc., manager devices, MVNO base stations, such as CBSD, MNO cellular base stations, such as eNB or gNB, UE devices or other devices described in this application. In some embodiments, the components are implemented as hardware devices, in which case the components are hardware components. In other embodiments, the components may be implemented as software, such as a processor or a collection of computer executable instructions. Depending on the embodiment, the components may be all-hardware components, all-software components, a combination of hardware and / or software, or in some embodiments, some components are hardware components and other components are software components.

[0293] The methods and procedures used herein for the UE (102) and the PLMN (156) may also be applied to the case where the first path #1 passes through a standalone non-public network (SNPN) core network (CN), such as a network operated by a non-public network (NPN) operator and not dependent on network functions provided by the PLMN. In such a case, since the UE 102 communicates with the N3IWF 114 in the PLMN through the SNPN CN, the SNPN CN is treated similarly to an untrusted WiFi access point (e.g., similar to N3GPP access #A 106).

[0294] The method and apparatus are well suited for use with both trusted and untrusted N3GPP access networks and can be used to use such networks in combination with a PLMN to support MA PDU sessions.

[0295] According to the foregoing description, those skilled in the art will recognize many other variations of the methods and devices of the various embodiments described above. Such variations should be considered to fall within the scope of the present invention. According to the foregoing description and the appended claims, those skilled in the art will recognize many other embodiments within the scope of the present invention. Such variations should be considered to fall within the scope of the present invention.

Claims

1. A communication method, the method comprising: operating a network interface device to receive a first message from a first user equipment (UE), the first message comprising an initial registration request message; as well as The network interface device is operated to send a registration acceptance message to the first UE, wherein the registration acceptance message includes a globally unique AMF identifier (GUAMI) identifying the access and mobility management function (AMF) selected to support the communication session of the first UE, and includes AMF path switching capability information indicating the path switching support capability of the identified AMF.

2. The method according to claim 1, wherein: The path switching capability information in the registration accept message indicates that the identified AMF does not support path switching of multiple access protocol data unit (MA PDU) sessions between non-3GPP (N3GPP) access paths.

3. The method according to claim 2, wherein: The path switching capability information in the registration accept message indicates that the identified AMF supports path switching of MA PDU sessions between N3GPP access paths.

4. The method according to claim 3, further comprising: The operation identifies the AMF to receive an initiate MA PDU session establishment message from the first UE.

5. The method according to claim 4, further comprising: The operation identifies the AMF and selects a session management function (SMF) that supports path switching of MA PDU sessions between N3GPP access paths to support communication with the first UE.

6. The method according to claim 5, further comprising: The operation identifies the AMF and sends a create session management (SM) context request to the selected SMF to create an SM context for the first UE at the selected SMF.

7. The method according to claim 6, wherein: Sending the create SM content request is sent by the selected SMF as part of establishing an MA PDU session for the first UE in response to an initiate MA PDU session establishment message received from the first UE.

8. The method according to claim 7, further comprising: Another network interface device is operated to communicate with the UE via the MA PDU path established in response to the initiate MA PDU session establishment message.

9. A communication system comprising: Network interface devices, including: a first receiver; a first transmitter; and The first processor is configured to: operating a network interface device to receive a first message from a first user equipment (UE), the first message comprising an initial registration request message; and The network interface device is operated to send a registration acceptance message to the first UE, wherein the registration acceptance message includes a GUAMI of an AMF that identifies the AMF selected as the AMF supporting the communication session of the first UE, and includes AMF path switching capability information indicating the path switching support capability of the identified AMF.

10. The communication system according to claim 9, wherein: The path switching capability information in the registration accept message indicates that the identified AMF does not support path switching of MA PDU sessions between N3GPP access paths.

11. The communication system according to claim 10, wherein: The path switching capability information in the registration accept message indicates that the identified AMF supports path switching of MA PDU sessions between N3GPP access paths.

12. The communication system according to claim 11, further comprising: The identified AMF includes: a second receiver; and The second processor is configured as follows: The operation identifies the AMF to receive an initiate MA PDU session establishment message from the first UE.

13. The communication system according to claim 12, wherein: The second processor is further configured to: The AMF identified by the operation selects an SMF that supports path switching of MA PDU sessions between N3GPP access paths to support communication with the first UE.

14. The communication system according to claim 13, wherein: The identified AMF also includes a second transmitter; and Wherein, the second processor is further configured to: The operation identifies the AMF and sends a create session management (SM) context request to the selected SMF to create an SM context for the first UE at the selected SMF.

15. The communication system according to claim 14, wherein: Sending the create SM content request is sent by the selected SMF as part of establishing an MA PDU session for the first UE in response to an initiate MA PDU session establishment message received from the first UE.

16. A method of operating a first user equipment (UE) device, the method comprising: Operate the first UE device to send a first message to the first network interface device, wherein the first message includes an initial registration request message; as well as The first UE device is operated to receive a registration acceptance message, wherein the registration acceptance message includes a GUAMI of an AMF that identifies the AMF selected as the AMF supporting the communication session of the first UE device, and includes AMF path switching capability information indicating the path switching support capability of the identified AMF.

17. The method according to claim 16, wherein: The initial registration request message includes path switching capability information indicating whether the first UE device supports path switching of the MA PDU session between N3GPP access paths.

18. The method according to claim 16, wherein: The first network interface device is a 3GPP Next Generation Radio Access Network (NG-RAN) device, such as a gNB base station.

19. The method according to claim 16, wherein: The first network interface device is a non-3GPP interworking function (N3IWF).

20. The method according to claim 16, wherein: The first network interface device is a Trusted Network Gateway Function (TNGF).

21. The method according to claim 16, wherein: The AMF path switching capability information is conveyed through a mandatory field.

22. The method according to claim 16, wherein: The path switching capability information in the registration accept message indicates that the identified AMF does not support path switching of MA PDU sessions between N3GPP access paths.

23. The method according to claim 16, wherein: The path switching capability information in the registration accept message indicates that the identified AMF supports path switching of MA PDU sessions between N3GPP access paths.

24. The method according to claim 23, wherein: The initial registration request message includes path switching capability information indicating whether the first UE device supports path switching of the MA PDU session between N3GPP access paths.

25. The method of claim 23, further comprising: Operating a first UE device to participate in a first MA PDU session, the participation comprising communication via a first path, the first path comprising a first N3GPP access device; Operate the first UE device to implement a path switch of the first MA PDU session from a first path to a second path, where the second path includes a second N3GPP access device; as well as The first UE device is operated to continue to participate in the first MA PDU session, wherein the continued participation in the first MA PDU session includes communication through the second path.

26. A first user equipment (UE) device, comprising: Wireless transmitter; Wireless receiver; as well as The processor is configured as: Operate the first UE device to send a first message to the first network interface device, wherein the first message includes an initial registration request message; as well as The first UE device is operated to receive a registration acceptance message, wherein the registration acceptance message includes a GUAMI of an AMF that identifies the AMF selected as the AMF supporting the communication session of the first UE device, and includes AMF path switching capability information indicating the path switching support capability of the identified AMF.

27. The first UE device according to claim 26, wherein: The initial registration request message includes path switching capability information indicating whether the first UE device supports path switching of the MA PDU session between N3GPP access paths.

28. The first UE device according to claim 26, wherein: The path switching capability information in the registration accept message indicates that the identified AMF supports path switching of MA PDU sessions between N3GPP access paths.

29. The UE device according to claim 28, wherein: The initial registration request message includes path switching capability information indicating whether the first UE device supports path switching of the MA PDU session between N3GPP access paths.

30. The first UE device according to claim 28, wherein: The processor is further configured to: Operating a first UE device to participate in a first MA PDU session, the participation comprising communication via a first path (first access path), the first path comprising a first N3GPP access device; Operate the first UE device to implement a path switch of the first MA PDU session from a first path to a second path, where the second path includes a second N3GPP access device; as well as The first UE device is operated to continue to participate in the first MA PDU session, wherein the continued participation in the first MA PDU session includes communication through the second path.

Images