Data processing method and device, computer device, storage medium and product

Abstract

Embodiments of the present application provide a data processing method and device, computer equipment, storage medium and product, the method comprises: in the schedule application interface of target application, meeting creation component is displayed; in response to the first touch operation for the meeting creation component, the meeting configuration option is displayed in the schedule application interface; in response to the second touch operation for the meeting configuration option, the meeting configuration parameter obtained by the second touch operation is displayed in the schedule application interface; target meeting is generated based on the meeting configuration parameter. By the way described in the present application, the business development efficiency can be improved, and the business maintenance cost is reduced.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a data processing method, apparatus, computer equipment, storage medium, and product. Background Technology

[0002] With the development of technology, numerous collaborative and communication applications have emerged to assist enterprise office work, greatly improving the work efficiency of employees. However, these applications typically involve multiple business functions, each with its own business logic, and these functions are often isolated. For example, different business interfaces need to be developed for scheduling and meeting functions, requiring users to complete corresponding operations within their respective interfaces. This necessitates maintaining multiple sets of business logic, leading to low development efficiency and high maintenance costs. Summary of the Invention

[0003] This application provides a data processing method, apparatus, computer equipment, storage medium, and product that can improve business development efficiency and reduce business maintenance costs.

[0004] In a first aspect, embodiments of this application provide a data processing method, including:

[0005] Display the meeting creation component in the target application's calendar application interface;

[0006] In response to a first touch operation on the meeting creation component, meeting configuration options are displayed in the calendar application interface;

[0007] In response to a second touch operation on the meeting configuration options, the meeting configuration parameters obtained from the second touch operation are displayed in the calendar application interface;

[0008] The target meeting is generated based on the meeting configuration parameters.

[0009] Secondly, embodiments of this application provide a data processing apparatus, including:

[0010] The display module is used to show the meeting creation components in the target application's calendar application interface;

[0011] The processing module is configured to respond to a first touch operation on the meeting creation component and display meeting configuration options in the calendar application interface via the display module.

[0012] The processing module is further configured to respond to a second touch operation on the meeting configuration option and display the meeting configuration parameters obtained by the second touch operation in the calendar application interface through the display module;

[0013] The processing module is also used to generate a target meeting based on the meeting configuration parameters.

[0014] Thirdly, embodiments of this application provide a computer device, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps of the method described in the first aspect.

[0015] Fourthly, embodiments of this application provide a computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the steps of the method described in the first aspect.

[0016] Fifthly, embodiments of this application provide a computer program product, including a computer program that, when executed by a processor, implements the steps of the method described in the first aspect.

[0017] In summary, the computer device can display a meeting creation component in the calendar application interface of the target application. By operating the meeting creation component, meeting configuration options can be displayed in the calendar application interface. Then, meeting configuration parameters can be obtained based on the meeting configuration options, which are then used to generate the target meeting. This application adopts this process to realize the creation of meetings on the calendar application interface. The calendar application interface can realize functions such as calendar creation and meeting creation. There is no need to develop different business interfaces for calendar business and meeting business to perform calendar creation and meeting creation separately. This can improve business development efficiency and reduce business maintenance costs. Attached Figure Description

[0018] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0019] Figure 1 This is a schematic diagram of the structure of a data processing system provided in an embodiment of this application;

[0020] Figure 2 This is a flowchart illustrating a data processing method provided in an embodiment of this application;

[0021] Figure 3 This is a schematic diagram illustrating the operation process of a voice / video switch provided in an embodiment of this application;

[0022] Figure 4 This is a flowchart illustrating another data processing method provided in an embodiment of this application;

[0023] Figure 5AThis is a schematic diagram illustrating how to display schedule options based on a chat window, as provided in an embodiment of this application.

[0024] Figure 5B This is a schematic diagram of a calendar application interface provided in an embodiment of this application;

[0025] Figure 5C This is a schematic diagram of another scheduling application interface provided in an embodiment of this application;

[0026] Figure 5D This is a schematic diagram illustrating how to select a meeting time based on the schedule data of the participants, provided in an embodiment of this application.

[0027] Figure 5E This is a schematic diagram of an interface that displays detailed information about a meeting room awaiting approval, provided in an embodiment of this application.

[0028] Figure 5F This is a schematic diagram of an interface displaying schedule details provided in an embodiment of this application;

[0029] Figure 6 This is a schematic diagram of a data processing procedure provided in an embodiment of this application;

[0030] Figure 7 This is a schematic diagram of another data processing procedure provided in an embodiment of this application;

[0031] Figure 8 This is a schematic diagram of the structure of a data processing device provided in an embodiment of this application;

[0032] Figure 9 This is a schematic diagram of the structure of a computer device provided in an embodiment of this application. Detailed Implementation

[0033] The technical solutions in the embodiments of this application will now be described with reference to the accompanying drawings.

[0034] This application provides a data processing method applicable to computer devices, which can be terminals, including but not limited to smartphones, tablets, laptops, desktop computers, tablet computers, wearable devices such as wearable watches, vehicle terminals, and aircraft. The computer device has a target application installed. The target application can be a communication application (e.g., enterprise communication application), a collaboration application (e.g., enterprise collaboration application), or a work application (e.g., enterprise office application). The target application enables functions such as meeting reservation, schedule booking, and meeting room reservation.

[0035] Specifically, the data processing method involves displaying a meeting creation component in the calendar application interface of the target application; responding to a first touch operation on the meeting creation component, displaying meeting configuration options in the calendar application interface; responding to a second touch operation on the meeting configuration options, displaying meeting configuration parameters obtained from the second touch operation in the calendar application interface; and generating a target meeting based on the meeting configuration parameters. This application employs this process, enabling meeting creation on the calendar application interface. It achieves functions such as schedule creation and meeting creation based on the calendar application interface, eliminating the need to develop separate business interfaces for schedule and meeting services. Essentially, it allows the implementation of some business logic that would otherwise be implemented by the meeting service based on the business logic of the schedule service, improving the development efficiency of the target application's business. It also eliminates the need to maintain similar business logic for the schedule and meeting services separately, such as separate schedule creation and meeting creation logic, thus reducing business maintenance costs.

[0036] In one embodiment, the data processing method can be applied to Figure 1 The data processing system shown. Among them, Figure 1 The data processing system shown includes multiple terminals (including terminal 1, terminal 2, etc.) and server 10. Each terminal can establish communication with server 10. The data processing method described can be applied to any one of the multiple terminals. Server 10 can be a single server or a server cluster. The server can be a single physical server, a server cluster consisting of at least two physical servers, or a distributed system. It can also be a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, Content Delivery Network (CDN), and big data and artificial intelligence platforms. Server 10 can provide the terminal with the data required to generate a meeting during the process of a terminal (e.g., terminal 1) generating a meeting based on a calendar application interface. In one embodiment, server 10 can also provide the terminal with the data required to generate a calendar during the process of a terminal generating a calendar based on a calendar application interface. In another embodiment, server 10 can also provide the terminal with the data required to reserve a meeting room during the process of a terminal reserving a meeting room based on a calendar application interface.

[0037] In one embodiment, server 10 can also obtain and store data submitted by the terminal based on the calendar application interface, and when the data submitted by the calendar application interface is related to meeting business, it can obtain data related to meeting business based on the submitted data and send the data related to meeting business to the corresponding business module of the terminal for display, and when the data submitted by the calendar application interface is related to meeting room business, it can obtain data related to meeting room business based on the submitted data and send the data related to meeting room business to the corresponding business module of the terminal for display.

[0038] In one embodiment, server 10 may include a schedule server, a conference server, and a conference room server. In one embodiment, the schedule server can acquire and store data submitted by the terminal based on the schedule application interface. Furthermore, when the data submitted through the schedule application interface is related to conference services, the server can obtain relevant conference service data based on the submitted data and send this data to the corresponding business module on the terminal for display via the conference server. Similarly, when the data submitted through the schedule application interface is related to conference room services, the server can obtain relevant conference room service data based on the submitted data and send this data to the corresponding business module on the terminal for display via the conference room server.

[0039] In one embodiment, after receiving data submitted based on the calendar application interface, the server 10 may send a notification message to the terminal indicating that the calendar has been successfully created.

[0040] In one embodiment, the server 10 may also send a message indicating successful meeting creation to the terminal after acquiring data related to the meeting service.

[0041] In one embodiment, after acquiring data related to the conference room business, the server 10 can also send a notification message to the terminal indicating that the conference room has been successfully created.

[0042] The data processing methods mentioned above will be explained in detail below.

[0043] Please see Figure 2 This is a flowchart illustrating a data processing method provided in an embodiment of this application. The method can be applied to the aforementioned computer equipment. Specifically, the method may include the following steps:

[0044] S201. Display the meeting creation component in the calendar application interface of the target application.

[0045] In this embodiment, a user can access a target application on a computer device and open the calendar application interface of that application, thereby displaying a meeting creation component within the calendar application interface. This meeting creation component is a key component for associating a schedule with a meeting. In one embodiment, the meeting creation component is a meeting creation control. In another embodiment, the meeting creation component is a meeting settings switch; when the meeting settings switch is turned on, the schedule can be associated with a meeting, indicating that the user intends to create a meeting based on the calendar application interface. In yet another embodiment, the meeting settings switch is a voice / video conferencing switch; when the voice / video conferencing switch is turned on, the schedule can be associated with a meeting, specifically, with a voice / video conferencing session.

[0046] In this embodiment, a calendar application interface enables the creation of schedules, meetings, and the reservation of meeting rooms. The calendar application interface may include interface components such as time configuration options, meeting creation components, meeting room configuration options, and object configuration options (including but not limited to a topic information input field). These components are shared throughout the schedule creation, meeting creation, and meeting room reservation processes. Specifically, when the meeting creation component is not enabled, the calendar application interface displays general configuration options (time configuration options, meeting room configuration options, object configuration options, and a topic information input field, etc.) for the schedule creation, meeting creation, and meeting room reservation processes. When the meeting creation component is enabled, the calendar application interface displays the aforementioned general configuration options and personalized configuration components for the meeting creation process (such as meeting type configuration options).

[0047] For example, when the meeting creation component is set to a meeting settings switch and the switch is on, the meeting time can be configured via the time configuration option. When the meeting creation component is off, the schedule time can be configured via the time configuration option, i.e., the activity time corresponding to the schedule. For example, if the meeting creation component is set to a meeting settings switch and the switch is on, a meeting room configured based on the meeting room configuration option can be used as the meeting room for holding a meeting. When the meeting settings switch is off, a meeting room configured based on the meeting room configuration option can be used as the meeting room required for a schedule. For example, if the meeting creation component is set to a meeting settings switch and the switch is on, an object configured based on the object configuration option can be used as a participant object; here, the object configuration option is equivalent to the participant object configuration option. When the meeting settings switch is off, an object configured based on the object configuration option can be used as a participant object for the schedule. In other words, the terminal can create a standardized application interface for the process of creating schedule data, the process of creating a meeting, and the process of booking a meeting room through the target application. It does not require developing separate application interfaces for these processes (i.e., the functions implemented by these businesses), nor does it require maintaining separate processing logic for these processes, thereby improving business development efficiency and reducing business maintenance costs.

[0048] In one embodiment, the target application includes a schedule management module. This schedule management module can be a schedule subroutine capable of implementing schedule management functions. In one embodiment, the schedule subroutine can be a schedule applet. Alternatively, the schedule subroutine can be a schedule function module. In one embodiment, the schedule application interface is a designated application interface included in the schedule management module. In one embodiment, the designated application interface is a new schedule interface.

[0049] In one embodiment, the meeting creation component can be presented not only as a meeting settings switch, but also as a meeting settings menu bar, etc. This application embodiment does not limit this. The menu bar includes, but is not limited to, drop-down menu bars, pop-up menu bars, etc.

[0050] S202, In response to a first touch operation on the meeting creation component, display meeting configuration options in the schedule application interface.

[0051] In this embodiment, the user can perform a first touch operation on the meeting creation component. The computer device can then display meeting configuration options in the calendar application interface in response to this first touch operation. This embodiment configures meeting attribute information through meeting configuration options, including but not limited to parameters such as meeting type and / or meeting description and / or meeting importance indicator (which may include a general introduction to the meeting content or keywords related to the meeting content). Configuring these parameters based on the meeting configuration options allows meeting organizers and / or participants to quickly understand the general situation of the meeting.

[0052] In one embodiment, the first touch operation can be at least one of the following: long press, single click, double click, continuous click, swipe in a preset direction, or drag. In another embodiment, the first touch operation can also be replaced by air gestures, voice control, or other similar operations. For example, if the meeting creation component is a meeting settings switch, the first touch operation is a click that turns the meeting settings switch on. For example, if the meeting creation component is a meeting settings menu bar, the first touch operation is a click that expands or pops up the meeting settings menu bar.

[0053] In one embodiment, the meeting configuration options may include meeting type configuration options. In another embodiment, there may be multiple meeting type configuration options, meaning multiple meeting type configuration options can be displayed in the calendar application interface. The meeting type can be selected by choosing a meeting type configuration option. For example, the multiple meeting type configuration options may include online meeting options and offline meeting options. For example, the multiple meeting type configuration options may include audio conferencing options and video conferencing options.

[0054] In one embodiment, the meeting type configuration option can also be replaced by a meeting type input box. The meeting type input box allows users to input the meeting type.

[0055] In one embodiment, when the meeting configuration option is switched off, the meeting configuration option is hidden, meaning it is not displayed in the calendar application interface, and the user will not see it. In this case, meeting creation cannot be achieved through the calendar application interface, but event creation and / or meeting room booking are still possible. When the meeting configuration option is switched on, the meeting configuration option is displayed, meaning it is shown in the calendar application interface, and the user can see it. In this case, meeting creation, as well as the creation of related events and / or meeting room booking, can be achieved through the calendar application interface.

[0056] In one embodiment, the meeting configuration options may further include a meeting introduction input field. This field allows users to input a brief description of the meeting.

[0057] In one embodiment, the meeting configuration options may further include a meeting importance configuration option, which allows for the marking of meeting importance.

[0058] S203. In response to a second touch operation on the meeting configuration options, display the meeting configuration parameters obtained from the second touch operation in the calendar application interface.

[0059] In this embodiment of the application, the user can perform a second touch operation on the meeting configuration options, and the computer device can respond to the second touch operation on the meeting configuration options by displaying the meeting configuration parameters obtained by the second touch operation in the calendar application interface.

[0060] In one embodiment, the second touch operation can be at least one of the following: long press, tap, double tap, swipe in a preset direction, or drag. In another embodiment, the second touch operation can also be replaced by air gestures, voice control, or other similar operations.

[0061] In one embodiment, if the meeting configuration options include a meeting type configuration option, then the meeting configuration parameters include the meeting type. In one embodiment, if the meeting configuration options include a meeting type configuration option, and there are multiple meeting type configuration options, then the second touch operation can be a touch operation targeting a target meeting type configuration option among the multiple meeting type configuration options. The target meeting type configuration option is the meeting type configuration option selected from the multiple meeting type configuration options.

[0062] For example, the meeting configuration options are meeting type configuration options, and there are multiple meeting type configuration options, including online meeting options and offline meeting options. The second touch operation can be a click operation for the online meeting option or a click operation for the offline meeting option. Accordingly, if the second touch operation is a click operation for the online meeting option, then the meeting type included in the meeting configuration parameters is online meeting. If the second touch operation is a click operation for the offline meeting option, then the meeting type included in the meeting configuration parameters is offline meeting.

[0063] For example, the meeting configuration options include multiple meeting type configuration options, including audio conferencing and video conferencing options. The second touch operation can be a click operation on the audio conferencing option or a click operation on the video conferencing option. Accordingly, if the second touch operation is a click operation on the audio conferencing option, the meeting type included in the meeting configuration parameters is audio conferencing. If the second touch operation is a click operation on the video conferencing option, the meeting type included in the meeting configuration parameters is video conferencing.

[0064] In one application scenario, see Figure 3 The illustrated procedure for switching the audio / video conferencing switch on and off is as follows: When the switch is off, the user can click it to turn it on. After turning on the audio / video conferencing switch, the computer device will display meeting type options in the calendar application interface. The user can click the meeting type selection option to choose audio conferencing, at which point the meeting configuration parameters will include audio conferencing. Figure 3 The interface shown still displays calendar options and more information options.

[0065] In one embodiment, when the meeting configuration option is a meeting type input field, the second touch operation can be an input operation for the meeting type. Accordingly, if the second touch operation is an input operation for the meeting type, then the meeting type configuration parameters include the input meeting type.

[0066] In one embodiment, the meeting type option may also include other options. Correspondingly, the meeting type corresponding to these other options can be other. Furthermore, the input meeting type can also be other. It should be noted that, depending on the needs of the actual meeting scenario, the meeting type option includes, but is not limited to, the meeting type options mentioned above, and the meeting type also includes, but is not limited to, the meeting types mentioned earlier.

[0067] In one embodiment, if the meeting configuration options also include a meeting introduction input field, then the meeting configuration parameters also include the input meeting introduction, such as researching the latest technological directions in autonomous driving. In one embodiment, if the meeting configuration options also include a meeting importance configuration option, then the meeting configuration parameters also include the meeting importance, such as "very important".

[0068] S204. Generate the target meeting based on the meeting configuration parameters.

[0069] In this embodiment, the computer device can create a target meeting based on meeting configuration parameters. The target meeting is the meeting created using the calendar application interface.

[0070] In one embodiment, the computer device can obtain and display meeting configuration parameters related to the target meeting.

[0071] In one application scenario, if a user creates a meeting based on the calendar application interface, the user can also configure meeting configuration parameters such as participants, meeting time, and meeting room in the calendar application interface. The computer device can also obtain the configured meeting configuration parameters such as participants, meeting time, and meeting room. It should be noted that users can configure meeting-related information according to their own needs, and this application embodiment does not impose any restrictions on this.

[0072] visible, Figure 2 In this embodiment, the computer device can not only create schedules based on the schedule application interface, but also create meetings based on the schedule application interface. Using the schedule application interface for various transaction processing processes can improve business development efficiency and reduce business maintenance costs.

[0073] Please see Figure 4 This is a flowchart illustrating another data processing method provided in an embodiment of this application. This method can be applied to the aforementioned computer equipment. Specifically, the method may include the following steps:

[0074] S401. In response to a third touch operation on the scheduled meeting option in the target application, display a meeting creation component in the calendar application interface of the target application.

[0075] In this embodiment, a user can perform a third touch operation on the scheduled meeting option in the target application. The computer device can detect the third touch operation on the scheduled meeting option and then open the calendar application interface of the target application, displaying the meeting creation component in the calendar application interface. The third touch operation is a touch operation that opens the calendar application interface.

[0076] In one embodiment, the third touch operation can be at least one of the following: long press, single click, double click, continuous click, swipe in a preset direction, or drag. In another embodiment, the third touch operation can also be replaced by air gestures, voice control, or other similar operations.

[0077] In one embodiment, the target application further includes a meeting management module. The meeting management module can be understood as a meeting subroutine for meeting management. In one embodiment, the meeting subroutine may be a meeting applet. Alternatively, the meeting subroutine may be a meeting function module.

[0078] In one embodiment, if the target application further includes a meeting management module and the meeting management module has a scheduled meeting option, then displaying the meeting creation component in the calendar application interface of the target application in response to a third touch operation on the scheduled meeting option in the target application can be: displaying the meeting creation component in the calendar application interface in response to a third touch operation on the scheduled meeting option in the meeting management module. That is, the user can perform a third touch operation on the scheduled meeting option in the meeting management module, the computer device can detect the third touch operation on the scheduled meeting option, and then open the calendar application interface of the target application, displaying the meeting creation component in the calendar application interface. Typically, clicking the scheduled meeting option in the meeting management module will open the new meeting interface of the meeting management module (the new meeting interface is not the calendar application interface), but in this embodiment, the calendar application interface is opened uniformly.

[0079] In one embodiment, the target application further includes a meeting room management module. The meeting room management module can be understood as a meeting room subroutine for meeting room management. In one embodiment, the meeting room subroutine may be a meeting room applet. Alternatively, the meeting room subroutine may be a meeting room function module.

[0080] In one embodiment, if the target application further includes a meeting room management module and the meeting room management module has a scheduled meeting option, then displaying the meeting creation component in the calendar application interface of the target application in response to a third touch operation on the scheduled meeting option in the target application can be: displaying the meeting creation component in the calendar application interface in response to a third touch operation on the scheduled meeting option in the meeting room management module. That is, the user can perform a third touch operation on the scheduled meeting option in the meeting room management module, the computer device can detect the third touch operation on the scheduled meeting option, and then open the calendar application interface of the target application, displaying the meeting creation component in the calendar application interface. Generally speaking, clicking the scheduled meeting option in the meeting room management module will open the new meeting interface of the meeting room management module, but in this embodiment, the calendar application interface is opened uniformly.

