Abstract:
A network device may receive a request for determination of a first non-session management policy control decision for a UE, and may provide an account limits request to another network device based on the request. The network device may receive, from the other network device, account limits for the UE, and may determine a first non-session management policy control service for the UE based on the account limits. The network device may cause the UE to be provisioned with a service based on the first non-session management policy control service, and may receive a request for determination of a second non-session management policy control decision for the UE. The network device may determine a second non-session management policy control service for the UE based on the account limits, and may cause the UE to be provisioned with a service based on the second non-session management policy control service.
Abstract:
A first network device may receive, from a second network device, a first policy control create request and may provide, to the second network device, a common policy control request trigger. The first network device may receive a second policy control create request associated with a user equipment (UE) and may cause a UE policy to be provided to the UE. The first network device may receive, from a third network device, a third policy control create request and may provide a network device policy to the third network device. The first network device may receive, from the second network device, a policy control update request based on the common policy control request trigger and may generate an updated UE policy or an updated network device policy based on the policy control update request.
Abstract:
One or more devices are provided that receive a request, from a client device, to connect to an operator network. The request is received at a request time. The one or more devices obtain information identifying a connect time at which the client device is permitted to connect to the operator network and determine whether the request time matches the connect time. If the request time is determined to be different than the connect time, the one or more devices reject the request to connect to the operator network based on the request time being determined to be different than the connect time. If the request time is determined to match the connect time, the one or more devices establish a communication session between the client device and the operator network based on the request time being determined to match the connect time.
Abstract:
A first device may receive data associated with a second device from within a first network and independently of a second network. The second device may include a sensor or an application to form or process a data record. The first device may establish a bearer between the first device and a particular user device, of multiple user devices, in accordance with a bearer policy; and provide the data towards the particular user device via a first sub-network, of multiple sub-networks, of the second network and via the bearer. The first sub-network may be independent of a second sub-network of the multiple sub-networks. The second sub-network may permit user device data to be transmitted between the multiple user devices. The first sub-network and the second sub-network may consume different levels of network resources.
Abstract:
A system may receive a request to receive a particular quality of service level for traffic flow between a user device and an over-the-top application server that provides an over-the-top application service. The over-the-top application server may be outside of a service provider network. The system may determine that the user device is to receive the particular quality of service level for the over-the-top application service based on receiving the request. The system may cause the traffic flow to receive the particular quality of service level based on determining that the user device is to receive the particular quality of service level. The traffic flow may be transmitted using the service provider network. The system may determine usage information associated with the traffic flow, where the usage information identifies the user device and the particular quality of service level. The system may provide the usage information.
Abstract:
A first device may establish a connection with a user device via a particular bearer associated with multiple policies for corresponding data flows. The first device may also receive a first data packet associated with a first data flow; apply, to the first data flow, a first policy of the multiple policies; transmit the first data packet to the user device via the particular bearer; receive a second data packet associated with a second data flow; apply, to the second data flow, a second policy of the one or more policies; and transmit the second data packet to the user device via the particular bearer.
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:
Examples described herein involve an internet protocol (IP) multimedia subsystem (IMS) network. An example process may include receiving, from a user equipment (UE), a request for an IMS session. The IMS session may be between the IMS network and the UE. The process may include requesting a subscriber management component to provide platform information associated with the IMS session. The platform information may identify a platform device that hosts a user plane function (UPF) for the IMS session. The process may include receiving, from the subscriber management component, the platform information and selecting, based on the platform information, a user plane component of the IMS network. The user plane component may perform a user plane operation associated with the IMS session. The process may include causing the user plane component to perform the user plane operation for the IMS session.
Abstract:
A base station may receive an indication to manage a connection, associated with a device, or traffic associated with the device. The indication may include a network identifier associated with a core network. The base station may determine, based on the network identifier, management information associated with managing the connection or the traffic associated with the device. The base station may manage, based on the management information, the connection or the traffic associated with the device.
Abstract:
A device may receive streaming information associated with one or more user devices, streaming content being provided to the one or more user devices, and a cell associated with the one or more user devices. The device may determine a quantity of user devices receiving the streaming content in the cell based on the streaming information. The device may determine whether the streaming content is being provided using a unicast stream or is being provided using a multicast stream. The device may determine to switch from the unicast stream to the multicast stream or from the multicast stream to the unicast stream based on the quantity of user devices. The device may switch from the unicast stream to the multicast stream, or the multicast stream to the unicast stream based on determining to switch.