1、 ETSI TS 102 333 V1.2.0 (2008-01)Technical Specification Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN);Gate control protocolETSI ETSI TS 102 333 V1.2.0 (2008-01) 2 Reference RTS/TISPAN-03140-tech Keywords control, protocol ETSI 650 Route des Luciol
2、es 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 Individual copies of the present document can be downloaded from: http:/
3、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 Format (PDF). In case of dispute, the reference shall be the prin
4、ting 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 current status of this and other ETSI documents is available at http:/
5、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 may be reproduced except as authorized by written permission. The copyright and t
6、he foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2008. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTM, TIPHONTM, the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM is a Trade Mark
7、of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. ETSI ETSI TS 102 333 V1.2.0 (2008-01) 3 Contents Intellectual Property Rights6 Foreword.6 1 Scope 7 2 References 7 2.1 Normative references .7 3 Definitions and abbreviations.8 3.1 Definitions8 3.2 Abbreviatio
8、ns .8 4 Architecture9 5 Profile definition 10 5.1 Profile identification.10 5.2 Summary 11 5.3 Naming conventions.11 5.3.1 MG and MGC names11 5.3.2 Termination names .11 5.3.3 Digit map names .12 5.4 Topology descriptor .12 5.5 Time stamps .12 5.6 Transaction timers 12 5.7 Transport 12 5.8 Encoding.
9、12 5.9 Mandatory support of SDP and annex C information elements .12 5.9.1 Protocol version (v=) 13 5.9.2 Origin (o=)13 5.9.3 Session name (s=) .13 5.9.4 Connection data (c=).13 5.9.5 Media announcements (m=) .13 5.9.6 Bandwidth (b=).14 5.9.7 Time (t=).14 5.10 Packages.14 5.11 Security 15 5.12 Proce
10、dures 15 5.12.1 General principles.15 5.12.2 Opening and closing gates 16 5.12.3 Packet marking .16 5.12.4 Resource reservation.16 5.12.5 Allocation and translation of IP addresses and ports 17 5.12.6 Policing of incoming traffic17 5.12.7 Usage metering .17 5.12.8 Quality of Service monitoring 18 5.
11、12.9 Inactivity test 18 5.12.10 Overload control .18 Annex A (normative): Differentiated Services package19 A.1 Overall description .19 A.2 Properties19 A.3 Events.19 A.4 Signals 19 A.5 Statistics .19 A.6 Procedures 19 ETSI ETSI TS 102 333 V1.2.0 (2008-01) 4 Annex B (normative): Gate management pack
12、age .20 B.1 Overall description .20 B.2 Properties20 B.3 Events.21 B.4 Signals 21 B.5 Statistics .22 B.6 Procedures 22 Annex C (normative): Traffic management package23 C.1 Overall description .23 C.2 Properties23 C.3 Events.23 C.4 Signals 24 C.5 Statistics .24 C.6 Procedures 24 Annex D (normative):
13、 Gate recovery information package.25 D.1 Overall description .25 D.2 Properties25 D.3 Events.25 D.4 Signals 25 D.5 Statistics .25 D.6 Procedures 25 Annex E (normative): NAT traversal package26 E.1 Overall description .26 E.2 Properties26 E.3 Events.26 E.4 Signals 26 E.5 Statistics .26 E.6 Procedure
14、s 26 Annex F (normative): MPLS package .27 F.1 Overall description .27 F.2 Properties27 F.3 Events.27 F.4 Signals 27 F.5 Statistics .27 F.6 Procedures 27 Annex G (normative): VLAN package .28 G.1 Overall description .28 ETSI ETSI TS 102 333 V1.2.0 (2008-01) 5 G.2 Properties28 G.3 Events.28 G.4 Signa
15、ls 28 G.5 Statistics .28 G.6 Procedures 29 Annex H (informative): Bibliography.30 History 31 ETSI ETSI TS 102 333 V1.2.0 (2008-01) 6 Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essent
16、ial IPRs, if any, is publicly available for ETSI members and non-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
17、are available on the ETSI Web server (http:/webapp.etsi.org/IPR/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 ETS
18、I 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 Technical Committee Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN). ETSI ETSI TS 102 333 V1.2.
19、0 (2008-01) 7 1 Scope The present document defines a profile of the MEGACO protocol for controlling gates between IP transport domains. It also defines specific packages that are required by this profile specification. 2 References References are either specific (identified by date of publication an
20、d/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 accepted that it will be possible to use all future change
21、s 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. For online referenced documents, information sufficient
22、 to identify and locate the source shall be provided. Preferably, the primary source of the referenced document should be cited, in order to ensure traceability. Furthermore, the reference should, as far as possible, remain valid for the expected life of the document. The reference shall include the
23、 method of access to the referenced document and the full network address, with the same punctuation and use of upper case and lower case letters. 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 re
24、ferences The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. 1 ITU-T Recommendation H.248
25、.1: “Gateway control protocol: Version 3“. 2 ETSI TS 101 332: “Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 4; Interface Protocol Requirements Definition; TIPHON Extended H.248/MEGACO Package (EMP) Specification; ICF Control over Reference Point“. 3 IETF RFC
26、2327: “SDP: Session Description Protocol“. 4 IETF RFC 2401: “Security Architecture for the Internet Protocol“. 5 IETF RFC 2402: “IP Authentication Header“. 6 IETF RFC 3264: “An Offer/Answer Model with Session Description Protocol (SDP)“. 7 IETF RFC 2474: “Definition of the Differentiated Services Fi
27、eld (DS field) in the IPv4 and IPv6 Headers“. 8 ITU-T Recommendation H.248.4: “Gateway control protocol: Transport over Stream Control Transmission Protocol (SCTP)“. 9 ITU-T Recommendation H.248.13: “Gateway control protocol: Quality Alert Ceasing package“. ETSI ETSI TS 102 333 V1.2.0 (2008-01) 8 10
28、 ITU-T Recommendation H.248.10: “Gateway control protocol: Media gateway resource congestion handling package“. 11 ITU-T Recommendation H.248.11: “Gateway control protocol: Media gateway overload control package“. 12 ITU-T Recommendation H.248.14: “Gateway control protocol: Inactivity timer package“
29、. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definitions apply: gate: represents a transport plane function enabling or disabling the forwarding of IP packets under specified conditions (e.g. QoS) Gate Controller (GC): logical en
30、tity that controls gates and associated resources in a Multimedia Border Gateway Multimedia Border Gateway (MBG): physical entity that sits at the boundary between two IP transport networks and manages a set of gates under the control of a Gate Controller 3.2 Abbreviations For the purposes of the pr
31、esent document, the following abbreviations apply: CDR Call Detailed Record DNS Domain Name System DS Differentiated ServicesDSCP Differentiated Services Code Point EMP Extended MEGACO Package GC Gate Controller IANA Internet Assigned Number Authority IKE Internet Key Exchange IP Internet Protocol I
32、PSec IP SecurityMBG Multimedia Border Gateway MG Media Gateway MGC Media Gateway Controller MPLS Multi Protocol Label Switching NAPT Network Address and Port Translation NAT Network Address TranslationPHB Per Hop Behaviour QoS Quality of Service RSVP ReSource reserVation Protocol RTCP Real-time Tran
33、sport Control Protocol RTP Real time Transport Protocol RTSP Real Time Streaming Protocol SCTP Stream Control Transport Protocol SDP Session Description Protocol SIP Session Initiation Protocol TCP Transmission Control ProtocolUDP User Datagram Protocol VLAN Virtual LAN ETSI ETSI TS 102 333 V1.2.0 (
34、2008-01) 9 4 Architecture Figure 1 illustrates the architecture assumed in the present document. A Multimedia Border Gateway (MBG) that sits at the boundary between two IP transport networks manages a set of gates under the control of a Gate Controller (GC). Gate Controller IP Transport Network IP T
35、ransport Network Scope of the present document MBG Gate(s) te(s) Figure 1: Gate control architecture With regards to the H.248 protocol, the Gate Controller plays the role of the MGC, while the Multimedia Border Gateway plays the role of the MG. The commands sent by the Gate Controller to the Multim
36、edia Border Gateway are conditioned by admission control policy rules and signalling events that depend on the type of service for which transport resources are to be set-up. Depending on the network architecture and type of services, a Gate Controller may receive such events from other gate control
37、lers or from various types of functions/equipment (e.g. application server functions, call control functions, mediation functions, etc.). The Gate Controller may be co-located with such functions or reside in a stand alone piece of equipment. Admission control policies are outside the scope of the p
38、resent document. In the context of session-based services (e.g. conversational services) the commands sent by the Gate Controller to the Multimedia Border Gateway may depend on session control signalling events. Conversely, the session control signalling entity might need information available at th
39、e Gate Controller (e.g. for mapping IP addresses in SDP descriptions in case NAPT is implemented in the Multimedia Border Gateway). Figure 2 illustrates a configuration where the session signalling entity is co-located with the gate controller. When these entities are not co-located, an appropriate
40、interface and/or mediation function is required between them. The specifications of such interface and/or intermediate function are outside the scope of the present document. ETSI ETSI TS 102 333 V1.2.0 (2008-01) 10GateControllerIP Core NetworkIP Access NetworkScope of thepresent documentSessionCont
41、rolSignallingSession Control SignallingMBGGate (s)Gate (s)SessionControlFigure 2: Example of Gate Control architecture for conversational services In the context of non-conversational services (e.g. video download) the commands sent by the Gate Controller to the Multimedia Access Gateway depend on c
42、ontrol events coming from e.g. an application server function. Figure 3 illustrates a configuration where the application server function is co-located with the gate controller. When these entities are not co-located, an appropriate interface and/or mediation function is required between them. The s
43、pecifications of such interface and/or intermediate function are outside the scope of the present document. GateControllerIP Core NetworkIP Access NetworkScope of the present documentMBGGate (s)Gate (s)ApplicationServerFigure 3: Example of Gate Control architecture for non-conversational service 5 P
44、rofile definition 5.1 Profile identification This profile is entitled “ETSI_GateControl“. The version number is 01. This name shall be used by conforming Multimedia Border Gateways when sending a ServiceChange command as part of the initial registration procedure. This profile is based on ITU-T Reco
45、mmendation H.248.1 version 2 1. NOTE The profile name has been registered with IANA. ETSI ETSI TS 102 333 V1.2.0 (2008-01) 115.2 Summary The profile defined in the present document enables the control of the following functionalities, at the IP layer, at the boundary between two IP transport domains
46、: 1) Opening and closing gates (i.e. packets filtering depending on “IP address/port“). 2) Packet marking for outgoing traffic (i.e. packets leaving the MBG). 3) Resource allocation and bandwidth reservation for outgoing and incoming traffic at both sides of the MBG. 4) Allocation and translation of
47、 IP addresses and port numbers (NAPT). 5) Policing of incoming traffic (i.e. packets entering the MBG). 6) Usage metering. 7) Quality of service monitoring. It also enables the control of the following “layer 2“ functionalities: 1) MPLS labels. 2) VLAN tags. 5.3 Naming conventions 5.3.1 MG and MGC n
48、ames MBG and GC names shall be in the form of a domain name. An example GC name is: . Reliability is provided by the following precautions: MBGs and GCs are identified by their domain name, not their network addresses. Several addresses can be associated with a domain name. If a command cannot be fo
49、rwarded to one of the network addresses, implementations shall retry the transmission using another address. MBGs and GCs may move to another platform. The association between a logical name (domain name) and the actual platform are kept in the Domain Name System (DNS). MBG and GC shall keep track of the records time-to-live read from the DNS. They shall query the DNS to refresh the information if the time-to-live has expired. 5.3.2 Termination names The Termination ID structure is provisioned in the MBG and is known by the M
