SIST-TS ETSI/TS 101 909-13-1 V1.1.1:2005

• Abstract:

  Produce a TS defining a profile of H.248 protocol for controlling media gateways between cable networks and the PSTN. This profile may need H.248 packages that are not currently available. Definition of such packages is also part of the work item. This activity should result in a single standard for European use taken into account DTS/AT-020020-13 and DES/AT-022212-13.

• Status: Published
• Publication Date: 31-Dec-2004
• ICS: 33.040.35 - Telephone networks
• Technical Committee: SPN - Services and Protocols for Networks
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Jan-2005
• Due Date: 01-Jan-2005
• Completion Date: 01-Jan-2005
• Ref Project: ETSI TS 101 909-13-1 V1.1.1 (2002-03) - Digital Broadband Cable Access to the Public Telecommunications Network; IP Multimedia Time Critical Services; Part 13: Trunking Gateway Control Protocol; Sub-part 1: H.248 option

SIST-TS ETSI/TS 101 909-13-1 V1.1.1:2005 is the SIST version of the ETSI Technical Specification for Digital Broadband Cable Access to the Public Telecommunications Network, Part 13, Sub-part 1, H.248 option. It specifies a Trunking Gateway Control Protocol (TGCP) profile for controlling Media Gateways between cable networks and the PSTN, including gateway naming, package support, transport, security and SDP use. The document is written for Media Gateway Controllers, Media Gateways, and the engineers who integrate, test or procure them.

What does SIST-TS ETSI/TS 101 909-13-1 V1.1.1:2005 specify?

SIST-TS ETSI/TS 101 909-13-1 V1.1.1:2005 specifies the TGCP profile of H.248 for the interface between a Media Gateway Controller and a Media Gateway at the boundary between a packet cable network and the PSTN. The document defines how that profile is named, which packages are supported, how signaling is transported, and how SDP is used for audio sessions.

The document is organized into clauses for scope, references, abbreviations, architectural assumptions and profile definition, followed by Annex A with specific package definitions.

Annex	What it covers
Annex A (normative)	Specific package definitions for the Security package

What are the key requirements of SIST-TS ETSI/TS 101 909-13-1 V1.1.1:2005?

Profile identity and package support

Clause 5 defines the profile as TGCP version 1.0, and conforming gateways return that name during initial registration in a ServiceChange command. In practice, this tells an MGC what profile the gateway implements.

Clause 5.1 requires support for the H.248 packages used for generic control, network and TDM circuit handling, tone detection and generation, and call progress handling. It also allows optional packages for announcements, modem, fax modem, fax, and security, with conditional support when modem-related codecs are not transparent or when RTP/RTCP security services are used. This matters because implementation choices depend on the gateway’s trunk types and service mix.

Gateway naming, topology and transport

Clause 5.3 requires MG and MGC names to be domain names and uses DNS-based retry and refresh behavior. Termination identifiers for physical trunks follow a slash-separated hierarchy starting with ds, so a gateway can map control names to physical structure in a consistent way.

Clause 5.4 says topology support is not required, so an MGC must not assume topology information is available. Clause 5.5 requires all H.248 transaction timers, and clause 5.6 requires UDP/ALF transport on both the MG and MGC side. Clause 5.7 allows one primary and one or more secondary MGCs for registration, which is relevant for redundancy planning.

Security and SDP behavior

Clause 5.8 requires IPsec and uses IKE for key management. Clause 5.9 requires text encoding. Clause 5.10 restricts SDP to audio and applies strict RFC 2327 behavior, with specific send and receive rules for each field.

For practical implementation, the most important SDP points are:

• m= uses audio with RTP/AVP
• c= uses IN IP4 and a unicast IP address
• b=AS should be included, especially when rtpmap or non well-known codecs are used
• k= is not used for security parameters
• a= supports rtpmap, X-pc-codecs, X-pc-secret, X-pc-csuites-rtp, X-pc-csuites-rtcp, X-pc-spi-rtcp, recvonly, sendrecv, sendonly and ptime

In practice, these rules tell the gateway exactly what it may signal for codecs, bandwidth, directionality and security, and what it must ignore if received.

Clause 5.11 says timestamps are not required in every notify command, and clause 5.12 says digit maps are not required. That reduces implementation burden where those features are not needed.

What terms does SIST-TS ETSI/TS 101 909-13-1 V1.1.1:2005 define?

TGCP means Trunking Gateway Control Protocol, the H.248 profile specified by this document.
MG means Media Gateway, the endpoint that sits at the cable network/PSTN boundary.
MGC means Media Gateway Controller, the control entity that manages the gateway.
PSTN means Public Switched Telephone Network, the circuit-switched telephone network on the other side of the gateway.
SDP means Session Description Protocol, the media description format used for audio session setup.
IPsec means Internet Protocol security, the security framework required for gateway protection.
IANA means Internet Assigned Number Authority, which is referenced for the Security package identifier allocation.

