Conference joining method, device, conference platform and computer readable storage medium

Abstract

This application provides a meeting joining method, apparatus, meeting platform, and computer-readable storage medium. The method includes: obtaining a preset meeting type corresponding to the meeting to which the target member to join the first meeting belongs, based on a meeting joining request, wherein the first meeting is a software meeting type based on a first private protocol; when the preset meeting type is different from the software meeting type, creating a temporary meeting corresponding to the target member, and sending the meeting number corresponding to the temporary meeting to the hardware terminal corresponding to the target member, wherein the temporary meeting is a meeting based on a preset standard protocol; receiving a call request sent by the hardware terminal based on the meeting number; establishing a communication connection with the hardware terminal based on the call request, and joining the target member to the first meeting through the temporary meeting. In this way, meeting interoperability between the hardware side and the software side can be realized, thereby avoiding the problem of meeting interoperability between the hardware side and the software side due to different private protocols.

Description

Technical Field

[0001] The present application relates to the field of data communication technology, and in particular to a conference joining method, device, conference platform and computer-readable storage medium. Background Art

[0002] The current types of conferences usually include software conference types and hardware conference types. Software conferences are usually presented in the form of desktop applications and are mainly aimed at public customers. Software conference platforms are mainly built based on a private protocol based on the SVC (Scalable Video Coding) architecture. Hardware and software conferences are usually presented in physical dedicated conference terminals and are mainly aimed at government and enterprise customers. Hardware and software conference platforms are mainly built based on another private protocol based on the AVC (Advanced Video Coding) / SVC hybrid architecture.

[0003] Since the software conference platform and the hardware conference platform use different private protocols, the two conference platforms are currently unable to communicate with each other, making it impossible for users of the two types of conferences to hold meetings in the same conference room. Summary of the invention

[0004] The purpose of the embodiments of the present application is to provide a conference joining method, device, conference platform and computer-readable storage medium, which can enable users of software conferences and hardware conferences to enter the same conference for communication.

[0005] In order to achieve the above purpose, the embodiments of the present application are implemented in the following manner:

[0006] In a first aspect, an embodiment of the present application provides a conference joining method, the method comprising: obtaining, according to a conference joining request, a preset conference type corresponding to a conference to which a target member who wishes to join a first conference belongs, wherein the first conference belongs to a software conference type based on a first private protocol; when the preset conference type is different from the software conference type, creating a temporary conference corresponding to the target member, and sending the conference number corresponding to the temporary conference to a hardware terminal corresponding to the target member, wherein the temporary conference is a conference based on a preset standard protocol; receiving a call request sent by the hardware terminal based on the conference number; based on the call request, establishing a communication connection with the hardware terminal, and joining the target member to the first conference through the temporary conference.

[0007] In the above implementation, when the preset conference type corresponding to the target member is different from the software conference type, it means that the preset conference type is a hardware conference type. At this time, by creating a temporary 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 temporary conference, and then transmit data to the software conference platform using the standard protocol to achieve conference intercommunication, thereby avoiding the problem of being unable to achieve conference intercommunication due to different private protocols.

[0008] In combination with the first aspect, in some optional embodiments, the method also 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.

[0009] In combination with the first aspect, in some optional embodiments, the method also includes: converting the multimedia data transmitted by other members in the first conference based on the first private protocol into multimedia data of the preset standard protocol, wherein the other members are members of the first conference other than the target member; sending the converted multimedia data to the gateway device corresponding to the hardware terminal through the temporary conference, so that the gateway device converts the converted multimedia data into multimedia data of the second private protocol corresponding to the target member, and the gateway device sends the multimedia data of the second private protocol to the hardware terminal.

[0010] In combination with the first aspect, in some optional implementations, before obtaining the preset conference type corresponding to the conference to which the target member who wants to join 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.

[0011] In a second aspect, the present application also provides a conference joining method, the method comprising: when a target member requests to join a second conference, obtaining 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; when the preset conference type is different from the software conference type, joining the target member to the second conference by calling a second software development kit corresponding to the second conference, wherein 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 of the second conference other than the target member.

[0012] In the above-mentioned implementation, by calling the second software development kit, the target members 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 uses the second private protocol to communicate and achieve conference intercommunication, avoiding the inability to conduct conference intercommunication due to different private protocols.

[0013] In conjunction with the second aspect, in some optional implementations, the method further includes:

[0014] When the preset conference type is the same as the software conference type, the target member is added to 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 the target member to transmit data to the other members in the second conference based on the first private protocol.

[0015] In a third aspect, the present application further provides a conference joining device, the device comprising:

[0016] A first acquisition unit, configured to acquire, according to a conference joining request, a preset conference type corresponding to a conference to which a target member who wants to join a first conference belongs, wherein the first conference belongs to a software conference type based on a first private protocol;

[0017] A creating unit, configured to create a temporary meeting corresponding to the target member when the preset meeting type is different from the software meeting type, and send a meeting number corresponding to the temporary meeting to a hardware terminal corresponding to the target member, wherein the temporary meeting is a meeting based on a preset standard protocol;

[0018] A receiving unit, configured to receive a call request sent by the hardware terminal based on the conference number;

[0019] A communication establishing unit is used to establish a communication connection with the hardware terminal based on the call request, and add the target member to the first conference through the temporary conference.

[0020] In a fourth aspect, the present application further provides a conference joining device, the device comprising:

[0021] A second acquisition unit is used to acquire a preset conference type corresponding to the second conference when the target member requests to join the second conference, wherein the conference to which the target member belongs is a software conference type based on the first private protocol;

[0022] A conference joining unit, used for, when the preset conference type is different from the software conference type, joining the target member to the second conference by calling a second software development kit corresponding to the second conference, wherein 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 of the second conference other than the target member.

[0023] In a fourth aspect, the present application further provides a conference platform, comprising a processor and a memory coupled to each other, wherein the memory stores a computer program, and when the computer program is executed by the processor, the conference platform executes the method of the first aspect or the second aspect mentioned above.

[0024] In a fifth aspect, the present application further provides a computer-readable storage medium, wherein a computer program is stored in the computer-readable storage medium. When the computer program is executed on a computer, the computer executes the method of the first aspect or the second aspect as described above. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the embodiments of the present application will be briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0026] Figure 1 A schematic diagram of a scenario in which a software conference and a hardware conference are interconnected according to an embodiment of the present application.

[0027] Figure 2 This is one of the flowcharts of the conference joining method provided in the embodiment of the present application.

[0028] Figure 3 This is one of the block diagrams of the conference joining device provided in the embodiment of the present application.

[0029] Figure 4 The second flowchart of the conference joining method provided in the embodiment of the present application.

[0030] Figure 5 This is a second block diagram of the conference joining device provided in an embodiment of the present application.

[0031] Icons: 10-software conference platform; 11-client; 12-client; 20-hardware conference platform; 21-hardware terminal; 22-hardware terminal; 30-border 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

[0032] The technical solutions in the embodiments of the present application will be described below in conjunction with the accompanying drawings in the embodiments of the present application. It should be noted that the terms "first", "second", etc. are only used to distinguish the description and cannot be understood as indicating or implying relative importance. In the absence of conflict, the following embodiments and features in the embodiments can be combined with each other.

[0033] First embodiment

[0034] The present application provides a conference platform, which may include a processing module and a storage module. The storage module stores a computer program, and when the computer program is executed by the processing module, the conference platform can execute the corresponding steps in the following conference joining method.

[0035] Please refer to Figure 1 In this embodiment, the conference platform may be a software conference platform 10, or a hardware conference platform 20. The conference platform may be a host or server for setting up a conference, and may be flexibly configured according to actual conditions.

[0036] The software conference platform 10 can be connected to one or more clients for establishing a software conference, and the hardware conference platform 20 can be connected to one or more hardware terminals for establishing a hardware conference.

[0037] The client can be understood as the terminal of the user participating in the software conference, which can be but not limited to a personal computer, tablet computer, smart phone, etc.

