CN101145223A - Calendar supervision system and its supervision method - Google Patents

Calendar supervision system and its supervision method Download PDF

Info

Publication number
CN101145223A
CN101145223A CNA2007101517299A CN200710151729A CN101145223A CN 101145223 A CN101145223 A CN 101145223A CN A2007101517299 A CNA2007101517299 A CN A2007101517299A CN 200710151729 A CN200710151729 A CN 200710151729A CN 101145223 A CN101145223 A CN 101145223A
Authority
CN
China
Prior art keywords
calendar
client
server
subscribe request
user
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.)
Pending
Application number
CNA2007101517299A
Other languages
Chinese (zh)
Inventor
黎巍
吴波
严峻
刘方敏
丁千
罗登
窦枫
刘忠林
高舜东
黄志华
何卫星
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.)
Tencent Technology Shenzhen Co Ltd
Original Assignee
Tencent Technology Shenzhen Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Tencent Technology Shenzhen Co Ltd filed Critical Tencent Technology Shenzhen Co Ltd
Priority to CNA2007101517299A priority Critical patent/CN101145223A/en
Publication of CN101145223A publication Critical patent/CN101145223A/en
Pending legal-status Critical Current

Links

Images

Abstract

The invention provides a calendar management system, which comprises a client and a calendar server, wherein the client sends out a customizing requirement which includes a client sign and a customizing proposal to the calendar server; the calendar server is used for storing and/or managing the calendar, receiving the customizing requirement of the client and feeding back the result information and/or the calendar to the client for treatment and storage. The invention also provides a calendar management method. The calendar management system and the calendar management method provided by the invention provide a calendar subscribing mechanism, wherein the calendar server publishes calendar information for users to subscribe calendars. When the calendars change, the user of the calendar reads a renewed one; when a calendar is subscribed by a plurality of users, the same data can be seen and can be renovated synchronously, so the invention facilitates a plurality of users to make uniform agenda arrangement and has the advantages of convenient use, high flexibility and performance.

Description

