CN102750605A - Device, system and method for calendar management - Google Patents
Device, system and method for calendar management Download PDFInfo
- Publication number
- CN102750605A CN102750605A CN2012101520659A CN201210152065A CN102750605A CN 102750605 A CN102750605 A CN 102750605A CN 2012101520659 A CN2012101520659 A CN 2012101520659A CN 201210152065 A CN201210152065 A CN 201210152065A CN 102750605 A CN102750605 A CN 102750605A
- Authority
- CN
- China
- Prior art keywords
- calendar
- server
- client
- issue
- sent
- 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
Links
Images
Landscapes
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention discloses a client which is used for performing data operation of a calendar according to an instruction of a user and saving an operation result; sending a publishing request and/or the calendar to a calendar server according to the instruction of the user; and when an updating state is in an automatic state, sending data which changes to the calendar server for updating. The invention also discloses the calendar server, a calendar management system and a method. According to the server, the system and the method, the user can publish the calendar which is established by the user by using a network, and the working efficiency is improved.
Description
This case is that application number is 200710151730.1, the applying date is on September 27th, 2007, denomination of invention is divided an application for the patented claim of " calendar management system and management method ".
Technical field
The present invention relates to calendar management technology in the computer network, relate in particular to a kind of calendar management equipment, system and method.
Background technology
Along with the fast development of existing network infotech, network can provide compiling in a large number of information, and the facility that propagation is provided, retrieves and consults.Calendar software is the computer software of tissue and displaying calendar, incident and schedule, and general isolated operation supplies the user to consult the date on user's computer, writes down, revises and consult calendar informations such as incident and schedule.
At present, because existing calendar software is that the calendar that is stored in server is operated, and do not store calendar data in the user's computer.So, when the user uses other computing machines, just can't check or use own calendar information on former computing machine, and, be not easy to check the ready-made schedule of other users.Obviously, this calendar software receives the restriction of network, and efficiency ratio is lower; And, when network breaks off, the calendar data that the user can't the access server end.
Summary of the invention
In view of this, the present invention provides a kind of calendar management equipment, system and method, the calendar that the user can be created through Web publishing self.
For achieving the above object, technical scheme of the present invention is achieved in that
Claim to be copied ...
Adopt calendar management equipment provided by the invention, system and method, the user is carried out in client the major part operation of calendar, avoid the use of network, thereby can improve certain efficient; Simultaneously, can guarantee that when network broke off, the user still can operate the calendar management system.
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 client;
Fig. 3 is the structural representation of first embodiment of the invention Calendar server;
Fig. 4 is the system architecture synoptic diagram of second embodiment of the invention;
Fig. 5 is the client of second embodiment of the invention or the structural representation of handheld terminal.
Embodiment
With reference to Fig. 1, show the system architecture of first embodiment of the invention, comprise Calendar server 20 and client 10, client 10 is carried out data manipulation according to user instruction to calendar, and this data manipulation comprises establishment, revises and/or deletion, and preserves operating result; Client 10 is sent calendar according to user's instruction to Calendar server 20; Client 10 is sent the issue request according to user's issuing command to Calendar server 20; Calendar server 20 receives calendar and/or the issue request that client 10 is sent, and storage and/or management calendar.
With reference to Fig. 2, show the structure of first embodiment of the invention client 10, client 10 comprises interface unit 101, realizes the exchanges data of said client 10 and Calendar server 20; Storage unit 103 is preserved the calendar of client 10; Processing unit 102, the management and/or the issue of calendar are realized in control interface unit 101 and storage unit 103 work.Concrete, processing unit 102 is sent to Calendar server 20 with the calendar in the storage unit 103 through interface unit 101 according to user instruction; Processing unit 102 forms the issue request according to user instruction, sends the issue request through interface unit 101 to Calendar server 20.
Present embodiment is realized the management to calendar in client 10 through adopting client database, and specifically, client database comprises client calendar information table and client calendar event table.
With reference to table 1, client calendar information table comprises " calendar ID ", " title ", " classification ", " founder ID ", " zero-time ", " termination time ", " update mode " and fields such as " issued states ".Wherein, " calendar ID " is the ID of the unique identification calendar of client database distribution; " title " is the calendar title of being set by the user, for example " work program in June " perhaps " activity schedule in July "; " classification " is meant the classification of calendar, for example " operation class " perhaps " leisure "; " founder ID " be the ID of creating calendar; " zero-time " and " termination time " writes down the zero-time and the termination time of calendar respectively; " update mode " indicated the mode that calendar upgrades, and comprises manual renewal or renewal automatically; " issued state " is meant that whether calendar is open to other users, allows other users to subscribe to.
| Calendar ID | Title | Classification | Founder ID | Zero-time | Termination time | Update mode | Issued state |
| …… | …… | …… | …… | …… | …… | …… | …… |
Table 1
With reference to table 2, client calendar event table comprises " calendar ID ", " event id ", " incident ", " circulation sign ", " zero-time " and " termination time ".Wherein, " the calendar ID " in " calendar ID " and the client calendar information table is consistent; " event id " is the ID of the unique identification incident of client database distribution; The concrete incident that " incident " recording user is arranged; " circulation sign " indicated the information that incident regularly takes place, for example 1 year 1 time; " zero-time " and " termination time " be 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
The client 10 of present embodiment is installation and operates in the client-side program on the subscriber computer, also can be the program that runs in the subscriber computer browser; The user can be connected to Calendar server 20 from browser, realizes calendar publication.
The workflow of the client 10 of present embodiment comprises:
Step S11: client 10 is sent calendar to Calendar server 20;
Step S 12: client 10 is sent the issue request to Calendar server 20.
Specifically, above-mentioned steps S11 comprises:
Step S111: processing unit 102 carries out data manipulation according to user instruction to calendar, and the data manipulation result is stored in the storage unit 103; Data manipulation comprise to calendar carry out newly-built, editor or the deletion;
Step S112: the calendar of user's appointment is sent to Calendar server 20 through interface unit 101.
Above-mentioned steps S112 specifically comprises:
Step S1121: processing unit 102 forms the request of transmission according to user instruction, and this transmission request comprises information such as " founder ID ", " title ";
Step S1122: interface unit 101 sends the transmission request that step S1121 forms to Calendar server 20;
Step S1123: receive the response message that Calendar server 20 is returned, response message comprises " allowing to send " and " refusal sends " two kinds;
Step S1124:, then specify calendar to send to Calendar server 20 user if response message is " allowing to send "; If response message is " refusal sends ", then return failure information to the user.
Concrete, above-mentioned steps S12 comprises:
Step S121: client 10 is set the issue rule according to user instruction and is formed the issue request, and the issue request comprises " calendar ID ", " founder ID " and issue rule;
Step S122: processing unit 102 sends the issue request to Calendar server 20.
Among the above-mentioned steps S121; The user can set the issue rule according to field in the client calendar information table; For example: according to " zero-time " and " termination time " issue, on August 1st, 2007, " termination time " was all calendars between 15 days Augusts in 2007 like issue " from date "; According to " classification " issue, be the calendar of " work " like issue all " classification "; Can also develop and publish rule according to a plurality of fields in the client calendar information table, for example: being distributed on all " classification " on August 15 1 day to 2007 August in 2007 according to the combination of " zero-time ", " termination time " and fields such as " classification " is the calendar of " work "; Can also be according to the field in the calendar data table, to announced calendar cancellation issue.
The structure of the Calendar server 20 that Fig. 3 shows, as shown in Figure 3, Calendar server 20 comprises memory module 201, stores at least one calendar; Communication module 203 is connected with client 10 through network, realizes Calendar server 20 and client 10 exchanges data; Processing module 202, control store module 201 and communication module 203 work realize the management and/or the issue of calendar respectively.Concrete, processing module 202 control communication modules 203 receive the calendar that client 10 is sent, and with calendar stores to memory module 201; Processing module 202 control communication modules 203 receive the issue request that client 10 is sent, based on issue request management and/or issue calendar.
Above-mentioned network is internet, LAN, wireless communication networks and/or private line network.
At Calendar server 20 ends, present embodiment adopts database to realize the management to calendar.Specifically, in memory module 201, calendar database is set, this calendar database comprises server calendar information table and server calendar event table.
With reference to table 3, server calendar information table comprises " calendar ID ", " title ", " classification ", " founder ID ", " zero-time ", " termination time ", " update mode " and " issued state " field." calendar ID " is the ID of the unique identification calendar of calendar database distribution, and the content in the client calendar information table of " title ", " classification ", " founder ID ", " zero-time ", " termination time " and " update mode " and client 10 is consistent; " issued state " is meant whether calendar is open to other users, and other users can subscribe to.
| Calendar ID | Title | Classification | Founder ID | Zero-time | Termination time | Update mode | Issued state |
| …… | …… | …… | …… | …… | …… | …… | …… |
Table 3
With reference to table 4, server calendar event table comprises " calendar ID ", " event id ", " incident ", " circulation sign ", " zero-time " and " termination time "." calendar ID " in " calendar ID " and the client calendar information table is consistent; " event id " and " incident " in " event id " and " incident " and the client calendar event table is consistent; " circulation identifies " in " circulation sign " and the client calendar event table is consistent; " zero-time " and " termination time " in " zero-time " and " termination time " and the client calendar event table is consistent.
| Calendar ID | Event id | Incident | The circulation sign | Zero-time | Termination time |
| …… | …… | …… | …… | …… | …… |
Table 4
The groundwork flow process of the Calendar server 20 of present embodiment is following:
Step S21: Calendar server 20 receives calendar;
Step S22: Calendar server 20 response issue requests, issue calendar.
Specifically, above-mentioned steps S21 is meant that Calendar server 20 receives the calendar that client 10 is sent through communication module 203, and processing module 202 deposits calendar in server calendar information table and the server calendar event table in;
Above-mentioned steps S22 is meant; Processing module 202 is received the issue request that client 10 is sent; In the server calendar information table of memory module 203 and server calendar event table, find corresponding calendar, change the value of " issued state " parameter into " disclosing " perhaps " underground " according to the issue rule in the issue request.
The calendar management system that the foregoing description provides; Can realize basic calendar management and issue; But because Calendar server 20 structures and issue mechanism are comparatively simple, the user uses still has many inconvenience, also can't adapt to the management and the issue demand of a large amount of calendars.
Be the calendar management ability of further raising calendar management of the present invention system, user-friendly, the present invention proposes second embodiment, and the calendar management system architecture of second embodiment is as shown in Figure 4.
Present embodiment comprises client 11, handheld terminal 12 and Calendar server 21; Said Calendar server 21 comprises calendar child servers crowd 210, the webserver 211, cluster server 212 and wireless server 213, can also comprise event server 214 and/or other servers 215.
In conjunction with shown in Figure 5, the client 11 in the present embodiment or the structure of handheld terminal 12 also comprise notification unit 114, Active Desktop Calendar unit 115, main boundary element 116, temporal logic unit 117, software development kit 118 and/or MSN run-time library 119.
The interface of 118 conducts of MSN run-time library and other Account Administration systems is accepted the control of processing unit 112 and is called other Account Administration systems, to realize calling other Account Administration systemic-functions.
The user uses client 11 to be connected with calendar child servers crowd 210 with cluster server 212 through the webserver 211 respectively; The user uses handheld terminal 12 to be connected with calendar child servers crowd 210 with cluster server 212 through wireless server 213.Calendar child servers crowd 210 comprises a plurality of child servers; As shown in Figure 5; Comprise that the first calendar management server 2101, the second calendar management server 2102,3-calendar management server 2103 and interface child servers 2104 interconnect; Be connected with cluster server 212 and swap data through interface child servers 2104, also can be connected and swap data with event server 214 and/or other servers 215.
The background program of the Calendar server 21 in the present embodiment comprises an interface service process and several calendar management service processess.Wherein, Interface child servers 2104 runnable interface service processess; 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 establishment, modification, deletion of calendar etc.
Above-mentioned client 11 or handheld terminal 12 and Calendar server 21 and child servers thereof all realize that according to TCP and/or udp protocol communication network connects, and network is internet, wireless communication networks, LAN and/or private line network.
Client 11 or handheld terminal 12 adopt existing client-side program, browser or handheld terminal technology to realize, so do not give unnecessary details.
The client 11 of present embodiment is installation and operates in the client-side program 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 21 from browser and consult and issue calendar.And handheld terminal 12 is to operate in user's wireless telecommunications system or the client-side program on the wireless data treating apparatus; 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 consult and issue calendar.
The concrete workflow and the last embodiment of client 11, handheld terminal 12 and Calendar server 21 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 Account Administration systems.
The calendar management system that uses present embodiment to provide; Can realize a plurality of user's issues or consult a plurality of calendars; The user can issue or consult work schedule, notice of meeting, activity schedule, friend's calendars such as schedule on wireless telecommunications system or wireless data treating apparatus, trade company or organization user can issue multiple information such as preview, market activity notification, favor information, stock market.
The user can be provided with automatic renewal; When the calendar management system that present embodiment provides can realize Calendar server 21, client 11 or handheld terminal 12 wherein the calendar of an end changes; Automatically be updated to the other end, be very easy to the user, realized the dirigibility and the practicality of calendar publication.
On the foregoing description basis, the present invention proposes the 3rd embodiment, realizes that the user consults announced calendar, specifically may further comprise the steps:
Step S31: client forms and sends the request of consulting according to the condition of consulting of user's appointment;
Step S32: Calendar server finds the calendar that meets the condition of consulting according to consulting the condition of consulting in the request in memory module;
Step S33: the calendar that Calendar server will meet the condition of consulting sends to client.
Among the above-mentioned steps S31; The described request of consulting comprises " calendar ID ", consults information such as condition; The condition of consulting is to set according to the field of issuing the calendar data table, for example: consult according to " classification ", consult perhaps according to " zero-time ", according to " termination time " and consult according to a plurality of field combination; As: consult according to the combination of " zero-time ", " termination time " and fields such as " classification " that to be distributed on all " classification " on August 15 1 day to 2007 August in 2007 be the calendar of " work ".
The present invention proposes the 4th embodiment; On the previous embodiment basis; Propose to upgrade automatically the mechanism of calendar; Client calendar information table and server calendar information table all comprise " update mode " this field, and when user's " update mode " field was set to " automatically ", client sent to Calendar server with the data that change in client calendar information table and/or the client calendar event table automatically and upgrades.In like manner, when the data in server calendar information table and/or the server calendar event table changed, Calendar server sent to client with the data that change automatically and upgrades.
The present invention proposes the 5th embodiment, and a kind of calendar management method realizes calendar management based on client and Calendar server, and this method comprises:
Step S41: client is sent calendar to Calendar server;
Step S42: Calendar server receives calendar;
Step S43: client is sent the issue request to Calendar server;
Step S44: Calendar server response issue request, issue calendar.
Specifically, above-mentioned steps S41 comprises:
Step S411: processing unit carries out data manipulation according to user instruction to calendar, and the data manipulation result is stored in the storage unit; Data manipulation comprise to calendar carry out newly-built, editor or the deletion;
Step S412: client sends to Calendar server 20 with the calendar of user's appointment with through interface unit.
Above-mentioned steps S412 specifically comprises:
Step S4121: processing unit forms the request of transmission according to user instruction, and this transmission request comprises information such as " founder ID ", " title ";
Step S4122: interface unit sends the transmission request that step S4121 forms to Calendar server;
Step S4123: receive the response message that Calendar server is returned, response message comprises " allowing to send " and " refusal sends " two kinds;
Step S4124:, then specify calendar to send to Calendar server the user if response message is " allowing to send "; If response message is then returned failure information to the user for " refusal sends ".
Above-mentioned steps S42 is meant that Calendar server receives the calendar that client is sent through communication module, and processing module deposits calendar server calendar information table in and deposits in the server calendar event table.
Above-mentioned steps S43 comprises:
Step S431: client is set the issue rule based on user instruction and is formed the issue request, and the issue request comprises " calendar ID ", " founder ID " and issue rule;
Step S432: processing unit sends the issue request to Calendar server.
Issue rule among the above-mentioned steps S431 can be confirmed according to the field in the calendar information table of terminal; For example: issue according to " zero-time " and " termination time "; On August 1st, 2007, " termination time " was all calendars between 15 days Augusts in 2007 like issue " from date "; According to " classification " issue, be the calendar of " work " like issue all " classification "; Can also develop and publish rule according to a plurality of fields in the calendar information table of terminal, for example: being distributed on all " classification " on August 15 1 day to 2007 August in 2007 according to the combination of " zero-time ", " termination time " and fields such as " classification " is the calendar of " work "; Can also be to announced calendar cancellation issue.
Above-mentioned steps S44 is meant; Processing module is received the issue request that client is sent; In the server calendar information table of memory module and server calendar event table, find corresponding calendar, change the value of " issued state " parameter into " disclosing " perhaps " underground " according to the issue rule in the issue request.
Above-mentioned calendar management method also comprises the step of consulting announced calendar, comprising:
Step S51: client forms and sends the request of consulting according to the condition of consulting of user's appointment;
Step S52: Calendar server finds the calendar that meets the condition of consulting according to consulting the condition of consulting in the request in memory module;
Step S53: the calendar that Calendar server will meet the condition of consulting sends to client.
Consulting request described in the above-mentioned steps S51 comprises calendar ID, consults information such as condition; The condition of consulting is to set according to the field of issuing in the calendar data table; For example: consult according to " classification ", according to " zero-time ", consult or consult according to a plurality of field combination according to " termination time ", for example being distributed on all " classification " on August 15 1 day to 2007 August in 2007 according to the combination of " zero-time ", " termination time " and fields such as " classification " is the calendar of " work ".
Present embodiment also proposes to upgrade automatically the mechanism of calendar; Client calendar information table and server calendar information table all comprise " update mode " this field; When user's " update mode " field was set to " automatically ", client sent to Calendar server with the data that change in client calendar information table and/or the client calendar event table automatically and upgrades.In like manner, when the data in server calendar information table and/or the server calendar event table changed, Calendar server sent to client with the data that change automatically and upgrades.
The above is merely preferred embodiment of the present invention, is not to be used to limit protection scope of the present invention, all any modifications of within spirit of the present invention and principle, being done, is equal to replacement and improvement etc., all should be included within protection scope of the present invention.
Claims (15)
1. a client is characterized in that, said client is used for according to user instruction calendar being carried out data manipulation, and preserves operating result; Send issue request and/or calendar according to user instruction to Calendar server; Also be used in update mode when being automatic, the data that automatically self changed send to Calendar server and upgrade.
2. client according to claim 1 is characterized in that, said client comprises:
Interface unit, the exchanges data of realization client and Calendar server;
Storage unit, the calendar of storage client;
Processing unit, control interface unit and memory cell work; Based on user instruction the calendar in the memory cell is sent to Calendar server through interface unit; And/or pass through interface unit based on user instruction formation issue request and send the request of issue to Calendar server.
3. client according to claim 1 and 2 is characterized in that, said client also comprises: notification unit is used for sending the alert notification that expires to the user.
4. client according to claim 1 and 2 is characterized in that, said client also comprises: Active Desktop Calendar unit, main boundary element, temporal logic unit, software development kit and/or MSN run-time library.
5. a Calendar server is characterized in that, said Calendar server is used to receive calendar and/or the issue request that client is sent, and storage and/or management calendar; Also be used in update mode when being automatic, the data that automatically self changed send to client and upgrade.
6. Calendar server according to claim 5 is characterized in that, said Calendar server comprises:
Memory module, the storage calendar;
Communication module is connected with client through network, realizes the exchange of Calendar server and client data;
Processing module, the control communication module receives the calendar that client is sent, and calendar is sent to said memory module storage; The control communication module receives the issue request that client is sent, according to issue request management and/or issue calendar.
7. according to claim 5 or 6 described Calendar server, it is characterized in that said Calendar server comprises calendar child servers crowd, the webserver, cluster server and wireless server;
Said calendar child servers crowd is connected with client with cluster server through the webserver; Said calendar child servers crowd is connected with handheld terminal with wireless server through cluster server.
8. Calendar server according to claim 7 is characterized in that, said calendar child servers crowd comprises interface child servers and a plurality of calendar management server; Said each calendar management server and interface child servers interconnect; Said each calendar management server is connected with cluster server and swap data through the interface child servers.
9. Calendar server according to claim 8 is characterized in that, said Calendar server also comprises event server and/or other servers.
10. Calendar server according to claim 9; It is characterized in that said Calendar server, the webserver, cluster server, wireless server, calendar child servers crowd, interface child servers, event server and/or other servers are a station server.
11. a calendar management system is characterized in that, said calendar management system comprises each described client of claim 1 to 4 and each described Calendar server of claim 5 to 10.
12. a calendar management method is characterized in that, this method comprises:
Client is sent calendar to Calendar server, and Calendar server receives calendar;
Client is sent the issue request to Calendar server, Calendar server response issue Intra-request Concurrency cloth calendar;
Client and/or Calendar server self update mode is set to when automatic, and the data that client and/or Calendar server change self automatically send to Calendar server and/or client is upgraded.
13., it is characterized in that said client is sent the issue request to Calendar server and is based on the said calendar management method of claim 12: client is set the issue rule based on user instruction and is formed the issue request, and sends the issue request to Calendar server.
14., it is characterized in that this method also comprises according to the said calendar management method of claim 12: said client to calendar carry out data manipulation comprise to calendar carry out newly-built, editor or the deletion.
15. according to the said calendar management method of claim 12, it is characterized in that this method also comprises: client is sent the request of consulting to said Calendar server; Calendar server is searched the calendar that meets the condition of consulting, and the calendar that will meet the condition of consulting sends to client.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2012101520659A CN102750605A (en) | 2007-09-27 | 2007-09-27 | Device, system and method for calendar management |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2012101520659A CN102750605A (en) | 2007-09-27 | 2007-09-27 | Device, system and method for calendar management |
Related Parent Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNA2007101517301A Division CN101145224A (en) | 2007-09-27 | 2007-09-27 | Calendar supervision system and its supervision method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN102750605A true CN102750605A (en) | 2012-10-24 |
Family
ID=47030762
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2012101520659A Pending CN102750605A (en) | 2007-09-27 | 2007-09-27 | Device, system and method for calendar management |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102750605A (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102955997A (en) * | 2012-11-15 | 2013-03-06 | 广东欧珀移动通信有限公司 | Method and system for remote schedule management |
| CN105378769A (en) * | 2013-06-10 | 2016-03-02 | 微软技术许可有限责任公司 | Navigation calendar |
| WO2017054359A1 (en) * | 2015-09-28 | 2017-04-06 | 小米科技有限责任公司 | Method, device and system for managing calendar information |
| CN113779049A (en) * | 2020-06-23 | 2021-12-10 | 北京沃东天骏信息技术有限公司 | Calendar updating method and device |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1725240A (en) * | 2004-07-23 | 2006-01-25 | 乐金电子(中国)研究开发中心有限公司 | Programme management method caeeied by mobile communication terminal computer |
| CN1882014A (en) * | 2005-06-17 | 2006-12-20 | 中兴通讯股份有限公司 | Subscriber calendar prompting method based on intelligent network |
| CN1964329A (en) * | 2006-11-24 | 2007-05-16 | 华为技术有限公司 | A method to provide calendar information in presence service and presence server |
| CN1971604A (en) * | 2005-11-23 | 2007-05-30 | 阿尔卡特公司 | System and method for calendar presence retrieval |
| WO2007064992A1 (en) * | 2005-12-01 | 2007-06-07 | Microsoft Corporation | Secured and filtered personal information publishing |
| CN101026643A (en) * | 2006-02-22 | 2007-08-29 | 迈世亚（北京）科技有限公司 | Automatic updating method of telephone directory data |
-
2007
- 2007-09-27 CN CN2012101520659A patent/CN102750605A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1725240A (en) * | 2004-07-23 | 2006-01-25 | 乐金电子(中国)研究开发中心有限公司 | Programme management method caeeied by mobile communication terminal computer |
| CN1882014A (en) * | 2005-06-17 | 2006-12-20 | 中兴通讯股份有限公司 | Subscriber calendar prompting method based on intelligent network |
| CN1971604A (en) * | 2005-11-23 | 2007-05-30 | 阿尔卡特公司 | System and method for calendar presence retrieval |
| WO2007064992A1 (en) * | 2005-12-01 | 2007-06-07 | Microsoft Corporation | Secured and filtered personal information publishing |
| CN101026643A (en) * | 2006-02-22 | 2007-08-29 | 迈世亚（北京）科技有限公司 | Automatic updating method of telephone directory data |
| CN1964329A (en) * | 2006-11-24 | 2007-05-16 | 华为技术有限公司 | A method to provide calendar information in presence service and presence server |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102955997A (en) * | 2012-11-15 | 2013-03-06 | 广东欧珀移动通信有限公司 | Method and system for remote schedule management |
| CN105378769A (en) * | 2013-06-10 | 2016-03-02 | 微软技术许可有限责任公司 | Navigation calendar |
| US10535043B2 (en) | 2013-06-10 | 2020-01-14 | Microsoft Technology Licensing, Llc | Navigating a calendar |
| WO2017054359A1 (en) * | 2015-09-28 | 2017-04-06 | 小米科技有限责任公司 | Method, device and system for managing calendar information |
| CN113779049A (en) * | 2020-06-23 | 2021-12-10 | 北京沃东天骏信息技术有限公司 | Calendar updating method and device |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101416178B (en) | Managing rich presence collections | |
| CN101416208B (en) | The set on the scene of managing rich | |
| CN1527227B (en) | Distributing data access method and equipment for process control system | |
| CN101960439B (en) | Client environment creates system and client environment creation method | |
| CN101416177A (en) | Managing rich presence collections | |
| CN1818873A (en) | System and method for centralized software management in virtual machines | |
| CN101689167A (en) | In distributed system, progressively realize declarative models | |
| CN102663543A (en) | Scheduling system used for enterprise data unification platform | |
| CN102750605A (en) | Device, system and method for calendar management | |
| US7865913B2 (en) | Systems and methods for collaboration between computers | |
| CN108848132A (en) | A kind of distribution scheduling station system based on cloud | |
| CN102480390A (en) | Method and device for monitoring system | |
| CN100357889C (en) | Method for managing long-distance structural components service cycle with class as unit | |
| CN1964273A (en) | A method to interact service configuration information | |
| CN103593345A (en) | Webpage flow chart editing method and system | |
| CN101145224A (en) | Calendar supervision system and its supervision method | |
| CN111901228A (en) | User group communication method based on address book and electronic equipment | |
| CN102103717A (en) | Defining additional resources in a MES user management system | |
| CN110913018A (en) | Distributed regulation and control service system | |
| CN101521592B (en) | Method and device for establishing the SNMP agent of printer | |
| CN104735134A (en) | Method and device for providing computing service | |
| CN114358842A (en) | Advertisement delivery regulation and control method, device, system, equipment and medium | |
| CN102004715A (en) | Communication processing method and system of state machines | |
| CN113138844A (en) | Task issuing method, management component and working component of virtual machine cluster | |
| US20030120828A1 (en) | System and method for exchanging information between systems |
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: 20121024 |