10 DIMSE-N

10.1 Services

The following sections describe the DIMSE-N Services. The behavior of these services is also described in PS 3.4. The Affected SOP Class UID in the DIMSE-N command need not match the SOP Class UID in the Presentation Context negotiated for the association over which the DIMSE-N command has been sent. PS 3.4 specifies which combinations are valid.

10.1.1 N-EVENT-REPORT SERVICE

The N-EVENT-REPORT service is used by a DIMSE-service-user to report an event to a peer DIMSE-service-user. It is a confirmed service.

10.1.1.1 N-EVENT-REPORT parameters

Table 10.1-1 lists the parameters for this service.

Table 10.1-1 N-EVENT-REPORT PARAMETERS

DIMSE Parameter Name Req/Ind Rsp/Conf
Message ID M
Message ID Being Responded To M
Affected SOP Class UID M U(=)
Affected SOP Instance UID M U(=)
Event Type ID M C(=)
Event Information U
Event Reply C
Status M

10.1.1.1.1 Message ID

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: Τhe Message ID (0000,0110) is recommended to be unique within the scope of an Association, to support debug procedures.

10.1.1.1.2 Message ID being responded to

This parameter specifies the Message ID (0000,0110) of the notification request/indication to which this response/confirmation applies.

10.1.1.1.3 Affected SOP class UID

For the request/indication, this parameter specifies the SOP Class of the SOP Instance for the event. It may be included in the response/confirmation. If included in the response/confirmation, this parameter shall be equal to the value in the request/indication.

10.1.1.1.4 Affected SOP instance UID

For the request/indication, this parameter specifies the SOP Instance for the event. It may be included in the response/confirmation. If included in the response/confirmation, this parameter shall be equal to the value in the request/indication.

10.1.1.1.5 Event type ID

This parameter specifies the type of event being reported. It may be included in the success response/confirmation and shall be included if the Event Reply parameter is included.

Note: Service Class Specifications contained in PS 3.4 defines any application usage of the Event Type ID parameter.

10.1.1.1.6 Event information

This application-specific parameter contains information that the invoking DIMSE-service-user is able to supply about the event.

Note: Service Class Specifications contained in PS 3.4 defines any application usage of the Event Information parameter.

10.1.1.1.7 Event reply

This application-specific parameter contains the optional reply to the event report. It may only be included in the success response/confirmation.

Note: Service Class Specifications contained in PS 3.4 defines any application usage of the Event Reply parameter.

10.1.1.1.8 Status

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 argument value: the event information value specified was out of range or otherwise inappropriate.

⎯ invalid SOP Instance: the SOP Instance UID specified implied a violation of the UID construction rules.

⎯ mistyped argument: one of the parameters supplied has not been agreed for use on the Association between the DIMSE-service-users.

⎯ no such argument: the event information specified was not recognized.

⎯ no such event type: the event type specified was not recognized.

⎯ 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 notification.

⎯ unrecognized operation: the operation is not one of those agreed between the DIMSE-service-users.

10.1.1.2 N-EVENT-REPORT service procedures

The following N-EVENT-REPORT procedures apply:

a) The invoking DIMSE-service-user reports an event to the performing DIMSE-service-user by issuing an N-EVENT-REPORT request primitive to the DIMSE-service-provider.

b) The DIMSE-service-provider issues an N-EVENT-REPORT indication primitive to the performing DIMSE-service-user.

c) The performing DIMSE-service-user reports acceptance or rejection of the N-EVENT-REPORT request primitive by issuing an N-EVENT-REPORT response primitive to the DIMSE-service-provider.

d) The DIMSE-service-provider issues an N-EVENT-REPORT confirmation primitive to the invoking DIMSE-service-user, completing the N-EVENT-REPORT notification.

The performing DIMSE-service-user may return an N-EVENT-REPORT response primitive with the status of Failed or Refused before the entire N-EVENT-REPORT indication (Data Set) has been completely transmitted by the invoking DIMSE-service-user. A N-EVENT-REPORT response primitive with the status of Success or Warning shall not be returned until the entire N-EVENT-REPORT 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.

10.1.2 N-GET Service

The N-GET service is used by a DIMSE-service-user to retrieve Attribute values from a peer DIMSE-service-user. It is a confirmed service.

10.1.2.1 N-GET Parameters

Table 10.1-2 lists the parameters for this service.

Table 10.1-2 N-GET PARAMETERS

DIMSE Parameter Name Req/Ind Rsp/Conf
Message ID M
Message ID Being Responded To M
Requested SOP Class UID M
Requested SOP Instance UID M
Attribute Identifier List U
Affected SOP Class UID U
Affected SOP Instance UID U
Attribute List C
Status M

10.1.2.1.1 Message ID

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.

10.1.2.1.2 Message ID being responded to

This parameter specifies the Message ID (0000,0110) of the operation request/indication to which this response/confirmation applies.

10.1.2.1.3 Requested SOP class UID

This parameter specifies the SOP Class for which Attribute Values are to be retrieved.

10.1.2.1.4 Requested SOP instance UID

This parameter specifies the SOP Instance for which Attribute Values are to be retrieved.

10.1.2.1.5 Attribute identifier list

This parameter contains a set of Attribute identifiers for which the Attribute Values are to be returned by the performing DIMSE-service-user. If this parameter is omitted, all Attribute identifiers are assumed. The definitions of the Attributes are found in the specification of the Information Object Definition in PS 3.3.

10.1.2.1.6 Affected SOP class UID

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.

10.1.2.1.7 Affected SOP instance UID

This parameter specifies the SOP Instance for which Attribute Values are returned. 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.

10.1.2.1.8 Attribute list

This parameter contains the set of Attribute identifiers and values which are returned by the performing DIMSE-service-user. It shall be included in the success response/confirmation.

10.1.2.1.9 Status

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:

⎯ attribute list error: one or more Attribute Values were not read because the specified Attribute was not recognized. The Attribute Values that could be read are returned.

⎯ 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 SOP Instance: the SOP Instance UID specified implied a violation of the UID construction rules.

⎯ mistyped argument: one of the parameters supplied has not been agreed for use on the Association between the DIMSE-service-users.

⎯ 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.

10.1.2.2 N-GET service procedures

The following N-GET procedures apply;

a) The invoking DIMSE-service-user requests the performing DIMSE-service-user to retrieve Attribute Value(s) by issuing an N-GET request primitive to the DIMSE-service-provider.

b) The DIMSE-service-provider issues an N-GET indication primitive to the performing DIMSE-service-user.

c) If the operation can be performed, then the performing DIMSE-service-user retrieves the requested Attribute Value(s) and generates a response indicating acceptance of the N-GET request primitive by issuing an N-GET 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-GET request by issuing an N-GET response primitive with the appropriate error code to the DIMSE-service-provider.

e) The DIMSE-service-provider issues an N-GET confirmation primitive to the invoking DIMSE-service-user, completing the N-GET operation.

10.1.3 N-SET SERVICE

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.

10.1.3.1 N-SET parameters

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 M
Message ID Being Responded To M
Requested SOP Class UID M
Requested SOP Instance UID M
Modification List M
Attribute List U
Affected SOP Class UID U
Affected SOP Instance UID U
Status M

10.1.3.1.1 Message ID

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.

10.1.3.1.2 Message ID being responded to

This parameter specifies the Message ID (0000,0110) of the operation request/indication to which this response/confirmation applies.

10.1.3.1.3 Requested SOP class UID

This parameter specifies the SOP Class for which Attribute Values are to be modified.

10.1.3.1.4 Requested SOP instance UID

This parameter specifies the SOP Instance for which Attribute Values are to be modified.

10.1.3.1.5 Modification list

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.

10.1.3.1.6 Attribute list

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.

10.1.3.1.7 Affected SOP class UID

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.

10.1.3.1.8 Affected SOP instance UID

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.

10.1.3.1.9 Status

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.

10.1.3.2 N-SET service procedures

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.

10.1.4 N-ACTION SERVICE

The N-ACTION service is used by a DIMSE-service-user to request an action by a peer DIMSE-service-user. It is a confirmed service.

10.1.4.1 N-ACTION parameters

Table 10.1-4 lists the parameters for this service.

Table 10.1-4 N-ACTION PARAMETERS

DIMSE Parameter Name Req/Ind Rsp/Conf
Message ID M
Message ID Being Responded To M
Requested SOP Class UID M
Requested SOP Instance UID M
Action Type ID M C(=)
Action Information U
Affected SOP Class UID U
Affected SOP Instance UID U
Action Reply C
Status M

10.1.4.1.1 Message ID

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.

10.1.4.1.2 Message ID being responded to

This parameter specifies the Message ID (0000,0110) of the operation request/indication to which this response/confirmation applies.

10.1.4.1.3 Requested SOP class UID

This parameter specifies the SOP Class for which the action is to be performed.

10.1.4.1.4 Requested SOP instance UID

This parameter specifies the SOP Instance on which the action is to be performed.

10.1.4.1.5 Action type ID

This parameter specifies a particular action which is to be performed. It may be included in the success response/confirmation and shall be included if the action reply parameter is included.

Note: Service Class Specifications contained in PS 3.4 defines any application usage of the Action Type ID (0000,1008) parameter.

10.1.4.1.6 Action information

This parameter specifies extra application-specific information when necessary to further define the nature, variations, or operands of the action to be performed. The syntax and semantics of the parameter depend upon the action requested. It may only be included in the request/indication.

Note: Service Class Specifications contained in PS 3.4 defines any application usage of the Action Information parameter.

10.1.4.1.7 Affected SOP class UID

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.

10.1.4.1.8 Affected SOP instance UID

This parameter specifies the SOP Instance on which the action is to be performed. 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.

10.1.4.1.9 Action reply

This parameter contains the application-specific reply to the action. It may be included in the success response/confirmation.

Note: Service Class Specifications contained in PS 3.4 defines any application usage of the Action Reply parameter.

10.1.4.1.10 Status

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 type 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 argument value: the action information value specified was out of range or otherwise inappropriate.

⎯ invalid SOP Instance: the SOP Instance UID specified implied a violation of the UID construction rules.

⎯ mistyped argument: one of the parameters supplied has not been agreed for use on the Association between the DIMSE-service-users.

⎯ no such action: the action type specified was not supported.

⎯ no such argument: the action information specified was not supported.

⎯ 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.

10.1.4.2 N-ACTION service procedures

The following N-ACTION procedures apply:

a) The invoking DIMSE-service-user requests the performing DIMSE-service-user to perform an action on a managed SOP Instance by issuing an N-ACTION request primitive to the DIMSE-service-provider.

b) The DIMSE-service provider issues an N-ACTION indication primitive to the performing DIMSE-service-user.

c) If the operation can be performed, the performing DIMSE-service-user applies the action to the specified SOP Instance and generates a response indicating acceptance of the N-ACTION request primitive by issuing an N-ACTION response primitive to the DIMSE-service-provider. In this case the following procedure does not apply. The Action Reply may be included in a successful response.

d) If the operation cannot be performed, then the performing DIMSE-service-user rejects the N-ACTION request by issuing an N-ACTION response primitive with the appropriate error code to the DIMSE-service-provider.

e) The DIMSE-service-provider issues an N-ACTION confirmation primitive to the invoking DIMSE-service-user, completing the N-ACTION operation.

The performing DIMSE-service-user may return an N-ACTION response primitive with the status of Failed or Refused before the entire N-ACTION indication (Data Set) has been completely transmitted by the invoking DIMSE-service-user. A N-ACTION response primitive with the status of Success or Warning shall not be returned until the entire N-ACTION 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.

10.1.5 N-CREATE SERVICE

The N-CREATE service is used by a DIMSE-service-user to request a peer DIMSE-service-user to create a new managed SOP Instance, complete with its identification and the values of its associated Attributes, and simultaneously to register its identification. It is a confirmed service.

10.1.5.1 N-CREATE parameters

Table 10.1-5 lists the parameters for this service.

Table 10.1-5N-CREATE PARAMETERS

DIMSE Parameter Name Req/Ind Rsp/Conf
Message ID M
Message ID Being Responded To M
Affected SOP Class UID M U(=)
Affected SOP Instance UID U C
Attribute List U U
Status M

10.1.5.1.1 Message ID

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.

10.1.5.1.2 Message ID being responded to

This parameter specifies the Message ID (0000,0110) of the operation request/indication to which this response/confirmation applies.

10.1.5.1.3 Affected SOP class UID

For the request/indication, this parameter specifies the SOP Class of the new SOP Instance which is to be created by the performing DIMSE-service-user. The performing DIMSE-service-user assigns to the new SOP Instance, a set of Attribute Values as specified by the definition of its SOP Class. For the response/confirmation, this parameter specifies the SOP class of the SOP Instance which was created. It may be included in the response/confirmation. If included in the response/confirmation, this parameter shall be equal to the value in the request/indication.

10.1.5.1.4 Affected SOP instance UID

For the request/indication, this parameter specifies the SOP Instance which is used by the performing DIMSE-service-user. If the SOP Instance UID is not supplied by the invoking DIMSE-service-user, then the performing DIMSE-service-user assigns a value to this identification of instance. For the response/confirmation, this parameter may only be included in the success response/confirmation and shall be included if it is not supplied by the invoking DIMSE-service-user.

10.1.5.1.5 Attribute list

When this parameter is supplied by the invoking DIMSE-service-user, it contains a set of Attribute identifiers and values that the performing DIMSE-service-user is to assign to the new managed SOP Instance. When returned by the performing DIMSE-service-user, this parameter contains the complete list of all Attribute identifiers and values that were assigned to the new managed SOP Instance. It may be included in the success response/confirmation.

10.1.5.1.6 Status

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 type 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.

⎯ duplicate SOP Instance: the new managed SOP Instance Value supplied by the invoking DIMSE-service-user was already registered for a managed SOP Instance of the specified SOP Class.

⎯ invalid Attribute Value: the Attribute Value specified was out of range or otherwise inappropriate.

⎯ invalid SOP Instance: the SOP Instance UID specified implied a violation of the UID construction rules.

⎯ missing Attribute: a required Attribute was not supplied.

⎯ missing Attribute Value: a required Attribute Value was not supplied and a default value was not available.

⎯ mistyped argument: one of the parameters supplied has not been agreed for use on the Association between the DIMSE-service-users.

⎯ no such Attribute: the Tag for the specified Attribute was not recognized.

⎯ 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.

10.1.5.2 N-CREATE service procedures

The following N-CREATE procedures apply:

a) The invoking DIMSE-service-user requests the creation and registration of a new managed SOP Instance by issuing an N-CREATE request primitive to the DIMSE-service-provider.

b) The DIMSE-service provider issues an N-CREATE indication primitive to the performing DIMSE-service-user.

c) If the operation can be performed, the performing DIMSE-service-user creates and registers the new managed SOP Instance and generates a response indicating acceptance of the N-CREATE request primitive by issuing an N-CREATE 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-CREATE request by issuing an N-CREATE response primitive with the appropriate error code to the DIMSE-service-provider.

e) The DIMSE-service-provider issues an N-CREATE confirmation primitive to the invoking DIMSE-service-user, completing the N-CREATE operation.

The performing DIMSE-service-user may return an N-CREATE response primitive with the status of Failed or Refused before the entire N-CREATE indication (Data Set) has been completely transmitted by the invoking DIMSE-service-user. A N-CREATE response primitive with the status of Success or Warning shall not be returned until the entire N-CREATE 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.

10.1.6 N-DELETE SERVICE

The N-DELETE service is used by an invoking DIMSE-service-user to request a peer DIMSE-service-user to delete a managed SOP Instance and to de-register its identification. It is a confirmed service.

10.1.6.1 N-DELETE parameters

Table 10.1-6 lists the parameters for this service.

Table 10.1-6 N-DELETE PARAMETERS

DIMSE Parameter Name Req/Ind Rsp/Conf
Message ID M
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
Status M

10.1.6.1.1 Message ID

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.

10.1.6.1.2 Message ID being responded to

This parameter specifies the Message ID (0000,0110) of the operation request/indication to which this response/confirmation applies.

10.1.6.1.3 Requested SOP class UID

This parameter specifies the SOP Class which is to be deleted.

10.1.6.1.4 Requested SOP instance UID

This parameter specifies the SOP Instance which is to be deleted.

10.1.6.1.5 Affected SOP class UID

This parameter may be included in the response/confirmation. If included in the response/confirmation, this parameter shall be equal to the parameter value used in the request/indication.

10.1.6.1.6 Affected SOP instance UID

This parameter specifies the SOP Instance which was deleted. 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.

10.1.6.1.7 Status

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 SOP Instance: the SOP Instance UID specified implied a violation of the UID construction rules

⎯ mistyped argument: one of the parameters supplied has not been agreed for use on the Association between the DIMSE-service-users

⎯ 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

10.1.6.2 N-DELETE service procedures

The following N-DELETE procedures apply:

a) The invoking DIMSE-service-user requests the performing DIMSE-service-user to delete a managed SOP Instance by issuing an N-DELETE request primitive to the DIMSE-service-provider.

b) The DIMSE-service provider issues an N-DELETE indication primitive to the performing DIMSE-service-user.

c) If the operation can be performed, the performing DIMSE-service-user deletes the specified managed SOP Instance and generates a response indicating acceptance of the N-DELETE request primitive by issuing an N-DELETE 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-DELETE request by issuing an N-DELETE response primitive with the appropriate error code to the DIMSE-service-provider.

e) The DIMSE-service-provider issues an N-DELETE confirmation primitive to the invoking DIMSE-service-user, completing the N-DELETE operation.

10.2 Sequencing

10.2.1 TYPES OF SERVICES

All operation and notifications shall be confirmed services.

10.2.2 USAGE RESTRICTIONS

These services may only be invoked within the context of an established Association.

10.2.3 DISRUPTED PROCEDURES

These services do not disrupt any other service procedure.

10.2.4 DISRUPTING PROCEDURES

These services are disrupted by the A-ABORT service procedure.

10.3 Protocol

This section specifies the protocol necessary to perform the set of DIMSE-N operations and notifications. The Value Representations (VR) specified in the following tables shall be encoded as defined in PS 3.5.

10.3.1 N-EVENT-REPORT PROTOCOL

The information necessary for the N-EVENT-REPORT request and indication DIMSE-N primitives are conveyed in the N-EVENT-REPORT-RQ Message. The information necessary for the N-EVENT-REPORT response and confirmation DIMSE-N primitives are conveyed in the N-EVENT-REPORT-RSP Message.

10.3.1.1 N-EVENT-REPORT-RQ

The N-EVENT-REPORT-RQ Message contains fields as defined in Table 10.3-1. Each field shall conform to DICOM encoding and Value Representation as defined in PS 3.5. Fields are required as specified in the N-EVENT-REPORT service definition unless otherwise noted in Table 10.3-1. Fields not specified in the N-EVENT-REPORT service definition but present in Table 10.3-1 are required by the DIMSE-N protocol.

Table 10.3-1N-EVENT-REPORT-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.
Affected SOP Class UID (0000,0002) UI 1 SOP Class UID of the SOP Instance for which this event occurred.
Command Field (0000,0100) US 1 This field distinguishes the DIMSE-N notification conveyed by this Message. The value of this field shall be set to 0100H for the N-EVENT-REPORT-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 if a Data Set is present in the Message. This field shall be set to the value of 0101H if no Data Set is present; any other value indicates a Data Set is included in the Message.
Affected SOP Instance UID (0000,1000) UI 1 Contains the UID of the SOP Instance for which this event occurred.
Event Type ID (0000,1002) US 1 Values for this field are application-specific.
Event Information (no tag) Application-specific Data Set containing additional information related to the operation.

Notes: 1. Service Class Specifications contained in PS 3.4 defines the values needed for the Event Type ID parameter.

2. Service Class Specifications contained in PS 3.4 defines the Data Set needed for the Event Information parameter.

10.3.1.2 N-EVENT-REPORT-RSP

The N-EVENT-REPORT-RSP Message contains fields as defined in Table 10.3-2 and Annex C. Each field shall conform to DICOM encoding and Value Representation as defined in PS 3.5. Fields are required as specified in the N-EVENT-REPORT service definition unless otherwise noted in Table 10.3-2. Fields not specified in the N-EVENT-REPORT service definition but present in Table 10.3-2 are required by the DIMSE-N protocol.

Table 10.3-2 N-EVENT-REPORT-RSP 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.
Affected SOP Class UID (0000,0002) UI 1 SOP Class UID of the SOP Instance for which this event occurred.
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 8100H for the N-EVENT-REPORT-RSP Message.
Message ID Being Responded To (0000,0120) US 1 Shall be set to the value of the Message ID (0000,0110) field used in associated N-EVENT-REPORT-RQ Message.
Command Data Set Type (0000,0800) US 1 This field indicates if a Data Set is present in the Message. This field shall be set to the value of 0101H if no Data Set is present; any other value indicates a Data Set is included in the Message.
Status (0000,0900) US 1 The value of this field depends upon the status type. Annex C defines the encoding of the status types defined in the service definition.
Affected SOP Instance UID (0000,1000) UI 1 Contains the UID of the SOP Instance for which this event occurred.
Event Type ID (0000,1002) US 1 Values for this field are application-specific.
Event Reply (no tag) Application-specific Data Set containing additional information related to the operation.

Notes: 1. Service Class Specifications contained in PS 3.4 defines the values needed for the Event Type ID parameter.

2. Service Class Specifications contained in PS 3.4 defines the Data Set needed for the Event Reply parameter related to each defined Event Type ID.

10.3.1.3 N-EVENT-REPORT protocol procedures

The N-EVENT-REPORT reporting procedures are initiated by the invoking DIMSE-service-user issuing an N-EVENT-REPORT request primitive. On receipt of the N-EVENT-REPORT request primitive the DIMSE-N protocol machine shall:

⎯ construct a Message conveying the N-EVENT-REPORT-RQ

⎯ send the Message using the P-DATA request service (See 8.1)

On receipt of a Message conveying an N-EVENT-REPORT-RQ the DIMSE-N protocol machine shall issue an N-EVENT-REPORT indication primitive to the performing DIMSE-service-user.

On receipt of the N-EVENT-REPORT response primitive issued by the performing DIMSE-service-user , the DIMSE-N protocol machine shall:

⎯ construct a Message conveying the N-EVENT-REPORT-RSP

⎯ send the Message using the P-DATA request service (See Section 8.1)

On receipt of a Message conveying an N-EVENT-REPORT-RSP the DIMSE-N protocol machine shall issue an N-EVENT-REPORT confirmation primitive to the invoking DIMSE-service-user, thus completing the notification procedure.

The performing DIMSE-service-user may return an N-EVENT-REPORT-RSP with the status of Failed or Refused before the complete N-EVENT-REPORT-RQ request Message has been completely transmitted by the invoking DIMSE-service-user (this is called an early failed response). Upon receipt of this Failed or Refused N-EVENT-REPORT-RSP the invoking DIMSE-service-user may terminate the Message before it is completely sent (i.e. set the Last Fragment bit to 1 in a Data PDV for this Message, see Annex F). Following this, it may invoke another operation or notification. It is a protocol violation for an invoking DIMSE-service-user to set the Last Fragment bit to 1 before an N-EVENT-REPORT-RQ Message has been completely transmitted if it has not received a Failed or Refused N-EVENT-REPORT-RSP to that request.

Note: When an Association is operating in asynchronous mode, it is possible for an invoking DIMSE-service-user to transmit several Messages before a response. Therefore, while sending a Message it may receive a response to a previously transmitted Message. In this case this response is not an early failed response because the related Message has already been sent.

10.3.2 N-GET PROTOCOL

The information necessary for the N-GET request and indication DIMSE-N primitives are conveyed in the N-GET-RQ Message. The information necessary for the N-GET response and confirmation DIMSE-N primitives are conveyed in the N-GET-RSP Message.

10.3.2.1 N-GET-RQ

The N-GET-RQ Message contains fields as defined in Table 10.3-3. Each field shall conform to DICOM encoding and Value Representation as defined in PS 3.5. Fields are required as specified in the N-GET service definition unless otherwise noted in Table 10.3-3. Fields not specified in the N-GET service definition but present in Table 10.3-3 are required by the DIMSE-N protocol.

Table 10.3-3 N-GET-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 retrieved.
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 0110H for the N-GET-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 no Data Set shall be present in the Message. This field shall be set to the value of 0101H).
Requested SOP Instance UID (0000,1001) UI 1 Contains the UID of the SOP Instance for which Attribute Values are to be retrieved.
Attribute Identifier List (0000,1005) AT 1-n This field contains an Attribute Tag for each of the n Attributes applicable to the N-GET operation.

10.3.2.2 N-GET-RSP

The N-GET-RSP Message contains fields as defined in Table 10.3-4 and Annex C. Each field shall conform to DICOM encoding and Value Representation as defined in PS 3.5. Fields are required as specified in the N-GET service definition unless otherwise noted in Table 10.3-4. Fields not specified in the N-GET service definition but present in Table 10.3-4 are required by the DIMSE-N protocol.

Table 10.3-4 N-GET-RSP 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.
Affected SOP Class UID (0000,0002) UI 1 SOP Class UID of the SOP Instance for which Attribute Values are returned.
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 8110H for the N-GET-RSP Message.
Message ID Being Responded To (0000,0120) US 1 Shall be set to the value of the Message ID (0000,0110) field used in associated N-GET-RQ Message.
Command Data Set Type (0000,0800) US 1 This field indicates if a Data Set is present in the Message. This field shall be set to the value of 0101H if no Data Set is present; any other value indicates a Data Set is included in the Message.
Status (0000,0900) US 1 The value of this field depends upon the status type. Annex C defines the encoding of the status types defined in the service definition.
Affected SOP Instance UID (0000,1000) UI 1 Contains the UID of the SOP Instance for which Attribute Values are returned.
Attribute List (no tag) T his field is encoded as a Data Set. One Data Element is encoded for each Attribute Value returned.

Note: The permitted contents of Attribute 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).

10.3.2.3 N-GET protocol procedures

The N-GET procedures are initiated by the invoking DIMSE-service-user issuing an N-GET request primitive. On receipt of the N-GET request primitive the DIMSE-N protocol machine shall:

⎯ construct a Message conveying the N-GET-RQ

⎯ send the Message using the P-DATA request service (See 8.1)

On receipt of a Message conveying an N-GET-RQ the DIMSE-N protocol machine shall issue an N-GET indication primitive to the performing DIMSE-service-user.

On receipt of the N-GET response primitive, issued by the performing DIMSE-service-user, the DIMSE-N protocol machine shall:

⎯ construct a Message conveying the N-GET-RSP

⎯ send the Message using the P-DATA request service (See 8.1)

On receipt of a Message conveying an N-GET-RSP the DIMSE-N protocol machine shall issue an N-GET confirmation primitive to the invoking DIMSE-service-user, thus completing the N-GET procedure.

10.3.3 N-SET PROTOCOL

The information necessary for the N-SET request and indication DIMSE-N primitives are conveyed in the N-SET-RQ Message. The information necessary for the N-SET response and confirmation DIMSE-N primitives are conveyed in the N-SET-RSP Message. Fields not specified in the N-SET service definition but present in Table 10.3-3 are required by the DIMSE-N protocol.

10.3.3.1 N-SET-RQ

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).

10.3.3.2 N-SET-RSP

The N-SET-RSP Message contains all fields as defined in Table 10.3-6 and in Annex C. 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. Fields not specified in the N-SET service definition but present in Table 10.3-6 are required by the DIMSE-N protocol.

Table 10.3-6 N-SET-RSP 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.
Affected SOP Class UID (0000,0002) UI 1 SOP Class UID of the SOP Instance for which Attribute Values were 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 8120H for the N-SET-RSP Message.
Message ID Being Responded To (0000,0120) US 1 Shall be set to the value of the Message ID (0000,0110) field used in associated N-SET-RQ Message.
Command Data Set Type (0000,0800) US 1 This field indicates if a Data Set is present in the Message. This field shall be set to the value of 0101H if no Data Set is present; any other value indicates a Data Set is included in the Message.
Status (0000,0900) US 1 The value of this field depends upon the status type. Annex C defines the encoding of the status types defined in the service definition.
Affected SOP Instance UID (0000,1000) UI 1 Contains the UID of the SOP Instance for which Attribute Values were modified.
Attribute 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: The permitted contents of Attribute 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).

10.3.3.3 N-SET protocol procedures

The N-SET procedures are initiated by the invoking DIMSE-service-user issuing an N-SET request primitive. On receipt of the N-SET request primitive the DIMSE-N protocol machine shall:

⎯ construct a Message conveying the N-SET-RQ

⎯ send the Message using the P-DATA request service (See 8.1)

On receipt of a Message conveying an N-SET-RQ the DIMSE-N protocol machine shall issue an N-SET indication primitive to the performing DIMSE-service-user.

On receipt of the N-SET response primitive, issued by the performing DIMSE-service-user, the DIMSE-N protocol machine shall:

⎯ construct a Message conveying the N-SET-RSP

⎯ send the Message using the P-DATA request service (See 8.1)

On receipt of a Message conveying an N-SET-RSP the DIMSE-N protocol machine shall issue an N-SET confirmation primitive to the invoking DIMSE-service-user, thus completing the N-SET procedure.

The performing DIMSE-service-user may return an N-SET-RSP with the status of Failed or Refused before the complete N-SET-RQ request Message has been completely transmitted by the invoking DIMSE-service-user (this is called an early failed response). Upon receipt of this Failed or Refused N-SET-RSP the invoking DIMSE-service-user may terminate the Message before it is completely sent (i.e. set the Last Fragment bit to 1 in a Data PDV for this Message, see Annex F). Following this, it may invoke another operation or notification. It is a protocol violation for an invoking DIMSE-service-user to set the Last Fragment bit to 1 before an N-SET-RQ Message has been completely transmitted if it has not received a Failed or Refused N-SET-RSP to that request.

Note: When an Association is operating in asynchronous mode, it is possible for an invoking DIMSE-service-user to transmit several Messages before a response. Therefore, while sending a Message it may receive a response to a previously transmitted Message. In this case this response is not an early failed response because the related Message has already been sent.

10.3.4 N-ACTION PROTOCOL

The information necessary for the N-ACTION request and indication DIMSE-N primitives are conveyed in the N-ACTION-RQ Message. The information necessary for the N-ACTION response and confirmation DIMSE-N primitives are conveyed in the N-ACTION-RSP Message.

10.3.4.1 N-ACTION-RQ

The N-ACTION-RQ Message contains fields as defined in Table 10.3-7. Each field shall conform to DICOM encoding and Value Representation as defined in PS 3.5. Fields are required as specified in the N-ACTION service definition unless otherwise noted in Table 10.3-7. Fields not specified in the N-ACTION service definition but present in Table 10.3-7 are required by the DIMSE-N protocol.

Table 10.3-7N-ACTION-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 the action is to be performed.
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 0130H for the N-ACTION-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 if a Data Set is present in the Message. This field shall be set to the value of 0101H if no Data Set is present; any other value indicates a Data Set is included in the Message.
Requested SOP Instance UID (0000,1001) UI 1 Contains the UID of the SOP Instance for which the action is to be performed.
Action Type ID (0000,1008) US 1 Values for this field are application-specific.
Action Information (no tag) Application-specific Data Set containing additional information related to the operation.

Notes: 1. Service Class Specifications contained in PS 3.4 define the values needed for the Action Type ID (0000,1008) parameter.

2. Service Class Specifications contained in PS 3.4 define the Data Set needed for the Action Information parameter.

10.3.4.2 N-ACTION-RSP

The N-ACTION-RSP Message contains fields as defined in Table 10.3-8 and Annex C. Each field shall conform to DICOM encoding and Value Representation as defined in PS 3.5. Fields are required as specified in the N-ACTION service definition unless otherwise noted in Table 10.3-8. Fields not specified in the N-ACTION service definition but present in Table 10.3-8 are required by the DIMSE-N protocol.

Table 10.3-8N-ACTION-RSP 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.
Affected SOP Class UID (0000,0002) UI 1 SOP Class UID of the SOP Instance for which the action was performed.
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 8130H for the N-ACTION-RSP Message.
Message ID Being Responded To (0000,0120) US 1 Shall be set to the value of the Message ID (0000,0110) field used in associated N-ACTION-RQ Message.
Command Data Set Type (0000,0800) US 1 This field indicates if a Data Set is present in the Message. This field shall be set to the value of 0101H if no Data Set is present; any other value indicates a Data Set is included in the Message.
Status (0000,0900) US 1 The value of this field depends upon the status type. Annex C defines the encoding of the status types defined in the service definition.
Affected SOP Instance UID (0000,1000) UI 1 Contains the UID of the SOP Instance for which the action was performed.
Action Type ID (0000,1008) US 1 Values for this field are application-specific.
Action Reply (no tag) Application-specific Data Set containing additional information related to the operation.

Notes: 1. Service Class Specifications contained in PS 3.4 define the values needed for the Action Type ID (0000,1008) parameter.

2. Service Class Specifications contained in PS 3.4 define the Data Set needed for the Action Reply parameter related to each defined Action Type ID.

3. Service Class Specifications contained in PS 3.4 define the encoding of the Action Reply parameter.

10.3.4.3 N-ACTION protocol procedures

The N-ACTION procedures are initiated by the invoking DIMSE-service-user issuing an N-ACTION request primitive. On receipt of the N-ACTION request primitive the DIMSE-N protocol machine shall:

⎯ construct a Message conveying the N-ACTION-RQ

  1. send the Message using the P-DATA request service (See 8.1)

On receipt of a Message conveying an N-ACTION-RQ the DIMSE-N protocol machine shall issue an N-ACTION indication primitive to the performing DIMSE-service-user.

On receipt of the N-ACTION response primitive, issued by the performing DIMSE-service-user, the DIMSE-N protocol machine shall:

⎯ construct a Message conveying the N-ACTION-RSP

⎯ send the Message using the P-DATA request service (See 8.1)

On receipt of a Message conveying an N-ACTION-RSP the DIMSE-N protocol machine shall issue an N-ACTION confirmation primitive to the invoking DIMSE-service-user, thus completing the N-ACTION procedure.

The performing DIMSE-service-user may return an N-ACTION-RSP with the status of Failed or Refused before the complete N-ACTION-RQ request Message has been completely transmitted by the invoking DIMSE-service-user (this is called an early failed response). Upon receipt of this Failed or Refused N-ACTION-RSP the invoking DIMSE-service-user may terminate the Message before it is completely sent (i.e. set the Last Fragment bit to 1 in a Data PDV for this Message, see Annex F). Following this, it may invoke another operation or notification. It is a protocol violation for an invoking DIMSE-service-user to set the Last Fragment bit to 1 before an N-ACTION-RQ Message has been completely transmitted if it has not received a Failed or Refused N-ACTION-RSP to that request.

Note: When an Association is operating in asynchronous mode, it is possible for an invoking DIMSE-service-user to transmit several Messages before a response. Therefore, while sending a Message it may receive a response to a previously transmitted Message. In this case this response is not an early failed response because the related Message has already been sent.

10.3.5 N-CREATE PROTOCOL

The information necessary for the N-CREATE request and indication DIMSE-N primitives are conveyed in the N-CREATE-RQ Message. The information necessary for the N-CREATE response and confirmation DIMSE-N primitives are conveyed in the N-CREATE-RSP Message.

10.3.5.1 N-CREATE-RQ

The N-CREATE-RQ Message contains fields as defined in Table 10.3-9. Each field shall conform to DICOM encoding and Value Representation as defined in PS 3.5. Fields are required as specified in the N-CREATE service definition unless otherwise noted in Table 10.3-9. Fields not specified in the N-CREATE service definition but present in Table 10.3-9 are required by the DIMSE-N protocol.

Table 10.3-9N-CREATE-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.
Affected SOP Class UID (0000,0002) UI 1 SOP Class UID of the SOP Instance to be created.
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 0140H for the N-CREATE-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 if a Data Set is present in the Message. This field shall be set to the value of 0101H if no Data Set is present; any other value indicates a Data Set is included in the Message.
Affected SOP Instance UID (0000,1000) UI 1 Contains the UID of the SOP Instance to be created.
Attribute 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: The permitted contents of Attribute 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).

10.3.5.2 N-CREATE-RSP

The N-CREATE-RSP Message contains fields as defined in Table 10.3-10 and Annex C. Each field shall conform to DICOM encoding and Value Representation as defined in PS 3.5. Fields are required as specified in the N-CREATE service definition unless otherwise noted in Table10.3-10. Fields not specified in the N-CREATE service definition but present in Table 10.3-10 are required by the DIMSE-N protocol.

Table 10.3-10N-CREATE-RSP 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.
Affected SOP Class UID (0000,0002) UI 1 SOP Class UID of the SOP Instance which was created.
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 8140H for the N-CREATE-RSP Message.
Message ID Being Responded To (0000,0120) US 1 Shall be set to the value of the Message ID (0000,0110) field used in associated N-CREATE-RQ Message.
Command Data Set Type (0000,0800) US 1 This field indicates if a Data Set is present in the Message. This field shall be set to the value of 0101H if no Data Set is present; any other value indicates a Data Set is included in the Message.
Status (0000,0900) US 1 The value of this field depends upon the status type. Annex C defines the encoding of the status types defined in the service definition.
Affected SOP Instance UID (0000,1000) UI 1 Contains the UID of the SOP Instance which was created.
Attribute 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: The permitted contents of Attribute 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).

10.3.5.3 N-CREATE protocol procedures

The N-CREATE procedures are initiated by the invoking DIMSE-service-user issuing an N-CREATE request primitive. On receipt of the N-CREATE request primitive the DIMSE-N protocol machine shall:

⎯ construct a Message conveying the N-CREATE-RQ

⎯ send the Message using the P-DATA request service (See 8.1)

On receipt of a Message conveying an N-CREATE-RQ the DIMSE-N protocol machine shall issue an N-CREATE indication primitive to the performing DIMSE-service-user.

On receipt of the N-CREATE response primitive, issued by the performing DIMSE-service-user, the DIMSE-N protocol machine shall:

⎯ construct a Message conveying the N-CREATE-RSP

⎯ send the Message using the P-DATA request service (See 8.1)

On receipt of a Message conveying an N-CREATE-RSP the DIMSE-N protocol machine shall issue an N-CREATE confirmation primitive to the invoking DIMSE-service-user, thus completing the N-CREATE procedure.

The performing DIMSE-service-user may return an N-CREATE-RSP with the status of Failed or Refused before the complete N-CREATE-RQ request Message has been completely transmitted by the invoking DIMSE-service-user (this is called an early failed response). Upon receipt of this Failed or Refused N-CREATE-RSP the invoking DIMSE-service-user may terminate the Message before it is completely sent (i.e. set the Last Fragment bit to 1 in a Data PDV for this Message, see Annex F). Following this, it may invoke another operation or notification. It is a protocol violation for an invoking DIMSE-service-user to set the Last Fragment bit to 1 before an N-CREATE-RQ Message has been completely transmitted if it has not received a Failed or Refused N-CREATE-RSP to that request.

Note: When an Association is operating in asynchronous mode, it is possible for an invoking DIMSE-service-user to transmit several Messages before a response. Therefore, while sending a Message it may receive a response to a previously transmitted Message. In this case this response is not an early failed response because the related Message has already been sent.

10.3.6 N-DELETE PROTOCOL

The information necessary for the N-DELETE request and indication DIMSE-N primitives are conveyed in the N-DELETE-RQ Message. The information necessary for the N-DELETE response and confirmation DIMSE-N primitives are conveyed in the N-DELETE-RSP Message.

10.3.6.1 N-DELETE-RQ

The N-DELETE-RQ Message contains fields as defined in Table 10.3-11. Each field shall conform to DICOM encoding and Value Representation as defined in PS 3.5. Fields are required as specified in the N-DELETE service definition unless otherwise noted in Table 10.3-11. Fields not specified in the N-DELETE service definition but present in Table 10.3-11 are required by the DIMSE-N protocol.

Table 10.3-11 N-DELETE-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 to be deleted.
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 0150H for the N-DELETE-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 no Data Set is present in the Message. It shall be set to the value of 0101H.
Requested SOP Instance UID (0000,1001) UI 1 Contains the UID of the SOP Instance to be deleted.

10.3.6.2 N-DELETE-RSP

The N-DELETE-RSP Message contains fields as defined in Table 10.3-12 and Annex C. Each field shall conform to DICOM encoding and Value Representation as defined in PS 3.5. Fields are required as specified in the N-DELETE service definition unless otherwise noted in Table 10.3-12. Fields not specified in the N-DELETE service definition but present in Table 10.3-12 are required by the DIMSE-N protocol.

Table10.3-12 N-DELETE-RSP 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.
Affected SOP Class UID (0000,0002) UI 1 SOP Class UID of the SOP Instance which was deleted.
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 8150H for the N-DELETE-RSP Message.
Message ID Being Responded To (0000,0120) US 1 Shall be set to the value of the Message ID (0000,0110) field used in associated N-DELETE-RQ Message.
Command Data Set Type (0000,0800) US 1 This field indicates that no Data Set is present in the Message. This field shall be set to the value of 0101H).
Status (0000,0900) US 1 The value of this field depends upon the status type. Annex C defines the encoding of the status types defined in the service definition.
Affected SOP Instance UID (0000,1000) UI 1 Contains the UID of the SOP Instance which was deleted.

10.3.6.3 N-DELETE protocol procedures

The N-DELETE procedures are initiated by the invoking DIMSE-service-user issuing an N-DELETE request primitive. On receipt of the N-DELETE request primitive the DIMSE-N protocol machine shall:

⎯ construct a Message conveying the N-DELETE-RQ

⎯ end the Message using the P-DATA request service (See 8.1)

On receipt of a Message conveying an N-DELETE-RQ the DIMSE-N protocol machine shall issue an N-DELETE indication primitive to the performing DIMSE-service-user.

On receipt of the N-DELETE response primitive, issued by the performing DIMSE-service-user, the DIMSE-N protocol machine shall:

⎯ construct a Message conveying the N-DELETE-RSP

⎯ send the Message using the P-DATA request service (See 8.1)

On receipt of a Message conveying an N-DELETE-RSP the DIMSE-N protocol machine shall issue an N-DELETE confirmation primitive to the invoking DIMSE-service-user, thus completing the N-DELETE procedure.