[0081] In one embodiment, if a meeting scheduling option exists in the schedule management module, then displaying the meeting creation component in the schedule application interface of the target application in response to a third touch operation on the meeting scheduling option in the schedule management module can be: displaying the meeting creation component in the schedule application interface in response to a third touch operation on the meeting scheduling option in the schedule management module. That is, the user can perform a third touch operation on the meeting scheduling option in the schedule management module, the computer device can detect the third touch operation on the meeting scheduling option, and then open the schedule application interface of the target application, displaying the meeting creation component in the schedule application interface. Normally, clicking the meeting scheduling option in the schedule management module opens the new meeting interface of the schedule management module, but in this embodiment, the schedule application interface is opened uniformly.

[0082] In one embodiment, the target application also includes a chat window. The chat window can be a group chat window or a one-to-one chat window. The chat window includes a chat message editing bar. The chat message editing bar includes a chat text input box and a symbol indicating more functions, such as the "+" symbol. Clicking this symbol expands multiple function items, such as image options and schedule options (schedule options include, but are not limited to, schedule graphics and / or schedule text). Clicking the schedule option displays options to schedule a meeting and create a new schedule.

[0083] In one embodiment, if the scheduled meeting option is displayed after a click on the schedule option is detected, then displaying the meeting creation component in the schedule application interface of the target application in response to a third touch operation on the scheduled meeting option in the target application can be: displaying the meeting creation component in the schedule application interface of the target application in response to a third touch operation on the scheduled meeting option. That is, the computer device can display the scheduled meeting option after detecting a user's click on the schedule option, the user can perform a third touch operation on the scheduled meeting option, the computer device can detect the third touch operation on the scheduled meeting option, and then open the schedule application interface of the target application, displaying the meeting creation component in the schedule application interface. Normally, clicking on the scheduled meeting option opens a new meeting interface, but in this embodiment, the schedule application interface is opened uniformly.

[0084] It should be noted that the above are only some of the scenarios in which the meeting scheduling option appears, and the meeting scheduling option can also appear in other scenarios, which will not be elaborated here in the embodiments of this application.

[0085] S402. In response to a first touch operation on the meeting creation component, display meeting configuration options in the calendar application interface.

[0086] S403. In response to a second touch operation on the meeting configuration options, display the meeting configuration parameters obtained from the second touch operation in the calendar application interface.

[0087] S404. Generate the target meeting based on the meeting configuration parameters.

[0088] Steps S402-S404 can also be found in [reference needed]. Figure 2 Steps S202-S204 in the embodiment.

[0089] It should be noted that although in principle, the purpose of users touching the "Schedule Meeting" option is usually to schedule a meeting, after opening the calendar application interface, whether the user wants to book a meeting, reserve a meeting room, or create a schedule depends on the parameters set by the user in the calendar application interface and on the user's actual needs.

[0090] It can be seen that, in Figure 4 In this embodiment, after a user performs a third touch operation on the scheduled meeting option of the target application, they can schedule a meeting based on the calendar application interface.

[0091] In other embodiments, the computer device may also respond to a fourth touch operation on the meeting room reservation option in the target application, displaying a meeting creation component in the calendar application interface of the target application, and then executing steps S402-S404. This application employs this process, whereby a user performs a fourth touch operation on the meeting room reservation option in the target application, the computer device can detect the fourth touch operation on the meeting room reservation option, and subsequently open the calendar application interface of the target application, displaying the meeting creation component in the calendar application interface. Here, the fourth touch operation is a touch operation that opens the calendar application interface.

[0092] In one embodiment, the fourth touch operation can be at least one of the following operations: long press, single click, double click, continuous click, swipe in a preset direction, or drag. In another embodiment, the fourth touch operation can also be replaced by air gestures, voice control, or other similar operations.

[0093] In one embodiment, if the target application further includes a meeting room management module and the meeting room management module contains a meeting room booking option, then displaying the meeting creation component in the calendar application interface of the target application in response to a fourth touch operation on the meeting room booking option in the target application can be: displaying the meeting creation component in the calendar application interface in response to a fourth touch operation on the meeting room booking option in the meeting room management module. That is, the user can perform a fourth touch operation on the meeting room booking option in the meeting room management module, the computer device can detect the fourth touch operation on the meeting room booking option, and then open the calendar application interface of the target application, displaying the meeting creation component in the calendar application interface.

[0094] In one embodiment, if the schedule management module includes a meeting room booking option, displaying a meeting creation component in the schedule application interface of the target application in response to a fourth touch operation on the meeting room booking option in the schedule management module can be: displaying the meeting creation component in the schedule application interface in response to a fourth touch operation on the meeting room booking option in the schedule management module. That is, the user can perform a fourth touch operation on the meeting room booking option in the schedule management module, the computer device can detect the fourth touch operation on the meeting room booking option, and then open the schedule application interface of the target application, displaying the meeting creation component in the schedule application interface.

[0095] It should be noted that although in principle, the purpose of users touching the meeting room reservation option is usually to reserve a meeting room, after opening the calendar application interface, whether the user wants to reserve a meeting, reserve a meeting room, or create a schedule depends on the specific parameters set by the user in the calendar application interface and on the user's actual needs.

[0096] It should be noted that the above only lists a few scenarios in which meeting room reservation options may appear, and meeting room reservation options may also appear in other scenarios, which will not be elaborated here in the embodiments of this application.

[0097] In other embodiments, the computer device may also respond to a fifth touch operation on the schedule creation option in the target application, displaying a meeting creation component in the schedule application interface of the target application, and then executing steps S402-S403. This application employs this process, whereby a user performs a fifth touch operation on the schedule creation option in the target application, the computer device can detect the fifth touch operation on the schedule creation option, and subsequently open the schedule application interface of the target application, displaying the meeting creation component in the schedule application interface. Here, the fifth touch operation is a touch operation that opens the schedule application interface.

[0098] In one embodiment, the fifth touch operation can be at least one of the following operations: long press, single click, double click, continuous click, swipe in a preset direction, or drag. In another embodiment, the fifth touch operation can also be replaced by air gestures, voice control, or other similar operations.

[0099] In one embodiment, if the target application further includes a meeting room management module and the meeting room management module contains a "create schedule" option, then displaying the meeting creation component in the schedule application interface of the target application in response to a fifth touch operation on the "create schedule" option in the target application can be: displaying the meeting creation component in the schedule application interface in response to a fifth touch operation on the "create schedule" option in the meeting room management module. That is, the user can perform a fifth touch operation on the "create schedule" option in the meeting room management module, the computer device can detect the fifth touch operation on the "create schedule" option, and then open the schedule application interface of the target application, displaying the meeting creation component in the schedule application interface.

[0100] In one embodiment, if a "Create Schedule" option exists in the schedule management module, then displaying the meeting creation component in the schedule application interface of the target application in response to a fifth touch operation on the "Create Schedule" option in the schedule management module can be: displaying the meeting creation component in the schedule application interface in response to a fifth touch operation on the "Create Schedule" option in the schedule management module. That is, the user can perform a fifth touch operation on the "Create Schedule" option in the schedule management module, the computer device can detect the fifth touch operation on the "Create Schedule" option, and then open the schedule application interface of the target application, displaying the meeting creation component in the schedule application interface. In this embodiment, "Create Schedule" and "Create New Schedule" have the same meaning.

[0101] In one embodiment, the target application also includes a chat window. The chat window can be a group chat window or a one-to-one chat window. The chat window includes a chat message editing bar. The chat message editing bar includes a chat text input box and a symbol indicating more functions, such as the "+" symbol. Clicking this symbol expands multiple function items, such as schedule options (including but not limited to displaying schedule graphics and / or schedule text). Clicking the schedule option displays options to schedule a meeting and create a schedule.

[0102] In one embodiment, if the "Create Schedule" option is displayed after a click operation on the schedule option is detected, then displaying the meeting creation component in the schedule application interface of the target application in response to a third touch operation on the "Create Schedule" option in the target application can be: displaying the meeting creation component in the schedule application interface of the target application in response to a third touch operation on the "Create Schedule" option. That is, the computer device can display the "Create Schedule" option after detecting a user's click operation on the schedule option, the user can perform a third touch operation on the "Create Schedule" option, the computer device can detect the third touch operation on the "Create Schedule" option, and then open the schedule application interface of the target application, displaying the meeting creation component in the schedule application interface.

[0103] In one embodiment, the target application further includes a chat window, which includes a chat dialog box or chat content. Clicking the chat dialog box or chat content displays a schedule option. In one embodiment, if the terminal displays the schedule option after detecting an operation such as a long press on the chat dialog box or chat content, then displaying the meeting creation component in the schedule application interface of the target application in response to a fifth touch operation on the create schedule option in the target application can be: displaying the meeting creation component in the schedule application interface of the target application in response to a fifth touch operation on the schedule option. That is, the user can long press the chat dialog box or chat content to display a schedule option in the chat window, and the user can perform a fifth touch operation on the schedule option. The computer device can detect the fifth touch operation on the create schedule option, and then open the schedule application interface of the target application, displaying the meeting creation component in the schedule application interface.

[0104] For example, such as Figure 5A As shown, users can long-press the chat dialog box to display the schedule option on the computer device, and then open the schedule application interface by clicking the schedule option. Alternatively, users can click the symbol that indicates more functions to display the schedule option on the computer device. Users can further click the schedule option to display the option to schedule a meeting (not shown) and the option to create a schedule (not shown). Users can open the schedule application interface by clicking the option to schedule a meeting or the option to create a schedule.

[0105] It should be noted that although in principle, the purpose of users touching the calendar option or creating a calendar is usually to create a calendar, after opening the calendar application interface, whether the user wants to book a meeting, book a meeting room, or create a calendar depends on the parameters set by the user based on the calendar application interface and on the user's actual needs.

[0106] It should be noted that the above are only some of the scenarios in which the "Create Schedule" option appears. There are other scenarios in which the "Create Schedule" option can appear, which will not be elaborated here.

[0107] It should be noted that, in addition to the meeting creation component and the meeting configuration options displayed after detecting the first touch operation on the meeting creation component, the schedule application interface mentioned in this solution may also include the aforementioned interface components such as the topic information input field, object configuration options, time configuration options, and meeting room configuration options. The following is a detailed description of these interface elements included in the schedule application interface.

