Source: http://www.google.com/patents/US8144692?dq=6,304,975
Timestamp: 2015-01-27 18:21:24
Document Index: 375602302

Matched Legal Cases: ['application No. 2555567', 'Application No. 200580004362', 'application No. 2555567', 'application No. 200580004362', 'Application No. 200580004362', 'application No. 200580004362']

Patent US8144692 - Automation of IP phone provisioning with self-service voice application - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign inAdvanced Patent SearchPatentsApproaches for provisioning phones in packet voice networks are disclosed. One approach includes determining that an Internet Protocol (IP) phone has registered in a network; receiving a unique identifier of the IP phone; receiving identifying information about a user to be associated with the IP phone;...http://www.google.com/patents/US8144692?utm_source=gb-gplus-sharePatent US8144692 - Automation of IP phone provisioning with self-service voice applicationAdvanced Patent SearchPublication numberUS8144692 B2Publication typeGrantApplication numberUS 11/089,281Publication dateMar 27, 2012Filing dateMar 23, 2005Priority dateFeb 12, 2004Also published asCA2555567A1, CA2555567C, CN1918868A, CN1918868B, DE202005021044U1, EP1719311A1, EP1719311A4, US7673021, US20050180403, US20050198218, WO2005081479A1Publication number089281, 11089281, US 8144692 B2, US 8144692B2, US-B2-8144692, US8144692 B2, US8144692B2InventorsNajeeb Farhan Haddad, Laure F. Andrieux, Michael Edric Tasker, Jawhny Cooke, Fong ShenOriginal AssigneeCisco Technology, Inc.Export CitationBiBTeX, EndNote, RefManPatent Citations (40), Non-Patent Citations (12), Referenced by (1), Classifications (41), Legal Events (2) External Links: USPTO, USPTO Assignment, EspacenetAutomation of IP phone provisioning with self-service voice applicationUS 8144692 B2Abstract Approaches for provisioning phones in packet voice networks are disclosed. One approach includes determining that an Internet Protocol (IP) phone has registered in a network; receiving a unique identifier of the IP phone; receiving identifying information about a user to be associated with the IP phone; determining, based on the information provided, a user identifier; generating a configuration for the IP phone based on the user identifier that includes information such as phone number, feature sets, and other configuration parameters; and providing the configuration to the IP phone. Various approaches for determining a user identifier based on information provided by the user are disclosed.
receiving a voice sample from an individual user, wherein the individual user is to be associated with the IP phone;
determining an identity of the individual user based on said voice sample;
retrieving, based on the user identity, a phone number, feature set for the IP phone, and other configuration parameters associated with the individual user;
generating a configuration for the IP phone based on the user identity;
wherein generating the configuration comprises selecting a stored basic configuration for the IP phone based on the unique identifier of the IP phone and a user identifier, assigning the phone number, and assigning the feature set that is for the IP phone, to result in generating a final configuration that is specific to the IP phone;
providing the final configuration to the IP phone;
wherein providing the final configuration includes delivering the final configuration to the IP phone, rebooting the IP phone, and applying the final configuration to the IP phone;
2. A method as recited in claim 1, wherein the step of determining the identity of the individual user based on said voice sample further comprises the steps of:
receiving user identification information from a voice recognition system;
authenticating the user identification information; and
determining the user identifier from the user identification information.
3. A method as recited in claim 1, wherein the step of determining that an IP phone has registered in the network comprises the steps of requesting a call controller in the network to provide information about all IP phones that are known to the call controller, and wherein the step of receiving a unique identifier of the IP phone comprises receiving, from the call controller, a MAC address of each IP phone that is known to the call controller.
4. A method as recited in claim 1, further comprising the step of provisioning a call controller in the network with the final configuration.
5. A method as recited in claim 1, further comprising the steps of registering the IP phone at a call control system with a minimum configuration and a temporary number that is assigned from a pool of available numbers.
6. The method of claim 1, wherein the step of determining an identity of the individual user is based on the phone number used to call a call control center.
7. The method of claim 1, further comprising instructing the user how to associate the users identity with the IP phone, wherein instructions are delivered to the user in a voice mail message.
8. The method of claim 1, further comprising directing all calls from an uninitialized IP phone to a call control center, wherein an uninitialized IP phone is not yet associated with the user; and prompting the user to provide user identification information.
9. A method comprising the computer-implemented steps of:
assigning a unique temporary phone number to the IF phone;
retrieving, from a database of user information, a user record based on the user identity;
obtaining a user phone number from the user record;
obtaining, from the user record, a feature set for the IP phone, and other configuration parameters associated with the individual user;
wherein generating the configuration comprises selecting a stored basic configuration for the IP phone based on the media access control (MAC) address of the IP phone and a user identifier, assigning the user phone number, and assigning the feature set that is for the IP phone, to result in generating a final configuration that is specific to the IP phone;
10. A computer-readable volatile or non-volatile medium storing one or more sequences of instructions which, when executed by one or more processors, cause the one or more processors to perform the steps of:
wherein generating the configuration comprises selecting a stored basic configuration for the IP phone based on the unique identifier of the IP phone and a user identifier, assigning the phone number, and assigning the feature set that is for the IP phone, to result in generating a final configuration that is specific to the IP phone; and
wherein the instructions that cause providing the final configuration include instructions that cause delivering the final configuration to the IP phone, rebooting the IP phone, and applying the final configuration to the IP phone.
11. The computer-readable volatile or non-volatile medium of claim 10, wherein the instructions that cause determining the identity of the individual user based on said voice sample further comprise instructions which, when executed, cause:
12. The computer-readable volatile or non-volatile medium of claim 10,
wherein the instructions that cause determining that an IP phone has registered in a network, further comprise instructions which, when executed, cause requesting a call controller in the network to provide information about all IP phones that are known to the call controller, and
wherein the instructions that cause receiving a unique identifier of the IP phone, further comprise instructions which, when executed, cause receiving, from the call controller, a MAC address of each IP phone that is known to the call controller.
13. The computer-readable volatile or non-volatile medium of claim 10, further comprising instructions which when executed cause provisioning a call controller in the network with the final configuration.
14. The computer-readable volatile or non-volatile medium of claim 10, further comprising instructions which when executed cause registering the IP phone at a call control system with a minimum configuration and a temporary number that is assigned from a pool of available numbers.
15. A computer-readable volatile or non-volatile medium storing one or more sequences of instructions which, when executed by one or more processors, cause the one or more processors to perform the steps of:
wherein the instructions that cause providing the final configuration include instructions that cause delivering the final configuration to the IP phone, rebooting the IP phone, and applying the final configuration to the IP phone. Description
CROSS-REFERENCE TO RELATED APPLICATIONS; PRIORITY CLAIM This application is related to and claims domestic priority under 35 U.S.C. �120 as a Continuation-in-part of prior application Ser. No. 10/778,516, filed Feb. 12, 2004, �Automated Provisioning of Phones in Packet Voice Networks,� of Michael Tasker et al., the entire contents of which are hereby incorporated by reference as if fully set forth herein.
Call control systems are used to manage IP phones in VoIP networks. Commercial examples of call control systems include Cisco Call Manager and Call Manager Express on Cisco IOS� routers, commercially available from Cisco Systems, Inc., San Jose, Calif. A call control system identifies a phone by its Media Access Control (MAC) address, which is an identifier value that is assigned when the phone is manufactured and which is typically never changed. Dynamic IP addressing is typically used in VoIP networks, and call control systems typically include or can access a Dynamic Host Control Protocol (DHCP) server for assigning IP addresses.
DETAILED DESCRIPTION An approach for automated provisioning of IP phones in packet voice networks is described in co-pending application Ser. No. 10/778,516, filed Feb. 12, 2004, �Automated Provisioning of Phones in Packet Voice Networks,� of Michael Tasker et al, hereinafter the �Automated Provisioning application�, the contents of which have been incorporated by reference. As disclosed in the Automated Provisioning application, phone to user associations are determined automatically, and IP phones are provisioned automatically to facilitate large-scale deployment of IP phones.
1.0 General Overview 2.0 Structural and Functional Overview 3.0 Automated Provisioning of Phones in Packet Voice Networks 3.1 Automatically Determining an Association of Phone Identifier to User Identifier 3.2 User Identifier Information Provided By User 3.3 Automatically Provisioning Phone Based on User Identifier 3.4 Deployment in a Cisco Network 4.0 Implementation Mechanisms-Hardware Overview 5.0 Extensions and Alternatives 1.0 General Overview
In the following description, the term �phone� typically refers to an IP phone. However, any phone with a switch port, such as an Ethernet or USB port, and a display, may be used. A commercial example of an IP phone is the Cisco 7920 IP phone, although any kind of IP phone may be used.
The description herein of FIGS. 2A and 2B assumes that certain preliminary steps have occurred in the deployment of IP phones. For example, this description assumes that a service provider or customer orders IP phones from a manufacturing organization, which ships the phones directly to the customer site; that is, there is no requirement for a �staging area� or other pre-configuration point at which the IP phones are configured after manufacture but before deployment to the end user site or customer. The service provider also configures the call control system with a minimum configuration for each type of phone or for several types of phones, and a pool of phone numbers to be assigned. The pool comprises temporary numbers that may not correspond to the final numbers that are assigned to the phones on a generally permanent basis.
For example, for Cisco Catalyst� Ethernet switches and IP phones, CDP can be enabled to obtain this information. A provisioning system can query the CDP table of the switch, using a Simple Network Management Protocol (SNMP) query directed to the Cisco-CDP Management Information Base (CDP-MIB) to obtain neighboring device information. The cdpCacheTable of Cisco-CDP-MIB gives information about the type of connected device (e.g., router, switch, IP phone), device IP address, device hashKey, and MAC address.
When the user calls the IVR system, the IVR may use a calling line identification function (�Caller ID�) to determine and collect the calling number, which is the randomly generated phone number that was assigned at step 205. The IVR prompts the user to enter the user identifier and password from the e-mail. Alternatively, the IVR may prompt the user to enter a user identifier already known to the user. For example, the IVR may prompt the user to enter employee number, telephone extension number, or social security number.
The IVR system collects user identifier information from the user and authenticates the information. The user identifier information may include a user identifier and optional password. If an e-mail was used to provide user identifier information to the user, the IVR system will verify that a valid user identifier generated for the e-mail has been entered. If the e-mail also provided a password, or instructed the user as to a password to use, the IVR system will also verify that the correct user identifier and password combination was provided by the user. However, a password is not required. For example, in certain embodiments, use of a user identifier that should only be known by the user, such as his social security number, may be considered sufficiently secure to allow automatic provisioning of the phone. Typically, the customer ordering the IP phones can specify what user identifier information is needed to operate the IVR system and effect provisioning of the IP phones.
Patent CitationsCited PatentFiling datePublication dateApplicantTitleUS5633910 *Sep 13, 1994May 27, 1997Cohen; Kopel H.Outpatient monitoring systemUS5971854 *Sep 13, 1996Oct 26, 1999William Junkin TrustInteractive contest systemUS6185288 *Dec 18, 1997Feb 6, 2001Nortel Networks LimitedMultimedia call signalling system and methodUS6243443Feb 20, 1997Jun 5, 2001Hewlett-Packard CompanyMethod of making available content resources to users of a telephone networkUS6385583 *Aug 23, 2000May 7, 2002Motorola, Inc.Markup language for interactive services and methods thereofUS6678720 *Apr 10, 2000Jan 13, 2004Fujitsu LimitedChat system and method for delivering additional information via another independent networkUS6691155 *Jun 20, 2002Feb 10, 2004Linda GottfriedMultimedia system for sharing brand information keeps history of modifications of production information by consumers to allow recreating multimedia interface in its previous formatsUS6744759Sep 27, 1999Jun 1, 20043Com CorporationSystem and method for providing user-configured telephone service in a data network telephony systemUS6757363 *May 31, 2000Jun 29, 2004Cisco Technology, Inc.Method and apparatus for operating a telephone as an independent network clientUS6791970 *Sep 16, 1999Sep 14, 2004Mediaring Ltd.PC-to-phone for least cost routing with user preferencesUS6845499 *Jan 31, 2001Jan 18, 2005I2 Technologies Us, Inc.System and method for developing software applications using an extended XML-based frameworkUS6856616Nov 30, 2000Feb 15, 20053Com CorporationSystem and method for providing service provider configurations for telephones using a central server in a data network telephony systemUS6958992 *Mar 16, 2001Oct 25, 2005Mitel CorporationRegistering an IP phone with an IP phone switchUS6999458 *Feb 14, 2003Feb 14, 2006Theglobe.ComInternet telephony network and methods for using the sameUS7023989 *Jun 19, 2001Apr 4, 2006Cisco Technology, Inc.Arrangement for delivering applications to a network enabled telephony deviceUS7031288Dec 1, 2000Apr 18, 2006Sri InternationalReduced-overhead protocol for discovering new neighbor nodes and detecting the loss of existing neighbor nodes in a networkUS7278028 *Nov 5, 2003Oct 2, 2007Evercom Systems, Inc.Systems and methods for cross-hatching biometrics with other identifying dataUS20010037394 *Apr 25, 2001Nov 1, 2001Nec CorporationIP address assignment system and process method thereofUS20020064149 *Jun 14, 2001May 30, 2002Elliott Isaac K.System and method for providing requested quality of service in a hybrid networkUS20020131402Mar 16, 2001Sep 19, 2002Gordon LeeRegistering an IP phone with an IP phone switchUS20020150083 *Jul 11, 2001Oct 17, 2002Fangman Richard E.System and method for performing IP telephony including internal and external call sessionsUS20030055912 *Aug 17, 1998Mar 20, 2003Bruce K. MartinMethod and apparatus for controlling network connections based on destination locationsUS20030108172 *Mar 21, 2001Jun 12, 2003Petty Douglas T.Internet call waiting with voicemail system that provides monitoring during recordingUS20030135595 *Jan 3, 2002Jul 17, 2003Segelstein David J.Method of providing auto-registration of an IP telephony end-pointUS20030137991 *Jan 23, 2002Jul 24, 2003Doshi Parag M.Apparatus and method for enabling optimized gateway selection for inter-working between circuit-switched and internet telephonyUS20030217122Feb 28, 2003Nov 20, 2003Roese John J.Location-based access control in a data networkUS20030223403 *May 29, 2002Dec 4, 2003Richard HigginsMethod and apparatus for Voice-over IP services triggered by off-hook eventUS20040058710 *Jul 31, 2003Mar 25, 2004Timmins Timothy A.Technique for synchronizing data in user devices through an information serviceUS20040121813 *Dec 20, 2002Jun 24, 2004International Business Machines CorporationProviding telephone services based on a subscriber voice identificationUS20040156490 *Feb 7, 2003Aug 12, 2004Avaya Technology Corp.Methods and apparatus for routing and accounting of revenue generating calls using natural language voice recognitionUS20040180646 *Mar 10, 2003Sep 16, 2004Donley Christopher J.Authentication mechanism for telephony devicesUS20040260795 *Jun 6, 2003Dec 23, 2004Gentle Christopher ReonMethod and apparatus for determining telecommunication number based on presenceUS20040264665 *Jun 30, 2003Dec 30, 2004Idoni Michael A.Networkwide desk sharing with automatic device relocationUS20050008136 *Jul 8, 2003Jan 13, 2005Dobner Frank J.Portability of subscriber features in a telecommunication systemUS20050036663 *Aug 15, 2003Feb 17, 2005Rami CaspiSystem and method for secure bio-print storage and access methodsUS20050198218 *Feb 12, 2004Sep 8, 2005Michael TaskerAutomated provisioning of phones in packet voice networksUS20060013195 *May 30, 2003Jan 19, 2006Softbank Corp.Terminal connection device, connection control device, and multi-function telephone terminalUS20060258344 *Aug 22, 2003Nov 16, 2006Shao-Chun ChenMobile handset update package generator that employs nodes techniqueUS20090154681Feb 24, 2009Jun 18, 2009At&T Intellectual Property Ii, L.P.System with Call Forward ProfileKR20040010948A * Title not available* Cited by examinerNon-Patent CitationsReference12nd Office Action from CN for foreign patent application 200550004362.7 dated Jul. 20, 2010.2 *Alvin Ang. "IP Telephone". University of Queensland, Dept. of Information Technology and Electrical Engineering. Oct. 18, 2002.3CA Office Action for CA application serial No. 2555567, dated Aug. 26, 2010, (10 pgs).4Canadian Office Action for foreign patent application No. 2555567 dated Jan. 7, 2010.5Current claims for CA application serial No. 2555567.6Current Claims for CN OA Application No. 200580004362.7, (4 pages).7Current Claims in CA foreign patent application No. 2555567.8Current claims in CN for foreign patent application 200550004362.7.9Current claims in CN for foreign patent application No. 200580004362.7, dated Sep. 2011, 3 pages.10First Office Action, Chinese Patent Application No. 200580004362.7, dated Sep. 25, 2009, (8 pages) with English translation thereto (4 pages).11Office Action from CN for foreign patent application No. 200580004362.7 dated Sep. 21, 2011.12U.S. Appl. No. 10/778,516, filed Feb. 12, 2004, Supplemental Notice of Allowance, Jan. 22, 2010.* Cited by examinerReferenced byCiting PatentFiling datePublication dateApplicantTitleUS20100232423 *May 27, 2010Sep 16, 2010Hiroshi KodakaIp phone system and ip phone terminal registration method* Cited by examinerClassifications U.S. Classification370/352, 379/88.02, 370/420, 379/201.05, 379/15.04, 370/473, 370/395.3, 379/201.03, 370/474International ClassificationG06F15/173, H04M3/42, H04M3/22, G06F15/177, H04L12/56, H04M1/64, H04L12/28, G06F15/16, H04M1/24, H04L12/66, H04M3/08, H04J3/24Cooperative ClassificationH04L67/34, H04L29/12028, H04L61/6022, H04L41/0806, H04L61/20, H04L61/605, H04L29/12207, H04L61/103, H04L12/66, H04L29/12839, H04M3/42229, H04L29/12896European ClassificationH04L12/66, H04L29/12A9D30, H04L29/08N33, H04M3/42M, H04L29/12A3, H04L41/08A1, H04L61/20, H04L61/60D30Legal EventsDateCodeEventDescriptionMay 29, 2012CCCertificate of correctionMar 23, 2005ASAssignmentOwner name: CISCO TECHNOLOGY, INC., CALIFORNIAFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:HADDAD, NAJEEB FARHAN;ANDRIEUX, LAURE F.;TASKER, MICHAELEDRIC;AND OTHERS;REEL/FRAME:016410/0648;SIGNING DATES FROM 20050318 TO 20050322Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:HADDAD, NAJEEB FARHAN;ANDRIEUX, LAURE F.;TASKER, MICHAELEDRIC;AND OTHERS;SIGNING DATES FROM 20050318 TO 20050322;REEL/FRAME:016410/0648RotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services