9 DIMSE-C
Prev |  | Next

# 9 DIMSE-C

## 9.1 Services

### 9.1.1 C-STORE Service

The C-STORE service is used by a DIMSE-service-user to store a composite SOP Instance on a peer DIMSE-service-user. It is a confirmed service.

#### 9.1.1.1 C-STORE Parameters

Table 9.1-1 lists the parameters of this service.

Table 9.1-1. C-STORE Parameters

DIMSE-C Parameter Name | Req/Ind | Rsp/Conf
Message ID | M | U
Message ID Being Responded To | - | M
Affected SOP Class UID | M | U(=)
Affected SOP Instance UID | M | U(=)
Priority | M | -
Move Originator Application Entity Title | U | -
Move Originator Message ID | U | -
Data Set | M | -
Status | - | M

##### 9.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

1. Inclusion of this parameter in the confirmation was permitted in previous versions of this Standard but this mode of use is now retired. This parameter may be included in the confirmation but in such a case the invoking DIMSE-service-user should not attach any semantic significance to this parameter.

2. The Message ID (0000,0110) is recommended to be unique within the scope of an Association, to support debug procedures.

##### 9.1.1.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.

##### 9.1.1.1.3 Affected SOP Class UID

For the request/indication, this parameter specifies the SOP Class for the storage. 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.

##### 9.1.1.1.4 Affected SOP Instance UID

For the request/indication, this parameter specifies the SOP Instance to be stored. 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.

##### 9.1.1.1.5 Priority

This parameter specifies the priority of the C-STORE operation. It shall be one of LOW, MEDIUM, or HIGH.

##### 9.1.1.1.6 Move Originator Application Entity Title

This parameter specifies the DICOM AE Title of the DICOM AE that invoked the C-MOVE operation from which this C-STORE sub-operation is being performed.

##### 9.1.1.1.7 Move Originator Message ID

This parameter specifies the Message ID (0000,0110) of the C-MOVE request/indication primitive from which this C-STORE sub-operation is being performed.

##### 9.1.1.1.8 Data Set

The Data Set accompanying the C-STORE primitive contains the Attributes of the Composite SOP Instance to be stored.

##### 9.1.1.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 the response/confirmation. The following types of status may occur in a response/confirmation:

1. Refused: Out of Resources - This indicates that the peer DIMSE-service-user was unable to store the composite SOP Instance because it was out of resources.

2. Refused: SOP Class Not Supported - This indicates that the peer DIMSE-service-user was unable to store the composite SOP Instance because the SOP Class is not supported,

3. Error: Cannot Understand - This indicates that the peer DIMSE-service-user was unable to store the composite SOP Instance because it cannot understand certain Data Elements.

4. Error: Data Set does not match SOP Class - This indicates that the peer DIMSE-service-user was unable to store the composite SOP Instance because the Data Set does not match the SOP Class.

5. Warning - This indicates that the peer DIMSE-service-user was able to store the composite SOP Instance, but detected a probable error.

6. Success - This indicates that the composite SOP Instance was successfully stored.

7. Refused:Duplicate Invocation- Indicates that the Message ID (0000,0110) specified is allocated to another notification or operation.

8. Refused:Invalid SOP Instance- Indicates that the SOP Instance UID specified implied a violation of the UID construction rules.

9. Refused:Mistyped argument- Indicates that one of the parameters supplied has not been agreed for use on the Association between the DIMSE-service-users.

10. Refused:Unrecognized Operation- Indicates that the operation is not one of those agreed between the DIMSE-service-users.

11. Refused:Not Authorized- Indicates that the peer DIMSE-service-user was not authorized to store the composite SOP Instance.

#### 9.1.1.2 C-STORE Service Procedures

The following C-STORE procedures apply:

1. The invoking DIMSE-service-user requests that the performing DIMSE-service-user store a composite SOP Instance by issuing a C-STORE request primitive to the DIMSE-service-provider.

