WO2009057987A1

WO2009057987A1 - Smart client application using message formatting technique and mobile database

Info

Publication number: WO2009057987A1
Application number: PCT/MY2007/000070
Authority: WO
Inventors: Latifah Mohamed; Azrol Arshad; Ahmed Ali; Ida Zuraida Zakaria; Rozanudin Samsudin; Ahmad Tajuddin Samsudin; Zaidi Mukhtar
Original assignee: Telekom Malaysia Berhad
Priority date: 2007-10-31
Filing date: 2007-10-31
Publication date: 2009-05-07

Abstract

A system (1) is described for processing a message that updates a schedule. The system comprises one or more host units (2,4) each comprising means for formatting a message to include specified destination information and means for causing the formatted message to be sent to a mobile data communication device (12) of the data communication system (12). The system (1) also comprises one or more mobile data communication devices (12) each comprising (a) means for receiving messages, (b) a message inbox (34) arranged to processing received messages, (c) a scheduler application (28) arranged to maintain a schedule, (d) a listener module (30) for checking messages received by said receiving means for the presence of the specified destination information and, if the specified destination information is detected, diverting the received message to the scheduler application (28).

Description

Smart Client Application Using Message Formatting Technique and Mobile Database

Field of the invention

The present invention relates to a system and method for transferring information from a host system to a mobile data communication device. In particular, the invention relates to techniques for updating appointment schedules by transferring data using a message formatting technique and using a mobile database.

Background of the invention

Improved communication techniques and associated software have made great changes in the ways in which business may be conducted. Increasingly, information resources are available wherever a person is working.

Thus, a worker with a mobile computational device can access and download information as required. One useful application that is becoming widely used is a calendar function that can record details of scheduled meetings and tasks. However, as such meeting arrangements frequently change, there is a need for efficient techniques for updating calendar information.

In some existing systems, information is transferred from a host system to a user's mobile system through "synchronisation" techniques in which information is warehoused or stored on a host system and transmitted to the mobile device only in response to a user request.

There is an ongoing need for efficient and user-friendly systems for updating and transferring information to mobile devices.

Summary of the invention

According to a first aspect of the invention there is provided a method of processing a message sent to a mobile data communication device having a message inbox for received messages, the method comprising: (a) receiving the message;

(b) checking the message for the presence of specified destination information; and, if the specified destination information is detected,

(c) diverting the message from the message inbox to a scheduler module of the mobile communication device.

According to a second aspect of the invention there is provided a mobile data communication device comprising:

(a) means for receiving messages;

(b) a message inbox arranged to processing received messages;

(c) a scheduler application arranged to maintain a schedule; and characterised in that the device comprises:

(d) a listener module for checking messages received by said receiving means for the presence of specified destination information and, if the specified destination information is detected, diverting the received message to the scheduler application.

According to a further aspect of the invention there is provided a host unit in a data communication system comprising:

means for formatting a message to include specified destination information; and

means for causing the formatted message to be sent to a mobile data communication device of the data communication system,

wherein the specified destination information indicates to the mobile data communication device that the sent message is to be diverted from an inbox of the device to a scheduler application of the device. O

According to a further aspect of the invention there is provided a system for processing a message updating a schedule, the system comprising:

one or more host units each comprising:

means for causing the formatted message to be sent to a mobile data communication device of the data communication system; and

one or more mobile data communication devices each comprising:

(a) means for receiving messages;

(b) a message inbox arranged to processing received messages;

(c) a scheduler application arranged to maintain a schedule;

(d) a listener module for checking messages received by said receiving means for the presence of the specified destination information and, if the specified destination information is detected, diverting the received message to the scheduler application.

According to a further aspect of the invention there is provided a computer program product comprising machine-readable program code recorded on a machine- readable recording medium, for controlling the operation of a mobile data communication device on which the program code executes to perform a method of processing a message sent to the mobile data communication device having a message inbox for received messages, the method comprising:

(a) checking the message for the presence of specified destination information; and, if the specified destination information is detected, (b) diverting the message from the message inbox to a scheduler module of the mobile communication device.

According to a further aspect of the invention there is provided a computer program comprising machine-readable program code for controlling the operation of a mobile data communication device on which the program code executes to perform a method of processing a message sent to the mobile data communication device having a message inbox for received messages, the method comprising:

(a) checking the message for the presence of specified destination information; and, if the specified destination information is detected,

(b) diverting the message from the message inbox to a scheduler module of the mobile communication device.

Brief description of the drawings

Embodiments of the invention will now be described with reference to the drawings, in which:

Fig 1 is a schematic block diagram of a system in which an appointment schedule may be dynamically transferred to a mobile device;

Fig 2 is a schematic block diagram showing some of the functionality of the mobile device of Fig 1 ;

Fig 3 is a flow diagram of a method for preparing a message to send to the mobile device;

Fig 4A shows a flow diagram of a method performed on the mobile device to receive and process the message;

Fig 4B shows schematically an example of a message sent to the mobile device; Fig 5 is a flow diagram of a method of logging into the appointment management system running on the system of Fig. 1;

Fig 6 shows a method whereby a personal assistant selects between system features;

Fig 7 is a flow diagram illustrating a graphic user interface enabling a personal assistant to edit appointment information;

Fig 8 is a flow diagram of a graphic user interface application for changing the profile of a personal assistant;

Fig 9 is a flow diagram of a method enabling a personal assistant to set a messaging occurrence;

Fig 10 is a flow diagram of a method implemented on the mobile device to receive and view a message;

Fig 11 shows a flow diagram of a method whereby a user of the mobile device logs into the appointment management system;

Fig 12 is a flow diagram of a method enabling the user of the mobile device to amend appointment information;

Fig 13 is a flow diagram of a method enabling the user of the mobile device to update his or her profile;

Fig 14 is a flow diagram of a method enabling the user of the mobile device to set a messaging occurrence;

Fig 15 is a flow diagram of a method enabling a system administrator to log into the appointment management system;

Fig 16 is a flow diagram of a method enabling the system administrator to update appointment information; Fig 17 is a flow diagram of a method enabling a system administrator to update profile information;

Fig 18 is a flow diagram of a method enabling the system administrator to update group information; and

Fig 19 is a flow diagram of a method enabling the system administrator to set messaging occurrence information.

Detailed description of the embodiments

The system described herein enables a first user, for example a personal assistant, to update entries in an appointment management system. A second user of the system is enabled to retrieve and manage the appointment information in a systematic manner. The second user may, for example, be a manager who uses a mobile device such as a mobile phone or personal digital assistant (PDA) to receive and manage appointment schedule information wherever a wireless communication link is available.

Fig 1 shows a schematic overview of an operating environment in which the appointment management system may be implemented.

The first user, or personal assistant, has access to a computational device 2 which may, for example, be a standard desktop computer. The personal assistant unit 2 is in data communication with a local area network (LAN) 6, enabling, for example, communication within a company. Although a single personal assistant unit 2 is shown, it will be understood that in practice there may be many such units in the system 1.

There may also be one or more computational units 4 for use by a system administrator. The units 4 are typically standard computer units.

The local area network 6 is in data communication with a more widespread communication network such as the Internet 8. The appointment management system operates as software running on the personal assistant unit 2, administrator unit 4 and also the mobile device 12. There may also be a database in data communication with the LAN 6 for storing information related to the appointment management system.

Information relating to the appointment management system may be transferred via LAN 6 and Internet 8 to an interface 10 to a wireless network communication system. In turn, the wireless network conveys messages to and from a mobile device 12 which may, for example, be used by a manager or other representative of the company using the appointment management system.

Fig 2 shows a schematic view of some of the functionality of the mobile device 12. The mobile device 12 has a processor 20 capable of running software applications. The functions include software for receiving and processing short messaging system (SMS) messages. Such messages may, for example, be organised in an inbox 34 to enable the user of the device 12 to review received SMSs. In addition, other functions performed by software running on the processor 20 include a scheduler application 28, a listener module 30 and an attachment engine 32. These functional blocks will be described in more detail below.

In addition, the mobile device 12 includes a data storage unit 22 and a display 24. In addition, the mobile device 12 includes a user interface 26. The user interface 26 may include a key pad, microphone, track ball or other means for entering information.

Fig 3 shows a flow diagram of a method 100 for sending a message containing appointment information to a user of the mobile device 12. In an initial process a first user, for example a personal assistant, keys in information relating to the appointment schedule at the personal assistant unit 2 or administrator unit 4. Various forms of electronic document may also be attached to the appointment as an electronic attachment.

