CN116582639A - Conference control method, terminal device and storage medium - Google Patents

Conference control method, terminal device and storage medium Download PDF

Info

Publication number
CN116582639A
CN116582639A CN202310856488.7A CN202310856488A CN116582639A CN 116582639 A CN116582639 A CN 116582639A CN 202310856488 A CN202310856488 A CN 202310856488A CN 116582639 A CN116582639 A CN 116582639A
Authority
CN
China
Prior art keywords
conference
sdk
terminal
target
type
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
CN202310856488.7A
Other languages
Chinese (zh)
Other versions
CN116582639B (en
Inventor
唐昶荣
吴超杰
喇建国
陈志才
胡小辉
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Shenzhen Star Network Communication Technology Co ltd
Original Assignee
Shenzhen Star Network Communication Technology Co ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Shenzhen Star Network Communication Technology Co ltd filed Critical Shenzhen Star Network Communication Technology Co ltd
Priority to CN202310856488.7A priority Critical patent/CN116582639B/en
Publication of CN116582639A publication Critical patent/CN116582639A/en
Application granted granted Critical
Publication of CN116582639B publication Critical patent/CN116582639B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

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
    • H04N7/155—Conference systems involving storage of or access to video conference sessions
    • 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
    • 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/60—Network streaming of media packets
    • H04L65/75—Media network packet handling
    • H04L65/756—Media network packet handling adapting media to device capabilities
    • 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/80—Responding to QoS

Abstract

The application discloses a conference control method, terminal equipment and a storage medium, wherein the conference control method comprises the following steps: determining a conference identifier based on a trigger action received by a terminal, and acquiring equipment information corresponding to the terminal; determining a conference type according to the conference identifier, and determining a target SDK according to the equipment information and the conference type; and running the target SDK and entering a target conference based on the conference identification. And generating application terminals by integrating SDKs of all conference types, so that conferences of different conference types can be started or added based on the application terminals, conference operation steps are reduced, and conference efficiency is improved.

Description

Conference control method, terminal device and storage medium
Technical Field
The present application relates to the field of internet technologies, and in particular, to a conference control method, a terminal device, and a storage medium.
Background
In order to meet market demands, different manufacturers develop video conference platforms with different video functions, and users can choose to purchase and use video conference platforms developed by corresponding manufacturers according to the demands. However, the need for enterprises or units to conduct video conferences is diverse, and therefore, it is often necessary to purchase and install video conference platforms developed by a plurality of vendors. When actually performing the video conference, the video conference platform of the corresponding manufacturer is flexibly used according to the conference requirement, and the use modes of the video conference platforms developed by different manufacturers are different, so that the video conference operation steps are complicated.
The foregoing is provided merely for the purpose of facilitating understanding of the technical solutions of the present application and is not intended to represent an admission that the foregoing is prior art.
Disclosure of Invention
The embodiment of the application aims to solve the technical problem that the operation steps are complicated when a video conference is carried out by providing a conference control method, terminal equipment and a computer readable storage medium.
In order to achieve the above object, an embodiment of the present application provides a method for controlling a conference, including:
determining a conference identifier based on a trigger action received by a terminal, and acquiring equipment information corresponding to the terminal;
determining a conference type according to the conference identifier, and determining a target SDK according to the equipment information and the conference type;
and running the target SDK and entering a target conference based on the conference identification.
Optionally, after the step of running the target SDK and entering a target conference based on the conference identification, the method includes:
when receiving audio and video data sent by a first terminal based on the target conference, determining a data format corresponding to a second terminal according to a target conference type corresponding to the second terminal, wherein the first terminal and the second terminal are remote terminals accessing the target conference based on different conference types;
and converting the audio and video data into source data corresponding to the second terminal according to the data format so as to forward the audio and video data to the second terminal.
Optionally, before the step of converting the audio/video data into source data corresponding to the second terminal according to the data format to forward the audio/video data to the second terminal, the method includes:
when audio and video data sent by a first terminal are received based on the target conference, determining a first conference type corresponding to the first terminal according to a first conference identifier of the first terminal, and determining a second conference type corresponding to the second terminal according to a second conference identifier of the second terminal;
forwarding the audio and video data to the second terminal when the first conference type is the same as the second conference type;
and when the first conference type is different from the second conference type, executing the step of determining the data format corresponding to the second terminal according to the target conference type corresponding to the second terminal.
Optionally, the step of determining the conference type according to the conference identifier and determining the target SDK according to the device information and the conference type includes:
acquiring an SDK list corresponding to the equipment information;
determining the target SDK associated with the conference type based on the SDK list;
and running the target SDK and entering a target conference based on the conference identification.
Optionally, the step of obtaining the SDK list corresponding to the device information includes:
generating an SDK list request according to the equipment information, and sending the SDK list request to a server;
receiving the SDK list fed back by the server based on the SDK list request; or, reading the SDK list stored in the local database.
Optionally, after the step of obtaining the SDK list corresponding to the device information, the method includes:
acquiring SDKs corresponding to all conference types in the SDK list;
acquiring a corresponding packing template and a packing program of the packing template according to the conference type;
and packaging the SDKs corresponding to the conference types according to the packaging program, and storing the SDKs in association with the conference types in the SDK list.
Optionally, after the step of packaging the SDKs corresponding to the conference types according to the packaging program and storing the SDKs in association with the conference types in the SDK list, the method includes:
detecting the latest SDK version of the SDK corresponding to each conference type;
acquiring SDK versions of SDKs corresponding to the conference types in the SDK list;
and when the SDK version is inconsistent with the latest SDK version, acquiring the SDK corresponding to the latest SDK version, and executing the steps of packaging the SDKs corresponding to the conference types according to the packaging program and storing the SDKs in association with the conference types in the SDK list.
Optionally, the method for controlling the conference further includes:
when a conference creation process is triggered, determining conference participants or conference participant terminals based on the triggering actions, and determining target conference types according to the conference participants or the conference participant terminals; and/or when triggering a conference creation process, determining the target conference type based on the trigger action;
and running the SDK corresponding to the target conference type and generating a conference identification corresponding to the target conference type.
In addition, in order to achieve the above object, the present application further provides a terminal device, including: the conference control system comprises a memory, a processor and a conference control program stored in the memory and capable of running on the processor, wherein the conference control program realizes the steps of the conference control method when being executed by the processor.
In addition, in order to achieve the above object, the present application also provides a computer-readable storage medium having stored thereon a control program for a conference, which when executed by a processor, implements the steps of the control method for a conference as described above.
According to the conference control method provided by the embodiment of the application, the terminal equipment and the computer readable storage medium are used for determining the conference identification based on the trigger action received by the terminal, acquiring the equipment information corresponding to the terminal, determining the conference type according to the conference identification, determining the target SDK according to the equipment information and the conference type, finally operating the target SDK, and entering the target conference based on the conference identification. And generating application terminals by integrating SDKs of all conference types, so that conferences of different conference types can be started or added based on the application terminals, conference operation steps are reduced, and conference efficiency is improved.
Drawings
FIG. 1 is a flow chart of an embodiment of a method for controlling a conference according to the present application;
fig. 2 is a schematic diagram of a refinement flow of step S30 in a second embodiment of the conference control method of the present application;
fig. 3 is a schematic diagram of a refinement flow of step S20 in a third embodiment of the conference control method of the present application;
fig. 4 is a schematic diagram of a terminal structure of a hardware running environment according to an embodiment of the present application.
The achievement of the objects, functional features and advantages of the present application will be further described with reference to the accompanying drawings, in conjunction with the embodiments.
Detailed Description
It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the application.
In order to meet market demands, different manufacturers develop video conference platforms with different video functions, and users can choose to purchase and use video conference platforms developed by corresponding manufacturers according to the demands. However, the need for enterprises or units to conduct video conferences is diverse, and therefore, it is often necessary to purchase and install video conference platforms developed by a plurality of vendors. When actually performing the video conference, the video conference platform of the corresponding manufacturer is flexibly used according to the conference requirement, and the use modes of the video conference platforms developed by different manufacturers are different, so that the technical problems of complicated operation steps of the video conference and reduction of conference efficiency are caused.
In order to solve the above-mentioned drawbacks of the related art, the present application provides a method for controlling a conference, which mainly comprises the following steps:
the method comprises the steps of determining a conference identifier based on a trigger action received by a terminal, acquiring equipment information corresponding to the terminal, determining a conference type according to the conference identifier, determining a target SDK according to the equipment information and the conference type, finally operating the target SDK, and entering a target conference based on the conference identifier. And generating application terminals by integrating SDKs of all conference types, so that conferences of different conference types can be started or added based on the application terminals, conference operation steps are reduced, and conference efficiency is improved.
In order to better understand the above technical solution, exemplary embodiments of the present application will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present application are shown in the drawings, it should be understood that the present application may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the application to those skilled in the art.
Referring to fig. 1, in an embodiment of the method for controlling a conference according to the present application, the method for controlling a conference includes the following steps:
step S10: determining a conference identifier based on a trigger action received by a terminal, and acquiring equipment information corresponding to the terminal;
the application collects SDKs (Software Development Kit, software development tools) of different manufacturers or platforms in advance, integrates and packages SDKs of the same manufacturer or brand by adopting a packaging tool, then stores the SDKs to generate application terminals, and users can start conferences of different conference types by downloading the application terminals without downloading application terminals of corresponding conference types, thereby reducing conference operation steps and improving conference efficiency.
In this embodiment, the user may select a meeting type corresponding to a meeting that is desired to be added or created, or input a meeting identifier received in advance, so as to trigger the sending of the trigger action, which is not limited in this embodiment. The conference type can be selected based on the application terminal which is downloaded at the terminal and generated by the method, the conference identification corresponding to the conference type is automatically generated after the conference type is selected and confirmed, the triggering action is triggered at the moment, then the terminal determines the conference identification based on the received triggering action, and the equipment information of the terminal is acquired, so that the target conference is further created and/or entered.
When the user selects to join or create the corresponding conference type, the conference identifier corresponding to the conference type is automatically generated, so as to trigger the triggering action. The triggering action carries a meeting identifier. The device information includes, but is not limited to, a device model number and a device version.
Step S20: determining a conference type according to the conference identifier, and determining a target SDK according to the equipment information and the conference type;
step S30: and running the target SDK and entering a target conference based on the conference identification.
In this embodiment, the conference identifier may be understood as a conference number, and the conference type may be determined according to the conference number, which is not particularly limited in this embodiment. The meeting type is identified as a meeting developed by a different vendor or brand, such as Tencel meeting and bloom as a meeting, etc. It will be appreciated that SDKs compatible with different terminals are not identical, and thus it is also necessary to determine the SDKs compatible with the terminals according to the device model and the device version. The corresponding SDK list may be determined according to the device information of the terminal, so that a target SDK associated with the conference type is determined in the SDK list, and then the target SDK is operated and enters the target conference based on the conference identification. It can be understood that the conference control method provided by the application can create or join conferences with different conference types without downloading a plurality of application terminals with different conference types, thereby improving conference efficiency.
Optionally, the conference control method further includes: when the conference creation process is triggered, a conference participant or a conference participant terminal is determined based on the triggering action, a target conference type is determined according to the conference participant or the conference participant terminal, then an SDK corresponding to the target conference type is operated, and a conference identifier corresponding to the target conference type is generated.
In this embodiment, when a target conference is created based on a conference creation page provided by a terminal, a conference participant or a conference participant terminal of the target conference may be selected, and when a confirmation creation instruction for conference creation is received, the conference creation process is triggered. The target conference type may be determined by acquiring a conference type associated with the conference participant or a conference type corresponding to the conference participant terminal to which the conference participant belongs, or by acquiring a conference type corresponding to the conference participant terminal, which is not specifically limited in this embodiment. After determining the target conference type corresponding to the participant or the participant terminal, the SDK corresponding to the target conference type is operated, so that the target conference created by the terminal can be accessed through remote terminals of different conference types. The SDK corresponding to the target conference type is operated, and the conference identification corresponding to the target conference type is generated, so that conference participants can access the target conference through the remote terminal or the conference participant terminal of the target conference type based on the conference identification.
Optionally, the triggering event may be triggered when a corresponding conference participant or a conference participant terminal is added by clicking on the conference creation page, or when text information is copied on a paste area provided by the conference creation page, and the determined conference participant or conference participant terminal is parsed according to the text information, or when the conference participant or conference participant terminal is determined in a conference participation list uploaded by an upload button function provided by the conference creation page, which is not limited in this embodiment.
Optionally, the method for controlling the conference further includes: when the conference creation process is triggered, determining the target conference type based on the trigger action; and running the SDK corresponding to the target conference type and generating a conference identification corresponding to the target conference type.
In this embodiment, the type of the target conference corresponding to the running SDK may be selected based on clicking the conference creation page, and the number of the types of the target conference may be one or more, which is not specifically limited in this embodiment. It can be understood that the triggering action is to select the target conference type and confirm based on the conference creation page, so that when conference participants or conference participant terminals are too many, the conference participants or conference participant terminals are not required to be selected, and the target conference type is directly selected, thereby saving the time cost of creating the conference.
In the technical scheme provided by the embodiment, the conference identification is determined based on the trigger action received by the terminal, the equipment information corresponding to the terminal is obtained, then the conference type is determined according to the conference identification, the target SDK is determined according to the equipment information and the conference type, finally the target SDK is operated, and the target conference is entered based on the conference identification. And generating application terminals by integrating SDKs of all conference types, so that conferences of different conference types can be started or added based on the application terminals, conference operation steps are reduced, and conference efficiency is improved.
Referring to fig. 2, in the second embodiment, after the step S30, based on the first embodiment, the method further includes:
step S40: when receiving audio and video data sent by a first terminal based on the target conference, determining a data format corresponding to a second terminal according to a target conference type corresponding to the second terminal, wherein the first terminal and the second terminal are remote terminals accessing the target conference based on different conference types;
step S50: and converting the audio and video data into source data corresponding to the second terminal according to the data format so as to forward the audio and video data to the second terminal.
The target conference allows terminal access based on one or more conference types. For example, a remote terminal accessing the target meeting includes a first terminal and a second terminal. For example, in a different scenario, a first terminal accesses the target conference based on a vacation conference and a second terminal accesses the target conference for the conference based on a bloom. Alternatively, the first terminal and the second terminal may access the target conference based on the Chinese conference or the Tencentrated conference at the same time.
In this embodiment, the explanation is made based on the case where the first terminal and the second terminal access the target conference through different conference types. Because the first terminal and the second terminal are accessed through different conference types, the data cannot be shared between the first terminal and the second terminal, when the audio and video data sent by the first terminal is received based on the target conference, the audio and video data of the first terminal are converted into the source data corresponding to the second terminal, so that the audio and video data of the first terminal are forwarded to the second terminal, the data sharing between the first terminal and the second terminal is realized, the first terminal does not need to download the application terminal with the same conference type as the target conference, and the conference efficiency is improved.
Optionally, when the audio and video data sent by the first terminal is received based on the target conference, a first conference type corresponding to the first terminal and a second conference type corresponding to the second terminal may be obtained, when the first conference type and the second conference type are the same, the audio and video data of the first terminal may be directly forwarded to the second terminal, when the first conference type and the second conference type are different, a data format corresponding to the second terminal may be determined according to the second conference type corresponding to the second terminal, and then the audio and video data may be converted into source data corresponding to the second terminal according to the data format, so as to forward the audio and video data to the second terminal, thereby realizing data sharing between the first terminal and the second terminal.
In the technical scheme provided by the embodiment, the conference identifier is determined based on the trigger action received by the terminal, the equipment information corresponding to the terminal is acquired, then the conference type is determined according to the conference identifier, the target SDK is determined according to the equipment information and the conference type, finally the target SDK is operated, the target conference is entered based on the conference identifier, then when the audio and video data sent by the first terminal is received based on the target conference, the data format corresponding to the second terminal is determined according to the target conference type corresponding to the second terminal, wherein the first terminal and the second terminal are remote terminals which access the target conference based on different conference types, then the audio and video data are converted into source data corresponding to the second terminal according to the data format, so that the data sharing between the first terminal and the second terminal with different conference types is realized, a user can enter the target conference through the remote terminals with different conference types, and the situation that the corresponding conference types need to be started in different time periods are required to be communicated due to inconsistent conference types of conference participants or conference participant terminals and the target conference is avoided, and therefore time consumption is caused.
Referring to fig. 3, in a third embodiment, based on any of the above embodiments, the step S20 includes:
step S21: acquiring an SDK list corresponding to the equipment information;
in this embodiment, the device information includes, but is not limited to, a device model and a device version, and a corresponding SDK list may be obtained according to the device model and the device version, where the SDK list stores SDK files of respective conference types matched with the device information, and is used to create a conference and/or access the conference by running the SDK files of the corresponding conference types.
Optionally, the step of obtaining the SDK list corresponding to the device information includes: generating an SDK list request according to the equipment information, and sending the SDK list request to a server; receiving the SDK list fed back by the server based on the SDK list request; or reading the SDK list stored in the local database.
In this embodiment, the SDK list may be obtained by sending an SDK list request to the server, and it is understood that the server stores SDK lists of terminals corresponding to different device types. Meanwhile, in order to avoid occupying the memory resources of the terminal, the conference types corresponding to the SDK files in the SDK list are supported to be set by the user according to the equipment information of the terminal, the conference types which are not commonly used can be deleted in the SDK list and stored in the local database, and then the terminal can read the SDK list stored in the local database instead of accessing the server. For example, in the use scene of the user, only the Chinese conference and the Tech conference are needed, and the used terminal is the android and the windows, so that the user can only fill in the device information of the android and the windows and the conference type only fill in the Chinese conference and Tech conference, thereby generating the SDK list and storing the SDK list in the local database.
Optionally, since the SDK list stored in the local database is read and can be modified by the user, when the user creates or opens the target conference, and when detecting that there is no SDK file of the conference type corresponding to the target conference in the SDK list stored in the local database, the SDK list request may be sent to the server, the SDK list fed back by the server is obtained, and the SDK file corresponding to the target conference is obtained according to the SDK list fed back by the server, thereby creating the target conference and/or accessing the target conference, which is not limited in this embodiment. The terminal can determine the use frequency corresponding to each conference type according to the use data of the user in the preset time period, and when the use frequency of the conference type is lower than the preset frequency, the SDK corresponding to the conference type with the use frequency lower than the preset frequency in the SDK list stored in the local database can be deleted, so that the memory resource of the terminal is prevented from being occupied, and the data processing efficiency is improved.
Step S22: determining the target SDK associated with the conference type based on the SDK list;
step S23: and running the target SDK and entering a target conference based on the conference identification.
In this embodiment, a target SDK associated with the conference type is found in the SDK list, a target conference is created by running the target SDK, and a target conference is entered based on the conference identification.
Optionally, the step of obtaining the SDK list corresponding to the device information includes: acquiring SDKs corresponding to all conference types in the SDK list; acquiring a corresponding packing template and a packing program of the packing template according to the conference type; and packaging the SDKs corresponding to the conference types according to the packaging program, and storing the SDKs in association with the conference types in the SDK list.
In this embodiment, the SDK version of the SDK corresponding to each conference type may be obtained, the corresponding packaging template and the packaging program of the packaging template may be obtained according to the SDK version, and then the SDK corresponding to each conference type may be packaged according to the packaging program and stored in association with the conference type in the SDK list. It can be appreciated that the integrated packaging of SDKs of different vendors or brands corresponds to different packaging templates, for example, android employs the android packaging template to integrate and package SDKs of all meeting types, while IOS employs the IOS packaging template to integrate and package SDKs of all meeting types.
Optionally, after the step of packaging the SDKs corresponding to the conference type determinations and storing the SDKs in association with the conference types in the device list, the method includes: detecting and acquiring the latest SDK version of the SDK corresponding to each conference type; acquiring SDK versions of SDKs corresponding to the conference types in the equipment list; and when the SDK version is inconsistent with the latest SDK version, acquiring the SDK corresponding to the latest SDK version, packaging the SDKs corresponding to the conference types, and storing the SDKs in association with the conference types in the equipment list.
In this embodiment, by updating the SDK version of each conference type in the SDK list in real time, the situation that a user cannot join due to too low SDK version corresponding to the target conference when accessing the target conference by using a high-version remote terminal is avoided.
In the technical scheme provided by the embodiment, the conference identifier is determined based on the trigger action received by the terminal, the equipment information corresponding to the terminal is acquired, the SDK list corresponding to the equipment information is acquired from the server or the local database, then the SDK corresponding to each conference type in the SDK list is acquired, the packing template corresponding to each conference type and the packing program of the packing template are acquired according to the conference type, then the SDK corresponding to each conference type is packed according to the packing program and is associated with the conference type in the SDK list for storage, and therefore when a target conference is created, the target SDK associated with the conference type can be determined based on the SDK list, the target SDK is operated, and the target conference is entered based on the conference identifier. The user fills in the SDK list according to the actual use requirement and stores the SDK list in the local database, so that the use of the SDK list of the server is avoided, the resource memory of the user terminal is occupied, and meanwhile, the data processing efficiency of the conference can be improved.
Referring to fig. 4, fig. 4 is a schematic diagram of a terminal structure of a hardware running environment according to an embodiment of the present application.
The terminal in the embodiment of the application can be a mobile phone, a computer or a tablet personal computer, and the embodiment is not particularly limited.
As shown in fig. 4, the terminal may include: a processor 1001, such as a CPU, a network interface 1004, a user interface 1003, a memory 1005, a communication bus 1002. Wherein the communication bus 1002 is used to enable connected communication between these components. The user interface 1003 may include a Display screen (Display), an input unit such as a Keyboard (Keyboard), a mouse, etc., and the optional user interface 1003 may further include a standard wired interface, a wireless interface. The network interface 1004 may optionally include a standard wired interface, a wireless interface (e.g., WI-FI interface). The memory 1005 may be a high-speed RAM memory or a stable memory (non-volatile memory), such as a disk memory. The memory 1005 may also optionally be a storage device separate from the processor 1001 described above.
It will be appreciated by those skilled in the art that the terminal structure shown in fig. 4 is not limiting of the terminal and may include more or fewer components than shown, or may combine certain components, or a different arrangement of components.
As shown in fig. 4, an operating system, a network communication module, a user interface module, and a control program for a conference may be included in the memory 1005 as one type of computer storage medium.
In the terminal shown in fig. 4, the network interface 1004 is mainly used for connecting to a background server and performing data communication with the background server; the processor 1001 may be configured to call a control program of a conference stored in the memory 1005, and perform the following operations:
determining a conference identifier based on a trigger action received by a terminal, and acquiring equipment information corresponding to the terminal;
determining a conference type according to the conference identifier, and determining a target SDK according to the equipment information and the conference type;
and running the target SDK and entering a target conference based on the conference identification.
Further, the processor 1001 may call a control program of the conference stored in the memory 1005, and further perform the following operations:
when receiving audio and video data sent by a first terminal based on the target conference, determining a data format corresponding to a second terminal according to a target conference type corresponding to the second terminal, wherein the first terminal and the second terminal are remote terminals accessing the target conference based on different conference types;
and converting the audio and video data into source data corresponding to the second terminal according to the data format so as to forward the audio and video data to the second terminal.
Further, the processor 1001 may call a control program of the conference stored in the memory 1005, and further perform the following operations:
when audio and video data sent by a first terminal are received based on the target conference, determining a first conference type corresponding to the first terminal according to a first conference identifier of the first terminal, and determining a second conference type corresponding to the second terminal according to a second conference identifier of the second terminal;
forwarding the audio and video data to the second terminal when the first conference type is the same as the second conference type;
and when the first conference type is different from the second conference type, executing the step of determining the data format corresponding to the second terminal according to the target conference type corresponding to the second terminal.
Further, the processor 1001 may call a control program of the conference stored in the memory 1005, and further perform the following operations:
acquiring an SDK list corresponding to the equipment information;
determining the target SDK associated with the conference type based on the SDK list;
and running the target SDK and entering a target conference based on the conference identification.
Further, the processor 1001 may call a control program of the conference stored in the memory 1005, and further perform the following operations:
generating an SDK list request according to the equipment information, and sending the SDK list request to a server;
receiving the SDK list fed back by the server based on the SDK list request; or alternatively, the process may be performed,
and reading the SDK list stored in the local database.
Further, the processor 1001 may call a control program of the conference stored in the memory 1005, and further perform the following operations:
acquiring SDKs corresponding to all conference types in the SDK list;
acquiring a corresponding packing template and a packing program of the packing template according to the conference type;
and packaging the SDKs corresponding to the conference types according to the packaging program, and storing the SDKs in association with the conference types in the SDK list.
Further, the processor 1001 may call a control program of the conference stored in the memory 1005, and further perform the following operations:
detecting the latest SDK version of the SDK corresponding to each conference type;
acquiring SDK versions of SDKs corresponding to the conference types in the SDK list;
and when the SDK version is inconsistent with the latest SDK version, acquiring the SDK corresponding to the latest SDK version, and executing the steps of packaging the SDKs corresponding to the conference types according to the packaging program and storing the SDKs in association with the conference types in the SDK list.
Further, the processor 1001 may call a control program of the conference stored in the memory 1005, and further perform the following operations:
when a conference creation process is triggered, determining conference participants or conference participant terminals based on the triggering actions, and determining target conference types according to the conference participants or the conference participant terminals; and/or when triggering a conference creation process, determining the target conference type based on the trigger action;
and running the SDK corresponding to the target conference type and generating a conference identification corresponding to the target conference type.
In addition, in order to achieve the above object, the present application further provides a terminal device, including: the conference control system comprises a memory, a processor and a conference control program stored in the memory and capable of running on the processor, wherein the conference control program realizes the steps of the conference control method when being executed by the processor.
In addition, in order to achieve the above object, the present application also provides a computer-readable storage medium having stored thereon a control program for a conference, which when executed by a processor, implements the steps of the control method for a conference as described above.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or system that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or system. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or system that comprises the element.
The foregoing embodiment numbers of the present application are merely for the purpose of description, and do not represent the advantages or disadvantages of the embodiments.
From the above description of embodiments, it will be clear to a person skilled in the art that the above embodiment method may be implemented by means of software plus a necessary general hardware platform, but may of course also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on this understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a storage medium (e.g. ROM/ram. Magnetic disk. Optical disk) as described above, comprising instructions for causing a terminal device (which may be a mobile phone, a computer, a tablet computer) to perform the method according to the embodiments of the present application.
The foregoing description is only of the preferred embodiments of the present application, and is not intended to limit the scope of the application, but rather is intended to cover any equivalents of the structures or equivalent processes disclosed herein or in the alternative, which may be employed directly or indirectly in other related arts.

Claims (10)

1. A method for controlling a conference, the method comprising:
determining a conference identifier based on a trigger action received by a terminal, and acquiring equipment information corresponding to the terminal;
determining a conference type according to the conference identifier, and determining a target SDK according to the equipment information and the conference type;
and running the target SDK and entering a target conference based on the conference identification.
2. The method for controlling a conference according to claim 1, wherein after the step of running the target SDK and entering a target conference based on the conference identification, comprising:
when receiving audio and video data sent by a first terminal based on the target conference, determining a data format corresponding to a second terminal according to a target conference type corresponding to the second terminal, wherein the first terminal and the second terminal are remote terminals accessing the target conference based on different conference types;
and converting the audio and video data into source data corresponding to the second terminal according to the data format so as to forward the audio and video data to the second terminal.
3. The method for controlling a conference according to claim 2, wherein before the step of converting the audio/video data into source data corresponding to the second terminal according to the data format to forward the audio/video data to the second terminal, the method comprises:
when audio and video data sent by a first terminal are received based on the target conference, determining a first conference type corresponding to the first terminal according to a first conference identifier of the first terminal, and determining a second conference type corresponding to the second terminal according to a second conference identifier of the second terminal;
forwarding the audio and video data to the second terminal when the first conference type is the same as the second conference type;
and when the first conference type is different from the second conference type, executing the step of determining the data format corresponding to the second terminal according to the target conference type corresponding to the second terminal.
4. The method for controlling a conference according to claim 1, wherein the step of determining a conference type based on the conference identification and determining a target SDK based on the device information and the conference type comprises:
acquiring an SDK list corresponding to the equipment information;
determining the target SDK associated with the conference type based on the SDK list;
and running the target SDK and entering a target conference based on the conference identification.
5. The method for controlling a conference according to claim 4, wherein said step of acquiring the SDK list corresponding to the device information includes:
generating an SDK list request according to the equipment information, and sending the SDK list request to a server;
receiving the SDK list fed back by the server based on the SDK list request; or alternatively, the process may be performed,
and reading the SDK list stored in the local database.
6. The method for controlling a conference according to claim 5, wherein after the step of acquiring the SDK list corresponding to the device information, the method comprises:
acquiring SDKs corresponding to all conference types in the SDK list;
acquiring a corresponding packing template and a packing program of the packing template according to the conference type;
and packaging the SDKs corresponding to the conference types according to the packaging program, and storing the SDKs in association with the conference types in the SDK list.
7. The method for controlling a conference according to claim 6, wherein after said step of packing SDKs corresponding to the respective conference types according to the packing program and storing the packed SDKs in association with the conference types in the SDK list, the method comprises:
detecting the latest SDK version of the SDK corresponding to each conference type;
acquiring SDK versions of SDKs corresponding to the conference types in the SDK list;
and when the SDK version is inconsistent with the latest SDK version, acquiring the SDK corresponding to the latest SDK version, and executing the steps of packaging the SDKs corresponding to the conference types according to the packaging program and storing the SDKs in association with the conference types in the SDK list.
8. The method for controlling a conference according to claim 1, wherein the method for controlling a conference further comprises:
when a conference creation process is triggered, determining conference participants or conference participant terminals based on the triggering actions, and determining target conference types according to the conference participants or the conference participant terminals; and/or
When the conference creation process is triggered, determining the target conference type based on the trigger action;
and running the SDK corresponding to the target conference type and generating a conference identification corresponding to the target conference type.
9. A terminal device, characterized in that the terminal device comprises: memory, a processor and a control program for a video conference of a terminal device stored on the memory and executable on the processor, which control program for a video conference of a terminal device, when executed by the processor, implements the steps of the method for controlling a conference according to any one of claims 1 to 8.
10. A computer-readable storage medium, characterized in that the computer-readable storage medium has stored thereon a control program for a video conference of a terminal device, which, when executed by a processor, implements the steps of the method for controlling a conference according to any one of claims 1 to 8.
CN202310856488.7A 2023-07-13 2023-07-13 Conference control method, terminal device and storage medium Active CN116582639B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202310856488.7A CN116582639B (en) 2023-07-13 2023-07-13 Conference control method, terminal device and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202310856488.7A CN116582639B (en) 2023-07-13 2023-07-13 Conference control method, terminal device and storage medium

Publications (2)

Publication Number Publication Date
CN116582639A true CN116582639A (en) 2023-08-11
CN116582639B CN116582639B (en) 2023-11-07

Family

ID=87534586

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202310856488.7A Active CN116582639B (en) 2023-07-13 2023-07-13 Conference control method, terminal device and storage medium

Country Status (1)

Country Link
CN (1) CN116582639B (en)

Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113099152A (en) * 2021-03-31 2021-07-09 北京奇艺世纪科技有限公司 Method and device for call among multiple systems
CN114125362A (en) * 2021-11-19 2022-03-01 中国电信集团系统集成有限责任公司 Conference joining method and device, conference platform and computer readable storage medium
CN114884924A (en) * 2022-04-24 2022-08-09 康键信息技术（深圳）有限公司 Audio and video channel selection method and device, electronic equipment and storage medium
CN115103150A (en) * 2022-06-15 2022-09-23 中移（杭州）信息技术有限公司 Access method, device, equipment and medium for audio and video online conference
KR20230015685A (en) * 2021-07-23 2023-01-31 홍윤광 A video conference mediation platform, the method for inviting and accepting video conference using the same
US20230071282A1 (en) * 2021-09-09 2023-03-09 Arris Enterprises Llc Video conference manager
US20230136344A1 (en) * 2021-10-28 2023-05-04 Zoom Video Communications, Inc. Video conferencing integration for third party applications
CN116193062A (en) * 2022-12-30 2023-05-30 视联动力信息技术股份有限公司 Conference interconnection method and device, electronic equipment and storage medium
CN116382934A (en) * 2022-12-30 2023-07-04 五八同城信息技术有限公司 SDK call control method and device, electronic equipment and storage medium

Patent Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113099152A (en) * 2021-03-31 2021-07-09 北京奇艺世纪科技有限公司 Method and device for call among multiple systems
KR20230015685A (en) * 2021-07-23 2023-01-31 홍윤광 A video conference mediation platform, the method for inviting and accepting video conference using the same
US20230071282A1 (en) * 2021-09-09 2023-03-09 Arris Enterprises Llc Video conference manager
US20230136344A1 (en) * 2021-10-28 2023-05-04 Zoom Video Communications, Inc. Video conferencing integration for third party applications
CN114125362A (en) * 2021-11-19 2022-03-01 中国电信集团系统集成有限责任公司 Conference joining method and device, conference platform and computer readable storage medium
CN114884924A (en) * 2022-04-24 2022-08-09 康键信息技术（深圳）有限公司 Audio and video channel selection method and device, electronic equipment and storage medium
CN115103150A (en) * 2022-06-15 2022-09-23 中移（杭州）信息技术有限公司 Access method, device, equipment and medium for audio and video online conference
CN116193062A (en) * 2022-12-30 2023-05-30 视联动力信息技术股份有限公司 Conference interconnection method and device, electronic equipment and storage medium
CN116382934A (en) * 2022-12-30 2023-07-04 五八同城信息技术有限公司 SDK call control method and device, electronic equipment and storage medium

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
杜金房: "FreeSWITCH视频会议"标准"解决方案 - 知乎", Retrieved from the Internet <URL:https://zhuanlan.zhihu.com/p/180474593?utm_id=0> *
阿里云: "如何完成SDK集成操作_钉钉会议-阿里云帮助中心", Retrieved from the Internet <URL:https://help.aliyun.com/document_detail/208861.html?spm=a2c4g.166577.0.i0> *

Also Published As

Publication number Publication date
CN116582639B (en) 2023-11-07

Similar Documents

Publication Publication Date Title
CN109684054B (en) Information processing method and device, electronic equipment and memory
US20160170712A1 (en) Method for integrally implementing development and release of APP
US20230308504A9 (en) Method and system of application development for multiple device client platforms
WO2018107719A1 (en) Data sharing method, apparatus, terminal device and server
WO2021068765A1 (en) Web page screenshot method and apparatus, device, and computer-readable storage medium
US20110320286A1 (en) System And Method For Integrating An Ad Banner With A Calling Application
JP2011512571A (en) System and method for integrating banner advertisement and calling application
CN111182065A (en) Message processing method and device based on MQTT protocol and computer equipment
CN112307397A (en) Schedule processing method, device and equipment based on online document and storage medium
CN111427552A (en) Front-end component development method and device, computer equipment and storage medium
CN111949314A (en) Method and device for generating application installation package, server and storage medium
CN116582639B (en) Conference control method, terminal device and storage medium
CN111026669B (en) Test log management method, test log management device and storage medium
CN111970192B (en) Information editing method and device based on session group
JP2007172098A (en) Information processing system and information processing server device
US20030078998A1 (en) Method and system for using a selected peripheral of a network
CN103795835A (en) Mobile terminal and method for realizing shortcut operation of mobile terminal
CN113221517B (en) Mail editing method and device, computer equipment and storage medium
CN111294404A (en) Processing method and device, computer equipment and medium suitable for various external short message services
CN112749355A (en) Page display method, device, terminal, server and storage medium
CN111078215A (en) Software product application method and device, storage medium and electronic equipment
JP2001282638A (en) Electronic mail device and computer-readable recording medium recorded with computer program
CN110674366A (en) Data distribution method based on OGNL expression language, electronic device and storage medium
CN114095464B (en) Instant message realization method and system
KR20130005835A (en) Method and system for producing an application

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant