JPH1198139A - Conference management equipment, system and method for internet - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide an interface that is controlled based on a web to manage an IP(Internet protocol) multicast session among pluralities of users. SOLUTION: Information to schedule a conference session is received by a user interface and a network interface receives information corresponding to users 90 taking part in a conference. A database stores conference schedule information and information corresponding to users taking part in the conference. A voice bridge manager 50 receives an instruction from the user interface, accesses the information stored in the database and gives an instruction to a voice bridge 30 to set up telephone connection with the user participants 90. An IP multicast network 95 generates an IP multicast address used to send multimedia information to the conference participants 90.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

The present invention relates generally to Internet communication systems, and more particularly, to a web-based interface for creating and managing Internet Protocol multicast conferences between multiple users.

[0002]

2. Description of the Related Art Currently, Internet Protocol (IP) data packets transmitted over an internetwork (Internet) are either unicast addresses used to send packets from a source to one recipient or from a source to an entire subnetwork. Have a broadcast address used to send packets to the network. The unicast protocol is limited to one source and one receiver configuration. Broadcast transmission protocols send data packets to a number of recipients limited by the sum of the bandwidth allowed for the source, regardless of whether the recipients in the subnetwork want to receive the packets.

[0003] An alternative to unicast and broadcast transmissions is IP multicast routing. Multicast routing allows a source to deliver one copy of a data packet to multiple recipients who are members of a multicast group within the same subnetwork or across different subnetworks. A multicast backbone, or M-bone, is an interconnected set of sub-networks that support the delivery of IP multicast traffic. The M-bone fills the destination address field of the IP packet header with 224.0.0.0.
239.255.255.255 to route packets across multiple networks using group addresses. Once a user has joined a particular multicast session, IP packet traffic is delivered by the network address infrastructure to all members of the group. By using M-bones, only one copy of a multicast message or data packet is sent through any node in the network. Multiple copies of the message are made only at the point where the network router splits the transmission path.
In this way, the network transmission bandwidth is kept constant.

[0004] For multicast routing, a group membership protocol is used by a network router to determine which users within that router's subnetwork belong to a particular multicast session. The user sends a group membership message notifying the network that it wants to receive IP traffic sent to a particular group of participants. In this way, the user can initiate the process of connecting to the multicast group session so that the initiator of the session does not have to maintain a participant list.

[0005]

Problems with the current multicast session are as follows. That is, participants can receive information from the group, but are merely recipients in that they cannot perform collaborative or interactive tasks.

Another problem is that packet delay, echo, and packet loss occur during voice communication.

[0007] Furthermore, since a multicast session is available to all users who have acquired a multicast address, security management of participants is almost impossible. In addition, a tool that currently allows users to access a web-based interface to schedule multicast sessions within a specific group of users, providing voice connectivity only to those users participating in the multicast conference session There are no tools available.

Thus, scheduling of IP multicast sessions accessible to all users with a web browser and used as conference tools and application sharing tools;
There is a need for an Internet web-based interface device for administration, security and maintenance.

[0009]

SUMMARY OF THE INVENTION A conference management apparatus for the Internet according to the present invention is an apparatus for managing an interactive conference between a plurality of users using an Internet protocol multicast network. A network interface residing on a browser, a user interface accessible via an Internet web browser, and adapted to communicate with the user interface and receive information related to the conference session;
A voice interface for receiving a command from the user interface and establishing a voice connection between the plurality of users; and an internet between the plurality of users receiving the command from the user interface and participating in the conference. A multicast interface for transmitting multimedia information via a protocol multicast network.

[0010] The user interface is located on an Internet web server, and is applicable to extracting schedule information corresponding to the conference.

[0011] The information processing apparatus may further include a database for storing information on the plurality of users.

[0012] The voice interface may further include a voice bridge manager for receiving and processing the instructions received at the user interface.

[0013] Further, the voice interface includes a voice bridge for establishing a voice connection with the plurality of users.

Further, the user interface includes a hypertext markup language page.

Further, the user interface generates a session identification code unique to a specific conference session.

[0016] The user interface may generate a session access code communicated to the user for accessing the conference session.

Further, the multicast interface communicates with the multicast network via a session description protocol file.

[0018] The multicast interface may generate a multicast address for transmitting the multimedia information to the user during the conference session.

