SG174651A1 - Context aware messaging and content distribution - Google Patents

Abstract

Context Aware Messaging and Content DistributionAbstractIn this document, a system, method and apparatus which provides selectable andautomatic context aware messages to the users is explained. It includes a method toprovide automatic messages for a required need, based on the processed outcome ofvarious contexts. The method to respond to a request for context aware messaging froman initiating device is explained as well method wherein the messages are automaticallypushed to the devices based on context and without any explicit request is also explained.The message communication initiated can be for a particular contact or for a list ofcontacts in the sending mobile device based on the processed outcome of variouscontexts.The messages can be provided to select from a set of predetermined messages based onthe processed contexts which in turn based on the profile of the users, contexts at theclient end, contexts of the content and other environmental contexts. The messages canalso be selected and provided based on common contexts of all selected contacts in thecontact list of the requesting device. The messages may be also be selected and directlyfrom the server to the recipient device instead of being sent back to sender and in turnsender forwarding it with/without editing the messages.Figure 1.

Description

Context Aware Messaging and Content Distribution

Detailed Description Field of the invention

The method, apparatus and system method disclosed, illustrated and claimed in this document pertains generally to communication networks. Embodiments of the present innovation include a client server framework particularly for providing context aware selectable or automatic context aware messages to a request to initiate message communication.

Background of the invention

There are billions of SMSs or MMSs being exchanged all over the world especially on occasions like New Year, Christmas and etc. A system which is intelligent enough to understand the certain preferences of each user who is a sender as well as recipients and a system which can propose a mechanism to generate intelligent messages which the users can directly use with or without modification will give the satisfaction to the user.

Many individuals have become increasingly busy in recent years. The increased level of activity is brought on by increased business, social, and other demands. Advances in technology and communications in particular have further increased and promoted available activities. Despite new communication technologies, maintaining and sending messages and fostering relationships maybe very demanding. As a result, important communications are frequently performed at the wrong time, incompletely or skipped altogether.

Many users are required or desire to communicate important messages not only as part of business, but also to maintain important social bonds and relationships with family, friends and associates. Maintaining social ties is important for psychological and emotional health.

Effectively conveying content, emotions and personality is important.

Many people would like to wish others on various contexts to maintain relationship through gifts, sending greeting e-mails, sending SMSs, sending MMSs, etc. A normal greeting message could be sent through a SMS or MMS. However, more personalized the message; more satisfied the sender and receiver. In all the above scenarios to manually create and send the message is time consuming and a typical human being may not be able to recollect all the contexts which are to be considered to send the messages. In one embodiment of the invention presented a method to select contextualized messages manually from a set of predetermined contextualized messages, sender can select messages based on context, it can be for a particular contact or for a list of contacts. In another embodiment presented a method and apparatus to provide automated context aware messages, where the messages are generated and sent automatically based on the context to a pre selected set of recipients.

The invention can be implemented in numerous ways, including as a method, system, device, apparatus (including graphical user interface or computer readable medium). Several embodiments of the invention are discussed below.

The present embodiments utilize open operating systems known in the art such as Symbian,

MIDlet, Java, Android, Apple etc, provided in the user’s handset to provide an interaction path between the handset and the server.

The objective of the invention is to introduce a novel concept that makes use of the described capabilities in such a way that users can be provided with a wide variety of personalized value-added services or features. The dependent claims describe the preferred embodiments of the invention.

Detailed Description of the invention

Sender and Receiver are the two ends of context aware messaging system with the sender requesting the context aware messaging service to send some information to the receiver. In the simplest case sender is a mobile user. Sender can also be the system itself (acting on behalf of a real “sender”). Receiver (typically a contact in the sender’s contact database) can be the mobile user when there is need to send some information at a pre-determined time.

When a contact is in the role of the sender, treat the surrounding environmental data (date, time, weather etc) as belonging to the sender’s context. Same thought applies for receiver.

The present embodiment takes input as sender’s and receiver's context as input and identifies the contextual content and delivers the content from sender to receiver depending on the delivery preference and content type. A call or a message is initiated to the recipient in response to the date and the time specified by the sender input being met depending on the obtained recipient user’s preference, selectively generating and delivering a message to the user of the received message. The present invention includes non automatic contextualize messages and automatic contextual messages.

Context aware messaging solution comprises of a client side application that needs to be installed on the mobile devices and a server which is deployed in the operator premises. The server solution consists of context database which stores the profiles and context information of the subscribers. The context is fed from several sources including mobile consumer’s phonebook and the client application installed on the mobile. The mobile application synchronizes the profile of the consumer to the server. The server has native content management functionality including a content database with associated content metadata. The server also can integrate with third party content servers. Several services are provided to the mobile subscriber primarily. These services utilize the context of the sender and the receiver to select an appropriate content and deliver the same to the mobile user through SMS or

MMS, etc. For example the automatic birthday greeting service allows to select an appropriate birthday greeting based on the context and can send it directly from the server.

The user can choose the option of reviewing the content on the mobile, and after approval can send it from the mobile.

A method for providing a contextualized messaging or personalized messaging service where in the method includes obtaining a message for the sender according to the recipient context or sending message automatically there by producing a personalized message. The crux is the server which collects and stores the context of sender, receiver and generates a messages thus makes the messages more attractive to the context. In some cases server generates messages personalized to the subscriber and send them to subscriber automatically. For example for a subscriber who is living in Netherlands during winter, if the weather turns to 25 degrees which is something superb and rare, messaging server can popup on his mobile saying weather is great do u want to join for a walk with your girl friend or wife targeting girl friend then user will be so tempted to send message to his girl friend.

System sends contextual messages related to personal needs also, for example system will send a message about vaccination program of user child if the user context has a child with less than 5 years of age.

System and method described generates and stores user context in a distributed way. The distributed storage selection is because of dynamic context. The dynamic context can be generated at server side or at client side, location which is a dynamic context can be generated at client side only and client has to do synchronization with server about dynamic context. Static context information can be stored at server or client depending on client computational capability. The matching process of metadata and context will be done at server only.

Profile data can be self profile or perceived profile of a contact in the phone book, profile data is a static context.

A user profile data includes user name, date of birth, email address or system assigned id, favorite color, favorite actor, favorite author, favorite food, favorite music album, favorite novel, favorite music genre, favorite sport, favorite sports person, favorite Video, first name,

Last name, marital status, gender, nick name, phone number, email Id, favorite past time, day to remember, most memorable day, preferred phone number, fax number, work number, home number, girl/ boy friend mobile number, best friend number and family members phone numbers, native language, languages one can speak and write and the preferred language, home country, time zone, countries visited till now, last visited or recently visited places, places want to visit in future (for example user want to visit Venice in future engine can provide updates on all happenings in Venice or information regarding Venice travel), occupation, income, job description/type, expertise, hobbies, other interests (Numerology,

Astrology, Politics, etc ). Profile data can be entered during registration and user presence (availability and mood (hungry and/or thirsty, partying, looking for company, etc) set to any of the predefined values).

Gender information will be used to select content touchier, emotional, caring and loving. A default color can be selected using gender. Pink is a ladies color. Gender can be used to make the same content available to a group of friends sharing common interest.

Date of Birth will be used to find out the age group, if the date of birth is on “special-day” ex: mahatma-gandhi birthday etc we can utilize that to give more special greetings / context aware messaging. Using numerology name and DOB matching can be done, and some interesting outcome can come which can be delivered if the person is interested in “astrology”.

In case of perceived profile data relationship with the person in the contact list, favorite past time spent together will be very useful to select the content. In some cases context can be perceived user preferences of the list of contacts, learned user preferences, data from local databases, context of sender and receiver gleaned from various social networking sites and home pages, context of recipient device, garner information from various open web services, occasion as context, user Intent (what is the customer trying to do? What is the motivation factor? What is the key driving force? For-example: birthday, anniversary, entertainment, or may be “nothing”), preferences of the customer (Content-type? delivery preference? Does the user have any delivery preferences? For example: send-as-sms, send-as-mms, send-only-as- mms otherwise send-as-sms etc.). Client device can also collect and store the context depending on its computational and memory capability.

System providing contextualized message service will have calendar integration whether in client or server, which will have information on key dates of every year, it could be a

National Importance Day, Independence day of the country, could be various festivals, this day in the history, this day in the user history, community events all those things will be captured globally however the capturing scope can be defined based on the people who are logging in “people for registering”. A user birth day might fall into an important day in our calendar system; the day might be an important day in Greek history or Indian History etc which will be used for generating message or selecting the appropriate content.

Calendar System contains information about the important meetings, lectures, workshops, etc. Date and time of each event is also stored. The calendar system provides the information about future context. The reminder system contains information about the important reminders of a person. The Calendar System is the main source of collecting Context History.

This system also provides the information about future context. To do list of a user provides his/her future context. Future context can be divided into multiple levels of contexts depending on how far future context to arrive. Future context is a dynamic context as it can be re scheduled any time, once event is completed it will become static or context history.

Location context can be combined with to do list context, location based messaging using to do list context, for example a user might want to buy an item which is in his/her to do list, when a user visited a particular location system can infer using location and to do list whether the item is available in that place or not, using the inference message can be generated and sent advertisement of the suggested business establishment can be added to this messages.

Current Context of a user can be derived using future context (take context to arrive in near future), Context History and other static and dynamic contexts, which will be used to select or generate the contextualized message.

This provides the business huge amount of subscriber’s information and preferences which can be used to tailor suitable offering for the customers.

For example if a person working in Netherlands during the winter, if the weather turns to 25 degrees which is something superb and rare in Netherlands, if a message can popup on his/her mobile saying weather is great if you want to join for a walk targeting girl friend/boy friend then the user will be so tempted to send the message immediately thus generating the volume of the SMSs.

Contextualized messages can be sent based on learned user preference and perceived preferences.

Human Resources department can target the employers in an enterprise when more information is known about the employee. An employee who left on a sick leave can be given a get well soon card on behalf of the organization. A nice greeting from the supervisor on the birthday of the employee’s daughter creates a sense of belonging and improves employee’s morale. The above scenario can be provided by integrating with the enterprise employee database, leave management system and other employee and corporate information systems.

The system can then deduct the context of the employee and provide intelligent and appropriate response based on the employee context. It can provide the much needed information in a simplified format at the finger tips of the HR managers to enable them to understand and take appropriate decisions. It would be easy to build relationship through

SMSs. A company can use the context aware messaging system as a mobile mentor where it can send motivational messages to employees to complete the project in time, sending the current status of project giving motivation to complete it early. These messages can be sent as it is like sending a senior manager sending message. Management can send different messages to employees depending on their performance, like excellent, medium and poor to give them inspiration for appreciating good performance and tips to improve and the benefits they would get. Company can send information on time logging data.

The user preferences may be set in advance are collected or learned dynamically.

The system typically involves mechanisms for context acquisition, preprocessing, representation, management and utilization in an application.

The raw context data can be obtained from different types of sources. The raw context data may subject to different forms of preprocessing, for example to deal with missing data or elicit higher level abstractions such as logical relationships or activities.

The Client will also have a default content that will be sent in case of any communication failure with Server. The system will consider recipient’s time zone while sending messages.

The system will consider recipient’s time zone as sender’s time zone if recipient’s time zone is not available explicitly in the profile. If the client device is switched off for any reason, the client will consider sending belated wishes for birthdays happening during the current week.

The client will do synchronization of local profile database with server securely on periodic basis. The client will be able to edit the profile even without a network connection.

A system and method to provide context aware caller tones, user will enter the perceived profile and preferences of the selected contacts in the phone book or the perceived profiles and preferences will be learned by system. System will select and play the caller tone based on the perceived profile, preferences and other context parameters (occasion, date, day, etc) of the caller whose number is in the contact list of the receiver. If the caller is not there in contact list or caller is not selected for service, a caller tone will be selected and played using default context parameters. Default context parameters could be occasion, date, day, calendar, etc. On the day of New year, Christmas ring tone content can be selected appropriately. In detail when user], user2, user3 calling a user different caller tones will be selected and played using the perceived profile, preferences, context parameters of callers respectively. If a user is registered for this service, when user] called him he might be getting caller tune as "Om

Namah Shivaya" (some devotional song) if he is more devotional, When another user called him me he might get a song of his favorite singer. In Context aware caller tone system there is no interaction of callers; system will select the caller tone based on the perceived preferences or some ring tone based on context.

The contextual messages can be selected or generated in following ways 1) Ideas for the messages will be given to user and the user can generate the message

2) Server generates the messages for a single contact or for a list of contacts who are all in a group (classmates) or for all contacts in the contact list based on context (occasion, general information, etc) and send it to user, user can forward those messages with editing or without editing to the recipient or recipients. 3) The users in the network can generate the messages which can be used by other users, it is a context messaging cloud where millions of users write messages and put it on to a system and people can use these messages as they get some kind of royalty or points can be maintained. So this concept reveals the creative capability of the people so there will be sole satisfaction of putting those messages. No of messages written and no of times it is been used by users can be considered to rate the creativity and to allot some rewards. There can be a web portal also where all these messages can be placed.

Context aware Images can also be considered in the same way.

Contextual Messaging blasting, system sending messages to subscriber based on context it will select predefined messages or generate messages and send them to user.

Contextual message broker is a method used to make temporary friends, if a user is entered to a new location, system can suggest a temporary friend in that location who is also interested in making friends, so that user will not face any difficulty at new location.

For the occasion of birthday, the client agent on the mobile asks the user to select a set of contacts from the address-book for whom the automatic birthday greeting service would be cnabled. These contacts at a minimum must have birthday filed available. The system provides the user a way to enter the relevant perceived profile information for each user in the selected list. Automatic birthday greetings / context aware messaging are sent to each of the contacts in the user list on appropriate day. The content can be local-static content or generated from the server. Subscriber will be given the option to view the message before sending in case of Automatic Birthday service.

The system also provides an option to which an automatic birth day reminder of the subscriber is sent. This enables subscriber’s friends to be able to send birthday greeting on time.

The system would send an automatic birthday greeting to the subscriber himself with appropriate content. The user should be able to disable this.

A young man should find reasons to send repeated greetings / context aware messaging to his girl friend or potential girl friend or wife. The system should enable him to do so, by providing appropriate content for various events (festivals, sport-dates, anniversary, etc) which is tailored to the tastes and preferences of the partner. The system shall provide the user an option to automatically send the greetings / context aware messaging or have him validate each of these before sending. This is for successful relationship building. For this one has to select the contacts with whom he/she wants to maintain good relationships or build relationship, user has to enter the perceived preferences of the contact. Subscriber will be given option to view the message before sending in case of Build a relationship.

For example a contextualized outbound message may be set for each each of the user’s family members birthdays on specified days throughout the year. Similarly user may plan contextualized outbound messages with regard to important conferences, sales meetings, deadlines, or other important events for coworkers and customers.

Considering the above the user can select and send messages or automatic messages can be provided on various occasions or intentionally. Personalization brings benefits for the user by matching his stated and learned preferences, thus matching more the user's wishes and needs.

The system provides non automatic contextualized messages (user can request and select depending on context) for a recipient or a for a group of contacts from at least one server to a mobile device includes providing a request path from the mobile device to a mobile service platform, receiving request from the mobile device, authenticating the identity of the user of the mobile device, obtaining the user profile information. The method further includes authorizing control and access to the at least one source, providing a control channel from the mobile service platform to at least one server, and providing data to the mobile device in response to the request via the at least one server. GPRS will be used to connect to mobile service platform and http connections are used to access the content on any one of the server based on context. Mobile device connects the server and selects the single / multiple messages based on the category and downloads into the mobile device.

The content categorization and selection will be done using Age, Relation, Hobbies and tone of the message. Using the age of the recipient system will determine whether the recipient is a kid, teen, youth, adult, middle-age, mature, senior, etc. The relation can be one of the following friend, close friend, wife, husband, girl friend, boy friend, dating, family, mother, father, boss brother, sister, colleague, acquaintance, etc. Acquaintance is the default relation if it is not selected in perceived profile. Hobbies can be Listening music, hanging out, reading, singing, watching tv, etc.

The tone of the message can be one of humor, sharing, advice, funky, general, romantic, funny, flattering, impressing, teasing, inspirational, motivational, traditional, conservative, professional, standard, energetic, fresh, boisterous, humorous, poetic, lyrical, rhythmic, blessing, philosophical, gyan, boring, out-dated, hackneyed, emotional, realist, etc

For building relationship case time is one more input which will be used by system to send message whether to send relationship built up message during morning or evening or night or any time.

Using all above multiple content categories and content selections is possible. Gender and language which receiver can speak and write are other dimensions useful for content selection in addition to recipient profile. The content selection completely depends on recipient user profile.

Content server categorizes the messages in the following manner: - Categories contain calendar events or news events. - Each category contain following sections: Fun/Funky/Loving/Polite/etc.. - Each category specifies Most used Messages, Best rated messages, newly arrived messages.

Network operator can use the profile database to send contextual greetings / context aware messaging or messages to the subscribers. Network operator can add personalized advertisements to greetings / context aware messaging or messages in some cases when a free message is sent to subscriber like when sending a self SMS to a user on a occasion or about information about some discount on a product which is related to his preferences, this is for messages which are sent from subscriber or from corporate who can use our content database for example “On this your 27 birthday get some discount on Item1 by showing this SMS at any of our showrooms”. Interface to user profile database will be given to corporate or some business establishments which will send contextualized messages to their existing customers or to new customers.

Successful personalization of content considering the current context depends on proper descriptions of the user as well as the content itself. Therefore, a user profile and content metadata are essential. To respect the user’s situation there is also a need for linking contextual information to the content like the current time to opening hours of a shop within a content description. Another aspect is the utilization of a service. The user could be informed automatically about relevant content in a proactive way, but also fulfill the active part by requesting content from a reactive system.

This server component contains meta-data about the content data sources. The meta-data would consist of two portions. The first portion would be generated by the Meta data feature extractors and can be stored in the meta-data component or can be stores as a part of the data sources (like, for example, xml documents). The second portion of the meta-data would be populated based on the response/feedback of the user’s query.

A data source is the representation of an information store in the system. Typical data sources are phonebook, datebook, home pages, social networking websites etc. A data source could be an interface to some of the system information without a persistence store attached; for example a time and day data source. Can be interfaces to external information (online) also.

Context indexing mechanism is nothing but rule engine or inference engine. ( Mention about rule engine)

A method for Content Coining, take base content and understand the context of the environment of the user or the requestor and modify the content or enhance the content to ensure that the produced content fits into the expectation. Example toning the base content depending on the requirement, a normal birthday greeting is like “Happy Birthday John” but the toned message after content coining is “Happppppy Birthhhhhhhhhhday Johnnnnnnnnn”.

Similarly based on a specific location like temple or place of worship, cultural events or museums etc, the content could be coined more intelligently so as to provide the best value of content and quality of experience to end users.

The content context needs to be matched with the user's context. This is done by tags and rules processing.

Brief description of the diagrams

Figure 1 depicts how the context aware messaging system works. User will configure messaging services from a context aware client running on his/her mobile. The context aware client on mobile communicates with context aware messaging server using GPRS link. Once configured, the context aware message server dispatches contextual messages (either through

SMS or MMS) to the user or his/her contacts at appropriate time.

Figure 2 explains the component of context and content management as explained below:

The system and method considers the user’s context (static context as well as dynamic context), the user’s history, the user’s future activities, and the user’s group profile.

Context Collector/ Refiner/Aggregator:

This component collects context parameters from various sources. It is responsible to refine the context. Various Context parameters are user preferences, user profile, user current context (static and dynamic), and user future context. The refined context is posted to rule engine to obtain to obtain the content description object.

Rule Engine:

This component takes the context refined Context Refiner to inference, Rule engine constructs the Content Description Object using rules defined and by inference. The Content

Description Object contains various tags required to select the appropriate content.

Content Meta Data Manager

Content Meta Data Manager contains meta-data about the content. Meta data can be stored in a flat file, xml file, etc.

The meta-data would consist of two portions. The first portion would be generated by the feature extractors and can be stored in the meta-data component. The second portion of the meta-data would be populated based on the response/feedback of the user’s query.

Meta-Data Updater

This component is responsible for updating the portion of meta-data that is populated based on the successful query or inferred feedback explicit feedback by the users.

Content Selection Algorithm

This component finds an appropriate content suitable to the context using CDQ. This component returns the absolute URL to the content

