Abstract: A device may receive, from a mobile device and via a first radio access network, a request for a service. The device may receive a mobile device identifier that identifies the mobile device on a second radio access network. The second radio access network may be a different type of radio access network than the first radio access network. The device may provide the mobile device identifier to an equipment identity register. The device may receive, from the equipment identity register, an authentication indicator that indicates whether to permit or deny access to the service by the mobile device and via the first radio access network. The device may selectively permit or deny the mobile device access to the service, via the first radio access network, based on the authentication indicator.

Abstract: A system may be configured to receive traffic that is destined for a user device, determine a type of content associated with the traffic, determine, based on the type of content, a base station paging scheme, and locate the user device by using the base station paging scheme. In some implementations, a system may include a traffic content analyzer device to analyze header information of a data packet to identify a type of content of the data packet, and output a message that is based on the identified type of content; and a mobile management entity device to receive the message from the traffic content analyzer device, and locate an intended recipient of the data packet by paging one or more base stations using a paging scheme that is based on information in the message.

Abstract: Systems and methods for server reset procedures are disclosed. Some implementations include determining, at a server, that the server is to be reset while currently being in connection to one or more peers, wherein the one or more peers store session information associated with the connection to the server, upon the determination and post reset, sending a notification from the server to the one or more peers connected to the server, and when the server reconnects with the one or more peers after the reset, automatically receiving the stored session information from the one or more peers.

Abstract: Bandwidth for a radio access network may be efficiently allocated for certain voice over LTE (VoLTE) services. In one implementation, a request associated with traffic flows may be received. Each of the traffic flows may be associated with an amount of guaranteed bit rate (GBR) traffic. The method may further include selectively summing the GBR traffic, to obtain an aggregate bandwidth value. The method may further include reserving an amount of GBR bandwidth corresponding to the previous version of the aggregate bandwidth value when a comparison indicates that the aggregate bandwidth value is less than the previous version of the aggregate bandwidth value; and reservation an amount of GBR bandwidth corresponding to the aggregate bandwidth value when a comparison indicates that the aggregate bandwidth value is not less than the previous version of the aggregate bandwidth value.

Abstract: A first device associated with an evolved packet core network receives a first update request from a second device associated with the evolved packet core network. The first update request is associated with a communication session previously provided between the first device and the second device, and the first update request is generated based on a voice/video request. The first device generates an update answer in response to the first update request, where the update answer includes a code requesting that the communication session be restored between the first device and the second device. The first device receives, based on the code, a second update request from the second device, where the second update request includes session information associated with the communication session. The first device restores, based on the session information, the communication session between the first device and the second device to create a restored communication session.

Abstract: A device may receive, from an access network, a mobile device identifier. The mobile device identifier may identify a mobile device that is connected to the access network. The device may receive or determine subscriber information associated with the mobile device identifier. The subscriber information may identify one or more users associated with the mobile device. The device may provide the mobile device identifier and the subscriber information for determination of an action indicator. The action indicator may indicate an action to perform with respect to the mobile device identifier. The device may receive the action indicator based on providing the mobile device identifier and the subscriber information. The device may provide the action indicator for routing toward the mobile device for performance of the action.

Abstract: Systems and methods for server reset procedures are disclosed. Some implementations include determining, at a server, that the server is to be reset while currently being in connection to one or more peers, wherein the one or more peers store session information associated with the connection to the server, upon the determination and post reset, sending a notification from the server to the one or more peers connected to the server, and when the server reconnects with the one or more peers after the reset, automatically receiving the stored session information from the one or more peers.

Abstract: A device receives, from a user equipment (UE), a first request to access a first packet data network (PDN), and receives authentication information from the UE. The device also grants, based on the first request, the UE access to the first PDN when the authentication information authenticates the UE. The device further receives, from the UE, a second request to access a second PDN, and determines whether a re-authentication timer associated with the second PDN has expired before granting the UE access to the second PDN.

Abstract: A first device associated with an evolved packet core network receives a first update request from a second device associated with the evolved packet core network. The first update request is associated with a communication session previously provided between the first device and the second device, and the first update request is generated based on a voice/video request. The first device generates an update answer in response to the first update request, where the update answer includes a code requesting that the communication session be restored between the first device and the second device. The first device receives, based on the code, a second update request from the second device, where the second update request includes session information associated with the communication session. The first device restores, based on the session information, the communication session between the first device and the second device to create a restored communication session.

Abstract: A system may include a first network device, configured to establish first and second channels with a user device, the first and second channels being channels of a network layer of an Open Systems Interconnect (“OSI”) model, receive traffic associated with the user device, and output the traffic via one of the first channel or the second channel. The system may also include a second network device, configured to receive the traffic outputted by the first network device, identify via which channel, of the first and second channels, the traffic was outputted, determine a paging scheme associated with the identified channel, generate a downlink data notification (“DDN”) request, the DDN request indicating the determined paging scheme, and output the DDN request to a third network device, wherein the third network device performs paging, based on the determined paging scheme, to locate the user device.