A conference management system for the Internet according to the present invention is a system for performing a multimedia conference among a plurality of users using an Internet protocol multicast network, wherein the plurality of users are accessible and correspond to a scheduled conference. A user interface on an Internet web server for inputting information associated with the conference, a network interface on an Internet web server for inputting information corresponding to a plurality of users participating in the conference session, and the scheduled conference. Storing the information corresponding to the plurality of users participating in the scheduled conference and the information corresponding to the plurality of users participating in the scheduled conference. A database allowing access to confirm conference information by a face, a voice bridge manager communicating with the user interface and accessing information stored in the database, and a voice bridge manager communicating with the voice bridge manager; A voice bridge for initiating a telephone connection with the plurality of users based on instructions received from the interface, and generating an IP multicast address used to send multimedia traffic to the plurality of users participating in the conference And an address generator for performing the operation.

The voice bridge dials a telephone number associated with each of the users participating in the conference.

Further, the information corresponding to the plurality of users participating in the conference session includes an Internet address associated with each of the users.

Further, the information stored in the database is accessed using a common gateway interface script.

Further, each of the users receives the multicast traffic via a multicast enabling router.

[0024] The apparatus may further include a gateway server connected to the multicast enabling router, wherein the user is connected to the gateway server to receive the multicast traffic.

A method for managing an interactive Internet Protocol Multicast Conference session according to the present invention is a method for managing an interactive Internet Protocol multicast conference session, comprising the steps of: accessing a user interface via an Internet web browser; Entering information about the conference session and the user conference participant; storing the information about the conference session and the conference participant in a database; and generating an Internet Protocol multicast address associated with the conference session. A multicast session corresponding to the multicast address. To activate the, characterized by comprising the steps of: via the internet protocol multicast network transmits the multimedia information to the conference participants.

The method may further include the step of authenticating the information corresponding to the conference session schedule.

[0027] The method may further include the step of establishing a voice connection with the conference participant based on the information stored in the database.

[0028] The conference participant receives multicast traffic from the multicast network via a multicast enabling router.

The conference participant receives the multicast traffic from the multicast network via a gateway server connected to a multicast enabling router.

[0030] The method may further include a step of dynamically generating a session description protocol file from information stored in the database regarding the conference session.

[0031] The method may further include the step of activating a browsing application via the user interface for transmitting multicast traffic.

The system manages an Internet Protocol Multicast Network Conference session where multiple users receive the transmitted multimedia information. A network interface on the web server manages the conference session.
An interface accessible via a web browser can be applied to receive information about the conference session. The voice interface establishes a voice connection between the conference participants.
The multicast interface sends multimedia information over an internet protocol network.

[0033]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Referring to FIG. 1, a system 10 according to the present invention includes a session manager 20, a multicast address generator 30, a directory manager 40, a voice bridge manager 50, a session activator 60, and a voice bridge 70. Yes,
Set up, manage and participate in multimedia sessions and enable users to engage in multimedia closed user group (CUG) activities, such as application sharing among multiple users. This system uses the Internet 94 and IP
A normal telephone system (POTS) network 75 interconnecting with a multicast network 95
Are also interconnected to establish a multimedia session.

