CN101052045B - Synchronous source identifier distributing method - Google Patents
Synchronous source identifier distributing method Download PDFInfo
- Publication number
- CN101052045B CN101052045B CN200710103056XA CN200710103056A CN101052045B CN 101052045 B CN101052045 B CN 101052045B CN 200710103056X A CN200710103056X A CN 200710103056XA CN 200710103056 A CN200710103056 A CN 200710103056A CN 101052045 B CN101052045 B CN 101052045B
- Authority
- CN
- China
- Prior art keywords
- session
- user
- main control
- control server
- source identifier
- 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.)
- Expired - Fee Related
Links
Images
Landscapes
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The method comprises: 202) a first user sends a session initial protocol inviting request to its home server to request to participate a established session; 204) in case of not being the main controlling server, the home server of the first user replays the session initial protocol invention request to the main control server; 206) in case of needing to expanding the session initial protocol, the main control server allocates synchronous source identifier for the first user; 208) the main control server compares the synchronous source identifier allocated for the first user with the synchronous source identifiers from other sending ends in order to decide if they are the same; if yes, the main control server sends a confirmation message containing the synchronous identifier to the first user; if not, the main control server re-executes the step 208.
Description
Technical field
The present invention relates to communication and internet arena, relate in particular to a kind of synchronous source identifier (synchronization source identifier abbreviates SSRC as) distribution method.
Background technology
IP Multimedia System (IP multimedia subsystem, abbreviate IMS as) at first at third generation partner program (3rd generation partnership project, abbreviate 3GPP as) the R5 version in be suggested, its purpose is to define a cover based on the Internet engineering work group (internet engineering task force, abbreviate IETF as) the session control ability, irrelevant with access network, can use packet-switched domain (packet switch with the multimedia carrying, abbreviate the PS territory as), and support the complete solution of Internet protocol (Internetprotocol abbreviates IP as) multimedia application.
The IMS territory is in particular real-time and non real-time user, and multimedia service is designed end to end.IMS passes through such as session negotiation and management, service quality (quality of service, abbreviate QoS as) and a series of key mechanisms of mobile management etc. provide real-time multimedia service end to end (for example for the user, the voice and video phone of increment), non real-time user can also be provided, and multimedia service is (for example end to end, chat and instant message), multi-user service (for example, multimedia conferencing and chatroom), user side to the server end business (for example, strong professional (PUSH business) and PTT (push-to-talk overcellular the abbreviates PoC as) business of accusing of promoting).
Session initiation protocol (Session Initiation Protocol abbreviates SIP as) is the application layer protocol that is used to set up change and stops Multimedia session or calling.Session Initiation Protocol can be used for initiation session, also can be used to invite the member to add the session of otherwise having set up.
RTP (Real-time Transport Protocol abbreviates RTP as) is a kind of host-host protocol that is used on the Internet at multimedia data stream.It is a kind of RTP that end-to-end transmission service is provided, be used for being supported in transmitting real-time data in single goal broadcasting and the service of multiple target radio network, the transmission of real time data is then monitored by RTCP Real-time Transport Control Protocol (Real-time Transport Control Protocol abbreviates RTCP as) and controls.Simultaneously, RTP be defined in one to one or the transmission situation of one-to-many under work, its objective is provides the time and realizes that stream synchronously, usually use User Datagram Protoco (UDP) (userdatagram protocol, abbreviate UDP as) transmit data, but also can wait on other agreement and work in transmission control protocol (transmission control protocol abbreviates TCP as) or asynchronous transfer mode (asynchronous transfer mode abbreviates ATM as).
To use two ports when application program begins a RTP session: give RTP for one, another gives RTCP.RTP itself can not provide reliable transfer mechanism for the packet that transmits in order, and flow control or congested control are not provided yet, and it relies on RTCP that these services are provided.During the RTP session, each participant periodically sends the RTCP bag.Contain the quantity of data packets that has sent, the statistics of losing such as quantity of data packets in the RTCP bag, therefore, server can utilize these information dynamically to change transmission rate, even changes PT Payload Type.RTP and RTCP are used, and can make the efficiency of transmission optimization with effective feedback and minimum expense, thereby be particularly suitable for transmitting online real time data.
The message format of RTP as shown in Figure 1.Wherein, the SSRC identifier is 32 bit identifiers of the original transmitting terminal of RTP message, is used for the value of decision message sequence number and timestamp.The SSRC identifier produces at random, and has overall uniqueness in certain specific RTP session.Because this identifier produces at random, so might can select identical SSRC identifier by several transmitting terminals, if a plurality of transmitting terminal begins to send data simultaneously, the probability that then this conflict produces can be very high.Dynamically calculate the transmission interval of RTCP packet in the RTP session according to group size, otherwise can cause network congestion.In order to estimate group size, each transmitting terminal all will be intercepted multicastapackets and be calculated the number that adds the member, and this just needs to guarantee the uniqueness of each member SSRC.
Therefore, also do not have a kind of SSRC identifier collisions of can avoiding in RTP, occurring at present, that is, can guarantee the scheme of the uniqueness of SSRC identifier.
Summary of the invention
Consider the problems referred to above that exist in the correlation technique and make the present invention, for this reason, main purpose of the present invention is to provide a kind of synchronous source identifier distributing method.
This method comprises: step S202, and first user sends session initiation protocol to its dependent server and invites request, adds the session of having set up with request; Step S204 is not that dependent server sends to the main control server of session with the request of inviting of session initiation protocol under the situation of main control server of session at first user's dependent server; Step S206, main control server judges whether needs expansion session initiation protocol according to the particular value in the specific fields in the Session Description Protocol in the message body in the session initiation protocol invitation request, under the situation of needs expansion session initiation protocol, main control server is that first user distributes synchronous source identifier; Step S208, whether the synchronous source identifier of other transmitting terminal in the synchronous source identifier that main control server will distribute for first user and the session is compared, be unique to judge synchronous source identifier; In judged result is under the situation that is, main control server sends the response message that carries described synchronous source identifier to first user; And judged result for situation not under, main control server re-executes step S208.
Wherein, between step S202 and step S204, further comprise following processing: judge whether dependent server is the main control server of session.
Particularly, be that dependent server is the main control server of session under the situation of the session of being set up by first user in session, and handle and proceed to step S206; Not that dependent server is not the main control server of session under the situation of the session of being set up by first user in session, and handle and proceed to step S204 that wherein, in this case, the dependent server of setting up the user of session is a main control server.
In addition, in step S206, be under the situation of RTP/AVP at particular value, judging needs the expansion session initiation protocol.
In addition, after step S208, this method further comprises following processing: first user resolves response message, obtains synchronous source identifier; And first the user construct the RTP packet, synchronous source identifier is inserted the respective field of RTP packet head and sends the transmission of beginning multi-medium data.
By technical scheme of the present invention, avoided the collision problem of SSRC identifier in the RTP session, reduced producing the probability in loop, thereby increased the accuracy of group size estimation.
Description of drawings
Accompanying drawing described herein is used to provide further understanding of the present invention, constitutes the application's a part, and illustrative examples of the present invention and explanation thereof are used to explain the present invention, do not constitute improper qualification of the present invention.In the accompanying drawings:
Fig. 1 is the schematic diagram that illustrates according to the RTP message format of correlation technique;
Fig. 2 is the flow chart that illustrates according to the synchronous source identifier distributing method of the embodiment of the invention; And
Fig. 3 is the signaling process figure that illustrates according to the synchronous source identifier distributing method example of the embodiment of the invention;
Fig. 4 is the detailed process flow chart that illustrates according to the synchronous source identifier distributing method example of the embodiment of the invention.
Embodiment
At first need to prove, according to the associated description among the RFC3550, all is to adopt Message Digest 55 (message-digest algorithm version 5 abbreviates MD5 as) to produce by each transmitting terminal about the distribution of synchronous source identifier (SSRC).In the following technical scheme of the present invention that provides, still adopt the MD5 algorithm to produce the SSRC identifier, but be not to produce by each terminal but in whole real-time transport protocol (rtp) conversation procedure, carry out global assignment by the expansion Session Initiation Protocol by a particular server.
Describe embodiments of the invention below with reference to accompanying drawings in detail.
In embodiments of the present invention, the method that provides a kind of synchronous source identifier to distribute; Fig. 2 is the flow chart that this method is shown.
With reference to Fig. 2, this method comprises:
Step S202, first user (for example, user A) sends session initiation protocol to its dependent server (for example, dependent server A) and invites (SIP INVITE) request, adds the session of having set up with request;
Step S204 is not that dependent server sends to the main control server of session with the request of inviting of session initiation protocol under the situation of main control server of session at first user's dependent server;
Step S206, under the situation of needs expansion session initiation protocol, main control server is that first user distributes synchronous source identifier (SSRC);
Step S208, whether the synchronous source identifier of other transmitting terminal in the synchronous source identifier that main control server will distribute for first user and the session is compared, be unique to judge synchronous source identifier; Particularly, be under the situation that is in judged result, main control server sends the response message (step S210) that carries described synchronous source identifier to first user; And judged result for situation not under, main control server re-executes step S208.
Wherein, between step S202 and step S204, further comprise following processing: judge whether dependent server is the main control server of session.
Particularly, be that dependent server is the main control server of session under the situation of the session of being set up by first user in session, and handle and proceed to step S206; Not that dependent server is not the main control server of session under the situation of the session of being set up by first user in session, and handle and proceed to step S204 that wherein, the dependent server of setting up the user of session is a main control server.
In addition, in step S206, main control server according to the particular value in the specific fields in the Session Description Protocol in the message body in the session initiation protocol invitation request (for example, among the field m＜transport value) judge whether to need the expansion session initiation protocol, wherein, at particular value is under the situation of RTP/AVP, and judging needs the expansion session initiation protocol.
In addition, this method further comprises following processing: first user resolves response message, obtains synchronous source identifier; And first the user construct the RTP packet, synchronous source identifier is inserted the respective field of RTP packet head and sends the transmission of beginning multi-medium data.
Below will describe the method for distributing, but the invention is not restricted to this with the example that is applied as of chat group session among the PoC according to the synchronous source identifier of the embodiment of the invention.Wherein, Fig. 3 shows the signaling process of the processing of this example, and Fig. 4 shows the detailed process flow process of this example.
The signaling process figure of the processing example that a user joins in the chat group to be carried out particularly, has been shown among Fig. 3.As shown in Figure 3, its detailed process is as follows:
UE A sends to auxiliary PoC A with SIP INVITE request, and chat group PoC server authenticates the user, if the user then joins this user in the chat group by authentication, and will represent that the successful message SIP 200OK of adding returns to UE A;
Next, after UE A receives 200OK, media device is carried out initialization, and SIP ACK request is sent to auxiliary PoC, auxiliary PoC is transmitted to the master control PoC with chat group with this request, just can carry out the transmission of media data packet (RTP message) afterwards, and user's adding finishes.
In PoC used, what the logic function of finishing according to (from the whole process that is established to termination of session) server in the RTP conversation procedure judged that server takes on was main control server or secondary server.Particularly, under the situation of group session, initiate the server that the user invites is taken on the function of main control server, and under the situation of chat group and predefine group session, preserve the server of group definition sign and take on main control server.
At first, user B sets up the session of a PoC chat group, and at this moment, the subordinate service server B of user B can be a master server;
Then, user A (that is, first user) sends SIP INVITE and asks to dependent server A, is responsible for this SIP INVITE request is transmitted to the main control server (perhaps, dependent server B is main control server) of this session by the dependent server B of user B.
Said process can be understood with reference to the step S402 to S410 among Fig. 4.
Wherein, the SIP INVITE request of user A transmission is:
INVITE?sip:A@ims.zhongxing.chinamobile.com SIP/2.0
Via：.............
From：<sip:A@ims.zhongxing.chinamobile.com>；tag＝789
To： <sip:groupB@ims.zhongxing.chinamobile.com>
Call-ID：....
m＝audio...RTP/AVP
Main control server is according to Session Description Protocol (the session description protocol in the message body in the SIP INVITE request, abbreviate SDP as) among the field m＜transport value need to judge whether the expansion Session Initiation Protocol, if being worth, this is then to need to expand Session Initiation Protocol by RTP/AVP; Otherwise, then do not need to expand.(corresponding to the step S412 among Fig. 4)
Expand Session Initiation Protocol if desired, then distribute a SSRC for user A, and it is compared with the SSRC identifier of other transmitting terminal in this session, judge whether to exist conflict by main control server.If there is conflict, then redistribute a SSRC, in whole session, have overall uniqueness until SSRC.(corresponding to the step S414 among Fig. 4)
Main control server is preserved the SSRC identifier that produces, and is associated with user's unique identification (for example, SIP URL), so that provide foundation for the judgement of other user SSRC identifier uniqueness.(corresponding to the step S416 among Fig. 4)
Main control server sends the response of 200OK to the SIP INVITE request of user A dependent server, and will be attached to extended field SSRC in the response message body of 200OK, and 200OK is transmitted to user A by the dependent server of user A for the SSRC identifier that user A produces.(corresponding to step S418 among Fig. 4 and S420)
Wherein, the 200OK response is as follows:
SIP/2.0?2000K
Via：.............
From：<sip:A@ims.zhongxing.chinamobile.com>；tag＝789
To：<sip:groupB@ims.zhongxing.chinamobile.com>；tag＝123；
Contact：......
Call-ID：......
SSRC:...... (32 random strings)
Then, user A resolves 200OK, takes out the SSRC identifier, structure RTP packet, and the head respective field of the SSRC identifier that obtains being inserted the RTP packet also sends, and begins to carry out the multi-medium data transmission.
By produced the mode of SSRC identifier by main control server, comparing produces this identifier at transmitting terminal in PoC, can carry out the control of the overall situation in the whole session process to the generation of SSRC, can effectively avoid the conflict and the loop problem that exist among the RTP.(corresponding to the step S422 among Fig. 4)
In sum,, avoided the collision problem of SSRC sign in the RTP session, reduced producing the probability in loop, thereby increased the accuracy of group size estimation by technical scheme of the present invention.
The above is the preferred embodiments of the present invention only, is not limited to the present invention, and for a person skilled in the art, the present invention can have various changes and variation.Within the spirit and principles in the present invention all, any modification of being done, be equal to replacement, improvement etc., all should be included within protection scope of the present invention.
Claims (5)
1. a synchronous source identifier distributing method is characterized in that, comprising:
Step S202, first user sends session initiation protocol to its dependent server and invites request, adds the session of having set up with request;
Step S204 is not that described dependent server sends to the main control server of described session with the request of inviting of described session initiation protocol under the situation of main control server of described session at described first user's dependent server;
Step S206, described main control server invites in the message body in the request particular value in the specific fields in the Session Description Protocol to judge whether that needs expand described session initiation protocol according to described session initiation protocol, under the situation of needs expansion session initiation protocol, described main control server is that described first user distributes synchronous source identifier;
Step S208, whether the synchronous source identifier of other transmitting terminal in the synchronous source identifier that described main control server will distribute for described first user and the described session is compared, be unique to judge described synchronous source identifier;
In judged result is under the situation that is, described main control server sends the response message that carries described synchronous source identifier to described first user;
In judged result is that described main control server re-executes described step S208 under the situation not;
Wherein, between described step S202 and described step S204, further comprise following processing: judge whether described dependent server is the main control server of described session;
Be that described dependent server is the main control server of described session under the situation of the session of being set up by described first user in described session, and handle and proceed to step S206.
2. synchronous source identifier distributing method according to claim 1, it is characterized in that, not that described dependent server is not the main control server of described session under the situation of the session of being set up by described first user in described session, and handle and proceed to described step S204.
3. synchronous source identifier distributing method according to claim 2 is characterized in that, the dependent server of setting up the user of described session is described main control server.
4. synchronous source identifier distributing method according to claim 1 is characterized in that, is under the situation of RTP/AVP at described particular value, and judging needs the described session initiation protocol of expansion.
5. synchronous source identifier distributing method according to claim 1 is characterized in that, after described step S208, further comprises following processing:
Described first user resolves described response message, obtains described synchronous source identifier; And
Described first user constructs the RTP packet, described synchronous source identifier is inserted the respective field of described RTP packet head and send the transmission of beginning multi-medium data.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200710103056XA CN101052045B (en) | 2007-05-16 | 2007-05-16 | Synchronous source identifier distributing method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200710103056XA CN101052045B (en) | 2007-05-16 | 2007-05-16 | Synchronous source identifier distributing method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101052045A CN101052045A (en) | 2007-10-10 |
| CN101052045B true CN101052045B (en) | 2010-06-02 |
Family
ID=38783234
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN200710103056XA Expired - Fee Related CN101052045B (en) | 2007-05-16 | 2007-05-16 | Synchronous source identifier distributing method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101052045B (en) |
Families Citing this family (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101588356B (en) * | 2008-05-19 | 2012-01-25 | 鸿富锦精密工业（深圳）有限公司 | Network equipment and method for detecting voice packet by same |
| CN101938397A (en) * | 2009-06-29 | 2011-01-05 | 华为技术有限公司 | Method for associating RTP (Real-time Transport Protocol) packets in SIP (Session Initiation Protocol) session, device and system thereof |
| EP2782309B1 (en) * | 2012-11-13 | 2016-05-04 | Huawei Technologies Co., Ltd. | Bidirectional forwarding detection (bfd) session negotiation method, device and system |
| CN104601497B (en) * | 2013-10-31 | 2019-01-18 | 华为技术有限公司 | 1588V2 message transmitting method and device based on wan interface |
| CN104660546B (en) * | 2013-11-18 | 2018-01-19 | 北京信威通信技术股份有限公司 | A kind of method of the transmitting-receiving RTP bags based on SSRC |
| KR102188537B1 (en) * | 2019-08-14 | 2020-12-08 | 라인플러스 주식회사 | Method and system for group call using unicast and multicast |
| CN112423245B (en) * | 2019-08-23 | 2021-10-22 | 成都鼎桥通信技术有限公司 | Data transmission method and device, server and terminal equipment |
| EP4140120A4 (en) * | 2020-05-20 | 2023-08-02 | Samsung Electronics Co., Ltd. | Method and apparatus for communication in communication system supporting multi-talker mission critical push-to-talk (mcptt) |
| CN115174539B (en) * | 2022-06-28 | 2023-06-02 | 上海网达软件股份有限公司 | Security video streaming transmission method, system, equipment and storage medium |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2006091000A1 (en) * | 2005-02-23 | 2006-08-31 | Samsung Electronics Co., Ltd. | Method and system for granting floor in push-to-talk over cellular network |
| WO2007045274A1 (en) * | 2005-10-17 | 2007-04-26 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and apparatus for handling redirection of sip messages |
| EP1781049A1 (en) * | 2005-10-28 | 2007-05-02 | Telefonaktiebolaget LM Ericsson (publ) | Methods and apparatus for push to talk type service |
-
2007
- 2007-05-16 CN CN200710103056XA patent/CN101052045B/en not_active Expired - Fee Related
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2006091000A1 (en) * | 2005-02-23 | 2006-08-31 | Samsung Electronics Co., Ltd. | Method and system for granting floor in push-to-talk over cellular network |
| WO2007045274A1 (en) * | 2005-10-17 | 2007-04-26 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and apparatus for handling redirection of sip messages |
| EP1781049A1 (en) * | 2005-10-28 | 2007-05-02 | Telefonaktiebolaget LM Ericsson (publ) | Methods and apparatus for push to talk type service |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101052045A (en) | 2007-10-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101052045B (en) | Synchronous source identifier distributing method | |
| JP5033173B2 (en) | Inter-domain group communication | |
| US20080155055A1 (en) | Method and system for sending media stream-based charging request in a multiparty session | |
| KR101214326B1 (en) | Method and arrangement for providing different services in a multimedia communication system | |
| CN101218777A (en) | Method and system for multicasting data in a communication network | |
| JP4989657B2 (en) | Talk Rights Management System and Method for Multimedia Communication Service in PoC System, and Terminal Device | |
| US9264467B2 (en) | Method, user equipment, and system for opening an ad-hoc PoC session in a PoC system | |
| US20060229094A1 (en) | User equipment, method and system for simultaneous session control | |
| US8160627B2 (en) | System for establishing and managing multimedia PoC session for performing multimedia call service, method thereof and user equipment therefor | |
| US7573837B1 (en) | Establishment of multicast Push-to-X over Cellular (PoC) communication | |
| WO2006101353A1 (en) | Method and system for establishing ad-hoc session in push to talk over cellular network | |
| CN101015167A (en) | Sharing ongoing data session | |
| EP2211587B1 (en) | Method, system, server and client for transmitting media burst data | |
| US20080281621A1 (en) | Peer-to-peer communication charging method, communication system and charging device | |
| CN102160353A (en) | Method and apparatus for establishing a poc session | |
| CN101453402A (en) | Method, system and equipment for media flow control | |
| US20110295954A1 (en) | Method and apparatus for requesting media replication in a collaborative communication session, and method and apparatus for assigning a communication medium for a collaborative communication session | |
| CN104135468A (en) | IMS (IP Multimedia Subsystem) session negotiation control system, device and method supporting multipath relay transmission | |
| US20080288643A1 (en) | Session Initiation Protocol Signalling | |
| KR101011891B1 (en) | Method and apparatus for determining pt server having controlling function | |
| CN100384296C (en) | Internet protocol multimedia subsystem charging mark distributing method | |
| CN101568068A (en) | Broadcasting/multicasting method and broadcasting/multicasting equipment | |
| Cruz et al. | Push-to-Talk in IMS mobile environment | |
| RU2755529C1 (en) | Method for establishing session of group packet voice communication over data transmission networks | |
| KR100748990B1 (en) | Ssrc conflict control method in poc 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 | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20100602 Termination date: 20170516 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |