WO2017054359A1 - 日历信息管理方法、装置及系统 - Google Patents
日历信息管理方法、装置及系统 Download PDFInfo
- Publication number
- WO2017054359A1 WO2017054359A1 PCT/CN2015/099734 CN2015099734W WO2017054359A1 WO 2017054359 A1 WO2017054359 A1 WO 2017054359A1 CN 2015099734 W CN2015099734 W CN 2015099734W WO 2017054359 A1 WO2017054359 A1 WO 2017054359A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- calendar
- information
- client
- user account
- original
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 85
- 238000007726 management method Methods 0.000 claims description 145
- 230000004048 modification Effects 0.000 claims description 17
- 238000012986 modification Methods 0.000 claims description 17
- 238000012790 confirmation Methods 0.000 claims description 11
- 238000005516 engineering process Methods 0.000 abstract description 13
- 238000010586 diagram Methods 0.000 description 30
- 238000004891 communication Methods 0.000 description 20
- 238000012545 processing Methods 0.000 description 19
- 230000000694 effects Effects 0.000 description 18
- 230000005236 sound signal Effects 0.000 description 8
- 230000001960 triggered effect Effects 0.000 description 8
- 230000007115 recruitment Effects 0.000 description 6
- 230000001133 acceleration Effects 0.000 description 4
- 230000003993 interaction Effects 0.000 description 4
- 230000003287 optical effect Effects 0.000 description 4
- 230000008569 process Effects 0.000 description 4
- 230000008859 change Effects 0.000 description 3
- 230000009471 action Effects 0.000 description 2
- 238000013500 data storage Methods 0.000 description 2
- 238000003384 imaging method Methods 0.000 description 2
- 239000004973 liquid crystal related substance Substances 0.000 description 2
- 230000002093 peripheral effect Effects 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- 230000006978 adaptation Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000003247 decreasing effect Effects 0.000 description 1
- 230000006870 function Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06N—COMPUTING ARRANGEMENTS BASED ON SPECIFIC COMPUTATIONAL MODELS
- G06N20/00—Machine learning
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/109—Time management, e.g. calendars, reminders, meetings or time accounting
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/109—Time management, e.g. calendars, reminders, meetings or time accounting
- G06Q10/1093—Calendar-based scheduling for persons or groups
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/40—Support for services or applications
- H04L65/401—Support for services or applications wherein the services involve a main real-time session and one or more additional parallel real-time or time sensitive sessions, e.g. white board sharing or spawning of a subconference
- H04L65/4015—Support for services or applications wherein the services involve a main real-time session and one or more additional parallel real-time or time sensitive sessions, e.g. white board sharing or spawning of a subconference where at least one of the additional parallel sessions is real time or time sensitive, e.g. white board sharing, collaboration or spawning of a subconference
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/55—Push-based network services
Definitions
- the present disclosure relates to the field of electronic technology applications, and in particular, to a calendar information management method, apparatus, and system.
- the calendar client is a client that can be used for calendar viewing by a user, and can be installed on a smart terminal such as a smart phone, a tablet computer, a vehicle terminal, etc., and provides a management function of calendar information for the user, wherein the calendar information can include the date.
- Information and event information the event information is used to indicate the event that occurred on the date corresponding to the date information.
- the calendar client can present the calendar to the user, and each date in the calendar corresponds to a date page (which can also be referred to as a calendar grid).
- a date page which can also be referred to as a calendar grid.
- the user may add event information of the to-be-created event in the calendar grid corresponding to the date of the event to be processed, and perform a memo setting, so that the calendar client can remind the user at the specified time, wherein the event information is included in the event information.
- the time information may be included to indicate the occurrence time of the event in the event information, and the specified time may be the first two hours of the event occurrence time, for example, the student may add the preaching information of the campus recruitment meeting to the preaching
- the date corresponds to the calendar box and the memo settings are made so that the calendar client can remind the students to participate in the campus recruitment meeting at the specified time.
- the present disclosure provides a calendar information management method, apparatus, and system.
- the technical solution is as follows:
- a calendar information management method comprising:
- the second calendar client is a calendar client to which the second user account is logged in, the first calendar client
- the calendar client is the first user account to log in, and the second user account is associated with the first user account.
- the original calendar information is obtained by the first calendar client updating the first original calendar information by using the third original calendar information, where the third original calendar information is the third calendar client at the third Calendar client display Adding corresponding event information in the specified date page of the calendar interface is obtained and published to the server, and the first calendar information is pushed by the server to the first calendar client.
- the corresponding calendar information is added to the specified date page of the calendar interface displayed by the first calendar client, and the original calendar information includes: date information and the event information, where the event information is used to indicate that the date information corresponds to The event that occurred on the date;
- the method further includes:
- the original calendar information is obtained by adding, by the first calendar client, corresponding event information in a specified date page of the calendar interface displayed by the first calendar client, where the original calendar information includes: a date Information and the event information, the event information being used to indicate an event occurring on a date corresponding to the date information.
- the method further includes:
- the acquiring the second user account associated with the first user account includes:
- the other user account does not include the first user account
- the other user account is used as the second user account.
- the acquiring the second user account associated with the first user account includes:
- the user account that subscribes to the first user account is used as the second user account.
- the acquiring the second user account associated with the first user account includes:
- the user account associated with the first user account obtained from the user account association list is used as the second user account.
- a calendar information management method comprising:
- the server pushes the shared calendar information to a second calendar client, where the second calendar client is a calendar client that is logged in by the second user account, and the first calendar client
- the calendar client is the first user account to log in, and the second user account is associated with the first user account.
- the modifying, according to the update instruction, the content indicated by the update instruction in the original calendar information including:
- the prompt information is used to prompt the user to modify the content indicated by the update instruction in the original calendar information
- the content indicated by the update instruction in the original calendar information is modified when receiving the confirmation instruction that the user triggers the instruction to modify.
- the original calendar information includes date information and event information
- the event information is used to indicate an event that occurs on a date corresponding to the date information
- the method before the displaying the original calendar information, the method further includes:
- the third calendar client Receiving, by the third calendar client, third event information that is pushed by the server, adding, by the third calendar client, corresponding event information in a specified date page of the calendar interface displayed by the third calendar client, and publishing To the server, the user account logged in the third calendar client is associated with the first user account.
- the method further includes:
- the updating the first original calendar information by using the third original calendar information to obtain the original calendar information comprises:
- the original calendar information is obtained by replacing the first original calendar information with the third original calendar information.
- the updating the first original calendar information by using the third original calendar information to obtain the original calendar information comprises:
- the method before the displaying the original calendar information, the method further includes:
- a calendar information management method comprising:
- the shared calendar information is sent by the server to the second calendar client after receiving the shared calendar information published by the first calendar client, and the second calendar client is the login a calendar client of the second user account, the first calendar client is a calendar client to which the first user account is logged in, the second user account is associated with the first user account, and the shared calendar information is The first calendar client modifies the original calendar information displayed by the first calendar client;
- the calendar client obtains the corresponding event information in the specified date page of the calendar interface displayed by the second calendar client.
- the updating the second original calendar information by using the shared calendar information includes:
- the second original calendar information is replaced with the shared calendar information.
- the updating the second original calendar information by using the shared calendar information includes:
- the shared calendar information and the second original calendar information are merged.
- a calendar information management apparatus comprising:
- a first receiving module configured to receive shared calendar information published by the first calendar client, where the shared calendar information is obtained by modifying, by the first calendar client, the original calendar information displayed by the first calendar client ;
- a first pushing module configured to push the shared calendar information to a second calendar client, so that the second calendar client updates the second original calendar information by using the shared calendar information, the second original calendar information
- the second calendar client is obtained by adding corresponding event information to a specified date page of the calendar interface displayed by the second calendar client, where the second calendar client is a calendar client that is logged in by the second user account.
- the first calendar client is a calendar client that is logged in by the first user account, and the second user account is associated with the first user account.
- the original calendar information is obtained by the first calendar client updating the first original calendar information by using the third original calendar information, where the third original calendar information is the third calendar client at the third Adding corresponding event information in the specified date page of the calendar interface displayed by the calendar client is obtained and published to the server, and the first calendar information is the first calendar client.
- the original calendar information includes: date information and the event information, the event information is used to indicate the The event that occurred on the date corresponding to the date information;
- the device also includes:
- the second receiving module is configured to receive the third original calendar information issued by the third calendar client, where the user account registered in the third calendar client is associated with the first user account;
- a second push module configured to push the third original calendar information to the first calendar client.
- the original calendar information is obtained by adding, by the first calendar client, corresponding event information in a specified date page of the calendar interface displayed by the first calendar client, where the original calendar information includes: a date Information and the event information, the event information being used to indicate an event occurring on a date corresponding to the date information.
- the device further includes:
- An obtaining module configured to acquire the second user account associated with the first user account.
- the obtaining module is configured to:
- the other user account does not include the first user account
- the other user account is used as the second user account.
- the obtaining module is configured to:
- the user account that subscribes to the first user account is used as the second user account.
- the obtaining module is configured to:
- the user account associated with the first user account obtained from the user account association list is used as the second user account.
- a calendar information management apparatus comprising:
- a display module configured to display original calendar information
- a first receiving module configured to receive an update instruction for the original calendar information
- the modifying module is configured to modify, according to the update instruction, the content indicated by the update instruction in the original calendar information to obtain shared calendar information;
- a publishing module configured to publish the shared calendar information to a server, so that the server pushes the shared calendar information to a second calendar client, where the second calendar client is a calendar client logged in by a second user account
- the first calendar client is a calendar client that is logged in by the first user account, and the second user account is associated with the first user account.
- the modification module is configured to:
- the prompt information is used to prompt the user to modify the content indicated by the update instruction in the original calendar information
- the content indicated by the update instruction in the original calendar information is modified when receiving the confirmation instruction that the user triggers the instruction to modify.
- the original calendar information includes date information and event information
- the event information is used to indicate an event that occurs on a date corresponding to the date information
- the modification module is configured to:
- the device further includes:
- a second receiving module configured to receive third original calendar information pushed by the server, where the third original calendar information is in a specified date page of the calendar interface displayed by the third calendar client Adding corresponding event information is obtained and published to the server, and the user account registered in the third calendar client is associated with the first user account.
- the device further includes:
- An update module configured to update the first original calendar information by using the third original calendar information to obtain the original calendar information, where the first original calendar information is displayed by the first calendar client on the first calendar client Add the corresponding event information to the specified date page of the calendar interface.
- the update module is configured to:
- the original calendar information is obtained by replacing the first original calendar information with the third original calendar information.
- the update module is configured to:
- the device further includes:
- the adding module is configured to add the corresponding event information in the specified date page of the calendar interface displayed by the first calendar client to obtain the original calendar information.
- a calendar information management apparatus comprising:
- the receiving module is configured to receive shared calendar information pushed by the server, where the shared calendar information is sent by the server to the second calendar client after receiving the shared calendar information published by the first calendar client, the second
- the calendar client is a calendar client that logs in to the second user account
- the first calendar client is a calendar client to which the first user account is logged in
- the second user account is associated with the first user account
- the shared calendar information is obtained by modifying, by the first calendar client, the original calendar information displayed by the first calendar client;
- An update module configured to update the second original calendar information with the shared calendar information, the second original calendar information being a specified date page of the calendar interface displayed by the second calendar client on the second calendar client Add the corresponding event information to get.
- the update module is configured to:
- the second original calendar information is replaced with the shared calendar information.
- the update module is configured to:
- the shared calendar information and the second original calendar information are merged.
- a calendar information management apparatus including:
- a memory for storing executable instructions of the processor
- processor is configured to:
- the second calendar client is a calendar client to which the second user account is logged in, the first calendar client
- the calendar client is the first user account to log in, and the second user account is associated with the first user account.
- a calendar information management apparatus including:
- a memory for storing executable instructions of the processor
- processor is configured to:
- the server pushes the shared calendar information to a second calendar client, where the second calendar client is a calendar client that is logged in by the second user account, and the first calendar client
- the calendar client is the first user account to log in, and the second user account is associated with the first user account.
- a calendar information management apparatus including:
- a memory for storing executable instructions of the processor
- processor is configured to:
- the shared calendar information is sent by the server to the second calendar client after receiving the shared calendar information published by the first calendar client, and the second calendar client is the login a calendar client of the second user account, the first calendar client is a calendar client to which the first user account is logged in, the second user account is associated with the first user account, and the shared calendar information is The first calendar client modifies the original calendar information displayed by the first calendar client;
- the second original calendar information is that the second calendar client adds corresponding event information in a specified date page of the calendar interface displayed by the second calendar client owned.
- a calendar information management system comprising: a server, a first calendar client, and a second calendar client,
- the server includes the calendar information management apparatus according to any of the fourth aspect or the fourth aspect;
- the first calendar client includes the calendar information management device according to any of the fifth aspect or the fifth aspect;
- the second calendar client includes the calendar information management apparatus according to any one of the sixth aspect or the sixth aspect.
- a calendar information management system comprising: a server, a first calendar client, and a second calendar client,
- the server includes the calendar information management device of the seventh aspect
- the first calendar client includes the calendar information management device of the eighth aspect
- the second calendar client includes the calendar information management device of the ninth aspect.
- the server receives the shared calendar information published by the first calendar client, and the shared calendar information is that the first calendar client modifies the original calendar information displayed by the first calendar client.
- Pushing shared calendar information to the second calendar client to enable sharing of the second calendar client The calendar information updates the second original calendar information, and the second original calendar information is obtained by adding the corresponding event information to the second calendar client in the specified date page of the calendar interface displayed by the second calendar client. Since the shared calendar information is obtained by modifying the original calendar information displayed by the first calendar client by the first calendar client, the problem that the accuracy of the calendar information is low is avoided, thereby solving the accuracy of the calendar information management in the related art. The problem of lower sex has achieved the effect of improving the accuracy of calendar information management.
- FIG. 1 is a schematic structural diagram of an implementation environment involved in a calendar information management method according to various embodiments of the present disclosure
- FIG. 2 is a flowchart of a method for managing a calendar information according to an exemplary embodiment
- FIG. 3 is a flowchart of a method for managing a calendar information according to another exemplary embodiment
- FIG. 4 is a flowchart of a method for managing a calendar information according to still another exemplary embodiment
- 5-1 is a flowchart of a method for managing a calendar information according to still another exemplary embodiment
- FIG. 5-2 is a calendar interface diagram displayed by a third calendar client according to the embodiment shown in FIG. 5-1;
- Figure 5-3 is a calendar interface diagram displayed by another third calendar client provided by the embodiment shown in Figure 5-1;
- Figure 5-4 is a calendar interface diagram displayed by the first calendar client provided by the embodiment shown in Figure 5-1;
- 5-5 is a calendar interface diagram displayed by another first calendar client provided by the embodiment shown in FIG. 5-1;
- 5-6 is a calendar interface diagram displayed by the first calendar client provided by the embodiment shown in FIG. 5-1;
- FIG. 5-1 is a flowchart of a method for modifying, by the first calendar client, the content indicated by the update instruction in the original calendar information according to the update instruction, provided by the embodiment shown in FIG. 5-1;
- FIG. 5-8 is a schematic diagram of a prompt interface displayed by the first calendar client according to the embodiment shown in FIG. 5-1;
- 5-9 is an interface diagram of an original calendar information displayed by the first calendar client according to the embodiment shown in FIG. 5-1 after updating the original calendar information;
- 5-10 is a flowchart of a method for a server to obtain a second user account associated with a first user account according to the embodiment shown in FIG. 5-1;
- FIG. 5-11 are flowcharts of another method for obtaining, by the server shown in FIG. 5-1, a second user account associated with a first user account;
- FIG. 5-12 is a flowchart of a method for obtaining, by another server, the second user account associated with the first user account according to the embodiment shown in FIG. 5-1;
- FIG. 6 is a block diagram of a calendar information management apparatus according to an exemplary embodiment
- FIG. 7 is a block diagram of another calendar information management apparatus according to an exemplary embodiment.
- FIG. 8 is a block diagram of a calendar information management apparatus according to another exemplary embodiment.
- FIG. 9 is a block diagram showing another calendar information management apparatus according to another exemplary embodiment.
- FIG. 10 is a block diagram of a calendar information management apparatus according to still another exemplary embodiment.
- FIG. 11 is a block diagram of a calendar information management apparatus according to an exemplary embodiment
- FIG. 12 is a block diagram showing a calendar information management apparatus according to another exemplary embodiment.
- FIG. 13 is a block diagram of a calendar information management apparatus according to still another exemplary embodiment.
- FIG. 14 is a block diagram of a calendar information management system, according to an exemplary embodiment.
- FIG. 1 is a schematic structural diagram of an implementation environment involved in a calendar information management method according to various embodiments of the present disclosure.
- the implementation environment includes a first terminal 120, a second terminal 140, a third terminal 160, and a server 180.
- the first terminal 120, the second terminal 140, and the third terminal 160 may be respectively connected to the server 180 through a wired network or a wireless network, and the wireless network may include, but is not limited to, wireless fidelity (English: Wireless Fidelity, referred to as WIFI) ), Bluetooth, infrared, Zigbee, data, and the first terminal 120, the second terminal 140, and the third terminal 160 may also be connected to each other through a wired network or a wireless network (not shown in FIG. 1)
- WIFI Wireless Fidelity
- the first calendar client is installed on the first terminal 120, the first terminal 120 manages the calendar information by using the first calendar client, and the second calendar client is installed on the second terminal 140.
- the second terminal 140 implements management of the calendar information through the second calendar client;
- the third terminal 160 is installed with the third calendar client, and the third terminal 160 manages the calendar information through the third calendar client.
- the first terminal 120, the second terminal 140, and the third terminal 160 realize sharing of calendar information by the server 180.
- the third calendar client may log in a user account associated with the first user account, the first user account is a user account registered in the first calendar client, and the third calendar client may be in the third calendar client.
- the corresponding event information is added to the specified date page of the displayed calendar interface to obtain the third original calendar information, and the third original calendar information is released to the server 180.
- the server 180 may receive the third original calendar information issued by the third calendar client, and push the third original calendar information to the first calendar client, so that the first calendar client updates the first original calendar by using the third original calendar information.
- the information obtains the original calendar information, and the first original calendar information is obtained by adding the corresponding event information to the first calendar client in the specified date page of the calendar interface displayed by the first calendar client.
- the user account logged in the first calendar client may be the first user account
- the user account logged in the third calendar client may be associated with the first user account
- the server 180 may store the association relationship of the user account, and according to the user. The relationship of the account is entered into the calendar information. Push.
- the first calendar client can display the original calendar information, and receive an update instruction of the original calendar information triggered by the user, modify the content indicated by the update instruction in the original calendar information according to the update instruction, obtain the shared calendar information, and publish the information to the server. Share calendar information.
- the original calendar information displayed by the first calendar client may be obtained by receiving the third original calendar information pushed by the server, and updating the first original calendar information by using the third original calendar information, where the first original calendar information is the first calendar.
- the client obtains the corresponding event information in the specified date page of the calendar interface displayed by the first calendar client, and the original calendar information displayed by the first calendar client may also be displayed by the first calendar client on the first calendar client.
- the updating, by the first calendar client, the first original calendar information by using the third original calendar information may include: the first calendar client replacing the first original calendar information with the third original calendar information to obtain the original calendar information, or first The calendar client merges the third original calendar information with the first original calendar information to obtain the original calendar information.
- the modifying, by the first calendar client, the content indicated by the update instruction in the original calendar information according to the update instruction may include: displaying, by the first calendar client, the prompt information, where the prompt information is used to prompt the user to update the instruction in the original calendar information.
- the content of the indication is modified; when the confirmation instruction for the modification triggered by the user is received, the content indicated by the update instruction in the original calendar information is modified.
- the original calendar information may include date information and event information, and the first calendar client may modify at least one of the date information and the event information in the original calendar information according to the update instruction.
- the server 180 may receive the shared calendar information published by the first calendar client, and push the shared calendar information to the second calendar client, so that the first calendar client updates the first original calendar information with the third original calendar information to obtain the original calendar information.
- the second calendar client is a calendar client to which the second user account is logged in.
- the first calendar client is a calendar client to which the first user account is logged in, and the second user account is associated with the first user account.
- the server 180 may obtain a second user account associated with the first user account before pushing the shared calendar information to the second calendar client.
- the obtaining, by the server 180, the second user account associated with the first user account may include: the server 180 acquiring the subscription account of the first user account, and acquiring other user accounts that subscribe to the subscription account, and then using the other user account as the second user.
- the account number that is, the server 180 associates the user account that subscribes to the same subscription account as the associated user account.
- the obtaining, by the server 180, the second user account associated with the first user account may further include: the server 180 acquiring the user account that subscribes to the first user account, and using the user account that subscribes to the first user account as the second user account. That is, the server 180 uses the user account that subscribes to the first user account as the user account associated with the first user account.
- the obtaining, by the server 180, the second user account associated with the first user account may further include: the server 180 querying the preset user account association list according to the first user account, and the user account association list records the association of each user account.
- the user account associated with the first user account obtained from the user account association list is used as the second user account, that is, the correspondence relationship between the user accounts is configured in the server 180, and the server obtains the corresponding relationship according to the correspondence relationship of the user accounts.
- a user account associated with a user account is not limited in this embodiment of the present disclosure.
- the second calendar client may receive the shared calendar information pushed by the server 180, and update the second original calendar information by using the shared calendar information, where the second calendar information is displayed in the calendar interface of the second calendar client. Add the corresponding event information to the specified date page of the face.
- the updating, by the second calendar client, the second original calendar information by using the shared calendar information may include: replacing, by the second calendar client, the second original calendar information by using the shared calendar information, or the second calendar client sharing the calendar information and The second original calendar information is merged, and the embodiment of the present disclosure does not limit this.
- the first terminal 120, the second terminal 140, and the third terminal 160 realize the sharing of the calendar information through the server 180, thereby implementing the management of the calendar information, and improving the accuracy of the calendar information management.
- FIG. 2 is a flowchart of a method for managing a calendar information according to an exemplary embodiment. The embodiment is described by using the calendar information management method in the server 180 in the implementation environment shown in FIG. 2, the calendar information management method can include the following steps:
- step 201 the shared calendar information published by the first calendar client is received, and the shared calendar information is obtained by modifying the original calendar information displayed by the first calendar client by the first calendar client.
- step 202 the shared calendar information is pushed to the second calendar client, so that the second calendar client updates the second original calendar information with the shared calendar information, and the second original calendar information is the second calendar client at the second calendar client.
- the corresponding event information is added to the specified date page of the calendar interface displayed on the side.
- the second calendar client is a calendar client that is logged in by the second user account
- the first calendar client is a calendar client that is logged in by the first user account
- the second user account is associated with the first user account.
- the server receives the shared calendar information published by the first calendar client, and the shared calendar information is the original calendar information displayed by the first calendar client to the first calendar client. Making the modified; pushing the shared calendar information to the second calendar client, so that the second calendar client updates the second original calendar information with the shared calendar information, and the second original calendar information is the second calendar client at the second calendar client.
- the corresponding event information is added to the specified date page of the calendar interface displayed on the side. Since the shared calendar information is obtained by modifying the original calendar information displayed by the first calendar client by the first calendar client, the problem that the accuracy of the calendar information is low is avoided, thereby solving the accuracy of the calendar information management in the related art. The problem of lower sex has achieved the effect of improving the accuracy of calendar information management.
- the original calendar information is obtained by the first calendar client updating the first original calendar information by using the third original calendar information
- the third original calendar information is the calendar interface displayed by the third calendar client on the third calendar client.
- Adding corresponding event information to the specified date page and publishing to the server is pushed by the server to the first calendar client, and the first original calendar information is the first calendar client in the specified date page of the calendar interface displayed by the first calendar client.
- the original calendar information is obtained by adding corresponding event information, including: date information and event information, and the event information is used to indicate an event occurring on a date corresponding to the date information;
- the method may further include:
- the original calendar information is obtained by adding, by the first calendar client, the corresponding event information in the specified date page of the calendar interface displayed by the first calendar client, where the original calendar information includes: date information and event information, and event information is used. An event that occurs on the date indicated by the date information.
- the method may further include:
- obtaining the second user account associated with the first user account may include:
- obtaining the second user account associated with the first user account may include:
- the user account that subscribes to the first user account is used as the second user account.
- obtaining the second user account associated with the first user account may include:
- the user account associated with the first user account obtained from the user account association list is used as the second user account.
- the server receives the shared calendar information published by the first calendar client, and the shared calendar information is the original calendar information displayed by the first calendar client to the first calendar client. Making the modified; pushing the shared calendar information to the second calendar client, so that the second calendar client updates the second original calendar information with the shared calendar information, and the second original calendar information is the second calendar client at the second calendar client.
- the corresponding event information is added to the specified date page of the calendar interface displayed on the side. Since the shared calendar information is obtained by modifying the original calendar information displayed by the first calendar client by the first calendar client, the problem that the accuracy of the calendar information is low is avoided, thereby solving the accuracy of the calendar information management in the related art. The problem of lower sex has achieved the effect of improving the accuracy of calendar information management.
- FIG. 3 is a flowchart of a method for managing a calendar information according to another exemplary embodiment.
- the embodiment is illustrated by applying the calendar information management method to a first calendar client, where the first calendar is illustrated.
- the client may be a calendar client installed on the first terminal 120 in the implementation environment shown in FIG. 1.
- the calendar information management method may include the following steps:
- step 301 the original calendar information is displayed.
- step 302 an update instruction to the original calendar information is received.
- step 303 according to the update instruction, the content indicated by the update instruction in the original calendar information is modified, and To share calendar information.
- step 304 the shared calendar information is issued to the server such that the server is used to push the shared calendar information to the second calendar client.
- the second calendar client is a calendar client that is logged in by the second user account
- the first calendar client is a calendar client that is logged in by the first user account
- the second user account is associated with the first user account.
- the first calendar client receives an update instruction for the original calendar information by displaying the original calendar information, and updates the content indicated by the instruction in the original calendar information according to the update instruction. Modifying, obtaining shared calendar information, and publishing shared calendar information to the server, so that the server pushes the shared calendar information to the second calendar client, because the shared calendar information pushed by the server to the second calendar client is the first calendar client pair.
- the original calendar information displayed by the first calendar client is modified, thereby avoiding the problem that the accuracy of the calendar information is low. Therefore, the problem of low accuracy of calendar information management in the related art is solved, and the calendar information is improved. The effect of managing the accuracy.
- step 303 can include:
- the prompt information is used to prompt the user to modify the content indicated by the update instruction in the original calendar information
- the original calendar information includes date information and event information
- the event information is used to indicate an event occurring on a date corresponding to the date information.
- Step 303 can include:
- the method may further include:
- the third original calendar information is that the third calendar client adds the corresponding event information to the server on the specified date page of the calendar interface displayed by the third calendar client, and is distributed to the server, and the third The user account logged in the calendar client is associated with the first user account.
- the method further includes:
- updating the first original calendar information by using the third original calendar information to obtain the original calendar information including:
- the first original calendar information is replaced with the third original calendar information to obtain the original calendar information.
- updating the first original calendar information by using the third original calendar information to obtain the original calendar information including:
- the third original calendar information and the first original calendar information are combined to obtain original calendar information.
- the method may further include:
- the first calendar client receives an update instruction for the original calendar information by displaying the original calendar information, and updates the content indicated by the instruction in the original calendar information according to the update instruction. Modifying, obtaining shared calendar information, and publishing shared calendar information to the server, so that the server pushes the shared calendar information to the second calendar client, because the shared calendar information pushed by the server to the second calendar client is the first calendar client pair.
- the original calendar information displayed by the first calendar client is modified, thereby avoiding the problem that the accuracy of the calendar information is low. Therefore, the problem of low accuracy of calendar information management in the related art is solved, and the calendar information is improved. The effect of managing the accuracy.
- FIG. 4 is a flowchart of a method for managing a calendar information according to still another exemplary embodiment. The embodiment is illustrated by applying the calendar information management method to a second calendar client, where the second calendar is illustrated.
- the client may be a calendar client installed on the second terminal 140 in the implementation environment shown in FIG. 1.
- the calendar information management method may include the following steps:
- step 401 the shared calendar information pushed by the server is received, and the shared calendar information is sent by the server to the second calendar client after receiving the shared calendar information published by the first calendar client, and the second calendar client is the second user account.
- the registered calendar client, the first calendar client is a calendar client that is logged in by the first user account, the second user account is associated with the first user account, and the shared calendar information is displayed by the first calendar client to the first calendar client.
- the original calendar information was modified.
- the second original calendar information is updated by using the shared calendar information, and the second original calendar information is obtained by adding the corresponding event information to the specified date page of the calendar interface displayed by the second calendar client by the second calendar client.
- the second calendar client receives the shared calendar information pushed by the server, and updates the second original calendar information by using the shared calendar information, because the server sends the second calendar client to the second calendar client.
- the pushed shared calendar information is obtained by modifying the original calendar information displayed by the first calendar client by the first calendar client, thereby avoiding the problem that the calendar information is less accurate, and therefore solving the calendar information management in the related art.
- the problem of lower accuracy has the effect of improving the accuracy of calendar information management.
- step 402 may include:
- step 402 may include:
- the shared calendar information and the second original calendar information are merged.
- the second calendar client receives the server The shared calendar information is pushed, and the second calendar information is updated by using the shared calendar information.
- the shared calendar information pushed by the server to the second calendar client is the first calendar client modifying the original calendar information displayed by the first calendar client.
- 5-1 is a flowchart of a method for managing a calendar information according to another exemplary embodiment. The embodiment is described by using the calendar information management method in the implementation environment shown in FIG.
- the first calendar client is installed on the first terminal 120
- the second calendar client is installed on the second terminal 140
- the third calendar client is installed on the third terminal 160.
- the calendar information management method may include the following steps:
- step 501 the third calendar client adds corresponding event information to the specified date page of the calendar interface displayed by the third calendar client to obtain third original calendar information.
- the calendar interface displayed by the third calendar client may be as shown in FIG. 5-2.
- the current login user account in the third calendar client is: xiaomi123
- the calendar interface displayed by the third calendar client is displayed.
- the calendar for September 2015 is displayed.
- September 2015 there are 30 dates.
- Each date can correspond to a date page.
- Users who use the third calendar client can specify the date on the calendar interface shown in Figure 5-2.
- the event that occurs on the corresponding date is the specified date.
- a user who uses the third calendar client can add event information "3:30 pm, XX company holds a job fair at the school gymnasium" on the date page corresponding to the date on September 12, so that the third original calendar information is obtained, therefore,
- the three original calendar information can be "September 12 at 3:30 pm, XX company held a job fair at the school gym.”
- the calendar interface displayed by the third calendar client may display the third original calendar information.
- the calendar interface displayed by the third calendar client may display partial information of the third original calendar information, and when the user using the third calendar client clicks the partial information, the calendar interface displayed by the third calendar client displays complete The third original calendar information, for example, as shown in FIG. 5-2, on the calendar interface displayed by the third calendar client, the “recruitment meeting” is displayed on the corresponding date page on September 12, when the third calendar client is used.
- the calendar interface displayed by the third calendar client displays the complete third original calendar information
- the calendar interface displayed by the third calendar client displays the complete third original calendar information as shown in Figure 5-3. Shown.
- step 502 the third calendar client issues third original calendar information to the server.
- the third calendar client After the third calendar client obtains the third original calendar information, the third original calendar information that can be released to the server.
- the third calendar client issues a third original calendar information to the server "3:30 pm on September 12, and XX company holds a job fair at the school gym.”
- step 503 the server receives the third original calendar information issued by the third calendar client.
- the server may receive the third original calendar information published by the third calendar client.
- the server receives the third original calendar information "3:30 pm on September 12, XX company holds a job fair at the school gym.”
- step 504 the server pushes the third original calendar information to the first calendar client, the user account logged in the first calendar client is the first user account, and the user account and the first user account logged in the third calendar client Association.
- the server may push the original calendar information to the first calendar client.
- the first calendar client is a calendar client that is logged in by the first user account, and the first user account is associated with the user account logged in the third calendar client.
- the server pushes the third original calendar information to the first calendar client "3:30 pm on September 12, XX company holds a job fair at the school gym.”
- the user account registered in the first calendar client is the first user account
- the user account registered in the third calendar client is associated with the first user account.
- the user account is xiaoxiao111
- the first user account xiaoxiao111 is associated with the login user account xiaomi123 in the third calendar client.
- step 505 the first calendar client receives the third original calendar information pushed by the server.
- the first calendar client may receive the third original calendar information pushed by the server.
- the first calendar client receives the third original calendar information “September 12th At 3:30 in the afternoon, XX company held a job fair at the school gym.
- step 506 the first calendar client updates the first original calendar information with the third original calendar information to obtain the original calendar information.
- the first calendar client may update the first original calendar information to obtain the original calendar information by using the third original calendar information, where the first original calendar information is the first calendar client at the first
- the corresponding event information is added to the specified date page of the calendar interface displayed by the calendar client.
- the first original calendar information may be “3:30 pm on September 13 and XX company holds a job fair at the school gym”, and the calendar interface displayed by the first calendar client may be as shown in FIG. 5-4.
- FIG. 5-4 For the description of the corresponding figure in FIG. 5-4, reference may be made to the description in FIG. 5-2 in step 501, and the embodiments of the present disclosure are not described herein again.
- the first calendar client uses the third original calendar information "3:30 pm on September 12, XX company holds a job fair at the school gymnasium" to update the first original calendar information "September 13 at 3:30 pm, XX The company held a job fair at the school gym.”
- the first calendar client updates the first original calendar information by using the third original calendar information to obtain the original calendar information, which may include the following two methods:
- Method 1 The first calendar client replaces the first original calendar information with the third original calendar information to obtain the original calendar information.
- the first calendar client may determine date information and event information in the third original calendar information, and then add the event information in the third original calendar information to the date page corresponding to the date information in the original calendar information. And deleting the first original calendar information to obtain the original calendar information, wherein the original calendar information is also the third Original calendar information, by way of example, the first calendar client uses the third original calendar information "3:30 pm on September 12, XX company holds a job fair at the school gymnasium" to replace the first original calendar information "September 13 afternoon 3 Half point, XX company held a job fair in the school gymnasium.
- the interface diagram of the original calendar information can be shown in Figure 5-5. See Figure 5-5.
- the original calendar information can be "September 12 at 3:30 pm, XX The company held a job fair at the school gym.”
- the first calendar client combines the third original calendar information and the first original calendar information to obtain the original calendar information.
- the first calendar client may determine date information and event information in the third original calendar information, and then add the event information in the third original calendar information to the date page corresponding to the date information in the original calendar information. , get the original calendar information.
- the first calendar client will have the third original calendar information "3:30 pm on September 12, XX company holds a job fair at the school gymnasium" and the first original calendar information "September 13 at 3:30 pm, XX The company holds a job fair at the school gymnasium.
- the interface diagram of the original calendar information can be as shown in Figure 5-6. See Figure 5-6.
- the original calendar information can be “September 12 at 3:30 pm, XX company is at The school gymnasium held a job fair" and "September 13 at 3:30 pm, XX company held a job fair at the school gymnasium.”
- the original calendar information is obtained by the first calendar client updating the first original calendar information by using the third original calendar information.
- the original calendar information may also be The first calendar client is obtained by adding corresponding event information to the specified date page of the calendar interface displayed by the first calendar client, wherein the first calendar client is in the specified date page of the calendar interface displayed by the first calendar client.
- the process of adding the corresponding event information to obtain the original calendar information is the same as the process of adding the corresponding event information to the third calendar client in the specified date page of the calendar interface displayed by the third calendar client in step 501 to obtain the third original calendar information.
- the implementation process may refer to step 501, and details are not described herein again.
- the original calendar information is taken as an example of "September 12 at 3:30 pm, XX company held a job fair at the school gymnasium" as an example.
- step 507 the first calendar client displays the original calendar information.
- the first calendar client After receiving the original calendar information pushed by the server, the first calendar client can display the original calendar information. For example, the first calendar client displays the original calendar information. “September 12th at 3:30 pm, XX company holds recruitment at the school gymnasium. meeting”.
- the first calendar client may add the event information in the original calendar information to the date page corresponding to the date indicated by the date information in the original calendar information, and in the first calendar client.
- the display is performed on the display interface of the terminal, which is not limited by the embodiment of the present disclosure.
- step 508 the first calendar client receives an update instruction to the original calendar information.
- the original calendar information may have information that does not conform to the actual situation, resulting in low accuracy of the original calendar information. For example, it is assumed that the recruitment meeting of the XX company is 3:30 pm on September 15. At the school gymnasium, the original calendar information displayed by the first calendar client is "3:30 pm on September 12, XX company holds a job fair at the school gym", so the accuracy of the original calendar information is low.
- the user who uses the first calendar client can enter the original calendar information.
- the user who uses the first calendar client can modify the content of the original calendar information, and can also add new information to the original calendar information, which is not limited by the embodiment of the present disclosure.
- an update instruction to the original calendar information may be triggered, and the first calendar client may receive the update instruction, for example, A calendar client receives an update instruction to the original calendar information "3:30 pm on September 12, XX company held a job fair at the school gymnasium".
- step 509 the first calendar client modifies the content indicated by the update instruction in the original calendar information according to the update instruction to obtain shared calendar information.
- the first calendar client may modify the content indicated by the update instruction in the original calendar information according to the update instruction to obtain the shared calendar information.
- FIG. 5-7 shows that a first calendar client provided by the embodiment shown in FIG. 5-1 modifies the content indicated by the update instruction in the original calendar information according to the update instruction, and obtains A flow chart of a method for sharing calendar information, see FIG. 5-7, the method flow may include the following steps:
- step 5091 the first calendar client displays a prompt message for prompting the user to modify the content indicated by the update instruction in the original calendar information.
- the first calendar client may display prompt information, which is used to prompt the user to modify the content indicated by the update instruction in the original calendar information.
- the prompt information may be: “ Confirm the modification of the calendar information?”
- the interface of the first calendar client to display the prompt information can be as shown in Figure 5-8. See Figure 5-8.
- the calendar interface displays a prompt box with a prompt message. Confirm the modification of the calendar information?" and the "confirm" button.
- step 5092 upon receiving the user-initiated confirmation instruction to modify, the first calendar client modifies the content indicated by the update instruction in the original calendar information.
- the user can perform an operation to trigger the confirmation instruction to modify the prompt information.
- the first calendar client may modify the content indicated by the update instruction in the original calendar information.
- the original calendar information may include date information and event information, and the event information is used to indicate an event that occurs on a date corresponding to the date information. Therefore, the first calendar client modifies the content indicated by the update instruction in the original calendar information according to the update instruction.
- the method may include: modifying, by the first calendar client, at least one of date information and event information according to the update instruction. That is, the first calendar client may modify the event information in the original calendar information, and may also modify the date information in the original calendar information, which is not limited by the embodiment of the present disclosure.
- the first calendar client modifies the date information in the original calendar information, and when the content indicated by the update instruction is event information, the first calendar client pairs the original calendar. The event information in the message is modified.
- the first calendar client may modify the date information in the original calendar information according to the update instruction to obtain a sharing date.
- Calendar information for example, the shared calendar information obtained by modifying the date information in the original calendar information by the first calendar client may be "3:30 pm on September 15th, and XX company holds a job fair at the school gymnasium".
- the first calendar client modifies the content indicated by the update instruction in the original calendar information according to the update instruction, and the interface diagram obtained after the shared calendar information is obtained may be as shown in FIG. 5-9.
- step 510 the first calendar client issues shared calendar information to the server.
- the shared calendar information may be released to the server.
- the first calendar client issues the shared calendar information to the server. "September 15th, 3:30 pm, XX The company held a job fair at the school gym.”
- step 511 the server receives the shared calendar information published by the first calendar client.
- the server may receive the shared calendar information published by the first calendar client. For example, the server receives the shared calendar information. "September 15th at 3:30 pm, XX company is at the school gymnasium. Hold a job fair.”
- step 512 the server obtains a second user account associated with the first user account.
- the server may obtain the second user account associated with the first user account. For example, the server acquires the user account associated with the first user account xiaoxiao 111.
- the user account that subscribes to the same subscription account may be an associated user account. Therefore, the server may determine the second user account associated with the first user account according to the subscription account of the first user account.
- FIG. 5-10 is a flowchart of a method for a server to obtain a second user account associated with a first user account according to the embodiment shown in FIG. 5-1. See FIG. 5-10.
- the method flow can include:
- the server obtains a subscription account for the first user account.
- the server obtains the subscription account dingyue1.
- the server may store the correspondence between the user account and the subscription account, and the server obtains the subscription account of the first user account according to the correspondence between the user account and the subscription account.
- the user account and the subscription account stored by the server are The correspondence can be as shown in Table 1 below:
- the server can query the corresponding relationship shown in Table 1 according to the first user account xiaoxiao111, obtain the subscription account dingyue1 of the first user account xiaoxiao111, and obtain the subscription account dingyue1.
- the server obtains other user accounts that subscribe to the subscription account, and the other user accounts do not include the first user account.
- the server may obtain another user account that subscribes to the subscription account, and the other user account does not include the first user account. For example, the server obtains other user accounts that subscribe to the subscription account dingyue1.
- other user accounts that subscribe to the subscription account dingyue1 include: user account xiaomi111 and user account Huawei112.
- the server can query the corresponding relationship shown in Table 1 according to the subscription account dingyue1, and obtain other user accounts xiaomi111 of the subscription subscription account dingyue1.
- the server uses the other user account as the second user account.
- the server After the server obtains another user account that subscribes to the subscription account, the other user account is used as the second user account.
- the server uses the user accounts xiaomi111 and Huawei 112 as the second user account.
- the user account xiaomi 111 is a user account that is logged in the third calendar client. Therefore, in order to facilitate the subsequent description, the embodiment of the present disclosure uses the second user account as the user account Huawei 112 as an example for description.
- the server also stores the correspondence between the user accounts Huawei 112, Huaweii 001, Huawei 002, and the subscription account dingyue2, wherein the Huawei 112, the Huaweii 001, and the Huawei 002 are all subscribed to the subscription account dingyue 2, and the embodiments of the present disclosure are not described herein.
- the user account that subscribes to the first user account may be the user account associated with the first user account. Therefore, the server may determine the user account that subscribes to the first user account, and the user account that subscribes to the first user account. That is, the second user account associated with the first user account.
- FIG. 5-11 is a flowchart of a method for another server provided by the embodiment shown in FIG. 5-1 to obtain a second user account associated with a first user account. 11.
- the method flow can include:
- the server obtains a user account that subscribes to the first user account.
- the server may store the correspondence between the user account and the subscription account, and the server may obtain the user account that subscribes to the first user account.
- the correspondence between the user account and the subscription account stored by the server may be as shown in Table 2 below. Show:
- the server queries the corresponding relationship shown in Table 2, and obtains the user account that subscribes to the first user account xiaoxiao111.
- the user accounts that subscribe to the first user account xiaoxiao111 include: xiaomi111, Huawei112, and Huaweii002. Therefore, the server obtains the user account xiaomi111. , Huawei 112 and Huaweii002.
- the server subscribes the user account of the first user account as the second user account.
- the server After the server obtains the user account that subscribes to the first user account, the user account that subscribes to the first user account is used as the second user account. For example, the server uses the user accounts xiaomi111, Huawei 112, and Huawei 002 as the second user account.
- the embodiment of the present disclosure uses the second user account as the user account Huawei 112 as an example for description.
- the user account association list may be manually configured, and the user account association list records the association relationship of each user account, and the server may store the user account association list, and obtain the first user according to the user account association list.
- the second user account associated with the account For example, please refer to FIG. 5-12, which is a flowchart of a method for obtaining a second user account associated with a first user account by another server provided by the embodiment shown in FIG. 5-1, see FIG. 5 - 12.
- the method flow can include:
- the server queries the preset user account association list according to the first user account, and the user account association list records the association relationship of each user account.
- the preset user account association list can be as shown in Table 3 below:
- the user accounts stored by the server are xiaoxiao111 and Huaweii001, wherein the user accounts associated with the user account xiaoxiao111 are Huawei 112 and Huawei 111, and the user account associated with the user account Huaweii 001 is Xiaomi 002.
- the server can determine, according to the first user account xiaoxiao 111, the user account association list shown in Table 1 that the user accounts associated with the first user account xiaoxiao 111 are Huawei 112 and Huawei 111.
- the server queries the user account associated with the first user account obtained from the user account association list as the second user account.
- the server After the server queries the user account associated with the first user account, the user account associated with the first user account is used as the second user account. For example, the server uses the user accounts Huawei 112 and xiaomi 111 as the second user account.
- the embodiment of the present disclosure uses the second user account.
- the number is the user account Huawei 112 as an example.
- step 513 the server pushes the shared calendar information to the second calendar client, and the second calendar client is the calendar client to which the second user account logs in.
- the server pushes the shared calendar information to the second calendar client, where the second calendar client is the calendar client that the second user account logs in, for example, the second The user account registered in the calendar client is Huawei 112, and the server pushes the shared calendar information to the second calendar client. "September 15th at 3:30 pm, XX company holds a job fair at the school gym.”
- step 514 the second calendar client receives the shared calendar information pushed by the server.
- the second calendar client may receive the shared calendar information pushed by the server.
- the second calendar client receives the shared calendar information pushed by the server "September 15 afternoon At 3:30, XX company held a job fair at the school gymnasium.”
- step 515 the second calendar client updates the second original calendar information with the shared calendar information.
- the step 515 is the same as or similar to the above step 506.
- the implementation process may refer to step 506.
- the embodiment of the present disclosure will not be described herein again.
- the second original calendar information is the second.
- the calendar client obtains the corresponding event information in the specified date page of the calendar interface displayed by the second calendar client.
- the server receives the shared calendar information published by the first calendar client, and the shared calendar information is the original calendar information displayed by the first calendar client to the first calendar client. Making the modified; pushing the shared calendar information to the second calendar client, so that the second calendar client updates the second original calendar information with the shared calendar information, and the second original calendar information is the second calendar client at the second calendar client.
- the corresponding event information is added to the specified date page of the calendar interface displayed on the side. Since the shared calendar information is obtained by modifying the original calendar information displayed by the first calendar client by the first calendar client, the problem that the accuracy of the calendar information is low is avoided, thereby solving the accuracy of the calendar information management in the related art. The problem of lower sex has achieved the effect of improving the accuracy of calendar information management.
- FIG. 6 is a block diagram of a calendar information management apparatus 600, which may be implemented as a server 180 in the implementation environment shown in FIG. 1 by software, hardware, or a combination of both, according to an exemplary embodiment. Part or all, referring to FIG. 6, the calendar information management apparatus 600 may include:
- the first receiving module 610 is configured to receive shared calendar information published by the first calendar client, where the shared calendar information is obtained by modifying, by the first calendar client, the original calendar information displayed by the first calendar client.
- the first pushing module 620 is configured to push the shared calendar information received by the first receiving module 610 to the second calendar client, so that the second calendar client updates the second original calendar information by using the shared calendar information, and the second original calendar
- the information is obtained by adding the corresponding event information to the second calendar client in the specified date page of the calendar interface displayed by the second calendar client, and the second calendar client is the calendar client that is logged in by the second user account, and the first calendar client
- the end is a calendar client to which the first user account is logged in, and the second user account is associated with the first user account.
- the server receives the shared calendar information published by the first calendar client, and the shared calendar information is the original calendar information displayed by the first calendar client to the first calendar client. Making the modified; pushing the shared calendar information to the second calendar client, so that the second calendar client updates the second original calendar information with the shared calendar information, and the second original calendar information is the second calendar client at the second calendar client.
- the corresponding event information is added to the specified date page of the calendar interface displayed on the side. Since the shared calendar information is obtained by modifying the original calendar information displayed by the first calendar client by the first calendar client, the problem that the accuracy of the calendar information is low is avoided, thereby solving the accuracy of the calendar information management in the related art. The problem of lower sex has achieved the effect of improving the accuracy of calendar information management.
- FIG. 7 is a block diagram of another calendar information management apparatus 600, which may be implemented as a server 180 in the implementation environment shown in FIG. 1 by software, hardware, or a combination of both, according to an exemplary embodiment. Part or all of, referring to FIG. 7, the calendar information management apparatus 600 may include:
- the first receiving module 610 is configured to receive shared calendar information published by the first calendar client, where the shared calendar information is obtained by modifying, by the first calendar client, the original calendar information displayed by the first calendar client.
- the first pushing module 620 is configured to push the shared calendar information received by the first receiving module 610 to the second calendar client, so that the second calendar client updates the second original calendar information by using the shared calendar information, and the second original calendar
- the information is obtained by adding the corresponding event information to the second calendar client in the specified date page of the calendar interface displayed by the second calendar client, and the second calendar client is the calendar client that is logged in by the second user account, and the first calendar client
- the end is a calendar client to which the first user account is logged in, and the second user account is associated with the first user account.
- the original calendar information is obtained by the first calendar client updating the first original calendar information by using the third original calendar information
- the third original calendar information is the calendar interface displayed by the third calendar client on the third calendar client.
- Adding corresponding event information to the specified date page and publishing to the server is pushed by the server to the first calendar client
- the first original calendar information is the first calendar client in the specified date page of the calendar interface displayed by the first calendar client.
- the original calendar information is obtained by adding the corresponding event information, and the original calendar information includes: date information and event information, and the event information is used to indicate an event that occurs on the date corresponding to the date information.
- the calendar information management apparatus 600 may further include:
- the second receiving module 630 is configured to receive third original calendar information issued by the third calendar client, where the user account registered in the third calendar client is associated with the first user account;
- the second pushing module 640 is configured to push the third original calendar information received by the second receiving module 630 to the first calendar client.
- the original calendar information is obtained by adding, by the first calendar client, the corresponding event information in the specified date page of the calendar interface displayed by the first calendar client, where the original calendar information includes: date information and event information, and event information is used. An event that occurs on the date indicated by the date information.
- the calendar information management apparatus 600 may further include:
- the obtaining module 650 is configured to acquire a second user account associated with the first user account.
- the obtaining module 650 is configured to:
- the obtaining module 650 is configured to:
- the user account that subscribes to the first user account is used as the second user account.
- the obtaining module 650 is configured to:
- the user account associated with the first user account obtained from the user account association list is used as the second user account.
- the server receives the shared calendar information published by the first calendar client, and the shared calendar information is the original calendar information displayed by the first calendar client to the first calendar client. Making the modified; pushing the shared calendar information to the second calendar client, so that the second calendar client updates the second original calendar information with the shared calendar information, and the second original calendar information is the second calendar client at the second calendar client.
- the corresponding event information is added to the specified date page of the calendar interface displayed on the side. Since the shared calendar information is obtained by modifying the original calendar information displayed by the first calendar client by the first calendar client, the problem that the accuracy of the calendar information is low is avoided, thereby solving the accuracy of the calendar information management in the related art. The problem of lower sex has achieved the effect of improving the accuracy of calendar information management.
- FIG. 8 is a block diagram of a calendar information management apparatus 700, which may be implemented as part or all of a first calendar client by software, hardware, or a combination of both, according to another exemplary embodiment.
- the first calendar client may be a calendar client installed on the first terminal 120 in the implementation environment shown in FIG. 1.
- the calendar information management apparatus 700 may include:
- the display module 710 is configured to display original calendar information.
- the first receiving module 720 is configured to receive an update instruction of the original calendar information displayed by the display module 710.
- the modification module 730 is configured to compare the original calendar information according to the update instruction received by the first receiving module 720.
- the content indicated by the update instruction is modified to obtain shared calendar information.
- the publishing module 740 is configured to issue the shared calendar information obtained by the modification module 730 to the server, so that the server pushes the shared calendar information to the second calendar client, where the second calendar client is the calendar client that the second user account logs in, A calendar client is a calendar client to which the first user account is logged in, and the second user account is associated with the first user account.
- the first calendar client receives the update instruction of the original calendar information by displaying the original calendar information, and updates the content indicated by the instruction in the original calendar information according to the update instruction. Modifying, obtaining shared calendar information, and publishing shared calendar information to the server, so that the server pushes the shared calendar information to the second calendar client, because the shared calendar information pushed by the server to the second calendar client is the first calendar client pair.
- the original calendar information displayed by the first calendar client is modified, thereby avoiding the problem that the accuracy of the calendar information is low. Therefore, the problem of low accuracy of calendar information management in the related art is solved, and the calendar information is improved. The effect of managing the accuracy.
- FIG. 9 is a block diagram of another calendar information management apparatus 700, which may be implemented as part or all of a first calendar client by software, hardware, or a combination of both, according to another exemplary embodiment.
- the first calendar client may be a calendar client installed on the first terminal 120 in the implementation environment shown in FIG. 1.
- the calendar information management apparatus 700 may include:
- the display module 710 is configured to display original calendar information.
- the first receiving module 720 is configured to receive an update instruction of the original calendar information displayed by the display module 710.
- the modification module 730 is configured to modify the content indicated by the update instruction in the original calendar information according to the update instruction received by the first receiving module 720 to obtain shared calendar information.
- the publishing module 740 is configured to issue the shared calendar information obtained by the modification module 730 to the server, so that the server pushes the shared calendar information to the second calendar client, where the second calendar client is the calendar client that the second user account logs in, A calendar client is a calendar client to which the first user account is logged in, and the second user account is associated with the first user account.
- the modification module 730 is configured to:
- the prompt information is used to prompt the user to modify the content indicated by the update instruction in the original calendar information
- the original calendar information includes date information and event information
- the event information is used to indicate an event occurring on a date corresponding to the date information.
- the modification module 730 is configured to:
- the calendar information management apparatus 700 may further include:
- the second receiving module 750 is configured to receive third original calendar information pushed by the server, where the third original calendar information is that the third calendar client adds corresponding event information to the specified date page of the calendar interface displayed by the third calendar client.
- the user account registered in the third calendar client is obtained and published to the server, and is associated with the first user account.
- the calendar information management apparatus 700 may further include:
- the update module 760 is configured to update the first original calendar information by using the third original calendar information received by the second receiving module 750 to obtain original calendar information, where the first original calendar information is displayed by the first calendar client on the first calendar client.
- the corresponding event information is added to the specified date page of the calendar interface.
- the updating module 760 is configured to: replace the first original calendar information with the third original calendar information received by the second receiving module 750 to obtain original calendar information.
- the updating module 760 is configured to combine the third original calendar information received by the second receiving module 750 and the first original calendar information to obtain original calendar information.
- the calendar information management apparatus 700 may further include:
- the adding module 770 is configured to add corresponding event information to the specified date page of the calendar interface displayed by the first calendar client to obtain original calendar information.
- the first calendar client receives the update instruction of the original calendar information by displaying the original calendar information, and updates the content indicated by the instruction in the original calendar information according to the update instruction. Modifying, obtaining shared calendar information, and publishing shared calendar information to the server, so that the server pushes the shared calendar information to the second calendar client, because the shared calendar information pushed by the server to the second calendar client is the first calendar client pair.
- the original calendar information displayed by the first calendar client is modified, thereby avoiding the problem that the accuracy of the calendar information is low. Therefore, the problem of low accuracy of calendar information management in the related art is solved, and the calendar information is improved. The effect of managing the accuracy.
- FIG. 10 is a block diagram of a calendar information management apparatus 800, which may be implemented as part or all of a second calendar client by software, hardware, or a combination of both, according to still another exemplary embodiment.
- the second calendar client may be a calendar client installed on the second terminal 140 in the implementation environment shown in FIG. 1.
- the calendar information management apparatus 800 may include:
- the receiving module 810 is configured to receive shared calendar information pushed by the server, where the shared calendar information is sent by the server to the second calendar client after receiving the shared calendar information published by the first calendar client, and the second calendar client is logged in.
- a calendar client of the second user account the first calendar client is a calendar client to which the first user account is logged in, the second user account is associated with the first user account, and the shared calendar information is the first calendar client to the first calendar client
- the original calendar information displayed on the side is modified;
- the update module 820 is configured to update the second original calendar information by using the shared calendar information received by the receiving module 810, where the second original calendar information is in the specified date page of the calendar interface displayed by the second calendar client. Add the corresponding event information to get.
- the update module 820 is configured to:
- the second original calendar information is replaced with the shared calendar information received by the receiving module 810.
- the update module 820 is configured to:
- the shared calendar information received by the receiving module 810 and the second original calendar information are merged.
- the calendar information management apparatus receives the shared calendar information pushed by the server, and updates the second original calendar information by using the shared calendar information, because the server sends the second calendar client to the second calendar client.
- the pushed shared calendar information is obtained by modifying the original calendar information displayed by the first calendar client by the first calendar client, thereby avoiding the problem that the calendar information is less accurate, and therefore solving the calendar information management in the related art.
- the problem of lower accuracy has the effect of improving the accuracy of calendar information management.
- FIG. 11 is a block diagram of a calendar information management apparatus 1100 according to an exemplary embodiment.
- device 1100 can be provided as a server.
- apparatus 1100 includes a processing component 1122 that further includes one or more processors, and memory resources represented by memory 1132 for storing instructions, such as applications, that are executable by processing component 1122.
- An application stored in memory 1132 can include one or more modules each corresponding to a set of instructions.
- the processing component 1122 is configured to execute instructions to perform the calendar information management method described above, the method comprising:
- the second calendar client updates the second original calendar information with the shared calendar information
- the second original calendar information is the calendar interface displayed by the second calendar client on the second calendar client.
- the corresponding calendar information is added to the specified date page
- the second calendar client is the calendar client to which the second user account is logged in
- the first calendar client is the calendar client to which the first user account is logged in
- the second user account is The first user account is associated.
- the original calendar information is obtained by the first calendar client updating the first original calendar information by using the third original calendar information
- the third original calendar information is the calendar interface displayed by the third calendar client on the third calendar client.
- Adding corresponding event information to the specified date page and publishing to the server is pushed by the server to the first calendar client, and the first original calendar information is the first calendar client in the specified date page of the calendar interface displayed by the first calendar client.
- the original calendar information is obtained by adding corresponding event information, including: date information and event information, and the event information is used to indicate an event occurring on a date corresponding to the date information;
- the method further includes:
- the original calendar information is obtained by adding, by the first calendar client, the corresponding event information in the specified date page of the calendar interface displayed by the first calendar client, where the original calendar information includes: date information and event information, and event information is used. An event that occurs on the date indicated by the date information.
- the method before the shared calendar information is pushed to the second calendar client, the method further includes:
- obtaining a second user account associated with the first user account including:
- obtaining a second user account associated with the first user account including:
- the user account that subscribes to the first user account is used as the second user account.
- obtaining a second user account associated with the first user account including:
- the user account associated with the first user account obtained from the user account association list is used as the second user account.
- the device 1100 can also include a power supply component 1126 configured to perform power management of the device 1100, a wired or wireless network interface 1150 configured to connect the device 1100 to the network, and an input/output (I/O) interface 1158.
- Apparatus 1100 may operate based on an operating system stored in the memory 1132, for example, Windows Server TM, Mac OS X TM , Unix TM, Linux TM, FreeBSD TM or the like.
- the calendar information management apparatus receives the shared calendar information published by the first calendar client, and the shared calendar information is performed by the first calendar client on the original calendar information displayed by the first calendar client. Modifying the shared calendar information to the second calendar client, so that the second calendar client updates the second original calendar information with the shared calendar information, and the second original calendar information is the second calendar client at the second calendar client The corresponding event information is added to the specified date page of the displayed calendar interface. Since the shared calendar information is obtained by modifying the original calendar information displayed by the first calendar client by the first calendar client, the problem that the accuracy of the calendar information is low is avoided, thereby solving the accuracy of the calendar information management in the related art. The problem of lower sex has achieved the effect of improving the accuracy of calendar information management.
- FIG. 12 is a block diagram of an apparatus 1200 for calendar information management, according to another exemplary embodiment.
- the calendar information management device 1200 can be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, a fitness device, a personal digital assistant, etc.
- the calendar information management device 1200 can The calendar client is installed, and the calendar information management device 1200 manages the calendar information through the calendar client.
- apparatus 1200 can include one or more of the following components: processing component 1202, memory 1204, power component 1206, multimedia component 1208, audio component 1210, input/output (I/O) interface 1212, sensor component 1214, and Communication component 1216.
- Processing component 1202 typically controls the overall operations of device 1200, such as operations associated with display, data communication, and recording operations.
- Processing component 1202 can include one or more processors 1220 to execute instructions to perform all or part of the steps described above.
- processing component 1202 can include one or more modules to facilitate interaction between component 1202 and other components.
- processing component 1202 can include a multimedia module to facilitate interaction between multimedia component 1208 and processing component 1202.
- Memory 1204 is configured to store various types of data to support operation at device 1200. Examples of such data include instructions for any application or method operating on device 1200, contact data, phone book data, messages, pictures, videos, calendar data, and the like.
- the memory 1204 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read only memory (EEPROM), erasable Programmable Read Only Memory (EPROM), Programmable Read Only Memory (PROM), Read Only Memory (ROM), Magnetic Memory, Flash Memory, Disk or Optical Disk.
- SRAM static random access memory
- EEPROM electrically erasable programmable read only memory
- EPROM erasable Programmable Read Only Memory
- PROM Programmable Read Only Memory
- ROM Read Only Memory
- Magnetic Memory Flash Memory
- Disk Disk or Optical Disk.
- Power component 1206 provides power to various components of device 1200.
- Power component 1206 can include a power management system, one or more power sources, and other components associated with generating, managing, and distributing power for device 1200.
- the multimedia component 1208 includes a screen between the device 1200 and the user that provides an output interface.
- the screen can include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen can be implemented as a touch screen to receive input signals from the user.
- the touch panel includes one or more touch sensors to sense touches, slides, and gestures on the touch panel. The touch sensor can sense not only the boundaries of the touch or sliding action, but also the duration and pressure associated with the touch or slide operation.
- the audio component 1210 is configured to output and/or input an audio signal.
- audio component 1210 includes a microphone (MIC) that is configured to receive an external audio signal when device 1200 is in an operational mode, such as a recording mode and a voice recognition mode.
- the received audio signal may be further stored in memory 1204 or transmitted via communication component 1216.
- audio component 1210 also includes a speaker for outputting an audio signal.
- the I/O interface 1212 provides an interface between the processing component 1202 and the peripheral interface module, which may be a keyboard, a click wheel, a button, or the like. These buttons may include, but are not limited to, a home button, a volume button, a start button, and a lock button.
- Sensor assembly 1214 includes one or more sensors for providing status assessment of various aspects to device 1200.
- sensor assembly 1214 can detect an open/closed state of device 1200, a relative positioning of components, such as a display and a keypad of device 1200, and sensor component 1214 can also detect a change in position of a component of device 1200 or device 1200, the user The presence or absence of contact with device 1200, device 1200 orientation or acceleration/deceleration and temperature change of device 1200.
- Sensor assembly 1214 can include a proximity sensor configured to detect the presence of nearby objects without any physical contact.
- Sensor assembly 1214 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications.
- the sensor assembly 1214 can also include an acceleration sensor, a gyro sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.
- Communication component 1216 is configured to facilitate wired or wireless communication between device 1200 and other devices.
- the device 1200 can access a wireless network based on a communication standard, such as WiFi, 2G or 3G, or a combination thereof.
- communication component 1216 receives broadcast signals or broadcast associated information from an external broadcast management system via a broadcast channel.
- communication component 1216 also includes a near field communication (NFC) module to facilitate short range communication.
- NFC near field communication
- the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.
- RFID radio frequency identification
- IrDA infrared data association
- UWB ultra-wideband
- Bluetooth Bluetooth
- device 1200 may be implemented by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable A gate array (FPGA), controller, microcontroller, microprocessor, or other electronic component implementation for performing the above methods.
- ASICs application specific integrated circuits
- DSPs digital signal processors
- DSPDs digital signal processing devices
- PLDs programmable logic devices
- FPGA field programmable A gate array
- controller microcontroller, microprocessor, or other electronic component implementation for performing the above methods.
- non-transitory computer readable storage medium comprising instructions, such as a memory 1204 comprising instructions executable by processor 1220 of apparatus 1200 to perform the above method.
- the non-transitory computer readable storage medium can be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, and an optical data storage device.
- a non-transitory computer readable storage medium when instructions in a storage medium are executed by a processor of apparatus 1200, to enable apparatus 1200 to perform a calendar information management method, the method comprising:
- the shared calendar information is issued to the server, so that the server pushes the shared calendar information to the second calendar client, the second calendar client is the calendar client that the second user account logs in, and the first calendar client is the calendar for the first user account to log in.
- the client, the second user account is associated with the first user account.
- modifying, according to the update instruction, the content indicated by the update instruction in the original calendar information including:
- the prompt information is used to prompt the user to modify the content indicated by the update instruction in the original calendar information
- the original calendar information includes date information and event information
- the event information is used to indicate an event occurring on a date corresponding to the date information.
- the content indicated by the update instruction in the original calendar information is modified, including:
- the method before displaying the original calendar information, the method further includes:
- the third original calendar information is that the third calendar client adds the corresponding event information to the server on the specified date page of the calendar interface displayed by the third calendar client, and is distributed to the server, and the third The user account logged in the calendar client is associated with the first user account.
- the method further includes:
- the first original calendar information Updating the first original calendar information by using the third original calendar information to obtain original calendar information, the first original calendar information It is obtained by adding the corresponding event information to the first calendar client in the specified date page of the calendar interface displayed by the first calendar client.
- updating the first original calendar information by using the third original calendar information to obtain the original calendar information including:
- the first original calendar information is replaced with the third original calendar information to obtain the original calendar information.
- updating the first original calendar information by using the third original calendar information to obtain the original calendar information including:
- the third original calendar information and the first original calendar information are combined to obtain original calendar information.
- the method before displaying the original calendar information, the method further includes:
- the corresponding event information is added to the specified date page of the calendar interface displayed by the first calendar client to obtain the original calendar information.
- the calendar information management apparatus receives the update instruction of the original calendar information by displaying the original calendar information, and modifies the content indicated by the update instruction in the original calendar information according to the update instruction, and obtains the sharing. Calendar information, and publishing shared calendar information to the server, so that the server pushes the shared calendar information to the second calendar client, because the server pushes the shared calendar information to the second calendar client, the first calendar client displays the first calendar client.
- the original calendar information is modified to avoid the problem of low accuracy of calendar information. Therefore, the problem of low accuracy of calendar information management in related technologies is solved, and the effect of improving the accuracy of calendar information management is achieved. .
- FIG. 13 is a block diagram of an apparatus 1300 for calendar information management, according to still another exemplary embodiment.
- the calendar information management device 1300 can be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, a fitness device, a personal digital assistant, etc.
- the calendar information management device 1300 can The calendar client is installed, and the calendar information management device 1300 manages the calendar information through the calendar client.
- apparatus 1300 can include one or more of the following components: processing component 1302, memory 1304, power component 1306, multimedia component 1308, audio component 1310, input/output (I/O) interface 1312, sensor component 1314, and Communication component 1316.
- Processing component 1302 typically controls the overall operation of device 1300, such as operations associated with display, data communication, and recording operations.
- Processing component 1302 can include one or more processors 1320 to execute instructions to perform all or part of the steps described above.
- processing component 1302 can include one or more modules to facilitate interaction between component 1302 and other components.
- processing component 1302 can include a multimedia module to facilitate interaction between multimedia component 1308 and processing component 1302.
- Memory 1304 is configured to store various types of data to support operation at device 1300. Examples of such data include instructions for any application or method operating on device 1300, contact data, phone book data, messages, pictures, videos, calendar data, and the like.
- Memory 1304 can be implemented by any type of volatile or non-volatile storage device, or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read only memory (EEPROM), erasable Programmable Read Only Memory (EPROM), Programmable Read Only Memory (PROM), Read only memory (ROM), magnetic memory, flash memory, disk or optical disk.
- SRAM static random access memory
- EEPROM electrically erasable programmable read only memory
- EPROM erasable Programmable Read Only Memory
- PROM Programmable Read Only Memory
- ROM Read only memory
- magnetic memory magnetic memory
- flash memory disk or optical disk.
- Power component 1306 provides power to various components of device 1300.
- Power component 1306 can include a power management system, one or more power sources, and other components associated with generating, managing, and distributing power for device 1300.
- the multimedia component 1308 includes a screen between the device 1300 and the user that provides an output interface.
- the screen can include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen can be implemented as a touch screen to receive input signals from the user.
- the touch panel includes one or more touch sensors to sense touches, slides, and gestures on the touch panel. The touch sensor can sense not only the boundaries of the touch or sliding action, but also the duration and pressure associated with the touch or slide operation.
- the audio component 1310 is configured to output and/or input an audio signal.
- the audio component 1310 includes a microphone (MIC) that is configured to receive an external audio signal when the device 1300 is in an operational mode, such as a recording mode and a voice recognition mode.
- the received audio signal may be further stored in memory 1304 or transmitted via communication component 1316.
- the audio component 1310 also includes a speaker for outputting an audio signal.
- the I/O interface 1312 provides an interface between the processing component 1302 and the peripheral interface module, which may be a keyboard, a click wheel, a button, or the like. These buttons may include, but are not limited to, a home button, a volume button, a start button, and a lock button.
- Sensor assembly 1314 includes one or more sensors for providing device 1300 with a status assessment of various aspects.
- the sensor assembly 1314 can detect an open/closed state of the device 1300, the relative positioning of the components, such as a display and a keypad of the device 1300, and the sensor component 1314 can also detect a change in position of a component of the device 1300 or device 1300, the user The presence or absence of contact with device 1300, device 1300 orientation or acceleration/deceleration and temperature variation of device 1300.
- Sensor assembly 1314 can include a proximity sensor configured to detect the presence of nearby objects without any physical contact.
- Sensor assembly 1314 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications.
- the sensor component 1314 can also include an acceleration sensor, a gyro sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.
- Communication component 1316 is configured to facilitate wired or wireless communication between device 1300 and other devices.
- the device 1300 can access a wireless network based on a communication standard, such as WiFi, 2G or 3G, or a combination thereof.
- communication component 1316 receives broadcast signals or broadcast associated information from an external broadcast management system via a broadcast channel.
- communication component 1316 also includes a near field communication (NFC) module to facilitate short range communication.
- NFC near field communication
- the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.
- RFID radio frequency identification
- IrDA infrared data association
- UWB ultra-wideband
- Bluetooth Bluetooth
- apparatus 1300 may be implemented by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable A gate array (FPGA), controller, microcontroller, microprocessor, or other electronic component implementation for performing the above methods.
- ASICs application specific integrated circuits
- DSPs digital signal processors
- DSPDs digital signal processing devices
- PLDs programmable logic devices
- FPGA field programmable A gate array
- controller microcontroller, microprocessor, or other electronic component implementation for performing the above methods.
- non-transitory computer readable storage medium comprising instructions, such as a memory 1304 comprising instructions executable by processor 1320 of apparatus 1300 to perform the above method.
- the non-transitory computer readable storage medium may be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, and an optical data storage device.
- a non-transitory computer readable storage medium when executed by a processor of the apparatus 1300, enables the apparatus 1300 to perform a calendar information management method, the method comprising:
- the shared calendar information is sent by the server to the second calendar client after receiving the shared calendar information published by the first calendar client, and the second calendar client is the calendar client logged in by the second user account.
- the second user account is associated with the first user account, and the shared calendar information is obtained by modifying, by the first calendar client, the original calendar information displayed by the first calendar client;
- the second original calendar information is updated by using the shared calendar information, and the second original calendar information is obtained by adding the corresponding event information to the specified date page of the calendar interface displayed by the second calendar client by the second calendar client.
- updating the second original calendar information by using shared calendar information including:
- updating the second original calendar information by using shared calendar information including:
- the shared calendar information and the second original calendar information are merged.
- the second calendar client receives the shared calendar information pushed by the server, and displays the shared calendar information, because the shared calendar information pushed by the server to the second calendar client is
- the first calendar client modifies the original calendar information displayed by the first calendar client, thereby avoiding the problem that the accuracy of the calendar information is low, and therefore solving the problem of low accuracy of calendar information management in the related art. , to achieve the effect of improving the accuracy of calendar information management.
- FIG. 14 is a schematic structural diagram of a calendar information management system 1400 according to an exemplary embodiment.
- the calendar information management system 1400 can include a server 1410, a first calendar client 1420, and a second calendar client 1430.
- the server 1410 includes the calendar information management device shown in FIG. 6, FIG. 7, or FIG.
- the first calendar client 1420 includes the calendar information management device shown in FIG. 8, FIG. 9, or FIG. 12;
- the second calendar client 1430 includes the calendar information management device shown in FIG. 10 or FIG.
- the server receives the shared calendar information published by the first calendar client, and the shared calendar information is the original calendar information displayed by the first calendar client to the first calendar client. Making the modified; pushing the shared calendar information to the second calendar client, so that the second calendar client updates the second original calendar information with the shared calendar information, and the second original calendar information is the second calendar client at the second calendar client.
- the corresponding event information is added to the specified date page of the calendar interface displayed on the side. Since the shared calendar information is obtained by modifying the original calendar information displayed by the first calendar client by the first calendar client, the problem that the accuracy of the calendar information is low is avoided, thereby solving the accuracy of the calendar information management in the related art. The problem of lower sex has achieved the effect of improving the accuracy of calendar information management.
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Human Resources & Organizations (AREA)
- Entrepreneurship & Innovation (AREA)
- Strategic Management (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- General Physics & Mathematics (AREA)
- Marketing (AREA)
- Tourism & Hospitality (AREA)
- Quality & Reliability (AREA)
- General Business, Economics & Management (AREA)
- Operations Research (AREA)
- Economics (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Multimedia (AREA)
- Software Systems (AREA)
- Computer Vision & Pattern Recognition (AREA)
- Evolutionary Computation (AREA)
- Medical Informatics (AREA)
- Artificial Intelligence (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Mathematical Physics (AREA)
- Information Transfer Between Computers (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
Description
Claims (41)
- 一种日历信息管理方法,其特征在于,所述方法包括:接收第一日历客户端发布的共享日历信息,所述共享日历信息是所述第一日历客户端对所述第一日历客户端显示的原始日历信息进行修改得到的;向第二日历客户端推送所述共享日历信息,以使得所述第二日历客户端采用所述共享日历信息更新第二原始日历信息,所述第二原始日历信息是所述第二日历客户端在所述第二日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到的,所述第二日历客户端是第二用户账号登陆的日历客户端,所述第一日历客户端是第一用户账号登陆的日历客户端,所述第二用户账号与所述与第一用户账号关联。
- 根据权利要求1所述的方法,其特征在于,所述原始日历信息是所述第一日历客户端采用第三原始日历信息更新第一原始日历信息得到的,所述第三原始日历信息是第三日历客户端在所述第三日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到并发布至服务器由所述服务器推送给所述第一日历客户端的,所述第一原始日历信息是所述第一日历客户端在所述第一日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到的,所述原始日历信息包括:日期信息和所述事件信息,所述事件信息用于指示所述日期信息对应的日期发生的事件;在所述接收第一日历客户端发布的共享日历信息之前,所述方法还包括:接收所述第三日历客户端发布的所述第三原始日历信息,所述第三日历客户端中登录的用户账号与所述第一用户账号关联;向所述第一日历客户端推送所述第三原始日历信息。
- 根据权利要求1所述的方法,其特征在于,所述原始日历信息是所述第一日历客户端在所述第一日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到的,所述原始日历信息包括:日期信息和所述事件信息,所述事件信息用于指示所述日期信息对应的日期发生的事件。
- 根据权利要求1至3任一所述的方法,其特征在于,在所述向第二日历客户端推送所述共享日历信息之前,所述方法还包括:获取与所述第一用户账号关联的所述第二用户账号。
- 根据权利要求4所述的方法,其特征在于,所述获取与所述第一用户账号关联的所述第二用户账号,包括:获取所述第一用户账号的订阅账号;获取订阅所述订阅账号的其他用户账号,所述其他用户账号不包括所述第一用户账 号;将所述其他用户账号作为所述第二用户账号。
- 根据权利要求4所述的方法,其特征在于,所述获取与所述第一用户账号关联的所述第二用户账号,包括:获取订阅所述第一用户账号的用户账号;将所述订阅所述第一用户账号的用户账号作为所述第二用户账号。
- 根据权利要求4所述的方法,其特征在于,所述获取与所述第一用户账号关联的所述第二用户账号,包括:根据所述第一用户账号,查询预设的用户账号关联列表,所述用户账号关联列表记录了各个用户账号的关联关系;将从所述用户账号关联列表查询得到的与所述第一用户账号关联的用户账号作为所述第二用户账号。
- 一种日历信息管理方法,其特征在于,所述方法包括:显示原始日历信息;接收对所述原始日历信息的更新指令;根据所述更新指令,对所述原始日历信息中所述更新指令指示的内容进行修改,得到共享日历信息;向服务器发布所述共享日历信息,以使得所述服务器向第二日历客户端推送所述共享日历信息,所述第二日历客户端是第二用户账号登陆的日历客户端,第一日历客户端是第一用户账号登陆的日历客户端,所述第二用户账号与所述与第一用户账号关联。
- 根据权利要求8所述的方法,其特征在于,所述根据所述更新指令,对所述原始日历信息中所述更新指令指示的内容进行修改,包括:显示提示信息,所述提示信息用于提示用户对所述原始日历信息中所述更新指令指示的内容进行修改;在接收到所述用户触发的指示进行修改的确认指令时,对所述原始日历信息中所述更新指令指示的内容进行修改。
- 根据权利要求8或9所述的方法,其特征在于,所述原始日历信息包括日期信息和事件信息,所述事件信息用于指示所述日期信息对应的日期发生的事件,所述根据所述更新指令,对所述原始日历信息中所述更新指令指示的内容进行修改,包括:根据所述更新指令对所述日期信息和所述事件信息中的至少一种进行修改。
- 根据权利要求8至10任一所述的方法,其特征在于,在所述显示原始日历信息之前,所述方法还包括:接收所述服务器推送的第三原始日历信息,所述第三原始日历信息是第三日历客户端在所述第三日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到并发布至所述服务器的,所述第三日历客户端中登录的用户账号与所述第一用户账号关联。
- 根据权利要求11所述的方法,其特征在于,在所述接收所述服务器推送的第三原始日历信息之后,所述方法还包括:采用所述第三原始日历信息更新第一原始日历信息得到所述原始日历信息,所述第一原始日历信息是第一日历客户端在所述第一日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到的。
- 根据权利要求12所述的方法,其特征在于,所述采用所述第三原始日历信息更新第一原始日历信息得到所述原始日历信息,包括:采用所述第三原始日历信息替换所述第一原始日历信息得到所述原始日历信息。
- 根据权利要求12所述的方法,其特征在于,所述采用所述第三原始日历信息更新第一原始日历信息得到所述原始日历信息,包括:将所述第三原始日历信息和所述第一原始日历信息进行合并得到所述原始日历信息。
- 根据权利要求8至10任一所述的方法,其特征在于,在所述显示原始日历信息之前,所述方法还包括:在所述第一日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到所述原始日历信息。
- 一种日历信息管理方法,其特征在于,所述方法包括:接收服务器推送的共享日历信息,所述共享日历信息是所述服务器接收到第一日历客户端发布的共享日历信息后,向第二日历客户端推送的,所述第二日历客户端是第二用户账号登录的日历客户端,所述第一日历客户端是第一用户账号登陆的日历客户端,所述第二用户账号与所述与第一用户账号关联,所述共享日历信息是所述第一日历客户端对所述第一日历客户端显示的原始日历信息进行修改得到的;采用所述共享日历信息更新第二原始日历信息,所述第二原始日历信息是所述第二日历客户端在所述第二日历客户端显示的日历界面的指定日期页面中添加对应的事件信息 得到的。
- 根据权利要求16所述的方法,其特征在于,所述采用所述共享日历信息更新第二原始日历信息,包括:采用所述共享日历信息替换所述第二原始日历信息。
- 根据权利要求16所述的方法,其特征在于,所述采用所述共享日历信息更新第二原始日历信息,包括:将所述共享日历信息和所述第二原始日历信息进行合并。
- 一种日历信息管理装置,其特征在于,所述装置包括:第一接收模块,被配置为接收第一日历客户端发布的共享日历信息,所述共享日历信息是所述第一日历客户端对所述第一日历客户端显示的原始日历信息进行修改得到的;第一推送模块,被配置为向第二日历客户端推送所述共享日历信息,以使得所述第二日历客户端采用所述共享日历信息更新第二原始日历信息,所述第二原始日历信息是所述第二日历客户端在所述第二日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到的,所述第二日历客户端是第二用户账号登陆的日历客户端,所述第一日历客户端是第一用户账号登陆的日历客户端,所述第二用户账号与所述与第一用户账号关联。
- 根据权利要求19所述的装置,其特征在于,所述原始日历信息是所述第一日历客户端采用第三原始日历信息更新第一原始日历信息得到的,所述第三原始日历信息是第三日历客户端在所述第三日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到并发布至服务器由所述服务器推送给所述第一日历客户端的,所述第一原始日历信息是所述第一日历客户端在所述第一日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到的,所述原始日历信息包括:日期信息和所述事件信息,所述事件信息用于指示所述日期信息对应的日期发生的事件;所述装置还包括:第二接收模块,被配置为接收所述第三日历客户端发布的所述第三原始日历信息,所述第三日历客户端中登录的用户账号与所述第一用户账号关联;第二推送模块,被配置为向所述第一日历客户端推送所述第三原始日历信息。
- 根据权利要求19所述的装置,其特征在于,所述原始日历信息是所述第一日历客户端在所述第一日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到的,所述原始日历信息包括:日期信息和所述事件信息,所述事件信息用于指示所述日期信息对应的日期发生的事件。
- 根据权利要求19至21任一所述的装置,其特征在于,所述装置还包括:获取模块,被配置为获取与所述第一用户账号关联的所述第二用户账号。
- 根据权利要求22所述的装置,其特征在于,所述获取模块,被配置为:获取所述第一用户账号的订阅账号;获取订阅所述订阅账号的其他用户账号,所述其他用户账号不包括所述第一用户账号;将所述其他用户账号作为所述第二用户账号。
- 根据权利要求22所述的装置,其特征在于,所述获取模块,被配置为:获取订阅所述第一用户账号的用户账号;将所述订阅所述第一用户账号的用户账号作为所述第二用户账号。
- 根据权利要求22所述的装置,其特征在于,所述获取模块,被配置为:根据所述第一用户账号,查询预设的用户账号关联列表,所述用户账号关联列表记录了各个用户账号的关联关系;将从所述用户账号关联列表查询得到的与所述第一用户账号关联的用户账号作为所述第二用户账号。
- 一种日历信息管理装置,其特征在于,所述装置包括:显示模块,被配置为显示原始日历信息;第一接收模块,被配置为接收对所述原始日历信息的更新指令;修改模块,被配置为根据所述更新指令,对所述原始日历信息中所述更新指令指示的内容进行修改,得到共享日历信息;发布模块,被配置为向服务器发布所述共享日历信息,以使得所述服务器向第二日历客户端推送所述共享日历信息,所述第二日历客户端是第二用户账号登陆的日历客户端,第一日历客户端是第一用户账号登陆的日历客户端,所述第二用户账号与所述与第一用户账号关联。
- 根据权利要求26所述的装置,其特征在于,所述修改模块,被配置为:显示提示信息,所述提示信息用于提示用户对所述原始日历信息中所述更新指令指示的内容进行修改;在接收到所述用户触发的指示进行修改的确认指令时,对所述原始日历信息中所述更新指令指示的内容进行修改。
- 根据权利要求26或27所述的装置,其特征在于,所述原始日历信息包括日期信息和事件信息,所述事件信息用于指示所述日期信息对应的日期发生的事件,所述修改模块,被配置为:根据所述更新指令对所述日期信息和所述事件信息中的至少一种进行修改。
- 根据权利要求26至28任一所述的装置,其特征在于,所述装置还包括:第二接收模块,被配置为接收所述服务器推送的第三原始日历信息,所述第三原始日历信息是第三日历客户端在所述第三日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到并发布至所述服务器的,所述第三日历客户端中登录的用户账号与所述第一用户账号关联。
- 根据权利要求29所述的装置,其特征在于,所述装置还包括:更新模块,被配置为采用所述第三原始日历信息更新第一原始日历信息得到所述原始日历信息,所述第一原始日历信息是第一日历客户端在所述第一日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到的。
- 根据权利要求30所述的装置,其特征在于,所述更新模块,被配置为:采用所述第三原始日历信息替换所述第一原始日历信息得到所述原始日历信息。
- 根据权利要求30所述的装置,其特征在于,所述更新模块,被配置为:将所述第三原始日历信息和所述第一原始日历信息进行合并得到所述原始日历信息。
- 根据权利要求26至28任一所述的装置,其特征在于,所述装置还包括:添加模块,被配置为在所述第一日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到所述原始日历信息。
- 一种日历信息管理装置,其特征在于,所述装置包括:接收模块,被配置为接收服务器推送的共享日历信息,所述共享日历信息是所述服务 器接收到第一日历客户端发布的共享日历信息后,向第二日历客户端推送的,所述第二日历客户端是登陆第二用户账号的日历客户端,所述第一日历客户端是第一用户账号登陆的日历客户端,所述第二用户账号与所述与第一用户账号关联,所述共享日历信息是所述第一日历客户端对所述第一日历客户端显示的原始日历信息进行修改得到的;更新模块,被配置为采用所述共享日历信息更新第二原始日历信息,所述第二原始日历信息是所述第二日历客户端在所述第二日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到的。
- 根据权利要求34所述的装置,其特征在于,所述更新模块,被配置为:采用所述共享日历信息替换所述第二原始日历信息。
- 根据权利要求34所述的装置,其特征在于,所述更新模块,被配置为:将所述共享日历信息和所述第二原始日历信息进行合并。
- 一种日历信息管理装置,其特征在于,包括:处理器;用于存储所述处理器的可执行指令的存储器;其中,所述处理器被配置为:接收第一日历客户端发布的共享日历信息,所述共享日历信息是所述第一日历客户端对所述第一日历客户端显示的原始日历信息进行修改得到的;向第二日历客户端推送所述共享日历信息,以使得所述第二日历客户端采用所述共享日历信息更新第二原始日历信息,所述第二原始日历信息是所述第二日历客户端在所述第二日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到的,所述第二日历客户端是第二用户账号登陆的日历客户端,所述第一日历客户端是第一用户账号登陆的日历客户端,所述第二用户账号与所述与第一用户账号关联。
- 一种日历信息管理装置,其特征在于,包括:处理器;用于存储所述处理器的可执行指令的存储器;其中,所述处理器被配置为:显示原始日历信息;接收对所述原始日历信息的更新指令;根据所述更新指令,对所述原始日历信息中所述更新指令指示的内容进行修改,得到 共享日历信息;向服务器发布所述共享日历信息,以使得所述服务器向第二日历客户端推送所述共享日历信息,所述第二日历客户端是第二用户账号登陆的日历客户端,第一日历客户端是第一用户账号登陆的日历客户端,所述第二用户账号与所述与第一用户账号关联。
- 一种日历信息管理装置,其特征在于,包括:处理器;用于存储所述处理器的可执行指令的存储器;其中,所述处理器被配置为:接收服务器推送的共享日历信息,所述共享日历信息是所述服务器接收到第一日历客户端发布的共享日历信息后,向第二日历客户端推送的,所述第二日历客户端是登陆第二用户账号的日历客户端,所述第一日历客户端是第一用户账号登陆的日历客户端,所述第二用户账号与所述与第一用户账号关联,所述共享日历信息是所述第一日历客户端对所述第一日历客户端显示的原始日历信息进行修改得到的;采用所述共享日历信息更新第二原始日历信息,所述第二原始日历信息是所述第二日历客户端在所述第二日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到的。
- 一种日历信息管理系统,其特征在于,所述系统包括:服务器、第一日历客户端和第二日历客户端,所述服务器包括权利要求19至25任一所述的日历信息管理装置;所述第一日历客户端包括权利要求26至33任一所述的日历信息管理装置;所述第二日历客户端包括权利要求34至36任一所述的日历信息管理装置。
- 一种日历信息管理系统,其特征在于,所述系统包括:服务器、第一日历客户端和第二日历客户端,所述服务器包括权利要求37所述的日历信息管理装置;所述第一日历客户端包括权利要求38所述的日历信息管理装置;所述第二日历客户端包括权利要求39所述的日历信息管理装置。
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2017542266A JP6476309B2 (ja) | 2015-09-28 | 2015-12-30 | カレンダー情報管理方法、装置及びシステム、プログラム及び記録媒体 |
RU2016114448A RU2651202C2 (ru) | 2015-09-28 | 2015-12-30 | Способы, устройства и системы для управления календарными данными |
MX2016004097A MX2016004097A (es) | 2015-09-28 | 2015-12-30 | Metodos, dispositivos y sistemas para manejar datos de calendario. |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201510628262.7A CN105279637A (zh) | 2015-09-28 | 2015-09-28 | 日历信息管理方法、装置及系统 |
CN201510628262.7 | 2015-09-28 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2017054359A1 true WO2017054359A1 (zh) | 2017-04-06 |
Family
ID=55148606
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2015/099734 WO2017054359A1 (zh) | 2015-09-28 | 2015-12-30 | 日历信息管理方法、装置及系统 |
Country Status (7)
Country | Link |
---|---|
US (1) | US20170091714A1 (zh) |
EP (1) | EP3147842A1 (zh) |
JP (1) | JP6476309B2 (zh) |
CN (1) | CN105279637A (zh) |
MX (1) | MX2016004097A (zh) |
RU (1) | RU2651202C2 (zh) |
WO (1) | WO2017054359A1 (zh) |
Families Citing this family (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN105897726A (zh) * | 2016-05-09 | 2016-08-24 | 深圳市永兴元科技有限公司 | 关联账号数据共享方法和装置 |
CN106331104B (zh) * | 2016-08-25 | 2019-08-02 | 上海葡萄纬度科技有限公司 | 一种多账号间日程信息的推送方法及系统 |
CN108038658A (zh) * | 2017-11-10 | 2018-05-15 | 深圳市金立通信设备有限公司 | 一种群组内成员日程协调方法、以及终端 |
JP7390781B2 (ja) * | 2018-06-19 | 2023-12-04 | 正規 荻野 | スケジュール情報共有方法およびシステム |
CN109242408A (zh) * | 2018-07-12 | 2019-01-18 | 浙江工业大学 | 一种基于gis的校园上课自动预警方法 |
CN108989574A (zh) * | 2018-08-29 | 2018-12-11 | 珠海格力电器股份有限公司 | 一种智能终端的日历事件提醒交互方法、系统及智能终端 |
CN110099111A (zh) * | 2019-04-26 | 2019-08-06 | 深圳智链物联科技有限公司 | 一种推送消息的显示系统及其显示方法 |
US11120407B2 (en) * | 2019-05-16 | 2021-09-14 | Microsoft Technology Licensing, Llc | Real time collaboration in calendar |
US11645628B2 (en) | 2019-05-16 | 2023-05-09 | Microsoft Technology Licensing, Llc | Translation of time between calendar systems |
US11151104B2 (en) | 2019-05-16 | 2021-10-19 | Microsoft Technology Licensing, Llc | Time systems as data |
US11061525B2 (en) | 2019-05-16 | 2021-07-13 | Microsoft Technology Licensing, Llc | Digital map calendar user interface |
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 |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101145223A (zh) * | 2007-09-27 | 2008-03-19 | 腾讯科技(深圳)有限公司 | 日历管理系统及管理方法 |
CN101520862A (zh) * | 2008-02-29 | 2009-09-02 | 国际商业机器公司 | 电子日历约会计划的更新方法、设备和产生方法、设备 |
CN102750605A (zh) * | 2007-09-27 | 2012-10-24 | 腾讯科技(深圳)有限公司 | 日历管理设备、系统及方法 |
Family Cites Families (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP3575790B2 (ja) * | 2000-05-08 | 2004-10-13 | 株式会社コムアップ | 情報共有システム及び方法 |
JP2002092277A (ja) * | 2000-09-19 | 2002-03-29 | Sony Corp | スケジュール管理システム、サービス提供方法およびプログラム格納媒体 |
US7917468B2 (en) * | 2005-08-01 | 2011-03-29 | Seven Networks, Inc. | Linking of personal information management data |
JP2005318021A (ja) * | 2004-04-26 | 2005-11-10 | Dowango:Kk | スケジュール登録方法、スケジュール登録プログラムおよびスケジュール登録システム |
US7757181B2 (en) * | 2006-05-05 | 2010-07-13 | Microsoft Corporation | Agenda and day hybrid calendar view |
US20100269049A1 (en) * | 2008-10-13 | 2010-10-21 | Regen Fearon | System and method for managing events in a multiple schedule environment |
US20110252351A1 (en) * | 2010-04-09 | 2011-10-13 | Calamander Inc. | Systems and methods for consuming, sharing, and synchronizing time based information |
US20130036369A1 (en) * | 2011-08-02 | 2013-02-07 | SquaredOut, Inc. | Systems and methods for managing event-related information |
US20130145282A1 (en) * | 2011-12-05 | 2013-06-06 | Zhenzhen ZHAO | Systems and methods for social-event based sharing |
CN103517218B (zh) * | 2012-06-15 | 2017-02-01 | 华为技术有限公司 | 一种电子日历的共享方法和装置 |
CN102867249A (zh) * | 2012-07-12 | 2013-01-09 | 广东步步高电子工业有限公司 | 基于移动互联网的在线日历系统 |
JP2014179056A (ja) * | 2013-02-17 | 2014-09-25 | Net Security Kk | イベント情報共有システムおよびカレンダー表示装置 |
US9635108B2 (en) * | 2014-01-25 | 2017-04-25 | Q Technologies Inc. | Systems and methods for content sharing using uniquely generated idenifiers |
CN104243559A (zh) * | 2014-08-29 | 2014-12-24 | 小米科技有限责任公司 | 日历信息推送方法、装置及系统 |
-
2015
- 2015-09-28 CN CN201510628262.7A patent/CN105279637A/zh active Pending
- 2015-12-30 JP JP2017542266A patent/JP6476309B2/ja active Active
- 2015-12-30 RU RU2016114448A patent/RU2651202C2/ru active
- 2015-12-30 MX MX2016004097A patent/MX2016004097A/es unknown
- 2015-12-30 WO PCT/CN2015/099734 patent/WO2017054359A1/zh active Application Filing
-
2016
- 2016-05-10 EP EP16169052.4A patent/EP3147842A1/en not_active Ceased
- 2016-07-26 US US15/219,300 patent/US20170091714A1/en not_active Abandoned
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101145223A (zh) * | 2007-09-27 | 2008-03-19 | 腾讯科技(深圳)有限公司 | 日历管理系统及管理方法 |
CN102750605A (zh) * | 2007-09-27 | 2012-10-24 | 腾讯科技(深圳)有限公司 | 日历管理设备、系统及方法 |
CN101520862A (zh) * | 2008-02-29 | 2009-09-02 | 国际商业机器公司 | 电子日历约会计划的更新方法、设备和产生方法、设备 |
Also Published As
Publication number | Publication date |
---|---|
MX2016004097A (es) | 2018-06-22 |
RU2016114448A (ru) | 2017-10-19 |
US20170091714A1 (en) | 2017-03-30 |
JP6476309B2 (ja) | 2019-02-27 |
EP3147842A1 (en) | 2017-03-29 |
RU2651202C2 (ru) | 2018-04-18 |
JP2018501589A (ja) | 2018-01-18 |
CN105279637A (zh) | 2016-01-27 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2017054359A1 (zh) | 日历信息管理方法、装置及系统 | |
WO2017008396A1 (zh) | 一种控制设备的方法及装置 | |
WO2016011744A1 (zh) | 使用验证码进行验证的方法及装置 | |
WO2016082460A1 (zh) | 一种调整智能家居设备运行状态的方法及装置 | |
WO2017031905A1 (zh) | 社交关系分析方法及装置 | |
WO2016050038A1 (zh) | 通信消息识别方法及装置 | |
WO2016045277A1 (zh) | 信息获取方法、装置和系统 | |
WO2017206165A1 (zh) | 信息发送方法、信息接收方法、装置及系统 | |
WO2017020410A1 (zh) | 目标功能的开启方法、装置及系统 | |
WO2017020482A1 (zh) | 票务信息展示方法及装置 | |
EP3937482A1 (en) | Image collection method and apparatus, and device and storage medium | |
WO2017031872A1 (zh) | 通信消息处理方法和装置 | |
EP2924627A1 (en) | Method, device and system for event reminding | |
WO2016173246A1 (zh) | 基于云名片的电话呼叫方法及装置 | |
WO2016065760A1 (zh) | 设备连接的提示方法及装置 | |
WO2017080205A1 (zh) | 一种锁屏壁纸相关信息获取方法及装置 | |
WO2017035995A1 (zh) | 联系人记录处理方法及装置 | |
WO2020020048A1 (zh) | 更新群成员数据的方法、装置、终端、系统及存储介质 | |
WO2023155822A1 (zh) | 会话的方法、装置、电子设备和存储介质 | |
WO2023124906A1 (zh) | 一种消息处理方法、装置、设备及介质 | |
KR20180081231A (ko) | 데이터를 공유하기 위한 방법 및 그 전자 장치 | |
CN108737249B (zh) | 调整群组名片的方法、电子设备、计算机可读存储介质 | |
WO2016206301A1 (zh) | 事件提醒方法及装置 | |
WO2017054350A1 (zh) | 一种提醒方法及装置 | |
WO2016008241A1 (zh) | 服务注册更新方法、装置、服务器及客户端 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
ENP | Entry into the national phase |
Ref document number: 2017542266 Country of ref document: JP Kind code of ref document: A |
|
WWE | Wipo information: entry into national phase |
Ref document number: 1020167006913 Country of ref document: KR |
|
WWE | Wipo information: entry into national phase |
Ref document number: MX/A/2016/004097 Country of ref document: MX |
|
ENP | Entry into the national phase |
Ref document number: 2016114448 Country of ref document: RU Kind code of ref document: A |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 15905269 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 15905269 Country of ref document: EP Kind code of ref document: A1 |