WO2013033785A1

WO2013033785A1 - Mobile communication device event scheduling

Info

Publication number: WO2013033785A1
Application number: PCT/AU2012/001070
Authority: WO
Inventors: George RADMAN; Carmen KHAIRO; Sergio PASAPERA
Original assignee: Calert Pty Ltd
Priority date: 2011-09-08
Filing date: 2012-09-07
Publication date: 2013-03-14

Abstract

According to one aspect, there is provided a system for mobile communication device event scheduling, the system comprising: a scheduler server; and a plurality of communication devices in communication with the schedule server across a communications network, wherein the system is operable to receive, at the scheduler server, event data relating to an event; determine one or more target mobile communication devices of the plurality of mobile communication devices in accordance with the event data; send, across the communications network, event schedule data from the scheduler server to the one or more target mobile communication devices; update, in the one or more target mobile communication devices, an event of a calendar application in accordance with the event schedule data. Advantageously, the system is adapted for the event schedule management for a plurality of mobile communication devices across a communications network. In this manner, the system may be used to schedule one or more events for a plurality of users and manage the rescheduling, acceptance of and declines of the one or more events.

Description

OBILE COMMUNICATION DEVICE EVENT SCHEDULING

Field of the Invention

The present invention relates to a system, scheduler server, mobile communication device and computer readable storage medium for mobile communication device event scheduling.

Background

According to existing arrangements, appointment scheduling typically takes place manually, For example, a dentist may have their administration phone one or more patients to arrange consultations and the like. Such an arrangement is disadvantageous on account of the time involved in setting up such consultations, especially where a patient has to reschedule.

Attempts have been made to automate the scheduling process. For example, some existing arrangements are configured to send out a short message service (SMS) or email message and the like to schedule an appointment. However, such systems are unreliable in that the message may go astray or that the attendee may forget about the meeting at the time of the meeting. Furthermore, the attendee has no means to accept, decline or reschedule the event other than phoning the event organizer to do so.

As such, a need therefore exists for means which will overcome or substantially ameliorate at least some of the above and other deficiencies of the prior art, or to at least provide an alternative.

It is to be understood that, if any prior art information is referred to herein, such reference does not constitute an admission that the information forms part of the common general knowledge in the art, in Australia or any other country.

Summary

The invention seeks to provide a system, scheduler server, mobile communication device and computer readable storage medium for mobile communication device event scheduling which will overcome or substantially ameliorate at least some of the deficiencies of the prior art, or to at least provide an alternative.

According to one aspect, there is provided a system for mobile communication device event scheduling, the system comprising:

a scheduler server; and

a plurality of communication devices in communication with the schedule server across a communications network, wherein the system is operable to:

receive, at the scheduler server, event data relating to an event; determine one or more target mobile communication devices of the plurality of mobile communication devices in accordance with the event data;

send, across the communications network, event schedule data from the scheduler server to the one or more target mobile communication devices;

update, in the one or more target mobile communication devices, an event of a calendar application in accordance with the event schedule data.

Advantageously, the system is adapted for the event schedule management for a plurality of mobile communication devices across a communications network. In this manner, the system may be used to schedule one or more events for a plurality of users and manage the rescheduling, acceptance of and declines of the one or more events.

Preferably, the event schedule data is a push notification.

Advantageously, the system is adapted for propagating event schedule data across the communications network in an efficient manner, negating the need for persistent connections, polling and the like on the part of the one or more one or more target mobile communication devices.

Preferably, the push notification is delivered using a delivery technique selected from the set of delivery techniques comprising unicast and multicast delivery techniques.

Advantageously, the system is adapted to not only schedule an event for a single user, but also for more than one user who may be grouped by user type and the like.

Preferably, the calendar application is a native calendar application.

Advantageously, the system leverages the existing calendar capabilities of the mobile communication device allowing for integrated functions such as alerting and the like.

Preferably, the event data comprises mobile communication device identification data, and wherein the system is operable to determine one or more target mobile communication devices in further accordance with the mobile communication device identification data.

Advantageously, the event data may be associated with a mobile communication device in accordance with such identification as phone number, Media Access Control address (MAC address), IP address and the like.

Preferably, the system is further operable to:

receive, at the scheduler server, event update data relating to the event

send, across the communications network, event schedule update data from the scheduler server to the one or more target mobile communication devices; and update, in the one or more target mobile communication devices, the event of the calendar application in accordance with the event schedule update data.

Advantageously, the system is configured for the updating of events in one or more remote mobile communication devices.

Preferably, the event schedule update data comprises event identification data identifying the event.

Advantageously, the system is configured each event may be updated in accordance with event identification data.

Preferably, the system is further operable to:

receive, at least one of the one or more target mobile communication devices, user option data representing a user's option in relation to the event;

send, across the communications network, the user option data from the at least one of the one or more target mobile communication devices to the scheduler server; and

update, at the schedule server, the event data in accordance with the user option data. Preferably, the user option data represents options selected from the set of options comprising accept, cancel or reschedule options.

Advantageously, the system is configured such that users of the plurality of mobile communication devices may accept, cancel or reschedule the event. In this manner, the scheduler may receive confirmation of the attendance of a user before the start date.

Preferably, the system is further operable to:

generate, at the schedule server, event reminder data in accordance with the event data;

send, across the communications network, the event reminder data from the scheduler server to the at least one of the one or more target mobile communication devices.

Advantageously, the system is adapted for generating reminders at the one or more target mobile communication devices so as to reduce the number of likely missed meetings.

Preferably, the event schedule data comprises parameters selected from the set of parameters comprising event data, event duration, event subject, event message parameters.

Advantageously, the system is configured such that one or more data relating to the event may be conveyed to the one or more target mobile communication devices. Preferably, the event schedule data comprises Extensible Markup Language.

According to another aspect, there is provided a scheduler server for mobile communication device event scheduling, comprising:

a processor for processing digital data;

a memory device for storing digital data including computer program code and being coupled to the processor via a bus;

a data interface for sending and receiving digital data and being coupled to the processor via the bus; and

