Abstract: A device can receive, at a radio access network (RAN) and from a user device, first information to initiate a communications session that has one or more properties. The device can send second information to an access and mobility management function component (AMF) to authenticate the user device. The device can send third information to a user plane function component (UPF) to determine a set of network slice policies for managing the communications session. The device can receive the set of network slice policies and apply the set of network slice policies to the communications session. The device can detect a change in the one or more properties of the communications session and send a signal to the UPF to analyze the communications session. The device can receive a new set of network slice policies and apply the new set of network slice policies to the communications session.

Abstract: A method, a device, and a non-transitory storage medium are described in which a network slice deployment service is described. The network slice deployment service includes storing network resource and capability information that indicates available network resources in a network. Network level requirement information pertaining to a request for network service from a user is generated. The network level requirement information is used to select available network resources based on the network resource capability information. The network slice deployment service calculates network resource utilization associated with available network resources so that optimal usage of network resources can be selected and end-to-end network slice deployment layout information can be generated and used to provision a network slice deployment layout that supports the request for network service.

Abstract: A radio access network (RAN) node can receive, from a user equipment (UE), a request to establish a session associated with a low-latency service level agreement (SLA). The session can be mapped to a radio bearer associated with a network slice configured to support the low-latency SLA, wherein the network slice can include a RAN portion and a core network portion that are co-located at a RAN edge to support the low-latency SLA. The RAN node can provide information related to the radio bearer to a distributed unit (DU) associated with the RAN portion of the network slice and route traffic associated with the session through the network slice configured to support the low-latency SLA via the radio bearer mapped to the session. As such, the session can have a context maintained in the RAN portion and the core network portion of the network slice.

Abstract: A system may determine an identifier associated with a location of a user device in response to receiving an indication that the user device has moved to the location and perform a first lookup to determine an application specific location associated with the identifier. A second lookup may be performed to determine one or more network functions available in the application specific location. An indication of the one or more network functions may be outputted.

Abstract: A device of a RAN may receive first traffic associated with a first network type service, second traffic associated with a second network type service, and core network data associated with a core network that provides the first network type service and the second network type service. The device may calculate a per QCI split based on the core network data, and may calculate an initial resource split based on the per QCI split. The device may provide, to a first device, data identifying the initial resource split, and may receive a traffic bias per QCI based on providing the data identifying the initial resource split. The device may calculate a final resource split for the first traffic and the second traffic based on the traffic bias per QCI, and may cause the final resource split to be implemented via resources associated with the RAN.

Abstract: A slice order system may receive a request to generate a network slice configuration for providing a service via a network. The slice offer system may determine a description template associated with a network slice type. The slice offer system may determine, based on the description template and a set of deployment parameters, a description profile for the network slice configuration. The slice offer system may generate, based on the description profile and a location, a slice deployment description for the network slice configuration according to location-specific characteristics associated with resources at the location and a service level agreement associated with the request. The slice offer system may deploy the slice deployment description to permit a network slice instance to be created according to the slice deployment description.

Abstract: A RAN node may determine an aggregate signal-to-noise ratio (SNR) of each resource block of a plurality of resource blocks, where the aggregate SNR of a given resource block of the plurality of resource blocks is based on SNRs of subcarrier frequencies of the given resource block. The RAN node may determine, based on a type of network traffic on each network slice of a plurality of network slices, an index value of each network slice of the plurality of network slices. The RAN node may map, based on the aggregate SNR of each resource block, based on the index value of each network slice, and for each resource block of the plurality of resource blocks, a resource block of the plurality of resource blocks to a network slice of the plurality of network slices.

Abstract: A device can receive, at a radio access network (RAN) and from a user device, first information to initiate a communications session that has one or more properties. The device can send second information to an access and mobility management function component (AMF) to authenticate the user device. The device can send third information to a user plane function component (UPF) to determine a set of network slice policies for managing the communications session. The device can receive the set of network slice policies and apply the set of network slice policies to the communications session. The device can detect a change in the one or more properties of the communications session and send a signal to the UPF to analyze the communications session. The device can receive a new set of network slice policies and apply the new set of network slice policies to the communications session.

Abstract: A method, a device, and a non-transitory storage medium are described in which a radio and core integrated layers service is provided. The service provides a direct mapping of a quality of service flow between a packet data unit layer and a service data adaptation layer associated with a user plane function and a central unit-user plane function without an intermediary mapping of a tunneling protocol in the user plane.

Abstract: Systems and methods described herein provide an intelligent MEC resource scheduling service. A network device in a MEC network stores, in a memory, threshold values indicating overload conditions for resource usage by a first MEC cluster; monitors resource usage in the first MEC cluster; determines, based on the monitoring, when one of the threshold values is reached; identifies available resources in a second MEC cluster; and re-directs, based on the identifying, at least some of the resource usage from the first MEC cluster to the second MEC cluster.

