WO2011029316A1

WO2011029316A1 - Multimedia conference engine system and method

Info

Publication number: WO2011029316A1
Application number: PCT/CN2010/072838
Authority: WO
Inventors: 彭磊; 王志勇; 骆毅
Original assignee: 中兴通讯股份有限公司
Priority date: 2009-09-10
Filing date: 2010-05-17
Publication date: 2011-03-17
Also published as: CN101656746A

Abstract

A multimedia conference engine system is provided by the present invention, and includes a WEB module and an application service module. A multimedia conference engine method is implemented by the multimedia conference engine system, and includes that: Application Programming Interface (API) call interfaces externally opened by the multimedia conference engine system is defined in the WEB module; using a request input interface of the API call interfaces, a conference operation request sent from a user via a conference terminal is accepted; and using a request response output interface of the API call interfaces, a process result made by the conference engine system for the conference operation request is fed back to the conference terminal. Thereby, various functions of conference service are implemented. As the API call interfaces are opened externally, on the one hand, they can be used by various types of conference terminals without limitation; on the other hand, they are easy to extend and facilitates the development for the third party.

Description

Multimedia engine system and method

The present invention relates to the field of communications, and in particular, to a multimedia conference engine system and method. Background technique

In the existing IP Multimedia Subsystem (IMS) or Next Generation Network (NGN) multimedia conferencing system mode, the conference terminal and conference service capabilities of the human-machine interface used by the participants are the same multimedia. The conference engine system provides that the conference server communicates with the conference terminal through an informal or non-standard private interface. The private nature of the private interface leads to the limitations of the conference system, mainly as follows: On the one hand, the members of the conference are required to only You can use the conference terminal of the type specified by the conference system, install the specified PC communication software or download fixed controls; on the other hand, it is not easy to expand. Summary of the invention

The technical problem to be solved by the present invention is to provide a multimedia conference engine system that calls an interface for various types of conference terminals and is easy to expand, and provides a call interface for use by various types of conference terminals and is easy to expand. Multimedia conference engine approach.

The technical solution adopted by the present invention to solve the technical problem is: a multimedia conference engine system, including a WEB module and an application service module; the WEB module includes an application programming interface (Application Programming Interface) for opening the multimedia conference system to the outside. API) calling an interface, the API call interface including a request access port for each conference operation request and a request response outlet for responding to each conference operation request; the application service module is configured to The conference operation request of the WEB module is processed, and the result of the processing is fed back to the WEB module, and the request response is sent back to the conference terminal. The present invention discloses a multimedia conference engine system, including: a conference terminal, a WEB module, and an application service module, where the WEB module includes an API call interface that is open to the multimedia conference system, and the API call interface is used for each conference. The requesting access port of the operation request and the request response for the various meeting operation request responses are connected;

The WEB module is configured to send a conference operation request that is accessed by requesting the access port to the application service module; and after the application service module feeds back the result of the conference operation request processing, request the conference operation by requesting the response The result of the processing is fed back to the conference terminal;

The application service module is configured to process the conference operation request from the WEB module, and feed back the result of the processing to the WEB module.

The API call interface further includes an authentication access port and an authentication response receiving port; wherein the authentication access port is configured to authenticate the use permission of the requesting access interface; An exit, an authentication response for feeding back the authentication result to the conference terminal.

The conference operation includes at least one of the following: conference initialization, participation withdrawal conference, conference suspension, conference control, conference member operation, moderator change and floor control, conference status subscription and notification, participant information subscription, and notification.

The API call interface uses an XML format.

The invention also discloses a multimedia conference engine method, comprising:

Setting an API call interface for the multimedia conference system to be opened to the outside in the WEB module, where the API call interface includes a request access port for requesting each conference operation request and a request response export port for responding to each conference operation request response;

The WEB module sends the conference operation request accessed by the requesting access port to the application service module; the application service module processes the conference operation request, and feeds the processing result back to the WEB module;

The WEB module feeds back the result of the conference operation request processing to the conference by requesting the response to the exit. Terminal.

The API call interface further includes: an authentication access port for authenticating the use right of the request access interface, and an authentication response receiving and outputting the authentication result to the conference terminal; the WEB module will pass Before requesting the conference operation request that is accessed by the access port to be sent to the application service module, the method further includes:

The authentication access port verifies the source IP address of the conference operation request, passes the verification, and performs the subsequent process; otherwise, discards the conference operation request.