Content Data Base

In the data Base, the data is stored. This can be done in several formats. Examples are text, xml, html, video/audio, or relational, or object oriented databases.

Content Metadata Extractor

This component extracts certain features (Metadata) from the content data.

Group Locator

This component locates the information about the location of groups based on the group identifiers.

Group Information Handler

This component is responsible for collecting query related information from the available group information.

Group Identifiers

Group identifiers are used to identify the groups a user might be associated to. Group identifiers are allotted to users based on their static profile, first time when the user registers for the system.

User Content Preferences

User can provide certain Content specific preferences in a standard xml format, which would be used by the Context Refinement component

User Profile/Static Context

User Profile and Static Context is composed of a number of information items like the User

Identity, which could probably be the user’s email address or the system assigned id. User profile contains the information regarding job description/type, expertise, hobbies, and interests of the user. It also includes social situation of the user: marital status, and information about any nearby people who already use the system. The profile and static context information would be used for context elaboration purpose.

User Dynamic Context/History/Future Manager

The module deals with future/history and dynamic context for retrieval.

The module has the following sub-systems:

Calendar Diary System

This system contains information about the important meetings, lectures, workshops, etc .

Date and time of each event is also stored. This module provides the information to the

Future Context Diary.

Reminder System

This system contains information about the important reminders of a person. Functionality of this module is similar to the previous module.

Future Context Diary

This module stores information retrieves information from Calendar/Diary System, Reminder

System, and To Do List. This output of this module is combinaed with other modules like

History Module, User Profile module.

Future Context Diary has three levels of information -- Near Future Information: This is the information that is related to the near future. This information has more effect on the query as compared to the lower two levels of information.

When near future has passed, the Future to History Converter modules converts this information to User History module. -- Mid Future Information: This level of information is little far in future as compared to Near

Future Information. The information from this level flows to Near Future Module.

-- Far Future Information: This is the far information in the future and has less impact on the query as compared to above two levels. The information from this module flows to Mid

Future Level.

Future to History Converter

This module converts the information of future, when it has passed in to the User History module.

Current Context Predictor

This module takes information from Future Context Diary and User History to store the information in the Current Conext Diary.

Current Context Diary

This modules contains information about the current context of the user. Query module takes information from this module while providing result.

Content Retrieval Manager

This module collects the refined results from the content data sources, and presents the results to the user.

Figure 3 explains the handling of caller tones in a contextual manner. Based on the content aggregation, rule engine, content selection and content retrieval the caller tone is selected and played.

Figure 4 explains the above in a flow chart where step by step process is given.

Figure 5 explains the a flow chart wherein step by step process is explained for identifying and processing contexts and selecting relevant messaging or other content to the user based on such processed context.

Conclusion

The above described methods and mobile device describe a context aware messaging system where user can select message based on context or system can send contextual messages automatically. Although invention has been described in language specific to structural features and/or methodological acts, it is to be understood that the invention define in the appended claims is not necessarily limited to the specific features or acts described. Rather, the specific features and acts are disclosed as exemplary forms of implementing the claimed invention.

Claims (33)

Claims

1) A method of providing selectable and automatic messages in response to a request to initiate a message communication, the method comprising Receiving the request to initiate a message communication from an initiating device, the request identifying an intended recipient device;

Selecting a message from a set of pre-determined messages or automatic selection and sending of message based on recipient user profile information

Generating a response message to the initiating device, the response message indicating the selected greeting; and sending the response message indicating the selected greeting; and sending the response message to the initiating device.

2) The method of claim 1, wherein selecting the greeting from the set of pre-determined greetings / context aware messaging is based on an identity of a user of the initiating device or based on occasion.

3) The method of claim2. Where in selecting the greeting from the set of pre-determined greetings / context aware messaging is further based on membership of the user of the initiating device and based on the user profile information from the user of the recipient device and also based on all relevant context associated with these.

4) The method of claim 1, wherein selecting the greeting from a set of pre-determined greetings / context aware messaging comprises selecting a plurality of possible from the set of pre-determined greetings / context aware messaging

5) A system for providing selectable greetings / context aware messaging through a common communication medium like http through GPRS through a mobile browser, in response to such request to initiate a communication from any device whether such device has the relevant client software or not.

