US20010054072A1 - Generating meeting requests and group scheduling from a mobile device - Google Patents

Generating meeting requests and group scheduling from a mobile device Download PDF

Info

Publication number
US20010054072A1
US20010054072A1 US09/058,679 US5867998A US2001054072A1 US 20010054072 A1 US20010054072 A1 US 20010054072A1 US 5867998 A US5867998 A US 5867998A US 2001054072 A1 US2001054072 A1 US 2001054072A1
Authority
US
United States
Prior art keywords
meeting
electronic mail
mobile device
store
objects
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.)
Granted
Application number
US09/058,679
Other versions
US6370566B2 (en
Inventor
Anthony Discolo
Scott Skorupa
Salim Alam
Garrett R. Vargas
Dave Whitney
Bryce Ulrich
John I Ferrell
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.)
Microsoft Technology Licensing LLC
Original Assignee
Individual
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
Family has litigation
First worldwide family litigation filed litigation Critical https://patents.darts-ip.com/?family=22018248&utm_source=google_patent&utm_medium=platform_link&utm_campaign=public_patent_search&patent=US20010054072(A1) "Global patent litigation dataset” by Darts-ip is licensed under a Creative Commons Attribution 4.0 International License.
Priority to US09/058,679 priority Critical patent/US6370566B2/en
Assigned to MICROSOFT CORPORATION reassignment MICROSOFT CORPORATION ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: ALAM, SALIM, DISCLOLO, ANTHONY, SKORUPA, SCOTT, ULRICH, BRYCE, VARGAS, GARRETT R., WHITNEY, DAVE, FERRELL, JOHN I.
Application filed by Individual filed Critical Individual
Assigned to MICROSOFT CORPORATION reassignment MICROSOFT CORPORATION ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: ULRICH, BRYCE
Priority to JP2000518349A priority patent/JP4575591B2/en
Priority to PCT/US1998/022413 priority patent/WO1999022324A1/en
Priority to CA002306264A priority patent/CA2306264C/en
Priority to EP98953902A priority patent/EP1025526A1/en
Assigned to MICROSOFT CORPORATION reassignment MICROSOFT CORPORATION CORRECTED ASSIGNMENT TO CORRECT THE LAST NAME OF FIRST INVENTOR RECORDED ON REEL 9116, FRAME 322. Assignors: ALAM, SALIM, DISCOLO, ANTHONY, SKORUPA, SCOTT, ULRICH, BRYCE, VARGAS, GARRETT R., WHITNEY, DAVE, FERRELL, JOHN I.
Publication of US20010054072A1 publication Critical patent/US20010054072A1/en
Publication of US6370566B2 publication Critical patent/US6370566B2/en
Application granted granted Critical
Assigned to MICROSOFT TECHNOLOGY LICENSING, LLC. reassignment MICROSOFT TECHNOLOGY LICENSING, LLC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: MICROSOFT CORPORATION
Anticipated expiration legal-status Critical
Expired - Lifetime legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION 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/00Administration; Management
    • G06Q10/10Office automation; Time management
    • G06Q10/109Time management, e.g. calendars, reminders, meetings or time accounting
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F15/00Digital computers in general; Data processing equipment in general
    • G06F15/02Digital computers in general; Data processing equipment in general manually operated with input through keyboard and computation using a built-in program, e.g. pocket calculators
    • G06F15/0225User interface arrangements, e.g. keyboard, display; Interfaces to other computer systems

