Abstract:
A third-party application, executing at a mobile device, may be provided with information describing congestion levels in a network, such as a cellular wireless network through which the mobile device connects. In one implementation, the third-party application may select, based on the information describing the congestion levels, a data flow, from a number of data flows, to use when communicating with a destination device, each of the data flows being associated with different quality of service (QoS) parameters and being associated with different charging rates. The mobile device may communicate, through a proxy server, and using the selected data flow, with the destination device. The communication with the destination device may be implemented using sponsored data that is not charged to an account associated with an owner of the mobile device.
Abstract:
One or more servers may: receive information regarding a content file stored by a device; provide information associated with a first cost value corresponding to a cost to deliver the content file from the device to a user device; receive a delivery instruction directing the one or more servers to provide a portion of the content file to the user device via one or more ports or via one or more access points, each of the one or more ports or the one or more access points being associated with respective one or more second cost values; generate a key associated with the information regarding the content file and with the delivery instruction; receive an indication of selection of the key by the user device; deliver, to the user device, the portion of the content file via the one or more ports or the one or more access points.
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.
Abstract:
One or more servers may: receive information regarding a content file stored by a device; provide information associated with a first cost value corresponding to a cost to deliver the content file from the device to a user device; receive a delivery instruction directing the one or more servers to provide a portion of the content file to the user device via one or more ports or via one or more access points, each of the one or more ports or the one or more access points being associated with respective one or more second cost values; generate a key associated with the information regarding the content file and with the delivery instruction; receive an indication of selection of the key by the user device; deliver, to the user device, the portion of the content file via the one or more ports or the one or more access points.
Abstract:
Techniques described herein may enable a wireless telecommunications network to implement different types of core networks, and enable end devices—user equipment (UEs) such as broadband devices (e.g., smartphones, tablets) and Internet of Things (IoT)/Machine Type Communication (MTC) devices (sometimes referred to herein as Machine-to-Machine (M2M) devices)—to connect to whichever core network is most suitable to the capabilities of the UE. For example, a broadband core network may provide UEs with broadband connectivity for media sessions (e.g., telephone calls, video calls, etc.) and broadband Internet access. An M2M core network may provide UEs with network connectivity consistent with the lower resource usage patterns typical M2M devices. Additionally, a UE connected to a first core network (e.g., an M2M core network) may detect a prompt to connect to a second core network (e.g., a broadband core network), and in response, may dynamically switch to the second core network.
Abstract:
A third-party application, executing at a mobile device, may be provided with information describing congestion levels in a network, such as a cellular wireless network through which the mobile device connects. In one implementation, the third-party application may select, based on the information describing the congestion levels, a data flow, from a number of data flows, to use when communicating with a destination device, each of the data flows being associated with different quality of service (QoS) parameters and being associated with different charging rates. The mobile device may communicate, through a proxy server, and using the selected data flow, with the destination device. The communication with the destination device may be implemented using sponsored data that is not charged to an account associated with an owner of the mobile device.
Abstract:
Techniques described herein may enable a wireless telecommunications network to implement different types of core networks, and enable end devices—user equipment (UEs) such as broadband devices (e.g., smartphones, tablets) and Internet of Things (IoT)/Machine Type Communication (MTC) devices (sometimes referred to herein as Machine-to-Machine (M2M) devices)—to connect to whichever core network is most suitable to the capabilities of the UE. For example, a broadband core network may provide UEs with broadband connectivity for media sessions (e.g., telephone calls, video calls, etc.) and broadband Internet access. An M2M core network may provide UEs with network connectivity consistent with the lower resource usage patterns typical M2M devices. Additionally, a UE connected to a first core network (e.g., an M2M core network) may detect a prompt to connect to a second core network (e.g., a broadband core network), and in response, may dynamically switch to the second core network.
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.
Abstract:
Techniques described herein may allow for the granting and revoking of temporary access, for User Equipment (“UE”) devices, to a wireless network. Multiple UEs may be registered with a group, where only a limited quantity of UEs in the group may be active at a given time. Once granted access, a UE device may have limits on the access, such as a maximum duration and/or a data limit. When a particular UE device, in a group, requests access to the network, a Group Device Authentication Server (“GDAS”) may determine whether to grant the access, based on how many other UEs in the group (if any) currently have access. The GDAS may also revoke the access once granted (e.g., once the maximum duration has been reached).
Abstract:
Techniques described herein may allow for the granting and revoking of temporary access, for User Equipment (“UE”) devices, to a wireless network. Multiple UEs may be registered with a group, where only a limited quantity of UEs in the group may be active at a given time. Once granted access, a UE device may have limits on the access, such as a maximum duration and/or a data limit. When a particular UE device, in a group, requests access to the network, a Group Device Authentication Server (“GDAS”) may determine whether to grant the access, based on how many other UEs in the group (if any) currently have access. The GDAS may also revoke the access once granted (e.g., once the maximum duration has been reached).