1、 ETSI TR 183 068 V3.1.1 (2009-08)Technical Report Telecommunications and Internet converged Services andProtocols for Advanced Networking (TISPAN);Guidelines on using Ia H.248 profile forcontrol of Border Gateway Functions (BGF);Border Gateway GuidelinesETSI ETSI TR 183 068 V3.1.1 (2009-08) 2Referen
2、ce DTR/TISPAN-03202-NGN-R3 Keywords gateway, H.248, SIP 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 Importan
3、t notice Individual 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 Po
4、rtable 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 that the document may be subject to revision or change of status. Informat
5、ion on the current 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, please send your comment to one of the following services: http:/portal.etsi.org/chaircor/ETSI_support.asp Copyright Notification No part
6、may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2009. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTM, TIPHONTM, the TIPHON logo and the ETSI logo are Trade
7、 Marks of ETSI registered 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. LTE is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP Organizational Partners. G
8、SM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TR 183 068 V3.1.1 (2009-08) 3Contents Intellectual Property Rights 6g3Foreword . 6g31 Scope 7g32 References 7g32.1 Normative references . 7g32.2 Informative references 8g33 Abbreviations . 9g34 Structure of th
9、is Technical Report 9g3Annex A: Illustration of Gate/Pinhole Concept. 10g3A.1 General . 10g3A.2 Relationships between gates and H.248 Streams . 10g3Annex B: Void 11g3Annex C: Void 12g3Annex D: Illustration of an IP processing model for an H.248 (IP, IP) Context . 13g3D.1 Example model . 13g3D.2 Aspe
10、cts of filter interaction 15g3D.2.1 Interaction between address latching and address policing 15g3Annex E: Guidelines for Ia-to-Gq mapping . 17g3E.1 Guidelines for Ia-to-Gq mapping with regards to session-independent procedures 17g3E.1.1 Introduction 17g3E.1.2 Mapping guidelines 17g3E.1.2.1 Session-
11、dependent procedures 17g3E.1.2.2 Session-independent procedures . 18g3E.2 Guidelines for Ia-to-Gq mapping with regards to bearer-specific events 18g3E.2.1 Introduction 18g3E.2.2 Mapping guidelines 19g3E.2.2.1 Guidelines for Specific Action AVPs 19g3E.2.2.2 Other AVPs . 19g3Annex F: Bandwidth Reserva
12、tion - Examples for Bandwidth Estimations . 20g3F.1 Introduction 20g3F.1.1 Bitrate B in general. 21g3F.1.1.1 Before service admission 21g3F.1.1.1a After service completion . 21g3F.1.1.2 Transport efficiency 21g3F.1.2 Some important RACS principles . 22g3F.1.2.1 Independence of layer 2 and layer 1 .
13、22g3F.1.2.2 Awareness of IP version . 22g3F.1.3 VPN Identifiers 22g3F.1.4 SDP “b=“ line semantic in H.248 Ia profile versions . 22g3F.1.5 Conclusion: ideal resource management model for resource “bitrate“ . 22g3F.2 Traffic aspects 23g3F.2.1 Quality of bitrate reservation 23g3F.3 Examples 23g3ETSI ET
14、SI TR 183 068 V3.1.1 (2009-08) 4F.3.1 Examples for media-aware streams 23g3F.3.1.1 Example for G.711 23g3F.3.2 Examples for media-agnostic streams 24g3Annex G: Illustration of BGF modes of operation 26g3G.1 Major SDP Information Elements for Media/Bearer/Resource Control in the BGF 26g3G.1.1 Example
15、 27g3G.2 BGF modes driven by particular SDP lines . 27g3G.2.1 SDP “c=“ line . 27g3G.2.2 SDP “m=“ line 28g3G.3 BGF modes driven by configuration management . 28g3G.3.1 Media-related modes 28g3G.3.2 Transport-related modes . 28g3Annex H: Illustration of NAPT modes of operation . 29g3H.1 NAPT types 29g
16、3H.1.1 Remote NA(P)T devices 29g3H.1.2 MG-local NA(P)T function 30g3H.2 NAPT-full modes . 30g3H.2.1 General case: non-symmetrical remote network addresses 30g3H.2.1.1 “Double“ NAPT mode without explicit Local Source settings . 30g3H.2.1.2 “Double“ NAPT mode with explicit Local Source settings 32g3H.
17、2.2 Special case: symmetrical remote network addresses 32g3H.2.2.1 “Double“ NAPT mode without explicit Local Source settings . 33g3H.2.2.2 “Double“ NAPT mode with explicit Local Source settings 34g3H.3 NAPT-less 34g3H.3.1 Definition . 34g3H.3.2 BGF (MG) behaviour for NAPT-less . 34g3H.3.2.1 Handling
18、 of source transport address values SA, SP 35g3H.3.2.2 Handling of destination transport address values DA, DP 35g3H.3.3 Control methods of NAPT-less mode 35g3H.3.3.1 Method 1: mirrored H.248 LD and RD between the two H.248 IP terminations (stream endpoints) . 35g3H.3.3.2 Method 2: omitted address i
19、nformation in H.248 LD and RD 35g3H.3.3.3 Method 3: explicit indication via H.248 Context Attribute 35g3H.3.4 NAPT-less examples 36g3H.3.4.1 “Double“ NAPT-less mode, controlled via method 1 . 36g3H.4 Mixed NA(P)T-full/NA(P)T-less modes 36g3H.4.1 Example of combination of Double-NAPT and NAPT-less 36
20、g3H.4.2 Profile limitations . 37g3Annex I: Illustration of “Protocol Layer Lx“-based Packet Processing BGF modes 38g3I.1 BGF modes - Technological Framework . 39g3I.2 BGF modes - Control Framework 40g3I.3 Example BGF modes - RTP-based Applications . 43g3I.3.1 Example application . 43g3I.3.2 Transpor
21、t-agnostic modes 44g3I.3.3 L4-port aware and transport-protocol agnostic modes . 46g3I.3.4 Transport aware (= L4-port aware and transport-protocol aware) modes 49g3I.3.5 Media framing aware (= media-type aware, media-format agnostic, L4-port aware and transport-protocol aware) modes . 52g3I.3.5.1 Op
22、en items 55g3I.3.6 Media aware “RTP Transport Translator“ (= media-type aware, media-format aware) modes . 55g3I.3.7 Media aware “RTP Media Translator“ (= media-type aware, media-format aware) modes . 58g3I.4 Example BGF modes - TCP-based Applications . 61g3I.4.1 Example application . 61g3ETSI ETSI
23、TR 183 068 V3.1.1 (2009-08) 5I.4.1.1 Mode discrimination . 62g3I.4.2 TCP relay modes 62g3I.4.2.1 Unencrypted transport layer 62g3I.4.2.2 Encrypted transport layer using TLS 64g3I.4.3 TCP proxy modes . 65g3I.5 Summary 67g3Annex J: Illustration of BGF Reporting of Protocol Layer Lx based Performance M
24、easurements . 68g3History 70g3ETSI ETSI TR 183 068 V3.1.1 (2009-08) 6Intellectual 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
25、-members, 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/
26、home.asp). 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
27、the present document. Foreword This Technical Report (TR) has been produced by ETSI Technical Committee Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN). ETSI ETSI TR 183 068 V3.1.1 (2009-08) 71 Scope The present document defines guidelines for usage
28、and implementation of border gateways (BGW), based on H.248 profile definitions for controlling such IP-to-IP gateways like ETSI TISPAN “H.248 Ia profile“ specifications i.1, i.2 and i.3. Figure 1 illustrates the architecture assumed in the present document. Figure 1: Scope 2 References References a
29、re either specific (identified by date of publication and/or edition number or version number) or non-specific. For a specific reference, subsequent revisions do not apply. Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is ac
30、cepted that it will be possible to use all future changes of the referenced document for the purposes of the referring document; - for informative references. Referenced documents which are not found to be publicly available in the expected location might be found at http:/docbox.etsi.org/Reference.
31、 NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity. 2.1 Normative references The following referenced documents are indispensable for the application of the present document. For dated references, only the edition
32、cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. Not applicable. ETSI ETSI TR 183 068 V3.1.1 (2009-08) 82.2 Informative references The following referenced documents are not essential to the use of the present document but
33、they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. i.1 ETSI ES 283 018 (Release 1): “Telecommunications and Internet converged Services and Protocols for Advanced Networking (TI
34、SPAN); Resource and Admission Control: H.248 Profile for controlling Border Gateway Functions (BGF) in the Resource and Admission Control Subsystem (RACS); Protocol specification“. - also known as “H.248 Ia Profile Version 1“. i.2 ETSI ES 283 018 (Release 2): “Telecommunications and Internet converg
35、ed Services and Protocols for Advanced Networking (TISPAN); Resource and Admission Control: H.248 Profile for controlling Border Gateway Functions (BGF) in the Resource and Admission Control Subsystem (RACS); Protocol specification“. - also known as “H.248 Ia Profile Version 2“. i.3 ETSI TS 183 018
36、(Release 3): “Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Resource and Admission Control: H.248 Profile Version 3 for controlling Border Gateway Functions (BGF) in the Resource and Admission Control Subsystem (RACS); Protocol specification“. - a
37、lso known as “H.248 Ia Profile Version 3“. i.4 ITU-T Recommendation H.248.1 (2005): “Gateway control protocol: Version 3“ including its Amendment 1 (05/2008). i.5 ETSI TS 183 048: “Telecommunications and Internet Converged Services and Protocols for Advanced Networking (TISPAN); Resource and Admissi
38、on Control System (RACS); Protocol Signalling flows specification; RACS Stage 3“. i.6 ETSI TS 183 017: “Telecommunications and Internet Converged Services and Protocols for Advanced Networking (TISPAN); Resource and Admission Control: DIAMETER protocol for session based policy set-up information exc
39、hange between the Application Function (AF) and the Service Policy Decision Function (SPDF); Protocol specification“. i.7 ETSI TS 181 018 (Release 2): “Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Requirements for QoS in a NGN“. i.8 ETSI TR 182 0
40、22 (Release 2): “Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Architectures for QoS handling“. i.9 IEEE 802.3: “Ethernet Working Group“. i.10 ETSI TR 187 008 (Release 1): “Telecommunications and Internet converged Services and Protocols for Advan
41、ced Networking (TISPAN); NAT traversal feasibility study report“. i.11 IETF RFC 5117 (2008-01): “RTP Topologies“. i.12 draft-hunt-avt-rtcptrans-00.txt (2007-11): “RTCP Reporting by Translators“. i.13 ITU-T Recommendation Y.1251 (08/2002): “General architectural model for interworking“. i.14 Draft IT
42、U-T Recommendation G.IP2IP: “Functionality and Performance of an IP-to-IP Voice Gateway, optimised for the transport of voice and voiceband data“. i.15 ITU-T Recommendation Y.1560 (09/2003): “Parameters for TCP connection performance in the presence of middleboxes“. i.16 IEEE 802.1: “Local Area Netw
43、orks: Architecture or possible interactions between functions (see e.g. clause D.2). It has to be noted that the model is just an example, not exhaustive concerning all possible functions with regards to supported capabilities by this profile, and not related to any particular implementation. D.1 Ex
44、ample model Figure D.1 provides an example pipeline model, which is only indicating a single H.248 Stream of the (IP, IP) Context. A H.248 Stream is fundamentally bidirectional, i.e. relates to two unicast IP flows, one per traffic direction. This example is not considering aspects of RTP/RTCP mappi
45、ng on a H.248 Stream. The example model is considering optional and mandatory functions by this profile specification. The example is using modelling components for filter (F), detector (D), address processing (A) and statistic (S) entities. There might be further modelling components, e.g. for medi
46、a-aware specific processing functions. The example model is assuming a pure serial processing pipeline, real implementations could of course benefit from parallelization. ETSI ETSI TR 183 068 V3.1.1 (2009-08) 14Figure D.1: H.248 Context - Illustration of IP flow processing - Example Overview There m
47、ight be dependencies between different processing stages, which impact the order of pipeline stages. ETSI ETSI TR 183 068 V3.1.1 (2009-08) 15D.2 Aspects of filter interaction Possible filter interactions are already indicated in several package specifications of the ITU-T Recommendation H.248.x-seri
48、es of Recommendations. General solutions/recommendations are not yet provided by the package definitions themselves. This is therefore rather a subject for profile specifications, which using the correspondent packages. D.2.1 Interaction between address latching and address policing This profile ver
49、sion indicates two possible cases for filter interaction, either due to: enabled latching plus address policing per H.248 Stream, i.e. application of packages ipnapt v1 and gm v1; or the correlation of SDP information from the RD and gm v1 address policing (see clause 5.18.1.1.1, TS 183 118 i.3). Figure D.2 illustrates the possible interaction: the ingress filter stage Fin,1provides explicit source address and port policing and is controlled via gm v1 properties (see clause 5.18.1.1.1, TS 183 118 i.3). Source address
