1. Field of the Invention
The present invention relates generally to caller identification systems. More specifically, it relates to a post-page caller name identification system that bridges SS7 retrievable caller data with a user-accessible IP interface. Carrier implementation of caller name identification has become increasingly complicated due to the fragmentation of service providers on the North American Public-Switched Telephone Network (PSTN). The present invention restores functionality of this important SS7/PSTN capability, caller name identification, to the increasing number of telecommunications end-users left without this feature.
2. Description of the Prior Art
To place a call using the earliest long-distance telephone systems, a calling party initiated a request with the local switchboard operator. The calling party's local operator would connect to the inward operator, and specify the called party. The inward operator would identify the calling party to the called party, then coordinate the completed telephone circuit with the originating local operator.
Direct dial systems using automated protocols over the Public Switched Telephone Network eventually phased out the operator switchboard system by the 1960's. Unlike the system utilizing human operators, the direct dial networks did not readily identify the calling party to the called party. The relative anonymity of automated PSTN systems created both inconvenience and the potential for abuse. The invention of what became known as caller identification addressed these shortfalls. Between 1969 and 1975, Mr. Theodore Paraskevakos successfully claimed twenty separate patents related to automatic telephone line identification. By 1989, Bell Atlantic, BellSouth, and U.S. West Communications had implemented caller identification in their consumer service offerings.
Caller identification, or Caller ID, may colloquially refer to the presentation of either the calling party's telephone number, or name, to the called party. The initial caller identification systems transmitted only the calling party's phone number to the called party. By their rollout in the late 1980's, or shortly thereafter, the “Baby Bell” Caller ID service offerings typically included both CID and CNAM functionality. These services grew in popularity, with tens of millions of subscribers by the late 1990's. For this specification, caller identification, or CID, refers to the presentation of the calling party's phone number to the called party. Caller name identification, or CNAM Caller ID, shall refer to the presentation of the calling party's name to the called party.
The technical protocols for Caller ID evolved since Mr. Paraskevakos' invention, to what is now industry-standard implementation over the PSTN SS7 network. Despite the standardization of the protocol, telephone line portability deregulation significantly increased the complexity and cost of a CNAM Caller ID query. CNAM information previously held in a few databases of the Baby Bells increased to hundreds, if not thousands, of databases operated by the emerging telephone companies.
At the time of filing, a complete CID & CNAM Caller ID query typically involved the following steps: 1) the CID is transmitted from the calling party to the called party during SS7 call circuit provisioning (the network “page”), 2) a Global Title Translation (GTT) is initiated from the called party's SS7 signaling transfer point (STP) to determine which CNAM database and telephone carrier represents the calling party CID, 3) a GR-1188 CNAM query is relayed via SS7 to the service control point (SCP) for the respective CNAM database, and 4) the GR-1188 CNAM query result is presented to the called party. The exact sequence of events may vary depending upon the called and calling party's intercarrier agreements and SS7 implementation. Characteristic of the prior art implementations, the entire sequence of events takes place during the ringing or network page, and prior to the call completion.
As mobile phones and voice-over-IP telephony (VOIP) proliferated over the past decade, many providers never implemented full CNAM Caller ID to their mobile or VOIP end-users. Those that did implement CNAM Caller ID usually charge a monthly fee for CNAM Caller ID. For example, a major American wireless carrier recently began offering “Caller Name ID” as a premium monthly feature. Furthermore, individuals now may own several phone numbers, including a home land-line, a personal cellular mobile, and a VOIP line at work. Subscribing to a monthly CNAM service on multiple lines, if the feature is even available, is costly. As a result, CNAM Caller ID prevalence is trending backwards.
In view of the foregoing limitations inherent in the known types of caller identification systems present in the prior art, the present invention provides a post-page caller name identification system. This standalone system may function for multiple telephone devices owned or operated by the end-user. The system is independent of the end-user's carrier implementation (or lack thereof) of CNAM Caller ID.
The utility of the present invention, which shall be described subsequently in greater detail, is to identify the calling party's name when only the CID is known. This is typically the case with most modern cellular mobile and VOIP systems. The present invention's post-page functionality complements the prior art. In an ideal telephony network, CNAM Caller ID would be transmitted during the page, or ring. As described above, CNAM implementation has been declining for a decade due to increasing complexity of carriers. This necessitates the present invention as the next-best solution for an end-user wishing to identify a calling party.
To attain this, the present invention comprises a system that interfaces the user directly with the calling party's SS7 SCP-connected CNAM database. After a call or page terminates, the user accesses the present invention via the user terminal, which may operate on a mobile phone application or via direct HTML web access. The user inputs the CID information relayed from the calling party to the end-user. The system then performs a Global Title Translation (GTT) query using its SS7 node. The GTT lookup returns the respective phone carrier and CNAM database applicable to the CID. The system then performs a GR-1188 CNAM query via SS7 to the service control point (SCP) for the respective CNAM database. Finally, the CNAM query result is presented on the user-interface.
By utilizing the present invention, the end-user consolidates CNAM services and enjoys significant cost savings. At time of filing, a commercial implementation of the present invention was offered free-of-charge to the user via either a smartphone applications or direct web access. As stated above, the CNAM functionality offered by the present invention is often unavailable, even as a premium service, on many VOIP and cellular carriers.
The calling party may opt-out from this process at three points. First, the calling party may opt-out from CID transmission on a per-call basis, which is typically known as “*67 Caller ID Block.” Second, the calling party may inform his/her carrier to remove his information from their CNAM database. Third, the calling party may opt-out using a form implemented on the privacy policy page of the present invention.
Features of the exemplary implementations of the invention will become apparent from the description, the claims, and the drawings in which:
From
Having understood the possible combinations of CID and/or CNAM presentations possible on a caller identification system,
The end-user initiates use of the system by accessing the user terminal. The user enters the CID from (2) into the CID entry field (3) of the user terminal. After entering a valid CID, the user (4) submits the query to the system. The system then initiates the “CNAM database query” (5) via the SS7 network.
There exist several methodologies to obtain a CNAM database result via SS7, and the exact implementation depends upon the calling party's carrier, the system's carrier, and any contractual relationships between the two carriers. Exemplified in
Upon successful CNAM database query, the CNAM Caller ID is relayed back to the user terminal. The caller name identification is displayed on the appropriate user interface element, thereby completing the process.
The system then instructs the SS7 interfacing node to initiate an SS7 session, if one is not already active (103). The exact state or instructions relayed to the SS7 switch/node varies depending upon carrier implementation. Once the SS7 session is active, a Global Title Translation (GTT) is performed using the CID from the CID entry interface. (104). The GTT returns the calling party carrier information necessary to locate the carrier's CNAM database on the SS7 network. A query is thereafter sent, usually via the GR-1188 protocol, to the signal control point (SCP) for the calling carrier CNAM database (105). Assuming the calling party didn't opt-out from its carrier CNAM database, the calling party's CNAM is returned to the system's SS7 node (106). Then, the CNAM database query result is displayed on the user interface (107).
Number | Name | Date | Kind |
---|---|---|---|
5457738 | Sylvan | Oct 1995 | A |
5903636 | Malik | May 1999 | A |
6782086 | Clapper | Aug 2004 | B2 |
6954526 | Glenn | Oct 2005 | B1 |
7308408 | Stifelman | Dec 2007 | B1 |
7839987 | Kirchhoff | Nov 2010 | B1 |
8155287 | Woodring | Apr 2012 | B2 |
8358766 | Denenberg | Jan 2013 | B1 |
8447285 | Bladon | May 2013 | B1 |
8625762 | White et al. | Jan 2014 | B1 |
8644470 | Gosselin | Feb 2014 | B2 |
8699682 | Nguyen | Apr 2014 | B2 |
9641663 | Rincon | May 2017 | B2 |
20020099720 | Bansal | Jul 2002 | A1 |
20080037764 | Lee | Feb 2008 | A1 |
20080052372 | Weber | Feb 2008 | A1 |
20080147771 | Bertolino | Jun 2008 | A1 |
20080222144 | Backer et al. | Sep 2008 | A1 |
20080240383 | Fronczak et al. | Oct 2008 | A1 |
20090158367 | Myers | Jun 2009 | A1 |
20090257575 | Gosselin | Oct 2009 | A1 |
20090328118 | Ravishankar et al. | Dec 2009 | A1 |
20100254524 | Kim | Oct 2010 | A1 |
20110013755 | Martino | Jan 2011 | A1 |
20110081911 | Silver | Apr 2011 | A1 |
20130287196 | Zerillo | Oct 2013 | A1 |
Entry |
---|
Kessler, “In Apps For Mobile Advertising, Brands Pay You To Listen” fastcompany.com, Sarah Kessler, Aug. 15, 2013, (pp. 1-10) (Hereinafter Kessler). |
3:16-cv-00175-RS Greenflight Venture Corporation et al. v. Whitepages, Inc. et., “Order Granting Defendant's Motion for Judgment on the Pleadings,” issued on Jul. 25, 2016. |
3:16-cv-00175-RS Greenflight Venture Corporation et al. v. Whitepages, Inc. et., “Order Denying Applicant's Motion For Reconsideration,” issued on Aug. 16, 2016. |
Zhang, “The Line Information Database (LIDB) and Wireless Services,” Telcordia Technologies, Inc., White Paper Analysis, Dec. 2001. |
“OSSGR Section 22.3: Line Information Database,” Telcordia, Apr. 2009, Issue 8 (GR-1158). |
3:16-cv-00175-RS Greenflight Venture Corporation et al. v. Whitepages, Inc. et., “Defendant Whitepages, Inc.'s Reply in Support of Its Motion for Judgment on the Pleadings of Invalidity under 35 USC 101,” filed on Jun. 13, 2016. |
3:16-cv-00175-RS Greenflight Venture Corporation et al. v. Whitepages, Inc. et., “Whitepages, Inc.'s Opposition to Defendants' Motion for Reconsideration,” filed on Aug. 9, 2016. |
3:16-cv-00175-RS Greenflight Venture Corporation et al. v. Whitepages, Inc. et., “Defendant Whitepages, Inc.'s Notice of Motion and Motion for Judgment on the Pleadings of Invalidity under 35 USC 101,” filed on May 23, 2016. |
3:16-cv-00175-RS Greenflight Venture Corporation et al. v. Whitepages, Inc. et., “Defendants Greenflight Venture Corporation and Jeffrey Isaacs' Opposition to Motion for Judgment on the Pleadings of Invalidity under 35 USC 101,” filed on Jun. 6, 2016. |
3:16-cv-00175-RS Greenflight Venture Corporation et al. v. Whitepages, Inc. et., “Defendants' Notice of Motion and Motion for Leave to File Motion for Reconsideration,” filed on Jul. 29, 2016. |
Number | Date | Country | |
---|---|---|---|
Parent | 14174724 | Feb 2014 | US |
Child | 15289905 | US |