2. The DIMSE-service-provider issues a C-STORE indication primitive to the performing DIMSE-service-user.

3. The performing DIMSE-service-user reports acceptance or rejection of the C-STORE request primitive by issuing a C-STORE response primitive to the DIMSE-service-provider,

4. The DIMSE-service-provider issues a C-STORE confirmation primitive to the invoking DIMSE-service-user, completing the C-STORE operation.

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

### 9.1.2 C-FIND Service

The C-FIND service is used by a DIMSE-service-user to match a set of Attributes against the Attributes of a set of composite SOP Instances maintained by a peer DIMSE-service-user. It is a confirmed service.

#### 9.1.2.1 C-FIND Parameters

See Table 9.1-2.

Table 9.1-2. C-FIND Parameters

DIMSE-C Parameter Name | Req/Ind | Rsp/Conf | CnclReq/CnclInd
Message ID | M | U | -
Message ID Being Responded To | - | M | M
Affected SOP Class UID | M | U(=) | -
Priority | M | - | -
Identifier | M | C | -
Status | - | M | -

##### 9.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

1. Inclusion of this parameter in the confirmation was permitted in previous versions of this Standard but this mode of use is now retired. This parameter may be included in the confirmation but in such a case the invoking DIMSE-service-user should not attach any semantic significance to this parameter.

2. The Message ID (0000,0110) is recommended to be unique within the scope of an Association, to support debug procedures.

##### 9.1.2.1.2 Message ID Being Responded To

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

##### 9.1.2.1.3 Affected SOP Class UID

For the request/indication, this parameter specifies the SOP Class of the Information Model for the query. 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.

##### 9.1.2.1.4 Priority

This parameter specifies the priority of the C-FIND operation. It shall be one of LOW, MEDIUM, or HIGH.

##### 9.1.2.1.5 Identifier

In the request/indication, this is a list of Attributes to be matched against the values of the Attributes in the instances of the composite objects known to the performing DIMSE-service-user.

In the response/confirmation, this is the same list of Attributes with values of these Attributes in a particular composite SOP Instance that matched. It shall be sent only when that Status (0000,0900) is equal to Pending (not permitted for other statuses).

The list of Attributes and the rules for construction are specified in PS3.4.

###### 9.1.2.1.5 Status

Indicates the status of the response. It may have any of the following values:

1. Success-This indicates that processing of the matches is complete. It shall not contain a matching Identifier.

2. Pending-This indicates that processing of the matches is initiated or continuing. It shall contain a matching Identifier.

3. Refused: Out of Resources-Indicates that processing of the C-FIND has been terminated because it was out of resources. This may be the initial response to the C-FIND, or may be sent after a number of pending C-FIND responses. This response shall not contain a matching Identifier.

4. Refused: SOP Class Not Supported - Indicates that processing of the C-FIND has been terminated because the SOP Class was not supported. This response shall not contain a matching Identifier.

5. Cancel-Indicates that the processing of the C-FIND has been terminated due to a C-FIND Cancel indication primitive. The response shall not contain an Identifier.

6. Failed-Indicates that the C-FIND operation failed at the performing DIMSE-service-user.

#### 9.1.2.2 C-FIND Service Procedures

The following C-FIND service procedures apply to the invoking DIMSE-service user:

1. The invoking DIMSE-service-user requests a performing DIMSE-service-user to match an Identifier against the Attributes of all SOP Instances known to the performing DIMSE-service-user by issuing a C-FIND request primitive to the DIMSE-service-provider. If the request is rejected by the DIMSE-service-provider, the following procedures do not apply.

2. At any time before receiving a C-FIND confirmation primitive with a status unequal to Pending, the invoking DIMSE-service-user may request the performing DIMSE-service-user to cancel the service by issuing a C-FIND cancel request primitive to the DIMSE-service-provider.

3. The invoking DIMSE-service-user receives a C-FIND confirmation primitive for each unique match of the Identifier to a set of composite SOP Instance Attributes.

