Conference joining method and device, equipment and storage medium

Abstract

The embodiment of the invention provides a conference joining method and device, equipment and a storage medium, and the method comprises the steps: presetting a conference interaction file corresponding to a conference configuration webpage, enabling a conference client to call the corresponding conference interaction file after the conference configuration webpage is loaded, and carrying out the joining of a conference according to an interaction rule in the conference interaction file, according to the embodiment of the invention, the interaction operation is executed on the interaction element in the conference configuration webpage, so that the operation on the interaction element is automatically executed, and the target conference can be automatically joined after the operation is completed. Namely, in the process that the user joins the target conference by using the conference client, the conference client can automatically complete the operation required for joining the target conference, and manual operation is not needed in the process, so that the operation of the user is simplified, the use experience of the user is greatly improved, and the user experience is improved. The technical problem that in the related technology, operation is complex and tedious in the process that the user joins the remote conference is solved.

Description

Technical Field

[0001] This application relates to the field of computers, and more particularly to a method, apparatus, device, and storage medium for joining a meeting. Background Technology

[0002] In related technologies, users can conduct remote meetings by logging into a conferencing platform to achieve online collaboration and communication. However, currently, after logging into the conferencing platform, users need to go through a series of operations before joining a remote meeting. For example, after logging into the conferencing platform, users need to click on the meeting chain or enter the meeting number, and then fill in the device name and / or set related functions (such as setting the camera status and / or setting the microphone status) before joining a remote meeting. This makes the process of joining a meeting relatively complicated and cumbersome, resulting in a poor user experience. Summary of the Invention

[0003] This application provides a method, apparatus, device, and storage medium for joining a meeting, which solves the technical problem that the process of a user joining a remote meeting is complex and cumbersome in related technologies.

[0004] In a first aspect, embodiments of this application provide a meeting joining method, which is applicable to a meeting client and includes:

[0005] The corresponding meeting configuration webpage is loaded based on the first webpage address obtained at present. The meeting configuration webpage is a webpage that requires user interaction during the process of joining the target meeting. The target meeting is a meeting created using third-party meeting software. The meeting configuration webpage contains at least one first interactive element.

[0006] Once it is determined that the meeting configuration webpage has been loaded, the meeting interaction file corresponding to the meeting configuration webpage is executed. The meeting interaction file records the first interaction rules when interacting with the first interaction element.

[0007] Receive an interactive operation for the first interactive element, wherein the interactive operation is an operation performed on the first interactive element according to the first interactive rule when executing the meeting interactive file;

[0008] The operation results of the interactive operation are displayed on the meeting configuration webpage, and when it is determined that a webpage needs to be redirected, the address of the second webpage is obtained;

[0009] When the second webpage address corresponds to the target meeting webpage, the corresponding target meeting webpage is loaded according to the second webpage address. The target meeting webpage is the webpage after joining the target meeting.

[0010] As described above, by pre-setting a meeting interaction file corresponding to the meeting configuration webpage, the meeting client, after loading the meeting configuration webpage, can call the corresponding meeting interaction file. Based on the interaction rules in the meeting interaction file, it can perform interactive operations on the interactive elements in the meeting configuration webpage, thereby automatically executing the operations on the interactive elements. After the operations are completed, it can automatically join the target meeting. In other words, during the process of a user joining a target meeting using the meeting client, the meeting client can automatically complete the operations required to join the target meeting without any manual intervention. This simplifies the user experience, greatly improves user experience, and solves the technical problem of complex and cumbersome operations in the process of joining remote meetings in related technologies.

[0011] In one embodiment of this application, executing the meeting interaction file corresponding to the meeting configuration webpage after determining that the meeting configuration webpage has finished loading includes:

[0012] Once it is determined that the meeting configuration webpage has been loaded, the corresponding meeting interaction file is searched in the meeting configuration plugin according to the first webpage address. The meeting configuration plugin includes the first webpage address of the meeting configuration webpage required to join the target meeting process and the meeting interaction file corresponding to the first webpage address. The meeting configuration webpage is at least one.

[0013] Execute the found meeting interaction file.

[0014] As mentioned above, when multiple meeting configuration webpages need to be loaded during the process of joining a target meeting, the meeting client can call and execute the meeting interaction file corresponding to each meeting configuration webpage according to the meeting configuration plugin during the loading of each meeting configuration webpage, thereby realizing the automated configuration of each meeting configuration webpage, which greatly improves the configuration efficiency and the user experience.

[0015] In one embodiment of this application, the target meeting webpage contains at least one meeting information element, and the meeting configuration plugin further includes a second webpage address of the target meeting webpage and a meeting information collection file corresponding to the second webpage address. The meeting information collection file records the identification rules for the meeting information element.

[0016] After loading the corresponding target meeting webpage according to the second webpage address, the process further includes:

[0017] Locate the corresponding meeting information collection file in the meeting configuration plugin based on the second webpage address;

[0018] Execute the retrieved meeting information collection file;

[0019] Acquire meeting information, which is the meeting information obtained when the meeting information collection file is executed and meeting information elements are identified according to the identification rules;

[0020] Save the meeting information.

[0021] As mentioned above, by setting a meeting information collection file in the meeting configuration plugin, when the meeting client joins the target meeting, it can also identify meeting information elements in the target meeting webpage by executing the meeting information collection file, thereby collecting and saving the meeting information of the target meeting. This enables automatic collection of meeting information, eliminating the need for manual collection when users need meeting information, further reducing user operation steps and improving the user experience.

[0022] In one embodiment of this application, the meeting client supports multiple third-party meeting software, and each of the third-party meeting software has a corresponding meeting configuration plugin.

[0023] As described above, by setting up meeting configuration plugins corresponding to different third-party meeting software, the meeting client can automatically configure the target meeting when joining the target meeting created by different third-party meeting software, thus expanding the applicability of the meeting configuration method provided in this application.

[0024] In one embodiment of this application, the meeting joining method further includes:

[0025] When the version update conditions are met, the latest first version number of the meeting configuration plugin is obtained from the server. The version update conditions are that the meeting client completes startup or receives a meeting selection instruction from the user. The meeting selection instruction is an instruction to join a meeting created by third-party meeting software.

[0026] Determine whether the second version number of the currently used meeting configuration plugin on the local machine is consistent with the first version number;

[0027] If the second version number is inconsistent with the first version number, then download the meeting configuration plugin corresponding to the first version number from the server and replace the local meeting configuration plugin with the downloaded meeting configuration plugin.

[0028] As described above, when the meeting configuration plugin version update conditions are met, the meeting client obtains the latest first version number of the meeting configuration plugin from the server and determines whether the version number of the local meeting configuration plugin is the first version number. If it is not the first version number, the client downloads the meeting configuration plugin corresponding to the first version number from the server, completes the update of the local meeting configuration plugin, and thus ensures that the latest version of the meeting configuration plugin can be used.

[0029] In one embodiment of this application, the meeting interaction file also records a timed search rule corresponding to the first interactive element. The timed search rule is used to specify the period of searching for the first interactive element when the meeting interaction file is executed, so that the action of searching for the first interactive element can be performed within each period of time until the first interactive element is found.

[0030] As described above, by recording the timed search rules corresponding to the first interactive element in the meeting interaction file, the action of searching for the first interactive element in the meeting configuration webpage can be performed periodically after the meeting interaction file is executed. This avoids missing the first interactive element when it loads slowly, thus preventing the situation where no interactive operation is performed on the first interactive element.

[0031] In one embodiment of this application, the interactive operation includes at least one of the following: switch selection operation, information writing operation, button click operation, option selection operation, and pop-up window closing operation.

[0032] As mentioned above, the current interactive operation styles are quite diverse, basically covering all scenarios that require user operation during the membership process.

[0033] Secondly, embodiments of this application provide a meeting joining device, which is applicable to a meeting client and includes:

[0034] The configuration webpage loading module is used to load the corresponding meeting configuration webpage according to the currently obtained first webpage address. The meeting configuration webpage is a webpage that requires user interaction during the process of joining the target meeting. The target meeting is a meeting created using third-party meeting software. The meeting configuration webpage contains at least one first interactive element.

[0035] An interactive file execution module is used to execute a meeting interactive file corresponding to the meeting configuration webpage when it is determined that the meeting configuration webpage has been loaded. The meeting interactive file records a first interaction rule when interacting with the first interactive element.

[0036] An interactive operation receiving module is used to receive interactive operations for the first interactive element, wherein the interactive operation is an operation performed on the first interactive element according to the first interactive rules when the meeting interactive file is executed;

[0037] The operation result display module is used to display the operation result of the interactive operation on the meeting configuration webpage, and to obtain the second webpage address when it is determined that a webpage needs to be redirected.

[0038] The meeting joining module is used to load the corresponding target meeting webpage according to the second webpage address when the second webpage address corresponds to the target meeting webpage. The target meeting webpage is the webpage after joining the target meeting.

[0039] Thirdly, embodiments of this application provide a conference joining device, which includes a processor and a memory;

[0040] The memory is used to store computer programs and to transfer the computer programs to the processor;

[0041] The processor is configured to execute a meeting joining method as described in the first aspect, according to instructions in the computer program.

[0042] Fourthly, embodiments of this application provide a storage medium for storing computer-executable instructions, which, when executed by a computer processor, are used to perform a meeting joining method as described in the first aspect.

[0043] The beneficial effects of the aforementioned meeting joining devices, equipment, and storage media can be referenced in light of the beneficial effects of the meeting joining method. Attached Figure Description

[0044] Figure 1 This is a schematic diagram of the first webpage interface provided in the related technology.

[0045] Figure 2 This is a schematic diagram of a second webpage interface provided in related technologies.

[0046] Figure 3 This is a schematic diagram of a third webpage interface provided in related technologies.

[0047] Figure 4 A flowchart illustrating a meeting joining method provided in an embodiment of this application.

[0048] Figure 5 This is a schematic diagram of a meeting configuration webpage provided in an embodiment of this application.

[0049] Figure 6 A flowchart illustrating a meeting joining method provided in an embodiment of this application.

[0050] Figure 7 This is a flowchart illustrating another meeting joining method provided in an embodiment of this application.

[0051] Figure 8 This is a schematic diagram of the interface of a target meeting webpage provided in an embodiment of this application.

[0052] Figure 9 This is a flowchart illustrating a meeting joining method provided in this application.

[0053] Figure 10 This is a schematic diagram illustrating an update of a JS plugin version, as provided in an embodiment of this application.

[0054] Figure 11 This is a schematic diagram of a meeting joining device provided in an embodiment of this application.

[0055] Figure 12 This is a schematic diagram of a conference joining device provided in an embodiment of this application. Detailed Implementation

[0056] The following description and accompanying drawings fully illustrate specific embodiments of this application to enable those skilled in the art to practice them. The embodiments represent only possible variations. Individual components and functions are optional unless explicitly required, and the order of operation may vary. Parts and features of some embodiments may be included in or replace parts and features of other embodiments. The scope of embodiments of this application includes the entire scope of the claims and all available equivalents of the claims. In this document, each embodiment may be referred to individually or collectively by the term "invention," which is merely for convenience and is not intended to automatically limit the scope of the application to any single invention or inventive concept if more than one invention is disclosed. Relational terms such as "first" and "second" are used herein only to distinguish one entity or operation from another, without requiring or implying any actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed. The various embodiments in this document are described in a progressive manner, with each embodiment focusing on its differences from other embodiments. Similar or identical parts between embodiments can be referred to interchangeably. For the structures, products, etc., disclosed in the embodiments, since they correspond to the disclosed parts, the descriptions are relatively simple; relevant details can be found in the method section.

[0057] Remote conferencing refers to holding meetings across different regions using modern communication methods. With the development of network technology, remote conferencing is widely used in office, teaching, and other scenarios.

[0058] In the process of implementing a remote conference, a user first needs to create a remote conference using their own electronic device. The electronic device then communicates with the server providing the remote conference service. The server creates the remote conference and sends relevant information (such as the conference ID) back to the electronic device, allowing it to display the newly created conference. Other users who wish to join the conference can obtain the conference ID and / or conference link and join using their own electronic devices based on this information. Generally, users participating in the same remote conference consider themselves to have entered the same remote conference room, which is a network room created by the server. After joining the remote conference room, an electronic device can access all the functions of the remote conference.

[0059] Currently, with the development of remote conferencing technology, various conferencing platforms have emerged to enable remote meetings. A conferencing platform can also be understood as the software that enables remote meetings; it can also be referred to as conferencing software. For example, Teams, Google Meet, and WebEx are all common conferencing platforms. It's understandable that when users join a remote meeting through electronic devices, they primarily do so through the conferencing platform. At this time, users can join the remote meeting through a locally installed conferencing platform application (also referred to as application software) on their electronic devices, or they can access the conferencing platform through a browser (i.e., join the remote meeting through the web version of the conferencing platform).

[0060] When users join a remote meeting through a browser, they also need to manually fill in the device name and / or set related functions (such as setting the camera status and / or setting the microphone status).

[0061] For example, taking the Teams meeting platform as an example, Figure 1 This is a schematic diagram of a first webpage interface provided in the related technology. When a user obtains the meeting link (which can also be understood as a network address) for a remote meeting and clicks the meeting link, the corresponding webpage is loaded in the browser. The current interface of this webpage is as follows: Figure 1 As shown, at this point, the user needs to select option 11, "Continue in browser," to continue joining the remote meeting in the browser. After the user selects the "Continue in browser" option, the browser redirects to another webpage. Figure 2 This is a schematic diagram of a second webpage interface provided in the related technology. After the user selects the "Continue in browser" option, the browser redirects to display another webpage, the interface of which is as follows: Figure 2As shown, the webpage displays an input box 12 for entering the user's name (i.e., device name) and a "Join Meeting" button 13. Additionally, the webpage displays settings options 14 and 15 for setting the microphone and camera status. Users can then enter their device name in input box 12 to participate in the remote meeting. Afterward, the user clicks the "Join Meeting" button 13 to join the remote meeting. Furthermore, clicking the "Join Meeting" button 13 allows the user to configure the microphone and camera status using settings options 14 and 15 respectively. After the user clicks the "Join Meeting" button 13, the meeting platform can join the remote meeting based on the user's actions. Subsequently, a webpage displaying the ongoing remote meeting (such as displaying user avatars or videos) is shown in the browser. Based on the foregoing description, when a user joins a remote meeting using the Teams platform, after clicking the meeting connection, they still need to perform the operations of selecting a browser, entering the device name, setting the microphone status, setting the camera status, and clicking the "Join Meeting" button, making the user's operation rather cumbersome.

[0062] Alternatively, when a user needs to join the Google Meetings platform, after loading the Google Meetings webpage in their browser, the webpage interface looks like this: Figure 3 As shown, Figure 3 This is a schematic diagram of a third webpage interface provided in related technologies. Figure 3 The webpage displayed includes an input box 21 for entering the user's name (i.e., device name) and a "Join Meeting" button 22 (i.e., the "Request to Join" button); microphone and camera on / off switches 23 and 25 for configuring the microphone and camera respectively; microphone and camera device source options 24 and 26 for configuring the microphone and camera device source; and speaker device option 27 for configuring the speaker device source. After entering the device name in input box 21, the user can click the "Join Meeting" button 22 to join the remote meeting. Additionally, before or after clicking "Join Meeting," the user needs to configure the microphone status and device source using microphone on / off button 23 and microphone device option 24, the camera status and device source using camera on / off button 25 and camera device option 26, and the speaker device source using speaker device option 27. As can be seen, when users join a remote meeting on the Google platform, after clicking the meeting connection button, they still need to perform the following operations: enter the device name, set the microphone status and device source, set the camera status and device source, set the speaker device source, and click the join meeting button. The operation is equally complicated and cumbersome.

