CAN CSA-ISO IEC 15507-2001 Information technology - Telecommunications and information exchange between systems - Private Integrated Services Network - Inter-exchange signalling pr.pdf

1、National Standard of CanadaCAN/CSA-ISO/IEC 15507-01(ISO/IEC 15507:1997)International Standard ISO/IEC 15507:1997 (first edition, 1997-12-01), has been adopted withoutmodification as CSA Standard CAN/CSA-ISO/IEC 15507-01, which has been approved as a National Standardof Canada by the Standards Counci

2、l of Canada.ISBN 1-55324-361-7 March 2001G35G48G49G48G55G48G51G46G48 G51G58G50G45G48G55G2cG36G32G12G2cG28G26 G14G18G18G13G1aG1dG14G1cG1cG1aGbG28GcThe Canadian Standards Association, which The Standards Council of Canada is theoperates under the name CSA International coordinating body of the Nationa

3、l Standards system, (CSA), under whose auspices this National Standard a federation of independent, autonomoushas been produced, was chartered in 1919 and organizations working towards the furtheraccredited by the Standards Council of Canada to the development and improvement of voluntaryNational St

4、andards system in 1973. It is a not-for-profit, standardization in the national interest.nonstatutory, voluntary membership association The principal objects of the Council are to foster engaged in standards development and certification and promote voluntary standardization as a means activities. o

5、f advancing the national economy, benefiting theCSA standards reflect a national consensus of health, safety, and welfare of the public, assisting producers and users including manufacturers, and protecting the consumer, facilitating domestic consumers, retailers, unions and professional and interna

6、tional trade, and furthering internationalorganizations, and governmental agencies. The cooperation in the field of standards.standards are used widely by industry and commerce A National Standard of Canada is a standard whichand often adopted by municipal, provincial, and federal has been approved

7、by the Standards Council ofgovernments in their regulations, particularly in the Canada and one which reflects a reasonablefields of health, safety, building and construction, and agreement among the views of a number of capablethe environment. individuals whose collective interests provide to theIn

8、dividuals, companies, and associations across greatest practicable extent a balance ofCanada indicate their support for CSAs standards representation of producers, users, consumers, anddevelopment by volunteering their time and skills to others with relevant interests, as may be appropriateCSA Commi

9、ttee work and supporting the Associations to the subject in hand. It normally is a standardobjectives through sustaining memberships. The more which is capable of making a significant and timelythan 7000 committee volunteers and the 2000 contribution to the national interest.sustaining memberships t

10、ogether form CSAs total Approval of a standard as a National Standard ofmembership from which its Directors are chosen. Canada indicates that a standard conforms to theSustaining memberships represent a major source of criteria and procedures established by the Standardsincome for CSAs standards dev

11、elopment activities. Council of Canada. Approval does not refer to theThe Association offers certification and testing services technical content of the standard; this remains thein support of and as an extension to its standards continuing responsibility of the accrediteddevelopment activities. To

12、ensure the integrity of its standards-development organization.certification process, the Association regularly and Those who have a need to apply standards arecontinually audits and inspects products that bear the encouraged to use National Standards of CanadaCSA Mark. whenever practicable. These s

13、tandards are subject In addition to its head office and laboratory complex to periodic review; therefore, users are cautioned in Toronto, CSA has regional branch offices in major to obtain the latest edition from the organizationcentres across Canada and inspection and testing preparing the standard

14、.agencies in eight countries. Since 1919, the Association The responsibility for approving National Standards has developed the necessary expertise to meet its of Canada rests with thecorporate mission: CSA is an independent service Standards Council of Canadaorganization whose mission is to provide

15、 an open and 270 Albert Street, Suite 200effective forum for activities facilitating the exchange of Ottawa, Ontario, K1P 6N7goods and services through the use of standards, Canadacertification and related services to meet national andinternational needs.For further information on CSA services, writ

16、e toCSA International178 Rexdale BoulevardToronto, Ontario, M9W 1R3CanadaAlthough the intended primary application of this Standard is stated in its Scope, it is importantto note that it remains the responsibility of the users to judge its suitability for their particular purpose.Registered trade-ma

17、rk of Canadian Standards AssociationInformation technology Telecommunications and information exchangebetween systems Private Integrated Services Network CAN/CSA-ISO/IEC 15507-01 Inter-exchange signalling protocol PINX clock synchronization March 2001 CSA/1CAN/CSA-ISO/IEC 15507-01Information technol

18、ogy Telecommunications andinformation exchange betweensystems Private IntegratedServices Network Inter-exchangesignalling protocol PINX clocksynchronizationCSA PrefaceStandards development within the Information Technology sector is harmonized with internationalstandards development. Through the CSA

