US20080040192A1 - System and Method for Scheduled Events to Subscribe to Live Information Topics - Google Patents
System and Method for Scheduled Events to Subscribe to Live Information Topics Download PDFInfo
- Publication number
- US20080040192A1 US20080040192A1 US11/877,171 US87717107A US2008040192A1 US 20080040192 A1 US20080040192 A1 US 20080040192A1 US 87717107 A US87717107 A US 87717107A US 2008040192 A1 US2008040192 A1 US 2008040192A1
- Authority
- US
- United States
- Prior art keywords
- topic
- channel
- event
- calendar
- topic channel
- 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.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/109—Time management, e.g. calendars, reminders, meetings or time accounting
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0631—Resource planning, allocation, distributing or scheduling for enterprises or organisations
- G06Q10/06314—Calendaring for a resource
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S715/00—Data processing: presentation processing of document, operator interface processing, and screen saver display processing
- Y10S715/961—Operator interface with visual structure or function dictated by intended use
- Y10S715/963—Calendar or scheduling
Definitions
- the present invention relates generally to the field of electronic calendar systems. More specifically, the present invention is related to accessing dynamic content linked to different calendar events.
- entries are static. They are entered by a calendar user as a reminder for a future event and, perhaps, an accompanying alarm is set as well. Recently, it has been recognized that it would be useful for a calendar system to automatically retrieve additional information related to the scheduled events or entries. Examples of additional information that can be automatically collected and tied to a calendar entries include information about meeting participants, flight itineraries, driving instructions, and weather forecasts. While this general concept has previously been identified, the prior art fails to provide details regarding how to implement the capability of linking calendar events and related dynamic information. The following two patents provide an introduction to electronic calendaring systems and locating additional information relevant to a calendar entry.
- the prior art does not provide for sharing and linking additional information among multiple calendar events and multiple calendar users; nor does it provide methods for updating and refreshing dynamic information.
- a calendar system stores and organizes materials related to scheduled events, to-dos, addresses, etc. and allows a user to browse a calendar and select entries for viewing.
- each entry is linked to any number of topics related to that entry and up-to-date information on these topics are displayed when the entry is viewed.
- Topics are published on topic channels by one or more topic providers and a calendar system administrator defines which topics relate to which calendar entries.
- the calendar system determines which topics relate to that event and identifies corresponding topic channels which currently exist, or need to be created, between the calendar system and the topic providers.
- links are created to local versions of the appropriate topic channels and the entry is then persistently stored. Multiple calendar events and multiple calendar users are able to link to the same local topic channel and thereby reduce data searching, retrieval, and storage costs.
- FIG. 1 illustrates the overall architecture of a calendar system according to the present invention.
- FIG. 2 illustrates a flowchart of a method of linking a topic channel to a new calendar event according to the present invention.
- FIG. 3 illustrates a flowchart of a method of removing a topic channel according to the present invention.
- Services gather information, organize the information into topics and publish the information periodically to update its subscribers. Services are typically distributed across a number of separate servers across multiple networks.
- Service Parameters Service parameters control things such as refresh rates for individual topics, information retrieval control parameters, etc.
- Topic A topic is a node in a topic tree. Topic names are hierarchical. For example, a weather service has two topics “Weather/San Jose” and “Weather/Boston”. A subscriber can subscribe to any of these two topics; meaning the subscriber retrieves weather forecasts from both San Jose and Boston. The subscriber can also subscribe to the root topic, “Weather”.
- Topic Channel A topic channel is used to pass messages from a topic publisher to a topic subscriber.
- Sun'sTM Java Messaging Service Interface is one standard for setting up publisher/subscriber infrastructures across networks.
- Microsoft'sTM Channel Definition Format is a specification regarding how web publishers can offer frequently updated collections of information to interested subscribers.
- FIG. 1 depicts the logical components of the present invention along with their interconnections. The principles and operation of the present invention are provided by discussing the flow of information between these logical components.
- Calendar Server 100 is illustrated as a single entity; however, the present invention also contemplates the logical components of server 100 distributed across networked systems.
- Calendar Server 100 handles request 120 from a client (not shown) and, in response, creates new calendar event (or entry, throughout the specification these terms are used interchangeably) 108 .
- Request Handler 102 receives request 120 for a new event 108 to be scheduled and begins processing it.
- Request Handler 102 first passes new event 108 to Topic Selector 104 .
- Topic Selector 104 receives new event 108 and retrieves from Topic Binding Repository 106 all the services which are associated with new event 108 . Specifically, Topic Selector 104 extracts relevant information from new event 108 and forwards it to Repository 106 which then maps the event's category (e.g. meeting, travel, vacation etc.) and the event's properties (e.g. departure location, destination, date, etc.) to a number of corresponding services. Repository 106 and its mappings are typically set up by a calendar administrator; however, the present invention also contemplates within its scope custom editing of Repository 106 entries by clients. As an example, when a client schedules a business trip to Boston, Mass.
- event's category e.g. meeting, travel, vacation etc.
- the event's properties e.g. departure location, destination, date, etc.
- Topic Selector 104 looks in Topic Binding Repository 106 under the business trip category and finds (for example) mapping entries identifying two services: “Weather” and “FlightSchedules”. Further, Topic Selector 104 extracts, from new event 108 , the destination for this business trip which results in the construction of two topic names: “Weather/MA/Boston” and “FlightSchedules/SJC/Boston”. Many additional topic names and services are contemplated within the scope of the present invention.
- Topic Finder 110 which returns a list of Topic Channels 114 a, 114 b and 114 c.
- Topic Finder 110 takes the list of topic names and, for each name, checks whether there is an existing Topic Channel already set-up. If there is, then this existing Topic Channel is used. If not, then a new Topic Channel must be created for new event 108 . To create a new Topic Channel, Topic Finder 110 instructs Topic Creator 112 to create an appropriate, new Topic Channel for new event 108 .
- Topic Creator 112 receives one or more topic names (e.g. Weather/AZ/Tucson) from Topic Finder 110 and sends a request to an administrator 160 of a remote Topic Provider 150 to create a new Topic 156 a, 156 b and 156 c and Topic Channel 158 a, 158 b and 158 c for a given topic name.
- Topic Creator 112 creates corresponding local Topic Channel(s) 114 a, 114 b and 114 c, which are also linked to remote Topic Channels 158 a, 158 b and 158 c, and returns these channel names to Topic Finder 110 .
- Remote Topic Provider(s) 150 and their administrator(s) 160 control, using known methods, how services 154 a and 154 b, Topics 156 a, 156 b and 156 c, and Topic Channels 158 a, 158 b and 158 c are internally managed and arranged. While depicted as a homogeneous block in FIG. 1 , multiple and distributed Topic Providers 150 are also considered within the scope of the present invention.
- Topic Finder 110 receives from Topic Creator 112 a list of topic channels (existing or newly created) corresponding to new event 108 and forwards this list to Topic Selector 104 which then passes the list to Request Handler 102 .
- Request Handler 102 continues processing new event 108 by adding a link in new event 108 to each Topic Channel 114 a, 114 b and 114 c received from Topic Selector 104 . Finally, Request Handler 102 stores new event 108 in a persistent calendar store (not shown) in order to allow retrieval at a later time.
- Request Handler 102 In the event that a client requests deletion of a scheduled event, Request Handler 102 first removes all the links to the event's Topic Channels and then proceeds to erase the event from the persistent calendar store.
- FIG. 2 depicts a flowchart of the logic of creating links to topic channels in new events. This figure focuses on the flow of the logic without explicit references to the components performing the steps.
- a new event is retrieved in step 202 .
- topic names are determined which correspond to this type of event and to the data characterizing this event. These topic names are individually looped through, in step 206 , to determine if a corresponding Topic Channel exists (step 208 ) or needs to be created (step 210 ).
- step 212 a list of corresponding Topic Channels is constructed and step 214 loops back around to ensure all topic names have been analyzed. Processing continues, in step 216 , by linking the identified Topic Channels to the new event. After storing the new event in any type of well-known computer storage media, in step 218 , processing finishes in step 220 .
- FIG. 3 illustrates the logical flow of removing a subscriber from a topic.
- step 302 the link from an event to a topic is deleted and step 304 tests whether there are any other links to the particular topic. If there are, then the flow ends in step 308 . If there are no other links, however, the topic is deleted in step 306 and then flow completes with step 308 .
- the present invention allows calendar events to subscribe to specific topics that are relevant to that particular event. Relevant topics include weather forecasts, flight schedules, traffic reports, local news stories and other information. Information is published by an information service and retrieved by one or more information subscribers. Using the infrastructure of the present invention, multiple calendar events are able to share the same information by having each separate event, which relies on similar live information, link to the same local Topic Channel. For example, if two calendar users are traveling to New York on the same day, both events are linked to information retrieved from the New York weather topic and New York local news topic. The present invention relieves the need to repeatedly search, retrieve and store additional information for every single calendar event scheduled. These performance improvements are true for different calendar events belonging to a single user as well as separate calendar events belonging to different users.
- a system and method has been shown in the above embodiments for the effective implementation of linking electronic calendar events to related, dynamic information by subscribing the events to live information topics. While various preferred embodiments have been shown and described, it will be understood that there is no intent to limit the invention by such disclosure, but rather, it is intended to cover all modifications and alternate constructions falling within the spirit and scope of the invention and as further defined in the appended claims.
- the present invention should not be limited by calendaring software/program, computing environment, specific computing hardware, specific information service providers, particular publication/subscription hierarchies, specific enterprise messaging interfaces, particular push-content technologies and specific distributed arrangement of the system's functional components.
- the present invention may be implemented on a conventional IBM PC or equivalent, multi-nodal system (e.g. LAN), across extended networks such as the Internet or using portable equipment such as laptop computers or wireless equipment (RF, microwaves, infrared, photonics, etc.).
Abstract
Description
- This application is a continuation of U.S. application Ser. No. 09/531,016, filed Mar. 20, 2000.
- 1. Field of Invention
- The present invention relates generally to the field of electronic calendar systems. More specifically, the present invention is related to accessing dynamic content linked to different calendar events.
- 2. Discussion of Prior Art
- In traditional electronic scheduling or calendaring systems, entries are static. They are entered by a calendar user as a reminder for a future event and, perhaps, an accompanying alarm is set as well. Recently, it has been recognized that it would be useful for a calendar system to automatically retrieve additional information related to the scheduled events or entries. Examples of additional information that can be automatically collected and tied to a calendar entries include information about meeting participants, flight itineraries, driving instructions, and weather forecasts. While this general concept has previously been identified, the prior art fails to provide details regarding how to implement the capability of linking calendar events and related dynamic information. The following two patents provide an introduction to electronic calendaring systems and locating additional information relevant to a calendar entry.
- The patent to Borovoy et al. (U.S. Pat. No. 5,842,009) provides for a system which automatically retrieves documents relevant to a user's calendar event. This reference focuses on determining when to retrieve information and how to determine what information might be most relevant.
- The patent to Rasansky et al. (U.S. Pat. No. 5,960,406) provides for a computerized calendar and scheduling system which allows access to web-based clients. However, no teaching of dynamic content delivery is provided.
- Whatever the precise merits and features of the prior art in this field, the earlier art does not achieve or fulfill the purposes of the present invention. The prior art does not provide for sharing and linking additional information among multiple calendar events and multiple calendar users; nor does it provide methods for updating and refreshing dynamic information.
- A calendar system stores and organizes materials related to scheduled events, to-dos, addresses, etc. and allows a user to browse a calendar and select entries for viewing. In addition, each entry is linked to any number of topics related to that entry and up-to-date information on these topics are displayed when the entry is viewed. Topics are published on topic channels by one or more topic providers and a calendar system administrator defines which topics relate to which calendar entries. When a client enters information related to a new calendar entry or event, the calendar system determines which topics relate to that event and identifies corresponding topic channels which currently exist, or need to be created, between the calendar system and the topic providers. Finally, in each calendar entry, links are created to local versions of the appropriate topic channels and the entry is then persistently stored. Multiple calendar events and multiple calendar users are able to link to the same local topic channel and thereby reduce data searching, retrieval, and storage costs.
-
FIG. 1 illustrates the overall architecture of a calendar system according to the present invention. -
FIG. 2 illustrates a flowchart of a method of linking a topic channel to a new calendar event according to the present invention. -
FIG. 3 illustrates a flowchart of a method of removing a topic channel according to the present invention. - While this invention is illustrated and described in a preferred embodiment, the invention may be produced in many different configurations, forms and materials. There is depicted in the drawings, and will herein be described in detail, a preferred embodiment of the invention, with the understanding that the present disclosure is to be considered as a exemplification of the principles of the invention and the associated functional specifications of the materials for its construction and is not intended to limit the invention to the embodiment illustrated. Those skilled in the art will envision many other possible variations within the scope of the present invention.
- The following definitions may assist in understanding terminology used throughout the present specification:
- Service: Services gather information, organize the information into topics and publish the information periodically to update its subscribers. Services are typically distributed across a number of separate servers across multiple networks.
- Service Parameters: Service parameters control things such as refresh rates for individual topics, information retrieval control parameters, etc.
- Topic: A topic is a node in a topic tree. Topic names are hierarchical. For example, a weather service has two topics “Weather/San Jose” and “Weather/Boston”. A subscriber can subscribe to any of these two topics; meaning the subscriber retrieves weather forecasts from both San Jose and Boston. The subscriber can also subscribe to the root topic, “Weather”.
- Topic Channel: A topic channel is used to pass messages from a topic publisher to a topic subscriber. Sun's™ Java Messaging Service Interface is one standard for setting up publisher/subscriber infrastructures across networks. Microsoft's™ Channel Definition Format (CDF) is a specification regarding how web publishers can offer frequently updated collections of information to interested subscribers.
-
FIG. 1 depicts the logical components of the present invention along with their interconnections. The principles and operation of the present invention are provided by discussing the flow of information between these logical components. CalendarServer 100 is illustrated as a single entity; however, the present invention also contemplates the logical components ofserver 100 distributed across networked systems. -
Calendar Server 100 handles request 120 from a client (not shown) and, in response, creates new calendar event (or entry, throughout the specification these terms are used interchangeably) 108. In particular, RequestHandler 102 receivesrequest 120 for anew event 108 to be scheduled and begins processing it. RequestHandler 102 first passesnew event 108 toTopic Selector 104. - Topic
Selector 104 receivesnew event 108 and retrieves from Topic Binding Repository 106 all the services which are associated withnew event 108. Specifically,Topic Selector 104 extracts relevant information fromnew event 108 and forwards it toRepository 106 which then maps the event's category (e.g. meeting, travel, vacation etc.) and the event's properties (e.g. departure location, destination, date, etc.) to a number of corresponding services.Repository 106 and its mappings are typically set up by a calendar administrator; however, the present invention also contemplates within its scope custom editing ofRepository 106 entries by clients. As an example, when a client schedules a business trip to Boston, Mass. in their calendar, TopicSelector 104 looks in Topic Binding Repository 106 under the business trip category and finds (for example) mapping entries identifying two services: “Weather” and “FlightSchedules”. Further,Topic Selector 104 extracts, fromnew event 108, the destination for this business trip which results in the construction of two topic names: “Weather/MA/Boston” and “FlightSchedules/SJC/Boston”. Many additional topic names and services are contemplated within the scope of the present invention. - The list of topic names generated from
Topic Binding Repository 106 is passed to Topic Finder 110 which returns a list ofTopic Channels new event 108. To create a new Topic Channel,Topic Finder 110 instructsTopic Creator 112 to create an appropriate, new Topic Channel fornew event 108. -
Topic Creator 112 receives one or more topic names (e.g. Weather/AZ/Tucson) fromTopic Finder 110 and sends a request to anadministrator 160 of aremote Topic Provider 150 to create anew Topic Topic Channel Topic Creator 112 creates corresponding local Topic Channel(s) 114 a, 114 b and 114 c, which are also linked toremote Topic Channels Topic Finder 110. Remote Topic Provider(s) 150 and their administrator(s) 160 control, using known methods, howservices Topics Topic Channels FIG. 1 , multiple and distributedTopic Providers 150 are also considered within the scope of the present invention. -
Topic Finder 110 receives from Topic Creator 112 a list of topic channels (existing or newly created) corresponding tonew event 108 and forwards this list toTopic Selector 104 which then passes the list to RequestHandler 102. -
Request Handler 102 continues processingnew event 108 by adding a link innew event 108 to eachTopic Channel Topic Selector 104. Finally,Request Handler 102 storesnew event 108 in a persistent calendar store (not shown) in order to allow retrieval at a later time. - In the event that a client requests deletion of a scheduled event,
Request Handler 102 first removes all the links to the event's Topic Channels and then proceeds to erase the event from the persistent calendar store. -
FIG. 2 depicts a flowchart of the logic of creating links to topic channels in new events. This figure focuses on the flow of the logic without explicit references to the components performing the steps. - First, a new event is retrieved in
step 202. Next, instep 204, topic names are determined which correspond to this type of event and to the data characterizing this event. These topic names are individually looped through, in step 206, to determine if a corresponding Topic Channel exists (step 208) or needs to be created (step 210). Instep 212, a list of corresponding Topic Channels is constructed and step 214 loops back around to ensure all topic names have been analyzed. Processing continues, instep 216, by linking the identified Topic Channels to the new event. After storing the new event in any type of well-known computer storage media, in step 218, processing finishes instep 220. -
FIG. 3 illustrates the logical flow of removing a subscriber from a topic. Instep 302, the link from an event to a topic is deleted and step 304 tests whether there are any other links to the particular topic. If there are, then the flow ends instep 308. If there are no other links, however, the topic is deleted instep 306 and then flow completes withstep 308. - The present invention allows calendar events to subscribe to specific topics that are relevant to that particular event. Relevant topics include weather forecasts, flight schedules, traffic reports, local news stories and other information. Information is published by an information service and retrieved by one or more information subscribers. Using the infrastructure of the present invention, multiple calendar events are able to share the same information by having each separate event, which relies on similar live information, link to the same local Topic Channel. For example, if two calendar users are traveling to New York on the same day, both events are linked to information retrieved from the New York weather topic and New York local news topic. The present invention relieves the need to repeatedly search, retrieve and store additional information for every single calendar event scheduled. These performance improvements are true for different calendar events belonging to a single user as well as separate calendar events belonging to different users.
- A system and method has been shown in the above embodiments for the effective implementation of linking electronic calendar events to related, dynamic information by subscribing the events to live information topics. While various preferred embodiments have been shown and described, it will be understood that there is no intent to limit the invention by such disclosure, but rather, it is intended to cover all modifications and alternate constructions falling within the spirit and scope of the invention and as further defined in the appended claims. For example, the present invention should not be limited by calendaring software/program, computing environment, specific computing hardware, specific information service providers, particular publication/subscription hierarchies, specific enterprise messaging interfaces, particular push-content technologies and specific distributed arrangement of the system's functional components. In addition, the present invention may be implemented on a conventional IBM PC or equivalent, multi-nodal system (e.g. LAN), across extended networks such as the Internet or using portable equipment such as laptop computers or wireless equipment (RF, microwaves, infrared, photonics, etc.).
Claims (15)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/877,171 US20080040192A1 (en) | 2000-03-20 | 2007-10-23 | System and Method for Scheduled Events to Subscribe to Live Information Topics |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/531,016 US7302643B1 (en) | 2000-03-20 | 2000-03-20 | System and method for scheduled events to subscribe to live information topics |
US11/877,171 US20080040192A1 (en) | 2000-03-20 | 2007-10-23 | System and Method for Scheduled Events to Subscribe to Live Information Topics |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/531,016 Continuation US7302643B1 (en) | 2000-03-20 | 2000-03-20 | System and method for scheduled events to subscribe to live information topics |
Publications (1)
Publication Number | Publication Date |
---|---|
US20080040192A1 true US20080040192A1 (en) | 2008-02-14 |
Family
ID=38722083
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/531,016 Expired - Lifetime US7302643B1 (en) | 2000-03-20 | 2000-03-20 | System and method for scheduled events to subscribe to live information topics |
US11/877,171 Abandoned US20080040192A1 (en) | 2000-03-20 | 2007-10-23 | System and Method for Scheduled Events to Subscribe to Live Information Topics |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/531,016 Expired - Lifetime US7302643B1 (en) | 2000-03-20 | 2000-03-20 | System and method for scheduled events to subscribe to live information topics |
Country Status (1)
Country | Link |
---|---|
US (2) | US7302643B1 (en) |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8370763B1 (en) * | 2001-10-31 | 2013-02-05 | At&T Intellectual Property I, L. P. | System and method for creating an electronic-calendar entry |
WO2013159175A1 (en) * | 2012-04-27 | 2013-10-31 | Research In Motion Limited | Systems and methods for providing files in relation to a calendar event |
WO2013159176A1 (en) * | 2012-04-27 | 2013-10-31 | Research In Motion Limited | Systems and methods for establishing and using a personal linking graph |
US20140040716A1 (en) * | 2012-08-06 | 2014-02-06 | Fisher Lee | Method for personalizing a calendar by collecting web page information according to data entries in the calendar |
Families Citing this family (19)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7003720B1 (en) | 2000-01-07 | 2006-02-21 | Abf Freight Sysems. Inc. | Electronic shipment planner |
US6721779B1 (en) * | 2000-07-07 | 2004-04-13 | Softwired Ag | Messaging proxy system |
US7627830B1 (en) * | 2000-10-31 | 2009-12-01 | Aol Llc, A Delaware Limited Liability Company | Click-to-add, jot-it-down, and add banner |
US7475021B2 (en) * | 2003-10-22 | 2009-01-06 | International Business Machines Corporation | Method and storage medium for importing calendar data from a computer screen into a calendar application |
US7562313B2 (en) * | 2005-12-29 | 2009-07-14 | Sap Ag | Timescale selection window for temporal selection in computer applications |
US8146100B2 (en) * | 2006-03-21 | 2012-03-27 | Sap Ag | System and method for event-based information flow in software development processes |
US20090307212A1 (en) * | 2006-07-13 | 2009-12-10 | Hayoman ,Internet Technologies Ltd. | System and method for event management |
US8578301B2 (en) * | 2006-11-22 | 2013-11-05 | Skadool, Inc. | Hierarchical events |
US8473528B2 (en) * | 2008-08-14 | 2013-06-25 | Accenture Global Services | Delivery enablement workforce utilization tool integration |
EP2455870A1 (en) * | 2010-11-19 | 2012-05-23 | Research In Motion Limited | Method, device and system for record storage in an automatically selected database |
US20120227005A1 (en) * | 2010-12-09 | 2012-09-06 | uTemporis, Inc. | Time-driven event scheduling systems and methods |
TW201243746A (en) * | 2011-04-29 | 2012-11-01 | Ko-Chung Lee | Calendar matching social network system and method for performing the same |
US20130054558A1 (en) * | 2011-08-29 | 2013-02-28 | Microsoft Corporation | Updated information provisioning |
EP2620906A1 (en) * | 2012-01-24 | 2013-07-31 | Amadeus | Automatic live publisher event system and method of same |
US20150234583A1 (en) * | 2014-02-19 | 2015-08-20 | Doat Media Ltd. | System and method for direct communication between a publisher and users |
US9348493B2 (en) * | 2014-05-13 | 2016-05-24 | Jack Ke Zhang | Automated subscriber-based customization of electronic channels for content presentation |
CN108549957B (en) * | 2018-04-11 | 2021-10-29 | 中译语通科技股份有限公司 | Internet topic trend auxiliary prediction method and system and information data processing terminal |
US20230034999A1 (en) * | 2021-07-22 | 2023-02-02 | Microsoft Technology Licensing, Llc | Customizable event management in computing systems |
CN115499791B (en) * | 2022-08-19 | 2024-01-12 | 广州汽车集团股份有限公司 | Service-oriented communication method, device, electronic equipment and storage medium |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5842009A (en) * | 1996-09-30 | 1998-11-24 | Apple Computer, Inc. | System for automatically retrieving information relevant to a user's scheduled event |
US5855006A (en) * | 1996-03-01 | 1998-12-29 | Humware | Personal activity scheduling apparatus |
US5960406A (en) * | 1998-01-22 | 1999-09-28 | Ecal, Corp. | Scheduling system for use between users on the web |
US6065012A (en) * | 1998-02-27 | 2000-05-16 | Microsoft Corporation | System and method for displaying and manipulating user-relevant data |
US6369840B1 (en) * | 1999-03-10 | 2002-04-09 | America Online, Inc. | Multi-layered online calendaring and purchasing |
-
2000
- 2000-03-20 US US09/531,016 patent/US7302643B1/en not_active Expired - Lifetime
-
2007
- 2007-10-23 US US11/877,171 patent/US20080040192A1/en not_active Abandoned
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5855006A (en) * | 1996-03-01 | 1998-12-29 | Humware | Personal activity scheduling apparatus |
US5842009A (en) * | 1996-09-30 | 1998-11-24 | Apple Computer, Inc. | System for automatically retrieving information relevant to a user's scheduled event |
US5960406A (en) * | 1998-01-22 | 1999-09-28 | Ecal, Corp. | Scheduling system for use between users on the web |
US6065012A (en) * | 1998-02-27 | 2000-05-16 | Microsoft Corporation | System and method for displaying and manipulating user-relevant data |
US6369840B1 (en) * | 1999-03-10 | 2002-04-09 | America Online, Inc. | Multi-layered online calendaring and purchasing |
Cited By (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8370763B1 (en) * | 2001-10-31 | 2013-02-05 | At&T Intellectual Property I, L. P. | System and method for creating an electronic-calendar entry |
US9104232B2 (en) | 2001-10-31 | 2015-08-11 | At&T Intellectual Property I, L.P. | System and method for creating an electronic-calendar entry |
WO2013159175A1 (en) * | 2012-04-27 | 2013-10-31 | Research In Motion Limited | Systems and methods for providing files in relation to a calendar event |
WO2013159176A1 (en) * | 2012-04-27 | 2013-10-31 | Research In Motion Limited | Systems and methods for establishing and using a personal linking graph |
US20150088927A1 (en) * | 2012-04-27 | 2015-03-26 | Blackberry Limited | Systems and Methods for Establishing and Using a Personal Linking Graph |
US10475000B2 (en) | 2012-04-27 | 2019-11-12 | Blackberry Limited | Systems and methods for providing files in relation to a calendar event |
US20140040716A1 (en) * | 2012-08-06 | 2014-02-06 | Fisher Lee | Method for personalizing a calendar by collecting web page information according to data entries in the calendar |
CN103577525A (en) * | 2012-08-06 | 2014-02-12 | 李振瀛 | Method for generating personal calendar by collecting web page information according to calendar setting information |
Also Published As
Publication number | Publication date |
---|---|
US7302643B1 (en) | 2007-11-27 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20080040192A1 (en) | System and Method for Scheduled Events to Subscribe to Live Information Topics | |
JP6111394B2 (en) | System and method for controlling access to aspects of an electronic message campaign | |
AU770242B2 (en) | System and method of presenting channelized data | |
US20080163073A1 (en) | System and method for providing multiple participants with a central access portal to geographic point of interest data | |
US6604113B1 (en) | Method and apparatus for providing account information | |
US7136915B2 (en) | System for communicating through maps | |
JP4040849B2 (en) | Knowledge accumulation support system and message transfer method in the same system | |
US8812444B2 (en) | Managing disconnected investigations | |
US6108686A (en) | Agent-based on-line information retrieval and viewing system | |
US6748385B1 (en) | Dynamic insertion and updating of hypertext links for internet servers | |
US5946687A (en) | Geo-enabled personal information manager | |
US6859217B2 (en) | System and method to display and manage data within hierarchies and polyarchies of information | |
US6581065B1 (en) | Dynamic insertion and updating of hypertext links for internet servers | |
US7016853B1 (en) | Method and system for resume storage and retrieval | |
US20020027567A1 (en) | Listing network for classified information | |
US20080134042A1 (en) | Qkd System Wth Ambiguous Control | |
Scavo | World Wide Web site design and use in public management | |
US20060059225A1 (en) | Methods and apparatus for automatic generation of recommended links | |
US20050273702A1 (en) | Creation and management of common interest community web sites | |
US20030110106A1 (en) | System and method for enabling content providers in a financial services organization to self-publish content | |
US7120628B1 (en) | System and method for enabling a user to subscribe to updates from information sources | |
US20020087678A1 (en) | Intelligent management of information in a network environment | |
US20040111387A1 (en) | Methods and systems for organizing information stored within a computer network-based system | |
US20040210468A1 (en) | System and method for providing a territory management tool | |
JP4146101B2 (en) | Knowledge accumulation support system and public summary providing method in the same system |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: INTERNATIONAL BUSINESS MACHINES CORPORATION, NEW Y Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:EDLUND, STEFAN B;FORD, DANIEL ALEXANDER;RUVOLO, JOANN;REEL/FRAME:020000/0105;SIGNING DATES FROM 20000310 TO 20000313 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO PAY ISSUE FEE |
|
AS | Assignment |
Owner name: DAEDALUS GROUP LLC, NEW YORK Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:INTERNATIONAL BUSINESS MACHINES CORPORATION;REEL/FRAME:051032/0784 Effective date: 20190930 |
|
AS | Assignment |
Owner name: DAEDALUS GROUP, LLC, NEW YORK Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:INTERNATIONAL BUSINESS MACHINES CORPORATION;REEL/FRAME:051710/0445 Effective date: 20191230 |
|
AS | Assignment |
Owner name: DAEDALUS BLUE LLC, NEW YORK Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:DAEDALUS GROUP, LLC;REEL/FRAME:051737/0191 Effective date: 20200128 |
|
AS | Assignment |
Owner name: TERRACE LICENSING LLC, TEXAS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:DAEDALUS BLUE LLC;REEL/FRAME:059209/0046 Effective date: 20211129 |