Abstract: Consumable feed products and vegetation are delivered to animals using a single container in which the container holds the feed product and is used to deliver the feed and which includes ungerminated seeds embedded in the container body. The seeds are caused to germinate and produce vegetation from the container body, and the germinated seeds and/or vegetation is fed to the animal. Multiple containers may be used simultaneously so that while the consumable feed product from one container is used to feed an animal, another container may be used to grow vegetation or deliver vegetation to the animal. Confined birds such as poultry and chicks may benefit from ingesting feed and vegetation produced from such containers.

Abstract: A lighting unit in the form of laminated layers including a first layer (A), and a second layer (B). At least one of the layers (A) or (B) is optically transparent and the layers (A) and (B) are arranged parallel to each other. At least one functional interlayer (C) is arranged between the layers (A) and (B) and arranged parallel to the layers (A) and (B). The lighting unit includes at least one light source. Preparation of the lighting unit is disclosed. The lighting unit is suitable for use in buildings, furniture, cars, trains, planes and ships as well as in facades, skylights, glass, roofs, stair treads, glass bridges, canopies and railings.

Abstract: Described are a process for preparing a layer structure for an electrochromic device and a process for preparing an electrochromic device.

Abstract: A system and method for synchronizing messages between client application instances and a message service provider includes a connection service communicatively coupled to a plurality of client messaging application instances; a first intermediary transfer layer with an inbound message data queue that queues message updates of a client application instance and an outbound message data queue that queues message updates and notifications from a mailbox service layer; a mailbox service layer communicatively coupled to the connection service through the first intermediary transfer layer; a second intermediary transfer layer with an mailbox message data queue that contains queued message data directed at the mailbox service layer and a message service data queue that contains queued message updates directed at a message service layer; and a message service layer configured for message interactions with an outside message service provider.

Abstract: A message management service that acts as intermediary between a messaging service and a client device can generate a synchronization data bundle for a message that includes an external message identifier usable to retrieve the message from the messaging service. The message management service can send the synchronization data bundle to the client along with the message, and the client can store the synchronization data bundle for each message in its local data store. The client can later return the synchronization data bundle to the message management service, which can use information contained therein to facilitate synchronization and related operations.

Abstract: A message management service can enable a client to search and retrieve of messages from one or more messaging services. The message management service can stage delivery of results to the client to reduce response time for identification of messages satisfying a query. Initially, the message management service can send information descriptive of results, which the client can display. The message management service can send subsequent responses including supplemental information associated with a result and/or actual messages.

Abstract: A message management service can enable a client to search and retrieve of messages from one or more messaging services. The message management service can stage delivery of results to the client to reduce response time for identification of messages satisfying a query. Initially, the message management service can send information descriptive of results, which the client can display. The message management service can send subsequent responses including supplemental information associated with a result and/or actual messages.

Abstract: A system and method for synchronizing messages between client application instances and a message service provider includes a connection service communicatively coupled to a plurality of client messaging application instances; a first intermediary transfer layer with an inbound message data queue that queues message updates of a client application instance and an outbound message data queue that queues message updates and notifications from a mailbox service layer; a mailbox service layer communicatively coupled to the connection service through the first intermediary transfer layer; a second intermediary transfer layer with an mailbox message data queue that contains queued message data directed at the mailbox service layer and a message service data queue that contains queued message updates directed at a message service layer; and a message service layer configured for message interactions with an outside message service provider.

Abstract: Filtering rules for incoming messages can be dynamically generated by a message management service based on patterns in the user's behavior. The message management service can analyze event records associating user actions with features of messages to detect correlations between message features and resulting actions, including correlations across multiple messaging accounts belonging to the same user. Based on correlations, the message management service can provide a suggested rule to the user's client device, and the user can accept or decline the suggestion.

Abstract: A system and method for synchronizing messages between client application instances and a message service provider includes a connection service communicatively coupled to a plurality of client messaging application instances; a first intermediary transfer layer with an inbound message data queue that queues message updates of a client application instance and an outbound message data queue that queues message updates and notifications from a mailbox service layer; a mailbox service layer communicatively coupled to the connection service through the first intermediary transfer layer; a second intermediary transfer layer with an mailbox message data queue that contains queued message data directed at the mailbox service layer and a message service data queue that contains queued message updates directed at a message service layer; and a message service layer configured for message interactions with an outside message service provider.

Abstract: Filtering rules for incoming messages can be dynamically generated by a message management service based on patterns in the user's behavior. The message management service can analyze event records associating user actions with features of messages to detect correlations between message features and resulting actions, including correlations across multiple messaging accounts belonging to the same user. Based on correlations, the message management service can provide a suggested rule to the user's client device, and the user can accept or decline the suggestion.

Abstract: Message management services can include processing an email to identify relevant content from among all content in the email and converting the identified relevant content into a simple, easy-to-read format. For example, message management services can apply multiple parsing strategies to an email. Each strategy can attempt to parse the email to identify relevant content and to output results that include any identified relevant content and an associated confidence score. The results having the highest confidence score can be selected. The identified relevant content included in the selected results can be converted into a flat string with stylings and links for displaying relevant content of the email in a simple, easy-to-read format.

Abstract: Implementations for providing role-based distributed key management (DKM) replication are described. A server node receives a request from a requester node to perform a DKM create or update function. The server node determines the role of the requester node based on a public key of the requester node. The server node determines whether the role of the requester node indicates that the requester node is authorized to request the DKM create or update function. If the requester node's role is authorized to request the DKM create or update function, then the server node performs the requested function. The DKM create or update function may involve a replication function. Public key and trust chains may be derived from physical cryptographic processors, such as TPMs.

Abstract: Location brokering technique embodiments are presented that employ sensor data captured by a user's mobile device to determine the device's location, encrypt the location data and store it in a database. The location data is encrypted in such a way that it is possible to determine when a user's mobile device is currently in the same vicinity as another user's mobile device who is a member of the same group as the first user. However, the actual location and relative mobility or immobility of the users cannot be ascertained except by the users themselves via a decryption procedure or by trusted components. Services are provided can read the stored encrypted location data, processes it to determine if group members are in the same vicinity, and either respond to user queries about the location of other members of a group the user belongs to, or push this information to appropriate users.

Abstract: Filtering rules for incoming messages can be dynamically generated by a message management service based on patterns in the user's behavior. The message management service can analyze event records associating user actions with features of messages to detect correlations between message features and resulting actions, including correlations across multiple messaging accounts belonging to the same user. Based on correlations, the message management service can provide a suggested rule to the user's client device, and the user can accept or decline the suggestion.

Abstract: Systems and methods for identifying threads of related messages. A computer can associate messages with threads by storing a thread identifier (thread ID) identifying a thread and associating the thread ID with a message identifier (message ID) of each known message that belongs to the thread. The computer can inspect a message to determine whether the message identifies a reference message. Before assigning a thread ID to the message or a reference message, the computer can determine whether a message ID for either message is stored in association with a thread ID. If a thread ID is stored for a message ID of either message, the computer can assign the thread ID to message IDs of other reference messages. If a thread ID is not stored for a message ID of either message or is different for either message, store a common thread ID in association with both messages.

Abstract: Filtering rules for incoming messages can be dynamically generated by a message management service based on patterns in the user's behavior. The message management service can analyze event records associating user actions with features of messages to detect correlations between message features and resulting actions, including correlations across multiple messaging accounts belonging to the same user. Based on correlations, the message management service can provide a suggested rule to the user's client device, and the user can accept or decline the suggestion.

Abstract: Filtering rules for incoming messages can be dynamically generated by a message management service based on patterns in the user's behavior. The message management service can analyze event records associating user actions with features of messages to detect correlations between message features and resulting actions, including correlations across multiple messaging accounts belonging to the same user. Based on correlations, the message management service can provide a suggested rule to the user's client device, and the user can accept or decline the suggestion.

Abstract: A message management service that acts as intermediary between a messaging service and a client device can generate a synchronization data bundle for a message that includes an external message identifier usable to retrieve the message from the messaging service. The message management service can send the synchronization data bundle to the client along with the message, and the client can store the synchronization data bundle for each message in its local data store. The client can later return the synchronization data bundle to the message management service, which can use information contained therein to facilitate synchronization and related operations.

Abstract: Implementations for providing role-based distributed key management (DKM) replication are described. A server node receives a request from a requester node to perform a DKM create or update function. The server node determines the role of the requester node based on a public key of the requester node. The server node determines whether the role of the requester node indicates that the requester node is authorized to request the DKM create or update function. If the requester node's role is authorized to request the DKM create or update function, then the server node performs the requested function. The DKM create or update function may involve a replication function. Public key and trust chains may be derived from physical cryptographic processors, such as TPMs.