[0063] As can be seen from the foregoing, in the relevant technologies, when a user joins a remote meeting through a conferencing platform in a browser, after entering the meeting number or meeting link, the user still needs to perform operations such as entering the device name, setting the microphone status, setting the camera status, and clicking the join meeting button. This makes the process of joining a remote meeting quite cumbersome for the user.

[0064] Based on this, this application provides a meeting joining method. This meeting joining method can use a meeting client to join a remote meeting on a meeting platform. The meeting client can automatically perform the operations required by the user in the webpage during the process of joining the remote meeting based on pre-set interaction rules, so as to achieve automatic joining of the remote meeting. This eliminates the need for the user to perform operations such as entering the device name, setting the microphone status, setting the camera status, and clicking the join meeting button, thus avoiding tedious operations for the user.

[0065] The meeting joining method provided in this application embodiment can be implemented by a meeting joining device, which can be implemented by software and / or hardware. The meeting joining device can consist of two or more physical entities, or it can consist of a single physical entity. Currently, the meeting joining device can be a network-connected electronic device such as a mobile phone, tablet computer, interactive whiteboard (e.g., IFP), laptop computer, or desktop computer.

[0066] In one embodiment, the conference joining device includes a processor, and the number of processors may be one or more. The processor may include processing units such as application processors (APs), graphics processing units (GPUs), and central processing units (CPUs). The processor performs various functional applications and data processing of the conference joining device by running computer-executable programs (such as software programs, instructions, and modules) stored in memory.

[0067] The conference joining device also includes memory. The memory can be used to store computer-executable programs, including instructions, for the conference joining device. The memory may include a program storage area and a data storage area. The program storage area may store the operating system and at least one application program required for a given function. The data storage area may store data created based on the use of the electronic device. The memory may include high-speed random access memory and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other non-volatile solid-state storage device. In some instances, the memory may further include memory remotely located relative to the processor, which can be connected to the electronic device via a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.

[0068] Meeting equipment may also include displays, and there may be one or more displays. These displays can be liquid crystal displays (LCDs), LED displays, organic light-emitting diode (OLED) displays, or flexible light-emitting diode (FLED) displays, etc. The displays can be based on processor instructions, such as displaying web pages related to the remote meeting.

[0069] In some cases, the display screen may also have touch functionality, i.e., a touch display screen, which includes a display panel and a touch panel. The display panel is used to provide visual output. The touch panel can be a component that supports infrared touch, electromagnetic touch, capacitive touch, or resistive touch, etc. The touch panel can transmit the touch data corresponding to the detected touch operation to the processor, and the display panel can provide visual output related to the touch operation.

[0070] The conference equipment may also include a communication module, which may include a wired communication module and / or a wireless communication module. The wired communication module includes at least one communication interface, such as a Universal Serial Bus (USB) interface, a network interface, etc. The wireless communication module includes one or more of the following: Bluetooth module, infrared module, Wi-Fi module, and Near Field Communication (NFC) module. Currently, the processor can communicate with external devices through the communication module, such as communicating with servers, communicating with other devices, and communicating with external devices adapted to electronic devices. These external devices may be one or more of the following: a writing pen (also known as a smart pen, stylus, etc.), a keyboard, and a mouse.

[0071] Based on the above structure, the conference joining device supports at least one type of operating system, which can be Android, Windows, Linux, iOS, or macOS, etc. In one embodiment, the conference joining device supports at least Windows as an example. The conference joining device has at least one application (also referred to as application software, software program, APP, etc.) installed on the Windows system. This application can be an application that comes with the operating system or an application downloaded from a third-party device or server. In one embodiment, the application installed on the conference joining device includes at least a conference client.

[0072] In this context, a meeting client refers to an application that allows users to join and participate in remote meetings created by third-party meeting software via a web page. The meeting client can be a native application. Optionally, the meeting client can be an application built on the Flutter framework.

[0073] Third-party conferencing software refers to conferencing platforms developed by other developers that can be accessed by the conferencing client. Third-party conferencing software is a software tool used to support remote conferencing, online collaboration, and team communication, typically offering multiple functions including video conferencing, audio calling, screen sharing, online document collaboration, and real-time messaging. For example, Teams, Google Meet, and WebEx can all be considered third-party conferencing software. In one embodiment, the conferencing client supports multiple third-party conferencing software programs; for example, the conferencing client supports at least Teams, Google Meet, and WebEx. In one embodiment, after a user selects a third-party conferencing software in the conferencing client, the conferencing client can use WebView (currently mainly WebView2) technology to open the relevant webpage of the third-party conferencing software, thus enabling the user to join and participate in a remote meeting created by the third-party conferencing software. Currently, the relevant webpage includes at least a meeting configuration webpage and a target meeting webpage. The meeting configuration webpage refers to the page that requires user interaction when joining a remote meeting, such as in the Teams conferencing platform. Figure 1 and Figure 2 The web pages shown can all be considered meeting configuration pages, such as those on the Google Meet platform. Figure 3 The webpage shown can be considered the meeting configuration webpage. The target meeting webpage refers to the webpage after joining the remote meeting; it can also be understood as the meeting interface, which at least displays the avatars, names, or video data of other participants. In some scenarios, participants can also share documents and share their desktops on the target meeting webpage.

[0074] In one embodiment, when the meeting client displays the meeting configuration webpage, it can simulate the user's required interactive operations based on pre-set interaction rules. This means that the user can automatically join the meeting without manually performing any operations. In this case, the meeting joining method provided in this embodiment can also be considered as being executed by the meeting client; that is, the meeting client can also function as the meeting joining device itself.

[0075] Figure 4 A flowchart illustrating a meeting joining method provided in this application embodiment. The meeting joining method provided in this application embodiment is applicable to meeting clients. (Refer to...) Figure 4 The method includes the following steps:

[0076] Step 201: Load the corresponding meeting configuration webpage based on the currently obtained first webpage address. The meeting configuration webpage is a webpage that requires user interaction during the process of joining the target meeting. The target meeting is a meeting created using third-party meeting software. The meeting configuration webpage contains at least one first interactive element.

[0077] In this embodiment, a meeting created by third-party conferencing software (i.e., a remote meeting) is designated as the target meeting. Users join the target meeting using a conferencing client.

[0078] When a user needs to join a target meeting, they can perform a meeting join operation on the meeting client. The meeting client responds to the meeting join operation by executing the steps to join the target meeting. Optionally, the user can enter or click the web address (which can also be referred to as a URL, and can be considered as the meeting link of the target meeting) required to join the meeting in the meeting client. Alternatively, the user can enter the meeting ID corresponding to the target meeting in the meeting client. The meeting client can then obtain the web address required to access from the target meeting's server based on the meeting ID. In this case, the user's entry of the meeting ID can be considered as a meeting join operation. The meeting ID can also be referred to as a meeting code or invitation code. The meeting ID can be composed of numbers and / or letters, or it can be a QR code. Each remote meeting can correspond to a unique meeting ID. Optionally, when third-party conferencing software needs to create a remote meeting, it can send a request to its own server (the server of the target meeting). The server then creates the remote meeting room and sends the corresponding web address or meeting ID back to the third-party conferencing software. The user of the third-party conferencing software then notifies other participants (including users using the conferencing client) of the web address or meeting ID. Users using the conferencing client can then apply to join the target meeting based on the web address or meeting ID. It is understood that the server used by the third-party conferencing software and the server used by the conferencing client can be different servers.

[0079] In one embodiment, the webpage address that a user needs to access during the process of joining the target meeting is designated as the first webpage address. After obtaining the first webpage address, the meeting client loads and opens the corresponding webpage based on the first webpage address. In one embodiment, the webpage corresponding to the first webpage address is a meeting configuration webpage. Users can configure and join the target meeting by interacting with the meeting configuration webpage. The configuration of the target meeting includes, but is not limited to, starting or stopping the local camera, starting or stopping the microphone, and setting the names of participating devices (which can also be referred to as the meeting name or user). Each meeting configuration webpage has a corresponding webpage address. Optionally, the meeting client embeds a WebView2 control. Embedding the WebView2 control in the meeting client allows the meeting client to access various methods and properties provided by the WebView2 class or interface, enabling the application to load and display web pages and interact with the pages. That is, the meeting client uses WebView2 to open the meeting configuration webpage corresponding to the first webpage address.

[0080] In one embodiment, the meeting configuration webpage includes at least one first interactive element. This interactive element is an element displayed on the page that requires user interaction, allowing the user to perform corresponding functions by interacting with it. When displayed on the meeting configuration webpage, the interactive element can be an element in the document object model (DOM) of the meeting configuration webpage, an element in the document of the meeting configuration webpage, or an element directly displayed on the meeting configuration webpage (which is an HTML webpage). The interactive element can be a page element such as an input box, option, pop-up window, or button icon. Currently, the interactive element included in the meeting configuration webpage is referred to as the first interactive element. For example, Figure 5 This is a schematic diagram of a meeting configuration webpage provided in an embodiment of this application. The first interactive elements in the meeting configuration webpage include an input box 31 for inputting the participant's name, a microphone switch button 32 and a camera switch button 33 for configuring the microphone and camera to be turned on and off respectively, a microphone device option 34 and a camera device option 35 for configuring the microphone device source and the camera device source, and a meeting join button 36 (i.e., the "Request to Join" button) for joining the meeting.

[0081] It should be further explained that after the meeting initiator creates the target meeting on third-party conferencing software, they can generate a web address corresponding to the target meeting and share it with other users. After obtaining the web address, other users can input it as the first web address into the meeting client, causing the meeting client to load the meeting configuration webpage corresponding to the first web address. Optionally, the first web address includes the software identifier of the third-party conferencing software that created the target meeting. The meeting client can identify the third-party conferencing software by analyzing the software identifier in the first web address and open the meeting configuration webpage corresponding to that third-party conferencing software. Alternatively, after the meeting client starts, it can display the identifiers of all currently compatible third-party conferencing software (displayed via icons or other methods). Then, the user selects the identifier of the third-party conferencing software corresponding to the target meeting. The meeting client then displays an interface requiring the user to enter the meeting number or the first web address. After the user enters (through copying) the meeting number or the first web address, the meeting client loads the corresponding meeting configuration webpage.

[0082] It is understood that different third-party conferencing software in the embodiments may correspond to different conferencing configuration web pages.

[0083] Step 202: Once the meeting configuration webpage has been loaded, execute the meeting interaction file corresponding to the meeting configuration webpage. The meeting interaction file records the first interaction rules when interacting with the first interaction element.

[0084] For example, when the meeting client loads the meeting configuration webpage, it confirms the webpage loading is complete upon receiving the `onPageFinished` callback. Then, the meeting client needs to locate the meeting interaction file corresponding to the meeting configuration webpage. This meeting interaction file is a file recording the first interaction rules when interacting with the first interactive element. The interaction rules include the rules for interacting with the interactive element. For example, if the interactive element is an input box, the interaction rules include the element identifier (used to distinguish different interactive elements), the operation performed during the interaction (a message writing operation), and the specific content to be written. Similarly, if the interactive element is a button, the interaction rules include the element identifier of the interactive element and the operation performed during the interaction (a button click operation). Furthermore, if the interactive element is a microphone switch button, the interaction rules include the element identifier of the interactive element, the operation performed during the interaction (a switch selection operation), and the specific selection of "on" or "off". In this embodiment, the interaction rule corresponding to the first interactive element is recorded as the first interaction rule. Currently, each first interactive element has a corresponding first interaction rule. The specific content of the first interaction rule can be set according to actual needs; this embodiment does not impose specific limitations. The first interaction rule can be set by the user during the process of writing the meeting interaction document.

[0085] In one embodiment, the meeting interaction files are pre-stored in a local or cloud-based database (i.e., the server used by the meeting client). Each meeting configuration webpage has a corresponding meeting interaction file. Optionally, the corresponding meeting interaction file can be found through the webpage identifier of the meeting configuration webpage. The webpage identifier is used to distinguish different meeting configuration webpages. Currently, the webpage address corresponding to the meeting configuration webpage can be used as the webpage identifier. That is, after the meeting client loads the meeting configuration webpage, it can find the corresponding meeting interaction file based on the first webpage address.

[0086] Optionally, the meeting interaction file is a JavaScript (hereinafter referred to as JS) file. The JS text consists of JS code, that is, the first interaction rule can be recorded in the form of JS code.

[0087] After the meeting client locates the meeting interaction file, it executes the meeting interaction file, that is, it runs the JS code of the meeting interaction file.

[0088] When executing meeting interaction files, corresponding operations can be performed on the first interaction element based on the first interaction rule. Specifically, when performing operations based on the first interaction rule, the corresponding first interaction element can be found in advance, and then the corresponding interaction operation can be performed on the first interaction element.

[0089] In one embodiment, if the first interactive element requires a long loading time (e.g., the first interactive element occupies a large amount of space, is a high-definition element, or has a slow network), it may be impossible to find the first interactive element because it has not yet finished loading. For example, after the meeting configuration webpage has finished loading, a certain first interactive element within it may still be loading. In this case, when responding according to the first interactive pair recorded in the meeting interaction file, the first interactive element may not be found, and the corresponding interactive operation cannot be performed on it. The meeting client will then consider that no corresponding interactive operation is needed, thus failing to meet the user's configuration requirements. To avoid this situation, in one embodiment, the first interactive element can be searched periodically. The meeting interaction file also records a timed search rule corresponding to the first interactive element. This timed search rule specifies the period for searching the first interactive element when executing the meeting interaction file, ensuring that the search for the first interactive element can be performed within each period until it is found. The period duration can be implemented by setting a setTimeout timer; the specific value of the period duration can be set according to actual needs, and will not be elaborated in detail in this embodiment. After executing the meeting interaction file, if a timed search rule exists for a certain first interaction element, then the first interaction element can be searched periodically according to the period duration specified in the custom search rule. Specifically, a timer is started, and the first interaction element is searched. If the first interaction element is not found after the timer expires (i.e., one period duration ends), another period duration is started, and the search for the first interaction element continues until it is found.

[0090] Step 203: Receive the interaction operation for the first interaction element. The interaction operation is the operation performed on the first interaction element according to the first interaction rule when executing the meeting interaction document.

[0091] During the execution of the meeting interaction file by the meeting client, interactive operations can be performed on the corresponding first interactive element in the meeting configuration interface according to the first interactive rule in the meeting interaction file. The interactive operation is the operation that needs to be performed on the first interactive element during the process of joining the remote meeting.

[0092] In one embodiment, the interactive operation includes at least one of the following: switch selection operation, information writing operation, button click operation, option selection operation, and pop-up close operation. The switch selection operation refers to the operation whereby a user selects or toggles the state of a switch through interactive methods such as clicking or swiping, thereby controlling the on / off state of a function or service. For example, Figure 5The microphone switch button 32 and camera switch button 33 can be used as switch selection operations based on the interactive operations they need to receive. Information writing operations (input) refer to the operation of inputting or editing information through input boxes, forms, or other interactive elements, for example, in... Figure 5 Input box 31 allows you to enter your conference name; the corresponding interactive action will then serve as the information writing operation. Button pre-click operations are actions that trigger corresponding program events or functions by clicking a button on the screen. For example... Figure 5 The "Apply to Join" button 36 requires an interactive action, which can be represented by a button click. An option selection action is the process of choosing one option from multiple options, for example... Figure 5 The microphone device option 34 and camera device option 35 can be selected based on the interactive operations they require. A pop-up close operation refers to the user closing a pop-up window or dialog box by clicking the close button or performing other actions. For example, in a meeting configuration webpage, clicking a link or button may trigger a prompt or confirmation box with "OK" or "Cancel" buttons. Clicking the "OK" or "Cancel" button in this case serves as a pop-up close operation. Similarly, when an advertisement window pops up on a meeting configuration webpage, clicking the close button in the upper right corner of the advertisement window closes it; in this case, clicking the close button also serves as a pop-up close operation.

[0093] After performing the corresponding operation on the first interactive element according to the first interaction rule, it can be considered that an interaction operation has been received for the first interactive element. That is, for the meeting configuration webpage, it still receives an interaction operation for the first interactive element, but this interaction operation is not initiated by the user, but is automatically initiated by the meeting client based on the first interaction rule. The meeting configuration webpage does not need to know who initiated the operation; it only needs to receive the interaction operation.

[0094] It should be noted that when there are multiple first-interaction elements on the meeting configuration webpage, and some of these elements may need to perform interactive operations in a preset order, for example, for... Figure 5 The meeting configuration webpage shown requires users to enter their meeting name in input box 31 and then click the "Apply to Join" button 36 to apply to join the target meeting. In this case, users can also predefine the interaction order in the first interaction rule. For example, the first interaction rule corresponding to input box 31 can be defined to execute the first interaction rule corresponding to the "Apply to Join" button 36 afterward, so that the meeting client can perform interactive operations on the first interactive elements in the order of interaction to complete the configuration of the target meeting.

[0095] Step 204: Display the results of the interactive operation on the meeting configuration webpage, and obtain the address of the second webpage when it is determined that a webpage needs to be redirected.

[0096] After the meeting client performs an interactive operation on the first interactive element, the meeting configuration webpage will display the result of the interactive operation. The operation result can also be considered a response to the interactive operation, which at least includes the form that the first interactive element should display when it receives the interactive operation. For example, when the interactive operation is a switch selection operation, the operation result is the form of the switch (i.e., the first interactive element) after it is turned on or off, and the corresponding function is set to on or off; when the interactive operation is a message writing operation, the operation result is to display the currently entered information in the input box (i.e., the first interactive element), and when the information entered in the input box needs to be used, to confirm that the currently entered information is used; when the interactive operation is a button click operation, the operation result is to display the form of the button (i.e., the first interactive element) after it is clicked, and to respond to the function corresponding to the button; when the interactive operation is an option selection operation, the operation result is to display the selected option (i.e., the first interactive element), and to confirm that the selected option is used; when the interactive operation is a pop-up close operation, the operation result is to close the currently displayed pop-up (i.e., the first interactive element). It can be understood that displaying the operation results allows the user of the meeting client to clearly understand which interactive operations the meeting client has automatically performed.

[0097] In some cases, the result may also include a redirect to a webpage. For example, Figure 5 When the "Request to Join" button 36 is clicked, the corresponding function of the button is that the meeting client will redirect to a new webpage, i.e., load a new webpage. For example, Figure 1 After clicking option 11, "Continue in browser," the meeting client will redirect to a new webpage, i.e., load a new webpage. Before loading the new webpage, the meeting client needs to obtain the webpage address. Currently, the address of the webpage to be loaded is denoted as the second webpage address. That is, when the meeting client responds to an interactive operation, if it needs to redirect to a webpage, it can obtain the second webpage address. It can be understood that the second webpage address is generated by the target meeting server and sent to the meeting client.

[0098] It is understandable that each time an interactive operation is performed based on the meeting interaction file, the corresponding operation result will be displayed.

[0099] Step 205: When the second webpage address corresponds to the target meeting webpage, load the corresponding target meeting webpage according to the second webpage address. The target meeting webpage is the webpage after joining the target meeting.

[0100] After obtaining the second webpage address, the meeting client loads the corresponding webpage based on that address. Currently, the webpage corresponding to the second webpage address can be either the meeting configuration webpage or the target meeting webpage, which can be determined based on the actual joining process of the target meeting.

[0101] If the second webpage address corresponds to the meeting configuration webpage, then after the meeting client loads the meeting configuration webpage, it can continue to automatically perform operations on the interactive elements in the meeting configuration webpage, that is, repeat steps 202-204.

[0102] If the second webpage address corresponds to the target meeting webpage, then once the meeting client confirms that the target meeting webpage has been loaded, the user can confirm joining the target meeting.

[0103] It should be noted that the target meeting webpage may also contain interactive elements (hereinafter referred to as the second interactive element). For example, the target meeting webpage may contain options for setting the volume and screen resolution of the target meeting. In this case, the interaction rules corresponding to the interactive element (hereinafter referred to as the second interaction rule) can be pre-set and recorded in the meeting interaction file corresponding to the target meeting webpage. This allows the meeting client to perform interactive operations on the second interactive element according to the second interaction rule in the meeting interaction file after being redirected to the target meeting webpage, thereby configuring the target meeting. The specific process can be referred to the process of performing interactive operations on the meeting configuration webpage described above, and will not be repeated in this embodiment.

