CN101848098A - Multiparty conference communication method based on SIP protocol - Google Patents
Multiparty conference communication method based on SIP protocol Download PDFInfo
- Publication number
- CN101848098A CN101848098A CN200910301078A CN200910301078A CN101848098A CN 101848098 A CN101848098 A CN 101848098A CN 200910301078 A CN200910301078 A CN 200910301078A CN 200910301078 A CN200910301078 A CN 200910301078A CN 101848098 A CN101848098 A CN 101848098A
- Authority
- CN
- China
- Prior art keywords
- conference
- server
- message
- party conference
- party
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Landscapes
- Telephonic Communication Services (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention relates to a multiparty communication technology in the network communication field, and discloses a multiparty communication method based on SIP protocol. The technical scheme is that: a, a terminal requests an IM server to establish an IM multiparty conference; b, a terminal participating in the IM multiparty conference invites other terminals to join in the conference; c, a terminal participating in the IM multiparty conference drives another terminal participating in the IM multiparty conference out of the IM multiparty conference; d, the terminals participating in the IM multiparty conference send an instant message to and receive an instant message from each other; e, the terminals participating in the IM multiparty conference do not comprise an initiator, and exit the conference; f, when the conference initiator exits the conference or all participants of the conference exit the conference, the IM multiparty conference is ended; and g, before the IM multiparty conference is ended, all users participating in the conference are informed of a minutes link address. The invention is applied to a multiparty conference system.
Description
Technical field
The present invention relates to the multi-party communication technology of network communication field, be particularly related to SIP (Session InitiationProtocol, Session initiation Protocol) visioning procedure of IM (Instant Message, instant message) Multi-Party Conference and user adding is withdrawed from flow process with the user in the system.
Background technology
In the IM Multi-Party Conference, carry out the transmission and the reception of instant message between message sender and the meeting participant by communication network.In message interaction process, a side who sends message is called message sender, and the participant of reception message is called message receiver.The transmit leg of message can be a terminal, and WEB user also can be other application servers.In the IM multiparty conference system, also comprise control of authority, meeting summary is stored and is obtained functions such as user management.
Along with the demand of market to presence (presenting) and IM increases day by day, various implementations have appearred.But the major part on the early stage market realizes generally all adopting proprietary protocol, and is incompatible each other, presents also imperfect that function realizes.IETF has set up IMPP (Instant Message and Presence Protocol) working group in 1998, to design safety and to present flexibly/instant message protocol.IMPP has defined necessary agreement and data format, is used for making up an instant messages system with reception, issue capability.Various draft agreement or suggestion have been proposed now, as: SIMPLE, XMPP, PRIM etc.Wherein, most representative is preceding two standards, and present IM/presence also mainly is divided into two big camp: SIP/SIMPLE and JABBER/XMPP.
The SIMPLE standard proposed by IETF SIMPLE working group is formal in February calendar year 2001, full name is SIP InstantMessaging and Presence Leveraging Extensions (at instant message and the conversation initialized protocol that presents professional utilization expansion), is the expansion of Session Initiation Protocol at IM/presence.
SIMPLE is a comparatively perfect standard of formulating so far, and many companies all are devoted to realize this agreement in their instant communicating system.Can send and receive by the MESSAGE method (RFC3428, Session Initiation Protocol (SIP) Extension for Instant Messaging) of SIP as common point-to-point instant message.
But in the SIMPLE standard, the IM Multi-Party Conference is not too much described and methods analyst.Flow process to the IM Multi-Party Conference in " draft-ietf-simple-chat " has been carried out some descriptions, but mainly is to use for reference the audio conferencing visioning procedure, and not to establishment, the user of Multi-Party Conference add, the user withdraws from, User Status etc. retrains.The transmission of messages passage that standard is used mainly uses MSRP, does not consider to use the MESSAGE method.The MESSAGE method is the standard of present terminal equipment in use, needs to consider compatible.
Application number is 200610037285.1 Chinese patent application, and the extended message head comes the recipient's of conference setup message information in Session Initiation Protocol bunch.This method can only be used for the mass-sending of message.Privately owned chat is not well supported for conference users.
Summary of the invention
Technical problem to be solved by this invention is exactly the above-mentioned shortcoming at prior art, and a kind of multiparty conference communication method based on Session Initiation Protocol is provided, to the establishment of Multi-Party Conference, user add, the user withdraws from, User Status etc. is carried out standard.
The present invention solve the technical problem, and the technical scheme of employing is, based on the multiparty conference communication method of Session Initiation Protocol, comprises terminal and IM server, it is characterized in that, may further comprise the steps:
A, terminal request IM server are created the IM Multi-Party Conference;
The terminal of b, participation IM Multi-Party Conference invites other-end to add meeting;
Another terminal that the terminal of c, participation IM Multi-Party Conference will participate in the IM Multi-Party Conference evicts out of the IM Multi-Party Conference;
The terminal of d, participation IM Multi-Party Conference sends and receives instant message mutually;
The terminal of e, participation IM Multi-Party Conference does not comprise the promoter, withdraws from meeting;
F, when the meeting promoter withdraws from that all participants withdraw from meeting in meeting or the meeting, the IM Multi-Party Conference finishes;
Before g, IM Multi-Party Conference finish, announce the minutes chained address to all users that participated in this meeting.
Step a specifically may further comprise the steps:
A1, terminal send the INVITE request of creating the IM Multi-Party Conference to the IM server;
A2, IM server create Multi-Party Conference, and be that this IM Multi-Party Conference distributes Conference ID number, write down founder's information and meeting relevant information;
The terminal that a3, IM server create the IM Multi-Party Conference to request sends response message, if create the meeting success, makes sound so and answers the Conference ID number that carries described IM Multi-Party Conference in the message;
A4, terminal send SUBSCRIBE message to the IM server, subscribe to IM Multi-Party Conference state information;
A5, IM server send NOTIFY to terminal, notice terminal IM Multi-Party Conference state information.
Step b specifically may further comprise the steps:
B1, invited party send REFER message to the IM server;
B2, IM server send the NOTIFY notice to invited party and invite progress;
B3, IM server send INVITE according to the REFER message of receiving to the side of being invited and set up session;
B4, IM server send the NOTIFY notice to invited party and invite successfully;
B5, IM server announce the information of member in the meeting to described IM Multi-Party Conference participant;
B6, the side's of being invited predetermined conference state information;
B7, IM server are to being invited square tube to accuse conference status information.
Step c specifically may further comprise the steps:
C1, expulsion direction IM server send REFER message, and be with " method=bye " parameter in the Refer-To of described REFER message header fields;
C2, IM server are to being subjected to send NOTIFY notice expulsion progress by the side;
C3, IM server are subjected to by the side to being subjected to send the expulsion of BYE message by the side;
C4, IM server are expelled successfully to being subjected to send the NOTIFY notice by the side;
C5, IM server are announced conference status information to IM Multi-Party Conference participant.
Steps d specifically may further comprise the steps:
D1, described instant message transmit leg transfer immediate news to described IM server by MESSAGE message;
D2, described IM server transfer immediate news by MESSAGE message to the described IM Multi-Party Conference participant except that the instant message sender.
Step e specifically may further comprise the steps:
E1, described IM Multi-Party Conference participant do not comprise the meeting promoter, send the BYE message request to described IM server and withdraw from described IM Multi-Party Conference;
E2, described IM server are announced described IM Multi-Party Conference state information to the described request for conference person of withdrawing from;
E3, described IM server are announced described IM Multi-Party Conference state information to described all participants of IM Multi-Party Conference.
Step f specifically may further comprise the steps:
F1, described IM Multi-Party Conference promoter send the BYE message request to described IM server and withdraw from meeting;
F2, described IM server send NOTIFY announcement conference status information to described IM Multi-Party Conference promoter;
F3, described IM server send the BYE request to all participants of described IM Multi-Party Conference, make described IM Multi-Party Conference participant withdraw from meeting, ask successfully after, announce conference status information by the transmission NOTIFY to it.
Step g specifically may further comprise the steps:
Before g1, described IM Multi-Party Conference finish, send MESSAGE message announcement minutes chained addresses to all terminals that once participated in this meeting;
G2, described IM Multi-Party Conference finish;
G3, described MESSAGE message receiver are visited described IM server by the web address, download described IM Multi-Party Conference record;
G4, described IM Multi-Party Conference are recorded on the described IM server and keep a period of time, out-of-date automatic deletion.
The invention has the beneficial effects as follows, standard the mechanism of IM Multi-Party Conference communication, adapt to the existing general accepted standard of terminal, be greatly replenishing to conventional voice communications.Can be in each big industry, enterprises is disposed corresponding IM system, improves office efficiency.
Description of drawings
Fig. 1 is infrastructure network figure of the present invention;
Fig. 2 is the data flow diagram that the present invention creates the instant message Multi-Party Conference;
Fig. 3 invites the user to add the data flowchart of IM Multi-Party Conference;
Fig. 4 is the data flowchart that a conference users is evicted another conference users from meeting;
Fig. 5 is the data flowchart that sends message in the IM Multi-Party Conference;
Fig. 6 is the data flowchart that IM Multi-Party Conference participant withdraws from the IM Multi-Party Conference;
Fig. 7 is the data flowchart that IM Multi-Party Conference promoter withdraws from the IM Multi-Party Conference;
Fig. 8 is the data flowchart that the IM server sent minutes before the IM Multi-Party Conference finished to all users that once participated in this meeting.
Embodiment
Below in conjunction with drawings and Examples, describe technical scheme of the present invention in detail.
With reference to figure 1, illustrate implement the present invention institute based on communication system, also can be regarded as enforcement environment of the present invention.As shown in the figure, described communication system comprises communication network, IM server and terminal 1～n, and n is the integer value more than or equal to 2.Communication system shown in Figure 1 operates based on Session Initiation Protocol.
(receive and send the SIP message capability even terminal 1～n) possesses, the communication network among the figure is based on Internet, and the IM server is supported the management of instant message Multi-Party Conference, is the convergent point of instant message for n among a figure terminal.
Embodiment
With reference to figure 2, when terminal 1 needs to use IM Multi-Party Conference function of the present invention, at first on the IM server, create an IM Multi-Party Conference.The data flow of creating the IM Multi-Party Conference is used the Session Initiation Protocol of standard, and Fig. 2 then illustrates the data flow of this process:
The first step, establish the founder of terminal 1, send INVITE to the IM server as the IM Multi-Party Conference.This message Request-Line field represents it is a request message of creating the instant message Multi-Party Conference, and wherein imc-Factory is system's agreement, is used for request message and can be routed to the IM server.It is instant message that the message parameter indicates medium type.Described INVITE information is as follows:
INVITE?sip:imc-Factory@conf.example.com?SIP/2.0
......
m＝message?10600?UDP?520
After second step, IM server received the INVITE request of creating the IM Multi-Party Conference, in meeting of the inner establishment of server, with the sign of terminal 1, name, address information joined in the instant message meeting, and terminal 1 are set to the founder of meeting.Then, the IM server is according to self rule, and the IM Multi-Party Conference distributes a unique Conference ID number for this reason.The IM server is after creating the success of IM Multi-Party Conference, reply 200 OK response messages to conference creation person's (being terminal 1), and in its Contact header field, carry the Conference ID number (as imConfId) and the parameter isfocus (showing that this is a meeting URI) of the IM Multi-Party Conference of this time creating.Described 200 OK informations are as follows:
SIP/2.0?200?OK
......
Contact：<sip:imConfId@conf.example.com>；isfocus
......
After the 3rd step, terminal 1 are created the success of IM Multi-Party Conference, send SUBSCRIBE message to the IM server, IM Multi-Party Conference state information pulls subscription.
The 4th step, IM server are replied 200 OK response messages to described terminal, agree the request of terminal 1.
The 5th step, IM server send NOTIFY to terminal 1, the state information of announcement IM Multi-Party Conference.
What deserves to be explained is that terminal 1 can be created a plurality of IM Multi-Party Conferences, the participant of each IM Multi-Party Conference does not limit.That is to say that each terminal can be participated in a plurality of IM Multi-Party Conferences.
With reference to figure 3, when terminal 1 invites terminal 2 to add the IM Multi-Party Conference:
The first step, terminal 1 send REFER message to the IM server;
Second step, IM server response REFER message, and send NOTIFY, notice is invited progress;
The 3rd step, IM server are according to the REFER message of receiving, success makes a call to terminal 2;
The 4th step, IM server notification terminal 1 access success;
The 5th step, IM server notification terminal 1 conference status information (referring to that here terminal 2 adds meeting);
The 6th step, terminal 2 predetermined conference state informations;
The 7th step, IM server are to terminal 2 announcement conference status information.
With reference to figure 4, when terminal 1 wants to evict terminal 2 from meeting:
The first step, terminal 1 send REFER message to the IM server, and add URI parameter " method=BYE " and evict the IM Multi-Party Conference to show the user with the Refer-To indication in the Refer-To header field;
Second step, IM server response REFER message, and return NOTIFY, the progress of evicting the user with notice from;
The 3rd step, IM server send BYE message according to the REFER message of receiving to terminal 2, evict terminal 2 from meeting;
The 4th step, IM server send NOTIFY to terminal 2, and notice terminal 2 withdraws from meeting;
The 5th step, IM server notification terminal 1 are evicted terminal 2 from the meeting success;
The 6th step, IM server all terminal announcement conference status information in the IM Multi-Party Conference.
With reference to figure 5, in the IM Multi-Party Conference, carry out the transmitting-receiving of instant message:
The first step, terminal 1 transfer immediate news to the IM server;
Second step, the IM server other-end except that terminal 1 in the IM Multi-Party Conference is transmitted instant message.
With reference to figure 6, IM Multi-Party Conference participant (non-meeting promoter) withdraws from meeting:
The first step, establish IM Multi-Party Conference participant terminal 3 and send the BYE message request to the IM server and withdraw from meeting;
Second step, IM server are to terminal 3 announcement IM Multi-Party Conference state informations;
The 3rd step, IM server are announced IM Multi-Party Conference state information to all participants of IM Multi-Party Conference.
With reference to figure 7, when IM Multi-Party Conference promoter wants to withdraw from meeting:
The first step, terminal 1 are the promoter of IM Multi-Party Conference, when it withdraws from the IM Multi-Party Conference, send the BYE message request to the IM server and withdraw from meeting;
Second step, IM server send the conference status notice message to terminal 1;
The 3rd step, IM server send the BYE request to all participants of IM Multi-Party Conference, so that described participant withdraws from meeting, and to its announcement conference status information.
With reference to figure 8, the IM Multi-Party Conference is announced the minutes chained address to all users that participated in this meeting before finishing:
The first step, IM server send the chained address of minutes by MESSAGE message to the promoter of IM Multi-Party Conference and all participants once; Afterwards, IM server deletion IM Multi-Party Conference.
Second step, MESSAGE message receiver are downloaded the minutes of IM Multi-Party Conference by web address visit IM server.Download in the IM Multi-Party Conference recording process, the IM server authenticates terminal, has only the participant once of IM Multi-Party Conference just can download minutes.
Claims (12)
1. based on the multiparty conference communication method of Session Initiation Protocol, comprise terminal and IM server, it is characterized in that, may further comprise the steps:
A, terminal request IM server are created the IM Multi-Party Conference;
The terminal of b, participation IM Multi-Party Conference invites other-end to add meeting;
Another terminal that the terminal of c, participation IM Multi-Party Conference will participate in the IM Multi-Party Conference evicts out of the IM Multi-Party Conference;
The terminal of d, participation IM Multi-Party Conference sends and receives instant message mutually;
The terminal of e, participation IM Multi-Party Conference withdraws from meeting;
F, when the meeting promoter withdraws from that all participants withdraw from meeting in meeting or the meeting, the IM Multi-Party Conference finishes;
Before g, IM Multi-Party Conference finish, announce the minutes chained address to all users that participated in this meeting.
2. the multiparty conference communication method based on Session Initiation Protocol according to claim 1 is characterized in that step a specifically may further comprise the steps:
A1, terminal send the INVITE request of creating the IM Multi-Party Conference to the IM server;
A2, IM server create Multi-Party Conference, and be that this IM Multi-Party Conference distributes Conference ID number, write down founder's information and meeting relevant information;
The terminal that a3, IM server create the IM Multi-Party Conference to request sends response message, if create the meeting success, makes sound so and answers the Conference ID number that carries described IM Multi-Party Conference in the message;
A4, terminal send SUBSCRIBE message to the IM server, subscribe to IM Multi-Party Conference state information;
A5, IM server send NOTIFY to terminal, notice terminal IM Multi-Party Conference state information.
3. the multiparty conference communication method based on Session Initiation Protocol according to claim 2 is characterized in that, the request message of INVITE described in the step a1 comprises the type of IM Multi-Party Conference, and described type is decided to be the instant message type approximately.
4. the multiparty conference communication method based on Session Initiation Protocol according to claim 2, it is characterized in that, the information of founder described in the step a2 comprises founder's sign, name, contact address, and described meeting relevant information comprises Session Topic, meeting URI information.
5. the multiparty conference communication method based on Session Initiation Protocol according to claim 2 is characterized in that, indicates IM Multi-Party Conference that Conference ID number is this time created for described terminal in the information of conference status described in the step a4.
6. the multiparty conference communication method based on Session Initiation Protocol according to claim 2, it is characterized in that, the Multi-Party Conference of IM described in step a5 state information is represented with the xml structure, specifically comprises: meeting URI, Conference ID number, participant terminal quantity, participant terminal URI.
7. the multiparty conference communication method based on Session Initiation Protocol according to claim 1 is characterized in that step b specifically may further comprise the steps:
B1, invited party send REFER message to the IM server;
B2, IM server send the NOTIFY notice to invited party and invite progress;
B3, IM server send INVITE according to the REFER message of receiving to the side of being invited and set up session;
B4, IM server send the NOTIFY notice to invited party and invite successfully;
B5, IM server announce the information of member in the meeting to described IM Multi-Party Conference participant;
B6, the side's of being invited predetermined conference state information;
B7, IM server are to being invited square tube to accuse conference status information.
8. the multiparty conference communication method based on Session Initiation Protocol according to claim 1 is characterized in that step c specifically may further comprise the steps:
C1, expulsion direction IM server send REFER message, and be with " method=bye " parameter in the Refer-To of described REFER message header fields;
C2, IM server are to being subjected to send NOTIFY notice expulsion progress by the side;
C3, IM server are subjected to by the side to being subjected to send the expulsion of BYE message by the side;
C4, IM server are expelled successfully to being subjected to send the NOTIFY notice by the side;
C5, IM server are announced conference status information to IM Multi-Party Conference participant.
9. the multiparty conference communication method based on Session Initiation Protocol according to claim 1 is characterized in that steps d specifically may further comprise the steps:
D1, described instant message transmit leg transfer immediate news to described IM server by MESSAGE message;
D2, described IM server transfer immediate news by MESSAGE message to the described IM Multi-Party Conference participant except that the instant message sender.
10. the multiparty conference communication method based on Session Initiation Protocol according to claim 1 is characterized in that step e specifically may further comprise the steps:
E1, described IM Multi-Party Conference participant do not comprise the meeting promoter, send the BYE message request to described IM server and withdraw from described IM Multi-Party Conference;
E2, described IM server are announced described IM Multi-Party Conference state information to the described request for conference person of withdrawing from;
E3, described IM server are announced described IM Multi-Party Conference state information to described all participants of IM Multi-Party Conference.
11. the multiparty conference communication method based on Session Initiation Protocol according to claim 1 is characterized in that step f specifically may further comprise the steps:
F1, described IM Multi-Party Conference promoter send the BYE message request to described IM server and withdraw from meeting;
F2, described IM server send NOTIFY announcement conference status information to described IM Multi-Party Conference promoter;
F3, described IM server send the BYE request to all participants of described IM Multi-Party Conference, make described IM Multi-Party Conference participant withdraw from meeting, ask successfully after, announce conference status information by the transmission NOTIFY to it.
12. the multiparty conference communication method based on Session Initiation Protocol according to claim 1 is characterized in that step g specifically may further comprise the steps:
Before g1, described IM Multi-Party Conference finish, send MESSAGE message announcement minutes chained addresses to all terminals that once participated in this meeting;
G2, described IM Multi-Party Conference finish;
G3, described MESSAGE message receiver are visited described IM server by the web address, download described IM Multi-Party Conference record;
G4, described IM Multi-Party Conference are recorded on the described IM server and keep a period of time, out-of-date automatic deletion.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200910301078A CN101848098A (en) | 2009-03-24 | 2009-03-24 | Multiparty conference communication method based on SIP protocol |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200910301078A CN101848098A (en) | 2009-03-24 | 2009-03-24 | Multiparty conference communication method based on SIP protocol |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN101848098A true CN101848098A (en) | 2010-09-29 |
Family
ID=42772564
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN200910301078A Pending CN101848098A (en) | 2009-03-24 | 2009-03-24 | Multiparty conference communication method based on SIP protocol |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101848098A (en) |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104301127A (en) * | 2014-09-29 | 2015-01-21 | 大唐移动通信设备有限公司 | Conference control method and equipment |
| CN104580247A (en) * | 2015-01-27 | 2015-04-29 | 宇龙计算机通信科技(深圳)有限公司 | Information synchronization method and information synchronization device based on IMS multi-party calls |
| CN107295203A (en) * | 2016-04-01 | 2017-10-24 | 中国移动通信有限公司研究院 | Method for message transmission and device in a kind of MPTY meeting |
| CN109150856A (en) * | 2018-08-01 | 2019-01-04 | 携程旅游信息技术（上海）有限公司 | Realize method, system, electronic equipment and the storage medium of videoconference |
| CN109257318A (en) * | 2017-07-12 | 2019-01-22 | 中国移动通信集团广东有限公司 | A kind of group call method for building up and platform |
| CN112152907A (en) * | 2015-02-16 | 2020-12-29 | 钉钉控股（开曼）有限公司 | Communication method and communication system |
-
2009
- 2009-03-24 CN CN200910301078A patent/CN101848098A/en active Pending
Cited By (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104301127A (en) * | 2014-09-29 | 2015-01-21 | 大唐移动通信设备有限公司 | Conference control method and equipment |
| CN104301127B (en) * | 2014-09-29 | 2017-11-14 | 大唐移动通信设备有限公司 | A kind of method and apparatus of Conference control |
| CN104580247A (en) * | 2015-01-27 | 2015-04-29 | 宇龙计算机通信科技(深圳)有限公司 | Information synchronization method and information synchronization device based on IMS multi-party calls |
| WO2016119300A1 (en) * | 2015-01-27 | 2016-08-04 | 宇龙计算机通信科技(深圳)有限公司 | Information synchronization method and information synchronization device based on ims multi-party call, and terminal |
| CN112152907A (en) * | 2015-02-16 | 2020-12-29 | 钉钉控股（开曼）有限公司 | Communication method and communication system |
| CN107295203A (en) * | 2016-04-01 | 2017-10-24 | 中国移动通信有限公司研究院 | Method for message transmission and device in a kind of MPTY meeting |
| CN107295203B (en) * | 2016-04-01 | 2019-08-02 | 中国移动通信有限公司研究院 | Method for message transmission and device in a kind of multi-party call meeting |
| CN109257318A (en) * | 2017-07-12 | 2019-01-22 | 中国移动通信集团广东有限公司 | A kind of group call method for building up and platform |
| CN109257318B (en) * | 2017-07-12 | 2021-06-11 | 中国移动通信集团广东有限公司 | Group call establishing method and platform |
| CN109150856A (en) * | 2018-08-01 | 2019-01-04 | 携程旅游信息技术（上海）有限公司 | Realize method, system, electronic equipment and the storage medium of videoconference |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101243657B (en) | Method and system for managing chat service | |
| US9065919B2 (en) | Mixed media conferencing | |
| CN101336542B (en) | Automatic voice conference actions driven by potential conferee presence | |
| CN101237336B (en) | Multi-party communication method, system and method for distribution event status | |
| JP5531044B2 (en) | System and method for initiating a conference call | |
| CN101257395B (en) | System and method for supporting multimedia conference booking | |
| CN101232465B (en) | Method for transmitting document in conference system, document transmitting system and conference server | |
| US8245043B2 (en) | Audio start service for Ad-hoc meetings | |
| US9426108B2 (en) | Method for storing conversation upon user's request in CPM system, and system thereof | |
| CN100563259C (en) | A kind of method and system of in JICQ, carrying out multi-conference | |
| US7526281B2 (en) | Method and device for establishing a conference call between a plurality of user terminals of a communication network | |
| US20060190543A1 (en) | Systems and methods for advanced communications and control | |
| US20070033249A1 (en) | Multimodal conversation | |
| CN101848098A (en) | Multiparty conference communication method based on SIP protocol | |
| CN105472310A (en) | Video conference realization method and system thereof based on SIP protocol | |
| CN102388631A (en) | System and method for establishing session upon satisfaction of particular conditions | |
| CN201146535Y (en) | System for implementing multiple-human conversation in an instant communication tool | |
| CN101267325A (en) | Method, conference server and terminal for originating and joining in conference session | |
| KR20050114624A (en) | Method for managing selective presence for an instantaneous messaging service in a telecommunication network such as an internet network | |
| Kausar et al. | Architecture of conference control functions | |
| US20130335510A1 (en) | System for exchanging ptt messages for brief multi video conferences | |
| CN102546994B (en) | Method and system for realizing information interaction of multimedia conference members | |
| Chen et al. | DigiParty-a decentralized multi-party video conferencing system | |
| KR100609688B1 (en) | System for providing multi-media conference call sevice and method of the same | |
| KR20060018990A (en) | The method for making multi-party communication channel using sip service |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C12 | Rejection of a patent application after its publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20100929 |