Abstract: A computer-implemented method is provided. The method includes determining, by a user device, that the user device is within range of a particular satellite. The method also includes sending, by the user device, a connection request to the particular satellite in response to determining that the user device is within range of the particular satellite. The connection request is forwarded to a network device, via the particular satellite, to indicate to the network device that the user device is available to receive messages via the particular satellite. The method also includes receiving, by the user device and via the particular satellite, a message from the network device in response to sending the connection request.

Abstract: A method for carrier network integration through a user proxy interface includes receiving a request from a mobile device associated with a subscriber of a carrier provider to establish voice services with the carrier provider for a companion device linked to the mobile device. The request includes a subscriber identifier of the mobile device. The method also includes authenticating the companion device based on the subscriber identifier, obtaining session initiation protocol (SIP) credentials corresponding to the subscriber identifier, and registering the SIP credentials for the companion device at a network interface proxy. The network interface proxy is in communication with an internet protocol multimedia subsystem (IMS) of the carrier provider and the companion device. The method also includes establishing voice services between the companion device and the IMS through the network interface proxy using the SIP credentials.

Abstract: A method for carrier network integration through a user proxy interface includes receiving a request from a mobile device associated with a subscriber of a carrier provider to establish voice services with the carrier provider for a companion device linked to the mobile device. The request includes a subscriber identifier of the mobile device. The method also includes authenticating the companion device based on the subscriber identifier, obtaining session initiation protocol (SIP) credentials corresponding to the subscriber identifier, and registering the SIP credentials for the companion device at a network interface proxy. The network interface proxy is in communication with an internet protocol multimedia subsystem (IMS) of the carrier provider and the companion device. The method also includes establishing voice services between the companion device and the IMS through the network interface proxy using the SIP credentials.

Abstract: A method (300) for carrier network integration through a user proxy interface includes receiving a request (130) from a mobile device (110) associated with a subscriber (10) of a carrier provider (301) to establish voice services with the carrier provider for a companion device (120) linked to the mobile device. The request includes a subscriber identifier (132) of the mobile device. The method also includes authenticating the companion device based on the subscriber identifier, obtaining session initiation protocol (SIP) credentials (140) corresponding to the subscriber identifier, and registering the SIP credentials for the companion device at a network interface proxy (200). The network interface proxy is in communication with an internet protocol multimedia subsystem (IMS) (320) of the carrier provider and the companion device. The method also includes establishing voice services between the companion device and the IMS through the network interface proxy using the SIP credentials.

Abstract: A method for carrier network integration through a user proxy interface includes receiving a request from a mobile device associated with a subscriber of a carrier provider to establish voice services with the carrier provider for a companion device linked to the mobile device. The request includes a subscriber identifier of the mobile device. The method also includes authenticating the companion device based on the subscriber identifier, obtaining session initiation protocol (SIP) credentials corresponding to the subscriber identifier, and registering the SIP credentials for the companion device at a network interface proxy. The network interface proxy is in communication with an internet protocol multimedia subsystem (IMS) of the carrier provider and the companion device. The method also includes establishing voice services between the companion device and the IMS through the network interface proxy using the SIP credentials.

Abstract: A method (300) for carrier network integration through a user proxy interface includes receiving a request (130) from a mobile device (110) associated with a subscriber (10) of a carrier provider (301) to establish voice services with the carrier provider for a companion device (120) linked to the mobile device. The request includes a subscriber identifier (132) of the mobile device. The method also includes authenticating the companion device based on the subscriber identifier, obtaining session initiation protocol (SIP) credentials (140) corresponding to the subscriber identifier, and registering the SIP credentials for the companion device at a network interface proxy (200). The network interface proxy is in communication with an internet protocol multimedia subsystem (IMS) (320) of the carrier provider and the companion device. The method also includes establishing voice services between the companion device and the IMS through the network interface proxy using the SIP credentials.

Abstract: A method, device, and computer-readable medium provide for receiving, from an first presence server at a proxy presence device, a presence status request for presence information associated with a user device in a home carrier network; sending the presence status request to a second presence server in the home carrier network; receiving the presence status of the user device and storing the presence status of the user device in an associated database; sending presence status to the first presence server; receiving at least one subsequent request for the presence status of the user device; and sending the presence status.

Abstract: A method, device, and computer-readable medium provide for receiving, from an first presence server at a proxy presence device, a presence status request for presence information associated with a user device in a home carrier network; sending the presence status request to a second presence server in the home carrier network; receiving the presence status of the user device and storing the presence status of the user device in an associated database; sending presence status to the first presence server; receiving at least one subsequent request for the presence status of the user device; and sending the presence status.

Abstract: A method includes receiving, from an external presence server at a proxy presence device, a presence status request for presence information associated with a user device in a home carrier network. The method includes sending the presence status request to an internal presence server in the home carrier network. The method also includes receiving the presence status of the user device and storing the presence status of the user device with a time to live (TTL) in an associated database. The presence status is sent to the external presence server. The method includes receiving at least one subsequent request for the presence status of the user device within a time window of the TTL. The method also includes sending the presence status within the time window of the TTL without sending another presence status request to the internal presence server.

