A cloud video-based multi-service fusion system

Abstract

The application discloses a multi-service fusion system based on cloud video. The system is composed of a backstage, a middle stage and a front stage, and realizes comprehensive fusion of cloud video conference. The backstage is based on resources of the CNOOC cloud platform, and constructs an efficient and reliable video conference system, which supports smooth expansion. The middle stage provides rich video conference services, including basic, advanced, development and access, and realizes seamless connection with multi-vendor systems. The front stage faces users, and provides video conference, command and dispatch, collaborative work and other full-scene business applications, and improves intelligent communication and collaboration capabilities through the fusion of multiple services. The overall system is safe and reliable, easy to expand, and meets the remote communication needs in multiple scenes.

Description

Technical Field

[0001] The present invention relates to the field of information and communication technologies, and in particular to a multi-service fusion system based on cloud video. Background Art

[0002] With the rapid development of information technology, cloud computing and video technology have gradually become important cornerstones of information interaction and processing in modern society. Cloud computing, with its powerful computing power, storage capabilities, and flexible scalability, provides efficient and reliable support for various businesses. Video technology, particularly cloud video technology, leverages the advantages of cloud computing to make video transmission, storage, and processing more efficient and convenient. Currently, multi-service convergence has become a key research direction in the field of information technology. By integrating different business systems, resources can be shared, optimized, and coordinated between businesses, thereby improving overall business efficiency and user experience. However, traditional multi-service convergence systems often face problems such as complex data processing, poor system stability, and insufficient scalability. A single service model can no longer meet the needs of enterprises. Therefore, multi-service convergence based on cloud video has become a future development trend.

[0003] There are a variety of cloud video systems currently on the market, most of which focus on aspects such as video stream transmission, encoding and decoding, and terminal device compatibility. While these systems meet users' video communication needs to a certain extent, they still have many shortcomings in terms of multi-service integration. For example, in addition to basic auxiliary functions such as video calling, file sharing, screen sharing, and real-time annotation, video conferencing systems also need to present and analyze data from other business systems of the group. These functions often require switching between different systems or platforms, making data integration, connection, and transition difficult. Summary of the Invention

[0004] Based on this, the embodiments of this application provide a multi-service convergence system based on cloud video. By leveraging the real-time, interactive, and multimedia characteristics of cloud video, various services can be integrated using video as a medium. Through specific API interfaces, intuitive information display and efficient interaction are achieved. The application of cloud video technology in the multi-service convergence system solves the problems in the existing technology.

[0005] This application provides a multi-service integration system based on cloud video, including a backend system, a middle-end system, and a front-end system, wherein:

[0006] The backend system is deployed on the information infrastructure cloud platform, and builds a cloud video conferencing platform by utilizing X86 cloud hosts, Xinchuang cloud host computing resources, cloud storage resources, cloud network resources, cloud security resources, and databases, and is decoupled from hardware devices;

[0007] The middle-office system is used to provide various services of the cloud video conferencing platform, including basic system services, advanced system services, development services, and access services. Among them, the basic system services provide the cloud video conferencing platform with underlying video sharing, whiteboard collaboration, and conference control services; the advanced system services provide the cloud video conferencing platform with development, live broadcasting, monitoring, recording, and multi-protocol integration services; the development service can be connected to other third-party video conferencing systems through open protocol SDK / API, and is compatible with multi-vendor and multi-product systems; the access service connects to various video conferencing connection methods;

[0008] The front-end system is used to provide full-scenario business applications of the cloud video conferencing platform, including video conferencing, command and dispatch, collaborative work, enterprise live broadcast, enterprise training, remote recruitment, data collaboration and multiple businesses, and can integrate multiple business applications at the same time.

[0009] Optionally, the signaling service entrance of the cloud video conferencing platform adopts the innovative strategy of F5+HA; signaling service messages are uniformly received through F5 network equipment, and multi-active service logic processing is implemented using HA services.

[0010] Optionally, the cloud video conferencing platform specifically adopts the nginx distribution mode to directly distribute the request signaling to the corresponding multi-copy service; for internal service API calls, they are completed through internal-nginx, and a polling algorithm is used to ensure load balancing.

[0011] Optionally, the cloud video conferencing platform sets up an API interface for exporting meeting details according to the meeting time; obtains the signature field by calling the signature authentication method, and uses the interface to return the meeting details list, and then performs data statistics based on the participant number.

