IP Library Granted Patent US 9,137,342
Granted Patent B2
US 9,137,342 · App. 13/591,962 · Granted Sep 15, 2015

Automatic contact population

Inventors: Peter M Hillier (Kanata, CA); Kenneth Armstrong (Woodlawn, CA)
Assignee: Mitel Networks Corporation
H04M1/274516H04M1/56H04M3/42093H04M3/46H04M7/128H04W88/06H04M1/2535H04M1/274508H04M1/274575H04M1/274583H04M1/575H04M3/4931
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 9,137,342
App. No.
13/591,962
Granted
Sep 15, 2015
Kind
B2
Abstract

Systems and methods for populating a contacts directory are disclosed. A method of populating a contacts directory associated with a telephonic device includes placing a call from a first telephonic device to a second telephonic device. Called party contact information associated with the second telephonic device can be received and stored automatically in the contacts directory as a contact.

Claims (34)

1. A method of populating a contacts directory associated with a telephonic device, comprising:

placing a call from a first telephonic device to a second telephonic device;

receiving called party contact information associated with the second telephonic device; and

storing the called party contact information automatically in the contacts directory as a contact, wherein receiving the called party contact information associated with the second telephonic device comprises receiving the called party contact information at a third telephonic device inactively engaged in the call and different from the first and second telephonic devices, and storing the called party contact information comprises automatically storing the called party contact information as a contact on the third telephonic device.

2. The method of claim 1 , wherein placing the call comprises placing the call over a private branch exchange (PBX) network.

3. The method of claim 1 , wherein storing the called party contact information as a contact comprises:

storing the called party contact information as a new contact when a contact for a called party at the second telephonic device does not already exist; or

storing the called party contact information to an existing contact when a contact for the called party at the second telephonic device already exists and the called party contact information is more than cumulative of information stored for the contact.

4. The method of claim 1 , further comprising tagging the contact with a label associated with a network over which the call is placed.

5. The method of claim 1 , wherein the call from the first telephonic device to the second telephonic device is placed through the third telephonic device, the method further comprising transferring the call from the third device to the second device to receive the called party contact information associated with the second telephonic device.

6. The method of claim 1 , wherein the call from the first telephonic device to the second telephonic device is placed over a private branch exchange (PBX) network and the called party contact information includes a public switched telephone network (PSTN) phone number associated with a PBX phone number in a ring group used to place the call.

7. The method of claim 1 , wherein the called party contact information includes contact information for multiple different contact methods.

8. The method of claim 1 , wherein availability of the contact for placing a second call is dependent on a network to which the first telephonic device is connected.

9. The method of claim 1 , further comprising prioritizing the contact among other contacts based on frequency of calls to the contact.

10. The method of claim 1 , further comprising adding additional profile information to the called party contact information when creating the contact based on a rule stored in the first telephonic device to enable use of the contact across multiple different types of telephone networks.

11. The method of claim 1 , wherein the called party contact information includes other information in addition to a name and phone number of a called party.

12. A system for populating a contacts directory associated with a telephonic device, comprising:

a telephonic device configured to connect to a telephone network;

a contacts directory associated with the telephonic device;

a contact generation module associated with the telephonic device, and being configured to receive party contact information associated with a party through the telephone network, and store the party contact information automatically in the contacts directory as a contact;

a network identification module operable to identify the type of said telephone network;

a tagging module configured to tag the contact based on the identified telephone network to enable selective availability of the contact information depending on the availability of the telephone network; and

a graphical user interface to enable selective availability of the contact information depending on the availability of the telephone network by visually differentiating numbers on networks not currently accessible to the telephonic device.

13. The system of claim 12 , further comprising a second telephonic device configured to connect to the telephone network and to receive a call placed over the telephone network when transferred from the telephonic device, the contact generation module being on the second telephonic device and operable to store the party contact information as the contact in the contacts directory on the second telephonic device.

14. The system of claim 12 , wherein the network identification module operable to add additional profile information to the party contact information when creating the contact based on a rule stored in the telephonic device to enable use of the contact across multiple different types of telephone networks when identification of the telephone network triggers the rule.

