KR20120034558A - Conditionally intercepting data indicating one or more aspects of a communique to obfuscate the one or more aspects of the communique - Google Patents

Abstract

The computer-implemented method conditionally obfuscates coronike aspect data associated with a particular source entity and displays one or more aspects of the communique directed towards the end user entity and towards the end user entity. intercepting, in accordance with one or more conditional instructions of the end user entity to obfuscate; And in response to intercepting the cocaine aspect data, sending to the end user entity secret indicator data that secretly indicates one or more aspects of the cocaine upon receipt by the end user entity, instead of sending a direct representation of the cocaine to the end user entity. But not limited to. In addition to the foregoing, other method aspects are described in the claims, drawings, and text that form part of this disclosure.

Description

CONDITIONALLY INTERCEPTING DATA INDICATING ONE OR MORE ASPECTS OF A COMMUNIQUE TO OBFUSCATE THE ONE OR MORE ASPECTS OF THE COMMUNIQUE}

This application claims and relates to the benefit of the highest available valid application date (s) from the application (s) listed below ("related application"). (E.g., claiming interest under 35 USC §119 (e) for provisional applications or making priority use for applications that are not provisional applications for any and all subapplications, grandfathering applications, great-admission applications, etc. of the relevant application (s) All subject matters, such as related applications and any and all subapplications, grandfathering applications, great-admission applications, etc. of related applications, are to be regarded as reference to the present disclosure unless such a subject matter contradicts the present disclosure. Included.

For purposes of USPTO additional statutory requirements, this application is US Application No. 12 / 228,664, titled "SYSTEM AND METHOD FOR TRANSMITTING ILLUSORY IDENTIFICATION CHARACTERISTICS." And the inventor is Alexander J .. Alexander J. Cohen, Edward K. Wye. Edward K.Y.Jung, Royce A. Levi A. Levien, Robert W. Robert W. Lord, Mark A. Mark A. Malamud, William H. William H. Mangione-Smith, John D. Rinaldo, Jr. and Clarence Tee. Clareness T. Tegreene, a partial continuing application of the U.S. patent application filed on August 14, 2008, which filed the current application or granted the benefit of the date of application to the currently pending application. Application.

For purposes of USPTO additional statutory requirements, this application is US Application No. 12 / 228,873, entitled "SYSTEM AND METHOD FOR TRANSMITTING ILLUSORY". AND NONILLUSORY IDENTIFICATION CHARACTERISTICS), and the inventor is Alexander J .. Cohen, Edward K. Wai. Jung, Royce A. Levien, Robert W. Rod, Mark A. Malmouth, William H. Manzoni-Smith, John D. Rinaldo, Jr. and Clarence Tee. Tegrin, which is part of a pending US patent application filed on August 15, 2008, is an application that is currently pending or has granted the benefit of the date of application to the currently pending application.

For purposes of USPTO additional statutory requirements, this application is US Application No. 12 / 287,268, entitled "SYSTEM AND METHOD FOR TRANSMITTING ILLUSORY IDENTIFICATION CHARACTERISTICS." And the inventor is Alexander J .. Cohen, Edward K. Wai. Jung, Royce A. Levien, Robert W. Rod, Mark A. Malmouth, William H. Manzoni-Smith, John D. Rinaldo, Jr. and Clarence Tee. Tegrin, a partial continuing application of the United States Patent Application, filed Oct. 7, 2008, which is a pending application or grants a benefit of a filing date to an application that is currently pending.

For purposes of USPTO additional statutory requirements, this application is US Application No. 12 / 454,113, entitled "SYSTEM AND METHOD FOR MODIFYING ILLUSORY USER IDENTIFICATION". CHARACTERISTICS) ", and the inventor is Alexander J. Cohen, Edward K. Wai. Jung, Royce A. Levien, Robert W. Rod, Mark A. Malmouth, William H. Manzoni-Smith, John D. Rinaldo, Jr. and Clarence Tee. Tegrin, a partial continuing application of a US patent application filed on May 12, 2009, which is a pending application or grants a benefit of a filing date to a currently pending application.

For purposes of USPTO additional statutory requirements, this application is US Application No. 12 / 799,794, entitled “SYSTEM AND METHOD FOR CONDITIONALLY TRANSMITTING ONE” OR MORE LOCUM TENENTES) ", and the inventor is Alexander J. Cohen, Edward K. Wai. Jung, Royce A. Levien, Robert W. Rod, Mark A. Malmouth, William H. Manzoni-Smith, John D. Rinaldo, Jr. and Clarence Tee. Tegrin, which is a partial continuing application of the US patent application filed on April 29, 2010, which application is currently pending or has granted the benefit of the date of application to the currently pending application.

For purposes of USPTO additional statutory requirements, this application is U.S. Application No. 12 / 802,139, entitled "Observation of Identity of Source Entities Linked to Coquenice in accordance with Conditional Instructions Provided by Receiving Entities ( OBFUSCATING IDENTITY OF A SOURCE ENTITY AFFILIATED WITH A COMMUNIQUE IN ACCORDANCE WITH CONDITIONAL DIRECTIVE PROVIDED BY A RECEIVING ENTITY. " Cohen, Edward K. Wai. Jung, Royce A. Levien, Robert W. Rod, Mark A. Malmouth, William H. Manzoni-Smith, John D. Rinaldo, Jr. and Clarence Tee. Tegrin, which is part of a pending US patent application, filed May 27, 2010, which application is currently pending or has granted the benefit of the date of application to a pending application.

For purposes of USPTO additional statutory requirements, this application is U.S. Application No. 12 / 802,136, entitled "Observation of Identity of Source Entities Linked to Coquenice by Conditional Instruction Provided by Receiving Entity" OBFUSCATING IDENTITY OF A SOURCE ENTITY AFFILIATED WITH A COMMUNIQUE IN ACCORDANCE WITH CONDITIONAL DIRECTIVE PROVIDED BY A RECEIVING ENTITY. " Cohen, Edward K. Wai. Jung, Royce A. Levien, Robert W. Rod, Mark A. Malmouth, William H. Manzoni-Smith, John D. Rinaldo, Jr. and Clarence Tee. Tegrin, which is part of a pending US patent application, filed May 28, 2010, which application is currently pending or has granted the benefit of the date of application to a currently pending application.

For purposes of USPTO additional statutory requirements, this application is US Application No. 12 / 802,863, entitled "Source entity linked to a communeke that is sent to the receiving user in accordance with the conditional instructions provided by the receiving user. OBFUSCATING IDENTITY OF A SOURCE ENTITY AFFILIATED WITH A COMMUNIQUE DIRECTED TO A RECEIVING USER AND IN ACCORDANCE WITH CONDITIONAL DIRECTIVE PROVIDED BY THE RECEIVING USER. " Cohen, Edward K. Wai. Jung, Royce A. Levien, Robert W. Rod, Mark A. Malmouth, William H. Manzoni-Smith, John D. Rinaldo, Jr. and Clarence Tee. Tegrin, which is part of a pending US patent application filed on June 14, 2010, which is a pending application or grants a benefit of a filing date to a currently pending application.

For purposes of USPTO additional statutory requirements, this application is US Application No. 12 / 802,922, entitled "Source entity linked to a communeke which is sent to the receiving user in accordance with the conditional instructions provided by the receiving user." OBFUSCATING IDENTITY OF A SOURCE ENTITY AFFILIATED WITH A COMMUNIQUE DIRECTED TO A RECEIVING USER AND IN ACCORDANCE WITH CONDITIONAL DIRECTIVE PROVIDED BY THE RECEIVING USER. " Cohen, Edward K. Wai. Jung, Royce A. Levien, Robert W. Rod, Mark A. Malmouth, William H. Manzoni-Smith, John D. Rinaldo, Jr. and Clarence Tee. Tegrin, which is a partial application of US patent applications filed on June 15, 2010, which applications are currently pending or have granted benefit of the date of application to applications currently pending.

For purposes of USPTO additional statutory requirements, this application is US Application No. 12 / 804,765, entitled "OBFUSCATING RECEPTION OF COMMUNIQUE AFFILIATED WITH A SOURCE ENTITY." And the inventor is Alexander J .. Cohen, Edward K. Wai. Jung, Royce A. Levien, Robert W. Rod, Mark A. Malmouth, William H. Manzoni-Smith, John D. Rinaldo, Jr. and Clarence Tee. Tegrin, which is a partial continuing application of a US patent application filed on July 27, 2010, which application is currently pending or has granted the benefit of the date of application to a currently pending application.

For purposes of USPTO additional statutory requirements, this application is US Application No. 12 / 804,832, entitled "OBFUSCATING RECEPTION OF COMMUNIQUE AFFILIATED WITH A SOURCE ENTITY." And the inventor is Alexander J .. Cohen, Edward K. Wai. Jung, Royce A. Levien, Robert W. Rod, Mark A. Malmouth, William H. Manzoni-Smith, John D. Rinaldo, Jr. and Clarence Tee. Tegrin, which is a partial continuing application of a US patent application filed on July 28, 2010, which application is currently pending or has granted the benefit of the date of application to a currently pending application.

For purposes of USPTO additional statutory requirements, this application is US Application No. 12 / 806,677, entitled “Obtain Obfuscation of Coquenices Associated with Source Entities in Response to Receipt of Information Indicative of Receipt of Coquenices. (OBFUSCATING RECEPTION OF COMMUNIQUE AFFILIATED WITH A SOURCE ENTITY IN RESPONSE TO RECEIVING INFORMATION INDICATING RECEPTION OF THE COMMUNIQUE). " Cohen, Edward K. Wai. Jung, Royce A. Levien, Robert W. Rod, Mark A. Malmouth, William H. Manzoni-Smith, John D. Rinaldo, Jr. and Clarence Tee. Tegrin, which is part of a pending US patent application filed on Aug. 17, 2010, which is a pending application or grants a benefit of a filing date to a currently pending application.

For purposes of USPTO additional statutory requirements, this application is US Application No. 12 / 806,738, entitled “Receive obfuscation of a communike associated with a source entity in response to receiving information indicating receipt of a communike. (OBFUSCATING RECEPTION OF COMMUNIQUE AFFILIATED WITH A SOURCE ENTITY IN RESPONSE TO RECEIVING INFORMATION INDICATING RECEPTION OF THE COMMUNIQUE). " Cohen, Edward K. Wai. Jung, Royce A. Levien, Robert W. Rod, Mark A. Malmouth, William H. Manzoni-Smith, John D. Rinaldo, Jr. and Clarence Tee. Tegrin, which is a partial continuing application of the US patent application filed on August 18, 2010, which application is currently pending or has granted the benefit of the date of application to the currently pending application.

The US Patent and Trademark Office (USPTO) has issued a notice stating that the US Patent Office computer program requires the patent applicant to indicate the serial number and whether the application is a continuation or continuation-in-part. . Stephen G., Gazette, published on March 18, 2003. Stephen G. Kunin's "Benefit of Prior-Filed Application", http://www.uspto.gov/web/offices/com/sol/og/2003/week11 Available at /patbene.htm. As above, the subject of the application (hereinafter referred to as the "applicant") provides a clear reference to the priority claimed application, as described in the decree. Applicants understand that the decree is clear in that specific reference language and does not require any particular or serial number, such as "continued" or "partial", to claim priority in a US patent application. Notwithstanding the foregoing, Applicants have stated that the US Patent Office computer program has some data entry requirements, and therefore Applicant designates this application as part of its sub-application as described above, but such designation is It is clarified that it will not be understood in any way as any kind of explanation and / or recognition as to whether the application includes any new content in addition to the content of its sub-application (s).

The computer-implemented method conditionally obfuscates coronike aspect data associated with a particular source entity and displays one or more aspects of the communique directed towards the end user entity and towards the end user entity. intercepting, in accordance with one or more conditional instructions of the end user entity to obfuscate; And in response to intercepting the cocaine aspect data, sending to the end user entity secret indicator data that secretly indicates one or more aspects of the cocaine upon receipt by the end user entity, instead of sending a direct representation of the cocaine to the end user entity. But not limited to. In addition to the foregoing, other method aspects are described in the claims, drawings, and text that form part of this disclosure.

In one or more various aspects, an associated system includes, but is not limited to, circuitry and / or programming for implementing the method aspects mentioned in the present disclosure, and circuitry and / or programming may be used to implement the aspects mentioned in the present disclosure. It can be virtually any combination depending on the design choices of the system designer of the configured hardware, software, and / or firmware.

The computer-implemented system displays one or more aspects of the communeike directed to the end user entity and the comonike aspect data associated with the particular source entity and one of the end user entities to conditionally obfuscate the commune associated with the source entity. Means for intercepting, in accordance with the conditional instructions above; And in response to intercepting the cocaine aspect data, sending to the end user entity secret indicator data that secretly indicates one or more aspects of the cocaine upon receipt by the end user entity, instead of sending a direct representation of the cocaine to the end user entity. Means for including but not limited to. In addition to the foregoing, other system aspects are described in the claims, drawings, and text that form part of this disclosure.

The computer-implemented system displays one or more aspects of the communeike directed to the end user entity and the comonike aspect data associated with the particular source entity and one of the end user entities to conditionally obfuscate the commune associated with the source entity. A circuit for intercepting according to the above conditional instruction; And in response to intercepting the cocaine aspect data, sending to the end user entity secret indicator data that secretly indicates one or more aspects of the cocaine upon receipt by the end user entity, instead of sending a direct representation of the cocaine to the end user entity. Circuits for, but are not limited to. In addition to the foregoing, other system aspects are described in the claims, drawings, and text that form part of this disclosure.

The computer program product represents one or more aspects of the communeque directed towards the end user entity and the communeche aspect data associated with the particular source entity and one of the end user entities to conditionally obfuscate the commune associated with the source entity. One or more instructions for intercepting, in accordance with the conditional instructions above; And in response to intercepting the cocaine aspect data, sending to the end user entity secret indicator data that secretly indicates one or more aspects of the cocaine upon receipt by the end user entity, instead of sending a direct representation of the cocaine to the end user entity. It may include a signal-bearing medium for carrying one or more instructions for. In addition to the foregoing, other computer program product aspects are described in the claims, drawings, and text that form part of this disclosure.

A method for obfuscating a communeque directed to an end user entity and associated with a particular source entity by at least intercepting comonike aspect data directed to an end user entity representing one or more aspects of the commune according to one or more conditional instructions of the end user entity, Using one or more processors, the end user entity to present one or more aspects of the cocaine to the end user entity and to conditionally obfuscate the cocaine aspect data associated with the particular source entity and to coordinate the cocaine associated with the source entity. According to one or more conditional instructions of intercepting; And in response to intercepting the cocaine aspect data, sending to the end user entity secret indicator data that secretly indicates one or more aspects of the cocaine upon receipt by the end user entity, instead of sending a direct representation of the cocaine to the end user entity. It may include.

The foregoing summary is for illustrative purposes only and is not intended to be limiting in any way. 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.

1A and 1B show a high level block diagram of a network device 10 operating in a network environment.
2A and 2B illustrate the Corniche aspect data intercept module 102 of the network device 10 of FIG. 1B from another perspective.
FIG. 2C shows the secret indicator data transmission module 102 of the network device 10 of FIG. 1B from another perspective.
3 is a high level logic flow diagram of a process.
4A is a high level logic flow diagram of a process illustrating an alternative implementation of the communeike aspect data intercept operation 302 of FIG. 3.
FIG. 4B is a high level logic flow diagram of a process illustrating an alternative implementation of the communeike aspect data intercept operation 302 of FIG. 3.
4C is a high level logic flow diagram of a process illustrating an alternative implementation of the communeike aspect data intercept operation 302 of FIG. 3.
4D is a high level logic flow diagram of a process illustrating an alternative implementation of the communeike aspect data intercept operation 302 of FIG. 3.
4E is a high level logic flow diagram of a process illustrating an alternative implementation of the communeike aspect data intercept operation 302 of FIG. 3.
4F is a high level logic flow diagram of a process illustrating an alternative implementation of the communeike aspect data intercept operation 302 of FIG. 3.
4G is a high level logic flow diagram of a process illustrating an alternative implementation of the communeike aspect data intercept operation 302 of FIG. 3.
FIG. 5A is a high level logic flow diagram of a process illustrating an alternative implementation of the secret indicator data transfer operation 304 of FIG. 3.
FIG. 5B is a high level logic flow diagram of a process illustrating an alternative implementation of the secret indicator data transfer operation 304 of FIG. 3.
FIG. 5C is a high level logic flow diagram of a process illustrating an alternative implementation of the secret indicator data transfer operation 304 of FIG. 3.
FIG. 5D is a high level logic flow diagram of a process illustrating an alternative implementation of the secret indicator data transfer operation 304 of FIG. 3.
FIG. 5E is a high level logic flow diagram of a process illustrating an alternative implementation of the secret indicator data transfer operation 304 of FIG. 3.
FIG. 5F is a high level logic flow diagram of a process illustrating an alternative implementation of the secret indicator data transfer operation 304 of FIG. 3.
FIG. 5G is a high level logic flow diagram of a process illustrating an alternative implementation of the secret indicator data transfer operation 304 of FIG. 3.
6 is another high level logic flow diagram of another process.
FIG. 7 is a high level block diagram illustrating another implementation of the network device 10 of FIG. 1B.

The following detailed description is made with reference to the accompanying drawings, which form a part of this disclosure. Unless otherwise noted, like reference numerals in the drawings generally refer to like components. The illustrative embodiments described in the detailed description, drawings, and claims are not meant to be limiting. Other embodiments may be utilized or other changes may be made without departing from the spirit or scope of the disclosure.

Recently, the computing / communication industry has made remarkable technological advances and has gained enormous commercial popularity. As a result, those who choose to enjoy the fruit of technological advances in computing / communication benefit a lot. For example, with the rapid development of personal communication devices such as mobile phones, personal digital assistants (PDAs), smart phones, laptop computers, desktop computers, etc., users of these devices are now at a relatively low cost with other users 24 hours a day, seven days a week. You can stay connected for seven days. Such connections may include, for example, various communications such as phone calls, email, Voice over Internet Protocol (VoIP), text messages (eg, Short Message Service (SMS) or Multimedia Messaging Service (MMS)), Instant Messaging (IM), and the like. This can be done through the channel. Users of these technologies enjoy a lot of benefits, but unfortunately they have to deal with the whole new issues and issues that come with these new technologies.

For example, users of such personal communication devices (eg, cell phones, smart phones, laptops and desktop computers, etc.) encounter various privacy and security issues. One such issue that has arisen with users of personal communication devices is that communication (e.g., phone calls, VoIP, email, text messages, IMs, etc.) received through such personal communication devices may be the primary user of such devices (e.g., Often accessible by people other than the owner. As a result, highly sensitive communes (e.g., confidential personal or business communes) directed at key users of these devices and information pointing to the various aspects of such communes become accessible to others, even embarrassing even if they do not cause disaster. It is likely to lead to.

For example, there has been a large report recently that a famous professional athlete has caught extramarital affairs with his wife, and it is widely reported that she knew this when she found a voice message from her husband's government on her mobile phone. . The husband in this case (that is, a famous professional athlete) could not have erased, hidden or disguised the voice message from his government, so he had to suffer huge economic losses from the loss of huge public embarrassment and commercial advertising revenue.

Of course, the necessity for communication or confidentiality is not limited to personal situations, but may also be necessary in professional or professional situations. For example, when you are at work or in a different location (e.g., when you are in a meeting with a customer), you may be able to It may not be appropriate to receive.

According to various embodiments, one or more conditional terms provided by the end user entity provide coronike aspect data pointing to an end user entity (eg, end user and / or communication device) and pointing to one or more aspects of the communeike (eg, source identification). Based on the instructions, methods, systems, and computer program products are provided for obfuscating one or more aspects of a communeque, at least intercepting (eg, bypassing or withholding), associated with a particular source entity and towards an end user entity. In particular, the method, system, and computer program product may be useful for the communication of a communeke (eg, email, instant message (IM), text message, phone call, VoIP call, video message, etc.) associated with and directed to a particular source entity. In response to intercepting (e.g., not releasing) the Coquenice aspect data that points to one or more aspects according to one or more conditional instructions of the end-user entity, and intercepting the Coquenice aspect data, final (any) direct representation of the Coquenice is finalized. Instead of transmitting to the user entity, it may be designed to transmit to the end user entity secret indicator data that secretly points to one or more aspects of the commune upon receipt by the end user entity. As described in detail below, the method, system, and computer program product may be implemented in a network device that may include one or more network servers. For the purposes of this description, unless otherwise stated, the term “network server” may be interpreted broadly and used to designate, for example, routers, switches, telephone exchanges, and the like designed to facilitate the transmission / direction / routing / storage of the coquenic. It may be associated with a variety of network devices, including.

In some embodiments, the method, system, and computer program product are directed to a particular end user entity and associated with one or more associated cochlenick aspects (eg, email) associated with a particular source entity that the end user of the end user entity may wish to obfuscate. It may be particularly useful when there is information or data (hereinafter referred to as “communicator aspect data”) indicating text messages, phone calls, video messages, etc.). Such coquenic aspect data may, for example, indicate a telephone number or email address associated with a source for the coquenice, a destination telephone number or email address, a reception time stamp, or the like.

There are at least two scenarios in which such information (e.g., Cohenike aspect data) may be generated and / or propagated. The first scenario involves situations where the recipient's communication device (eg, end user) is offline or “out of signal range,” and therefore has “unsuccessful” or “missed” communication (eg missed phone call). Relevant specific information (e.g., Coquenice aspect data) may be generated (e.g., extracted from missed Cocaine) and maintained on the server for subsequent transmission to the communication device when the communication device returns to "online". This usually happens when you miss a phone call. When a communication device (e.g. a cell phone or smartphone) returns online or within signal range, the server will send information (e.g. in the form of comonike aspect data) indicating a communication missing in that communication device.

The second scenario, on the other hand, relates to a situation that occurs in a pull-type communication system (e.g., a system in which Coquenice is pulled rather than pushed to the end user's device). For example, in a full technology email system, email is typically stored on one or more network servers. By storing the email on one or more network servers, the email recipient can access the email from any computing device. In such a full type system, there may be a situation in which only certain optional information (e.g., Cohenike aspect data) is propagated to the communication device of the end user (e.g., the recipient). For example, in some cases, a list of received emails may be provided to an end user's communication device, which may include communeike aspect data indicating one or more aspects of the commune associated with a particular source entity.

In order to obfuscate commune associated with a particular source entity in one of the two scenarios described above, a method, system, and computer program product according to various embodiments may be used to prevent comonike aspect data from reaching the end user entity. It may be designed to display more than one aspect and intercept coronike aspect data directed to a particular end user entity, wherein the intercept of the coronike aspect data is one or more conditional instructions of the end user entity (e.g., one or more conditional of the end user of the end user entity). Instructions). As noted above, methods, systems, and computer program products according to various embodiments may, in response to intercepting Coquenice aspect data, upon receipt by an end user entity instead of sending any direct representation of the coquenice to the end user entity. It can be designed to send secret indicator data to the end user entity that secretly represents one or more aspects of the ekonikeke.

For the purposes of the description below, “communicate” refers to, for example, a visual text commune such as an email message, a text message (eg, a short message service “SMS” or a multimedia messaging service “MMS”), an instant message (IM), or the like. Reference to any one of a variety of electronic communication means, including audio communication such as telephone calls, VoIP calls, voice messages, video messages, and the like. On the other hand, a reference to “coquenice aspect data” may refer to any data or information that represents one or more aspects associated with the coquenice. In some cases, the Coquenice aspect data may be Cocone's header information (ie, header data), or may include or indicate at least Coco's header type data. For example, in some embodiments, such coquenic aspect data may include the name, phone number, or address (eg, email address, IP address, URL) of the sender or source for the coquenic, the subject of the coquenice, the time stamp of receipt, etc. Can be displayed. In some cases, the Coquenice aspect data may be provided separately in connection with the Coquenice, or may be in the form of header data or information that may be embedded or integrated into the Coquenice itself.

As described below, a “source entity” may refer to any entity associated with a communeike where the end user wishes to obfuscate an identity, for example. In some examples, the source entity may be a source or intermediate source for the commune. In some cases, the source entity may include a source user, which may be, for example, a human or robot user, and / or a source user device, such as a mobile phone, smart phone, laptop or desktop computer. In some cases, the source entity may be an organization such as a business or an account or a profit group. In some examples, the source entity can be a website.

An “end user” can be a human or robot user designated to receive one or more commune. In some cases where the end user is a robot user, the robot user may be a network device such as, for example, a network server for voice mail services, text messaging services, or web based application services. In some cases, the end user may receive one or more commune via a “communication device” (also referred to as a “receiving device”). The communication device may be any form of computing device designed to transmit / receive a communeike, including, for example, a mobile phone, smart phone, PDA, landline phone, laptop or desktop computer, tablet computer, workstation, and the like.

“Conditional instructions” refer to commands or instructions that cause one or more actions to be executed when one or more conditions are generated and / or detected, as described below. Thus, for the purposes of this description, conditional instructions specify a necessary (eg mandatory) condition that can trigger one or more actions to be achieved and / or executed to achieve a particular result (eg, obfuscate the reception of a communeike associated with a particular source entity). One or more actions to be performed to identify may be identified. For example, in some cases, the conditional indication may be directed to an end user entity (e.g., an end user and / or end user owned communication device) when presenting one or more aspects of the communeke determined that the comunique aspect data is associated with a particular source entity. Secret indicator that intercepts (eg, maintains or “holds” without sending) the Cochnicique aspect data that is transmitted, and secretly (eg indirectly) displays one or more aspects of the Cochnicike instead of sending any direct representation of the Cochnicike. It may be a command to transmit data.

The term “secret indicator data” may be transmitted, for example, to an end user's communication device, as described below, and upon communication by a communication device (eg, mobile phone, smartphone, PDA, laptop computer, etc.) It may refer to any form of data that causes the device to secretly display one or more aspects of the communeque associated with a particular source user. As described below, in some cases, the secret indicator data that may be sent to and received by an end user's communication device may be a simple “ping” with little content, or one or more aspects of one or more aspects of the commune. It may contain more content, including data indicating temporary tenentes (eg Latin for placeholder or substitute). A more detailed description related to the secret indicator data will be described later.

1A and 1B, which illustrate an exemplary environment 100 of a method, system, circuit, and computer program product according to various embodiments that may now be implemented in or by the network device 10, are described. Let's take a look. In particular, the methods, systems, circuits, and computer program products implemented by the network device 10 are directed towards the end user entity 30 (eg, towards the end user 32 of the end user entity 30). The source entity 20 represents one or more aspects of the communeke 52 pointing to the user entity 30 (eg, toward the end user 32) and associated with the particular source entity 20. In accordance with one or more conditional instructions 50 of the end user entity 30 (e.g., end user 32) to conditionally obfuscate the commune 52 associated with the e.g. And in response to intercepting the Coquenice aspect data 53, instead of sending a direct representation of Coquenice 52 to the end user entity 30 (eg, an end user). May be designed to transmit to the end user entity 30 secret indicator data 54 which secretly indicates one or more aspects of the commune 52 upon receipt by the communication device 34 of the entity 30. In some embodiments, network device 10 may be a network system located at a single network site or at multiple network sites as in the case of cloud computing. In various embodiments, network device 10 may include one or more network servers that include one or more telephone switches, one or more telephone exchanges, and / or one or more routers. In some embodiments, network device 10 may include multiple network components as in the case of cloud computing.

In some embodiments, network device 10 may be designed to facilitate communication between various entities. For example, in some cases, network device 10 may, for example, communicate with one or more communication networks 40 (eg, email, text message) between source entity 20 and end user entity 30 via one or more communication networks 40. , And visual text communication such as instant messages, or audio communication such as telephone calls, VoIP calls, voice messages, and video messages. Source entity 20 may be human or robotic source user 22 and / or source user device 24 (eg, laptop computer, desktop computer, workstation, smartphone, mobile phone, PDA, or other computing / communication device). It may include. In another aspect, source entity 20 may be a website or an organization, such as a business, social group, transaction / technical group, or interest group. In some cases, source entity 20 may include a global positioning system (GPS), which may be part of source user device 24.

Similarly, end user entity 30 may be a human or robot user and / or communication device 34 (eg, laptop computer, workstation, smartphone, PDA, desktop computer, mobile phone, etc.). ) May be included. In some cases, end user entity 30 may be, for example, a voice mail service, a text messaging service, a web based application service, or the like, which may be associated with end user 32.

As briefly described above, the network device 10 may be designed to facilitate the relaying of one or more commune 52 between the source entity 20 and the end user entity 30 via one or more communication networks 40. Can be. One or more communication networks 40 may include one or more local area networks (LANs), metropolitan area networks (MANs), wireless local area networks (WLANs), personal area networks (PANs), worldwide interoperability for microwave access (WIMAX), and PTSN (PTSN) It may include a Public Switched Telephone Network (GPRS), a General Packet Radio Service (GPRS) network, a cellular telephone network, a client / server network, a virtual private network (VPN), and the like.

Returning to the example environment 100 of FIGS. 1A and 1B, in various embodiments, the network device 10 may be configured to include an end user entity 30 (eg, an end user entity 30) via one or more communication networks 40. It may be designed to receive one or more conditional instructions 50 from the end user 32. The one or more conditional instructions 50 to be received may indicate a specific condition and / or a specific action that may be executed to obfuscate the cochnice 52 associated with the specific source entity 20 and directed to the end user entity 30. have. In some cases, one or more conditional instructions 50 may be requested from end user 32.

As further shown in FIGS. 1A and 1B, the network device 10 may also, in accordance with one or more conditional instructions 50, end user entity 30 (eg, end user 32 of end user entity 30). Can be designed to receive and intercept communeike aspect data 53 indicative of one or more aspects of the commune 52 associated with a particular source entity 20. In various implementations, the Cohenike aspect data 53 may be intercepted to prevent the Cokenike aspect data 53 from reaching the end user entity 30. In some cases, intercepting the Coeniket aspect data 53 may include at least temporarily maintaining the Coeniket aspect data 53 without releasing the Coeniket aspect data 53 to the end user entity 30. Intercepting the Coquenice aspect data 53 may further include bypassing the Coquenice aspect data 53 to a memory 140 (eg, volatile memory, non-volatile memory, cache memory, etc.). In some implementations, as will be described below, intercepting the Coquenice aspect data 53 is at least specified by one or more conditional instructions 50 of the end user entity 30 (eg, the end user 32), for example. At least one triggering event associated with the end user entity 30 (eg, the end user 32 owns the communication device 34 of the end user entity 30), and a specific third party Not in close proximity, it may be necessary to maintain (eg, hold) Cochlenick aspect data 53 without releasing until communication device 34 is in or out of one or more locations, and the like.

In some cases, the Cohenike aspect data 53 intercepted by the network device 10 may be provided by the source entity 20 associated with the Cokenike 52, or by another network device 14. . In some implementations, the Cokenike aspect data 53 may be embedded in or included in the Cokenike 52 itself, which may also be received by the network device 10. Thus, in some cases, the network device 10 may be designed to intercept the coronike aspect data 53 by receiving at least the coronike 52 and extracting the coronike aspect data 53 from the coronike 52. In such implementations, the Corniche aspect data 53 may be in the form of header data (eg, header information). Alternatively, the network device 10 may be designed to intercept the Cokenike aspect data 53 by receiving Cokenike aspect data 53 independently of Cokenike 52 or without receiving Cokenike 52. In other words, in this implementation, the Coquenice aspect data 53 may exist independently of the Coquenice 52, and may be obtained independently from other network devices 14, for example.

In various embodiments, the Cohenike aspect data 53 received by the network device 10 and directed to the end user entity 30 may have the Cohenike aspect data 53 end-user entity 30 in order to obfuscate the Coquenice 52. (E.g., hold without holding or releasing) to prevent reaching (e.g., communication device 34). In various embodiments, intercepting the Coquenice aspect data 53 may be in accordance with one or more conditional instructions 50 of the end user entity 30. In some cases, this may mean that the intercept of Coquenice's aspect data 52 may occur only if a particular condition specified by one or more conditional instructions 50 has occurred or has been detected. For example, in some cases the network device 10 may determine that the communication device 34 is not owned by the end user 32 or that a particular third party is in the vicinity of the communication device 34 or otherwise described below. Cochenike aspect data 53 may only be intercepted when conditions exist (eg, communication device 34 is in or outside one or more locations).

One way for the network device 10 to determine if such a condition (eg, a “triggering event”) is present is, for example, the end user entity 30 (eg, the communication device 34 of the end user entity 30). From the end user entity data 55 which can indicate various environmental conditions of the communication device 34. Examples of the types of data that may be included in the end user entity data 55 may include, for example, data verifying that the communication device 34 is owned by the end user 32. In some cases, such data may include, for example, password verification data or biometric verification (eg, digital image of a face, digital image of a fingerprint, digital voice) verifying that the end user 32 owns the communication device 34. Sensor data such as recording, etc.). Another form of data that may be included in the end user entity data 55 that may be provided to the network device 10 may be data indicating whether a particular third party is in close proximity to the communication device 34. Here, "nearby" means a third party sees a commune 52 provided within 3 feet, 5 feet, 8 feet, 10 feet, or other communication device 34 from the communication device 34; It may indicate that you are within range of what you can hear / detect. Other forms of data indicative of other forms of environmental conditions associated with end user entity 30 (eg, communication device 34) may be included with end user entity data 55 in various other embodiments.

Note that end user entity data 55 that may be received by network device 10 may be used by network device 10 in at least two ways. First use for end user entity data 55 may be that one or more triggering events (eg, communication device 34 are not owned by end user 32) that cause network device 10 to intercept cochlear aspect data 53. ) To detect the occurrence of A second use for the end user entity data 55 is another set of triggering events (e.g., the communication device 34 has an end point) that causes the network device 10 to release the communeike aspect data 53 to the end user entity 30. Verification of ownership of the user 32).

The network device 10 is not only designed to intercept the coquenic aspect data 53, but also secretly display one or more aspects of the coquenice 52 upon receipt by the end user entity 30 (eg, of the coquenic 52). Can be designed to transmit the secret indicator data 54 designed to indirectly indicate presence or reception, wherein the transmission of the secret indicator data 54 is in response to the intercept of the coronike aspect data 53 and any of the coronike 52. Instead of sending a direct representation of to the end user entity 30. The secret indicator data 54 that may be transmitted may be in accordance with one or more conditional instructions 50 of the end user entity 30 (eg, end user 32). As a result, as will be described later, the secret indicator data 54 may appear in various forms, including small amounts or large amounts of data. Also, as will be described in more detail below, the secret indicator data 54 that may be transmitted to the end user entity 30 when received by the communication device 34 of the end user entity 30 may be communicated by the communication device 34. One or more audio / visual / vibration secret indicators may be presented to secretly display (eg, indirectly display) one or more aspects of (52). In some cases, the secret indicator data 54 that may be transmitted may include one or more temporary substitutes (eg, Latin for placeholders or substitutes) for one or more aspects of the commune 52. For example, the secret indicator data 54 may include one or more “secret” code names for a particular source entity 20 associated with the commune 52. Alternatively or additionally, the secret indicator data 54 may include one or more code words and / or symbols to secretly indicate the presence or receipt of a commune 52 associated with the source entity 20.

Now consider the network device 10 of FIG. 1B in particular. The network device 10 may include various modules, submodules, and various other components, as shown. In some embodiments, network device 10 may be a single network device, such as a single server, which may be a single router, a single telephone switch, or other device located at a single network site. Alternatively, network device 10 may be a collection of network component devices including a set of multiple servers located at one network site or at multiple network sites as in the case of cloud computing. Thus, the network device 10 can be implemented at multiple network sites or at a single network site using a single server or multiple servers. Note that the network device 10 shown in FIG. 1B is illustrated as a single server for convenience of illustration and description. However, as noted above, network device 10 may be a network system that may be implemented using multiple network servers, such as in the case of cloud computing, for example.

As shown, the network device 10 may include at least the Cohenike aspect data intercept module 102 (which may further include one or more submodules as shown in FIGS. 2A and 2B) and the secret indicator data transmission module 104. (Which may further include one or more submodules as shown in FIG. 2C). As further shown, in some embodiments, the network device 10 further includes a conditional indication request module 105, which may further include a conditional indication receiving module 101 (conditional indication request sending module 106). May be included).

In summary, conditional instruction receiving module 101 may be configured to receive one or more conditional instructions 50 from end user entity 30 (eg, end user 32 of end user entity 30). On the other hand, the Coquenice aspect data intercept module 102 displays one or more aspects of the coquenice 52 that are directed to the end user entity 30 and also toward the end user entity 30 and are associated with a particular source entity 20. Can be configured to intercept the coquenice aspect data 53, wherein the intercept of coquenice aspect data 53 is in accordance with one or more conditional instructions 50 to conditionally obfuscate the coquenice 52 associated with the source entity 20. Can be done. The secret indicator data transmission module 104 may be configured to send the secret indicator data 54 to the end user entity 30 which secretly indicates one or more aspects of the commune 52 upon receipt by the end user entity 30. And the transmission of the secret indicator data 54 may be made in response to the intercept of the communeike aspect data 53, instead of sending (any and all) direct indications of the communeke 52 to the end user entity 30. have. More detailed descriptions related to the Cohenike aspect data intercept module 102, the secret indicator data transmission module 104, the conditional indication receiving module 101, and all submodules thereof are provided below for the operations and processes to be described in this disclosure. Will be.

In various embodiments, network device 10 may include a network interface 108 (eg, a network interface card or NIC) and / or memory 140. Although not shown, the network device 10 may also include other components such as one or more processors (eg, microprocessors) and one or more user interfaces. In various embodiments, the network device 10 including the Coquenice aspect data intercept module 102, the secret indicator data transmission module 104, and their submodules (as shown in FIGS. 2A, 2B, and 2C). The various modules included in may be implemented using hardware (eg, circuitry), software, firmware, or any combination thereof.

For example, in some embodiments, the Cohenike aspect data intercept module 102, the secret indicator data transmission module 104, and the conditional indication receiving module 101 (and submodules thereof) are, for example, application specific integrated circuits. That is, using hardware such as a specially designed circuit that includes an ASIC. Alternatively, the Cohenike aspect data intercept module 102, the secret indicator data transmission module 104, and the conditional indication receiving module 101 (and submodules thereof) may be one or more, as described below with respect to FIG. 6. A computer executed by a processor may be implemented using software in the form of readable instructions. In another embodiment, the Cohenike aspect data intercept module 102, the secret indicator data transmission module 104, and / or the conditional indication receiving module 101 (and submodules thereof) are, for example, a Cochenike aspect data intercept module ( 102, a combination of hardware and software, such as when the secret indicator data transmission module 104 and the conditional indication receiving module 101 (and submodules thereof) are implemented using a Field Programmable Gate Array (FPGA). Can be implemented. 1B illustrates a hardware implementation of the network device 10. That is, the Coquenice aspect data intercept module 102, the secret indicator data transmission module 104, and the conditional indication receiving module 101 shown in FIG. 1B may each be coupled together by, for example, a bus 110. It is shown to be implemented by circuitry used with 108 and memory 140.

Again, for the sake of illustration and understanding, note that FIG. 1B illustrates a single device embodiment of the network device 10 (eg, the network device 10 shown in FIG. 1B may be as numerous as in the case of cloud computing). Rather than being implemented by a server of a single server). However, one of ordinary skill in the art appreciates that the network device 10 can be implemented using multiple network component devices (eg, multiple servers) located at multiple network sites, as in the case of cloud computing. There will be.

In addition, while FIG. 1B illustrates only a hardware embodiment of the network device 10, a person of ordinary skill in the art receives the Coquenice aspect data intercept module 102, the secret indicator data transmission module 104, and conditional indication reception. Module 101 (and their submodules as shown in FIGS. 1B, 2A, 2B, and 2C) may also be implemented using software, firmware, or any combination of hardware, software, and firmware. Note that you will know. In addition, one or more modules of the network device 10 including the Coquenice aspect data intercept module 102, the secret indicator data transmission module 104, and the conditional indication receiving module 101 (and submodules thereof) may be cloud computing. It can be located on multiple network sites, as in the case of.

In various embodiments, network device 10 may include a memory 140 for storing various types of data. In such an embodiment, memory 140 may include one or more mass storage devices, read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), random access memory (RAM), Flash memory, synchronous random access memory (SRAM), dynamic random access memory (DRAM), cache memory, and / or other forms of memory devices. In some embodiments, memory 140 may be located at a single network site. Alternatively, memory 140 may be located at multiple network sites.

In various alternative embodiments, memory 140 may store various data. For example, in some embodiments, memory 140 may include one or more conditional instructions 50, one or more commune 52, and / or at least one of at least one commune 52 associated with a particular source entity 20. The Coquenice aspect data 53 which displays an aspect can be stored.

Referring now to FIGS. 2A and 2B, which illustrate a particular implementation of the communeike aspect data intercept module 102 of FIG. 1B. As shown, the Coquenice aspect data intercept module 102 may include one or more submodules in various alternative implementations. For example, in various implementations, the Coquenice aspect data intercept module 102 may be, as shown in FIG. 2A, a Coquenice receiving module 202 (coqueneque aspect data extraction module 203, visual Coquenice receiving module 204, and / or Or may further include an audio community reception module 205), a triggering event determination module 207 (password verification reception module 209, and / or biometric verification reception module 210). And may further include a proprietary verification module 208, a communications device location determination module 212, a communications device time determination module 213, and / or a third party proximity determination module 214). Cochenike aspect data retention module 206, and / or communication device location determination module 217, communication device time determination module 218, end user-owned determination module 219 (password verification determination module 221 and / or biometrics). Awareness May further comprise an end-user-owned verification module 220, which may include an attestation determination module 222, and / or an environmental condition determination module, which may further include a third party proximity determination module 223 216).

In addition, as shown in FIG. 2B, the Cohenike aspect data intercept module 102 may, alternatively or additionally, in various implementations, source entity representation determination module 225 (source entity association name determination module 226, source entity association address). Source module association determination module 224, which may further include a determination module 227, and / or a source entity association telephone number determination module 228) and / or a source determination module 229. End user entity association representation determination module 231 (also end user entity association address determination module 232, end user entity association telephone number determination module 233, and / or end user entity association name determination module 234). End user entity designation determination module 230, and / or source entity association subject determination module 235, which may further include a < RTI ID = 0.0 > As discussed above, each submodule of the Cohenike aspect data intercept module 102 may be hardware (eg, circuitry), software (eg, computer readable instructions that may be executed by one or more processors), firmware, or any thereof. It can be implemented using a combination. Detailed descriptions of the Coquenice aspect data intercept module 102 and sub-modules of the Coquenice aspect data intercept module 102 described above will be provided below with reference to the operations and processes described in this disclosure.

Referring now to FIG. 2C, which depicts a particular implementation of the secret indicator data transfer module 104 of FIG. 1B. As shown, the secret indicator data transfer module 104 may also include one or more submodules in various alternative embodiments. For example, in some implementations, the secret indicator data transfer module 104 may further include a temporary surrogate secret indicator data transfer module 240 (which may further include an alternate containing secret indicator data transfer module 241) and / or receive co-located lists. It may include a transmission module 242. Loom tenens are the singular form of loom tenentes. As described above, each submodule of the secret indicator data transfer module 104 may be hardware (eg, circuitry), software (eg, computer readable instructions executed by one or more processors), firmware, or any combination thereof. Can be implemented using Detailed descriptions of the submodules of the above-described secret indicator data transmission module 104 will be provided below with reference to the operations and processes to be described in the present disclosure.

A more detailed discussion relating to the network device 10 of FIG. 1B will be provided with reference to the operations and processes described in this disclosure. In particular, FIG. 3 is associated with a particular source entity by intercepting (bypassing and keeping in memory) communeike aspect data that represents one or more aspects of the communeque and is directed to (eg, being a destination or transmitted to) an end user entity and is associated with a particular end user entity. A flow diagram 300 is shown that illustrates an example operation for obfuscating a commune destined for a user according to one or more conditional instructions provided by an end user entity. In the following figures, including FIG. 3 and various flow chart examples, with reference to the example environment 100 shown in FIGS. 1A and 1B and described above, and / or (eg, as provided in FIGS. 2A, 2B, 2C, and 7) Discussion and description will be provided with reference to other examples and contexts. However, it should be noted that the flowcharts may be executed in a variety of other environments and contexts, and / or modified versions of FIGS. 1A, 1B, 2A, 2B, 2C, and 7. Also, while various flow diagrams are provided in the order shown, it should be noted that various operations may be performed in a different order than that shown, or may be performed concurrently.

In addition, various operations in FIG. 3 and the following figures may be shown in the form of a box-within-a-box. Such illustration may indicate that the operation of the inner box includes an optional embodiment of the operation shown in one or more outer boxes. However, it should be noted that the inner box operation may be considered an operation independent of any associated outer box, and may be performed in any order or concurrently for all other illustrated operations. In addition, these operations shown in FIG. 3 and other operations described in this disclosure may be performed by at least one of a machine, an article of manufacture, or a composition of matter.

In any event, after the start operation, the flowchart 300 of FIG. 3 displays one or more aspects of the communeque directed to the end user entity and toward the end user entity and correlating the source entity with the communeike aspect data associated with the particular source entity. In order to intercept according to one or more conditional indications of the end-user entity for conditional obfuscation of the associated communeike, it may move to the communeike aspect data intercept operation 302. For example, as shown, the Cohenike aspect data intercept module 102 of the network device 10 of the example environment 100 of FIGS. 1A and 1B is directed (eg, sent or transmitted) to the end user entity 30. Display one or more aspects of the cocaine 52 directed to the end user entity 30 (e.g., the telephone number or address of the source for cocaine 52, the subject for the cocaine 52, if received, etc.) It is possible to intercept (eg, bypass, capture, and / or maintain) Cochlenick aspect data 53 associated with a particular source entity 20, wherein the intercept of Cochlenick aspect data 53 is associated with the source entity 20. According to one or more conditional instructions 50 of the end user entity 30 (eg, one or more conditional instructions of the end user 32 of the end user entity 30) to conditionally obfuscate the commune 52. You can break them. In some embodiments, the presence of the commune 52 associated with the source entity 20 by intercepting the communeike aspect data 53 and preventing the communeche aspect data 53 from reaching the end user entity 30 and And / or the association between the commune 52 and the particular source entity 20 may be obfuscated.

In addition to the Coquenice aspect data intercept operation 302, the flowchart 300 is in response to the intercept of Coquenice aspect data, as shown further in FIG. 3, instead of sending a direct representation of the Coquenice to the end user entity. A secret indicator data transfer operation 304 may be further included to transmit to the end user entity secret indicator data that secretly indicates one or more aspects of the commune upon receipt by. For example, the secret indicator data transmission module 104 of the network device 10 of FIG. 1B responds to the end user entity 30, in response to the intercept of the communeike aspect data 53, to provide a direct indication of the commune 52 to the end user entity. Instead of transmitting to 30, it secretly displays one or more aspects of the cocaine 52 upon receipt by the end user entity 30 (eg, reception of the cocaine 52 associated with a particular source entity 20). The secret indicator data 54 may be transmitted. As briefly described above and further described in this disclosure, the secret indicator data 54 to be transmitted is received by the end user entity 30 (eg, by the communication device 34 of the end user entity 30). When received, one or more aspects of the commune 52 can be transmitted in various forms that can be secretly indicated. Thus, in some respects, the content that the secret indicator data 54 includes may not be as relevant as how the communication device 34 of the end user entity 30 behaves in response to receiving the secret indicator data 54. That is, rather than defining the secret indicator data 54 as its content, the communication device 34 of the end user entity 30 reacts to the secret indicator data 54 when it receives the secret indicator data 54. It may be more appropriate to define the secret indicator data 54 as shown.

