Abstract:
A system may be configured to receive a request for emergency contact information associated with a first user. The request may include information identifying the first user. The system may further determine a geographic location of the first user; and identify a second user. The identifying may be based on at least one of an amount or frequency of communication between the first user and the second user, or a geographical proximity of the first user to the second user. The system may additionally identify contact information associated with the second user; and output, to a device from which the request was received, the contact information associated with the second user.
Abstract:
A system for and method of for detecting a non-functional battery back-up unit (BBU) of an optical network terminal is presented. The system and method may include receiving power outage data associated with a plurality of customer sites, receiving, from each of the plurality of customer sites, discharge time data associated with a battery via a network, calculating a mean discharge time based on the discharge time data, comparing the discharge time data associated with each battery to the mean discharge time, determining that each battery that is associated with discharge time data that indicates a discharge time value that is less than the mean discharge time is faulty, and outputting a data signal that indicates that a battery is faulty.
Abstract:
A device may receive information that identifies a failover configuration associated with a user device. The failover configuration may identify a backup user device. The device may receive information indicating that a failover condition, identified in the failover configuration, has been satisfied. The device may identify the backup user device based on receiving the information indicating that the failover condition has been satisfied. The device may contact the backup user device based on identifying the backup user device. The device may determine that a service request, associated with a service and intended for the user device, is to be forwarded to the backup user device based on contacting the backup user device. The service may be identified by the failover configuration. The device may forward the service request to the backup user device to permit the backup user device to obtain the service rather than the user device.
Abstract:
A network device receives a message that identifies a relationship between a first user device and a second user device, the relationship permitting status information of the first user device to be sent to the second user device when the first user device is communicating with a third user device. The network device receives the status information relating to a communication involving the first user device. The network device determines to send the status information to the second user device, based on the information identifying the relationship stored by the network device; and the network device sends the status information for presentation on the second user device.
Abstract:
A system for and method of for detecting a non-functional battery back-up unit (BBU) of an optical network terminal is presented. The system and method may include receiving power outage data associated with a plurality of customer sites, receiving, from each of the plurality of customer sites, discharge time data associated with a battery via a network, calculating a mean discharge time based on the discharge time data, comparing the discharge time data associated with each battery to the mean discharge time, determining that each battery that is associated with discharge time data that indicates a discharge time value that is less than the mean discharge time is faulty, and outputting a data signal that indicates that a battery is faulty.
Abstract:
A device may receive information that identifies a failover configuration associated with a user device. The failover configuration may identify a backup user device. The device may receive information indicating that a failover condition, identified in the failover configuration, has been satisfied. The device may identify the backup user device based on receiving the information indicating that the failover condition has been satisfied. The device may contact the backup user device based on identifying the backup user device. The device may determine that a service request, associated with a service and intended for the user device, is to be forwarded to the backup user device based on contacting the backup user device. The service may be identified by the failover configuration. The device may forward the service request to the backup user device to permit the backup user device to obtain the service rather than the user device.
Abstract:
A mobile device stores a service-creation application and presents, via the service-creation application, a user interface to solicit a service definition for client mobile devices. The mobile device stores a service-engine for providing the service and announces availability of the service to the client mobile devices. The mobile device receives, in response to the announcing, a registration request from one of the client mobile devices and validates the registration request. The mobile device then provides, to the one of the client mobile devices, the service via the service engine.
Abstract:
A mobile device stores a service-creation application and presents, via the service-creation application, a user interface to solicit a service definition for client mobile devices. The mobile device stores a service-engine for providing the service and announces availability of the service to the client mobile devices. The mobile device receives, in response to the announcing, a registration request from one of the client mobile devices and validates the registration request. The mobile device then provides, to the one of the client mobile devices, the service via the service engine.
Abstract:
A system may be configured to receive a request for emergency contact information associated with a first user. The request may include information identifying the first user. The system may further determine a geographic location of the first user; and identify a second user. The identifying may be based on at least one of an amount or frequency of communication between the first user and the second user, or a geographical proximity of the first user to the second user. The system may additionally identify contact information associated with the second user; and output, to a device from which the request was received, the contact information associated with the second user.