[0104] Understandably, for the meeting client to execute JS files (i.e., meeting interaction files) correctly, a JS configuration file needs to be configured. This JS configuration file can be stored on the meeting client or in a cloud database (i.e., the database used by the meeting client's server). The JS configuration file records the configurations required when the JS file is executed. Currently, the JS configuration file at least records the webpage identifier (e.g., webpage address) corresponding to each JS file. This allows the meeting client to find the file identifier (e.g., filename) of the corresponding JS file based on the webpage identifier after loading a webpage, thus determining which JS file to execute. Optionally, if no JS file identifier is found, it is determined that the currently loaded webpage does not require automatic interactive operations.

[0105] Figure 6The flowchart illustrates a meeting joining method provided in this application embodiment. The meeting client loads a meeting configuration webpage via WebView. Upon receiving the `onPageFinished` callback, it confirms the webpage loading is complete and queries the corresponding JS file (i.e., the meeting interaction file) through a JS configuration file (represented by `teams_manifest.json`). The meeting client then executes interactive operations on the first interactive element in the meeting configuration webpage according to the first interaction rule in the JS file, thereby configuring the target meeting. Finally, the meeting client loads the target meeting webpage based on WebView to join the target meeting.

[0106] As described above, by pre-setting a meeting interaction file corresponding to the meeting configuration webpage, the meeting client, after loading the meeting configuration webpage, can call the corresponding meeting interaction file to perform interactive operations on the interactive elements in the meeting configuration webpage according to the interaction rules in the meeting interaction file. This automatically executes the operations on the interactive elements, and after the operations are completed, the user can automatically join the target meeting. In other words, during the process of a user joining a target meeting using the meeting client, the meeting client can automatically complete the operations required to join the target meeting without manual intervention, simplifying the user's operation, greatly improving the user experience, and solving the technical problem of complex and cumbersome operations in the process of joining a remote meeting in related technologies. Furthermore, the current interactive operation styles are quite rich, basically covering all scenarios requiring user operation during the meeting joining process. Moreover, by recording the timed search rules corresponding to the first interactive element in the meeting interaction file, the action of searching for the first interactive element in the meeting configuration webpage can be periodically executed after the meeting interaction file is executed. This avoids missing the first interactive element when it loads slowly, thus preventing situations where no interactive operation is performed on the first interactive element.

[0107] Figure 7 This is a flowchart illustrating another meeting joining method provided in this application embodiment. The meeting joining method provided in this application embodiment is a specific embodiment of the above-described meeting joining method. (Refer to...) Figure 7 The methods for joining the meeting include:

[0108] Step 401: Load the corresponding meeting configuration webpage based on the currently obtained first webpage address. The meeting configuration webpage is a webpage that requires user interaction during the process of joining the target meeting. The target meeting is a meeting created using third-party meeting software. The meeting configuration webpage contains at least one first interactive element.

[0109] Step 402: Once it is confirmed that the meeting configuration webpage has been loaded, locate the corresponding meeting interaction file in the meeting configuration plugin based on the first webpage address. The meeting configuration plugin includes the first webpage address of the meeting configuration webpage required to join the target meeting process and the meeting interaction file corresponding to the first webpage address. There is at least one meeting configuration webpage.

[0110] A meeting configuration plugin is an auxiliary tool or extension that runs in a meeting client to enhance or customize the functionality of third-party meeting software. Meeting configuration plugins allow users to add, modify, or extend the functionality of the meeting client according to specific needs or scenarios without modifying the main program. Currently, meeting configuration plugins are used to automatically implement interactive operations required by the user during the process of joining a target meeting. In one embodiment, the meeting configuration plugin includes a first webpage address of the meeting configuration webpage required for joining the target meeting and a corresponding meeting interaction file for the first webpage address. Each first webpage address corresponds to one meeting interaction file, and there is at least one meeting configuration webpage. When multiple meeting configuration webpages need to be loaded sequentially during the process of joining the target meeting, multiple meeting interaction files exist.

[0111] In one embodiment, the meeting configuration plugin is a JS plugin. The JS plugin consists of at least one JS file and a JS configuration file. Each JS file represents a meeting interaction file, which is composed of JS code. The JS configuration file records the correspondence between each JS file and its corresponding webpage address (currently, the webpage address is used as the webpage identifier). The JS configuration file is denoted as manifest.json. A JS file can be denoted as xxx.js, and the specific content of xxx varies depending on the JS file. When the meeting client calls the JS plugin, it can find the corresponding JS file in the JS configuration file based on the first webpage address and execute the JS file.

[0112] In one embodiment, the meeting client supports multiple third-party conferencing software programs, each with its own corresponding meeting configuration plugin. Currently, the meeting client can access and use the meeting services provided by various third-party conferencing software programs and join target meetings created by different third-party conferencing software programs. To ensure compatibility with multiple third-party conferencing software programs and automatically configure and join target meetings during the process of joining such meetings, this embodiment requires pre-setting meeting configuration plugins corresponding to different third-party conferencing software programs and saving them to a database on the meeting client's local machine or in the cloud. Subsequently, the meeting client can call the corresponding meeting configuration plugin based on the different third-party conferencing software programs to automatically complete the configuration process and join the target meeting.

[0113] Step 403: Execute the found meeting interaction file. The meeting interaction file records the first interaction rules when interacting with the first interaction element.

[0114] Optionally, the meeting interaction file also records the timed lookup rules corresponding to the first interaction element.

[0115] Step 404: Receive the interaction operation for the first interaction element. The interaction operation is the operation performed on the first interaction element according to the first interaction rule when executing the meeting interaction document.

[0116] Step 405: Display the results of the interactive operation on the meeting configuration webpage, and obtain the address of the second webpage when it is determined that a webpage needs to be redirected.

[0117] Step 406: When the second webpage address corresponds to the target meeting webpage, load the corresponding target meeting webpage according to the second webpage address. The target meeting webpage is the webpage after joining the target meeting.

[0118] Step 407: Locate the corresponding meeting information collection file in the meeting configuration plugin based on the second webpage address.

[0119] In one embodiment, the target meeting webpage contains at least one meeting information element, and the meeting configuration plugin further includes a second webpage address of the target meeting webpage and a meeting information collection file corresponding to the second webpage address. The meeting information collection file records the identification rules for the meeting information elements.

[0120] Similar to meeting interaction files, meeting information collection files can be JavaScript files. These files include rules for identifying meeting information elements, which are elements carrying meeting information. This information may include the target meeting's meeting ID and password (the password to join the target meeting). The meeting information elements are displayed on the target meeting's webpage; that is, the target meeting webpage contains at least one meeting information element. The rules for identifying meeting information elements refer to the rules used to extract the meeting information represented by these elements from the target meeting webpage. Their specific content can be set according to actual needs; for example, the rules may include the identifier, location, and method of extracting meeting information elements.

[0121] Understandably, if the target meeting webpage also contains a second interactive element to be interacted with—for example, if the target meeting webpage includes options for setting the volume and screen resolution of the target meeting—then the second interactive rules corresponding to the interactive element can be pre-set and recorded in the meeting information collection file. In this case, the meeting information collection file also functions as a meeting interaction file, and is specific to the target meeting webpage.

[0122] In one embodiment, there is a correspondence between target conference webpages and conference information collection files; that is, each target conference webpage has a corresponding conference information collection file. The corresponding conference information collection file can be found through the webpage identifier of the target conference webpage. Currently, the second webpage address corresponding to the target conference webpage can be used as the webpage identifier, meaning that the conference client can find the corresponding conference information collection file based on the second webpage address.

[0123] In one embodiment, the JS configuration file of the meeting configuration plugin also records the second webpage address corresponding to the meeting information collection file (i.e., the second webpage address of the target meeting webpage and the meeting information collection file corresponding to the second webpage address). After the meeting client determines that the target meeting webpage has been loaded (which can be achieved by receiving the onPageFinished callback), it can look up the file identifier (such as the file name) of the corresponding meeting information collection file based on the second webpage address of the target meeting webpage according to the JS configuration file, so that the meeting client can determine which meeting information collection file needs to be executed.

[0124] Step 408: Execute the found meeting information collection file.

[0125] After locating the meeting information collection file corresponding to the target meeting webpage, the meeting client executes the meeting information collection file.

[0126] During the execution of the meeting information collection file, the meeting information elements in the target meeting webpage can be identified according to the recognition rules in the file to extract the meeting information contained therein. For example, Figure 8 This is a schematic diagram of the interface of a target meeting webpage provided in an embodiment of this application. Figure 8 The meeting information elements include the target meeting's meeting ID (e.g., 51) and the meeting password (e.g., 52). Optionally, both meeting elements can be text elements. During the execution of the meeting information collection file, the target meeting's meeting ID "AAAA" and the meeting password "BBBB" can be extracted.

[0127] Optionally, a timed lookup rule corresponding to the second interactive element can be recorded in the meeting information collection file, depending on the actual situation. This rule serves the same purpose and is implemented in the same way as the timed lookup rule for the first interactive element, and will not be elaborated upon here. By using timed lookup rules, meeting information elements can still be identified even when loading is slow.

[0128] Step 409: Obtain meeting information. The meeting information is obtained when the meeting information collection file is executed and the meeting information elements are identified according to the recognition rules.

[0129] Optionally, after obtaining the meeting information, the meeting client can also acquire it. In one embodiment, the meeting configuration plugin (i.e., the JS plugin) and the meeting client can communicate via jsbridge technology. That is, the meeting information extracted by the JS plugin can be sent to the meeting client via jsbridge technology, enabling the meeting client to obtain the meeting information. When sending the meeting information, a JavaScriptinterface (a method that allows JavaScript code to interact with other programming languages ​​or technologies) can be called, and a native method can be executed to send the meeting information back to the meeting client. The native method is a native method defined in the meeting client that records how to receive the meeting information via jsbridge technology.

[0130] Step 410: Save meeting information.

[0131] After obtaining the meeting information, the meeting client can save it for later use. In one embodiment, after saving the meeting information, the meeting client can generate a QR code for joining the meeting and share it with other users. Other users can join the target meeting by scanning the QR code. For example, Figure 9 As shown, Figure 9 This is a flowchart illustrating a meeting joining method provided in this application. After determining that it needs to be redirected to the target meeting webpage, the meeting client loads the meeting configuration webpage via WebView. Upon receiving the onPageFinished callback, it confirms that the target meeting webpage has finished loading and queries the corresponding JS file (i.e., the meeting information collection file) through the JS configuration file (which can be represented by teams_manifest.json). Then, the meeting client identifies the meeting information elements in the target meeting webpage according to the recognition rules in the JS file, retrieves the meeting information from these elements, executes native methods, and sends the meeting information back to the meeting client.

[0132] As described above, by setting a meeting information collection file in the meeting configuration plugin, after the meeting client joins the target meeting, it can identify meeting information elements in the target meeting webpage by executing the meeting information collection file, thereby collecting and saving the meeting information of the target meeting. This enables automatic collection of meeting information, eliminating the need for manual collection when users need meeting information, further reducing user operation steps and improving the user experience. Furthermore, when multiple meeting configuration webpages need to be loaded during the process of joining the target meeting, the meeting client can call and execute the meeting interaction file corresponding to each meeting configuration webpage according to the meeting configuration plugin during the loading of each webpage, thereby achieving automated configuration for each meeting configuration webpage. This means refining specific interaction rules for each specific page, greatly improving configuration efficiency and enhancing the user experience. Moreover, by setting meeting configuration plugins corresponding to different third-party meeting software, the meeting client can automatically configure the target meeting when joining target meetings created by different third-party meeting software, expanding the applicability of the meeting configuration method provided in this application.

[0133] Based on the above embodiments, when the meeting client runs the meeting configuration plugin, the meeting configuration plugin needs to be the latest version. This latest version is applicable to the latest version of the corresponding third-party meeting software, so that even if the third-party meeting software is updated, the meeting configuration plugin can still automatically join meetings and configure target meetings. In this case, the meeting joining method may further include: when the version update condition is met, obtaining the latest first version number of the meeting configuration plugin from the server. The version update condition is that the meeting client completes startup or receives a meeting selection instruction from the user, which is an instruction to join a meeting created by the third-party meeting software. Determining whether the second version number of the currently used meeting configuration plugin is consistent with the first version number. If the second version number is inconsistent with the first version number, downloading the meeting configuration plugin corresponding to the first version number from the server and replacing the local meeting configuration plugin with the downloaded one.

[0134] In one embodiment, when the meeting configuration plugin version update conditions are met, the meeting client will also determine whether the meeting configuration plugin is the latest version, and if it is not the latest version, update the meeting configuration plugin to the latest version.

[0135] The version update condition is that the meeting client completes startup or receives a meeting selection command from the user. For example, after the meeting client starts up, it accesses the server and retrieves the version number corresponding to the latest version of the meeting configuration plugin. When the meeting client is compatible with multiple third-party meeting software, it can retrieve the version number of the latest version of the meeting configuration plugin for each third-party meeting software from the server. As another example, after receiving a meeting selection command from the user (which selects the third-party meeting software corresponding to the target meeting), the meeting client retrieves the version number of the latest version of the meeting configuration plugin for that third-party meeting software from the server according to the command. The version number is a set of numbers or identifiers used to identify different versions of software, systems, or applications, typically used to track software changes, updates, and fixes. Currently, the latest version number retrieved from the server is designated as the first version number. Optionally, the meeting configuration plugin version number can be implemented using MD5 hashes.

[0136] Optionally, each meeting configuration plugin (including JS configuration files and JS files) can be stored in a database used by the server on the meeting client. In this case, the database also stores the configuration of the meeting configuration plugin (i.e., jsConFig), which records the URL and MD5 hash of the latest meeting configuration file. When the meeting client determines that the version update conditions are met, it sends a request to the server. The server reads the database based on this request, finds the URL and MD5 hash of the meeting configuration file in the database's configuration, and sends it back to the meeting client.

[0137] After obtaining the latest version number of the meeting configuration plugin, the meeting client checks if the version number of the currently used local meeting configuration plugin matches the version number to determine if it is the latest version. Taking MD5 as the version number as an example, the meeting client checks if the obtained MD5 code matches the local MD5 code. If they don't match, the meeting client confirms that the currently used local meeting configuration plugin is not the latest version. The meeting client needs to download the meeting configuration plugin corresponding to the version number from the server and replace the local plugin with the downloaded one to complete the local meeting configuration plugin update. At this point, the meeting client can download the latest meeting configuration plugin via a URL and replace the local plugin. If they match, there is no need to update the local meeting configuration.

[0138] In one embodiment, such as Figure 10 As shown, Figure 10This diagram illustrates an embodiment of updating a JS plugin. After developing a new version of the JS plugin, the user imports it into the server database. Once the meeting client starts or receives a meeting selection command from the user, it retrieves the latest first version number from the server database and compares it with the second version number of the local JS plugin to determine whether to update the JS plugin.

[0139] As described above, in this embodiment of the application, when the meeting configuration plugin version update condition is met, the meeting client obtains the latest first version number of the meeting configuration plugin from the server and determines whether the version number of the local meeting configuration plugin is the first version number. If it is not the first version number, the meeting configuration plugin corresponding to the first version number is downloaded from the server, completing the update of the local meeting configuration plugin, thereby ensuring that the latest version of the meeting configuration plugin can be used. Furthermore, because the meeting configuration plugin is lightweight, highly flexible, and cross-platform compatible, it enables rapid development, and after development, it can be quickly deployed and iterated. When requirements change, only the meeting configuration plugin needs to be modified, without requiring changes to the underlying code of the meeting client, making it widely applicable.

[0140] This application also provides a meeting joining device. Figure 11 This is a schematic diagram of a meeting joining device provided in an embodiment of this application, as shown below. Figure 11 As shown, the meeting joining device provided in this embodiment is suitable for meeting clients, and the meeting joining device includes:

[0141] The configuration webpage loading module 501 is used to load the corresponding meeting configuration webpage based on the currently obtained first webpage address. The meeting configuration webpage is a webpage that requires user interaction during the process of joining the target meeting. The target meeting is a meeting created using third-party meeting software. The meeting configuration webpage contains at least one first interactive element. The interaction file execution module 502 is used to execute the meeting interaction file corresponding to the meeting configuration webpage when it is determined that the meeting configuration webpage has been loaded. The meeting interaction file records the first interaction rules when interacting with the first interactive element. The interaction operation receiving module 503 is used to receive the interaction operation for the first interactive element. The interaction operation is the operation performed on the first interactive element according to the first interaction rules when the meeting interaction file is executed. The operation result display module 504 is used to display the operation result of the interaction operation in the meeting configuration webpage and obtain the second webpage address when it is determined that a page needs to be redirected. The meeting joining module 505 is used to load the corresponding target meeting webpage based on the second webpage address when the second webpage address corresponds to the target meeting webpage. The target meeting webpage is the webpage after joining the target meeting.

[0142] Based on the above embodiments, the interactive file execution module 502 includes: an interactive file search submodule, used to search for the corresponding interactive meeting file in the meeting configuration plugin according to the first webpage address when it is determined that the meeting configuration webpage has been loaded. The meeting configuration plugin includes the first webpage address of the meeting configuration webpage required to join the target meeting process and the interactive meeting file corresponding to the first webpage address. There is at least one meeting configuration webpage; and an interactive file execution submodule, used to execute the found interactive meeting file.

[0143] Based on the above embodiments, the target meeting webpage contains at least one meeting information element, and the meeting configuration plugin also includes a second webpage address of the target meeting webpage and a meeting information collection file corresponding to the second webpage address. The meeting information collection file records the identification rules for the meeting information elements. The meeting joining device also includes: a collection file search module, used to search for the corresponding meeting information collection file in the meeting configuration plugin according to the second webpage address; a collection file execution module, used to execute the found meeting information collection file; a meeting information acquisition module, used to acquire meeting information, which is the meeting information obtained when the meeting information collection file is executed and the meeting information elements are identified according to the identification rules; and an information storage module, used to store the meeting information.

[0144] Based on the above embodiments, the meeting client supports a variety of third-party meeting software, and each third-party meeting software has a corresponding meeting configuration plugin.

[0145] Based on the above embodiments, the meeting joining device further includes: a version number query module, used to obtain the latest first version number of the meeting configuration plugin from the server when the version update condition is met, wherein the version update condition is that the meeting client completes startup or receives a meeting selection instruction issued by the user, and the meeting selection instruction is an instruction to join a meeting created by third-party meeting software; a version number judgment module, used to determine whether the second version number of the meeting configuration plugin currently used locally is consistent with the first version number; and a plugin update module, used to download the meeting configuration plugin corresponding to the first version number from the server if the second version number is inconsistent with the first version number, and replace the local meeting configuration plugin with the downloaded meeting configuration plugin.

[0146] Based on the above embodiments, the conference interaction file also records the timed search rule corresponding to the first interactive element. The timed search rule is used to specify the period of searching for the first interactive element when executing the conference interaction file, so that the action of searching for the first interactive element can be performed within each period of time until the first interactive element is found.

[0147] Based on the above embodiments, the interactive operations include at least one of the following: switch selection operation, information writing operation, button click operation, option selection operation, and pop-up window closing operation.

[0148] The meeting joining method apparatus provided in this application embodiment is included in the meeting joining device and can be used to execute the meeting joining method provided in the above embodiment, and has corresponding functions and beneficial effects.

[0149] It is worth noting that in the embodiments of the meeting joining method device described above, the various units and modules included are only divided according to functional logic, but are not limited to the above division, as long as the corresponding functions can be achieved; in addition, the specific names of each functional unit are only for easy differentiation and are not used to limit the scope of protection of this application.

[0150] This application also provides a meeting joining device, such as... Figure 12 As shown, Figure 12 This is a schematic diagram of a conference joining device provided in an embodiment of the present application. The conference joining device 60 provided in this embodiment of the present application includes a processor 600 and a memory 601;

[0151] The memory 601 is used to store the computer program 602 and to transfer the computer program 602 to the processor 600;

[0152] The processor 600 is used to execute the steps in one of the above-described meeting joining method embodiments according to the instructions in the computer program 602.

[0153] For example, computer program 602 may be divided into one or more modules / units, one or more of which are stored in memory 601 and executed by processor 600 to complete this application. One or more modules / units may be a series of computer program instruction segments capable of performing a specific function, which describe the execution process of computer program 602 in conference joining device 60.

[0154] The participating devices can be network-connected electronic devices such as mobile phones, tablets, interactive whiteboards (e.g., IFP), laptops, and desktop computers. The participating device 60 may include, but is not limited to, processor 600 and memory 601. Those skilled in the art will understand that... Figure 12 This is merely an example of conference joining device 60 and does not constitute a limitation on conference joining device 60. It may include more or fewer components than shown, or combine certain components, or different components. For example, conference joining device 60 may also include input / output devices, network access devices, buses, displays, communication modules, etc.

[0155] For a description of the processor 600 and memory 601, please refer to the description in the foregoing embodiments.

[0156] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0157] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces, or indirect coupling or communication connection between apparatuses or units, and may be electrical, mechanical, or other forms.