[0038] The hardware terminal may be a terminal dedicated to hardware conferencing that implements video and audio processing and network communication based on DSP (Digital Signal Processing) and embedded software, and is a terminal well known to those skilled in the art.

[0039] For example, please refer again to Figure 1 The software conference platform 10 can be connected to the client 11 and the client 12 in communication. The hardware conference platform 20 can be connected to the hardware terminal 21 and the hardware terminal 22 in communication.

[0040] In this embodiment, the software conference platform 10 can be connected to the session border controller (SBC) through a connector, and then the session border controller 30 establishes a communication connection with the gateway device 40. The gateway device 40 and the session border controller 30 can serve as a bridge for communication between the hardware conference platform 20 and the software conference platform 10, respectively.

[0041] In this embodiment, the gateway device 40 may be a SIP (Session initialization Protocol) gateway, which may convert the data of the hardware conference platform 20 based on the private protocol into the data of the SIP protocol. The connector may be a Room Connector (RC), which may be used to convert the private protocol of the software conference platform 10 into a standard protocol. The standard protocol may be flexibly determined according to actual conditions, such as the SIP protocol.

[0042] It should be noted that the connector and the border session controller 30 may be integrated into the software conference platform 10, or exist independently of the software conference platform 10. For example, the connector and the border session controller 30 may be used as an independent service device.

[0043] In this embodiment, the enabling platform can be understood as a software function module deployed on the software conference platform 10, which is an independent account management and conference management scheduling platform. All client conference functions can be implemented by calling the interface of the enabling platform.

[0044] Please refer to Figure 2 The present application provides a 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. When a user on the hardware side wants to join a conference created by the software side, the method may include the following steps:

[0045] Step S110, according to the conference joining request, obtaining a preset conference type corresponding to the conference to which the target member who wants to join the first conference belongs, wherein the first conference belongs to a software conference type based on a first private protocol;

[0046] Step S120, when the preset conference type is different from the software conference type, creating a temporary conference corresponding to the target member, and sending the conference number corresponding to the temporary conference to the hardware terminal corresponding to the target member, wherein the temporary conference is a conference based on a preset standard protocol;

[0047] Step S130, receiving a call request sent by the hardware terminal based on the conference number;

[0048] Step S140: establishing a communication connection with the hardware terminal based on the call request, and adding the target member to the first conference through the temporary conference.

[0049] In the above implementation, 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 a temporary 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 temporary conference, and then transmit the data to the software conference platform 10 using the standard protocol to achieve conference intercommunication, thereby avoiding the problem of being unable to achieve conference intercommunication between the software test and the hardware side due to different private protocols.

[0050] The following is a detailed description of each step of the method:

[0051] Before step S110, the method may include the step of creating a first meeting. For example, before step S110, the method may include:

[0052] According to the received conference creation request, the first conference based on the software conference type is created.

[0053] Understandably, the user who initiates the conference creation request is usually the conference host. The user can initiate the conference creation request to the software conference platform 10 through the corresponding APP (Application) of the client.

[0054] After receiving the conference request, the software conference platform 10 can 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 users of other clients as members to participate in the first conference according to actual conditions.

[0055] For example, the host can invite the user at the client 12 to join the first meeting through the client 11. The members of the first meeting can communicate based on the first private protocol. The first private protocol can be flexibly determined according to actual conditions and is not specifically limited here.

[0056] In step S110, the target member refers to a user who wants to join the first conference. For example, if a user wants to join the first conference through the hardware terminal 21, the user is the target member. At this time, the target member can input the conference number of the first conference through the hardware terminal 21, and then the hardware terminal 21 generates a conference joining request based on the conference number of the first conference.

[0057] The conference joining request may carry a conference type that represents the conference to which the hardware terminal belongs. In this case, the conference type of the conference to which the target member or hardware terminal belongs is the hardware conference type.

[0058] It should be noted that the target member performs data communication in the hardware conference using the second private protocol. The second private protocol is different from the first private protocol and can be flexibly determined according to actual conditions.

[0059] After sending a conference joining request, the hardware terminal can call the enabling platform in the software conference platform 10. 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 it with the software conference type of the first conference. Since the preset conference type at this time is the hardware conference type, the enabling platform can conclude that the preset conference type is different from the software conference type.

[0060] In step S120, when the preset conference type is different from the software conference type, the hardware conference platform 20 can send a request to the enabling platform to create a temporary conference by calling the signaling service. After receiving the request, the enabling platform or the software conference platform 10 can create a temporary conference for the target member and return the conference number corresponding to the temporary conference to the hardware terminal corresponding to the target member.

[0061] Among them, one temporary conference consumes one RC resource. In this process, the hardware conference platform 20 can convert the second private protocol used by itself into the SIP protocol through the gateway device 40. In addition, the temporary conference uses a preset standard protocol for data communication. The preset standard protocol can be flexibly determined according to actual conditions, such as the SIP protocol.

[0062] Understandably, the temporary conference can convert the data based on the second private protocol sent by the target member into data of the preset standard protocol for transmission, so as to avoid the data transmitted by the target member being the second private protocol and unable to be sent to the software conference platform 10.

[0063] If N hardware terminals apply to join the same software conference, N temporary conferences will be generated so that the conference host on the software side can control the video streams generated by these N hardware terminals in different ways. Where N is an integer greater than or equal to 1. For example, when hardware terminal 21 and hardware terminal 22 both join the first conference, at this time, the host can hide the screen of hardware terminal 21 and display the screen of hardware terminal 22; or hide the screen of hardware terminal 22 and display the screen of hardware terminal 21.

[0064] In step S130, the call request is a request issued by the hardware terminal when receiving the conference number of the temporary conference returned by the software conference platform 10. The call request is used for the software conference platform 10 to add the target member to the first conference through the temporary conference.

[0065] For example, please refer again to Figure 1 The call request is sent by the hardware terminal 21 and then transmitted to the gateway device 40, which calls the IP address of the border session controller 30 based on the temporary conference number to establish a SIP connection with the software conference platform 10.

[0066] In step S140 , based on the call request, a SIP connection between the border session controller 30 and the gateway device 40 may be established, so that the software conference platform 10 may communicate with the hardware device through the border session controller 30 , the gateway device 40 , and the hardware conference platform 20 .

[0067] After the target member joins the first conference, the method may further include:

[0068] Receiving multimedia data based on the preset standard protocol sent by the target member through the temporary conference;

[0069] Converting the multimedia data into multimedia data of the first private protocol;

[0070] The converted multimedia data is sent to other members in the first conference except the target member.

[0071] Understandably, after the target member joins the first conference, the data sent by the target member based on the hardware terminal can be sent to other members in the first conference through the temporary conference. Other members are members in the first conference excluding the target member.

[0072] For example, please refer again to Figure 1 After the target member joins the first conference, the hardware terminal 21 can send multimedia data to the hardware conference platform 20 using the second private protocol. Then, the hardware conference platform 20 converts the multimedia data into multimedia data of the SIP protocol through the gateway device 40, and sends it to the software conference platform 10 through the temporary conference. The software conference platform 10 then converts the multimedia data of the SIP protocol into multimedia data of the first private protocol, and sends it to the corresponding clients of other users. For example, it is sent to client 11 and client 12. In this way, the intercommunication between the hardware-side conference and the software-side conference can be achieved.

[0073] In this embodiment, the method may further include:

[0074] Converting multimedia data transmitted by other members in the first conference based on the first private protocol into multimedia data of the preset standard protocol, wherein the other members are members in the first conference excluding the target member;

[0075] Through the temporary conference, the converted multimedia data is sent to the gateway device 40 corresponding to the hardware terminal, so that the gateway device 40 converts the converted multimedia data into multimedia data of the 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.

[0076] For example, please refer again to Figure 1 After the target members join the first conference, the user of the client 11 can send his own multimedia data (such as audio and video streams) to the software conference platform 10 based on the first private protocol; then the software conference platform 10 converts the multimedia data into data based on the SIP protocol, and sends the multimedia data based on the SIP protocol to the gateway device 40 through a temporary conference. The gateway device 40 then converts the multimedia data of the SIP protocol into multimedia data of the second private protocol and sends it to the hardware conference platform 20. The hardware conference platform 20 then sends the multimedia data of the second private protocol to the hardware terminal 21 and the hardware terminal 22. In this way, the intercommunication between the software conference and the hardware conference can be achieved.

[0077] Please refer to Figure 3 The embodiment of the present application also provides a conference joining device 200, which can be applied to the above-mentioned conference platform to execute each step in the method. The conference joining device 200 includes at least one software function module that can be stored in the storage module in the form of software or firmware or solidified in the operating system (OS) of the conference platform. The processing module is used to execute the executable module stored in the storage module, such as the software function module and computer program included in the conference joining device 200.

[0078] The conference joining device 200 may include a first acquisition unit 210, a creation unit 220, a receiving unit 230, and a communication establishment unit 240. The functions of each unit may be as follows:

[0079] The first acquisition unit 210 is used to acquire, according to the conference joining request, a preset conference type corresponding to the conference to which the target member who wants to join the first conference belongs, wherein the first conference belongs to a software conference type based on a first private protocol;

[0080] A creation unit 220, configured to create a temporary meeting corresponding to the target member when the preset meeting type is different from the software meeting type, and send a meeting number corresponding to the temporary meeting to a hardware terminal corresponding to the target member, wherein the temporary meeting is a meeting based on a preset standard protocol;

[0081] The receiving unit 230 is used to receive a call request sent by the hardware terminal based on the conference number;

[0082] The communication establishing unit 240 is used to establish a communication connection with the hardware terminal based on the call request, and add the target member to the first conference through the temporary conference.

[0083] Optionally, the conference joining device 200 may also include a conversion unit and a sending unit. The receiving unit 230 is also used to receive multimedia data based on the preset standard protocol sent by the target member through the temporary conference; the conversion unit is used to convert the multimedia data into multimedia data of the first private protocol; and the sending unit is used to send the converted multimedia data to other members of the first conference except the target member.

[0084] Optionally, the conversion unit is further used to convert multimedia data transmitted by other members in the first conference based on the first private protocol into multimedia data of the preset standard protocol, wherein the other members are members of the first conference excluding the target member;

[0085] The sending unit is also used to send the converted multimedia data 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 the 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.

[0086] Optionally, before the first obtaining unit 210 obtains the preset conference type corresponding to the conference to which the target member who wants to join the first conference 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.

[0087] It should be noted that those skilled in the art can clearly understand that for the convenience and simplicity of description, the specific working process of the conference joining device 200 described above can refer to the corresponding process of each step in the aforementioned method, and will not be repeated here.

[0088] Second embodiment

[0089] Please refer to Figure 4The present application also provides another conference joining method, which can be applied to the above-mentioned software conference platform 10, and the software conference platform 10 executes or implements each step in the method. Compared with the first embodiment, in the second embodiment, a user on the software side wants to join a conference created by the hardware side. The method may include the following steps:

[0090] Step S310, when the target member requests to join the second conference, obtaining 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 the first private protocol;

[0091] Step S320, when the preset conference type is different from the software conference type, the target member is added to the second conference by calling a second software development kit corresponding to the second conference, wherein 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 of the second conference other than the target member.

[0092] In the above-mentioned implementation, by calling the second software development kit, the target members 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 uses the second private protocol to communicate and achieve conference intercommunication, avoiding the inability to conduct conference intercommunication due to different private protocols.

[0093] The steps of the method in the second embodiment are described in detail below:

[0094] Before step S310, the conference host can create a second conference of a hardware conference type through a hardware terminal and communicate using a second private protocol corresponding to the hardware conference type; or create a second conference of a software conference type through a client and communicate using a first private protocol corresponding to the software conference type.

[0095] In step S310, the preset conference type corresponding to the second conference can be flexibly determined according to the actual situation, and can be a hardware conference type or a software conference type. The target members are the corresponding conference participants on the client APP side.

