WO2017054359A1 - 日历信息管理方法、装置及系统 - Google Patents

日历信息管理方法、装置及系统 Download PDF

Info

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
Application number
PCT/CN2015/099734
Other languages
English (en)
French (fr)
Inventor
胡珊
张鹏
刘绍辉
Original Assignee
小米科技有限责任公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 小米科技有限责任公司 filed Critical 小米科技有限责任公司
Priority to JP2017542266A priority Critical patent/JP6476309B2/ja
Priority to RU2016114448A priority patent/RU2651202C2/ru
Priority to MX2016004097A priority patent/MX2016004097A/es
Publication of WO2017054359A1 publication Critical patent/WO2017054359A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management
    • 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

日历信息管理方法、装置及系统
本申请基于申请号为201510628262.7、申请日为2015年9月28日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此引入本申请作为参考。
技术领域
本公开涉及电子技术应用领域，特别涉及一种日历信息管理方法、装置及系统。
背景技术
日历客户端是一种可以供用户进行日历查阅的客户端，其可以安装在诸如智能手机、平板电脑、车载终端等智能终端上，为用户提供日历信息的管理功能，其中，日历信息可以包括日期信息和事件信息，事件信息用于指示日期信息对应的日期发生的事件。
日历客户端可以向用户呈现日历，日历中的每个日期对应一个日期页面(也可以称为日历格子间)。相关技术中，用户可以在待办事件的日期对应的日历格子间中添加待办事件的事件信息，并进行备忘设置，以便于日历客户端在指定时刻对用户进行提醒，其中，事件信息中可以包括时间信息，该时间信息用于指示该事件信息中的事件的发生时刻，指定时刻可以为该事件的发生时刻的前两个小时，例如，学生可以将校园招聘会的宣讲信息添加在宣讲日期对应的日历格子间中，并进行备忘设置，以便于日历客户端在指定时刻提醒学生参加校园招聘会。
发明内容
为了实现提高日历信息管理的准确性的效果，本公开提供了一种日历信息管理方法、装置及系统。所述技术方案如下：
根据本公开的第一方面，提供一种日历信息管理方法，所述方法包括：
接收第一日历客户端发布的共享日历信息，所述共享日历信息是所述第一日历客户端对所述第一日历客户端显示的原始日历信息进行修改得到的；
向第二日历客户端推送所述共享日历信息，以使得所述第二日历客户端采用所述共享日历信息更新第二原始日历信息，所述第二原始日历信息是所述第二日历客户端在所述第二日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到的，所述第二日历客户端是第二用户账号登陆的日历客户端，所述第一日历客户端是第一用户账号登陆的日历客户端，所述第二用户账号与所述与第一用户账号关联。
可选地，所述原始日历信息是所述第一日历客户端采用第三原始日历信息更新第一原始日历信息得到的，所述第三原始日历信息是第三日历客户端在所述第三日历客户端显示 的日历界面的指定日期页面中添加对应的事件信息得到并发布至服务器由所述服务器推送给所述第一日历客户端的，所述第一原始日历信息是所述第一日历客户端在所述第一日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到的，所述原始日历信息包括：日期信息和所述事件信息，所述事件信息用于指示所述日期信息对应的日期发生的事件；
在所述接收第一日历客户端发布的共享日历信息之前，所述方法还包括：
接收所述第三日历客户端发布的第三原始日历信息，所述第三日历客户端中登录的用户账号与所述第一用户账号关联；
向所述第一日历客户端推送所述第三原始日历信息。
可选地，所述原始日历信息是所述第一日历客户端在所述第一日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到的，所述原始日历信息包括：日期信息和所述事件信息，所述事件信息用于指示所述日期信息对应的日期发生的事件。
在所述向第二日历客户端推送所述共享日历信息之前，所述方法还包括：
获取与所述第一用户账号关联的所述第二用户账号。
可选地，所述获取与所述第一用户账号关联的所述第二用户账号，包括：
获取所述第一用户账号的订阅账号；
获取订阅所述订阅账号的其他用户账号，所述其他用户账号不包括所述第一用户账号；
将所述其他用户账号作为所述第二用户账号。
可选地，所述获取与所述第一用户账号关联的所述第二用户账号，包括：
获取订阅所述第一用户账号的用户账号；
将所述订阅所述第一用户账号的用户账号作为所述第二用户账号。
可选地，所述获取与所述第一用户账号关联的所述第二用户账号，包括：
根据所述第一用户账号，查询预设的用户账号关联列表，所述用户账号关联列表记录了各个用户账号的关联关系；
将从所述用户账号关联列表查询得到的与所述第一用户账号关联的用户账号作为所述第二用户账号。
根据本公开的第二方面，提供一种日历信息管理方法，所述方法包括：
显示原始日历信息；
接收对所述原始日历信息的更新指令；
根据所述更新指令，对所述原始日历信息中所述更新指令指示的内容进行修改，得到共享日历信息；
向服务器发布所述共享日历信息，以使得所述服务器向第二日历客户端推送所述共享日历信息，所述第二日历客户端是第二用户账号登陆的日历客户端，第一日历客户端是第一用户账号登陆的日历客户端，所述第二用户账号与所述与第一用户账号关联。
可选地，所述根据所述更新指令，对所述原始日历信息中所述更新指令指示的内容进行修改，包括：
显示提示信息，所述提示信息用于提示用户对所述原始日历信息中所述更新指令指示的内容进行修改；
在接收到所述用户触发的指示进行修改的确认指令时，对所述原始日历信息中所述更新指令指示的内容进行修改。
可选地，所述原始日历信息包括日期信息和事件信息，所述事件信息用于指示所述日期信息对应的日期发生的事件，
所述根据所述更新指令，对所述原始日历信息中所述更新指令指示的内容进行修改，包括：
根据所述更新指令对所述日期信息和所述事件信息中的至少一种进行修改。
可选地，在所述显示原始日历信息之前，所述方法还包括：
接收所述服务器推送的第三原始日历信息，所述第三原始日历信息是第三日历客户端在所述第三日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到并发布至所述服务器的，所述第三日历客户端中登录的用户账号与所述第一用户账号关联。
可选地，在所述接收所述服务器推送的第三原始日历信息之后，所述方法还包括：
采用所述第三原始日历信息更新第一原始日历信息得到所述原始日历信息，所述第一原始日历信息是第一日历客户端在所述第一日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到的。
可选地，所述采用所述第三原始日历信息更新第一原始日历信息得到所述原始日历信息，包括：
采用所述第三原始日历信息替换所述第一原始日历信息得到所述原始日历信息。
可选地，所述采用所述第三原始日历信息更新第一原始日历信息得到所述原始日历信息，包括：
将所述第三原始日历信息和所述第一原始日历信息进行合并得到所述原始日历信息。
可选地，在所述显示原始日历信息之前，所述方法还包括：
在所述第一日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到所述原始日历信息。
根据本公开的第三方面，提供一种日历信息管理方法，所述方法包括：
接收服务器推送的共享日历信息，所述共享日历信息是所述服务器接收到第一日历客户端发布的共享日历信息后，向第二日历客户端推送的，所述第二日历客户端是登陆第二用户账号的日历客户端，所述第一日历客户端是第一用户账号登陆的日历客户端，所述第二用户账号与所述与第一用户账号关联，所述共享日历信息是所述第一日历客户端对所述第一日历客户端显示的原始日历信息进行修改得到的；
采用所述共享日历信息更新第二原始日历信息，所述第二原始日历信息是所述第二日 历客户端在所述第二日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到的。
可选地，所述采用所述共享日历信息更新第二原始日历信息，包括：
采用所述共享日历信息替换所述第二原始日历信息。
可选地，所述采用所述共享日历信息更新第二原始日历信息，包括：
将所述共享日历信息和所述第二原始日历信息进行合并。
根据本公开的第四方面，提供一种日历信息管理装置，所述装置包括：
第一接收模块，被配置为接收第一日历客户端发布的共享日历信息，所述共享日历信息是所述第一日历客户端对所述第一日历客户端显示的原始日历信息进行修改得到的；
第一推送模块，被配置为向第二日历客户端推送所述共享日历信息，以使得所述第二日历客户端采用所述共享日历信息更新第二原始日历信息，所述第二原始日历信息是所述第二日历客户端在所述第二日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到的，所述第二日历客户端是第二用户账号登陆的日历客户端，所述第一日历客户端是第一用户账号登陆的日历客户端，所述第二用户账号与所述与第一用户账号关联。
可选地，所述原始日历信息是所述第一日历客户端采用第三原始日历信息更新第一原始日历信息得到的，所述第三原始日历信息是第三日历客户端在所述第三日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到并发布至服务器由所述服务器推送给所述第一日历客户端的，所述第一原始日历信息是所述第一日历客户端在所述第一日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到的，所述原始日历信息包括：日期信息和所述事件信息，所述事件信息用于指示所述日期信息对应的日期发生的事件；
所述装置还包括：
第二接收模块，被配置为接收所述第三日历客户端发布的所述第三原始日历信息，所述第三日历客户端中登录的用户账号与所述第一用户账号关联；
第二推送模块，被配置为向所述第一日历客户端推送所述第三原始日历信息。
可选地，所述原始日历信息是所述第一日历客户端在所述第一日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到的，所述原始日历信息包括：日期信息和所述事件信息，所述事件信息用于指示所述日期信息对应的日期发生的事件。
可选地，所述装置还包括：
获取模块，被配置为获取与所述第一用户账号关联的所述第二用户账号。
可选地，所述获取模块，被配置为：
获取所述第一用户账号的订阅账号；
获取订阅所述订阅账号的其他用户账号，所述其他用户账号不包括所述第一用户账号；
将所述其他用户账号作为所述第二用户账号。
可选地，所述获取模块，被配置为：
获取订阅所述第一用户账号的用户账号；
将所述订阅所述第一用户账号的用户账号作为所述第二用户账号。
可选地，所述获取模块，被配置为：
根据所述第一用户账号，查询预设的用户账号关联列表，所述用户账号关联列表记录了各个用户账号的关联关系；
将从所述用户账号关联列表查询得到的与所述第一用户账号关联的用户账号作为所述第二用户账号。
根据本公开的第五方面，提供一种日历信息管理装置，所述装置包括：
显示模块，被配置为显示原始日历信息；
第一接收模块，被配置为接收对所述原始日历信息的更新指令；
修改模块，被配置为根据所述更新指令，对所述原始日历信息中所述更新指令指示的内容进行修改，得到共享日历信息；
发布模块，被配置为向服务器发布所述共享日历信息，以使得所述服务器向第二日历客户端推送所述共享日历信息，所述第二日历客户端是第二用户账号登陆的日历客户端，第一日历客户端是第一用户账号登陆的日历客户端，所述第二用户账号与所述与第一用户账号关联。
可选地，修改模块，被配置为：
显示提示信息，所述提示信息用于提示用户对所述原始日历信息中所述更新指令指示的内容进行修改；
在接收到所述用户触发的指示进行修改的确认指令时，对所述原始日历信息中所述更新指令指示的内容进行修改。
可选地，所述原始日历信息包括日期信息和事件信息，所述事件信息用于指示所述日期信息对应的日期发生的事件，
所述修改模块，被配置为：
根据所述更新指令对所述日期信息和所述事件信息中的至少一种进行修改。
可选地，所述装置还包括：
第二接收模块，被配置为接收所述服务器推送的第三原始日历信息，所述第三原始日历信息是第三日历客户端在所述第三日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到并发布至所述服务器的，所述第三日历客户端中登录的用户账号与所述第一用户账号关联。
可选地，所述装置还包括：
更新模块，被配置为采用所述第三原始日历信息更新第一原始日历信息得到所述原始日历信息，所述第一原始日历信息是第一日历客户端在所述第一日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到的。
可选地，所述更新模块，被配置为：
采用所述第三原始日历信息替换所述第一原始日历信息得到所述原始日历信息。
可选地，所述更新模块，被配置为：
将所述第三原始日历信息和所述第一原始日历信息进行合并得到所述原始日历信息。
可选地，所述装置还包括：
添加模块，被配置为在所述第一日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到所述原始日历信息。
根据本公开的第六方面，提供一种日历信息管理装置，所述装置包括：
接收模块，被配置为接收服务器推送的共享日历信息，所述共享日历信息是所述服务器接收到第一日历客户端发布的共享日历信息后，向第二日历客户端推送的，所述第二日历客户端是登陆第二用户账号的日历客户端，所述第一日历客户端是第一用户账号登陆的日历客户端，所述第二用户账号与所述与第一用户账号关联，所述共享日历信息是所述第一日历客户端对所述第一日历客户端显示的原始日历信息进行修改得到的；
更新模块，被配置为采用所述共享日历信息更新第二原始日历信息，所述第二原始日历信息是所述第二日历客户端在所述第二日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到的。
可选地，所述更新模块，被配置为：
采用所述共享日历信息替换所述第二原始日历信息。
可选地，所述更新模块，被配置为：
将所述共享日历信息和所述第二原始日历信息进行合并。
根据本公开的第七方面，提供一种日历信息管理装置，包括：
处理器；
用于存储所述处理器的可执行指令的存储器；
其中，所述处理器被配置为：
接收第一日历客户端发布的共享日历信息，所述共享日历信息是所述第一日历客户端对所述第一日历客户端显示的原始日历信息进行修改得到的；
向第二日历客户端推送所述共享日历信息，以使得所述第二日历客户端采用所述共享日历信息更新第二原始日历信息，所述第二原始日历信息是所述第二日历客户端在所述第二日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到的，所述第二日历客户端是第二用户账号登陆的日历客户端，所述第一日历客户端是第一用户账号登陆的日历客户端，所述第二用户账号与所述与第一用户账号关联。
根据本公开的第八方面，提供一种日历信息管理装置，包括：
处理器；
用于存储所述处理器的可执行指令的存储器；
其中，所述处理器被配置为：
显示原始日历信息；
接收对所述原始日历信息的更新指令；
根据所述更新指令，对所述原始日历信息中所述更新指令指示的内容进行修改，得到共享日历信息；
向服务器发布所述共享日历信息，以使得所述服务器向第二日历客户端推送所述共享日历信息，所述第二日历客户端是第二用户账号登陆的日历客户端，第一日历客户端是第一用户账号登陆的日历客户端，所述第二用户账号与所述与第一用户账号关联。
根据本公开的第九方面，提供一种日历信息管理装置，包括：
处理器；
用于存储所述处理器的可执行指令的存储器；
其中，所述处理器被配置为：
接收服务器推送的共享日历信息，所述共享日历信息是所述服务器接收到第一日历客户端发布的共享日历信息后，向第二日历客户端推送的，所述第二日历客户端是登陆第二用户账号的日历客户端，所述第一日历客户端是第一用户账号登陆的日历客户端，所述第二用户账号与所述与第一用户账号关联，所述共享日历信息是所述第一日历客户端对所述第一日历客户端显示的原始日历信息进行修改得到的；
采用所述共享日历信息更新第二原始日历信息，所述第二原始日历信息是所述第二日历客户端在所述第二日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到的。
根据本公开的第十方面，提供一种日历信息管理系统，所述系统包括：服务器、第一日历客户端和第二日历客户端，
所述服务器包括第四方面或第四方面任一可选方式所述的日历信息管理装置；
所述第一日历客户端包括第五方面或第五方面任一可选方式所述的日历信息管理装置；
所述第二日历客户端包括第六方面或第六方面任一可选方式所述的日历信息管理装置。
根据本公开的第十一方面，提供一种日历信息管理系统，所述系统包括：服务器、第一日历客户端和第二日历客户端，
所述服务器包括第七方面所述的日历信息管理装置；
所述第一日历客户端包括第八方面所述的日历信息管理装置；
所述第二日历客户端包括第九方面所述的日历信息管理装置。
本公开的提供的技术方案可以包括以下有益效果：
本公开提供的日历信息管理方法、装置及系统，服务器通过接收第一日历客户端发布的共享日历信息，共享日历信息是第一日历客户端对第一日历客户端显示的原始日历信息进行修改得到的；向第二日历客户端推送共享日历信息，以使得第二日历客户端采用共享 日历信息更新第二原始日历信息，第二原始日历信息是第二日历客户端在第二日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到的。由于共享日历信息是第一日历客户端对第一日历客户端显示的原始日历信息进行修改得到的，避免了日历信息的准确性较低的问题，因此，解决了相关技术中日历信息管理的准确性较低的问题，达到了提高日历信息管理的准确性的效果。
应当理解的是，以上的一般描述和后文的细节描述仅是示例性的，并不能限制本公开。
附图说明
此处的附图被并入说明书中并构成本说明书的一部分，示出了符合本发明的实施例，并与说明书一起用于解释本发明的原理。
图1是本公开各个实施例提供的日历信息管理方法所涉及的一种实施环境的结构示意图；
图2是根据一示例性实施例示出的一种日历信息管理方法的方法流程图；
图3是根据另一示例性实施例示出的一种日历信息管理方法的方法流程图；
图4是根据再一示例性实施例示出的一种日历信息管理方法的方法流程图；
图5-1是根据又一示例性实施例示出的一种日历信息管理方法的方法流程图；
图5-2是图5-1所示实施例提供的一种第三日历客户端显示的日历界面图；
图5-3是图5-1所示实施例提供的另一种第三日历客户端显示的日历界面图；
图5-4是图5-1所示实施例提供的一种第一日历客户端显示的日历界面图；
图5-5是图5-1所示实施例提供的另一种第一日历客户端显示的日历界面图；
图5-6是图5-1所示实施例提供的再一种第一日历客户端显示的日历界面图；
图5-7是图5-1所示实施例提供的一种第一日历客户端根据更新指令对原始日历信息中更新指令指示的内容进行修改的方法流程图；
图5-8是图5-1所示实施例提供的一种第一日历客户端显示的提示界面图；
图5-9是图5-1所示实施例提供的一种第一日历客户端显示的对原始日历信息进行更新后的界面图；
图5-10是图5-1所示实施例提供的一种服务器获取与第一用户账号关联的第二用户账号的方法流程图；
图5-11是图5-1所示实施例提供的另一种服务器获取与第一用户账号关联的第二用户账号的方法流程图；
图5-12是图5-1所示实施例提供的再一种服务器获取与第一用户账号关联的第二用户账号的方法流程图；
图6是根据一示例性实施例示出的一种日历信息管理装置的框图；
图7是根据一示例性实施例示出的另一种日历信息管理装置的框图；
图8是根据另一示例性实施例示出的一种日历信息管理装置的框图；
图9是根据另一示例性实施例示出的另一种日历信息管理装置的框图；
图10是根据再一示例性实施例示出的一种日历信息管理装置的框图；
图11是根据一示例性实施例示出的一种日历信息管理装置的框图；
图12是根据另一示例性实施例示出的一种日历信息管理装置的框图；
图13是根据再一示例性实施例示出的一种日历信息管理装置的框图；
图14是根据一示例性实施例示出的一种日历信息管理系统的框图。
具体实施方式
为了使本公开的目的、技术方案和优点更加清楚，下面将结合附图对本公开作进一步地详细描述，显然，所描述的实施例仅仅是本公开一部份实施例，而不是全部的实施例。基于本公开中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其它实施例，都属于本公开保护的范围。
图1是本公开各个实施例提供的日历信息管理方法所涉及的一种实施环境的结构示意图。参见图1，该实施环境包括第一终端120、第二终端140、第三终端160和服务器180。其中，第一终端120、第二终端140和第三终端160可以通过有线网络或者无线网络分别与服务器180连接，该无线网络可以包括但不限于：无线保真(英文：Wireless Fidelity，简称：WIFI)、蓝牙、红外、紫蜂(英文：Zigbee)、数据，且第一终端120、第二终端140和第三终端160之间也可以通过有线网络或者无线网络互相连接(图1中未画出)，本公开实施例对此不做限定。
在本公开实施例中，第一终端120上安装有第一日历客户端、第一终端120通过第一日历客户端实现对日历信息的管理；第二终端140上安装有第二日历客户端，第二终端140通过第二日历客户端实现对日历信息的管理；第三终端160上安装有第三日历客户端，第三终端160通过第三日历客户端实现对日历信息的管理。第一终端120、第二终端140和第三终端160通过服务器180实现日历信息的共享。
示例地，第三日历客户端中可以登录与第一用户账号关联的用户账号，第一用户账号是登陆在第一日历客户端中的用户账号，第三日历客户端可以在第三日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到第三原始日历信息，并向服务器180发布第三原始日历信息。
服务器180可以接收第三日历客户端发布的第三原始日历信息，并向第一日历客户端推送该第三原始日历信息，以使得第一日历客户端采用第三原始日历信息更新第一原始日历信息得到原始日历信息，第一原始日历信息是第一日历客户端在第一日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到的。其中，第一日历客户端中登录的用户账号可以为第一用户账号，第三日历客户端中登录的用户账号可以与第一用户账号关联，服务器180可以存储用户账户的关联关系，并根据用户账号的关联关系对日历信息进 行推送。
第一日历客户端可以显示原始日历信息，并接收用户触发的对原始日历信息的更新指令，根据更新指令，对原始日历信息中更新指令指示的内容进行修改，得到共享日历信息，并向服务器发布共享日历信息。可选地，第一日历客户端显示的原始日历信息可以是接收服务器推送的第三原始日历信息，采用第三原始日历信息更新第一原始日历信息得到的，第一原始日历信息是第一日历客户端在第一日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到的，第一日历客户端显示的原始日历信息也可以是第一日历客户端在第一日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到的，本公开实施例对此不做限定。可选地，第一日历客户端采用第三原始日历信息更新第一原始日历信息可以包括：第一日历客户端采用第三原始日历信息替换第一原始日历信息得到原始日历信息，或者，第一日历客户端将第三原始日历信息和第一原始日历信息进行合并得到原始日历信息。可选地，第一日历客户端根据更新指令，对原始日历信息中更新指令指示的内容进行修改可以包括：第一日历客户端显示提示信息，提示信息用于提示用户对原始日历信息中更新指令指示的内容进行修改；在接收到用户触发的指示进行修改的确认指令时，对原始日历信息中更新指令指示的内容进行修改。其中，原始日历信息可以包括日期信息和事件信息，第一日历客户端可以根据更新指令对原始日历信息中的日期信息和事件信息中的至少一种进行修改。
服务器180可以接收第一日历客户端发布的共享日历信息，向第二日历客户端推送共享日历信息，以使得第一日历客户端采用第三原始日历信息更新第一原始日历信息得到原始日历信息。第二日历客户端是第二用户账号登陆的日历客户端，第一日历客户端是第一用户账号登陆的日历客户端，第二用户账号与第一用户账号关联。可选地，在向第二日历客户端推送共享日历信息之前，服务器180可以获取与第一用户账号关联的第二用户账号。其中，服务器180获取与第一用户账号关联的第二用户账号可以包括：服务器180获取第一用户账号的订阅账号，并获取订阅该订阅账号的其他用户账号，进而将其他用户账号作为第二用户账号，也即，服务器180将订阅同一订阅账号的用户账号作为关联的用户账号。可选地，服务器180获取与第一用户账号关联的第二用户账号还可以包括：服务器180获取订阅第一用户账号的用户账号，并将订阅第一用户账号的用户账号作为与第二用户账号，也即，服务器180将订阅第一用户账号的用户账号作为与第一用户账号关联的用户账号。可选地，服务器180获取与第一用户账号关联的第二用户账号还可以包括：服务器180根据第一用户账号，查询预设的用户账号关联列表，用户账号关联列表记录了各个用户账号的关联关系；将从用户账号关联列表查询得到的与第一用户账号关联的用户账号作为第二用户账号，也即，服务器180中配置了用户账号的对应关系，服务器根据用户账号的对应关系获取与第一用户账号关联的用户账号，本公开实施例对此不做限定。
第二日历客户端可以接收服务器180推送的共享日历信息，并采用共享日历信息更新第二原始日历信息，第二原始日历信息是第二日历客户端在第二日历客户端显示的日历界 面的指定日期页面中添加对应的事件信息得到的。可选地，第二日历客户端采用共享日历信息更新第二原始日历信息可以包括：第二日历客户端采用共享日历信息替换第二原始日历信息，或者，第二日历客户端将共享日历信息和第二原始日历信息进行合并，本公开实施例对此不做限定。
在本公开实施例中，第一终端120、第二终端140和第三终端160通过服务器180实现日历信息的共享，进而实现对日历信息的管理，提高了日历信息管理的准确性。
图2是根据一示例性实施例示出的一种日历信息管理方法的方法流程图，本实施例以该日历信息管理方法应用于图1所示实施环境中的服务器180中来进行举例说明，参见图2，该日历信息管理方法可以包括如下几个步骤：
在步骤201中，接收第一日历客户端发布的共享日历信息，共享日历信息是第一日历客户端对第一日历客户端显示的原始日历信息进行修改得到的。
在步骤202中，向第二日历客户端推送共享日历信息，以使得第二日历客户端采用共享日历信息更新第二原始日历信息，第二原始日历信息是第二日历客户端在第二日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到的。
其中，第二日历客户端是第二用户账号登陆的日历客户端，第一日历客户端是第一用户账号登陆的日历客户端，第二用户账号与第一用户账号关联。
综上所述，本公开实施例提供的日历信息管理方法，服务器通过接收第一日历客户端发布的共享日历信息，共享日历信息是第一日历客户端对第一日历客户端显示的原始日历信息进行修改得到的；向第二日历客户端推送共享日历信息，以使得第二日历客户端采用共享日历信息更新第二原始日历信息，第二原始日历信息是第二日历客户端在第二日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到的。由于共享日历信息是第一日历客户端对第一日历客户端显示的原始日历信息进行修改得到的，避免了日历信息的准确性较低的问题，因此，解决了相关技术中日历信息管理的准确性较低的问题，达到了提高日历信息管理的准确性的效果。
可选地，原始日历信息是第一日历客户端采用第三原始日历信息更新第一原始日历信息得到的，第三原始日历信息是第三日历客户端在第三日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到并发布至服务器由服务器推送给第一日历客户端的，第一原始日历信息是第一日历客户端在第一日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到的，原始日历信息包括：日期信息和事件信息，事件信息用于指示日期信息对应的日期发生的事件；
在步骤201之前，该方法还可以包括：
接收第三日历客户端发布的第三原始日历信息，第三日历客户端中登录的用户账号与第一用户账号关联；
向第一日历客户端推送第三原始日历信息。
可选地，原始日历信息是第一日历客户端在第一日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到的，原始日历信息包括：日期信息和事件信息，事件信息用于指示日期信息对应的日期发生的事件。
可选地，在步骤202之前，该方法还可以包括：
获取与第一用户账号关联的第二用户账号。
可选地，获取与第一用户账号关联的第二用户账号可以包括：
获取第一用户账号的订阅账号；
获取订阅订阅账号的其他用户账号，其他用户账号不包括第一用户账号；
将其他用户账号作为第二用户账号。
可选地，获取与第一用户账号关联的第二用户账号可以包括：
获取订阅第一用户账号的用户账号；
将订阅第一用户账号的用户账号作为第二用户账号。
可选地，获取与第一用户账号关联的第二用户账号可以包括：
根据第一用户账号，查询预设的用户账号关联列表，用户账号关联列表记录了各个用户账号的关联关系；
将从用户账号关联列表查询得到的与第一用户账号关联的用户账号作为第二用户账号。
上述所有可选技术方案，可以采用任意结合形成本公开的可选实施例，在此不再一一赘述。
综上所述，本公开实施例提供的日历信息管理方法，服务器通过接收第一日历客户端发布的共享日历信息，共享日历信息是第一日历客户端对第一日历客户端显示的原始日历信息进行修改得到的；向第二日历客户端推送共享日历信息，以使得第二日历客户端采用共享日历信息更新第二原始日历信息，第二原始日历信息是第二日历客户端在第二日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到的。由于共享日历信息是第一日历客户端对第一日历客户端显示的原始日历信息进行修改得到的，避免了日历信息的准确性较低的问题，因此，解决了相关技术中日历信息管理的准确性较低的问题，达到了提高日历信息管理的准确性的效果。
图3是根据另一示例性实施例示出的一种日历信息管理方法的方法流程图，本实施例以该日历信息管理方法应用于第一日历客户端中来进行举例说明，其中，第一日历客户端可以是安装在图1所示实施环境中的第一终端120上的日历客户端，参见图3，该日历信息管理方法可以包括如下几个步骤：
在步骤301中，显示原始日历信息。
在步骤302中，接收对原始日历信息的更新指令。
在步骤303中，根据更新指令，对原始日历信息中更新指令指示的内容进行修改，得 到共享日历信息。
在步骤304中，向服务器发布共享日历信息，以使得服务器用于向第二日历客户端推送共享日历信息。
其中，第二日历客户端是第二用户账号登陆的日历客户端，第一日历客户端是第一用户账号登陆的日历客户端，第二用户账号与第一用户账号关联。
综上所述，本公开实施例提供的日历信息管理方法，第一日历客户端通过显示原始日历信息，接收对原始日历信息的更新指令，根据更新指令，对原始日历信息中更新指令指示的内容进行修改，得到共享日历信息，并向服务器发布共享日历信息，以使得服务器向第二日历客户端推送共享日历信息，由于服务器向第二日历客户端推送的共享日历信息是第一日历客户端对第一日历客户端显示的原始日历信息进行修改得到的，避免了日历信息的准确性较低的问题，因此，解决了相关技术中日历信息管理的准确性较低的问题，达到了提高日历信息管理的准确性的效果。
可选地，步骤303可以包括：
显示提示信息，提示信息用于提示用户对原始日历信息中更新指令指示的内容进行修改；
在接收到用户触发的指示进行修改的确认指令时，对原始日历信息中更新指令指示的内容进行修改。
可选地，原始日历信息包括日期信息和事件信息，事件信息用于指示日期信息对应的日期发生的事件，
步骤303可以包括：
根据更新指令对日期信息和事件信息中的至少一种进行修改。
可选地，在步骤301之前，该方法还可以包括：
接收服务器推送的第三原始日历信息，第三原始日历信息是第三日历客户端在第三日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到并发布至服务器的，第三日历客户端中登录的用户账号与第一用户账号关联。
可选地，在接收服务器推送的第三原始日历信息之后，该方法还包括：
采用第三原始日历信息更新第一原始日历信息得到原始日历信息，第一原始日历信息是第一日历客户端在第一日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到的。
可选地，采用第三原始日历信息更新第一原始日历信息得到原始日历信息，包括：
采用第三原始日历信息替换第一原始日历信息得到原始日历信息。
可选地，采用第三原始日历信息更新第一原始日历信息得到原始日历信息，包括：
将第三原始日历信息和第一原始日历信息进行合并得到原始日历信息。
可选地，在步骤301之前，该方法还可以包括：
在第一日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到原始 日历信息。
上述所有可选技术方案，可以采用任意结合形成本公开的可选实施例，在此不再一一赘述。
综上所述，本公开实施例提供的日历信息管理方法，第一日历客户端通过显示原始日历信息，接收对原始日历信息的更新指令，根据更新指令，对原始日历信息中更新指令指示的内容进行修改，得到共享日历信息，并向服务器发布共享日历信息，以使得服务器向第二日历客户端推送共享日历信息，由于服务器向第二日历客户端推送的共享日历信息是第一日历客户端对第一日历客户端显示的原始日历信息进行修改得到的，避免了日历信息的准确性较低的问题，因此，解决了相关技术中日历信息管理的准确性较低的问题，达到了提高日历信息管理的准确性的效果。
图4是根据再一示例性实施例示出的一种日历信息管理方法的方法流程图，本实施例以该日历信息管理方法应用于第二日历客户端中来进行举例说明，其中，第二日历客户端可以是安装在图1所示实施环境中的第二终端140上的日历客户端，参见图4，该日历信息管理方法可以包括如下几个步骤：
在步骤401中，接收服务器推送的共享日历信息，共享日历信息是服务器接收到第一日历客户端发布的共享日历信息后，向第二日历客户端推送的，第二日历客户端第二用户账号登录的日历客户端，第一日历客户端是第一用户账号登陆的日历客户端，第二用户账号与第一用户账号关联，共享日历信息是第一日历客户端对第一日历客户端显示的原始日历信息进行修改得到的。
在步骤402中，采用共享日历信息更新第二原始日历信息，第二原始日历信息是第二日历客户端在第二日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到的。
综上所述，本公开实施例提供的日历信息管理方法，第二日历客户端通过接收服务器推送的共享日历信息，并采用共享日历信息更新第二原始日历信息，由于服务器向第二日历客户端推送的共享日历信息是第一日历客户端对第一日历客户端显示的原始日历信息进行修改得到的，避免了日历信息的准确性较低的问题，因此，解决了相关技术中日历信息管理的准确性较低的问题，达到了提高日历信息管理的准确性的效果。
可选地，步骤402可以包括：
采用共享日历信息替换第二原始日历信息。
可选地，步骤402可以包括：
将共享日历信息和第二原始日历信息进行合并。
上述所有可选技术方案，可以采用任意结合形成本公开的可选实施例，在此不再一一赘述。
综上所述，本公开实施例提供的日历信息管理方法，第二日历客户端通过接收服务器 推送的共享日历信息，并采用共享日历信息更新第二原始日历信息，由于服务器向第二日历客户端推送的共享日历信息是第一日历客户端对第一日历客户端显示的原始日历信息进行修改得到的，避免了日历信息的准确性较低的问题，因此，解决了相关技术中日历信息管理的准确性较低的问题，达到了提高日历信息管理的准确性的效果。
图5-1是根据又一示例性实施例示出的一种日历信息管理方法的方法流程图，本实施例以该日历信息管理方法应用于图1所示实施环境中来进行举例说明，其中，在图1所示实施环境中，第一终端120上安装有第一日历客户端，第二终端140上安装有第二日历客户端，第三终端160上安装有第三日历客户端，参见图5-1，该日历信息管理方法可以包括如下几个步骤：
在步骤501中，第三日历客户端在第三日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到第三原始日历信息。
其中，第三日历客户端显示的日历界面可以如图5-2所示，参见图5-2，第三日历客户端中当前登陆用户账号是：xiaomi123，第三日历客户端显示的日历界面中显示的是2015年9月的日历，2015年9月共包括30个日期，每个日期可以对应一个日期页面，使用第三日历客户端的用户可以在图5-2所示的日历界面的指定日期页面中添加对应的事件信息得到第三原始日历信息，其中，指定日期可以是事件信息指示的事件的发生日期，第三原始日历信息可以包括：日期信息和事件信息，事件信息用于指示日期信息对应的日期发生的事件，也即，日期信息指示的日期即为指定日期。示例地，使用第三日历客户端的用户可以在9月12日这个日期对应的日期页面添加事件信息“下午3点半，XX公司在学校体育馆举行招聘会”得到第三原始日历信息，因此，第三原始日历信息可以为“9月12日下午3点半，XX公司在学校体育馆举行招聘会”。
第三日历客户端在第三日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到第三原始日历信息后，第三日历客户端显示的日历界面可以显示第三原始日历信息，可选地，第三日历客户端显示的日历界面可以显示第三原始日历信息的部分信息，当使用第三日历客户端的用户点击该部分信息时，第三日历客户端显示的日历界面显示完整的第三原始日历信息，示例地，如图5-2所示，第三日历客户端显示的日历界面上，在9月12日对应的日期页面显示有“招聘会”，当使用第三日历客户端的用户点击该“招聘会”时，第三日历客户端显示的日历界面显示完整的第三原始日历信息，第三日历客户端显示的日历界面显示完整的第三原始日历信息如图5-3所示。
在步骤502中，第三日历客户端向服务器发布第三原始日历信息。
第三日历客户端得到第三原始日历信息后，可以向服务器发布的第三原始日历信息。示例地，第三日历客户端向服务器发布第三原始日历信息“9月12日下午3点半，XX公司在学校体育馆举行招聘会”。
在步骤503中，服务器接收第三日历客户端发布的第三原始日历信息。
第三日历客户端向服务器发布原始日历信息时，服务器可以接收第三日历客户端发布的第三原始日历信息。示例地，服务器接收第三原始日历信息“9月12日下午3点半，XX公司在学校体育馆举行招聘会”。
在步骤504中，服务器向第一日历客户端推送第三原始日历信息，第一日历客户端中登录的用户账号为第一用户账号，第三日历客户端中登录的用户账号与第一用户账号关联。
服务器接收到第三日历客户端发布的第三原始日历信息后，可以向第一日历客户端推送原始日历信息。其中，第一日历客户端是第一用户账号登录的日历客户端，第一用户账号与第三日历客户端中登录的用户账户关联。示例地，服务器向第一日历客户端推送第三原始日历信息“9月12日下午3点半，XX公司在学校体育馆举行招聘会”。
需要说明的是，在本公开实施中，第一日历客户端中登录的用户账号为第一用户账号，第三日历客户端中登录的用户账号与第一用户账号关联，示例地，假设第一用户账号为xiaoxiao111，则第一用户账号xiaoxiao111与第三日历客户端中登陆用户账号xiaomi123关联。
在步骤505中，第一日历客户端接收服务器推送的第三原始日历信息。
服务器向第一日历客户端推送第三原始日历信息时，第一日历客户端可以接收服务器推送的第三原始日历信息，示例地，第一日历客户端接收第三原始日历信息“9月12日下午3点半，XX公司在学校体育馆举行招聘会”。
在步骤506中，第一日历客户端采用第三原始日历信息更新第一原始日历信息得到原始日历信息。
第一日历客户端接收服务器推送的第三原始日历信息后，可以采用第三原始日历信息更新第一原始日历信息得到原始日历信息，其中，第一原始日历信息是第一日历客户端在第一日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到的。示例地，第一原始日历信息可以为“9月13日下午3点半，XX公司在学校体育馆举行招聘会”，则第一日历客户端显示的日历界面可以如图5-4所示。其中，该图5-4对应的说明可以参考步骤501中关于图5-2所示的说明，本公开实施例在此不再赘述。示例地，第一日历客户端采用第三原始日历信息“9月12日下午3点半，XX公司在学校体育馆举行招聘会”更新第一原始日历信息“9月13日下午3点半，XX公司在学校体育馆举行招聘会”。
在本公开实施例中，第一日历客户端采用第三原始日历信息更新第一原始日历信息得到原始日历信息可以包括以下两种方式：
方式一、第一日历客户端采用第三原始日历信息替换第一原始日历信息得到原始日历信息。
示例地，第一日历客户端可以确定出第三原始日历信息中的日期信息和事件信息，然后将第三原始日历信息中的事件信息添加在该原始日历信息中的日期信息对应的日期页面中，并删除第一原始日历信息，得到原始日历信息，其中，该原始日历信息也即是第三 原始日历信息，示例地，第一日历客户端采用第三原始日历信息“9月12日下午3点半，XX公司在学校体育馆举行招聘会”替换第一原始日历信息“9月13日下午3点半，XX公司在学校体育馆举行招聘会”得到原始日历信息的界面图可以如图5-5所示，参见图5-5，原始日历信息可以为“9月12日下午3点半，XX公司在学校体育馆举行招聘会”。
方式二、第一日历客户端将第三原始日历信息和第一原始日历信息进行合并得到原始日历信息。
示例地，第一日历客户端可以确定出第三原始日历信息中的日期信息和事件信息，然后将第三原始日历信息中的事件信息添加在该原始日历信息中的日期信息对应的日期页面中，得到原始日历信息。示例地，第一日历客户端将第三原始日历信息“9月12日下午3点半，XX公司在学校体育馆举行招聘会”与第一原始日历信息“9月13日下午3点半，XX公司在学校体育馆举行招聘会”进行合并，原始日历信息的界面图可以如图5-6所示，参见图5-6，原始日历信息可以为“9月12日下午3点半，XX公司在学校体育馆举行招聘会”和“9月13日下午3点半，XX公司在学校体育馆举行招聘会”。
需要说明的是，本公开实施例是以原始日历信息是第一日历客户端采用第三原始日历信息更新第一原始日历信息得到的为例进行说明的，实际应用中，原始日历信息还可以是第一日历客户端在第一日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到的，其中，第一日历客户端在第一日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到原始日历信息的过程与步骤501中第三日历客户端在第三日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到第三原始日历信息的过程相同或者类似，其实现过程可以参考步骤501，本公开实施例在此不再赘述。还需要说明的是，本实施例步骤506以后均以原始日历信息为“9月12日下午3点半，XX公司在学校体育馆举行招聘会”为例进行说明。
在步骤507中，第一日历客户端显示原始日历信息。
第一日历客户端接收到服务器推送的原始日历信息后，可以显示原始日历信息，示例地，第一日历客户端显示原始日历信息“9月12日下午3点半，XX公司在学校体育馆举行招聘会”。
需要说明的是，第一日历客户端在显示原始日历信息时，可以将原始日历信息中的事件信息添加在原始日历信息中的日期信息指示的日期对应的日期页面中，并在第一日历客户端的显示界面上进行显示，本公开实施例对此不做限定。
在步骤508中，第一日历客户端接收对原始日历信息的更新指令。
在本公开实施例中，原始日历信息中可能存在与实际情况不符合的信息，导致原始日历信息的准确性较低，示例地，假设XX公司的招聘会是9月15日下午3点半，在学校体育馆举行，而第一日历客户端显示的原始日历信息为“9月12日下午3点半，XX公司在学校体育馆举行招聘会”，因此，原始日历信息的准确性较低。但是在本公开实施例中，第一日历客户端显示原始日历信息后，使用第一日历客户端的用户可以对原始日历信息进 行更新，示例地，使用第一日历客户端的用户可以修改原始日历信息的内容，也可以在原始日历信息中增加新的信息，本公开实施例对此不做限定。
使用第一日历客户端的用户修改原始日历信息的内容或者在原始日历信息中增加新的信息时，可以触发对原始日历信息的更新指令，第一日历客户端可以接收该更新指令，示例地，第一日历客户端接收对原始日历信息“9月12日下午3点半，XX公司在学校体育馆举行招聘会”的更新指令。
在步骤509中，第一日历客户端根据更新指令，对原始日历信息中更新指令指示的内容进行修改，得到共享日历信息。
第一日历客户端接收到使用第一日历客户端的用户触发的更新指令后，可以根据更新指令，对原始日历信息中更新指令指示的内容进行修改，得到共享日历信息。
示例地，请参考图5-7，其示出的是图5-1所示实施例提供的一种第一日历客户端根据更新指令，对原始日历信息中更新指令指示的内容进行修改，得到共享日历信息的方法流程图，参见图5-7，该方法流程可以包括如下几个步骤：
在步骤5091中，第一日历客户端显示提示信息，提示信息用于提示用户对原始日历信息中更新指令指示的内容进行修改。
第一日历客户端在接收到用户触发的更新指令时，可以显示提示信息，该提示信息用于提示用户对原始日历信息中更新指令指示的内容进行修改，示例地，该提示信息可以为：“确认修改该日历信息？”，第一日历客户端显示提示信息的界面可以如图5-8所示，参见图5-8，该日历界面中显示有提示框，提示框中显示有提示信息“确认修改该日历信息？”以及“确认”按钮。
在步骤5092中，在接收到用户触发的指示进行修改的确认指令时，第一日历客户端对原始日历信息中更新指令指示的内容进行修改。
第一日历客户端显示提示信息后，用户可以对提示信息进行操作触发指示进行修改的确认指令。示例地，用户点击图5-8所示的“确认”按钮，触发指示进行修改的确认指令。第一日历客户端在接收到该触发指令时，可以对原始日历信息中更新指令指示的内容进行修改。
其中，原始日历信息可以包括日期信息和事件信息，事件信息用于指示日期信息对应的日期发生的事件，因此，第一日历客户端根据更新指令，对原始日历信息中更新指令指示的内容进行修改可以包括：第一日历客户端根据更新指令对日期信息和事件信息中的至少一种进行修改。也即，第一日历客户端可以修改原始日历信息中的事件信息，也可以修改原始日历信息中的日期信息，本公开实施例对此不做限定。实际应用中，当更新指令指示的内容为日期信息时，第一日历客户端对原始日历信息中的日期信息进行修改，当更新指令指示的内容为事件信息时，第一日历客户端对原始日历信息中的事件信息进行修改。
在本公开实施例中，由于原始日历信息中的日期信息与实际的日期信息不符，因此，第一日历客户端可以根据更新指令，对原始日历信息中的日期信息进行修改，得到共享日 历信息，示例地，第一日历客户端对原始日历信息中的日期信息进行修改得到的共享日历信息可以为“9月15日下午3点半，XX公司在学校体育馆举行招聘会”。第一日历客户端根据更新指令，对原始日历信息中更新指令指示的内容进行修改，得到共享日历信息后的界面图可以如图5-9所示。
在步骤510中，第一日历客户端向服务器发布共享日历信息。
第一日历客户端对原始日历信息进行修改得到共享日历信息后，可以向服务器发布共享日历信息，示例地，第一日历客户端向服务器发布共享日历信息“9月15日下午3点半，XX公司在学校体育馆举行招聘会”。
在步骤511中，服务器接收第一日历客户端发布的共享日历信息。
第一日历客户端向服务器发布共享日历信息时，服务器可以接收第一日历客户端发布的共享日历信息，示例地，服务器接收共享日历信息“9月15日下午3点半，XX公司在学校体育馆举行招聘会”。
在步骤512中，服务器获取与第一用户账号关联的第二用户账号。
服务器接收到第一日历客户端发布的共享日历信息后，可以获取与第一用户账号关联的第二用户账号，示例地，服务器获取与第一用户账号xiaoxiao111关联的用户账号。
在本公开实施例中，订阅同一订阅账号的用户账号可以为关联的用户账号，因此，服务器可以根据第一用户账号的订阅账号确定与第一用户账号关联的第二用户账号。示例地，请参考图5-10，其示出的是图5-1所示实施例提供的一种服务器获取与第一用户账号关联的第二用户账号的方法流程图，参见图5-10，该方法流程可以包括：
在子步骤5111a中，服务器获取第一用户账号的订阅账号。
示例地，假设第一用户账号xiaoxiao111的订阅账号为dingyue1，则服务器获取订阅账号dingyue1。
在本公开实施例中，服务器可以存储用户账号与订阅账号的对应关系，服务器根据用户账号和订阅账号的对应关系获取第一用户账号的订阅账号，示例地，服务器存储的用户账号与订阅账号的对应关系可以如下表1所示：
表1
Figure PCTCN2015099734-appb-000001
服务器可以根据第一用户账号xiaoxiao111，查询表1所示的对应关系，得到第一用户账号xiaoxiao111的订阅账号dingyue1，进而获取该订阅账号dingyue1。
在子步骤5112a中，服务器获取订阅订阅账号的其他用户账号，其他用户账号不包括第一用户账号。
服务器获取到第一用户账号的订阅账号后，可以获取订阅该订阅账号的其他用户账号，该其他用户账号不包括第一用户账号。示例地，服务器获取订阅订阅账号dingyue1的其他用户账号。
参见表1可知，订阅订阅账号dingyue1的其他用户账户包括：用户账号xiaomi111和用户账号Xiaomi112，服务器可以根据订阅账号dingyue1，查询表1所示的对应关系，得到订阅订阅账号dingyue1的其他用户账户xiaomi111和Xiaomi112。
在子步骤5113a中，服务器将其他用户账号作为第二用户账号。
服务器获取到订阅订阅账号的其他用户账号后，将该其他用户账号作为第二用户账号，示例地，服务器将用户账号xiaomi111和Xiaomi112作为第二用户账号。
需要说明的是，参见上述可知，用户账号xiaomi111为登录在第三日历客户端中的用户账号，因此，为了便于后续描述，本公开实施例以第二用户账号为用户账号Xiaomi112为例进行说明。
参见表1还可知，服务器还存储有用户账号Xiaomi112、Xiaomii001、Xiaomii002和订阅账号dingyue2的对应关系，其中，Xiaomi112、Xiaomii001、Xiaomii002都订阅了订阅账号dingyue2，本公开实施例在此不再赘述。
在本公开实施例中，订阅第一用户账号的用户账号可以为与第一用户账号关联的用户账号，因此，服务器可以确定订阅第一用户账号的用户账号，该订阅第一用户账号的用户账号即为与第一用户账号关联的第二用户账号。示例地，请参考图5-11，其示出的是图5-1所示实施例提供的另一种服务器获取与第一用户账号关联的第二用户账号的方法流程图，参见图5-11，该方法流程可以包括：
在子步骤5111b中，服务器获取订阅第一用户账号的用户账号。
在本公开实施例中，服务器可以存储用户账号与订阅账号的对应关系，服务器可以获取订阅第一用户账号的用户账号，示例地，服务器存储的用户账号与订阅账号的对应关系可以如下表2所示：
表2
Figure PCTCN2015099734-appb-000002
服务器查询表2所示的对应关系，得到订阅第一用户账号xiaoxiao111的用户账号，参见表1可知，订阅第一用户账号xiaoxiao111的用户账号包括：xiaomi111、Xiaomi112和Xiaomii002，因此，服务器获取用户账号xiaomi111、Xiaomi112和Xiaomii002。
在子步骤5112b中，服务器将订阅第一用户账号的用户账号作为第二用户账号。
服务器获取到订阅第一用户账号的用户账号后，将该订阅第一用户账号的用户账号作为与第二用户账号，示例地，服务器将用户账号xiaomi111、Xiaomi112和Xiaomii002作为第二用户账号。
需要说明的是，在本公开实施例中，为了便于后续描述，本公开实施例以第二用户账号为用户账号Xiaomi112为例进行说明。
在本公开实施例中，可以手动配置用户账号关联列表，该用户账号关联列表记录了各个用户账号的关联关系，服务器可以存储该用户账号关联列表，并根据该用户账号关联列表获取与第一用户账号关联的第二用户账号。示例地，请参考图5-12，其示出的是图5-1所示实施例提供的再一种服务器获取与第一用户账号关联的第二用户账号的方法流程图，参见图5-12，该方法流程可以包括：
在子步骤5111c中，服务器根据第一用户账号，查询预设的用户账号关联列表，用户账号关联列表记录了各个用户账号的关联关系。
示例地，预设的用户账号关联列表可以如下表3所示：
表3
Figure PCTCN2015099734-appb-000003
参见表3，服务器存储的用户账号为xiaoxiao111和Xiaomii001，其中，与用户账号xiaoxiao111关联的用户账号为Xiaomi112和xiaomi111，与用户账号Xiaomii001关联的用户账号为Xiaomii002。
服务器根据第一用户账号xiaoxiao111查询表1所示用户账号关联列表可以确定与第一用户账号xiaoxiao111关联的用户账号为Xiaomi112和xiaomi111。
在子步骤5112c中，服务器将从用户账号关联列表查询得到的与第一用户账号关联的用户账号作为第二用户账号。
服务器查询得到与第一用户账号关联的用户账号后，将与第一用户账号关联的用户账号作为第二用户账号，示例地，服务器将用户账号Xiaomi112和xiaomi111作为第二用户账号。
需要说明的是，在本公开实施例中，为了便于后续描述，本公开实施例以第二用户账 号为用户账号Xiaomi112为例进行说明。
在步骤513中，服务器向第二日历客户端推送共享日历信息，第二日历客户端是第二用户账号登陆的日历客户端。
服务器获取到与第一用户账号关联的第二用户账号后，向第二日历客户端推送共享日历信息，其中，第二日历客户端是第二用户账号登陆的日历客户端，示例地，第二日历客户端中登录的用户账号为Xiaomi112，服务器向第二日历客户端推送共享日历信息“9月15日下午3点半，XX公司在学校体育馆举行招聘会”。
在步骤514中，第二日历客户端接收服务器推送的共享日历信息。
服务器向第二日历客户端器推送的共享日历信息时，第二日历客户端可以接收服务器推送的共享日历信息，示例地，第二日历客户端接收服务器推送的共享日历信息“9月15日下午3点半，XX公司在学校体育馆举行招聘会”。
在步骤515中，第二日历客户端采用共享日历信息更新第二原始日历信息。
该步骤515的与上述步骤506相同或者类似，其实现过程可以参考步骤506，本公开实施例在此不再赘述，但是需要说明的是，在本步骤515中，第二原始日历信息是第二日历客户端在第二日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到的。
需要说明的是，本公开实施例提供的日历信息管理方法步骤的先后顺序可以进行适当调整，步骤也可以根据情况进行相应增减，任何熟悉本技术领域的技术人员在本公开揭露的技术范围内，可轻易想到变化的方法，都应涵盖在本公开的保护范围之内，因此不再赘述。
综上所述，本公开实施例提供的日历信息管理方法，服务器通过接收第一日历客户端发布的共享日历信息，共享日历信息是第一日历客户端对第一日历客户端显示的原始日历信息进行修改得到的；向第二日历客户端推送共享日历信息，以使得第二日历客户端采用共享日历信息更新第二原始日历信息，第二原始日历信息是第二日历客户端在第二日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到的。由于共享日历信息是第一日历客户端对第一日历客户端显示的原始日历信息进行修改得到的，避免了日历信息的准确性较低的问题，因此，解决了相关技术中日历信息管理的准确性较低的问题，达到了提高日历信息管理的准确性的效果。
下述为本公开装置实施例，可以用于执行本公开方法实施例。对于本公开装置实施例中未披露的细节，请参照本公开方法实施例。
图6是根据一示例性实施例示出的一种日历信息管理装置600的框图，该日历信息管理装置600可以通过软件、硬件或者两者的结合实现成为图1所示实施环境中的服务器180的部分或者全部，参见图6，该日历信息管理装置600可以包括：
第一接收模块610，被配置为接收第一日历客户端发布的共享日历信息，共享日历信息是第一日历客户端对第一日历客户端显示的原始日历信息进行修改得到的。
第一推送模块620，被配置为向第二日历客户端推送第一接收模块610接收到的共享日历信息，以使得第二日历客户端采用共享日历信息更新第二原始日历信息，第二原始日历信息是第二日历客户端在第二日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到的，第二日历客户端是第二用户账号登陆的日历客户端，第一日历客户端是第一用户账号登陆的日历客户端，第二用户账号与第一用户账号关联。
综上所述，本公开实施例提供的日历信息管理装置，服务器通过接收第一日历客户端发布的共享日历信息，共享日历信息是第一日历客户端对第一日历客户端显示的原始日历信息进行修改得到的；向第二日历客户端推送共享日历信息，以使得第二日历客户端采用共享日历信息更新第二原始日历信息，第二原始日历信息是第二日历客户端在第二日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到的。由于共享日历信息是第一日历客户端对第一日历客户端显示的原始日历信息进行修改得到的，避免了日历信息的准确性较低的问题，因此，解决了相关技术中日历信息管理的准确性较低的问题，达到了提高日历信息管理的准确性的效果。
图7是根据一示例性实施例示出的另一种日历信息管理装置600的框图，该日历信息管理装置600可以通过软件、硬件或者两者的结合实现成为图1所示实施环境中的服务器180的部分或者全部，参见图7，该日历信息管理装置600可以包括：
第一接收模块610，被配置为接收第一日历客户端发布的共享日历信息，共享日历信息是第一日历客户端对第一日历客户端显示的原始日历信息进行修改得到的。
第一推送模块620，被配置为向第二日历客户端推送第一接收模块610接收到的共享日历信息，以使得第二日历客户端采用共享日历信息更新第二原始日历信息，第二原始日历信息是第二日历客户端在第二日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到的，第二日历客户端是第二用户账号登陆的日历客户端，第一日历客户端是第一用户账号登陆的日历客户端，第二用户账号与第一用户账号关联。
可选地，原始日历信息是第一日历客户端采用第三原始日历信息更新第一原始日历信息得到的，第三原始日历信息是第三日历客户端在第三日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到并发布至服务器由服务器推送给第一日历客户端的，第一原始日历信息是第一日历客户端在第一日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到的，原始日历信息包括：日期信息和事件信息，事件信息用于指示日期信息对应的日期发生的事件；请继续参考图7，该日历信息管理装置600还可以包括：
第二接收模块630，被配置为接收第三日历客户端发布的第三原始日历信息，第三日历客户端中登录的用户账号与第一用户账号关联；
第二推送模块640，被配置为向第一日历客户端推送第二接收模块630接收到的第三原始日历信息。
可选地，原始日历信息是第一日历客户端在第一日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到的，原始日历信息包括：日期信息和事件信息，事件信息用于指示日期信息对应的日期发生的事件。
可选地，请继续参考图7，该日历信息管理装置600还可以包括：
获取模块650，被配置为获取与第一用户账号关联的第二用户账号。
可选地，获取模块650，被配置为：
获取第一用户账号的订阅账号；
获取订阅订阅账号的其他用户账号，其他用户账号不包括第一用户账号；
将其他用户账号作为第二用户账号。
可选地，获取模块650，被配置为：
获取订阅第一用户账号的用户账号；
将订阅第一用户账号的用户账号作为第二用户账号。
可选地，获取模块650，被配置为：
根据第一用户账号，查询预设的用户账号关联列表，用户账号关联列表记录了各个用户账号的关联关系；
将从用户账号关联列表查询得到的与第一用户账号关联的用户账号作为第二用户账号。
综上所述，本公开实施例提供的日历信息管理装置，服务器通过接收第一日历客户端发布的共享日历信息，共享日历信息是第一日历客户端对第一日历客户端显示的原始日历信息进行修改得到的；向第二日历客户端推送共享日历信息，以使得第二日历客户端采用共享日历信息更新第二原始日历信息，第二原始日历信息是第二日历客户端在第二日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到的。由于共享日历信息是第一日历客户端对第一日历客户端显示的原始日历信息进行修改得到的，避免了日历信息的准确性较低的问题，因此，解决了相关技术中日历信息管理的准确性较低的问题，达到了提高日历信息管理的准确性的效果。
图8是根据另一示例性实施例示出的一种日历信息管理装置700的框图，该日历信息管理装置700可以通过软件、硬件或者两者的结合实现成为第一日历客户端的部分或者全部，该第一日历客户端可以是安装在图1所示实施环境中的第一终端120上的日历客户端，参见图8，该日历信息管理装置700可以包括：
显示模块710，被配置为显示原始日历信息。
第一接收模块720，被配置为接收对显示模块710显示的原始日历信息的更新指令。
修改模块730，被配置为根据第一接收模块720接收到的更新指令，对原始日历信息 中更新指令指示的内容进行修改，得到共享日历信息。
发布模块740，被配置为向服务器发布修改模块730得到的共享日历信息，以使得服务器向第二日历客户端推送共享日历信息，第二日历客户端是第二用户账号登陆的日历客户端，第一日历客户端是第一用户账号登陆的日历客户端，第二用户账号与第一用户账号关联。
综上所述，本公开实施例提供的日历信息管理装置，第一日历客户端通过显示原始日历信息，接收对原始日历信息的更新指令，根据更新指令，对原始日历信息中更新指令指示的内容进行修改，得到共享日历信息，并向服务器发布共享日历信息，以使得服务器向第二日历客户端推送共享日历信息，由于服务器向第二日历客户端推送的共享日历信息是第一日历客户端对第一日历客户端显示的原始日历信息进行修改得到的，避免了日历信息的准确性较低的问题，因此，解决了相关技术中日历信息管理的准确性较低的问题，达到了提高日历信息管理的准确性的效果。
图9是根据另一示例性实施例示出的另一种日历信息管理装置700的框图，该日历信息管理装置700可以通过软件、硬件或者两者的结合实现成为第一日历客户端的部分或者全部，该第一日历客户端可以是安装在图1所示实施环境中的第一终端120上的日历客户端，参见图9，该日历信息管理装置700可以包括：
显示模块710，被配置为显示原始日历信息。
第一接收模块720，被配置为接收对显示模块710显示的原始日历信息的更新指令。
修改模块730，被配置为根据第一接收模块720接收到的更新指令，对原始日历信息中更新指令指示的内容进行修改，得到共享日历信息。
发布模块740，被配置为向服务器发布修改模块730得到的共享日历信息，以使得服务器向第二日历客户端推送共享日历信息，第二日历客户端是第二用户账号登陆的日历客户端，第一日历客户端是第一用户账号登陆的日历客户端，第二用户账号与第一用户账号关联。
可选地，修改模块730，被配置为：
显示提示信息，提示信息用于提示用户对原始日历信息中更新指令指示的内容进行修改；
在接收到用户触发的指示进行修改的确认指令时，对原始日历信息中更新指令指示的内容进行修改。
可选地，原始日历信息包括日期信息和事件信息，事件信息用于指示日期信息对应的日期发生的事件，
修改模块730，被配置为：
根据更新指令对日期信息和事件信息中的至少一种进行修改。
可选地，请继续参考图9，该日历信息管理装置700还可以包括：
第二接收模块750，被配置为接收服务器推送的第三原始日历信息，第三原始日历信息是第三日历客户端在第三日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到并发布至服务器的，第三日历客户端中登录的用户账号与第一用户账号关联。
可选地，请继续参考图9，该日历信息管理装置700还可以包括：
更新模块760，被配置为采用第二接收模块750接收到的第三原始日历信息更新第一原始日历信息得到原始日历信息，第一原始日历信息是第一日历客户端在第一日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到的。
可选地，更新模块760，被配置为：采用第二接收模块750接收到的第三原始日历信息替换第一原始日历信息得到原始日历信息。
可选地，更新模块760，被配置为：将第二接收模块750接收到的第三原始日历信息和第一原始日历信息进行合并得到原始日历信息。
可选地，请继续参考图9，该日历信息管理装置700还可以包括：
添加模块770，被配置为在第一日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到原始日历信息。
综上所述，本公开实施例提供的日历信息管理装置，第一日历客户端通过显示原始日历信息，接收对原始日历信息的更新指令，根据更新指令，对原始日历信息中更新指令指示的内容进行修改，得到共享日历信息，并向服务器发布共享日历信息，以使得服务器向第二日历客户端推送共享日历信息，由于服务器向第二日历客户端推送的共享日历信息是第一日历客户端对第一日历客户端显示的原始日历信息进行修改得到的，避免了日历信息的准确性较低的问题，因此，解决了相关技术中日历信息管理的准确性较低的问题，达到了提高日历信息管理的准确性的效果。
图10是根据再一示例性实施例示出的一种日历信息管理装置800的框图，该日历信息管理装置800可以通过软件、硬件或者两者的结合实现成为第二日历客户端的部分或者全部，该第二日历客户端可以是安装在图1所示实施环境中的第二终端140上的日历客户端，参见图10，该日历信息管理装置800可以包括：
接收模块810，被配置为接收服务器推送的共享日历信息，共享日历信息是服务器接收到第一日历客户端发布的共享日历信息后，向第二日历客户端推送的，第二日历客户端是登陆第二用户账号的日历客户端，第一日历客户端是第一用户账号登陆的日历客户端，第二用户账号与第一用户账号关联，共享日历信息是第一日历客户端对第一日历客户端显示的原始日历信息进行修改得到的；
更新模块820，被配置为采用接收模块810接收到的共享日历信息更新第二原始日历信息，第二原始日历信息是第二日历客户端在第二日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到的。
可选地，更新模块820，被配置为：
采用接收模块810接收到的共享日历信息替换第二原始日历信息。
可选地，更新模块820，被配置为：
将接收模块810接收到的共享日历信息和第二原始日历信息进行合并。
综上所述，本公开实施例提供的日历信息管理装置，第二日历客户端通过接收服务器推送的共享日历信息，并采用共享日历信息更新第二原始日历信息，由于服务器向第二日历客户端推送的共享日历信息是第一日历客户端对第一日历客户端显示的原始日历信息进行修改得到的，避免了日历信息的准确性较低的问题，因此，解决了相关技术中日历信息管理的准确性较低的问题，达到了提高日历信息管理的准确性的效果。
图11是根据一示例性实施例示出的一种日历信息管理装置1100的框图。例如，装置1100可以被提供为一服务器。参照图11，装置1100包括处理组件1122，其进一步包括一个或多个处理器，以及由存储器1132所代表的存储器资源，用于存储可由处理部件1122执行的指令，例如应用程序。存储器1132中存储的应用程序可以包括一个或一个以上的每一个对应于一组指令的模块。此外，处理组件1122被配置为执行指令，以执行上述日历信息管理方法，该方法包括：
接收第一日历客户端发布的共享日历信息，共享日历信息是第一日历客户端对第一日历客户端显示的原始日历信息进行修改得到的；
向第二日历客户端推送共享日历信息，以使得第二日历客户端采用共享日历信息更新第二原始日历信息，第二原始日历信息是第二日历客户端在第二日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到的，第二日历客户端是第二用户账号登陆的日历客户端，第一日历客户端是第一用户账号登陆的日历客户端，第二用户账号与第一用户账号关联。
可选地，原始日历信息是第一日历客户端采用第三原始日历信息更新第一原始日历信息得到的，第三原始日历信息是第三日历客户端在第三日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到并发布至服务器由服务器推送给第一日历客户端的，第一原始日历信息是第一日历客户端在第一日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到的，原始日历信息包括：日期信息和事件信息，事件信息用于指示日期信息对应的日期发生的事件；
在接收第一日历客户端发布的共享日历信息之前，该方法还包括：
接收第三日历客户端发布的第三原始日历信息，第三日历客户端中登录的用户账号与第一用户账号关联；
向第一日历客户端推送第三原始日历信息。
可选地，原始日历信息是第一日历客户端在第一日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到的，原始日历信息包括：日期信息和事件信息，事件信息用于指示日期信息对应的日期发生的事件。
可选地，在向第二日历客户端推送共享日历信息之前，方法还包括：
获取与第一用户账号关联的第二用户账号。
可选地，获取与第一用户账号关联的第二用户账号，包括：
获取第一用户账号的订阅账号；
获取订阅订阅账号的其他用户账号，其他用户账号不包括第一用户账号；
将其他用户账号作为第二用户账号。
可选地，获取与第一用户账号关联的第二用户账号，包括：
获取订阅第一用户账号的用户账号；
将订阅第一用户账号的用户账号作为与第二用户账号。
可选地，获取与第一用户账号关联的第二用户账号，包括：
根据第一用户账号，查询预设的用户账号关联列表，用户账号关联列表记录了各个用户账号的关联关系；
将从用户账号关联列表查询得到的与第一用户账号关联的用户账号作为第二用户账号。
装置1100还可以包括一个电源组件1126被配置为执行装置1100的电源管理，一个有线或无线网络接口1150被配置为将装置1100连接到网络，和一个输入输出(I/O)接口1158。装置1100可以操作基于存储在存储器1132的操作系统，例如Windows ServerTM，Mac OS XTM，UnixTM，LinuxTM，FreeBSDTM或类似。
综上所述，本公开实施例提供的日历信息管理装置，通过接收第一日历客户端发布的共享日历信息，共享日历信息是第一日历客户端对第一日历客户端显示的原始日历信息进行修改得到的；向第二日历客户端推送共享日历信息，以使得第二日历客户端采用共享日历信息更新第二原始日历信息，第二原始日历信息是第二日历客户端在第二日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到的。由于共享日历信息是第一日历客户端对第一日历客户端显示的原始日历信息进行修改得到的，避免了日历信息的准确性较低的问题，因此，解决了相关技术中日历信息管理的准确性较低的问题，达到了提高日历信息管理的准确性的效果。
图12是根据另一示例性实施例示出的一种日历信息管理的装置1200的框图。例如，日历信息管理的装置1200可以是移动电话，计算机，数字广播终端，消息收发设备，游戏控制台，平板设备，医疗设备，健身设备，个人数字助理等，该日历信息管理的装置1200上可以安装日历客户端，日历信息管理的装置1200通过日历客户端实现对日历信息的管理。
参照图12，装置1200可以包括以下一个或多个组件：处理组件1202，存储器1204，电源组件1206，多媒体组件1208，音频组件1210，输入/输出(I/O)接口1212，传感器组件1214，以及通信组件1216。
处理组件1202通常控制装置1200的整体操作，诸如与显示，数据通信，和记录操作相关联的操作。处理组件1202可以包括一个或多个处理器1220来执行指令，以完成上述的方法的全部或部分步骤。此外，处理组件1202可以包括一个或多个模块，便于处理组件1202和其他组件之间的交互。例如，处理组件1202可以包括多媒体模块，以方便多媒体组件1208和处理组件1202之间的交互。
存储器1204被配置为存储各种类型的数据以支持在装置1200的操作。这些数据的示例包括用于在装置1200上操作的任何应用程序或方法的指令，联系人数据，电话簿数据，消息，图片，视频，日历数据等。存储器1204可以由任何类型的易失性或非易失性存储设备或者它们的组合实现，如静态随机存取存储器(SRAM)，电可擦除可编程只读存储器(EEPROM)，可擦除可编程只读存储器(EPROM)，可编程只读存储器(PROM)，只读存储器(ROM)，磁存储器，快闪存储器，磁盘或光盘。
电源组件1206为装置1200的各种组件提供电力。电源组件1206可以包括电源管理系统，一个或多个电源，及其他与为装置1200生成、管理和分配电力相关联的组件。
多媒体组件1208包括在装置1200和用户之间的提供一个输出接口的屏幕。在一些实施例中，屏幕可以包括液晶显示器(LCD)和触摸面板(TP)。如果屏幕包括触摸面板，屏幕可以被实现为触摸屏，以接收来自用户的输入信号。触摸面板包括一个或多个触摸传感器以感测触摸、滑动和触摸面板上的手势。触摸传感器可以不仅感测触摸或滑动动作的边界，而且还检测与触摸或滑动操作相关的持续时间和压力。
音频组件1210被配置为输出和/或输入音频信号。例如，音频组件1210包括一个麦克风(MIC)，当装置1200处于操作模式，如记录模式和语音识别模式时，麦克风被配置为接收外部音频信号。所接收的音频信号可以被进一步存储在存储器1204或经由通信组件1216发送。在一些实施例中，音频组件1210还包括一个扬声器，用于输出音频信号。
I/O接口1212为处理组件1202和外围接口模块之间提供接口，上述外围接口模块可以是键盘，点击轮，按钮等。这些按钮可包括但不限于：主页按钮、音量按钮、启动按钮和锁定按钮。
传感器组件1214包括一个或多个传感器，用于为装置1200提供各个方面的状态评估。例如，传感器组件1214可以检测到装置1200的打开/关闭状态，组件的相对定位，例如组件为装置1200的显示器和小键盘，传感器组件1214还可以检测装置1200或装置1200一个组件的位置改变，用户与装置1200接触的存在或不存在，装置1200方位或加速/减速和装置1200的温度变化。传感器组件1214可以包括接近传感器，被配置用来在没有任何的物理接触时检测附近物体的存在。传感器组件1214还可以包括光传感器，如CMOS或CCD图像传感器，用于在成像应用中使用。在一些实施例中，该传感器组件1214还可以包括加速度传感器，陀螺仪传感器，磁传感器，压力传感器或温度传感器。
通信组件1216被配置为便于装置1200和其他设备之间有线或无线方式的通信。装置1200可以接入基于通信标准的无线网络，如WiFi，2G或3G，或它们的组合。在一个示 例性实施例中，通信组件1216经由广播信道接收来自外部广播管理系统的广播信号或广播相关信息。在一个示例性实施例中，通信组件1216还包括近场通信(NFC)模块，以促进短程通信。例如，在NFC模块可基于射频识别(RFID)技术，红外数据协会(IrDA)技术，超宽带(UWB)技术，蓝牙(BT)技术和其他技术来实现。
在示例性实施例中，装置1200可以被一个或多个应用专用集成电路(ASIC)、数字信号处理器(DSP)、数字信号处理设备(DSPD)、可编程逻辑器件(PLD)、现场可编程门阵列(FPGA)、控制器、微控制器、微处理器或其他电子元件实现，用于执行上述方法。
在示例性实施例中，还提供了一种包括指令的非临时性计算机可读存储介质，例如包括指令的存储器1204，上述指令可由装置1200的处理器1220执行以完成上述方法。例如，非临时性计算机可读存储介质可以是ROM、随机存取存储器(RAM)、CD-ROM、磁带、软盘和光数据存储设备等。
一种非临时性计算机可读存储介质，当存储介质中的指令由装置1200的处理器执行时，使得装置1200能够执行一种日历信息管理方法，该方法包括：
显示原始日历信息；
接收对原始日历信息的更新指令；
根据更新指令，对原始日历信息中更新指令指示的内容进行修改，得到共享日历信息；
向服务器发布共享日历信息，以使得服务器向第二日历客户端推送共享日历信息，第二日历客户端是第二用户账号登陆的日历客户端，第一日历客户端是第一用户账号登陆的日历客户端，第二用户账号与第一用户账号关联。
可选地，根据更新指令，对原始日历信息中更新指令指示的内容进行修改，包括：
显示提示信息，提示信息用于提示用户对原始日历信息中更新指令指示的内容进行修改；
在接收到用户触发的指示进行修改的确认指令时，对原始日历信息中更新指令指示的内容进行修改。
可选地，原始日历信息包括日期信息和事件信息，事件信息用于指示日期信息对应的日期发生的事件，
根据更新指令，对原始日历信息中更新指令指示的内容进行修改，包括：
根据更新指令对日期信息和事件信息中的至少一种进行修改。
可选地，在显示原始日历信息之前，方法还包括：
接收服务器推送的第三原始日历信息，第三原始日历信息是第三日历客户端在第三日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到并发布至服务器的，第三日历客户端中登录的用户账号与第一用户账号关联。
可选地，在接收服务器推送的第三原始日历信息之后，方法还包括：
采用第三原始日历信息更新第一原始日历信息得到原始日历信息，第一原始日历信息 是第一日历客户端在第一日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到的。
可选地，采用第三原始日历信息更新第一原始日历信息得到原始日历信息，包括：
采用第三原始日历信息替换第一原始日历信息得到原始日历信息。
可选地，采用第三原始日历信息更新第一原始日历信息得到原始日历信息，包括：
将第三原始日历信息和第一原始日历信息进行合并得到原始日历信息。
可选地，在显示原始日历信息之前，方法还包括：
在第一日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到原始日历信息。
综上所述，本公开实施例提供的日历信息管理装置，通过显示原始日历信息，接收对原始日历信息的更新指令，根据更新指令，对原始日历信息中更新指令指示的内容进行修改，得到共享日历信息，并向服务器发布共享日历信息，以使得服务器向第二日历客户端推送共享日历信息，由于服务器向第二日历客户端推送共享日历信息是第一日历客户端对第一日历客户端显示的原始日历信息进行修改得到的，避免了日历信息的准确性较低的问题，因此，解决了相关技术中日历信息管理的准确性较低的问题，达到了提高日历信息管理的准确性的效果。
图13是根据再一示例性实施例示出的一种日历信息管理的装置1300的框图。例如，日历信息管理的装置1300可以是移动电话，计算机，数字广播终端，消息收发设备，游戏控制台，平板设备，医疗设备，健身设备，个人数字助理等，该日历信息管理的装置1300上可以安装日历客户端，日历信息管理的装置1300通过日历客户端实现对日历信息的管理。
参照图13，装置1300可以包括以下一个或多个组件：处理组件1302，存储器1304，电源组件1306，多媒体组件1308，音频组件1310，输入/输出(I/O)接口1312，传感器组件1314，以及通信组件1316。
处理组件1302通常控制装置1300的整体操作，诸如与显示，数据通信，和记录操作相关联的操作。处理组件1302可以包括一个或多个处理器1320来执行指令，以完成上述的方法的全部或部分步骤。此外，处理组件1302可以包括一个或多个模块，便于处理组件1302和其他组件之间的交互。例如，处理组件1302可以包括多媒体模块，以方便多媒体组件1308和处理组件1302之间的交互。
存储器1304被配置为存储各种类型的数据以支持在装置1300的操作。这些数据的示例包括用于在装置1300上操作的任何应用程序或方法的指令，联系人数据，电话簿数据，消息，图片，视频，日历数据等。存储器1304可以由任何类型的易失性或非易失性存储设备或者它们的组合实现，如静态随机存取存储器(SRAM)，电可擦除可编程只读存储器(EEPROM)，可擦除可编程只读存储器(EPROM)，可编程只读存储器(PROM)， 只读存储器(ROM)，磁存储器，快闪存储器，磁盘或光盘。
电源组件1306为装置1300的各种组件提供电力。电源组件1306可以包括电源管理系统，一个或多个电源，及其他与为装置1300生成、管理和分配电力相关联的组件。
多媒体组件1308包括在装置1300和用户之间的提供一个输出接口的屏幕。在一些实施例中，屏幕可以包括液晶显示器(LCD)和触摸面板(TP)。如果屏幕包括触摸面板，屏幕可以被实现为触摸屏，以接收来自用户的输入信号。触摸面板包括一个或多个触摸传感器以感测触摸、滑动和触摸面板上的手势。触摸传感器可以不仅感测触摸或滑动动作的边界，而且还检测与触摸或滑动操作相关的持续时间和压力。
音频组件1310被配置为输出和/或输入音频信号。例如，音频组件1310包括一个麦克风(MIC)，当装置1300处于操作模式，如记录模式和语音识别模式时，麦克风被配置为接收外部音频信号。所接收的音频信号可以被进一步存储在存储器1304或经由通信组件1316发送。在一些实施例中，音频组件1310还包括一个扬声器，用于输出音频信号。
I/O接口1312为处理组件1302和外围接口模块之间提供接口，上述外围接口模块可以是键盘，点击轮，按钮等。这些按钮可包括但不限于：主页按钮、音量按钮、启动按钮和锁定按钮。
传感器组件1314包括一个或多个传感器，用于为装置1300提供各个方面的状态评估。例如，传感器组件1314可以检测到装置1300的打开/关闭状态，组件的相对定位，例如组件为装置1300的显示器和小键盘，传感器组件1314还可以检测装置1300或装置1300一个组件的位置改变，用户与装置1300接触的存在或不存在，装置1300方位或加速/减速和装置1300的温度变化。传感器组件1314可以包括接近传感器，被配置用来在没有任何的物理接触时检测附近物体的存在。传感器组件1314还可以包括光传感器，如CMOS或CCD图像传感器，用于在成像应用中使用。在一些实施例中，该传感器组件1314还可以包括加速度传感器，陀螺仪传感器，磁传感器，压力传感器或温度传感器。
通信组件1316被配置为便于装置1300和其他设备之间有线或无线方式的通信。装置1300可以接入基于通信标准的无线网络，如WiFi，2G或3G，或它们的组合。在一个示例性实施例中，通信组件1316经由广播信道接收来自外部广播管理系统的广播信号或广播相关信息。在一个示例性实施例中，通信组件1316还包括近场通信(NFC)模块，以促进短程通信。例如，在NFC模块可基于射频识别(RFID)技术，红外数据协会(IrDA)技术，超宽带(UWB)技术，蓝牙(BT)技术和其他技术来实现。
在示例性实施例中，装置1300可以被一个或多个应用专用集成电路(ASIC)、数字信号处理器(DSP)、数字信号处理设备(DSPD)、可编程逻辑器件(PLD)、现场可编程门阵列(FPGA)、控制器、微控制器、微处理器或其他电子元件实现，用于执行上述方法。
在示例性实施例中，还提供了一种包括指令的非临时性计算机可读存储介质，例如包括指令的存储器1304，上述指令可由装置1300的处理器1320执行以完成上述方法。例 如，非临时性计算机可读存储介质可以是ROM、随机存取存储器(RAM)、CD-ROM、磁带、软盘和光数据存储设备等。
一种非临时性计算机可读存储介质，当存储介质中的指令由装置1300的处理器执行时，使得装置1300能够执行一种日历信息管理方法，该方法包括：
接收服务器推送的共享日历信息，共享日历信息是服务器接收到第一日历客户端发布的共享日历信息后，向第二日历客户端推送的，第二日历客户端是第二用户账号登陆的日历客户端，第二用户账号与第一用户账号关联，共享日历信息是第一日历客户端对第一日历客户端显示的原始日历信息进行修改得到的；
采用共享日历信息更新第二原始日历信息，第二原始日历信息是第二日历客户端在第二日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到的。
可选地，采用共享日历信息更新第二原始日历信息，包括：
采用共享日历信息替换第二原始日历信息。
可选地，采用共享日历信息更新第二原始日历信息，包括：
将共享日历信息和第二原始日历信息进行合并。
综上所述，本公开实施例提供的日历信息管理方法，第二日历客户端通过接收服务器推送的共享日历信息，并显示共享日历信息，由于服务器向第二日历客户端推送的共享日历信息是第一日历客户端对第一日历客户端显示的原始日历信息进行修改得到的，避免了日历信息的准确性较低的问题，因此，解决了相关技术中日历信息管理的准确性较低的问题，达到了提高日历信息管理的准确性的效果。
图14是根据一示例性实施例示出的一种日历信息管理系统1400的结构示意图。参见图14，该日历信息管理系统1400可以包括：服务器1410、第一日历客户端1420和第二日历客户端1430。
服务器1410包括图6、图7或图11所示的日历信息管理装置；
第一日历客户端1420包括图8、图9或图12所示的日历信息管理装置；
第二日历客户端1430包括图10或图13所示的日历信息管理装置。
综上所述，本公开实施例提供的日历信息管理系统，服务器通过接收第一日历客户端发布的共享日历信息，共享日历信息是第一日历客户端对第一日历客户端显示的原始日历信息进行修改得到的；向第二日历客户端推送共享日历信息，以使得第二日历客户端采用共享日历信息更新第二原始日历信息，第二原始日历信息是第二日历客户端在第二日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到的。由于共享日历信息是第一日历客户端对第一日历客户端显示的原始日历信息进行修改得到的，避免了日历信息的准确性较低的问题，因此，解决了相关技术中日历信息管理的准确性较低的问题，达到了提高日历信息管理的准确性的效果。
本领域技术人员在考虑说明书及实践这里公开的公开后，将容易想到本公开的其它实施方案。本申请旨在涵盖本公开的任何变型、用途或者适应性变化，这些变型、用途或者适应性变化遵循本公开的一般性原理并包括本公开未公开的本技术领域中的公知常识或惯用技术手段。说明书和实施例仅被视为示例性的，本公开的真正范围和精神由下面的权利要求指出。
应当理解的是，本公开并不局限于上面已经描述并在附图中示出的精确结构，并且可以在不脱离其范围进行各种修改和改变。本公开的范围仅由所附的权利要求来限制。

