Patent application number | Description | Published |
20080263156 | Secure Transactional Communication - Systems for providing sign-up email addresses are disclosed herein. A user may set up a sign-up email address for receiving emails from a trusted, Internet-based enterprise. The user may set up a dedicated mailbox folder associated with the sign-up email address or enterprise. The email server may automatically direct emails coming from that enterprise into that folder. To “unsubscribe,” the user needs only to delete the folder or the sign-up address. Emails from the enterprise to the sign-up address may be highlighted in the user's main inbox. Thus, the user may be assured that any such email is truly from the enterprise, and not a phishing expedition or spam. Such systems also provide the user with effective tools to recognize phish or spam emails that appear to be from the trusted enterprise and not to act on them. | 10-23-2008 |
20080317228 | Message Recall Using Digital Rights Management - Email messages are recalled in accordance with restrictions attached to the message. Use of the message is limited per the restrictions. Example restrictions include printing restrictions, forwarding restrictions, exporting restrictions, copying restrictions, reading restrictions, and a expiration time of the message. | 12-25-2008 |
20100185735 | EXTENSIBILITY FOR HOSTED MESSAGING SERVERS - Architecture for messaging server extensibility without the need to update or make changes to the messaging server by routing selected messages to a remote location for processing by custom code or third-party code. The messaging server routes the selected messages based server analysis of the messages and in view of configuration data (or conditions) for routing messages. The remote location processes the message and can instruct the messaging server to accept, reject, or redirect the message. Additionally, the remote location can modify the message and instruct the messaging server to process the modified message. The hosted organization can configure triggers to have the messaging server call to a web service with the messages, which extends the functionality of the messaging server. | 07-22-2010 |
20100191810 | TRANSPORT HIGH AVAILABILITY FOR SIDE EFFECT MESSAGES - Architecture that protects side effect messages by associating the side effect messages with a primary (redundant) message that was received by a transport mechanism (e.g., a message transport agent). Side effect messages are considered “side effects” of a primary message that caused generation of the side effect messages. The primary message is only considered fully delivered after the primary message and all associated side effect messages are delivered, after which the source of the primary message is ACK'd (sent an “ACKnowledgement” message). Hence, in case of hardware failures after the primary message was delivered, but before delivery of side effect messages, the redundancy approach used triggers re-delivery of the primary message and re-generation and delivery of the side effect messages. | 07-29-2010 |
20100205257 | TRANSPORT HIGH AVAILABILITY VIA ACKNOWLEDGE MANAGEMENT - Architecture that facilitates transport high availability for messaging services by providing the ability of a receiving entity (e.g., receiving message transfer agent (MTA)) to detect if a sending entity (e.g., sending MTA or client) is a legacy sending entity. When the receiving entity detects that the sending entity is a legacy system, by advertising transport high availability capability to the sending entity, if the sending entity does not opt-in to this capability, the receiving entity keeps the sending entity client “on hold”, that is, waiting for an acknowledgement (ACK) until the receiving entity delivers the message to the next hops (immediate destinations). This approach maintains at least two copies of the message until the message is successfully delivered (to the next hop(s)). Hence, if the legacy sending entity or the receiving entity fails, the message is still delivered successfully. | 08-12-2010 |
20100306554 | DISTRIBUTED KEY ENCRYPTION IN SERVERS - Architecture that stores specific passwords on behalf of users, and encrypts the passwords using encryption keys managed by a distributed key management system. The encryption keys are stored in a directory service (e.g., hierarchical) in an area that is inaccessible by selected entities (e.g., administrative users) having superior permissions such as supervisory administrators, but accessible to the account components that need to access the unencrypted passwords. The distributed key management system makes the encryption key stored in the directory service available to all hardware/software components that need the key to encrypt or decrypt the passwords. | 12-02-2010 |
20100325215 | MESSAGE REQUIREMENTS BASED ROUTING OF MESSAGES - Architecture for enabling messages to be routed between network servers based on message requirements related to version, capabilities, and features, for example. The message requirements designate delivery over a transport path compatible with the message requirements. The message requirements can include a particular version or other features related to different software applications that require compatibility in message handling. Routing information is maintained related to a transport server or other network transport entity compatible with the message requirements and through which the message can be routed. The message is routed to the compatible transport server for delivery to the destination while avoiding delivery to transport servers incompatible with the message requirements. | 12-23-2010 |
20130103774 | TRANSPORT HIGH AVAILABILITY VIA ACKNOWLEDGE MANAGEMENT - Architecture that facilitates transport high availability for messaging services by providing the ability of a receiving entity (e.g., receiving message transfer agent (MTA)) to detect if a sending entity (e.g., sending MTA or client) is a legacy sending entity. When the receiving entity detects that the sending entity is a legacy system, by advertising transport high availability capability to the sending entity, if the sending entity does not opt-in to this capability, the receiving entity keeps the sending entity client “on hold”, that is, waiting for an acknowledgement (ACK) until the receiving entity delivers the message to the next hops (immediate destinations). This approach maintains at least two copies of the message until the message is successfully delivered (to the next hop(s)). Hence, if the legacy sending entity or the receiving entity fails, the message is still delivered successfully. | 04-25-2013 |
20140006783 | ESTABLISHING SECURE, MUTUALLY AUTHENTICATED COMMUNICATION CREDENTIALS | 01-02-2014 |
20140313902 | OPTIMIZATION OF OVER-THE-TOP (OTT) SERVICES ON CARRIER NETWORKS - Methods and apparatus for executing a client-based, over-the-top (OTT) application, the client-based OTT application for maintaining communications with a second communication device, comprising, in one embodiment, a first transceiver for transmitting and receiving user traffic, a memory for storing processor-executable instructions, and a processor, coupled to the transceiver and the memory, for executing the processor-executable instructions that cause the wireless communication device to establish a first control plane connection, establish a second control plane connection, establish a first data plane for transporting the user traffic, the first data plane connection relating to the first control plane connection, establish a second data plane connection for transporting the user traffic if at least one predetermined event has occurred, the second data plane connection related to the second control plane connection, and to transmit and receive the user traffic over the second data plane connection via the first transceiver. | 10-23-2014 |