Abstract: This disclosure is directed to performing diagnostics on deployed devices that use network connectivity to transmit data in response to at least partially automated processes. In some embodiments, a diagnostic entity may monitor network traffic from deployed devices. The diagnostic entity may aggregate at least some of the network traffic to create profiles for at least some of the deployed devices and/or for some activities. The diagnostic entity may then identify outlier devices/activities from observed network behavior of deployed devices and/or activities based on the accessed network traffic and the profiles. The diagnostic entity may generate reports and/or perform or cause some corrective operations in response to identification of the outliers. In various embodiments, the diagnostic entity may predict network usage information for a group of devices and may possibly suggest revisions to service plans and/or usage of the deployed devices based at least partly on the predicted usage.

Abstract: This disclosure is directed to performing diagnostics on deployed devices that use network connectivity to transmit data in response to at least partially automated processes. In some embodiments, a diagnostic entity may monitor network traffic from deployed devices. The diagnostic entity may aggregate at least some of the network traffic to create profiles for at least some of the deployed devices and/or for some activities. The diagnostic entity may then identify outlier devices/activities from observed network behavior of deployed devices and/or activities based on the accessed network traffic and the profiles. The diagnostic entity may generate reports and/or perform or cause some corrective operations in response to identification of the outliers. In various embodiments, the diagnostic entity may predict network usage information for a group of devices and may possibly suggest revisions to service plans and/or usage of the deployed devices based at least partly on the predicted usage.

Abstract: Voice Over Internet Protocol (VoIP) devices are invited to a conference bridge based on a pre-defined criteria for the conference bridge (e.g., passengers on a plane. The conference invite messages are transmitted using Internet Protocol, which they may or may not accept. The invited VoIP users may be determined based on their physical proximity to the initial caller and other pre-determined characteristics. A VoIP soft switch includes conference bridges that eliminate the conventional requirement that they dial the phone number of another specific VoIP communications device. Instead, location information relating to the initial VoIP user is passed to the VoIP conference bridge, either from the user's VoIP communication device or from their respective location server. Location and other information is then compared by the VoIP soft switch against other VoIP devices, to find potential VoIP conference participants.

Abstract: Voice Over Internet Protocol (VoIP) emergency calls to an Emergency Response Center (ERC) are handled through a VoIP conference bridge on a VoIP service provider's soft switch. The soft switch works with a VoIP positioning center (VPC) to obtain location information, which is compared against a PSAP database to find an initial best-appropriate PSAP for the location of the emergency caller. The PSAP is issued an Invite message to join the conference, establishing an emergency call. Third parties such as police, ambulance may be issued Invite messages to join the conference. Cold transfers are avoided by Inviting participants to join a single emergency conference rather than passing an emergency call from party to party (e.g., from PSAP to police to ambulance, etc.) The PSAP, other emergency responders, and even the initial VoIP emergency caller may leave and rejoin the VoIP conference without dropping the conference between the others.

Abstract: Voice Over Internet Protocol (VoIP) emergency calls to an Emergency Response Center (ERC) are handled through a VoIP conference bridge on a VoIP service provider's soft switch. The soft switch works with a VoIP positioning center (VPC) to obtain location information, which is compared against a PSAP database to find an initial best-appropriate PSAP for the location of the emergency caller. The PSAP is issued an Invite message to join the conference, establishing an emergency call. Third parties such as police, ambulance may be issued Invite messages to join the conference. Cold transfers are avoided by Inviting participants to join a single emergency conference rather than passing an emergency call from party to party (e.g., from PSAP to police to ambulance, etc.) The PSAP, other emergency responders, and even the initial VoIP emergency caller may leave and rejoin the VoIP conference without dropping the conference between the others.

Abstract: Voice Over Internet Protocol (VoIP) emergency calls to an Emergency Response Center (ERC) are handled through a VoIP conference bridge on a VoIP service provider's soft switch. The soft switch works with a VoIP positioning center (VPC) to obtain location information, which is compared against a PSAP database to find an initial best-appropriate PSAP for the location of the emergency caller. The PSAP is issued an Invite message to join the conference, establishing an emergency call. Third parties such as police, ambulance may be issued Invite messages to join the conference. Cold transfers are avoided by Inviting participants to join a single emergency conference rather than passing an emergency call from party to party (e.g., from PSAP to police to ambulance, etc.) The PSAP, other emergency responders, and even the initial VoIP emergency caller may leave and rejoin the VoIP conference without dropping the conference between the others.

Abstract: A system and method are provided for controlling the computing bandwidth and resources provided to external entities based on subscription levels associated with those external entities. Higher subscription levels provide greater resource allocation. Accounting is accomplished by tracking bandwidth allocated and used over given periods of time.

Abstract: The function of determination of location is separated from the function of gathering information based on determined location by use of a Location Object (LO) proxy between an initiating VoIP capable device and a positioning center. The LOProxy queries an appropriate location database using a location key, and injects a PIDF-LO into a routing SIP message otherwise without location. A SIP request without location is received from a VoIP capable device. The SIP request contains messages indicating the type of location generator or service needed. A location key (like a telephone number or SIP URI), in addition to the type of location generator or service needed, is included in a SIP request. A location object (LO) broker may be used between a routing SIP message and a positioning center to direct a routing SIP message to an appropriate one of a plurality of location object (LO) proxies.

Abstract: The function of determination of location is separated from the function of gathering information based on determined location by use of a Location Object (LO) proxy between an initiating VoIP capable device and a positioning center. The LOProxy queries an appropriate location database using a location key, and injects a PIDF-LO into a routing SIP message otherwise without location. A SIP request without location is received from a VoIP capable device. The SIP request contains messages indicating the type of location generator or service needed. A location key (like a telephone number or SIP URI), in addition to the type of location generator or service needed, is included in a SIP request. A location object (LO) broker may be used between a routing SIP message and a positioning center to direct a routing SIP message to an appropriate one of a plurality of location object (LO) proxies.

Abstract: The function of determination of location is separated from the function of gathering information based on determined location by use of a Location Object (LO) proxy between an initiating VoIP capable device and a positioning center. The LOProxy queries an appropriate location database using a location key, and injects a PIDF-LO into a routing SIP message otherwise without location. A SIP request without location is received from a VoIP capable device. The SIP request contains messages indicating the type of location generator or service needed. A location key (like a telephone number or SIP URI), in addition to the type of location generator or service needed, is included in a SIP request. A location object (LO) broker may be used between a routing SIP message and a positioning center to direct a routing SIP message to an appropriate one of a plurality of location object (LO) proxies.