4. The invoking DIMSE-service-user receives a final C-FIND confirmation primitive.

### Note

In the above procedures, (c) may precede (b).

The following C-FIND service procedures apply to the performing DIMSE-service-user:

1. When the performing DIMSE-service-user receives a C-FIND indication from the DIMSE-service-provider, it matches the Identifier against the Attributes of known composite SOP Instances.

2. At any time following the C-FIND indication, the performing DIMSE-service-user may receive a C-FIND cancel indication.

3. If the C-FIND cancel indication is received before the processing of the C-FIND indication has completed, then the C-FIND operation is aborted; otherwise the following procedure does not apply.

4. The performing DIMSE-service-user issues a C-FIND response with a status of Canceled to the DIMSE-service-provider to indicate that the C-FIND has been canceled. The following procedures do not apply.

5. For each match, the performing DIMSE-service-user issues a C-FIND response with the status set to Pending and a matching Identifier.

6. When the C-FIND operation completes (either in success or in failure), the performing DIMSE-service-user issues a C-FIND response with the status set to either Refused, Failed, or Success to the DIMSE-service-provider.

The following C-FIND service procedures apply to the DIMSE-service-provider:

1. When the DIMSE-service-provider receives a C-FIND request primitive from the invoking DIMSE-service-user, it issues a C-FIND indication primitive to the performing DIMSE-service-user.

2. When the DIMSE-service-provider receives a C-FIND cancel request primitive from the invoking DIMSE-service-user, it issues a C-FIND cancel indication to the performing DIMSE-service-user.

3. When the DIMSE-service-provider receives a C-FIND response primitive from the performing DIMSE-service-user, it issues a C-FIND confirmation primitive to the invoking DIMSE-service-user.

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

### 9.1.3 C-GET Service

The C-GET service is used by a DIMSE-service-user to match a set of Attributes against the Attributes of a set of composite SOP Instances maintained by a peer DIMSE-service-user, and retrieve all composite SOP Instances that match. It triggers one or more C-STORE sub-operations on the same Association. It is a confirmed service.

#### 9.1.3.1 C-GET Parameters

See Table 9.1-3.

Table 9.1-3. C-GET Parameters

DIMSE-C Parameter Name | Req/Ind | Rsp/Conf | CnclReq/CnclInd
Message ID | M | U | -
Message ID Being Responded To | - | M | M
Affected SOP Class UID | M | U(=) | -
Priority | M | - | -
Identifier | M | U | -
Status | - | M | -
Number of Remaining Sub-operations | - | C | -
Number of Completed Sub-operations | - | C | -
Number of Failed Sub-operations | - | C | -
Number of Warning Sub-operations | - | C | -

##### 9.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

1. Inclusion of this parameter in the confirmation was permitted in previous versions of this Standard but this mode of use is now retired. This parameter may be included in the confirmation but in such a case the invoking DIMSE-service-user should not attach any semantic significance to this parameter.

2. The Message ID (0000,0110) is recommended to be unique within the scope of an Association, to support debug procedures.

##### 9.1.3.1.2 Message ID Being Responded To

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

##### 9.1.3.1.3 Affected SOP Class UID

For the request/indication, this parameter specifies the SOP Class of the Information Model for the retrieve. 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.

##### 9.1.3.1.4 Priority

This parameter specifies the priority of the C-GET operation. It shall be one of LOW, MEDIUM or HIGH. This priority shall also be the priority used for all sub-operations.

##### 9.1.3.1.5 Identifier

In the request/indication, this is a list of Attributes to be matched against the values of the Attributes of known composite SOP Instances of the performing DIMSE-service-user. The list of Attributes allowed and the rules for the construction are specified in PS3.4.

### Note

The Identifier is specified as U in the Response/Confirmation, but Services defined in PS3.4 that use this primitive may impose mandatory or conditional requirements on its presence.

