< 上一个 | 内容 | 下一个 >

C.11 Metering: Reading

This is a use case where a Metering function set client (e.g., in-premises display) queries a reading from a usage point. For this example, we will assume the meter is configured for four TOU tiers and no blocks and that we want to read the current tier three consumption.


Description: C:\Users\EA068\Desktop\ExampleSection\docs-12-0321-05-Metering_Examples\Metering - Reading.gif

Figure C.10—Meter reading


NOTE—In most cases, registration is required to obtain access to metering.


Table C.12—POX example: Meter reading


Step

Description

1

Client GETs the UsagePointList from the Metering server.

Note: If directed through FunctionSetAssignments to a particular UsagePoint, these first two steps would be skipped.

Client sends the following request:

GET /upt HTTP/1.1 Host: {hostname}

Accept: application/sep+xml

2

Metering server replies with UsagePointList. A typical response looks like:

HTTP/1.1 200 OK

Content-Type: application/sep+xml Content-Length: {contentLength}

<UsagePointList all="1" href="/upt" results="1" subscribable="0" xmlns="urn:ieee:std:2030.5:ns">

<UsagePoint href="/upt/0">

<mRID>0B00006CC8</mRID>

<description>Usage Point</description>

<roleFlags>12</roleFlags>

<serviceCategoryKind>0</serviceCategoryKind>

<status>1</status>

<MeterReadingListLink all="6" href="/upt/0/mr"/>

</UsagePoint>

</UsagePointList>

3

Client GETs the MeterReadingList from the Metering server.

Note: This and the next three steps may be repeated for each page required to read the entire list. For this example, we are requesting up to ten MeterReadings at a time. Subsequent GETs would increment the “s” query parameter by ten, or however many list items are returned.

Client sends the following request:

GET /upt/0/mr?s=0&l=10 HTTP/1.1 Host: {hostname}

Accept: application/sep+xml


Table C.12—POX example: Meter reading (continued)

Step

Description

4

Metering server replies with up to ten MeterReadingList instances. Only six are returned in this case as indicated by the MeterReadingListLink “all” attribute in step 2.

A typical response looks like:

HTTP/1.1 200 OK

Content-Type: application/sep+xml Content-Length: {contentLength}

<MeterReadingList all="6" href="/upt/0/mr" results="6" subscribable="0" xmlns="urn:ieee:std:2030.5:ns">

<MeterReading href="/upt/0/mr/5">

<mRID>1500006CC8</mRID>

<description>Instantaneous Reading for VAR’s</description>

<ReadingLink href="/upt/0/mr/5/r"/>

<ReadingTypeLink href="/upt/0/mr/5/rt"/>

</MeterReading>

<MeterReading href="/upt/0/mr/4">

<mRID>1400006CC8</mRID>

<description>Instantaneous Reading for Wh</description>

<ReadingLink href="/upt/0/mr/4/r"/>

<ReadingTypeLink href="/upt/0/mr/4/rt"/>

</MeterReading>

<MeterReading href="/upt/0/mr/3">

<mRID>1200006CC8</mRID>

<description>Interval Reading for VAR’s</description>

<ReadingSetListLink all="24" href="/upt/0/mr/3/rs"/>

<ReadingTypeLink href="/upt/0/mr/3/rt"/>

</MeterReading>

<MeterReading href="/upt/0/mr/2">

<mRID>1000006CC8</mRID>

<description>Interval Reading for Wh</description>

<ReadingSetListLink all="24" href="/upt/0/mr/2/rs"/>

<ReadingTypeLink href="/upt/0/mr/2/rt"/>

</MeterReading>

<MeterReading href="/upt/0/mr/1">

<mRID>0E00006CC8</mRID>

<description>Cumulative Reading for VAR’s</description>

<ReadingLink href="/upt/0/mr/1/r"/>

<ReadingSetListLink all="1" href="/upt/0/mr/1/rs"/>

<ReadingTypeLink href="/upt/0/mr/1/rt"/>

</MeterReading>

<MeterReading href="/upt/0/mr/0">

<mRID>0C00006CC8</mRID>

<description>Cumulative Reading for Wh</description>

<ReadingLink href="/upt/0/mr/0/r"/>

<ReadingSetListLink all="1" href="/upt/0/mr/0/rs"/>

<ReadingTypeLink href="/upt/0/mr/0/rt"/>

</MeterReading>

</MeterReadingList>

5

Client GETs the ReadingType from the Metering server.

Note: Step 5 and step 6 may be repeated for each MeterReading returned in step 4 to identify the MeterReading of interest by iterating through the MeterReadings returned in step 4.

Client sends the following request:

GET /upt/0/mr/0/rt HTTP/1.1 Host: {hostname}

Accept: application/sep+xml


Table C.12—POX example: Meter reading (continued)

Step

Description

6

Metering server replies with ReadingType. A typical response looks like:

HTTP/1.1 200 OK

Content-Type: application/sep+xml Content-Length: {contentLength}

<ReadingType href="/upt/0/mr/0/rt" xmlns="urn:ieee:std:2030.5:ns">

<accumulationBehaviour>9</accumulationBehaviour>

<commodity>1</commodity>

<dataQualifier>0</dataQualifier>

<flowDirection>1</flowDirection>

<kind>12</kind>

<numberOfConsumptionBlocks>1</numberOfConsumptionBlocks>

<numberOfTouTiers>4</numberOfTouTiers>

<phase>40</phase>

<powerOfTenMultiplier>3</powerOfTenMultiplier>

<uom>72</uom>

</ReadingType>

Note: Once the desired ReadingType is identified we proceed to the next step.

7

Client GETs the ReadingSetList from the Metering server.

Note: Because the ReadingSet resources are ordered by their timePeriod earliest time first, we can read the first ReadingSet to get the current values. If a particular historic value is desired, you would traverse the ReadingSetList looking for the ReadingSet with the appropriate time stamp.

Client sends the following request:

GET /upt/0/mr/0/rs?s=0&l=4 HTTP/1.1 Host: {hostname}

Accept: application/sep+xml

8

Metering server replies with ReadingSetList with the ReadingSet of interest. A typical response looks like:

HTTP/1.1 200 OK

Content-Type: application/sep+xml Content-Length: {contentLength}

<ReadingSetList all="1" href="/upt/0/mr/0/rs" results="1" subscribable="0" xmlns="urn:ieee:std:2030.5:ns">

<ReadingSet href="/upt/0/mr/0/rs/0">

<mRID>0D00006CC8</mRID>

<description>Cumulative Reading Set for Whrs</description>

<timePeriod>

<duration>7737</duration>

<start>1338817886</start>

</timePeriod>

<ReadingListLink all="5" href="/upt/0/mr/0/rs/0/r"/>

</ReadingSet>

</ReadingSetList>

9

Client GETs the ReadingList from the Metering server.

Note: Because the Reading resources are ordered by their touTier and remembering the first element is the total Reading, we can read the fourth (index 3) reading to get the current tier three value.

Client sends the following request:

GET /upt/0/mr/0/rs/0/r?s=3&l=12 HTTP/1.1 Host: {hostname}

Accept: application/sep+xml


Table C.12—POX example: Meter reading (continued)

Step

Description

10

Metering server replies with ReadingList with the Reading of interest. A typical response looks like:

HTTP/1.1 200 OK

Content-Type: application/sep+xml Content-Length: {contentLength}

<ReadingList all="5" href="/upt/0/mr/0/rs/0/r" results="1" xmlns="urn:ieee:std:2030.5:ns">

<Reading href="/upt/0/mr/0/rs/0/r/3">

<value>361231</value>

</Reading>

</ReadingList>