Definitions

  • Mobile devices are small electronic computing devices often referred to as personal digital assistants.
  • One such mobile device is sold under the trade name Handheld PC (or “H/PC”) based on a Windows CE brand operating system provided by Microsoft Corporation of Redmond, Washington. While a wide variety of computing tasks and applications can be performed by such mobile devices, personal information managers (PIMs) are particularly well suited to mobile devices.
  • Handheld PC or “H/PC”
  • Windows CE brand operating system provided by Microsoft Corporation of Redmond, Washington.
  • PIMs personal information managers
  • PIMs typically comprise applications which enable the user of the mobile device to better manage scheduling and communications, and other such tasks.
  • Some commonly available PIMs include scheduling and calendar programs, task lists, address books, and electronic mail (e-mail) programs.
  • Some commonly commercially available PIMs are sold under the brand names Microsoft Schedule+ and Microsoft Outlook and are commercially available from Microsoft Corporation of Redmond, Washington.
  • PIMs shall also include separate electronic mail applications, such as that available under the brand name Microsoft Exchange.
  • a mobile device it is also common for mobile devices to be used in conjunction with a desktop computer.
  • the user of a mobile device may also have access to, and use, a desktop computer at work, at home, or both.
  • a user may typically run the same types of PIMs on both the desktop computer and the mobile device (although the particular versions of the PIMs may be somewhat different from the desktop computer to the mobile device).
  • the mobile device it is quite advantageous for the mobile device to be designed to be couplable to the desktop computer to exchange information with, and share information with, the desktop computer.
  • the user may also typically make changes to the PIMs both on the mobile device, and at the desktop. Therefore, it is advantageous for the PIMs on both the mobile device and the desktop to contain the most up-to-date information, regardless of whether recent changes to the PIMs have been made on the mobile device or the desktop computer.
  • the process of coupling the mobile device with the desktop computer, and integrating the information stored by the PIMs on the mobile device and the desktop computer such that the two contain the same updated information is referred to as synchronization.
  • Conventional PIMs which support electronic calendaring and scheduling features are traditionally supported on desktop computers. Such PIMs provide the ability of the user to schedule a meeting request for one or more desired attendees.
  • the user In order to generate a meeting request, the user typically interacts with the scheduling application through a user interface.
  • the user interface provides the user with a plurality of selectable options to parameterize the meeting request. For example, the user interface typically allows the user to pick a date and time (and often a place) on which the meeting is to be held.
  • the user interface also typically allows the user to select a group of attendees that the user wishes to attend the meeting, to enter some textual description of the meeting, and to specify whether the meeting is for only a single date, or is a recurring meeting (i.e., whether the meeting is to occur only on one date, the 15 th of every month, the first Monday of every month, every Monday, etc.).
  • the scheduling application creates an object which is representative of the meeting and enters it on the user's calendar as an appointment.
  • objects are typically defined by a number of properties, some of which are defined by the user input information which the user provides while generating the meeting request.
  • the meeting object also contains a critical time stamp (UTC) which is updated whenever a critical change is made to the meeting object, such as changes to the start or end date or time, changes in the location, etc.
  • UTC critical time stamp
  • the appointment entered on the calendar is viewed as a meeting and the scheduling application typically calls methods exposed by an electronic mail application in accordance with messaging application programming interfaces (MAPI), or other APIs which are a set of well documented, published interfaces commercially available from the Microsoft Corporation of Redmond, Washington.
  • MMI messaging application programming interfaces
  • the electronic mail application creates another object (an electronic mail meeting request object) indicative of the meeting request and the electronic mail application (or suitable transport) formats this electronic mail meeting request object into a well defined electronic mail message suitable for transmission. In doing so, the critical time stamp from the meeting object is also placed in the electronic mail meeting request object.
  • the electronic mail application then interacts with a specified transport and transports the electronic mail meeting request object to a network which routes it to the designated attendees.
  • the electronic mail application typically accesses an address book stored in a database to obtain the fully qualified electronic mail address for the attendees. This is also typically done by calling MAPI or other suitable API methods associated with the database storing the address book.
  • the generation of the meeting object and the creation of the electronic mail meeting request object will be referred to herein collectively as creating a meeting request.
  • the potential attendees then typically respond to the meeting request. In doing so, the originator's critical time stamp is sent back (unmodified) along with the response.
  • the response also includes a recipient critical time stamp and an indication of the recipient's response (e.g., accept, decline, tentative, etc.).
  • the recipient critical time stamp is updated by the recipient (potential attendee) whenever a critical change is made by the recipient.
  • the response is then transmitted back to the originator (e.g., the sending computer).
  • the electronic mail application and scheduling application on the originator then typically process the response (or responses) accordingly.
  • the originator stores, for each recipient (or potential attendee) the recipient critical time stamp in a table along with each recipient's response code (which is indicative of the accept, decline, tentative response).
  • the two commercially available PIMs identified above are examples of PIMs which support the features discussed above.
  • Meeting cancellations, and exceptions to recurring meeting must also be handled.
  • the PIMs may allow scheduled meetings to be cancelled, and allow a variety of exceptions to a recurring meeting pattern.
  • a number of significant obstacles present themselves when attempting to provide the user with the capability of generating a meeting request from a mobile device. Meeting cancellations and exceptions to recurring meetings must be handled. Also, a significant problem arises with respect to the possibility of transmitting duplicate meeting requests. While duplicate meeting requests as described below may not necessarily be created with all PIMs, they do present a potential problem which must be considered. For example, if the user of the mobile device were able to generate a meeting request, a meeting object would first be entered on the calendar of the mobile device. The electronic mail application on the mobile device would then create a corresponding electronic mail meeting request object.
  • the meeting object would be synchronized with the calendar object store on the desktop computer and the electronic mail meeting request object would be synchronized to the desktop outbox.
  • the desktop computer would recognize the electronic mail meeting request object in its outbox, format it for transmission, and transmit it over the network. Further, synchronizing the meeting object to the calendar of the desktop computer may result in another electronic mail meeting request object being created and transmitted by the desktop computer. This would result in duplicate electronic mail meeting request objects being created (one by the mobile device, and one by the desktop computer after synchronization) and transmitted. Under that scenario, potential attendees would receive two or more meeting requests, and may respond to both. This would create duplicate responses to what was intended to be a single meeting request.
  • a similar problem may occur if a meeting request were generated in a conventional manner (on a desktop computer) for instance, and was then synchronized to a mobile device having the capability of generating and transmitting meeting requests.
  • the meeting object on the desktop calendar would be synchronized to the calendar of the mobile device.
  • the mobile device might then recognize the meeting object synchronized from the desktop, and create an electronic mail meeting request object and attempt to transmit the object. This would result in substantially the same problem—duplicate meeting requests and duplicate responses for what was intended to be a single meeting request.
  • both desktop computers would synchronize with, and recognize, the meeting object and the electronic mail meeting request object from the mobile device.
  • the desktop computers would both potentially create additional electronic mail meeting request objects and transmit them to the potential attendees. Again, this would result in many different meeting requests and responses being transmitted for what was intended to be only a single meeting request.
  • the meeting request could be generated by one mobile device, responded to by another mobile device, and scheduled on both mobile devices.
  • that computer might again recognize the meeting object synchronized from the calendar of the mobile device, create another electronic mail meeting request object and transmit the electronic mail meeting request object.
  • the present invention addresses some or all of these obstacles.
  • the present invention includes a mobile device which provides the user with the ability to schedule a meeting request from the mobile device itself.
  • the mobile device creates an object representative of the meeting request and assigns the object a global identification number which uniquely identifies the object to other devices which encounter the object. In this way, other devices which encounter the meeting request are capable of identifying it as a unique meeting request in order to alleviate the problem of duplicate meeting request transmissions.
  • an electronic mail application or calendar application on the mobile device obtains a fully qualified electronic mail address for the potential attendees from an abridged address book or directory stored on the mobile device itself. This alleviates problems associated with the storage capacity of the mobile device.
  • the mobile device creates the meeting object and the electronic mail meeting request object using a set of properties which are supported by a plurality of PIMs that may receive the objects . This provides compatibility with an increased number of devices which are likely to encounter the objects.
  • localizers implement a plurality of templates on the mobile device which are used in formatting the properties of the objects associated with the meeting request.
  • a data stream representative of the meeting request is parsed by the mobile device and placed in pre-defined fields in the appropriate templates so that the text viewed by the user of the mobile device more closely conforms to local convention.
  • time zone information is also included in one embodiment.
  • FIG. 1 is a block diagram illustrating a basic environment of the present invention.
  • FIG. 2 is a block diagram of one embodiment of a conventional desktop computer used in conjunction with a mobile device in accordance with the present invention.
  • FIG. 3 is a simplified pictorial illustration of one embodiment of a mobile device in accordance with the present invention.
  • FIG. 4 is a simplified block diagram of one embodiment of the mobile device shown in FIG. 3.
  • FIG. 5 is an architectural block diagram illustrating one embodiment of portions of the desktop computer shown in FIG. 2 and the mobile device shown in FIGS. 3 and 4 to illustrate synchronization of information stored in object stores on the desktop computer and the mobile device in accordance with the present invention.
  • FIG. 6 is an architectural block diagram illustrating one embodiment of portions of the desktop computer shown in FIG. 2 and the mobile device shown in FIGS. 3 and 4 to illustrate the generation and transmission of a meeting request.
  • FIG. 7 is a flow diagram illustrating the generation of a meeting request in accordance with one preferred embodiment of the present invention.
  • FIG. 8 is a flow diagram illustrating the handling of responses to a meeting request on the mobile device shown in FIGS. 3 and 4 in accordance with one preferred embodiment of the present invention.
  • FIG. 9 is a flow diagram illustrating the handling of responses to a meeting request on the desktop computer shown in FIG. 2 in accordance with one preferred embodiment of the present invention.
  • FIG. 10 is a flow diagram illustrating the use of a localizer to localize the textual description of a meeting request in accordance with one preferred embodiment of the present invention.
  • FIGS. 11A and 11B illustrate one embodiment of a template used to localize the textual description of a meeting request in accordance with the present invention.
  • FIG. 1 is a block diagram of a typical system or environment 2 in which the present invention operates.
  • Environment 2 includes mobile device 3 and desktop computer 4 .
  • FIG. 1 also illustrates that mobile device 3 can optionally be separately coupled to another mobile device 10 or another desktop computer 13 .
  • Mobile device 3 includes an application program 5 and an object store 6 .
  • Desktop computer 4 also includes an application program 7 and an object store 8 .
  • Mobile device 10 includes an application program 11 and object store 12 .
  • desktop computer 13 includes an application program 14 and an object store 15 .
  • Mobile device 3 is couplable to desktop computer 4 , mobile device 10 or desktop computer 13 by one of a plurality of connection mechanisms 9 .
  • the operation of desktop computers 4 and 13 and the operation of mobile devices 3 and 10 are preferably similar. Therefore, for the sake of simplicity, the present description proceeds only with respect to mobile device 3 and desktop computer 4 .
  • application program 7 on desktop 4 is a personal information manager (PIM) which supports electronic mail messaging, scheduling and calendaring and an address book containing contact information.
  • PIM personal information manager
  • PIM applications are not always integrated. For instance, some scheduling programs do not contain electronic mail features, but interface with whatever electronic mail program is provided, and vice versa.
  • PIM 7 (whether it be a single application, a single integrated application or multiple interfaced applications) can be configured to support a wide variety of other features, such as task lists and personalized address books, to name a few.
  • PIM 7 can be configured to support a wide variety of other features, such as task lists and personalized address books, to name a few.
  • only features relating to electronic mail messaging, scheduling and calendar features, and address book features are discussed in detail with respect to the present invention.
  • Object store 8 is a memory which is configured to store a plurality of individual records or objects, each comprising a plurality of fields or properties related to the above-mentioned features.
  • PIM 7 is a program, such as that available under the commercial designation Microsoft Outlook 97
  • object store 8 is configured to store objects, each of which has a plurality of properties which can be associated with electronic mail messaging, scheduling and calendaring, and contact information.
  • some properties included in an object associated with electronic mail messaging include the sender's name, the recipient's name, text messages, an indication of whether attachments are attached to any given electronic mail message, and possibly other similar properties.
  • some properties associated with scheduling and calendaring include critical time stamp information, date and time information, potential attendees, recurrence properties which describe recurrent meetings or meeting requests, and a textual description of the meeting request.
  • Some properties associated with contact information include the proper names, or familiar names, of those in the contact list, the addresses and telephone numbers of those listed, and the fully qualified electronic mail address for those in the list. Any number of other properties can also be included.
  • Desktop computer 4 executes the application program identified as PIM 7 to maintain objects stored in object store 8 .
  • the application program designated as PIM 5 for mobile device 3 is a similar PIM to that stored on desktop computer 4 .
  • Object store 6 on mobile device 3 is configured to store a plurality of individual records or objects, each comprising a plurality of fields or properties related to the above-mentioned, supported features.
  • PIM 5 can also support a wide variety of other features. However, for the sake of clarity, only those features related to the present invention are discussed in detail herein.
  • each object stored in object store 8 is also stored in object store 6 .
  • there are actually two instances of each object one in object store 6 and one in object store 8 .
  • the second instance of that object in the other of stores 6 and 8 is preferably updated the next time mobile device 3 is connected to desktop computer 4 so that both instances of the same object contain up-to-date data. This is referred to as synchronization.
  • synchronization components run on both mobile device 3 and desktop computer 4 .
  • the synchronization components communicate with PIMs 5 and 7 on mobile device 3 and desktop computer 4 through well defined interfaces to manage communication and synchronization.
  • mobile device 3 and desktop computer 4 communicate with each other through any suitable, and commercially available, communication link 9 , and using a suitable communications protocol.
  • mobile device 3 is connectable to desktop computer 4 with a physical cable which communicates using a serial communications protocol.
  • Other communication mechanisms are also contemplated by the present invention, such as infrared (IR) communication, direct modem communication, remote dial-up networking communication, communication through commercially available network cards (i.e., using TCP/IP), remote access services (RAS), wireless modem, wireless cellular digital packet data (CDPD), or other suitable communication mechanisms.
  • FIG. 2 and the related discussion are intended to provide a brief, general description of a suitable desktop computer 4 in which portions of the invention may be implemented.
  • the invention will be described, at least in part, in the general context of computer-executable instructions, such as program modules, being executed by a personal computer 4 or mobile device 3 .
  • program modules include routine programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types.
  • desktop computer 4 may be implemented with other computer system configurations, including multiprocessor systems, microprocessor-based or programmable consumer electronics, network PCs, minicomputers, mainframe computers, and the like.
  • the invention may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network.
  • program modules may be located in both local and remote memory storage devices. Examples of distributed programs include those available under the commercial designations Exchange, Schedule+ and MS Mail, all available from Microsoft Corporation.
  • an exemplary system for implementing desktop computer 4 includes a general purpose computing device in the form of a conventional personal computer 4 , including processing unit 21 , a system memory 22 , and a system bus 23 that couples various system components including the system memory to the processing unit 21 .
  • the system bus 23 may be any of several types of bus structures including a memory bus or memory controller, a peripheral bus, and a local bus using any of a variety of bus architectures.
  • the system memory includes read only memory (ROM) 24 and random access memory (RAM) 25 .
  • serial port interface 46 that is coupled to the system bus 23 , but may be connected by other interfaces, such as a sound card, a parallel port, a game port or a universal serial bus (USB) .
  • a monitor 47 or other type of display device is also connected to the system bus 23 via an interface, such as a video adapter 48 .
  • desktop computers may typically include other peripheral output devices such as speaker 45 and printers.
  • the desktop computer 4 may operate in a networked environment using logic connections to one or more remote computers (other than mobile device 3 ), such as a remote computer 49 .
  • the remote computer 49 may be another personal computer, a server, a router, a network PC, a peer device or other network node, and typically includes many or all of the elements described above relative to desktop computer 4 , although only a memory storage device 50 has been illustrated in FIG. 2.
  • the logic connections depicted in FIG. 2 include a local area network (LAN) 51 and a wide area network (WAN) 52 .
  • LAN local area network
  • WAN wide area network
  • FIG. 3 is a pictorial illustration of one preferred embodiment of a mobile device 3 which can be used in accordance with the present invention.
  • Mobile device 3 in one preferred embodiment, is a desktop assistant sold under the designation H/PC and being based on, for example, the Windows CE brand operating system provided by Microsoft Corporation.
  • mobile device 3 is housed in a housing which fits comfortably in the hand of a typical user.
  • Mobile device 3 has some components which are similar to those of desktop computer 4 .
  • mobile device 3 includes a miniaturized keyboard 82 , display 84 , and stylus 86 . Of course, other configurations, such as without keyboards, can also be used.
  • display 84 is a liquid crystal display (LCD) which uses a contact-sensitive display screen in conjunction with stylus 86 .
  • Stylus 86 is used to press or contact the display 84 at designated coordinates to accomplish certain user input functions.
  • other user input configurations can be used as well.
  • user input mechanisms could be included such as a keypad, a track ball, and other various types of miniaturized keyboards, or the like.
  • mobile device 3 may not be embodied as the H/PC brand of digital assistant, but could also be implemented as another type of personal digital assistant (PDA), another personal organizer, a palm top computer, or a similar computerized notepad device.
  • PDA personal digital assistant
  • FIG. 4 is a more detailed block diagram of mobile device 3 .
  • Mobile device 3 preferably includes microprocessor 88 , memory 90 , input/output (I/O) components 92 (which include keyboard 82 and touch sensitive screen 84 ), optional expansion slots 93 (which can be used for plugging in such things as PC cards, compact flash memory, etc.) and serial interface 94 .
  • I/O input/output
  • these components of mobile device 3 are coupled for communication with one another over a suitable bus 96 .
  • memory 90 is implemented as non-volatile electronic memory such as a random access memory (RAM) with a battery back-up module (not shown) such that information stored in memory 90 is not lost when the general power to mobile device 30 is shut down.
  • RAM random access memory
  • a portion of memory 90 is preferably allocated as addressable memory for program execution, while another portion of memory 90 is preferably used to simulate storage on a disk drive.
  • Memory 90 includes operating system 98 and application (or PIM) 5 .
  • Operating system 98 during operation, is preferably loaded into, and executed by, processor 88 from memory 90 .
  • Operating system 98 in one preferred embodiment, is the Windows CE brand operating system.
  • the operating system 98 is preferably designed for mobile devices, and implements database features which can be utilized by PIM 5 through a set of exposed application programming interfaces and methods.
  • the objects in object store 6 are preferably maintained by PIM 5 and operating system 98 , at least partially in response to calls to the exposed application program interfaces and methods.
  • PIM 5 is not necessarily designed to be entirely compatible with PIM 7 which executes on desktop computer 4 .
  • PIM 7 executes on desktop computer 4 .
  • Some properties supported by the electronic mail messaging features of PIM 5 may have no corresponding features in PIM 7 on desktop computer 4 , and vise versa.
  • FIG. 5 is an architectural block diagram illustrating one preferred embodiment of architectural components of mobile device 3 and desktop computer 4 which are used in synchronizing objects stored in object store 6 on mobile device 3 and object store 8 on desktop computer 4 .
  • the synchronization architecture illustrated in FIG. 5 is but one preferred embodiment and others could be used as well.
  • the synchronization operation can be carried out between any two coupled stores (such as those on any combination of pairs of computers 4 and 13 , and mobile devices 3 and 10 ). All that is required is a synchronization manager component, as described below, which directs synchronization of the two coupled stores.
  • the synchronization manager can reside on either device, or both, or on a third computer coupled to the two stores.
  • the present synchronization protocol is but one preferred embodiment, as another suitable protocol could be implemented on top of standard electronic mail protocols.
  • mobile device 3 includes synchronization module 97 which, in turn, includes interface component 100 , and synchronization manager 102 .
  • Mobile device 3 also includes communications component 94 , remote application programming interface (RAPI) server 116 , and electronic mail messaging transports 132 , 134 and 136 .
  • RAPI remote application programming interface
  • Desktop computer 4 includes, in addition to PIM 7 and object store 8 , synchronization module 99 which, in turn, includes interface component 108 , synchronization manager 110 , reference store 112 , and RAPI component 114 .
  • Desktop computer 4 also includes communications component 115 .
  • synchronization manager 110 executes on desktop computer 4 and orchestrates synchronization between objects in object store 6 in handheld device 3 , and objects in object store 8 in desktop computer 4 .
  • Synchronization manager 110 also maintains reference store 112 apart from desktop object store 8 as is described in greater detail below.
  • Synchronization manager 110 implements the synchronization protocol to allow a comparison between corresponding objects stored in object store 6 in mobile device 3 and object store 8 in desktop computer 4 , to receive objects from object store 8 , and to update objects in object store 8 .
  • the synchronization protocol also facilitates the retrieval of objects stored in object store 6 in mobile device 3 through synchronization interface component 100 and synchronization manager 102 , as well as communications component 94 .
  • the synchronization interface component 100 exposes application programming interfaces which synchronization manager 102 calls to read and store objects and object properties on object store 6 .
  • the application programming interfaces allow the creation of databases for different types of objects, and allow application programs to write and read property names and values to and from respective objects within object store 6 .
  • PIM 5 executes on mobile device 3 and maintains object store 6 .
  • PIM 7 executes on desktop computer 4 and maintains object store 8 .
  • PIMs 5 and 7 can store objects in object stores 6 and 8 .
  • PIMs 5 and 7 create a distinct database for each object type. For example, different databases are created for meetings, contacts, tasks, electronic mail messages, etc. A predefined set of properties is supported for each object type, and each of the databases is assigned a name by the application program that creates it.
  • the application programs in PIMs 5 and 7 may use a single database for all object types, with the first property of each object defining the type of object.
  • objects are uniquely identified within mobile device 3 and desktop computer 4 by object identifiers which are independent of the names assigned by the application programs creating the object.
  • Synchronization manager 110 is not necessarily closely associated with PIM 7 . Rather, it is an independent component which synchronizes objects from any application program that supports the appropriate desktop synchronization interfaces. The specific synchronization interfaces are described in greater detail in the co-pending patent application incorporated above. Communication components 94 and 115 implement serial communications between the computers using suitable link 9 .
  • Synchronization manager 110 communicates with PIM 7 and accesses object store 8 through synchronization interface component 108 .
  • Synchronization interface component 108 corresponds generally to a DLL discussed with respect to FIG. 2 above, and exposes one or more application program interfaces and method.
  • the interfaces and methods are described in greater detail in the co-pending patent application which is incorporated above by reference.
  • the MAPI exposed by component 108 is a C-language application programming interface which allows programmable access to features of an electronic mail messaging program known as MS Mail also commercially available from the Microsoft Corporation.
  • the MAPI exposed by component 108 is a component object model based (COM-based) set of interfaces which is sometimes referred to as extended MAPI and includes a set of automation interfaces to messaging systems, for use in Visual Basic and the like.
  • COM-based component object model based
  • Synchronization manager 110 maintains reference store 112 so that reference store 112 contains the identifying data segments corresponding respectively to a plurality of object instances in object store 8 on desktop computer 4 that are to be synchronized with instances of the same object in object store 6 on mobile device 3 .
  • the identifying data segments are updated each time corresponding object instances have been synchronized.
  • the exact composition of an identifying data segment which is used to identify the particular object instances are assignable by the developer of the desktop synchronization interface component 108 , and are then handled and stored by synchronization manager 110 .
  • the identifying data segments preferably include some sort of time stamp information which can be compared to determine whether an object has changed since the identifying data segment was last recorded in reference store 112 .
  • synchronization manager 110 In addition to maintaining a plurality of identifying data segments, synchronization manager 110 also maintains a list of object identifiers corresponding to objects maintained in object store 6 . These identifiers are provided to synchronization manager 110 whenever a new object is added to object store 6 on mobile device 3 .
  • synchronization manager 110 In order to synchronize objects, synchronization manager 110 first creates two lists of handles which refer to particular objects.
  • the term “handle” refers to a number or other identifier that can be used to uniquely identify an object and to access the object. Generally, a handle is valid for a particular time period or session, such as during the time when an object has been “opened.” If the same object is opened again, its handle may be different.
  • the first list of handles is obtained from reference store 112 and is indicative of objects which have been synchronized in the past and are identified in reference store 112 .
  • the second list of handles is a list which identifies the objects stored on object store 8 .
  • the two lists of handles are compared against one another to determine whether the same objects are stored in reference store 112 and object store 8 .
  • synchronization manager 110 determines how to handle the object. In one preferred embodiment, those objects which have been deleted from desktop object store 8 are also deleted from reference store 112 . Further, those which have been added to object store 8 are also added to reference store 112 .
  • Synchronization manager 110 determines whether any of the objects stored in object store 8 have been modified at the desktop since the last synchronization. In other words, if handles corresponding to the same object appear in both object store 8 and reference store 112 , but they are not identical (such as the time stamp, a revision number, or another suitable identifying segment is not the same) that indicates that the object in object store 8 has been modified since the last synchronization.
  • Synchronization manager 110 determines whether any objects stored in object store 6 on mobile device 3 have been added or modified since the last synchronization. To determine whether an object has been added to object store 6 , synchronization manager 110 compares the list of objects in reference store 112 (which reflects all objects at the last synchronization) with a list of objects on object store 6 maintained by synchronization manager 102 . To determine whether an existing object has been modified, synchronization manager 102 is configured to maintain a status bit associated with each object stored in object store 6 . The status bit reflects whether the particular object associated with that bit has been changed since the last synchronization. If so, synchronization manager 102 notifies synchronization manager 110 of that change if device 3 is then coupled to desktop computer 4 , or simply logs the status bit and sends it to synchronization manager 110 the next time device 3 is coupled to desktop computer 4 .
  • synchronization manager 110 forms a list of objects which have been changed on either object store 8 or object store 6 and simply calls upon the respective synchronization interface components to update the outdated object. If the same object has been modified both on mobile device 3 and desktop. computer 4 , a conflict arises. Synchronization manager 110 resolves the conflicts by either prompting the user, or referencing profile information entered by the user during a set-up procedure which dictates which device the user wants to take precedence over the other, and in which instances. The process of setting up profile information is described in greater detail in the above-identification patent applications.
  • synchronization manager 110 calls an interface method known as “Set-Up” which specifies a handle for the object to be obtained from object store 8 in desktop computer 4 and transferred to object store 6 in mobile device 3 .
  • the method known as “GetPacket” is called repeatedly to retrieve a data stream which represents the object, and which is formatted by interface component 108 .
  • Synchronization manager 110 simply treats the data as a data stream which is retrieved and sent over link 9 to synchronization manager 102 , and eventually to object store 6 .
  • the appropriate synchronization interface component 100 parses the data stream in order to identify certain property values associated with properties corresponding to the object. Those properties are then stored in the object store 6 .
  • Synchronization manager 110 detects any new objects in object store 8 which represent new electronic mail messages, meetings or appointments or contact information and causes those objects to be transferred to object store 6 on mobile device 3 for attention by the user of mobile device 3 .
  • FIG. 6 is an architectural block diagram illustrating one preferred embodiment of a mechanism by which meeting requests are generated.
  • Mobile device 3 and desktop computer 4 are shown coupled to one another, as shown in FIG. 5.
  • FIG. 6 also illustrates that mobile device 3 and desktop computer 4 can be coupled to a wide area network 138 which can include simply another mobile device, another desktop computer, LAN 51 (shown in FIG. 2), WAN 52 (shown in FIG. 2), or any other suitable network.
  • FIG. 6 illustrates that, in one preferred embodiment, PIM 5 includes an electronic mail application 140 , a calendar and scheduling application 142 , and an abridged address book 144 . Also, while each of the applications may have designated application programming interfaces, only a single API component 146 is shown in FIG. 6, for the sake of simplicity.
  • FIG. 6 further illustrates that object store 6 preferably interfaces with applications 140 , 142 and 144 through its own set of application programming interfaces 148 .
  • applications 140 , 142 and 144 maintain object store 6 by calling methods exposed by application programming interfaces 148 associated with object store 6 .
  • communication component 94 and sync component 99 communicate with application programs 140 , 142 and 144 by calling methods exposed by application programming interfaces 146 .
  • PIM 7 in desktop computer 4 has also been illustrated as a more detail block diagram.
  • PIM 7 includes electronic mail application program 150 , scheduling and calendaring program 152 and full address book program 154 . While each of the application programs 150 , 152 and 154 may have an associated set of application programming interfaces, only a single application programming interface component 156 is illustrated in FIG. 6, for the sake of simplicity.
  • FIG. 6 further illustrates that, in one preferred embodiment, object store 8 is associated with its own set of application programming interfaces 158 (which may also be the same as API 156 , preferably MAPI, or which may be separate therefrom).
  • application programs 150 , 152 and 154 call methods exposed by application programming interfaces 158 to maintain, and interact with, object store 8 .
  • communications component 115 calls methods exposed by application programming interfaces 156 to interact with application programs 150 , 152 and 154 .
  • FIG. 6 shows that desktop computer 4 preferably includes electronic mail transport 160 .
  • Electronic mail transport 160 is preferably a commercially available electronic mail transport, such as a SMTP transport.
  • desktop computer 4 can include any suitable transport, or combination of transports.
  • FIG. 7 is a flow diagram illustrating the creation of a meeting request on mobile device 3 . The following description will proceed with reference to FIGS. 6 and 7.
  • the user In order to create a meeting request from mobile device 3 , the user first enters meeting request information through a suitable user interface.
  • the user opens the scheduling application program 142 which causes a suitable user interface to be displayed on screen 84 .
  • the user Using stylus 86 , and possibly keypad 82 (or any other suitable input mechanism), the user enters appropriate information to request a meeting.
  • Such information will typically include the date and time of the meeting, the requested attendees (which may be entered by using a fully qualified electronic mail address, or by entering a familiar name, or selected from entries in a contacts database which have a non-empty electronic mail address field), the subject matter of the meeting, an indication of whether the meeting is recurring or a single event, possibly the location of the meeting, and so on.
  • Scheduling application 142 creates an object representative of the meeting request.
  • This information is used to create a meeting object and enter that object in the store associated with the calendar on mobile device 3 .
  • an electronic mail meeting request object is also created. It should also be noted that subsequent critical modifications to the meeting object will also cause updated electronic mail meeting request objects to be created and transmitted as well.
  • a selection has already been made which specifies a transport by which any electronic mail meeting request objects are to be sent.
  • the transport to be used can be implicit in the full electronic mail address, itself. For example, it can be specified that any of transports 132 - 136 are to be used, when mobile device 3 is to transmit the meeting request itself.
  • a selection has also preferably already been made to specify certain options which are to be used in the sync protocol discussed above. For example, if an inbox synchronization option is enabled, the electronic mail meeting request objects will be synchronized to the outbox of desktop computer 4 . Also, if a calendar synchronization option is enabled, the meeting object will be synchronized to the calendar of desktop computer 4 . Desktop computer 4 then preferably transmits the electronic mail meeting request object synchronized to its outbox.
  • the critical time stamp is added to the objects (as indicated by block 165 ) and scheduling application 142 assigns a global object identification tag to the meeting object created.
  • the global object identification tag is a tag, such as a number, which uniquely identifies the object representative of the meeting request to mobile device 3 , to desktop computer 4 , and to all other devices which may encounter that object.
  • the global identification tag is carried with the electronic mail meeting request object when it is transmitted, and remains with the object on other devices. This is indicated by block 166 .
  • scheduling application 142 calls methods in API 146 which manipulate electronic mail program 140 to retrieve a fully qualified electronic mail address for all of the potential attendees who are to receive the meeting request.
  • scheduling application 142 obtains the fully qualified address directly from an address book.
  • mobile device 3 includes abridged address book program 144 .
  • abridged address book program 144 is implemented as a contacts feature provided by Microsoft Outlook 97 . The abridged address book contains proper names, familiar names, addresses, telephone numbers, and fully qualified electronic mail addresses for people that the user has chosen to add to the abridged address book.
  • Those people will likely be people who receive a significant number of electronic mail messages from the user of mobile device 3 . Therefore, that information likely contains the fully qualified electronic mail addresses for the potential attendees of the meeting request.
  • the synchronization component 97 on desktop 4 attempts to resolve the name on the desktop prior to sending the electronic mail transmission.
  • either electronic mail application 140 or scheduling application 142 call methods in API 146 which cause abridged address book program 144 to retrieve the fully qualified electronic mail address for the familiar names entered by the user as potential attendees.
  • This significantly alleviates memory overhead which would otherwise be required, for instance, if the user was required to download a full address book from desktop computer 4 in order to send an electronic mail message or a meeting request.
  • This is indicated by block 168 .
  • the functionality associated with block 168 is performed at block 162 , as soon as the user inputs the appropriate information.
  • the transport option has preferably already been chosen which indicates the particular transport by which the electronic mail messages are to be transmitted.
  • Those transports can be any of transports 132 - 136 on mobile device 3 or through synchronization with desktop computer 4 , using one of its transports. Based on the option which has been chosen, the electronic mail meeting request object is transmitted through the appropriate transport and, once transmitted, is removed from the outbox of mobile device 3 .
  • the appropriate transport formats the meeting request for transmission .
  • the particular properties which scheduling application program 142 attributes to an electronic mail meeting request object representative of a meeting request are compatible with multiple other PIMs. Therefore, these properties may be a subset or a superset, of all of the properties recognized by the multiple PIMs such that the object can be entertained and appropriately handled by those PIMs.
  • Appendix A which is attached hereto and forms a part of this document, is a list of message properties by which the Microsoft Schedule+brand scheduling program defines objects associated with meeting requests. These properties notably include revised recurring notification properties which are backward compatible with other versions of Microsoft Schedule+ scheduling software.
  • recurring notifications which are used to define recurring meetings are formatted as a superset of single-instance notifications.
  • prior versions of the Microsoft Schedule+ scheduling software will be provided with well formed meeting notifications, even for recurring meetings.
  • scheduling program 142 then calls methods exposed by API 146 related to electronic mail application program 140 .
  • the electronic mail message which contains the electronic mail meeting request object is formulated into one of a predetermined number of classes by electronic mail application 140 .
  • the receiving scheduler program of the potential attendee differentiates between the type of meeting notification based on the mail message class. For example, in one preferred embodiment, mail message classifications exist for a meeting cancellation notice from the originator, a meeting request from the originator, a meeting acceptance from the attendee, a meeting declined from the attendee and a meeting tentatively accepted from the attendee. Thus, this is preferably included along with the object when the transport formats the electronic mail meeting request object for transmission.
  • the meeting request is transmitted, through communications component 94 to the designated transport 132 , 134 or 136 which, in turn, formats and transmits the message to network 138 .
  • the electronic mail meeting request object After the electronic mail meeting request object is sent, it is removed from the outbox of mobile device 3 to indicate that the message has been sent. This is indicated by block 190 .
  • the meeting object Upon next being coupled to desktop computer 4 , the meeting object is synchronized to the store containing the calendar on desktop computer 4 .
  • the PIMs also provide a feature which can be utilized to prevent the PIM from creating and sending an electronic mail meeting request object simply because the meeting object has been synchronized to the calendar on the desktop. The feature may simply be to only create electronic mail meeting request objects for meeting requests created on the desktop. This feature is implemented to further address the problem of duplicate messaging.
  • electronic mail application program 150 Upon receiving the electronic mail meeting request object indicative of the meeting request, electronic mail application program 150 recognizes that the meeting request needs to be transmitted. Electronic mail application program 150 calls the necessary methods exposed by API 158 to have the appropriate object transported, through communications component 115 and transport 160 , to network 138 . This is again indicated by blocks 172 , 173 , 174 and 190 .
  • the meeting request need not be entirely formatted on mobile device 3 .
  • the data representing the electronic mail meeting request object can simply be stored and transferred during synchronization to desktop computer 4 where it is fully formatted.
  • mobile device 3 does not store the particular transport to be used by desktop computer 4 in sending the meeting request. Since this information is not stored by mobile device 3 , it is not synchronized with desktop computer 4 .
  • electronic mail application program 150 on desktop computer 4 calls the necessary methods through API 156 to have full address book 154 retrieve the transport associated with each of the potential attendees identified by the user. That information is then used by electronic mail application program 150 in choosing the appropriate transport 160 with which to transmit the electronic mail meeting request object. In this way, additional memory capacity need not be consumed on mobile device 3 to store such transport information. This is indicated by block 188 .
  • electronic mail application program 150 causes the electronic mail meeting request object to be transmitted to network 138 , it is removed from the outbox. This is indicated by block 190 .
  • FIG. 8 is a flow diagram illustrating one preferred embodiment of how mobile device 3 ′ handles responses to the meeting requests transmitted in accordance with FIG. 7.
  • the addressee for responses to meeting requests is the meeting originator. Both senders and recipients of the meeting requests can be arranged properly for delegate handling.
  • the publicly available MAPI specification fully discloses how to interpret such properties.
  • the recipient of the meeting request is provided with a suitable user interface to indicate a response.
  • the response is addressed to the meeting originator, or another proper delegate.
  • the response is then transferred by the device which the recipient is operating on and is received through one of transports 132 , 134 or 136 , or through communications component 94 on mobile device 3 . This is indicated by block 194 in FIG. 8.
  • scheduling application program 142 Upon receiving the response, scheduling application program 142 correlates the response to the meeting object which was formed by scheduling application program 142 when the user created the request, and which is stored in object store 6 . This correlation is performed by using the unique global identification number which uniquely identifies that meeting request to all devices which may encounter it. This is indicated by block 196 .
  • the critical time stamp information is then checked to determine whether the response corresponds to the latest meeting object.
  • the response preferably actually contains two time stamps. The first is the recipient's opinion of the originator's critical time stamp. The second is a time stamp assigned by the recipient. The first is checked to determined whether it is the same as the originator's time stamp. If so, the response is considered to be in date. If not, the response is rejected or ignored as an out-of-date response. The second must be equal to or greater than any previously recorded time stamp from this particular recipient for the response to be in date. If not, the response is rejected or ignored as out-of-date. This is indicated by block 197 .
  • time stamps are always moving forward. Thus, even if the user resets the clock sufficiently into the past, any subsequent time stamp is always the later of a current clock time and the last time stamp plus one second.
  • Scheduling application program 142 then calls the necessary methods exposed by API 148 in order to update the attendee status associated with the request. This is updated based on the particular response received from the attendee. This is indicated by block 198 .
  • Mobile device 3 then simply waits to be connected to desktop computer 4 . Once it is connected, the updated objects (containing the updated attendee status property) are synchronized to the instance of that object stored in object store 8 . This is accomplished utilizing the synchronization protocol discussed above. This is indicated by blocks 200 and 202 . The meeting object is then available to scheduling application program 152 and desktop computer 4 to be displayed on the user's calendar at desktop computer 4 for user observation and interaction.
  • FIG. 9 is a flow diagram which illustrates one preferred embodiment of how responses are handled when received through transport 160 on desktop computer 4 .
  • the user first inputs information through an appropriate user interface which defines the user's response to the meeting request.
  • the response is then transmitted back to desktop computer 4 through transport 160 and communications component 115 . This is indicated by block 204 .
  • Scheduling application program 152 correlates the response to the meeting object, as did mobile device 3 , by utilizing the global identification number assigned to the meeting object, and received along with the response to the meeting request. This is indicated by block 206 . The time stamp information is then checked to determine whether the response corresponds to the latest meeting object, again as described above. If not, the response is rejected or ignored as an out-of-date response. This is indicated by block 207 . Scheduling application program 152 then calls the necessary methods exposed by API 158 to modify and update the attendee status of the meeting object stored in object store 8 . This is indicated by block 208 . Desktop computer 4 then simply waits until it is next coupled to mobile device 3 .
  • the updated objects in object store 8 (which have been updated to accurately reflect the new attendee status based on the response) are synchronized to the other instance of that object then stored in object store 6 . Synchronization is accomplished in accordance with the synchronization protocol discussed above. The updated object is then available for review and manipulation by the user of mobile device 3 . This is indicated by blocks 210 and 212 .
  • the mobile device in accordance with an illustrative embodiment of the present invention also handles exceptions to recurring meetings and meeting cancellations.
  • the scheduling PIM erases all exceptions when an update to the recurrence pattern of a recurrent meeting is received.
  • new electronic mail objects must be created and sent for each exception once a charge in the recurrent meeting pattern has been sent. For instance, assuming the user entered a recurring meeting request on mobile device 3 .
  • Scheduling application 142 creates a recurring meeting object and enters it on the calendar of the user.
  • Electronic mail application 140 also creates an electronic mail recurring meeting request object for transmission to potential attendees. The recipients (potential attendees) can respond generally as described above.
  • the first is simply created to indicate the new location which modifies the recurrence pattern. This may also, in some PIMs, erase the previous two exceptions. Thus, two new pieces of electronic mail are created to reinstitute the two exceptions (i.e., the cancellation of the April 8 th meeting and the time change for the April 15 th meeting). These pieces of electronic mail are automatically created by electronic mail application 140 . These same actions are taken in response to other suitable modifications as well, such as modification of the list of attendees.
  • a meeting object is typically accompanied by a textual phrase which describes the nature of the meeting request.
  • the textual phrase is generated based upon the property values input by the user during creation of the meeting request. For example, a user may request the potential attendees to attend a meeting on the third Monday of each month at 10:00 a.m., and for a period which extends from Jan. 1, 2000, to Mar. 20, 2001.
  • a typical text message which might be retrieved and placed in the meeting request object to accompany that object for display to the potential attendees might read as follows:
  • a predetermined text message of the type set out above is generated to describe each different type of recurring meeting which can be requested by the user of mobile device 3 .
  • the text messages used to describe requests for recurring meetings are broken down into a plurality of phrases.
  • Each of the phrases which has been created is broken down into a plurality of fields.
  • the particular phrases which can be created to define a meeting request, and the particular fields into which those phrases are separated can be any suitable phrases and fields.
  • FIG. 11A illustrates one embodiment of the fields into which that phrase can be broken.
  • FIG. 11A shows that a first portion of the phrase “This meeting shall take place on the third Monday of each month” is placed in field 214 .
  • the term “at” is placed in field 216 .
  • the time designation “10:00” is placed in field 218 and the AM/PM designator is placed in field 220 .
  • the term “beginning” is placed in field 222 , and the remaining message is similarly broken up into fields 224 , 226 , 228 , 230 , 234 , 236 , 238 , 240 and 242 .
  • FIG. 10 is a flow diagram illustrating how the localization process works.
  • the creation of the textual phrases defining meeting requests, and the breaking up of those requests into various predetermined fields, is indicated by block 242 .
  • a Vocalizer program is run on mobile device 3 to rearrange fields 214 - 240 , for each of the messages created, such that the messages conform to local convention.
  • the specific localizer program which is run on mobile device 3 will depend on the particular locality and consumer base for which mobile device 3 is intended.
  • mobile device 3 contains a plurality of sets of fields, referred to as templates, into which message data is placed in order to display the textual message in a localized fashion.
  • Running of the localizer program in setting up the templates is indicated by block 244 .
  • mobile device 3 After mobile device 3 has templates which have been localized, mobile device 3 is ready to receive a meeting request and properly display the textual description of the meeting request.
  • the data stream indicative of the textual phrase which describes the meeting is also received by scheduling application program 142 .
  • Scheduling application program 142 parses the incoming data stream into values associated with the various fields in the appropriate template (the appropriate template corresponds to the specific textual description being received) This is indicated by block 248 .
  • the parsed data is placed into preselected fields in the templates based on the created phrases. This is indicated by block 250 . Because the localizer program has already been run, the fields in the templates are already placed in appropriate order to conform to local convention.
  • FIG. 11B illustrates the rearrangement of the fields in the template illustrated in FIG. 11A to conform to a different convention.
  • FIG. 11B illustrates the conformation of the phrase to a convention in which the phrasing is slightly different from that shown in FIG. 11A, and in which the day is conventionally placed prior to the month in a date.
  • the phrase now contains the same terms, but reads:
  • time zone information is handled in an advantageous manner. For instance, when a recurring meeting request is created and sent to a device located in a different time zone, the textual phrase indicative of the recurring meeting includes an indication of the time zone in which the recurring meeting request was created. For instance, if a user in Paris sends a recurring meeting request to a recipient in Seattle (nine hours different) for a meeting occurring every Tuesday at 8:00 a.m. beginning March 3, the textual phrase may be:
  • the time is preferably simply displayed as the appropriate time for the recipient (e.g., “This meeting is scheduled for Tuesday at 11:00 p.m.”).
  • the present invention provides significant advantages over prior systems.
  • the present invention allows the creation of a meeting request from a mobile device itself.
  • the present invention further identifies the object associated with such a meeting request in a manner which uniquely identifies the object to all other devices likely to encounter the object.
  • the present invention also utilizes a feature in the PIMs which indicates whether the meeting request has been sent to potential attendees. These features eliminate duplicate messaging.
  • the present invention also preferably implements features which reduce the memory required to implement the meeting request feature by use of an abridged address book. Further, the present invention preferably uses a set of scheduling properties which are compatible with a plurality of different PIMs likely to encounter the meeting request. In addition, the present invention preferably utilizes localization procedures which localize meeting requests to more closely conform to local convention and handle time zone information in an advantageous manner. The present invention also preferably supports the use of multiple electronic mail transports as well as a synchronization protocol.

Abstract

The present invention includes a mobile device which provides the user with the ability to schedule a meeting request from the mobile device itself. The mobile device creates an object representative of the meeting request and assigns the object a global identification number which uniquely identifies the object to other devices which encounter the object. In addition, the mobile device in accordance with one aspect of the present invention provides a property in the object which is indicative of whether the meeting request has already been transmitted. In this way, other devices which encounter the meeting request are capable of identifying it as a unique meeting request, and of determining whether the meeting request has already been transmitted, in order to alleviate the problem of duplicate meeting request transmissions.

Description

    REFERENCE TO CO-PENDING PATENT APPLICATION
  • This patent application claims the priority of the following two U.S. provisional patent applications, serail No. _______ entitled “FEATURES OF A MOBILE DEVICE AND ASSOCIATED COMPUTER”, filed on Oct. 24, 1997 and Ser. No. entitled “FEATURES OF A MOBILE DEVICE AND ASSOCIATED COMPUTER”, filed on Nov. 7, 1997. [0001]
  • Reference is hereby made to the following co-pending U.S. patent applications which are hereby incorporated by reference: [0002]
  • Ser. No. ______, filed on even date herewith, entitled “ELECTRONIC MAIL OBJECT SYNCHRONIZATION BETWEEN A DESKTOP COMPUTER AND MOBILE DEVICE”; and [0003]
  • Ser. No. ______, filed on even date herewith, entitled “SYSTEM AND METHOD FOR INTERACTION BETWEEN A DESKTOP COMPUTER AND MULTIPLE MOBILE DEVICE”, all of which are assigned to same assignee as the present invention.[0004]
  • BACKGROUND OF THE INVENTION
  • Mobile devices are small electronic computing devices often referred to as personal digital assistants. One such mobile device is sold under the trade name Handheld PC (or “H/PC”) based on a Windows CE brand operating system provided by Microsoft Corporation of Redmond, Washington. While a wide variety of computing tasks and applications can be performed by such mobile devices, personal information managers (PIMs) are particularly well suited to mobile devices. [0005]
  • PIMs typically comprise applications which enable the user of the mobile device to better manage scheduling and communications, and other such tasks. Some commonly available PIMs include scheduling and calendar programs, task lists, address books, and electronic mail (e-mail) programs. Some commonly commercially available PIMs are sold under the brand names Microsoft Schedule+ and Microsoft Outlook and are commercially available from Microsoft Corporation of Redmond, Washington. For purposes of this discussion, PIMs shall also include separate electronic mail applications, such as that available under the brand name Microsoft Exchange. [0006]
  • It is also common for mobile devices to be used in conjunction with a desktop computer. For example, the user of a mobile device may also have access to, and use, a desktop computer at work, at home, or both. A user may typically run the same types of PIMs on both the desktop computer and the mobile device (although the particular versions of the PIMs may be somewhat different from the desktop computer to the mobile device). Thus, it is quite advantageous for the mobile device to be designed to be couplable to the desktop computer to exchange information with, and share information with, the desktop computer. [0007]
  • The user may also typically make changes to the PIMs both on the mobile device, and at the desktop. Therefore, it is advantageous for the PIMs on both the mobile device and the desktop to contain the most up-to-date information, regardless of whether recent changes to the PIMs have been made on the mobile device or the desktop computer. The process of coupling the mobile device with the desktop computer, and integrating the information stored by the PIMs on the mobile device and the desktop computer such that the two contain the same updated information is referred to as synchronization. [0008]
  • Conventional PIMs which support electronic calendaring and scheduling features (collectively referred to as a scheduler, or as a scheduling application) are traditionally supported on desktop computers. Such PIMs provide the ability of the user to schedule a meeting request for one or more desired attendees. [0009]
  • In order to generate a meeting request, the user typically interacts with the scheduling application through a user interface. The user interface provides the user with a plurality of selectable options to parameterize the meeting request. For example, the user interface typically allows the user to pick a date and time (and often a place) on which the meeting is to be held. The user interface also typically allows the user to select a group of attendees that the user wishes to attend the meeting, to enter some textual description of the meeting, and to specify whether the meeting is for only a single date, or is a recurring meeting (i.e., whether the meeting is to occur only on one date, the 15[0010] th of every month, the first Monday of every month, every Monday, etc.).
  • Based on this information, the scheduling application creates an object which is representative of the meeting and enters it on the user's calendar as an appointment. Such objects are typically defined by a number of properties, some of which are defined by the user input information which the user provides while generating the meeting request. The meeting object also contains a critical time stamp (UTC) which is updated whenever a critical change is made to the meeting object, such as changes to the start or end date or time, changes in the location, etc. [0011]
  • Since other people are identified as attendees, the appointment entered on the calendar is viewed as a meeting and the scheduling application typically calls methods exposed by an electronic mail application in accordance with messaging application programming interfaces (MAPI), or other APIs which are a set of well documented, published interfaces commercially available from the Microsoft Corporation of Redmond, Washington. [0012]
  • In response, the electronic mail application creates another object (an electronic mail meeting request object) indicative of the meeting request and the electronic mail application (or suitable transport) formats this electronic mail meeting request object into a well defined electronic mail message suitable for transmission. In doing so, the critical time stamp from the meeting object is also placed in the electronic mail meeting request object. [0013]
  • The electronic mail application then interacts with a specified transport and transports the electronic mail meeting request object to a network which routes it to the designated attendees. In doing so, the electronic mail application typically accesses an address book stored in a database to obtain the fully qualified electronic mail address for the attendees. This is also typically done by calling MAPI or other suitable API methods associated with the database storing the address book. The generation of the meeting object and the creation of the electronic mail meeting request object will be referred to herein collectively as creating a meeting request. [0014]
  • The potential attendees then typically respond to the meeting request. In doing so, the originator's critical time stamp is sent back (unmodified) along with the response. The response also includes a recipient critical time stamp and an indication of the recipient's response (e.g., accept, decline, tentative, etc.). The recipient critical time stamp is updated by the recipient (potential attendee) whenever a critical change is made by the recipient. [0015]
  • This allows the user to reliably order receipt of multiple versions of the same meeting (e.g., where the originator changes the time, date or location of the meeting such that multiple meeting requests are generated). It also allows the originator to reliably order receipt of responses and ensure that each response correlates to the most recent version of the meeting. [0016]
  • The response is then transmitted back to the originator (e.g., the sending computer). The electronic mail application and scheduling application on the originator then typically process the response (or responses) accordingly. For example, the originator stores, for each recipient (or potential attendee) the recipient critical time stamp in a table along with each recipient's response code (which is indicative of the accept, decline, tentative response). The two commercially available PIMs identified above (the Microsoft Schedule+ and Microsoft Outlook brand PIMs) are examples of PIMs which support the features discussed above. [0017]
  • Meeting cancellations, and exceptions to recurring meeting must also be handled. For example, the PIMs may allow scheduled meetings to be cancelled, and allow a variety of exceptions to a recurring meeting pattern. [0018]
  • Scheduling of meeting requests as described above has, to date, only been supported by desktop computers or laptop computers which are fitted with a hard disk drive or other high capacity memory mechanisms, or by low intelligence terminals which are permanently attached to a server or other similar computer which, itself, contains a high capacity storage device. The ability to schedule a meeting request from a mobile device is simply unavailable. While some current mobile devices are provided with PIMs that allow the user to view meeting requests, and to view meetings which have already been scheduled, current mobile devices do not allow the user to generate a meeting request from the mobile device itself. [0019]
  • A number of significant obstacles present themselves when attempting to provide the user with the capability of generating a meeting request from a mobile device. Meeting cancellations and exceptions to recurring meetings must be handled. Also, a significant problem arises with respect to the possibility of transmitting duplicate meeting requests. While duplicate meeting requests as described below may not necessarily be created with all PIMs, they do present a potential problem which must be considered. For example, if the user of the mobile device were able to generate a meeting request, a meeting object would first be entered on the calendar of the mobile device. The electronic mail application on the mobile device would then create a corresponding electronic mail meeting request object. [0020]
  • The next time the mobile device was synchronized with the desktop computer, the meeting object would be synchronized with the calendar object store on the desktop computer and the electronic mail meeting request object would be synchronized to the desktop outbox. The desktop computer, would recognize the electronic mail meeting request object in its outbox, format it for transmission, and transmit it over the network. Further, synchronizing the meeting object to the calendar of the desktop computer may result in another electronic mail meeting request object being created and transmitted by the desktop computer. This would result in duplicate electronic mail meeting request objects being created (one by the mobile device, and one by the desktop computer after synchronization) and transmitted. Under that scenario, potential attendees would receive two or more meeting requests, and may respond to both. This would create duplicate responses to what was intended to be a single meeting request. [0021]
  • A similar problem may occur if a meeting request were generated in a conventional manner (on a desktop computer) for instance, and was then synchronized to a mobile device having the capability of generating and transmitting meeting requests. The meeting object on the desktop calendar would be synchronized to the calendar of the mobile device. The mobile device might then recognize the meeting object synchronized from the desktop, and create an electronic mail meeting request object and attempt to transmit the object. This would result in substantially the same problem—duplicate meeting requests and duplicate responses for what was intended to be a single meeting request. [0022]
  • Further, if the user of the mobile device coupled the mobile device for synchronization with more than one desktop computer (e.g., a home computer and work computer, if the mobile device were provided with this capability) the same problem would result. In that instance, and using conventional architecture, both desktop computers would synchronize with, and recognize, the meeting object and the electronic mail meeting request object from the mobile device. The desktop computers would both potentially create additional electronic mail meeting request objects and transmit them to the potential attendees. Again, this would result in many different meeting requests and responses being transmitted for what was intended to be only a single meeting request. [0023]
  • In addition, if mobile devices were provided with the capability of being connected directly to one another, and communicating with one another, without going through a desktop or similar computer, the meeting request could be generated by one mobile device, responded to by another mobile device, and scheduled on both mobile devices. However, the next time the first mobile device is synchronized with the desktop computer, that computer might again recognize the meeting object synchronized from the calendar of the mobile device, create another electronic mail meeting request object and transmit the electronic mail meeting request object. Thus, a significant problem potentially exists with respect to the generation of multiple meeting requests. [0024]
  • Of course, similar problems also result from critical changes to the meeting object on either the desktop computer or the mobile device. This will cause unwanted duplicate electronic mail meeting requests in a similar fashion. [0025]
  • Additional problems also present themselves simply by the fact that conventional mobile devices have a memory capacity which is significantly less than that of a desktop computer or similar computer. Thus, problems arise with respect to storing address books on the mobile device itself which contain the fully qualified electronic mail address of all potential attendees. [0026]
  • Further obstacles present themselves because many desktop computers on which the meeting request must be processed have different scheduling applications. Therefore, the meeting request generated by the mobile device may be incompatible with scheduling applications which it encounters. [0027]
  • In addition, localization of meeting requests can present a problem. For instance, in some localities, it is conventional, when writing a date, to place the month first, the day second and the year third. In other localities, other orders are conventional. Further, a textual description which describes the meeting and which accompanies the meeting request, may need to be rearranged to conform to local convention. Also, meeting requests can be generated in one time zone and transmitted to recipients in other time zones. This can tend to be confusing. [0028]
  • The present invention addresses some or all of these obstacles. [0029]
  • SUMMARY OF THE INVENTION
  • The present invention includes a mobile device which provides the user with the ability to schedule a meeting request from the mobile device itself. The mobile device creates an object representative of the meeting request and assigns the object a global identification number which uniquely identifies the object to other devices which encounter the object. In this way, other devices which encounter the meeting request are capable of identifying it as a unique meeting request in order to alleviate the problem of duplicate meeting request transmissions. [0030]
  • In accordance with another preferred feature of the present invention, an electronic mail application or calendar application on the mobile device obtains a fully qualified electronic mail address for the potential attendees from an abridged address book or directory stored on the mobile device itself. This alleviates problems associated with the storage capacity of the mobile device. [0031]
  • In accordance with another preferred embodiment of the present invention, the mobile device creates the meeting object and the electronic mail meeting request object using a set of properties which are supported by a plurality of PIMs that may receive the objects . This provides compatibility with an increased number of devices which are likely to encounter the objects. [0032]
  • In accordance with yet another preferred feature of the present invention, localizers implement a plurality of templates on the mobile device which are used in formatting the properties of the objects associated with the meeting request. A data stream representative of the meeting request is parsed by the mobile device and placed in pre-defined fields in the appropriate templates so that the text viewed by the user of the mobile device more closely conforms to local convention. In addition, time zone information is also included in one embodiment.[0033]
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • FIG. 1 is a block diagram illustrating a basic environment of the present invention. [0034]
  • FIG. 2 is a block diagram of one embodiment of a conventional desktop computer used in conjunction with a mobile device in accordance with the present invention. [0035]
  • FIG. 3 is a simplified pictorial illustration of one embodiment of a mobile device in accordance with the present invention. [0036]
  • FIG. 4 is a simplified block diagram of one embodiment of the mobile device shown in FIG. 3. [0037]
  • FIG. 5 is an architectural block diagram illustrating one embodiment of portions of the desktop computer shown in FIG. 2 and the mobile device shown in FIGS. 3 and 4 to illustrate synchronization of information stored in object stores on the desktop computer and the mobile device in accordance with the present invention. [0038]
  • FIG. 6 is an architectural block diagram illustrating one embodiment of portions of the desktop computer shown in FIG. 2 and the mobile device shown in FIGS. 3 and 4 to illustrate the generation and transmission of a meeting request. [0039]
  • FIG. 7 is a flow diagram illustrating the generation of a meeting request in accordance with one preferred embodiment of the present invention. [0040]
  • FIG. 8 is a flow diagram illustrating the handling of responses to a meeting request on the mobile device shown in FIGS. 3 and 4 in accordance with one preferred embodiment of the present invention. [0041]
  • FIG. 9 is a flow diagram illustrating the handling of responses to a meeting request on the desktop computer shown in FIG. 2 in accordance with one preferred embodiment of the present invention. [0042]
  • FIG. 10 is a flow diagram illustrating the use of a localizer to localize the textual description of a meeting request in accordance with one preferred embodiment of the present invention. [0043]
  • FIGS. 11A and 11B illustrate one embodiment of a template used to localize the textual description of a meeting request in accordance with the present invention.[0044]
  • DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS OVERVIEW
  • FIG. 1 is a block diagram of a typical system or environment [0045] 2 in which the present invention operates. Environment 2 includes mobile device 3 and desktop computer 4. FIG. 1 also illustrates that mobile device 3 can optionally be separately coupled to another mobile device 10 or another desktop computer 13.
  • [0046] Mobile device 3 includes an application program 5 and an object store 6. Desktop computer 4 also includes an application program 7 and an object store 8. Mobile device 10 includes an application program 11 and object store 12. Further, desktop computer 13 includes an application program 14 and an object store 15.
  • [0047] Mobile device 3 is couplable to desktop computer 4, mobile device 10 or desktop computer 13 by one of a plurality of connection mechanisms 9. The operation of desktop computers 4 and 13 and the operation of mobile devices 3 and 10 are preferably similar. Therefore, for the sake of simplicity, the present description proceeds only with respect to mobile device 3 and desktop computer 4.
  • In one preferred embodiment of the present invention, [0048] application program 7 on desktop 4 is a personal information manager (PIM) which supports electronic mail messaging, scheduling and calendaring and an address book containing contact information.
  • PIM applications are not always integrated. For instance, some scheduling programs do not contain electronic mail features, but interface with whatever electronic mail program is provided, and vice versa. Of course, PIM [0049] 7 (whether it be a single application, a single integrated application or multiple interfaced applications) can be configured to support a wide variety of other features, such as task lists and personalized address books, to name a few. However, for the sake of clarity, only features relating to electronic mail messaging, scheduling and calendar features, and address book features are discussed in detail with respect to the present invention.
  • [0050] Object store 8 is a memory which is configured to store a plurality of individual records or objects, each comprising a plurality of fields or properties related to the above-mentioned features. In one preferred embodiment, PIM 7 is a program, such as that available under the commercial designation Microsoft Outlook 97, and object store 8 is configured to store objects, each of which has a plurality of properties which can be associated with electronic mail messaging, scheduling and calendaring, and contact information.
  • For example, some properties included in an object associated with electronic mail messaging include the sender's name, the recipient's name, text messages, an indication of whether attachments are attached to any given electronic mail message, and possibly other similar properties. Also, some properties associated with scheduling and calendaring include critical time stamp information, date and time information, potential attendees, recurrence properties which describe recurrent meetings or meeting requests, and a textual description of the meeting request. Some properties associated with contact information include the proper names, or familiar names, of those in the contact list, the addresses and telephone numbers of those listed, and the fully qualified electronic mail address for those in the list. Any number of other properties can also be included. [0051] Desktop computer 4 executes the application program identified as PIM 7 to maintain objects stored in object store 8.
  • The application program designated as [0052] PIM 5 for mobile device 3 is a similar PIM to that stored on desktop computer 4. Object store 6 on mobile device 3 is configured to store a plurality of individual records or objects, each comprising a plurality of fields or properties related to the above-mentioned, supported features. As with PIM 7, PIM 5 can also support a wide variety of other features. However, for the sake of clarity, only those features related to the present invention are discussed in detail herein.
  • In one illustrative embodiment, each object in [0053] object store 6 comprises the same set of properties stored in object store 8 for related messages, or a subset of those properties. In addition, the objects stored in object store 6 also preferably include a critical change time stamp, properties which indicate whether potential attendees identified in a meeting request have responded, and a global identification of each individual meeting request (discussed in greater detail below). Mobile device 3 executes PIM 5 to maintain the objects in object store 6.
  • In the illustrative embodiment, each object stored in [0054] object store 8 is also stored in object store 6. However, there are actually two instances of each object (one in object store 6 and one in object store 8). Thus, when a user changes one instance of the object stored in either store 6 or store 8, the second instance of that object in the other of stores 6 and 8 is preferably updated the next time mobile device 3 is connected to desktop computer 4 so that both instances of the same object contain up-to-date data. This is referred to as synchronization.
  • In order to accomplish synchronization, synchronization components run on both [0055] mobile device 3 and desktop computer 4. The synchronization components communicate with PIMs 5 and 7 on mobile device 3 and desktop computer 4 through well defined interfaces to manage communication and synchronization.
  • The components of [0056] mobile device 3 and desktop computer 4 communicate with each other through any suitable, and commercially available, communication link 9, and using a suitable communications protocol. For instance, in one preferred embodiment, mobile device 3 is connectable to desktop computer 4 with a physical cable which communicates using a serial communications protocol. Other communication mechanisms are also contemplated by the present invention, such as infrared (IR) communication, direct modem communication, remote dial-up networking communication, communication through commercially available network cards (i.e., using TCP/IP), remote access services (RAS), wireless modem, wireless cellular digital packet data (CDPD), or other suitable communication mechanisms.
  • FIG. 2 and the related discussion are intended to provide a brief, general description of a [0057] suitable desktop computer 4 in which portions of the invention may be implemented. Although not required, the invention will be described, at least in part, in the general context of computer-executable instructions, such as program modules, being executed by a personal computer 4 or mobile device 3. Generally, program modules include routine programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. Moreover, those skilled in the art will appreciate that desktop computer 4 may be implemented with other computer system configurations, including multiprocessor systems, microprocessor-based or programmable consumer electronics, network PCs, minicomputers, mainframe computers, and the like. The invention may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote memory storage devices. Examples of distributed programs include those available under the commercial designations Exchange, Schedule+ and MS Mail, all available from Microsoft Corporation.
  • With reference to FIG. 2, an exemplary system for implementing [0058] desktop computer 4 includes a general purpose computing device in the form of a conventional personal computer 4, including processing unit 21, a system memory 22, and a system bus 23 that couples various system components including the system memory to the processing unit 21. The system bus 23 may be any of several types of bus structures including a memory bus or memory controller, a peripheral bus, and a local bus using any of a variety of bus architectures. The system memory includes read only memory (ROM) 24 and random access memory (RAM) 25.
  • A basic input/output system (BIOS) [0059] 26, containing the basic routine that helps to transfer information between elements within the desktop computer 4, such as during start-up, is stored in EEPROM which is part of ROM 24. The desktop computer 4 further preferably includes a hard disk drive 27 for reading from and writing to a hard disk (not shown), a magnetic disk drive 28 for reading from or writing to removable magnetic disk 29, and an optical disk drive 30 for reading from or writing to a removable optical disk 31 such as a CD ROM or other optical media. The hard disk drive 27, magnetic disk drive 28, and optical disk drive 30 are connected to the system bus 23 by a hard disk drive interface 32, magnetic disk drive interface 33, and an optical drive interface 34, respectively. The drives and the associated computer-readable media provide nonvolatile storage of computer readable instructions, data structures, program modules and other data For the desktop computer 4.
  • Although the exemplary environment described herein employs a hard disk, a removable [0060] magnetic disk 29 and a removable optical disk 31, it should be appreciated by those skilled in the art that other types of computer readable media which can store data that is accessible by a computer, such as magnetic cassettes, flash memory cards, digital video disks (DVDs) , Bernoulli cartridges, random access memories (RAMs), read only memory (ROM), and the like, may also be used in the exemplary operating environment.
  • A number of program modules may be stored on the hard disk, [0061] magnetic disk 29, optical disk 31, ROM 24 or RAM 25, including an operating system 35, one or more application programs 36 (which include PIMs 7), other program modules 37, and program data 38. A user may enter commands and information into the desktop computer 4 through input devices such as a keyboard 40, pointing device 42 and microphone 62. Other input devices (not shown) may include a joystick, game pad, satellite dish, scanner, or the like. These and other input devices are often connected to the processing unit 21 through a serial port interface 46 that is coupled to the system bus 23, but may be connected by other interfaces, such as a sound card, a parallel port, a game port or a universal serial bus (USB) . A monitor 47 or other type of display device is also connected to the system bus 23 via an interface, such as a video adapter 48. In addition to the monitor 47, desktop computers may typically include other peripheral output devices such as speaker 45 and printers.
  • The [0062] desktop computer 4 may operate in a networked environment using logic connections to one or more remote computers (other than mobile device 3), such as a remote computer 49. The remote computer 49 may be another personal computer, a server, a router, a network PC, a peer device or other network node, and typically includes many or all of the elements described above relative to desktop computer 4, although only a memory storage device 50 has been illustrated in FIG. 2. The logic connections depicted in FIG. 2 include a local area network (LAN) 51 and a wide area network (WAN) 52. Such networking environments are commonplace in offices, enterprise-wide computer network intranets and the Internet.
  • When used in a LAN networking environment, the [0063] desktop computer 4 is connected to the local area network 51 through a network interface or adapter 53. When used in a WAN networking environment, the desktop computer 4 typically includes a modem 54 or other means for establishing communications over the wide area network 52, such as the Internet. The modem 54, which may be internal or external, is connected to the system bus 23 via the serial port interface 46. In a network environment, program modules depicted relative to desktop computer 4, or portions thereof, may be stored in the remote memory storage devices. It will be appreciated that the network connections shown are exemplary and other means of establishing a communications link between the computers may be used.
  • [0064] Desktop computer 4 runs operating system 35 that is typically stored in non-volatile memory 24 and executes on the processor 21. One suitable operating system is a Windows brand operating system sold by Microsoft Corporation, such as Windows 95 or Windows NT, operating systems, other derivative versions of Windows brand operating systems, or another suitable operating system. Other suitable operating systems include systems such as the Macintosh OS sold from Apple Corporation, and the OS/2 Presentation Manager sold by International Business Machines (IBM) of Armonk, N.Y. PIM 7 is preferably stored in program module 37, in volatile memory or non-volatile memory, or can be loaded into any of the components shown in FIG. 2 from a floppy diskette 29, CDROM drive 31, downloaded from a network via network adapter 53, or loaded using another suitable mechanism.
  • A dynamically linked library (DLL), comprising a plurality of executable functions is associated with [0065] PIM 7 for execution by processor 21. Interprocessor and intercomponent calls are facilitated using the component object model (COM) as is common in programs written for Microsoft Windows brand operating systems. Briefly, when using COM, a software component such as a DLL has a number of interfaces. Each interface exposes a plurality of methods, which can be called individually to utilize different services offered by the software component. In addition, interfaces are provided such that methods or functions can be called from other software components which optionally receive and return one or more parameter arguments.
  • In general, the DLL associated with [0066] PIM 7 is designed specifically to work in conjunction with PIM 7 and to expose desktop synchronization interfaces that function as described in more detail in the above-referenced co-pending U.S. patent application according to a synchronization protocol. The DLL, in turn, calls interfaces exposed by PIM 7 in order to access data representing individual properties of objects maintained in object store 8. Object store 8, of course, can reside in any one of the suitable memory components described with respect to FIG 2.
  • FIG. 3 is a pictorial illustration of one preferred embodiment of a [0067] mobile device 3 which can be used in accordance with the present invention. Mobile device 3, in one preferred embodiment, is a desktop assistant sold under the designation H/PC and being based on, for example, the Windows CE brand operating system provided by Microsoft Corporation. In one preferred embodiment, mobile device 3 is housed in a housing which fits comfortably in the hand of a typical user. Mobile device 3 has some components which are similar to those of desktop computer 4. For instance, in one preferred embodiment, mobile device 3 includes a miniaturized keyboard 82, display 84, and stylus 86. Of course, other configurations, such as without keyboards, can also be used.
  • In the embodiment shown in FIG. 3, [0068] display 84 is a liquid crystal display (LCD) which uses a contact-sensitive display screen in conjunction with stylus 86. Stylus 86 is used to press or contact the display 84 at designated coordinates to accomplish certain user input functions. Of course, other user input configurations can be used as well. For example, user input mechanisms could be included such as a keypad, a track ball, and other various types of miniaturized keyboards, or the like. In addition, mobile device 3 may not be embodied as the H/PC brand of digital assistant, but could also be implemented as another type of personal digital assistant (PDA), another personal organizer, a palm top computer, or a similar computerized notepad device.
  • FIG. 4 is a more detailed block diagram of [0069] mobile device 3. Mobile device 3 preferably includes microprocessor 88, memory 90, input/output (I/O) components 92 (which include keyboard 82 and touch sensitive screen 84), optional expansion slots 93 (which can be used for plugging in such things as PC cards, compact flash memory, etc.) and serial interface 94. In the illustrative embodiment, these components of mobile device 3 are coupled for communication with one another over a suitable bus 96.
  • In the illustrative embodiment, [0070] memory 90 is implemented as non-volatile electronic memory such as a random access memory (RAM) with a battery back-up module (not shown) such that information stored in memory 90 is not lost when the general power to mobile device 30 is shut down. A portion of memory 90 is preferably allocated as addressable memory for program execution, while another portion of memory 90 is preferably used to simulate storage on a disk drive.
  • [0071] Memory 90 includes operating system 98 and application (or PIM) 5. Operating system 98, during operation, is preferably loaded into, and executed by, processor 88 from memory 90. Operating system 98, in one preferred embodiment, is the Windows CE brand operating system. The operating system 98 is preferably designed for mobile devices, and implements database features which can be utilized by PIM 5 through a set of exposed application programming interfaces and methods. The objects in object store 6 are preferably maintained by PIM 5 and operating system 98, at least partially in response to calls to the exposed application program interfaces and methods.
  • It should be noted that [0072] PIM 5 is not necessarily designed to be entirely compatible with PIM 7 which executes on desktop computer 4. For instance, there may not be a precise one-to-one matching between the properties of specific object types. Some properties supported by the electronic mail messaging features of PIM 5 may have no corresponding features in PIM 7 on desktop computer 4, and vise versa.
  • Object Synchronization
  • While object synchronization is described in greater detail in the above-referenced co-pending patent applications, it is described here, briefly, to assist in understanding the present invention. [0073]
  • FIG. 5 is an architectural block diagram illustrating one preferred embodiment of architectural components of [0074] mobile device 3 and desktop computer 4 which are used in synchronizing objects stored in object store 6 on mobile device 3 and object store 8 on desktop computer 4. It should be noted that the synchronization architecture illustrated in FIG. 5 is but one preferred embodiment and others could be used as well. Further, the synchronization operation can be carried out between any two coupled stores (such as those on any combination of pairs of computers 4 and 13, and mobile devices 3 and 10). All that is required is a synchronization manager component, as described below, which directs synchronization of the two coupled stores. The synchronization manager can reside on either device, or both, or on a third computer coupled to the two stores. However, for the sake of simplicity, only the embodiment in which desktop computer 4 is coupled to mobile device 3 is described herein. Also, the present synchronization protocol is but one preferred embodiment, as another suitable protocol could be implemented on top of standard electronic mail protocols.
  • In addition to [0075] PIM 5 and object store 6, mobile device 3 includes synchronization module 97 which, in turn, includes interface component 100, and synchronization manager 102. Mobile device 3 also includes communications component 94, remote application programming interface (RAPI) server 116, and electronic mail messaging transports 132, 134 and 136.
  • [0076] Desktop computer 4 includes, in addition to PIM 7 and object store 8, synchronization module 99 which, in turn, includes interface component 108, synchronization manager 110, reference store 112, and RAPI component 114. Desktop computer 4 also includes communications component 115.
  • Generally, in the embodiment illustrated in FIG. 5, [0077] synchronization manager 110 executes on desktop computer 4 and orchestrates synchronization between objects in object store 6 in handheld device 3, and objects in object store 8 in desktop computer 4. Synchronization manager 110 also maintains reference store 112 apart from desktop object store 8 as is described in greater detail below. Synchronization manager 110 implements the synchronization protocol to allow a comparison between corresponding objects stored in object store 6 in mobile device 3 and object store 8 in desktop computer 4, to receive objects from object store 8, and to update objects in object store 8. The synchronization protocol also facilitates the retrieval of objects stored in object store 6 in mobile device 3 through synchronization interface component 100 and synchronization manager 102, as well as communications component 94.
  • On the side of [0078] mobile device 3, the synchronization interface component 100 exposes application programming interfaces which synchronization manager 102 calls to read and store objects and object properties on object store 6. In general, the application programming interfaces allow the creation of databases for different types of objects, and allow application programs to write and read property names and values to and from respective objects within object store 6.
  • As discussed with respect to FIG. 1, [0079] PIM 5 executes on mobile device 3 and maintains object store 6. PIM 7 executes on desktop computer 4 and maintains object store 8. There are many different ways which PIMs 5 and 7 can store objects in object stores 6 and 8. However, in a preferred embodiment PIMs 5 and 7 create a distinct database for each object type. For example, different databases are created for meetings, contacts, tasks, electronic mail messages, etc. A predefined set of properties is supported for each object type, and each of the databases is assigned a name by the application program that creates it.
  • In an alternative embodiment, the application programs in [0080] PIMs 5 and 7 may use a single database for all object types, with the first property of each object defining the type of object. In any case, objects are uniquely identified within mobile device 3 and desktop computer 4 by object identifiers which are independent of the names assigned by the application programs creating the object.
  • [0081] Synchronization manager 110 is not necessarily closely associated with PIM 7. Rather, it is an independent component which synchronizes objects from any application program that supports the appropriate desktop synchronization interfaces. The specific synchronization interfaces are described in greater detail in the co-pending patent application incorporated above. Communication components 94 and 115 implement serial communications between the computers using suitable link 9.
  • [0082] Synchronization manager 110 communicates with PIM 7 and accesses object store 8 through synchronization interface component 108. Synchronization interface component 108 corresponds generally to a DLL discussed with respect to FIG. 2 above, and exposes one or more application program interfaces and method.
  • The interfaces and methods are described in greater detail in the co-pending patent application which is incorporated above by reference. Of these interfaces, one of note is preferably of the form known as messaging application program interfaces (MAPI) developed and published by the Microsoft Corporation for Windows brand operating system platforms, but other suitable interfaces can be used as well. In one preferred embodiment, the MAPI exposed by [0083] component 108 is a C-language application programming interface which allows programmable access to features of an electronic mail messaging program known as MS Mail also commercially available from the Microsoft Corporation. In another preferred embodiment, the MAPI exposed by component 108 is a component object model based (COM-based) set of interfaces which is sometimes referred to as extended MAPI and includes a set of automation interfaces to messaging systems, for use in Visual Basic and the like. However, synchronization interface component 108 and the associated application program interfaces and methods can be any suitable synchronization interface components designed for any particular application in PIM 7. Because the application program interfaces are preferably standardized, they allow synchronization manager 110 to access and synchronize any number of different desktop PIMs, as long as the required interface methods are implemented for each PIM.
  • [0084] Reference store 112 provides a mapping between instances of objects stored in object store 6 on mobile device 3 and objects stored in object store 8 on desktop computer 4. Since the same object identifiers are not used by PIM 5 to identify objects on object store 6 as are used by PIM 7 to identify objects in object store 8, this mapping is required.
  • [0085] Synchronization manager 110 maintains reference store 112 so that reference store 112 contains the identifying data segments corresponding respectively to a plurality of object instances in object store 8 on desktop computer 4 that are to be synchronized with instances of the same object in object store 6 on mobile device 3. The identifying data segments are updated each time corresponding object instances have been synchronized.
  • The exact composition of an identifying data segment which is used to identify the particular object instances are assignable by the developer of the desktop [0086] synchronization interface component 108, and are then handled and stored by synchronization manager 110. The identifying data segments preferably include some sort of time stamp information which can be compared to determine whether an object has changed since the identifying data segment was last recorded in reference store 112.
  • In addition to maintaining a plurality of identifying data segments, [0087] synchronization manager 110 also maintains a list of object identifiers corresponding to objects maintained in object store 6. These identifiers are provided to synchronization manager 110 whenever a new object is added to object store 6 on mobile device 3.
  • Synchronization Protocol
  • The exact protocol by which full synchronization is accomplished in accordance with one embodiment of the present system is described in greater detail in the above referenced patent application. However, a brief discussion of that protocol is helpful in understanding of the present invention. In order to synchronize objects, [0088] synchronization manager 110 first creates two lists of handles which refer to particular objects. The term “handle” refers to a number or other identifier that can be used to uniquely identify an object and to access the object. Generally, a handle is valid for a particular time period or session, such as during the time when an object has been “opened.” If the same object is opened again, its handle may be different.
  • The first list of handles is obtained from [0089] reference store 112 and is indicative of objects which have been synchronized in the past and are identified in reference store 112. The second list of handles is a list which identifies the objects stored on object store 8. The two lists of handles are compared against one another to determine whether the same objects are stored in reference store 112 and object store 8.
  • If an object is identified in [0090] reference store 112, but not in object store 8, that particular object has been deleted from the desktop 4 since the last synchronization. On the other hand, if an object is identified in object store 8, but it does not appear in reference store 112, then it has been added to the desktop since the last synchronization. In either case, synchronization manager 110 determines how to handle the object. In one preferred embodiment, those objects which have been deleted from desktop object store 8 are also deleted from reference store 112. Further, those which have been added to object store 8 are also added to reference store 112.
  • [0091] Synchronization manager 110 then determines whether any of the objects stored in object store 8 have been modified at the desktop since the last synchronization. In other words, if handles corresponding to the same object appear in both object store 8 and reference store 112, but they are not identical (such as the time stamp, a revision number, or another suitable identifying segment is not the same) that indicates that the object in object store 8 has been modified since the last synchronization.
  • [0092] Synchronization manager 110 then determines whether any objects stored in object store 6 on mobile device 3 have been added or modified since the last synchronization. To determine whether an object has been added to object store 6, synchronization manager 110 compares the list of objects in reference store 112 (which reflects all objects at the last synchronization) with a list of objects on object store 6 maintained by synchronization manager 102. To determine whether an existing object has been modified, synchronization manager 102 is configured to maintain a status bit associated with each object stored in object store 6. The status bit reflects whether the particular object associated with that bit has been changed since the last synchronization. If so, synchronization manager 102 notifies synchronization manager 110 of that change if device 3 is then coupled to desktop computer 4, or simply logs the status bit and sends it to synchronization manager 110 the next time device 3 is coupled to desktop computer 4.
  • It should be noted that none of these procedures require either [0093] synchronization manager 110 or synchronization manager 102 to be aware of the particular nature or format of the identifying data segments or of the objects to which they correspond. Rather, interface components 100 and 108 are called upon for all actions that depend upon the actual content of the identifying data segments, and the content of the objects. It is up to the designer of those interfaces to define a format for the identifying data segments that allows the interfaces to perform their required functions.
  • Once the changes, additions and deletions are determined by [0094] synchronization manager 110, the items are synchronized. In order to do this, synchronization manager 110 forms a list of objects which have been changed on either object store 8 or object store 6 and simply calls upon the respective synchronization interface components to update the outdated object. If the same object has been modified both on mobile device 3 and desktop. computer 4, a conflict arises. Synchronization manager 110 resolves the conflicts by either prompting the user, or referencing profile information entered by the user during a set-up procedure which dictates which device the user wants to take precedence over the other, and in which instances. The process of setting up profile information is described in greater detail in the above-identification patent applications.
  • Where an object has either been created at the [0095] desktop computer 4 or in the mobile device 3, that object needs to be exchanged with the other device. In the instance where mobile device 3 needs to obtain a new object from desk-top computer 4, synchronization manager 110 calls an interface method known as “Set-Up” which specifies a handle for the object to be obtained from object store 8 in desktop computer 4 and transferred to object store 6 in mobile device 3. Once the handle is obtained, the method known as “GetPacket” is called repeatedly to retrieve a data stream which represents the object, and which is formatted by interface component 108. Synchronization manager 110 simply treats the data as a data stream which is retrieved and sent over link 9 to synchronization manager 102, and eventually to object store 6. The appropriate synchronization interface component 100 parses the data stream in order to identify certain property values associated with properties corresponding to the object. Those properties are then stored in the object store 6.
  • Finally, [0096] synchronization manager 110 updates the identifying data segments associated with either synchronized or exchanged objects and stores the updated data segments in reference store 112.
  • It is worth noting that the architecture described herein provides synchronization of objects associated with electronic mail messages, meetings or appointments, and contacts information, as well as other objects maintained by [0097] PIMs 5 and 7. Thus, using the above synchronization protocol, objects associated with these features are synchronized during the synchronization process. Synchronization manager 110 detects any new objects in object store 8 which represent new electronic mail messages, meetings or appointments or contact information and causes those objects to be transferred to object store 6 on mobile device 3 for attention by the user of mobile device 3.
  • Further, if the user composes an electronic mail message or schedules a meeting (and therefore creates a meeting object and an electronic mail meeting request object) or enters contact information on [0098] mobile device 3 using an appropriate application in PIM 5, the objects associated with those items are stored as new objects in object store 6. During synchronization, those new objects are transferred to desktop computer 4 and object store 8.
  • Meeting Request
  • FIG. 6 is an architectural block diagram illustrating one preferred embodiment of a mechanism by which meeting requests are generated. [0099] Mobile device 3 and desktop computer 4 are shown coupled to one another, as shown in FIG. 5. However, FIG. 6 also illustrates that mobile device 3 and desktop computer 4 can be coupled to a wide area network 138 which can include simply another mobile device, another desktop computer, LAN 51 (shown in FIG. 2), WAN 52 (shown in FIG. 2), or any other suitable network.
  • Similar items to those shown in FIG. 5 are similarly numbered. However, in FIG. 6, PIMs [0100] 5 and 7 are shown in greater detail. FIG. 6 illustrates that, in one preferred embodiment, PIM 5 includes an electronic mail application 140, a calendar and scheduling application 142, and an abridged address book 144. Also, while each of the applications may have designated application programming interfaces, only a single API component 146 is shown in FIG. 6, for the sake of simplicity.
  • FIG. 6 further illustrates that [0101] object store 6 preferably interfaces with applications 140, 142 and 144 through its own set of application programming interfaces 148. Thus, applications 140, 142 and 144 maintain object store 6 by calling methods exposed by application programming interfaces 148 associated with object store 6. In addition, communication component 94 and sync component 99 communicate with application programs 140, 142 and 144 by calling methods exposed by application programming interfaces 146.
  • [0102] PIM 7 in desktop computer 4 has also been illustrated as a more detail block diagram. In one preferred embodiment, PIM 7 includes electronic mail application program 150, scheduling and calendaring program 152 and full address book program 154. While each of the application programs 150, 152 and 154 may have an associated set of application programming interfaces, only a single application programming interface component 156 is illustrated in FIG. 6, for the sake of simplicity.
  • FIG. 6 further illustrates that, in one preferred embodiment, [0103] object store 8 is associated with its own set of application programming interfaces 158 (which may also be the same as API 156, preferably MAPI, or which may be separate therefrom). Thus, application programs 150, 152 and 154 call methods exposed by application programming interfaces 158 to maintain, and interact with, object store 8. In addition, communications component 115 calls methods exposed by application programming interfaces 156 to interact with application programs 150, 152 and 154.
  • FIG. 6 shows that [0104] desktop computer 4 preferably includes electronic mail transport 160. Electronic mail transport 160 is preferably a commercially available electronic mail transport, such as a SMTP transport. However, it should be noted that desktop computer 4 can include any suitable transport, or combination of transports.
  • FIG. 7 is a flow diagram illustrating the creation of a meeting request on [0105] mobile device 3. The following description will proceed with reference to FIGS. 6 and 7.
  • In order to create a meeting request from [0106] mobile device 3, the user first enters meeting request information through a suitable user interface. In one preferred embodiment, the user opens the scheduling application program 142 which causes a suitable user interface to be displayed on screen 84. Using stylus 86, and possibly keypad 82 (or any other suitable input mechanism), the user enters appropriate information to request a meeting. Such information will typically include the date and time of the meeting, the requested attendees (which may be entered by using a fully qualified electronic mail address, or by entering a familiar name, or selected from entries in a contacts database which have a non-empty electronic mail address field), the subject matter of the meeting, an indication of whether the meeting is recurring or a single event, possibly the location of the meeting, and so on. Scheduling application 142 creates an object representative of the meeting request.
  • This information is used to create a meeting object and enter that object in the store associated with the calendar on [0107] mobile device 3. As a result of the creation of the meeting object, an electronic mail meeting request object is also created. It should also be noted that subsequent critical modifications to the meeting object will also cause updated electronic mail meeting request objects to be created and transmitted as well.
  • In a preferred embodiment, a selection has already been made which specifies a transport by which any electronic mail meeting request objects are to be sent. Alternatively, the transport to be used can be implicit in the full electronic mail address, itself. For example, it can be specified that any of transports [0108] 132-136 are to be used, when mobile device 3 is to transmit the meeting request itself. In addition, a selection has also preferably already been made to specify certain options which are to be used in the sync protocol discussed above. For example, if an inbox synchronization option is enabled, the electronic mail meeting request objects will be synchronized to the outbox of desktop computer 4. Also, if a calendar synchronization option is enabled, the meeting object will be synchronized to the calendar of desktop computer 4. Desktop computer 4 then preferably transmits the electronic mail meeting request object synchronized to its outbox.
  • The receipt of the meeting request information from the user, and the creation of a meeting object representative of the meeting and an electronic mail meeting request object are indicated by [0109] blocks 162 and 164 in FIG. 7.
  • Next, the critical time stamp is added to the objects (as indicated by block [0110] 165) and scheduling application 142 assigns a global object identification tag to the meeting object created. The global object identification tag is a tag, such as a number, which uniquely identifies the object representative of the meeting request to mobile device 3, to desktop computer 4, and to all other devices which may encounter that object. The global identification tag is carried with the electronic mail meeting request object when it is transmitted, and remains with the object on other devices. This is indicated by block 166.
  • Because the electronic mail meeting request object must be transmitted to another device, [0111] scheduling application 142 calls methods in API 146 which manipulate electronic mail program 140 to retrieve a fully qualified electronic mail address for all of the potential attendees who are to receive the meeting request. In one preferred embodiment, scheduling application 142 obtains the fully qualified address directly from an address book. In another embodiment, mobile device 3 includes abridged address book program 144. In a preferred embodiment, abridged address book program 144 is implemented as a contacts feature provided by Microsoft Outlook 97. The abridged address book contains proper names, familiar names, addresses, telephone numbers, and fully qualified electronic mail addresses for people that the user has chosen to add to the abridged address book. Those people will likely be people who receive a significant number of electronic mail messages from the user of mobile device 3. Therefore, that information likely contains the fully qualified electronic mail addresses for the potential attendees of the meeting request. In addition, if the address is not fully qualified, the synchronization component 97 on desktop 4 attempts to resolve the name on the desktop prior to sending the electronic mail transmission.
  • Thus, either [0112] electronic mail application 140 or scheduling application 142 call methods in API 146 which cause abridged address book program 144 to retrieve the fully qualified electronic mail address for the familiar names entered by the user as potential attendees. This significantly alleviates memory overhead which would otherwise be required, for instance, if the user was required to download a full address book from desktop computer 4 in order to send an electronic mail message or a meeting request. This is indicated by block 168. In another preferred embodiment, the functionality associated with block 168 is performed at block 162, as soon as the user inputs the appropriate information.
  • Also, the transport option has preferably already been chosen which indicates the particular transport by which the electronic mail messages are to be transmitted. Those transports can be any of transports [0113] 132-136 on mobile device 3 or through synchronization with desktop computer 4, using one of its transports. Based on the option which has been chosen, the electronic mail meeting request object is transmitted through the appropriate transport and, once transmitted, is removed from the outbox of mobile device 3.
  • If the electronic mail meeting request object is to be sent directly from one of the transports on [0114] mobile device 3, the appropriate transport formats the meeting request for transmission . In a preferred embodiment, the particular properties which scheduling application program 142 attributes to an electronic mail meeting request object representative of a meeting request are compatible with multiple other PIMs. Therefore, these properties may be a subset or a superset, of all of the properties recognized by the multiple PIMs such that the object can be entertained and appropriately handled by those PIMs. Appendix A, which is attached hereto and forms a part of this document, is a list of message properties by which the Microsoft Schedule+brand scheduling program defines objects associated with meeting requests. These properties notably include revised recurring notification properties which are backward compatible with other versions of Microsoft Schedule+ scheduling software. For instance, in the embodiment described in Appendix A, recurring notifications which are used to define recurring meetings are formatted as a superset of single-instance notifications. In this way, prior versions of the Microsoft Schedule+ scheduling software will be provided with well formed meeting notifications, even for recurring meetings.
  • In the preferred embodiment, [0115] scheduling program 142 then calls methods exposed by API 146 related to electronic mail application program 140. The electronic mail message which contains the electronic mail meeting request object is formulated into one of a predetermined number of classes by electronic mail application 140. The receiving scheduler program of the potential attendee differentiates between the type of meeting notification based on the mail message class. For example, in one preferred embodiment, mail message classifications exist for a meeting cancellation notice from the originator, a meeting request from the originator, a meeting acceptance from the attendee, a meeting declined from the attendee and a meeting tentatively accepted from the attendee. Thus, this is preferably included along with the object when the transport formats the electronic mail meeting request object for transmission. The meeting request is transmitted, through communications component 94 to the designated transport 132, 134 or 136 which, in turn, formats and transmits the message to network 138.
  • The formatting and transmission of the electronic mail meeting request object from a transport on [0116] mobile device 3 is indicated by blocks 172 and 174 in FIG. 7.
  • After the electronic mail meeting request object is sent, it is removed from the outbox of [0117] mobile device 3 to indicate that the message has been sent. This is indicated by block 190. Upon next being coupled to desktop computer 4, the meeting object is synchronized to the store containing the calendar on desktop computer 4. Preferably, the PIMs also provide a feature which can be utilized to prevent the PIM from creating and sending an electronic mail meeting request object simply because the meeting object has been synchronized to the calendar on the desktop. The feature may simply be to only create electronic mail meeting request objects for meeting requests created on the desktop. This feature is implemented to further address the problem of duplicate messaging.
  • If the transport option has been chosen to send the electronic mail meeting request object using the synchronization protocol and a mail transport on [0118] desktop computer 4, processing is substantially the same, except that the electronic mail meeting request object is synchronized to the outbox of desktop computer 4 (as indicated by block 173). Mobile device 3 simply waits until it is coupled to desktop computer 4 before any further action is taken with respect to that meeting request. Upon coupling of mobile device 3 to desktop computer 4, the synchronization protocol described above is executed. During the synchronization process, the meeting object is synchronized to the calendar on the desktop computer 4 and the electronic mail meeting request object is then synchronized to the outbox of desktop computer 4 through synchronization components 97 and 99. Upon receiving the electronic mail meeting request object indicative of the meeting request, electronic mail application program 150 recognizes that the meeting request needs to be transmitted. Electronic mail application program 150 calls the necessary methods exposed by API 158 to have the appropriate object transported, through communications component 115 and transport 160, to network 138. This is again indicated by blocks 172, 173, 174 and 190.
  • It is also worth noting that, in one alternatively preferred embodiment, the meeting request need not be entirely formatted on [0119] mobile device 3. Instead, the data representing the electronic mail meeting request object can simply be stored and transferred during synchronization to desktop computer 4 where it is fully formatted. For instance, in one preferred embodiment, mobile device 3 does not store the particular transport to be used by desktop computer 4 in sending the meeting request. Since this information is not stored by mobile device 3, it is not synchronized with desktop computer 4. Instead, electronic mail application program 150 on desktop computer 4 (prior to sending the meeting request) calls the necessary methods through API 156 to have full address book 154 retrieve the transport associated with each of the potential attendees identified by the user. That information is then used by electronic mail application program 150 in choosing the appropriate transport 160 with which to transmit the electronic mail meeting request object. In this way, additional memory capacity need not be consumed on mobile device 3 to store such transport information. This is indicated by block 188.
  • In any case, once electronic [0120] mail application program 150 causes the electronic mail meeting request object to be transmitted to network 138, it is removed from the outbox. This is indicated by block 190.
  • After the electronic mail meeting request object has been sent it is determined whether any other meeting requests were synchronized with [0121] desktop computer 4 during the last synchronization process. If not, normal processing continues. If so, processing reverts back to block 172 wherein electronic mail application program 150 calls the necessary APIs to send the object. This is indicated by block 192.
  • FIG. 8 is a flow diagram illustrating one preferred embodiment of how [0122] mobile device 3′ handles responses to the meeting requests transmitted in accordance with FIG. 7. In the preferred embodiment, the addressee for responses to meeting requests is the meeting originator. Both senders and recipients of the meeting requests can be arranged properly for delegate handling. The publicly available MAPI specification fully discloses how to interpret such properties.
  • Thus, the recipient of the meeting request is provided with a suitable user interface to indicate a response. The response is addressed to the meeting originator, or another proper delegate. The response is then transferred by the device which the recipient is operating on and is received through one of [0123] transports 132, 134 or 136, or through communications component 94 on mobile device 3. This is indicated by block 194 in FIG. 8.
  • Upon receiving the response, [0124] scheduling application program 142 correlates the response to the meeting object which was formed by scheduling application program 142 when the user created the request, and which is stored in object store 6. This correlation is performed by using the unique global identification number which uniquely identifies that meeting request to all devices which may encounter it. This is indicated by block 196.
  • The critical time stamp information is then checked to determine whether the response corresponds to the latest meeting object. The response preferably actually contains two time stamps. The first is the recipient's opinion of the originator's critical time stamp. The second is a time stamp assigned by the recipient. The first is checked to determined whether it is the same as the originator's time stamp. If so, the response is considered to be in date. If not, the response is rejected or ignored as an out-of-date response. The second must be equal to or greater than any previously recorded time stamp from this particular recipient for the response to be in date. If not, the response is rejected or ignored as out-of-date. This is indicated by [0125] block 197.
  • It should be noted that in the preferred embodiment, the time stamps are always moving forward. Thus, even if the user resets the clock sufficiently into the past, any subsequent time stamp is always the later of a current clock time and the last time stamp plus one second. [0126]
  • [0127] Scheduling application program 142 then calls the necessary methods exposed by API 148 in order to update the attendee status associated with the request. This is updated based on the particular response received from the attendee. This is indicated by block 198.
  • [0128] Mobile device 3 then simply waits to be connected to desktop computer 4. Once it is connected, the updated objects (containing the updated attendee status property) are synchronized to the instance of that object stored in object store 8. This is accomplished utilizing the synchronization protocol discussed above. This is indicated by blocks 200 and 202. The meeting object is then available to scheduling application program 152 and desktop computer 4 to be displayed on the user's calendar at desktop computer 4 for user observation and interaction.
  • FIG. 9 is a flow diagram which illustrates one preferred embodiment of how responses are handled when received through [0129] transport 160 on desktop computer 4. The user first inputs information through an appropriate user interface which defines the user's response to the meeting request. The response is then transmitted back to desktop computer 4 through transport 160 and communications component 115. This is indicated by block 204.
  • [0130] Scheduling application program 152 correlates the response to the meeting object, as did mobile device 3, by utilizing the global identification number assigned to the meeting object, and received along with the response to the meeting request. This is indicated by block 206. The time stamp information is then checked to determine whether the response corresponds to the latest meeting object, again as described above. If not, the response is rejected or ignored as an out-of-date response. This is indicated by block 207. Scheduling application program 152 then calls the necessary methods exposed by API 158 to modify and update the attendee status of the meeting object stored in object store 8. This is indicated by block 208. Desktop computer 4 then simply waits until it is next coupled to mobile device 3.
  • At that point, the updated objects in object store [0131] 8 (which have been updated to accurately reflect the new attendee status based on the response) are synchronized to the other instance of that object then stored in object store 6. Synchronization is accomplished in accordance with the synchronization protocol discussed above. The updated object is then available for review and manipulation by the user of mobile device 3. This is indicated by blocks 210 and 212.
  • The mobile device in accordance with an illustrative embodiment of the present invention also handles exceptions to recurring meetings and meeting cancellations. In one embodiment, the scheduling PIM erases all exceptions when an update to the recurrence pattern of a recurrent meeting is received. Thus, new electronic mail objects must be created and sent for each exception once a charge in the recurrent meeting pattern has been sent. For instance, assuming the user entered a recurring meeting request on [0132] mobile device 3. Scheduling application 142 creates a recurring meeting object and enters it on the calendar of the user. Electronic mail application 140 also creates an electronic mail recurring meeting request object for transmission to potential attendees. The recipients (potential attendees) can respond generally as described above.
  • For the sake of the present example, assume the recurring meeting is to occur every Tuesday from 10:00-11:00 a.m. beginning on April 1. However, the user (originator) then needs to cancel the April [0133] 8 th meeting. The user enters scheduling application 142 and deletes the desired instance. Electronic mail application 140, in turn, creates another object for transmission which indicates this cancellation (which is an exception to the recurrence pattern). The originator then needs to move the April 15th meeting to 11:00-12:00 noon. A similar process is executed to create this exception as well. Suppose then that the originator wishes to make a change to the location of the recurring meetings and apply the change to the entire recurrence pattern. This requires three new pieces of electronic mail to be transmitted.
  • The first is simply created to indicate the new location which modifies the recurrence pattern. This may also, in some PIMs, erase the previous two exceptions. Thus, two new pieces of electronic mail are created to reinstitute the two exceptions (i.e., the cancellation of the April 8[0134] th meeting and the time change for the April 15th meeting). These pieces of electronic mail are automatically created by electronic mail application 140. These same actions are taken in response to other suitable modifications as well, such as modification of the list of attendees.
  • Localization
  • As previously discussed, in the preferred embodiment, a meeting object is typically accompanied by a textual phrase which describes the nature of the meeting request. The textual phrase is generated based upon the property values input by the user during creation of the meeting request. For example, a user may request the potential attendees to attend a meeting on the third Monday of each month at 10:00 a.m., and for a period which extends from Jan. 1, 2000, to Mar. 20, 2001. In that case, a typical text message which might be retrieved and placed in the meeting request object to accompany that object for display to the potential attendees might read as follows: [0135]
  • “This meeting shall take place on the third Monday of each month at 10:00 a.m. beginning Jan. 1, 2000, and ending Mar. 20, 2001.”However, in a different locality, convention may dictate that the day be placed before the month when reciting dates. Further, words or phrases in the text message, and the order of the components of the text message, may need to be rearranged in order to more closely conform to local convention. [0136]
  • In the preferred embodiment, a predetermined text message of the type set out above is generated to describe each different type of recurring meeting which can be requested by the user of [0137] mobile device 3.
  • In accordance with one aspect of the present invention, the text messages used to describe requests for recurring meetings are broken down into a plurality of phrases. Each of the phrases which has been created is broken down into a plurality of fields. The particular phrases which can be created to define a meeting request, and the particular fields into which those phrases are separated can be any suitable phrases and fields. [0138]
  • For the phrase mentioned above, FIG. 11A illustrates one embodiment of the fields into which that phrase can be broken. FIG. 11A shows that a first portion of the phrase “This meeting shall take place on the third Monday of each month” is placed in [0139] field 214. The term “at” is placed in field 216. The time designation “10:00” is placed in field 218 and the AM/PM designator is placed in field 220. The term “beginning” is placed in field 222, and the remaining message is similarly broken up into fields 224, 226, 228, 230, 234, 236, 238, 240 and 242.
  • FIG. 10 is a flow diagram illustrating how the localization process works. The creation of the textual phrases defining meeting requests, and the breaking up of those requests into various predetermined fields, is indicated by [0140] block 242. Next, during manufacture of mobile device 3, a Vocalizer program is run on mobile device 3 to rearrange fields 214-240, for each of the messages created, such that the messages conform to local convention. Of course, the specific localizer program which is run on mobile device 3 will depend on the particular locality and consumer base for which mobile device 3 is intended. Once the localizer program has been run, mobile device 3 contains a plurality of sets of fields, referred to as templates, into which message data is placed in order to display the textual message in a localized fashion. Running of the localizer program in setting up the templates is indicated by block 244.
  • After [0141] mobile device 3 has templates which have been localized, mobile device 3 is ready to receive a meeting request and properly display the textual description of the meeting request. When a meeting request is received, the data stream indicative of the textual phrase which describes the meeting is also received by scheduling application program 142. This is indicated by block 246. Scheduling application program 142 parses the incoming data stream into values associated with the various fields in the appropriate template (the appropriate template corresponds to the specific textual description being received) This is indicated by block 248.
  • Next, the parsed data is placed into preselected fields in the templates based on the created phrases. This is indicated by [0142] block 250. Because the localizer program has already been run, the fields in the templates are already placed in appropriate order to conform to local convention.
  • FIG. 11B illustrates the rearrangement of the fields in the template illustrated in FIG. 11A to conform to a different convention. FIG. 11B illustrates the conformation of the phrase to a convention in which the phrasing is slightly different from that shown in FIG. 11A, and in which the day is conventionally placed prior to the month in a date. The phrase now contains the same terms, but reads: [0143]
  • “Beginning Jan., 1, 2000 and ending Mar., 20 2001 this meeting shall take place on the third Monday of each month at 10:00 AM.”[0144]
  • All appropriate phrases will, of course, be similarly localized. [0145]
  • Also, in an illustrative embodiment, time zone information is handled in an advantageous manner. For instance, when a recurring meeting request is created and sent to a device located in a different time zone, the textual phrase indicative of the recurring meeting includes an indication of the time zone in which the recurring meeting request was created. For instance, if a user in Paris sends a recurring meeting request to a recipient in Seattle (nine hours different) for a meeting occurring every Tuesday at 8:00 a.m. beginning March 3, the textual phrase may be: [0146]
  • “This meeting occurs every Tuesday at 8:00 a.m. beginning March 3; (GMT+1) Paris, Madrid.”[0147]
  • This allows the recipient to view the recurrence pattern as originally composed by the sender. [0148]
  • On the other hand, if the meeting is nonrecurrent, the time is preferably simply displayed as the appropriate time for the recipient (e.g., “This meeting is scheduled for Tuesday at 11:00 p.m.”). [0149]
  • Conclusion
  • Therefore, it can be seen that the present invention provides significant advantages over prior systems. First, the present invention allows the creation of a meeting request from a mobile device itself. The present invention further identifies the object associated with such a meeting request in a manner which uniquely identifies the object to all other devices likely to encounter the object. The present invention also utilizes a feature in the PIMs which indicates whether the meeting request has been sent to potential attendees. These features eliminate duplicate messaging. [0150]
  • The present invention also preferably implements features which reduce the memory required to implement the meeting request feature by use of an abridged address book. Further, the present invention preferably uses a set of scheduling properties which are compatible with a plurality of different PIMs likely to encounter the meeting request. In addition, the present invention preferably utilizes localization procedures which localize meeting requests to more closely conform to local convention and handle time zone information in an advantageous manner. The present invention also preferably supports the use of multiple electronic mail transports as well as a synchronization protocol. [0151]
  • Although the present invention has been described with reference to preferred embodiments, workers skilled in the art will recognize that changes may be made in form and detail without departing from the spirit and scope of the invention. [0152]

Claims (26)

What is claimed is:
1. A mobile device, comprising:
an object store;
an application program configured to maintain objects on the object store;
a user input mechanism configured to receive user input information;
a synchronization component configured to synchronize individual objects stored on the object store with remote objects stored on a remote object store;
a communications component configured to communicate with a remote device containing the remote object store; and
wherein the application program is further configured to generate a meeting object and an electronic mail meeting request object based on the user input information.
2. The mobile device of
claim 1
wherein the application program is configured to generate the meeting object with a global identifier property uniquely identifying the meeting object among a plurality of other objects.
3. The mobile device of
claim 2
wherein the application program is configured to generate the meeting object with a time stamp indicative of a relative time when the meeting object was created and wherein the application program generates the electronic mail meeting request object with the time stamp.
4. The mobile device of
claim 3
wherein the application program comprises:
a first application program configured to generate the meeting object based on the user input information; and
a second application program configured to generate the electronic mail meeting request object.
5. The mobile device of
claim 1
wherein the application program further comprises:
a contacts application program configured to maintain objects on the object store indicative of contact information wherein the contact information includes address information indicative of a fully qualified electronic mail addresses for individuals identified by the contact information; and
wherein the application program is configured to obtain the fully qualified electronic mail address of potential attendees identified by the contact information by interaction with the contacts application program.
6. The mobile device of
claim 1
wherein the application program is configured to generate the meeting object and the electronic mail meeting request object such that properties of the objects are compatible with at least a second application program associated with the remote object store and different from the application program.
7. The mobile device of
claim 1
wherein the application program is configured to receive a data stream indicative of a textual phrase describing the meeting object, to parse the data stream into sections and place the sections in corresponding fields of a preselected template containing the fields, the preselected template being associated with the textual phrase received.
8. The mobile device of
claim 7
wherein the preselected template is created by arranging the fields in an order, the order being based on a specific locality.
9. A method of operating a mobile device, comprising:
providing a first object store on the mobile device;
providing a first application program on the mobile device;
maintaining objects in the first object store with the first application program;
intermittently synchronizing the objects in the first object store with objects in a remote object store;
receiving user input information indicative of a meeting request;
generating a meeting object with the first application program such that at least some of the user input information defines properties in the meeting object;
generating an electronic mail meeting request object based on the information in the meeting object; and
storing the meeting object and the electronic mail meeting request object in the first object store for transmission.
10. The method of
claim 9
wherein synchronizing comprises:
coupling the mobile device to a computing device having the remote object store;
synchronizing objects in the first data store with objects in the remote data store; and
transmitting the electronic mail meeting request from an electronic mail transport on the computing device.
11. The method of
claim 9
and further comprising:
providing an electronic mail transport on the mobile device; and
transmitting the electronic mail meeting request object through an electronic mail transport on the mobile device.
12. The method of
claim 11
wherein providing an electronic mail transport on the mobile device comprises:
providing a plurality of electronic mail transports on the mobile device; and
selecting one of the plurality of electronic mail transports through which the electronic mail meeting request objects are to be transmitted.
13. The method of
claim 9
wherein generating a meeting object comprises:
assigning the meeting object a global identifier which uniquely identifies the meeting request relative to other objects.
14. The method of
claim 13
wherein generating a meeting object further comprises:
assigning the meeting object a time stamp indication indicating a time when the meeting object was created; and
wherein generating the electronic mail meeting request object includes assigning the electronic mail meeting request object the time stamp indication.
15. The method of
claim 14
and further comprising:
receiving response objects;
correlating the response objects with the meeting object on the mobile device based on the global identifier and the time stamp indication; and
updating a response status associated with the meeting object based on the response objects received.
16. The method of
claim 15
and further comprising: synchronizing the response status with the remote object store.
17. A data transmission system, comprising:
a first computing device including:
a first data store configured to store objects; a user input mechanism; and
a first application program configured to receive user input information from the user input mechanism, create a first object based on the user input information and store the first object on the first data store;
a synchronization manager configured to synchronize objects in the first data store with objects in a second data store;
a second computing device including:
the second data store, the second data store being configured to store objects; and
a second application program configured to access the second data store and create an electronic mail object based on the first object being synchronized to the second data store from the first data store;
an electronic mail transport; and
wherein the second application program is configured to transmit the electronic mail objects with the electronic mail transport.
18. The system of
claim 17
and further comprising: a third computing device including:
a third data store configured to store objects; and
a third application program configured to access the third data store, to receive electronic mail objects from the second computing device and to store the electronic mail objects on the third data store.
19. The system of
claim 18
and further comprising:
a fourth computing device including: a fourth data store; and
a fourth application program configured to access the fourth data store and store objects on the fourth data store; and
wherein the synchronization manager is configured to synchronize objects in the third and fourth data stores.
20. The system of
claim 19
wherein the synchronization manager comprises:
a first synchronization manager on at least one of the first and second computing devices; and
a second synchronization manager on at least one of the third and fourth computing devices.
21. The system of
claim 17
wherein the first object comprises a meeting object and wherein the electronic mail object comprises an electronic mail meeting request object.
22. The system of
claim 17
wherein the first computing device comprises a mobile device.
23. The system of
claim 22
wherein the first application program comprises a scheduling program and wherein the second application program comprises an electronic mail application program.
24. A mobile device, comprising: an object store;
a user input mechanism configured to receive user input values;
a plurality of electronic mail transports; and
a first application program configured to create an object based on the user input values and to transmit the object using a preselected one of the electronic mail transports.
25. The mobile device of
claim 24
and further comprising:
a synchronization component configured to provide a remote computing device with access to the object store for synchronization of objects on the remote computing device with objects on the object store.
26. The mobile device of
claim 24
and further comprising:
a housing sized to hold the object store, the application program and the plurality of electronic mail transports and to fit in the hand.
US09/058,679 1997-10-24 1998-04-10 Generating meeting requests and group scheduling from a mobile device Expired - Lifetime US6370566B2 (en)

Priority Applications (5)

Application Number Priority Date Filing Date Title
US09/058,679 US6370566B2 (en) 1998-04-10 1998-04-10 Generating meeting requests and group scheduling from a mobile device
EP98953902A EP1025526A1 (en) 1997-10-24 1998-10-23 Generating meeting requests and group scheduling from a mobile device
JP2000518349A JP4575591B2 (en) 1997-10-24 1998-10-23 Meeting requests and group scheduling generation from mobile devices
CA002306264A CA2306264C (en) 1997-10-24 1998-10-23 Generating meeting requests and group scheduling from a mobile device
PCT/US1998/022413 WO1999022324A1 (en) 1997-10-24 1998-10-23 Generating meeting requests and group scheduling from a mobile device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US09/058,679 US6370566B2 (en) 1998-04-10 1998-04-10 Generating meeting requests and group scheduling from a mobile device

Publications (2)

Publication Number Publication Date
US20010054072A1 true US20010054072A1 (en) 2001-12-20
US6370566B2 US6370566B2 (en) 2002-04-09

Family

ID=22018248

Family Applications (1)

Application Number Title Priority Date Filing Date
US09/058,679 Expired - Lifetime US6370566B2 (en) 1997-10-24 1998-04-10 Generating meeting requests and group scheduling from a mobile device

