Remote conference starting method, terminal device and storage medium

Abstract

Embodiments of the present application disclose a remote conference starting method, a terminal device and a storage medium. The method receives a conference starting instruction in a window of a collaboration application, the collaboration application logs in a collaboration server through a user account; in response to the conference starting instruction, the collaboration application requests a conference code from a conference server through the collaboration application, the collaboration server and the conference server are mutually connected; the conference code and the user account are sent to a conference application as opening parameters through a page jump protocol, so that the conference application logs in the conference server through the user account and joins a remote conference, the collaboration application and the conference application correspond to the same user account of the same user; the collaboration application obtains a conference state of the user account on the conference server from the collaboration server, and displays the conference state on the window of the collaboration application, the conference state is synchronized from the conference server to the collaboration server. The collaboration application directly starts the conference application through information transmission, and accurately obtains the conference state in the conference process.

Description

Technical Field

[0001] The embodiments of the present invention relate to the field of computer-aided conferencing technology, and in particular to remote conferencing initiation methods, terminal devices, and storage media. Background Technology

[0002] In computer-assisted conferencing scenarios, different auxiliary applications are designed to meet various meeting needs. For example, collaboration applications record and save meeting-related data, while conferencing applications enable real-time video transmission. In computer-assisted conferencing scenarios, there may be a need to use different auxiliary applications in combination to meet diverse requirements. For instance, collaboration applications might be used for whiteboard recording and saving, while conferencing applications might be used for real-time video transmission of both the participants and the whiteboard.

[0003] When the inventors used a collaboration application and a conferencing application to perform multi-dimensional data processing during a remote meeting, they discovered that during the remote meeting, the collaboration application could not transmit information to the conferencing application, and the conferencing application could not accurately determine the running status of the conferencing application. Summary of the Invention

[0004] This invention provides a method for initiating a remote meeting, a terminal device, and a storage medium to solve the technical problems that existing collaborative applications and meeting applications cannot transmit information, and that collaborative applications cannot accurately determine the operating status of meeting applications.

[0005] In a first aspect, embodiments of the present invention provide a method for initiating a remote conference, including:

[0006] Receive the meeting start command in the window of the collaboration application, and log in to the collaboration server through the user account in the collaboration application;

[0007] In response to the meeting start command, the collaboration application requests a meeting code from the meeting server, and the collaboration server and the meeting server connect to each other;

[0008] The meeting code and user account are sent as opening parameters to the meeting application via a page redirection protocol, so that the meeting application can log in to the meeting server with the user account and join the remote meeting according to the meeting code. The collaboration application and the meeting application correspond to the same user account.

[0009] The collaboration application retrieves the user account's meeting status on the meeting server from the collaboration server and displays the meeting status in the collaboration application's window. The meeting status is synchronized from the meeting server to the collaboration server.

[0010] Secondly, embodiments of the present invention also provide a terminal device, including:

[0011] One or more processors;

[0012] Memory, used to store one or more programs;

[0013] When the one or more programs are executed by the one or more processors, the terminal device enables the remote conference initiation method as described in the first aspect.

[0014] Thirdly, embodiments of the present invention also provide a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the remote conference initiation method as described in the first aspect.

[0015] The aforementioned remote conferencing initiation method, terminal device, and storage medium, through receiving a conferencing initiation command in the window of the collaboration application, allows the collaboration application to log in to the collaboration server using a user account. In response to the initiation command, the collaboration application requests a conferencing code from the conferencing server, and the collaboration server and conferencing server connect. A page redirection protocol is used to send the conferencing code and user account as initiation parameters to the conferencing application, enabling the conferencing application to log in to the conferencing server using the user account and join the remote conferencing based on the conferencing code. The collaboration application and conferencing application correspond to the same user account. The collaboration application retrieves the user account's conferencing status from the collaboration server and displays the conferencing status in its window. The conferencing status is synchronized from the conferencing server to the collaboration server. By connecting the collaboration server and conferencing server, the collaboration application obtains conferencing-related information generated by the conferencing server and uses this information as initiation parameters. When starting the conferencing application via the page redirection protocol, it directly joins the remote conferencing based on the conferencing-related information. The collaboration application retrieves the conferencing status from the conferencing server through the collaboration server, enabling the collaboration application to directly initiate the conferencing application through information transmission and accurately obtain the conferencing status during the meeting. Attached Figure Description

[0016] Figure 1 This is a flowchart illustrating a method for initiating a remote meeting, as provided in an embodiment of the present invention.

[0017] Figure 2 This is a schematic diagram of the data transmission and reception process of a remote conference initiation method provided in an embodiment of the present invention.

[0018] Figure 3 This is a schematic diagram of the structure of a terminal device provided in an embodiment of the present invention. Detailed Implementation

[0019] The present invention will now be described in further detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are for illustrative purposes only and not for limiting the invention. Furthermore, it should be noted that, for ease of description, the accompanying drawings show only the parts relevant to the present invention and not the entire structure.

[0020] It should be noted that, due to space limitations, this application specification does not exhaustively list all possible implementation methods. Those skilled in the art should be able to conceive after reading this application specification that, as long as the technical features do not contradict each other, any combination of technical features can constitute an optional implementation method.

[0021] In multi-person interactive scenarios such as meetings, teaching, discussions, and brainstorming, information transmission between multiple participants has historically been achieved through speech, sight, and hearing. This information transmission can provide participants with a good communication experience, but the recording of information during the communication process depends on the participants' personal habits and abilities, and the actual information transmitted may be lost.

[0022] With the development of information technology, information display and recording in multi-person interactive scenarios have become more sophisticated, especially in multi-person interaction based on conference equipment. Each participant can centralize the content they need to present on the conference equipment, and the equipment can receive and save various information from the collaborative communication process. Conference equipment can be hardware products specifically developed for conference scenarios (such as interactive whiteboards), or it can utilize existing devices (large-screen smart TVs) for content display. Overall, the conference equipment implementing the collaborative information display and control method in this solution is characterized by its large size, independent operating system, and network access, thus enabling the display of collaborative information to multiple participants, necessary data transmission with terminal devices, and network connectivity with remote devices, meeting design requirements.

[0023] The interactive flat panel mentioned in this solution can be an integrated device that uses touch technology to control the content displayed on the display flat panel and realize human-computer interaction. It integrates one or more functions such as projector, electronic whiteboard, screen, audio, television and video conferencing terminal.

[0024] Generally, an interactive flat panel includes at least one display screen. For example, an interactive flat panel is equipped with a touch-enabled display screen, which can be a capacitive, resistive, or electromagnetic screen. Users can perform touch operations by touching the display screen with their fingers or a stylus. Correspondingly, the interactive flat panel detects the touch location and responds accordingly to realize the touch function. Typically, an interactive flat panel is equipped with at least one operating system, which includes, but is not limited to, Android, Linux, HarmonyOS, and Windows.

[0025] Interactive whiteboards, primarily designed to support multi-person communication scenarios, utilize software designed to fulfill the functional requirements of such scenarios. For example, an interactive whiteboard can install at least one application with document presentation capabilities. This application can be a pre-installed application on the operating system; alternatively, it may include applications downloaded from third-party devices or servers. Optionally, in addition to displaying pre-edited content, the document presentation application may offer other editing functions during the presentation process, such as inserting tables, images, and graphs, and creating tables and graphs. This allows for real-time display of user information input and the presentation of input content, thereby enhancing the information display and interactive experience during document presentations.

[0026] In the development of computer-assisted conferencing applications, the development may be tailored to specific needs, resulting in a more focused application function, simpler application usage, and a more focused and professional development direction for the development team.

[0027] For example, an application with whiteboard functionality allows users to write, modify, and save in real-time during multi-person collaborative communication scenarios. Multi-person communication based on interactive whiteboards may also require centralizing content files for display during communication on the whiteboard, opening and displaying them one by one, and recording and annotating based on the whiteboard during the communication process. Data generated in such multi-person communication scenarios can be managed through a dedicated application, namely the collaborative application mentioned in this solution. The data managed by the collaborative application is not stored locally on the terminal device, but rather stored and managed through a collaborative server for easy collaborative management and cross-device viewing.

