WO2025098413A1 - 用于管理日程的方法、装置、设备和介质 - Google Patents

用于管理日程的方法、装置、设备和介质 Download PDF

Info

Publication number
WO2025098413A1
WO2025098413A1 PCT/CN2024/130342 CN2024130342W WO2025098413A1 WO 2025098413 A1 WO2025098413 A1 WO 2025098413A1 CN 2024130342 W CN2024130342 W CN 2024130342W WO 2025098413 A1 WO2025098413 A1 WO 2025098413A1
Authority
WO
WIPO (PCT)
Prior art keywords
schedule
information
meeting
user
application
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/CN2024/130342
Other languages
English (en)
French (fr)
Inventor
雷烨
张天豪
张岩
王文博
马兰
成铃君
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Zitiao Network Technology Co Ltd
Original Assignee
Beijing Zitiao Network Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Beijing Zitiao Network Technology Co Ltd filed Critical Beijing Zitiao Network Technology Co Ltd
Publication of WO2025098413A1 publication Critical patent/WO2025098413A1/zh
Anticipated expiration legal-status Critical
Pending legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0481—Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance
    • G06F3/04817—Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance using icons
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/445—Program loading or initiating
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/451—Execution arrangements for user interfaces
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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
    • H04M—TELEPHONIC COMMUNICATION
    • H04M1/00—Substation equipment, e.g. for use by subscribers
    • H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
    • H04M1/724—User interfaces specially adapted for cordless or mobile telephones
    • H04M1/72448—User interfaces specially adapted for cordless or mobile telephones with means for adapting the functionality of the device according to specific conditions
    • H04M1/72451—User interfaces specially adapted for cordless or mobile telephones with means for adapting the functionality of the device according to specific conditions according to schedules, e.g. using calendar applications

