Reservation planning RPC view of RESET RESET deals with the following information items:

34 Copyright © 2014 Open Geospatial Consortium

6.3.3 Reservation planning

The typical scenario is: ‐ The client gets the capabilities of the server using the GetCapabilities operation GET . ‐ Selects the sensor to be tasked from the GetCapabilities and optionally if more information is required the DescribeSensor methods GET procedures{sps:procedure}{swes:sensorDescriptionFormat?}. The user then requests the format of the Tasking parameters needed to submit a task, through the DescribeTasking operation GET procedures{sps:procedure}tasking. ‐ Then this structure is filled in on the client side, allowing the user to choose the area of interest, the time of interest, as well as other parameters such as the instrument mode. ‐ This structure is then sent to the server as part of a Reserve request corresponding to POST reservation. This will return a set of segments representing the acquisitions that have been submitted to fulfill the given request. This will start a new reservation task. ‐ This will reserve the task. The user then has the possibility, until the reservation expiration time, to change the request by using the Update operation PUT reservation{taskID}. ‐ If the result is satisfactory, the user can then submit the task with the Confirm operation POST reservation{taskID}. This will start a new planning task. ‐ After that, the following events are possible: o The user requests the status of the task using the GetStatus operation GET planning{taskID}, or the complete description of the task using the GetTask operation GET planning{taskID}segments. o The user cancels the task using the Cancel operation DELETE planning{taskID}. ‐ Once the task is finished, which corresponds to all segments involved begin acquired, the user can do the following: o Get the data describing a given segment, through the GetTask GET planning{taskID}segments, and the results with the DescribeResultAccess operationGET planning{taskID}results. This will provide the means to connect to the Download Server in order to get the acquired products. ‐ After assessing these results, validate a given segment using the Validate POST planning{taskID}segments{segmentID} operation. 35 Copyright © 2014 Open Geospatial Consortium Figure 6-3 Reservation planning sequence diagram e er ationPlanning RESET Client RESET Server Download Server opt opt opt opt opt getCapabilities describeSensor describeTasking fillInRequest reservetaskingParameters updatetaskingParameters confirm getStatustaskID canceltaskID getTasktaskID describeResultAccesstaskID validatetaskID, segmentID downloadResults 36 Copyright © 2014 Open Geospatial Consortium

7. Resource model