Patent application number | Description | Published |
20080215932 | CONTROLLING SOFTWARE FAILURE DATA REPORTING AND RESPONSES - User input defines transmission filter rules to be met when sending an error report to a support provider. User input also defines collection filter rules to be met when including failure data within an error report. Error reports corresponding to crash failures at clients are filtered with the transmission filter rules to determine which of the error reports to send to the support provider, and each error report to be sent to the support provider is further filtered to remove any failure data that fails to satisfy the collection filter rules. Each error report that satisfies the transmission filter rules, along with the failure data satisfying the collection filter rules, is sent to the support provider for analysis. Standard and or custom failure responses corresponding to the failures at the clients may be retrieved and sent to the clients in accordance with the collection filter rules. | 09-04-2008 |
20080215933 | CONTROLLING SOFTWARE FAILURE DATA REPORTING AND RESPONSES - User input defines transmission filter rules to be met when sending an error report to a support provider. User input also defines collection filter rules to be met when including failure data within an error report. Error reports corresponding to crash failures at clients are filtered with the transmission filter rules to determine which of the error reports to send to the support provider, and each error report to be sent to the support provider is further filtered to remove any failure data that fails to satisfy the collection filter rules. Each error report that satisfies the transmission filter rules, along with the failure data satisfying the collection filter rules, is sent to the support provider for analysis. Standard and or custom failure responses corresponding to the failures at the clients may be retrieved and sent to the clients in accordance with the collection filter rules. | 09-04-2008 |
20080229160 | CONTROLLING SOFTWARE FAILURE DATA REPORTING AND RESPONSES - User input defines transmission filter rules to be met when sending an error report to a support provider. User input also defines collection filter rules to be met when including failure data within an error report. Error reports corresponding to crash failures at clients are filtered with the transmission filter rules to determine which of the error reports to send to the support provider, and each error report to be sent to the support provider is further filtered to remove any failure data that fails to satisfy the collection filter rules. Each error report that satisfies the transmission filter rules, along with the failure data satisfying the collection filter rules, is sent to the support provider for analysis. Standard and or custom failure responses corresponding to the failures at the clients may be retrieved and sent to the clients in accordance with the collection filter rules. | 09-18-2008 |
20080263406 | CONTROLLING SOFTWARE FAILURE DATA REPORTING AND RESPONSES - User input defines transmission filter rules to be met when sending an error report to a support provider. User input also defines collection filter rules to be met when including failure data within an error report. Error reports corresponding to crash failures at clients are filtered with the transmission filter rules to determine which of the error reports to send to the support provider, and each error report to be sent to the support provider is further filtered to remove any failure data that fails to satisfy the collection filter rules. Each error report that satisfies the transmission filter rules, along with the failure data satisfying the collection filter rules, is sent to the support provider for analysis. Standard and or custom failure responses corresponding to the failures at the clients may be retrieved and sent to the clients in accordance with the collection filter rules. | 10-23-2008 |
20130080521 | RESOLVING CONTACTS IN CONFLICT THROUGH SUGGESTION - A communication application resolves contacts in conflict through a suggestive user interface. The communication application retrieves a contact that includes conflicting information with an existing contact from an external resource through a data service. External resources include social networks, e-mail servers, local address providers, etc. The user application employs a sliding scale algorithm to recognize the contact that includes the conflicting information according to a variety of categories including source of the contact, level of interaction and number of matching identifiers between the user and the contact. Subsequently, the communication application presents a suggestion to link the contact that includes the conflicting information with the existing contact to the user in a linking user interface. Upon a user acceptance of the suggestion, the communication application links the contact that includes the conflicting information to the existing contact. | 03-28-2013 |
20130080914 | STORAGE AND EXPOSURE OF UNIFIED CONTACTS BASED ON MATCH CRITERIA - Individual contact information from a variety of sources are linked into a unified contact view to provide consistent user experience across platforms, while contact data is tracked in a distributed fashion. A communication application unifying multiple sources of contact data into a single logical view may communicate to a user that the unification has occurred. Through granular change tracking and data linkage, the user may be empowered to both understand and correct any system action. Match criteria for contact information may be exposed in individual contact views and in the unified contact view clarifying to the user matching and conflicting contact information. | 03-28-2013 |
20130086008 | USE OF MAILBOX FOR STORING METADATA IN CONFLICT RESOLUTION - Metadata associated with contact unification, which may involve conflict resolution and de-duplication, is stored in a user's mailbox for optimizing future automated unification operations, sharing of information between different clients and services, and providing relational data that can be used for other applications. User interactions regarding unification such as rejection or acceptance of automated actions, usage of created unified contacts, as well as data from external applications and services may be analyzed and stored in the mailbox. Such metadata may then be used to resolve conflicts the same user or other users in future contact unification operations and shared with other applications and services through a predefined schema such that those applications and services can update their data as well. | 04-04-2013 |
20130097124 | AUTOMATICALLY AGGREGATING CONTACT INFORMATION - A communication application automatically aggregates contact information. The communication application classifies contact information retrieved from data sources as either duplicate or complimentary contact information to a contact. The communication application aggregates the contact information and the contact into a unified contact object by eliminating the duplicate contact information and adding the complimentary contact information. The application presents the unified contact object through a user interface. | 04-18-2013 |
20130117768 | WEB SERVICE API FOR UNIFIED CONTACT STORE - An Application Programming Interface (API) provides functions for interacting with contact lists and contacts that are stored in a unified contact store by a primary contact service. For example, a client of a unified communications service may use the API to access contact information that is stored with a primary contact service (e.g. a messaging application/service). The contact information is maintained by the primary contact service. The API includes functions such as, but not limited to: adding a new IM contact to a group, adding a new IM group, removing an IM contact from a group, adding a distribution group to an IM list, getting an IM item list, and tagging an IM contact. The contacts may be obtained from the primary contact service and temporarily stored by the client (e.g. within a cache) of a different service. | 05-09-2013 |
20140172849 | FACILITATING PERSONAS IN COMMUNICATION EXCHANGE ENVIRONMENTS - Systems, methods, and software are disclosed herein for facilitating personas in communication exchange environments. In at least one implementation, a communication exchange system receives a persona request for a specific persona and in response identifies contacts associated with the specific persona. The communication exchange system assembles contact information from at least a portion of each of the contacts associated with the specific persona and replies to the persona request with at least the specific persona. The specific persona includes the contact information assembled from the at least a portion of each of the plurality of contacts. | 06-19-2014 |
20140196060 | WEB SERVICE API FOR UNIFIED CONTACT STORE - An Application Programming Interface (API) provides functions for interacting with contact lists and contacts that are stored in a unified contact store by a primary contact service. For example, a client of a unified communications service may use the API to access contact information that is stored with a primary contact service (e.g. a messaging application/service). The contact information is maintained by the primary contact service. The API includes functions such as, but not limited to: adding a new IM contact to a group, adding a new IM group, removing an IM contact from a group, adding a distribution group to an IM list, getting an IM item list, and tagging an IM contact. The contacts may be obtained from the primary contact service and temporarily stored by the client (e.g. within a cache) of a different service. | 07-10-2014 |
Patent application number | Description | Published |
20130232463 | SYSTEM AND METHOD FOR CUSTOMIZING A DEPLOYMENT PLAN FOR A MULTI-TIER APPLICATION IN A CLOUD INFRASTRUCTURE - A deployment system enables a developer to customize a deployment plan generated according to a logical, multi-tier application blueprint for deploying multiple applications in a cloud infrastructure. Using the deployment system, the developer inserts a custom script or task in a sequence of tasks to be performed to deploy an application component in different phases (e.g., installation, configuration, start-up) on a virtual machine. The deployment system anchors the custom script to the different phases of the application component's deployment such that the customizations to the deployment plan are maintained through changes to the underlying application blueprint. | 09-05-2013 |
20130232480 | SINGLE, LOGICAL, MULTI-TIER APPLICATION BLUEPRINT USED FOR DEPLOYMENT AND MANAGEMENT OF MULTIPLE PHYSICAL APPLICATIONS IN A CLOUD ENVIRONMENT - A deployment system enables a developer to define a logical, multi-tier application blueprint that can be used to create and manage (e.g., redeploy, upgrade, backup, patch) multiple applications in a cloud infrastructure. In the application blueprint, the developer models an overall application architecture, or topology, that includes individual and clustered nodes (e.g., VMs), logical templates, cloud providers, deployment environments, software services, application-specific code, properties, and dependencies between top-tier and second-tier components. The application can be deployed according to the application blueprint, which means any needed VMs are provisioned from the cloud infrastructure, and application components and software services are installed. | 09-05-2013 |
20130232497 | EXECUTION OF A DISTRIBUTED DEPLOYMENT PLAN FOR A MULTI-TIER APPLICATION IN A CLOUD INFRASTRUCTURE - A deployment system orchestrates execution of deployment plan in coordination with nodes participating in deployment of a multi-tier application in a cloud infrastructure. The deployment system distributes local deployment plans to each node and maintains a centralized state of deployment time dependencies between tasks in different local deployment plans. Prior to execution of each task, deployment agents executing on each node communicates with the centralized deployment system to check whether any deployment time dependencies need to be resolved. Additionally, the deployment system utilizes a node task timer that triggers a heartbeat mechanism for monitoring failure of deployment agents. | 09-05-2013 |
20130232498 | SYSTEM TO GENERATE A DEPLOYMENT PLAN FOR A CLOUD INFRASTRUCTURE ACCORDING TO LOGICAL, MULTI-TIER APPLICATION BLUEPRINT - A deployment system enables a developer to generate a deployment plan according to a logical, multi-tier application blueprint defined by application architects. The deployment plan includes tasks to be executed for deploying application components on virtual computing resource provided in a cloud infrastructure. The deployment plan includes time dependencies that determine an execution order of the tasks according to dependencies between application components specified in the application blueprint. The deployment plan enables system administrators to view the application blueprint as an ordered workflow view that facilitates collaboration between system administrators and application architects. | 09-05-2013 |
20150081773 | HIGH AVAILABILITY ARCHITECTURE FOR A CLOUD-BASED CONCURRENT-ACCESS COLLABORATION PLATFORM - Embodiments in the present disclosure include systems and methods related to a high-availability architecture for a cloud-based concurrent-access collaboration platform. The disclosed technology relates to an active data center which includes multiple document server instances that handle user requests for concurrently accessing documents. Multiple document server instances are implemented on a single physical server. This architecture uses an instance assignment manager to assign documents to the document server instances, a primary repository to store backup snapshots of the documents, and a datastore to store all changes made to the documents. The disclosed technology also involves a backup data center that can be swapped with the active data center automatically. | 03-19-2015 |