CC.4 Conformance Requirements

Implementations providing conformance to any of the UPS SOP Classes (UPS Pull, UPS Push, UPS Watch and UPS Event) shall be conformant as described in the following sections and shall include within their Conformance Statement information as described below.

An implementation may conform to any of the UPS SOP Classes as an SCU or as an SCP. The Conformance Statement shall be in the format defined in Annex A of PS 3.2.

CC.4.1 SCU Conformance

An implementation, which is conformant to any of the UPS SOP Classes as an SCU, shall meet conformance requirements for the operations that it invokes.

CC.4.1.1 Operations

The SCU Conformance Statement shall be formatted as defined in Annex A of PS 3.2.

An implementation, that conforms to any of the UPS Push, UPS Pull or UPS Watch SOP Classes as an SCU, shall specify under which conditions it will request the modification of the value of the Procedure Step State (0074,1000) attribute to “IN PROGRESS”, “COMPLETED”, and ”CANCELED”.

An implementation that conforms to the UPS Pull or UPS Watch SOP Classes as an SCU shall state in its Conformance Statement

CC.4.2 SCP Conformance

An implementation which is conformant to any of the UPS SOP Classes as an SCP shall meet conformance requirements for the operations which it performs.

CC.4.2.1 Operations

The SCP Conformance Statement shall be formatted as defined in Annex A of PS 3.2.

The SCP Conformance Statement shall provide information on the behavior of the SCP at the following occurrences: