1、 INTERNATIONAL TELECOMMUNICATION UNION ITU-T Q.1248.4 TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (07/2001) SERIES Q: SWITCHING AND SIGNALLING Intelligent Network Interface Recommendation for Intelligent Network Capability Set 4: SCF-SDF interface ITU-T Recommendation Q.1248.4 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.4 (07/2001) i ITU-T Recommendation Q.1248.4 Interface Recommendation for Intelligent Network Capabili
6、ty Set 4: SCF-SDF interface Summary The Q.1248.x series of ITU-T Recommendations defines the Intelligent Network (IN) Application Protocol (INAP) for IN Capability Set 4 (IN CS-4), the INAP for IN CS-4 based upon IN CS-3 Q.1238 specification (2000), and the general rules for INAP provided in ITU-T Q
7、.1208, and is consistent with the scope of IN CS-4 as defined in ITU-T Q.1241. Within the Q.124x series of ITU-T Recommendations, the Q.1248.x series describes the protocol realizing the Q.1241 Distributed Functional Plane in a service and vendor implementation independent manner, as constrained by
8、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.x series of ITU-T Recommendation
9、s for IN Capability Set 4. It covers the SCF-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 Annex A, ASN.1 definitions. Source ITU-T Recommendation Q.
10、1248.4 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), Service Data Function (SDF).
11、ii ITU-T Rec. Q.1248.4 (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 responsible for studying technical, op
12、erating 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 turn,
13、 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. NOTE I
14、n 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 may inv
15、olve 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 this Rec
16、ommendation, 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 database.
17、 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.4 (07/2001) iii CONTENTS Page 1 Scope. 1 2 References. 1 3 A
18、bbreviations and acronyms 1 4 Introduction. 1 4.1 SCF-SDF relationship. 1 4.2 Introduction to the reuse of X.500 for SDF interfaces . 1 4.2.1 Alignment between the X.500 concepts and the IN 1 4.2.2 Use of a limited subset of X.500 . 2 4.3 Versions and the rules for extensibility 3 4.3.1 Version nego
19、tiation 3 4.3.2 SCF side. 3 4.3.3 Request processing at the SDF side. 4 5 Service Control Function (SCF) Model 4 6 Service Data Function (SDF) Model 4 6.1 General 4 6.2 SDF components. 5 6.2.1 General. 5 6.2.2 SDF data manager . 5 6.2.3 Functional entity access manager 5 6.2.4 Security manager . 6 6
20、.3 Data types handled by SDF 6 7 FSM for SCF. 6 7.1 Overview. 6 7.2 SCME-FSM 7 7.2.1 State 1: “Idle“. 8 7.2.2 State 2: “Bind Pending“. 8 7.2.3 State 3: “Active“ 8 7.3 SDF-related states (SCSM-SDF) 9 7.3.1 State 1: “Idle“. 9 7.3.2 State 2: “Wait for subsequent Requests“ . 9 7.3.3 State 3: “Wait for B
21、ind Result“ . 10 7.3.4 State 4: “SDF Bound“ 10 8 FSM for SDF 10 8.1 Overview. 10 8.2 SDME-FSM 12 iv ITU-T Rec. Q.1248.4 (07/2001) Page 8.2.1 State 1: “Idle“. 12 8.2.2 State 2: “Wait for TFC“ . 12 8.2.3 State 3: “Wait for BindResult“ 13 8.2.4 State 4: “Active“ 13 8.3 SDF state transition model for SC
22、F-related states 13 8.3.1 State 1: “Idle“. 14 8.3.2 State 2: “Bind Pending“. 14 8.3.3 State 3: “SCF Bound“ 14 9 Detailed operations procedure 15 9.1 IN-Execute procedure . 15 9.1.1 General description 15 9.1.2 Parameters . 15 9.1.3 Invoking entity (SCF) 16 9.1.4 Responding entity (SDF). 17 9.2 IN-Ad
23、dEntry procedure 18 9.2.1 General description 18 9.2.2 Parameters . 18 9.2.3 Invoking entity (SCF) 19 9.2.4 Responding entity (SDF). 19 9.3 IN-DirectoryBind procedure. 20 9.3.1 General description 20 9.3.2 Parameters . 20 9.3.3 Invoking Entity (SCF) . 20 9.3.4 Responding Entity (SDF) 21 9.4 IN-Modif
24、yEntry procedure . 21 9.4.1 General description 21 9.4.2 Parameters . 21 9.4.3 Invoking entity (SCF) 22 9.4.4 Responding entity (SDF). 22 9.5 IN-RemoveEntry procedure 23 9.5.1 General description 23 9.5.2 Parameters . 23 9.5.3 Invoking entity (SCF) 23 9.5.4 Responding entity (SDF). 24 9.6 IN-Search
25、procedure . 24 9.6.1 General description 24 9.6.2 Parameters . 24 9.6.3 Invoking entity (SCF) 25 9.6.4 Responding entity (SDF). 26 ITU-T Rec. Q.1248.4 (07/2001) v Page 9.7 IN-Unbind procedure 26 9.7.1 General description 26 9.7.2 Invoking entity (SCF in Directory Access) . 26 9.7.3 Responding entity
26、 (SDF in Directory Access) 27 9.7.4 Invoking entity (SDF in traffic flow control) 27 9.7.5 Responding Entity (SCF in traffic flow control). 27 9.8 TFCBind procedure 28 9.8.1 General description 28 9.8.2 Invoking entity (SDF) 28 9.8.3 Responding entity (SCF) . 28 9.9 TrafficFlowControl procedure 29 9
27、.9.1 General description 29 9.9.2 Parameters . 29 9.9.3 Invoking entity (SDF) 30 9.9.4 Responding entity (SCF) . 30 9.10 Operation timer values 30 10 Parameters. 31 10.1 BaseObject 31 10.2 Changes. 31 10.3 CheckOverspecified 31 10.4 CommonResults 31 10.5 ControlType 31 10.6 Credentials 31 10.7 Durat
28、ion 32 10.8 Entry 32 10.9 Filter 32 10.10 IN-CommonArguments 32 10.11 Information . 33 10.12 Input-assertions. 33 10.13 MatchedValuesOnly . 34 10.14 Method-id 34 10.15 Null . 34 10.16 Object 34 10.17 Output-assertions 34 10.18 SearchAliases 34 10.19 SearchInfo. 34 10.20 Security . 35 vi ITU-T Rec. Q
29、.1248.4 (07/2001) Page 10.21 Selection 35 10.22 Specific-input 36 10.23 Specific-output 36 10.24 Subset 36 10.25 TargetSystem 36 10.26 TfcCriteria. 36 10.27 UncorrelatedSearchInfo 37 10.28 Versions 37 10.29 WasChained 37 11 Errors 37 11.1 Operation-related error procedures. 37 11.1.1 AttributeError
30、38 11.1.2 ExecutionError. 38 11.1.3 IN-DirectoryBindError 39 11.1.4 IN-ServiceError . 40 11.1.5 NameError . 40 11.1.6 Referral 41 11.1.7 SecurityError . 41 11.1.8 TFCBindError 42 11.1.9 UpdateError . 42 12 Service assumed from TCAP 43 12.1 Normal procedures 43 12.1.1 SCSM/SDSM-related messages 43 12
31、.1.2 SCME/SDME-related messages 43 12.2 Abnormal procedures 44 12.3 Dialogue handling. 44 12.3.1 Dialogue establishment 44 12.3.2 Dialogue continuation 44 12.3.3 Dialogue termination . 44 12.3.4 User abort 44 12.3.5 Provider abort 44 12.3.6 Mapping to TC dialogue primitives. 44 12.4 Component handli
32、ng. 47 12.4.1 Procedures for INAP operations 47 12.4.2 Mapping to TC component parameters . 47 Annex A ASN.1 definitions (electronic attachment) 47 ITU-T Rec. Q.1248.4 (07/2001) 1ITU-T Recommendation Q.1248.4 Interface Recommendation for Intelligent Network Capability Set 4: SCF-SDF interface11 Scop
33、e This Recommendation belongs to the Q.1248.x series of ITU-T Recommendations for IN Capability Set 4. 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 Refere
34、nces 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 Q.1248.1. 4 Introduction 4.1 SCF-SDF relationship This SCF-SDF relationship is used for messages between an SCF and
35、 an SDF in the public network. The relationship supports access 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 pa
36、rt, the call unrelated actions are to support the registration, 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
37、 the network, effectively hiding the specific structure of the 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 relatio
38、nship is used for the Secured Data Acquisition from an SDF by an 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-1 and CS-2 and uses the same operations. It differs from the IN CS-1 and
39、 CS-2 relationship in the provision of additional methods for supporting verification of user/terminal credential. 4.2 Introduction to the reuse of X.500 for SDF interfaces 4.2.1 Alignment between the X.500 concepts and the IN The X.500 series of ITU-T Recommendations are used to specify the SCF-SDF
40、 interface and the contents of the SDF. Most of the concepts of the X.500 series are directly used in the IN environment; however, some alignments need to be done at the terminology level to ensure that the _ 1This Recommendation includes an electronic attachment containing Annex A, ASN.1 definition
41、s. 2 ITU-T Rec. Q.1248.4 (07/2001) concepts introduced in the Directory are correctly understood. The purpose of this subclause is to 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 Da
42、ta Management is the part of the SCF responsible for the interactions 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 associat
43、ion is ended. The SDF is the entity responsible for answering the database 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 i
44、s a collection of DSAs/SDFs. This set can be used for a specific service 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. Th
45、e information is organized into entries. An entry is a collection of 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
46、 of interest to hold information on in the database. A typical example 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 r
47、esponsible for the management and the administration of the data contained 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
48、Use of a limited subset of X.500 The primary purpose of the X.500 series of ITU-T Recommendations is to 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.
49、The Operation Procedure, Parameters, and ASN.1 definitions try to indicate which aspects of the Directory 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.1 subtyping facilities; however, these definitions do not form a protocol specification. The ASN.1 module is desc
