Abstract: Various embodiments herein provide at least one of systems, methods, software, and data structures for tracking usage of mobile codes on mobile electronic devices. Some embodiments include tracking mobile code usage locally on mobile electronic devices. Some embodiments include server mechanisms which facilitate mobile code tracking by mobile code tracking processes on mobile electronic devices. Other embodiments are also described.

Abstract: A method within a computing execution environment for the establishment of a context for a watcher, the method receiving a subscription request including a service identifier; associating the service identifier with a service context for a service; and applying the service context to information returned to the watcher.

Abstract: Various embodiments include systems, methods, data structures, and software to allow a mobile electronic device to update content resolved from a mobile code. For example, a mobile code-reading application executing on a mobile electronic device may receive a mobile code image and decode the mobile code into a data format, the data format including resolved content. The mobile code reading application may detect a content update address field in the data format, the content update address field identifying a content source. A request may be sent to the content source to verify if the resolved content is current and the resolved content or updated content may be presented by a user interface device of the mobile electronic device. In some embodiments, metadata of the resolved content is stored on the mobile electronic device and sent with the request to aid in the verifying. Other embodiments are also described.

Abstract: Various embodiments include systems, methods, data structures, and software to allow a mobile electronic device to retrieve additional content pertaining to content resolved from a mobile code. For example, a mobile code reading application executing on a mobile electronic device may receive a mobile code image and resolve the image to obtain data represented therein. The data resolved from the mobile code image may then be parsed to identify content, such as an image, and an identifier of additional content, such as a Universal Resource Identifier. The content item may then be presented by a target application via a user interface device of the mobile electronic device along with a user interface element representative of the additional content. Other embodiments include providing a mobile code service on a mobile electronic device or on a computing resource accessible by a mobile computing device over a network. Other embodiments are also described.

Abstract: A method and apparatus for use in a network in a mobile environment provides tracking of interactive events related to electronic advertisements. An application running on the network provides a listing of interactive capabilities to a tracking application, also running on the network. The tracking application identifies interactive events of interest and assigns event codes to these events. During operation, the application reports these events to the tracking application.

Abstract: Embodiments of a distributed ad-selection system and method for distributed ad selection are generally described herein. In some embodiments, an applications service provider sends a query to an advertising service provider for ads. The query includes ad-selection criteria and an indication to indicate whether broadening of the criteria is permitted. The ads are received and cached by the application service provider including associated relevancy information. Cached ads are selected by the applications service provider for distribution to mobile devices based on the relevancy information and based on applications operating on the mobile devices that are being serviced by the applications service provider.

Abstract: A method within a computing execution environment for adding an aspect trigger for an aspect, an aspect being an application level abstraction relevant to a source or service, along with the execution environment, where the method includes defining service aspects; inserting or encapsulating the service aspects as named aspects into an abstraction layer in the computing execution environment; and associating the named aspects with the aspect trigger, wherein the abstraction layer is configured to associate aspect triggers for a plurality of client applications.

Abstract: A converged address book system having a converged address book (CAB) client for managing contact information, the CAB client including: an interface for interacting with a CAB server; and a synchronization interface for communicating with a synchronization module for interacting with a data synchronization enabler for synchronization between the CAB client and CAB server; the interface allowing the CAB client to manage contact information by making requests to and receiving responses from the CAB server. The CAB server including an interface for interacting with a CAB client; a data synchronization manager for synchronizing information between at least one CAB user device and the CAB server; a data synchronization interface for synchronizing data with the CAB client; a subscription manager for managing CAB subscription and authorization information; a document management interface for communicating with a CAB XMDS; and an XDMC for accessing and manipulate CAB data stored in the XDMS.

Abstract: A method and system for addressing a unique device from an address book, the method having the steps of: receiving a message having a root token and a secondary token; checking whether the root token exists within the address book, if no, creating a record in the address book with the root and secondary token; and if yes, checking whether the secondary token exists within the address book, if yes, providing a representation of the unique device; and if no, storing the secondary token against the root token in the address book.

Abstract: A method and system for the creation of aspects from a service or application, the method defining related service aspects; inserting or encapsulating service aspects as named aspects into an abstraction layer in an execution environment; and associating the named aspects with logic in the abstraction layer to support application or service function points.

Abstract: A method for execution in a computing execution environment for the creation of aspects from a service or application, an aspect being an application level abstraction relevant to a source or service, the method comprising: defining related service aspects; inserting or encapsulating service aspects as named aspects into a context aware layer in the execution environment, the context aware layer adapted to be called from a plurality of application types or services; and associating the named aspects with logic in the context aware layer to support application or service function points.

Abstract: A context aware platform including a context aware server, the context aware server including: aspects, the aspects being application level abstractions related to a context; policies associated with a context at a point in an application lifecycle, the policies specifying behavior or treatment of aspects; and rules and triggers providing a sequence of steps or logic required to compute aspects; and at least one client, said client being in an execution environment and communicating with said context aware server, wherein the context aware platform replaces aspects, triggers, or both aspects and triggers in the at least one client.