Country Status (1)

Country Link
US (1) US6370566B2 (en)

Cited By (58)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6438585B2 (en) 1998-05-29 2002-08-20 Research In Motion Limited System and method for redirecting message attachments between a host system and a mobile data communication device
US6463464B1 (en) * 1998-05-29 2002-10-08 Research In Motion Limited System and method for pushing information from a host system to a mobile data communication device
US6463463B1 (en) 1998-05-29 2002-10-08 Research In Motion Limited System and method for pushing calendar event messages from a host system to a mobile data communication device
US6592038B2 (en) 2001-04-09 2003-07-15 Ncr Corporation Item processing system and method which track label usage
US20030220826A1 (en) * 2002-05-23 2003-11-27 Steve Mansour Time request queue
US20040199611A1 (en) * 2002-11-25 2004-10-07 Sven Bernhard Method and system for remote configuration of network devices
US20040196866A1 (en) * 2002-09-16 2004-10-07 Samsung Electronics Co., Ltd. Method for transmitting and recording schedule using short message service
US20050091264A1 (en) * 2003-10-23 2005-04-28 Microsoft Corporation Identity system for use in a computing environment
US20050108359A1 (en) * 2003-11-05 2005-05-19 Robert Hyder Remote mail management system
US20050143097A1 (en) * 2002-06-14 2005-06-30 Cingular Wireless Ii, Llc System for providing location-based services in a wireless network, such as providing notification regarding meetings, destination arrivals, and the like
FR2873220A1 (en) * 2004-07-16 2006-01-20 Imed Oueslati Online diary management device for use in e.g. enterprise, has module displaying user diaries` data and functions input and conversion in standard and multilingual formats and module securing user data
US20060031470A1 (en) * 2004-06-30 2006-02-09 International Business Machines Corporation Method to update status on multiple voice and text systems from a single device
US20060095859A1 (en) * 2004-11-03 2006-05-04 Bocking Andrew D Handheld electronic device including appointment and meeting conflict notification, and associated method
EP1655693A1 (en) * 2004-11-03 2006-05-10 Research In Motion Limited Handheld electronic device including appointment and meeting conflict notification, and associated method
US20060123088A1 (en) * 2004-12-02 2006-06-08 Microsoft Corporation System and method for replicating offline scheduling transactions from a client to a server
US20060142997A1 (en) * 2002-12-27 2006-06-29 Per Jakobsen Predictive text entry and data compression method for a mobile communication terminal
US20070094301A1 (en) * 2003-10-23 2007-04-26 Microsoft Corporation Application programming interface for centralized storage of principal data
US20070136119A1 (en) * 2005-12-08 2007-06-14 Record Andrew D Recurrence definition identification
US20070250366A1 (en) * 2006-04-21 2007-10-25 Nokia Corporation Apparatus, method and computer program product for annotating a meeting in an electronic calendar
US20070265903A1 (en) * 2006-05-10 2007-11-15 Colin Blair Meeting notification and merging agents
US7440961B1 (en) * 2004-02-18 2008-10-21 Microsoft Corporation System and method for filtering recurrence events
US20090164595A1 (en) * 1999-10-13 2009-06-25 Lot 38 Acquisition Foundation, Llc Method and system for creating and sending handwritten or handdrawn messages via mobile devices
US20090286513A1 (en) * 2002-06-14 2009-11-19 At&T Mobility Ii Llc Apparatus And Systems For Providing Location-Based Services Within A Wireless Network
US20100030788A1 (en) * 2008-08-01 2010-02-04 Chin-Ju Rex Chen Automatic temporary address book
US7693736B1 (en) 2006-10-30 2010-04-06 Avaya Inc. Recurring meeting schedule wizard
US7778858B1 (en) * 2006-07-17 2010-08-17 Avaya Inc. Linking unable to respond messages to entries in electronic calendar
US20100217644A1 (en) * 2006-10-11 2010-08-26 International Business Machines Corporation Electronic Calendar Auto Event Resolution System and Method
US7827240B1 (en) 2007-01-02 2010-11-02 Avaya Inc. Calendar item hierarchy for automatic specialization
US7899782B1 (en) * 2008-02-21 2011-03-01 SmartLine Inc. Security system for synchronization of desktop and mobile device data
US7953802B2 (en) 1998-05-29 2011-05-31 Research In Motion Limited System and method for pushing information from a host system to a mobile data communication device
US7984378B1 (en) 2006-02-07 2011-07-19 Avaya Inc. Management of meetings by grouping
US8037143B1 (en) 2006-10-30 2011-10-11 Avaya Inc. Automatic display of email distribution lists
US8050684B2 (en) 2000-12-22 2011-11-01 Research In Motion Limited Wireless router system and method
US8060564B2 (en) 1998-05-29 2011-11-15 Research In Motion Limited System and method for pushing information from a host system to a mobile data communication device
US8134954B2 (en) 2001-10-26 2012-03-13 Research In Motion Limited System and method for controlling configuration settings for mobile communication devices and services
US8180900B2 (en) 2001-12-07 2012-05-15 Research In Motion Limited System and method of managing information distribution to mobile stations
US8200520B2 (en) 2007-10-03 2012-06-12 International Business Machines Corporation Methods, systems, and apparatuses for automated confirmations of meetings
US8230026B2 (en) 2002-06-26 2012-07-24 Research In Motion Limited System and method for pushing information between a host system and a mobile data communication device
US8365240B2 (en) 2005-04-18 2013-01-29 Research In Motion Limited Method for providing wireless application privilege management
US8489442B1 (en) 2004-02-02 2013-07-16 Avaya Inc. Interface for meeting facilitation and coordination, method and apparatus
US8498289B2 (en) 2001-01-18 2013-07-30 Research In Motion Limited System, method and mobile device for remote control of a voice mail system
US8516055B2 (en) 1998-05-29 2013-08-20 Research In Motion Limited System and method for pushing information from a host system to a mobile data communication device in a wireless data network
US20140200944A1 (en) * 2011-11-08 2014-07-17 Matchware A/S Automation of meeting scheduling and task list access permissions within a meeting series
US9037660B2 (en) 2003-05-09 2015-05-19 Google Inc. Managing electronic messages
US9152475B1 (en) * 2005-09-29 2015-10-06 Hewlett-Packard Development Company, L.P. Notifying listeners of change events
US9258372B2 (en) 2007-05-09 2016-02-09 Blackberry Limited Wireless router system and method
US9274687B1 (en) 2013-10-11 2016-03-01 Google Inc. Managing schedule changes for correlated calendar events
US9374435B2 (en) 1998-05-29 2016-06-21 Blackberry Limited System and method for using trigger events and a redirector flag to redirect messages
US9531651B1 (en) 2014-02-13 2016-12-27 Google Inc. Methods for displaying notifications
US9576271B2 (en) 2003-06-24 2017-02-21 Google Inc. System and method for community centric resource sharing based on a publishing subscription model
US10445703B1 (en) 2006-10-30 2019-10-15 Avaya Inc. Early enough reminders
US10636014B2 (en) * 2016-09-26 2020-04-28 Microsoft Technology Licensing, Llc Conversational calendar integration
US11677875B2 (en) 2021-07-02 2023-06-13 Talkdesk Inc. Method and apparatus for automated quality management of communication records
US11706339B2 (en) * 2019-07-05 2023-07-18 Talkdesk, Inc. System and method for communication analysis for use with agent assist within a cloud-based contact center
US11736616B1 (en) 2022-05-27 2023-08-22 Talkdesk, Inc. Method and apparatus for automatically taking action based on the content of call center communications
US11736615B2 (en) 2020-01-16 2023-08-22 Talkdesk, Inc. Method, apparatus, and computer-readable medium for managing concurrent communications in a networked call center
US11783246B2 (en) 2019-10-16 2023-10-10 Talkdesk, Inc. Systems and methods for workforce management system deployment
US11856140B2 (en) 2022-03-07 2023-12-26 Talkdesk, Inc. Predictive communications system

Families Citing this family (182)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1997022936A1 (en) * 1995-12-19 1997-06-26 Motorola Inc. Method and apparatus for rate governing communications
JPH11313105A (en) * 1998-04-24 1999-11-09 Canon Inc Server, client, server control method, client control method, client-server system and storage medium
US7209955B1 (en) * 1998-05-29 2007-04-24 Research In Motion Limited Notification system and method for a mobile data communication device
US20020049818A1 (en) * 1998-05-29 2002-04-25 Gilhuly Barry J. System and method for pushing encrypted information between a host system and a mobile data communication device
US7266365B2 (en) * 1998-05-29 2007-09-04 Research In Motion Limited System and method for delayed transmission of bundled command messages
US6735701B1 (en) * 1998-06-25 2004-05-11 Macarthur Investments, Llc Network policy management and effectiveness system
US6810405B1 (en) * 1998-08-18 2004-10-26 Starfish Software, Inc. System and methods for synchronizing data between multiple datasets
JP2000090151A (en) * 1998-09-10 2000-03-31 Ibm Japan Ltd Schedule display and change method, schedule management device and storage medium storing schedule management program
US6862617B1 (en) 1998-10-12 2005-03-01 Microsoft Corp. System and method for synchronizing objects between two devices
AU6410699A (en) 1998-10-13 2000-05-01 Chris Cheah Method and system for controlled distribution of information over a network
US7689563B1 (en) * 1998-10-20 2010-03-30 Jacobson Andrea M Electronic record management system
US6963900B2 (en) * 2000-02-29 2005-11-08 John Edward Boyd Computer-based networking service and method and system for performing the same
US6707942B1 (en) * 2000-03-01 2004-03-16 Palm Source, Inc. Method and apparatus for using pressure information for improved computer controlled handwriting recognition, data entry and user authentication
WO2001075692A2 (en) * 2000-03-31 2001-10-11 Mdsi Mobile Data Solutions Inc. Assigning technique for a scheduling system
EP1273135B1 (en) * 2000-04-10 2010-07-14 Research In Motion Limited System and method for bundling information
US7571254B1 (en) * 2000-05-15 2009-08-04 Access Systems Americas, Inc. Mutual scheduling of events on handheld computers
US6785868B1 (en) * 2000-05-31 2004-08-31 Palm Source, Inc. Method and apparatus for managing calendar information from a shared database and managing calendar information from multiple users
US7174303B2 (en) * 2000-07-31 2007-02-06 Uappoint, Inc Customer driven, sponsor controlled network-based graphical scheduling system and method
JP3750504B2 (en) * 2000-08-09 2006-03-01 セイコーエプソン株式会社 Data update method and information processing apparatus
US6879996B1 (en) * 2000-09-13 2005-04-12 Edward W. Laves Method and apparatus for displaying personal digital assistant synchronization data using primary and subordinate data fields
US20020046248A1 (en) * 2000-10-13 2002-04-18 Honeywell International Inc. Email to database import utility
US7076275B1 (en) * 2000-10-13 2006-07-11 Palmsource, Inc. Method and system for single-step enablement of telephony functionality for a portable computer system
US20020065881A1 (en) * 2000-11-29 2002-05-30 Tapio Mansikkaniemi Wireless family bulletin board
US6937853B2 (en) * 2000-12-21 2005-08-30 William David Hall Motion dispatch system
US7017105B2 (en) * 2001-02-02 2006-03-21 Microsoft Corporation Deleting objects from a store of a device
US7191449B2 (en) * 2001-02-16 2007-03-13 Microsoft Corporation System and method for providing componentized transports and forms
US7013350B2 (en) * 2001-02-16 2006-03-14 Microsoft Corporation System setting flags based on address types in destination address field of a message to indicate different transports to deliver the message
US20030004773A1 (en) * 2001-03-15 2003-01-02 Objectsoft, Inc. Scheduling system with methods for polling to determine best date and time
US20020138326A1 (en) * 2001-03-22 2002-09-26 Leo Parker System and method for group scheduling using a wireless device
US20060095357A1 (en) * 2001-04-05 2006-05-04 Remote Sales LLC, a limited liability corporation of the State of Nevada Wireless payment processing
US7386589B1 (en) 2001-04-05 2008-06-10 Remote Sales, Llc Managed messaging platform with message response aggregation
US7533187B1 (en) * 2001-04-05 2009-05-12 Marcellino Tanumihardja Wireless device detection
US20020158903A1 (en) * 2001-04-26 2002-10-31 International Business Machines Corporation Apparatus for outputting textual renditions of graphical data and method therefor
GB2375017A (en) * 2001-04-28 2002-10-30 Hewlett Packard Co Mobile computing device having diary and data transfer functions
US7231423B1 (en) * 2001-05-23 2007-06-12 Jens Horstmann Interactive wireless device communication system for meetings and conferences
US20030225842A1 (en) * 2001-05-29 2003-12-04 Kenneth Li Distribution of messages using an address book of a user
US7272232B1 (en) * 2001-05-30 2007-09-18 Palmsource, Inc. System and method for prioritizing and balancing simultaneous audio outputs in a handheld device
US20030046670A1 (en) * 2001-06-15 2003-03-06 Marlow Mark J. Binary object system for automated data translation
US7340691B2 (en) * 2001-06-25 2008-03-04 International Business Machines Corporation Method, system, and program for accessing calendar information for shadowed users from a database
US6961740B2 (en) 2001-08-01 2005-11-01 Valaran Corporation Method and system for multimode garbage collection
US7454459B1 (en) * 2001-09-04 2008-11-18 Jarna, Inc. Method and apparatus for implementing a real-time event management platform
US8346718B2 (en) * 2001-09-07 2013-01-01 Extended Systems, Inc. Synchronizing recurring events
US7213039B2 (en) * 2001-09-07 2007-05-01 Extended System, Inc. Synchronizing differing data formats
US7080123B2 (en) * 2001-09-20 2006-07-18 Sun Microsystems, Inc. System and method for preventing unnecessary message duplication in electronic mail
US20030069899A1 (en) * 2001-10-04 2003-04-10 International Business Machines Corporation Method, system, and program for providing personal preference information when scheduling events
JPWO2003048945A1 (en) * 2001-12-05 2005-04-21 株式会社サイバード Communication information sharing system, communication information sharing method, communication information sharing program
US7305700B2 (en) 2002-01-08 2007-12-04 Seven Networks, Inc. Secure transport for mobile communication network
US7248872B2 (en) * 2002-01-08 2007-07-24 International Business Machines Corporation Method, system, and program for providing information on users of wireless devices in a database to a personal information manager
US20030135643A1 (en) * 2002-01-11 2003-07-17 Chaucer Chiu Data transmission scheduling system and method
US8427303B1 (en) 2002-06-27 2013-04-23 Geomass Limited Liability Company System and method for providing media content having attributes matching a user's stated preference
WO2004003705A2 (en) 2002-06-27 2004-01-08 Small World Productions, Inc. System and method for locating and notifying a user of a person, place or thing having attributes matching the user's stated prefernces
US8102253B1 (en) 2002-06-27 2012-01-24 Earthcomber, Llc System and method for notifying a user of people, places or things having attributes matching a user's stated preference
US20040078436A1 (en) * 2002-10-18 2004-04-22 International Business Machines Corporation Adding meeting information to a meeting notice
EP1422901A1 (en) * 2002-11-22 2004-05-26 Sun Microsystems, Inc. Client driven synchronization of file and folder content in web publishing
US20040128304A1 (en) * 2002-12-30 2004-07-01 International Business Machines Corporation Selective exposure of free time in group scheduling systems
US7917468B2 (en) 2005-08-01 2011-03-29 Seven Networks, Inc. Linking of personal information management data
US7853563B2 (en) * 2005-08-01 2010-12-14 Seven Networks, Inc. Universal data aggregation
US8468126B2 (en) 2005-08-01 2013-06-18 Seven Networks, Inc. Publishing data in an information community
US7337448B1 (en) * 2003-06-25 2008-02-26 Microsoft Corporation Address book clearinghouse interface system and method
US7197635B2 (en) * 2003-09-04 2007-03-27 International Business Machines Corporation Method and apparatus for providing updated time at a data processing system
WO2005036365A2 (en) * 2003-10-10 2005-04-21 Accenture Global Services Gmbh Tool for synchronization of business information
US7844639B2 (en) * 2003-11-24 2010-11-30 Ebay Inc. Backward compatibility in database schemas
US7818759B2 (en) 2003-11-24 2010-10-19 Ebay Inc. API and business language schema design framework for message exchanges
US20050273493A1 (en) * 2004-06-04 2005-12-08 John Buford Proximity reminder system using instant messaging and presence
US8495045B2 (en) * 2004-07-16 2013-07-23 Sap Ag Method and apparatus for creating an activity record in a business management system from an email message
US8850330B2 (en) * 2004-07-26 2014-09-30 International Business Machines Corporation Editing repeating calendar events
US7606687B2 (en) 2004-09-14 2009-10-20 Friendster, Inc. Proximity search methods using tiles to represent geographical zones
US20070100834A1 (en) * 2004-09-15 2007-05-03 John Landry System and method for managing data in a distributed computer system
US8117073B1 (en) * 2004-09-17 2012-02-14 Rearden Commerce, Inc. Method and system for delegation of travel arrangements by a temporary agent
US20060101447A1 (en) * 2004-10-05 2006-05-11 Robert Koch Methods, systems, and computer program products for performing per-event device synchronization
US7925540B1 (en) 2004-10-15 2011-04-12 Rearden Commerce, Inc. Method and system for an automated trip planner
WO2006045102A2 (en) 2004-10-20 2006-04-27 Seven Networks, Inc. Method and apparatus for intercepting events in a communication system
US8010082B2 (en) 2004-10-20 2011-08-30 Seven Networks, Inc. Flexible billing architecture
US7706781B2 (en) 2004-11-22 2010-04-27 Seven Networks International Oy Data security in a mobile e-mail service
FI117152B (en) 2004-12-03 2006-06-30 Seven Networks Internat Oy E-mail service provisioning method for mobile terminal, involves using domain part and further parameters to generate new parameter set in list of setting parameter sets, if provisioning of e-mail service is successful
US7856483B2 (en) 2004-12-10 2010-12-21 Microsoft Corporation Information management systems with time zone information, including event scheduling processes
US7970666B1 (en) 2004-12-30 2011-06-28 Rearden Commerce, Inc. Aggregate collection of travel data
US20060178925A1 (en) * 2005-02-04 2006-08-10 Banner & Witcoff, Ltd. System for docketing litigation events
US20080147450A1 (en) * 2006-10-16 2008-06-19 William Charles Mortimore System and method for contextualized, interactive maps for finding and booking services
US8060539B2 (en) * 2005-02-24 2011-11-15 Research In Motion Limited Method of notifying an invitee to an event of changes to the event in an electronic calendar system
US7752633B1 (en) 2005-03-14 2010-07-06 Seven Networks, Inc. Cross-platform event engine
US7925525B2 (en) * 2005-03-25 2011-04-12 Microsoft Corporation Smart reminders
US20060223547A1 (en) * 2005-03-31 2006-10-05 Microsoft Corporation Environment sensitive notifications for mobile devices
US8130193B2 (en) * 2005-03-31 2012-03-06 Microsoft Corporation System and method for eyes-free interaction with a computing device through environmental awareness
US7353034B2 (en) 2005-04-04 2008-04-01 X One, Inc. Location sharing and tracking using mobile phones or other wireless devices
US8438633B1 (en) 2005-04-21 2013-05-07 Seven Networks, Inc. Flexible real-time inbox access
US7796742B1 (en) 2005-04-21 2010-09-14 Seven Networks, Inc. Systems and methods for simplified provisioning
US8626556B2 (en) * 2005-04-25 2014-01-07 International Business Machines Corporation Visualizing multiple time zones in a calendaring and scheduling application
WO2006119228A2 (en) * 2005-04-29 2006-11-09 Lehman Brothers Inc. Contact management system and method
US8751279B2 (en) * 2005-05-23 2014-06-10 Blackberry Limited System and method for preventing the lapse of a recurring event using electronic calendar system
WO2006136660A1 (en) 2005-06-21 2006-12-28 Seven Networks International Oy Maintaining an ip connection in a mobile network
US8069166B2 (en) * 2005-08-01 2011-11-29 Seven Networks, Inc. Managing user-to-user contact with inferred presence information
CA2623150A1 (en) * 2005-09-26 2007-03-29 Research In Motion Limited Communications event scheduler
TW200717264A (en) * 2005-10-18 2007-05-01 Inst Information Industry Method/system managing schedules according to Internet information and storage medium saving the program executing this method
US7283927B2 (en) 2005-12-07 2007-10-16 Katrina Delargy Activity recording module
US20070150349A1 (en) * 2005-12-28 2007-06-28 Rearden Commerce, Inc. Method and system for culling star performers, trendsetters and connectors from a pool of users
US9117223B1 (en) 2005-12-28 2015-08-25 Deem, Inc. Method and system for resource planning for service provider
US7769395B2 (en) 2006-06-20 2010-08-03 Seven Networks, Inc. Location-based operations and messaging
US8315905B1 (en) 2006-03-30 2012-11-20 Navadi, Inc. Location based advertising systems
US8260924B2 (en) * 2006-05-03 2012-09-04 Bluetie, Inc. User load balancing systems and methods thereof
WO2007131331A1 (en) * 2006-05-16 2007-11-22 Research In Motion Limited System and method for integrated presentation of information
US8056082B2 (en) * 2006-05-31 2011-11-08 Bluetie, Inc. Capacity management and predictive planning systems based on trended rate change of monitored factors and methods thereof
US20080004917A1 (en) * 2006-06-30 2008-01-03 Rearden Commerce, Inc. System and method for automatically rebooking reservations
US7941374B2 (en) 2006-06-30 2011-05-10 Rearden Commerce, Inc. System and method for changing a personal profile or context during a transaction
US20080097815A1 (en) * 2006-10-23 2008-04-24 Bluetie, Inc. Methods for employing temporary time zones and predictive locations and systems thereof
US20080162614A1 (en) * 2006-12-28 2008-07-03 Nokia Corporation Apparatus, method and computer program product providing calendar application with automatic decision making for received invitation based on parameter sets
US7711717B2 (en) * 2007-03-20 2010-05-04 Microsoft Corporation Achieving recurring item recordings from calendaring applications over LOB systems
EP1972994A1 (en) * 2007-03-20 2008-09-24 Seiko Epson Corporation Projector
US8805425B2 (en) 2007-06-01 2014-08-12 Seven Networks, Inc. Integrated messaging
US8693494B2 (en) 2007-06-01 2014-04-08 Seven Networks, Inc. Polling
US20090006143A1 (en) * 2007-06-26 2009-01-01 Rearden Commerce, Inc. System and Method for Interactive Natural Language Rebooking or Rescheduling of Calendar Activities
US8607250B2 (en) 2007-09-14 2013-12-10 International Business Machines Corporation Visually indicating a calendar event among different time zones
US8364181B2 (en) 2007-12-10 2013-01-29 Seven Networks, Inc. Electronic-mail filtering for mobile devices
US9002828B2 (en) 2007-12-13 2015-04-07 Seven Networks, Inc. Predictive content delivery
US8793305B2 (en) 2007-12-13 2014-07-29 Seven Networks, Inc. Content delivery to a mobile device from a content service
US8107921B2 (en) 2008-01-11 2012-01-31 Seven Networks, Inc. Mobile virtual network operator
US8862657B2 (en) 2008-01-25 2014-10-14 Seven Networks, Inc. Policy based content service
US20090193338A1 (en) 2008-01-28 2009-07-30 Trevor Fiatal Reducing network and battery consumption during content delivery and playback
US20090210351A1 (en) * 2008-02-15 2009-08-20 Bush Christopher L System and Method for Minimizing Redundant Meetings
US20090210261A1 (en) * 2008-02-20 2009-08-20 Rearden Commerce, Inc. System and Method for Multi-Modal Travel Shopping
US20090228321A1 (en) * 2008-03-04 2009-09-10 Oracle International Corporation Accessing an Enterprise Calendar and Scheduling Group Meetings Using a Mobile Device
US20090248457A1 (en) * 2008-03-31 2009-10-01 Rearden Commerce, Inc. System and Method for Providing Travel Schedule of Contacts
US20090255153A1 (en) * 2008-04-15 2009-10-15 Microsoft Corporation Group calendar interface
US7882244B2 (en) * 2008-04-23 2011-02-01 Sharp Laboratories Of America, Inc. Method and system for facilitating group organization using mobile devices
US8787947B2 (en) 2008-06-18 2014-07-22 Seven Networks, Inc. Application discovery on mobile devices
US20090327439A1 (en) * 2008-06-25 2009-12-31 Heims Tracy M Mobile phone and computer message system
US8078158B2 (en) 2008-06-26 2011-12-13 Seven Networks, Inc. Provisioning applications for a mobile device
US8909759B2 (en) 2008-10-10 2014-12-09 Seven Networks, Inc. Bandwidth measurement
US8135770B2 (en) * 2008-12-29 2012-03-13 International Business Machines Corporation Processing recurring events within personal information management clients
US20100198871A1 (en) * 2009-02-03 2010-08-05 Hewlett-Packard Development Company, L.P. Intuitive file sharing with transparent security
US20100211419A1 (en) * 2009-02-13 2010-08-19 Rearden Commerce, Inc. Systems and Methods to Present Travel Options
US20100235216A1 (en) * 2009-03-16 2010-09-16 Microsoft Corporation Integration of pre-meeting and post-meeting experience into a meeting lifecycle
US8626552B2 (en) * 2009-03-26 2014-01-07 International Business Machines Corporation Quorum management of appointment scheduling
US10552849B2 (en) 2009-04-30 2020-02-04 Deem, Inc. System and method for offering, tracking and promoting loyalty rewards
WO2011126889A2 (en) 2010-03-30 2011-10-13 Seven Networks, Inc. 3d mobile user interface with configurable workspace management
US8886176B2 (en) 2010-07-26 2014-11-11 Seven Networks, Inc. Mobile application traffic optimization
EP3651028A1 (en) 2010-07-26 2020-05-13 Seven Networks, LLC Mobile network traffic coordination across multiple applications
US8838783B2 (en) 2010-07-26 2014-09-16 Seven Networks, Inc. Distributed caching for resource and mobile network traffic management
US9077630B2 (en) 2010-07-26 2015-07-07 Seven Networks, Inc. Distributed implementation of dynamic wireless traffic policy
US8204953B2 (en) 2010-11-01 2012-06-19 Seven Networks, Inc. Distributed system for cache defeat detection and caching of content addressed by identifiers intended to defeat cache
US8843153B2 (en) 2010-11-01 2014-09-23 Seven Networks, Inc. Mobile traffic categorization and policy for network use optimization while preserving user experience
CN103620576B (en) 2010-11-01 2016-11-09 七网络公司 It is applicable to the caching of mobile applications behavior and network condition
WO2012060997A2 (en) 2010-11-01 2012-05-10 Michael Luna Application and network-based long poll request detection and cacheability assessment therefor
US8326985B2 (en) 2010-11-01 2012-12-04 Seven Networks, Inc. Distributed management of keep-alive message signaling for mobile network resource conservation and optimization
US9060032B2 (en) 2010-11-01 2015-06-16 Seven Networks, Inc. Selective data compression by a distributed traffic management system to reduce mobile data traffic and signaling traffic
WO2012060995A2 (en) 2010-11-01 2012-05-10 Michael Luna Distributed caching in a wireless network of content delivered for a mobile application over a long-held request
US8484314B2 (en) 2010-11-01 2013-07-09 Seven Networks, Inc. Distributed caching in a wireless network of content delivered for a mobile application over a long-held request
US9330196B2 (en) 2010-11-01 2016-05-03 Seven Networks, Llc Wireless traffic management system cache optimization using http headers
CA2798523C (en) 2010-11-22 2015-02-24 Seven Networks, Inc. Aligning data transfer to optimize connections established for transmission over a wireless network
GB2500327B (en) 2010-11-22 2019-11-06 Seven Networks Llc Optimization of resource polling intervals to satisfy mobile device requests
GB2501416B (en) 2011-01-07 2018-03-21 Seven Networks Llc System and method for reduction of mobile network traffic used for domain name system (DNS) queries
WO2012145533A2 (en) 2011-04-19 2012-10-26 Seven Networks, Inc. Shared resource and virtual resource management in a networked environment
EP2702500B1 (en) 2011-04-27 2017-07-19 Seven Networks, LLC Detecting and preserving state for satisfying application requests in a distributed proxy and cache system
GB2496537B (en) 2011-04-27 2014-10-15 Seven Networks Inc System and method for making requests on behalf of a mobile device based on atmoic processes for mobile network traffic relief
US9449288B2 (en) 2011-05-20 2016-09-20 Deem, Inc. Travel services search
EP2737742A4 (en) 2011-07-27 2015-01-28 Seven Networks Inc Automatic generation and distribution of policy information regarding malicious mobile traffic in a wireless network
WO2013033785A1 (en) * 2011-09-08 2013-03-14 Calert Pty Ltd Mobile communication device event scheduling
WO2013086214A1 (en) 2011-12-06 2013-06-13 Seven Networks, Inc. A system of redundantly clustered machines to provide failover mechanisms for mobile traffic management and network resource conservation
US8934414B2 (en) 2011-12-06 2015-01-13 Seven Networks, Inc. Cellular or WiFi mobile traffic optimization based on public or private network destination
WO2013086455A1 (en) 2011-12-07 2013-06-13 Seven Networks, Inc. Flexible and dynamic integration schemas of a traffic management system with various network operators for network traffic alleviation
WO2013086447A1 (en) 2011-12-07 2013-06-13 Seven Networks, Inc. Radio-awareness of mobile device for sending server-side control signals using a wireless network optimized transport protocol
EP2792188B1 (en) 2011-12-14 2019-03-20 Seven Networks, LLC Mobile network reporting and usage analytics system and method using aggregation of data in a distributed traffic optimization system
US9832095B2 (en) 2011-12-14 2017-11-28 Seven Networks, Llc Operation modes for mobile traffic optimization and concurrent management of optimized and non-optimized traffic
WO2013090821A1 (en) 2011-12-14 2013-06-20 Seven Networks, Inc. Hierarchies and categories for management and deployment of policies for distributed wireless traffic optimization
US8909202B2 (en) 2012-01-05 2014-12-09 Seven Networks, Inc. Detection and management of user interactions with foreground applications on a mobile device in distributed caching
US8843558B2 (en) * 2012-01-09 2014-09-23 International Business Machines Corporation Calendaring tool with optimized management capabilities
WO2013116856A1 (en) 2012-02-02 2013-08-08 Seven Networks, Inc. Dynamic categorization of applications for network access in a mobile network
WO2013116852A1 (en) 2012-02-03 2013-08-08 Seven Networks, Inc. User as an end point for profiling and optimizing the delivery of content and data in a wireless network
US8812695B2 (en) 2012-04-09 2014-08-19 Seven Networks, Inc. Method and system for management of a virtual network connection without heartbeat messages
WO2013155208A1 (en) 2012-04-10 2013-10-17 Seven Networks, Inc. Intelligent customer service/call center services enhanced using real-time and historical mobile application and traffic-related statistics collected by a distributed caching system in a mobile network
US8775631B2 (en) 2012-07-13 2014-07-08 Seven Networks, Inc. Dynamic bandwidth adjustment for browsing or streaming activity in a wireless network based on prediction of user behavior when interacting with mobile applications
KR20140027826A (en) * 2012-08-27 2014-03-07 삼성전자주식회사 Apparatus and method for displaying a content in a portabel terminal
US9161258B2 (en) 2012-10-24 2015-10-13 Seven Networks, Llc Optimized and selective management of policy deployment to mobile clients in a congested network to prevent further aggravation of network congestion
US9307493B2 (en) 2012-12-20 2016-04-05 Seven Networks, Llc Systems and methods for application management of mobile device radio state promotion and demotion
US9241314B2 (en) 2013-01-23 2016-01-19 Seven Networks, Llc Mobile device with application or context aware fast dormancy
US8874761B2 (en) 2013-01-25 2014-10-28 Seven Networks, Inc. Signaling optimization in a wireless network for traffic utilizing proprietary and non-proprietary protocols
US9326185B2 (en) 2013-03-11 2016-04-26 Seven Networks, Llc Mobile network congestion recognition for optimization of mobile traffic
US9065765B2 (en) 2013-07-22 2015-06-23 Seven Networks, Inc. Proxy server associated with a mobile carrier for enhancing mobile traffic management in a mobile network
US10096002B2 (en) * 2014-04-14 2018-10-09 The Boeing Company Time zone sensitive calendar
US9984037B1 (en) 2015-04-27 2018-05-29 Synaptic Engines, Llc Scheduler for a fine grained graph processor
US10796284B2 (en) 2016-09-20 2020-10-06 Fujitsu Limited Collaborative scheduling
US10389764B2 (en) 2016-10-18 2019-08-20 At&T Intellectual Property I, L.P. Network data source time management for data streaming processing system

Family Cites Families (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5392390A (en) 1992-04-10 1995-02-21 Intellilink Corp. Method for mapping, translating, and dynamically reconciling data between disparate computer platforms
US5666530A (en) * 1992-12-02 1997-09-09 Compaq Computer Corporation System for automatic synchronization of common file between portable computer and host computer via communication channel selected from a plurality of usable channels there between
US5729687A (en) * 1993-12-20 1998-03-17 Intel Corporation System for sending differences between joining meeting information and public meeting information between participants in computer conference upon comparing annotations of joining and public meeting information
US5805830A (en) * 1994-09-30 1998-09-08 Intel Corporation Method and apparatus for managing communications with selective subsets of conference participants
US5684990A (en) 1995-01-11 1997-11-04 Puma Technology, Inc. Synchronization of disparate databases
US5758354A (en) * 1995-04-28 1998-05-26 Intel Corporation Application independent e-mail synchronization
US5664228A (en) 1995-08-09 1997-09-02 Microsoft Corporation Portable information device and system and method for downloading executable instructions from a computer to the portable information device
PL177486B1 (en) * 1995-08-14 1999-11-30 Ibm Improved services of distribution of queuing the messages for postal systems
US5630081A (en) 1995-09-07 1997-05-13 Puma Technology, Inc. Connection resource manager displaying link-status information using a traffic light iconic representation
US5884323A (en) 1995-10-13 1999-03-16 3Com Corporation Extendible method and apparatus for synchronizing files on two different computer systems
US5727202A (en) * 1995-10-18 1998-03-10 Palm Computing, Inc. Method and apparatus for synchronizing information on two different computer systems
US6016478A (en) * 1996-08-13 2000-01-18 Starfish Software, Inc. Scheduling system with methods for peer-to-peer scheduling of remote users
US6018761A (en) * 1996-12-11 2000-01-25 The Robert G. Uomini And Louise B. Bidwell Trust System for adding to electronic mail messages information obtained from sources external to the electronic mail transport process
US5961590A (en) * 1997-04-11 1999-10-05 Roampage, Inc. System and method for synchronizing electronic mail between a client site and a central site
US6034621A (en) * 1997-11-18 2000-03-07 Lucent Technologies, Inc. Wireless remote synchronization of data between PC and PDA
US5960406A (en) * 1998-01-22 1999-09-28 Ecal, Corp. Scheduling system for use between users on the web

Cited By (107)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8060564B2 (en) 1998-05-29 2011-11-15 Research In Motion Limited System and method for pushing information from a host system to a mobile data communication device
US6463463B1 (en) 1998-05-29 2002-10-08 Research In Motion Limited System and method for pushing calendar event messages from a host system to a mobile data communication device
US9374435B2 (en) 1998-05-29 2016-06-21 Blackberry Limited System and method for using trigger events and a redirector flag to redirect messages
US9298793B2 (en) 1998-05-29 2016-03-29 Blackberry Limited System and method for pushing information from a host system to a mobile data communication device
US7953802B2 (en) 1998-05-29 2011-05-31 Research In Motion Limited System and method for pushing information from a host system to a mobile data communication device
US6701378B1 (en) 1998-05-29 2004-03-02 Research In Motion Limited System and method for pushing information from a host system to a mobile data communication device
US9344839B2 (en) 1998-05-29 2016-05-17 Blackberry Limited System and method for pushing information from a host system to a mobile communication device
US6438585B2 (en) 1998-05-29 2002-08-20 Research In Motion Limited System and method for redirecting message attachments between a host system and a mobile data communication device
US8516055B2 (en) 1998-05-29 2013-08-20 Research In Motion Limited System and method for pushing information from a host system to a mobile data communication device in a wireless data network
US6463464B1 (en) * 1998-05-29 2002-10-08 Research In Motion Limited System and method for pushing information from a host system to a mobile data communication device
US20090164595A1 (en) * 1999-10-13 2009-06-25 Lot 38 Acquisition Foundation, Llc Method and system for creating and sending handwritten or handdrawn messages via mobile devices
US8782159B2 (en) * 1999-10-13 2014-07-15 Lot 38 Acquisition Foundation, Llc Method and system for creating and sending handwritten or handdrawn messages via mobile devices
US8050684B2 (en) 2000-12-22 2011-11-01 Research In Motion Limited Wireless router system and method
US8165575B2 (en) 2000-12-22 2012-04-24 Research In Motion Limited Wireless router system and method
US8483694B2 (en) 2000-12-22 2013-07-09 Research In Motion Limited Wireless router system and method
US8693996B2 (en) 2000-12-22 2014-04-08 Blackberry Limited Wireless router system and method
US8498289B2 (en) 2001-01-18 2013-07-30 Research In Motion Limited System, method and mobile device for remote control of a voice mail system
US6592038B2 (en) 2001-04-09 2003-07-15 Ncr Corporation Item processing system and method which track label usage
US9584366B2 (en) 2001-10-26 2017-02-28 Blackberry Limited System and method for controlling configuration settings for mobile communication devices and services
US8134954B2 (en) 2001-10-26 2012-03-13 Research In Motion Limited System and method for controlling configuration settings for mobile communication devices and services
US8259611B2 (en) 2001-10-26 2012-09-04 Research In Motion Limited System and method for controlling configuration settings for mobile communication devices and services
US11310219B2 (en) 2001-10-26 2022-04-19 Blackberry Limited System and method for controlling configuration settings for mobile communication devices and services
US10476865B2 (en) 2001-10-26 2019-11-12 Blackberry Limited System and method for controlling configuration settings for mobile communication devices and services
US9049071B2 (en) 2001-10-26 2015-06-02 Blackberry Limited System and method for controlling configuration settings for mobile communication devices and services
US8180900B2 (en) 2001-12-07 2012-05-15 Research In Motion Limited System and method of managing information distribution to mobile stations
US9369531B2 (en) 2001-12-07 2016-06-14 Blackberry Limited System and method of managing information distribution to mobile stations
US8694650B2 (en) 2001-12-07 2014-04-08 Blackberry Limited System and method of managing information distribution to mobile stations
US7865387B2 (en) * 2002-05-23 2011-01-04 Aol Inc. Method and system for scheduling a meeting for a set of attendees via a special attendee
US8239236B2 (en) 2002-05-23 2012-08-07 Aol Inc. Method and system for scheduling a meeting for a set of attendees via a special attendee
US20110167356A1 (en) * 2002-05-23 2011-07-07 Aol Inc. Method and System for Scheduling a Meeting for a Set of Attendees Via a Special Attendee
US20030220826A1 (en) * 2002-05-23 2003-11-27 Steve Mansour Time request queue
US7912745B2 (en) 2002-05-23 2011-03-22 Aol Inc. Method and system for scheduling a meeting for a set of attendees via a special attendee
US20100169141A1 (en) * 2002-05-23 2010-07-01 Steve Mansour Time request queue
US20090286513A1 (en) * 2002-06-14 2009-11-19 At&T Mobility Ii Llc Apparatus And Systems For Providing Location-Based Services Within A Wireless Network
US9037159B2 (en) 2002-06-14 2015-05-19 At&T Mobility Ii Llc Apparatus and systems for providing location-based services within a wireless network
US8634857B2 (en) 2002-06-14 2014-01-21 At&T Mobility Ii Llc Apparatus and systems for providing location-based services within a wireless network
US8068857B2 (en) 2002-06-14 2011-11-29 At&T Mobility Ii Llc Apparatus and systems for providing location-based services within a wireless network
US20050143097A1 (en) * 2002-06-14 2005-06-30 Cingular Wireless Ii, Llc System for providing location-based services in a wireless network, such as providing notification regarding meetings, destination arrivals, and the like
US9918194B2 (en) 2002-06-14 2018-03-13 At&T Mobility Ii Llc Apparatus and systems for providing location-based services within a wireless network
US9451405B2 (en) 2002-06-14 2016-09-20 At&T Mobility Ii Llc Apparatus and systems for providing location-based services within a wireless network
US8230026B2 (en) 2002-06-26 2012-07-24 Research In Motion Limited System and method for pushing information between a host system and a mobile data communication device
US20040196866A1 (en) * 2002-09-16 2004-10-07 Samsung Electronics Co., Ltd. Method for transmitting and recording schedule using short message service
US8046008B2 (en) * 2002-09-16 2011-10-25 Samsung Electronics Co., Ltd Method for transmitting and recording schedule using short message service
US7831734B2 (en) * 2002-11-25 2010-11-09 Sap Ag Method and system for remote configuration of network devices
US20040199611A1 (en) * 2002-11-25 2004-10-07 Sven Bernhard Method and system for remote configuration of network devices
US20060142997A1 (en) * 2002-12-27 2006-06-29 Per Jakobsen Predictive text entry and data compression method for a mobile communication terminal
US9037660B2 (en) 2003-05-09 2015-05-19 Google Inc. Managing electronic messages
US9576271B2 (en) 2003-06-24 2017-02-21 Google Inc. System and method for community centric resource sharing based on a publishing subscription model
US7631060B2 (en) 2003-10-23 2009-12-08 Microsoft Corporation Identity system for use in a computing environment
US7593951B2 (en) * 2003-10-23 2009-09-22 Microsoft Corporation Application programming interface for centralized storage of principal data
US20070094301A1 (en) * 2003-10-23 2007-04-26 Microsoft Corporation Application programming interface for centralized storage of principal data
US20050091264A1 (en) * 2003-10-23 2005-04-28 Microsoft Corporation Identity system for use in a computing environment
US20050108359A1 (en) * 2003-11-05 2005-05-19 Robert Hyder Remote mail management system
US8489442B1 (en) 2004-02-02 2013-07-16 Avaya Inc. Interface for meeting facilitation and coordination, method and apparatus
US8706539B1 (en) 2004-02-02 2014-04-22 Avaya Inc. Interface for meeting facilitation and coordination, method and apparatus
US7440961B1 (en) * 2004-02-18 2008-10-21 Microsoft Corporation System and method for filtering recurrence events
US20080275986A1 (en) * 2004-06-30 2008-11-06 Yen-Fu Chen Method to Update Status on Multiple Voice and Text Systems from a Single Device
US7631042B2 (en) 2004-06-30 2009-12-08 International Business Machines Corporation Method to update status on multiple voice and text systems from a single device
US20060031470A1 (en) * 2004-06-30 2006-02-09 International Business Machines Corporation Method to update status on multiple voice and text systems from a single device
FR2873220A1 (en) * 2004-07-16 2006-01-20 Imed Oueslati Online diary management device for use in e.g. enterprise, has module displaying user diaries` data and functions input and conversion in standard and multilingual formats and module securing user data
EP1655693A1 (en) * 2004-11-03 2006-05-10 Research In Motion Limited Handheld electronic device including appointment and meeting conflict notification, and associated method
US8136035B2 (en) 2004-11-03 2012-03-13 Research In Motion Limited Handheld electronic device including appointment and meeting conflict notification, and associated method
US20080235287A1 (en) * 2004-11-03 2008-09-25 Bocking Andrew D Handheld electronic device including appointment and meeting conflict notification, and associated method
US20060095859A1 (en) * 2004-11-03 2006-05-04 Bocking Andrew D Handheld electronic device including appointment and meeting conflict notification, and associated method
US9047592B2 (en) 2004-11-03 2015-06-02 Blackberry Limited Handheld electronic device including appointment and meeting conflict notification, and associated method
US7519924B2 (en) 2004-11-03 2009-04-14 Research In Motion Limited Handheld electronic device including appointment and meeting conflict notification, and associated method
US20060123088A1 (en) * 2004-12-02 2006-06-08 Microsoft Corporation System and method for replicating offline scheduling transactions from a client to a server
US9183547B2 (en) * 2004-12-02 2015-11-10 Microsoft Technology Licensing, Llc System and method for replicating offline scheduling transactions from a client to a server
US8185590B2 (en) * 2004-12-02 2012-05-22 Microsoft Corporation System and method for replicating offline scheduling transactions from a client to a server
US20120254282A1 (en) * 2004-12-02 2012-10-04 Microsoft Corporation System and method for replicating offline scheduling transactions from a client to a server
US20170111400A1 (en) 2005-04-18 2017-04-20 Blackberry Limited Method for providing wireless application privilege management
US9537896B2 (en) 2005-04-18 2017-01-03 Blackberry Limited Method for providing wireless application privilege management
US10965718B2 (en) 2005-04-18 2021-03-30 Blackberry Limited Method for providing wireless application privilege management
US10462189B2 (en) 2005-04-18 2019-10-29 Blackberry Limited Method for providing wireless application privilege management
US8365240B2 (en) 2005-04-18 2013-01-29 Research In Motion Limited Method for providing wireless application privilege management
US9059891B2 (en) 2005-04-18 2015-06-16 Blackberry Limited Method for providing wireless application privilege management
US10686842B2 (en) 2005-04-18 2020-06-16 Blackberry Limited Method for providing wireless application privilege management
US9152475B1 (en) * 2005-09-29 2015-10-06 Hewlett-Packard Development Company, L.P. Notifying listeners of change events
US20070136119A1 (en) * 2005-12-08 2007-06-14 Record Andrew D Recurrence definition identification
US9892382B2 (en) * 2005-12-08 2018-02-13 International Business Machines Corporation Recurrence definition identification
US7984378B1 (en) 2006-02-07 2011-07-19 Avaya Inc. Management of meetings by grouping
US20070250366A1 (en) * 2006-04-21 2007-10-25 Nokia Corporation Apparatus, method and computer program product for annotating a meeting in an electronic calendar
US8600794B2 (en) 2006-05-10 2013-12-03 Avaya Inc. Meeting notification and merging agents
US20070265903A1 (en) * 2006-05-10 2007-11-15 Colin Blair Meeting notification and merging agents
US7778858B1 (en) * 2006-07-17 2010-08-17 Avaya Inc. Linking unable to respond messages to entries in electronic calendar
US9129264B2 (en) * 2006-10-11 2015-09-08 Google Inc. Electronic calendar auto event resolution system and method
US20100217644A1 (en) * 2006-10-11 2010-08-26 International Business Machines Corporation Electronic Calendar Auto Event Resolution System and Method
US10445703B1 (en) 2006-10-30 2019-10-15 Avaya Inc. Early enough reminders
US8037143B1 (en) 2006-10-30 2011-10-11 Avaya Inc. Automatic display of email distribution lists
US7693736B1 (en) 2006-10-30 2010-04-06 Avaya Inc. Recurring meeting schedule wizard
US7827240B1 (en) 2007-01-02 2010-11-02 Avaya Inc. Calendar item hierarchy for automatic specialization
US9258372B2 (en) 2007-05-09 2016-02-09 Blackberry Limited Wireless router system and method
US8200520B2 (en) 2007-10-03 2012-06-12 International Business Machines Corporation Methods, systems, and apparatuses for automated confirmations of meetings
US7899779B1 (en) 2008-02-21 2011-03-01 SmartLine Inc. Security system for synchronization of desktop and mobile device data
US7899782B1 (en) * 2008-02-21 2011-03-01 SmartLine Inc. Security system for synchronization of desktop and mobile device data
US20100030788A1 (en) * 2008-08-01 2010-02-04 Chin-Ju Rex Chen Automatic temporary address book
US20140200944A1 (en) * 2011-11-08 2014-07-17 Matchware A/S Automation of meeting scheduling and task list access permissions within a meeting series
US9274687B1 (en) 2013-10-11 2016-03-01 Google Inc. Managing schedule changes for correlated calendar events
US9871756B1 (en) 2014-02-13 2018-01-16 Google Inc. Methods for displaying notifications
US9531651B1 (en) 2014-02-13 2016-12-27 Google Inc. Methods for displaying notifications
US10636014B2 (en) * 2016-09-26 2020-04-28 Microsoft Technology Licensing, Llc Conversational calendar integration
US11706339B2 (en) * 2019-07-05 2023-07-18 Talkdesk, Inc. System and method for communication analysis for use with agent assist within a cloud-based contact center
US11783246B2 (en) 2019-10-16 2023-10-10 Talkdesk, Inc. Systems and methods for workforce management system deployment
US11736615B2 (en) 2020-01-16 2023-08-22 Talkdesk, Inc. Method, apparatus, and computer-readable medium for managing concurrent communications in a networked call center
US11677875B2 (en) 2021-07-02 2023-06-13 Talkdesk Inc. Method and apparatus for automated quality management of communication records
US11856140B2 (en) 2022-03-07 2023-12-26 Talkdesk, Inc. Predictive communications system
US11736616B1 (en) 2022-05-27 2023-08-22 Talkdesk, Inc. Method and apparatus for automatically taking action based on the content of call center communications

