Abstract: According to an example, collaborative healthcare may include retrieving healthcare data for a patient from at least one data source, and generating a plurality of distinct healthcare programs for the patient based on the healthcare data. Collaborative healthcare may further include reconciling the plurality of distinct healthcare programs to generate a universal patient healthcare plan for the patient. The universal patient healthcare plan may include a universal view of the overall healthcare for the patient and healthcare provider-specific views for the patient. The reconciling may include detecting conflicts for predetermined components of the healthcare programs, and in response to the detection of the conflicts, eliminating errors related to the detected conflicts.

Abstract: A device intelligence architecture configures and controls on-site devices and performs environment monitoring to facilitate effective device functionality. The architecture facilitates efficient use of devices (e.g., robotics) in an unstructured and dynamic environment, which will allow deployments in many more environments than is currently possible. The architecture stores and shares information between segregated devices to avoid the silo effect of vendor specific stacks. The architecture also models capabilities of devices and maps actions to intelligence packages to deploy a specific intelligence package to the device. The architecture also implements distributed processing. For instance, computationally intensive tasks may be offloaded to the back end processing, with action updates resulting from the processing pushed to the devices.

Abstract: Unmanned vehicle (UV) movement and data control may include controlling a UV according to a movement plan. Formatted movement and status metadata may be received from a sensor of the UV during movement of the UV. The movement and status metadata may include time and location information for the UV during the movement of the UV. An unformatted data stream may be received from the sensor of the UV. The time and location information may be injected into metadata of the unformatted data stream to generate a time and location correlated (TLC) stream. The TLC stream may be analyzed to identify an event related to the UV, and a notification related to the event may be generated.

Abstract: Unmanned vehicle (UV) movement and data control may include controlling a UV according to a movement plan. Formatted movement and status metadata may be received from a sensor of the UV during movement of the UV. The movement and status metadata may include time and location information for the UV during the movement of the UV. An unformatted data stream may be received from the sensor of the UV. The time and location information may be injected into metadata of the unformatted data stream to generate a time and location correlated (TLC) stream. The TLC stream may be analyzed to identify an event related to the UV, and a notification related to the event may be generated.

Abstract: Unmanned vehicle (UV) control may include receiving a UV work order and generating a mission request based on the UV work order. The mission request may identify an objective of a mission, assign a UV and a sensor to the mission from a fleet of UVs and sensors, and assign a first movement plan to the mission based on the identified objective of the mission. The assigned UV may be controlled according to the assigned first movement plan, and communication data may be received from the assigned sensor. The communication data may be analyzed to identify an event related to the mission. The identified event and the first movement plan may be analyzed to assign a second movement plan to the mission based on the analysis of the identified event and the first movement plan to meet the identified objective of the mission.

Abstract: A device may receive sensor data from a sensor device located on a particular farm. The device may identify an alert, associated with the particular farm, based on the sensor data and using a model. The model may be created based on imagery data and numeric data relating to a group of farms. The device may determine, using the model, a recommended course of action to address the alert, and provide, to a user device associated with the particular farm, the recommended course of action.

Abstract: A device may receive sensor data from a sensor device located on a particular farm. The device may identify an alert, associated with the particular farm, based on the sensor data and using a model. The model may be created based on imagery data and numeric data relating to a group of farms. The device may determine, using the model, a recommended course of action to address the alert, and provide, to a user device associated with the particular farm, the recommended course of action.

Abstract: Unmanned vehicle (UV) control may include receiving a UV work order and generating a mission request based on the UV work order. The mission request may identify an objective of a mission, assign a UV and a sensor to the mission from a fleet of UVs and sensors, and assign a first movement plan to the mission based on the identified objective of the mission. The assigned UV may be controlled according to the assigned first movement plan, and communication data may be received from the assigned sensor. The communication data may be analyzed to identify an event related to the mission. The identified event and the first movement plan may be analyzed to assign a second movement plan to the mission based on the analysis of the identified event and the first movement plan to meet the identified objective of the mission.

Abstract: Unmanned vehicle (UV) control may include receiving a UV work order and generating a mission request based on the UV work order. The mission request may identify an objective of a mission, assign a UV and a sensor to the mission from a fleet of UVs and sensors, and assign a first movement plan to the mission based on the identified objective of the mission. The assigned UV may be controlled according to the assigned first movement plan, and communication data may be received from the assigned sensor. The communication data may be analyzed to identify an event related to the mission. The identified event and the first movement plan may be analyzed to assign a second movement plan to the mission based on the analysis of the identified event and the first movement plan to meet the identified objective of the mission.

Abstract: A device may receive sensor data from a sensor device located on a particular farm. The device may identify an alert, associated with the particular farm, based on the sensor data and using a model. The model may be created based on imagery data and numeric data relating to a group of farms. The device may determine, using the model, a recommended course of action to address the alert, and provide, to a user device associated with the particular farm, the recommended course of action.

