Schedule processing method and device and program product

Abstract

The invention discloses a schedule processing method and device and a program product, and the method comprises the steps: displaying a schedule management interface; the schedule is associated with at least two accounts; in response to a trigger operation for a session management control in the management interface, entering a session interface of a target session; the target session comprises the at least two accounts. According to the method, when the user checks or creates the schedule, the session interface related to the schedule can be seamlessly switched, switching among different applications is not needed, and the continuity and convenience of user experience are greatly improved.

Description

Technical Field

[0001] The present application relates to the field of data processing technology, and in particular to a schedule processing method, device and program product. Background Art

[0002] With the popularization of digital office, schedule management and conversation communication have become an indispensable part of the modern workplace. However, traditional office tools are often fragmented in these two aspects, and users need to switch between different platforms to complete schedules and instant messaging. This fragmented experience not only affects work efficiency, but also increases the complexity of user operations. Summary of the invention

[0003] In view of this, the embodiments of the present application at least provide a schedule processing method, device and program product.

[0004] The technical solution of the embodiment of the present application is implemented as follows:

[0005] On the one hand, an embodiment of the present application provides a schedule processing method, the method comprising: displaying a schedule management interface; the schedule is associated with at least two accounts; in response to a trigger operation on a session management control in the management interface, entering a session interface of a target session; the target session includes the at least two accounts.

[0006] On the other hand, an embodiment of the present application provides a schedule processing device, which includes: a first display module, used to display a schedule management interface; the schedule is associated with at least two accounts; a second display module, used to enter a session interface of a target session in response to a trigger operation on a session management control in the management interface; the target session includes the at least two accounts.

[0007] On the other hand, an embodiment of the present application provides a computer program product, including a computer program or instructions, which, when executed by a processor, implements some or all of the steps in the above method.

[0008] In the embodiment of the present application, since the schedule management and the session management are integrated into the same application (such as a calendar application), when viewing or creating a schedule, the user can seamlessly switch to the session interface related to the schedule without switching between different applications, which greatly improves the consistency and convenience of the user experience. At the same time, since the schedule is associated with at least two accounts, when entering the target session through the schedule management interface, the above at least two accounts also participate in the target session. In other words, the embodiment of the present application can bring together all participants of the schedule, which facilitates rapid communication and collaboration between team members, thereby improving the efficiency of team collaboration.

[0009] It should be understood that the above general description and the following detailed description are merely exemplary and explanatory, and are not intended to limit the technical solutions of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] The drawings herein are incorporated into the specification and constitute a part of the specification. These drawings illustrate embodiments consistent with the present application and are used together with the specification to illustrate the technical solution of the present application.

[0011] Figure 1 A schematic diagram of an implementation process of a schedule processing method provided in an embodiment of the present application Figure 1 ;

[0012] Figure 2A A schematic diagram of the overall interface of a calendar application provided in an embodiment of the present application;

[0013] Figure 2B A schematic diagram of the overall interface of another calendar application provided in an embodiment of the present application;

[0014] Figure 2C A schematic diagram of an interface of a management interface in an online conference scenario provided by an embodiment of the present application;

[0015] Figure 2D A schematic diagram of a conversation interface of a target conversation provided in an embodiment of the present application;

[0016] Figure 2E A state diagram of the session management control in a first display state provided by an embodiment of the present application;

[0017] Figure 2F A state diagram of the session management control in a second display state provided by an embodiment of the present application;

[0018] Figure 3A A second schematic diagram of an implementation flow of a schedule processing method provided in an embodiment of the present application;

[0019] Figure 3B A schematic diagram of a session configuration interface including contact book information provided in an embodiment of the present application;

[0020] Figure 3C A schematic diagram of a session configuration interface including historical session information provided in an embodiment of the present application;

[0021] Figure 4 Schematic diagram 3 of a schedule processing method for implementing the present application embodiment;

[0022] Figure 5 A schematic diagram of an implementation process of a schedule processing method provided in an embodiment of the present application Figure 4 ;

[0023] Figure 6 A schematic diagram of the structure of a schedule processing device provided in an embodiment of the present application;

[0024] Figure 7 A hardware entity diagram of a computer device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0025] In order to make the purpose, technical solutions and advantages of the present application clearer, the technical solutions of the present application are further elaborated in detail below in conjunction with the drawings and embodiments. The described embodiments should not be regarded as limiting the present application. All other embodiments obtained by ordinary technicians in the field without making creative work are within the scope of protection of the present application.

[0026] In the following description, reference is made to "some embodiments", which describe a subset of all possible embodiments, but it is understood that "some embodiments" may be the same subset or different subsets of all possible embodiments, and may be combined with each other without conflict. The terms "first / second / third" involved are merely used to distinguish similar objects and do not represent a specific order for the objects. It is understood that "first / second / third" may be interchanged in a specific order or sequence where permitted, so that the embodiments of the present application described herein can be implemented in an order other than that illustrated or described herein.

[0027] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as those commonly understood by those skilled in the art to which this application belongs. The terms used herein are only for the purpose of describing this application and are not intended to limit this application.

[0028] In the existing information-based office environment, schedule management and session management are two indispensable functional modules. Schedule management is mainly used to arrange individual or team schedule activities, such as meetings, appointments, work tasks, etc., to ensure that various affairs can be carried out on time. Session management is mainly used for instant communication and collaboration between team members, so that they can respond quickly when discussing issues, sharing information or coordinating work. However, in traditional office tools, these two functional modules are often independent of each other, and users need to frequently switch between different applications or interfaces to complete schedule scheduling and session discussions. This fragmented experience not only reduces work efficiency, but also increases users' operating costs.

[0029] In order to solve the above problems, the present application proposes a schedule processing method, which not only supports a variety of activity scenarios, but also realizes the connection between conversations and schedules, so that users can quickly complete tasks such as schedule scheduling, conversation discussions and team collaboration. The method can be executed by a processor of a computer device. Among them, the computer device may refer to a server, a laptop, a tablet computer, a desktop computer, a smart TV, a set-top box, a mobile device (such as a mobile phone, a portable video player, a personal digital assistant, a dedicated messaging device, a portable gaming device) and other devices with data processing capabilities.

[0030] Figure 1 A schematic diagram of an implementation process of a schedule processing method provided in an embodiment of the present application Figure 1 ,like Figure 1 As shown, the method includes the following steps S101 to S102:

[0031] Step S101, displaying a schedule management interface; the schedule is associated with at least two accounts.

[0032] In some embodiments, the management interface may be any interface of a calendar application. The management interface may be an interface recording schedule information or an interface for creating a schedule. The at least two accounts associated with the schedule are accounts participating in the schedule.

[0033] In some embodiments, the calendar interface of the calendar application can simultaneously display the schedule management interface and the preview interface of the schedule in the calendar. The preview interface is at least used to display the distribution of the schedule in a preset time period (such as one day, one week, or one year). In some embodiments, the preview interface can also display the schedule information of multiple accounts. The management interface is used to display the relevant information of the schedule, including but not limited to the schedule name, schedule time, user accounts participating in the schedule, etc.

[0034] like Figure 2A As shown, Figure 2AThe overall interface of the calendar application is shown. The calendar interface 210 may include a management interface 211 and a management interface 212. The management interface 212 is used to display the account schedule. For example, on January 1, 2030, user A is in a "busy state" from 9:00 to 10:00, user B is in a "busy state" from 10:00 to 11:00, and user C is in a "busy state" from 13:00 to 14:00. The management interface 211 is used to display the relevant information of the schedule. Taking the creation of a schedule as an example, for the period from 14:00 to 15:00 on January 1, 2030, the relevant information of the schedule can be configured in the management interface 211, for example, the "schedule name", "schedule time", "meeting minutes template", "add participants", "add meeting location", "add meeting materials", "reminder method", etc. can be configured.

[0035] In some embodiments, in response to a trigger operation on a target time interval in a calendar interface, a management interface based on the target time interval can be displayed. The target time interval in the calendar interface corresponds to a target schedule time and at least two accounts; the schedule time of the schedule in the management interface is the target schedule time; and the accounts participating in the schedule include the two accounts corresponding to the target time interval.

[0036] For example, see Figure 2A In response to the trigger operation on the target time area 213 in the management interface 212, the management interface 211 displays the management interface of the schedule corresponding to the target time area 213, wherein, since the target time area 213 is between 14:00 and 15:00 on January 1, 2030, the "schedule time" in the management interface 211 is automatically filled with the above time information; similarly, since the target time area 213 corresponds to user A, user B and user C, the "participants" in the management interface 211 are automatically filled with the above user A, user B and user C.

[0037] In other embodiments, the calendar interface of the calendar application may first display a preview interface of the schedule in the calendar, and in response to a trigger operation on the schedule, display a management interface of the schedule in a pop-up window.

[0038] like Figure 2B As shown, Figure 2B The overall interface of the calendar application is shown, and the calendar interface 220 may include a preview interface 221. The preview interface 221 may display calendar information, such as Figure 2BIn some embodiments, the management interface 223 also includes a "more options" control 224, which jumps to the "more options" control 224 in response to the trigger operation on the "more options" control 224. Figure 2A Calendar interface 210 is shown.

[0039] In some embodiments, the schedule can be associated with activities in real scenes; the activities that the schedule can be associated with may include, but are not limited to, at least one of the following: online activities; offline activities. The online activities may include, but are not limited to, at least one of the following: online meetings; online speeches; online interviews; online classes; online live broadcasts. The offline activities may include, but are not limited to: offline meetings, offline travel, offline speeches, offline interviews, offline classes, offline meetings, etc. Correspondingly, the at least two accounts associated with the schedule are accounts participating in activities in real scenes. Taking the activity as an online meeting as an example, the at least two accounts associated with the schedule are accounts for participating in the online meeting. In order to facilitate a full description of the embodiments of the present application, the embodiments are described below using the example of an online meeting associated with the schedule, and this example is not a limitation on the application scenario of the present application.

[0040] In some embodiments, the schedule management interface also includes an activity entry, and the activity entry is used to participate in the online activity pointed to by the schedule online. For example, if the online activity is an online meeting, the activity entry can be a link or meeting number for calling an online meeting application to enter the online meeting. Exemplarily, if the schedule is to display an online meeting, it can be supported by the meeting capabilities of a meeting component or a meeting application. The meeting component or meeting application can be a third-party component or a third-party application.

[0041] In some embodiments, the schedule management interface also includes activity settings. Assuming that the schedule is an online meeting, the management interface may support meeting settings, which may include setting the application used for the online meeting, setting the duration of the online meeting, setting the meeting number of the online meeting, etc.

[0042] See also Figure 2C , which shows a schematic diagram of the management interface in an online conference scenario. Figure 2CAs shown, in addition to the schedule-related information, the management interface 230 also includes an activity entry 231 and an activity setting 232. In response to a trigger operation on the activity entry 231, the video conference corresponding to the schedule can be directly entered through the conference component or conference application; in response to a trigger operation on the activity setting 232, the conference setting interface can be entered to set the application used for the online meeting, the duration of the online meeting, the meeting number of the online meeting, etc.

[0043] In some embodiments, the schedule management interface may also be used to display schedule information of the schedule; when creating schedule information of a schedule, it may include but is not limited to at least one of the following:

[0044] Create schedule information of the schedule based on the schedule creation template;

[0045] Access the text information input through the information input interface to create the schedule information. This method can be used to import information from third-party applications to quickly create schedules.

[0046] Establishing schedule information for a schedule based on one or more drop-down menus in a dialog box for creating a schedule;

[0047] The first account selects one or more time periods to create schedule information of a schedule in a schedule interface based on a schedule shared by one or more other accounts.

[0048] Step S102: In response to a trigger operation on a session management control in the management interface, entering a session interface of a target session; the target session includes the at least two accounts.

[0049] In some embodiments, the management interface further includes a session management control. After receiving a trigger operation for the session management control, the session interface corresponding to the target session may be entered; or the target session may be created and the session interface corresponding to the target session may be entered. The accounts participating in the target session include at least two accounts associated with the schedule. It is understandable that the target session is a session or discussion directly related to the schedule, and these sessions may include discussion, preparation, and follow-up of the schedule.

[0050] Exemplarily, if the accounts associated with the schedule include "User A", "User B" and "User C", accordingly, in the process of entering the session interface of the target session in response to the trigger operation of the session management control in the management interface, the target session also includes "User A", "User B" and "User C", that is, "User A", "User B" and "User C" are also participating users of the target session.

[0051] In some embodiments, the trigger operation is any user operation or a device operation performed by the electronic device based on a pre-configuration. For example, the trigger operation may be an operation such as a user clicking operation or a sliding operation to enter the session interface of the target session. Figure 2A The management interface 211 includes the session management control 214, namely the "conference group chat" control. Figure 2B The management interface 223 includes the session management control 225, namely the "conference group chat" control. Figure 2C The management interface 230 includes the session management control 233, namely the "conference group chat" control.

