1、INTERNATIONAL TELECOMMUNICATION UNIONITU-T Series QTELECOMMUNICATIONSTANDARDIZATION SECTOROF ITUSupplement 34(12/2000)SERIES Q: SWITCHING AND SIGNALLINGTechnical report TRQ.2410: Signallingrequirements capability set 1 for support of IPbearer control in BICC networksITU-T Q-series Recommendations Su
2、pplement 34(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.99CLAUSES APPLICABLE TO ITU-T
3、 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.599INTERWORKING OF SIGNALLING SYST
4、EMS 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 REQUIREMENTS AND PROT
5、OCOLS FOR IMT-2000 Q.1700Q.1799BROADBAND ISDN Q.2000Q.2999General aspects Q.2000Q.2099Signalling ATM adaptation layer (SAAL) Q.2100Q.2199Signalling network protocols Q.2200Q.2299Common aspects of B-ISDN application protocols for access signalling and network signallingand interworkingQ.2600Q.2699B-I
6、SDN application protocols for the network signalling Q.2700Q.2899B-ISDN application protocols for access signalling Q.2900Q.2999For further details, please refer to the list of ITU-T Recommendations.Q series Supplement 34 (12/2000) iSupplement 34 to ITU-T Q-series RecommendationsTechnical report TRQ
7、.2410: Signalling requirements capability set 1for support of IP bearer control in BICC networksSummaryThis Supplement to ITU-T Q-series Recommendations is a technical report on the requirements forthe Support of Narrowband Services using IP Bearer Technologies. Its scope is limited to theCapability
8、 Set 1 requirements common to the bearer control protocol for IP technology (only) for usein BICC CS-2 Networks.SourceSupplement 34 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 Supp
9、lement 34 (12/2000)FOREWORDThe International Telecommunication Union (ITU) is the United Nations 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 tarif
10、f questions and issuing Recommendationson them with a view to standardizing telecommunications 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 Recommendat
11、ions on thesetopics.The approval of ITU-T Recommendations is covered by the procedure laid down 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 ex
12、pression “Administration“ is used for conciseness to indicate both atelecommunication administration 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 Intellect
13、ual Property Right. ITU takes no position concerning the evidence, validity orapplicability of 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
14、intellectual property, protectedby patents, which may be required to implement this publication. 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 publ
15、ication may be reproduced or utilized in any form or by any means,electronic or mechanical, including photocopying and microfilm, without permission in writing from ITU.Q series Supplement 34 (12/2000) iiiCONTENTSPage1 Scope . 12 References 13 Abbreviations . 14 Definitions 25 General Requirements 2
16、6 Detailed Requirements 26.1 General. 26.1.1 Bearer Information. 26.1.2 Quality of Service 26.1.3 Connection Types supported 36.1.4 Multi-Connection Support . 36.1.5 Contention resolution. 36.1.6 Error reporting. 37 Signalling Procedures. 37.1 Bearer establishment 37.1.1 Successful Establishment of
17、a new bearer 37.1.2 Unsuccessful Establishment of a new bearer 37.2 Modification of a Bearer. 37.2.1 Successful Modification of a Bearer. 37.2.2 Unsuccessful Modification of a Bearer 47.3 Release of a Bearer. 47.4 Error Handling . 47.5 Echo Control Procedure 47.6 Reset 4Q series Supplement 34 (12/20
18、00) 1Supplement 34 to ITU-T Q-series RecommendationsTechnical report TRQ.2410: Signalling requirements capability set 1for support of IP bearer control in BICC networks1ScopeThis Supplement provides requirements for the support of services via IP bearer technologies. Itsscope is limited to the Capab
19、ility Set 1 (CS-1) requirements common to the bearer control protocolfor IP technology (only) in BICC Capability Set 2 (CS-2) Networks.2 References1 IETF RFC 1889 (1996), RTP: A Transport Protocol for Real-Time Applications.2 IETF RFC 1890 (1996), Profile for Audio and Video Conferences with Minimal
20、 Control.3 ITU-T Q-Series Supplement 16 (1999), Technical report TRQ.2140: Signallingrequirements for the support of narrowband services via broadband transport technologies.4 IETF RFC 2833 (2000), RTP Payload for DTMF Digits, Telephony Tones and TelephonySignals.5 ITU-T Q-Series Supplement 31 (2000
21、), Technical report TRQ. 2141.0: Signallingrequirements for the support of narrowband services over broadband transport technologies capability set 2 (CS-2).6 IETF RFC 2327 (1998), SDP: Session Description Protocol.3 AbbreviationsThis Supplement uses the following abbreviations:BCF Bearer Control Fu
22、nctionBICC Bearer Independent Call ControlBNC Backbone Network ConnectionBNC-ID Backbone Network Connection IdentifierCBC Call and Bearer ControlCS Capability SetCSF Call Service FunctionDTMF Dual Tone Multi-FrequencyIP Internetworking ProtocolMFC MultiFrequency CompelledQoS Quality of ServiceRFC Re
23、quest For CommentRTCP Real Time Control ProtocolRTP Real Time ProtocolTDM Time Division Multiplex2 Q series Supplement 34 (12/2000)TMR Transmission Medium RequirementUSI User Service Information4 DefinitionsSee Overall Requirements for BICC 5.5 General RequirementsTheBNC-IDneedstobeavailableatbothBC
24、F.The establishment of a bearer shall be performed by a forward flow and backward flow, bound to thecall.The signalling of information on framing control protocols is not required.The Bearer Control shall support the modification of the bearer as part of the procedures for codecmodification, if requ
25、ired. The Bearer Control shall also support the modification of the bearer as partof the procedures initiated by the underlying bearer transport.The required bandwidth is not required to be signalled horizontally in the IP bearer control. It isassumed that although the required bandwidth may be deri
26、ved from information such as the TMR,USI and Codec, this will be dealt with below the IP level.The IP bearer established for the support of narrowband services shall be capable of providing thequality of service of a TDM trunk.The transfer of bearer control information consists of one or more flows
27、between peer BCF. Thisflow shall be achieved by the transparent tunnelling of the information in the CBC (verticalinterface) and the call control.The support for the reuse of idle bearers is not applicable to IP.6 Detailed Requirements6.1 General6.1.1 Bearer InformationThe following list of bearer i
28、nformation shall be transferred between BCF as bearer information:The indication of the use of a framing protocol (e.g. RTP 1) and associated information,The profile 2.NOTE The same profile will be used in both directions.Media packetization time (optional), as defined in SDP 6.An indication for the
29、 support of in-band signalling systems (e.g. DTMF, MFC) 4.Indications for support for all tones and signals defined in 4 shall be optional.Transport end point addresses (including port numbers).6.1.2 Quality of ServiceFor connectionless bearer types, more than one method of providing quality of serv
30、ice is supported.The call control signalling interacts with the bearer control supported on a BNC type and remainsindependent of the underlying QoS mechanism.Q series Supplement 34 (12/2000) 36.1.3 Connection Types supportedThe backbone network shall support symmetric point-to-point BNC connections.
31、 In BICC CS-2Networks, a call can support only one BNC type.6.1.4 Multi-Connection SupportSupport for multiple streams in BICC CS-2 is limited to a single BNC.6.1.5 Contention resolutionBearer control is responsible for contention resolution of bearer resource allocation and collisionsduring connect
32、ion establishment and connection modification.6.1.6 Error reportingAll Types of bearer control protocols shall include mechanisms for detecting and reporting signallingprocedural errors or other failures to network management.The detection of errors in the information carried in the bearer control t
33、hat prevent the successfulestablishment of a bearer shall be reported to the call control.7 Signalling Procedures7.1 Bearer establishment7.1.1 Successful Establishment of a new bearerA bearer establishment can be initiated in either direction. A bearer is established by the exchange ofinformation be
34、tween peer BCF to open two unidirectional streams. A bearer shall be establishedonce sufficient information is received to identify the media required. Inclusion of an indication ofsupport to receive in-band events is optional. Absence or presence of such information shall notcause failure of bearer
35、 establishment.Information specifying the media packetization time of packets sent in the media streams mayoptionally be included in the IPBCP messages exchanged. If an entity that receives a media streamcannot accept the media packetization time as indicated in a message, it may abort the connectio
36、nestablishment procedure.7.1.2 Unsuccessful Establishment of a new bearerUnsuccessful set-up could be detected by bearer control and reported to the call control. The bearercontrol is only required to report the failure to establish a bearer. No explicit details on the reasonsfor failure shall be pr
37、ovided.7.2 Modification of a Bearer7.2.1 Successful Modification of a BearerThe bearer control may modify the characteristics of the bearer, based on a request from the callcontrol to modify the codec or due to bearer information such as RTCP reports. The bearer controlprotocol shall exchange inform
38、ation on the modified bearer with its peer BCF, by the transparenttunnelling of the information in the CBC (vertical interface) and the call control. Inclusion of anindication of support to receive in-band events is optional. Absence or presence of such informationshall not cause failure of bearer e
39、stablishment.Information specifying the media packetization time of packets sent in the media streams mayoptionally be included in the IPBCP messages exchanged.4 Q series Supplement 34 (12/2000)7.2.2 Unsuccessful Modification of a BearerIf a request for modification of a bearer cannot be performed (
40、e.g. due to insufficient resources), theconnection will be maintained. The requesting entity must therefore maintain its previousconfiguration. If the procedure was invoked by call control, then it must be informed of the failure.If an entity that receives a media stream cannot accept the media pack
41、etization time as indicated in amessage, it may abort the connection modification procedure.7.3 Release of a BearerThe bearer control shall release a bearer when requested by call control without any exchange ofinformation with the peer BCF. This requirement supports the simultaneous release of call
42、 andbearer.The release of a bearer by the bearer control protocol will be reported to call control.7.4 Error HandlingError handling shall be the responsibility of the bearer control protocol.7.5 Echo Control ProcedureThere are no special requirements on the protocol procedures for echo control at th
43、e bearer controllevel.7.6 ResetThe reset of bearer resources shall be handled by the bearer control.Geneva, 2001SERIES OF ITU-T RECOMMENDATIONSSeries A Organization of the work of ITU-TSeries B Means of expression: definitions, symbols, classificationSeries C General telecommunication statisticsSeri
44、es 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 Integrated
45、 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 maintenance: i
46、nternational 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 installations, local
47、 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