[0158] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0159] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0160] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing computer programs, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0161] One embodiment of this application also provides a storage medium containing computer-executable instructions, which, when executed by a processor, are used to perform relevant operations in the meeting joining method provided in any embodiment of this application, and have corresponding functions and beneficial effects.

[0162] Note that the above are merely preferred embodiments and the technical principles applied in this application. Those skilled in the art will understand that the embodiments of this application are not limited to the specific embodiments described herein, and various obvious changes, readjustments, and substitutions can be made by those skilled in the art without departing from the protection scope of the embodiments of this application. Therefore, although the embodiments of this application have been described in detail through the above embodiments, the embodiments of this application are not limited to the above embodiments. More other equivalent embodiments may be included without departing from the concept of the embodiments of this application, and the scope of the embodiments of this application is determined by the scope of the appended claims.

Claims

1. A method for joining a meeting, characterized in that, The meeting joining method is applicable to meeting clients, and the meeting joining method includes: The corresponding meeting configuration webpage is loaded based on the first webpage address obtained at present. The meeting configuration webpage is a webpage that requires user interaction during the process of joining the target meeting. The target meeting is a meeting created using third-party meeting software. The meeting configuration webpage contains at least one first interactive element. Once it is determined that the meeting configuration webpage has been loaded, the meeting interaction file corresponding to the meeting configuration webpage is executed. The meeting interaction file records the first interaction rules when interacting with the first interaction element. Receive an interactive operation for the first interactive element, wherein the interactive operation is an operation performed on the first interactive element according to the first interactive rule when executing the meeting interactive file; The operation results of the interactive operation are displayed on the meeting configuration webpage, and when it is determined that a webpage needs to be redirected, the address of the second webpage is obtained; When the second webpage address corresponds to the target meeting webpage, the corresponding target meeting webpage is loaded according to the second webpage address. The target meeting webpage is the webpage after joining the target meeting.

