1、 INTERNATIONAL TELECOMMUNICATION UNION ITU-T Series QTELECOMMUNICATION STANDARDIZATION SECTOR OF ITU Supplement 32(11/2002) SERIES Q: SWITCHING AND SIGNALLING Technical Report TRQ.2141.1: Signalling requirements for the support of narrowband services via broadband transport technologies CS-2 signall
2、ing flows ITU-T Q-series Recommendations Supplement 32 ITU-T Q-SERIES RECOMMENDATIONS SWITCHING AND SIGNALLING SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE Q.1Q.3 INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING Q.4Q.59 FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN Q.60Q.99 CLAUSES AP
3、PLICABLE TO ITU-T STANDARD SYSTEMS Q.100Q.119 SPECIFICATIONS OF SIGNALLING SYSTEM No. 4 Q.120Q.139 SPECIFICATIONS OF SIGNALLING SYSTEM No. 5 Q.140Q.199 SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 Q.250Q.309 SPECIFICATIONS OF SIGNALLING SYSTEM R1 Q.310Q.399 SPECIFICATIONS OF SIGNALLING SYSTEM R2 Q.400Q
4、.499 DIGITAL EXCHANGES Q.500Q.599 INTERWORKING OF SIGNALLING SYSTEMS Q.600Q.699 SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 Q.700Q.799 Q3 INTERFACE Q.800Q.849 DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 Q.850Q.999 PUBLIC LAND MOBILE NETWORK Q.1000Q.1099 INTERWORKING WITH SATELLITE MOBILE SYSTEMS Q.1100
5、Q.1199 INTELLIGENT NETWORK Q.1200Q.1699 SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 Q.1700Q.1799 SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) Q.1900Q.1999 BROADBAND ISDN Q.2000Q.2999 For further details, please refer to the list of ITU-T Recommendations. Q se
6、ries Supplement 32 (11/2002) i Supplement 32 to ITU-T Q-series Recommendations Technical Report TRQ.2141.1: Signalling requirements for the support of narrowband services via broadband transport technologies CS-2 signalling flows Summary This Supplement to ITU-T Q-series Recommendations is a technic
7、al report on the procedures, information flows and information elements needed for supporting CS-2 signalling requirement flows for the support of narrowband services via broadband transport technologies. Its scope is limited to functionality of the Serving Node and Call Mediation Node, and the asso
8、ciated protocols at the call control, bearer control, and call-bearer control levels needed for Capability Set 2. Source Supplement 32 to ITU-T Q-series Recommendations was revised by ITU-T Study Group 11 (2001-2004) and approved under ITU-T Recommendation A.13 (10/2000) procedure on 22 November 200
9、2. ii Q series Supplement 32 (11/2002) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technic
10、al, operating and tariff questions and issuing Recommendations on 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
11、 turn, produce Recommendations on these topics. 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 are prepared on a collaborative basis with ISO and IEC.
12、NOTE In this publication, the expression “Administration“ is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. INTELLECTUAL PROPERTY RIGHTS ITU draws attention to the possibility that the practice or implementation of this publication may inv
13、olve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the publication development process. As of the date of approval of this public
14、ation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this publication. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. ITU 2003
15、 All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. Q series Supplement 32 (11/2002) iii CONTENTS Page 1 Scope 1 1.1 Functional reference model 1 2 References. 1 3 Definitions 3 3.1 Functional model definitions 3
16、3.2 Definition of signalling flow objects 5 4 Abbreviations 6 5 Backbone network signalling flows . 7 5.1 Object reference model. 7 5.2 Definitions 8 5.3 Backbone network establishment. 20 5.4 Call modification flows 74 5.5 Call release . 122 5.6 Bearer release . 128 Annex A Composite structured AAL
17、 1 signalling flows 131 A.1 Changes to “Backward Backbone Network Establishment Composite Flow“ procedures necessary to support structured AAL 1 bearers 132 A.2 Changes to the “Forward Composite“ flows necessary to support structured AAL 1 bearers . 139 Annex B ISUP “NNI“ access establishment and re
18、lease flows 149 Annex C Overview of bearer redirection 154 C.1 Bearer redirection . 154 C.2 Redirection Schema 159 Annex D Overview of “Tunnelling“ . 160 D.1 Introduction 160 D.2 Operation of the mechanism. 160 Q series Supplement 32 (11/2002) 1 Supplement 32 to ITU-T Q-series Recommendations Techni
19、cal Report TRQ.2141.1: Signalling requirements for the support of narrowband services via broadband transport technologies CS-2 signalling flows 1 Scope This Supplement provides signalling flows for the support of BICC CS-2 signalling requirements for the support of narrowband services via broadband
20、 transport technologies. 1.1 Functional reference model Figure 1 shows the composition of the functional reference model. Refer to clause 3 for the definition of each of the functional entities. The signalling network will be used for the transport of the call control signalling. The interface from
21、the existing network will be N-ISUP. 2 References 1 ITU-T Recommendation Q.115 (1999), Logic for the control of echo control devices. 2 ITU-T Recommendation Q.761 (1999), Signalling System No. 7 ISDN user part functional description. 3 ITU-T Recommendation Q.762 (1999), Signalling System No. 7 ISDN
22、user part general functions of messages and signals. 4 ITU-T Recommendation Q.763 (1999), Signalling System No. 7 ISDN user part formats and codes. 5 ITU-T Recommendation Q.764 (1999), Signalling System No. 7 ISDN user part signalling procedures. 6 ITU-T Recommendation Q.766 (1993), Performance obje
23、ctives in the integrated services digital network application. 7 ITU-T Recommendation Q.701 (1993), Functional description of the message transfer part (MTP) of Signalling System No. 7. 8 ITU-T Recommendation Q.702 (1988), Signalling data link. 9 ITU-T Recommendation Q.703 (1996), Signalling link. 1
24、0 ITU-T Recommendation Q.704 (1996), Signalling network functions and messages. 11 ITU-T Recommendation Q.706 (1993), Message transfer part signalling performance. 12 ITU-T Recommendation Q.765 (2000), Signalling System No. 7 Application transport mechanism. 13 ITU-T Recommendation Q.2210 (1996), Me
25、ssage transfer part level 3 functions and messages using the services of ITU-T Recommendation Q.2140. 14 ITU-T Recommendation Q.2140 (1995), B-ISDN ATM adaptation layer Service specific coordination function for signalling at the network node interface (SSCF at NNI). 15 ITU-T Recommendation H.248.1
26、(2002), Gateway control protocol: Version 2. 2 Q series Supplement 32 (11/2002) T11114930-01ISN-ATETETETETSN-x GSN-x GSN-yCSF-N CSF-T CSF-G CSF-G CSF-CCMN-xCSF-CISN-BCSF-RACN-EBCF-A(a)BCF-RBCF-N(z)BCF-RBCF-JBCF-G(y)BCF-G(x)BCF-RBCF-T(w)BCF-RBCF-N(v)Network bearer connection (end to end) Figure 1 Com
27、posite functional reference modelBackbone network connectionsSignalling transport networkOtherservicesuppliernetworksScope of signalling requirementsBearerInterworkingFunction(BIWF)Backbone network connection linkAccess controlsignallingCall BCF-G, BCF-J, BCF-N, BCF-R and BCF-T. The Bearer Control G
28、ateway Function (BCF-G) provides the control of the bearer switching function, the communication capability with its associated call service function (CSF-G), and the signalling capability necessary to establish and release of the backbone network connection. The Bearer Control Joint Function (BCF-J
29、) provides the control of the bearer switching function, the communication capability with two associated call service functions (CSF), and the signalling capability necessary to establish and release the backbone network connection. The Bearer Control Nodal Function (BCF-N) provides the control of
30、the bearer switching function, the communication capability with its associated call service function (CSF), and the signalling capability necessary to establish and release of the backbone network connection to its peer (BCF-N). The Bearer Control Relay Function (BCF-R) provides the control of the
31、bearer switching function and relays the bearer control signalling requests to next BCF in order to complete the edge to edge backbone network connection The Bearer Control Transit Function (BCF-T) provides the control of the bearer switching function, the communication capability with its associate
32、d call service function (CSF-T), and the signalling capability necessary to establish and release of the backbone network connection. 3.1.4 Bearer Control Segment (BCS): Represents the signalling relationship between two adjacent Bearer Control Functional entities (BCF). 3.1.5 Bearer InterWorking Fu
33、nction (BIWF): A functional entity which provides bearer control and media mapping/switching functions within the scope of a Serving Node (ISN, TSN or GSN). A BIWF contains one Bearer Control Nodal Function (BCF-N, BCF-T or BCF-G) and one or more MCF and MMSF, and is functionally equivalent to a Med
34、ia Gateway that incorporates bearer control. See General Requirements documents for the definitions for MCF and MMSF. 3.1.6 Call Control Association (CCA): Defines the peer-to-peer signalling association between Call, and Call Empty (i.e. no AuditToken); Events; Media; Modem; Mux; Packages; Signals.
35、 4) Bearer Information Transport: carries the tunnelled Bearer Control information. 5) Bearer Service Characteristics: identifies the user requested bearer service to be provided by the network. It is used by the BIWF to condition the bearer termination. 6) BIWF Address (T-BIWF-Addr): the address on
36、 which the BNC is terminated. Passed from the terminating BIWF to the CSF and through the BICC horizontal. 7) BIWF Control Port: defines the signalling port associated with the BIWF which is used to interact with the CCU over the CBC interface. This object has a unique address within the network ser
37、vice supplier domain. 8) BNC.Cut Through: indicates when through connection of BNC has occurred. Q series Supplement 32 (11/2002) 17 9) BNC.Established: indication that a BNC has been established on a particular termination in the BIWF. 10) BNC.Modified: indicates when the characteristics (i.e. Code
38、c, Bearer Service Characteristics) has been modified. 11) BNC.Release: an indication with a general reason for the release of a BNC (e.g. Normal Release, Interworking unspecified, ) 12) BNC Characteristic: identifies the type of transport to be established across the backbone network. It is carried
39、between call control instances via BICC signalling. 13) BNC-Cut-through Capability: used by the BIWF to inform the CSM of the bearer cut-through capability (i.e. commits resources on the receipt of a bearer-setup-req or confirm. 14) BNC-ID: identifies the logical connection between a local and remot
40、e termination. 15) CCU Control Port: defines the signalling port associated with the CSF which is used to interact with the BIWF over the CBC Interface. This object has a unique address within the network service supplier domain. 16) Codec: contains the coding information (ie selected CODEC) to be u
41、sed by the BIWF. 17) Connection_Topology/Connection Configuration: specifies the type and configuration of the connection type to be established (e.g. Type 1, Type 2, Type 6). To specify the connection topology the connections between the terminations in a context is specified (e.g. Type-x/One-way o
42、r BothWay). 18) Context ID: identifies the context entity. Generated by the BIWF upon creation of the context. In this Supplement, the following values are used: ALL, when referencing all contexts in use; Context ID, when referencing a specific context in use. Null Context, which indicates a context
43、 where terminations, that have resources associated with them and are not part of a Local Call Instance, reside. 19) Detect_Digit(x): indicates that a digit stimulus is detected on a termination in an BIWF. The digit/s is indicated in “x“. 20) Digit: identifies that a DTMF digit/s of a certain value
44、 (i.e. 0 9, #, *, ABCD) is applied to a termination. 21) Digit Map Descriptor: holds Digit Map data such as Digit Map Name and Value. 22) Event: is an indication that there has been an occurance of the stimulus contained in a NotificationRequested request. It indicates that the stimulus has been obs
45、erved on a termination in a BIWF. It may contain parameters detailing the specifics of the stimulus. 23) Events Descriptor: holds Event data such as Package and Event Names and Event Parameter Names and possible Values. 24) Event ID: provides the correlation between a request to detect an event and
46、the notification that the event has been detected. 25) Logical Port ID: identifies the Logical Port entity. Provisioned value in BIWF. The type of logical port is provisioned and known in the BIWF. 26) Local Control Descriptor: holds Local Control data such as Package and Property Names and current
47、and possible Property Values. 27) Local Descriptor: holds Local data such as Package and Property Names and current and possible Property Values. 28) Non Standard Data: can specify the BIWF Type, e.g. as Brand, Version and Issue. 29) Media Descriptor: holds Media data such as Package and Property Na
48、mes and current and possible Property Values. 18 Q series Supplement 32 (11/2002) 30) Modem Descriptor: holds Modem data such as Package and Property Names and current and possible Property Values. 31) Mux Descriptor: holds Mux data such as Mux Type and muxed Termination IDs. 32) Packages Descriptor
49、: holds data about Packages such as Package Names and Versions. 33) Notification_Requested “x“: identifies to the BIWF that it must monitor a termination for the stimulus “x“ to occur. Once the stimulus “x“ is detected an event is sent from the BIWF to the CSM. 34) Remote Descriptor: holds Remote data such as Package and Property Names and current and possible Property Values. 35) Service Change Address: indicates New own CCU/BIWF Control Address to be used. 36) Ser
