《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
25、onizationbifo invoke APDU from the Requesting PINX, the Destination PINX shall convey the information to the Synchronization Entity and remain in state SYNC- Active. In state SYNC-Active, if the Synchronization Entity requests sending a response to a synchronizationRequest invoke APDU, the Destinati
26、on PINX shall send a synchronizationRequest return result APDU to the Requesting PINX and remain in state SYNC-Active. On request of the Synchronization Entity, the Destination PINX shall release the connection towards the Requesting PINX and enter state SYNC-Idle. In state SYNC-Active, if the conne
27、ction is released by the adjacent PINX, the Destination PINX shall inform the Synchronization Entity and enter state SYNC-Idle. 6.5.2.2 Exceptional procedures If a synchronizationRequest invoke APDU cannot be accepted a synchronizationRequest return error APDU shall be returned. 6.6 Impact of interw
28、orking 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 ANPs Not applicable. 6.9 Parameter values (timers) 6.9.1 Timer Tl Timer Tl operates at the Requesting PINX in state SYNC
29、-Wait. Its purpose is to protect against the absence of a response to the synchronizationRequest invoke APDU. Timer Tl shall have a value not less than 15 s. Copyright International Organization for Standardization Provided by IHS under license with ISO Licensee=NASA Technical Standards 1/9972545001
30、 Not for Resale, 04/19/2007 22:35:01 MDTNo reproduction or networking permitted without license from IHS -,-,- ISOREC 15507:1997 (E) Annex A (normative) OISO/IEC Protocol Implementation Conformance Statement (PICS) Proforma A.1 Introduction The supplier of a protocol implementation which is claimed
31、to conform to this International Standard shall complete the Protocol Implementation Conformance Statement (PICS) proforma. A completed PICS proforma is the PICS for the implementation in question. The PICS is a statement of which capabilities and options of the protocol have been implemented. The P
32、ICS can have a number of uses, including use: - by a protocol implementer, as a check-list to reduce the risk of failure to conform to the standard through oversight; - by the supplier and acquirer (or potential acquirer) of the implementation, as a detailed indication of the capabilities of the imp
33、lementation, stated relative to the common basis for understanding provided by the standard PICS proforma; - by the user (or potential user) of the implementation, as a basis for initially checking the possibility of interworking with another implementation (note that, while interworking cannot be g
34、uaranteed, failure to interwork can often be predicted from incompatible PICS); - by a protocol tester, as the basis for selecting appropriate tests against which to asses the claim for conformance of the implementation. A.2 Instructions for completing the PICS proforma A.2.1 General structure of th
35、e PICS proforma The PICS proforma is a fixed-format questionnaire divided into subclauses each containing a group of individual items. Each item is identified by an item number, the name of the item (question to be answeredj and the reference(s) to the clause(s) that specifies (specify) the item in
36、the main body of this International Standard. The “Status” column indicates whether an item is applicable and, if so, whether support is mandatory or optional. The following terms are used: m mandatory (the capability is required for conformance to the protocol); 0 optional (the capability is not re
37、quired for conformance to the protocol, but if the capability is implemented it is required to conform to the protocol specifications); optional, but support of at least one of the group of options labelled by the same numeral is required; X prohibited; c. conditional requirement, depending on supp
38、ort for the item or items listed in condition ; 4terrD:m simple conditional requirement, the capability being mandatory if item number is supported, otherwise not applicable; :0 simple conditional requirement, the capability being optional if item number is supported, otherwise not applicable. Answe
39、rs to the questionnaire items are to be provided either in the “Support” column, by simply marking an answer to indicate a restricted choice (Yes or No) or in the “Not Applicable” column (N/A). Copyright International Organization for Standardization Provided by IHS under license with ISO Licensee=N
40、ASA Technical Standards 1/9972545001 Not for Resale, 04/19/2007 22:35:01 MDTNo reproduction or networking permitted without license from IHS -,-,- OISO/IEC ISO/IEC 15507:1997 (E) A.2.2 Additional information Items of additional information allow a supplier to provide further information intended to
41、assist the interpretation of the PICS. It is not intended or expected that a large quantity will be supplied, and a PICS can be considered complete without any such information. Examples might be an outline of the ways in which a (single) implementation can be set up to operate in a variety of envir
42、onments and configurations. References to items of additional information may be entered next to any answer in the questionnaire, and may be included in items of exception information. A.2.3 Exception information It may occasionally happen that a supplier will wish to answer an item with mandatory o
43、r prohibited status (after any conditions have been applied) in a way that conflicts with the indicated requirements. No pre-printed answer will be found in the Support column for this. Instead, the supplier is required to write into the Support column an x. reference to an item of exception informa
44、tion, and to provide the appropriate rationale in the exception item itself. An implementation for which an exception item is required in this way does not conform to this International Standard. A possible reason for the situation described above is that a defect in the Standard has been reported,
45、a correction for which is expected to change the requirement not met by the implementation. 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 network
46、ing permitted without license from IHS -,-,- ISO/IEC 15507:1997 (E) OISO/IEC A.3 PICS proforma for ISO/IEC 15507 A.3.1 Implementation identification Supplier Contact point for queries about the PICS Implementation name(s) and version(s) Other information necessary for full identification, e.g. name(
47、s) and version(s) for machines and/or operating systems; system name(s) Only the first three items are required for all implementations; other information may be completed as appropriate in meeting the requirement for full identification. The terms name and version should be interpreted appropriatel
48、y to correspond with a suppliers terminology (e.g. type, series, model). A.3.2 Protocol summary Protocol version Addenda implemented (if applicable) 1.0 Amendments implemented Have any exception items been required (see A.2.3)? No 1 Yes 1 (The answer Yes means that the implementation does not confor
49、m to this International Standard) Date of Statement 8 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 permitted without license from IHS -,-