Calendar management system and management method
Technical field
The present invention relates to electric digital data processing field, particularly calendar management system and management method.
Background technology
The facility that the fast development of existing network infotech provides information to compile in a large number and propagate, retrieve and consult.Calendar software is the computer software of tissue and displaying calendar, incident and schedule, generally be isolated operation on user's computer, consult date, record, revise and consult calendar informations such as incident and schedule for the user.When the user uses other computing machines, can't check or use the calendar information on the former computing machine, and be not easy to check the ready-made schedule of other users.Existing calendar software is that the calendar that is stored in server is operated, but does not store calendar data in the user's computer.This calendar software is subjected to the restriction of network speed, and efficiency ratio is lower; And when network disconnects, the calendar data that the user can't the access server end.
Summary of the invention
The invention provides a kind of calendar management system and management method, make the user subscribe to the calendar of being issued by network.
The invention provides a kind of calendar management system, comprising: client and Calendar server, client is sent subscribe request to Calendar server, and subscribe request comprises client identification and subscription scheme; Calendar server is used for storage and/or management calendar, receives the subscribe request of client, and to client feedback object information and/or calendar, this object information and/or calendar are by client process and storage.
Above-mentioned client comprises: interface unit, realize and the Calendar server swap data; Storage unit, event memory information and/or calendar; Processing unit, control interface unit and storage unit work respectively generates subscribe request and processing result information and/or calendar; Processing unit forms subscribe request according to user instruction, sends to Calendar server by interface unit; Interface unit receives the object information and/or the calendar of Calendar server feedback, sends to processing unit; Processing unit is to user's return results information and/or calendar, and calendar is sent to cell stores.
Above-mentioned Calendar server comprises: memory module, store at least one calendar; Communication module is connected with client by network, realizes Calendar server and client exchange data; Processing module, control store module and communication module work respectively, the management calendar, the response subscribe request also generates object information; Communication module receives the subscribe request that client is sent by network, sends to processing module; Processing module is extracted from memory module according to subscribe request and is specified calendar and/or form object information, and object information and/or calendar are sent to communication module, feeds back to client by communication module.
The present invention also provides a kind of calendar management method, realizes calendar management based on Calendar server and client, and Calendar server storage and/or management calendar provide calendar to subscribe to; Client is connected with Calendar server, subscribes to calendar to Calendar server, and comprising: client is sent the step of subscribe request to Calendar server; Calendar server sends the step of calendar to client; Client receives and/or manages the step of calendar.
Above-mentioned step from subscribe request to Calendar server that send comprises: client provides the step that can subscribe to calendar to the user; Client forms the step of subscribe request according to user instruction; Client sends the step of subscribe request to Calendar server.
Above-mentioned step to client transmission calendar comprises: Calendar server receives the step of subscribe request; Calendar server is revised the step of calendar according to subscribe request; Calendar server sends to calendar the step of the client that proposes subscribe request.
The step of above-mentioned reception and/or management calendar comprises: client receives the step of calendar; Client is returned the step of calendar to the user; The step of the calendar that client stores and/or administrative institute receive.
Above-mentioned calendar management method also comprises: the step of the calendar of Calendar server storage and/or management update; Calendar server sends the step of update notification to the client of subscribing to calendar; Client is upgraded the step of calendar according to update notification.
Calendar management system provided by the invention and management method provide the calendar subscribing mechanism, and Calendar server issue calendar information is subscribed to calendar for the user.When calendar changed, the calendar that the user sees was what to upgrade; When a plurality of users subscribed to same calendar, what a plurality of users saw was that same data also can be upgraded synchronously, and the unified schedules of arranging of convenient a plurality of users are easy to use, flexible and efficient.
Description of drawings
Fig. 1 is the system architecture synoptic diagram of first embodiment of the invention;
Fig. 2 is the structural representation of first embodiment of the invention Calendar server;
Fig. 3 is the structural representation of first embodiment of the invention client;
Fig. 4 is the structural representation of second embodiment of the invention client;
Fig. 5 is the system architecture synoptic diagram of third embodiment of the invention.
The realization of the object of the invention, functional characteristics and advantage will be in conjunction with the embodiments, are described further with reference to accompanying drawing.
Embodiment
Fig. 1 illustrates the system architecture synoptic diagram of first embodiment of the invention.The calendar management system of present embodiment comprises client and Calendar server, and client is sent subscribe request to Calendar server, and subscribe request comprises client identification and subscription scheme; Calendar server is used for storage and/or management calendar, receives the subscribe request of client, and to client feedback object information and/or calendar, this object information and/or calendar are by client process and storage.
In conjunction with 20 structural representations of the Calendar server shown in Fig. 2, Calendar server 20 comprises memory module 201, stores at least one calendar; Communication module 203 is connected with client 10 by network, realizes Calendar server 20 and client 10 swap datas and information; Processing module 202, control store module 201 and communication module 203 work respectively, the management calendar, the response subscribe request also generates object information.Communication module 203 receives the subscribe request that client 10 is sent from network, sends to processing module 202; Processing module 202 is extracted from memory module 201 according to subscribe request and is specified calendar and/or form object information, and object information and/or calendar are sent to communication module 203, feeds back to client 10 by communication module 203.
Above-mentioned network is internet, LAN (Local Area Network) and/or private line network.
The information that client 10 is sent to Calendar server 20 is referred to as subscribe request, subscribe request comprises subscription scheme, subscription scheme has inquiry, subscribes to, quits the subscription of three kinds, and Calendar server 20 is carried out corresponding operating according to subscription scheme: subscription scheme for " inquiry " then Calendar server 20 inquire about and can subscribe to calendar; Subscription scheme then will specify calendar to issue client for " subscription "; Subscription scheme is then cancelled 10 pairs of subscription of specifying calendar of client for " quitting the subscription of "; For searching the appointment calendar, subscribe request comprises that also calendar information is to specify calendar.
And Calendar server 20 is sent object information and/or calendar to client 10, object information is used for the operating result to client 10 notice subscribe request, sending calendar is Calendar server 20 response " subscription " subscription scheme, specifies the information of calendar and incident to send to client 10 subscribe request.
At Calendar server 20 ends, present embodiment adopts the management of database realization to calendar.Specifically, in memory module 201 calendar database is set, this calendar database comprises calendar information table and calendar event table, and the information of a calendar is recorded in the calendar information table; Calendar can comprise a plurality of incidents, and the logout of calendar is in the calendar event table, and is related with this calendar by calendar ID.With reference to table 1, the calendar information table comprises " calendar ID ", " title ", " classification ", " founder ID ", " zero-time ", " termination time ", " issued state ", " authority ", " booking reader ", " update mode " and fields such as " lastest imformations ".The ID of the unique identification calendar that distributes of " calendar ID " field record database wherein; " title " field record calendar title, for example " work program in June " or " activity schedule in July "; The classification of " classification " field record calendar, for example " operation class " or " leisure "; " founder ID " field record is created the user ID of calendar; Zero-time and termination time that " zero-time " and " termination time " field writes down calendar respectively; Whether " issued state " field record calendar is open to other users, allows other users to subscribe to; The authority that " authority " field record calendar is subscribed to, comprise readable, can write, read-write and whether busy check only; " booking reader " field record is subscribed to the user ID tabulation of this calendar; The mode that " update mode " field record calendar upgrades comprises manual renewal or renewal automatically; " lastest imformation " field record last update date.
Calendar ID Title Classification Founder ID Zero-time Termination time Issued state Authority The booking reader Update mode Lastest imformation
…… …… …… …… …… …… …… …… …… …… ……
Table 1
With reference to table 2, the calendar event table comprises " calendar ID ", " event id ", " incident ", " circulation sign ", " zero-time " and " termination time " field.The value of " calendar ID " field is consistent with corresponding " calendar ID " field in the calendar information table; The ID of the unique identification incident that " event id " field record database distributes; The concrete incident of " incident " field record; The information that " circulation sign " field record incident regularly takes place, for example 1 year 1 time; " zero-time " and " termination time " field is the zero-time and the termination time of recording events respectively
Calendar ID Event id Incident The circulation sign Zero-time Termination time
…… …… …… …… …… ……
Table 2
In the above-mentioned calendar information table, " founder ID " reaches the ID that " booking reader " field record is used the calendar management system user of present embodiment, and this user can be the user in the calendar management system registry.The Calendar server 20 of present embodiment can be provided with user management mechanism, realizes that the user registers ID and to the management of user ID, and user ID and calendar are connected.
In the calendar information table, " issued state " field is definite or definite automatically by the calendar management system by the founder of this calendar of issue, indicates whether this calendar allows to be subscribed to by other users.If this field value is " disclosing ", then allow other users to subscribe to this calendar; If this field value is " underground ", then other users can't subscribe to this calendar." issued state " field and " authority " field are determined the subscription authority of user to announced calendar jointly.If this field value is " disclosing ", then allow other users to subscribe to this calendar; If this field value is " underground ", then other users can't subscribe to this calendar; The authority that the booking reader subscribes to according to the calendar of " authority " fields specify, carry out readable, can write, read-write and check the subscription of different rights such as whether busy only.
" zero-time " in the calendar information table, " termination time " and " update mode " field are in conjunction with determining whether calendar is effective, for example current date is considered as losing efficacy above the calendar of " date of expiry ", the inefficacy calendar is removed automatically by Calendar server 20, and this calendar will no longer be accepted subscription; Also can keep by the user of this calendar of issue or remove; Or accept user's subscription as historical calendar.
The groundwork flow process of the Calendar server 20 of present embodiment is as follows:
Step S11: communication module 203 is sent can be for the information of subscribing to calendar;
Step S12: the subscribe request that communication module 203 receives from client 10;
Step S13: processing module 202 is revised calendar information according to subscribe request visit memory module 201;
Step S14: communication module 203 is returned calendar and/or object information to client 10.
Specifically, above-mentioned steps S11 comprises:
Step S111: the subscribe request that communication module 203 receives from client 10, this subscribe request comprises subscription scheme and querying condition, and wherein subscription scheme is " inquiry ", is used for inquiry and can subscribes to calendar; Querying condition comprise founder ID, calendar title, classification, zero-time, termination time, lastest imformation etc. one or more;
Step S112: processing module 202 is found out the calendar of " issued state " field value for " disclosing " from the calendar information table of memory module 201, and this calendar is that the user who formulates calendar has issued and allowed other users' subscription;
Step S113: processing module 202 forms object information, and object information comprises " calendar ID ", " title ", " classification ", " founder ID ", " zero-time ", " termination time ", " authority " and the calendar informations such as " lastest imformations " that can subscribe to calendar;
Step S114: communication module 203 is returned the object information that step S113 generates to the client 10 of sending subscribe request.
Above-mentioned steps S12: the subscribe request that communication module 203 receives from client 10 specifically is the subscribe request that communication module 203 receives from client 10, subscribe request is sent to processing module 202 handle.Subscribe request comprises calendar information and subscription scheme, and subscription scheme comprises two kinds of " subscription ", " quitting the subscription of ", and calendar information comprises " calendar ID ", " booking reader ID " etc.
Above-mentioned steps S13: processing module 202 is revised calendar information according to subscribe request visit memory module 201, specifically is meant processing module 202 according to the subscribe request from client 10, the value of " booking reader " field of corresponding calendar in the modification calendar information table.Specifically, subscribe to certain calendar, then in the calendar information table, add the user ID of sending subscribe request in " booking reader " field of corresponding calendar if the subscription scheme that comprises in the subscribe request is requirement; Quit the subscription of certain calendar if the subscription scheme that comprises in the subscribe request is requirement, then from the calendar information table, delete the user ID of sending subscribe request in " booking reader " field of corresponding calendar; According to the implementation status of above-mentioned modification calendar information operation, form the object information of " subscribe request is accepted " or " subscribe request is rejected, customized failure ".
Above-mentioned steps S14 is a Calendar server 20 according to from the subscribe request of client 10 feedback procedure to client 10 specifically.Specifically, if being requirement, the subscription scheme that comprises in the subscribe request subscribes to certain calendar, then from memory module 201, extract customer requirements Subscribed calendar (information and all incidents that comprise this calendar), send to the client 10 that proposes subscribe request by communication module 203; Or according to the object information of the implementation status of revising the calendar information operation among the step S1 3 to client 10 transmissions " subscribe request is accepted " or " subscribe request is rejected, customized failure ".
The structural representation of client 10 as shown in Figure 3, client 10 runs on user's computer, comprises interface unit 101, realizes and Calendar server 20 swap datas; Storage unit 103, event memory information and/or calendar; Processing unit 102, control interface unit 101 and storage unit 103 work generate subscribe request and processing result information and/or calendar respectively; Processing unit 102 forms subscribe request according to user instruction, sends to Calendar server 20 by interface unit 101; Interface unit 101 receives the object information and/or the calendar of Calendar server 20 feedbacks, sends to processing unit 102; Processing unit 102 is to user's return results information and/or calendar, and calendar is sent to storage unit 103 storages.
In client 10, present embodiment adopts the management of database realization to calendar.Specifically, the subscription calendar database is set in storage unit 103, this subscription calendar database comprises to be subscribed to the calendar information table and subscribes to the calendar event table, and a calendar can comprise a plurality of incidents, and the information of calendar is recorded in subscribes in the calendar information table; The logout of this calendar is in subscribing to the calendar event table, and is related with this calendar by calendar ID.
The example of subscribing to the calendar information table is as shown in table 3, comprise " calendar ID ", " title ", " classification ", " founder ID ", " zero-time ", " termination time ", " authority ", " lastest imformation " and fields such as " subscription status ", wherein the value of " calendar ID ", " title ", " classification ", " founder ID ", " zero-time ", " termination time ", " authority ", " lastest imformation " field is consistent with respective record in the calendar information table of Calendar server 20 respectively; And " subscription status " field indicates that the user subscribes to the state of this calendar, and its value can be " subscribing to ", " not subscribing to " or " quitting the subscription of ", wherein " subscribes to " the expression user and has subscribed to this calendar; " do not subscribe to " the expression user and never subscribed to this calendar; " quit the subscription of " expression user once subscribed to this calendar, after quit the subscription of again.
Calendar ID Title Classification Founder ID Zero-time Termination time Authority Lastest imformation Subscription status
…… …… …… …… …… …… …… …… ……
Table 3
With reference to table 4, subscribe to the calendar event table and comprise " calendar ID ", " event id ", " incident ", " circulation sign ", " zero-time " and " termination time " field, the value of these fields is consistent with respective record in the calendar event table of Calendar server 20 respectively.
Calendar ID Event id Incident The circulation sign Zero-time Termination time
…… …… …… …… …… ……
Table 4
The client 10 of present embodiment is the client-side program of installing and operating on the subscriber computer, also can be the program that runs in the subscriber computer browser, and the user can be connected to Calendar server 20 from browser, realizes that calendar is customized.
The workflow of the client 10 of present embodiment comprises:
Step S21: client 10 is sent subscribe request to Calendar server 20;
Step S22: client 10 receives calendar and/or object information;
Step S23: client 10 management calendars.
Above-mentioned steps S21 comprises:
Step S211: processing unit 102 forms subscribe request according to the condition of user's appointment; This subscribe request comprises subscription scheme and querying condition, and wherein subscription scheme is " inquiry ", is used for inquiry and can subscribes to calendar; Querying condition comprise founder ID, calendar title, classification, zero-time, termination time, lastest imformation etc. one or more;
Step S212: interface unit 101 sends the subscribe request that step S211 forms to Calendar server 20;
Step S213: provide calendar information to the user, the calendar information subscribed to that will receive is shown to the user on the one hand, and the user can select to subscribe to one or more calendar; The calendar information that to subscribe in the calendar information table is shown to the user on the other hand, and for the calendar of wherein quitting the subscription of, the user can select to subscribe to one or more calendar; For one or more calendars of having subscribed to, the user can select to quit the subscription of; The object information that Calendar server 20 is returned can also be shown to the user;
Step S214: form subscribe request according to user instruction; Specific practice is according to the user subscription scheme of the selection that can subscribe to calendar and user's appointment to be formed subscribe request; Subscribe request comprises calendar information and subscription scheme, and wherein calendar information comprises calendar informations such as " calendar ID ", " booking reader ID "; Subscription scheme comprises " subscription " or " quitting the subscription of " two kinds;
Step S215: the subscribe request that forms to Calendar server 20 forwarding step S214 by interface unit 101.
Above-mentioned steps S22 comprises:
Step S221: receive calendar and/or the object information that Calendar server 20 is sent by interface unit 101;
Step S222: return calendar and/or the object information that receives to the user.
Above-mentioned steps S23 specifically is the calendar stores that will receive at the subscription calendar information table of storage unit 103 and subscribes in the calendar event table.
Workflow in conjunction with above-mentioned Calendar server 20 and client 10, present embodiment proposes to upgrade calendar mechanism, realize when the founder upgrades calendar or calendar and changes, subscribing to the calendar of the client 10 of this calendar from Calendar server 20 automatic receptions renewal.For realizing update mechanism, present embodiment proposes update notification, and Calendar server 20 is sent update notification to having subscribed to the user client of upgrading calendar, and whether client accepts renewal according to this update notification decision, then returns subscribe request if accept to upgrade.Subscription scheme in the present embodiment definition subscribe request is " renewal ", when calendar server 20 receives the subscribe request that comprises " renewal " subscription scheme, finds out the calendar of the renewal that this user subscribed to and sends to client 10.
The flow process of upgrading calendar comprises:
Step S31: the calendar of Calendar server 20 storages and/or management update;
Step S32: Calendar server 20 sends update notification to the client 10 of subscribing to calendar;
Step S33: client 10 is upgraded calendar according to update notification.
Above-mentioned renewal calendar or calendar change and comprise that increase, deletion, modification incident, one or more calendar informations change, situations such as the expired or inefficacy of calendar, and Calendar server is revised corresponding lastest imformation according to the date that above-mentioned variation takes place.
Wherein, step S31 comprises:
Step S311: Calendar server 20 ends upgrade calendar or the calendar situation that changes according to the founder and revise corresponding information in the calendar database;
Step S312: processing module 202 obtains all user ID of subscribing to this calendar from " booking reader " field of upgrading the calendar correspondence.
Above-mentioned steps S32 comprises:
Step S321: processing module 202 forms update notification, and update notification comprises calendar informations such as " the calendar ID " that upgrade calendar, " booking reader ID ";
Step S322: communication module 203 is sent update notification to the client 10 of all user ID of subscribing to this calendar.
Above-mentioned steps S33 comprises:
Step S331: interface unit 101 receives update notification, is transmitted to processing unit 102;
Step S332: processing unit 102 forms subscribe request, sends to Calendar server 20 by interface unit 101; Subscribe request comprises subscription scheme and calendar information, and wherein subscription scheme is " renewal ", and calendar information comprises " booking reader ID " information;
Step S333: Calendar server 20 is extracted the calendar of all renewals of booking reader's subscription, sends to the interface unit 101 of client 10;
Step S334: the renewal calendar that client 10 storages and/or administrative institute receive, specific practice is the value and the identical record of renewal calendar of searching " calendar ID " field in subscribing to the calendar information table, if find the value and the identical record of renewal calendar of " calendar ID " field, then substitute original calendar information in the subscription calendar information table, substitute the incident of subscribing to original calendar in the calendar event table with the incident of upgrading calendar to upgrade calendar information; If do not find the value and the identical record of renewal calendar of " calendar ID " field, then the renewal calendar is added to subscribe to forming a new record in the calendar information table, the incident of upgrading calendar is added to subscribe in the calendar event table, set up related with the renewal calendar.
The calendar management system that uses present embodiment to provide, can realize subscribing to work schedule, notice of meeting, the activity schedule of personal user's issue, friend's schedule etc., can also subscribe to by multiple information such as the preview of trade company or mechanism's issue, market activity notification, favor information, stock markets.
On the foregoing description basis, the present invention proposes second embodiment.Present embodiment comprises client 11 and Calendar server 20, and client 11 is sent subscribe request to Calendar server 20, and subscribe request comprises client identification and subscription scheme; Calendar server 20 is used for storage and/or management calendar, receives the subscribe request of client 11, and to client 11 feedback result information and/or calendars, this object information and/or calendar are handled and storage by client 11.The structure of present embodiment Calendar server 20 and the course of work and first embodiment are similar, so do not give unnecessary details.
Fig. 4 illustrates the client terminal structure synoptic diagram of present embodiment.Client 11 comprises interface unit 111, realizes and Calendar server 20 swap datas; Storage unit 113, event memory information and/or calendar; Processing unit 112, control interface unit 111 and storage unit 113 work generate subscribe request and processing result information and/or calendar; The structure and the course of work of interface unit 111, processing unit 112 and storage unit 113, and the data structure and first embodiment of calendar, incident are similar, so do not give unnecessary details.
The client 11 of present embodiment also comprises notification unit 114, Active Desktop Calendar unit 115, main boundary element 116, temporal logic unit 117, software development kit 118 and/or Instant Messenger (IM) software run-time library 119.
Wherein, notification unit 114 is accepted the control of processing unit 112, sends the alert notification that expires to the user.Specifically, processing unit 112 is according to the subscription calendar information table and the subscription calendar event table of storage unit 113 storages, monitoring " circulation sign ", " zero-time " and fields such as " termination times ", be about to expire as incident, when needing to remind the user, processing unit 112 control notification units 114 send the alert notification that expires of this incident to the user, and the alert notification that expires comprises information and this incident and contents such as circulation sign, zero-time and termination time thereof such as the calendar title, classification, founder ID of incident place calendar.
The control of processing unit 112 is accepted in Active Desktop Calendar unit 115, is presented at the mini small interface on the subscriber computer desktop, is used for to the simple information of user's displaying calendar and/or the alert notification that expires.
Main boundary element 116 is large interfaces of telotism, for client 11 and user interactions, according to the control of processing unit 112, receives the instruction that the user sends, and to user's return results information and/or calendar.
Temporal logic unit 117, the zero-time of " zero-time ", " termination time " and the incident of judgement calendar " and " termination time " equal time condition, call for processing unit 112.
Software development kit 118 is SDK (Software Developers Kit).
Instant Messenger (IM) software run-time library 118 as with the interface of other Account Administration systems, accept the control of processing unit 112, call other Account Administration systems, realize calling to other Account Administration systemic-functions.
The client 11 of present embodiment also provides the data manipulation function of subscribing to calendar database.For example, the user uses locating function, finds out and subscribes to the calendar that has exceeded the term of validity in the calendar information table, carries out customized to it; Perhaps find out and delete the calendar of having quit the subscription of, deletion action will be deleted this calendar from subscribe to the calendar information table, simultaneously all incidents of this calendar of deletion from subscribe to the calendar event table; Similarly, the user can search subscribing to incident in the calendar event table, deletion action.
The calendar management system that the foregoing description provides, can realize basic calendar management and subscription, but because Calendar server 20 structures and subscribing mechanism are comparatively simple, the user uses still many inconvenience, also can't adapt to the management and the subscription demand of a large amount of calendars.
For further improving the calendar management ability of native system, user-friendly, the present invention proposes the 3rd embodiment, and system architecture as shown in Figure 5.
Present embodiment comprises client 12, handheld terminal 13 and Calendar server 21, Calendar server 21 comprises calendar child servers group 210, the webserver 211, cluster server 212 and wireless server 213, can also comprise information server 214 and/or other servers 215.
The user uses client 12 to be connected with calendar child servers group 210 with cluster server 212 by the webserver 211 respectively; The user uses handheld terminal 13 to be connected with calendar child servers group 210 with cluster server 212 by wireless server 213.Calendar child servers group 210 comprises a plurality of child servers, the first calendar management server 2101, the second calendar management server 2102,3-calendar management server 2103 and interface child servers 2104 interconnect as shown in Figure 5, be connected with cluster server 212 and swap data by interface child servers 2104, also can be connected and swap data with information server 214 and/or other servers 215.
Calendar server 21 in the present embodiment, the webserver 211, cluster server 212, wireless server 213, calendar child servers group 210, interface child servers 2104, information server 214 and/or other servers 215 can be station servers, also can form, all adopt existing server technology by multiple servers.
The background program of the Calendar server 21 in the present embodiment comprises an interface service process and several calendar management service processess.Interface child servers 2104 runnable interface service processess wherein, be responsible for the access service of calendar management and event action, and then calendar management and incident are distributed to the first calendar management server 2101, the second calendar management server 2102 and/or 2103 processing of 3-calendar management server.And a plurality of calendar management servers are divided by calendar database, move the calendar management service processes respectively, independently are responsible for carrying out the bookkeeping and the data storage operations of part calendar database, comprise that calendar is newly-built, modification, deletion etc.
Above-mentioned client 12 or handheld terminal 13 realize that according to TCP and/or udp protocol communication network is connected with Calendar server 21 and child servers thereof, and network is internet, wireless communication networks, LAN (Local Area Network) and/or private line network.
Client 12 in the present embodiment or handheld terminal 13 adopt multiple client, browser or handheld terminal technology to realize, it is similar to form the structure and the course of work and previous embodiment, so do not give unnecessary details.
The client 12 of present embodiment is the client-side program of installing and operating on the subscriber computer, it also can be the program that runs in the subscriber computer browser, the user can be connected to Calendar server 21 from browser and search and subscribe to calendar, and idiographic flow and previous embodiment are similar, so do not give unnecessary details.And handheld terminal 13 operates in user's wireless telecommunications system or the client-side program on the wireless data treating apparatus, it also can be the program that operates on the browser of wireless telecommunications system or wireless data treating apparatus, the user can be connected to Calendar server 21 from browser and search and subscribe to calendar, idiographic flow and previous embodiment are similar, so do not give unnecessary details.
The user of present embodiment can be the user in the calendar management system registry of present embodiment, also can be the user of other number of the account management systems.The Calendar server 20 of present embodiment can be provided with user management mechanism, realizes that the user registers ID and to the management of user ID, and user ID and calendar are connected; Also can not carry out the management of user ID, but cooperate, user ID and the calendar of user in other Account Administration systems connected with other Account Administration systems.Above-mentioned other Account Administration systems can be instant communicating systems, also can be mailing systems.The user can use own account number in other Account Administration systems to sign in to other Account Administration systems, thereby being key word, account number that can other Account Administration systems in the calendar management system of present embodiment, searches the calendar of own interested account number issue, send the subscribe request of the account number that comprises oneself, Calendar server 21 will provide the subscription calendar service for the user according to account.
Client 12 or handheld terminal 13 can comprise the Instant Messenger (IM) software run-time library, this Instant Messenger (IM) software run-time library as with the interface of other Account Administration systems, can call other Account Administration systems, to realize calling to other Account Administration systemic-functions.
Present embodiment is also expanded subscription scheme, and the User Defined subscription scheme is provided, and forms subscribe request according to the calendar of user's selection and the self-defined subscription scheme of appointment, and Calendar server 21 provides calendar to subscribe to according to subscribe request.
Subscribe request and aforementioned subscribe request are similar, comprise calendar informations such as " calendar ID ", " booking reader ID ", the subscription scheme that also comprises self-defined kind, this subscription scheme except that comprise aforementioned subscription, quit the subscription of, the kind such as renewal, can also comprise regular subscription, according to certain condition subscribe to or quit the subscription of, subscribe to similar calendar, subscribe to certain user calendar, subscribe to historical calendar, in certain time limit, subscribe to or quit the subscription of etc. one or more, be referred to as self-defined.Client 12 or handheld terminal 13 are issued Calendar server 21 with subscribe request, Calendar server 21 audits subscription scheme wherein, the object information of formation " subscribe request is accepted " or " subscribe request is rejected, customized failure "; If receive this subscribe request, then subscription scheme is managed, set up the calendar of subscription scheme and appointment and the corresponding relation between the user ID, be convenient to send calendar according to subscription scheme to user client 12 or handheld terminal 13 automatically.
The calendar management system that uses present embodiment to provide, can realize the subscription of a plurality of users to a large amount of calendars, the user can subscribe to work schedule, notice of meeting, the activity schedule of personal user issue, friend's schedule etc. on wireless telecommunications system or wireless data treating apparatus, can also subscribe to by multiple information such as the preview of trade company or mechanism's issue, market activity notification, favor information, stock markets.The user can self-defined subscription scheme, and the calendar management system that present embodiment provides provides the subscription of calendar according to self-defined subscription scheme, is very easy to the user, has realized dirigibility and practicality that calendar is subscribed to.
Below propose the 4th embodiment, specify calendar management of the present invention system.The system architecture of present embodiment and the 3rd embodiment are similar, comprise a plurality of users' a plurality of clients 12, handheld terminal 13 and Calendar server 21.Wherein user A is the ad distribution merchant, and user B is a commercial audience.User A and user B can be the users in the calendar management system registry of present embodiment, also can be the users of other Account Administration systems.
User A is by client 12 and Calendar server 21 issue calendars, the content of calendar be certain period cinema the motion picture projection advance notice, corresponding calendar is categorized as " movie news ".The film information that the calendar information record will be shown, the example of calendar information table is as shown in table 5:
Calendar ID Title Classification Founder ID Zero-time Termination time Issued state Authority The booking reader Update mode Lastest imformation
1 The god of war Movie news A 2007-8-10 2007-9-10 Open Readable Manually 2007-08-08
2 The superman Movie news A 2007-8-10 2007-8-10 Open Readable Manually 2007-08-08
Table 5
The concrete projection arrangement of record in the calendar event table, the example of calendar event table is as shown in table 6:
Calendar ID Event id Incident The circulation sign Zero-time Termination time
1 01 Morning show (No. 1 Room) Only 1 time 10:10 12:00
1 02 Noon field (No. 2 Rooms) Only 1 time 12:10 14:00
1 03 Evening show (No. 5 Rooms) Only 1 time 19:10 21:00
1 02 Late show (No. 3 Rooms) Only 1 time 23:10 01:00
2 01 Field in afternoon (No. 2 Rooms) Only 1 time 14:10 16:00
2 02 Evening show (No. 3 Rooms) Only 1 time 19:10 21:00
2 03 Late show (No. 4 Rooms) Only 1 time 20:10 24:00
Table 6
User B sends subscribe request by handheld terminal 13 to Calendar server 21, calendar to Calendar server 21 inquiry " movie news " classes, Calendar server 21 returns to the handheld terminal 13 of user B with the calendar information that finds, comprising the calendar as shown in table 5 of user A issue.User B selects the calendar of user A issue, send subscribe request to Calendar server 21, Calendar server 21 " booking reader " field of corresponding calendar information in the calendar information table adds the account number of access customer B, and calendar and incident thereof is sent to the handheld terminal 13 of user B.13 pairs of calendars that receive of the handheld terminal of user B manage, and form subscription calendar information table as shown in table 7:
Calendar ID Title Classification Founder ID Zero-time Termination time Authority Lastest imformation Subscription status
1 The god of war Movie news A 2007-8-10 2007-9-10 Open Readable Subscribe to
Table 7
The handheld terminal 13 of user B forms subscription calendar event table as shown in table 8:
Calendar ID Event id Incident The circulation sign Zero-time Termination time
1 01 Morning show (No. 1 Room) Only 1 time 10:10 12:00
1 02 Noon field (No. 2 Rooms) Only 1 time 12:10 14:00
1 03 Evening show (No. 5 Rooms) Only 1 time 19:10 21:00
1 02 Late show (No. 3 Rooms) Only 1 time 23:10 01:00
2 01 Field in afternoon (No. 2 Rooms) Only 1 time 14:10 16:00
2 02 Evening show (No. 3 Rooms) Only 1 time 19:10 21:00
2 03 Late show (No. 4 Rooms) Only 1 time 20:10 24:00
Table 8
When the motion picture projection arrangement changed, user A upgraded this calendar, and Calendar server 21 is sent update notification to the user B that has subscribed to this calendar, and the handheld terminal 13 of user B forms subscribe request and sends to Calendar server 21 according to update notification; Calendar server 21 is extracted the calendar of this renewal, sends to the handheld terminal 13 of user B.Handheld terminal 13 storages of user B and/or the renewal calendar that administrative institute receives.
Present embodiment also provides the User Defined subscription scheme, forms subscribe request according to the calendar of user's selection and the self-defined subscription scheme of appointment, and Calendar server 21 provides calendar to subscribe to according to subscribe request.For example the subscription scheme of user B formulation is: " movie news " class calendar of every month booking reader A.The handheld terminal 13 of user B forms subscribe request in view of the above and issues Calendar server 21, Calendar server 21 audits subscription scheme wherein, the object information of formation " subscribe request is accepted " or " subscribe request is rejected, customized failure "; If receive this subscribe request, then subscription scheme is managed, set up the calendar of subscription scheme and appointment and the corresponding relation between the user B, send calendar according to subscription scheme to the handheld terminal 13 of user B automatically.
The present invention proposes the 5th embodiment, and a kind of calendar management method realizes calendar management based on client and Calendar server, comprising:
Step S41: client is sent subscribe request to Calendar server;
Step S42: Calendar server sends calendar to client;
Step S43: client receives and/or the management calendar.
Above-mentioned steps S41 comprises:
Step S411: client forms subscribe request according to the condition of user's appointment, and this subscribe request comprises subscription scheme and querying condition, and wherein subscription scheme is " inquiry ", is used for inquiry and can subscribes to calendar; Querying condition comprise founder ID, calendar title, classification, zero-time, termination time, lastest imformation etc. one or more;
Step S412: client is sent the subscribe request that step S411 forms to Calendar server;
Step S413: Calendar server is consulted and can be subscribed to calendar, and its information is returned to client;
Step S414: client provides the calendar information of the calendar subscribed to that inquires according to querying condition to the user; Specific practice is to receive and store and can subscribe to calendar information, and calendar information is shown to the user;
Step S415: client forms subscribe request according to user instruction; Specific practice is according to the user subscription scheme of the selection that can subscribe to calendar and appointment to be formed subscribe request; Subscribe request comprises calendar informations such as " calendar ID ", " booking reader ID ", also comprise subscription scheme, comprise subscription, quit the subscription of, regularly subscribe to certain calendar, according to certain condition subscribe to or quit the subscription of, subscribe to similar calendar, subscribe to certain user calendar, subscribe to historical calendar, in certain time limit, subscribe to or quit the subscription of etc. one or more;
Step S416: the subscribe request that client forms to Calendar server forwarding step S415.
Above-mentioned steps S42 comprises:
Step S421: Calendar server receives the subscribe request from client;
Step S422: Calendar server is revised calendar information according to subscribe request; Specifically be meant according to subscribe request, revise the value of " booking reader " field of corresponding calendar in the calendar information table.Subscribe to certain calendar if the subscription scheme that comprises in the subscribe request is requirement, then in " booking reader " field of corresponding calendar, add the user ID of sending subscribe request; Quit the subscription of certain calendar if the subscription scheme that comprises in the subscribe request is requirement, then from " booking reader " field, delete the user ID of sending subscribe request;
Step S423: Calendar server is returned calendar to client, specifically, is according to the subscribe request from client, extracts the customer requirements Subscribed calendar, sends to the client that proposes subscribe request.
Above-mentioned steps S43 comprises:
Step S431: client receives the calendar that Calendar server is sent;
Step S432: client is returned the calendar that receives to the user;
Step S433: the calendar that client stores and/or administrative institute receive specifically is that the calendar stores that will receive is being subscribed to the calendar information table and subscribed in the calendar event table.
Present embodiment also can adopt object information, and Calendar server returns to client according to the subscription operation result information of bearing results, and notifies the user by client.
Specifically, above-mentioned steps S422 also comprises the implementation status of Calendar server according to above-mentioned modification calendar information operation, forms the object information of " subscribe request is accepted " or " subscribe request is rejected, customized failure ".
And step S423 also comprises if revise the calendar information operation failure, and then Calendar server sends the object information of " subscribe request is accepted " or " subscribe request is rejected, customized failure " to client.
Correspondingly, above-mentioned steps S43 comprises:
Step S431: client receives calendar and/or the object information that Calendar server is sent;
Step S432: client is returned calendar and/or the object information that receives to the user;
Step S433: the calendar that client stores and/or administrative institute receive.
The present invention proposes the 6th embodiment, also comprises the step of upgrading calendar on the 5th embodiment basis, and when the user upgrades certain calendar, or certain calendar information subscribes to the client of this calendar and upgrade calendar from the Calendar server automatic reception when changing, and comprising:
Step S51: the calendar of Calendar server storage and/or management update;
Step S52: Calendar server sends update notification to the client of subscribing to calendar;
Step S53: client is upgraded calendar according to update notification.
Above-mentioned renewal calendar or calendar change and comprise that increase, deletion, modification incident, one or more calendar informations change, situations such as the expired or inefficacy of calendar, and Calendar server is revised corresponding lastest imformation according to the date that above-mentioned variation takes place.
Wherein, step S51 comprises:
Step S511: the Calendar server end upgrades certain calendar, revises the corresponding information in the calendar database;
Step S512: Calendar server obtains the user ID of subscribing to this calendar from " booking reader " field of upgrading the calendar correspondence.
Above-mentioned steps S52 comprises:
Step S521: Calendar server forms update notification, and content of announcement comprises calendar informations such as " the calendar ID " that upgrade calendar, " booking reader ID ";
Step S522: Calendar server is sent update notification to the subscription client of subscribing to this calendar.
Above-mentioned steps S53 comprises:
Step S531: client receives update notification;
Step S532: client forms subscribe request, sends to Calendar server; Subscribe request comprises subscription scheme and calendar information, and wherein subscription scheme is " renewal ", and calendar information comprises " booking reader ID " information;
Step S533: the calendar that Calendar server is extracted all renewals of booking reader's subscription sends to client;
Step S534: the calendar that client stores and/or administrative institute receive, specific practice is to subscribe to search " calendar ID " in the calendar information table and upgrade the identical record of calendar in client, if find the value and the identical record of renewal calendar of " calendar ID " field, then substitute original calendar information in the subscription calendar information table, substitute the incident of subscribing to original calendar in the calendar event table with the incident of upgrading calendar to upgrade calendar information; If do not find the value and the identical record of renewal calendar of " calendar ID " field, then the renewal calendar is added to subscribe to forming a new record in the calendar information table, the incident of upgrading calendar is added to subscribe in the calendar event table, set up related with the renewal calendar.
The above only is the preferred embodiments of the present invention; be not so limit claim of the present invention; every equivalent structure or equivalent flow process conversion that utilizes instructions of the present invention and accompanying drawing content to be done; or directly or indirectly be used in other relevant technical fields, all in like manner be included in the scope of patent protection of the present invention.

