1、 ETSI TS 101 884-1 V4.1.1 (2003-08)Technical Specification Telecommunications and Internet ProtocolHarmonization Over Networks (TIPHON) Release 4;Technology Mapping;Part 1: Implementation of TIPHON architecture using SIPETSI ETSI TS 101 884-1 V4.1.1 (2003-08) 2 Reference RTS/TIPHON-03018-1R4 Keyword
2、s architecture, IP, SIP, telephony, VoIP ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice Indivi
3、dual copies of the present document can be downloaded from: http:/www.etsi.org The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document
4、 Format (PDF). In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the curr
5、ent status of this and other ETSI documents is available at http:/portal.etsi.org/tb/status/status.asp If you find errors in the present document, send your comment to: editoretsi.org Copyright Notification No part may be reproduced except as authorized by written permission. The copyright and the f
6、oregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2003. All rights reserved. DECTTM, PLUGTESTSTM and UMTSTM are Trade Marks of ETSI registered for the benefit of its Members. TIPHONTMand the TIPHON logo are Trade Marks currently being registere
7、d by ETSI for the benefit of its Members. 3GPPTM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. ETSI ETSI TS 101 884-1 V4.1.1 (2003-08) 3 Contents Intellectual Property Rights5 Foreword.5 1 Scope 6 2 References 7 3 Definitions and abbreviat
8、ions.8 3.1 Definitions8 3.2 Abbreviations .8 4 SIP environment overview .8 4.1 Introduction 8 4.2 SIP protocol9 4.2.1 SIP signalling, methods and responses .9 4.2.1.1 SIP signalling 9 4.2.1.2 Methods and responses .9 4.2.2 SIP protocol components 10 4.3 SDP 10 4.4 HTTP/1.110 5 Implementation of TIPH
9、ON functional architecture using SIP .10 5.1 Introduction 10 5.2 SIP functional architecture .10 6 Registration service12 6.1 Introduction 12 6.2 Registration functional entities mapping14 6.3 Registration Messages Mapping.14 6.4 Registration information flow Mapping.15 6.4.1 Relationship ra (RFE1/R
10、FE2).15 6.4.2 Relationship rb (RFE2/RFE3).17 6.4.3 Relationship rc (RFE1/RFE3).18 6.4.4 Relationship rd (RFE2/RFE4).18 6.5 Registration action Mapping 19 6.6 Conclusion19 7 Simple call application .20 7.1 Introduction 20 7.2 Simple call functional entities mapping .24 7.3 Simple call messages mappin
11、g.24 7.4 Simple call information flow mapping.25 7.4.1 Relationship ra (CallingUser/CFE1).26 7.4.2 Relationship rf, ri (CFE3/CFE6/CFE9) 28 7.4.3 Relationship rl (CFE11/CalledUser).30 7.5 Simple call functional entity actions mapping32 7.6 Timers 33 7.7 Conclusion34 8 Media Control service 34 8.1 Int
12、roduction 34 8.2 Media Control functional entities mapping 34 8.3 Media Control information flow Mapping .34 8.3.1 Relationship ra (CCA/MFE1).35 8.4 Conclusion36 9 Transport 36 9.1 Introduction 36 10 Supplementary services36 ETSI ETSI TS 101 884-1 V4.1.1 (2003-08) 4 11 Control of end-to-end Quality
13、of Service.36 11.1 Introduction 36 11.2 Control of end-to-end Quality of Service functional entities mapping.37 11.3 Control of end-to-end Quality of Service flows mapping 37 11.4 Control of end-to-end Quality of Service information flow data mapping.39 11.4.1 Relationship ra (CallingUser/QFE1).39 1
14、1.4.2 Relationship rc, rd (QFE2/QFE8/QFE3) 40 11.4.3 Relationship rf (QFE4/CalledUser) 42 11.4.4 Relationship rg (QFE1/QFE5) 42 11.5 Control of end-to-end Quality of Service functional entity actions mapping.43 11.6 Timers 43 11.7 Conclusion44 12 Security service 44 Annex A (informative): Bibliograp
15、hy.48 History 49 ETSI ETSI TS 101 884-1 V4.1.1 (2003-08) 5 Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members,
16、and can be found in ETSI SR 000 314: “Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (http:/webapp.etsi.org/IPR/home.asp).
17、 Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the presen
18、t document. Foreword This Technical Specification (TS) has been produced by ETSI Project Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON). The present document is part 1 of a multi-part deliverable covering implementation, of TIPHON architecture using the SIP protocol, a
19、s identified below: Part 1: “Implementation of TIPHON architecture using SIP“; Part 2: “Implementation Profile for SIP“. ETSI ETSI TS 101 884-1 V4.1.1 (2003-08) 6 1 Scope The present document describes how the SIP protocol 9 completed with correlated protocols like SDP 11, HTTP 12 can be a candidate
20、 for TIPHON release 4 according to guidelines given in TS 101 315 Release 4 (see bibliography) and TS 101 315 Release 3 2. The SIP profile is derived from the examination of the following TIPHON Release 4 documents: the TIPHON baseline architecture described in TS 101 314 1; the capabilities service
21、 required by TS 101 878 (see bibliography); the Meta-protocol as defined in multi part document TS 101 882-1 5, TS 101 882-2 6, TS 101 882-3 (see bibliography), TS 101 882-4 (see bibliography) and TS 101 882-5 7; the end-to-end Quality of Service defined in TS 102 024-3 3; the Security service defin
22、ed in TS 102 165-1 4. The mapping of Meta-Protocol to SIP is limited to the following parts, while other parts are not available yet like supplementary services: Registration Meta-Protocol 6; Simple Call Meta-Protocol (TS 101 882-3 - see bibliography); Media Control Meta-Protocol (TS 101 882-4 - see
23、 bibliography); the end-to-end Quality of Service defined in TS 102 024-3 3; IETF RFC 3261: “SIP: Session Initiation Protocol“ 9; IETF RFC 2327: “SDP: Session Description Protocol“ 11; IETF RFC 2616: “Hypertext Transfer Protocol - HTTP/1.1“ 12; IETF RFC 2617: “HTTP Authentication: Basic and Digest A
24、uthentication“ (see bibliography); Furthermore the following documents have been consulted for information: TS 124 229: “IP Multimedia Call Control Protocol based on SIP and SDP“ (see bibliograpy); TS 124 228: “Signalling flows for the IP multimedia call control based on SIP and SDP“ 8. ETSI ETSI TS
25、 101 884-1 V4.1.1 (2003-08) 7 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For
26、a specific reference, subsequent revisions do not apply. For a non-specific reference, the latest version applies. Referenced documents which are not found to be publicly available in the expected location might be found at http:/docbox.etsi.org/Reference. 1 ETSI TS 101 314: “Telecommunications and
27、Internet Protocol Harmonization Over Networks (TIPHON) Release 4; Abstract Architecture and Reference Points Definition; Network Architecture and Reference Points“. 2 ETSI TS 101 315: “Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 3; Functional entities, infor
28、mation flow and reference point definitions; Guidelines for application of TIPHON functional architecture to inter-domain services“. 3 ETSI TS 102 024-3: “Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 4; End-to-end Quality of Service in TIPHON Systems; Part 3:
29、 Signalling and Control of end-to-end Quality of Service“. 4 ETSI TS 102 165-1: “Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 4; Protocol Framework Definition; Methods and Protocols for Security; Part 1: Threat Analysis“. 5 ETSI TS 101 882-1: “Telecommunicati
30、ons and Internet Protocol Harmonization Over Networks (TIPHON) Release 4; Protocol Framework Definition; Part 1: Meta-protocol design rules, development method, and mapping guideline“. 6 ETSI TS 101 882-2: “Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 4; Prot
31、ocol Framework Definition; Part 2: Registration and Service Attachment service meta-protocol definition.“. 7 ETSI TS 101 882-5: “Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 4; Protocol Framework Definition; Part 5: Transport control service meta-protocol def
32、inition;“. 8 ETSI TS 124 228: “Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Signalling flows for the IP multimedia call control based on SIP and SDP; Stage 3 (3GPP TS 24.228 version 5.3.0 Release 5)“. 9 IETF RFC 3261: “SIP: Session Initiat
33、ion Protocol“. 10 IETF RFC 3264: “An Offer/Answer Model with Session Description Protocol (SDP)“. 11 IETF RFC 2327: “SDP: Session Description Protocol“. 12 IETF RFC 2616: “Hypertext Transfer Protocol - HTTP/1.1“. 13 IETF RFC 2617: “HTTP Authentication: Basic and Digest Access Authentication“. 14 IET
34、F RFC 1890: “RTP Profile for Audio and Video Conferences with Minimal Control“. 15 IETF RFC 1889: “RTP: A Transport Protocol for Real-Time Applications“. 16 IETF RFC 2806: “URLs for Telephone Calls“. 17 IETF RFC 2748: “The COPS (Common Open Policy Service) Protocol“. ETSI ETSI TS 101 884-1 V4.1.1 (2
35、003-08) 8 18 IETF RFC 2326: “Real Time Streaming Protocol (RTSP)“. 19 IETF RFC 3525: “Gateway Control Protocol Version 1“. 20 IETF RFC 3265: “Session Initiation Protocol (SIP)-Specific Event Notification“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the
36、terms and definitions given in TS 101 314 1 and TS 101 878 (see bibliography) apply. 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: B2BUA Back-to-Back User Agent BC Bearer Control CC Call Control COPS Common Open Policy Service FG Functional GroupICF I
37、nter-Connect Function IP Internet ProtocolMC Media Control NFG Network Functional Group PCM Pulse Code Modulation PDP Policy Decision Point PSTN Public Switched Telephone Network QoS Quality of Service RPC Remote Procedure Call SAP Service Access Point SC Service Control SDP Session Description Prot
38、ocol SpoA Service point of Attachment TE Terminal EquipmentUA User Agent UAC User Agent Client UAS User Agent Server URI Uniform Resource Identifier 4 SIP environment overview 4.1 Introduction The purpose of the present document is not to describe how to implement SIP protocol but how TIPHON protoco
39、l can be represented in a SIP environment. For example parameter mandatory in SIP but without equivalence in TIPHON information elements are not documented. Mandatory behaviours in SIP that do not correspond to any TIPHON behaviours are not documented either. The aim is to identify gap in TIPHON to
40、SIP direction between both protocols. Informative suggestions to fill those gaps could be given in conclusion. ETSI ETSI TS 101 884-1 V4.1.1 (2003-08) 9 4.2 SIP protocol SIP is a relatively new technology (1995) developed for remote control, establishment and tear-down of multimedia sessions. The or
41、igins of SIP are in the academic and IETF community and assumed in its first incarnation a public internet although with the interest shown by 3GPP the application to a managed network that uses IP has become ascendant. SIP is based upon the communication model of HTTP and therefore is broadly viewe
42、d as a request-response protocol. In relation to other well known protocols SIP has close cousins in Remote Procedure Call (RPC) and in the ITU-T ROSE protocol. According to RFC 3261 9, SIP is an application-layer-control protocol to manage multimedia session. But, “SIP is not a vertically integrate
43、d communications system“, and will need other IETF protocols to build a complete multimedia architecture (e.g.: RTP RFC 1889 15, RTSP RFC 2326 18, MEGACO RFC 3525 19, SDP RFC 2327 11). The choice of the protocol for the session description is opened in SIP and appears in SIP only as a parameter valu
44、e (Content-Type). The media type descriptions that can be included in the body of a SIP message are Internet Media Types as in HTPP/1.1. However, in this profile only Session Description Protocol (SDP) defined in RFC 2327 11 has been considered. SIP reuses also the authentication mechanism defined i
45、n HTTP. The SIP technology has been considered through the following standards: “SIP: Session Initiation Protocol“ - RFC 3261 9. “SDP: Session Description Protocol“ - RFC 2327 11. “RTP Profile for Audio and Video Conferences with Minimal Control“ - RFC 1890 14. “Hypertext Transfer Protocol - HTTP/1.
46、1“ - RFC 2616 12. SIP does not define services. Rather, SIP provides primitives that can be used to implement different services. For example, SIP can locate a user and deliver an opaque object to his current location. If this primitive is used to deliver a session description written in SDP, for in
47、stance, the endpoints can agree on the parameters of a session. If the same primitive is used to deliver a photo of the caller as well as the session description, a “caller ID“ service can be easily implemented. As this example shows, a single primitive is typically used to provide several different
48、 services. SIP does not offer conference control services such as floor control or voting and does not prescribe how a conference is to be managed. SIP can be used to initiate a session that uses some other conference control protocol. Since SIP messages and the sessions they establish can pass thro
49、ugh entirely different networks, SIP cannot, and does not, provide any kind of network resource reservation capabilities. The nature of the services provided make security particularly important. To that end, SIP provides a suite of security services, which include denial-of-service prevention, authentication (both user to user and proxy to user), integrity protection, and encryption and privacy services. SIP works with both IPv4 and IPv6. 4.