In the response/confirmation, this is a list of Attributes that provide status information about the C-GET operation. The list of Attributes allowed and the rules that define the usage of the Identifier are specified in PS3.4.

##### 9.1.3.1.6 Status

Indicates the status of the response. It may have any of the following values:

1. Success - This indicates that processing of the matches and all sub-operations are complete.

2. Pending - This indicates that processing of the matches and sub-operations is initiated or continuing.

3. Refused: Out of Resources - Indicates that processing of the C-GET has been terminated because it was out of resources. This may be the initial response to the C-GET or may be sent after a number of Pending statuses.

4. Refused: SOP Class Not Supported - Indicates that processing of the C-GET has been terminated because the SOP Class was not supported.

5. Cancel - Indicates that processing of the C-GET has been terminated due to a C-GET Cancel indication primitive.

6. Failed- Indicates that the C‑GET operation failed at the performing DIMSE-service-user.

7. Refused:Duplicate Invocation- Indicates that the Message ID (0000,0110) specified is allocated to another notification or operation.

8. Refused:Mistyped argument- Indicates that one of the parameters supplied has not been agreed for use on the Association between the DIMSE-service-users.

9. Refused:Unrecognized Operation- Indicates that the operation is not one of those agreed between the DIMSE-service-users.

10. Refused:Not Authorized- Indicates that the peer DIMSE-service-user was not authorized to invoke the C-FIND operation.

##### 9.1.3.1.7 Number of Remaining Sub-Operations

This specifies the number of remaining C-STORE sub-operations to be invoked by this C-GET operation. It may be included in any response/confirmation and shall be included if the status is equal to Pending.

##### 9.1.3.1.8 Number of Completed Sub-Operations

This specifies the number of C-STORE sub-operations invoked by this C-GET operation that have completed successfully. It may be included in any response/confirmation and shall be included if the status is equal to Pending.

##### 9.1.3.1.9 Number of Failed Sub-Operations

This specifies the number of C-STORE sub-operations invoked by this C-GET operation that have failed. It may be included in any response/confirmation and shall be included if the status is equal to Pending.

##### 9.1.3.1.10 Number of Warning Sub-Operations

This specifies the number of C-STORE sub-operation invoked by this C-GET operation that generated Warning responses. It may be included in any response/confirmation and shall be included if the status is equal to Pending.

#### 9.1.3.2 C-GET Service Procedures

The following C-GET service procedures apply to the invoking DIMSE-service user:

1. The invoking DIMSE-service-user requests a performing DIMSE-service-user to match an Identifier against the Attributes of all SOP Instances known to the performing DIMSE-service-user and generate a C-STORE sub-operation for each match. This request is made by issuing a C-GET request primitive to the DIMSE-service-provider. If the request is rejected by the DIMSE-service-provider, the following procedures do not apply.

2. At any time before receiving a C-GET confirmation primitive with status unequal to Pending, the invoking DIMSE-service-user may request the performing DIMSE-service-user to cancel the service by issuing a C-GET cancel request primitive to the DIMSE-service-provider.

3. The invoking DIMSE-service-user may receive C-GET confirmation primitives with status of Pending during the processing of the C-GET operation.

4. The invoking DIMSE-service-user receives a final C-GET confirmation primitive.

### Note

In the above procedures, (c) may precede (b).

The following C-GET service procedures apply to the performing DIMSE-service-user:

1. When the performing DIMSE-service-user receives a C-GET indication from the DIMSE-service-provider it matches the Identifier against the Attributes of known composite SOP Instances and generates a C-STORE sub-operation for each match.

2. At any time following the C-GET indication, the performing DIMSE-service-user may receive a C-GET cancel indication.

3. If the C-GET cancel indication is received before the processing of the C-GET indication has completed, then the C-GET operation is terminated; otherwise the following procedure does not apply.

4. The performing DIMSE-service-user issues a C-GET response with a status of Canceled to the DIMSE-service-provider to indicate that the C-GET has been canceled. The following procedures do not apply.

5. For each match, the performing DIMSE-service-user initiates a C-STORE sub-operation on the same Association as the C-GET. In this sub-operation, the C-GET performing DIMSE-service-user becomes the C-STORE invoking DIMSE-service-user. The C-STORE performing DIMSE-service-user is the C-GET invoking DIMSE-service-user.

6. During the processing of the C-GET operation, the performing DIMSE-service-user may issue C-GET response primitives with a status of Pending.

7. When the C-GET operation completes (either in success or in failure), the performing DIMSE-service-user issues a C-GET response with the status set to either refused, failed or success to the DIMSE-service-provider.

The following C-GET service procedures apply to the DIMSE-service-provider:

1. When the DIMSE-service-provider receives a C-GET request primitive from the invoking DIMSE-service-user, it issues a C-GET indication primitive to the performing DIMSE-service-user.

2. When the DIMSE-service-provider receives a C-GET cancel request primitive from the invoking DIMSE-service-user, it issues a C-GET cancel indication to the performing DIMSE-service-user.

3. When the DIMSE-service-provider receives a C-GET response primitive from the performing DIMSE-service-user, it issues a C-GET confirmation primitive to the invoking DIMSE-service-user.

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

### 9.1.4 C-MOVE Service

The C-MOVE service is used by a DIMSE-service-user to match a set of Attributes against the Attributes of a set of composite SOP Instances maintained by a peer DIMSE-service-user, and retrieve all composite SOP Instances that match. It triggers one or more C-STORE sub-operations on a separate Association. It is a confirmed service.

#### 9.1.4.1 C-MOVE Parameters

See Table 9.1-4.

Table 9.1-4. C-MOVE Parameters

DIMSE-C Parameter Name | Req/Ind | Rsp/Conf | CnclReq/CnclInd
Message ID | M | U | -
Message ID Being Responded To | - | M | M
Affected SOP Class UID | M | U(=) | -
Priority | M | - | -
Move Destination | M | - | -
Identifier | M | U | -
Status | - | M | -
Number of Remaining Sub-operations | - | C | -
Number of Completed Sub-operations | - | C | -
Number of Failed Sub-operations | - | C | -
Number of Warning Sub-operations | - | C | -

##### 9.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

1. Inclusion of this parameter in the confirmation was permitted in previous versions of this Standard but this mode of use is now retired. This parameter may be included in the confirmation but in such a case the invoking DIMSE-service-user should not attach any semantic significance to this parameter.

2. The Message ID (0000,0110) is recommended to be unique within the scope of an Association, to support debug procedures.

##### 9.1.4.1.2 Message ID Being Responded To

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

##### 9.1.4.1.3 Affected SOP Class UID

For the request/indication, this parameter specifies the SOP Class of the Information Model for the retrieve. 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.

##### 9.1.4.1.4 Priority

This parameter specifies the priority of the C-MOVE operation. It shall be one of LOW, MEDIUM or HIGH . This priority shall also be the priority used for all sub-operations.

##### 9.1.4.1.5 Move Destination

This parameter specifies the DICOM AE Title of the destination DICOM AE to which the C-STORE sub-operations are being performed.

##### 9.1.4.1.6 Identifier

In the request/indication, this is a list of Attributes to be matched against the values of the Attributes of known composite SOP Instances of the performing DIMSE-service-user. The list of Attributes allowed and the rules for the construction are in PS3.4.

### Note

The Identifier is specified as U in the Response/Confirmation, but Services defined in PS3.4 that use this primitive may impose mandatory or conditional requirements on its presence.

In the response/confirmation, this is a list of Attributes that provide status information about the C-MOVE operation. The list of Attributes allowed and the rules that define the usage of the Identifier are specified in PS3.4.

##### 9.1.4.1.7 Status

Indicates the status of the response. It may have any of the following values:

1. Success - This indicates that processing of the matches and all sub-operations are complete.

