1、INTERNATIONAL TELECOMMUNICATION UNIONITU-T Series QTELECOMMUNICATIONSTANDARDIZATION SECTOROF ITUSupplement 36(12/2000)SERIES Q: SWITCHING AND SIGNALLINGTechnical report TRQ.3030: Operation of thebearer independent call control (BICC) protocol(CS-2) with IP bearer control protocol (IPBCP)ITU-T Q-seri
2、es Recommendations Supplement 36(Formerly CCITT Recommendations)ITU-T Q-SERIES RECOMMENDATIONSSWITCHING AND SIGNALLINGSIGNALLING IN THE INTERNATIONAL MANUAL SERVICE Q.1Q.3INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING Q.4Q.59FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN Q.60Q.99CLAUSE
3、S APPLICABLE TO ITU-T STANDARD SYSTEMS Q.100Q.119SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4 AND No. 5 Q.120Q.249SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 Q.250Q.309SPECIFICATIONS OF SIGNALLING SYSTEM R1 Q.310Q.399SPECIFICATIONS OF SIGNALLING SYSTEM R2 Q.400Q.499DIGITAL EXCHANGES Q.500Q.599INTERWORKI
4、NG OF SIGNALLING SYSTEMS Q.600Q.699SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 Q.700Q.799Q3 INTERFACE Q.800Q.849DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 Q.850Q.999PUBLIC LAND MOBILE NETWORK Q.1000Q.1099INTERWORKING WITH SATELLITE MOBILE SYSTEMS Q.1100Q.1199INTELLIGENT NETWORK Q.1200Q.1699SIGNALLING
5、REQUIREMENTS AND PROTOCOLS FOR IMT-2000 Q.1700Q.1799BROADBAND ISDN Q.2000Q.2999For further details, please refer to the list of ITU-T Recommendations.Q series Supplement 36 (12/2000) iSupplement 36 to ITU-T Q-series RecommendationsTechnical report TRQ.3030: Operation of the bearer independent call c
6、ontrol(BICC) protocol (CS-2) with IP bearer control protocol (IPBCP)SummaryThis Supplement to ITU-T Recommendation Q.1902 describes the general aspects of the operationof the Bearer Independent Call Control (BICC) protocol Capability Set 2 (CS-2) with IP BearerControl Protocol, used to control IP Be
7、arer Connections.SourceSupplement 36 to ITU-T Q-series Recommendations was prepared by ITU-T Study Group 11(2001-2004) and approved under the WTSA Resolution 5 procedure on 6 December 2000.ii Q series Supplement 36 (12/2000)FOREWORDThe International Telecommunication Union (ITU) is the United Nation
8、s specialized agency in the field oftelecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ ofITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendationson them with a view to standardizing telecommunications
9、on a worldwide basis.The World Telecommunication Standardization Assembly (WTSA), which meets every four years,establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on thesetopics.The approval of ITU-T Recommendations is covered by the procedure laid down
10、 in WTSA Resolution 1.In some areas of information technology which fall within ITU-Ts purview, the necessary standards areprepared on a collaborative basis with ISO and IEC.NOTEIn this publication, the expression “Administration“ is used for conciseness to indicate both atelecommunication administr
11、ation and a recognized operating agency.INTELLECTUAL PROPERTY RIGHTS ITU draws attention to the possibility that the practice or implementation of this publication may involve theuse of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity orapplicability of
12、claimed Intellectual Property Rights, whether asserted by ITU members or others outside ofthe publication development process.As of the date of approval of this publication, ITU had not received notice of intellectual property, protectedby patents, which may be required to implement this publication
13、. However, implementors are cautioned thatthis may not represent the latest information and are therefore strongly urged to consult the TSB patentdatabase. ITU 2001All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means,electronic or mechanical, inc
14、luding photocopying and microfilm, without permission in writing from ITU.Q series Supplement 36 (12/2000) iiiCONTENTSPage1 Scope . 12 References 13 Definitions 24 Abbreviations . 25 Information exchanged between BICC and IPBCP Signalling Entities 35.1 Channel Attributes 35.1.1 Codec Information. 35
15、.1.2 Transmission Medium Requirements. 45.2 Addressing . 45.3 Binding Information . 45.4 Cause . 4Q series Supplement 36 (12/2000) 1Supplement 36 to ITU-T Q-series RecommendationsTechnical report TRQ.3030: Operation of the bearer independent call control(BICC) protocol (CS-2) with IP bearer control
16、protocol (IPBCP)1ScopeThis Supplement contains information relevant to the operation of the Bearer Independent CallControl (BICC) Protocol Capability Set 2 (CS-2) 6 and 7, with the IP Bearer Control Protocol8.Information which is relevant to be passed between the BICC 6 and 7 signalling entity and t
17、heIPBCP 8 signalling entity is identified. The dashed box of Figure 1 shows the scope of thisSupplement. Interaction with layer management is outside the scope of this Supplement.NOTE The handling of reuse of idle bearer connections is outside the scope of the present Supplement.T11112920-01BICCSign
18、allingSAPprimitivesLayerManagementBICC signalling PDUsCSFBCFScope of this SupplementIPBCP signalling PDUsSAPprimitivesIPBCPSignallingIP Service End PointFigure 1 Scope of this Supplement2 References1 ITU-T H.248 (2000), Gateway control protocol.2 IETF RFC 2327 (1998), SDP: Session Description Protoc
19、ol.3 IETF RFC 1890 (1996), RTP Profile for Audio and Video Conferences with MinimalControl.4 ITU-T X.200 (1994), Information technology Open Systems Interconnection BasicReference Model: The basic model.5 ITU-T X.210 (1993), Information technology Open Systems Interconnection BasicReference Model: C
20、onventions for the definition of OSI services.6 ITU-T Q.765.5 (2000), Signalling system No. 7 Application transport mechanism: Bearerindependent call control (BICC).2 Q series Supplement 36 (12/2000)7 ITU-T Q.1902.x, Bearer Independent Call Control (CS-2).8 ITU-T Q.1970 (2001), BICC IP Bearer Contro
21、l Protocol.9 IETF RFC 1889 (1996), RTP: A Transport Protocol for Real-Time Applications.10 ITU-T G.711 (1988), Pulse code modulation (PCM) of voice frequencies.11 ITU-T G.722 (1988), 7 kHz audio-coding within 64 kbit/s.12 ITU-T G.723.1 (1996), Dual rate speech coder for multimedia communications tra
22、nsmittingat 5.3 and 6.3 kbit/s.13 ITU-T G.726 (1990), 40, 32, 24, 16 kbit/s adaptive differential pulse code modulation(ADPCM).14 ITU-T G.727 (1990), 5, 4, 3 and 2-bit sample embedded adaptive differential pulse codemodulation (ADPCM).15 ITU-T G.728 (1992), Coding of speech at 16 kbit/s using low-de
23、lay code excited linearprediction.16 ITU-T G.729 (1996), Coding of speech at 8 kbit/s using conjugate-structure algebraic-code-excited linear-prediction (CS-ACELP).17 ITU-T H.221 (1999), Frame structure for a 64 to 1920 kbit/s channel in audiovisualteleservices.18 ITU-T Q.763 (1999), Signalling syst
24、em No.7 ISDN user part formats and codes.19 ITU-T Q.850 (1998), Usage of cause and location in the digital subscriber signalling systemNo. 1 and the signalling system No. 7 ISDN user part.3 DefinitionsNo definitions are introduced for the purpose of this Supplement.4 AbbreviationsThis Supplement use
25、s the following abbreviations:AVP Audio/Video ProfileBCF Bearer Control FunctionBICC Bearer Independent Call ControlCSF Call Server FunctionCS-2 Capability Set 2IP Internet ProtocolIPBCP IP Bearer Control ProtocolPDU Protocol Data UnitRTP Real Time ProtocolSAP Service Access PointSDP Session Descrip
26、tion ProtocolQ series Supplement 36 (12/2000) 35 Information exchanged between BICC and IPBCP Signalling EntitiesIt is assumed that the format of information passed between the BICC 6 and 7 entity and theIPBCP 8 entity is the same as the format of information passed between two peer BICC 6 and 7enti
27、ties. No primitives are defined for this interfaceThe following clauses list the information passed between the BICC 6 and 7 and IPBCP8Signalling Entities. The relevant information relates to:1) Channel Attributes;2) Addressing;3) Binding Information; and4) Cause.5.1 Channel AttributesTable 1 identi
28、fies the Channel Attributes related information passed from the BICC entity to theIPBCP Signalling entity which are applicable to derive the IP Bearer Control Parameters needed tocontrol the establishment of the IPBCP bearer.Table 1 Mapping of Channel AttributesBICC Signalling Entity 6 and 7 IPBCP S
29、ignalling Entity 8Codec Information (Note), orTransmission Medium Requirements (User ServiceInformation) (Note)SDP Payload (m = audio RTP/AVP)NOTE Codec Information is used if present, otherwise the Transmission Medium Requirements areused. When Transmission Medium Requirements equals Speech or 3.1
30、kHz Audio, then the User ServiceInformation, u/A law indication may also be examined5.1.1 Codec InformationTable 2 identifies the Codec type information passed from the BICC entity to the IPBCP Signallingentity which are applicable to derive the RTP/AVP Payload Type which may be used to control thee
31、stablishment of the IPBCP bearer.Table 2 Mapping of Codec Type to RTP/AVP Payload TypeBICC Signalling Entity 6 and 7Codec TypeIPBCP Signalling Entity 8Payload Type 2 and 3G.711 64 kbit/s A-law 8G.711 64 kbit/s -law 0G.711 56 kbit/s A-law Not supportedG.711 56 kbit/s -law Not supportedG.722 (SB-ADPCM
32、) 9G.723.1 Not supportedAnnex A/G.723.1 (silence suppression) Not supportedG.726 (ADPCM) Not supportedG.727 (Embedded ADPCM) Not supportedG.728 154 Q series Supplement 36 (12/2000)Table 2 Mapping of Codec Type to RTP/AVP Payload Type (continued)BICC Signalling Entity 6 and 7Codec TypeIPBCP Signallin
33、g Entity 8Payload Type 2 and 3G.729 (CS-ACELP) Not supportedAnnex B/G.729 (silence suppression) Not supportedNOTE The IETF continues to develop new RTP payload type definitions. Therefore for the codecsindicated as “not supported“ in the table above, approved RFCs may exist in the future defining RT
34、Ppayload types for these codecs.5.1.2 Transmission Medium RequirementsTable 3 identifies the Transmission Medium Requirements information passed from the BICC entityto the IPBCP Signalling entity which are applicable to derive the RTP/AVP Payload Type whichmay be used to control the establishment of
35、 the IPBCP bearer. This mapping applies only if Codectype information is not available.Table 3 Mapping of Transmission Medium Requirementsto RTP/AVP Payload TypeBICC Signalling Entity 6 and 7 TransmissionMedium Requirements 19IPBCP Signalling Entity 8Payload Type 2 and 364 kbit/s unrestricted Not su
36、pported64 kbit/s unrestricted preferred 93.1 kHz audio 0 or 8 (Note 1)Speech 0 or 8 (Note 2)2 64 Not supported384 Not supported1536 Not supported1920 Not supportedMultirate (64 kbit/s base rate)1n31Not supportedNOTE 1 Knowledge of u/A law PCM (payload types 0/8) is based on User Service Information
37、(ifpresent), otherwise on network configuration data.NOTE 2 Knowledge of u/A law PCM (payload types 0/8) is based on User Service Information.5.2 AddressingAddressing related information is not passed between the BICC entity and the IPBCP Signallingentity, as the IPBCP is tunneled via H.248 1 (if ap
38、plicable) and BICC 6 and 7.5.3 Binding InformationBinding related information is not passed between the BICC entity and the IPBCP Signalling entity,as the IP bearer control protocol is tunneled via H.248 1 (if applicable) and BICC 6 and 7.5.4 CauseTable 4 identifies the Cause related information, de
39、rived from the IPBCP signalling, which is passedfrom the IPBCP Signalling entity to the BICC entity to provide the Cause parameter fields givingdetails on the circumstances of a call being cleared due to an IPBCP bearer establishment failure.Q series Supplement 36 (12/2000) 5Table 4 Mapping of Cause
40、(IPBCP Signalling Entity to BICC Signalling Entity)IPBCP Signalling Entity 8 Result = Rejected BICC Signalling Entity 7 Cause IndicatorsNOTE Location does not exist in IPBCPsignalling.Location 19 = network beyond interworkingpoint (BI)NOTE Coding Standard does not exist in IPBCPsignalling.Coding Sta
41、ndard 19 = ITU-T standardized codingNOTE Cause value does not exist in IPBCPsignallingCause value 19 (refer Table 5)Table 5 identifies the mapping of information received in the IPBCP Signalling, when the resultequals rejected and passed by the IPBCP signalling entity to the BICC signalling entity.T
42、able 5 Generation of Cause values (IPBCP Signalling to BICC)IPBCP Signalling Entity 8 BICC Signalling Entity 7 Cause value 19Rejected Message 47 Resource unavailable, unspecifiedConfused Message 127 Interworking, unspecifiedThere is no Cause related information passed from the BICC entity to the IPB
43、CP Signalling entity,as there is no explicit IPBCP clearing procedure as a result of the call being cleared.Geneva, 2001SERIES OF ITU-T RECOMMENDATIONSSeries A Organization of the work of ITU-TSeries B Means of expression: definitions, symbols, classificationSeries C General telecommunication statis
44、ticsSeries D General tariff principlesSeries E Overall network operation, telephone service, service operation and human factorsSeries F Non-telephone telecommunication servicesSeries G Transmission systems and media, digital systems and networksSeries H Audiovisual and multimedia systemsSeries I In
45、tegrated services digital networkSeries J Cable networks and transmission of television, sound programme and other multimedia signalsSeries K Protection against interferenceSeries L Construction, installation and protection of cables and other elements of outside plantSeries M TMN and network mainte
46、nance: international transmission systems, telephone circuits,telegraphy, facsimile and leased circuitsSeries N Maintenance: international sound programme and television transmission circuitsSeries O Specifications of measuring equipmentSeries P Telephone transmission quality, telephone installation
47、s, local line networksSeries Q Switching and signallingSeries R Telegraph transmissionSeries S Telegraph services terminal equipmentSeries T Terminals for telematic servicesSeries U Telegraph switchingSeries V Data communication over the telephone networkSeries X Data networks and open system communicationsSeries Y Global information infrastructure and Internet protocol aspectsSeries Z Languages and general software aspects for telecommunication systems
