ITU-T Q 1248 7-2001 Interface Recommendation for Intelligent Network capability set 4 SCF-CUSF Interface《对于智能网能力集4接口的建议 对于智能网能力集4接口的建议-SCF-CUSF接口》.pdf

1、 INTERNATIONAL TELECOMMUNICATION UNION ITU-T Q.1248.7TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (07/2001) SERIES Q: SWITCHING AND SIGNALLING Intelligent Network Interface Recommendation for Intelligent Network capability set 4: SCF-CUSF Interface ITU-T Recommendation Q.1248.7 ITU-T Q-SERIES REC

2、OMMENDATIONS 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 SIGNALLIN

3、G 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 SPECIFICATI

5、ONS 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.7 (07/2001) i ITU-T Recommendation Q.1248.7 Interface Recommendation for Intelligent Network capabili

6、ty set 4: SCF-CUSF Interface Summary The Q.1248.x family of Recommendations defines the Intelligent Network (IN) Application Protocol (INAP) for IN capability set 4 (IN CS-4). This family of Recommendation defines the INAP for IN CS-4 based upon IN CS-3 ITU-T Q.1238 (2000), and the general rules for

7、 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, the ITU-T Q.1248.x family describes the protocol realizing the Q.1244 Distributed Functional Plane in a service and vendor implementation independent m

8、anner, 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 IN CS-N. This Recommendation belongs to ITU-T Q.1248.x

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

10、e ITU-T Recommendation Q.1248.7 was prepared by ITU-T Study Group 11 (2001-2004) and approved under the WTSA Resolution 1 procedure on 13 July 2001. Keywords Intelligent Network (IN), Intelligent Network Application Protocol (INAP), IN Capability Set 4 (IN CS-4), Service Control Function (SCF), Call

11、 Unrelated Service Function (CUSF). ii ITU-T Rec. Q.1248.7 (07/2001) 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 re

12、sponsible for studying technical, 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 th

13、e 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 areas of information technology which fall within ITU-Ts purview, the necessary standards are prepared on a collabor

14、ative 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 operating agency. INTELLECTUAL PROPERTY RIGHTS ITU draws attention to the possibility that the practice or implement

15、ation 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 Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. As

16、 of the date of approval of this 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

17、 to consult the TSB patent database. ITU 2002 All rights reserved. No part of this publication 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. ITU-T Rec. Q.1248.7 (07/2001) iii CONTENTS

18、 Page 1 Scope. 1 2 References. 1 3 Abbreviations and acronyms 1 4 Relationships. 1 4.1 SCF-CCF/CUSF relationship . 1 4.2 CUSF-SSF relationship. 1 5 CCF/CUSF model. 1 5.1 General 1 5.2 CCF/CUSF components . 2 5.2.1 Basic Non-Call Manager (BNCM) 2 5.2.2 IN Non-Switching Manager (IN-NSM) . 2 5.2.3 Feat

19、ure Interaction Manager/Non-Call Manager (FIM/NCM) . 2 5.3 Relationship of CCF/CUSF model components. 2 5.3.1 BNCM relationship to IN-NSM 2 5.3.2 BNCM and IN-NSM relationship to FIM/NCM . 2 5.4 Basic Call Unrelated State Model (BCUSM) . 2 5.4.1 BCUSM description 4 5.4.2 BCUSM DP criteria. 8 6 SCF mo

20、del 9 7 FSM for CUSF 9 7.1 Relations between CUSF FSM and the SSF/CCF and maintenance functions 9 7.2 CUSF state transition diagram 11 7.2.1 State a: “Idle“. 12 7.2.2 State b: “Waiting for Instructions“ 13 7.2.3 State c: “Monitoring“. 14 8 FSM for SCF. 14 8.1 Overview. 14 8.2 SCME FSM. 15 8.3 CUSF-r

21、elated states (SCSM-CUSF). 15 8.3.1 State N1: “Idle“ 16 8.3.2 State N2: “Preparing CUSF Instructions“ 16 9 FSM for USI . 19 9.1 Overview. 19 9.2 SCF USI FSM for CUSF 21 iv ITU-T Rec. Q.1248.7 (07/2001) Page 9.3 CUSF USI FSM 21 10 Operation procedures 21 10.1 ActivationReceivedAndAuthorized procedure

22、. 22 10.1.1 General description 22 10.1.2 Parameters . 22 10.1.3 Invoking entity (CUSF) . 23 10.1.4 Responding entity (SCF) . 23 10.2 ActivityTest procedure . 24 10.2.1 General description 24 10.2.2 Parameters . 24 10.2.3 Invoking entity (SCF) 24 10.2.4 Responding entity (CUSF) 24 10.3 AssociationRe

23、leaseRequested procedure 25 10.3.1 General description 25 10.3.2 Parameters . 25 10.3.3 Invoking entity (CUSF) . 26 10.3.4 Responding entity (SCF) . 26 10.4 ComponentReceived procedure 26 10.4.1 General description 26 10.4.2 Parameters . 27 10.4.3 Invoking entity (CUSF) . 27 10.4.4 Responding entity

24、 (SCF) . 27 10.5 ConnectAssociation procedure . 28 10.5.1 General description 28 10.5.2 Parameters . 28 10.5.3 Invoking entity (SCF) 28 10.5.4 Responding entity (CUSF) 29 10.6 ContinueAssociation procedure 29 10.6.1 General description 29 10.6.2 Parameters . 29 10.6.3 Invoking entity (SCF) 29 10.6.4

25、 Responding entity (CUSF) 30 10.7 EventReportBCUSM procedure . 30 10.7.1 General description 30 10.7.2 Parameters . 31 10.7.3 Invoking entity (CUSF) . 31 10.7.4 Responding entity (SCF) . 32 10.8 InitialAssociationDP procedure 32 10.8.1 General description 32 ITU-T Rec. Q.1248.7 (07/2001) v Page 10.8

26、.2 Parameters . 32 10.8.3 Invoking entity (CUSF) . 33 10.8.4 Responding entity (SCF) . 34 10.9 InitiateAssociation procedure . 34 10.9.1 General description 34 10.9.2 Parameters . 34 10.9.3 Invoking entity (SCF) 34 10.9.4 Responding entity (CUSF) 35 10.10 ReleaseAssociation procedure 35 10.10.1 Gene

27、ral description 35 10.10.2 Parameters . 35 10.10.3 Invoking entity (SCF) 35 10.10.4 Responding entity (CUSF) 35 10.11 ReportUTSI procedure 36 10.11.1 General description 36 10.11.2 Parameters . 36 10.11.3 Invoking entity (CUSF) . 36 10.11.4 Responding entity (SCF) . 36 10.12 RequestReportBCUSMEvent

28、procedure 37 10.12.1 General description 37 10.12.2 Parameters . 37 10.12.3 Invoking entity (SCF) 37 10.12.4 Responding entity (CUSF) 38 10.13 RequestReportUTSI procedure. 38 10.13.1 General description 38 10.13.2 Parameters . 38 10.13.3 Invoking entity (SCF) 38 10.13.4 Responding entity (CUSF) 39 1

29、0.14 SendComponent procedure. 39 10.14.1 General description 39 10.14.2 Parameters . 39 10.14.3 Invoking entity (SCF) 39 10.14.4 Responding entity (CUSF) 40 10.15 SendSTUI procedure. 40 10.15.1 General description 40 10.15.2 Parameters . 40 10.15.3 Invoking entity (SCF) 40 10.15.4 Responding entity

30、(CUSF) 41 10.16 Operation timers . 41 vi ITU-T Rec. Q.1248.7 (07/2001) Page 11 Parameters. 42 11.1 Address . 42 11.2 BCUSMEvents 42 11.3 BearerCapability . 42 11.4 CalledPartyNumber 42 11.5 CallingPartyNumber . 43 11.6 CallingPartySubaddress 43 11.7 CallUnrelatedDpSpecificCommonParameters . 43 11.8

31、Cause. 44 11.9 Component 44 11.10 ComponentCorrelationID . 44 11.11 ComponentType 44 11.12 ComponentTypes 44 11.13 CUApplicationInd. 44 11.14 CUDPCriteria 45 11.15 EventSpecificInformationBCUSM. 45 11.16 EventTypeBCUSM. 45 11.17 GenericNumbers . 45 11.18 HighLayerCompatibility. 45 11.19 LegID 46 11.

32、20 Message 46 11.21 MiscCallInfo . 46 11.22 MonitorDuration . 46 11.23 RequestedUTSIList. 47 11.24 ServiceKey 47 11.25 USIInformation. 47 11.26 USIServiceIndicator 47 12 Error procedures . 47 12.1 Operation-related error procedures. 47 12.1.1 MissingCustomerRecord . 48 12.1.2 MissingParameter 49 12.

33、1.3 ParameterOutOfRange. 50 12.1.4 SystemFailure 50 12.1.5 TaskRefused 50 12.1.6 UnexpectedComponentSequence 50 12.1.7 UnexpectedDataValue . 50 ITU-T Rec. Q.1248.7 (07/2001) vii Page 12.1.8 UnexpectedParameter 50 12.1.9 UnknownLegID . 50 12.2 Entity-related error procedures . 50 12.2.1 Expiration of

34、 TCUSF50 13 Service assumed by TCAP . 51 13.1 Normal procedures 51 13.1.1 CUSF-to-SCF messages 51 13.1.2 SCF-to-CUSF messages 52 13.2 Abnormal procedures 52 13.2.1 Dialogue handling 52 13.2.2 Component handling 53 Annex A ASN.1 definitions (electronic attachment) 53 ITU-T Rec. Q.1248.7 (07/2001) 1IT

35、U-T Recommendation Q.1248.7 Interface Recommendation for Intelligent Network capability set 4: SCF-CUSF Interface11 Scope This Recommendation belongs to the Q.1248.x family of Recommendations for IN capability set 4. It specifies the protocol on the CUSF-SCF interface and provides a description of t

36、he aspects of the CUSF and SCF Functional Entities which are involved in the realization of this interface. 2 References All ITU-T Recommendations and other references 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

37、 Q.1248.1. 4 Relationships 4.1 SCF-CCF/CUSF relationship The SCF-CUSF relationship is used for messages between an SCF and a CUSF in the public network. This relationship provides a service, or service features, which need call-unrelated user interaction. This provides, for example, user location re

38、gistration, user authentication, supplementary service activation or de-activation. Details of service drivers can be found in ITU-T Q.1241. This relationship is used for three cases, and respective cases are exclusive for the others. Case 1) for sending/receiving ROSE APDUs to/from a user. Case 2)

39、for sending/receiving USI informations to/from a user. Case 3) for relaying some informations for call unrelated association establishment from a supplementary service (e.g. CCBS) in CCF (BCUSM). 4.2 CUSF-SSF relationship It is considered that the CUSF and the SSF may have a relationship, but the re

40、lationship is not defined in IN CS-4, and is not mandatory. This relationship may be used to influence the basic call processing in the SSF/CCF (e.g. activation or de-activation of Call Forwarding) via call-unrelated interaction. 5 CCF/CUSF model 5.1 General The CCF/CUSF model shown in Figure 1 is f

41、or a single-ended service logic instance related to a user. The purpose of this model is to provide a framework for the understanding of call unrelated modelling with respect to the CCF/CUSF. _ 1This Recommendation includes an electronic attachment containing Annex A, ASN.1 definitions. ITU-T Rec. Q

42、.1248.7 (07/2001) 2 5.2 CCF/CUSF components The CCF/CUSF model consists of several entities. Each of the entities is briefly described below. It is noted that this shows a conceptual model of CCF/CUSF and is not intended to imply an actual implementation of the CCF/CUSF. 5.2.1 Basic Non-Call Manager

43、 (BNCM) This entity provides an abstraction of an association and proceedings for call unrelated interactions between a user and a network. It detects basic call unrelated events that can lead to the invocation of IN service logic instances or those that should be reported to active IN service logic

44、 instances. It also manages resources required to support basic call unrelated control. The BNCM interacts with the FIM/NCM as described in the FIM/NCM description below. The BNCM also manages the BCUSM and the DP processing logic. 5.2.2 IN Non-Switching Manager (IN-NSM) This entity interacts with t

45、he SCF via SCF Access Manager in the course of providing IN services/features to users. It provides the SCF with an observable view of a CUSF call unrelated processing activities, and provides the SCF with access to CUSF capabilities, such as managing of an association and invoked operations. It als

46、o detects non-call processing events that should be reported to active IN service logic instances or can lead to the invocation of IN service logic instances. It manages CUSF resources required to support IN service logic instances, if any. 5.2.3 Feature Interaction Manager/Non-Call Manager (FIM/NCM

47、) This entity provides mechanisms to prevent invocation of multiple instances of IN and non-IN service logic instances on a single association. The ability of the FIM/NCM to arbitrate IN/non-IN call associated/call unrelated associated services/features and IN call unrelated associated services/feat

48、ures is outside the scope of this capability set. These two types of arbitration need an implicit relationship. The FIM/NCM integrates these interactions mechanisms with the BNCM and IN-NSM to provide the CUSF with a unified view of call unrelated processing internal to the CUSF for an association.

49、5.3 Relationship of CCF/CUSF model components 5.3.1 BNCM relationship to IN-NSM This is the relationship that encompasses the interaction between the BNCM and the IN-NSM, through the FIM/NCM. The message related to this interaction is not externally visible and is not for standardization. However, an understanding of this subject is required to identify how basic call unrelated processing and IN call unrelated processing interact. 5.3.2 BNCM and IN-NSM relationship to FIM/NCM This is the relationship that encompasses the interaction between the BN