Meeting Time Recommendation Method, Device, Computer Equipment and Storage Medium

Abstract

This application relates to the fields of computer technology and cloud computing, and relates to a method, device, computer equipment and storage medium for recommending meeting time. The method includes: receiving a meeting addition request for a target meeting; obtaining the to-be-processed schedule information of each meeting member specified in the meeting addition request; performing an overlap analysis on the time periods corresponding to the schedule information of each meeting member; if there are idle time periods without overlap, recommending a meeting time period for the target meeting from the idle time periods; if there are no such idle time periods, recommending a meeting time period for the target meeting from the overlapping non-idle time periods according to the degree of overlap between the time periods corresponding to each schedule information. Using this method can improve the efficiency of adding meetings.

Description

Technical Field

[0001] This application relates to the field of computer technology, and particularly to a meeting time recommendation method, apparatus, computer device, and storage medium. Background Art

[0002] With the development of science and technology, cloud computing has developed rapidly. The emergence of cloud computing will drive a revolutionary change in the entire Internet mode and enterprise management mode in concept. Enterprise office systems have emerged as the times require. More and more enterprises start to work online, and adding meetings by arranging meeting times online is one of the applications. In this application, it is very important to arrange meeting times quickly and ensure the rationality of meeting times.

[0003] In traditional methods, generally, the person arranging the meeting arranges the meeting time and adds the meeting by himself / herself. If the arranged meeting time conflicts with the time of the things planned or arranged by the meeting members, it is necessary to communicate with each meeting member separately, and manually adjust the meeting time repeatedly according to the conflict situation between the times of the things planned or arranged by each meeting member to ensure the rationality of the meeting time. However, such a method of manually communicating the meeting time is time-consuming and laborious, and the efficiency is very low. Summary of the Invention

[0004] Based on this, in view of the above technical problems, it is necessary to provide a meeting time recommendation method, apparatus, computer device, and storage medium that can improve the efficiency of adding meetings.

[0005] A meeting time recommendation method, the method includes:

[0006] Receiving a meeting addition request for a target meeting;

[0007] Obtaining the to-be-processed schedule information of each meeting member specified in the meeting addition request;

[0008] Performing an overlap analysis on the time periods corresponding to the schedule information of each meeting member;

[0009] If there are non-overlapping idle time periods, recommending a meeting time period for the target meeting from the idle time periods;

[0010] If there are no such idle time periods, then

[0011] Recommending a meeting time period for the target meeting from the overlapping non-idle time periods according to the degree of overlap between the time periods corresponding to each schedule information.

[0012] In one embodiment, the obtaining the to-be-processed schedule information of each meeting member specified in the meeting addition request includes:

[0013] Obtain a timeline with schedule information added;

[0014] From the schedule information added on the timeline, obtain the pending schedule information of each meeting member specified in the meeting addition request;

[0015] The overlapping analysis of the time periods corresponding to the schedule information of each meeting member includes:

[0016] Determine the time period corresponding to the obtained schedule information on the timeline;

[0017] Conduct an overlapping analysis on the determined time periods.

[0018] In one embodiment, the overlapping analysis of the determined time periods includes:

[0019] Exhaustively divide the determined time periods into pairs;

[0020] Compare the respective time points corresponding to the two time periods in each pair in sequence;

[0021] Determine the time period composed of the time points with consistent comparison results as the overlapping non-idle time period, and determine the time period on the timeline other than the non-idle time period as the non-overlapping idle time period.

[0022] In one embodiment, the overlapping analysis of the determined time periods includes:

[0023] Add the start time points of the determined time periods to the first set;

[0024] Add the end time points of the determined time periods to the second set;

[0025] Sequentially select the current time period from the determined time periods. For each current time period, select a candidate start time point from the first set and a candidate end time point from the second set; wherein, the candidate start time point is less than or equal to the end time point of the current time period; the candidate end time point is greater than or equal to the start time point of the current time period;

[0026] Select the time period corresponding to the candidate start time point and the candidate end time point from the determined time periods other than the current time period, and determine it as the non-idle time period overlapping with the current time period;

[0027] Determine the time period on the timeline other than the non-idle time period corresponding to the determined time periods as the non-overlapping idle time period.

[0028] In one embodiment, the meeting addition request includes the meeting duration of the target meeting; the recommending the meeting time period of the target meeting from the idle time periods if there are non-overlapping idle time periods includes:

[0029] If there are non-overlapping idle time periods that meet the meeting duration, recommend the meeting time period of the target meeting from the idle time periods that meet the meeting duration;

[0030] The recommending the meeting time period of the target meeting from the overlapping non-idle time periods according to the overlapping degree between the time periods corresponding to each schedule information if there are no such idle time periods includes:

[0031] If there are no idle time periods that meet the meeting duration, recommend the meeting time period of the target meeting that meets the meeting duration from the overlapping non-idle time periods according to the overlapping degree between the time periods corresponding to each schedule information.

[0032] In one embodiment, the target meeting is a team meeting, and the method further includes:

[0033] Obtain the meeting times of all historical meetings of the team corresponding to the team meeting;

[0034] Predict the meeting time preference of the team according to the obtained meeting times of the historical meetings;

[0035] The recommending the meeting time period of the target meeting from the idle time periods includes:

[0036] Recommend the meeting time period of the target meeting from the idle time periods according to the meeting time preference.

[0037] In one embodiment, the meeting addition request includes the target meeting type of the target meeting;

[0038] The obtaining the meeting times of all historical meetings of the team corresponding to the team meeting includes:

[0039] For the team corresponding to the team meeting, obtain the meeting times of the historical meetings that the team participates in and belong to the target meeting type;

[0040] The predicting the meeting time preference of the team according to the obtained meeting times of the historical meetings includes:

[0041] Predict the meeting time preference of the team for the meetings of the target meeting type according to the obtained meeting times of the historical meetings.

[0042] In one embodiment, the recommending the meeting time period of the target meeting from the overlapping non-idle time periods according to the overlapping degree between the time periods corresponding to each of the schedule information includes:

[0043] Sorting each of the overlapping non-idle time periods in ascending order of the overlapping degree according to the overlapping degree between the time periods corresponding to each of the schedule information;

[0044] Recommending the meeting time period of the target meeting according to the previous preset number of the non-idle time periods.

[0045] In one embodiment, the schedule information includes a meeting schedule;

[0046] The recommending the meeting time period of the target meeting from the overlapping non-idle time periods according to the overlapping degree between the time periods corresponding to each of the schedule information includes:

[0047] Recommending the meeting time period of the target meeting from the overlapping non-idle time periods according to the overlapping degree between the time periods corresponding to each of the meeting schedules and the priority of the meeting corresponding to the meeting schedule.

[0048] In one embodiment, the recommending the meeting time period of the target meeting from the overlapping non-idle time periods according to the overlapping degree between the time periods corresponding to each of the meeting schedules and the priority of the meeting corresponding to the meeting schedule includes:

[0049] Sorting each of the non-idle time periods in ascending order of the overlapping degree according to the overlapping degree between the time periods corresponding to each of the meeting schedules;

[0050] Eliminating the non-idle time periods whose corresponding meeting priorities meet the time period locking condition from the sorted non-idle time periods according to the priority of the meeting corresponding to each of the non-idle time periods;

[0051] Selecting the previous preset number of non-idle time periods from the remaining non-idle time periods after elimination;

[0052] Recommending the meeting time period of the target meeting according to the selected non-idle time periods.

[0053] In one embodiment, the target meeting is a team meeting, and the recommending the meeting time period of the target meeting according to the selected non-idle time periods includes:

[0054] Obtaining the meeting time preference of the team corresponding to the target meeting;

[0055] Recommend a meeting time period for the target meeting from the selected non - idle time periods according to the meeting time preference.

[0056] In one embodiment, the meeting addition request includes the recommended meeting duration; the target meeting is a team meeting.

[0057] Before receiving the meeting addition request for the target meeting, the method further includes:

[0058] Determine the meeting duration preference of the team corresponding to the team meeting according to the meeting durations of the historical meetings of the team.

[0059] Recommend the meeting duration of the target meeting according to the meeting duration preference.

[0060] A meeting time recommendation device, the device includes:

[0061] A request receiving module, configured to receive a meeting addition request for a target meeting.

[0062] A schedule information acquisition module, configured to acquire the to - be - processed schedule information of each meeting member specified in the meeting addition request.

[0063] An overlap analysis module, configured to perform an overlap analysis on the time periods corresponding to the schedule information of each meeting member.

[0064] A meeting time recommendation module, configured to recommend a meeting time period for the target meeting from the idle time periods if there are non - overlapping idle time periods.

[0065] The meeting time recommendation module is further configured to, if there are no such idle time periods, recommend a meeting time period for the target meeting from the overlapping non - idle time periods according to the degree of overlap between the time periods corresponding to each schedule information.

[0066] A computer device includes a memory and a processor. When a computer program stored in the memory is executed by the processor, the processor executes the steps in the meeting time recommendation method described in the embodiments of the present application.

[0067] A computer - readable storage medium has a computer program stored thereon. When the computer program is executed by a processor, the processor executes the steps in the meeting time recommendation method described in the embodiments of the present application.

[0068] A computer program product or computer program, the computer program product or computer program comprising computer instructions stored in a computer-readable storage medium; a processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, such that the computer device executes the steps in the interaction method based on a shared storage space described in the embodiments of the present application.

[0069] In the above meeting time recommendation method, device, computer device and storage medium, the to-be-processed schedule information of each meeting member specified in the meeting addition request is obtained, and then overlapping analysis is performed on the time periods corresponding to the schedule information of each meeting member, so as to automatically determine whether there is an idle time period between the time periods of the schedule information of each meeting member. If there is an idle time period without overlap, a meeting time period of the target meeting is recommended from the idle time periods, so that the idle time period can be quickly recommended without communicating with each meeting member, and the meeting time can be arranged efficiently; if there is no idle time period, a meeting time period of the target meeting is recommended from the overlapping non-idle time periods according to the overlapping degree between the time periods corresponding to each schedule information. In this way, when there is no idle time period, the meeting time period can be automatically recommended from the non-idle time periods according to the overlapping degree without communicating with each meeting member separately, and the meeting time can be arranged efficiently, thereby improving the efficiency of meeting addition. BRIEF DESCRIPTION OF THE DRAWINGS

[0070] Figure 1 It is an application environment diagram of the meeting time recommendation method in one embodiment;

[0071] Figure 2 It is a schematic flowchart of the meeting time recommendation method in one embodiment;

[0072] Figure 3 It is a schematic diagram of the principle of determining overlapping time periods in one embodiment;

[0073] Figure 4 It is a schematic diagram of the principle of determining the time periods overlapping with the current time period in one embodiment;

[0074] Figure 5 It is a schematic overall flowchart of the meeting time recommendation method in one embodiment;

[0075] Figure 6 It is a timing diagram of the meeting time recommendation method in one embodiment;

[0076] Figure 7 It is a structural block diagram of the meeting time recommendation device in one embodiment;

[0077] Figure 8 It is a structural block diagram of the meeting time recommendation device in another embodiment;

[0078] Figure 9 is the internal structure diagram of a computer device in an embodiment;

[0079] Figure 10 is the internal structure diagram of a computer device in another embodiment. Detailed implementation manners

[0080] In order to make the objectives, technical solutions and advantages of the present application more clear and understandable, the present application will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0081] The meeting time recommendation method provided by the present application can be applied to an application environment as Figure 1 shown. Among them, the terminal 102 communicates with the server 104 through a network. The terminal 102 can be a smart phone, a tablet computer, a laptop computer, a desktop computer, a smart speaker, a smart watch, etc., but is not limited thereto. The server 104 can be an independent physical server, or a server cluster or a distributed system composed of multiple physical servers. It can also be a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms. The terminal 102 and the server 104 can be directly or indirectly connected through wired or wireless communication methods, and the present application does not make any restrictions here.

[0082] Specifically, the terminal 102 can display a graphical interface, and generate a meeting addition request for a target meeting according to the meeting addition operation of the user 106 in the graphical interface, and send the meeting addition request to the server 104. The server 104 can, in response to the meeting addition request, obtain the schedule information of each meeting member from the database 108, perform overlap analysis, recommend the meeting time period of the target meeting, and send the recommended meeting time period of the target meeting to the terminal 102, and the terminal 102 can display the recommended meeting time period of the target meeting.

[0083] Among them, cloud computing is a computing model that distributes computing tasks on a resource pool composed of a large number of computing devices, enabling various application systems to obtain computing power, storage space, and information services as needed. The network that provides resources is called the "cloud". As a basic capability provider of cloud computing, a cloud computing resource pool (referred to as a cloud platform, generally called an IaaS (Infrastructure as a Service) platform) will be established, and various types of virtual resources will be deployed in the resource pool for external customers to select and use.

[0084] In one embodiment, the meeting time recommendation method of the present application can be implemented using artificial intelligence technology. For example, the overlapping analysis of the time periods corresponding to the schedule information of each meeting member can be implemented using artificial intelligence technology.

[0085] Artificial Intelligence (AI) is a theory, method, technology, and application system that uses digital computers or machines controlled by digital computers to simulate, extend, and expand human intelligence, perceive the environment, acquire knowledge, and use knowledge to obtain the best results. In other words, artificial intelligence is a comprehensive technology in computer science that attempts to understand the essence of intelligence and produce a new intelligent machine that can react in a way similar to human intelligence. Artificial intelligence also studies the design principles and implementation methods of various intelligent machines, enabling the machines to have the functions of perception, reasoning, and decision-making.

[0086] Artificial intelligence technology is an interdisciplinary subject with a wide range of fields, including both hardware-level technologies and software-level technologies. The basic technologies of artificial intelligence generally include technologies such as sensors, dedicated artificial intelligence chips, cloud computing, distributed storage, big data processing technology, operation / interaction systems, and mechatronics. The software technologies of artificial intelligence mainly include several major directions such as computer vision technology, speech processing technology, natural language processing technology, and machine learning / deep learning.

[0087] In one embodiment, the meeting time recommendation method of the present application can be implemented using blockchain technology. For example, the schedule information of each meeting member can be stored in the nodes of the blockchain to prevent the schedule information from being tampered with and improve data security.

[0088] Blockchain is a new application model of computer technologies such as distributed data storage, peer-to-peer transmission, consensus mechanism, and encryption algorithms. Blockchain, in essence, is a decentralized database, a string of data blocks generated by using cryptographic methods. Each data block contains information about a batch of network transactions, which is used to verify the validity (anti-counterfeiting) of the information and generate the next block. Blockchain can include the blockchain underlying platform, the platform product service layer, and the application service layer.

[0089] The underlying blockchain platform may include processing modules such as user management, basic services, smart contracts, and operation monitoring. Among them, the user management module is responsible for the identity information management of all blockchain participants, including maintaining the generation of public and private keys (account management), key management, and maintaining the correspondence between the real identity of users and blockchain addresses (permission management). And under authorized circumstances, it supervises and audits the transaction situations of certain real identities, and provides rule configuration for risk control (risk control audit); the basic service module is deployed on all blockchain node devices, used to verify the validity of business requests, and record them on the storage after consensus for valid requests. For a new business request, the basic service first performs interface adaptation parsing and authentication processing (interface adaptation), then encrypts the business information through a consensus algorithm (consensus management), transmits it to the shared ledger completely and consistently after encryption (network communication), and performs record storage; the smart contract module is responsible for the registration and issuance of contracts, as well as contract triggering and contract execution. Developers can define contract logic through a certain programming language, publish it to the blockchain (contract registration), trigger the execution according to the logic of contract terms by calling keys or other events, complete the contract logic, and at the same time provide functions for contract upgrade and cancellation; the operation monitoring module is mainly responsible for the deployment, configuration modification, contract setting, cloud adaptation during the product release process, and visual output of the real-time status during product operation, such as: alarm, monitoring network conditions, monitoring the health status of node devices, etc.

[0090] The platform product service layer provides the basic capabilities and implementation frameworks of typical applications. Developers can build on these basic capabilities and overlay the characteristics of the business to complete the blockchain implementation of the business logic. The application service layer provides application services based on the blockchain solution for business participants to use.

[0091] In one embodiment, as Figure 2 shown, a meeting time recommendation method is provided. This meeting time recommendation method can be executed by a server or a terminal, or jointly executed by a terminal and a server. In this embodiment of the application, this method is applied to Figure 1 the server in as an example for illustration, including the following steps:

[0092] S202, receive a meeting addition request for a target meeting.

[0093] Among them, the target meeting is the meeting to be added. The meeting addition request is used to request the addition of the target meeting.

[0094] In one embodiment, adding the target meeting may be adding the target meeting to the schedule information, that is, adding a meeting schedule.

[0095] In one embodiment, the target meeting can be an offline meeting or an online meeting. In one embodiment, the online meeting can be any one of a video meeting, a voice meeting, etc.

[0096] In one embodiment, the target meeting can be a team meeting or a non-team meeting. Among them, a team meeting refers to a meeting held by members belonging to the same team. A non-team meeting refers to a meeting held by members who do not jointly belong to the same team. For example: In an enterprise scenario, a team meeting can refer to a meeting held by members belonging to any one of the same project team, department, or group, etc. A non-team meeting can refer to a meeting held by members who do not jointly belong to the same team. For example, a new employee meeting is a non-team meeting because these new employees may not belong to the same team.

[0097] Specifically, the user (i.e., the meeting adder) can perform a meeting addition operation for the target meeting through the graphical interface of the terminal. The terminal can generate a meeting addition request for the target meeting according to the user's meeting addition operation and send the meeting addition request to the server. The server can receive the meeting addition request sent by the terminal through the network.

[0098] In one embodiment, the meeting addition request may include at least one of the meeting venue information, meeting member information, meeting duration, meeting type, and priority, etc. of the target meeting.

[0099] In one embodiment, the user can set at least one of the meeting venue information, meeting member information, meeting duration, meeting type, and priority, etc. of the target meeting through the graphical interface of the terminal to perform the meeting addition operation. The terminal can generate a meeting addition request for the target meeting according to the user's meeting addition operation, and the generated meeting addition request may include the user's setting results.

[0100] S204, obtain the to-be-processed schedule information of each meeting member specified in the meeting addition request.

[0101] Among them, a meeting member is a member who needs to attend the target meeting. Schedule information refers to a plan or arrangement for a time period. The to-be-processed schedule information refers to the schedule information that has not been processed currently.

[0102] In one embodiment, the things planned or arranged by the schedule information may include at least one of attending a meeting, handling work tasks, or other affairs, etc. For example: The schedule information can be attending a project meeting from 9:00 to 12:00 on December 14th, or meeting a client from 14:00 to 15:00 on December 15th, etc.

[0103] It can be understood that if the event planned or arranged in the schedule information is to attend a meeting, then the schedule information is the meeting schedule. It can be understood that the successfully added target meeting will also be recorded in the schedule information.

[0104] In one embodiment, the event planned or arranged in the added schedule information can be relatively important and it is difficult to spare time from this event to attend a meeting. For example, having a meeting or meeting a client belongs to the event where it is difficult to spare time to attend a meeting. Another example is dealing with an unimportant work task, which does not belong to the event where it is difficult to spare time to attend a meeting and thus does not need to be added to the schedule information. In other embodiments, any thing that one wants to note can also be added to the schedule information regardless of the importance of the schedule information.

[0105] Specifically, each meeting member can pre-add their own schedule information, and the server can store the pre-added schedule information. When the user triggers a meeting addition request through a meeting addition operation, the user can specify the meeting members who need to attend the target meeting. The server can determine the meeting members specified in the meeting addition request, and then obtain the pending schedule information of the specified meeting members from the pre-stored schedule information.

[0106] In one embodiment, in an enterprise scenario, each member in the enterprise can add their own schedule information, or each member in the enterprise's team can add their own schedule information. The server can store the pre-added schedule information. The server can obtain the pending schedule information of the meeting members specified in the meeting addition request from the pre-stored schedule information of each member in the enterprise or each member in the team.

[0107] In one embodiment, the schedule information of the meeting members can be stored in a database. The server can obtain the pending schedule information of the meeting members specified in the meeting addition request from the database.

[0108] In one embodiment, the server can record the pre-added schedule information on the timeline.

[0109] S206. Perform an overlap analysis on the time periods corresponding to the schedule information of each meeting member.

[0110] Among them, the overlap analysis refers to analyzing the overlap situation between each time period.

[0111] Specifically, the server can determine the time periods corresponding to the pending schedule information of each meeting member according to the obtained pending schedule information of each meeting member, and then perform an overlap analysis on the determined time periods.

[0112] In one embodiment, the server may first determine the overlapping time periods between each time period, use the determined overlapping time periods as non-idle time periods, and determine the time periods other than the overlapping time periods as non-overlapping idle time periods.

[0113] S208, if there are non-overlapping idle time periods, recommend the meeting time period of the target meeting from the idle time periods.

[0114] In one embodiment, the server may recommend the meeting time period of the target meeting from the non-overlapping idle time periods.

[0115] In another embodiment, if the meeting addition request does not include the meeting duration, the server may obtain a preset meeting duration threshold. The server may determine the non-overlapping idle time periods with a duration greater than or equal to the meeting duration threshold as the final idle time periods, and then recommend the meeting time period of the target meeting from the final idle time periods.

[0116] In other embodiments, if the meeting addition request includes the meeting duration, the server may determine the non-overlapping idle time periods that meet the meeting duration as the final idle time periods, and then recommend the meeting time period of the target meeting from the final idle time periods.

[0117] In one embodiment, if there is one idle time period, the server may use this idle time period as the meeting time period of the recommended target meeting.

[0118] In another embodiment, if there are multiple idle time periods, the server may select some or all of the idle time periods according to a preset recommendation rule as the meeting time period of the recommended target meeting.

[0119] In one embodiment, if there are multiple idle time periods, the server may obtain the meeting time preference, and according to the meeting time preference, recommend the meeting time period of the target meeting from the idle time periods. The meeting time preference is used to represent the preferred meeting time. That is, it can reflect which time periods are more preferred for holding meetings.

[0120] In one embodiment, the server may determine the meeting time preference according to the meeting time of historical meetings. Specifically, the server may determine the meeting time preference according to the frequency of occurrence of the meeting time of each historical meeting. The server may also screen the meeting times of the nearest preset number of historical meetings that match the meeting type of the target meeting from the meeting times of each historical meeting, and determine the meeting time preference according to the screened meeting times.

[0121] In other embodiments, the server may also predict the meeting time preference according to at least one of the information of the meeting members of the target meeting and the meeting type of the target meeting.