Who uses SIST-TS ETSI/TS 101 909-13-1 V1.1.1:2005?

This document is used by vendors and engineers working on cable telephony gateways, gateway controllers, and cable network interconnection with the PSTN. It is also relevant to system integrators, interoperability testers, and quality teams that need a clear TGCP profile for implementation checks, registration behavior, transport choices and SDP interworking.

Which standards are used with SIST-TS ETSI/TS 101 909-13-1 V1.1.1:2005?

Reference	What it contributes
ITU-T Recommendation H.248	Base gateway control protocol, package rules and compatibility rules
ETSI TS 101 909-2	Architectural framework for time critical services over cable television networks
ETSI TS 101 909-3	Audio codec requirements
ETSI TS 101 909-11	Security services and permissible ciphersuites
ETSI TS 101 909-1	General series information
ETSI TS 101 909-13-2	The MGCP option for the same trunking gateway control work
IETF/RFC 2327	SDP field rules and session description behavior
IETF/RFC 2401 and IETF/RFC 2402	IPsec and the cited key-management reference
IETF/RFC 1889 and IETF/RFC 1890	RTP and the RTP audio/video profile context
IETF/RFC 2543	Direction attributes such as recvonly, sendrecv and sendonly
IETF/RFC 2234	ABNF syntax notation used in parameter syntax
IETF/RFC 2045	Base64 encoding for security-related text values

What does the SIST-TS ETSI/TS 101 909-13-1 V1.1.1:2005 document contain?

The document contains package tables for mandatory, optional and conditional TGCP support, plus the profile rules that decide when each package applies. It gives naming examples for Media Gateways, MGCs and terminations so implementers can build consistent control identifiers.

It also contains detailed SDP send and receive rules for audio, including c=, b=, m=, a= and ptime behavior. Annex A defines the Security package, its properties and the procedures for secrets and ciphersuites, which is the part most directly used when implementing security-related gateway control.

SLOVENSKI STANDARD
01-januar-2005
'LJLWDOQLãLURNRSDVRYQLNDEHOVNLGRVWRSGRMDYQLKWHOHNRPXQLNDFLMVNLKRPUHåLM±
9HþSUHGVWDYQRVWQHþDVRYQRNULWLþQHVWRULWYH,3±GHO.UPLOQLSURWRNRO
SUHQRVQLãNHJDSUHKRGD±SRGGHO,]ELUD+
Digital Broadband Cable Access to the Public Telecommunications Network; IP
Multimedia Time Critical Services; Part 13: Trunking Gateway Control Protocol; Sub-part
1: H.248 option
Ta slovenski standard je istoveten z: TS 101 909-13-1 Version 1.1.1
ICS:
33.040.35 Telefonska omrežja Telephone networks
SIST-TS ETSI/TS 101 909-13-1 en
V1.1.1:2005
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

Technical Specification
Digital Broadband Cable Access to the
PublicTelecommunications Network;
IP Multimedia Time Critical Services;
Part 13: Trunking Gateway Control Protocol;
Sub-part 1: H.248 option
2 ETSI TS 101 909-13-1 V1.1.1 (2002-03)

Reference
DTS/SPAN-120085
Keywords
gateway, H.248, IP, profile
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important 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 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 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://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, send your comment to:
[e-mail]
Copyright Notification
No part 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 2002.
All rights reserved.
TM TM TM
DECT , PLUGTESTS and UMTS are Trade Marks of ETSI registered for the benefit of its Members.
TM
TIPHON and the TIPHON logo are Trade Marks currently being registered by ETSI for the benefit of its Members.
TM
3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
ETSI
3 ETSI TS 101 909-13-1 V1.1.1 (2002-03)
Contents
Intellectual Property Rights.4
Foreword.4
Introduction .4
1 Scope.5
2 References.5
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 packages.7
5.2 Compatibility rules.7
5.3 Naming conventions.7
5.3.1 MG and MGC names.7
5.3.2 Termination identifiers.8
5.4 Topology descriptor.8
5.5 Transaction timers.8
5.6 Transport.8
5.7 Service change procedures .9
5.8 Security.9
5.9 Encoding.9
5.10 Use of SDP .9
5.10.1 Protocol version (v=) .9
5.10.2 Origin (o=).9
5.10.3 Session name (s=) .10
5.10.4 Session and media information (i=).10
5.10.5 URI (u=).10
5.10.6 E-mail address and phone number (e=, p=) .10
5.10.7 Connection data (c=).11
5.10.8 Bandwidth (b=).11
5.10.9 Time, repeat times and time zones (t=, r=, z=) .11
5.10.10 Encryption keys.12
5.10.11 Attributes (a=).12
5.10.12 Media announcements (m=) .14
5.11 Timestamp.14
5.12 Digits maps.14
Annex A (normative): Specific package definitions .15
A.1 Security package.15
A.1.1 Properties.15
A.1.2 Events.15
A.1.3 Signals.15
A.1.4 Statistics.16
A.1.5 Procedures.16
History .17

ETSI
4 ETSI TS 101 909-13-1 V1.1.1 (2002-03)
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, 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).
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 present document.
Foreword
This Technical Specification (TS) has been produced by ETSI Technical Committee Services and Protocols for
Advanced Networks (SPAN).
The present document is part 13, sub-part 1 of a multi-part deliverable. Full details of the entire series can be found in
part 1 [12].
Introduction
The present document defines a solution based on H.248. The solution based on MGCP is defined in
TS 101 909-13-2 [13].
Where alternative solutions for the same interface are being considered, interoperability issues between the various
IPCablecom system components need to be addressed.
ETSI
5 ETSI TS 101 909-13-1 V1.1.1 (2002-03)
1 Scope
The present document specifies a profile of the H.248 protocol [1] for controlling media gateways between cable
networks and the 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 edition 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.
[1] ITU-T Recommendation H.248: "Gateway Control Protocol".
[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 Television networks using cable modems".
[3] ETSI TS 101 909-3: "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 Television 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 (1988): "SDP: Session Description Protocol".
[6] IETF/RFC 2401 (1998): "Security Architecture for the Internet Protocol".
[7] IETF/RFC 2402 (1998): "IP Authentication Header".
[8] IETF/RFC 1889 (1996): "RTP: A Transport Protocol for Real-Time Applications".
[9] IETF/RFC 2543: "Session Initiation Protocol".
[10] IETF/RFC 2234: "Augmented BNF for Syntax Specifications: ABNF".
[11] IETF/RFC 1890: "RTP Profile for Audio and Video Conferences with Minimal Control".
[12] ETSI TS 101 909-1: "Digital Broadband Cable Access to the Public Telecommunications
Network; IP Multimedia Time Critical Services; Part 1: General".
[13] 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."
[14] IETF/RFC 2045: "Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet
Message Bodies".
ETSI
6 ETSI TS 101 909-13-1 V1.1.1 (2002-03)
3 Abbreviations
For the purposes of the present document, the following abbreviations apply:
ASCII American Standard Code for Information Interchange
AVP Audio Video Profile
DNS Domain Name System
IANA Internet Assigned Number Authority
IP Internet Protocol
MG Media Gateway
MGC Media Gateway Controller
MTA Message 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 Ressource Identifier
4 Architectural 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 [2].
5 Profile definition
This profile shall be entitled "TGCP". 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.
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 Recommendation H.248 [1], annex E
Base Root root 1 ITU Recommendation H.248 [1], annex E
Continuity ct 1 ITU Recommendation H.248 [1], annex E
Network nt 1 ITU Recommendation H.248 [1], annex E
TDM Circuit tdmc 1 ITU Recommendation H.248 [1], annex E
Tone Detect tonedet 1 ITU Recommendation H.248 [1], annex E
Call Progress Detect cd 1 ITU Recommendation H.248 [1], annex E
Tone Generator tonegen 1 ITU Recommendation H.248 [1], annex E
Call Progress Generator cg 1 ITU Recommendation H.248 [1], annex E

ETSI
7 ETSI TS 101 909-13-1 V1.1.1 (2002-03)
5.1.2 Optional packages
The following packages may be supported:
Table 2: Optinal packages
Package Name Id Version Defined in
Announcement an 1 ITU Recommendation H.248 [1], annex K
Modem mdm 1 ITU Recommendation H.248 [1], annex F
FaxModem ftmd 1 ITU Recommendation H.248 [1], annex F
Fax Fax 1 ITU Recommendation H.248 [1], annex F
Security sec 1 TS 101 909-13-1 [12], clause A.1

5.1.3 Conditional packages
The following optional packages shall be supported under the specified conditions:
Table 3: Conditional packages
Package Name Condition (e.g. trunk type supported)
Modem Some of the codec supported by the cable networks are not
transparent to modem signals.
FaxModem Some of the codec supported by the cable networks are not
transparent to modem signals.
Fax Some of the codec supported by the cable networks are not
transparent to modem signals.
Security The RTP/RTCP services defined in TS 101 909-11 [4] are
supported.
NOTE: A list of permissible ciphersuites are specified in the IPCablecom Security Specification
TS 101 909-11 [4].
5.2 Compatibility rules
This profile is based on ITU-T Recommendation H.248 [1] version 1 (06/00). The compatibility rules for packages,
signals, events, properties and statistics and the H.248 protocol are defined in ITU-T Recommendation H.248 [1].
5.3 Naming 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: mgc1.whatever.net
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 domain 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 (DNS). MG and MGC shall keep track of the record's
time-to-live read from the DNS. They shall query the DNS to refresh the information if the time-to-live has
expired.
...