Method and apparatus for setting schedule authority, electronic device, and storage medium

Abstract

The present disclosure provides a method and apparatus for setting schedule permissions and an electronic device. The method includes displaying a permission setting prompt message when detecting a preset trigger event, and setting schedule permissions in response to an operation of executing the setting of schedule permissions. The method provided by the present disclosure timely reminds the user to set schedule permissions when detecting a preset trigger event, thereby avoiding the threat to schedule order management caused by untimely setting of schedule permissions, improving the efficiency of schedule order management, reducing schedule risks, and thus improving the user's schedule experience.

Description

Technical Field

[0001] [Cross - reference to Related Applications] This application is based on and claims priority to a Chinese application with the application number 202211486206.0 and titled "Method and Apparatus for Setting Schedule Permissions, Electronic Device, and Storage Medium" filed on November 24, 2022. The disclosure content of this Chinese application is incorporated into this application as a whole.

[0002] This disclosure relates to the field of computer technology, and particularly to a method and apparatus for setting schedule permissions, an electronic device, and a storage medium.

Background Art

[0003] Due to the rapid development of the Internet and multimedia technologies, multimedia conferences such as voice conferences and video conferences with excellent real - time performance and interactivity are widely applied. In the case of multimedia conferences, depending on the situation, the need to manage conference permissions (such as speaking permissions, sharing permissions, etc.) is increasing. If the conference permission management is not appropriate, uninvited users may participate in the conference, disrupting the conference order and threatening the conference security.

[0004] In related technologies, it is often the case that the conference permissions of participants are set and managed consciously and voluntarily through the moderator. However, when the number of participants is large or the moderator lacks experience, it is often impossible to manage the conference permissions of participants in a timely manner, resulting in poor management efficiency of the conference order.

Summary of the Invention

[0005] According to one aspect of this disclosure, a method for setting schedule permissions is provided. The method includes displaying a permission - setting prompt message when detecting a preset trigger event, and setting schedule permissions in response to an operation of executing the setting of schedule permissions.

[0006] According to another aspect of the present disclosure, a method for setting schedule permissions is provided. The method includes receiving schedule progress information from a client, determining that a preset trigger event occurs for the client based on the schedule progress information, and setting schedule permissions based on a permission setting recommendation policy.

[0007] According to another aspect of the present disclosure, a device for setting schedule permissions is provided. The device includes a display module for displaying a permission setting prompt message when detecting a preset trigger event, and a setting module for setting schedule permissions in response to an operation of executing the setting of schedule permissions.

[0008] According to another aspect of the present disclosure, a device for setting schedule permissions is provided. The device includes a communication module for receiving schedule progress information from a client, and a setting module for determining that a preset trigger event occurs for the client based on the schedule progress information and setting schedule permissions based on a permission setting recommendation policy.

[0009] According to another aspect of the present disclosure, an electronic device is provided. The electronic device includes a processor and a memory storing a program. The program includes instructions which, when executed by the processor, cause the processor to execute the method described in the exemplary embodiments of the present disclosure.

[0010] According to another aspect of the present disclosure, a non-transitory computer-readable storage medium storing computer instructions is provided. The computer instructions are used to cause a computer to execute the method described in the exemplary embodiments of the present disclosure.

[0011] One or more technical solutions provided in the exemplary embodiments of the present disclosure can display an authority setting prompt message when detecting a preset trigger event, and the displayed authority setting prompt message can timely remind the user to set the current schedule authority. Based on this, in response to the setting operation for the current schedule authority, the current schedule authority can be set. Obviously, the method of the exemplary embodiments of the present disclosure can timely remind the user to set the schedule authority when detecting the preset trigger event, thereby improving the schedule management efficiency and avoiding the chaos of the schedule order caused by the untimely setting of the schedule authority.

Brief Description of the Drawings

[0012] Hereinafter, exemplary embodiments will be described in conjunction with the drawings, and further details, features, and advantages of the present disclosure will be disclosed.

[0013]

Figure 1

Figure 2

Figure 3A

Figure 3B

Figure 3C

Figure 4A

Figure 4B

Figure 5

Figure 6A

Figure 6B

Figure 6C

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Embodiments for Carrying Out the Invention

[0014] Hereinafter, embodiments of the present disclosure will be described in more detail with reference to the drawings. Although several embodiments of the present disclosure are shown in the drawings, the present disclosure can be realized in various forms and should not be construed as limited to the embodiments described herein. On the contrary, it should be understood that providing these embodiments is for a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are merely for illustrative purposes and do not limit the protection scope of the present disclosure.

[0015] It should be understood that each step described in the embodiments of the method of the present disclosure may be executed in a different order and / or executed in parallel. In addition, the embodiments of the method may include additional steps and / or may be executed by omitting the steps shown. The scope of the present disclosure is not limited in this regard.

[0016] As used herein, the term "comprising" and its variations are non-limiting "including", that is, "including... but not limited to it (them)". The term "based on" means "at least partially based on". The term "an embodiment" represents "at least one embodiment". The term "another embodiment" represents "at least one another embodiment". The term "some embodiments" represents "at least some embodiments". Related definitions of other terms are given in the following description. It should be noted that the concepts such as "first", "second", etc. mentioned in the present disclosure are only for distinguishing different devices, modules or units, and are not for limiting the order or interdependence of the functions executed by these devices, modules or units.

[0017] It should be noted that the modifications of "one" and "a plurality" mentioned in the present disclosure are exemplary and not restrictive. As understood by those skilled in the art, unless otherwise clearly specified in the context, it should be understood as "one or a plurality".

[0018] The names of the messages or information that interact between multiple devices in the embodiments of the present disclosure are for illustrative purposes only and are not for limiting the scope of these messages or information.

[0019] Before introducing the embodiments of the present disclosure, first, the related nouns related to the embodiments of the present disclosure are interpreted as follows.

[0020] A schedule refers to the plan and arrangement for a certain point in time or period, such as one day, one week, or one month. A schedule can be realized in various possible forms, such as video conferences, voice calls, and text communications. In this case, the schedule may be a meeting schedule. Taking a general web conference as an example, the initiator of the meeting can create a web conference by adding participants and reserving the meeting period, and can send the web conference link to the participants. When the reserved meeting start time arrives, the participants can enter the schedule and enter the web conference room to participate in the meeting by clicking on the web conference link, scanning the schedule invitation code, or entering the schedule number, etc.

[0021] When the speaker is speaking, if the speaking rights of other participants are not managed in a timely manner, the noise in the meeting room will be loud and the speaker's voice will not be heard clearly. As another example, when the speaker is sharing a file, if the sharing rights of the participants are not managed in a timely manner, the shared screen will be preempted and the meeting will be interrupted. Moreover, during the progress of the schedule, it is common for uninvited users to enter the schedule and talk, chat, share files, or change markups at will, disrupting the order management of the schedule and threatening the safety of the schedule.

[0022] In related technologies, in order to manage the order of the meeting, the administrator needs to consciously and voluntarily set and manage the meeting rights of the participants. However, the administrator needs to set them consciously and cannot manage the meeting rights of the participants in a timely manner, and the efficiency of schedule order management is often poor.

[0023] The inventors have discovered that as the number of participants increases, the proportion of participants who need to manage meeting permissions such as speaking permissions and sharing permissions also increases, making it difficult to manage the schedule order. Therefore, in order to solve the technical problem that the schedule order management is not efficient because the meeting permission management of participants is not timely, exemplary embodiments of the present disclosure provide a method for setting schedule permissions, which timely reminds the user to set schedule permissions when detecting a preset trigger event, thereby avoiding the threat to schedule order management caused by the untimely setting of schedule permissions, improving the efficiency of schedule management, and thus improving the user's schedule experience.

[0024] The method for setting schedule permissions according to the exemplary embodiments of the present disclosure can be applied to various scenarios available for schedule permission setting. FIG. 1 is a schematic diagram of an exemplary system capable of implementing various methods described herein according to the exemplary embodiments of the present disclosure. As shown in FIG. 1, the application scenario 100 according to the exemplary embodiments of the present disclosure includes a first terminal 110, a second terminal 120, a server 130, and a data storage system 140.

[0025] In actual applications, as shown in FIG. 1, both the first terminal 110 and the second terminal 120 install clients capable of participating in the schedule, but other clients can also be installed. Here, the client can be any client capable of participating in the schedule, including a schedule client, a live client, a chat site, etc., and will not be listed one by one here.

[0026] The clients installed on the first terminal 110 and the second terminal 120 may be the same type of applications based on the same or different operating system platforms (such as Android, IOS, Huawei Hongmeng system, etc.). The first terminal 110 may be the starting terminal of the schedule, or the second terminal 120 may be the target terminal corresponding to other users participating in the schedule. The number of the second terminals 120 may be one or multiple, which is determined according to the actual application scenario. The exemplary embodiments of the present disclosure are only shown with respect to the first terminal 110 and the second terminal 120. The device types of the first terminal 110 and the second terminal 120 may be the same or different, and the device types include at least one of smartphones, tablet PCs, laptop computers, and desktop computers.

[0027] As shown in FIG. 1, the above-mentioned first terminal 110 and second terminal 120 can communicate with the server 130 via a communication network. In terms of the communication method, the communication network may be classified as a wireless communication network such as satellite communication and microwave communication, or may be a wired communication network such as optical fiber communication and power line carrier communication. In terms of the communication range, the communication network may be a local communication network such as a Wifi or Zigbee communication network, or may be a wide area communication network such as the Internet network.

[0028] As shown in FIG. 1, the server 130 may be a single server, or a server cluster or distributed system composed of multiple servers, and may 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, content delivery networks (CDNs), and big data and artificial intelligence platforms. The data storage system 140 may be a general term and includes a local memory and a database for storing historical data. The data storage system 140 may be separate from the server 130 or may be incorporated into the server 130.

[0029] In actual applications, the user corresponding to the first terminal 110 is the first user, the first user is the schedule start user, the user corresponding to the second terminal 120 is the second user, and the second user is the schedule participating user. The first user and the second user each log in to the server 130 by entering their usernames and passwords via the first terminal 110 and the second terminal 120 respectively. The server 130 reads the user database to verify the user's identity. If both the username and password are correct, a mark indicating that the user has successfully logged in is displayed. The first user can open a schedule by inviting at least one second user into the meeting room in a group chat manner. The first user and the second user may enter the meeting room and participate in the schedule by clicking on the schedule link, scanning the schedule invitation code, entering the schedule number, etc.

[0030] The first user can set schedule permissions in the permission setting interface of the first terminal 110. The first terminal 110 responds to the user's setting operation for schedule permissions, sets the schedule permissions, and obtains schedule permission setting information. At the same time, the first terminal 110 sends the schedule permission setting information to the server 130. The server 130 sends the schedule permission setting information to the second terminal 120. After receiving the schedule permission setting information, the second terminal 120 sets the schedule permissions based on the schedule permission setting information. Also, schedule permissions can be set in the server 130. The server 130 sends the set schedule permission setting information to the first terminal 110 and the second terminal 120. After receiving the schedule permission setting information, the first terminal 110 and the second terminal 120 set the schedule permissions based on the schedule permission setting information.

[0031] In the method of the exemplary embodiments of the present disclosure, when a preset trigger event is detected, the setting operation for schedule permissions can be performed either on the client or on the server. When the setting operation for schedule permissions is performed on the client, the permission setting prompt message for the preset trigger event may be directly displayed on the client, or may be displayed after receiving the permission setting prompt message from the server.

[0032] When the setting operation for schedule permissions is performed on the client, the schedule permission setting method according to the exemplary embodiments of the present disclosure can be executed by the client. The client in the exemplary embodiments of the present disclosure may be a schedule client (multimedia conference terminal), or may be a schedule control terminal (a control terminal for controlling a multimedia conference), and is not particularly limited here. Figure 2 is an exemplary flowchart of the schedule permission setting method according to the exemplary embodiments of the present disclosure. As shown in Figure 2, the schedule permission setting method according to the exemplary embodiments of the present disclosure may include the following steps. Step 201: When a preset trigger event is detected, display a permission setting prompt message. The schedule in the exemplary embodiment of the present disclosure may be a meeting schedule, and the timing for detecting the preset trigger event may be before the start of the meeting schedule or during the progress of the meeting schedule.

[0033] The above preset trigger event can support setting and updating. That is, according to the actual schedule scenario, the preset trigger event can be flexibly set. At this time, considering that the preset trigger events for triggering schedule permission management may be different in different schedule scenarios, the preset trigger event that has been set can be updated to match the current schedule scenario with the updated preset trigger event. Therefore, the exemplary embodiment of the present disclosure realizes diverse management of schedule permissions by flexibly setting the preset trigger event, improves the compatibility between the schedule permission and the current schedule scenario, and thereby improves the efficiency of schedule management.

[0034] Step 202: In response to a setting operation for schedule permissions, set the schedule permissions. The user can set the schedule permissions based on the permission setting recommendation information in the permission setting interface, so that the set schedule permissions match the permission recommendation policy, reduce the risk during the schedule progress, and ensure the safety of the schedule. It should be understood that the user here may be a schedule creator, a schedule moderator, or a co-moderator, or one or several designated users. The above setting for schedule permissions may be a setting for a certain schedule permission or a setting for multiple schedule permissions.

[0035] Obviously, the method provided by the exemplary embodiments of the present disclosure can display a permission setting prompt message when detecting a preset trigger event, and the displayed permission setting prompt message can timely remind the user to set the current schedule permission. Based on this, in response to the setting operation for the current schedule permission, the current schedule permission can be set. Obviously, the method of the exemplary embodiments of the present disclosure can timely remind the user to set the schedule permission when detecting a preset trigger event, thereby improving the schedule management efficiency, reducing the scale risk, and avoiding the chaos of the schedule order caused by the untimely setting of the schedule permission.

[0036] In an optional embodiment, step 201 may include displaying a permission setting prompt message on the client interface of the first user having the schedule setting permission when detecting a preset trigger event, so that the first user and / or the second user designated by the first user can set the schedule permission. Note that the first user is a user having the schedule setting permission, and may be a schedule creator or a schedule moderator. The second user may be a co-moderator designated by the first user, another schedule participant, a schedule control terminal, or a server. The second user also has the schedule setting permission, but the authorization of the first user is required for the effectiveness of the second user's schedule setting permission.

