This invention relates in general to the field of communications and, more particularly, to a system and a method for user anonymity in a session initiated protocol network environment.
Electronic architectures have experienced significant notoriety because they can offer the benefits of automation, convenience, and data management for their respective online communities. Certain network protocols may be used in order to allow an end user to be matched to other end users or to scenarios in which they stand to benefit (e.g., job searches, person-finding services, real estate searches, online dating, etc.).
In some cases, end users desire that their identity, address, or other personal information remain anonymous. The ability to initiate a communication session between two users without exchanging personal information offers a significant challenge to network operators, administrators, and device manufacturers.
To provide a more complete understanding of the present invention and features and advantages thereof, reference is made to the following description, taken in conjunction with the accompanying figures, wherein like reference numerals represent like parts, in which:
Endpoints 12 are clients or customers wishing to initiate a communication in communication system 10 via some network. In one example implementation, endpoints 12 are personal computers that are operable to interface with a SIP network. Note also that the term ‘endpoint’ may be inclusive of devices used to initiate a communication, such as a computer, a personal digital assistant (PDA), a laptop or electronic notebook, a cellular telephone, an IP telephone, an I-Phone, or any other device, component, element, or object capable of initiating voice, audio, or data exchanges within communication system 10. Endpoints 12 may also be inclusive of a suitable interface to the human user, such as a microphone, a display, or a keyboard or other terminal equipment. Endpoints 12 may also be any device that seeks to initiate a communication on behalf of another entity or element, such as a program, a database, or any other component, device, element, or object capable of initiating a voice or a data exchange within communication system 10. Data, as used herein in this document, refers to any type of numeric, voice, or script data, or any type of source or object code, or any other suitable information in any appropriate format that may be communicated from one point to another.
Any device capable of operating as an endpoint 12 may connect to communications network 14 via wire, wireless, cellular, satellite link or other suitable interfaces. Web server 16, which includes memory 18 and processor 20, hosts central website 22 and has access to transmit and receive user or presence data (e.g., user profile data, user and/or user endpoint data, user contact data) from database 24. Presence data may be collected, aggregated, and utilized as required to facilitate communications between endpoints 12 over communications network 10 or other outside communication systems. Presence data may also include information and/or instructions enabling the creation, duration, and termination of communication sessions between diverse endpoints 12 that utilize different communication and/or networking protocols.
Central website 22 can be configured to interface with endpoints 12 and database 24, and may display data inputs from users via endpoints 12 and/or database 24. Note that central website 22 and web server 16
In one example, software that resides in web server 16 (which may be included within central website 22 is executed by processor 20 (potentially in conjunction with memory 18) to achieve the communication coordination, while protecting end user anonymity as outlined herein. Such activity could also be developed externally and then uploaded to web server 16 (i.e., central website 22).
With regard to the possible items that effectuate the teachings of the present invention, central website 22 and/or web server 16 may include software and/or algorithms to achieve the operations for processing, communicating, delivering, gathering, uploading, maintaining, and/or generally managing data, as described herein. This includes suitably displaying some [or all] of these items. Alternatively, such operations and techniques may be achieved by any suitable hardware, component, device, application specific integrated circuit (ASIC), additional software, field programmable gate array (FPGA), server, processor, algorithm, erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or any other suitable object that is operable to facilitate such operations.
Considerable flexibility is provided by the structure of central website 22 and web server 16 in the context of system 10. Thus, it can be easily appreciated that such functions could be provided external to central website 22 and web server 16 (e.g., as a solitary and/or proprietary component). In such cases, such a functionality could be readily embodied in a separate component, server, processor, device, or module. Note that these data coordination features and capabilities may be provided in just one of these elements, in both, or distributed across both of them.
For purposes of teaching and discussion, it is useful to provide some overview as to the way in which the invention disclosed herein operates in a SIP environment. The following information may be viewed as a basis from which the present invention may be properly explained. Such discussion is for purposes of explanation only and, accordingly, should not be construed in any way to limit the broad scope of the invention disclosed herein and its potential applications. Though the current invention is illustrated in the SIP environment, it is not limited to SIP and can actually apply to other VoIP protocols, as well as multiplexing implementations, etc.
Many applications require the creation and management of a session, where a session is considered an exchange of data between an association of participants. The implementation of these applications is complicated by the practices of participants: users move between endpoints, they may be addressable by multiple names, and they may communicate in several different media (in many cases simultaneously). Certain protocols, such as SIP, VoIP, RTMP and H.323, have been developed to carry various forms of real-time multimedia session data such as voice, video, and text messages.
Reliable, flexible, multimedia and voice traffic over internet protocol (IP) networks have been enabled by the SIP topology. SIP is an application layer, control protocol used to establish, modify, and terminate multimedia sessions or calls. SIP provides proxy-able messages used to perform call setup, modification, and termination functions. For example, one SIP message used to perform call setup functions is the INVITE message. The INVITE message is used to invite telephony devices to participate in media stream communications, such as voice communication, data communication, video communication, or any combination thereof. The INVITE message includes a session description protocol (SDP) portion that is used by end user devices to exchange media capabilities and other information. As unified networks emerge, it is becoming increasingly important to provide communication services seamlessly across SIP based packet networks to provide anonymized communication within these unified networks.
In some social networks, end users desire that a user's identity, address, telephone number or other personal information remain anonymous so that other users on the network may not physically, electronically, or otherwise locate a user or utilize a user's contact information for a nefarious purpose. Thus, the ability to initiate a communication session (e.g. text messaging sessions, multimedia sessions, voice call sessions, etc.) between two users, without the exchange of personal contact information in the context of a social networking network is critical from various standpoints, including personal safety and identity theft/fraud prevention.
The SIP features of communications system 10 work in concert with these protocols by enabling endpoints 12 (which may also be referred to as “user agents”) to discover one another and to agree on a characterization of a session they would like to share. For locating prospective session participants, and for other functions, SIP enables the creation of an infrastructure of network hosts (which may also be referred to as “proxy servers”) to which user agents can send registrations, invitations to sessions, and other requests. SIP is an agile, general-purpose tool for creating, modifying, and terminating sessions. SIP works independently of underlying transport protocols and without dependency on the type of session that is being established.
SIP is an application-layer control protocol that can establish, modify, and terminate multimedia sessions (conferences) such as Internet telephony calls. SIP can also invite participants to already existing sessions such as multicast conferences. Media can be added to (and removed from) an existing session. SIP transparently supports name mapping and redirection services, which supports personal mobility. End users can maintain a single externally visible identifier regardless of their network location.
SIP supports five facets of establishing and terminating multimedia communications: 1) user location: determination of the end system to be used for communication; 2) user availability: determination of the willingness of the called party to engage in communications; 3) user capabilities: determination of the media and media parameters to be used; 4) session setup: “ringing” establishment of session parameters at both the called and calling party locations; and 5) session management: including transfer and termination of sessions, modifying session parameters, and invoking services.
A standard SIP platform does not necessarily provide services. Rather, SIP provides primitives that can be used to implement different services. For example, SIP can locate a user and deliver opaque objects to his current location. If this primitive is used to deliver a session description written in SDP, for instance, the endpoints can agree on the parameters of a session. If the same primitive is used to deliver a photo of the caller as well as the session description, a “caller id” service can be easily implemented.
Referring back to
The communications broker transmits the translated call request to the recipient originating from the source profile address (step 70), with the translated call request being received by the recipient SIP endpoint from the recipient SIP server (step 72). The call recipient must then decide whether to accept or deny the call request (step 74). If the recipient accepts the call request, a communication session (e.g., telephone call, text messaging session, etc.) is initiated between the SIP endpoints (step 76). The session can remain active until terminated by the user(s) (step 78). However, if the recipient denies the request for a communication session from the source, the session is terminated.
It is important to note that the stages and steps in
Although the present invention has been described in detail with reference to particular embodiments, it should be understood that various other changes, substitutions, and alterations may be made hereto without departing from the spirit and scope of the present invention. The illustrated network architecture of
Also, some of the steps illustrated in the preceding FIGURES may be changed or deleted where appropriate and additional steps may also be added to the process flows. These changes may be based on specific communication architectures or particular interfacing arrangements and configurations of associated elements and do not depart from the scope or the teachings of the present invention. It is important to recognize that the FIGURES illustrate just one of a myriad of potential implementations of system 10.
Numerous other changes, substitutions, variations, alterations, and modifications may be ascertained to one skilled in the art and it is intended that the present invention encompass all such changes, substitutions, variations, alterations, and modifications as falling within the spirit and scope of the appended claims.
Number | Name | Date | Kind |
---|---|---|---|
6175619 | DeSimone | Jan 2001 | B1 |
6408001 | Chuah et al. | Jun 2002 | B1 |
6564261 | Gudjonsson et al. | May 2003 | B1 |
6680943 | Gibson et al. | Jan 2004 | B1 |
6865161 | Sponaugle et al. | Mar 2005 | B1 |
7139811 | Lev Ran et al. | Nov 2006 | B2 |
7151749 | Vega-Garcia et al. | Dec 2006 | B2 |
7171482 | Jones et al. | Jan 2007 | B2 |
7203674 | Cohen | Apr 2007 | B2 |
7394811 | Gibson et al. | Jul 2008 | B2 |
7440562 | Barnes et al. | Oct 2008 | B2 |
7478161 | Bernet et al. | Jan 2009 | B2 |
7486696 | Garg et al. | Feb 2009 | B2 |
7499720 | Idnani | Mar 2009 | B2 |
7539127 | Shaffer et al. | May 2009 | B1 |
7630486 | Lee et al. | Dec 2009 | B2 |
7640293 | Wilson et al. | Dec 2009 | B2 |
7649881 | Casey | Jan 2010 | B2 |
7792065 | Jepson et al. | Sep 2010 | B2 |
8051130 | Logan et al. | Nov 2011 | B2 |
8054960 | Gunasekara | Nov 2011 | B1 |
8281027 | Martinez et al. | Oct 2012 | B2 |
8316134 | Tanimoto | Nov 2012 | B2 |
8621090 | Bustamente | Dec 2013 | B2 |
8885012 | Bustamente | Nov 2014 | B2 |
8996618 | Bustamente | Mar 2015 | B2 |
20020041590 | Donovan | Apr 2002 | A1 |
20030224792 | Verma et al. | Dec 2003 | A1 |
20030235209 | Garg et al. | Dec 2003 | A1 |
20040030747 | Oppermann | Feb 2004 | A1 |
20050246419 | Jaatinen | Nov 2005 | A1 |
20050276268 | Poikselka et al. | Dec 2005 | A1 |
20060045243 | Durga et al. | Mar 2006 | A1 |
20060146997 | Qian et al. | Jul 2006 | A1 |
20060235994 | Wu | Oct 2006 | A1 |
20060281407 | Deeds et al. | Dec 2006 | A1 |
20070019545 | Alt et al. | Jan 2007 | A1 |
20070064895 | Wong et al. | Mar 2007 | A1 |
20070071223 | Lee et al. | Mar 2007 | A1 |
20070201480 | Bao et al. | Aug 2007 | A1 |
20070282621 | Altman et al. | Dec 2007 | A1 |
20080070697 | Robinson et al. | Mar 2008 | A1 |
20080104227 | Birnie et al. | May 2008 | A1 |
20080144615 | Casey | Jun 2008 | A1 |
20080255989 | Altberg et al. | Oct 2008 | A1 |
20090024741 | Roach | Jan 2009 | A1 |
20090322597 | Medina-Herrero et al. | Dec 2009 | A1 |
20100071053 | Ansari et al. | Mar 2010 | A1 |
20100077017 | Martinez et al. | Mar 2010 | A1 |
20100083364 | Fernandez Gutierrez | Apr 2010 | A1 |
20100088246 | Lim | Apr 2010 | A1 |
20100099389 | Zhu et al. | Apr 2010 | A1 |
20100106842 | Cosmadopoulos et al. | Apr 2010 | A1 |
20100195488 | Mehrotra et al. | Aug 2010 | A1 |
20100217837 | Ansari et al. | Aug 2010 | A1 |
20100217876 | Fikouras et al. | Aug 2010 | A1 |
20100241755 | Bassett et al. | Sep 2010 | A1 |
20100260174 | Preiss et al. | Oct 2010 | A1 |
20100283827 | Bustamente | Nov 2010 | A1 |
20100285856 | Thomas | Nov 2010 | A1 |
20100287286 | Bustamente | Nov 2010 | A1 |
20110182205 | Gerdes et al. | Jul 2011 | A1 |
20110289574 | Hull et al. | Nov 2011 | A1 |
20110313647 | Koebler | Dec 2011 | A1 |
20130003718 | daCosta et al. | Jan 2013 | A9 |
20130212494 | Heiferman et al. | Aug 2013 | A1 |
20130232213 | Bustamente | Sep 2013 | A1 |
20130238708 | Bustamente | Sep 2013 | A1 |
20140082087 | Bustamente | Mar 2014 | A1 |
Entry |
---|
Rosenberg et al., “SIP: Session Initiation Protocol”, Network Working Group Request for Comments: 3261, Jun. 2002. |
Non-Final Office Action in U.S. Appl. No. 12/436,912 mailed on Apr. 28, 2011. |
Response to Non-Final Office Action dated Apr. 28, 2011 in U.S. Appl. No. 12/436,912, filed Jul. 28, 2011. |
Final Office Action in U.S. Appl. No. 12/436,912 mailed on Oct. 11, 2011. |
Request for Continued Examination and Amendment in U.S. Appl. No. 12/436,912, filed Dec. 8, 2011. |
Examiner Interview Summary in U.S. Appl. No. 12/436,912 mailed on Dec. 14, 2011. |
Offringa, Peter “Zoosk—The Engineering behind Real Time Communications,” available online at <URL http://highscalability.com/blog/2012/8/27/zoosk-the-engineering-behind-real-time-communications.html>, Aug. 27, 2012 (4 pages). |
Zoosk Customer Support, “How Do I Video Chat?” available online at <URL https://zoosk.zendesk.com/entries/20513017-how-do-i-video-chat> Oct. 7, 2011 (3 pages). |
Fiore, Andrew, et al., “Online Personals: An Overview,” CHI 2004, Apr. 24-12, 2004, Vienna, Austria (pp. 1395-1398). |
Non-Final Office Action in U.S. Appl. No. 12/436,869 mailed on Feb. 7, 2012. |
Response to Non-Final Office Action dated Feb. 7, 2012 in U.S. Appl. No. 12/436,869, filed Apr. 25, 2012. |
Final Office Action in U.S. Appl. No. 12/436,869 mailed on May 30, 2012. |
Request for Continued Examination and Amendment in U.S. Appl. No. 12/436,869, filed Jul. 25, 2012. |
Non-Final Office Action in U.S. Appl. No. 12/436,912 mailed on Nov. 27, 2012. |
Response to Non-Final Office Action dated Nov. 27, 2012 in U.S. Appl. No. 12/436,912, filed Feb. 27, 2013. |
Notice of Allowance in U.S. Appl. No. 12/436,912 mailed on Jul. 18, 2013. |
U.S. Appl. No. 13/869,912, filed Apr. 24, 2013 and entitled “System and Method for Providing Calendar and Speed Dating Features for Matching Users in a Network Environment”, Inventor Michael G. Bustamente. |
U.S. Appl. No. 13/869,948, filed Apr. 24, 2013 and entitled “System and Method for Providing Calendar and Speed Dating Features for Matching Users in a Network Environment”, Inventor Michael G. Bustamente. |
Notice of Allowance in U.S. Appl. No. 12/436,869 mailed on Jul. 9, 2014. |
Notice of Allowance in U.S. Appl. No. 14/088,387 mailed on Dec. 18, 2014. |
Non-Final Office Action in U.S. Appl. No. 13/869,912 mailed on Feb. 27, 2015. |
Non-Final Office Action in U.S. Appl. No. 14/088,387 mailed on Sep. 22, 2014. |
Response to Non-Final Office Action dated Sep. 22, 2014 in U.S. Appl. No. 14/088,387, filed Nov. 20, 2014. |
Response to Non-Final Office Action dated Feb. 27, 2015 in U.S. Appl. No. 13/869,912 filed on May 27, 2015. |
Notice of Allowance in U.S. Appl. No. 13/869,948 mailed on May 19, 2015. |
Number | Date | Country | |
---|---|---|---|
20100246576 A1 | Sep 2010 | US |