ECMA 245-1997 Private Integrated Services Network (PISN) - Inter-Exchange Signalling Protocol - PINX Clock Synchronization (SYNC-SIG)《专用综合业务网络(PISN) 局间信令协议 PINX时钟同步(SYNC-SIG) 第2版》.pdf

《ECMA 245-1997 Private Integrated Services Network (PISN) - Inter-Exchange Signalling Protocol - PINX Clock Synchronization (SYNC-SIG)《专用综合业务网络(PISN) 局间信令协议 PINX时钟同步(SYNC-SIG) 第2版》.pdf》由会员分享，可在线阅读，更多相关《ECMA 245-1997 Private Integrated Services Network (PISN) - Inter-Exchange Signalling Protocol - PINX Clock Synchronization (SYNC-SIG)《专用综合业务网络(PISN) 局间信令协议 PINX时钟同步(SYNC-SIG) 第2版》.pdf（30页珍藏版）》请在麦多课文档分享上搜索。

1、Standard ECMA-2452nd Edition - September 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) -Inter-Exchange Signalling Protocol -PINX Clock Synchronizatio

2、n.Standard ECMA-2452nd Edition - September 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-245.doc 02-09-97 12,12Private Integrated Services Network(PISN) -Inter-Exchange Signalling Pro

3、tocol -PINX Clock Synchronization(SYNC-SIG).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 developed by ITU-T and conforms to the framework ofIntern

4、ational Standards for Open Systems Interconnection as defined by ISO/IEC. It has been produced under ETSI work itemDE/ECMA-00115.This particular Standard specifies the signalling protocol for the support of PINX clock synchronization. The protocol definedin this Standard forms part of the PSS1 proto

5、col (informally known as QSIG).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, ITU-T, ETSI and other international and national standardizationbodies. It represents a pragmatic and

6、widely based consensus.Compared to the 1st Edition of Standard ECMA-245 (published by ECMA in June 1996), this 2nd Edition incorporateschanges in order to achieve complete alignment with International Standard ISO/IEC 15507 to be published by ISO/IEC.Adopted as 2nd Edition of Standard ECMA-245 by th

7、e General Assembly in September 1997.- i -Table of contents1 Scope 12 Conformance 13 References (normative) 14 Definitions 14.1 External definitions 14.2 Other definitions 24.2.1 Adjacent PINX 24.2.2 Requesting PINX 24.2.3 Destination PINX 24.2.4 Synchronization Entity 25 List of acronyms 26 Signall

8、ing protocol for the support of the protocol 26.1 Description 26.2 Operational requirements 26.3 Coding requirements 36.3.1 Operations 36.3.2 Information elements 46.3.3 Messages 46.4 State definitions 46.4.1 States at the Requesting PINX 46.4.2 States at the Destination PINX 46.5 Signalling procedu

9、res 46.5.1 Actions at the Requesting PINX 46.5.2 Actions at the Destination PINX 56.6 Impact of interworking with public ISDNs 56.7 Impact of interworking with non-ISDNs 56.8 Protocol interactions between Synchronization and supplementary services and ANFs 66.9 Parameter values (timers) 66.9.1 Timer

10、 T1 6Annex A - Protocol Implementation Conformance Statement (PICS) Proforma 7Annex B - Examples of Message Sequences 11Annex C - Specification and Description Language (SDL) Representation of Procedures 15- ii -.1ScopeThis Standard specifies the signalling protocol for the support of clock synchron

11、ization (SYNC-SIG) between PrivateIntegrated Services Network Exchanges (PINXs) connected together within a Private Integrated Services Network(PISN).This protocol supports the synchronization of a PISN using the different sources of clocks available to each PINX. Theprotocol is based on the method

12、of synchronization described in annex F of the International Standard ISO/IEC 11573.This Standard is applicable to PINXs which can be interconnected to form a PISN.2 ConformanceIn order to conform to this Standard, a PINX shall satisfy the requirements identified in the Protocol ImplementationConfor

13、mance Statement (PICS) proforma in annex A.3 References (normative)The following standards contain provisions 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 invest

14、igate thepossibility of applying the most recent editions 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

15、-165 Private Integrated Services Network - Generic Functional Protocol for the Support ofSupplementary Services - Inter-Exchange Signalling Procedures and Protocol (InternationalStandard ISO/IEC 11582)ISO/IEC 11573 Information technology - Telecommunications and information exchange between systems

16、-Synchronization methods and technical requirements for Private Integrated Services NetworksISO/IEC 11579-1 Information technology - Telecommunications and information exchange between systems -Private Integrated Services Network - Part 1: Reference configuration for PISN Exchanges(PINX)ITU-T Rec. I

17、.112 Vocabulary of terms for ISDNs (1993)ITU-T Rec. Z.100 Specification and description language (1993)4 DefinitionsFor the purposes of this Standard, the following definitions apply.4.1 External definitionsThis Standard uses the following terms defined in other documents: Application Protocol Data

18、Unit (ECMA-165) End PINX (ECMA-165) Interpretation APDU (ECMA-165) Private Integrated Services Network (PISN) (ISO/IEC 11579-1) Private Integrated Services Network Exchange (PINX) (ISO/IEC 11579-1) Signalling (ITU-T Rec. I.112) Originating PINX (ECMA-165) Terminating PINX (ECMA-165)- 2 -4.2 Other de

19、finitions4.2.1 Adjacent PINXOne of two PINXs that are directly connected by means of an inter-PINX link.4.2.2 Requesting PINXPINX that initiates a confirmed or unconfirmed transaction.4.2.3 Destination PINXPINX which is the target of a confirmed or unconfirmed transaction.4.2.4 Synchronization Entit

20、yEntity which is in charge of the synchronization in a PINX.NOTEThe functions of the Synchronization Entity are described in ISO/IEC 11573.5 List of acronymsAPDU Application Protocol Data UnitASN.1 Abstract Syntax Notation OneISDN Integrated Services Digital NetworkNFE Network Facility ExtensionPICS

21、 Protocol Implementation Conformance StatementPINX Private Integrated Network ExchangePISN Private Integrated Service NetworkSDL Specification and Description Language6 Signalling protocol for the support of the protocol6.1 DescriptionWhen two or more PINXs are connected to each other, it is require

22、d by ISO/IEC 11573 that these PINXs shall workfor transmission with the same clock value: in that case PINXs are ”synchronized”. Without such synchronization,information can be lost from one PINX to another.ISO/IEC 11573 describes the “clock synchronization” in detail and defines a method to use for

23、 a networksynchronization. The signalling protocol for this method is defined in this Standard. The protocol involves theexchange of APDUs between adjacent PINXs using the call-independent signalling connection (connection-oriented) transport mechanism specified in ECMA-165.6.2 Operational requireme

24、ntsGeneric procedures for the call-independent control (connection-oriented), as specified in ECMA-165 for anOriginating PINX and Terminating PINX, shall apply.A Synchronization Entity which can be called by a predetermined called party number shall exist in each PINX.- 3 -6.3 Coding requirements6.3

25、.1 OperationsTo convey information defined by the method of synchronization in messages, the operations defined in AbstractSyntax Notation number 1 (ASN.1) in table 1 shall apply.Table 1 - Operations in support of clock synchronizationSynchronization-Operations iso (1) standard (0) pinx-clock-synchr

26、onization (15507)synchronization-operations (0) DEFINITIONS EXPLICIT TAGS :=BEGINIMPORTS OPERATION, ERROR FROM Remote-Operation-Notation joint-iso-ccitt (2) remote-operations (4) notation (0) Extension FROM Manufacturer-specific-service-extension-definitioniso (1) standard (0)pss1-generic-procedures

27、 (11582) msi-definition (0);- The following two operations shall apply to SYNC-SIGSynchronizationRequest := OPERATIONARGUMENT SynchronizationReqArgRESULT SynchronizationReqResERRORS unspecifiedSynchronizationInfo := OPERATIONARGUMENT SynchronizationInfoArgSynchronizationReqArg := SEQUENCE action Act

28、ion,argExtension ArgExtension OPTIONALSynchronizationReqRes := SEQUENCE action Action,response BOOLEAN, - TRUE = yes, FALSE = noargExtension ArgExtension OPTIONALSynchronizationInfoArg := SEQUENCE stateinfo INTEGER freerunning (0), idle (1),argExtension ArgExtension OPTIONALAction := INTEGER enslave

29、ment (0), holdon (1)ArgExtension := CHOICE extension 1 IMPLICIT Extension,sequOfExtn 2 IMPLICIT SEQUENCE OF Extension synchronizationRequest SynchronizationRequest := 78synchronizationInfo SynchronizationInfo := 79unspecified Unspecified := 1008Unspecified := ERROR PARAMETER ExtensionEND - of Synchr

30、onization-Operations- 4 -6.3.2 Information elements6.3.2.1 Facility information elementThe operations defined in 6.3.1 shall be coded in the Facility information element in accordance withECMA-165.When conveying the invoke APDU of the operations defined in 6.3.1, the destinationEntity data element o

31、f theNFE shall contain value endPINX and the interpretation APDU shall either be omitted or be included with thevalue rejectAnyUnrecognisedInvokePdu.6.3.2.2 Other information elementsAny other information element (e.g. Called party number) shall be coded in accordance with ECMA-165.6.3.3 MessagesThe

32、 transport mechanism is based on call-independent signalling connection (connection-oriented).The Facilityinformation element shall be conveyed in the FACILITY message as specified in clause 10 of ECMA-165.6.4 State definitionsThe procedures for each PINX in the network are written in terms of the f

33、ollowing conceptual states existing withinthe SYNC-SIG control entity in that PINX.6.4.1 States at the Requesting PINX6.4.1.1 SYNC-IdleThis state exists when the connection for synchronization is not established (exchange of information is notpossible).6.4.1.2 SYNC-ActiveThis state exists when the c

34、onnection for synchronization is established (exchange of information is possible).6.4.1.3 SYNC-WaitThis state exists when the connection is established and a synchronizationRequest invoke APDU is sent to theDestination PINX and the response is not yet received.6.4.2 States at the Destination PINX6.

35、4.2.1 SYNC-IdleThis state exists when the connection for synchronization is not established (exchange of information is notpossible).6.4.2.2 SYNC-ActiveThis state exists when the connection for synchronization is established (exchange of information is possible).6.5 Signalling proceduresAnnex B cont

36、ains examples of message sequences of the signalling procedures.6.5.1 Actions at the Requesting PINXThe SDL representation of procedures of the Requesting PINX is shown in C.1 of annex C.NOTEChoice of information to request by the Requesting PINX and actions in the Synchronization Entity on receipt

37、orabsence of response from the Destination PINX are to be made in conformance with ISO/IEC 11573 and areoutside the scope of this Standard.6.5.1.1 Normal proceduresIn state SYNC-Idle, on request of the Synchronization Entity the SYNC-SIG Control entity shall invokeSYNC-SIG towards an adjacent PINX.

38、The Requesting PINX shall act as an Originating PINX and establish acall-independent signalling connection (connection-oriented) towards the Terminating PINX using the specificcalled party number given by the Synchronization entity. The SYNC-SIG Control entity shall inform theSynchronization Entity

39、when the connection is established and enter state SYNC-Active. Only the callreference of this call-independent signalling connection shall be used to transport SYNC-SIG operations. On- 5 -request of the Synchronization Entity, the SYNC-SIG Control entity releases the connection towards theadjacent

40、PINX and SYNC-SIG enters state SYNC-Idle.In states SYNC-Wait and SYNC-Idle, requests from the Synchronization Entity for sending information to theadjacent PINX are ignored. In SYNC-Active state, if the Synchronization Entity requests for sendinginformation not requiring a response (free-running, id

41、le), the Requesting PINX shall send asynchronizationInfo invoke APDU, and remain in state SYNC-Active.In state SYNC-Active, if the Synchronization Entity requests for sending information requiring a responsefrom the Destination PINX (enslavement or holdon request), the Requesting PINX shall send asy

42、nchronizationRequest invoke APDU, start timer T1, and enter state SYNC-Wait. In state SYNC-Wait, onreceipt of the synchronizationRequest return result APDU from the Destination PINX, the Requesting PINXshall convey the result to the Synchronization Entity, stop timer T1, and enter state SYNC-Active.

43、In state SYNC-Wait, if the connection is released, the Requesting PINX shall inform its SynchronizationEntity, stop timer T1, and enter state SYNC-Idle. In state SYNC-Active, if the connection is released by theadjacent PINX, the Requesting PINX shall inform Synchronization Entity and enter state SY

44、NC-Idle.6.5.1.2 Exceptional proceduresIn state SYNC-Wait, on receipt of the synchronizationRequest return error or reject APDU from theDestination PINX, the Requesting PINX shall inform the Synchronization Entity, stop timer T1, and enterstate SYNC-Active. If timer T1 expires in state SYNC-Wait, the

45、 Requesting PINX shall inform theSynchronization Entity, and enter state SYNC-Active.6.5.2 Actions at the Destination PINXThe SDL representation of procedures of the Destination PINX is shown in C.2 of annex C.NOTEChoice of response to send by the Destination PINX and actions in the Synchronization

46、Entity on receipt ofrequests from the Requesting PINX are to be made in conformance with ISO/IEC 11573 and are outside thescope of this Standard.6.5.2.1 Normal proceduresThe call reference of the call-independent signalling connection that was established by the Requesting PINXshall be used to trans

47、port SYNC-SIG operations.The SYNC-SIG Control entity shall inform the Synchronization Entity when the connection is established andenter state SYNC-Active.In state SYNC-Active, on receipt of the synchronizationRequest invoke APDU or synchronizationInfo invokeAPDU from the Requesting PINX, the Destin

48、ation PINX shall convey the information to the SynchronizationEntity and remain in state SYNC-Active. In state SYNC-Active, if the Synchronization Entity requests sendinga response to a synchronizationRequest invoke APDU, the Destination PINX shall send asynchronizationRequest return result APDU to

49、the Requesting PINX and remain in state SYNC-Active.On request of the Synchronization Entity, the Destination PINX shall release the connection towards theRequesting PINX and enter state SYNC-Idle.In state SYNC-Active, if the connection is released by the adjacent PINX, the Destination PINX shall informthe Synchronization Entity and enter state SYNC-Idle.6.5.2.2 Exceptional proceduresIf a synchronizationRequest invoke APDU cannot be accepted a synchronizationRequest return error APDUshall be returned.6.6 Impact of interworking with pub