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 method, a system, and a non-transitory storage medium provide for encoding a general packet radio service (GPRS)-tunnel endpoint identifier (GTP-TEID) with data identifying radio frequency (RF) bandwidths supported in a local radio environment (LRE) from which a user equipment (UE) device accesses the wireless access station; sending, via a signaling channel, the GTP-TEID to a core network device; notifying one or more core network devices of an RF bandwidth category level corresponding to the RF bandwidths; and applying at least one of a policy rule or a charging rule to a packet data unit (PDU) session for the UE device, based on the RF bandwidth category level.

Abstract: Systems and methods described herein include receiving an indication that an application on a user device has been launched; determining subscription information associated with the user device or a provider of the application, wherein the subscription information includes an indication of one or more recommended network slices to use for traffic associated with the application; and initiating a data session with the user device for sending and receiving the traffic associated with the application via a recommended network slice of the one or more recommended network slices.

Abstract: Devices, methods, and computer-readable media described herein and provide for sending, by a first wireless station, a suspend message to a second wireless station associated with a radio resource control (RRC) session for a dual connectivity (DC) capable user equipment (UE) device that places the DC capable UE device in an RRC inactive mode; storing, by the first wireless station, UE context information from a core network for the DC capable UE device for the RRC session; and evaluating, by the first wireless station, a set of criteria to determine whether to also store the UE context information at the second wireless station.

Abstract: A method for controlling bearers in a core network includes receiving, from a user equipment (UE) device, a request for access to network resources, where the core network is coupled with a primary radio access technology (RAT) and a secondary RAT. The method includes determining an access point name (APN) RAT access restriction in response to the received request, where the APN RAT access restriction associates an APN with a corresponding RAT, where the corresponding RAT comprises at least one of the primary RAT or the secondary RAT. The method also includes assigning a radio bearer based on the determined APN RAT access restriction, wherein the assigned radio bearer exchanges data via the corresponding RAT; and identifying, to a master node, the assigned radio bearer for exchanging data between the UE device and a device specified by the APN via the corresponding RAT.

Abstract: A system described herein may provide a technique for the differentiated Quality of Service (“QoS”) treatment of different traffic types associated with the same application (e.g., a “multi-persona” application) by a wireless network, without the exposure of an application identifier of the application to the wireless network. The application may provide a traffic type indication, based on which a User Equipment (“UE”) may establish one or more QoS flows or other types of communication sessions with the wireless network, where the QoS flows or other types of communication sessions are associated with a network slice that is associated with the traffic type. The communication sessions may include Data Radio Bearers (“DRBs”), backhaul links, protocol data unit (“PDU”) sessions, or other suitable types of communication sessions.

Abstract: A device includes a memory that stores a User Equipment Route Selection Policy (URSP) that includes a rule. The rule includes enhanced route selection descriptors (RSDs). Each of the enhanced RSDs may include special RSD parameter, such as a Technology selector. The device is configured to receive a request from a component, in the device, to establish a session with a network. The request includes request parameters. The devices processes each of the RSDs.

Abstract: In some implementations, a network device may receive an identifier associated with an application server. The network device may associate the identifier with a service profile associated with a network slice based on a quality of service associated with the network slice. The network device may provide, to a device associated with the application server, information indicating that the identifier is associated with the service profile. The network device may receive address information associated with the application server. The network device may associate the address information with the service profile. The network device may provide service profile information to a security device included in a core network to cause the security device to forward traffic transmitted by the application server toward a destination via the network slice. The service profile information may include an identifier associated with the service profile, the identifier, and the address information.

Abstract: A system described herein may provide a technique for the proactive failover of groups of Virtualized Network Functions (“VNFs”) based on monitoring Key Performance Indicators (“KPIs”) associated with the VNFs. KPIs associated with a particular VNF or a set of VNFs may be monitored, and a failover event indicating service degradation or imminent service degradation may be detected based on the KPIs associated with the particular VNF or set of VNFs. Additional VNFs, associated with the particular VNF or set of VNFs, may be further identified for failover from a first data center to a second data center. The additional VNFs may be identified for failover without necessarily monitoring KPIs associated with the additional VNFs, and/or based on factors in addition to KPIs associated with the additional VNFs. For example, the additional VNFs may be failed over based on the KPIs associated with the particular VNF or set of VNFs.

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 method, a device, and a non-transitory storage medium are described in which a dual connectivity path selection service is provided. The service may select a network path for dual connectivity. The service may use mapping information that may correlate network parameters and values to dual connectivity configurations. The service may compare parameters included in a configuration request pertaining to end devices with the mapping information for selection of a dual connectivity configuration.

Abstract: Systems and methods leverage trust anchors to generate tokens which can then be used by network functions (NFs). A virtualization infrastructure manager (VIM) for a virtualized platform receives a NF software package and a certificate request token (CRT) from a management function. The NF is a virtual NF, a containerized NF, or another virtual entity (xNF) to be deployed. The CRT is digitally signed by the management function and includes a network address of a trust anchor platform and a NF profile. The VIM deploys the NF and provides the CRT to the NF. The NF obtains from the CRT the network address of the trust anchor platform, generates a certificate signing request (CSR) for a digital certificate, and submits the CSR and the CRT to the trust anchor platform. The NF receives a digital certificate from the trust anchor platform based on validation of both the CSR and CRT.

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 method, a device, and a non-transitory storage medium are described in which an access control with differentiated service is provided. The service may provide access barring information that includes an access class and a group identifier. The access class and group identifier may constitute an access category identifier that identifies an access category under a unified access control (UAC). The access class and group identifier may correlate to a type of access attempt and/or condition related to the end device. The access class and group identifier may pertain to end device access via a non-standalone deployment.

Abstract: Systems and methods enable secure service-based communications in networks that use a Services Communications Proxy (SCP). A Network Function (NF) producer receives a service request including an authorization token and a signed service request object, wherein the service request originates from an NF consumer of the wireless core network and is forwarded to the NF producer via the SCP. The NF producer verifies the signed service request object and generates, after the verifying, a service response. The service response includes a signed service response object. The NF producer sends, to the NF consumer and via the SCP, the service response with the signed service response object.

Abstract: In some implementations, a network device may receive an identifier associated with an application server. The network device may associate the identifier with a service profile associated with a network slice based on a quality of service associated with the network slice. The network device may provide, to a device associated with the application server, information indicating that the identifier is associated with the service profile. The network device may receive address information associated with the application server. The network device may associate the address information with the service profile. The network device may provide service profile information to a security device included in a core network to cause the security device to forward traffic transmitted by the application server toward a destination via the network slice. The service profile information may include an identifier associated with the service profile, the identifier, and the address information.

Abstract: A device includes a memory that stores a User Equipment Route Selection Policy (URSP) that includes a rule. The rule includes enhanced route selection descriptors (RSDs). Each of the enhanced RSDs may include special RSD parameter, such as a Technology selector. The device is configured to receive a request from a component, in the device, to establish a session with a network. The request includes request parameters. The devices processes each of the RSDs.

Abstract: A network device may select a first user plane function for establishing, with a user equipment, a protocol data unit session with a single flow and may receive an application function trigger associated with a first new flow for a first application of the user equipment. The network device may select a second user plane function for the first new flow and may create a first traffic filter for the first new flow. The network device may cause the first traffic filter to be provided to the user equipment so that first application traffic is routed, based on the first traffic filter, to the second user plane function and a first multi-access edge computing device associated with the second user plane function.

Abstract: A device may receive, from a network device, a user equipment (UE) parameter update request notification indicating an update to a UE parameter of a universal subscriber identity module (USIM), and may generate an encrypted UE parameter update request. The device may cause the encrypted UE parameter update request to be provided to the USIM to cause the USIM to update the UE parameter and to generate an encrypted UE parameter update response. The device may receive, from the network device, the encrypted UE parameter update response, and may verify an authenticity of content of the encrypted UE parameter update response based on whether the encrypted UE parameter update response is signed by the USIM. The device may provide, to the network device, a result indicating whether the UE parameter is updated and whether the authenticity of the content of the encrypted UE parameter update response is verified.

Abstract: A method, a device, and a non-transitory storage medium are described in which a registration area-based application exposure and network slice selection service is provided. The service may include the generation of multiple sets of allowed network slices based on a type of end device, current tracking area, and registration area information. The service may also include selecting one of the sets of allowed network slices based on a mobility pattern of the end device. The service may also translate allowed network slices, current tracking area and registration area information, and expose the translated information to an application function.