WO2023015978A1 - 日程更新方法和设备 - Google Patents

日程更新方法和设备 Download PDF

Info

Publication number
WO2023015978A1
WO2023015978A1 PCT/CN2022/091108 CN2022091108W WO2023015978A1 WO 2023015978 A1 WO2023015978 A1 WO 2023015978A1 CN 2022091108 W CN2022091108 W CN 2022091108W WO 2023015978 A1 WO2023015978 A1 WO 2023015978A1
Authority
WO
WIPO (PCT)
Prior art keywords
schedule
field
schedule information
change
information
Prior art date
Application number
PCT/CN2022/091108
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 荣耀终端有限公司
Publication of WO2023015978A1 publication Critical patent/WO2023015978A1/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
    • G06Q10/109—Time management, e.g. calendars, reminders, meetings or time accounting
    • G06Q10/1093—Calendar-based scheduling for persons or groups
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F40/00—Handling natural language data
    • G06F40/10—Text processing
    • G06F40/103—Formatting, i.e. changing of presentation of documents
    • G06F40/117—Tagging; Marking up; Designating a block; Setting of attributes

Definitions

  • the present application relates to the technical field of schedule update, in particular to a schedule update method and device.
  • the user often encounters a situation where the schedule is changed, for example, the time or the location of the meeting is temporarily changed due to meeting conflicts.
  • the user is not given enough reminders of the change of the schedule, so that the user does not know the change of the schedule.
  • Embodiments of the present application provide a method and device for updating a schedule, capable of displaying a label corresponding to an updated schedule field in a schedule of a calendar application, so as to prompt a user that a schedule is changed.
  • the technical solution provides a method for updating a schedule, which includes:
  • the second schedule information is updated to the first schedule of the calendar application, and at least one label is displayed in the updated first schedule.
  • displaying at least one label in the updated first schedule includes:
  • At least one label is displayed in the updated first schedule.
  • the schedule field includes: a time field, a location field, a subject field, or a participant field.
  • the tag includes: time change, location change, theme change, or participant change.
  • the correspondence between the schedule field and the label includes: the time field corresponds to the time change, the location field corresponds to the location change Correspondingly, the subject field corresponds to the subject change, and the participant field corresponds to the participant change.
  • the tags are sorted in descending order of priority: the time change, the location change, the theme change, and the participant change .
  • the first schedule information and the second schedule information come from an email client.
  • the first schedule information and the second schedule information come from an email containing a schedule received by the email client.
  • the first schedule information and the second schedule information come from a third-party application.
  • the schedule identifier includes an ID of schedule information.
  • the technical solution provides a schedule update device, including:
  • a transceiver unit configured to receive first schedule information and second schedule information, the second schedule information having the same schedule identifier as the first schedule information, and the first schedule information and the second schedule information having at least a different schedule field;
  • a display unit configured to display a first schedule in a calendar application according to the first schedule information
  • An updating unit configured to update the second schedule information to the first schedule of the calendar application according to the at least one different schedule field
  • a prompting unit configured to display at least one label in the updated first schedule.
  • the prompting unit is specifically configured to, after updating, according to the at least one different schedule field and the correspondence between the schedule field and the label At least one label is displayed in the first schedule of .
  • the schedule field includes: a time field, a location field, a subject field, or a participant field.
  • the tag includes: time change, location change, theme change, or participant change.
  • the correspondence between the schedule field and the label includes: the time field corresponds to the time change, the location field corresponds to the location change Correspondingly, the subject field corresponds to the subject change, and the participant field corresponds to the participant change.
  • the tags are sorted in descending order of priority: the time change, the location change, the theme change, and the participant change .
  • the first schedule information and the second schedule information come from an email client.
  • the first schedule information and the second schedule information come from an email containing a schedule received by the email client.
  • the first schedule information and the second schedule information come from a third-party application.
  • the schedule identifier includes an ID of schedule information.
  • the technical solution provides an electronic device, including: one or more processors; memory; and one or more computer programs, wherein the one or more computer programs are stored in the memory,
  • the one or more computer programs include instructions that, when executed by the device, cause the device to perform the following steps:
  • the second schedule information is updated to the first schedule of the calendar application, and at least one label is displayed in the updated first schedule.
  • the electronic device when the instruction is executed by the electronic device, the electronic device is made to perform the following steps:
  • At least one label is displayed in the updated first schedule.
  • the schedule field includes: a time field, a location field, a subject field, or a participant field.
  • the tag includes: time change, location change, theme change, or participant change.
  • the correspondence between the schedule field and the tag includes: the time field corresponds to the time change, the location field corresponds to the location change Correspondingly, the subject field corresponds to the subject change, and the participant field corresponds to the participant change.
  • the tags are sorted in descending order of priority: the time change, the location change, the theme change, and the participant change .
  • the first schedule information and the second schedule information come from an email client.
  • the first schedule information and the second schedule information come from an email containing a schedule received by the email client.
  • the first schedule information and the second schedule information come from a third-party application.
  • the schedule identifier includes the ID of the schedule information
  • the technical solution provides a device for updating a schedule
  • the device includes a storage medium and a central processing unit
  • the storage medium may be a non-volatile storage medium
  • a computer executable program is stored in the storage medium
  • the central processing unit is connected to the non-volatile storage medium, and executes the computer-executable program to implement the first aspect or the method in any possible implementation manner of the first aspect.
  • the technical solution provides a chip, the chip includes a processor and a data interface, and the processor reads the instructions stored in the memory through the data interface, and executes any of the first aspect or the first aspect.
  • the chip includes a processor and a data interface, and the processor reads the instructions stored in the memory through the data interface, and executes any of the first aspect or the first aspect.
  • the chip may further include a memory, the memory stores instructions, the processor is configured to execute the instructions stored in the memory, and when the instructions are executed, the The processor is configured to execute the first aspect or the method in any possible implementation manner of the first aspect.
  • the technical solution provides a computer-readable storage medium, where the computer-readable medium stores program code for device execution, and the program code includes any one of the first aspect or the first aspect.
  • FIG. 1 is a schematic diagram of a main interface of a calendar application
  • FIG. 2 is a schematic diagram of a new schedule interface of a calendar application
  • FIG. 3 is another schematic diagram of a new schedule interface of a calendar application
  • Fig. 4 is another schematic diagram of the main interface of the calendar application.
  • FIG. 5 is a schematic diagram of a pop-up selection box on the main interface of the calendar application
  • FIG. 6 is a schematic diagram of an interface for adding an account in a calendar application
  • FIG. 7 is another schematic diagram of an interface for adding an account in a calendar application
  • Fig. 8 is a kind of system frame diagram of automatically adding schedule
  • Fig. 9 is another schematic diagram of the main interface of the calendar application.
  • FIG. 10 is a system architecture for schedule update provided by an embodiment of the present application.
  • Fig. 11 is a schematic diagram of the main interface of the calendar application provided by the embodiment of the present application.
  • Fig. 12 is a schematic structural diagram of an electronic device provided by an embodiment of the present application.
  • FIG. 13 is a software structural block diagram of an electronic device provided by an embodiment of the present application.
  • FIG. 14 is a flow chart of a method for updating a schedule provided by an embodiment of the present application.
  • FIG. 15 is a flow chart of another method for updating a schedule provided by an embodiment of the present application.
  • Fig. 16 is a schematic structural diagram of a device for updating a schedule provided by an embodiment of the present application.
  • the schedule update method provided by the embodiment of the present application is applied to the scenario of schedule synchronization in electronic devices.
  • the label corresponding to the schedule field can be displayed in the schedule of the calendar application according to the changed schedule field to prompt the user Schedule changes.
  • the ways of adding schedule include manual adding and automatic adding.
  • Manual addition means that the user manually adds an event in the calendar application.
  • the user opens the calendar application in the mobile phone, and the main interface of the calendar application is displayed on the screen, as shown in Figure 1, the main interface of the calendar application displays today's date as August 6, 2021, and displays today There is no schedule, and an add button a is displayed at the lower right corner of the screen, and the add button a is used to add a new schedule.
  • the add button a as shown in Figure 2
  • the screen displays the title, location, time, description, etc. of the newly created schedule, and the user can edit the content of the new schedule on this interface.
  • the title of the new schedule is "Smart Conference", the location is “Meijiang Convention and Exhibition Center”, the start time is "09:00, August 7", and it is set to remind 10 minutes before and not to repeat .
  • click the finish button b in the upper right corner of the screen to complete the editing.
  • the screen of the mobile phone returns to the main interface of the calendar application.
  • the user selects August 7, 2021 in the calendar, as shown in Figure 4.
  • the newly created schedule is displayed on the screen, and the displayed content includes the time, title and location of the schedule.
  • the automatic adding means that the electronic device automatically adds the schedule obtained from the third-party application or email client to the schedule of the calendar application.
  • the mail client belongs to the system application of the electronic device.
  • the automatically added schedule comes from a schedule added by a user in a mail client or a third-party application, or from an email received by the email client, and the email includes schedule information.
  • the user needs to add the email account to the account management of the calendar application in advance to realize the function of automatically adding schedules.
  • the electronic device as a mobile phone as an example, as shown in Figure 5, after the user clicks the button c in the upper right corner of the main interface of the calendar application, a selection box pops up on the screen, and the selection box includes "jump to a specified date", " Calendar Account Management", "Subscription Management” and "Settings” 4 options.
  • the email account "123456789@qq.com” will be displayed on the calendar account management interface, and the calendar application has the ability to access the " 123456789@qq.com” email account permissions.
  • the user adds the email account to the account management of the calendar application, and the calendar application obtains the permission to access the email account; at the same time, the user logs in the email account in the email client in the electronic device.
  • the mail client or third-party application in the electronic device synchronizes the schedule to the calendar storage through the schedule synchronization module. After the calendar storage stores the schedule through the schedule insertion module, the schedule is sent to the calendar application. After receiving the schedule, the schedule receiver of the calendar application sends the schedule to the schedule card module, the schedule view module and the schedule reminder module respectively.
  • the schedule card module is used to display the schedule card corresponding to the schedule according to the schedule information; the schedule view module is used to display the view in the schedule card corresponding to the schedule according to the schedule information; the schedule reminder module is used to execute the schedule according to the schedule information Reminder action.
  • the user logs in the email account of "123456789@qq.com” in the email client of the mobile phone.
  • the email account of "123456789@qq.com” receives an email containing a schedule
  • the schedule is in August 2021 At 9:00 am on the 9th, the venue is the water park, the theme is team building, and the reminder time is 30 minutes in advance.
  • the calendar application in the mobile phone can obtain the schedule of the email account "123456789@qq.com” in the email client, and automatically add the obtained schedule to the calendar application, and the calendar application will display the obtained schedule, as shown in Figure 9 shown.
  • Schedule synchronization refers to electronic devices synchronizing schedules in email clients or third-party applications with schedules in calendar applications.
  • a schedule is changed, for example, a time or a location of a meeting is temporarily changed due to meeting conflicts.
  • the mail client or third-party application directly sends the changed schedule to the calendar application, and the calendar application will display the changed schedule as a new schedule without prompting The user's schedule has changed.
  • an embodiment of the present application provides a system architecture for updating a schedule.
  • the system architecture includes email client or third-party application, calendar storage and calendar application.
  • the email client or third-party application includes a schedule synchronization module.
  • the calendar storage includes a schedule insertion module, a schedule modification module, a schedule deletion module, a schedule change calculation module and a schedule change notification module.
  • the calendar application includes a schedule change receiver, a schedule card module, a schedule view module and a schedule reminder module.
  • the schedule synchronization module is used to send the schedule information in the mail client or the third-party application to the schedule identification module stored in the calendar.
  • the schedule identification module is used to identify the schedule identifier of the schedule information, and judge whether the schedule information corresponding to the schedule identifier is stored in the calendar storage, and if it is judged that the schedule information corresponding to the schedule identifier is not stored in the calendar storage, the schedule information Send to the schedule insertion module; otherwise, send the schedule information to the schedule modification module.
  • the schedule identifier includes the ID of the schedule information.
  • the schedule insertion module is used to store the schedule information and send the schedule information to the schedule receiver of the calendar application.
  • the schedule receiver is used to send the schedule information to the schedule card module, schedule view module and schedule reminder module respectively.
  • the schedule card module is used to display the corresponding schedule card according to the schedule information;
  • the schedule view module is used to display the corresponding view in the schedule card according to the schedule information;
  • the schedule reminder module is used to perform reminder operations according to the schedule information.
  • the schedule modification module is used to modify the stored schedule information according to the received schedule information; and send the pre-modified schedule information and the modified schedule information to the schedule change calculation module. It should be noted that there is at least one different schedule field between the schedule information before modification and the schedule information after modification.
  • the schedule change calculation module is configured to determine at least one different schedule field according to the unmodified schedule information and the revised schedule information, and send at least one different schedule field in the revised schedule information to the schedule change notification module. Specifically, the schedule change calculation module determines at least one different schedule field in the revised schedule information by comparing the fields of the schedule information before modification with the fields of the modified schedule information.
  • the schedule fields include: time field, location field, subject field or participant field.
  • a schedule change notification module configured to generate a schedule change notification according to at least one different schedule field in the modified schedule information and a schedule identifier of the schedule information, and send the schedule change notification to the schedule receiver of the calendar application.
  • the schedule receiver is also used to obtain at least one different schedule field and the schedule identifier of the schedule information in the revised schedule information by parsing the schedule change notification, and send at least one different schedule field and schedule identifier to the schedule card module respectively , schedule view module and schedule reminder module.
  • the schedule card module is also used to find the schedule card corresponding to the schedule ID in the notification bar according to the schedule ID, update the corresponding information according to at least one different schedule field and display at least one label corresponding to at least one schedule field.
  • Tags include: time change, location change, theme change, or participant change. The tags are sorted in descending order of priority: time change, location change, theme change, and participant change.
  • the schedule view module is further configured to display a corresponding view in the schedule card corresponding to the updated first schedule according to at least one schedule field and the schedule identifier.
  • the schedule reminder module is further configured to perform a reminder operation according to at least one schedule field and a schedule identifier.
  • the schedule reminder module changes the reminder time according to the time field, and executes the reminder operation according to the changed reminder time.
  • the above-mentioned "123456789@qq.com” email account receives another email containing a schedule.
  • the schedule ID of the schedule is the same as the schedule ID of the above schedule, but the time of the schedule is 2021 At 10:00 am on August 9, 2019, the venue, theme and reminder time are the same as the above schedule.
  • the calendar application in the mobile phone obtains the schedule information of the schedule in the email account "123456789@qq.com” in the email client, compares it with the schedule information of the above schedule, determines that the time field has changed, and updates the above schedule in the calendar time field, and display the time change label in the schedule card, as shown in Figure 11.
  • the electronic device can be a mobile phone, a tablet computer, a wearable device, a vehicle-mounted device, an augmented reality (augmented reality, AR)/virtual reality (virtual reality, VR) device, a notebook computer, an ultra-mobile personal computer (ultra-mobile personal computer) , UMPC), netbook, personal digital assistant (personal digital assistant, PDA) and other electronic equipment, the embodiment of the present application does not make any restrictions on the specific type of electronic equipment.
  • FIG. 12 shows a schematic structural diagram of an electronic device 100 provided by an embodiment of the present application.
  • the electronic device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (universal serial bus, USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, and an antenna 2 , mobile communication module 150, wireless communication module 160, audio module 170, speaker 170A, receiver 170B, microphone 170C, earphone jack 170D, sensor module 180, button 190, motor 191, indicator 192, camera 193, display screen 194, and A subscriber identification module (subscriber identification module, SIM) card interface 195 and the like.
  • SIM subscriber identification module
  • the sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, bone conduction sensor 180M, etc.
  • the structure illustrated in the embodiment of the present application does not constitute a specific limitation on the electronic device 100 .
  • the electronic device 100 may include more or fewer components than shown in the figure, or combine certain components, or separate certain components, or arrange different components.
  • the illustrated components can be realized in hardware, software or a combination of software and hardware.
  • the processor 110 may include one or more processing units, for example: the processor 110 may include an application processor (application processor, AP), a modem processor, a graphics processing unit (graphics processing unit, GPU), an image signal processor (image signal processor, ISP), controller, video codec, digital signal processor (digital signal processor, DSP), baseband processor, and/or neural network processor (neural-network processing unit, NPU), etc. Wherein, different processing units may be independent devices, or may be integrated in one or more processors.
  • application processor application processor, AP
  • modem processor graphics processing unit
  • GPU graphics processing unit
  • image signal processor image signal processor
  • ISP image signal processor
  • controller video codec
  • digital signal processor digital signal processor
  • baseband processor baseband processor
  • neural network processor neural-network processing unit
  • the controller may be the nerve center and command center of the electronic device 100 .
  • the controller can generate an operation control signal according to the instruction opcode and timing signal, and complete the control of fetching and executing the instruction.
  • a memory may also be provided in the processor 110 for storing instructions and data.
  • the memory in processor 110 is a cache memory.
  • the memory may hold instructions or data that the processor 110 has just used or recycled. If the processor 110 needs to use the instruction or data again, it can be called directly from the memory. Repeated access is avoided, and the waiting time of the processor 110 is reduced, thus improving the efficiency of the system.
  • processor 110 may include one or more interfaces.
  • the interface may include an integrated circuit (inter-integrated circuit, I2C) interface, an integrated circuit built-in audio (inter-integrated circuit sound, I2S) interface, a pulse code modulation (pulse code modulation, PCM) interface, a universal asynchronous transmitter (universal asynchronous receiver/transmitter, UART) interface, mobile industry processor interface (mobile industry processor interface, MIPI), general-purpose input and output (general-purpose input/output, GPIO) interface, subscriber identity module (subscriber identity module, SIM) interface, and /or universal serial bus (universal serial bus, USB) interface, etc.
  • I2C integrated circuit
  • I2S integrated circuit built-in audio
  • PCM pulse code modulation
  • PCM pulse code modulation
  • UART universal asynchronous transmitter
  • MIPI mobile industry processor interface
  • GPIO general-purpose input and output
  • subscriber identity module subscriber identity module
  • SIM subscriber identity module
  • USB universal serial bus
  • the interface connection relationship between the modules shown in the embodiment of the present application is only a schematic illustration, and does not constitute a structural limitation of the electronic device 100 .
  • the electronic device 100 may also adopt different interface connection manners in the foregoing embodiments, or a combination of multiple interface connection manners.
  • the internal memory 121 may be used to store computer-executable program codes including instructions.
  • the internal memory 121 may include an area for storing programs and an area for storing data.
  • the stored program area can store an operating system, an application program required by at least one function (such as a schedule update function, etc.), and the like.
  • the data storage area can store data created during use of the electronic device 100 (such as image data, etc.).
  • the internal memory 121 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk storage device, flash memory device, universal flash storage (universal flash storage, UFS) and the like.
  • the processor 110 executes various functional applications and data processing of the electronic device 100 by executing instructions stored in the internal memory 121 and/or instructions stored in a memory provided in the processor.
  • the software system of the electronic device 100 may adopt a layered architecture, an event-driven architecture, a micro-kernel architecture, a micro-service architecture, or a cloud architecture.
  • the software structure of the electronic device 100 is exemplarily described by taking an Android system with a layered architecture as an example.
  • FIG. 13 is a software structural block diagram of the electronic device 100 provided by the embodiment of the present application.
  • the layered architecture divides the software into several layers, and each layer has a clear role and division of labor. Layers communicate through software interfaces.
  • the Android system is divided into four layers, which are respectively the application program layer, the application program framework layer, the Android runtime (Android runtime) and the system library, and the kernel layer from top to bottom.
  • the application layer can consist of a series of application packages.
  • the application package may include application programs such as camera, gallery, calendar, call, map, navigation, WLAN, Bluetooth, music, video, and short message.
  • application programs such as camera, gallery, calendar, call, map, navigation, WLAN, Bluetooth, music, video, and short message.
  • the application framework layer provides an application programming interface (application programming interface, API) and a programming framework for applications in the application layer.
  • the application framework layer includes some predefined functions.
  • the application framework layer can include window manager, content provider, view system, phone manager, resource manager, notification manager, etc.
  • a window manager is used to manage window programs.
  • the window manager can get the size of the display screen, determine whether there is a status bar, lock the screen, capture the screen, etc.
  • Content providers are used to store and retrieve data and make it accessible to applications.
  • the data may include video, images, etc.
  • the view system includes visual controls, such as controls for displaying text, controls for displaying pictures, and so on.
  • the view system can be used to build applications.
  • a display interface can consist of one or more views.
  • a display interface including a text message notification icon may include a view for displaying text and a view for displaying pictures.
  • the phone manager is used to provide communication functions of the electronic device 100 . For example, the management of call status (including connected, hung up, etc.).
  • the resource manager provides various resources for the application, such as localized strings, icons, pictures, layout files, video files, and so on.
  • the notification manager enables the application to display notification information in the status bar, which can be used to convey notification-type messages, and can automatically disappear after a short stay without user interaction.
  • the notification manager is used to notify the download completion, message reminder, etc.
  • the notification manager can also be a notification that appears in the status bar at the top of the system in the form of a chart or scroll bar text, such as a notification of an application running in the background, or a notification that appears on the screen in the form of a dialog window.
  • prompting text information in the status bar issuing a prompt sound, vibrating the electronic device, and flashing the indicator light, etc.
  • the Android Runtime includes core library and virtual machine. The Android runtime is responsible for the scheduling and management of the Android system.
  • the core library consists of two parts: one part is the function function that the java language needs to call, and the other part is the core library of Android.
  • the application layer and the application framework layer run in virtual machines.
  • the virtual machine executes the java files of the application program layer and the application program framework layer as binary files.
  • the virtual machine is used to perform functions such as object life cycle management, stack management, thread management, security and exception management, and garbage collection.
  • a system library can include multiple function modules. For example: surface manager (surface manager), media library (Media Libraries), 3D graphics processing library (eg: OpenGL ES), 2D graphics engine (eg: SGL), etc.
  • the kernel layer is the layer between hardware and software.
  • the kernel layer includes at least a display driver, a camera driver, an audio driver, and a sensor driver.
  • a method for updating a schedule provided in the embodiment of the present application includes:
  • the first schedule information comes from the email client.
  • the user creates a schedule in the email client, or the email client receives an email containing the schedule sent by the email server.
  • the mailbox server includes an Exchange server.
  • the mail client sends the schedule information of the schedule to the calendar storage through the schedule synchronization module; the calendar storage recognizes the schedule identifier of the schedule information through the schedule identification module, and judges that the schedule is not stored in the calendar storage.
  • the identified schedule information send the schedule information to the schedule insertion module; the schedule insertion module stores the schedule in the calendar storage, and sends the schedule information to the schedule receiver of the calendar application; the schedule receiver sends the schedule information to the schedule card module respectively , schedule view module and schedule reminder module.
  • the schedule card module displays the corresponding schedule card according to the schedule information; the schedule view module displays the corresponding view in the schedule card according to the schedule information; the schedule reminder module performs reminder operations according to the schedule information.
  • the first schedule information and the second schedule information come from a third-party application.
  • a user creates a schedule in a third-party application.
  • the third-party application sends the schedule information of the schedule to the calendar storage through the schedule synchronization module; the calendar storage recognizes the schedule identifier of the schedule information through the schedule identification module, and judges that there is no information related to the schedule stored in the calendar storage.
  • the identified schedule information send the schedule information to the schedule insertion module; the schedule insertion module stores the schedule information in the calendar storage, and sends the schedule information to the schedule receiver of the calendar application; the schedule receiver sends the schedule information to the schedule card respectively module, schedule view module and schedule reminder module.
  • the schedule card module displays the corresponding schedule card according to the schedule information; the schedule view module displays the corresponding view in the schedule card according to the schedule information; the schedule reminder module performs reminder operations according to the schedule information.
  • the first schedule information includes a plurality of schedule fields, and the schedule fields include: a time field, a location field, a subject field, or a participant field.
  • the second schedule information also includes a plurality of schedule fields, and the schedule fields include: time field, location field, subject field or participant field.
  • the second schedule information has the same schedule identifier as the first schedule information, indicating that the second schedule information is generated based on the first schedule information.
  • the second schedule information is generated by changing one or any combination of the time field, location field, subject field and participant field of the first schedule information.
  • the schedule identifier includes the ID of the schedule information.
  • the mail client or the third-party application sends the second schedule information to the schedule identification module stored in the calendar through the schedule synchronization module.
  • the schedule identification module identifies the schedule identifier of the second schedule information through the schedule identification module, and judges that the first schedule information with the schedule identifier has been stored in the calendar storage, and sends the second schedule information to the schedule modification module.
  • the schedule modifying module modifies the stored first schedule information according to the received second schedule information; and sends the first schedule information and the second schedule information to the schedule change calculation module.
  • the schedule change calculation module determines at least one different schedule field according to the first schedule information and the second schedule information, and sends the at least one different schedule field in the second schedule information to the schedule change notification module.
  • the schedule change calculation module determines at least one different schedule field in the revised schedule information by comparing the schedule fields of the first schedule information and the second schedule information.
  • the schedule fields include: time field, location field, subject field or participant field.
  • the schedule change notification module generates a schedule change notification according to at least one different schedule field and a schedule identifier in the second schedule information, and sends the schedule change notification to the schedule receiver of the calendar application.
  • the second schedule information may have at least one different schedule field.
  • displaying at least one label in the updated first schedule includes: displaying at least one label in the updated first schedule according to at least one different schedule field and the corresponding relationship between the schedule field and the label .
  • the label includes: time change, location change, theme change or participant change.
  • the corresponding relationship between the schedule field and the label includes: the time field corresponds to the time change, the location field corresponds to the location change, the subject field corresponds to the theme change, and the participant field corresponds to the participant change.
  • the tags are sorted in descending order of priority: time change, location change, theme change, and participant change.
  • the schedule receiver obtains at least one different schedule field and a schedule identifier in the second schedule information by analyzing the schedule change notification, and separates the at least one different schedule field and the schedule identifier Send to Agenda Card Module, Agenda View Module and Agenda Reminder Module.
  • the schedule card module finds the schedule card corresponding to the schedule ID in the notification bar according to the schedule ID, updates the corresponding information according to at least one different schedule field and displays at least one label corresponding to the at least one schedule field.
  • the schedule view module displays a corresponding view in the schedule card corresponding to the updated first schedule according to at least one schedule field and the schedule identifier.
  • the schedule reminder module executes a reminder operation according to at least one schedule field and a schedule identifier.
  • the first schedule information is received, and the first schedule is displayed in the calendar application according to the first schedule information; the second schedule information is received, and the information of the second schedule and the first schedule information
  • the schedule identifiers are the same, and the first schedule information and the second schedule information have at least one different schedule field; according to the at least one different schedule field, the second schedule information is updated to the first schedule of the calendar application, and the updated Display at least one label in the first schedule.
  • a label corresponding to the updated schedule field can be displayed in the schedule of the calendar application, so as to prompt the user that the schedule is changed.
  • another method for reminding a schedule change provided by the embodiment of the present application is applied to an electronic device, and the electronic device includes a mail client or a third-party application, a calendar storage, and a calendar application; the method includes:
  • An email client or a third-party application sends first schedule information to a calendar store.
  • the email client or the third-party application sends the schedule information of the first schedule to the calendar storage through the schedule synchronization module.
  • the first schedule information includes a plurality of schedule fields, and the schedule fields include: a time field, a location field, a subject field, or a participant field.
  • the calendar storage stores the first schedule information in the calendar storage.
  • the calendar store identifies the schedule identifier of the first schedule information through the schedule identification module, and judges that no schedule information with the schedule identifier is stored in the calendar storage, and sends the first schedule information to To the schedule insertion module; the schedule insertion module stores the first schedule information into the calendar storage.
  • the calendar store sends the first schedule information to the calendar application.
  • the schedule insertion module sends the first schedule information to the schedule receiver of the calendar application.
  • the calendar application displays the first schedule in the calendar application according to the first schedule information.
  • the schedule receiver sends the first schedule information to the schedule card module, the schedule view module and the schedule reminder module respectively.
  • the schedule card module displays a corresponding schedule card according to the first schedule information;
  • the schedule view module displays a corresponding view in the schedule card according to the first schedule information;
  • the schedule reminder module executes a reminder operation according to the first schedule information.
  • the mail client or the third-party application sends the second schedule information to the calendar storage, where the second schedule information is the same as the schedule identifier of the first schedule information.
  • the second schedule information also includes a plurality of schedule fields, and the schedule fields include: time field, location field, subject field or participant field.
  • the second schedule information has the same schedule identifier as the first schedule information, indicating that the second schedule information is generated based on the first schedule information.
  • the second schedule information is generated by changing one or any combination of the time field, location field, subject field and participant field of the first schedule information.
  • the schedule identifier includes the ID of the schedule information.
  • the mail client or the third-party application sends the second schedule information to the schedule identification module stored in the calendar through the schedule synchronization module.
  • the calendar storage modifies the first schedule information according to the second schedule information, and determines at least one different schedule field in the second schedule information according to the first schedule information and the second schedule information.
  • the schedule identification module identifies the schedule identifier of the second schedule information through the schedule identification module, and judges that the first schedule information corresponding to the schedule identifier has been stored in the calendar storage, and stores the second schedule information.
  • the schedule information is sent to the schedule modification module.
  • the schedule modification module modifies the stored first schedule information according to the received second schedule information; and sends the first schedule information and the second schedule information to the schedule change calculation module.
  • the schedule change calculation module determines at least one different schedule field according to the first schedule information and the second schedule information, and sends at least one different schedule field in the second schedule information to the schedule change notification module. Specifically, the schedule change calculation module determines at least one different schedule field in the revised schedule information by comparing the schedule fields of the first schedule information and the second schedule information.
  • the schedule fields include: time field, location field, subject field or participant field.
  • the calendar store sends at least one different schedule field and schedule identifier to the calendar application.
  • the schedule change notification module generates a schedule change notification according to at least one different schedule field and a schedule identifier in the second schedule information, and sends the schedule change notification to the schedule receiver of the calendar application .
  • the calendar application updates the second schedule information to the first schedule of the calendar application according to at least one different schedule field, and displays at least one label in the updated first schedule.
  • the second schedule information may have at least one different schedule field.
  • displaying at least one label in the updated first schedule includes: displaying at least one label in the updated first schedule according to at least one different schedule field and the corresponding relationship between the schedule field and the label .
  • the label includes: time change, location change, theme change or participant change.
  • the corresponding relationship between the schedule field and the label includes: the time field corresponds to the time change, the location field corresponds to the location change, the subject field corresponds to the theme change, and the participant field corresponds to the participant change.
  • the tags are sorted in descending order of priority: time change, location change, theme change, and participant change.
  • the schedule receiver obtains at least one different schedule field and a schedule identifier in the second schedule information by analyzing the schedule change notification, and separates the at least one different schedule field and the schedule identifier Send to Agenda Card Module, Agenda View Module and Agenda Reminder Module.
  • the schedule card module finds the schedule card corresponding to the schedule ID in the notification bar according to the schedule ID, updates the corresponding information according to at least one different schedule field and displays at least one label corresponding to the at least one schedule field.
  • the schedule view module displays a corresponding view in the schedule card corresponding to the updated first schedule according to at least one schedule field and the schedule identifier.
  • the schedule reminder module executes a reminder operation according to at least one schedule field and a schedule identifier.
  • the functional modules of the electronic device may be divided according to the above method examples.
  • each functional module may be divided corresponding to each function, or two or more functions may be integrated into one processing module.
  • the above integrated modules may be implemented in the form of hardware. It should be noted that the division of modules in this embodiment is schematic, and is only a logical function division, and there may be other division methods in actual implementation.
  • FIG. 16 shows a possible composition diagram of the schedule update device involved in the above embodiment.
  • the schedule update device 300 may include: Unit 301, display unit 302, update unit 303 and prompt unit 304, wherein:
  • a transceiver unit 301 configured to receive first schedule information and second schedule information, the second schedule information has the same schedule identifier as the first schedule information, and the first schedule information and the second schedule information exist at least one different schedule field;
  • a display unit 302 configured to display a first schedule in a calendar application according to the first schedule information
  • An updating unit 303 configured to update the second schedule information to the first schedule of the calendar application according to the at least one different schedule field.
  • a prompting unit 304 configured to display at least one label in the updated first schedule.
  • the prompting unit 304 is specifically configured to display in the updated first schedule according to the at least one different schedule field and the corresponding relationship between the schedule field and the label At least one label.
  • the schedule field includes: a time field, a location field, a subject field, or a participant field.
  • the label includes: time change, location change, theme change, or participant change.
  • the correspondence between the schedule field and the label includes: the time field corresponds to the time change, the location field corresponds to the location change, and the subject field and The subject change corresponds, and the participant field corresponds to the participant change.
  • the tags are sorted in descending order of priority: time change, location change, theme change, and participant change.
  • the first schedule information and the second schedule information are from an email client.
  • the first schedule information and the second schedule information are from an email containing a schedule received by the email client.
  • the first schedule information and the second schedule information come from a third-party application.
  • the schedule identifier includes an ID of schedule information.
  • the electronic devices here are embodied in the form of functional units.
  • the term "unit” here may be implemented in the form of software and/or hardware, which is not specifically limited.
  • a “unit” may be a software program, a hardware circuit or a combination of both to realize the above functions.
  • the hardware circuitry may include application specific integrated circuits (ASICs), electronic circuits, processors (such as shared processors, dedicated processors, or group processors) for executing one or more software or firmware programs. etc.) and memory, incorporating logic, and/or other suitable components to support the described functionality.
  • ASICs application specific integrated circuits
  • processors such as shared processors, dedicated processors, or group processors
  • memory incorporating logic, and/or other suitable components to support the described functionality.
  • the present application also provides a schedule update device, the device includes a storage medium and a central processing unit, the storage medium may be a non-volatile storage medium, a computer executable program is stored in the storage medium, and the central processing unit The device is connected to the non-volatile storage medium, and executes the computer-executable program to implement the above method for updating the schedule.
  • the present application also provides a computer-readable storage medium, where instructions are stored in the computer-readable storage medium, and when the instructions are run on a computer, the computer is made to execute each step of the schedule updating method of the present application.
  • the present application also provides a computer program product containing instructions.
  • the computer program product is run on a computer or any at least one processor, the computer is made to execute each step of the schedule updating method of the present application.
  • the present application also provides a chip, including a processor and a data interface, and the processor reads instructions stored in the memory through the data interface to execute corresponding operations and/or processes performed by the schedule updating method provided in the present application.
  • the chip further includes a memory, the memory is connected to the processor through a circuit or wires, and the processor is used to read and execute the computer program in the memory.
  • the chip further includes a communication interface, and the processor is connected to the communication interface.
  • the communication interface is used to receive data and/or information to be processed, and the processor acquires the data and/or information from the communication interface and processes the data and/or information.
  • the communication interface may be an input-output interface.
  • the memory may be read-only memory (ROM), other types of static storage devices that can store static information and instructions, random access memory (random access memory, RAM), or other types of memory that can store information and instructions
  • ROM read-only memory
  • RAM random access memory
  • a dynamic storage device can also be an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage ( Including Compact Disc, Laser Disc, Optical Disc, Digital Versatile Disc, Blu-ray Disc, etc.), magnetic disk storage medium or other magnetic storage devices, or can be used to carry or store desired program code in the form of instructions or data structures and can Any other media accessed by a computer, etc.
  • EEPROM electrically erasable programmable read-only memory
  • CD-ROM compact disc read-only memory
  • CD-ROM compact disc read-only memory
  • optical disc storage Including Compact Disc, Laser Disc, Optical Disc, Digital Versatile Disc,
  • At least one of a, b, and c may represent: a, b, c, a-b, a-c, b-c, or a-b-c, wherein a, b, and c may be single or multiple.
  • any function is realized in the form of a software function unit and sold or used as an independent product, it can be stored in a computer-readable storage medium.
  • the technical solution of the present application is essentially or the part that contributes to the prior art or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (read-only memory, ROM), random access memory (random access memory, RAM), magnetic disk or optical disc and other media that can store program codes. .

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Human Resources & Organizations (AREA)
  • Theoretical Computer Science (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Strategic Management (AREA)
  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • Tourism & Hospitality (AREA)
  • Health & Medical Sciences (AREA)
  • Operations Research (AREA)
  • Marketing (AREA)
  • General Business, Economics & Management (AREA)
  • Economics (AREA)
  • Data Mining & Analysis (AREA)
  • Quality & Reliability (AREA)
  • Artificial Intelligence (AREA)
  • Audiology, Speech & Language Pathology (AREA)
  • Computational Linguistics (AREA)
  • General Health & Medical Sciences (AREA)
  • General Engineering & Computer Science (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Calculators And Similar Devices (AREA)

Abstract

本申请实施例涉及通信技术领域，尤其涉及一种日程更新方法和设备。其中，日程更新方法包括：接收第一日程信息，根据所述第一日程信息在日历应用中显示第一日程；接收第二日程信息，所述第二日程信息与所述第一日程信息的日程标识相同，并且所述第一日程信息和所述第二日程信息存在至少一个不同的日程字段；根据所述至少一个不同的日程字段，将所述第二日程信息更新至所述日历应用的所述第一日程，并在更新后的所述第一日程中显示至少一个标签。本申请能够在日历应用的日程中显示与更新的日程字段对应的标签，以提示用户日程发生变更。

Description

日程更新方法和设备
本申请要求于2021年8月12日提交中国专利局、申请号为202110926177.4、申请名称为“日程更新方法和设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及日程更新技术领域，尤其涉及一种日程更新方法和设备。
背景技术
用户在使用日历应用的过程中，经常会遇到日程变更的情况，比如，由于会议冲突导致会议的时间临时变更或者地点临时变更。但是在目前的日历应用中，没有给用户足够的日程变更的提示，导致用户不知道日程发生变更。
申请内容
本申请实施例提供一种日程更新方法和设备，能够在日历应用的日程中显示与更新的日程字段对应的标签，以提示用户日程发生变更。
第一方面，本技术方案提供了一种日程更新方法，该方法包括：
接收第一日程信息，根据所述第一日程信息在日历应用中显示第一日程；
接收第二日程信息，所述第二日程信息与所述第一日程信息的日程标识相同，并且所述第一日程信息和所述第二日程信息存在至少一个不同的日程字段；
根据所述至少一个不同的日程字段，将所述第二日程信息更新至所述日历应用的所述第一日程，并在更新后的所述第一日程中显示至少一个标签。
结合第一方面，在第一方面的某些实现方式中，在更新后的所述第一日程中显示至少一个标签，包括：
根据所述至少一个不同的日程字段，以及所述日程字段和所述标签的对应关系，在更新后的所述第一日程中显示至少一个标签。
结合第一方面，在第一方面的某些实现方式中，所述日程字段包括：时间字段、地点字段、主题字段或者与会人字段。
结合第一方面，在第一方面的某些实现方式中，所述标签包括：时间变更、地点变更、主题变更或者与会人变更。
结合第一方面，在第一方面的某些实现方式中，所述日程字段和所述标签的对应关系，包括：所述时间字段和所述时间变更对应，所述地点字段和所述地点变更对应，所述主题字段和所述主题变更对应，所述与会人字段和所述与会人变更对应。
结合第一方面，在第一方面的某些实现方式中，所述标签按照优先级从大到小的排序为：所述时间变更、所述地点变更、所述主题变更、所述与会人变更。
结合第一方面，在第一方面的某些实现方式中，所述第一日程信息和所述第二日程信息来自邮箱客户端。
结合第一方面，在第一方面的某些实现方式中，所述第一日程信息和所述第二日程信息来自所述邮箱客户端接收的包含日程的邮件。
结合第一方面，在第一方面的某些实现方式中，所述第一日程信息和所述第二日程信息来自第三方应用。
结合第一方面，在第一方面的某些实现方式中，所述日程标识包括日程信息的ID。
第二方面，本技术方案提供了一种日程更新设备，包括：
收发单元，用于接收第一日程信息和第二日程信息，所述第二日程信息与所述第一日程信息的日程标识相同，并且所述第一日程信息和所述第二日程信息存在至少一个不同的日程字段；
显示单元，用于根据所述第一日程信息在日历应用中显示第一日程；
更新单元，用于根据所述至少一个不同的日程字段，将所述第二日程信息更新至所述日历应用的所述第一日程；
提示单元，用于在更新后的所述第一日程中显示至少一个标签。
结合第二方面，在第二方面的某些实现方式中，所述提示单元，具体用于根据所述至少一个不同的日程字段，以及所述日程字段和所述标签的对应关系，在更新后的所述第一日程中显示至少一个标签。
结合第二方面，在第二方面的某些实现方式中，所述日程字段包括：时间字段、地点字段、主题字段或者与会人字段。
结合第二方面，在第二方面的某些实现方式中，所述标签包括：时间变更、地点变更、主题变更或者与会人变更。
结合第二方面，在第二方面的某些实现方式中，所述日程字段和所述标签的对应关系，包括：所述时间字段和所述时间变更对应，所述地点字段和所述地点变更对应，所述主题字段和所述主题变更对应，所述与会人字段和所述与会人变更对应。
结合第二方面，在第二方面的某些实现方式中，所述标签按照优先级从大到小的排序为：所述时间变更、所述地点变更、所述主题变更、所述与会人变更。
结合第二方面，在第二方面的某些实现方式中，所述第一日程信息和所述第二日程信息来自邮箱客户端。
结合第二方面，在第二方面的某些实现方式中，所述第一日程信息和所述第二日程信息来自所述邮箱客户端接收的包含日程的邮件。
结合第二方面，在第二方面的某些实现方式中，所述第一日程信息和所述第二日程信息来自第三方应用。
结合第二方面，在第二方面的某些实现方式中，所述日程标识包括日程信息的ID。
第三方面，本技术方案提供了一种电子设备，包括：一个或多个处理器；存储器；以及一个或多个计算机程序，其中所述一个或多个计算机程序被存储在所述存储器中，所述一个或多个计算机程序包括指令，当所述指令被所述设备执行时，使得所述设备执行以下步骤：
接收第一日程信息，根据所述第一日程信息在日历应用中显示第一日程；
接收第二日程信息，所述第二日程信息与所述第一日程信息的日程标识相同，并且所述第一日程信息和所述第二日程信息存在至少一个不同的日程字段；
根据所述至少一个不同的日程字段，将所述第二日程信息更新至所述日历应用的所述第一日程，并在更新后的所述第一日程中显示至少一个标签。
结合第三方面，在第三方面的某些实现方式中，当所述指令被所述电子设备执行时，使得所述电子设备执行以下步骤：
在更新后的所述第一日程中显示至少一个标签，包括：
根据所述至少一个不同的日程字段，以及所述日程字段和所述标签的对应关系，在更新后的所述第一日程中显示至少一个标签。
结合第三方面，在第三方面的某些实现方式中，所述日程字段包括：时间字段、地点字段、主题字段或者与会人字段。
结合第三方面，在第三方面的某些实现方式中，所述标签包括：时间变更、地点变更、主题变更或者与会人变更。
结合第三方面，在第三方面的某些实现方式中，所述日程字段和所述标签的对应关系，包括：所述时间字段和所述时间变更对应，所述地点字段和所述地点变更对应，所述主题字段和所述主题变更对应，所述与会人字段和所述与会人变更对应。
结合第三方面，在第三方面的某些实现方式中，所述标签按照优先级从大到小的排序为：所述时间变更、所述地点变更、所述主题变更、所述与会人变更。
结合第三方面，在第三方面的某些实现方式中所述第一日程信息和所述第二日程信息来自邮箱客户端。
结合第三方面，在第三方面的某些实现方式中，所述第一日程信息和所述第二日程信息来自所述邮箱客户端接收的包含日程的邮件。
结合第三方面，在第三方面的某些实现方式中，所述第一日程信息和所述第二日程信息来自第三方应用。
结合第三方面，在第三方面的某些实现方式中，所述日程标识包括日程信息的ID
第四方面，本技术方案提供了一种日程更新设备，所述设备包括存储介质和中央处理器，所述存储介质可以是非易失性存储介质，所述存储介质中存储有计算机可执行程序，所述中央处理器与所述非易失性存储介质连接，并执行所述计算机可执行程序以实现所述第一方面或者第一方面的任一可能的实现方式中的方法。
第五方面，本技术方案提供了一种芯片，所述芯片包括处理器与数据接口，所述处理器通过所述数据接口读取存储器上存储的指令，执行第一方面或第一方面的任一可能的实现方式中的方法。
可选的，作为一种实现方式，所述芯片还可以包括存储器，所述存储器中存储有指令，所述处理器用于执行所述存储器上存储的指令，当所述指令被执行时，所述处理器用于执行第一方面或第一方面的任一可能的实现方式中的方法。
第六方面，本技术方案提供了一种计算机可读存储介质，所述计算机可读介质存储用于设备执行的程序代码，所述程序代码包括用于执行第一方面或者第一方面的任一可能的实现方式中的方法的指令。
附图说明
图1是日历应用的主界面的一种示意图；
图2是日历应用的新建日程界面的一种示意图；
图3是日历应用的新建日程界面的又一种示意图；
图4是日历应用的主界面的又一种示意图；
图5是日历应用的主界面弹出选择框的示意图；
图6是日历应用的添加账户界面的一种示意图；
图7是日历应用的添加账户界面的又一种示意图；
图8是自动添加日程的一种系统框架图；
图9是日历应用的主界面的又一种示意图；
图10是本申请实施例提供一种日程更新的系统架构；
图11是本申请实施例提供的日历应用的主界面的一种示意图；
图12是本申请实施例提供的电子设备的一种结构示意图；
图13是本申请实施例提供的电子设备的一种软件结构框图；
图14是本申请实施例提供的一种日程更新方法的流程图；
图15是本申请实施例提供的又一种日程更新方法的流程图；
图16是本申请实施例提供的日程更新设备的一种结构示意图。
具体实施方式
下面将结合附图，对本申请中的技术方案进行描述。
本申请实施例提供的日程更新方法应用于电子设备中日程同步的场景中，当日程发生变更时，能够根据变更的日程字段，在日历应用的日程中显示与日程字段对应的标签，以提示用户日程发生变更。
由于本申请实施例涉及日历应用中日程添加和日程同步的场景，为了便于理解，下面先对相关概念进行介绍。
(1)日程添加
日程添加的方式包括手动添加和自动添加。
手动添加是指用户在日历应用中通过手动操作添加日程。以电子设备为手机为例，用户打开手机中日历应用，屏幕显示日历应用的主界面，如图1所示，日历应用的主界面中显示今天的日期为2021年8月6日，并且显示今天没有日程，屏幕的右下角位置显示一个添加按钮a，添加按钮a用于添加新日程。用户点击添加按钮a之后，如图2所示，屏幕显示新建日程的标题、地点、时间、说明等内容，用户可以通过在此界面编辑新日程的内容。例如，如图3所示，新日程的标题为“智能大会”，地点为“梅江会展中心”，开始时间为“8月7日09：00”，并且设置为10分钟前提醒和不重复。当用户编辑完新日程后，点击屏幕右上角的完成按钮b以完成编辑，此时手机的屏幕返回日历应用的主界面，用户在日历中选择2021年8月7日，如图4所示，屏幕中显示刚才新建的日程，显示内容包括日程的时间、标题和地点。
自动添加是电子设备将从第三方应用或者邮箱客户端获取的日程自动添加至日历应用的日程中。其中，邮件客户端属于电子设备的系统应用。
其中，自动添加的日程来自用户在邮件客户端或者第三方应用中添加的日程，或者来自邮件客户端接收的邮件，该邮件包含日程信息。
以邮件客户端为例，用户需要提前将邮箱账户添加至日历应用的账户管理中，才可以实现自动添加日程的功能。具体的，以电子设备为手机为例，如图5所述，用户点击日历应用的主界面右上角的按钮c之后，屏幕中弹出选择框，选择框中包括“跳转到指定日期”、“日历账户管理”、“订阅管理”和“设置”4个选项。用户点击“日历账户管理”之后进入日历账户管理界面，如图6所示，日历账户管理界面中显示“添加账户”，用户可以通过点击“添加账户”在日历应用中添加邮箱账户。例如，在日历应用中添加“123456789@qq.com”的邮箱账户之后，如图7所示，日历账户管理界面中会显示“123456789@qq.com”的邮箱账户，并且日历应用具备了访问“123456789@qq.com”的邮箱账户的权限。
用户将邮箱账户添加至日历应用的账户管理中，日历应用获取了访问该邮箱账户的权限；同时，用户在电子设备中的邮箱客户端中登录该邮箱账户。如图8所示，电子设备中的邮件客户端或者第三方应用通过日程同步模块将日程同步至日历存储。日历存储通过日程插入模块将该日程进行存储后，将该日程发送至日历应用。日历应用的日程接收器接收到该日程后，将日程分别发送至日程卡片模块、日程视图模块和日程提醒模块。日程卡片模块用于根据日程的信息显示与该日程对应的日程卡片；日程视图模块用于根据日程的信息在与日程对应的日程卡片中显示视图；日程提醒模块用于根据日程的信息执行日程的提醒操作。
例如，用户在手机中的邮箱客户端中登录“123456789@qq.com”的邮箱账户，当“123456789@qq.com”的邮箱账户接收到包含日程的邮件，该日程的时间是2021年8月9日上午9：00，地点是水上公园，主题是团建，提醒时间是提前30分钟提醒。手机中的日历应用就可以获取邮箱客户端中“123456789@qq.com”的邮箱账户的该日程，并将获取的日程自动添加至日历应用中，日历应用对获取的日程进行显示，如图9所示。
(2)日程同步
日程同步指的电子设备将邮箱客户端或者第三方应用中的日程，与日历应用中的日程进行同步。
用户在使用电子设备时，经常会遇到日程变更的情况，比如，由于会议冲突导致会议的时间临时变更或者地点临时变更。邮件客户端或者第三方应用中的日程发生变更后，邮件客户端或者第三方应用直接将变更后的日程发送给日历应用，日历应用将变更后的日程当作新的日程进行显示，并没有提示用户是日程发生了变更。
综上，在目前的日历应用中，没有给用户足够的日程变更的提示，导致用户不知道日程发生变更。
针对上述技术问题，如图10所示，本申请实施例提供一种日程更新的系统架构。在图10中，系统架构包括邮箱客户端或者第三方应用、日历存储和日历应用。邮箱客户端或者第三方应用包括日程同步模块。日历存储包括日程插入模块、日程修改模块、日程删 除模块、日程变更计算模块和日程变更通知模块。日历应用包括日程变更接收器、日程卡片模块、日程视图模块和日程提醒模块。
日程同步模块，用于将邮件客户端或者第三方应用中的日程信息发送至日历存储的日程识别模块。
日程识别模块，用于识别日程信息的日程标识，并判断日历存储中是否存储有与该日程标识对应的日程信息，若判断出日历存储中未存储与该日程标识对应的日程信息，将日程信息发送至日程插入模块；否则，将日程信息发送至日程修改模块。
其中，日程标识包括日程信息的ID。
日程插入模块，用于将日程信息进行存储，并将日程信息发送至日历应用的日程接收器。
日程接收器，用于将日程信息分别发送至日程卡片模块、日程视图模块和日程提醒模块。日程卡片模块，用于根据日程信息显示对应的日程卡片；日程视图模块用于根据日程信息在日程卡片中显示对应的视图；日程提醒模块，用于根据日程信息执行提醒操作。
日程修改模块，用于根据接收的日程信息，将已存储的日程信息进行修改；并将修改前的日程信息和修改后的日程信息发送至日程变更计算模块。需要说明的是，修改前的日程信息和修改后的日程信息存在至少一个不同的日程字段。
日程变更计算模块，用于根据修改前的日程信息和修改后的日程信息确定至少一个不同的日程字段，并将修改后的日程信息中至少一个不同的日程字段发送至日程变更通知模块。具体的，日程变更计算模块通过将修改前的日程信息的字段和修改后的日程信息的字段进行比对，确定出修改后的日程信息中至少一个不同的日程字段。日程字段包括：时间字段、地点字段、主题字段或者与会人字段。
日程变更通知模块，用于根据修改后的日程信息中的至少一个不同的日程字段和日程信息的日程标识生成日程变更通知，并将日程变更通知发送至日历应用的日程接收器。
日程接收器，还用于通过解析日程变更通知得到修改后的日程信息中的至少一个不同的日程字段和日程信息的日程标识，并将至少一个不同的日程字段和日程标识分别发送至日程卡片模块、日程视图模块和日程提醒模块。
日程卡片模块，还用于根据日程标识找到通知栏中与日程标识对应的日程卡片，根据至少一个不同的日程字段更新对应的信息并显示与至少一个日程字段对应的至少一个标签。标签包括：时间变更、地点变更、主题变更或者与会人变更。标签按照优先级从大到小的排序为：时间变更、地点变更、主题变更、与会人变更。
日程视图模块，还用于根据至少一个日程字段和日程标识，在与更新后的第一日程对应的日程卡片中显示相应的视图。
日程提醒模块，还用于根据至少一个日程字段和日程标识，执行提醒操作。
例如，日程的时间发生了变更，日程提醒模块根据时间字段更改提醒时间，并根据更改后的提醒时间执行提醒操作。
例如，上述“123456789@qq.com”的邮箱账户在接收到上述包含日程的邮件后，又接收一个包含日程的邮件，该日程的日程标识和上述日程的日程标识相同，但是日程的时间是2021年8月9日上午10：00，地点、主题和提醒时间均和上述日程一样。手机中的日历应用获取邮箱客户端中“123456789@qq.com”的邮箱账户的该日程的日程信息，并与 上述日程的日程信息进行比较，确定出时间字段发生了改变，更新日历中上述日程的时间字段，并在日程卡片中显示时间变更的标签，如图11所示。
其中，电子设备可以是手机、平板电脑、可穿戴设备、车载设备、增强现实(augmented reality，AR)/虚拟现实(virtual reality，VR)设备、笔记本电脑、超级移动个人计算机(ultra-mobile personal computer，UMPC)、上网本、个人数字助理(personal digital assistant，PDA)等电子设备，本申请实施例对电子设备的具体类型不作任何限制。
示例性的，图12示出了本申请实施例提供的电子设备100的一种结构示意图。电子设备100可以包括处理器110，外部存储器接口120，内部存储器121，通用串行总线(universal serial bus，USB)接口130，充电管理模块140，电源管理模块141，电池142，天线1，天线2，移动通信模块150，无线通信模块160，音频模块170，扬声器170A，受话器170B，麦克风170C，耳机接口170D，传感器模块180，按键190，马达191，指示器192，摄像头193，显示屏194，以及用户标识模块(subscriber identification module，SIM)卡接口195等。其中传感器模块180可以包括压力传感器180A，陀螺仪传感器180B，气压传感器180C，磁传感器180D，加速度传感器180E，距离传感器180F，接近光传感器180G，指纹传感器180H，温度传感器180J，触摸传感器180K，环境光传感器180L，骨传导传感器180M等。
可以理解的是，本申请实施例示意的结构并不构成对电子设备100的具体限定。在本申请另一些实施例中，电子设备100可以包括比图示更多或更少的部件，或者组合某些部件，或者拆分某些部件，或者不同的部件布置。图示的部件可以以硬件，软件或软件和硬件的组合实现。
处理器110可以包括一个或多个处理单元，例如：处理器110可以包括应用处理器(application processor，AP)，调制解调处理器，图形处理器(graphics processing unit，GPU)，图像信号处理器(image signal processor，ISP)，控制器，视频编解码器，数字信号处理器(digital signal processor，DSP)，基带处理器，和/或神经网络处理器(neural-network processing unit，NPU)等。其中，不同的处理单元可以是独立的器件，也可以集成在一个或多个处理器中。
其中，控制器可以是电子设备100的神经中枢和指挥中心。控制器可以根据指令操作码和时序信号，产生操作控制信号，完成取指令和执行指令的控制。
处理器110中还可以设置存储器，用于存储指令和数据。在一些实施例中，处理器110中的存储器为高速缓冲存储器。该存储器可以保存处理器110刚用过或循环使用的指令或数据。如果处理器110需要再次使用该指令或数据，可从所述存储器中直接调用。避免了重复存取，减少了处理器110的等待时间，因而提高了系统的效率。
在一些实施例中，处理器110可以包括一个或多个接口。接口可以包括集成电路(inter-integrated circuit，I2C)接口，集成电路内置音频(inter-integrated circuit sound，I2S)接口，脉冲编码调制(pulse code modulation，PCM)接口，通用异步收发传输器(universal asynchronous receiver/transmitter，UART)接口，移动产业处理器接口(mobile industry processor interface，MIPI)，通用输入输出(general-purpose input/output，GPIO)接口，用户标识模块(subscriber identity module，SIM)接口，和/或通用串行总线(universal serial bus，USB)接口等。
可以理解的是，本申请实施例示意的各模块间的接口连接关系，只是示意性说明，并不构成对电子设备100的结构限定。在本申请另一些实施例中，电子设备100也可以采用上述实施例中不同的接口连接方式，或多种接口连接方式的组合。
内部存储器121可以用于存储计算机可执行程序代码，所述可执行程序代码包括指令。内部存储器121可以包括存储程序区和存储数据区。其中，存储程序区可存储操作系统，至少一个功能所需的应用程序(比如日程更新功能等)等。存储数据区可存储电子设备100使用过程中所创建的数据(比如图像数据等)等。此外，内部存储器121可以包括高速随机存取存储器，还可以包括非易失性存储器，例如至少一个磁盘存储器件，闪存器件，通用闪存存储器(universal flash storage，UFS)等。处理器110通过运行存储在内部存储器121的指令，和/或存储在设置于处理器中的存储器的指令，执行电子设备100的各种功能应用以及数据处理。
电子设备100的软件系统可以采用分层架构，事件驱动架构，微核架构，微服务架构，或云架构。本申请实施例以分层架构的安卓(Android)系统为例，示例性说明电子设备100的软件结构。
图13是本申请实施例提供的电子设备100的一种软件结构框图。分层架构将软件分成若干个层，每一层都有清晰的角色和分工。层与层之间通过软件接口通信。在一些实施例中，将Android系统分为四层，从上至下分别为应用程序层，应用程序框架层，安卓运行时(Android runtime)和系统库，以及内核层。应用程序层可以包括一系列应用程序包。
如图13所示，应用程序包可以包括相机，图库，日历，通话，地图，导航，WLAN，蓝牙，音乐，视频，短信息等应用程序。
应用程序框架层为应用程序层的应用程序提供应用编程接口(application programming interface，API)和编程框架。应用程序框架层包括一些预先定义的函数。
如图13所示，应用程序框架层可以包括窗口管理器，内容提供器，视图系统，电话管理器，资源管理器，通知管理器等。
窗口管理器用于管理窗口程序。窗口管理器可以获取显示屏大小，判断是否有状态栏，锁定屏幕，截取屏幕等。
内容提供器用来存放和获取数据，并使这些数据可以被应用程序访问。所述数据可以包括视频，图像等。
视图系统包括可视控件，例如显示文字的控件，显示图片的控件等。视图系统可用于构建应用程序。显示界面可以由一个或多个视图组成的。例如，包括短信通知图标的显示界面，可以包括显示文字的视图以及显示图片的视图。
电话管理器用于提供电子设备100的通信功能。例如通话状态的管理(包括接通，挂断等)。
资源管理器为应用程序提供各种资源，比如本地化字符串，图标，图片，布局文件，视频文件等等。
通知管理器使应用程序可以在状态栏中显示通知信息，可以用于传达告知类型的消息，可以短暂停留后自动消失，无需用户交互。比如通知管理器被用于告知下载完成，消息提醒等。通知管理器还可以是以图表或者滚动条文本形式出现在系统顶部状态栏的通 知，例如后台运行的应用程序的通知，还可以是以对话窗口形式出现在屏幕上的通知。例如在状态栏提示文本信息，发出提示音，电子设备振动，指示灯闪烁等。
Android Runtime包括核心库和虚拟机。Android runtime负责安卓系统的调度和管理。
核心库包含两部分：一部分是java语言需要调用的功能函数，另一部分是安卓的核心库。
应用程序层和应用程序框架层运行在虚拟机中。虚拟机将应用程序层和应用程序框架层的java文件执行为二进制文件。虚拟机用于执行对象生命周期的管理，堆栈管理，线程管理，安全和异常的管理，以及垃圾回收等功能。
系统库可以包括多个功能模块。例如：表面管理器(surface manager)，媒体库(Media Libraries)，三维图形处理库(例如：OpenGL ES)，2D图形引擎(例如：SGL)等。
内核层是硬件和软件之间的层。内核层至少包含显示驱动，摄像头驱动，音频驱动，传感器驱动。
为方便理解，本申请以下实施例将以具有图12和图13所示结构的电子设备为例，结合图10的系统架构，对本申请实施例提供的日程更新方法进行说明。如图14所示，本申请实施例提供的一种日程更新方法，包括：
202，接收第一日程信息，根据第一日程信息在日历应用中显示第一日程。
作为一种可选方案，第一日程信息来自邮箱客户端。
例如，用户在邮件客户端中新建一个日程，或者，邮箱客户端接收到邮箱服务器发送的一个包含日程的邮件。其中，邮箱服务器包括Exchange服务器。如图10所示，邮件客户端通过日程同步模块将该日程的日程信息发送至日历存储；日历存储通过日程识别模块识别出该日程信息的日程标识，并判断出日历存储中未存储与该日程标识的日程信息，将日程信息发送至日程插入模块；日程插入模块将日程存储值日历存储中，并将日程信息发送至日历应用的日程接收器；日程接收器将日程信息分别发送至日程卡片模块、日程视图模块和日程提醒模块。日程卡片模块根据日程信息显示对应的日程卡片；日程视图模块根据日程信息在日程卡片中显示对应的视图；日程提醒模块根据日程信息执行提醒操作。
作为另一种可选方案，第一日程信息和第二日程信息来自第三方应用。
例如，用户在第三方应用中新建一个日程。如图10所示，第三方应用通过日程同步模块将该日程的日程信息发送至日历存储；日历存储通过日程识别模块识别出该日程信息的日程标识，并判断出日历存储中未存储与该日程标识的日程信息，将日程信息发送至日程插入模块；日程插入模块将日程信息存储至日历存储中，并将日程信息发送至日历应用的日程接收器；日程接收器将日程信息分别发送至日程卡片模块、日程视图模块和日程提醒模块。日程卡片模块根据日程信息显示对应的日程卡片；日程视图模块根据日程信息在日程卡片中显示对应的视图；日程提醒模块根据日程信息执行提醒操作。
本申请实施例中，第一日程信息中包含多个日程字段，日程字段包括：时间字段、地点字段、主题字段或者与会人字段。
204，接收第二日程信息，第二日程信息与第一日程信息的日程标识相同，并且第一日程信息和第二日程信息存在至少一个不同的日程字段。
本申请实施例中，第二日程信息也包含多个日程字段，日程字段包括：时间字段、地点字段、主题字段或者与会人字段。
需要说明的是，第二日程信息与第一日程信息的日程标识相同，表明第二日程信息是在第一日程信息的基础上生成的。例如，通过更改第一日程信息的时间字段、地点字段、主题字段和与会人字段中的其中之一或者任意组合生成第二日程信息。
其中，日程标识包括日程信息的ID。
本申请实施例中，如图10所示，邮件客户端或者第三方应用将第二日程信息通过日程同步模块发送至日历存储的日程识别模块。日程识别模块通过日程识别模块识别出第二日程信息的日程标识，并判断出日历存储中已存储与该日程标识的第一日程信息，将第二日程信息发送至日程修改模块。日程修改模块，根据接收的第二日程信息，将已存储的第一日程信息进行修改；并将第一日程信息和第二日程信息发送至日程变更计算模块。日程变更计算模块根据第一日程信息和第二日程信息确定至少一个不同的日程字段，并将第二日程信息中至少一个不同的日程字段发送至日程变更通知模块。具体的，日程变更计算模块通过将第一日程信息和第二日程信息的日程字段进行比对，确定出修改后的日程信息中至少一个不同的日程字段。日程字段包括：时间字段、地点字段、主题字段或者与会人字段。日程变更通知模块根据第二日程信息中的至少一个不同的日程字段和日程标识生成日程变更通知，并将日程变更通知发送至日历应用的日程接收器。
206，根据至少一个不同的日程字段，将第二日程信息更新至日历应用的第一日程，并在更新后的第一日程中显示至少一个标签。
需要说明的是，第二日程信息相比于第一日程信息，可以存在至少一个不同的日程字段。
本申请实施例中，在更新后的第一日程中显示至少一个标签，包括：根据至少一个不同的日程字段，以及日程字段和标签的对应关系，在更新后的第一日程中显示至少一个标签。
本申请实施例中，标签包括：时间变更、地点变更、主题变更或者与会人变更。
其中，日程字段和标签的对应关系，包括：时间字段和时间变更对应，地点字段和地点变更对应，主题字段和主题变更对应，与会人字段和与会人变更对应。
本申请实施例中，标签按照优先级从大到小的排序为：时间变更、地点变更、主题变更、与会人变更。
本申请实施例中，如图10所示，日程接收器通过解析日程变更通知得到第二日程信息的中的至少一个不同的日程字段和日程标识，并将至少一个不同的日程字段和日程标识分别发送至日程卡片模块、日程视图模块和日程提醒模块。日程卡片模块根据日程标识找到通知栏中与日程标识对应的日程卡片，根据至少一个不同的日程字段更新对应的信息并显示与至少一个日程字段对应的至少一个标签。日程视图模块根据至少一个日程字段和日程标识，在与更新后的第一日程对应的日程卡片中显示相应的视图。日程提醒模块根据至少一个日程字段和日程标识，执行提醒操作。
本申请实施例提供的日程更新方法的技术方案中，接收第一日程信息，根据第一日程信息在日历应用中显示第一日程；接收第二日程信息，第二日程信息与第一日程信息的日程标识相同，并且第一日程信息和第二日程信息存在至少一个不同的日程字段；根据至 少一个不同的日程字段，将第二日程信息更新日历应用的所述第一日程，并在更新后的第一日程中显示至少一个标签。本申请实施例能够在日历应用的日程中显示与更新的日程字段对应的标签，以提示用户日程发生变更。
如图15所示，本申请实施例提供的又一种日程变更提示方法，应用于电子设备，所述电子设备包括邮件客户端或者第三方应用、日历存储和日历应用；所述方法包括：
401，邮箱客户端或者第三方应用向日历存储发送第一日程信息。
本申请实施例中，如图10所示，邮箱客户端或者第三方应用通过日程同步模块将第一日程的日程信息发送至日历存储。
本申请实施例中，第一日程信息中包含多个日程字段，日程字段包括：时间字段、地点字段、主题字段或者与会人字段。
402，日历存储将第一日程信息存储值日历存储中。
本申请实施例中，如图10所示，日历存储通过日程识别模块识别出第一日程信息的日程标识，并判断出日历存储中未存储与该日程标识的日程信息，将第一日程信息发送至日程插入模块；日程插入模块将第一日程信息存储至日历存储中。
403，日历存储将第一日程信息发送至日历应用。
本申请实施例中，如图10所示，日程插入模块将第一日程信息发送至日历应用的日程接收器。
404，日历应用根据第一日程信息在日历应用中显示第一日程。
本申请实施例中，如图10所示，日程接收器将第一日程信息分别发送至日程卡片模块、日程视图模块和日程提醒模块。日程卡片模块根据第一日程信息显示对应的日程卡片；日程视图模块根据第一日程信息在日程卡片中显示对应的视图；日程提醒模块根据第一日程信息执行提醒操作。
405，邮件客户端或者第三方应用向日历存储发送第二日程信息，第二日程信息于第一日程信息的日程标识相同。
本申请实施例中，第二日程信息也包含多个日程字段，日程字段包括：时间字段、地点字段、主题字段或者与会人字段。
需要说明的是，第二日程信息与第一日程信息的日程标识相同，表明第二日程信息是在第一日程信息的基础上生成的。例如，通过更改第一日程信息的时间字段、地点字段、主题字段和与会人字段中的其中之一或者任意组合生成第二日程信息。
其中，日程标识包括日程信息的ID。
本申请实施例中，如图10所示，邮件客户端或者第三方应用将第二日程信息通过日程同步模块发送至日历存储的日程识别模块。
406，日历存储根据第二日程信息，修改第一日程信息，并根据第一日程信息和第二日程信息，确定第二日程信息中至少一个不同的日程字段。
本申请实施例中，如图10所示，日程识别模块通过日程识别模块识别出第二日程信息的日程标识，并判断出日历存储中已存储与该日程标识的第一日程信息，将第二日程信息发送至日程修改模块。日程修改模块根据接收的第二日程信息，将已存储的第一日程信息进行修改；并将第一日程信息和第二日程信息发送至日程变更计算模块。日程变更计算模块根据第一日程信息和第二日程信息确定至少一个不同的日程字段，并将第二日程信息 中至少一个不同的日程字段发送至日程变更通知模块。具体的，日程变更计算模块通过将第一日程信息和第二日程信息的日程字段进行比对，确定出修改后的日程信息中至少一个不同的日程字段。日程字段包括：时间字段、地点字段、主题字段或者与会人字段。
407，日历存储将至少一个不同的日程字段和日程标识发送给至日历应用。
本申请实施例中，如图10所示，日程变更通知模块根据第二日程信息中的至少一个不同的日程字段和日程标识生成日程变更通知，并将日程变更通知发送至日历应用的日程接收器。
408，日历应用根据至少一个不同的日程字段，将第二日程信息更新至日历应用的第一日程，并在更新后的第一日程中显示至少一个标签。
需要说明的是，第二日程信息相比于第一日程信息，可以存在至少一个不同的日程字段。
本申请实施例中，在更新后的第一日程中显示至少一个标签，包括：根据至少一个不同的日程字段，以及日程字段和标签的对应关系，在更新后的第一日程中显示至少一个标签。
本申请实施例中，标签包括：时间变更、地点变更、主题变更或者与会人变更。
其中，日程字段和标签的对应关系，包括：时间字段和时间变更对应，地点字段和地点变更对应，主题字段和主题变更对应，与会人字段和与会人变更对应。
本申请实施例中，标签按照优先级从大到小的排序为：时间变更、地点变更、主题变更、与会人变更。
本申请实施例中，如图10所示，日程接收器通过解析日程变更通知得到第二日程信息的中的至少一个不同的日程字段和日程标识，并将至少一个不同的日程字段和日程标识分别发送至日程卡片模块、日程视图模块和日程提醒模块。日程卡片模块根据日程标识找到通知栏中与日程标识对应的日程卡片，根据至少一个不同的日程字段更新对应的信息并显示与至少一个日程字段对应的至少一个标签。日程视图模块根据至少一个日程字段和日程标识，在与更新后的第一日程对应的日程卡片中显示相应的视图。日程提醒模块根据至少一个日程字段和日程标识，执行提醒操作。
本实施例可以根据上述方法示例对电子设备进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或者两个以上的功能集成在一个处理模块中。上述集成的模块可以采用硬件的形式实现。需要说明的是，本实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
在采用对应各个功能划分各个功能模块的情况下，图16示出了上述实施例中涉及的日程更新设备的一种可能的组成示意图，如图16所示，该日程更新设备300可以包括：收发单元301、显示单元302、更新单元303和提示单元304，其中：
收发单元301，用于接收第一日程信息和第二日程信息，所述第二日程信息与所述第一日程信息的日程标识相同，并且所述第一日程信息和所述第二日程信息存在至少一个不同的日程字段；
显示单元302，用于根据所述第一日程信息在日历应用中显示第一日程；
更新单元303，用于根据所述至少一个不同的日程字段，将所述第二日程信息更新至所述日历应用的所述第一日程。
提示单元304，用于在更新后的所述第一日程中显示至少一个标签。
在一种可能的实现方式中，提示单元304，具体用于根据所述至少一个不同的日程字段，以及所述日程字段和所述标签的对应关系，在更新后的所述第一日程中显示至少一个标签。
在一种可能的实现方式中，所述日程字段包括：时间字段、地点字段、主题字段或者与会人字段。
在一种可能的实现方式中，所述标签包括：时间变更、地点变更、主题变更或者与会人变更。
在一种可能的实现方式中，所述日程字段和所述标签的对应关系，包括：所述时间字段和所述时间变更对应，所述地点字段和所述地点变更对应，所述主题字段和所述主题变更对应，所述与会人字段和所述与会人变更对应。
在一种可能的实现方式中，所述标签按照优先级从大到小的排序为：时间变更、地点变更、主题变更、与会人变更。
在一种可能的实现方式中，所述第一日程信息和所述第二日程信息来自邮箱客户端。
在一种可能的实现方式中，所述第一日程信息和所述第二日程信息来自所述邮箱客户端接收的包含日程的邮件。
在一种可能的实现方式中，所述第一日程信息和所述第二日程信息来自第三方应用。
在一种可能的实现方式中，所述日程标识包括日程信息的ID。
应理解，这里的电子设备以功能单元的形式体现。这里的术语“单元”可以通过软件和/或硬件形式实现，对此不作具体限定。例如，“单元”可以是实现上述功能的软件程序、硬件电路或二者结合。所述硬件电路可能包括应用特有集成电路(application specific integrated circuit，ASIC)、电子电路、用于执行一个或多个软件或固件程序的处理器(例如共享处理器、专有处理器或组处理器等)和存储器、合并逻辑电路和/或其它支持所描述的功能的合适组件。
本申请还提供了一种日程更新设备，所述设备包括存储介质和中央处理器，所述存储介质可以是非易失性存储介质，所述存储介质中存储有计算机可执行程序，所述中央处理器与所述非易失性存储介质连接，并执行所述计算机可执行程序以实现上述日程更新方法。
本申请还提供了一种计算机可读存储介质，该计算机可读存储介质中存储有指令，当该指令在计算机上运行时，使得计算机执行本申请日程更新方法的各个步骤。
本申请还提供了一种包含指令的计算机程序产品，当该计算机程序产品在计算机或任一至少一种处理器上运行时，使得计算机执行本申请日程更新方法的各个步骤。
本申请还提供一种芯片，包括处理器与数据接口，所述处理器通过所述数据接口读取存储器上存储的指令，以执行本申请提供的日程更新方法执行的相应操作和/或流程。
可选地，该芯片还包括存储器，该存储器与该处理器通过电路或电线与存储器连接，处理器用于读取并执行该存储器中的计算机程序。进一步可选地，该芯片还包括通信接口，处理器与该通信接口连接。通信接口用于接收需要处理的数据和/或信息，处理器从该通信接口获取该数据和/或信息，并对该数据和/或信息进行处理。该通信接口可以是输入输出接口。
存储器可以是只读存储器(read-only memory，ROM)、可存储静态信息和指令的其它类型的静态存储设备、随机存取存储器(random access memory，RAM)或可存储信息和指令的其它类型的动态存储设备，也可以是电可擦可编程只读存储器(electrically erasable programmable read-only memory，EEPROM)、只读光盘(compact disc read-only memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其它磁存储设备，或者还可以是能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其它介质等。
本申请实施例中，“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示单独存在A、同时存在A和B、单独存在B的情况。其中A，B可以是单数或者复数。字符“/”一般表示前后关联对象是一种“或”的关系。“以下至少一项”及其类似表达，是指的这些项中的任意组合，包括单项或复数项的任意组合。例如，a，b和c中的至少一项可以表示：a,b,c,a-b,a-c,b-c,或a-b-c，其中a,b,c可以是单个，也可以是多个。
本领域普通技术人员可以意识到，本文中公开的实施例中描述的各单元及算法步骤，能够以电子硬件、计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，任一功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。本申请的保护范围应以所述权利要求的保护范围为准。

Claims (21)

  1. 一种日程更新方法，其特征在于，包括：
    接收第一日程信息，根据所述第一日程信息在日历应用中显示第一日程；
    接收第二日程信息，所述第二日程信息与所述第一日程信息的日程标识相同，并且所述第一日程信息和所述第二日程信息存在至少一个不同的日程字段；
    根据所述至少一个不同的日程字段，将所述第二日程信息更新至所述日历应用的所述第一日程，并在更新后的所述第一日程中显示至少一个标签。
  2. 根据权利要求1所述的方法，其特征在于，在更新后的所述第一日程中显示至少一个标签，包括：
    根据所述至少一个不同的日程字段，以及所述日程字段和所述标签的对应关系，在更新后的所述第一日程中显示至少一个标签。
  3. 根据权利要求1或2所述的方法，其特征在于，所述日程字段包括：时间字段、地点字段、主题字段或者与会人字段。
  4. 根据权利要求3所述的方法，其特征在于，所述标签包括：时间变更、地点变更、主题变更或者与会人变更。
  5. 根据权利要求4所述的方法，其特征在于，所述日程字段和所述标签的对应关系，包括：所述时间字段和所述时间变更对应，所述地点字段和所述地点变更对应，所述主题字段和所述主题变更对应，所述与会人字段和所述与会人变更对应。
  6. 根据权利要求4或5所述的方法，其特征在于，所述标签按照优先级从大到小的排序为：所述时间变更、所述地点变更、所述主题变更、所述与会人变更。
  7. 根据权利要求1所述的方法，其特征在于，所述第一日程信息和所述第二日程信息来自邮箱客户端。
  8. 根据权利要求7所述的方法，其特征在于，所述第一日程信息和所述第二日程信息来自所述邮箱客户端接收的包含日程的邮件。
  9. 根据权利要求1所述的方法，其特征在于，所述第一日程信息和所述第二日程信息来自第三方应用。
  10. 根据权利要求1所述的方法，其特征在于，所述日程标识包括日程信息的ID。
  11. 一种电子设备，其特征在于，包括：
    一个或多个处理器；存储器；以及一个或多个计算机程序，其中所述一个或多个计算机程序被存储在所述存储器中，所述一个或多个计算机程序包括指令，当所述指令被所述电子设备执行时，使得所述电子设备执行以下步骤：
    接收第一日程信息，根据所述第一日程信息在日历应用中显示第一日程；
    接收第二日程信息，所述第二日程信息与所述第一日程信息的日程标识相同，并且所述第一日程信息和所述第二日程信息存在至少一个不同的日程字段；
    根据所述至少一个不同的日程字段，将所述第二日程信息更新至所述日历应用的所述第一日程，并在更新后的所述第一日程中显示至少一个标签。
  12. 根据权利要求11所述的设备，其特征在于，当所述指令被所述电子设备执行时，使得所述电子设备执行以下步骤：
    在更新后的所述第一日程中显示至少一个标签，包括：
    根据所述至少一个不同的日程字段，以及所述日程字段和所述标签的对应关系，在更新后的所述第一日程中显示至少一个标签。
  13. 根据权利要求11或12所述的设备，其特征在于，所述日程字段包括：时间字段、地点字段、主题字段或者与会人字段。
  14. 根据权利要求13所述的设备，其特征在于，所述标签包括：时间变更、地点变更、主题变更或者与会人变更。
  15. 根据权利要求14所述的设备，其特征在于，所述日程字段和所述标签的对应关系，包括：所述时间字段和所述时间变更对应，所述地点字段和所述地点变更对应，所述主题字段和所述主题变更对应，所述与会人字段和所述与会人变更对应。
  16. 根据权利要求14或15所述的设备，其特征在于，所述标签按照优先级从大到小的排序为：所述时间变更、所述地点变更、所述主题变更、所述与会人变更。
  17. 根据权利要求11所述的设备，其特征在于，所述第一日程信息和所述第二日程信息来自邮箱客户端。
  18. 根据权利要求17所述的设备，其特征在于，所述第一日程信息和所述第二日程信息来自所述邮箱客户端接收的包含日程的邮件。
  19. 根据权利要求11所述的设备，其特征在于，所述第一日程信息和所述第二日程信息来自第三方应用。
  20. 根据权利要求11所述的设备，其特征在于，所述日程标识包括日程信息的ID。
  21. 一种计算机存储介质，其特征在于，包括计算机指令，当所述计算机指令在电子设备上运行时，使得所述电子设备执行如权利要求1至10中任一项所述的日程更新方法。
PCT/CN2022/091108 2021-08-12 2022-05-06 日程更新方法和设备 WO2023015978A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110926177.4A CN113780980A (zh) 2021-08-12 2021-08-12 日程更新方法和设备
CN202110926177.4 2021-08-12

Publications (1)

Publication Number Publication Date
WO2023015978A1 true WO2023015978A1 (zh) 2023-02-16

Family

ID=78837546

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/091108 WO2023015978A1 (zh) 2021-08-12 2022-05-06 日程更新方法和设备

Country Status (2)

Country Link
CN (1) CN113780980A (zh)
WO (1) WO2023015978A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113780980A (zh) * 2021-08-12 2021-12-10 荣耀终端有限公司 日程更新方法和设备
CN117675495A (zh) * 2022-08-22 2024-03-08 荣耀终端有限公司 一种数据同步方法、电子设备及介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2012032887A (ja) * 2010-07-28 2012-02-16 Fujitsu Ltd スケジュール管理プログラム、スケジュール管理装置およびスケジュール管理方法
CN103024692A (zh) * 2012-11-23 2013-04-03 惠州Tcl移动通信有限公司 管理日程表的方法及其系统
CN103647698A (zh) * 2013-11-28 2014-03-19 宇龙计算机通信科技(深圳)有限公司 关注事件变更的提醒方法和装置
CN111950983A (zh) * 2020-08-13 2020-11-17 上海博泰悦臻网络技术服务有限公司 日程事件的提醒与变更同步的方法、系统、设备及介质
CN113780980A (zh) * 2021-08-12 2021-12-10 荣耀终端有限公司 日程更新方法和设备

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2012032887A (ja) * 2010-07-28 2012-02-16 Fujitsu Ltd スケジュール管理プログラム、スケジュール管理装置およびスケジュール管理方法
CN103024692A (zh) * 2012-11-23 2013-04-03 惠州Tcl移动通信有限公司 管理日程表的方法及其系统
CN103647698A (zh) * 2013-11-28 2014-03-19 宇龙计算机通信科技(深圳)有限公司 关注事件变更的提醒方法和装置
CN111950983A (zh) * 2020-08-13 2020-11-17 上海博泰悦臻网络技术服务有限公司 日程事件的提醒与变更同步的方法、系统、设备及介质
CN113780980A (zh) * 2021-08-12 2021-12-10 荣耀终端有限公司 日程更新方法和设备

Also Published As

Publication number Publication date
CN113780980A (zh) 2021-12-10

Similar Documents

Publication Publication Date Title
WO2023015978A1 (zh) 日程更新方法和设备
WO2021057643A1 (zh) 一种多线程同步方法及电子设备
US20170337045A1 (en) Automatic graphical user interface generation from notification data
EP2843525A1 (en) Electronic device and method for displaying application information
US20170011010A1 (en) Method for displaying web content and electronic device supporting the same
CN115629884B (zh) 一种线程调度方法、电子设备及存储介质
US20180026923A1 (en) Electronic device and email management method therefor
WO2021227860A1 (zh) 一种数据同步的方法、装置、终端以及存储介质
US20230147786A1 (en) Thread Management Method and Apparatus
CN116774809A (zh) 调整频率的方法、装置、电子设备及可读存储介质
CN113986092A (zh) 消息显示方法和装置
CN113419873A (zh) 聊天消息的提醒方法、装置、存储介质及终端设备
WO2023005751A1 (zh) 渲染方法及电子设备
CN114461053B (zh) 资源调度方法及相关装置
US11347554B1 (en) Context-aware job prioritization
CN113641431A (zh) 二维码的增强显示的方法和终端设备
CN114531413A (zh) 电子设备及其邮件同步方法和可读介质
CN110704157A (zh) 一种应用启动方法、相关装置及介质
WO2024007816A1 (zh) 通信方法及装置
CN116700813B (zh) 微件的加载方法、电子设备及可读存储介质
CN117176850B (zh) 界面显示方法及相关装置
WO2024093431A1 (zh) 一种图像绘制方法及电子设备
CN116700818B (zh) 应用程序运行的方法及电子设备
WO2024066976A1 (zh) 控件显示方法及电子设备
CN116661882B (zh) 预加载小程序的方法、电子设备及存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22854975

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE