1、BRITISH STANDARD BS EN 61334-4-32: 1997 IEC 61334-4-32: 1996 Distribution automation using distribution line carrier system Part 4: Data communication protocols Section 32: Data link layer Logical link control (LLC) The European Standard EN 61334-4-32:1997 has the status of a British Standard ICS 29
2、.240.20; 35.100.20BSEN61334-4-32:1997 This British Standard, having been prepared under the directionof the Electrotechnical Sector Board, was published underthe authority of the Standards Board and comes intoeffect on 15 November 1997 BSI 04-2000 ISBN 0 580 28701 7 National foreword This British St
3、andard is the English language version of EN 61334-4-32:1997. It is identical with IEC 61334-4-32:1996. The UK participation in its preparation was entrusted to Technical Committee PEL/57, Power system control and associated communications, which has the responsibility to: aid enquirers to understan
4、d the text; present to the responsible international/European committee any enquiries on the interpretation, or proposals for change, and keep the UK interests informed; monitor related international and European developments and promulgate them in the UK. A list of organizations represented on this
5、 committee can be obtained on request to its secretary. From 1 January 1997, all IEC publications have the number 60000 added to the old number. For instance, IEC 27-1 has been renumbered as IEC 60027-1. For a period of time during the change over from one numbering system to the other, publications
6、 may contain identifiers from both systems. Cross-references Attention is drawn to the fact that CEN and CENELEC Standards normally include an annex which lists normative references to international publications with their corresponding European publications. The British Standards which implement th
7、ese international or European publications may be found in the BSI Standards Catalogue under the section entitled “International Standards Correspondence Index”, or by using the “Find” facility of the BSI Standards Electronic Catalogue. A British Standard does not purport to include all the necessar
8、y provisions of a contract. Users of British Standards are responsible for their correct application. Compliance with a British Standard does not of itself confer immunity from legal obligations. Summary of pages This document comprises a front cover, an inside front cover, pages i and ii, theEN tit
9、le page, pages 2 to 28, an inside back cover and a back cover. This standard has been updated (see copyright date) and may have had amendments incorporated. This will be indicated in the amendment table on the inside front cover. Amendments issued since publication Amd. No. Date CommentsBSEN61334-4-
10、32:1997 BSI 04-2000 i Contents Page National foreword Inside front cover Foreword 2 Test of EN 61334-4-32 3ii blankEUROPEAN STANDARD NORME EUROPENNE EUROPISCHE NORM EN 61334-4-32 December 1996 ICS 35.100.20 Descriptors: Electric power, distribution automation, line carrier systems, data communicatio
11、n protocols, data link layer, logical link control English version Distribution automation using distribution line carrier systems Part 4: Data communication protocols Section 32: Data link layer Logical link control (LLC) (IEC 1334-4-32:1996) Automatisation de la distribution laide de systmes de co
12、mmunication courants porteurs Partie 4: Protocoles de communication de donnes Section 32: Couche de liaison de donnes Contrle de liaison logique (LLC) (CEI 1334-4-32:1996) Verteilungsautomatisierung mit Hilfe von Trgersystemen auf Verteilungsleitungen Teil 4: Datenkommunikationsprotokolle Hauptabsch
13、nitt 32: Sicherungsschicht, Steuerung logischer Verbindungen (LLC) (IEC 1334-4-32:1996) This European Standard was approved by CENELEC on 1996-10-01. CENELEC members are bound to comply with the CEN/CENELEC Internal Regulations which stipulate the conditions for giving this European Standard the sta
14、tus of a national standard without any alteration. Up-to-date lists and bibliographical references concerning such national standards may be obtained on application to the Central Secretariat or to any CENELEC member. This European Standard exists in three official versions (English, French, German)
15、. A version in any other language made by translation under the responsibility of a CENELEC member into its own language and notified to the Central Secretariat has the same status as the official versions. CENELEC members are the national electrotechnical committees of Austria, Belgium, Denmark, Fi
16、nland, France, Germany, Greece, Iceland, Ireland, Italy, Luxembourg, Netherlands, Norway, Portugal, Spain, Sweden, Switzerland and UnitedKingdom. CENELEC European Committee for Electrotechnical Standardization Comit Europen de Normalisation Electrotechnique Europisches Komitee fr Elektrotechnische N
17、ormung Central Secretariat: rue de Stassart 35, B-1050 Brussels 1996 Copyright reserved to CENELEC members Ref. No. EN 61334-4-32:1996 EEN61334-4-32:1996 2 BSI 04-2000 Foreword The text of document 57/266/FDIS, future edition 1 of IEC 1334-4-32, prepared by IEC TC 57, Power system control and associ
18、ated communications, was submitted to the IEC-CENELEC parallel vote and was approved by CENELEC as EN 61334-4-32 on1996-10-01. The following dates were fixed: Annexes designated “normative” are part of the body of the standard. In this standard, Annex ZA is normative. Annex ZA has been added by CENE
19、LEC. Endorsement notice The text of the International Standard IEC 1334-4-32:1996 was approved by CENELEC as a European Standard without any modification. Contents Page Foreword 2 1 General 3 1.1 Scope and object 3 1.2 Normative references 3 2 LLC service specification 3 2.1 Overview of interactions
20、 3 2.2 DL_Data.request 7 2.3 DL_Data.confirm 8 2.4 DL_Data.indication 8 2.5 DL_Reply.request 9 2.6 DL_Reply.confirm 9 2.7 DL_Reply.indication 10 2.8 DL_Update_Reply.request 11 2.9 DL_Update_Reply.confirm 11 2.10 DL_Update_Reply.indication 12 2.11 DL_Broadcast.request 13 3 LLC to MAC sublayer interfa
21、ce 13 3.1 Overview of interactions 13 Page 3.2 MA_Data.request 13 3.3 MA_Data.confirm 14 3.4 MA_Data.indication 14 4 LLC protocol data unit structure (LLC_PDU) 15 4.1 General 15 4.2 LLC_PDU format 15 4.3 Control field 15 4.4 Address field 17 4.5 Invalid LLC_PDU 17 5 LLC procedures description 17 5.1
22、 Overview of the procedures 17 5.2 Sender and receiver state tables 18 5.3 Transitions table description 25 Annex ZA (normative) Normative references to international publications with their corresponding European publications Inside back cover Figure 1 Relationship to reference model 4 Figure 2 Sen
23、d Data Non-acknowledged 5 Figure 3 Update_Reply 6 Figure 4 Reply Data on Request 6 Figure 5 Transmission example 7 Figure 6 LLC_PDU format 15 Figure 7 Control field 16 Figure 8 DSAP and SSAP 17 Figure 9 SDN state diagram 21 Figure 10 RDR state diagram 22 Figure 11 Receiver state diagram 25 Table 1 S
24、ender state transition table 19 Table 2 Receiver state transition table 23 latest date by which the ENhas to be implemented at national level by publication of an identical national standard or by endorsement (dop) 1997-07-01 latest date by which the national standards conflicting with the EN haveto
25、 be withdrawn (dow) 1997-07-01EN61334-4-32:1996 BSI 04-2000 3 1 General 1.1 Scope and object This section of IEC 1334-4 covers the services required of, or by, the DCP Logical Link Control (LLC) sublayer entity at the logical interfaces with the application layer and the MAC sublayer. In general, th
26、e services of a layer (or a sublayer) are the capabilities which it offers to a user in the next layer. In order to provide its service, a layer (or a sublayer) builds its functions on the services which it requires from the next lower layer or sublayer. Services are specified by describing the info
27、rmation flow between the application layer and the MAC-sublayer. That is by describing the service primitives and parameters which characterize each service. These primitives are associated with the connectionless transmission. NOTE 1This section refers to the three-layer reference model described i
28、n IEC 1334-4-1 but provisions are made for future extensions of this model to more than three layers. NOTE 2Provisions are also made in this section for future extensions to connection oriented transmission. In this clause, reference is made to the OSI reference model ISO 7498. 1.2 Normative referen
29、ces The following normative documents contain provisions which, through reference in this text, constitute provisions of this section of IEC 1334-4. At the time of publication, the editions indicated were valid. All normative documents are subject to revision, and parties to agreements based on this
30、 section of IEC 1334-4 are encouraged to investigate the possibility of applying the most recent editions of the normative documents indicated below. Members of IEC and ISO maintain registers of currently valid International Standards. IEC 1334-4-1:1996, Distribution automation using distribution li
31、ne carrier systems Part 4: Data communication protocols Section 1: Reference model of the communication system. ISO 7498:1984, Information processing systems Open Systems Interconnection Basic Reference Model. 2 LLC service specification This clause specifies the services required of the LLC sublaye
32、r by the application layer, as viewed from the application layer, to allow a local application layer entity to exchange packets with remote peer application layer entities using DCP LLC operations at the logical link control sublayer. The services are described in an abstract way. 2.1 Overview of in
33、teractions 2.1.1 Basic services Three ground services are proposed as usual in the OSI model for the main transmission purposes: DL_Data.request DL_Data.confirm DL_Data.indication These services are non-acknowledged and in connectionless mode.EN61334-4-32:1996 4 BSI 04-2000 Figure 1 Relationship to
34、reference modelEN61334-4-32:1996 BSI 04-2000 5 2.1.2 Unsolicited services Six services are proposed for providing facilities to transfer unsolicited L_SDU between a remote application layer entity and the local application layer entity: DL_Reply.request DL._Reply.indication DL_Reply.confirm The DL_R
35、eply.services are designed for asking the remote LLC sublayer entity to send a previously prepared L_SDU. DL_Update_Reply.request DL_Update_Reply.indication DL_Update_Reply.confirm The DL_Update_Reply services are designed to prepare DL_Reply services. Figure 2 Send Data Non-acknowledgedEN61334-4-32
36、:1996 6 BSI 04-2000 Figure 3 Update_Reply Figure 4 Reply Data on RequestEN61334-4-32:1996 BSI 04-2000 7 2.1.3 Management service One service is provided for management purposes: DL_Broadcast.request This service uses the broadcast facilities available at the MAC sublayer entity. This service is used
37、 to transmit very few data to all peer LLC sublayer entities. 2.2 DL_Data.request 2.2.1 Function The DL_Data.request primitive is passed to the LLC sublayer entity to request that an L_SDU be sent to a remote LLC sublayer entity or entities using the LLC transmission procedures. 2.2.2 Structure The
38、semantics of the primitive are as follows: The Source_LSAP and Destination_LSAP parameters specify the local and remote LSAPs involved in the data unit transmission. The Destination_address parameter specifies the address of the remote station involved in the data unit transmission. The L_SDU parame
39、ter specifies the link data unit to be transferred by the LLC sublayer entity to the peer LLC sublayer entity or entities. The Link_class parameter is reserved for future DL_Data transfer service extension. Figure 5 Transmission example DL_Data.request ( Destination_LSAP, Source_LSAP, Destination_ad
40、dress, L_SDU, Link_class )EN61334-4-32:1996 8 BSI 04-2000 2.2.3 Use This primitive is generated by the application layer entity whenever data is transmitted to a peer application layer entity or entities. The receipt of this primitive will cause the LLC sublayer entity to append all LLC specific fie
41、lds (given below) and pass the properly formed L_PDU to the lower layers of protocol for transfer to the peer LLC sublayer entity or entities. The receipt of this primitive will generate a MA_Data.request for transfer to the MAC sublayer entity. 2.3 DL_Data.confirm 2.3.1 Function The DL_Data.confirm
42、 issues a local confirmation of the transmission of the L_PDU. This primitive has only local significance and provides an appropriate response to the application layer entity which initiated a DL_Data.request primitive indicating the local success or failure of the request, as specified by the lower
43、 levels. 2.3.2 Structure The semantics of the primitive are as follows: The Source_LSAP and Destination_LSAP parameters specify the local and remote LSAPs involved in the data unit transmission. The Source_LSAP parameter specifies the LSAP which has previously issued a DL_Data.request and to which t
44、he confirm has to be sent. The Destination_address parameter specifies the address of the remote station involved in the data unit transmission. The Transmission_Status parameter is used to pass status information back to the local requesting application layer entity. It is used to indicate the succ
45、ess or failure of the previous associated DL_Data.request primitive. 2.3.3 Use This primitive is generated in response to a DL_Data.request primitive back to the local application layer entity. This primitive is generated on an incoming MA_Data.confirm service issued by the local MAC sublayer entity
46、. It is assumed that sufficient information is available to the application layer entity to associate the response with the appropriate request. 2.4 DL_Data.indication 2.4.1 Function The DL_Data.indication primitive is passed from the LLC sublayer to the application layer entity or entities to indic
47、ate the arrival of a L_PDU. This primitive defines the transfer of data from the LLC sublayer entity to the application layer entity or entities. 2.4.2 Structure The semantics of the primitive are as follows: DL_Data.confirm ( Destination_LSAP, Source_LSAP, Destination_address, Transmission_Status )
48、 DL_Data.indication ( Destination_LSAP, Source_LSAP, Destination_address, Source_address, L_SDU, Link_class )EN61334-4-32:1996 BSI 04-2000 9 The Destination_LSAP and Source_LSAP parameters specify the local and remote LSAPs involved in the data unit transmission. The Destination_LSAP may be either a
49、n individual or a group address as specified by the incoming L_PDU. The Destination_address and Source_address parameters specify the address of the local and of the remote stations involved in the data unit transmission. The Destination_address may be either an individual or a group address. The L_SDU parameter specifies the link service data unit which has been received by the LLC sublayer entity. The Link_class parameter is reserved for future DL_Data transfer service ext