After the authentication access port passes the verification of the IP address, the method further includes:

The authentication access port further verifies the password agreed by the multimedia conference engine system and the conference terminal;

After the password is verified, the subsequent process is performed; otherwise, the conference operation request is discarded, and the authentication response exits the result of the verification failure to the conference terminal.

After the password verification is passed, the method further includes:

The WEB module is connected to the application service module to verify whether the conference terminal account exists, the conference terminal account exists, and the subsequent process is performed; otherwise, the authentication response export returns the result of the verification failure to the conference terminal.

The conference operation includes at least one of the following: conference initialization, participation exit conference, conference suspension, conference control, conference member operation, moderator change and floor control, conference status subscription/notification, participant information subscription, and notification.

The beneficial effects of the present invention are: defining an API call interface for the multimedia conference system to be opened to the outside in the WEB module, using the request access port in the API call interface to access the conference operation request sent by the user through the conference terminal, and using the API call interface The request response outlet in the request feeds back the processing result of the conference operation request to the conference terminal by the conference engine system, thereby implementing various functions of the conference service. Since the API call interface is open to the outside world, on the one hand, various types of conference terminals can be used without limitation, on the other hand, it is easy to expand, which is beneficial to third-party development. DRAWINGS

1 is a multimedia conference engine system according to an embodiment of the present invention;

2 is a basic flowchart of a multimedia conference engine method according to an embodiment of the present invention; FIG. 3 is an authentication flowchart of a multimedia conference engine method according to an embodiment of the present invention; FIG. 4 is a multimedia diagram of an embodiment of the present invention; Conference initialization flow chart of the conference engine method;

FIG. 5 is a flowchart of conference information subscription and notification of a multimedia conference engine method according to an embodiment of the present invention. 1 is a multimedia conference engine system according to an embodiment of the present invention. As shown in FIG. 1, the system includes: a conference terminal 1, a WEB module 2, and an application service module 3;

The WEB module 2 includes an API call interface for the multimedia conference system to be open to the conference terminal 1. The API call interface includes a request access port 21 for accessing the conference operation request sent by the conference terminal 1, and is used for each conference. The request response response request is sent to the outlet 22; the WEB module 2 is configured to send the conference operation request accessed by the requesting access port to the application service module; and after the application service module feeds back the result of the conference operation request processing, Returning, by requesting response, the result of the conference operation request processing to the conference terminal;

The application service module 3 is configured to process the conference operation request sent by the WEB module 2, and feed back the result of the processing to the WEB module 2, and feed back to the conference terminal 1 by the request response outlet 22, so that the user of the conference terminal 1 performs Corresponding processing. The above API call interfaces are all defined in XML format, and are defined for conference operation functions including participation in exit conference, conference suspension, conference control, conference member operation, moderator change and floor control, conference status subscription/notification, and the like. Each has its own corresponding API call interface, and is released to the public through the WEB module for third-party development.

In addition, the API call interface further includes the use permission for using the request access interface 21. The authentication access port 23 of the right and the authentication response to the conference terminal are fed back to the exit terminal 24. 2 is a basic flowchart of a method for a multimedia conference engine according to an embodiment of the present invention. The basic process of the method is as follows:

Step S1: Define the API call interface.

Specifically, an API calling interface that is open to the conference terminal by the multimedia conference system is defined in the WEB module, where the API call interface includes a requesting access port for requesting each conference operation and a response request for each conference operation request. Request response to the exit. The API call interface is defined in XML format, and defines the conference operation functions including participation in the exit conference, conference suspension, conference control, conference member operation, moderator change and floor control, conference status subscription/notification, and the like. The functions have their own corresponding API call interface, and are released to the public through the WEB module for third-party development.

Step S2: Access the conference operation request.

Specifically, the WEB module sends the conference operation request that is accessed by the requesting access port to the application service module, and the application service module processes the conference operation request, and feeds the processing result back to the WEB module.

Step S3: The feedback operation requests the processing result.

Specifically, the WEB module feeds back the operation request processing result to the request through the request response interface, and the API call interface further includes: authenticating the authentication access port that uses the use permission of the request access interface, and feeding back the authentication result to the conference. The authentication response of the terminal is connected to the exit. The specific authentication process includes:

