C.20 Flow Reservation: General
Figure C.19—Flow Reservation: General
The following is a summary of the example:
Step 1—Client (PEV) creates a FlowReservationRequest at 5:00 PM for charging between midnight and 8:00 AM, 12 kWh energy requested at a power level of 7 kW, 7371 seconds duration requested.
Subsequently, the server creates a FlowReservationResponse with a charge interval between 1:00 AM and 5:20 AM at 3 kW.
Step 3—Client requests the FlowReservationResponseList to find the response matching the request. Step 4—Server responds with the FlowReservationResponseList.
Step 5—Client periodically requests the FlowReservationResponse to look for changes. Step 7—Client updates PowerStatus periodically during charging.
Note: In most cases, registration is required to obtain access to request Flow Reservations.
Table C.21—POX example: Flow Reservation—general
Step | Description |
1 | Client POSTs a FlowReservationRequest to the Flow Reservation server at 22 September 2013, 5:00 PM. Client sends the following request: POST /edev/3/frq HTTP/1.1 Host: {hostname} Content-Type: application/sep+xml Content-Length: {contentLength} <FlowReservationRequest xmlns="urn:ieee:std:2030.5:ns"> <mRID>68512866203db3b10000e566</mRID> <description>Charge from 12:00 AM to 8:00 AM</description> <creationTime>1379869200</creationTime> <!-- 9/22/2013 5:00 PM --> <durationRequested>7371</durationRequested> <!-- 6171sec charging + 1200sec conditioning --> <energyRequested> <multiplier>3</multiplier> <!-- 12 kWh --> <value>12</value> </energyRequested> <intervalRequested> <duration>28800</duration> <!-- 8 hours --> <start>1379894400</start> <!-- 9/23/2013 12:00 AM --> </intervalRequested> <powerRequested> <multiplier>3</multiplier> <!-- 7 kW --> <value>7</value> </powerRequested> <RequestStatus> <dateTime>1379869200</dateTime> <requestStatus>0</requestStatus> <!-- Requested --> </RequestStatus> </FlowReservationRequest> |
2 | Flow Reservation server responds with the FlowReservationRequest location. Server sends the following response: HTTP/1.1 201 Created Location: /edev/3/frq/1 |
3 | Client GETs the FlowReservationResponseList from the Flow Reservation server to look for a response to the request. Client sends the following request: GET /edev/3/frp HTTP/1.1 Host: {hostname} Accept: application/sep+xml |
Table C.21—POX example: Flow Reservation—general (continued) | |
Step | Description |
4 | Flow Reservation server responds with the FlowReservationResponseList. Server sends the following response: HTTP/1.1 200 OK Content-Type: application/sep+xml Content-Length: {contentLength} <FlowReservationResponseList all="1" href="/edev/3/frp" results="1" subscribable="1" xmlns="urn:ieee:std:2030.5:ns"> <FlowReservationResponse href="/edev/3/frp/1" subscribable="1"> <mRID>f8afa6fde40db98d0000ea75</mRID> <description>Charge from 1:00 AM to 5:20 AM</description> <!-- 1379869260 = 09/22/2013 5:01:00 PM --> <creationTime>1379869260</creationTime> <EventStatus> <currentStatus>0</currentStatus> <!-- Scheduled --> <dateTime>1379869260</dateTime> <potentiallySuperseded>false</potentiallySuperseded> </EventStatus> <interval> <duration>15600</duration> <!-- 4 hours 20 minutes --> <start>1379898000</start> <!-- 1:00 AM 9/23/2013 --> </interval> <energyAvailable> <!-- 12000 Wh --> <multiplier>0</multiplier> <value>12000</value> </energyAvailable> <powerAvailable> <multiplier>0</multiplier> <value>3000</value> </powerAvailable> <subject>68512866203db3b10000e566</subject> </FlowReservationResponse> </FlowReservationResponseList> |
5 | Client GETs the FlowReservationResponseList periodically (or subscribes) from the Flow Reservation server. Client sends the following request: GET /edev/3/frp HTTP/1.1 Host: {hostname} Accept: application/sep+xml |
Table C.21—POX example: Flow Reservation—general (continued) | |
Step | Description |
6 | Flow Reservation server responds with the FlowReservationResponseList. Server sends the following response: HTTP/1.1 200 OK Content-Type: application/sep+xml Content-Length: {contentLength} <FlowReservationResponseList all="1" href="/edev/3/frp" results="1" subscribable="1" xmlns="urn:ieee:std:2030.5:ns"> <FlowReservationResponse href="/edev/3/frp/1" subscribable="1"> <mRID>f8afa6fde40db98d0000ea75</mRID> <description>Charge from 1:00 AM to 5:20 AM</description> <!-- 1379869260 = 09/22/2013 5:01:00 PM --> <creationTime>1379869260</creationTime> <EventStatus> <currentStatus>0</currentStatus> <!-- Scheduled --> <dateTime>1379869260</dateTime> <potentiallySuperseded>false</potentiallySuperseded> </EventStatus> <interval> <duration>15600</duration> <!-- 4 hours 20 minutes --> <start>1379898000</start> <!-- 1:00 AM 9/23/2013 --> </interval> <energyAvailable> <!-- 12000 Wh --> <multiplier>0</multiplier> <value>12000</value> </energyAvailable> <powerAvailable> <multiplier>0</multiplier> <value>3000</value> </powerAvailable> <subject>68512866203db3b10000e566</subject> </FlowReservationResponse> </FlowReservationResponseList> |
Table C.21—POX example: Flow Reservation—general (continued) | |
Step | Description |
7 | From 1:00 AM to 5:20 AM while charging the client periodically updates its PowerStatus. Client sends the following request: PUT /edev/3/ps HTTP/1.1 Host: {hostname} Content-Type: application/sep+xml Content-Length: {contentLength} <PowerStatus xmlns="urn:ieee:std:2030.5:ns"> <!-- less than LowChargeThreshold remaining --> <batteryStatus>2</batteryStatus> <!-- 3:00 AM 9/23/2013 --> <changedTime>1379905200</changedTime> <!-- mains --> <currentPowerSource>1</currentPowerSource> <estimatedChargeRemaining>150</estimatedChargeRemaining> <PEVInfo> <chargingPowerNow> <multiplier>0</multiplier> <value>3000</value> </chargingPowerNow> <energyRequestNow> <multiplier>0</multiplier> <value>6100</value> </energyRequestNow> <maxForwardPower> <multiplier>3</multiplier> <!-- 24 kW --> <value>24</value> </maxForwardPower> <!-- 3600sec * 6100Wh/7000W + 1200sec conditioning --> <minimumChargingDuration>4337</minimumChargingDuration> <targetStateOfCharge>10000</targetStateOfCharge> <!-- 8:00 AM 9/23/2013 --> <timeChargeIsNeeded>1379923200</timeChargeIsNeeded> <timeChargingStatusPEV>1379905200</timeChargingStatusPEV> </PEVInfo> </PowerStatus> |
8 | Flow Reservation server responds: HTTP/1.1 204 No Content |