Abstract: A method, a device, and a non-transitory storage medium are described in which a radio access network slice and core network slice service is provided based on RAN-CN network slice pairing information. A radio access network slice and/or a core network slice uses the RAN-CN network slice pairing information to select network resources to support sessions of end devices. The RAN-CN network slice pairing information may include location information, radio access network slice information, core network slice information correlated to different types or applications or services available to end devices. The RAN-CN network slice pairing information may include information indicating current and available radio access network resources pertaining to the radio access network slices and threshold resources that may be used to support the different types of applications or services.

Abstract: A device of a RAN may receive first traffic associated with a first network type service, second traffic associated with a second network type service, and core network data associated with a core network that provides the first network type service and the second network type service. The device may calculate a per QCI split based on the core network data, and may calculate an initial resource split based on the per QCI split. The device may provide, to a first device, data identifying the initial resource split, and may receive a traffic bias per QCI based on providing the data identifying the initial resource split. The device may calculate a final resource split for the first traffic and the second traffic based on the traffic bias per QCI, and may cause the final resource split to be implemented via resources associated with the RAN.

Abstract: A slice order system may receive a request to generate a network slice configuration for providing a service via a network. The slice offer system may determine a description template associated with a network slice type. The slice offer system may determine, based on the description template and a set of deployment parameters, a description profile for the network slice configuration. The slice offer system may generate, based on the description profile and a location, a slice deployment description for the network slice configuration according to location-specific characteristics associated with resources at the location and a service level agreement associated with the request. The slice offer system may deploy the slice deployment description to permit a network slice instance to be created according to the slice deployment description.

Abstract: Systems and methods described herein provide an intelligent MEC resource scheduling service. A network device in a MEC network stores, in a memory, threshold values indicating overload conditions for resource usage by a first MEC cluster; monitors resource usage in the first MEC cluster; determines, based on the monitoring, when one of the threshold values is reached; identifies available resources in a second MEC cluster; and re-directs, based on the identifying, at least some of the resource usage from the first MEC cluster to the second MEC cluster.

Abstract: A method, a device, and a non-transitory storage medium are described in which a radio and core integrated layers service is provided. The service provides a direct mapping of a quality of service flow between a packet data unit layer and a service data adaptation layer associated with a user plane function and a central unit-user plane function without an intermediary mapping of a tunneling protocol in the user plane.

Abstract: A device can receive, using an application policy handler (APH) component included in the device, a request for a data session for an application associated with the device. The device can identify, using the APH component included in the device, a user equipment route selection policy (URSP) rule, associated with the application, included in a URSP. The device can identify, using the APH component, a network slice specified by the URSP rule associated with the application and a data network specified by the URSP rule associated with the application. The device can attempt, using a modem component included in the device, to establish the data session using the network slice specified by the URSP rule associated with the application and the data network specified by the URSP rule associated with the application.

Abstract: A device can receive, from first user equipment, information that relates to a first application, where the information includes a plurality of S-NSSAI. The device can determine whether the plurality of S-NSSAI are configured as a group of associated S-NSSAI. The device can determine that a preference is to be given to one of: communication sessions associated with the first application relative to a communication session associated with a second application, that does not utilize multiple network slices, of the first user equipment or second user equipment; traffic flows associated with the first application relative to a traffic flow associated with the second application; or a plurality of network slices associated with the first application relative to a network slice associated with the second application. The device can perform one or more actions based on determining the preference to thereby facilitate a particular functionality of the first application.

Abstract: A device of a RAN may receive first traffic associated with a first network type service, second traffic associated with a second network type service, and core network data associated with a core network that provides the first network type service and the second network type service. The device may calculate a per QCI split based on the core network data, and may calculate an initial resource split based on the per QCI split. The device may provide, to a first device, data identifying the initial resource split, and may receive a traffic bias per QCI based on providing the data identifying the initial resource split. The device may calculate a final resource split for the first traffic and the second traffic based on the traffic bias per QCI, and may cause the final resource split to be implemented via resources associated with the RAN.

Abstract: An example method can include receiving, by a device, single-network slice selection assistance information (S-NSSAI) associated with a user equipment. The S-NSSAI can be associated with a network. The method can include determining location information associated with the user equipment, determining that a network slice instance (NSI) is to be created for the S-NSSAI, and creating an NSI based on a network service (NS) associated with the user equipment. The NSI can be created using a network function virtualization orchestrator (NFVO), associated with the network, that allocates resources, of the network, for the NSI according to the NS.

Abstract: A RAN node may determine an aggregate signal-to-noise ratio (SNR) of each resource block of a plurality of resource blocks, where the aggregate SNR of a given resource block of the plurality of resource blocks is based on SNRs of subcarrier frequencies of the given resource block. The RAN node may determine, based on a type of network traffic on each network slice of a plurality of network slices, an index value of each network slice of the plurality of network slices. The RAN node may map, based on the aggregate SNR of each resource block, based on the index value of each network slice, and for each resource block of the plurality of resource blocks, a resource block of the plurality of resource blocks to a network slice of the plurality of network slices.