[0108] In one embodiment, the topic information input field is used to configure the topic. It can be understood that when the meeting creation component has the meeting settings switch on and off, the topic entered in the topic information input field can be used as the meeting topic. When the meeting settings switch is off, the topic entered in the topic information input field can be understood as the schedule topic. For example, see... Figure 5B The interface shown allows users to... Figure 5B The topic is entered in the topic information input field of the interface shown. In one embodiment, if a topic is entered in the topic information input field during the creation of the target meeting, the meeting configuration parameters also include the topic entered in the topic information field; that is, the meeting configuration parameters can also include the meeting topic of the target meeting.

[0109] In one embodiment, object configuration options are used to configure objects. It is understood that when the meeting creation component has a meeting settings switch on and the meeting settings switch is in the "on" state, the object configuration options can serve as participant object configuration options, and objects selected based on these options can be used as participant objects. When the meeting creation component has a meeting settings switch on and the meeting settings switch is in the "off" state, the object configuration options can serve as schedule participant object configuration options, and objects selected based on these options can be used as schedule participants. For example, see... Figure 5B The interface shown has the following object configuration options: Figure 5B The participant configuration options shown can be clicked by the user. The computer device can detect this click and display a list of participants for selection. During the creation of the target meeting, if participants are selected based on the participant configuration options, the meeting configuration parameters can also include the selected participants; that is, the meeting configuration parameters can also include the participants of the target meeting.

[0110] In one embodiment, during the creation of a target meeting based on a calendar application interface, the computer device can respond to a sixth touch operation on the participant configuration options and display a list of candidate participants on the calendar application interface; responding to a second selection operation on a candidate participant in the candidate participant list, the candidate participant obtained by the second selection operation is determined as a participant in the target meeting. Correspondingly, the terminal can also obtain the participants configured based on the participant configuration options, and the meeting configuration parameters may include the participants of the target meeting. The sixth touch operation can be at least one of the following operations: long press, single click, double click, continuous click, swipe in a preset direction, or drag. In one embodiment, the fifth touch operation can also be replaced by air gesture operation, voice control operation, etc. The second selection operation is an operation to select a candidate participant, such as a click operation.

[0111] In one embodiment, after acquiring the configured object, the computer device can display calendar data viewing options in the calendar application interface. For example, with Figure 5C For example, the options for viewing schedule data are as follows: Figure 5C The control shown is for viewing the schedule. If the computer device detects a touch operation, such as a click, on the control for viewing the schedule, it can display the schedule data for the object selected based on the object configuration options, so as to facilitate the setting of at least one of the following: schedule time, meeting time, and meeting room usage time.

[0112] For example, in a scenario where a meeting is created using a calendar application interface, a user can click on the control to view the schedule. The computer device can detect the click on the schedule control and display something like... Figure 5D The image shows the meeting schedule data for attendees. Users can view this data to set meeting times. If a user sets a meeting time based on attendee schedule data, the computer device can retrieve the set meeting time and update it accordingly. Figure 5C The interface shown should be noted as follows: Figure 5C The displayed meeting times are those that haven't been updated yet. If the user wants to... Figure 5D If you are not satisfied with the set meeting time, you can also adjust it based on... Figure 5C The time configuration options shown allow you to reset the meeting time. It should be noted that when creating a meeting using the calendar application interface, this should be enabled. Figure 5C Voice / video conferencing switch.

[0113] In one embodiment, the scheduling application interface may further include time configuration options. These options allow configuration of at least one of the following: schedule time, meeting time, and meeting room usage time. For example, ... Figure 5BAs shown, the time configuration options include date configuration options, start time configuration options, duration configuration options, and a switch to indicate whether the duration is set to full day. If the switch to indicate full day is on, the duration will be set to full day. It should be noted that... Figure 5B The switch indicating whether the duration is set to all day is off. In one embodiment, the duration configuration option can also be replaced with a meeting end time configuration option.

[0114] In one embodiment, when creating a meeting, the meeting time can be obtained in one of two ways: first, by configuring the time configuration option, and second, by selecting the aforementioned schedule data.

[0115] In one embodiment, for the first approach, the computer device may, in response to a meeting time configuration operation on a time configuration option, obtain the configured meeting time based on the meeting time configuration operation.

[0116] In one embodiment, for the second approach, the computer device can respond to a seventh touch operation on the schedule data viewing option in the schedule application interface, displaying the schedule data of the participants of the target meeting in the schedule application interface; and obtaining the meeting time selected based on the schedule data. The seventh touch operation can be at least one of the following: long press, single click, double click, triple click, swipe in a preset direction, or drag. In one embodiment, the fifth touch operation can also be replaced by air gestures, voice control, etc. The schedule data can include data such as the participants' schedule arrangements over multiple time periods. The meeting time selected based on the schedule data can include the meeting date, meeting start time, and meeting end time.

[0117] In one embodiment, the time configured based on the time configuration option can include information such as date, start time, and duration. For example, in the scenario of creating a meeting, the time configured based on the time configuration option can be used as the meeting time, the corresponding date can be used as the meeting date, the start time can be understood as the meeting start time, and the duration can be used as the meeting duration. The time configured based on the time configuration option can also be used as the schedule time, which will not be elaborated upon here.

[0118] In one embodiment, the scheduling application interface may further include meeting room configuration options. These options allow for the configuration of meeting rooms. In another embodiment, if a target meeting room is configured based on the target application interface, the meeting configuration parameters may further include the target meeting room.

[0119] In one embodiment, the target meeting room can be configured as follows: In response to an eighth touch operation on the meeting room configuration option, the computer device displays a list of candidate meeting rooms in the schedule application interface; in response to a third selection operation on a candidate meeting room in the candidate meeting room list, the candidate meeting room obtained by the third selection operation is determined as the target meeting room for the target meeting. The eighth touch operation can be at least one of the following: long press, single click, double click, continuous click, swipe in a preset direction, or drag. In one embodiment, the fifth touch operation can also be replaced by air gestures, voice control, etc. The third selection operation can be a click operation to select a candidate meeting room. In one embodiment, the computer device can obtain the list of candidate meeting rooms from the meeting room server by calling the meeting room management module through the schedule management module, or the schedule management module can obtain the list of candidate meeting rooms from the meeting room server by calling the meeting room interface.

[0120] In one embodiment, when the target meeting room is a meeting room awaiting review, generating the target meeting based on the meeting configuration parameters includes: displaying review options for the target meeting room in the calendar application interface; displaying reservation information for the target meeting room in the calendar application interface in response to a ninth touch operation on the review options for the target meeting room; and generating the target meeting based on the meeting configuration parameters in response to a confirmation operation on the reservation information for the target meeting room. In one embodiment, the ninth touch operation can be at least one of the following operations: long press, single click, double click, continuous click, swipe in a preset direction, or drag. In one embodiment, the ninth touch operation can also be replaced by air gesture operation, voice control operation, etc.

[0121] In one embodiment, when the target meeting room is the meeting room to be reviewed, if a touch operation is detected for the meeting room selection option (i.e., the review option), the computer device may display... Figure 5E The interface shown (including details of the selected meeting room) displays the reservation information for the target meeting room within the scheduling application interface. After configuring or confirming the relevant information, the user can click the submit button. The computer device will respond to this click, submitting the approval process. After the approval process is completed, the target meeting can be generated based on the meeting configuration parameters. See also... Figure 5E The interface shown includes at least one of the following meeting room details: participant information, meeting time, meeting room information (including meeting room ID), and approver information. The confirmation action is clicking the submit button.

[0122] In one embodiment, the scheduling application interface may further include a calendar option, wherein the calendar option is used to display calendar information, such as the calendar to which the event or meeting belongs, such as user A's calendar. In one embodiment, the scheduling application interface may further include more information options, such as... Figure 5B As shown. The "More Information" option also displays reminder options, recurring options, and attachment options within the calendar application interface. See [link to relevant documentation]. Figure 5C The options include: **Reminder Options:** Configure the reminder method, such as the reminder time for a schedule or meeting, for example, how far in advance the reminder should begin (e.g., 15 minutes before the meeting starts). **Repeat Options:** Configure the repetition method for the schedule or meeting, such as daily reminders, weekly reminders, etc. **Add Attachment Options:** Used to add attachments. In one embodiment, the "More Information" option may also include a work discussion display item. In one embodiment, if the user clicks the schedule option displayed after long-pressing the chat content dialog box, the "More Information" option may include a work discussion display item, which includes the chat content in the pressed chat content dialog box.

[0123] In one embodiment, the scheduling application interface may include a button indicating that the scheduling is complete, such as a save button, submit button, finish button, or confirm button. The user can click the button indicating that the scheduling is complete, and the computer device, upon detecting the touch operation on that button, can generate the target meeting based on the meeting configuration parameters.

[0124] In one embodiment, the meeting configuration parameters mentioned in this application may include meeting configuration parameters related to the target meeting. In one embodiment, the meeting configuration parameters related to the target meeting may be data that the meeting management module needs to record.

[0125] In one embodiment, the meeting configuration parameters mentioned in this application embodiment may also include schedule-related meeting configuration parameters, which may also generate data that the schedule management module needs to record.

[0126] In one embodiment, if the target meeting room where the target meeting is located is also configured based on the calendar application interface, the meeting configuration parameters may also include meeting configuration parameters related to the target meeting room.

[0127] In one embodiment, after detecting a touch operation on the button indicating that the schedule has been set, the terminal can obtain data based on the schedule application interface configuration, which includes meeting configuration parameters, and send the data based on the schedule application interface configuration to the schedule server for storage.

[0128] In one embodiment, if a meeting room is also configured based on the calendar application interface, the data submitted by the computer device to the server based on the calendar application interface may include some data that the calendar management module needs to record, some data that the meeting management module needs to record, and some data that the meeting room management module needs to record.

[0129] In one embodiment, the data that the schedule management module needs to record may include schedule title, schedule participants, schedule time, reserved meeting room, calendar information, meeting reminder method, meeting repetition method, and other schedule-related data.

[0130] In one embodiment, the data that the meeting management module needs to record may include meeting-related data such as meeting topic, participants, meeting time, reserved meeting room, and meeting status.

[0131] In one embodiment, the data that the meeting room management module needs to record may include the reserved meeting room, the meeting room location, the meeting room reservation time (including the reserved start time and reserved end time, which can be obtained based on the meeting time), the meeting room status, and other meeting room-related data.

[0132] In one embodiment, after setting up any one of the schedule, meeting, or meeting room, the computer device can display partial schedule-related data through the schedule management module. In one embodiment, this partial schedule-related data includes, for example... Figure 5F As shown.

