1、 TECHNICAL REPORT T1.TR.76-2001 Technical Report on Operation of the Bearer Independent Call Control Protocol with IP Bearer Control Protocol Prepared by T1S1.7 Working Group on Services, Architecture, and Control Problem Solvers to the Telecommunications Industry A Word from ATIS and Committee T1 E
2、stablished in February 1984, Committee T1 develops technical standards, reports and requirements regarding interoperability of telecommunications networks at interfaces with end-user systems, carriers, information and enhanced-service providers, and customer premises equipment (CPE). Committee T1 is
3、 sponsored by ATIS and is accredited by ANSI. T1.TR.76-2001 Published by Alliance for Telecommunications Industry Solutions 1200 G Street, NW, Suite 500 Washington, DC 20005 Committee T1 is sponsored by the Alliance for Telecommunications Industry Solutions (ATIS) and accredited by the American Nati
4、onal Standards Institute (ANSI). Copyright 2002 by Alliance for Telecommunications Industry Solutions All rights reserved. No part of this publication may be reproduced in any form, in an electronic retrieval system or otherwise, without the prior written permission of the publisher. For information
5、 contact ATIS at 202.628.6380. ATIS is online at . Printed in the United States of America. T1.TR.76-2001 Technical Report Operation of the Bearer Independent Call Control Protocol with IP Bearer Control Protocol Alliance for Telecommunications Industry Solutions Approved October 2001 Abstract This
6、report describes the general aspects of the operation of the Bearer Independent Call Control (BICC) protocol Capability Set 1+ (CS 1+) with IP Bearer Control Protocol, used to control IP bearer connections. The text is based on the ITU-T Recommendation Q.Sup36 Technical Report TRQ.3030. Changes from
7、 ITU-T Recommendation Q.Sup36 Technical Report TRQ.3030 to suit the national environment are shown with change bars. T1.TR.76-2001 Foreword This technical report (TR) describes the general aspects of the operation of the Bearer Independent Call Control (BICC) protocol Capability Set 1+ (CS 1+) with
8、IP Bearer Control Protocol, used to control IP bearer connections. Footnotes and informative annexes are not officially part of this TR. Future control of this TR will reside with Alliance for Telecommunications Industry Solutions. Suggestions for improvement of this specification will be welcome. T
9、hese should be sent to the Alliance for Telecommunications Industry Solutions, T1 Secretariat, 1200 G Street, NW, Suite 500, Washington DC 20005. This TR was processed and approved for submittal to ATIS by the Accredited Standards Committee on Telecommunications, T1. Committee approval of this speci
10、fication does not necessarily imply that all Committee members voted for its approval. Working Group T1S1.7 of Technical Subcommittee T1S1 on Services, Architectures, and Signaling developed this TR. Over the course of its development the following individuals participated in the Working Groups disc
11、ussions and made significant contributions to the report: Martin Dolly, T1S1.7 Working Group Chair Joe Zebarth, T1S1.7 Working Group Vice Chair Viqar Shaikh, T1S1.7 Technical Editor Stuart Goldman Kevin Hager Mike Pierce Janey Cheu Koan S. Chong Tung-Hai Hsiao Donna Imrich Doris Lebovits Hans Oudmae
12、r A. J. Moore, Jr. Stewart Patch Dan Greene Chip Sharp Dick Boblin Don Choi Keith Bronley Linda Troy Bruce Northcote M. I. McLoughlin Michael Collison Chris Vitalos Mark Hosford Dawn Benedetto Rolfe Buhrke Jim Calme Julie Federico Larry Forni Patti McCalmont Michael McGrew Cheryl Toth Al Varney Robe
13、rt B. Waller Tom Walsh John Boal Yatendra Pathak Dick Weadon Nick Andre Carolyn Taylor Hui Feng Khalid Ahmad Ghassem Koleyni Gregory Wright Michael Zeug Tuan A. Pham Eliot Rosen Glenn Sisson Dave VanderMeiden George Allen John Roquet B. Sambasivan Mike Tisiker Jim Lord Jason Torrey Wesley Downum Jay
14、 Hilton Zhi-Wei Lin Selvam Rengasami Niranjan Sandesara Ray P. Singh Joanie Cardon Steve Showell ii T1.TR.76-2001 Table of Contents 0 Executive Summary .1 1 Scope.1 2 References.2 3 Definitions 3 4 Abbreviations .3 5 Information Exchanged between BICC and IP BCP Signaling Entities 3 5.1 Channel Attr
15、ibutes4 5.1.1 Codec Information4 5.1.2 User Service Information4 5.2 Addressing .5 5.3 Binding Information 5 5.4 Cause.5 Table of Tables Table 1 - Mapping of Channel Attributes4 Table 2 - Mapping of Codec Type to RTP/AVP Payload Type.4 Table 3 - Mapping of User Service Information to RTP/AVP Payload
16、 Type.5 Table 4 - Mapping of Cause (IP BCP Signaling Entity to BCF/CSF Logical Interface).6 Table 5 - Generation of Cause Values (IP BCP Signaling Entity to BICC Cause Categories) .6 Table of Figures Figure 1 - Scope of this Report 1 T1.TR.76-2001 Operation of the Bearer Independent Call Control Pro
17、tocol with IP Bearer Control Protocol 0 Executive Summary This report describes the general aspects of the operation of the Bearer Independent Call Control (BICC) protocol Capability Set 1+ (CS 1+) with IP Bearer Control Protocol, used to control IP bearer connections. 1 Scope This report contains i
18、nformation relevant to the operation of the Bearer Independent Call Control (BICC) Protocol Capability Set 1+ (CS 1+) 7, with the IP Bearer Control Protocol (IP BCP) 8. Information that is relevant to be passed between the BICC 7 signaling entity and the IP BCP 8 signaling entity is identified. The
19、dashed box of Figure 1 shows the scope of this report. Interaction with layer management is outside the scope of this report. NOTE - The handling of reuse of idle bearer connections is outside the scope of the present report. BICC signaling PDUsBICCSignalingIP BCPSignalingScope of this reportIP BCP
20、signaling PDUsSAPprimitivesSAPprimitivesLayer ManagementBCFCSFIP Service End PointFigure 1 - Scope of this Report 1 T1.TR.76-2001 2 References The following references are cited at the appropriate places in the text of this report: 1 ITU-T Recommendation H.248 (06/2000), Gateway Control Protocol12 I
21、ETF RFC 2327, SDP: Session Description Protocol23 IETF RFC 1890, RTP Profile for Audio and Video Conferences with Minimal Control24 ITU-T Recommendation X.200 (07/1994), Information Technology Open System Interconnection Basic Reference Model: The Basic Model15 ITU-T Recommendation X.210 (11/1993),
22、Information Technology Open System Interconnection Basic Model: Convention for the Definition of OSI Services16 ITU-T Recommendation Q.Sup36 Technical Report TRQ.3030 (12/2000), Operation of the Bearer Independent Call Control Protocol with IP Bearer Control Protocol17 T1.673-2002, Bearer Independen
23、t Call Control (BICC) Capability Set (CS) 1+38 T1.676-2001, BICC IP Bearer Control Protocol (IPBCP)39 IETF RFC 1189 - RTP: A Transport Protocol for Real-Time Applications210 ITU-T Recommendation G.711 (11/1988), Pulse code modulation (PCM) of voice frequencies111 ITU-T Recommendation G.722 (11/1988)
24、, 7 kHz audio-coding within 64 kbit/s112 ITU-T Recommendation G.723.1 (03/1996), Dual rate speech coder for multimedia communications transmitting at 5.3 and 6.3 kbit/s113 ITU-T Recommendation G.726 (12/1990), 40, 32, 24, 16 kbit/s Adaptive Differential Pulse Code Modulation (ADPCM)114 ITU-T Recomme
25、ndation G.727 (12/1990), 5-, 4-, 3- and 2-bits sample embedded adaptive differential pulse code modulation (ADPCM)115 ITU-T Recommendation G.728 (09/1992), Coding of speech at 16 kbit/s using low-delay code excited linear prediction116 ITU-T Recommendation G.729 (03/1996), Coding of speech at 8 kbit
26、/s using conjugate-structure algebraic-code-excited linear-prediction117 ITU-T Recommendation H.221 (05/1999), Frame structure for a 64 to 1920 kbit/s channel in audiovisual teleservices118 T1.113-2000, Signaling System No.7 ISDN User Part3_ 1This document is available from the International Telecom
27、munications Union. 2This document is available from the Internet Engineering Task Force (IETF). 3This document is available from the Alliance for Telecommunications Industry Solutions, 1200 G Street N.W., Suite 500, Washington, DC 20005. 2 T1.TR.76-2001 19 ITU-T Recommendation Q.850 (05/1998), Usage
28、 of Cause and Location in the Digital Subscriber Signaling System No. 1 and the Signaling System No. 7 ISDN User Part13 Definitions No definitions are introduced for the purpose of this report. 4 Abbreviations AVP Audio/Video Profile BCF Bearer Control Function BICC Bearer Independent Call Control C
29、SF Call Server Function CS 1+ Capability Set 1+ IP Internet Protocol IP BCP IP Bearer Control Protocol PDU Protocol Data Unit RTP Real Time Protocol SAP Service Access Point SDP Session Description Protocol 5 Information Exchanged between BICC and IP BCP Signaling Entities It is assumed that the for
30、mat of information passed between the BICC 7 signaling entity and the IP BCP 8 signaling entity is the same as the format of information passed between two peer BICC 7 entities. No primitives are defined for this interface. The following sub sections list the information passed between the BICC 7 an
31、d IP BCP 8 signaling entities. The relevant information relates to: 1. Channel Attributes, 2. Addressing, 3. Binding Information, and 4. Cause. 3 T1.TR.76-2001 5.1 Channel Attributes Table 1 identifies the Channel Attributes related information passed from the BICC signaling entity to the IP BCP sig
32、naling entity that are applicable to derive the IP Bearer Control Parameters needed to control the establishment of the IP BCP bearer. Table 1 - Mapping of Channel Attributes BICC Signaling Entity7 IP BCP Signaling Entity8 Codec Information note, or | User Service Information note SDP Payload (m= au
33、dio RTP/AVP ) | NOTE - Codec Information is used if present; otherwise, the User Service Information is used. 5.1.1 Codec Information Table 2 identifies the Codec type information passed from the BICC signaling entity to the IP BCP signaling entity that are applicable to derive the RTP/AVP Payload T
34、ype which may be used to control the establishment of the IP BCP bearer. Table 2 - Mapping of Codec Type to RTP/AVP Payload Type BICC Signaling Entity 7 Codec Type IP BCP Signaling Entity8 Payload Type2,3 ITU-T Recommendation G.711 64 kbit/s -law0 ITU-T Recommendation G.711 56 kbit/s -lawNot support
35、ed ITU-T Recommendation G.722 (SB-ADPCM)9 ITU-T Recommendation G.723.1Not supported ITU-T Recommendation G.723.1 Annex A (silence suppression)Not supported ITU-T Recommendation G.726 (ADPCM)Not supported ITU-T Recommendation G.727 (Embedded ADPCM)Not supported ITU-T Recommendation G.72815 ITU-T Reco
36、mmendation G.729 (CS-ACELP)Not supported ITU-T Recommendation G.729 Annex B (silence suppression)Not supported 5.1.2 User Service Information Table 3 identifies the User service Information passed from the BICC signaling entity to the IP BCP signaling entity that are applicable to derive the RTP/AVP
37、 Payload Type which may be used to control the establishment of the IP BCP bearer. This mapping applies only if Codec type information is not available. 4 T1.TR.76-2001 Table 3 - Mapping of User Service Information to RTP/AVP Payload Type | BICC Signaling Entity7 User Service Information 19 IP BCP S
38、ignaling Entity8 Payload Type2,3 64 kbit/s unrestricted Not supported 64 kbit/s unrestricted preferred 9 | 3.1 kHz audio 0 | Speech 0 | 2 x 64 (No procedures specified for US networks.) 384 Not supported | 1472 Not supported 1536 Not supported | 1920 (No procedures specified for US networks.) | Mult
39、irate (64 kbit/s base rate) 1 n 24 Not supported 5.2 Addressing Addressing related information is not passed between the BICC signaling entity and the IP BCP signaling entity, as the IP BCP is tunneled via H.2481 (if applicable) and BICC7. 5.3 Binding Information Binding related information is not p
40、assed between the BICC signaling entity and the IP BCP signaling entity, as the IP bearer control protocol is tunneled via H.2481 (if applicable) and BICC7. 5.4 Cause Table 4 identifies the Cause related information, derived from the IP BCP signaling, which is passed from the IP BCP signaling entity
41、 to the BICC signaling entity via the BCF/CSF logical interface to provide the Cause parameter fields giving details on the circumstances of a call being cleared due to an IP BCP bearer establishment failure. 5 T1.TR.76-2001 Table 4 - Mapping of Cause (IP BCP Signaling Entity to BCF/CSF Logical Inte
42、rface) | IP BCP Signaling Entity8 Result = Rejected BCF/CSF Logical Interface Cause Category Note - Location does not exist in IP BCP signaling. Location19 = network beyond interworking point (BI) | Cause related information Cause category (see Table 5) note | | Note - If a BCF/CSF logical cause cat
43、egory is received and a BICC cause value needs to be generated, the BICC cause value #47 “resource unavailable, unspecified” is used. Table 5 identifies the mapping of information received in the IP BCP signaling entity, when the result equals rejected and passed by the IP BCP signaling entity to th
44、e BICC signaling entity via the BCF/CSF logical interface. Applicable information received in the IP BCP signaling entity is mapped to one of the two categories: a) resource unavailable, unspecified or b) interworking, unspecified. Table 5 - Generation of Cause Values (IP BCP Signaling Entity to BIC
45、C Cause Categories) | IP BCP Signaling Entity8 BICC Cause Category | Rejected Message “a“ Resource unavailable, unspecified | Confused Message “b“ Interworking, unspecified There is no Cause related information passed from the BICC signaling entity to the IP BCP signaling entity, as there is no explicit IP BCP clearing procedure as a result of the call being cleared. 6