[0037] For example, in a class scenario, when a preset trigger event is detected, a permission setting prompt message pops up on the teacher's client interface. If the teacher directly performs permission setting, the progress of the class is interrupted. At this time, the teacher authorizes the co-host or other users with schedule setting permissions in the form of a notice, and allows the co-host or other users to set the schedule permissions. The teacher can also send a schedule permission setting command to the schedule control terminal or the server, and request the schedule control terminal or the server to set the schedule permissions. Obviously, in the method according to the exemplary embodiments of the present disclosure, the first user can authorize the second user with schedule setting permissions, and the second user can realize the setting of schedule permissions, thereby enhancing the security of the schedule without interfering with the schedule progress.

[0038] In a selectable embodiment, the preset trigger event may include at least one of the following: the number of schedule participants is greater than or equal to a predetermined number, there are participants with a predetermined identity among the schedule participants, the schedule nature is a preset schedule nature, the permission status does not match the permission setting recommendation policy, and the display times of the permission setting prompt message are less than a predetermined number.

[0039] When the preset trigger event includes that the number of schedule participants is equal to or more than a predetermined number, the predetermined number may be the predetermined number of schedule participants, or the predetermined number of schedule participants recommended by the client, or the predetermined number of schedule participants determined by the user based on experience, or the predetermined number of schedule participants determined by the user according to the needs of the schedule scenario. Specifically, it is determined based on the actual application scenario, which is not limited here. In the same schedule, when the number of schedule participants is equal to or more than a predetermined number, the order of the schedule may be disrupted. Therefore, when it is detected that the number of schedule participants is equal to or more than a predetermined number, the displayed permission setting prompt message timely reminds the user to set the current schedule permission, reduces the risk of the schedule, and avoids the disruption of the schedule order due to the untimely setting of the schedule permission.

[0040] In the following, in order to make the realization process of the method of the exemplary embodiment of the present disclosure easier to understand, with reference to the drawings, the realization process of the method of the exemplary embodiment of the present disclosure will be described. It should be understood that the following realization process is for illustrative purposes only and is not limiting.

[0041] FIG. 3A is a schematic diagram of a schedule creation page according to an exemplary embodiment of the present disclosure. As shown in FIG. 3A, after the addition of schedule participants is completed on the schedule creation page, when the schedule client detects that the number of schedule participants is 40 or more, a floating box can be displayed at the "Meeting Settings" location to display a permission setting prompt message such as "Since there are many meeting participants, it is recommended to change the meeting settings to ensure the safety and order of the meeting", and remind the schedule client user to perform permission setting.

[0042] Figure 3B is a schematic diagram of the interface of the schedule control terminal according to an exemplary embodiment of the present disclosure. As shown in Figure 3B, when the schedule control terminal detects that the number of schedule participants is 40 or more, the schedule control terminal interface can display a pop-up that can display an authority setting prompt message such as "Since the number of meeting participants is large, it is recommended to change the meeting settings to ensure the safety and order of the meeting", and remind the schedule control terminal user to perform the authority setting.

[0043] When the preset trigger event includes the presence of a participant with a predetermined identity among the schedule participants, the schedule participant may be a friend user of the schedule client, a user searched in the mailbox, or a user member in another schedule, which is specifically determined according to the actual application scenario and is not limited here. The predetermined identity may be a user of a preset rank or a custom preset user. When there is a participant with a predetermined identity among the schedule participants, since the content of the schedule is generally highly private, when it is detected that there is a participant with a predetermined identity among the schedule participants, the displayed authority setting prompt message can timely remind the user to set the current schedule authority in order to further improve the security level of the schedule, guarantee the privacy of the schedule content, and reduce the risk of leakage of the schedule content.

[0044] For example, when adding schedule participants to the schedule creation page shown in Figure 3A, since schedule participants tend to have identity labels, when it is detected that there is a participant with the identity label of "officer" among the schedule participants, a floating box that can display an authority setting prompt message such as "Since the positions of the meeting participants are high, it is recommended to change the meeting settings to ensure the safety and order of the meeting" can be displayed in the "meeting settings" section, and the user is reminded to perform the authority setting.

[0045] For preset trigger events, when the schedule property is a preset schedule property, the schedule property may be determined based on the schedule theme name, may be selected from a drop-down box during schedule creation, or a new one may be added. The preset schedule property may be one of a class scene, a live meeting scene, a webinar, and other custom scenes where the security level needs to be raised. When the schedule property is a preset schedule property, the number of schedule participants included in the schedule is relatively large, the order of the schedule is easily disrupted, and the harm caused when the order of the schedule is disrupted is significant. For example, an uninvited user invades the class, takes away the teacher's speaking and sharing permissions, talks, chats, shares files, or tampers with markup at will, disrupting the order management of the class and threatening the safety of the class. Therefore, when it is detected that the schedule property is a preset schedule property, the displayed permission setting prompt message can timely remind the user to set the current schedule permissions, further manage the schedule permissions, ensure the order of the schedule, and reduce the risk of the schedule.

[0046] For example, when adding a schedule theme name to a schedule creation page as shown in Figure 3A, if the schedule theme name is detected and its directivity is clear, for example, if it is "XXXXX classroom", the schedule property of this schedule can be determined as "class". If the directivity of the schedule theme name is unclear, for example, if it is "Confirm the content of XXXX online in 10 minutes", the schedule property cannot be determined. In this case, the schedule property may be selected from the schedule property dropdown box on the schedule creation page, or the schedule property may be customized and added in the schedule property dropdown box. After determining the schedule property, if it is detected that the schedule property is a preset class property, a floating box that can display an authority setting prompt message such as "Since the meeting property is a preset property, it is recommended to change the meeting settings to ensure the safety and order of the meeting" can be displayed at the "Meeting Settings" location, to alert the user to perform the authority setting.

[0047] If the preset trigger event includes a mismatch between the permission state and the permission setting recommendation policy, the permission setting recommendation policy is satisfied when the permission state of the schedule permission meets the permission recommendation state, and the permission recommendation state is used to manage the schedule permission. If the permission state of the schedule participant matches the corresponding permission recommendation state, the risk during the schedule is low, the normal operation of the schedule order can be guaranteed, there is no need to reset the permission state of the schedule permission, and the permission state of the schedule permission can be continuously maintained. For example, for the permission of "automatically muting when participating in a meeting" of a schedule participant, the permission recommendation state of the permission of "automatically muting when participating in a meeting" is the on state. If the current permission state of the permission of "automatically muting when participating in a meeting" is the on state, the current permission state of the permission of "automatically muting when participating in a meeting" matches the permission recommendation state. In that case, there is no need to reset the permission of "automatically muting when participating in a meeting", and the on state of this permission of "automatically muting when participating in a meeting" is continuously maintained. If the permission state of the schedule participant does not match the corresponding permission recommendation state, the permission state of the schedule permission is reset so that it matches the corresponding permission recommendation state. For example, if the current permission state of the permission of "automatically muting when participating in a meeting" is the off state, the current permission state of the permission of "automatically muting when participating in a meeting" does not match the permission recommendation state. In that case, it is necessary to reset the permission of "automatically muting when participating in a meeting" and set the permission state of the permission of "automatically muting when participating in a meeting" to the on state. Therefore, when it is detected that the permission state and the permission setting recommendation policy do not match, a permission setting prompt message is displayed, and the user is immediately notified to set the permission state of the corresponding schedule permission based on the permission setting recommendation policy, thereby making the permission state of the schedule permission match the permission setting recommendation policy, improving the schedule order management efficiency, and reducing the schedule risk.