[0028] In multi-person communication scenarios, participants may be located in different spaces, requiring video sharing (including the interactive whiteboard display and the live feed) via remote conferencing. This sharing is achieved through a conferencing application. Of course, conferencing applications can include features such as remote conferencing device management, pre-meeting scheduling, and check-in. Data related to the conferencing application is stored and managed through a conferencing server. It's important to note that "collaboration application" and "conferencing application" are merely exemplary application type definitions and do not represent the actual names of the applications themselves. Applications implementing similar functions can be considered either collaboration or conferencing applications. Interactive whiteboards and conferencing devices are also just exemplary device configurations; the actual installation platform for collaboration and conferencing applications will be the terminal device.

[0029] However, in multi-person communication scenarios, multiple computer-aided conferencing applications may need to be used in combination to meet user needs. For example, in multi-space conferencing scenarios, the conferencing application needs to share the screen, while the collaboration application needs to record conferencing-related data. To ensure the continuity of the meeting process, it is generally undesirable to switch between different applications during the meeting. Existing solutions use a front-end page approach to determine the running status of other applications in order to reduce operation switching. For example, the collaboration application listens for events from other window tabs. When a tab changes from visible to invisible or vice versa, the event is triggered. However, this listening cannot distinguish the source of the event. The collaboration application will also respond if it hears that a window tab outside the conferencing application triggers the event, and this event can only be triggered when the collaboration application's window is completely obscured. The collaboration application and the conferencing application cannot exchange information point-to-point, and the collaboration application cannot accurately determine the running status of the conferencing application. To address the above problems, this invention provides a remote conferencing initiation method to achieve accurate information transmission and accurate status determination between multiple applications during the meeting.

[0030] The embodiments are described in detail below.

[0031] Figure 1 This is a flowchart illustrating a method for initiating a remote conference according to an embodiment of the present invention. This method is used in a terminal device. Please refer to... Figure 2 The diagram shown is a schematic representation of the data transmission and reception process of a remote conference initiation method provided in this embodiment of the invention. Figure 1 As shown, the method for starting a remote meeting includes:

[0032] Step S110: Receive the meeting start command in the window of the collaboration application, and log in to the collaboration server through the user account.

[0033] The window of collaborative application 11 is displayed after the application icon corresponding to collaborative application 11 is triggered and the user logs in with their account. The triggering method in this solution can vary depending on the interactive hardware configuration of the terminal device 10. For example, if the interactive hardware is a touchscreen, a single trigger can be achieved through touch operation or mouse operation; if the interactive hardware is a non-touchscreen, a single trigger can be achieved through a mouse or other touch peripherals (such as a trackball). The triggering method for controls in the window of collaborative application 11 remains basically consistent. User account login can be automatic login after the application icon is triggered, or it can be that the login interface is displayed after the application icon is triggered, and the user logs in with their account on the login interface.

[0034] Depending on the interaction goal, the window of Collaboration Application 11 can present a file management interface involved in the meeting, such as a file list under the current meeting topic, or a remote meeting control interface. The remote meeting control interface can have different remote meeting operation controls, such as a meeting initiation control, a meeting joining control, and a meeting pause control. When the meeting initiation control receives a trigger operation, it confirms that the meeting start instruction has been received.

[0035] Step S120: In response to the meeting start command, the collaboration application requests a meeting code from the meeting server, and the collaboration server and the meeting server connect to each other.

[0036] Collaboration server 20 and conference server 30, as two servers with different data service objects, each perform different data services. Based on user accounts established by the same user within the same or related account system, they can interconnect to synchronize some related data. Specifically, collaboration server 20 can forward remote conference requests from terminal device 10 to conference server 30, and conference server 30 can synchronize the status of the remote conference to collaboration server 20. Collaboration application 11 requests a conference code from conference server 30 through collaboration server 20, and receives the same response as conference application 12 directly requesting a conference code from conference server 30, thus obtaining a conference code used to identify a specific remote conference.

