ITU-T Q 1238 7-2000 Interface Recommendation for Intelligent Network Capability Set 3 SCF-CUSF Interface Series Q Switching and Signalling Intelligent Network (Study Group 11)《对于智能.pdf

《ITU-T Q 1238 7-2000 Interface Recommendation for Intelligent Network Capability Set 3 SCF-CUSF Interface Series Q Switching and Signalling Intelligent Network (Study Group 11)《对于智能.pdf》由会员分享，可在线阅读，更多相关《ITU-T Q 1238 7-2000 Interface Recommendation for Intelligent Network Capability Set 3 SCF-CUSF Interface Series Q Switching and Signalling Intelligent Network (Study Group 11)《对于智能.pdf（63页珍藏版）》请在麦多课文档分享上搜索。

1、INTERNATIONAL TELECOMMUNICATION UNION ITU-T TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU Q.1238.7 (06/2 O O O) SERIES Q: SWITCHING AND SIGNALLING Intelligent Network Interface Recommendation for intelligent network capability set 3: SCF-CUSF interface ITU-T Recommendation Q.1238.7 (Formerly CCITT

2、 Recommendation) ITU-T Q-SERIES RECOMMENDATIONS SWITCHING AND SIGNALLING SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4 AND No. 5 SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 SPECIFICATIONS OF SIGNALLING

3、 SYSTEM R1 SPECIFICATIONS OF SIGNALLING SYSTEM R2 DIGITAL EXCHANGES INTERWORKING OF SIGNALLING SYSTEMS SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 43 INTERFACE DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 PUBLIC LAND MOBILE NETWORK INTERWORKING WITH SATELLITE MOBILE SYSTEMS INTELLIGENT NETWORK BROADBAND

4、 ISDN INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 Q. 14.3 4.44.59 Q.6O-Q.99 Q.lOO-Q.119 Q. 120-Q.249 4.250-4.309 4.310-4.399 4.400-4.499 Q.50O-Q.599 Q.60O-Q.699 4.700-4.799 Q.80O-Q.849 Q.85O-Q.999

5、Q. lOOO-Q.1099 Q. 110O-Q. 1 199 Q.120O-Q.1699 Q.170O-Q.1799 Q.200O-Q.2999 For further details, please refer to the list of ITU-TRecommendations. ITU-T Recommendation 4.1238.7 Interface Recommendation for intelligent network capability set 3: SCF-CUSF interface Summary The Q. 1238.x series of IT-T Re

6、commendations defines the Intelligent Network (IN) Application Protocol (INAP) for IN Capability Set 3 (IN CS-3), the INAP for IN CS-3 based upon IN CS-2 4.1228 and 4.1224 specification (1997) and the general rules for INM provided in 4.1208, and is consistent with the scope of IN CS-3 as defined in

7、 IT-T Q. 123 1. Within the Q.123 series of Recommendations, the Q.1238.x series describes the protocol realizing the Q. 123 1 Distributed Functional Plane in a service and vendor implementation independent manner, as constrained by the capabilities of the embedded base of network technology. This pr

8、ovides the flexibility to allocate distributed functionality into multiple physical network configurations and to evolve IN from IN CS-3 to some future IN CS-N. This Recommendation belongs to Q.1238.x series of ITU-T Recommendations for IN Capability Set 3. It covers the CUSF-SCF interface including

9、 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 clause 13 ASN. 1 definitions. Source ITU-T Recommendation 4.1238.7 was prepared by TTU-T Study Group 11 (1997-2000) and appro

10、ved under the WTSC Resolution 1 procedure on 15 June 2000. Keywords Intelligent Network (IN), Intelligent Network Application Protocol (INAP), IN Capability Set 3 (IN CS-3), Service Control Function (SCF), Call Unrelated Service Function (CUSF). ITU-T Q.1238.7 (06/2000) i FOREWORD The International

11、Telecommunication Union (IT) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of IT. -T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them

12、with a view to standardizing telecommunications on a worldwide basis. The World Telecommunication Standardization Conference (WTSC), 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

13、 Recommendations is covered by the procedure laid down in WTSC Resolution 1. In some areas of information technology which fall within ITU-Ts purview, the necessary standards are prepared on a collaborative basis with IS0 and EC. NOTE In this Recommendation, the expression “Administration“ is used f

14、or 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 may involve the use of a claimed Intellectual Property Right. U takes n

15、o 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 this Recommendation, had not received notice of intellectual property, pro

16、tected by patents, which may be required to implement this Recommendation. However, impiementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. o 2001 All rights reserved. No part of this publication may be reprod

17、uced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from ITU. ITU-T 4.1238.7 (06/2000) CONTENTS Page 1 Scope . 2 1 References . 3 Abbreviations and acronyms 1 4 4.1 4.2 Relationships . SCF-CCFKUSF relationship .

18、CUSF-SSF relationship . 1 1 5 5.1 5.2 CCFKUSF model . General CCFKUSF components . 5.2.1 Basic Non-Call Manager (BNCM) 5.2.2 5.2.3 IN - Non-Switching Manager (IN-NSM) . Feature Interaction Managermon-Call Manager (FIM/NCM) . Relationship of CCFKUSF model components . BNCM relationship to IN-NSM BNCM

19、 and IN-NSM relationship to FIM/NCM . BCUSM (Basic Call Unrelated State Model) . 5.3.1 5.3.2 5.4.1 BCUSM description 5.4.2 BCUSM DP criteria . 2 5.3 2 2 2 4 8 5.4 SCF model 9 6 7 7.1 9 9 11 12 13 14 FSM for CUSF Relations between CUSF FSM and the SSFKCF and maintenance functions 7.2 CUSF state trans

20、ition diagram State b: “Waiting for Instructions“ 7.2.3 State c: “Monitoring“ . 7.2.1 State a: “Idle“ . 7.2.2 FSM for SCF . Overview . SCME FSM . CUSF related states (SCSM-CUSF) . State N2: “Preparing CUSF Instructions“ . 8.3.1 8.3.2 State N 1 : “Idle“. . 14 14 15 15 16 16 8 8.1 8.2 8.3 9 9.1 9.2 FS

21、M for US1 . Overview . SCF US1 FSM for CUSF 19 19 21 ITU-T 4.1238.7 (06/2000) . 111 9.3 10 10.1 10.2 10.3 10.4 10.5 10.6 10.7 10.8 iv CUSF US1 FSM Operation procedures ActivationReceivedAndAuthorized procedure . General description 10.1.3 Invoking entity (CUSF) . ActivityTest procedure . 10.2.1 Gene

22、ral descnption 1 O . 1 . 1 1 O . 1.2 Parameters . 10.1.4 Responding entity (SCF) . 10.2.2 Parameters . 10.2.3 Invoking entity (SCF) 10.2.4 Responding entity (CUSF) AssociationReleaseRequested procedure . 10.3.1 General description 10.3.3 Invoking entity (CUSF) . 10.3.2 Parameters . 10.3.4 Responding

23、 entity (SCF) . ComponentReceived procedure 10.4.1 General description 10.4.2 Parameters . 10.4.3 Invoking entity (CUSF) . ConnectAssociation procedure . 10.5.1 General description 10.5.3 Invoking entity (SCF) ContinueAssociation procedure 10.6.1 General description 10.4.4 Responding entity (SCF) .

24、10.5.2 Parameters . 10.5.4 Responding entity (CUSF) 10.6.2 Parameters . 10.6.3 Invoking entity (SCF) 10.6.4 Responding entity (CUSF) EventReportBCUSM procedure . 10.7.1 General description 10.7.2 Parameters . 10.7.3 Invoking entity (CUSF) . 10.7.4 Responding entity (SCF) . InitialAssociationDP proce

25、dure 1 O . 8.1 General description ITU-T 4.1238.7 (06/2000) Page 21 21 22 22 22 23 23 24 24 24 24 24 25 25 25 26 26 26 26 27 27 27 28 28 28 28 29 29 29 29 29 30 30 30 31 31 32 32 32 10.8.2 Parameters . 10.8.3 Invoking entity (CUSF) . 10.8.4 Responding entity (SCF) . 10.9 InitiateAssociation procedur

26、e . 10.9.1 General description 10.9.2 Parameters . 10.9.3 Invoking entity (SCF) 10.9.4 Responding entity (CUSF) 10.10 ReleaseAssociation procedure 10.10.1 General description 1 O . 10.2 Parameters . 10.10.3 Invoking entity (SCF) 1 O . 10.4 Responding entity (CUSF) ReportUTSI procedure 10.11.1 Genera

27、l description 1 O . 1 1.2 Parameters . 10.1 1.3 Invoking entity (CUSF) . 10.11.4 Responding entity (SCF) . RequestReportBCUSMEvent procedure 1 O . 12.1 General description 10.12.2 Parameters . 10.12.3 Invoking entity (SCF) 10.12.4 Responding entity (CUSF) 1 O . 1 1 1 O . 12 10.13 RequestReportUTSI p

28、rocedure . 1 O . 13.1 General description 1 O . 13.2 Parameters . 10.13.3 Invoking entity (SCF) 10.13.4 Responding entity (CUSF) 10.14 SendComponent procedure . 1 O . 14.1 General descnption 1 O . 14.2 Parameters . 1 O . 14.3 Invoking entity (SCF) 1 O . 14.4 Responding entity (CUSF) 10.15 SendSTUI p

29、rocedure . 1 O . 15.1 General description 1 O . 15.2 Parameters . 10.15.3 Invoking entity (SCF) 10.15.4 Responding entity (CUSF) 11 Parameters . ITU-T 4.1238.7 (06/2000) Page 32 33 34 34 34 34 34 35 35 35 35 35 35 36 36 36 36 36 37 37 37 38 38 38 38 38 39 39 39 39 39 40 40 40 40 40 41 41 41 V 11.1 A

30、ddress . 11.2 BCUSMEvents 1 1.3 Bearercapability . 1 1.5 CallingPartyNumber . 1 1.6 CallingPartySubaddress 1 1.7 CallUnrelatedDpSpecificCommonParameters . 1 1.9 Component 11.10 ComponentCorrelationID . 1 1.1 1 ComponentType 11.4 CalledPartyNumber 11.8 Cause . 11.12 11.13 11.14 11.15 11.16 11.17 11.1

31、8 11.19 11.20 11.21 11.22 11.23 ComponentTypes CUApplicationInd . CUDPCriteria Event SpecificInformationBCUSM . EventTypeBCUSM . GenericNumbers . HighLa yerCompatibility . Message MiscCallInfo . MonitorDuration . RequestedUTSIList . LegID 11.24 ServiceKey 11.25 USIInformation . 1 1.26 USIServiceIndi

32、cator 12 12.1 vi Error procedures . Operation-related error procedures . 12.1.1 MissingCustomerRecord . 12.1.2 MissingParameter 12.1.3 ParameterutOfRange . 12.1.5 TaskRefsed 12.1.4 SystemFailure 12.1.6 UnexpectedComponentSequence 12.1.7 UnexpectedDataValue . 12.1.8 UnexpectedParameter 12.1.9 Unknown

33、LegID . ITU-T Q.1238.7 (06/2000) Page 41 41 42 42 42 42 43 43 44 44 44 44 44 44 44 45 45 45 45 46 46 46 46 46 46 46 46 47 47 48 49 49 49 49 49 49 49 12.2 Entity related error procedures . 12.2.1 Expiration of TcusF . 13 ASN . 1 definitions (electronic attachment) . 14 Service assumed by TCAP . 14.1

34、Normal procedures 14.1.1 CUSF-to-SCF messages 14.1.2 SCF-to-CUSF messages 14.2 Abnormal procedures 14.2.1 Dialogue handling 14.2.2 Component handling Page 50 50 50 50 50 50 51 51 51 52 ITU-T 4.1238.7 (06/2000) vii ITU-T Recommendation 4.1238.7 Interface Recommendation for intelligent network capabil

35、ity set 3: SCF-CUSF interface 1 Scope This Recommendation belongs to the Q.1238.x series of IT-T Recommendations for IN Capability Set 3. It specifies the protocol on the CUSF-SCF interface and provides a description of the aspects of the CUSF and SCF Functional Entities which are involved in the re

36、alization of this interface. 2 References All ITU-T Recommendations and other references are identified in ITU-T Q. 1238.1. 3 Abbreviations and acronyms All abbreviations and acronyms used in this text are defined in IT-T 4.1238.1. 4 Relationships 4.1 SCF-CCF/CUSF relationship The SCF-CUSF relations

37、hip is used for messages between an SCF and a CUSF in the public network. This relationship provides service or service features which need call-unrelated user interaction. This provides, for example, user location registration, user authentication, supplementary service activation or de-activation.

38、 Details of service drivers can be found in ITU-T Q. 123 1. This relationship is used for three cases, and respective cases are exclusive for the others. Case 1) For sendingheceiving ROSE APDUs to/from a user. Case 2) For sendingkeceiving US1 information to/from a user. Case 3) For relaying some inf

39、ormations for call unrelated association establishment fiom 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 relationship is not defined in IN CS-3, and is not mandatory. This relationship may be

40、 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 CCFKUSF model shown in Figure 1 is for a single-ended service logic instance related to a user. The purpose of this model

41、 is to provide a framework for the understanding of call unrelated modelling with respect to the CCFKUSF. 1 This Recommendation includes an electronic attachment containing clause 13 ASN. 1 defnitions. ITU-T 4.1238.7 (06/2000) 1 5.2 CCFICUSF components The CCF/CUSF model consists of several entities

42、. 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 (BNCM) This entity provides an abstraction of an association and proceedings for call unre

43、lated 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 instances. It also manages resources required to support basic call unrelated control. The

44、 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 This entity interacts with the SCF via SCF Access Manager in the course of providing IN services/features to users. It provides the SCF with an observabl

45、e 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 also detects non-call processing events that should be reported to active IN service logic instances or can lead to the invocati

46、on of IN service logic instances. It manages CUSF resources required to support IN service logic instances, if any. 5.2.3 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 arbitr

47、ate IN/non-IN call associatedkall unrelated associated services/features and IN call unrelated associated services/features 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 an

48、d IN-NSM to provide the CUSF with a unified view of call unrelated processing internal to the CUSF for an association. IN - Non-Switching Manager (IN-NSM) Feature Interaction Managermon-Call Manager (FIM/NCM) 5.3 Relationship of CCFKUSF model components 5.3.1 BNCM relationship to IN-NSM This is the

49、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 identi how basic call unrelated processing and IN call unrelated processing interact. 5.3.2 This is the relationship that encompasses the interaction between the BNCM and the FIM/NCM, and the interaction between the IN-NSM and the FIM/NCM. The messages related to these interactions are not externally visible and are n