Then, in process 104, software running on the personal assistant unit 2 or administrator unit 4 formats the appointment schedule data into a suitable SMS format. The SMS header is formatted to enable the SMS message to be diverted to the scheduler application 28 in the mobile device. In one arrangement the User Data Header (UDH) of the SMS is reformatted. An example of the UDH is:

060504xxxxyyyy

where xxxx is the destination port in hex, and yyyy is the source port in hex. In one arrangement the process 104 specifies the destination port number in xxxx and, since the source port is not important in the described implementation, the source port is replaced with zeros.

An example of a complete format of the SMS body and SMS header is:

"http://127.0.0.1 :8800/Send%20Binary%20Message%20Other.htm?PhoneNumber =" & app_manager_mobileno & "&UNUSED=on&UDH=06050413880000&Data=" & app_date & "%23+" & appjime & "%23+" & appjitle & "%23" & app_alert & "%23+" & app_venue & "%23+" & app_details & "%23+" & app_attach_url & "&PID=0&DCS=0&Submit=Submit&Binary=1"

where the destination phone number of the mobile device 12 is defined in

'appjnanagerjmobileno¹ and the UDH is 06050413880000, ie the destination port is 1388. The data in the SMS includes 'app_date^J which represents the appointment date, ^*app_time' which represents the appointment time, 'app_title' which represents the appointment title, 'app_alert' which represents the alert flag, 'app_venue' which represents the appointment venue, 'app_details' which represents the appointment details, and 'app_attach_url' which provides an address for an appointment attachment. In one arrangement the attachment is defined by a URL.

Fig 4B shows schematically the content 150 of the appointment SMS prepared for sending to the mobile device 12.

Then, in process 106, the formatted SMS message is pushed via the LAN 6, internet 8 and interface 10 over a wireless connection to the mobile device 12. "Pushing" implies that the message is sent automatically to the mobile device 12 upon the occurrence of a triggering event within the appointment management system. This contrasts with a "pull" system in which the mobile device 12 requests that information be transferred to it.

Fig 4 shows a flow diagram giving an overview of the operation of the mobile device 12 when an SMS message containing appointment management information is received. In a first process 122 of the method 120, the mobile device 12 detects the arrival of an SMS message. Then, in process 124 the information in the formatted SMS header is read by the listener module 30. If the header identifies a match for the specified port number (for example 1388), the listener module causes the SMS to be diverted to the scheduler application 28 before the SMS reaches the default inbox 34.

This diversion separates out the appointment management information from the standard SMSs received by the mobile device 12. This overcomes a problem that may arise where many SMSs are received, and the user of the mobile device 12 finds it difficult to differentiate between SMSs relating to the appointment management system and ordinary SMSs. In one arrangement, the formatted header information specifies a specific port number of the mobile device 12.

The scheduler application 28 running on the processor 20 of the mobile device 12 receives the SMS message and uses the information to automatically update the appointment schedule of the user of the mobile device 12. In process 128 the updated schedule information is stored in a database on the data storage 22 of the mobile device 12.

In process 130, the scheduler application 28 formats the data for display on the display 24. The mobile device 12 receives the SMS as a single text string, which may have the format illustrated in Fig 4B. The string is placed into a loop and the data fields are extracted from the string and formatted for display, taking into account the small display 24 typically associated with the device 12. The appointment information may be displayed automatically on display 24. Alternatively, the user may be displayed on display 24 if the user chooses to open the scheduler application 28.

In process 132, if the SMS has an attachment and the user of the mobile device 12 chooses to view or play the attachment, then the scheduler application 28 may extract the URL of the attachment from the SMS string and provide the URL to the attachment engine 32. The attachment engine 32 processes the URL and initiates a request "need for connection to remote server". The attachment is downloaded to the mobile device 12 and the attachment engine 32 opens or plays the attachment, using an appropriate software application running on the processor 20. The user preferably has the option of terminating the download if desired. The software may also prompt the user to confirm that he or she wishes to download the attachment.

Different mobile devices may have different applications. Some examples of applications that can be used to play attachments are:

Sony Ericsson P910i phone

Quickword

Quicksheet

Quickpoint

Pdf+

Video player

Music player

Picture viewer

Motorola A1000

Picsel Viewer - this application is able to support the opening of various files such as doc, ppt, pdf and many more.

Nokia N9O, 6680, 6681

Quickword

Quicksheet

Quickpoint

Adobe Pdf+

Real Player

Picture viewer Process 134 is an optional step whereby an alert is output if the alarm flag 152 has been set. The alert could, for example, be a sound or a ring tone to indicate to the user that the scheduled time for an appointment is approaching.

One advantage of the described system is that a database containing the schedule information is stored on the mobile device 12. Thus, even if communications are temporarily disrupted, the user of the mobile device 12 still has access to the appointment information stored in the data storage 22. This contrasts with other systems in which access to a centralised database is required to extract and display appointment information.

The use of the one-way push communication techniques also assists in avoiding communication problems between the host system and the mobile device 12.

The appointment management system may confer different privileges to different types of users. In one arrangement, there are three types of users, as illustrated in Fig 5, namely a system administrator (SA), a manager (MGR) and a personal assistant (PA). These categories are used for convenience and may encompass other roles within an organisation. For example, the employee using the mobile device 12 may not be a manager but may, for example, be a salesman or a repair technician. Similarly, the "personal assistant" may be any person within the organisation entrusted with entering data related to appointment scheduling.

Fig 5 illustrates a log-on process that may be executed at any of the administrator unit 4, personal assistant unit 2 or mobile device 12. The process starts at 200, and in process 202 the user logs in. The user may enter a log-in ID and password in process 202. In process 204, software running on the unit used by the user determines whether the user is a system administrator, manager or personal assistant. The user type is set when a new user is added to the system or a profile is modified. Depending on the outcome of the decision in process 204, control flow proceeds either to process 206 for a system administrator, 208 for a personal assistant or 210 for a manager. The control flow 208 for a personal assistant is further illustrated in Fig 6. In process 212, software running on the unit, which may be the personal assistant unit 2, prompts the personal assistant to indicate whether they wish to amend appointment information for a manager (step 214), amend a manager profile (process 216) or update a system setting (process 218).

Fig 7 shows further steps implemented as a graphic user interface on the personal assistant unit 2 if the user selects process 214. In process 220, the personal assistant is offered a choice between managing an appointment (control goes to process 222) or adding a new appointment (process 224).

In process 222, the current appointment list is displayed on a display of the personal assistant unit. The user can then perform one of two operations. By clicking on a check box associated with an appointment (step 226) the user can choose to delete an appointment. In process 230, the software asks the user to confirm whether or not to delete the appointment. The user may make a choice by, for example, typing on a keyboard associated with the personal assistant unit 2. If the user enters "yes", then in process 232 the selected appointment is deleted. Otherwise, if the user enters "no", then the proposed deletion is cancelled in step 234 and control flow returns to process 222 in which the appointment list is displayed.

The user may elect to amend appointment details by clicking on an appointment title in process 228. Details of the selected appointment are then displayed on a display on the personal assistant unit 2. The user is then able to make changes to the appointment details in step 236, or to add an attachment to the appointment details in step 238. The attachment is then uploaded in step 242 and if the user selects a "save" option the changes are saved in process 244. The updated information and attachments may be stored on the personal assistant unit 2, or on a server or database in data communication with LAN 6.

The user is also presented in process 240 with the option of immediately sending the new amendments to a selected receiver by selecting a "send SMS" button. I o

If the user opts to add a new appointment, then in process 224 a form is displayed enabling the user to add appointment details. The user is able to enter the appointment details using, for example, a keyboard of the personal assistant unit 2 in process 246. The details may include the date, time and location of the meeting and a list of attendees. Associated attachments may include a meeting agenda or minutes of a preceding meeting. Formats such as Word™ documents or pdf files may be used. The user may then select a save option to have the new appointment stored in process 248. The system adds a new appointment to the existing appointment list.

In process 216, shown in Fig 8, the user chooses to manage a profile. In process 250, the user is offered the choice of managing his or her own profile (process 276), adding a new profile (process 268), or managing profiles of a group of people associated with the user. If the user chooses the third option, then in process 252 all the profiles relating to the user are displayed. By clicking on the name of a selected profile, a detailed view of the profile is displayed. The user can make necessary changes and click a "save" button to retain the modifications or a "back" button to go to a previous screen. By clicking on a check box, the user is given the choice in process 254 of deleting a profile. The system will then, in process 265, confirm whether or not the user does wish to delete the profile. The user has the choice of confirming the deletion in process 258 or cancelling the deletion in process 260 and then returning to the displayed profile list.

By clicking on a profile name, a profile detail is displayed in 262. The user may then enter changes in process 264 and click on the "save" button for the system to save the changes in process 266.

In one arrangement, the system is structured such that there is only a single manager associated with each personal assistant. In this case, if the user attempts to add a new profile, then in process 268 software running on the personal assistant unit checks whether the group already has a manager. If the answer is yes, then the system displays an error message indicating that "The manager's profile for this group has been already defined. Only one manager's profile is allowed for this group.". Alternatively, if no manager profile has been defined, then in step 272, an add new profile form is displayed in the unit 2 and the user is able to fill in the form and click on an "add" button to have the new profile saved in process 274.

If the user elects to amend his or her own profile, then in process 276 the profile details are displayed on the unit 2. In process 278, the user may amend the details using the keyboard or other input means of the unit 2 and then click on a save button to have the changes saved in process 280.

A profile may include the following:

• User Name • Login ID

• Password

• Group

• Designation

• Phone number • Mobile phone number

Fig 9 shows process flow when the user proceeds to process 218 to set the SMS occurrence. In the displayed arrangement there is only one link that the user can choose from, which is the "SMS occurrence" link displayed in process 282. In process 284, the user selects an appropriate setting for when SMS information should be sent to the manager's mobile device 12. The new setting is saved in process 286 by clicking on a "save" button.

In one arrangement occurrences can be set on a Daily, Weekly, and Monthly basis and at different interval time. For example, Group A may like SMSs to be sent Daily at 8.30 a.m. and Group B may specify that SMSs are to be sent weekly at 10.30 a.m.

Fig 10 is a flow chart that illustrates the use of the client applications that run on the mobile device 12. Process flow commences at 300 and in process 302, the user switches the mobile device 12 on and the device enters standby mode. In process 304, the listener module 30 checks for the arrival of an SMS relating to the appointment management system. If such an SMS arrives, then in step 306 the user is given the option of opening the scheduler application 28.

If the application is not opened, the process flow returns to the standby mode in process 302. If the application is opened then in process 308 an initial view of the appointment information is displayed on display 24. The initial content displayed includes the appointment date, time and a title associated with the appointment. Then, in process 310 the user of the mobile device 12 is given the option of exiting (process 312) or selecting to view more detail (process 314). If the detailed view is selected, then in process 316 the scheduler application 28 displays further details of the appointment on display 24. This detailed view may include the appointment venue, appointment summary details and information about attachment files relating to the appointment, for example, a meeting agenda or minutes of a meeting.

Then, in step 318 the user is given the option of viewing the attachment or attachments if there are any. If the user chooses to view the attachment, then in process 320 the attachment engine acts to download the attachment and open or play the attachment on the mobile device 12.

When a user designated as a manager logs on to the appointment management system, the steps described in Fig 11 are performed. The manager may log on using the mobile device 12 or another device such as a standard desktop computer or laptop that is in data communication with the LAN 6. If a manager has logged on, then in process 400 the manager is offered the choice of managing appointments in process 402, managing profiles in process 404 or managing system settings in process 406.

Process 402 is further described in Fig 12. On choosing process 402, the manager is given the option in process 408 of managing appointments or adding new appointments. In process 410, the existing appointment list is displayed on a display of the device used by the manager. In process 412, by clicking on a check box associated with an appointment, the manager is given the option of deleting the appointment. The system then in process 414 asks the manager to confirm whether or not he or she wishes to delete the appointment. The appointment is deleted if the manager provides confirmation in step 416. Alternatively, the manager may choose to cancel the deletion in process 418.

By clicking on an appointment title, the system in process 420 displays the appointment details. The manager may then make changes in process 422 or add an attachment in process 424. A file for attachment may be uploaded in process 428 and any changes made may be saved in process 430. The manager may elect, in process 426, to send an SMS immediately.

If the manager wishes to add a new appointment, then an appropriate form is displayed in process 432. The form is displayed on the display of a device used by the manager, for example the mobile device 12 or another computational device in data communication with the appointment management system. In process 434, the manager fills in details of the appointment on the form and, by clicking a save button, the system adds the new appointment in process 436.

