ISO-15507-1997.pdf
《ISO-15507-1997.pdf》由会员分享,可在线阅读,更多相关《ISO-15507-1997.pdf(20页珍藏版)》请在三一文库上搜索。
1、INTERNATIONAL STANDARD lSO/lEC 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 de /information - T .- The following
2、 two operations shall apply to SYNC-SIG 3ynchronizationRequest := Synchronizationlnfo - - SynchronizationReqArg := OPERATION ARGUMENT SynchronizationReqArg RESULT SynchronizationReqRes ERRORS unspecified OPERATION ARGUMENT SynchronizationlnfoArg SEQUENCE action Action, argExtension ArgExtension OPTI
3、ONAL SynchronizationReqRes := SynchronizationlnfoArg := SEQUENCE action Action, response BOOLEAN, - TRUE = yes, FALSE = no argExtension ArgExtension OPTIONAL SEQUENCE stateinfo INTEGER freerunning (0), idle (l), argExtension ArgExtension OPTIONAL Action := INTEGER enslavement (0) holdon (1) ArgExten
4、sion := CHOICE extension l IMPLICIT Extension, sequOfExtn 2 IMPLICIT SEQUENCE OF Extension synchronizationRequest SynchronizationRequest := 78 synchronizationlnfo Synchronizationlnfo := 79 unspecified Unspecified := 1008 Unspecified := ERROR PARAMETER Extension END - of Synchronization-Operations Co
5、pyright International Organization for Standardization Provided by IHS under license with ISO Licensee=NASA Technical Standards 1/9972545001 Not for Resale, 04/19/2007 22:35:01 MDTNo reproduction or networking permitted without license from IHS -,-,- ISOLIEC 15507:1997 (E) OISO/IEC 6.3.2 Information
6、 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 APDU of the operations defined in 6.3.1, the destinationEntity data element of the NFE shall contain value end
7、PINX 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. Called party number) shall be coded in accordance with ISO/IEC 11582. 6.3.3 Messages The transport mechanism i
8、s 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.4 State definitions The procedures for each PINX in the network are written in terms of the following conce
9、ptual 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 established (exchange of information is not possible). 6.4.1.2 SYNC-Active This state exists when the connect
10、ion 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 sent to the Destination PINX and the response is not yet received. 6.4.2 States at the Destination PINX 6.4
11、.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 for synchronization is established (exchange of information is possible). 6.5 Signalling procedures Annex B
12、 contains examples of message sequences of the signalling procedures. 6.51 Actions at the Requesting PINX The SDL representation of procedures of the Requesting PINX is shown in C. 1 of annex C. Note - Choice of information to request by the Requesting PINX and actions in the Synchronization Entity
13、on receipt or absence of response from the Destination PINX are to be made in confxmance with ISOAEC 11573 and are outside the scope of this International Standard. 6.5.1.1 Normal procedures In state SYNC-Idle, on request of the Synchronization Entity the SYNC-SIG Control entity shall invoke SYNC-SI
14、G towards an adjacent PINX. The Requesting PINX shall act as an Originating PINX and establish a call-independent signalling connection (connection-oriented) towards the Terminating PINX using the specific called party number given by the Synchronization entity. The SYNC-SIG Control entity shall inf
15、orm the Synchronization Entity when the connection is established and enter state SYNC-Active. Only the call reference of this call-independent signalling connection shall be used to transport SYNC-SIG operations. On request of the Synchronization Entity, the SYNC-SIG Control entity releases the con
16、nection towards the adjacent PINX and SYNC-SIG enters state SYNC-Idle. In states SYNC-Wait and SYNC-Idle, requests from the Synchronization Entity for sending information to the adjacent PINX are ignored. In SYNC-Active state, if the Synchronization Entity requests for sending information not requir
17、ing 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 requests for sending information requiring a response from the Destination PINX (enslavement or holdon request),
18、 the Requesting PINX shall send a synchronizationRequest invoke APDU, start timer 4 Copyright International Organization for Standardization Provided by IHS under license with ISO Licensee=NASA Technical Standards 1/9972545001 Not for Resale, 04/19/2007 22:35:01 MDTNo reproduction or networking perm
19、itted without license from IHS -,-,- OISO/IEC ISO/IEC 15507:1997 (E) Tl, and enter state SYNC-Wait. In state SYNC-Wait, on receipt of the synchronizationRequest return result APDU from the Destination PINX, the Requesting PINX shall convey the result to the Synchronization Entity, stop timer Tl, and
20、 enter state SYNC-Active. In state SYNC-Wait, if the connection is released, the Requesting PINX shall inform its Synchronization Entity, stop 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 Synchronizati
21、on Entity and enter state SYNC-Idle. 6.5.1.2 Exceptional procedures In state SYNC-Wait, on receipt of the synchronizationRequest return error or 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
22、 expires in state SYNC-Wait, the Requesting PINX shall inform the Synchronization Entity, and enter state SYNC-Active. 6.5.2 Actions at the Destination PINX The SDL representation of procedures of the Destination PINX is shown in C.2 of annex C. Note - Choice of response to send by the Destination P
23、INX and actions in the Synchronization Entity on receipt of requests from the Requesting PINX are to be made in conformance with ISO/IEC 11573 and are outside the scope of this International Standard. 6.5.2.1 Normal procedures The call reference of the call-independent signalling connection that was
24、 established by the Requesting PINX shall be used to transport SYNC-SIG operations. The SYNC-SIG Control entity shall inform the Synchronization Entity when the connection is established and enter state SYNC-Active. In state SYNC-Active, on receipt of the synchronizationRequest invoke APDU or synchr
- 配套讲稿:
如PPT文件的首页显示word图标,表示该PPT已包含配套word讲稿。双击word图标可打开word文档。
- 特殊限制:
部分文档作品中含有的国旗、国徽等图片,仅作为作品整体效果示例展示,禁止商用。设计者仅对作品中独创性部分享有著作权。
- 关 键 词:
- ISO 15507 1997
链接地址:https://www.31doc.com/p-3776979.html