Abstract: A base station may establish a radio resource control (RRC) connection with a first user device. The base station may determine a bearer attribute of a bearer associated with the RRC connection and the first user device. The base station may determine that the bearer attribute satisfies a set of conditions, and may analyze multiple bearer attributes associated with multiple established RRC connections. The base station may select a terminable RRC connection, of the multiple established RRC connections, based on analyzing the multiple bearer attributes. The terminable RRC connection may be associated with a second user device that is different from the first user device, and the terminable RRC connection may be different from the RRC connection. The device may terminate the terminable RRC connection based on selecting the terminable RRC connection.

Abstract: A system may receive a bandwidth allocation policy, may allocate first bandwidth to a first set of queues based on the bandwidth allocation policy, and may allocate second bandwidth to a second set of queues based on the bandwidth allocation policy. The system may identify a first characteristic associated with packets, and may store information associated with the packets in first queues based on the first characteristic. The system may identify a second characteristic associated with the packets, and may store information associated with the packets, from the first queues, in second queues, based on the second characteristic, the allocated first bandwidth, and the bandwidth allocation policy. The system may store information associated with the packets, from the second queues, in an output queue based on the allocated second bandwidth and the bandwidth allocation policy, and may service the packets from the output queue for delivery to a device.

Abstract: A network selection device may determine that a communication between a user device and a first network device should be transferred from the first network device to a second network device that is in an idle state; output an instruction to cause the second network device to exit the idle state and communicate with the user device; determine that the second network device is unused or underutilized; and output, based on determining that the second network device is unused or underutilized, an instruction to cause the second network device to reenter the idle state.

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 is configured to obtain backlog information from a network device. The backlog information indicates a backlog of a queue included in the network device. The device obtains settings information for the network device. The settings information indicates a setting of the queue. The device determines an adjustment to the setting of the queue based on the backlog information and the settings information. The device provides adjustment information, indicating the adjustment to the setting of the queue, to the network device for the network to adjust the setting of the queue.

Abstract: A device is configured to obtain base station information for base stations indicating whether data communicated via a respective base station should receive optimization processing. The device may obtain a base station identifier from a base station. The device may determine whether the data communicated via the base station should receive the optimization processing based on the base station information and the base station identifier. The device may receive non-optimized data to be sent to a client device via the base station. The device may selectively cause the optimization processing to be performed on the non-optimized data based on whether the data communicated via the base station should receive the optimization processing. The device may provide optimized data generated by the optimization processing or the non-optimized data to the client device via the base station based on selectively causing the optimization processing to be performed.

Abstract: A device receives configuration information that instructs the device about when to send content to a user device. The device also receives content from an application server at a first time, and stores the content. The device determines, based on the configuration information, that the content is to be sent to the user device, and sends the content to the user device based on the determination. The content is sent to the user device at a second time that is later than the first time.

Abstract: A network device within an outdoor broadband unit receives, via Ethernet over coaxial cable signals, Internet Protocol (IP) data traffic originating from a device within a local area network (LAN). The IP data traffic is buffered in a memory within the outdoor broadband unit. A forwarding plane module of the network device sends the IP data traffic toward a destination via an air interface for a wide area network (WAN). The network device receives, via different Ethernet over coaxial cable signals, IP control traffic originating from the device within the LAN. A control plane module of the network device implements the instructions in the IP control traffic to initiate a test function for the network device.

Abstract: A base station may establish a radio resource control (RRC) connection with a first user device. The base station may determine a bearer attribute of a bearer associated with the RRC connection and the first user device. The base station may determine that the bearer attribute satisfies a set of conditions, and may analyze multiple bearer attributes associated with multiple established RRC connections. The base station may select a terminable RRC connection, of the multiple established RRC connections, based on analyzing the multiple bearer attributes. The terminable RRC connection may be associated with a second user device that is different from the first user device, and the terminable RRC connection may be different from the RRC connection. The device may terminate the terminable RRC connection based on selecting the terminable RRC connection.

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 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: An exemplary method includes detecting, by a user feedback system, ring-back content provided to a first computing device during a connection period prior to beginning a communication session between the first computing device and a second computing device, and providing, by the user feedback system in conjunction with the detecting of the ring-back content provided to the first computing device, a feedback mechanism that facilitates a user of the first computing device providing feedback regarding the ring-back content. Corresponding systems and methods are also described.