Also Published As

Publication number Publication date
US6370566B2 (en) 2002-04-09

Similar Documents

Publication Publication Date Title
US6370566B2 (en) Generating meeting requests and group scheduling from a mobile device
US6052735A (en) Electronic mail object synchronization between a desktop computer and mobile device
US6216131B1 (en) Methods for mapping data fields from one data set to another in a data processing environment
US11050693B2 (en) System and apparatus for sending complete responses to truncated electronic mail messages on a mobile device
US8719842B2 (en) Transmitting a calendar event in target calendaring system format
US7284002B2 (en) Calendar-enhanced awareness for instant messaging systems and electronic status boards
US6216110B1 (en) System and method for publishing calendar information to a publicly accessible location
US5930471A (en) Communications system and method of operation for electronic messaging using structured response objects and virtual mailboxes
US6016478A (en) Scheduling system with methods for peer-to-peer scheduling of remote users
US8219920B2 (en) Methods and systems for managing to do items or notes or electronic messages
US6915312B2 (en) Data processing environment with methods providing contemporaneous synchronization of two or more clients
US8171104B2 (en) Scheduling and searching meetings in a network environment
JP4575591B2 (en) Meeting requests and group scheduling generation from mobile devices
US20080065758A1 (en) Dynamic transient buddy and contact lists
US20090125818A1 (en) Systems and methods to create follow-up meetings
US20070101284A1 (en) Unified tracking of time dependent events
JPS63189965A (en) Electronic type schedule management
US20120131024A1 (en) Apparatus and method for providing contact information and portable terminal using same
EP1986142A1 (en) Method and system for modifying a meeting attendee list of an email calendar application
EP1868147A1 (en) Method and System for Generating and Processing Electronic Meeting Communications for Multiple Formats
JP2000148691A (en) Information synchronization system and recording medium
JP2002269019A (en) Project management method, program for executing the method, and recording medium

