Abstract: A method may include receiving, by at least one network device and from a user device, a registration message including a service identifier and at least one of a network slice identifier or a network slice token. The method may also include determining, based on information included in the registration message, whether the user device is authorized to use a network slice associated with the service identifier. The method may further include setting up a data session to be serviced by the network slice, in response to determining that the user device is authorized to use the network slice.

Abstract: A base station determines a latency requirement of a user equipment device (UE), and receives latency measurements associated with multiple neighboring cells or cell sectors having coverage areas within a certain proximity to the base station. The base station measures a latency associated with a first cell or cell sector, having a coverage area generated by the base station, that is currently serving the UE. The base station triggers a mobility event for the UE, based on the UE's latency requirement, the measured latency of the first cell or cell sector, and the latency measurements associated with the multiple neighboring cells or cell sectors, to a selected one of the multiple neighboring cells or cell sectors.

Abstract: A method may include providing a network data analytics function (NWDAF) in a network and providing, a non-third generation partnership project (3GPP) interworking function (N3IWF) in the network. The method may also include subscribing, by the N3IWF, to the NWDAF, and obtaining, by the NWDAF and from the N3IWF, data associated with processing performed by the N3IWF.

Abstract: A network device may maintain a list of existing slice identifiers, associated with slices of a core network, that are in use in active UE sessions, and may receive a slice identifier associated with a slice of the core network and provided in a request to establish a session between a UE and the slice of the core network. The network device may determine whether the slice identifier matches an existing slice identifier included in the list, and may create a new network address, with an address of the network device and the slice identifier, based on the slice identifier failing to match an existing slice identifier included in the list. The network device may utilize the new network address to establish the session between the UE and the slice of the core network.

Abstract: A system described herein may maintain and distribute precision time across diverse locations and network types, including wired and wireless networks. A particular device may receive topology information indicating a particular set of time synchronization nodes, out of a plurality of time synchronization nodes of a time synchronize network; communicate with the particular set of time synchronization nodes on an ongoing basis, wherein the device and the plurality of devices maintain precision time information based on the ongoing communication; receive a request for precision time information from a particular time synchronization client, wherein the particular time synchronization client is assigned to the device based on attributes of the time synchronization client and the device; and output, to the particular time synchronization client and in response to the request, the requested precision time information.

Abstract: A computer device may include a memory storing instructions and processor configured to execute the instructions to host a network function container that implements a microservice for a network function in a wireless communications network, wherein the network function container is deployed by a container orchestration platform; host a service proxy container associated with the network function container, wherein the service proxy container is deployed by the container orchestration platform; and configure the hosted service proxy container to apply a wireless network policy to the microservice for the network function. The processor may be further configured to intercept messages associated with the microservice for the network function using the configured service proxy container; and apply the wireless network policy to the intercepted messages using the configured service proxy container.

Abstract: Embodiments described herein allow reduced latency and computational costs by identifying a slice associated with a packet and determining an action to be performed with respect to the packet without having to perform deep packet inspection on the packet. An aspect of the present disclosure is a method comprising receiving a packet including a slice identifier corresponding to a slice of a network, the slice identifier having a plurality of bits; determining a bit value for each bit in a subset of the plurality of bits; and performing an action with respect to the packet based on the bit value of at least one bit in the subset.

Abstract: In some implementations, a network device may obtain a message that includes service parameter data associated with an application. The service parameter data may indicate a revalidation time. The network device may generate, based on the service parameter data, a user equipment route selection policy (URSP) rule associated with the application that includes the revalidation time indicated by the service parameter data. The URSP rule may expire at the revalidation time. The network device may transmit the URSP rule for a user equipment (UE) that executes the application. The network device may receive a state indication message associated with the UE that is triggered at the revalidation time.

Abstract: A system described herein may provide a technique for a policy and/or rules element of a core network, such as a Policy Control Function (“PCF”), to identify a first network slice with which a communication session between a User Equipment (“UE”) and a core network, such as a protocol data unit (“PDU”) session, is associated. The policy and/or rules element may identify a second network slice with which the communication session should be associated, such as based on traffic monitoring, network congestion monitoring, or other criteria, and may output an indication, indicating a second network slice, to a session control element, such as an Session Management Function (“SMF”). The session control element may cause the communication session to be moved from the first network slice to the second network slice based on receiving the indication.

Abstract: A first User Equipment (“UE”) may communicate with a second UE via a communication link to determine an operational status of the second UE. The second UE may be connected to a network via one or more communication sessions. The first UE may determine, based on the communication link, that the second UE is non-operational, and may output, based on determining that the second UE is non-operational, a request to communicate with the network via the one or more communication sessions associated with the second UE. The network may modify the one or more communication sessions to be associated with the first UE based on the request, and the first UE may communicate with the network via the one or more modified communication sessions.

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: Systems and methods described herein provide dynamic network slicing. A network device receives, from an application server, application performance requirements for an application and receives capability and performance information of an existing network slice that is servicing a User Equipment (UE) device using the application. The network device determines, based on the capability and performance information, that a new network slice is needed to support the application performance requirements for the UE device; and sends a signal to initiate a slice creation process for the new network slice.

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 an entity to support a network slice and/or access to an application service for end devices. 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.

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: Systems and methods are provided to enable mobile network operators to dynamically determine when a Low-Latency, Low-Loss Scalable-Throughput (L4S) service shall be enabled for a data flow. A network device in a core network receives a request for a Quality of Service (QoS) flow associated with a user equipment (UE) device; determines whether to enable a LS4 service for the QoS flow; and notifies, based on the determining, a Session Management Function (SMF) to create the QoS flow with L4S service enabled.

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: In some implementations, an access and mobility management function (AMF) may receive subscribed network slice selection assistance information (NSSAI) that indicates location information associated with a slice and time information associated with the slice. The AMF may determine an allowed NSSAI based on one or more of the location information, the time information, a static policy, or a dynamic policy. A access and mobility policy control function (AM-PCF) may create the dynamic policy to determine a location and a time at which the subscribed NSSAI may be used. The AMF may transmit, to a user equipment (UE), an indication of the allowed NSSAI.

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: A method, a network device, and a non-transitory computer-readable storage medium are described in relation to an LAS service. The LAS service may include enablement or disablement of the LA service subsequent to an establishment and active traffic flow associated with an application session. The LAS service may be enabled or disabled based on performance metric criteria and threshold values not being satisfied or being satisfied. The LAS service may be implemented to include an exposure function.

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.