Definitions

  • Exemplary implementations of the present disclosure generally relate to schedule management, and more particularly, to methods, apparatuses, devices, and computer-readable storage media for managing schedules.
  • a conference application can provide a meeting reminder at a predetermined time point before the meeting (for example, five minutes in advance, etc.).
  • schedule information can be added to a calendar application to manage the schedule.
  • the user has to open the conference application and/or the calendar application to view the schedule information. At this time, it is expected to present and manage the schedule information in a more convenient and effective way.
  • a method for managing a schedule is provided.
  • it is determined whether a schedule exists within a predetermined time range.
  • first information about the schedule is presented in a predetermined area in a display area of a client device.
  • a device for managing a schedule includes: a determination module configured to determine whether a schedule exists within a predetermined time range; and a first presentation module configured to present first information about the schedule in a predetermined area of a display area of a client device in response to determining that a schedule exists within the predetermined time range.
  • an electronic device in a third aspect of the present disclosure, includes: at least one processing unit; and at least one memory, the at least one memory is coupled to the at least one processing unit and stores instructions for execution by the at least one processing unit, and when the instructions are executed by the at least one processing unit, the electronic device executes the method according to the first aspect of the present disclosure.
  • a computer-readable storage medium on which a computer program is stored.
  • the processor implements the method according to the first aspect of the present disclosure.
  • FIG1 shows a block diagram of an application environment according to an exemplary implementation of the present disclosure
  • FIG2 shows a block diagram for managing a schedule according to some implementations of the present disclosure
  • FIG3 is a block diagram showing information of a conference according to some implementations of the present disclosure.
  • FIG. 4 illustrates a block diagram for determining a meeting icon based on a current time and a time period of a meeting according to some implementations of the present disclosure
  • 5A illustrates a block diagram of user interactions for presenting information about a conference according to some implementations of the present disclosure
  • FIG6 shows a block diagram for presenting detailed information of a meeting according to some implementations of the present disclosure
  • FIG7 is a block diagram showing information of a conference according to some implementations of the present disclosure.
  • FIG8 is a block diagram showing information of conferences in different conference applications according to some implementations of the present disclosure.
  • FIG9 illustrates a block diagram of a conference card according to some implementations of the present disclosure
  • FIG10 illustrates a block diagram of a location for presenting conference information according to some implementations of the present disclosure
  • FIG11 shows a flowchart of a method for managing a schedule according to some implementations of the present disclosure
  • FIG. 12 shows a block diagram of an apparatus for managing a schedule according to some implementations of the present disclosure.
  • FIG. 13 shows a block diagram of a device capable of implementing various implementations of the present disclosure.
  • model may represent an association relationship between various data. For example, the above association relationship may be obtained based on a variety of technical solutions currently known and/or to be developed in the future.
  • a prompt message is sent to the user to clearly prompt the user that the operation requested to be performed will require obtaining and using the user's personal information.
  • the user can autonomously choose whether to provide personal information to software or hardware such as an electronic device, application, server, or storage medium that performs the operation of the technical solution of the present disclosure according to the prompt message.
  • the prompt information in response to receiving an active request from the user, is sent to the user in a manner such as a pop-up window, in which the prompt information can be presented in text form.
  • the pop-up window can also carry a selection control for the user to choose "agree” or “disagree” to provide personal information to the electronic device.
  • the term "in response to” as used herein refers to a state in which a corresponding event occurs or a condition is satisfied. It will be understood that the timing of executing a subsequent action executed in response to the event or condition is not necessarily strongly related to the time when the event occurs or the condition is satisfied. For example, in some cases, the subsequent action may be executed immediately when the event occurs or the condition is satisfied; while in other cases, the subsequent action may be executed some time after the event occurs or the condition is satisfied.
  • FIG. 1 an application environment according to an exemplary implementation of the present disclosure is described.
  • the specific implementation of the present disclosure will be described below using a meeting as an example of a schedule.
  • the schedule herein may include, but is not limited to, meetings, appointments, and any other matters for which a user desires to set reminders.
  • FIG. 1 shows a block diagram 100 of an application environment according to an exemplary implementation of the present disclosure.
  • a meeting reminder may pop up to inform the user of the upcoming meeting information.
  • a meeting reminder 110 as shown in FIG. 1 may be provided, for example, a meeting reminder 110 may be provided at a predetermined time point before the meeting (for example, 10 minutes in advance or at another time point).
  • the meeting reminder 110 may include: the name of the meeting "Technical Discussion", the time of the meeting, and other information.
  • the user may select the reminded meeting in the event box 120 and click on the "Cancel" button. 130 to cancel the reminder, etc.
  • a technical solution for managing meetings using a calendar application has also been proposed. For example, the relevant information of each meeting can be managed in the calendar application. At this time, the user needs to start the calendar application to view and/or manage the meeting information.
  • a method for managing a schedule is proposed.
  • the meeting information of a meeting within a certain time range can be presented in a predetermined area in the display area of a client device.
  • the meeting information will always be presented and will not be blocked by windows of other applications. In this way, it is convenient for users to quickly understand the meeting information they are interested in at any time point.
  • FIG. 2 shows a block diagram 200 for managing a conference according to some implementations of the present disclosure.
  • a display area 210 represents an operation interface of a client device, and the display area 210 may include a plurality of objects (e.g., an application 230, a file 232, and a folder 234, etc.) located on a desktop.
  • the display area 210 may further include windows of one or more applications that the user has opened.
  • a predetermined area 220 may be set in the display area 210.
  • the predetermined area 220 may be located at any unobstructed position in the display area 210, such as at the upper edge or lower edge of the display area 210, etc.
  • the user may specify a predetermined time range (e.g., 1 day, 2 days, or other time range). It may be determined whether there is a meeting within the predetermined time range. If it is determined that there is a meeting within the predetermined time range, information about the meeting may be presented in the predetermined area 220 in the display area 210 of the client device (for ease of description, the information may be referred to as first information).
  • the first information may be summary information about the meeting, such as including the meeting name "technical discussion", the meeting status "in progress", and the like.
  • the user can perform desired operations in the display area 210, for example, one or more applications can be opened.
  • the predetermined area 220 is not blocked by the windows of the opened applications, but the relevant information of the meeting is always presented in the predetermined area 220. In this way, the user can quickly learn the meeting information of interest at any time point, and pay attention to the meeting information at any time without opening the meeting application and/or calendar application.
  • one or more conference applications can be installed at a client device.
  • the various conference applications installed at the client device can be first determined, and then the meeting can be determined from the calendar of each conference application.
  • the meeting is determined from the calendar of the conference application.
  • the calendars of various conference applications can be accessed regularly, or notifications of the latest meetings can be received from the calendar module when the calendar of the conference application is updated.
  • a user can customize the conference information presented within a certain time range. For example, a user can specify to present conference information within 2 days (or 1 day, etc.), etc. Further, various information about the conference can be obtained from the conference application, and whether to present the information of a certain conference can be determined based on the comparison between the time period of the conference and the current time.
  • an indication of no meeting may be presented within the predetermined range 220. For example, it may be presented: "No meeting within 2 days", etc. Alternatively and/or additionally, if it is determined that there is a meeting within the predetermined time range, information about the meeting may be presented in the predetermined area 220.
  • the first information in the predetermined area 220 may include, for example, a conference name 320 and a conference status 330.
  • the conference name 320 herein may be extracted from a conference application.
  • the conference information may be presented in different modes, for example, when the length of the conference name meets a threshold condition (e.g., less than 10 characters, etc.), the full conference name may be presented; when the length of the conference name does not meet the threshold condition, a portion of the conference name may be presented (e.g., the first 10 characters, and/or a subject word in the conference name, etc.).
  • a threshold condition e.g., less than 10 characters, etc.
  • the meeting status 330 can be determined based on the comparison between the meeting time period read from the conference application and the current time. If the current time is within the meeting time period, the meeting status 330 can be expressed as "in progress". If the current time is before the meeting time period, the meeting status 330 can be expressed as the start time of the meeting. Alternatively and/or additionally, the meeting status 330 can represent the difference between the start time of the meeting and the current time, for example, "10 minutes later", etc. According to an exemplary implementation of the present disclosure, it is possible to further distinguish whether the meeting to be started is a meeting of the same day.
  • the start time of the meeting and/or the difference between the start time and the current time can be presented; for a meeting that is not of the same day, the date of the meeting can be presented, for example, "tomorrow”, "the day after tomorrow", etc. In this way, it is convenient for users to understand the urgency of the meeting and arrange their own schedule.
  • the information of the multiple meetings can be presented simultaneously.
  • an overlap indicator e.g., displaying a "+1", "+2" symbol, or an ellipsis, etc.
  • the user is currently holding multiple meetings.
  • a "+1" symbol may be presented in the meeting information to prompt the user that the time periods of multiple meetings overlap.
  • the user may click the "+1" symbol to view information about more meetings.
  • the number in the overlapping symbol may represent the number of meetings that are not displayed.
  • meeting information about one or more meetings may be presented in the predetermined area 220 based on the size of the predetermined area 220. If the predetermined area 220 is large enough to present information about multiple meetings, information about multiple meetings may be presented in sequence.
  • the first information in the predetermined area 220 may further include a meeting icon 310 for reminding the meeting, and the meeting icon 310 may be determined based on a comparison between the time period of the meeting and the current time.
  • FIG4 shows a block diagram 400 for determining a meeting icon based on the current time and the time period of the meeting according to some implementations of the present disclosure. As shown in FIG4 , a corresponding meeting icon is selected based on a comparison 430 between the current time 410 and the time period 420 of the meeting. Assuming that the current time 410 is within the time period 420 of the meeting, an icon 440 may be used as a meeting icon, which may indicate that the meeting is in progress.
  • an icon 442 can be presented to remind the user of the upcoming meeting.
  • an icon 444 can be presented to remind the user to attend the meeting in time.
  • an icon 446 can be presented to inform the user not to forget to participate in the meeting.
  • different meeting icons can indicate different urgency levels of the meeting. In this way, it is convenient for users to promptly understand the meeting situation in the current and future time periods, and then arrange their work schedules in advance.
  • the present disclosure it is possible to detect user interaction between a user of a client device and a user of a client device, and in the case where user interaction is detected, detailed information about the meeting (also referred to as second information) is presented.
  • the second information may include other information in addition to the first information.
  • the presentation of the second information may be triggered based on a variety of user interactions, and more details about user interaction are described in FIG. 5A and FIG. 5B .
  • FIG. 5A shows a block diagram 500A of user interaction for presenting information about a meeting according to some implementations of the present disclosure.
  • a user can utilize a mouse, stylus, and/or finger, etc. to perform an interactive operation 510 (e.g., single-click, double-click, etc.) within a predetermined area 220 to present more information about the meeting.
  • FIG. 5B shows a block diagram 500B of user interaction for presenting information about a meeting according to some implementations of the present disclosure.
  • a user can utilize a mouse, stylus, and/or finger, etc. to perform an interactive operation 520 at a border position of a display area 210 to present detailed information about the meeting at a specified position in the display area 210.
  • FIG6 shows a block diagram 600 for presenting detailed information 610 of a meeting according to some implementations of the present disclosure.
  • the detailed information 610 of the meeting can be displayed in the display area 210.
  • Detailed information 610 of the meeting is presented near the left border of the display area 210.
  • FIG. 6 only shows an example of presenting detailed information 610 near the left border by way of example, and alternatively and/or additionally, the detailed information may be presented at other locations of the screen.
  • the user may slide a finger to the left at the right border of the display area 210, and the detailed information of the meeting may be presented at the right border of the display area 210.
  • the detailed information 610 may include at least any one of the following: the name, status, start time, end time, location, status, information of the conference application used to participate in the conference, and the like.
  • FIG. 7 shows a block diagram 700 of information of a conference according to some implementations of the present disclosure.
  • the detailed information 610 may include a conference card 710 of a recent conference.
  • the conference card 710 may include: the name 714 of the conference, the status 712 of the conference, and the time 716 of the conference (e.g., the start time and the end time).
  • the conference card 710 may include various information about the conference, thereby providing richer content to the user.
  • the conference card 710 may further include: an entry control 720 for participating in the conference.
  • the user can directly click on the entry control 720 to participate in the conference.
  • an entry to participate in the conference can be provided to the user in a more convenient and effective manner.
  • the entry control 720 can be directly used to quickly join the meeting.
  • the user does not have to go through a long operation path to open the conference application, but can directly click on the entry control 720 provided in the conference card 710 to join the meeting.
  • a user may interact with the entry control 720. For example, a user may click on the entry control 720 to start a conference application for participating in a conference. Further, the user may be guided to join a conference in the conference application. Specifically, the user's user ID, conference password, and other information may be used to join the conference. In this way, the user does not have to manually enter a large amount of information in the conference application, but can directly use the auxiliary functions provided by the conference management application to reduce the user's workload.
  • the user's identity in the meeting can be determined, and then the user can be guided to join the meeting in the application based on the determined identity. If the user is a guest in the meeting, the entry control can display "Join Meeting"; if the user is a host in the meeting, the entry control can display "Start Meeting", and so on.
  • meeting card 730 can indicate relevant information of the meeting at 12:00 today
  • meeting cards 732 and 734 can indicate relevant information of the meetings at 14:00 and 16:00 today, respectively.
  • meeting card 740 can indicate relevant information of the meeting at 12:00 tomorrow. The user can click on the meeting card of interest to learn more about the meeting information. In this way, the user does not have to go through a complicated operation path to open the meeting application and/or calendar application, but can view the detailed information 610 of each meeting in a faster way.
  • FIG. 7 merely schematically shows an example of presenting meeting information within the next two days, and alternatively and/or additionally, meeting information within a longer or shorter time range may be presented. 7 to view the entire schedule.
  • one or more conference applications may be installed at the client device.
  • the conference may include different conferences held in different conference applications.
  • information of the conference application used to participate in the conference may be further presented in the conference card.
  • FIG8 shows a block diagram 800 of information about conferences in different conference applications according to some implementations of the present disclosure.
  • each conference card in the detailed information 810 may include information about the conference application used to participate in the conference.
  • conference card 820 may include information 812 about the conference application, that is, use APP1 to participate in the conference
  • conference card 830 may include information 814 about the conference application, that is, use APP1 to participate in the conference
  • conference card 832 may include information 816 about the conference application, that is, use APP2 to participate in the conference, and so on.
  • information about the conference application can be directly provided, so that the user can quickly understand which conference application is used to participate in the conference by viewing the conference card.
  • different formats may be used to present information of meetings corresponding to different meeting applications.
  • a white dialog box may be used to present meeting cards 820, 830, and 834 of a meeting held in APP1
  • a light gray dialog box may be used to present a meeting card 832 of a meeting held in APP2
  • a dark gray dialog box may be used to present a meeting card 840 of a meeting held in APP3.
  • FIG. 9 shows a block diagram 900 of a conference card 910 according to some implementations of the present disclosure.
  • the conference card 910 shows detailed information of a meeting that has not yet started, and the status of the meeting is "not started". Assuming that the user's identity in the meeting is a "moderator", an entry control 920 for initiating a meeting may be presented.
  • various aspects of information about meetings currently in progress and/or meetings that have not yet started may be presented based on a variety of formats, thereby facilitating users to arrange their own schedules.
  • an adjustment control for adjusting the scheduled time range may be presented to the user, for example, an edit box, a selection box, a drop-down menu, a scroll wheel, and other methods may be provided to adjust the scheduled time range.
  • the user may interact with the adjustment control to set the scheduled time range to 1 day, 2 days, or other time lengths. In this way, the user may set the time range of interest according to his or her own needs, and then present the corresponding meeting information.
  • the predetermined area 220 may be located at the edge of the display area 210, and the predetermined area 220 is always presented during the operation of the client device. In other words, the predetermined area 220 always exists and will not be blocked by windows of other applications at the client device. In this way, it is convenient for users to view meeting-related information at any time.
  • the predetermined area 220 may be located in a task bar or a status bar in the display area.
  • FIG. 10 shows a location for presenting conference information according to some implementations of the present disclosure.
  • Block diagram 1000 As shown in FIG. 10, the conference information may be presented at position 1030 in the status bar 1010 in the display area. Alternatively and/or additionally, the conference information may be presented at position 1032 in the task bar 1020 in the display area. In this way, the free space in the status bar and/or the task bar may be fully utilized, and the conference information may be managed in a simpler and more efficient manner.
  • the schedule can be any matter for which the user wishes to set a reminder.
  • the schedule can represent a reminder set by the user to purchase concert tickets (or airplane tickets, train tickets, etc.) at a predetermined time point, and the reminder can be presented in the predetermined area 220.
  • the name of the ticket purchase application and the access portal, etc. can be presented in the page for presenting detailed information. In this way, it is convenient for users to manage schedules related to various matters, thereby improving time management efficiency.
  • schedule information of schedules within a certain time range can be presented in a predetermined area in the display area of the client device. At this time, the schedule information will always be presented and will not be blocked by windows of other applications. In this way, it is convenient for users to quickly understand the schedule information they need to attend at any time point, and then arrange their work schedule in advance.
  • FIG11 shows a flow chart of a method 1100 for managing a schedule according to some implementations of the present disclosure.
  • it is determined whether a schedule exists within a predetermined time range. If it is determined that a schedule exists, the method 1100 proceeds to block 1120.
  • first information about the schedule is presented in a predetermined area in a display area of a client device.
  • the first information includes at least any one of the following: a name and a status of a schedule.
  • the method 1100 further includes: in response to receiving an interaction between a user of the client device and a user of the client device, presenting second information about the schedule, wherein the second information includes other information than the first information.
  • the second information includes at least any one of the following: name, status, start time, end time, location, status of the schedule, and information of a schedule application used to participate in the schedule.
  • the second information further includes: an entry control for participating in the schedule.
  • the method further includes: in response to receiving an interaction between a user of a client device and a portal control, launching a schedule application for participating in a schedule; and guiding the user to join the schedule in the schedule application.
  • guiding a user to add a schedule to an application includes: determining an identity of the user in the schedule; and guiding the user to add the schedule to the application based on the identity.
  • determining a schedule includes: determining at least one schedule application installed at a client device; and determining a schedule from a calendar of the at least one schedule application.
  • the method 1100 further includes: presenting an adjustment control for adjusting the predetermined time range; and adjusting the predetermined time range in response to receiving an interaction with the adjustment control.
  • the method 1100 further includes: in response to determining that there is no schedule within the predetermined time range, presenting an indication of no schedule within the predetermined range.
  • a schedule includes: a first schedule held in a first schedule application and a second schedule held in a second schedule application, and presenting first information includes: presenting first information of the first schedule using a first format, and presenting first information of the second schedule using a second format different from the first format.
  • the predetermined area is located at an edge of the display area, and the predetermined area is always presented during the operation of the client device.
  • the first information includes a schedule icon for reminding a schedule
  • the method 1100 further includes: determining the schedule icon based on a comparison between a time period of the schedule and the current time.
  • the apparatus 1200 includes: a determination module 1210 configured to determine whether a schedule exists within a predetermined time range; and a first presentation module 1220 configured to present first information about the schedule in a predetermined area of a display area of a client device in response to determining that a schedule exists within the predetermined time range.
  • the first information includes at least any one of the following: a name and a status of a schedule.
  • the device 1200 further includes: a second presentation module, configured to present second information about the schedule in response to receiving interaction between a user of the client device and a user of the client device, wherein the second information includes other information than the first information.
  • a second presentation module configured to present second information about the schedule in response to receiving interaction between a user of the client device and a user of the client device, wherein the second information includes other information than the first information.
  • the second information includes at least any one of the following: name, status, start time, end time, location, status of the schedule, and information of a schedule application used to participate in the schedule.
  • the second information further includes: an entry control for participating in the schedule.
  • the device 1200 further includes: a startup module, configured to start a schedule application for participating in a schedule in response to receiving an interaction between a user and an entry control from a client device; and a guidance module, configured to guide the user to add a schedule to the schedule application.
  • a startup module configured to start a schedule application for participating in a schedule in response to receiving an interaction between a user and an entry control from a client device
  • a guidance module configured to guide the user to add a schedule to the schedule application.
  • the guidance module includes: an identity determination module configured to determine the identity of the user in the schedule; and an identity-based guidance module configured to guide the user based on the identity. Users can add schedules in the app.
  • the determination module 1210 includes: an application determination module configured to determine at least one schedule application installed at the client device; and a calendar-based determination module configured to determine a schedule from a calendar of at least one schedule application.
  • the device 1200 further includes: an adjustment control presentation module configured to present an adjustment control for adjusting a predetermined time range; and an adjustment module configured to adjust the predetermined time range in response to receiving an interaction with the adjustment control.
  • the first presentation module further comprises: in response to determining that there is no schedule within the predetermined time range, presenting an indication of no schedule within the predetermined range.
  • a schedule includes: a first schedule held in a first schedule application and a second schedule held in a second schedule application, and presenting first information includes: presenting first information of the first schedule using a first format, and presenting first information of the second schedule using a second format different from the first format.
  • the predetermined area is located at an edge of the display area, and the predetermined area is always presented during the operation of the client device.
  • the first information includes a schedule icon for reminding a schedule
  • the device further includes: an icon determination module configured to determine the schedule icon based on a comparison between a time period of the schedule and a current time.
  • FIG13 shows a block diagram of a device 1300 capable of implementing multiple implementations of the present disclosure. It should be understood that the computing device 1300 shown in FIG13 is merely exemplary and should not constitute any limitation on the functionality and scope of the implementations described herein. The computing device 1300 shown in FIG13 can be used to implement the methods described above.
  • computing device 1300 is in the form of a general-purpose computing device.
  • Components of computing device 1300 may include, but are not limited to, one or more processors or processing units 1310, memory 1320, storage device 1330, one or more communication units 1340, one or more input devices 1350, and one or more output devices 1360.
  • Processing unit 1310 may be an actual or virtual processor and is capable of performing various processes according to a program stored in memory 1320. In a multi-processor system, multiple processing units execute computer executable instructions in parallel to increase the parallel processing capabilities of computing device 1300.
  • the computing device 1300 typically includes a number of computer storage media. Such media may be any available media accessible to the computing device 1300, including but not limited to volatile and nonvolatile media, removable and non-removable media.
  • the memory 1320 may be a volatile memory (e.g., registers, cache, random access memory (RAM)), a nonvolatile memory (e.g., read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory), or some combination thereof.
  • the storage device 1330 may be a removable or non-removable medium and may include a machine-readable medium such as a flash drive, a disk, or any other medium, It may be capable of being used to store information and/or data (eg, training data used for training) and may be accessed within computing device 1300 .
  • the computing device 1300 may further include additional removable/non-removable, volatile/non-volatile storage media.
  • a disk drive for reading or writing from a removable, non-volatile disk e.g., a “floppy disk”
  • an optical drive for reading or writing from a removable, non-volatile optical disk may be provided.
  • each drive may be connected to a bus (not shown) by one or more data media interfaces.
  • the memory 1320 may include a computer program product 1325 having one or more program modules configured to perform various methods or actions of various implementations of the present disclosure.
  • the communication unit 1340 enables communication with other computing devices via a communication medium. Additionally, the functions of the components of the computing device 1300 can be implemented in a single computing cluster or multiple computing machines that can communicate via a communication connection. Therefore, the computing device 1300 can operate in a networked environment using a logical connection with one or more other servers, a network personal computer (PC), or another network node.
  • PC network personal computer
  • Input device 1350 may be one or more input devices, such as a mouse, keyboard, trackball, etc.
  • Output device 1360 may be one or more output devices, such as a display, speaker, printer, etc.
  • Computing device 1300 may also communicate with one or more external devices (not shown) through communication unit 1340 as needed, such as storage devices, display devices, etc., communicate with one or more devices that allow a user to interact with computing device 1300, or communicate with any device that allows computing device 1300 to communicate with one or more other computing devices (e.g., a network card, a modem, etc.). Such communication may be performed via an input/output (I/O) interface (not shown).
  • I/O input/output
  • a computer-readable storage medium on which computer-executable instructions are stored, wherein the computer-executable instructions are executed by a processor to implement the method described above.
  • a computer program product is also provided, the computer program product is tangibly stored on a non-transitory computer-readable medium and includes computer-executable instructions, and the computer-executable instructions are executed by a processor to implement the method described above.
  • a computer program product is provided, on which a computer program is stored, and when the program is executed by a processor, the method described above is implemented.
  • These computer-readable program instructions can be provided to a processing unit of a general-purpose computer, a special-purpose computer, or other programmable data processing device, thereby producing a machine, so that when these instructions are executed by the processing unit of the computer or other programmable data processing device, a device that implements the functions/actions specified in one or more boxes in the flowchart and/or block diagram is generated.
  • These computer-readable program instructions can also be stored in a computer-readable storage medium, and these instructions make the computer, programmable data processing device, and/or other equipment work in a specific way. Therefore, the computer-readable medium storing the instructions includes a manufactured product, which includes implementing the flowchart and/or block diagram. Instructions for various aspects of the functions/actions specified in one or more boxes.
  • Computer-readable program instructions can be loaded onto a computer, other programmable data processing apparatus, or other device so that a series of operational steps are performed on the computer, other programmable data processing apparatus, or other device to produce a computer-implemented process, so that the instructions executed on the computer, other programmable data processing apparatus, or other device implement the functions/actions specified in one or more boxes in the flowchart and/or block diagram.
  • each square box in the flow chart or block diagram can represent a part of a module, program segment or instruction, and a part of a module, program segment or instruction includes one or more executable instructions for realizing the logical function of the specification.
  • the function marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two continuous square boxes can actually be executed substantially in parallel, and they can sometimes be executed in reverse order, depending on the functions involved.
  • each square box in the block diagram and/or flow chart, and the combination of the square boxes in the block diagram and/or flow chart can be realized by a special hardware-based system that performs the function or action of the specification, or can be realized by a combination of special hardware and computer instructions.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Software Systems (AREA)
  • Physics & Mathematics (AREA)
  • Human Resources & Organizations (AREA)
  • General Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • Human Computer Interaction (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Strategic Management (AREA)
  • Marketing (AREA)
  • Quality & Reliability (AREA)
  • Tourism & Hospitality (AREA)
  • Operations Research (AREA)
  • General Business, Economics & Management (AREA)
  • Economics (AREA)
  • Data Mining & Analysis (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

提供了用于管理日程的方法、装置、设备和介质。在一种方法中，确定在预定时间范围内是否存在日程。响应于确定在预定时间范围内存在日程，在客户端设备的显示区域中的预定区域中，呈现关于日程的第一信息。利用本公开的示例性实现方式，在客户端设备的显示区域中的预定区域中，可以始终呈现在感兴趣时间范围内的日程的日程信息，进而便于用户在任意时间点迅速了解自己需要参加的日程信息。

Description

用于管理日程的方法、装置、设备和介质
本申请要求2023年11月07日递交的、标题为“用于管理日程的方法、装置、设备和介质”、申请号为202311475789.1的中国发明专利申请的优先权，该申请的全部内容通过引用结合在本申请中。
技术领域
本公开的示例性实现方式总体涉及日程管理，特别地涉及用于管理日程的方法、装置、设备和计算机可读存储介质。
背景技术
随着计算机技术的发展，目前已经提出了多种日程管理方式。例如，会议应用可以在会议召开前的预定时间点(例如，提前五分钟，等等)提供会议提醒。又例如，可以向日历应用中添加日程信息以便管理日程。然而，用户不得不打开会议应用和/或日历应用，才能查看日程信息。此时，期望以更为方便并且有效的方式来呈现并且管理日程信息。
发明内容
在本公开的第一方面，提供了一种用于管理日程的方法。在该方法中，确定在预定时间范围内是否存在日程。响应于确定在预定时间范围内存在日程，在客户端设备的显示区域中的预定区域中，呈现关于日程的第一信息。
在本公开的第二方面，提供了一种用于管理日程的装置。该装置包括：确定模块，被配置用于确定在预定时间范围内是否存在日程；以及第一呈现模块，被配置用于响应于确定在预定时间范围内存在日程，在客户端设备的显示区域中的预定区域中，呈现关于日程的第一信息。
在本公开的第三方面，提供了一种电子设备。该电子设备包括：至少一个处理单元；以及至少一个存储器，至少一个存储器被耦合到至少一个处理单元并且存储用于由至少一个处理单元执行的指令，指令在由至少一个处理单元执行时使电子设备执行根据本公开第一方面的方法。
在本公开的第四方面，提供了一种计算机可读存储介质，其上存储有计算机程序，计算机程序在被处理器执行时使处理器实现根据本公开第一方面的方法。
应当理解，本内容部分中所描述的内容并非旨在限定本公开的实现方式的关键特 征或重要特征，也不用于限制本公开的范围。本公开的其它特征将通过以下的描述而变得容易理解。
附图说明
在下文中，结合附图并参考以下详细说明，本公开各实现方式的上述和其他特征、优点及方面将变得更加明显。在附图中，相同或相似的附图标注表示相同或相似的元素，其中：
图1示出了根据本公开的一个示例性实现方式的应用环境的框图；
图2示出了根据本公开的一些实现方式的用于管理日程的框图；
图3示出了根据本公开的一些实现方式的会议的信息的框图；
图4示出了根据本公开的一些实现方式的用于基于当前时间和会议的时间段来确定会议图标的框图；
图5A示出了根据本公开的一些实现方式的用于呈现会议的信息的用户交互的框图；
图5B示出了根据本公开的一些实现方式的用于呈现会议的信息的用户交互的框图；
图6示出了根据本公开的一些实现方式的用于呈现会议的详细信息的框图；
图7示出了根据本公开的一些实现方式的会议的信息的框图；
图8示出了根据本公开的一些实现方式的不同会议应用中的会议的信息的框图；
图9示出了根据本公开的一些实现方式的会议卡片的框图；
图10示出了根据本公开的一些实现方式的用于呈现会议信息的位置的框图；
图11示出了根据本公开的一些实现方式的用于管理日程的方法的流程图；
图12示出了根据本公开的一些实现方式的用于管理日程的装置的框图；以及
图13示出了能够实施本公开的多个实现方式的设备的框图。
具体实施方式
下面将参照附图更详细地描述本公开的实现方式。虽然附图中示出了本公开的某些实现方式，然而应当理解的是，本公开可以通过各种形式来实现，而且不应该被解释为限于这里阐述的实现方式，相反，提供这些实现方式是为了更加透彻和完整地理解本公开。应当理解的是，本公开的附图及实现方式仅用于示例性作用，并非用于限制本公开的保护范围。
在本公开的实现方式的描述中，术语“包括”及其类似用语应当理解为开放性包含，即“包括但不限于”。术语“基于”应当理解为“至少部分地基于”。术语“一个实现方式”或“该实现方式”应当理解为“至少一个实现方式”。术语“一些实现方式” 应当理解为“至少一些实现方式”。下文还可能包括其他明确的和隐含的定义。如本文中所使用的，术语“模型”可以表示各个数据之间的关联关系。例如，可以基于目前已知的和/或将在未来开发的多种技术方案来获取上述关联关系。
可以理解的是，本技术方案所涉及的数据(包括但不限于数据本身、数据的获取或使用)应当遵循相应法律法规及相关规定的要求。
可以理解的是，在使用本公开各实施例公开的技术方案之前，均应当根据相关法律法规通过适当的方式对本公开所涉及个人信息的类型、使用范围、使用场景等告知用户并获得用户的授权。
例如，在响应于接收到用户的主动请求时，向用户发送提示信息，以明确地提示用户，其请求执行的操作将需要获取和使用到用户的个人信息。从而，使得用户可以根据提示信息来自主地选择是否向执行本公开技术方案的操作的电子设备、应用程序、服务器或存储介质等软件或硬件提供个人信息。
作为一种可选的但非限制性的实现方式，响应于接收到用户的主动请求，向用户发送提示信息的方式，例如可以是弹出窗口的方式，弹出窗口中可以以文字的方式呈现提示信息。此外，弹出窗口中还可以承载供用户选择“同意”或“不同意”向电子设备提供个人信息的选择控件。
可以理解的是，上述通知和获取用户授权过程仅是示意性的，不对本公开的实现方式构成限定，其他满足相关法律法规的方式也可应用于本公开的实现方式中。
在此使用的术语“响应于”表示相应的事件发生或者条件得以满足的状态。将会理解，响应于该事件或者条件而被执行的后续动作的执行时机，与该事件发生或者条件成立的时间，二者之间未必是强关联的。例如，在某些情况下，后续动作可在事件发生或者条件成立时立即被执行；而在另一些情况下，后续动作可在事件发生或者条件成立后经过一段时间才被执行。
示例环境
随着计算机技术的发展，目前已经提出了多种会议管理方式。参见图1描述根据本公开的一个示例性实现方式的应用环境。为了便于描述，在下文中将以会议作为日程的示例描述本公开的具体实现方式。应当理解，在此的日程可以包括但不限于会议、约会、以及用户期望设置提醒的任何其他事务。
图1示出了根据本公开的一个示例性实现方式的应用环境的框图100。对于临近的会议信息，可以弹出会议提醒来告知用户临近会议信息。例如，可以提供如图1所示的会议提醒110，例如可以在会议之前的预定时间点(例如，提前10分钟或者其他时间点)提供会议提醒110。该会议提醒110可以包括：会议的名称“技术讨论”、会议的时间等信息。进一步，用户可以在事件框120中选中提醒的会议，并且点击消除 130来取消提醒，等等。目前还提出了利用日历应用来管理会议的技术方案。例如，可以在日历应用中管理各个会议的相关信息。此时，用户需要启动日历应用，进而查看和/或管理会议信息。
尽管上述技术方案可以在一定程度上便于用户管理会议信息，然而，对于感兴趣的会议信息，用户无法随时查看会议信息，并且用户仅能在会议开始前的预定时间点接收会议提醒110。在关闭会议提醒之后，用户并不能持续查看会议信息。当用户希望持续查看会议信息时，不得不打开会议应用和/或日历应用，此时操作路径较长。鉴于上述不足，期望以更为方便并且有效的方式来呈现并且管理会议信息。
管理日程的概要
为了至少部分地解决现有技术中的不足，根据本公开的一个示例性实现方式，提出了一种用于管理日程的方法。概括而言，可以在客户端设备的显示区域中的预定区域中，呈现在某个时间范围的会议的会议信息。此时，会议信息将始终被呈现，并且不会被其他应用的窗口所遮挡。以此方式，可以便于用户在任意时间点迅速了解自己感兴趣的会议信息。
参见图2描述根据本公开的一个示例性实现方式的概要，图2示出了根据本公开的一些实现方式的用于管理会议的框图200。如图2所示，显示区域210表示客户端设备的操作界面，并且显示区域210可以包括位于桌面中的多个对象(例如，应用230、文件232、以及文件夹234，等等)。尽管未示出，显示区域210可以进一步包括用户已经打开的一个或多个应用的窗口。
在显示区域210中可以设置预定区域220。该预定区域220可以位于显示区域210中的不受遮挡的任意位置，例如位于显示区域210的上侧边缘、或下侧边缘，等等。用户可以指定预定的时间范围(例如，1天、2天或者其他时间范围)。可以确定在该预定时间范围内是否存在会议。如果确定在预定时间范围内存在会议，则可以在客户端设备的显示区域210中的预定区域220中，呈现关于该会议的信息(为了便于描述，可以将该信息称为第一信息)。在此，第一信息可以是有关会议的概要信息，例如包括会议名称“技术讨论”、会议状态“进行中”，等等。
用户可以在显示区域210中执行期望的操作，例如，可以打开一个或多个应用。此时，预定区域220并不会被打开的应用的窗口所遮挡，而是会议的相关信息始终被呈现在预定区域220内。以此方式，用户在任意时间点都可以迅速了解自己感兴趣的会议信息，并且在无需打开会议应用和/或日历应用的情况下，随时关注会议信息。
管理日程的详细过程
已经参见图2描述了根据本公开的一个示例性实现方式的概要，在下文中，将描 述有关管理会议信息的更多细节。根据本公开的一个示例性实现方式，在客户端设备处可以安装一个或多个会议应用(例如，由不同开发者提供的会议应用，例如，音频会议应用、视频会议应用，等等)。此时，可以首先确定在客户端设备处安装的各个会议应用，进而从各个会议应用的日历中确定会议。在本公开的上下文中，在会议应用许可的情况下，从会议应用的日历中确定会议。例如，可以定期访问各个会议应用的日历，或者可以在会议应用的日历被更新的情况下，从日历模块接收最新会议的通知。
根据本公开的一个示例性实现方式，用户可以自定义呈现在某个时间范围内的会议信息。例如，用户可以指定呈现2天(或者1天，等等)内的会议信息，等等。进一步，可以从会议应用中获取有关会议的多方面信息，并且可以基于会议的时间段与当前时间之间的比较，来确定是否呈现某个会议的信息。
根据本公开的一个示例性实现方式，如果确定在预定时间范围内不存在会议，则在预定范围220内可以呈现无会议的指示。例如，可以呈现：“2天内没有会议”，等等。备选地和/或附加地，如果确定在该预定时间范围内存在会议，则可以预定区域220中呈现关于该会议的信息。
参见图3描述会议信息的更多细节，该图3示出了根据本公开的一些实现方式的会议的信息的框图100。如图3所示，预定区域220中的第一信息例如可以包括会议名称320和会议状态330。将会理解，在此的会议名称320可以是从会议应用中提取的。可以以不同模式来呈现会议信息，例如，当会议名称的长度满足阈值条件(例如，低于10个字符，等等)时，可以呈现完整的会议名称；当会议名称的长度不满足该阈值条件时，可以呈现会议名称中的一部分(例如，前10个字符，和/或会议名称中的主题词，等等)。
根据本公开的一个示例性实现方式，可以基于从会议应用中读取的会议时间段以及当前时间之间的比较，来确定会议状态330。如果当前时间处于会议时间段之内，则会议状态330可以表示为“进行中”。如果当前时间处于会议时间段之前，则会议状态330可以表示为会议的开始时间。备选地和/或附加地，会议状态330可以表示会议的开始时间与当前时间之间的差异，例如，“10分钟后”，等等。根据本公开的一个示例性实现方式，可以进一步区分待开始会议是否为当日会议。对于当日会议，可以呈现会议的开始时间和/或开始时间与当前时间之间的差异；对于非当日会议，可以呈现会议的日期，例如，“明天”、“后天”，等等。以此方式，可以便于用户了解会议的紧急程度，进而安排自己的日程。
根据本公开的一个示例性实现方式，如果多个会议的时间段之间出现重叠，则可以同时呈现多个会议的信息。假设在当前时间点正在召开多个会议，则可以在会议信息中呈现重叠指示符(例如，显示“+1”、“+2”符号，或者省略号等)，以便提示 用户此时正在召开多个会议。又例如，假设在某个时间点将会召开多个会议，也可以在会议信息中呈现“+1”符号，以便提示用户多个会议的时间段有所重叠。此时，用户可以点击“+1”符号，以便查看有关更多会议的信息。在此，重叠符号中的数字可以表示未被显示的会议数量。备选地和/或附加地，可以基于预定区域220的大小来在该预定区域220中呈现有关一个或多个会议的会议信息。如果预定区域220足够呈现多个会议信息，可以按顺序呈现多个会议的信息。
如图3所示，预定区域220中的第一信息可以进一步包括用于提醒会议的会议图标310，并且可以基于会议的时间段与当前时间之间的比较来确定会议图标310。图4示出了根据本公开的一些实现方式的用于基于当前时间和会议的时间段来确定会议图标的框图400。如图4所示，基于当前时间410和会议的时间段420之间的比较430来选择相应的会议图标。假设当前时间410处于会议的时间段420之内，则可以将图标440作为会议图标，该图标440可以表示会议正在进行中。
备选地和/或附加地，假设当前时间410与会议的时间段420之间的间隔较小(例如，0-30分钟，或者其他区间)，这表示会议即将开始并且可以呈现图标442，以便提醒用户注意即将开始的会议。假设当前时间410与会议的时间段420之间的间隔居中(例如，30-60分钟，或者其他区间)，则可以呈现图标444，以便提醒用户注意及时参加会议。假设当前时间410与会议的时间段420之间的间隔较长(例如，1小时之后，或者其他区间)，则可以呈现图标446，以便告知用户不要忘记参与会议。利用本公开的示例性实现方式，不同的会议图标可以指示会议的不同紧急程度。以此方式，可以便于用户及时了解在当前和未来各个时间段内的会议情况，进而提前安排自己的工作日程。
根据本公开的一个示例性实现方式，可以检测客户端设备的用户与客户端设备的用户交互，并且在检测到用户交互的情况下，呈现关于会议的详细信息(也称为第二信息)。在此，第二信息可以包括第一信息以外的其他信息。可以基于多种用户交互来触发呈现第二信息，参见图5A和图5B描述有关用户交互的更多细节。
图5A示出了根据本公开的一些实现方式的用于呈现会议的信息的用户交互的框图500A。如图5A所示，用户可以利用鼠标、触笔、和/或手指等来在预定区域220内执行交互操作510(例如，单击、双击，等等)，以便呈现有关会议的更多信息。进一步，图5B示出了根据本公开的一些实现方式的用于呈现会议的信息的用户交互的框图500B。如图5B所示，用户可以利用鼠标、触笔、和/或手指等来在显示区域210的边界位置处执行交互操作520，以便在显示区域210中的指定位置处呈现有关会议的详细信息。
图6示出了根据本公开的一些实现方式的用于呈现会议的详细信息610的框图600。例如，随着用户从显示区域210的左侧边界向右侧滑动手指，可以在显示区域210 的左侧边界附近呈现会议的详细信息610。将会理解，图6仅以示例方式示出在左侧边界附近呈现详细信息610的示例，备选地和/或附加地，可以在屏幕的其他位置处呈现该详细信息。例如，用户可以在显示区域210的右侧边界处向左侧滑动手指，此时可以在显示区域210的右侧边界处呈现会议的详细信息。
根据本公开的一个示例性实现方式，详细信息610可以包括以下至少任一项：会议的名称、状态、开始时间、结束时间、地点、状态、用于参与会议的会议应用的信息，等等。在下文中，参见图7描述有关详细信息的更多细节，该图7示出了根据本公开的一些实现方式的会议的信息的框图700。如图7所示，详细信息610可以包括最近会议的会议卡片710。具体地，会议卡片710可以包括：会议的名称714、会议的状态712、会议的时间716(例如，开始时间和结束时间)。以此方式，会议卡片710可以包括有关会议的多方面的信息，进而向用户提供更为丰富的内容。
备选地和/或附加地，会议卡片710可以进一步包括：用于参与会议的入口控件720。此时，用户可以直接点击入口控件720来参与会议。利用本公开的示例性实现方式，可以以更为方便并且有效的方式来向用户提供参与会议的入口。尤其是，当用户发现会议临近或者已经到达会议的开始时间时，可以直接利用入口控件720来快速加入会议。此时用户不必经由漫长的操作路径来打开会议应用，而是可以直接点击会议卡片710中提供的入口控件720即可加入会议。
根据本公开的一个示例性实现方式，用户可以与入口控件720进行交互。例如，用户可以点击入口控件720，以便启动用于参与会议的会议应用。进一步，可以引导用户在会议应用中加入会议。具体地，可以利用该用户的用户标识、会议密码等信息来加入会议。以此方式，用户不必在会议应用中手工输入大量信息，而是可以直接利用会议管理应用提供的辅助功能来减轻用户的工作负载。
根据本公开的一个示例性实现方式，为了引导用户在应用中加入会议，可以确定用户在会议中的身份，继而基于该确定的身份来引导用户在应用中加入会议。假设用户在会议中为访客身份，则入口控件可以显示“加入会议”；假设用户在会议中为主持人身份，则入口控件可以显示“发起会议”，等等。
如图7所示，可以以不同的格式来呈现后续的紧急程度较低的其他会议的信息。例如，会议卡片730可以表示今日12点的会议的相关信息，会议卡片732和734可以分别表示今日14点和16点的会议的相关信息。进一步，会议卡片740可以表示明日12点的会议的相关信息。用户可以点击感兴趣的会议卡片，进而了解更多会议信息。以此方式，用户不必经过复杂的操作路径来打开会议应用和/或日历应用，而是可以以更为快速的方式来查看各个会议的详细信息610。
将会理解，图7仅仅示意性示出了呈现未来两日内的会议信息的示例，备选地和/或附加地，可以呈现更长或者更短时间范围内的会议信息。进一步，用户可以点击图 7中的控件750，以便查看全部日程。
通常而言，在客户端设备处可能会安装一个或多个会议应用。此时，会议可以包括在不同会议应用中召开的不同会议。为了便于区分使用哪个会议应用来参与会议，可以在会议卡片中进一步呈现用于参与会议的会议应用的信息。
图8示出了根据本公开的一些实现方式的不同会议应用中的会议的信息的框图800。如图8所示，详细信息810中的各个会议卡片可以包括用于参与会议的会议应用的信息。例如，会议卡片820可以包括会议应用的信息812，也即，使用APP1来参与会议；会议卡片830可以包括会议应用的信息814，也即，使用APP1来参与会议；并且会议卡片832可以包括会议应用的信息816，也即，使用APP2来参与会议，等等。以此方式，可以直接提供有关会议应用的信息，进而使得用户通过查看会议卡片即可快速了解使用哪个会议应用来参与会议。
根据本公开的一个示例性实现方式，可以利用不同的格式(例如，不同颜色、不同字体，等等)来呈现对应于不同会议应用的会议的信息。如图8所示，可以利用白色对话框来呈现在APP1中召开的会议的会议卡片820、830、和834，可以利用浅灰对话框来呈现在APP2中召开的会议的会议卡片832，并且可以利用深灰色对话框来呈现在APP3中召开的会议的会议卡片840。以此方式，可以便于用户了解会议与会议应用之间的对应关系，进而便于提高用户管理会议日程的效率。
将会理解，图8中的各个会议卡片仅仅是示意性而并非限制性的，并且可以以其他格式来呈现会议卡片。图9示出了根据本公开的一些实现方式的会议卡片910的框图900。如图9所示，会议卡片910示出了尚未开始的会议的详细信息，此时会议的状态为“未开始”。假设用户在会议中的身份为“主持人”，则可以呈现用于发起会议的入口控件920。利用本公开的示例性实现方式，可以基于多种格式来呈现目前正在进行的会议和/或尚未开始的会议的多方面信息，从而便于用户安排自身的日程。
根据本公开的一个示例性实现方式，可以向用户呈现用于调整预定时间范围的调整控件，例如，可以提供编辑框、选择框、下拉菜单、滚轮等多种方式来调整预定时间范围。用户可以与调整控件交互，以便将预定时间范围设置为1天、2天、或者其他时间长度。以此方式，可以便于用户根据自身需求来设置感兴趣的时间范围，进而呈现相应的会议信息。
根据本公开的一个示例性实现方式，预定区域220可以位于显示区域210的边缘，并且该预定区域220在客户端设备的运行期间始终被呈现。换言之，该预定区域220始终存在并且不会被客户端设备处的其他应用的窗口所遮挡。以此方式，可以便于用户随时查看会议相关信息。
根据本公开的一个示例性实现方式，预定区域220可以位于显示区域中的任务栏或者状态栏中。图10示出了根据本公开的一些实现方式的用于呈现会议信息的位置的 框图1000。如图10所示，可以在显示区域中的状态栏1010中的位置1030处呈现会议信息。备选地和/或附加地，可以在显示区域中的任务栏1020中的位置1032处呈现会议信息。以此方式，可以充分利用状态栏和/或任务栏中的空闲空间，并且可以以更为简单并且有效的方式来管理会议信息。
应当理解，尽管上文以会议作为日程的具体示例描述了管理会议的具体过程。备选地和/或附加地，在此的日程可以是用户期望设置提醒的任何事务。例如，日程可以表示用户设置的在预定时间点购买演唱会门票(或者飞机票、火车票，等等)的提醒，此时可以在预定区域220中呈现该提醒。进一步，可以在用于呈现详细信息的页面中呈现购票应用的名称以及访问入口，等等。以此方式，可以便于用户管理多种事务相关的日程，从而提高时间管理效率。
利用本公开的示例性实现方式，可以在客户端设备的显示区域中的预定区域中，呈现在某个时间范围的日程的日程信息。此时，日程信息将始终被呈现，并且不会被其他应用的窗口所遮挡。以此方式，可以便于用户在任意时间点迅速了解自己需要参加的日程信息，进而提前安排自己的工作日程。
示例过程
图11示出了根据本公开的一些实现方式的用于管理日程的方法1100的流程图。在框1110处，确定在预定时间范围内是否存在日程。如果确定存在日程，则方法1100前进至框1120。在框1120处，在客户端设备的显示区域中的预定区域中，呈现关于日程的第一信息。
根据本公开的一个示例性实现方式，第一信息包括以下至少任一项：日程的名称、状态。
根据本公开的一个示例性实现方式，该方法1100进一步包括：响应于接收到来自客户端设备的用户与客户端设备的用户交互，呈现关于日程的第二信息，第二信息包括第一信息以外的其他信息。
根据本公开的一个示例性实现方式，第二信息包括以下至少任一项：日程的名称、状态、开始时间、结束时间、地点、状态、用于参与日程的日程应用的信息。
根据本公开的一个示例性实现方式，第二信息进一步包括：用于参与日程的入口控件。
根据本公开的一个示例性实现方式，该方法进一步包括：响应于接收到来自客户端设备的用户与入口控件的交互，启动用于参与日程的日程应用；以及引导用户在日程应用中加入日程。
根据本公开的一个示例性实现方式，引导用户在应用中加入日程包括：确定用户在日程中的身份；以及基于身份来引导用户在应用中加入日程。
根据本公开的一个示例性实现方式，确定日程包括：确定在客户端设备处安装的至少一个日程应用；以及从至少一个日程应用的日历中确定日程。
根据本公开的一个示例性实现方式，该方法1100进一步包括：呈现用于调整预定时间范围的调整控件；以及响应于接收到针对调整控件的交互，调整预定时间范围。
根据本公开的一个示例性实现方式，该方法1100进一步包括：响应于确定不存预定时间范围内的日程，在预定范围内呈现无日程的指示。
根据本公开的一个示例性实现方式，日程包括：在第一日程应用中召开的第一日程和在第二日程应用中召开的第二日程，并且呈现第一信息包括：利用第一格式来呈现第一日程的第一信息，并且利用不同于第一格式的第二格式来呈现第二日程的第一信息。
根据本公开的一个示例性实现方式，预定区域位于显示区域的边缘，并且预定区域在客户端设备的运行期间始终被呈现。
根据本公开的一个示例性实现方式，第一信息包括用于提醒日程的日程图标，以及方法1100进一步包括：基于日程的时间段与当前时间之间的比较来确定日程图标。
示例装置和设备
图12示出了根据本公开的一些实现方式的用于管理日程的装置1200的框图。该装置1200包括：确定模块1210，被配置用于确定在预定时间范围内是否存在日程；以及第一呈现模块1220，被配置用于响应于确定在预定时间范围内存在日程，在客户端设备的显示区域中的预定区域中，呈现关于日程的第一信息。
根据本公开的一个示例性实现方式，第一信息包括以下至少任一项：日程的名称、状态。
根据本公开的一个示例性实现方式，该设备1200进一步包括：第二呈现模块，被配置用于响应于接收到来自客户端设备的用户与客户端设备的用户交互，呈现关于日程的第二信息，第二信息包括第一信息以外的其他信息。
根据本公开的一个示例性实现方式，第二信息包括以下至少任一项：日程的名称、状态、开始时间、结束时间、地点、状态、用于参与日程的日程应用的信息。
根据本公开的一个示例性实现方式，第二信息进一步包括：用于参与日程的入口控件。
根据本公开的一个示例性实现方式，该设备1200进一步包括：启动模块，被配置用于响应于接收到来自客户端设备的用户与入口控件的交互，启动用于参与日程的日程应用；以及引导模块，被配置用于引导用户在日程应用中加入日程。
根据本公开的一个示例性实现方式，引导模块包括：身份确定模块，被配置用于确定用户在日程中的身份；以及基于身份的引导模块，被配置用于基于身份来引导用 户在应用中加入日程。
根据本公开的一个示例性实现方式，确定模块1210包括：应用确定模块，被配置用于确定在客户端设备处安装的至少一个日程应用；以及基于日历的确定模块，被配置用于从至少一个日程应用的日历中确定日程。
根据本公开的一个示例性实现方式，该装置1200进一步包括：调整控件呈现模块，被配置用于呈现用于调整预定时间范围的调整控件；以及调整模块，被配置用于响应于接收到针对调整控件的交互，调整预定时间范围。
根据本公开的一个示例性实现方式，第一呈现模块进一步包括：响应于确定不存预定时间范围内的日程，在预定范围内呈现无日程的指示。
根据本公开的一个示例性实现方式，日程包括：在第一日程应用中召开的第一日程和在第二日程应用中召开的第二日程，并且呈现第一信息包括：利用第一格式来呈现第一日程的第一信息，并且利用不同于第一格式的第二格式来呈现第二日程的第一信息。
根据本公开的一个示例性实现方式，预定区域位于显示区域的边缘，并且预定区域在客户端设备的运行期间始终被呈现。
根据本公开的一个示例性实现方式，第一信息包括用于提醒日程的日程图标，以及装置进一步包括：图标确定模块，被配置用于基于日程的时间段与当前时间之间的比较来确定日程图标。
图13示出了能够实施本公开的多个实现方式的设备1300的框图。应当理解，图13所示出的计算设备1300仅仅是示例性的，而不应当构成对本文所描述的实现方式的功能和范围的任何限制。图13所示出的计算设备1300可以用于实现上文描述的方法。
如图13所示，计算设备1300是通用计算设备的形式。计算设备1300的组件可以包括但不限于一个或多个处理器或处理单元1310、存储器1320、存储设备1330、一个或多个通信单元1340、一个或多个输入设备1350以及一个或多个输出设备1360。处理单元1310可以是实际或虚拟处理器并且能够根据存储器1320中存储的程序来执行各种处理。在多处理器系统中，多个处理单元并行执行计算机可执行指令，以提高计算设备1300的并行处理能力。
计算设备1300通常包括多个计算机存储介质。这样的介质可以是计算设备1300可访问的任何可以获得的介质，包括但不限于易失性和非易失性介质、可拆卸和不可拆卸介质。存储器1320可以是易失性存储器(例如寄存器、高速缓存、随机访问存储器(RAM))、非易失性存储器(例如，只读存储器(ROM)、电可擦除可编程只读存储器(EEPROM)、闪存)或它们的某种组合。存储设备1330可以是可拆卸或不可拆卸的介质，并且可以包括机器可读介质，诸如闪存驱动、磁盘或者任何其他介质， 其可以能够用于存储信息和/或数据(例如用于训练的训练数据)并且可以在计算设备1300内被访问。
计算设备1300可以进一步包括另外的可拆卸/不可拆卸、易失性/非易失性存储介质。尽管未在图13中示出，可以提供用于从可拆卸、非易失性磁盘(例如“软盘”)进行读取或写入的磁盘驱动和用于从可拆卸、非易失性光盘进行读取或写入的光盘驱动。在这些情况中，每个驱动可以由一个或多个数据介质接口被连接至总线(未示出)。存储器1320可以包括计算机程序产品1325，其具有一个或多个程序模块，这些程序模块被配置为执行本公开的各种实现方式的各种方法或动作。
通信单元1340实现通过通信介质与其他计算设备进行通信。附加地，计算设备1300的组件的功能可以以单个计算集群或多个计算机器来实现，这些计算机器能够通过通信连接进行通信。因此，计算设备1300可以使用与一个或多个其他服务器、网络个人计算机(PC)或者另一个网络节点的逻辑连接来在联网环境中进行操作。
输入设备1350可以是一个或多个输入设备，例如鼠标、键盘、追踪球等。输出设备1360可以是一个或多个输出设备，例如显示器、扬声器、打印机等。计算设备1300还可以根据需要通过通信单元1340与一个或多个外部设备(未示出)进行通信，外部设备诸如存储设备、显示设备等，与一个或多个使得用户与计算设备1300交互的设备进行通信，或者与使得计算设备1300与一个或多个其他计算设备通信的任何设备(例如，网卡、调制解调器等)进行通信。这样的通信可以经由输入/输出(I/O)接口(未示出)来执行。
根据本公开的示例性实现方式，提供了一种计算机可读存储介质，其上存储有计算机可执行指令，其中计算机可执行指令被处理器执行以实现上文描述的方法。根据本公开的示例性实现方式，还提供了一种计算机程序产品，计算机程序产品被有形地存储在非瞬态计算机可读介质上并且包括计算机可执行指令，而计算机可执行指令被处理器执行以实现上文描述的方法。根据本公开的示例性实现方式，提供了一种计算机程序产品，其上存储有计算机程序，程序被处理器执行时实现上文描述的方法。
这里参照根据本公开实现的方法、装置、设备和计算机程序产品的流程图和/或框图描述了本公开的各个方面。应当理解，流程图和/或框图的每个方框以及流程图和/或框图中各方框的组合，都可以由计算机可读程序指令实现。
这些计算机可读程序指令可以提供给通用计算机、专用计算机或其他可编程数据处理装置的处理单元，从而生产出一种机器，使得这些指令在通过计算机或其他可编程数据处理装置的处理单元执行时，产生了实现流程图和/或框图中的一个或多个方框中规定的功能/动作的装置。也可以把这些计算机可读程序指令存储在计算机可读存储介质中，这些指令使得计算机、可编程数据处理装置和/或其他设备以特定方式工作，从而，存储有指令的计算机可读介质则包括一个制造品，其包括实现流程图和/或框图 中的一个或多个方框中规定的功能/动作的各个方面的指令。
可以把计算机可读程序指令加载到计算机、其他可编程数据处理装置、或其他设备上，使得在计算机、其他可编程数据处理装置或其他设备上执行一系列操作步骤，以产生计算机实现的过程，从而使得在计算机、其他可编程数据处理装置、或其他设备上执行的指令实现流程图和/或框图中的一个或多个方框中规定的功能/动作。
附图中的流程图和框图显示了根据本公开的多个实现的系统、方法和计算机程序产品的可能实现的体系架构、功能和操作。在这点上，流程图或框图中的每个方框可以代表一个模块、程序段或指令的一部分，模块、程序段或指令的一部分包含一个或多个用于实现规定的逻辑功能的可执行指令。在有些作为替换的实现中，方框中所标注的功能也可以以不同于附图中所标注的顺序发生。例如，两个连续的方框实际上可以基本并行地执行，它们有时也可以按相反的顺序执行，这依所涉及的功能而定。也要注意的是，框图和/或流程图中的每个方框、以及框图和/或流程图中的方框的组合，可以用执行规定的功能或动作的专用的基于硬件的系统来实现，或者可以用专用硬件与计算机指令的组合来实现。
以上已经描述了本公开的各实现，上述说明是示例性的，并非穷尽性的，并且也不限于所公开的各实现。在不偏离所说明的各实现的范围和精神的情况下，对于本技术领域的普通技术人员来说许多修改和变更都是显而易见的。本文中所用术语的选择，旨在最好地解释各实现的原理、实际应用或对市场中的技术的改进，或者使本技术领域的其他普通技术人员能理解本文公开的各个实现方式。

Claims (16)

  1. 一种用于管理日程的方法，包括：
    确定在预定时间范围内是否存在日程；以及
    响应于确定在所述预定时间范围内存在日程，在客户端设备的显示区域中的预定区域中，呈现关于所述日程的第一信息。
  2. 根据权利要求1所述的方法，其中所述第一信息包括以下至少任一项：所述日程的名称、状态。
  3. 根据权利要求1所述的方法，进一步包括：响应于接收到来自所述客户端设备的用户与所述客户端设备的用户交互，呈现关于所述日程的第二信息，所述第二信息包括所述第一信息以外的其他信息。
  4. 根据权利要求1所述的方法，其中所述第二信息包括以下至少任一项：所述日程的名称、状态、开始时间、结束时间、地点、状态、用于参与所述日程的应用的信息。
  5. 根据权利要求4所述的方法，其中所述第二信息进一步包括：用于参与所述日程的入口控件。
  6. 根据权利要求5所述的方法，进一步包括：响应于接收到来自所述客户端设备的用户与所述入口控件的交互，
    启动用于参与所述日程的应用；以及
    引导所述用户在所述应用中加入所述日程。
  7. 根据权利要求6所述的方法，其中引导所述用户在所述应用中加入所述日程包括：
    确定所述用户在所述日程中的身份；以及
    基于所述身份来引导所述用户在所述应用中加入所述日程。
  8. 根据权利要求1所述的方法，其中确定所述日程包括：
    确定在所述客户端设备处安装的至少一个应用；以及
    从所述至少一个应用的日历中确定所述日程。
  9. 根据权利要求1所述的方法，进一步包括：
    呈现用于调整所述预定时间范围的调整控件；以及
    响应于接收到针对所述调整控件的交互，调整所述预定时间范围。
  10. 根据权利要求1所述的方法，进一步包括：响应于确定不存所述预定时间范围内的日程，在所述预定范围内呈现无日程的指示。
  11. 根据权利要求1所述的方法，其中所述日程包括：在第一应用中的第一日程 和在第二应用中的第二日程，并且呈现所述第一信息包括：
    利用第一格式来呈现所述第一日程的第一信息，并且利用不同于所述第一格式的第二格式来呈现所述第二日程的第一信息。
  12. 根据权利要求1所述的方法，其中所述预定区域位于所述显示区域的边缘，并且所述预定区域在所述客户端设备的运行期间始终被呈现。
  13. 根据权利要求1所述的方法，其中所述第一信息包括用于提醒所述日程的日程图标，以及所述方法进一步包括：
    基于所述日程的时间段与当前时间之间的比较来确定所述日程图标。
  14. 一种用于管理日程的设备，包括：
    确定模块，被配置用于确定在预定时间范围内是否存在日程；以及
    第一呈现模块，被配置用于响应于确定在所述预定时间范围内存在日程，在客户端设备的显示区域中的预定区域中，呈现关于所述日程的第一信息。
  15. 一种电子设备，包括：
    至少一个处理单元；以及
    至少一个存储器，所述至少一个存储器被耦合到所述至少一个处理单元并且存储用于由所述至少一个处理单元执行的指令，所述指令在由所述至少一个处理单元执行时使所述电子设备执行根据权利要求1至13中任一项所述的方法。
  16. 一种计算机可读存储介质，其上存储有计算机程序，所述计算机程序在被处理器执行时使所述处理器实现根据权利要求1至13中任一项所述的方法。
PCT/CN2024/130342 2023-11-07 2024-11-06 用于管理日程的方法、装置、设备和介质 Pending WO2025098413A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202311475789.1 2023-11-07
CN202311475789.1A CN119963152A (zh) 2023-11-07 2023-11-07 用于管理日程的方法、装置、设备和介质

Publications (1)

Publication Number Publication Date
WO2025098413A1 true WO2025098413A1 (zh) 2025-05-15

Family

ID=95597949

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2024/130342 Pending WO2025098413A1 (zh) 2023-11-07 2024-11-06 用于管理日程的方法、装置、设备和介质

Country Status (2)

Country Link
CN (1) CN119963152A (zh)
WO (1) WO2025098413A1 (zh)

Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101127994A (zh) * 2007-09-25 2008-02-20 中兴通讯股份有限公司 移动终端的日程表的显示方法
WO2016115774A1 (zh) * 2015-01-20 2016-07-28 宇龙计算机通信科技(深圳)有限公司 一种日程提醒方法及装置
CN106469365A (zh) * 2016-09-22 2017-03-01 北京小米移动软件有限公司 日程管理方法及装置
CN106873845A (zh) * 2015-12-12 2017-06-20 上海卓易科技股份有限公司 移动终端及其事件提醒方法
CN107343096A (zh) * 2017-06-30 2017-11-10 广东欧珀移动通信有限公司 信息提醒方法、装置、存储介质及电子设备
CN108197893A (zh) * 2018-01-10 2018-06-22 维沃移动通信有限公司 一种提醒方法及移动终端
CN113810540A (zh) * 2021-08-11 2021-12-17 荣耀终端有限公司 日程管理方法和终端设备
CN115225758A (zh) * 2021-04-19 2022-10-21 华为技术有限公司 通知方法、相关装置
CN116708653A (zh) * 2022-10-24 2023-09-05 荣耀终端有限公司 日程提醒方法及相关装置

Patent Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101127994A (zh) * 2007-09-25 2008-02-20 中兴通讯股份有限公司 移动终端的日程表的显示方法
WO2016115774A1 (zh) * 2015-01-20 2016-07-28 宇龙计算机通信科技(深圳)有限公司 一种日程提醒方法及装置
CN106873845A (zh) * 2015-12-12 2017-06-20 上海卓易科技股份有限公司 移动终端及其事件提醒方法
CN106469365A (zh) * 2016-09-22 2017-03-01 北京小米移动软件有限公司 日程管理方法及装置
CN107343096A (zh) * 2017-06-30 2017-11-10 广东欧珀移动通信有限公司 信息提醒方法、装置、存储介质及电子设备
CN108197893A (zh) * 2018-01-10 2018-06-22 维沃移动通信有限公司 一种提醒方法及移动终端
CN115225758A (zh) * 2021-04-19 2022-10-21 华为技术有限公司 通知方法、相关装置
CN113810540A (zh) * 2021-08-11 2021-12-17 荣耀终端有限公司 日程管理方法和终端设备
CN116708653A (zh) * 2022-10-24 2023-09-05 荣耀终端有限公司 日程提醒方法及相关装置

Also Published As

Publication number Publication date
CN119963152A (zh) 2025-05-09

Similar Documents

Publication Publication Date Title
US11755174B2 (en) Template based calendar events with graphic enrichment
US10872316B2 (en) Modern calendar system including free form input electronic calendar surface
US7251786B2 (en) Meeting information
RU2388049C2 (ru) Способ и система для усовершенствованного электронного управления задачами и их маркировки
Johnson GUI bloopers 2.0: common user interface design don'ts and dos
US20170277377A1 (en) Personal notes on a calendar item
US9508056B2 (en) Electronic note taking features including blank note triggers
US20190243879A1 (en) Embedded Action Card in Editable Electronic Document
US20050102607A1 (en) Method and system for setting document-linked timed reminders
WO2017205305A1 (en) Automatic task flow management across multiple platforms
CN117170550A (zh) 内容交互的方法、装置、设备和存储介质
CN101436271A (zh) 一种设置自动提醒的方法及装置
CN118642627B (zh) 用于信息展示的方法、装置、设备和存储介质
US20060277468A1 (en) System and method for dynamic, embedded help in software
KR20050048468A (ko) 액티브 어젠더
US20210294484A1 (en) Information processing system, user terminal, and method of processing information
WO2025098413A1 (zh) 用于管理日程的方法、装置、设备和介质
US20190108491A1 (en) Automatically maintaining a social media event database
WO2026001128A1 (zh) 用于信息处理的方法、装置、设备和存储介质
CN118708084A (zh) 用于信息交互的方法、装置、设备和存储介质
US11625155B2 (en) Information processing system, user terminal, method of processing information
US20260016948A1 (en) Systems and methods for morphable chat input with drag-to-private and drag-to-edit interactions
US20250370598A1 (en) Systems and methods for generating content
WO2025026227A1 (zh) 信息处理的方法、装置、设备和存储介质
WO2025107893A1 (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: 24888024

Country of ref document: EP

Kind code of ref document: A1