Abstract: Systems and methods provide a selective network slice admission control (NSAC) service on a per user equipment (UE) device level, and include manage select NSAC criteria related to a first limit to a number of user equipment (UE) devices and a second limit to a number of protocol data unit (PDU) sessions supportable on a network slice; receive an indication that a first UE device requests a first PDU session on the network slice; apply at least one of the select NSAC criteria to the first UE device and/or the first PDU session; determine, based on the application, that the first UE device is countable toward the first limit and/or the first PDU session is countable toward the second limit; and generate an NSAC update response message indicating that the first UE device and/or the first PDU session is countable.

Abstract: A system described herein may dynamically determine whether a User Equipment (“UE”) is authorized to access a given Local Area Data Network (“LADN”) based on dynamically determined factors, such as temporal factors, network load factors, registration or de-registration of the UE for the LADN, etc. Updates to such polices may be further used to determine whether the UE is authorized to access the LADN. Thus, the providing of services associated with a LADN may be more dynamic and based on additional factors than a determination of whether UE subscription information (e.g., as provided by a UE information repository) indicates that a given UE has subscribed to the LADN.

Abstract: A network device may receive a PDU session create message associated with establishing a PDU session with a user device and via a RAN, and may receive a first 5QI value and a second 5QI value associated with the PDU session. The network device may attempt to establish the PDU session with the first 5QI value and via the RAN, and may receive an indication that the first 5QI value is not supported for establishing the PDU session. The network device may cause the PDU session to be established with the second 5QI value, and via the RAN, based on the indication that the first 5QI value is not supported for establishing the PDU session.

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 method may include subscribing, by a first network repository function (NRF) located in a first segment of a network, to event information associated with a unified data management (UDM) function or a unified data repository (UDR) located in a second segment of the network. The method may also include receiving, by the first NRF and from a second NRF included in the second segment UDM or UDR information associated with the UDM or UDR located in the second segment of the network. The method may further include receiving, at the first NRF, a UDM or UDR discovery request from a network function (NF), wherein the UDM or UDR discovery request is associated with subscriber information stored in a UDM or UDR located in the second segment of the network, and responding, by the first NRF, to the discovery request.

Abstract: A method, a device, and a non-transitory storage medium are described in which a network analytics model service is provided. The service may include ingesting customized models and non-customized models by a network analytics device. The ingestion procedure may include receiving the model and model specification data. The service may include provisioning the model and registering the model for discovery by other network devices. The service may include specifying customized identifiers to be used prospective subscribing network devices for the analytics information. The service may also facilitate the use of the analytics information by the subscribing network devices.

Abstract: A method, a system, and a non-transitory storage medium are described in which an discovery service is provided. The discovery service may provide a network device to request for binding information from a binding service function. The request may or may not include information that indicates a type of policy control function. For example, the information may indicate a session management policy control function, an access management policy control function, or another dedicated type of policy control function.

Abstract: A method, a device, and a non-transitory storage medium are described in which an inter-operator mobility service is provided. The service may provide provisioning decisions and configurations that may include core devices that are shared between users of a first entity and users of a second entity, or are dedicated to the users of the second entity to support a network slice and/or access to an application service for end devices associated with the second entity. The service may manage access and use of radio frequencies associated with the first and second entities based on subscription information and location of the end devices associated with first and second entities. The service may further include enabling inter-network handovers associated with end devices associated with end devices associated with the second entity.

Abstract: A system may receive, by a first network device in an access network, a request to setup a radio access bearer (RAB) for use in establishing a connection with a user equipment (UE), wherein the request includes at least one Quality-of-Service (QOS) attribute associated with the request. The first network device may determine that the at least one QoS attribute is not supported by the access network and may send a notification that RAB setup has failed to a second network device in a core network, wherein the notification includes a cause indicator that indicates that the failure is caused by an unsupported QoS. In response, the core network may modify the request to include a default quality of service attribute that is supported by the access network and may send the modified request to the first network device.

Abstract: A system described herein may request, from a first network, access parameters associated with a User Equipment (“UE”) and a second network. The first network may be, for example, a home network with respect to the UE and the second network may be a roaming network with respect to the UE. The system may receive, from the first network, the requested access parameters associated with the UE and the second network, which may include authentication information associated with the first network (e.g., as provided by an authentication system of the first network). The system may output the access parameters and the authentication information to the UE, which may verify the access parameters based on the authentication information, select one or more access parameters of the verified access parameters, and request a communication session establishment with the second network in accordance with the selected one or more access parameters.