[0037] In practice, if there is no prior meeting reservation, the user account of the collaborative application 11 that requests the meeting code from the meeting server 30 can be set as the host of the remote meeting; if the user account of the collaborative application 11 that requests the meeting code from the meeting server 30 has a prior meeting reservation for the current time period (whether it is the initiator or the reservation recipient), the initiator of the prior meeting reservation can be set as the host of the remote meeting.

[0038] After obtaining the meeting code, it can be further confirmed whether the meeting application 12 is available. If it is available, step S130 is executed; if it is not available, the meeting function built into the collaboration application 11 is used directly to realize the remote meeting. That is, step S120 can also include step S131:

[0039] Step S131: Read the application's installation information. If the installation information does not include the application name of the conferencing application, start the remote conferencing function of the collaboration application according to the conferencing code.

[0040] Collaboration application 11 can also have basic remote conferencing functions. The meeting code provided by meeting server 30 is applicable to the remote conferencing functions of meeting application 12, and can also be used for the remote conferencing functions of collaboration application 11. When the "Initiate Meeting" control in the remote conferencing control interface of collaboration application 11 is triggered, after confirming the receipt of the meeting start command, the application's installation information can be read. If the installation information does not include the application name of meeting application 12, the remote conferencing function of collaboration application 11 itself can be started. Based on the mutual connection between collaboration server 20 and meeting server 30, collaboration application 11 joins the remote meeting according to the meeting code.

[0041] Step S130: Send the meeting code and user account as opening parameters to the meeting application via the page redirection protocol, so that the meeting application can log in to the meeting server through the user account and join the remote meeting according to the meeting code. The user account corresponding to the same user is the same for the collaboration application and the meeting application.

[0042] In the existing account system, terminal device 10 verification is usually required, or authorization registration and login can be performed through a commonly used account. Based on the existing account system, the user accounts of the same user in different applications are usually the same in form (e.g., mobile phone number, ID card number, social application account) or the same in real time (all bound to the same mobile phone number). Based on this similarity, for the same user, the user account of the collaboration application 11 can be directly used as the login account of the meeting application 12.

[0043] When initiating a remote meeting, collaboration application 11 can directly launch meeting application 12 via a page redirection protocol, using the meeting code and user account as launch parameters for meeting application 12. In this page redirection protocol-based launch method, the launch parameters can directly correspond to the parameters required during the launch process and the execution parameters for predetermined operations after launch. That is, meeting application 12 can directly log in to the meeting server 30 using the user account and join the remote meeting using the meeting code after logging in. From the user's perspective, this is equivalent to receiving the meeting launch command in the collaboration application 11 window and directly opening the meeting application 12 window and entering the remote meeting interface. The meeting application 12 window can be displayed independently of the collaboration application 11 window, or it can be displayed in conjunction with the collaboration application 11 window, such as maintaining a snapped border between the two windows or embedding the meeting application 12 window into the collaboration application 11 window.

[0044] Step S140: The collaboration application obtains the meeting status of the user account on the meeting server from the collaboration server and displays the meeting status in the window of the collaboration application. The meeting status is synchronized from the meeting server to the collaboration server.

[0045] Based on the connection between collaboration server 20 and conference server 30, the two can synchronize the status of the ongoing remote conference. Collaboration application 11 obtains the conference status of user accounts on conference server 30 from collaboration server 20, such as conference duration and conference end, and displays the conference status in the window of collaboration application 11. Collaboration application 11 can periodically request the conference status from collaboration server 20, that is, obtain the conference status through polling; or, terminal device 10 can maintain a long socket connection with collaboration server 20, and collaboration server 20 can receive real-time callbacks of the conference status through the long socket connection, that is, obtain the conference status through an information channel.

[0046] In the specific implementation process, before step S110, there is also step S100, in which the configuration between applications is completed.

[0047] Step S100: Obtain the application configuration table, which records the application name and page jump path of the conference application.

[0048] The application configuration table can be configured manually by the user, directly by the backend developers, or configured on a dedicated portal website. The terminal device 10 can obtain the application configuration table generated by any of these methods. The application configuration table can be obtained each time the collaborative application 11 is launched, or it can be obtained and saved to a specified path with a certain validity period. It can be used at any time within the validity period, and it can also be obtained and updated from different channels at any time. The application configuration table records the specific meeting name that is prioritized for opening the meeting application 12, as well as the page jump path for opening the meeting application 12.

[0049] Corresponding to step S100, step S130 includes steps S131 and S132:

[0050] Step S131: Read the application's installation information and confirm that the installation information includes the application name of the conferencing application.

[0051] Step S132: Send the meeting code and user account as opening parameters to the meeting application according to the page redirection protocol and the page redirection path.

[0052] Corresponding to the application configuration table, when executing the process of starting the meeting application 12, the installation information of the application can be read first to confirm that the installation information includes the application name of the meeting application 12. For example, on the Windows terminal device 10, the installed registry will be read. If the meeting application 12 is detected in the registry, it is considered that this application can be opened. On the macOS terminal device 10, the list of applications is checked to see if there is an application name corresponding to the meeting application 12. If it exists, it is considered that it can be opened. After confirming its existence, an attempt is made to open it through a page redirection protocol, and the meeting code and user account are sent as opening parameters to the meeting application 12 according to the page redirection path, thus completing the process of starting the remote meeting.

[0053] During the meeting, after requesting the meeting code from the meeting server 30, the meeting invitation can be implemented through steps S121 and S122.

[0054] Step S121: Receive a meeting invitation in the window of the collaboration application. The meeting invitation indicates that there is at least one target user account.

[0055] The remote conferencing control interface of Collaboration Application 11 can also be configured with a meeting invitation control. When a trigger operation is received on the meeting invitation control, a member list of the organization to which the user account belongs pops up. Each member in the member list corresponds to their own user account. When a selection operation is received on one or more user accounts, it is confirmed that the selected user account is the target user account. When a selection operation is received on one or more user accounts, it is confirmed that a complete meeting invitation operation has been received, and the user account selected in the selection operation is the target user account indicated by the meeting invitation operation.

[0056] Step S122: In response to the meeting invitation operation, send the meeting code to the target user account via the collaboration application.

[0057] In collaboration application 11, as a response to the meeting invitation operation, the meeting code is sent to the target user account via collaboration application 11. If there are multiple target user accounts, it is sent to each target user account accordingly. This allows the corresponding user to join the established remote meeting based on the meeting code.

[0058] For a terminal device 10, the collaboration application 11 may not be the initiator of a remote meeting during use, but rather join an existing remote meeting. The specific joining process is implemented through steps S150 and S160.

[0059] Step S150: Receive the meeting join instruction in the window of the collaboration application. The collaboration application logs into the collaboration server through the user account. The meeting join instruction carries the meeting code.

[0060] Step S160: In response to the meeting join instruction, the meeting code and user account are sent as open parameters to the meeting application via the page redirection protocol, so that the meeting application can log in to the meeting server through the user account and join the remote meeting according to the meeting code.

[0061] The process of joining a remote meeting based on steps S150 and S160 is largely the same as the process of starting a remote meeting based on the previous steps. That is, the collaboration application 11 sends the user account and meeting code to the meeting application 12. The meeting application 12 logs into the meeting server 30 using the user account and joins the remote meeting based on the meeting code. The difference from starting a remote meeting is that the meeting code is not obtained directly from the meeting server 30 by the collaboration server 20, but rather through other means. For example, in the remote meeting control interface, as mentioned earlier, there are controls for initiating a meeting and joining a meeting. When the join meeting control is triggered, an input area is displayed. This input area receives user input and obtains the meeting code that the user knows through other means, such as meeting codes sent by other meeting participants through instant messaging software. In other words, for the collaboration application 11, the meeting code is obtained by receiving input. For example, when the collaborative application 11 in other terminal device 10 executes steps S121 and S122, the collaborative application 11, corresponding to its target user account, receives the meeting code sent via the meeting invitation operation. Upon triggering the link control on the receiving page, it confirms receipt of the meeting join operation and directly sends the meeting code and user account as opening parameters to the meeting application 12. The link control can directly display the meeting code or a prompt to join. The meeting code is recorded at the underlying level and read from the background for sending upon confirmation of receiving the meeting join operation. In other words, for the collaborative application 11, the meeting code is obtained by receiving meeting codes sent by other user accounts.

[0062] It should be noted that the above process is not the complete execution process of the collaboration application 11 and the conferencing application 12 installed on a single terminal device 10 during a meeting. Rather, after installing the collaboration application 11 and the conferencing application 12, a single terminal device 10 can execute different steps according to the needs of the specific meeting scenario to achieve different remote meeting joining methods. For example, if a user of a terminal device 10 is the initiator of a meeting, they can initiate a remote meeting through steps S100-S140 and invite other users to join the remote meeting; if the user is a general participant in another meeting, they can join the remote meeting through steps S150 and S160. The meeting code used to join the remote meeting can be received via email or real-time communication and entered manually, or it can be automatically processed after the collaboration application 11 receives the invitation.

[0063] The above method involves receiving a meeting start command in the collaboration application's window, and then logging into the collaboration server using a user account. In response to the command, the collaboration application requests a meeting code from the conference server, and the collaboration and conference servers connect. Through a page redirection protocol, the meeting code and user account are sent as start parameters to the conference application, allowing it to log into the conference server using the user account and join the remote conference based on the meeting code. The collaboration and conference applications use the same user account. The collaboration application retrieves the meeting status of the user account on the conference server from the collaboration server and displays it in its window. The meeting status is synchronized from the conference server to the collaboration server. By connecting the collaboration and conference servers, the collaboration application obtains meeting-related information generated by the conference server and uses this information as start parameters. When launching the conference application via the page redirection protocol, it directly joins the remote conference based on this information. The collaboration application retrieves the meeting status from the conference server through the collaboration server, enabling it to directly launch the conference application through information transmission and accurately obtain the meeting status during the meeting.

[0064] Figure 3 This is a schematic diagram of the structure of a terminal device provided in an embodiment of the present invention. Figure 3 As shown, the terminal device includes a processor 310, a memory 320, an input device 330, an output device 340, and a communication device 350; the number of processors 310 in the terminal device can be one or more. Figure 3 Taking a processor 310 as an example; the processor 310, memory 320, input device 330, output device 340, and communication device 350 in the terminal device can be connected via a bus or other means. Figure 3 Taking the example of a connection between China and Israel via a bus.

[0065] The memory 320, as a computer-readable storage medium, can be used to store software programs, computer-executable programs, and modules, such as the program instructions / modules corresponding to the remote conference initiation method in this embodiment of the invention. The processor 310 executes various functional applications and data processing of the terminal device by running the software programs, instructions, and modules stored in the memory 320, thereby implementing the aforementioned remote conference initiation method.

[0066] The memory 320 may primarily include a program storage area and a data storage area. The program storage area may store the operating system and applications required for at least one function; the data storage area may store data created based on the use of the terminal device. Furthermore, the memory 320 may include high-speed random access memory and 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 320 may further include memory remotely located relative to the processor 310, which can be connected to the terminal 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.

[0067] Input device 330 can be used to receive input digital or character information, and to generate key signal inputs related to user settings and function control of the terminal device. Output device 340 may include display devices such as a display screen.

[0068] The aforementioned terminal devices can be used to execute any method of starting a remote conference, and have the corresponding functions and beneficial effects.

[0069] This invention also provides a computer-readable storage medium storing a computer program thereon. When the computer program is executed by a processor, it implements the relevant operations in the remote conferencing initiation method provided in any embodiment of this application, and has corresponding functions and beneficial effects.

