1、 ETSI TS 101 909-13-1 V1.2.1 (2004-05)Technical Specification Digital Broadband Cable Access to thePublicTelecommunications Network;IP Multimedia Time Critical Services;Part 13: Trunking Gateway Control Protocol;Sub-part 1: H.248 optionETSI ETSI TS 101 909-13-1 V1.2.1 (2004-05) 2 Reference RTS/TISPA
2、N-03017-Tech Keywords gateway, H.248, IP, profile 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 noti
3、ce 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 Portable
4、 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. Information on
5、 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, send your comment to: editoretsi.org Copyright Notification No part may be reproduced except as authorized by written permission. The copyright
6、and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2004. 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
7、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 ETSI TS 101 909-13-1 V1.2.1 (2004-05) 3 Contents Intellectual Property Rights4 Foreword.4 Introduction 4 1 Scope 5 2 References 5
8、3 Abbreviations .6 4 Architectural assumptions 6 5 Profile definition 6 5.1 Support of packages .6 5.1.1 Mandatory packages .6 5.1.2 Optional packages.7 5.1.3 Conditional packages7 5.2 Compatibility rules.7 5.3 Naming conventions.7 5.3.1 MG and MGC names7 5.3.2 Termination identifiers .7 5.4 Topolog
9、y descriptor .8 5.5 Multiplex descriptor .8 5.6 Transaction timers 8 5.7 Transport 9 5.8 Service change procedures .9 5.9 Security 9 5.10 Encoding.9 5.11 Use of SDP .9 5.11.1 Protocol version (v=) 10 5.11.2 Origin (o=)10 5.11.3 Session name (s=) .11 5.11.4 Session and media information (i=)11 5.11.5
10、 URI (u=) .12 5.11.6 E-mail address and phone number (e=, p=) 12 5.11.7 Connection data (c=).12 5.11.8 Bandwidth (b=).13 5.11.9 Time, repeat times and time zones (t=, r=, z=) .14 5.11.10 Encryption keys 14 5.11.11 Attributes (a=).14 5.11.12 Media announcements (m=) .17 5.12 Timestamp19 5.13 Digits m
11、aps.19 Annex A (informative): Bibliography.20 History 21 ETSI ETSI TS 101 909-13-1 V1.2.1 (2004-05) 4 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 a
12、vailable 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 are available on the ETSI Web s
13、erver (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 ETSI Web server) which are, or may
14、 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). The present document is part 13, sub-part 1 of a multi-pa
15、rt deliverable. Full details of the entire series can be found in part 1 9. Introduction The present document defines a solution based on ITU-T Recommendation H.248.1 1. The solution based on MGCP is defined in TS 101 909-13-2 10. Where alternative solutions for the same interface are being consider
16、ed, interoperability issues between the various IPCablecom system components need to be addressed. ETSI ETSI TS 101 909-13-1 V1.2.1 (2004-05) 5 1 Scope The present document specifies a profile of the ITU-T Recommendation H.248 protocol 1 for controlling media gateways between cable networks and the
17、PSTN. This profile is known as Trunking Gateway Control Protocol (TGCP) version 1. 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 ed
18、ition number or version number) or non-specific. For 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/R
19、eference. 1 ITU-T Recommendation H.248.1: “Gateway control protocol: Version 2“. 2 ETSI TS 101 909-2: “Digital Broadband Cable Access to the Public Telecommunications Network; IP Multimedia Time Critical Services; Part 2: Architectural framework for the delivery of time critical services over cable
20、Television networks using cable modems“. 3 ETSI TS 101 909-3: “Access and Terminals (AT); Digital Broadband Cable Access to the Public Telecommunications Network; IP Multimedia Time Critical Services; Part 3: Audio Codec Requirements for the Provision of Bi-Directional Audio Service over Cable Telev
21、ision Networks using Cable Modems“. 4 ETSI TS 101 909-11: “Digital Broadband Cable Access to the Public Telecommunications Network; IP Multimedia Time Critical Services; Part 11: Security“. 5 IETF RFC 2327: “SDP: Session Description Protocol“. 6 IETF RFC 1889: “RTP: A Transport Protocol for Real-Tim
22、e Applications“. 7 IETF RFC 2234: “Augmented BNF for Syntax Specifications: ABNF“. 8 IETF RFC 1890: “RTP Profile for Audio and Video Conferences with Minimal Control“. 9 ETSI TS 101 909-1: “Digital Broadband Cable Access to the Public Telecommunications Network; IP Multimedia Time Critical Services;
23、 Part 1: General“. 10 ETSI TS 101 909-13-2: “Digital Broadband Cable Access to the Public Telecommunications Network; IP Multimedia Time Critical Services; Part 13: Trunking Gateway Control Protocol; Sub-part 2: MGCP option“. 11 IETF RFC 2045: “Multipurpose Internet Mail Extensions (MIME) Part One:
24、Format of Internet Message Bodies“. 12 ITU-T Recommendation J.170: “IPCablecom security specification“. 13 ITU-T Recommendation J.171: “IPCablecom Trunking Gateway Control Protocol (TGCP)“. 14 ITU-T Recommendation H.248.2: “Gateway control protocol: Facsimile, text conversation and call discriminati
25、on packages“. ETSI ETSI TS 101 909-13-1 V1.2.1 (2004-05) 6 3 Abbreviations For the purposes of the present document, the following abbreviations apply: ALF Application Level Framing AVP Audio Video Profile DNS Domain Name System IP Internet Protocol MG Media GatewayMGC Media Gateway Controller MTA M
26、essage Transfer Agent PSTN Public Switched Telephone Network RTCP Real-time Transfer Control Protocol RTP Real-time Transfer Protocol SDP Session Description Protocol SPI Security Parameters Index TGCP Trunking Gateway Control Protocol UDP User Data Protocol URI Universal Resource Identifier 4 Archi
27、tectural assumptions The present document applies to the interface between a Media Gateway Controller and a Media Gateway sitting at the boundary between a packet cable network and the PSTN. The overall architecture for interconnecting packet cable networks with the PSTN is described in TS 101 909-2
28、 2. 5 Profile definition This profile shall be entitled “TGCP_H248“. The version number shall be 1.0. This name shall be returned by conforming gateways when sending a ServiceChange command as part of the initial registration of the MG. This Profile is applicable to version 2 if ITU-T Recommendation
29、 H.248.1 1. 5.1 Support of packages 5.1.1 Mandatory packages The following packages shall be supported. Table 1: Mandatory packages Package name Id Version Defined in Generic g 1 ITU-T Recommendation H.248.1 1, annex E Base Root root 1 ITU-T Recommendation H.248.1 1, annex E Continuity ct 1 ITU-T Re
30、commendation H.248.1 1, annex E Network nt 1 ITU-T Recommendation H.248.1 1, annex E TDM Circuit tdmc 1 ITU-T Recommendation H.248.1 1, annex E ISUP Trunk Tones Generator isuptn 1 ITU-T Recommendation J.171 13, annex B ETSI ETSI TS 101 909-13-1 V1.2.1 (2004-05) 7 5.1.2 Optional packages Void. 5.1.3
31、Conditional packages The following optional packages shall be supported under the specified conditions. Table 2: Conditional packages Package name Id Version Defined in Condition Fax/TextPhone/ Modem Tones Detection ftmd 1 ITU-T Recommendation H.248.2 14 Some of the codecs supported by the cable net
32、works are not transparent to fax, modem or textphone signals. 5.2 Compatibility rules This profile is based on ITU-T Recommendation H.248.1 1. The compatibility rules for packages, signals, events, properties and statistics and the H.248 protocol are defined in ITU-T Recommendation H.248.1 1. 5.3 Na
33、ming conventions 5.3.1 MG and MGC names MG and MGC names shall be in the form of a domain name. An example MGC name is: . Reliability is provided by the following precautions: MGs and MGCs are identified by their domain name, not their network addresses. Several addresses can be associated with a do
34、main name. If a command cannot be forwarded to one of the network addresses, implementations shall retry the transmission using another address. MGs and MGCs may move to another platform. The association between a logical name (domain name) and the actual platform are kept in the Domain Name Service
35、 (DNS). MG and MGC 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 identifiers Termination identifiers representing physical trunks or trunks groups shall adhere to the following co
36、nventions: Termination names shall consist of a series of terms each separated by a slash (“/“) that describe the physical hierarchy within the gateway: ds/-/-/ The first term (ds) identifies the termination naming scheme used and the basic termination type. The last term is a decimal number that in
37、dicates the channel number at the lowest level of the hierarchy. ETSI ETSI TS 101 909-13-1 V1.2.1 (2004-05) 8 Intermediate terms between the first term (ds) and last term (channel number) represent intermediate levels of the hierarchy and consist of and separated by an underscore (“_“) where: - the
38、identifies the particular hierarchy level. Values of presently defined are: “s“, “su“, “oc3“, “ds3“, “e3“, “ds2“, “e2“, “ds1“, “e1“ where “s“ indicates a slot number and “su“ indicates a sub-unit within a slot. Other values representing physical hierarchy levels that have not been included in this l
39、ist but which follow the same basic naming rules will also be allowed; - the is a decimal number which is used to reference to a particular instance of a at that level of the hierarchy. The number of levels and naming of those levels is based on the physical hierarchy within the media gateway, as il
40、lustrated by the following examples: - a Media Gateway that has some number of DS1 interfaces: ds/ds1_#/# - a Media Gateway that has some number of OC3 interfaces, that contain channelized DS3 and DS1 hierarchies: ds/oc3_#/ds3_#/ds1_#/# - a Media Gateway that contains some number of slots with each
41、slot having some number of DS3 interfaces: ds/s_#/ds3_#/ds1_#/# Some terminations may not contain all possible levels of a hierarchy, however all levels supported by a given termination are contained in the termination naming scheme. For example, a DS3 without DS1 framing could be represented by the
42、 following naming scheme: ds/s_#/ds3_#/# - however, a DS3 with DS1 framing could not be represented by that naming scheme. 5.4 Topology descriptor A Gateway conforming to the present document need not to implement topology. MGCs that expect control gateway conforming to the present document shall no
43、t assume that topology is supported. 5.5 Multiplex descriptor A Gateway conforming to the present document need not implement the mux descriptor. MGCs that expect to control gateways conforming to the present document shall not assume that mux descriptor is supported. 5.6 Transaction timers All tran
44、saction timers as specified in ITU-T Recommendation H.248.1 1 shall be supported here. For this profile of ITU-T Recommendation H.248 the following default values are specified in relation to ITU-T Recommendation H.248 transaction timers and retransmission thresholds: LONG-TIMER: This shall have a d
45、efault value of 30 s. T-MAX: This shall have a default value of 20 s. MAX-1: This shall have a default value of 5 re-transmissions. MAX-2: This shall have a default value of 7 re-transmissions. ETSI ETSI TS 101 909-13-1 V1.2.1 (2004-05) 9 NOTE: In all cases where ITU-T Recommendation H.248.1 1 speci
46、fies defaults, it should be noted that all of the properties of the timer or re-transmission thresholds described within ITU-T Recommendation H.248.1 1 itself remain in force. In particular this means that if H.248 states that a timer or re-transmission threshold may be later configured through prov
47、isioning, then this behaviour is also allowed 5.7 Transport Media Gateways shall implement UDP/ALF. 5.8 Service change procedures The Media Gateway shall allow one primary and one or more secondary MGCs to be provisioned for registration. 5.9 Security Media Gateways and Media Gateways Controllers sh
48、all implement as described in the IPCablecom security specification (ITU-T Recommendation J.170 12). 5.10 Encoding Conforming Media Gateways and Media Gateway Controllers shall support text encoding. 5.11 Use of SDP The Local and Remote descriptors use SDP with certain modifications in the MGC to MG
49、 direction as specified in ITU-T Recommendation H.248.1 1. Furthermore, trunking gateways conforming to this profile may make certain simplifying assumptions about the session descriptions as specified in the following. SDP usage depends on the type of session, as specified in the “media“ parameter. The present document only supports media of type “audio“. The SDP profile provided describes the use of the session description protocol in TGCP. The general descrip
