Method for handling slices for evolved packet data gateway Wi-Fi access

Abstract

Methods, systems, and apparatus for wireless communications are described. A user equipment (UE) may establish a cellular connection with a base station associated with a cellular radio network. The UE may receive an access policy of the cellular radio network, the access policy identifying an access preference rule for the UE to employ for connecting to a core network function of the cellular radio network, the access preference rule indicating to the UE that connection to the core network function is preferably via a non-cellular radio network. The UE may determine that a gateway between the non-cellular radio network and the core network function of the cellular radio network is not configured. The UE may determine that a gateway selection policy for the cellular radio network is not configured. The UE may establish a connection to a legacy core network function of a legacy cellular radio network via a legacy gateway.

Description

[0001] Cross-references

[0002] This patent application claims the benefit of U.S. non-provisional patent application No. 17 / 230,502, filed by Zhang et al. on April 14, 2021, entitled “METHODS TO HANDLESLICING ACCOUNTING FOR EVOLVED PACKET DATA GATEWAY WI-FI ACCESS,” and U.S. provisional patent application No. 63 / 011,854, filed by Zhang et al. on April 17, 2020, entitled “METHODS TO HANDLE SLICING ACCOUNTINGFOR EVOLVED PACKET DATA GATEWAY WI-FI ACCESS,” each of which is assigned to the assignee of this application. Technical Field

[0003] The following relates generally to wireless communications and, more particularly, to methods for handling slicing for Evolved Packet Data Gateway (Wi-Fi) access.

[0004] background

[0005] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcast, and the like. These systems may be able to support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth generation (4G) systems (such as long term evolution (LTE) systems, advanced LTE (LTE-A) systems, or LTE-A Pro systems), and fifth generation (5G) systems, which may be referred to as new radio (NR) systems. These systems may employ various technologies, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal frequency division multiple access (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations or one or more network access nodes, each base station or network access node simultaneously supporting communication with multiple communication devices, which may be further referred to as user equipment (UE).

[0006] Overview

[0007] The described technology relates to improved methods, systems, devices, and apparatuses for supporting methods for handling slices that account for evolved packet data gateway Wi-Fi access. In general, the described technology provides various mechanisms for resolving inconsistencies between legacy cellular radio networks and advanced cellular radio networks being deployed. That is, various aspects of the described technology provide mechanisms that can be implemented by user equipment (UE) operating in a heterogeneous environment, the heterogeneous environment including at least one of: a non-cellular radio network (e.g., a Wi-Fi network), a legacy cellular radio network (e.g., such as a fourth generation (4G) cellular radio network, a fifth generation (5G) new radio (NR) non-standalone (NSA) cellular radio network, etc.) and / or a 5G NR standalone (SA) cellular radio network.

[0008] For example, a UE may establish a connection with a base station associated with a cellular radio network (e.g., a 5G NR SA connection). Upon establishing a connection with a base station, the base station may generally configure, instruct, or otherwise communicate various policies, protocols, and the like for the cellular radio network to the UE. Accordingly, the UE may receive an access policy (e.g., a UE routing selection policy (URSP)) that identifies access preference rules for the UE to use to connect to a core network function of the cellular radio network (e.g., for connecting to a 5G core network (5GC)). That is, the URSP may generally indicate whether the UE is to preferentially route outgoing traffic (e.g., traffic may be routed to an established protocol data unit (PDU) session (e.g., to the 5GC via a 5G NR SA base station), offloaded to a non-3rd Generation Partnership Project (3GPP) cellular connection (e.g., via a Wi-Fi network)), or establish a new PDU session (e.g., a new PDU session with the 5GC via a 5G NR SA base station). In this example, the URSP may indicate to the UE that it prefers to connect to the 5GC via a non-cellular radio network, for example, by routing outgoing traffic in a PDU session via a Wi-Fi network. However, the UE may determine that a gateway (3GPP Networking Function (N3IWF) gateway) between the Wi-Fi radio network and the 5GC is not configured or is unavailable for some other reason. The UE may also determine that a gateway selection policy (e.g., an Access Network Discovery Selection Policy (ANDSP)) is not configured for 5G NR SA. Broadly speaking, ANDSP is used by the UE to select non-3GPP access networks, such as wireless local area networks (WLANs), Wi-Fi networks, and the like. Consequently, the UE may establish a connection to a legacy core network function (e.g., an Evolved Packet Data Gateway (EPDG)) of a legacy cellular radio network (e.g., a 4G and / or 5G NR NSA cellular radio network) via a legacy gateway (e.g., an Evolved Packet Data Gateway (EPDG)). Broadly speaking, the EPDG may be a gateway between the Wi-Fi network and the EPC. Thus, even though the URSP gives a preference for Wi-Fi networks and the ANDSP and N3IWF are not configured or otherwise unavailable, the UE can still connect to the EPC core network using the EPDG following the URSP access policy when the ANDSP / N3IWF has not yet been configured for the 5G NR SA cellular radio network.

[0009] Additionally or alternatively, the UE may have already established a cellular connection with a base station in a 5G NR SA cellular radio network. However, in this example, the URSP received by the UE may indicate a preference for a 3GPP connection, for example, for the UE to route outgoing traffic to the 5G NR SA cellular radio network. That is, the URSP may indicate a preference for the UE to connect to the 5GC via a 5G NR SA base station. However, the UE may determine that neither the N3IWF gateway nor the ANDSP gateway selection policy is configured for a cellular radio network (e.g., for a 5G NR SA cellular radio network). Subsequently, the UE may determine that the 5G NR SA cellular radio network has become unavailable, but the Wi-Fi radio network is available. In response, the UE may establish a connection to a legacy core network function (e.g., EPC) of a legacy cellular radio network (e.g., 4G / 5G NR NSA) via a legacy gateway (e.g., EPDG). The UE may identify or otherwise determine a legacy access policy (e.g., an Access Network Discovery and Selection Function (ANDSF)) that gives a preference for the UE to use a non-cellular radio network (e.g., a Wi-Fi network). That is, in a broad sense, the ANDSF helps the UE discover non-3GPP access networks, such as WLAN, Wi-Fi networks, and the like. However, the UE may determine that a 5G NR SA cellular radio network has become available again and may therefore establish a new connection to the cellular radio network. That is, even if the ANDSF instructs the UE to give a preference for a Wi-Fi network, the UE will follow the preference given in the URSP and re-establish its connection to the 5G NR NSA cellular radio network when the 5G NR SA network becomes available again. Otherwise, the UE may be stuck on a Wi-Fi connection even if a more advanced 5G NR SA network is available.

[0010] Additionally or alternatively, the UE may establish a cellular connection to a 5G NR SA cellular radio network and receive a URSP that, in this example, prefers a non-cellular radio network (e.g., a non-3GPP network such as a Wi-Fi network). Similarly, the UE may determine that neither the ANDSP nor the N3IWF is configured for the 5G NR SA cellular radio network, but that a Wi-Fi network is available. Therefore, the UE may establish a connection to the EPC legacy core network function of the 4G / 5G NR NSA legacy cellular radio network via the EPDG gateway. The UE may receive or otherwise identify an ANDSF legacy access policy that, in this example, prefers a 3GPP connection. Previously, the UE would switch back and forth between a 5G NR SA connection and a Wi-Fi connection. However, to avoid this switching, the UE may maintain a connection to the EPC legacy core network function via the EPDG legacy gateway. This approach prevents the UE from frequently switching between a 5G NR SA network, where the URSP prefers a non-3GPP connection, and a Wi-Fi network, where the ANDSF prefers a 3GPP connection.

[0011] Additionally or alternatively, the UE may establish a connection to the EPC legacy core network function of the 4G / 5G NR NSA legacy cellular radio network via an EPDG legacy gateway. The UE may be configured with a set of traffic descriptors (e.g., the UE may have different applications operating on the UE). For each traffic descriptor set (e.g., each application), the UE may identify an ANDSF legacy access policy that indicates a preference for the UE to connect via a cellular radio network (e.g., a 3GPP cellular radio network) or a non-cellular radio network (e.g., a non-3GPP radio network). The UE may also identify or otherwise determine the legacy slice handling associated with each traffic descriptor, for example, based at least in part on the connection to the EPC via the EPDG. The UE may establish a connection to the 5GC core network function of the 5G NR SA cellular radio network via the N3IWF gateway. Accordingly, the UE may receive or otherwise identify a URSP access policy for the UE to employ, which also informs the UE whether to prefer connecting via a cellular radio network or a non-cellular radio network. The UE may also determine or otherwise identify the slice handling for each traffic descriptor based, for example, at least in part on the URSP access policy, the traffic descriptor identifier, the traffic descriptor type, etc. Thus, the UE may use the URSP access policy, the legacy slice handling (from the EPC), and / or the slice handling (from the 5GC) to determine whether to transfer the connection for each traffic descriptor from the EPC via the EPDG gateway to the 5GC via the N3IWF or to establish an updated connection with the 5GC via the N3IWF. Thus, the UE may ensure that each traffic descriptor is given the appropriate slice handling and / or connection preference when switching from the EPC connection to the 5GC connection.

[0012] A method of wireless communication at a UE is described. The method may include establishing a cellular connection with a base station associated with a cellular radio network. The method may also include receiving an access policy of the cellular radio network, the access policy identifying an access preference rule for the UE to employ for connecting to a core network function of the cellular radio network, the access preference rule indicating to the UE that connection to the core network function is preferably via a non-cellular radio network. The method may include determining that a gateway between the non-cellular radio network and the core network function of the cellular radio network is not configured and determining that a gateway selection policy for the cellular radio network is not configured. The method may further include establishing a connection to a legacy core network function of the legacy cellular radio network via a legacy gateway between the non-cellular radio network and the legacy core network function based at least in part on the access preference rule, the non-configuration of the gateway, and the non-configuration of the gateway selection policy.

[0013] An apparatus for wireless communication at a UE is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions are executable by the processor to cause the apparatus to establish a cellular connection with a base station associated with a cellular radio network and receive an access policy of the cellular radio network, the access policy identifying an access preference rule for the UE to use for connecting to a core network function of the cellular radio network, the access preference rule indicating to the UE that connection to the core network function is preferably via a non-cellular radio network. The instructions are executable by the processor to cause the apparatus to determine that a gateway between the non-cellular radio network and the core network function of the cellular radio network is not configured and to determine that a gateway selection policy for the cellular radio network is not configured. The instructions are also executable by the processor to cause the apparatus to establish a connection to a legacy core network function of a legacy cellular radio network via a legacy gateway between the non-cellular radio network and the legacy core network function based at least in part on the access preference rule, the non-configured gateway, and the non-configured gateway selection policy.

[0014] Another apparatus for wireless communication at a UE is described. The apparatus may include means for establishing a cellular connection with a base station associated with a cellular radio network and means for receiving an access policy of the cellular radio network, the access policy identifying an access preference rule for the UE to employ for connecting to a core network function of the cellular radio network, the access preference rule indicating to the UE that connection to the core network function is preferably via a non-cellular radio network. The apparatus may also include means for determining that a gateway between the non-cellular radio network and the core network function of the cellular radio network is not configured and means for determining that a gateway selection policy for the cellular radio network is not configured. The apparatus may also include means for establishing a connection to a legacy core network function of a legacy cellular radio network via a legacy gateway between the non-cellular radio network and the legacy core network function of the legacy cellular radio network based at least in part on the access preference rule, the non-configuration of the gateway, and the non-configuration of the gateway selection policy.

[0015] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions executable by a processor to establish a cellular connection with a base station associated with a cellular radio network and receive an access policy of the cellular radio network, the access policy identifying an access preference rule for the UE to use for connecting to a core network function of the cellular radio network, the access preference rule indicating to the UE that connection to the core network function is preferably via a non-cellular radio network. The code may also include instructions executable by the processor to determine that a gateway between the non-cellular radio network and the core network function of the cellular radio network is not configured. The code may also include instructions executable by the processor to determine that a gateway selection policy of the cellular radio network is not configured. The code may also include instructions executable by the processor to establish a connection to a legacy core network function of a legacy cellular radio network via a legacy gateway between the non-cellular radio network and the legacy core network function based at least in part on the access preference rule, the non-configuration of the gateway, and the non-configuration of the gateway selection policy.

[0016] Some examples of the methods, devices (apparatus), and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for receiving a configuration for connection via a non-cellular radio network, the configuration configuring the UE to connect to a legacy core network function or to a core network function via the non-cellular radio network.

[0017] Some examples of the methods, devices (apparatus), and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for receiving a configuration for connection via a non-cellular radio network, the configuration configuring the UE to attempt to connect to a core network function and to connect to a legacy core network function via the non-cellular radio network if the attempt to connect to the core network may be unsuccessful.

[0018] In some examples of the methods, devices, and non-transitory computer-readable media described herein, the cellular radio network includes a 5G NR SA cellular radio network, the legacy cellular radio network includes at least one of a 4G LTE cellular radio network or a 5G NR NSA cellular radio network, the access policy includes a URSP, the gateway selection policy includes an ANDSP, the gateway includes an N3IWF between a core network function of the 5G NR SA cellular radio network and a non-cellular radio network, and the legacy gateway includes an EPC core network function of the 4G LTE cellular radio network or the 5G NR NSA cellular radio network and an EPDG between the non-cellular radio network.

[0019] Another method of wireless communication at a UE is described. The method may include establishing a cellular connection with a base station associated with a cellular radio network and receiving an access policy of the cellular radio network, the access policy identifying an access preference rule for the UE to employ for connecting to a core network function of the cellular radio network, the access preference rule indicating to the UE that connection to the core network function is preferably via the cellular radio network and via a gateway between the cellular radio network and the core network function. The method may also include determining that the gateway is not configured, determining that a gateway selection policy of the cellular radio network is not configured, and determining that a non-cellular radio network is available and that the cellular radio network has become unavailable. The method may also include establishing, via the non-cellular radio network, a connection to the legacy core network function via a legacy gateway between a legacy cellular radio network and the non-cellular radio network. The method may further include identifying a legacy access policy of the legacy cellular radio network, the legacy access policy identifying a legacy access preference rule for the UE to employ for connecting to the legacy core network function, the legacy access preference rule indicating to the UE that connection to the legacy core network function is preferred via a non-cellular radio network; determining that the cellular radio network has become available for establishing a new connection; and establishing the new connection to the cellular radio network based at least on the access preference rule.

[0020] An apparatus for wireless communication at a UE is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions are executable by the processor to cause the apparatus to establish a cellular connection with a base station associated with a cellular radio network and receive an access policy for the cellular radio network, the access policy identifying an access preference rule for the UE to employ for connecting to a core network function of the cellular radio network, the access preference rule indicating to the UE that connection to the core network function is preferably via the cellular radio network and via a gateway between the cellular radio network and the core network function. The instructions are also executable by the processor to cause the apparatus to determine that the gateway is not configured, that the gateway selection policy for the cellular radio network is not configured, and that a non-cellular radio network is available and that the cellular radio network has become unavailable. The instructions are executable by the processor to cause the apparatus to establish a connection to a legacy core network function of a legacy cellular radio network via a legacy gateway between the legacy core network function and the non-cellular radio network via the non-cellular radio network, and to identify a legacy access policy of the legacy cellular radio network, the legacy access policy identifying a legacy access preference rule for a UE to employ for connecting to the legacy core network function, the legacy access preference rule indicating to the UE that connection to the legacy core network function via the non-cellular radio network is preferred. The instructions are executable by the processor to cause the apparatus to determine that the cellular radio network has become available for establishing a new connection and to establish a new connection to the cellular radio network based at least on the access preference rule.

[0021] Another apparatus for wireless communication at a UE is described. The apparatus may include means for establishing a cellular connection with a base station associated with a cellular radio network and means for receiving an access policy of the cellular radio network, the access policy identifying an access preference rule for the UE to employ for connecting to a core network function of the cellular radio network, the access preference rule indicating to the UE that connection to the core network function is preferably made via the cellular radio network via a gateway between the cellular radio network and the core network function. The apparatus may also include means for determining that the gateway is not configured, means for determining that a gateway selection policy of the cellular radio network is not configured, and means for determining that a non-cellular radio network is available and that the cellular radio network has become unavailable. The apparatus may further include means for establishing a connection to a legacy core network function of a legacy cellular radio network via a legacy gateway between the legacy core network function and the non-cellular radio network via the non-cellular radio network, and means for identifying a legacy access policy of the legacy cellular radio network, the legacy access policy identifying a legacy access preference rule for the UE to adopt for connecting to the legacy core network function, the legacy access preference rule indicating to the UE that it is preferred to connect to the legacy core network function via the non-cellular radio network. The apparatus may include means for determining that a cellular radio network has become available for establishing a new connection and means for establishing the new connection to the cellular radio network based at least on the access preference rule.

[0022] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions executable by a processor to establish a cellular connection with a base station associated with a cellular radio network and receive an access policy for the cellular radio network, the access policy identifying an access preference rule for the UE to employ for connecting to a core network function of the cellular radio network, the access preference rule indicating to the UE that connection to the core network function is preferably via the cellular radio network and via a gateway between the cellular radio network and the core network function. The code may also include instructions executable by the processor to determine that the gateway is not configured, determine that a gateway selection policy for the cellular radio network is not configured, and determine that a non-cellular radio network is available and that the cellular radio network has become unavailable. The code may also include instructions executable by the processor for establishing a connection to a legacy core network function of a legacy cellular radio network via a legacy gateway between the legacy core network function and the non-cellular radio network, and identifying a legacy access policy of the legacy cellular radio network, the legacy access policy identifying a legacy access preference rule for the UE to adopt for connecting to the legacy core network function, the legacy access preference rule indicating to the UE that it is preferred to connect to the legacy core network function via the non-cellular radio network. The code may also include instructions executable by the processor for determining that the cellular radio network has become available for establishing a new connection and establishing a new connection to the cellular radio network based at least on the access preference rule.

[0023] Some examples of the methods, devices, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for determining, based at least in part on the new connection, that a gateway of the cellular radio network may be configured, and transferring, based at least in part on an access policy, a connection to a legacy core network function of the legacy cellular radio network via the legacy gateway to a core network function of the cellular radio network via the gateway.

[0024] Some examples of the methods, devices (apparatus), and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for receiving a configuration for connection via a non-cellular radio network, the configuration configuring the UE to connect to a legacy core network function or to a core network function via the non-cellular radio network.

[0025] Some examples of the methods, devices (apparatus), and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for receiving a configuration for connection via a non-cellular radio network, the configuration configuring the UE to attempt to connect to a core network function and to connect to a legacy core network function via the non-cellular radio network if the attempt to connect to the core network may be unsuccessful.

[0026] In some examples of the methods, devices, and non-transitory computer-readable media described herein, the cellular radio network includes a 5G NR SA cellular radio network, the legacy cellular radio network includes at least one of a 4G LTE cellular radio network or a 5G NR NSA cellular radio network, the access policy includes a URSP, the gateway selection policy includes an ANDSP, the legacy access policy includes an ANDSF, the gateway includes an N3IWF between a core network function of the 5G NR SA cellular radio network and a non-cellular radio network, and the legacy gateway includes an EPC core network function of the 4G LTE cellular radio network or the 5G NR NSA cellular radio network and an EPDG between the non-cellular radio network.

[0027] Another method of wireless communication at a UE is described. The method may include establishing a cellular connection with a base station associated with a cellular radio network and receiving an access policy of the cellular radio network, the access policy identifying an access preference rule for the UE to use for connecting to a core network function of the cellular radio network, the access preference rule indicating to the UE that connection to the core network function is preferably via a non-cellular radio network. The method may also include determining that a non-cellular radio network is available and a gateway between the non-cellular radio network and the core network function of the cellular radio network is not configured, and determining that a gateway selection policy of the cellular radio network is not configured. The method may also include establishing a connection to a legacy core network function of a legacy cellular radio network via a legacy gateway between the legacy core network function and the non-cellular radio network, and identifying a legacy access policy of the legacy cellular radio network, the legacy access policy identifying a legacy access preference rule for the UE to use for connecting to the legacy core network function, the legacy access preference rule indicating to the UE that connection to the legacy core network function is preferably via the legacy cellular radio network. The method may also include maintaining a connection to a legacy core network function of the legacy radio network via the legacy gateway based at least in part on the access preference rule.

[0028] Another apparatus for wireless communication at a UE is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions are executable by the processor to cause the apparatus to establish a cellular connection with a base station associated with a cellular radio network and receive an access policy of the cellular radio network, the access policy identifying an access preference rule for the UE to employ for connecting to a core network function of the cellular radio network, the access preference rule indicating to the UE that connection to the core network function is preferably via a non-cellular radio network. The instructions are also executable by the processor to cause the apparatus to determine that a non-cellular radio network is available and that a gateway between the non-cellular radio network and the core network function of the cellular radio network is not configured, determine that a gateway selection policy for the cellular radio network is not configured, and establish a connection to a legacy core network function of the legacy cellular radio network via a legacy gateway between the legacy core network function and the non-cellular radio network. The instructions are also executable by the processor to cause the apparatus to identify a legacy access policy for the legacy cellular radio network, the legacy access policy identifying a legacy access preference rule for the UE to employ for connecting to the legacy core network function, the legacy access preference rule indicating to the UE that connection to the legacy core network function is preferred via the legacy cellular radio network, and maintaining a connection to the legacy core network function of the legacy radio network via the legacy gateway based at least in part on the access preference rule.

[0029] Another apparatus for wireless communication at a UE is described. The apparatus may include means for establishing a cellular connection with a base station associated with a cellular radio network and means for receiving an access policy of the cellular radio network, the access policy identifying an access preference rule for the UE to employ for connecting to a core network function of the cellular radio network, the access preference rule indicating to the UE that connection to the core network function is preferably via a non-cellular radio network. The apparatus may include means for determining that a non-cellular radio network is available and that a gateway between the non-cellular radio network and the core network function of the cellular radio network is not configured, means for determining that a gateway selection policy for the cellular radio network is not configured, and means for establishing a connection to a legacy core network function of the legacy cellular radio network via a legacy gateway between the legacy core network function and the non-cellular radio network. The apparatus may include means for identifying a legacy access policy of a legacy cellular radio network, the legacy access policy identifying a legacy access preference rule for a UE to employ for connecting to a legacy core network function, the legacy access preference rule indicating to the UE that connection to the legacy core network function is preferably via the legacy cellular radio network; and means for maintaining a connection to the legacy core network function of the legacy radio network via the legacy gateway based at least in part on the access preference rule.

[0030] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions executable by a processor to establish a cellular connection with a base station associated with a cellular radio network and receive an access policy of the cellular radio network, the access policy identifying an access preference rule for the UE to employ for connecting to a core network function of the cellular radio network, the access preference rule indicating to the UE that connection to the core network function is preferably via a non-cellular radio network. The code may include instructions executable by the processor to determine that a non-cellular radio network is available and a gateway between the non-cellular radio network and a core network function of the cellular radio network is not configured, determine that a gateway selection policy for the cellular radio network is not configured, and establish a connection to a legacy core network function of the legacy cellular radio network via a legacy gateway between the legacy core network function and the non-cellular radio network. The code may include instructions executable by the processor to identify a legacy access policy for the legacy cellular radio network, the legacy access policy identifying a legacy access preference rule for a UE to employ for connecting to a legacy core network function, the legacy access preference rule indicating to the UE that connection to the legacy core network function is preferred via the legacy cellular radio network, and maintaining a connection to the legacy core network function of the legacy radio network via the legacy gateway based at least in part on the access preference rule.

[0031] Some examples of the methods, devices (apparatus), and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for receiving a configuration for connection via a non-cellular radio network, the configuration configuring the UE to connect to a legacy core network function or to a core network function via the non-cellular radio network.

[0032] Some examples of the methods, devices (apparatus), and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for receiving a configuration for connection via a non-cellular radio network, the configuration configuring the UE to attempt to connect to a core network function and to connect to a legacy core network function via the non-cellular radio network if the attempt to connect to the core network may be unsuccessful.

[0033] In some examples of the methods, devices, and non-transitory computer-readable media described herein, the cellular radio network includes a 5G NR SA cellular radio network, the access policy includes a URSP, the gateway selection policy includes an ANDSP, the legacy access policy includes an ANDSF, the gateway includes an N3IWF between a core network function of the 5G NR SA cellular radio network and a non-cellular radio network, and the legacy gateway includes an EPC core network function of a 4G LTE cellular radio network or a 5G NR NSA cellular radio network and an EPDG between the non-cellular radio network.

[0034] A method of wireless communication at a UE is described. The method may include establishing a connection to a legacy core network function of a legacy cellular radio network via a legacy gateway between the legacy cellular radio network and a non-cellular radio network; and identifying, for each traffic descriptor in a traffic descriptor set, a legacy access policy of the legacy cellular radio network, the legacy access policy identifying a legacy access preference rule for the UE to employ for connecting to the legacy core network function, each legacy access preference rule indicating to the UE whether to preferably connect to the legacy core network function via the legacy cellular radio network or the non-cellular radio network for the traffic descriptor and legacy slice handling for the traffic descriptor. The method may include establishing a connection to a core network function of a cellular radio network via a gateway between the cellular radio network and the non-cellular radio network; and identifying, for each traffic descriptor in a set of traffic descriptors, an access policy of the cellular radio network, the access policy identifying an access preference rule for a UE to employ for connecting to the core network function of the cellular radio network, each access preference rule indicating to the UE whether to preferably connect to the core network function via the cellular radio network or the non-cellular radio network for the traffic descriptor and the slicing processing of the traffic descriptor. The method may also include determining, for each traffic descriptor and based at least in part on the legacy slicing processing and the slicing processing and based at least in part on the access policy, whether to transfer a connection associated with the traffic descriptor to the core network function or to establish an updated connection for the traffic descriptor with the core network function.

[0035] An apparatus for wireless communication at a UE is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions are executable by the processor to cause the apparatus to establish a connection to a legacy core network function of a legacy cellular radio network via a legacy gateway between the legacy cellular radio network and a non-cellular radio network; and for each traffic descriptor in a traffic descriptor set, identify a legacy access policy of the legacy cellular radio network, the legacy access policy identifying a legacy access preference rule for the UE to adopt for connecting to the legacy core network function, each legacy access preference rule indicating to the UE whether to preferably connect to the legacy core network function via the legacy cellular radio network or the non-cellular radio network for the traffic descriptor and legacy slice processing for the traffic descriptor. The instructions are executable by the processor to cause the apparatus to establish a connection to a core network function of the cellular radio network via a gateway between the cellular radio network and the non-cellular radio network; and for each traffic descriptor in the traffic descriptor set, identify an access policy of the cellular radio network, the access policy identifying an access preference rule for the UE to employ for connecting to the core network function of the cellular radio network, each access preference rule indicating to the UE whether to preferably connect to the core network function via the cellular radio network or the non-cellular radio network for the traffic descriptor and the slice processing of the traffic descriptor. The instructions are executable by the processor to cause the apparatus to determine, for each traffic descriptor and based at least in part on the legacy slice processing and the slice processing and at least in part on the access policy, whether to transfer a connection associated with the traffic descriptor to the core network function or to establish an updated connection for the traffic descriptor with the core network function.

[0036] Another apparatus for wireless communication at a UE is described. The apparatus may include means for establishing a connection to a legacy core network function of a legacy cellular radio network via a legacy gateway between the legacy cellular radio network and a non-cellular radio network; and means for identifying, for each traffic descriptor in a traffic descriptor set, a legacy access policy of the legacy cellular radio network, the legacy access policy identifying a legacy access preference rule for the UE to employ for connecting to the legacy core network function, each legacy access preference rule indicating to the UE whether to preferably connect to the legacy core network function via the legacy cellular radio network or the non-cellular radio network for the traffic descriptor and legacy slice handling for the traffic descriptor. The apparatus may include means for establishing a connection to a core network function of a cellular radio network via a gateway between the cellular radio network and the non-cellular radio network; and means for identifying, for each traffic descriptor in a set of traffic descriptors, an access policy of the cellular radio network, the access policy identifying an access preference rule for a UE to employ for connecting to the core network function of the cellular radio network, each access preference rule indicating to the UE whether to preferably connect to the core network function via the cellular radio network or the non-cellular radio network for the traffic descriptor and the slicing processing of the traffic descriptor. The apparatus may also include means for determining, for each traffic descriptor and based at least in part on the legacy slicing processing and the slicing processing and based at least in part on the access policy, whether to transfer a connection associated with the traffic descriptor to the core network function or to establish an updated connection for the traffic descriptor with the core network function.

[0037] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions executable by a processor to: establish a connection to a legacy core network function of a legacy cellular radio network via a legacy gateway between the legacy cellular radio network and a non-cellular radio network; and, for each traffic descriptor in a traffic descriptor set, identify a legacy access policy of the legacy cellular radio network, the legacy access policy identifying a legacy access preference rule for the UE to employ for connecting to the legacy core network function, each legacy access preference rule indicating to the UE whether to prefer connecting to the legacy core network function via the legacy cellular radio network or the non-cellular radio network for the traffic descriptor and legacy slicing processing for the traffic descriptor. The code may include instructions executable by the processor to establish a connection to a core network function of a cellular radio network via a gateway between the cellular radio network and the non-cellular radio network, and, for each traffic descriptor in a set of traffic descriptors, identify an access policy of the cellular radio network, the access policy identifying an access preference rule for a UE to employ for connecting to the core network function of the cellular radio network, each access preference rule indicating to the UE whether to preferably connect to the core network function via the cellular radio network or the non-cellular radio network for the traffic descriptor and slice processing for the traffic descriptor. The code may include instructions executable by the processor to determine, for each traffic descriptor and based at least in part on the legacy slice processing and the slice processing and based at least in part on the access policy, whether to transfer a connection associated with the traffic descriptor to the core network function or to establish an updated connection for the traffic descriptor with the core network function.

[0038] Some examples of the methods, devices, and non-transitory computer-readable media described herein may further include operations, features, devices, or instructions for: for at least two traffic descriptors in a traffic descriptor set, determining that the legacy traffic descriptor and the traffic descriptor may be the same traffic descriptor, and transferring connections for the at least two traffic descriptors to a core network function.

[0039] Some examples of the methods, devices, and non-transitory computer-readable media described herein may further include operations, features, devices, or instructions for: for at least two traffic descriptors in a traffic descriptor set, determining that the legacy traffic descriptor and the traffic descriptor may be different traffic descriptors, and updating a connection for at least one of the two traffic descriptors with a core network function.

[0040] Some examples of the methods, devices, and non-transitory computer-readable media described herein may further include operations, features, devices, or instructions for: for at least two traffic descriptors in a traffic descriptor set that can be associated with the same traffic descriptor, determining that the legacy access policy and the access policy can be the same access policy, and transferring connections for the at least two traffic descriptors to a core network function.

[0041] Some examples of the methods, devices, and non-transitory computer-readable media described herein may further include operations, features, devices, or instructions for: for at least two traffic descriptors in a traffic descriptor set that can be associated with the same traffic descriptor, determining that the legacy access policy and the access policy can be different access policies, and updating a connection for at least one of the two traffic descriptors with a core network function.

[0042] In some examples of the methods, devices, and non-transitory computer-readable media described herein, the cellular radio network includes a 5G NR SA cellular radio network, the legacy cellular radio network includes at least one of a 4G LTE cellular radio network or a 5G NR NSA cellular radio network, the access policy includes a URSP, the legacy access policy includes an ANDSP, the core network function includes a 5G NR SA core network (5GC), the gateway includes an N3IWF between the core network function of the 5G NR SA cellular radio network and the non-cellular radio network, and the legacy gateway includes an EPC core network function of the 4G LTE cellular radio network or the 5G NR NSA cellular radio network and an EPDG between the non-cellular radio network. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] Figure 1 An example of a wireless communication system supporting methods for handling slices accounting for Evolved Packet Data Gateway (Wi-Fi) access in accordance with aspects of the present disclosure is illustrated.

