CN102082675B - Method and equipment for service processing of remote-presence conferences - Google Patents

Abstract

The present invention provides a telepresence conference service processing method and equipment. The method includes obtaining the binding relationship between the main and auxiliary screens of the telepresence conference terminal including at least two screens; according to the binding relationship between the main and auxiliary screens, sending a message for applying for resources to the MRS, and the message for applying for resources carry the information of each screen in order to establish a session for joining the telepresence conference corresponding to each screen. The embodiment of the present invention can improve the scope of application and distinguish each screen.

Description

Telepresence conference service processing method and equipment

technical field

The invention relates to network communication technology, in particular to a method and equipment for processing telepresence conference services.

Background technique

A telepresence terminal includes multiple screens, and each screen includes at least one or more video streams, zero or more voice streams, and even data streams and control streams. Therefore, it is necessary to give the terminal joining process to realize terminal and video exchange The platform (Multipoint Control Unit, MCU) has the function of establishing multiple media streams. In the prior art, when a telepresence terminal including multiple screens joins a conference, only one session is established, and then multiple sub-sessions are negotiated through Real-time Transfer Protocol (RTP)/RTP Control Protocol (RTCP). session. A private protocol is used in the process of negotiating multiple sub-sessions.

In the prior art, adopting a private protocol will limit the scope of use. In addition, when only one session is established, each terminal corresponds to only one terminal identifier. In this way, in the conference control process, it is impossible to identify the main screen or the auxiliary screen, and it is difficult to accurately control multiple screens included in one terminal.

Contents of the invention

Embodiments of the present invention provide a telepresence conference service processing method and equipment, which are used to solve the problems in the prior art that the scope of application is limited and it is difficult to control each screen.

An embodiment of the present invention provides a telepresence conference business processing method, including:

Obtain the binding relationship between the main and auxiliary screens of the telepresence conference terminal including at least two screens;

According to the binding relationship between the main and auxiliary screens, send a message for applying for resources to the MRS, and the message for applying for resources carries the information of each screen, so as to establish a conference for joining a telepresence conference corresponding to each screen. session.

An embodiment of the present invention provides a telepresence conference service processing device, including:

An acquisition module, configured to acquire the binding relationship between the main and auxiliary screens of the telepresence conference terminal including at least two screens;

The resource application module is configured to send a resource application message to the MRS according to the binding relationship between the primary and secondary screens, and the resource application message carries information about each screen, so as to establish a corresponding screen for each screen. Session used to join a telepresence meeting.

It can be seen from the above technical solution that, by establishing a session for each screen in the embodiment of the present invention, there is no need to use a private protocol to negotiate multiple sub-sessions in an established session, which can improve the scope of application; Establish a session for each screen separately, you can distinguish different screens according to the parameters in the session, realize the control of each screen, and solve the problem of not being able to distinguish each screen.

Description of drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following will briefly introduce the drawings that need to be used in the description of the embodiments. Obviously, the drawings in the following description are some embodiments of the present invention. For those skilled in the art, other drawings can also be obtained based on these drawings without any creative effort.

Fig. 1 is the schematic flow chart of the method of the first embodiment of the present invention;

Fig. 2 is a schematic flow chart of the method of the second embodiment of the present invention;

3 is a schematic flow diagram of a method according to a third embodiment of the present invention;

4 is a schematic flow diagram of a method according to a fourth embodiment of the present invention;

5 is a schematic flow chart of a method according to a fifth embodiment of the present invention;

6 is a schematic flow diagram of a method according to a sixth embodiment of the present invention;

Fig. 7 is a schematic diagram of the equipment structure of the seventh embodiment of the present invention.

Detailed ways

In order to make the purpose, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments It is a part of embodiments of the present invention, but not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by persons of ordinary skill in the art without making creative efforts belong to the protection scope of the present invention.

Fig. 1 is a schematic flow chart of the method of the first embodiment of the present invention, including:

Step 11: Obtain the binding relationship between the primary and secondary screens of the telepresence conference terminal including at least two screens;

Step 12: Send a message for applying for resources to a media resource server (Media resource server, MRS) according to the binding relationship between the main and auxiliary screens, and the message for applying for resources carries the information of each screen, so as to correspond to each Each screen establishes a session for joining a telepresence conference.

