The SOP Class UID of the specified UPS instance will always be the UPS Push SOP Class UID, which might not match the UPS SOP Class negotiated with the SCU. See CC.3.1 for further details.
The SCP shall support the attribute changes to the UPS instance specified by the SCU in the N-SET request primitive as specified in Table CC.2.5-3.
The SCP shall refuse N-SET requests on an IN PROGRESS UPS and not modify the UPS if the N-SET request does not include the Transaction UID (0008,1195) attribute with the same value as currently recorded in the UPS instance.
The SCP shall refuse N-SET requests on a COMPLETED or CANCELED UPS.
The SCP shall merge the Specific Character Set (0008,0005) value provided by the SCU with the existing value in the UPS instance.
The SCP shall return, via the N-SET response primitive, the N-SET Response Status Code applicable to the associated request as specified in Section CC.2.6.4.
The SCP may itself modify any Attributes of a UPS instance independently of an N-SET request, e.g., if the SCP is performing the procedure step itself, if it has been determined that the performing SCU has been disabled, or if it is necessary to correct attribute values after completion of the procedure in order to carry out reconciliation of the data. A description of the coercions the SCP may perform shall be documented in the conformance statement of the SCP.
Bi-directional Authentication of machines/users/applications is possible at association time (see PS 3.7 and PS 3.15). PS 3.7 provides a “Refused: Not Authorized” error code. There are no specific requirements to perform authorization.