2. The meeting joining method according to claim 1, characterized in that, The step of executing the meeting interaction file corresponding to the meeting configuration webpage after determining that the meeting configuration webpage has been loaded includes: Once it is determined that the meeting configuration webpage has been loaded, the corresponding meeting interaction file is searched in the meeting configuration plugin according to the first webpage address. The meeting configuration plugin includes the first webpage address of the meeting configuration webpage required to join the target meeting process and the meeting interaction file corresponding to the first webpage address. The meeting configuration webpage is at least one. Execute the found meeting interaction file.

3. The meeting joining method according to claim 2, characterized in that, The target meeting webpage contains at least one meeting information element, and the meeting configuration plugin also includes a second webpage address of the target meeting webpage and a meeting information collection file corresponding to the second webpage address. The meeting information collection file records the identification rules for the meeting information element. After loading the corresponding target meeting webpage according to the second webpage address, the process further includes: Locate the corresponding meeting information collection file in the meeting configuration plugin based on the second webpage address; Execute the retrieved meeting information collection file; Acquire meeting information, which is the meeting information obtained when the meeting information collection file is executed and meeting information elements are identified according to the identification rules; Save the meeting information.

4. A method for joining a meeting according to claim 2, characterized in that, The meeting client supports a variety of third-party meeting software, and each of these third-party meeting software programs has a corresponding meeting configuration plugin.

5. The meeting joining method according to any one of claims 2-4, characterized in that, Also includes: When the version update conditions are met, the latest first version number of the meeting configuration plugin is obtained from the server. The version update conditions are that the meeting client completes startup or receives a meeting selection instruction from the user. The meeting selection instruction is an instruction to join a meeting created by third-party meeting software. Determine whether the second version number of the currently used meeting configuration plugin on the local machine is consistent with the first version number; If the second version number is inconsistent with the first version number, then download the meeting configuration plugin corresponding to the first version number from the server and replace the local meeting configuration plugin with the downloaded meeting configuration plugin.

6. A method for joining a meeting according to claim 1, characterized in that, The meeting interaction file also records the timed search rule corresponding to the first interactive element. The timed search rule is used to specify the period of searching for the first interactive element when the meeting interaction file is executed, so that the action of searching for the first interactive element can be performed within each period of time until the first interactive element is found.

7. A method for joining a meeting according to claim 1, characterized in that, The interactive operations include at least one of the following: switch selection operation, information writing operation, button click operation, option selection operation, and pop-up window closing operation.

8. A meeting joining device, characterized in that, The meeting joining device is suitable for meeting clients, and the meeting joining device includes: The configuration webpage loading module is used to load the corresponding meeting configuration webpage according to the currently obtained first webpage address. The meeting configuration webpage is a webpage that requires user interaction during the process of joining the target meeting. The target meeting is a meeting created using third-party meeting software. The meeting configuration webpage contains at least one first interactive element. An interactive file execution module is used to execute a meeting interactive file corresponding to the meeting configuration webpage when it is determined that the meeting configuration webpage has been loaded. The meeting interactive file records a first interaction rule when interacting with the first interactive element. An interactive operation receiving module is used to receive interactive operations for the first interactive element, wherein the interactive operation is an operation performed on the first interactive element according to the first interactive rules when the meeting interactive file is executed; The operation result display module is used to display the operation result of the interactive operation on the meeting configuration webpage, and to obtain the second webpage address when it is determined that a webpage needs to be redirected. The meeting joining module is used to load the corresponding target meeting webpage according to the second webpage address when the second webpage address corresponds to the target meeting webpage. The target meeting webpage is the webpage after joining the target meeting.

9. A conference joining device, characterized in that, The conference joining device includes a processor and a memory; The memory is used to store computer programs and to transfer the computer programs to the processor; The processor is configured to execute a meeting joining method as described in any one of claims 1-7 according to instructions in the computer program.

10. A storage medium for storing computer-executable instructions, characterized in that, The computer-executable instructions, when executed by a computer processor, are used to perform a meeting joining method as described in any one of claims 1-7.

Images