ITU-T Q 1248 3-2001 Interface Recommendation for Intelligent Network Capability Set 4 SCF-SRF interface《对于智能网能力集4接口的建议 对于智能网能力集4接口的建议-SCF-SRF接口》.pdf

1、 INTERNATIONAL TELECOMMUNICATION UNION ITU-T Q.1248.3 TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (07/2001) SERIES Q: SWITCHING AND SIGNALLING Intelligent Network Interface Recommendation for Intelligent Network Capability Set 4: SCF-SRF interface ITU-T Recommendation Q.1248.3 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 Q.1248.3 (07/2001) i ITU-T Recommendation Q.1248.3 Interface Recommendation for Intelligent Network Capability Se

6、t 4: SCF-SRF interface Summary The Q.1248.x family of ITU-T Recommandations define the Intelligent Network (IN) Application Protocol (INAP) for IN Capability Set 4 (IN CS-4). This definition is based upon IN CS-3 ITU-T Q.1238 (2000) and upon the general rules for INAP provided in ITU-T Q.1208, and i

7、s 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 family of ITU-T Recommendations describes the protocol realizing the Q.1244 Distributed Functional Plane in a service and vendor implementation independent manner, as co

8、nstrained 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.x family of ITU-T R

9、ecommendations for IN Capability Set 4. It covers the SCF-SRF interface including the description of the aspects of the SCF and SRF Functional Entities which are relevant to this interface. This Recommendation includes an electronic attachment containing Annex A, ASN.1 definitions. Source ITU-T Reco

10、mmendation Q.1248.3 was prepared by ITU-T Study Group 11 (2001-2004) and approved under the WTSA Resolution 1 procedure on 13 July 2001. Keywords IN, CS-4, INAP, SRF, SCF, IP. ii ITU-T Q.1248.3 (07/2001) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agenc

11、y 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 Recommendations on them with a view to standardizing telecommunications on a worldwide b

12、asis. 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, produce Recommendations on these topics. The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Res

13、olution 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 In this Recommendation, the expression “Administration“ is used for conciseness to indicate both a telecommunication administratio

14、n 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. ITU takes no position concerning the evidence, validity or applicability o

15、f 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 intellectual property, protected by patents, which may be required to implement this

16、Recommendation. However, 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

17、permission of ITU. ITU-T Q.1248.3 (07/2001) iii CONTENTS Page 1 Scope. 1 2 References. 1 3 Abbreviations and acronyms 1 4 Relationships. 1 4.1 SRF-CCF relationship. 1 4.2 SCF-SRF relationship. 1 5 SCF FE model. 1 6 SRF FE model. 2 6.1 Resource Control Part (RCP) 3 6.1.1 SRF Resource Manager . 4 6.1.

18、2 Transaction Module. 4 6.1.3 User Interaction scripts (UI Script) . 4 6.1.4 Resource Logic Library. 4 6.1.5 Resource Logic Instances 4 6.2 Resource Function Part (RFP) 4 6.3 Data Part (DP). 4 7 SRF application entity procedures 4 7.1 The SRF management finite state model (SRME FSM) 5 7.2 The SRF ca

19、ll State Model: SRSM 5 7.2.1 State 1: “Idle“. 7 7.2.2 State 2: “Connected“ 8 7.2.3 State 3: “User interaction“ . 9 7.3 SRF control procedures using CTR/ETC . 10 7.3.1 SRF connect procedures 11 7.3.2 SRF end user interaction procedures. 15 7.3.3 SRF disconnection procedures 19 7.3.4 Call-unrelated in

20、teraction 22 7.3.5 Examples illustrating complete user Interaction sequences 23 7.3.6 Example illustrating the use of SDSS 32 7.4 Other SRF control procedures 32 7.4.1 SRF connect procedures 32 7.4.2 SRF disconnection procedures 34 7.4.3 Examples illustrating complete User Interaction sequences . 34

21、 7.4.4 Differences from the procedures using CTR/ETC 35 8 SCF Application Entity procedure 35 iv ITU-T Q.1248.3 (07/2001) Page 8.1 The SCF Management state model for SRF . 36 8.1.1 The Activity Test FSM 36 8.1.2 The Call GAP FSM . 37 8.2 The SCF Call State Model (SCSM): FSM for specialized resource.

22、 38 8.2.1 State R1: “SRF Control Idle“. 39 8.2.2 State R2: “Controlling SRF“ 39 9 Detailed operation procedure 41 9.1 ActivityTest procedure . 41 9.1.1 General description 41 9.1.2 Parameters . 41 9.1.3 Invoking entity (SCF) 41 9.1.4 Responding entity (SRF) . 41 9.2 AssistRequestInstructions procedu

23、re 42 9.2.1 General description 42 9.2.2 Parameters . 42 9.2.3 Invoking entity (SRF) 42 9.2.4 Responding entity (SCF) . 42 9.3 Cancel procedure 43 9.3.1 General description 43 9.3.2 Parameters . 43 9.3.3 Invoking entity (SCF) 43 9.3.4 Responding entity (SRF) . 44 9.3.5 Responding entity (SSF) 44 9.4

24、 ConnectToResource procedure. 44 9.5 DisconnectForwardConnection procedure . 44 9.6 DisconnectForwardConnectionWithArgument procedure . 44 9.7 EstablishTemporaryConnection procedure. 44 9.8 PlayAnnouncement procedure 44 9.8.1 General description 44 9.8.2 Parameters . 45 9.8.3 Invoking entity (SCF) 4

25、5 9.8.4 Responding entity (SRF) . 46 9.9 PromptAndCollectUserInformation procedure. 46 9.9.1 General description 46 9.9.2 Parameters . 46 9.9.3 Invoking entity (SCF) 47 9.9.4 Responding entity (SRF) . 48 ITU-T Q.1248.3 (07/2001) v Page 9.10 PromptAndReceiveMessage procedure 49 9.10.1 General descrip

26、tion 49 9.10.2 Parameters . 49 9.10.3 Invoking entity (SCF) 50 9.10.4 Responding entity (SRF) . 50 9.11 ReportUTSI procedure 51 9.12 RequestReportUTSI procedure. 51 9.13 SendSTUI procedure. 51 9.14 ScriptClose procedure. 51 9.14.1 General description 51 9.14.2 Parameters . 52 9.14.3 Invoking entity

27、(SCF) 52 9.14.4 Responding entity (SRF) . 52 9.15 ScriptEvent procedure. 53 9.15.1 General description 53 9.15.2 Parameters . 53 9.15.3 Invoking entity (SRF) 53 9.15.4 Responding entity (SCF) . 54 9.16 ScriptInformation procedure. 54 9.16.1 General description 54 9.16.2 Parameters . 54 9.16.3 Invoki

28、ng entity (SCF) 55 9.16.4 Responding entity (controlling SRF). 55 9.17 ScriptRun procedure . 55 9.17.1 General description 55 9.17.2 Parameters . 55 9.17.3 Invoking entity (SCF) 56 9.17.4 Responding entity (SRF) . 56 9.18 SpecializedResourceReport procedure . 56 9.18.1 General description 56 9.18.2

29、Parameters . 57 9.18.3 Invoking entity (SRF) 57 9.18.4 Responding entity (SCF) . 57 9.19 SRFCallGap procedure . 57 9.19.1 General description 57 9.19.2 Parameters . 57 9.19.3 Invoking entity (SRF) 58 9.19.4 Responding entity (SCF) . 58 9.20 Operation timer values 59 vi ITU-T Q.1248.3 (07/2001) Page

30、10 Parameters. 60 10.1 CallSegmentID 60 10.2 CallSegmentToCancel 60 10.3 CollectedInfo 60 10.4 ControlType 62 10.5 Digits. 62 10.6 CorrelationID 62 10.7 DisconnectFromIPForbidden 62 10.8 GapIndicators 62 10.9 InformationToRecord . 62 10.10 InformationToSend. 63 10.11 LastEventIndicator 64 10.12 LegI

31、D 65 10.13 Media 65 10.14 MailBoxID 65 10.15 ReceivedStatus 65 10.16 RecordedMessageID. 65 10.17 RecordedMessageUnits 65 10.18 RequestAnnouncementComplete 65 10.19 SRFgapCriteria . 65 10.20 SubscriberID . 66 10.21 UIScriptId . 66 10.22 UIScriptResultInfo 66 10.23 UIScriptSpecificInfo. 66 11 Error pr

32、ocedures . 66 11.1 Operation-related error procedures. 66 11.1.1 Cancelled . 67 11.1.2 ImproperCallerResponse . 68 11.1.3 MissingCustomerRecord . 69 11.1.4 MissingParameter 69 11.1.5 ParameterOutOfRange. 70 11.1.6 SystemFailure 70 11.1.7 TaskRefused 71 11.1.8 UnavailableResource . 71 11.1.9 Unexpect

33、edComponentSequence 72 11.1.10 UnexpectedDataValue . 72 11.1.11 UnexpectedParameter 73 ITU-T Q.1248.3 (07/2001) vii Page 11.1.12 UnknownLegID . 73 11.1.13 Expiration of TSRF73 12 Services assumed from TCAP 74 12.1 Normal procedures 74 12.1.1 SCF-to/from-SRF messages 74 12.2 Abnormal procedures 74 12

34、.2.1 SCF-to-SRF messages . 74 12.2.2 SRF-to-SCF messages . 75 12.3 Dialogue handling. 75 12.3.1 Dialogue establishment 75 12.3.2 Dialogue continuation 75 12.3.3 Dialogue termination . 75 12.3.4 User abort 75 12.3.5 Provider abort 75 12.3.6 Mapping to TC dialogue primitives. 75 12.3.7 Component handl

35、ing 76 ANNEX A ASN.1 definitions. 77 ITU-T Q.1248.3 (07/2001) 1 ITU-T Recommendation Q.1248.3 Interface Recommendation for Intelligent Network Capability Set 4: SCF-SRF interface11 Scope This Recommendation belongs to the Q.1248.x family of ITU-T Recommendations for IN CS-4. It covers the SCF-SRF in

36、terface including the description of the aspects of the Functional Entities SRF and SCF which are relevant to this interface. 2 References All 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 R

37、elationships 4.1 SRF-CCF relationship At present, it is considered that the CCF is under control of the SSF: a SRF-SSF/CCF relationship exists for connection control to specialized resources. The relationship between the SRF and the CCF is not defined (e.g. in the case of releasing a connection on w

38、hich a resource is used). The SRF may contain functionality similar to the CCF to manage bearer connections to specialized resources, but no call model is specified. 4.2 SCF-SRF relationship This SCF-SRF relationship is used when the SCF sends instructions to the SRF. The SCF-SRF relationship could

39、be a direct link or established via a relay through the SSF. In some cases, this SCF-SRF relationship is used when the SCF delegates some of the service logic to the SRF, which executes a specialized type of service logic, known as User Interaction scripts. This can avoid long response times, which

40、are unavoidable if functions are physically distributed over two network nodes: the SCP and the IP. In assisting scenarios the SRF establishes the relationship towards the SCF. 5 SCF FE model The prime function of the Service Control Function (SCF) is the execution of service logic. Service logics i

41、nterface and interact with the Service Switching and Call Control Function for establishing end user interaction to send and receive information. Specialized resources used in the context of end user interaction are managed by the Specialized Resource Function (SRF) and controlled by the Service Con

42、trol functionality. _ 1This Recommendation includes an electronic attachment containing Annex A, ASN.1 definitions. 2 ITU-T Q.1248.3 (07/2001) 6 SRF FE model This clause describes the various components found within an SRF. It is noted that this shows a conceptual model of SRF and is not intended to

43、 imply an actual implementation of the SRF. Main SRF components are: a) Functional Entity Access Manager (FEAM); b) SRF Resource Manager (RM); c) Resources. The SRF Resource Manager is contained in a block called Resource Control Part along with the Resource Logic Library and the Resource Logic Inst

44、ances; it is possible to split the Resources in the following blocks: a) Resource Function Part (RFP); b) Data Part (DP). Enhancements of the SRF components are described in the following subclauses and in Figure 1. ITU-T Q.1248.3 (07/2001) 3 T11106730-02RCPSRFResourceManagerResourceLogic LibraryRes

45、ourceLogic InstancesUI scriptsTransactionModuleSSF/CCF OSFSCFFEAMRFP DPannouncementsvoice recordingsvoice recognitionDTMF collec./detectionModem detectionDB managerrecorded voicesoundimagetextData/BearerControl/SignallingRCP Resource Control PartRFP Resource Function PartFEAM Functionality Entity Ac

46、cess ManagerDP Data PortSDSS Server Display and Script ServiceSDSSText To SpeechFigure 1/Q.1248.3 SRF FE model 6.1 Resource Control Part (RCP) The RCP contains SRF service logic, and controls the service procedure using the capabilities of other blocks. To offer a specialized resource, RCP uses reso

47、urce-function pair in the RFP and data in the DP. Whenever RCP receives a call requesting a specialized resource-function pair, it invokes the internal resource controller, which manages the first needed resource function pair to make a decision of admission or rejection of the call. The SRF sends A

48、CK or NACK messages according to the decision by the resource controller. 4 ITU-T Q.1248.3 (07/2001) There are as many controllers as there are special resource function types. The controllers accept or reject calls requesting a resource-function pair on the basis of characteristic parameters. A con

49、troller consists of an interface unit and a decision unit. First one encodes and decodes messages from/to the FEAM, and makes the input patterns for the decision unit; the characteristic parameter permitting the acceptation or rejection of the call controlled by an algorithm within the decision unit, and is based on the parameters from the interface unit. 6.1.1 SRF Resource Manager The RM provides the functionality which is necessary for the SRF to manage the resources contained in it. The RM contains the capabilities to search for a resource, to al