ECMA 250-1998 Private Integrated Services Network (PISN) Specification Functional Model and Information Flows - Common Information Additional Network Feature《专用综合业务网络(PISN) 规范 功能模型.pdf

1、Standard ECMA-2502nd Edition - December 1998Standardizing 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 -Common I

2、nformation AdditionalNetwork Feature.Standard ECMA-2502nd Edition - December 1998Standardizing Information and Communication SystemsPhone: +41 22 849.60.00 - Fax: +41 22 849.60.01 - URL: http:/www.ecma.ch - Internet: helpdeskecma.chIW Ecma-250.doc 06-01-99 10,46Private Integrated Services Network(PI

3、SN) -Specification, Functional Model andInformation Flows -Common Information AdditionalNetwork Feature(ANF-CMNSD).Brief HistoryThis Standard is one of a series of ECMA standards defining services and signalling protocols applicable to Private IntegratedServices Networks. The series uses the ISDN co

4、ncepts as developed by ITU-T (formerly CCITT) and is also within theframework of standards for open systems interconnection as defined by ISO. It has been produced under ETSI work itemDE/ECMA-00070.This Standard specifies the Common Information additional network feature.The Standard is based upon t

5、he practical 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.There is currently no equivalent feat

6、ure specified by ITU-T or ETSI for public ISDNs.Compared to the 1st Edition of Standard ECMA-250 (published by ECMA in December 1996), this 2nd Edition incorporateschanges to achieve complete alignment with International Standard ISO/IEC 15771:1998(E) published by ISO/IEC inNovember 1998.Adopted as

7、2nd Edition of Standard ECMA-250 by the General Assembly of December 1998.- i -Table of contents1 Scope 12 Conformance 13 References (normative) 14 Definitions 14.1 External definitions 14.2 Additional Network Feature 24.3 ANF-CMN User 24.4 Backward direction 24.5 Call, Basic Call 24.6 Common Inform

8、ation 24.7 Feature Identifier 24.8 Forward direction 24.9 Equipment Identity 24.10 Node Identity 34.11 Group Identity 34.12 Unit Identity 34.13 Party Category 35 List of acronyms 36 ANF-CMN stage 1 specification 36.1 Description 36.1.1 General description 36.1.2 Qualifications on Applicability to Te

9、lecommunication Services 46.2 Procedures 46.2.1 Provision/Withdrawal 46.2.2 Normal procedures 46.2.3 Exceptional procedures 46.3 Interactions with other Supplementary Services and ANFs 46.3.1 Calling Line Identification Presentation (CLIP) 46.3.2 Connected Line Identification Presentation (COLP) 46.

10、3.3 Calling/Connected Line Identification Restriction (CLIR) 46.3.4 Calling Name Identification Presentation (CNIP) 46.3.5 Connected Name Identification Presentation (CONP) 46.3.6 Calling/Connected Name Identification Restriction (CNIR) 46.3.7 Call Forwarding Unconditional (CFU) 56.3.8 Call Forwardi

11、ng Busy (CFB) 56.3.9 Call Forwarding No Reply (CFNR) 56.3.10 Call Deflection (CD) 56.3.11 Call Transfer (CT) 5- ii -6.3.12 Completion of Calls to Busy Subscriber (CCBS) 56.3.13 Completion of Calls on No Reply (CCNR) 56.3.14 Call Intrusion (CI) 56.3.15 Call Offer (CO) 56.3.16 Do Not Disturb (DND) 56.

12、3.17 Do Not Disturb Override (DNDO) 56.3.18 Call Interception (CINT) 56.3.19 Advice Of Charge (AOC) 56.3.20 Message Waiting Indication (MWI) 56.3.21 Path Replacement (PR) 56.3.22 Recall (RE) 56.3.23 Cordless Terminal Mobility, Outgoing call (CTMO) 66.3.24 Cordless Terminal Mobility, Incoming call (C

13、TMI) 66.3.25 Cordless Terminal, Location Registration (CTLR) 66.3.26 Cordless Terminal, Authentication (CTAN, CTAT) 66.3.27 Transit Counter (TC) 66.4 Interworking considerations 66.5 Overall SDL 67 ANF-CMN stage 2 specification 87.1 Functional Model 87.1.1 Functional Model Description 87.1.2 Descrip

14、tion of Functional Entities 87.1.3 Relationship of Functional Model to Basic Call Functional Model 87.2 Information Flows 97.2.1 Definition of Information Flows 97.2.2 Relationship of Information Flows to Basic Call Information Flows 127.2.3 Information Flow Sequences 127.3 Functional entity actions

15、 147.3.1 Functional entity actions of FE1 147.3.2 Functional entity actions of FE2 147.4 Functional entity behaviour 147.4.1 Behaviour of FE1 157.4.2 Behaviour of FE2 167.5 Allocation of Functional Entities to Physical Equipment 167.6 Interworking considerations 16Annex A - Party category and Equipm

16、ent Identity 191ScopeThis Standard specifies the additional network feature Common Information (ANF-CMN), which is applicable tovarious basic services supported by Private Integrated Services Networks (PISN). Basic services are specified inECMA-142.ANF-CMN is an additional network feature which enab

17、les the exchange of Common Information between entitiesacting on behalf of the two ends of a connection through a PISN. This Common Information is a collection ofmiscellaneous information that relates to the user or equipment at one end of a connection and includes one or more ofthe following: Featu

18、re Identifiers, Party Category, Equipment Identity. This information, when received by an entity,can be used for any purpose, e.g. as the basis for indications to the local user or to another network or in order to filterfeature requests.Additional network feature specifications are produced in thre

19、e stages, according to the method described inETS 300 387. This Standard contains the stage 1 and stage 2 specifications of ANF-CMN. The stage 1 specification(clause 6) specifies the additional network feature as seen by users of the feature. The stage 2 specification (clause 7)identifies the functi

20、onal entities involved in the additional network 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 additional netwo

21、rk feature specified in this Standard. Thismeans that, to claim conformance, a stage 3 standard is required to be adequate for the support of those aspects ofclause 6 (stage 1) and clause 7 (stage 2) which are relevant to the interface or equipment to which the stage 3 standardapplies.3 References (

22、normative)The following standards contain provisions which, through reference in this text, constitute provision 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

23、of the standards indicated below.In the case of references 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-133 Private Integrated Services Network - Reference Confi

24、guration for PISN Exchanges (PINX)(International Standard ISO/IEC 11579-1)ECMA-142 Private Integrated Services Network (PISN) - Circuit-mode 64 kbit/s bearer services - Servicedescription, functional capabilities and information flows (International StandardISO/IEC 11574)ETS 300 387 Private Telecomm

25、unication 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 telecommunication services supported by an ISDN and the means to describe them(1993)ITU-T Rec. Z.100 Specification and de

26、scription language (1993)4 DefinitionsFor the purpose of this Standard the following definitions apply.4.1 External definitionsThis Standard uses the following terms defined in other documents:G01 Basic Service (ITU-T Rec. I.210)G01 Connection (ITU-T Rec. I.112)- 2 -G01 Private Integrated Services N

27、etwork (PISN) (ECMA-133)G01 Private Integrated Services Network Exchange (PINX) (ECMA-133)G01 Service (ITU-T Rec. I.112)G01 Signalling (ITU-T Rec. I.112)G01 Supplementary Service (ITU-T Rec. I.210)G01 User (except in the context of ANF-CMN user) (ECMA-142)This Standard refers to the following basic

28、call functional entities (FEs) defined in ECMA-142:G01 Call Control (CC)G01 Call Control Agent (CCA)This Standard refers to the following basic call inter-FE relationships defined in ECMA-142:G01 r1G01 r2G01 r3This Standard refers to the following basic call information flows defined in ECMA-142:G01

29、 SETUP request/indicationG01 SETUP response/confirmation4.2 Additional Network FeatureA capability, over and above that of a basic service, provided by a PISN, but not directly to a PISN user.4.3 ANF-CMN UserAn entity that acts on behalf of one end of a connection through a PISN by using ANF-CMN to

30、exchange CommonInformation with a peer entity acting on behalf of the other end of the connection.4.4 Backward directionWithin the context of a call, the direction from the called user towards the calling user.4.5 Call, Basic CallAn instance of the use of a basic service.4.6 Common InformationInform

31、ation relating to the user or equipment at one end of a connection through a PISN. This information includesone or more of the following: Feature Identifiers, Party Category, Equipment Identity.4.7 Feature IdentifierIn the context of a particular call, an indication of the availability of a suppleme

32、ntary service or ANF or of aparticular capability of a supplementary service or ANF.4.8 Forward directionWithin the context of a call, the direction from the calling user towards the called user.4.9 Equipment IdentityA unique identity, three-level structured consisting of Node identity, Group identi

33、ty, Unit identity.NOTEThe purpose of the Equipment Identity is to indicate, to another user or to another PINX, information about acalling or called party involved in a call. Assignment of network wide unique Equipment Id values is outside thescope of this Standard.- 3 -4.10 Node IdentityThe identit

34、y of the PINX at which a unit of equipment is located.4.11 Group IdentityWithin the context of a PINX, the identity of the group of equipment to which a unit of equipment belongs.4.12 Unit IdentityWithin the context of a PINX or a group of equipment within a PINX, the identity of a unit of equipment

35、.4.13 Party CategoryIndicates the category of a party involved in a call.NOTEThe purpose of the Party Category is to indicate to the other end of a connection the category of a user involved ina call. A received Party Category information may be used for display at the users terminal or for the PISN

36、-internal call handling process, e.g. depending whether the calling party is an extension or PISN attendant, the callhandling may invoke different options of a supplementary service related to that call.5 List of acronymsANF Additional Network FeatureANF-CMN Additional Network Feature Common Informa

37、tionCC Call Control (functional entity)CCA Call Control Agent (functional entity)FE Functional EntityFI Feature IdentifierISDN Integrated Services Digital NetworkPINX Private Integrated Services Network ExchangePISN Private Integrated Services NetworkSDL Specification and Description LanguageSS Supp

38、lementary Service6 ANF-CMN stage 1 specification6.1 Description6.1.1 General descriptionANF-CMN is an additional network feature which enables the exchange of Common Information between ANF-CMN users acting on behalf of the two ends of a connection through a PISN. This Common Information is acollect

39、ion of miscellaneous information that relates to the user or equipment at one end of a connection andincludes one or more of the following: Feature Identifiers, Party Category, Equipment Identity. This information,when received by an ANF-CMN user, can be used for any purpose, e.g. as the basis for i

40、ndications to the localuser or to another network or in order to filter feature requests.A solicited and an unsolicited service can be offered to an ANF-CMN user (which may be located at either endof a connection).The solicited service enables the ANF-CMN user to request the Common Information from

41、a peer ANF-CMNuser.The unsolicited service enables an ANF-CMN user to supply Common Information to a peer ANF-CMN user.These services may be combined and are not mutually exclusive.- 4 -6.1.2 Qualifications on Applicability to Telecommunication ServicesANF-CMN is applicable to all circuit-mode basic

42、 services defined in ECMA-142.6.2 Procedures6.2.1 Provision/WithdrawalANF-CMN shall be PISN instigated.6.2.2 Normal procedures6.2.2.1 Activation/Deactivation/Registration/InterrogationNot applicable.6.2.2.2 Invocation and operationThe conditions under which ANF-CMN is invoked shall be an implementat

43、ion matter. Also, CommonInformation offered by a PISN shall be an implementation matter.An ANF-CMN user may invoke ANF-CMN at any time during a callG01 to send its own Common Information to the peer ANF-CMN user (unsolicited service), orG01 to request the Common Information of the peer ANF-CMN user

44、(solicited service).Sending and requesting the Common Information may be combined.NOTETypically the Common Information is exchanged during the establishment of a call.On receiving a request for Common Information the receiving ANF-CMN user shall respond with its CommonInformation.6.2.3 Exceptional p

45、rocedures6.2.3.1 Activation/Deactivation/Registration/InterrogationNot applicable.6.2.3.2 Invocation and OperationIf no response is received on a request for Common Information (solicited service), the action to be taken shallbe implementation dependent.6.3 Interactions with other Supplementary Serv

46、ices and ANFsInteractions with other supplementary services and ANFs for which PISN standards were available at the time ofpublication of this Standard are specified below.6.3.1 Calling Line Identification Presentation (CLIP)No interaction.6.3.2 Connected Line Identification Presentation (COLP)No in

47、teraction.6.3.3 Calling/Connected Line Identification Restriction (CLIR)No interaction.6.3.4 Calling Name Identification Presentation (CNIP)No interaction.6.3.5 Connected Name Identification Presentation (CONP)No interaction.6.3.6 Calling/Connected Name Identification Restriction (CNIR)No interactio

48、n.- 5 -6.3.7 Call Forwarding Unconditional (CFU)Common Information relating to the originating end of a call sent at the time of the call establishment requestshall, if the call is diverted, be diverted to the ANF-CMN user at the terminating end of the diverted call.6.3.8 Call Forwarding Busy (CFB)C

49、lause 6.3.7 shall apply.6.3.9 Call Forwarding No Reply (CFNR)Unsolicited Common Information relating to the originating end of a call sent at the time of the call establishmentrequest shall, if the call is diverted, be diverted to the ANF-CMN user at the terminating end of the diverted call.A request for solicited Common Information relating to the originating end of a call sent at the time of the callestablishment request shall not, if the call is diverted, be diverted to the ANF-CMN user at the terminating end ofthe diverted call.6.3.10 Call Deflection (CD)In case of Call Deflection