Abstract: Disclosed are systems and methods for a network framework for Wi-Fi barring of network usage that enables network management at a device level, which provides capabilities for the optimization of internet connectivity and data usage based on a user's and/or device's specific needs and priorities. The framework operates to handle information management system (IMS) connections and IMS registration failures over evolved Packet Data Gateways (ePDG). The framework provides a Wi-Fi backoff timer that can be implemented for particular Wi-Fi networks, which can correspond to a Wi-Fi access point (AP). Thus, a connected device (e.g., a user's smart phone) can toggle connectivity to and/or from a cellular network in accordance with encountered failures with an AP via the timer's implementation and network control of the device.

Abstract: In some implementations, a device may generate a user equipment (UE) route selection policy (URSP) rule that indicates a route selection descriptor and a traffic descriptor, and one of the route selection descriptor or the traffic descriptor indicates a core network (CN) type associated with the URSP rule. The device may transmit the URSP rule.

Abstract: A device may forward, to a User Equipment device (UE) over a network, an updated list of subscribed network slices; receive, from the UE, a registration request that includes a list of requested network slices; generate, based on the list of requested network slices, an updated list of allowed network slices; and send the updated list of allowed network slices to the UE. The updated list of allowed network slices may be synchronized to the updated list of subscribed network slices.

Abstract: A device described herein may maintain information associating sets of traffic attributes with respective sets of Quality of Service (“QoS”) parameters, and may receive a request to establish a traffic flow. The request may indicate one or more traffic attributes associated with the requested traffic flow. The device may compare the one or more traffic attributes, included in the request, to the information associating the sets of traffic attributes with the respective sets of QoS parameters, identify a particular set of QoS parameters with which the traffic flow is associated, establish a communication session with a network based on the particular set of QoS parameters, communicate traffic, associated with the traffic flow, with the network via the established communication session. The device may include an application programming interface (“API”) via which an application associated with the traffic flow may specify the traffic attributes in the request.

Abstract: In some implementations, a radio access network (RAN) may receive a graded quality of service (QoS) profile indicating a set of QoS profiles and corresponding observed flow data rates. The RAN may measure an observed flow data rate of traffic associated with a session. The RAN may select a QoS profile from the set of QoS profiles based on the observed flow data rate. The RAN may apply the QoS profile to the session.

Abstract: Systems and methods described herein enable network slice selection from different service providers using embedded Subscriber Identity Modules (eSIMs). A user equipment (UE) device stores a first eSIM associated with a first service provider of a first mobile network and a second eSIM associated with a second service provider of a second mobile network. The UE device also stores policy rules governing selection of the first eSIM and the second eSIM, wherein the policy rules limit use of second eSIM to a network slice on the second mobile network. The UE device initiates a session connection request associated with an application and directs the session connection request through one of the first eSIM or the second eSIM based on the policy rules.

Abstract: A method, a network device, and a non-transitory computer-readable storage medium are described in relation to an registration support service. The registration support service may include providing an end device with registration support information that may facilitate a re-registration of the end device with an access and mobility management function, a mobility management entity, or the like. The registration support information may include a time period and/or a location with which the end device may initiate a registration procedure. The registration support information may be generated based on historical behavior of the end device.

Abstract: A system comprises one or more devices that implement a network function. The network function receives a connection request for a User Equipment (UE) device, the connection request including requested Network Slice Selection Assistance Information (NSSAI) for a mobile network. The network function retrieves subscribed NSSAI that includes NSSAI of slices from a subscription associated with the UE device. The network function determines expanded allowed NSSAI based on the subscribed NSSAI and NSSAI supported by the network. The network function sends, to the user device, the expanded allowed NSSAI.

Abstract: A gateway wirelessly connected to a mobile network receives traffic for a user equipment device (UE) connected to the gateway. A router of the gateway identifies a network slice, from a set of network slices potentially supported by the mobile network, for the traffic, and applies network address translation (NAT) policy rules to select a NAT type from multiple different NAT types to perform for the traffic based on the identified network slice. The router of the gateway performs the selected NAT type for the traffic and forwards the traffic to a gateway modem for transmitting towards the traffic's destination.

Abstract: A gateway wirelessly connected to a mobile network receives traffic for a user equipment device (UE) connected to the gateway. A router of the gateway identifies a network slice, from a set of network slices potentially supported by the mobile network, for the traffic, and applies network address translation (NAT) policy rules to select a NAT type from multiple different NAT types to perform for the traffic based on the identified network slice. The router of the gateway performs the selected NAT type for the traffic and forwards the traffic to a gateway modem for transmitting towards the traffic's destination.

Abstract: A device, such as a User Equipment (“UE”), may identify that the device is communicatively coupled to a wireless network via a particular network slice. The particular network slice may be associated with a particular set of Quality of Service (“QoS”) parameters, Service Level Agreements (“SLAs”), or the like. The UE may determine the particular network slice based on a slice identifier provided by a network interface of the device, based on attributes of traffic sent or received via the wireless network, and/or based on attributes of a wireless connection between the device and the wireless network. The device may identify a slice indicator associated with the particular network slice, and may present the slice indicator via a user interface of the device. The presented slice indicator may notify a user of the device that the particular network slice is being used for traffic sent or received via the device.

Abstract: A device may create a list of identifiers for base stations that support a fixed wireless service for a user device. The device may receive a first identifier of a first base station associated with a first attach request of the user device. The device may enable the fixed wireless service for the first base station for the user device when the first identifier is included in the list of identifiers. The device may disable the fixed wireless service for the first base station for the user device when the first identifier is not included in the list of identifiers.

Abstract: A user equipment (UE) may store a default user equipment route selection policy (URSP) and may receive, from a fourth-generation (4G) core network, a default protocol configuration option (PCO) value for a default network slice of the 4G core network. The UE may utilize the default network slice based on the default URSP and the default PCO value and may receive a request to update the default URSP with a new URSP associated with a new network slice of the 4G core network. The UE may update the default URSP with the new URSP to generate an updated URSP and may receive, from the 4G core network, a new PCO value for the new network slice of the 4G core network. The UE may utilize the default network slice and the new network slice based on the updated URSP, the default PCO value, and the new PCO value.

Abstract: Systems and methods described herein enable dynamic in-app subscriptions and controls for network slices. A user device receives a command to launch an application and identifies a preferred network slice for the application. The application determines that a network services subscription for the user device does not include the preferred network slice and obtains consent, from a user of the user device, to add the preferred network slice to the network services subscription. The user device receives, from a provider network, authorization for using the preferred network slice by the application and initiates a network session on the preferred network slice.

Abstract: In the various embodiments, systems and methods are disclosed for determining the location of User Equipment (UE) in a network and for authorizing access to content based on said location. An aspect of the present disclosure is a method including receiving, by a Content Authorization Function (CAF), a request to provide a UE type of a UE and a physical location associated with the UE, the request including a UE Internet Protocol (IP) address associated with the UE; querying, by the CAF, a Network Function (NF), to provide the UE type and associated physical location, the query including the UE IP address; receiving, by the CAF from the NF, the UE type and associated physical location; and transmitting the UE type and associated physical location.

Abstract: A network device may delegate a first prefix length to a primary WAN interface and delegate a second prefix length to a backup WAN interface. The network device may assign a first primary prefix and a first backup prefix to a first VLAN interface and may assign a second primary prefix and a second backup prefix to a second VLAN interface. The network device may provide egress traffic from host devices, connected to the first VLAN interface and to the second VLAN interface, to the primary WAN interface and without prefix translation, when the primary WAN interface is available. The network device may provide ingress traffic to the host devices, via the primary WAN interface and without prefix translation, when the primary WAN interface is available.

Abstract: A device described herein may maintain information associating sets of traffic attributes with respective sets of Quality of Service (“QoS”) parameters, and may receive a request to establish a traffic flow. The request may indicate one or more traffic attributes associated with the requested traffic flow. The device may compare the one or more traffic attributes, included in the request, to the information associating the sets of traffic attributes with the respective sets of QoS parameters, identify a particular set of QoS parameters with which the traffic flow is associated, establish a communication session with a network based on the particular set of QoS parameters, communicate traffic, associated with the traffic flow, with the network via the established communication session. The device may include an application programming interface (“API”) via which an application associated with the traffic flow may specify the traffic attributes in the request.

Abstract: A first wireless access device, associated with a wireless service provider, establishes a wireless local area network connection with a second wireless access device and receives a certificate including a unique identifier associated with the second wireless access device. The first wireless access device determines whether the second wireless access device is authorized to connect to the first wireless access device. For example, if the certificate is signed by a certificate authority associated with the wireless service provider and the unique identifier appears in a whitelist stored at the first wireless access device, the first wireless access device and the second wireless access device perform a mutual authentication procedure based on one or more ephemeral keys. The first wireless access device provides the second wireless access device with access to a wide area network based on successful completion of the mutual authentication procedure.

Abstract: Techniques for stateless address auto-configuration with support for multiple, different subnets are disclosed. In one embodiment, a method is disclosed comprising receiving, by a network device, a router solicitation (RS) message from a network node, generating, by the network device, a router advertisement (RA) message for use in determining the network node's network address, the RA message including a network address prefix and subnetting information, the subnetting information comprising a subnet address, a subnet address length and a subnet option type, and transmitting, by the network device, the RA message to the network node.

Abstract: An Ethernet protocol data unit (PDU) over 5G service is provided. A network device in a core network stores addresses of advertised subnets, associated with multiple user equipment or customer premises equipment (UE/CPE) devices, in a subnet table that correlates a MAC address of each of the multiple UE/CPE devices to a subnet address. The network device receives an allocation and retention priority (ARP) request over a data link layer. The ARP request indicates an IP address for a target host of a data flow. The network device determines, based on the subnet table and the IP address, a MAC address of one UE/CPE device servicing the host address. The network device sends a directed ARP request to the UE/CPE device using the MAC address, receives in response a target MAC address for the target host, and sends a response to the ARP request with the target MAC address.