[0096] In step S320, if the preset conference type is different from the software conference type, it means that the preset conference type is a hardware conference type. At this time, the second conference that the target member wants to join is a hardware conference. At the same time, the software conference platform 10 can automatically call the second software development kit (SDK) corresponding to the hardware conference to enable the target member to join the second conference.

[0097] In this embodiment, the first SDK uses a first private protocol for internal conferences on the software side. The second SDK uses a second private protocol for directly connecting users on the software side to conferences on the hardware side based on the second private protocol. Both the first SDK and the second SDK are pre-installed in the software conference platform 10 so that they can be flexibly called according to needs.

[0098] In this embodiment, the method may also 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, wherein 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.

[0099] It should be noted that when any member participating in the first conference or the second conference needs to exit the conference, the exit can be automatically realized, and the SIP connection between the gateway device 40 and the software conference platform 10 can be destroyed to realize resource recovery. In addition, the conference host can flexibly control the voice or video of the participating members in the conference according to the needs, for example, allowing / prohibiting the display of the target member's picture, allowing or prohibiting the playback of the target member's audio, etc. The control operation can be realized through the corresponding control command, which is not specifically limited here.

[0100] Please refer to Figure 5 The embodiment of the present application also provides a conference joining device 400, which can be applied to the above-mentioned software conference platform 10 to execute each step in the method. The conference joining device 400 includes at least one software function module that can be stored in the storage module in the form of software or firmware or fixed in the operating system (OS) of the conference platform. The processing module is used to execute the executable module stored in the storage module, such as the software function module and computer program included in the conference joining device 400.

[0101] The conference joining device 400 may include a second acquisition unit 410 and a conference joining unit 420, and the functions of each unit may be as follows:

[0102] The second acquisition unit 410 is used to acquire a preset conference type corresponding to the second conference when the target member requests to join the second conference, wherein the conference to which the target member belongs is a software conference type based on the first private protocol;

[0103] The conference joining unit 420 is used 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, wherein 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 of the second conference other than the target member.

[0104] Optionally, the conference joining unit 420 is also used to: when the preset conference type is the same as the software conference type, join the target member to 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 the target member to transmit data to the other members in the second conference based on the first private protocol.

[0105] In this embodiment, the processing module may be an integrated circuit chip having the ability to process signals. The above-mentioned processing module may be a general-purpose processor. For example, the processor may be a central processing unit (CPU), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, and may implement or execute the disclosed methods, steps and logic block diagrams in the embodiments of the present application.

[0106] The storage module may be, but is not limited to, a random access memory, a read-only memory, a programmable read-only memory, an erasable programmable read-only memory, an electrically erasable programmable read-only memory, etc. In this embodiment, the storage module may be used to store conference types, cache multimedia data, etc. Of course, the storage module may also be used to store programs, and the processing module executes the program after receiving the execution instruction.

[0107] It should be noted that those skilled in the art can clearly understand that for the convenience and brevity of description, the specific working process of the conference joining device 400 described above can refer to the corresponding process of each step in the aforementioned method, and will not be repeated here.

[0108] The embodiment of the present application also provides a computer-readable storage medium. The computer-readable storage medium stores a computer program, and when the computer program is executed on a computer, the computer executes the conference joining method described in the above embodiment.

[0109] Through the description of the above implementation methods, technical personnel in this field can clearly understand that the present application can be implemented by hardware, and can also be implemented by means of software plus a necessary general hardware platform. Based on such an understanding, the technical solution of the present application can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.), including a number of instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods described in each implementation scenario of the present application.

[0110] In summary, in this solution, when the preset conference type corresponding to the target member is different from the software conference type, it means that the preset conference type is a hardware conference type. At this time, by creating a temporary 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 temporary conference, and then transmit data to the software conference platform using the standard protocol to achieve conference intercommunication, thereby avoiding the problem of being unable to achieve conference intercommunication due to different private protocols.

