CN114125362B - Conference joining method, device, conference platform and computer readable storage medium - Google Patents
Conference joining method, device, conference platform and computer readable storage medium Download PDFInfo
- Publication number
- CN114125362B CN114125362B CN202111401030.XA CN202111401030A CN114125362B CN 114125362 B CN114125362 B CN 114125362B CN 202111401030 A CN202111401030 A CN 202111401030A CN 114125362 B CN114125362 B CN 114125362B
- Authority
- CN
- China
- Prior art keywords
- conference
- target member
- software
- platform
- hardware
- 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.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 54
- 238000004891 communication Methods 0.000 claims abstract description 26
- 238000004590 computer program Methods 0.000 claims description 11
- 230000011664 signaling Effects 0.000 claims description 3
- 238000012545 processing Methods 0.000 description 12
- 230000006870 function Effects 0.000 description 8
- 238000010586 diagram Methods 0.000 description 6
- 230000005540 biological transmission Effects 0.000 description 2
- 238000006243 chemical reaction Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000000977 initiatory effect Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000004064 recycling Methods 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N7/00—Television systems
- H04N7/14—Systems for two-way working
- H04N7/15—Conference systems
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/1066—Session management
- H04L65/1083—In-session procedures
- H04L65/1093—In-session procedures by adding participants; by removing participants
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/40—Support for services or applications
- H04L65/403—Arrangements for multi-party communication, e.g. for conferences
Landscapes
- Engineering & Computer Science (AREA)
- Multimedia (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Business, Economics & Management (AREA)
- General Business, Economics & Management (AREA)
- Telephonic Communication Services (AREA)
- Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)
Abstract
The application provides a conference joining method, a conference joining device, a conference platform and a computer readable storage medium. The method comprises the steps of obtaining a preset conference type corresponding to a conference to which a target member to be added in a first conference belongs according to a conference joining request, wherein the first conference belongs to a software conference type based on a first private protocol, creating an ad hoc conference corresponding to the target member when the preset conference type is different from the software conference type, and sending a conference number corresponding to the ad hoc conference to a hardware terminal corresponding to the target member, wherein the ad hoc conference is a conference based on a preset standard protocol, receiving a call request sent by the hardware terminal based on the conference number, establishing communication connection with the hardware terminal based on the call request, and joining the target member in the first conference through the ad hoc conference, so that conference intercommunication between a hardware side and a software side can be realized, and the problem that the conference between the hardware side and the software side cannot be realized due to different private protocols can be avoided.
Description
Technical Field
The present application relates to the field of data communications technologies, and in particular, to a conference joining method, a conference joining device, a conference platform, and a computer readable storage medium.
Background
Current conference types generally include two types, a software conference type and a hardware conference type. Software conferences are typically presented in the form of desktop applications, mainly facing public clients. The software conference platform is mainly built based on a private protocol of SVC (Scalable Video Coding scalable video coding technology) framework. The hard-software conference is usually presented as a dedicated conference terminal of the entity, mainly facing the government enterprise clients. The hard-software conference platform is mainly built based on another private protocol of AVC (Advanced Video Coding, short for advanced video coding)/SVC hybrid architecture.
Because the private protocols used by the software conference platform and the hardware conference platform are different, the two conference platforms cannot be communicated at present, so that users of the two types of conferences cannot develop conferences in the same conference.
Disclosure of Invention
The embodiment of the application aims to provide a conference joining method, a conference joining device, a conference platform and a computer readable storage medium, which can enable users of a software conference and a hardware conference to enter the same conference for communication.
In order to achieve the above object, an embodiment of the present application is achieved by:
According to a first aspect, an embodiment of the application provides a conference joining method, which comprises the steps of obtaining a preset conference type corresponding to a conference to which a target member to be joined in a first conference belongs according to a conference joining request, wherein the first conference belongs to a software conference type based on a first private protocol, creating an ad hoc conference corresponding to the target member when the preset conference type is different from the software conference type, and sending a conference number corresponding to the ad hoc conference to a hardware terminal corresponding to the target member, wherein the ad hoc conference is a conference based on a preset standard protocol, receiving a call request sent by the hardware terminal based on the conference number, establishing communication connection with the hardware terminal based on the call request, and joining the target member in the first conference through the ad hoc conference.
In the above embodiment, when the preset conference type corresponding to the target member is different from the software conference type, it indicates that the preset conference type is a hardware conference type. At this time, the temporary conference based on the standard protocol is created for the target member, so that the target member can convert the private protocol corresponding to the hardware conference into the standard protocol of the temporary conference, and then transmit data to the software conference platform by the standard protocol to realize conference intercommunication, thereby avoiding the problem that conference intercommunication cannot be realized due to different private protocols.
With reference to the first aspect, in some optional embodiments, the method further includes receiving multimedia data based on the preset standard protocol sent by the target member through the temporary conference, converting the multimedia data into multimedia data of the first private protocol, and sending the converted multimedia data to other members in the first conference except the target member.
With reference to the first aspect, in some optional embodiments, the method further includes converting, by the gateway device, the other members in the first conference to the multimedia data of the preset standard protocol based on the multimedia data transmitted by the first private protocol, where the other members are members in the first conference except the target member, sending, by the ad hoc conference, the converted multimedia data to a gateway device corresponding to the hardware terminal, so that the gateway device converts the converted multimedia data to the multimedia data of the second private protocol corresponding to the target member, and sending, by the gateway device, the multimedia data of the second private protocol to the hardware terminal.
With reference to the first aspect, in some optional embodiments, before acquiring the preset conference type corresponding to the conference to which the target member to be added to the first conference belongs, the method further includes creating the first conference based on the software conference type according to the received conference creation request.
The conference joining method comprises the steps of obtaining a preset conference type corresponding to a second conference when a target member requests to join the second conference, wherein the conference to which the target member belongs is a software conference type based on a first private protocol, and joining the target member to the second conference by calling a second software development kit corresponding to the second conference when the preset conference type is different from the software conference type, wherein the second software development kit is used for transmitting data to other members in the second conference based on the second private protocol, the second private protocol is the private protocol corresponding to the second conference, and the other members are members except the target member in the second conference.
In the above embodiment, by calling the second software development kit, the target member in the software conference can transmit data to other members in the second conference of the hardware conference type based on the second private protocol, thereby ensuring that the second conference adopts the second private protocol for communication, realizing conference intercommunication, and avoiding the incapability of conference intercommunication due to different private protocols.
With reference to the second aspect, in some optional embodiments, the method further includes:
And when the preset conference type is the same as the software conference type, the target member is added into the second conference by calling a first software development kit corresponding to the software conference type, wherein the first software development kit is used for transmitting data to the other members in the second conference by the target member based on the first private protocol.
In a third aspect, the present application also provides a conference joining apparatus, the apparatus comprising:
The first acquisition unit is used for acquiring a preset conference type corresponding to a conference to which a target member to be added in a first conference belongs according to a conference adding request, wherein the first conference belongs to a software conference type based on a first private protocol;
The creation unit is used for creating an ad hoc conference corresponding to the target member when the preset conference type is different from the software conference type, and sending a conference number corresponding to the ad hoc conference to a hardware terminal corresponding to the target member, wherein the ad hoc conference is a conference based on a preset standard protocol;
The receiving unit is used for receiving a call request sent by the hardware terminal based on the conference number;
And the communication establishing unit is used for establishing communication connection with the hardware terminal based on the call request and joining the target member into the first conference through the temporary conference.
In a fourth aspect, the present application also provides a conference joining apparatus, the apparatus including:
the second acquisition unit is used for acquiring a preset conference type corresponding to a second conference when a target member requests to join the second conference, wherein the conference to which the target member belongs is a software conference type based on a first private protocol;
And the conference joining unit is used for joining the target member into the second conference by calling a second software development kit corresponding to the second conference when the preset conference type is different from the software conference type, wherein the second software development kit is used for transmitting data to other members in the second conference based on a second private protocol, the second private protocol is the private protocol corresponding to the second conference, and the other members are members except the target member in the second conference.
In a fourth aspect, the present application also provides a conference platform comprising a processor and a memory coupled to each other, the memory storing a computer program which, when executed by the processor, causes the conference platform to perform the method of the first or second aspect described above.
In a fifth aspect, the present application also provides a computer readable storage medium having a computer program stored therein, which when run on a computer causes the computer to perform the method of the first or second aspect as described above.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the embodiments of the present application will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present application and should not be considered as limiting the scope, and other related drawings can be obtained according to these drawings without inventive effort for a person skilled in the art.
Fig. 1 is a schematic view of a scenario of intercommunication between a software conference and a hardware conference according to an embodiment of the present application.
Fig. 2 is a schematic flow chart of a conference joining method according to an embodiment of the present application.
Fig. 3 is a block diagram of a conference joining apparatus according to an embodiment of the present application.
Fig. 4 is a second flowchart of a conference joining method according to an embodiment of the present application.
Fig. 5 is a second block diagram of a conference joining apparatus according to an embodiment of the present application.
The icons are 10-software conference platform, 11-client, 12-client, 20-hardware conference platform, 21-hardware terminal, 22-hardware terminal, 30-boundary session controller, 40-gateway device, 200-conference joining device, 210-first acquisition unit, 220-creation unit, 230-receiving unit, 240-communication establishment unit, 400-conference joining device, 410-second acquisition unit, 420-conference joining unit.
Detailed Description
The technical solutions in the embodiments of the present application will be described below with reference to the accompanying drawings in the embodiments of the present application. It should be noted that the terms "first," "second," and the like are used merely to distinguish between descriptions and should not be construed as indicating or implying relative importance. The following embodiments and features of the embodiments may be combined with each other without conflict.
First embodiment
The application provides a conference platform which can comprise a processing module and a storage module. The storage module stores a computer program which, when executed by the processing module, enables the conference platform to perform the respective steps in the conference joining method described below.
Referring to fig. 1, in the present embodiment, the conference platform may be a software conference platform 10 or a hardware conference platform 20. The conference platform can be a host or a server for building a conference and can be flexibly set according to actual conditions.
Wherein the software conference platform 10 may be communicatively coupled to one or more clients for establishing a software conference. The hardware conference platform 20 may be communicatively coupled to one or more hardware terminals for establishing a hardware conference.
A client may be understood as a terminal of a user participating in a software conference, which may be, but is not limited to, a personal computer, a tablet, a smart phone, etc.
The hardware terminal may be a terminal dedicated to a hardware conference, which realizes video and audio Processing and network communication based on DSP (DIGITAL SIGNAL Processing, digital signal processor) and embedded software, and is well known to those skilled in the art.
For example, referring again to fig. 1, a software conference platform 10 may be communicatively coupled to clients 11 and 12. The hardware conference platform 20 may be communicatively connected to a hardware terminal 21 and a hardware terminal 22.
In this embodiment, the software conference platform 10 may connect with the border session controller (Session Border Controller, SBC) via a connector, and then establish a communication connection with the gateway device 40 by the border session controller 30. Wherein gateway device 40 and border session controller 30 may bridge communications between hardware conferencing platform 20 and software conferencing platform 10, respectively.
In this embodiment, gateway device 40 may be a SIP (Session initialization Protocol, session initiation protocol) gateway, and may convert data of the hardware conference platform 20 based on the private protocol into data of the SIP protocol. The Connector may be a Room Connector (RC) that may be used to convert proprietary protocols of the software conference platform 10 to standard protocols. The standard protocol can be flexibly determined according to actual conditions, for example, the SIP protocol.
It should be noted that the connector and the boundary session controller 30 may be integrated into the software conference platform 10 or may be independent of the existence of the software conference platform 10. For example, the connector and border session controller 30 may act as a stand-alone service device.
In this embodiment, the enabling platform may be understood as a software function module deployed on the software conference platform 10, which is an independent accounting management and conference management scheduling platform, and the conference functions of all clients may be implemented by calling the interfaces of the enabling platform.
Referring to fig. 2, the present application provides a conference joining method, which can be applied to the above-mentioned software conference platform 10, and the steps of the method are executed or implemented by the software conference platform 10. When a user on the hardware side wants to join a conference created on the software side, the method may comprise the steps of:
Step S110, acquiring a preset conference type corresponding to a conference to which a target member to be added in a first conference belongs according to a conference adding request, wherein the first conference belongs to a software conference type based on a first private protocol;
Step S120, when the preset conference type is different from the software conference type, creating an ad hoc conference corresponding to the target member, and sending a conference number corresponding to the ad hoc conference to a hardware terminal corresponding to the target member, wherein the ad hoc conference is a conference based on a preset standard protocol;
step S130, receiving a call request sent by the hardware terminal based on the conference number;
step S140, based on the call request, establishing a communication connection with the hardware terminal, and joining the target member into the first conference through the temporary conference.
In the above embodiment, when the preset conference type corresponding to the target member is different from the software conference type, it indicates that the preset conference type is a hardware conference type. At this time, by creating the ad hoc conference based on the standard protocol for the target member, the target member can convert the private protocol corresponding to the hardware conference into the standard protocol of the ad hoc conference, and then transmit data to the software conference platform 10 by using the standard protocol, so as to realize conference intercommunication, thereby avoiding the problem that the software test and the hardware side conference intercommunication cannot be realized due to different private protocols.
The steps of the method will be described in detail below, as follows:
Prior to step S110, the method may comprise the step of creating a first meeting. For example, before step S110, the method may include:
and according to the received conference creation request, creating the first conference based on the software conference type.
Understandably, the user initiating the meeting creation request is typically a meeting presenter. The user may initiate a conference creation request to the software conference platform 10 via the corresponding APP (Application) of the client.
The software conference platform 10, upon receiving the conference request, may create a first conference based on the software conference type. At this time, the first conference is a software conference. In addition, the host can flexibly invite the users of other clients to be members participating in the first conference according to actual conditions.
For example, a moderator may invite a user at client 12 to join a first conference through client 11. Communication may be based on a first private protocol between members of the first conference. The first private protocol may be flexibly determined according to practical situations, which is not specifically limited herein.
In step S110, the target member refers to the user who wants to join the first conference. For example, if a user wants to join a first session through the hardware terminal 21, the user is the target member. At this time, the target member may input the conference number of the first conference through the hardware terminal 21, and then a conference joining request is generated by the hardware terminal 21 based on the conference number of the first conference.
The conference joining request may carry a conference type characterizing a conference to which the hardware terminal itself belongs. At this time, the conference type of the conference to which the target member or the hardware terminal belongs is the hardware conference type.
It should be noted that, in the hardware conference, the target member performs data communication in the second private protocol. The second private protocol is different from the first private protocol, and can be flexibly determined according to actual conditions.
After the hardware terminal sends the conference joining request, the enabling platform in the software conference platform 10 can be called, and the enabling platform can extract the preset conference type corresponding to the conference to which the target member belongs from the conference request and then compare with the software conference type of the first conference. Because the preset conference type is the hardware conference type at this time, the enabling platform can obtain a conclusion that the preset conference type is different from the software conference type.
In step S120, when the preset conference type is different from the software conference type, the hardware conference platform 20 may issue a request for creating an ad hoc conference to the enabling platform by invoking a signaling service. After receiving the request, the enabling platform or the software conference platform 10 can create an ad hoc conference for the target member, and return the conference number corresponding to the ad hoc conference to the hardware terminal corresponding to the target member.
Wherein one ad hoc conference consumes one way of RC resources, during which the hardware conference platform 20 may convert the second proprietary protocol used by itself into SIP protocol through the gateway device 40. In addition, the temporary conference adopts a preset standard protocol for data communication. The preset standard protocol can be flexibly determined according to practical situations, for example, the SIP protocol.
Understandably, the ad hoc conference may convert the data based on the second private protocol sent by the target member into data of a preset standard protocol for transmission, so as to avoid that the data transmitted by the target member is the second private protocol and cannot be sent to the software conference platform 10.
If N hardware terminals apply to join the same software conference, N temporary conferences are generated, so that conference owners at the software side can respectively control video streams generated by the N hardware terminals. Wherein N is an integer greater than or equal to 1. For example, when both the hardware terminal 21 and the hardware terminal 22 join the first conference, the presenter may hide the screen of the hardware terminal 21, display the screen of the hardware terminal 22, or hide the screen of the hardware terminal 22, display the screen of the hardware terminal 21.
In step S130, the call request is a request issued by the hardware terminal upon receiving the conference number of the temporary conference returned by the software conference platform 10. The call request is for the software conference platform 10 to join the target member to the first conference via the ad hoc conference.
Illustratively, referring again to fig. 1, a call request is issued by the hardware terminal 21 and then transmitted to the gateway device 40, and the gateway device 40 establishes a SIP connection with the software conference platform 10 based on the IP address of the ad hoc conference number outbound boundary session controller 30.
In step S140, based on the call request, a SIP connection of the border session controller 30 and the gateway device 40 may be established, so that the software conference platform 10 may be communicatively connected with the hardware devices through the border session controller 30, the gateway device 40, the hardware conference platform 20.
After the target member joins the first conference, the method may further include:
Receiving multimedia data based on the preset standard protocol, which is sent by the target member through the temporary conference;
converting the multimedia data into multimedia data of the first proprietary protocol;
and sending the converted multimedia data to other members except the target member in the first conference.
It will be appreciated that, after the target member joins the first conference, the target member may be sent to other members in the first conference through the ad hoc conference based on the data sent by the hardware terminal. The other members are members except the target member in the first conference.
Illustratively, referring again to fig. 1, after the target member joins the first conference, multimedia data may be sent to the hardware conference platform 20 via the hardware terminal 21 in a second proprietary protocol. The multimedia data is then converted by the hardware conference platform 20 into multimedia data of the SIP protocol through the gateway apparatus 40 and transmitted to the software conference platform 10 through the ad hoc conference. The software conference platform 10 converts the multimedia data of the SIP protocol into multimedia data of the first proprietary protocol, and sends the multimedia data to the corresponding clients of other users. For example, to clients 11 and 12. Thus, the intercommunication of the hardware side conference and the software side conference can be realized.
In this embodiment, the method may further include:
Converting other members in the first conference into multimedia data of the preset standard protocol based on the multimedia data transmitted by the first private protocol, wherein the other members are members except the target member in the first conference;
The converted multimedia data is sent to the gateway device 40 corresponding to the hardware terminal through the temporary conference, so that the gateway device 40 converts the converted multimedia data into multimedia data of a second private protocol corresponding to the target member, and the gateway device 40 sends the multimedia data of the second private protocol to the hardware terminal.
Illustratively, referring again to FIG. 1, after the target member joins the first conference, the user of the client 11 may send his own multimedia data (e.g., audio/video stream) to the software conference platform 10 based on the first private protocol, then the software conference platform 10 converts the multimedia data into SIP protocol-based data, and sends the SIP protocol-based multimedia data to the gateway device 40 via the ad hoc conference. Gateway device 40 then converts the SIP-protocol multimedia data to second proprietary-protocol multimedia data and sends it to hardware conferencing platform 20. The hardware conference platform 20 then sends the multimedia data of the second proprietary protocol to the hardware terminal 21 and the hardware terminal 22. In this way, interworking of software conferences and hardware conferences may be achieved.
Referring to fig. 3, an embodiment of the present application further provides a conference joining apparatus 200, which may be applied to the above-mentioned conference platform, for executing each step in the method. Conference joining device 200 includes at least one software function module that may be stored in a memory module in the form of software or Firmware (Firmware) or cured in a conference platform Operating System (OS). The processing module is configured to execute executable modules stored in the storage module, such as software function modules and computer programs included in the conference joining apparatus 200.
The conference joining apparatus 200 may include a first acquisition unit 210, a creation unit 220, a reception unit 230, and a communication establishment unit 240, and the functional roles of the respective units may be as follows:
A first obtaining unit 210, configured to obtain, according to a conference joining request, a preset conference type corresponding to a conference to which a target member to be joined in a first conference belongs, where the first conference belongs to a software conference type based on a first private protocol;
A creating unit 220, configured to create an ad hoc conference corresponding to the target member when the preset conference type is different from the software conference type, and send a conference number corresponding to the ad hoc conference to a hardware terminal corresponding to the target member, where the ad hoc conference is a conference based on a preset standard protocol;
A receiving unit 230, configured to receive a call request sent by the hardware terminal based on the conference number;
a communication establishing unit 240, configured to establish a communication connection with the hardware terminal based on the call request, and join the target member to the first conference through the temporary conference.
Optionally, the conference joining apparatus 200 may further include a conversion unit and a transmission unit. The receiving unit 230 is further configured to receive multimedia data based on the preset standard protocol sent by the target member through the temporary conference, the converting unit is configured to convert the multimedia data into multimedia data of the first private protocol, and the sending unit is configured to send the converted multimedia data to other members in the first conference except the target member.
Optionally, the conversion unit is further configured to convert, based on the multimedia data transmitted by the first private protocol, other members in the first conference into multimedia data of the preset standard protocol, where the other members are members in the first conference except the target member;
The sending unit is further configured to send, through the temporary conference, the converted multimedia data to a gateway device 40 corresponding to the hardware terminal, so that the gateway device 40 converts the converted multimedia data into multimedia data of a second private protocol corresponding to the target member, and the gateway device 40 sends the multimedia data of the second private protocol to the hardware terminal.
Optionally, before the first obtaining unit 210 obtains a preset conference type corresponding to a conference to which the target member to be joined in the first conference itself belongs, the creating unit 220 is further configured to create the first conference based on the software conference type according to the received conference creation request.
It should be noted that, for convenience and brevity of description, the specific working process of the conference adding apparatus 200 described above may refer to the corresponding process of each step in the foregoing method, and will not be described in detail herein.
Second embodiment
Referring to fig. 4, the present application further provides another conference joining method, which can be applied to the above-mentioned software conference platform 10, and each step in the method is executed or implemented by the software conference platform 10. In comparison with the first embodiment, in the second embodiment, it is the user on the software side that wants to join in the conference created on the hardware side. The method may comprise the steps of:
step S310, when a target member requests to join a second conference, acquiring a preset conference type corresponding to the second conference, wherein the conference to which the target member belongs is a software conference type based on a first private protocol;
step S320, when the preset conference type is different from the software conference type, adding the target member into the second conference by calling a second software development kit corresponding to the second conference, where the second software development kit is used for the target member to transmit data to other members in the second conference based on a second private protocol, the second private protocol is a private protocol corresponding to the second conference, and the other members are members in the second conference except the target member.
In the above embodiment, by calling the second software development kit, the target member in the software conference can transmit data to other members in the second conference of the hardware conference type based on the second private protocol, thereby ensuring that the second conference adopts the second private protocol for communication, realizing conference intercommunication, and avoiding the incapability of conference intercommunication due to different private protocols.
The steps of the method of the second embodiment will be described in detail as follows:
Before step S310, the conference moderator can create a second conference of a hardware conference type through the hardware terminal and communicate with the second conference by using a second private protocol corresponding to the hardware conference type, or create a second conference of a software conference type through the client and communicate with the first conference by using a first private protocol corresponding to the software conference type.
In step S310, the preset conference type corresponding to the second conference may be flexibly determined according to the actual situation, and may be a hardware conference type or a software conference type. The target member is a participant member corresponding to the client APP side.
In step S320, if the preset conference type is different from the software conference type, it indicates that the preset conference type is a hardware conference type. At this time, the second conference to be added by the target member is a hardware conference. Meanwhile, the software conference platform 10 may automatically call a second software development kit (Software Development Kit, SDK) corresponding to the hardware conference, so that the target member joins the second conference.
In this embodiment, a first proprietary protocol is used in the first SDK for conferencing inside the software side. And a second private protocol is used in the second SDK and is used for enabling the user on the software side to be directly accessed into the conference on the hardware side based on the second private protocol. The first SDK and the second SDK are both installed in the software conference platform 10 in advance so that flexible call can be performed according to the needs.
In this embodiment, the method may further include step S330, when the preset conference type is the same as the software conference type, adding the target member to the second conference by calling a first software development kit corresponding to the software conference type, where the first software development kit is used for the target member to transmit data to the other members in the second conference based on the first private protocol.
It should be noted that, when any member participating in the first conference or the second conference needs to log out of the conference, log out may be automatically implemented, and SIP connection between the gateway apparatus 40 and the software conference platform 10 may be destroyed to implement resource recycling. In addition, the conference host can flexibly control the voice or video of the participant in the conference according to the requirement, for example, permit/prohibit the display of the picture of the target member, permit or prohibit the playing of the audio of the target member, etc. The control operation may be implemented by a corresponding control command, which is not particularly limited herein.
Referring to fig. 5, the embodiment of the present application further provides a conference joining apparatus 400, which can be applied to the software conference platform 10 described above, and is used for executing each step in the method. Conference joining device 400 includes at least one software functional module that may be stored in a memory module in the form of software or Firmware (Firmware) or cured in a conference platform Operating System (OS). The processing module is configured to execute executable modules stored in the storage module, such as software function modules and computer programs included in the conference joining apparatus 400.
The conference joining apparatus 400 may include a second acquisition unit 410 and a conference joining unit 420, and the functions of the respective units may be as follows:
a second obtaining unit 410, configured to obtain a preset conference type corresponding to a second conference when a target member requests to join the second conference, where the conference to which the target member belongs is a software conference type based on a first private protocol;
And a conference joining unit 420, configured to join the target member to the second conference by calling a second software development kit corresponding to the second conference when the preset conference type is different from the software conference type, where the second software development kit is used for the target member to transmit data to other members in the second conference based on a second private protocol, the second private protocol is a private protocol corresponding to the second conference, and the other members are members in the second conference except the target member.
Optionally, the conference joining unit 420 is further configured to join the target member to the second conference by calling a first software development kit corresponding to the software conference type when the preset conference type is the same as the software conference type, where the first software development kit is used for the target member to transmit data to the other members in the second conference based on the first private protocol.
In this embodiment, the processing module may be an integrated circuit chip with signal processing capability. The processing module may be a general purpose processor. For example, the processor may be a central processing unit (Central Processing Unit, CPU), application SPECIFIC INTEGRATED Circuit (ASIC), field-Programmable gate array (Field-Programmable GATE ARRAY, FPGA) or other Programmable logic device, discrete gate or transistor logic, discrete hardware components, or a combination of both, that may implement or perform the methods, steps, and logic blocks disclosed in embodiments of the present application.
The memory module may be, but is not limited to, random access memory, read only memory, programmable read only memory, erasable programmable read only memory, electrically erasable programmable read only memory, and the like. In this embodiment, the storage module may be used to store conference types, cache multimedia data, and the like. Of course, the storage module may also be used to store a program, and the processing module executes the program after receiving the execution instruction.
It should be noted that, for convenience and brevity of description, the specific working process of the conference adding apparatus 400 described above may refer to the corresponding process of each step in the foregoing method, and will not be described in detail herein.
The embodiment of the application also provides a computer readable storage medium. The computer-readable storage medium has stored therein a computer program which, when run on a computer, causes the computer to perform the conference joining method as described in the above embodiments.
From the foregoing description of the embodiments, it will be apparent to those skilled in the art that the present application may be implemented in hardware, or by means of software plus a necessary general hardware platform, and based on this understanding, the technical solution of the present application may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (may be a CD-ROM, a U-disc, a mobile hard disk, etc.), and includes several instructions for causing a computer device (may be a personal computer, a server, or a network device, etc.) to execute the method described in the respective implementation scenario of the present application.
In summary, in the present solution, when the preset conference type corresponding to the target member is different from the software conference type, it indicates that the preset conference type is a hardware conference type. At this time, the temporary conference based on the standard protocol is created for the target member, so that the target member can convert the private protocol corresponding to the hardware conference into the standard protocol of the temporary conference, and then transmit data to the software conference platform by the standard protocol to realize conference intercommunication, thereby avoiding the problem that conference intercommunication cannot be realized due to different private protocols.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus, system and method may be implemented in other manners as well. The above-described apparatus, system, and method embodiments are merely illustrative, for example, flow charts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions. In addition, functional modules in the embodiments of the present application may be integrated together to form a single part, or each module may exist alone, or two or more modules may be integrated to form a single part.
The above description is only an example of the present application and is not intended to limit the scope of the present application, and various modifications and variations will be apparent to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the protection scope of the present application.
Claims (7)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202111401030.XA CN114125362B (en) | 2021-11-19 | 2021-11-19 | Conference joining method, device, conference platform and computer readable storage medium |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202111401030.XA CN114125362B (en) | 2021-11-19 | 2021-11-19 | Conference joining method, device, conference platform and computer readable storage medium |
Publications (2)
Publication Number | Publication Date |
---|---|
CN114125362A CN114125362A (en) | 2022-03-01 |
CN114125362B true CN114125362B (en) | 2025-01-21 |
Family
ID=80440792
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN202111401030.XA Active CN114125362B (en) | 2021-11-19 | 2021-11-19 | Conference joining method, device, conference platform and computer readable storage medium |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN114125362B (en) |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN116582639B (en) * | 2023-07-13 | 2023-11-07 | 深圳星网信通科技股份有限公司 | Conference control method, terminal device and storage medium |
Family Cites Families (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6965614B1 (en) * | 1999-11-12 | 2005-11-15 | Nortel Networks Limited | Method and system for communications between different types of devices |
US7127487B1 (en) * | 2001-10-15 | 2006-10-24 | 3Com Corporation | System and method for sidebar functionality in a regular conference system |
CN100420194C (en) * | 2006-10-08 | 2008-09-17 | 华为技术有限公司 | A video conferencing system and its data transmission method and device |
US20130151623A1 (en) * | 2011-12-07 | 2013-06-13 | Reginald Weiser | Systems and methods for translating multiple client protocols via a conference bridge |
US9001180B2 (en) * | 2012-10-15 | 2015-04-07 | Bank Of America Corporation | Multiple-participant customer service conference |
US20150229766A1 (en) * | 2014-02-13 | 2015-08-13 | Synergem Technologies, Inc. | Methods and Systems for Routing Emergency Service Calls Background |
US9131112B1 (en) * | 2014-09-29 | 2015-09-08 | Edifire LLC | Dynamic signaling and resource allocation in secure media-based conferencing |
CN110062191B (en) * | 2019-04-17 | 2021-03-02 | 视联动力信息技术股份有限公司 | A method and server for multi-party group meeting based on Internet of Views |
-
2021
- 2021-11-19 CN CN202111401030.XA patent/CN114125362B/en active Active
Also Published As
Publication number | Publication date |
---|---|
CN114125362A (en) | 2022-03-01 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9716731B2 (en) | Consolidated peer-to-peer media sessions for audio and/or video communications | |
JP6141323B2 (en) | Call generation using additional terminals | |
CN103188300B (en) | The methods, devices and systems of VOIP phone are realized in cloud computing environment | |
CN103404132B (en) | Video communication method, home terminal, and home server | |
CN104125540B (en) | Multi-party call terminal and the method that one-to-one call is converted to from multi-party call | |
US10798138B2 (en) | Instant calling method, apparatus and system | |
US20150077509A1 (en) | System for a Virtual Multipoint Control Unit for Unified Communications | |
CN102308560B (en) | Transmission method and device of media stream data in cloud calculative system | |
CN104902111A (en) | Web RTC-based method, equipment and system for establishing multi party call | |
WO2011095007A1 (en) | Method and system for radio terminal to actively establish video conference | |
CN114245057B (en) | Audio and video call method, device, equipment and storage medium based on insurance business | |
CN111131641A (en) | Conference cascading method, device, server and readable storage medium | |
WO2018006678A1 (en) | Voice call method and apparatus | |
CN110996039B (en) | Electronic whiteboard sharing method, system and computer-readable storage medium | |
CN107181926A (en) | A kind of communication means, device and server | |
CN114125362B (en) | Conference joining method, device, conference platform and computer readable storage medium | |
CN103581607A (en) | Method for transmitting video stream to local endpoint host using remote camera device | |
CN107666396A (en) | A kind of multiple terminals meeting processing method and processing device | |
US11070665B2 (en) | Voice over internet protocol processing method and related network device | |
CN115604045A (en) | Online conference fusion method and device and computer storage medium | |
TW201528821A (en) | System and method of controlling video conference based on IP | |
US20060031343A1 (en) | Integrated instant message system with gateway functions and method for implementing the same | |
CN113923396A (en) | Remote desktop control method, device and medium based on video conference scene | |
US10412124B2 (en) | Initiating a server-directed communication session | |
CN117596231B (en) | Communication method, terminal device, system and 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 | ||
CB02 | Change of applicant information | ||
CB02 | Change of applicant information |
Address after: Room 1308, 13th floor, East Tower, 33 Fuxing Road, Haidian District, Beijing 100082 Applicant after: China Telecom Digital Intelligence Technology Co.,Ltd. Address before: Room 1308, 13th floor, East Tower, 33 Fuxing Road, Haidian District, Beijing 100082 Applicant before: CHINA TELECOM GROUP SYSTEM INTEGRATION Co.,Ltd. |
|
GR01 | Patent grant | ||
GR01 | Patent grant |