15. A method of populating a contacts directory associated with a telephonic device, comprising:

receiving a phone call at the telephonic device;

identifying calling party contact information received in connection with the phone call;

storing the calling party contact information automatically in the contacts directory as a contact;

tagging the contact with a label associated with a network over which the call was received, wherein the availability of the calling party for placing a call is dependent on a network to which the telephonic device is connected; and

using a graphical user interface of the telephonic device to enable selective availability of the calling party contact information depending on the availability of the network over which the call was received by visually differentiating numbers on networks not currently accessible to the telephonic device.

16. The method as in claim 15 , wherein the phone call is received over a private branch exchange (PBX) network.

17. The method as in claim 15 , wherein the phone call is received over a public switched telephone network (PSTN).

18. The method of claim 15 , wherein the calling party contact information includes other information in addition to a name and phone number of the calling party.

Assignments (25)
SECURITY INTEREST Recorded Jun 30, 2025
From: MLN US HOLDCO LLC; MITEL (DELAWARE), INC.; MITEL NETWORKS CORPORATION; MITEL NETWORKS, INC.
To: U.S. PCI SERVICES, LLC
Reel/Frame 071758/0843 →
RELEASE OF SECURITY INTEREST Recorded Jun 24, 2025
From: ANKURA TRUST COMPANY, LLC
To: MITEL (DELAWARE), INC.; MITEL COMMUNICATIONS, INC.; MITEL CLOUD SERVICES, INC.; MITEL NETWORKS, INC.; MITEL NETWORKS CORPORATION
Reel/Frame 071722/0721 →
RELEASE OF SECURITY INTEREST Recorded Jun 24, 2025
From: ACQUIOM AGENCY SERVICES LLC
To: MITEL (DELAWARE), INC.; MITEL NETWORKS, INC.; MITEL NETWORKS CORPORATION
Reel/Frame 071730/0632 →
RELEASE OF SECURITY INTEREST Recorded Jun 24, 2025
From: WILMINGTON SAVINGS FUND SOCIETY, FSB
To: MITEL (DELAWARE), INC.; MITEL COMMUNICATIONS, INC.; MITEL NETWORKS, INC.; MITEL NETWORKS CORPORATION
Reel/Frame 071712/0821 →
SECURITY INTEREST Recorded Jun 20, 2025
From: MITEL (DELAWARE), INC.; MITEL NETWORKS CORPORATION; MITEL NETWORKS, INC.
To: ACQUIOM AGENCY SERVICES LLC
Reel/Frame 071676/0815 →
SECURITY INTEREST Recorded Mar 12, 2025
From: MITEL (DELAWARE), INC.; MITEL NETWORKS CORPORATION; MITEL NETWORKS, INC.
To: ACQUIOM AGENCY SERVICES LLC
Reel/Frame 070689/0857 →
NOTICE OF SUCCESSION OF AGENCY - 5L Recorded Jan 14, 2025
From: UBS AG, STAMFORD BRANCH, AS LEGAL SUCCESSOR TO CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
To: ANKURA TRUST COMPANY, LLC
Reel/Frame 069897/0046 →
NOTICE OF SUCCCESSION OF AGENCY - 3L Recorded Jan 14, 2025
From: UBS AG, STAMFORD BRANCH, AS LEGAL SUCCESSOR TO CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
To: WILMINGTON SAVINGS FUND SOCIETY, FSB
Reel/Frame 070006/0268 →
NOTICE OF SUCCCESSION OF AGENCY - 2L Recorded Jan 14, 2025
From: UBS AG, STAMFORD BRANCH, AS LEGAL SUCCESSOR TO CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
To: WILMINGTON SAVINGS FUND SOCIETY, FSB
Reel/Frame 069896/0001 →
NOTICE OF SUCCCESSION OF AGENCY - PL Recorded Jan 14, 2025
From: UBS AG, STAMFORD BRANCH, AS LEGAL SUCCESSOR TO CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
To: WILMINGTON SAVINGS FUND SOCIETY, FSB
Reel/Frame 069895/0755 →
NOTICE OF SUCCESSION OF AGENCY - 4L Recorded Jan 14, 2025
From: UBS AG, STAMFORD BRANCH, AS LEGAL SUCCESSOR TO CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
To: ANKURA TRUST COMPANY, LLC
Reel/Frame 069896/0827 →
SECURITY INTEREST Recorded Oct 31, 2022
From: MITEL NETWORKS CORPORATION
To: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT
Reel/Frame 061824/0282 →
SECURITY INTEREST Recorded Dec 7, 2018
From: MITEL NETWORKS ULC
To: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT
Reel/Frame 047741/0674 →
SECURITY INTEREST Recorded Dec 7, 2018
From: MITEL NETWORKS ULC
To: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT
Reel/Frame 047741/0704 →
RELEASE OF SECURITY INTEREST Recorded Dec 3, 2018
From: CITIZENS BANK, N.A.
To: MITEL NETWORKS CORPORATION
Reel/Frame 048096/0785 →
RELEASE OF SECURITY INTEREST Recorded Mar 25, 2017
From: BANK OF AMERICA, N.A., AS COLLATERAL AGENT; BANK OF AMERICA, N.A., (ACTING THROUGH ITS CANADA BRANCH), AS CANADIAN COLLATERAL AGENT
To: MITEL US HOLDINGS, INC.; MITEL NETWORKS CORPORATION; MITEL (DELAWARE), INC.; MITEL NETWORKS, INC.; MITEL COMMUNICATIONS, INC.; MITEL BUSINESS SYSTEMS, INC.
Reel/Frame 042244/0461 →
SECURITY INTEREST Recorded Mar 23, 2017
From: MITEL NETWORKS CORPORATION
To: CITIZENS BANK, N.A.
Reel/Frame 042107/0378 →
SECURITY INTEREST Recorded May 28, 2015
From: MITEL NETWORKS CORPORATION
To: BANK OF AMERICA, N.A.(ACTING THROUGH ITS CANADA BRANCH), AS CANADIAN COLLATERAL AGENT
Reel/Frame 035783/0540 →
RELEASE OF SECURITY INTEREST Recorded May 1, 2015
From: JEFFERIES FINANCE LLC, AS THE COLLATERAL AGENT
To: MITEL US HOLDINGS, INC.; MITEL NETWORKS CORPORATION; MITEL COMMUNICATIONS INC. FKA AASTRA USA INC.
Reel/Frame 035562/0157 →
SECURITY AGREEMENT Recorded Feb 14, 2014
From: MITEL US HOLDINGS, INC.; MITEL NETWORKS CORPORATION; AASTRA USA INC.
To: JEFFERIES FINANCE LLC, AS THE COLLATERAL AGENT
Reel/Frame 032264/0760 →
RELEASE OF SECURITY INTEREST Recorded Feb 10, 2014
From: BANK OF AMERICA, N.A.
To: MITEL NETWORKS CORPORATION; MITEL US HOLDINGS, INC.
Reel/Frame 032210/0245 →
RELEASE OF SECURITY INTEREST Recorded Feb 7, 2014
From: WILMINGTON TRUST, NATIONAL ASSOCIATION
To: MITEL NETWORKS CORPORATION; MITEL US HOLDINGS, INC.
Reel/Frame 032176/0818 →
SECURITY INTEREST Recorded Apr 8, 2013
From: MITEL NETWORKS CORPORATION
To: WILMINGTON TRUST, N.A., AS SECOND COLLATERAL AGENT
Reel/Frame 030201/0743 →
SECURITY AGREEMENT Recorded Apr 8, 2013
From: MITEL NETWORKS CORPORATION
To: BANK OF AMERICA, N.A., AS COLLATERAL AGENT
Reel/Frame 030186/0894 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 22, 2012
From: HILLIER, PETER MATTHEW; ARMSTRONG, KEN
To: MITEL NETWORKS CORPORATION
Reel/Frame 028832/0460 →
Continuity (1)
Related Publication 20140057608A1 · Feb 27, 2014