As discussed below, the Coquenice aspect data intercept operation 302 and the secret indicator data transfer operation 304 of FIG. 3 may be implemented in various ways in various alternative implementations. For example, FIGS. 4A, 4B, 4C, 4D, 4E, 4F, and 4G illustrate some alternative ways in which the Coquenice aspect data intercept operation 302 of FIG. 3 can be implemented in various alternative implementations. For example, in various implementations, the Coquenice aspect data intercept operation 302 of FIG. 3 may include an operation 402 for intercepting Coquenice aspect data at the network device shown in FIG. 4A. For example, the Cohenike aspect data intercept module 102 of the network device 10 of FIG. 1B may intercept Cokenike aspect data at the network device 10 (eg, one or multiple servers located at a single or multiple network sites). have.

In some implementations, operation 402 can further include operation 403 for intercepting Corniche aspect data at the network device, where the network device can be located at one or more network sites as further shown in FIG. 4A. have. For example, the Cokenike aspect data intercept module 102 of the network device 10 of FIG. 1B may intercept Cochnicike aspect data 53 at the network device 10, where the network device 10 is located at one or more network sites. (Eg, for cloud computing, network device 10 may include multiple servers located at multiple sites).

As further shown in FIG. 4A, operation 403 may further include one or more additional operations. For example, in some implementations, operation 403 can include an operation 404 for intercepting Corniche aspect data at a network device, where the network device is one located at one or more network sites as further shown in FIG. 4A. It may include more than one network server. For example, the Cokenike aspect data intercept module 102 of the network device 10 of FIG. 1B may intercept Cochnicike aspect data 53 at the network device 10, where the network device 10 is located at one or more network sites. It may include one or more network servers.

Next, operation 404 may further include an operation 405 for intercepting Corniche aspect data at the network device, wherein the network device may include at least one router as further shown in FIG. 4A. For example, the Cokenike aspect data intercept module 102 of the network device 10 of FIG. 1B may intercept Cochnicike aspect data 53 at the network device 10, and the network device 10 includes at least one router. can do.

In the same or other implementations, operation 404 can include operation 406 for intercepting Corniche aspect data at the network device, the network device including at least a telephone switch or telephone switch as further shown in FIG. 4A. can do. For example, the Cohenike aspect data intercept module 102 of the network device 10 of FIG. 1B may intercept Cokenike aspect data 53 at the network device 10, the network device 10 being at least a telephone switch or telephone exchange. It may include.

In some cases, the Cohenike aspect data intercept operation 302 of FIG. 3 is an operation 407 for intercepting Cokenike aspect data by intercepting Cokenike aspect data received via one or more communication networks as further shown in FIG. 4A. ) May be included. For example, the Corniche aspect data intercept module 102 of the network device 10 of FIG. 1B may include one or more communication networks 40 (eg, WLAN, WMAN, WiMAX, PTSN, cellular networks, client / server networks, VPNs, and / or the like). Or the co-Nike aspect data 53 received via one or more of other types of networks).

In some cases, the Corniche aspect data 53 intercepted via the Corniche aspect data intercept operation 302 may be included or embedded in the Corniche 52. For example, in some implementations, the Coquenice aspect data intercept operation 302 can include an operation 408 for intercepting Coquenice aspect data by receiving a Coquenice, the Coquenice aspect data as further shown in FIG. 4A. It may include. For example, the Cohenike aspect data intercept module 102, which includes the Cokenike receiving module 202 (see FIG. 2A) of the network device 10 of FIG. 1B, may include a Cokenike receiving module 202 (eg, header data or telephone calls). Coquenice aspect data by having it receive a cocaine 52 (eg, email, text message, instant message, phone call, voice message, video message, etc.) that includes coquenic aspect data 53, which may be data embedded in the tone. (53) can be intercepted. In other implementations, it is noted that communeike aspect data 53 may not be included in communeike 52.

As further shown in FIG. 4A, operation 408 may include, in various alternative implementations, an operation 409 for receiving a communeike, for example, by receiving a communeike that includes the comoniket aspect data in the form of header data. The operation may further include. For example, the communeike receiving module 202 of the network device 10 of FIG. 1B may receive the communeke 52 by receiving the communeke 52 including the comoniket aspect data 53 in the form of header data.

In the same or other implementations, operation 408 may include an operation 410 for receiving a cocaine by receiving a cocaine that includes cocaine aspect data embedded in the coquette's tones as further shown in FIG. 4A. For example, the coquenic receive module 202 of the network device 10 of FIG. 1B includes coquenice aspect data 53 embedded in a coping tone (such as a beep of a missed or unsuccessful telephone call). By receiving the commune 52, the commune 52 can be received.

In the same or other implementations, operation 408 may include an operation 411 for intercepting the Corniche aspect data by extracting the Corniche aspect data from the Corniche as further shown in FIG. 4A. For example, the Cohenike aspect data intercept module 102, which includes the Cohenike aspect data extraction module 203 (see FIG. 2A) of the network device 10 of FIG. The communeike 52 can be received by extracting the communeike aspect data 53.

In the same or other implementations, operation 408 may include an operation 412 for receiving a co-working by receiving a visual co-working as further shown in FIG. 4A. For example, the co-communication receiving module 202, which includes the visual cocaine receiving module 204 (see FIG. 2A) of the network device 10 of FIG. Can receive a commune 52 by receiving a text message, an instant message, or a visual text message such as an IM.

In the same or other implementations, operation 408 may include an operation 413 for receiving the co-working by receiving the audio co-working as further shown in FIG. 4A. For example, a co-working reception module 202 including an audio co-working reception module 205 (see FIG. 2A) of the network device 10 of FIG. Missed or unsuccessful phone calls, including VoIP calls, video messages, voice messages or other audio communications) may be received to receive the commune 52.

In various implementations, the Cohenike aspect data intercept operation 302 of FIG. 3 for intercepting Cokenike aspect data 53 may be performed by the Cohenike aspect data 53 on the end user entity 30 as shown in FIGS. 4B and 4C. It may include at least temporarily holding the Coquenice aspect data 53 to prevent reaching. In some implementations, for example, the Coquenice aspect data intercept operation 302 is an operation 414 for intercepting Coquenice aspect data by at least temporarily maintaining the Coquenice aspect data in order to prevent Cochenice aspect data from reaching the end user entity. It may further comprise, the maintenance of the aspect data of the communeike may be made according to one or more conditional instructions as shown in Figure 4b. For example, the Cohenike aspect data intercept module 102, which includes the Cohenike aspect data retention module 206 (see FIG. 2A) of the network device 10 of FIG. 1B, may be configured to have the Cohenike aspect data 53 sent to the end user entity 30. In order to prevent reaching, the Cohenike aspect data maintenance module 206 maintains Cohenike aspect data 53 at least temporarily (e.g., temporarily until at least one triggering event occurrence is detected, as described below). By maintaining without holding or releasing) the cocaine aspect data 53 can be intercepted, and the cocaine aspect data 53 can be maintained in accordance with one or more conditional instructions 50.

As further shown in FIG. 4B, operation 414 may further include an operation 415 for maintaining the Cochlenick aspect data in memory at least temporarily without releasing the Cochnice aspect data. For example, the communeike aspect data retention module 206 of the network device 10 of FIG. Nonvolatile memory, cache memory, etc.).

In various implementations, operation 415 for at least temporarily retaining the cochnice aspect data in memory without releasing the cochlear aspect data may further include one or more additional operations. For example, in some implementations, operation 415 may be performed without release of the cocaine aspect data to the end user entity until the occurrence of at least one triggering event associated with at least the end user entity is determined, as further illustrated in FIG. 4B. Operation 416 to maintain the memory in the memory. For example, the Cohenike aspect data retention module 206 comprising the triggering event determination module 207 (see FIG. 2A) of the network device 10 of FIG. 1B may include at least the triggering event determination module 207, for example, an end user entity ( Cokenike aspect data 53 may be maintained in memory 140 without releasing (e.g., transmitting) the cochnice aspect data 53 to the end user entity 30 until a decision is made to generate one or more triggering events associated with 30). .

Next, operation 416 may, in various implementations, memory the Cohenike aspect data without releasing the Cohenike aspect data to the end user entity until at least verification has been obtained that the end user of the end user entity owns the communication device of the end user entity. The method may further include an operation 417 to maintain. For example, the Cohenike aspect data maintenance module 206 comprising the end user proprietary verification module 208 (see FIG. 2A) of the network device 10 of FIG. 1B may be configured such that at least the end user proprietary verification module 208 is configured as an end user entity. The end user 32 of 30 is connected to the communication device 34 of the end user entity 30 (eg, a mobile phone, smartphone, PDA, laptop or desktop computer, workstation, or other form of communication / computing device). It is possible to keep the communeike aspect data 53 in the memory 140 without releasing the communeike aspect data 53 to the end user entity 30 until a verification is obtained that it owns.

In some cases, operation 417 may be performed without release of the Cohenike aspect data to the end user entity until at least a password verification is provided that verifies that the end user owns the communication device, as further illustrated in FIG. 4B. Operation 418 may be further included to maintain the data in memory. For example, the Cohenike aspect data retention module 206 including the password verification receiving module 209 (see FIG. 2A) of the network device 10 of FIG. 1B may include at least the password verification receiving module 209. Coeniket aspect data 53 may be maintained in memory 140 without releasing cochlear aspect data 53 to the end user entity 30 until it receives a password verification that verifies that it owns the communication device 34. have.

In the same or other implementations, operation 417 also does not release the Cohenike aspect data to the end user entity until at least receiving biometric verification that verifies that the end user owns the communication device, as further shown in FIG. 4B. And maintaining 419 the Corniche aspect data in memory. For example, the Cohenike aspect data maintenance module 206 including the biometric verification receiving module 210 (see FIG. 2A) of the network device 10 of FIG. 1B may include at least the biometric verification receiving module 210. The Cohenike aspect data 53 is sent to the end user entity until it receives a biometric verification (eg, digital image of a face, digital voice recording, retinal scan results, etc.) that verifies that the device owns the communication device 34. It is possible to keep the communeike aspect data 53 in the memory 140 without releasing it to 30).

In some cases, operation 419 may receive at least one of retinal scan verification, face verification, voice verification, or fingerprint verification to verify that at least the end user owns the communication device as further shown in FIG. 4B. The method may further include an operation 420 for maintaining the communeike aspect data in memory without releasing it to the end user entity until. For example, the Cohenike aspect data retention module 206 including the biometric verification receiving module 210 of the network device 10 of FIG. 1B may include at least the biometric verification receiving module 210 of the end user 32. (34) retinal scan verification (e.g., digitized image of the retina) to verify that it owns, facial verification (e.g., digitized image of the face), voice verification (e.g., digital voice recording), or fingerprint verification (e.g., The cochlear aspect data 53 may be maintained in the memory 140 without release of the cochlear aspect data 53 to the end user entity 30 until at least one of the digital image of the fingerprint is received. That is, it receives a digitized image of the retina, a digitized image of the face, a digitized voice recording, or a digitized image of the fingerprint and receives appropriate software (e.g., retinal recognition application, face recognition application, voice recognition application, or fingerprint recognition application). By using, for example, verification can be made that the end user 32 owns the communication device 10.

In some implementations, as shown in FIG. 4C, an operation for maintaining the cochleque aspect data in memory without releasing the cochlear aspect data to the end user entity until at least one occurrence of one or more triggering events associated with the end user entity is determined ( 416 operates 421 to maintain the co-Nike aspect data in memory without releasing the Co-Nike aspect data to the end-user entity until at least it determines that the communication device of the end-user entity is at one or more locations specified by one or more conditional instructions. ) May be included. For example, the Cohenike aspect data retention module 206 comprising the communication device positioning module 212 (see FIG. 2A) of the network device 10 of FIG. End user using the Cohenike aspect data 53 until the communication device 34 (e.g., a mobile device with a GPS, such as a smartphone) is at one or more locations specified by one or more conditional instructions 50. It is possible to keep the communeike aspect data 53 in the memory 140 without releasing it to the entity 30. In such implementation, communication device location determination module 212 may determine the location of communication device 34 based on end user entity data 55 (eg, GPS data) provided by communication device 34.

In the same or another implementation, operation 416 may transmit the Cohenike aspect data to the end user entity until at least the communication device of the end user entity determines that it is outside one or more locations specified by one or more conditional instructions, as shown in FIG. 4C. Alternatively or additionally, an operation 422 may be included to maintain the Corniche aspect data in memory without releasing. For example, the Cohenike aspect data retention module 206, which includes the communication device positioning module 212 (see FIG. 2A) of the network device 10 of FIG. 1B, is configured such that at least the communication device positioning module 212 is an end user entity. End user entity until the communication device 34 of 30 determines that it is specified by one or more conditional instructions 50 and outside the one or more locations determined by the communication device positioning module 212. It is possible to hold the communeike aspect data 53 in the memory 140 without releasing it to 30.

In the same or another implementation, operation 416 may be performed until the communication device of the end user entity determines that at least one communication device of the end user entity is at one or more specific time points or time intervals specified by one or more conditional instructions. May alternatively or additionally include an operation 423 for maintaining the Cohenike aspect data in memory without releasing it to the end user entity. For example, the Cohenike aspect data retention module 206 comprising the communication device time determination module 213 (see FIG. 2A) of the network device 10 of FIG. 1B may include at least a communication device time determination module 213. That communication device 34 of 30 is at one or more specific time points or time intervals specified by one or more conditional instructions 50 (e.g., to end user entity data 55 provided by end user entity 30). Basis may be maintained in the memory 140 without release of the cocaine aspect data 53 to the end user entity 30 until a determination is made.

In the same or other implementations, operation 416 may be performed until the co-Nike aspect data has been determined to determine that the one or more third parties specified by the at least one or more conditional instructions are not in close proximity to the end user entity's communication device. May alternatively or additionally include an operation 424 for maintaining the Cohenike aspect data in memory without releasing to the end user entity. For example, the Cohenike aspect data retention module 206 comprising a third party proximity determination module 214 (see FIG. 2A) of the network device 10 of FIG. 1B includes at least one third party proximity determination module 214. Release the Cohenike aspect data 53 to the end user entity 30 until one or more third parties specified by the above conditional instructions 50 determine that they are not in the vicinity of the communication device 34 of the end user entity 30. Instead, the communeike aspect data 53 can be held in the memory 140.

Intercepting the Cohenike aspect data 53 in the Cohenike aspect data intercept operation 302 of FIG. 3 may be in response to one or more environmental conditions of the end user entity 30. For example, in various implementations, the Cohenike aspect data intercept operation 302 of FIG. 3 may be applied to one or more conditional indications by intercepting Cohenike aspect data as a function of one or more environmental conditions of the communication device of the end user entity as shown in FIG. 4D. May include an operation 425 to intercept the Corniche aspect data. For example, the Cohenike aspect data intercept module 102, which includes the environmental condition determination module 216 (see FIG. 2A) of the network device 10 of FIG. 1B, may be configured to include the communication device 34 of the end user entity 30. For example, do not release Cochnicque aspect data 53 as a function of one or more environmental conditions, as determined by environmental condition determination module 216, until an intercept (eg, at least detect triggering event occurrence associated with end user entity 30) is detected. ), It is possible to intercept communeike aspect data 53 according to one or more conditional instructions 50.

As further depicted in FIG. 4D, in various implementations, operation 425 is also an operation 426 for intercepting Corniche aspect data as a function of one or more environmental conditions indicated by end user entity data provided by the communication device. ) May be included. For example, the Cohenike aspect data intercept module 102 comprising the environmental condition determination module 216 of the network device 10 of FIG. 1B is determined by the environmental condition determination module 216 and provided by the communication device 34. End user entity data 55 (e.g., to one or more sensors, including data or image data, audio data, or other forms of data input by the end user 32, such as through a microblog or personal care application). The Cohenike aspect data 53 may be intercepted as a function of one or more environmental conditions (eg, a third party is present or absent in the vicinity of the communication device 34) indicated by the data provided by the device.

In the same or other implementations, operation 425 may include an operation 427 for intercepting Corniche aspect data as a function of the location of the communication device specified by one or more conditional instructions as further shown in FIG. 4D. . For example, the Cohenike aspect data intercept module 102 that includes the communication device positioning module 217 (see FIG. 2A) of the network device 10 of FIG. 1B may be a communication device specified by one or more conditional instructions 50. As a function of the position of 34, the Cohenike aspect data 53 may be intercepted (eg, held), and the position of the communication device 34 may be determined by the communication device positioning module 217. Note that in FIG. 2A the communication device positioning module 217 and the communication device positioning module 212 perform essentially the same function. Thus, in some implementations, they can be the same module.

Next, operation 427 further includes an operation 428 for intercepting Corniche aspect data in response to determining that the communication device is at one or more specific locations specified by one or more conditional instructions, as further shown in FIG. 4D. can do. For example, the Cohenike aspect data intercept module 102, which includes the communication device positioning module 217 of the network device 10 of FIG. 1B, may be configured such that the communication device positioning module 217 is one or more conditional units. Intercept (e.g., determine) the Cohenike aspect data 53 in response to determining that it is at one or more specific locations specified by the indication 50 (e.g., based on GPS data provided through the end user entity data 55). Withhold).

In the same or other implementations, the operation 425 for intercepting Corniche aspect data as a function of one or more environmental conditions of the communication device of the end user entity is specified by one or more conditional instructions as further shown in FIG. 4D. And operation 429 for intercepting Corniche aspect data as a function of time relative to. For example, the Cohenike aspect data intercept module 102 that includes the communication device time determination module 218 (see FIG. 2A) of the network device 10 of FIG. 1B may be a communication device specified by one or more conditional instructions 50. It is possible to intercept (e.g., hold) the Coquenice aspect data 53 as a function of the time associated with 34, and the time associated with the communications device 34 is the end user entity data 55 provided by the communications device 34. May be determined by the communication device time determination module 218. Note that the communication device time determination module 218 and the communication device time determination module 213 of FIG. 2A may perform essentially the same function, and thus may be the same module in various alternative implementations.

In some cases, operation 429 may be used to intercept, for example, the Cohenike aspect data for the communication device at one or more specific times of the day specified by one or more conditional instructions, as further shown in FIG. 4D. 430). For example, the Cohenike aspect data intercept module 102, which includes the communication device time determination module 218 of the network device 10 of FIG. 1B, may be specified by one or more conditional instructions 50 for the communication device 34. At one or more specific times of the day (e.g., between 6 pm and 8 am), the Cochenike aspect data 53 may be intercepted (e.g., held), and the time associated with the communication device 34 is determined by the communication device time determination module. 218, for example, may be determined based on end user entity data 55 provided by communication device 34.

In the same or other implementations, operation 429 is an operation for intercepting Coquenice aspect data at one or more specific times of a calendar year specified by one or more conditional instructions for a communication device as further shown in FIG. 4D. 431 may be included. For example, the Cohenike aspect data intercept module 102, which includes the communication device time determination module 218 of the network device 10 of FIG. 1B, may be specified by one or more conditional instructions 50 for the communication device 34. At one or more specific times of the calendar year (eg, on Christmas Day), the Cohenike aspect data 53 may be intercepted (eg, held), and the time associated with the communication device 34 may be determined, for example, by the communication device time determination module 218. It may be determined based on the end user entity data 55 provided by the communication device 34.

In the same or another implementation, an operation 425 for intercepting Cochinike aspect data as a function of one or more environmental conditions of an end user entity's communication device, as shown in FIG. 4E, causes the communication device to communicate to the end user of the end user entity. By intercepting the Coquenice aspect data in response to determining that it is not owned by the user, it may include an operation 432 for intercepting the Coquenice aspect data in accordance with one or more conditional instructions. For example, the Cohenike aspect data intercept module 102 that includes the end user owned determination module 219 of the network device 10 of FIG. 1B (see FIG. 2A) may be used by the end user owned determination module 219. Based on at least some of the end user entity data 55 provided by 34, the communication device 34 is in response to determining that it is not owned by the end user 32 of the end user entity 30. ) May intercept (e.g., hold) the Cohenike aspect data 53 in accordance with one or more conditional instructions 50.

Next, in some cases, operation 432 may include an operation 433 for intercepting Corniche aspect data at least in part in response to a determination of the absence of verification that the end user owns the communication device, as shown in FIG. 4E. Can be. For example, the Cohenike aspect data intercept module 102 that includes the end user proprietary verification module 220 (see FIG. 2A) of the network device 10 of FIG. 1B may be configured to include an end user 32. ) May intercept (eg, suspend) Coquenice aspect data 53 at least partially in response to determining the absence of verification that the device owns communication device 34. Note that in various alternative implementations, the end-user-owned verification module 220 and the end-user-owned verification module 208 of FIG. 2A may perform essentially the same function and thus be the same module.

As further shown in FIG. 4E, operation 433 may further include one or more additional operations in various alternative implementations. For example, in some implementations, the operation 433 further includes an operation 434 for intercepting Corniche aspect data in response to at least in part a determination of the absence of password verification that the end user owns the communication device as shown in FIG. 4E. can do. For example, the Cohenike aspect data intercept module 102 including the password verification determination module 221 (see FIG. 2A) of the network device 10 of FIG. 1B may be configured by a password verification determination module 221. ) May intercept (e.g., hold) the Cohenike aspect data 53 at least partially in response to determining the absence of password verification. Note that in some implementations, the password verification determination module 221 and the password verification reception module 209 of FIG. 2A may perform essentially the same function, and thus may be the same module.

In the same or another implementation, operation 433 is an operation 435 for intercepting Cochnicique aspect data at least partially in response to determining absence of biometric verification that the end user owns the communication device as further shown in FIG. 4E. It may include. For example, the Cohenike aspect data intercept module 102 that includes the biometric verification determination module 222 (see FIG. 2A) of the network device 10 of FIG. 1B may include an end user 32. ) May intercept (eg, suspend) Coquenice aspect data 53 at least partially in response to determining the absence of biometric verification that the device owns communication device 34. Note that in some implementations, the biometric verification determination module 222 and the biometric verification receiving module 210 of FIG. 2A may perform similar functions and thus may be the same module.

In some cases, operation 435 is at least partially in determining the absence of at least one of retinal scan verification, facial verification, voice verification, or fingerprint verification that the end user owns the communication device, as further shown in FIG. 4E. In response, the method may further include an operation 436 for intercepting the Coquenice aspect data. For example, the Cohenike aspect data intercept module 102 including the biometric verification determination module 222 of the network device 10 of FIG. 1B may include a biometric verification determination module 222. 34) may intercept (e.g., hold) Cochlenick aspect data 53 at least partially in response to determining the absence of at least one of retinal scan verification, facial verification, voice verification, or fingerprint verification.

In the same or other implementations, the operation 425 for intercepting Coquenice aspect data as a function of one or more environmental conditions of the communication device of the end user entity is specified by one or more conditional instructions, as further shown in FIG. 4E. And intercepting the Coquenice aspect data in accordance with one or more conditional instructions, at least in part in response to determining that the one or more third parties are in close proximity to the communication device. For example, the Cohenike aspect data intercept module 102 that includes the third party proximity determination module 223 (see FIG. 2A) of the network device 10 of FIG. 1B may include one or more third party proximity determination modules 223. One or more conditional indications by intercepting Cochlenick aspect data 53 at least partially in response to determining that the one or more third parties specified (eg, identified) by the conditional indication 50 are in the vicinity of the communication device 34. According to (50) it is possible to intercept (e.g., hold) the Coquenice aspect data 53. In various implementations, one or more specified third parties are provided by one or more third parties within 3 feet, within 5 feet, within 8 feet, within 10 feet, or through other communication device 34 from the communication device 34. It may be determined to be within “near proximity” of the communication device 34 when the commune 52 is within a range that one or more third parties can see / hear / sensing. Note that in some implementations, the third party proximity determination module 223 and the third party proximity determination module 214 of FIG. 2A may perform essentially the same function and thus may be the same module.

In various implementations, the Cokenike aspect data intercept operation 302 of FIG. 3 may only be executed when a determination is made that Cokenike 52 is associated with the source entity 20. For example, in some implementations, the Cohenike aspect data intercept operation 302 is performed by intercepting Cochenike aspect data at least in part in response to a determination that Cokenike aspect data includes data that associates the Cokenike with a source entity as shown in FIG. 4F. And an operation 438 for intercepting the Coquenice aspect data in accordance with the conditional instructions above. For example, the Cohenike aspect data intercept module 102 that includes the source entity association determination module 224 (see FIG. 2B) of the network device 10 of FIG. 1B may be configured by the source entity association determination module 224. In accordance with one or more conditional instructions 50 in accordance with one or more conditional instructions 50 by intercepting the Coquenice aspect data 53 at least partially in response to determining that 53 includes data that associates the Coquenice 52 with the source entity 20. ) Can be intercepted (for example, pending).

As further shown in FIG. 4F, in various alternative implementations, operation 438 may include one or more additional operations. For example, in some implementations, operation 438 is 439 for intercepting the Kokenike aspect data in response to at least in part a determination that the Kokenike aspect data includes header data that associates the source entity with the Kokenike. ) May be included. For example, the Cohenike aspect data intercept module 102 that includes the source entity association determination module 224 of the network device 10 of FIG. 1B may be configured such that the source entity association determination module 224 has the Cohenike aspect data 53 added to the source entity. Header data (e.g., message header information indicating a specific aspect of the cocaine 52, such as the address or telephone number of the source for the cocaine 52 and the subject, if present) that associates (20) with cocaine (52) Intercepting (eg, withholding) the Cohenike aspect data 53 may be at least partially in response to determining to include it.

In the same or other implementations, operation 338 may be performed in accordance with one or more conditional instructions by intercepting the Cokenike aspect data at least partially in response to determining that the Cokenike aspect data includes one or more representations of the source entity, as further shown in FIG. 4F. It may additionally or alternatively include an operation 440 for intercepting Coquenice aspect data. For example, the Cohenike aspect data intercept module 102, which includes the source entity representation determination module 225 (see FIGS. 2A and B) of the network device 10 of FIG. 1B, has the source entity representation determination module 225 co-located aspect. At least partly in determining that data 53 includes one or more representations of source entity 20 (eg, one or more identifiers such as, for example, one or more names, email addresses, IP addresses, telephone numbers, and / or other identifiers). In response to this, the Coquenice aspect data 53 can be intercepted (eg, suspended) according to one or more conditional instructions 50.

In some cases, operation 440 may be applied to one or more conditional indications by intercepting the Cokenike aspect data at least partially in response to determining that Cokenike aspect data includes at least one name associated with the source entity, as further illustrated in FIG. 4F. Accordingly, may comprise an operation 441 for intercepting the Coquenice aspect data. For example, the Cohenike aspect data intercept module 102, which includes the source entity association name determination module 226 (see FIG. 2B) of the network device 10 of FIG. 1B, may be configured by the source entity association name determination module 226. In accordance with one or more conditional instructions 50 by intercepting Cochnicque aspect data 53 at least partially in response to determining that data 53 includes at least one name (eg, a user name) associated with source entity 20. Cochenike aspect data 53 may be intercepted (eg, pending).

In the same or other implementations, operation 440 may include one or more conditional indications by intercepting the Kokenike aspect data at least partially in response to determining that the Kokenike aspect data includes at least one address associated with the source entity, as further illustrated in FIG. 4F. And an operation 442 for intercepting Corniche aspect data. For example, the Cohenike aspect data intercept module 102 that includes the source entity association address determination module 227 (see FIG. 2B) of the network device 10 of FIG. One or more predicates by intercepting Cochlenick aspect data 53 in response at least in part to determining that data 53 includes at least one address (eg, email address, IP address, or URL) associated with source entity 20. The instruction 50 may intercept (eg, hold) the Coquenice aspect data 53.

In the same or other implementations, operation 440 may include one or more conditional portions by intercepting the Coquenice aspect data in response to at least in part a determination that the Coconutian aspect data includes at least one phone number associated with the source entity, as further shown in FIG. 4F. And act 443 to intercept the Corniche aspect data in accordance with the instructions. For example, the Cohenike aspect data intercept module 102 that includes the source entity associated telephone number determination module 228 (see FIG. 2B) of the network device 10 of FIG. 1B may be configured to include a source entity associated telephone number determination module 228. In accordance with one or more conditional instructions 50 by intercepting the coquenic aspect data 53 at least partially in response to determining that the coquenic aspect data 53 includes at least one phone number associated with the source entity 20. (53) may intercept (eg, hold).

In some implementations, the operation 438 for intercepting the Cornishike aspect data in accordance with one or more conditional instructions by intercepting the Corkenike aspect data at least partially in response to determining that the Corkenike aspect data includes data that associates the Corkenike with the source entity. As shown in FIG. 4F, it may include an operation 444 for intercepting Corniche aspect data at least partially in response to determining that the source entity was a source for the Corniche. For example, the Cohenike aspect data intercept module 102 that includes the source determination module 229 (see FIG. 2B) of the network device 10 of FIG. 53 may intercept (e.g., hold) the Cohenike aspect data 53 at least partially in response to determining that it was a source (e.g., caller or caller).

In some cases, the Coquenice aspect data intercept operation 302 of FIG. 3 may perform an operation 445 for intercepting Coquenice aspect data at least in part in response to the determination that Coquenice is directed to the end user entity, as shown in FIG. 4G. It may include. For example, the Cohenike aspect data intercept module 102 that includes the end user entity designation determination module 230 (see FIG. 2B) of the network device 10 of FIG. 1B may be configured by the end user entity designation determination module 230. 52 may intercept (e.g., hold) the Cohenike aspect data 53 at least in response to determining that 52 is directed to (eg, sent or transmitted to) the end user entity 30.

As shown in FIG. 4G, in some implementations, operation 445 can further include one or more additional operations. For example, in various implementations, operation 445 may further include an operation 446 for intercepting the Corniche aspect data at least partially in response to determining that the Corniche is directed to a representation of an end user entity as shown in FIG. 4G. have. For example, the Cohenike aspect data intercept module 102 that includes the end user entity association representation determination module 231 (see FIG. 2B) of the network device 10 of FIG. 1B may be configured to include an end user entity association representation determination module 231. In response, at least in part, to determine that the cocaine is directed to a representation of the end user entity 30 (e.g., an identifier such as a name, address, or telephone number) may intercept (e.g., hold) cocaine aspect data 53. .

In some cases, operation 446 again includes an operation 447 for intercepting the Corsonike aspect data at least in part in response to a determination that the Corkenike is directed to an address associated with the end user entity, as further shown in FIG. 4G. can do. For example, the Cohenike aspect data intercept module 102 that includes the end user entity association address determination module 232 (see FIG. 2B) of the network device 10 of FIG. 1B may be configured to include an end user entity association address determination module 232. In response to at least partly determining that the cochnice 52 is directed to an address (eg, an email address) associated with the end user entity 30, the cochnice aspect data 53 may intercept (eg, hold).

In some implementations, operation 447 is at least partially in response to determining that the cocaine destined for at least one of an email address, an Internet Protocol (IP) address, or a URL associated with the end user entity, as shown further in FIG. 4G. May further comprise an operation 448 to intercept. For example, the Cohenike aspect data intercept module 102 that includes the end user entity association address determination module 232 (see FIG. 2B) of the network device 10 of FIG. 1B may be configured to include an end user entity association address determination module 232. Intercept (e.g., hold) the Cornish Nike aspect data 53 in response at least in part to determining that the Corniche 52 is directed to at least one of an email address, an Internet Protocol (IP) address, or a URL associated with the end user entity 30. can do.

In the same or other implementations, the operation 446 for intercepting the Coquenice aspect data in response to at least partly in response to the determination that Cocaine is directed to the representation of the end user entity is further illustrated in FIG. And operation 449 for intercepting Coquenice aspect data at least in part in response to determining that it is directed to an associated telephone number. For example, the Cohenike aspect data intercept module 102 that includes the end user entity associated phone number determination module 233 (see FIG. 2B) of the network device 10 of FIG. 1B is an end user entity associated phone number determination module 233. ) May intercept (eg, hold) the Corniche aspect data 53 at least in part in response to determining that the Corniche 52 is directed to the telephone number associated with the end user entity 30.

In the same or another implementation, operation 446 may include an operation 450 for intercepting the Corniche aspect data in response at least in part to a determination that the Corniche is directed to a name associated with the end user entity, as further illustrated in FIG. 4G. Can be. For example, the Cohenike aspect data intercept module 102 that includes the end user entity association name determination module 234 (see FIG. 2B) of the network device 10 of FIG. 1B may be configured to include an end user entity association name determination module 234. In response to at least partly determining that the coquenice 52 is directed to the name associated with the end user entity 30, the coquenice aspect data 53 may intercept (eg, hold).

In some cases, the cocaine aspect data intercept operation 302 of FIG. 3 may include one or more conditional indications by intercepting cocaine in response to determining that at least cocaine is associated with and directed to the end user entity, as further shown in FIG. 4G. The method may further include an operation 451 for intercepting the Coquenice aspect data. For example, the Cohenike aspect data intercept module 102, which includes the source entity association determination module 224 and the end user entity assignment determination module 230 of the network device 10 of FIG. 1B, is the source entity association determination module 224. And the one or more conditional instructions by intercepting the co-working 52 in response to the end-user entity designation determining module 230 determining at least the co-working 52 is associated with the source entity 20 and directed towards the end-user entity 30, respectively. According to (50) it is possible to intercept (e.g., hold) the Coquenice aspect data 53.

In the same or other implementations, the Coquenice aspect data intercept operation 302 of FIG. 3 includes one or more specific words or phrases, as shown in FIG. 4G, where the coquenice is specified by one or more conditional instructions associated with the source entity. It may additionally or alternatively include an operation 452 for intercepting the Coquenice aspect data in accordance with one or more conditional instructions by intercepting the Coquenice aspect data at least partially in response to a determination to include the subject. For example, the Cohenike aspect data intercept module 102 that includes the source entity association subject determination module 235 (see FIG. 2B) of the network device 10 of FIG. 1B may be configured to include a source entity association subject determination module 235. Intercepting cocaine 52 at least partially in response to determining that cocaine 52 includes a subject that includes one or more specific words or phrases specified by one or more conditional instructions 50 associated with source entity 20. Thereby intercepting (e.g., holding) Cochlenick aspect data 53 in accordance with one or more conditional instructions 50. The determination as to whether the cochnice 52 includes a subject heading that includes one or more specific words or phrases associated with the source entity 20 may be based on the cochlenick aspect data 53, and the cochnice aspect data 53 may be The subject head of the commune 52 can be displayed.

Returning to the secret indicator data transfer operation 304 of FIG. 3, the secret indicator data transfer operation 304 similar to the Coquenice aspect data intercept operation 302 of FIG. 3 can be described with respect to FIGS. As shown in 5g, it can be implemented in a variety of ways in various alternative implementations. For example, in some implementations, the secret indicator data transfer operation 304 of FIG. 3 can further include an operation 553 for transmitting the secret indicator data via one or more communication networks as shown in FIG. 5A. For example, the secret indicator data transmission module 104 of the network device 10 of FIG. 1B may include one or more communication networks 40 (eg, WLAN, WMAN, WiMAX, PTSN, VoIP networks, cellular networks, client / server networks, The secret indicator data 54 can be transmitted via a VPN or the like.

In the same or other implementations, the secret indicator data transfer operation 304 of FIG. 3 may include an operation 554 for transmitting the secret indicator data to the communication device of the end user entity as further shown in FIG. 5A. For example, the secret indicator data transmission module 104 of the network device 10 of FIG. 1B may transmit the secret indicator data 54 to the communication device 34 of the end user entity 30 (eg, mobile phone, PDA, smart phone). , Computer tablet, laptop or desktop computer).

In the same or other implementations, the secret indicator data transfer operation 304 may include an operation 555 for transmitting the secret indicator data to the end user's representation of the end user entity as further shown in FIG. 5A. For example, the secret indicator data transmission module 104 of the network device 10 of FIG. 1B may send the secret indicator data 54 to a representation (eg, identifier) of the end user 32 of the end user entity 30. have.

In particular, operation 555 may include operation 556 for transmitting, in some cases, secret indicator data to at least one of a name, address, or telephone number associated with the end user, as further illustrated in FIG. 5A. For example, the secret indicator data transmission module 104 of the network device 10 of FIG. IP address or URL address) or a telephone number.

In the same or other implementations, the secret indicator data transfer operation 304 is secret to the end user entity instead of sending all direct indications of the commune to the end user entity in response to an intercept of the cochlear aspect data, as further shown in FIG. 5A. And operation 557 for sending the indicator. For example, the secret indicator data transmission module 104 of the network device 10 of FIG. 1B may respond to the intercept of the Coquenice aspect data 53 to tell the end user entity 30 all (eg, any) of the Coquenice 52. And total) direct indicator data 54 to the end user entity 30 instead of sending a direct indication. An example of a direct representation of the commune 52 may refer to the source entity 20 associated with the commune 52, for example, in the form of an email address, IP address, name, or telephone number associated with the source entity 20. An indication to identify, an indication to indicate the subject matter for the cocaine 52, if present, the receipt of a cocaine 52 (e.g., an email or voice message), such as when the cocaine 52 was received by the network device 10 And an indication for displaying the time.

As further shown in FIG. 5A, instead of sending a direct indication of the commune 52, the operation 557 for transmitting communeike data may be performed in a variety of ways. For example, in some implementations, operation 557 may be configured to transmit secret indicator data to an end user entity in response to an intercept of the communeike aspect data, as shown further in FIG. 558). For example, the secret indicator data transmission module 104 of the network device 10 of FIG. 1B may respond to an intercept of the communeike aspect data 53 with a communeike 52 (e.g., a text message, e.g. Instead of sending to the end user entity 30 an electronic copy of the commune 52, which may be the same audio message, or other form of communication, the secret indicator data 54 may be sent to the end user entity 30. .

In the same or another implementation, operation 557 is in response to the intercept of the cochlear aspect data, as shown in FIG. 5A, for sending secret indicator data to the end user entity instead of sending the cochlear aspect data to the end user entity. 559 may be included. For example, the secret indicator data transmission module 104 of the network device 10 of FIG. 1B responds to the intercept of the cocaine aspect data 53 instead of sending the cocaine aspect data 53 to the end user entity 30. The secret indicator data 54 may be sent to the user entity 30.

In the same or another implementation, operation 557 sends secret indicator data to the end user entity in response to the intercept of the cocaine aspect data as shown in FIG. 5A, instead of sending the header type data associated with the cocaine to the end user entity. And an operation 560 to do so. For example, the secret indicator data transmission module 104 of the network device 10 of FIG. 1B may send header type data (eg, associated with the communeike 52) to the end user entity 30 in response to the intercept of the communeike aspect data 53. Instead of transmitting the end user entity (data including header type information including the telephone number, name, or address of the source for the cocaine 52, subject headings for the cocaine 52, reception time, etc.) 30 may send secret indicator data 54.

In some cases, operation 560 may be subject to the subject of Cochinike, any data that directly identifies the source entity associated with Cochinike to the end user entity in response to an intercept of Cochinike aspect data, as further illustrated in FIG. 5A. Or instead of transmitting the reception time of the communeike, an operation 561 for transmitting the secret indicator data to the end user entity. For example, the secret indicator data transmission module 104 of the network device 10 of FIG. 1B may respond to the end user entity 30 with the source entity 20 in association with the commune 52 in response to the intercept of the communeike aspect data 53. Instead of sending any data that directly identifies, the subject of the cocaine 52, or the time of receipt of the cocaine 52, the secret indicator data 54 may be sent to the end user entity 30.

The secret indicator data 54, which may be transmitted to the end user entity 30 in the secret indicator data transfer operation 304 of FIG. 3, may take various forms including various content. For example, in some cases, the transmitted secret indicator data 54 may provide one or more secret indicators for the receiving device (eg, communication device 34) to secretly display one or more aspects of, for example, the commune 52. It can be a simple "ping" with very little content to let you. In other cases, however, the secret indicator data 54 may be more complex, containing more content. For example, in some cases, the secret indicator data 54 may be one or more aspects of the cocaine 52 (eg, an email address or phone number of the source entity 20 associated with the cocaine 52, cocaine 52, if present). And one or more temporary representations (eg, substitutes or placeholders) for the subject, and / or other aspects of the. The content of the secret indicator data 54 is broad because the end user entity 30 cooperating with the network device 10 (eg, the end user 32) can determine what may be included in the secret indicator data 54. Can change.

Thus, in order to define the secret indicator data 54, rather than defining the secret indicator data 54 as its content, the end user entity 30 (eg, communication device 34) is responsible for receiving the secret indicator data 54. It may be more appropriate to define the secret indicator data 54 by identifying how it responds. That is, the actual content of the secret indicator data 54 may include, for example, when the communication device 34 receives the secret indicator data 54, the secret indicator data 54 is transmitted to the communication device 34 of the end user entity 30. It may not be as important as the effect. For example, in some implementations, the secret indicator data transfer operation 304 of FIG. 3 may cause one or more aspects of the commune to be communicated to the end user of the end user entity by the communication device upon receipt by the communication device of the end user entity as shown in FIG. 5B. And transmitting 562 the secret indicator data by sending the secret indicator data to the end user entity to provide a secret indicator to secretly indicate. For example, the secret indicator data transmission module 104 of the network device 10 of FIG. 1B may be configured such that upon receipt by the communication device 34 of the end user entity 30, the communication device 34 may be configured to receive the end user entity 30. Secretly presenting one or more aspects of cocaine 52 to end user 32 (eg, source entity 20, subject of cocaine 52, if present, receipt time of cocaine 52, and / or coquenice). Secret indicator data 54 to provide (eg, visually display and / or audibly display) a secret indicator (eg, an indirect indicator) that secretly displays other aspects associated with (52). The secret indicator data 54 can be transmitted by sending it to 30).

As further shown in FIG. 5B, in various alternative implementations, operation 562 may include one or more additional operations. For example, in some implementations, operation 562 is a predefined secret indicator known by the end user that, upon receipt by the communication device, the communication device secretly indicates one or more aspects of the commune, as shown further in FIG. 5B. And transmitting 563 the secret indicator data to the end user entity by sending the predetermined data to the end user entity to provide. For example, the secret indicator data transmission module 104 of the network device 10 of FIG. 1B may be configured such that upon receipt by the communication device 34, the communication device 34 secretly displays one or more aspects of the commune 52, Predetermined secret indicators known by the end user 32 (e.g., images, messages, specific fonts or colors that have a specific meaning to the end user 32, for example, when a pre-specified secret indicator is provided through the communication device 34). Secret indicator data 54 may be transmitted to the end user entity 30 by sending predetermined data to the end user entity 30.

In some cases, operation 563 may further include an operation 564 for transmitting the predetermined data to the end user entity at least partially defined by one or more conditional instructions, as further shown in FIG. 5B. Can be. For example, the secret indicator data transmission module 104 of the network device 10 of FIG. 1B may transmit, to the end user entity 30, predefined data defined at least in part by one or more conditional instructions 50, The predefined data may be simple "pings" or data containing more content.