[0012] Optionally, the cloud video conferencing platform includes a middleware cluster strategy; wherein asynchronous communication and message passing between systems are achieved through AMQ and Kafka message queues; ZooKeeper provides a distributed coordination service for maintaining system status and implementing service discovery; and Redis is used as an in-memory database.

[0013] Optionally, the cloud video conferencing platform includes the introduction of distributed caching technology to achieve rapid access and sharing of audio and video encoding data; secondly, the use of load balancing technology to distribute audio and video encoding service requests to multiple nodes for processing; and the introduction of intelligent scheduling algorithms and fault-tolerant mechanisms to achieve dynamic load balancing and automatic fault recovery between nodes.

[0014] Optionally, the cloud video conferencing platform's various services include scheduled meetings and instant meetings, including:

[0015] Scheduling a meeting involves: integrating the conference SDK to embed video capabilities; users can log in with third-party account authentication, integrate an H5 application within the collaborative office module, and call the cloud conference platform's meeting scheduling API; set the meeting name and password parameters, and select participants from the address book maintained independently by the collaborative office module or the company address book; once the appointment is completed, the system automatically returns the meeting number and pushes the meeting information through the embedded message channel;

[0016] Instant conference specifically includes: in the application scenario, after creating a meeting, you can initiate the meeting.

[0017] Optionally, the implementation of the scheduled meeting includes:

[0018] Initiate a meeting reservation process in the APP, where the reservation meeting information includes meeting topic, meeting time, participants, joining password, and host password;

[0019] After the meeting initiator fills in the reservation information, he / she requests the API service to create a conference room number. The API service responds to the request and returns the conference room password.

[0020] Store appointment information and create appointment meeting records; push meeting information to participants through the message channel embedded in the APP;

[0021] After logging into the client, technical experts using the cloud conference app can view upcoming meetings in the schedule. After checking their personal meeting schedule in the app, participants can return to their personal meeting schedule list and obtain the conference room number after opening the meeting schedule.

[0022] When the meeting schedule arrives, participants use the SDK's MakeCall method to call into the corresponding conference room for the meeting.

[0023] Optionally, the implementation of the instant conference includes:

[0024] The instant conference initiator selects participants and requests the API service to create a conference room number. The API service responds to the request and returns the conference room number to the instant conference initiator.

[0025] The instant conference initiator initiates a message call in the app based on the participants and conference room number: iterates over all participants to ensure that all participants receive the call request;

[0026] Participants use the SDK's MakeCall method to call into the corresponding conference room based on the conference room number in the call request.

[0027] Optionally, the cloud video conferencing platform adopts the form of an IPPBX external IP voice gateway; the IPPBX needs to be connected to the IP voice gateway device through an IP network, and the IP voice gateway provides an external line interface and an extension interface.

[0028] The beneficial effects of the present invention are as follows:

[0029] (1) Through the embedded video module, fast and direct remote audio and video communication is achieved, effectively shortening communication time and improving work efficiency. Support for multi-party audio and video interaction, shared data files, electronic whiteboard and other functions makes communication more intuitive and efficient, helping to quickly solve problems.

[0030] (2) Enhanced work safety: The use of Android explosion-proof mobile phones ensures the safety of offshore workers using equipment in complex environments. The multi-network communication capabilities of enterprise dedicated lines and the Internet ensure the stability of video calls and the security of data.

[0031] (3) Through load balancing, high availability of microservice nodes and other technical means, the stability and reliability of the system are ensured, ensuring smooth user use even during peak hours. The adoption of middleware clustering strategies (such as AMQ, Kafka, ZK, Redis, etc.) further improves the system's processing power and scalability, providing a solid foundation for future business growth. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] To more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following briefly introduces the drawings required for the embodiments or the description of the prior art. Obviously, the drawings described below are merely exemplary, and those skilled in the art can, without inventive effort, derive other implementation drawings based on the provided drawings.

[0033] Figure 1 A functional structure diagram of a multi-service fusion system based on cloud video provided in an embodiment of the present application;

[0034] Figure 2 A diagram of the system topology provided in the embodiment of the present application;

[0035] Figure 3 This is a diagram of the docking architecture provided in the embodiment of this application. DETAILED DESCRIPTION

[0036] In order to make the purpose, technical solutions and advantages of this application more clear, the following further describes this application in detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain this application and are not intended to limit this application.

[0037] In the description of the present invention, the terms "comprise", "have" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or apparatus comprising a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may also include other steps or units that are not explicitly listed but are inherent to these processes, methods, products or apparatuses, or steps or units that are added based on further optimization schemes conceived by the present invention.

[0038] This application develops a multi-business fusion system based on cloud video, which integrates and optimizes different business modules within the group to achieve seamless connection and efficient collaboration of business, which has important practical significance and application value.

[0039] Based on the established private cloud conference platform, the platform has functions such as two-factor login, video conferencing, video recording and broadcasting, monitoring integration, and telephone voice. It efficiently and stably ensures the normal application of remote video in the group units and has supported many major group events.

[0040] The main goal of this project is to rely on the private cloud platform, follow the principles of "integration, unification, and sharing", and build a safe, reliable, scenario-free, efficient and convenient cloud conferencing platform by optimizing and upgrading the platform architecture and customizing business integration needs on the basis of the existing cloud conferencing platform.

[0041] Specifically, please refer to Figure 1 , which shows a functional structure diagram of a multi-service integration system based on cloud video provided by an embodiment of the present application. The multi-service integration system includes a backend system, a middle-end system, and a front-end system, wherein:

[0042] The backend system is deployed on the information infrastructure cloud platform, and builds a cloud video conferencing platform by utilizing X86 cloud hosts, Xinchuang cloud host computing resources, cloud storage resources, cloud network resources, cloud security resources, and databases, and is decoupled from hardware devices;

[0043] The middle-office system is used to provide various services of the cloud video conferencing platform, including basic system services, advanced system services, development services, and access services. Among them, the basic system services provide the cloud video conferencing platform with underlying video sharing, whiteboard collaboration, and conference control services; the advanced system services provide the cloud video conferencing platform with development, live broadcasting, monitoring, recording, and multi-protocol integration services; the development service can be connected to other third-party video conferencing systems through open protocol SDK / API, and is compatible with multi-vendor and multi-product systems; the access service connects to various video conferencing connection methods;

[0044] The front-end system is used to provide full-scenario business applications of the cloud video conferencing platform, including video conferencing, command and dispatch, collaborative work, enterprise live broadcast, enterprise training, remote recruitment, data collaboration and multiple services, and can integrate multiple business applications. Figure 2 A summary of the system functional structure is given.

[0045] Combined with the component types of the cloud conference platform's core services, stability is improved mainly in five aspects, including: inlet load balancing strategy, microservice node high availability and loadbalance implementation method, service registration and discovery, middleware cluster strategy (amq, kafka, zk, redis), and distributed node fusion AVC service optimization design.

[0046] (1) Ingress load balancing strategy

[0047] The cloud conference platform uses F5+HA to achieve a high-reliability architecture at the system level in the signaling service entrance and the disaster recovery switching architecture design in Beijing and Shanghai.

[0048] At the service entry point, F5 network equipment is deployed at the front end to centrally receive signaling service messages. HA services are configured on the F5 to distribute service load. HA services are deployed on both the primary system in Beijing and the backup system in Shanghai. These two HA service modules handle active-active service logic. Assuming the primary system is operating normally, the HA services on both the primary and backup systems simultaneously push video service messages forwarded by the F5 to the Nginx service clusters that serve as the front-end for the primary and recording agents. Finally, the Nginx service clusters implement multi-replica routing.

[0049] At the same time, the HA server can determine the operating status of the Beijing main system and Shanghai backup system in real time, and support automatic and manual configuration for business switching.

[0050] As can be seen, this technical solution utilizes the innovative F5+HA strategy for the cloud video conferencing platform's signaling service entry and disaster recovery switchover architecture. Signaling service messages are uniformly received via F5 network devices, and HA services are used to implement multi-active service logic processing. This strategy ensures synchronized service message push between the primary and backup systems, and implements multi-replica routing through the Nginx service cluster, thus achieving a highly reliable system-wide architecture. The HA server can determine system operating status in real time and supports both automatic and manual service switchover, significantly improving system availability and stability.

[0051] (2) Microservice node high availability and loadbance implementation

[0052] The high-availability platform nginx (main-proxy for the main business and vod-proxy for the recording and broadcasting business) adopts a distribution mode, directly distributing request signaling to the corresponding multi-copy services.

[0053] Internal service API calls are completed through internal-nginx using a round-robin algorithm. Since the number of replicas of call-related services is greater than or equal to 2, when a single node (server) goes down, it will not affect normal calls.

[0054] The platform's high-availability design is evident in the distribution model of nginx (both the main service agent and the recording and broadcasting service agent), which directly distributes request signals to the corresponding multi-replica services. Internal service API calls are handled by internal-nginx, using a round-robin algorithm to ensure load balancing. Because the number of replicas for critical services is greater than or equal to two, even if a single node (server) fails, normal calls remain unaffected, achieving high availability and load balancing for microservice nodes.

[0055] (3) Multi-business integration - branch office collaborative office docking solution

[0056] Requirements Overview:

[0057] The branch's offshore workers carry explosion-proof Android phones with a collaborative office app installed. They now need to integrate a video module to enable remote connections with onshore technical experts. The specific implementation details are as follows:

[0058] 1) The collaborative office APP integrates the cloud conference-specific Android SDK.

[0059] 2) Ability to connect multiple networks including enterprise dedicated lines and the Internet.

[0060] 3) Onshore technical experts can participate in the meeting through explosion-proof mobile phones or independent cloud conference APP.

[0061] 4) During video communication, multi-party audio and video interaction, sharing of data files, electronic whiteboard, video recording, etc. can be carried out.

[0062] Implementation plan:

[0063] The collaborative office APP embeds video capabilities by integrating the cloud conference SDK. In the application scenarios, the application modules of scheduled meetings and instant meetings can be used. In the scenario of scheduled meetings, meetings can be booked in advance to address technical issues; in the scenario of instant meetings, meetings can be initiated temporarily.

[0064] Schedule a meeting:

[0065] The cloud conference SDK can be directly embedded in the collaborative office APP, and login can be completed through the unique identification ID and name of the third-party account authentication.

[0066] Integrate H5 applications in the collaborative office APP and call the API interface of the cloud conference platform to schedule meetings. It supports setting the meeting name, meeting password, meeting control password and invitation address book. The invitation address book involves two parts: the address book independently maintained by the collaborative office APP and the address book of the cloud conference platform branch.

[0067] After the appointment is completed, the system automatically returns the meeting number. The collaborative office APP can push the meeting information through the message channel embedded in the APP; technical experts using the cloud conference APP log in to the client and view the meetings to be attended in the schedule.

[0068] In the embodiment of the present application, the appointment meeting is first initiated in the APP. The meeting appointment information includes the meeting subject, meeting time, participants (where participants can be selected from the APP address book), joining password, host password and other information;

[0069] After the meeting initiator fills in the reservation information, he / she requests the API service to create a conference room number and returns the conference room password. The reservation information is stored and the reservation meeting is established.

[0070] After checking their personal meeting schedule in the app, participants return to their personal meeting schedule list and obtain the conference room number after opening the meeting schedule. When the meeting schedule arrives, they use the MakeCall method of the SDK to call into the conference room.

[0071] The collaborative office app can directly enter the meeting or use the cloud conference app to participate in the meeting.

[0072] Instant Meeting:

[0073] Instant meetings can refer to the model of scheduled meetings. In the application scenario, after creating a meeting, you can initiate the meeting.

[0074] Note: For instant meetings, if you invite a cloud conference client, you need to call the "Invite to Meeting" API interface.

[0075] To enable efficient integration between the cloud conferencing platform and the platform, the platform provides an API interface for exporting meeting details by participant time. This mechanism retrieves the signature field by calling a signature authentication method and uses this interface to return a list of meeting details, which is then used to generate statistics based on participant numbers. This service registration and discovery mechanism not only improves the efficiency of interface data return but also ensures data security and accuracy.

[0076] In the embodiment of the present application, the specific signaling interaction process for the instant conference is as follows:

[0077] The instant conference initiator first selects participants A, B, and C, and requests the Create Conference Room Number API, which returns the conference room number.

[0078] The instant conference initiator calls participants A, B, and C in the app based on the participants and conference room numbers. Specifically, the instant conference initiator selects the participants and requests the API service to create a conference room number; the API service responds to the request and returns the conference room number to the instant conference initiator;

[0079] The instant conference initiator initiates a message call in the app based on the participants and conference room number: iterates over all participants to ensure that all participants receive the call request;

[0080] Participants use the SDK's MakeCall method to call into the corresponding conference room based on the conference room number in the call request.

[0081] (4) Multi-business integration - group platform docking solution

[0082] Requirements Overview:

[0083] The group plans to build a mini-program platform to show the weekly energy conservation and carbon reduction achievements of each employee by counting the number of times and duration of group employees' use of the cloud conference platform each week and the corresponding meeting list.

[0084] Implementation plan:

[0085] The cloud conference platform provides an API interface for "exporting meeting details by meeting time". By connecting with the backend service, the interface data is returned. The main connection steps are as follows:

[0086] Call the signature authentication method 2.0 of the cloud conference platform to obtain the "signature" signature field.

[0087] Use the "Export meeting details by participant" interface to return the meeting details list, and then perform data statistics based on the returned "callNumber" participant number.

[0088] In the embodiment of this application, the specific process of the docking solution is as follows:

[0089] S1, business access server in APP;

[0090] S2, the server exports the details interface API to the cloud conference according to the participants, and obtains the meeting details returned by the cloud conference;

[0091] S3: The server analyzes and displays the obtained meeting details to the APP.

[0092] (5) Multi-service integration - Telephone conference access cloud platform

[0093] To further enhance the converged communication capabilities of the cloud conference platform and improve the manageability and controllability of telephone access, the current cloud conference system (X86 environment) requires the addition of an IPPBX device that can be integrated with the group company's PBX equipment to implement telephone conference entry and IVR reminder functions.

[0094] The IPPBX adopts the form of an external IP voice gateway. In this case, the IPPBX needs to be connected to the IP voice gateway device through the IP network, and the IP voice gateway provides external line interface and extension interface to improve scalability and flexibility.

[0095] In addition, the middleware cluster strategy is the key to the stable operation of the cloud video conferencing platform. In this technical solution, the application of middleware cluster strategies (such as AMQ, Kafka, ZK, Redis, etc.) ensures the high performance, high availability and scalability of the system. For example, message queues (such as AMQ and Kafka) are used to implement asynchronous communication and message delivery between systems; ZooKeeper (ZK) provides distributed coordination services for maintaining system status and implementing service discovery; Redis, as an in-memory database, provides high-speed data reading and writing capabilities, supporting caching and message publishing / subscription functions. By building these middleware clusters, the system's processing power and response speed can be further improved to meet the needs of large-scale concurrent access and complex business scenarios.

[0096] Advanced distributed architectures and algorithms are employed in the optimized design of distributed node-integrated AVC services. First, by introducing distributed caching technology, rapid access and sharing of audio and video coding (AVC) data is achieved. Second, load balancing technology is utilized to distribute AVC service requests to multiple nodes for processing, improving system throughput and response speed. Finally, by introducing intelligent scheduling algorithms and fault-tolerant mechanisms, dynamic load balancing and automatic fault recovery between nodes are achieved. These optimization measures not only improve the performance and reliability of AVC services, but also provide users with a smoother and clearer audio and video experience. At the same time, we will continue to explore and research new technical methods and optimization approaches to continuously enhance the service quality and user experience of the cloud video conferencing platform.

[0097] From the above, it can be seen that this application has achieved:

[0098] 1. Resource integration and sharing

[0099] The multi-service convergence system based on cloud video enables resource integration and sharing. This means that different business modules within related units within the group can share the same set of cloud video resources, avoiding duplication and waste of resources and improving resource utilization efficiency.

[0100] 2. Business fragmentation

[0101] Traditional cloud video systems are often designed for a single service, forcing users to switch between different systems or platforms when using multiple service functions, resulting in inconvenience and low efficiency. A multi-service convergence system based on cloud video solves the problem of service fragmentation by integrating multiple service functions and achieving seamless integration between services.

[0102] 3. Multi-service collaborative processing

[0103] The multi-service fusion system based on cloud video can realize collaborative processing between different services. Specific services can be collaboratively processed in the cloud, improving service response speed and user experience.

[0104] 4. Flexible business expansion

[0105] The multi-service convergence system based on cloud video enables flexible business expansion. Since the core functions of the service are implemented in the cloud, business expansion can be achieved through simple software updates or the addition of new business modules without modifying hardware equipment, greatly reducing expansion costs and risks.

[0106] In general, solving these issues will help promote the digital transformation of related industries, improve service quality and operational efficiency, and also provide users with a richer and more convenient service experience.

[0107] The technical features of the above-mentioned embodiments can be combined arbitrarily. In order to make the description concise, not all possible combinations of the technical features in the above-mentioned embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0108] The above-described embodiments merely represent several implementation methods of the present application. While the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the patent application. It should be noted that a person of ordinary skill in the art may make various modifications and improvements without departing from the spirit of the present application, and these modifications and improvements fall within the scope of protection of the present application. Therefore, the scope of protection of the present patent application shall be determined by the appended claims.

Claims