wherein the processor is controlled by the computer program code to:

receive, via the data interface, event data relating to an event;

determine one or more target mobile communication devices of a plurality of mobile communication devices in accordance with the event data;

send, via the data interface, event schedule data to the one or more target mobile communication devices.

Preferably, the event schedule data is a push notification.

Preferably, the processor is further controlled by the computer program code to:

receive, via the data interface, event update data relating to the event; and

send, via the data interface, event schedule update data from the scheduler server to the one or more target mobile communication devices.

receive, via the data interface, user option data representing a user's option in relation to the event; and

update the event in accordance with the user option data. Preferably, the user option data represents options selected from the set of options comprising accept, cancel or reschedule options.

generate event reminder data in accordance with the event data; and

send, via the data interface, the event reminder data from the scheduler server to the at least one of the one or more target mobile communication devices.

According to another aspect, there is provided a mobile communication device for event scheduling, comprising:

a processor for processing digital data;

a communications network interface for sending and receiving digital data and being coupled to the processor via the bus; and

wherein the processor is controlled by the computer program code to:

receive, via the communications network interface, event schedule data;

update an event of a calendar application in accordance with the event schedule data mobile communication device.

Preferably, the event schedule data is a push notification.

Preferably, the calendar application is a native calendar application.

receive, via the communications network interface, event schedule update data from a scheduler server; and

update the event of the calendar application in accordance with the event schedule update data. Preferably, the event schedule update data comprises event identification data identifying the event.

receive user option data representing a user's option in relation to the event;

send, via the communications network interface, the user option data to a scheduler server.

Preferably, the user option data represents options selected from the set of options comprising accept, cancel or reschedule options.

receive, via the communications network interface, event reminder data from the scheduler server to the at least one of the one or more target mobile communication devices; generate an alert in accordance with the event reminder data.

According to another aspect, there is provided a computer readable storage medium for execution by a scheduler server for mobile communication device event scheduling, the computer readable storage medium having computer program code instructions recorded thereon, the computer program code instructions being executable by a computer and comprising:

instructions for receiving, via a data interface, event data relating to an event;

instructions for determining one or more target mobile communication devices of plurality of mobile communication devices in accordance with the event data;

instructions for sending, via the data interface, event schedule data from the computer readable storage medium to the one or more target mobile communication devices.

Preferably, the event schedule data is a push notification.

Preferably, the event data comprises mobile communication device identification data, and wherein the system is operable to determine one or more target mobile communication devices in further accordance with the mobile communication device identification data. Preferably, the computer readable storage medium further comprises:

instructions for receiving, via the data interface, event update data relating to the event; and

instructions for sending, via the data interface, event schedule update data from the computer readable storage medium to the one or more target mobile communication devices.

Preferably, the computer readable storage medium further comprises:

instructions for receiving, via the data interface, user option data representing a user's option in relation to the event; and

instructions for updating the event in accordance with the user option data.

Preferably, the computer readable storage medium further comprises:

instructions for generating event reminder data in accordance with the event data; and instructions for sending, via the data interface, the event reminder data from the computer readable storage medium to the at least one of the one or more target mobile communication devices.

According to another aspect, there is provided a computer readable storage medium for execution by a mobile communication device for mobile communication device event scheduling, the computer readable storage medium having computer program code instructions recorded thereon, the computer program code instructions being executable by a computer and comprising:

instructions for receiving, via a communications network interface, event schedule data; instructions for updating an event of a calendar application in accordance with the event schedule data

Preferably, the event schedule data is a push notification. Preferably, the push notification is delivered using a delivery technique selected from the set of delivery techniques comprising unicast and multicast delivery techniques.

Preferably, the calendar application is a native calendar application.

Preferably, the computer readable storage medium further comprises:

instructions for receiving, via the communications network interface, event schedule update data from a scheduler server; and

instructions for updating the event of the calendar application in accordance with the event schedule update data.

Preferably, the computer readable storage medium further comprises:

instructions for receive user option data representing a user's option in relation to the event;

instructions for send, via the communications network interface, the user option data to a scheduler server.

Preferably, the computer readable storage medium further comprises:

instructions for receiving, via the communications network interface, event reminder data from the scheduler server to the at least one of the one or more target mobile communication devices;

instructions for generating an alert in accordance with the event reminder data.

It should be noted that the web server, client computing device and the computer readable storage medium provide the same or similar advantages as the advantages provided by the corresponding computer implemented method, some of which are described herein. Additionally the web server and/or client computing device provides the advantage of deployment across a computer network, such as the Internet, providing distribution, access and economy of scale advantages. Furthermore, the computer readable storage medium provides further advantages, such allowing the deployment of computer instructions for installation and execution by one or more computing devices.

Other aspects of the invention are also disclosed.

Brief Description of the Drawings

Notwithstanding any other forms which may fall within the scope of the present invention, preferred embodiments of the invention will now be described, by way of example only, with reference to the accompanying drawings in which:

Fig. 1 shows a computing device on which the various embodiments described herein may be implemented in accordance with an embodiment of the present invention;

Fig. 2 shows a network of computing devices on which the various embodiments described herein may be implemented in accordance with an embodiment of the present invention;

Fig. 3 shows a system implemented method for mobile communication device event scheduling in accordance with another preferred embodiment of the present invention;

Fig. 4 shows an exemplary graphical user interface (GUI) comprising a calendar comprising one or more calendar cells representing one or more time periods, such as days, weeks, months, years and the like in accordance with another embodiment of the present invention;

Fig. 5 shows an exemplary GUI for inputting event data relating to the event in accordance with another embodiment of the present invention;

Fig. 6 shows an exemplary GUI of a native calendar of a mobile communication device in accordance with another embodiment of the present invention; and

Fig. 7 shows an exemplary GUI allowing a user to accept, cancel, reschedule the event and the like in accordance with another embodiment of the present invention. Detailed Description of Specific Embodiments

It should be noted in the following description that like or the same reference numerals in different embodiments denote the same or similar features.