[0122] In one embodiment, the meeting time preference may be the meeting time preference of the team corresponding to the target meeting, or the meeting time preference of the team corresponding to the target meeting for the meeting type of the target meeting, or the meeting time preference of the user performing the meeting addition operation, or others, which are not limited.

[0123] In one embodiment, the server may sort all the idle time periods in descending order of preference according to the meeting time preference, and the server may use the first preset number of idle time periods as the meeting time periods of the recommended target meeting.

[0124] In one embodiment, the server may send the meeting time periods of the recommended target meeting to the terminal, and the terminal may display the meeting time periods of the recommended target meeting for the user to select. The user may select the target meeting time period from the meeting time periods of the recommended target meeting to complete the addition of the target meeting.

[0125] In another embodiment, the server may send the meeting time periods of the recommended target meeting to the terminal, and the terminal may display the meeting time periods of the recommended target meeting for the user to select and refer to. The user may refer to the meeting time periods of the recommended target meeting to set the meeting time period of the target meeting to complete the addition of the target meeting. The meeting time period set by the user may be one of the recommended meeting time periods or may not belong to the recommended meeting time periods. That is, the recommended meeting time periods are only for the user's reference and do not limit that the time period for adding the target meeting must be selected from the recommended meeting time periods.

[0126] In one embodiment, the terminal may arrange and display the meeting time periods of each recommended target meeting in the recommended order.

[0127] S210. If there is no idle time period, recommend the meeting time period of the target meeting from the overlapping non-idle time periods according to the overlapping degree between the time periods corresponding to each schedule information.

[0128] It can be understood that in step S210, the meeting time period of the target meeting may be recommended from the overlapping non-idle time periods according to the overlapping degree between at least part (i.e., part or all) of the time periods corresponding to the schedule information.

[0129] In one embodiment, the server may recommend the meeting time period of the target meeting from the overlapping non-idle time periods only according to the overlapping degree. In one embodiment, the overlapping degree may be characterized by the number of overlaps. Specifically, the server may recommend the meeting time period of the target meeting from the overlapping non-idle time periods according to the number of overlaps of the time periods corresponding to each schedule information.

[0130] In other embodiments, the server may also recommend a meeting time period for the target meeting from the overlapping non-idle time periods according to the degree of overlap and in combination with other information.

[0131] In one embodiment, the server may recommend a meeting time period for the target meeting from the overlapping non-idle time periods according to at least two of the degree of overlap between the time periods corresponding to the respective schedule information, the priority of the meeting corresponding to the schedule information, and the meeting time preference. It can be understood that the priority order among the above three reference dimensions for recommending the meeting time period (i.e., the three reference dimensions of the degree of overlap, priority, and meeting time preference) can be set arbitrarily and is not limited. For example: the server may first recommend according to the degree of overlap. If the degrees of overlap are the same, it may then recommend according to the priority. If the priorities are the same, it may then recommend according to the meeting time preference. The server may also first recommend according to the degree of overlap. If the degrees of overlap are the same, it may then recommend according to the meeting time preference. If the meeting time preferences are the same, it may then recommend according to the priority.

[0132] In the above meeting time recommendation method, the to-be-processed schedule information of each meeting member specified in the meeting addition request is obtained, and then an overlap analysis is performed on the time periods corresponding to the schedule information of each meeting member, so as to automatically determine whether there is an idle time period between the time periods of the schedule information of each meeting member. If there is an idle time period without overlap, a meeting time period for the target meeting is recommended from the idle time periods. In this way, it is possible to quickly recommend an idle time period without communicating with each meeting member, and efficiently arrange the meeting time; if there is no idle time period, a meeting time period for the target meeting is recommended from the overlapping non-idle time periods according to the degree of overlap between the time periods corresponding to the respective schedule information. In this way, in the case of no idle time period, it is possible to automatically recommend a meeting time period from the non-idle time periods according to the degree of overlap without communicating with each meeting member separately, and efficiently arrange the meeting time, thereby improving the efficiency of meeting addition.

[0133] In one embodiment, S204 obtaining the to-be-processed schedule information of each meeting member specified in the meeting addition request includes: obtaining a timeline with schedule information added; and obtaining the to-be-processed schedule information of each meeting member specified in the meeting addition request from the schedule information added on the timeline. In this embodiment, S206 performing an overlap analysis on the time periods corresponding to the schedule information of each meeting member includes: determining the time periods corresponding to the obtained schedule information on the timeline; and performing an overlap analysis on the determined time periods.

[0134] Specifically, the server can record the schedule information pre-added by members on the timeline and store it. The server can, in response to a meeting addition request, obtain the timeline with the schedule information added, and obtain the pending schedule information of each meeting member specified in the meeting addition request from the schedule information added on the timeline. Then, the server can determine the time periods corresponding to the obtained schedule information on the timeline and perform an overlap analysis on the determined time periods.

[0135] In one embodiment, the target meeting is a team meeting. The server can record the schedule information pre-added by each team member on the timeline and store it. The server can, in response to a meeting addition request, obtain the timeline with the schedule information added, and obtain the pending schedule information of each meeting member specified in the meeting addition request from the schedule information added on the timeline.

[0136] For example: Assume that the team corresponding to the target meeting includes 5 team members, namely team members A, B, C, D, and E. The server can record the schedule information pre-added by team members A, B, C, D, and E on the timeline and store it. After receiving the meeting addition request, the server can determine that the meeting members specified in the meeting addition request are A, D, and E. The server can obtain the pending schedule information of A, D, and E from the timeline. Then, the server can determine the time periods corresponding to the pending schedule information of A, D, and E on the timeline, and then perform an overlap analysis on these time periods to analyze whether these time periods overlap and the degree of overlap, etc.

[0137] In the above embodiment, by recording the schedule information on the timeline, the pending schedule information of each specified meeting member can be quickly determined from the timeline, and the time periods corresponding to each schedule information can be determined, thereby improving the efficiency of recommending meeting times and eliminating the need to communicate with each meeting member one by one, and further improving the efficiency of meeting addition.

[0138] In one embodiment, the target meeting is a team meeting. Team members can pre-add or modify their personal schedule information on the timeline through the terminal and can view the schedule information of team members other than themselves. The terminal used by the team member can send the personal schedule information added or modified on the timeline to the server, and the server can store the timeline with the schedule information added. After receiving a meeting addition request for the target meeting, the server can, in response to the meeting addition request, obtain the timeline with the schedule information added and obtain the schedule information of each team member specified in the meeting addition request from the schedule information added on the timeline.

[0139] In the above embodiments, team members can add or modify their personal schedule information on the timeline in advance, so that the to-be-processed schedule information of each specified team member can be quickly determined from the timeline, thereby improving the efficiency of recommending meeting times. There is no need to communicate with each participating team member one by one, and thus the efficiency of adding meetings can be improved. It is possible to overall manage the schedule information of the entire team and improve the team collaboration efficiency.

[0140] In one embodiment, the overlapping analysis of the determined time periods includes: exhaustively dividing the determined time periods into pairs; sequentially comparing each time point corresponding to the two time periods in each pair; determining the time period composed of the time points with consistent comparison results as the overlapping non-idle time period, and determining the time periods other than the non-idle time period on the timeline as the non-overlapping idle time periods.

[0141] Specifically, the server can exhaustively divide the determined time periods into pairs and sequentially compare each time point corresponding to the two time periods in each pair, that is, among the determined time periods, comparison is performed between every two time periods, and during the comparison process, each time point of one time period is sequentially compared with each time point of the other time period.

[0142] For example: if the determined time periods are A, B, and C respectively, then after exhaustively dividing the time periods into pairs, the following three pairs will be obtained: A and B, B and C, and A and C. The server can compare the two time periods in each of the above pairs respectively, that is, compare A and B, compare B and C, and compare A and C. During the comparison of two time periods, each time point of one time period is sequentially compared with each time point of the other time period, that is, each time point of A is sequentially compared with each time point of B, each time point of B is sequentially compared with each time point of C, and each time point of A is sequentially compared with each time point of C.

[0143] In one embodiment, the server can determine the time period composed of the time points with consistent comparison results as the overlapping non-idle time period. For example: if time period A is from 9:00 to 11:00 on December 11th, and time period B is from 10:00 to 12:00 on December 11th, after comparing A and B, the time period composed of the time points with consistent comparison results is from 10:00 to 11:00 on December 11th, and the time period from 10:00 to 11:00 on December 11th composed of the time points with consistent comparison results is determined as the overlapping non-idle time period.

[0144] In one embodiment, the server may determine the time periods on the timeline other than the non-idle time periods as non-overlapping idle time periods. For example, assuming that only the time period from 10:00 to 11:00 on December 11th is a non-idle time period, then all other time periods on December 11th except the time period from 10:00 to 11:00 are non-overlapping idle time periods. The same applies to other dates.

[0145] In another embodiment, the server may determine the time periods on the timeline other than the overlapping non-idle time periods within the pre-set working time periods as non-overlapping idle time periods. Since the time outside the working time periods is the private time of the meeting members, meetings may not be scheduled. For example, if the pre-set working time period is from 9:00 to 18:00, then the time periods on the timeline other than the overlapping non-idle time periods within this working time period are non-overlapping idle time periods, and the time periods outside this working time period will not be determined as non-overlapping idle time periods. For example, if the overlapping non-idle time period is from 10:00 to 16:00, then the non-overlapping idle time periods are from 9:00 to 10:00 and from 16:00 to 18:00, and the time periods from 0:00 to 9:00 and from 18:00 to 24:00 will not be determined as non-overlapping idle time periods.

[0146] In the above embodiments, the server may exhaustively divide the determined time periods into pairs, and compare the respective time points corresponding to the two time periods in each pair in sequence to determine the overlapping time periods between the time periods, and then automatically determine the non-idle time periods and idle time periods for meeting time recommendation. This improves the efficiency and accuracy of meeting time recommendation, and further improves the efficiency of meeting addition.

[0147] In one embodiment, for any two determined time periods, if the start time point of one of the time periods is less than or equal to the end time point of the other time period, and the end time point of this one of the time periods is greater than or equal to the start time point of the other time period, then the server may determine these two time periods as overlapping non-idle time periods.

[0148] In one embodiment, the overlapping non-idle time periods may satisfy the constraint relationship represented by formula (1):

[0149] t 2_starttime ≤t 1_endtime ; and

[0150] t 2_endtime ≥t 1_starttime ; (1)

[0151] Wherein, t1 and t2 are respectively any one of the determined time periods, t 1_starttime is the start time point of time period t1, t 1_endtime is the end time point of time period t1, t 2_starttimeis the start time point of time period t2, t 2_endtime is the end time point of time period t2. The server can determine the time periods that satisfy the above formula (1) as overlapping time periods with each other.

[0152] For the sake of easy understanding, an example is given below. It can be understood that for two time periods t1 and t2, the overlapping situations between them can include Figure 3 the three situations shown as follows:

[0153] 1. The start time point of time period t2 falls within time period t1;

[0154] 2. The end time point of time period t2 falls within time period t1;

[0155] 3. Time period t2 includes the entire time period t1.

[0156] Therefore, the overlap between time period t1 and time period t2 can be represented by the above formula (1).

[0157] In one embodiment, the overlapping analysis of the determined time periods includes: adding the start time points of the determined time periods to the first set; adding the end time points of the determined time periods to the second set; sequentially selecting the current time period from the determined time periods, and for each current time period, selecting candidate start time points from the first set and candidate end time points from the second set; wherein, the candidate start time points are less than or equal to the end time point of the current time period; the candidate end time points are greater than or equal to the start time point of the current time period; among the determined time periods other than the current time period, selecting the time periods corresponding to the candidate start time points and candidate end time points, and determining them as non-idle time periods overlapping with the current time period; determining the time periods on the time axis other than the non-idle time periods corresponding to the determined time periods as non-overlapping idle time periods.

[0158] Specifically, the server can add the start time points of the determined time periods to the first set S, and add the end time points of the determined time periods to the second set E. The server can sequentially select the current time period (s, e) from the determined time periods, and for each current time period (s, e), select candidate start time points {x|x∈S∧x≤e} from the first set S, and select candidate end time points {y|y∈E∧y≥s} from the second set, that is, the candidate start time point x is less than or equal to the end time point e of the current time period, and the candidate end time point y is greater than or equal to the start time point s of the current time period.

[0159] The server can select, from among the determined time periods other than the current time period (s, e), the time periods corresponding to the candidate start time point x and the candidate end time point y, and determine them as non-idle time periods overlapping with the current time period.

[0160] In one embodiment, the non-idle time periods overlapping with the current time period can be determined according to the following formula (2):

[0161] {x|x∈S∧x≤e}∩{y|y∈E∧y≥s}; (2)

[0162] Where s is the start time point of the current time period, e is the end time point of the current time period, S is the first set, E is the second set, x is the candidate start time point, and y is the candidate end time point.

[0163] That is, according to formula (2), the time periods corresponding to the candidate start time point and the candidate end time point can be determined to obtain the non-idle time periods overlapping with the current time period.

[0164] It can be understood that selecting the time periods corresponding to the candidate start time point and the candidate end time point means that the start time point of the selected time period belongs to the candidate start time point and the end time point belongs to the candidate end time point.

[0165] The following is an example. As Figure 4 shown, assume that the determined time periods are s1e1, s2e2, s3e3, s4e4, s5e5, and s6e6. The server can add s1 to s6 to the first set S and add e1 to e6 to the second set E, and then sequentially select the current time period from the 6 time periods to determine the time periods overlapping with the current time period. Assume that the current time period is s2e2. Then s1, s2, s4, s5, and s6 in the first set S are all candidate start time points less than or equal to e2, and e1, e2, e3, e4, and e5 in the second set E are all candidate end time points greater than or equal to s2. Among the 5 time periods other than the current time period s2e2, s1e1, s4e4, and s5e5 are all time periods whose start time point belongs to the candidate start time point and the end time point belongs to the candidate end time point, while the start time point s3 of s3e3 does not belong to the candidate start time point and the end time point e6 of s6e6 does not belong to the candidate end time point. Therefore, the server can determine s1e1, s4e4, and s5e5 as the time periods overlapping with the current time period s2e2.

[0166] In one embodiment, the server can determine all the overlapping non-idle time periods according to the overlapping non-idle time periods corresponding to each current time period.

[0167] In one embodiment, the server may determine the time periods on the timeline other than all overlapping non-idle time periods as non-overlapping idle time periods. For example, assuming that only the time period from 10:00 to 11:00 on December 11th is a non-idle time period, then all other time periods on December 11th except for the time period from 10:00 to 11:00 are non-overlapping idle time periods. The same applies to other dates.

[0168] In another embodiment, the server may determine the time periods on the timeline other than all overlapping non-idle time periods within a pre-set working time period as non-overlapping idle time periods. Since the time outside the working time period is the private time of the meeting members, meetings may not be scheduled. For example, if the pre-set working time period is from 9:00 to 18:00, then the time periods on this working time period other than the overlapping non-idle time periods are non-overlapping idle time periods, and the time periods outside this working time period will not be determined as non-overlapping idle time periods. For example, if the overlapping non-idle time period is from 10:00 to 16:00, then the non-overlapping idle time periods are from 9:00 to 10:00 and from 16:00 to 18:00, and the time periods from 0:00 to 9:00 and from 18:00 to 24:00 will not be determined as non-overlapping idle time periods.

[0169] In the above embodiments, the server may sequentially select the current time period, and based on the start time point and end time point of each time period, determine the overlapping non-idle time periods between each time period and the current time period, and then automatically determine the non-idle time periods and idle time periods for meeting time recommendation. This improves the efficiency and accuracy of meeting time recommendation, and thus improves the efficiency of meeting addition.

[0170] In one embodiment, the meeting addition request includes the meeting duration of the target meeting. In this embodiment, in S208, if there are non-overlapping idle time periods, the recommended meeting time period for the target meeting from the idle time periods includes: if there are non-overlapping idle time periods that meet the meeting duration, recommend the meeting time period for the target meeting from the idle time periods that meet the meeting duration. In S210, if there are no idle time periods, the recommended meeting time period for the target meeting from the overlapping non-idle time periods according to the overlapping degree between the time periods corresponding to each schedule information includes: if there are no idle time periods that meet the meeting duration, then according to the overlapping degree between the time periods corresponding to each schedule information, recommend the meeting time period for the target meeting that meets the meeting duration from the overlapping non-idle time periods.

[0171] The meeting duration of the target meeting refers to the duration required for the target meeting to be held, that is, the length of the meeting time period of the target meeting.

[0172] Specifically, the user can set the meeting duration of the target meeting through the graphical interface of the terminal. The terminal can generate a meeting addition request including the meeting duration according to the set meeting duration and send the meeting addition request to the server. The server can perform an overlap analysis on the time periods corresponding to the schedule information of each meeting member in response to the meeting addition request to determine whether there is an idle time period without overlap that meets the meeting duration.

[0173] If there is an idle time period without overlap that meets the meeting duration, the server can recommend a meeting time period for the target meeting from the idle time periods that meet the meeting duration.

[0174] If there is no idle time period that meets the meeting duration, then according to the degree of overlap between the time periods corresponding to each schedule information, a meeting time period for the target meeting that meets the meeting duration is recommended from the overlapping non-idle time periods.

[0175] In the above embodiments, the user can set the meeting duration of the target meeting, and the server can recommend a meeting time period that meets the meeting duration according to the meeting duration, avoiding the recommendation of inappropriate meeting time periods and improving the accuracy and rationality of meeting time recommendation.

[0176] In one embodiment, the target meeting is a team meeting, and the method further includes: obtaining the meeting times of each historical meeting of the team corresponding to the team meeting; predicting the meeting time preference of the team according to the obtained meeting times of the historical meetings; and recommending a meeting time period for the target meeting from the idle time periods including: recommending a meeting time period for the target meeting from the idle time periods according to the meeting time preference.

[0177] Among them, a historical meeting refers to a meeting that has been held.

[0178] Specifically, the server can obtain the meeting times of each historical meeting of the team corresponding to the team meeting and predict the meeting time preference of the team according to the obtained meeting times of each historical meeting. Then, the server can recommend a meeting time period for the target meeting from the idle time periods according to the meeting time preference of the team. In one embodiment, the server can predict the meeting time preference of the team according to the frequency of occurrence of the meeting times of each historical meeting, and the meeting time with a higher frequency of occurrence is a meeting time period with a greater degree of preference.

[0179] In one embodiment, the server may screen the meeting times of the nearest preset number of historical meetings that match the meeting type of the target meeting from the meeting times of each historical meeting, and determine the meeting time preference according to the screened meeting times. In other embodiments, the server may also determine the meeting time preference according to the duration experienced by the meeting times of each historical meeting. For example, the longer the duration, to a certain extent, it can indicate a preference for holding meetings during this period.

[0180] In one embodiment, the meeting time preference may be the meeting time preferred by the team. The server may perform an overlapping analysis of the meeting times of each historical meeting on a weekly basis, that is, perform an overlapping analysis after representing the meeting times of each historical meeting on a weekly basis. Among them, representing on a weekly basis means representing as from a certain time to a certain time on a certain day of the week. For example: from 14:00 to 16:00 on Wednesday, or from 9:00 to 10:00 on Friday, etc. The server may determine the frequency of occurrence of the meeting times of the historical meetings according to the number of overlaps between the meeting times of each historical meeting. The greater the number of overlaps, the greater the frequency of occurrence of the corresponding meeting time. Then, determine the meeting time preference according to the frequency of occurrence, that is, determine at what time on what day of the week the team is more inclined to hold meetings. For example: among the meeting times of each historical meeting, the number of overlaps of the time period from 14:00 to 16:00 on Wednesday is 3 times, that is, it indicates that this time period has appeared a total of 4 times in historical meetings. If the frequency of 4 times is the highest compared to the frequencies of occurrence of the meeting times of other historical meetings, it can be determined that the team is more inclined to hold meetings from 14:00 to 16:00 on Wednesday.

[0181] In one embodiment, the server may use the idle time period that matches the meeting time preference as the meeting time period recommended for the target meeting. For example: if it is predicted that the meeting time preference is more inclined to hold meetings in the morning, then use the idle time period belonging to the morning as the meeting time period recommended for the target meeting. Another example: if it is predicted that the meeting time preference is more inclined to hold meetings on Friday, then use the idle time period belonging to Friday as the meeting time period recommended for the target meeting.

[0182] In one embodiment, the meeting time preference may be the preference degree of the time period. The server may predict the preference degree of the team for each idle time period according to the frequency of occurrence of the meeting times of each historical meeting, and then recommend the meeting time period of the target meeting from the idle time periods according to the magnitude of the preference degree. Specifically, the server may sort the meeting times of each historical meeting according to the magnitude of the frequency of occurrence. The server may predict the preference degree of the team for each idle time period according to the sorting position corresponding to each idle time period in the meeting times of the historical meetings.

[0183] In another embodiment, the server may sort all the idle time periods in descending order of preference, and select the top preset number of idle time periods as the meeting time periods for the recommended target meeting.

[0184] In the above embodiment, the server may determine the meeting time preference of the team corresponding to the team meeting based on the meeting times of all the historical meetings of the team, and recommend the meeting time period of the target meeting from the idle time periods according to the meeting time preference, so as to be able to recommend the meeting time more accurately, make the recommended meeting time more in line with the team's preference, and thus improve the efficiency of meeting addition.

[0185] In one embodiment, the meeting addition request includes the target meeting type of the target meeting. Obtaining the meeting times of all the historical meetings of the team corresponding to the team meeting includes: for the team corresponding to the team meeting, obtaining the meeting times of the historical meetings that the team participated in and belong to the target meeting type. Predicting the meeting time preference of the team based on the obtained meeting times of the historical meetings includes: predicting the meeting time preference of the team for the meetings of the target meeting type based on the obtained meeting times of the historical meetings.

[0186] Wherein, the target meeting type of the target meeting refers to the meeting type of the target meeting.

[0187] In one embodiment, the target meeting type may include at least one of types such as weekly meetings, project meetings, experience exchange meetings, trainings, and lectures.

[0188] Specifically, the server may obtain the meeting times of all the historical meetings that the team corresponding to the team meeting participated in and belong to the target meeting type, and predict the meeting time preference of the team for the meetings of the target meeting type based on the obtained meeting times. Then, the server may recommend the meeting time period of the target meeting from the idle time periods according to the meeting time preference of the team for the meetings of the target meeting type.

[0189] In the above embodiment, the server may predict the meeting time preference of the team for the meetings of the target meeting type based on the meeting times of the historical meetings, and recommend the meeting time period of the target meeting from the idle time periods according to the meeting time preference of the team for the meetings of the target meeting type. Thus, the meeting time can be recommended more accurately, making the recommended meeting time more in line with the team's meeting time preference for the meetings of the target meeting type, and thus improving the efficiency of meeting addition.

