Abstract: Systems and methods are described that facilitate a conference call between a plurality of communication devices. The method may comprise: providing a first primary communication device; providing a second primary communication device; providing a conference call controller; providing a first alternate communication device; establishing a first control link between the first primary communication device and the conference call controller; establishing a media link between the first and second primary communication devices via the conference call controller; and establishing a second media link between the first alternate communication device and the conference call controller. The second media link may be established upon the conference call controller receiving a link request from the first primary communication device via the control link. In some embodiments, the first media link conveys a first media signal which is different than a second media signal conveyed by the second media link.

Abstract: A method and system for distributing data between a first user and a second user by detecting direct or indirect communication between the first user and the second user, creating an entry for the second user in a roster for the first user, populating the entry for the second user in the roster of the first user with data elements and attributes of the data elements, the data elements and attributes of the data elements indicating what data can be shared with the second user and how the data is to be shared and utilizing the roster of the first user to distribute data reflecting the first user to the second user.

Abstract: A method and system for processing a data request from a watcher for a target at a server, the method receiving a request for information; searching through a policy for rules to be applied based on the watcher; applying any rules found by the searching, the rule causing a transformation of the information into at least one aspect interpretable by the watcher, the applying utilizing a presence information data format transformation; and returning the at least one aspect incorporated in a presence information data format.

Abstract: A method of sharing contacts within a converged address book system having a converged address book server, the method receiving from a requestor, at the converged address book server, a request for a contact to be shared with a recipient identified in the request; obtaining contact information for the contact from a repository; and delivering the shared contact to the recipient. Also, a method for interaction with a legacy address book system from a network based converged address book system, the method receiving a request to import legacy address book data from a legacy address book system; contacting the legacy address book system and supplying access parameters; retrieving data from the legacy address book system; and storing the imported data in a network based address book storage.

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 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 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 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.