ATIS T1 TR 65-2000 Operation of the Bearer Independent Call Control (BICC) Protocol with Broadband Integrated Services Digital Network User Part (B-ISUP) for AAL Type 1 Adaptation.pdf

1、Technical Report No. 65November 2000Operation of the Bearer IndependentCall Control (BICC) Protocol withBroadband Integrated ServicesDigital Network User Part (B-ISUP)for AAL Type 1 AdaptationPrepared by T1S1.3Working Group onCommon, Channel SignalingProblem Solvers to the Telecommunications Industr

2、yCopyright 2000 by Alliance for Telecommunications Industry SolutionsAll 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 for

3、m,in an electronic retrieval system or otherwise, without theprior written permission of the publisher.A Technical Report onOperation of the Bearer Independent Call Control (BICC)Protocol with Broadband Integrated Services DigitalNetwork User Part (B-ISUP) for AAL Type 1AdaptationDocument T1S1.3/200

4、0-162Prepared byT1S1.3 Working Group onCommon Channel Signaling- i -Table of ContentsSummary 11 Scope 12 References 13 Definitions 24 Abbreviations. 25 Mapping Functions between BICC Signaling Entity and B-ISUP Signaling Entity. 35.1 Binding Information 35.2 Bearer Service Information 35.3 Address I

5、nformation. 85.4 Cause Information 8- ii -Table of FiguresFigure 1 - Scope of this Report. 1- iii -Table of TablesTable 1 - Mapping of Binding Information 3Table 2 - B-ISUP Parameters Required for the Mapping of Bearer Service Information 3Table 3 - Mapping of the BICC USI Parameter and B-ISUP Broad

6、band Bearer Capability and QoSParameters. 5Table 4 - Mapping of the BICC USI Parameter and B-ISUP AAL Parameters Parameter 6Table 5 - Mapping of BICC USI Codes and ATM Peak Cell Rates in the ATM Cell Rate Parameter . 7Table 6 - Mapping of Address Information 8Table 7 - Mapping of Cause Information (

7、B-ISUP Signaling Entity to the BCF/CSF Logical Interface) 8Table 8 - Mapping of B-ISUP Signaling Entity Cause Values to BICC Cause Categories 9Table 9 - Mapping of Cause Information (BCF/CSF Logical Interface to B-ISUP Signaling Entity) 10- iv -ForewordThis Technical Report (TR) describes the genera

8、l aspects of the operation of the Bearer IndependentCall Control (BICC) protocol with Broadband Integrated Services Digital Network (B-ISDN) User Part (B-ISUP) protocol, Capability Set 1 (CS 1), used to control AAL type 1 bearer connections.Footnotes and informative annexes are not officially part o

9、f this TR.Future control of this TR will reside with Alliance for Telecommunications Industry Solutions.Suggestions for improvement of this specification will be welcome. These should be sent to the Alliancefor Telecommunications Industry Solutions, T1 Secretariat, 1200 G Street, NW, Suite 500, Wash

10、ingtonDC 20005.This TR was processed and approved for submittal to ATIS by the Accredited Standards Committee onTelecommunications, T1. Committee approval of this specification does not necessarily imply that allCommittee members voted for its approval.Working Group T1S1.3 developed this TR. Over th

11、e course of its development the following individualsparticipated in the Working Groups discussions and made significant contributions to the report:Wesley Downum, T1S1.3 Working Group ChairStuart Goldman, T1S1.3 Working Group Vice ChairViqar Shaikh, EditorStuart GoldmanKevin HagerMike PierceJaney C

12、heuKoan S. ChongMartin DollyTung-Hai HsiaoDonna ImrichDoris LebovitsHans OudmaerA. J. Moore, Jr.Stewart PatchDan GreeneChip SharpDick BobilinDon ChoiKeith BronleyLinda TroyBruce NorthcoteM. I. McLoughlinMichael CollisonChris VitalosMark HosfordDawn BenedettoRolfe BuhrkeJim CalmeJulie FedericoLarry F

