Abstract: A system described herein may maintain policy information associating a plurality of network credentials with respective device identifiers of User Equipment (“UEs”) that are authorized to use respective network credentials to access a network. The system may receive network monitoring information indicating that a particular UE, associated with a particular device identifier, is accessing the network using a particular network credential; compare the particular device identifier and the particular network credential to the policy information; determine, based on comparing the particular device identifier and the particular network credential to the policy information, that the particular UE is not authorized to use the particular network credential; and output a notification to the network that the particular UE is not authorized to use the particular network credential to access the network, wherein the network suspends the particular network credential based on the notification.

Abstract: Disclosed are systems and methods that provide a framework that enables user to delegate other users as operators of their securely held account credentials via services backed by OAuth protocols. The disclosed framework provides functionality for users to be delegated access to other users' account credentials, information and resources for the performance of specific electronic transactions. The framework operates by connecting two OAuth registered users so that one user can perform an electronic transaction using another user's securely held credentials upon approval by the other user. This ensures that each electronic transaction is securely held and performed, and operated under the control of the delegator despite performance of the transaction by the delegatee involving the delegator's account information.

Abstract: A method, a device, and a non-transitory storage medium are described in which a native-based support service for an over-the-top application is provided. A network device provides a registration procedure that enables a linking between an identity of the over-the-top application and an identity of a native application for a communication service, and enables a quality of service to be provisioned afforded to the native application for the over-the-top application. The network device provisions originating and terminating communication sessions of the communication service having the native quality of service in relation to the identity of the over-the-top application.

Abstract: A device can be configured to receive first internet protocol multimedia subsystem (IMS) data from a user device, provide the first IMS registration data to an IMS device, maintain—on behalf of the user device—an IMS connection between the user device and the IMS device. In addition, the device an receive, from the IMS device, an IMS invite addressed to the user device, temporarily hold the IMS invite, provide a push notification device with a push notification request specifying the user device, receive second IMS registration data from the user device, and perform an action based on the second IMS registration data.

Abstract: A method, a device, and a non-transitory storage medium are described in which a native-based support service for an over-the-top application is provided. A network device provides a registration procedure that enables a linking between an identity of the over-the-top application and an identity of a native application for a communication service, and enables a quality of service to be provisioned afforded to the native application for the over-the-top application. The network device provisions originating and terminating communication sessions of the communication service having the native quality of service in relation to the identity of the over-the-top application.

Abstract: A device can be configured to receive first internet protocol multimedia subsystem (IMS) data from a user device, provide the first IMS registration data to an IMS device, maintain—on behalf of the user device—an IMS connection between the user device and the IMS device. In addition, the device an receive, from the IMS device, an IMS invite addressed to the user device, temporarily hold the IMS invite, provide a push notification device with a push notification request specifying the user device, receive second IMS registration data from the user device, and perform an action based on the second IMS registration data.

Abstract: A device can be configured to receive first internet protocol multimedia subsystem (IMS) data from a user device, provide the first IMS registration data to an IMS device, maintain—on behalf of the user device—an IMS connection between the user device and the IMS device. In addition, the device an receive, from the IMS device, an IMS invite addressed to the user device, temporarily hold the IMS invite, provide a push notification device with a push notification request specifying the user device, receive second IMS registration data from the user device, and perform an action based on the second IMS registration data.

Abstract: A device can be configured to receive first internet protocol multimedia subsystem (IMS) data from a user device, provide the first IMS registration data to an IMS device, maintain—on behalf of the user device—an IMS connection between the user device and the IMS device. In addition, the device an receive, from the IMS device, an IMS invite addressed to the user device, temporarily hold the IMS invite, provide a push notification device with a push notification request specifying the user device, receive second IMS registration data from the user device, and perform an action based on the second IMS registration data.

Abstract: A method including determining that a device is connected to a first communication network; establishing, via the first communication network, a multimedia session with the device serving as a first endpoint of the multimedia session via the first communication network; determining that the device is connected to a second communication network while the multimedia session is ongoing, wherein the second communication network is different than the first communication network; requesting via the second communication network, in response to determining that the device is connected to the second communication network while the multimedia session is ongoing, that the first endpoint of the multimedia session be replaced with the device serving as a second endpoint of the multimedia session via the second communication network; and continuing, after the request that the first endpoint of the multimedia session be replaced, the multimedia session via the second communication network.

Abstract: Multiple mobile device numbers (MDNs) may be associated with a single user device. For outgoing communications, the user may choose which of the accounts are to be used. For incoming communications, application layer processes may perform an arbitration function to ensure that that the communication state, associated with each MDN, is correctly updated both at the user device and in the telecommunications network.

Abstract: A method including determining that a device is connected to a first communication network; establishing, via the first communication network, a multimedia session with the device serving as a first endpoint of the multimedia session via the first communication network; determining that the device is connected to a second communication network while the multimedia session is ongoing, wherein the second communication network is different than the first communication network; requesting via the second communication network, in response to determining that the device is connected to the second communication network while the multimedia session is ongoing, that the first endpoint of the multimedia session be replaced with the device serving as a second endpoint of the multimedia session via the second communication network; and continuing, after the request that the first endpoint of the multimedia session be replaced, the multimedia session via the second communication network

Abstract: An identifier may be generated for an endpoint device associated with a user device. The identifier may include first data indicating that the identifier is generated, second data identifying the user device, and third data identifying the endpoint device from a plurality of endpoint devices associated with the user device. The identifier may be formatted as an International Mobile Subscriber Identity (IMSI). The first data may include a three-digit mobile country code (MCC) not associated with a country. The second data may include a telephone number associated with the user device. The third data includes a counter value incremented for endpoint devices associated with the user device.

Abstract: Multiple mobile device numbers (MDNs) may be associated with a single user device. For outgoing communications, the user may choose which of the accounts are to be used. For incoming communications, application layer processes may perform an arbitration function to ensure that that the communication state, associated with each MDN, is correctly updated both at the user device and in the telecommunications network.

Abstract: An identifier may be generated for an endpoint device associated with a user device. The identifier may include first data indicating that the identifier is generated, second data identifying the user device, and third data identifying the endpoint device from a plurality of endpoint devices associated with the user device. The identifier may be formatted as an International Mobile Subscriber Identity (IMSI). The first data may include a three-digit mobile country code (MCC) not associated with a country. The second data may include a telephone number associated with the user device. The third data includes a counter value incremented for endpoint devices associated with the user device.

Abstract: A user device may receive an identifier without prior provisioning from a server. The server may be configured to: receive, from a user device a first identifier, a first value of a second identifier, and an instruction to register the first value with the first identifier; register the first value with the first identifier based on determining that the second identifier is available for registration; receive request for subscription to receive a notification when a second user device registers with the first identifier; provide, to the user device, a list of unavailable or available second values of the second identifiers; receive, from the user device, a second instruction to register one of the available second values with the first identifier and with the user device; and receive, from the user device, a third instruction including an instruction to unregister the first value with the first identifier.

Abstract: A user device may receive an identifier without prior provisioning from a server. The server may be configured to: receive, from a user device a first identifier, a first value of a second identifier, and an instruction to register the first value with the first identifier; register the first value with the first identifier based on determining that the second identifier is available for registration; receive request for subscription to receive a notification when a second user device registers with the first identifier; provide, to the user device, a list of unavailable or available second values of the second identifiers; receive, from the user device, a second instruction to register one of the available second values with the first identifier and with the user device; and receive, from the user device, a third instruction including an instruction to unregister the first value with the first identifier.