WO2013121200A1

WO2013121200A1 - Messaging system and method

Info

Publication number: WO2013121200A1
Application number: PCT/GB2013/050347
Authority: WO
Inventors: Declan James METCALFE
Original assignee: Juice Technologies Ltd
Priority date: 2012-02-18
Filing date: 2013-02-14
Publication date: 2013-08-22
Also published as: GB201202779D0

Abstract

A method of transmitting positive messages to a user device. The method comprises: generating behaviour timeline data indicative of times at which a user performs a behaviour; generating a message group list comprising contact data associated with a plurality of other users and transmitting, using the contact data, invitation messages to the plurality of other users of the message group list; receiving, from one or more of other users of the message group list, positive messages generated in response to the invitation messages and storing said positive messages, and transmitting one or more of the positive messages to the user device in correspondence with the times of the behaviour timeline data.

Description

MESSAGING SYSTEM AND METHOD

Field of Invention

The invention relates to systems and methods for sending messages to user devices.

Background

Techniques for sending short messages to and from user devices such as smart phones are well known. Such techniques include short message service (SMS) messages sent to and from cellular phones, instant messages using instant messaging clients, messaging between social networking apps and so on. As well as being a practical and convenient way to exchange information, sending and receiving messages also provides a psychological benefit to users. For example, a user receiving a message from a friend or acquaintance can help the user through difficult times or encourage the user to achieve a goal. Current systems enable messages to be exchanged between users on an ad hoc basis, i.e. a message is sent from a first user to a second user only at the discretion of the first user. If the aim of the message from the first user is to support or encourage the second user (i.e. a positive message), the first user will typically send a message when they guess that the second user might need, or most benefit from, encouragement or support. However, there is no way for the first user to be sure that the message is sent at the most appropriate time, i.e. at a time at which the second user is most likely to benefit from the message.

At present there is no technical system that enables messages of support to be sent to a user at a time when they are most likely to benefit from it. Summary of Invention

In accordance with a first aspect of the present invention there is provided a method of transmitting positive messages to a user device. The method comprises:

generating behaviour timeline data indicative of times at which a user performs a behaviour;

generating a message group list comprising contact data associated with a plurality of other users and transmitting, using the contact data, invitation messages to the plurality of other users of the message group list;

receiving, from one or more of other users of the message group list, positive messages generated in response to the invitation messages and storing said positive messages, and

transmitting one or more of the positive messages to the user device in correspondence with the times of the behaviour timeline data.

In accordance with this aspect of the invention, a method is provided that enables a user of a user device to receive positive messages (e.g. messages of support or encouragement) from other users well placed to support or encourage the user and at times when the user is more likely to benefit from the support or encouragement. In particular, the positive messages can help a user achieve a goal, for example to reduce or quit the performance of a harmful behaviour such as smoking or overeating.

This is in contrast with techniques using conventional messaging systems, in which other users wishing to provide support and encouragement have to guess when the most effective time to support or encourage the user is and where there is no way to encourage other users selected specifically by the user to provide support and encouragement. Optionally, the method further comprises transmitting one or more of the positive messages to the user device in response to a user request input to the user device. Optionally, the step of transmitting the one or more positive messages in correspondence with the times of the behaviour timeline comprises transmitting one or more positive messages a predefined amount of time before the times of the behaviour timeline data. Optionally, the message group list is generated by collecting contact data from data stored on the user device and/or available to the user device via a data connection.

Optionally, at least part of the message group list is generated from contact data collected from a contact directory stored on the user device.

Optionally, the method includes generating the message group list comprises the user selecting one or more users from the collected contact data. Optionally, at least part of the message group list is generated from contact data collected from a social network app installed on the user device.

Optionally, at least part of the message group list comprises, at least in part, a predefined message group list.

Optionally, the behaviour time line data comprises data entered by a user to the user device indicative of times at which the user anticipates they will perform the behaviour. Optionally, the behaviour time line data comprises data entered by a user to the user device at times corresponding to times at which they perform the behaviour, said behaviour time line data being generated over a predefined period.

Optionally, the method further comprises receiving user input to the user device indicative of a behaviour type of the behaviour.

Optionally, the user input is based on a selection of one behaviour type from a list of behaviour types. Optionally, the positive messages include one or more of text data, picture data and audio/video data.

Optionally, the invitation messages comprise an encoded URL, providing a link to a messaging website, and the positive messages are entered via the messaging website.

In accordance with a second aspect of the invention there is provided a system for transmitting positive messages to a user device. The system comprises a messaging server and a user device. The user device is arranged to collect behaviour timeline data indicative of times at which a user performs a behaviour and to transmit the behaviour timeline data to the messaging server. The user device is further arranged to generate a message group list comprising contact data associated with a plurality of other users and to transmit an invitation message to users of a message group list requesting a positive message. The messaging server is arranged to receive and store the behaviour timeline data and receive and store positive messages from the users of the message group list. The messaging server is arranged to transmit one or more of the positive messages to the user device in correspondence with the times of the behaviour timeline data. In accordance with a third aspect of the invention there is provided a messaging server arranged to receive and store behaviour timeline data from a user device indicative of times at which a user of the user device performs a behaviour, and to receive and store positive messages from users of a message group list. The messaging server is arranged to transmit one or more of the positive messages to the user device at times corresponding with the times of the behaviour timeline data.

In accordance with a fourth aspect of the invention there is provided a user device arranged to collect behaviour timeline data indicative of times at which a user of the user device performs a behaviour and to transmit the behaviour timeline data to a message server. The user device is arranged to generate a message group list comprising contact data associated with a plurality of other users and to transmit, using the contact data, invitation messages to the plurality of other users of the message group list. The user device is further arranged to receive positive messages from the other users of the message group list transmitted from the message server at times corresponding with the times of the behaviour timeline data. In accordance with a fifth aspect of the invention there is provided a method of receiving positive messages at a user device from a messaging server. The method comprises:

collecting behaviour timeline data indicative of times at which a user of the user device performs a behaviour;

transmitting the behaviour timeline data to the message server,

generating a message group comprising contact data associated with a plurality of other users and transmitting, using the contact data, invitation messages to the plurality of other users of the message group list, and

receiving positive messages from the other users of the message group transmitted from the message server at times corresponding with the times of the behaviour timeline data. In accordance with a sixth aspect of the invention there is provided a computer program (e.g. an "app") comprising computer executable instructions which when run on a computer causes the computer to perform the method of the fifth aspect of the invention.

In accordance with a seventh aspect of the invention there is provided a computer program product comprising a computer program according to the sixth aspect of the invention.

Various further aspects and features of the invention are defined in the claims.

Brief Description of Figures

Embodiments of the present invention will now be described by way of example only with reference to the accompanying drawings where like parts are provided with corresponding reference numerals and in which:

Figure 1 provides a schematic diagram of an example of a positive messaging system;

Figure 2 provides a flow diagram illustrating an app launch process;

Figure 3 provides a flow diagram illustrating a sign up process;

Figure 4 provides a flow diagram illustrating a process enabling a user to invite other users to join a message group;

Figure 5 provides a flow diagram illustrating a positive message creation process;

Figure 6 provides a flow chart illustrating a process performed by the system shown in Figure 1; and

Figures 7a to 7n provide illustrations of exemplary screen shots of a user interface of positive messaging app.

Detailed Description

Figure 1 provides a schematic diagram of an example of a positive messaging system that provides a messaging service to users of user devices. The system includes a user device 101, such as a smart phone, on which is installed a positive messaging app 102. As is known in the art, an "app" is a computer program typically downloaded from a server to a user device, that runs on the user device. As is known in the art, a user device such as a smart phone includes a communication interface allowing data to be transmitted to and received from by the device, a processor for running software, memory for storing data, a display screen and input means such as a touch sensitive display for receiving user input. In examples where the user device communicates data using a public land mobile network (PLMN), the user device typically includes a subscriber identity module (SIM) as is known in the art.

The system includes a messaging server 103 and a messaging website 104. The messaging website 104 will typically be hosted on a web server (not shown) as is known in the art. A plurality of other user devices 105, 106, 107 are also shown. The other user devices 105, 106, 107 might typically also be smart phones. As is known in the art, servers, such as the messaging server and web server include one or more processors, memory and a communication interface for communicating with other network elements and devices.

Using, for example, a public land mobile network (PLMN) the user device 101 is able to communicate data to and from the plurality of user devices 105, 106, 107. The plurality of user devices 105, 106, 107 are able upload data to and download data from the messaging website 104 via browsing software installed in the user devices 105, 106, 107 and using, for example, a connection provided by a PLMN to the internet via an access point node (APN) within the PLMN. Figure 1 also shows a social network system 108. The messaging website 104 and the social networking system can exchange data via an internet connection using, for example, a suitable application programming interface (API) associated with the social network system 108.

Generally, the system shown in Figure 1 enables positive messages to be sent to a user via the user device 101 at times when the user will be more likely to benefit from the positive message. The system is operated in conjunction with the app 102 running on the user device 101 and the messaging server 103.

During a configuration phase, the app enables a message group to be created comprising other users the user of the user device may know. A message group list (i.e. a list comprising data identifying other users) can be created by the app 104 first collecting contact data stored on, or accessible by, the mobile device 101 and presenting this to the user and then enabling a user to select which of other users the user wishes to be invited to join the message group. Once the message group list is created, the app 102 controls the user device to transmit an invitation message to the other users of the message group list using the contact data. In some examples the message group list is generated in one go and the invitation messages are sent out at substantially the same time. In other examples, a user may add users to the message group list over an extended period of time and every time a user is added, an invitation message is sent out.

In some examples, the app 102 enables the user to enter a greeting message with the invitation message. For example:

"Hi guys, John here, follow this link to leave a message to help me quit smoking!"

The invitation messages are received at the other user devices 105, 106, 107 associated with the other users. Typically, the invitation message includes an encrypted uniform resource locator (URL) which when entered into a browser, directs a user of the message group to a webpage of the messaging website 104 that is associated with the user of the user device. The messaging website 104 provides a means by which a user of the message group can leave a positive message for the user of the user device 101. Typically, the webpage may display further guidance information about the type of positive message to be left. For example:

"Hi, John has requested that you leave a message to help him quit smoking.

Leave an inspirational message!"

The user of the message group may then leave a positive message encouraging the user not to smoke. For example:

"Don't do it John! Quitting smoking was the best thing I have ever done! "

Once a positive message has been left by a user of the message group, the messaging website sends this to the messaging server 103 along with an indication of the user who left the message. Separately, during the configuration phase, the user of the user device 101 enters behaviour timeline data via a user interface of the app 102. The behaviour timeline data indicates times at which a user is prone to perform a behaviour. Typically, "performing a behaviour" means undertaking a potentially harmful act. In some examples the user can select from one of a predefined number of behaviours. Shown below is a table representative of behaviour timeline data collected for a user who has indicated that their behaviour is smoking.

Behaviour: SMOKING; ·/ = usually tempted to smoke a cigarette

Time Monday Tuesday Wednesday Thursday Friday Saturday Sunday

0000

0100 0200 ·/

0300

0400

0500

0600

0700

0800

0900

1000

1100

1200

1300

1400

1500

1600

1700

1800

1900

2000

2100

2200

2300

Once entered, the app 102 controls the user device 101 to transmit the behaviour timeline data to the messaging server. In some examples, the behaviour timeline data sent to the messaging server comprises a data structure comprising a list of days during a week, and for each day during the week a list of times as indicated in the table above. In other examples the behaviour timeline data is structured similarly but rather than comprising a list of days during the week, instead comprises a list of days over any suitable period (along with corresponding times for each day in the period), for example a ten-day period, a 28-day period etc. In this way the timeline of the user performing the behaviour can be captured over any appropriate period.

The messaging server 103 holds account data for the user of the user device 101. The account data includes the behaviour timeline data and the positive messages provided by users of the message group. The account data may also include a record of the message group list generated by the user. This will be transmitted from the app 102 via the user device 101 to the messaging server 103 once it has been created by the user.

During operation (i.e. during an operational phase), the messaging server 103 sends one or more positive messages to the user device 101 at times

corresponding to times the behaviour timeline indicates a user will perform the behaviour. The positive message includes the message left by one of the message group users and, for example, an indication of the message group user who left the message. For example, with reference to the table above, at or just before 0700 on Mondays, the messaging server sends a positive message to the user device 101 collected from the messaging website 104. For example: Message from Bob: Don't do it John! Quitting smoking was the best thing I have ever done!

Figures 2 to 6 provide flow diagrams illustrating an example of the configuration and operation of the system shown in Figure 1 in more detail.

Figure 2 provides a flow diagram illustrating an app launch process which is performed when the app 102 is run on the user device 101.

At a first step S201 the app is launched, for example by a user selecting an icon on a display of the user device 101. At second step S202 it is determined if a user account associated with the app 102 has already been set up for a user of the smart device 101 or if this is the first time the app 102 has been launched and/or no user account has yet been set up for the user of the smart device 101.

If it is determined at step S202 that a user account has already been set up, the process moves to a third step S203 where the user can login to an account. This may be performed by displaying a login screen on the user device 101 requiring the user to enter a user name and password, or may be an automatic log in requiring no further input from the user.

Once the login step S203 is completed, the process moves to a fourth step S204 in which the user can begin using the messaging service. At this fourth step S204 a communication session is established between the messaging server 103 and the user device 101 such that the user can access information, messages and associated content relating to their account stored on the messaging server 103.

If at step S202 it is determined that no user account has yet been set up, the process moves to a create account step S205. The create account step S205 is explained in further detail below. Once the create account step has been completed, the process moves to the fourth step S204 as described above, whereby the user can begin using the messaging service.

Figure 3 provides a flow diagram illustrating in more detail the sign up process step S205 described above with reference to Figure 2.

As a preliminary step (not shown), a user may enter and confirm a user name, password etc. setting up a message service account with the messaging server 103. In a first sign up step S301, an interface is displayed on the user device 101 enabling a user to select a predefined behaviour. Examples of the predefined behaviour include habits such as eating, smoking, drinking and so on. In a second sign up step S302 a user enters information via the interface on the user device 101 relating to the details of the behaviour and in particular times during the day at which the behaviour is likely to be performed. For example, if a user is prone to smoke a cigarette at 0900 hrs., 1200 hrs., 1500 hrs. and 1800 hrs., the user enters these times to the app via the user interface. In another example, if a user is prone to eat a snack at a particular time during the day, the user enters these times. This information is collected and stored as behaviour timeline data. The behaviour timeline is collected and transmitted from the user device 101 to the messaging server 103. In some examples, rather than a user entering the details of the behaviour all at one time (i.e. an estimation when they believe they are most likely to perform the behaviour), instead, for a predefined period, for example a week, the app 102 provides an interface whereby a user can log when they perform the behaviour. For example, if the behaviour in question was snacking on food, the user selects a behaviour logging icon on the user interface when they eat a snack or feel tempted to eat a snack. Alternatively, if the behaviour in questions was smoking, the user selects the behaviour logging icon when they smoke a cigarette or feel tempted to smoke a cigarette. In a third sign-up step S303, a user invites other users to join a message group for sending positive messages to the user. The invite other users step S303 is explained in more detail below.

On completion of the invite other users step S303, the process returns to the fourth step S204 shown in Figure 2, whereby the user can begin using the messaging service. Figure 4 provides a flow diagram illustrating in more detail the process enabling a user to invite other users to join a message group. When the process is performed a list of user contacts stored on, or at least accessible by, the user device 101 is generated and presented as a list to the user via the user interface displayed on the user device 101. The user can then select from this list which users from the user contact list they wish to join the message group and send to these users an invitation to join the message group.

At a first step S401 the app 102 accesses contact data available to the user device 101. Typically the contact data comprises data a) identifying the other users and b) data allowing messages to be routed to the other users. For example, for each individual user the contact data might include an identifier (e.g. a name) and means of sending a message to the other user (e.g. a telephone number, email address, social network identifier (e.g. a Twitter or Facebook username) and so on.

The app 102 can access the contact data using any suitable means. The app 104 can access contacts stored in the user device itself in the user device's contact directory. Typically the contact directory is a section of the user device's memory in which details such as telephone numbers, email addresses and so on are stored with corresponding user identifiers (e.g. user names).

In some examples the user device 101 will also have installed thereon one or more social network apps. The social network apps typically include a list of contacts which are stored on the user device 101, or are at least accessible by the user device 101 via the social network app communicating, for example, with a social network system. The app 102 can also access contacts from these social network apps too. The app 102 may incorporate code developed using one or more software development kits (SDKs) and/or APIs associated with a particular social network. This allows the app 102 to access contact data from the social network apps.

In some examples the way in which contacts are gathered will depend on the type of operating system running on the user device 101.

A first operating system (OS1) may allow a single SDK to be used to gain access to contact data from multiple social network apps. For example, the operating system iOS 6 includes the so-called "SocialKit Framework" to access contact data from social network apps such as Facebook and Twitter.

Another operating system (OS2) may require an SDK/API to be provided by each individual social network for the corresponding social network app. For example, the operating system Android may require an SDK/API for Facebook and an SDK/API for Twitter to allow the contact details from these respective social networking apps to be accessed. In some examples, getting contact details in this way may require the user to be logged in using a social networking app on the user device.

As illustrated in Figure 4, part of the invite other users process can include a decision step S402 during which it is determined which operating system is being used and thus which SDK to use to access the contact data of the social network apps.

Once the contact data has been accessed as described above in steps S401 and S402, a list of contacts is generated by the app 102 at a third step S403. This can be presented to the user via a user interface as a list potential other users that the user can invite to join the message group. At a fourth step S404, the user can select which other users to invite to join the message group by selecting an icon (for example a check box) next to the other user's name/details in the list. In some examples, the message group list is generated once all the other users that the user wishes to join the message group have been selected.

In some examples, the step S404 need not happen as a once only step, and the user can add other users to the message group list at any time. In this example, steps S405 and S406, discussed below, are repeated every time an other user is added to the message group list.

At a fifth step S405, the user can enter text or other content via the user interface displayed on the user device 101 to be included in the invitation message. The message text can be a generic message to all of the selected other users or individual messages for some or all of the selected other users.

At a sixth step S406, the app 102 controls the user device 101 to send a message to the selected other users in the generated message group list including the invitation message entered during the fifth step S405. As explained above, the contact details typically specify telephone numbers, email addresses and so on enabling the messages to be received by the other user devices 105, 106, 107.

Typically, the message includes an encoded Uniform Resource Locator (URL) and may also include a greeting message as described above. The message may be sent in any suitable format, for example as an email or a short message service (SMS) message.

In some examples instead of, or in addition to, generating the message group from the user's contacts, the app 102 may enable the user to choose a predefined message group comprising a predefined group of users. In this case the user need not transmit invitation messages, and may instead receive positive messages from a pre-stored set of positives messages already stored on the message server 103.

Figure 5 provides a flow diagram illustrating a positive message creation process undertaken when an invitation message, sent from the user device 101 as described with reference to the process shown in Figure 4, is received at one of the other plurality of user devices 105, 106, 107.

At a first step S501, the invitation message is received at one of the plurality of other user devices 105, 106, 107. When the invitation message is received, typically a notification will be displayed on the other user device and a user of the other user device will be able to view the invitation message. The invitation message may include the text or other content entered by the user at step S405 as discussed above.

In a second step S502, when the invitation message is displayed, the user can select the encoded URL which will direct a browser running on the user device to an address corresponding to a page generated by the messaging website 104. The webpage generated by the messaging website 104 and presented to the user (i.e. the recipient of the invitation message) on completion of step S502 comprises a login page. This requires the user to create an account with the messaging service. At a third step S503 the user can choose to create an account using an existing social network account, for example a Facebook account. In order to achieve this, the user would typically select an icon on the webpage that activates a control based on an appropriate social network SDK and enables a messaging system account to be created using a social network account. This can be a "create account with Facebook" button as is known in the art. In this case, the process moves to a fourth step S504 whereby the user is authenticated via their social network account and then, with no further input required from the user, a messaging system account is created at a fifth step S505 using information from the user's account with the social network. Referring back to Figure 1, it can be seen that this step is enabled by the interface between the messaging website 104 and the social network system 108.

However, if it is not possible, or the user does not wish to create a messaging account with a social network account, the user can complete step S505 by creating an account manually (e.g. by entering a username and password and so on. The user may also provide contact details such as an email address).

In either case, at a final step S506 once an account has been created, the user is prompted to leave a positive message via the webpage of the messaging website 104. Once the positive message has been provided by the user, this is

communicated from the messaging website 104 to the messaging server 103.

The positive message can be provided in any suitable format. For example simple text, icon (e.g. an "emoticon") a picture or photograph, a video and/or audio file and so on.

Once the sign up process shown in Figure 3, the invite other users process shown in Figure 4 and the positive message creation process shown in Figure 5 have been performed, the various outputs of these processes are sent to and stored in the messaging server 103.

More specifically, once a user of the smart device 101 on which the app 102 is running has created an account and once other users have been invited to join the message group and leave positive messages, the behaviour timeline data and the positive messages entered by other users via the messaging website 104 are communicated to and stored in the messaging server 103. Figure 6 provides a flow chart illustrating a process performed by the system shown in Figure 1.

At a first decision step S601a, if a user has requested a positive message be sent, the process moves to a send positive message step S602 whereby one or more of the positive messages provided by the other users is transmitted to the user device 101. The user can request a positive message by, for example, selecting an icon on the user interface of the app. At a second decision step S601b, if the current time corresponds with a time on the behaviour timeline that the user has indicated they perform the behaviour, the process moves to the send positive message step S602 and one or more of the positive messages provided by the other users is transmitted to the user device 101. In some examples, at the second decision step S601b, if the current time corresponds with a predetermined period of time before the time on the behaviour timeline that the user has indicated they perform the behaviour, the process moves to the send positive message step S602 and one or more of the positive messages provided by the other users is transmitted to the user device 101. In this alternative, positive messages can be received a short period of time (e.g. 5 or 10 minutes) before a user has indicated they might perform the behaviour.

At the send positive message step, the message can be transmitted from the messaging server 103 to the user device 101 using any appropriate technique. In some examples, the message is sent from the messaging server 103 and displayed to the user via a user interface provided by the app 102. In other words the receipt and display of the positive message is controlled by the app 102 running on the user device 101. In other examples, the message may be sent from the messaging server as an SMS message via a PLMN to the user device 101. In this way, the receipt and display of the positive message is independent of the app 102 running on the user device 101.

Figures 7a to 7n provide illustrations of exemplary screen shots of a user interface of the app 102 displayed on the user device 101. The exemplary screen shots relate to an example of the messaging system being used to support a user not to over eat.

Figure 7a shows a screen shot of an example of a sign-in page of the app 102; Figure 7b shows a screen shot of an example of a behaviour selection page of the app 102; Figure 7c shows a first screen shot of a behaviour timeline capturing page of the app 102; Figure 7d shows a second screen shot of a behaviour timeline capturing page of the app 102; Figure 7e shows a screen shot of a first message group generating page of the app 102; Figure 7f shows a screen shot of a second message group generating page of the app 102 in which a list of contacts from a phone directory of the user device 101 is displayed; Figure 7g shows a screen shot of a second message group generating page of the app 102 in which the user is given the option to log in to a Facebook account to collect contact data for the message group; Figure 7h shows a screen shot of a third message group generating page of the app 102 in which the user is given the option to log in to a Twitter account to collect contact data for the message group; Figure 7i shows an example of an invitation message page of the app 102, enabling a user to enter invitation text to be included with an invitation message sent to the message group; Figures 7j and 7k show, respectively first and second pages of the app enabling a user to join a predefined message group; Figure 71 shows an example of a home page of the app 102 including options for allowing a user to track their performance of the behaviour; Figure 7m provides a page of the app enabling a user to enter data about their current mood, and Figure 7n shows an example of a page of the app showing a diary function displaying how much the user has been performing the behaviour. Various modifications can be made to the embodiments described herein, without departing from the scope of the invention.

For example, although the user devices have been described mainly in terms of smart phones, it will be understood that other types of user devices are envisaged such as personal computers, tablets, games consoles and so on.

Furthermore, it will be understood that although the embodiments have been described in terms only of a single user receiving positive messages via a user device, the messaging server might typically be arranged to provide positive messages in the manner described above to many thousands or hundreds of thousands of users.

Furthermore, although the examples of performing a behaviour have been described mainly in terms of a user performing a potentially harmful act such smoking a cigarette or eating a snack, it will be understood that the invention can be used to encourage generally beneficial behaviour such as exercise.

Claims

1. A method of transmitting positive messages to a user device, said method comprising:

2. A method according to claim 1, further comprising transmitting one or more of the positive messages to the user device in response to a user request input to the user device.

3. A method according to claim 1 or claim 2, wherein the step of

transmitting the one or more positive messages in correspondence with the times of the behaviour timeline comprises transmitting one or more positive messages a predefined amount of time before the times of the behaviour timeline data.

4. A method according to any preceding claim, wherein the message group list is generated by collecting contact data from data stored on the user device and/or available to the user device via a data connection.

5. A method according to claim 4, wherein at least part of the message group list is generated from contact data collected from a contact directory stored on the user device.

6. A method according to claim 4 or 5, wherein generating the message group list comprises the user selecting one or more users from the collected contact data.

7. A method according to claim 4 or 5, wherein at least part of the message group list is generated from contact data collected from a social network app installed on the user device.

8. A method according to any of claims 4 to 7, wherein at least part of the message group list comprises, at least in part, a predefined message group list.

9. A method according to any previous claim, wherein the behaviour time line data comprises data entered by a user to the user device indicative of times at which the user anticipates they will perform the behaviour.

10. A method according to any of claims 1 to 9, wherein the behaviour time line data comprises data entered by a user to the user device at times corresponding to times at which they perform the behaviour, said behaviour time line data being generated over a predefined period.

11. A method according to any previous claim, further comprising receiving user input to the user device indicative of a behaviour type of the behaviour.

12. A method according to claim 11, wherein the user input is based on a selection of one behaviour type from a list of behaviour types.

13. A method according to any previous claim, wherein the positive messages include one or more of text data, picture data and audio/video data.

14. A method according to any previous claim, wherein the invitation messages comprise an encoded URL, providing a link to a messaging website, and the positive messages are entered via the messaging website.

15. A system for transmitting positive messages to a user device, said system comprising a messaging server and a user device,

said user device arranged to collect behaviour timeline data indicative of times at which a user performs a behaviour and to transmit the behaviour timeline data to the messaging server, said user device further arranged to generate a message group list comprising contact data associated with a plurality of other users and to transmit, using the contact data, an invitation message to users of a message group list requesting a positive message, and said messaging server arranged to receive and store the behaviour timeline data and receive and store positive messages from the users of the message group list, wherein

said messaging server is arranged to transmit one or more of the positive messages to the user device in correspondence with the times of the behaviour timeline data.

16. A messaging server arranged to receive and store behaviour timeline data from a user device indicative of times at which a user of the user device performs a behaviour, and to receive and store positive messages from users of a message group list, wherein said messaging server is arranged to transmit one or more of the positive messages to the user device at times corresponding with the times of the behaviour timeline data.

17. A user device arranged to collect behaviour timeline data indicative of times at which a user of the user device performs a behaviour and to transmit the behaviour timeline data to a message server, said user device further arranged to generate a message group list comprising contact data associated with a plurality of other users and to transmit, using the contact data, invitation messages to the plurality of other users of the message group list, wherein said user device is further arranged to receive positive messages from the other users of the message group list transmitted from the message server at times corresponding with the times of the behaviour timeline data.

18. A method of receiving positive messages at a user device from a messaging server, said method comprising

transmitting the behaviour timeline data to the message server, generating a message group comprising contact data associated with a plurality of other users and transmitting, using the contact data, invitation messages to the plurality of other users of the message group list, and

receiving positive messages from the other users of the message group transmitted from the message server at times corresponding with the times of the behaviour timeline data.

19. A computer program comprising computer executable instructions which when run on a computer causes the computer to perform the method of claim 18.

20. A computer program product comprising a computer program as defined in claim 19.