[0048] When the preset trigger event includes the case where the display count of the permission setting prompt message is less than a predetermined number of times, the predetermined number of times may be once or multiple times. When the predetermined number of times is once, if at least one of the above preset trigger events (the number of schedule participants is equal to or more than a predetermined number, there are participants with a predetermined identity among the schedule participants, the schedule nature is the preset schedule nature, the permission state does not match the permission setting recommendation policy) is detected, the user can be timely reminded of setting the schedule permission, the efficiency of schedule order management can be improved, and the schedule risk can be reduced. When the predetermined number of times is multiple times, if at least one of the above preset trigger events is detected, the user can be reminded to set the schedule permission at regular time intervals, and after the user receives the permission setting prompt message, an event that threatens the safety of the schedule due to forgetting the management of the schedule permission can be avoided.

[0049] In actual applications, the display count of the permission setting prompt message can be recorded. If at least one of the above preset trigger events (the number of schedule participants is equal to or more than a predetermined number, there are participants with a predetermined identity among the schedule participants, the schedule nature is the preset schedule nature, the permission state does not match the permission setting recommendation policy) is detected, first, it is determined whether the display count of the permission setting prompt message is less than the predetermined number of times. If it is less than the predetermined number of times, it indicates that during the progress of the schedule, the permission setting prompt message has not been displayed to the user, or the user has not performed a setting operation on the permission setting prompt message, and the permission setting prompt message can be displayed. Otherwise, it means that the user has already set the schedule permission, and afterwards, the permission setting prompt message will no longer be displayed. Alternatively, it means that the user already knows the permission setting prompt message and it is no longer necessary to display it.

[0050] When it is determined that the display count of the permission setting prompt message is less than a predetermined count, it is possible to determine whether to detect at least one of the other four preset trigger events. When at least one of the preset trigger events is detected, the permission setting prompt message can be displayed. When one of the other four preset trigger events is detected, it is possible to further determine whether any other preset trigger event has occurred, thereby more comprehensively determining whether to display the permission setting prompt message to the user, and avoiding repeatedly displaying the permission setting prompt message during the progress of the schedule to interrupt the schedule, thereby improving the user's schedule experience.

[0051] Note that in the exemplary embodiments of the present disclosure, in FIGS. 3A and 3B, as a preset trigger event, an example of a permission setting prompt message is given only when the number of schedule participants is equal to or more than a predetermined number. It should be understood that in some application scenarios, the preset trigger event may be at least one of the other preset trigger events described above. In these application scenarios, the display format of the permission setting prompt message may be the same or different, and the specific prompt content can correspond to the preset trigger event, and examples are not given one by one here.

[0052] Obviously, by monitoring a plurality of preset trigger events, the exemplary embodiments of the present disclosure avoid disturbing the rhythm of the schedule by always displaying the permission setting prompt message during the progress of the schedule, which may deteriorate the user's schedule experience. Further, when it is detected that the number of schedule participants is equal to or more than a preset number, the user is timely reminded to set the current schedule permission, reducing the schedule risk and avoiding the chaos of the schedule order due to untimely setting of the schedule permission. Also, when it is detected that there are participants with a predetermined identity among the schedule participants, the user is timely reminded to raise the security level of the schedule, thereby guaranteeing the privacy of the schedule content, reducing the risk of leakage of the schedule content. Moreover, when it is detected that the schedule nature is a preset schedule nature, the user is timely reminded to manage the schedule permission, thereby guaranteeing the schedule order and reducing the schedule risk. When a discrepancy between the permission status and the permission setting recommendation policy is detected, the user can be timely reminded to make the permission status of the schedule permission consistent with the permission setting recommendation policy by setting the permission, preventing the occurrence of events threatening the schedule security and improving the efficiency of schedule order management.

[0053] In one possible embodiment, the permission setting prompt message of the exemplary embodiments of the present disclosure may be generated by the client or transmitted by the server.

[0054] When the permission setting prompt message is the permission setting information generated by the client, the client can detect the preset trigger event, generate the permission setting prompt message, and is used to prompt the user to perform timely permission setting.

[0055] When the permission setting prompt message is the permission setting information sent by the server, if the client detects a preset trigger event, the client receives the permission setting prompt message from the server. For example, the client can send a message request command to the server, and the message request command requests the server to send a permission setting prompt message. Based on the message request, the server can send a permission setting prompt message to the client. Also, for example, the server can monitor the preset trigger event in real time, and in the case of a preset trigger event, the server can send a permission setting prompt message to the client.

[0056] Exemplarily, the permission setting prompt message of the exemplary embodiment of the present disclosure can further include a schedule safety risk message used to suggest potential safety risks during the progress of the schedule. The user can refer to the permission setting prompt message to set the schedule permission, and the set schedule permission can eliminate potential safety risks during the schedule progress, improve the safety of the schedule, avoid unnecessary interference, thereby improving the schedule order management efficiency.

[0057] In actual applications, when a permission setting prompt message is displayed on the client interface, the user can open the permission setting interface to set the schedule permission. Here, the client may be a multimedia conference terminal or a control terminal for controlling a multimedia conference. Correspondingly, the client interface may be a multimedia conference interface or a control terminal interface for controlling a multimedia conference. The permission setting interface may be derived from the client interface when creating the schedule or from the client interface during the progress of the schedule.

[0058] Regardless of whether the permission setting interface is a multimedia conference interface or a control terminal interface for controlling a multimedia conference, the permission setting entry of the permission setting interface may be provided in a security setting component, a friend list component, other components of the display interface, or also in a permission setting prompt message. When the permission setting entry of the permission setting interface is provided in the permission setting prompt message, the permission setting prompt message may also include the permission setting entry, and the permission setting entry can be used to provide an entry to the permission setting interface. The client can display the permission setting interface in response to a click operation on the permission setting entry.

[0059] Exemplarily, the method of the exemplary embodiment of the present disclosure further includes deleting a permission setting prompt message in response to a deletion operation on the permission setting prompt message. The deletion operation may be at least one of an opening operation on the permission setting interface, a cancellation operation on a schedule, a confirmation operation on the permission setting prompt message, and a new schedule creation operation.

[0060] When the user performs an opening operation on the permission setting interface, the user has already received a permission setting prompt message, indicating the start of schedule permission setting. In this case, the permission setting prompt message can be deleted. When the user performs a confirmation operation on the permission setting prompt message, it indicates that the user has already confirmed the permission setting prompt message. In this case, the permission setting prompt message is deleted. When the user performs a cancellation operation on a schedule, it indicates that the schedule has been cancelled, and there is no need to continue setting the schedule permission for that schedule. In this case, the permission setting prompt message is deleted. When the user performs a new schedule creation operation, it indicates that the schedule has already been set. In this case, the permission setting prompt message is deleted. For the deletion operation of the permission setting prompt message performed by the user, the client can respond to the deletion operation on the permission setting prompt message and delete the permission setting prompt message, avoiding the situation where the permission setting prompt message is always displayed on the display interface, occupying the display interface space and degrading the user experience.

[0061] In the following, for the sake of clarity in the realization process of the method of the exemplary embodiments of the present disclosure, with reference to the drawings, the realization process of the method of the exemplary embodiments of the present disclosure will be described. It should be understood that the following realization process is for illustrative purposes only and is not limiting.

[0062] In the schedule creation stage, when the permission setting prompt message is generated by the client, as shown in Figure 3A, in the entry for setting the permission setting interface of the permission setting prompt message, the user can trigger "Go to Settings" (for example, trigger "Go to Settings" by touching the mobile terminal) to enter the permission setting interface, or can also enter the permission setting interface by clicking "Meeting Settings". If there is no need to set permissions, "Understood" can be triggered.

[0063] As shown in FIG. 3B, the user can enter the permission setting interface by triggering "Settings", can also enter the permission setting interface by clicking "Security", and can also enter the permission setting interface by clicking "Settings". If permission setting is not required, the user can trigger "Understood" or close the component.

[0064] FIG. 3C is a schematic diagram of a schedule creation page for deleting a permission setting prompt message according to an exemplary embodiment of the present disclosure. As shown in FIG. 3C, when the user triggers "Settings", "Meeting Settings", or "Understood", the permission setting prompt message on the schedule creation page is deleted.

[0065] After schedule creation is completed and before the schedule starts, if a permission setting prompt message is sent by the server, FIG. 4A shows a schematic diagram of a schedule creation notification according to an exemplary embodiment of the present disclosure, and FIG. 4B shows a schematic diagram of a permission opening notification according to an exemplary embodiment of the present disclosure. As shown in FIG. 4A, after schedule creation is completed, the client sends schedule editing information to the server, and the server can detect whether a preset trigger event has occurred based on the schedule editing information. When the server detects a preset trigger event, the server sends a permission setting prompt message to the client, and the meeting assistant of the client can receive the permission setting prompt message. For example, a notification of successful creation of a meeting can be sent to the client in the form of a notification, and the user can be notified that permission setting is required. An entry to the permission setting interface can also be set in the notification of successful creation of the meeting, and the user can enter by triggering "Settings" or click on the gear-shaped component (indicating "Meeting Settings") in the upper right corner to enter and set permissions. As shown in FIG. 4B, after the user sets the permissions, the meeting assistant of the client can receive the notification of "Permission opened" synchronously sent by the server.

[0066] During the progress of the schedule, regardless of whether it is an authority setting prompt message generated by the client or an authority setting prompt message sent by the server, the display method on the schedule interface of the client may be the same. FIG. 5 is a schematic diagram of a method for displaying an authority setting prompt message in a display interface according to an exemplary embodiment of the present disclosure. As shown in FIG. 5, when a preset trigger event is detected, an authority setting prompt message, for example, "Since there are currently a large number of meeting participants, it is recommended to limit the speaking and sharing authorities to ensure the order of the meeting", can be displayed above the display interface. The authority setting prompt message can also include a portal (such as "To restrictions") of the authority setting interface. The user can enter the authority setting interface by triggering "To restrictions", and can also enter the authority setting interface by triggering "Safe" located below the display interface. In addition, by clicking on the upper triangular component to the right of each type of component (microphone, camera, chat, sharing, recording, expression) located below the display interface, the user can enter the corresponding schedule authority setting interface. Also, by clicking on the schedule participant list located below the display interface, the user can enter the authority setting interface.

[0067] Exemplarily, the user can enter the first type of permission setting interface shown in FIG. 6A through the permission setting interface entry or the "Security" component included in the permission setting prompt message displayed by the client schedule interface. Taking the example that the user clicks on the up triangle component to the right of each type of schedule permission component below the schedule interface, thereby clicking on the up triangle component to the right of the "Schedule" component below the schedule interface, the second type of permission setting interface shown in FIG. 6B is expanded. Naturally, the user enters the third type of permission setting interface shown in FIG. 6C by touching the permission setting interface entry, the "Security" component or the schedule participant list setting included in the permission setting prompt message displayed on the mobile schedule interface.

[0068] As can be seen from FIGS. 6A to 6C, the method of the exemplary embodiment of the present disclosure can further include displaying schedule permission setting items in response to an opening operation on the schedule permission setting interface. The schedule permission setting items may be of one type or multiple types, and are determined according to the actual application scenario. Each type of schedule permission setting item can include schedule permission and schedule permission status. The permission status of each type of schedule permission is displayed for that schedule permission, and the permission status can be represented by a permission status label, which is used to indicate whether the permission status of that schedule permission is on or off.

[0069] When the authority state of the schedule authority does not match the authority recommendation state, the corresponding authority setting recommendation information is displayed. The authority setting recommendation information is used to instruct the user to adjust the authority state of the schedule authority to the authority recommendation state. The display position of the authority setting recommendation information may be the display position of the corresponding schedule authority or other positions of the authority setting interface, and specifically is determined according to the actual scenario and is not limited here. When the authority state of the schedule authority matches the authority recommendation state, there is no need to display the corresponding authority setting recommendation information, and the authority state of the schedule authority can ensure the schedule order and schedule security.

[0070] The authority setting recommendation information can include multiple types of authority state recommendation indicators, and each of the authority state recommendation indicators is used to indicate the authority recommendation state of the corresponding schedule authority. For example, the authority state recommendation indicator may be an on-recommendation indicator and an off-recommendation indicator. When the on-recommendation indicator is displayed for the schedule authority, the authority recommendation state of the schedule authority is the authority-on state. When the off-recommendation indicator is displayed for the schedule authority, the authority recommendation state of the schedule authority is the authority-off state.

[0071] Based on this, the method of the exemplary embodiment of the present disclosure can further include displaying a security hint in response to an operation on the authority state recommendation indicator. The operation on the authority state recommendation indicator can include one of a click operation on the authority state recommendation indicator and a mouse hovering operation on the authority state recommendation indicator. When an operation on the authority state recommendation indicator occurs, a security hint is displayed on the display interface to alert the user to the security risks existing during the progress of the schedule in the current authority state. Next, taking FIG. 6A as an example, the operation process of authority setting will be described.

[0072] As shown in FIG. 6A, when entering the permission setting interface through "Restriction" shown in FIG. 5 or "Security" below the display interface, the permission setting interface displays schedule permission setting items including a total of 10 types of schedule permissions 610 and the corresponding schedule permission states. The 10 types of schedule permissions 610 can be classified by type into meeting security, speaking permissions, sharing permissions, and participant permissions. The permission state of each schedule permission 610 can be indicated by whether the corresponding checkbox of the schedule permission is checked. For example, when the checkbox 621 of "Turn on the waiting room" is checked, it indicates that the permission state of the schedule permission is on. When the checkbox 622 of "Only the moderator can share" is not checked, it indicates that the permission state of the schedule permission is off.

[0073] A permission state recommendation label 630 is displayed for "Only the moderator can share". For example, a label of "Recommend to turn on" can be displayed at the end of "Only the moderator can share". This label is used to instruct the user to adjust the permission state of "Only the moderator can share" to the on state. When the user clicks on the permission state recommendation label 630 or places the mouse over the permission state recommendation label 630, a security hint 640, such as "Since the number of people in the meeting is large, it is recommended to turn it on", is displayed on the permission state recommendation label 630. When the recommended permission state of "Only the moderator can share" is on and the checkbox 622 of "Only the moderator can share" is not checked, the user can consider that the permission state and the recommended permission state of "Only the moderator can share" do not match. Therefore, the user can modify the permission state of "Only the moderator can share" to the on state by checking the checkbox 622 of "Only the moderator can share", thereby ensuring that the permission state of the modified schedule permission 610 meets the permission recommendation and guaranteeing the schedule order and schedule security.

