1、ETSI TS 102 108 V4.1.1 (2002-06) Technical Specificafion Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 4; H.248/MEGACO Profile for TIPHON reference point 13; Interconnect Function (ICF) control over reference point 13 2 ETSI TS 102 108 V4.1.1 (2002-06) Referen
2、ce DTS/TIPHON-O3028R4 Keywords architecture, configuration, H.248, internet, IP, megaco, network, protocol, telephony, VolP ETSI 650 Route des Lucioles F-O6921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 O0 Fax: +33 4 93 65 47 16 Siret No 348 623 562 00017 - NAF 742 C Association but non lu
3、cratif enregistre la Sous-prfecture de Grasse (06) No 7803/88 Important notice Individual copies of the present document can be downloaded from: http:lwmv.etsi .arq The present document may be made available in more than one electronic version or in print. In any case of existing or perceived differ
4、ence in contents between such versions, the reference version is the Portable Document 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 tha
5、t the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at ha p:/pa rta I. etsi I a rgltbistat uslstatus .as p If you find errors in the present document, send your comment to: Cori vriaht Notifica tion No part ma
6、y be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media. O European Telecommunications Standards Institute 2002. All rights reserved. DECTTM, PLUGTESTSTMand UMTSTMare Trade Marks of ETSI registered for the benefit of
7、 its Members. TIPHONTM and the TIPHON logo are Trade Marks currently being registered 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 3 ETSI TS 102 108 V4.1.1 (2002-06) Contents Intellectua
8、l Property Rights . .5 Foreword . 5 Introduction . .5 1 2 3 3.1 3.2 4 4.1 4.2 4.3 4.4 4.5 4.6 5 6 6.1 6.2 6.3 6.3.1 6.3.2 6.3.3 6.3.4 6.4 6.5 6.6 6.6.1 Scope 6 References . .7 Definitions and abbreviations .7 Definitions . 7 Abbreviations . . 8 Use ofthe H.248 ICF profile 9 Functionality supported b
9、y the Profile . 9 Service capabilities supported 9 General note on compliance . 9 Error handling 9 Security 10 Setting up of the controller-middlebox control interface . 10 Use of the profile for the establishment of transport flows 10 Scope ofthe H.248 ICF profile 8 Process used . 10 Packages suppo
10、rted . Required H,248/MEGACO messages and parameters . . Parameters . . 8 . . . . . . 6.6.1.1 QoS policing of inc . 6.6.2 QoS on outgoing flows . 6.6.2.1 TOS tagging of outg 6.6.2.2 6.7 coming flows . 7 Management operations . 14 Annex A (normative): Mapping with meta-protocol 15 A.l Code point mapp
11、ing . 15 A. 1.1 Primitive mappings . 15 A.1.2 Binary encoding . 16 A. 1.2.1 For an IP-based transport flow 16 A. 1.3 Text encoding . 16 A.2 Error reasons 17 Annex B (normative): Meta-protocol to SDP mapping 18 B. 1 Mappable fields 18 B.2 SpeciSling the OriginatorMpoA . 19 B.3 SpeciSling QoS mechanis
12、m specific values . 19 B.3.1 DiffServ Type of Service (TOS) value 19 A.1.3.1 For an IP-based transport flow ETSI 4 ETSI TS 102 108 V4.1.1 (2002-06) B.3.2 RSVP 19 B.4 Unmappable fields 20 Basic flow without address translation without source filtering 21 Flow with address translation without source f
13、iltering 28 Annex C (informative): C . 1 C.2 C.3 C.4 C.5 C.6 C.7 Annex D (informative): D . 1 Annex E (informative): TIPHON template usage scenarios 21 Basic scenario with address translation (the legacy mode) 24 Flow without address translation with source filtering 33 Flow with address translation
14、 with source filtering . 37 Explicit RTCP addresses with source filtering and address translation . 42 Signalling: example flow for a H323 RAS control pin-hole 49 Options on the basic scenarios 52 Transport activation option 52 History 56 Bibliography . 55 ETSI 5 ETSI TS 102 108 V4.1.1 (2002-06) Int
15、ellectual 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, and can be found in ETSI SR O00 314: “Intellectual Property Ri
16、ghts (7PRs); Essential, orpotentially Essential, IPRs notlJied to ETSI in respect ofETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (5). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out
17、by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR O00 3 14 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Foreword This Technical Specification (TS) has been produced by ETSI Project Telecom
18、munications and Internet Protocol Harmonization Over Networks (TIPHON). I n t rod uct ion The present document defines technology mappings of the meta-protocol to reference points in the transport plane. It specifies the technology mappings to reference point I3 as defined in TS 101 882 2. ETSI 6 ET
19、SI TS 102 108 V4.1.1 (2002-06) 1 Scope The present document describes a mapping of the meta-protocol for reference point 13, as described in annex D of TS 101 882 2, to the ITU-T Recommendation H.248 l/IETF MEGACO protocol, to produce an interoperable profile (subset) of H.248/MEGACO augmented by th
20、e TPC Extension package defined in TS 101 332 5. It may be used for the control of equipment within an IP network such as Firewalls, Address Translators, Middleboxes and also other network edge devices. Originatingi Terminating Terminal FG OnginatingiTerminating Network FG A k- Serving Home * Ingres
21、sEgress Core transport domain Terminal FG transport domain Intermediate Terminatingi Network FG Onginating Gateway FG T I . Originating Gatewav FG EgressiIngress transport domain Figure la: TIPHON architecture with reference point 13 highlighted ETSI 7 ETSI TS 102 108 V4.1.1 (2002-06) 2 Re fe re nce
22、s 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 andor edition number or version number) or non-specific. For a specific reference, subsequent revisions
23、 do not apply. For a non-specific reference, the latest version applies. il 21 ITU-T Recommendation H.248 (2000): “Gateway control protocol“. ETSI TS 101 882: “Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 3; Protocol Framework Definition; General (meta-protoc
24、ol)“. ETSI TS 101 3 14: “Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 3; Abstract Architecture and Reference Points Definition; Network Architecture and Reference Points“. 31 41 51 IETF RFC 2327 (April 1998): “SDP Session Description Protocol“. ETSI TS 101 33
25、2: “Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 4; Interface Protocol Requirements Definition; TIPHON Extended H.248MEGACO Package (EMP) Specification; ICF Control over Reference Point“. IETF RFC 2205: “Resource Reservation Protocol (RSVP) - Version 1 Functi
26、onal Specification“ ETSI TS 10 1 329-3 : “Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 3; End-to-end Quality of Service in TIPHON systems; Part 3: Signalling and control of end-to-end Quality of Service (QoS)“. 61 71 3 3.1 Definitions and abbreviations De fi
27、nit ions For the purposes of the present document, the following terms and definitions apply: charging: process of determining the amount of money a user shall pay for usage of a certain service flow: single data stream, identified by a set of characteristic values (source address, source port, dest
28、ination address, destination port, protocol number) functional entity: entity in a system that performs a specific set of functions functional group: collection of functional entities within a domain NOTE: In TIPHON systems functional groups are used to structure the necessary functionality to offer
29、 IP telephony services across domains. IP endpoint: device that originates or terminates the IP based part of a call NOTE: Endpoints include H.323 clients, and IP telephony gateways. IP network packet transport network comprising one or more transport domains each employing the IP protocol middlebox
30、: firewall or NAT device which is coupled to a MIDCOM server, which offers the firewall/NAT services to clients network telecommunications network that provides telecommunications services ETSI 8 ETSI TS 102 108 V4.1.1 (2002-06) protocol: set of semantics, syntax and procedures which govern the exch
31、ange of information across an interface Switched Circuit Network (SCN): telecommunications network, e.g. Public Switched Telephone Network (PSTN), Integrated Services Digital Network (ISDN), and General System for Mobile communications (GSM), that uses circuit-switched technologies for the support o
32、f voice calls NOTE: The SCN may be a public network or a private network. TIPHON compliant: entity that complies with the mandatory requirements identified in the TIPHON requirements documents together with compliance to the parts of the TIPHON specifications in which these requirements are embodied
33、 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: EMP GK ICF IP MC MB QOS RAS RSVP RTCP RTP SCN SDL TOS TRM Extended Megaco Package GateKeeper Interconnect Function Internet Protocol Media Control MiddleBox Quality of Service Registration Admission and S
34、tatus Resource reseVation Set-up Protocol RealTime Conferencing Protocol RealTime transfer Protocol Switched Circuit Networks Specification and Description Language Type Of Service Transport Resource Manager 4 Scope of the H.248 ICF profile The present document describes a profile of H.248 that mand
35、ates certain optional parts of the protocol and does not mandate certain other options. Here the H.248 protocol is used to convey only flow properties to edge devices (ICFs) in the transport plane. Used solely for this purpose, H.248/MEGACO, reduces to a small sub-set of the full protocol. ETSI 9 ET
36、SI TS 102 108 V4.1.1 (2002-06) 4.1 Use of the H.248 ICF profile Reference Point I3 NOTE: This profile of H.248/MEGACO is used to control Middlebox devices in the transport plane. For the purposes of the present document a Middlebox is defined as a physical implementation of an Interconnect Function
37、(ICF) TS 101 314 3 and TS 101 329-3 7. A controller is defined as an implementation of control functionality. The control relationship between a Middlebox and its controller is shown in figure 1 b. Figure 1 b: Entities involved in Control over the 13 Reference point 4.2 Fu nct ion al i ty su p porte
38、d by the Profi I e The I3 reference point controls the ICF functions in a transport domain and will be under the control of the operator or administrator of that domain. Instructions from the TRM (here the controller) to the ICF will relate to admission control in the case of firewalls, network addr
39、esses in the case of Address Translators or control signals for QoS mechanisms such as RSVP or DiffSDerv. 4.3 Service capa bi I i ties supported TIPHON Release 4 service capabilities supported by the profile are basic bearer and QoS bearer Set-up. 4.4 General note on compliance Any options in the H.
40、248 protocol not mentioned in the present document MAY be supported by the Middlebox or controller, however are outside the scope of the present document. 4.5 Error handling General use of the error codes can be found in clause A.2. If an H.248 information element is received (descriptor or paramete
41、r), which is not specified in this profile, the receiver shall ignore the information element and act as if the information element were not received. If an unknown H.248 command or an information element not specified in this profile is received, the receiver shall ignore the command and send an ap
42、propriate error (443 - unsupported or unknown command or 444 - unsupported or unknown descriptor, 445 - unsupported or unknown property, 446 - unsupported or unknown parameter). If an H.248 command with a mandatory information element missing is received, the receiver shall act as if the information
43、 element was received carrying the default values, or reject with the appropriate error message if there is no default value specified in the H.248 standard. ETSI 10 ETSI TS 102 108 V4.1.1 (2002-06) If an H.248 information element is received with syntactically invalid contents the receiver shall: i
44、f the information element is optional, ignore the information element; or if the information element is mandatory, act as if the information element was received correctly coded carrying the default values and reject/fail if there is no default value specified in the standard. If an H.248 informatio
45、n element is received with a value not allowed within the context of the present document, the receiver shall: if the information element is optional, pass on, but otherwise ignore the information element; or if the information element is mandatory reject/fail. NOTE: The security policy of an operat
46、ors network or the security policy implemented in a network element may override the error handling as described above. 4.6 Security Security issues associated with the use of this profile are outside the scope of the present document. It is intended that they will be included in future releases of
47、the present document. 5 Setting up of the controller-middlebox control i n t e rfa ce Clause 1 1 of ITU-T Recommendation H.248 i shall apply without restrictions. This may change in future releases of the present document. 6 Use of the profile for the establishment of transport flows The basic messa
48、ges of H.248 used in this profile are here defined as well as certain H.248 packages. This clause describes the messages used in the profile. 6.1 Process used This clause provides the mapping of the flows in TS 101 882 2 annex D, to H248 message flows. The parameter and error reason definitions in T
49、S 101 882 2 annex D are aligned to ensure interoperability of these values across the mappings of these reference points. In general each of the primitives defined on the T/I reference points in TS 101 882 2 each map to one or more commands in H.248. General note on source filtering used in the scenarios SDP (see RFC 2327 4) specifies in clause B.2.1 a means for speciSling unicast sessions. This provides the means to encode the originator MpoA. In clause B.2 it is shown how the recvonly and send only attribute are used for speciSling the sender side