[0045] Figure 2 An example of a wireless communication system supporting methods for handling slices accounting for Evolved Packet Data Gateway (Wi-Fi) access in accordance with aspects of the present disclosure is illustrated.

[0046] Figure 3 Illustrated are examples of processes supporting a method for handling slices that account for Evolved Packet Data Gateway Wi-Fi access in accordance with aspects of the present disclosure.

[0047] Figure 4 Illustrated are examples of processes supporting a method for handling slices that account for Evolved Packet Data Gateway Wi-Fi access in accordance with aspects of the present disclosure.

[0048] Figure 5 Illustrated are examples of processes supporting a method for handling slices that account for Evolved Packet Data Gateway Wi-Fi access in accordance with aspects of the present disclosure.

[0049] Figure 6 Illustrated are examples of processes supporting a method for handling slices that account for Evolved Packet Data Gateway Wi-Fi access in accordance with aspects of the present disclosure.

[0050] Figure 7 Illustrated are examples of processes supporting a method for handling slices that account for Evolved Packet Data Gateway Wi-Fi access in accordance with aspects of the present disclosure.

[0051] Figure 8 Illustrated are examples of processes supporting a method for handling slices that account for Evolved Packet Data Gateway Wi-Fi access in accordance with aspects of the present disclosure.

[0052] Figure 9 and 10 Illustrated is a block diagram of an apparatus supporting a method for handling slices accounting for Evolved Packet Data Gateway Wi-Fi access in accordance with various aspects of the present disclosure.

[0053] Figure 11 A block diagram of a communications manager supporting a method for handling slices accounting for Evolved Packet Data Gateway Wi-Fi access in accordance with aspects of the present disclosure is illustrated.

[0054] Figure 12 Illustrated is a diagram of a system including devices supporting a method for handling slices that account for Evolved Packet Data Gateway Wi-Fi access in accordance with aspects of the present disclosure.

[0055] Figures 13 to 18 A flow chart illustrating a method for handling slices taking into account Evolved Packet Data Gateway Wi-Fi access according to aspects of the present disclosure is shown.

[0056] Detailed description

[0057] Various aspects of the described techniques provide mechanisms that can be implemented by user equipment (UE) operating in a heterogeneous environment, including at least one of a non-cellular radio network (e.g., a wireless local area network (WLAN), a Wi-Fi network, etc.), a legacy cellular radio network (e.g., such as a fourth generation (4G) cellular radio network, a fifth generation (5G) New Radio (NR) non-standalone (NSA) cellular radio network, etc.), and / or a 5G NR standalone (SA) cellular radio network. Wireless networks continue to evolve, such that UEs may increasingly be located in such heterogeneous networks. However, because each generation of wireless networks has its own set of rules, policies, protocols, functions, entities, etc., this may result in differences between different wireless networks. This may result in the UE being presented with conflicting and / or missing protocols, entities, etc. with respect to each network. This may disrupt communications between the UE and the associated wireless networks.

[0058] Aspects of the present disclosure are initially described in the context of wireless communication systems. Generally speaking, the described techniques provide various mechanisms to resolve inconsistencies between legacy cellular radio networks and advanced cellular radio networks being deployed.

[0059] For example, a UE may establish a connection with a base station associated with a cellular radio network (e.g., a 5G NR SA connection). Whenever a UE establishes a connection with a base station, the base station may generally configure, instruct, or otherwise communicate various policies, protocols, and the like for the cellular radio network to the UE. Accordingly, the UE may receive an access policy (e.g., a UE routing selection measure (URSP)) that identifies access preference rules for the UE to use to connect to a core network function of a cellular cell (e.g., to a 5G core network (5GC)). That is, the URSP may generally indicate whether the UE will prefer to route outgoing traffic (e.g., traffic may be routed to an established protocol data unit (PDU) session (e.g., to the 5GC via a 5G NR SA base station), offloaded to a non-3rd Generation Partnership Project (3GPP) cellular connection (e.g., via a Wi-Fi network)), or establish a new PDU session (e.g., a new PDU session with the 5GC via a 5G NR SA base station). In this example, the URSP may indicate to the UE that it prefers to connect to the 5GC via a non-cellular radio network, for example, by routing outgoing traffic in a PDU session via a Wi-Fi network. However, the UE may determine that a gateway (e.g., a 3GPP Networking Function (N3IWF) gateway) between the Wi-Fi radio network and the 5GC is not configured or is unavailable for some other reason. The UE may also determine that a gateway selection policy (e.g., an Access Network Discovery Selection Policy (ANDSP)) is not configured for 5G NRSA. Broadly speaking, ANDSP is used by the UE to select a non-3GPP access network, such as a wireless local area network (WLAN), a Wi-Fi network, etc. Consequently, the UE may establish a connection to a legacy core network function (e.g., an Evolved Packet Data Gateway (EPDG)) of a legacy cellular radio network (e.g., a 4G and / or 5G NR NSA cellular radio network) via a legacy gateway (e.g., an Evolved Packet Data Gateway (EPDG)). Broadly speaking, the EPDG may be a gateway between the Wi-Fi network and the EPC. Thus, even though the URSP gives a preference for Wi-Fi networks and the ANDSP and N3IWF are not configured or otherwise unavailable, the UE can still connect to the EPC core network using the EPDG following the URSP access policy when the ANDSP / N3IWF has not yet been configured for the 5G NR SA cellular radio network.

[0060] Additionally or alternatively, the UE may have already established a cellular connection with a base station in a 5G NR SA cellular radio network. However, in this example, the URSP received by the UE may indicate a preference for a 3GPP connection, for example, for the UE to route outgoing traffic to the 5G NR SA cellular radio network. That is, the URSP may indicate a preference for the UE to connect to the 5GC via a 5G NR SA base station. However, the UE may determine that neither the N3IWF gateway nor the ANDSP gateway selection policy is configured for a cellular radio network (e.g., for a 5G NR SA cellular radio network). Subsequently, the UE may determine that the 5G NR SA cellular radio network has become unavailable, but the Wi-Fi radio network is available. In response, the UE may establish a connection to a legacy core network function (e.g., EPC) of a legacy cellular radio network (e.g., 4G / 5G NR NSA) via a legacy gateway (e.g., EPDG). The UE may identify or otherwise determine a legacy access policy (e.g., an Access Network Discovery and Selection Function (ANDSF)) that gives a preference for the UE to use a non-cellular radio network (e.g., a Wi-Fi network). That is, in a broad sense, the ANDSF helps the UE discover non-3GPP access networks, such as WLAN, Wi-Fi networks, etc. However, the UE may determine that a 5G NR SA cellular radio network has become available again and therefore establish a new connection to the cellular radio network. That is, even if the ANDSF instructs the UE to give a preference for a Wi-Fi network, the UE may follow the preference given in the URSP and re-establish its connection to the 5G NR NSA cellular radio network when the 5G NR SA network becomes available again. Otherwise, the UE may be stuck on a Wi-Fi connection even if a more advanced 5G NR SA network is available.

[0061] Additionally or alternatively, the UE may establish a cellular connection to a 5G NR SA cellular radio network and receive a URSP that, in this example, prefers a non-cellular radio network (e.g., a non-3GPP network such as a Wi-Fi network). Similarly, the UE may determine that neither the ANDSP nor the N3IWF is configured for the 5G NR SA cellular radio network, but that a Wi-Fi network is available. Therefore, the UE may establish a connection to the EPC legacy core network function of the 4G / 5G NR NSA legacy cellular radio network via the EPDG gateway. The UE may receive or otherwise identify an ANDSF legacy access policy that, in this example, prefers a 3GPP connection. Previously, the UE would switch back and forth between a 5G NR SA connection and a Wi-Fi connection. However, to avoid this switching, the UE may maintain a connection to the EPC legacy core network function via the EPDG legacy gateway. This approach may prevent the UE from frequently switching between a 5G NR SA network, where the URSP prefers a non-3GPP connection, and a Wi-Fi network, where the ANDSF prefers a 3GPP connection.

[0062] Additionally or alternatively, the UE may establish a connection to the EPC legacy core network function of the 4G / 5G NR NSA legacy cellular radio network via an EPDG legacy gateway. The UE may be configured with a set of traffic descriptors (e.g., the UE may have different applications operating on the UE). For each traffic descriptor set (e.g., each application), the UE may identify an ANDSF legacy access policy that indicates a preference for the UE to connect via a cellular radio network (e.g., a 3GPP cellular radio network) or a non-cellular radio network (e.g., a non-3GPP radio network). The UE may also identify or otherwise determine the legacy slice handling associated with each traffic descriptor, for example, based at least in part on the connection to the EPC via the EPDG. The UE may establish a connection to the 5GC core network function of the 5G NR SA cellular radio network via the N3IWF gateway. Accordingly, the UE may receive or otherwise identify a URSP access policy for the UE to employ, which also informs the UE whether to prefer connecting via a cellular radio network or a non-cellular radio network. The UE may also determine or otherwise identify the slice handling for each traffic descriptor based, for example, at least in part on the URSP access policy, the traffic descriptor identifier, the traffic descriptor type, etc. Thus, the UE may use the URSP access policy, the legacy slice handling (from the EPC), and / or the slice handling (from the 5GC) to determine whether to transfer the connection for each traffic descriptor from the EPC via the EPDG gateway to the 5GC via the N3IWF or to establish an updated connection with the 5GC via the N3IWF. Thus, the UE may ensure that each traffic descriptor is given the appropriate slice handling and / or connection preference when switching from the EPC connection to the 5GC connection.

[0063] Various aspects of the present disclosure are further illustrated and described through and with reference to device diagrams, system diagrams, and flow charts related to methods for handling slices that account for evolved packet data gateway Wi-Fi access.

[0064] Figure 1 An example of a wireless communication system 100 supporting methods for handling slices that account for evolved packet data gateway Wi-Fi access in accordance with aspects of the present disclosure is illustrated. The wireless communication system 100 may include one or more base stations 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-A Pro network, or a New Radio (NR) network. In some examples, the wireless communication system 100 may support enhanced broadband communications, ultra-reliable (e.g., mission-critical) communications, low-latency communications, communications with low-cost and low-complexity devices, or any combination thereof.

[0065] Base stations 105 may be dispersed throughout a geographic area to form wireless communication system 100 and may be different forms of devices or devices with different capabilities. Base stations 105 and UEs 115 may communicate wirelessly via one or more communication links 125. Each base station 105 may provide a coverage area 110 over which UEs 115 and base stations 105 may establish one or more communication links 125. Coverage area 110 may be an example of a geographic area over which base stations 105 and UEs 115 may support signal communication according to one or more radio access technologies.

[0066] The UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary or mobile, or stationary and mobile at different times. The UEs 115 may be different forms of devices or devices with different capabilities. Figure 1 1. The UE 115 described herein may be capable of communicating with various types of devices, such as other UEs 115, base stations 105, or network equipment (e.g., core network nodes, relays, integrated access and backhaul (IAB) nodes, or other network equipment), such as Figure 1 As shown in .

[0067] Each base station 105 can communicate with the core network 130, with each other, or both. For example, the base stations 105 can interface with the core network 130 via one or more backhaul links 120 (e.g., via S1, N2, N3, or other interfaces). The base stations 105 can communicate with each other directly (e.g., directly between the base stations 105), indirectly (e.g., via the core network 130), or both directly and indirectly on the backhaul links 120 (e.g., via X2, Xn, or other interfaces). In some examples, the backhaul links 120 can be or include one or more wireless links.

[0068] One or more of the base stations 105 described herein may include or may be referred to by one of ordinary skill in the art as a base transceiver station, a radio base station, an access point, a radio transceiver, a Node B, an evolved Node B (eNB), a next generation Node B, or a Gigabit Node B (any of which may be referred to as a gNB), a Home Node B, a Home Evolved Node B, or other suitable terminology.

[0069] UE 115 may include or be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable terminology, where "device" may also be referred to as a unit, a station, a terminal, or a client, etc. UE 115 may also include or be referred to as a personal electronic device, such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, UE 115 may include or be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communication (MTC) device, etc., which may be implemented in various objects, such as appliances or vehicles, meters, etc.

[0070] The UE 115 described herein may be capable of communicating with various types of devices, such as other UEs 115, which may sometimes act as relays, as well as base stations 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, relay base stations, etc. Figure 1 As shown in .

[0071] The UE 115 and the base station 105 may communicate wirelessly with each other via one or more communication links 125 on one or more carriers. The term "carrier" may refer to a set of radio frequency spectrum resources having a defined physical layer structure for supporting the communication link 125. For example, a carrier for the communication link 125 may include a portion of a radio frequency spectrum band (e.g., a bandwidth portion (BWP)) that operates according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling for coordinating carrier operation, user data, or other signaling. The wireless communication system 100 may support communication with the UE 115 using carrier aggregation or multi-carrier operation. The UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers according to a carrier aggregation configuration. Carrier aggregation may be used with both frequency division duplex (FDD) and time division duplex (TDD) component carriers.

[0072] In some examples (e.g., in a carrier aggregation configuration), a carrier may also have acquisition signaling or control signaling that coordinates the operation of other carriers. A carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute Radio Frequency Channel Number (EARFCN)) and may be located according to a channel grid for discovery by a UE 115. A carrier may operate in a standalone mode in which initial acquisition and connection may be performed by a UE 115 via the carrier, or a carrier may operate in a non-standalone mode in which the connection is anchored using a different carrier (e.g., a different carrier of the same or different radio access technology).

[0073] The communication link 125 shown in the wireless communication system 100 may include an uplink transmission from the UE 115 to the base station 105, or a downlink transmission from the base station 105 to the UE 115. A carrier may carry downlink or uplink communications (e.g., in FDD mode) or may be configured to carry both downlink and uplink communications (e.g., in TDD mode).

[0074] A carrier may be associated with a particular bandwidth of radio frequency spectrum, and in some examples, the carrier bandwidth may be referred to as the "system bandwidth" of the carrier or wireless communication system 100. For example, the carrier bandwidth may be one of several determined bandwidths (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 megahertz (MHz)) of a carrier of a particular radio access technology. Devices of the wireless communication system 100 (e.g., base station 105, UE 115, or both) may have a hardware configuration that supports communication on a particular carrier bandwidth, or may be configurable to support communication on one of a set of carrier bandwidths. In some examples, the wireless communication system 100 may include a base station 105 or UE 115 that supports simultaneous communication via carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate on a portion (e.g., a subband, a BWP) or all of the carrier bandwidth.

[0075] The signal waveform transmitted on the carrier may include multiple subcarriers (e.g., using a multicarrier modulation (MCM) technique such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system employing MCM techniques, a resource element may include one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, where the symbol period and subcarrier spacing are inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the code rate of the modulation scheme, or both). Thus, the more resource elements received by UE 115 and the higher the order of the modulation scheme, the higher the data rate of UE 115 can be. Wireless communication resources may refer to a combination of radio frequency spectrum resources, time resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial layers may further improve the data rate or data integrity of communications with UE 115.

[0076] One or more parameter designs for a carrier may be supported, where the parameter designs may include subcarrier spacing (Δf) and cyclic prefix. A carrier may be divided into one or more BWPs with the same or different parameter designs. In some examples, a UE 115 may be configured with multiple BWPs. In some examples, a single BWP for a carrier may be active at a given time, and communications for the UE 115 may be limited to the one or more active BWPs.

[0077] The time interval of the base station 105 or the UE 115 can be expressed as a multiple of a basic time unit, which can be, for example, a sampling period T s =1 / (Δf max ·N f ) seconds, where Δf max It can represent the maximum supported subcarrier spacing, and N f The maximum supported discrete Fourier transform (DFT) size may be indicated. Time intervals of communication resources may be organized according to radio frames, each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).

[0078] Each frame may include a plurality of consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may be divided (e.g., in the time domain) into subframes, and each subframe may be further divided into a number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a number of code element periods (e.g., depending on the length of the cyclic prefix added before each code element period). In some wireless communication systems 100, a time slot may be further divided into a plurality of mini-time slots containing one or more code elements. Excluding the cyclic prefix, each code element period may contain one or more (e.g., N f The duration of a symbol period may depend on the subcarrier spacing or the operating band.

[0079] A subframe, slot, mini-slot, or symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communication system 100 and may be referred to as a transmission time interval (TTI). In some examples, the TTI duration (e.g., the number of symbol periods in a TTI) may be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 may be dynamically selected (e.g., in bursts of shortened TTIs (sTTIs)).

[0080] Physical channels may be multiplexed on a carrier according to various techniques. Physical control channels and physical data channels may be multiplexed on a downlink carrier, for example, using one or more of time division multiplexing (TDM), frequency division multiplexing (FDM), or hybrid TDM-FDM techniques. A control region (e.g., a control resource set (CORESET)) for physical control channels may be defined by a number of symbol periods and may extend across the system bandwidth or a subset of the system bandwidth of a carrier. One or more control regions (e.g., CORESETs) may be configured for a set of UEs 115. For example, one or more of UEs 115 may monitor or search the control region for control information according to one or more search space sets, and each search space set may include one or more control channel candidates in one or more aggregation levels arranged in a cascaded manner. An aggregation level for a control channel candidate may refer to the number of control channel resources (e.g., control channel elements (CCEs)) associated with encoded information for a control information format having a given payload size. The search space sets may include a common search space set configured for transmitting control information to multiple UEs 115 and a UE-specific search space set for transmitting control information to a specific UE 115 .

[0081] Each base station 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hotspots, or other types of cells, or any combination thereof). The term "cell" may refer to a logical communication entity used to communicate with a base station 105 (e.g., on a carrier) and may be associated with an identifier (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID), or other) used to distinguish between adjacent cells. In some examples, a cell may also refer to a geographic coverage area 110 or a portion of a geographic coverage area 110 (e.g., a sector) on which the logical communication entity operates. The scope of such a cell may range from a smaller area (e.g., a structure, a subset of structures) to a larger area depending on various factors (such as the capabilities of the base station 105). For example, a cell may be or include a building, a subset of buildings, or an external space between or overlapping geographic coverage areas 110, among other examples.

[0082] A macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access to UEs 115 that have a service subscription with a network provider that supports the macro cell. A small cell may be associated with a lower power base station 105 (compared to a macro cell), and the small cell may operate in the same or different (e.g., licensed, unlicensed) frequency band as the macro cell. A small cell may provide unrestricted access to UEs 115 that have a service subscription with the network provider, or may provide restricted access to UEs 115 associated with the small cell (e.g., UEs 115 in a closed subscriber group (CSG), UEs 115 associated with users in a home or office). A base station 105 may support one or more cells and may also support communications over one or more cells using one or more component carriers.

[0083] In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB)) that may provide access to different types of devices.

[0084] In some examples, base stations 105 can be mobile and, therefore, provide communication coverage for mobile geographic coverage areas 110. In some examples, different geographic coverage areas 110 associated with different technologies can overlap, but the different geographic coverage areas 110 can be supported by the same base station 105. In other examples, overlapping geographic coverage areas 110 associated with different technologies can be supported by different base stations 105. The wireless communication system 100 can include, for example, a heterogeneous network in which different types of base stations 105 provide coverage for various geographic coverage areas 110 using the same or different radio access technologies.

[0085] The wireless communication system 100 may support synchronous or asynchronous operation. For synchronous operation, the base stations 105 may have similar frame timing, and transmissions from different base stations 105 may be approximately aligned in time. For asynchronous operation, the base stations 105 may have different frame timing, and transmissions from different base stations 105 may not be aligned in time in some examples. The techniques described herein may be used for either synchronous or asynchronous operation.

[0086] Some UEs 115, such as MTC or IoT devices, may be low-cost or low-complexity devices and may provide automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC may refer to data communication technology that allows devices to communicate with each other or with a base station 105 without human intervention. In some examples, M2M communication or MTC may include communications from devices that incorporate sensors or meters to measure or capture information and relay such information to a central server or application that utilizes the information or presents it to a person interacting with the application. Some UEs 115 may be designed to collect information or implement automated behavior of machines or other devices. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wilderness survival monitoring, weather and geographic event monitoring, queue management and tracking, remote security sensing, physical access control, and transaction-based commercial charging.

[0087] Some UEs 115 may be configured to employ a reduced power consumption mode of operation, such as half-duplex communication (e.g., a mode that supports unidirectional communication via transmission or reception but not simultaneous transmission and reception). In some examples, half-duplex communication may be performed at a reduced peak rate. Other power saving techniques for UEs 115 include entering a power-saving deep sleep mode when not engaged in active communication, operating over a limited bandwidth (e.g., according to narrowband communication), or a combination of these techniques. For example, some UEs 115 may be configured to operate using a narrowband protocol type that is associated with a defined portion or range (e.g., a set of subcarriers or resource blocks (RBs)) within a carrier, within a guard band of a carrier, or outside a carrier.