Claims (41)

  1. 一种日历信息管理方法，其特征在于，所述方法包括：
    接收第一日历客户端发布的共享日历信息，所述共享日历信息是所述第一日历客户端对所述第一日历客户端显示的原始日历信息进行修改得到的；
    向第二日历客户端推送所述共享日历信息，以使得所述第二日历客户端采用所述共享日历信息更新第二原始日历信息，所述第二原始日历信息是所述第二日历客户端在所述第二日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到的，所述第二日历客户端是第二用户账号登陆的日历客户端，所述第一日历客户端是第一用户账号登陆的日历客户端，所述第二用户账号与所述与第一用户账号关联。
  2. 根据权利要求1所述的方法，其特征在于，所述原始日历信息是所述第一日历客户端采用第三原始日历信息更新第一原始日历信息得到的，所述第三原始日历信息是第三日历客户端在所述第三日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到并发布至服务器由所述服务器推送给所述第一日历客户端的，所述第一原始日历信息是所述第一日历客户端在所述第一日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到的，所述原始日历信息包括：日期信息和所述事件信息，所述事件信息用于指示所述日期信息对应的日期发生的事件；
    在所述接收第一日历客户端发布的共享日历信息之前，所述方法还包括：
    接收所述第三日历客户端发布的所述第三原始日历信息，所述第三日历客户端中登录的用户账号与所述第一用户账号关联；
    向所述第一日历客户端推送所述第三原始日历信息。
  3. 根据权利要求1所述的方法，其特征在于，所述原始日历信息是所述第一日历客户端在所述第一日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到的，所述原始日历信息包括：日期信息和所述事件信息，所述事件信息用于指示所述日期信息对应的日期发生的事件。
  4. 根据权利要求1至3任一所述的方法，其特征在于，在所述向第二日历客户端推送所述共享日历信息之前，所述方法还包括：
    获取与所述第一用户账号关联的所述第二用户账号。
  5. 根据权利要求4所述的方法，其特征在于，所述获取与所述第一用户账号关联的所述第二用户账号，包括：
    获取所述第一用户账号的订阅账号；
    获取订阅所述订阅账号的其他用户账号，所述其他用户账号不包括所述第一用户账 号；
    将所述其他用户账号作为所述第二用户账号。
  6. 根据权利要求4所述的方法，其特征在于，所述获取与所述第一用户账号关联的所述第二用户账号，包括：
    获取订阅所述第一用户账号的用户账号；
    将所述订阅所述第一用户账号的用户账号作为所述第二用户账号。
  7. 根据权利要求4所述的方法，其特征在于，所述获取与所述第一用户账号关联的所述第二用户账号，包括：
    根据所述第一用户账号，查询预设的用户账号关联列表，所述用户账号关联列表记录了各个用户账号的关联关系；
    将从所述用户账号关联列表查询得到的与所述第一用户账号关联的用户账号作为所述第二用户账号。
  8. 一种日历信息管理方法，其特征在于，所述方法包括：
    显示原始日历信息；
    接收对所述原始日历信息的更新指令；
    根据所述更新指令，对所述原始日历信息中所述更新指令指示的内容进行修改，得到共享日历信息；
    向服务器发布所述共享日历信息，以使得所述服务器向第二日历客户端推送所述共享日历信息，所述第二日历客户端是第二用户账号登陆的日历客户端，第一日历客户端是第一用户账号登陆的日历客户端，所述第二用户账号与所述与第一用户账号关联。
  9. 根据权利要求8所述的方法，其特征在于，所述根据所述更新指令，对所述原始日历信息中所述更新指令指示的内容进行修改，包括：
    显示提示信息，所述提示信息用于提示用户对所述原始日历信息中所述更新指令指示的内容进行修改；
    在接收到所述用户触发的指示进行修改的确认指令时，对所述原始日历信息中所述更新指令指示的内容进行修改。
  10. 根据权利要求8或9所述的方法，其特征在于，所述原始日历信息包括日期信息和事件信息，所述事件信息用于指示所述日期信息对应的日期发生的事件，
    所述根据所述更新指令，对所述原始日历信息中所述更新指令指示的内容进行修改，包括：
    根据所述更新指令对所述日期信息和所述事件信息中的至少一种进行修改。
  11. 根据权利要求8至10任一所述的方法，其特征在于，在所述显示原始日历信息之前，所述方法还包括：
    接收所述服务器推送的第三原始日历信息，所述第三原始日历信息是第三日历客户端在所述第三日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到并发布至所述服务器的，所述第三日历客户端中登录的用户账号与所述第一用户账号关联。
  12. 根据权利要求11所述的方法，其特征在于，在所述接收所述服务器推送的第三原始日历信息之后，所述方法还包括：
    采用所述第三原始日历信息更新第一原始日历信息得到所述原始日历信息，所述第一原始日历信息是第一日历客户端在所述第一日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到的。
  13. 根据权利要求12所述的方法，其特征在于，所述采用所述第三原始日历信息更新第一原始日历信息得到所述原始日历信息，包括：
    采用所述第三原始日历信息替换所述第一原始日历信息得到所述原始日历信息。
  14. 根据权利要求12所述的方法，其特征在于，所述采用所述第三原始日历信息更新第一原始日历信息得到所述原始日历信息，包括：
    将所述第三原始日历信息和所述第一原始日历信息进行合并得到所述原始日历信息。
  15. 根据权利要求8至10任一所述的方法，其特征在于，在所述显示原始日历信息之前，所述方法还包括：
    在所述第一日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到所述原始日历信息。
  16. 一种日历信息管理方法，其特征在于，所述方法包括：
    接收服务器推送的共享日历信息，所述共享日历信息是所述服务器接收到第一日历客户端发布的共享日历信息后，向第二日历客户端推送的，所述第二日历客户端是第二用户账号登录的日历客户端，所述第一日历客户端是第一用户账号登陆的日历客户端，所述第二用户账号与所述与第一用户账号关联，所述共享日历信息是所述第一日历客户端对所述第一日历客户端显示的原始日历信息进行修改得到的；
    采用所述共享日历信息更新第二原始日历信息，所述第二原始日历信息是所述第二日历客户端在所述第二日历客户端显示的日历界面的指定日期页面中添加对应的事件信息 得到的。
  17. 根据权利要求16所述的方法，其特征在于，
    所述采用所述共享日历信息更新第二原始日历信息，包括：
    采用所述共享日历信息替换所述第二原始日历信息。
  18. 根据权利要求16所述的方法，其特征在于，
    所述采用所述共享日历信息更新第二原始日历信息，包括：
    将所述共享日历信息和所述第二原始日历信息进行合并。
  19. 一种日历信息管理装置，其特征在于，所述装置包括：
    第一接收模块，被配置为接收第一日历客户端发布的共享日历信息，所述共享日历信息是所述第一日历客户端对所述第一日历客户端显示的原始日历信息进行修改得到的；
    第一推送模块，被配置为向第二日历客户端推送所述共享日历信息，以使得所述第二日历客户端采用所述共享日历信息更新第二原始日历信息，所述第二原始日历信息是所述第二日历客户端在所述第二日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到的，所述第二日历客户端是第二用户账号登陆的日历客户端，所述第一日历客户端是第一用户账号登陆的日历客户端，所述第二用户账号与所述与第一用户账号关联。
  20. 根据权利要求19所述的装置，其特征在于，所述原始日历信息是所述第一日历客户端采用第三原始日历信息更新第一原始日历信息得到的，所述第三原始日历信息是第三日历客户端在所述第三日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到并发布至服务器由所述服务器推送给所述第一日历客户端的，所述第一原始日历信息是所述第一日历客户端在所述第一日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到的，所述原始日历信息包括：日期信息和所述事件信息，所述事件信息用于指示所述日期信息对应的日期发生的事件；
    所述装置还包括：
    第二接收模块，被配置为接收所述第三日历客户端发布的所述第三原始日历信息，所述第三日历客户端中登录的用户账号与所述第一用户账号关联；
    第二推送模块，被配置为向所述第一日历客户端推送所述第三原始日历信息。
  21. 根据权利要求19所述的装置，其特征在于，
    所述原始日历信息是所述第一日历客户端在所述第一日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到的，所述原始日历信息包括：日期信息和所述事件信息，所述事件信息用于指示所述日期信息对应的日期发生的事件。
  22. 根据权利要求19至21任一所述的装置，其特征在于，所述装置还包括：
    获取模块，被配置为获取与所述第一用户账号关联的所述第二用户账号。
  23. 根据权利要求22所述的装置，其特征在于，
    所述获取模块，被配置为：
    获取所述第一用户账号的订阅账号；
    获取订阅所述订阅账号的其他用户账号，所述其他用户账号不包括所述第一用户账号；
    将所述其他用户账号作为所述第二用户账号。
  24. 根据权利要求22所述的装置，其特征在于，
    所述获取模块，被配置为：
    获取订阅所述第一用户账号的用户账号；
    将所述订阅所述第一用户账号的用户账号作为所述第二用户账号。
  25. 根据权利要求22所述的装置，其特征在于，
    所述获取模块，被配置为：
    根据所述第一用户账号，查询预设的用户账号关联列表，所述用户账号关联列表记录了各个用户账号的关联关系；
    将从所述用户账号关联列表查询得到的与所述第一用户账号关联的用户账号作为所述第二用户账号。
  26. 一种日历信息管理装置，其特征在于，所述装置包括：
    显示模块，被配置为显示原始日历信息；
    第一接收模块，被配置为接收对所述原始日历信息的更新指令；
    修改模块，被配置为根据所述更新指令，对所述原始日历信息中所述更新指令指示的内容进行修改，得到共享日历信息；
    发布模块，被配置为向服务器发布所述共享日历信息，以使得所述服务器向第二日历客户端推送所述共享日历信息，所述第二日历客户端是第二用户账号登陆的日历客户端，第一日历客户端是第一用户账号登陆的日历客户端，所述第二用户账号与所述与第一用户账号关联。
  27. 根据权利要求26所述的装置，其特征在于，
    所述修改模块，被配置为：
    显示提示信息，所述提示信息用于提示用户对所述原始日历信息中所述更新指令指示的内容进行修改；
    在接收到所述用户触发的指示进行修改的确认指令时，对所述原始日历信息中所述更新指令指示的内容进行修改。
  28. 根据权利要求26或27所述的装置，其特征在于，所述原始日历信息包括日期信息和事件信息，所述事件信息用于指示所述日期信息对应的日期发生的事件，
    所述修改模块，被配置为：
    根据所述更新指令对所述日期信息和所述事件信息中的至少一种进行修改。
  29. 根据权利要求26至28任一所述的装置，其特征在于，所述装置还包括：
    第二接收模块，被配置为接收所述服务器推送的第三原始日历信息，所述第三原始日历信息是第三日历客户端在所述第三日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到并发布至所述服务器的，所述第三日历客户端中登录的用户账号与所述第一用户账号关联。
  30. 根据权利要求29所述的装置，其特征在于，所述装置还包括：
    更新模块，被配置为采用所述第三原始日历信息更新第一原始日历信息得到所述原始日历信息，所述第一原始日历信息是第一日历客户端在所述第一日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到的。
  31. 根据权利要求30所述的装置，其特征在于，
    所述更新模块，被配置为：
    采用所述第三原始日历信息替换所述第一原始日历信息得到所述原始日历信息。
  32. 根据权利要求30所述的装置，其特征在于，
    所述更新模块，被配置为：
    将所述第三原始日历信息和所述第一原始日历信息进行合并得到所述原始日历信息。
  33. 根据权利要求26至28任一所述的装置，其特征在于，所述装置还包括：
    添加模块，被配置为在所述第一日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到所述原始日历信息。
  34. 一种日历信息管理装置，其特征在于，所述装置包括：
    接收模块，被配置为接收服务器推送的共享日历信息，所述共享日历信息是所述服务 器接收到第一日历客户端发布的共享日历信息后，向第二日历客户端推送的，所述第二日历客户端是登陆第二用户账号的日历客户端，所述第一日历客户端是第一用户账号登陆的日历客户端，所述第二用户账号与所述与第一用户账号关联，所述共享日历信息是所述第一日历客户端对所述第一日历客户端显示的原始日历信息进行修改得到的；
    更新模块，被配置为采用所述共享日历信息更新第二原始日历信息，所述第二原始日历信息是所述第二日历客户端在所述第二日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到的。
  35. 根据权利要求34所述的装置，其特征在于，
    所述更新模块，被配置为：
    采用所述共享日历信息替换所述第二原始日历信息。
  36. 根据权利要求34所述的装置，其特征在于，
    所述更新模块，被配置为：
    将所述共享日历信息和所述第二原始日历信息进行合并。
  37. 一种日历信息管理装置，其特征在于，包括：
    处理器；
    用于存储所述处理器的可执行指令的存储器；
    其中，所述处理器被配置为：
    接收第一日历客户端发布的共享日历信息，所述共享日历信息是所述第一日历客户端对所述第一日历客户端显示的原始日历信息进行修改得到的；
    向第二日历客户端推送所述共享日历信息，以使得所述第二日历客户端采用所述共享日历信息更新第二原始日历信息，所述第二原始日历信息是所述第二日历客户端在所述第二日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到的，所述第二日历客户端是第二用户账号登陆的日历客户端，所述第一日历客户端是第一用户账号登陆的日历客户端，所述第二用户账号与所述与第一用户账号关联。
  38. 一种日历信息管理装置，其特征在于，包括：
    处理器；
    用于存储所述处理器的可执行指令的存储器；
    其中，所述处理器被配置为：
    显示原始日历信息；
    接收对所述原始日历信息的更新指令；
    根据所述更新指令，对所述原始日历信息中所述更新指令指示的内容进行修改，得到 共享日历信息；
    向服务器发布所述共享日历信息，以使得所述服务器向第二日历客户端推送所述共享日历信息，所述第二日历客户端是第二用户账号登陆的日历客户端，第一日历客户端是第一用户账号登陆的日历客户端，所述第二用户账号与所述与第一用户账号关联。
  39. 一种日历信息管理装置，其特征在于，包括：
    处理器；
    用于存储所述处理器的可执行指令的存储器；
    其中，所述处理器被配置为：
    接收服务器推送的共享日历信息，所述共享日历信息是所述服务器接收到第一日历客户端发布的共享日历信息后，向第二日历客户端推送的，所述第二日历客户端是登陆第二用户账号的日历客户端，所述第一日历客户端是第一用户账号登陆的日历客户端，所述第二用户账号与所述与第一用户账号关联，所述共享日历信息是所述第一日历客户端对所述第一日历客户端显示的原始日历信息进行修改得到的；
    采用所述共享日历信息更新第二原始日历信息，所述第二原始日历信息是所述第二日历客户端在所述第二日历客户端显示的日历界面的指定日期页面中添加对应的事件信息得到的。
  40. 一种日历信息管理系统，其特征在于，所述系统包括：服务器、第一日历客户端和第二日历客户端，
    所述服务器包括权利要求19至25任一所述的日历信息管理装置；
    所述第一日历客户端包括权利要求26至33任一所述的日历信息管理装置；
    所述第二日历客户端包括权利要求34至36任一所述的日历信息管理装置。
  41. 一种日历信息管理系统，其特征在于，所述系统包括：服务器、第一日历客户端和第二日历客户端，
    所述服务器包括权利要求37所述的日历信息管理装置；
    所述第一日历客户端包括权利要求38所述的日历信息管理装置；
    所述第二日历客户端包括权利要求39所述的日历信息管理装置。
PCT/CN2015/099734 2015-09-28 2015-12-30 日历信息管理方法、装置及系统 WO2017054359A1 (zh)

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)

* Cited by examiner, † Cited by third party
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)

* Cited by examiner, † Cited by third party
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)

* Cited by examiner, † Cited by third party
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 小米科技有限责任公司 日历信息推送方法、装置及系统

Patent Citations (3)

* Cited by examiner, † Cited by third party
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