CN115713317A - Conference implementation method, system, storage medium and terminal equipment - Google Patents
Conference implementation method, system, storage medium and terminal equipment Download PDFInfo
- Publication number
- CN115713317A CN115713317A CN202110950249.9A CN202110950249A CN115713317A CN 115713317 A CN115713317 A CN 115713317A CN 202110950249 A CN202110950249 A CN 202110950249A CN 115713317 A CN115713317 A CN 115713317A
- Authority
- CN
- China
- Prior art keywords
- conference
- resident
- interface
- information
- joining request
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Abstract
The embodiment of the invention discloses a conference realization method, a conference realization system, a storage medium and terminal equipment, which are applied to the technical field of communication. When the application terminal starts the current application process or later, a resident conference process is started in advance, so that the current application process displays a conference realization interface, receives a conference joining request through a conference access interface of the conference realization interface, transmits the conference joining request to the resident conference process, and the resident conference process connects a corresponding target conference according to conference information in the conference joining request and displays a conference interface of the target conference. The conference is realized through a resident conference process independent of the current application process, so that the realization of other functions in the current application process is not influenced, and the resident conference process is started in advance and is not started when a conference joining request is initiated, so that the target conference can be quickly connected according to the conference joining request, and the time for connecting the target conference is less.
Description
Technical Field
The present invention relates to the field of communications technologies, and in particular, to a conference implementation method, a conference implementation system, a storage medium, and a terminal device.
Background
The enterprise WeChat is a communication and office tool developed for each enterprise, communication among employees in the enterprise can be facilitated through the enterprise WeChat, and functions related to enterprise management in the enterprise WeChat, such as functions of meetings, check-in, employee self-help, regulations and regulations, are continuously improved.
The conference function in the enterprise WeChat can realize live conference among enterprise employees in real time, but the conference function needs to carry out real-time video communication, and consumed resources are more, so that the enterprise WeChat can influence other function realization of the enterprise WeChat when the conference function is realized.
Disclosure of Invention
The embodiment of the invention provides a conference realization method, a conference realization system, a storage medium and terminal equipment, thereby isolating the realization of a conference function and other functions.
An embodiment of the present invention provides a conference implementation method, including:
displaying a conference implementation interface, wherein the conference implementation interface comprises a conference access interface;
receiving a conference joining request through the conference access interface, wherein the conference joining request comprises conference information of a target conference;
if a resident conference process is pre-started currently, transmitting the conference joining request to the resident conference process so that the resident conference process executes the following steps:
and connecting a corresponding target conference according to the conference information in the conference joining request, and displaying a conference interface of the target conference.
Another aspect of the embodiments of the present invention provides a conference implementation system, including:
the interface display unit is used for displaying a conference realization interface, and the conference realization interface comprises a conference access interface;
the conference request unit is used for receiving a conference joining request through the conference access interface, wherein the conference joining request comprises conference information of a target conference;
a request transmitting unit, configured to transmit, if a resident conference process is pre-started currently, the conference joining request to the resident conference process, so that the resident conference process performs the following steps: and connecting a corresponding target conference according to the conference information in the conference joining request, and displaying a conference interface of the target conference.
In another aspect, an embodiment of the present invention further provides a computer-readable storage medium, where the computer-readable storage medium stores a plurality of computer programs, and the computer programs are adapted to be loaded by a processor and execute a conference implementation method according to an aspect of an embodiment of the present invention.
In another aspect, an embodiment of the present invention further provides a terminal device, including a processor and a memory;
the memory is used for storing a plurality of computer programs, and the computer programs are used for being loaded by the processor and executing the conference realizing method according to the aspect of the embodiment of the invention; the processor is configured to implement each of the plurality of computer programs.
It can be seen that, in the method of this embodiment, when the application terminal starts the current application process or after the current application process, a resident conference process is pre-started, so that the current application process displays a conference implementation interface, receives a conference joining request through a conference access interface of the conference implementation interface, transmits the conference joining request to the resident conference process, and connects a corresponding target conference according to conference information in the conference joining request by the resident conference process, and displays a conference interface of the target conference. The conference is realized through a resident conference process independent of the current application process, so that the realization of other functions in the current application process is not influenced, and the resident conference process is started in advance and is not started when a conference joining request is initiated, so that the target conference can be quickly connected according to the conference joining request, and the time for connecting the target conference is less.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the embodiments or the description of the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
Fig. 1 is a schematic diagram of a conference implementation method provided in an embodiment of the present invention;
fig. 2 is a flowchart of a conference implementation method according to an embodiment of the present invention;
FIG. 3a is a schematic diagram of a conference implementation interface displayed by a current application process in one embodiment of the present invention;
FIG. 3b is a diagram illustrating a setting interface of a conference to be created displayed by a current application process in an embodiment of the present invention;
FIG. 3c is a diagram illustrating a meeting details interface of a reserved meeting displayed by a current application process in accordance with an embodiment of the present invention;
FIG. 3d is a diagram of a user input interface displayed by a current application process in one embodiment of the invention;
FIG. 4 is a flowchart of a method for pre-starting a resident conference process in an application embodiment of the present invention;
FIG. 5 is a flow chart of a method for joining a conference in an embodiment of the present invention;
FIG. 6 is a schematic diagram of a distributed system to which a conference implementation method is applied in another embodiment of the present invention;
FIG. 7 is a block diagram illustrating an exemplary block structure according to another embodiment of the present invention;
fig. 8 is a schematic logical structure diagram of a conference implementation system according to an embodiment of the present invention;
fig. 9 is a schematic logical structure diagram of a terminal device according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
The terms "first," "second," "third," "fourth," and the like in the description and in the claims, as well as in the drawings, if any, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the invention described herein are, for example, capable of operation in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
The embodiment of the invention provides a conference implementation method, which is mainly applied to any application terminal with a conference function, such as an enterprise WeChat application terminal and the like, and as shown in FIG. 1, the application terminal can implement a conference according to the following steps:
displaying a conference implementation interface, wherein the conference implementation interface comprises a conference access interface;
receiving a conference joining request through the conference access interface, wherein the conference joining request comprises conference information of a target conference;
if a resident conference process is pre-started currently, transmitting the conference joining request to the resident conference process so that the resident conference process executes the following steps:
and connecting a corresponding target conference according to the conference information in the conference joining request, and displaying a conference interface of the target conference.
Therefore, the realization of the conference is carried out through the resident conference process independent of the current application process, so that the realization of other functions in the current application process is not influenced, and the resident conference process is started in advance and is not started when a conference joining request is initiated, so that the target conference can be quickly connected according to the conference joining request, and the time cost for connecting the target conference is less.
An embodiment of the present invention provides a conference implementation method, which is a method executed by an application terminal, and a flowchart is shown in fig. 2, where the method includes:
It can be understood that the user may operate the application terminal, so that the application terminal starts the current application process, and the current application process displays the conference implementation interface, where the conference implementation interface may include a conference access interface, through which the user may connect to the conference and view the conference video or the conference audio.
Further, the meeting implementation interface may further include a meeting pre-creation interface for creating a new meeting in advance, when the user operates the meeting pre-creation interface, the current application process responds to the operation of the meeting pre-creation interface and displays a user input interface, and the user may input meeting information of the pre-creation meeting, such as information of meeting attendees, meeting time, meeting content, and the like, on the user input interface; therefore, the current application process receives the conference information input from the user input interface, determines the conference identifier corresponding to the input conference information, associates the conference identifier with the input conference information to obtain the associated conference information, and then transmits the associated conference information to the pre-started resident conference process for storage.
It should be noted that, in the embodiment of the present invention, in order to enable the application terminal to implement the conference function without affecting other function implementations of the application terminal, the implementation of the conference function and other functions is separated by two processes, specifically, the conference function is implemented by a resident application process, and the other functions of the application terminal are implemented by a current application process.
In a specific implementation, the application terminal starts the resident conference process at the same time of starting the current application process or after the current application process is started, and transmits the created first conference information to the resident conference process through the current application process. The resident conference process is started in advance instead of waiting for the user to initiate the conference joining request by operating the application terminal at the same time when the current application process is started or at any time after the current application process is started, so that the user can enter the conference quickly and watch the conference video or the conference audio when initiating the conference joining request.
And 102, receiving a conference joining request through a conference access interface, wherein the conference joining request comprises conference information of a target conference. The target conference refers to a conference requested to be joined by the conference joining request, and the conference information may include a conference identifier, and may also include information such as conference personnel, conference time, and conference content.
Specifically, receiving the conference join request through the conference access interface may include, but is not limited to, the following two cases:
(1) The conference access interface is a first interface for accessing a conference to be created.
When a user operates the first interface, the current application process responds to the operation of the first interface, and displays a setting interface of the conference to be created, wherein the setting interface comprises a setting interface and a conference connection interface, so that the user can set conference information of the conference to be created through the setting interface, such as information of conference participants, conference contents and the like, and the current application process receives the conference information of the conference to be created, which is input by the user, from the setting interface; when a user operates the conference connection interface, the current application process responds to the operation of the conference connection interface and receives a conference joining request, and the conference information of the target conference included in the conference joining request is the conference information of the conference to be created, which is set by the user through the setting interface.
(2) The conference access interface is a second interface for accessing the created conference.
When a user operates the second interface, the current application process responds to the operation of the second interface and receives a conference joining request, wherein the conference information of the target conference included in the conference joining request is a conference identifier of the created conference; when a conference joining request sent by the current application process is received after the resident conference process, other conference information of the created conference can be found according to the conference identifier of the created conference included in the conference joining request, and the corresponding created conference is connected according to the found conference information and the conference identifier.
The conference information of the created conference is sent to the resident conference process for storage in the process of starting the resident conference process by the current application process, so that when the current application process initiates a conference joining request through the second interface, only the conference identifier of the created conference is carried in the conference joining request and is transmitted to the resident conference process, and the resident conference process can find other conference information of the created conference through the conference identifier.
If the resident conference process is not started currently, the resident conference process needs to be started first, and then the conference joining request is transmitted to the resident conference process. The resident conference process is a process for taking charge of the current application terminal to join the conference, and keeping the current application terminal online in the conference, and the like, and realizing the functions related to the conference.
For example, the conference implementation interface shown in fig. 3a includes an "instant conference" button, a "conference reservation" button, and a reserved conference list, where the "instant conference" button is the first interface, the "conference reservation" button is the conference pre-creation interface, the conference list includes conference identifiers of 3 reserved conferences, and a conference identifier of each reserved conference is the second interface.
As shown in fig. 3b, when the user clicks the "instant conference on" button, the current application process first displays a setting interface of the conference to be created, where the setting interface includes a plurality of (n are illustrated in the figure as examples) setting interfaces of the conference information and a "enter confirmation" button (i.e., the conference connection interface), where the setting interfaces are input frames of the respective conference information, the user inputs a plurality of conference information of the conference to be created through the setting interfaces, and clicks the "enter confirmation" button, and then the current application process carries the conference information of the conference to be created, which is input by the user, in the conference join request, and transmits the conference join request to the resident conference process.
When a user clicks a conference identifier of a reserved conference, for example, clicks a reserved conference 1, the current application process receives a conference joining request and transmits the conference joining request to the resident conference process. Or, when the user clicks a meeting identifier of a reserved meeting, the current application process may first display a meeting detail interface of the reserved meeting as shown in fig. 3c, where the meeting detail interface may include user information (i.e., user a) initiating the meeting, time of the reserved meeting, and meeting type (voice or video type), and the meeting detail interface may further include a "enter meeting" button and a "share" button, and when the user clicks the "enter meeting" button, the current application process receives a meeting join request of the reserved meeting and transmits the meeting join request to the resident meeting process; when the user clicks the "share" button, the current application process sends the conference information of the reserved conference to other users.
As shown in fig. 3d, when the user clicks the "reserve meeting" button, the current application process displays a user input interface, the user can input meeting information of the pre-created meeting, such as information of meeting attendees, meeting time, meeting content and the like, on the user input interface, and the "confirm reservation" button is further included in the user input interface. Therefore, when a user inputs each conference information of the pre-established conference through the user input interface and clicks the 'confirm reservation' button, the current application process can confirm the conference identifier corresponding to the input conference information, associate the conference identifier with the input conference information to obtain the associated conference information, and then transmit the associated conference information to the pre-started resident conference process for storage. Further, the current application process puts the created meeting into a meeting list of a meeting implementation interface for displaying.
Further, after the application terminal starts the current application process and the resident conference process, since the current application process and the resident conference process are isolated and not affected with each other, the resident conference process can be monitored in real time through the current application process, which may specifically include but is not limited to monitoring in several ways as follows:
(1) The current application process determines a startup state for starting the resident conference process.
Specifically, when the current application process is started successfully in the process of starting the resident conference process, the resident conference process feeds back a starting state of successful starting to the current application process; when the abnormal starting is caused by the starting abnormity or the starting overtime and the like, the current application process does not receive the starting state of successful starting fed back by the resident conference process within the preset time for starting the resident conference process, and the resident conference process is restarted when the starting state of the resident conference process is determined to be the unsuccessful starting of the resident conference process.
(2) The current application process determines that the resident conference process is connected with the first state of the target conference.
Specifically, in the process of connecting the resident conference process to the target conference according to the conference joining request, the first state of unsuccessful connection, successful connection or connection timeout may be returned to the current application process, and if the first state indicates that the resident conference process is abnormally connected to the target conference or the connection target conference is timeout, the current application process retransmits the conference joining request to the resident conference process, so that the resident conference process reconnects the target conference.
(3) And the current application process determines the second state of the resident conference process sent by the resident conference process.
Specifically, the second state of the resident conference process is determined to be the resident conference process exception, and the resident conference process is restarted, wherein the resident conference process exception refers to the resident conference process jamming or the network connection exception.
(4) The current application process determines a communication state between the current application process and the resident conference process.
Specifically, the resident conference process sends a heartbeat signal to the current application process according to a certain period, the current application process returns a heartbeat response to the resident conference process, and if the current application process does not receive the heartbeat signal within a period of time, it is determined that the communication state between the resident conference process and the current application process indicates that the communication between the current application process and the resident conference process is abnormal, and the resident conference process needs to be restarted.
It can be seen that, in the method of this embodiment, when the application terminal starts the current application process or after the current application process, a resident conference process is pre-started, so that the current application process displays a conference implementation interface, receives a conference joining request through a conference access interface of the conference implementation interface, transmits the conference joining request to the resident conference process, and connects a corresponding target conference according to conference information in the conference joining request by the resident conference process, and displays a conference interface of the target conference. The conference is realized through a resident conference process independent of the current application process, so that the realization of other functions in the current application process is not influenced, and the resident conference process is started in advance and is not started when a conference joining request is initiated, so that the target conference can be quickly connected according to the conference joining request, and the time spent on connecting the target conference is less.
In this embodiment, the application terminal is specifically an enterprise wechat application terminal, and the current application process started by the enterprise wechat application terminal is an enterprise wechat process, which specifically includes the following two processes:
as shown in fig. 4, the enterprise wechat application terminal may pre-start the resident conference process according to the following steps:
The enterprise wechat process is used for realizing other functions except the conference function in the enterprise wechat, and the resident conference process is used for realizing the conference function.
Specifically, if the enterprise wechat process receives the feedback of the resident conference process and successfully receives the first conference information, the starting state of the resident conference process is normal starting, and the resident conference process does not need to be restarted; if the enterprise wechat process receives the feedback of the resident conference process, that is, the first conference information is not successfully received, or the feedback of the resident conference process is received overtime (that is, the feedback is not received within a period of time after the enterprise wechat process sends the first conference information), the starting state of the resident conference process is abnormal starting, and the resident conference process needs to be restarted.
It should be noted that, in the above steps 201 to 203, the resident conference process is started after the enterprise wechat process is started, and in another specific implementation, the resident conference process may be started while the enterprise wechat application terminal starts the enterprise wechat process.
(II) as shown in FIG. 5, the enterprise WeChat application terminal may initiate a conference start resident conference process according to the following steps:
step 301, the user operates the enterprise wechat application terminal, so that the started enterprise wechat process may display a conference implementation interface, where the conference implementation interface may include a conference access interface, and a specific implementation form of the conference access interface is as described in the foregoing embodiments, which is not described herein again.
Step 302, a user initiates a conference joining request by operating a conference access interface of a conference realization interface, and the enterprise wechat process receives the conference joining request, wherein the conference joining request includes conference information of a target conference.
It should be noted that, after the enterprise wechat process receives the conference joining request, it may be determined whether the resident conference process is pre-started at present, and if the resident conference process is started, the following step 303 may be directly performed; if not, the resident conference process needs to be started first, and then the following step 303 is executed.
And 303, the enterprise wechat process transmits the conference joining request to a pre-started resident conference process, and the resident conference process connects a corresponding target conference according to the conference joining request and displays a conference interface of the target conference.
Step 304, the resident conference process feeds back information whether the target conference is successfully connected to the enterprise wechat process, the enterprise wechat process determines a first state that the resident conference process is connected to the target conference according to the feedback of the resident conference process, and determines whether a conference joining request needs to be retransmitted to the resident conference process based on the first state.
Specifically, if the resident conference process feedback received by the enterprise wechat process is that the target conference is successfully connected, determining that the first state indication is normal when the target conference is connected, and not transmitting a conference joining request again; if the resident conference process feedback received by the enterprise wechat process indicates that the target conference is not successfully connected, or the resident conference process feedback is not received within a period of time after the enterprise wechat process transmits the conference joining request, it is determined that the first state indication is abnormal when the target conference is connected, and the conference joining request needs to be retransmitted.
And 305, the resident conference process sends a heartbeat signal to the enterprise WeChat process according to a certain period in the process of connecting the target conference, the enterprise WeChat process returns a heartbeat response, the enterprise WeChat process determines the communication state between the resident conference process and the enterprise WeChat according to the heartbeat signal sent by the resident conference process, and determines whether the resident conference process needs to be restarted or not based on the communication state.
Specifically, when the enterprise wechat process does not receive the heartbeat signal sent by the resident conference process within a period of time, it is determined that the communication state indicates that the communication between the resident conference process and the enterprise wechat is abnormal, and the resident conference process needs to be restarted.
It should be noted that, the data structure for communication between the enterprise wechat process and the resident conference process can be represented by the following codes in table 1:
TABLE 1
And the data structure of the conference join request initiated by the enterprise wechat process may be represented by the following code in table 2:
TABLE 2
Therefore, in the embodiment, based on the complexity of the conference implementation, the implementation of the conference function is isolated from the implementation of other functions in the enterprise wechat application terminal through the resident conference process and the enterprise wechat process, and the process of implementing the conference function through the resident conference process is monitored through the enterprise wechat process, so that the stability of implementing the conference function and implementing other functions is ensured.
The conference implementation method in the present invention is described below with another specific application example, the conference implementation system in the embodiment of the present invention is mainly a distributed system 100, the distributed system may include a client 300 and a plurality of nodes 200 (any form of computing devices in an access network, such as servers and user terminals), and the client 300 and the nodes 200 are connected in a network communication manner.
Taking a distributed system as an example of a blockchain system, fig. 6 is an optional structural schematic diagram of the application of the distributed system 100 To the blockchain system, which is provided by the embodiment of the present invention, and is formed by a plurality of nodes 200 (any form of computing devices in an access network, such as servers and user terminals) and a client 300, a point-To-point (P2P) network is formed between the nodes, and the P2P Protocol is an application layer Protocol running on a Transmission Control Protocol (TCP). In a distributed system, any machine, such as a server or a terminal, can join to become a node, and the node comprises a hardware layer, a middle layer, an operating system layer and an application layer.
Referring to the functions of each node in the block chain system shown in fig. 6, the related functions include:
1) Routing, a basic function that a node has, is used to support communication between nodes.
Besides the routing function, the node can also have the following functions:
2) The application is used for being deployed in a block chain, realizing specific services according to actual service requirements, recording data related to the realization function to form recording data, carrying a digital signature in the recording data to represent a source of task data, and sending the recording data to other nodes in the block chain system, so that the other nodes add the recording data to a temporary block when the source and integrity of the recording data are verified successfully.
For example, the service implemented by the application includes a code implementing a conference implementation function, and the conference implementation function mainly includes:
displaying a conference implementation interface, wherein the conference implementation interface comprises a conference access interface; receiving a conference joining request through the conference access interface, wherein the conference joining request comprises conference information of a target conference; if a resident conference process is pre-started currently, transmitting the conference joining request to the resident conference process so that the resident conference process executes the following steps: and connecting a corresponding target conference according to the conference information in the conference joining request, and displaying a conference interface of the target conference.
3) And the Block chain comprises a series of blocks (blocks) which are mutually connected according to the generated chronological order, new blocks cannot be removed once being added into the Block chain, and recorded data submitted by nodes in the Block chain system are recorded in the blocks.
Referring to fig. 7, an optional schematic diagram of a Block Structure (Block Structure) provided in the embodiment of the present invention is shown, where each Block includes a hash value of a transaction record stored in the Block (hash value of the Block) and a hash value of a previous Block, and the blocks are connected by the hash values to form a Block chain. The block may also include information such as a time stamp at the time of block generation. A block chain (Blockchain), which is essentially a decentralized database, is a string of data blocks associated by using cryptography, and each data block contains related information for verifying the validity (anti-counterfeiting) of the information and generating a next block.
An embodiment of the present invention further provides a conference implementation system, for example, the above-mentioned enterprise wechat application terminal, and a schematic structural diagram of the conference implementation system is shown in fig. 8, and specifically, the conference implementation system may include:
and the interface display unit 10 is configured to display a conference implementation interface, where the conference implementation interface includes a conference access interface.
A conference request unit 11, configured to receive a conference join request through the conference access interface displayed by the interface display unit 10, where the conference join request includes conference information of a target conference.
A request transmitting unit 12, configured to transmit, if a resident conference process is pre-started currently, the conference join request received by the conference requesting unit 11 to the resident conference process, so that the resident conference process performs the following steps: and connecting a corresponding target conference according to the conference information in the conference joining request, and displaying a conference interface of the target conference.
In a specific implementation, if the conference access interface is a first interface for accessing a conference to be created, the conference request unit 11 is specifically configured to respond to an operation on the first interface and display a setting interface of the conference to be created, where the setting interface includes a setting interface and a conference connection interface; receiving conference information of the conference to be created, which is input by a user, from the setting interface; and responding to the operation of the conference connection interface, receiving the conference joining request, wherein the conference information of the target conference included in the conference joining request is the conference information of the conference to be created.
In another specific implementation, if the conference access interface is a second interface for accessing a created conference, the conference request unit 11 is specifically configured to receive the conference join request in response to an operation on the second interface, where conference information of a target conference included in the conference join request is a conference identifier of the created conference; therefore, when the resident conference process is connected with the corresponding target conference according to the conference information in the conference joining request, other conference information of the created conference is found according to the conference identifier of the created conference, and the corresponding created conference is connected according to the conference identifier and the found conference information.
Further, the conference implementation system of this embodiment may further include:
a conference creating unit 13, configured to enable the conference implementation interface displayed by the interface display unit 10 to further include: a conference pre-creation interface that displays a user input interface in response to an operation on the conference pre-creation interface; when meeting information input from the user input interface is received, a meeting identifier corresponding to the input meeting information is determined; associating the conference identifier with the input conference information to obtain associated conference information; and transmitting the associated conference information to the resident conference process for storage.
And the pre-starting unit 14 is configured to start the resident conference process while the current application process is started or after the current application process is started, and transmit the created first conference information to the resident conference process through the current application process. The request transmitting unit 12 transmits the conference join request to the pre-start unit 14 to pre-start the resident conference process.
The monitoring unit 15 is configured to determine a starting state for starting the resident conference process; and if the starting state indicates that the resident conference process is not started successfully, restarting the resident conference process.
The monitoring unit 15 is further configured to determine a first state of the resident conference process connecting with the target conference; if the first state indicates that the resident conference process is not successfully connected to the target conference or the connection to the target conference is overtime, the conference joining request is retransmitted to the resident conference process so that the resident conference process is connected to the target conference again.
The monitoring unit 15 is further configured to determine a second state of the resident conference process sent by the resident conference process, and restart the resident conference process if the second state indicates that the resident conference process is abnormal.
The monitoring unit 15 is further configured to determine a communication state between the current application process and the resident conference process; and restarting the resident conference process if the communication state indicates that the communication between the current application process and the resident conference process is abnormal.
As can be seen, in the conference implementation system of this embodiment, the implementation of the conference is performed through a resident conference process independent of the current application process, which does not affect the implementation of other functions in the current application process, and since the resident conference process is started in advance and is not started when the conference join request is initiated, the target conference can be quickly connected according to the conference join request, and the time spent on connecting the target conference is relatively small.
The present invention further provides a terminal device, a schematic structural diagram of which is shown in fig. 9, where the terminal device may generate a relatively large difference due to different configurations or performances, and may include one or more Central Processing Units (CPUs) 20 (e.g., one or more processors) and a memory 21, and one or more storage media 22 (e.g., one or more mass storage devices) storing the application programs 221 or the data 222. Wherein the memory 21 and the storage medium 22 may be a transient storage or a persistent storage. The program stored in the storage medium 22 may include one or more modules (not shown), each of which may include a series of instruction operations for the terminal device. Still further, the central processor 20 may be configured to communicate with the storage medium 22 to execute a series of instruction operations in the storage medium 22 on the terminal device.
Specifically, the application programs 221 stored in the storage medium 22 include application programs for implementing a conference, and the programs may include the interface display unit 10, the conference request unit 11, the request transmission unit 12, the conference creation unit 13, the pre-start unit 14, and the monitoring unit 15 in the conference implementation system, which will not be described in detail herein. Further, the central processor 20 may be configured to communicate with the storage medium 22, and execute a series of operations corresponding to the conference-implemented application stored in the storage medium 22 on the terminal device.
The terminal equipment may also include one or more power supplies 23, one or more wired or wireless network interfaces 24, one or more input-output interfaces 25, and/or one or more operating systems 223, such as Windows Server, mac OS XTM, unixTM, linuxTM, freeBSDTM, and the like.
The steps executed by the conference implementing system described in the above method embodiment may be based on the structure of the terminal device shown in fig. 9.
In another aspect, an embodiment of the present invention further provides a computer-readable storage medium, where the computer-readable storage medium stores a plurality of computer programs, and the computer programs are adapted to be loaded by a processor and execute a conference implementation method executed by the conference implementation system.
In another aspect, an embodiment of the present invention further provides a terminal device, including a processor and a memory;
the memory is used for storing a plurality of computer programs, and the computer programs are used for being loaded by the processor and executing the conference realizing method executed by the conference realizing system; the processor is configured to implement each of the plurality of computer programs.
According to an aspect of the application, a computer program product or computer program is provided, comprising computer instructions, the computer instructions being stored in a computer readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the conference implementation method provided in the above-mentioned various alternative implementations.
Those skilled in the art will appreciate that all or part of the steps in the methods of the above embodiments may be implemented by associated hardware instructed by a program, which may be stored in a computer-readable storage medium, and the storage medium may include: read Only Memory (ROM), random Access Memory (RAM), magnetic or optical disks, and the like.
The method, system, storage medium and terminal device for implementing a conference provided by the embodiments of the present invention are described in detail above, and a specific example is applied in the description to explain the principle and the implementation of the present invention, and the description of the above embodiments is only used to help understanding the method and the core idea of the present invention; meanwhile, for a person skilled in the art, according to the idea of the present invention, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present invention.
Claims (10)
1. A conference implementation method, comprising:
displaying a conference implementation interface, wherein the conference implementation interface comprises a conference access interface;
receiving a conference joining request through the conference access interface, wherein the conference joining request comprises conference information of a target conference;
if a resident conference process is pre-started currently, transmitting the conference joining request to the resident conference process so that the resident conference process executes the following steps:
and connecting a corresponding target conference according to the conference information in the conference joining request, and displaying a conference interface of the target conference.
2. The method of claim 1, wherein if the conference access interface is a first interface accessing a conference to be created, the receiving a conference join request through the conference access interface specifically includes:
responding to the operation of the first interface, and displaying a setting interface of the conference to be created, wherein the setting interface comprises a setting interface and a conference connection interface;
receiving conference information of the conference to be created, which is input by a user, from the setting interface;
and responding to the operation of the conference connection interface, receiving the conference joining request, wherein the conference information of the target conference included in the conference joining request is the conference information of the conference to be created.
3. The method of claim 1, wherein if the conference access interface is a second interface accessing a created conference, the receiving a conference join request through the conference access interface specifically comprises:
responding to the operation of the second interface, receiving the conference joining request, wherein the conference information of the target conference included in the conference joining request is the conference identifier of the established conference;
the resident conference process connects a corresponding target conference according to the conference information in the conference joining request, and specifically includes:
and the resident conference process finds out other conference information of the created conference according to the conference identifier of the created conference, and connects the corresponding created conference according to the conference identifier and the found conference information.
4. The method of claim 1, wherein the meeting fulfillment interface further comprises: a conference pre-creation interface, the method further comprising:
responding to the operation of the conference pre-creation interface, and displaying a user input interface;
when meeting information input from the user input interface is received, a meeting identifier corresponding to the input meeting information is determined;
associating the conference identifier with the input conference information to obtain associated conference information;
and transmitting the associated conference information to the resident conference process for storage.
5. The method of any of claims 1 to 4, wherein prior to transmitting the conference join request to the resident conference process, further comprising:
and starting the resident conference process at the same time of starting the current application process or after the current application process is started, and transmitting the created first conference information to the resident conference process through the current application process.
6. The method of any of claims 1 to 4, further comprising:
determining a first state of the resident conference process connecting with the target conference;
and if the first state indicates that the resident conference process is abnormally connected to the target conference or the connection of the resident conference process to the target conference is overtime, the conference joining request is retransmitted to the resident conference process, so that the resident conference process is conveniently and reconnected to the target conference.
7. The method of any one of claims 1 to 4,
determining a second state of the resident conference process sent by the resident conference process,
if the second state of the resident conference process sent by the resident conference process indicates that the resident conference process is abnormal, restarting the resident conference process;
or restarting the resident conference process if the communication state between the current application process and the resident conference process indicates that the communication between the current application process and the resident conference process is abnormal;
or if the starting state of the resident conference process indicates that the resident conference process is not started successfully, restarting the resident conference process.
8. A conference effectuating system, comprising:
the interface display unit is used for displaying a conference realization interface, and the conference realization interface comprises a conference access interface;
the conference request unit is used for receiving a conference joining request through the conference access interface, wherein the conference joining request comprises conference information of a target conference;
a request transmitting unit, configured to transmit, if a resident conference process is pre-started currently, the conference joining request to the resident conference process, so that the resident conference process performs the following steps: and connecting a corresponding target conference according to the conference information in the conference joining request, and displaying a conference interface of the target conference.
9. A computer-readable storage medium, characterized in that it stores a plurality of computer programs adapted to be loaded by a processor and to execute the conference realization method of any of claims 1 to 7.
10. A terminal device comprising a processor and a memory;
the memory is used for storing a plurality of computer programs, the computer programs are used for being loaded by the processor and executing the conference realizing method as claimed in any one of claims 1 to 7; the processor is configured to implement each of the plurality of computer programs.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110950249.9A CN115713317A (en) | 2021-08-18 | 2021-08-18 | Conference implementation method, system, storage medium and terminal equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110950249.9A CN115713317A (en) | 2021-08-18 | 2021-08-18 | Conference implementation method, system, storage medium and terminal equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115713317A true CN115713317A (en) | 2023-02-24 |
Family
ID=85229992
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110950249.9A Pending CN115713317A (en) | 2021-08-18 | 2021-08-18 | Conference implementation method, system, storage medium and terminal equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115713317A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116405339A (en) * | 2023-06-07 | 2023-07-07 | 北京伍拾陆度科技有限公司 | Remote conference management method and system for enterprise service |
-
2021
- 2021-08-18 CN CN202110950249.9A patent/CN115713317A/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116405339A (en) * | 2023-06-07 | 2023-07-07 | 北京伍拾陆度科技有限公司 | Remote conference management method and system for enterprise service |
| CN116405339B (en) * | 2023-06-07 | 2023-08-11 | 北京伍拾陆度科技有限公司 | Remote conference management method and system for enterprise service |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7203755B2 (en) | System and method for application sharing in collaborative setting | |
| US6901448B2 (en) | Secure communications system for collaborative computing | |
| US7461347B2 (en) | Distributed document sharing | |
| US7484115B2 (en) | Fault-tolerant server for collaborative computing | |
| US7523163B2 (en) | Distributed network system architecture for collaborative computing | |
| US6567813B1 (en) | Quality of service maintenance for distributed collaborative computing | |
| US6925645B2 (en) | Fault tolerant server architecture for collaborative computing | |
| US7069298B2 (en) | Fault-tolerant distributed system for collaborative computing | |
| EP2712119B1 (en) | Abnormality handling method, device and client | |
| US20030167304A1 (en) | Distributed meeting management | |
| US20030167302A1 (en) | Scalable distributed network system for collaborative computing | |
| JP2005216313A (en) | System and method for session reestablishment between client terminal and server | |
| KR101996624B1 (en) | Binding crud-type protocols in distributed agreement protocols | |
| WO2008077816A1 (en) | Method and system for resource-based synchronization between endpoints in a web-based real time collaboration | |
| US20060161651A1 (en) | Managing resources within a fault tolerant collaboration system | |
| CN114070733A (en) | Consensus method, device and system based on block chain network | |
| CN114422460A (en) | Method and system for establishing same-screen communication sharing in instant messaging application | |
| CN109474759B (en) | Information processing method, device and storage medium | |
| CN115713317A (en) | Conference implementation method, system, storage medium and terminal equipment | |
| CN108874947B (en) | Data processing system and data processing method | |
| CN113626002A (en) | Service execution method and device | |
| CN110401809B (en) | Method and device for forcibly stopping video networking conference | |
| JP4224037B2 (en) | Service providing method and data processing apparatus | |
| CN110971669B (en) | Message notification method, device, server, electronic equipment and readable storage medium | |
| JP2006059321A (en) | Session maintenance method in distributed object environment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |