The N-SET-RQ Message contains fields as defined in Table 10.3-5. Each field shall conform to DICOM encoding and Value Representation as defined in PS 3.5. Fields are required as specified in the N-SET service definition unless otherwise noted in Table 10.3-5. Fields not specified in the N-SET service definition but present in Table 10.3-5 are required by the DIMSE-N protocol.
Table 10.3-5 N-SET-RQ MESSAGE FIELDS
|Message Field||Tag||VR||VM||Description of Field|
|Command Group Length||(0000,0000)||UL||1||The even number of bytes from the end of the value field to the beginning of the next group.|
|Requested SOP Class UID||(0000,0003)||UI||1||SOP Class UID of the SOP Instance for which Attribute values are to be modified.|
|Command Field||(0000,0100)||US||1||This field distinguishes the DIMSE-N operation conveyed by this Message. The value of this field shall be set to 0120H for the N-SET-RQ Message.|
|Message ID||(0000,0110)||US||1||Implementation-specific value which distinguishes this Message from other Messages.|
|Command Data Set Type||(0000,0800)||US||1||This field indicates that a Data Set is present in the Message. It shall be set to any value other than 0101H (Null).|
|Requested SOP Instance UID||(0000,1001)||UI||1||Contains the UID of the SOP Instance for which Attribute values are to be modified.|
|Modification List||(no tag)||⎯||⎯||This field is encoded as a Data Set. One Data Element is encoded for each Attribute and Attribute Value applicable to the operation.|
Note: Τhe permitted contents of Modification List, encoded as a series of Data Elements, are defined in the Information Object Definition (PS 3.3) and Service Class Specifications (PS 3.4).