ECMA 161-1993 PRIVATE TELECOMMUNICATION NETWORKS - SIGNALLING AT THE S REFERENCE POINT - GENERIC FEATURE KEY MANAGEMENT PROTOCOL FOR THE CONTROL OF SUPPLEMENTARY SERVICES (PTN SSIG.pdf

《ECMA 161-1993 PRIVATE TELECOMMUNICATION NETWORKS - SIGNALLING AT THE S REFERENCE POINT - GENERIC FEATURE KEY MANAGEMENT PROTOCOL FOR THE CONTROL OF SUPPLEMENTARY SERVICES (PTN SSIG.pdf》由会员分享，可在线阅读，更多相关《ECMA 161-1993 PRIVATE TELECOMMUNICATION NETWORKS - SIGNALLING AT THE S REFERENCE POINT - GENERIC FEATURE KEY MANAGEMENT PROTOCOL FOR THE CONTROL OF SUPPLEMENTARY SERVICES (PTN SSIG.pdf（44页珍藏版）》请在麦多课文档分享上搜索。

1、EUROPEAN COMPUTER MANUFACTURERS ASSOCIATIONSTANDARD ECMA-161PRIVATE TELECOMMUNICATION NETWORKS-SIGNALLING AT THE S REFERENCE POINT-GENERIC FEATURE KEY MANAGEMENT PROTOCOLFOR THE CONTROL OF SUPPLEMENTARY SERVICES(PTN SSIG-FK)2nd Edition - June 1993EUROPEAN COMPUTER MANUFACTURERS ASSOCIATIONSTANDARD E

2、CMA-161PRIVATE TELECOMMUNICATION NETWORKS-SIGNALLING AT THE S REFERENCE POINT-GENERIC FEATURE KEY MANAGEMENT PROTOCOLFOR THE CONTROL OF SUPPLEMENTARY SERVICES(PTN SSIG-FK)2nd Edition - June 1993Brief HistoryThis Standard is one of a series of ECMA standards defining services and signalling protocols

3、 applicable to PrivateTelecommunication Networks (PTNs). The series uses the ISDN concepts as developed by the ITU-TS and is also within theframework of standards for open systems interconnection as defined by ISO. It has been produced under ETSI IMCC workitem DE/ECMA-00027.This particular Standard

4、defines the feature key management stimulus protocol for use at the S reference point in support ofbasic circuit mode services.The feature key management protocol for Private Telecommunication Networks (PTNs) selects options from andcomplements CCITT Recommendation Q.932. The differences between thi

5、s Standard and the relevant section of Q.932 andthe impact of these differences on terminal interchangeability can be found in annex E.This Standard is based upon the practical experience of ECMA member companies and the results of their active andcontinuous participation in the work of ISO/IEC JTC1

6、, ITU-TS, ETSI and other international and national standardizationbodies. It represents a pragmatic and widely based consensus.Compared to the 1st Edition of Standard ECMA-161 (published by ECMA in December 1991), various changes have beenmade in order to achieve alignment with ETS 300 240 (which i

7、s based on the 1st Edition of ECMA-161 but modified duringPublic Enquiry and published by ETSI in June 1993).Accepted as 2nd Edition of Standard ECMA-161 by the General Assembly of June 1993.- i -Table of contentsPage1 Scope 12 Conformance 13 References 14 Definitions 14.1 Access 14.2 Endpoint Ident

8、ifier (EID) 14.3 Feature 14.4 Feature indication 14.5 Feature request 14.6 Private Telecommunication Network (PTN) 24.7 Private Telecommunication Network Exchange (PTNX) 24.8 Service profile 24.9 Service Profile Identifier (SPID) 24.10 Supplementary Service 24.11 Terminal Equipment (TE) 24.12 Termin

9、al Identifier (TID) 24.13 User 24.14 User Service Identifier (USID) 25 Acronyms and abbreviations 26 Feature Key Management Protocol 26.1 Messages 36.1.1 Messages used in association with a Call Reference 36.1.2 Messages used in association with the Dummy Call Reference 36.1.3 Additional information

10、 elements 36.2 Procedures 46.2.1 TE requests 46.2.2 PTN responses 56.2.3 General aspects 56.2.4 Error conditions 67 Coding of Information Elements 67.1 Dummy call reference 67.2 Calling party number 67.3 Cause 67.4 Display 67.5 Endpoint identifier 67.6 Feature activation 77.7 Feature indication 87.8

11、 Information request 97.9 Keypad facility 107.10 Signal 107.11 Service profile identification 10- ii -7.12 Switchhook 11Annex A - User Service Profiles and Terminal Identification 13Annex B - Information Request Procedures 17Annex C - Illustration of the Feature Key Management Protocol 19Annex D - P

12、rotocol Implementation Conformance Statement (PICS) Proformas 21Annex E - Relationship to Corresponding Standards for Public ISDNs 291 ScopeThis Standard defines the Feature Key Management signalling protocol for the purpose of supplementary servicecontrol at an interface at the S reference point be

13、tween a Terminal Equipment (TE) and a PrivateTelecommunication Network (PTN).The Feature Key Management protocol operates in conjunction with the signalling protocol specified in StandardETS 300 192 for circuit-switched call control. It is based on the use of the two information elements, Featureact

14、ivation and Feature indication. While the procedures associated with feature key invocation and indication arespecified in this Standard, the allocation of actual codes used to designate individual supplementary services isoutside the scope of this Standard.This Standard is applicable to the user ac

15、cesses of PTNs and to TEs which are intended for connection to PTNs.2 ConformanceIn order to conform to this Standard, a PTNX shall satisfy the requirements identified in the Protocol ImplementationConformance Statement (PICS) proforma in sub-clause D.3 of annex D.In order to conform to this Standar

16、d, a TE shall satisfy the requirements identified in the Protocol ImplementationConformance Statement (PICS) proforma in sub-clause D.4 of annex D.3 ReferencesECMA-105 Private Telecommunication Networks (PTN) - Signalling at the S Reference Point - Data LinkLayer Protocol (SSIG-L2) (1993)ETS 300 102

17、-1 Integrated Services Digital Network (ISDN); User-network interface layer 3; Specification forbasic call control; Application of CCITT Rec. Q.930/I.450 and Rec. Q.931/I.451 (1990)ETS 300 189 Private Telecommunication Network (PTN); Addressing (1992)ETS 300 192 Private Telecommunication Network (PT

18、N); Signalling protocol at the S-reference point;Circuit mode basic services (1992)CCITT Rec. I.112 Vocabulary of terms for ISDNs (1988)CCITT Rec. Q.932 Generic procedures for the control of ISDN supplementary services (1988)ENV 41007 Definition of terms in private telecommunication networks (1989)4

19、 DefinitionsFor the purpose of this Standard the following definitions apply.4.1 AccessThe definition of CCITT Rec. I.112 for “user-network access“ shall apply, with “telecommunication network“being interpreted as “PTN“.4.2 Endpoint Identifier (EID)Information used for terminal identification. The e

20、ndpoint identifier parameters contain a USID and TID andadditional information used to interpret them.4.3 FeatureA supplementary service or a user-initiated PTN action which constitutes one specific part of a supplementaryservice.4.4 Feature indicationAn indication of the status of a feature from th

21、e PTN to the user.4.5 Feature requestThe initiation of a feature by the user.- 2 -4.6 Private Telecommunication Network (PTN)The definition in ENV 41007 shall apply.4.7 Private Telecommunication Network Exchange (PTNX)The definition in ENV 41007 shall apply.4.8 Service profileThe information that th

22、e PTN maintains for a given user to characterize the service offered by the PTN to thatuser. As an example, this may contain the association of feature identifiers with specific supplementary services. Aservice profile may for example be allocated to a PTN access interface or to a particular TE or a

23、 group of TEs.4.9 Service Profile Identifier (SPID)Identifies a specific service profile in the case that a TE asks for automatic assignment of a USID and TID by thePTN. The SPID allows the PTN to distinguish between different terminals that would otherwise beindistinguishable (e.g. same PTN number)

24、. The SPID value is provided to the user when installing a serviceprofile and should uniquely identify that service profile.4.10 Supplementary ServiceA capability provided by a PTN to a PTN user over and above that of a basic call.4.11 Terminal Equipment (TE)The definition in ENV 41007 shall apply.4

25、.12 Terminal Identifier (TID)Identifies a terminal uniquely within a given USID. If two TEs on an interface have the same service profile thetwo TEs will be assigned the same USID. However, two different TIDs are required to uniquely identify each ofthe two TEs.4.13 UserThe definition in ENV 41007 s

26、hall apply.4.14 User Service Identifier (USID)Uniquely identifies a service profile on a PTN access interface.5 Acronyms and abbreviationsCEI Connection Endpoint IdentifierCES Connection Endpoint SuffixEID Endpoint IdentifierISDN Integrated Services Digital NetworkPICS Protocol Implementation Confor

27、mance StatementPTN Private Telecommunication NetworkPTNX Private Telecommunication Network ExchangeSAPI Service Access Point IdentifierSPID Service Profile IdentifierTE Terminal EquipmentTEI Terminal Endpoint IdentifierTID Terminal IdentifierUSID User Service Identifier6 Feature Key Management Proto

28、colNOTE 1The text in this clause is based on section 5 of CCITT Rec. Q.932. Differences are indicated by emboldening.The Feature Key management protocol is a mechanism allowing users to invoke supplementary services. As these arestimulus procedures, the protocol elements do not directly identify the

29、 service invoked. To determine the service- 3 -invoked requires knowledge of the users service profile maintained in the PTN. No call state changes occur directlyas a result of these procedures.The Feature Key management protocol is based on two information elements: Feature activation and Featurein

30、dication. The Feature activation information element is the means by which a user requests a supplementaryservice. The Feature activation information element contains a feature identifier number which the PTN maps to thecorresponding service as indicated by that users service profile. The TE need no

31、t have any knowledge of whatservice is being indicated by the feature identifier number and the user may send a feature request at any time.Feature indication is the means by which a response to a feature request is indicated by the PTN. The featureidentifier number correlates the PTNs response with

32、 a users request and/or an indicator associated with a TE. TheFeature indication information element also contains a status indicator. The status indicator indicates the status of therequested service and may be used by the TE as appropriate with its man-machine interface.6.1 Messages6.1.1 Messages

33、used in association with a Call ReferenceThe Feature activation and Feature indication information elements may be present in several of the messagesdefined in ETS 300 192. The Feature activation information element may appear in the following messages inthe direction TE to PTN:a) SETUPb) INFORMATIO

34、Nc) ALERTINGd) CONNECTe) DISCONNECTf) RELEASEg) RELEASE COMPLETEThe Feature activation information element may be repeated in a single message.NOTE 2“Activation“ as part of the name “Feature activation“ should not be confused with the term “activation“ usedelsewhere, e.g. in stage 1 descriptions. De