[0190] In one embodiment, the target meeting is a team meeting. In this embodiment, if there is no idle time slot, the meeting time slot of the target meeting is recommended from the overlapping non-idle time slots according to the overlapping degree between the time slots corresponding to each schedule information, including: if there is no idle time slot, the meeting time slot of the target meeting is recommended from the overlapping non-idle time slots according to the team identity priorities of each meeting member of the team meeting and the overlapping degree between the time slots corresponding to each schedule information.

[0191] Among them, the team identity priority is the priority corresponding to the identity of the meeting member in the team. It can be understood that the time slot outside the time slot corresponding to the schedule information of the meeting member with a larger team identity priority is preferentially used as the recommended time slot of the target meeting.

[0192] In one embodiment, the server can determine the target meeting members whose team identity priorities are among the top preset positions from each meeting member of the team meeting; determine the time slots except those corresponding to the schedule information of the target meeting members from the time slots corresponding to the schedule information of each meeting member of the team meeting; and recommend the time slot of the target meeting from the determined time slots according to the overlapping degree between the time slots corresponding to the schedule information of the non-target meeting members and the determined time slot.

[0193] The non-target meeting members are the meeting members of the team meeting other than the target meeting members.

[0194] It can be understood that the idle time slot is the time slot in the team meeting when all meeting members have no scheduled schedule and are in an idle state. Since there is no idle time slot between the time slots corresponding to all meeting members in the team meeting in this embodiment, the time slot except the time slot corresponding to the schedule information of the target meeting members belongs to the non-idle time slot. Therefore, recommending the time slot of the target meeting from the determined time slots is equivalent to recommending the time slot of the target meeting from the determined non-idle time slots.

[0195] For example, among the meeting members of the team meeting, there are a supervisor and group members, and the team identity priority of the supervisor is higher than that of the group members. Then, the time slot corresponding to the schedule information of each meeting member of the team meeting can be excluded from the time slot corresponding to the schedule information of this supervisor (that is, the time slot when the supervisor has a scheduled schedule and cannot hold a meeting). Then, according to the overlapping degree between the time slots corresponding to each group member and the remaining time slots, the time slot of the target meeting is recommended from the remaining time slots. Suppose a team has 1 supervisor and 3 group members, and the supervisor has 2 time slots A and B without a scheduled schedule (i.e., the remaining time slots). In time slot A, the schedules of 2 group members overlap with it, and in time slot B, the schedule of 1 group member overlaps with it. Then, time slot B can be recommended as the time slot of the target meeting.

[0196] In one embodiment, if the overlap degree between the time period corresponding to the schedule information of a non-target meeting member and the determined time period is less than or equal to a preset threshold, the server may recommend a time period for the target meeting from the determined time period according to the overlap degree between the time period corresponding to the schedule information of the non-target meeting member and the determined time period. If the overlap degree between the time period corresponding to the schedule information of the non-target meeting member and the determined time period is greater than the preset threshold, the meeting time period of the target meeting may be recommended from the overlapping non-idle time periods according to the overlap degree between the time periods corresponding to the schedule information of all meeting members.

[0197] In one embodiment, recommending a meeting time period of a target meeting from the overlapping non-idle time periods according to the overlap degree between the time periods corresponding to each schedule information includes: sorting the overlapping non-idle time periods in ascending order of the overlap degree according to the overlap degree between the time periods corresponding to each schedule information; recommending the meeting time period of the target meeting according to the first preset number of non-idle time periods.

[0198] Specifically, the server may sort the overlapping non-idle time periods in ascending order of the overlap degree according to the overlap degree between the time periods corresponding to each schedule information, and use the first preset number of non-idle time periods as the recommended meeting time period of the target meeting.

[0199] In one embodiment, the terminal may display the recommended meeting time periods of the target meeting in ascending order of the overlap degree.

[0200] In the above embodiment, the server may recommend the meeting time period of the target meeting from the overlapping non-idle time periods according to the size of the overlap degree, so as to be able to recommend the meeting time more accurately, make the recommended meeting time more reasonable, and ensure that more meeting members can participate in the meeting.

[0201] In one embodiment, the schedule information includes a meeting schedule. Recommending a meeting time period of a target meeting from the overlapping non-idle time periods according to the overlap degree between the time periods corresponding to each schedule information includes: recommending the meeting time period of the target meeting from the overlapping non-idle time periods according to the overlap degree between the time periods corresponding to each meeting schedule and the priority of the meeting corresponding to the meeting schedule.

[0202] Among them, the priority of the meeting is used to represent the importance of the meeting.

[0203] It can be understood that the higher the priority of a meeting, the more important the meeting is, and thus the more necessary it is to ensure the meeting time of this meeting first. The lower the priority of a meeting, the less important the meeting is, and thus other meetings can be arranged during the time period of this meeting more easily.

[0204] In one embodiment, during the process of adding a meeting, the user can set the priority of the target meeting. Therefore, the schedule information can include the priority of the corresponding meeting.

[0205] In one embodiment, the priority of the target meeting can be the priority of the target meeting itself.

[0206] In another embodiment, if the target meeting is a project meeting, the priority of the target meeting can also be the priority of the project corresponding to the target meeting.

[0207] In other embodiments, the priority of the target meeting can also be the priority corresponding to the type of the target meeting. The priority of the target meeting can also be other values, which are not limited.

[0208] In one embodiment, if the priority of the target meeting is the priority of the target meeting itself, during the process of adding a meeting, the user can set the priority of the target meeting itself through the terminal, and the terminal can generate a meeting addition request including the priority of the target meeting itself and send it to the server.

[0209] In one embodiment, if the priority of the target meeting is the priority of the project corresponding to the target meeting, during the process of adding a meeting, the user can set the priority of the project corresponding to the target meeting through the terminal, and the terminal can generate a meeting addition request including the priority of the project and send it to the server.

[0210] In another embodiment, if the priority of the target meeting is the priority of the project corresponding to the target meeting, the user can pre-set the priorities of each project through the terminal, and the server can store the pre-set priorities of each project. During the process of adding a meeting through the terminal, the user can set the project corresponding to the target meeting, and the terminal can generate a meeting addition request including the project corresponding to the target meeting and send it to the server. Then, the server can determine the priority of the project corresponding to the target meeting according to the project corresponding to the target meeting and the pre-stored priorities of each project.

[0211] In one embodiment, if the priority of the target meeting is the priority of the target meeting type corresponding to the target meeting, then during the process of the user performing a meeting addition operation, the user can set the priority of the target meeting type corresponding to the target meeting through the terminal, and the terminal can generate a meeting addition request including the priority of the target meeting type and send it to the server.

[0212] In another embodiment, if the priority of the target meeting is the priority of the target meeting type corresponding to the target meeting, then the user can pre-set the priorities of each meeting type through the terminal, and the server can store the pre-set priorities of each meeting type. During the process of the user performing a meeting addition operation through the terminal, the user can set the target meeting type corresponding to the target meeting, and the terminal can generate a meeting addition request including the target meeting type corresponding to the target meeting and send it to the server. Then, the server can determine the priority of the target meeting type corresponding to the target meeting according to the target meeting type corresponding to the target meeting and the pre-stored priorities of each meeting type.

[0213] In one embodiment, the server can first sort each non-idle time period in ascending order of the overlap degree between the time periods corresponding to each meeting schedule, and then sort the non-idle time periods in the same order after sorting by overlap degree in ascending order of the priority of the corresponding meeting, and then use the first preset number of time periods after sorting by priority as the meeting time period of the recommended target meeting.

[0214] In one embodiment, the server can first sort each non-idle time period in ascending order of the overlap degree between the time periods corresponding to each meeting schedule, and then sort the non-idle time periods in the same order after sorting by overlap degree in descending order of the preference degree, and then use the first preset number of time periods after sorting by meeting time preference as the meeting time period of the recommended target meeting.

[0215] In one embodiment, the server can first sort each non-idle time period in ascending order of the overlap degree between the time periods corresponding to each meeting schedule, and then sort the non-idle time periods in the same order after sorting by overlap degree in ascending order of the priority of the corresponding meeting, and then sort the non-idle time periods in the same order after sorting by priority in descending order of the preference degree, and finally use the first preset number of time periods after sorting by meeting time preference as the meeting time period of the recommended target meeting. In one embodiment, the order of use of the above three reference dimensions for recommending meeting times (i.e., the three reference dimensions of overlap degree, priority, and meeting time preference) can be set arbitrarily.

[0216] In one embodiment, the server may score each time period according to the overlap degree between the time periods corresponding to each meeting schedule and the priority of the meetings corresponding to each time period, and then calculate a comprehensive score according to the scores in the overlap degree dimension and the scores in the priority dimension according to a preset weight, so as to obtain the comprehensive scores corresponding to each time period respectively. Based on the comprehensive scores of the time periods corresponding to each meeting schedule, the meeting time period of the target meeting is recommended.

[0217] In one embodiment, the server may score each time period according to at least two of the three evaluation dimensions of the overlap degree between the time periods corresponding to each meeting schedule, the priority of the meetings corresponding to each time period, and the meeting time preference. Then, a comprehensive score is calculated according to the scores in the selected evaluation dimensions according to a preset weight, so as to obtain the comprehensive scores corresponding to each time period respectively. Based on the comprehensive scores of the time periods corresponding to each meeting schedule, the meeting time period of the target meeting is recommended.

[0218] In one embodiment, the server may remove the time periods that meet the time period locking condition from the time periods corresponding to each meeting schedule according to the priority of the meetings corresponding to each time period, and recommend the meeting time period of the target meeting from the overlapping non-idle time periods according to the overlap degree between the time periods corresponding to each meeting schedule.

[0219] In the above embodiment, the server may recommend the meeting time period of the target meeting from the overlapping non-idle time periods according to the overlap degree between the time periods corresponding to each schedule information and the priority of the meetings corresponding to each time period, analyze each time period from multiple dimensions, recommend the meeting time period of the target meeting, give priority to ensuring the meeting time of the meetings with high priority, and adjust the meeting time of the meetings with low priority, thereby improving the accuracy and rationality of the meeting time recommendation, and further improving the efficiency of meeting addition.

[0220] In one embodiment, recommending the meeting time period of the target meeting from the overlapping non-idle time periods according to the overlap degree between the time periods corresponding to each meeting schedule and the priority of the meetings corresponding to the meeting schedule includes: sorting each non-idle time period in ascending order of the overlap degree according to the overlap degree between the time periods corresponding to each meeting schedule; removing the non-idle time periods whose corresponding meeting priorities meet the time period locking condition from the sorted non-idle time periods according to the priority of the meetings corresponding to each non-idle time period; selecting the first preset number of non-idle time periods from the remaining non-idle time periods after removal; and recommending the meeting time period of the target meeting according to the selected non-idle time periods.

[0221] Among them, the time period locking condition is used to determine whether a time period needs to be locked. It can be understood that a time period that meets the time period locking condition cannot be recommended.

[0222] Specifically, the server can sort the non-idle time periods in ascending order of the degree of overlap between the time periods corresponding to each meeting schedule, and then remove the non-idle time periods whose corresponding meeting priorities meet the time period locking condition from the sorted non-idle time periods according to the priorities of the meetings corresponding to the non-idle time periods. Then, from the remaining non-idle time periods after the removal, the server selects the first preset number of non-idle time periods as the meeting time periods of the recommended target meetings. In one embodiment, the server can sort the non-idle time periods sorted according to the degree of overlap in descending order of the priorities of the corresponding meetings, and determine the non-idle time periods with the priorities ranked among the first preset number as the non-idle time periods that meet the time period locking condition.

