1、I NTERNATIONAL TELECOMMUN CATION UN ION lTU=T TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU Q.1238.4 SERIES Q: SWITCHING AND SIGNALLING Intelligent Network (O 612 O0 O) Interface Recommendation for intelligent network capability set 3: SCF-SDF interface ITU-T Recommendation Q. 1238.4 (Formerly CCI
2、TT 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 SIGNALLI
3、NG 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 BROADBA
4、ND ISDN INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 Q.l-Q.3 4.4-4.59 Q.6O-Q.99 Q.lOO-Q.119 Q.12O-Q.249 4.250-4.309 4.3 1O-Q.399 Q.40O-Q.499 QSOO-Q.599 Q.60O-Q.699 Q.70O-Q.799 Q.8OO-Q.849 Q .8 5 O-Q
5、 . 9 9 9 Q.lOOO-Q.1099 Q. 1 100-Q. 1199 Q.1200-Q.1699 Q.170O-Q.1799 Q.200O-Q.2999 For further details, please refer to the list of ITU-TRecommendatiom. ITU-T Recommendation Q.1238.4 Interface Recommendation for intelligent network capability set 3: SCF-SDF interface Summary The Q. 1238.x series of I
6、TU-T Recommendations 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 Q. 1228 and Q. 1224 specification (1 997) and the general rules for INAP provided in ITU-T Q. 1208, and is consistent with the scope of IN
7、CS-3 as defined in ITU-T Q. 123 1. Within the Q.123 series of ITU-T 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 ne
8、twork technology. This provides the flexibility to allocate distributed functionality into multiple physical network configurations and to evolve IN from IN CS-3 to some future CS-N. This Recommendation belongs to the Q.1238.x series of ITU-T Recommendations for IN Capability Set 3. It covers the SC
9、F-SDF interface including the description of the aspects of the SCF and SDF Functional Entities which are relevant to this interface. This Recommendation includes an electronic attachment containing clause 12 ASN. 1 definitions. Source ITU-T Recommendation Q. 1238.4 was prepared by ITU-T Study Group
10、 1 1 (1997-2000) and approved under the WTSC Resolution 1 procedure on 15 June 2000. Keywords IN Capability Set 3 (IN CS-3), Intelligent Network (IN), Intelligent Network Application Protocol (INAP), Service Control Function (SCF), Service Data Function (SDF). ITU-T 4.1238.4 (06/2000) i FOREWORD The
11、 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 technical, operating and tariff questions and issuing Reco
12、mmendations on them 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. T
13、he approval of ITU-T 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 IEC. NOTE In this Recommendation, the expression “Admi
14、nistration“ 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 may involve the use of a claimed Intellectual Prop
15、erty 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 this Recommendation, ITU had not received notice of
16、 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 database. O ITU 2001 All rights reserved. No part of
17、 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. 11 ITU-T 4.1238.4 (06/2000) CONTENTS Page 4 4.1 4.2 4.3 5 6 6.1 6.2 6.3 7 7.1 7.2 7.3 Scope . References . Abbreviation
18、s and acronyms Introduction . SCF-SDF relationship . Introduction to the reuse of X.500 for SDF Interfaces . 4.2.1 Alignment between the X.500 concepts and the IN 4.2.2 Use of a limited subset of X.500 . Versions and the rules for extensibility 4.3.1 Version negotiation Request processing at the SDF
19、 side . 4.3.2 SCF side . 4.3.3 Service Control Function (SCF) Model Service Data Function (SDF) Model General SDF components . 6.2.1 General . 6.2.2 SDF data manager . 6.2.3 Functional entity access manager 6.2.4 Security Manager . Data types handled by SDF FSM for SCF . Overview . SCME-FSM 7.2.1 St
20、ate 1: “Idle“ . 7.2.2 State 2: “Bind Pending“ . 7.2.3 State 3: “Active“ SDF Related states (SCSM-SDF) . 7.3.1 State 1: “Idle“ . 7.3.2 State 2: “Wait for subsequent Requests“ . 7.3.3 State 3: “Wait for Bind Result“ . 7.3.4 State 4: “SDF Bound“ 8 FSM for SDF 8.1 Overview . 8.2 SDME-FSM ITU-T Q.1238.4
21、(06/2000) 1 1 2 4 6 6 7 8 8 8 9 9 9 9 9 10 10 12 . 111 8.2.1 State 1: “Idle“ . 8.2.2 State 2: “Wait for TFC“ . 8.2.3 State 3: “Wait for BindResult“ 8.2.4 State 4: flActivefl SDF state transition model for SCF related states 8.3.1 State 1: “Idle“ . 8.3.2 State 2: “Bind Pending“ . 8.3.3 State 3: “SCF
22、Bound“ 8.3 9 Detailed Operation Procedure . 9.1 Execute procedure . 9.1.1 General description 9.1.3 Invoking entity (SCF) 9.1.4 Responding entity (SDF) . 9.2.1 General description 9.2.3 Invoking entity (SCF) 9.2.4 Responding entity (SDF) . 9.3 IN-DirectoryBind procedure . 9.3.1 General description 9
23、.1.2 Parameters . 9.2 IN-AddEntry procedure 9.2.2 Parameters . 9.3.2 Parameters . 9.3.3 Invoking Entity (SCF) . 9.3.4 Responding Entity (SDF) 9.4 IN-ModifyEntry procedure . 9.4.1 General description 9.4.2 Parameters . 9.4.3 Invoking entity (SCF) 9.5 IN-RemoveEntry procedure 9.5.1 General description
24、 9.5.2 Parameters . 9.5.3 Invoking entity (SCF) 9.5.4 Responding entity (SDF) . 9.6 IN-Search procedure . 9.6.1 General description 9.6.2 Parameters . 9.6.3 Invoking entity (SCF) 9.6.4 Responding entity (SDF) . 9.4.4 Responding entity (SDF) . Page 12 12 13 13 13 14 14 14 15 15 15 15 16 17 18 18 18 1
25、9 19 20 20 20 20 21 21 21 21 22 22 23 23 23 23 24 24 24 24 25 26 iv ITU-T 4.1238.4 (06/2000) . 9.7 IN-Unbind procedure 9.7.1 General descnption 9.7.2 Invoking entity (SCF in Directory Access) . 9.7.3 Responding entity (SDF in Directory Access) 9.7.4 Invoking Entity (SDF in traffic flow control) . 9.
26、7.5 Responding Entity (SCF in traffic flow control) . 9.8.1 General description 9.8.2 Invoking Entity (SDF) . 9.9 TrafficFlowControl procedure 9.9.1 General description 9.8 TFCBind procedure 9.8.3 Responding Entity (SCF) . 9.9.2 Parameters . 9.9.3 Invoking entity (SDF) 9.9.4 Responding entity (SCF)
27、. 10 Parameters . 1 O . 1 10.2 Changes . Baseobject 10.3 Checkoverspecified 10.4 CommonResults 10.5 ControlType 10.6 Credentials 10.7 Duration 10.8 En try 10.9 Filter 1 O . 1 O IN-CommonArguments 1 O . 1 1 Information . 1 O . 12 Input-assertions . 1 O . 13 MatchedValuesOnly . 1 O . 14 Method-id 10.1
28、5 Null . 10.16 Object 1 O . 17 1 O . 1 8 SearchAliases 1 O . 19 SearchInfo . 10.20 Security . 10.2 1 Selection Output-assertions Page 26 26 26 27 27 27 28 28 28 28 29 29 29 30 30 31 31 31 31 31 31 31 31 31 32 32 33 33 33 33 34 34 34 34 34 35 35 ITU-T 4.1238.4 (06/2000) V 10.22 Specific-input 10.23 S
29、pecific-output 10.24 Subset 10.25 Targetsystem 10.26 TfcCnteria . 10.27 UncorrelatedSearchInfo 10.28 Versions 10.29 Waschained 11 Errors 1 1.1 Operation related error procedures . 1 1.1.1 AttributeError 1 1 . 1.2 ExecutionError . 11.1.3 IN-DirectoryBindError 1 1.1.4 IN-ServiceError . 1 1 1.5 NameErr
30、or . 1 1.1.6 Referral 1 1.1.7 SecurityError . 11.1.8 TFCBindError 1 1.1.9 UpdateError . . 12 ASN . 1 Definitions (electronic attachment) 13 Service assumed from TCAP 13.1 Normal Procedures . 13.1.1 SCSWSDSM related messages . 13.1.2 SCME/SDME related messages 13.2 Abnormal Procedures . 13.3 Dialogue
31、 Handling 1 3.3.1 Dialogue Establishment . 13.3.2 Dialogue Continuation . 13.3.3 Dialogue Termination 13.3.4 User Abort . 13.3.5 Provider Abort . 13.3.6 Mapping to TC Dialogue Primitives . 13.4 Component Handling 13.4.1 Procedures for INAP Operations . 13.4.2 Mapping to TC Component Parameters 36 36
32、 36 36 37 37 37 38 39 39 40 40 41 41 42 42 42 43 43 43 43 43 43 44 44 44 44 44 46 46 46 vi ITU-T 4.1238.4 (06/2000) ITU-T Recommendation 4.1238.4 Interface Recommendation for intelligent network capability set 3: SCF-SDF interface 1 Scope The Recommendation belongs to the Q.1238.x series of ITU-T Re
33、commendations for IN Capability Set 3. It specifies the protocol on the SCF-SDF interface and provides a description of the aspects of the SCF and SDF Functional Entities which are involved in the realization of this interface. 2 References All ITU-T Recommendations and other references are identifi
34、ed in ITU-T Q. 1238.1 3 Abbreviations and acronyms All abbreviations and acronyms used in this text are defined in ITU-T Q. 1238.1. 4 Introduction 4.1 SCF-SDF relationship This SCF-SDF relationship is used for messages between an SCF and an SDF in the public network. The relationship supports access
35、 to service data, which can be for intra-network or inter-network purposes. The SCF-SDF relationship supports messages for services when no call is actually taking place (call unrelated) as well as during call processing. For the most part, the call unrelated actions are to support the registration,
36、 authentication, encryption and handover procedures for terminal and personal mobility. The SCF-SDF relationship is also one of a limited set of relationships to support inter-networking. As such it provides a point of interconnection to the network, effectively hiding the specific structure of the
37、network and providing access security to the network from other public networks. The SCF-SDF relationship is used for various purposes. Each of the purposes can apply to the intra-network or inter-network cases. Specifically, the relationship is used for the Secured Data Acquisition from an SDF by a
38、n SCF. In this case, an SCF requires data to complete its processing of service logic. This relationship is the same as the SCF-SDF relationship as defined in IN CS-I and CS-2 and uses the same operations. It differs from the IN CS-1 and CS-2 relationship in the provision of additional methods for s
39、upporting verification of user/terminal credential. 4.2 Introduction to the reuse of X.500 for SDF Interfaces 4.2.1 The X.500 series of ITU-T Recommendations are used to specify the SCF-SDF interface and the contents of the SDF. Most of the concepts of the X.500 series are directly used in the IN en
40、vironment, however some alignments need to be done at the terminology level to ensure that the concepts introduced in the Directory are correctly understood. The purpose of this subclause is to Alignment between the X.500 concepts and the IN 1 This Recommendation includes an electronic attachment co
41、ntaining clause 12 ASN. 1 definitions. ITU-T 4.1238.4 (06/2000) I provide this alignment. It therefore only concentrates on the terms that are ambiguous in the IN environment. When looking at the structure of the SCF, the Service Data Management is the part of the SCF responsible for the interaction
42、s with the SDF. It can be mapped onto the concept of Directory User Agent (DUA). When an SCF on behalf of a user wants to Set-up an association with an SDF, an instance of a DUA is created in the SLPI. It is killed when the association is ended. The SDF is the entity responsible for answering the da
43、tabase requests. This functional entity can be mapped onto the Directory System Agent (DSA). When an association is set-up between an SCF and an SDF, an instance of a DSA is created for the length of the association. The Directory is a collection of DSAdSDFs. This set can be used for a specific serv
44、ice or for a variety of services. The notion of Directory is equivalent to the concept of database systems in IN. The Directory can also be seen as a repository of data. IN services provide various kinds of data access to users. The information is organized into entries. An entry is a collection of
45、information that can be identified (or named). When it represents an object (i.e. contains primary information about an object), it is called an object entry. Objects are anything which are identifiable (can be named) and which are of interest to hold information on in the database. A typical exampl
46、e of an object is a user. Objects can be described by several entries. Each individual information that is used to describe an object is an attribute. They are associated to entries. In the IN environment, the service provider is responsible for the management and the administration of the data cont
47、ained in a DSA. Therefore, the service provider plays the administrator role. He is the administrative authority in X.500 terminology. The service provider enforces the security procedure (authentication and access control). 4.2.2 The primary purpose of the X.500 series of ITU-T Recommendations is t
48、o provide a directory service and not the description of the SCF-SDF interface as SG 11 wants to use them. The X.500 functionality covers more than the functionality needed for this capability set. The Operation Procedure, Parameters, and ASN. 1 definitions try to indicate which aspects of the Direc
49、tory Abstract Service should be considered and supported by implementors within the scope of this IN capability set. It also mentions the attitude to adopt when a non-supported parameter is received. Profiling is used as a means to present the status of the different parameters. For convenience and clarity, this profile is defined using ASN.l subtyping facilities; however, these definitions do not form a protocol specification. The ASN.1 module is described in subclause 12.5 for information. This simply indicates which parameters should not be sent for an implementation. It does not change