35、pending on the context, “Feature activation“ can mean invocation,activation, deactivation, interrogation etc. of a supplementary service.The Feature indication information element may be sent in the direction PTN to TE in the following messages:a) SETUPb) SETUP ACKNOWLEDGEc) CONNECTd) CALL PROCEEDIN

36、Ge) ALERTINGf) INFORMATIONg) DISCONNECTh) RELEASEi) RELEASE COMPLETEj) CONNECT ACKNOWLEDGEThe Feature indication information element may be repeated in a single message.6.1.2 Messages used in association with the Dummy Call ReferenceOne or more Feature activation information elements may appear in a

37、n INFORMATION message in thedirection TE to PTN.One or more Feature indication information elements may appear in an INFORMATION message in thedirection PTN to TE.6.1.3 Additional information elementsSeveral messages may contain further information elements, in addition to those specified in ETS300

38、192, according to the following list:- 4 -Calling party number: May be included in an INFORMATION message with the dummy callreference in the direction TE to PTN for multiple subscriber numberarrangements (see ETS 300 189).Cause: May be included in an INFORMATION message in the direction PTNto TE (a

39、s response to a feature request).Display: May be included in every message in the direction PTN to TE.Endpoint identifier: May be included in INFORMATION and in SETUP messages (used forthe optional terminal identification procedures described in annex A).Information request: May be included in an IN

