1、Standard ECMA-2242nd Edition - June 1997Standardizing Information and Communication SystemsPhone: +41 22 849.60.00 - Fax: +41 22 849.60.01 - URL: http:/www.ecma.ch - Internet: helpdeskecma.chPrivate Integrated Services Network(PISN) -Specification, Functional Model andInformation Flows -Transit Coun
2、terAdditional Network Feature.Standard ECMA-2242nd Edition - June 1997Standardizing Information and Communication SystemsPhone: +41 22 849.60.00 - Fax: +41 22 849.60.01 - URL: http:/www.ecma.ch - Internet: helpdeskecma.chIW Ecma-224.doc 25-08-97 14,17Private Integrated Services Network(PISN) -Specif
3、ication, Functional Model andInformation Flows -Transit CounterAdditional Network Feature(ANF-TCSD).Brief HistoryThis Standard is one of a series of ECMA Standards defining services and signalling protocols applicable to Private IntegratedServices Networks (PISNs). The series uses ISDN concepts as d
4、eveloped by ITU-T and conforms to the framework ofInternational Standards for Open Systems Interconnection as defined by ISO/IEC. It has been produced under ETSI work itemDE/ECMA-00145.This particular Standard specifies the Transit Counter additional network feature.This Standard is based upon the p
5、ractical experience of ECMA member companies and the results of their active andcontinuous participation in the work of ISO/IEC JTC1, ITU-T, ETSI and other international and national standardizationbodies. It represents a pragmatic and widely based consensus.Compared to the 1st Edition of Standard E
6、CMA-224 (published by ECMA in June 1995), this 2nd Edition incorporateschanges in order to achieve complete alignment with International Standard ISO/IEC 15055:1997(E) published by ISO/IEC inMay 1997.Differences between this ECMA Standard and the ISO/IEC International Standard with which it is align
7、ed are clearlyidentified.Adopted as 2nd Edition of Standard ECMA-224 by the General Assembly of June 1997.- i -Table of contents1 Scope 12 Conformance 13 References (normative) 14 Definitions 24.1 External definitions 24.2 Other definitions 24.2.1 Additional network feature 24.2.2 Call, basic call 2
8、4.2.3 Signalling connection 24.2.4 Transit counter 25 List of acronyms 26 ANF-TC stage 1 specification 36.1 Description 36.1.1 General description 36.1.2 Qualifications on applicability to telecommunication services 36.2 Procedure 36.2.1 Provision/withdrawal 36.2.2 Normal procedures 36.2.3 Exception
9、al procedures 36.3 Interaction with other supplementary services and ANFs 36.3.1 Calling Line Identification Presentation (SS-CLIP) 36.3.2 Connected Line Identification Presentation (SS-COLP) 36.3.3 Calling/Connected Line Identification Restriction (SS-CLIR) 36.3.4 Calling Name Identification Presen
10、tation (SS-CNIP) 36.3.5 Connected Name Identification Presentation (SS-CONP) 36.3.6 Calling/Connected Name Identification Restriction (SS-CNIR) 46.3.7 Completion of Calls to Busy Subscriber (SS-CCBS) 46.3.8 Completion of Calls on No Reply (SS-CCNR) 46.3.9 Call Transfer (SS-CT) 46.3.10 Call Forwardin
11、g Unconditional (SS-CFU) 46.3.11 Call Forwarding Busy (SS-CFB) 46.3.12 Call Forwarding No Reply (SS-CFNR) 46.3.13 Call Deflection (SS-CD) 46.3.14 Path Replacement (ANF-PR) 46.3.15 Call Interception (ANF-CINT) 46.3.16 Advice of Charge (SS-AOC) 46.3.17 Recall (SS-RE) 46.3.18 Call Offer (SS-CO) 4- ii -
12、6.3.19 Call Intrusion (SS-CI) 46.3.20 Do Not Disturb (SS-DND) 46.3.21 Do Not Disturb Override (SS-DNDO) 46.3.22 Cordless Terminal Location Registration (SS-CTLR) 46.3.23 Cordless Terminal Mobility Incoming Call (ANF-CTMI) 46.4 Interworking considerations 56.5 Overall SDL 57 ANF-TC stage 2 specificat
13、ion 57.1 Functional model 57.1.1 Functional model description 57.1.2 Description of functional entities 67.1.3 Relationship of functional model to basic call functional model 67.2 Information flows 67.2.1 Definition of information flows 67.2.2 Relationship of information flows to basic call informat
14、ion flows 77.2.3 Examples of information flow sequences 77.3 Functional entity actions 87.3.1 Functional entity actions of FE1 87.3.2 Functional entity actions of FE2 87.4 Functional entity behaviour 87.4.1 Behaviour of FE1 87.4.2 Behaviour of FE2 97.5 Allocation of functional entities to physical e
15、quipment 107.6 Interworking considerations 101ScopeThis Standard specifies the Transit Counter additional network feature (ANF-TC), which is applicable to various basicservices supported by Private Integrated Services Networks (PISN). Basic services are specified in ECMA-142.ANF-TC is an additional
16、network feature which limits the number of network exchanges that a call request may transitduring call establishment, e.g. to protect the network against indefinite looping. There is no user involved in theprovision or operation of ANF-TC.Additional network feature specifications are produced in th
17、ree stages, according to the method described in ETS300 387. This Standard contains the stage 1 and stage 2 specifications of ANF-TC. The stage 1 specification (clause 6)specifies the general feature principles and capabilities. The stage 2 specification (clause 7) identifies the functionalentities
18、involved in the feature and the information flows between them.2 ConformanceIn order to conform to this Standard, a stage 3 standard shall specify signalling protocols and equipment behaviour thatare capable of being used in a PISN which supports the feature specified in this Standard. This means th
19、at, to claimconformance, a stage 3 standard is required to be adequate for the support of those aspects of clause 6 (stage 1) andclause 7 (stage 2) which are relevant to the interface or equipment to which the stage 3 standard applies.3 References (normative)The following standards contain provision
20、s which, through reference in this text, constitute provisions of this Standard.All standards are subject to revision, and parties to agreements based on this Standard are encouraged to investigate thepossibility of applying the most recent editions of the standards indicated below.In the case of re
21、ferences to ECMA Standards that are aligned with ISO/IEC International Standards, the number of theappropriate ISO/IEC International Standard is given in brackets after the ECMA reference.ECMA-142 Private Integrated Services Network - Circuit-mode 64 kbit/s Bearer Services - ServiceDescription, Func
22、tional Capabilities and Information Flows (International StandardISO/IEC 11574)ECMA-173 Private Integrated Services Network - Specification, Functional Model and Information Flows -Call Diversion Supplementary Services (International Standard ISO/IEC 13872)ECMA-175 Private Integrated Services Networ
23、k - Specification, Functional Model and Information Flows -Path Replacement Additional Network Feature (International Standard ISO/IEC 13863)ECMA-177 Private Integrated Services Network - Specification, Functional Model and Information Flows -Call Transfer Supplementary Service (International Standa
24、rd ISO/IEC 13865)ECMA-185 Private Integrated Services Network - Specification, Functional Model and Information Flows -Call Completion Supplementary Services (International Standard ISO/IEC 13866)ISO/IEC 11579-1 Information technology - Telecommunications and information exchange between systems -Pr
25、ivate Integrated Services Network - Part 1: Reference configuration for PISN Exchanges(PINX)ETS 300 387 Private Telecommunication Network (PTN); Method for the specification of basic andsupplementary services (1994)ITU-T Rec. I.112 Vocabulary of terms for ISDNs (1993)ITU-T Rec. I.210 Principles of t
26、elecommunication services supported by an ISDN and the means to describe them(1993)ITU-T Rec. Z.100 Specification and description language (1993)- 2 -4 DefinitionsFor the purposes of this Standard, the following definitions apply.4.1 External definitionsThis Standard uses the following terms defined
27、 in other documents: Basic service (ITU-T Rec. I.210) Private Integrated Services Network (PISN) (ISO/IEC 11579-1) Private Integrated Services Network Exchange (PINX) (ISO/IEC 11579-1) Service (ITU-T Rec. I.112) Signalling (ITU-T Rec. I.112) Supplementary Service (ITU-T Rec. I.210) User (ECMA-142)Th
28、is Standard refers to the following basic call functional entity (FE) defined in ECMA-142: Call Control (CC)This Standard refers to the following basic call inter-FE relationship defined in ECMA-142: r2This Standard refers to the following basic call information flows defined in ECMA-142: Setup requ
29、est/indication Setup-Reject request/indication4.2 Other definitions4.2.1 Additional network featureA capability over and above that of a basic call, but not provided directly to a user.4.2.2 Call, basic callAn instance of the use of a basic service.4.2.3 Signalling connectionA connection used to exc
30、hange information between peer supplementary service protocol control entitiesindependently of a basic call.4.2.4 Transit counterA counter for the number of transit exchanges involved in a call or signalling connection during the establishmentphase.5 List of acronymsANF(-TC) Additional Network Featu
31、re (Transit Counter)CC Call Control (functional entity)FE Functional EntityISDN Integrated Services Digital NetworkPINX Private Integrated Services Network ExchangePISN Private Integrated Services NetworkSDL Specification and Description LanguageSS Supplementary Service- 3 -6 ANF-TC stage 1 specific
32、ationThroughout this clause, the term “call” shall be interpreted as meaning “call or signalling connection”.6.1 Description6.1.1 General descriptionANF-TC may be invoked in conjunction with a call request when it is desired to limit the number of networkexchanges that the call can transit. The maxi
33、mum number of network exchanges that the call can transit isnetwork dependent, in the range 1 to 31.6.1.2 Qualifications on applicability to telecommunication servicesANF-TC is applicable to all basic services defined in ECMA-142.6.2 Procedure6.2.1 Provision/withdrawalANF-TC shall be generally avail
34、able for all calls that involve more than one network exchange.6.2.2 Normal procedures6.2.2.1 Activation/deactivation/registration/interrogationNot applicable.6.2.2.2 Invocation and operationANF-TC may be invoked in conjunction with a call request. When invoked, the transit counter shall be set toan
35、 initial value and then incremented with every network exchange that the call request transits. The initialvalue shall be zero unless any knowledge available about the history of the call (e.g. route taken, interworking,diversions) is used to choose a higher initial value.ANF-TC shall terminate when
36、 the call request reaches its destination, is released, or leaves the PISN.6.2.3 Exceptional procedures6.2.3.1 Activation/deactivation/registration/interrogationNot applicable.6.2.3.2 Invocation and operationIf the transit counter exceeds a PISN specific limit (which takes any value in the range 1 t
37、o 31) before the callreaches its destination or leaves the PISN, the call shall be aborted.NOTEOther actions that the PISN may take are outside the scope of this Standard.6.3 Interaction with other supplementary services and ANFsInteractions with other supplementary services and ANFs for which PISN
38、standards were available at the time ofpublication of this Standard are specified below.6.3.1 Calling Line Identification Presentation (SS-CLIP)No interaction.6.3.2 Connected Line Identification Presentation (SS-COLP)No interaction.6.3.3 Calling/Connected Line Identification Restriction (SS-CLIR)No
39、interaction.6.3.4 Calling Name Identification Presentation (SS-CNIP)No interaction.6.3.5 Connected Name Identification Presentation (SS-CONP)No interaction.- 4 -6.3.6 Calling/Connected Name Identification Restriction (SS-CNIR)No interaction.6.3.7 Completion of Calls to Busy Subscriber (SS-CCBS)ANF-T
40、C may apply to a call resulting from the use of SS-CCBS.6.3.8 Completion of Calls on No Reply (SS-CCNR)ANF-TC may apply to a call resulting from the use of SS-CCNR.6.3.9 Call Transfer (SS-CT)ANF-TC may apply to the establishment of the new connection during transfer by rerouteing.6.3.10 Call Forward
41、ing Unconditional (SS-CFU)ANF-TC may be invoked when establishing the diverted call.6.3.11 Call Forwarding Busy (SS-CFB)6.3.10 shall apply.6.3.12 Call Forwarding No Reply (SS-CFNR)6.3.10 shall apply.6.3.13 Call Deflection (SS-CD)6.3.10 shall apply.6.3.14 Path Replacement (ANF-PR)ANF-TC may apply to
42、the establishment of the new connection.6.3.15 Call Interception (ANF-CINT)ANF-TC may be invoked when establishing the intercepted call.6.3.16 Advice of Charge (SS-AOC)No interaction.6.3.17 Recall (SS-RE)No interaction.6.3.18 Call Offer (SS-CO)No interaction.6.3.19 Call Intrusion (SS-CI)No interacti
43、on.6.3.20 Do Not Disturb (SS-DND)No interaction.6.3.21 Do Not Disturb Override (SS-DNDO)No interaction.6.3.22 Cordless Terminal Location Registration (SS-CTLR)No interaction.6.3.23 Cordless Terminal Mobility Incoming Call (ANF-CTMI)ANF-TC may be invoked when establishing the call to the CTM user.Dif
44、ference from ISO/IEC 15055Subclauses 6.3.22 and 6.3.23 do not exist in the ISO/IEC International Standard.End of Difference- 5 -6.4 Interworking considerationsANF-TC may apply to calls entering the PISN from another network or to calls going to another network.6.5 Overall SDLFigure 1 contains the dy
45、namic description of ANF-TC using the Specification and Description Language (SDL)defined in ITU-T Rec. Z.100 (1993). The SDL process represents the behaviour of the PISN in providing ANF-TC.Input symbols from the left and output symbols to the left represent internal stimuli.Call requestpresentinit
46、ialize transit counterTC-IDLEAbortcalllimit exceeded?NOYESTC-COUNTINGCall requestat transitnodeCall clearinginitiatedCall reacheddestination orleft the networkincrement transit counterTC-COUNTINGTC-IDLEFigure 1 - ANF-TC, overall SDL7 ANF-TC stage 2 specificationThroughout this clause, the term “call
47、” shall be interpreted as meaning “call or signalling connection”.7.1 Functional model7.1.1 Functional model descriptionThe functional model shall comprise the following functional entities:FE1 TC InitializeFE2 TC Execute- 6 -The following functional relationship shall exist between these FEs:ra bet
48、ween FE1 and FE2 and between consecutive FE2sFigure 2 shows these FEs and relationship.FE1FE2 FE2ra raFigure 2 - Functional model for ANF-TC7.1.2 Description of functional entities7.1.2.1 TC Initialize, FE1This FE recognises the invocation of ANF-TC, sets the transit counter to its initial value and
49、 passes it to FE2.7.1.2.2 TC Execute, FE2This FE receives the transit counter from FE1 or from another FE2. The following two types of FE2 exist:Intermediate FE2An intermediate FE2 compares the transit counter to the allowed limit. If below the limit, FE2 increments thetransit counter and passes it to the next FE2; otherwise it requests rejection of the call request.Final FE2The final FE2 terminates ANF-TC.7.1.3 Relationship of functional model to basic call functional modelFE1 shall be collocated with the Originating CC, an Incoming Gateway CC, or a Transit CC.An intermediat