Before requesting the access port to access the conference operation request, the authentication access port verifies the source IP address of the conference operation request, and discards the conference operation request if the IP address verification fails; the authentication access port pair After the IP address is verified, the password agreed by the multimedia conference engine system and the conference terminal is further verified. If the password verification fails, the conference operation request is discarded. The authentication response receiving and exporting returns the result of the verification failure to the conference terminal; if the password verification is passed, the process proceeds to step S2; or, after the authentication access port passes the password verification, the WEB module is connected to the application service module to verify whether the conference terminal account is verified. If yes, the authentication response receiving and outputting returns the result of the verification failure to the conference terminal; if yes, proceeding to step S2 above.

The embodiment implements a multimedia conference engine method by using a multimedia conference engine system, and defines an API call interface for opening the multimedia conference system in the WEB module, and uses the request access port in the API call interface to connect the conference operation request sent by the user through the conference terminal. The request response response in the API call interface is used to feed back the processing result of the conference operation request by the conference engine system to the conference terminal, thereby implementing various functions of the conference service. Since the API call interface is open to the outside world, on the one hand, various types of conference terminals can be used without limitation, on the other hand, it is easy to expand and is beneficial to third-party development.

The multimedia conference engine method of the present embodiment will be specifically described below with specific examples. FIG. 3 is a flowchart of an authentication process of a multimedia conference engine method according to an embodiment of the present invention. As shown in FIG. 3, the method specifically includes the following process:

Step S31: Access request.

The user sends a conference operation access request to the WEB module through the conference terminal.

Step S32: IP address verification.

The WEB module performs IP address verification on the access request information. If the IP address verification fails, the request is discarded and the response is not received.

Step S33: The IP address verification is passed, and password verification is performed.

If the IP address is verified, the password agreed by the multimedia conference engine system and the conference terminal is verified. If the password verification fails, the result of the verification failure is fed back to the conference terminal.

Step S34: The password verification is passed, and the conference terminal account verification is performed.

If the password verification is passed, the WEB module is connected to the application service module to verify whether the conference terminal account exists. If it does not exist, the request is discarded, and the result of the authentication failure is reversed. Feed to the conference terminal.

Step S35: The feedback allows the access request.

If the conference terminal account is verified, the authentication response is sent to the conference terminal to feed back the response requesting the access request.

Step S36: The conference terminal receives the feedback result.

The conference terminal receives the feedback from the WEB module and performs corresponding processing.

FIG. 4 is a flowchart of a conference initialization process of a multimedia conference engine method according to an embodiment of the present invention. As shown in FIG. 4, the method specifically includes the following process:

Step S41: Access the conference initialization request.

The user sends a conference initialization request to the WEB module through the conference terminal. The WEB module accesses the conference initialization request through the requesting access port, and starts the authentication access port.

Step S42: IP address verification.

The authentication access port performs IP address verification on the conference initialization request information. If the IP address verification fails, the initialization request is discarded, and no response is received.

Step S43: The IP address verification is passed, and password verification is performed.

If the IP address is verified, the password agreed by the multimedia conference engine system and the conference terminal is verified. If the password verification fails, the conference initialization request is discarded, and the authentication response and the exit end feed back the result of the verification failure to the conference terminal.

Step S44: After the password verification is passed, the WEB module sends the conference initialization request to the application service module for processing.

If the password verification is passed, the WEB module sends the conference initialization request to the application service module for processing, and waits for the processing result of the application service module.

Step S45: Processing the conference initialization request.

The application service module receives the conference initialization request of the WEB module, performs processing, and feeds the conference request to the WEB module. Step S46: The feedback processing result is sent to the conference terminal.

The WEB module receives the processing result of the application service module, and feeds back the feedback through the request response to the step S47: the conference terminal processes the feedback result.

The conference terminal receives the request to hold the conference and performs corresponding processing.

The processes of conference suspension, conference control, conference member control, participation in exit conference, moderator change, and floor control are the same as the conference initialization process, and will not be repeatedly described herein.

FIG. 5 is a flowchart of conference information subscription and notification of a multimedia conference engine method according to an embodiment of the present invention. As shown in FIG. 5, the method specifically includes the following process:

Step S51: Access the site information subscription request.

The user sends a site information subscription request to the WEB module through the conference terminal. The WEB module accesses the site information subscription request through the requesting access port, and starts the authentication access port.

Step S52: IP address verification.

The WEB module performs IP address verification on the site information subscription request information. If the IP address verification fails, the site information subscription request is discarded, and no response is made.