40、FORMATION message in the direction PTNto TE (used for the optional information request procedures described inannex B).Keypad facility: May be included in INFORMATION and SETUP messages in thedirection TE to PTN to provide additional information, e.g. inconjunction with the information request proce

41、dures according to annexB.Signal: May be included in the direction PTN to TE in the messages:ALERTINGCONNECTCONNECT ACKNOWLEDGEDISCONNECTINFORMATIONRELEASERELEASE COMPLETESETUPSETUP ACKNOWLEDGEService profile identification: May be included in an INFORMATION message in the direction TE toPTN (used f

42、or the optional automatic assignment procedure described insub-clause A.4 of annex A).Switchhook: May be included in the direction TE to PTN in the messages:CONNECTDISCONNECTINFORMATIONRELEASESETUPThe coding of these information elements is specified in clause 7.6.2 Procedures6.2.1 TE requests6.2.1.

43、1 Feature requests in association with a Call ReferenceThe TE may request a feature by including a Feature activation information element in any of the messagesdefined in 6.1. The TE shall indicate the desired feature by specifying the appropriate value in the featureidentifier number field.An INFOR

44、MATION message may be sent at any time after sending or receiving the first response tothe SETUP message and before sending or receiving a RELEASE or RELEASE COMPLETEmessage.6.2.1.2 Feature requests in association with the Dummy Call ReferenceThe Feature activation information element may be sent in

45、 an INFORMATION message using thedummy call reference in situations where it is inappropriate to use an existing call reference or toestablish a new call reference for the purpose.- 5 -Before sending an INFORMATION message with the dummy call reference the TE must first ensurethat a Data Link connec

46、tion exists between the TE and the PTN. If a Data Link connection does notexist the TE shall establish a Data Link connection according to the procedures described in sub-clause6.1.1 of ETS 300 192.6.2.1.3 Switchhook indicationThe Switchhook information element may be used to indicate “on-hook“ or “

47、off-hook“ to the PTN.6.2.2 PTN responsesThe PTN may respond to a feature request in several ways. The action chosen is supplementary service andimplementation specific.6.2.2.1 Return of a Feature indicationThe PTN may return a Feature indication information element in an INFORMATION message or any o

48、therappropriate call control message as defined in 6.1. The Feature indication may or may not have the samefeature identifier number as was present in the original feature request. The status indicator shall be providedas appropriate to the specific supplementary service requested.6.2.2.2 Prompting

49、for further informationThe PTN may prompt the user for more information (e.g. additional information related to a given featurerequest). The procedures employed are implementation specific, possibilities including the use of tones /announcements, displays, etc.; the TE may send the required information in Keypad facility or othersuitable information elements. Optionally the information request procedures defined in annex B may beused.6.2.2.3 Implicit responseThe PTN, under certain situations, may not return any explicit indication to the TE after a feature request.In this case the response