Abstract: A device receives roaming information associated with a user equipment (UE), a current eNodeB conducting a current Internet protocol (IP) session with the UE, and a plurality of eNodeBs that are neighboring the current eNodeB. The device also selects, based on the roaming information and from the plurality of eNodeBs, an optimal eNodeB to which to handover the UE, and establishes a preemptive IP session with the optimal eNodeB. The device further initiates a handover of the current IP session and the UE from the current eNodeB to the optimal eNodeB, where the current eNodeB acts as an anchoring point for a bearer path associated with the UE during the handover.

Abstract: A device may receive connection information associated with a connection, between a user device and a network, used to provide an application service to the user device. The connection information may include information identifying a network type of the network. The connection information may include information identifying an access point name associated with the connection. The application service may be provided by a device associated with providing the application service to the user device. The device may store the connection information based on receiving the connection information. The device may determine that the connection information is to be provided to the device associated with providing the application service to the user device, and may provide the connection information to the device associated with the application service. The connection information may permit the application service to be provided based on the network type of the network.

Abstract: A first node device, associated with an evolved packet core network, receives an error code from a second node device associated with the evolved packet core network, where the error code is destined for a user equipment. The first node device compares the error code to information included in a data structure that maps multiple error codes to multiple translated error codes understood by the user equipment, and translates the error code into a translated error code based on the comparing of the error code to the information included in the data structure. The translated error code is in a format that is understood by the user equipment. The first node device provides the translated error code to the user equipment or to a third node device associated with the evolved packet core network.

Abstract: A method that includes establishing a connection with a default access point, transmitting a request to access or utilize an application, a service, or a resource, receiving a response to the request that includes a location of a serving access point that provides the application, the service, or the resource, establishing a connection with the serving access point, and receiving an assignment of a network address that is anchored by the serving access point.

Abstract: A first device, provided in an evolved packet core (EPC) network, receives load information associated with a second device provided in the EPC network. The load information includes a load threshold associated with the second device. The first device also receives traffic to be provided to the second device, and determines whether providing the traffic to the second device will cause the second device to exceed the load threshold. The first device provides the traffic to the second device when providing the traffic to the second device will not cause the second device to exceed the load threshold. The first device reduces a quantity associated with the traffic, to create throttled traffic, and provides the throttled traffic to the second device, when providing the traffic to the second device will cause the second device to exceed the load threshold.

Abstract: A method including receiving a session request associated with a user equipment (UE); selecting one or more network address pool name lists based on a type of service to be provided to the UE; selecting one or more network address pool names from the one or more network address pool name lists based on a priority associated with the one or more network address pool names; selecting one or more network addresses from the one or more network address pool names; assigning the one or more network addresses to the UE; and establishing a session with the UE.

Abstract: A system may include a first network device, configured to establish first and second channels with a user device, the first and second channels being channels of a network layer of an Open Systems Interconnect (“OSI”) model, receive traffic associated with the user device, and output the traffic via one of the first channel or the second channel. The system may also include a second network device, configured to receive the traffic outputted by the first network device, identify via which channel, of the first and second channels, the traffic was outputted, determine a paging scheme associated with the identified channel, generate a downlink data notification (“DDN”) request, the DDN request indicating the determined paging scheme, and output the DDN request to a third network device, wherein the third network device performs paging, based on the determined paging scheme, to locate the user device.

Abstract: A first device associated with an evolved packet core network receives a first update request from a second device associated with the evolved packet core network. The first update request is associated with a communication session previously provided between the first device and the second device, and the first update request is generated based on a voice/video request. The first device generates an update answer in response to the first update request, where the update answer includes a code requesting that the communication session be restored between the first device and the second device. The first device receives, based on the code, a second update request from the second device, where the second update request includes session information associated with the communication session. The first device restores, based on the session information, the communication session between the first device and the second device to create a restored communication session.

Abstract: A device may receive connection information associated with a connection, between a user device and a network, used to provide an application service to the user device. The connection information may include information identifying a network type of the network. The connection information may include information identifying an access point name associated with the connection. The application service may be provided by a device associated with providing the application service to the user device. The device may store the connection information based on receiving the connection information. The device may determine that the connection information is to be provided to the device associated with providing the application service to the user device, and may provide the connection information to the device associated with the application service.

Abstract: A first mobility management entity (MME) device receives an attachment request that includes information associated with a user device. The first MME device creates a context for the user device based on the information, stores the context, and creates an optimized context based on the context, wherein a size of the optimized context is smaller than a size of the context. The first MME device also identifies a second MME device that is a backup for the first MME device, and transmits the optimized context to the second MME device.