Source: https://patents.google.com/patent/US9065903B2/en
Timestamp: 2018-07-22 21:24:24
Document Index: 617785724

Matched Legal Cases: ['Application No. 10770162', 'Application No. 201080020015', 'Application No. 2012', 'Application No. 099109673', 'Application No. 201080020015', 'Application No. 2010241810', 'Application No. 2010241810', 'Application No. 201080020015', 'Application No. 201080020015', 'Application No. 201080020015', 'Application No. 10770162', 'Application No. 201080020015', 'Application No. 201080020015', 'art 3', 'art 3']

US9065903B2 - User-based authentication for realtime communications - Google Patents
US9065903B2
US9065903B2 US13753485 US201313753485A US9065903B2 US 9065903 B2 US9065903 B2 US 9065903B2 US 13753485 US13753485 US 13753485 US 201313753485 A US201313753485 A US 201313753485A US 9065903 B2 US9065903 B2 US 9065903B2
US13753485
US20130182832A1 (en )
This application is a Continuation of copending Non-Provisional patent application Ser. No. 12/432,773, entitled “USER-BASED AUTHENTICATION FOR REALTIME COMMUNICATIONS”, and filed Apr. 30, 2009, the entirety of which is hereby incorporated by reference.
In yet another embodiment, the telephone can be provided a certificate that once verified and signed, can be used for telephone authentication for all subsequent connections after the initial connection provisioning process.
Upon entering an extension and PIN, the phone 602 requests an IP address from the DHCP server 506. The DHCP server 506 returns to the phone 602 an IP address and a DNS record giving the location of the enterprise communications server 302. Upon receiving the location information, the IP phone 602 sends a registration request in the form of an http://request that includes the user extension and PIN to the enterprise communications server 302.
At 714, the user enters an associated extension and PIN via the IP phone 702. This combination uniquely identifies the user to the enterprise server 704. At 716, the extension and PIN are sent to the enterprise server 704 included in an http://message as part of a provisioning sequence. At 718, the enterprise server 704 uses the extension to retrieve the user SIP URI. This can be accomplished either by accessing the user extension in a local database on the enterprise server 704 or by sending a request to the authentication server 708.
1. A method of communications, the method comprising acts of:
initiating a request via a telephone for access to a communications network, the request comprises a telephone number and a personal identification number (PIN);
discovering the communications network via the telephone based on the request;
authenticating the telephone of a user to the communications network using the telephone number and the PIN;
issuing a certificate to the telephone based on the telephone number and the PIN;
registering the telephone to the communications network using the certificate; and
configuring a microprocessor to execute instructions associated with at least one of the acts of initiating, discovering, authenticating, issuing, or registering.
2. The method of claim 1, further comprising provisioning a cell phone, as the telephone, using at least one of the acts of initiating, discovering, authenticating, issuing, or registering.
3. The method of claim 1, further comprising discovering a communications server of the communications network based on location information provided to the telephone.
4. The method of claim 1, further comprising registering the telephone to the network using in-band communications.
5. The method of claim 1, further comprising assigning a SIP URI to the telephone as part of registering the registering the telephone to the communications network and accessing the communications network based on the SIP URI.
6. The method of claim 1, further comprising provisioning the telephone to the communications network using a new PIN and a new telephone number.
7. The method of claim 1, further comprising authenticating to other network services and functionality via a computer based on connection of the telephone to the computer.
8. The method of claim 1, further comprising provisioning the telephone with a SIP URI and the certificate based on registration of the telephone to an internal enterprise network, which is the communications network, and accessing the internal enterprise network from a location external to the internal enterprise network using the provisioned telephone, based on the certificate.
9. The method of claim 1, further comprising provisioning the telephone from a location external to the communications network via a computer having access to the communications network.
10. The method of claim 1, further comprising provisioning the telephone to a different user based on a SIP URI and PIN of the different user.
11. A method of communications, the method comprising acts of:
receiving a telephone number and a numeric personal identification number (PIN) via a telephone as part of provisioning the telephone;
looking-up a username and certificate associated with the telephone number and the PIN;
provisioning the telephone to an enterprise communications network based on the username and certificate; and
configuring a microprocessor to execute instructions associated with at least one of the acts of receiving, looking-up, or provisioning.
12. The method of claim 11, further comprising generating the certificate via a web service discovered using a network registrar.
13. The method of claim 12, further comprising prompting confirmation of a suffix of the web service to prevent malicious spoofing of the network registrar.
14. The method of claim 11, further comprising provisioning a SIP URI to the telephone based on validation of the telephone number and the PIN by a certificate web service.
15. The method of claim 11, further comprising provisioning the telephone only as a first-time use of the telephone by a given user.
16. A method of communications, the method comprising acts of:
receiving a numeric user identifier and PIN via a telephone to be provisioned;
providing location information of an enterprise communications server to the telephone;
issuing a telephony address to the telephone based on the numeric user identifier;
authenticating the telephone based on the telephony address and the PIN;
generating a certificate via the enterprise communications server and storing the certificate on the telephone to complete the provisioning; and
configuring a microprocessor to execute instructions associated with at least one of the acts of receiving, providing, issuing, authenticating, or generating.
17. The method of claim 16, further comprising communicating SIP messages with the enterprise communications server using the telephony address, which is a SIP URI.
18. The method of claim 16, further comprising discovering a unified communications service based only on the numeric user identifier and PIN, without specifying a domain of the unified communications service.
19. The method of claim 16, further comprising uniquely identifying a user of the enterprise via the numeric user identifier and the PIN.
20. The method of claim 16, further comprising automatically returning location information of the enterprise communications server to the telephone based on based on a request from the telephone for network access.
US13753485 2009-04-30 2013-01-29 User-based authentication for realtime communications Active US9065903B2 (en)
US12432773 US8391452B2 (en) 2009-04-30 2009-04-30 User-based authentication for realtime communications
US13753485 US9065903B2 (en) 2009-04-30 2013-01-29 User-based authentication for realtime communications
US12432773 Continuation US8391452B2 (en) 2009-04-30 2009-04-30 User-based authentication for realtime communications
US20130182832A1 true US20130182832A1 (en) 2013-07-18
US9065903B2 true US9065903B2 (en) 2015-06-23
US12432773 Active 2031-12-06 US8391452B2 (en) 2009-04-30 2009-04-30 User-based authentication for realtime communications
US13753485 Active US9065903B2 (en) 2009-04-30 2013-01-29 User-based authentication for realtime communications
WO (1) WO2010126800A3 (en)
JP2001216400A (en) 2000-02-04 2001-08-10 Teikoku Databank Ltd Electronic business transaction system
US6847704B1 (en) 2002-12-23 2005-01-25 At&T Corp. Self-installable and portable voice telecommunication service
WO2007013966A2 (en) 2005-07-21 2007-02-01 Pulver.Com Enterprises A system and method for securely storing and accessing credentials and certificates for secure voip endpoints
JP2007142621A (en) 2005-11-16 2007-06-07 Sanyo Electric Co Ltd Ip phone system compatible with free address
JP2007266799A (en) 2006-03-28 2007-10-11 Hitachi Ltd Ip telephone system and ip telephone terminal registration method
US20080137644A1 (en) 2006-12-11 2008-06-12 Reynolds Douglas F METHODS AND APPARATUS TO PROVIDE VOICE OVER INTERNET PROTOCOL (VoIP) SERVICES
JP2008172382A (en) 2007-01-10 2008-07-24 Nec Corp Telephone set, communication system using the same, and call origination/termination history registration/display method used for them
CN101252434A (en) 2008-02-29 2008-08-27 北京中电华大电子设计有限责任公司;西安西电捷通无线网络通信有限公司;中太数据通信(深圳)有限公司;信息产业部通信计量中心 Apparatus and method for implementing mobile telephone access identification in wireless local area network
JP2008228028A (en) 2007-03-14 2008-09-25 Kddi Corp System, method and program for attribute authentication in ip telephone network
JP2008278085A (en) 2007-04-27 2008-11-13 Nakayo Telecommun Inc Ip telephone set having data terminal interlinked automatic log-in function
JP2009043043A (en) 2007-08-09 2009-02-26 Nec Corp Authentication system and authentication method using sip
US20090073962A1 (en) 2007-09-18 2009-03-19 Avaya Technology Llc Modular messaging log application on an IP phone
JP2009077075A (en) 2007-09-19 2009-04-09 Toshiba Corp Telephone system
US20090177585A1 (en) 2001-03-14 2009-07-09 Thomson Licensing Conditional access system for broadcast digital television
"Avaya IP Office Conferencing Solutions", Retrieved at <<http://www.cablenet.com.tr/dosyalar/Conferencing%20Solutions.pdf>>, 2004, 4 pages.
"Avaya IP Office Conferencing Solutions", Retrieved at >, 2004, 4 pages.
"Cisco Unity 4.2 for Microsoft Exchange", Retrieved at <<http://www.cisco.com/en/US/prod/collateral/voicesw/ps6789/ps5745/ps2237/product-data-sheet0900aecd800fe148.html>>, last retrieved: Dec. 29, 2008, 9 pages.
"Configuring Call-Control Integration for Cisco Unified MeetingPlace Express with Cisco Unified Communications Manager", Retrieved at <<http://www.cisco.com/en/US/docs/voice-ip-comm/meetingplace-express/2-0/english/administration/guide/cm20call.html>>, last retrieved: Dec. 29, 2008, 16 pages.
"European Search Report Received in European Patent Application No. 10770162.5", Mailed Date: Feb. 10, 2014, Filed Date: Apr. 23, 2010, 6 Pages.
"First Office Action Received in Chinese Patent Application No. 201080020015.4", Mailed Date: Nov. 6, 2013, Filed Date: Apr. 23, 2010, 11 Pages.
"First Office Action Received in Japanese Patent Application No. 2012-508552", Mailed Date: Apr. 1, 2014, Filed Date: Apr. 23, 2010, 3 Pages. (w/o English Translation).
"LDAP Directory Integration", Retrieved at <<http://www.cisco.com/en/US/docs/voice-ip-comm/cucm/srnd/6x/directry.html>>, last retrieved: Dec. 29, 2008, 12 pages.
"LDAP Directory Integration", Retrieved at >, last retrieved: Dec. 29, 2008, 12 pages.
"Non-Final Office Action Received for U.S Appl. No. 12/432,773", Mailed Date: May 23, 2012, 13 Pages.
"Notice of Allowance Received for Mexican Patent Application No. MX/A/2011/011349", Mailed Date: Aug. 20, 2013, 1 Page.
"Office Action & Search Report Received for Taiwan Patent Application No. 099109673", Mailed Date: Aug. 20, 2014, 8 Pages.
"Office Action Received for Chinese Patent Application No. 201080020015.4", Feb. 10, 2015, 8 Pages.
"Office Action Received in Australian Patent Application No. 2010241810", Mailed Date: Mar. 12, 2014, Filed Date: Apr. 23, 2010, 3 Pages.
"Response to Non-Final Office Action Filed in U.S. Appl. No. 12/432,773", Response Filed Date: Sep. 21, 2012, 17 Pages.
"Response to Office Action Filed in Australian Patent Application No. 2010241810", Response Filed Date: Apr. 14, 2014, 3 Pages.
"Response to Office Action Filed in Chinese Patent Application No. 201080020015.4", Response Filed Date: Feb. 12, 2014, 9 Pages.
"Response to Office Action Filed in Chinese Patent Application No. 201080020015.4", Response Filed Date: Jun. 6, 2014, 10 Pages.
"Response to Office Action Filed in Chinese Patent Application No. 201080020015.4", Response Filed Date: Oct. 8, 2014, 6 Pages.
"Response to Office Action Filed in European Patent Application No. 10770162.5", Response Filed Date: Sep. 8, 2014, 19 Pages.
"Second Office Action Received in Chinese Patent Application No. 201080020015.4", Mailed Date: Mar. 26, 2014, Filed Date: Apr. 23, 2010, 14 Pages.
"Third Office Action Received in China Patent Application No. 201080020015.4", Mailed Dated: Jul. 18, 2014, 9 Pages.
Masterson, Joey, "White Paper: Managing Exchange 2007 Unified Messaging-Part 3", Retrieved at <<http://technet.microsoft.com/en-us/library/bb738123.aspx>>, Sep. 2007, last retrieved: Dec. 29, 2008, 133 pages.
Masterson, Joey, "White Paper: Managing Exchange 2007 Unified Messaging-Part 3", Retrieved at >, Sep. 2007, last retrieved: Dec. 29, 2008, 133 pages.
KR101635244B1 (en) 2016-06-30 grant
US8391452B2 (en) 2013-03-05 grant
EP2425645A2 (en) 2012-03-07 application
EP2425645A4 (en) 2014-03-12 application
JP2012525778A (en) 2012-10-22 application
US20130182832A1 (en) 2013-07-18 application
WO2010126800A2 (en) 2010-11-04 application
KR20120007520A (en) 2012-01-20 application
RU2011143931A (en) 2013-05-10 application
WO2010126800A3 (en) 2011-02-10 application
US20100278322A1 (en) 2010-11-04 application
JP5710596B2 (en) 2015-04-30 grant
CA2756835A1 (en) 2010-11-04 application
CN102415117A (en) 2012-04-11 application
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:KRANTZ, ANTON W.;PARANDEKAR, AMEY;EYDELMAN, VADIM;AND OTHERS;SIGNING DATES FROM 20090427 TO 20090428;REEL/FRAME:034585/0907