[0111] In the embodiments provided in the present application, it should be understood that the disclosed device, system and method can also be implemented in other ways. The above-described device, system and method embodiments are merely schematic, for example, the flowchart and block diagram in the accompanying drawings show the possible architecture, function and operation of the system, method and computer program product according to the multiple embodiments of the present application. In this regard, each box in the flowchart or block diagram can represent a part of a module, a program segment or a code, and a part of the module, program segment or code contains one or more executable instructions for implementing the specified logical function. It should also be noted that each box in the block diagram and / or the flowchart, and the combination of the boxes in the block diagram and / or the flowchart can be implemented by a dedicated hardware-based system that performs the specified function or action, or can be implemented by a combination of dedicated hardware and computer instructions. In addition, each functional module in each embodiment of the present application can be integrated together to form an independent part, or each module can exist separately, or two or more modules can be integrated to form an independent part.

[0112] The above description is only an embodiment of the present application and is not intended to limit the protection scope of the present application. For those skilled in the art, the present application may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims

1. A conference joining method, characterized in that: Applied to a software conference platform, the method comprises: According to the conference joining request, obtaining a preset conference type corresponding to a conference to which a target member who wants to join the first conference belongs, wherein the first conference belongs to a software conference type based on a first private protocol; When the preset conference type is different from the software conference type, based on the request for creating a temporary conference sent by the hardware conference platform by calling the signaling service, a temporary conference corresponding to the target member is created, and the conference number corresponding to the temporary conference is sent to the hardware terminal corresponding to the target member, wherein the temporary conference is a conference based on a preset standard protocol; receiving a call request sent by the hardware terminal based on the conference number; Based on the call request, establishing a communication connection with the hardware terminal, and adding the target member to the first conference through the temporary conference; Wherein, establishing a communication connection with the hardware terminal includes: A communication connection with a gateway device corresponding to the hardware terminal is established through a border session controller, wherein the border session controller is connected to the software conference platform through a connector.

2. The method according to claim 1, characterized in that The method further comprises: 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; The converted multimedia data is sent to other members in the first conference except the target member.

3. The method according to claim 1, characterized in that: The method further comprises: Converting multimedia data transmitted by other members in the first conference based on the first private protocol into multimedia data of the preset standard protocol, wherein the other members are members in the first conference excluding the target member; Through the temporary conference, the converted multimedia data is sent to the gateway device corresponding to the hardware terminal, so that the gateway device converts the converted multimedia data into multimedia data of the second private protocol corresponding to the target member, and the gateway device sends the multimedia data of the second private protocol to the hardware terminal.

4. The method according to claim 1, characterized in that: Before obtaining the preset conference type corresponding to the conference to which the target member who wants to join the first conference belongs, the method further includes: According to the received conference creation request, the first conference based on the software conference type is created.

5. A conference joining device, characterized in that: Applied to a software conference platform, the device comprises: A first acquisition unit, configured to acquire, according to a conference joining request, a preset conference type corresponding to a conference to which a target member who wants to join a first conference belongs, wherein the first conference belongs to a software conference type based on a first private protocol; A creation unit, configured to create a temporary meeting corresponding to the target member based on a request for creating a temporary meeting sent by the hardware conference platform by calling a signaling service when the preset conference type is different from the software conference type, and send a conference number corresponding to the temporary meeting to a hardware terminal corresponding to the target member, wherein the temporary meeting is a meeting based on a preset standard protocol; A receiving unit, configured to receive a call request sent by the hardware terminal based on the conference number; A communication establishing unit, configured to establish a communication connection with the hardware terminal based on the call request, and add the target member to the first conference through the temporary conference; Wherein, establishing a communication connection with the hardware terminal includes: A communication connection with a gateway device corresponding to the hardware terminal is established through a border session controller, wherein the border session controller is connected to the software conference platform through a connector.

6. A conference platform, characterized in that: The conference platform includes a processor and a memory coupled to each other, wherein a computer program is stored in the memory. When the computer program is executed by the processor, the conference platform executes the method according to any one of claims 1 to 4.

7. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed on a computer, the computer is enabled to execute the method according to any one of claims 1 to 4.

Images