Abstract: A device may receive network data for network devices of an IMS network, and may determine that the network devices are active. The device may identify a set of network devices associated with the network data satisfying an upper threshold, and may determine that the network data of the set of network devices indicates healthy redundant network devices and satisfies a lower redundancy threshold. The device may determine that network data of the healthy redundant network devices satisfies an upper redundancy threshold, and may calculate a variance for the network data of the set of network devices. The device may analyze the network data of the set of network devices based on the variance satisfying a variance threshold, and may identify a first increase or a second increase in traffic for a particular network device. The device may perform actions based on identifying the first increase or the second increase.

Abstract: A network device receives a network service request, for network service in a mobile network, from a user equipment device (UE), where the network service request includes a first service identifier (ID) and a subscription concealed ID (SUCI). The network device sends, to a Network Function (NF) in the mobile network, a SUCI deconcealment request that includes the SUCI. The network device receives, from the NF, a deconcealed Subscription Permanent Identifier (SUPI) decrypted from the SUCI. The network device verifies a validity of the first service ID for the deconcealed SUPI, and sends a service authorization response to the UE based on verification of the validity of the service ID from the UE.

Abstract: Systems and methods described herein enable premium session retainability for differentiation of services with respect to network function failures. A first network function of a core network obtains a session retention indicator during establishment of a protocol data unit (PDU) session. The first network function calculates a compute footprint for the first network function to support the PDU session and any other premium sessions currently serviced by the first network function. An orchestration device receives the compute footprint and provisions a second network function based on the compute footprint. The first network function and the second network function perform data replication of state information for the PDU session to allow premium sessions to continue with no or minimal interruption in the event of a failover scenario.

Abstract: A network device executing a Network Exposure Function (NEF) receives, from a requestor, an on-demand Subscription Concealed Identifier (SUCI) deconcealment request associated with a mobile network subscriber. The NEF sends a second SUCI deconcealment request to a network function (NF) in the mobile network, where the second SUCI deconcealment request includes a SUCI associated with the mobile network subscriber. The NEF receives, from the NF, a SUCI deconcealment response that includes a Subscription Permanent Identifier (SUPI), associated with the mobile network subscriber, decrypted from the SUCI by the NF, and forwards the SUCI deconcealment response to the requestor.

Abstract: In some implementations, a network device (e.g., an Internet protocol multimedia subsystem (IMS) application server (IMS-AS) may receive, via a first communication interface, from a call session control function (CSCF) device, a request to register for an Internet protocol multimedia subsystem (IMS) service. The network device may provide via a second communication interface between the network device and a unified data management (UDM) device, and to the UDM device, a request for IMS service information associated with the IMS service. The network device may receive based on providing the request for IMS service information, via the second communication interface, and from the UDM device, IMS service information. The network device may cause, based on the IMS service information, the IMS service to be provided to a user device associated with the request to register for the IMS service.

Abstract: In some implementations, a network device may store first data associated with a monitoring event, wherein the first data is associated with a subscriber and is stored as persistent data in a memory associated with the network device. The network device may receive second data associated with an occurrence of the monitoring event. The network device may determine that the second data indicates a change to the first data. The network device may provide the second data to a network exposure function (NEF) based on the second data indicating the change to the first data, wherein the second data is not provided to the NEF when the second data does not indicate the change to the first data.

Abstract: In some implementations, a network device (e.g., an Internet protocol multimedia subsystem (IMS) application server (IMS-AS) may receive, via a first communication interface, from a call session control function (CSCF) device, a request to register for an Internet protocol multimedia subsystem (IMS) service. The network device may provide via a second communication interface between the network device and a unified data management (UDM) device, and to the UDM device, a request for IMS service information associated with the IMS service. The network device may receive based on providing the request for IMS service information, via the second communication interface, and from the UDM device, IMS service information. The network device may cause, based on the IMS service information, the IMS service to be provided to a user device associated with the request to register for the IMS service.

Abstract: A network device may receive, from a CSCF device, a request for registration data associated with an IMS service, and may provide, to the CSCF device, the registration data associated with the IMS service. The network device may receive, from the CSCF device, a request for location data associated with the IMS service, and may provide, to the CSCF device, the location data associated with the IMS service. The network device may receive, from the CSCF device, a request for authentication data associated with the IMS service, and may provide, to the CSCF device, the authentication data associated with the IMS service. The network device may receive, from the CSCF device, a request for subscriber profile data associated with the IMS service, and may provide, to the CSCF device, the subscriber profile data associated with the IMS service.

Abstract: A method, a device, and a non-transitory storage medium are described in which a monitoring event handling service is provided. The service may include a non-stand-alone core device subscribing to a registration status for an end device with a stand-alone core device. The service may also include the non-stand-alone core device subscribing to a monitoring event service with the stand-alone core device on behalf of another non-stand-alone core network device. The stand-alone core device may monitor an event when the end device is stand-alone registered and may notify the non-stand-alone core device when the event occurs. The service may include the non-stand-alone core device notifying the other non-stand-alone core device when the event occurs.

Abstract: Disclosed are systems and methods for an advanced authorization framework that provides advanced network security and control of network hosted data. The disclosed framework provides computerized mechanisms that dictate a control of which data is accessible by particular network components, and which operations the privileged components are enabled to be performed. The disclosed framework can allow Network Function (NF) service consumers to discover and request network data that is specific to the operational status (e.g., PCF can request policy data). The disclosed framework provides an access scope of the NF service consumer that manages which hosted data is accessible, and to what degree it can be manipulated, if at all.

Abstract: In some implementations, a device may receive a session initiation protocol (SIP) message. The device may determine that the SIP message does not include a parameter indicating that a first portion of the SIP message is to be processed as a telephone number. The device may perform one or more actions including one or more of: determining whether a second portion of the SIP message includes information identifying a service; determining whether the first portion of the SIP message includes a code; determining whether the first portion of the SIP message is formatted according to a format associated with a telephone number; or determining whether the first portion of the SIP message includes characters that are different than hexadecimal characters. The device may selectively cause the SIP message to be routed using the first portion of the SIP message or routed using the second portion of the SIP message.

Abstract: A network device may receive, from a CSCF device, a request for registration data associated with an IMS service, and may provide, to the CSCF device, the registration data associated with the IMS service. The network device may receive, from the CSCF device, a request for location data associated with the IMS service, and may provide, to the CSCF device, the location data associated with the IMS service. The network device may receive, from the CSCF device, a request for authentication data associated with the IMS service, and may provide, to the CSCF device, the authentication data associated with the IMS service. The network device may receive, from the CSCF device, a request for subscriber profile data associated with the IMS service, and may provide, to the CSCF device, the subscriber profile data associated with the IMS service.

Abstract: A system includes a Network Repository Function in a segment of a Fifth Generation (5G) network. The NRF is configured to receive a registration request from a Unified Data Repository (UDR). The request indicates that the UDR includes both UE-specific data and non-UE specific data. The NRF is further configured to: store registration information provided in the registration request; receive a request from a network function within the segment and send a response to the request based on the registration information.

Abstract: Systems and methods described herein enable distribution of a Charging Function group identifier (“CHF-Group-ID”) and other CHF selection data to CHF consumers during Protocol Data Unit (PDU) session establishment in a 5G network. A Unified Data Repository (UDR) is provisioned with CHF-Group-ID details for each subscriber of the network. In one aspect, during PDU session establishment, CHF consumers obtain CHF-Group-ID information as part of a subscriber profile that is provided to all CHF consumers. No additional step or hop is needed for the CHF consumers to obtain the CHF-Group-ID. Thus, regionally segmented CHFs can be implemented without replication of data between CHFs in different regional segments and without additional signaling between network functions.

Abstract: In some implementations, a device may receive a session initiation protocol (SIP) message. The device may determine that the SIP message does not include a parameter indicating that a first portion of the SIP message is to be processed as a telephone number. The device may perform one or more actions including one or more of: determining whether a second portion of the SIP message includes information identifying a service; determining whether the first portion of the SIP message includes a code; determining whether the first portion of the SIP message is formatted according to a format associated with a telephone number; or determining whether the first portion of the SIP message includes characters that are different than hexadecimal characters. The device may selectively cause the SIP message to be routed using the first portion of the SIP message or routed using the second portion of the SIP message.