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: 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, 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: 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 network device may determine a user equipment route selection policy (URSP) for a first network slice, and may provide the URSP to a user equipment (UE) via non-access stratum (NAS) signaling. The network device may determine an updated URSP for a second network slice that is different than the first network slice, and may determine that the NAS signaling is unavailable for the UE. The network device may provide, based on determining that the NAS signaling is unavailable, the updated URSP to a subscriber identity module (SIM) over-the-air (OTA) system to cause the SIM-OTA system to provide the updated URSP to the UE.

Abstract: A system may comprise one or more devices in a network. The devices may be configured to: receive network slice performance data; and determine whether a network slice to which a User Equipment (UE) device is connected meets one or more criteria based on the network slice performance data. When the network slice does not meet the one or more criteria, the one or more devices may identify a different network slice that meets the one or more criteria; obtain an application identifier (app ID) or a traffic descriptor from a UE Route Selection Policy (URSP) rule whose slice ID matches a slice ID of the different network slice; and send the app ID or the traffic descriptor to the UE device.

Abstract: A system described herein may receive a set of attributes associated with a particular User Equipment (“UE”), such as a location of the UE, Quality of Service (“QoS”) parameters, or UE power class. The system may identify a set of radio access network (“RAN”) configuration parameters based on the received set of attributes associated with the particular UE, wherein the RAN configuration parameters include radio frequency (“RF”) channel configuration parameters such as an orthogonal frequency-division multiplexing (“OFDM”) slot format. The system may provide the identified set of RAN configuration parameters to the RAN, and the RAN may utilize the RF channel configuration parameters included in the identified set of RAN configuration parameters to configure one or more channels between the RAN and the particular UE.

Abstract: A method, a device, and a non-transitory storage medium are described in which an inter-RAT PDN connection management service is provided. The service may include provisioning a packet data network (PDN) session based on network slice (NS) and access point name (APN) information received from an end device via a non-slice radio access device. The service may further include provisioning, during the PDU session, a network slice based on the NS and APN information in which core devices of the network slice are selected and the same as the core devices that supported the PSN session.

Abstract: A device may include a processor configured to provide an interface to enable a user equipment (UE) device to request a data flow in a network slice via a network exposure function (NEF). The processor may be further configured to receive a request from the UE device via the provided interface to create a data flow in the network slice, wherein the data flow is associated with a Quality of Service (QOS) characteristic; map the QoS characteristic to a QoS identifier; and create a data flow associated with the QoS identifier in a communication session associated with the UE device in the network slice.

Abstract: Systems and methods described herein provide a slice management and prioritization service on a per user equipment (UE) device level. A network device in a core network may receive a notification that a UE device has exhausted a quota of available simultaneous data radio bearers (DRBs) and, afterwards, receive an indication that an application on the UE device has requested a new protocol data unit (PDU) session on a requested network slice that is not currently active for the UE device. The network device may identify relative priorities for the requested network slice and active network slices for the UE device; determine, based on the relative priorities, if the new PDU session can preempt a DRB for an active PDU session; and delete the active PDU session when it is determined the new PDU session can preempt a DRB for an active PDU session.

Abstract: Network devices may be configured to execute computer-executable instructions to instantiate a deployable unit based on the instructions. The instructions may include a virtual network function (VNF) template that includes: a virtualized deployment unit (VDU) template that describes the deployable unit that includes containers; and a connection point template bound to the VDU template. The deployable unit may provide services of a network function in an access network or a core network. The deployable unit may include an interface defined by the connection point template.

Abstract: Systems and methods described herein provide an interface for a Network Data Analytics Function (NWDAF) to extract event data from a Location Management Function (LMF) located in a core network or radio access network (RAN). An NWDAF receives, from a network device, an information request for a location-assistance service. The NWDAF sends to the LMF a data request based on the information request, and receives, from the LMF, event data responsive to the data request. The NWDAF generates an analytics report based on the event data.

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 network device may receive, for an emergency call, a session initiation protocol (SIP) invite that includes a registered address of a user device that initiated the emergency call, and may determine whether the user device is associated with a private network based on the SIP invite. The network device may extract the registered address of the user device from the SIP invite and based on the user device being associated with the private network, and may provide the registered address to another network device. The other network device may determine a registered geographic location of the user device, based on the registered address, and may provide the registered geographic location to a public safety answering point associated with the emergency call.

Abstract: A network device may receive, for an emergency call, a session initiation protocol (SIP) invite that includes a registered address of a user device that initiated the emergency call, and may determine whether the user device is associated with a private network based on the SIP invite. The network device may extract the registered address of the user device from the SIP invite and based on the user device being associated with the private network, and may provide the registered address to another network device. The other network device may determine a registered geographic location of the user device, based on the registered address, and may provide the registered geographic location to a public safety answering point associated with the emergency call.

Abstract: A first network device may receive, from an application server, a first request for a dedicated bearer session for an application with a quality of service (QoS) and for a notification of an idle session for the application. The first network device may generate, based on the first request, a second request to be notified regarding expiration of an idle session timer for the application, and may provide the second request to a second network device. The first network device may receive, from the second network device and based on the second request, a notification of expiration of the idle session timer for the application, and may provide, to the application server, the notification of expiration of the idle session timer for the application.

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 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 method may include storing information identifying network slices associated with transmitting data in a network, information identifying a maximum number of user equipment (UE) devices that can be registered for each network slice and/or information identifying a maximum number of data sessions that can be established for each network slice based on locations or areas associated with the UE devices. The method may also include receiving, from a first UE device, a registration request or a request for a data session and identifying a first slice associated with the first UE device. The method may further include determining, based on a location or area associated with the first UE device, whether a maximum number of UE devices that can be registered for the first slice has been reached and/or a maximum number of data sessions that can be served by the first slice has been reached.

Abstract: A method, a network device, and a non-transitory computer-readable storage medium are described in relation to an propagation delay compensation service. The propagation delay compensation service may calculate or select propagation delay compensation method and configuration data based on a time synchronization error budget value, which may be calculated based on quality of service information associated with a network slice, network slice information, and time sensitive communication assistance information. The propagation delay compensation service may calculate or select the propagation delay compensation method and configuration data based on other context information.