As further shown in FIG. 5B, in various implementations, operation 562 includes secret indicator data that, upon receipt by the communication device, cause the communication device to provide the end user with a secret indicator that indirectly indicates one or more aspects of the commune. And act 565 to send the secret indicator data to the end user entity. For example, the secret indicator data transmission module 104 of the network device 10 of FIG. Provides a secret indicator (e.g. visually display, The secret indicator data 54, including the secret indicator data 54 for audible display and / or vibration, may be transmitted to the end user entity 30.

Operation 565, in turn, causes the communication device to provide a secret audio indicator that, upon receipt by the communication device, upon receipt by the communication device, indirectly and indirectly presenting one or more aspects of the commune to the end user, as further shown in FIG. 5B. The method may further include an operation 566 for transmitting the secret indicator data to the end user entity by sending the data to the end user entity. For example, the secret indicator data transmission module 104 of the network device 10 of FIG. 1B may include one or more aspects of the commune 52 when the communication device 34 receives the end user 32 upon receipt by the communication device 34. Sending the secret indicator data 54 to the end user entity 30 by sending the secret indicator data 54 to the end user entity 30 to provide a secret audio indicator that audibly and indirectly indicates (eg, receipt of the co-enforcement 52). Transmit to entity 30.

In some implementations, operation 566 can include at least a ping, ring, or indirect indication of one or more aspects of the commune to the end user by the communication device upon receipt by the communication device, as further shown in FIG. 5B. And act 567 for transmitting the secret indicator data to the end user entity by sending the secret indicator data to the end user entity to provide an hum to the end user entity. For example, the secret indicator data transmission module 104 of the network device 10 of FIG. 1B may include one or more aspects of the commune 52 when the communication device 34 receives the end user 32 upon receipt by the communication device 34. Secret indicator data 54 to audibly provide at least a ping, ring, or hum to indicate indirectly (e.g., reception of cocaine 52 or association with source entity 20 of cocaine 52). Secret indicator data 54 may be transmitted to the end user entity 30 by sending.

In the same or another implementation, operation 566 may further include one or more simulated natural background noises that, upon receipt by the communication device, indirectly indicate one or more aspects of the commune to the end user, as shown in FIG. 5B. And act 568 for transmitting the secret indicator data to the end user entity by sending the secret indicator data to the end user entity for audible presentation. For example, the secret indicator data transmission module 104 of the network device 10 of FIG. 1B may be configured such that, upon receipt by the communication device 34, the communication device 34 provides the end user 32 with one or more attributes of the cooperative. To provide one or more simulated natural background noises (e.g., noises such as passing trucks or dog barks) that indirectly indicate (e.g., reception of the commune 52 from the source entity 20). The secret indicator data 54 may be transmitted to the end user entity 30 by sending the secret indicator data 54 to the end user entity 30.

Referring now to FIG. 5C, in various implementations, upon receipt by the communication device, the end device entity may present secret indicator data to the end user entity that causes the communication device to provide the end user with a secret audio indicator that audibly and indirectly displays one or more aspects of the commune. Operation 566 for transmitting comprises end-user entity secret information, such as upon receipt by the communication device, that the communication device acoustically provides the end user with at least one voice message indirectly indicating one or more aspects of the commune. And sending the secret indicator data to the end user entity by sending it to. For example, the secret indicator data transmission module 104 of the network device 10 of FIG. 1B may include one or more aspects of the commune 52 when the communication device 34 receives the end user 32 upon receipt by the communication device 34. At least one voice message that indicates indirectly to the voice message (e.g., a voice message generated to indirectly display a previously received voice message or one or more aspects of the commune 52 that may not be associated with the commune 52). The secret indicator data 54 can be transmitted to the end user entity 30 by sending the secret indicator data 54 to the end user entity 30 for audible presentation.

In some cases, operation 569 further displays at least one voice message generated such that upon receipt by the communication device the communication device indirectly displays one or more aspects of the commune to the end user, as shown in FIG. 5C. And act 570 for sending the secret indicator data to the end user entity by sending the secret indicator data to the end user entity to provide it to the user. For example, the secret indicator data transmission module 104 of the network device 10 of FIG. 1B may include one or more aspects of the commune 52 when the communication device 34 receives the end user 32 upon receipt by the communication device 34. By sending the secret indicator data 54 to the end user entity 30 for audibly providing at least one voice message generated (eg, generated in accordance with one or more conditional instructions 50) to indirectly indicate The secret indicator data 54 may be sent to the end user entity 30.

In the same or other implementations, operation 569 may include at least one voice previously provided such that, upon receipt by the communication device, the communication device indirectly displays one or more aspects of the commune to the end user, as shown in FIG. 5C. And operation 571 for sending the secret indicator data to the end user entity by sending the secret indicator data to the end user entity to provide an audible message. For example, the secret indicator data transmission module 104 of the network device 10 of FIG. 1B may include one or more aspects of the commune 52 when the communication device 34 receives the end user 32 upon receipt by the communication device 34. Send the secret indicator data 54 to the end user entity 30 by sending the secret indicator data 54 to the end user entity 30 to audibly provide at least one voice message previously provided to indirectly indicate Can be.

In some cases, operation 571 may include at least one voice previously provided and modified to indirectly display one or more aspects of the commune to the end user upon receipt by the communication device, as shown in FIG. 5C. The method may further include an operation 572 for transmitting the secret indicator data to the end user entity by sending the secret indicator data to the end user entity for providing the message acoustically. For example, the secret indicator data transmission module 104 of the network device 10 of FIG. 1B may include one or more aspects of the commune 52 when the communication device 34 receives the end user 32 upon receipt by the communication device 34. Audibly present at least one voice message that has been previously provided to indirectly display (e.g., an audio community 52 previously provided from a third party not associated with the source entity 20) (e.g., tone change). The secret indicator data 54 can be transmitted to the end user entity 30 by sending the secret indicator data 54 to the end user entity 30.

Referring now to FIG. 5D, in various implementations, an end user may display secret indicator data, including secret indicator data, such that upon receipt by the communication device, the communication device provides the end user with a secret indicator that indirectly displays one or more aspects of the communeke. Operation 565 for transmitting to the entity provides the end user entity with secret indicator data that, upon reception by the communication device, the communication device provides the end user with a secret visual indicator that visually indirectly displays one or more aspects of the communeke. And sending 557 the secret indicator data to the end user entity. For example, the secret indicator data transmission module 104 of the network device 10 of FIG. 1B may include one or more aspects of the commune 52 when the communication device 34 receives the end user 32 upon receipt by the communication device 34. End user entity 30 to provide secret indicator data 54 to provide a secret visual indicator that visually indirectly displays (e.g., indirectly via a co-working application interface such as an email application interface or an operating system interface). The secret indicator data 54 may be transmitted to the end user entity 30 by sending it to.

In some implementations, operation 573 can include one or more visual symbols or icons that, when further received by the communication device, visually indirectly display one or more aspects of the commune to the end user, as shown in FIG. 5D. The method may further include an operation 574 for transmitting the secret indicator data to the end user entity by sending the secret indicator data to the end user entity to provide. For example, the secret indicator data transmission module 104 of the network device 10 of FIG. 1B may include one or more aspects of the commune 52 when the communication device 34 receives the end user 32 upon receipt by the communication device 34. The secret indicator data 54 may be transmitted to the end user entity 30 by sending the secret indicator data 54 to the end user entity 30 to provide one or more visual symbols or icons that visually and indirectly indicate. have.

In the same or other implementations, operation 573 may include one or more specific colors that, upon further reception by the communication device, visually indirectly display one or more aspects of the commune to the end user, as shown in FIG. 5D. And transmitting 575 the secret indicator data to the end user entity by sending the secret indicator data to the end user entity. For example, the secret indicator data transmission module 104 of the network device 10 of FIG. 1B may include one or more aspects of the commune 52 when the communication device 34 receives the end user 32 upon receipt by the communication device 34. Secret indicator data 54 by sending secret indicator data 54 to the end user entity 30 to provide one or more specific colors that visually indirectly display (e.g., providing a particular icon or image in a particular color). May be sent to the end user entity 30.

In the same or another implementation, operation 573 may include at least one visual message that, upon reception by the communication device, visually indirectly displays one or more aspects of the commune to the end user, as shown in FIG. 5E. And transmitting 576 the secret indicator data to the end user entity by sending the secret indicator data to the end user entity to provide. For example, the secret indicator data transmission module 104 of the network device 10 of FIG. 1B may include one or more aspects of the commune 52 when the communication device 34 receives the end user 32 upon receipt by the communication device 34. Sends the secret indicator data 54 to the end user entity 30 by sending the secret indicator data 54 to the end user entity 30 to provide at least one visual message (eg, a text message) that visually indirectly displays the. ) Can be sent.

As shown in FIG. 5E, operation 576 is a secret indicator that, upon reception by the communication device, causes the communication device to provide one or more visual words or phrases that visually indirectly indicate one or more aspects of the commune to the end user. One or more additional operations, including an operation 577 for sending the secret indicator data to the end user entity by sending the data to the end user entity. For example, the secret indicator data transmission module 104 of the network device 10 of FIG. 1B may include one or more aspects of the commune 52 when the communication device 34 receives the end user 32 upon receipt by the communication device 34. May be visually indirectly displayed (e.g., visually indirectly indicating that the cochnice 52 associated with the source entity 20 has been received) or one or more visual words or phrases (e.g., provided to the end user 32). The secret indicator data 54 is sent to the end user entity 30 by sending the secret indicator data 54 to the end user entity 30 to provide one or more words or phrases recognized by the user 32 as having a specific meaning. ) Can be sent.

In some implementations, operation 577 can include one or more visual words or phrases upon receipt by the communication device that the communication device visually indirectly displays one or more aspects of the commune to the end user, as further shown in FIG. 5E. The method may further include an operation 578 for transmitting the secret indicator data to the end user entity by sending the secret indicator data to the end user entity to provide the in a particular font or style. For example, the secret indicator data transmission module 104 of the network device 10 of FIG. 1B may include one or more aspects of the commune 52 when the communication device 34 receives the end user 32 upon receipt by the communication device 34. Sends the secret indicator data 54 to the end user entity 30 by providing one or more visual words or phrases in a particular font or style to visually and indirectly display the. 30).

In some cases, the operation 576 for transmitting secret indicator data upon receipt by the communication device to cause the communication device to provide the end user with one or more visual words or phrases that visually indirectly indicate one or more aspects of the commune. ) Further displays secret indicator data that, upon receipt by the communication device, the communication device provides a previously provided visual message to the end user to visually indirectly display one or more aspects of the commune, as further shown in FIG. 5E. And sending the secret indicator data to the end user entity by sending it to the user entity. For example, the secret indicator data transmission module 104 of the network device 10 of FIG. 1B may include one or more aspects of the commune 52 when the communication device 34 receives the end user 32 upon receipt by the communication device 34. The secret indicator data 54 to the end user entity 30 by sending the secret indicator data 54 to the end user entity 30 to provide a previously provided visual message (eg, a visual text message) to visually indirectly display the. 30 can be sent.

In some cases, operation 579 is previously provided and modified to allow the communication device to visually indirectly display one or more aspects of the commune to the end user upon receipt by the communication device, as further shown in FIG. 5E. The method may further include an operation 580 for sending the secret indicator data to the end user entity by sending the secret indicator data to the end user entity to provide a message. For example, the secret indicator data transmission module 104 of the network device 10 of FIG. 1B may include one or more aspects of the commune 52 when the communication device 34 receives the end user 32 upon receipt by the communication device 34. Secret indicator data 54 by sending to the end user entity 30 a secret indicator data 54 which was previously provided to visually indirectly display (e.g., previously received email or phone message) and which provides a modified visual message. 54 may be sent to the end user entity 30.

As further shown in FIG. 5E, in various implementations, an operation for transmitting secret indicator data such that upon receipt by the communication device the communication device provides the end user with a secret indicator indirectly indicating one or more aspects of the commune. 565) transmits the secret indicator data to the end user entity by sending the secret indicator data to the end user entity upon receiving by the communication device the secret device providing the end user a secret vibration indicator that indirectly indicates one or more aspects of the communeke through a specific vibration. And operation 581 for sending the secret indicator data to the user entity. For example, the secret indicator data transmission module 104 of the network device 10 of FIG. 1B may communicate with the end user 32 when the communication device 34 receives the communication information from the communication device 34 through a specific vibration. Secret indicator data by sending secret indicator data 54 to the end user entity 30 to provide a secret vibration indicator indirectly indicating one or more aspects of 52) (eg, to generate a specific vibration with a specific vibration pattern). 54 may be sent to the end user entity 30.

Referring now to FIG. 5F, the secret indicator data transfer operation 304 of FIG. 3, in various alternative implementations, secrets to the end user entity by sending secret indicator data to the end user entity that does not at least directly identify the source entity. And operation 582 for transmitting the indicator data. For example, the secret indicator data transmission module 104 of the network device 10 of FIG. 1B may transmit a secret indicator data 54 to the end user entity 30 that does not at least directly identify the source entity 20. Indicator data 54 may be sent to end user entity 30. That is, secret indicator data 54 may be transmitted that includes at least any data identifying a relationship between source entity 20 and commune 52.

For example, in some implementations, operation 582 may be secreted to the end user entity by sending secret indicator data to the end user entity that does not at least directly identify the source entity as the source for the commune, as further shown in FIG. 5F. And operation 583 for transmitting the indicator data. For example, the secret indicator data transmission module 104 of the network device 10 of FIG. 1B identifies at least directly the source entity 20 as a source for the coworker 52 (e.g., the source entity 20 may be The secret indicator data 54 may be sent to the end user entity 30 by sending the secret indicator data 54, which is not identified as the originator or caller of 52, to the end user entity 30.

In the same or another implementation, operation 582 transmits the secret indicator data to the end user entity by sending the secret indicator data to the end user entity that does not include any representation of the source entity, as further shown in FIG. 5F. May comprise an operation 584 to do so. For example, the secret indicator data transfer module 104 of the network device 10 of FIG. 1B may include secret indicator data 54 that does not include any representation (eg, identifier) of the source entity 20. And the secret indicator data 54 to the end user entity 30.

In various implementations, operation 584 may be directed to the end user entity by sending secret indicator data to the end user entity that does not include any name, address, or telephone number associated with the source entity, as further illustrated in FIG. 5F. The method may further include an operation 585 for transmitting the secret indicator data. For example, the secret indicator data transmission module 104 of the network device 10 of FIG. 1B may include any name associated with the source entity 20 (eg, user name, business name, website name, etc.), address (eg, The secret indicator data 54 can be sent to the end user entity 30 by sending the secret indicator data 54 to the end user entity 30 that does not include an email address, an IP address, a URL, etc.) or a telephone number. .

In the same or another implementation, operation 584 is secret to the end user entity by sending secret indicator data to the end user entity that includes one or more temporary surrogate for one or more representations of the source entity, as shown in FIG. 5F. And operation 586 for transmitting the indicator data. For example, the secret indicator data transmission module 104 including the temporary surrogate secret indicator data transmission module 240 (see FIG. 2C) of the network device 10 of FIG. 1B may include the temporary indicator secret indicator data transmission module 240. ) Provides the end user entity 30 with secret indicator data (including one or more temporary representations (eg, surrogate or placeholders) for one or more representations (eg, address, phone number, name, etc.) of the source entity 20. 54 may transmit the secret indicator data 54 to the end user entity 30. That is, for example, one or more (fictional or non-fictional) surrogate names, (fictional or non-fictional) for one or more real names, addresses, and / or phone numbers associated with the source entity 20 that may be included in the Cohenike aspect data 53, for example. Secret indicator data 54, including a fictitious) alternate address, and / or a (fictional or non-fictitious) alternate phone number, may be sent to the end user entity 30.

As further shown in FIG. 5F, in some implementations, operation 586 sends secret indicator data to the end user entity by sending secret indicator data to the end user entity that includes one or more surrogates for one or more names associated with the source entity. Operation 587 may be further included. For example, the secret indicator data transmission module 104 including the surrogate secret indicator data transmission module 241 (see FIG. 2C) of the network device 10 of FIG. 1B may include a surrogate secret indicator data transmission module 241. End user may have secret indicator data 54 that includes one or more surrogates for one or more names associated with source entity 20 (eg, surrogate names or other forms of surrogate for representing source entity 20 secretly). By sending to the entity 30, the secret indicator data 54 can be transmitted to the end user entity 30.

In the same or another implementation, operation 586 is secret to the end user entity by sending secret indicator data to the end user entity that includes one or more surrogates for one or more addresses associated with the source entity, as shown in FIG. 5F. Operation 588 for transmitting the indicator data. For example, the secret indicator data transmission module 104 including the surrogate secret indicator data transmission module 241 (see FIG. 2C) of the network device 10 of FIG. 1B may include a surrogate secret indicator data transmission module 241. Represent one or more surrogates (e.g., surrogate addresses or other forms of surrogate to secretly represent the source entity 20) for one or more addresses (e.g., email addresses, IP addresses, URLs, etc.) associated with the source entity 20 The secret indicator data 54 may be transmitted to the end user entity 30 by causing the containing secret indicator data 54 to be sent to the end user entity 30.

In the same or another implementation, operation 586 may be performed by sending the end user entity secret indicator data including at least one surrogate for at least one telephone number associated with the source entity, as shown in FIG. 5F. And operation 589 for sending the secret indicator data to the entity. For example, the secret indicator data transmission module 104 including the surrogate secret indicator data transmission module 241 (see FIG. 2C) of the network device 10 of FIG. 1B may include a surrogate secret indicator data transmission module 241. Finalizing the secret indicator data 54 including at least one surrogate for at least one telephone number associated with the source entity 20 (eg, a surrogate phone number or other surrogate to secretly represent the source entity 20). Secret indicator data 54 may be transmitted to end user entity 30 by having the user entity 30 transmit.

As shown in FIG. 5F, in various implementations, operation 582 for transmitting the secret indicator data that does not at least directly identify the source entity may include sending secret indicator data to the end user entity that does not at least directly identify the commune. And by sending 590 the secret indicator data to the end user entity. For example, the secret indicator data transmission module 104 of the network device 10 of FIG. 1B may transmit the secret indicator data 54 to the end user entity 30 that does not at least directly identify the communicator 52. Data 54 may be sent to end user entity 30.

In some implementations, operation 590 transmits the secret indicator data to the end user entity by sending the secret indicator data to the end user entity that does not at least directly identify the subject for the commune, as further illustrated in FIG. 5F. It may include an operation 591 to. For example, the secret indicator data transmission module 104 of the network device 10 of FIG. By sending 54 to the end user entity 30, the secret indicator data 54 can be sent to the end user entity 30.

Referring now to FIG. 5G, in various implementations, the secret indicator data transfer operation 304 of FIG. 3 may be performed by sending the secret indicator data in the form of header data to the end user entity, as further illustrated in FIG. 5G. And an operation 592 for sending the secret indicator data to the user. For example, the secret indicator data transmission module 104 of the network device 10 of FIG. 1B sends the secret indicator data 54 in the form of header data to the end user entity 30 to finalize the secret indicator data 54. Send to user entity 30.

In the same or another implementation, the secret indicator data transfer operation 304 of FIG. 3 may be performed by sending an end user entity a list of one or more received communecides containing secret indicator data, as further shown in FIG. 5G. And operation 593 for sending the secret indicator data to the entity. For example, the secret indicator data transmission module 104 including the reception co-nique list transmission module 242 (see FIG. 2C) of the network device 10 of FIG. 1B may include a reception indicator data transmission module 242. The secret indicator data 54 may be sent to the end user entity 30 by having a list of one or more received communication 52 (eg, email) including 54 be sent to the species user entity 30. For example, a list of received emails may be sent that includes at least one list of fictitious emails (eg, secret indicator data 54) to secretly indicate receipt of the commune 52.

In some cases, operation 593 may be secreted by sending a list of one or more received communikes to the end user entity that includes one or more temporary surrogate for one or more representations of the source entity, as further shown in FIG. 5G. The method may further include an operation 594 for sending a list of one or more received communeques including the indicator data to the end user entity. For example, the secret indicator data transmission module 104, which includes the receiving communication list transmission module 242 of the network device 10 of FIG. 1B, has a receiving communication list transmission module 242 having one or more representations of the source entity 20. End User Entities A list of one or more received commune 52 containing one or more temporary surrogates (eg, surrogate or placeholder) for an identifier, such as an address, name, phone number, or other form of identifier. Sending to 30 may transmit to end user entity 30 a list of one or more received coworkers 52 including secret indicator data 54.

Reference is made to FIG. 6, which illustrates another flowchart 600 in accordance with various embodiments. The flowchart 600 includes specific operations that reflect the operations included in the flowchart 300 of FIG. 3. This operation includes the Cochniquet aspect data intercept operation 602 and the secret indicator data transmission operation 604, which correspond and reflect the Cochlenick aspect data intercept operation 302 and the secret indicator data transmission operation 304 of FIG. 3, respectively.

Additionally, flowchart 600 may include a conditional indication receiving operation 606 for receiving one or more conditional indications from an end user entity as shown in FIG. 6. For example, the conditional instruction receiving module 101 of the network device 10 of FIG. 1B may receive one or more conditional instructions 50 from the end user entity 30.

In some implementations, conditional instruction receiving operation 606 can further include an operation 608 for requesting one or more conditional instructions from an end user entity as further shown in FIG. 6. For example, the conditional indication request module 105 of the network device 10 of FIG. 1B may request one or more conditional instructions 50 from the end user entity 30 (eg, the end user 32 of the end user entity 30). Request one or more conditional instructions 50).

Next, operation 608 may further include operation 610, in various implementations, for sending one or more requests for one or more conditional instructions to the end user entity, as shown in FIG. 6. For example, the conditional indication request transmission module 106 of the network device 10 may send an end user entity 30 a request for one or more conditional instructions 50 (eg, via one or more communication networks 40). Can transmit

Referring now to FIG. 7, which is a high level block diagram illustrating a particular implementation of the network device 10 of FIG. 1B. As shown, in some embodiments network device 10, which may include one or more servers, may include one or more processors 702 that are connected to storage medium 706 (eg, volatile and / or nonvolatile memory). (Eg, one or more microprocessors, one or more controllers, etc.). Storage medium 706 can store computer readable instructions 704 (eg, a computer program product). One or more processors 702 are the ones shown and described above in various implementations, such as in FIGS. 3, 4a, 4b, 4c, 4d, 4e, 4f, 4g, 5a, 5b, 5c, 5d, 5e, 5f, and 5g. Computer-readable instructions 704 may be executed to perform the above operations. In another aspect, FIG. 7 shows the Coquenice aspect data intercept module 102, the secret indicator data transmission module 104 of the network device 10, and subordinates thereof (eg, as shown in FIGS. 2A, 2B, and 2C). By one or more processors 702 executing software (eg, shown as computer readable instructions 704 in FIG. 7) that may be stored in a memory (eg, shown as storage medium 706 in FIG. 7). One implementation of a network device 10 that is implemented is shown.

For example, the processor 702 may display one or more aspects of the commune 52 directed to the end user entity 30 and directed to the end user entity 30, as shown by the flowchart 300 of FIG. 3. Intercept according to one or more conditional instructions 50 of the end-user entity 30 to conditionally obfuscate the Coquenice aspect data 53 associated with the source entity 20 and the Coquenice 52 associated with the source entity 20. And in response to intercepting the cocaine aspect data 53, instead of sending a direct representation of the cocaine 52 to the end user entity 30, one of the cocaine 52 upon receipt by the end user entity 30. Computer readable instructions 704 may be executed to send secret indicator data 54 to the end user entity 30 that secretly indicates the above aspects.

Those of ordinary skill in the art have evolved to the point where there is not much difference between implementing a system aspect in hardware and in software, so that the use of hardware and software can be It will be appreciated that design choices generally represent a cost-effective tradeoff, although not always in the sense that selection can be important. Those of ordinary skill in the art have a variety of means (e.g., hardware, software, and / or firmware) that can affect the processes and / or systems and / or other techniques described in this disclosure, and It will be appreciated that the preferred means may vary depending upon the circumstances in which the system and / or other techniques are used. For example, if an implementer decides that speed and accuracy are top priorities, the implementer may primarily choose hardware and / or firmware means; alternatively, if flexibility is determined to be top priority, the implementer may primarily choose a software implementation, Alternatively, the implementer may choose any combination of hardware, software, and / or firmware. Thus, there are many possible means by which the processes and / or devices and / or other techniques described in this disclosure may be affected, none of which are absolutely superior to the other, and which means to use. This is a choice depending on the context in which it is used and the particular consideration of the implementer (eg, speed, flexibility, or predictability), each of which may vary. One skilled in the art will recognize that the optical aspect of the implementation will generally employ optically-oriented hardware, software, and / or firmware.

The above detailed description has set forth various embodiments of the device and / or process using block diagrams, flow diagrams, and / or examples. As long as such block diagrams, flowcharts, and / or examples include one or more functions and / or operations, one of ordinary skill in the art will appreciate that each function and / or operation of such block diagrams, flowcharts, or examples vary. It will be appreciated that the hardware, software, firmware, or virtually any combination thereof may be implemented individually and / or collectively. In one embodiment, various portions of the subject matter described in this disclosure may be implemented through Application Specific Integrated Circuitry (ASIC), Field Programmable Gate Array (FPGA), Digital Signal Processor (DSP), or other integrated circuit form. However, those skilled in the art will appreciate that some aspects of the embodiments of the present disclosure may be, in whole or in part, one or more computer programs (e.g., one or more programs executed on one or more computer systems) running on one or more computers, May be equally implemented in integrated circuits such as one or more programs running on one or more processors (eg, one or more programs running on one or more microprocessors), firmware, or virtually any combination thereof, and software and / or It will be appreciated that the coding and / or circuit design for the firmware is within the skill of one of ordinary skill in the art in light of the present disclosure. In addition, those skilled in the art may distribute the mechanism of the subject matter described in this disclosure in various forms of program products, and the exemplary embodiments of the subject matter described in this disclosure are used to actually perform the distribution. It will be appreciated that it applies regardless of the particular form of signaling medium being employed. Examples of signaling media include recordable media such as floppy disks, hard disk drives, compact discs (CDs), digital video disks (DVDs), digital tapes, computer memory, and the like, as well as digital and / or analog communication media (e.g., fiber optic cables, Transmission media such as waveguides, wired communication links, wireless communication links, and the like.

Generally, one of ordinary skill in the art will appreciate that the various aspects described in this disclosure that can be implemented individually and / or collectively using a variety of hardware, software, firmware, or any combination thereof, It will be appreciated that it can be considered to include various forms of "electrical circuits." As a result, in the present disclosure, an “electric circuit” includes an electrical circuit including at least one discrete electrical circuit, an electrical circuit including at least one integrated circuit, an electrical circuit including at least one application specific integrated circuit, and a computer program. A general purpose computing device configured (e.g., a general purpose computer configured by a computer program that at least partially performs the processes and / or devices described in this disclosure or a computer that performs at least partially the processes and / or devices described in this disclosure. Electrical circuits constituting a microprocessor configured by a program, electrical circuits constituting a memory device (e.g., RAM), and / or communications device (e.g., modem, communication switch, or optical-electrical device) Electrical circuits are included but are not limited to these. Those skilled in the art will appreciate that the subject matter described in this disclosure can be implemented in analog or digital fashion or any combination thereof.

Those skilled in the art will recognize that it is common in the art to describe devices and / or processes in the manner set forth in this disclosure, and therefore, using engineering practices, such described devices and / or processes Will be integrated into the data processing system. That is, at least some of the devices and / or processes described in this disclosure can be integrated into the data processing system through appropriate amounts of experimentation. One of ordinary skill in the art will typically know that a typical data processing system typically includes one or more system unit housings, video display devices, memory such as volatile and nonvolatile memory, processors, operating systems, drivers, such as microprocessors and digital signal processors. , Graphical user interfaces, and computer entities such as application programs, one or more interaction devices such as touch pads or screens, and / or feedback loops and control motors (e.g. feedback for position and / or speed sensing, components And / or a control motor for volume adjustment and / or movement). Typical data processing systems may be implemented using any suitable commercially available components, such as those commonly found in data computing / communication and / or network computing / communication systems.

The subject matter described in this disclosure sometimes shows other components included within or connected with other components. It is to be understood that such illustrated architecture is merely exemplary and in practice may implement many other architectures that achieve the same functionality. Conceptually, any arrangement of components to achieve the same functionality is substantially "associated" such that the desired functionality is achieved. Thus, any two components combined to achieve a particular function in this disclosure may be viewed as "associated" with each other such that the desired function is achieved regardless of the architecture or intermediate component. Likewise, any two components so associated may also be viewed as "operably linked" or "operatively coupled" with each other to achieve the desired functionality, and any two components that may be so associated may desire the desired functionality. It can be seen as "operatively coupling" to each other to achieve. Specific examples of operatively combinable include physically combinable and / or physically interacting components and / or wirelessly interactable and / or wirelessly interacting components and / or logically interacting and / or logically interactable components. But it is not limited to this.

While certain aspects of the subject matter described in this disclosure have been shown and described, modifications may be made to those skilled in the art based on what is described in this disclosure without departing from the subject matter described herein and its broader aspects. And changes may be made, and therefore, the appended claims will be within the scope of all modifications and changes that fall within the true spirit and scope of the subject matter described in this disclosure. It is also to be understood that the invention is defined by the appended claims.

Those of ordinary skill in the art generally intend that the terminology used in this disclosure and in particular in the appended claims (eg, the text of the appended claims) is intended to be an “open” term (eg, the term “comprising”). Should be interpreted to include, but is not limited to, the term "having", "having at least", and the term "comprising" should be interpreted as "including but not limiting." The person will also appreciate that if a particular number of claims is intended, such intent will be expressly set forth in the claims, and without such a description, no such intention is intended. For the purpose of describing a claim, it may include the use of introductory phrases such as "at least one" and "one or more." Even when an introductory phrase such as "or" at least one "and an indefinite article such as" a "or" an "are included, a claim description by an indefinite article such as a" or "an" includes that claim description It should not be construed as to imply that any particular claim made herein is limited to inventions that include such descriptions (eg, "a" and / or "an" generally mean "at least one" or "one or more"). This also applies to the use of definite articles used in the claims.

In addition, even if a particular number of the appended claims is expressly stated, one of ordinary skill in the art will generally appreciate that such descriptions generally mean at least the number of those listed (e.g., "two descriptions" without other modifiers). Will generally be interpreted as meaning at least two or more than one substrate). Also, in examples where idioms similar to “at least one of A, B, C, etc.” are used, such constructs will generally be understood by those of ordinary skill in the art to understand such idioms (eg, “A Systems having at least one of, B, and C "include, but are not limited to, systems having A alone, B alone, C alone, A and B, A and C, B and C, and / or A, B and C, etc. It is written under the premise that it is not limited thereto.

In examples where idioms similar to "at least one of A, B, or C, etc." are used, such constructs will generally be understood by those of ordinary skill in the art to understand such idioms (e.g., "A, B Or a system having at least one of C "includes, but is not limited to, systems having A alone, B alone, C alone, A and B, A and C, B and C, and / or A, B and C, and the like. It is written under the premise of One of ordinary skill in the art would also appreciate that virtually any adjoining words and / or phrases representing two or more alternative terms may be used in any of the terms, either in the description, the claims, or the drawings. It will be understood that the possibility of including the term "," or both terms is considered. For example, the phrase "A or B" will be understood to include the possibility of "A" or "B" or "A and B".

Claims (197)

Conditionally obfuscate the communike aspect data associated with a particular source entity and indicate one or more aspects of the communique directed to the end user entity and towards the end user entity. Intercepting, according to one or more conditional indications of the end user entity; And
In response to intercepting the cocaine aspect data, instead of sending a direct representation of the cocaine to the end user entity, the secret indicator data secretly representing the one or more aspects of the cocaine upon receipt by the end user entity. Steps to Send to End User Entity
Computer implemented method comprising a. The method of claim 1,
One of the end user entity to indicate one or more aspects of the communeike directed to the end user entity and to conditionally obfuscate the communeike associated with the source entity, In accordance with the conditional instructions above, intercepting includes intercepting the Cohenike aspect data at a network device. The method of claim 2,
Intercepting the coquenic aspect data at the network device comprises intercepting the coquenic aspect data at the network device located at one or more network sites. The method of claim 3,
Intercepting the Coeniket aspect data at the network device located at the one or more network sites comprises intercepting the Coeniket aspect data at the network device including at least one network server located at the one or more network sites. Computer-implemented method. The method of claim 4, wherein
Intercepting the Coeniket aspect data at the network device including at least one network server located at the at least one network site comprises intercepting the Coeniket aspect data at the network device including at least one router. Computer-implemented method. The method of claim 4, wherein
Intercepting the Coeniket aspect data at the network device including at least one network server located at the at least one network site comprises at least intercepting the Coeniket aspect data at the network device including at least a telephone switch or telephone exchange. Comprising a computer implementation method. The method of claim 1,
One of the end user entity to indicate one or more aspects of the communeike directed to the end user entity and to conditionally obfuscate the communeike associated with the source entity, In accordance with the conditional instructions above, intercepting includes intercepting the Kokenike aspect data by intercepting Cokenike aspect data received via one or more communication networks. The method of claim 1,
One of the end user entity to indicate one or more aspects of the communeike directed to the end user entity and to conditionally obfuscate the communeike associated with the source entity, In accordance with the conditional instructions above, intercepting includes intercepting the Kokenike aspect data by receiving the Kokenike including the Kokenike aspect data. The method of claim 8,
Intercepting the communike aspect data by receiving the communike aspect comprising the communike aspect data comprises receiving the communeike by receiving a communeike containing the communike aspect data in a header data form. . The method of claim 8,
Intercepting the coquenice aspect data by receiving the coquenice containing the coquenice aspect data, receiving the coquenice by receiving a coquenice comprising the coquenice aspect data embedded in a ringing signal of the coquenice. Comprising a computer implementation method. The method of claim 8,
And intercepting the coquenice aspect data by receiving the coquenice aspect data including the coquenice aspect data, intercepting the coquenice aspect data by extracting the coquenice aspect data from the coquenice. The method of claim 8,
And intercepting the coquenice aspect data by receiving the coquenice containing the coquenice aspect data comprises receiving the coquenice by receiving a visual coquenice. The method of claim 8,
And intercepting the coquenice aspect data by receiving the coquenice containing the coquenice aspect data comprises receiving the coquenice by receiving an audio cocaineque. The method of claim 1,
One of the end user entity to indicate one or more aspects of the communeike directed to the end user entity and to conditionally obfuscate the communeike associated with the source entity, In accordance with the conditional instruction above, intercepting may include: maintaining the cochlenick aspect data at least temporarily, in accordance with the one or more conditional instructions, in order to prevent the cochlear aspect data from reaching the end user entity. And intercepting data. The method of claim 14,
In order to prevent the cocaine aspect data from reaching the end user entity, intercepting the cocaine aspect data by maintaining the cocaine aspect data, at least temporarily, in accordance with the one or more conditional instructions, the cocaine aspect data. And maintaining said Kochenike aspect data in memory at least temporarily without releasing it. 16. The method of claim 15,
Maintaining at least the cohenike aspect data in memory without releasing the cohenike aspect data may cause the co user to present the cohenike aspect data to the end user entity until at least one occurrence of at least one triggering event associated with the end user entity is determined. Maintaining the communeike aspect data in memory without releasing. The method of claim 16,
Maintaining the cocaine aspect data in memory without releasing the cocaine aspect data to the end user entity until determining the occurrence of one or more triggering events associated with the at least the end user entity comprises: at least the end of the end user entity And maintaining the communeike aspect data in memory without releasing the comoniket aspect data to the end user entity until a user obtains a verification that the user owns a communication device of the end user entity. Way. The method of claim 17,
Maintaining the communeike aspect data in memory without releasing the comonike aspect data to the end user entity until at least a verification that an end user of the end user entity owns the communication device of the end user entity, And maintaining the cocaineque aspect data in a memory without releasing the cocaineque aspect data to the end user entity until at least a password verification that verifies that the end user owns the communication device. . The method of claim 17,
Maintaining the communeike aspect data in memory without releasing the comonike aspect data to the end user entity until at least a verification that an end user of the end user entity owns the communication device of the end user entity, Maintaining the communique aspect data in memory without releasing the communike aspect data to the end user entity until at least the biometric verification that the end user owns the communication device is received. , Computer implemented method. 20. The method of claim 19,
Maintaining the communeike aspect data in a memory without releasing the comoniket aspect data to the end user entity until at least the end user receives a biometric verification that verifies that the end user owns the communication device. The cochlear aspect data in memory without releasing the cochlear aspect data to the end user entity until receiving at least one of retinal scan verification, face verification, voice verification, or fingerprint verification verifying that the user owns the communication device. And maintaining the computer-implemented method. The method of claim 16,
Maintaining the cocaine aspect data in memory without releasing the cocaine aspect data to the end user entity until determining the occurrence of one or more triggering events associated with the at least the end user entity comprises: at least communication of the end user entity And maintaining the communique aspect data in memory without releasing the communike aspect data to the end user entity until the device determines that the device is at one or more locations specified by the one or more conditional instructions. The method of claim 16,
Maintaining the cocaine aspect data in memory without releasing the cocaine aspect data to the end user entity until determining the occurrence of one or more triggering events associated with the at least the end user entity comprises: at least communication of the end user entity And maintaining the communeike aspect data in a memory without releasing the comoniket aspect data to the end user entity until a device determines that the device is outside one or more locations specified by the one or more conditional instructions. The method of claim 16,
Maintaining the cocaine aspect data in memory without releasing the cocaine aspect data to the end user entity until determining the occurrence of one or more triggering events associated with the at least the end user entity comprises: at least communication of the end user entity Maintaining the communeike aspect data in memory without releasing the comoniket aspect data to the end user entity until the device determines to be at one or more specific time intervals or points specified by the one or more conditional instructions; Computer implementation method. The method of claim 16,
Maintaining the cocaine aspect data in memory without releasing the cocaine aspect data to the end user entity until determining the occurrence of one or more triggering events associated with the at least the end user entity comprises: at least one or more conditional instructions. The co-Nike aspect data in memory without releasing the Co-Nike aspect data to the end-user entity until it is determined that one or more third parties specified are not within the proximate vicinity of the end-user entity's communication device. And maintaining the computer-implemented method. The method of claim 1,
One of the end user entity to indicate one or more aspects of the communeike directed to the end user entity and to conditionally obfuscate the communeike associated with the source entity, In accordance with any of the above conditional instructions, intercepting includes intercepting the Coquenice aspect data in accordance with the one or more conditional instructions by intercepting the Cohenike aspect data as a function of one or more environmental conditions of the communication device of the end user entity. Computer-implemented method. The method of claim 25,
The step of intercepting the Coeniket aspect data in accordance with the one or more conditional instructions by intercepting the Coeniket aspect data as a function of one or more environmental conditions of the communication device of the end user entity may comprise end user entity data provided by the communication device. Intercepting the Coquenice aspect data as a function of one or more environmental conditions indicated by. The method of claim 25,
The step of intercepting the coquenic aspect data in accordance with the one or more conditional instructions by intercepting the cocaine aspect data as a function of one or more environmental conditions of the communication device of the end user entity comprises: the communication specified by the one or more conditional instructions. Intercepting the Coquenice aspect data as a function of the location of a device. The method of claim 27,
Intercepting the communeike aspect data as a function of the location of the communication device specified by the one or more conditional instructions comprises determining that the communication device is at one or more specified locations specified by the one or more conditional instructions. In response to intercepting the communeike aspect data. The method of claim 25,
The step of intercepting the coquenic aspect data in accordance with the one or more conditional instructions by intercepting the cocaine aspect data as a function of one or more environmental conditions of the communication device of the end user entity comprises: the communication specified by the one or more conditional instructions. Intercepting the Coquenice aspect data as a function of time with respect to a device. The method of claim 29,
Intercepting the Coquenice aspect data as a function of time for the communication device specified by the one or more conditional instructions may comprise one or more of the days specified by the one or more conditional instructions with respect to the communication device. Intercepting the Coquenice aspect data at a specified time. The method of claim 29,
Intercepting the Coquenice aspect data as a function of time for the communication device specified by the one or more conditional instructions comprises: one of a calendar year specified for the communication device and specified by the one or more conditional instructions. Intercepting the Coquenice aspect data at the specified time above. The method of claim 25,
Intercepting the coquenic aspect data in accordance with the one or more conditional instructions by intercepting the coquenic aspect data as a function of one or more environmental conditions of the communication device of the end user entity, wherein the communication device intercepts the end user of the end user entity. Intercepting the Coquenice aspect data in accordance with the one or more conditional instructions by intercepting the Coquenice aspect data in response to determining that it is not owned. 33. The method of claim 32,
Intercepting the coquenice aspect data according to the one or more conditional instructions by intercepting the coquenice aspect data in response to determining that the communication device is not owned by an end user of the end user entity, wherein the end user intercepts Intercepting the Coquenice aspect data at least partially in response to determining that there is no verification of owning a device. The method of claim 33, wherein
Intercepting at least part of the Cohenike aspect data in response to determining that there is no verification that the end user owns the communication device comprises at least partially determining that there is no password verification that the end user owns the communication device. In response to intercepting the communeike aspect data. The method of claim 33, wherein
Intercepting the Coquenice aspect data at least partially in response to determining that the end user possesses no communication device, at least in part, determining that there is no biometric verification that the end user owns the communication device. And intercepting the Coquenice aspect data in response. 36. The method of claim 35,
Intercepting the communeike aspect data at least in part in response to determining that the end user owns the communication device does not include: retinal scan verification, face verification, voice that the end user owns the communication device Intercepting the communeike aspect data at least in part in response to determining that there is no at least one of verification, or fingerprint verification. The method of claim 25,
The step of intercepting the coquenic aspect data according to the one or more conditional instructions by intercepting the coquenic aspect data as a function of one or more environmental conditions of the communication device of the end user entity may include one or more specified conditional instructions. Intercepting the coquenice aspect data in accordance with the one or more conditional instructions by intercepting the coquenice aspect data at least partially in response to determining that a third party is within close proximity of the communication device. The method of claim 1,
One of the end user entity to indicate one or more aspects of the communeike directed to the end user entity and to conditionally obfuscate the communeike associated with the source entity, In accordance with the conditional instructions above, intercepting may further comprise intercepting the Cochlenick aspect data in response to at least partly determining that the Cochnicel aspect data includes data that associates the Cochnicike with the source entity. Intercepting the Coquenice aspect data. The method of claim 38,
Intercepting the coquenice aspect data in accordance with the one or more conditional instructions by intercepting the coquenice aspect data at least partially in response to determining that the coquenice aspect data includes data that associates the coquenice with the source entity. Intercepting the coquenic aspect data in response at least in part to determining that coquenic aspect data includes header data that associates the source entity with the coquenice. The method of claim 38,
Intercepting the coquenice aspect data in accordance with the one or more conditional instructions by intercepting the coquenice aspect data at least partially in response to determining that the coquenice aspect data includes data that associates the coquenice with the source entity. Intercepting the coquenice aspect data according to the one or more conditional instructions by intercepting the coquenice aspect data at least partially in response to determining that cocaine aspect data includes one or more representations of the source entity. Computer implementation method. The method of claim 40,
Intercepting the coquenice aspect data in accordance with the one or more conditional instructions by intercepting the coquenice aspect data at least partially in response to determining that the coquenice aspect data includes one or more representations of the source entity. Intercepting the coquenice aspect data in accordance with the one or more conditional instructions by intercepting the coquenice aspect data at least partially in response to determining that includes at least one name associated with the source entity. The method of claim 40,
Intercepting the coquenice aspect data in accordance with the one or more conditional instructions by intercepting the coquenice aspect data at least partially in response to determining that the coquenice aspect data includes one or more representations of the source entity. Intercepting the coquenice aspect data in accordance with the one or more conditional instructions by intercepting the coquenice aspect data at least partially in response to determining that includes at least one address associated with the source entity. The method of claim 40,
Intercepting the coquenice aspect data in accordance with the one or more conditional instructions by intercepting the coquenice aspect data at least partially in response to determining that the coquenice aspect data includes one or more representations of the source entity. Intercepting the coquenic aspect data according to the one or more conditional instructions by intercepting the coquenic aspect data at least partially in response to determining that includes at least a telephone number associated with the source entity. The method of claim 38,
Intercepting the coquenice aspect data in accordance with the one or more conditional instructions by intercepting the coquenice aspect data at least partially in response to determining that the coquenice aspect data includes data that associates the coquenice with the source entity. Intercepting the communike aspect data at least partially in response to determining that a source entity was the source for the communeike. The method of claim 1,
One of the end user entity to indicate one or more aspects of the communeike directed to the end user entity and to conditionally obfuscate the communeike associated with the source entity, In accordance with the conditional instructions above, intercepting includes intercepting the Coquenice aspect data at least in part in response to determining that the Coquenice is directed to the end user entity. The method of claim 45,
Intercepting the communeike aspect data at least partially in response to determining that the communeike is destined for the end user entity, at least partially in response to determining that the communeike is directed to a representation of the end user entity. Intercepting a computer-implemented method. 47. The method of claim 46 wherein
Intercepting at least part of the communike aspect data in response to determining that the communeike is directed to the representation of the end user entity, at least in part in response to determining that the communeike is directed to an address associated with the end user entity And intercepting communeike aspect data. The method of claim 47,
In response to at least partly determining that the cocaine is directed to an address associated with the end user entity, intercepting the cocaine aspect data may include an email address, an Internet Protocol (IP) address, or an IP address associated with the cocaine. Intercepting the communeike aspect data at least in part in response to determining to head to at least one of a Uniform Resource Locator (URL). 47. The method of claim 46 wherein
Intercepting at least in part the co-working aspect data in response to determining that the co-working force is directed to the representation of the end-user entity, at least in part in response to determining that the co-working force is directed to the telephone number associated with the end-user entity. Intercepting the Coquenice aspect data. 47. The method of claim 46 wherein
Intercepting the communeike aspect data at least in part in response to determining that the communeike is directed to a representation of the end user entity, at least in part in response to determining that the communeike is directed to a name associated with the end user entity And intercepting communeike aspect data. The method of claim 1,
One of the end user entity to indicate one or more aspects of the communeike directed to the end user entity and to conditionally obfuscate the communeike associated with the source entity, In accordance with the conditional instructions above, intercepting may intercept the Cochnicque aspect data in accordance with the one or more conditional instructions by intercepting the Cochnicque in response to determining that at least the Cochnyke is associated with and directed to the end user entity. Computer-implemented method. The method of claim 1,
One of the end user entity to indicate one or more aspects of the communeike directed to the end user entity and to conditionally obfuscate the communeike associated with the source entity, In accordance with any of the above conditional instructions, intercepting at least includes determining that the commune includes subject heading that includes one or more specific words or phrases specified by the one or more conditional instructions associated with the source entity. Intercepting the coquenic aspect data in accordance with the one or more conditional instructions by partially intercepting the coquenic aspect data. The method of claim 1,
In response to intercepting the cocaine aspect data, instead of sending a direct representation of the cocaine to the end user entity, the secret indicator data secretly representing the one or more aspects of the cocaine upon receipt by the end user entity. And transmitting to the end user entity comprises transmitting the secret indicator data over one or more communication networks. 54. The method of claim 53,
Transmitting the secret indicator data over the one or more communication networks comprises transmitting the secret indicator data to a communication device of the end user entity. 54. The method of claim 53,
Transmitting the secret indicator data over the one or more communication networks comprises transmitting the secret indicator data in a representation of an end user of the end user entity. 56. The method of claim 55,
Transmitting the secret indicator data to a representation of an end user of the end user entity comprises transmitting the secret indicator data to at least one of a name, address or telephone number associated with the end user. . The method of claim 1,
In response to intercepting the cocaine aspect data, instead of sending a direct representation of the cocaine to the end user entity, the secret indicator data secretly representing the one or more aspects of the cocaine upon receipt by the end user entity. Sending to the end user entity includes sending the secret indicator data to the end user entity in response to intercepting the coquenic aspect data, instead of sending all direct indications of the coquenice to the end user entity. Computer-implemented method. The method of claim 57,
In response to intercepting the coquenic aspect data, sending the secret indicator data to the end user entity instead of sending all direct representations of the coquenice to the end user entity, in response to intercepting the coquenic aspect data And sending the secret indicator data to the end user entity, instead of sending the coworker to the end user entity. The method of claim 57,
In response to intercepting the coquenic aspect data, sending the secret indicator data to the end user entity instead of sending all direct representations of the coquenice to the end user entity, in response to intercepting the coquenic aspect data And sending the secret indicator data to the end user entity, instead of sending the communeike data to the end user entity. The method of claim 57,
In response to intercepting the coquenic aspect data, sending the secret indicator data to the end user entity instead of sending all direct representations of the coquenice to the end user entity, in response to intercepting the coquenic aspect data And sending the secret indicator data to the end user entity, instead of sending the header type data associated with the coworker to the end user entity. 64. The method of claim 60,
In response to intercepting the coquenice aspect data, sending the secret indicator data to the end user entity, instead of sending the header-type data associated with the cocaineke to the end user entity, is further configured to intercept the coquenice aspect data. In response, the secret indicator data is sent to the end user entity, instead of transmitting to the end user entity the time of receipt of the cocaine, the subject of the cocaine, or any data that directly identifies the source entity associated with the cocaine. And transmitting to the computer-implemented method. The method of claim 1,
In response to intercepting the cocaine aspect data, instead of sending a direct representation of the cocaine to the end user entity, the secret indicator data secretly representing the one or more aspects of the cocaine upon receipt by the end user entity. Transmitting to an end user entity may cause the communication device to provide a secret indicator to secretly indicate one or more aspects of the commune to the end user of the end user entity when received by the communication device of the end user entity. Transmitting the secret indicator data by sending secret indicator data to the end user entity. 63. The method of claim 62,
When received by a communication device of the end user entity, the communication device provides secret indicator data to the end user entity to provide a secret indicator to the end user of the end user entity to secretly indicate one or more aspects of the communeke. Transmitting the secret indicator data by transmitting causes the communication device to provide a predetermined secret indicator known by the end user, when received by the communication device, to secretly indicate one or more aspects of the communeike. Transmitting the secret indicator data to the end user entity by sending predetermined data to the end user entity. The method of claim 63, wherein
Sending the predetermined data to the end user entity to cause the communication device to provide a predetermined secret indicator known by the end user, when received by the communication device, to secretly indicate one or more aspects of the communeke; Sending secret indicator data to the end user entity comprises transmitting the predetermined data to the end user entity defined at least in part by the conditional indication. 63. The method of claim 62,
When received by a communication device of the end user entity, the communication device provides secret indicator data to the end user entity to provide a secret indicator to the end user of the end user entity to secretly indicate one or more aspects of the communeke. Transmitting the secret indicator data by transmitting the secret indicator data when received by the communication device causes the communication device to provide a secret indicator that indirectly indicates to the end user the one or more aspects of the communeke. And transmitting the secret indicator data to the end user entity. 66. The method of claim 65,
The secret indicator data to the end user entity, the secret indicator data comprising secret indicator data that when received by the communication device causes the communication device to provide a secret indicator indirectly indicating to the end user the one or more aspects of the communeke. The transmitting may include secret indicator data when received by the communication device such that the communication device provides a secret audio indicator that audibly and indirectly indicates to the end user one or more aspects of the communique. And sending the secret indicator data to the end user entity by sending a. 67. The method of claim 66,
The secret by sending secret indicator data to the end user entity that, when received by the communication device, provide the secret audio indicator to audibly and indirectly indicate to the end user one or more aspects of the communeke. Transmitting indicator data to the end user entity includes at least a ping, ring (indirectly) indicating to the end user the one or more aspects of the communeke when received by the communication device. transmitting the secret indicator data to the end user entity by sending secret indicator data to the end user entity to provide an audible ring or hum. 67. The method of claim 66,
The secret by sending secret indicator data to the end user entity that, when received by the communication device, provide the secret audio indicator to audibly and indirectly indicate to the end user one or more aspects of the communeke. Transmitting indicator data to the end user entity includes, when received by the communication device, the communication device audibly outputs one or more simulated natural background noises that indirectly indicate to the end user the one or more aspects of the commune. And sending the secret indicator data to the end user entity by sending secret indicator data to the end user entity for providing. 67. The method of claim 66,
The secret by sending secret indicator data to the end user entity that, when received by the communication device, provide the secret audio indicator to audibly and indirectly indicate to the end user one or more aspects of the communeke. Transmitting indicator data to the end user entity includes, when received by the communication device, the communication device audibly displaying at least one voice message indirectly indicating to the end user the one or more aspects of the commune. And sending the secret indicator data to the end user entity by sending secret indicator data to the end user entity to provide. 70. The method of claim 69,
When received by the communication device, sends secret indicator data to the end user entity that causes the communication device to acoustically provide at least one voice message indirectly indicating to the end user the one or more aspects of the communeke. Thereby transmitting the secret indicator data to the end user entity, wherein the communication device, when received by the communication device, generates at least one voice indirectly indicating to the end user the one or more aspects of the communeke. And sending the secret indicator data to the end user entity by sending secret indicator data to the end user entity to provide an audible message. 70. The method of claim 69,
When received by the communication device, sends secret indicator data to the end user entity that causes the communication device to acoustically provide at least one voice message indirectly indicating to the end user the one or more aspects of the communeke. And thereby transmitting the secret indicator data to the end user entity includes at least one previously provided for the communication device to indirectly indicate to the end user the one or more aspects of the communeike when received by the communication device. Sending the secret indicator data to the end user entity by sending secret indicator data to the end user entity to provide an audible message to the end user entity. 72. The method of claim 71,
The end user providing secret indicator data to the end user, when received by the communication device, to audibly provide at least one voice message previously provided to indirectly display the one or more aspects of the co-working to the end user. Transmitting the secret indicator data to the end user entity by transmitting to the entity, previously provided by the communication device to indirectly indicate to the end user the one or more aspects of the communeike when received by the communication device. Transmitting the secret indicator data to the end user entity by sending secret indicator data to the end user entity to audibly provide the modified at least one voice message. Computer-implemented method. 66. The method of claim 65,
The secret indicator data to the end user entity, the secret indicator data comprising secret indicator data that when received by the communication device causes the communication device to provide a secret indicator indirectly indicating to the end user the one or more aspects of the communeke. And transmitting the secret user data to the end user entity such that when received by the communication device, the communication device provides a secret visual indicator that visually and indirectly indicates to the end user the one or more aspects of the commune. And sending the secret indicator data to the end user entity by sending a. The method of claim 73,
The secret by sending secret indicator data to the end user entity that, when received by the communication device, cause the communication device to provide a secret visual indicator that visually indirectly displays the one or more aspects of the communeke to the end user. Transmitting indicator data to the end user entity may include one or more visual symbols or icons that, when received by the communication device, cause the communication device to visually indirectly display the one or more aspects of the co-working to the end user. And sending the secret indicator data to the end user entity by sending secret indicator data to the end user entity to provide. The method of claim 73,
The secret by sending secret indicator data to the end user entity that, when received by the communication device, cause the communication device to provide a secret visual indicator that visually indirectly displays the one or more aspects of the communeke to the end user. Transmitting indicator data to the end user entity may include, when received by the communication device, the communication device to provide one or more specific colors that visually indirectly indicate to the end user the one or more aspects of the coquenic. And sending the secret indicator data to the end user entity by sending secret indicator data to the end user entity. The method of claim 73,
The secret by sending secret indicator data to the end user entity that, when received by the communication device, cause the communication device to provide a secret visual indicator that visually indirectly displays the one or more aspects of the communeke to the end user. Transmitting indicator data to the end user entity, when received by the communication device, provides the at least one visual message that the communication device visually indirectly indicates to the end user the one or more aspects of the commune. Transmitting the secret indicator data to the end user entity by sending secret indicator data to the end user entity. 80. The method of claim 76,
By transmitting secret indicator data to the end user entity that, when received by the communication device, cause the communication device to provide at least one visual message that visually indirectly displays the one or more aspects of the communeke to the end user. The sending of the secret indicator data to the end user entity may include one or more visual words that, when received by the communication device, cause the communication device to visually indirectly indicate to the end user the one or more aspects of the communeke or Sending the secret indicator data to the end user entity by sending secret indicator data to the end user entity to provide a phrase. 78. The method of claim 77 wherein
And when received by the communication device, to the end user entity secret indicator data to cause the communication device to provide one or more visual words or phrases that visually indirectly indicate to the end user the one or more aspects of the commune. Thereby transmitting the secret indicator data to the end user entity, wherein the communication device, when received by the communication device, visually indirectly displays the one or more aspects of the communeike to the end user. Transmitting the secret indicator data to the end user entity by sending secret indicator data to the end user entity to provide a word or phrase in a particular font or style. , Computer implemented method. 80. The method of claim 76,
By transmitting secret indicator data to the end user entity that, when received by the communication device, cause the communication device to provide at least one visual message that visually indirectly displays the one or more aspects of the communeke to the end user. The sending of the secret indicator data to the end user entity may comprise: a visual message previously provided such that when received by the communication device the communication device visually indirectly displays the one or more aspects of the communeike to the end user. And sending the secret indicator data to the end user entity by sending secret indicator data to the end user entity to provide a. 80. The method of claim 79,
By sending to the end user entity secret indicator data that, when received by the communication device, cause the communication device to provide a previously provided visual message to visually indirectly display the one or more aspects of the co-working to the end user. Transmitting the secret indicator data to the end user entity may be previously provided and modified to cause the communication device to visually indirectly display to the end user the one or more aspects of the commune when received by the communication device. Transmitting the secret indicator data to the end user entity by sending secret indicator data to the end user entity to provide a visual message. 66. The method of claim 65,
The secret indicator data to the end user entity, the secret indicator data comprising secret indicator data that when received by the communication device causes the communication device to provide a secret indicator indirectly indicating to the end user the one or more aspects of the communeke. The transmitting may include the secret indicator data, when received by the communication device, to provide the secret indicator data to indirectly indicate the one or more aspects of the communeike to the end user via a particular vibration. Transmitting the secret indicator data to the end user entity by transmitting to a user entity. The method of claim 1,
In response to intercepting the cocaine aspect data, instead of sending a direct representation of the cocaine to the end user entity, the secret indicator data secretly representing the one or more aspects of the cocaine upon receipt by the end user entity. Transmitting to the end user entity comprises transmitting the secret indicator data to the end user entity by transmitting to the end user entity secret indicator data that does not at least directly identify the source entity. . 83. The method of claim 82,
Sending the secret indicator data to the end user entity by sending secret indicator data to the end user entity that does not at least directly identify the source entity comprises at least directly the source entity as a source for the co-working. Transmitting the secret indicator data to the end user entity by sending unidentified secret indicator data to the end user entity. 83. The method of claim 82,
Sending the secret indicator data to the end user entity by sending secret indicator data to the end user entity that does not at least directly identify the source entity, wherein the secret indicator does not include any representation of the source entity. Transmitting the secret indicator data to the end user entity by sending data to the end user entity. 85. The method of claim 84,
Sending the secret indicator data to the end user entity by sending secret indicator data to the end user entity that does not include any representation of the source entity, includes any name, address or telephone number associated with the source entity. Transmitting the secret indicator data to the end user entity by sending secret indicator data to the end user entity that does not include. 85. The method of claim 84,
Sending the secret indicator data to the end user entity by sending secret indicator data to the end user entity that does not include any representation of the source entity further comprises one or more temporary representations of one or more representations of the source entity. sending the secret indicator data to the end user entity by sending secret indicator data to the end user entity. 87. The method of claim 86,
Sending the secret indicator data to the end user entity by sending secret indicator data to the end user entity including one or more temporary representations of one or more representations of the source entity may include one or more names associated with the source entity. Sending the secret indicator data to the end user entity by sending secret indicator data to the end user entity comprising one or more substitutes for the end user entity. 87. The method of claim 86,
Sending the secret indicator data to the end user entity by sending secret indicator data to the end user entity including one or more temporary surrogates for one or more representations of the source entity, wherein the one or more addresses associated with the source entity include: And sending the secret indicator data to the end user entity by sending secret indicator data to the end user entity comprising one or more substitutes for the end user entity. 87. The method of claim 86,
Sending the secret indicator data to the end user entity by sending secret indicator data to the end user entity including one or more temporary surrogates for one or more representations of the source entity, wherein the at least one associated with the source entity comprises: Transmitting the secret indicator data to the end user entity by sending secret indicator data to the end user entity comprising at least one substitute for a telephone number. 83. The method of claim 82,
Sending the secret indicator data to the end user entity by sending secret indicator data to the end user entity that does not at least directly identify the source entity comprises at least secret secret data not to directly identify the communeike. Transmitting the secret indicator data to the end user entity by sending to the end user entity. 91. The method of claim 90,
The step of transmitting the secret indicator data to the end user entity by sending secret indicator data to the end user entity that does not at least directly identify the cocaine may include at least a secret that does not directly identify a subject for the cocaine. And sending the secret indicator data to the end user entity by sending indicator data to the end user entity. The method of claim 1,
In response to intercepting the cocaine aspect data, instead of sending a direct representation of the cocaine to the end user entity, the secret indicator data secretly representing the one or more aspects of the cocaine upon receipt by the end user entity. Sending to the end user entity by sending secret indicator data in the form of header data to the end user entity. The method of claim 1,
In response to intercepting the cocaine aspect data, instead of sending a direct representation of the cocaine to the end user entity, the secret indicator data secretly representing the one or more aspects of the cocaine upon receipt by the end user entity. And transmitting to the end user entity the transmitting of the secret indicator data to the end user entity by transmitting to the end user entity a list of one or more received coworkers including the secret indicator data. Way. 94. The method of claim 93,
Transmitting the secret indicator data to the end user entity by sending a list of one or more received co-workikes containing the secret indicator data to the end user entity, wherein the one or more temporary representations of one or more representations of the source entity And sending said list of one or more received cocaniques to said end user entity by sending said list of one or more received cocaniques to said end user entity. . The method of claim 1,
Receiving the one or more conditional instructions from the end user entity
Computer implemented method further comprising. 97. The method of claim 95,
Receiving the one or more conditional instructions from the end user entity comprises requesting the one or more conditional instructions from the end user entity. 97. The method of claim 96,
Requesting the one or more conditional instructions from the end user entity comprises sending one or more requests for the one or more conditional instructions to the end user entity. Conditionally obfuscate the communike aspect data associated with a particular source entity and indicate one or more aspects of the communique directed to the end user entity and towards the end user entity. Circuitry for intercepting, in accordance with one or more conditional indications of the end user entity; And
In response to intercepting the cocaine aspect data, instead of sending a direct representation of the cocaine to the end user entity, the secret indicator data secretly representing the one or more aspects of the cocaine upon receipt by the end user entity. Circuitry for transmitting to end-user entities
Computer implemented system comprising a. 99. The method of claim 98,
One of the end user entity to indicate one or more aspects of the communeike directed to the end user entity and to conditionally obfuscate the communeike associated with the source entity, In accordance with the conditional instructions above, the circuitry for intercepting includes circuitry for intercepting the Corsonike aspect data at a network device. 105. The method of claim 99,
Circuitry for intercepting the Cokenike aspect data at the network device comprises circuitry for intercepting the Cokenike aspect data at the network device located at one or more network sites. 101. The method of claim 100,
Circuitry for intercepting the Coeniket aspect data at the network device located at the one or more network sites comprises at least one network server located at the at least one network site for intercepting the Coeniket aspect data at the network device. Computer implemented system comprising circuitry. 102. The method of claim 101, wherein
Circuitry for intercepting the Coeniket aspect data in the network device that includes one or more network servers located in the one or more network sites, circuitry for intercepting the Coeniket aspect data in the network device that includes at least one router. A computer implemented system comprising a. 102. The method of claim 101, wherein
Circuitry for intercepting the Coeniket aspect data at the network device comprising at least one network server located at the at least one network site, includes at least a telephone switch or telephone switch to intercept the Coeniket aspect data at the network device. Computer-implemented system comprising circuitry. 99. The method of claim 98,
One of the end user entity to indicate one or more aspects of the communeike directed to the end user entity and to conditionally obfuscate the communeike associated with the source entity, In accordance with the conditional instructions above, the circuitry for intercepting includes circuitry for intercepting the Corsonike aspect data by intercepting Cochenike aspect data received via one or more communication networks. 99. The method of claim 98,
One of the end user entity to indicate one or more aspects of the communeike directed to the end user entity and to conditionally obfuscate the communeike associated with the source entity, And in accordance with the conditional instructions above, the circuitry for intercepting includes circuitry for intercepting the coquenice aspect data by receiving the coquenice containing the coquenice aspect data. 105. The method of claim 105,
Circuitry for intercepting the coquenice aspect data by receiving the coquenice containing the coquenice aspect data comprises circuitry for receiving the coquenice by receiving a coquenice that includes the coquenice aspect data in a header data form. Implementation system. 105. The method of claim 105,
Circuitry for intercepting the coquenice aspect data by receiving the coquenice containing the coquenice aspect data, receives the coquenice by receiving a coquenice that includes the coquenice aspect data embedded in a ringing signal of the coquenice. Computer-implemented system comprising circuitry. 105. The method of claim 105,
And circuitry for intercepting the kokeniket aspect data by receiving the kokeniket containing the kokeniket aspect data comprises circuitry for intercepting the kokeniket aspect data by extracting the kokeniket aspect data from the kokeniket. 105. The method of claim 105,
Circuitry for intercepting the coquenice aspect data by receiving the coquenice data that includes the coquenice aspect data comprises circuitry for receiving the coquenice by receiving a visual coquenice. 105. The method of claim 105,
Circuitry for intercepting the coquenice aspect data by receiving the coquenice data that includes the coquenice aspect data comprises circuitry for receiving the coquenice by receiving an audio coquenice. 99. The method of claim 98,
One of the end user entity to indicate one or more aspects of the communeike directed to the end user entity and to conditionally obfuscate the communeike associated with the source entity, In accordance with the conditional instruction above, the circuitry for intercepting may maintain the cochnicike aspect data by, at least temporarily, maintaining the cochnicike aspect data in accordance with the one or more conditional instructions in order to prevent the cochlear aspect data from reaching the end user entity. And circuitry for intercepting aspect data. 112. The method of claim 111, wherein
The circuitry for intercepting the Kokenike aspect data by maintaining the Kokenike aspect data, at least temporarily, in accordance with the one or more conditional instructions, to prevent the Kokenike aspect data from reaching the end user entity, And circuitry for retaining the Corniche aspect data in memory at least temporarily without releasing data. 112. The method of claim 112,
Circuitry for retaining the cochlenick aspect data at least temporarily in memory without releasing the cochlear aspect data is further configured to communicate the cochlenick aspect data to the end user entity until at least one occurrence of one or more triggering events associated with the end user entity is determined. And circuitry for maintaining the communeike aspect data in a memory without releasing it. 113. The method of claim 113,
The circuitry for maintaining the communeike aspect data in memory without releasing the comoniket aspect data to the end user entity until determining occurrence of one or more triggering events associated with the at least the end user entity comprises: And circuitry for maintaining the communique aspect data in memory without releasing the communike aspect data to the end user entity until a verification is obtained that an end user owns the communication device of the end user entity; Computer implemented system. 119. The method of claim 114,
Circuitry for maintaining the communeike aspect data in memory without releasing the comonike aspect data to the end user entity until at least a verification that an end user of the end user entity owns the communication device of the end user entity is obtained. And circuitry for maintaining the communeike aspect data in memory without releasing the comoniket aspect data to the end user entity until at least a password verification verifying that the end user owns the communication device is received. Implementation system. 119. The method of claim 114,
Circuitry for maintaining the communeike aspect data in memory without releasing the comonike aspect data to the end user entity until at least a verification that an end user of the end user entity owns the communication device of the end user entity is obtained. Circuitry for maintaining the communique aspect data in memory without releasing the communike aspect data to the end user entity until at least a biometric verification is received that verifies that the end user owns the communication device. Computer-implemented system. 116. The method of claim 116 wherein
The circuitry for maintaining the communeike aspect data in memory without releasing the comoniket aspect data to the end user entity until receiving at least the biometric verification verifying that the end user owns the communication device comprises: The communeike aspect in memory without releasing the comoniket aspect data to the end user entity until an end user receives at least one of retinal scan verification, face verification, voice verification, or fingerprint verification verifying that he owns the communication device. A computer implemented system comprising circuitry for holding data. 113. The method of claim 113,
The circuitry for maintaining the communeike aspect data in memory without releasing the comoniket aspect data to the end user entity until determining occurrence of one or more triggering events associated with the at least the end user entity comprises: Computer-implemented circuitry for maintaining the co-working aspect data in memory without releasing the co-working aspect data to the end-user entity until it determines that the communication device is at one or more locations specified by the one or more conditional instructions. system. 113. The method of claim 113,
The circuitry for maintaining the communeike aspect data in memory without releasing the comoniket aspect data to the end user entity until determining occurrence of one or more triggering events associated with the at least the end user entity comprises: Computer-implemented circuitry for maintaining the cochlenick aspect data in a memory without releasing the cochlenick aspect data to the end user entity until a communication device determines that it is outside one or more locations specified by the one or more conditional instructions. system. 113. The method of claim 113,
The circuitry for maintaining the communeike aspect data in memory without releasing the comoniket aspect data to the end user entity until determining occurrence of one or more triggering events associated with the at least the end user entity comprises: And circuitry for maintaining the cochlenick aspect data in memory without releasing the cochlenick aspect data to the end user entity until the communication device determines that it is at one or more specific time intervals or points specified by the one or more conditional instructions. Computer implemented system. 113. The method of claim 113,
The circuitry for maintaining the co-working aspect data in memory without releasing the co-working aspect data to the end-user entity until determining the occurrence of one or more triggering events associated with the at least the end-user entity includes: The coquenic aspect in memory without releasing the cocaine aspect data to the end user entity until it is determined that one or more third parties specified by are not within the proximate vicinity of the end user entity's communication device. A computer implemented system comprising circuitry for holding data. 99. The method of claim 98,
One of the end user entity to indicate one or more aspects of the communeike directed to the end user entity and to conditionally obfuscate the communeike associated with the source entity, In accordance with the conditional instruction above, circuitry for intercepting circuitry for intercepting the Cochlenick aspect data in accordance with the one or more conditional instructions by intercepting the Cokenike aspect data as a function of one or more environmental conditions of the communication device of the end user entity. A computer implemented system comprising a. 123. The method of claim 122 wherein
Circuitry for intercepting the cochleque aspect data in accordance with the one or more conditional instructions by intercepting the cochlear aspect data as a function of one or more environmental conditions of the communication device of the end user entity is provided by the end user entity. And circuitry for intercepting the Coquenice aspect data as a function of one or more environmental conditions represented by data. 123. The method of claim 122 wherein
The circuitry for intercepting the coquenique aspect data in accordance with the one or more conditional instructions by intercepting the coquenic aspect data as a function of one or more environmental conditions of the communication device of the end user entity comprises: And circuitry for intercepting the Corniche aspect data as a function of a location of a communication device. 124. The method of claim 124 wherein
Circuitry for intercepting the Coquenice aspect data as a function of the location of the communication device specified by the one or more conditional instructions determines that the communication device is at one or more specified locations specified by the one or more conditional instructions. And circuitry for intercepting the Coquenice aspect data in response. 123. The method of claim 122 wherein
The circuitry for intercepting the coquenique aspect data in accordance with the one or more conditional instructions by intercepting the coquenic aspect data as a function of one or more environmental conditions of the communication device of the end user entity comprises: And circuitry for intercepting the Corniche aspect data as a function of time for a communication device. 126. The method of claim 126, wherein
Circuitry for intercepting the Cokenike aspect data as a function of time for the communication device specified by the one or more conditional instructions is one of the days specified by the one or more conditional instructions with respect to the communication device. And circuitry for intercepting the Coquenice aspect data at the specified time above. 126. The method of claim 126, wherein
Circuitry for intercepting the Coquenice aspect data as a function of time with respect to the communication device specified by the one or more conditional instructions is characterized by a calendar year specified by the one or more conditional instructions with respect to the communication device. And circuitry for intercepting the Coquenice aspect data at one or more specified times. 123. The method of claim 122 wherein
Circuitry for intercepting the coquenic aspect data in accordance with the one or more conditional instructions by intercepting the cocaine aspect data as a function of one or more environmental conditions of the communication device of the end user entity, wherein the communication device is capable of intercepting the end of the end user entity And circuitry for intercepting the coquenic aspect data in accordance with the one or more conditional instructions by intercepting the coquenic aspect data in response to determining not owned by a user. 129. The method of claim 129 wherein
Circuitry for intercepting the coquenic aspect data in accordance with the one or more conditional instructions by intercepting the coquenic aspect data in response to determining that the communication device is not owned by an end user of the end user entity, wherein the end user And circuitry for intercepting the Coquenice aspect data at least partially in response to determining that there is no verification of owning a communication device. 131. The method of claim 130,
Circuitry for intercepting the Coquenice aspect data at least partially in response to determining that there is no verification that the end user owns the communication device is at least partially in determining that there is no password verification that the end user owns the communication device. And circuitry for intercepting the Coquenice aspect data in response. 131. The method of claim 130,
Circuitry for intercepting the Coquenice aspect data at least partially in response to determining that there is no verification that the end user owns the communication device comprises at least one determining that there is no biometric verification that the end user owns the communication device. And circuitry for intercepting the Coquenice aspect data in part. 133. The method of claim 132,
Circuitry for intercepting the Coquenice aspect data in response at least in part to determining that there is no biometric verification that the end user owns the communication device includes retinal scan verification, face verification, And circuitry for intercepting the Coquenice aspect data in response at least in part to determining that at least one of voice verification or fingerprint verification is absent. 123. The method of claim 122 wherein
Circuitry for intercepting the cochlequet aspect data according to the one or more conditional instructions by intercepting the cochlear aspect data as a function of one or more environmental conditions of the communication device of the end user entity is one specified by the one or more conditional instructions. And circuitry for intercepting the Coquenice aspect data in accordance with the one or more conditional instructions by intercepting the Coquenice aspect data at least partially in response to determining that a third party is within close proximity of the communication device. 99. The method of claim 98,
One of the end user entity to indicate one or more aspects of the communeike directed to the end user entity and to conditionally obfuscate the communeike associated with the source entity, In accordance with the conditional instructions above, the circuitry for intercepting the intercepts the at least one conditional indication by intercepting the at least one conditional coherence aspect data in response to at least partly determining that the at least one coordinator aspect data includes data linking the at least one coordinator with the source entity. And circuitry for intercepting the Coquenice aspect data accordingly. 137. The method of claim 135,
Circuitry for intercepting the coquenice aspect data in accordance with the one or more conditional instructions by intercepting the coquenice aspect data at least partially in response to determining that the coquenice aspect data includes data that associates the coquette with the source entity; And circuitry for intercepting the Kokenike aspect data in response at least in part to determining that the Kokenike aspect data includes header data that associates the source entity with the Kokenike. 137. The method of claim 135,
Circuitry for intercepting the coquenice aspect data in accordance with the one or more conditional instructions by intercepting the coquenice aspect data at least partially in response to determining that the coquenice aspect data includes data that associates the coquette with the source entity; And circuitry for intercepting the coquenice aspect data in accordance with the one or more conditional instructions by intercepting the coquenice aspect data at least partially in response to determining that the coquenice aspect data includes one or more representations of the source entity. Computer implemented system. 138. The method of claim 137,
Circuitry for intercepting the cochlenick aspect data in accordance with the one or more conditional instructions by intercepting the cochlenick aspect data at least in part in response to determining that the cochnice aspect data includes one or more representations of the source entity comprises: And circuitry for intercepting the coquenic aspect data in accordance with the one or more conditional instructions by intercepting the coquenic aspect data at least partially in response to determining that data includes at least one name associated with the source entity. system. 138. The method of claim 137,
Circuitry for intercepting the cochlenick aspect data in accordance with the one or more conditional instructions by intercepting the cochlenick aspect data at least in part in response to determining that the cochnice aspect data includes one or more representations of the source entity comprises: And circuitry for intercepting the coquenic aspect data in accordance with the one or more conditional instructions by intercepting the coquenic aspect data at least partially in response to determining that data includes at least one address associated with the source entity. system. 138. The method of claim 137,
Circuitry for intercepting the cochlenick aspect data in accordance with the one or more conditional instructions by intercepting the cochlenick aspect data at least in part in response to determining that the cochnice aspect data includes one or more representations of the source entity comprises: And circuitry for intercepting the coquenic aspect data in accordance with the one or more conditional instructions by intercepting the coquenic aspect data at least partially in response to determining that data includes at least a telephone number associated with the source entity. . 137. The method of claim 135,
Circuitry for intercepting the coquenice aspect data in accordance with the one or more conditional instructions by intercepting the coquenice aspect data at least partially in response to determining that the coquenice aspect data includes data that associates the coquette with the source entity; And circuitry for intercepting the Coquenice aspect data in at least part in response to determining that the source entity was a source for the Coquenice. 99. The method of claim 98,
One of the end user entity to indicate one or more aspects of the communeike directed to the end user entity and to conditionally obfuscate the communeike associated with the source entity, In accordance with the conditional instructions above, circuitry for intercepting includes circuitry for intercepting the Coquenice aspect data in response at least in part to determining that the Coquenice is directed to the end user entity. 143. The method of claim 142, wherein
Circuitry for intercepting the coquenice aspect data in response at least in part to determining that the coquenice is destined for the end user entity, wherein the circuit for intercepting the coquenice is directed to the representation of the end user entity And a circuit for intercepting data. 143. The method of claim 143 wherein
Circuitry for intercepting the coquenice aspect data in response at least in part to determining that the coquenice is directed to a representation of the end user entity, at least in part in response to determining that the coquenice is directed to an address associated with the end user entity And circuitry for intercepting the Coquenice aspect data. 145. The method of claim 144 wherein
Circuitry for intercepting the communicator aspect data in response at least in part to determining that the cocaine is directed to an address associated with the end user entity includes: an email address, an Internet Protocol (IP) address, Or circuitry for intercepting the Cohenike aspect data in response at least in part to determining to head to at least one of a Uniform Resource Locator (URL). 143. The method of claim 143 wherein
Circuitry for intercepting the coquenice aspect data in response at least in part to determining that the coquenice is directed to the representation of the end user entity is at least partially in determining that the coquenice is directed to the telephone number associated with the end user entity. And circuitry for receptively intercepting the Kokenike aspect data. 143. The method of claim 143 wherein
Circuitry for intercepting the coquenice aspect data at least partially in response to determining that the coquenice is directed to the representation of the end user entity, at least in part in response to determining that the coquenice is directed to a name associated with the end user entity And circuitry for intercepting the Coquenice aspect data. 99. The method of claim 98,
One of the end user entity to indicate one or more aspects of the communeike directed to the end user entity and to conditionally obfuscate the communeike associated with the source entity, In accordance with the conditional instructions above, the circuitry for intercepting intercepts the coquenice in accordance with the one or more conditional instructions by intercepting the coquenice at least in response to determining that the cocaine is associated with and directed to the end user entity. And a circuit for intercepting. 99. The method of claim 98,
One of the end user entity to indicate one or more aspects of the communeike directed to the end user entity and to conditionally obfuscate the communeike associated with the source entity, In accordance with the conditional instructions above, the circuitry for intercepting may be further configured to determine that the communeike includes a subject heading that includes one or more specific words or phrases specified by the one or more conditional instructions associated with the source entity. And circuitry for intercepting the Kochenike aspect data in accordance with the one or more conditional instructions by intercepting the Kokenike aspect data at least partially. 99. The method of claim 98,
In response to intercepting the cocaine aspect data, instead of sending a direct representation of the cocaine to the end user entity, the secret indicator data secretly representing the one or more aspects of the cocaine upon receipt by the end user entity. Circuitry for transmitting to an end user entity comprises circuitry for transmitting the secret indicator data over one or more communication networks. 151. The method of claim 150,
Circuitry for transmitting the secret indicator data over the one or more communication networks comprises circuitry for transmitting the secret indicator data to a communication device of the end user entity. 151. The method of claim 150,
Circuitry for transmitting the secret indicator data over the one or more communication networks comprises circuitry for transmitting the secret indicator data in a representation of an end user of the end user entity. 152. The method of claim 152,
Circuitry for transmitting the secret indicator data to a representation of an end user of the end user entity includes circuitry for transmitting the secret indicator data to at least one of a name, address or telephone number associated with the end user. Implementation system. 99. The method of claim 98,
In response to intercepting the cocaine aspect data, instead of sending a direct representation of the cocaine to the end user entity, the secret indicator data secretly representing the one or more aspects of the cocaine upon receipt by the end user entity. Circuitry for sending to an end user entity circuitry for sending the secret indicator data to the end user entity, in response to intercepting the coquenic aspect data, instead of sending all direct indications of the coquenice to the end user entity. A computer implemented system comprising a. 154. The method of claim 154, wherein
In response to intercepting the coquenic aspect data, the circuitry for transmitting the secret indicator data to the end user entity, instead of sending all direct indications of the coquenice to the end user entity, is configured to intercept the coquenic aspect data. In response, comprising circuitry for sending the secret indicator data to the end user entity, instead of sending the communeke to the end user entity. 154. The method of claim 154, wherein
In response to intercepting the coquenic aspect data, the circuitry for transmitting the secret indicator data to the end user entity, instead of sending all direct indications of the coquenice to the end user entity, is configured to intercept the coquenic aspect data. In response, including circuitry for sending the secret indicator data to the end user entity, instead of sending the co-Onique aspect data to the end user entity. 154. The method of claim 154, wherein
In response to intercepting the coquenic aspect data, the circuitry for transmitting the secret indicator data to the end user entity, instead of sending all direct indications of the coquenice to the end user entity, is configured to intercept the coquenic aspect data. And, in response, comprise circuitry for sending the secret indicator data to the end user entity, instead of sending the header-like data associated with the coworker to the end user entity. 161. The method of claim 157,
In response to intercepting the Coquenice aspect data, circuitry for transmitting the secret indicator data to the end user entity, instead of transmitting the header-type data associated with the Coquenice to the end user entity, intercepts the Coquenice aspect data. In response, sending the secret indicator data to the end user, instead of transmitting to the end user entity the time of receipt of the co-working, the subject of the co-working, or any data directly identifying the source entity associated with the co-working. And circuitry for transmitting to the entity. 99. The method of claim 98,
In response to intercepting the cocaine aspect data, instead of sending a direct representation of the cocaine to the end user entity, the secret indicator data secretly representing the one or more aspects of the cocaine upon receipt by the end user entity. The circuitry for transmitting to the end user entity is such that the communication device, when received by the communication device of the end user entity, provides the secret indicator to secretly indicate one or more aspects of the commune to the end user of the end user entity. And circuitry for transmitting the secret indicator data by sending secret indicator data to the end user entity. 161. The method of claim 159,
When received by a communication device of the end user entity, the communication device provides secret indicator data to the end user entity to provide a secret indicator to the end user of the end user entity to secretly indicate one or more aspects of the communeke. Circuitry for transmitting the secret indicator data by transmitting causes the communication device to provide a predetermined secret indicator known by the end user that, when received by the communication device, secretly indicates one or more aspects of the communeike. And circuitry for sending the secret indicator data to the end user entity by sending predetermined data to the end user entity. 161. The method of claim 160,
Sending the predetermined data to the end user entity to cause the communication device to provide a predetermined secret indicator known by the end user, when received by the communication device, to secretly indicate one or more aspects of the communeke; Circuitry for transmitting secret indicator data to the end user entity includes circuitry for transmitting the predetermined data to the end user entity defined at least in part by the conditional indication. 161. The method of claim 159,
When received by a communication device of the end user entity, the communication device provides secret indicator data to the end user entity to provide a secret indicator to the end user of the end user entity to secretly indicate one or more aspects of the communeke. Circuitry for transmitting the secret indicator data by transmitting causes the communication device to provide a secret indicator indirectly indicating to the end user the one or more aspects of the commune when received by the communication device. And circuitry for sending the secret indicator data to the end user entity. 162. The method of claim 162,
The secret indicator data to the end user entity, the secret indicator data comprising secret indicator data that when received by the communication device causes the communication device to provide a secret indicator indirectly indicating to the end user the one or more aspects of the communeke. The circuitry for transmitting may include secret indicator data when received by the communication device such that the communication device provides a secret audio indicator that audibly and indirectly indicates to the end user one or more aspects of the commune. And circuitry for transmitting the secret indicator data to the end user entity by transmitting to an entity. 163. The method of claim 163 wherein
The secret by sending secret indicator data to the end user entity that, when received by the communication device, provide the secret audio indicator to audibly and indirectly indicate to the end user one or more aspects of the communeke. Circuitry for transmitting indicator data to the end user entity includes at least a ping, a ring, when received by the communication device, the communication device indirectly indicating to the end user the one or more aspects of the coworker. and circuitry for transmitting the secret indicator data to the end user entity by sending secret indicator data to the end user entity to provide a ring or hum to the end user entity. 163. The method of claim 163 wherein
The secret by sending secret indicator data to the end user entity that, when received by the communication device, provide the secret audio indicator to audibly and indirectly indicate to the end user one or more aspects of the communeke. The circuitry for transmitting indicator data to the end user entity is further configured to: listen for one or more simulated natural background noises, when received by the communication device, that the communication device indirectly indicates to the end user the one or more aspects of the commune. And circuitry for transmitting the secret indicator data to the end user entity by sending secret indicator data to the end user entity to provide it to the end user entity. 163. The method of claim 163 wherein
The secret by sending secret indicator data to the end user entity that, when received by the communication device, provide the secret audio indicator to audibly and indirectly indicate to the end user one or more aspects of the communeke. The circuitry for transmitting indicator data to the end user entity is further configured such that the communication device, when received by the communication device, at least one voice message indirectly indicating to the end user the one or more aspects of the commune. And circuitry for transmitting the secret indicator data to the end user entity by sending secret indicator data to the end user entity for providing. 167. The method of claim 166,
When received by the communication device, sends secret indicator data to the end user entity that causes the communication device to acoustically provide at least one voice message indirectly indicating to the end user the one or more aspects of the communeke. Circuitry for transmitting the secret indicator data to the end user entity, such that the communication device, when received by the communication device, is configured to indirectly indicate to the end user the one or more aspects of the communeke. And circuitry for sending the secret indicator data to the end user entity by sending secret indicator data to the end user entity to provide an audible message to the end user entity. 167. The method of claim 166,
When received by the communication device, sends secret indicator data to the end user entity that causes the communication device to acoustically provide at least one voice message indirectly indicating to the end user the one or more aspects of the communeke. Circuitry for transmitting the secret indicator data to the end user entity by means of at least one previously provided for the communication device to indirectly indicate to the end user the one or more aspects of the commune when received by the communication device. And circuitry for transmitting the secret indicator data to the end user entity by sending secret indicator data to the end user entity to audibly provide a voice message of the end user entity. . 168. The method of claim 168,
The end user providing secret indicator data to the end user, when received by the communication device, to audibly provide at least one voice message previously provided to indirectly display the one or more aspects of the co-working to the end user. Circuitry for transmitting the secret indicator data to the end user entity by transmitting to an entity may be further configured to cause the communication device to indirectly indicate to the end user the one or more aspects of the commune when received by the communication device. Circuitry for transmitting the secret indicator data to the end user entity by transmitting secret indicator data to the end user entity to provide an audited at least one voice message provided and modified. Also, a computer-implemented system. 162. The method of claim 162,
The secret indicator data to the end user entity, the secret indicator data comprising secret indicator data that when received by the communication device causes the communication device to provide a secret indicator indirectly indicating to the end user the one or more aspects of the communeke. Circuitry for transmitting may include secret indicator data when received by the communication device, the communication device providing a secret visual indicator that visually and indirectly indicates to the end user the one or more aspects of the communeke. And circuitry for transmitting the secret indicator data to the end user entity by transmitting to an entity. 172. The method of claim 170,
The secret by sending secret indicator data to the end user entity that, when received by the communication device, cause the communication device to provide a secret visual indicator that visually indirectly displays the one or more aspects of the communeke to the end user. Circuitry for transmitting indicator data to the end user entity may include one or more visual symbols or icons that, when received by the communication device, cause the communication device to visually indirectly display to the end user the one or more aspects of the commune. And circuitry for transmitting the secret indicator data to the end user entity by sending secret indicator data to the end user entity. 172. The method of claim 170,
The secret by sending secret indicator data to the end user entity that, when received by the communication device, cause the communication device to provide a secret visual indicator that visually indirectly displays the one or more aspects of the communeke to the end user. Circuitry for transmitting indicator data to the end user entity provides one or more specific colors that, when received by the communication device, cause the communication device to visually indirectly indicate to the end user the one or more aspects of the commune. And circuitry for transmitting the secret indicator data to the end user entity by sending secret indicator data to the end user entity. 172. The method of claim 170,
The secret by sending secret indicator data to the end user entity that, when received by the communication device, cause the communication device to provide a secret visual indicator that visually indirectly displays the one or more aspects of the communeke to the end user. Circuitry for sending indicator data to the end user entity may include at least one visual message that, when received by the communication device, causes the communication device to visually indirectly indicate to the end user the one or more aspects of the commune. And circuitry for transmitting the secret indicator data to the end user entity by sending secret indicator data to the end user entity to provide. 174. The method of claim 173, wherein
By transmitting secret indicator data to the end user entity that, when received by the communication device, cause the communication device to provide at least one visual message that visually indirectly displays the one or more aspects of the communeke to the end user. Circuitry for transmitting the secret indicator data to the end user entity includes one or more visual words that, when received by the communication device, cause the communication device to visually indirectly indicate to the end user the one or more aspects of the commune. Or circuitry for sending the secret indicator data to the end user entity by sending secret indicator data to the end user entity to provide a phrase. 174. The method of claim 174, wherein
And when received by the communication device, to the end user entity secret indicator data to cause the communication device to provide one or more visual words or phrases that visually indirectly indicate to the end user the one or more aspects of the commune. Circuitry for transmitting the secret indicator data to the end user entity, such that the communication device visually indirectly displays to the end user the one or more aspects of the commune when received by the communication device. Circuitry for transmitting the secret indicator data to the end user entity by sending secret indicator data to the end user entity to provide visual words or phrases in a particular font or style. The computer-implemented system, comprising. 174. The method of claim 173, wherein
By transmitting secret indicator data to the end user entity that, when received by the communication device, cause the communication device to provide at least one visual message that visually indirectly displays the one or more aspects of the communeke to the end user. Circuitry for transmitting the secret indicator data to the end user entity may include a previously provided visual representation that, when received by the communication device, cause the communication device to visually indirectly display the one or more aspects of the communeike to the end user. And circuitry for sending the secret indicator data to the end user entity by sending secret indicator data to the end user entity to provide a message. 176. The method of claim 176,
By sending to the end user entity secret indicator data that, when received by the communication device, cause the communication device to provide a previously provided visual message to visually indirectly display the one or more aspects of the co-working to the end user. Circuitry for transmitting the secret indicator data to the end user entity is previously provided such that when received by the communication device the communication device visually indirectly displays the one or more aspects of the communeke to the end user. And circuitry for transmitting the secret indicator data to the end user entity by sending secret indicator data to the end user entity to provide a modified visual message. System. 162. The method of claim 162,
The secret indicator data to the end user entity, the secret indicator data comprising secret indicator data that when received by the communication device causes the communication device to provide a secret indicator indirectly indicating to the end user the one or more aspects of the communeke. The circuitry for transmitting may include secret indicator data when received by the communication device such that the communication device provides a secret vibration indicator that indirectly displays the one or more aspects of the communeike to the end user via a particular vibration. And circuitry for transmitting the secret indicator data to the end user entity by transmitting to an end user entity. 99. The method of claim 98,
In response to intercepting the cocaine aspect data, instead of sending a direct representation of the cocaine to the end user entity, the secret indicator data secretly representing the one or more aspects of the cocaine upon receipt by the end user entity. Circuitry for transmitting to the end user entity comprises circuitry for transmitting the secret indicator data to the end user entity by transmitting to the end user entity secret indicator data that does not at least directly identify the source entity. Implementation system. 178. The method of claim 179,
The circuitry for transmitting the secret indicator data to the end user entity by sending secret indicator data to the end user entity that does not at least directly identify the source entity further comprises at least directly directing the source entity to the source for the co-worker. And circuitry for transmitting the secret indicator data to the end user entity by sending secret indicator data that is not identified as the end user entity. 179. The method of claim 179,
The circuitry for transmitting the secret indicator data to the end user entity by sending secret indicator data to the end user entity that does not at least directly identify the source entity includes a secret that does not include any representation of the source entity. And circuitry for sending the secret indicator data to the end user entity by sending indicator data to the end user entity. 182. The method of claim 181,
Circuitry for transmitting the secret indicator data to the end user entity by sending secret indicator data to the end user entity that does not include any representation of the source entity may include any name, address or telephone associated with the source entity. And circuitry for sending the secret indicator data to the end user entity by sending secret indicator data without a number to the end user entity. 182. The method of claim 181,
Circuitry for transmitting the secret indicator data to the end user entity by sending secret indicator data to the end user entity that does not include any representation of the source entity may include one or more temporary representations of one or more representations of the source entity. And circuitry for transmitting the secret indicator data to the end user entity by sending secret indicator data including a local tenens to the end user entity. 185. The method of claim 183,
Circuitry for transmitting the secret indicator data to the end user entity by sending secret indicator data to the end user entity comprising one or more temporary representations of one or more representations of the source entity may include one or more associated with the source entity. And circuitry for sending the secret indicator data to the end user entity by sending secret indicator data to the end user entity including one or more substitutes for a name. 185. The method of claim 183,
Circuitry for transmitting the secret indicator data to the end user entity by sending secret indicator data to the end user entity comprising one or more temporary representations of one or more representations of the source entity may include one or more associated with the source entity. And circuitry for sending the secret indicator data to the end user entity by sending secret indicator data to the end user entity comprising one or more substitutes for an address. 185. The method of claim 183,
Circuitry for transmitting the secret indicator data to the end user entity by sending secret indicator data to the end user entity comprising one or more temporary surrogates for one or more representations of the source entity includes at least one associated with the source entity. And circuitry for sending the secret indicator data to the end user entity by sending secret indicator data to the end user entity, the secret indicator data comprising at least one substitute for the telephone number of. 179. The method of claim 179,
The circuit for transmitting the secret indicator data to the end user entity by transmitting secret indicator data to the end user entity that does not at least directly identify the source entity further includes at least the secret indicator data that does not directly identify the communeike. And circuitry for sending the secret indicator data to the end user entity by sending a to the end user entity. 187. The method of claim 187,
The circuitry for transmitting the secret indicator data to the end user entity by transmitting secret indicator data to the end user entity that does not at least directly identify the cocaine does not at least directly identify a subject for the cocaine. And circuitry for sending the secret indicator data to the end user entity by sending secret indicator data to the end user entity. 99. The method of claim 98,
In response to intercepting the cocaine aspect data, instead of sending a direct representation of the cocaine to the end user entity, the secret indicator data secretly representing the one or more aspects of the cocaine upon receipt by the end user entity. Circuitry for transmitting to the end user entity comprises circuitry for transmitting the secret indicator data to the end user entity by sending secret indicator data in the form of header data to the end user entity. 99. The method of claim 98,
In response to intercepting the cocaine aspect data, instead of sending a direct representation of the cocaine to the end user entity, the secret indicator data secretly representing the one or more aspects of the cocaine upon receipt by the end user entity. Circuitry for transmitting to an end user entity includes circuitry for transmitting the secret indicator data to the end user entity by transmitting to the end user entity a list of one or more received communeikes containing the secret indicator data. Computer implemented system. 192. The method of claim 190,
Circuitry for transmitting the secret indicator data to the end user entity by sending a list of one or more received co-workers containing the secret indicator data to the end user entity includes one or more temporary representations of one or more representations of the source entity. And circuitry for transmitting to the end user entity the list of one or more received communikes including the secret indicator data by sending the list of one or more received cocaniques including a surrogate to the end user entity. Implementation system. 99. The method of claim 98,
Circuitry for receiving the one or more conditional instructions from the end user entity
Computer implemented system further comprising. 192. The method of claim 192,
Circuitry for receiving the one or more conditional instructions from the end user entity comprises circuitry for requesting the one or more conditional instructions from the end user entity. 194. The method of claim 193, wherein
Circuitry for requesting the one or more conditional instructions from the end user entity comprises circuitry for sending one or more requests for the one or more conditional instructions to the end user entity. Conditionally obfuscate the communike aspect data associated with a particular source entity and indicate one or more aspects of the communique directed to the end user entity and towards the end user entity. Means for intercepting, according to one or more conditional indications of the end user entity; And
In response to intercepting the cocaine aspect data, instead of sending a direct representation of the cocaine to the end user entity, the secret indicator data secretly representing the one or more aspects of the cocaine upon receipt by the end user entity. Means for sending to end user entity
Computer implemented system comprising a. Conditionally obfuscate the communike aspect data associated with a particular source entity and indicate one or more aspects of the communique directed to the end user entity and towards the end user entity. One or more instructions for intercepting, according to one or more conditional instructions of the end user entity; And
In response to intercepting the cocaine aspect data, instead of sending a direct representation of the cocaine to the end user entity, the secret indicator data secretly representing the one or more aspects of the cocaine upon receipt by the end user entity. One or more commands for sending to the end user entity
A computer program product comprising an article of manufacture comprising a signal-bearing medium for conveying a signal. Using one or more processors, one or more aspects of a communique pointing to an end user entity and representing communiques, and associated with a particular source entity, the communike aspect data associated with the source entity, Intercepting, according to one or more conditional instructions of the end user entity, to conditionally obfuscate the coquenic; And
In response to intercepting the cocaine aspect data, instead of sending a direct representation of the cocaine to the end user entity, the secret indicator data secretly representing the one or more aspects of the cocaine upon receipt by the end user entity. Steps to Send to End User Entity
How to include.

Images