[go: up one dir, main page]

WO2013033785A1 - Planification d'événement de dispositif de communication mobile - Google Patents

Planification d'événement de dispositif de communication mobile Download PDF

Info

Publication number
WO2013033785A1
WO2013033785A1 PCT/AU2012/001070 AU2012001070W WO2013033785A1 WO 2013033785 A1 WO2013033785 A1 WO 2013033785A1 AU 2012001070 W AU2012001070 W AU 2012001070W WO 2013033785 A1 WO2013033785 A1 WO 2013033785A1
Authority
WO
WIPO (PCT)
Prior art keywords
event
data
mobile communication
schedule
communication devices
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/AU2012/001070
Other languages
English (en)
Inventor
George RADMAN
Carmen KHAIRO
Sergio PASAPERA
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
CALERT Pty Ltd
Original Assignee
CALERT Pty Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from AU2011903672A external-priority patent/AU2011903672A0/en
Application filed by CALERT Pty Ltd filed Critical CALERT Pty Ltd
Publication of WO2013033785A1 publication Critical patent/WO2013033785A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management
    • G06Q10/109—Time management, e.g. calendars, reminders, meetings or time accounting
    • G06Q10/1093—Calendar-based scheduling for persons or groups

Definitions

  • the present invention relates to a system, scheduler server, mobile communication device and computer readable storage medium for mobile communication device event scheduling.
  • 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.
  • SMS short message service
  • email message email message and the like
  • the message may go astray or that the attendee may forget about the meeting at the time of the meeting.
  • the attendee has no means to accept, decline or reschedule the event other than phoning the event organizer to do so.
  • 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.
  • a system for mobile communication device event scheduling comprising:
  • a plurality of communication devices in communication with the schedule server across a communications network, wherein the system is operable to:
  • event data relating to an event
  • the system is adapted for the event schedule management for a plurality of mobile communication devices across a communications network.
  • 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.
  • the event schedule data is a push notification.
  • 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.
  • the push notification is delivered using a delivery technique selected from the set of delivery techniques comprising unicast and multicast delivery techniques.
  • 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.
  • the calendar application is a native calendar application.
  • the system leverages the existing calendar capabilities of the mobile communication device allowing for integrated functions such as alerting and the like.
  • the event data comprises mobile communication device identification data
  • the system is operable to determine one or more target mobile communication devices in further accordance with the mobile communication device identification data.
  • 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.
  • identification such as phone number, Media Access Control address (MAC address), IP address and the like.
  • system is further operable to:
  • 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.
  • the system is configured for the updating of events in one or more remote mobile communication devices.
  • the event schedule update data comprises event identification data identifying the event.
  • each event may be updated in accordance with event identification data.
  • system is further operable to:
  • user option data representing a user's option in relation to the event
  • the event data in accordance with the user option data.
  • the user option data represents options selected from the set of options comprising accept, cancel or reschedule options.
  • the system is configured such that users of the plurality of mobile communication devices may accept, cancel or reschedule the event.
  • the scheduler may receive confirmation of the attendance of a user before the start date.
  • system is further operable to:
  • 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.
  • the event schedule data comprises parameters selected from the set of parameters comprising event data, event duration, event subject, event message parameters.
  • 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.
  • the event schedule data comprises Extensible Markup Language.
  • a scheduler server for mobile communication device event scheduling comprising:
  • 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;
  • processor is controlled by the computer program code to:
  • the event schedule data is a push notification.
  • the push notification is delivered using a delivery technique selected from the set of delivery techniques comprising unicast and multicast delivery techniques.
  • the event data comprises mobile communication device identification data
  • the system is operable to determine one or more target mobile communication devices in further accordance with the mobile communication device identification data.
  • the processor is further controlled by the computer program code to:
  • the event schedule update data comprises event identification data identifying the event.
  • the processor is further controlled by the computer program code to:
  • the user option data represents options selected from the set of options comprising accept, cancel or reschedule options.
  • the processor is further controlled by the computer program code to:
  • the event schedule data comprises parameters selected from the set of parameters comprising event data, event duration, event subject, event message parameters.
  • a mobile communication device for event scheduling comprising:
  • a memory device for storing digital data including computer program code and being coupled to the processor via a bus;
  • a communications network interface for sending and receiving digital data and being coupled to the processor via the bus;
  • processor is controlled by the computer program code to:
  • the event schedule data is a push notification.
  • the push notification is delivered using a delivery technique selected from the set of delivery techniques comprising unicast and multicast delivery techniques.
  • the calendar application is a native calendar application.
  • the processor is further controlled by the computer program code to:
  • the event schedule update data comprises event identification data identifying the event.
  • the processor is further controlled by the computer program code to:
  • the user option data represents options selected from the set of options comprising accept, cancel or reschedule options.
  • the processor is further controlled by the computer program code to:
  • 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.
  • the event schedule data comprises parameters selected from the set of parameters comprising event data, event duration, event subject, event message parameters.
  • 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:
  • the event schedule data is a push notification.
  • the push notification is delivered using a delivery technique selected from the set of delivery techniques comprising unicast and multicast delivery techniques.
  • the event data comprises mobile communication device identification data
  • the system is operable to determine one or more target mobile communication devices in further accordance with the mobile communication device identification data
  • the computer readable storage medium further comprises:
  • the event schedule update data comprises event identification data identifying the event.
  • the computer readable storage medium further comprises:
  • the user option data represents options selected from the set of options comprising accept, cancel or reschedule options.
  • the computer readable storage medium further comprises:
  • the event schedule data comprises parameters selected from the set of parameters comprising event data, event duration, event subject, event message parameters.
  • 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:
  • the event schedule data is a push notification.
  • the push notification is delivered using a delivery technique selected from the set of delivery techniques comprising unicast and multicast delivery techniques.
  • the calendar application is a native calendar application.
  • the computer readable storage medium further comprises:
  • the event schedule update data comprises event identification data identifying the event.
  • the computer readable storage medium further comprises:
  • the user option data represents options selected from the set of options comprising accept, cancel or reschedule options.
  • the computer readable storage medium further comprises:
  • the event schedule data comprises parameters selected from the set of parameters comprising event data, event duration, event subject, event message parameters.
  • 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.
  • 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.
  • 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.
  • Fig. 1 shows a computing device 100 on which the various embodiments described herein may be implemented.
  • 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.
  • DLL dynamic link libraries
  • the device 100 comprises semiconductor memory 110 comprising volatile memory such as random access memory (RAM) or read only memory (ROM).
  • RAM random access memory
  • ROM read only memory
  • 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.
  • 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 EthernetTM network or a wireless network, such as a BluetoothTM 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.
  • LAN local area network
  • WAN wide area network
  • 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.
  • an operating system and one or more software applications are loaded from the storage device 1030 into the memory 110.
  • 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.
  • 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.
  • a display device 1020 such as a liquid crystal display (LCD), cathode-ray tube (CRT) or similar display device.
  • LCD liquid crystal display
  • CRT cathode-ray tube
  • 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.
  • ISA Industry Standard Architecture
  • PCI Peripheral Component Interconnect
  • PCIe PCI Express
  • Serial Advanced Technology Attachment Serial ATA
  • 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.
  • the schedule server 205 may be provided with webserver capabilities, such that the GUIs may be viewable within an Internet browser across the Internet.
  • 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.
  • 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.
  • 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.
  • 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 may be further specified.
  • the schedule server 205 is adapted to interface with third party calendar or event scheduling software.
  • 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.
  • 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.
  • 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.
  • 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.
  • one or more mobile communication device 210 may be allocated to a group.
  • a dentistry practice may group several patients into a single mobile communication device 210 group.
  • 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.
  • the system 200 is adapted for sending the push notification delivery techniques comprising unicast and multicast delivery techniques.
  • 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.
  • 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 AppleTM Push Notification Service, AndroidTM C2DM Service or the Urban Airship push notification service for BlackberryTM. It should be noted that various forms of push technologies may be used including HTTP server push, Pushlet, Long polling, FlashTM XMLSocket relays and the like.
  • 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.
  • event schedule data may comprise extensible markup language (XML).
  • XML extensible markup language
  • Exemplary event schedule data for an event may comprise the following:
  • the event schedule data comprises payment data for the purposes of facilitating an electronic payment.
  • the event schedule data comprises payment data relating to a bank account number, a BSB number, an invoice number and an amount for payment.
  • 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.
  • 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.
  • 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.
  • each mobile communication device 210 comprises a calendar update application that has an event listener 220 for trapping the schedule event data push notifications.
  • the event listener 220 is adapted to update a calendar of the mobile communication device 210 in accordance with the schedule event data.
  • 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.
  • each user will download and install on each mobile communication device 210 the calendar update application.
  • the mobile communication device 210 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.
  • 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.
  • FIG. 6 there is shown an exemplary GUI 600 of a native calendar of a mobile communication device 210.
  • 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.
  • FIG. 7 there is shown an exemplary GUI 700 allowing a user to accept, cancel, reschedule the event and the like.
  • an Edit button 610 allowing a user to edit the event details.
  • 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.
  • the schedule server 205 may update the display of the event to the event scheduler, indicating the new parameters.
  • the system 200 is able to manage event updates.
  • 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.
  • the person will have the option of confirming his or her attendance of the appointment or declining the appointment.
  • 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.
  • the event schedule update data may refer to the unique event identification number in the event update data, such as, for example::
  • 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.
  • 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.
  • the calendar 405 representation comprising one or more event indicia 415 of the event.
  • 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.
  • the event indicia 415 may be represented in a second colour, indicating that the event has been accepted.
  • the event indicia 415 may be represented in a third colour.
  • 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.
  • the event schedule data may comprise availability data so as to advantageously mitigate unnecessary communication between parties for the purposes of rescheduling an event.
  • the system 200 is adapted for reminding event attendees of upcoming events, so as to advantageously reduce the number of missed events.
  • 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.
  • 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.
  • the schedule server 205 may be adapted to use alternative communication means, such as by short message service or e-mail communication.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the event schedule update data may comprise event identification data identifying the event.
  • 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.
  • the user option data may represent options selected from the set of options comprising accept, cancel or reschedule options.
  • 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.
  • the event schedule data may comprise parameters selected from the set of parameters comprising event date, event duration, event subject, event message parameters.
  • 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.
  • 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.
  • 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.
  • the calendar application 225 may be a native calendar application 225.
  • 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.
  • the event schedule update data may comprise event identification data identifying the event.
  • 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.
  • the user option data may represent options selected from the set of options comprising accept, cancel or reschedule options.
  • 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.
  • the event schedule data may comprise parameters selected from the set of parameters comprising event date, event duration, event subject, event message parameters.
  • 'in accordance with' may also mean 'as a function of and is not necessarily limited to the integers specified in relation thereto.
  • '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.
  • 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.
  • 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.
  • 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.
  • 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.
  • processors capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken are included.
  • the processing system further may include a memory subsystem including main RAM and/or a static RAM, and/or ROM.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the software may further be transmitted or received over a network via a network interface device.
  • 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.
  • 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.
  • 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.
  • 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.