19、 Technical Committee on Information Technology (TCIT),Canadians serve as the Canadian Advisory Committee (CAC) on ISO/IEC Joint Technical Committee 1 onInformation Technology (ISO/IEC JTC1) for the Standards Council of Canada (SCC), the ISO memberbody for Canada and sponsor of the Canadian National

20、Committee of the IEC. Also, as a member of theInternational Telecommunication Union (ITU), Canada participates in the International Telegraph andTelephone Consultative Committee (ITU-T). This International Standard was reviewed by the CSA TCIT under the jurisdiction of the StrategicSteering Committe

21、e on Information Technology and deemed acceptable for use in Canada. (Acommittee membership list is available on request from the CSA Project Manager.) From time to time,ISO/IEC may publish addenda, corrigenda, etc. The CSA TCIT will review these documents for approvaland publication. For a listing,

22、 refer to the CSA Information Products catalogue or CSA Info Update orcontact a CSA Sales representative. This Standard has been formally approved, without modification, bythese Committees and has been approved as a National Standard of Canada by the Standards Council ofCanada.March 2001 CSA Interna

23、tional 2001All rights reserved. No part of this publication may be reproduced in any form whatsoever without the prior permissionof the publisher. ISO/IEC material is reprinted with permission. Inquiries regarding this National Standard of Canadashould be addressed to CSA International, 178 Rexdale

24、Boulevard, Toronto, Ontario, M9W 1R3.INTERNATIONAL STANDARD ISOAEC 15507 First edition 1997-12-01 Information technology - Telecommunications and information exchange between Systems - Private Integrated Services Network - Inter-exchange signalling protocol - PINX clock synchronization Technologies

25、de Iinforma tion - T .- The following two operations shall apply to SYNC-SIG 3ynchronizationRequest l .- . .- OPERATION ARGUMENT SynchronizationReqArg RESULT SynchronizationReqRes ERRORS unspecified Synchronizationlnfo l - - OPERATION ARGUMENT SynchronizationInfoArg SynchronizationReqArg .- . .- SEQ

26、UENCE action Action, argExtension ArgExtension OPTIONAL SynchronizationReqRes l - - SEQUENCE action Action, response BOOLEAN, - TRUE = yes, FALSE = no argExtension ArgExtension OPTIONAL SynchronizationInfoArg .*- - SEQUENCE stateinfo INTEGER freerunning (0), idle (l), argExtension ArgExtension OPTIO

27、NAL Action := INTEGER enslavement (0), holdon (1) ArgExtension := CHOICE extension 1 IMPLICIT Extension, sequOfExtn 2 IMPLICIT SEQUENCE OF Extension synchronizationRequest SynchronizationRequest := 78 synchronizationlnfo Synchronizationlnfo := 79 unspecified Unspecified := 1008 Unspecified l .- - ER

28、ROR PARAMETER Extension END - of Synchronkation-Operations ISO/IECl5507:1997 (E) OISO/IEC 6.3.2 Information elements 6.3.2.1 Facility information element The operations defined in 6.3.1 shall be coded in the Facility information element in accordance with ISO/IEC 11582. When conveying the invoke APD

29、U of the operations defined in 6.3.1, the destinationEntity data element of the NFE shall contain value endPINX and the interpretation APDU shall either be omitted or be included with the value rejectAnyUnrecognisedInvokePdu. 6.3.2.2 Other information elements Any other information element (e.g. Cal

30、led party number) shall be coded in accordance with ISO/IEC 11582. 6.3.3 Messages The transport mechanism is based on call-independent signalling connection (connection-oriented).The Facility information element shall be conveyed in the FACILITY message as specified in clause 10 of ISO/IEC 11582. 6.

31、4 State definitions The procedures for each PINX in the network are written in terms of the following conceptual states existing within the SYNC- SIG control entity in that PINX. 6.4.1 States at the Requesting PINX 6.4.1.1 SYNC-Idle This state exists when the connection for synchronization is not es

32、tablished (exchange of information is not possible). 6.4.1.2 SYNC-Active This state exists when the connection for synchronization is established (exchange of information is possible). 6.4.1.3 SYNC-Wait This state exists when the connection is established and a synchronizationRequest invoke APDU is

33、sent to the Destination PINX and the response is not yet received. 6.4.2 States at the Destination PINX 6.4.2.1 SYNC-Idle This state exists when the connection for synchronization is not established (exchange of information is not possible). 6.4.2.2 SYNC-Active This state exists when the connection

34、for synchronization is established (exchange of information is possible). 6.5 SignaIling procedures Annex B contains examples of message sequences of the signalling procedures. 6.5.1 Actions at the Requesting PINX The SDL representation of procedures of the Requesting PINX is shown in C.l of annex C