2. Pending - This indicates that procession of the matches and sub-operations is initiated or continuing.

3. Refused: Out of Resources - Indicates that processing of the C-MOVE has been terminated because it was out of resources. This may be the initial response to the C-MOVE or may be sent after a number of Pending statuses.

4. Refused: SOP Class Not Supported - Indicates that processing of the C-MOVE has been terminated because the SOP Class was not supported.

5. Refused: Move Destination Unknown - Indicates that processing of the C-MOVE has been terminated because the Move destination was unknown.

6. Cancel- Indicates that processing of the C-MOVE has been terminated due to a C-MOVE Cancel indication primitive.

7. Failed - Indicates that the C‑MOVE operation failed at the performing DIMSE-service-user.

8. Refused:Duplicate Invocation- Indicates that the Message ID (0000,0110) specified is allocated to another notification or operation.

9. Refused:Mistyped argument- Indicates that one of the parameters supplied has not been agreed for use on the Association between the DIMSE-service-users.

10. Refused:Unrecognized Operation- Indicates that the operation is not one of those agreed between the DIMSE-service-users.

11. Refused:Not Authorized- Indicates that the peer DIMSE-service-user was not authorized to invoke the C-MOVE operation.

##### 9.1.4.1.8 Number of Remaining Sub-Operations

This specifies the number of remaining C-STORE sub-operations to be invoked by this C-MOVE operation. It may be included in any response/confirmation and shall be included if the status is equal to Pending.

##### 9.1.4.1.9 Number of Completed Sub-Operations

This specifies the number of C-STORE sub-operations invoked by this C-MOVE operation that have completed successfully. It may be included in any response/confirmation and shall be included if the status is equal to Pending.

##### 9.1.4.1.10 Number of Failed Sub-Operations

This specifies the number of C-STORE sub-operations invoked by this C-MOVE operation that have failed. It may be included in any response/confirmation and shall be included if the status is equal to Pending.

##### 9.1.4.1.11 Number of Warning Sub-Operations

This specifies the number of C-STORE sub-operation invoked by this C-MOVE operation that generated Warning responses. It may be included in any response/confirmation and shall be included if the status is equal to Pending.

#### 9.1.4.2 C-MOVE Service Procedures

The following C-MOVE service procedures apply to the invoking DIMSE-service user:

1. The invoking DIMSE-service-user requests a performing DIMSE-service-user to match an Identifier against the Attributes of all SOP Instances known to the performing DIMSE-service-user and generate a C-STORE sub-operation for each match. This request is made by issuing a C-MOVE request primitive to the DIMSE-service-provider. If the request is rejected by the DIMSE-service-provider, the following procedures do not apply.

2. At any time before receiving a C-MOVE confirmation primitive with status unequal to Pending, the invoking DIMSE-service-user may request the performing DIMSE-service-user to cancel the service by issuing a C-MOVE cancel request primitive to the DIMSE-service-provider.

3. The invoking DIMSE-service-user may receive C-MOVE confirmation primitives with status of Pending during the processing of the C-MOVE operation.

4. The invoking DIMSE-service-user receives a final C-MOVE confirmation primitive.

### Note

in the above procedures, (c) may precede (b).

The following C-MOVE service procedures apply to the performing DIMSE-service-user:

1. When the performing DIMSE-service-user receives a C-MOVE indication from the DIMSE-service-provider it matches the Identifier against the Attributes of known composite SOP Instances and generates a C-STORE sub-operation for each match.

2. At any time following the C-MOVE indication, the performing DIMSE-service-user may receive a C-MOVE cancel indication.

3. If the C-MOVE cancel indication is received before the processing of the C-MOVE request has completed, then the C-MOVE operation is terminated; otherwise the following procedure does not apply.

4. The performing DIMSE-service-user issues a C-MOVE response with a status of Canceled to the DIMSE-service-provider to indicate that the C-MOVE has been canceled. The following procedures do not apply.

