C.21 Flow Reservation: Cancel
Figure C.20—Flow Reservation: Cancel
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.
Subsequently, the server creates a FlowReservationResponse with a charge interval between 1:00 AM and 5:20 AM at 3 kW.
Step 3—At 1:00 AM the client wants to change the time the charging is needed and therefore creates a new FlowReservationRequest for charging between 1:00 AM and 5:00 AM.
Subsequently, the server creates a FlowReservationResponse with a charge interval between 1:02 AM and 4:22 AM at 4 kW.
Step 5—Client cancels the original FlowReservationRequest.
Subsequently, the server cancels the original FlowReservationResponse.
Step 7—Client requests the FlowReservationResponseList.
Step 8—Server responds with the FlowReservationResponseList, the first FlowReservationResponse is canceled, and the second FlowReservationResponse is Active.
Table C.22—POX example: Flow Reservation—cancel
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 | Due to a change in when the vehicle is needed, at 23 September 2013, 1:00 AM the client creates a second FlowReservationRequest for charging between 1:00 AM and 5:00 AM. 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>68512866203db3b20000e566</mRID> <description>Charge from 1:00 AM to 6:00 AM</description> <creationTime>1379898000</creationTime> <!-- 9/23/2013 1:00 AM --> <durationRequested>7371</durationRequested> <!-- 6171sec charging + 1200sec conditioning --> <energyRequested> <multiplier>3</multiplier> <!-- 12 kWh --> <value>12</value> </energyRequested> <intervalRequested> <duration>14400</duration> <!-- 5 hours --> <start>1379898000</start> <!-- 9/23/2013 1:00 AM --> </intervalRequested> <powerRequested> <multiplier>3</multiplier> <!-- 7 kW --> <value>7</value> </powerRequested> <RequestStatus> <dateTime>1379898000</dateTime> <requestStatus>0</requestStatus> <!-- Requested --> </RequestStatus> </FlowReservationRequest> |
Table C.22—POX example: Flow Reservation—cancel (continued) | |
Step | Description |
4 | Flow Reservation server responds with the FlowReservationRequest location. Server sends the following response: HTTP/1.1 201 Created Location: /edev/3/frq/2 |
5 | Client PUTs a canceled status to the first FlowReservationRequest. Client sends the following request: PUT /edev/3/frq/1 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>1379898060</dateTime> <requestStatus>1</requestStatus> <!-- Canceled --> </RequestStatus> </FlowReservationRequest> |
6 | Flow Reservation server sends the following response: HTTP/1.1 204 No Content |
7 | Client GETs the FlowReservationResponseList periodically (or subscribes) from the Flow Reservation server. Client sends the following request: GET /edev/3/frp?l=2 HTTP/1.1 Host: {hostname} Accept: application/sep+xml |
Table C.22—POX example: Flow Reservation—cancel (continued) | |
Step | Description |
8 | Flow Reservation server responds with the FlowReservationResponseList. The first FlowReservationResponse |
is canceled, the second is active. | |
Server sends the following response: | |
HTTP/1.1 200 OK | |
Content-Type: application/sep+xml | |
Content-Length: {contentLength} | |
<FlowReservationResponseList all="2" href="/edev/3/frp" results="2" | |
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> | |
<creationTime>1379869260</creationTime> | |
<EventStatus> | |
<!-- Canceled --> | |
<currentStatus>2</currentStatus> | |
<dateTime>1379898060</dateTime> | |
<potentiallySuperseded>false</potentiallySuperseded> | |
</EventStatus> | |
<interval> | |
<!-- 4 hours 20 minutes --> | |
<duration>15600</duration> | |
<!-- 1:00 AM 9/23/2013 --> | |
<start>1379898000</start> | |
</interval> | |
<energyAvailable> | |
<multiplier>0</multiplier> | |
<value>12000</value> | |
</energyAvailable> | |
<powerAvailable> | |
<multiplier>0</multiplier> | |
<value>3000</value> | |
</powerAvailable> | |
<subject>68512866203db3b10000e566</subject> | |
</FlowReservationResponse> | |
<FlowReservationResponse href="/edev/3/frp/2" subscribable="1"> | |
<mRID>f8afa6fde40db98e0000ea75</mRID> | |
<description>Charge from 1:02 AM to 4:22 AM</description> | |
<creationTime>1379898120</creationTime> | |
<EventStatus> | |
<!-- Active --> | |
<currentStatus>1</currentStatus> | |
<dateTime>1379898120</dateTime> | |
<potentiallySuperseded>false</potentiallySuperseded> | |
</EventStatus> | |
<interval> | |
<!-- 3 hours 20 minutes --> | |
<duration>12000</duration> | |
<!-- 1:02 AM 9/23/2013 --> | |
<start>1379898120</start> | |
</interval> | |
<energyAvailable> | |
<multiplier>0</multiplier> | |
<value>12000</value> | |
</energyAvailable> | |
<powerAvailable> | |
<multiplier>0</multiplier> | |
<value>4000</value> | |
</powerAvailable> | |
<subject>68512866203db3b20000e566</subject> | |
</FlowReservationResponse> | |
</FlowReservationResponseList> | |