A multicast conference session is an interactive voice, video and / or data session shared among multiple users. For purposes of illustration, FIG. 1 shows users 80 and 90, but it will be appreciated that the present invention can establish a conference session with a number of participants not shown in FIG. A session initiator or host 80 having a computer 81 and a telephone 82 accesses an Internet web browser to book a session, and accesses the conference service web page via the session manager 20 using its computer 81. As a session participant, a user 90 having a computer 91 and a telephone 92
The conference 91 is accessed through the session manager 20 using the computer 91. The front end of the session manager 20 is
Host 80 and user 90 for security purposes
Such that participants can be authenticated by the system. At the session reservation time, the host 80
By accessing a hypertext markup language (HTML) page, the session manager 2 provides all the information needed to activate the session.
0 is provided. This information includes the conference session title, session start time, session end time, session duration, number of session repetitions, number of ports or participants in the session, required bandwidth, media type used, etc. You can go out. These addresses are automatically generated by the multicast address generator 30 based on the date and time, the duration, and the number of repetitions input from the host 80. Alternatively, the IP multicast address needed to initiate and maintain the conference session and the ports needed for different media types are manually entered by user 80 using session manager 20 at the start of the conference. May be. The multicast address generator 30 retrieves the nearest unassigned address from the list of reserved multicast class D address blocks,
Automatically generate an IP multicast address. The information received from host 80 is sufficient to generate a session description protocol (SDP) file. Once the session information is stored, the session I
D and the access code are returned to host 80 as the conference initiator. Profile data associated with the host 80 may be retrieved from the directory manager 40 and pre-positioned in an area at the start of the conference session. The profile information associated with the host 80 may include a name, an e-mail address, a telephone number, a company name, and the like. Once a session is scheduled, all data for that session is stored in the directory manager 40 corresponding to the session ID generated by the session manager 20 for a particular conference. Further, once the session is scheduled, the host 80 can invite additional participants, such as the user 90, via another communication mechanism, such as email and / or telephone, thereby providing them with a session The title, description, date, start time, end time, session ID, and the most important session access code that allows the user to access the conference. In this way, session security is maintained because only participants with a valid session ID and access code can participate in the multicast conference.

To activate the audio portion of the conference, the session activator 60 communicates with the audio bridge manager 50 and, based on the session ID retrieved from the directory manager 40 for the particular conference, the participants 90 and Set up a bridge conference accessible to host 80. The session activator 60 continuously inquires of the directory manager 40 about the start date and time and the repetition date and time of the scheduled session,
Includes a process that activates the session if it matches the current date and time. The participant 90 inputs the session ID, the access code, and his / her name and telephone number, and
0 authenticates that the input information is correct. And
Session manager 20 retrieves information associated with a particular conference session from directory manager 40. The session manager 20 communicates with the voice bridge manager 50 to cause the participant 90 to participate in a voice session corresponding to a specific session ID. The session manager 20 sends the telephone number of the participant 90 to the voice bridge manager 50, which instructs the voice bridge 70 to call the telephone 92 of the participant 90, which normally Voice connection via the POTS network 75 is realized. A similar process occurs with the realization of the telephone 80 of the host 80 and the voice connection of the host.

Once a voice connection is established between participant 90 and voice bridge 70, an SDP file is dynamically generated from information retrieved from directory manager 40 for the conference session. SDP
The file is in a format that can be understood and processed by a viewer application to provide the multicast data to the user. This information is stored in the MIME content type application / x-
It is returned to the web browser used by the participant 90 having sdp. As a result, the browsing application can be automatically started from the participant's browser as usual.

