The United States Patent Office (USPTO) has published a notice to the effect that the USPTO's computer programs require that patent applicants reference both a serial number and indicate whether an application is a continuation or continuation-in-part. Stephen G. Kunin, Benefit of Prior-Filed Application, USPTO Official Gazette Mar. 18, 2003, available at http://www.uspto.gov/web/offices/com/sol/og/2003/week11/patbene.htm. The present Applicant Entity (hereinafter “Applicant”) has provided above a specific reference to the application(s) from which priority is being claimed as recited by statute. Applicant understands that the statute is unambiguous in its specific reference language and does not require either a serial number or any characterization, such as “continuation” or “continuation-in-part,” for claiming priority to U.S. patent applications. Notwithstanding the foregoing, Applicant understands that the USPTO's computer programs have certain data entry requirements, and hence Applicant is designating the present application as a continuation-in-part of its parent applications as set forth above, but expressly points out that such designations are not to be construed in any way as any type of commentary and/or admission as to whether or not the present application contains any new matter in addition to the matter of its parent application(s).
A computationally implemented method includes, but is not limited to receiving one or more conditional directives from a receiving user, the one or more conditional directives delineating one or more conditions for obfuscating identity of a source entity affiliated with one or more communiqués directed to the receiving user; and presenting at least a second communiqué in response to at least a reception of a first communiqué affiliated with the source entity and in accordance with the one or more conditional directives, the second communiqué being presented in lieu of presenting the first communiqué. In addition to the foregoing, other method aspects are described in the claims, drawings, and text forming a part of the present disclosure.
In one or more various aspects, related systems include but are not limited to circuitry and/or programming for effecting the herein-referenced method aspects; the circuitry and/or programming can be virtually any combination of hardware, software, and/or firmware configured to effect the herein-referenced method aspects depending upon the design choices of the system designer.
A computationally implemented system includes, but is not limited to: means for receiving one or more conditional directives from a receiving user, the one or more conditional directives delineating one or more conditions for obfuscating identity of a source entity affiliated with one or more communiqués directed to the receiving user; and means for presenting at least a second communiqué in response to at least a reception of a first communiqué affiliated with the source entity and in accordance with the one or more conditional directives, the second communiqué being presented in lieu of presenting the first communiqué. In addition to the foregoing, other system aspects are described in the claims, drawings, and text forming a part of the present disclosure.
A computationally implemented system includes, but is not limited to: circuitry for receiving one or more conditional directives from a receiving user, the one or more conditional directives delineating one or more conditions for obfuscating identity of a source entity affiliated with one or more communiqués directed to the receiving user; and circuitry for presenting at least a second communiqué in response to at least a reception of a first communiqué affiliated with the source entity and in accordance with the one or more conditional directives, the second communiqué being presented in lieu of presenting the first communiqué. In addition to the foregoing, other system aspects are described in the claims, drawings, and text forming a part of the present disclosure.
A computer program product including a signal-bearing medium bearing one or more instructions for receiving one or more conditional directives from a receiving user, the one or more conditional directives delineating one or more conditions for obfuscating identity of a source entity affiliated with one or more communiqués directed to the receiving user; and one or more instructions for presenting at least a second communiqué in response to at least a reception of a first communiqué affiliated with the source entity and in accordance with the one or more conditional directives, the second communiqué being presented in lieu of presenting the first communiqué. In addition to the foregoing, other computer program product aspects are described in the claims, drawings, and text forming a part of the present disclosure.
A method for obfuscating identity of a source entity affiliated with communiqué directed to a receiving user, the obfuscation of the identity being in accordance with one or more conditional directives provided, at least in part, by the receiving user, the method includes receiving one or more conditional directives from a receiving user, the one or more conditional directives delineating one or more conditions for obfuscating identity of a source entity affiliated with one or more communiqués directed to the receiving user; and presenting, using one or more processors, at least a second communiqué in response to at least a reception of a first communiqué affiliated with the source entity and in accordance with the one or more conditional directives, the second communiqué being presented in lieu of presenting the first communiqué.
The foregoing summary is illustrative only and is not intended to be in any way limiting. In addition to the illustrative aspects, embodiments, and features described above, further aspects, embodiments, and features will become apparent by reference to the drawings and the following detailed description.
In the following detailed description, reference is made to the accompanying drawings, which form a part hereof. In the drawings, similar symbols typically identify similar components, unless context dictates otherwise. The illustrative embodiments described in the detailed description, drawings, and claims are not meant to be limiting. Other embodiments may be utilized, and other changes may be made, without departing from the spirit or scope of the subject matter presented here.
In recent years, the computing/communication industry has enjoyed dramatic technological advancement and spectacular commercial popularity, providing numerous benefits for those who choose to enjoy the fruits of technological developments in the computing/communication sectors. For example, with the rapid development of personal communication devices such as cellular telephones, personal digital assistants (PDAs), Smartphones, laptop computers, desktop computers, and so forth, users of such devices are now able to maintain 24/7 connectivity with other users at relatively low costs. Such connectivity may be via a variety of communication channels including, for example, telephone calls, emails, Voice over Internet Protocol (VoIP) calls, text messaging (e.g., short message service or SMS, or multimedia messaging service or MMS), instant messaging (IM), and so forth. Unfortunately, in addition to providing significant benefits to users, users of such technologies must also deal with a whole new set of issues and problems that have also arisen with this new computing/communication technology.
For example, users of such personal communication devices (e.g., cellular telephones, Smartphones, laptop and desktop computers, and so forth) face a number of privacy and security issues. One such issue that has surfaced with respect to users of personal communication devices is that communiqués (e.g., electronic communications including, for example, telephone calls, VoIP, emails, text messages, IMs, and so forth) received through these personal communication devices are often easily accessible by those other than the primary users (e.g., owners) of such devices. As a result, highly sensitive communiqués (e.g., confidential personal or business communiqués) that are directed to the primary users of such devices may often be accessed by others potentially causing embarrassing if not devastating consequences.
For example, it was extensively reported recently that a well-known and well-admired professional athlete was discovered having an extramarital affair by his spouse. It was widely reported that the spouse discovered this affair when she found a voice message from her husband's mistress on her husband's cellular telephone. Because the husband (i.e., famous professional athlete) in that incident had not erased or was not able to hide or disguise the voice message from his mistress, the husband had to endure significant public humiliation and substantial financial loss due to loss of commercial endorsement income.
Of course the need for maintaining communication or communiqué secrecy is not just limited to personal situations, but may also be necessary in professional/business context. For example, it may be inappropriate for a person to receive certain sensitive communiqués from particular parties (e.g., communiqués from certain clients or competitors, or communiqués from a particular websites or business) while at work or while at other locations (e.g., when meeting with clients).
According to various embodiments, methods, systems, and computer program products are provided for obfuscating identity of a source entity affiliated with a communiqué that is directed to a receiving user, the obfuscating of the identity of the source entity being based on one or more conditional directives provided by the receiving entity. More particularly, the methods, systems, and computer program products may be designed to receive one or more conditional directives from a receiving user, the one or more conditional directives delineating one or more conditions for obfuscating identity of a source entity affiliated with one or more communiqués directed to the receiving user; and to present at least a second communiqué in response to at least a reception of a first communiqué affiliated with the source entity and in accordance with the one or more conditional directives, the second communiqué being presented in lieu of presenting the first communiqué. In various embodiments, the methods, systems, and computer program products may be implemented at a computing/communication device of the receiving user.
For purposes of the following description, a “communiqué” may be in reference to any one of a variety of communication means including, for example, a telephone call, an email message, a text message (e.g., SMS or MMS), an instant message (IM), a Voice over Internet Protocol (VoIP) call, a voice message, a video message, and so forth. As will be further described herein, a “source entity” may be in reference to any entity that may be the original or an intermediate source for a communiqué. In some cases, a source entity may include, for example, a source user who may be a human or robotic user and/or a source user device such as a cellular telephone, Smartphone, laptop or desktop computer, and so forth. In some cases, a source entity may be an organization such as a business or a trade or interest group. In some instances, a source entity may be a website. A “receiving user” may be a human or robotic user that is designated to receive one or more communiqués. In some cases where the receiving user is a robotic user, the robotic user may be a network device such as a network server for, for example, a voicemail service, a text messaging service, or a web-based application service.
A “conditional directive,” as will be discussed herein, relates to a command or instruction to execute one or more actions when one or more conditions have occurred and/or detected. For example, a conditional directive may be a command to intercept a first communiqué directed to a receiving user and to present, in lieu of presenting the first communiqué, a second communiqué when, for example, one or more particular conditions are determined to have occurred. In some cases, a conditional directive may dictate that a first communiqué be intercepted and replaced by a second communiqué in order to obfuscate the identity of a source entity affiliated with the first communiqué so long as the first communiqué indicates its affiliation to the source entity. In other cases, and as will be described in greater detail herein, other conditions must be detected before presenting the second communiqué in lieu of the first communiqué in order to obfuscate the identity of the source entity.
Turning now to
From another perspective, the computing device 10 may be a receiving user device (e.g., a communication device for a receiving user 32) that is designed to receive one or more conditional directives 50 from a receiving user 32, and to execute the one or more conditional directives 50 in order to obfuscate the identity of a source entity 20 affiliated with a communiqué (e.g., the first communiqué 52 in
The computing device 10 may be generally designed to facilitate communication in the form of communiqués between a receiving user 32 and one or more source entities 20 via one or more communication networks 40. As described above, a receiving user 32 may be a human user or robotic user (e.g., answering service server). In various embodiments, a source entity 20 may comprise of a human or robotic source user 22 and/or a source user device 24 (e.g., a laptop computer, a desktop computer, a workstation, a Smartphone, a cellular telephone, a personal digital assistant (PDA), or other computing/communication devices). In some embodiments, and from another perspective, the source entity 20 may be a website or an organization such as a business, a social group, a trade/technical group, or an interest group.
In some cases, the computing device 10 may be designed to receive one or more conditional directives 50 from a receiving user 32 through a user interface 107. In various embodiments, the user interface 107 may comprise of an audio, user interface 110 (e.g., microphone/speaker system) and/or a display user interface 112 (e.g., one or more of a display monitor including a touch screen, a keypad or keyboard, a mouse, and so forth). As will be further described herein, in order to facilitate or prompt the receiving user 32 to input the one or more conditional directives 50, the computing device 10 may, in some cases, present to the receiving user 32, via the user interface 107, a conditional directive input interface for inputting the one or more conditional directives 50. The conditional directive input interface that may be presented may be a visual conditional directive input interface (e.g., as provided through a display monitor of a display user interface 112 and/or an audio conditional directive input interface (e.g., as provided through a speaker/microphone system of an audio user interface 110).
In some embodiments, the conditional directive input interface that may be presented to the receiving user 32 may solicit one or more conditional directives 50 from the receiving user 32 that, at a minimum, at least identify the one or more source entities 20 whose identities are to be obfuscated with respect to communiqués that are affiliated with the one or more source entities 20 and that are directed (e.g., sent) to the receiving user 32. For these implementations, the conditional directive input interface that may be presented to the receiving user 32 may only require the receiving user 32 to provide a minimal amount of input data in order to generate the one or more conditional directives 50. For example, in some cases, the conditional directive input interface that may be presented to a receiving user 32 (e.g., via the user interface 107) may only obtain from the receiving user 32 data that merely indicates the one or more representations (e.g., identifiers such as names, email addresses, Internet Protocol addresses, telephone numbers, and so forth) of the source entity 20 that may be found in communiqués directed to the receiving user 32 that the receiving user 32 wishes to obfuscate.
In some implementations, and as will be further described herein, the conditional directive input interface that may be presented to the receiving user 32 may be designed to acquire from the receiving user 32 data that indicates the specific conditions associated with, for example, the computing device 10 that must be present in order to cause the identity of a source entity 20 affiliated with a communiqué (e.g., the first communiqué 52 of
The one or more conditional directives 50 that may be received and executed by the computing device 10 may include a variety of directives for conditionally obfuscating the identity of a source entity 20 with respect to one or more communiqués that are directed to the receiving user 32. For example, in some embodiments, the one or more conditional directives 50 that may be received by the computing device 10 may include a directive to direct the computing device 10 to obfuscate the identity of a source entity 20 whenever the computing device 10 receives any communiqué (e.g., first communiqué 52 of
In some embodiments, and as briefly discussed above, the one or more conditional directives 50 that may be received by the computing device 10 may include a directive to direct the computing device 10 to obfuscate the identity of a source entity 20 only when certain conditions are present. For example, in some embodiments the one or more conditional directives 50 may include a directive to direct the computing device 10 to obfuscate the identity of a source entity 20 (with respect to a received communiqué such as the first communiqué 52 of
In some embodiments, the one or more conditional directives 50 that may be received by the computing device 10 may include a directive to direct the computing device 10 to obfuscate the identity of a source entity 20 (with respect to a received communiqué such as the first communiqué 52 of
In various embodiments, the one or more conditional directives 50 that may be received by the computing device 10 may direct the computing device 10 to obfuscate the identity of a source entity 20 with respect to a received communiqué (e.g., the first communiqué 52 of
The second way to provide the replacement communiqué is to provide or generate a distinct substitute communiqué that is unrelated to the original received communiqué (e.g., the first communiqué 52 of
Referring back to the example environment 100 of
In some embodiments, the reception of the first communiqué 52 may include the interception (e.g., seizing, capturing, or interrupting) of the first communiqué 52 in order to prevent the first communiqué 52 from being presented (e.g., visually displayed and/or audibly indicated) at least as is. As will be further described herein, if the first communiqué 52 is indeed intercepted, then the intercepting of the first communiqué 52 may be in accordance with the one or more conditional directives 50 as provided by the receiving user 32.
The first communiqué 52 that may be received and/or intercepted by the computing device 10 may be directed to (e.g., destined for or sent to) the receiving user 32 and may be any one of a variety of electronic communications including, for example, a telephone call, a VoIP call, a voice mail or message, an email, a text message (e.g., SMS or MMS), an IM, a video message, and so forth. Depending on whether the first communiqué 52 is an email, a telephone call, a VoIP call, a video call or some other type of communiqué, the first communiqué 52 may include various types of data including, for example, header data (which may identify the sender, the destination address and/or receiving party, subject heading, routing or path, and so forth), message content data (e.g., audio data if the first communiqué 52 is a telephone or VoIP call or text data if the first communiqué 52 is an email or text message), and/or metadata.
In various embodiments, the first communiqué 52 that may be received by the computing device 10 may be affiliated with the source entity 20 by indicating the source entity 20 in the form of one or more representations (e.g., identifiers) associated with the source entity 20. A representation of the source entity 20, which may be included in the first communiqué 52 in the form of header data, message content data, or metadata, may be any one of a name (e.g., an individual's legal name, a username, a business name, a website name), address (e.g., email address, uniform resource locator or URL, Internet Protocol or IP address, and so forth), a telephone number, an image (e.g., digital facial image or iconic figure), a voice signature, or any other identifier that may be associated with the source entity 20.
As described earlier, after receiving the first communiqué 52 and determining that the first communiqué 52 is affiliated with the source entity 20, the computing device 10 may present (e.g., audibly indicating and/or visually displaying) at least a second communiqué 54 in lieu of presenting the first communiqué 52 in accordance with the one or more conditional directives 50. In various embodiments, the computing device 10 may present the second communiqué 54 audibly and/or visually via a user interface 107, which may further include an audio user interface 110 (e.g., microphone/speaker system) and/or a display user interface 112 (e.g., a system that include a display monitor including a touch screen, a keypad or keyboard, a mouse, and/or other peripheral devices).
In some embodiments, the computing device 10 in accordance with the one or more conditional directives 50 may present the second communiqué 54 in lieu of presenting the first communiqué 52 only when certain conditions are detected. For example, the one or more conditional directives 50 as described earlier, may require that the second communiqué 54 be presented in lieu of presenting the first communiqué 52 only when it is determined that the computing device 10 is not in the possession of receiving user 32. In some cases, such a determination may be made by determining whether a verification (e.g., password or biometric verification) has been provided that indicates that the receiving user 32 has possession of the computing device 10.
In some cases, the one or more conditional directives 50 may require that the second communiqué 54 be presented in lieu of presenting the first communiqué 52 only when it is determined that the computing device 10 is the proximate vicinity of a specific third party (e.g., as specified by the receiving user 32). Such a determination may be made by, for example, processing audio and/or image data provided by an audio device such as a microphone and/or a image capturing device such as a digital camera or a webcam.
In some cases, the one or more conditional directives 50 may require that the second communiqué 54 be presented in lieu of presenting the first communiqué 52 only when it is determined that the computing device 10 is at one or more specified locations (e.g., workplace, home, etc.) or is at or has reached one or more points or intervals of time. In still other cases, the one or more conditional directives 50 may require that the second communiqué 54 be presented in lieu of presenting the first communiqué 52 only when it is determined that other types of conditions exists as will be further described herein.
In some embodiments, the computing device 10 after receiving the first communiqué 52 and determining that the first communiqué 52 is indeed affiliated with the source entity 20 may store the first communiqué 52 in a memory 140 (see
As also indicated earlier, in various embodiments, the second communiqué 54 that is to be presented in lieu of presenting the first communiqué 52 may be provided or generated by modifying the first communiqué 52 in accordance with the one or more conditional directives 50. In some cases, the modification of the first communiqué 52 may involve replacement of one or more representations associated with the source entity 20 that may be included in the first communiqué 52 with one or more locum tenentes (e.g., placeholders, proxies, stand-ins, and so forth). Alternatively, the second communiqué 54 may be provided by providing a substitute communiqué that is a distinct and unrelated communiqué from the first communiqué 52. In some cases, and as will be further described herein, the substitute communiqué that may be provided may be a previously received communiqué that was directed to the receiving user 32. In some cases, the substitute communiqué that may be provided may be a communiqué that is supplied by the receiving user 32.
Regardless of whether the second communiqué 54 is merely a modified version of the first communiqué 52 or a communiqué that is distinct and unrelated from the first communiqué 52, the second communiqué 54 may at least not appear to be affiliated with the source entity 20. This means that in some embodiments, the second communiqué 54 to be presented may not include any representation (e.g., identifiers such as a name, email address, image, telephone number, voice signature, and so forth) of the source entity 20.
As described above, in embodiments where the second communiqué 54 is provided by modifying the first communiqué 52, the first communiqué 52 may be modified by replacing one or more representations of the source entity 20 that may be included in the first communiqué 52 with one or more locum tenentes. For example, replacing one or more representative addresses or names of the source entity 20 included in the first communiqué 52 with one or more substitute addresses or names. Note that the one or more locum tenentes (e.g., substitute addresses or substitute names) that are to replace the one or more representations (e.g., representative addresses and names) of the source entity 20 that may be included in the first communiqué 52 may be either fictional or non-fictional substitutes as will be further described herein. In cases where the first communiqué 52 is an audio communiqué such as a telephone call or a VoIP call, the voice signature of the source entity 20 (e.g., a human source user 22) may be modified. A “voice signature” may be in reference to the distinct patterns of speech (e.g., tone, pitch, rhythm, accent, and so forth) that each person's voice may be uniquely associated with.
In embodiments in which the second communiqué 54 is provided by providing a substitute communiqué that is a distinct communiqué unrelated to the first communiqué 52, the second communiqué 54 may be a direct or indirect substitute for the first communiqué 52. That is, in some embodiments, the second communiqué 54 that may be presented may be a direct substitute that is the same type of communiqué as the first communiqué 52. For example replacing an email that is affiliated with the source entity 20 with another email that at least should not appear to a third party to be affiliated with the source entity 20.
In other embodiments, however, the second communiqué 54 that may be presented may be an indirect substitute that is a different type of communiqué from the first communiqué 52. For example, replacing a text message that is affiliated with the source entity 20 with a voice message that does not at least appear to be affiliated with the source entity 20. In some embodiments, the second communiqué 54 that may be presented may be a copy of a communiqué (which may have been sent by a third party) that was previously received by the computing device 10. For these embodiments, the second communiqué 54 may be a copy of the most recently received communiqué received by the computing device 10 that was directed to the receiving user 32.
In embodiments in which the second communiqué 54 is provided by providing a substitute communiqué that is a distinct communiqué unrelated to the first communiqué 52 (rather than merely being a modified version of the first communiqué 52), the second communiqué 54 may be retrieved from a memory 140 (e.g., see
In various embodiments, the second communiqué 54 that may be presented by the computing device 10 may include at least one of a textual or numerical content data. For these embodiments, the second communiqué 54 may be at least one of an email, an IM, or a text message. In alternative or the same embodiments, the second communiqué 54 that may be presented by the computing device 10 may include at least one of audio or image data. For these embodiments, the second communiqué 54 may be at least one of a telephone call, a video call, a VoIP call, or a voice mail.
In various embodiments, the presenting by the computing device 10 of the second communiqué 54, in lieu of presenting of the first communiqué 52, may also include the presentation of a communiqué accessing interface for accessing the second communiqué 54. For these embodiments, the communiqué accessing interface to be presented may be provided in order to covertly alert or indicate to the receiving user 32 that the second communiqué 54 is being presented in lieu of the first communiqué 52. The communiqué accessing interface that may be presented may be an audio and/or a visual interface for accessing the second communiqué 54 and may be presented through the audio user interface 110 (e.g., microphone/speaker system) and/or the display user interface 112 (e.g., a system comprising display monitor including a touch screen, a keypad or keyboard, a mouse, and so forth) of the computing device 10.
The type of communiqué accessing interface that may be presented may depend on the type of communiqué (e.g., the second communiqué 54) to be presented through the communiqué accessing interface. Examples of communiqué accessing interfaces that may be presented include, for example, an email application interface, an IM application interface, a VoIP interface, and so forth. In order to covertly alert the receiving user 32 that the second communiqué 54 is being presented as a replacement for the first communiqué 52, the communiqué accessing interface (e.g., audio communiqué accessing interface or a visual communiqué accessing interface) that may be presented may include an audio alert (e.g., background sound such as simulated natural sounds such as birds chirping), a visual alert (e.g., displaying a particular color or icon in the background of a display screen), and/or a vibration alert (e.g., particular rhythmic vibration) to discretely indicate to the receiving user 32 that the second communiqué 54 is being presented in lieu of the first communiqué 52. In some cases, such an alert, although may not specifically indicate that the second communiqué 54 is being presented in lieu of the first communiqué 52, may at least covertly indicate to the receiving user 32 that the second communiqué 54 that is being presented is a deception.
Turning specifically now to the computing device 10 of
As illustrated, the computing device 10 may include one or more processors 101 (e.g., one or more microprocessors and/or controllers), a memory 140 (which may be a storage medium) including computer readable instructions 40, a transceiver 105 (e.g., designed to transmit and receive communication signals), a network interface 106 (e.g., a network interface such as a network interface card or “NIC” for accessing one or more communication networks 40), a user interface 107 (which may further include an audio user interface 110 and/or display user interface 112) as described earlier, and/or one or more sensors 150. In various implementations, the one or more processors 101 may include certain logic blocks for executing the novel operations and processes to be described herein. For example, the one or more processors 101, when executing the computer readable instructions 40 of the memory 140, may include logic blocks including a conditional directive receiving module 102 and a communiqué presenting module 104.
As will be further described herein, the conditional directive receiving module 102 may be configured to receive one or more conditional directives 50 from a receiving user 32, the one or more conditional directives 50 delineating one or more conditions for obfuscating identity of a source entity 20 affiliated with one or more communiqués (e.g., first communiqué 52 of
The computing device 10, in various embodiments, may include one or more sensors 150. For example, in some embodiments, the computing device 10 may include a global positioning system 120, one or more image capturing devices 122 (e.g., digital camera or a webcam) that may also be part of a display user interface 112, one or more audio capturing devices that may be part of an audio user interface 110, and one or more biometric sensors 124 (e.g., retinal scanner 126, fingerprint scanner 127, and so forth).
In various embodiments, the memory 140 that may be included in the computing device 10 may be designed for storing various types of data and computer readable programming instructions. For these embodiments, memory 140 may comprise of one or more of mass storage device, read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), cache memory such as random access memory (RAM), flash memory, synchronous random access memory (SRAM), dynamic random access memory (DRAM), and/or other types of memory devices.
As illustrated in
In embodiments where the memory 140 includes the one or more substitute representations 57, the one or more substitute representations 57 (e.g., one or more substitute names, addresses, telephone numbers, images, voice signatures, and so forth) may be used as one or more locum tenentes to replace one or more representations of the source entity 20 that may be included in a first communiqué 52 received by the computing device 10 and determined to be affiliated with the source entity 20. In some embodiments, the memory 140 may include the facial recognition application 172, and/or the voice recognition application 170. These applications may be used in some cases in order to, for example, determine that the first communiqué 52 received by the computing device 10 includes one or more representations (e.g., in the form of image representations and/or voice representations) of the source entity 20. Such applications may also or may alternatively be employed in order to determine whether, for example, a particular third party is in the proximate vicinity of the computing device 10.
Referring now to
Referring now to
As further illustrated in
A more detailed discussion related to the computing device 10 of
Further, in
In any event, after a start operation, the operational flow 300 of
In addition to the conditional directive receiving operation 302, operational flow 300 may also include a communiqué presenting operation 304 for presenting at least a second communiqué in response to at least a reception of a first communiqué affiliated with the source entity and in accordance with the one or more conditional directives, the second communiqué being presented in lieu of presenting the first communiqué as further illustrated in
As will be further described herein, the conditional directive receiving operation 302 and the communiqué presenting operation 304 of
In the same or different implementations, the conditional directive receiving operation 302 of
Operation 403, in turn, may further include an operation 404 for receiving the one or more conditional directives via an audio user interface as further depicted in
In the same or different implementations, operation 403 may include an operation 405 for receiving the one or more conditional directives via a display user interface as also depicted in
In various implementations, the conditional directive receiving operation 302 of
In some implementations, operation 406 may include an operation 407 for receiving the one or more conditional directives at one of a cellular telephone, a Smartphone, a personal digital assistant (PDA), a laptop computer, a tablet computer, a desktop computer, or a workstation as depicted in
In some cases, the one or more conditional directives 50 that may be received through the conditional directive receiving operation 302 of
The receiving user 32 may be prompted to provide the one or more conditional directives 50 using various means in various alternative implementations. For example, in some implementations, operation 408 may further include an operation 409 for prompting the receiving user to input the one or more conditional directives by presenting a conditional directive input interface to the receiving user to permit the receiving user to input the one or more conditional directives as depicted in
In some implementations, operation 409 may further include an operation 410 for presenting a conditional directive input interface to the receiving user that solicits for the one or more conditional directives as depicted in
In the same or different implementations, operation 409 may include an operation 411 for presenting the conditional directive input interface to the receiving user to permit the receiving user to input the one or more conditional directives, the conditional directive input interface to be presented being at least one of an audio conditional directive input interface or a visual conditional directive input interface as further depicted in
The one or more conditional directives 50 that are received through the conditional directive receiving operation 302 of
As further depicted in
In the same or different implementations, operation 412 may include an operation 414 for receiving at least one directive from the receiving user that indicates at least one address associated with the source entity to conditionally obfuscate identity of the source entity when a communiqué is received that is determined to include the at least one address as further depicted in
In the same or different implementations, operation 412 may include an operation 415 for receiving at least one directive from the receiving user that indicates at least one telephone number associated with the source entity to conditionally obfuscate identity of the source entity when a communiqué is received that is determined to include the at least one telephone number as further depicted in
In the same or different implementations, operation 412 may include an operation 416 for receiving at least one directive from the receiving user that indicates at least one of a numerical, textual, or symbolic identifier associated with the source entity to conditionally obfuscate identity of the source entity when a communiqué is received that is determined to include at least one of the numerical, textual, or symbolic identifier associated with the source entity as further depicted in
In the same or different implementations, operation 412 may include an operation 417 for receiving at least one directive from the receiving user that indicates at least one image associated with the source entity to conditionally obfuscate identity of the source entity when a communiqué is received that is determined to include the at least one image as further depicted in
In the same or different implementations, operation 412 may include an operation 418 for receiving at least one directive from the receiving user that indicates at least a voice signature associated with the source entity to conditionally obfuscate identity of the source entity when a communiqué is received that is determined to include at least the voice signature as depicted in
A “voice signature,” which may also be referred to as “voice biometrics,” relates to the particular combination of characteristics associated with a person's voice that makes each person's voice distinctive. For example, a typical individual will have a voice with certain distinct characteristics (e.g., speech pattern, pitch, tone, rhythm, accent, and so forth) that make that individual's voice relatively unique. By changing the voice signature (e.g., modifying voice characteristics such as tone, pitch, and so forth) of an individual's voice, the voice may be disguised and the identity of the individual that the original voice belongs to may be obfuscated.
In some implementations, the conditional directive receiving operation 302 of
In the same or different implementations, the conditional directive receiving operation 302 of
In the same or different implementations, the conditional directive receiving operation 302 of
In some implementations, operation 421 may further include an operation 422 for receiving at least one directive from the receiving user to conditionally obfuscate the identity of the source entity in response to determining that the receiving user device is at one or more specified locations as further depicted in
In the same or different implementations, the conditional directive receiving operation 302 of
In some implementations, operation 423 may further include an operation 424 for receiving at least one directive from the receiving user to conditionally obfuscate the identity of the source entity in response to determining that the receiving user device has reached one or more specified times of a day as further depicted in
In the same or different implementations, operation 423 may include an operation 425 for receiving at least one directive from the receiving user to conditionally obfuscate the identity of the source entity in response to determining that the receiving user device has reached one or more specified times of a calendar year as further depicted in
In the same or different implementations, the conditional directive receiving operation 302 of
In some cases, operation 426 may further include an operation 427 for receiving at least one directive from the receiving user to conditionally obfuscate the identity of the source entity in response to determining that one or more third parties are in proximate vicinity of the receiving user device as further depicted in
In various implementations, the conditional directive receiving operation 302 of
As further illustrated in
In some cases, operation 429 may further include an operation 430 for receiving at least one directive from the receiving user to conditionally obfuscate the identity of the source entity in absence of a password verification of the receiving user being in possession of the receiving user device as depicted in
In the same or different implementations, operation 429 may include an operation 431 for receiving at least one directive from the receiving user to conditionally obfuscate the identity of the source entity in absence of a biometric verification of the receiving user being in possession of the receiving user device as further depicted in
In some implementations, operation 431 may further include an operation 432 for receiving at least one directive from the receiving user to conditionally obfuscate the identity of the source entity in absence of at least one of a retinal scan verification, a voice verification, or a fingerprint verification of the receiving user being in possession of the receiving user device as depicted in
Referring back to the communiqué presenting operation 304 of
In the same or different implementations, the communiqué presenting operation 304 of
In the same or different implementations, the communiqué presenting operation 304 of
In the same or different implementations, the communiqué presenting operation 304 of
As further illustrated in
In the same or different implementations, operation 536 may include an operation 538 for presenting at least the second communiqué in accordance with the one or more conditional directives including in response to determining that the first communiqué includes one or more representations associated with the source entity in message content data form as depicted in
In the same or different implementations, operation 536 may include an operation 539 for presenting at least the second communiqué in accordance with the one or more conditional directives including in response to determining that the first communiqué includes one or more representations associated with the source entity in metadata form as depicted in
In the same or different implementations, operation 536 may include an operation 540 for presenting at least the second communiqué in accordance with the one or more conditional directives including in response to determining that the first communiqué includes at least one name associated with the source entity as depicted in
In the same or different implementations, operation 536 may include an operation 541 for presenting at least the second communiqué in accordance with the one or more conditional directives including in response to determining that the first communiqué includes at least one address associated with the source entity as depicted in
In the same or different implementations, operation 536 may include an operation 542 for presenting at least the second communiqué in accordance with the one or more conditional directives including in response to determining that the first communiqué includes at least one telephone number associated with the source entity as further depicted in
In the same or different implementations, operation 536 may include an operation 543 for presenting at least the second communiqué in accordance with the one or more conditional directives including in response to determining that the first communiqué includes at least one of a numerical, textual, or symbolic identifier associated with the source entity as depicted in
In the same or different implementations, operation 536 may include an operation 544 for presenting at least the second communiqué in accordance with the one or more conditional directives including in response to determining that the first communiqué includes at least an image associated with the source entity as further depicted in
In the same or different implementations, operation 536 may include an operation 545 for presenting at least the second communiqué in accordance with the one or more conditional directives including in response to determining that the first communiqué includes at least a voice signature associated with the source entity as depicted in
In some implementations, the communiqué presenting operation 304 of
In the same or different implementations, the communiqué presenting operation 304 of
In the same or different implementations, the communiqué presenting operation 304 of
In some cases, operation 548 may, in turn, include an operation 549 for presenting at least the second communiqué in accordance with the one or more conditional directives including in response to determining that the receiving user device is at one or more specified locations as further depicted in
In various implementations, the communiqué presenting operation 304 of
In some implementations, operation 550 may further include an operation 551 for presenting at least the second communiqué in accordance with the one or more conditional directives including in response to determining that the receiving user device is at one or more specified times of a day as further depicted in
In the same or different implementations, operation 550 may further include an operation 552 for presenting at least the second communiqué in accordance with the one or more conditional directives including in response to determining that the receiving user device is at one or more specified times of a calendar year as depicted in
In the same or different implementations, the communiqué presenting operation 304 of
In some cases, operation 553 may further include an operation 554 for presenting at least the second communiqué in accordance with the one or more conditional directives including in response to determining that one or more third parties are in proximate vicinity of the receiving user device as further depicted in
In various implementations, the communiqué presenting operation 304 of
In some cases, operation 555 may further include an operation 556 for presenting at least the second communiqué in accordance with the one or more conditional directives including upon determining absence of a verification of the receiving user having possession of the receiving user device as further depicted in FIG. 5d. For instance, the communiqué presenting module 104 including the receiving user device possession verification determining module 240 (see
Operation 556, in turn, may further include one or more additional operations in various alternative implementations. For example, in some implementations, operation 556 may further include an operation 557 for presenting at least the second communiqué in accordance with the one or more conditional directives including upon determining absence of a password verification of the receiving user having possession of the receiving user device as depicted in
In the same or different implementations, operation 556 may also include an operation 558 for presenting at least the second communiqué in accordance with the one or more conditional directives including upon determining absence of a biometric verification of the receiving user having possession of the receiving user device as further depicted in
In some cases, operation 558 may, in turn, include an operation 559 for presenting at least the second communiqué in accordance with the one or more conditional directives including upon determining absence of at least one of a retinal scan verification, a voice verification, or a fingerprint verification of the receiving user having possession of the receiving user device as depicted in
In various implementations, the second communiqué 54 that may be presented through the communiqué presenting operation 304 of
As further illustrated in
In some cases, operation 561 may further include an operation 562 for replacing the one or more representations of the source entity included in the first communiqué with the one or more locum tenentes by replacing one or more names associated with the source entity that are included in the first communiqué with one or more substitutes as further depicted in
In the same or different implementations, operation 561 may include an operation 563 for replacing the one or more representations of the source entity included in the first communiqué with the one or more locum tenentes by replacing one or more telephone numbers associated with the source entity that are included in the first communiqué with one or more substitutes as further depicted in
In the same or different implementations, operation 561 may include an operation 564 for replacing the one or more representations of the source entity included in the first communiqué with the one or more locum tenentes by replacing one or more addresses associated with the source entity that are included in the first communiqué with one or more substitutes as further depicted in
Various types of addresses included in the first communiqué 52 may be replaced in operation 564 in various alternative implementations. For example, in some implementations, operation 564 may include an operation 565 for replacing the one or more representations of the source entity included in the first communiqué with the one or more locum tenentes by replacing one or more of an email address, an Internet Protocol (IP) address, or a Uniform Resource Locator (URL) associated with the source entity that are included in the first communiqué with one or more substitutes as further depicted in
In the same or different implementations, operation 561 may include an operation 566 for replacing the one or more representations of the source entity included in the first communiqué with the one or more locum tenentes by replacing one or more images associated with the source entity that are included in the first communiqué with one or more substitutes as further depicted in
In the same or different implementations, operation 561 may include an operation 567 for replacing the one or more representations of the source entity included in the first communiqué with the one or more locum tenentes by replacing one or more voice signatures associated with the source entity that are included in the first communiqué with one or more substitutes as further depicted in
In the same or different implementations, operation 561 may include an operation 568 for replacing the one or more representations of the source entity included in the first communiqué with the one or more locum tenentes by replacing the one or more representations with one or more fictional substitutes as depicted in
In the same or different implementations, operation 561 may include an operation 569 for replacing the one or more representations of the source entity included in the first communiqué with the one or more locum tenentes by replacing the one or more representations with one or more non-fictional substitutes as further depicted in
In the same or different implementations, operation 561 may include an operation 570 for replacing the one or more representations of the source entity included in the first communiqué with the one or more locum tenentes by replacing the one or more representations with modified versions of the one or more representations as further depicted in
In the same or different implementations, operation 561 may include an operation 571 for replacing the one or more representations of the source entity included in the first communiqué with the one or more locum tenentes by replacing the one or more representations with one or more direct substitutes as further depicted in
In the same or different implementations, operation 561 may include an operation 572 for replacing the one or more representations of the source entity included in the first communiqué with the one or more locum tenentes by replacing the one or more representations with one or more indirect substitutes as depicted in
In some cases, the second communiqué 54 presented through the communiqué presenting operation 304 of
As further illustrated in
In some implementations, operation 574 may further include an operation 575 for presenting, in lieu of presenting the first communiqué, at least a second communiqué that is a copy of a communiqué that was most recently received by the receiving user as depicted in
In the same or different implementations, operation 573 may include an operation 576 for presenting, in lieu of presenting the first communiqué, at least a second communiqué that was previously provided by the receiving user as further depicted in
In the same or different implementations, operation 573 may include an operation 577 for presenting, in lieu of presenting the first communiqué, at least a second communiqué that is a direct substitute communiqué for the first communiqué as depicted in
In the same or different implementations, operation 573 may include an operation 578 for presenting, in lieu of presenting the first communiqué, at least a second communiqué that is an indirect substitute communiqué from the first communiqué as illustrated in
In the same or different implementations, operation 573 may include an operation 579 for presenting, in lieu of presenting the first communiqué, at least a second communiqué that is a direct substitute communiqué from the first communiqué as depicted in
In various implementations, the communiqué presenting operation 304 of
In some cases, operation 580 may further include an operation 581 for presenting, in lieu of presenting the first communiqué, at least a second communiqué including presenting at least one of an email, an instant message (IM), or a text message as depicted in
In some implementations, the communiqué presenting operation 304 of
In some cases, operation 582 may further include an operation 583 for presenting, in lieu of presenting the first communiqué, at least a second communiqué including presenting at least one of a telephone call, a video call, a voice over Internet Protocol (VoIP) call, or a voice mail as further depicted in
In various implementations, the communiqué presenting operation 304 of
In some cases, operation 584 may further include an operation 585 for presenting, in lieu of presenting the first communiqué, the second communiqué and the communiqué accessing interface for accessing the second communiqué, the communiqué accessing interface providing an indication to covertly indicate to the receiving user that the second communiqué is being presented in lieu of the first communiqué as depicted in
Operation 585 may, in turn, include an operation 586 for presenting, in lieu of presenting the first communiqué, the second communiqué and the communiqué accessing interface for accessing the second communiqué, the communiqué accessing interface being an audio communiqué accessing interface as depicted in
As further depicted in
In some implementations, operation 587 may further include an operation 588 for presenting, in lieu of presenting the first communiqué, the second communiqué and the audio communiqué accessing interface with the audio alert, the audio alert being a ping, a ring, or a hum provided through the audio communiqué accessing interface as depicted in
In the same or different implementations, operation 587 may include an operation 589 for presenting, in lieu of presenting the first communiqué, the second communiqué and the audio communiqué accessing interface with the audio alert, the audio alert being one or more simulated natural background noises provided through the audio communiqué accessing interface as depicted in
In the same or different implementations, the operation 586 for presenting the second communiqué 54 and the audio communiqué accessing interface may include an operation 590 for presenting, in lieu of presenting the first communiqué, the second communiqué and the audio communiqué accessing interface including a visual alert to covertly indicate to the receiving user that the second communiqué is being presented in lieu of the first communiqué as further depicted in
In some implementations, operation 590 may further include an operation 591 for presenting, in lieu of presenting the first communiqué, the second communiqué and the audio communiqué accessing interface including the visual alert, the visual alert being one or more particular symbols or icons that are displayed through a display screen as further depicted in
In the same or different implementations, operation 590 may include an operation 592 for presenting, in lieu of presenting the first communiqué, the second communiqué and the audio communiqué accessing interface including the visual alert, the visual alert being one or more particular colors that are displayed through a display screen as further depicted in
In some alternative implementations, rather than presenting a visual alert or an audio alert, the operation 585 for presenting an audio communiqué accessing interface (e.g., as presented by the audio communiqué accessing interface presenting module 256) may also involve the presentation of other forms of alerts. For example, since many communication/computing devices such as cellular phones and Smart phones include the capacity to vibrate when a telephone call is received, in some implementations, the operation 585 for presenting the audio communiqué accessing interface may also include an operation for presenting a vibrating alert (e.g., as provided by the vibrating alert providing module 259) to covertly indicate to the receiving user 32 that the second communiqué 54 is being presented in lieu of the first communiqué 52.
In various implementations, the operation 585 for presenting, in lieu of presenting the first communiqué, the second communiqué and the communiqué accessing interface for accessing the second communiqué, the communiqué accessing interface providing an indication to covertly indicate to the receiving user that the second communiqué is being presented in lieu of the first communiqué may include an operation 593 for presenting, in lieu of presenting the first communiqué, the second communiqué and the communiqué accessing interface for accessing the second communiqué, the communiqué accessing interface being a visual communiqué accessing interface as depicted in
As further illustrated in
In some cases, operation 594 may further include an operation 595 for presenting, in lieu of presenting the first communiqué, the second communiqué and the visual communiqué accessing interface with the visual alert, the visual alert being one or more particular symbols or icons displayed through the visual communiqué accessing interface as further depicted in
In the same or different implementations, operation 594 may include an operation 596 for presenting, in lieu of presenting the first communiqué, the second communiqué and the visual communiqué accessing interface with the visual alert, the visual alert being one or more particular colors displayed through the visual communiqué accessing interface as further depicted in
In the same or different implementations, the operation 593 for presenting the second communiqué and the visual communiqué accessing interface may include an operation 597 for presenting, in lieu of presenting the first communiqué, the second communiqué and the visual communiqué accessing interface including an audio alert to covertly indicate to the receiving user that the second communiqué is being presented in lieu of the first communiqué as depicted in
In some implementations, operation 597 may include an operation 598 for presenting, in lieu of presenting the first communiqué, the second communiqué and the visual communiqué accessing interface including the audio alert, the audio alert being a ping, a ring, or a hum provided through a speaker system as further depicted in
In some implementations, operation 597 may include an operation 599 for presenting, in lieu of presenting the first communiqué, the second communiqué and the visual communiqué accessing interface including the audio alert, the audio alert being one or more simulated natural background noises provided through a speaker system as further depicted in
In some implementations, the operation 593 for presenting the second communiqué and the visual communiqué accessing interface may further include an operation 600 for presenting, in lieu of presenting the first communiqué, the second communiqué and the visual communiqué accessing interface including a vibrating alert to covertly indicate to the receiving user that the second communiqué is being presented in lieu of the first communiqué as further depicted in
Those having skill in the art will recognize that the state of the art has progressed to the point where there is little distinction left between hardware and software implementations of aspects of systems; the use of hardware or software is generally (but not always, in that in certain contexts the choice between hardware and software can become significant) a design choice representing cost vs. efficiency tradeoffs. Those having skill in the art will appreciate that there are various vehicles by which processes and/or systems and/or other technologies described herein can be effected (e.g., hardware, software, and/or firmware), and that the preferred vehicle will vary with the context in which the processes and/or systems and/or other technologies are deployed. For example, if an implementer determines that speed and accuracy are paramount, the implementer may opt for a mainly hardware and/or firmware vehicle; alternatively, if flexibility is paramount, the implementer may opt for a mainly software implementation; or, yet again alternatively, the implementer may opt for some combination of hardware, software, and/or firmware. Hence, there are several possible vehicles by which the processes and/or devices and/or other technologies described herein may be effected, none of which is inherently superior to the other in that any vehicle to be utilized is a choice dependent upon the context in which the vehicle will be deployed and the specific concerns (e.g., speed, flexibility, or predictability) of the implementer, any of which may vary. Those skilled in the art will recognize that optical aspects of implementations will typically employ optically-oriented hardware, software, and or firmware.
The foregoing detailed description has set forth various embodiments of the devices and/or processes via the use of block diagrams, flowcharts, and/or examples. Insofar as such block diagrams, flowcharts, and/or examples contain one or more functions and/or operations, it will be understood by those within the art that each function and/or operation within such block diagrams, flowcharts, or examples can be implemented, individually and/or collectively, by a wide range of hardware, software, firmware, or virtually any combination thereof. In one embodiment, several portions of the subject matter described herein may be implemented via Application Specific Integrated Circuitry (ASICs), Field Programmable Gate Arrays (FPGAs), digital signal processors (DSPs), or other integrated formats. However, those skilled in the art will recognize that some aspects of the embodiments disclosed herein, in whole or in part, can be equivalently implemented in integrated circuitry, as one or more computer programs running on one or more computers (e.g., as one or more programs running on one or more computer systems), as one or more programs running on one or more processors (e.g., as one or more programs running on one or more microprocessors), as firmware, or as virtually any combination thereof, and that designing the circuitry and/or writing the code for the software and or firmware would be well within the skill of one of skill in the art in light of this disclosure. In addition, those skilled in the art will appreciate that the mechanisms of the subject matter described herein are capable of being distributed as a program product in a variety of forms, and that an illustrative embodiment of the subject matter described herein applies regardless of the particular type of signal bearing medium used to actually carry out the distribution. Examples of a signal bearing medium include, but are not limited to, the following: a recordable type medium such as a floppy disk, a hard disk drive, a Compact Disc (CD), a Digital Video Disk (DVD), a digital tape, a computer memory, etc.; and a transmission type medium such as a digital and/or an analog communication medium (e.g., a fiber optic cable, a waveguide, a wired communications link, a wireless communication link, etc.).
In a general sense, those skilled in the art will recognize that the various aspects described herein which can be implemented, individually and/or collectively, by a wide range of hardware, software, firmware, or any combination thereof can be viewed as being composed of various types of “electrical circuitry.” Consequently, as used herein “electrical circuitry” includes, but is not limited to, electrical circuitry having at least one discrete electrical circuit, electrical circuitry having at least one integrated circuit, electrical circuitry having at least one application specific integrated circuit, electrical circuitry forming a general purpose computing device configured by a computer program (e.g., a general purpose computer configured by a computer program which at least partially carries out processes and/or devices described herein, or a microprocessor configured by a computer program which at least partially carries out processes and/or devices described herein), electrical circuitry forming a memory device (e.g., forms of random access memory), and/or electrical circuitry forming a communications device (e.g., a modem, communications switch, or optical-electrical equipment). Those having skill in the art will recognize that the subject matter described herein may be implemented in an analog or digital fashion or some combination thereof.
Those having skill in the art will recognize that it is common within the art to describe devices and/or processes in the fashion set forth herein, and thereafter use engineering practices to integrate such described devices and/or processes into data processing systems. That is, at least a portion of the devices and/or processes described herein can be integrated into a data processing system via a reasonable amount of experimentation. Those having skill in the art will recognize that a typical data processing system generally includes one or more of a system unit housing, a video display device, a memory such as volatile and non-volatile memory, processors such as microprocessors and digital signal processors, computational entities such as operating systems, drivers, graphical user interfaces, and applications programs, one or more interaction devices, such as a touch pad or screen, and/or control systems including feedback loops and control motors (e.g., feedback for sensing position and/or velocity; control motors for moving and/or adjusting components and/or quantities). A typical data processing system may be implemented utilizing any suitable commercially available components, such as those typically found in data computing/communication and/or network computing/communication systems.
The herein described subject matter sometimes illustrates different components contained within, or connected with, different other components. It is to be understood that such depicted architectures are merely exemplary, and that in fact many other architectures can be implemented which achieve the same functionality. In a conceptual sense, any arrangement of components to achieve the same functionality is effectively “associated” such that the desired functionality is achieved. Hence, any two components herein combined to achieve a particular functionality can be seen as “associated with” each other such that the desired functionality is achieved, irrespective of architectures or intermedial components. Likewise, any two components so associated can also be viewed as being “operably connected”, or “operably coupled”, to each other to achieve the desired functionality, and any two components capable of being so associated can also be viewed as being “operably couplable”, to each other to achieve the desired functionality. Specific examples of operably couplable include but are not limited to physically mateable and/or physically interacting components and/or wirelessly interactable and/or wirelessly interacting components and/or logically interacting and/or logically interactable components.
While particular aspects of the present subject matter described herein have been shown and described, it will be apparent to those skilled in the art that, based upon the teachings herein, changes and modifications may be made without departing from the subject matter described herein and its broader aspects and, therefore, the appended claims are to encompass within their scope all such changes and modifications as are within the true spirit and scope of the subject matter described herein. Furthermore, it is to be understood that the invention is defined by the appended claims.
It will be understood by those within the art that, in general, terms used herein, and especially in the appended claims (e.g., bodies of the appended claims) are generally intended as “open” terms (e.g., the term “including” should be interpreted as “including but not limited to,” the term “having” should be interpreted as “having at least,” the term “includes” should be interpreted as “includes but is not limited to,” etc.). It will be further understood by those within the art that if a specific number of an introduced claim recitation is intended, such an intent will be explicitly recited in the claim, and in the absence of such recitation no such intent is present. For example, as an aid to understanding, the following appended claims may contain usage of the introductory phrases “at least one” and “one or more” to introduce claim recitations. However, the use of such phrases should not be construed to imply that the introduction of a claim recitation by the indefinite articles “a” or “an” limits any particular claim containing such introduced claim recitation to inventions containing only one such recitation, even when the same claim includes the introductory phrases “one or more” or “at least one” and indefinite articles such as “a” or “an” (e.g., “a” and/or “an” should typically be interpreted to mean “at least one” or “one or more”); the same holds true for the use of definite articles used to introduce claim recitations.
In addition, even if a specific number of an introduced claim recitation is explicitly recited, those skilled in the art will recognize that such recitation should typically be interpreted to mean at least the recited number (e.g., the bare recitation of “two recitations,” without other modifiers, typically means at least two recitations, or two or more recitations). Furthermore, in those instances where a convention analogous to “at least one of A, B, and C, etc.” is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., “ a system having at least one of A, B, and C” would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and/or A, B, and C together, etc.).
In those instances where a convention analogous to “at least one of A, B, or C, etc.” is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., “ a system having at least one of A, B, or C” would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and/or A, B, and C together, etc.). It will be further understood by those within the art that virtually any disjunctive word and/or phrase presenting two or more alternative terms, whether in the description, claims, or drawings, should be understood to contemplate the possibilities of including one of the terms, either of the terms, or both terms. For example, the phrase “A or B” will be understood to include the possibilities of “A” or “B” or “A and B.”
The present application is related to and claims the benefit of the earliest available effective filing date(s) from the following listed application(s) (the “Related Applications”) (e.g., claims earliest available priority dates for other than provisional patent applications or claims benefits under 35 USC §119(e) for provisional patent applications, for any and all parent, grandparent, great-grandparent, etc. applications of the Related Application(s)). All subject matter of the Related Applications and of any and all parent, grandparent, great-grandparent, etc. applications of the Related Applications is incorporated herein by reference to the extent such subject matter is not inconsistent herewith. For purposes of the USPTO extra-statutory requirements, the present application constitutes a continuation-in-part of U.S. patent application Ser. No. 12/228,664, entitled SYSTEM AND METHOD FOR TRANSMITTING ILLUSORY IDENTIFICATION CHARACTERISTICS, naming Alexander J. Cohen; Edward K. Y. Jung; Royce A. Levien; Robert W. Lord; Mark A. Malamud; William H. Mangione-Smith; John D. Rinaldo, Jr. and Clarence T. Tegreene as inventors, filed Aug. 14, 2008, now abandoned. For purposes of the USPTO extra-statutory requirements, the present application constitutes a continuation-in-part of U.S. patent application Ser. No. 12/228,873, entitled SYSTEM AND METHOD FOR TRANSMITTING ILLUSORY AND NON-ILLUSORY IDENTIFICATION CHARACTERISTICS, naming Alexander J. Cohen; Edward K. Y. Jung; Royce A. Levien; Robert W. Lord; Mark A. Malamud; William H. Mangione-Smith; John D. Rinaldo, Jr. and Clarence T. Tegreene as inventors, filed Aug. 15, 2008, now abandoned. For purposes of the USPTO extra-statutory requirements, the present application constitutes a continuation-in-part of U.S. patent application Ser. No. 12/287,268, entitled SYSTEM AND METHOD FOR TRANSMITTING ILLUSORY IDENTIFICATION CHARACTERISTICS, naming Alexander J. Cohen; Edward K. Y. Jung; Royce A. Levien; Robert W. Lord; Mark A. Malamud; William H. Mangione-Smith; John D. Rinaldo, Jr. and Clarence T. Tegreene as inventors, filed Oct. 7, 2008, now U.S. Pat. No. 8,224,907. For purposes of the USPTO extra-statutory requirements, the present application constitutes a continuation-in-part of U.S. patent application Ser. No. 12/454,113, entitled SYSTEM AND METHOD FOR MODIFYING ILLUSORY USER IDENTIFICATION CHARACTERISTICS, naming Alexander J. Cohen; Edward K. Y. Jung; Royce A. Levien; Robert W. Lord; Mark A. Malamud; William H. Mangione-Smith; John D. Rinaldo, Jr. and Clarence T. Tegreene as inventors, filed May 12, 2009, now abandoned. For purposes of the USPTO extra-statutory requirements, the present application constitutes a continuation-in-part of U.S. patent application Ser. No. 12/799,794, entitled SYSTEM AND METHOD FOR CONDITIONALLY TRANSMITTING ONE OR MORE LOCUM TENENTES, naming Alexander J. Cohen; Edward K. Y. Jung; Royce A. Levien; Robert W. Lord; Mark A. Malamud; William H. Mangione-Smith; John D. Rinaldo, Jr. and Clarence T. Tegreene as inventors, filed Apr. 29, 2010, now abandoned. For purposes of the USPTO extra-statutory requirements, the present application constitutes a continuation-in-part of U.S. patent application Ser. No. 12/802,139, entitled OBFUSCATING IDENTITY OF A SOURCE ENTITY AFFILIATED WITH A COMMUNIQUÉ IN ACCORDANCE WITH CONDITIONAL DIRECTIVE PROVIDED BY A RECEIVING ENTITY, naming Alexander J. Cohen; Edward K. Y. Jung; Royce A. Levien; Robert W. Lord; Mark A. Malamud; William H. Mangione-Smith; John D. Rinaldo, Jr. and Clarence T. Tegreene as inventors, filed May 27, 2010, which is currently co-pending, or is an application of which a currently co-pending application is entitled to the benefit of the filing date. For purposes of the USPTO extra-statutory requirements, the present application constitutes a continuation-in-part of U. S. patent application Ser. No. 12/802,136, entitled OBFUSCATING IDENTITY OF A SOURCE ENTITY AFFILIATED WITH A COMMUNIQUÉ IN ACCORDANCE WITH CONDITIONAL DIRECTIVE PROVIDED BY A RECEIVING ENTITY, naming Alexander J. Cohen; Edward K. Y. Jung; Royce A. Levien; Robert W. Lord; Mark A. Malamud; William H. Mangione-Smith; John D. Rinaldo, Jr. and Clarence T. Tegreene as inventors, filed May 28, 2010, which is currently co-pending, or is an application of which a currently co-pending application is entitled to the benefit of the filing date.
Number | Name | Date | Kind |
---|---|---|---|
3985972 | Rolin et al. | Oct 1976 | A |
4218738 | Matyas et al. | Aug 1980 | A |
5493692 | Theimer et al. | Feb 1996 | A |
5508699 | Silverman | Apr 1996 | A |
5732138 | Noll et al. | Mar 1998 | A |
5751806 | Ryan | May 1998 | A |
5790074 | Rangedahl et al. | Aug 1998 | A |
5812639 | Bartholomew et al. | Sep 1998 | A |
5835856 | Patel | Nov 1998 | A |
5933498 | Schneck et al. | Aug 1999 | A |
5978940 | Newman et al. | Nov 1999 | A |
5987633 | Newman et al. | Nov 1999 | A |
6005926 | Mashinsky | Dec 1999 | A |
6026291 | Carlsson et al. | Feb 2000 | A |
6199102 | Cobb | Mar 2001 | B1 |
6224109 | Yang | May 2001 | B1 |
6351745 | Itakura et al. | Feb 2002 | B1 |
6396531 | Gerszberg et al. | May 2002 | B1 |
6493696 | Chazin | Dec 2002 | B1 |
6496931 | Rajchel et al. | Dec 2002 | B1 |
6510236 | Crane et al. | Jan 2003 | B1 |
6522889 | Aarnio | Feb 2003 | B1 |
6529592 | Khan | Mar 2003 | B1 |
6563913 | Kaghazian | May 2003 | B1 |
6571279 | Herz et al. | May 2003 | B1 |
6591291 | Gabber et al. | Jul 2003 | B1 |
6738808 | Zellner et al. | May 2004 | B1 |
6816885 | Raghunandan | Nov 2004 | B1 |
6857021 | Schuster et al. | Feb 2005 | B1 |
6917610 | Kung et al. | Jul 2005 | B1 |
6918039 | Hind et al. | Jul 2005 | B1 |
6937730 | Buxton | Aug 2005 | B1 |
6985569 | Baker | Jan 2006 | B2 |
6990590 | Hanson et al. | Jan 2006 | B2 |
7007025 | Nason et al. | Feb 2006 | B1 |
7133837 | Barnes, Jr. | Nov 2006 | B1 |
7159011 | Knight et al. | Jan 2007 | B1 |
7203315 | Livesay | Apr 2007 | B1 |
7225342 | Takao et al. | May 2007 | B2 |
7248885 | Benco et al. | Jul 2007 | B2 |
7275090 | Oeda et al. | Sep 2007 | B2 |
7278023 | Siegel et al. | Oct 2007 | B1 |
7308251 | Karaoguz | Dec 2007 | B2 |
7310816 | Burns et al. | Dec 2007 | B1 |
7327312 | Harris | Feb 2008 | B1 |
7334267 | Engstrom | Feb 2008 | B2 |
7363024 | Jenkins | Apr 2008 | B2 |
7382881 | Uusitalo et al. | Jun 2008 | B2 |
7389541 | Jia et al. | Jun 2008 | B2 |
7400878 | Hassan et al. | Jul 2008 | B2 |
7401159 | Aviani et al. | Jul 2008 | B1 |
7458095 | Forsberg | Nov 2008 | B2 |
7555769 | Shapiro | Jun 2009 | B1 |
7567936 | Peckover et al. | Jul 2009 | B1 |
7587480 | Gebhart et al. | Sep 2009 | B2 |
7614081 | Prohel et al. | Nov 2009 | B2 |
7616943 | Oesterling | Nov 2009 | B2 |
7623639 | Thai et al. | Nov 2009 | B2 |
7627334 | Cohen et al. | Dec 2009 | B2 |
7630495 | Kiiveri et al. | Dec 2009 | B2 |
7634295 | Hayaashi et al. | Dec 2009 | B2 |
7643484 | Willman et al. | Jan 2010 | B2 |
7724918 | Balakrishnan et al. | May 2010 | B2 |
7783741 | Hardt | Aug 2010 | B2 |
7787870 | Burgan et al. | Aug 2010 | B2 |
7797024 | Sutardja | Sep 2010 | B2 |
7814017 | Vancini et al. | Oct 2010 | B2 |
7827245 | Cohen | Nov 2010 | B2 |
7920050 | Juels et al. | Apr 2011 | B2 |
7921052 | Dabney et al. | Apr 2011 | B2 |
7940302 | Mehrotra et al. | May 2011 | B2 |
7966664 | Makkinejad | Jun 2011 | B2 |
8140062 | Hildner et al. | Mar 2012 | B1 |
8190126 | Whitney | May 2012 | B1 |
8190128 | Lundy et al. | May 2012 | B1 |
8626848 | Cohen et al. | Jan 2014 | B2 |
8730836 | Cohen et al. | May 2014 | B2 |
8850044 | Cohen et al. | Sep 2014 | B2 |
20010023432 | Council et al. | Sep 2001 | A1 |
20010031631 | Pitts | Oct 2001 | A1 |
20010034677 | Farhat et al. | Oct 2001 | A1 |
20010034723 | Subramaniam | Oct 2001 | A1 |
20010036822 | Mead et al. | Nov 2001 | A1 |
20010047391 | Szutu | Nov 2001 | A1 |
20020044067 | Ilcisin | Apr 2002 | A1 |
20020069077 | Brophy et al. | Jun 2002 | A1 |
20020077078 | Antti | Jun 2002 | A1 |
20020077897 | Zellner et al. | Jun 2002 | A1 |
20020081972 | Rankin | Jun 2002 | A1 |
20020099822 | Rubin et al. | Jul 2002 | A1 |
20020101997 | Curtis et al. | Aug 2002 | A1 |
20020102523 | Pelletier | Aug 2002 | A1 |
20020111845 | Chong | Aug 2002 | A1 |
20020111954 | McCoy | Aug 2002 | A1 |
20020143869 | Cohen | Oct 2002 | A1 |
20020154055 | Davis et al. | Oct 2002 | A1 |
20020163572 | Center, Jr. et al. | Nov 2002 | A1 |
20020169664 | Walker et al. | Nov 2002 | A1 |
20020169840 | Sheldon et al. | Nov 2002 | A1 |
20020174073 | Nordman et al. | Nov 2002 | A1 |
20020174363 | Chefalas et al. | Nov 2002 | A1 |
20020177449 | McDonnell et al. | Nov 2002 | A1 |
20020188562 | Igarashi et al. | Dec 2002 | A1 |
20020198777 | Yuasa | Dec 2002 | A1 |
20030008672 | Fujii | Jan 2003 | A1 |
20030009593 | Apte | Jan 2003 | A1 |
20030009687 | Ferchau | Jan 2003 | A1 |
20030014286 | Cappellini | Jan 2003 | A1 |
20030014637 | Ellison et al. | Jan 2003 | A1 |
20030021413 | Kiiveri et al. | Jan 2003 | A1 |
20030040326 | Levy et al. | Feb 2003 | A1 |
20030044050 | Clark et al. | Mar 2003 | A1 |
20030086543 | Raymond | May 2003 | A1 |
20030134645 | Stern et al. | Jul 2003 | A1 |
20030145039 | Bonney et al. | Jul 2003 | A1 |
20030149881 | Patel et al. | Aug 2003 | A1 |
20030154254 | Awasthi | Aug 2003 | A1 |
20030158960 | Engberg | Aug 2003 | A1 |
20030177357 | Chamberlin et al. | Sep 2003 | A1 |
20030217118 | Kobayashi et al. | Nov 2003 | A1 |
20030217151 | Roese et al. | Nov 2003 | A1 |
20030217287 | Kruglenko | Nov 2003 | A1 |
20030220978 | Rhodes | Nov 2003 | A1 |
20030224754 | Herzog | Dec 2003 | A1 |
20030227386 | Pulkkinen et al. | Dec 2003 | A1 |
20030233329 | Laraki et al. | Dec 2003 | A1 |
20030236095 | Ross | Dec 2003 | A1 |
20040015553 | Griffin | Jan 2004 | A1 |
20040030932 | Juels et al. | Feb 2004 | A1 |
20040064692 | Kahn et al. | Apr 2004 | A1 |
20040064734 | Ehrlich | Apr 2004 | A1 |
20040083166 | Pailles | Apr 2004 | A1 |
20040111625 | Duffy et al. | Jun 2004 | A1 |
20040128301 | Thint et al. | Jul 2004 | A1 |
20040139204 | Ergezinger et al. | Jul 2004 | A1 |
20040162821 | Buckwalter et al. | Aug 2004 | A1 |
20040162904 | Eida et al. | Aug 2004 | A1 |
20040165702 | Finnigan | Aug 2004 | A1 |
20040177122 | Appelman et al. | Sep 2004 | A1 |
20040177280 | Maruyama et al. | Sep 2004 | A1 |
20040178880 | Meyer et al. | Sep 2004 | A1 |
20040181683 | Jia et al. | Sep 2004 | A1 |
20040203776 | Jun | Oct 2004 | A1 |
20040236838 | Tout | Nov 2004 | A1 |
20040248588 | Pell et al. | Dec 2004 | A1 |
20040254998 | Horvitz | Dec 2004 | A1 |
20040255127 | Arnouse | Dec 2004 | A1 |
20040266398 | Adamczyk et al. | Dec 2004 | A1 |
20050004871 | Dort | Jan 2005 | A1 |
20050008135 | Bressler | Jan 2005 | A1 |
20050014485 | Kokkonen et al. | Jan 2005 | A1 |
20050021826 | Kumar | Jan 2005 | A1 |
20050027618 | Zucker et al. | Feb 2005 | A1 |
20050027839 | Day et al. | Feb 2005 | A1 |
20050031106 | Henderson | Feb 2005 | A1 |
20050044423 | Mellmer et al. | Feb 2005 | A1 |
20050048951 | Saito | Mar 2005 | A1 |
20050063544 | Uusitalo et al. | Mar 2005 | A1 |
20050075096 | Aljuraid | Apr 2005 | A1 |
20050084100 | Spies et al. | Apr 2005 | A1 |
20050091393 | Gleeson et al. | Apr 2005 | A1 |
20050091543 | Holtzman et al. | Apr 2005 | A1 |
20050097337 | Sesek | May 2005 | A1 |
20050100140 | Tsai | May 2005 | A1 |
20050114343 | Wesinger, Jr. et al. | May 2005 | A1 |
20050136903 | Kashima et al. | Jun 2005 | A1 |
20050172120 | Wang et al. | Aug 2005 | A1 |
20050192056 | Karaki | Sep 2005 | A1 |
20050198131 | Appelman et al. | Sep 2005 | A1 |
20050198171 | Landsman et al. | Sep 2005 | A1 |
20050204005 | Purcell | Sep 2005 | A1 |
20050204008 | Shinbrood | Sep 2005 | A1 |
20050204037 | Levy | Sep 2005 | A1 |
20050226468 | Deshpande et al. | Oct 2005 | A1 |
20050227705 | Rousu et al. | Oct 2005 | A1 |
20050232423 | Horvitz et al. | Oct 2005 | A1 |
20050246419 | Jaatinen | Nov 2005 | A1 |
20050275543 | Hisano | Dec 2005 | A1 |
20060005023 | Homer et al. | Jan 2006 | A1 |
20060026438 | Stern et al. | Feb 2006 | A1 |
20060031301 | Herz et al. | Feb 2006 | A1 |
20060031369 | Caron et al. | Feb 2006 | A1 |
20060034441 | Kraft | Feb 2006 | A1 |
20060041507 | Novack et al. | Feb 2006 | A1 |
20060052095 | Vazvan | Mar 2006 | A1 |
20060075037 | Rothschild | Apr 2006 | A1 |
20060075051 | Jain et al. | Apr 2006 | A1 |
20060079238 | Liu et al. | Apr 2006 | A1 |
20060099967 | Colvin et al. | May 2006 | A1 |
20060109983 | Young et al. | May 2006 | A1 |
20060116142 | Cofta | Jun 2006 | A1 |
20060123245 | Avidan et al. | Jun 2006 | A1 |
20060148400 | Farrow | Jul 2006 | A1 |
20060152374 | Singer et al. | Jul 2006 | A1 |
20060167991 | Heikes et al. | Jul 2006 | A1 |
20060168059 | Chang et al. | Jul 2006 | A1 |
20060173957 | Robinson et al. | Aug 2006 | A1 |
20060176821 | Hemesath et al. | Aug 2006 | A1 |
20060199575 | Moore et al. | Sep 2006 | A1 |
20060227955 | Thai et al. | Oct 2006 | A1 |
20060237531 | Heffez et al. | Oct 2006 | A1 |
20060248011 | Hecht-Nielsen et al. | Nov 2006 | A1 |
20060256959 | Hymes | Nov 2006 | A1 |
20060274896 | Livesay | Dec 2006 | A1 |
20060276175 | Chandran | Dec 2006 | A1 |
20060276226 | Jiang | Dec 2006 | A1 |
20070022165 | Daniels et al. | Jan 2007 | A1 |
20070024527 | Heikkinen et al. | Feb 2007 | A1 |
20070030824 | Ribaudo et al. | Feb 2007 | A1 |
20070032225 | Konicek et al. | Feb 2007 | A1 |
20070036314 | Kloberdans et al. | Feb 2007 | A1 |
20070074046 | Czajkowski et al. | Mar 2007 | A1 |
20070074590 | Smith | Apr 2007 | A1 |
20070118874 | Adams | May 2007 | A1 |
20070127658 | Gruchala et al. | Jun 2007 | A1 |
20070130323 | Landsman et al. | Jun 2007 | A1 |
20070140145 | Kumar et al. | Jun 2007 | A1 |
20070164102 | Haertel | Jul 2007 | A1 |
20070168430 | Brun et al. | Jul 2007 | A1 |
20070180122 | Barrett | Aug 2007 | A1 |
20070198639 | Litwin et al. | Aug 2007 | A1 |
20070203644 | Thota et al. | Aug 2007 | A1 |
20070204026 | Berger | Aug 2007 | A1 |
20070208816 | Baldwin et al. | Sep 2007 | A1 |
20070208947 | Sudo et al. | Sep 2007 | A1 |
20070220273 | Campisi | Sep 2007 | A1 |
20070242827 | Prafullchandra et al. | Oct 2007 | A1 |
20070243880 | Gits et al. | Oct 2007 | A1 |
20070245263 | Hale et al. | Oct 2007 | A1 |
20070250571 | Griffin, Jr. | Oct 2007 | A1 |
20070250641 | Flannery et al. | Oct 2007 | A1 |
20070250920 | Lindsay | Oct 2007 | A1 |
20070255704 | Baek et al. | Nov 2007 | A1 |
20070264974 | Frank et al. | Nov 2007 | A1 |
20070277235 | Barrett et al. | Nov 2007 | A1 |
20070282791 | Amzalag | Dec 2007 | A1 |
20070293202 | Moshir et al. | Dec 2007 | A1 |
20070294096 | Randall et al. | Dec 2007 | A1 |
20070297641 | Criddle et al. | Dec 2007 | A1 |
20080005325 | Wynn et al. | Jan 2008 | A1 |
20080010665 | Hinton et al. | Jan 2008 | A1 |
20080021962 | Ryan et al. | Jan 2008 | A1 |
20080037040 | Hashimoto et al. | Feb 2008 | A1 |
20080056468 | Fredlund et al. | Mar 2008 | A1 |
20080071544 | Beaufays et al. | Mar 2008 | A1 |
20080077431 | Calder | Mar 2008 | A1 |
20080086646 | Pizano | Apr 2008 | A1 |
20080107274 | Worthy | May 2008 | A1 |
20080108324 | Moshir et al. | May 2008 | A1 |
20080118150 | Balakrishnan et al. | May 2008 | A1 |
20080130630 | Shim et al. | Jun 2008 | A1 |
20080132255 | Benco et al. | Jun 2008 | A1 |
20080140769 | Matoba | Jun 2008 | A1 |
20080146157 | Aaron | Jun 2008 | A1 |
20080147849 | Bruker | Jun 2008 | A1 |
20080154697 | Guday et al. | Jun 2008 | A1 |
20080163365 | Austin et al. | Jul 2008 | A1 |
20080169903 | Fein et al. | Jul 2008 | A1 |
20080194290 | Lebert et al. | Aug 2008 | A1 |
20080196098 | Cottrell et al. | Aug 2008 | A1 |
20080207329 | Wallace et al. | Aug 2008 | A1 |
20080235336 | Stern et al. | Sep 2008 | A1 |
20080242265 | Cohen et al. | Oct 2008 | A1 |
20080247543 | Mick et al. | Oct 2008 | A1 |
20080248815 | Busch | Oct 2008 | A1 |
20080250129 | Carpenter et al. | Oct 2008 | A1 |
20080254817 | Tornkvist | Oct 2008 | A1 |
20080267099 | Curcio et al. | Oct 2008 | A1 |
20080274694 | Castell et al. | Nov 2008 | A1 |
20080282344 | Shuster | Nov 2008 | A1 |
20080294556 | Anderson | Nov 2008 | A1 |
20080294726 | Sidman | Nov 2008 | A1 |
20080300859 | Chen et al. | Dec 2008 | A1 |
20080306972 | Wilkin et al. | Dec 2008 | A1 |
20080318598 | Fry | Dec 2008 | A1 |
20090005072 | Forstall et al. | Jan 2009 | A1 |
20090006565 | Velusamy et al. | Jan 2009 | A1 |
20090081989 | Wuhrer | Mar 2009 | A1 |
20090083826 | Baribault | Mar 2009 | A1 |
20090099701 | Li et al. | Apr 2009 | A1 |
20090109037 | Farmer | Apr 2009 | A1 |
20090113005 | Gregg et al. | Apr 2009 | A1 |
20090131022 | Buckley et al. | May 2009 | A1 |
20090132419 | Grammer et al. | May 2009 | A1 |
20090158054 | Dijk et al. | Jun 2009 | A1 |
20090170532 | Lee et al. | Jul 2009 | A1 |
20090183215 | McCartie et al. | Jul 2009 | A1 |
20090195445 | DeHaas | Aug 2009 | A1 |
20090204580 | Seamon et al. | Aug 2009 | A1 |
20090215469 | Fisher et al. | Aug 2009 | A1 |
20090224970 | Tsau | Sep 2009 | A1 |
20090227268 | Sorensson et al. | Sep 2009 | A1 |
20090232288 | Forbes et al. | Sep 2009 | A1 |
20090234764 | Friesen | Sep 2009 | A1 |
20090248844 | Sommer et al. | Oct 2009 | A1 |
20090262987 | Ioffe et al. | Oct 2009 | A1 |
20090265326 | Lehrman et al. | Oct 2009 | A1 |
20090275363 | McGregor et al. | Nov 2009 | A1 |
20090298474 | George | Dec 2009 | A1 |
20090300774 | Makkinejad | Dec 2009 | A1 |
20090307087 | Haas | Dec 2009 | A1 |
20090318112 | Vasten | Dec 2009 | A1 |
20090319172 | Almeida et al. | Dec 2009 | A1 |
20100009657 | Dingler et al. | Jan 2010 | A1 |
20100015991 | Evans et al. | Jan 2010 | A1 |
20100024042 | Motahari et al. | Jan 2010 | A1 |
20100042583 | Gervais et al. | Feb 2010 | A1 |
20100042685 | Yanovski et al. | Feb 2010 | A1 |
20100053169 | Cook | Mar 2010 | A1 |
20100071035 | Budko et al. | Mar 2010 | A1 |
20100146583 | Prehofer et al. | Jun 2010 | A1 |
20100174911 | Isshiki | Jul 2010 | A1 |
20100183125 | Hayes, Jr. et al. | Jul 2010 | A1 |
20100205541 | Rapaport et al. | Aug 2010 | A1 |
20100257222 | Hamilton, II et al. | Oct 2010 | A1 |
20100274815 | Vanasco | Oct 2010 | A1 |
20100281051 | Sheffi et al. | Nov 2010 | A1 |
20100283728 | Hollemans et al. | Nov 2010 | A1 |
20100313253 | Reiss | Dec 2010 | A1 |
20110016053 | Dittmer | Jan 2011 | A1 |
20110069661 | Waytena, Jr. et al. | Mar 2011 | A1 |
20110143716 | Shaw | Jun 2011 | A1 |
20110238767 | Murphy | Sep 2011 | A1 |
20120028659 | Whitney | Feb 2012 | A1 |
20120034930 | Zellner et al. | Feb 2012 | A1 |
20120135775 | Drozt et al. | May 2012 | A1 |
20120174233 | Waterson | Jul 2012 | A1 |
20130086225 | Gay | Apr 2013 | A1 |
20140047560 | Meyer | Feb 2014 | A1 |
Number | Date | Country |
---|---|---|
1688150 | Oct 2005 | CN |
101184264 | May 2008 | CN |
101268470 | Sep 2008 | CN |
101370209 | Feb 2009 | CN |
Entry |
---|
“Sometimes, I just don't want them to know it's me calling . . . ”; spoofcard.com; pp. 1-2; located at: http://www.spoofcard.com/; printed on Jul. 8, 2010. |
“Spoof Caller ID with Telespoof.com”; Telespoof.com; Bearing a date of 2010; pp. 1-2; located at: http://www.telespoof.com/; printed on Jul. 8, 2010. |
“Spoofkit is the ultimate windup kit available on the net today”; Spoofkit.com; Bearing dates of 2010-2014; pp. 1-6; located at: http://www.spoofkit.com/; printed on Jul. 8, 2010. |
Chinese State Intellectual Property Office, Notification of First Office Action; App. No. 201110279028.X; Nov. 3, 2015, (received by our agent on Nov. 13, 2015); pp. 1-7 (machine translation provided). |
Chinese State Intellectual Property Office, Notification of First Office Action; App. No. 201110279048.7; Sep. 16, 2015, (received by our agent on Sep. 17, 15); pp. 1-13 (machine translation provided). |
Chinese State Intellectual Property Office, Notification of First Office Action, App. No. 2011/10279007.8 Jul. 17, 2015; pp. 1-23 (machine translation provided). |
Chinese State Intellectual Property Office, Notification of First Office Action; App. No. 201110279036.4; Sep. 16, 2015, (received by our agent on Sep. 28, 2015); pp. 1-10 (machine translation provided). |
Number | Date | Country | |
---|---|---|---|
20110041061 A1 | Feb 2011 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 12228664 | Aug 2008 | US |
Child | 12802863 | US | |
Parent | 12228873 | Aug 2008 | US |
Child | 12228664 | US | |
Parent | 12287268 | Oct 2008 | US |
Child | 12228873 | US | |
Parent | 12454113 | May 2009 | US |
Child | 12287268 | US | |
Parent | 12779794 | Apr 2010 | US |
Child | 12454113 | US | |
Parent | 12802139 | May 2010 | US |
Child | 12779794 | US | |
Parent | 12802136 | May 2010 | US |
Child | 12802139 | US |