Release Tuner Reservation

Release Tuner Reservation Message

The client can release an existing tuner reservation. Normally, a token need not be released if its owner device and activity have not changed. In this case a next TunerReservation request will update the same token with new values of { servicelocator, startTime, duration}.
The format of releasing a reservation is,

{
    "releaseTunerReservation" : {
         "requestId"        : [String] requestId,
         "device"           : [String] device,
         "reservationToken" : [String] reservationToken
    }
}

The fields are defined as follows:

• requestId : a GUID (Globally Unique Identifier) used to match requests with responses. For every request, the client supplies a requestId that it can use to match the corresponding response. For every notification, the sender supplies a requestId.
• device : the remote device making the request.
• reservationToken: the reservation to be released. After successful release, the token is no longer valid and cannot be used in future messages. It is clients responsibility to stop the associated activity first before releasing the tuner reservation with TRM.

Release Tuner Reservation Response Message

The general format of the response payload is:

{
      releaseTunerReservationResponse: {
          "requestId"         : [String] requestId,
          <ResponseStatus>
          "reservationToken"  : [String] reservationToken
          "released"          : [String] released
      }
}

The fields are defined as follows:

• reservationToken : the reservation released. After successful release, the token is no longer valid and cannot be used in future messages.
• Released : a string of "true" or "false", indicating if an valid token is successfully released. If the token is not valid, the ResponseStatus will carry "MALFORMED_REQUEST"