[0088] The wireless communication system 100 can be configured to support ultra-reliable communication or low-latency communication or various combinations thereof. For example, the wireless communication system 100 can be configured to support ultra-reliable low-latency communication (URLLC) or mission-critical communication. The UE 115 can be designed to support ultra-reliable, low-latency or critical functions (e.g., mission-critical functions). Ultra-reliable communication can include private communication or group communication and can be supported by one or more mission-critical services such as mission-critical push-to-talk (MCPTT), mission-critical video (MCVideo), or mission-critical data (MCData). Support for mission-critical functions can include prioritization of services, and mission-critical services can be used for public safety or general commercial applications. The terms ultra-reliable, low-latency, mission-critical, and ultra-reliable low-latency can be used interchangeably herein.

[0089] In some examples, UE 115 may also be able to communicate directly with other UEs 115 over a device-to-device (D2D) communication link 135 (e.g., using a peer-to-peer (P2P) or D2D protocol). One or more UEs 115 utilizing D2D communication may be within the geographic coverage area 110 of base station 105. Other UEs 115 in such a group may be outside the geographic coverage area 110 of base station 105 or otherwise unable to receive transmissions from base station 105. In some examples, groups of UEs 115 communicating via D2D communication may utilize a one-to-many (1:M) system, in which each UE 115 transmits to every other UE 115 in the group. In some examples, base station 105 facilitates the scheduling of resources for D2D communication. In other cases, D2D communication is performed between UEs 115 without involving base station 105.

[0090] In some systems, the D2D communication link 135 can be an example of a communication channel (such as a sidelink communication channel) between vehicles (e.g., UE 115). In some examples, the vehicles can communicate using vehicle-to-everything (V2X) communication, vehicle-to-vehicle (V2V) communication, or some combination of these communications. The vehicles can signal information related to traffic conditions, signal scheduling, weather, safety, emergency situations, or any other information related to the V2X system. In some examples, the vehicles in the V2X system can use vehicle-to-network (V2N) communication to communicate with roadside infrastructure (such as roadside units), with the network, or with both, via one or more network nodes (e.g., base station 105).

[0091] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), and the EPC or 5GC may include at least one control plane entity (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) that manages access and mobility, and at least one user plane entity (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)) that routes packets or interconnects to external networks. The control plane entity may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management for UEs 115 served by base stations 105 associated with the core network 130. User IP packets may be delivered through the user plane entity, which may provide IP address allocation and other functions. The user plane entity may be connected to the network operator IP service 150. Operator IP services 150 may include access to the Internet, an intranet, an IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0092] Some network devices (such as base stations 105) may include subcomponents, such as access network entities 140, which may be examples of access node controllers (ANCs). Each access network entity 140 may communicate with each UE 115 through one or more other access network transport entities 145, which may be referred to as radio heads, smart radio heads, or transmit / receive points (TRPs). Each access network transport entity 145 may include one or more antenna panels. In some configurations, the various functions of each access network entity 140 or base station 105 may be distributed across various network devices (e.g., radio heads and ANCs) or consolidated into a single network device (e.g., base station 105).

[0093] The wireless communication system 100 can operate using one or more frequency bands, typically in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Generally speaking, the 300 MHz to 3 GHz region is referred to as the ultra-high frequency (UHF) region or the decimeter band because the wavelengths range from approximately 1 decimeter to 1 meter long. UHF waves can be blocked or redirected by buildings and environmental features, but these waves can penetrate various structures sufficiently for macrocells to provide service to UEs 115 located indoors. Transmissions using UHF waves can be associated with smaller antennas and a shorter range (e.g., less than 100 kilometers) compared to transmissions using the lower frequencies and longer wavelengths in the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0094] The wireless communication system 100 may also operate in a super high frequency (SHF) region using a frequency band from 3 GHz to 30 GHz (also known as a centimeter band) or in an extremely high frequency (EHF) region of the spectrum (e.g., from 30 GHz to 300 GHz) (also known as a millimeter band). In some examples, the wireless communication system 100 may support millimeter wave (mmW) communications between the UE 115 and the base station 105, and the EHF antennas of the corresponding devices may be smaller and more closely spaced than the UHF antennas. In some examples, this may facilitate the use of antenna arrays within the device. However, the propagation of EHF transmissions may be subject to even greater atmospheric attenuation and a shorter range than SHF or UHF transmissions. The techniques disclosed herein may be employed across transmissions using one or more different frequency regions, and the use of frequency bands specified across these frequency regions may vary by country or regulatory agency.

[0095] The wireless communication system 100 may utilize both licensed and unlicensed radio frequency spectrum bands. For example, the wireless communication system 100 may employ licensed assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology in an unlicensed band, such as the 5 GHz industrial, scientific, and medical (ISM) band. When operating in an unlicensed radio frequency spectrum band, devices (such as base stations 105 and UEs 115) may employ carrier sensing for conflict detection and avoidance. In some examples, operations in the unlicensed band may be based on a carrier aggregation configuration (e.g., LAA) in coordination with component carriers operating in the licensed band. Operations in the unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among others.

[0096] The base station 105 or UE 115 may be equipped with multiple antennas that can be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of the base station 105 or UE 115 may be located within one or more antenna arrays or antenna panels that can support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly (such as an antenna tower). In some examples, the antennas or antenna arrays associated with the base station 105 may be located at different geographical locations. The base station 105 may have an antenna array having several rows and columns of antenna ports that the base station 105 can use to support beamforming for communications with the UE 115. Similarly, the UE 115 may have one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support radio frequency beamforming for signals transmitted via the antenna ports.

[0097] The base station 105 or the UE 115 can use MIMO communication to exploit multipath signal propagation and improve spectral efficiency by transmitting or receiving multiple signals via different spatial layers. Such a technique may be referred to as spatial multiplexing. For example, a transmitting device may transmit multiple signals via different antennas or different antenna combinations. Similarly, a receiving device may receive multiple signals via different antennas or different antenna combinations. Each of the multiple signals may be referred to as a separate spatial stream and may carry bits associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers may be associated with different antenna ports for channel measurement and reporting. MIMO techniques include single-user MIMO (SU-MIMO), in which multiple spatial layers are transmitted to the same receiving device, and multi-user MIMO (MU-MIMO), in which multiple spatial layers are transmitted to multiple devices.

[0098] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting device or a receiving device (e.g., base station 105, UE 115) to shape or steer an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming can be achieved by combining signals communicated via antenna elements of an antenna array so that some signals propagating at a particular orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to signals communicated via antenna elements can include the transmitting device or the receiving device applying an amplitude offset, a phase offset, or both to the signals carried via the antenna elements associated with that device. The adjustments associated with each antenna element can be defined by a set of beamforming weights associated with a particular orientation (e.g., relative to the antenna array of the transmitting device or the receiving device, or relative to some other orientation).

[0099] The base station 105 or the UE 115 may use beam sweeping techniques as part of a beamforming operation. For example, the base station 105 may use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communication with the UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted multiple times by the base station 105 in different directions. For example, the base station 105 may transmit signals according to different sets of beamforming weights associated with different transmission directions. The transmissions in different beam directions may be used (e.g., by a transmitting device (such as the base station 105) or a receiving device (such as the UE 115)) to identify a beam direction for later transmission or reception by the base station 105.

[0100] Some signals, such as data signals associated with a particular recipient device, may be transmitted by base station 105 in a single beam direction, e.g., a direction associated with a recipient device, such as UE 115. In some examples, a beam direction associated with transmissions along a single beam direction may be determined based on signals transmitted in one or more beam directions. For example, UE 115 may receive one or more signals transmitted by base station 105 in different directions and may report to base station 105 an indication of the signal received by UE 115 with the highest signal quality or other acceptable signal quality.

[0101] In some examples, transmission by a device (e.g., by a base station 105 or a UE 115) may be performed using multiple beam directions, and the device may use a combination of digital precoding or radio frequency beamforming to generate a combined beam for transmission (e.g., from the base station 105 to the UE 115). The UE 115 may report feedback indicating precoding weights for one or more beam directions, and the feedback may correspond to a configured number of beams across the system bandwidth or one or more subbands. The base station 105 may transmit reference signals that may be precoded or unprecoded (e.g., cell-specific reference signals (CRS), channel state information reference signals (CSI-RS)). The UE 115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., a multi-panel type codebook, a linear combination type codebook, a port selection type codebook). Although these techniques are described with reference to signals transmitted by base station 105 in one or more directions, UE 115 may use similar techniques to transmit signals multiple times in different directions (e.g., to identify a beam direction for subsequent transmission or reception by UE 115) or to transmit signals in a single direction (e.g., to transmit data to a receiving device).

[0102] A receiving device (e.g., UE 115) may attempt multiple receive configurations (e.g., directional listening) when receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from base station 105. For example, the receiving device may attempt multiple receive directions by receiving via different antenna subarrays, processing received signals according to different antenna subarrays, receiving according to different receive beamforming weight sets applied to signals received at multiple antenna elements of an antenna array (e.g., different directional listening weight sets), or processing received signals according to different receive beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, any of which may be referred to as "listening" according to different receive configurations or receive directions. In some examples, the receiving device may use a single receive configuration to receive along a single beam direction (e.g., when receiving data signals). The single receive configuration may be aligned on a beam direction determined based on listening according to different receive configuration directions (e.g., a beam direction determined to have the highest signal strength, highest signal-to-noise ratio (SNR), or other acceptable signal quality based on listening according to multiple beam directions).

[0103] The wireless communication system 100 can be a packet-based network that operates according to a layered protocol stack. In the user plane, the communication of the bearer or packet data convergence protocol (PDCP) layer can be IP-based. The radio link control (RLC) layer can perform packet segmentation and reassembly to communicate on the logical channel. The media access control (MAC) layer can perform priority handling and multiplex the logical channel into the transport channel. The MAC layer can also use error detection technology, error correction technology, or both to support retransmission of the MAC layer to improve link efficiency. In the control plane, the radio resource control (RRC) protocol layer can provide the establishment, configuration and maintenance of the RRC connection of the radio bearer that supports user plane data between the UE 115 and the base station 105 or the core network 130. In the physical layer, the transport channel can be mapped to the physical channel.

[0104] UE 115 and base station 105 may support retransmission of data to increase the likelihood that the data is successfully received. Hybrid Automatic Repeat Request (HARQ) feedback is a technique for increasing the likelihood that data is correctly received on communication link 125. HARQ may include a combination of error detection (e.g., using a cyclic redundancy check (CRC)), forward error correction (FEC), and retransmission (e.g., automatic repeat request (ARQ)). HARQ may improve MAC layer throughput in poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, a device may support simultaneous slot HARQ feedback, wherein the device may provide HARQ feedback in a particular time slot for data received in a previous symbol in that time slot. In other cases, the device may provide HARQ feedback in a subsequent time slot or based on some other time interval.

[0105] A UE 115 may establish a cellular connection with a base station 105 associated with a cellular radio network. The UE 115 may receive an access policy of the cellular radio network, the access policy identifying an access preference rule for the UE 115 to employ for connecting to a core network function of the cellular radio network, the access preference rule indicating to the UE that connection to the core network function is preferably via a non-cellular radio network. The UE 115 may determine that a gateway between the non-cellular radio network and the core network function of the cellular radio network is not configured. The UE 115 may determine that a gateway selection policy for the cellular radio network is not configured. The UE 115 may establish a connection to a legacy core network function of the legacy cellular radio network via a legacy gateway between the non-cellular radio network and the legacy core network function based at least in part on the access preference rule, the non-configured gateway, and the non-configured gateway selection policy.

[0106] UE 115 may establish a cellular connection with base station 105 associated with a cellular radio network. UE 115 may receive an access policy of the cellular radio network, the access policy identifying access preference rules for UE 115 to use to connect to a core network function of the cellular radio network, the access preference rules indicating to UE 115 that connection to the core network function is preferably made via the cellular radio network and via a gateway between the cellular radio network and the core network function. UE 115 may determine that the gateway is not configured. UE 115 may determine that a gateway selection policy for the cellular radio network is not configured. UE 115 may determine that a non-cellular radio network is available and that the cellular radio network has become unavailable. UE 115 may establish a connection via the non-cellular radio network to a legacy core network function of the legacy cellular radio network via a legacy gateway between the non-cellular radio network and the legacy core network function. UE 115 may identify a legacy access policy for the legacy cellular radio network, the legacy access policy identifying a legacy access preference rule for UE 115 to employ for connecting to the legacy core network function, the legacy access preference rule indicating to UE 115 that connection to the legacy core network function is preferred via a non-cellular radio network. UE 115 may determine that a cellular radio network has become available for establishing a new connection. UE 115 may establish the new connection to the cellular radio network based at least on the access preference rule.

[0107] UE 115 may establish a cellular connection with a base station 105 associated with a cellular radio network. UE 115 may receive an access policy of the cellular radio network, the access policy identifying an access preference rule for the UE 115 to employ for connecting to a core network function of the cellular radio network, the access preference rule indicating to the UE 115 that connection to the core network function is preferably via a non-cellular radio network. UE 115 may determine that the non-cellular radio network is available and that a gateway between the non-cellular radio network and the core network function of the cellular radio network is not configured. UE 115 may determine that a gateway selection policy for the cellular radio network is not configured. UE 115 may establish a connection to a legacy core network function of the legacy cellular radio network via a legacy gateway between the legacy core network function and the non-cellular radio network. The UE 115 may identify a legacy access policy for the legacy cellular radio network, the legacy access policy identifying a legacy access preference rule for the UE 115 to employ for connecting to the legacy core network function, the legacy access preference rule indicating to the UE 115 that connection to the legacy core network function is preferred via the legacy cellular radio network. The UE 115 may maintain connection to the legacy core network function of the legacy radio network via the legacy gateway based at least in part on the access preference rule.

[0108] The UE 115 may establish a connection to a legacy core network function of the legacy cellular radio network via a legacy gateway between the legacy cellular radio network and the non-cellular radio network. The UE 115 may identify, for each traffic descriptor in the traffic descriptor set, a legacy access policy of the legacy cellular radio network, the legacy access policy identifying a legacy access preference rule for the UE 115 to employ for connecting to the legacy core network function, each legacy access preference rule indicating to the UE 115 whether to preferably connect to the legacy core network function via the legacy cellular radio network or the non-cellular radio network for the traffic descriptor and legacy slice handling for the traffic descriptor. The UE 115 may establish a connection to the core network function of the cellular radio network via the gateway between the cellular radio network and the non-cellular radio network. The UE 115 may, for each traffic descriptor in the traffic descriptor set, identify an access policy of the cellular radio network, the access policy identifying an access preference rule for the UE 115 to employ for connecting to a core network function of the cellular radio network, each access preference rule indicating to the UE 115 whether to preferably connect to the core network function via the cellular radio network or the non-cellular radio network for the traffic descriptor and the slice handling of the traffic descriptor. For each traffic descriptor and based at least in part on the legacy slice handling and the slice handling and based at least in part on the access policy, the UE 115 may determine whether to transfer a connection associated with the traffic descriptor to the core network function or to establish an updated connection with the core network function for the traffic descriptor.

[0109] Figure 2 An example of a wireless communication system 200 that supports methods for handling slices that account for evolved packet data gateway Wi-Fi access according to aspects of the present disclosure is illustrated. In some examples, the wireless communication system 200 can implement aspects of the wireless communication system 100. The wireless communication system 200 can include a UE 205, an eNB 210 (e.g., a base station associated with a legacy cellular radio network), a Wi-Fi access point (AP) 215, a gNB 220, an EPC 225, a 5GC 230, an EPDG 235, an N3IWF 240, and an IP Multimedia Subsystem (IMS) 245 (e.g., an IMS Core Network (CN) subsystem), which can be examples of respective devices described herein.

[0110] Broadly speaking, eNB 210 may be an example of any base station associated with a legacy cellular radio network (such as a 4G cellular radio network and / or a 5G NR NSA cellular radio network). Similarly, gNB 220 may be an example of any base station associated with a cellular radio network (such as a 5G NR SA cellular radio network). Wi-Fi AP 215 may be an example of an access point in a non-cellular radio network (such as a WLAN, Wi-Fi, or any other non-cellular radio network). EPC 225 may refer to the legacy core network functions of a legacy cellular radio network (e.g., a 4G cellular radio network and / or a 5G NR NSA cellular radio network). Similarly, 5GC 230 may refer to the core network functions of a cellular radio network (e.g., a 5G NR SA cellular radio network). IMS 245 may generally refer to any device, function, architectural framework, etc. that delivers IP multimedia services (e.g., IP-based voice traffic) between EPC 225, Wi-Fi AP 215, and / or 5GC 230 and the Internet.

[0111] When UE 205 acts as a Wi-Fi-only UE, it can connect to Wi-Fi AP 215 to exchange traffic via Wi-Fi AP 215 and via IMS 245. When UE 205 is connected to eNB 210 (e.g., UE 205 is connected to a legacy cellular radio network), it can exchange traffic with IMS 245 via eNB 210 and EPC 225. If UE 205 is connected to gNB 220 (e.g., UE 205 is connected to a cellular radio network), it can exchange traffic with IMS 245 via gNB 220 and 5GC 230. However, in some scenarios, accessing IMS 245 via a Wi-Fi network may be more beneficial for UE 205. UE 205 may be configured with various policies, protocols, functions, entities, etc. that allow UE 205 to route traffic to IMS 245 via a gateway between Wi-Fi AP 215 and corresponding core network functions.

[0112] UE 205 may be connected to eNB 210 and / or gNB 220 and may be provided or otherwise identified with a legacy access policy and / or access policy, respectively. A non-limiting example of a legacy access policy may include an ANDSF. Broadly speaking, ANDSF may refer to an entity within EPC 225. The purpose of ANDSF is to assist UE 205 in discovering non-3GPP access networks (e.g., 4G / 5G NR NSA) that can be used for data communication (e.g., to discover non-cellular radio networks such as WLAN, Wi-Fi networks, etc.). In addition, ANDSF may provide UE 205 with rules governing connections to such non-cellular radio networks. For example, UE 205 may be within the coverage area of ​​both eNB 210 and Wi-Fi AP 215, but may initially connect to eNB 210 to communicate via a legacy cellular radio network. Upon connecting to the eNB 210 (and in some examples, the gNB 220), the UE 205 may be provided with an ANDSF legacy access policy that identifies or otherwise informs the UE 205 of a preference for PDU traffic over non-3GPP connections. When the UE 205 is within the coverage area of ​​the Wi-Fi AP 215, it may connect to the Wi-Fi AP 215 and then establish a connection to the legacy core network function (e.g., EPC 225) via the EPDG 235 gateway. Of course, the ANDSF may inform the UE 205 of a preference for PDU traffic over a 3GPP connection (such as a connection to the EPC 225 via the eNB 210).

[0113] As another example, UE 205 may connect to gNB 220 and be provided with or otherwise identified an access policy. A non-limiting example of an access policy includes a URSP. Broadly speaking, UE 205 may use the URSP to determine how to route outgoing traffic. Traffic may be routed to an established PDU session (e.g., via gNB 220 with 5GC), offloaded to a non-3GPP access (e.g., to a non-cellular radio network, such as a Wi-Fi network), or may trigger the establishment of a new PDU session. Similarly, UE 205 may be provided with or otherwise identified a gateway selection policy, such as an ANDSP. Broadly speaking, the ANDSP is used by UE 205 to select a non-3GPP access network (e.g., any non-cellular radio network, such as a Wi-Fi network). The ANDSP may include rules that assist UE 205 in selecting a WLAN access network. For example, UE 205 may be within the coverage area of ​​both gNB 220 and Wi-Fi AP 215, but may initially connect to gNB 220 to communicate via the cellular radio network. Upon connecting to the gNB 220, the UE 205 may be provisioned with a URSP access policy that identifies or otherwise informs the UE 205 of a preference for PDU traffic over non-3GPP connections (such as Wi-Fi networks). Furthermore, the ANDSP access policy may assist the UE 205 in selecting an appropriate non-3GPP access network. When the UE 205 is within the coverage area of ​​the Wi-Fi AP 215 and the ANDSP assists the UE 205 in identifying the Wi-Fi AP 215 as an acceptable non-3GPP access network, the UE 205 may connect to the Wi-Fi AP 215 and then establish a connection to a core network function (e.g., 5GC 230) via the N3IWF 240 gateway. Of course, the URSP may inform the UE 205 of a preference for PDU traffic over a 3GPP connection (such as a connection to the 5GC 230 via the gNB 220).

[0114] While such technology may be agreed upon by the relevant regulatory standards bodies and configured for use with the UE 205, there may be circumstances where one or more entities and / or policies have not yet been implemented or otherwise configured for use. That is, the deployment of heterogeneous networks such as the wireless communication system 200 may be an ongoing process. For example, a legacy cellular radio network (e.g., a 4G radio network) may be deployed separately, but primarily concurrently with a non-3GPP access network (such as a Wi-Fi network). The 5G NR NSA cellular radio network may be deployed after the 4G radio network. The 5G NR SA cellular radio network may be deployed last, and in some aspects, this deployment may be ongoing.

[0115] In some cases, this can result in a discrepancy between how connectivity is configured and how it can be achieved. As an example, many network operators deploying 5G NR SA cellular radio networks in various regions may not include every function, policy, entity, etc. For example, some network operators deploy 5G NR SA cellular radio networks consisting of gNB 220 and / or 5GC 230, but do not implement ANDSP and / or N3IWF 230. That is, UE 205 can establish a cellular connection with gNB 220 associated with the 5G NR SA cellular radio network. UE 205 can receive a URSP access policy for the 5G NR SA cellular radio network, which specifies the access preference for the 5GC 230 core network function that UE 205 should use to connect to the cellular radio network. In scenarios where the URSP specifies a preference for a 3GPP access network, UE 205 can simply access IMS 245 via gNB 220 and 5GC 230. However, in some examples, the UE 205 may determine that the ANDSP and / or N3IWF 240 are not configured, activated, or unavailable for the 5G NR SA cellular radio network for some other reason. This creates a discrepancy for the UE 205 regarding how to proceed when the URSP gives a preference for a non-3GPP access network. For example, when neither the ANDSP nor the N3IWF 240 are configured for the 5G NR SA cellular radio network, the UE 205 may be unable to identify the Wi-Fi AP 215 and / or connect to the 5GC 230 via the Wi-Fi AP 215 and the N3IWF 240 without the ANDSP. In general, the described techniques provide various mechanisms to address such differences and inconsistencies between legacy cellular radio networks and advanced cellular radio networks.

[0116] For example, UE 205 may establish a connection with gNB 220 associated with a cellular radio network (e.g., a 5G NR SA cellular connection). Consequently, UE 205 may receive an access policy (e.g., a URSP) identifying access preference rules for UE 205 to use to connect to a core network function (such as 5GC 230) of the cellular radio network. The URSP may indicate to UE 205 that it is preferred to connect to the 5GC via a non-cellular radio network, such as routing outgoing traffic in a PDU session via a Wi-Fi network. However, UE 205 may determine that the N3IWF 240 gateway between the Wi-Fi radio network (e.g., Wi-Fi AP 215) and 5GC 230 is not configured or is unavailable for some other reason. UE 205 may also determine that the ANDSP gateway selection policy is not configured for 5G NR SA. Thus, the UE 205 can establish a connection to a legacy core network function (e.g., an EPC 225 core network function) of a legacy cellular radio network (e.g., a 4G and / or 5G NR NSA cellular radio network) via a legacy gateway (e.g., via the EPDG 235). Thus, even though the URSP gives a preference for Wi-Fi networks and the ANDSP and N3IWF are not configured or otherwise unavailable, when no ANDSP / N3IWF 240 is configured for the 5G NR SA cellular radio network, the UE 205 can still utilize the EPDG 235 to connect to the EPC 225 core network in accordance with the URSP access policy. The UE 205 can access the IMS 245 via the EPC 225 to exchange PDU session traffic.

[0117] As another example, UE 205 may have already established a cellular connection with gNB 220 in a 5G NR SA cellular radio network. However, in this example, the URSP received by UE 205 may indicate a preference for a 3GPP connection, e.g., for routing outgoing traffic in the PDU session to the 5G NR SA cellular radio network via 5GC 230 and gNB 220. The URSP may indicate a preference for UE 205 to connect to 5GC 230 via a 5G NR SA base station (e.g., gNB 220). However, UE 205 may determine that neither the N3IWF 240 gateway nor the ANDSP gateway selection policy is configured for a cellular radio network (e.g., for a 5G NR SA cellular radio network). Subsequently, UE 205 may determine that its 5G NR SA cellular radio network has become unavailable (e.g., UE 205 has lost its connection to gNB 220), but a Wi-Fi radio network is available (e.g., UE 205 is within the coverage area of ​​Wi-Fi AP 215). In response, UE 205 may establish a connection to a legacy core network function (e.g., EPC 225) of a legacy cellular radio network (e.g., 4G / 5G NR NSA) via a legacy gateway (e.g., EPDG 235). UE 205 may identify or otherwise determine a legacy access policy (e.g., ANDSF) that prefers the UE 205 to use a non-cellular radio network (e.g., a Wi-Fi network). However, UE 205 may determine that a 5G NR SA cellular radio network has become available again and therefore establish a new connection to that cellular radio network. That is, even though the ANDSF instructs UE 205 to prefer a Wi-Fi network, the UE 205 will adhere to the preference given in the URSP and re-establish its connection to the 5G NR NSA cellular radio network via gNB 220 when the 5G NR SA cellular radio network becomes available again. Otherwise, UE 205 may be forced to use a Wi-Fi connection even if a more advanced 5G NR SA network is available.

[0118] As another example, the UE 205 may establish a cellular connection to a 5G NR SA cellular radio network (e.g., a connection to the 5GC 230 via the gNB 220) and receive a URSP access policy that, in this example, gives a preference for non-cellular radio networks (e.g., a preference for non-3GPP networks such as Wi-Fi networks). Similarly, the UE 205 may determine that both the ANDSP and the N3IWF 240 are not configured or otherwise available for the 5G NR SA cellular radio network, but that the Wi-Fi network is available. Therefore, the UE 205 may establish a connection to the EPC 225 legacy core network function of the 4G / 5G NR NSA legacy cellular radio network via the EPDG 235 legacy gateway. The UE 205 may receive or otherwise identify the ANDSF legacy access policy that, in this example, gives a preference for 3GPP connections. Previously, the UE 205 would switch back and forth between the 5G NR SA connection and the Wi-Fi connection when both were available. That is, the URSP prefers Wi-Fi while the ANDSF prefers cellular, meaning that the UE 205 will connect to the URSP, which triggers the UE 205 to establish a Wi-Fi connection. While connected to Wi-Fi, the UE 205 will be given the ANDSF's preference for cellular connections. Due to the difference between the two access policies, the UE 205 will switch back and forth between Wi-Fi and cellular radio network connections. However, to avoid this switching, the UE 205 can maintain a connection to the EPC 225 legacy core network functions via the EPDG 235 legacy gateway. As discussed, since the N3IWF 240 and ANDSP have not yet been configured or otherwise made available for use on the 5G NR SA cellular radio network, the UE 205 can maintain a connection to the EPC 225 legacy core network functions via the EPDG 235. This approach can prevent the UE 205 from constantly or frequently switching between a 5G NR SA network, where the URSP gives a preference for non-3GPP connections, and a Wi-Fi network, where the ANDSF gives a preference for 3GPP connections.

[0119] Another approach for one or more of the above scenarios may include the gNB 220 providing out-of-band signaling to the UE 205 via Open Mobile Alliance (OMA) Device Management (DM) signaling to identify a connection preference for the UE 205 to employ. For example, the gNB 220 may transmit a configuration signal to the UE 205 for connection via a non-cellular radio network. The configuration signal may configure the UE 205 to connect to a legacy core network function (e.g., EPC 225) via the non-cellular radio network. For example, the configuration signal may configure the UE 205 to attempt to connect to the EPC 225 via the EPDG 235 when on Wi-Fi access. The configuration signal may configure the UE 205 to attempt to connect to the 5GC 230 via the N3IWF 240 when on Wi-Fi access. In one example, the configuration signal may configure the UE 205 to attempt to connect to the N3IWF 240 when on Wi-Fi access, but if that attempt is unsuccessful, to attempt to connect to the EPDG 235 when on Wi-Fi access. Thus, the configuration signal may provide more explicit guidance for the UE 205 to take for connecting to a core network function (e.g., the EPC 225 or the 5GC 230).

[0120] Another difference that may arise in this heterogeneous network involves features implemented in 5G NR SA cellular radio networks, rather than in legacy cellular radio networks or non-3GPP access networks. One example of such functionality involves slicing within 5G NR SA cellular radio networks. That is, cellular radio networks generally support or can be multi-service networks that support a variety of traffic descriptors with a wide range of performance and service requirements. Slicing allows network operators to provide portions of their networks for specific customer use cases (such as smart homes, Internet of Things (IoE), IoT factories, connected cars, etc.). Each use case (e.g., slice) generally receives a unique set of optimized resources and network topology tailored to the application (also referred to as a common traffic descriptor) requirements (such as connectivity, speed, capacity, throughput, latency, reliability, etc.). Thus, a user can pay for a slice's processing of a specific application / traffic descriptor, and the network operator guarantees that the slice's processing meets that application / traffic descriptor.

[0121] This feature can create differences for UE 205 when dealing with heterogeneous networks, such as wireless communication system 200. For example, while a 5G NR SA cellular radio network may support slicing, a 4G / 5G NR NSA legacy cellular radio network may not "speak" slicing in the same language as a 5G NR SA cellular radio network. That is, a 4G / 5G NR NSA cellular radio network may not be provisioned or otherwise support slicing for traffic descriptors in the same manner as a 5G NR SA cellular radio network. This can result in the user of UE 205 being charged for slicing that a network operator may have difficulty providing when UE 205 is connected to EPC 225 via EPDG 235 while on a Wi-Fi network.

[0122] Thus, aspects of the described technology provide various mechanisms for a UE 205 to employ when handling slices in a heterogeneous network. For example, the UE 205 may establish a connection to the EPC 225 legacy core network function of a 4G / 5G NR NSA legacy cellular radio network via the EPDG 235 legacy gateway. The UE 205 may be configured with a set of traffic descriptors (e.g., the UE 205 may operate different applications, each application having one or more associated traffic descriptors). For each traffic descriptor (e.g., each application), the UE 205 may identify an ANDSF legacy access policy that gives a preference for whether the UE 205 connects via a cellular radio network (e.g., a 3GPP cellular radio network) or a non-cellular radio network (e.g., a non-3GPP radio network, such as a Wi-Fi network). The UE 205 may also identify or otherwise determine, for example, the legacy slice handling associated with each traffic descriptor based at least in part on the connection to the EPC 225 via the EPDG 235. Legacy slicing can generally refer to performance characteristics provided for a traffic descriptor, such as latency requirements, priority, reliability requirements, and the like. UE 205 can establish a connection to a 5GC 230 core network function of a 5G NR SA cellular radio network. Accordingly, UE 205 can receive or otherwise identify a URSP access policy for UE 205 to employ, which also informs UE 205 whether to preferably connect via a cellular radio network or a non-cellular radio network. UE 205 can also determine or otherwise identify slicing for each traffic descriptor based, for example, at least in part on the URSP access policy, a traffic descriptor identifier, a traffic descriptor type, and the like. Therefore, the UE 205 can use the URSP access policy, the legacy slice handling (from the EPC 225), and / or the slice handling (from the 5GC 230) to determine whether to transfer the connection for each traffic descriptor from the EPC 225 via the EPDG 235 gateway to the 5GC 230 or to establish an updated connection with the 5GC 230 via the N3IWF 240 gateway. Thus, the UE 205 can ensure that each traffic descriptor is given the appropriate slice handling and / or connection preference when switching from the EPC 225 connection to the 5GC 230 connection.

[0123] Figure 3An example of a process 300 for supporting a method for handling slices that account for Evolved Packet Data Gateway (EPDG) Wi-Fi access according to aspects of the present disclosure is illustrated. In some examples, process 300 can implement aspects of wireless communication systems 100 and / or 200. Aspects of process 300 can be implemented by UE 305, 5GC 310, and / or EPC 315, which can be examples of corresponding devices described herein. It will be understood that UE 305 can connect to 5GC 310 via a 5G NR SA base station and / or via a Wi-Fi AP and N3IWF gateway when UE 305 is connected to a non-3GPP access network, such as a Wi-Fi network. Similarly, UE 305 can connect to EPC 315 via a Wi-Fi AP and an EPDG legacy gateway when UE 305 is connected to a non-3GPP access network, such as a Wi-Fi network.

[0124] As discussed above, various aspects of the described technology provide mechanisms for UE 305 to address differences in heterogeneous networks. For example, URSP access policies (e.g., non-3GPP or Wi-Fi access policies) were originally intended to support UE 305 connecting to 5GC 310 via an N3IWF gateway. URSP was subsequently modified to include an EPDG for connecting to EPC 315 via an EPDG gateway, but to allow the ANDSP gateway to select a policy that instructs or otherwise guides the UE 305 to select the node that the UE 305 uses. However, neither the N3IWF nor the ANDSF are deployed or otherwise configured for many 5G NR SA cellular radio networks. This creates the following problem: how does the UE 305 know whether URSP rules related to non-3GPP (e.g., Wi-Fi) access are even relevant, as many operators have not yet deployed N3IWF gateways and / or ANDSPs. For operators that have deployed ANDSF for legacy cellular radio networks (e.g., 4G / 5G NR NSA), the guidance indicates that if a UE 305 is registered to the 5GC 310 via 3GPP access and to the EPC 310 via non-3GPP access, the UE 305 may use ANDSF rules and radio access network (RAN) rules (if available at the UE 305) for uplink user data sent via the EPDG, and apply URSP rules and applicable user preferences (if available at the UE 305) to all its uplink user data.

[0125] However, this creates a bootstrapping problem for UE 305. Specifically, how does UE 305 first decide whether to register with EPC 315 and which uplink user data should be sent via the EPDG? This leads to a looping logic scenario for UE 305. Specifically, to select the correct policy to follow, UE 305 needs to determine which uplink data should be delivered via the EPDG. However, the guidance standard indicates to UE 305 that ANDSP should be used to decide between the EPDG or N3IWF, but ANDSP may not be deployed. Process 300 illustrates a non-limiting example of how UE 305 can resolve this scenario.

[0126] At 320, UE 305 may register with 5GC 310. That is, UE 305 may establish a cellular connection with a base station associated with a cellular radio network (e.g., a 5G NR SA base station). For example, UE 305 may start up in a 5G NR SA radio coverage area and connect to the 5GC 310 core network using non-access stratum (NAS) signaling.

[0127] At 325, UE 305 may be configured with a URSP policy for the cellular network. That is, UE 305 may receive an access policy (e.g., URSP) for the cellular radio network from the network via the base station, the access policy identifying access preference rules for UE 305 to use for connecting to a core network function (e.g., 5GC 310) of the cellular radio network. The URSP may indicate to UE 305 that it is preferred to connect to the core network function via a non-cellular radio network (e.g., preferably a non-3GPP access network, such as a Wi-Fi network). Thus, the network may download the URSP policy to UE 305.

[0128] At 330, the URSP may be installed for UE 305. That is, the network may have downloaded the URSP policy to UE 305. At this point, and in accordance with the guidelines, UE 305 should only refer to the URSP for its policy. One of the rules specified in the URSP is whether the preferred access is 3GPP (e.g., cellular) or non-3GPP (e.g., Wi-Fi) for each Data Network Name (DNN). For example, the URSP rules may look like:

[0129] Traffic Descriptor: DNN-Name = DNN1

[0130] RouteSelectionDescriptor: Access-Preference = Non-3GPP

[0131] Access-Preference = 3GPP

[0132] This rule may mean that when UE 305 is in an area with both 5G and Wi-Fi coverage, the network operator wants to connect to DNN1 via Wi-Fi access (if possible). However, if UE 305 is not in a Wi-Fi coverage area (or has any other problem connecting to the Wi-Fi network), the network operator wants UE 305 to establish its connection to 5GC 310 via 5G.

[0133] At 335, UE 305 may determine that it has entered an area of ​​Wi-Fi coverage in addition to the 5G NR SA cellular radio network. That is, UE 305 may have entered an area where Wi-Fi coverage exists in addition to 5G NR coverage. However, in accordance with guidance standards for URSP, a UE 305 accessing a non-3GPP coverage area that includes an N3IWF or EPDG may assume that an ANDSP gateway selection policy will be available to the UE 305 to select which gateway to use. As previously discussed, some 5G NR SA cellular radio networks are not configured with an N3IWF and / or ANDSP (e.g., the operator has not deployed or otherwise activated these features). Therefore, UE 305 may determine that an N3IWF gateway and / or ANDSP gateway selection policy is not configured for its 5G NR SA cellular radio network connection. According to the described techniques, the UE 305 can consider non-3GPP access to be access via Wi-Fi and EPDG to obtain access to the EPC 315 (e.g., to obtain access to the 4G EPC) to resolve the bootstrapping issue discussed above. When the UE 305 encounters a URSP rule that prefers a non-3GPP access network (e.g., a Wi-Fi network), these techniques direct the UE 305 to connect to the EPC 315 via the EPDG legacy gateway. If the connection is successful, the UE 305 can then follow the content specified in the guidance standard and continue using the ANDSF legacy access policy.

[0134] Therefore, at 340, UE 305 may establish a connection for DNN1 with EPC 315 via the EPDG gateway. That is, UE 305 may establish a connection with a Wi-Fi AP and then access EPC 315 via the EPDG legacy gateway located between the Wi-Fi AP and EPC 315.

[0135] As also discussed above, in some examples, the network (e.g., via the base station using out-of-band signaling) may configure UE 305 with values ​​corresponding to:

[0136] 0 - Only try to connect to the EPDG when on Wi-Fi access

[0137] 1-Only try to connect to N3IWF when on Wi-Fi access

[0138] 2- When on Wi-Fi access, try to connect to N3IWF first, but if that connection attempt is unsuccessful, try to connect to EPDG

[0139] For example, the base station may transmit a configuration signal to the UE 305 for connection via a non-cellular radio network, which configures how the UE 305 attempts to connect to the N3IWF gateway to the 5GC 310 core network function of the 5G NR SA cellular radio network and / or the EPDG legacy gateway to the EPC 315 legacy core network function of the 4G / 5G NR NSA legacy cellular radio network.

[0140] Figure 4 An example of a process 400 supporting a method for handling slices that account for Evolved Packet Data Gateway (EPDG) Wi-Fi access according to aspects of the present disclosure is illustrated. In some examples, process 400 can implement aspects of wireless communication systems 100 and / or 200 and / or process 300. Aspects of process 400 can be implemented by UE 405, 5GC 410, and / or EPC 415, which can be examples of corresponding devices described herein. It will be understood that UE 405 can connect to 5GC 410 via a 5G NR SA base station and / or via a Wi-Fi AP and N3IWF gateway when UE 405 is connected to a non-3GPP access network, such as a Wi-Fi network. Similarly, UE 405 can connect to EPC 415 via a Wi-Fi AP and an EPDG legacy gateway when UE 405 is connected to a non-3GPP access network, such as a Wi-Fi network.

[0141] As discussed above, various aspects of the described technology provide mechanisms for UE 405 to address differences in heterogeneous networks. For example, URSP access policies (e.g., non-3GPP or Wi-Fi access policies) were originally intended to support UE 405 connecting to 5GC 410 via an N3IWF gateway. URSP was subsequently modified to include an EPDG for connecting to EPC 415 via an EPDG gateway, but to allow the ANDSP gateway to select a policy that instructs or otherwise guides the UE 405 to select the node that the UE 405 uses. However, neither the N3IWF nor the ANDSF are deployed or otherwise configured for many 5G NR SA cellular radio networks. This creates the following problem: how does the UE 405 know whether URSP rules related to non-3GPP (e.g., Wi-Fi) access are even relevant, as many operators have not yet deployed N3IWF gateways and / or ANDSPs. For operators that have deployed ANDSF for legacy cellular radio networks (e.g., 4G / 5G NR NSA), the guidance indicates that if a UE 405 is registered to the 5GC 415 via 3GPP access and to the EPC 410 via non-3GPP access, the UE 405 may use ANDSF rules and RAN rules (if available at the UE 405) for uplink user data sent via the EPDG, and apply URSP rules and applicable user preferences (if available at the UE 405) to all its uplink user data.

[0142] However, this creates a bootstrapping problem for UE 405. That is, UE 405 may not know how to initially decide whether to register with EPC 415 or which uplink user data should be sent via the EPDG. This leads to a looping logic scenario for UE 405. That is, in order to select the correct policy to follow, UE 405 may need to determine which uplink data should be communicated via the EPDG and EPC 415. However, the guiding standards indicate to UE 405 that ANDSP should be used to decide between the EPDG or N3IWF, but ANDSP may not be deployed. Process 400 illustrates a non-limiting example of how UE 405 can resolve this scenario.

[0143] At 420, UE 405 may be provisioned or otherwise identify its ANDSF policy. UE 405 may identify the ANDSF legacy access policy based at least in part on a permanent configuration (e.g., pre-configured for UE 405), via RRC signaling, etc. Examples of ANDSF policies may be:

[0144] ANDSF Inter-System Routing Policy (ISRP) configured as:

[0145] ANDSF / ISRP / <x> / ForServiceBased(For service-based) / access point name one(APN1) / APN

[0146] ANDSF / Policy / <x>Prioritized Access (Priority Access) / WLAN / Access Technology (Access Technology)

[0147] ANDSF / ISRP / <x> / ForServiceBased / APN1 / APN

[0148] ANDSF / Policy / <x> / PrioritizedAccess / 3gpp / AccessTechnology

[0149] The ANDSF legacy access policy may indicate to the UE 405 that a preference is given to non-3GPP access networks (e.g., Wi-Fi networks). That is, the ANDSF rule indicates that when the UE 405 is in the coverage area of ​​both the 4G / 5G NR NSA legacy cellular radio network and the Wi-Fi network, the network operator wants to connect to the DNN1 via the Wi-Fi access network (if possible). However, if the UE 405 is not in the Wi-Fi coverage area or has any difficulty connecting to the Wi-Fi network, the UE 405 may utilize the legacy cellular radio network to connect to the EPC 415 via the EPDG legacy gateway.

[0150] At 425, UE 405 may register with 5GC 410. That is, UE 405 may establish a cellular connection with a base station associated with a cellular radio network (e.g., a 5G NR SA base station). For example, UE 405 may start up in a 5G NR SA radio coverage area and use NAS signaling to connect to the 5GC 410 core network.

[0151] At 430, UE 405 may be configured with a URSP policy for the cellular network. That is, UE 405 may receive an access policy (e.g., URSP) for the cellular radio network from the network via the base station, the access policy identifying access preference rules for UE 405 to use for connecting to a core network function (e.g., 5GC 410) of the cellular radio network. The URSP may indicate to UE 405 that it is preferred to connect to the core network function via the cellular radio network (e.g., UE 405 may prefer a 3GPP access network, such as a 5GNR SA network). Accordingly, the network may download the URSP policy to UE 405.

[0152] At 435, the URSP may be installed for UE 405. That is, the network may have downloaded the URSP policy to UE 405. At this point, and according to the guidelines, UE 405 should only refer to the URSP for its policy. One of the rules specified in the URSP is whether the preferred access is 3GPP (e.g., cellular) or non-3GPP (e.g., Wi-Fi) for each DNN. For example, the URSP rules may look like:

[0153] Traffic Descriptor:DNN-Name=DNN1

[0154] RouteSelectionDescriptor:Access-Preference=3GPP

[0155] Access-Preference=Non-3GPP

[0156] This rule may mean that when UE 405 is in an area with both 5G and Wi-Fi coverage, the network operator wants to connect to DNN1 via 5G access (if possible). However, if UE 405 is not in a 5G coverage area (or has any other problem connecting to the 5G network), the network operator wants UE 405 to establish its connection to 5GC 410 via Wi-Fi.

[0157] At 440, UE 405 may determine that it has entered an area of ​​Wi-Fi coverage but no 5G NR SA cellular radio network coverage. That is, UE 405 may have entered an area where only Wi-Fi coverage exists but no 5G NR coverage (e.g., UE 405 may have lost its 5G connection). However, in accordance with guidance standards for URSP, UE 405 accessing a non-3GPP coverage area that includes an N3IWF or EPDG may assume that an ANDSP gateway selection policy will be available to the UE 405 to select which gateway to use. As previously discussed, some 5G NR SA cellular radio networks are not configured with an N3IWF and / or ANDSP (e.g., the operator has not deployed or otherwise activated these features). Therefore, UE 405 may determine that an N3IWF gateway and / or ANDSP gateway selection policy is not configured for its 5G NR SA cellular radio network connection. According to the described techniques, the UE 405 can consider non-3GPP access to be access via Wi-Fi and EPDG to obtain access to the EPC 415 (e.g., to obtain access to the 4G EPC) to resolve the bootstrapping issue discussed above. When the UE 405 encounters a URSP rule that prefers a non-3GPP access network (e.g., a Wi-Fi network), these techniques direct the UE 405 to connect to the EPC 415 via the EPDG legacy gateway. If the connection is successful, the UE 405 can then follow the content specified in the guidance standard and continue using the ANDSF legacy access policy.

[0158] Therefore, at 445, UE 405 may establish a connection for DNN1 with EPC 415 via the EPDG gateway. That is, UE 405 may establish a connection with the Wi-Fi AP and then access EPC 415 via the EPDG legacy gateway located between the Wi-Fi AP and EPC 415.

[0159] Following the rules discussed with respect to process 300, UE 405 may use the EPDG legacy gateway to access EPC 415 via its connection according to the second preference provided in the URSP rules installed at 435. However, UE 405 may now begin to follow the ANDSF rules received at 420, which give a preference for Wi-Fi connections. At this point, UE 405 connects to EPC 410 via the EPDG legacy gateway and according to its ANDSF legacy access rules. However, this may cause problems for UE 405 if UE 405 enters a 5G NR SA coverage area again.

[0160] That is, the network operator's intention (e.g., according to the URSP access policy) is for DNN1 to give preference to 5G when the 5G network is available and to use only Wi-Fi networks if the 5G network is not available. However, once UE 405 connects to EPC 415 via the EPDG legacy gateway and 5G coverage is lost, UE 405 follows the ANDSF legacy access policy, which gives preference to EPC 415's Wi-Fi network for connecting to the 4G network. UE 405 may follow the guidance standards discussed above, which instruct UE 405 to use ANDSF rules and RAN rules (if available at UE 405) for uplink user data sent via the EPDG legacy gateway. In the event that UE 405 once again enters 5G coverage, if the UE 405 blindly follows the ANDSF legacy access policy, it will not attempt to establish a new connection to the 5G network. This may deny UE 405 the opportunity to reconnect to the 5G network if it becomes available.

[0161] However, according to the described techniques, UE 405 can establish a new connection to a 5G NR SA cellular radio network once it becomes available again. That is, the described techniques allow UE 405 to start using the URSP access policy again when the 5G network is available and registered for UE 405, rather than following the guidelines discussed above. UE 405 can do this even if it already is using an EPDG legacy gateway over a Wi-Fi connection for data transmission. If the URSP access policy rules indicate that 5G is preferred, UE 405 can attempt to handover DNN1 to 5GC 410.

[0162] Thus, at 450, UE 405 may determine that a cellular radio network (e.g., a 5G NR SA cellular radio network) has become available again and may attempt to establish a new connection with the cellular radio network. Thus, at 455, UE 405 may register with 5GC 410 (e.g., UE 405 may connect to a base station associated with the 5G NR SA cellular radio network and connect to 5GC 410 via the base station). At 460, UE 405 may switch to a URSP access policy that gives a preference for 3GPP access networks. Thus, at 465, UE 405 may switch the DNN1 connection from EPC 415 to 5GC 410. That is, although the guiding standards instruct UE 405 to follow the ANDSF legacy access policy and give a preference for Wi-Fi connections when available, UE 405 may reconnect to the 5G network when the 5G network becomes available again. Because 5G networks may have better performance characteristics than 4G and / or Wi-Fi networks, this may ensure that UE 405 is able to connect to the most capable network available.

[0163] In a scenario where the N3IWF gateway and ANDSP are configured for a new connection to the 5G NR SA cellular radio network and the updated URSP rules given at 460 give a preference for non-3GPP, the UE 405 may transfer the DNN1 connection to the 5GC 410 from the EPC 415 via the EPDG legacy gateway to the 5GC 410 via the N3IWF gateway.

[0164] As also discussed above, in some examples, the network (e.g., via the base station using out-of-band signaling) may configure UE 405 with values ​​corresponding to:

[0165] 0 - Only try to connect to the EPDG when on Wi-Fi access

[0166] 1-Only try to connect to N3IWF when on Wi-Fi access

[0167] 2- When on Wi-Fi access, try to connect to N3IWF first, but if that connection attempt is unsuccessful, try to connect to EPDG

[0168] For example, the base station may transmit a configuration signal to the UE 405 for connection via a non-cellular radio network, which configures how the UE 405 attempts to connect to the N3IWF gateway to the 5GC 410 core network function of the 5G NR SA cellular radio network and / or the EPDG legacy gateway to the EPC 415 legacy core network function of the 4G / 5G NR NSA legacy cellular radio network.

[0169] Figure 5 An example of a process 500 supporting a method for handling slices that account for Evolved Packet Data Gateway (EPDG) Wi-Fi access according to aspects of the present disclosure is illustrated. In some examples, process 500 can implement aspects of wireless communication systems 100 and / or 200 and / or processes 300 and / or 400. Aspects of process 500 can be implemented by UE 505, 5GC 510, and / or EPC 515, which can be examples of corresponding devices described herein. It will be understood that UE 505 can connect to 5GC 510 via a 5G NR SA base station and / or via a Wi-Fi AP and N3IWF gateway when UE 505 is connected to a non-3GPP access network, such as a Wi-Fi network. Similarly, UE 505 can connect to EPC 515 via a Wi-Fi AP and an EPDG legacy gateway when UE 505 is connected to a non-3GPP access network, such as a Wi-Fi network.

[0170] As discussed above, various aspects of the described technology provide mechanisms for UE 505 to address differences in heterogeneous networks. For example, URSP access policies (e.g., non-3GPP or Wi-Fi access policies) were originally intended to support UE 505 connecting to 5GC 510 via an N3IWF gateway. URSP was subsequently modified to include an EPDG for connecting to EPC 515 via an EPDG gateway, but to allow the ANDSP gateway selection policy to instruct or otherwise guide the UE 505 in selecting the node to use. However, both the N3IWF and the ANDSF are not deployed or otherwise configured for many 5G NR SA cellular radio networks. This creates the following problem: how does the UE 505 know whether URSP rules related to non-3GPP (e.g., Wi-Fi) access are even relevant, as many operators have not yet deployed N3IWF gateways and / or ANDSPs. For operators that have deployed ANDSF for legacy cellular radio networks (e.g., 4G / 5G NR NSA), the guidance indicates that if a UE 505 is registered to the 5GC 510 via 3GPP access and to the EPC 510 via non-3GPP access, the UE 505 may use ANDSF rules and RAN rules (if available at the UE 505) for uplink user data sent via the EPDG, and apply URSP rules and applicable user preferences (if available at the UE 505) to all its uplink user data.

[0171] However, this creates a bootstrapping problem for UE 505. Specifically, how does UE 505 first decide whether to register with EPC 515 and which uplink user data to send via EPDG? This leads to a looping logic scenario for UE 505. Specifically, in order to select the correct policy to follow, UE 505 needs to determine which uplink data should be communicated via EPDG and EPC 515. However, the guiding standards instruct UE 505 to use ANDSP to decide between EPDG or N3IWF, but ANDSP may not be deployed.

[0172] At 520, the UE 505 may be provisioned or otherwise identify its ANDSF policy. The UE 505 may identify the ANDSF legacy access policy based at least in part on a permanent configuration (e.g., pre-configured for the UE 505), via RRC signaling, etc. Examples of ANDSF policies may be:

[0173] ANDSF ISRP is configured as follows:

[0174] ANDSF / ISRP / <x> / ForServiceBased / APN1 / APN

[0175] ANDSF / Policy / <x>PrioritizedAccess / 3gpp / AccessTechnology

[0176] ANDSF / ISRP / <x> / ForServiceBased / APN1 / APN

[0177] ANDSF / Policy / <x> / PrioritizedAccess / WLAN / AccessTechnology

[0178] The ANDSF legacy access policy may indicate to the UE 505 that a preference is given to a 3GPP access network (e.g., a 5G network). That is, the ANDSF rule may indicate that when the UE 505 is in the coverage area of ​​both the 4G / 5G NR NSA legacy cellular radio network and the Wi-Fi network, the network operator wants to connect to the DNN1 via the 3GPP access network (if possible). However, if the UE 505 is not in a 5G coverage area or has any difficulty connecting to the 5G network, the UE 505 may utilize a non-3GPP access network to connect to the EPC 515 via the EPDG legacy gateway.

[0179] At 520, the UE 505 may determine that it is in the coverage area of ​​5G NR SA, 4G / 5G NR NSA, and Wi-Fi networks.

[0180] Thus, at 530, UE 505 may register with 5GC 510. That is, UE 505 may establish a cellular connection with a base station associated with a cellular radio network (e.g., a 5G NR SA base station). For example, UE 505 may start up in a 5G NR SA radio coverage area and use NAS signaling to connect to the 5GC 510 core network.

[0181] At 535, UE 505 may be configured with a URSP policy for the cellular network. That is, UE 505 may receive an access policy (e.g., URSP) for the cellular radio network from the network via the base station, the access policy identifying access preference rules for UE 505 to use for connecting to a core network function (e.g., 5GC 510) of the cellular radio network. The URSP may indicate to UE 505 that it is preferred to connect to the core network function via a non-cellular radio network (e.g., preferably a non-3GPP access network, such as a Wi-Fi network). Therefore, the network may download the URSP policy to UE 505.

[0182] Therefore, the URSP may be installed for UE 505. That is, the network may have downloaded the URSP policy to UE 505. At this point, and according to the guidelines, UE 505 should only refer to the URSP for its policy. One of the rules specified in the URSP is whether the preferred access is 3GPP (e.g., cellular) or non-3GPP (e.g., Wi-Fi) for each DNN. For example, the URSP rule may look like:

[0183] Traffic Descriptor:DNN-Name=DNN1

[0184] RouteSelectionDescriptor:Access-Preference=Non-3GPP

[0185] Access-Preference = 3GPP

[0186] This rule may mean that when UE 505 is in an area with both 5G and Wi-Fi coverage, the network operator wants to connect to DNN1 via the Wi-Fi access network (if possible). However, if UE 505 is not in a Wi-Fi coverage area (or has any other problem connecting to the Wi-Fi network), the network operator wants UE 505 to establish its connection to 5GC 510 via the 5G access network.

[0187] Thus, the network operator may configure the ANDSF legacy access policy to be the opposite of the URSP policy (e.g., ANDSF prefers 3GPP over Wi-Fi, while URSP prefers Wi-Fi over 3GPP). One possible reason for this configuration is that the operator wants the policy to be that if the UE 505 has the option of a 5G and WLAN network, WLAN is selected because the 5G network may have spotty coverage during the early deployment period. However, if the UE 505 has the option of a 4G / 5G NR NSA or WLAN network, the 4G / 5G NR NSA network may be selected because it is a mature, stable network with a larger coverage area. However, this misconfiguration may result in a situation where the UE 505 keeps switching back and forth between 5G and WLAN if it is in the coverage area of ​​all three networks at the same time because the URSP prefers Wi-Fi and once connected to the EPC 515 via the EPDG legacy gateway, the ANDSF prefers a 3GPP connection. If these network operators deploy the N3IWF gateway and ANDSP within the 5G NR SA cellular radio network, this problem may have been avoided because the UE 505 would only have to rely on the URSP.

[0188] Therefore, according to the URSP, at 540, UE 505 can establish a connection for DNN1 with EPC 515 via the EPDG gateway. That is, UE 505 can establish a connection with the Wi-Fi AP and then access EPC 515 via the EPDG legacy gateway located between the Wi-Fi AP and EPC 515.

[0189] According to the described techniques, UE 505 can maintain its connection for DNN1 with EPC 515 via the EPDG gateway at 545. That is, although the ANDSF legacy access policy directs UE 505 to preferably connect to the 3GPP cellular radio network, UE 505 can continue to follow the URSP access policy and maintain its connection for DNN1 on EPC 515.

[0190] As also discussed above, in some examples, the network (e.g., via the base station using out-of-band signaling) may configure UE 405 with values ​​corresponding to:

[0191] 0 - Only try to connect to the EPDG when on Wi-Fi access

[0192] 1-Only try to connect to N3IWF when on Wi-Fi access

[0193] 2- When on Wi-Fi access, try to connect to N3IWF first, but if that connection attempt is unsuccessful, try to connect to EPDG

[0194] For example, the base station may transmit a configuration signal to the UE 505 for connection via a non-cellular radio network, which configures how the UE 505 attempts to connect to the N3IWF gateway to the 5GC 510 core network function of the 5G NR SA cellular radio network and / or the EPDG legacy gateway to the EPC 515 legacy core network function of the 4G / 5G NR NSA legacy cellular radio network.

[0195] Figure 6 An example of a process 600 supporting a method for handling slices that account for Evolved Packet Data Gateway (EPDG) Wi-Fi access according to aspects of the present disclosure is illustrated. In some examples, process 600 can implement aspects of wireless communication systems 100 and / or 200 and / or processes 300, 400, and / or 500. Aspects of process 600 can be implemented by UE 605, 5GC 610, and / or EPC 615, which can be examples of corresponding devices described herein. It will be understood that UE 605 can connect to 5GC 610 via a 5G NR SA base station and / or via a Wi-Fi AP and N3IWF gateway when UE 605 is connected to a non-3GPP access network, such as a Wi-Fi network. Similarly, UE 605 can connect to EPC 615 via a Wi-Fi AP and an EPDG legacy gateway when UE 605 is connected to a non-3GPP access network, such as a Wi-Fi network.

[0196] In some aspects, the UE 605 may include a set of applications, of which two applications are shown as examples. In general, each application may refer to any general traffic descriptor. Thus, the UE 605 may include a first application 625, a second application 620, and a modem 630, which may be examples of corresponding devices described herein. The modem 630 may monitor, control, or otherwise manage various aspects of communication between the UE 605 and the 5GC 610 and / or EPC 615 (e.g., via one or more base stations, Wi-Fi APs, N3IWF gateways, EPDG legacy gateways, etc.).

[0197] As discussed above, aspects of the described techniques can support a UE 605 establishing a connection to an EPC 615 legacy core network function of a 4G / 5G NR NSA legacy cellular radio network via an EPDG legacy gateway. The UE 605 can be configured with a set of traffic descriptors (e.g., the UE 605 can have different applications operating on the UE 605, such as a first application 625 and / or a second application 620). For each traffic descriptor (e.g., each application), the UE 605 can identify an ANDSF legacy access policy, such as a routing preference, that specifies whether the UE 605 connects via a cellular radio network (e.g., a 3GPP cellular radio network) or a non-cellular radio network (e.g., a non-3GPP radio network). The UE 605 can also identify or otherwise determine, for example, a legacy slice process associated with each traffic descriptor based at least in part on the connection to the EPC 615 via the EPDG. The UE 605 may establish a connection to the 5GC 610 core network function of the 5G NR SA cellular radio network via the N3IWF gateway. Thus, the UE 605 may receive or otherwise identify a URSP access policy for the UE 605 to adopt, which also informs the UE 605 whether to preferably connect via the cellular radio network or the non-cellular radio network. The UE 605 may also determine or otherwise identify a slice handling for each traffic descriptor based, for example, at least in part on the URSP access policy, the traffic descriptor identifier, the traffic descriptor type, etc. Thus, the UE 605 may use the URSP access policy, the legacy slice handling (from the EPC 615), and / or the slice handling (from the 5GC 610) to determine whether to transfer the connection for each traffic descriptor (e.g., application) from the EPC 615 via the EPDG gateway to the 5GC 610 via the N3IWF gateway or to establish an updated connection with the 5GC 610 via the N3IWF. Thus, the UE 605 can ensure that each traffic descriptor is given appropriate slice processing and / or connection preference when switching from an EPC 615 connection to a 5GC 610 connection.

[0198] Thus, at 635, the UE 605 may be configured with the URSP policy of the cellular network. That is, the UE 605 may receive an access policy (e.g., URSP) for the cellular radio network from the network via the base station, the access policy identifying access preference rules for the UE 605 to adopt for connecting to a core network function (e.g., 5GC 610) of the cellular radio network. The URSP may indicate to the UE 605 that it is preferred to connect to the core network function via the cellular radio network (e.g., preferably a 3GPP access network, such as a 5GNR SA network). Thus, the URSP may be installed for the UE 605. That is, the network may have downloaded the URSP policy to the UE 605. At this point, and in accordance with the guiding standards, the UE 605 should only refer to the URSP for its policy. One of the rules specified in the URSP is whether the preferred access is 3GPP (e.g., cellular) or non-3GPP (e.g., Wi-Fi) for each DNN. For example, the URSP rule may look like:

[0199] Traffic Descriptor:App-Id=APP1,APP2

[0200] RouteSelectionDescriptor:DNN=DNN1, Access-Preference=3GPP, S-NSSAI=1

[0201] DNN=DNN1, Access-Preference=Non-3GPP, S-NSSAI=2

[0202] Where S-NSSAI refers to Single-Network Slice Selection Assistant. This rule may mean that both APP1 and APP2 are assumed to prefer cellular when there is a choice between cellular and Wi-Fi coverage. This rule may also mean that UE 605 can request slice 1 as long as slice 1 is allowed by the network. If no cellular network is available, both APP1 and APP2 can connect via the Wi-Fi network.

[0203] At 640, UE 605 may be located only in a Wi-Fi coverage area, e.g., there is no available 5G coverage area to which UE 605 can connect. However, at 645, a first application 625 (e.g., APP1) may request to connect to modem 630, which requests to establish a connection to EPC 615 via an EPDG legacy gateway and a Wi-Fi AP. Since the EPDG legacy gateway belongs to EPC 615, there is no concept of slicing. However, for the guidance standard for 5GC 610, EPC 615 may inform UE 605 what S-NSSAI it should store for connecting to EPC 615 via the EPDG legacy gateway, so that if there is a handover to 5GC 610, UE 605 should request the same S-NSSAI that was signaled to it by EPC 615 via the EPDG legacy gateway. In this manner, at 650, the EPC 615 assigns S-NSSAI2 to the connection, which may also be referred to as a legacy traffic descriptor and / or slice handling for the connection.

[0204] Thus, UE 605 may establish a legacy core network function to the legacy cellular radio network via the legacy gateway at 655. UE 605 may identify a legacy access policy (e.g., ANDSF) that preferably instructs UE 605 to connect to the legacy core network function via a 3GPP connection or a non-3GPP connection.

[0205] At 660, UE 605 may enter an area with 5G coverage. For example, UE 605 may connect to a 5G NR SA base station and establish a connection with 5GC 610 via the base station. Since the URSP access policy gives a preference for 3GPP access networks for DNN1 connections, this may trigger a handover procedure for S-NSSAI2 granted by 5GC 610 at 665. Therefore, at 670, modem 630 of UE 605 may tear down the connection with EPC 615 for DNN1.

[0206] At this point, the first application 625 uses the 5G NR SA cellular radio network to connect to the 5GC 610. However, if the second application 620 requires the modem 630 to connect, the UE 605 will refer to the URSP access policy, which indicates that the first option for the second application 620 is S-NSSAI1. Therefore, the UE 605 will initiate NAS signaling to request a connection for S-NSSAI1, which can be granted by the network (e.g., the 5GC 610). Therefore, the UE 605 will establish a connection with the 5GC 610 for S-NSSAI1 for the second application 620. Now, the second application 620 will connect to the 5GC 610 over the 5G cellular radio network via slice 1 (S-NSSAI1), and the first application 625 will connect to the 5GC 610 over the 5G cellular radio network via slice 2 (S-NSSAI2) as a separate PDU session. Therefore, even if the network operator may aim to give both DNN1 and DNN2 the same slice processing, this approach will not give the desired results.

[0207] Thus, at 675, aspects of the described techniques allow the modem 630 of the UE 605 to reevaluate the previously provided URSP access policy. That is, whenever there is a handover from the EPC 615 to the 5GC 610, the UE 605 may go beyond the provisions of the guiding standard and may not blindly specify the S-NSSAI received during EPDG signaling (e.g., the legacy slice handling indication received from the EPC 615 via the EPDG legacy gateway). The UE 605 may instead reevaluate the URSP access policy to see if the S-NSSAI received from the EPDG is a valid routing descriptor (RSD) in the URSP (even if it is a lower priority RSD) and / or if it is an allowed S-NSSAI. If not, the UE 605 may tear down the call and have the application (e.g., the first application 625) retry. If it is valid, the UE 605 may continue to use the current connection. If another application requests a call (eg, to establish a connection) under the same rules, the UE 605 may lock the application to the same call (eg, connection).

[0208] In this example, the URSP reevaluation may indicate that S-NSSAI2 is not a valid route for the first application 625. Therefore, at 685, the modem 630 of the UE 605 may send an indication to the first application 625 that the network interface is shut down. At 690, the first application 625 may send a call request to the modem 630 of the UE 605 requesting a new connection. At 695, the modem 630 of the UE 605 may establish a new connection with the 5GC 610 for the first application 625. Therefore, the UE 605 may tear down the original connection for DNN1 over S-NSSAI2 for the first application 625 and establish an updated connection for DNN1 over S-NSSAI1 on the 5GC 610. This may result in the desired slice processing / routing for each application.

[0209] Figure 7 An example of a process 700 supporting a method for handling slices that account for Evolved Packet Data Gateway (EPDG) Wi-Fi access according to aspects of the present disclosure is illustrated. In some examples, process 700 can implement aspects of wireless communication systems 100 and / or 200 and / or processes 300, 400, 500, and / or 600. Aspects of process 700 can be implemented by UE 705, 5GC 710, and / or EPC 715, which can be examples of corresponding devices described herein. It will be understood that UE 705 can connect to 5GC 710 via a 5G NR SA base station and / or via a Wi-Fi AP and N3IWF gateway when UE 705 is connected to a non-3GPP access network, such as a Wi-Fi network. Similarly, UE 705 can connect to EPC 715 via a Wi-Fi AP and an EPDG legacy gateway when UE 705 is connected to a non-3GPP access network, such as a Wi-Fi network.

[0210] In some aspects, the UE 705 may include a set of applications, of which two applications are shown as examples. In general, each application may refer to any general traffic descriptor. Thus, the UE 705 may include a first application 725, a second application 720, and a modem 730, which may be examples of corresponding devices described herein. The modem 730 may monitor, control, or otherwise manage various aspects of communication between the UE 705 and the 5GC 710 and / or EPC 715 (e.g., via one or more base stations, Wi-Fi APs, N3IWF gateways, EPDG legacy gateways, etc.).

[0211] As discussed above, aspects of the described techniques can support a UE 705 establishing a connection to an EPC 715 legacy core network function of a 4G / 5G NR NSA legacy cellular radio network via an EPDG legacy gateway. The UE 705 can be configured with a set of traffic descriptors (e.g., the UE 705 can have different applications operating on the UE 705, such as a first application 725 and / or a second application 720). For each traffic descriptor (e.g., each application), the UE 705 can identify an ANDSF legacy access policy, such as a routing preference, that specifies whether the UE 705 connects via a cellular radio network (e.g., a 3GPP cellular radio network) or a non-cellular radio network (e.g., a non-3GPP radio network). The UE 705 can also identify or otherwise determine, for example, a legacy slice process associated with each traffic descriptor based at least in part on the connection to the EPC 715 via the EPDG. The UE 705 may establish a connection to the 5GC 710 core network function of the 5G NR SA cellular radio network via the N3IWF gateway. Thus, the UE 705 may receive or otherwise identify a URSP access policy for the UE 705 to adopt, which also informs the UE 705 whether to preferably connect via the cellular radio network or the non-cellular radio network. The UE 705 may also determine or otherwise identify a slice handling for each traffic descriptor based, for example, at least in part on the URSP access policy, the traffic descriptor identifier, the traffic descriptor type, etc. Thus, the UE 705 may use the URSP access policy, the legacy slice handling (from the EPC 715), and / or the slice handling (from the 5GC 710) to determine whether to transfer the connection for each traffic descriptor (e.g., application) from the EPC 715 via the EPDG gateway to the 5GC 710 or to establish an updated connection with the 5GC 715. Thus, the UE 705 can ensure that each traffic descriptor is given appropriate slice processing and / or connection preference when switching from an EPC 715 connection to a 5GC 710 connection.

[0212] Thus, at 735, UE 705 may be configured with a URSP policy for the cellular network. That is, UE 705 may receive an access policy (e.g., URSP) for the cellular radio network from the network via the base station, the access policy identifying access preference rules for UE 705 to adopt for connecting to a core network function (e.g., 5GC 710) of the cellular radio network. The URSP may indicate to UE 705 that it is preferred to connect to the core network function via the cellular radio network (e.g., a 3GPP access network, such as a 5GNR SA network). Thus, the URSP may be installed for UE 705. That is, the network may have downloaded the URSP policy to UE 705. At this point, and in accordance with the guiding standards, UE 705 should only refer to the URSP for its policy. One of the rules specified in the URSP is whether the preferred access is 3GPP (e.g., cellular) or non-3GPP (e.g., Wi-Fi) for each DNN. For example, the URSP rule may look like:

[0213] Traffic Descriptor:App-Id=APP1

[0214] RouteSelectionDescriptor:DNN=DNN1, Access-Preference=3GPP, S-NSSAI=1

[0215] DNN=DNN1, Access-Preference=Non-3GPP, S-NSSAI=2

[0216] App-Id = App2

[0217] RouteSelectionDescriptor:DNN=DNN1, Access-Preference=Non-3GPP, S-NSSAI=1

[0218] DNN=DNN1, Access-Preference=3GPP, S-NSSAI=2

[0219] This rule may mean that both APP1 and APP2 are assumed to be on S-NSSAI1, but the first application 725 prefers cellular, while the second application 720 prefers Wi-Fi. That is, these two applications or traffic descriptors operating on UE 705 may require the same slice processing, but have different routing descriptors.

[0220] At 740, UE 705 may be located in a Wi-Fi-only coverage area, e.g., there is no 5G coverage area for UE 705 to connect to. However, at 745, a first application 725 (e.g., APP1) may request to connect to modem 730, which requests to establish a connection to EPC 715 via an EPDG legacy gateway and a Wi-Fi AP. Since the EPDG legacy gateway belongs to EPC 715, there is no concept of slicing. However, for the guidance standard for 5GC 710, EPC 715 may inform UE 705 what S-NSSAI it should store for connecting to EPC 715 via the EPDG legacy gateway, so that if there is a handover to 5GC 710, UE 705 should request the same S-NSSAI that was signaled to it by EPC 715 via the EPDG legacy gateway. In this example, at 750, the EPC 715 assigns S-NSSAI1 to the connection, which may also be referred to as a legacy traffic descriptor and / or slice handling for the connection.

[0221] Thus, UE 705 may have been established by a legacy gateway to a legacy core network function of a legacy cellular radio network at 755. UE 705 may identify a legacy access policy (e.g., ANDSF) that preferably instructs UE 705 to connect to the legacy core network function via a 3GPP connection or a non-3GPP connection.

[0222] At 760, UE 705 may enter an area with 5G coverage. For example, UE 705 may connect to a 5G NR SA base station and establish a connection with 5GC 710 via the base station. Since the URSP access policy gives a preference for the 3GPP access network for the DNN1 connection of the first application 725, this may trigger a handover procedure for S-NSSAI1 granted by 5GC 710 at 765. Therefore, at 770, modem 730 of UE 705 may tear down the connection for DNN1 with EPC 715.

[0223] At this point, first application 725 uses the 5G NR SA cellular radio network to connect to 5GC 710 for connection to DNN1 and a given S-NSSAI1. However, if second application 720 requires modem 730 to connect, UE 705 will refer to the URSP access policy, which indicates that the first choice for second application 720 is S-NSSAI1 on the Wi-Fi network. Therefore, UE 705 will initiate a request for connection over S-NSSAI2. However, the network may deny this connection request because the same DNN1 with slice S-NSSAI1 has already been established on 5GC 710 (e.g., by first application 725). Therefore, this may prevent UE 705 from establishing a connection for second application 720.

[0224] Thus, at 775, aspects of the described techniques allow modem 730 of UE 705 to reevaluate the previously provisioned URSP access policy. That is, whenever a handover occurs from EPC 715 to 5GC 710, UE 705 may go beyond the guidelines and may not blindly assign the S-NSSAI received during EPDG signaling (e.g., the legacy slice handling indication received from EPC 715 via the EPDG legacy gateway). UE 705 may instead reevaluate the URSP access policy to see if the S-NSSAI received from the EPDG is a valid RSD in the URSP (even if it is a lower priority RSD) and / or if it is an allowed S-NSSAI. If not, UE 705 may tear down the call and have the application retry. If it is valid, UE 705 may continue using the current connection. If another application requests a call under the same rules (e.g., to establish a connection), UE 705 may lock that application to the same call (e.g., connection).

[0225] In this example, the URSP reevaluation may indicate that S-NSSAI 1 is a valid route for first application 725. Therefore, at 785, modem 730 of UE 705 may maintain a connection on 5GC 710 for first application 725 on DNN 1 and the given slice S-NSSAI 1. At 790, second application 720 may send a call request to modem 730 of UE 705 requesting a new connection. At 795, since the requested slice handling for S-NSSAI 1 has already been established on DNN 1 for first application 725, modem 730 of UE 705 may lock second application 720 to the connection with 5GC 710 for first application 725. Therefore, UE 705 may maintain the original connection of DNN 1 on S-NSSAI 1 for first application 725 and lock the connection of DNN 1 on 5GC 710 on S-NSSAI 1 for second application 720. This may result in the desired slice handling / routing for each application.

[0226] Figure 8 An example of a process 800 supporting a method for handling slices that account for Evolved Packet Data Gateway (EPDG) Wi-Fi access according to aspects of the present disclosure is illustrated. In some examples, process 800 can implement aspects of wireless communication systems 100 and / or 200 and / or processes 300, 400, 500, 600, and / or 700. Aspects of process 800 can be implemented by UE 805, 5GC 810, and / or EPC 815, which can be examples of corresponding devices described herein. It will be understood that UE 805 can connect to 5GC 810 via a 5G NR SA base station and / or via a Wi-Fi AP and N3IWF gateway when UE 805 is connected to a non-3GPP access network, such as a Wi-Fi network. Similarly, UE 805 can connect to EPC 815 via a Wi-Fi AP and an EPDG legacy gateway when UE 805 is connected to a non-3GPP access network, such as a Wi-Fi network.

[0227] In some aspects, the UE 805 may include a set of applications, of which two applications are shown as examples. In general, each application may refer to any general traffic descriptor. Thus, the UE 805 may include a first application 825, a second application 820, and a modem 830, which may be examples of corresponding devices described herein. The modem 830 may monitor, control, or otherwise manage various aspects of communication between the UE 805 and the 5GC 810 and / or EPC 815 (e.g., via one or more base stations, Wi-Fi APs, N3IWF gateways, EPDG legacy gateways, etc.).

[0228] As discussed above, aspects of the described techniques can support a UE 805 establishing a connection to an EPC 815 legacy core network function of a 4G / 5G NR NSA legacy cellular radio network via an EPDG legacy gateway. The UE 805 can be configured with a set of traffic descriptors (e.g., the UE 805 can have different applications operating on the UE 805, such as a first application 825 and / or a second application 820). For each traffic descriptor (e.g., each application), the UE 805 can identify an ANDSF legacy access policy, such as a routing preference, that specifies whether the UE 805 connects via a cellular radio network (e.g., a 3GPP cellular radio network) or a non-cellular radio network (e.g., a non-3GPP radio network). The UE 805 can also identify or otherwise determine, for example, a legacy slice process associated with each traffic descriptor based at least in part on the connection to the EPC 815 via the EPDG. The UE 805 may establish a connection to the 5GC 810 core network function of the 5G NR SA cellular radio network via the N3IWF gateway. Thus, the UE 805 may receive or otherwise identify a URSP access policy for the UE 805 to employ, which may also inform the UE 805 whether to preferably connect via the cellular radio network or the non-cellular radio network. The UE 805 may also determine or otherwise identify a slice handling for each traffic descriptor based, for example, at least in part on the URSP access policy, the traffic descriptor identifier, the traffic descriptor type, etc. Thus, the UE 805 may use the URSP access policy, the legacy slice handling (from the EPC 815), and / or the slice handling (from the 5GC 810) to determine whether to transfer the connection for each traffic descriptor (e.g., application) from the EPC 815 via the EPDG gateway to the 5GC 810 or to establish an updated connection with the 5GC 815. Thus, the UE 805 can ensure that each traffic descriptor is given appropriate slice processing and / or connection preference when switching from an EPC 815 connection to a 5GC 810 connection.

[0229] Process 800 illustrates an example where two applications are assumed to have different slice handling, but both prefer non-3GPP access policies. A later application (e.g., the last application to send a call request) may not be able to obtain service because the first application may have established a connection using the same DNN but with different slice handling under the EPDG. Alternatively, on 5GC 810, the applications were assumed to receive different slice handling but ultimately received the same slice handling.

[0230] Thus, at 835, UE 805 may be configured with a URSP policy for the cellular network. That is, UE 805 may receive an access policy (e.g., URSP) for the cellular radio network from the network via the base station, the access policy identifying access preference rules for UE 805 to adopt for connecting to a core network function (e.g., 5GC 810) of the cellular radio network. The URSP may indicate to UE 805 that it is preferred to connect to the core network function via the cellular radio network (e.g., a 3GPP access network, such as a 5GNR SA network). Thus, the URSP may be installed for UE 805. That is, the network may have downloaded the URSP policy to UE 805. At this point, and in accordance with the guiding standards, UE 805 should only refer to the URSP for its policy. One of the rules specified in the URSP is whether the preferred access is 3GPP (e.g., cellular) or non-3GPP (e.g., Wi-Fi) for each DNN. For example, the URSP rule may look like:

[0231] Traffic Descriptor:App-Id=APP1

[0232] RouteSelectionDescriptor:DNN=DNN1, Access-Preference=Non-3GPP, S-NSSAI=1

[0233] DNN=DNN1, Access-Preference=3GPP, S-NSSAI=1

[0234] App-Id = App2

[0235] RouteSelectionDescriptor:DNN=DNN1, Access-Preference=Non-3GPP, S-NSSAI=2

[0236] DNN=DNN1, Access-Preference=3GPP, S-NSSAI=2

[0237] This rule may mean that APP1 is assumed to prefer EPDG when there is a choice between cellular and Wi-Fi networks, and UE 805 should request slice 1 (e.g., S-NSSAI1) in the case of a 5G call. However, for APP2, it also prefers EPDG, but should use slice S-NSSAI2 in the case of a 5G call. That is, these two applications or traffic descriptors operating on UE 805 may require different slice handling, but have the same routing descriptor.

[0238] At 840, UE 805 may be located in both Wi-Fi and 5G coverage. At 845, a first application 825 (e.g., APP1) may request to connect to modem 830, which requests to establish a connection to EPC 815 via an EPDG legacy gateway and a Wi-Fi AP. Since the EPDG legacy gateway belongs to EPC 815, there is no concept of slice handling. However, for the guidance standard for 5GC 810, EPC 815 may inform UE 805 what S-NSSAI it should store for connecting to EPC 815 via the EPDG legacy gateway, so that if there is a handover to 5GC 810, UE 805 should request the same S-NSSAI that was signaled to it by EPC 815 via the EPDG legacy gateway. In this example, at 850, EPC 815 assigns S-NSSAI1 to the connection, which may also be referred to as a legacy traffic descriptor and / or slice handling for the connection.

[0239] Thus, UE 805 may have established a legacy core network function to the legacy cellular radio network by a legacy gateway at 855. UE 805 may identify a legacy access policy (e.g., ANDSF) that preferably instructs UE 805 to connect to the legacy core network function via a 3GPP connection or a non-3GPP connection.

[0240] However, at 860, second application 820 may send a call request for a data connection. However, this may cause at least two problems. In one issue, UE 805 will establish a PDN connection for second application 820 with EPC 815 on DNN1 via the EPDG legacy gateway. However, the network will reject this connection request because DNN1 is already established. In another issue, UE 805 may decide to lock second application 820 to the DNN1 PDN on S-NSSAI1. However, this approach will ultimately result in first application 825 and second application 820 being on DNN1 on S-NSSAI1. However, according to the URSP access policy, second application 820 should use S-NSSAI2.

[0241] Therefore, at 865, UE 805 may determine that a DNN1 connection has already been established. That is, even though second application 820 prefers EPDG, since a PDN connection already exists for the same DNN with a different slice, UE 805, in this example, may select RSD2 (e.g., routing policy #2 in the URSP for APP2) for use with second application 820. Therefore, at 870, UE 805 may establish a connection for second application 820 with 5GC 810 using slice S-NSSAI2. That is, UE 805 may skip RSD1 (e.g., preferring a non-3GPP connection for APP2 per URSP) since a PDN connection already exists for DNN1 (e.g., the same DNN) and a different slice for first application 825. UE 805 may instead use RSD2 (e.g., preferring a 3GPP connection for APP2 per URSP) to establish a PDN connection for second application 820 with 5GC 810.

[0242] Thus, at 875, UE 805 may use the cached slice S-NSSAI2 in the PDU context to operate on 5GC 810 with the PDN connection established on DNN1 for the second application 820. This may allow UE 805 to follow the appropriate slice handling and routing preferences for both applications.

[0243] Figure 9 A block diagram 900 of a device 905 supporting methods for handling slices that account for Evolved Packet Data Gateway Wi-Fi access according to aspects of the present disclosure is shown. The device 905 can be an example of aspects of the UE 115 as described herein. The device 905 may include a receiver 910, a communication manager 915, and a transmitter 920. The device 905 may also include a processor. Each of these components may be in communication with each other (e.g., via one or more buses).

[0244] The receiver 910 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to methods for handling slices accounting for Evolved Packet Data Gateway Wi-Fi access, etc.). The information may be passed to other components of the device 905. The receiver 910 may be a reference Figure 12 Examples of aspects of the described transceiver 1220. The receiver 910 may utilize a single antenna or a set of antennas.

[0245] The communications manager 915 may establish a cellular connection with a base station associated with a cellular radio network, establish a connection to a legacy core network function of the legacy cellular radio network via a legacy gateway between a non-cellular radio network and the legacy core network function of the legacy cellular radio network based at least in part on the access preference rule, the gateway not being configured, and the gateway selection policy not being configured, receive an access policy of the cellular radio network, the access policy identifying an access preference rule for the UE to employ for connecting to the core network function of the cellular radio network, the access preference rule indicating to the UE that connection to the core network function is preferably via the non-cellular radio network, determine that a gateway between the non-cellular radio network and the core network function of the cellular radio network is not configured, and determine that the gateway selection policy of the cellular radio network is not configured.

[0246] The communications manager 915 may also establish a cellular connection with a base station associated with a cellular radio network; determine that a non-cellular radio network is available and that the cellular radio network has become unavailable; establish, via the non-cellular radio network, a connection to a legacy core network function of the legacy cellular radio network via a legacy gateway between the legacy core network function and the non-cellular radio network; determine that the cellular radio network has become available for establishing a new connection; establish a new connection to the cellular radio network based at least on an access preference rule; receive an access policy of the cellular radio network, the access policy identifying an access preference rule for the UE to adopt for connecting to the core network function of the cellular radio network, the access preference rule indicating to the UE that it is preferred to connect to the core network function via the cellular radio network and via a gateway between the cellular radio network and the core network function; identify a legacy access policy of the legacy cellular radio network, the legacy access policy identifying a legacy access preference rule for the UE to adopt for connecting to the legacy core network function, the legacy access preference rule indicating to the UE that it is preferred to connect to the legacy core network function via the non-cellular radio network; determine that the gateway is not configured; and determine that a gateway selection policy of the cellular radio network is not configured.

[0247] The communications manager 915 may also establish a cellular connection with a base station associated with a cellular radio network; determine that a non-cellular radio network is available and that a gateway between the non-cellular radio network and a core network function of the cellular radio network is not configured; establish a connection to a legacy core network function of the legacy cellular radio network via a legacy gateway between the legacy core network function and the non-cellular radio network; maintain a connection to the legacy core network function of the legacy radio network via the legacy gateway based at least in part on the access preference rule; receive an access policy of the cellular radio network, the access policy identifying an access preference rule for the UE to adopt for connecting to the core network function of the cellular radio network, the access preference rule indicating to the UE that it is preferred to connect to the core network function via the non-cellular radio network; identify a legacy access policy of the legacy cellular radio network, the legacy access policy identifying a legacy access preference rule for the UE to adopt for connecting to the legacy core network function, the legacy access preference rule indicating to the UE that it is preferred to connect to the legacy core network function via the legacy cellular radio network; and determine that a gateway selection policy of the cellular radio network is not configured.

[0248] The communication manager 915 may also establish a connection to a legacy core network function of the legacy cellular radio network via a legacy gateway between the legacy cellular radio network and the non-cellular radio network; establish a connection to the core network function of the cellular radio network via a gateway between the cellular radio network and the non-cellular radio network; for each traffic descriptor in the traffic descriptor set, identify a legacy access policy of the legacy cellular radio network, the legacy access policy identifying a legacy access preference rule for the UE to adopt for connecting to the legacy core network function, each legacy access preference rule indicating to the UE whether to preferably connect to the legacy core network function via the legacy cellular radio network or the non-cellular radio network for the traffic descriptor and for the traffic descriptor The method further comprises: determining, for each traffic descriptor and based at least in part on the legacy slicing processing and the slicing processing and based at least in part on the access policy, whether to transfer a connection associated with the traffic descriptor to a core network function or to establish an updated connection for the traffic descriptor with the core network function; and identifying, for each traffic descriptor in the traffic descriptor set, an access policy of a cellular radio network, the access policy identifying an access preference rule for the UE to adopt for connecting to the core network function of the cellular radio network, each access preference rule indicating to the UE whether to preferably connect to the core network function via a cellular radio network or a non-cellular radio network for the traffic descriptor and the slicing processing of the traffic descriptor. The communication manager 915 can be an example of aspects of the communication manager 1210 described herein.

[0249] The communication manager 915 or its subcomponents may be implemented in hardware, in code executed by a processor (e.g., software or firmware), or any combination thereof. If implemented in code executed by a processor, the functions of the communication manager 915 or its subcomponents may be performed by a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device designed to perform the functions described in this disclosure, discrete gate or transistor logic, discrete hardware components, or any combination thereof.

[0250] The communication manager 915 or its subcomponents may be physically located at various locations, including being distributed such that portions of functionality are implemented by one or more physical components at different physical locations. In some examples, according to various aspects of the present disclosure, the communication manager 915 or its subcomponents may be separate and distinct components. In some examples, according to various aspects of the present disclosure, the communication manager 915 or its subcomponents may be combined with one or more other hardware components, including but not limited to input / output (I / O) components, a transceiver, a network server, another computing device, one or more other components described in the present disclosure, or a combination thereof.

[0251] The transmitter 920 may transmit signals generated by other components of the device 905. In some examples, the transmitter 920 may be co-located with the receiver 910 in a transceiver module. For example, the transmitter 920 may be a reference Figure 12 Examples of aspects of the described transceiver 1220. The transmitter 920 may utilize a single antenna or a collection of antennas.

[0252] Figure 10 A block diagram 1000 of a device 1005 supporting a method for handling slices accounting for evolved packet data gateway Wi-Fi access according to aspects of the present disclosure is shown. The device 1005 may be an example of aspects of the device 905 or UE 115 as described herein. The device 1005 may include a receiver 1010, a communication manager 1015, and a transmitter 1045. The device 1005 may also include a processor. Each of these components may be in communication with each other (e.g., via one or more buses).

[0253] The receiver 1010 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to methods for handling slices accounting for Evolved Packet Data Gateway Wi-Fi access, etc.). The information may be passed to other components of the device 1005. The receiver 1010 may be a reference Figure 12 Examples of various aspects of the described transceiver 1220. The receiver 1010 may utilize a single antenna or a set of antennas.

[0254] The communication manager 1015 may be an example of aspects of the communication manager 915 as described herein. The communication manager 1015 may include a connection manager 1020, an access policy manager 1025, a gateway manager 1030, a gateway selection policy manager 1035, and a traffic descriptor manager 1040. The communication manager 1015 may be an example of aspects of the communication manager 1210 described herein.

[0255] The connection manager 1020 may establish a cellular connection with a base station associated with the cellular radio network and establish a connection to a legacy core network function of the legacy cellular radio network via a legacy gateway between the non-cellular radio network and the legacy core network function of the legacy cellular radio network based at least in part on the access preference rule, the gateway not being configured, and the gateway selection policy not being configured.

[0256] The access policy manager 1025 may receive an access policy of the cellular radio network, the access policy identifying an access preference rule for the UE to adopt for connecting to a core network function of the cellular radio network, the access preference rule indicating to the UE that it is preferred to connect to the core network function via a non-cellular radio network.

[0257] The gateway manager 1030 may determine that a gateway between the non-cellular radio network and the core network function of the cellular radio network is not configured.

[0258] The gateway selection policy manager 1035 may determine that the gateway selection policy of the cellular radio network is not configured.

[0259] The connection manager 1020 may establish a cellular connection with a base station associated with a cellular radio network; determine that a non-cellular radio network is available and that the cellular radio network has become unavailable; establish, via the non-cellular radio network, a connection to a legacy core network function of the legacy cellular radio network via a legacy gateway between the legacy core network function and the non-cellular radio network; determine that the cellular radio network has become available for establishing a new connection; and establish a new connection to the cellular radio network based at least on an access preference rule.

[0260] The access policy manager 1025 may receive an access policy of a cellular radio network, the access policy identifying an access preference rule for a UE to adopt for connecting to a core network function of the cellular radio network, the access preference rule indicating to the UE that it is preferred to connect to the core network function via the cellular radio network and via a gateway between the cellular radio network and the core network function; and a legacy access policy identifying a legacy access preference rule for a legacy cellular radio network to adopt for connecting to a legacy core network function, the legacy access preference rule indicating to the UE that it is preferred to connect to the legacy core network function via a non-cellular radio network.

[0261] The gateway manager 1030 may determine that the gateway is not configured.

[0262] The gateway selection policy manager 1035 may determine that the gateway selection policy of the cellular radio network is not configured.

[0263] The connection manager 1020 may also establish a cellular connection with a base station associated with a cellular radio network; determine that a non-cellular radio network is available and that a gateway between the non-cellular radio network and a core network function of the cellular radio network is not configured; establish a connection to a legacy core network function of the legacy cellular radio network via a legacy gateway between the legacy core network function and the non-cellular radio network; and maintain the connection to the legacy core network function of the legacy radio network via the legacy gateway based at least in part on the access preference rule.

[0264] The access policy manager 1025 may also receive an access policy of the cellular radio network, the access policy identifying an access preference rule for the UE to adopt for connecting to a core network function of the cellular radio network, the access preference rule indicating to the UE that it is preferred to connect to the core network function via a non-cellular radio network; and a legacy access policy identifying a legacy access preference rule for the UE to adopt for connecting to the legacy core network function, the legacy access preference rule indicating to the UE that it is preferred to connect to the legacy core network function via the legacy cellular radio network.

[0265] The gateway selection policy manager 1035 may determine that the gateway selection policy of the cellular radio network is not configured.

[0266] The connection manager 1020 may establish a connection to a legacy core network function of a legacy cellular radio network via a legacy gateway between the legacy cellular radio network and the non-cellular radio network; and establish a connection to a core network function of a cellular radio network via a gateway between the cellular radio network and the non-cellular radio network.

[0267] The traffic descriptor manager 1040 may, for each traffic descriptor in the traffic descriptor set, identify a legacy access policy of the legacy cellular radio network, the legacy access policy identifying a legacy access preference rule for the UE to adopt for connecting to the legacy core network function, each legacy access preference rule indicating to the UE whether to preferably connect to the legacy core network function via the legacy cellular radio network or the non-cellular radio network for the traffic descriptor and the legacy slicing processing for the traffic descriptor; and for each traffic descriptor and at least in part based on the legacy slicing processing and slicing processing and at least in part based on the access policy, determine whether to transfer the connection associated with the traffic descriptor to the core network function or to establish an updated connection for the traffic descriptor with the core network function.

[0268] The access policy manager 1025 can identify, for each traffic descriptor in the traffic descriptor set, an access policy of the cellular radio network, the access policy identifying an access preference rule for the UE to adopt for connecting to the core network function of the cellular radio network, each access preference rule indicating to the UE whether to preferably connect to the core network function via the cellular radio network or the non-cellular radio network for the traffic descriptor and the slice processing of the traffic descriptor.

[0269] The transmitter 1045 can transmit signals generated by other components of the device 1005. In some examples, the transmitter 1045 can be co-located with the receiver 1010 in a transceiver module. For example, the transmitter 1045 can be a reference Figure 12 Examples of aspects of the described transceiver 1220. The transmitter 1045 may utilize a single antenna or a collection of antennas.

[0270] Figure 11 A block diagram 1100 illustrates a communication manager 1105 that supports methods for handling slices that account for evolved packet data gateway Wi-Fi access in accordance with aspects of the present disclosure. The communication manager 1105 can be an example of aspects of the communication manager 915, the communication manager 1015, or the communication manager 1210 described herein. The communication manager 1105 can include a connection manager 1110, an access policy manager 1115, a gateway manager 1120, a gateway selection policy manager 1125, a connection configuration manager 1130, an N3IWF manager 1135, a traffic descriptor manager 1140, and a slice handling manager 1145. Each of these modules can communicate directly or indirectly with each other (e.g., via one or more buses).

[0271] The connection manager 1110 may establish a cellular connection with a base station associated with the cellular radio network. In some examples, the connection manager 1110 may establish a connection to a legacy core network function of the legacy cellular radio network via a legacy gateway between the non-cellular radio network and the legacy core network function of the legacy cellular radio network based at least in part on the access preference rule, the gateway not being configured, and the gateway selection policy not being configured.

[0272] In some examples, connection manager 1110 may determine that a non-cellular radio network is available and that a cellular radio network has become unavailable. In some examples, connection manager 1110 may establish a connection to a legacy core network function of a legacy cellular radio network via a legacy gateway between the legacy core network function and the non-cellular radio network via the non-cellular radio network. In some examples, connection manager 1110 may determine that a cellular radio network has become available for establishing a new connection. In some examples, connection manager 1110 may establish a new connection to the cellular radio network based at least on an access preference rule.

[0273] In some examples, the connection manager 1110 may determine that the non-cellular radio network is available and that a gateway between the non-cellular radio network and the core network function of the cellular radio network is not configured. In some examples, the connection manager 1110 may establish a connection to a legacy core network function of the legacy cellular radio network via a legacy gateway between the legacy core network function and the non-cellular radio network.

[0274] In some examples, the connection manager 1110 can maintain a connection to a legacy core network function of a legacy radio network via a legacy gateway based at least in part on the access preference rule. In some examples, the connection manager 1110 can establish a connection to a core network function of a cellular radio network via a gateway between the cellular radio network and the non-cellular radio network.

[0275] In some cases, the cellular radio network comprises a 5G NR SA cellular radio network. In some cases, the legacy cellular radio network comprises at least one of a 4G LTE cellular radio network or a 5G NR NSA cellular radio network. In some cases, the access policy comprises a URSP. In some cases, the gateway selection policy comprises an ANDSP. In some cases, the gateway comprises an N3IWF between the core network function of the 5G NR SA cellular radio network and the non-cellular radio network. In some cases, the legacy gateway comprises an EPC core network function of a 4G LTE cellular radio network or a 5G NR SA cell and an EPDG between the non-cellular radio network. In some cases, the legacy access policy comprises an ANDSF. In some cases, the core network function comprises a 5GC.

[0276] The access policy manager 1115 may receive an access policy of the cellular radio network, the access policy identifying an access preference rule for the UE to adopt for connecting to a core network function of the cellular radio network, the access preference rule indicating to the UE that it is preferred to connect to the core network function via a non-cellular radio network.

[0277] In some examples, the access policy manager 1115 may receive an access policy of a cellular radio network that identifies an access preference rule for a UE to adopt for connecting to a core network function of the cellular radio network, the access preference rule indicating to the UE that it is preferred to connect to the core network function via the cellular radio network and via a gateway between the cellular radio network and the core network function.

[0278] In some examples, the access policy manager 1115 may identify a legacy access policy for a legacy cellular radio network, which legacy access policy identifies a legacy access preference rule for the UE to adopt for connecting to the legacy core network function, which legacy access preference rule indicates to the UE that it is preferred to connect to the legacy core network function via a non-cellular radio network.

[0279] In some examples, the access policy manager 1115 may receive an access policy of the cellular radio network, which access policy identifies an access preference rule for the UE to adopt for connecting to a core network function of the cellular radio network, the access preference rule indicating to the UE that it is preferred to connect to the core network function via a non-cellular radio network.

[0280] In some examples, the access policy manager 1115 may identify a legacy access policy of the legacy cellular radio network, which legacy access policy identifies a legacy access preference rule for the UE to adopt for connecting to the legacy core network function, which legacy access preference rule indicates to the UE that it is preferred to connect to the legacy core network function via the legacy cellular radio network.

[0281] In some examples, the access policy manager 1115 may identify an access policy of the cellular radio network for each traffic descriptor in the traffic descriptor set, the access policy identifying an access preference rule for the UE to adopt for connecting to a core network function of the cellular radio network, each access preference rule indicating to the UE whether to preferably connect to the core network function via a cellular radio network or a non-cellular radio network for the traffic descriptor and slice processing of the traffic descriptor.

[0282] The gateway manager 1120 may determine that a gateway between the non-cellular radio network and the core network function of the cellular radio network is not configured. In some examples, the gateway manager 1120 may determine that the gateway is not configured.

[0283] The gateway selection policy manager 1125 may determine that the gateway selection policy of the cellular radio network is not configured. In some examples, the gateway selection policy manager 1125 may determine that the gateway selection policy of the cellular radio network is not configured. In some examples, the gateway selection policy manager 1125 may determine that the gateway selection policy of the cellular radio network is not configured.

[0284] The traffic descriptor manager 1140 may identify, for each traffic descriptor in the traffic descriptor set, a legacy access policy for the legacy cellular radio network, the legacy access policy identifying a legacy access preference rule for the UE to employ for connecting to the legacy core network function, each legacy access preference rule indicating to the UE whether to preferably connect to the legacy core network function via the legacy cellular radio network or the non-cellular radio network for the traffic descriptor and the legacy slice processing for the traffic descriptor. In some examples, for each traffic descriptor and based at least in part on the legacy slice processing and the slice processing and at least in part on the access policy, the traffic descriptor manager 1140 may determine whether to transfer a connection associated with the traffic descriptor to the core network function or to establish an updated connection for the traffic descriptor with the core network function.

[0285] The connection configuration manager 1130 may receive a configuration for connection via a non-cellular radio network, the configuration configuring the UE to connect to a legacy core network function or to connect to the core network function via the non-cellular radio network. In some examples, the connection configuration manager 1130 may receive a configuration for connection via a non-cellular radio network, the configuration configuring the UE to attempt to connect to the core network function and to connect to the legacy core network function via the non-cellular radio network if the attempt to connect to the core network function is unsuccessful.

[0286] In some examples, the connection configuration manager 1130 may receive a configuration for connection via a non-cellular radio network that configures the UE to connect to a legacy core network function or to connect to a core network function via the non-cellular radio network. In some examples, the connection configuration manager 1130 may receive a configuration for connection via a non-cellular radio network that configures the UE to attempt to connect to the core network function and to connect to the legacy core network function via the non-cellular radio network if the attempt to connect to the core network function is unsuccessful.

[0287] In some examples, the connection configuration manager 1130 may receive a configuration for connection via a non-cellular radio network that configures the UE to connect to a legacy core network function or to connect to a core network function via the non-cellular radio network. In some examples, the connection configuration manager 1130 may receive a configuration for connection via a non-cellular radio network that configures the UE to attempt to connect to the core network function and to connect to the legacy core network function via the non-cellular radio network if the attempt to connect to the core network function is unsuccessful.

[0288] The N3IWF manager 1135 may determine, based at least in part on the new connection, that a gateway of the cellular radio network is configured. In some examples, the N3IWF manager 1135 may transfer a connection to a legacy core network function of the legacy cellular radio network via the legacy gateway to the core network function of the cellular radio network via the gateway based at least in part on the access policy.

[0289] For at least two traffic descriptors in the traffic descriptor set, the slice processing manager 1145 may determine that the legacy traffic descriptor and the traffic descriptor are the same traffic descriptor. In some examples, the slice processing manager 1145 may transfer the connection for the at least two traffic descriptors to the core network function. In some examples, for at least two traffic descriptors in the traffic descriptor set, the slice processing manager 1145 may determine that the legacy traffic descriptor and the traffic descriptor are different traffic descriptors. In some examples, the slice processing manager 1145 may update the connection for at least one of the two traffic descriptors with the core network function. In some examples, for at least two traffic descriptors in the traffic descriptor set associated with the same traffic descriptor, the slice processing manager 1145 may determine that the legacy access policy and the access policy are the same access policy. In some examples, for at least two traffic descriptors in the traffic descriptor set associated with the same traffic descriptor, the slice processing manager 1145 may determine that the legacy access policy and the access policy are different access policies.

[0290] Figure 12 A diagram of a system 1200 including a device 1205 supporting a method for handling slices that account for evolved packet data gateway Wi-Fi access according to aspects of the present disclosure is illustrated. The device 1205 may be an example of, or include components of, the device 905, device 1005, or UE 115 as described herein. The device 1205 may include components for two-way voice and data communications, including components for transmitting and receiving communications, including a communication manager 1210, an I / O controller 1215, a transceiver 1220, an antenna 1225, a memory 1230, and a processor 1240. These components may be in electronic communication via one or more buses (e.g., bus 1245).

[0291] The communications manager 1210 may establish a cellular connection with a base station associated with a cellular radio network; establish a connection to a legacy core network function of the legacy cellular radio network via a legacy gateway between a non-cellular radio network and a legacy core network function of the legacy cellular radio network based at least in part on the access preference rule, the gateway not being configured, and the gateway selection policy not being configured; receive an access policy of the cellular radio network, the access policy identifying an access preference rule for the UE to adopt for connecting to the core network function of the cellular radio network, the access preference rule indicating to the UE that it is preferred to connect to the core network function via the non-cellular radio network; determine that a gateway between the non-cellular radio network and the core network function of the cellular radio network is not configured; and determine that the gateway selection policy of the cellular radio network is not configured.

[0292] The communications manager 1210 may also establish a cellular connection with a base station associated with a cellular radio network; determine that a non-cellular radio network is available and that the cellular radio network has become unavailable; establish, via the non-cellular radio network, a connection to a legacy core network function of the legacy cellular radio network via a legacy gateway between the legacy core network function and the non-cellular radio network; determine that the cellular radio network has become available for establishing a new connection; establish a new connection to the cellular radio network based at least on an access preference rule; receive an access policy of the cellular radio network, the access policy identifying an access preference rule for the UE to adopt for connecting to the core network function of the cellular radio network, the access preference rule indicating to the UE that connection to the core network function is preferably via the cellular radio network and via a gateway between the cellular radio network and the core network function; identify a legacy access policy of the legacy cellular radio network, the legacy access policy identifying a legacy access preference rule for the UE to adopt for connecting to the legacy core network function, the legacy access preference rule indicating to the UE that connection to the legacy core network function is preferably via the non-cellular radio network; determine that the gateway is not configured; and determine that a gateway selection policy of the cellular radio network is not configured.

[0293] The communications manager 1210 may also establish a cellular connection with a base station associated with a cellular radio network; determine that a non-cellular radio network is available and that a gateway between the non-cellular radio network and a core network function of the cellular radio network is not configured; establish a connection to a legacy core network function of the legacy cellular radio network via a legacy gateway between the legacy core network function and the non-cellular radio network; maintain a connection to the legacy core network function of the legacy radio network via the legacy gateway based at least in part on the access preference rule; receive an access policy of the cellular radio network, the access policy identifying an access preference rule for the UE to adopt for connecting to the core network function of the cellular radio network, the access preference rule indicating to the UE that it is preferred to connect to the core network function via the non-cellular radio network; identify a legacy access policy of the legacy cellular radio network, the legacy access policy identifying a legacy access preference rule for the UE to adopt for connecting to the legacy core network function, the legacy access preference rule indicating to the UE that it is preferred to connect to the legacy core network function via the legacy cellular radio network; and determine that a gateway selection policy of the cellular radio network is not configured.

[0294] The communications manager 1210 may also establish a connection to a legacy core network function of the legacy cellular radio network via a legacy gateway between the legacy cellular radio network and the non-cellular radio network; establish a connection to the core network function of the cellular radio network via the gateway between the cellular radio network and the non-cellular radio network; for each traffic descriptor in the traffic descriptor set, identify a legacy access policy of the legacy cellular radio network, the legacy access policy identifying a legacy access preference rule for the UE to adopt for connecting to the legacy core network function, each legacy access preference rule indicating to the UE whether to preferably connect to the legacy core network function via the legacy cellular radio network or the non-cellular radio network for the traffic descriptor and for the traffic descriptor for each traffic descriptor and based at least in part on the legacy slicing processing and the slicing processing and based at least in part on the access policy, determining whether to transfer the connection associated with the traffic descriptor to the core network function or to establish an updated connection for the traffic descriptor with the core network function; and for each traffic descriptor in the traffic descriptor set, identifying the access policy of the cellular radio network, the access policy identifying an access preference rule for the UE to be adopted for connecting to the core network function of the cellular radio network, each access preference rule indicating to the UE whether to preferably connect to the core network function via the cellular radio network or the non-cellular radio network for the traffic descriptor and the slicing processing of the traffic descriptor.

[0295] I / O controller 1215 can manage input and output signals for device 1205. I / O controller 1215 can also manage peripheral devices that are not integrated into device 1205. In some cases, I / O controller 1215 can represent a physical connection or port to an external peripheral device. In some cases, I / O controller 1215 can utilize an operating system, such as or another known operating system. In other cases, I / O controller 1215 may represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, I / O controller 1215 may be implemented as part of a processor. In some cases, a user may interact with device 1205 via I / O controller 1215 or via hardware components controlled by I / O controller 1215.

[0296] The transceiver 1220 can communicate bidirectionally via one or more antennas, wired or wireless links, as described above. For example, the transceiver 1220 can represent a wireless transceiver and can communicate bidirectionally with another wireless transceiver. The transceiver 1220 can also include a modem to modulate packets and provide the modulated packets to the antenna for transmission, and demodulate packets received from the antenna.

[0297] In some cases, a wireless device may include a single antenna 1225. However, in some cases, the device may have more than one antenna 1225, which may be capable of transmitting or receiving multiple wireless transmissions concurrently.

[0298] Memory 1230 may include random access memory (RAM) and read-only memory (ROM). Memory 1230 may store computer-readable, computer-executable code 1235 including instructions that, when executed, cause the processor to perform the various functions described herein. In some cases, memory 1230 may include, among other things, a basic input / output system (BIOS), which may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0299] The processor 1240 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor 1240 may be configured to operate a memory array using a memory controller. In other cases, the memory controller may be integrated into the processor 1240. The processor 1240 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1230) to cause the device 1205 to perform various functions (e.g., functions or tasks supporting a method for handling slices for Evolved Packet Data Gateway Wi-Fi access).

[0300] The code 1235 may include instructions for implementing various aspects of the present disclosure, including instructions for supporting wireless communications. The code 1235 may be stored in a non-transitory computer-readable medium, such as system memory or other types of memory. In some cases, the code 1235 may not be directly executed by the processor 1240, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein.

[0301] Figure 13 A flow chart illustrating a method 1300 for supporting a method for handling slices accounting for Evolved Packet Data Gateway Wi-Fi access according to aspects of the present disclosure is shown. The operations of the method 1300 may be implemented by a UE 115 or components thereof as described herein. For example, the operations of the method 1300 may be implemented by a UE 115 or components thereof as described herein. Figures 9 to 12 In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the following functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the following functions.

[0302] At 1305, the UE may establish a cellular connection with a base station associated with a cellular radio network. The operations of 1305 may be performed according to the methods described herein. In some examples, aspects of the operations of 1305 may be performed as described in reference to Figures 9 to 12 The connection manager described is implemented.

[0303] At 1310, the UE may receive an access policy of the cellular radio network, the access policy identifying an access preference rule for the UE to adopt for connecting to a core network function of the cellular radio network, the access preference rule indicating to the UE that it is preferred to connect to the core network function via a non-cellular radio network. The operations of 1310 may be performed according to the methods described herein. In some examples, aspects of the operations of 1310 may be performed as described with reference to Figures 9 to 12 The described access policy manager is executed.

[0304] At 1315, the UE may determine that a gateway between the non-cellular radio network and the core network function of the cellular radio network is not configured. The operations of 1315 may be performed according to the methods described herein. In some examples, aspects of the operations of 1315 may be performed as described in reference to Figures 9 to 12 The gateway manager described here is used to execute.

[0305] At 1320, the UE may determine that the gateway selection policy of the cellular radio network is not configured. The operations of 1320 may be performed according to the methods described herein. In some examples, aspects of the operations of 1320 may be performed as described in reference to Figures 9 to 12 The gateway described here selects the policy manager to execute.

[0306] At 1325, the UE may establish a connection to the legacy core network function of the legacy cellular radio network via the legacy gateway between the non-cellular radio network and the legacy core network function of the legacy cellular radio network based at least in part on the access preference rule, the gateway not being configured, and the gateway selection policy not being configured. The operations of 1325 may be performed according to the methods described herein. In some examples, aspects of the operations of 1325 may be performed as described with reference to Figures 9 to 12 The connection manager described is implemented.

[0307] Figure 14 A flow chart illustrating a method 1400 for supporting a method for handling slices accounting for Evolved Packet Data Gateway Wi-Fi access according to aspects of the present disclosure is shown. The operations of the method 1400 may be implemented by a UE 115 or components thereof as described herein. For example, the operations of the method 1400 may be implemented by a UE 115 or components thereof as described herein. Figures 9 to 12 In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the following functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the following functions.

[0308] At 1405, the UE may establish a cellular connection with a base station associated with a cellular radio network. The operations of 1405 may be performed according to the methods described herein. In some examples, aspects of the operations of 1405 may be performed as described in reference to Figures 9 to 12 The connection manager described is implemented.

[0309] At 1410, the UE may receive a configuration for connection via a non-cellular radio network, the configuration configuring the UE to connect to a legacy core network function or to a core network function via the non-cellular radio network. The operations of 1410 may be performed according to the methods described herein. In some examples, aspects of the operations of 1410 may be performed as described with reference to Figures 9 to 12 The connection configuration manager described is executed.

[0310] At 1415, the UE may receive an access policy of the cellular radio network, the access policy identifying an access preference rule for the UE to adopt for connecting to a core network function of the cellular radio network, the access preference rule indicating to the UE that it is preferred to connect to the core network function via a non-cellular radio network. The operations of 1415 may be performed according to the methods described herein. In some examples, aspects of the operations of 1415 may be performed as described with reference to Figures 9 to 12 The described access policy manager is executed.

[0311] At 1420, the UE may determine that a gateway between the non-cellular radio network and the core network function of the cellular radio network is not configured. The operations of 1420 may be performed according to the methods described herein. In some examples, aspects of the operations of 1420 may be performed as described in reference to Figures 9 to 12 The gateway manager described here is used to execute.

[0312] At 1425, the UE may determine that the gateway selection policy of the cellular radio network is not configured. The operations of 1425 may be performed according to the methods described herein. In some examples, aspects of the operations of 1425 may be performed as described in reference to Figures 9 to 12 The gateway described here selects the policy manager to execute.

[0313] At 1430, the UE may establish a connection to the legacy core network function of the legacy cellular radio network via the legacy gateway between the non-cellular radio network and the legacy core network function of the legacy cellular radio network based at least in part on the access preference rule, the gateway not being configured, and the gateway selection policy not being configured. The operations of 1430 may be performed according to the methods described herein. In some examples, aspects of the operations of 1430 may be performed as described with reference to Figures 9 to 12 The connection manager described is implemented.

[0314] Figure 15 A flow chart illustrating a method 1500 for supporting a method for handling slices accounting for Evolved Packet Data Gateway Wi-Fi access according to aspects of the present disclosure is shown. The operations of the method 1500 may be implemented by a UE 115 or components thereof as described herein. For example, the operations of the method 1500 may be implemented by a UE 115 or components thereof as described herein. Figures 9 to 12 In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the following functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the following functions.

[0315] At 1505, the UE may establish a cellular connection with a base station associated with a cellular radio network. The operations of 1505 may be performed according to the methods described herein. In some examples, aspects of the operations of 1505 may be performed as described in reference to Figures 9 to 12 The connection manager described is implemented.

[0316] At 1510, the UE may receive a configuration for connection via a non-cellular radio network, the configuration configuring the UE to attempt to connect to a core network function and, if the attempt to connect to the core network function is unsuccessful, to connect to a legacy core network function via the non-cellular radio network. The operations of 1510 may be performed according to the methods described herein. In some examples, aspects of the operations of 1510 may be performed as described with reference to Figures 9 to 12 The connection configuration manager described is executed.

[0317] At 1515, the UE may receive an access policy of the cellular radio network, the access policy identifying an access preference rule for the UE to adopt for connecting to a core network function of the cellular radio network, the access preference rule indicating to the UE that it is preferred to connect to the core network function via a non-cellular radio network. The operations of 1515 may be performed according to the methods described herein. In some examples, aspects of the operations of 1515 may be performed as described with reference to Figures 9 to 12 The described access policy manager is executed.

[0318] At 1520, the UE may determine that a gateway between the non-cellular radio network and the core network function of the cellular radio network is not configured. The operations of 1520 may be performed according to the methods described herein. In some examples, aspects of the operations of 1520 may be performed as described in reference to Figures 9 to 12 The gateway manager described here is used to execute.

[0319] At 1525, the UE may determine that the gateway selection policy of the cellular radio network is not configured. The operations of 1525 may be performed according to the methods described herein. In some examples, aspects of the operations of 1525 may be performed as described in reference to Figures 9 to 12 The gateway described here selects the policy manager to execute.

[0320] At 1530, the UE may establish a connection to the legacy core network function of the legacy cellular radio network via the legacy gateway between the non-cellular radio network and the legacy core network function of the legacy cellular radio network based at least in part on the access preference rule, the gateway not being configured, and the gateway selection policy not being configured. The operations of 1530 may be performed according to the methods described herein. In some examples, aspects of the operations of 1530 may be performed as described with reference to Figures 9 to 12 The connection manager described is implemented.

[0321] Figure 16 A flow chart illustrating a method 1600 for supporting a method for handling slices accounting for Evolved Packet Data Gateway Wi-Fi access according to aspects of the present disclosure is shown. The operations of the method 1600 may be implemented by a UE 115 or components thereof as described herein. For example, the operations of the method 1600 may be implemented by a UE 115 or components thereof as described herein. Figures 9 to 12 In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the following functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the following functions.

[0322] At 1605, the UE may establish a cellular connection with a base station associated with a cellular radio network. The operations of 1605 may be performed according to the methods described herein. In some examples, aspects of the operations of 1605 may be performed as described in reference to Figures 9 to 12 The connection manager described is implemented.

[0323] At 1610, the UE may receive an access policy of a cellular radio network, the access policy identifying an access preference rule for the UE to adopt for connecting to a core network function of the cellular radio network, the access preference rule indicating to the UE that it is preferred to connect to the core network function via the cellular radio network and via a gateway between the cellular radio network and the core network function. The operations of 1610 may be performed according to the methods described herein. In some examples, aspects of the operations of 1610 may be performed as described with reference to Figures 9 to 12 The described access policy manager is executed.

[0324] At 1615, the UE may determine that the gateway is not configured. The operations of 1615 may be performed according to the methods described herein. In some examples, aspects of the operations of 1615 may be performed as described in reference to Figures 9 to 12 The gateway manager described here is used to execute.

[0325] At 1620, the UE may determine that the gateway selection policy of the cellular radio network is not configured. The operations of 1620 may be performed according to the methods described herein. In some examples, aspects of the operations of 1620 may be performed as described in reference to Figures 9 to 12 The gateway described here selects the policy manager to execute.

[0326] At 1625, the UE may determine that the non-cellular radio network is available and the cellular radio network has become unavailable. The operations of 1625 may be performed according to the methods described herein. In some examples, aspects of the operations of 1625 may be performed as described in reference to Figures 9 to 12 The connection manager described is implemented.

[0327] At 1630, the UE may establish a connection to the legacy core network function via the legacy gateway between the legacy core network function of the legacy cellular radio network and the non-cellular radio network via the non-cellular radio network. The operations of 1630 may be performed according to the methods described herein. In some examples, aspects of the operations of 1630 may be performed as described in reference to Figures 9 to 12 The connection manager described is implemented.

[0328] At 1635, the UE may identify a legacy access policy of the legacy cellular radio network, the legacy access policy identifying a legacy access preference rule for the UE to employ for connecting to the legacy core network function, the legacy access preference rule indicating to the UE that it is preferred to connect to the legacy core network function via the non-cellular radio network. The operations of 1635 may be performed according to the methods described herein. In some examples, aspects of the operations of 1635 may be performed as described with reference to Figures 9 to 12 The described access policy manager is executed.

[0329] At 1640, the UE may determine that a cellular radio network has become available for establishing a new connection. The operations of 1640 may be performed according to the methods described herein. In some examples, aspects of the operations of 1640 may be performed as described in reference to Figures 9 to 12 The connection manager described is implemented.

[0330] At 1645, the UE may establish a new connection to the cellular radio network based at least on the access preference rule. The operations of 1645 may be performed according to the methods described herein. In some examples, aspects of the operations of 1645 may be performed as described in reference to Figures 9 to 12 The connection manager described is implemented.

[0331] Figure 17 A flow chart illustrating a method 1700 for supporting a method for handling slices accounting for Evolved Packet Data Gateway Wi-Fi access according to aspects of the present disclosure is shown. The operations of the method 1700 may be implemented by a UE 115 or components thereof as described herein. For example, the operations of the method 1700 may be implemented by a UE 115 or components thereof as described herein. Figures 9 to 12 In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the following functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the following functions.

[0332] At 1705, the UE may establish a cellular connection with a base station associated with a cellular radio network. The operations of 1705 may be performed according to the methods described herein. In some examples, aspects of the operations of 1705 may be performed as described in reference to Figures 9 to 12 The connection manager described is implemented.

[0333] At 1710, the UE may receive an access policy of the cellular radio network, the access policy identifying an access preference rule for the UE to adopt for connecting to a core network function of the cellular radio network, the access preference rule indicating to the UE that it is preferred to connect to the core network function via a non-cellular radio network. The operations of 1710 may be performed according to the methods described herein. In some examples, aspects of the operations of 1710 may be performed as described with reference to Figures 9 to 12 The described access policy manager is executed.

[0334] At 1715, the UE may determine that a non-cellular radio network is available and that a gateway between the non-cellular radio network and the core network function of the cellular radio network is not configured. The operations of 1715 may be performed according to the methods described herein. In some examples, aspects of the operations of 1715 may be performed as described in reference to Figures 9 to 12 The connection manager described is implemented.

[0335] At 1720, the UE may determine that the gateway selection policy of the cellular radio network is not configured. The operations of 1720 may be performed according to the methods described herein. In some examples, aspects of the operations of 1720 may be performed as described in reference to Figures 9 to 12 The gateway described here selects the policy manager to execute.

[0336] At 1725, the UE may establish a connection to the legacy core network function of the legacy cellular radio network via a legacy gateway between the legacy core network function and the non-cellular radio network. The operations of 1725 may be performed according to the methods described herein. In some examples, aspects of the operations of 1725 may be performed as described in reference to Figures 9 to 12 The connection manager described is implemented.

[0337] At 1730, the UE may identify a legacy access policy of the legacy cellular radio network, the legacy access policy identifying a legacy access preference rule for the UE to employ for connecting to the legacy core network function, the legacy access preference rule indicating to the UE that it is preferred to connect to the legacy core network function via the legacy cellular radio network. The operations of 1730 may be performed according to the methods described herein. In some examples, aspects of the operations of 1730 may be performed as described with reference to Figures 9 to 12 The described access policy manager is executed.

[0338] At 1735, the UE may maintain a connection to the legacy core network function of the legacy radio network via the legacy gateway based at least in part on the access preference rule. The operations of 1735 may be performed according to the methods described herein. In some examples, aspects of the operations of 1735 may be performed as described with reference to Figures 9 to 12 The connection manager described is implemented.

[0339] Figure 18 A flow chart illustrating a method 1800 for supporting a method for handling slices accounting for Evolved Packet Data Gateway Wi-Fi access according to aspects of the present disclosure is shown. The operations of the method 1800 may be implemented by a UE 115 or components thereof as described herein. For example, the operations of the method 1800 may be implemented by a UE 115 or components thereof as described herein. Figures 9 to 12 In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the following functions. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the following functions.

[0340] At 1805, the UE may establish a connection to a legacy core network function of a legacy cellular radio network via a legacy gateway between the legacy cellular radio network and the non-cellular radio network. The operations of 1805 may be performed according to the methods described herein. In some examples, aspects of the operations of 1805 may be performed as described in reference to Figures 9 to 12 The connection manager described is implemented.

[0341] At 1810, the UE may identify, for each traffic descriptor in the traffic descriptor set, a legacy access policy for the legacy cellular radio network, the legacy access policy identifying a legacy access preference rule for the UE to adopt for connecting to the legacy core network function, each legacy access preference rule indicating to the UE whether to preferably connect to the legacy core network function via the legacy cellular radio network or the non-cellular radio network for the traffic descriptor and the legacy slicing processing for the traffic descriptor. The operations of 1810 may be performed according to the methods described herein. In some examples, aspects of the operations of 1810 may be performed as described with reference to Figures 9 to 12 The traffic descriptor manager described is used to perform the operation.

[0342] At 1815, the UE may establish a connection to a core network function of the cellular radio network via a gateway between the cellular radio network and the non-cellular radio network. The operations of 1815 may be performed according to the methods described herein. In some examples, aspects of the operations of 1815 may be performed as described in reference to Figures 9 to 12 The connection manager described is implemented.

[0343] At 1820, the UE may identify, for each traffic descriptor in the traffic descriptor set, an access policy of the cellular radio network, the access policy identifying an access preference rule for the UE to adopt for connecting to a core network function of the cellular radio network, each access preference rule indicating to the UE whether to preferably connect to the core network function via a cellular radio network or a non-cellular radio network for the traffic descriptor and slice processing of the traffic descriptor. The operations of 1820 may be performed according to the methods described herein. In some examples, aspects of the operations of 1820 may be performed as described with reference to Figures 9 to 12 The described access policy manager is executed.

[0344] At 1825, for each traffic descriptor and based at least in part on the legacy slice processing and the slice processing and based at least in part on the access policy, the UE may determine whether to transfer the connection associated with the traffic descriptor to the core network function or to establish an updated connection for the traffic descriptor with the core network function. The operations of 1825 may be performed according to the methods described herein. In some examples, aspects of the operations of 1825 may be performed as described with reference to Figures 9 to 12 The traffic descriptor manager described is used to perform the operation.

[0345] It should be noted that the methods described herein describe possible implementations, and that the operations and steps may be rearranged or otherwise modified and other implementations are possible. Furthermore, aspects from two or more methods may be combined.

[0346] The following provides an overview of various aspects of the disclosure:

[0347] Aspect 1: A method for wireless communication at a UE, comprising: establishing a cellular connection with a base station associated with a cellular radio network; receiving an access policy of the cellular radio network, the access policy identifying an access preference rule for the UE to adopt for connecting to a core network function of the cellular radio network, the access preference rule indicating to the UE that connection to the core network function is preferably via a non-cellular radio network; determining that a gateway between the non-cellular radio network and the core network function of the cellular radio network is not configured; determining that a gateway selection policy of the cellular radio network is not configured; and establishing a connection to the legacy core network function of the legacy cellular radio network via a legacy gateway between the non-cellular radio network and the legacy core network function based at least in part on the access preference rule, the non-configuration of the gateway, and the non-configuration of the gateway selection policy.

[0348] Aspect 2: The method according to aspect 1 further comprises: receiving a configuration for connection via the non-cellular radio network, the configuration configuring the UE to connect to the legacy core network function or to the core network function via the non-cellular radio network.

[0349] Aspect 3: The method as described in any one of Aspects 1 to 2 further includes: receiving a configuration for connection via the non-cellular radio network, the configuration configuring the UE to attempt to connect to the core network function and connect to the legacy core network function via the non-cellular radio network if the attempt to connect to the core network function is unsuccessful.

[0350] Aspect 4: A method as described in any one of Aspects 1 to 3, wherein the cellular radio network includes a fifth generation (5G) new radio (NR) stand-alone (SA) cellular radio network; the legacy cellular radio network includes at least one of a fourth generation (4G) long term evolution (LTE) cellular radio network or a 5G NR non-stand-alone (NSA) cellular radio network; the access policy includes a UE routing selection policy (URSP); the gateway selection policy includes an access network discovery selection policy (ANDSP); the gateway includes a non-third generation partnership project (3GPP) interworking function (N3IWF) between the core network function of the 5G NR SA cellular radio network and the non-cellular radio network; and the legacy gateway includes an evolved packet core (EPC) core network function of the 4G LTE cellular radio network or the 5G NR NSA cellular radio network and an evolved packet data gateway (EPDG) between the non-cellular radio network.

[0351] Aspect 5: A method for wireless communication at a UE, comprising: establishing a cellular connection with a base station associated with a cellular radio network; receiving an access policy of the cellular radio network, the access policy identifying an access preference rule for the UE to adopt for connecting to a core network function of the cellular radio network, the access preference rule indicating to the UE that it is preferred to connect to the core network function via the cellular radio network and via a gateway between the cellular radio network and the core network function; determining that the gateway is not configured; determining that the gateway selection policy of the cellular radio network is not configured; determining that the non-cellular radio network is available and that the cellular radio network has become unavailable; establishing, via the non-cellular radio network, a connection to the legacy core network function via a legacy gateway between a legacy core network function of the legacy cellular radio network and the non-cellular radio network; identifying a legacy access policy of the legacy cellular radio network, the legacy access policy identifying a legacy access preference rule for the UE to adopt for connecting to the legacy core network function, the legacy access preference rule indicating to the UE that it is preferred to connect to the legacy core network function via the non-cellular radio network; determining that the cellular radio network has become available for establishing a new connection; and establishing the new connection to the cellular radio network based at least on the access preference rule.

[0352] Aspect 6: The method of Aspect 5 further comprises: determining that the gateway of the cellular radio network is configured based at least in part on the new connection; and transferring the connection to the legacy core network function of the legacy cellular radio network via the legacy gateway to the core network function of the cellular radio network via the gateway based at least in part on the access policy.

[0353] Aspect 7: The method according to any one of aspects 5 to 6, further comprising: receiving a configuration for connection via the non-cellular radio network, the configuration configuring the UE to connect to the legacy core network function or to the core network function via the non-cellular radio network.

[0354] Aspect 8: The method as described in any one of Aspects 5 to 7 further includes: receiving a configuration for connection via the non-cellular radio network, the configuration configuring the UE to attempt to connect to the core network function and connect to the legacy core network function via the non-cellular radio network if the attempt to connect to the core network function is unsuccessful.

[0355] Aspect 9: A method as described in any one of Aspects 5 to 8, wherein the cellular radio network includes a fifth generation (5G) new radio (NR) stand-alone (SA) cellular radio network; the legacy cellular radio network includes at least one of a fourth generation (4G) long term evolution (LTE) cellular radio network or a 5G NR non-stand-alone (NSA) cellular radio network; the access policy includes a UE routing selection policy (URSP); the gateway selection policy includes an access network discovery selection policy (ANDSP); the legacy access policy includes an access network discovery and selection function (ANDSF); the gateway includes a non-third generation partnership project (3GPP) interworking function (N3IWF) between the core network function of the 5G NR SA cellular radio network and the non-cellular radio network; and the legacy gateway includes an evolved packet core (EPC) core network function of the 4G LTE cellular radio network or the 5G NR NSA cellular radio network and an evolved packet data gateway (EPDG) between the non-cellular radio network.

[0356] Aspect 10: A method for wireless communication at a UE, comprising: establishing a cellular connection with a base station associated with a cellular radio network; receiving an access policy of the cellular radio network, the access policy identifying an access preference rule for the UE to adopt for connecting to a core network function of the cellular radio network, the access preference rule indicating to the UE that it is preferred to connect to the core network function via a non-cellular radio network; determining that the non-cellular radio network is available and a gateway between the non-cellular radio network and the core network function of the cellular radio network is not configured; and determining a gateway selection policy for the cellular radio network. is not configured; establishing a connection to a legacy core network function of a legacy cellular radio network via a legacy gateway between the legacy core network function and the non-cellular radio network; identifying a legacy access policy of the legacy cellular radio network, the legacy access policy identifying a legacy access preference rule for the UE to employ for connecting to the legacy core network function, the legacy access preference rule indicating to the UE that connection to the legacy core network function via the legacy cellular radio network is preferred; and maintaining the connection to the legacy core network function of the legacy radio network via the legacy gateway based at least in part on the access preference rule.

[0357] Aspect 11: The method according to aspect 10 further comprises: receiving a configuration for connection via the non-cellular radio network, the configuration configuring the UE to connect to the legacy core network function or to the core network function via the non-cellular radio network.

[0358] Aspect 12: The method according to any one of Aspects 10 to 11, further comprising: receiving a configuration for connection via the non-cellular radio network, the configuration configuring the UE to attempt to connect to the core network function and to connect to the legacy core network function via the non-cellular radio network if the attempt to connect to the core network function is unsuccessful.

[0359] Aspect 13: A method as described in any one of Aspects 10 to 12, wherein the cellular radio network includes a fifth generation (5G) new radio (NR) stand-alone (SA) cellular radio network; the access policy includes a UE routing selection policy (URSP); the gateway selection policy includes an access network discovery selection policy (ANDSP); the legacy access policy includes an access network discovery and selection function (ANDSF); the gateway includes a non-third generation partnership project (3GPP) interworking function (N3IWF) between the core network function of the 5GNR SA cellular radio network and the non-cellular radio network; and the legacy gateway includes an evolved packet core (EPC) core network function to the 4G LTE cellular radio network or the 5G NR NSA cellular radio network and an evolved packet data gateway (EPDG) of the non-cellular radio network.

[0360] Aspect 14: A method for wireless communication at a UE, comprising: establishing a connection to a legacy core network function of a legacy cellular radio network via a legacy gateway between the legacy cellular radio network and a non-cellular radio network; identifying, for each traffic descriptor in a traffic descriptor set, a legacy access policy of the legacy cellular radio network, the legacy access policy identifying a legacy access preference rule for the UE to adopt for connecting to the legacy core network function, each legacy access preference rule indicating to the UE whether to preferably connect to the legacy core network function via the legacy cellular radio network or the non-cellular radio network for the traffic descriptor and legacy slicing processing of the traffic descriptor; establishing a connection to the cellular radio network via the gateway between the cellular radio network and the non-cellular radio network; for each traffic descriptor in the traffic descriptor set, identifying an access policy of the cellular radio network, the access policy identifying an access preference rule for the UE to adopt for connecting to the core network function of the cellular radio network, each access preference rule indicating to the UE whether to preferably connect to the core network function via the cellular radio network or the non-cellular radio network for the traffic descriptor and slicing processing of the traffic descriptor; and for each traffic descriptor and based at least in part on the legacy slicing processing and the slicing processing and at least in part on the access policy, determining whether to transfer the connection associated with the traffic descriptor to the core network function or to establish an updated connection for the traffic descriptor with the core network function.

[0361] Aspect 15: The method as described in Aspect 14 further includes: for at least two traffic descriptors in the traffic descriptor set, determining that the legacy traffic descriptor and the traffic descriptor are the same traffic descriptor; and transferring the connection for the at least two traffic descriptors to the core network function.

[0362] Aspect 16: The method as described in any one of Aspects 14 to 15 further includes: for at least two traffic descriptors in the traffic descriptor set, determining that the legacy traffic descriptor and the traffic descriptor are different traffic descriptors; and using the core network function to update the connection for at least one of the two traffic descriptors.

[0363] Aspect 17: The method as described in any one of Aspects 14 to 16 further includes: for at least two traffic descriptors in the traffic descriptor set that are associated with the same traffic descriptor, determining that the legacy access policy and the access policy are the same access policy; and transferring the connection for the at least two traffic descriptors to the core network function.

[0364] Aspect 18: The method as described in any one of Aspects 14 to 17 further includes: for at least two traffic descriptors in the traffic descriptor set that are associated with the same traffic descriptor, determining that the legacy access policy and the access policy are different access policies; and using the core network function to update the connection for at least one of the two traffic descriptors.

[0365] Aspect 19: A method as described in any one of Aspects 14 to 18, wherein the cellular radio network includes a fifth generation (5G) new radio (NR) stand-alone (SA) cellular radio network; the legacy cellular radio network includes at least one of a fourth generation (4G) long term evolution (LTE) cellular radio network or a 5G NR non-stand-alone (NSA) cellular radio network; the access policy includes a UE routing selection policy (URSP); the legacy access policy includes an access network discovery and selection function (ANDSF); the core network function includes a 5G NR SA core network (5GC); the gateway includes a non-third generation partnership project (3GPP) interworking function (N3IWF) between the core network function of the 5G NR SA cellular radio network and the non-cellular radio network; and the legacy gateway includes an evolved packet core (EPC) core network function of the 4G LTE cellular radio network or the 5G NR NSA cellular radio network and an evolved packet data gateway (EPDG) between the non-cellular radio network.

[0366] Aspect 20: An apparatus for wireless communication at a UE, comprising a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method as described in any one of aspects 1 to 4.

[0367] Aspect 21: An apparatus for wireless communication at a UE, comprising at least one means for performing the method of any one of aspects 1 to 4.

[0368] Aspect 22: A non-transitory computer-readable medium storing code for wireless communication at a UE, the code comprising instructions executable by a processor to perform the method of any one of aspects 1 to 4.

[0369] Aspect 23: An apparatus for wireless communication at a UE, comprising a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method as described in any one of aspects 5 to 9.

[0370] Aspect 24: An apparatus for wireless communication at a UE, comprising at least one means for performing the method of any one of aspects 5 to 9.

[0371] Aspect 25: A non-transitory computer-readable medium storing code for wireless communication at a UE, the code comprising instructions executable by a processor to perform the method of any one of aspects 5 to 9.

[0372] Aspect 26: An apparatus for wireless communication at a UE, comprising a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of any one of aspects 10 to 13.

[0373] Aspect 27: An apparatus for wireless communication at a UE, comprising at least one means for performing the method of any one of aspects 10 to 13.

[0374] Aspect 28: A non-transitory computer-readable medium storing code for wireless communication at a UE, the code comprising instructions executable by a processor to perform the method of any one of aspects 10 to 13.

[0375] Aspect 29: An apparatus for wireless communication at a UE, comprising a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of any one of aspects 14 to 19.

[0376] Aspect 30: An apparatus for wireless communication at a UE, comprising at least one means for performing the method of any one of aspects 14 to 19.

[0377] Aspect 31: A non-transitory computer-readable medium storing code for wireless communication at a UE, the code comprising instructions executable by a processor to perform the method of any one of aspects 14 to 19.

[0378] Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for example purposes, and the terminology of LTE, LTE-A, LTE-A Pro, or NR may be used throughout much of the description, the techniques described herein may also be applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described may be applicable to various other wireless communication systems, such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0379] The information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referred to throughout this description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0380] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or performed with a general purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

[0381] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, each function may be stored on or transmitted by a computer-readable medium as one or more instructions or code. Other examples and implementations fall within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination thereof. Features that implement the functions may also be physically located in various locations, including being distributed so that parts of the functions are implemented at different physical locations.

[0382] Computer-readable media include both non-transient computer storage media and communication media, including any media that facilitates the transfer of a computer program from one place to another. Non-transient storage media can be any available medium that can be accessed by a general or special-purpose computer. As an example and not limitation, non-transient computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage, magnetic disk storage or other magnetic storage device, or any other non-transient medium that can be used to carry or store the desired program code means in the form of instructions or data structures and can be accessed by a general or special-purpose computer, or a general or special-purpose processor. Similarly, any connection is also properly referred to as a computer-readable medium. For example, if software is transmitted from a website, server or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwaves, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwaves are included in the definition of computer-readable media. Disk and disc, as used herein, include CDs, laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blu-ray discs, where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.

[0383] As used herein (including in the claims), "or" used in a list of items (e.g., a list of items followed by wording such as "at least one of" or "one or more of") indicates an inclusive list, so that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Likewise, as used herein, the phrase "based at least in part on" should not be read as referencing a closed set of conditions. For example, an example step described as "based at least in part on Condition A" may be based at least in part on both Condition A and Condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase "based at least in part on" should be read in the same manner as the phrase "based at least in part on."

[0384] In the accompanying drawings, similar components or features may have the same reference number. In addition, components of the same type may be distinguished by following the reference number with a dash and a second reference number that distinguishes between the similar components. If only the first reference number is used in the specification, the description applies to any of the similar components having the same first reference number, regardless of the second reference number or other subsequent reference numbers.

[0385] The descriptions set forth herein in conjunction with the accompanying drawings describe example configurations and do not represent all examples that can be implemented or that fall within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration" and does not mean "better than" or "better than other examples." This detailed description includes specific details to provide an understanding of the described techniques. However, these techniques can be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0386] The description herein is provided to enable one of ordinary skill in the art to make or use the present disclosure. Various modifications to the present disclosure will be readily apparent to those of ordinary skill in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Thus, the present disclosure is not limited to the examples and designs described herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.< / x> < / x> < / x> < / x> < / x> < / x> < / x> < / x>

Claims

1. A method for wireless communication at a user equipment (UE), comprising: establishing a cellular connection with a base station associated with a cellular radio network; receiving an access policy of the cellular radio network, the access policy identifying an access preference rule for the UE to employ for connecting to a core network function of the cellular radio network, the access preference rule indicating to the UE to preferably connect to the core network function via the cellular radio network and via a gateway between the cellular radio network and the core network function; determining that the gateway between the cellular radio network and the core network function is not configured; determining that a gateway selection policy of the cellular radio network is not configured; determining that a non-cellular radio network is available and the cellular radio network has become unavailable; establishing, via the non-cellular radio network, a connection to the second core network function via a second gateway between a second core network function of a second cellular radio network and the non-cellular radio network; identifying a second access policy for the second cellular radio network, the second access policy identifying a second access preference rule for the UE to employ for connecting to the second core network function, the second access preference rule indicating to the UE that connection to the second core network function is preferably via the non-cellular radio network; determining that the cellular radio network has become available for establishing a new connection; as well as The new connection to the cellular radio network is established based at least on the access preference rules.

2. The method of claim 1, further comprising: determining, based at least in part on the new connection, that the gateway of the cellular radio network is configured; as well as A connection to the second core network function of the second cellular radio network via the second gateway is transferred to the core network function of the cellular radio network via the gateway based at least in part on the access policy.

3. The method of claim 1, further comprising: A configuration for connection via the non-cellular radio network is received, the configuration configuring the UE to connect to the second core network function or to the core network function via the non-cellular radio network.

4. The method of claim 1, further comprising: A configuration for connection via the non-cellular radio network is received, the configuration configuring the UE to attempt to connect to the core network function and to connect to a second core network function via the non-cellular radio network if the attempt to connect to the core network function is unsuccessful.

5. The method of claim 1, wherein: The cellular radio network comprises a fifth generation 5G New Radio NR standalone SA cellular radio network; The second cellular radio network comprises at least one of a fourth generation (4G) Long Term Evolution (LTE) cellular radio network or a 5G NR Non-Standalone (NSA) cellular radio network; The access strategy includes a user equipment UE routing strategy URSP; The gateway selection strategy includes an access network discovery selection strategy ANDSP; The second access strategy includes an access network discovery and selection function ANDSF; The gateway comprises a non-3rd Generation Partnership Project 3GPP interworking function N3IWF between the core network function of the 5G NR SA cellular radio network and the non-cellular radio network; and The second gateway includes an evolved packet data gateway EPDG between an evolved packet core EPC core network function of the 4G LTE cellular radio network or the 5G NR NSA cellular radio network and the non-cellular radio network.

6. A method for wireless communication at a user equipment (UE), comprising: establishing a cellular connection with a base station associated with a cellular radio network; receiving an access policy of the cellular radio network, the access policy identifying an access preference rule for the UE to employ for connecting to a core network function of the cellular radio network, the access preference rule indicating to the UE that connection to the core network function is preferably via a non-cellular radio network; determining that the non-cellular radio network is available and a gateway between the non-cellular radio network and the core network function of the cellular radio network is not configured; determining that a gateway selection policy of the cellular radio network is not configured; establishing a connection to a second core network function of a second cellular radio network via a second gateway between the second core network function and the non-cellular radio network; identifying a second access policy for the second cellular radio network, the second access policy identifying a second access preference rule for the UE to adopt for connecting to the second core network function, the second access preference rule indicating to the UE that connection to the second core network function is preferably via the second cellular radio network; as well as A connection is maintained to the second core network function of the second cellular radio network via the second gateway based at least in part on the access preference rule.

7. The method of claim 6, further comprising: A configuration for connection via the non-cellular radio network is received, the configuration configuring the UE to connect to the second core network function or to the core network function via the non-cellular radio network.

8. The method of claim 6, further comprising: A configuration for connection via the non-cellular radio network is received, the configuration configuring the UE to attempt to connect to the core network function and to connect to a second core network function via the non-cellular radio network if the attempt to connect to the core network function is unsuccessful.

9. The method of claim 6, wherein: The cellular radio network comprises a fifth generation 5G New Radio NR standalone SA cellular radio network; The access strategy includes a user equipment UE routing strategy URSP; The gateway selection strategy includes an access network discovery selection strategy ANDSP; The second access strategy includes an access network discovery and selection function ANDSF; The gateway comprises a non-3rd Generation Partnership Project 3GPP interworking function N3IWF between the core network function of the 5G NR SA cellular radio network and the non-cellular radio network; and The second gateway includes an evolved packet core (EPC) core network function to the fourth generation (4G) Long Term Evolution (LTE) cellular radio network or the 5GNR (NSA) cellular radio network and an evolved packet data gateway (EPDG) to the non-cellular radio network.

10. An apparatus for wireless communication at a user equipment (UE), comprising: processor; a memory coupled to the processor; as well as instructions stored in the memory and executable by the processor, the instructions causing the apparatus to: establishing a cellular connection with a base station associated with a cellular radio network; receiving an access policy of the cellular radio network, the access policy identifying an access preference rule for the UE to employ for connecting to a core network function of the cellular radio network, the access preference rule indicating to the UE to preferably connect to the core network function via the cellular radio network and via a gateway between the cellular radio network and the core network function; determining that the gateway between the cellular radio network and the core network function is not configured; determining that a gateway selection policy of the cellular radio network is not configured; determining that a non-cellular radio network is available and the cellular radio network has become unavailable; establishing, via the non-cellular radio network, a connection to the second core network function via a second gateway between a second core network function of a second cellular radio network and the non-cellular radio network; identifying a second access policy for the second cellular radio network, the second access policy identifying a second access preference rule for the UE to employ for connecting to the second core network function, the second access preference rule indicating to the UE that connection to the second core network function is preferably via the non-cellular radio network; determining that the cellular radio network has become available for establishing a new connection; as well as A new connection to the cellular radio network is established based at least on the access preference rules.

11. The apparatus of claim 10, wherein the instructions are further executable by the processor to cause the apparatus to: determining, based at least in part on the new connection, that the gateway of the cellular radio network is configured; and A connection to the second core network function of the second cellular radio network via the second gateway is transferred to the core network function of the cellular radio network via the gateway based at least in part on the access policy.

12. The apparatus of claim 10, wherein the instructions are further executable by the processor to cause the apparatus to: A configuration for connection via the non-cellular radio network is received, the configuration configuring the UE to connect to the second core network function or to the core network function via the non-cellular radio network.

13. The apparatus of claim 10, wherein the instructions are further executable by the processor to cause the apparatus to: A configuration for connection via the non-cellular radio network is received, the configuration configuring the UE to attempt to connect to the core network function and to connect to a second core network function via the non-cellular radio network if the attempt to connect to the core network function is unsuccessful.

14. The apparatus of claim 10, wherein: The cellular radio network comprises a fifth generation 5G New Radio NR standalone SA cellular radio network; The second cellular radio network comprises at least one of a fourth generation (4G) Long Term Evolution (LTE) cellular radio network or a 5G NR Non-Standalone (NSA) cellular radio network; The access strategy includes a user equipment UE routing strategy URSP; The gateway selection strategy includes an access network discovery selection strategy ANDSP; The second access strategy includes an access network discovery and selection function ANDSF; The gateway comprises a non-3rd Generation Partnership Project 3GPP interworking function N3IWF between the core network function of the 5G NR SA cellular radio network and the non-cellular radio network; and The second gateway includes an evolved packet data gateway EPDG between an evolved packet core EPC core network function of the 4G LTE cellular radio network or the 5G NR NSA cellular radio network and the non-cellular radio network.

15. An apparatus for wireless communication at a user equipment (UE), comprising: processor; a memory coupled to the processor; as well as instructions stored in the memory and executable by the processor, the instructions causing the apparatus to: establishing a cellular connection with a base station associated with a cellular radio network; receiving an access policy of the cellular radio network, the access policy identifying an access preference rule for the UE to employ for connecting to a core network function of the cellular radio network, the access preference rule indicating to the UE that connection to the core network function is preferably via a non-cellular radio network; determining that the non-cellular radio network is available and a gateway between the non-cellular radio network and the core network function of the cellular radio network is not configured; determining that a gateway selection policy of the cellular radio network is not configured; establishing a connection to a second core network function of a second cellular radio network via a second gateway between the second core network function and the non-cellular radio network; identifying a second access policy for the second cellular radio network, the second access policy identifying a second access preference rule for the UE to adopt for connecting to the second core network function, the second access preference rule indicating to the UE that connection to the second core network function is preferably via the second cellular radio network; as well as A connection is maintained to the second core network function of the second cellular radio network via the second gateway based at least in part on the access preference rule.

16. The apparatus of claim 15, wherein the instructions are further executable by the processor to cause the apparatus to: A configuration for connection via the non-cellular radio network is received, the configuration configuring the UE to connect to the second core network function or to the core network function via the non-cellular radio network.

17. The apparatus of claim 15, wherein the instructions are further executable by the processor to cause the apparatus to: A configuration for connection via the non-cellular radio network is received, the configuration configuring the UE to attempt to connect to the core network function and to connect to a second core network function via the non-cellular radio network if the attempt to connect to the core network function is unsuccessful.

18. The apparatus of claim 15, wherein: The cellular radio network comprises a fifth generation 5G New Radio NR standalone SA cellular radio network; The access strategy includes a user equipment UE routing strategy URSP; The gateway selection strategy includes an access network discovery selection strategy ANDSP; The second access strategy includes an access network discovery and selection function ANDSF; The gateway comprises a non-3rd Generation Partnership Project 3GPP interworking function N3IWF between the core network function of the 5G NR SA cellular radio network and the non-cellular radio network; and The second gateway includes an evolved packet core (EPC) core network function to the fourth generation (4G) Long Term Evolution (LTE) cellular radio network or the 5GNR (NSA) cellular radio network and an evolved packet data gateway (EPDG) to the non-cellular radio network.

19. An apparatus for wireless communication at a user equipment (UE), comprising: means for establishing a cellular connection with a base station associated with a cellular radio network; means for receiving an access policy of the cellular radio network, the access policy identifying an access preference rule for the UE to employ for connecting to a core network function of the cellular radio network, the access preference rule indicating to the UE to preferably connect to the core network function via the cellular radio network and via a gateway between the cellular radio network and the core network function; means for determining that the gateway between the cellular radio network and the core network function is not configured; means for determining that a gateway selection policy of the cellular radio network is not configured; means for determining that a non-cellular radio network is available and that the cellular radio network has become unavailable; means for establishing, via the non-cellular radio network, a connection to a second core network function of a second cellular radio network via a second gateway between the non-cellular radio network and the second core network function; means for identifying a second access policy for the second cellular radio network, the second access policy identifying a second access preference rule for the UE to employ for connecting to the second core network function, the second access preference rule indicating to the UE that connection to the second core network function is preferably via the non-cellular radio network; means for determining that said cellular radio network has become available for establishing a new connection; as well as means for establishing said new connection to said cellular radio network based at least on said access preference rules.

20. The apparatus of claim 19, further comprising: means for determining, based at least in part on the new connection, that the gateway of the cellular radio network is configured; as well as Means for transferring a connection to the second core network function of the second cellular radio network via the second gateway to the core network function of the cellular radio network via the gateway based at least in part on the access policy.

21. The apparatus of claim 19, further comprising: means for receiving a configuration for connection via the non-cellular radio network, the configuration configuring the UE to connect to the second core network function or to the core network function via the non-cellular radio network.

22. The apparatus of claim 19, further comprising: means for receiving a configuration for connection via the non-cellular radio network, the configuration configuring the UE to attempt to connect to the core network function and to connect to a second core network function via the non-cellular radio network if the attempt to connect to the core network function is unsuccessful.

23. The apparatus of claim 19, wherein: The cellular radio network comprises a fifth generation 5G New Radio NR standalone SA cellular radio network; The second cellular radio network comprises at least one of a fourth generation (4G) Long Term Evolution (LTE) cellular radio network or a 5G NR Non-Standalone (NSA) cellular radio network; The access strategy includes a user equipment UE routing strategy URSP; The gateway selection strategy includes an access network discovery selection strategy ANDSP; The second access strategy includes an access network discovery and selection function ANDSF; The gateway comprises a non-3rd Generation Partnership Project 3GPP interworking function N3IWF between the core network function of the 5G NR SA cellular radio network and the non-cellular radio network; and The second gateway includes an evolved packet data gateway EPDG between an evolved packet core EPC core network function of the 4G LTE cellular radio network or the 5G NR NSA cellular radio network and the non-cellular radio network.

24. An apparatus for wireless communication at a user equipment (UE), comprising: means for establishing a cellular connection with a base station associated with a cellular radio network; means for receiving an access policy of the cellular radio network, the access policy identifying an access preference rule for the UE to employ for connecting to a core network function of the cellular radio network, the access preference rule indicating to the UE to preferably connect to the core network function via a non-cellular radio network; means for determining that the non-cellular radio network is available and a gateway between the non-cellular radio network and the core network function of the cellular radio network is not configured; means for determining that a gateway selection policy of the cellular radio network is not configured; means for establishing a connection to a second core network function of a second cellular radio network via a second gateway between the second core network function and the non-cellular radio network; means for identifying a second access policy for the second cellular radio network, the second access policy identifying a second access preference rule for the UE to employ for connecting to the second core network function, the second access preference rule indicating to the UE that connection to the second core network function is preferably via the second cellular radio network; as well as Means for maintaining a connection to the second core network function of the second cellular radio network via the second gateway based at least in part on the access preference rule.

25. The apparatus of claim 24, further comprising: means for receiving a configuration for connection via the non-cellular radio network, the configuration configuring the UE to connect to the second core network function or to the core network function via the non-cellular radio network.

26. The apparatus of claim 24, further comprising: means for receiving a configuration for connection via the non-cellular radio network, the configuration configuring the UE to attempt to connect to the core network function and to connect to a second core network function via the non-cellular radio network if the attempt to connect to the core network function is unsuccessful.

27. The apparatus of claim 24, wherein: The cellular radio network comprises a fifth generation 5G New Radio NR standalone SA cellular radio network; The access strategy includes a user equipment UE routing strategy URSP; The gateway selection strategy includes an access network discovery selection strategy ANDSP; The second access strategy includes an access network discovery and selection function ANDSF; The gateway comprises a non-3rd Generation Partnership Project 3GPP interworking function N3IWF between the core network function of the 5G NR SA cellular radio network and the non-cellular radio network; and The second gateway includes an evolved packet core (EPC) core network function to the fourth generation (4G) Long Term Evolution (LTE) cellular radio network or the 5GNR (NSA) cellular radio network and an evolved packet data gateway (EPDG) to the non-cellular radio network.

28. A non-transitory computer-readable medium storing code for wireless communication at a user equipment (UE), the code comprising instructions executable by a processor to: establishing a cellular connection with a base station associated with a cellular radio network; receiving an access policy of the cellular radio network, the access policy identifying an access preference rule for the UE to employ for connecting to a core network function of the cellular radio network, the access preference rule indicating to the UE to preferably connect to the core network function via the cellular radio network and via a gateway between the cellular radio network and the core network function; determining that the gateway between the cellular radio network and the core network function is not configured; determining that a gateway selection policy of the cellular radio network is not configured; determining that a non-cellular radio network is available and the cellular radio network has become unavailable; establishing, via the non-cellular radio network, a connection to the second core network function via a second gateway between a second core network function of a second cellular radio network and the non-cellular radio network; identifying a second access policy for the second cellular radio network, the second access policy identifying a second access preference rule for the UE to employ for connecting to the second core network function, the second access preference rule indicating to the UE that connection to the second core network function is preferably via the non-cellular radio network; determining that the cellular radio network has become available for establishing a new connection; as well as A new connection to the cellular radio network is established based at least on the access preference rules.

29. The non-transitory computer readable medium of claim 28, wherein the instructions are further executable to: determining, based at least in part on the new connection, that the gateway of the cellular radio network is configured; and A connection to the second core network function of the second cellular radio network via the second gateway is transferred to the core network function of the cellular radio network via the gateway based at least in part on the access policy.

30. The non-transitory computer readable medium of claim 28, wherein the instructions are further executable to: A configuration for connection via the non-cellular radio network is received, the configuration configuring the UE to connect to the second core network function or to the core network function via the non-cellular radio network.

31. The non-transitory computer readable medium of claim 28, wherein the instructions are further executable to: A configuration for connection via the non-cellular radio network is received, the configuration configuring the UE to attempt to connect to the core network function and to connect to a second core network function via the non-cellular radio network if the attempt to connect to the core network is unsuccessful.

32. The non-transitory computer-readable medium of claim 28, wherein: The cellular radio network comprises a fifth generation 5G New Radio NR standalone SA cellular radio network; The second cellular radio network comprises at least one of a fourth generation (4G) Long Term Evolution (LTE) cellular radio network or a 5G NR Non-Standalone (NSA) cellular radio network; The access strategy includes a user equipment UE routing strategy URSP; The gateway selection strategy includes an access network discovery selection strategy ANDSP; The second access strategy includes an access network discovery and selection function ANDSF; The gateway comprises a non-3rd Generation Partnership Project 3GPP interworking function N3IWF between the core network function of the 5G NR SA cellular radio network and the non-cellular radio network; and The second gateway includes an evolved packet data gateway EPDG between an evolved packet core EPC core network function of the 4G LTE cellular radio network or the 5G NR NSA cellular radio network and the non-cellular radio network.

33. A non-transitory computer-readable medium storing code for wireless communication at a user equipment (UE), the code comprising instructions executable by a processor to: establishing a cellular connection with a base station associated with a cellular radio network; receiving an access policy of the cellular radio network, the access policy identifying an access preference rule for the UE to employ for connecting to a core network function of the cellular radio network, the access preference rule indicating to the UE that connection to the core network function is preferably via a non-cellular radio network; determining that the non-cellular radio network is available and a gateway between the non-cellular radio network and the core network function of the cellular radio network is not configured; determining that a gateway selection policy of the cellular radio network is not configured; establishing a connection to a second core network function of a second cellular radio network via a second gateway between the second core network function and the non-cellular radio network; identifying a second access policy for the second cellular radio network, the second access policy identifying a second access preference rule for the UE to adopt for connecting to the second core network function, the second access preference rule indicating to the UE that connection to the second core network function is preferably via the second cellular radio network; as well as A connection is maintained to the second core network function of the second cellular radio network via the second gateway based at least in part on the access preference rule.

34. The non-transitory computer readable medium of claim 33, wherein the instructions are further executable to: A configuration for connection via the non-cellular radio network is received, the configuration configuring the UE to connect to the second core network function or to the core network function via the non-cellular radio network.

35. The non-transitory computer readable medium of claim 33, wherein the instructions are further executable to: A configuration for connection via the non-cellular radio network is received, the configuration configuring the UE to attempt to connect to the core network function and to connect to a second core network function via the non-cellular radio network if the attempt to connect to the core network is unsuccessful.

36. The non-transitory computer-readable medium of claim 33, wherein: The cellular radio network comprises a fifth generation 5G New Radio NR standalone SA cellular radio network; The access strategy includes a user equipment UE routing strategy URSP; The gateway selection strategy includes an access network discovery selection strategy ANDSP; The second access strategy includes an access network discovery and selection function ANDSF; The gateway comprises a non-3rd Generation Partnership Project 3GPP interworking function N3IWF between the core network function of the 5G NR SA cellular radio network and the non-cellular radio network; and The second gateway includes an evolved packet core (EPC) core network function to the fourth generation (4G) Long Term Evolution (LTE) cellular radio network or the 5GNR (NSA) cellular radio network and an evolved packet data gateway (EPDG) to the non-cellular radio network.

Images