Abstract: A method, a device, and a non-transitory storage medium are described in which a network slice selection service is provided. The service may include using route selection policies that includes radio frequency criteria for selection of a network slice. The service may include establishing an application session based on the route selection policies. The service may further include determining that a radio frequency of the network slice cannot be sustained. The service may include executing an application session release procedure and an application session establishment procedure. The procedures may include using cause data and context data pertaining to the initial application session to re-establish the application session via a different network slice and a different radio frequency based on the route selection policies.

Abstract: A method, a network device, and a non-transitory computer-readable storage medium are described in relation to a hybrid network slicing service. The hybrid network slicing service may enable the initial configuration of a network slice according to network slice requests that may include customized and user-specified network performance criteria. The hybrid network slicing service may enable network slice requests to specify selection of network resources and use/availability based on entity-based criteria including end device and/or application specific associations. The hybrid network slicing service may optimize network slice configurations and generate network slice templates.

Abstract: A system described herein may identify a requested communication session between a UE and a network, such as a core of a wireless network. The system may identify Quality of Service (“QoS”) information associated with the UE and/or the requested communication session. The QoS information may include or may be based on a network slice identifier, a QoS value, a Service Level Agreement (“SLA”), one or more models associated with UE attributes, or other suitable information. The system may determine a maximum transmission unit (“MTU”) configuration for the UE based on the identified QoS information and/or models that associate UE attributes to MTU configurations. The system may implement the determined MTU configuration, including providing the MTU configuration to one or more gateways or endpoints of the network and/or to the UE. The UE and the network may accordingly use the MTU configuration when communicating via the requested communication session.

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 network device may receive historical data identifying historical error data and error data categorizations associated with a first core network and may store the historical data in a data structure. The network device may receive a request associated with a user equipment and may receive error data from the first core network based on the request. The network device may receive network health data identifying load levels and health of the first core network and a second core network. The network device may determine possible cause data identifying causes associated with the error data based on the historical data, the error data, and the network health data. The network device may generate a cause code for the user equipment based on the possible cause data and may provide the cause code to the user equipment.

Abstract: A method, a network device, and a non-transitory storage medium are described in which an application-aware scheduling service is provided. The application-aware scheduling service may be configured with bandwidth values and usability values for traffic of applications. The application-aware scheduling service may manage air interface scheduling based on the bandwidth and usability values. The application-aware scheduling service may perform packet inspection to identify an application relating to traffic. The application-aware scheduling service may be configured with a maximum bandwidth for traffic of applications.

Abstract: In some implementations, a policy control function (PCF) device may receive, from an access and mobility management function (AMF) device, an access and mobility (AM) policy association request that is related to a user equipment (UE) that is associated with AM policy data. The PCF device may modify at least a portion of the AM policy data to generate modified AM policy data associated with the UE. The PCF device may create, based on the modified AM policy data, an AM control policy associated with the UE. The PCF device may transmit, to the AMF device, an AM policy association message, responsive to the AM policy association request, indicating the AM control policy.

Abstract: A method may include identifying network slices associated with transmitting data in a network and determining, by a routing device, that a failure associated with a path used to transmit data has occurred. The method may also include determining, by the routing device, whether the failure is associated with one of the plurality of network slices. The method may further include prioritizing, by the routing device, a route selection process in response to determining that the failure is associated with one of the plurality of network slices.

Abstract: In some implementations, a device of a network may receive, from a user equipment (UE), a request associated with enabling the UE to access a network, wherein the request includes a first routing indicator. The device may identify an authentication manager, of the network, that is mapped to the first routing indicator in an entry of a routing table of the network. The device may route the request to the authentication manager of the network to permit the authentication manager to authenticate the UE. The device may purge, based on the request being routed to the authentication manager, the entry to remove the first routing indicator from the routing table. The device may store, after purging the entry, a second routing indicator in the entry to map the second routing indicator to the authentication manager, wherein the second routing indicator is different from the first routing indicator.

Abstract: A device may receive performance requirements for a service, and may receive RAN factors that influence a RAN, core factors that influence a core network, and transport factors that influence a transport network. The device may determine a RAN capability to satisfy the performance requirements, and may determine a core capability to satisfy the performance requirements. The device may determine a transport capability to satisfy the performance requirements, and may determine RAN configuration settings, core configuration settings, and transport configuration settings based on the RAN capability, the core capability, and the transport capability, respectively. The device may generate a RAN SON based on the RAN configuration settings, a core SON based on the core configuration settings, and a transport SON based on the transport configuration settings. The device may create a network slice based service area based on the RAN SON, the core SON, and the transport SON.