Landscapes

  • Business, Economics & Management (AREA)
  • Human Resources & Organizations (AREA)
  • Engineering & Computer Science (AREA)
  • Strategic Management (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Operations Research (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Data Mining & Analysis (AREA)
  • Quality & Reliability (AREA)
  • Tourism & Hospitality (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Selon un aspect, l'invention concerne un système de planification d'événement de dispositif de communication mobile, le système comprenant : un serveur de planification ; et une pluralité de dispositifs de communication en communication avec le serveur de planification à travers un réseau de communication, le système étant apte à recevoir, au niveau du serveur de planification, des données d'événement relatives à un événement ; à déterminer un ou plusieurs dispositifs de communication mobile cibles de la pluralité de dispositifs de communication mobile conformément aux données d'événement ; à envoyer, à travers le réseau de communication, des données de planification d'événement du serveur de planification au ou aux dispositifs de communication mobile cibles ; à mettre à jour, dans le ou les dispositifs de communication mobile cibles, un événement d'une application de calendrier conformément aux données de planification d'événement. De manière avantageuse, le système est conçu pour la gestion de planification d'événement pour une pluralité de dispositifs de communication mobile à travers un réseau de communication. De cette manière, le système peut être utilisé pour planifier un ou plusieurs événements pour une pluralité d'utilisateurs et gérer la replanification, l'acceptation et les refus du ou des événements.
PCT/AU2012/001070 2011-09-08 2012-09-07 Planification d'événement de dispositif de communication mobile Ceased WO2013033785A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
AU2011903672A AU2011903672A0 (en) 2011-09-08 A system, scheduler server, mobile communication device and computer readable storage medium for mobile communication device event scheduling
AU2011903672 2011-09-08

Publications (1)

Publication Number Publication Date
WO2013033785A1 true WO2013033785A1 (fr) 2013-03-14

Family

ID=47831370

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/AU2012/001070 Ceased WO2013033785A1 (fr) 2011-09-08 2012-09-07 Planification d'événement de dispositif de communication mobile

Country Status (1)

Country Link
WO (1) WO2013033785A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE102014208532A1 (de) * 2014-05-07 2015-11-12 Siemens Aktiengesellschaft Verfahren zur Steuerung medizinischer Untersuchungen mittels eines Patientenkommunikationssystems, sowie Patientenkommunikationssystem, Patientengerät und klinische Servereinheit
US10070277B2 (en) 2013-12-31 2018-09-04 Nokia Technologies Oy Method and apparatus for providing a dynamic polling notification system

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5960406A (en) * 1998-01-22 1999-09-28 Ecal, Corp. Scheduling system for use between users on the web
US6370566B2 (en) * 1998-04-10 2002-04-09 Microsoft Corporation Generating meeting requests and group scheduling from a mobile device
US20090029724A1 (en) * 2007-07-27 2009-01-29 Research In Motion Limited System and method for acknowledging calendar appointments using a mobile device
US20090094088A1 (en) * 2007-10-03 2009-04-09 Yen-Fu Chen Methods, systems, and apparatuses for automated confirmations of meetings

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5960406A (en) * 1998-01-22 1999-09-28 Ecal, Corp. Scheduling system for use between users on the web
US6370566B2 (en) * 1998-04-10 2002-04-09 Microsoft Corporation Generating meeting requests and group scheduling from a mobile device
US20090029724A1 (en) * 2007-07-27 2009-01-29 Research In Motion Limited System and method for acknowledging calendar appointments using a mobile device
US20090094088A1 (en) * 2007-10-03 2009-04-09 Yen-Fu Chen Methods, systems, and apparatuses for automated confirmations of meetings

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10070277B2 (en) 2013-12-31 2018-09-04 Nokia Technologies Oy Method and apparatus for providing a dynamic polling notification system
DE102014208532A1 (de) * 2014-05-07 2015-11-12 Siemens Aktiengesellschaft Verfahren zur Steuerung medizinischer Untersuchungen mittels eines Patientenkommunikationssystems, sowie Patientenkommunikationssystem, Patientengerät und klinische Servereinheit

Similar Documents

Publication Publication Date Title
US8126974B2 (en) Specifying during meeting establishment when respondents are to be prompted for attendance intentions
US10579969B2 (en) Techniques for managing calendar invites received from different messaging services
US20110015961A1 (en) Method and system for an event scheduler
US8484745B2 (en) Electronic calendar collaboration
JP5335904B2 (ja) モバイルデバイスからのメッセージの送信のスケジュールを設定するための方法及び装置
US20150220888A1 (en) System and method of scheduling meetings, appointments and events using multiple identities
US20080270211A1 (en) method and system for modifying a meeting attendee list of an email calendar application
US9231991B1 (en) Method and apparatus of providing notification services to smartphone devices
US20140310045A1 (en) Generating and Displaying a Calendar Event Recurrence Preview
US20140310044A1 (en) Transmitting an Electronic Message to Calendar Event Invitees
CN104376451A (zh) 一种待提醒事件的提醒方法及终端
US20120164997A1 (en) System and method for organizing events and meetings
US8751602B1 (en) Method and apparatus of providing notification services to smartphone devices
CN104079609A (zh) 日程信息处理方法及设备
US20110160998A1 (en) Method and apparatus for conditional event planning
CN111886617A (zh) 用于日历项的自动更新的可配置设置
WO2013033785A1 (fr) Planification d'événement de dispositif de communication mobile
US20130054295A1 (en) Providing indications by a calendaring system that a meeting has been previously rescheduled to aid in scheduling
TW201629861A (zh) 約會邀請方法和系統
US20160247125A1 (en) R We Still On Time? An Active Approach for Aggregating 2-Way Re-confirmations in Electronic Calendaring Systems
US20090099896A1 (en) System and method for workflow delinquency remediation
CN114830045A (zh) 基于在预定义的工作时间之外收到的会议邀请而更新闹钟设置
US20110015959A1 (en) Appointment alert system and method
US11977721B1 (en) Event scheduling system and method
US20150142901A1 (en) Systems and methods for delivering time-delayed electronic notifications

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 12829849

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 12829849

Country of ref document: EP

Kind code of ref document: A1