The N-SET service is used by a DIMSE-service-user to request the modification of Attribute Values from a peer DIMSE-service-user. It is a confirmed service.
Table 10.1-3 lists the parameters for this service.
Table 10.1-3 N-SET PARAMETERS
|DIMSE Parameter Name||Req/Ind||Rsp/Conf|
|Message ID Being Responded To||⎯||M|
|Requested SOP Class UID||M||⎯|
|Requested SOP Instance UID||M||⎯|
|Affected SOP Class UID||⎯||U|
|Affected SOP Instance UID||⎯||U|
This parameter identifies the operation. It is used to distinguish this operation from other notifications or operations that the DIMSE-service-provider may have in progress. No two identical values for the Message ID (0000,0110) shall be used for outstanding operations or notifications.
Note: The Message ID (0000,0110) is recommended to be unique within the scope of an Association, to support debug procedures.
This parameter specifies the Message ID (0000,0110) of the operation request/indication to which this response/confirmation applies.
This parameter specifies the SOP Class for which Attribute Values are to be modified.
This parameter specifies the SOP Instance for which Attribute Values are to be modified.
This parameter contains the set of Attribute identifiers and values which are to be used by the performing DIMSE-service-user to replace the current values of the Attributes specified.
This parameter contains the set of Attribute identifiers and values which were used by the performing DIMSE-service-user to replace the values of the Attributes specified. It may be included in the success response/confirmation.
This parameter may be included in the response/confirmation. If included in the response/confirmation, this parameter shall be equal to the Requested SOP Class UID parameter value used in the request/indication.
This parameter specifies the SOP Instance for which Attribute Values were modified. It may be included in any response/confirmation and when included shall be equal to the Requested SOP Instance UID (0000,1001) parameter value used in the invocation.
This parameter contains the error or success notification for the operation. It shall be included by the performing DIMSE-service-user in any response/confirmation. The following types of status may occur:
⎯ class-instance conflict: the specified SOP Instance is not a member of the specified SOP Class.
⎯ duplicate invocation: the Message ID (0000,0110) specified is allocated to another notification or operation.
⎯ invalid Attribute Value: the Attribute Value specified was out of range or otherwise inappropriate. The Attribute Values that could be modified were modified.
⎯ mistyped argument: one of the parameters supplied has not been agreed for use on the Association between the DIMSE-service-users.
⎯ invalid SOP Instance: the SOP Instance UID specified implied a violation of the UID construction rules.
⎯ missing Attribute Value: a required Attribute Value was not supplied.
⎯ no such Attribute: the Tag for the specified Attribute was not recognized. The Attribute Values that could be modified were modified.
⎯ no such SOP class: the SOP Class was not recognized.
⎯ no such SOP Instance: the SOP Instance was not recognized.
⎯ processing failure: a general failure in processing the operation was encountered.
⎯ resource limitation: the operation was not performed due to resource limitation.
⎯ success: successful operation.
⎯ unrecognized operation: the operation is not one of those agreed between the DIMSE-service-users.
The following N-SET procedures apply:
a) The invoking DIMSE-service-user requests the performing DIMSE-service-user to modify Attribute Value(s) by issuing an N-SET request primitive to the DIMSE-service-provider.
b) The DIMSE-service provider issues an N-SET indication primitive to the performing DIMSE-service-user.
c) If the operation can be performed, then the performing DIMSE-service-user modifies the requested Attribute Value(s) and generates a response indicating acceptance of the N-SET request primitive by issuing an N-SET response primitive to the DIMSE-service-provider. In this case the following procedure does not apply.
d) If the operation cannot be performed, then the performing DIMSE-service-user rejects the N-SET request by issuing an N-SET response primitive with the appropriate error code to the DIMSE-service-provider.
e) The DIMSE-service-provider issues an N-SET confirmation primitive to the invoking DIMSE-service-user, completing the N-SET operation.
The performing DIMSE-service-user may return an N-SET response primitive with the status of Failed or Refused before the entire N-SET indication (Data Set) has been completely transmitted by the invoking DIMSE-service-user. A N-SET response primitive with the status of Success or Warning shall not be returned until the entire N-SET indication has been received by the performing DIMSE-service-user.
Note: Such an occurrence of a "Failed" response is often called an early failed response.