Abstract: A computer device may include logic configured to intercept a tracking area update response from a wireless network device to a user equipment device and trigger a device ping process for the user equipment device, in response to intercepting the tracking area update response. The logic may be further configured to generate a device ping message based on the triggering; send the device ping message to an application system associated with the user equipment device; receive a device ping response from the application system; incorporate information from the device ping response into the intercepted tracking area update response; and send the tracking area update response with the incorporated device ping information to the user equipment device.

Abstract: A method, a device, and a non-transitory storage medium provide to receive a trigger to initiate a media session that is to be supported by a control channel and a media channel; generate a first Short Message Service (SMS) message, which includes a first Session Initiation Protocol (SIP) message configured to initiate the media session, in response to the trigger; transmit, via non-access stratum as the control channel, the first SMS message that includes the first SIP message to a server via a mobility management entity, in response to the generation; determine whether a bearer for the media channel is already established; establish the bearer in response to a determination that the bearer is not already established; use the bearer as the media channel in response to the establishment; and use the bearer as the media channel in response to a determination that the bearer is already established.

Abstract: A device may receive service information associated with an internet protocol multimedia subsystem (IMS) service. The IMS service may be provided via an IMS network. The service information may include information that identifies a terminating device that is to receive the IMS service. The device may cause registration trigger information to be provided to the terminating device based on receiving the service information. The registration trigger information may be provided to the terminating device to cause the terminating device to register to the IMS network to allow the terminating device to receive the IMS service.

Abstract: A device may receive a request to establish a packet data network (PDN) session for a user device. The device may provide a first instruction to establish the PDN session for the user device with a temporary default bearer based on receiving the request. The temporary default bearer may be maintained for less than a duration of the PDN session. The device may receive an indication to release the temporary default bearer after providing the first instruction to establish the PDN session. The device may provide a second instruction to release the temporary default bearer and maintain one or more signaling sessions associated with the PDN session based on receiving the indication to release the temporary default bearer. The one or more signaling sessions, associated with the PDN session, may be maintained after the temporary default bearer has been released.

Abstract: A first server device, associated with a first carrier network, may provide a first identifier of a first application device to a second server device to cause the second server device to store the first identifier. The second server device may be accessible from the first carrier network and from a different second carrier network. The first server device may receive a first message from the first application device; transmit the first message and the first identifier of the first application device towards a client device via the first carrier network and the second carrier network; receive, from a second application device associated with the second carrier network, a second message; identify the second application device based on information, maintained by the second server, associating the second application device with the second identifier; identify a set of policies based on the second identifier; and apply the set of policies.

Abstract: The period for Tracking Area Update (TAU) requests, that are made by Machine-to-machine (M2M) User Equipment (UE) in a wireless cellular network, may be dynamically modified. In one implementation, the period for the TAU request may be dynamically increased for M2M UEs that tend to be stationary. Increasing the period at which M2M UEs initiate TAU requests with the wireless network can reduce the amount of control signaling that needs to be performed over the radio links.

Abstract: A system may be configured to establish a communication between a first user device and a second user device, where the first and second user devices are associated with different service providers that provide different networks with which the first and second user devices are respectively associated. The establishing may include determining capability information, associated with the second user device, without requesting the capability information from the telecommunications network with which the second user device is associated. The establishing may further include transcoding the communication based on the capability information associated with the second user device.

Abstract: A device may receive service information associated with an internet protocol multimedia subsystem (IMS) service. The IMS service may be provided via an IMS network. The service information may include information that identifies a terminating device that is to receive the IMS service. The device may cause registration trigger information to be provided to the terminating device based on receiving the service information. The registration trigger information may be provided to the terminating device to cause the terminating device to register to the IMS network to allow the terminating device to receive the IMS service.

Abstract: A first server device, associated with a first carrier network, may provide a first identifier of a first application device to a second server device to cause the second server device to store the first identifier. The second server device may be accessible from the first carrier network and from a different second carrier network. The first server device may receive a first message from the first application device; transmit the first message and the first identifier of the first application device towards a client device via the first carrier network and the second carrier network; receive, from a second application device associated with the second carrier network, a second message; identify the second application device based on information, maintained by the second server, associating the second application device with the second identifier; identify a set of policies based on the second identifier; and apply the set of policies.

Abstract: A device provides, to a domain name system (DNS), uniform resource locator (URL) information received from a user device, and generates a redirect query when a redirect error is received from the DNS based on the URL information. The device also provides the redirect query to a policy server/accounting database, and receives, from the policy server/accounting database, information indicating that the user device subscribes to a redirect service and subscriber information associated with the user device. A device management database (DMD) query is generated based on the subscriber information, provides the DMD query to a DMD server, and receives, from the DMD server, model information associated with the user device, where the URL information and the model information are used to retrieve redirect information for the user device.

Abstract: A device provides, to a domain name system (DNS), uniform resource locator (URL) information received from a user device, and generates a redirect query when a redirect error is received from the DNS based on the URL information. The device also provides the redirect query to a policy server/accounting database, and receives, from the policy server/accounting database, information indicating that the user device subscribes to a redirect service and subscriber information associated with the user device. A device management database (DMD) query is generated based on the subscriber information, provides the DMD query to a DMD server, and receives, from the DMD server, model information associated with the user device, where the URL information and the model information are used to retrieve redirect information for the user device.