ITU-T Q 1248 2-2001 Interface Recommendation for Intelligent Network Capability Set 4 SCF-SSF interface SERIES Q SWITCHING AND SIGNALLING Intelligent Network《对于智能网能力集4接口的建议 SCF-SSF.pdf

1、 INTERNATIONAL TELECOMMUNICATION UNION ITU-T Q.1248.2TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (07/2001) SERIES Q: SWITCHING AND SIGNALLING Intelligent Network Interface Recommendation for Intelligent Network Capability Set 4: SCF-SSF interface ITU-T Recommendation Q.1248.2 ITU-T Q-SERIES RECO

2、MMENDATIONS 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 APPLICABLE TO ITU-T STANDARD SYSTEMS Q.100Q.119 SPECIFICATIONS OF SIGNALLING

3、 SYSTEMS No. 4 AND No. 5 Q.120Q.249 SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 Q.250Q.309 SPECIFICATIONS OF SIGNALLING SYSTEM R1 Q.310Q.399 SPECIFICATIONS OF SIGNALLING SYSTEM R2 Q.400Q.499 DIGITAL EXCHANGES Q.500Q.599 INTERWORKING OF SIGNALLING SYSTEMS Q.600Q.699 SPECIFICATIONS OF SIGNALLING SYSTEM

4、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.1100Q.1199 INTELLIGENT NETWORK Q.1200Q.1699 SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 Q.1700Q.1799 SPECIFICATIO

5、NS 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. ITU-T Rec. Q.1248.2 (07/2001) i ITU-T Recommendation Q.1248.2 Interface Recommendation for Intelligent Network Capabilit

6、y Set 4: SCF-SSF interface Summary The Q.1248.x family of Recommendations defines the Intelligent Network (IN) Application Protocol for IN capability set 4 (IN CS-4). This family of Recommendations Q.1248.x defines the INAP for IN CS-4 based upon IN CS-2 ITU-T Q.1228 and Q.1224 (1997), and the gener

7、al rules for INAP provided in ITU-T Q.1208, and is consistent with the scope of IN CS-4 as defined in ITU-T Q.1241. Within the Q.124x series of Recommendations, ITU-T Q.1248.x family describes the protocol realizing the Q.1231 Distributed Functional Plane in a service and vendor implementation indep

8、endent manner, as constrained by the capabilities of the embedded base of network technology. This provides the flexibility to allocate distributed functionality into multiple physical network configurations and to evolve IN from IN CS-4 to some future CS-N. This Recommendation belongs to the Q.1248

9、.x family of Recommendations for IN capability set 4. It covers the SSF-SCF interface including the description of the aspects of the Functional Entities SSF and SCF which are relevant to this interface. This Recommendation includes an electronic attachment containing Annex A, ASN.1 definitions. Sou

10、rce ITU-T Recommendation Q.1248.2 was prepared by ITU-T Study Group 11 (2001-2004) and approved under the WTSA Resolution 1 procedure on 13 July 2001. ii ITU-T Rec. Q.1248.2 (07/2001) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of te

11、lecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. The World Tele

12、communication 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 these topics. The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. In some a

13、reas of information technology which fall within ITU-Ts purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. NOTE In this Recommendation, the expression “Administration“ is used for conciseness to indicate both a telecommunication administration and a recognized o

14、perating agency. INTELLECTUAL PROPERTY RIGHTS ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectu

15、al Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. As of the date of approval of this Recommendation, ITU had received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However,

16、 implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. ITU 2002 All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. ITU-T

17、 Rec. Q.1248.2 (07/2001) iii CONTENTS Page 1 Scope 1 2 References 1 3 Abbreviations and acronyms 1 4 Relationships 1 4.1 SSF-CCF relationship 1 4.2 SSF-SCF relationship. 2 5 CCF Functional Model. 2 5.1 Introduction 2 5.2 Basic Call Control Entity . 3 5.2.1 Overview 3 5.2.2 BCSM Model . 6 5.2.3 BCSM

18、Resume Points and BCSM Transitions in the IN CS-4 Call Model 31 5.2.4 BCSM Indications for the CS-4 call model . 41 5.2.5 Mapping from Cause to DP 48 5.2.6 Signalling Terminations . 56 5.3 Bearer Control Entity . 62 5.3.1 Overview 62 5.3.2 Bearer State Model. 63 5.4 Functional Interface between the

19、CCF and the SSF 65 5.4.1 Interactions from the CCF to the SSF 65 5.4.2 Interactions from the SSF to the CCF 65 6 SSF Function Model Components . 66 6.1 DP Criteria 66 6.2 Trigger Types and Trigger Precedence 69 6.3 Feature interaction manager (FIM) call manager (CM). 69 6.4 IN-Switching Manager. 70

20、6.4.1 IN-switching state model (IN-SSM) 70 6.4.2 The Connection View Model . 74 6.4.3 Connection View State Transitions 78 6.5 Out-Channel Call-Related User Interaction (OCCRUI) 99 7 SCF Model . 99 8 FSM for SSF. 99 8.1 SSF management finite state model (SSME-FSM) 100 9 FSM for SCF 101 iv ITU-T Rec.

21、 Q.1248.2 (07/2001) Page 10 FSM for USI. 101 11 Operation procedures . 101 11.1 Modified operations . 101 11.1.1 AnalyzeInformation . 102 11.1.2 CallGap. 102 11.1.3 Connect. 105 11.1.4 ConnectToRessouce. 106 11.1.5 ContinueWithArgument. 106 11.2 CreateOrRemoveTriggerData procedure . 106 11.2.1 Gener

22、al description 106 11.2.2 Invoking entity (SCF). 107 11.2.3 Responding entity (SSF) 107 11.2.4 DisconnectLeg 108 11.2.5 InitialDP . 109 11.2.6 InitiateCallAttempt. 109 11.2.7 ManageTriggerData . 109 11.2.8 MergeCallSegments . 110 11.2.9 MoveCallSegments 113 11.2.10 MoveLeg 114 11.2.11 RequestReportB

23、CSMEvent 115 11.2.12 SelectFacility 115 11.2.13 SelectRoute. 115 11.2.14 SplitLeg 115 11.3 New operations. 116 11.3.1 CallFiltering procedure 116 11.3.2 MonitorRouteRequest procedure . 118 11.3.3 MonitorRouteReport Procedure . 119 11.4 Operation Timers 120 12 Parameter Descriptions. 122 12.1 Modifie

24、d parameters 122 12.1.1 scfID. 122 12.1.2 BearerCapability. 123 12.1.3 DpSpecificCommonParameters . 123 12.1.4 EventSpecificInformationBCSM . 123 12.1.5 GapCriteria. 126 12.1.6 Profile. 126 12.1.7 ServiceInteractionIndicatorsTwo . 127 12.2 New parameters 130 12.2.1 AALParameters 130 ITU-T Rec. Q.124

25、8.2 (07/2001) v Page 12.2.2 AdditionalATMCellRate 130 12.2.3 AESACalledParty. 130 12.2.4 AESACallingParty . 130 12.2.5 AlternativeATMCellRate. 130 12.2.6 ATMCellRate. 130 12.2.7 BISDNParameters 130 12.2.8 CDVTDescriptor 131 12.2.9 ConnectionIdentifier. 131 12.2.10 CumulativeTransitDelay 131 12.2.11

26、Cug-Index. 131 12.2.12 Cug-Interlock . 131 12.2.13 Cug-OutgoingAccess . 131 12.2.14 DetachSignallingPath. 131 12.2.15 DestinationIndex 131 12.2.16 EndtoEndTransitDelay. 131 12.2.17 ExportSignallingPath . 131 12.2.18 GenericIdentifier 132 12.2.19 IncomingSignallingBufferCopy. 132 12.2.20 IPRelatedInf

27、ormation. 132 12.2.21 MergeSignallingPaths 132 12.2.22 MinimumATMCellRate. 133 12.2.23 MonitoringCriteria . 133 12.2.24 MonitoringTimeout 133 12.2.25 NoAnswerCause. 133 12.2.26 QoSParameter. 133 12.2.27 RouteCounters 133 12.2.28 StartTime 133 13 Errors 133 14 Services assumed from TCAP 136 14.1 Hand

28、ling of SSME-Related messages 136 14.1.1 SSF to SCF messages. 136 14.1.2 SCF to SSF messages. 136 14.1.3 Use of TC_BEGIN primitive parameters. 137 Annex A ASN.1 Definitions. 137 ITU-T Rec. Q.1248.2 (07/2001) 1 ITU-T Recommendation Q.1248.2 Interface Recommendation for Intelligent Network Capability

29、Set 4: SCF-SSF interface11 Scope This Recommendation belongs to the Q.1248.x family of Recommendations for IN capability set 4. It specifies the protocol on the SSF-SCF interface and provides a description of the aspects of the SSF and SCF Functional Entities which are involved in the realization of

30、 this interface. 2 References All ITU-T Recommendations and other references in this text are identified in ITU-T Q.1248.1. 3 Abbreviations and acronyms All abbreviations and acronyms used in this text are defined in ITU-T Q.1248.1. 4 Relationships 4.1 SSF-CCF relationship Call/service processing bu

31、ilds upon the current call process infrastructure of existing digital exchanges. It does so by using a generic model of existing call control functionality to process basic two-party calls, then adding service switching functionality to invoke and manage IN service logic. Once invoked, IN service lo

32、gic is executed under the control of service control functionality, in conjunction with service data functionality. With this distributed approach to call/service processing, the existing call control functionality retains ultimate responsibility for the integrity of calls, as well as for the contro

33、l of call processing resources. The following call/service processing constraints apply: 1) Call control and service switching functionality are tightly coupled, thus the relationship between SSF and CCF is not standardized. 2) A call is either between two or more end users that are external to the

34、network and addressable via a directory number or combination of directory number and bearer capability, or a call is between one or more end users and the network itself. 3) A call may be initiated by an end user, or by an SCF within the network on behalf of an end user. To supplement a call, IN se

35、rvice logic may either be invoked by an end user served by an IN exchange, or by the network on behalf of an end user. 4) A call may span multiple exchanges. As such, each exchange only controls the portion of the call in that exchange: call processing is functionally separated between exchanges. IN

36、 service logic invoked on IN exchanges in such an inter-exchange call is managed independently by each IN exchange. 5) Existing exchanges can be viewed as having two functionally separate sets of call processing logic that coordinate call processing activities to create and maintain a basic two-part

37、y call. This functional separation is provided between the originating portion of the call and the terminating portion of the call. This functional separation should be maintained in an IN exchange to allow IN service logic invoked on the originating portion of the call _ 1This Recommendation includ

38、es an electronic attachment containing Annex A, ASN.1 definitions. 2 ITU-T Rec. Q.1248.2 (07/2001) (i.e. on behalf of the calling party) to be managed independently of IN service logic invoked on the terminating portion of the call (i.e. on behalf of the called party). 6) It is desirable to allow mu

39、ltiple IN-supported service logic instances to be simultaneously active for a given end user. It is also recognized that non-IN service logic will continue to exist in the network. As such, service feature logic instances mechanisms should: i) determine which service logic to invoke for a given serv

40、ice request. This mechanism should select the appropriate IN-supported service logic or non-IN-supported service logic, and block the invocation of any other service logic for that particular service request; ii) limit simultaneously active IN- and non-IN-supported service logic instances; iii) ensu

41、re that simultaneously active IN-supported service logic instances adhere either to the single-ended, single point of control (SPC) restriction or to the single-ended, multiple points of control (MPC) capability as introduced with IN CS-4. For each half call a CS-4 compliant CCF/SSF may behave eithe

42、r according to SPC rules or MPC rules depending on trigger table information provided at IN service triggering. 7) The distributed approach and added complexity of call/service processing requires mechanisms for fault detection and recovery, allowing graceful termination of calls and appropriate tre

43、atments for end users. 4.2 SSF-SCF relationship The SCF-SSF relationship is used for communication between an SCF and an SSF in the public network. This relationship, with the aid of possible other relationships (e.g. the SCF-SRF, SCF-SCF and SCF-SDF), provides a variety of services and service feat

44、ures. Details of service drivers for IN CS-4 can be found in ITU-T Q.1241. A relationship between the SCF and SSF is established either as a result of the SSF sending a request for instruction to the SCF, or at the request of the SCF for initiation of a call or for some non-call-related reason. A re

45、lationship between a SCF and a SSF is normally terminated at the request of the SCF. The SSF may also terminate the relationship, e.g. when no pending monitor requests prevails or in error cases. A single SCF instance may have concurrent relationships with multiple SSF instances. A single SSF instan

46、ce may have concurrent relationships with multiple SCF instances in the case where the IN CS-4 Multiple Points of Control applies to a half call instance. If Single Point of Control applies a single SSF instance it may only have a relationship with one SCF instance at a time for any given half-call

47、instance. Note that this refers to control as opposed to monitor relationships. It should be noted that the selection of an SRF is not always performed by the SCF. In some cases selection is performed by an SSF, for example, where assist/hand-off procedures are being used. For details regarding the

48、relationship to the SRF see ITU-T Q.1248.3. 5 CCF Functional Model 5.1 Introduction The Call Control Function (CCF) provides an abstraction of the part of a switch which implements basic call and connection control to establish communication paths for users, and to interconnect such communication pa

49、ths. 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 Entity is ITU-T Rec. Q.1248.2 (07/2001) 3 responsible for the overall co-ordination of basic call processing. It interacts with the Bearer Control Entity that controls media resources. The CCF and the media resources may reside in the same physical entity (e.g. traditional switching centre) or be implemented in two different physical n