Claims (10)

1. calendar management system comprises: client and Calendar server, and described client is sent subscribe request to Calendar server, and described subscribe request comprises client identification and subscription scheme; Described Calendar server is used for storage and/or management calendar, receives the subscribe request of client, and to described client feedback object information and/or calendar, this object information and/or calendar are by described client process and storage.
2. calendar management according to claim 1 system is characterized in that described client comprises:
Interface unit is realized and the Calendar server swap data;
Storage unit, event memory information and/or calendar;
Processing unit, control interface unit and storage unit work respectively generates subscribe request and processing result information and/or calendar;
Described processing unit forms subscribe request according to user instruction, sends to Calendar server by interface unit; Described interface unit receives the object information and/or the calendar of described Calendar server feedback, sends to processing unit; Described processing unit is to user's return results information and/or calendar, and calendar is sent to described cell stores.
3. calendar management according to claim 2 system is characterized in that described client also comprises:
Notification unit is accepted the control of processing unit, according to the calendar of cell stores, sends the notice that expires and remind to the user.
4. according to any described calendar management system of claim 1 to 3, it is characterized in that described Calendar server comprises:
Memory module is stored at least one calendar;
Communication module is connected with described client by network, realizes Calendar server and described client exchange data;
Processing module, control store module and communication module work respectively, the management calendar, the response subscribe request also generates object information;
Described communication module receives the subscribe request that described client is sent by network, sends to described processing module; Processing module is extracted from memory module according to subscribe request and is specified calendar and/or form object information, and object information and/or calendar are sent to communication module, feeds back to described client by communication module.
5. a calendar management method realizes calendar management based on Calendar server and client, and described Calendar server storage and/or management calendar provide calendar to subscribe to; Described client is connected with described Calendar server, also comprises:
Client is sent the step of subscribe request to described Calendar server;
Calendar server sends the step of calendar to described client;
The step that client receives and/or manages described calendar.
6. calendar management method according to claim 5 is characterized in that:
Described subscribe request comprises subscription scheme, and described subscription scheme comprises inquiry, subscribes to, quits the subscription of, renewal and/or self-defined.
7. according to claim 5 or 6 described calendar management methods, it is characterized in that step from subscribe request to described Calendar server that send comprises:
Client provides the step that can subscribe to calendar to the user;
Client forms the step of subscribe request according to user instruction;
Client sends the step of described subscribe request to described Calendar server.
8. according to claim 5 or 6 described calendar management methods, it is characterized in that described step to client transmission calendar comprises:
Calendar server receives the step of subscribe request;
Calendar server is revised the step of calendar according to subscribe request;
Calendar server sends to calendar the step of the client that proposes subscribe request.
9. according to claim 5 or 6 described calendar management methods, it is characterized in that described reception and/or the step of managing described calendar comprise:
Client receives the step of described calendar;
Client is returned the step of described calendar to the user;
The step of the calendar that client stores and/or administrative institute receive.
10. according to claim 5 or 6 described calendar management methods, it is characterized in that, also comprise:
The step of the calendar of Calendar server storage and/or management update;
Calendar server sends the step of update notification to the client of subscribing to described calendar;
Client is upgraded the step of calendar according to described update notification.
CNA2007101517299A 2007-09-27 2007-09-27 Calendar supervision system and its supervision method Pending CN101145223A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CNA2007101517299A CN101145223A (en) 2007-09-27 2007-09-27 Calendar supervision system and its supervision method

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CNA2007101517299A CN101145223A (en) 2007-09-27 2007-09-27 Calendar supervision system and its supervision method