Session manager 2 in the system
0, the transmission of information between the multicast address generator 30, the directory manager 40, the voice bridge manager 50 and the session activator 60, via the Internet, an asynchronous transfer mode connection, a serial line connection, a standard modem or other similar transmission medium.
Transmission Control Protocol / Internet Protocol (TC
(P / IP) socket connection. Session manager 20 communicates with multicast address generator 30, directory manager 40 and voice bridge manager 50 by using a common gateway interface (CGI) program residing on a web server. If the multicast address generator 30, directory manager 40, or voice bridge manager 50 is on a separate machine other than the web server, communication between the components can be performed by any remote mechanism such as a remote procedure call (RPC) from a CGI script. May be made. Each CGI program analyzes parameters from a URL or submission form received from the user's browser (using a method such as GET or POST).

As mentioned briefly above, the session manager 20 functions as an entry point into the conference system and as a central point for administration, coordination and communication with other session participants. Session manager 20 resides on an Internet web server and is widely available to all Internet users. Users 80 and 9
0 accesses an HTML page acting as a gateway to the session manager 20 via a web browser on the user's desktop computer. Host 80 schedules a particular conference session by entering information via an HTML page.

The directory manager 40 comprises a database containing various participant information associated with the scheduling of a particular conference session received from the session manager 20. For example, the stored information includes the participant's name, company name, email address,
It may include phone numbers, fax numbers, and the like. Further, the directory manager 40 includes a session ID,
Session title, session start time, session end time, multicast range, type and format of media used in the session and corresponding IP multicast address and port, quality of service information, bandwidth, as well as active conference session and its participants Store the multicast attributes associated with the particular conference session, including the corresponding information. This information is received from the session initiator via the session manager 20. The architecture associated with directory manager 40 provides a mechanism for Internet users to query and manage any database of hierarchical attribute / value pairs ("" What is a Directory Service? And What is L
DAP ”SLAPD and SLURPE Administrators Guide, Unive
rsity of michigan, Release 3.3 April 3, 1996
(Such as the Lightweight Administrative Access Protocol (LDAP) described in the "Day 0 Publication"). Alternatively, data stored in directory manager 40 may be stored and searched in a commercial database.

The session manager 20 uses the CGI script to make the directory manager 4
Access the information stored in 0. This task is called C
Making database calls from CGI scripts is implemented by various tools such as Rogue Wave, dbTools h ++ and Tools h ++ libraries. Alternatively, existing information may be updated or deleted while new information is added to a database in directory manager 40 by an SQL command or other tool executed by a coordinator or supervisor with special access rights. Good. Each conference session and its attributes are queried using the session ID as the primary key. The session subscriber is registered with the directory manager 40 before the start of the conference session. Alternatively, the conference participant can register himself or another conference participant with the directory manager 40 at the start of the conference session. FIG. 5 is a diagram showing an example of the subscriber information stored in the database of the directory manager 40.

The voice bridge manager 50 receives a command from the session manager 20 regarding the multicast conference session. The voice bridge manager 50 is connected to the voice bridge 70 via a communication protocol such as DATAKIT and communicates all statuses and controls to the voice bridge 70.
Contains PI. Voice bridge manager 50 shares the same database with session manager 20 and has access to all necessary participant session information. The communication between the session manager 20 and the voice bridge manager 50 is such that the procedure call is CGI
RP performed over the network using a script
Executed via C. Thus, for example, the participant's P
All status changes, such as the termination of the OTS connection, are sent from the voice bridge 70 to the voice bridge manager 50.
, Where the HTML screen is dynamically updated in the session manager 20 by server push technology. The web server dynamically updates the data to the browser without explicitly requesting the browser to receive the data. At the conference session activation time, a voice session is activated at voice bridge 70 by communication between session manager 20 and voice bridge manager 50. An IP multicast application server on the multicast network 95 initiates voice, video or data transmission to the IP multicast address specified by the session reservation or activation time. In order for host 80 and participant 90 to receive IP multicast traffic, they must access a multicast-enabled router. If users 80 and / or participants 90 are not connected to a multicast-enabled router, they must be connected to a gateway server that communicates with the multicast-enabled router that allows end users to receive multicast traffic. No. Voice bridge manager 50 may be on either the same web server machine where session manager 20 is located, or on another machine.

FIG. 2 is a flowchart showing a typical process for starting a multicast session and inviting participants to the session using the system described with reference to FIG. The process begins at step 200, where the session initiator or host 80 accesses a web-based interface via the session manager 20 using his web browser. Host 8
0 inputs related session information authenticated by the system based on the user password authentication process in step 201. If the authentication is not successful, an error message is sent to the web browser of host 80 in step 202 and the process proceeds to step 21
Exit at 0. If the authentication of step 201 is confirmed, the process proceeds to step 203, where the host 80 requests reservation of the multicast session and uses the HTM to schedule the conference.
L pages are provided to the host 80. The host 80 inputs the conference session parameters necessary to start the conference session at step 203, as described above. In step 204, the session manager 20 communicates with the multicast address generator 30 to send the scheduled date, start time and end time of the session. In step 204, the user 80 receives the IP multicast address from the multicast address generator 30. In step 205, all data related to the conference session is stored in the directory manager 40 and the
At 04, it is associated with the specific session ID generated by the session manager 20. In step 206, the specific session ID and the session manager 20
And the access code automatically generated by the host 80. In step 207, session access information such as the date and time of the conference is transmitted to the participant 90 via the session manager 20 along with the related user information. Alternatively, the initiator user can notify participant 90 and other participants via email or some other communication mechanism such as a telephone.

FIG. 3 is a flowchart showing a typical example of a session activation process using the system described with reference to FIG. The session is activated by the session activator 60 at the time entered during the conference scheduling period. In step 301, the session activator 60
Obtains pre-stored information about a particular conference session from the directory manager 40. The session activator 60 determines in step 302
, The voice bridge manager 50 is notified by an RPC call from the CGI script to the voice bridge manager 50 to activate a new voice session on the voice bridge 70 associated with the particular session ID. In step 303, the session activator 60 notifies the directory manager 40 to update and activate the current conference session status. The process then ends at step 304.

FIG. 4 is a flowchart illustrating a typical process for adding a participant 90 to an activated multicast session using the system described with reference to FIG. The participant 90 accesses the session manager 20 via a web browser. Participant 9
0 is authenticated to the system by entering a username and password. In step 401, participant 90 requests an HTM to join the conference session.
Take out the L page and enter the session ID and access code. Then, in a conditional branch 402, the session manager 20 attempts to authenticate the user information by querying the directory manager 40, and the session I given to the participant in step 401
Check D and access code. If step 40
If the confirmation cannot be made in step 2, the participant 90
Is given an error message, and the session manager 20 denies the participant 90 access. If the session is valid, the process proceeds to step 404 where another conditional is executed to determine at step 402 whether the authenticated session is currently active.
The active session condition branch is executed by the session manager 20 calling an API on the voice bridge manager 50 to check whether the session is active. If the conference session is not active, an error message is given to the user at step 405 and the process proceeds to step 41
It ends with 1.

If it is determined in step 404 that the conditional branch is satisfied and that the session is active, in step 406, session manager 20 retrieves information associated with the particular session from directory manager 40. In step 407, session manager 20 calls a CGI script located on a web server used by participant 90. The participant 90 initiates communication with the voice bridge manager 50 via RPC and sends the telephone number of the participant 90 to the voice bridge manager 50 by calling an appropriate API. A voice connection with the participant 90 is established at step 408 by the voice bridge manager 50 communicating with the voice bridge 70 and calling the telephone 92 associated with the participant 90 using the bridge interface. In step 409, once the participant 90 subscribes to the voice session, the session manager 20 generates an SDP file by the MIME content type application / x-sdp based on the data retrieved from the directory manager 40, and joins this file. Is returned to the web browser used by the person 90. In step 410, upon receiving the SDI file, the web browser associated with the participant 90 activates the IP multicast viewing application to allow the participant 90 to join the multicast session of the IP multicast address specified in the SDP file. . The participant 90 receives the multicast data transmitted between the users of the session. This viewing application may be built as a plug-in or helper application for the participant's browser.

When the voice connection of the POTS network 75 is disconnected by the API call to the voice bridge manager 50 by the session manager 20, the participant may leave the session at any time and the viewing application terminates the process at step 411. It will be terminated at that point. Alternatively, the session may be terminated at the display stop time entered by the host 80 at the beginning of the scheduled session, or may be terminated at any time by the host.

Using a web-based controlled interface, a multicast conference session is created and managed among a large number of participants. The unique session ID and access code guarantee a closed user group that imposes access restrictions for conference security. The voice bridge manager coordinates communications between participants using the voice bridge and establishes a voice connection using the POTS network. In this way, a multicast session is established between specific groups of users, which provides a voice connection to those users participating in the multicast conference session. The multicast conference system according to the present invention comprises:
Utilize user interface and network interface. With this user interface,
Participants can set up a multicast session while the network interface retrieves information from the appropriate user database.

[Brief description of the drawings]

FIG. 1 is a block diagram of a system according to an embodiment of the present invention.

FIG. 2 is a flowchart showing a typical process for starting a multicast session.

FIG. 3 is a flowchart illustrating an exemplary process for activating a multicast session.

FIG. 4 is a flowchart illustrating an exemplary process for a user joining an active multicast session.

FIG. 5 is a diagram showing an example of subscriber information stored in a directory manager database in a table format.

[Explanation of symbols]

20 session manager, 30 multicast address generator, 40 directory manager,
50 voice bridge manager, 60 session activator, 70 voice bridge, 75 POTS, 8
0,90 Host (user), 81,91 Computer, 82,92 Telephone, 94 Internet, 95
IP multicast network.

 ──────────────────────────────────────────────────続 き Continuing on the front page (72) Inventor Mojan Dash Dashty United States Tinton Falls Citation Court, New Jersey 22 (72) Inventor Vikram Earl Saxena United States New Jersey Freehold Bennington Road 281

Claims (23)

[Claims] 1. An apparatus for managing an interactive conference between a plurality of users using an Internet protocol multicast network, comprising: a network interface on an Internet web browser for managing a conference session, accessible via the Internet web browser. A user interface adapted to communicate with the user interface and receive information related to a conference session; and a voice receiving instructions from the user interface and establishing a voice connection between the plurality of users. And an Internet protocol between the plurality of users participating in the conference, receiving instructions from the user interface. Internet for Conference management apparatus characterized by comprising: a multicast interface, the transmitting multimedia information over a multicast network. 2. The conference management apparatus according to claim 1, wherein the user interface is located on an Internet web server and is applicable for extracting schedule information corresponding to the conference. 3. The Internet conference management device according to claim 1, further comprising a database for storing information on the plurality of users. 4. The apparatus of claim 1, wherein the voice interface includes a voice bridge manager for receiving and processing the instructions received at the user interface. 5. The conference management apparatus for the Internet according to claim 4, wherein said voice interface includes a voice bridge for establishing a voice connection with said plurality of users. 6. The conference management apparatus according to claim 1, wherein the user interface includes a hypertext markup language page. 7. The conference management apparatus according to claim 1, wherein the user interface generates a session identification code unique to a specific conference session. 8. The conference management apparatus according to claim 1, wherein the user interface generates a session access code communicated to the user for accessing the conference session. 9. The conference management apparatus according to claim 1, wherein the multicast interface communicates with the multicast network via a session description protocol file. 10. The multicast interface according to claim 1, wherein the multicast interface generates a multicast address for transmitting the multimedia information to the user during the conference session.
The conference management device for Internet described in the above. 11. A system for providing a multimedia conference between a plurality of users using an internet protocol multicast network, wherein the plurality of users are accessible and have access to the Internet for inputting information corresponding to a scheduled conference. A user interface at a web server; a network interface at an internet web server for inputting information corresponding to a plurality of users participating in the conference session; and the information corresponding to the scheduled conference and the scheduled conference. Storing the information corresponding to the plurality of users participating in the conference, and confirming the conference information by the user interface. A voice bridge manager that communicates with the user interface and accesses information stored in the database; communicates with the voice bridge manager and, based on instructions received from the user interface, A voice bridge for initiating a telephone connection with a plurality of users; and an address generator for generating an IP multicast address used to send multimedia traffic to the plurality of users participating in the conference. Conference management system for the Internet. 12. The voice bridge of claim 1, wherein the voice bridge dials a telephone number associated with each of the users participating in the conference.
2. The conference management system for Internet according to 1. 13. The conference management for the Internet according to claim 11, wherein the information corresponding to the plurality of users participating in the conference session includes an Internet address associated with each of the users. system. 14. The conference management system for the Internet according to claim 11, wherein the information stored in the database is accessed using a common gateway interface script. 15. The conference management system according to claim 11, wherein each of the users receives the multicast traffic via a multicast enabling router. 16. The Internet conference of claim 11, further comprising a gateway server connected to a multicast-enabled router, wherein said user is connected to said gateway server to receive said multicast traffic. Management system. 17. A method for managing an interactive Internet Protocol multicast conference session, comprising the steps of: accessing a user interface via an Internet web browser; and using the user interface for the conference session and a user conference participant. Inputting information; storing the information about the conference session and the conference participants in a database; generating an Internet Protocol multicast address associated with the conference session; and a multicast corresponding to the multicast address. Activate a session to activate Internet Protocol Internet for Conference management method characterized by comprising the steps of transmitting multimedia information to the conference participants through a multicast network. 18. The conference management method according to claim 17, further comprising the step of authenticating the information corresponding to the conference session schedule. 19. The method of claim 17, further comprising establishing a voice connection with the conference participant based on information stored in the database. 20. The method of claim 17, wherein the conference participant receives multicast traffic from the multicast network via a multicast enabling router. 21. The conference management method according to claim 17, wherein the conference participant receives the multicast traffic from the multicast network via a gateway server connected to a multicast enabling router. 22. The method of claim 17, further comprising dynamically generating a session description protocol protocol file from information stored in the database regarding the conference session.
Conference management method for Internet described. 23. The method of claim 22, further comprising the step of launching a browsing application via the user interface to transmit multicast traffic.