35、. Note - Choice of information to request by the Requesting PINX and actions in the Synchronization Entity on receipt or Destination PINX arc to be made in confxrnance with ISO/IEC 11573 and arc outside the scope of this International Standard. absence of response from the 6.5.1.1 Normal procedures

36、In state SYNC-Idle, on request of the Synchronization Entity the SYNC-SIG Control entity shall invoke SYNC-SIG towards an adjacent PINX. The Requesting PINX shall act as an Originating PINX and establish a call-independent signalling connection (connection-oriented) towards the Termirrating PINX usi

37、ng the specific called party number given by the Synchronization entity. The SYNC-SIG Control entity shall inform the Synchronization Entity when the connection is established and enter state SYNC-Active. Only the cal1 reference of this call-independent signalling connection shall be used to transpo

38、rt SYNC-SIG operations. On request of the Synchronization Entity, the SYNC-SIG Control entity releases the connection towards the adjacent PINX and SYNC-SIG enters state SYNC-Idle. In states SYNC-Wait and SYNC-Idle, requests Flom the Synchronization Entity for sending information to the adjacent PIN

39、X are ignored. In SYNC-Active state, if the Synchronization Entity requests for sending information not requiring a response (free-running, idle), the Requesting PINX shall send a synchronizationInfo invoke APDU, and remain in state SYNC-Active. In state SYNC-Active, if the Synchronization Entity re

40、quests for sending information requiring a response from the Destination PINX (enslavement or holdon request), the Requesting PINX shall send a synchronizationRequest invoke APDU, Start timer 4 OISO/IEC ISOkIEC 15507: 1997 (E) Tl, and enter state SYNC-Wait. In state SYNC-Wait, on receipt of the sync

41、hronizationRequest retum result APDU from the Destination PINX, the Requesting PINX shall convey the result to the Synchronization Entity, stop timer Tl, and enter state SYNC-Active. In state SYNC-Wait, if the connection is released, the Requesting PINX shall inform its Synchronization Entity, stop

42、timer Tl, and enter state SYNC-Idle. In state SYNC-Active, if the connection is released by the adjacent PINX, the Requesting PINX shall inform Synchronization Entity and enter state SYNC-Idle. 6.5.1.2 Exceptional procedures In state SYNC-Wait, on receipt of the synchronizationRequest retum error or

43、 reject APDU from the Destination PINX, the Requesting PINX shall inform the Synchronization Entity, stop timer Tl, and enter state SYNC-Active. If timer Tl expires in state SYNC-Wait, the Requesting PINX shall inform the Synchronization Entity, and enter state SYNC-Active. 6.5.2 Actions at the Dest

44、ination PINX The SDL representation sf procedures of the Destination PINX is shown in C.2 of annex C. Note - Choice of response to send by the Destination PINX and actions in the Synchronization Entity be made in conformance with ISO/IEC 1 1573 and are outside the scope of this International Standar

45、d. on receipt of requests from the Req ,uesting PINX are to 6.5.2.1 Normal procedures The cal1 reference of the call-independent signalling connection that was established by the Requesting PINX shall be used to transport SYNC-SIG operations. The SYNC-SIG Control entity shall inform the Synchronizat

46、ion Entity when the connection is established and enter state SYNC-Active. In state SYNC-Active, on receipt of the synchronizationRequest invoke APDU or synchronizationInfo invoke APDU from the Requesting PINX, the Destination PINX shall convey the information to the Synchronization Entity and remai

47、n in state SYNC- Active. In state SYNC-Active, if the Synchronization Entity requests sending a response to a synchronizationRequest invoke APDU, the Destination PINX shall send a synchronizationRequest retum result APDU to the Requesting PINX and remain in state SYNC-Active. On request of the Synch

48、ronization Entity, the Destination PINX shall release the connection towards the Requesting PINX and enter state SYNC-Idle. In state SYNC-Active, if the connection is released by the adjacent PINX, the Destination PINX shall inform the Synchronization Entity and enter state SYNC-Idle. 6.5.2.2 Except

49、ional procedures If a synchronizationRequest invoke APDU cannot be accepted a synchronizationRequest return error APDU shall be retumed. 6.6 Impact of interworking with public ISDNs Not applicable. 6.7 Impact of interworking with non-ISDNs Not applicable. 6.8 Protocol interactions between Synchronization and supplementary Services and ANFs Not applicable. 6.9 Parameter vaiues (timers) 6.9.1 Timer Tl Timer Tl operates at the Requesting PINX in state SYNC-Wait. Its purpose is to protect against the absence of a response to the syn