Publications (1)

Publication Number Publication Date
CN101145223A true CN101145223A (en) 2008-03-19

Family

ID=39207743

Family Applications (1)

Application Number Title Priority Date Filing Date
CNA2007101517299A Pending CN101145223A (en) 2007-09-27 2007-09-27 Calendar supervision system and its supervision method

Country Status (1)

Country Link
CN (1) CN101145223A (en)

Cited By (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101820448A (en) * 2009-02-27 2010-09-01 捷讯研究有限公司 The communication system of mobile device notification is provided based on personal interest information and calendar event
CN102045265A (en) * 2009-10-20 2011-05-04 爱思开电讯投资(中国)有限公司 Device and method for information interaction
CN104125305A (en) * 2014-08-13 2014-10-29 广州华多网络科技有限公司 Method and system for dynamic push of calendar information
CN104243559A (en) * 2014-08-29 2014-12-24 小米科技有限责任公司 Calendar information pushing method, device and system
CN105279637A (en) * 2015-09-28 2016-01-27 小米科技有限责任公司 Calendar information management method, device and system
CN105868232A (en) * 2015-12-01 2016-08-17 乐视体育文化产业发展(北京)有限公司 Method, device and system for concerning events in calendars
CN105868955A (en) * 2015-11-19 2016-08-17 乐视体育文化产业发展(北京)有限公司 Calendar event statistical method and device thereof
CN108768679A (en) * 2018-05-18 2018-11-06 栾德洋 A kind of method and computer readable storage medium for realizing that stroke is shared
CN110852694A (en) * 2019-09-27 2020-02-28 口碑(上海)信息技术有限公司 Calendar component processing method and system
WO2020231574A1 (en) * 2019-05-16 2020-11-19 Microsoft Technology Licensing, Llc Real time collaboration in calendar
US11061525B2 (en) 2019-05-16 2021-07-13 Microsoft Technology Licensing, Llc Digital map calendar user interface
US11151104B2 (en) 2019-05-16 2021-10-19 Microsoft Technology Licensing, Llc Time systems as data
CN115186198A (en) * 2022-09-09 2022-10-14 中国中金财富证券有限公司 Stock market quotation pushing method and related device
US11514405B1 (en) 2021-05-14 2022-11-29 Microsoft Technology Licensing, Llc Map calendar graphical user interface with dynamic time mold functionality
US11645628B2 (en) 2019-05-16 2023-05-09 Microsoft Technology Licensing, Llc Translation of time between calendar systems
US11681424B2 (en) 2021-05-14 2023-06-20 Microsoft Technology Licensing, Llc Map calendar graphical user interface with content-variable view levels

Cited By (21)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101820448A (en) * 2009-02-27 2010-09-01 捷讯研究有限公司 The communication system of mobile device notification is provided based on personal interest information and calendar event
CN102045265A (en) * 2009-10-20 2011-05-04 爱思开电讯投资(中国)有限公司 Device and method for information interaction
CN104125305A (en) * 2014-08-13 2014-10-29 广州华多网络科技有限公司 Method and system for dynamic push of calendar information
CN104243559A (en) * 2014-08-29 2014-12-24 小米科技有限责任公司 Calendar information pushing method, device and system
CN105279637A (en) * 2015-09-28 2016-01-27 小米科技有限责任公司 Calendar information management method, device and system
WO2017054359A1 (en) * 2015-09-28 2017-04-06 小米科技有限责任公司 Method, device and system for managing calendar information
CN105868955A (en) * 2015-11-19 2016-08-17 乐视体育文化产业发展(北京)有限公司 Calendar event statistical method and device thereof
WO2017084263A1 (en) * 2015-11-19 2017-05-26 乐视控股(北京)有限公司 Method and apparatus for collecting statistics on event in calendar
CN105868232A (en) * 2015-12-01 2016-08-17 乐视体育文化产业发展(北京)有限公司 Method, device and system for concerning events in calendars
WO2017092349A1 (en) * 2015-12-01 2017-06-08 乐视控股(北京)有限公司 Method, apparatus and system for event of interest in calendar
CN108768679A (en) * 2018-05-18 2018-11-06 栾德洋 A kind of method and computer readable storage medium for realizing that stroke is shared
CN108768679B (en) * 2018-05-18 2021-03-23 栾德洋 Method for realizing travel sharing and computer readable storage medium
WO2020231574A1 (en) * 2019-05-16 2020-11-19 Microsoft Technology Licensing, Llc Real time collaboration in calendar
US11061525B2 (en) 2019-05-16 2021-07-13 Microsoft Technology Licensing, Llc Digital map calendar user interface
US11120407B2 (en) 2019-05-16 2021-09-14 Microsoft Technology Licensing, Llc Real time collaboration in calendar
US11151104B2 (en) 2019-05-16 2021-10-19 Microsoft Technology Licensing, Llc Time systems as data
US11645628B2 (en) 2019-05-16 2023-05-09 Microsoft Technology Licensing, Llc Translation of time between calendar systems
CN110852694A (en) * 2019-09-27 2020-02-28 口碑(上海)信息技术有限公司 Calendar component processing method and system
US11514405B1 (en) 2021-05-14 2022-11-29 Microsoft Technology Licensing, Llc Map calendar graphical user interface with dynamic time mold functionality
US11681424B2 (en) 2021-05-14 2023-06-20 Microsoft Technology Licensing, Llc Map calendar graphical user interface with content-variable view levels
CN115186198A (en) * 2022-09-09 2022-10-14 中国中金财富证券有限公司 Stock market quotation pushing method and related device

Similar Documents

Publication Publication Date Title
CN101145223A (en) Calendar supervision system and its supervision method
CN101416178B (en) Managing rich presence collections
CN101416208B (en) The set on the scene of managing rich
CN101448247B (en) Updating data on a remote device
US9407707B2 (en) Method and apparatus for demographic-based reminders
JP3141943B2 (en) Data distribution methods and data structures
US7856498B2 (en) Collaborative alert management and monitoring
US7739345B2 (en) Alert notification engine
CN101171580A (en) System and method for utilizing a presence service to advertise activity availability
US7647283B2 (en) Method, system, and computer program product for adaptively learning user preferences for smart services
US8812440B2 (en) Web-based information delivery method, system, and apparatus
US20070233859A1 (en) Method and apparatus for providing presence information
JP2000122949A (en) Content managing method
CN101160873A (en) Method and system for notifying presence information
CN106651073A (en) Task distribution management system and method thereof
WO2002037393A2 (en) System and method for service specific notification
US20140067907A1 (en) Method, System, And Computer Program Product For Delivering Smart Services
US8806378B2 (en) Mobile client application for managing display of messages to users
WO2005079381A2 (en) Automated dissemination of presence and availability schedule
US7765173B2 (en) Method, system, and computer program product for delivering smart services
CN101467215A (en) Auxiliary output device
US20090112722A1 (en) Centralized consumer notification system
CN110913018A (en) Distributed regulation and control service system
CN101145224A (en) Calendar supervision system and its supervision method
JP3979310B2 (en) Advertisement delivery system and advertisement delivery method

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
C10 Entry into substantive examination
SE01 Entry into force of request for substantive examination
C12 Rejection of a patent application after its publication
RJ01 Rejection of invention patent application after publication

Application publication date: 20080319