Abstract:
A device may receive relationship information indicating a relationship between first geographic information and a network gateway. The network gateway may be associated with providing a user device with access to a network. The device may store the relationship information. The device may receive, from the user device and via a base station, second geographic information indicating a tracking area in which the user device is located. The device may identify one or more network gateways, associated with the second geographic information, based on the second geographic information and the relationship information. The device may provide, to the user device, one or more device identifiers associated with the one or more network gateways to permit the user device to access the network via the one or more network gateways. The one or more device identifiers may be provided in association with a non-access stratum message.
Abstract:
A device may detect an event associated with a user device. The event may include at least one of a data reachability event, a loss of connectivity event, or a loss of reachability event. The device may determine, based on detecting the event, event information associated with the event. The event information may include information that identifies a type of a packet data network (PDN) connection when the event includes a data reachability event. The event information may include information that identifies a reason for detachment from a network when the event includes a loss of connectivity event. The event information may include information indicating that one or more PDN connections have been closed when the event includes a loss of reachability event. The device may provide the event information for reporting to one or more devices that are to receive event reports associated with the user device.
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:
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:
In some implementations, a radio access network (RAN) may receive a graded quality of service (QoS) profile indicating a set of QoS profiles and corresponding observed flow data rates. The RAN may measure an observed flow data rate of traffic associated with a session. The RAN may select a QoS profile from the set of QoS profiles based on the observed flow data rate. The RAN may apply the QoS profile to the session.
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:
In some implementations, a policy control function (PCF) device may receive, from an access and mobility management function (AMF) device, an access and mobility (AM) policy association request that is related to a user equipment (UE) that is associated with AM policy data. The PCF device may modify at least a portion of the AM policy data to generate modified AM policy data associated with the UE. The PCF device may create, based on the modified AM policy data, an AM control policy associated with the UE. The PCF device may transmit, to the AMF device, an AM policy association message, responsive to the AM policy association request, indicating the AM control policy.
Abstract:
A device may receive performance requirements for a service, and may receive RAN factors that influence a RAN, core factors that influence a core network, and transport factors that influence a transport network. The device may determine a RAN capability to satisfy the performance requirements, and may determine a core capability to satisfy the performance requirements. The device may determine a transport capability to satisfy the performance requirements, and may determine RAN configuration settings, core configuration settings, and transport configuration settings based on the RAN capability, the core capability, and the transport capability, respectively. The device may generate a RAN SON based on the RAN configuration settings, a core SON based on the core configuration settings, and a transport SON based on the transport configuration settings. The device may create a network slice based service area based on the RAN SON, the core SON, and the transport SON.
Abstract:
In some implementations, an entity in a wireless network may receive a packet with a flag set to a first value, wherein the first value indicates that the packet is associated with non-low latency, low loss and scalable throughput (non-L4S) traffic. The entity may determine, based on a packet detection rule, that the packet should be associated with L4S traffic. The entity may transmit, based on a determination that the packet should be associated with L4S traffic, the packet with the flag set to a second value, wherein the second value indicates that the packet is associated with L4S traffic.
Abstract:
A network device may receive, for an emergency call, a session initiation protocol (SIP) invite that includes a registered address of a user device that initiated the emergency call, and may determine whether the user device is associated with a private network based on the SIP invite. The network device may extract the registered address of the user device from the SIP invite and based on the user device being associated with the private network, and may provide the registered address to another network device. The other network device may determine a registered geographic location of the user device, based on the registered address, and may provide the registered geographic location to a public safety answering point associated with the emergency call.