Verizon Patent and Licensing Inc.

Cellco Partnership

Verizon Services Corporation

Jeffrey R Evans

Priscilla Lau

Mingxing Li

John Herman Wurster

Susan M Middleswarth

Euclid S Brooks

Nashwa F Sidhom

Henry L Tam

Lawrence J Fronczak

Yi Jing

Gaurav B Patel

Gunjan Thakkar

Taral Patel

Tim Dalrymple

Robert P Faber, Jr

A method may include receiving, at an application server, a session initiation protocol (SIP) message including a public user identifier (ID) associated a user. The public user ID corresponds to a plurality of user devices. The method also includes determining an applicable order of alerting at least one of the plurality of user devices. The method further includes identifying at least one available user device associated with the user, based on a terminal identifier (ID) associated with each at least one available user device. The method also includes selecting a user device from the at least one available user device based on the applicable order of alerting. A SIP invite message, including a terminal ID for the selected user device, is generated. The method includes sending the SIP invite message to the selected user device based on the applicable order of alerting, and receiving a response to the SIP invite message.

User device selection

A device may receive a first session initiation protocol (SIP) message from another device, and may determine a first timestamp associated with the first SIP message. The first timestamp may represent a receipt time of the first SIP message by the device. The device may determine a second timestamp associated with a second SIP message. The second timestamp may represent a transmission time of the second SIP message by the device, and may be a response to the first SIP message. The device may determine a device latency value representing a difference between the second timestamp and the first timestamp. The device may provide the second SIP message to the other device at the transmission time. The second SIP message may include the device latency value.

Measuring session initiation protocol (SIP) messaging latency

A network node receives a registration message, where the registration message is associated with registering a user equipment (UE) with a call signaling network for sending or receiving calls. The network node receives a notification message from a call session control node in the call signaling network, where the notification message indicates whether the UE is currently provisioned to engage in calls via a Voice over Long Term Evolution (VoLTE) network. The network node causes calls to or from the UE to be routed via the VoLTE network if the notification message indicates that the UE is currently provisioned to engage in calls via the VoLTE network, and causes calls to or from the UE to be routed via a legacy network, that is different than the VoLTE network, if the notification message indicates that the UE is currently not provisioned to engage in calls via the VoLTE network.

Determining correct device VoLTE status for call routing

A method may include receiving, at an application server, a session initiation protocol (SIP) message including a public user identifier (ID) associated a user. The public user ID corresponds to a plurality of user devices. The method also includes determining an applicable order of alerting at least one of the plurality of user devices. The method further includes identifying at least one available user device associated with the user, based on a terminal identifier (ID) associated with each at least one available user device. The method includes selecting a user device from the at least one available user device based on the applicable order of alerting. A SIP invite message, including a terminal ID for the selected user device, is generated. The method includes sending the SIP invite message to the selected user device based on the applicable order of alerting, and receiving a response to the SIP invite message.

A device receives information associated with a calling party, validates the calling party for an originating locator service based on the calling party information, and sends an instruction to play an announcement requesting information associated with a called party. The device also receives the called party information from the calling party in response to the announcement, and retrieves called party destination information based on the called party information. The device then sends an instruction to originate a sequence of calls to the called party based on the called party destination information.

Originating locator service

Emergency call backs may be placed to a user device in a manner that bypasses certain features (e.g., call forwarding) that may be enabled by the device. A method may include receiving an emergency call from a user device; and creating, in response to the emergency call, an emergency session associated with the user device, where the creating includes forwarding the call to a public safety access point (PSAP) server that handles emergency calls. The method may further include receiving a call, such as an emergency call back call, destined for the user device; determining that the emergency session has not expired when an elapse time associated with the emergency session is less than a threshold; and forwarding, to the user device, the call, as a return call from the PSAP server, based on the determination that the emergency session has not expired.

Enabling emergency call back to a user device

A system may receive a telephone call request for a Voice over Internet Protocol (VoIP) user. The telephone call request omits a name of a calling party. The system may further determine if the VoIP user has a calling party name feature enabled and obtaining, when the VoIP user has a calling party name feature enabled, the name of the calling party from a Public Switched Telephone Network (PSTN) based repository of calling party names.

Calling party name provisioning

A method and system are disclosed for providing a low cost mechanism for remotely re-routing queries in a telecommunications network. A service control point (SCP) executes an application which causes a queries to be launched over a LAN or WAN to a remotely located data center. A primary and secondary data center are defined, in which the secondary data center operations on a 'hot-standby' basis. Based on a manually provided indication, maintenance personnel may telephone and interact with a voice response unit or a web-based interface, which indicates that the SCP or SCP application should route queries to the secondary data center. Similarly, the same mechanism can be used to indicate that queries should be re-routed back to the primary data center. This allows remote management for controlling the queries without having to extensively modify the related infrastructure.

Systems and methods for using the advanced intelligent network to redirect data network traffic

A device receives, from a calling party, a call to a Voice over Internet Protocol (VoIP) subscriber, and generates a request for the calling party to record information. The device also receives information from the calling party based on the request, and provides the information from the calling party and call handling options to the VoIP subscriber. The device further receives a response from the VoIP subscriber to the call handling options, and handles the call based on the VoIP subscriber response.

Call intercept for voice over internet protocol (VoIP)

A device includes a traffic load profile containing information for regulating rates of routing calls and a controller. The controller may be configured to access the traffic load profile, obtain network calls from a traffic load producer, and route the network calls to a system under test based on the traffic load profile.

Controlling a test load throttle

A method may include receiving an Advanced Intelligent Network/Intelligent Network (AIN/IN) service request from a Voice over Internet Protocol (VoIP) subscriber, generating an IP-based message for invoking the AIN/IN service based on the AIN/IN service request, routing the IP-based message to an AIN/IN service control device via an IP signaling gateway, receiving an AIN/IN response from the AIN/IN service control device based on the IP-based message, and connecting the VoIP subscriber to the AIN/IN service based on the AIN/IN response.

VoIP-based invocation of PSTN-based AIN/IN services

Systems, methods, and computer program product are disclosed for providing a mechanism for re-routing queries in a telecommunications network. A service control point (SCP) executes an application which causes queries to be launched over a LAN or WAN to a remotely located data center. Primary and secondary data centers are defined, in which the secondary data center operates on a 'hot-standby' basis. Based on an automatically verifying system, the detection (or lack thereof) of a response from a primary data center and comparison of the response against an answer or response from another site indicates whether or not the SCP or SCP application should route queries to the secondary data center. Similarly, the same mechanism can be used to indicate that queries should be re-routed back to the primary data center.

Systems, methods, and computer program product for automatically verifying a standby site

A device receives information associated with a calling party, and validates the calling party for an originating simultaneous calls service based on the calling party information. The device also receives information associated with a called party, retrieves called party destination information based on the called party information, and sends an instruction to originate two or more simultaneous calls to the called party based on the called party destination information.

Growing community of inventors

Lovettsville, VA, United States of America

Jeffrey R Evans