ANSI Std C1223Trilliant

1、- 1 -ansi std c12.23-200 xcompliance testing for standard protocol c12.18copyright 200x by the national electrical manufacturers association1300 north 17th street, suite 1847rosslyn, va 22209, usaall rights reservedthis is an unapproved draft of a proposed ansi standard, subject to change. permissio

2、n is hereby granted for ansi standards committee participants to reproduce this document for purposes of ansi standardization activities. use of information contained in this unapproved draft is at your own risk.modified october 20, 2005standard version 0.0document version 1.0- 2 -table of contents1

3、.introduction.42.scope.43.document syntax.44.references.45.definitions.45.1.psem.45.2.table.45.2.1.ansi.55.2.2.application layer.55.2.3.amr.55.2.4.baud rate .55.2.5.catastrophic failure a.k.a. fatal failure.55.2.6.crc .55.2.7.data link layer.55.2.8.device under test.55.2.9.dut.55.2.10.flc.55.2.11.fu

4、nction under test.65.2.12.fut.65.2.13.half duplex .65.2.14.meter under test.65.2.15.mut.65.2.16.octet .65.2.17.packet.65.2.18.packet envelope .65.2.19.psem.65.2.20.retrieve.65.2.21.test .75.2.22.test application.75.2.23.write.76.product submission and verification criteria.76.1.rational.76.2.submiss

5、ion rules.76.3.verification goals.76.4.verification non goals.86.5.interpretation of the standards.86.6.other criteria.86.6.1.example .example .example .example 4.107.general conformance statement.107.1.the test application.107.2.the test application as a reference ansi c12.1

6、9/ieee-1377 implementation.117.3.test results and ranking categories.117.3.1.not applicable.11- 3 -7.3.2.not tested.117.3.3.conforming.117.3.4.conforming with discrepancy.117.3.5.non-conforming.117.3.6.non-conforming, rejected.127.3.7.test remarks .128.verification objectives for ansi c12.18 devices

7、.128.1.ansi standard c12.19-1997 / ieee-1377 “utility industry standard tables”.128.1.1.type of tables.128.1.2.operations on tables .128.2.ansi standard c12.18-1996 “protocol specification for ansi type 2 optical port”.138.2.1.basic implementation assumptions.138.2.2.states and services.139.test pro

8、cedures for ansi c12.18 .149.1.test procedures for the physical layer.149.1.1.transmitter characteristics (section ).149.2.test procedures for the data link layer.159.2.1.pre-test general set-up requirements.159.2.2.basic sanity check.169.2.3.immunity to random noise .169.2.4.ack returned due

9、 to reception of a duplicate packet.179.2.5.nak returned due to crc error.179.2.6.nak returned due to inter-character timeout.179.2.7.nak returned due to long packet.189.2.8.nak returned due to invalid multi-packet flag setting.199.2.9.nak returned due to invalid first-packet flag setting.199.2.10.n

10、ak returned due to an invalid sequence number.199.2.11.retransmission triggered by a response timeout .209.2.12.retransmission triggered by a nak.209.2.13.link termination after third retry attempt (nak).219.2.14.link termination after third retry attempt (response timeout) .219.2.15.link terminatio

11、n due to channel traffic timeout.229.2.16.sensitivity to the initial state of the toggle bit.239.2.17.default packet size validation (read).239.2.18.default packet size validation (write) .249.3.psem test procedures.249.3.1.psem service transaction.249.3.2.identification service (response).259.3.3.n

12、egotiate service (change baud rate).259.3.4.negotiate service (number of packets and packet size) .269.3.5.negotiate service (honors negotiated limits).269.3.6.negotiate service (establish maximum packet limits) .279.3.7.wait service.289.3.8.terminate service working.289.3.9.service sequence state.2

13、9annex a - test reports (normative).30a.1 tests summary sheet.30a.2 detail results of “test procedures for ansi standard c12.18-1996” .31a.2.1 results of “test procedures for the data link layer”.31a.2.2 results of “psem test procedures”.31annex b - verification codes (normative).31- 4 -to do: creat

14、e a requirement metrix and qualify each test base on this metrix.to do: add examples of real message format to do: format the definitions sectiontodo: add list test equipment and traceability to standards1. introductiongive some background about this standard, what it has to accomplish, the referenc

15、ed standard and how its envisioned to be implemented in the industry. add text on pre-requisites and order of tests2. scopethis document is a collection of compliance test procedures that aim to validate the implementation correctness of ansi c12.19-1997/ieee-1377 devices that communicate using ansi

16、 c12.18-1996 standard communication.3. document syntaxexplain the various annotations used in this document.4. referencesansi std c12.18-1996:protocol specification for ansi type 2 optical portiso 7498/1:osi reference modeliso 3309-1993(e):information technology - telecommunications and information

17、exchange between systems - high-level data link control (hdlc) procedures - frame structure, annex a explanatory notes on implementation of the frame checking sequenceansi std c12.19-1997:utility industry end device data tables.5. definitionsfor the purposes of this document, the following definitio

18、ns are made for terms and syntax used throughout this document.5.1.psemprotocol specification for electricity metering as referenced in c12.18-19965.2.tablefunctionally related data elements, grouped together into a single data structure for transport as defined by ansi standard c12.19-1997- 5 -5.2.

19、1. ansiamerican national standards institute. the primary organization for fostering the development of technology standards in the united states, ansi works with industry groups and is the u.s. member of the international standards organization (iso) and the international electrotechnical commissio

20、n (iec).5.2.2. application layerthe application layer (osi layer 7) is the layer at which a user application interfaces with a communication network.5.2.3. amramr is an acronym for automated meter reading.5.2.4. baud ratebaud was the prevalent measure for data transmission speed until replaced by a

21、more accurate term, bps (bits per second). one baud is one electronic state change per second. since a single state change can involve more than a single bit of data, the bps unit of measurement has replaced it as a better expression of data transmission speed. the standards use the terms baud, baud

22、 rate, bps and bits per second interchangeably.5.2.5. catastrophic failure a.k.a. fatal failurea failure that results in temporary or permanent disruption of communication, corruption of protocol, delivery of wrong data, misrepresentation of data format, incorrect placement of data in accordance to

23、the test application reference model.5.2.6. crccrc is an acronym for “cyclic redundancy check”. the crc is used to validate the integrity of the transmitted packets.5.2.7. data link layerthe data link layer (osi layer 2) provides the synchronization of data, error detection and correction procedures

24、 used during data transmission.5.2.8. device under testa c12.19 utility industry standard tables driven device, using c12.18, c12.21 or optionally c12.22 in any combination. this device and its accessories are being tested for successful communication and data exchange with test application. the tes

25、ts are carried in a sequence, one function under test at a time.5.2.9. dutdut is an acronym for “device under test”.5.2.10. flcansi c12.19/ieee-1377 function limiting control tables (x0/x1, where x is the decade number 0-240).- 6 -5.2.11. function under testa software, firmware, hardware or protocol

26、 component test that is applied to a device under test in order to validate the correct performance of a component. the test will establish whether the component meets or does not meet interface, state, timing, data values, data representation, data placement, protocol or implementation requirements

27、 in reference to the test application. a “conforming”, “conforming with discrepancy”, “non-conforming” or “non-conforming, rejected” grade shall be assigned following the test of each function under test.5.2.12. futfut is an acronym for “function under test”.5.2.13. half duplexhalf-duplex data trans

28、mission means that data can be transmitted in both directions on a signal carrier, but not at the same time. one station can send data on the line and then shortly after receive data on the line from the same direction in which data was just transmitted.5.2.14. meter under testa device under test th

29、at is a sensor measuring water, gas or electricity.5.2.15. mutmut is an acronym for “meter under test”.5.2.16. octetan octet (from the latin “octo” or “eight”) is a sequence of eight bits. an octet is an eight-bit byte.5.2.17. packeta packet is the unit of data that is routed between an origin and a

30、 destination. in an ansi c12.18 dut, the individual packets may be fragments of a given service request. when they have all arrived, they are reassembled into the original message at the receiving end.an ansi c12.18 packet begins with the start of packet octet, = 0 xee, and ends with a two octets cr

31、c, based on the ccitt crc standard polynomial (x16+ x12 + x5 + 1).5.2.18. packet envelopethe packets start-of-packet octet, , and the end of packet crc.5.2.19. psempsem is an acronym for “protocol specification for electric metering” usa.psem is an acronym for “protocol specification for electronic

32、metering” canada.5.2.20. retrieveto cause the transmission from the dut to the test application of an entire or partial dut table. the act of data retrieval may require the invocation of some or all the following psem services: identification, negotiate, logon, wait, security, read and logoff.- 7 -5

33、.2.21. testa test is the execution of one element of a fut procedure by the test application.5.2.22. test applicationthe test application is a software application built to enable manufacturers, utilities and meter verifiers to migrate their amr and testing environment to ansi c12.19 standard-based

34、technology. it can read and program any ansi c12.19-based device that uses ansi c12.18 standard communication protocol. it also accepts and creates table definition files, which describe the architecture and state of any ansi c12.19 device. it may also be a diagnostic and test tool, which is a refer

35、ence application used to validate device design assumptions and implementation details.5.2.23. writeto cause the transmission from the test application to dut of an entire or partial dut table. the act of data writing may, in addition to the above, require the invocation of some or all the following

36、 psem services: identification, negotiate, logon, wait, security, read, write and logoff. the dut may require the invocation of the procedure 2, “save configuration”, prior to logoff for it to retain the changes.6. product submission and verification criteria6.1.rationalthis document defines a suite

37、 of tests with well-defined acceptance criteria that promotes interoperability among devices that use the referenced standards. 6.2.submission rulesit shall be required to obtain manufacturer consent to each compliance procedure for the fut. test procedures that do not meet with manufacturer approva

38、l, or are withdrawn by the manufacturer, prior to test initiation, shall be entered as “not tested”, and an explanation for the result shall be entered in the exception field of the report.the test suite outlined in this document performs an assessment of the dut and its ability to conform to the sa

39、id reference test application. the following is a summary of the general components that will, and will not be assessed as part of these conformance tests.6.3.verification goalsthe tester shall perform an assessment of the following:1.completeness of submission of dut for testing (e.g. meter, connec

40、tors, accessories, manuals, supporting electronic files, etc.)2.configuration and state disclosure of the dut prior to testing (passwords, special processes, jumper settings, mode settings, etc.)3.readiness of the dut for testing (e.g. is it in metering state, is it sealed, does it need to be set up

41、? if so, how?).4.compatibility with test application communication reference interface (c12.18) at the physical layer.5.compatibility with test application communication reference implementation (c12.18,) at the data link layer.- 8 -6.compatibility with test application protocol reference implementa

42、tion (c12.18) at the application layer (psem).7.general assessment of firmware stability, solely derived from performing the tests describes above.6.4.verification non goalsthe tester shall not perform an assessment of the following:1.dut accuracy tests (including time, interval, and metrological re

43、gisters).2.dut reliability tests (drop test, vibration test, electromagnetic susceptibility, weather, temperature, etc.).3.hardware interface quality, accuracy and signaling strengths (except where it clearly does not work reliably).4.device factory configuration and setup.5.implementation logic (as

44、sessment of device functions implemented, their delivery logic or value to customer).6.evaluation of device performance, efficiency and effective delivery of advertised functionality to the marketplace.6.5.interpretation of the standardsexplain how this standard is applied; and how other standards a

45、re interpreted. explain how ambiguity is addressed or not addresses. give an example6.6.other criteria1.where the standard is clear and unambiguous, produce a clear pass/fail a result.2.where the standard is unambiguously clear in its intent, but does not provide implementation details for the requi

46、red functionality, apply common sense.3.where the standard is vague or there is room for multiple interpretations, the test will be written to handle the alternatives and expose the variations.4.where the standard says nothing or is so vague that one cannot formulate a test, do not test.do we want t

47、o revise these examples to be specific to c12.18?6.6.1. example 1this example describes a test result where the standard is clear and unambiguous.descriptionevent_inhibit_ovf_flag is defined as follows in table 71.falseevent log is not inhibiting new entries when an overflow condition exists.trueeve

48、nt log is inhibiting new entries when an overflow condition exists overflow_flag is defined as follows in table 76.falseoverflow has not occurred.- 9 -truean attempt was made to enter an event such that the number of unread entries would have exceeded the actual number of possible entries in the log

49、.conclusionthe standard is very clear in its expression of the intended implementation of the overflow_flag status as restricted by the event_inhibit_ovf_flag control flag. therefore, one cannot argue against a test that validates the behavior of an end device, following excessive excitation that wi

50、ll cause the log to overflow. the compliant log shall not overflow if event_inhibit_ovf_flag control flag is true, and it shall overflow if event_inhibit_ovf_flag control flag is false. regardless of the state of event_inhibit_ovf_flag control flag, the overflow_flag shall be set.6.6.2. example 2thi

51、s example describes a test result where the standard is unambiguously clear in its intent but does not provide implementation details for the intent.descriptionlist_type_flag is defined as follows in table 26.falsefifo (first in first out) as placed in self read list.truecircular list as placed in s

52、elf read list.list_type is defined as follows in table 63.0fifo (first in first out) as placed in load profile storage.1circular list as placed in load profile storage.list_type is defined as follows in table 74.0fifo - as placed in log.1circular - as placed in log.conclusionthe acronym fifo is not

53、defined in the standard. however the standard qualifies the term fifo in table 26 and table 63 with the definition first in first out. using (flawed) logic one can argue that one cannot make any assumption about what the term fifo means in table 74, since the standard is silent about that (this foll

54、ows the reasoning similar to that of manufacturer tables do not have flcs). so what would one make out of fifo in table 74? does fifo mean first in first out or fill in faulty order or first in final out? one could argue that a test for fifo in table 74 cannot be carried out on this basis.reasonable

55、 people would say that it is rather obvious that based on prior use of the term fifo, the standard is clear about the intended use of the definition first in first out and the compliance standard shall perform the tests accordingly.caveat: the term circular is not defined in the standard, does it me

56、an that c12.23 cannot have a test for circular vs. fifo since we do not know what it really means in terms of placement or ordering of entries in a logs? if so, how can one build an amr system to read a log based on the c12.19 standard?6.6.3. example 3this example describes a test where the standard

57、 is vague or there is room for possibilities the test will be written to cope with these possibilities and expose the variations:description- 10 -the value of the element last_entry_seq_nbr, 0.4,294,967,295, the sequence number of the newest valid entry in the log, is not clearly described by c12.19

58、.it could retain its value after a reset list pointers or it could be reset. however, there are only two possible outcomes following the execution of a reset list pointers procedure:last_entry_seq_nbr retains its value.last_entry_seq_nbr does not retain its value.conclusionthe standard is clear that

59、 following execution of a reset list pointer procedure, all elements that describe the content (extent) of the list shall be consistent with that of the empty list. therefore, one can design a test that validates the reset action to create an empty list and also report the value of last_entry_seq_nb

60、r before and after the test. this will expose the actual implementation model of the dut. implementation variations of the last_entry_seq_nbr shall not result in a failure of a dut, unless there is a country-specific clause regarding a specific desired behavior (e.g. for canada).6.6.4. example 4this