Abstract: A method includes executing a user equipment (UE) device in a doze mode, a peek mode, and a normal mode. The doze mode includes terminating any connections with a network, comparing a clock time with a maintenance window schedule of maintenance time windows, and executing the peek mode when the clock time is within a maintenance time window. The peek mode includes receiving a connection request from a mobility management entity (MME) system when the MME system has been notified of at least one buffered downlink packet addressed to the UE device, and executing the normal mode in response to receiving the connection request. The normal mode includes establishing a connection to the network and receiving the at least one buffered downlink packet.

Abstract: A device forwards a set of packets between a first network device, associated with a first network, and a second network device, associated with a second network. The set of packets may be associated with permitting access, by a set of mobile devices connected to the first network, to the second network. The device may generate and store configuration information, identifying the set of mobile devices, based on the set of packets. The device may receive, from a third network device, a request associated with establishing a communication session between the third network device and a fourth network device associated with the second network, may determine, based on the configuration information, whether a particular mobile device, associated with the request, is permitted to establish the communication session, and may selectively create the communication session based on determining that the particular mobile device is permitted to establish the communication session.

Abstract: A device may receive a request for domain name system (DNS) information to be provided to a user device communicating via a visited network. The device may identify roaming policy information associated with the user device and, based on the roaming policy information, may determine that the user device is restricted from sending or receiving data via the visited network. The device may determine DNS information, to be provided to the user device, that includes information that identifies a restricted DNS server to which the user device is to be directed. The device may provide the DNS information to the user device to cause the user device to be directed to the restricted DNS server. The user device may be directed to the restricted DNS server to permit a user of the user device to authorize the user device to send or receive data via the visited network.

Abstract: A method includes receiving, from an external presence server at a proxy presence device, a presence status request for presence information associated with a user device in a home carrier network. The method includes sending the presence status request to an internal presence server in the home carrier network. The method also includes receiving the presence status of the user device and storing the presence status of the user device with a time to live (TTL) in an associated database. The presence status is sent to the external presence server. The method includes receiving at least one subsequent request for the presence status of the user device within a time window of the TTL. The method also includes sending the presence status within the time window of the TTL without sending another presence status request to the internal presence server.

Abstract: A first device may receive an indication that a multimedia message service (MMS message) message has been sent from a first user device to a second user device; obtain, from a second device, the roaming status of the first user device at a time that the MMS message was sent by the first user device; generate a call details record (CDR) indicating the obtained roaming status of the first user device at the time the MMS message was sent by the first user device; and store or output the CDR to a billing system that charges an account, associated with the first user device, for sent MMS message. An amount charged by the billing system may be based on the roaming status of the first user device at the time at which MMS message are sent by the first user device.

Abstract: A device forwards a set of packets between a first network device, associated with a first network, and a second network device, associated with a second network. The set of packets may be associated with permitting access, by a set of mobile devices connected to the first network, to the second network. The device may generate and store configuration information, identifying the set of mobile devices, based on the set of packets. The device may receive, from a third network device, a request associated with establishing a communication session between the third network device and a fourth network device associated with the second network, may determine, based on the configuration information, whether a particular mobile device, associated with the request, is permitted to establish the communication session, and may selectively create the communication session based on determining that the particular mobile device is permitted to establish the communication session.

Abstract: A device may receive a request for domain name system (DNS) information to be provided to a user device communicating via a visited network. The device may identify roaming policy information associated with the user device and, based on the roaming policy information, may determine that the user device is restricted from sending or receiving data via the visited network. The device may determine DNS information, to be provided to the user device, that includes information that identifies a restricted DNS server to which the user device is to be directed. The device may provide the DNS information to the user device to cause the user device to be directed to the restricted DNS server. The user device may be directed to the restricted DNS server to permit a user of the user device to authorize the user device to send or receive data via the visited network.

Abstract: A multimedia messaging service (MMS) center (MMSC) receives an MMS message associated with forwarding multimedia content, associated with a source device, to a recipient device. The multimedia content is tagged with tagging data that is generated based on a numerical key. The MMSC parses the modified MMS message to determine the source device and the tagging data. MMSC uses the tagging data to determine the sending device using the tagging data. For example, the MMSC may access an identifier for the sending device, as stored by a subscriber profile controller, using the tagging data and/or a Lightweight Directory Access Protocol (LDAP) interface. The MMSC determines whether the source device associated with the MMS message corresponds to the sending device (e.g., whether the MMS message correctly identifies the sending device), and the MMSC discards the MMS message when the source device and the sending device differ.

Abstract: A first device may receive an indication that a multimedia message service (MMS message) message has been sent from a first user device to a second user device; obtain, from a second device, the roaming status of the first user device at a time that the MMS message was sent by the first user device; generate a call details record (CDR) indicating the obtained roaming status of the first user device at the time the MMS message was sent by the first user device; and store or output the CDR to a billing system that charges an account, associated with the first user device, for sent MMS message. An amount charged by the billing system may be based on the roaming status of the first user device at the time at which MMS message are sent by the first user device.

Abstract: A method includes receiving, at a network device in a shared network that includes a plurality of PLMNs, a request from an inbound roaming user device to connect to a home network of the inbound roaming user device. The method also includes identifying, by the network device, a PLMN selected by the inbound roaming user device, and accessing a listing of allowed PLMNs and disallowed PLMNs for roaming in the shared network. The method includes determining whether the selected PLMN is an allowed PLMN and blocking the connection to the home network in response to a determination that the selected PLMN is not an allowed PLMN.

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.