Abstract: Automated discovery of related mobile applications across operating systems

Abstract: In embodiments, a unique ID may be generated for a user of a mobile device by requesting, from a DNS server, an address record for each domain name of a series of domain names to create an address record set. The address record for each domain name may be randomly selected from a group of address records associated with the respective domain name. The unique ID may then be generated utilizing the address record set. In other embodiments, a list of URI schemes may be sent to the mobile device, which may respond with an indication of a subset of the URI schemes that are supported by the mobile device. This subset of the URI schemes may then be correlated with one or more associated native applications to identify native applications installed on the mobile device to automatically profile the mobile device. Other embodiments may be described and/or claimed.

Abstract: In embodiments, a unique ID may be generated for a user of a mobile device by requesting, from a DNS server, an address record for each domain name of a series of domain names to create an address record set. The address record for each domain name may be randomly selected from a group of address records associated with the respective domain name. The unique ID may then be generated utilizing the address record set. In other embodiments, a list of URI schemes may be sent to the mobile device, which may respond with an indication of a subset of the URI schemes that are supported by the mobile device. This subset of the URI schemes may then be correlated with one or more associated native applications to identify native applications installed on the mobile device to automatically profile the mobile device. Other embodiments may be described and/or claimed.

Abstract: The resources needed by an application to execute are declared by the application. When the application is activated, only the declared resources are made available to the application because only the declared resources are connected to the execution environment. Accessibility to resources may be controlled by the operating system by making the resource visible or invisible to the executing software by mapping a local name used by the executing software to a global resource, possibly limiting the type of access allowed. Because the executing software relies on the mapping function performed by the operating system for access to resources, and the operating system only maps names declared by the software, the operating system can isolate the software, and prevent the application from accessing undeclared global resources.

Abstract: The operating system organizes software so the set of extensions for an extendable application can be dynamically discovered and the extension can be run securely. Extensions are run as separate applications instead of within the extendable application's process. Extensions are discoverable to an activated extendable application by querying a category catalog. A category provides at least a partial description of a contract between an activating software entity and a software entity that is activated by the activating software entity. The category may enumerate a set of configuration settings associated with the contract that may be used to set up an isolated execution environment for the activated software entity. The category may also specify one or more extension points to be used for communication between the activating and activated software entities. The category may also include a list of software entities that implement the category.

Abstract: The operating system manages software entities by creating a construct called a context that organizes and manages software-related state and configuration settings of applications. A context may comprise an installation service, a configuration service and an activation service. Contexts can be linked or arranged hierarchically to form parent-child relationships. Hierarchies may be used to affect accessibility of software items, to satisfy dependencies, to control the visibility/invisibility of software items, to provide access to configuration settings and to override software availability, dependencies and configuration settings. An override may be applied to set policy when more than one context has a configuration setting, dependency or access to a software entity.

Abstract: The database (namespace) for storing component metadata for an application that is to be run in an isolated environment is isolated by an operating system by storing the component metadata in a local set of information associated with the isolated application instead of in a global namespace. The operating system utilizes this local metadata instead of the global database when components are employed. Registration data for components is placed within a manifest, enabling the operating system to determine the relationship between an application and a component or set of components used by the application.

Abstract: The operating system manages software entities by creating a construct called a context that organizes and manages software-related state and configuration settings of applications. A context may comprise an installation service, a configuration service and an activation service. Contexts can be linked or arranged hierarchically to form parent-child relationships. Hierarchies may be used to affect accessibility of software items, to satisfy dependencies, to control the visibility/invisibility of software items, to provide access to configuration settings and to override software availability, dependencies and configuration settings. An override may be applied to set policy when more than one context has a configuration setting, dependency or access to a software entity.

Abstract: Software typically changes over its useful lifetime. New versions of software are created to change or improve functionality, to add functionality, to correct coding errors, improve performance, to adapt to new hardware and for many other well-known reasons. The process of delivering new versions of software to users is called servicing the software. The operating system decides which version(s) of a piece of software satisfy dependencies of other software by creation of a context. The context may be used to organize and manage versions of software, to declare activation policies concerning the use of different versions of software and to service the versioned software. The context may include an activation service that maintains and manages resolution polices, resolves dependencies, constructs the environment in which an application runs and initiates the running of the software.

Abstract: The operating system manages software entities by creating a construct called a context that organizes and manages software-related state and configuration settings of applications. A context may comprise an installation service, a configuration service and an activation service. Contexts can be linked or arranged hierarchically to form parent-child relationships. Hierarchies may be used to affect accessibility of software items, to satisfy dependencies, to control the visibility/invisibility of software items, to provide access to configuration settings and to override software availability, dependencies and configuration settings. An override may be applied to set policy when more than one context has a configuration setting, dependency or access to a software entity.

Abstract: A user interface for use in one or more processor-based devices comprising an interactive, social ticker shared among a plurality of users, the interactive social ticker including an animated flow of selectable content.

Abstract: A rules-based software architecture that provides the infrastructure for the definition and execution of end-user rules logic. This enables end-user automation of data in a unified storage platform using simple IF-THEN rules. The architecture includes a monitoring component that tracks items associated with the data, and a rules component interfaces to the rules component, and employs metadata associated with the tracked items to provide for automated handling of a subset of the items. The system further provides for defining virtual collections and items in the system using content based logic. The system further comprises one or more trigger components that sets items and collections of items dynamically active as a function of trigger logic. Additional components can include a constraint component for imposing constraint logic on items, and a decision component that supports enabling application customization logic at decision points.

Abstract: A software application having a graphical user interface (GUI) is provided indicating labeled keys on a keypad of a user's mobile communications device. The GUI has sponsor regions for insertion of various sponsor provided content which may be cached on the communication device. The determination of which sponsors' content to be displayed on the device may be dependant on the content being viewed by the user. The sponsor's content may be inserted into the sponsor region. A selection of the sponsor's content may be made by a user to initiate a user transaction.