[0223] In one embodiment, the server can determine the non-idle time period with the highest priority of the corresponding meeting as the non-idle time period that meets the time period locking condition.

[0224] In the above embodiments, the server can remove the non-idle time periods that meet the time period locking condition according to the priorities of the meetings, and recommend the meeting time periods of the target meetings from the remaining non-idle time periods after the removal according to the degree of overlap, which can preferentially ensure the meeting time of meetings with high priorities and adjust the meeting time of meetings with low priorities, thereby improving the accuracy and rationality of the meeting time recommendation and further improving the efficiency of meeting addition.

[0225] In one embodiment, the target meeting is a team meeting. Recommending the meeting time period of the target meeting according to the selected non-idle time period includes: obtaining the meeting time preference of the team corresponding to the target meeting; and recommending the meeting time period of the target meeting from the selected non-idle time periods according to the meeting time preference.

[0226] Specifically, after sorting the non-idle time periods according to the degree of overlap and removing the non-idle time periods that meet the time period locking condition according to the priorities of the meetings, the server can obtain the meeting time preference of the team corresponding to the target meeting, and recommend the meeting time period of the target meeting from the selected non-idle time periods according to the meeting time preference of the team.

[0227] In one embodiment, after sorting the non-idle time periods according to the degree of overlap and removing the non-idle time periods that meet the time period locking condition according to the priority of the meeting, the server may sort the non-idle time periods in the same order from largest to smallest according to the preference degree, and use the first preset number of non-idle time periods as the meeting time periods of the recommended target meeting.

[0228] In another embodiment, the server may also screen out the non-idle time periods that meet the meeting time preferences of the team from the selected non-idle time periods for recommendation.

[0229] In the above embodiment, after sorting the non-idle time periods according to the degree of overlap and removing the non-idle time periods that meet the time period locking condition according to the priority of the meeting, the server may further recommend the meeting time according to the meeting time preferences of the team, analyze the non-idle time periods from multiple dimensions to recommend the meeting time, improve the accuracy and rationality of the meeting time recommendation, and make the recommended meeting time more in line with the preferences of the team.

[0230] In one embodiment, the meeting addition request includes the recommended meeting duration; the target meeting is a team meeting; before receiving the meeting addition request for the target meeting, the method further includes: determining the meeting duration preference of the team according to the meeting duration of the historical meetings of the team corresponding to the team meeting; recommending the meeting duration of the target meeting according to the meeting duration preference.

[0231] The meeting duration preference refers to the meeting duration that is more inclined to be set.

[0232] Specifically, the user may set the team corresponding to the target meeting through the terminal, or the server may determine the team to which the user belongs according to the user's identity information as the team corresponding to the target meeting. The server may determine the meeting duration preference of the team according to the meeting duration of the historical meetings of the team corresponding to the target meeting. The server may sort various meeting durations from largest to smallest according to the preference degree of the team for various meeting durations, use the first preset number of meeting durations as the meeting duration of the recommended target meeting, and send the meeting duration of the recommended target meeting to the terminal.

[0233] In one embodiment, the terminal may display the meeting duration of the recommended target meeting for the user to select. The user may select the target meeting duration from the recommended meeting durations. The terminal may generate a meeting addition request including the meeting duration according to the meeting duration selected by the user and send it to the server.

[0234] In another embodiment, the terminal may display the meeting duration of the recommended target meeting for the user's reference. The user may refer to the meeting duration of the recommended target meeting to set the meeting duration of the target meeting. The meeting duration set by the user may be one of the recommended meeting durations or may not belong to the recommended meeting durations. The terminal may generate a meeting addition request including the meeting duration according to the meeting duration set by the user and send it to the server.

[0235] In one embodiment, the server may also obtain the pre-set scientific meeting duration and send the scientific meeting duration to the terminal for meeting duration recommendation.

[0236] In this embodiment, the server may determine the meeting duration preference of the team according to the meeting durations of the historical meetings of the team, recommend the meeting duration, thereby improving the accuracy and rationality of the recommended meeting duration, ensuring that the meeting duration is more in line with the team preference or more scientific. In addition, the user can quickly perform the meeting addition operation according to the recommended meeting duration, improving the efficiency of meeting addition.

[0237] As Figure 5 shown, it is the overall flowchart of the meeting time recommendation method in each embodiment of the present application. First, the user may set the meeting duration and priority of the target meeting through the terminal. Then, the server may perform an overlap analysis on the time periods corresponding to the schedule information of each meeting member to determine whether there is an idle time period that meets the meeting duration. If there is, the server may sort the idle time periods that meet the meeting duration in descending order of preference degree, and send the first pre-set number of idle time periods as the recommended meeting time periods to the terminal, and the terminal may display the recommended meeting time periods. If there is no idle time period that meets the meeting duration, the server may sort the non-idle time periods in ascending order of overlap degree, and exclude the non-idle time periods that meet the time lock condition, and send the first pre-set number of non-idle time periods as the recommended meeting time periods to the terminal, and the terminal may display the recommended meeting time periods.

[0238] In one embodiment, as Figure 6 shown, a sequence diagram of a meeting time recommendation method is provided, which specifically includes the following steps:

[0239] S602, the terminal generates a meeting addition request according to the user's meeting addition operation.

[0240] S604, the terminal sends the meeting addition request to the server.

[0241] S606, in response to the meeting addition request, the server sends a request to obtain the to-be-processed schedule information of the meeting members specified in the meeting addition request to the database.

[0242] S608, the server obtains the to-be-processed schedule information of the meeting members specified in the meeting addition request of the target meeting from the database.

[0243] S610, the server performs an overlap analysis on the time periods corresponding to the schedule information of each meeting member.

[0244] If there is an idle time period without overlap, the following steps S612 - S616 are executed:

[0245] S612, the server sends a request to obtain the meeting time of the historical meeting to the database.

[0246] S614, the server obtains the meeting time of the historical meeting from the database.

[0247] S616, the server determines the meeting time preference according to the meeting time of the historical meeting, and sorts the idle time periods according to the meeting time preference to determine the recommended meeting time period.

[0248] If there is no idle time period without overlap, the following steps S618 - S620 are executed:

[0249] S618, the server sorts each time period according to the degree of overlap of each time period.

[0250] S620, the server eliminates the time periods that meet the time lock condition from the sorting result according to the priority of the meeting corresponding to the time period, and determines the recommended meeting time period according to the sorting result after elimination.

[0251] After executing S616 or S620, the following steps are executed:

[0252] S622, the server sends the recommended meeting time period to the terminal.

[0253] S624, the terminal displays the recommended meeting time period.

[0254] S626, the terminal sends the meeting time period of the target meeting set by the user to the server.

[0255] S628, the server stores the meeting time period of the target meeting in the schedule information of the database.

[0256] This application also provides an application scenario, which is a scenario for adding an online meeting, and this application scenario applies the above - mentioned meeting time recommendation method. Specifically, the application of the meeting time recommendation method in this application scenario is as follows:

[0257] Each team member in the enterprise's team can usually add or modify their personal schedule information on the timeline and can view the schedule information of team members other than themselves. The schedule information includes meeting schedules. The server can store the timeline with the added schedule information.

[0258] When a team member performs an online meeting addition operation through the terminal, during the online meeting addition operation (i.e., adding a meeting schedule), at least one of the meeting duration, meeting type, meeting member information, and meeting priority can be set. The terminal can generate a meeting addition request based on at least one of the meeting duration, meeting type, meeting member information, and meeting priority set by the user and send the meeting addition request to the server. The server can, according to the meeting addition request, obtain the pending schedule information of each meeting member specified in the meeting addition request from the timeline and perform an overlap analysis on the time periods corresponding to the pending schedule information of each meeting member. If there is an idle time period without overlap, recommend the meeting time period of the target meeting from the idle time periods; if there is no idle time period, recommend the meeting time period of the target meeting from the overlapping non-idle time periods according to the degree of overlap between the time periods corresponding to each schedule information.

[0259] Among them, when recommending the meeting time period of the target meeting from the idle time periods, the server can obtain the meeting times of each historical meeting of the team corresponding to the team meeting; according to the obtained meeting times of the historical meetings, predict the degree of meeting time preference of the team for each idle time period, sort the idle time periods according to the degree of meeting time preference, and select the top preset number of idle time periods from them as the recommended meeting time period of the target meeting.

[0260] It can be understood that when recommending the meeting time period of the target meeting from the overlapping non-idle time periods, the server can sort the overlapping non-idle time periods in ascending order of the degree of overlap, and eliminate the non-idle time periods corresponding to the meetings whose priorities meet the time period locking conditions from the sorted non-idle time periods; obtain the meeting time preference of the team corresponding to the target meeting; select the top preset number of non-idle time periods from the remaining non-idle time periods after elimination and recommend the meeting time period of the target meeting from the selected non-idle time periods.

[0261] The server can send the recommended meeting time period of the target meeting to the terminal, and the terminal can display the recommended meeting time period of the target meeting for the team member performing the meeting addition operation to select or refer to. After the team member sets the meeting time period and confirms it, the target meeting is successfully added, and the successfully added target meeting will also be marked on the timeline for storage. Each team member in the team can view the target meeting on the timeline.

[0262] After successfully adding the target meeting, the server can monitor the time. When the time reaches the start time point of the meeting time period of the finally set target meeting, the server can control the terminals used by each meeting member of the target meeting to start the online meeting.

[0263] In one embodiment, the online meeting can be a cloud meeting.

[0264] A cloud meeting is an efficient, convenient, and low-cost meeting form based on cloud computing technology. Users only need to perform simple and easy operations through an Internet interface to quickly and efficiently synchronously share voice, data files, and videos with teams and customers around the world, while complex technologies such as data transmission and processing during the meeting are operated by cloud meeting service providers to help users.

[0265] Currently, domestic cloud meetings mainly focus on service contents with the SaaS (Software as a Service) model as the main body, including service forms such as telephone, network, and video. The video meeting based on cloud computing is called a cloud meeting.

[0266] In the era of cloud meetings, the transmission, processing, and storage of data are all processed by the computer resources of video meeting manufacturers. Users no longer need to purchase expensive hardware and install cumbersome software at all. They only need to open a browser and log in to the corresponding interface to conduct efficient remote meetings.

[0267] The cloud meeting system supports multi-server dynamic cluster deployment and provides multiple high-performance servers, greatly improving the stability, security, and availability of the meeting. In recent years, video meetings have been welcomed by many users because they can significantly improve communication efficiency, continuously reduce communication costs, and bring about an upgrade in internal management level, and have been widely applied in various fields such as government, transportation, finance, operators, education, and enterprises. There is no doubt that after video meetings use cloud computing, they are more attractive in terms of convenience, speed, and ease of use, and will surely trigger the arrival of a new upsurge in video meeting applications.

[0268] This application also provides another application scenario, which is the scenario of adding an offline meeting, and this application scenario applies the above-mentioned meeting time recommendation method. Specifically, the application of the meeting time recommendation method in this application scenario is as follows:

[0269] If the target meeting to be added is an offline meeting, the server can recommend the meeting time period of the offline target meeting to the user who performs the meeting addition operation according to the meeting time recommendation method in the embodiments of the present application. The user can add the offline target meeting according to the recommended meeting time period, and can also reserve the meeting venue for the offline meeting. After successfully adding the target meeting, the server can monitor the time. When the time reaches the start time point of the meeting time period of the finally set target meeting, or within the preset time range before the start time point, the server can notify the terminals used by each meeting member to prompt the meeting members to participate in the target meeting offline. After receiving the notification through the terminal, the meeting members can arrive at the meeting venue by themselves to participate in the meeting.

[0270] It should be understood that although the steps in each flowchart are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless there is a clear description in this article, the execution of these steps has no strict order limit, and these steps can be executed in other orders. Moreover, at least a part of the steps in each flowchart may include multiple steps or multiple stages. These steps or stages are not necessarily executed at the same moment, but can be executed at different moments. The execution order of these steps or stages is not necessarily sequential, but can be executed alternately or alternately with at least a part of other steps or steps or stages in other steps.

[0271] In one embodiment, as Figure 7 shown, a meeting time recommendation device 700 is provided. This device can be a software module, a hardware module, or a combination of both to become a part of a computer device. Specifically, the device includes: a request receiving module 702, a schedule information obtaining module 704, an overlap analysis module 706, and a meeting time recommendation module 708, where:

[0272] The request receiving module 702 is configured to receive a meeting addition request for a target meeting.

[0273] The schedule information obtaining module 704 is configured to obtain the to-be-processed schedule information of each meeting member specified in the meeting addition request.

[0274] The overlap analysis module 706 is configured to perform overlap analysis on the time periods corresponding to the schedule information of each meeting member.

[0275] The meeting time recommendation module 708 is configured to recommend the meeting time period of the target meeting from the idle time periods if there are non-overlapping idle time periods.

[0276] The meeting time recommendation module 708 is further configured to recommend a meeting time period for the target meeting from the overlapping non-idle time periods according to the overlapping degree between the time periods corresponding to each schedule information if there is no idle time period.

[0277] In one embodiment, the schedule information acquisition module 704 is further configured to acquire a timeline with schedule information added; acquire the to-be-processed schedule information of each meeting member specified in the meeting addition request from the schedule information added on the timeline. The overlap analysis module 706 is further configured to determine the time periods corresponding to the acquired schedule information on the timeline; perform an overlap analysis on the determined time periods.

[0278] In one embodiment, the overlap analysis module 706 is further configured to exhaustively divide the determined time periods into pairs; sequentially compare each time point corresponding to the two time periods in each pair; determine the time period composed of the time points with consistent comparison results as the overlapping non-idle time period, and determine the time periods other than the non-idle time periods on the timeline as the non-overlapping idle time periods.

[0279] In one embodiment, the overlap analysis module 706 is further configured to add the start time points of the determined time periods to the first set; add the end time points of the determined time periods to the second set; sequentially select the current time period from the determined time periods, and for each current time period, select a candidate start time point from the first set and a candidate end time point from the second set; wherein, the candidate start time point is less than or equal to the end time point of the current time period; the candidate end time point is greater than or equal to the start time point of the current time period; select the time period corresponding to the candidate start time point and the candidate end time point from the determined time periods other than the current time period as the non-idle time period overlapping with the current time period; determine the time periods other than the non-idle time periods corresponding to the determined time periods on the timeline as the non-overlapping idle time periods.

[0280] In one embodiment, the meeting addition request includes the meeting duration of the target meeting. The meeting time recommendation module 708 is further configured to recommend a meeting time period for the target meeting from the non-overlapping idle time periods that meet the meeting duration if there are non-overlapping idle time periods that meet the meeting duration. The meeting time recommendation module 708 is further configured to recommend a meeting time period for the target meeting that meets the meeting duration from the overlapping non-idle time periods according to the overlapping degree between the time periods corresponding to each schedule information if there are no non-overlapping idle time periods that meet the meeting duration.

[0281] In one embodiment, the target meeting is a team meeting. The meeting time recommendation device 700 further includes:

[0282] A preference prediction module 710 is configured to obtain the meeting times of various historical meetings of the team corresponding to the team meeting; and predict the meeting time preference of the team according to the obtained meeting times of the historical meetings. The meeting time recommendation module 708 is further configured to recommend a meeting time period of the target meeting from the idle time periods according to the meeting time preference.

[0283] In one embodiment, the meeting addition request includes a target meeting type of the target meeting. The meeting time preference prediction module 710 is further configured to obtain the meeting times of the historical meetings belonging to the target meeting type participated by the team for the team corresponding to the team meeting; and predict the meeting time preference of the team for the meetings of the target meeting type according to the obtained meeting times of the historical meetings.

[0284] In one embodiment, the meeting time recommendation module 708 is further configured to sort the overlapping non-idle time periods in ascending order of the overlapping degree according to the overlapping degree between the time periods corresponding to the respective schedule information; and recommend a meeting time period of the target meeting according to the top preset number of non-idle time periods.

[0285] In one embodiment, the schedule information includes a meeting schedule. The meeting schedule includes the priority of the corresponding meeting. The meeting time recommendation module 708 is further configured to recommend a meeting time period of the target meeting from the overlapping non-idle time periods according to the overlapping degree between the time periods corresponding to the respective meeting schedules and the priority of the meeting corresponding to the meeting schedule.

[0286] In one embodiment, the meeting time recommendation module 708 is further configured to sort the non-idle time periods in ascending order of the overlapping degree according to the overlapping degree between the time periods corresponding to the respective meeting schedules; exclude the non-idle time periods whose corresponding meeting priorities meet the time period locking condition from the sorted non-idle time periods according to the priorities of the meetings corresponding to the non-idle time periods; select the top preset number of non-idle time periods from the remaining non-idle time periods after exclusion; and recommend a meeting time period of the target meeting according to the selected non-idle time periods.

[0287] In one embodiment, the target meeting is a team meeting. The meeting time recommendation module 708 is further configured to obtain the meeting time preference of the team corresponding to the target meeting; and recommend a meeting time period of the target meeting from the selected non-idle time periods according to the meeting time preference.

[0288] In one embodiment, the meeting addition request includes a recommended meeting duration. The target meeting is a team meeting. As Figure 8 shown, the meeting time recommendation apparatus 700 further includes:

[0289] The meeting duration recommendation module 712 is used to determine the meeting duration preference of a team based on the meeting durations of the historical meetings of the team corresponding to the team meeting; and recommend the meeting duration of the target meeting according to the meeting duration preference.

[0290] In the above meeting time recommendation device, the to-be-processed schedule information of each meeting member specified in the meeting addition request is obtained, and then the overlapping analysis is performed on the time periods corresponding to the schedule information of each meeting member, so as to automatically determine whether there is an idle time period between the time periods of the schedule information of each meeting member. If there is an idle time period without overlap, the meeting time period of the target meeting is recommended from the idle time periods. In this way, without communicating with each meeting member, the idle time period can be quickly recommended, and the meeting time can be arranged efficiently; if there is no idle time period, then according to the overlapping degree between the time periods corresponding to each schedule information, the meeting time period of the target meeting is recommended from the overlapping non-idle time periods. In this way, in the case of no idle time period, without communicating with each meeting member separately, the meeting time period can be automatically recommended from the non-idle time periods according to the overlapping degree, and the meeting time can be arranged efficiently, thereby improving the efficiency of meeting addition.

[0291] For the specific limitations of the meeting time recommendation device, reference can be made to the limitations of the meeting time recommendation method in the above text, which will not be elaborated here. Each module in the above meeting time recommendation device can be implemented in whole or in part by software, hardware and their combination. The above modules can be embedded in the processor of the computer device in the form of hardware or independent of it, or stored in the memory of the computer device in the form of software, so that the processor can call and execute the operations corresponding to the above modules.

[0292] In one embodiment, a computer device is provided. The computer device can be a server, and its internal structure diagram can be as Figure 9 shown. The computer device includes a processor, a memory and a network interface connected through a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store schedule information data. The network interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, it implements a meeting time recommendation method.

[0293] In one embodiment, a computer device is provided. The computer device can be a terminal, and its internal structure diagram can be as Figure 10As shown in the figure. The computer device includes a processor, a memory, a communication interface, a display screen, and an input device connected by a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage medium. The communication interface of the computer device is used to communicate with an external terminal in a wired or wireless manner. The wireless manner can be achieved through WIFI, a carrier network, NFC (Near Field Communication), or other technologies. When the computer program is executed by the processor, it implements a meeting time recommendation method. The display screen of the computer device can be a liquid crystal display screen or an electronic ink display screen. The input device of the computer device can be a touch layer covering the display screen, or a button, a trackball, or a touchpad provided on the outer shell of the computer device, or an external keyboard, touchpad, or mouse, etc.

[0294] Those skilled in the art can understand that Figure 9 and Figure 10 the structure shown in the figure is only a block diagram of some structures related to the solution of this application, and does not constitute a limitation on the computer device to which the solution of this application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine some components, or have a different component layout.

[0295] In one embodiment, a computer device is further provided, including a memory and a processor. A computer program is stored in the memory. When the processor executes the computer program, the steps in the above method embodiments are implemented.

[0296] In one embodiment, a computer-readable storage medium is provided, storing a computer program. When the computer program is executed by the processor, the steps in the above method embodiments are implemented.

[0297] In one embodiment, a computer program product or a computer program is provided. The computer program product or the computer program includes computer instructions, and the computer instructions are stored in a computer-readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the steps in the above method embodiments.

[0298] Those of ordinary skill in the art can understand that all or part of the processes in the methods of the above embodiments can be completed by instructing relevant hardware through a computer program. The computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above various methods. Among them, any reference to a memory, storage, database, or other medium used in the various embodiments provided in the present application can include at least one of non-volatile and volatile memories. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, or optical memory, etc. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM), etc.

[0299] The technical features of the above embodiments can be combined arbitrarily. For the sake of brevity of description, not all possible combinations of the various technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, it should be considered as the scope described in this specification.

[0300] The above-described embodiments merely represent several implementation manners of the present application. Their descriptions are relatively specific and detailed, but they should not be construed as limiting the scope of the invention patent. It should be noted that for those of ordinary skill in the art, without departing from the concept of the present application, several modifications and improvements can still be made, and these all belong to the protection scope of the present application. Therefore, the protection scope of the patent of the present application shall be subject to the appended claims.

Claims

1. A method for recommending meeting time, characterized in that, The method includes: Receiving a meeting addition request for a target meeting; Obtaining a timeline with schedule information added, where the schedule information added on the timeline is obtained from nodes of a blockchain; Obtaining, from the schedule information added on the timeline, the to-be-processed schedule information of each meeting member specified in the meeting addition request; Determining, on the timeline, the time periods corresponding to the obtained schedule information, where each of the time periods includes respective start time points and end time points in the timeline; Adding the start time points of the determined time periods to a first set; Adding the end time points of the determined time periods to a second set; Sequentially selecting a current time period from the determined time periods, and for each of the current time periods, selecting a candidate start time point from the first set and a candidate end time point from the second set; wherein, the candidate start time point is less than or equal to the end time point of the current time period; the candidate end time point is greater than or equal to the start time point of the current time period; Selecting, from the determined time periods other than the current time period, the time periods corresponding to the candidate start time point and the candidate end time point, and determining them as non-idle time periods overlapping with the current time period; determining the time periods on the timeline other than the non-idle time periods corresponding to the determined time periods as non-overlapping idle time periods; If there are non-overlapping idle time periods, determining, from the idle time periods, the final idle time with a duration greater than or equal to a meeting duration threshold, and recommending, according to the priority of the target meeting, the meeting time period of the target meeting from the final idle time; If there are no such idle time periods and the target meeting is a team meeting, determining target meeting members among the meeting members of the team meeting whose team identity priorities are in the top preset positions; Determining, from the time periods corresponding to the schedule information of each meeting member of the team meeting, the time periods other than the time periods corresponding to the schedule information of the target meeting members; When the overlap degree between the time period corresponding to the schedule information of a non-target meeting member and the determined time period is not greater than a preset threshold, recommending, according to the overlap degree between the time period corresponding to the schedule information of the non-target meeting member and the determined time period and the priority of the target meeting, the time period of the target meeting from the determined time period; When the overlap degree between the time period corresponding to the schedule information of the non-target meeting member and the determined time period is greater than the preset threshold, recommending, according to the overlap degree between the time periods corresponding to the schedule information of each meeting member in the team meeting and the priority of the target meeting, the meeting time period of the target meeting from the overlapping non-idle time periods; Wherein, the non-target meeting members include the meeting members other than the target meeting members in the team meeting, and the overlap degree includes the number of overlaps between the time periods corresponding to each schedule information.

2. The method according to claim 1, characterized in that, The method further includes: Exhaustively dividing the determined time periods into pairs. Compare each time point corresponding to the two time periods of each group in sequence; Determine the overlapping non-idle time period composed of the time points with consistent comparison results, and determine the time period other than the non-idle time period on the time axis as the non-overlapping idle time period.

3. The method according to claim 1, characterized in that, The meeting addition request includes the meeting duration of the target meeting; the method further includes: If there is a non-overlapping idle time period that meets the meeting duration, recommend the meeting time period of the target meeting from the idle time periods that meet the meeting duration; If there is no idle time period that meets the meeting duration, recommend the meeting time period of the target meeting that meets the meeting duration from the overlapping non-idle time periods according to the overlapping degree between the time periods corresponding to each schedule information.

4. The method according to claim 1, characterized in that, The method further includes: Obtain the meeting times of each historical meeting of the team corresponding to the team meeting; Predict the meeting time preference of the team according to the obtained meeting times of the historical meetings; The recommending the meeting time period of the target meeting from the final idle time according to the priority of the target meeting includes: Recommend the meeting time period of the target meeting from the final idle time period according to the meeting time preference and the priority of the target meeting.

5. The method according to claim 4, characterized in that, The meeting addition request includes the target meeting type of the target meeting; The obtaining the meeting times of each historical meeting of the team corresponding to the team meeting includes: For the team corresponding to the team meeting, obtain the meeting times of the historical meetings participated by the team that belong to the target meeting type; The predicting the meeting time preference of the team according to the obtained meeting times of the historical meetings includes: Predict the meeting time preference of the team for the meetings of the target meeting type according to the obtained meeting times of the historical meetings.

6. The method according to claim 1, characterized in that, The recommending the meeting time period of the target meeting from the overlapping non-idle time periods according to the overlapping degree between the time periods corresponding to the schedule information of each meeting member in the team meeting and the priority of the target meeting includes: Sort the overlapping non-idle time periods in ascending order of the overlapping degree according to the overlapping degree between the time periods corresponding to the schedule information of each meeting member in the team meeting and the priority of the target meeting; Recommend the meeting time period of the target meeting according to the previous preset number of non-idle time periods.

7. The method according to claim 1, characterized in that, The schedule information includes a meeting schedule; The recommending the meeting time period of the target meeting from the overlapping non-idle time periods according to the overlapping degree between the time periods corresponding to the schedule information of each meeting member in the team meeting and the priority of the target meeting includes: Recommend the meeting time period of the target meeting from the overlapping non-idle time periods according to the overlapping degree between the time periods corresponding to each meeting schedule and the priority of the meeting corresponding to the meeting schedule.

8. The method according to claim 7, characterized in that, Recommending a meeting time period for the target meeting from the overlapping non-idle time periods according to the degree of overlap between the time periods corresponding to each of the meeting schedules and the priority of the meeting corresponding to the meeting schedule includes: Sorting each of the non-idle time periods in ascending order of the degree of overlap according to the degree of overlap between the time periods corresponding to each of the meeting schedules; Excluding, from the sorted non-idle time periods, the non-idle time periods for which the priority of the meeting corresponding to the non-idle time period meets the time period locking condition according to the priority of the meeting corresponding to the meeting schedule corresponding to each of the non-idle time periods; Selecting a preset number of non-idle time periods from the remaining non-idle time periods after exclusion; Recommending a meeting time period for the target meeting according to the selected non-idle time periods.

9. The method according to claim 8, characterized in that, The recommending a meeting time period for the target meeting according to the selected non-idle time periods includes: Obtaining the meeting time preference of the team corresponding to the target meeting; Recommending a meeting time period for the target meeting from the selected non-idle time periods according to the meeting time preference.

10. The method according to any one of claims 1 to 9, characterized in that, The meeting addition request includes the recommended meeting duration; Before receiving the meeting addition request for the target meeting, the method further includes: Determining the meeting duration preference of the team according to the meeting duration of the historical meetings of the team corresponding to the team meeting; Recommending the meeting duration of the target meeting according to the meeting duration preference.

11. A meeting time recommendation device, characterized in that, The apparatus includes: A request receiving module, configured to receive a meeting addition request for a target meeting; A schedule information obtaining module, configured to obtain a time axis with schedule information added, where the schedule information added on the time axis is obtained from nodes of a blockchain; and obtaining, from the schedule information added on the time axis, the to-be-processed schedule information of each meeting member specified in the meeting addition request; An overlap analysis module, configured to determine, on the time axis, the time periods corresponding to the obtained schedule information, where each of the time periods includes its respective start time point and end time point in the time axis; adding the start time points of the determined time periods to a first set; adding the end time points of the determined time periods to a second set; sequentially selecting, from the determined time periods, a current time period, and for each current time period, selecting a candidate start time point from the first set and a candidate end time point from the second set; where the candidate start time point is less than or equal to the end time point of the current time period; the candidate end time point is greater than or equal to the start time point of the current time period; selecting, from the determined time periods other than the current time period, the time periods corresponding to the candidate start time point and the candidate end time point, and determining them as non-idle time periods overlapping with the current time period; and determining the time periods on the time axis other than the non-idle time periods corresponding to the determined time periods as idle time periods without overlap; A meeting time recommendation module, which is used to, if there are non-overlapping idle time periods, determine the final idle time with a duration greater than or equal to the meeting duration threshold from the idle time periods, and recommend the meeting time period of the target meeting from the final idle time according to the priority of the target meeting; The meeting time recommendation module is further used to, if there are no such idle time periods and the target meeting is a team meeting, determine the target meeting members whose team identity priorities are in the top preset positions among the members of the team meeting; determine the time periods other than the time periods corresponding to the schedule information of the target meeting members from the time periods corresponding to the schedule information of the members of the team meeting; when the overlap degree between the time periods corresponding to the schedule information of the non-target meeting members and the determined time period is not greater than the preset threshold, recommend the time period of the target meeting from the determined time period according to the overlap degree between the time periods corresponding to the schedule information of the non-target meeting members and the determined time period and the priority of the target meeting; when the overlap degree between the time periods corresponding to the schedule information of the non-target meeting members and the determined time period is greater than the preset threshold, recommend the meeting time period of the target meeting from the overlapping non-idle time periods according to the overlap degree between the time periods corresponding to the schedule information of the members of the team meeting and the priority of the target meeting; wherein, the non-target meeting members include the meeting members other than the target meeting members in the team meeting, and the overlap degree includes the number of overlaps between the time periods corresponding to each schedule information.

12. The device according to claim 11, characterized in that, The overlap analysis module is further used to exhaustively divide each of the determined time periods into pairs; sequentially compare each time point corresponding to the two time periods in each pair; determine the time period composed of the time points with consistent comparison results as the overlapping non-idle time period, and determine the time period other than the non-idle time period on the time axis as the non-overlapping idle time period.

13. The device according to claim 11, characterized in that, The meeting addition request includes the meeting duration of the target meeting; The meeting time recommendation module is further used to, if there are non-overlapping idle time periods that meet the meeting duration, recommend the meeting time period of the target meeting from the idle time periods that meet the meeting duration; if there are no idle time periods that meet the meeting duration, recommend the meeting time period of the target meeting that meets the meeting duration from the overlapping non-idle time periods according to the overlap degree between the time periods corresponding to each schedule information.

14. The device according to claim 11, characterized in that, The device further includes: A preference prediction module, which is used to obtain the meeting times of each historical meeting of the team corresponding to the team meeting; predict the meeting time preference of the team according to the obtained meeting times of the historical meetings; The meeting time recommendation module is further used to recommend the meeting time period of the target meeting from the final idle time periods according to the meeting time preference and the priority of the target meeting.

15. The device according to claim 14, characterized in that, The meeting addition request includes the target meeting type of the target meeting; The preference prediction module is further configured to obtain the meeting times of historical meetings of the team that belong to the target meeting type and are participated in by the team corresponding to the team meeting; and predict the meeting time preference of the team for meetings of the target meeting type according to the obtained meeting times of the historical meetings.

16. The device according to claim 11, wherein The meeting time recommendation module is further configured to sort the overlapping non-idle time periods in ascending order of the degree of overlap according to the degree of overlap between the time periods corresponding to the schedule information of each meeting member in the team meeting and the priority of the target meeting; and recommend the meeting time period of the target meeting according to the first preset number of the non-idle time periods.

17. The device according to claim 11, wherein The schedule information includes meeting schedules. The meeting time recommendation module is further configured to recommend the meeting time period of the target meeting from the overlapping non-idle time periods according to the degree of overlap between the time periods corresponding to the meeting schedules and the priority of the meetings corresponding to the meeting schedules.

18. The device according to claim 17, wherein The meeting time recommendation module is further configured to sort the non-idle time periods in ascending order of the degree of overlap according to the degree of overlap between the time periods corresponding to the meeting schedules; remove the non-idle time periods whose corresponding meeting priorities meet the time period locking condition from the sorted non-idle time periods according to the priorities of the meetings corresponding to the non-idle time periods; select the first preset number of non-idle time periods from the remaining non-idle time periods after removal; and recommend the meeting time period of the target meeting according to the selected non-idle time periods.

19. The device according to claim 11, wherein The meeting time recommendation module is further configured to obtain the meeting time preference of the team corresponding to the target meeting; and recommend the meeting time period of the target meeting from the selected non-idle time periods according to the meeting time preference.

20. The device according to claim 19, wherein The meeting addition request includes the recommended meeting duration; the apparatus further includes: A meeting duration recommendation module, configured to determine the meeting duration preference of the team according to the meeting durations of the historical meetings of the team corresponding to the team meeting; and recommend the meeting duration of the target meeting according to the meeting duration preference.

21. A computer device, comprising a memory and a processor, the memory storing a computer program, wherein When the processor executes the computer program, the steps of the method according to any one of claims 1 to 10 are implemented.

22. A computer-readable storage medium storing a computer program, wherein When the computer program is executed by the processor, the steps of the method according to any one of claims 1 to 10 are implemented.

23. A computer program product comprising a computer program, wherein When the computer program is executed by the processor, the steps of the method according to any one of claims 1 to 10 are implemented.

Images