5. For each matching composite SOP Instance, the C-MOVE performing DIMSE-service-user initiates a C-STORE sub-operation on a different Association than the C-MOVE. In this sub-operation, the C-MOVE performing DIMSE-service-user becomes the C-STORE invoking DIMSE-service-user. The C-STORE performing DIMSE-service-user may or may not be the C-MOVE invoking DIMSE-service-user.

6. During the processing of the C-MOVE operation, the performing DIMSE-service-user may issue C-MOVE response primitives with a status of Pending.

7. When the C-MOVE operation completes (either in success or in failure), the performing DIMSE-service-user issues a C-MOVE response with the status set to either Refused, Failed, or Success to the DIMSE-service-provider.

The following C-MOVE service procedures apply to the DIMSE-service-provider:

1. When the DIMSE-service-provider receives a C-MOVE request primitive from the invoking DIMSE-service-user, it issues a C-MOVE indication primitive to the performing DIMSE-service-user.

2. When the DIMSE-service-provider receives a C-MOVE cancel request primitive from the invoking DIMSE-service-user, it issues a C-MOVE cancel indication to the performing DIMSE-service-user.

3. When the DIMSE-service-provider receives a C-MOVE response primitive from the performing DIMSE-service-user, it issues a C-MOVE confirmation primitive to the invoking DIMSE-service-user.

The performing DIMSE-service-user may return a C-MOVE response primitive with the status of Failed or Refused before the entire C-MOVE indication (Data Set) has been completely transmitted by the invoking DIMSE-service-user. A C-MOVE response primitive with the status of Success or Warning shall not be returned until the entire C-MOVE indication has been received by the performing DIMSE-service-user.

### Note

1. Notes: Such an occurrence of a "Failed" response is often called an early failed response.

### 9.1.5 C-ECHO Service

The C-ECHO service is invoked by a DIMSE-service-user to verify end-to-end communications with a peer DIMSE-service-user. It is a confirmed service.

#### 9.1.5.1 C-ECHO Parameters

Table 9.1-5. C-ECHO Parameters

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

##### 9.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

1. Inclusion of this parameter in the confirmation was permitted in previous versions of this Standard but this mode of use is now retired. This parameter may be included in the confirmation but in such a case the invoking DIMSE-service-user should not attach any semantic significance to this parameter.

2. The Message ID (0000,0110) is recommended to be unique within the scope of an Association, to support debug procedures.

##### 9.1.5.1.2 Message ID Being Responded To

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

##### 9.1.5.1.3 Affected SOP Class UID

For the request/indication, this parameter specifies the SOP Class of the SOP Instance for the verification. 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.

##### 9.1.5.1.4 Status

Indicates the status of the response. It may have any of the following values:

1. Success

2. Refused:SOP Class Not Supported -Indicates that a different SOP Class than the Verification SOP Class was specified, which was not supported.

3. Refused:Duplicate Invocation - Indicates that the Message ID (0000,0110) specified is allocated to another notification or operation.

4. Refused:Mistyped argument - Indicates that one of the parameters supplied has not been agreed for use on the Association between the DIMSE-service-users.

5. Refused:Unrecognized Operation - Indicates that a different SOP Class than the Verification SOP Class was specified, which does not recognize a C-ECHO operation.

#### 9.1.5.2 C-ECHO Service Procedures

The following C-ECHO procedures apply:

1. The invoking DIMSE-service-user requests verification of communication to the performing DIMSE-service-user by issuing a C-ECHO request primitive to the DIMSE-service-provider.

2. The DIMSE-service-provider issues a C-ECHO indication primitive to the performing DIMSE-service-user.

3. The performing DIMSE-service-user verifies communication by issuing a C-ECHO response primitive to the DIMSE-service-provider.

4. The DIMSE-service-provider issues a C-ECHO confirmation primitive to the invoking DIMSE-service-user, completing the C-ECHO operation.

Prev |  | Next
8.3 Conformance | Home | 9.2 Sequencing