6) Selecting greeting or message is purely based on sender subscription only there is no subscription required from receiver and based on associated contexts.

7) Selecting the greetings / context aware messaging based on the sender’s subscription as well as receiver’s subscription and based on associated contexts with these.

8) A method of considering occasion and DOB as context.

In CA messaging case all user preferences are a context.

9) A method of adding advertisement to the content if the content is sponsrored with the content itself

10) A method of sending advertisement based on the processed contexts and the relevance of content to sender and or receiver and or relevant third party who is neither sender nor receiver.

11) A method of selcting and sending a message manually based on context most: Providing interface to user to connect to server where he/she can see the message content categorization Providing multiple messages to user to select based on the user inputs.

Receving user input specifying a recipient, a date and a time of delivery of the outbound message.

12) A method of selecting or generating context aware messages to a user based on recipient profile information, may comprise the operations of

Providing interface to user to slect and enter the percived user profile information ( date birth and email id is compulsary.

Obtaining or acquiring context information based on the context the user is in; Obtaining or acquiring a user’s prefernce based on the obtained context information; Depending on the obatined user’s preferences, selectivley generating and delivering a message notification to the user of the received message

13) The operations of obtaining context information and obtaining the user’s preference may be performed periodically, wherein these operations can be performed at least once when the system is started.

14) The operation of obtaining context information may comprise determining at least one of the location information, environmental information, user information, and computing infrmation

15) The location information may comprise information about the location of the user.

E.g determined by GPS or via any other suitable network.

The environmental information may comprise of information relating to temparature, lightness, etc.

The temporal information may comprise information relating to eg: time, date.etc.

The user information may comprise iformation relating to e.g: email, name, etc.

The computing information may comprise information relating to e.g: IP address of the user’s computer whther a beamer plugged into the the computer is detected etc

16) In case of voice mail greeting or MMS where a recipient can be charged to listen or see the received greeting, this is true in case where it will charged to listen a voice mail; Sender can send a greeting where the receiver charges will be paid by him, so there involves charges of transaction between users and between subscribers if required.

17) Providing context of incoming caller so that the receiver of the call can understand and customize the communication to the specific caller

18) Group based greetings / context aware messaging, wherein the greetings / context aware messaging can be generated by processing the context of the multiple group members and more relevant greetings / context aware messaging can be sent to the group

19) Providing Work Group preferences to have group SMS, wherein, based on a business need, a group or any individual can receive customised business specific contents based on the profile information and various contexts.

20) Providing the greetings / context aware messaging to receiver even if receiver does not require subscription.

User may or may not set the self preferences in profile database

21) Providing a method to select Contextual message to any user, by another user or the system itself

22) Method of dynamically shrinking the content based on the context, thus the content can be sent in relevant details to relevant person.

For example, a more busy person may get a more abridged content.

23) Sending a message (it could be any content, message or can be a advertisement also) when a user is in a ready state to receive (ie, he is not on call, after office hours, during weekend etc).

24) Suggesting a reply message automatically when a message is received, hence receiver can send that suggested reply message with or without modification to sender

25) Suggesting some keywords based on recipient and hence the sender can easily customise the content based on those key words.

26) Providing a method to link the advertisement and marketing agencies as well as the relevant business houses to the system, so that when a particular action is taken (for example, based on the advertisement sent to the user), the relevant business houses can be linked to the system for content usage as well as revenue sharing purposes

27) Providing Location based context aware messaging based on location, and To-do list of the user

28) Providing suggested message to users relevant to other users who are having relatively close proximity

29) Providing a method for dynamic business collaboration while selecting contextual discounts

30) Providing Context aware message management like deleting the expired messages and etc.

31) Customization of message either manually by user or by a mediator agency which may have people or system, depending on the context.

For example after a message is suggested it has to be customised based on the recipient before sending and such customisation can be done by the sender or intermediate user/system.

32) Providing a method of Linking messages, Proposing advertisements or discounts on birth day date.

Such discounts or advertisements are selected based on the processed contexts.

33) Providing Message optimality when sending the content based on the past content consumption, relevance of the content, interest of the user etc so that context is validated before sending the content.