[0052] In some embodiments, the calendar application may be any application that supports date display. In some embodiments, the calendar application itself may also support conversations, that is, the calendar application itself has both schedule capabilities and conversation capabilities, so that the connection between conversations and schedules is achieved through the calendar application, thereby improving the intelligence of the calendar application and the user experience. In this case, the calendar application may include a schedule component with schedule capabilities and a conversation component that supports conversations. Exemplarily, the conversation capabilities may include but are not limited to instant messaging capabilities. In other embodiments, the calendar application may be a capability that supports calling a conversation application. In this case, the above-mentioned conversation management control is more of an application program interface that calls a conversation application, etc.

[0053] In some embodiments, the conversation interface can be displayed in the calendar interface in the above embodiments; the conversation interface can also be other interfaces independent of the calendar interface, management interface or preview interface; the conversation interface can also be displayed in the form of a floating window on the calendar interface, management interface or preview interface, which is not limited in this application.

[0054] See also Figure 2D , which shows a schematic diagram of a session interface of a target session. Figure 2D As shown, the conversation interface 240 at least provides a conversation area 241 for displaying chat messages of accounts participating in the target conversation.

[0055] In some embodiments, the target session is created based on schedule information of the schedule, wherein the schedule information includes but is not limited to account information, remarks information, attachment file information, etc. in the schedule.

[0056] In some embodiments, there is an association relationship between the files of the schedule and the target session, that is, the files of the schedule and the files of the target session can be synchronized through a preset synchronization mechanism. Exemplarily, after a new attachment file is added to the schedule, the new attachment file will be added to the target session; similarly, after a new file is added to the target session, the new file will be added to the schedule. In some implementation scenarios, the synchronized files are files in the shared file column in the target session. In the process of displaying the session interface of the target session, the session interface is also used to display the shared file column corresponding to the target session. Users can add files to the target session by dragging, clicking, etc., and then synchronize the new files to the schedule associated with the target session through the synchronization method provided in the above embodiments.

[0057] In the embodiment of the present application, since the schedule management and the session management are integrated into the same application (such as a calendar application), when viewing or creating a schedule, the user can seamlessly switch to the session interface related to the schedule without switching between different applications, which greatly improves the consistency and convenience of the user experience. At the same time, since the schedule is associated with at least two accounts, when entering the target session through the schedule management interface, the above at least two accounts also participate in the target session. In other words, the embodiment of the present application can bring together all participants of the schedule, which facilitates rapid communication and collaboration between team members, thereby improving the efficiency of team collaboration.

[0058] In some embodiments, when there is a target session associated with the schedule, the session management control is displayed in the management interface in a first display state; when there is no target session associated with the schedule, the session management control is displayed in the management interface in a second display state, and the first display state is different from the second display state.

[0059] Among them, the first display state is used to indicate that the schedule has an associated target session, and the second display state is used to indicate that the schedule does not have an associated target session. For example, it is assumed that there is a schedule "Project Meeting at 10 am on Monday" that has been associated with a session named "Project Preparation Discussion". In the management interface of the schedule, for the schedule "Project Meeting at 10 am on Monday", the session management control included in it can be displayed in the form of highlight, special icon or first preset text (such as the session identifier of the target session) (first display state), prompting the user that the schedule has an associated target session. For other schedules that are not associated with a session, their session management controls can be displayed in the form of ordinary, second preset text (such as creating a target session) (second display state), indicating that these schedules currently have no associated sessions.

[0060] See also Figure 2E and Figure 2F , Figure 2E A state diagram of the session management control in a first display state is shown. Figure 2F A state diagram of the session management control in the second display state is shown. Figure 2E As shown, at this time, the schedule has a target conversation associated with it, so the session management control 251 in the management interface 250 can be a control 2511 including the semantics of "entering the conference group chat", or a control 2512 displayed in a highlighted manner, or a control 2513 displayed with a "session icon". It can be seen that the above examples can intuitively reflect that the schedule has an associated target conversation; Figure 2F As shown, at this time, the schedule has no target conversation associated with it, so the session management control 261 in the management interface 260 can be a control 2611 including the semantics of "create conference group chat", or a control 2612 displayed normally (non-highlighted), or a control 2613 displayed with a "create icon". It can be seen that the above examples can intuitively reflect that the schedule has no associated target conversation. It should be noted that in the current embodiment, the management interface will only have one session management control in a display state at a time, that is, a schedule can have at most one target conversation associated with it.

[0061] In some other embodiments, a schedule may be associated with at least two target sessions, and in the current scenario, the management interface may simultaneously display the session management control in the first display state and the session management control in the second display state. The method further includes: in response to a trigger operation on the session management control in the first display state, if the schedule is associated with at least two target sessions, displaying a session selection interface including the at least two target sessions; in response to a selection operation on one of the at least two target sessions, displaying a session interface of the one target session. Accordingly, if the schedule is associated with the one target session, the session interface of the one target session is displayed.

[0062] In some embodiments, in response to determining the target session, the session management control is switched from the second display state to the first display state; in response to a triggering operation on the session management control in the second display state, a session interface of the target session is entered.

[0063] In some embodiments, the target session may be a private chat session or a group chat session.

[0064] In some embodiments, when a schedule is associated with at least two target sessions, these group sessions may be set up by department or region. For example, users in the same region are added to one target session and users in different regions are divided into different target sessions. Alternatively, users in one region are added to one target session and users in different regions are divided into different target sessions.

[0065] In some embodiments, when a schedule is associated with at least two target sessions, the target session is divided into a total session and sub-sessions. The total session may include users of all sub-sessions, while the sub-sessions may only include some users of the total session according to the sub-session establishment strategy.

[0066] Figure 3A This is a schematic diagram of a second implementation flow of a schedule processing method provided in an embodiment of the present application, which can be executed by a processor of a computer device. Figure 1 , Figure 1 Step S102 in can be updated to step S201 to step S202, combining Figure 3A The steps shown are explained.

[0067] Step S201: In response to a triggering operation on a session management control in a second display state, a session configuration interface for configuring the target session is displayed.

[0068] The second display state is used to indicate that there is no target session associated with the schedule. The session configuration interface is used for the user to select and configure a target session to be associated with the schedule.

[0069] In some embodiments, the interface may include a contact list option, a historical conversation list, a search function, etc., so that the user can quickly find the required account or conversation to facilitate the creation of the target conversation.

[0070] Step S202: In response to the configuration operation on the session configuration interface, determine the target session and enter the session interface of the target session.

