Abstract: A device establishes a first encrypted tunnel with a first active security gateway at a first data center to enable the device to communicate, via the first encrypted tunnel, with a first access and mobility management function (AMF) at the first data center. The device forwards, via the first encrypted tunnel and the first active security gateway, a first User Equipment device (UE) message to the first AMF. The device determines an occurrence of a failure or overload condition at the first active security gateway, and establishes, based on the determined occurrence of the failure or overload condition, a second encrypted tunnel with a standby security gateway at a second data center to enable the device to communicate, via the second encrypted tunnel, with the first AMF. The device forwards, via the second encrypted tunnel and the standby security gateway, at least one second UE message to the first AMF.

Abstract: A network device, implementing a network function, receives a network slice request from a user equipment device (UE) that includes a requested network slice set in a network. The network device determines a first set of allowed network slices for the UE based on at least one of first network slices supported by a Radio Access Network (RAN), second network slices supported by the network function, third network slices to which the UE subscribes, or fourth network slices configured by a Network Slice Selection Function (NSSF) in the network. The network device obtains historical behavior data associated with the UE, and determines a second set of allowed network slices for the UE based on the first set and the historical behavior data associated with the UE. The network device returns the second set of allowed network slices to the UE.

Abstract: In the various embodiments, systems and methods are disclosed for determining the location of User Equipment (UE) in a network and for authorizing access to content based on said location. An aspect of the present disclosure is a method including receiving, by a Content Authorization Function (CAF), a request to provide a UE type of a UE and a physical location associated with the UE, the request including a UE Internet Protocol (IP) address associated with the UE; querying, by the CAF, a Network Function (NF), to provide the UE type and associated physical location, the query including the UE IP address; receiving, by the CAF from the NF, the UE type and associated physical location; and transmitting the UE type and associated physical location.

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: Embodiments described herein may provide for the return (e.g., reconnection) of a User Equipment (“UE”) to a first radio access network (“RAN”) to which the UE was connected, after the UE has been redirected to a second RAN based on the occurrence of an event. The event may include a voice call placed by or to the UE. The return of the UE to the first RAN may occur based on the occurrence of another event, such as the voice call being terminated.

Abstract: An improved cellular network architecture enables the distribution of Radio Resource Control (RRC) inactive state to devices in a core network. A mobility manager receives subscription requests from core network devices requesting notification of user equipment (UE) transitions to RRC Inactive states. Upon receiving an RRC transition report for a UE that indicates a transition to an RRC Inactive state, the mobility manager publishes an event including data representing the RRC inactive state and a UE identifier. Subscribing network elements receive this event and can adjust operations accordingly, including temporarily suspending operations until a further RRC state change.

Abstract: Embodiments described herein may provide for the return (e.g., reconnection) of a User Equipment (“UE”) to a first radio access network (“RAN”) to which the UE was connected, after the UE has been redirected to a second RAN based on the occurrence of an event. The event may include a voice call placed by or to the UE. The return of the UE to the first RAN may occur based on the occurrence of another event, such as the voice call being terminated.

Abstract: An improved cellular network architecture enables the distribution of Radio Resource Control (RRC) inactive state to devices in a core network. A mobility manager receives subscription requests from core network devices requesting notification of user equipment (UE) transitions to RRC Inactive states. Upon receiving an RRC transition report for a UE that indicates a transition to an RRC Inactive state, the mobility manager publishes an event including data representing the RRC inactive state and a UE identifier. Subscribing network elements receive this event and can adjust operations accordingly, including temporarily suspending operations until a further RRC state change.

Abstract: A network device may receive historical data identifying historical error data and error data categorizations associated with a first core network and may store the historical data in a data structure. The network device may receive a request associated with a user equipment and may receive error data from the first core network based on the request. The network device may receive network health data identifying load levels and health of the first core network and a second core network. The network device may determine possible cause data identifying causes associated with the error data based on the historical data, the error data, and the network health data. The network device may generate a cause code for the user equipment based on the possible cause data and may provide the cause code to the user equipment.

Abstract: Embodiments described herein may provide for the return (e.g., reconnection) of a User Equipment (“UE”) to a first radio access network (“RAN”) to which the UE was connected, after the UE has been redirected to a second RAN based on the occurrence of an event. The event may include a voice call placed by or to the UE. The return of the UE to the first RAN may occur based on the occurrence of another event, such as the voice call being terminated.

Abstract: Embodiments described herein may provide for the return (e.g., reconnection) of a User Equipment (“UE”) to a first radio access network (“RAN”) to which the UE was connected, after the UE has been redirected to a second RAN based on the occurrence of an event. The event may include a voice call placed by or to the UE. The return of the UE to the first RAN may occur based on the occurrence of another event, such as the voice call being terminated.