Abstract: A device receives, from a content provider, traffic parameters associated with a video content request received from a fixed user device connected to a wireless access network, and determines, based on the traffic parameters, a trigger for creating a dedicated bearer for the fixed user device in the wireless access network. The device also provides the trigger to the wireless access network, where the wireless access network creates the dedicated bearer for the fixed user device based on the trigger, and the wireless access network assigns quality of service (QoS) parameters, based on the traffic parameters, to video content delivered to the fixed user device.

Abstract: A network device is configured to send information identifying a frequency at which an application, downloaded on a user device, is to send geographic location information to the network device. The network device is configured further to receive personal information associated with a plurality of social networking applications from the application on the user device. The network device is configured further to receive the geographic location information from the application; and send the personal information and the geographic location information to a plurality of social networking servers associated with a plurality of social networking applications.

Abstract: A system is configured to receive, from a user device, voice traffic to be sent to another user device; determine whether the voice traffic is local traffic based on whether an eNodeB, associated with the user device, and another eNodeB, associated with the other user device, are served by a particular network device; forward the voice traffic, as non-local traffic, to another network device, associated with a packet data network, for processing when the eNodeB or the other eNodeB are not served by the particular network device; process the voice traffic as local traffic when the eNodeB and the other eNodeB are served by the particular network device; and forward, to the other user device via the other eNodeB, the voice traffic, as local traffic, where the forwarding is performed in a manner that does not include routing the voice traffic via the other network 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.

Abstract: A network device may receive, from a first telecommunications network, one or more temporary credentials that allow access to the first telecommunications network; receive, from a user device, a request to access the first telecommunications network; provide, to a server device associated with a second telecommunications network associated with the user device, a service validation request; receive, from the server device, a service validation response indicating that the user device is permitted to access the first telecommunications network; provide, based on receiving the service validation response, a particular temporary credential, of the one or more temporary credentials, to the user device; and transmit data to or from the user device via the first telecommunications network when the particular temporary credential is used to access the telecommunications network.

Abstract: A device may receive network congestion information relating to one or more connections. The network congestion information may identify respective utilizations of the one or more connections. The one or more connections may be associated with one or more access points. The device may cause the network congestion information to be provided to a set of user equipments (UEs) via a multicast transmission to cause one or more UEs, of the set of UEs, to switch from a first connection, of the one or more connections, to a second connection, of the one or more connections, based on the network congestion information. The one or more UEs may be connected to a network via a multicast connection.

Abstract: A device is configured to obtain interference information indicating interference levels at frequencies. The device is configured to determine a frequency for a small cell to use to communicate with a client device based on the interference information. The small cell is capable of using the frequencies to communicate and the frequency is determined from among the frequencies. The device is further configured to provide frequency information to the small cell instructing the small cell to communicate with the client device using the frequency.

Abstract: A method, a device, and a non-transitory storage medium provide to store packet data network (PDN) connection data pertaining to a user equipment connected to a network; store locale-to-packet data network gateway (PGW) data, wherein the locale-to-PGW data includes mappings between locales and PGWs to be used when the user equipment is located in the locales; receive a locale update pertaining to the user equipment; query the locale-to-PGW data in response to the locale update; determine, based on a result of the query, whether the user equipment is to be re-anchored to a different PGW than a PGW to which the user equipment is currently anchored; invoke a re-anchoring procedure, in response to a determination that the user equipment is to be re-anchored to the different PGW; and omit to invoke the re-anchoring procedure, in response to a determination that the user equipment is not to be re-anchored.