[0071] In some embodiments, the configuration operation is an operation performed by a user on the session configuration interface, including but not limited to click, select, input, etc., and the configuration operation is at least used to set an account to participate in the target session. In other embodiments, the configuration operation can also be used to set session parameters related to the target session, such as the session name, session sending rules, etc.

[0072] Exemplarily, the user can perform operations on the session configuration interface, such as selecting an account in the address book, selecting a historical session, etc. For example, the user can select at least two accounts in the address book information and create a new session based on these accounts, or the user can select a historical session in the historical session information and use the historical session as the target session.

[0073] In some embodiments, the session configuration interface includes address book information; the above-mentioned response to the configuration operation on the session configuration interface to determine the target session can be implemented through steps S2021 and S2022.

[0074] Step S2021: In response to a configuration operation on the address book information in the session configuration interface, at least one target address book account is determined in the address book information.

[0075] In some embodiments, the address book information may include multiple address book accounts. In the embodiments of the present disclosure, by selecting the address book information, it is convenient for the user to select a participating account to participate in the target session. Displaying the address book information may include: displaying each address book account one by one; and may also include: displaying the address book information according to the organizational structure hierarchy.

[0076] Step S2022: Create the target session based on the at least one target address book account.

[0077] In some embodiments, a session including the at least one target address book account may be created as the target session. It is understandable that the at least one target address book account may be an account other than the first account. In the process of creating the target session, the target session needs to be constructed based on the first account and the at least one target address book account. In some embodiments, the target session also includes a robot account.

[0078] See also Figure 3B Schematic diagram of a session configuration interface including address book information is shown. The session configuration interface 310 is used to display the address book information. In some embodiments, the address book information may be a session for which the first account has management authority. Figure 3B As shown, the address book information included in the session configuration interface 310 includes six address book accounts owned by the first account, namely, "user B" to "user G". For example, for each address book account, the user avatar and user name of the address book account can be displayed through the session configuration interface 310. Of course, other user information can also be displayed, which will not be repeated here.

[0079] In some embodiments, the session configuration interface may further include a selection control corresponding to each of the address book accounts, and the selection control may be a display area where the address book account is located, or may be an independent control displayed near the address book account. Figure 3B As shown, if the user needs to select "User B" and "User C", he can click (an example of a triggering method, which can also be other operation types) the user names corresponding to "User B" and "User C", and can also click the user avatars corresponding to "User B" and "User C", and can also click the user selection controls 311 and 312 corresponding to "User B" and "User C". Through the above process, the target address book account can be determined from multiple address book accounts.

[0080] In some embodiments, in response to determining the target address book account in the address book information, the target address book account can be displayed on the session configuration interface, thereby facilitating the first account to confirm whether the selection is correct. Figure 3B As shown, the selected target address book accounts 314 ("user B" and "user C") can be displayed while the address book information is displayed.

[0081] In some embodiments, the session configuration interface may further include a search control for receiving input target user information, and then searching for a corresponding target contact account in multiple contact book accounts of the first account based on the input target session information. Figure 3B As shown, the session configuration interface 310 also includes a search control 313 .

[0082] In some embodiments, Figure 3B The session configuration interface shown may also include a confirmation control 315. After the target address book account 314 ("User B" and "User C") is determined, in response to a trigger operation on the confirmation control 315, the target address book account 314 ("User B" and "User C") is determined as the target session.

[0083] In some embodiments, the session configuration interface includes historical session information; the above-mentioned response to the configuration operation on the session configuration interface to determine the target session can be implemented through steps S2023 and S2024.

[0084] Step S2023: In response to the configuration operation on the historical session information in the session configuration interface, determine a target historical session in the historical session information.

[0085] Step S2024: Use the target historical session as the target session.

[0086] See also Figure 3CSchematic diagram of a session configuration interface including historical session information is shown. The session configuration interface 320 is used to display historical session information. In some embodiments, the historical session information may be a session for which the first account has management authority. Figure 3C As shown, the historical session information included in the session configuration interface 320 includes five historical sessions managed by the first account, namely, "session 1" to "session 5". For example, for each historical session, the session avatar and session name of the historical session can be displayed through the session configuration interface 320. Of course, other session information can also be displayed, which will not be repeated here.

[0087] In some embodiments, the session configuration interface may further include a selection control corresponding to each of the historical sessions, and the selection control may be a display area where the historical session is located, or may be an independent control displayed near the historical session. Figure 3C As shown, if the user needs to select "session 3", he can click (an example of a triggering method, which can also be other operation types) the session name "session 3", and can also click the session avatar corresponding to "session 3", and can also click the selection control 321 corresponding to "session 3". Through the above process, the target historical session can be determined from multiple historical sessions.

[0088] In some embodiments, in response to determining the target historical session in the historical session information, the target historical session can be displayed on the session configuration interface, thereby facilitating the first account to confirm whether the selection is correct. Figure 3C As shown, the selected target historical session 322 can be displayed while displaying the historical session information.

[0089] In some embodiments, the session configuration interface may further include a search control for receiving input target session information, and then searching for a corresponding target historical session in multiple historical sessions managed by the first account based on the input target session information. Figure 3C As shown, the session configuration interface 320 also includes a search control 323 .

[0090] In some embodiments, Figure 3C The session configuration interface shown may further include a confirmation control 324. After the target historical session 322 ("session 3") is determined, in response to a trigger operation on the confirmation control 324, the target historical session 322 ("session 3") is determined as the target session.

[0091] In some embodiments, the schedule is created by a first account; and the historical session information includes historical sessions for which the first account has management authority.

[0092] In an embodiment of the present application, a historical session may be a session for which the first account has management authority. The first account is the account that creates the schedule. In some embodiments, the session for which the first account has management authority may include at least one of the following: a historical session created by the first account; a historical session in which the first account participated and was granted management authority by other participating accounts.

[0093] If historical sessions for which the first account has management authority are displayed on the session configuration interface, unnecessary friction or privacy leakage caused by using historical sessions for which the first account has no management authority as target sessions can be reduced.

[0094] In some embodiments, the historical session may also be any historical session in which the first account has participated. For example, colleagues in the same department can create a session associated with the schedule based on the same group. In this case, the first account is not required to have management authority over the corresponding historical session, making the execution more flexible.

[0095] In other embodiments, if the historical session is a session that the first account can participate in but has no management authority, when the first account selects the historical session, it can send an application for authority to the management account of the historical session, and after the authority application is passed, the historical session can be used as the target session. If the authority application is not passed, a prompt message can be output to prompt a new session or a new session to be selected.

[0096] In some embodiments, the method further includes: in response to determining the target session, adjusting the account of the schedule based on the account participating in the target session.