[0074] Note that the processes and principles of the schedule permission setting operation of the schedule client and the schedule permission setting operation of the schedule control terminal are the same, and the way to open the permission setting page is the same. However, the layout of the permission setting page is slightly different, which is not the key content of this disclosure. When the schedule permission setting operation is performed on the schedule control terminal, the user can enter the third type of permission setting interface shown in FIG. 6C from the "Settings" component of the schedule control terminal interface. The details of this step can be referred to the foregoing content and will not be elaborated here.

[0075] Obviously, one or more technical solutions provided in the exemplary embodiments of the present disclosure can display a permission setting prompt message when detecting a preset trigger event, and the displayed permission setting prompt message can timely remind the user to set the current schedule permission. Based on this, in response to the setting operation of the current schedule permission, the current schedule permission is set. Obviously, the method of the exemplary embodiments of the present disclosure can immediately remind the user to set the schedule permission when detecting a preset trigger event, thereby improving the schedule management efficiency and avoiding the chaos of the schedule order caused by the untimely setting of the schedule permission.

[0076] When the schedule permission setting operation is performed on the server, the schedule permission setting method provided by the exemplary embodiments of the present disclosure can be executed through the interaction between the client and the server. The following embodiments will interactively explain the method of the exemplary embodiments of the present disclosure with the client and the server as the execution entities respectively with reference to the drawings.

[0077] FIG. 7 is another exemplary flowchart of the schedule permission setting method according to the exemplary embodiments of the present disclosure. As shown in FIG. 7, the schedule permission setting method according to the exemplary embodiments of the present disclosure may include the following: Step 701: The client sends schedule progress information to the server. The schedule progress information may include schedule editing information or schedule dynamic information.

[0078] When the schedule progress information includes schedule editing information, after creating the schedule and before starting the schedule, the client can send the schedule progress information to the server. The schedule editing information can at least include the number of schedule participants in the participating schedule, the identities of the schedule participants, the nature of the schedule, and the authorization status of the schedule permissions. Of course, it can also include other information such as the start time and end time of the schedule, and the schedule host.

[0079] When the schedule progress information includes schedule dynamic information, the client can upload the schedule dynamic information to the server in real time during the schedule progress. At this time, the schedule dynamic information can at least include the number of currently online schedule participants, the identities of the schedule participants, the nature of the schedule, the authorization status of the schedule permissions, and the number of authorization settings.

[0080] Step 702: The server receives the schedule progress information from the client.

[0081] Step 703: The server determines that a preset trigger event occurs for the client based on the schedule progress information, and sets the schedule permission based on the permission setting recommendation policy. For the method by which the server determines the occurrence of a preset trigger event in the client, reference can be made to the foregoing description. The preset trigger event includes at least one of the following: the number of schedule participants is equal to or greater than a predetermined number; there are participants with a predetermined identity among the schedule participants; the schedule nature is a preset schedule nature; the permission status and the permission setting recommendation policy do not match; the display times of the permission setting prompt message are less than a predetermined number. The permission setting recommendation policy satisfies that the permission status of the schedule permission meets the permission recommendation status, and the permission recommendation status is used to manage the schedule permission.

[0082] If the schedule progress information includes schedule editing information, the server can determine that a preset trigger event has occurred based on the schedule editing information, automatically set the schedule permission based on the permission setting recommendation policy, and after the setting of the schedule permission is completed, send a "permission opened" notification to the meeting assistant of the client in a notification manner. Specifically, reference can be made to FIG. 4B.

[0083] When the schedule progress information includes the schedule dynamic information, the server determines whether a preset trigger event has occurred on the client based on the real-time schedule dynamic information sent by the client. When it is determined that a preset trigger event has occurred on the client, the server automatically sets the schedule permission based on the permission setting recommendation policy. After the setting of the schedule permission is completed, the server can send a "permission setting" notification to the client's meeting assistant in a notification manner (specifically, see FIGS. 4A and 4B). In addition, a prompt message indicating the completion of the permission setting can be popped up and displayed on the schedule interface, thereby informing the user that the permission setting of the schedule permission is completed and enabling the user to timely understand the setting status of the schedule permission.

[0084] In this way, the exemplary embodiments of the present disclosure can monitor the schedule progress information of the client by the server. When it is detected that a preset trigger event has occurred on the client, the server sets the schedule permission based on the permission setting recommendation policy and sends the set schedule permission information to the client. Thereby, the client can manage the schedule based on the set schedule permission information, realizing the automatic setting of the schedule permission by the server, reducing the schedule setting operation steps on the client, avoiding interrupting the user schedule flow by displaying the permission setting prompt message during the schedule progress, improving the management efficiency of the schedule order, ensuring the safety of the schedule, and thus improving the user's schedule experience.

[0085] To implement the above functions, the client or server in the exemplary embodiments of the present disclosure includes a hardware structure and / or software module corresponding to the execution of each function. Those skilled in the art will readily recognize that the present disclosure can be implemented in the form of hardware or a combination of hardware and computer software in relation to each example of the units and algorithm steps described in the embodiments disclosed herein. Whether a certain function is executed in hardware or in a manner that drives hardware with computer software depends on the specific application of the technical solution and design constraints. Those skilled in the art can use different methods for each specific application to implement the described functions, but such implementations should not be considered as exceeding the scope of the present disclosure.

[0086] In accordance with the above method examples, the embodiments of the present disclosure can perform a division of functional units for the client or server. For example, each functional module can be divided corresponding to each function, or two or more functions can be integrated into one processing module. The above integrated module can be implemented in the form of hardware or in the form of a software functional module. It should be noted that the division of modules in the embodiments of the present disclosure is schematic and is only a logical functional division. In actual implementation, there may be other division methods.

[0087] When dividing each functional module corresponding to each function, the exemplary embodiments of the present disclosure provide a scheduling permission setting device. FIG. 8 is a schematic block diagram of the modules of the scheduling permission setting device according to the exemplary embodiments of the present disclosure. As shown in FIG. 8, the scheduling permission setting device 800 includes a display module 801 for displaying a permission setting prompt message when detecting a preset trigger event, and a setting module 802 for setting scheduling permissions in response to an operation for executing the setting of scheduling permissions.

[0088] As one possible embodiment, the schedule permission setting device 800 further includes a communication module 803 for sending a message request command to the server, where the message request command is used to request the server to send a permission setting prompt message, and receiving the permission setting prompt message from the server when detecting a preset trigger event.

[0089] As a possible embodiment, the preset trigger event includes at least one of the following: the number of schedule participants is greater than or equal to a predetermined number; there are participants with a predetermined identity among the schedule participants; the schedule nature is a preset schedule nature; the permission state and the permission setting recommendation policy do not match; the display times of the permission setting prompt message are less than a predetermined number of times.

[0090] As a possible embodiment, the preset trigger event supports setting and updating.

[0091] As a possible embodiment, the display module 801 is further used to present schedule permission setting items in response to an opening operation on the schedule permission setting interface.

[0092] As a possible embodiment, the permission setting interface is derived from the client interface at the schedule creation time, and the permission setting interface is derived from the client interface during the schedule progress period.

[0093] As a possible embodiment, the client interface during the schedule progress period includes a multimedia conference interface or a control terminal interface for controlling the multimedia conference.

[0094] As a possible embodiment, the permission setting prompt message further includes a permission setting entry.

[0095] As a possible embodiment, when the display module 801 detects a preset trigger event, it displays an authorization setting prompt message on the client interface of the first user who has the schedule setting authority, so that the first user and / or the second user designated by the first user can be used to set the schedule authority.

[0096] As a possible embodiment, the display module 801 further displays corresponding authorization setting recommendation information when the authorization status of the schedule authority does not match the authorization recommendation status, and the authorization setting recommendation information is used to instruct the user to adjust the authorization status of the schedule authority to the authorization recommendation status.

[0097] As a possible embodiment, the authorization setting recommendation information includes multiple types of authorization status recommendation identifiers, and each of the authorization status recommendation identifiers is used to indicate the authorization recommendation status of the corresponding schedule authority. The display module 801 is also used to display security hints in response to operations on the authorization status recommendation identifiers.

[0098] As one possible embodiment, the schedule authority setting device 800 further includes an erasure module 804 that erases the authorization setting prompt message in response to an erasure operation on the authorization setting prompt message, and the erasure operation is at least one of an opening operation on the authorization setting interface, a cancellation operation on the schedule, a confirmation operation on the authorization setting prompt message, and a new schedule creation operation.

[0099] The exemplary embodiments of the present disclosure further provide other schedule authority setting devices. FIG. 9 is a schematic block diagram of the modules of a schedule authority setting device according to an exemplary embodiment of the present disclosure. As shown in FIG. 9, the schedule authority setting device 900 includes a communication module 901 for receiving schedule progress information from a client, It includes a setting module 902 for determining that a preset trigger event occurs for the client based on schedule progress information and setting schedule permissions based on a permission setting recommendation policy.

[0100] As a possible implementation form, the schedule progress information includes schedule editing information or schedule dynamic information.

[0101] As a possible embodiment, the preset trigger event includes at least one of the following: the number of schedule participants is equal to or greater than a predetermined number; there are participants with a predetermined identity among the schedule participants; the schedule nature is a preset schedule nature; the permission status does not match the permission setting recommendation policy; the display times of the permission setting prompt message are less than a predetermined number of times.

[0102] FIG. 10 is a schematic block diagram of a chip according to an exemplary embodiment of the present disclosure. As shown in FIG. 10, the chip 1000 includes one or two or more (including two) processors 1001 and a communication interface 1002. The communication interface 1002 can support the server to execute the data transmission and reception steps in the above method, and the processor 1001 can support the server to execute the data processing steps in the above method.

[0103] Optionally, as shown in FIG. 10, the chip 1000 can include a read-only memory and a random access memory, and further includes a memory 1003 that provides operation instructions and data to the processor. A part of the memory can also include a non-volatile random access memory (NVRAM).

[0104] In some embodiments, as shown in FIG. 10, the processor 1001 executes corresponding operations by calling operation instructions (which can be stored in the operating system) stored in the memory. The processor 1001 controls any processing operation of the terminal device, and the processor can also be called a central processing unit (CPU). The memory 1003 can include a read-only memory and a random access memory, and provides instructions and data to the processor 1001. A part of the memory 1003 can also include NVRAM. For example, in an application, the memory, the communication interface, and the memory are coupled to each other via a bus system, where the bus system can include a power bus, a control bus, a status signal bus, etc. in addition to the data bus. However, for clarity of explanation, the various buses are shown as a bus system 1004 in FIG. 10.

[0105] The methods disclosed in the embodiments of the present disclosure described above may be applied to a processor or may be implemented by a processor. The processor may be an integrated circuit chip having signal processing capabilities. In the implementation process, each step of the above-described method can be achieved by the integrated logic circuit of the hardware in the processor or by instructions in the form of software. The above-described processor may be a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components. Each method, step, and logical block diagram disclosed in the embodiments of the present disclosure can be implemented or executed. The general-purpose processor may be a microprocessor, or the processor may be any ordinary processor or the like. The steps of the method disclosed in connection with the embodiments of the present disclosure can be embodied as being directly executed and completed by a hardware decoding processor, or can be embodied as being executed and completed by combining the hardware and software modules in the decoding processor. The software module may be in a storage medium mature in the art such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, register, etc. The storage medium is in the memory, and the processor reads the information in the memory and combines it with its hardware to complete the steps of the above-described method.

[0106] Exemplary embodiments of the present disclosure further provide an electronic device, including at least one processor and a memory communicatively connected to the at least one processor, where the memory stores a computer program executable by the at least one processor, and when the computer program is executed by the at least one processor, it is used to cause the electronic device to execute the method according to the embodiments of the present disclosure.

[0107] Also, exemplary embodiments of the present disclosure provide a non-transitory computer-readable storage medium storing a computer program, where when the computer program is executed by a processor of a computer, it is used to cause the computer to execute the method according to the embodiments of the present disclosure.

[0108] Also, exemplary embodiments of the present disclosure provide a computer program product including a computer program, where when the computer program is executed by a processor of a computer, it is used to cause the computer to execute the method according to the embodiments of the present disclosure.

[0109] Next, with reference to FIG. 11, a block diagram of an electronic device 1100 that functions as a server or a client of the present disclosure will be described. It is an example of a hardware device applicable to each aspect of the present disclosure. The electronic device may represent various forms of digital electronic computer devices, such as laptop computers, desktop computers, tablets, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device may further represent various forms of mobile devices, such as personal digital processors, mobile phones, smartphones, wearable devices, and other similar computing devices. The components shown in this specification, their connection relationships, and their functions are merely exemplary and do not limit the implementation of the present disclosure described and / or claimed in this specification.

[0110] As shown in FIG. 11, the electronic device 1100 can include a computing unit 1101 and can execute various appropriate operations and processes based on a computer program stored in a read-only memory (ROM) 1102 or a computer program loaded from a storage unit 1108 into a random access memory (RAM) 1103. In the RAM 1103, various programs and data necessary for further operating the device 1100 may be stored. The computing unit 1101, the ROM 1102, and the RAM 1103 are connected to each other via a bus 1104. An input / output (I / O) interface 1105 is also connected to the bus 1104.

[0111] A plurality of components such as an input unit 1106, an output unit 1107, a storage unit 1108, and a communication unit 1109 in the electronic device 1100 are connected to the input / output (I / O) interface 1105. The input unit 1106 may be any type of device capable of inputting information into the electronic device 1100, and the input unit 1106 can generate input digital or character information and key signal inputs related to user settings and / or function controls of the electronic device. The output unit 1107 may be any type of device capable of presenting information, and may include, but is not limited to, a display, a speaker, a video / audio output terminal, a vibrator, and / or a printer. The storage unit 1108 may include, but is not limited to, a magnetic disk and an optical disk. The communication unit 1109 enables the electronic device 1100 to exchange information / data with other devices via, for example, a computer network such as the Internet and / or various telecommunication networks, and may include, but is not limited to, a modem, a network card, an infrared communication device, a wireless communication transceiver, and / or a chipset, for example, a Bluetooth (registered trademark) TM device, a WiFi device, a WiMax device, a cellular communication device, and / or the like.

[0112] As shown in FIG. 11, the computing unit 1101 may be various general-purpose and / or dedicated processing components having processing and computing capabilities. Some examples of the computing unit 1101 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various dedicated artificial intelligence (AI) computing chips, various computing units that execute machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. The computing unit 1101 executes each of the methods and processes described above. For example, in some embodiments, the method of the exemplary embodiments of the present disclosure may be implemented as a computer software program tangibly embodied in a machine-readable medium, such as the storage unit 1108. In some embodiments, part or all of the computer program may be loaded and / or installed into the electronic device 1100 via the ROM 1102 and / or the communication unit 1109. In some embodiments, the computing unit 1101 can be configured to execute the method in any other suitable manner (e.g., by firmware).

[0113] The program code for implementing the method of the present disclosure can be written using any combination of one or more programming languages. These program codes may be provided to the processor or controller of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus, so that when the program code is executed by the processor or controller, it implements the functions / operations defined in the flowchart and / or block diagram. The program code may be executed entirely by a machine, partially by a machine, partially by a device as an independent software package and partially by a remote device, or entirely by a remote device or server.

[0114] In the context of the present disclosure, a machine-readable medium may be a tangible medium that can embody or store a program for use in or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. The machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of the machine-readable storage medium include electrical connections by one or more leads, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0115] As used in the present disclosure, the terms "machine-readable medium" and "computer-readable medium" refer to any computer program product, apparatus, and / or device (e.g., magnetic disk, optical disk, memory, programmable logic device (PLD)) that provides machine instructions and / or data to a programmable processor, including a machine-readable medium that receives machine instructions as a machine-readable signal. The term "machine-readable signal" refers to any signal used to provide machine instructions and / or data to a programmable processor.

[0116] To provide interaction with a user, the systems and techniques described herein can be implemented on a computer having a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user, and a keyboard and a pointing device (e.g., a mouse or trackball), and the user may input to the computer via this keyboard and this pointing device. Other types of devices can be used to provide interaction with a user where the feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback), and input from the user can be received in any form (including acoustic input, voice input, or tactile input).

[0117] The systems and techniques described here may be implemented in a computing system including a back-end member (e.g., as a data server), a computing system including a middleware member (e.g., an application server), a computing system including a front-end member (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with embodiments of those systems and techniques), or a computing system consisting of any combination of those back-end members, middleware members, or front-end members. The members of the system may be interconnected by digital data communication of any form or medium (e.g., a communication network). Examples of communication networks include, for example, a local area network (LAN), a wide area network (WAN), and the Internet.

[0118] The computer system may include a client and a server. The client and the server are generally far apart from each other and usually interact via a communication network. The relationship between the client and the server is generated by operating on a computer corresponding to a computer program having a client-server relationship with each other.

[0119] In the above-described embodiments, all or part thereof may be implemented by software, hardware, firmware, or any combination thereof. When implemented by software, it can be implemented as a computer program product as a whole or in part. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of the present disclosure are executed in whole or in part. The computer may be a general-purpose computer, a dedicated computer, a computer network, a terminal, a user device, or other programmable devices. The computer program or instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer program or instructions can be transmitted wired or wirelessly from a certain website, computer, server, or data center to another website, computer, server, or data center. The computer-readable storage medium may be any available medium accessible by a computer, or a data storage device such as a server or a data center that integrates one or more available media. The available medium may be a magnetic medium, such as a floppy disk, a hard disk, or a magnetic tape, or an optical medium, such as a digital video disc (DVD), or a semiconductor medium, such as a solid state drive (SSD).

[0120] Although the present disclosure has been described in terms of specific features and examples thereof, various modifications and combinations can be made without departing from the spirit and scope of the present disclosure. Accordingly, the specification and drawings are merely exemplary descriptions of the present disclosure as defined by the appended claims, and are considered to cover any and all modifications, alterations, combinations, or equivalents within the scope of the present disclosure. It will be apparent to those skilled in the art that various changes and variations can be made to the present disclosure without departing from the spirit and scope thereof. Thus, if these modifications and variations of the present disclosure fall within the scope of the claims of the present disclosure and their equivalent technologies, the present disclosure is also intended to include these changes and variations.

Claims

1. A method for setting schedule permissions, the method comprising: displaying a permission setting prompt message when detecting a preset trigger event; and setting the schedule permission in response to a setting operation for the schedule permission.

2. The method further comprises: sending a message request command to a server, the message request command being used to request the server to send a permission setting prompt message; and receiving a permission setting prompt message from the server when detecting a preset trigger event.

3. The preset trigger event includes at least one of the following: the number of schedule participants is greater than or equal to a predetermined number, there is a participant with a predetermined identity among the schedule participants, the schedule nature is a preset schedule nature, the permission status and the permission setting recommendation policy do not match, and the display times of the permission setting prompt message are less than a predetermined number of times.

4. The preset trigger event supports setting and updating.

5. The method further comprises: presenting schedule permission setting items in response to an opening operation on the permission setting interface of the schedule.

6. The permission setting interface is derived from a client interface at the schedule creation time, or the permission setting interface is derived from a client interface during the schedule progress.

7. The client interface during the schedule progress includes a multimedia conference interface or a control terminal interface for controlling a multimedia conference.

8. The permission setting prompt message further includes a permission setting entry.

9. When detecting the preset trigger event, displaying the permission setting prompt message means: When a preset trigger event is detected, by presenting an authorization setting prompt message to the client interface of the first user having the schedule setting authority, the method according to claim 1, including that the first user and / or a second user designated by the first user set the schedule authority.

10. The method further includes presenting corresponding authorization setting recommendation information when the authorization state of the schedule authority does not match the authorization recommendation state, and the authorization setting recommendation information is used to adjust the authorization state of the schedule authority to the authorization recommendation state. The method according to any one of claims 1 to 9.

11. The authorization setting recommendation information includes multiple types of authorization state recommendation identifiers, and each of the authorization state recommendation identifiers is used to indicate the authorization recommendation state of the corresponding schedule authority. The method further includes displaying a security hint in response to an operation on the authorization state recommendation identifier. The method according to claim 10.

12. The method further includes aborting the display of the authorization setting prompt message in response to a deletion operation on the authorization setting prompt message, and the deletion operation is at least one of an opening operation on the authorization setting interface, a cancellation operation on the schedule, a confirmation operation on the authorization setting prompt message, and a new schedule creation operation. The method according to claim 10.

13. A method for setting schedule authority, the method including receiving schedule progress information from a client, determining that a preset trigger event occurs in the client based on the schedule progress information, and setting schedule authority based on an authorization setting recommendation policy. A method for setting schedule authority.

14. The schedule progress information includes schedule editing information or schedule dynamic information. The method according to claim 13.

15. The method according to claim 13, wherein the preset trigger event includes at least one of the following: the number of schedule participants is equal to or greater than a predetermined number; there are participants with a predetermined status among the schedule participants; the schedule nature is a preset schedule nature; the authority status and the authority setting recommendation policy do not match; the number of times the authority setting prompt message is displayed is less than a predetermined number.

16. A schedule authority setting device, the device comprising: a display module for displaying an authority setting prompt message when detecting a preset trigger event; and a setting module for setting the schedule authority in response to a setting operation for the schedule authority.

17. A schedule authority setting device, the device comprising: a communication module for receiving schedule progress information from a client; and a setting module for determining that a preset trigger event occurs for the client based on the schedule progress information and setting the schedule authority based on an authority setting recommendation policy.

18. An electronic device, comprising a processor and a memory for storing a program, wherein the program includes instructions that, when executed by the processor, cause the processor to execute the method according to any one of claims 1 to 15.

19. A non-transitory computer-readable storage medium storing computer instructions, wherein the computer instructions are used to cause a computer to execute the method according to any one of claims 1 to 15.

Images