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:
A network repository function (NRF) device may receive first locality and priority information concerning a first network function device from the first network function device and may receive second locality and priority information concerning a second network function device from the second network function device. The NRF device may update a data structure based on the first locality and priority information and the second locality and priority information. The NRF device may receive a query concerning a locality from a third network function device and may search the data structure based on the query to identify network function device information associated with the locality. The NRF device may send the network function device information to the third network function device.
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 mobility management entity device (MME) may receive a request from a user device to attach to a network. The request to attach to the network may include a user device identifier for the user device. The MME may receive, from a home subscriber server (HSS) and based on the user device identifier for the user device, information relating to the user device. The information may include at least one connection parameter. The at least one connection parameter may include at least information indicating whether a bearer should be allocated to the user device. The MME may establish a network connection for the user device based on the at least one connection parameter. The MME may cause traffic to be routed from the user device based on the at least one connection parameter.
Abstract:
A device may be configured to store advertisement control information for an advertisement. The advertisement control information may indicate a target demographic for the advertisement. The device may receive the advertisement to be provided to a user device via an operator network. The device may receive user information that indicates a demographic of a user of the user device. The device may determine a quality of service level with which to provide the advertisement to the user device. The quality of service level may be determined based on the target demographic and the demographic of the user. The device may provide the advertisement to the user device, via the operator network, at the determined quality of service level.
Abstract:
A device is configured to determine quality of service information and determine a set of service classes, associated with a wireless local area network, based on the quality of service information. The device is configured to determine an association between the set of service classes and a set of service identifiers. The device is configured to receive data traffic and to determine a service class, of the set of service classes, associated with the data traffic based on the association between the set of service classes and the set of service identifiers. The device is configured to schedule delivery of the data traffic based on the service class and to deliver the data traffic via the wireless local area network.
Abstract:
A device may receive a packet that includes priority information that is based on a priority assigned to bits included in the packet. The priority may be assigned based on scalable code used to encode the bits for transmission. The device may determine that an indicator of network congestion satisfies a threshold, and may schedule the packet for transmission to a user device based on the priority information and the determination that the indicator satisfies the threshold.
Abstract:
In some implementations, a unified data repository (UDR) device may receive, from a network device, a request associated with a user equipment (UE). The request may indicate an external identifier of the UE. The UDR device may determine, based on the external identifier of the UE, an internal identifier of the UE. The UDR device may provide, to the network device, a request response that is in response to the request. The request response may indicate information identified via the internal identifier of the UE.
Abstract:
In some implementations, a unified data repository (UDR) device may receive, from a unified data management (UDM) device or a policy control function (PCF) device, a subscription request to subscribe to receive a data change notification from the UDR device. The subscription request may include a monitoring indication and a report indication. The monitoring indication may identify a monitored data set associated with a user equipment (UE). The report indication may identify an attribute data set associated with the UE and indicate a request to receive a report associated with the attribute data set. The UDR may transmit, to at least one of the UDM device or the PCF device, an indication of a subscription to receive the data change notification based on the subscription request and the report based on the report indication.
Abstract:
A network device may receive a PDU session create message associated with establishing a PDU session with a user device and via a RAN, and may receive a first 5QI value and a second 5QI value associated with the PDU session. The network device may attempt to establish the PDU session with the first 5QI value and via the RAN, and may receive an indication that the first 5QI value is not supported for establishing the PDU session. The network device may cause the PDU session to be established with the second 5QI value, and via the RAN, based on the indication that the first 5QI value is not supported for establishing the PDU session.