[0097] Among them, based on the determined target session, at least one account corresponding to the target session (i.e., the account participating in the target session) can be obtained, and at least one account of the schedule (i.e., the account participating in the schedule, such as all the accounts participating in the online meeting) can be obtained; at least one account corresponding to the target session and at least one account of the schedule can be compared; accounts that exist in the target session but do not exist in the schedule (i.e., the account participating in the target session but not participating in the schedule) are added to the participating accounts of the schedule. In this way, the participating accounts of the target session and the schedule can be automatically synchronized.

[0098] In some embodiments, Figure 1 Step S102 in the method can also be updated to step S203.

[0099] Step S203: In response to a triggering operation on the session management control in the first display state, entering a session interface of the target session.

[0100] In the embodiment of the present application, when a schedule has an associated target session, the user clicks or touches the session management control in the first display state, and in response to the operation, the session interface of the target session is directly jumped to without reconfiguring. In this way, the user's work efficiency and convenience can be improved.

[0101] Figure 4 FIG3 is a schematic diagram of a method for implementing a schedule processing method provided in an embodiment of the present application, and the method can be executed by a processor of a computer device. Figure 1 The method may further include step S301, combining Figure 4 The steps shown are explained.

[0102] Step S301: managing member accounts participating in the target session based on participation in the schedule.

[0103] The participation status of the schedule includes the participation status of the user in the schedule, including information such as the second account participating in the schedule, the third account exiting the schedule, and the like.

[0104] In some embodiments, the target session also includes a robot account; the robot account is used to participate in the management of the target session.

[0105] In an embodiment of the present application, the robot account is a virtual account used to perform specific tasks (such as managing conversations, sending notifications, etc.). Generally speaking, compared to real users, the robot account does not have the identity characteristics of real users, but can simulate user behavior and perform automated operations. In some embodiments, the robot account may be an AI robot based on natural language processing. In some embodiments, the robot account is used to participate in the management of the target conversation, that is, based on the participation in the schedule, the management of the member accounts participating in the target conversation includes: based on the participation in the schedule, the robot account manages the member accounts participating in the target conversation.

[0106] In some embodiments, the member account may be an account participating in the target session. In some embodiments, the member account does not include the first account and the robot account.

[0107] In some embodiments, the above-mentioned participation status based on the schedule can be implemented through steps S3011 and S3012 to manage the member accounts participating in the target session.

[0108] Step S3011: If there is a second account participating in the schedule, add the second account to the target session.

[0109] In some embodiments, when creating a schedule, schedule information such as the time of the schedule can be set based on the schedule of the person to be involved, and an invitation to participate in the schedule can be initiated to the person to be involved based on point-to-point communication (or private chat) in the first account. Based on the response of the person to be involved to the invitation, it is determined whether the corresponding person participates in the schedule. If the person to be involved determines to participate in the schedule, the person to be involved is determined as the second account, and the second account is added to the target session.

[0110] Step S3012: If there is a third account that has exited the schedule, remove the third account from the target session.

[0111] In some embodiments, after the schedule is created and the corresponding target session is created, if there is a third account that has exited the schedule, the third account can be directly removed from the target session. Accordingly, the third account also exits the schedule.

[0112] In some embodiments, the second account may be added to the target session and the third account may be removed from the target session by the robot account.

[0113] For example, suppose there is an online meeting schedule, originally planned to be attended by user A, user B, and user C, and the target session corresponding to the online meeting schedule has been created. Before the meeting starts (or after the meeting starts), user D decides to join the meeting, but user C cannot attend for some reason. The robot account detects that user D has joined the meeting schedule and user C has exited the meeting schedule; at this time, the robot account automatically adds user D to the target session, so that users A, user B, and user D can communicate based on the target session; at the same time, the robot account removes user C from the meeting session, and the member list of the target session is updated to user A, user B, and user D.

[0114] In some embodiments, the method further includes: sending a reminder message in the target session according to the schedule progress of the first schedule.

[0115] The system can check the current status of the first schedule periodically or based on event triggers, including date, time, completed tasks, etc.; based on the progress of the schedule and preset reminder rules (such as 10 minutes before the start of the meeting, before the start of each discussion topic, etc.), determine whether a reminder message needs to be sent. This is crucial to maintaining the activity of the session and ensuring that members understand and participate in the schedule in a timely manner.

[0116] In some embodiments, the reminder information may be generated based on the specific time of the meeting start, the topic currently being discussed, materials to be prepared, etc. In the target session, the reminder information may be presented in the form of text, link, picture or voice message.

[0117] In some embodiments, the participants of the target session may respond to the reminder message, such as acknowledging receipt, asking questions, or providing feedback.

[0118] In some embodiments, when the robot account participates in the target conversation, the robot account can send reminder information to the members in the conversation according to the progress of the schedule; at the same time, the robot account can further process the feedback of the participating members on the reminder information, such as replying to confirm, answering questions or adjusting subsequent reminder strategies.

[0119] For example, assuming that the project meeting will start at 2 pm, the robot account will send a reminder message to all members through the target conversation 10 minutes before the meeting (that is, 1:50 pm): "Dear colleagues, the project meeting will start on time at 2 pm. Please enter the meeting room in advance and prepare relevant materials. If you have any questions or need assistance, please let me know at any time." Such a reminder function not only helps to ensure the smooth progress of the meeting, but also improves the collaboration efficiency and communication effectiveness among team members.

[0120] In some embodiments, the method further includes: based on the schedule information, using the first account or the robot account to reply to inquiries related to the schedule. In this way, it is equivalent to using the robot account to participate in the automatic maintenance of the schedule, which improves intelligence and user experience.

[0121] In some embodiments, the management interface is further used to display schedule information of the schedule; and the display status of the schedule information is used to represent the schedule progress of the schedule.

[0122] In some embodiments, the display status may include but is not limited to at least one of the following: display area; display font size; display layout; and information volume of displayed content.

[0123] Among them, the display status of the schedule information on the management interface can be controlled according to the schedule progress (completion status) of the schedule. On the one hand, it can be convenient for users to distinguish the completion status of the current schedule according to the display status. On the other hand, displaying the schedule information in accordance with the display status of the schedule completion status can enhance the user experience and the user's visual experience.

[0124] In some embodiments, the schedule information includes schedule identification information and schedule detail information; when the schedule progress indicates that the schedule has been completed, the schedule identification information is displayed and the schedule detail information is hidden; when the schedule progress indicates that the schedule has not been completed, the schedule identification information and the schedule detail information are displayed.