[0133] In one embodiment, the computer device can synchronize meeting configuration parameters related to the target meeting to the meeting management module via the schedule management module. In another embodiment, the computer device can send the meeting configuration parameters related to the target meeting to a schedule server via the schedule management module. The schedule management server then forwards the meeting configuration parameters to the meeting server. The meeting management module can then retrieve the meeting configuration parameters related to the target meeting from the meeting server, thus realizing the process of synchronizing the meeting configuration parameters related to the target meeting to the meeting management module via the schedule management module. Users can view the meeting configuration parameters related to the target meeting in the meeting management module.

[0134] In one embodiment, the computer device can synchronize the meeting room configuration parameters related to the target meeting room to the meeting room management module through the schedule management module. In another embodiment, the computer device can send the meeting room configuration parameters related to the target meeting room to the schedule server through the schedule management module, and the schedule server forwards the meeting room configuration parameters related to the target meeting room to the meeting room server. Then, the meeting room management module can obtain the meeting room configuration parameters related to the target meeting room from the meeting room server, thereby realizing the process of synchronizing the meeting room configuration parameters related to the target meeting room to the meeting room management module through the schedule management module.

[0135] The above process enables the unified distribution of business-related data by the backend server corresponding to the schedule management module.

[0136] The following is combined Figure 6 The business functions implemented based on the calendar application interface in the embodiments of this application will be briefly described.

[0137] like Figure 6 As shown, users can initiate a meeting scheduling request within the enterprise communication software. The software can detect the request, and users can schedule the meeting through the software's scheduling subroutine. For example, see... Figure 6 Users can perform touch operations on the meeting scheduling option included in the meeting management module of the enterprise communication software. If the computer device detects the touch operation on the meeting scheduling option in the meeting management module of the enterprise communication software, it can open the calendar application interface in the calendar management module of the enterprise communication software, where users can schedule meetings. In this solution, scheduling a meeting and creating a meeting are the same thing.

[0138] like Figure 6 As shown, users can initiate a meeting room reservation request within the enterprise communication software. The software can detect the request, and users can then reserve the meeting room through the software's scheduling subroutine. For example, see... Figure 6 Users can perform touch operations on the meeting room reservation options included in the meeting room management module of the enterprise communication software. If the computer device detects the touch operation on the meeting room reservation options included in the meeting room management module of the enterprise communication software, it can open the calendar application interface in the calendar management module of the enterprise communication software, and users can reserve meeting rooms in the calendar application interface.

[0139] like Figure 6As shown, users can initiate a request to create a schedule within the enterprise communication software. Once the enterprise communication software detects the request, the user can create the schedule within its schedule subroutine. Specifically, after detecting a request to schedule a meeting, the enterprise communication software can open the schedule application interface, where the user can create the schedule. For example, see... Figure 6 Users can perform touch operations on the "Create Schedule" option included in the meeting room management module of the enterprise communication software. If the computer device detects the touch operation on the "Create Schedule" option included in the meeting room management module of the enterprise communication software, it can open the schedule application interface in the schedule management module of the enterprise communication software, and users can book meeting rooms in the schedule application interface.

[0140] The following section details the process of users scheduling meetings using the calendar application interface.

[0141] Users can click the meeting booking option in the enterprise communication software to initiate a meeting booking request. The terminal can respond to the click operation of the meeting booking option, open the calendar application interface, and display meeting settings components such as the voice / video conferencing settings switch in the calendar application interface.

[0142] When a user turns on the voice / video conferencing settings switch in the calendar application interface, the terminal detects the activation of the voice / video conferencing settings switch and displays meeting type options in the calendar application interface. The user can then click on a meeting type option. After the terminal detects the click on the meeting type option, it displays a list of meeting types, which the user can then select from.

[0143] Users can also enter the meeting topic in the topic information input field.

[0144] Users can also configure the participants for the target meeting in the participant configuration option.

[0145] After the terminal detects the user's confirmation of the selected participants, it can display controls for viewing the schedule on the schedule application interface.

[0146] Users can also configure meeting times based on time configuration options.

[0147] After the user configures the meeting time using the time-based configuration option, the terminal calls the schedule management module to determine if there is a conflict between the selected participant's schedule and the configured meeting time. If a conflict is found, the user is prompted to reset the meeting time. Alternatively, in the event of a conflict, the user can either reconfigure the meeting time using the time-based configuration option or click the schedule view control. Upon detecting this click, the terminal generates a schedule data retrieval request and sends it to the schedule server. The schedule server uses the selected participant information carried in the request to query the selected participant's schedule data and sends it to the terminal, which can then display the selected participant's schedule data. The user can then reconfigure the meeting time based on the selected participant's schedule data. It should be noted that even if there is a conflict between a participant and the configured meeting time, the user can ignore the time conflict and continue configuring other meeting parameters.

[0148] Users can also configure meeting rooms based on the meeting room configuration options.

[0149] If a click operation based on the meeting room configuration options is detected, the terminal can invoke the meeting room management module to obtain a list of candidate meeting rooms. The user can then select a meeting room from this list. After selecting a meeting room, the user can click the "Approve" option (this option can also be replaced with a "Reserve" or "Confirm" option, which triggers the approval process). Upon detecting this click, the terminal checks if the selected meeting room is pending approval. If so, the approval process is triggered. Specifically, the approval process involves the computer displaying reservation information for the selected meeting room. The user can confirm this reservation. Upon detecting this confirmation, the computer sends an approval request for the selected meeting room to the meeting room server, carrying the reservation information. The meeting room server then performs the approval operation based on the request. Specifically, the approval process involves the meeting room server generating a reservation application form for the selected meeting room based on the reservation information and sending it to the appropriate reviewer (e.g., the meeting room administrator) for review. Subsequently, the meeting room server updates the approval status of the selected meeting room based on the reviewer's assessment.

[0150] Users can also configure reminder methods for scheduled meetings based on the reminder method configuration options, such as setting a reminder 15 minutes before the meeting starts, and / or configure the recurrence method for scheduled meetings, such as no recurrence or monthly recurrence, where monthly recurrence means the scheduled meeting will be held once a month. The reminder method and recurrence method can be configured as default options.

[0151] It's worth noting that in scenarios where meetings are created using the calendar application interface, not only can meetings be created, but also schedules. Furthermore, if a user has configured a meeting room in the calendar application interface, that meeting room reservation can also be made. In this case, meeting, scheduling, and meeting room services will share some parameters configured through the calendar application interface, achieving data integration between different services.

[0152] The following provides further explanation of the process for creating meetings and / or meeting rooms based on the calendar application interface.

[0153] Scenario 1: In a scenario where a user creates a meeting using the calendar application interface but does not reserve a meeting room, the computer device can obtain the data configured by the user in the calendar application interface, and can also obtain the schedule creation record and meeting creation record. The schedule creation record and meeting creation record are linked.

[0154] The computer device can acquire data configured by the user in the calendar application interface, and then submit this data to the calendar server through the calendar management module. The calendar server can generate calendar creation records based on the data configured in the calendar application interface and update these records in the calendar management module. In addition, the calendar server can also send meeting-related data to the meeting server, which will then generate meeting creation records based on the received data and update them in the meeting management module.

[0155] In the above scenario, the schedule server can generate a schedule ID (to identify an event where a schedule is created) and a corresponding schedule creation record based on the data configured in the schedule application interface. The schedule server can determine meeting-related data from the data configured in the schedule application interface and send the schedule ID and meeting-related data to the meeting server. The meeting server generates a meeting ID (to identify a scheduled meeting event; this meeting ID is not the meeting number) and a corresponding meeting creation record based on the meeting-related data. The meeting server maintains the correspondence between the schedule ID, meeting ID, and meeting creation record. Additionally, the meeting server also sends the meeting ID to the schedule server. The schedule server maintains the correspondence between the schedule ID, meeting ID, and schedule creation record.

[0156] In the above scenarios, computer devices can obtain schedule IDs, meeting IDs, and schedule creation records from the schedule server through the schedule management module, and users can view the schedule creation records in the schedule management module. Similarly, computer devices can obtain schedule IDs, meeting IDs, and meeting creation records from the meeting server through the meeting management module, and users can view the meeting creation records in the meeting management module. The meeting management module can associate specific schedule records with schedule IDs, and the schedule management module can associate specific meeting records with meeting IDs. In one application scenario, if the computer device detects a command to view data in a meeting creation record based on the schedule management module, it will invoke the meeting management module to view the data in the meeting creation record. Likewise, if the computer device detects a command to view data in a schedule creation record based on the meeting management module, it will invoke the schedule management module to view the data in the schedule creation record.

[0157] Scenario 2: In a scenario where a user creates a meeting and reserves a meeting room through the calendar application interface, the computer device can obtain the data configured by the user in the calendar application interface, and can obtain the schedule creation record, meeting creation record, and meeting room reservation record. These three records are interconnected.

[0158] The computer device can acquire data configured by the user in the scheduling application interface, and then submit this data to the scheduling server through the scheduling management module. The scheduling server can generate a schedule creation record based on the data configured in the scheduling application interface and update the schedule creation record in the scheduling management module. In addition, the scheduling server can also send meeting-related data to the meeting server, which will generate a meeting creation record based on the received meeting-related data and update it in the meeting management module. Furthermore, the scheduling server can also send meeting room-related data to the meeting room server, which will generate a meeting room ID (used to identify a meeting room reservation event; this meeting room ID is not the meeting room name, but rather a room number) and a meeting room reservation record based on the received meeting room-related data, and update the meeting room creation record in the meeting room management module.

[0159] In the above scenarios, the schedule server can generate a schedule ID and a corresponding schedule creation record based on the data configured in the schedule application interface. The schedule server can also determine meeting-related data from the data configured in the schedule application interface and send the schedule ID and meeting-related data to the meeting server. The meeting server generates a meeting ID and a corresponding meeting creation record based on the meeting-related data. The meeting server maintains the correspondence between the schedule ID, meeting ID, and meeting creation record. Additionally, the meeting server also sends the meeting ID to the schedule server. The schedule server can also determine meeting room-related data from the data configured in the schedule application interface and send the schedule ID and meeting room-related data to the meeting room server. The meeting room server generates a meeting room ID and a corresponding meeting room reservation record based on the meeting room-related data. The meeting room server maintains the correspondence between the schedule ID, meeting room ID, and meeting room reservation record. Additionally, the meeting room server also sends the meeting room ID to the schedule server. The schedule server maintains the correspondence between the schedule ID, meeting ID, meeting room ID, and schedule creation record.

[0160] In one sub-application scenario described above, a computer device can obtain a schedule ID, meeting ID, meeting room ID, and schedule creation record from the schedule server through the schedule management module. Users can then view these schedule creation records within the schedule management module. Similarly, a computer device can obtain a schedule ID, meeting ID, and meeting creation record from the meeting server through the meeting management module. Users can then view these meeting creation records within the meeting management module. The meeting management module can associate specific schedule records with schedule IDs, and vice versa. Likewise, a computer device can obtain a schedule ID, meeting room ID, and meeting room reservation record from the meeting room management module. Users can then view these meeting room reservation records within the meeting room management module. The meeting room management module can associate specific schedule records with schedule IDs, and vice versa. In another application scenario, if the computer device detects a command to view data in a meeting creation record based on the schedule management module, it will invoke the meeting management module to view that data. Likewise, if the computer device detects a command to view data in a schedule creation record based on the meeting management module, it will invoke the schedule management module to view that data. In one application scenario, if a computer device detects a command to view data in the meeting room reservation record based on the schedule management module, it will invoke the meeting room management module to view the data in the meeting room reservation record. Similarly, if a computer device detects a command to view data in the schedule creation record based on the meeting room management module, it will invoke the schedule management module to view the data in the schedule creation record.

[0161] In another sub-application scenario described above, the meeting server can also send the meeting ID to the meeting room server, and similarly, the meeting room server can send the meeting room ID to the meeting server. Thus, the meeting server can maintain the correspondence between the schedule ID, meeting ID, meeting room ID, and meeting creation record, and the meeting room server can maintain the correspondence between the schedule ID, meeting ID, meeting room ID, and meeting room reservation record. Correspondingly, the meeting management module can obtain the schedule ID, meeting ID, meeting room ID, and meeting creation record from the meeting management server. The meeting room management module can obtain the schedule ID, meeting ID, meeting room ID, and meeting room reservation record from the meeting room server. Unlike the previous sub-application scenario, in this sub-application scenario, the meeting server can also obtain the meeting room ID from the meeting server, and the meeting management module can also obtain the meeting ID from the meeting server. The meeting room server can obtain the meeting ID from the meeting server, and the meeting room management module can also obtain the meeting ID from the meeting room server. Scenario 3: In the scenario where a user has reserved a meeting room without creating a meeting based on the schedule application interface, the computer device can obtain the data configured by the user in the schedule application interface, and can obtain the schedule creation record and meeting room reservation record. The schedule creation record and meeting room reservation record are related.

[0162] The computer device can acquire data configured by the user in the scheduling application interface, and then submit this data to the scheduling server through the scheduling management module. The scheduling server can generate schedule creation records based on the data configured in the scheduling application interface and update these records in the scheduling management module. Furthermore, the scheduling server can also send meeting room-related data to the meeting room server, which will then generate meeting room IDs and meeting room reservation records based on the received data and update these records in the meeting room management module.

[0163] In the above scenario, the schedule server can generate a schedule ID and a corresponding schedule creation record based on the data configured in the schedule application interface. The schedule server can also determine meeting room-related data from the data configured in the schedule application interface and send the schedule ID and meeting room-related data to the meeting room server. The meeting room server generates a meeting room ID and a corresponding meeting room reservation record based on the meeting room-related data. The meeting room server maintains the correspondence between the schedule ID, meeting room ID, and meeting room reservation record. Furthermore, the meeting room server also sends the meeting room ID to the schedule server. The schedule server maintains the correspondence between the schedule ID, meeting room ID, and schedule creation record.

[0164] In the above scenario, the computer device can obtain the schedule ID, meeting room ID, and schedule creation record from the schedule server through the schedule management module, and the user can view the schedule creation record in the schedule management module. Similarly, the computer device can obtain the schedule ID, meeting room ID, and meeting room reservation record from the meeting room management module, and the user can view the meeting room reservation record in the meeting room management module. The meeting room management module can associate specific schedule records with schedule IDs, and vice versa. In one application scenario, if the computer device detects a command to view data in the meeting room reservation record based on the schedule management module, it will invoke the meeting room management module to view the data in the meeting room reservation record. Likewise, if the computer device detects a command to view data in the schedule creation record based on the meeting room management module, it will invoke the schedule management module to view the data in the schedule creation record.

[0165] The above process describes the process of generating different business data based on a unified schedule entry point. The unified business data distribution process is realized through the schedule server, which is equivalent to realizing the process of business data distribution by a unified schedule entry point. Furthermore, based on the different business data generated by the unified schedule entry point, some business data can be reused for different businesses, realizing the data integration process for different businesses.

[0166] In one embodiment, the aforementioned schedule creation record may include the schedule topic, schedule participants, schedule time, reserved meeting room, calendar information, reminder method, repetition method, etc. The reserved meeting room here specifically refers to the name of the reserved meeting room.

[0167] In one embodiment, the aforementioned meeting creation record may include the meeting topic, participants, meeting time, reserved meeting room, meeting status, etc. The meeting status may be, for example, not started, in progress, or ended. The meeting status can be updated based on the meeting's progress; for example, if the meeting has not yet been held, the meeting status may be "not started"; if the meeting has been held, the meeting status will be updated to "ended."

[0168] In one embodiment, the aforementioned meeting room reservation record may include the reserved meeting room, the reserved time, the meeting room status, etc. In another embodiment, the meeting room status may include at least one of approval status, reservation status, and occupancy status. The approval status, reservation status, and occupancy status of the meeting room can be updated based on the approval status of the meeting room, respectively. For example, if a reserved meeting room has not yet been approved, the approval status will be "approved but not approved." If the reserved meeting room is subsequently approved, the approval status will be updated to "approved but not approved."

[0169] In other embodiments, the present solution optimizes the aforementioned approval process as follows:

[0170] In one embodiment, if the target meeting room is a meeting room awaiting approval, the computer device can obtain historical approval records for the target meeting room. The system can then determine whether the target meeting room meets the criteria for expedited approval based on these records. If it does, the expedited approval interface is invoked to perform a quick approval operation based on the meeting room's reservation information. In one embodiment, the historical approval records include approval results for the target meeting room within a target time frame, such as the approval results for the most recent three months. Determining whether the target meeting room meets the expedited approval criteria based on historical approval records can be achieved as follows: if all historical approval results are approved, the expedited approval interface can be invoked to generate approval information, thus achieving expedited approval. This process is suitable for some fixed approval processes. For example, for meeting rooms where basic application is sufficient for approval, if a longer approval process is required, this method can achieve expedited approval, helping approvers and applicants save time and improve efficiency.

[0171] In one embodiment, if the target meeting room is a meeting room awaiting approval, the computer device can obtain historical approval records for all meeting rooms the user has applied for that are awaiting approval. The system can then determine whether the target meeting room meets the criteria for expedited approval based on these records. If it does, the expedited approval interface is invoked to perform a quick approval operation based on the meeting room's reservation information. In one embodiment, the historical approval records include historical approval results. Determining whether the target meeting room meets the expedited approval criteria based on these records can be achieved as follows: if the historical approval results indicate that the user has received approval for all meeting rooms they have applied for that are awaiting approval, the expedited approval interface can be invoked to generate approval information, thus achieving expedited approval. This process is suitable for some fixed approval processes, such as meeting rooms that can be approved with a basic application. If a longer approval process is required, this method can achieve expedited approval, helping approvers and applicants save time and improve efficiency.

[0172] In other embodiments, the proposed solution optimizes the process for determining the target meeting room as follows.

[0173] In large enterprises, meeting room resources may be scarce. To avoid wasting resources in large meeting rooms, the computer can, upon detecting a touch operation on meeting room configuration options, access the meeting room management module to obtain meeting room details for each meeting room within the user's enterprise. Based on these details and the configured meeting time, the number of available non-shared meeting rooms for that time period is determined. If the number of available non-shared meeting rooms is less than a preset number, a list of available shared meeting rooms for that time period is generated. A shared meeting room selected from this list is then chosen as the target meeting room.

[0174] In one embodiment, meeting room details may include a label indicating whether each meeting room is a shared meeting room and the occupancy status of each meeting room at different times. The method for determining the number of available non-shared meeting rooms at the meeting time based on the meeting room details and the configured meeting time can be as follows: Based on the label indicating whether each meeting room is a shared meeting room, the occupancy status of each meeting room at different times, and the configured meeting time, determine the number of available non-shared meeting rooms at the meeting time. If the number of available non-shared meeting rooms is less than a preset number, generate a list of available shared meeting rooms for that meeting time, and obtain a shared meeting room selected based on the list of available shared meeting rooms as the target meeting room. Correspondingly, the method for generating the list of available shared meeting rooms at that meeting time can be as follows: Based on the label indicating whether each meeting room is a shared meeting room, the occupancy status of each meeting room at different times, and the configured meeting time, determine the available shared meeting rooms for that meeting time, and generate a list of available shared meeting rooms for that meeting time based on the available shared meeting rooms.

[0175] In one embodiment, the computer device can obtain a shared meeting room selected based on a list of available shared meeting rooms by: obtaining the number of applicants for the shared meeting room during the meeting time, and obtaining the maximum number of applicants set for the target meeting room; then, based on the number of applicants during the meeting time and the maximum number of applicants set for the target meeting room, selecting a shared meeting room that meets preset conditions from the list of candidate meeting rooms as the target meeting room. In another embodiment, the method for selecting a shared meeting room that meets preset conditions from the list of candidate meeting rooms as the target meeting room can be: determining from the list of available shared meeting rooms that the difference between the maximum number of applicants and the number of applicants is less than a preset difference, and using this as the target meeting room. Alternatively, selecting the meeting room with the smallest difference between the maximum number of applicants and the number of applicants from the list of available shared meeting rooms as the target meeting room. This method maximizes the selection of relatively less resource-constrained shared meeting rooms for users when meeting room resources are scarce.

[0176] In other embodiments, the following optimizations are made to the participant configuration process:

[0177] Because the meeting participants' schedules involve a large amount of information, the process of comprehensively understanding all the schedule data and then making a decision on a suitable meeting time is time-consuming. Therefore, computer devices can acquire the meeting participants' schedule data and generate a list of available time slots, including time slots where all participants are available. The computer devices can then select available time slots from this list to determine the meeting time for the target meeting.

[0178] In other embodiments, the selection process for candidate participants is optimized as follows:

[0179] Typically, a candidate participant list displays contacts from the enterprise communication application's address book or group chats, or all contacts registered with the user's company within the application. However, selecting participants through this lookup method is time-consuming. Therefore, the computer device can obtain the schedule data of all contacts registered with the user's company within the enterprise communication application. Based on this data, it generates a list of available participants for each time period across multiple time slots. The computer device then selects participants from this list to serve as attendees for the target meeting.

[0180] In addition, regarding the aforementioned data processing methods, the following section will combine... Figure 7 The data processing procedure will be explained.

[0181] Users can open the new schedule interface of the enterprise communication software (the schedule application interface described in the embodiments of this application).

[0182] Users can select participants on the new event page, and the computer device can retrieve the selected participants. Specifically, users can click the participant configuration option on the new event page. When the computer device detects this click, it displays a list of candidate participants. Users can then select participants from this list, and the computer device will retrieve and display the selected participants on the new event page.

[0183] After the user selects participants, the computer device can display a schedule viewing option on the new schedule interface. The user can click this option, and the computer device will respond by displaying the schedule data of the selected participants. The user can then configure settings such as schedule time or meeting time based on this data, and the computer device can retrieve the times set by the user based on this schedule data. The new schedule interface may also include a time configuration option, which the user can also use to set the time.

[0184] Users can click the meeting room configuration option in the new schedule interface to select a meeting room.

[0185] If the user does not select the meeting room configuration option, the user can further determine whether to select the audio / video conferencing step, that is, whether to turn on the audio / video conferencing switch included in the new schedule interface.

[0186] If a user selects a meeting room configuration option, the computer device can display a list of candidate meeting rooms. The user can then select a target meeting room from this list, and the computer device can retrieve the target meeting room information. Additionally, the selected meeting room can be displayed on the calendar application interface.

[0187] However, since the candidate meeting room list may contain meeting rooms that do not require approval and meeting rooms that do require approval, the computer device, after acquiring the target meeting room, determines whether the target meeting room requires approval. If the target meeting room does not require approval, it proceeds to determine whether to select an audio / video conference; if the target meeting room requires approval, it submits the approval process, and then proceeds to determine whether to select an audio / video conference.

[0188] In one embodiment, regarding the aforementioned process of determining whether a voice / video conference has been selected: if the computer device detects a selection of a voice / video conference (i.e., the voice / video conference switch is on), after submitting data generated based on the calendar application interface, it can obtain records such as meeting creation records and schedule creation records, as well as messages such as meeting creation success message and schedule creation success message. If the computer device does not detect a selection of a voice / video conference (i.e., the voice / video conference switch is off), after submitting data generated based on the calendar application interface, it can obtain schedule creation records and schedule creation success messages. Furthermore, if the data generated based on the calendar application interface also includes meeting rooms, it can also obtain meeting room reservation records and meeting room reservation success messages.

[0189] In one embodiment, for a meeting room for which an approval process has been submitted, the user can also view the approval status of that meeting room in the enterprise communication application. If the approval for that meeting room fails, the user can view a notification message on the target application. After receiving the notification message, the user can reconfigure the meeting room for any existing schedules or meetings, or delete or cancel existing schedules or meetings, and then reopen the schedule application interface to recreate the schedule or meeting.

[0190] Please see Figure 8 This is a schematic diagram of a data processing device provided in an embodiment of this application. This data processing device can be applied to the aforementioned computer equipment. The device includes a display module 801 and a processing module 802. Specifically:

[0191] The display module is used to show the meeting creation components in the target application's calendar application interface;

[0192] The processing module is configured to respond to a first touch operation on the meeting creation component and display meeting configuration options in the calendar application interface via the display module;

[0193] The processing module is also configured to, in response to a second touch operation on the meeting configuration options, display the meeting configuration parameters obtained by the second touch operation in the calendar application interface via the display module;

[0194] The processing module is also used to generate a target meeting based on the meeting configuration parameters.

[0195] In one embodiment, the display module displays a meeting creation component in the calendar application interface of the target application, specifically: in response to a third touch operation on the meeting booking option in the target application, the meeting creation component is displayed in the calendar application interface of the target application; or, in response to a fourth touch operation on the meeting room booking option in the target application, the meeting creation component is displayed in the calendar application interface of the target application; or, in response to a fifth touch operation on the calendar creation option in the target application, the meeting creation component is displayed in the calendar application interface of the target application.

[0196] In one embodiment, the meeting configuration options include meeting type configuration options; the processing module, in response to a second touch operation on the meeting configuration options, displays the meeting configuration parameters obtained by the second touch operation in the calendar application interface, specifically: in response to a second touch operation on the meeting type configuration options, displays a meeting type list in the calendar application interface; in response to a first selection operation on a candidate meeting type in the meeting type list, determines the candidate meeting type obtained by the first selection operation as the meeting configuration parameter.

[0197] In one embodiment, the schedule application interface further includes a participant configuration option, and the meeting configuration parameters further include participants; the processing module is further configured to, in response to a sixth touch operation on the participant configuration option, display a list of candidate objects in the schedule application interface through the display module; and, in response to a second selection operation on a candidate object in the candidate object list, determine the candidate object obtained by the second selection operation as a participant of the target meeting.

[0198] In one embodiment, the meeting configuration parameters further include meeting time; the processing module is also configured to, in response to a seventh touch operation on the schedule data viewing option in the schedule application interface, display the schedule data of the participants of the target meeting in the schedule application interface through the display module; and obtain the meeting time selected based on the schedule data.

[0199] In one embodiment, the schedule application interface further includes a meeting room configuration option, and the meeting configuration parameters further include a target meeting room; the processing module is further configured to, in response to an eighth touch operation on the meeting room configuration option, display a list of candidate meeting rooms in the schedule application interface through a display module; and, in response to a third selection operation on a candidate meeting room in the candidate meeting room list, determine the candidate meeting room obtained by the third selection operation as the target meeting room for holding the target meeting.

[0200] In one embodiment, the target meeting room is a meeting room to be reviewed; the processing module generates the target meeting based on the meeting configuration parameters, specifically by: displaying the review options for the target meeting room in the schedule application interface through the display module; in response to a ninth touch operation on the review options for the target meeting room, displaying the reservation information of the target meeting room in the schedule application interface through the display module; and in response to a confirmation operation on the reservation information of the target meeting room, generating the target meeting based on the meeting configuration parameters.

[0201] In one embodiment, the processing module is further configured to synchronize the meeting configuration parameters related to the target meeting to the meeting management module through the schedule management module corresponding to the schedule application interface; and to display the meeting configuration parameters related to the target meeting in the meeting application interface of the target application through the meeting management module.

[0202] In one embodiment, the processing module is further configured to synchronize meeting configuration parameters related to the target meeting room to the meeting room management module through the schedule management module corresponding to the schedule application interface; and to display the meeting configuration parameters related to the target meeting room in the meeting room application interface of the target application through the meeting room management module.

[0203] visible, Figure 8 In this embodiment, the data processing device can not only create schedules based on the schedule application interface, but also create target meetings based on the schedule application interface. By using the schedule application interface for various transaction processing processes, business development efficiency can be improved and business maintenance costs can be reduced.

[0204] Please see Figure 9 This is a schematic diagram of the structure of a computer device provided in an embodiment of this application. Figure 9As shown, the aforementioned computer device 1000 may include: a processor 1001, a user interface 1003, and a memory 1005. Furthermore, the computer device 1000 may also include: at least one communication bus 1002 and a network interface 1004. The communication bus 1002 is used to enable communication between these components. The user interface 1003 may include a display screen and a keyboard, and may also include a standard wired interface and a wireless interface. The network interface 1004 may optionally include a standard wired interface and a wireless interface (such as a Wi-Fi interface). The memory 1005 may be high-speed RAM or non-volatile memory, such as at least one disk storage device. Optionally, the memory 1005 may also be at least one storage device located remotely from the aforementioned processor 1001. Figure 9 As shown, the memory 1005, which is a computer-readable storage medium, may include an operating system, a network communication module, a user interface module, and a device control application.

[0205] exist Figure 9 In the computer device 1000 shown, the user interface 1003 can sense touch operations and display interfaces, etc.; the user interface 1003 is mainly used to provide an input interface; and the processor 1001 can be used to call the device control application stored in the memory 1005 to achieve:

[0206] Display the meeting creation component in the target application's calendar application interface;

[0207] In response to a first touch operation on the meeting creation component, meeting configuration options are displayed in the calendar application interface;

[0208] In response to a second touch operation on the meeting configuration options, the meeting configuration parameters obtained from the second touch operation are displayed in the calendar application interface;

[0209] The target meeting is generated based on the meeting configuration parameters.

[0210] In one embodiment, when the meeting creation component is displayed in the calendar application interface of the target application, the processor 1001 can be used to call the device control application stored in the memory 1005 to specifically implement:

[0211] In response to a third touch operation on the meeting scheduling option in the target application, a meeting creation component is displayed in the calendar application interface of the target application; or,

[0212] In response to a fourth touch operation on the meeting room booking option in the target application, a meeting creation component is displayed in the calendar application interface of the target application; or,

[0213] In response to a fifth touch operation on the schedule creation option in the target application, a meeting creation component is displayed in the schedule application interface of the target application.

[0214] In one embodiment, the meeting configuration options include meeting type configuration options; when the meeting configuration parameters obtained by the second touch operation are displayed in the calendar application interface in response to a second touch operation on the meeting configuration options, the processor 1001 can be used to call the device control application stored in the memory 1005 to specifically implement:

[0215] In response to a second touch operation for the meeting type configuration options, a list of meeting types is displayed in the calendar application interface;

[0216] In response to a first selection operation for a candidate meeting type in the meeting type list, the candidate meeting type obtained from the first selection operation is determined as a meeting configuration parameter.

[0217] In one embodiment, the scheduling application interface further includes a participant configuration option, and the meeting configuration parameters further include the participants; the processor 1001 can be used to call the device control application stored in the memory 1005, and also implement:

[0218] In response to a sixth touch operation on the configuration options for the attendees, a list of candidate attendees is displayed in the scheduling application interface;

[0219] In response to a second selection operation on candidate objects in the candidate object list, the candidate objects obtained by the second selection operation are determined as participants in the target meeting.

[0220] In one embodiment, the meeting configuration parameters further include meeting time; the processor 1001 can be used to call the device control application stored in the memory 1005, and also implement:

[0221] In response to a seventh touch operation on the calendar data viewing option in the calendar application interface, the calendar data of the participants of the target meeting is displayed in the calendar application interface.

[0222] Obtain the meeting time selected based on the schedule data.

[0223] In one embodiment, the scheduling application interface further includes meeting room configuration options, and the meeting configuration parameters further include a target meeting room; the processor 1001 can be used to call the device control application stored in the memory 1005, and also implement:

[0224] In response to an eighth touch operation for the meeting room configuration options, a list of candidate meeting rooms is displayed in the scheduling application interface;

[0225] In response to a third selection operation on a candidate meeting room in the candidate meeting room list, the candidate meeting room obtained from the third selection operation is determined as the target meeting room for holding the target meeting.

[0226] In one embodiment, the target meeting room is the meeting room to be reviewed; when generating the target meeting based on the meeting configuration parameters, the processor 1001 can be used to call the device control application stored in the memory 1005 to specifically implement:

[0227] The approval options for the target meeting room are displayed in the calendar application interface;

[0228] In response to a ninth touch operation on the approval option for the target meeting room, the reservation information for the target meeting room is displayed in the calendar application interface;

[0229] In response to the confirmation operation of the reservation information for the target meeting room, a target meeting is generated based on the meeting configuration parameters.

[0230] In one embodiment, the processor 1001 can be used to invoke a device control application stored in the memory 1005, and also implement:

[0231] The meeting configuration parameters related to the target meeting are synchronized to the meeting management module through the schedule management module corresponding to the schedule application interface;

[0232] The meeting management module displays the meeting configuration parameters related to the target meeting in the meeting application interface of the target application.

[0233] In one embodiment, the processor 1001 can be used to invoke a device control application stored in the memory 1005, and also implement:

[0234] The meeting configuration parameters related to the target meeting room are synchronized to the meeting room management module through the schedule management module corresponding to the schedule application interface;

[0235] The meeting room management module displays meeting configuration parameters related to the target meeting room in the meeting room application interface of the target application.

[0236] visible, Figure 9 In this embodiment, the computer device can not only create schedules based on the schedule application interface, but also create target meetings based on the schedule application interface. Using the schedule application interface for various transaction processing processes can improve business development efficiency and reduce business maintenance costs.

[0237] It should be understood that the computer device 1000 described in the embodiments of this application can execute the foregoing text. Figure 2 or Figure 4 The data processing method described in the embodiments can also be implemented as described above. Figure 8 The description of the data processing apparatus in the corresponding embodiments will not be repeated here. Furthermore, the beneficial effects of using the same method will also not be repeated.

[0238] This application also provides a computer-readable storage medium storing a computer program executed by the aforementioned data processing apparatus. The computer program includes program instructions, and when the processor executes these program instructions, it can execute the aforementioned... Figure 2 Implementation examples or Figure 4 The data processing method described in the embodiments is therefore not repeated here. Similarly, the beneficial effects of using the same method will also not be repeated. For technical details not disclosed in the embodiments of the computer-readable storage medium involved in this application, please refer to the description of the method embodiments of this application.

[0239] As an example, the above program instructions can be deployed and executed on a computer device, or deployed and executed on at least two computer devices in one location, or executed on at least two computer devices distributed in at least two locations and interconnected by a communication network. At least two computer devices distributed in at least two locations and interconnected by a communication network can form a blockchain network.

[0240] The aforementioned computer-readable storage medium can be a data processing apparatus provided in any of the foregoing embodiments or a central storage unit of the aforementioned computer device, such as a hard disk or central storage of the computer device. The computer-readable storage medium can also be an external storage device of the computer device, such as a plug-in hard disk, smart media card (SMC), secure digital (SD) card, flash card, etc., provided on the computer device. Furthermore, the computer-readable storage medium may include both the central storage unit and external storage devices of the computer device. The computer-readable storage medium is used to store the computer program and other programs and data required by the computer device. The computer-readable storage medium can also be used to temporarily store data that has been output or will be output.

[0241] The terms "first," "second," etc., in the specification, claims, and drawings of this application are used to distinguish content in different media, rather than to describe a specific order. Furthermore, the term "comprising," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, apparatus, product, or device that includes a series of steps or units is not limited to the listed steps or modules, but may optionally include steps or modules not listed, or may optionally include other step units inherent to these processes, methods, apparatuses, products, or devices.

[0242] This application also provides a computer program product, including a computer program / instructions, which, when executed by a processor, implement the foregoing description. Figure 2 or Figure 4 The data processing method described in the embodiments is therefore not repeated here. Similarly, the beneficial effects of using the same method will not be repeated here either. For technical details not disclosed in the embodiments of the computer program product involved in this application, please refer to the description of the method embodiments of this application.

[0243] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this application.

[0244] The methods and related apparatus provided in this application are described with reference to the method flowcharts and / or structural diagrams provided in this application. Specifically, each block of the method flowchart and / or structural diagram, as well as combinations of blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable network-connected device to create a machine, such that the instructions, which execute via the processor of the computer or other programmable network-connected device, generate instructions for implementing the process. Figure 1 A schematic diagram of one or more processes and / or structures. Figure 1 The computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable network-connected device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 A schematic diagram of one or more processes and / or structures. Figure 1 The functions specified in one or more boxes. These computer program instructions may also be loaded onto a computer or other programmable network-connected device to cause a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable device for implementing the process. Figure 1 A process or multiple processes and / or structures illustrate the steps of the functions specified in one or more boxes.

[0245] The above-disclosed embodiments are merely preferred embodiments of this application and should not be construed as limiting the scope of this application. Therefore, any equivalent variations made in accordance with the claims of this application shall still fall within the scope of this application.

Claims

1. A data processing method, characterized in that, include: A meeting creation component is displayed in the calendar application interface of the target application. Schedules or meetings are created through this calendar application interface, which includes multiple interface components such as time configuration options, meeting creation components, meeting room configuration options, and object configuration options. These multiple interface components are shared during the schedule creation and meeting creation processes within the target application. Specifically, when the meeting creation component is not enabled, the time configuration options, meeting room configuration options, and object configuration options are used to configure the schedule time, the required meeting room, and the participants. When the meeting creation component is enabled, the same set of time configuration options, meeting room configuration options, and object configuration options are used to configure the meeting time, the required meeting room, and the participants. In response to a first touch operation on the meeting creation component, the meeting creation component is opened, and meeting configuration options are displayed in the calendar application interface. The meeting configuration options are used to configure the meeting's attribute information, including but not limited to meeting type, meeting description, or meeting importance indicator. In response to a second touch operation on the meeting configuration options, the meeting configuration parameters obtained from the second touch operation are displayed in the calendar application interface; A target meeting is generated based on the meeting configuration parameters; and the meeting configuration parameters related to the target meeting are synchronized to the meeting management module through the schedule management module corresponding to the schedule application interface, and the meeting configuration parameters related to the target meeting are displayed in the meeting application interface of the target application through the meeting management module.

2. The method according to claim 1, characterized in that, The step of displaying the meeting creation component in the target application's calendar application interface includes: In response to a third touch operation on the meeting scheduling option in the target application, a meeting creation component is displayed in the calendar application interface of the target application; or, In response to a fourth touch operation on the meeting room booking option in the target application, a meeting creation component is displayed in the calendar application interface of the target application; or, In response to a fifth touch operation on the schedule creation option in the target application, a meeting creation component is displayed in the schedule application interface of the target application.

3. The method according to claim 1, characterized in that, The meeting configuration options include meeting type configuration options; The response to a second touch operation on the meeting configuration options, displaying the meeting configuration parameters obtained from the second touch operation in the calendar application interface, includes: In response to a second touch operation for the meeting type configuration options, a list of meeting types is displayed in the calendar application interface; In response to a first selection operation for a candidate meeting type in the meeting type list, the candidate meeting type obtained from the first selection operation is determined as a meeting configuration parameter.

4. The method according to claim 3, characterized in that, The meeting configuration parameters also include the participants; The method further includes: In response to a sixth touch operation on the object configuration options, a list of candidate objects is displayed in the calendar application interface; In response to a second selection operation on candidate objects in the candidate object list, the candidate objects obtained by the second selection operation are determined as participants in the target meeting.

5. The method according to claim 4, characterized in that, The meeting configuration parameters also include meeting time; the method further includes: In response to a seventh touch operation on the calendar data viewing option in the calendar application interface, the calendar data of the participants of the target meeting is displayed in the calendar application interface. Obtain the meeting time selected based on the schedule data.

6. The method according to claim 3, characterized in that, The meeting configuration parameters also include the target meeting room; The method further includes: In response to an eighth touch operation for the meeting room configuration options, a list of candidate meeting rooms is displayed in the scheduling application interface; In response to a third selection operation on a candidate meeting room in the candidate meeting room list, the candidate meeting room obtained from the third selection operation is determined as the target meeting room for holding the target meeting.

7. The method according to claim 6, characterized in that, The target meeting room is the meeting room to be reviewed; the generation of the target meeting based on the meeting configuration parameters includes: The approval options for the target meeting room are displayed in the calendar application interface; In response to a ninth touch operation on the approval option for the target meeting room, the reservation information for the target meeting room is displayed in the calendar application interface; In response to the confirmation operation of the reservation information for the target meeting room, a target meeting is generated based on the meeting configuration parameters.

8. The method according to claim 1, characterized in that, The method further includes: The meeting configuration parameters related to the target meeting room are synchronized to the meeting room management module through the schedule management module corresponding to the schedule application interface; The meeting room management module displays meeting configuration parameters related to the target meeting room in the meeting room application interface of the target application.

9. A data processing apparatus, characterized in that, include: The display module is used to display the meeting creation component in the calendar application interface of the target application. The calendar application interface allows for the creation of schedules or meetings. The calendar application interface includes multiple interface components, such as time configuration options, meeting creation components, meeting room configuration options, and object configuration options. These multiple interface components are shared during the schedule creation and meeting creation processes within the target application. Specifically, when the meeting creation component is not enabled, the time configuration options, meeting room configuration options, and object configuration options are used to configure the schedule time, the required meeting room, and the participants. When the meeting creation component is enabled, the same set of time configuration options, meeting room configuration options, and object configuration options are used to configure the meeting time, the required meeting room, and the participants. The processing module is used to respond to a first touch operation on the meeting creation component, open the meeting creation component, and display meeting configuration options in the schedule application interface through the display module. The meeting configuration options are used to configure the meeting's attribute information, including but not limited to meeting type, meeting description, or meeting importance indicator. The processing module is further configured to respond to a second touch operation on the meeting configuration option and display the meeting configuration parameters obtained by the second touch operation in the calendar application interface through the display module; The processing module is further configured to generate a target meeting based on the meeting configuration parameters; and to synchronize the meeting configuration parameters related to the target meeting to the meeting management module through the schedule management module corresponding to the schedule application interface, and to display the meeting configuration parameters related to the target meeting in the meeting application interface of the target application through the meeting management module.

10. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 8.

11. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 8.

12. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 8.

Images