Fig. 1 shows a computing device 100 on which the various embodiments described herein may be implemented. In particular the steps of the method of mobile communication device event scheduling as shown in Fig. 3 may be implemented as computer program code instructions executable by the computing device 100. The computer program code instructions may be divided into one or more computer program code instruction libraries, such as dynamic link libraries (DLL), wherein each of the libraries performs a one or more steps of the method. Additionally, a subset of the one or more of the libraries may perform graphical user interface tasks relating to the steps of the method.

The device 100 comprises semiconductor memory 110 comprising volatile memory such as random access memory (RAM) or read only memory (ROM). The memory 100 may comprise either RAM or ROM or a combination of RAM and ROM.

The device 100 comprises a computer program code storage medium reader 130 for reading the computer program code instructions from computer program code storage media 120. The storage media 120 may be optical media such as CD-ROM disks, magnetic media such as floppy disks and tape cassettes or flash media such as USB memory sticks.

The device further comprises I/O interface 140 for communicating with one or more peripheral devices. The I/O interface 140 may offer both serial and parallel interface connectivity. For example, the I/O interface 140 may comprise a Small Computer System Interface (SCSI), Universal Serial Bus (USB) or similar I/O interface for interfacing with the storage medium reader 130. The I/O interface 140 may also communicate with one or more human input devices (HID) 160 such as keyboards, pointing devices, joysticks and the like. The I/O interface 140 may also comprise a computer to computer interface, such as a Recommended Standard 232 (RS-232) interface, for interfacing the device 100 with one or more personal computer (PC) devices 190. The I/O interface 140 may also comprise an audio interface for communicate audio signals to one or more audio devices 1050, such as a speaker or a buzzer.

The device 100 also comprises a network interface 170 for communicating with one or more computer networks 180. The network 180 may be a wired network, such as a wired Ethernet™ network or a wireless network, such as a Bluetooth™ network or IEEE 802.1 1 network. The network 180 may be a local area network (LAN), such as a home or office computer network, or a wide area network (WAN), such as the Internet or private WAN.

The device 100 comprises an arithmetic logic unit or processor 1000 for performing the computer program code instructions. The processor 1000 may be a reduced instruction set computer (RISC) or complex instruction set computer (CISC) processor or the like. The device 100 further comprises a storage device 1030, such as a magnetic disk hard drive or a solid state disk drive.

Computer program code instructions may be loaded into the storage device 1030 from the storage media 120 using the storage medium reader 130 or from the network 180 using network interface 170. During the bootstrap phase, an operating system and one or more software applications are loaded from the storage device 1030 into the memory 110. During the fetch-decode-execute cycle, the processor 1000 fetches computer program code instructions from memory 110, decodes the instructions into machine code, executes the instructions and stores one or more intermediate results in memory 100.

In this manner, the instructions stored in the memory 110, when retrieved and executed by the processor 1000, may configure the computing device 100 as a special-purpose machine that may perform the functions described herein.

The device 100 also comprises a video interface 1010 for conveying video signals to a display device 1020, such as a liquid crystal display (LCD), cathode-ray tube (CRT) or similar display device.

The device 100 also comprises a communication bus subsystem 150 for interconnecting the various devices described above. The bus subsystem 150 may offer parallel connectivity such as Industry Standard Architecture (ISA), conventional Peripheral Component Interconnect (PCI) and the like or serial connectivity such as PCI Express (PCIe), Serial Advanced Technology Attachment (Serial ATA) and the like.

Fig. 2 shows a system for mobile communication device event scheduling. The system 200 comprises a scheduler server 205 and plurality of mobile communication devices 210 in communication with the schedule server 205 across a communications network 215.

The communications network 215 may be selected from any communications network appropriate to the application, but is preferably a mobile communication device communications network such as a GSM network. Note that in other embodiments the communications network 215 may take the form of other wireless networks such as an IEEE 802.11 network.

Fig. 3 shows a system implemented method 300 for mobile communication device event scheduling. The method 300 is executed by one or more computing devices 100 and in particular plurality of mobile communication devices 210 connected across the communications network 215 to one or more scheduler server 205 as substantially shown in Fig. 2.

The method 300 starts at step 305 where the system 200 is operable to receive, at the scheduler server 205, event data relating to an event. Figs. 4 and 5 show exemplary graphical user interfaces (GUI) for inputting event data relating to an event. The GUIs may be displayed on a display device 1020 attached to the schedule server 205. In an alternative embodiment, the schedule server 205 may be provided with webserver capabilities, such that the GUIs may be viewable within an Internet browser across the Internet.

In Fig. 4, there is shown a GUI 400 comprising a calendar 405. The calendar 405 comprises one or more calendar cells 410 representing one or more time periods, such as days, weeks, months, years and the like. Each calendar cells 410 is user selectable, initiating the process of scheduling an event. As will be further described below, each calendar cell 410 may comprise one or more indicia indicating not only the occurrence of the event, but also the status such as accepted, declined etc. GUI 400 will typically be generated by the schedule server 205.

Further, referring to Fig. 5, GUI 500 shows a further exemplary embodiment for inputting the event data relating to the event. The GUI 500 comprises input fields for inputting data such as:

The mobile number of the target mobile communication device 210 such that the event data comprises mobile communication device 210 identification data such that the system 200 is operable to determine one or more target mobile communication devices 200 in further accordance with the mobile communication device 210 identification data. Note that in certain embodiments, as opposed to inputting a mobile phone number for a single mobile communication device 210, one or more mobile communication device 210 may be grouped into a group for group sending of event schedules.

The date 510 and time 515 of the event. Additionally, the end time or the duration of the vent may be further specified.

The title or subject 520 of the event.

The location 525 of the event.

A message or note for the event 530.

In an alternative embodiment, the schedule server 205 is adapted to interface with third party calendar or event scheduling software. For example, such third party calendar or event scheduling software may be provided with an add-in application, wherein the add-in application is adapted for listening for calendar and event schedule creation, update and delete events so as to receive event data relating to an event. Note that in certain instances, a separate schedule server 210 therefore is not needed, wherein the functionality described herein is executed by the add-in application operating on a desktop computing device 100 or the like. The GUI further comprises submit button 535 for scheduling the event according to the details as specified. Note that in further embodiments other event detail input fields may be provided depending on the application.

At step 310, the schedule server 205 is adapted to determine one or more target mobile communication devices 210 of the plurality of mobile communication devices 210 in accordance with the event data. The target mobile communication devices 210 may be determined in a number of ways. In a first embodiment, the telephone number of a single mobile communication device 210 may be provided such that schedule event data may be sent to the mobile communication device 210 in accordance with the number. Note that other means other than a telephone number may be used to identify a mobile communication device 210, such as an IP address and the like.

In a second embodiment, one or more mobile communication device 210 may be allocated to a group. For example, a dentistry practice may group several patients into a single mobile communication device 210 group. In this manner, the practice, in using the GUI 500 is able to select the single mobile communication device 210 group such that the schedule data is sent to each mobile communication device 210 of the mobile communication device 210 group. In this manner, the system 200 is adapted for sending the push notification delivery techniques comprising unicast and multicast delivery techniques.

At step 315, the schedule server 205 is adapted for sending, across the communications network 215, event schedule data from the scheduler server 205 to the one or more target mobile communication devices 210.

In a preferred embodiment, the event schedule data is a push notification; that is: where the event schedule data transaction is initiated by the schedule server 205. Various push notification services may be used in this regard, such as, for example, using the Apple™ Push Notification Service, Android™ C2DM Service or the Urban Airship push notification service for Blackberry™. It should be noted that various forms of push technologies may be used including HTTP server push, Pushlet, Long polling, Flash™ XMLSocket relays and the like.

Exemplary functions for generating register and unregister GET URL strings using the above services are as follows:

private static String formUnRegisterRequest(String bpasUrl, String appld,

String token) {

StringBuffer s b = new StringBuffer(bpasUrl);

sb.append( mss/PD_subDereg?");

sb.append("serviceid=").append(appld);

if (token != null && token. Iength() > 0) {

sb.append("&").append(token); }

return sb.toString();

}

private static String formRegisterRequest(String bpasUrl, String appld,

String token) {

StringBuffer sb = new StringBuffer(bpasUrl);

sb.append( mss/PD_subReg?");

sb.append("serviceid=").append(appld);

sb.append("&osversion=").append(Devicelnfo.getSoftwareVersion());

sb.append("&model=").append(Dev icelnfo.getDeviceName());

if (token != null && token. Iength() > 0) {

sb.append("&"). append (token);

}

return sb.toString() ;

}

In a less preferred embodiment, other types less conventional push technologies may be used such as short message service and Simple Mail Transfer Protocol techniques.

Furthermore, it should be noted however, that in certain other less preferred embodiments, each mobile communication device 210 may be adapted to employ pull techniques to obtain the event schedule data, such as periodic polling of the schedule server 205 to ascertain the existence of any event schedule data.

In certain embodiments the event schedule data may comprise extensible markup language (XML). Exemplary event schedule data for an event may comprise the following:

<?xml version='1.0' standalone- yes'?>

<parameter name='title'>Lakeside reception centre</parameter>

<parameter name='note'>Please ensure that you bring 10% deposit to

confirm booking</parameter>

In one embodiment, the event schedule data comprises payment data for the purposes of facilitating an electronic payment. In the above example, the event schedule data comprises payment data relating to a bank account number, a BSB number, an invoice number and an amount for payment. In this manner, the payment data may be used by the user ofr the purposes of payment, such as for payment of the appointment in advance. The invoice number may be used when making the payment such that the schedule server 205 may verify that the payment has been made before marking the appointment as confirmed. In a preferred embodiment, the event listener 220 is adapted for initiating a banking application on the mobile communication device 210 in accordance with the payment data for the purposes of at least partially automating the payment process.

At step 320, each of the target mobile communication devices 210 are adapted to update, in the one or more target mobile communication devices, an event of a calendar application in accordance with the event schedule data. In a preferred embodiment, each mobile communication device 210 comprises a calendar update application that has an event listener 220 for trapping the schedule event data push notifications. In this manner, the event listener 220 is adapted to update a calendar of the mobile communication device 210 in accordance with the schedule event data. In a preferred embodiment, the calendar is a native calendar 225 of the mobile communication device 210, offering greater integration with the functionality of the mobile communication device 210 as opposed to a stand-alone calendar application.

Typically, each user will download and install on each mobile communication device 210 the calendar update application. Upon installation of the calendar update application, the mobile communication device 210 will send device token id and name and mobile number data to the schedule server 205 for recordal in the database 270 of the schedule server 205. In this manner, the schedule server 205 will be able to send schedule data to each registered mobile communication device 210. The calendar update application may run as a background process, listening out for the event schedule data receipt event. In one embodiment, the calendar update application may be adapted to send confirmation data back to the schedule server 205, such that the scheduler is able to receive confirmation that the event has been received by the user and placed in the user's calendar.

Referring now to Fig. 6, there is shown an exemplary GUI 600 of a native calendar of a mobile communication device 210. As can be seen from the figure, the GUI 6 comprises a calendar portion, wherein an event indicia 605 is shown in the calendar portion. Furthermore, additional information 610 relating to the event may also be shown.

Referring to Fig. 7, there is shown an exemplary GUI 700 allowing a user to accept, cancel, reschedule the event and the like. In the example shown, there is an Edit button 610, allowing a user to edit the event details. In this manner, where an event has been updated on the native calendar 225, the event listener application 200 may be adapted to trap the event update event, and initiate a data transfer back to the schedule server 205 comprising the new event parameters. In this manner, the schedule server 205 may update the display of the event to the event scheduler, indicating the new parameters. In a preferred embodiment, the system 200 is able to manage event updates. For example, where a person has an appointment at 2pm at a dentistry practice, and the dentist is running late, the dentistry practice may use the system 200 to update the event relating to the persons appointment, such as by moving the appointment to an hour later. As will be describe in further detail below, the person will have the option of confirming his or her attendance of the appointment or declining the appointment. Specifically, in this manner, the system 200 is further operable to receive, at the scheduler server 205, event update data relating to the event, send, across the communications network 215, event schedule update data from the scheduler server 215 to the one or more target mobile communication devices 210 and update, in the one or more target mobile communication devices 210, the event of the calendar application in accordance with the event schedule update data.

The event schedule update data may comprise event identification data identifying the event to be updated. In this manner, where each event has allocated a unique event identification number, the event schedule update data may refer to the unique event identification number in the event update data, such as, for example::

<?xml version='1.0' standalone- yes'?>

</event>

As alluded to above, the system 200 is adapted for user feedback on a scheduled event. For example, where a user has been invited to an event, such as a dentist appointment, the user may not be available for at least one of the date, time or location proposed. In this manner, the user may, using the input interface of the mobile communication device 210, enter option data accept, cancel or reschedule options. Other options may be made available depending on the application.

In this manner, the system 200 is further operable to receive, at least one of the one or more target mobile communication devices 210, user option data representing a user's option in relation to the event; send, across the communications network 215, the user option data from the at least one of the one or more target mobile communication devices 210 to the scheduler server 205; and update, at the schedule server 205, the event data in accordance with the user option data.

Referring again to GUI 410 there is shown the calendar 405 representation comprising one or more event indicia 415 of the event. In this manner, the event indicia 415 may be adapted according to the status of the event. For example, where a scheduler schedules an event, the event indicia 415 may be represented in a first colour indicating that the event has been tentatively scheduled and that the event schedule data has been send to plurality of mobile communication devices 210. Hereafter, once the plurality of mobile communication devices 210 have confirmed the meeting (or at least a portion thereof), the event indicia 415 may be represented in a second colour, indicating that the event has been accepted. Similarly, if the event has been declined, the event indicia 415 may be represented in a third colour. Furthermore, where a recipient selects the option to reschedule the event, the event, as displayed in the calendar 405 representation may be moved to the new proposed date and time, having an indication or input means allowing for the scheduler to similarly accept or again propose a new time. In this manner, an event may be rescheduled a number of times before the parties are in agreement. Note that in one specific embodiment, the event schedule data may comprise availability data so as to advantageously mitigate unnecessary communication between parties for the purposes of rescheduling an event.

In a further preferred embodiment, the system 200 is adapted for reminding event attendees of upcoming events, so as to advantageously reduce the number of missed events. For example, the schedule server 205 may be adapted to remind attendees within a certain timeframe of an upcoming event, such as one month, week, or day before the event. Furthermore, the schedule server 205 may be adapted to send data for processing by the event listener 220 for the purposes of generating a reminder on the mobile communication device 210. In another less preferred embodiment, the schedule server 205 may be adapted to use alternative communication means, such as by short message service or e-mail communication.

As such, in this embodiment, the system 220 is adapted to generate, at the schedule server 205, event reminder data in accordance with the event data; send, across the communications network 215, the event reminder data from the scheduler server 205 to the at least one of the one or more target mobile communication devices 210 such that the at least one of the one or more target mobile communication devices 210 may play out a reminder.

Note that in a further embodiment, the event listener 220, in receiving the initial event schedule data may be operable to configure the native calendar 225 with a reminder such that the native calendar 225 generated an alert without event reminder having to be sent.

Referring specifically now to the scheduler server 205, the scheduler server 205 comprises a processor 1000 for processing digital data; a memory device 110 for storing digital data including computer program code and being coupled to the processor via a bus 150; a data interface (140,170) for sending and receiving digital data and being coupled to the processor 1000 via the bus 150. As such, the processor 1000 of the scheduler server 205 is controlled by the computer program code to receive, via the data interface (140,170), event data relating to an event; determine one or more target mobile communication devices 210 of the plurality of mobile communication devices 210 in accordance with the event data; and send, via the data interface (140,170), event schedule data to the one or more target mobile communication devices. In this manner, the event schedule data may be a push notification and delivered using a delivery technique selected from the set of delivery techniques comprising unicast and multicast delivery techniques. Furthermore, the event data may comprise mobile communication device identification data, and wherein the system is operable to determine one or more target mobile communication devices in further accordance with the mobile communication device identification data.

In a further preferred embodiment, the processor 1000 of the scheduler server 205 is further controlled by the computer program code to receive, via the data interface, event update data relating to the event; and send, via the data interface, event schedule update data from the scheduler server to the one or more target mobile communication devices. In this manner, the event schedule update data may comprise event identification data identifying the event.

In a further preferred embodiment, the processor 1000 of the scheduler server 205 is further controlled by the computer program code to receive, via the data interface (140,170), user option data representing a user's option in relation to the event; and update the event data in accordance with the user option data. In this manner, the user option data may represent options selected from the set of options comprising accept, cancel or reschedule options.

In a further preferred embodiment, the processor 1000 of the scheduler server 205 is further controlled by the computer program code to generate event reminder data in accordance with the event data; and send, via the data interface (140,170), the event reminder data from the scheduler server 205 to the at least one of the one or more target mobile communication devices. In this manner, the event schedule data may comprise parameters selected from the set of parameters comprising event date, event duration, event subject, event message parameters.

Referring now specifically to the mobile communication device 210, the mobile communication device 210 comprises a processor 1000 for processing digital data; a memory device 110 for storing digital data including computer program code and being coupled to the processor via a bus 150; a communications network interface 180 for sending and receiving digital data and being coupled to the processor via the bus 150. As such, the processor 1000 of the mobile communication device 210 is controlled by the computer program code to receive, via the communications network interface 170, event schedule data, update an event of the calendar application 225 in accordance with the event schedule data. In this manner, the event schedule data may be a push notification and delivered using a delivery technique selected from the set of delivery techniques comprising unicast and multicast delivery techniques. Furthermore, the calendar application 225 may be a native calendar application 225.

In a further preferred embodiment, the processor 1000 of the mobile communication device 210 is further controlled by the computer program code to receive, via the communications network interface 170, event schedule update data from the scheduler server 205 to the one or more target mobile communication devices; and update the event of the calendar application in accordance with the event schedule update data. In this manner, the event schedule update data may comprise event identification data identifying the event.

In a further preferred embodiment, the processor 1000 of the mobile communication device 210 is further controlled by the computer program code to receive user option data, via an I/O interface 140 representing a user's option in relation to the event; and send, via the communications network interface 170, the user option data to a scheduler server. In this manner, the user option data may represent options selected from the set of options comprising accept, cancel or reschedule options.

In a further preferred embodiment, the processor 1000 of the mobile communication device 210 is further controlled by the computer program code to receive, via the communications network interface 170, event reminder data from the scheduler server to the at least one of the one or more target mobile communication devices and generate an alert in accordance with the event reminder data. Furthermore, the event schedule data may comprise parameters selected from the set of parameters comprising event date, event duration, event subject, event message parameters. Interpretation

In accordance with

As described herein, 'in accordance with' may also mean 'as a function of and is not necessarily limited to the integers specified in relation thereto.

Composite items

As described herein, 'a computer implemented method' should not necessarily be inferred as being performed by a single computing device such that the steps of the method may be performed by more than one cooperating computing devices. Similarly objects as used herein such as 'web server', 'server', 'client computing device', 'computer readable medium' and the like should not necessarily be construed as being a single object, and may be implemented as a two or more objects in cooperation, such as, for example, a web server being construed as two or more web servers in a server farm cooperating to achieve a desired goal or a computer readable medium being distributed in a composite manner, such as program code being provided on a compact disk activatable by a license key downloadable from a computer network.

Wireless:

The invention may be embodied using devices conforming to other network standards and for other applications, including, for example other WLAN standards and other wireless standards. Applications that can be accommodated include IEEE 802.11 wireless LANs and links, and wireless Ethernet.

In the context of this document, the term "wireless" and its derivatives may be used to describe circuits, devices, systems, methods, techniques, communications channels, etc., that may communicate data through the use of modulated electromagnetic radiation through a non-solid medium. The term does not imply that the associated devices do not contain any wires, although in some embodiments they might not. In the context of this document, the term "wired" and its derivatives may be used to describe circuits, devices, systems, methods, techniques, communications channels, etc., that may communicate data through the use of modulated electromagnetic radiation through a solid medium. The term does not imply that the associated devices are coupled by electrically conductive wires.

Processes:

Unless specifically stated otherwise, as apparent from the following discussions, it is appreciated that throughout the specification discussions utilizing terms such as "processing", "computing", "calculating", "determining", "analysing" or the like, refer to the action and/or processes of a computer or computing system, or similar electronic computing device, that manipulate and/or transform data represented as physical, such as electronic, quantities into other data similarly represented as physical quantities.

Processor:

In a similar manner, the term "processor" may refer to any device or portion of a device that processes electronic data, e.g., from registers and/or memory to transform that electronic data into other electronic data that, e.g., may be stored in registers and/or memory. A "computer" or a "computing device" or a "computing machine" or a "computing platform" may include one or more processors. The methodologies described herein are, in one embodiment, performable by one or more processors that accept computer-readable (also called machine-readable) code containing a set of instructions that when executed by one or more of the processors carry out at least one of the methods described herein. Any processor capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken are included. Thus, one example is a typical processing system that includes one or more processors. The processing system further may include a memory subsystem including main RAM and/or a static RAM, and/or ROM.

Computer-Readable Medium:

Furthermore, a computer-readable carrier medium may form, or be included in a computer program product. A computer program product can be stored on a computer usable carrier medium, the computer program product comprising a computer readable program means for causing a processor to perform a method as described herein.

Networked or Multiple Processors:

In alternative embodiments, the one or more processors operate as a standalone device or may be connected, e.g., networked to other processor(s), in a networked deployment, the one or more processors may operate in the capacity of a server or a client machine in server- client network environment, or as a peer machine in a peer-to-peer or distributed network environment. The one or more processors may form a web appliance, a network router, switch or bridge, or any machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine.

Note that while some diagram(s) only show(s) a single processor and a single memory that carries the computer-readable code, those in the art will understand that many of the components described above are included, but not explicitly shown or described in order not to obscure the inventive aspect. For example, while only a single machine is illustrated, the term "machine" shall also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein.

Additional Embodiments:

Thus, one embodiment of each of the methods described herein is in the form of a computer- readable carrier medium carrying a set of instructions, e.g., a computer program that are for execution on one or more processors. Thus, as will be appreciated by those skilled in the art, embodiments of the present invention may be embodied as a method, an apparatus such as a special purpose apparatus, an apparatus such as a data processing system, or a computer-readable carrier medium. The computer-readable carrier medium carries computer readable code including a set of instructions that when executed on one or more processors cause a processor or processors to implement a method. Accordingly, aspects of the present invention may take the form of a method, an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of carrier medium (e.g., a computer program product on a computer-readable storage medium) carrying computer- readable program code embodied in the medium.

Carrier Medium:

The software may further be transmitted or received over a network via a network interface device. While the carrier medium is shown in an example embodiment to be a single medium, the term "carrier medium" should be taken to include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that store the one or more sets of instructions. The term "carrier medium" shall also be taken to include any medium that is capable of storing, encoding or carrying a set of instructions for execution by one or more of the processors and that cause the one or more processors to perform any one or more of the methodologies of the present invention. A carrier medium may take many forms, including but not limited to, non-volatile media, volatile media, and transmission media.

Implementation:

It will be understood that the steps of methods discussed are performed in one embodiment by an appropriate processor (or processors) of a processing (i.e., computer) system executing instructions (computer-readable code) stored in storage. It will also be understood that the invention is not limited to any particular implementation or programming technique and that the invention may be implemented using any appropriate techniques for implementing the functionality described herein. The invention is not limited to any particular programming language or operating system.

Means For Carrying out a Method or Function

Furthermore, some of the embodiments are described herein as a method or combination of elements of a method that can be implemented by a processor of a processor device, computer system, or by other means of carrying out the function. Thus, a processor with the necessary instructions for carrying out such a method or element of a method forms a means for carrying out the method or element of a method. Furthermore, an element described herein of an apparatus embodiment is an example of a means for carrying out the function performed by the element for the purpose of carrying out the invention. Connected

Similarly, it is to be noticed that the term connected, when used in the claims, should not be interpreted as being limitative to direct connections only. Thus, the scope of the expression a device A connected to a device B should not be limited to devices or systems wherein an output of device A is directly connected to an input of device B. It means that there exists a path between an output of A and an input of B which may be a path including other devices or means. "Connected" may mean that two or more elements are either in direct physical or electrical contact, or that two or more elements are not in direct contact with each other but yet still co-operate or interact with each other.

Embodiments:

Reference throughout this specification to "one embodiment" or "an embodiment" means that a particular feature, structure or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Thus, appearances of the phrases "in one embodiment" or "in an embodiment" in various places throughout this specification are not necessarily all referring to the same embodiment, but may. Furthermore, the particular features, structures or characteristics may be combined in any suitable manner, as would be apparent to one of ordinary skill in the art from this disclosure, in one or more embodiments.

Similarly it should be appreciated that in the above description of example embodiments of the invention, various features of the invention are sometimes grouped together in a single embodiment, figure, or description thereof for the purpose of streamlining the disclosure and aiding in the understanding of one or more of the various inventive aspects. This method of disclosure, however, is not to be interpreted as reflecting an intention that the claimed invention requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment. Thus, the claims following the Detailed Description of Specific Embodiments are hereby expressly incorporated into this Detailed Description of Specific Embodiments, with each claim standing on its own as a separate embodiment of this invention.

Furthermore, while some embodiments described herein include some but not other features included in other embodiments, combinations of features of different embodiments are meant to be within the scope of the invention, and form different embodiments, as would be understood by those in the art. For example, in the following claims, any of the claimed embodiments can be used in any combination. Specific Details

In the description provided herein, numerous specific details are set forth. However, it is understood that embodiments of the invention may be practiced without these specific details. In other instances, well-known methods, structures and techniques have not been shown in detail in order not to obscure an understanding of this description.

Terminology

In describing the preferred embodiment of the invention illustrated in the drawings, specific terminology will be resorted to for the sake of clarity. However, the invention is not intended to be limited to the specific terms so selected, and it is to be understood that each specific term includes all technical equivalents which operate in a similar manner to accomplish a similar technical purpose. Terms such as "forward", "rearward", "radially", "peripherally", "upwardly", "downwardly", and the like are used as words of convenience to provide reference points and are not to be construed as limiting terms.

Different Instances of Objects

As used herein, unless otherwise specified the use of the ordinal adjectives "first", "second", "third", etc., to describe a common object, merely indicate that different instances of like objects are being referred to, and are not intended to imply that the objects so described must be in a given sequence, either temporally, spatially, in ranking, or in any other manner.

Comprising and Including

In the claims which follow and in the preceding description of the invention, except where the context requires otherwise due to express language or necessary implication, the word "comprise" or variations such as "comprises" or "comprising" are used in an inclusive sense, i.e. to specify the presence of the stated features but not to preclude the presence or addition of further features in various embodiments of the invention.

Any one of the terms: including or which includes or that includes as used herein is also an open term that also means including at least the elements/features that follow the term, but not excluding others. Thus, including is synonymous with and means comprising.

Scope of Invention

Thus, while there has been described what are believed to be the preferred embodiments of the invention, those skilled in the art will recognize that other and further modifications may be made thereto without departing from the spirit of the invention, and it is intended to claim all such changes and modifications as fall within the scope of the invention. For example, any formulas given above are merely representative of procedures that may be used. Functionality may be added or deleted from the block diagrams and operations may be interchanged among functional blocks. Steps may be added or deleted to methods described within the scope of the present invention.

Although the invention has been described with reference to specific examples, it will be appreciated by those skilled in the art that the invention may be embodied in many other forms.

Industrial Applicability

It is apparent from the above, that the arrangements described are applicable to the software industry.

Claims

1. A system for mobile communication device event scheduling, the system comprising: a scheduler server; and

receive, at the scheduler server, event data relating to an event;

determine one or more target mobile communication devices of the plurality of mobile communication devices in accordance with the event data;

2. A system as claimed in claim 1 , wherein the event schedule data is a push notification.

3. A system as claimed in claim 1, wherein the push notification is delivered using a delivery technique selected from the set of delivery techniques comprising unicast and multicast delivery techniques.

4. A system as claimed in claim 1 , wherein the calendar application is a native calendar application.

5. A system as claimed in claim 1 , wherein the event data comprises mobile communication device identification data, and wherein the system is operable to determine one or more target mobile communication devices in further accordance with the mobile communication device identification data.

6. A system as claimed in claim 1 , wherein the system is further operable to:

receive, at the scheduler server, event update data relating to the event;

send, across the communications network, event schedule update data from the scheduler server to the one or more target mobile communication devices; and

update, in the one or more target mobile communication devices, the event of the calendar application in accordance with the event schedule update data.

7. A system as claimed in claim 1 , wherein the event schedule update data comprises event identification data identifying the event.

8. A system as claimed in claim 1 , wherein the system is further operable to: receive, at least one of the one or more target mobile communication devices, user option data representing a user's option in relation to the event;

update, at the schedule server, the event data in accordance with the user option data.

9. A system as claimed in claim 1 , wherein the user option data represents options selected from the set of options comprising accept, cancel or reschedule options.

10. A system as claimed in claim 1 , wherein the system is further operable to:

generate, at the schedule server, event reminder data in accordance with the event data; and

11. A system as claimed in claim 1 , wherein the event schedule data comprises parameters selected from the set of parameters comprising event data, event duration, event subject, event message parameters.

12. A system as claimed in claim 1 , wherein the event schedule data comprises Extensible Markup Language.

13. A scheduler server for mobile communication device event scheduling, comprising: a processor for processing digital data;

a memory device for storing digital data including computer program code and being coupled to the processor via a bus; and

a data interface for sending and receiving digital data and being coupled to the processor via the bus, wherein the processor is controlled by the computer program code to: receive, via the data interface, event data relating to an event;

14. A scheduler server as claimed in claim 13, wherein the event schedule data is a push notification.

15. A scheduler server as claimed in claim 13, wherein the push notification is delivered using a delivery technique selected from the set of delivery techniques comprising unicast and multicast delivery techniques.

16. A scheduler server as claimed in claim 13, wherein the event data comprises mobile communication device identification data, and wherein the system is operable to determine one or more target mobile communication devices in further accordance with the mobile communication device identification data.

17. A scheduler server as claimed in claim 13, wherein the processor is further controlled by the computer program code to:

receive, via the data interface, event update data relating to the event; and

18. A scheduler server as claimed in claim 13, wherein the event schedule update data comprises event identification data identifying the event.

19. A scheduler server as claimed in claim 13, wherein the processor is further controlled by the computer program code to:

update the event in accordance with the user option data.

20. A scheduler server as claimed in claim 13, wherein the user option data represents options selected from the set of options comprising accept, cancel or reschedule options.

21. A scheduler server as claimed in claim 13, wherein the processor is further controlled by the computer program code to:

generate event reminder data in accordance with the event data; and

22. A scheduler server as claimed in claim 13, wherein the event schedule data comprises parameters selected from the set of parameters comprising event data, event duration, event subject, event message parameters.

23. A mobile communication device for event scheduling, comprising:

a processor for processing digital data; a memory device for storing digital data including computer program code and being coupled to the processor via a bus; and

a communications network interface for sending and receiving digital data and being coupled to the processor via the bus, wherein the processor is controlled by the computer program code to:

receive, via the communications network interface, event schedule data; and update an event of a calendar application in accordance with the event schedule data mobile communication device.

24. A mobile communication device as claimed in claim 23, wherein the event schedule data is a push notification.

25. A mobile communication device as claimed in claim 23, wherein the push notification is delivered using a delivery technique selected from the set of delivery techniques comprising unicast and multicast delivery techniques.

26. A mobile communication device as claimed in claim 23, wherein the calendar application is a native calendar application.

27. A mobile communication device for event scheduling as claimed in claim 23, wherein the processor is further controlled by the computer program code to:

update the event of the calendar application in accordance with the event schedule update data.

28. A mobile communication device as claimed in claim 23, wherein the event schedule update data comprises event identification data identifying the event.

29. A mobile communication device for event scheduling as claimed in claim 23, wherein the processor is further controlled by the computer program code to:

receive user option data representing a user's option in relation to the event; and send, via the communications network interface, the user option data to a scheduler server.

30. A mobile communication device as claimed in claim 23, wherein the user option data represents options selected from the set of options comprising accept, cancel or reschedule options.

31. A mobile communication device for event scheduling as claimed in claim 23, wherein the processor is further controlled by the computer program code to:

32. A mobile communication device as claimed in claim 23, wherein the event schedule data comprises parameters selected from the set of parameters comprising event data, event duration, event subject, event message parameters.

33. A computer readable storage medium for execution by a scheduler server for mobile communication device event scheduling, the computer readable storage medium having computer program code instructions recorded thereon, the computer program code instructions being executable by a computer and comprising:

34. A computer readable storage medium as claimed in claim 33, wherein the event schedule data is a push notification.

35. A computer readable storage medium as claimed in claim 33, wherein the push notification is delivered using a delivery technique selected from the set of delivery techniques comprising unicast and multicast delivery techniques.

36. A computer readable storage medium as claimed in claim 33, wherein the event data comprises mobile communication device identification data, and wherein the system is operable to determine one or more target mobile communication devices in further accordance with the mobile communication device identification data.

37. A computer readable storage medium as claimed in claim 33, further comprising:

38. A computer readable storage medium as claimed in claim 33, wherein the event schedule update data comprises event identification data identifying the event.

39. A computer readable storage medium as claimed in claim 33, further comprising:

instructions for updating the event in accordance with the user option data.

40. A computer readable storage medium as claimed in claim 33, wherein the user option data represents options selected from the set of options comprising accept, cancel or reschedule options.

41. A computer readable storage medium as claimed in claim 33, further comprising:

42. A computer readable storage medium as claimed in claim 33, wherein the event schedule data comprises parameters selected from the set of parameters comprising event data, event duration, event subject, event message parameters.

43. A computer readable storage medium for execution by a mobile communication device for mobile communication device event scheduling, the computer readable storage medium having computer program code instructions recorded thereon, the computer program code instructions being executable by a computer and comprising:

44. A computer readable storage medium as claimed in claim 43, wherein the event schedule data is a push notification.

45. A computer readable storage medium as claimed in claim 43, wherein the push notification is delivered using a delivery technique selected from the set of delivery techniques comprising unicast and multicast delivery techniques.

46. A computer readable storage medium as claimed in claim 43, wherein the calendar application is a native calendar application.

47. A computer readable storage medium for event scheduling as claimed in claim 43, further comprising:

48. A computer readable storage medium as claimed in claim 43, wherein the event schedule update data comprises event identification data identifying the event.

49. A computer readable storage medium for event scheduling as claimed in claim 43, further comprising:

instructions for receive user option data representing a user's option in relation to the event; and

50. A computer readable storage medium as claimed in claim 43, wherein the user option data represents options selected from the set of options comprising accept, cancel or reschedule options.

51. A computer readable storage medium for event scheduling as claimed in claim 43, further comprising:

instructions for receiving, via the communications network interface, event reminder data from the scheduler server to the at least one of the one or more target mobile communication devices; and

52. A computer readable storage medium as claimed in claim 43, wherein the event schedule data comprises parameters selected from the set of parameters comprising event data, event duration, event subject, event message parameters.