[0125] Among them, the schedule identification information is the basic identification information of the schedule, such as the name, number or date of the schedule, and the schedule representation information is used to quickly locate a specific schedule in the list; the schedule details information is a detailed description of the schedule, which may include detailed information such as the specific time, location, participants, and discussion topics of the schedule. The schedule details information is used to indicate the specific content and requirements of the schedule.

[0126] In the above embodiment, when the schedule progress indicates that the schedule has been completed, only the identification information of the schedule is displayed on the management interface, and the detailed information of the schedule is hidden. This can save interface space and let the user know that the schedule has ended and there is no need to view the detailed information. When the schedule progress indicates that the schedule is not completed, the identification information and detailed information of the schedule are displayed on the management interface at the same time. In this way, the user can not only quickly identify the schedule, but also directly view its specific content so as to make corresponding preparations or adjustments.

[0127] For example, suppose there is a project management platform, and its management interface lists meeting schedules for multiple projects. For completed meeting schedules, the interface may only display the name and date of the meeting (as identification information), and no longer expand to display detailed information such as the specific time, location, and participants of the meeting. On the contrary, for unfinished meeting schedules, the interface will display the name, date, and detailed information such as the specific meeting time, location, and participants, so that project members can prepare in advance.

[0128] The display logic provided by the above embodiment not only improves the information display efficiency of the management interface, but also enhances the user experience, so that users can more conveniently manage and track the meeting schedule of the project.

[0129] Figure 5 This is a schematic diagram of the implementation process of a schedule processing method provided in an embodiment of the present application. Figure 4 , the method can be executed by a processor of a computer device. Figure 1 The method further includes steps S401 to S403, combining Figure 5 The steps shown are explained.

[0130] Step S401: In the session interface, the schedule information of the schedule is sent to the target session.

[0131] In some embodiments, the schedule information of the schedule is sent to the target session in the form of text, picture or file. In some implementation scenarios, after sending the schedule information, all session members can be notified that the schedule information has been published so that participating members can discuss or provide feedback.

[0132] Step S402: Collecting the session records for the schedule information in the target session.

[0133] In some embodiments, the chat messages in the target session may be checked periodically or in real time, and the chat messages may be in the form of text, pictures, files, etc. Afterwards, the discussion content related to the schedule is identified through a preset semantic recognition algorithm (such as natural language processing and machine learning algorithms); the above discussion content related to the schedule is collected to form a session record for subsequent analysis.

[0134] Step S403: Adjust the schedule based on the conversation record.

[0135] In some embodiments, the collected conversation records can be analyzed to identify key information (such as time, location, topic, etc.) that needs to be adjusted in the schedule. Based on this information, the corresponding part of the schedule can be automatically modified.

[0136] In some embodiments, the modified schedule information may be synchronized to a schedule application or a schedule component; the adjusted schedule information may also be republished to the target session, and all members may be notified that the schedule has been adjusted.

[0137] In the above embodiment, the real-time communication feature of the conversation interface can be used to take the schedule information as the basis for discussion, and the schedule information can be dynamically adjusted by collecting the discussion content in the conversation. This method makes schedule management more flexible and real-time, and can respond to changes quickly.

[0138] For example, suppose a team is discussing the project review meeting next week through a target session, and the first account or robot account publishes the meeting schedule information in the target session, including the meeting time, location and topic; the accounts participating in the target meeting send relevant chat messages in the target meeting to discuss the specific arrangements of the meeting. The chat messages may include the need to adjust the meeting time to avoid other important activities, and may also include materials related to the topic. At this time, the discussion content and file sharing records related to the schedule information can be collected. The system uses natural language processing and machine learning technology to automatically analyze the collected session records, and then identify change requests or new suggestions for key information such as meeting time, location, and topic. Based on these analysis results, the adjusted meeting schedule information is generated, including the adjusted time, the newly added topic, and the relevant reference material links. Then, the adjusted schedule information can be republished to the target session through the first account or robot account.

[0139] In the embodiment of the present application, the schedule is directly discussed and adjusted through the conversation interface, which reduces the time cost of email exchanges and meeting arrangements; in addition, the schedule is adjusted based on the real-time discussion results to ensure the accuracy and timeliness of the schedule information.

[0140] In some embodiments, the method further comprises: in response to determining the target session, associating the target session with the schedule.

[0141] In an embodiment of the present application, after constructing the target session, an association relationship is established between the target session and the schedule. In this way, information sharing between the calendar function and the session function can be achieved based on the association relationship, so that the user can more conveniently obtain relevant information and reduce the need to switch between different applications or interfaces.

[0142] Wherein, associating the target session and the schedule includes at least one of the following: adding the schedule information of the schedule to the session information of the target session; adding the session information of the target session to the schedule information of the schedule; adding the schedule information of the schedule and the meeting information of the target session to the association information table.

[0143] In some embodiments, the schedule information can be added as an additional field or metadata to the session information of the target session. In other embodiments, the unique identifier (such as ID) of the schedule can also be used as a foreign key to the session information of the target session. In this way, when viewing or participating in a session, the user can immediately understand the detailed information of the schedule associated with it. The above schedule information can include but is not limited to the meeting topic, time, location, participants, etc.

[0144] In some embodiments, the session name, participant list, etc. in the target session can be added to the schedule information of the schedule associated with the target session. In this way, when the user views the schedule, in addition to the information of the schedule itself, he can also quickly understand the overview of the sessions related to it.

[0145] In some embodiments, in order to maintain the flexibility and scalability of data, the association information of the schedule and the target session can be stored in a special association information table. The association information table usually contains at least two fields: a schedule identifier and a session identifier. In some embodiments, the association information table does not belong to the session information or the schedule information, but the associated schedule identifier or session identifier can be queried based on the session identifier or the schedule identifier. Exemplarily, the association information table can be queried by a schedule application, a session application, a schedule component or a schedule component.

[0146] Based on the foregoing embodiments, an embodiment of the present application provides a schedule processing device, which includes the units included and the modules included in the units, which can be implemented by a processor in a computer device; of course, it can also be implemented by a specific logic circuit; in the implementation process, the processor can be a central processing unit (CPU), a microprocessor (MPU), a digital signal processor (DSP) or a field programmable gate array (FPGA), etc.

[0147] Figure 6 A schematic diagram of the structure of a schedule processing device provided in an embodiment of the present application is shown in FIG. Figure 6 As shown, the schedule processing device 600 includes: a first display module 610 and a second display module 620, wherein:

[0148] The first display module 610 is used to display a schedule management interface; the schedule is associated with at least two accounts;

