All UPS Instances shall be created with the value of SOP Class UID set to “1.2.840.10008.5.1.4.34.6.1” (i.e. that of the UPS Push SOP Class).
Note: UPS Instances are all based on the Unified Procedure Step IOD and are all created either internally by the SCP, or in response to an N-CREATE issued as part of the UPS Push SOP Class.
Once created, UPS instances may be operated on by DIMSE services from any of the four UPS SOP Classes defined in the Unified Worklist and Procedure Step Service Class.
During association negotiation, the Abstract Syntax UID shall be the implemented SOP Class as shown in the following list:
1.2.840.10008.5.1.4.34.6.1 (UPS Push SOP Class)
1.2.840.10008.5.1.4.34.6.2 (UPS Watch SOP Class)
1.2.840.10008.5.1.4.34.6.3 (UPS Pull SOP Class)
1.2.840.10008.5.1.4.34.6.4 (UPS Event SOP Class)
CC.3.1.1 DIMSE Implications for UPS (Informative)
A SOP Instance may be created with one SOP Class UID (UPS Push) and later DIMSE Services may refer to it over an association negotiated for a different SOP Class UID. Further details on this can be found in PS 3.7 Section 10.
For DIMSE-N Services, the Affected SOP Class UID (0000,0002) or Requested SOP Class UID (0000,0003), when present, will be the UID of the UPS Push SOP Class regardless of the negotiated Abstract Syntax UID. The SCU and SCP will not reject DIMSE-N messages on the basis of the Affected/Requested SOP Class UID being that of the UPS Push SOP Class, rather than one of the other three SOP Class UIDs as listed in the Abstract Syntax UID during association negotiation. The SCU and SCP may reject the DIMSE-N messages if the instance is not a UPS Push SOP Class Instance.
For DIMSE-C Services (C-FIND), the Affected SOP Class UID will always match the negotiated Abstract Syntax UID for the Presentation Context under which the request is made. This will be either UPS Watch or UPS Pull. Both of these SOP Classes represent the UPS Information Model described in CC.2.8.1.
For example, in a typical “Pull Workflow” message exchange, the C-FIND query from a “performing SCU” would use the UPS Pull SOP Class UID for both the negotiated Abstract Syntax UID and the Affected SOP Class UID (0000,0002), however the SOP Class UID (0008,0016) of the C-FIND responses themselves will be set to the UPS Push SOP Class UID by the SCP. All the subsequent N-ACTION, N-SET, and N-GET messages, would then use the UPS Pull SOP Class UID for the negotiated Abstract Syntax UID, and the UPS Push SOP Class UID for the Affected SOP Class UID (0000,0002).
The well-known UID for subscribing/unsubscribing to events for all UPS Instances managed by an SCP shall have the value “1.2.840.10008.5.1.4.34.5”.