EN 60870-6-502-1996 en Telecontrol Equipment and Systems Part 6 Telecontrol Protocols Compatible with ISO Standards and ITU-T Recommendations Section 502 TASE 1 Protocol Definition.pdf

1、 - BSI BS*EN*b0870- b-502 Yb a 162466% 0567727 572 BRITISH STANDARD Telecontrol equipment and systems Part 6. Telecontrol protocols compatible with IS0 standards and ITU-T recommendations Section 502. TASE.1 Protocol definitions “he European Standard EN 60870-2-1 : 1996 has the status of a British S

2、tandard ICs 33.200 BS EN 1996 1995 60870-6-502 : IEC 870-6-502 : NO COPYING WITHOUT BSI PERMISSION EXCEPT AS PERMITTED BY COPYRIGHT LAW BS EN 60870-6-602 : 1996 Amd.No. Date Committees responsible for this British Standard Text affected The preparation of this British Standard was entrusted to Techn

3、ical Committee PEM7, Power systems control and associated communications, upon which the following bodies are represented BEXMA Metering Association MA) Building Automation and Mains Signalling Association (BASMA) Elech-icity Association Federation of the Electronics Indw GAMBICA Institution of Elec

4、trical Engineers ?k.ansmission and Distribution Association (BEAMA Ltd.) This British Standard, having been prepared under the 1989 Open Systems Interconnection : seruice - adaptability; - independence of lower layer architecture; - extensibility; - efficiency; - performance; - maintainability. - Th

5、e services of TASE.l are: - E - services for defining, changing, deleting and inspecting groups of information; - services for managing the transfer of information groups and blocks of information from different groups; - services for supervisory control. This section of IEC 870-6 specifies the prot

6、ocol (abstract syntax) and the procedures for the Telecontrol Application Service Element (TASE). The TASE.l services are provided in conjunction with the Remote Operations Service Element (ROSE) services (ISOIEC 9072-1) and the ROSE protocol (ISO/IEC 9072-2), and the Association Control Element (AC

7、SE) services (IS0 8649) and the ACSE protocol (IS0 8650). The TASE.1 procedures are defined in terms of: a) the interactions between peer TASE.l protocol machines through the use of ROSE sew ices; b) the interactions between the TASE.1 protocol machine and its service-user. The scope of the protocol

8、 is limited to the interconnection of systems. It does not specify or restrict the possible implementation of interfaces within a telecontrol system. BSI BS*EN*b0870- 6-502 96 W L62Lthb 05b9736 702 W Page 4 EN 60870-6-602 : 1996 2 Normative references The following normative documents contain provis

9、ions which, through reference in this text, constitute provisions of this section of IEC 870-6. At the time of publication, the editions indicated were valid. All normative documents are subject to revision, and parties to agreements based on this section of IEC 870-6 are encouraged to investigate t

10、he possibility of applying the most recent editions of the normative documents indicated below. Members of IEC and IS0 maintain registers of currently valid International Standards. IEC 870-6-501 : 1995, Telecontrol equlpment and systems - Part 6: Telecontrol protocols compatible with IS0 standards

11、and ITU-T recommendations - Section 501: TASE. 1 service definitions ISOAEC 8824: 1 990, Information technology - Open Systems Interconnection - Specification of Abstract Syntax Notation One (ASN. i) ISOAEC 8825: 1 990, Information technology - Open Systems Interconnection - Specification of Basic E

12、ncoding Rules for Abstract Syntax Notation One (ASN. i) ISOAEC 9072-1 : 1989, Information processing systems - Text communication - Remote Operations -Part 1: Model, notation and service definition ISOAEC 9072-2: 1989, Infomation processing systems - Text communication - Remote Operations - Part 2:

13、Protocol specification ISO/DIS 8825-2*, Information technology - Open Systems Interconnection - Specification of Basic Encoding Rules for Abstract Syntax Notation One (ASN. Y) - Part 2: Packed encoding rules IS0 7498: 1984, Information processing systems - Open Systems Interconnection - Basic Refere

14、nce Model ISOTTR 8509: 1987, Information processing systems - Open Systems Interconnection - Service conventions IS0 8649: 1988, Information processing systems - Open Systems Interconnection - Service definition for the Association Control Service Element IS0 8650: 1988, Information processing syste

15、ms - Open Systems. Interconnection - Protocol specification for the Association Control Service Element IS0 8822: 1994, Information technology - Open Systems Interconnection - Presentation service definition IS0 8859-1 : 1987, Information processing - association b) Application-context c) Applicatio

16、n Control Service Element 3.5 Remote operations definitions (defined in IS0 9072) a) ACSE-user b) ROSE-user c) BIND d) UNBIND e) Remote Operations f) RO-notation 9) Remote Operation Service Element BSI BS*EN*b0870- 6-502 96 W Lb24bb9 ClSb9738 585 W Page 6 EN 60870-6-502 : 1996 3.6 TASE. 1 service de

17、finfiions (defined in IEC 870-6-501) a) Initiator b) Responder 3.7 TASE. 1 protocol specification definitions 3.7.1 idle state: Connected entity waiting for anincoming event. 3.7.2 initiating entity: Application entity in idle state that receives a request event from the upper service-user. 3.7.3 re

18、sponding entity: Application entity in idle state that receives an incoming event from its lower service-provider. 3.7.4 DCUT1: Timer used by the application-process for supervision of the application- service-user. 3.7.5 DCLT1: Timer used by the application-process for supervision of the remote pee

19、r entity. 3.7.6 TASE-protocol-machine: The protocol machine for the TASE.1 specified in this section of the TASE.l standard. 4 Abbreviations ACSE Association Control Service Element AE Application-entity APCI Application Protocol Control Information APDU Application Protocol Data Unit OSIE Open Syst

20、ems Interconnection Environment PDU Protocol Data Unit ROSE Remote Operations Service Element TASE Telecontrol Application Sewice Element TPM Telecontrol Protocol Machine. * tn * Service TASE Bind BSI BS*EN*b0870- 6-502 96 Lb24569 8569739 411 Page 7 EN 60870-6-502 : 1996 Tm confirmed 5 Conventions T

21、ASE Abort Group Management Define Group Get (iroup This section of IEC 870-6 makes use of the following conventions: a) the abstract syntax definitions in annex A are defined using the abstract syntax notation defined in ISO/IEC 8824; b) the remote operation macros (RO-notation), and the application

22、-service-element and application-context macros are defined in IS0 9072-1. Provider-Initiated confirmed confinned confinned 6 Overview of the protocol Reqtte8ted Data Transfer Unsoilcited Data Transfer Management Send Non-Confirmed Data Send Confirmed Data Send Mixed Data 6.1 s8rVk8 provided confirm

23、ed Confirmed Non-confimied confirmed NOn-cOnfimied The protocol specified in this section of the TASE.l standard provides the TASE.1 services defined in the TASE.l service definition. These services are listed in table 1. Ini I confirmed I 1 Command Transfer I confirmed I Test Association I confirme

24、d I 6.2 US8 Of S8rViC8S The TASE.l protocol makes use of the underlying services as described below. 6.2.1 Use of the ROSE Service The TASE.l protocol machine (TPM) uses the RO-INVOKE, RO-RESULT, RO-ERROR, RO- REJECT-U and RO-REJECT-P services of the ROSE. The remote operations of the TASE.1 are cla

25、ss 2 (asynchronous, reporting success or failure) operations. Excepted from this general rule are the two non-confirmed services, Send Non- Confirmed Data and Send Mixed Data services, which are class 5 operations (asynchronous, outcome not reported). The restrictions on the use of the operations by

26、 the initiator and responder are defined in clause 7. - - BSI BS*EN*bO7O- 6-502 96 U 1624689 0567740 133 m Page 8 EN 60870-6-502 : 1996 The application-associations of TASE.l are association class 3, by which both initiator and- responder entities can invoke operations. The TASE.l services are defin

27、ed by means of RO-notation and the abstract syntax notation (ASN.l) defined in IS0 8824. 6.2.2 Use of the ACSE service The ACSE provides for the control (establishment, release, abort) of application-associations between application-entities. The ROSE Bind and Unbind macros are the sole users of the

28、 A-ASSOCIATE and A-RELEASE % services of ACSE in normal mode. The TASE.l protocol-machine (TPM) is the user of the A-P-ABORT and A-ABORT services of the ACSE. 6.3 Model for TASE. 1 services The TASE.1 protocol-machine (TPM) communicates with its service-user by means of primitives defined in the TAS

29、E.l service definition (see IEC 870-6-501). The TPM is driven by TASE1 service request primitives from its service-user, and by indication primitives of the ROSE services. The TPM, in turn, issues indication primitives to its service- user, and request primitives on the used ROSE services. 7 Element

30、s of procedure 7.1 Descriptive conventions Paragraphs 7.3 and 7.4 define a TASE.l Protocol Machine (TPM) using state table descriptive mechanism. All tables are shown from the viewpoint of the TASE.l service-provider. The state tables do not constitute a formal definition of the TPM. They are includ

31、ed to provide a more precise specification of the elements of procedure for the TASE.l services defined in the TASE.l Service Definition (see IEC 870-6-501). The notation used in the state tables is the same as used in ROSE Protocol Specification, annex A, and thus follows the same conventions (see

32、IS0 9072-2). 7.2 Mapping to ACSE and ROSE services This subclause defines how the Association Control Service Element (ACSE) and the Remote Operation Service Element (ROSE) services are used by the Telecontrol Protocol Machine (TPM). Any use of the ACSE or ROSE services other than described in this

33、subclause shall constitute a protocol error. The TASE.l protocol is positioned within the Open Systems Interconnection Environment (OSIE) within the application layer. As an application-service-element (ASE), TASE.l makes use of and maps onto the services and service primitives of ACSE and ROSE. The

34、 TASE.1- user may be elements within the application-process or another ASE. BSI BS*EN*bQ87Q- 6-502 76 E Lb24667 05677411 07T E TASE.1 service primitive TASE Bind request Page 9 EN 60870-6-502 : 1996 ACSE or ROSE service primitives A-ASSOCIATE request, indication 7.2.1 Mapping of TASE. I service pli

35、mitives All TASE.l service primitives shall be mapped on ACSE or ROSE services primitives. The mapping is described in table 2 below. _ TASE Unbind request TASE Unbind response TASE Abort indication Group Management request Group Management response . Define roup request Define Group response Get Gr

36、oup request Get Group response Requested Data Transfer request Requested Data Transfer response Table 2 - Mapping of TASE.l services onto ROSE and ACSE service primitives .A-RELEASEaquest, indication A-RELEASE response, confirm A-ABORT indication RO-INVOKE request, indication RO-RESULT request. indi

37、cation or RO-ERROR request. indication RO-INVOKE request, indication RO-RESULT request, indication or RO-ERROR request, indication RO-INVOKE request, indication RO-RESULT request, indication or R-ERROR request, indication RO-INVOKE request, Indication RO-RESULT request, indication or Unsdlclted Data

38、 Transfer Management request Unsolicited Data Transfer Management Invoked by I RO-ERROR request. Indication RO-INVOKE request, indication Initiator RO-RESULT request, indication or Responder Initiator I Send Confirmed Data request Send Confirmed Data response TASE Bind reswnae RO-INVOKE request, ind

39、ication RO-RESULT request, indication or 1 A-ASSOCIATE resnonse. confirm Send Mixed Data request Command Transfer request Command Transfer response Test Association request Test Association response R-ERROR request, indication RO-INVOKE request, indication Responder RO-INVOKE request, indication Ini

40、tiator RO-RESULT request, indication or Responder RO-ERROR request, indication RO-INVOKE request, indication initiator RO-RESULT request, indication or Responder RO-ERROR request, indication . Responder Initiator+ Responder ACSE senrice provider Initiator Responder Inltiator Responder Initiator Resp

41、onder Initiator Responder RO-ERROR request, indication response I Send Non-Confirmed Data mauest I RO-INVOKE mauest. indication BSI BS*EN*b0870- 6-502 96 W Lb246b9 0559742 Tob I Abbreviated name SOUice Name and description TBreq TASE.l-user TASE Bind request primitive TBRE+ TPM-peer TASE Bind respon

42、se (result = accepted) as user data on a A-ASSOCIATE conficm primitive TBRE- TPM-peer TASE Bind response (result = rejected) as user data on a A-ASSOCIATE confimi primitive A-ASCcn f- AC-provider A-ASSOCIATE confirm primitive (result = rejected (permanent) or result = *rejected (transit) TBrsp+ TASE

43、.1-user TASE Bind response primitive (result = accepted) TASE Bind response primitive Page 10 EN 60870-6-602 : 1996 TBRQ TUBreq TUBrsp+ TUBrsp- TUBRQ TUBRE+ TUBRE- A-ABRind The ACSE A-P-ABORT and A-ABORT services are mapped directly to the TASE Abort service, and hence TASE.l does not define an Abor

44、t PDU. TPM-peer TASE.l-user TASE Unbind request primitive TASE.1-user TASE.l-user TPM-peer TPM-peer TASE Bind request as user data on a A-ASSOCIATE request primitive TASE Unbind response primitive (result = ok) TASE Unbind response primitive (result = errof) TASE Unbind request as user data on a A-R

45、ELEASE indication primitive TASE Unbind response (result = ok) as user data on a A-RELEASE confirm primitive TASE Unbind response (result = error) as user data on a A-RELEASE confirm primitive TPM-peer AC-provider A-ABORT indication primitive The mapping of the abstract-syntax notation of the TASE.l

46、 onto ROSE and ACSE services is as defined in ISO/IEC 9072-1. An implementation of the TASE.l service-provider can support service primitives for users acting only as Initiators, or only as Responders, or service primitives for users acting as both Initiators and Responders. 7.3 Entering and leaving

47、 the TASE. 1 environment The TASE Bind and TASE Unbind services provide the mechanism for entering and leaving the TASE.l environment. The model for these services is described in clause 9 of IEC 870-6-501. Two AE-invocations enter the TASE.l environment when they both have defined the same TASE.1 a

48、pplication context and each AE-invocation has identified its context for the peer AE-invocation. * * Vi r- Abbreviated name A-ASCreq ES1 BS*EN*bO70- 6-502 96 Lb2Libb9 0569743 942 Destination Name and description AC-provider A-ASSOCIATE request primitive with TASE Bind reauest as user data. 1 Page 11

49、 EN 60870-6-502 : 1996 TBtnd TBcnf+ TBcnf- TABRtnd A-RELreq A-RELrsp+ Table 4 - Outgoing event list TASE.l -user TASE Bind indication TASE.1-user TASE.1-user TASE.1-user TASE Abort indication primitive AC- pro vi d e r AC-provider A-RELEASE response primitive (result= I :;Tsrt SCDRE SNCDreq SMDreq RQRJUind RO-ERRind ST1 RDTRE STSl SCDcnf+ STSO RO-INVreq STSO RO-INVreq STSO SCDmf- PUTstp RO-ERRind RO-RJUind SCDRQ RP-RJPind PUTexp STSO SCDind p2: LUTsrt PuTsrt RDTRQ RDTind PuTsrt LUTsrt SCDnp