[0149] The second display module 620 is used to enter the session interface of the target session in response to the trigger operation on the session management control in the management interface; the target session includes the at least two accounts.

[0150] In some embodiments, when there is a target session associated with the schedule, the session management control is displayed in the management interface in a first display state; when there is no target session associated with the schedule, the session management control is displayed in the management interface in a second display state, and the first display state is different from the second display state.

[0151] In some embodiments, the second display module 620 is further used to: in response to a trigger operation on a session management control in a second display state, display a session configuration interface for configuring the target session; the second display state is used to characterize that there is no target session associated with the schedule; in response to a configuration operation on the session configuration interface, determine the target session and enter the session interface of the target session.

[0152] In some embodiments, the session configuration interface includes address book information; the second display module 620 is also used to: determine at least one target address book account in the address book information in response to a configuration operation on the address book information in the session configuration interface; and create the target session based on the at least one target address book account.

[0153] In some embodiments, the session configuration interface includes historical session information; the second display module 620 is further used to: determine a target historical session in the historical session information in response to a configuration operation on the historical session information in the session configuration interface; and use the target historical session as the target session.

[0154] In some embodiments, the schedule is created by a first account; and the historical session information includes historical sessions for which the first account has management authority.

[0155] In some embodiments, the schedule processing device 600 further includes a data processing module. The data processing module is configured to adjust the account of the schedule based on the account participating in the target session in response to determining the target session.

[0156] In some embodiments, the second display module 620 is further configured to: enter a session interface of a target session in response to a triggering operation on the session management control in the first display state.

[0157] In some embodiments, the data processing module is further used to manage member accounts participating in the target session based on participation in the schedule.

[0158] In some embodiments, the data processing module is further used to: if there is a second account participating in the schedule, add the second account to the target session; if there is a third account that exits the schedule, remove the third account from the target session.

[0159] In some embodiments, the data processing module is further used to: send a reminder message in the target session according to the schedule progress of the first schedule.

[0160] In some embodiments, the management interface is further used to display schedule information of the schedule; and the display status of the schedule information is used to represent the schedule progress of the schedule.

[0161] In some embodiments, the schedule information includes schedule identification information and schedule detail information; when the schedule progress indicates that the schedule has been completed, the schedule identification information is displayed and the schedule detail information is hidden; when the schedule progress indicates that the schedule has not been completed, the schedule identification information and the schedule detail information are displayed.

[0162] In some embodiments, the second display module 620 is further used to: send the schedule information of the schedule to the target session in the session interface; collect the session record for the schedule information in the target session; and update the schedule based on the session record.

[0163] In some embodiments, the data processing module is further used to: in response to determining the target session, associate the target session with the schedule.

[0164] In some embodiments, associating the target session and the schedule includes at least one of the following: adding the schedule information of the schedule to the session information of the target session; adding the session information of the target session to the schedule information of the schedule; adding the schedule information of the schedule and the meeting information of the target session to an associated information table.

[0165] The description of the above device embodiment is similar to the description of the above method embodiment, and has similar beneficial effects as the method embodiment. In some embodiments, the functions or modules included in the device provided in the embodiment of the present application can be used to execute the method described in the above method embodiment. For technical details not disclosed in the device embodiment of the present application, please refer to the description of the method embodiment of the present application for understanding.

[0166] It should be noted that in the embodiment of the present application, if the above-mentioned schedule processing method is implemented in the form of a software function module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. Based on such an understanding, the technical solution of the embodiment of the present application is essentially or the part that contributes to the relevant technology can be embodied in the form of a software product, which is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the methods described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a U disk, a mobile hard disk, a read-only memory (ROM), a disk or an optical disk. In this way, the embodiment of the present application is not limited to any specific hardware, software or firmware, or any combination of hardware, software, and firmware.

[0167] An embodiment of the present application provides a computer device, including a memory and a processor, wherein the memory stores a computer program that can be run on the processor, and when the processor executes the program, some or all of the steps in the above method are implemented.

[0168] The embodiment of the present application provides a computer-readable storage medium on which a computer program is stored, and when the computer program is executed by a processor, some or all of the steps in the above method are implemented. The computer-readable storage medium can be transient or non-transient.

[0169] An embodiment of the present application provides a computer program, including a computer-readable code. When the computer-readable code is run in a computer device, a processor in the computer device executes some or all of the steps for implementing the above method.

[0170] The embodiment of the present application provides a computer program product, which includes a non-transitory computer-readable storage medium storing a computer program, and when the computer program is read and executed by a computer, some or all of the steps in the above method are implemented. The computer program product can be implemented specifically by hardware, software or a combination thereof. In some embodiments, the computer program product is specifically embodied as a computer storage medium, and in other embodiments, the computer program product is specifically embodied as a software product, such as a software development kit (SDK) and the like.

[0171] It should be noted here that the description of the various embodiments above tends to emphasize the differences between the various embodiments, and the same or similar aspects can be referenced to each other. The description of the above device, storage medium, computer program and computer program product embodiments is similar to the description of the above method embodiment, and has similar beneficial effects as the method embodiment. For technical details not disclosed in the embodiments of the device, storage medium, computer program and computer program product of this application, please refer to the description of the method embodiment of this application for understanding.

[0172] Figure 7 A hardware entity diagram of a computer device provided in an embodiment of the present application is shown in FIG. Figure 7 As shown, the hardware entity of the computer device 700 includes: a processor 701 and a memory 702, wherein the memory 702 stores a computer program that can be run on the processor 701, and the processor 701 implements the steps in the method of any of the above embodiments when executing the program.

[0173] The memory 702 stores computer programs that can be run on the processor. The memory 702 is configured to store instructions and applications executable by the processor 701. It can also cache data to be processed or processed by the processor 701 and various modules in the computer device 700 (for example, image data, audio data, voice communication data, and video communication data). This can be achieved through flash memory (FLASH) or random access memory (Random Access Memory, RAM).

[0174] When the processor 701 executes the program, the steps of any of the above-mentioned schedule processing methods are implemented. The processor 701 generally controls the overall operation of the computer device 700.

[0175] An embodiment of the present application provides a computer storage medium, which stores one or more programs. The one or more programs can be executed by one or more processors to implement the steps of the schedule processing method of any of the above embodiments.

[0176] It should be noted here that the description of the above storage medium and device embodiments is similar to the description of the above method embodiments, and has similar beneficial effects as the method embodiments. For technical details not disclosed in the storage medium and device embodiments of this application, please refer to the description of the method embodiments of this application for understanding.