13、orniPatti McCalmontMichael McGrewCheryl TothAl VarneyRobert B. WallerTom WalshJohn BoalRanga DendiYatendra PathakDick WeadonNick AndreCarolyn TaylorHui FengKhalid AhmadRiad HartaniGhassem KoleyniOmayma MoharramRoderick WilsonDavid WhitefordGregory WrightMichael ZeugTuan A. PhamEliot RosenGlenn Sisso

14、nDave VanderMeidenGeorge AllenJohn RoquetB. SambasivanMike TisikerJim LordJason TorreyWesley DownumJim GarrahanJay HiltonZhi-Wei LinSelvam RengasamiNiranjan SandesaraRay P. SinghJoanie CardonSteve ShowellFarshid MohammadiGreg RattaStan WainbergTECHNICAL REPORT NO. 65- 1 -SummaryThis report describes

15、 the general aspects of the Operation of the Bearer Independent Call Control(BICC) Protocol with Broadband Integrated Services Digital Network (B-ISDN) User Part (B-ISUP) forAAL Type 1 Adaptation.1 ScopeThis report contains information relevant to the operation of the Bearer Independent Call Control

16、 (BICC)protocol with the B-ISUP signaling protocol used for the control of AAL Type 1 bearer connections.Information which is relevant to be passed between the BICC signaling entity and B-ISUP signalingentity is identified. The dashed box of Figure 1 shows the scope of this report. Interaction with

17、the layermanagement is outside the scope of this report.BICC Signaling PDUsBICCSignalingB-ISUPSignalingScope of this reportB-ISUP ServiceEnd PointB-ISUP Signaling PDUsSAPprimitivesSAPprimitivesLayerManagementBCFCSFFigure 1Scope of this Report2 ReferencesThe following is a list of informative referen

18、ces:A “|” indicates a change from the ITU-T Technical Report TRQ.3020 (1999). Strictly editorial changes are notshown.TECHNICAL REPORT NO. 65- 2 -1. T1.672-2000, Bearer Independent Call Control (BICC)2. T1.648-1995, Broadband Integrated Services Digital Network (B-ISDN) Signaling System No. 7 B-ISDN

19、 User Part (B-ISUP)3. ITU-T Recommendation I.363.1, B-ISDN ATM Adaptation Layer Specification: Type 1 AAL4. ITU-T Recommendation Q.2726.4, Application Generated Identifiers5. T1.113-2000, Signaling System No.7 ISDN User Part (ISUP)6. ITU-T Recommendation I.371, Traffic Control and Congestion Control

20、 in B-ISDN7. ITU-T Recommendation Q.2610, Use of Cause and Location in the DSS2 and the B-ISDN UserPart8. ITU-T Recommendation X.200, Information Technology Open System Interconnection BasicReference Model: The Basic Model9. ITU-T Recommendation X.210, Information Technology Open System Interconnect

21、ion BasicModel: Convention for the Definition of OSI Services10. ITU-T Recommendation Q.2961.2, Support of ATM Transfer Capability in the Broadband BearerCapability Information Element11. ITU-T Recommendation Q.2965.1, B-ISDN Digital Subscriber Signaling System No. 2 Support ofQuality of Service Cla

22、sses12. ITU-T Recommendation I.356, B-ISDN ATM layer cell transfer performance3 DefinitionsNo new definitions are needed.4 AbbreviationsAAL ATM Adaptation LayerATM Asynchronous Transfer ModeBCF Bearer Control FunctionBICC Bearer Independent Call ControlB-ISDN Broadband Integrated Services Digital Ne

23、tworkB-ISUP Broadband ISDN User PartBIWF Bearer Interworking FunctionBNC-ID Backbone Network Connection IdentifierBTC Broadband Transfer CapabilityCBR Constant Bit RateCLP Cell Loss PriorityCSF Call Service FunctionCS 1 Capability Set 1DBR Deterministic Bit RateIAM Initial Address MessageISN Interfa

