Abstract: A method, device and computer program for the active notes application together with an application user interface (UI) is described in which the active notes application running on the mobile terminal is invoked in response to a user action or automatic event. Data entry and action event entry into the active notes application is made by a variety of input devices including proximity and location sensor. The entered data is embedded into an association application for example, contact manager, calendar and phone book running on the mobile terminal. The action is executed with the data specified using the corresponding associated application for the type of action identified whereby the notes are made active.

Abstract: Very flexible call management is achieved by a method for handling a call setup request (7-10, 7-22, . . . ) from A party (A1 . . . A9) to a B party (511). A reachability server (RS) receives (7-0) the B party's multiple simultaneous caller groups, profiles, redirection settings and associations thereof. Each time the B party's reachability changes, he indicates his current profile (7-20, 7-40, 7-50). Based on the call setup request, the server (RS) determines the A party's identity. Based on the A identity, one of the multiple simultaneous caller groups is determined. Then one of the multiple associations that corresponds to the determined caller group and the current B party is determined. Finally, the call setup request is processed according to the redirection setting of the determined association. The redirection settings may indicate a changed call mode, such as chatting, in case the B party is unable to take a voice call.

Abstract: Sharing information feed data via a network involves forming a token describing the information feed data. The token is received at a first data processing arrangement via the network. The token is processed at the first data processing arrangement to determine the information feed data. Access to the information feed data is provided at the first data processing arrangement based on processing of the token.

Abstract: Service Discovery (SD) agent (208) provides uniform and integrated service discovery operation, whereby a default connection to SD Engine (SDE) (224) may be automatically initiated to aid in service discovery. User agents (UA) (214-216) are installed to implement the various SDP interfaces (314-324) as required. Canonical query transform (310) transforms user queries from query generation tool (302) to the appropriate protocol as needed for SD interfaces (314-324). Likewise, service discovery results from the SD interfaces are translated by canonical query transform (310) into user friendly results for ultimate display to user interface (326).