The flow diagram shown in Figure C.17 describes a Billing client device obtaining a Billing projection.

Figure C.17—Billing projection
Table C.19—POX example: Billing projection
Step | Description |
1 | Client GETs the ProjectionReadingList from the Billing server. Client sends the following request: GET /bill/1/ca/1/pro HTTP/1.1 Host: {hostname} Accept: application/sep+xml |
2 | Billing server responds with the ProjectionReadingList. Server sends the following response: HTTP/1.1 200 OK Content-Type: application/sep+xml Content-Length: {contentLength} <ProjectionReadingList all="2" href="/bill/1/ca/1/pro" results="1" xmlns="urn:ieee:std:2030.5:ns"> <ProjectionReading href="/bill/1/ca/1/pro/1"> <mRID>d0b05a2e65144fca0000e566</mRID> <description>Billing Projections</description> <BillingReadingSetListLink all="1" href="/bill/1/ca/1/pro/1/brs"/> </ProjectionReading> </ProjectionReadingList> |
3 | Client GETs the BillingReadingSetList from the Billing server. Client sends the following request: GET /bill/1/ca/1/pro/1/brs?l=1 HTTP/1.1 Host: {hostname} Accept: application/sep+xml |
4 | Billing server responds with the BillingReadingSetList. Server sends the following response: HTTP/1.1 200 OK Content-Type: application/sep+xml Content-Length: {contentLength} <BillingReadingSetList all="1" href="/bill/1/ca/1/pro/1/brs" results="1" subscribable="1" xmlns="urn:ieee:std:2030.5:ns"> <BillingReadingSet href="/bill/1/ca/1/pro/1/brs/1"> <mRID>7cb8a5b136a9618e0000e566</mRID> <description>Start Consumption Block 2</description> <timePeriod> <duration>2419200</duration> <start>1360195200</start> </timePeriod> <BillingReadingListLink all="1" href="/bill/1/ca/1/pro/1/brs/1/br"/> </BillingReadingSet> </BillingReadingSetList> |
5 | Client GETs the BillingReadingList from the Billing server. Client sends the following request: GET /bill/1/ca/1/pro/1/brs/1/br?l=1 HTTP/1.1 Host: {hostname} Accept: application/sep+xml |
Table C.19—POX example: Billing projection (continued) | |
Step | Description |
6 | Billing server responds with the BillingReadingList. Server sends the following response: HTTP/1.1 200 OK Content-Type: application/sep+xml Content-Length: {contentLength} <BillingReadingList all="2" href="/bill/1/ca/1/pro/1/brs/1/br" results="1" xmlns="urn:ieee:std:2030.5:ns"> <BillingReading href="/bill/1/ca/1/pro/1/brs/1/br/1"> <consumptionBlock>2</consumptionBlock> <qualityFlags>40</qualityFlags> <timePeriod> <duration>0</duration> <start>1361664000</start> </timePeriod> <touTier>0</touTier> <value>400000</value> </BillingReading> </BillingReadingList> |