Patent Grant
RE48066
The Internet is a collection of computer networks from which users obtain and share information. The Internet has evolved from the ARPAnet to become the largest computer network in the world. The Internet supports various services. Of these services, the World Wide Web (the “Web”) and email are among the most widely used. Of these, the Web comprises a collection of hundreds of millions of documents (“Web pages”) written in mark up languages such as HTML, XML, and WML.
In Internet transmissions, Transaction Control Protocol/Internet Protocol (“TCP/IP”) is the communication standard. TCP/IP is a suite of protocols enabling communication between each node of the network. With the increasing bandwidth being offered by network carriers, not only data but also voice, audio and video are increasingly being transmitted through the network.
The evolution of the Internet continues and, in so doing, drives Internet-related product development, including in hardware, software and protocols. The Internet is extending in wireless communication and handheld devices. As an example, Internet-enabled cellular phones (such as smart and super phones) combine the features of cellular phones with the ability to access the Internet. As another example, certain personal digital assistants (“PDAs”) are directed to couple standard features with wireless access to the Internet. These phones, PDAs and other handheld devices exploit protocols such as, but not limited to, WAP, Web clipping, HDML or CHTML. Through these Internet-enabled devices, it is anticipated that users will not only place phone calls, organize their schedules and/or otherwise exploit the respective device's standard functionality, but also access the Internet for browsing the Web, obtaining information, communicating (e.g., via email) and the like. In so doing, it is also anticipated that the device's standard features and the Internet's benefits will both be enhanced.
The evolution of the Internet also implicates an evolution, if not revolution, in the infrastructure of communication networks. Today, people generally obtain personal access to the Internet by dialing up Internet service providers; the dial up may be carried for example over circuit-switched networks (“CSN”), typically via local telecommunications providers. In dial up, CSNs establish a physical circuit, which is dedicated exclusively to the call between the parties.
While generally available to users, CSNs appear to be in relative decline, being increasingly supplanted by packet-switched technologies. Packet-switched technologies significantly increase a network's speed and capacity. In packet-switched networks, traffic is digitized, compressed, and transported as packets. These networks enable the packets of a particular transmission to travel through various channels from source to destination. Moreover, these networks enable traffic in varied media types, including voice, audio, video, text, data and facsimile. In enabling the varied types, moreover, the networks may deploy technologies (e.g., ATM), which enable significant features, such as quality of service, wherein priorities are assigned to and among the media types (e.g., so that packets of voice communications arrive timely, thereby ensuring adequate fidelity for the conversation).
Packet-switched networks follow open standards. Accordingly, these networks enhance the ability of service providers to deploy new services, including high-bandwidth services for Internet use or otherwise (e.g., television programming and/or video on demand). By comparison, in circuit-switched networks, the call control functionality and the service logic tend to be buried within the switch. Moreover, the functionality generally is proprietary to the switch vendors. As such, new services generally are deployed at the discretion of the switch vendor, not the service providers.
In addition to hardware, software, protocols and infrastructure, the evolution of the Internet also implicates development of new and improved services. Already, marketplaces on the Internet (i.e., virtual marketplaces) are well known and increasingly diverse in direction, content and business model. Ebay, Yahoo, E*Trade and Amazon are examples, each facilitating transactions, including the selling, buying and auctioning of merchandise and the provision of services, with and among enterprises and individuals. The merchandise and services comprise a wide variety, from books to automobiles, to stocks, to calendaring, that seems ever expanding in breadth.
Overcoming the geographic constraints of physical proximity, the Internet also introduces increasing and new opportunities for people to meet and interact with each other. Communities on the Internet (i.e., virtual communities) are well known and increasingly diverse in style, content and target participants. Virtual communities typically offer services and associated tools, such as chat rooms, email and Web publishing. Through these services and tools, virtual communities enable their participants to communicate, including to express their respective views, share common interest(s) and otherwise interact as if in the physical world, and increasingly in ways not available in the physical world.
Virtual marketplaces may facilitate the exchange or trading of ideas, knowledge and information between and among individuals and entities (sometimes referred to collectively herein as “participants”). These virtual marketplaces (“information marketplaces”) tend to have an express or implied premise, understanding or foundation: individuals and entities have one or more interests and/or areas of expertise that can or should be (a) shared with or provided to participants, (b) nurtured/advanced by interaction with participants, and/or (c) otherwise communicated to or with other participants for some derived benefit of either or both participants.
In an example of a transaction in a contemplated information marketplace, a participant (the “initiator”) posts a question, inquiry or view (“posting”) at a selected Web site of the marketplace. The initiator has the goal of obtaining one or more of answers, information, direction, responses or interaction (“response”) from or with one or more participants. The initiator may choose to direct the posting to selected participants (“experts”). The initiator preferably is enabled to select experts based on the experts' identified or claimed interest/expertise. The initiator may have identified interests and expertise. Indeed, the initiator may also be an expert in the marketplace and, conversely, the expert may also be an initiator in the marketplace.
A contemplated information marketplace preferably supports provision of the qualifications or characteristics of its experts, initiators and/or participants and may do so variously. In an example case, the marketplace publishes qualifications/characteristics (e.g., on Web sites or page(s)). The qualifications/characteristics may be mandated or voluntary, or a combination. The qualifications/characteristics may, particularly in the case of initiators, be selectable by the participant. The qualifications/characteristics may include various data, such as, among others, profile descriptions, transaction history (e.g., in the marketplace), ratings (e.g., marketplace, participant, expert and/or initiator provided), comments and reviews (e.g., marketplace, participant, expert and/or initiator provided), fee schedules or other forms of pricing. Profile descriptions may include, among other things, certifications (e.g., marketplace, professional, or governmental), specialties, sub-area(s) of interest/expertise, education, years of practice, awards, geographic location, and geographic scope or limitation on the interest/expertise. Profile descriptions may also include—particularly for initiators—qualifications or characteristics in the field of the posting, transaction history in the field of the posting, credit rating, age, education level, and geographic location.
Once an initiator selects one or more experts, a next step is to establish a communication link between the initiator and an expert for posting and response (an “information transaction”). A communication link may be variously provided, including via email, online chat and instant messaging. However, a drawback of email is that it relies on text communication (e.g., typing), with its attendant mechanical challenges. Another drawback of email is the time lag (“latency”) between sending an email and receiving a response. Yet another drawback of email is that it has a low level of interactivity and, as such, tends to be impersonal, ambiguous and inefficient in communication. Accordingly, email tends to hinder experts in providing a response, particularly one suited to and satisfying of the initiator's needs.
Online chat and instant messaging tend to be more interactive than email. Even so, each also again relies on text communication. Moreover, by their nature, chat and instant messaging tend to introduce an emphasis on speed in that text communication (e.g., fast typing). This emphasis generally is undesirable. Indeed, this emphasis can be a substantial hindrance for people either who are not familiar or adept with keyboards, who are physically excluded from keyboard use and/or whose written language is not based on Roman characters (e.g., those using symbol-based written languages, such as Chinese). Moreover, this emphasis may be specifically undesirable and the hindrance exacerbated in the context of an information instruction (e.g., initiators and/or experts in an information marketplace find the emphasis on rapid typing to be detrimental to an information instruction).
Given these drawbacks, a contemplated information marketplace preferably supplants or supplements email, online chat and instant messaging with other forms of Internet-based or Internet-related communication. Such forms of communication typically rely—at least in part—on voice communication. These forms include audio and/or audio/video conferencing, with or without text communication. These forms are desirable in their enhanced interactivity, reduced latency and de-emphasis on writing, particularly rapid writing. As such, these forms tend to provide more personal, direct, clear and efficient communication. These forms are simply more natural. Accordingly, these forms tend to be particularly desirable for initiators and experts alike in the context of an information marketplace.
Although voice communication tends to be more direct, efficient and otherwise desirable than e-mail, chat, and instant messaging, voice communication also tends to have some drawbacks. In particular, voice communication generally is subject to a lower level of anonymity (whether real or perceived) than is typically associated with each of email, chat and instant messaging.
Anonymity typically characterizes interaction and other communication via the Internet. For example, people are enabled to interact and otherwise communicate in cyber space without revealing much, if any, personal information, such as legal names or phone numbers.
Internet users tend to prefer anonymity for various reasons. As an example, an employee using the Internet to search for a new job desires anonymity so as to preclude any revelation of their identity to a current employer, supervisors and/or colleagues. As another example, an individual who has provided personal financial data to an online planner may desire anonymity so that the data is not associated with the individual's identity (such association potentially transforming the raw data into valuable information). As yet another example, members of Internet communities use various kinds of substitute names (e.g., aliases, nicknames or user names) in communicating with each other.
The shortfall of anonymity in voice communications—particularly conversations conducted via the standard telephone system—tends to introduce problems with privacy, particularly expectations of privacy. A common such problem is the receipt of unwanted phone calls. These unwanted calls can be annoying (e.g., telephone calls from tele-marketers), disturbing (e.g., contact from objectionable political organizations) and even frightening (e.g., intrusions from ostensibly dangerous individuals). Perhaps because voice communication is direct, unwanted calls tend to be difficult to terminate. Perhaps because telephone conversations are more personal, people tend not to fully block, automatically reject or otherwise absolutely deal with calls from unknown sources, which calls have a tendency to be unwanted but which could cause desirable or important calls to be missed (e.g., a friend of family member calling for emergency assistance).
Based at least in part on concerns about unwanted calls, people remain reluctant to disclose their phone numbers, particularly their home telephone and personal cellular numbers. This reluctance also tends to reflect, at least in part, the perception that phone numbers enable the recipients to more readily discover personal information about the person that disclosed the number, such as name and physical address. This reluctance also tends to result in slow acceptance and lesser use among Internet users of voice communication (i.e., as compared to email, chat and instant messaging), whether such communication is Internet-based or Internet-related (e.g., via standard telephone service (also known as the plain old telephone system (“POTS”)), but initiated by or in connection with Internet services).
It is desirable, then, to integrate voice communication and anonymity. An example of such integration may be illustrated in the context of an information marketplace. There, an initiator determines to conduct an information instruction with a selected expert via voice communication. To do so, the initiator submits a request for voice communication with the selected expert, the submission being through the Internet to the operator or other infrastructure of the information marketplace (or other service or system that supports linking by voice communication). The marketplace contacts the selected expert. The contact may be via (a) the Internet, so as to support voice communication as voice over Internet protocol (“VoIP”) or (b) telephone service. In either case, if the contact results in establishing a voice communication link with the expert, the marketplace maintains that link (e.g., puts the expert on hold) while establishing voice connection with the initiator before connecting the expert and the initiator. The marketplace makes that connection, in one case, by linking the initiator and the expert over the Internet, with the marketplace either interposed in the transmission of packets or enabling direct transmission. In another case, the marketplace bridges between the initiator communicating over the Internet (e.g., VoIP) and the expert communicating via standard telephony. In yet another case, the marketplace connects by contacting the initiator by telephone and, once the initiator is on the line, connecting the initiator with the expert who is also linked by telephone. In each and any case, a connection is made and voice communication is enabled, characterized by enhanced support for anonymity.
Integration of anonymity and voice communication in this form tends to have shortfalls. One of the shortfalls is that a party may be contacted, without advance notice and at any time by the marketplace, responsive to any initiator's request. That scope of contact tends to deprive the contacted party of control over their respective schedules, which in turn, tends to degrade productivity and efficiency in their work and to reduce the quality of their personal time. Indeed, without advance notice of calls in an information marketplace, an expert may be induced to keep the telephone proximate at all times, so as to either take calls in interruption of other work or play and/or to forestall work or play in anticipation of calls (e.g., calls that might never arise). This tends to have enhanced relevance in the commercial or professional context, wherein the expert seeks to provide high quality and highly responsive service to clients (e.g., initiators) so as to, among other things, keep clients satisfied and otherwise happy with the provided services (e.g., to avoid unanswered calls).
One solution to this shortfall is to support specified times and/or time range(s) during which a party (e.g., an expert of an information marketplace) is committed to be available for receipt of calls from the information marketplace. In the information marketplace, these times and ranges are office hours. During an expert's office hours, the expert commits, or even guarantees, to be present to receive calls from the marketplace. At the same time, the expert benefits by enhanced knowledge of and personal control over, when such calls, if any, may arise.
This solution, however, also has shortfalls. In the information marketplace, one shortfall is its tendency to reduce, from an already finite number of experts available via the marketplace, the number of experts actually available at any given time. That is, at any given time, it is to be expected that, via the marketplace, less than all of the experts are within their office hours. Moreover, even if a particular expert is within their office hours, a reduced supply of experts will tend to reduce the frequency at which requests result in a connection (e.g., the expert will have an increased chance of being busy with another, earlier initiator).
Another shortfall is that the initiator will generally attempt to contact the expert promptly, if not immediately or substantially immediately, after indicating interest in contact, and this might not be convenient for the expert even if the initiator attempts to make contact within the expert's office hours.
As another example, a service or system supporting integration may assign individuals and entities respective user codes, each of which uniquely identifies the particular user. To support such codes, the service/system stores the codes, e.g., in one or more databases. Preferably, the service/system associates the codes with the telephone number and/or contact information of the respective individuals and entities.
The service/system may use the user codes variously. For example, in a virtual chat room context, the service/system may enable participants to place an advertisement (e.g., in a publication, such as a physical or virtual magazine) carrying the telephone number of the marketplace and citing the user code. In that circumstance, an observer of the advertisement may contact the participant by placing a telephone call to the marketplace and entering the user code. The service/system then establishes the communication link to the participant, e.g., by placing the observer on hold, retrieving the participant's telephone number by association with the user code, contacting the participant and, once the participant is contacted and found to be available, connecting the participant with the calling observer. In this manner, the observer does not know the actual phone number of the participant, thus preserving the participant's anonymity.
This design is suitable for chat rooms where participants talk to each other casually, and the system only needs to identify different participants. However, user code is not sufficient to identify and describe different transactions having different transaction specifications and connection criteria among participants, as in the context of an information marketplace where participants buy and sell information.
As still another example, a service or system supporting integration of anonymity and voice communication may assign each user a contact code, the contact code identifying each user as a party to a scheduled voice communication. The contact code may be one or more groups of alphanumeric characters (e.g., if the contact code comprises a call code and password, it may be provided as one or two numbers). In supporting contact codes, the service/system enables the parties to place separate telephone calls (through the public switched telephone network or via the Internet) to the service/system (or related infrastructure) at a scheduled time. Upon connection with the service/system, each party enters their respective contact codes (e.g., through their telephone keypads). The service/system compares the contact codes entered by the parties and connects the telephone calls if the contact codes are proper (e.g., the codes must either match exactly or match in accordance with predetermined criteria).
Yet another example is an extension of the contact code feature. In this case, the service/system creates, after the first successful connection between two parties, a record indicative of these two parties and/or of the connection. Based on that record, the service/system may be configured to connect either party to the other when, in the future, one party dials into the system and inputs their contact code. That is, the service/system places a call to the non-calling party, rather than requiring the non-calling party to dial in. In such case, the service/system may be configured to support (a) provision of information to the called party about the calling party, e.g., upon the service/system contacting the called party, (b) a request that the called party enter their contact code, (c) a combination of these. The service/system may be configured so that either or both parties may elect in or out of this feature.
In addition to the shortfall of using user code, this method requires participants placing separate phone calls to the service/system at the same time.
It has now been recognized that the services/systems described above do not allow one or more parties to specify the nature of the transaction, e.g. with respect to time or time interval, billing arrangements, and other variables.
In accordance with a first aspect of the invention there is provided a method of facilitating anonymous voice communication between a first station and a second station, at least the second station having an address for voice communication, the method comprising providing an interface that allows input of a transaction specification from at least one of the first and second stations, generating a reference code associated with the transaction, there being a defined relationship between the reference code and said address, supplying the reference code to at least the first station, receiving a voice communication request from the first station, receiving the reference code from the first station, using the reference code to recover said address, and opening a channel for voice communication between said first and second stations, whereby voice communication can be established between the first and second stations without providing said address to the first station.
In accordance with a second aspect of the invention there is provided a method of establishing anonymous voice communication between a first station and a second station, at least the second station having an address for voice communication, the method comprising supplying a transaction specification from at least one of the first and second stations to a controller, generating a reference code associated with the transaction at the controller, there being a defined relationship between the reference code and said address, supplying the reference code from the controller to at least the first station, making a voice communication request from the first station to the controller, supplying the reference code from the first station to the controller, using the controller to recover said address from the reference code, and opening a channel for voice communication between said first and second stations.
In accordance with a third aspect of the invention there is provided an apparatus for facilitating anonymous voice communication between a first party and a second party, at least the second party having an address for voice communication, including a means for enabling negotiation of a transaction specification, a means for generating a reference code, there being a defined relationship between the reference code and said address, and for supplying the reference code to the first party, a means for receiving a voice communication request from the first party and for receiving the reference code from the first party, a means for using the reference code to recover said address, and a means for opening a voice communication channel between said first party and said address without supplying said address to the first party.
A preferred embodiment of the invention facilitates anonymous voice communication between parties involved in online transactions.
In a preferred embodiment of the invention, either/both parties are able to schedule individually or in coordination one or more future (and/or immediate) appointments for voice communication while preserving anonymity.
A preferred embodiment of the invention allows transacting parties to specify their mutually agreed connection criteria, such as connection time frame, which party should initiate the connection, charging method and duration of the communication. Referring to the example of an expert community, experts are not restricted to their office hours without knowing when, if ever, they will be contacted by the system for servicing a user request. On the other hand, users would be able to have access to all registered experts without having to wait for their office hours because both parties can set up mutually agreed upon appointment time for voice communication.
In various forms of integration of voice communication and anonymity, one or more additional features may be desirable. As an example, a service or system supporting integration may provide a transaction tracking mechanism and/or process that enables identification and cataloging of a user's various transactions. Such mechanism and/or process responds to the fact that a given user may have a history of transactions and, at any given time, may be involved in several transactions, with each such past and current transaction typically having different attributes and connection criteria.
To illustrate by scenario, users A, B and C are participants in an information marketplace. In the marketplace, participant A is an expert in both career planning and fishing. Participant A is counseling participants B and C, individually, as to career planning, with the assistance being provided via anonymous voice communication. Participant A is also advising participant C as to fishing skills, which advice if provided via email. Participant A charges different fees to participant B than to participant C for career planning, based on the differing complexity of the cases. Participant A charges participant C a much lower price for the fishing advice. Moreover, participant A counsels participants B and C during daytime hours, while responding to C on fishing skills only during evening hours. Participant A also places restrictions on the times during which participants B and C are permitted to make contact for career counseling.
In the above scenario, the transaction tracking mechanism/process preferably is implemented so as (a) to differentiate among transactions, even if the transactions are between the same two participants and (b) to track, for each such transaction, the transaction's attributes, such as, but not limited to, fees or other pricing, elapsed time, connection type (e.g., voice, chat, email, etc.), and scheduling.
In a preferred embodiment of the invention, relating to this example, a reference code is associated with each transaction. The use of a transaction specific reference code makes it possible to manage each voice communication event individually according to connection criteria agreed by transacting parties. Assigning a reference code to each transaction provide more manageable flexibility. For example, user A can request to be connected to B and C separately. Since these two transactions have different reference codes, the system would know how to charge B and C differently for the connection. User C is to be connected with at least twice, once for career coaching and once for fishing tips. With different reference codes, the system is able to distinguish which connection is for career coaching and which is for fishing tips, and therefore, charge C accordingly.
A service or system supporting integration preferably offers network flexibility. Preferably the service/system is Internet-based, but also compatible with circuit-switched networks. In addition, the service/system preferably is not restricted to circuit-switched networks for establishment of communication links between parties, particularly for voice communication.
Still further, a preferred embodiment of the invention provides a method and apparatus to guarantee fulfillment of pre-agreed criteria of the transaction specification. For example, in a preferred embodiment of the invention the connection can only be established during a pre-agreed connection time frame. Connection request outside of the pre-agreed time frame may be rejected. This time frame, as an attribute of the transaction specification, is inputted by the user and stored in a database. This information can be retrieved from the database using the reference code. A controller unit qualifies the connection according to the transaction specification, such as the pre-agreed appointment time. The controller unit also monitors the connection and generates logs, which can be used to bill the user based on pre-agreed rate.
A preferred embodiment of the invention provides an automated process for end users to be connected automatically without manual input. The process of obtaining the reference code, connecting to the controller unit and inputting the reference code can be automated by a software program or hardware component in the communication device of the user. Therefore, with a click of a button, the user is anonymously and automatically connected with the other party for voice communication.
As yet another example, a service or system supporting integration may implement analytical services based on information (e.g., stored by the service/system) about users of the service/system, particularly in the context of voice communication. The service/system may be implemented to gather such information, either from the user, or from other users, or from third party sources or from the user's activity within the service/system. In the context of an information marketplace, this information may comprise some or all of the characteristics, qualifications and/or profiles of the participant.
An illustration of this feature is implementation of the service/system to analyze for matches between individuals and/or entities and, based on those matches, to establish communication links between the matched parties. In so establishing these links, the service/system may merely suggest that the parties communicate or may automatically initiate the links. Indeed, the service/system may be configured so that either or both parties may elect in or out of this matching feature and, if electing in, may select between suggestion and automatic treatment. In any such case, the service/system preferably provides information to each party about the other (e.g., interests and expertise, and why/how the match occurred). Particularly in the case of automatic initiation, the service/system preferably makes such provision in advance (e.g., prior to the call or at the outset of the connection with each party).
For a better understanding of the invention, and to show how the same may be carried into effect, reference will now be made, by way of example, to the accompanying drawings, in which
Turning to the Figures,
It is to be recognized that, although devices 14, 16 are shown separately from corresponding devices 26, 28, the functions of the respective devices may be provided via one apparatus, without departing from the principles of the invention. To illustrate, the devices 14 and 26, as well as the devices 16 and 28, may be integrated, e.g., as a Web-enabled digital cellular phone, and/or a connected personal computer with a speaker and microphone. Dotted lines 15 are set forth to indicate these configuration options.
The packet data network 18 typically is a packet switched network and preferably operates using open protocols. The network 18 generally is the Internet, but it can also comprise other publicly available networks, as well as private networks, such as a local area network (LAN) and/or an intranet. The packet data network 18 can also be a combination of these types of networks, or otherwise, so long as it provides the functions described herein.
The servers 20-22 may be variously implemented provided they support the functions described herein and, in particular, support the integration of voice communication and anonymity. Accordingly, servers 20-22 may be singular or plural in number.
The servers 20-22 preferably comprise Web servers implemented to host at least one and typically plural Web sites. Generally, such servers 20-22 host the front ends of such Web sites, which typically are otherwise independent (e.g. separately owned and/or operated) of the servers 20-22.
It is to be recognized that the servers 20-22, in providing a service to independent Web sites, may also be implemented to support (directly or indirectly) features, functions, services and applications other than the integration of voice and anonymity. That support reflects that the hosted Web sites may offer a variety of features, functions, services and applications (e.g., information marketplaces). These features, functions, services and applications may be recognized by users who access one or more of the Web pages typically comprising a hosted Web site. These features, functions, services and applications may also be unrecognized by (or even hidden from) users, such as, as examples, directory service, database inquiry, transaction processing, and security monitoring.
It is also to be recognized that the servers 20-22 may enable communication other than by voice. As such, the servers 20-22 may comprise email, fax, text messaging or other servers operating via packet data network 18. It is also to be recognized that the servers 20-22 may comprise gateways to the communication network 30, such as to provide voice messaging. In this latter example, the servers 20-22 may support either/both voice recognition (e.g., to acquire and identify all or part of incoming messages) and/or voice synthesis (e.g., to deliver messages with users, either in established network mailboxes or for personal delivery to the user or their message machine).
Controller unit 24 typically is implemented to manage and coordinate operation of the service/system so as to integrate voice communication and anonymity. In the case of an information marketplace, the unit 24 preferably provides for establishment of communication links between an initiator and an expert, particularly when the initiator requests voice communications, and while ensuring the anonymity of either/both the initiator and/or the expert.
Communication network 30 may be variously implemented. In one embodiment, the network 30 comprises a conventional, circuit-switched network (e.g., the public switched telephone network (“PSTN”)). In another embodiment, the network 30 comprises a packet-switched network, such as the Internet, supporting VoIP. In still another embodiment, the network 30 comprises a private data network which embodiment tends to provide an enhanced service level (e.g., quality of service). In yet another embodiment, the network 30 is optimized to employ a combination of one or more of the above-described embodiments, depending on factors such as what technologies are available to each user, quality of service needs, user convenience, costs incurred and fees charged (e.g., user-selected fee rates), and the like.
It is to be recognized that although the communication network 30 and packet data network 18 are illustrated as separate elements in
The above-described components of the service/system are coupled among one another by wired or wireless technologies, or both. From coupling to coupling, these technologies may comprise network equipment, such as, but not limited to, servers, modems, routers, bridges and gateways. Such network equipment is well known and understood by one of ordinary skill in that art and, as such, is not shown in
Various signals are transmitted between and among components of the service/system. The signals include transaction specification 32, connection instruction 34, reference code 36, and communication record 40.
Transaction specifications 32 include specifications, characteristics and other parameters (referred to sometimes hereafter, in the context of transaction specifications, individually and collectively as “parameters”) associated with and describing a proposed transaction. These parameters preferably include the type of product/service being exchanged, the quality of the product/service, fees or other price, if any (e.g., pre-agreed fees), delivery or appointment time(s), and other related requirements. These parameters preferably also includes an indication as to whether there is a request for anonymous voice communication and/or any other specification of whether the transaction is to comprise voice communication. These parameters may also include additional information sought by the service/system, such as to obtain information (a) omitted from submitted transaction specification(s), (b) related to submitted transaction specifications, (c) sought by the service/system, and/or (d) combinations of these. Additional information, as an example, may include data as to which user initiates an appointed transaction wherein voice communication is requested/accepted and/or the related contact information for use by the service/system to preserve anonymity in establishing the connection for the applicable communication.
Transaction specifications 32 may be obtained from various combinations of user(s). As one example, only one of the users 10, 12 provides a transaction specification 32 in connection with a particular transaction. In such case, a user that does not provide a specification 32 typically will have furnished the same, similar or sufficient information, in advance, to the service/system. That information preferably is relevant to transactions generally (e.g., fees, times available, etc.). Also, that information may be provided actively (e.g., by completing information requests of the service/system) or passively (e.g., by the service/system's collection of data and/or data mining of same in the context of the user's history of transactions). In having furnished such advance information, a user is relieved of providing a transaction specification 32. It is to be recognized, however, that this relief may be case-by-case (e.g., as to specific transactions, or parameters thereof, such as, a listed user) and/or time-to-time (e.g., as to transaction posed for certain time frames), such that, in any particular case or time, this user may ultimately submit a transaction specification 32 (e.g., when polled by the service/system).
In an alternative, one user may be relieved of providing a transaction specification because the system/server effectively provides that user's transaction specification. This circumstance may arise variously, e.g., based on the business model or other operation standards of the service/system. In a particular case of this alternative, the system/server or either/both users may establish that only the transaction specification 32 of the user initiating communication is to be obtained/recognized (e.g., in an information marketplace, the initiator's transaction specification 32 controls). In another particular case, the system/server or either/both users may establish that only the transaction specification 32 of the user sought for communication is to be obtained/recognized (e.g., in an information marketplace, the expert's transaction specification 32 controls). In any case, the relief may be case-by-case and/or time-to-time, as described above.
As an extension of the above, the service/system also supports operation wherein neither party provides transaction specifications 32. In accordance with the above, this extension responds to both users providing advance information relevant to transaction specifications 32. Based on that information (and perhaps responsive to observed patterns of a user's conduct, e.g., Web surfing), the service/system determines one or more transactions that may be available and/or appropriate to the users. Preferably, the service/system provides to each user the parameters of the transaction(s) available to the respective user (e.g., via servers 20-22, as Web-page content, as an email, as an instant message, as a fax (Internet- or POTS-based), and/or as a voice message). The service/system may be implemented to schedule a particular transaction, or suggest a schedule for same.
As another example, both users 10, 12 provide transaction specifications 32. This example admits various cases. In one case, the transaction specifications 32 are the same. This case applies where the specification have character-by-character congruence. This case also applies where one user acknowledges the other's specification, either explicitly or tacitly (e.g., where the specification is negotiated to agreement between the parties in advance, as described further below). This case yet also applies where one user abdicates, for whatever reason, to the other user's specification.
In another case, the transaction specifications are different. In this case, one or both user(s) may provide information, which is specific to that user or otherwise irrelevant to, outside the knowledge of, and/or not assigned by the service/system to be provided by, the other user. To illustrate, each user may provide a user name and/or contact information that differs from the other. To illustrate further, one user may provide data about the transaction that is required solely from that user by the service/system (e.g., in the context of an information marketplace, an expert is required to provide a curriculum as to the instant transaction). In either such case, the service/system may participate similar to as described above when one or no user provides transaction specifications 32 to relieve one or both users from having to provide certain information in the respective transaction specifications 32 (e.g., the same or different information for each user), including, or not, from case-to-case and time-to-time.
Transaction specification(s) 32 may also involve various processes. As an example, one or more users may submit a transaction specification 32 based on negotiation with the other user and/or the service/system. The negotiation may be conducted via a communication network (e.g., POTS or fax) and/or a packet data network (e.g., email and/or instant messaging) and/or otherwise. In one alternative, the negotiation may be conducted, in whole or in part, via the service/system. In one form of this alternative, the negotiation may be conducted via the transaction specifications 32, where these specifications are submitted and, as necessary, iteratively re-submitted by each of the negotiating users (and/or the service/system) toward reaching agreement. At the same time, the negotiation may be conducted via the service/system other than through use of the transaction specifications 32. In any case, any such negotiation preferably culminates in each submitting user's submission of a transaction specification that is final to the transaction.
In any case, a negotiation generally implicates some or all of the parameters of the transaction. Following negotiation of the implicated parameters, the submitting users preferably submit respective specifications 32 reflecting the agreements with the other users and/or service/system. If not all parameters are negotiated to agreement; the submitting users may submit the transaction specification 32 based on an implementation wherein the service/system arbitrates the undecided parameters. In such case, the service/system may be implemented not only to arbitrate the undecided parameters, but also to mediate agreement on such parameters (e.g., by providing alternatives of same to users), and/or to determine such parameters and/or to suggest changes or determine changes to otherwise agreed on parameters.
In the context of an information marketplace, an initiator and expert may engage in a negotiation process toward agreeing on the parameters of one information transaction (or plural information transactions), and submission of one or more specifications 32 relating to the information transaction. The negotiation may involve give and take by both participants. On the other hand, the negotiation may be straightforward, such as if the expert simply accepts the parameters proposed by the initiator, or vice versa (e.g., the initiator may accept all the parameters set forth by the expert via Web pages or otherwise via the service/system). In this context, the participants may submit separate-but-congruent transaction specifications, or they may submit only one transaction specification between them, with the non-submitting participant either acknowledging that specification (e.g., an express indication that the participant has reviewed and approved the specification) or not.
The transaction specification(s) 32 preferably are obtained through the packet data network 18. More specifically, the transaction specifications preferably are obtained via servers 20-22, e.g., as Web page content, as email, as instant message, as an Internet-based fax and/or otherwise. However, the transaction specifications may be obtained via the communication network 30, e.g., as POTS-based fax and/or as a voice message. In this latter aspect, the transaction specifications preferably are obtained and recognized automatically, e.g., through voice and or character recognition.
A connection instruction 34 provides information on a proposed connection between users 10, 12. A connection instruction's information may be variously configured, e.g., from service/system to service/system, or from type to type. As an example, a connection instruction 34 may include one or more of a connection's type (e.g., email, chat, voice, video, etc.), time frames (e.g., day/date for initiation and conclusion), connection process (e.g., which user(s) initiate, via what network(s) and how), charging method (e.g., by duration, connection time or fixed sum) and contact information (e.g., phone number, IP address, domain name, Web server information, security information, chat alias and/or email address). Generally, the connection instruction(s) 34 include contact information of at least one user in the proposed communication.
As an illustrative example, the servers 20-22 provide one or more connection instruction(s) 34 in association with an applicable transaction between users 10, 12. The servers 20-22 preferably generate connection instruction(s) 34 based on and/or responsive to one or more transaction specifications 32. The servers 20-22 may also generate connection instruction(s) 34 based on and/or responsive to information stored within the service/system, such as within databases associated with one or more servers 20-22 (e.g., user profile databases). This latter information may include, as non-exhaustive examples, either/both associated billing preferences and/or contact information.
The servers might not have access to the same transaction instruction(s) and/or the same information from other sources, including databases. Accordingly, a transaction may associate with plurality of connection instructions 34. These instructions may not be equivalent. Typically, however, they are complementary or supplementary of one another.
Also as an illustrative example, a connection instruction 34 is assembled from information extracted from one or more transaction specifications 32. In the specific case of transactions involving voice communication, one or more servers 20-22 extract information relevant to voice communication (e.g., voice communication request, connection time frame, payment method, who initiates the call, etc.) and assemble that information into one or more connection instructions 34. These connection instructions 34 may provide for voice communication in combination with one or more other forms of communication.
If the transaction specification 32 directs other than voice communication, the applicable servers 20-22 extract and assemble a connection instruction 34 relevant to that communication type. In this latter case, however, the service/system may also be implemented to provide connection instructions 34 that cover voice communication (i.e., even if not originally requested). To do so, the service/system may provide the information for voice communication either in a separate connection instruction or integrated in one connection instruction.
Servers 20-22 preferably forward connection instructions 34 to the controller unit 24. It is to be recognized that the controller unit 24 may receive connection instruction(s) from multiple, independent servers. It is also to be recognized that the controller unit 24 may be implemented to generate connection instructions, either instead of or in conjunction with the servers 20-22 (e.g., where transaction specifications are obtained via the communication network 30, e.g., as POTS-based fax subject to character recognition and/or as a voice messaging subject to voice recognition). In this latter case, the connection instructions 34 preferably are based on and/or responsive to one or more transaction specifications 32, together with or apart from information stored within the service/system, such as within databases associated with one or more servers 20-22 (e.g., user profile databases).
The controller unit 24 preferably stores the connection instruction(s) 34. The storage can be variously implemented, e.g., in format, duration and/or comprehensiveness. As an example, the storage may be terminated after the applicable communication is completed, so as to erase the associated information. As another example, only a portion of the storage may be terminated and/or some information archived, with any retained information used for various purposes, e.g., such as for billing or tracking purposes.
The controller unit 24 preferably also is implemented to generate one or more reference codes 36 in association with an applicable transaction between users 10, 12. The controller unit preferably generates the reference codes 36 based on and/or responsive to one or more connection instructions 34. In that, each reference code 36 preferably corresponds uniquely to the implicated connection instructions 34.
It is to be recognized that the controller unit 24 may also generate reference codes 36 based on and/or responsive to information stored within the service/system, such as within databases associated with the unit 24 and/or one or more servers 20-22 (e.g., user profile databases). This generation may be apart from or, preferably, together with one or more connection instructions 34.
It is also to be recognized that the controller unit 24 may be implemented to generate reference codes based on and/or responsive to information obtained directly from one or more transaction specifications 32. The unit 24 may so generate together with or apart from one, plural or all connection instructions 34. The unit 24 may so generate together with or apart from some or all information stored within the service/system (e.g., contact information).
In any case, reference codes 36 preferably are generated in association with transactions so as to uniquely correspond thereto. In particular, reference codes 36 preferably are generated to enable the connection process associated with transactions. In addition, reference codes 36 are generated to enable tracking of transactions. As to the latter, in information marketplaces, reference codes provide for tracking a user's information transactions and, in particular, enable identification and cataloging of such user's various information transactions. As previously described, tracking responds to the circumstance that a user will tend to have a history of transactions and, at any given time, may be involved in several transactions, with each such past and current transactions typically having different attributes and connection criteria. Tracking transactions preferably is implemented so as (a) to differentiate among transactions, even if the transactions are between the same two users and (b) to record, for each such transaction, the transaction's attributes, such as, but not limited to, the parameters and other information associated with transaction specifications and/or, if any, connection instructions and/or other service/system information (e.g., fees or other pricing, actual elapsed time).
Reference codes 36 may be variously implemented. In one implementation, reference codes 36 comprise one or more, and generally combinations of, letters, numbers and symbols. In other implementations, reference codes 36 may comprise graphics, images, video, and voice patterns, or combinations of these, with or without any letters, numbers or symbols. Reference codes may comprise one or more groups of the above, (e.g., if the reference code comprises a code body and password, it may be provided as one or two sets of numbers, letters, etc.). Reference codes may also be provided variously to user(s), including, as examples, visually (e.g., by screen display, printed document, video), audibly (e.g., by voice or voice mail) or by methods hidden from a user's perception.
In addition to generating reference codes 36, the controller unit 24 preferably also provides for storing such codes. The storage can be variously implemented, e.g., in format, duration and/or comprehensiveness. As an example, the storage may be terminated after the applicable communication is completed, so as to erase any or all associated information. As another example, only a portion of the storage may be terminated and/or some information archived, with any retained information used for various purposes, e.g., such as for billing or tracking purposes and/or so that reference codes can be recycled for use in future transactions. (Storage of reference codes is further described below in connection with reference code database 100.)
In addition to generating reference codes, the controller unit 24 preferably also provides for transmission of reference codes to one or more users in the applicable transaction. Preferably, the unit 24 so provides via the packet data network 18. As an illustrative example, the unit 24 so provides by furnishing the respective codes 36 to one or more selected servers 20-22, enabling the servers 20-22 to transmit the codes 36 to respective users 10, 12 via the network 18. The selected servers 20-22 may be Web servers, email servers, chat servers, Internet-fax servers or otherwise. In the case of a Web server, the user preferably is enabled to access the codes either audibly, visibly and/or in a secure, hidden form (e.g., so that only the system—preferably authenticated—recognizes and can act on all or certain of the codes).
It is to be recognized that the unit 24 may be implemented to provide the reference codes via the communication network 30, together with or apart from provision via the packet data network 18. In this implementation, the unit 24 preferably transmits the codes via a PSTN gateway (e.g., for voice or standard fax transmission). In voice transmission, the unit 24 typically employs voice synthesis for communication and, preferably, has access to voice mail, either PSTN-supported or via a subscriber's private answering machine. Provision of the reference codes via the communication network 30 may be together with, or apart from, provision of such codes via the packet data network 18.
In the provision of references codes 36 to users, various approaches may be taken, particularly based on enabled and/or applicable connection processes. In one example, an information marketplace may be implemented so that (a) the initiator receives a reference code, but the expert does not, or (b) the expert receives a reference code while the initiator does not, or (c) both parties receive the reference code, or (d) neither party receives the reference code (e.g., a form of immediate connection).
In their provision to users, the reference codes 36 typically enable the connection process. In one example of a connection process, one or more reference codes are provided together with contact information. In another example of a connection process, one caller may be volunteered, assigned or otherwise designated to initiate contact (the “designated caller”). The designated caller typically initiates contact with the other user via the controller unit 24, particularly through one or both of the packet data or communication networks 18, 30. In doing so, the designated caller typically submits their reference code. That submission may be accompanied, or not, by the other user submitting their reference code.
In the connection process, the submission of reference codes may be accomplished variously. As examples, a user may submit reference codes by voicing the reference code (e.g., via VoIP or POTS), by keying in the code (e.g., for Internet submission via chat, email, or the like, or for POTS submission via tone or pulse coding), or combination or otherwise.
The service/system receives the reference codes so entered by one or more users and determines whether the codes are proper. If the entered codes are proper, the service/system establishes connections (e.g., VoIP and/or telephone calls) between/among users. Codes may be proper under various criteria (e.g., all or part of the entered codes matches exactly another entered code (or part thereof) and/or matches such other entered code under predetermined criteria and/or matches exactly, matches under predetermined criteria or is otherwise in accord with code records).
The connection process typically includes, but is not limited to, receiving, storing, inputting and processing reference codes. Although the process above describes user input of reference codes, the connection process may be entirely or partially automated, e.g., by using a software program or hardware component in a user's communication device and/or in connection with the controller unit 24 or servers 20-22.
In the connection process, a controller unit 24 preferably retrieves connection instructions) 34 associated with a transaction identified to a received reference code. The connection instructions 34 typically are previously stored in a database associated with the unit 24 and/or with one or more servers 20-22. The connection instructions 34 are retrieved so as to enable connection management (e.g., by the controller unit 24) of the connection associated with the received reference code.
In an example of management by the unit 24, the unit 24 connects the designated caller to the called party using contact information. In another example, the controller unit may reject the designated caller's request for voice connection with the other transacting party if the calling time does not satisfy a pre-agreed calling time frame. In yet another example, the controller unit 24 generates communication records 40. The unit 24 typically generates such records, e.g., during the connection, via monitoring the transaction (e.g., particularly voice communications supporting anonymity). The communication records 40 typically include various data associated with transactions, e.g., the identities of communicating parties, billing information, transaction reference code (for the purpose of identifying each specific transaction), the starting time and duration of the communication, among other data.
PSTN gateways 52 provide an interface between the PSTN 58 and the Internet 50. The PSTN gateways 52 preferably provide a voice grade interface. The PSTN gateways 52 typically comprise one or more computers, switches and/or similar equipment for processing telephone calls. The PSTN gateways typically perform various functions such as (a) the conversion and compression of analog signals from the PSTN to digital signals for transmission via the Internet 50 and (b) decompression and conversion of digital signals received via the Internet 50 into analog signals for transmission via the PSTN.
In
Wireless terminals 64, 74 illustrate other implementations of voice-enabled devices 26, 28. Wireless terminals 64, 74 may comprise any of screen phones, smart and/or super phones, or wireless PDAs, or other similar device. Wireless terminals 64, 74 communicate with base stations 62. Base stations 62 typically are fixed in location for communicating with wireless terminals within a specific geographical range. Within that specific geographic range, base stations 62 may also be responsible for coordinating all wireless terminals 64, 74.
In turn, the base stations 62 communicate with a mobile switching office (MSO) 60. The MSO generally is responsible for coordinating activities between different base stations 62. The MSO 60 is connected to PSTN 58 for landline communications.
Personal computers (PCs) 68, 76 illustrate still other implementations of voice-enabled devices 26, 28. PCs 68, 76 typically comprise desktop or notebook computers equipped with voice input/output devices and various software, including application and utility programs directed to communication. PCs 68, 76 typically also include a communication interface, including, as examples, a modem, ISDN card and/or LAN interface card. Via respective such communication interfaces, PCs 68, 76 are connected to the Internet through Internet access point(s) 66. Internet access points 66 generally provide protocol conversions, as necessary, for two-way data communication over the Internet. For example, an Internet access point 66 may comprise multiple modems coupled to an Internet router, the router providing a ramp with the Internet.
In a communication network 30 configured as in
The communication network 30 of
Voice processing system 89 preferably performs one or both of voice recognition and speech synthesis. The system's synthesis of speech typically is to articulate voice prompts (e.g., relating or according to text commands). The system's recognition of voice typically is to enable the controller unit 24 to respond to users' voiced input. That is, with voice recognition, users are enabled to input, e.g., spoken requests for connection and/or input of reference codes, such as in the form of voiced numbers, letters and words. Where both synthesis and recognition are implemented, users may interact with the controller unit 24 through voice communication, whether the conduit is packet data network 18 or communication network 30.
Network interfaces 96 generally enable communication between, on the one hand, controller unit 24 and, on the other hand, networks 18, 30 and/or other elements of an implemented service/system with which the unit 24 interfaces, whether directly or indirectly. The interfaces 96 preferably comprise network adapter infrastructure and, as such, provide various signal conditioning/conversion functions. The interfaces 96 typically handle one or more data types, including, as examples, analog, digital, broadband, wireless, and optical data.
Data storage component 98 preferably includes a plurality of databases. Such databases may enable communications, as contemplated herein. Accordingly, one or more databases may be employed in connection with, and/or for the purposes of, scheduling, organizing, establishing, maintaining, tracking and/or otherwise enabling a transaction.
The databases preferably include one or more of the following: reference code database 100, connection instruction database 102 and communication records database 104. Communication record database 104 may be implemented to provide various functions, including, as an example, storing communication records 40 for selected current and previous transactions. The database 104 may also be implemented to store other information, including, as examples, one or more of user codes, contact codes, connect criteria based on contact codes, and/or analytical data, all as described above.
Reference code database 100 may be implemented to provide various functions, including, as examples: storing reference codes 36 that are reserved or otherwise assigned, tracking reference codes that are in current use, identifying reference codes 36 that are to be deleted or otherwise terminated (e.g., after the scheduled transaction or expiration of some other period of time), identifying or determining reference codes that are recyclable or otherwise available for use, and otherwise maintaining reference codes 36.
Connection instruction database 102 preferably stores connection instructions and/or contact information. The database 102 may be implemented to store only such contact information of users available for voice communication service. However, the database 102 preferably is implemented to store contact information for any user available for communication through the service/system. The database 102 may also be implemented to store other information, including, as examples, one or more of user codes, contact codes, connect criteria based on contact codes, and/or analytical data, all as described above.
The data storage component 98 may also be implemented to support other databases, including outside the controller unit 24. Such databases may store or provide for information, including, as examples, user codes, contact codes, connect criteria based on contact codes, and/or analytical data, all as described above.
In an example embodiment employing each of the databases 100, 102, 104, reference code database 100 stores reference codes 36 that are applied to index some or all of the information stored in either/both of connection instruction database 102 and communication records database 104. As such, the reference codes are employed for storing, retrieving and/or updating of transaction information of implicated databases 102, 104. In operation under this embodiment, processor 82 uses reference code(s) 36 to generate one or more queries of data storage component 98 so as to retrieve information pertaining to that reference code and relevant to the query, such as information from or relating to connection instructions 34 and/or communication records 40.
Although controller unit 24 is illustrated using the elements depicted in
An example context for users conducting on-line transactions is an information marketplace. There, as also described above, a user is an initiator if they post an inquiry. In connection with the posting, the initiator may also include related requirements, such as a price target or maximum, a quality characteristic, a preferred delivery method, etc. The initiator generally posts on a virtual bulletin board, e.g., supported via the Internet. The initiator typically receives a response from one or more other participants (e.g., experts) in the marketplace, which generally is directed to the initiator's requirements, e.g., by providing a bid. The initiator may select none, one or more of the experts, typically at their sole discretion. The initiator may also continue the on-line transaction(s) with one or more of the experts toward negotiating a transaction specification 32 and, if that is satisfactorily accomplished, possibly selecting the expert.
In this example process, users involved in a transaction (“transacting users”) submit, in step 112, a mutually agreed transaction specification 32. As described above, that submission preferably is via servers 20, 22 (e.g., Web servers).
In step 116, the example process tests for whether the transaction specification 32 includes a request for anonymous voice communication (e.g., via immediate or later-scheduled connection). If anonymous voice communication is not requested, the transaction proceeds by other means, as indicated by step 118. If anonymous voice communication is requested, server 20, 22 passes, in step 120, one or more connection instructions 34 to controller unit 24. In step 122, controller unit 24 stores the connection instruction 34 (e.g., in connection instruction database 102). In step 122, controller unit 24 generates a reference code 36 associated with the transaction implicated by the connection instruction 34. It is to be understood that, while the controller unit 24 is described for this example process as, in the same step, both storing the instruction 34 and generating the code 36, the unit 24 may (a) perform those functions in separate steps and (b) may generate the code 36 in the absence of the storing activity.
In step 124, the reference code is delivered to one or both of the transacting users (a “confirmation”). In an illustrative case, confirmations include contact information. In another illustrative case, confirmations may be delivered only to a transacting user assigned to initiate the communication (e.g., the designated caller in the information marketplace context). Confirmations preferably are delivered through packet data network 18, as previously described.
In step 126, the user assigned to place the call (e.g., the designated caller) manually records the confirmation. For example, the user records some or all of the confirmation by writing it down, printing it out and/or storing it in memory.
In step 130, the assigned user initiates the connection process. The user typically does so by contacting controller unit 24 using a voice enabled device 26, 28 (e.g., via a voice interface) or using an Internet enabled device 14, 16 (e.g., via entries in a Web page).
In step 132, the assigned user is prompted to enter the reference code applicable to the transaction. In step 134, the controller unit 24 receives the reference code so input by the assigned user and retrieves the connection instruction 34 associated with that reference code. In an example case, the controller unit 24 retrieves that connection instruction 34 from connection instruction database 102.
In step 136, controller unit 24 tests whether connection criteria of the connection instruction are satisfied. This testing preferably includes verification of the initiating user's identity and agreement with the connection's scheduled time. If the connection criteria are not met, the connection is rejected, in step 138. Following such rejection, the service/system may be implemented to provide, as a step 139, notice to the called party of the rejected connection. Such notice, if implemented at all, may comprise the identity of the initiating user (or, at least, of the proper initiating user), details of the scheduled transaction/connection, and the basis for rejecting the connection.
If the connection criteria are satisfied, the process proceeds to step 144 wherein the controller unit 24 routes the call to the called party.
Alternatively to step 126, the confirmation may be stored automatically (i.e., without the user's action). Such storage typically is provided using a hardware, firmware and/or software (collectively, the “connection program”).
The connection program preferably is implemented not only to automatically store the confirmation, but also to automatically retrieve all or part of the confirmation. In so retrieving, the connection program preferably either/both reminds the user of the connection (step 140) and/or obtains the user's authorization to automatically initiate the connection at the scheduled time, including by providing the reference code (step 142). Steps 140 and 142, in an example case, may be implemented in a device that is both packet- and voice-enabled, e.g., an Internet-enabled cellular phone (hereafter referred to as a “dual-enabled device”).
It is to be recognized that, in a fully automated system, step 140 may be selectable (e.g., by the user) or may be omitted. If selectable, step 140 may be made variously configurable. For example, the user may be enabled to configure the connection program to provide one or more reminders of the scheduled connection time. The user may also be enabled to determine whether to proceed with connection.
The service/system may also be implemented to support dual modes: one mode providing for manual reception and treatment of confirmations and another mode providing for automatic connections. In this implementation, if a user requests immediate connection in a transaction specification 32 (i.e., in step 112), the connection program immediately processes the connection, doing so automatically and in real time. This implementation provides that later scheduled (not immediate connection) transactions may proceed manually. In that alternative, this implementation may provide that a user may select manual or automatic, or both (e.g., automatic confirmation reception and reminders, but manual connection initiation), such as on a transaction by transaction base.
In step 144, controller unit 24 routes the call to the called party. The unit 24 preferably is enabled to do so via contact information provided in the associated connection instruction(s) and stored in the connection instruction database 102.
In step 146, the service/system tests whether a connection is established. If the called party cannot be contacted in accordance with the connection instructions, controller unit 24 may be implemented to provide further assistance, as step 148. In one example of further assistance, the unit 24 requests that the caller call again. The controller unit 24 may do so with a suggested time (e.g., based on information about the called party's schedule, whether maintained in storage or obtained at the time of the connection). The controller unit 24 preferably also notifies the called party, e.g., of the attempted connection and/or of the suggested time for the later call.
With connection established between the parties, the controller unit 24 preferably generates transaction logs, as step 150. Information being logged may include, as examples in step 152, the identity of communicating parties, billing information, reference codes (e.g., for the purpose of identifying the transaction), connection time, conversation duration, and satisfaction rating of each party. The logs preferably are stored in communication records database 104.
In step 154, connection reports are transmitted to servers 20, 22. At least some reports preferably are formulated based on the transaction logs. The servers 20, 22 (e.g., Web servers) employ the reports for, among other purposes, billing and record keeping.
As previously described,
As previously described,
Accordingly, the subject matter of this application is directed to privacy concerns through the establishment, maintenance and control of anonymity in the context of voice communication. To illustrate, the subject matter is directed to establishing, maintaining and controlling anonymity on the part of users and experts alike in information markets, particularly information markets involving the Internet.
In another aspect, the subject matter of this application is directed, in one aspect, to integrating voice communication and anonymity. That is, the subject matter is directed to enabling parties involved in an online transaction to communicate by voice while selectively preserving anonymity; e.g. each party can select what, if any, personal information is disclosed to the other.
In yet another aspect, the subject matter of this application is directed to establishing and controlling anonymity at the time of non-voice communication involving the Internet, then controlling and maintaining that anonymity for voice communication, whether that communication is transmitted via the Internet or other packet-switched technologies or that communication is transmitted via circuit switched technologies and services, such as PSTN/POTS.
The foregoing embodiments and features are for illustrative purposes and are not intended to be limiting persons skilled in the art capable of appreciating other embodiments from the scope and spirit of the foregoing teachings.
It will be appreciated that the invention is not restricted to the particular embodiment that has been described, and that variations may be made therein without departing from the scope of the invention as defined in the appended claims and equivalents thereof. Unless the context indicates otherwise, a reference in a claim to the number of instances of an element, be it a reference to one instance or more than one instance, requires at least the stated number of instances of the element but is not intended to exclude from the scope of the claim a structure or method having more instances of that element than stated.
This application claims benefit of Provisional Application No. 60/230,021 filed Sep. 5, 2000, the entire disclosure of which is hereby incorporated by reference herein for all purposes. This is a continuation reissue application of application Ser. No. 13/371,318 filed on Feb. 10, 2012, which is to issue on Dec. 12, 2017 as Reissue U.S. Pat. No. RE46,637, which is a continuation reissue application of application Ser. No. 12/199,647 filed on Aug. 27, 2008 and issued on Feb. 14, 2012 as Reissue U.S. Pat. No. RE43,181, which is a reissue application of U.S. Pat. No. 7,099,304 issued on Aug. 29, 2006 for application Ser. No. 09/947,116 filed on Sep. 4, 2001, which claims the benefit of Provisional Application No. 60/230,021 filed on Sep. 5, 2000. The entire disclosure of Provisional Application No. 60/230,021 is hereby incorporated by reference for all purposes. This reissue application is also related to the following reissue applications: Ser. No. 12/199,631 filed on Aug. 27, 2008 and issued on Oct. 11, 2011 as U.S. Pat. No. RE42,828; Ser. No. 12/199,711 filed on Aug. 27, 2008 and issued on Jul. 6, 2010 as U.S. Pat. No. RE41,416; Ser. No. 12/200,014 filed on Aug. 28, 2008 and issued on Aug. 10, 2010 as U.S. Pat. No. RE41,487; Ser. No. 12/200,148 filed on Aug. 28, 2008 and issued on Aug. 17, 2010 as U.S. Pat. No. RE41,532; Ser. No. 12/200,305 filed on Aug. 28, 2008 and issued on Sep. 14, 2010 as U.S. Pat. No. RE41,689; and Ser. No. 12/200,645 filed on Aug. 28, 2008 and issued on Oct. 26, 2010 as U.S. Pat. No. RE41,882.
| Number | Name | Date | Kind |
|---|---|---|---|
| 3648254 | Beausoleil | Mar 1972 | A |
| 3883693 | Moore | May 1975 | A |
| 3909562 | Lager | Sep 1975 | A |
| 4757267 | Riskin | Jul 1988 | A |
| 4847890 | Solomon et al. | Jul 1989 | A |
| 4878239 | Solomon et al. | Oct 1989 | A |
| 4899373 | Lee et al. | Feb 1990 | A |
| 5058152 | Solomon et al. | Oct 1991 | A |
| 5247571 | Kay et al. | Sep 1993 | A |
| 5353331 | Emery et al. | Oct 1994 | A |
| 5361295 | Solomon et al. | Nov 1994 | A |
| 5559868 | Blonder | Sep 1996 | A |
| 5751966 | Dauerer et al. | May 1998 | A |
| 5751968 | Cohen | May 1998 | A |
| 5754636 | Bayless et al. | May 1998 | A |
| 5754938 | Herz et al. | May 1998 | A |
| 5757267 | Xydis | May 1998 | A |
| 5761279 | Bierman et al. | Jun 1998 | A |
| 5796393 | MacNaughton et al. | Aug 1998 | A |
| 5797099 | Ejzak et al. | Aug 1998 | A |
| 5805677 | Ferry et al. | Sep 1998 | A |
| 5809114 | Solomon et al. | Sep 1998 | A |
| 5809224 | Schultz et al. | Sep 1998 | A |
| 5818836 | DuVal | Oct 1998 | A |
| 5825771 | Cohen et al. | Oct 1998 | A |
| 5845266 | Lupien et al. | Dec 1998 | A |
| 5864612 | Strauss et al. | Jan 1999 | A |
| 5907604 | Hsu | May 1999 | A |
| 5907677 | Glenn et al. | May 1999 | A |
| 5910946 | Csapo | Jun 1999 | A |
| 5918010 | Appleman et al. | Jun 1999 | A |
| 5933811 | Angles et al. | Aug 1999 | A |
| 5933827 | Cole et al. | Aug 1999 | A |
| 5948061 | Merriman et al. | Sep 1999 | A |
| 5956020 | D'Amico et al. | Sep 1999 | A |
| 5974148 | Stambler | Oct 1999 | A |
| 5983200 | Slotznick | Nov 1999 | A |
| 5991735 | Gerace | Nov 1999 | A |
| 6011794 | Mordowitz et al. | Jan 2000 | A |
| 6038433 | Vegt | Mar 2000 | A |
| 6067347 | Farris et al. | May 2000 | A |
| 6069890 | White et al. | May 2000 | A |
| 6072780 | Johnson, Jr. et al. | Jun 2000 | A |
| 6081788 | Appleman et al. | Jun 2000 | A |
| 6108004 | Medl | Aug 2000 | A |
| 6148067 | Leipow | Nov 2000 | A |
| 6167432 | Jiang | Dec 2000 | A |
| 6175619 | DeSimone | Jan 2001 | B1 |
| 6243398 | Kahane et al. | Jun 2001 | B1 |
| 6253203 | O'Flaherty | Jun 2001 | B1 |
| 6259538 | Amit et al. | Jul 2001 | B1 |
| 6266668 | Vanderveldt et al. | Jul 2001 | B1 |
| 6285983 | Jenkins | Sep 2001 | B1 |
| 6285987 | Roth et al. | Sep 2001 | B1 |
| 6317722 | Jacobi et al. | Nov 2001 | B1 |
| 6332153 | Cohen | Dec 2001 | B1 |
| 6353660 | Burger et al. | Mar 2002 | B1 |
| 6366298 | Haitsuka et al. | Apr 2002 | B1 |
| 6421669 | Gilmour et al. | Jul 2002 | B1 |
| 6434599 | Porter | Aug 2002 | B1 |
| 6445681 | Pogrebinsky | Sep 2002 | B1 |
| 6473738 | Garrett | Oct 2002 | B1 |
| 6496857 | Dustin et al. | Dec 2002 | B1 |
| 6519541 | Bitton | Feb 2003 | B1 |
| 6556313 | Chang et al. | Apr 2003 | B1 |
| 6587835 | Treyz et al. | Jul 2003 | B1 |
| 6594254 | Kelly | Jul 2003 | B1 |
| 6651086 | Manber et al. | Nov 2003 | B1 |
| 6661793 | Pogrebinsky | Dec 2003 | B1 |
| 6665389 | Haste, III | Dec 2003 | B1 |
| 6671068 | Chang et al. | Dec 2003 | B1 |
| 6678663 | Mayo | Jan 2004 | B1 |
| 6694003 | Karam | Feb 2004 | B1 |
| 6701009 | Makoto et al. | Mar 2004 | B1 |
| 6711158 | Kahane et al. | Mar 2004 | B1 |
| 6714519 | Luzzatti et al. | Mar 2004 | B2 |
| 6725191 | Mecayten | Apr 2004 | B2 |
| 6732161 | Hess | May 2004 | B1 |
| 6753978 | Chang | Jun 2004 | B1 |
| 6754181 | Elliott et al. | Jun 2004 | B1 |
| 6785301 | Chapman et al. | Aug 2004 | B1 |
| 6801952 | Belzile | Oct 2004 | B2 |
| 6845448 | Chaganti et al. | Jan 2005 | B1 |
| 6859228 | Chang et al. | Feb 2005 | B1 |
| 6876734 | Summers et al. | Apr 2005 | B1 |
| 6879994 | Matsliach et al. | Apr 2005 | B1 |
| 6889213 | Douvikas et al. | May 2005 | B1 |
| 6931403 | Agrawal et al. | Aug 2005 | B1 |
| 6947995 | Chang et al. | Sep 2005 | B2 |
| 7039040 | Burg | May 2006 | B1 |
| 7099304 | Liu et al. | Aug 2006 | B2 |
| 7142506 | Pogrebinsky | Nov 2006 | B1 |
| 7143356 | Shafrir et al. | Nov 2006 | B1 |
| 7158986 | Oliver et al. | Jan 2007 | B1 |
| 7318086 | Chang et al. | Jan 2008 | B2 |
| 7353251 | Balakrishnan | Apr 2008 | B1 |
| 7424439 | Fayyad et al. | Sep 2008 | B1 |
| 7609402 | Chang et al. | Oct 2009 | B2 |
| RE41416 | Liu et al. | Jul 2010 | E |
| RE41487 | Liu et al. | Aug 2010 | E |
| RE41532 | Liu et al. | Aug 2010 | E |
| RE41689 | Liu et al. | Sep 2010 | E |
| 7805720 | Chang et al. | Sep 2010 | B2 |
| RE41882 | Liu et al. | Oct 2010 | E |
| 7908401 | Chang | Mar 2011 | B2 |
| 7941541 | Chang et al. | May 2011 | B2 |
| 7944577 | Chang et al. | May 2011 | B2 |
| 7953818 | Chang et al. | May 2011 | B2 |
| RE42725 | Chang et al. | Sep 2011 | E |
| RE42828 | Liu et al. | Oct 2011 | E |
| RE43181 | Liu et al. | Feb 2012 | E |
| 8169649 | Chang et al. | May 2012 | B2 |
| 8184324 | Chang et al. | May 2012 | B2 |
| 8285802 | Chang et al. | Oct 2012 | B2 |
| 8296757 | Chang et al. | Oct 2012 | B2 |
| 8332521 | Chang et al. | Dec 2012 | B2 |
| 8533352 | Chang | Sep 2013 | B2 |
| 8595717 | Chang | Nov 2013 | B2 |
| 8630000 | Chang et al. | Jan 2014 | B2 |
| 8705097 | Chang et al. | Apr 2014 | B2 |
| 8711408 | Chang et al. | Apr 2014 | B2 |
| 8964220 | Chang et al. | Feb 2015 | B2 |
| 8972610 | Chang | Mar 2015 | B2 |
| 8989064 | Chang et al. | Mar 2015 | B2 |
| 9015329 | Chang et al. | Apr 2015 | B2 |
| 9036181 | Chang et al. | May 2015 | B2 |
| 9037088 | Chang et al. | May 2015 | B2 |
| 9042811 | Chang et al. | May 2015 | B2 |
| 9043482 | Chang | May 2015 | B2 |
| 9069510 | Chang et al. | Jun 2015 | B2 |
| 9092177 | Chang et al. | Jul 2015 | B2 |
| 9110622 | Chang et al. | Aug 2015 | B2 |
| 9116723 | Chang et al. | Aug 2015 | B2 |
| 9164718 | Chang et al. | Oct 2015 | B2 |
| 9298407 | Chang | Mar 2016 | B2 |
| 9383956 | Chang et al. | Jul 2016 | B2 |
| 9389822 | Chang et al. | Jul 2016 | B2 |
| 10126991 | Chang et al. | Nov 2018 | B2 |
| 10133527 | Chang et al. | Nov 2018 | B2 |
| 10140071 | Chang et al. | Nov 2018 | B2 |
| 10140072 | Chang et al. | Nov 2018 | B2 |
| 10140073 | Chang et al. | Nov 2018 | B2 |
| 20010011247 | O'Flaherty | Aug 2001 | A1 |
| 20010011264 | Kawasaki | Aug 2001 | A1 |
| 20020004900 | Patel | Jan 2002 | A1 |
| 20020104015 | Barzilai et al. | Aug 2002 | A1 |
| 20020141003 | Chang et al. | Oct 2002 | A1 |
| 20030041143 | Ronald et al. | Feb 2003 | A1 |
| 20040127254 | Chang | Jul 2004 | A1 |
| 20050122965 | Heinla et al. | Jun 2005 | A1 |
| 20080318602 | Chang et al. | Dec 2008 | A1 |
| 20090002760 | Chang et al. | Jan 2009 | A1 |
| 20090070411 | Chang et al. | Mar 2009 | A1 |
| 20100201996 | Chang et al. | Aug 2010 | A1 |
| 20100203824 | Chang et al. | Aug 2010 | A1 |
| 20100227550 | Chang et al. | Sep 2010 | A1 |
| 20110016280 | Chang et al. | Jan 2011 | A1 |
| 20110034150 | Chang et al. | Feb 2011 | A1 |
| 20110035682 | Chang et al. | Feb 2011 | A1 |
| 20110138378 | Chang et al. | Jun 2011 | A1 |
| 20110167166 | Chang | Jul 2011 | A1 |
| 20110167175 | Chang | Jul 2011 | A1 |
| 20110197159 | Chaganti et al. | Aug 2011 | A1 |
| 20110211226 | Chang et al. | Sep 2011 | A1 |
| 20110279829 | Chang et al. | Nov 2011 | A1 |
| 20110279863 | Chang et al. | Nov 2011 | A1 |
| 20120230315 | Chang et al. | Sep 2012 | A1 |
| 20120258700 | Chang et al. | Oct 2012 | A1 |
| 20130095887 | Chang et al. | Apr 2013 | A1 |
| 20130103775 | Chang et al. | Apr 2013 | A1 |
| 20130104052 | Chang et al. | Apr 2013 | A1 |
| 20130109353 | Chang et al. | May 2013 | A1 |
| 20140018130 | Chang et al. | Jan 2014 | A1 |
| 20140082604 | Chang et al. | Mar 2014 | A1 |
| 20150356561 | Chang et al. | Dec 2015 | A1 |
| 20150356564 | Chang et al. | Dec 2015 | A1 |
| 20150356565 | Chang et al. | Dec 2015 | A1 |
| 20150363763 | Chang et al. | Dec 2015 | A1 |
| 20150381612 | Chang et al. | Dec 2015 | A1 |
| 20160011836 | Chang et al. | Jan 2016 | A1 |
| 20160174068 | Chang et al. | Jun 2016 | A1 |
| 20160239232 | Chang et al. | Aug 2016 | A1 |
| 20160239243 | Chang et al. | Aug 2016 | A1 |
| Number | Date | Country |
|---|---|---|
| 1118950 | Jul 2001 | EP |
| 2332764 | Jun 1999 | GB |
| Entry |
|---|
| US RE41,123 E, 02/2010, Liu et al. (withdrawn) |
| US 7,814,209 B2, 10/2010, Chang et al. (withdrawn) |
| US 8,396,977 B2, 03/2013, Chang (withdrawn) |
| US 9,008,572 B2, 04/2015, Chang et al. (withdrawn) |
| U.S. Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 12/783,504, dated Nov. 7, 2014, 45 pages. |
| U.S. Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 12/764,015, dated Dec. 18, 2014, 29 pages. |
| U.S. Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 14/021,974, dated Dec. 19, 2014, 24 pages. |
| U.S. Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 10/734,481, dated Dec. 23, 2014, 15 pages. |
| U.S. Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 10/053,765, dated Dec. 29, 2014, 50 pages. |
| U.S. Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 12/764,032, dated Dec. 31, 2014, 38 pages. |
| U.S. Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 13/476,947, dated Jan. 8, 2015, 55 pages. |
| U.S. Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 13/708,607, dated Jan. 14, 2015, 66 pages. |
| U.S. Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 13/710,306, dated Jan. 21, 2015, 42 pages. |
| U.S. Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 13/864,000, dated Dec. 19, 2014, 7 pages. |
| U.S. Patent and Trademark Office, Office Action for U.S. Appl. No. 13/371,318, dated Mar. 21, 2013, 21 pages. |
| U.S. Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 13/371,318, dated Nov. 8, 2013, 16 pages. |
| U.S. Patent and Trademark Office, Office Action for U.S. Appl. No. 13/371,318, dated Mar. 13, 2014, 19 pages. |
| U.S. Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 13/371,318, dated Jul. 30, 2014, 12 pages. |
| U.S. Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 13/371,318, dated Nov. 21, 2014, 15 pages. |
| U.S. Patent and Trademark Office, Office Action for U.S. Appl. No. 13/371,318, dated Mar. 5, 2015, 16 pages. |
| U.S. Patent and Trademark Office, Office Action for U.S. Appl. No. 13/371,318, dated Jun. 26, 2015, 26 pages. |
| U.S. Patent and Trademark Office, Office Action for U.S. Appl. No. 13/371,318, dated Oct. 23, 2015, 14 pages. |
| U.S. Patent and Trademark Office, Office Action for U.S. Appl. No. 13/371,318, dated Mar. 9, 2016, 24 pages. |
| U.S. Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 13/371,318, dated Jul. 7, 2016, 19 pages. |
| U.S. Patent and Trademark Office, Office Action for U.S. Appl. No. 13/371,318, dated Nov. 25, 2016, 16 pages. |
| U.S. Patent and Trademark Office, Office Action for U.S. Appl. No. 13/371,318, dated Mar. 9, 2017, 9 pages. |
| U.S. Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 13/371,318, dated Jul. 25, 2017, 11 pages. |
| VocalTec, Ltd, “VocalTec Internet Phone Release 4 Help topics”, copyright 1993-1996, 77 pages. |
| VocalTec, Ltd, Screen Images from Internet Phone Release 4 software, copyright 1993-1996, 19 pages. |
| VocalTec, Ltd., “VocalTec Internet Phone Readme: Release 4 for Windows 95”, Jun. 7, 1996, 3 pages. |
| CTI for Management Buyer's Guide, “Internet Phone Release 4 VocalTec Ltd”, 1996/1997, pp. 28-32. |
| Hoshi et al, “Voice Stream Multiplexing between IP telephony Gateways”, IEICE TRANS_ INF_ & SYS, Apr. 4, 1999, vol. E82-D, No. 4, pp. 838-845. |
| Dodd, Annabel Z., “The Essential Guide to Telecommunications,” 1999, Chapters 8-10, Prentiss-Hall, 62 pages. |
| Production documents, No. FLE000103-FLE000114 relating to web pages from www.exp.com, Aug. 6, 2000, 12 pages. |
| Production documents, No. FLE000087-FLE000102 relating to web pages from www.keen.com, Aug. 6, 2000, 16 pages. |
| Cleveland, Kristin L., of Klarquist Sparkman, LLP, “Skype's Objections and Responses to Plaintiffs 1st Set of Interrogatories,” May 5, 2008, 18 pages. |
| U.S. Patent and Trademark Office, Office Action regarding U.S. Appl. No. 12/199,647, dated Mar. 13, 2009, 28 pages. |
| U.S. Patent and Trademark Office, Office Action regarding U.S. Appl. No. 12/199,631, dated Mar. 13, 2009, 23 pages. |
| U.S. Patent and Trademark Office, Office Action regarding U.S. Appl. No. 12/200,014, dated Mar. 13, 2009, 16 pages. |
| U.S. Patent and Trademark Office, Office Action regarding U.S. Appl. No. 12/200,148, dated Mar. 13, 2009, 26 pages. |
| U.S. Patent and Trademark Office, Office Action regarding U.S. Appl. No. 12/200,305, dated Mar. 13, 2009, 14 pages. |
| U.S. Patent and Trademark Office, Office Action regarding U.S. Appl. No. 12/200,645, dated Mar. 13, 2009, 15 pages. |
| U.S. Patent and Trademark Office, Office Action regarding U.S. Appl. No. 12/199,711, dated Apr. 3, 2009, 16 pages. |
| Zachary, Michael N., of Klarquist Sparkman, LLP and Heuser, Peter E., of Kolisch Hartwell, PC., “Stipulation and Order of Dismissal with Prejudice”, Apr. 21, 2009, 4 pages. |
| U.S. Patent and Trademark Office, Office Action regarding U.S. Appl. No. 12/199,631, dated Aug. 17, 2009, 25 pages. |
| U.S. Patent and Trademark Office, Office Action regarding U.S. Appl. No. 12/200,645, dated Aug. 17, 2009, 21 pages. |
| U.S. Patent and Trademark Office, Office Action regarding U.S. Appl. No. 12/200,305, dated Aug. 20, 2009, 21 pages. |
| U.S. Patent and Trademark Office, Notice of Allowance regarding U.S. Appl. No. 12/199,647, dated Sep. 3, 2009, 30 pages. |
| U.S. Patent and Trademark Office, Notice of Allowance regarding U.S. Appl. No. 12/199,711, dated Jan. 29, 2010, 8 pages. |
| U.S. Patent and Trademark Office, Notice of Allowance regarding U.S. Appl. No. 12/200,014, dated Mar. 24, 2010, 5 pages. |
| U.S. Patent and Trademark Office, Notice of Allowance regarding U.S. Appl. No. 12/200,148, dated Mar. 24, 2010, 4 pages. |
| U.S. Patent and Trademark Office, Office Action regarding U.S. Appl. No. 12/199,647, dated Apr. 13, 2010, 29 pages. |
| U.S. Patent and Trademark Office, Notice of Allowance regarding U.S. Appl. No. 12/200,305, dated Apr. 28, 2010, 29 pages. |
| U.S. Patent and Trademark Office, Notice of Allowance regarding U.S. Appl. No. 12/200,645, dated Jul. 13, 2010, 30 pages. |
| U.S. Patent and Trademark Office, Office Action regarding U.S. Appl. No. 12/199,647, dated Sep. 16, 2010, 45 pages. |
| U.S. Patent and Trademark Office, Office Action regarding U.S. Appl. No. 12/199,647, dated Feb. 2, 2011, 21 pages. |
| U.S. Patent and Trademark Office, Office Action regarding U.S. Appl. No. 12/199,631, dated Feb. 10, 2011, 19 pages. |
| U.S. Patent and Trademark Office, Notice of Allowance regarding U.S. Appl. No. 12/199,631, dated Jul. 14, 2011, 16 pages. |
| U.S. Patent and Trademark Office, Notice of Allowance regarding U.S. Appl. No. 12/199,647, dated Sep. 20, 2011, 24 pages. |
| U.S. Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 12/764,015, dated Apr. 4, 2014, 54 pages. |
| U.S. Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 12/764,032, dated Apr. 24, 2014, 65 pages. |
| U.S. Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 12/764,015, dated Apr. 28, 2014, 51 pages. |
| U.S. Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 10/053,765, dated May 9, 2014, 64 pages. |
| U.S. Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 13/477,987, dated Jun. 6, 2014, 26 pages. |
| U.S. Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 13/103,958, dated Jun. 18, 2014, 8 pages. |
| U.S. Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 09/992,413, dated Jun. 19, 2014, 69 pages. |
| U.S. Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 11/929,445, dated Jun. 25, 2014, 61 pages. |
| U.S. Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 10/734,481, dated Aug. 27, 2014, 23 pages. |
| U.S. Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 13/864,000, dated Aug. 29, 2014, 7 pages. |
| U.S. Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 12/783,504, dated Aug. 29, 2014, 78 pages. |
| U.S. Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 12/764,015, dated Sep. 11, 2014, 29 pages. |
| U.S. Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 10/053,765, dated Sep. 12, 2014, 25 pages. |
| U.S. Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 12/764,032, dated Sep. 12, 2014, 29 pages. |
| U.S. Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 13/477,987, dated Sep. 26, 2014, 42 pages. |
| U.S. Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 09/992,413, dated Oct. 15, 2014, 14 pages. |
| U.S. Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 13/047,672, dated Oct. 17, 2014, 33 pages. |
| U.S. Patent and Trademark Office, Notice of Allowance for U.S. Appl. No. 11/929,445, dated Oct. 24, 2014, 33 pages. |
| Office Action prepared by the U.S. Patent and Trademark Office for U.S. Appl. No. 15/838,234, dated Aug. 31, 2018, 45 pages. |
| Office Action prepared by the U.S. Patent and Trademark Office for U.S. Appl. No. 15/839,718, dated Aug. 31, 2018, 45 pages. |
| Final Office Action prepared by the U.S. Patent and Trademark Office for U.S. Appl. No. 15/838,234, dated Dec. 21, 2018, 19 pages. |
| Final Office Action prepared by the U.S. Patent and Trademark Office for U.S. Appl. No. 15/839,718, dated Dec. 21, 2018, 20 pages. |
| Office Action prepared by the U.S. Patent and Trademark Office for U.S. Appl. No. 15/838,234, dated Apr. 15, 2019, 18 pages. |
| Office Action prepared by the U.S. Patent and Trademark Office for U.S. Appl. No. 15/839,718, dated Apr. 15, 2019, 18 pages. |
| Office Action prepared by the U.S. Patent and Trademark Office for U.S. Appl. No. 15/838,234, dated Oct. 23, 2019, 16 pages. |
| Office Action prepared by the U.S. Patent and Trademark Office for U.S. Appl. No. 15/839,718, dated Oct. 23, 2019, 17 pages. |
| Notice of Allowance prepared by the US Patent and Trademark Office for U.S. Appl. No. 15/838,234, dated Feb. 10, 2020, 12 pages. |
| Notice of Allowance prepared by the US Patent and Trademark Office for U.S. Appl. No. 15/839,718, dated Feb. 10, 2020, 12 pages. |
| Hoshi et. al., Voice Stream Multiplexing between IP telephony Gateways, IEICE TRANS Dated Apr. 4, 1999. |
| Number | Date | Country | |
|---|---|---|---|
| 60230021 | Sep 2000 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 13371318 | Feb 2012 | US |
| Child | 09947116 | US | |
| Parent | 12199647 | Aug 2008 | US |
| Child | 13371318 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 09947116 | Sep 2001 | US |
| Child | 15838219 | US | |
| Parent | 09947116 | Sep 2001 | US |
| Child | 12199647 | US |
