CN112291371A - Conference message real-time synchronization method, system, device and storage medium - Google Patents
Conference message real-time synchronization method, system, device and storage medium Download PDFInfo
- Publication number
- CN112291371A CN112291371A CN202011574335.6A CN202011574335A CN112291371A CN 112291371 A CN112291371 A CN 112291371A CN 202011574335 A CN202011574335 A CN 202011574335A CN 112291371 A CN112291371 A CN 112291371A
- Authority
- CN
- China
- Prior art keywords
- conference
- message
- client
- server
- change
- 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.)
- Granted
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
- H04L67/141—Setup of application sessions
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/16—Arrangements for providing special services to substations
- H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
- H04L12/1813—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast for computer conferences, e.g. chat rooms
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/16—Arrangements for providing special services to substations
- H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
- H04L12/185—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast with management of multicast group membership
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/55—Push-based network services
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- General Engineering & Computer Science (AREA)
- Multimedia (AREA)
- Information Transfer Between Computers (AREA)
- Telephonic Communication Services (AREA)
Abstract
The embodiment of the invention discloses a method for synchronizing conference messages in real time, which comprises the following steps: the server receives handshake messages sent by the client and establishes connection with the client; the method comprises the steps of sending a subscription message to a conference platform end, receiving a conference change message sent by the conference platform end, and pushing the conference change message to a client, wherein the conference change message is generated and sent by the conference platform end after the conference platform end receives changes of conference participants. The invention also discloses a conference message real-time synchronization system, a conference message real-time synchronization device and a conference message real-time synchronization storage medium. The invention can effectively reduce resource consumption, improve communication efficiency and completely display messages.
Description
Technical Field
The present invention relates to the field of message transmission, and in particular, to a method, a system, a device, and a storage medium for real-time synchronization of conference messages.
Background
The traditional mode brings obvious disadvantages that the browser needs to send requests to the server continuously, however, the HTTP request may contain a long header, wherein the really effective data may be only a small part, and obviously, much bandwidth and other resources are wasted.
By adopting a polling mechanism, even if the polling mechanism is carried out every 3 seconds, the transmission of the message is delayed, the real state cannot be obtained in real time, and the data can be updated only after 3 seconds of delay, so that the use monitoring of the client is influenced.
Disclosure of Invention
In view of this, the present invention provides a method for synchronizing conference messages in real time, which is used to solve the problems of resource waste and low efficiency in the prior art.
A conference message real-time synchronization method comprises the following steps: the server receives handshake messages sent by the client and establishes connection with the client; receiving a conference change message sent by a conference platform end, and pushing the conference change message to the client, wherein the conference change message is generated and sent by the conference platform end after receiving the change of conference participants.
Wherein the step of establishing a connection with the client comprises: and receiving a conference request message sent by the client, and sending the conference request message to the conference platform end, so that the conference platform end starts a conference according to the conference request message.
Wherein the conference request message includes a request type, the request type including: at least one of a conference reservation, a request to mute outbound participants into a conference, a request to lock a conference, a request to record a conference, a request to mute participants, or a request to hang up.
A conference message real-time synchronization method comprises the following steps: a conference platform end receives a conference operation message sent by a conference participant; and generating a conference change message according to the conference operation message, and pushing the conference change message to a server side so that the server side pushes the conference change message to the client side.
Wherein the conference operation message comprises an operation type, and the operation type comprises: actively dialing at least one of a meeting, muting the telephone terminal, canceling the muting, raising a question and answer at the telephone terminal and hanging up the telephone.
Wherein the method further comprises: and receiving a conference request message sent by the server side, and starting a conference according to the conference request message.
A real-time synchronization system for conference messages comprises a server end and a conference platform end which are connected with each other; the conference platform end is used for receiving conference operation messages sent by conference participants; generating a conference change message according to the conference operation message, and pushing the conference change message to a server side; the server side is used for receiving handshake messages sent by a client side, establishing connection with the client side, receiving conference change messages sent by the conference platform side, and pushing the conference change messages to the client side.
The conference platform end comprises a middleware and a conference platform which are connected with each other; the conference platform is used for receiving conference operation messages sent by conference participants; generating a conference change message according to the conference operation message, and sending the conference change message to the middleware; the middleware is used for receiving the conference change message sent by the server side, sending the conference change message to the conference platform, and sending the conference change message to the server side.
A conference message real-time synchronization apparatus comprising an interconnected memory and a processor for running a computer program stored in the memory to implement a method as described above.
A storage medium storing a computer program executable to implement the method as described above.
The embodiment of the invention has the following beneficial effects:
the server side receives handshake messages sent by the client side and establishes connection with the client side, so that the server side can actively send messages to the client side, the conference platform side receives changes of conference participants to generate conference change messages, receives the conference change messages sent by the conference platform side and pushes the conference change messages to the client side, and therefore when the conference participants change, the client side can display the conference change messages in time to prompt the client side users that the conference participants change, notification efficiency can be effectively improved, and resources are saved.
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 description of the embodiments or 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.
Wherein:
fig. 1 is a schematic flow chart of a first embodiment of a conference message real-time synchronization method provided by the present invention;
fig. 2 is a schematic flow chart of a conference message real-time synchronization method according to a second embodiment of the present invention;
fig. 3 is a schematic flowchart of a third embodiment of a method for real-time synchronization of conference messages according to the present invention;
fig. 4 is a schematic flowchart of a fourth embodiment of a conference message real-time synchronization method provided by the present invention;
fig. 5 is a schematic structural diagram of a first embodiment of a conference message real-time synchronization system provided by the present invention;
fig. 6 is a schematic structural diagram of a second embodiment of the real-time conference message synchronization system provided by the present invention;
fig. 7 is a schematic structural diagram of an embodiment of a device for real-time synchronization of conference messages provided by the present invention;
fig. 8 is a schematic structural diagram of an embodiment of a storage medium provided in 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.
Referring to fig. 1, fig. 1 is a schematic flowchart illustrating a conference message real-time synchronization method according to a first embodiment of the present invention. The real-time synchronization method for the conference messages provided by the invention comprises the following steps:
s101: and the server receives the handshake message sent by the client and establishes connection with the client.
In a specific implementation scenario, data exchange between the server and the client is based on a WebSocket mechanism, and the WebSocket makes the data exchange between the client and the server simpler, and allows the server to actively push data to the client. In a WebSocket API (Application Programming Interface), a client and a server only need to complete one handshake, and persistent connection can be directly established between the client and the server for bidirectional data transmission. In the implementation scenario, when the client is initialized after being opened, the client first needs to perform WebSocket handshake with the server to establish a connection channel, and the server receives handshake messages sent by the client and establishes handshake connection with the client, so that the server can actively send messages to the client at any time.
S102: the method comprises the steps of sending a subscription message to a conference platform end, receiving a conference change message sent by the conference platform end, and pushing the conference change message to a client, wherein the conference change message is generated and sent by the conference platform end after the conference platform end receives changes of conference participants.
In a specific implementation scenario, the conference platform side determines whether the conference participant changes according to the received conference operation message sent by the conference participant, and generates a conference change message if the conference participant changes. In other implementation scenarios, the conference platform side determines whether the conference changes according to the received conference operation message sent by the conference participants, for example, at least one conference participant mutes, at least one conference participant speaks, and generates a conference change message according to the detected conference change.
The client sends subscription information to the conference platform end through the server end, and the subscription information is used for indicating the conference platform end to send all conference change information to the server end, so that the server end can push the conference change information to the client in time, and a user of the client can know the current change of the conference in time. Therefore, after receiving the conference change message sent by the conference platform, the server sends the conference change message to the client through the WebSocket channel according to the agreed mode, so as to realize real-time communication.
As can be seen from the above description, in this embodiment, the server receives the handshake message sent by the client and establishes handshake connection with the client, so that the server can actively send a message to the client, the conference platform receives a change of a conference participant to generate a conference change message, receives the conference change message sent by the conference platform, and pushes the conference change message to the client, so that when the conference participant changes, the client can display the conference change message in time to prompt the client user that the conference participant changes, thereby effectively improving notification efficiency and saving resources.
Referring to fig. 2, fig. 2 is a flowchart illustrating a conference message real-time synchronization method according to a second embodiment of the present invention. The real-time synchronization method for the conference messages provided by the invention comprises the following steps:
s201: and the server receives the handshake message sent by the client and establishes connection with the client.
In a specific implementation scenario, step S201 is substantially the same as step S101 in the first embodiment of the method for synchronizing a conference message in real time provided by the present invention, and details are not repeated here.
S202: and receiving a conference request message sent by the client, and sending the conference request message to the conference platform end, so that the conference platform end starts a conference response according to the conference request message.
In a specific implementation scenario, when the client is initialized after being opened, the client first needs to perform WebSocket handshake with the server, and after a connection channel is established, the client can send a message to the server through the established connection channel. A user of the client may send a conference request message through the client, where the conference request message includes a request type, and the request type includes: at least one of a conference reservation, an outbound participant meeting, a total mute request, a conference lock request, a conference recording request, a participant mute, or a hang-up request.
The server side sends the meeting request message to the conference platform side, and the conference platform side starts a meeting response according to the received meeting request message, for example, a meeting is started at a preset reserved time according to the meeting request message reserved by the meeting, and then, for example, a request is sent to the corresponding meeting participant according to the meeting request message of the outbound participant to inform the corresponding meeting participant to join the meeting, and for example, recording is carried out according to the meeting request message recorded by the meeting participant, and the recorded file is stored and sent.
S203: the method comprises the steps of sending a subscription message to a conference platform end, receiving a conference change message sent by the conference platform end, and pushing the conference change message to a client, wherein the conference change message is generated and sent by the conference platform end after the conference platform end receives changes of conference participants.
In a specific implementation scenario, step S203 is substantially the same as step S102 in the first embodiment of the method for synchronizing a conference message in real time provided by the present invention, and details are not repeated here.
As can be seen from the above description, in this implementation scenario, the server receives the conference request message sent by the client, and sends the conference request message to the conference platform, so that the conference platform starts a conference response according to the conference request message, which can effectively save communication time between the client and the server, and improve efficiency.
Referring to fig. 3, fig. 3 is a flowchart illustrating a conference message real-time synchronization method according to a third embodiment of the present invention. The real-time synchronization method for the conference messages provided by the invention comprises the following steps:
s301: and the conference platform end receives the conference operation message sent by the conference participant.
In a specific implementation scenario, the conference platform receives a conference operation message sent by a conference participant. The conference operation message includes an operation type, and the operation type includes: actively dialing at least one of a meeting, muting the telephone terminal, canceling the muting, raising a question and answer at the telephone terminal and hanging up the telephone. And the conference platform end starts the corresponding conference operation according to the conference operation message. For example, if a conference operation message for actively calling into a conference is received, the conference participant is added into the called conference, and if a conference operation message for muting the telephone terminal is received, the telephone terminal of the conference participant is muted, and if a conference operation message for hanging up the telephone terminal is received, the conference participant is deleted from the conference.
S302: and receiving a subscription sending message sent by the server, generating a conference change message according to the conference operation message, and pushing the conference change message to the server so that the server pushes the conference change message to the client side of the device.
In a specific implementation scenario, a client sends a subscription message to a conference platform end through a server end, where the subscription message is used to instruct the conference platform end to send all conference change messages to the server end, so that the server end can push the conference change messages to the client in time, and a user of the client can know the current change of a conference in time.
The conference platform end can judge whether the conference participants change according to the conference operation message, for example, if a new conference participant sends the conference operation message of actively calling to enter the conference, the new conference participant is shown to join the conference, or if the existing conference participant sends the conference operation message of hanging up the telephone, the existing conference participant exits the conference. If the conference participant is determined to be changed, a corresponding conference change message is generated, for example, a conference change message of the new conference participant is generated according to a conference operation message sent by the new conference participant to actively make a call for conference, and the conference change message may include an identifier of the new conference participant, including a name, a code number, a serial number, and the like. For another example, a conference change message for exiting the conference participant is generated according to the conference operation message of hanging up the phone, which is sent by the existing conference participant, and the conference change message includes the identification of the exiting conference participant, including the name, code number, serial number, and the like.
In other implementation scenarios, because the conference operation message changes correspondingly to the conference, for example, a new conference participant actively dials a call to enter the conference, or the telephone terminal of the existing conference participant is silent, the conference change message is generated according to the received conference operation message, and the conference change message is sent to the server terminal, so that the server terminal pushes the conference change message to the client terminal according to the WebSocket mechanism, and a user of the client terminal can know the change of the conference in time.
As can be seen from the above description, in this embodiment, the conference platform side generates a conference change message according to the question operation message sent by the conference participant and sends the conference change message to the server side, so that the server side pushes the conference change message to the client side according to the WebSocket mechanism, so that a user at the client side can know the change of the conference in time, the efficiency of the user at the client side acquiring the conference change can be effectively improved, the time delay is reduced, and the resource consumption of notification is reduced.
Referring to fig. 4, fig. 4 is a schematic flowchart illustrating a conference message real-time synchronization method according to a fourth embodiment of the present invention. The real-time synchronization method for the conference messages provided by the invention comprises the following steps:
s401: and receiving a conference request message sent by the server side, and starting a conference response according to the conference request message.
In a specific implementation scenario, a user of a client may send a conference request message through the client, where the conference request message includes a request type, and the request type includes: at least one of a conference reservation, an outbound participant meeting, a total mute request, a conference lock request, a conference recording request, a participant mute, or a hang-up request. The server side sends the meeting request message to the conference platform side, and the conference platform side starts a meeting response according to the received meeting request message, for example, a meeting is started at a preset reserved time according to the meeting request message reserved by the meeting, and then, for example, a request is sent to the corresponding meeting participant according to the meeting request message of the outbound participant to inform the corresponding meeting participant to join the meeting, and for example, recording is carried out according to the meeting request message recorded by the meeting participant, and the recorded file is stored and sent.
S402: and the conference platform end receives the conference operation message sent by the conference participant.
S403: and receiving a subscription sending message sent by the server, generating a conference change message according to the conference operation message, and pushing the conference change message to the server so that the server pushes the conference change message to the client.
As can be seen from the above description, in this embodiment, the conference platform side starts a conference response according to the conference request message sent by the server side, and can timely complete the indication of the client side, thereby meeting the user requirements.
Referring to fig. 5, fig. 5 is a schematic structural diagram of a conference message real-time synchronization system according to a first embodiment of the present invention. The conference message real-time synchronization system 10 comprises a server side 11 and a conference platform side 12 which are connected with each other.
The server 11 is configured to receive a handshake message sent by the client, and establish a connection with the client. The data exchange between the server and the client is based on a WebSocket mechanism, the WebSocket enables the data exchange between the client and the server to be simpler, and the server is allowed to actively push data to the client. In a WebSocket API (Application Programming Interface), a client and a server only need to complete one handshake, and persistent connection can be directly established between the client and the server for bidirectional data transmission.
The server 11 receives a conference request message sent by a user of a client through the client, where the conference request message includes a request type, and the request type includes: at least one of a conference reservation, an outbound participant meeting, a total mute request, a conference lock request, a conference recording request, a participant mute, or a hang-up request. The server side 11 sends a conference request message to the conference platform side 12.
The conference platform 12 starts a conference response according to the received conference request message, for example, starts a conference at a preset reservation time according to the conference request message for conference reservation, and then sends a request to the corresponding conference participant according to the conference request message for the outbound participant to join the conference, for example, records the conference request message according to the conference recording of the conference, stores and sends the recording file.
The client sends a subscription message to the conference platform end 12 through the server end 11, where the subscription message is used to instruct the conference platform end 12 to send all conference change messages to the server end, so that the server end 11 can push the conference change messages to the client in time, and a user of the client can know the current change of the conference in time.
The conference platform 12 receives a conference operation message sent by a conference participant, where the conference operation message includes an operation type, and the operation type includes: actively dialing at least one of a meeting, muting the telephone terminal, canceling the muting, raising a question and answer at the telephone terminal and hanging up the telephone. The conference platform 12 starts the corresponding conference operation according to the conference operation message. For example, if a conference operation message for actively calling into a conference is received, the conference participant is added into the called conference, and if a conference operation message for muting the telephone terminal is received, the telephone terminal of the conference participant is muted, and if a conference operation message for hanging up the telephone terminal is received, the conference participant is deleted from the conference.
Because the conference operation message is changed correspondingly to the conference, for example, a new conference participant actively makes a call to enter a conference, or the telephone terminal of the existing conference participant is muted, etc., the conference platform terminal 12 generates a conference change message according to the received conference operation message, and sends the conference change message to the server terminal 11.
After receiving the conference change message sent by the conference platform 12, the server 11 sends the conference change message to the client through the WebSocket channel according to the agreed mode, so as to implement real-time communication.
As can be seen from the above description, in this embodiment, in this implementation scenario, the server end receives the handshake message sent by the client end, and establishes handshake connection with the client end, so that the server end can actively send a message to the client end, the conference platform end receives a change of a conference participant to generate a conference change message, receives the conference change message sent by the conference platform end, and pushes the conference change message to the client end, so that when the conference participant changes, the client end can display the conference change message in time to prompt the client user that the conference participant changes, thereby effectively improving notification efficiency and saving resources.
Referring to fig. 6, fig. 6 is a schematic structural diagram of a real-time conference message synchronization system according to a second embodiment of the present invention. The conference message real-time synchronization system 20 comprises a server side 21 and a conference platform side 22 which are connected with each other. Conference platform end 22 includes interconnected middleware, such as ACM middleware 221, and a conference platform, such as Summit platform 222.
The server 21 is configured to receive a handshake message sent by the client, and establish a connection with the client.
The server 11 receives the conference request message sent by the user of the client through the client, and sends the conference request message to the ACM middleware 221.
The ACM middleware 221 receives the conference request message sent by the server 21, and sends the conference request message to the Summit platform 222.
The Summit platform 222 receives a conference operation message sent by a conference participant; and generating a conference change message according to the conference operation message, and sending the conference change message to the ACM middleware 221.
The ACM middleware 221 sends the conference change message to the server 21.
The server 21 receives the conference change message and pushes the conference change message to the client.
The ACM (conference call platform message transfer system) middleware is a middleware system serving the Summit platform and is used for transferring commands and messages between the conference application system and the Summit platform. When there is any change in the conference on the Summit platform, the Summit platform will send messages to the ACM middleware, which will broadcast these messages to the various application systems.
In this implementation scenario, conference participants can actively enter a conference, and can directly send a command to the Summit platform 222 through the operation of the telephone terminal to implement a related function, and this operation bypasses the client and the server 21, but after the command takes effect, the client is still affected by the message push mode.
As can be seen from the above description, in this embodiment, the WebSocket mechanism is used to process the conference message sent by the ACM, and the client and the server are combined to implement real-time synchronization of the message, so that resources can be effectively saved, efficiency is improved, and information display is more comprehensive.
Referring to fig. 7, fig. 7 is a schematic structural diagram of an embodiment of a device for real-time synchronization of conference messages according to the present invention. The conference message real-time synchronization apparatus 30 provided by the present invention includes a memory 31 and a processor 32 connected to each other. The memory 32 has stored therein a computer program which is executed by the processor 31 when it is operated to carry out the method as shown in fig. 1-4. The detailed methods can be referred to above and are not described herein.
As can be seen from the above description, in this embodiment, the real-time conference message synchronization device receives a handshake message sent by a client and establishes handshake connection with the client, so that a message can be actively sent to the client, a conference platform end receives a change of a conference participant to generate a conference change message, receives the conference change message sent by the conference platform end, and pushes the conference change message to the client, so that when the conference participant changes, the client can display the conference change message in time to prompt a client user that the conference participant changes, thereby effectively improving notification efficiency and saving resources.
Referring to fig. 8, fig. 8 is a schematic structural diagram of a storage medium according to an embodiment of the present invention. The computer-readable storage medium 40 stores at least one computer program 41, and the computer program 41 is used for being executed by a processor to implement the method shown in fig. 1 to 4, and the detailed method can be referred to above and is not described herein again. In one embodiment, the computer readable storage medium 30 may be a memory chip in a terminal, a hard disk, or other readable and writable storage tool such as a removable hard disk, a flash disk, an optical disk, or the like, and may also be a server or the like.
As can be seen from the above description, the computer program stored in the storage medium in this embodiment may be used to enable the server to receive the handshake message sent by the client and establish handshake connection with the client, so that the server may actively send a message to the client, the conference platform receives a change of a conference participant to generate a conference change message, receives the conference change message sent by the conference platform and pushes the conference change message to the client, and when the conference participant changes, the client may display the conference change message in time to prompt the client user that the conference participant changes, which may effectively improve notification efficiency and save resources.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware related to instructions of a computer program, and the program can be stored in a non-volatile computer readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, storage, database, or other medium used in the embodiments provided herein may include non-volatile and/or volatile memory, among others. Non-volatile memory can include read-only memory (ROM), Programmable ROM (PROM), Electrically Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDRSDRAM), Enhanced SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), Rambus Direct RAM (RDRAM), direct bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).
The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above examples only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the present application. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent shall be subject to the appended claims.
Claims (10)
1. A real-time synchronization method for conference messages is characterized by comprising the following steps:
the server receives handshake messages sent by the client and establishes connection with the client;
sending a subscription message to a conference platform end, receiving a conference change message sent by the conference platform end, and pushing the conference change message to the client, wherein the conference change message is generated and sent by the conference platform end after receiving the change of conference participants.
2. The method for synchronizing conference messages in real time according to claim 1, wherein the step of establishing a connection with the client is followed by the steps of:
and receiving a conference request message sent by the client, and sending the conference request message to the conference platform end, so that the conference platform end starts a conference response according to the conference request message.
3. The method of claim 2, wherein the conference request message comprises a request type, and wherein the request type comprises: at least one of a conference reservation, an outbound participant meeting, a total mute request, a conference lock request, a conference recording request, a participant mute, or a hang-up request.
4. A real-time synchronization method for conference messages is characterized by comprising the following steps:
a conference platform end receives a conference operation message sent by a conference participant;
receiving a subscription sending message sent by a server, generating a conference change message according to the conference operation message, and pushing the conference change message to the server so that the server pushes the conference change message to a client.
5. The real-time conference message synchronization method according to claim 4, wherein said conference operation message includes an operation type, said operation type including: actively dialing at least one of a meeting, muting the telephone terminal, canceling the muting, raising a question and answer at the telephone terminal and hanging up the telephone.
6. The method for real-time synchronization of conference messages according to claim 4, wherein said method further comprises:
and receiving a conference request message sent by the server side, and starting a conference response according to the conference request message.
7. A real-time synchronization system for conference messages is characterized by comprising a server end and a conference platform end which are connected with each other;
the conference platform end is used for receiving conference operation messages sent by conference participants; generating a conference change message according to the conference operation message, and pushing the conference change message to a server side;
the server side is used for receiving handshake messages sent by the client side, establishing connection with the client side, sending subscription messages to the conference platform side, receiving conference change messages sent by the conference platform side, and pushing the conference change messages to the client side.
8. The system for real-time synchronization of conference messages according to claim 7, wherein the conference platform side comprises a middleware and a conference platform connected with each other;
the conference platform is used for receiving conference operation messages sent by conference participants; generating a conference change message according to the conference operation message, and sending the conference change message to the middleware;
the middleware is used for receiving the conference request message sent by the server, sending the conference request message to the conference platform, and sending the conference change message to the server.
9. A conference message real-time synchronization apparatus, comprising a memory and a processor connected to each other, the processor being configured to execute a computer program stored in the memory to implement the method according to any one of claims 1-3 or claims 4-6.
10. A storage medium, characterized in that a computer program is stored, which computer program can be run to implement the method according to any one of claims 1-3 or 4-6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011574335.6A CN112291371B (en) | 2020-12-28 | 2020-12-28 | Conference message real-time synchronization method, system, device and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011574335.6A CN112291371B (en) | 2020-12-28 | 2020-12-28 | Conference message real-time synchronization method, system, device and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112291371A true CN112291371A (en) | 2021-01-29 |
| CN112291371B CN112291371B (en) | 2021-04-06 |
Family
ID=74426458
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011574335.6A Active CN112291371B (en) | 2020-12-28 | 2020-12-28 | Conference message real-time synchronization method, system, device and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112291371B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112565532A (en) * | 2021-02-20 | 2021-03-26 | 全时云商务服务股份有限公司 | Conference call joining method and system |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103546584A (en) * | 2013-11-13 | 2014-01-29 | 深圳市中兴移动通信有限公司 | Information pushing method and system |
| WO2015108760A1 (en) * | 2014-01-16 | 2015-07-23 | Microsoft Technology Licensing, Llc | Accessing and configuring meeting attributes |
| CN105991964A (en) * | 2015-02-13 | 2016-10-05 | 中兴通讯股份有限公司 | Method and apparatus for broadcasting dynamic information in multimedia conference |
| CN107580190A (en) * | 2017-08-22 | 2018-01-12 | 福建星网智慧科技股份有限公司 | A kind of list of conference based on Session Initiation Protocol is subscribed to and Notification Method |
| CN110138573A (en) * | 2018-02-09 | 2019-08-16 | 腾讯科技（深圳）有限公司 | A kind of conference status reminding method, server, intelligent terminal and storage medium |
| CN110475090A (en) * | 2019-08-05 | 2019-11-19 | 视联动力信息技术股份有限公司 | A kind of method and system of Conference control |
| CN111447391A (en) * | 2020-02-20 | 2020-07-24 | 平安科技（深圳）有限公司 | Conference data synchronization method and device, computer equipment and storage medium |
-
2020
- 2020-12-28 CN CN202011574335.6A patent/CN112291371B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103546584A (en) * | 2013-11-13 | 2014-01-29 | 深圳市中兴移动通信有限公司 | Information pushing method and system |
| WO2015108760A1 (en) * | 2014-01-16 | 2015-07-23 | Microsoft Technology Licensing, Llc | Accessing and configuring meeting attributes |
| CN105991964A (en) * | 2015-02-13 | 2016-10-05 | 中兴通讯股份有限公司 | Method and apparatus for broadcasting dynamic information in multimedia conference |
| CN107580190A (en) * | 2017-08-22 | 2018-01-12 | 福建星网智慧科技股份有限公司 | A kind of list of conference based on Session Initiation Protocol is subscribed to and Notification Method |
| CN110138573A (en) * | 2018-02-09 | 2019-08-16 | 腾讯科技（深圳）有限公司 | A kind of conference status reminding method, server, intelligent terminal and storage medium |
| CN110475090A (en) * | 2019-08-05 | 2019-11-19 | 视联动力信息技术股份有限公司 | A kind of method and system of Conference control |
| CN111447391A (en) * | 2020-02-20 | 2020-07-24 | 平安科技（深圳）有限公司 | Conference data synchronization method and device, computer equipment and storage medium |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112565532A (en) * | 2021-02-20 | 2021-03-26 | 全时云商务服务股份有限公司 | Conference call joining method and system |
| CN112565532B (en) * | 2021-02-20 | 2021-05-18 | 全时云商务服务股份有限公司 | Conference call joining method and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112291371B (en) | 2021-04-06 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10764430B2 (en) | Calling an unready terminal | |
| US20050202806A1 (en) | Automatic conference call replay | |
| EP3709664B1 (en) | Stream pushing method, system and server | |
| JP2008022584A (en) | System and method for wireless multimedia communication | |
| US8917824B2 (en) | Visual voicemail method for managing deleted messages | |
| US20220209878A1 (en) | Method, system and device for pushing information, and storage medium thereof | |
| WO2017101297A1 (en) | Method and device for video messaging, terminal, and server | |
| US20200244753A1 (en) | Method, system and server for stream-pushing | |
| KR20180019737A (en) | Method, system, and apparatus for processing system calls during a voice call | |
| CN1984373B (en) | System and method for providing multimedia contents in a communication system | |
| CN112291371B (en) | Conference message real-time synchronization method, system, device and storage medium | |
| CN107534660B (en) | Managing communication events | |
| CN112291501A (en) | Video conference control method and device | |
| CN109120578B (en) | Method and device for realizing link connection processing | |
| US20180352009A1 (en) | Apparatus for setting up conference call and method thereof | |
| CN110351570B (en) | Video live broadcast method and system under 5G network | |
| CN111796958A (en) | Transaction anti-hanging method and device under Dubbo frame | |
| CN116828022B (en) | Method, device, equipment and medium for managing connection relation with server | |
| CN113747100B (en) | Audio and video call method and device, storage medium and electronic equipment | |
| JP6634172B1 (en) | Program and system for transmitting / receiving digital information (message) to / from a short-range communication network | |
| WO2021121122A1 (en) | Conference creation method, terminal, server end, and storage medium | |
| CN114466025B (en) | Session processing method and first cluster control functional entity | |
| CN113973089B (en) | Streaming media transmission method, system, equipment and storage medium | |
| CN102651740A (en) | Method and device for processing voice information | |
| WO2021115437A1 (en) | Rejection short message sending method and apparatus, and computer device and storage medium |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |