Patent Publication Number: US-2004044647-A1

Title: Method and a device for activity-based presence information

Description:
CROSS REFERENCE TO RELATED APPLICATIONS  
       [0001] This application claims priority under 35 USC § 119 to Finnish Patent Application No. FI 20021211 filed on Jun. 20, 2002.  
       TECHNICAL FIELD  
       [0002] The present invention relates to a method and a device for providing distributed user activity-based presence information in a telecommunications network.  
       BACKGROUND OF THE INVENTION  
       [0003] Many traditional network applications such as Internet chat room programs offer a centralized way of exchanging data and/or updating the user presence information via a server. Launching a client application causes a notification message to be sent to the server, wherein the corresponding user presence information is updated in the server database. Users can typically acquire the current connection state of preferred persons by accessing the server and sometimes also adjust their own presence profile according to a set of predefined rules. The available presence information is often limited to the simple on-line/off-line type statements.  
       [0004] Document US20020038388 discloses a system and a method for capturing web interactions for further user manipulation. In so-called “collaboration mode” the user is able to share his interactions with other users logged on the system using a dedicated server module comprising a messaging server and a database server. A messaging server handles the collaboration between the user client and the server module, which includes a messaging server engine such as an IRC (Internet Relay Chat) server. A data server is responsible for data recording and conferences management in overall.  
       [0005] Document WO9816045 discloses a communication system wherein a network server maintains a list of users. According to the proposed solution, a communications terminal includes a connection notification apparatus, which informs the network server when the user is connected to the network. In addition, the user may define a list of users whose network connection status should be inspected and the server provides the requested information. Every user has a permanent and unique identification code; therefore the identification is preferably independent of the used communication terminal. The user may separately allow various information, such as localization data, exchanged with other users.  
       [0006] Although prior art solutions described above are certainly applicable in a number of cases, they do not serve all kinds of communication purposes so well. For example, in mobile communication systems the user is most of the time “on-line” and the simple connection state information hardly provides any valuable information to anyone. The user may not have a terminal with himself or then he may be just temporarily unreachable, in a middle of a meeting etc. Additionally, many service security and reliability issues are not covered in current solutions.  
       SUMMARY OF THE INVENTION  
       [0007] The object of the present invention is to overcome the aforesaid problems. The invention discloses a method and a device for providing user activity-based presence information to a set of users belonging to the same communication group. In the basic method, when two or more group members are communicating with each other, they also inform other members about current activity by sending them a notification. In a more cultivated solution, actions executed by the device of the invention are mapped to user profiles, which are in turn associated with at least one communication group.  
       [0008] Finally, notifications are sent to all members of said groups. This decentralized notification method with two different variations is reasonably simple to implement but nonetheless versatile and does not require servers, which are often prone to crash and vulnerable to hacking. The invention is characterized by what is stated in the appended claims.  
       [0009] According to the invention, a method for notifying communication group members, wherein said notifying is to be performed by a personal communications device operable in a telecommunications network, wherein at least one communication group and the members of said communication groups have been defined in said personal communications device, said device executing actions, comprises the steps of  
       [0010] defining the communication actions associated with the notification method,  
       [0011] identifying the communication actions associated with the notification method,  
       [0012] identifying a communication group having the far-end party of the communication action as a member, and  
       [0013] sending notifications to target devices, the users of which belonging to at least one identified communication group.  
       [0014] In another aspect of the invention, a method for notifying communication group members, wherein said notifying is to be performed by a personal communications device operable in a telecommunications network, wherein at least one communication group and the members of said communication groups have been defined in said personal communications device, said device executing actions, comprises the steps of  
       [0015] defining the associations of profiles with actions,  
       [0016] defining the associations of profiles with communication groups,  
       [0017] identifying the actions associated with a profile,  
       [0018] mapping actions to profiles connected to at least one communication group, and  
       [0019] sending notifications to target devices, the users of which belonging to at least one communication group.  
       [0020] In a further aspect of the invention, a personal communications device operable in a telecommunications network comprises processing means and memory means for processing and storing instructions and data, and said device is arranged to identify actions from a plurality of actions, further arranged to associate said identified actions with at least one communication group, and finally arranged to send notifications to target devices, the users of which belonging to at least one communication group.  
       [0021] The term “action” refers to any activity executed by a personal communications device either automatically or by the user initiative.  
       [0022] The term “address table” refers to any kind of stored entity of data comprising contact information of persons, which are supposed to get the notification messages to be sent according to the invention. Contact information is presented in a form exploitable by a personal communications device, e.g. as phone numbers or network addresses.  
       [0023] The term “communication group” refers to a plurality of persons who are somehow connected together, defined and stored in a memory of a personal communications device. In some cases the definitions of communication groups can be retrieved from an external device such as a server to said personal communications device. The connecting factor can be friendship, profession, work, hobby, family relations or whatever reason the user of a personal communications device has found useful.  
       [0024] In one embodiment of the invention a personal communications device supports defining communication groups comprising a plurality of users with appropriate addressing information. When communicating with another member of a group, said communications device is also arranged to send a notification message to other members of that particular group. Said communications device is correspondingly arranged to receive and store the user presence information acquired from other devices.  
       [0025] In another embodiment of the invention the scope of the embodiment above is expanded by exploiting several profiles including a plurality of actions. When an action belonging to a certain profile is executed, members of the communication group(s) associated with that profile are to be notified by said communications device.  
       [0026] In a further embodiment of the invention a personal communications device having initiated a communication task with another communications device is arranged to send a notification message on behalf of said another communications device.  
       [0027] In a further embodiment of the invention a visual and/or audio symbol is attached to each communication group and upon detecting activity in a group, a symbol associated with that group is presented to the user. 
     
    
    
     BRIEF DESCRIPTION OF THE DRAWINGS  
     [0028] In the following, the invention is described in more detail by reference to the attached drawings, wherein  
     [0029]FIG. 1 illustrates the overall concept of the invention wherein a communication group consists of four persons equipped with compatible personal communications devices;  
     [0030]FIG. 2 is a block diagram of a personal communications device, substantially a mobile terminal, capable of sending and receiving notification information according to the invention;  
     [0031]FIG. 3 is a flow diagram disclosing a first embodiment of the invention;  
     [0032]FIG. 4 is a flow diagram disclosing a second embodiment of the invention; and  
     [0033]FIG. 5 depicts a possible appearance of a notification message on a terminal display according to the second embodiment of the invention.  
    
    
     DETAILED DESCRIPTION  
     [0034] Referring to FIG. 1, the basic elements involved in the inventive concept are a bunch of personal communications devices  101 ,  102 ,  103 ,  104 , preferably mobile terminals, connected to a mobile network such as GSM (Global System for Mobile communications) or UMTS (Universal Mobile Telecommunication System). The users of said devices  101 - 104  belong to the same communication group, for example a “buddy list”, defined and stored in the memory of said devices. Considering this particular invention, the communication group may not have to share exactly same members in every single personal communications device, although it definitely would make sense, probably providing the best synergy for exploiting a proposed notification method. The user of device  101  initiates a communication by sending a SMS (Short Message Service) message  106  to another group member equipped with device  102  and according to the invention, device  101  is also supposed to inform the other two devices  103 ,  104  called “target devices” about the current activity status. Thus said device  101  sends separate notification messages  108 ,  110  to target devices  103 ,  104  as they were not involved in the original message transaction  106 . After the far-end party has read the message  106 , the device  102  may correspondingly notify target devices  103 ,  104  about its activity status. As the communication between group members occasionally goes on by e.g. SMS messaging or exploiting real-time methods such as voice calls, all related persons will get notification messages for updating the presence information of active members. Naturally the notification feature should be on/off switchable as if, for example, SMS or MMS (Multimedia Messaging Service) messaging based discussion gets intense as it sometimes does, the rate of incoming notifications may be annoyingly high, surely depending on the used communication method. On/off switching functionality, e.g. simple software controlled parameter to be checked before sending notifications, can be made discrete for sending and receiving directions. Also minimum time intervals etc. for specifying notify resend period can be defined to automatically prevent identical notifications to be transmitted again and again during an ongoing communication session between a plurality of the communication group members. However, if notifications are most of the time non-intrusive, such as short ambient sound signals, and require no further actions from the recipient, switching functionality may not be necessary.  
     [0035] Referring to FIG. 2, basic components of said personal communications device, preferably a mobile terminal, capable of sending and receiving notification information are presented. A memory  202  and a processing unit  214  are required for processing and storing instructions and data. A display  204  and a user interface  218  are typically needed for providing necessary device control and data visualization means to the user. Transceiver  206  handles data transmission over an air interface. Audio parts  216  include e.g. transducers and amplifiers necessary for interfacing acoustic signals such as speech and music with said device. Memory  202  comprises a database  210  for storing user/contact information, communication group and action profile definitions etc., and a specific notification application  212  responsible for executing the notification method in accordance with the invention. It has to be noted that said personal communications device may actually consists of two or more separable devices, which communicate with each other exploiting e.g. a wireless Bluetooth link. One of the devices may provide a connection to the actual communication network possibly utilizing components similar to the ones presented above, while another device may just act as a portable user interface.  
     [0036]FIG. 3 includes a flow diagram disclosing a first embodiment of the invention. In this particular example, the involved personal communications device is a mobile terminal equipped with additional invention related software. Communication actions associated with the proposed method have been predefined in the terminal, see step  302 . The notification procedure is originally initiated by the user who decides to send a SMS message to one of his buddies belonging to a certain communication group, the members of which have been defined in consensus by the group members themselves beforehand. A corresponding new task for handling required SMS transactions is generated. Next the terminal begins executing various task related actions including e.g. composing a new SMS message with necessary header information and payload, requesting the recipient ID and other required communication information from the user, and finally sending the generated message. Notification application  212  monitors executed actions  304  and according to predetermined rules, which may be at least partially defined by the user, identifies the communication actions  306 , which trigger the further execution of the presented method. Sending a message is a communication action and therefore recognized by said application  212 . Next the mobile terminal associates the recipient with a communication group  308  and transmits a notification message to all group members having not received the original message, see step  310 . In practise, association can be implemented by simply retrieving the communication group definitions from the user database  210  including the far-end party information.  
     [0037] If the original message has been sent to many persons belonging to several communication groups or correspondingly, if the single recipient is a member in a plurality of groups, the notification method applies to all concerned groups unless otherwise defined. Alternatively, the execution of the notification procedure can be limited e.g. just to a certain person, for example the first one located in a recipient list of the message and groups associated with him.  
     [0038] While identifying the recipient with certain communication group(s), the mobile terminal has to keep track of all members of various groups targeted for notification. The terminal may, for example, store related members&#39; phone numbers or IP (Internet Protocol) addresses in a temporary address table according to which the notifications are finally to be sent.  
     [0039] The communication actions, which launch the presence updating method in this first embodiment, can e.g. include sending and receiving messages and e-mail (electronic mail), initiating and answering calls, or any other procedures involving interaction of several group members. The recipient/far-end party of said communication action is essentially the factor, which defines the target group(s) for sending the notifications.  
     [0040] In another embodiment of the invention, see FIG. 4, the user is equipped with a modern mobile terminal supporting Internet connections and comprising a WWW (World Wide Web) browser. The user is a member of a few communication groups relating both to his work and hobbies. Communication groups have been explicitly defined in his mobile terminal by the necessary, group member specific addressing information. The user has also associated certain actions with certain profiles  404  and linked those profiles to a number of communication groups, step  406 . This time the user decides to check the WWW site of his sailing club for new and updated content, so he initiates the execution of several interrelated and mostly automated actions  408  for fulfilling the task. Automated actions relate to proper data connection management and required manual actions are mainly linked to interactive selections and decision-making, such as selecting an interesting WWW page to be followed etc. Accessing the sailing club&#39;s WWW site has been defined to belong in a sailing related hobby profile by the user as when he is having a relaxed opportunity of surfing the club site, he is not normally bothered by occasional communication attempts from other people with same hobby. Usually it is even fun and entertaining to swap opinions with persons having a similar “spirit” without need to specifically contact them first. Thus, the notify message can be seen as an unofficial announcement “I&#39;m here!” without pushing anyone to answer. The mobile terminal the user is carrying classifies data fetching from the club&#39;s site as a profiled action  410  and then determines all related communication groups associated with that profile, step  412 . Groups include certain individual members, the contact addresses of which are retrieved from the contact database  210 , e.g. “phone book”, in step  414  to a temporary address table comprising each retrieved contact address only once. The notifications are finally sent according to the address table to all found members possibly belonging to several different groups, step  416 . When the recipient receives the notification, it will be presented to him in a favourable way as well as the recipient&#39;s personal communication device may then automatically maintain a history log of group related actions and person specific activity/presence info by storing the information gathered from received notifications to the database  210  of his mobile terminal.  
     [0041] Notifications can vary considerably for different groups. Applied notification type and style may be selected from a list of predefined options stored in the terminal or they can be designed or at least tailored by the user if preferred. FIG. 5 depicts one possibility for the described second embodiment. The user has constructed a notification message comprising a text element “A sailing group notify: John S. is online!”, a sound sample of passenger ship&#39;s horn, and a figure representing a boat, and stored it in the memory of his mobile terminal. The terminal automatically sends this message to other sailing group members when the user visits the sailing club&#39;s WWW site. If some other group is also associated with the same action, the notification to be sent to the members of those groups may differ from the depicted one. If any specially designed notifications for a certain group are not determined, the notifications to be sent can be of the default type always available in the terminal.  
     [0042] Actions, Which launch the presence information update procedure according to the second embodiment of the invention, are not restricted to any specific class. Therefore, actions like accessing a WWW page or a certain service, changing active user profile or enabling the playing of ring tones, thus implicitly indicating the user is reachable, may be used for such purposes. Database  210  includes necessary couplings of actions, profiles and communication groups. Additionally, even accessing a certain service in a local server, e.g. reading a shared family calendar stored in home PC (Personal Computer) located at one&#39;s home with a Bluetooth enabled PDA (Personal Digital Assistant), can be considered to trigger the execution of said procedure. In that case, functionalities of a suggested personal communications device of the invention may be actually shared with several physically separate devices (e.g. a PDA with user interface wirelessly connected to a server with actual network connection) as mentioned earlier.  
     [0043] Notify messages can be constructed in various different ways but in the following, one possibility is described being targeted specially for the embodiment above. In this example, the notification is a slightly modified MMS message. MMS messages support flexible transmission of several media formats including traditional textual information, sounds, videos, pictures and synchronized presentations utilizing SMIL (Synchronized Multimedia Integration Language). SMIL is a presentation format comprising information about appearance of multimedia elements on a terminal&#39;s display.  
     [0044] X-Mms-Message-Type: m-send-req  
     [0045] X-Mms-Transaction-ID: 123  
     [0046] X-Mms-MMS-Version: 1.0  
     [0047] From: John Speedboat &lt;john.speedboat@testsite.com&gt; 
     [0048] To: Jesse Sailor &lt;iesse.sailor@notify.org&gt; 
     [0049] X-Mms-Message-Class: Auto  
     [0050] X-Mms-Priority: Low  
     [0051] X-Mms-Delivery-Report: No  
     [0052] X-Mms-Read-Reply: No  
     [0053] X-Notify: Activity  
     [0054] X-NotifyID: John Speedboat &lt;john.speedboat@testsite.com&gt; 
                               Content-Type: application/vnd.wap.multipart.related;                                            start=&lt;edit10@sailingclub.sml&gt;;           boundary=“thisistheborder123”;           type=application/smil                 --thisistheborder123       Content-ID: &lt;edit10@sailingclub.sml&gt;       Content-Type: application/smil; charset=“US-ASCII”       &lt;smil&gt;       &lt;head&gt;       &lt;layout&gt;       &lt;root-layout width=“100” height=“200”/&gt;       &lt;region id=“Pic1” width=“100” height=“150” left=“0” top=“0” /&gt;       &lt;region id=“Txt1” width=“100” height=“50” left=“0” top=“150” /&gt;       &lt;/layout&gt;       &lt;/head&gt;       &lt;body&gt;       &lt;par dur = “5s”&gt;       &lt;img src=“Sailnotify.gif” region=“Pic1” /&gt;       &lt;text src=“Sailnotify.txt” region=“Txt1” /&gt;       &lt;audio src=“Sailnotify.amr”/&gt;       &lt;/par&gt;       &lt;/body&gt;       &lt;/smil&gt;       --thisistheborder123       Content-ID: &lt;sail.notify@txt&gt;       Content-Location: Sailnotify.txt       Content-Type: text/plain       A sailing group notify: John S. is online!       --thisistheborder123       Content-ID: &lt;sail.notify@gif&gt;       Content-Location: Sailnotify.gif       Content-Type: IMAGE/GIF       Content-Transfer-Encoding: BASE64       R01GODlhGAGgAPEAAPZRaCgoAAAACH+PUNvcHlyaWdodCAo       QykgMTk5NSBJRVRGLiBVbmF1dGhvcm16ZWQgZHVwbGljYXRpb24       gcHJvaGliaXR1ZC4A ...       --thisistheborder123       Content-ID: &lt;sail.notify@amr&gt;       Content-Location: Sailnotify.amr       Content-Type: audio/AMR       Content-Transfer-Encoding: BASE64       CH+PUNvcHlyaWdodCAoQykgMTk5NSBJRVRGLiBVbmF1dGhvcm       16ZWQgZHVwbGljYXRpb24gcHJvaGliaXR1ZC4AGODlhGAGg ...       --thisistheborder123--                  
 
     [0055] MMS message header described here m-send-req and all other protocol data units for multimedia messaging service are specified in the WAP MMS Encapsulation Protocol document [1] by WAP Forum. For further reading, MMS Conformance document [2] by Nokia and Ericsson covers MMS interoperability issues and the basic structure of MMS messages. m-send-req is normally sent by MS (Mobile Station) to the MMS Proxy-Relay which handles further actions required for message transmission. SMIL presentations and other MMS specific data such as header fields are embedded in an extended MIME (Multi-purpose Internet Mail Extension) message traditionally used for sending composite e-mails on the Internet. See the following Internet Request For Comments documents for further information: RFC2045, RFC2046, RFC2387, RFC2557 [3]. Referring to RFC2046, header fields that begin with string “Content-” describe the content of a message and optional “X-” fields may be created for experimental or private purposes.  
     [0056] In the provided example, all mandatory header fields have been underlined for clarification purposes. X-Mms-Message-Type defines the type of the message, which in this case is m-send-req; send request of a MMS message. X-Mms-Transaction-ID is simply a unique identifier for the request and following replies. X-Mms-MMS-Version implies the used version of MMS standard, 1.0 for the present. From and To fields indicate addresses of the message sender and preferred recipient(s). X-Mms-Message-Class is set to Auto; message is automatically sent by the terminal and therefore further Delivery/Read-reports are not required. X-Mms-Priority Low indicates relatively low importance of the notification message for the recipient. X-Mms-Delivery-Report and X-Mms-Read-Reply fields are valued No as the message was classified “Auto” earlier. X-Notify is an invention specific field, which reflects the type of the notification. “Activity” refers to any kind of action, in this case surfing the WWW site associated with a certain communication group, which doesn&#39;t require real interaction with other members of a group, unlike some other actions like voice calls, real-time messaging etc. Values describing conventional communication action could be, for example, “Discussion”, which would indicate on-going voice-call, or “Messaging” which would indicate sending a message. Another invention specific field is X-NotifyID with senders address. This field can be used to specify the sender differently from the actual From field, if the sender is e.g. temporarily using a rental phone.  
     [0057] Content-Type is a standard MIME field, which has been valued application/wnd.wap.multipart.related disclosing that the separate parts of the message are related and cross-references from one to another are possible. Cross-referencing methods with Content-ID/Content-Location fields are explained in the reference RFC2557. If SMIL presentation is not available, other possible type is, for example, application/wnd.wap.multipart.mixed, which is a “standard” mixed set of parts. Start parameter identifies the presentation part from the overall message structure with ID “edit10@sailingclub.sml” and if not present, presentation part must be the first part of the multipart message. Boundary defines the notation which separates various parts of the multipart message. Therefore, it should be selected in a way that misreading is not possible. Selected “thisistheborder123” is supposed to provide that property. Expression “application/smil” determines the media type; this time top-level type is application and sub-level type is SMIL program.  
     [0058] Next part separated by the Boundary and identified with Content-ID “edit10@sailingclub.sml” includes SMIL program for controlling the appearance and presentation of the transmitted data. Layout section is separated by &lt;layout&gt; and &lt;/layout&gt; tags. It defines the layout for multimedia message, which this time consists of one “slide”. Display is divided into two parts, one for the text named “Txtl” and one for the picture “Picl”. Body tags &lt;body&gt;and &lt;/body&gt; include time container element identified with &lt;par&gt; and &lt;/par&gt; and attribute dur which determines the duration of a single slide. Additionally, several slides can be concatenated to form a traditional slideshow with consecutive time container elements. In this example, only one slide is presented with separate image (Sailnotify.gif), text (Sailnotify.txt) and audio (Sailnotify.amr) parts, which are referenced by their Content-Location field.  
     [0059] Rest of the body parts comprise the aforementioned (text, picture, sound) elements. Note that although Content-Location fields were used for referencing of the multimedia elements, corresponding Content-ID&#39;s were presented as well. Text part consists of plain text while GIF image and AMR audio sample have been coded with BASE64 content-transfer-encoding method. Coding of binary data into text with BASE64 has been described in RFC1521. Coded data in the body parts is purely fictional and not fully illustrated as can been seen from the three dots following the first few rows of picture and sound data.  
     [0060] Affordable but purely text-based SMS messages provide another favourable option for sending notifications whenever more versatile data type alternatives offered by MMS are not necessary. Also direct terminal-to-terminal connections utilizing e.g. mobile IPv6 (Internet Protocol, version 6) can be exploited in notification procedures without traditional SMS/MMS message and service structures.  
     [0061] In a further embodiment of the invention, the communication initiator notifies the rest of the communication group members on behalf of the recipient. Therefore, the initiator may send an additional notification message wherein, for example, X-NotifyID field of the previous embodiment actually includes the ID of the far-end party, not of the initiator. In that case, the additional notification message could be of a preset type in order to be distinguishable from the initiator&#39;s own notify message, which possibly comprises highly personalized content as the text “A sailing group notify: John S. is online!” in the previous embodiment. In another solution, a single notification message may comprise two ID fields: one for the sender and one for the recipient of the original communication action.  
     [0062] Still an additional field may be used to inform if the recipient activity has been actually confirmed by the sender party. For example, in person-to-person voice call scenario, the call originator and related personal communications device almost certainly identify if the far-end party really is active and on-line. Optionally, the notifications could be purely sent on basis of connection parties, regardless of the actual response received from the far-end. Of course, the communication devices may occasionally get confused by the answering machines etc. preventing the truthful presence info to be transmitted to the non-involved group members.  
     [0063] Functionality of the presented embodiment can be made conditional by requiring a separate permission from the recipient before notify “on behalf” can be executed. Authorization may be received automatically from the recipient during the communication action e.g. according to a preset parameter stored in the recipient&#39;s communications device. For example, invention specific software may send a SMS which is interpreted by the initiator&#39;s personal communications device. Described authorization technique mainly consists of sending/receiving a message and parsing text, and is therefore considered obvious to implement by a person skilled in the art.  
     [0064] When utilizing this embodiment, the receiving end of the communication action typically does not send any notification messages if it recognises the communication initiator as a member of the communication group being defined in his personal communications device. Then the receiving end possibly authorizes the communication initiator to continue with the notification procedure on his behalf as pointed out above. In these cases, communication groups should contain exactly the same members in all related communication devices to provide consistent notification service during every possible initiator-recipient scenario. Therefore, the member list should preferably be updated and frozen in consensus with all members or optionally, the communication group member information should be exchanged regularly between group members either automatically or manually by exploiting e.g. SMS/MMS messaging.  
     [0065] Concerning all presented embodiments, one option for automatized communication group (member list) update can rely on the actual notification traffic and preset time “countdown” parameters. For example, if a new notification message is received but the sender does not seem to belong to the communication group somehow mentioned (e.g. in a header field) in the notification, he can be automatically added to that particular group by the receiving personal communications device. On the other hand, if another group member has not been active for a certain time period according to a member specific “countdown timer” stored in the personal communications device, he can be removed from the member list in some cases, initial or updated communication group definitions can be made retrievable from an external device such as a server, which takes care of addition/removal of group members e.g. according to received registration or membership cancellation messages. However, actual notifications are still to be transmitted without a notification server. All proposed methods should be implemented in a way that utilization of external devices is not obligatory in any phase of the notification procedure, including retaining group membership information.  
     [0066] In a further embodiment of the invention a visual and/or audio symbol is attached to each communication group and upon detecting activity in a group by receiving a notification message, a symbol associated with that group is presented to the user. Actual notification message does not have to comprise any multimedia elements like the aforesaid symbol, as the symbol may have been, for example, received earlier in a separate message or created by the user himself, stored and associated with certain group. Anyhow, mandatory aspect of this embodiment still is that the notification message has to be recognized from other messages by e.g. exploiting invention specific header fields.  
     [0067] Referring to all presented embodiments, if modifications are not desirable in existing supported message types and new ones are not going to be developed, also payload of an unmodified, standard message can be used in the implementation of the notification method. For example, recalling how the boundary string separates the body parts of a MMS message, a similar solution can be utilized for identification of the notification message by embedding a reserved data pattern, e.g. a certain character string, into the payload of otherwise standard message. This approach correspondingly requires that the data pattern is carefully selected to avoid miss interpretations.  
     [0068] Today&#39;s people are independent in many ways, as we are not tied up with a certain location, culture, surrounding people or social background so tightly anymore. All this results not least from the advent of modern telecommunication systems which practically are global and most importantly, free of location. Time is maybe the most valuable resource in our everyday life and it is a question of how we would like to spend it, as there certainly are numerous options available to everyone. One obvious and common goal is to do and achieve as much as possible. With a life precept like that, it is undoubtedly hard to maintain the social relationships with other people, as it usually requires some extra effort from people ‘living on the edge’, chronically suffering from lack of time. This invention is likely to offer relief in a form of somewhat unintentional but surprisingly refreshing communication. Furthermore, the proposed method can be exploited in maintaining an automated, portable database of user activity/presence information.  
     [0069] The scope of the invention can be found from the following independent claims. However, utilized personal communications devices, actions and notifications may vary significantly depending on the current scenario, still converging to the basic ideas of this invention. Therefore, the invention is not strictly limited to the embodiments described above.  
     REFERENCES  
     [0070] [1] WAP: MMS Encapsulation Protocol V. Jan. 5, 2002, URL: http://www.wapforum.org/what/technical.htm, WAP Forum 2002  
     [0071] [2] MMS Conformance Document V. 1.1, URL: http://www.thewirelessfag.com/14.4.as, Nokia &amp; Ericsson 2001  
     [0072] [3] Internet FAQ Consortium, URL: http://www.faqs.org/rfcs/rfcXXXX.html, wherein XXXX is the identification number of desired RFC document (e.g. 2557)