lifecycle.v1

“end of” date

models with this exact “end of” date

mapped to its count

DeviceLifecycleSummaryKey is the key of

DeviceLifecycleSummary

software_eol is the software end of life of

a device

hardware_lifecycle_summary is the hardware lifecycle summary

of a device

device_id is the device ID

end_of_life of a HardwareLifecycleSummary

end_of_sale of a HardwareLifecycleSummary

end_of_tac_support of a HardwareLifecycleSummary

end_of_hardware_rma_requests of a HardwareLifecycleSummary

version of a SoftwareEOL

end_of_support of a SoftwareEOL

Key uniquely identifies a DeviceLifecycleSummary instance to retrieve.

This value must be populated.

Time indicates the time for which you are interested in the data.

If no time is given, the server will use the time at which it makes the request.

Value is the value requested.

This structure will be fully-populated as it exists in the datastore. If

optional fields were not given at creation, these fields will be empty or

set to default values.

Time carries the (UTC) timestamp of the last-modification of the

DeviceLifecycleSummary instance in this response.

PartialEqFilter provides a way to server-side filter a GetAll/Subscribe.

This requires all provided fields to be equal to the response.

While transparent to users, this field also allows services to optimize internal

subscriptions if filter(s) are sufficiently specific.

TimeRange allows limiting response data to within a specified time window.

If this field is populated, at least one of the two time fields are required.

For GetAll, the fields start and end can be used as follows:

* end: Returns the state of each DeviceLifecycleSummary at end.

* Each DeviceLifecycleSummary response is fully-specified (all fields set).

* start: Returns the state of each DeviceLifecycleSummary at start, followed by updates until now.

* Each DeviceLifecycleSummary response at start is fully-specified, but updates may be partial.

* start and end: Returns the state of each DeviceLifecycleSummary at start, followed by updates

until end.

* Each DeviceLifecycleSummary response at start is fully-specified, but updates until end may

be partial.

This field is not allowed in the Subscribe RPC.

Value is a value deemed relevant to the initiating request.

This structure will always have its key-field populated. Which other fields are

populated, and why, depends on the value of Operation and what triggered this notification.

Time holds the timestamp of this DeviceLifecycleSummary’s last modification.

Operation indicates how the DeviceLifecycleSummary value in this response should be considered.

Under non-subscribe requests, this value should always be INITIAL. In a subscription,

once all initial data is streamed and the client begins to receive modification updates,

you should not see INITIAL again.

Time holds the timestamp of the last item included in the metadata calculation.

Operation indicates how the value in this response should be considered.

Under non-subscribe requests, this value should always be INITIAL. In a subscription,

once all initial data is streamed and the client begins to receive modification updates,

you should not see INITIAL again.

Count is the number of items present under the conditions of the request.