Abstract:
A data message is received from a machine-to-machine (M2M) device over a mobile communication network. The data message includes: a Machine Identification (MID) number of a machine coupled to the M2M device and/or an identifier of the M2M device; location information of the machine; and an alert based on a condition of the machine satisfying a service or alarm criterion. A database associated with the application server is searched for different solutions for the machine satisfying a service or alarm criterion. The machine is then matched with one or more providers that can service the machine for each solution. A tailored response data message, based on the machine location information, the identified condition and the matched provider(s), is sent to the user of the machine.
Abstract:
A device may receive data indicating a required quality of service (QoS), and may receive radio access network (RAN) information associated with a RAN, wherein the RAN information is provided by a centralized unit (CU) of the RAN. The device may provide the RAN information to a multi-access edge computing (MEC) platform, and may receive, from the MEC platform, a QoS request that requests the required QoS. The device may provide the QoS request to the CU, and may receive a QoS response to the QoS request. The device may provide the QoS response to a policy control function (PCF) of a core network, and may receive an indication of approval of the QoS response from the PCF. The device may cause, based on receiving the indication of approval, the required QoS to be implemented by the MEC platform and network devices associated with the core network.
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 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.
Abstract:
A device may determine that a user device, connected to a first packet data network gateway (PGW) associated with a first area, is located in a second area associated with a second PGW. The first PGW may be associated with a provider network. The second PGW may be associated with the provider network. The user device may not be connected to the second PGW. The device may cause the user device to be disconnected from the first PGW and connected to the second PGW. The user device may remain connected to the provider network when disconnecting from the first PGW and connecting to the second PGW.
Abstract:
A device may receive a network identifier and roaming policy information associated with the network identifier. The roaming policy information may identify a manner in which to treat traffic associated with mobile devices that are associated with a home network identified by the network identifier. The device may store the network identifier and the roaming policy information using a global roaming policy data structure. The device may provide the network identifier and the roaming policy information to a mobility management entity device for storage using a local roaming policy data structure accessible by the mobility management entity device. The mobility management entity device may be one of multiple mobility management entity devices having access to respective local roaming policy data structures.
Abstract:
A device may receive information that identifies a radio frequency condition of a user device, where the radio frequency condition indicates a quality of a radio access network connection of the user device. The device may determine a radio frequency parameter value based on the radio frequency condition, and may set a data rate for a transmission control protocol (“TCP”) communication with the user device based on the radio frequency parameter value.