[0070] Those skilled in the art will understand that embodiments of this application may be provided as methods, systems, or computer program products.

[0071] Therefore, this application may take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code. This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, produce implementations of the flowchart... Figure 1 One or more processes and / or boxes Figure 1The computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The functions specified in one or more boxes. These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable apparatus for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0072] In a typical configuration, a computing device includes one or more processors (CPUs), input / output interfaces, network interfaces, and memory. Memory may include non-persistent memory in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0073] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0074] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0075] Note that the above description is merely a preferred embodiment of the present invention and the technical principles employed. Those skilled in the art will understand that the present invention is not limited to the specific embodiments described herein, and various obvious changes, readjustments, and substitutions can be made without departing from the scope of protection of the present invention. Therefore, although the present invention has been described in detail through the above embodiments, the present invention is not limited to the above embodiments, and may include many other equivalent embodiments without departing from the concept of the present invention, the scope of which is determined by the scope of the appended claims.

Claims

1. A method for initiating a remote meeting, characterized in that, include: The user receives a meeting start command in the window of the collaboration application, which logs into the collaboration server through a user account. In response to the meeting start command, the collaboration application requests a meeting code from the meeting server, and the collaboration server and the meeting server are interconnected. The meeting code and user account are sent as opening parameters to the meeting application via a page redirection protocol, so that the meeting application can log in to the meeting server through the user account and join the remote meeting according to the meeting code. The collaboration application and the meeting application correspond to the same user account. The collaborative application obtains the user account's meeting status on the meeting server from the collaborative server and displays the meeting status in the window of the collaborative application. The meeting status is synchronized from the meeting server to the collaborative server.

2. The remote conference initiation method according to claim 1, characterized in that, Before receiving the meeting start instruction in the window of the collaborative application, the process also includes: Obtain the application configuration table, which records the application name and page navigation path of the meeting application; Correspondingly, the step of sending the meeting code and user account as opening parameters to the meeting application via the page redirection protocol includes: Read the application's installation information and confirm that the installation information includes the application name of the conference application; The meeting code and user account are sent to the meeting application as opening parameters according to the page redirection protocol and the page redirection path.

3. The method for initiating a remote conference according to claim 2, characterized in that, In response to the meeting start command, after requesting a meeting code from the meeting server through the collaboration application, the process further includes: If the installation information of the application is read and it is confirmed that the application name of the meeting application is not included in the installation information, the remote meeting function of the collaboration application is enabled according to the meeting code.

4. The method for initiating a remote conference according to any one of claims 1-3, characterized in that, The meeting status includes meeting in progress and meeting ended.

5. The method for initiating a remote conference according to any one of claims 1-3, characterized in that, In response to the meeting start command, after requesting a meeting code from the meeting server through the collaboration application, the process further includes: The window of the collaboration application receives a meeting invitation operation, which indicates that there is at least one target user account; In response to the meeting invitation operation, the meeting code is sent to the target user account through the collaboration application.

6. The method for initiating a remote conference according to any one of claims 1-3, characterized in that, Also includes: The user receives a meeting join instruction in the window of the collaboration application. The collaboration application logs into the collaboration server through a user account. The meeting join instruction carries a meeting code. In response to the meeting join instruction, the meeting code and user account are sent as open parameters to the meeting application via a page redirection protocol, so that the meeting application can log in to the meeting server through the user account and join the remote meeting according to the meeting code.

7. The method for initiating a remote conference according to claim 6, characterized in that, The meeting code is obtained by receiving input operations or by receiving meeting codes sent by other user accounts.

8. The method for initiating a remote conference according to any one of claims 1-3, characterized in that, The meeting status is obtained through polling or message channels.

9. A terminal device, characterized in that, include: One or more processors; Memory, used to store one or more programs; When the one or more programs are executed by the one or more processors, the terminal device implements the remote conference initiation method as described in any one of claims 1-8.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the remote conference initiation method as described in any one of claims 1-8.

Images