Step S53: The IP address verification is passed, and password verification is performed.

If the IP address is verified, the password agreed by the multimedia conference engine system and the conference terminal is verified. If the password verification fails, the site subscription information request is discarded, and the authentication response is sent to the conference terminal.

Step S54: After the password verification is passed, the WEB module sends the field information subscription request to the application service module for processing.

If the password is verified, the WEB module sends the field subscription information request to the application service module for processing, and waits for the result of the return processing of the application service module.

Step S55: Processing the site information subscription request.

The application service module receives the site subscription information request of the WEB module for processing. Step S56: Do not subscribe. In the step S55, if the site information subscription request received by the application service module indicates that the site information is not subscribed, the request is agreed to and the current site information is fed back to the WEB module.

Step S57: The processing result is fed back to the conference terminal. The WEB module receives the processing result of the application service module, and feeds back the response of the operation success and the response of the current site information to the conference terminal by requesting the response to the exit, and proceeds to step S60.

Step S58: Subscribing. In the step S55, if the user subscribes to the site information on the conference engine service side, it indicates that the site information subscription request received by the application service module needs to subscribe to the site information, and the application service module records the request information of the user site information subscription.

Step S59: The processing result is fed back to the conference terminal application service module. The application service module feeds back the site information and the current site information to the WEB module. After receiving the agreement of the application service module to subscribe to the site information and the current site information, the WEB module feeds back the successful result of the subscription to the conference terminal by requesting the response to the export.

Step S60: The site information is updated. After the site information changes, the application service module notifies the WEB module; the WEB module feeds back the response of the current site information to the conference terminal according to the agreed mode of the status notification callback interface.

The participant information subscription and notification process is the same as the site information subscription and notification process, and will not be described repeatedly.

The above is a further detailed description of the present invention in connection with the specific embodiments, and the specific embodiments of the present invention are not limited to the description. It will be apparent to those skilled in the art that the present invention can be made without departing from the spirit and scope of the invention.

Claims

Claim

A multimedia conference engine system, the system comprising: a conference terminal, a WEB module, and an application service module, wherein the WEB module includes an API call interface that is open to the multimedia conference system, and the API call interface includes Responding to the requesting access port for each conference operation request and the request response for each conference operation request response;

The multimedia conference engine system according to claim 1, wherein the API call interface further includes an authentication access port and an authentication response outlet;

The authentication access port is configured to authenticate the use permission of the requesting access interface, and the authentication response is used for exporting the authentication result to the authentication response of the conference terminal.

The multimedia conference engine system according to claim 1 or 2, wherein the conference operation comprises at least one of the following: conference initialization, participation in an exit conference, conference suspension, conference control, conference member operation, and moderator change. And floor control, meeting status subscriptions and notifications, attendee information subscriptions and notifications.

The multimedia conference engine system according to claim 1 or 2, wherein the API call interface uses an XML format.

5. A multimedia conference engine method, the method comprising:

Setting an API call interface for the multimedia conference system to be opened to the outside in the WEB module, where the API call interface includes a request access port for requesting each conference operation request and a request response export port for responding to each conference operation request response; The WEB module sends the conference operation request accessed by the requesting access port to the application service module; the application service module processes the conference operation request, and feeds the processing result back to the WEB module; the WEB module requests the conference operation by requesting the response to the export. The result of the processing is fed back to the conference terminal.

The multimedia conference engine method according to claim 5, wherein the API call interface further comprises: an authentication access port that authenticates the use permission of the request access interface, and the authentication is performed. The result is fed back to the authentication terminal of the conference terminal to receive the exit;

Before the WEB module sends the conference operation request that is accessed by the access port to the application service module, the method further includes:

The method of the multimedia conference engine according to claim 6, wherein after the authentication access port passes the verification of the IP address, the method further includes:

The authentication access port further verifies the password agreed by the multimedia conference engine system and the conference terminal; the password verification passes, and the subsequent process is performed; otherwise, the conference operation request is discarded, and the authentication response exits the result of the verification failure to the conference terminal.

The multimedia conference engine method according to claim 7, wherein after the password verification is passed, the method further includes:

The multimedia conference engine method according to any one of claims 5 to 8, wherein the conference operation comprises at least one of the following: conference initialization, participation exit conference, conference suspension, conference control, conference member operation, Moderator changes and floor control, meeting status subscriptions/notifications, attendee information subscriptions and notifications.