Fig 13 illustrates a process flow that is available when a user designated as a manager selects process 404 to manage profiles. If the "manage profile" link is chosen, then in process 442 the system displays all profiles related to the user. By clicking on the name of the selected profile, its detailed view will be displayed in process 444. The manager may then make any changes deemed necessary in process 446 and, by clicking on a "save" button, the changes are saved in process 448. The user is directed back to the profile list when he or she clicks the "back" button. The user may also display his or her own profile details in process 450, make changes if required in process 452 and save such changes by clicking on a save button (process 454).

In the described arrangement, if the manager selects to amend system settings in process 406, there is only one link to choose from, which is the "SMS occurrence" link, which is then displayed in process 456. The page for editing the SMS occurrence is displayed and the user can select an appropriate setting which determines when SMSs should be sent from the appointment management system to the mobile device 12. The new setting may be saved by clicking on a save button and the system will store the new setting in process 460.

Fig 15 shows process steps that are followed when a user designated as a system administrator logs on to the system in process 206. Typically, the system administrator will be using an administrator unit 4, which then offers four alternatives for selection by the administrator. The administrator may choose to manage appointments (process 502), manage profiles (process 504), amend system settings (process 508) or manage groups (process 506).

Process 502 is further described in Fig 16. On choosing process 502, the system administrator is given the option, in process 510, of managing appointments or adding new appointments. In process 512 the existing appointment list is displayed on a display of the device used by the system administrator. In process 514, by clicking on a check box associated with an appointment, the system administrator is given the option of deleting the appointment. The system then in process 516 asks the system administrator to confirm whether or not he or she wishes to delete the appointment. The appointment is deleted if the system administrator provides confirmation in step 518. Alternatively, the system administrator may choose to cancel the deletion in process 520.

By clicking on an appointment title, the system in process 522 displays the appointment details. The system administrator may then make changes in process 524 or add an attachment in process 526. A file for attachment may be uploaded in process 530 and any changes made may be saved in process 532. The system administrator may elect, in process 528, to send an SMS immediately.

If the system administrator wishes to add a new appointment, then an appropriate form is displayed in process 534. The form is displayed on the display of a device used by the system administrator, for example the unit 4 or another computational device in data communication with the appointment management system. In process ,536, the system administrator fills in details of the appointment on therform and, by clicking a save button, the system adds the new appointment in process 538. Fig 17 illustrates a process flow that is available when a user designated as a system administrator selects process 504 to manage profiles. If the "manage profile" link is chosen in process 540, then in process 542 the system displays all profiles related to the administrator. By clicking on the name of the selected profile, its detailed view will be displayed in process 552. The system administrator may then make any changes deemed necessary in process 554 and, by clicking on a "save" button, the changes are saved in process 556. The user is directed back to the profile list when he or she clicks the "back" button. The user may also display his or her own profile details in process 566, make changes if required in process 568 and save such changes by clicking on a save button (process 570).

The system administrator also has rights to add or delete profiles. By clicking on a profile checkbox in process 544, the administrator is offered the option of deleting a profile. The administrator is then asked in process 546 to confirm whether or not to delete the profile. In option 548 the deletion is confirmed and in process 550 the deletion is cancelled.

If the administrator selects the option of adding a new profile, then in process 558 a form is displayed on unit 4. The system then checks, in process 560, whether the group already has a manager and personal assistant defined. If so, an error message is displayed in process 562. If not, the system adds the new profile to the existing profile link in process 564.

If option 506 is selected, the administrator is offered the choice in process 572 of managing existing groups or adding new groups. If the "Manage Group" link is chosen, then in process 574 the group lists are displayed. By clicking on the name of a selected group, the group detail is displayed in process 584 and the administrator is able to make changes in process 586. If the "Save" button is clicked the changes are saved in process 588.

If the user chooses to delete, he or she clicks on a "Delete" button displayed in process 576 after a group has been selected by clicking a group checkbox. A message window is displayed in process 578, prompting the user to confirm the deletion (process 580) or cancel the deletion (process 582). When the user has confirmed or cancelled the deletion, the system returns the user's view to the group list.

If the user chooses to add a new group by clicking on an "Add New Group" link, then in process 590 a suitable form is displayed for the user to fill out. When the fields have been completed the user clicks on an "Add" button and the new group is added to the existing group list in process 592. In one arrangement a group includes a manager and one or more personal assistants. Other group structure may also be used.

In the described arrangement, if the system administrator selects to amend system settings in process 508, there is only one link to choose from, which is the "SMS occurrence" link, which is then displayed in process 594. The page for editing the

SMS occurrence is displayed and the user can select an appropriate setting which determines when SMSs should be sent from the host system to the mobile device

12. The new setting may be saved by clicking on a save button and the system will store the new setting in process 598.

It will be understood that the invention disclosed and defined in this specification extends to all alternative combinations of two or more of the individual features mentioned or evident from the text or drawings. All of these different combinations constitute various alternative aspects of the invention.

It is apparent from the foregoing description that the arrangements are applicable to the computer and data processing industries.

Claims

Claims:

1. A method of processing a message sent to a mobile data communication device (12) having a message inbox (34) for received messages, the method comprising:

(a) receiving (122) the message;

(c) diverting (124) the message from the message inbox (34) to a scheduler module of the mobile communication device (12).

2. A method according to claim 1 , wherein the message includes schedule information relating to a scheduled appointment and the method comprises:

(d) updating (126) an appointment schedule based on the schedule information extracted from the message; and

(e) storing (128) the updated appointment schedule in data storage (22) of the mobile data communication device (12).

3. A method according to claim 1 or claim 2, wherein the message includes attachment information relating to one or more message attachments, and the method comprises:

retrieving the one or more attachments based on the attachment information extracted from the message.

4. A method according to claim 3 comprising:

displaying at least a portion of the one or more attachments on a display (24) of the mobile data communication device (12).

5. A method according to any one of the preceding claims comprising: formatting (104) the message to include the specified destination information; and

causing the formatted message to be sent (106) to the mobile data communication device (12).

6. A method according to claim 5 wherein said formatting adds a specified destination port to a header of a Short Messaging Service (SMS) message.

7. A mobile data communication device (12) comprising:

(a) means for receiving messages;

(b) a message inbox (34) arranged to processing received messages;

(c) a scheduler application (28) arranged to maintain a schedule; and characterised in that the device (12) comprises:

(d) a listener module (30) for checking messages received by said receiving means for the presence of specified destination information and, if the specified destination information is detected, diverting the received message to the scheduler application (28).

8. A mobile data communication device (12) according to claim 7 comprising:

data storage (22) operable to store the schedule maintained by the scheduler application (28).

9. A mobile data communication device (12) according to claim 7 or claim 8 comprising:

an attachment engine (32) arranged to retrieve one or more attachments associated with the received message, dependent on attachment information extracted from the received message.

10. A mobile data communication device (12) according to claim 9 comprising a display 24 for displaying information selected from (i) the schedule and (ii) at least a portion of one or more attachments.

11. A host unit (2,4) in a data communication system (1) comprising:

means for causing the formatted message to be sent to a mobile data communication device (12) of the data communication system (1),

wherein the specified destination information indicates to the mobile data communication device (12) that the sent message is to be diverted from an inbox (34) of the device (12) to a scheduler application (28) of the device(12).

12. A system (1) for processing a message updating a schedule, the system comprising:

one or more host units (2,4) each comprising:

means for causing the formatted message to be sent to a mobile data communication device (12) of the data communication system (1); and

one or more mobile data communication devices (12) each comprising:

(a) means for receiving messages;

(b) a message inbox (34) arranged to processing received messages;

(c) a scheduler application (28) arranged to maintain a schedule;

(d) a listener module (30) for checking messages received by said receiving means for the presence of the specified destination information and, if the specified destination information is detected, diverting the received message to the scheduler application (28).

13. A computer program product comprising machine-readable program code recorded on a machine-readable recording medium, for controlling the operation of a mobile data communication device (12) on which the program code executes to perform a method of processing a message sent to the mobile data communication device (12) having a message inbox (34) for received messages, the method comprising:

(b) diverting (124) the message from the message inbox (34) to a scheduler module of the mobile communication device (12).

14. A computer program comprising machine-readable program code for controlling the operation of a mobile data communication device (12) on which the program code executes to perform a method of processing a message sent to the mobile data communication device (12) having a message inbox (34) for received messages, the method comprising: