ETSI ETS 300 374-1-1994 Intelligent Network (IN) Intelligent Network Capability Set 1 (CS1) Core Intelligent Network Application Protocol (INAP) Part 1 Protocol Specification《智能网络(.pdf

《ETSI ETS 300 374-1-1994 Intelligent Network (IN) Intelligent Network Capability Set 1 (CS1) Core Intelligent Network Application Protocol (INAP) Part 1 Protocol Specification《智能网络(.pdf》由会员分享，可在线阅读，更多相关《ETSI ETS 300 374-1-1994 Intelligent Network (IN) Intelligent Network Capability Set 1 (CS1) Core Intelligent Network Application Protocol (INAP) Part 1 Protocol Specification《智能网络(.pdf（212页珍藏版）》请在麦多课文档分享上搜索。

1、34045830124b05 T77 ETS 300 374-1 September 1994 Source: ETSI TC-SPS Reference: DEEPS-0301 5 UDC: 621.395 Key words: Intelligent Network Intelligent Network (IN); Intelligent Network Capability Set 1 (CS 1 ) Core Intelligent Network Application Protocol (INAP) Part 1 : Protocol specification ETSI Eur

2、opean Telecommunications Standards Institute ETSI Secretariat Postal address: 06921 Sophia Antipolis Cedex - FRANCE Office address: Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE Tel.: + 33 92 94 42 O0 - Fax: + 33 93 65 47 16 European Telecommunications Standards Institute 1 994. All righ

3、ts reserved. No part may be reproduced except as authorised by written permission. The copyright and the foregoing restriction on reproduction extend to all media in which the information may be embodied. COPYRIGHT European Telecommunications Standards InstituteLicensed by Information Handling Servi

4、ces3404583 OL24bOb 903 Page 2 ETS 300 374-1 : 1994 Whilst every care has been taken in the preparation and publication of this document, errors in content, typographical or otherwise, may occur. If you have comments concerning its accuracy, please write to “ETSI Editing and Standards Approval Dept.“

5、 at the address shown on the title page. COPYRIGHT European Telecommunications Standards InstituteLicensed by Information Handling ServicesW 3404583 0124bO 84T Contents Page 3 ETS 300 374-1 : 1994 Foreword . 13 1 2 3 4 5 6 7 Scope . 15 Normative references 15 Definitions and abbreviations 16 General

6、 . 18 4.1 Definition methodology . 18 4.2 Example physical scenarios 18 4.3 INAP protocol architecture . 25 4.3.1 INAP signalling congestion control for Signalling System No.7 . 26 4.4 INAP addressing 26 4.5 Relationship between ITU-T Recommendation O . 12 14 and this ETS 27 4.6 Compatibility mechan

7、isms used for INAP . 28 4.6.1 Introduction 28 4.6.2 Definition of ETSI INAP compatibility mechanisms . 28 Compatibility mechanism for interworking of ETSI INAP and ITU-T Q.1218 INAP 28 Procedures for major additions to ETSI INAP 29 Procedures for minor additions to ETSI INAP 29 Procedures for inclus

8、ion of network specific additions to ETSI INAP . 29 4.6.2.1 4.6.2.2 4.6.2.3 4.6.2.4 Single/Multiple Association Control Function (SACF/MACF) rules . 29 Reflection of TCAP Application Context (AC) . 29 Sequential/parallel execution of operations. 29 5.1 5.2 Abstract syntax of the CS1 INAP 30 6.1 6.2

9、IN CS1 error types . 39 6.3 6.4 6.5 IN CS1 operation types . 31 IN CS1 data types 40 IN CS1 application protocol (operation and error codes) . 54 IN CS1 application contexts . 58 Application entity procedures . 60 SSF application entity procedures . 60 7.1.1 General 60 Model and interfaces . 60 SSF

10、state transition diagram . 64 State b: “Trigger Processing“ . 68 State c: “Waiting for Instructions“ 68 State d: “Waiting for End of User Interaction“ 70 State e: “Waiting for End of Temporary Connection“ . 70 State f: “Monitoring“ 71 Assisting/hand-off SSF FSM . 72 State b: “Waiting for Instruction

11、s“ 73 7.1 7.1.2 7.1.3 7.1.4 7.1.5 Relations between SSF FSM and the CCF and maintenance functions . 61 SSF Management Entity (SSME) FSM 63 7.1.5.1 State a: “Idle“ 67 7.1 -5.2 7.1.5.3 7.1.5.4 7.1.5.5 7.1.5.6 7.1.6.1 7.1.6.2 7.1.6.3 7.1.6 State a: “Idle“ 73 State c: “Waiting for End of User Interactio

12、n“ 74 COPYRIGHT European Telecommunications Standards InstituteLicensed by Information Handling ServicesW 3404583 0324608 786 Page 4 ETS 300 374-1 : 1994 7.2 7.3 SCF application entity procedures . 75 7.2.1 General . 75 7.2.2 Model and Interfaces 75 7.2.3 Relationship between the SCF FSM and Service

13、 Logic Programs (SLPsl/maintenance functions 76 7.2.4 Partial SCF Management Entity (SCME) state transition diagram . 78 7.2.4.1 State M3: “Service Filtering Idle“ . -78 7.2.4.2 State M4: “Waiting for SSF Service Filtering 7.2.4.3 The Resource Control Object (RCO) . 79 The SCF Call State Model (SCSM

14、) 79 7.2.5.1 State 1 : “Idle“ 82 7.2.5.2 State 2: “Preparing SSF Instructions“ 82 7.2.5.2.1 State 2.1 : “Preparing SSF Instructions“ . 83 7.2.5.2.2 State 2.2 “Queueing FSM“ . 85 7.2.5.2.3 State 2.3: “Waiting for Notification or Request“ 87 State 3: “Routing to Resource“ . 88 7.2.5.3.1 State 3.1 : “D

15、etermine Mode“ 89 7.2.5.3.2 State 3.2: “Waiting for Assist Response“ -78 7.2.5 7.2.5.3 Request Instructions“ -90 State 4: “User Interaction“ . 90 State 4.1 “Waiting for Response from the SRF“ . 91 SRF application entity procedures 92 7.3.1 General . 92 Model and interfaces 93 connection handling . 9

16、3 State 1 : “Idle“ 96 State 2: “Connected“ 97 State 3: “User Interaction“ . 97 Example SRF control procedures 98 SRF connect procedures 99 SRF connect physical procedures -99 SRF end user interaction procedures 103 SRF disconnection procedures 104 7.3.5.3.1 SRF initiated disconnect . 105 7.3.5.3.2 S

17、CF initiated disconnect . 106 Examples illustrating complete user interaction sequences . 107 7.3.5.4.1 Message sequences for service assist . 111 7.3.5.4.2 Message sequences for hand-off 112 7.2.5.4 7.2.5.4.1 7.3.2 7.3.3 7.3.4 Relationship between the SRF FSM and maintenance functionslbearer The SR

18、F Call State Model (SRSM) 95 7.3.4.1 7.3.4.2 7.3.4.3 7.3.5.1 7.3.5.2 7.3.5 7.3.5.1.1 7.3.5.2.1 Play Announcement/Prompt and Collect user information (PA/P Part 2: “Protocol Implementation Conformance Statement (PICS) proforma“; Part 3: “Test Suite Structure and Test Purposes (TSS Part 4: “Abstract T

19、est Suite (ATS) and partial Protocol Implementation extra Information for Testing (PIXIT) proforma“; Part 5: “Protocol specification for the SCF-SDF interface“; Part 6: “PICS proforma for the SCF-SDF interface“. Transposition dates Date of latest announcement of this ETS (doa): 31 December 1994 Date

20、 of latest publication of new National Standard or endorsement of this ETS (dop/e): Date of withdrawal of any conflicting National Standard (dow): 30 June 1995 30 June 1995 I COPYRIGHT European Telecommunications Standards InstituteLicensed by Information Handling ServicesH 3404583 OL24b18 625 H Pag

21、e 15 ETS 300 374-1 : 1994 1 Scope This first part of ETS 300 374 defines the Intelligent Network Application Protocol (INAP) required for support of Capability Set 1 (CS1). It supports interactions between the following three Functional Entities (FES), as defined in the Intelligent Network (IN) func

22、tional model: - Service Switching Function (SSF); - Service Control Function (SCF); - Specialized Resource Function (SRF). The scope of this ETS is the further development of the INAP for both the Integrated Services Digital Network (ISDN) and Public Switched Telecommunications Network (PSTN). It is

23、 intended as a guide to implementors and network operators to ensure interworking between different manufacturers equipment for the following IN CS1 defined interfaces (SCF-SSF and SCF-S RF) . As this ETS is intended for the early introduction of IN in the existing ISDN/PSTN, only simple solutions a

24、re assumed for solving the service interaction problems between IN and ISDN/PSTN. NOTE: More sophisticated solutions for the service interactions between IN and the ISDN/PSTN environment should be studied in the scope of future versions of INAP and the ISDN/PSTN signalling standards. 2 Normative ref

25、erences This ETS incorporates by dated and undated reference, provisions from other publications. These normative references are cited at the appropriate places in the text and the publications are listed hereafter. For dated references, subsequent amendments to or revisions of any of these publicat

26、ions apply to this ETS only when incorporated in it by amendment or revision. For undated references the latest edition of the publication referred to applies. ll 21 i31 i41 51 61 ETS 300 008 (1 993): “Integrated Services Digital Network (ISDN); CCITT Signalling System No.7; Message Transfer Part (M

27、TP) to support international interconnection“. ETS 300 O09 (1 9941: “Integrated Services Digital Network (ISDN); CCITT Signalling System No.7; Signalling Connection Control Part (SCCP) connectionless and connection-oriented to support international interconnection“. ETS 300 121 (1 992): “Integrated

28、Services Digital Network (ISDN); Application of the ISDN User Part (ISUP) of CCITT Signalling System No.7 for international ISDN interconnections (ISUP version 1 1“. ETC 300 196-1 (1 993): “Integrated Services Digital Network (ISDN); Generic functional protocol for the support of supplementary servi

29、ces; Digital Subscriber Signalling System No. one (DSS11 protocol; Part 1 : Protocol specification“. NOTE: ETS 300 196-1 (1 993) was initially published as ETS 300 196 (1 9931 ETS 300 287 (1 993): “Integrated Services Digital Network (ISDN); CCITT Signalling System No.7; Transaction Capabilities App

30、lication Part (TCAP) version 2“. ETS 300 348 (1 994): “Intelligent Network (IN); Physical plane for intelligent network Capability Set 1 (CS1 1 ITU-T Recommendation 0.1 21 5 (1 99311“. Previous page is blank COPYRIGHT European Telecommunications Standards InstituteLicensed by Information Handling Se

31、rvices= 3404583 0324637 561 Page 16 ETS 300 374-1 : 1994 i71 181 i91 I101 lll 121 t131 i1 41 il 51 11 61 t171 181 ETS 300 356-1 : “Integrated Services Digital Network (ISDN); CCITT Signalling System No.7; ISDN User Part (ISUP) version 2 for the international interface; Part 1 : Basic services“. ETS

32、300 403-1 : “Integrated Services Digital Network (ISDN); Digital Subscriber Signalling System No. one (DSS 1 1; User-network interface layer 3 specification for basic call control; Part 1 : Protocol specification IITU-T Recommendation 0.931 (1 9931, modified“. ITU-T Recommendation 0.700 (1 993): “In

33、troduction to CCITT Signalling System No.7“. ITU-T Recommendation O. 773 4 1 993) : “Specifications of Signalling System No.7; Transaction Capabilities formats and encoding“. ITU-T Recommendation 0. 121 4 Il 993): “Distributed functional plane for intelligent network CS1 I. ITU-T Recommendation 0.1

34、21 8 (1 993): “Interface Recommendation for intelligent network CS1 “. ITU-T Recommendation 0.1 400 (1 993): “Architecture framework for the development of signalling and organization, administration and maintenance protocols using OS1 principles“. CCITT Recommendation X.208 (1 988): “Specification

35、of Abstract Syntax Notation One (ASN.l I“. CCITT Recommendation X.209 (1 988): “Specification of basic encoding rules for Abstract Syntax Notation One (ASN. 1 1“. CCITT Recommendation X.219 (1 988): “Remote operations: Model, notation and service definition“. CCITT Recommendation X.229 (1 988): “Rem

36、ote operations: Protocol specification“. IS0 9545 (1 989): “Information technology - Open Systems Interconnection - Application Layer structure“. 3 Definitions and abbreviations For the purposes of this ETS, the following abbreviations apply: AC A AEI ASE APDU ASN. 1 BCSM CCF cs 1 Application Contex

37、t Application Entity Application Entity Invocation Application Service Element Application Protocol Data Unit Abstract Syntax Notation One Basic Call State Model Call Control Function Capability Set 1 COPYRIGHT European Telecommunications Standards InstituteLicensed by Information Handling Services3

38、404583 0124620 283 Page 17 ETS 300 374-1 : 1994 DP DSS 1 EDP EDP-N EDP-R FCI FE FEAM FSM ID IN INAP IP ISDN ISPBX ISUP LE MACF MTP P - the definition of the operations transferred between entities (Clause 6); - the definition of the actions taken at each entity (Clause 7). The SACF/MACF rules are de

39、fined in prose. The operation definitions are in Abstract Syntax Notation 1 (ASN.l, see CCITT Recommendation X.208 i1411, and the actions are defined in terms of state transition diagrams. Further guidance on the actions to be performed on receipt of an operation can be gained from Clause 6 and from

40、 the relevant detailed procedures in Clause 7. The INAP is a Remote Operations Service Element (ROSE) user protocol (see CCITT Recommendations X.219 1161 and X.229 171). The ROSE protocol is contained within the Digital Subscriber Signalling System No. One (DSS1, see ETS 300 196-1 41) and the Compon

41、ent Sublayer of the Transaction Capabilities Application Part (TCAP, see ETS 300 287 51). NOTE 1: At present, the ROSE Application Protocol Data Units (APDUs) are conveyed in Transaction sublayer messages in Signalling System No.7 (Signalling System No.7) and in the Q.931 FACILITY and Call Control m

42、essages in DSS1 (see ETS 300 403-1 81). Other supporting protocols may be added at a later date. NOTE 2: The INAP (as a ROSE user) and the ROSE protocol have been specified using ASN.l. At present, the only standardized way to encode the resulting PDUs is the Basic Encoding Rules (see CCITT Recommen

43、dation X.209 i1 51). 4.2 Example physical scenarios The protocol supports any mapping of functional to Physical Entities (PES), see ETS 300 348 61 (ITU-T Recommendation 0.1 21 5). It is the responsibility of network operators and equipment manufacturers to decide how to co-locate FES to the best pos

44、sible advantage as this may vary between manufacturers and between network operators. Therefore the protocol is defined assuming maximum distribution (.e. one PE per FE). The figures depicted in this subclause show how INAP would be supported in an Signalling System No.7 network environment. This do

45、es not imply that only Signalling System N0.7 may be used as the network protocol to support INAP. When TCAP appears in one of the following figures, it is to be understood as representing the TCAP functionalities associated with a single dialogue and transaction (as opposed to a TCAP entity). For e

46、ach physical scenario, the typical SRF control procedures to be applied are shown in subclause 7.3.5. The interface between remotely located SCF and SDF is INAP using TCAP which in turn uses the services of the connectionless SCCP and MTP (see figure 1). The SDF is responsible for any interworking t

47、o other protocols to access other types of networks. COPYRIGHT European Telecommunications Standards InstituteLicensed by Information Handling Servicesmp3404583 0324622 056 Type of signalling system between SSF and SRF ISUP DSS 1 implementation dependent Page 19 ETS 300 374-1 : 1994 Method to suppor

48、t SCF-SRF relationship direct TCAP link figure 2 figure 5 figure 6 figure 3 as figures 2 or 6 but with figure 4 implementation dependent SCP-IP interface relay via SSP II I MACF I I bl ASE(s) ASE(s) 6, SCCP MTP I I SDF I I ASE(s) i 1 (SCF-SDF) 1 TCAP 1 SCCP 6 SS No. 7 Link 6 SS No. 7 Link SS No. 7 N

49、etwork I To SSP SS No. 7 Link Figure 1 : Physical interface between SCP and SDP A number of example scenarios have been identified for support of the SCF, SSF and SRF FES as PES. These are illustrated as figures 2 to 6. Each example is characterized by: a) the method to support SCF-SRF relationship; and b) the type of signalling system between SSF and SRF. Table 1 summarizes the selection of features for each figure. Table 1 COPYRIGHT European Telecommunications Standards InstituteLicensed by Information Handling Services3404583 0324623 T92 II Page 20 ETS 300 374-1 19