24、ce Serving NodeN-ISDN Narrowband Integrated Services Digital NetworkOAM Operations, Administration, and MaintenancePCR Peak Cell RateSDT Structured Data TransferQoS Quality of ServiceT-BIWF Terminating Bearer Interworking FunctionUSI User Service InformationUDI Unrestricted Digital InformationUDI-TA

25、 Unrestricted Digital Information with Tones & AnnouncementTECHNICAL REPORT NO. 65- 3 -5 Mapping Functions Between BICC Signaling Entity and B-ISUP Signaling EntityThe following subclauses list the information passed between the BICC signaling entity and B-ISUPsignaling entity:1) Binding information

26、,2) Bearer service information,3) Address information, and4) Cause information.The mapping reflected in the tables of this clause show the parameter names followed by theinformation contents in parentheses.The originating BIWF is always viewed as an originating exchange in the context of the B-ISUPs

27、tandards. Similarly, the terminating BIWF is always viewed as a destination exchange.5.1 Binding InformationBinding information is used to associate the call control signaling and bearer control signaling for theestablishment of an AAL Type 1 bearer connection. The Backbone Network Connection Identi

28、fier(BNC-ID) is carried by the call control in the Application transport parameter. The BNC-ID is carried bybearer control in the Application generated identifiers parameter.The mapping of the binding information between BICC signaling entity and B-ISUP signaling entity isshown in Table 1.Table 1Map

29、ping of Binding InformationBICC Signaling Entity(Parameter)B-ISUP Signaling Entity(Parameter)Application transport parameter (BNC-ID) Application generated identifiers (BNC-ID)5.2 Bearer Service InformationThis subclause defines the mapping of the bearer service information contained in the BICC USI

30、parameter to the required B-ISUP parameters for the support of AAL Type 1 bearer connections.Note - BICC codec information is not used by this report.The B-ISUP parameters required for the mapping of the bearer service information are shown in Table2.Table 2B-ISUP Parameters Required for the Mapping

31、 of Bearer Service InformationParameters Used to DescribeNetwork Relevant BearerAttributesParameters Used to DescribeLower Layer AttributesTECHNICAL REPORT NO. 65- 4 -B-ISUP RelatedParameters (seeANSI T1.648.3)- Broadband bearer capability- ATM cell rate- QoS parameterATM adaptation layer parameters

32、(AAL parameters)Table 3 shows the mapping between the BICC USI parameter and the B-ISUP Broadband bearercapability parameter and QoS parameter. This mapping is independent of the USI parameter codes.Table 4 shows the mapping between the BICC USI parameter and B-ISUP AAL parameters parameter.The mapp

33、ing is independent of the USI parameter codes, except for the B-ISUP Constant Bit Rate(CBR) and Multiplier subfields.Table 5 shows the mapping between the BICC USI parameter and the ATM peak cell rates (CLP=0+1)signaled in the ATM cell rate parameter. For each USI parameter code, a value for the pea

34、k cell rate isselected such that the bit rate of the corresponding N-ISDN service (e.g., 64 kbit/s, Nx64 kbit/s) can betransported as the cell payload of the ATM cells, i.e., excluding the overhead of the ATM cell and AALType 1 header.TECHNICAL REPORT NO. 65- 5 -Table 3Mapping of the BICC USI Parame

35、ter and B-ISUP Broadband Bearer Capability and QoSParametersBICC USI Parameter = Speech, 64kbit/s Unrestricted, 3.1 kHz Audio,N*64 kbit/sB-ISUP Broadband Bearer Capability Parameter ContentsBearer ClassXX XBTC 7 (Note 1) 7 (Note 1)5Susceptibility to Clipping Not susceptible to clippingUser Plane Con

36、figuration Point-to-pointB-ISUP QoS Parameter ContentsQoS 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 ATM transfer capability is DBR (see Q.2961.2).Note 2 The requested I.356 QoS Class is Class 1 (stringent QoS class) (s

37、ee Q.2965.1).Note 3 No specific I.356 QoS class is explicitly requested (see Q.2965.1).TECHNICAL REPORT NO. 65- 6 -Table 4Mapping of the BICC USI Parameter and B-ISUP AAL Parameters ParameterUSI Parameter CodesSpeech, 64 kbit/sunrestricted or 3.1kHz audio384 kbit/sunrestricted1472 kbit/sunrestricted

38、1536 kbit/sunrestricted1920 kbit/sunrestricted(No proceduresspecified forUS networks.)N*64kbit/sB-ISUP AAL Parameters Parameter ContentsAAL 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 applicable 6 23 24 -

39、 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 N1, the SDT block size i

40、s set to N.TECHNICAL REPORT NO. 65- 7 -Table 5Mapping of BICC USI Codes and ATM Peak Cell Rates in the ATM Cell Rate ParameterBICC Signaling Entity B-ISUP Signaling EntityUSI ATM Cell RateForward/Backward Peak CellRate (CLP=0+1) (no OAM cells)(Note)Information TransferCapability(Octet 1, Bits 1-5)In

41、formationTransfer Rate(Octet 2, Bits1-5)Rate Multiplier(Octet 2.1)PCRSpeech 64 kbit/s Not applicable 171 cells/sec3.1 KHz 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 ce

42、lls/sec384 kbit/s Not applicable 1024 cells/sec1472 kbit/s Not applicable 3926 cell/sec1536 kbit/s Not applicable 4096 cells/sec2 342 cells/sec3 512 cells/sec4 683 cells/sec5 854 cells/sec6 1024 cells/sec7 1195 cells/sec8 1366 cells/sec9 1536 cells/sec10 1704 cells/sec11 1878 cells/sec12 2048 cells/

43、sec13 2219 cells/sec14 2390 cells/sec15 2560 cells/sec16 2731 cells/sec17 2902 cells/sec18 3072 cells/sec19 3243 cells/sec20 3414 cells/sec21 3584 cells/sec22 3755 cells/sec23 3926 cells/secUnrestricted DigitalInformation (UDI)Multi-Rate24 4096 cells/secRestricted DigitalInformation64 kbit/s. Not ap

44、plicable 171 cells/secNote - No OAM cells are included in the PCR calculations.TECHNICAL REPORT NO. 65- 8 -5.3 Address InformationThis subclause describes address information mapping between BICC signaling entity and B-ISUPsignaling entity. Address mapping between BICC signaling entity and B-ISUP si

45、gnaling entity is shownin Table 6.Table 6Mapping of Address InformationBICC Signaling Entity(Parameter)B-ISUP Signaling Entity(Parameter)Application transport parameter (T-BIWF-address)Called party number and/orAESA for called party (T-BIWF-address)5.4 Cause InformationThis subclause describes the m

46、apping of cause valuesbetween BICC call control signaling and B-ISUPbearer control signaling at the interface between the BCF and CSF. Cause values related to specificbearer operations in B-ISUP are mapped to suitable bearer control related cause values in BICC. Thecause value mappings apply to the

47、case where the BCF can no longer establish or maintain the bearer.Mapping of B-ISUP connection clearing message cause values to BICC are only performed at the ISNthat set up the connection. The scope of the cause value mapping is from the bearer protocol to thegeneric BCF-CSF primitive interface and

48、 not directly to the BICC protocol.Table 7 identifies the Cause related information, derived from B-ISUP signaling, which is passed fromthe B-ISUP signaling entity to the BICC signaling entity via the BCF/CSF logical interface to provideCause indicators parameter fields giving details on the circums

49、tances of a call being cleared due to a B-ISUP bearer establishment failure.Table 7Mapping of Cause Information (B-ISUP Signaling Entity to the BCF/CSF LogicalInterface)B-ISUP Signaling Entity CauseIndicatorsBCF/CSF Logical Interface CauseCategoryCoding standardCause value (see Table 8)Cause category (see Table 8) (Note)Location and diagnostic No mappingNote If a BCF/CSF logical cause category is received and a BICC cause value needs to be generated,the BICC cause value #47 “resource unavailable, unspecified” is used.Table 8, identifies the mapping of the cause value