Legal Events

Date Code Title Description
AS Assignment

Owner name: MICROSOFT CORPORATION, WASHINGTON

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:DISCLOLO, ANTHONY;SKORUPA, SCOTT;ALAM, SALIM;AND OTHERS;REEL/FRAME:009116/0322;SIGNING DATES FROM 19980327 TO 19980331

AS Assignment

Owner name: MICROSOFT CORPORATION, WASHINGTON

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:ULRICH, BRYCE;REEL/FRAME:009288/0431

Effective date: 19980618

AS Assignment

Owner name: MICROSOFT CORPORATION, WASHINGTON

Free format text: CORRECTED ASSIGNMENT TO CORRECT THE LAST NAME OF FIRST INVENTOR RECORDED ON REEL 9116, FRAME 322.;ASSIGNORS:DISCOLO, ANTHONY;SKORUPA, SCOTT;ALAM, SALIM;AND OTHERS;REEL/FRAME:009910/0239;SIGNING DATES FROM 19980327 TO 19980331

STCF Information on status: patent grant

Free format text: PATENTED CASE

CC Certificate of correction
FPAY Fee payment

Year of fee payment: 4

CC Certificate of correction
FPAY Fee payment

Year of fee payment: 8

FPAY Fee payment

Year of fee payment: 12

AS Assignment

Owner name: MICROSOFT TECHNOLOGY LICENSING, LLC., WASHINGTON

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MICROSOFT CORPORATION;REEL/FRAME:034142/0148

Effective date: 20141014