Abstract: A device may receive sensor data from a sensor device located on a particular farm. The device may identify an alert, associated with the particular farm, based on the sensor data and using a model. The model may be created based on imagery data and numeric data relating to a group of farms. The device may determine, using the model, a recommended course of action to address the alert, and provide, to a user device associated with the particular farm, the recommended course of action.

Abstract: Unmanned vehicle (UV) control may include receiving a UV work order and generating a mission request based on the UV work order. The mission request may identify an objective of a mission, assign a UV and a sensor to the mission from a fleet of UVs and sensors, and assign a first movement plan to the mission based on the identified objective of the mission. The assigned UV may be controlled according to the assigned first movement plan, and communication data may be received from the assigned sensor. The communication data may be analyzed to identify an event related to the mission. The identified event and the first movement plan may be analyzed to assign a second movement plan to the mission based on the analysis of the identified event and the first movement plan to meet the identified objective of the mission.

Abstract: One embodiment relates to a system for linking together multiple registries and aggregating data from the multiple registries. The system includes a plurality of local resource or service (resource/service) registries, a distributed index storage and retrieval system, and at least one proxy registry. The proxy registry is configured to receive a search query from a client system, retrieve information from the distributed index storage and retrieval system as to which of the local resource/service registries are relevant to the search query, and obtain pertinent entries from said relevant resource/service registries. Other embodiments are also disclosed.

Abstract: According to an example, collaborative healthcare may include retrieving healthcare data for a patient from at least one data source, and generating a plurality of distinct healthcare programs for the patient based on the healthcare data. Collaborative healthcare may further include reconciling the plurality of distinct healthcare programs to generate a universal patient healthcare plan for the patient. The universal patient healthcare plan may include a universal view of the overall healthcare for the patient and healthcare provider-specific views for the patient. The reconciling may include detecting conflicts for predetermined components of the healthcare programs, and in response to the detection of the conflicts, eliminating errors related to the detected conflicts.

Abstract: A network-based publish/subscribe model wherein a subscription request is received over the network from a subscriber and a community of interest is identified based on at least one of the subscription request and a network parameter related to the subscription request. Data pertaining to the subscription request and additional data pertaining to the community of interest is retrieved and transmitted to the subscriber. In one embodiment, the subscription request and the additional data are related to a same community of interest. The subscription request may be received by a content aware router.

Abstract: A mediator host is provided for identifying services of networked resources which are available for invocation in a grid computing architecture. A mediator host Application Program Interface (API) is configured to receive a service registry query and related resource query. The API identifies the service registry query and related resource query by signature. A service registry query processing agent is configured receive an identified service registry query from the API, and, to communicate with a corresponding service registry to satisfy the query. A resource query processing agent is configured to receive an identified related resource query from the API, and, to communicate with a corresponding resource registry to satisfy the query. The mediator host returns a service query response which satisfies a predetermined resource metric to identify candidate services for invocation.

Abstract: A wireless mobile computing device is provided for receiving and transmitting data. A wireless interface is configured to capture product parameters. The parameters function to at least identify the product with respect to a repository of information operably linked to the mobile computing device. A transceiving unit is configured to provide the captured product parameters to the repository of information, and, to provide location parameters of the mobile computing device to a market locator system. In return, the transceiving unit receives product information from the repository of information which corresponds to the product parameters. The product information also corresponds to a location of the mobile computing device identified by the market locator system. A user interface is configured to provide targeted product information to the user.

Abstract: A client terminal presents a graphical user interface (GUI) to a distributed computing environment. A first interface is configured to receive data of a portable storage medium. The data includes a key authentication signal and user settings. The key authentication signal identifies an authorized user of the distributed computing environment. A second interface is configured to communicate with an operably linked server. A controller is operative to verify the key authentication signal provided to the first interface in accordance with a distributed computing instruction set, and, upon verification, establishing communication with the operably linked server via the second interface. In this way, the server executes server side applications accessed by a user from the client terminal in accordance with the user settings.

Abstract: A system, method, and computer program product for generating a travel itinerary, including specifying a criteria for a query including a start point and an end point of the travel itinerary, and at least one route point, the route point being a service, a product, a place, an activity, or an event. An interactive mapping system is queried with the criteria to obtain information defining the travel itinerary including mapping information and route point descriptive information including consumer information related to the route point. The travel itinerary is displayed as a map, driving instructions, or the consumer information.

Abstract: One embodiment relates to a system for linking together multiple registries and aggregating data from the multiple registries. The system includes a plurality of local resource or service (resource/service) registries, a distributed index storage and retrieval system, and at least one proxy registry. The proxy registry is configured to receive a search query from a client system, retrieve information from the distributed index storage and retrieval system as to which of the local resource/service registries are relevant to the search query, and obtain pertinent entries from said relevant resource/service registries. Other embodiments are also disclosed.