1. A multi-service fusion system based on cloud video, characterized in that: The multi-service integration system includes back-end system, middle-end system and front-end system, among which: The backend system is deployed on the information infrastructure cloud platform, and builds a cloud video conferencing platform by utilizing X86 cloud hosts, Xinchuang cloud host computing resources, cloud storage resources, cloud network resources, cloud security resources, and databases, and is decoupled from hardware devices; The middle-office system is used to provide various services of the cloud video conferencing platform, including basic system services, advanced system services, development services, and access services. Among them, the basic system services provide the cloud video conferencing platform with underlying video sharing, whiteboard collaboration, and conference control services; the advanced system services provide the cloud video conferencing platform with development, live broadcasting, monitoring, recording, and multi-protocol integration services; the development service can connect with other third-party video conferencing systems through open protocol SDK / API, and is compatible with multi-vendor and multi-product systems; the access service connects to various video conferencing connection methods; The front-end system is used to provide full-scenario business applications of the cloud video conferencing platform, including video conferencing, command and dispatch, collaborative work, enterprise live broadcasting, enterprise training, remote recruitment, data collaboration and multiple services, and can also integrate multiple business applications; The signaling service entry of the cloud video conferencing platform adopts the innovative strategy of F5+HA; signaling service messages are uniformly received through F5 network devices, and multi-active service logic processing is implemented using HA services; The cloud video conferencing platform specifically adopts the nginx distribution mode, directly distributing the request signaling to the corresponding multi-copy service; for internal service API calls, they are completed through internal-nginx, and a polling algorithm is used to ensure load balancing.

2. The multi-service integration system according to claim 1, characterized in that: The cloud video conferencing platform sets up an API interface for exporting meeting details according to the meeting time; obtains the signature field by calling the signature authentication method, and uses the interface to return the meeting details list, and then performs data statistics based on the participant number.

3. The multi-service integration system according to claim 1, characterized in that: The cloud video conferencing platform includes a middleware cluster strategy; among them, asynchronous communication and message transmission between systems are realized through AMQ and Kafka message queues; ZooKeeper provides a distributed coordination service for maintaining system status and realizing service discovery; and Redis is used as an in-memory database.

4. The multi-service integration system according to claim 1, characterized in that: The cloud video conferencing platform includes the introduction of distributed caching technology to achieve rapid access and sharing of audio and video encoding data; secondly, the use of load balancing technology to distribute audio and video encoding service requests to multiple nodes for processing; By introducing intelligent scheduling algorithms and fault-tolerant mechanisms, dynamic load balancing and automatic fault recovery between nodes are achieved.

5. The multi-service integration system according to claim 1, characterized in that: The cloud video conferencing platform's various services include scheduled meetings and instant meetings, including: Scheduling a meeting involves: integrating the conference SDK to embed video capabilities; users can log in with third-party account authentication, integrate an H5 application within the collaborative office module, and call the cloud conference platform's meeting scheduling API; set the meeting name and password parameters, and select participants from the address book maintained independently by the collaborative office module or the company address book; once the appointment is completed, the system automatically returns the meeting number and pushes the meeting information through the embedded message channel; Instant conference specifically includes: in the application scenario, after creating a meeting, you can initiate the meeting.

6. The multi-service integration system according to claim 5, characterized in that: The implementation of scheduled conferences includes: Initiate a meeting reservation process in the APP, where the reservation meeting information includes meeting topic, meeting time, participants, joining password, and host password; After the meeting initiator fills in the reservation information, he / she requests the API service to create a conference room number. The API service responds to the request and returns the conference room password. Store appointment information and create appointment meeting records; push meeting information to participants through the message channel embedded in the APP; After logging into the client, technical experts using the cloud conference app can view upcoming meetings in the schedule. After checking their personal meeting schedule in the app, participants can return to their personal meeting schedule list and obtain the conference room number after opening the meeting schedule. When the meeting schedule arrives, participants use the SDK's MakeCall method to call into the corresponding conference room for the meeting.

7. The multi-service integration system according to claim 5, characterized in that: The implementation of instant conferencing includes: The instant conference initiator selects participants and requests the API service to create a conference room number. The API service responds to the request and returns the conference room number to the instant conference initiator. The instant conference initiator initiates a message call in the app based on the participants and conference room number: iterates over all participants to ensure that all participants receive the call request; Participants use the SDK's MakeCall method to call into the corresponding conference room based on the conference room number in the call request.

8. The multi-service integration system according to claim 1, characterized in that: The cloud video conferencing platform adopts the form of IPPBX external IP voice gateway; The IPPBX needs to be connected to the IP voice gateway device through the IP network, and the IP voice gateway provides the external line interface and extension interface.

Images