1、Technical Report No. 63November 2000Technical Report on the Operationof the BICC Protocol withDigital Subscriber SignallingSystem No. 2 (DSS2)Prepared by T1S1.7Working Group onServices, Architecture, and ControlProblem Solvers to the Telecommunications IndustryCopyright 2000 by Alliance for Telecomm
2、unications IndustrySolutionsAll rights reserved.Committee T1 is sponsored by the Alliance for TelecommunicationsIndustry Solutions (ATIS) and accredited by the American NationalStandards Institute (ANSI)No part of this publication may be reproduced in any form,in an electronic retrieval system or ot
3、herwise, without theprior written permission of the publisher.A Technical Report onTechnical Report on the Operation of the BICC Protocolwith Digital Subscriber Signalling System No. 2(DSS2)ABSTRACTThis contribution presents the final text for a new ANSI Technical Report that specifies theoperation
4、of the BICC protocol with the DSS2 signaling protocol (Q.2931). The proposed text isbased on the ITU-T Supplement (TRQ.3000) approved at the November/December 99 SG 11meeting.Changes from ITU-T TRQ.3000 are shown with change sidebars “|“ along the margins.Changes made to T1 Letter Ballot LB 851 and
5、reflected in this document are the result of thedecisions made at the Letter Ballot Resolution meeting held jointly with T1S1.3 and T1S1.7 onMay 23, 2000.Document T1S1.7/2000-52R3Prepared byT1S1.7 Working Group onServices, Architecture, and ControliTable of Contents1 Scope .12 References .23 Definit
6、ions.24 Abbreviations25 Mapping Functions Between BICC Signalling Entity and DSS2 Signalling Entity 35.1 Binding Information .35.2 Bearer Service Information35.3 Address Information 75.4 Cause 7iiTable of FiguresFigure 1 Scope of this Report 1iiiTable of TablesTable 1 Mapping of Binding Information3
7、Table 2 DSS2 Information Elements Required for the Mapping of Bearer Service Information .4Table 3 Mapping of the BICC USI Parameter and the DSS2 Broadband Bearer Capibility and QoSParameter Information Elements 4Table 4 Mapping of the BICC USI Parameter and the DSS2 AAL Parameters Information Eleme
8、nts .5Table 5 Mapping of BICC USI Codes and ATM Peak Cell Rates in the ATM Peak Cell Rates in the ATMTraffic Descriptor.6Table 6 Mapping of Address Information.7Table 7 Mapping of Cause Information (DSS2 Signalling Entity to BCF/CSF Logical Interface) 7Table 8 Mapping of DSS2 Signalling Entity Cause
9、 Values to BICC Cause Categories 8Table 9 Mapping of Cause Information (BICC Signalling Entity to DSS2 Signalling Entity) 9ivForewordThis Technical Report (TR) describes the general aspects of the Operation of the Bearer Independent CallControl (BICC) Protocol with Digital Subscriber Signalling Syst
10、em No. 2 (DSS2) used for the control ofAAL type 1 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. Suggestionsfor improvement of this specification will be welcome. T
11、hese should be sent to the Alliance forTelecommunications Industry Solutions, T1 Secretariat, 1200 G Street, NW, Suite 500, Washington DC20005.This TR was processed and approved for submittal to ATIS by the Accredited Standards Committee onTelecommunications, T1. Committee approval of this specifica
12、tion does not necessarily imply that allCommittee members voted for its approval.Working Group T1S1.7 developed this TR. Over the course of its development the following individualsparticipated in the Working Groups discussions and made significant contributions to the report:Greg Ratta, T1S1.7 Work
13、ing Group ChairLewis Robart, T1S1.7 Working Group Vice ChairJaney Cheu, EditorNick AndreDawn BenedettoDick BobilinRolfe BuhrkeJim CalmeKoan S. ChongRanga DendiWesley DownumMartin DollyJulie FedericoLarry ForniJim GarrahanEric GrayDan GreeneKevin HagerMark HosfordTung-Hai HsiaoZhi-Wei LinJim LordPatt
14、i McCalmontM.I. McLaughlinA.J. MooreBruce NorthcoteStewart PatchYatendra PathakSelvan RangasamiJohn RoquetB. SambasivanNiranjan SandesaraChip SharpViqar ShaikhRay P. SinghSteve ShowellMike TisikerLinda TroyDave VanderMeidenAl VarneyRobert WallerTom WalshDick WeadonDavid WhitefordRoderick WilsonTECHN
15、ICAL REPORT NO. 631SummaryThis report1describes the general aspects of the operation of Bearer Independent Call Control (BICC)protocol mapping with Digital Subscriber Signalling System No. 2 (DSS2) for AAL Type 1 bearer.1 ScopeThis Technical Report contains information relevant to the operation of t
16、he Bearer Independent CallControl (BICC) protocol1, with the DSS24signalling protocol used for the control of AAL type 1bearer connections.Information which is relevant to be passed between the BICC1signalling entity and the DSS24signalling entity is identified. The dashed box of Figure 1 shows the
17、scope of this report. Interactionwith layer management is outside the scope of this report.BICC signalling PDUsBICCSignallingDSS2SignallingScope of this supplementDSS2 ServiceEnd PointDSS2 signalling PDUsSAPprimitivesSAPprimitivesLayerManagementBCFCSFNoteNote: This is the user-side of DSS2 in the ca
18、se where the interface is to an ATM network. It can bethe network-side on bilateral agreement.Figure 1Scope of this Report1A “|“ mark in the side margin indicates a change from the ITU-T Technical Report TRQ.3000 (1999). Strictlyeditorial changes are not shown.TECHNICAL REPORT NO. 6322 References1 T
19、1.672-2000, Bearer Independent Call Control (BICC)2 ITU-T Recommendation I.363.1, B-ISDN ATM Adaptation Layer Type 1 Specification3 ITU-T Recommendation I.610, Organization and Maintenance Principles of the B-ISDN Access4 ITU-T Recommendation Q.2931, Broadband Integrated Services Digital Network (B-
20、ISDN) -Digital Subscriber Signalling System No. 2 (DSS 2) - User-Network Interface (UNI) Layer 3Specification For Basic Call/Connection Control5 ITU-T Draft Recommendation Q.2941.3, B-ISDN DSS2 Generic Identifier Transport Extensionfor Support of Bearer Independent Call Control6 ITU-T Recommendation
21、 Q.850, Usage of Cause and Location in the Digital SubscriberSignalling System No. 1 and the Signalling System No. 7 ISDN User Part7 ITU-T Recommendation Q.2965.1, B-ISDN Digital Subscriber Signalling System No. 2 Supportof Quality of Service Classes8 ITU-T Recommendation I.371, Traffic Control and
22、Congestion Control in B-ISDN9 ITU-T Recommendation Q.2961.2, Support of ATM Transfer Capability in the BroadbandBearer Capability Information Element10 T1.113-2000, Signalling System No. 7 - ISDN User Part11 ITU-T Recommendation I.356, B-ISDN ATM Layer Cell Transfer Performance12 ITU-T Recommendatio
23、n Q,2610, Broadband Integrated Services Digital Network (B-ISDN) -Usage of Cause and Location in B-ISDN User Part and DSS23 DefinitionsNo new definitions are introduced for the purpose of this report.4 AbbreviationsAAL ATM Adaptation LayerAPP Application Transport ParameterATM Asynchronous Transfer
24、ModeB-BC Broadband Bearer CapabilityBCF Bearer Control FunctionBICC Bearer Independent Call ControlBIWF Bearer Interworking FunctionBNC-ID Backbone Network Connection IdentifierCSF Call Services FunctionCS1 Capability Set 1DBR Deterministic Bit RateGIT Generic Identifier TransportN-ISUP Narrowband I
25、SDN User PartQoS Quality of ServiceSN Serving NodeSS7 Signalling System No. 7TMR Transmission Medium RequirementUSI User Service InformationVCC Virtual Channel ConnectionTECHNICAL REPORT NO. 6335 Mapping Functions between BICC Signalling Entity and DSS2Signalling EntityThe following subclauses list
26、the information passed between the BICC1,7 signaling entity and theDSS2 signaling entity:1) Binding information,2) Bearer service information,3) Address information, and4) Cause information.The mapping reflected in the tables of this clause show the information element or parameter namefollowed by t
27、he information contents in parentheses.5.1 Binding InformationBinding information is used to associate call control signalling and bearer control signalling for theestablishment of an ATM AAL Type 1 bearer. The Backbone Network Connection Identifier (BNC-ID)is carried by call control in the Applicat
28、ion Transport Parameter (APP)1. The BNC-ID is carried bybearer control in the Generic Identifier Transport (GIT)5.The mapping of Binding information between the BICC signalling entity and the DSS2 signalling entityis shown in Table 1 .Table 1Mapping of Binding InformationBICC Signalling Entity Param
29、eter(Call Control)DSS2 Signalling Entity Information Element(Bearer Control)Application Transport Parameter (BNC-ID)1Generic Identifier Transport (BNC-ID)55.2 Bearer Service InformationThis subclause defines the mapping of the bearer service information contained in the BICC USIparameter to the requ
30、ired DSS2 information elements for the support of AAL Type 1 bearerconnections.Note: BICC Codec information is not used by this report.The DSS2 information elements required for the mapping of the bearer service information are shownin Table 2 .TECHNICAL REPORT NO. 634Table 2DSS2 Information Element
31、s Required for the Mapping of Bearer Service InformationInformation ElementsUsed to DescribeNetwork Relevant BearerAttributesInformation Elements Used toDescribe Lower Layer AttributesDSS2 RelatedInformation Elements(see 4.5/Q.29314)- Broadband BearerCapability (B-BC)- ATM traffic descriptor- QoS pa
32、rameterATM adaptation layer parameters (AALparameters)Table 3 shows the mapping between the BICC USI parameter and the DSS2 broadband bearercapability information element and QoS parameter information elements. This mapping isindependent of the USI parameter codes.Table 3Mapping of the BICC USI Para
33、meter and the DSS2 Broadband BearerCapability and QoS Parameter Information ElementsBICC USI Parameter = Speech, 64kbit/s unrestricted, 3.1 kHz audio,N*64 kbit/sDSS2 Broadband Bearer Capability Information Element Contents 9Bearer classX X XBTC 7 (Note 1) 7 (Note 1)5Susceptibility to clipping Not su
34、sceptible to clippingUser plane configuration Point to pointDSS2 QoS Parameter Information Element Contents 7QoS class forward 1 (Note 2) 0 (Note 3) 0 (Note 3)QoS class backward 1 (Note 2) 0 (Note 3) 0 (Note 3)Note 1: The requested I.371 9 ATM transfer capability is DBR (see Q.2961.2 9).Note 2: The
35、requested I.356 12 QoS Class is Class 1 (stringent QoS class) (see Q.2965.17).Note 3: No specific I.356 QoS class is explicitly requested (see Q.2965.1 7).Table 4 shows the mapping between the BICC USI parameter and the DSS2 AAL parametersinformation element. The mapping is independent of the USI pa
36、rameter codes, except for the DSS2Constant Bit Rate (CBR) rate and Multiplier subfields.TECHNICAL REPORT NO. 635Table 4Mapping of the BICC USI Parameter and the DSS2 AAL Parameters InformationElementsUSI Parameter CodesSpeech, 64 kbit/sunrestricted or 3.1kHz audio384 kbit/sunrestricted1472 kbit/sunr
37、estricted1536 kbit/sunrestricted1920 kbit/sunrestricted(No proceduresspecified for USnetworks.)N*64kbit/sDSS2 AAL Parameters Information Element Contents9AAL type 1(AAL Type 1)Subtype 2(Circuit transport)CBR rate 1(64kbit/s)64(N)x64 kbit/s64(N)x64 kbit/s64(N)x64kbit/s-64N*64 kbit/sMultiplier Not app
38、licable 6 23 24 - NSource clockfrequencyrecovery method0(Null)Error correctionmethod0(Null)SDT block size(Note) 1 NPartially filledcells47(Full fill)Note: For single channel adaptation using AAL type 1, the SDT block size is set to 1. For 384 kbit/s,1472 kbit/s, 1536 kbit/s, and N*64, where N 1, the
39、 SDT block size is set to N.Table 5 shows the mapping between the BICC USI parameter and the ATM peak cell rates(CLP=0+1) signalled in the ATM traffic descriptor information element For each USI parameter code,a value for the peak cell rate is selected such that the bit rate of the corresponding N-I
40、SDN service(e.g. 64 kbit/s, Nx64 kbit/s) can be transported as the cell payload of the ATM cells, i.e. excluding theoverhead of the ATM cell and AAL type 1 header.TECHNICAL REPORT NO. 636Table 5Mapping of BICC USI Codes and ATM Peak Cell Rates in the ATM Traffic DescriptorBICC Signalling Entity DSS2
41、 Signalling Entity(Bearer Control)USI Parameter ATM Traffic DescriptorForward/Backward peakcell rate (CLP=0+1) (noOAM cells) (Note)Information TransferCapability(Octet 1, Bit 1-5)Information TransferRate(Octet 2, Bit 1-5)Rate Multiplier(Octet 2.1)PCRSpeech 64 kbit/s Not applicable 171 cells/sec3.1 K
42、Hz Audio 64 kbit/s Not applicable 171 cells/secUnrestricted DigitalInformation with Tones& Announcements (UDI-TA)64 kbit/s Not applicable 171 cells/sec64 kbit/s Not applicable 171 cells/sec384 kbit/s Not applicable 1024 cells/sec1472 kbit/s Not applicable 3926 cell/sec1536 kbit/s Not applicable 4096
43、 cells/sec2 64 kbit/s 342 cells/sec3 64 kbit/s 512 cells/sec4 64 kbit/s 683 cells/sec5 64 kbit/s 854 cells/sec6 x 64 kbit/s 1024 cells/sec7 64 kbit/s 1195 cells/sec8 64 kbit/s 1366 cells/sec9 64 kbit/s 1536 cells/sec10 64 kbit/s 1704 cells/sec11 64 kbit/s 1878 cells/sec12 64 kbit/s 2048 cells/sec13
44、64 kbit/s 2219 cells/sec14 64 kbit/s 2390 cells/sec15 64 kbit/s 2560 cells/sec16 64 kbit/s 2731 cells/sec17 64 kbit/s 2902 cells/sec18 64 kbit/s 3072cells/sec19 64 kbit/s 3243 cells/sec20 64 kbit/s 3414 cells/sec21 64 kbit/s 3584 cells/sec22 64 kbit/s 3755 cells/sec23 64 kbit/s 3926 cells/secUnrestr
45、icted DigitalInformation (UDI)Multi-Rate24 x 64 kbit/s 4096 cells/secRestricted DigitalInformation64 kbit/s. Not applicable 171 cells/secNote: No OAM cells are included in the PCR calculations.TECHNICAL REPORT NO. 6375.3 Address InformationThis subclause describes address information mapping between
46、 the BICC signalling entity and theDSS2 signalling entity. Address mapping between the BICC signalling entity and DSS2 signallingentity is shown in Table 6 .Table 6Mapping of Address InformationBICC Signalling Entity(Parameter)DSS2 Signalling Entity(Information Element)Application Transport Paramete
47、r1(T-BIWF-address)Called party number 4(T-BIWF-address)5.4 CauseThis subclause describes the mapping of cause values4,6,11between BICC call control signalling andDSS2 bearer signalling at the reference point between the BCF and CSF. Cause values related tospecific bearer operations in DSS2 are mappe
48、d to suitable bearer control related cause values inBICC. The cause value mappings apply to the case where the BCF can no longer establish ormaintain the bearer. Mapping of DSS2 connection clearing message Cause Values to BICC are onlyperformed at the ISN that set up the connection. The scope of the
49、 cause value mapping is from thebearer protocol to the generic BCF-CSF primitive interface and not directly to the BICC protocol.Table 7 identifies the Cause related information, derived from DSS2 signalling, which is passed fromthe DSS2 Signalling entity to the BICC Signalling entity via the BCF/CSF logical interface to provideCause parameter fields giving details on the circumstances of a call being cleared due to a DSS2bearer establishment failure.Table 7Mapping of Cause Inf