[0177] The processor may be at least one of an Application Specific Integrated Circuit (ASIC), a Digital Signal Processor (DSP), a Digital Signal Processing Device (DSPD), a Programmable Logic Device (PLD), a Field Programmable Gate Array (FPGA), a Central Processing Unit (CPU), a controller, a microcontroller, and a microprocessor. It is understandable that the electronic device that implements the functions of the processor may also be other, and the embodiments of the present application are not specifically limited.

[0178] The above-mentioned computer storage medium / memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a magnetic random access memory (FRAM), a flash memory (Flash Memory), a magnetic surface memory, an optical disk, or a compact disc read-only memory (CD-ROM) and the like; it can also be various terminals including one or any combination of the above-mentioned memories, such as mobile phones, computers, tablet devices, personal digital assistants, etc.

[0179] It should be understood that "one embodiment" or "an embodiment" mentioned throughout the specification means that specific features, structures or characteristics related to the embodiment are included in at least one embodiment of the present application. Therefore, "in one embodiment" or "in an embodiment" appearing throughout the specification does not necessarily refer to the same embodiment. In addition, these specific features, structures or characteristics can be combined in one or more embodiments in any suitable manner. It should be understood that in various embodiments of the present application, the size of the serial number of each step / process mentioned above does not mean the order of execution, and the execution order of each step / process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiment of the present application. The serial numbers of the embodiments of the present application mentioned above are for description only and do not represent the advantages and disadvantages of the embodiments.

[0180] It should be noted that, in this article, the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the existence of other identical elements in the process, method, article or device including the element.

[0181] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. The device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as: multiple units or components can be combined, or can be integrated into another system, or some features can be ignored or not executed. In addition, the coupling, direct coupling, or communication connection between the components shown or discussed can be through some interfaces, and the indirect coupling or communication connection of the devices or units can be electrical, mechanical or other forms.

[0182] The units described above as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units; they may be located in one place or distributed on multiple network units; some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0183] In addition, all functional units in the embodiments of the present application can be integrated into one processing unit, or each unit can be a separate unit, or two or more units can be integrated into one unit; the above integrated unit can be implemented in the form of hardware or in the form of hardware plus software functional units. A person of ordinary skill in the art can understand that all or part of the steps of the above method embodiments can be completed by hardware related to program instructions, and the above program can be stored in a computer-readable storage medium. When the program is executed, the steps of the above method embodiments are executed; and the above storage medium includes: mobile storage devices, read-only memory (ROM), disks or optical disks, etc., which can store program codes.

[0184] Alternatively, if the above-mentioned integrated unit of the present application is implemented in the form of a software function module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application can essentially or in other words, the part that contributes to the relevant technology can be embodied in the form of a software product, which is stored in a storage medium and includes a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the methods described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as mobile storage devices, ROMs, magnetic disks, or optical disks.

[0185] The above is only an implementation method of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application.

Claims

1. A schedule processing method, characterized in that: The method comprises: A management interface for displaying a schedule; the schedule is associated with at least two accounts; In response to a trigger operation on a session management control in the management interface, a session interface of a target session is entered; the target session includes the at least two accounts.

2. The method according to claim 1, characterized in that When there is a target session associated with the schedule, the session management control is displayed in the management interface in a first display state; when there is no target session associated with the schedule, the session management control is displayed in the management interface in a second display state, and the first display state is different from the second display state.

3. The method according to claim 1 or 2, characterized in that: The step of entering a session interface of a target session in response to a triggering operation on a session management control in the management interface includes: In response to a triggering operation of a session management control for a second display state, displaying a session configuration interface for configuring the target session; the second display state is used to indicate that there is no target session associated with the schedule; In response to the configuration operation on the session configuration interface, the target session is determined, and the session interface of the target session is entered.

4. The method according to claim 3, characterized in that The session configuration interface includes address book information; The step of determining the target session in response to the configuration operation on the session configuration interface includes: In response to a configuration operation on the contact book information in the session configuration interface, determining at least one target contact book account in the contact book information; The target session is created based on the at least one target contact book account.

5. The method according to claim 3, characterized in that: The session configuration interface includes historical session information; and determining the target session in response to a configuration operation on the session configuration interface includes: In response to a configuration operation on the historical session information in the session configuration interface, determining a target historical session in the historical session information; The target historical session is used as the target session.

6. The method according to claim 3, characterized in that The method further comprises: In response to determining the target session, accounts of the schedule are adjusted based on accounts participating in the target session.

7. The method according to claim 2, characterized in that The step of entering a session interface of a target session in response to a triggering operation on a session management control in the management interface includes: In response to a triggering operation on the session management control in the first display state, a session interface of the target session is entered.

8. The method according to any one of claims 1 to 7, characterized in that: The method further comprises: Based on the participation in the schedule, member accounts participating in the target session are managed.

9. The method according to claim 8, characterized in that The managing the member accounts participating in the target session based on the participation in the schedule includes: If there is a second account participating in the schedule, adding the second account to the target session; If there is a third account that has exited the schedule, the third account is removed from the target session.

10. The method according to any one of claims 1 to 9, characterized in that: The method further comprises: According to the schedule progress of the first schedule, a reminder message is sent in the target session.

11. The method according to any one of claims 1 to 10, characterized in that: The management interface is also used to display the schedule information of the schedule; the display status of the schedule information is used to represent the schedule progress of the schedule.

12. The method according to claim 11, characterized in that The schedule information includes schedule identification information and schedule details information; when the schedule progress indicates that the schedule has been completed, the schedule identification information is displayed and the schedule details information is hidden; When the schedule progress indicates that the schedule is not completed, the schedule identification information and the schedule detail information are displayed.

13. The method according to any one of claims 1 to 12, characterized in that: The method further comprises: In the session interface, sending the schedule information of the schedule to the target session; Collecting a session record for the schedule information in the target session; The schedule is adjusted based on the conversation record.

14. The method according to any one of claims 1 to 13, characterized in that: The method further comprises: In response to determining the target session, associating the target session with the schedule; The associating the target session with the schedule includes at least one of the following: adding schedule information of the schedule to session information of the target session; adding the session information of the target session to the schedule information of the schedule; The schedule information of the schedule and the meeting information of the target session are added to the associated information table.

15. A schedule processing device, characterized in that: The device comprises: A first display module, used to display a schedule management interface; the schedule is associated with at least two accounts; The second display module is used to enter the session interface of the target session in response to the trigger operation of the session management control in the management interface; the target session includes the at least two accounts.

16. A computer program product comprising a computer program or instructions, characterized in that When the computer program or instruction is executed by a processor, the steps in the method according to any one of claims 1 to 14 are implemented.

Images