Abstract: A network device may receive, a flow control request for a first device that is registered for an internet protocol (IP) pinhole service. The flow control request may include a device identifier associated with the first device and a private IP address. The network device may identify at least one of IP address information, port information, and pinhole rules. The network device may provide, to another network device, a flow control response that includes at least one of the IP address information, the port information, and the pinhole rules. The flow control response may cause the other network device to allow traffic flow through the firewall using at least one of the IP address information and the port information. The network device may provide a public IP address and a port identifier to a second device, allowing the second device to provide traffic to the first device.

Abstract: A first device can receive an attach request that includes information associated with a user device. The user device can provide the attach request to request access to a network. The first device can provide, to a second device and using the information associated with the user device, a request for information associated with a group identifier that is associated with the user device. The first device can receive, from the second device, the information associated with the group identifier that is associated with the user device based on providing the request for information associated with the group identifier. The first device can determine a network slice identifier that is associated with the user device based on the information associated with the group identifier that is associated with the user device. The first device can permit the user device to access a network slice, of the network, that is associated with the network slice identifier based on determining the network slice identifier.

Abstract: A mobility management node, in a first wireless carrier network, receives a connection request that includes a first Access Point Name (APN) that is invalid in the first wireless carrier network, wherein the connection request originated from a wireless device. The mobility management node obtains a set of first APNs that map the first APN, and other APNs, that are invalid in the first wireless carrier network, and translates the first APN to a second APN corresponding to the first wireless carrier network using the set of first APNs. The mobility management node uses the second APN in signaling associated with a connection, between the wireless device and the first wireless carrier network.

Abstract: A method includes determining, by a user equipment (UE) device, whether subscriber identification profile (SIDP) is stored within the UE device; sending, from the UE device, an attach request along with a universal globally unique temporary identifier (UGUTI) to a mobility management entity (MME) within a network, upon determining that the subscriber identification profile is not stored in the UE device; receiving, at the UE device, an authorization to attach to the network in response to the attach request; and accessing, by the UE device, the network in accordance with a pre-provisioned profile associated with the UGUTI, where the pre-provisioned profile limits access to the network.

Abstract: A network device may receive, a flow control request for a first device that is registered for an internet protocol (IP) pinhole service. The flow control request may include a device identifier associated with the first device and a private IP address. The network device may identify at least one of IP address information, port information, and pinhole rules. The network device may provide, to another network device, a flow control response that includes at least one of the IP address information, the port information, and the pinhole rules. The flow control response may cause the other network device to allow traffic flow through the firewall using at least one of the IP address information and the port information. The network device may provide a public IP address and a port identifier to a second device, allowing the second device to provide traffic to the first device.

Abstract: A network device receives, from a base station included in a network, location information associated with a user equipment included in the network. The network device determines, based on the location information, a cell type associated with a cell that is associated with the base station. The network device transmits, based on determining the cell type, a notification to a second network device included in the network, where the second network device, based on receiving the notification, determines a policy rule associated with the cell type, and where the second network device transmits the policy rule.

Abstract: A device may detect an event associated with a user device. The event may include at least one of a data reachability event, a loss of connectivity event, or a loss of reachability event. The device may determine, based on detecting the event, event information associated with the event. The event information may include information that identifies a type of a packet data network (PDN) connection when the event includes a data reachability event. The event information may include information that identifies a reason for detachment from a network when the event includes a loss of connectivity event. The event information may include information indicating that one or more PDN connections have been closed when the event includes a loss of reachability event. The device may provide the event information for reporting to one or more devices that are to receive event reports associated with the user device.

Abstract: Techniques described herein may be used to enable a wireless telecommunication network to provide notification to external devices (such as application servers) regarding Internet-of-Things (IoT) devices attached to the network. A customer may create a notification subscription regarding a group of IoT devices attached to the network. The subscription may identify the IoT devices, the events for which the customer would like to be notified, and an application server that is to receive the notifications (e.g., the IoT devices becoming available to send and receive information), and the application server that is to receive the notifications. The network may monitor the group of IoT devices for the events included in the subscription and may notify the application server if/when the events occur. In response, the application server may communicate with the IoT devices via the network.

Abstract: A device may detect an event associated with a user device. The event may include at least one of a data reachability event, a loss of connectivity event, or a loss of reachability event. The device may determine, based on detecting the event, event information associated with the event. The event information may include information that identifies a type of a packet data network (PDN) connection when the event includes a data reachability event. The event information may include information that identifies a reason for detachment from a network when the event includes a loss of connectivity event. The event information may include information indicating that one or more PDN connections have been closed when the event includes a loss of reachability event. The device may provide the event information for reporting to one or more devices that are to receive event reports associated with the user device.

Abstract: A method includes determining, by a user equipment (UE) device, whether subscriber identification profile (SIDP) is stored within the UE device; sending, from the UE device, an attach request along with a universal globally unique temporary identifier (UGUTI) to a mobility management entity (MME) within a network, upon determining that the subscriber identification profile is not stored in the UE device; receiving, at the UE device, an authorization to attach to the network in response to the attach request; and accessing, by the UE device, the network in accordance with a pre-provisioned profile associated with the UGUTI, where the pre-provisioned profile limits access to the network.

Abstract: A computer device may include a memory configured to store instructions and a processor configured to execute the instructions to select to use an access point name (APN) table to be received from a wireless access network and attach to the wireless access network. The processor may be further configured to execute the instructions to receive a Protocol Configuration Options (PCO) message from the wireless access network; retrieve the APN table from the received PCO message; select an APN from the retrieved APN table; and connect to a packet data network associated with the selected APN via the wireless access network using the selected APN.

Abstract: A method assigns a bootstrap server for wireless devices in a machine-to-machine environment. The method includes receiving, by a network device in a wireless access network and from a wireless device, a first request for a bootstrap server identifier. The method also includes providing, to the wireless device, a response including an address for a carrier-specific bootstrap server device. The method also includes receiving, by the carrier-specific bootstrap server device, a request for management server connection information. The request is submitted by the wireless device using the bootstrap server identifier. The method further includes assigning, by the carrier-specific bootstrap server device, the wireless device to a management server of a group of management servers and sending connection information for the management server to the wireless device.

Abstract: The operational status of devices (such as routers, gateways, etc.) may be determined automatically, without the need for a user to look up status lights or sounds in a manual. A particular device may be automatically identified (e.g., by image recognition techniques), and the operational status may also be automatically identified. For example, a user device may capture an image, video, and/or audio of the device, and may automatically identify an operational status of the device based on the captured image, video, and/or audio. A message and/or suggested set of actions may also be presented to the user, which may indicate the operational status and instructions for one actions that the user may perform to improve the operational status of the device.

Abstract: A network device receives business logic for Policy and Charging Rules Function (PCRF) policies and automatically generates a policy list based on the business logic. The network device receives input for PCRF policies; generates a policy list based on the input; receives signaling messages for user equipment; determines, based on the policy list, policy decisions that are responsive to each of the signaling messages; logs a decision flow associated with each of the signaling messages and a corresponding policy decision; and optimizes an order of the policy list based on the logging.

Abstract: The operational status of devices (such as routers, gateways, etc.) may be determined automatically, without the need for a user to look up status lights or sounds in a manual. A particular device may be automatically identified (e.g., by image recognition techniques), and the operational status may also be automatically identified. For example, a user device may capture an image, video, and/or audio of the device, and may automatically identify an operational status of the device based on the captured image, video, and/or audio. A message and/or suggested set of actions may also be presented to the user, which may indicate the operational status and instructions for one actions that the user may perform to improve the operational status of the device.

Abstract: A network device receives business logic for Policy and Charging Rules Function (PCRF) policies and automatically generates a policy list based on the business logic. The network device receives input for PCRF policies; generates a policy list based on the input; receives signaling messages for user equipment; determines, based on the policy list, policy decisions that are responsive to each of the signaling messages; logs a decision flow associated with each of the signaling messages and a corresponding policy decision; and optimizes an order of the policy list based on the logging.

Abstract: A network device receives business logic for Policy and Charging Rules Function (PCRF) policies and automatically generates a policy list based on the business logic. The network device receives signaling messages for user equipment and determines, based on the policy list, policy decisions that are responsive to each of the signaling messages. The network device further logs a decision flow associated with each of the signaling messages and corresponding policy decisions; determines, based on the logging, if the policy list can be structured more efficiently; and automatically updates the policy list when the policy list can be structured more efficiently.

Abstract: A network device receives business logic for Policy and Charging Rules Function (PCRF) policies and automatically generates a policy list based on the business logic. The network device receives signaling messages for user equipment and determines, based on the policy list, policy decisions that are responsive to each of the signaling messages. The network device further logs a decision flow associated with each of the signaling messages and corresponding policy decisions; determines, based on the logging, if the policy list can be structured more efficiently; and automatically updates the policy list when the policy list can be structured more efficiently.

Abstract: A server device may store inter-layer quality of service (“QoS”) information, indicating a set of link layer QoS levels that are associated with a particular device, a set of network layer QoS levels that are associated with the set of link layer QoS levels, and a set of MPLS QoS levels that are associated with the set of link layer QoS levels. A network device may establish a set of bearers, that correspond to the set of link layer QoS levels, with a particular device; output information regarding the set of network layer QoS levels that are associated with the set of link layer QoS levels, to allow the particular device to select a bearer, of the set of bearers, via which to output traffic to the network device; receive, from the particular device, traffic via the bearer; and determine a particular MPLS QoS level associated with the received traffic.

Abstract: A system and method are provided for reliable activation and attachment of mobile devices. An activation server receives, from a client device, a subscription request for accessing a network, wherein the subscription request includes a first identifier of the client device. The activation server determines, based on the first identifier, whether a pending subscription account exists or a new subscription account is to be created. Upon determining that the pending subscription account exists or the new subscription account is to be created, the activation server releases the pending subscription account or creates the new subscription account, and instructs the client device to remove a second identifier from the client device and to use the first identifier for attaching to the network.