In this embodiment, by establishing a session for each screen, there is no need to use a private protocol to negotiate multiple sub-sessions in an established session, which can improve the scope of application; and, in this embodiment, by establishing a session for each screen, Different screens can be distinguished according to the parameters in the session, and each screen can be controlled to solve the problem of not being able to distinguish each screen.

The telepresence terminal may include multiple screens. In the following embodiments, each telepresence terminal will include three screens as an example. The three screens are: main screen (main), left auxiliary screen (left) and right auxiliary screen. screen (right). In addition, in the following embodiments, the MRS is used as an example for a media resource function controller (Media resource function controller, MRFC) and a media resource function processor (Media Resource Function Processor, MRFP) (abbreviated as MRFC/MRFP). Wherein, the MRFC and the MRFP may be two separate network elements, or may be one network element.

FIG. 2 is a schematic flow diagram of a method in the second embodiment of the present invention. In this embodiment, a telepresence terminal dials a conference access number to join a conference, and the conference server presets a binding relationship between primary and secondary screens as an example. Referring to Fig. 2, the present embodiment includes:

Step 21: The main screen sends a request message for joining the conference to the conference server, and the request message for joining the conference includes the conference access number and the main screen number.

For example, the request message for joining the conference is a session establishment protocol (Session Initiation Protocol, SIP) message, specifically as:

SIP INVITE(SDP offer 1)

Request-URI=meeting access number, From=main screen number.

Step 22: The conference server sends a message for applying for resources to the MRFC/MRFP according to the preset binding relationship between the main and auxiliary screens, and the message for applying for resources carries the information of each screen.

For example, the conference server sends the following message to MRFC/MRFP:

SIP INVITE(SDP offer 1)

Request-URI: sip:msml-video-conf=<conference ID><MRFC IP addr>:<port>

From: <Conference Server>

TelePresence-URI: <main screen number>; position=main

TelePresence-URI: <left screen number>; position=left; index=1

TelePresence-URI: <right screen number>; position=right; index=1

Step 23: MRFC/MRFP returns a response message to the conference server.

For example, return a 200 INVITE (SDP answer 1) message.

Step 24: The conference server returns a response message to the main screen.

For example, return a 200 INVITE (SDP answer 1) message.

Step 25: The main screen sends a confirmation message, such as an ACK message, to the conference server.

Step 26: The conference server sends an acknowledgment message, such as an ACK message, to the MRFC/MRFP.

So far, the primary session description protocol (Session Description Protocol, SDP) media negotiation between the main screen and MRFC/MRFP is completed, and the main screen successfully joins the conference.

In addition, in this embodiment, the main screen actively applies to join the meeting as an example. It may also be that the conference server requests the main screen to join the conference. For the process of the conference server requesting the main screen to join the conference, refer to other embodiments below.

In this embodiment, by establishing a session for each screen, there is no need to use a private protocol to negotiate multiple sub-sessions in an established session, which can improve the scope of application; and, in this embodiment, by establishing a session for each screen, Different screens can be distinguished according to the parameters in the session, and each screen can be controlled to solve the problem of not being able to distinguish each screen. In addition, in this embodiment, the binding relationship between the main screen and the auxiliary screen is preset in the conference server, which can reduce the message overhead of the interaction between the main screen and the conference server.

After the main screen successfully joins the conference, the conference server can automatically invite the secondary screen number registered by the telepresence terminal. See next example.

FIG. 3 is a schematic flowchart of a method according to a third embodiment of the present invention. In this embodiment, the conference server invites a secondary screen to join a conference as an example. Referring to Fig. 3, the present embodiment includes:

Step 31: The conference server sends a message for inviting to join the conference to the left auxiliary screen.

For example, the message for inviting to join the meeting is SIP INVITE (without SDP).

Step 32: The left auxiliary screen returns a provisional response message to the conference server.

For example, the provisional response message is 100 Trying or 180 Ringing.

Step 33: Answer automatically or manually on the left auxiliary screen.

Step 34: The left auxiliary screen sends a response message to the conference server.

For example, the response message is 200 INVITE (SDP offer 2) or 200 OK (SDP offer).

Step 35: The conference server sends a request message for joining the conference to the MRFC/MRFP, and the message carries the information of the left auxiliary screen.

For example, the request message to join a meeting is:

SIP INVITE(SDP offer2)

TelePresense-URI=<left screen number>; position=left; index=1.

Step 36: MRFC/MRFP sends a response message to the conference server.

For example, the message is 200OK (SDP answer2).

Step 37: The conference server sends an acknowledgment message, such as an ACK message, to the MRFC/MRFP.

Step 38: The conference server sends a confirmation message, such as ACK (SDP answer 2), to the left auxiliary screen.

So far, the preliminary SDP media negotiation between the left auxiliary screen and MRFC/MRFP has been completed.

In addition, while inviting the left auxiliary screen, the right auxiliary screen can also be invited at the same time, and the process of inviting the right auxiliary screen can be referred to for execution. In addition, the process of inviting the left sub-screen and the process of inviting the right sub-screen have no chronological relationship. For example, you can invite the left sub-screen first and then invite the right sub-screen, or invite the right sub-screen first and then invite the left sub-screen, or at the same time Invite the left secondary screen and the right secondary screen.

In this embodiment, by carrying the information of the auxiliary screen when the auxiliary screen joins, the MRFP/MRFC can determine the main screen and session corresponding to the auxiliary screen according to the binding relationship between the main and auxiliary screens carried when the main screen joins the conference, and realize the successful joining of the auxiliary screen.

In the foregoing embodiments, the binding relationship between the main and auxiliary screens is preset in the conference server as an example, and the binding relationship may also be carried in a message sent from the main screen to the conference server. As in the next embodiment.

Fig. 4 is a schematic flow diagram of the method in the fourth embodiment of the present invention. In this embodiment, the telepresence terminal dials the conference access number to join the conference, and the message sent by the main screen to the conference server carries the binding relationship between the main screen and the auxiliary screen as an example. Referring to Figure 4, this embodiment includes:

Step 41: The main screen sends a request message for joining the conference to the conference server, and the request message for joining the conference includes the conference access number, the main screen number, and the binding relationship between the main screen and the auxiliary screen.

For example, the request message to join a meeting is:

SIP INVITE(SDP offer 1)

Request-URI=meeting access number, From=main screen number

TelePresence-URI: <main screen number>; position=main

TelePresence-URI: <left screen number>; position=left; index=l

TelePresence-URI: <right screen number>; position=right; index=1

Step 42: The conference server obtains the binding relationship between the main and auxiliary screens from the request message for joining the conference, and sends a message for applying for resources to the MRFC/MRFP according to the binding relationship between the main and auxiliary screens. The information of each screen is carried in the message.

For example, the conference server sends the following message to MRFC/MRFP:

SIP INVITE(SDP offer 1)

Request-URI: sip:msml-video-conf=<conference ID><MRFC IP addr>:<port>

From: <Conference Server>

TelePresence-URI: <main screen number>; position=main

TelePresence-URI: <left screen number>; position=left; index=1

TelePresence-URI: <right screen number>; position=right; index=1

Step 43: MRFC/MRFP returns a response message to the conference server.

Step 44: The conference server returns a response message to the main screen.

For example, return a 200 INVITE (SDP answer 1) message.

Step 45: The main screen sends a confirmation message, such as an ACK message, to the conference server.

Step 46: The conference server sends an acknowledgment message, such as an ACK message, to the MRFC/MRFP.

For details of steps 43-46, refer to steps 23-26.

At this point, the successful joining of the main screen is completed, and then the process of joining the conference on the auxiliary screen can be shown in Figure 3.

In this embodiment, by establishing a session for each screen, there is no need to use a private protocol to negotiate multiple sub-sessions in an established session, which can improve the scope of application; and, in this embodiment, by establishing a session for each screen, Different screens can be distinguished according to the parameters in the session, and each screen can be controlled to solve the problem of not being able to distinguish each screen. In addition, this embodiment does not need to preset the binding relationship between the primary and secondary screens in the conference server, which can reduce the burden of the conference server.

During the telepresence conference, the conference chairman can invite the telepresence terminal to participate in the conference through the terminal conference control, Web Portal conference control, or IVR Portal conference control, Video Portal conference control.

FIG. 5 is a schematic flowchart of a method according to a fifth embodiment of the present invention. In this embodiment, the conference server invites a main screen to join a conference as an example. Referring to Figure 5, this embodiment includes:

Step 51: The conference server sends a message for inviting to join the conference to the main screen.

For example, the message to invite a meeting is:

SIP INVITE (no SDP)

Request-URI = main screen number

From=<meeting access number>

Step 52: The main screen returns a provisional response message to the conference server.

For example, the provisional response message is 100Trying or 180Ringing.

Step 53: The main screen answers automatically or manually. Step 54: The main screen sends a response message to the conference server, and the response message carries the binding relationship of the main and auxiliary screens.

For example, the reply message is:

200INVITE(SDP offer 1)

TelePresence-URI: <main screen number>; position=main

TelePresence-URI: <left screen number>; position=left; index=1

TelePresence-URI: <right screen number>; position=right; index=1

Step 55: The conference server obtains the binding relationship between the main and auxiliary screens from the response message, and sends a message for applying for resources to the MRFC/MRFP according to the binding relationship between the main and auxiliary screens. The message for applying for resources carries each screen information.

For example, the conference server sends the following message to MRFC/MRFP:

SIP INVITE(SDP offer 1)

Request-URI: sip:msml-video-conf=<conference ID><MRFC IP addr>:<port>

From: <Conference Server>

TelePresence-URI: <main screen number>; position=main

TelePresence-URI: <left screen number>; position=left; index=1

TelePresence-URI: <right screen number>; position=right; index=1

It can be understood that, in steps 54-55, the main screen sends the binding relationship between the main and auxiliary screens to the conference server, and similar to the second embodiment, the binding relationship between the main and auxiliary screens can be preset in the conference server, so that the main screen is sending to the conference server. The message sent by the server does not need to carry the binding relationship between the primary and secondary screens.

Step 56: MRFC/MRFP sends a response message to the conference server.

For example, the message is 200OK(SDP answer1).

Step 57: The conference server sends an acknowledgment message, such as an ACK message, to the MRFC/MRFP.

Step 58: The conference server sends a confirmation message, such as ACK (SDP answer 1), to the main screen.

So far, the initial SDP media negotiation between the main screen and MRFC/MRFP has been completed.

Refer to Figure 3 for the subsequent process of inviting the left auxiliary screen and the right auxiliary screen.

In this embodiment, by establishing a session for each screen, there is no need to use a private protocol to negotiate multiple sub-sessions in an established session, which can improve the scope of application; and, in this embodiment, by establishing a session for each screen, Different screens can be distinguished according to the parameters in the session, and each screen can be controlled to solve the problem of not being able to distinguish each screen. In addition, in this embodiment, the conference server actively requests the main screen to participate in the conference, which can improve pertinence.

The foregoing embodiment takes 3 screens as an example. Of course, the embodiment of the present invention is not limited to 3 screens, and the number of screens of the telepresence terminal may be greater than or equal to 2. For example, when the number of telepresence terminal screens is 2N+1 (N≥1), the SIP header field TelePresence-URI and its parameters are extended definitions of the standard SIP header field, specifically:

TelePresence-URI: <number>; position=<main/left/right>; index=<0～N>

Among them, <number> can be the number of the main screen, the number of the left auxiliary screen, and the number of the right auxiliary screen. When there are one or more left auxiliary screens, the parameter position is filled with left, and the parameter index is filled with parameters indicating which left auxiliary screen, for example, it includes 3 left auxiliary screens, and the index corresponding to the left auxiliary screen adjacent to the main screen is 1 , the index corresponding to the middle left auxiliary screen is 2, and the index corresponding to the leftmost left auxiliary screen is 3. Similarly, when there are one or more right auxiliary screens, the parameter position fills in right, and the parameter index fills in the parameter indicating which right auxiliary screen, for example, it includes 3 right auxiliary screens, among which the right auxiliary screen adjacent to the main screen corresponds to Index is 1, the index corresponding to the middle right auxiliary screen is 2, and the index corresponding to the other rightmost right auxiliary screen is 3. Of course, the present invention is not limited to odd-numbered screens. For even-numbered screens, one of them can be designated as the main screen, and different “indexes” can be used to distinguish other auxiliary screens.

Other processes for joining a conference with a telepresence terminal including multiple screens can be performed by referring to the process for three screens.

In addition, in the above embodiment, after each screen of the telepresence terminal successfully joins the conference, the MRS can control each screen according to the SIP session with the conference server.

FIG. 6 is a schematic flowchart of a method according to a sixth embodiment of the present invention. This embodiment takes controlling a single screen of a telepresence terminal as an example. Referring to Figure 6, this embodiment includes:

Step 61: The conference server establishes a SIP session with the MRFC/MRFP.

The specific establishment process can refer to the above-mentioned embodiment. In the above-mentioned embodiment, the SIP signaling interacted between the conference server and MRFC/MRFP, such as SIP INVITE, 200OK, etc., can constitute a SIP session (SIP dialog). Therefore, through the above process, a SIP session can be established corresponding to each screen.

Step 62: When a certain screen needs to be controlled, the conference server sends a message for control to MRFC/MRFP, the message for control carries the identifier of the screen to be controlled, and the identifier of the screen to be controlled carries In the toTag parameter of the SIP session.

For example, the telepresence terminal TP_1 has 3 screens, and the corresponding identifiers are: TP_1_M, TP_1_L, TP_1_R, and the telepresence terminal TP_2 has 3 screens, and the corresponding identifiers are: TP_2_M, TP_2_L, TP_2_R, you need to control TP_1_M to select TP_2_L . Then it may be that MRFC/MRFP sends a SIP INFO message to the conference server, and the toTag parameter of the SIP INFO message carries TP_1_M and TP_2_L.

Specifically, the MSML body sample carried by SIP INFO is as follows:

<modifyconference name="myconf">

<videolayout type="text/msml-basic-layout"id="vidmix1"optmode="assign">

<assignscreen sourcescreen="conn: TP_2_L_toTag" destinationscreen="conn: TP_1_M_toTag"/>

</videolayout>

</modifycconference>

Step 63: The MRFC/MRFP controls the screen to be controlled according to the control message.

For example, output the input media stream corresponding to the TP_2_L screen to the TP_1_M screen for playback.

In this embodiment, by establishing a SIP session corresponding to each screen, the parameters in the SIP session can be used to carry the identification of the screen to realize the control of each screen of the telepresence terminal.

Fig. 7 is a schematic diagram of the device structure of the seventh embodiment of the present invention, including an acquisition module 71 and an application resource module 72; the acquisition module 71 is used to acquire the binding relationship between the main and auxiliary screens of the telepresence conference terminal including at least two screens; the application resource Module 72 is used to send a message for applying for resources to the MRS according to the binding relationship between the main and auxiliary screens, and the message for applying for resources carries the information of each screen, so as to establish an application for each screen. Join a session of a telepresence meeting.

This embodiment may also include: a main screen adding module 73, configured to receive a successful response message returned by the MRS after allocating resources for each screen, and forward the successful response message to the main screen of the telepresence conference terminal; The confirmation message returned by the main screen is forwarded to the MRS, so as to realize the successful joining of the main screen.

This embodiment may also include an auxiliary screen joining module 74, configured to send a request message for inviting to join a meeting to the auxiliary screen bound to the main screen according to the binding relationship between the main and auxiliary screens; After the successful response message returned by the screen, send a request message for joining the conference to the MRS, and the request message for joining the conference carries the information of the auxiliary screen, so as to realize the successful joining of the auxiliary screen.

The acquisition module 71 may be specifically configured to receive a request message for joining a meeting sent by the main screen, and obtain the preset binding relationship between the main and auxiliary screens after receiving the request message for joining the meeting; or, receive the message sent by the main screen. A request message for joining a conference, where the request message for joining a conference carries a binding relationship between the primary and secondary screens.

Specifically, the obtaining module 71 is specifically configured to receive a request message for joining a meeting actively sent by the main screen; or, send a request message for inviting to join a meeting to the main screen, and receive the request message for inviting to join the meeting when the main screen receives the invitation message. A request message to join a conference sent after a request message to join a conference.

This embodiment may further include: a control module 75, configured to send a message for control to the MRS through a SIP session corresponding to each screen, the message for control carrying the identifier of the screen to be controlled, the The identifier of the screen to be controlled is carried in the toTag parameter of the SIP session, so that the MRS controls the screen to be controlled according to the message for control.

In this embodiment, by establishing a session for each screen separately, there is no need to use a private protocol to negotiate multiple sub-sessions in an established session, which can improve the scope of application; and, the embodiment of the present invention establishes a session for each screen separately , Different screens can be distinguished according to the parameters in the session, and each screen can be controlled to solve the problem of not being able to distinguish each screen.

It can be understood that related features in the above methods and devices can refer to each other. In addition, "first", "second" and so on in the above embodiments are used to distinguish each embodiment, and do not represent the advantages and disadvantages of each embodiment.

Those of ordinary skill in the art can understand that all or part of the steps to realize the above method embodiments can be completed by hardware related to program instructions, and the aforementioned programs can be stored in computer-readable storage media. When the program is executed, the execution includes The steps of the above-mentioned method embodiments; and the aforementioned storage medium includes: ROM, RAM, magnetic disk or optical disk and other various media that can store program codes.

Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: it can still be Modifications are made to the technical solutions described in the foregoing embodiments, or equivalent replacements are made to some of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the various embodiments of the present invention.

Claims (8)

1. a remote presentation conference method for processing business, is characterized in that, comprising:

Obtain the major-minor screen binding relationship of the remote presentation conference terminal that comprises at least two screens;

According to described major-minor screen binding relationship, send the message that is used for the application resource to Media Resource Server MRS, the described message information of carrying each screen for the application resource is so that corresponding each screen is set up respectively a session that is used for adding remote presentation conference;

Receive described MRS shielding for each the successful respond message of returning after Resources allocation, described successful respond message is transmitted to the main screen of described remote presentation conference terminal;

Receive the confirmation message that described main screen is returned, described acknowledge message is transmitted to described MRS, to realize the successful membership of main screen;

According to described major-minor screen binding relationship, send to the auxiliary screen with described main screen binding the request message that adds meeting for inviting;

After receiving the successful respond message that described auxiliary screen returns, send the request message that is used for adding meeting to MRS, described request message for adding meeting carries the information of auxiliary screen, to realize the successful membership of auxiliary screen.

2. method according to claim 1, is characterized in that, the described major-minor screen binding relationship that obtains the remote presentation conference terminal that comprises at least two screens comprises:

Receive the request message that is used for adding meeting that main screen sends, after receiving described request message be used to adding meeting, obtain default major-minor screen binding relationship;

Perhaps,

Receive the request message that is used for adding meeting that main screen sends, described request message for adding meeting carries major-minor screen binding relationship.

3. method according to claim 2, is characterized in that, the request message that is used for adding meeting that described reception main screen sends comprises:

Receive the request message that is used for adding meeting that main screen initiatively sends;

Perhaps,

Send the request message that adds meeting for inviting to main screen, receive described main screen and receiving the described request message that is used for adding meeting that sends after the request message of meeting that adds for invitation.

4. method according to claim 1, is characterized in that, described session is session establishment agreement SIP session, and described method also comprises:

By the SIP session corresponding with each screen, send the message that is used for control to MRS, described sign of carrying screen to be controlled for the message of controlling, the sign of described screen to be controlled is carried in the toTag parameter of SIP session, so that described MRS controls described screen to be controlled according to described message for controlling.

5. a remote presentation conference service processing equipment, is characterized in that, comprising:

Acquisition module is for the major-minor screen binding relationship that obtains the remote presentation conference terminal that comprises at least two screens;

The application resource module, be used for according to described major-minor screen binding relationship, the message that send to be used for the application resource to Media Resource Server MRS, described information of carrying each screen for the message of application resource is so that corresponding each screen is set up respectively a session that is used for adding remote presentation conference;

Main screen adds module, is used for receiving described MRS shielding for each the successful respond message of returning after Resources allocation, described successful respond message is transmitted to the main screen of described remote presentation conference terminal; Receive the confirmation message that described main screen is returned, described acknowledge message is transmitted to described MRS, to realize the successful membership of main screen;

Auxiliary screen adds module, is used for according to described major-minor screen binding relationship, sends to the auxiliary screen with described main screen binding to be used for inviting the request message that adds meeting; After receiving the successful respond message that described auxiliary screen returns, send the request message that is used for adding meeting to MRS, described request message for adding meeting carries the information of auxiliary screen, to realize the successful membership of auxiliary screen.

6. equipment according to claim 5, is characterized in that, described acquisition module specifically is used for receiving the request message that is used for adding meeting that main screen sends, and after receiving described request message be used to adding meeting, obtains default major-minor screen binding relationship; Perhaps, receive the request message that is used for adding meeting that main screen sends, described request message for adding meeting carries major-minor screen binding relationship.

7. equipment according to claim 6, is characterized in that, described acquisition module specifically is used for receiving the request message that is used for adding meeting that main screen initiatively sends; Perhaps, send the request message that adds meeting for inviting to main screen, receive described main screen and receiving the described request message that is used for adding meeting that sends after the request message of meeting that adds for invitation.

8. equipment according to claim 5, is characterized in that, also comprises:

Control module, be used for by the session establishment agreement SIP session corresponding with each screen, send the message that is used for control to MRS, described sign of carrying screen to be controlled for the message of controlling, the sign of described screen to be controlled is carried in the toTag parameter of SIP session, so that described MRS controls described screen to be controlled according to described message for controlling.

Images