实例介绍
电能测量--付费系统--第52部分:标准传输规范(STS)--直接本地连接用双向虚拟令牌载波的物理层协议
IEC Ec62055-52 Edition 1.0 2008-05 NTERNATIONAL STANDARD Electricity metering-Payment systems Part 52: Standard transfer specification (sTS)- Physical layer protocol for a two-way virtual token carrier for direct local connection INTERNATIONAL ELECTROTECHNICAL COMMISSION PRICE CODE XA Cs35.100.20:17220.20:9114050 SBN28318-9747-5 2 62055-52@EC:2008(E) CONTENTS FOREWORD NTRODUCTION cope 2 Normative references 3 Terms definitions and abbreviations 10 3. 1 Terms and definitions 10 3.2 Abbreviations 10 3.3 Notation and terminology. 3.4 Numbering conventions ::: 12 4 STS protocol reference model 12 5 POSToToken CarrierInterface: Physical layer protocol...................13 6 TokenCarrierToMeterInterface: Physical layer protocol 13 6.1 TCDU 13 6.1.1 General 6.1.2 Token Data 13 6.1.3 Authentication result 14 6.1 4 Validation result 14 6.1.5 Token result 14 6.2 Physical connection and signal interfaces 6.2.1 Interface options .14 6.2.2 Option 1: Optical interface 14 6.2.3 Option 2: Current loop interface 14 6.2.4 Option 3: Voltage interface 14 6.3 Character transmission 翻B面 国,1 14 6.3. 1 Transmission type 14 6.3.2 Transmission format 15 6.3.3 Transmission speed 15 6.3.4 Character encoding 15 6.4 Message syntax definitions 17 6.4.1 General 17 6.4.2 IDRequest message 17 6.4.3 IDResponse message ..17 6.4.4 ReadCommand message .17 6.4.5 Write Command message 18 6.4.6 Break Command message 18 6.4.7 ACK: Acknowledge message 6.4.8 NAK: NegativeAcknowledge message 18 6.4. 9 Data message 18 6.5 Message field definitions 19 6.6 Physical layer protocol functions 21 6.6.1 Server protocol flow diagram 21 6.6.2 IDRequestProcessing function 22 6.6.3 ReadCommand Processing function 6.6. 4 Write Command Processing function 24 6.6.5 Break Command Processing function 25 62055-52@|EC:2008(E) 6.6.6 Undefined command processing…… 6.6.7 TokenLockout function 1面国 ..:a: 27 6.7 Server timing requirements..... 27 6.7.1nter- message and inter- character timing……… .27 6.7.2 Transmission error timing 28 6.7.3 Message execution timing 29 6.8 RegisterTable… ..30 6.8.1 Register Table interface class 6.8.2 Register interface class 31 6.8.3 Predefined Registers and registerId values 32 6. 9 Companion specifications and Register Table instantiations. .................................43 7 Maintenance of sts entities and related services .43 7.1 General 43 7.2 Register T able maintenance 44 7.3 Register maintenance……. 44 7.4 tabled maintenance 44 7.5 Foin maintenance 45 7.6 protocol Version maintenance .45 7.7 server status maintenance 45 78 token status maintenance .45 79 software version maintenance 45 Annex A(normative) Server state diagrams for request message processing 46 Bibliography… 51 Figure 1-Physical layers of the STS protocol stack 12 Figure 2-Character transmission format 15 Figure 3- Server protocol flow diagram 2 Figure 4-Inter-message timing responses 28 Figure 5-Transmission error timing .29 Figure A 1- Server state diagram for IDRequestProcessing function 46 Figure A 2-Server state diagram for Read Command Processing function 47 Figure A 3- Server state diagram for Write Command Processing function 48 Figure A 4- Server state diagram for Break Command Processing function 49 Figure A. 5- server state diagram for undefined command 0 Table 1-data elements in the tcdu 13 Table 2- Bit-encoding of a 7-bit character code.... .15 Table 3-Character encoding example of a 14-bit binary number 16 Table 4-Character encoding example of a 4-digit hexadecimal number .16 Table 5- character encoding example of a 4-digit decimal number 17 Table 6-Message field definitions 19 Table 7-Request messages supported by the server 22 Table8- Response messages supported by the server………… .22 Table 9- functions supported by the server 22 4 62055-52@EC:2008(E) Table 10- Server timing requirements to respond to a request message .28 Table 11-Inter-character timing requirements ..28 Table 12- Transmission error recovery wait period 29 Table 13-Generic format for register table ..30 Table 14-generic format for Register Tabe15- Predefined Registers and registerID values……… 32 Table 16-Instance format for Protocol Version register .33 Table 17-Defined protocol Version values 34 Table 18-Instance format for T abled register 34 Table 19-Instance format for Server status register .35 Table 20- defined serverstatus values 36 Table 21 -Instance format for software version register 37 Table 22-Instance format for Binary Token Entry register 38 Table 23-Instance format for Token Status register 39 Table 24- defined token status values 40 Table 25- Instance format for Token LockoutTimeRemaining register .42 Table 26- Entities/services requiring maintenance service 44 62055-52@|EC:2008(E) 5 INTERNATIONAL ELECTROTECHNICAL COMMISSION ELECTRICITY METERING PAYMENT SYSTEMS Part 52: Standard transfer specification (STs) Physical layer protocol for a two-way virtual token carrier for direct local connection FOREWORD 1)The International Electrotechnical Commission(IEC)is a worldwide organization for standardization comprising all national electrotechnical committees (IEc National Committees). the object of iec is to promote international co-operation on all questions concerning standardization in the electrical and electronic fields. To this end and in addition to other activities, IEC publishes International Standards: Technical Specifications Technical Re ports, Publicly Available Specifications (PAS)and Guides(hereafter referred to as "lEC Publication (s)"). Their preparation is entrusted to technical committees, any IEC National Committee interested in the subject dealt with may participate in this preparatory work. International, governmental and non governmental organizations liaising with the IEC also participate in this preparation. IEC collaborates closely with the International Organization for standardization (Iso) in accordance with conditions determined by agreement between the two organizations 2)The formal decisions ar agreements of IEC on technical matters express, as nearly as possible, an international consensus of opinion on the relevant subjects since each technical committee has representation from all interested Ec National committees 3)IEC Publications have the form of recommendations for international use and are accepted by IEC National Committees in that sense. While all reasonable efforts are made to ensure that the technical content of ec Publications is accurate, IEC cannot be held responsible for the way in which they are used or for any misinterpretation by any end user 4)In order to promote international uniformity, IEC National Committees undertake to apply lEC Publications transparently to the maximum extent possible in their national and regional publications. Any divergence between any IEC Publication and the corresponding national or regional publication shall be clearly indicated in the latter 5)EC provides no marking procedure to indicate its approval and cannot be rendered responsible for any equipment declared to be in conformity with an IEC Publication 6)All users should ensure that they have the latest edition of this publication 7)No liability shall attach to IEC or its directors, employees, servants or agents including individual experts and members of its technical committees and lEC National Committees for any personal injury, property damage or other damage of any nature whatsoever, whether direct or indirect, or for costs (including legal fees and arising out of the publ liance upon, this IEc Publication ny other EC Publications 8) Attention is drawn to the Normative references cited in this publication Use of the referenced publications is indispensable for the correct application of this publication 9)Attention is drawn to the possibility that some of the elements of this IEC Publication may be the subject of patent rights. IEC shall not be held responsible for identifying any or all such patent rights e International Electrotechnical Commission (IEC) draws attention to the fact that it is claimed that compliance this International Standard may involve the use of a maintenance service concerning encryption key management and the stack of protocols on which the present International Standard lEC 62055-41 is based. [See Clause C. 1 of lEC 62055-41. The lEc takes no position concerning the evidence, validity and scope of this maintenance service The provider of the maintenance service has assured the lec that he is willing to provide services under reasonable and non-discriminatory terms and conditions with applicants throughout the world. In this respect, the statement of the provider of the maintenance service is registered with the lEC. Information may be obtained from Address: The STS Association, P.O. Box 868, Ferndale 2160, Republic of South africa +27117891384 Fax: +27117891385 Email: email @sts. org.za WEbsitehttp://www.sts.org.za 6 62055-52@Ec2008(E technical committee 13: Electrical energy measurement, tariff and load contr e International Standard IEC 62055-52 has been prepared by working group 15, of IEC lEC 62055-52 is complementary to, and should be read in conjunction with, IEC 62055-4 1 The text of this standard is based on the following documents FDIS Report on voting 13/1424/FD|S 13/1428/RVD Full information on the voting for the approval of this standard can be found in the report on voting indicated in the above table This publication has been drafted in accordance with the Iso/EC Directives, Part 2 A list of all parts of lEC 62055 series, published under the general title Electricity metering Payment systems, can be found on the IEC website The committee has decided that the contents of this publication will remain unchanged until themaintenanceresultdateindicatedonthelecwebsiteunder"http://webstore.iecchin the data related to the specific publication. At this date, the publication will be reconfirmed withdrawn replaced by a revised edition, or amended a bilingual version of this publication may be issued at a later date 62055-52@|EC:2008(E) INTRODUCTION The IEC 62055 series covers payment systems, encompassing the customer information systems, point of sales systems, token carriers, payment meters and the respective interfaces that exist between these entities. At the time of preparation of this part, lEC 62055 comprised the following parts, under the general title Electricity metering- Payment systems Part 21: Framework for standardization Part 31: Particular requirements Static payment meters for active energy (classes 1 and 2 Part 41: Standard transfer specification (sTS)-Application layer protocol for one-way token carrier systems Part 51: Standard transfer specification(STS)-Physical layer protocol for one-way numeric and magnetic card token carriers Part 52: Standard transfer specification (STS)-Physical layer protocol for a two-way virtual token carrier for direct local connection The Part 4x series specifies application layer protocols and the Part 5x series specifies physical layer protocols The protocol in this International Standard is based on the lEC 62056-21 communication protocol and has been simplified by removing features from the IEC 62056-21 protocol, which are not required for the current requirements of data exchange between the vtco7 client device and the payment meter server. The main design objective in establishing the protocol has been the requirement to reduce the complexity of the software that is needed to implement this protocol in the payment meter This directly relates to a smaller memory size that can be translated into a cost saving or the ability to include additional software features for a given memory size The Standard Transfer Specification (STS)is a secure message protocol that allows information to be carried between point of sale(Pos) equipment and payment meters and it caters for several message types such as credit, configuration control, display and test instructions. It further specifies devices and codes of Practice that allows for the secure management (generation, storage, retrieval and transportation) of cryptographic keys used within the system The national electricity utility in South Africa(Eskom) first developed and published the StS in 1993 and transferred ownership to the STs Association in 1998 for management and further development Prior to the development of the STs,a variety of proprietary payment meters and Pos equipment had been developed, which were however not compatible with each other. This gave rise to a definite need among the major users to move towards standardized solutions in addressing operational problems experienced where various types of payment meter and Pos equipment had to be operated simultaneously. The Standard transfer Specification was developed that would allow for the application and inter-operability of payment meters and POS equipment from multiple manufacturers in a payment metering installation The Token Carrier is the physical medium used to transport information from a pos or the management system to the payment meter, or from the payment meter to the Pos or management system. This part of lEC 62055 specifies a virtual token carrier as embodied in a direct local connection between a management device client and a payment meter server. It has been assigned identification code 07 by the sTs Association and is also generally referred to as VTCO7. New token carriers can be proposed as new work items through the National committees or through the sts Association Although the main implementation of the STs is in the electricity supply industry, it inherently provides for the management of other utility services like water and gas. Future revisions of 62055-52@Ec2008(E the STs may allow for other token carrier technologies like smart cards and memory keys with two-way functionality The STs Association has established D-type liaison with working group 15 of IEC Tc 13 for the development of standards within the scope of the STs, and is thus responsible for the maintenance of any such lEC standards that might be developed as a result of this liaison The STS Association is also registered with the lEc as a Registration Authority for providing maintenance services in support of the Sts (see Clause C. 1 of lEc 62055-41 for more information) 【实例截图】
【核心代码】
标签:
小贴士
感谢您为本站写下的评论,您的评论对其它用户来说具有重要的参考价值,所以请认真填写。
- 类似“顶”、“沙发”之类没有营养的文字,对勤劳贡献的楼主来说是令人沮丧的反馈信息。
- 相信您也不想看到一排文字/表情墙,所以请不要反馈意义不大的重复字符,也请尽量不要纯表情的回复。
- 提问之前请再仔细看一遍楼主的说明,或许是您遗漏了。
- 请勿到处挖坑绊人、招贴广告。既占空间让人厌烦,又没人会搭理,于人于己都无利。
关于好例子网
本站旨在为广大IT学习爱好者提供一个非营利性互相学习交流分享平台。本站所有资源都可以被免费获取学习研究。本站资源来自网友分享,对搜索内容的合法性不具有预见性、识别性、控制性,仅供学习研究,请务必在下载后24小时内给予删除,不得用于其他任何用途,否则后果自负。基于互联网的特殊性,平台无法对用户传输的作品、信息、内容的权属或合法性、安全性、合规性、真实性、科学性、完整权、有效性等进行实质审查;无论平台是否已进行审查,用户均应自行承担因其传输的作品、信息、内容而可能或已经产生的侵权或权属纠纷等法律责任。本站所有资源不代表本站的观点或立场,基于网友分享,根据中国法律《信息网络传播权保护条例》第二十二与二十三条之规定,若资源存在侵权或相关问题请联系本站客服人员,点此联系我们。关于更多版权及免责申明参见 版权及免责申明
网友评论
我要评论