1、 INTERNATIONAL TELECOMMUNICATION UNION ITU-T Q.1922.4TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (12/2002) SERIES Q: SWITCHING AND SIGNALLING Specifications of signalling related to Bearer Independent Call Control (BICC) Interaction between the Intelligent Network application CS-4 protocol and t
2、he Bearer Independent Call Control protocol ITU-T Recommendation Q.1922.4 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
3、Q.60Q.99 CLAUSES APPLICABLE 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 SIGNALLI
4、NG SYSTEM R2 Q.400Q.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 MO
5、BILE SYSTEMS Q.1100Q.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 Re
6、commendations. ITU-T Rec. Q.1922.4 (12/2002) i ITU-T Recommendation Q.1922.4 Interaction between the Intelligent Network application CS-4 protocol and the Bearer Independent Call Control protocol Summary This Recommendation specifies procedures in order to provide interaction between the Bearer Inde
7、pendent Call Control (BICC) and INAP CS-4, i.e. to support IN services in an ISDN environment. It also specifies ISUP/INAP CS-4 interaction procedures as exceptions to BICC/INAP interaction procedures (see Annex B). The interaction between other signalling systems and INAP can be found by consulting
8、 the relevant interworking Recommendation to the BICC in combination with the BICC/INAP interaction Recommendation. Source ITU-T Recommendation Q.1922.4 was prepared by ITU-T Study Group 11 (2001-2004) and approved under the WTSA Resolution 1 procedure on 29 December 2002. Keywords BICC, INAP, SS7,
9、SSP. ii ITU-T Rec. Q.1922.4 (12/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 technica
10、l, 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. N
12、OTE In this Recommendation, 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 Recommendation ma
13、y involve 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 Recommendation development process. As of the date of approval of thi
14、s Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent data
15、base. ITU 2003 All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. ITU-T Rec. Q.1922.4 (12/2002) iii CONTENTS Page 1 Scope 1 2 References. 1 3 Terms and definitions . 2 4 Abbreviations 3 5 Conventions 4 6 Descripti
16、on 4 6.1 Establishment of bearer-related connections 4 6.2 Establishment of bearer unrelated connections 13 7 Operational requirements 13 8 Coding requirements. 13 8.1 Messages. 13 8.2 Parameters 13 9 State definitions 14 10 Signalling procedures . 14 10.1 Bearer-related connections . 14 10.2 Bearer
17、 unrelated connections . 44 11 Interaction with other networks 44 12 Interaction between IN basic call and ISDN supplementary services 44 12.1 Call diversion 46 12.2 Calling line identification presentation/restriction . 46 12.3 Completion of calls service 46 12.4 Conference 47 12.5 Connected line i
18、dentification presentation/restriction 47 12.6 Explicit call transfer . 48 12.7 Malicious call identification. 48 12.8 Three party 48 13 Interactions between IN services 48 13.1 Receiving an IN Service Compatibility in a BICC message 49 13.2 Handling of IN Service Compatibility in case outgoing legs
19、 are created by IN. 49 14 Parameter values (timers) . 50 iv ITU-T Rec. Q.1922.4 (12/2002) Page Annex A Signalling flows. 50 Annex B Exceptions for ISUP/INAP interaction 56 Appendix I Coding of the compatibility information for the parameters . 57 Appendix II Contents of the INAP serviceInteractionIn
20、dicatorsTwo 58 Appendix III Limitations for BICC basic call procedures and supplementary services for different types of IN calls 59 ITU-T Rec. Q.1922.4 (12/2002) 1 ITU-T Recommendation Q.1922.4 Interaction between the Intelligent Network application CS-4 protocol and the Bearer Independent Call Con
21、trol protocol 1 Scope This Recommendation specifies the interaction between BICC and INAP CS-4. It also specifies ISUP/INAP CS-4 interaction procedures as exceptions to BICC/INAP interaction procedures (see Annex B). For the purpose of this Recommendation the interface INAP CS-4 between SSP and SCP
22、is regarded as being an intra-network interface. The interaction between other signalling systems and INAP can be found by consulting the relevant interaction Recommendation to BICC in combination with this Recommendation. This Recommendation specifies procedures in order to provide interaction betw
23、een BICC and INAP, i.e. to support IN services in an ISDN environment. In addition, new protocol elements for the BICC are defined in this Recommendation in order to satisfy IN specific requirements. Based on the protocol inherent compatibility mechanism, a stepwise upgrade of the BICC functionality
24、 is possible. However, the new function is only available for an IN call, if supported in any of the affected service nodes. In this Recommendation the IN SSF is treated as a functional part of the BICC CSF (see Figure 2). It is presupposed that this functional inclusion of the SSF has no impact on
25、the CSF/BIWF interface. Any such impact is out of the scope of this Recommendation. This Recommendation describes SSF/CSF interaction only on “transit“ level, i.e. no special further interworking is described for CSF-Ns with incoming/outgoing call control signalling to access networks (i.e. ISN to A
26、CN-E/TE call control relationships). As a consequence, specific access-related interaction (e.g. interaction of line based triggering with ISDN supplementary services) is not within the scope of this Recommendation. This Recommendation therefore, also does not specify enhancements to the call contro
27、l protocols at the access network level (e.g. DSS1), which may be needed due to additional BICC functions or IN requirements, respectively. The main subjects of this interaction Recommendation are the following: description of specific call control functions for IN calls; impacts on the BICC basic c
28、all setup and the ISDN supplementary services for IN calls; and of the BICC protocol due to IN specific requirements. 2 References The following ITU-T Recommendations and other references contain provisions which, through reference is this text, constitute provisions of this Recommendation. At the t
29、ime of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below.
30、A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as an stand-alone document, the status of a Recommendation. 2 ITU-T Rec. Q.1922.4 (12/2002) 1 ITU-T Recommendations Q.761 to Q.764 (2000), Specificatio
31、ns of Signalling system No. 7 ISDN User Part (ISUP). 2 ITU-T Recommendation Q.1224 (1997), Distributed functional plane for intelligent network Capability Set 2. 3 ITU-T Recommendation Q.1231 (1999), Introduction to the Intelligent Network Capability Set 3. 4 ITU-T Recommendations Q.1238.x, Specific
32、ations of the Intelligent Network Application Protocol Capability Set 3. 5 ITU-T Recommendation Q.1290 (1998) , Glossary of terms used in the definition of intelligent networks. 6 ITU-T Recommendation Q.1601 (1999), Signalling system No. 7 Interaction between N-ISDN and INAP CS-2. 7 ITU-T Recommenda
33、tions Q.1902.1 to Q.1902.4 (2001), Specifications of the Bearer Independent Call Control protocol (BICC). 8 ITU-T Recommendation Q.1912.1 (2001), Interworking between the Signalling system No. 7 ISDN user part (ISUP) and the Bearer Independent Call Control protocol. 9 ITU-T Recommendation Q.1912.2 (
34、2001), Interworking between selected signalling systems (PSTN access, DSS1, C5, R1, R2, TUP) and the Bearer Independent Call Control protocol. 10 ITU-T Recommendation Q.1922.2 (2001), Interworking between the Intelligent Network Application protocol Capability Set 2 and the Bearer Independent Call C
35、ontrol protocol. 11 ITU-T Recommendation Q.931 (1998), ISDN user-network interface (DSS1); Layer 3 specification for basic call control. 12 ITU-T Recommendation Q.765.1 (1998), Signalling system No. 7 Application transport mechanism: Support of VPN applications with PSS1 information flows. 13 ITU-T
36、Recommendation Q.769.1 (1999), Signalling system No. 7 ISDN user part enhancements for the support of number portability. 14 ITU-T Recommendation Q.1902.6 (2001), Bearer Independent Call Control protocol (Capability Set 2): Generic signalling procedures and support of ISDN user part supplementary se
37、rvices for bearer redirection. 15 ITU-T Recommendations Q.1248.x (2001), Interface Recommendation for Intelligent Network Capability Set 4. 3 Terms and definitions This Recommendation defines the following terms: Call Control Function (CCF): see 3.3/Q.1224 2. Service Control Function (SCF): see 3.3/
38、Q.1224 2. Service Switching Function (SSF): see 3.3/Q.1224 2. Specialized Resource Function (SRF): see 3.3/Q.1224 2. ITU-T Rec. Q.1922.4 (12/2002) 3 4 Abbreviations This Recommendation uses the following abbreviations: ACM Address Complete Message (BICC) ANM Answer Message (BICC) APM Application Tra
39、nsport Mechanism ATP Access Transport Parameter (BICC) BCF Bearer Control Function (BICC) BCSM Basic Call State Model (IN) BICC Bearer Independent Call Control BIWF Bearer Inter-Working Function (BICC) CCSS Call Completion Service Set-up CMN Call Mediation Node (BICC) CON Connect message (BICC) COT
40、Continuity message (BICC) CPG Call Progress message (BICC) CSF Call Service Function (BICC) DLE Destination Local Exchange DP Detection Point (IN) DSS1 Digital Subscriber Signalling System No. 1 EDP-N Event Detection Point Notification (IN) EDP-R Event Detection Point Request (IN) ERB EventReportBCS
41、M (IN) FAR Facility Request Message (BICC) FOT Forward Transfer Message (BICC) FRJ Facility Reject (BICC) GVNS Global Virtual Network Service IAM Initial Address Message (BICC) IDR Identification Request Message (BICC) IE Information Element IN Intelligent Network INAP Intelligent Network Applicatio
42、n Protocol IP Intelligent Peripheral (IN) IRS Identification Response message (BICC) ISDN Integrated Services Digital Network ISN Interface Serving Node (BICC) ISUP ISDN User Part OLE Originating Local Exchange 4 ITU-T Rec. Q.1922.4 (12/2002) PRI Pre-release Information message (BICC) REL RELease me
43、ssage (BICC) RES RESume message (BICC) RLC Release Complete message (BICC) SCP Service Control Point (IN) SGM Segmentation Message (BICC) SN Serving Node (BICC) SS Signalling System SSP Service Switching Point (IN) SUS Suspend message (BICC) TMR Transmission Medium Requirement TNS Transit Network Se
44、lection (BICC) 5 Conventions The name of each element of the following class of terms is capitalized, and capital letters within that term can possibly occur: operations. Example: ContinueWithArgument operation. parameters within operations. Example: CalledPartyNumber. 6 Description 6.1 Establishmen
45、t of bearer-related connections 6.1.1 Integration of IN service control into a BICC serving node ITU-T Rec. Q.1248.1 15 provides a distributed functional plane architecture for IN Capability Set 4 (CS-4). Interactions between the following functional entities (FEs) are relevant for this Recommendati
46、on: Call Control Function (CCF); Service Switching Function (SSF); Service Control Function (SCF); and Specialized Resource Function (SRF). The functional entities can be implemented in one or more network elements called physical entities. The service control point (SCP) is the physical entity in t
47、he intelligent network that implements the SCF. The CCF and SSF are realized in the service switching point (SSP) and the SRF is realized in the intelligent peripheral (IP). The main function of the CCF, according to ITU-T Rec. Q.1248.1 (see 15), is to provide the IN service logic with an abstract v
48、iew of the call state and specific call(-state) associated data according to a “Basic Call State Model“ (BCSM). This BCSM defines “detection points“ at which the SSF can interrupt normal call processing and access an IN service logic in the SCF to change call data, or reconfigure the call, before co
49、ntinuing call processing at a specified BCSM-point. ITU-T Rec. Q.1922.4 (12/2002) 5 Instead of interrupting call processing, the SSF may also only retrieve call-related information to notify it to the IN service logic. The CCF can in turn be decomposed into several entities. Figure 1 depicts a functional decomposition of the CCF and its relationship to other components that are involved in call and service processing. Within the CCF, the Basic Call Control (BCC) Entity is responsible for th
