Abstract: A communication system issues tokens in order to control communication received by the system. The tokens are arbitrary symbols which are stored in one or more Token Logs (TLs) for future reference. Those to whom the tokens are issued use specific tokens by including them in messages sent to the token issuer. The communication systems belonging to the potential token users record tokens which they have been issued, so that those tokens may be included in subsequent communication to the token issuers. Incoming messages without tokens are given a tokenless status and possibly rejected. Token-request tokens are automatically issued to allow other individuals to request tokens which can be used in subsequent communication. Multiple Token Logs are synchronized across multiple devices.

Abstract: A method for managing a message communication system comprising providing a token log as a data structure that contains a user-extensible set of tokens and implied conditions under which specific tokens are considered valid. The method also includes creating a new token as a set of symbols and storing the new token in the token log together with information that implies one or more conditions under which the token is considered valid, which validity information implies one or more specific actions to be performed when a message accompanied by the new token experiences an event. The method further includes providing for distributing the new token to one or more external entities and providing a system operator with the ability to change a validity status of the token.

Abstract: A communication device records a current mode, which is an indication of how incoming communications and other alert events are to be processed. We provide a mode stack, which records modes that have been the current mode, with means for determining which one or more mode stack entries constitutes the current mode. We also provide for an automode table, which records events that will trigger specific modes to be automatically registered and unregistered on the mode stack. Automode table entries may be based on temporal events such as from electronic calendars, based on geographical events such as determined by GPS or RFID, based on application events such as phone or media player usage, based on communication events such as establishing a communication link with a Bluetooth device, or based on other detectable events. The result is a device that can automatically adjust mode and alert response according to predefined conditions.

Abstract: A file system or other system that manages information entities includes a sub-system to store one or more tokens, as well as a token action log to associate each token with a customizable set of one or more actions, where each token is to trigger the associated set of one or more actions in response to accompanying a file-system/information entity that experiences an event. The file system also includes a token log manager, which initiates the appropriate actions corresponding to file-system entities that experience an event.

Abstract: A communication system includes a token generator to create one or more tokens, as well as a token action log to associate each token with a customizable set of one or more actions, where each token is to trigger the associated set of one or more actions in response to accompanying a communication that experiences an event. The communication system also includes a token distributor to make the one or more tokens available for distribution to entities potentially desiring to communicate with the communication system.

Abstract: A file system or other system that manages information entities includes a subsystem to store one or more tokens, as well as a token action log to associate each token with a customizable set of one or more actions, where each token is to trigger the associated set of one or more actions in response to accompanying a file-system/information entity that experiences an event. The file system also includes a token log manager, which initiates the appropriate actions corresponding to file-system entities that experience an event.

Abstract: A communication system includes a token generator to create one or more tokens, as well as a token action log to associate each token with a customizable set of one or more actions, where each token is to trigger the associated set of one or more actions in response to accompanying a communication that experiences an event. The communication system also includes a token distributor to make the one or more tokens available for distribution to entities potentially desiring to communicate with the communication system.

Abstract: An account holder initiates a transaction by providing a vendor both account information as well as a specific Transaction Authorization Token (TAT) that was previously stored in a Token Log. The vendor passes the account information and TAT with the transaction information to an institution responsible for authorizing one or more transactions involving the financial account. That institution determines whether or not to authorize the transaction by consulting the Token Log entry for the given TAT.

Abstract: A file system or other system that manages information entities includes a subsystem to store one or more tokens, as well as a token action log to associate each token with a customizable set of one or more actions, where each token is to trigger the associated set of one or more actions in response to accompanying a file-system/information entity that experiences an event. The file system also includes a token log manager, which initiates the appropriate actions corresponding to file-system entities that experience an event.