C.5 Association negotiation

Association establishment is the first phase of any instance of communication between peer DICOM AEs. AEs supporting DICOM Query/Retrieve SOP Classes utilize Association establishment negotiation by defining the use of Application Association Information. See PS 3.7 for an overview of Association negotiation.

SOP Classes of the Query/Retrieve Service Class, which include query services based on the C-FIND operation, may use SOP Class Extended Negotiation Sub-Item to negotiate options such as Relational-queries.

SOP Classes of the Query/Retrieve Service Class, which include retrieval services based on the C-MOVE and C-GET operations, may use the SOP Class Extended Negotiation Sub-Item to negotiate relational-retrieval.

SOP Classes of the Query/Retrieve Service Class, which include retrieval services based on the C-GET operation, use the SCP/SCU Role Selection Sub-Item to identify the SOP Classes which may be used for retrieval.

C.5.1 Association Negotiation for C-FIND SOP Classes

The following negotiation rules apply to DICOM SOP Classes and Specialized DICOM SOP Classes of the Query/Retrieve Service Class which include the C-FIND operation.

The Association-requester (query SCU role) shall convey in the A-ASSOCIATE request:

The Association-acceptor (query SCP role) of an A-ASSOCIATE request shall accept:

C.5.1.1 SOP Class Extended Negotiation

The SOP Class Extended Negotiation allows, at Association establishment, peer DICOM AEs to exchange application Association information defined by specific SOP Classes. This is achieved by defining the Service-class-application-information field. The Service-class-application-information field is used to define support for relational-queries, combined date time matching, and fuzzy semantic matching of person names.

This negotiation is optional. If absent, the default conditions shall be:

The Association-requester, for each SOP Class, may use one SOP Class Extended Negotiation Sub-Item. The SOP Class is identified by the corresponding Abstract Syntax Name (as defined by PS 3.7) followed by the Service-class-application-information field. This field defines either a single sub-field:

or three sub-fields:

The Association-acceptor shall return a single byte field (single sub-field) if offered a single byte field (single sub-field) by the Association-requester. The Association-acceptor may return either a single byte field (single sub-field) or a three byte field (three sub-fields) if offered a three byte field (three sub-fields) by the Association-requester. A one byte response to a three byte request means that the missing sub-fields shall be treated as 0 values.

The Association-acceptor, for each sub-field of the SOP Class Extended Negotiation Sub-Item offered, either accepts the Association-requester proposal by returning the same value (1) or turns down the proposal by returning the value (0)

If the SOP Class Extended Negotiation Sub-Item is not returned by the Association-acceptor then relational-queries are not supported over the Association (default condition).

If the SOP Class Extended Negotiation Sub-Items do not exist in the A-ASSOCIATE indication they shall be omitted in the A-ASSOCIATE response.

C.5.1.1.1 SOP Class Extended Negotiation Sub-Item Structure (A-ASSOCIATE-RQ)

The SOP Class Extended Negotiation Sub-Item consists of a sequence of mandatory fields as defined by PS 3.7. Table C.5-1 defines the Service-class-application-information field for DICOM Query/Retrieve SOP Classes and Specialized DICOM Query/Retrieve SOP Classes which include the C-FIND operation. This field may be either one or three bytes in length (i.e., item bytes 2 and 3 are optional).

Table C.5-1— SOP CLASS EXTENDED NEGOTIATION SUB-ITEM (service-class-application-information field)—A-ASSOCIATE-RQ

Item Bytes Field Name Description of Field
1 Relational-queries This byte field defines relational-query support by the Association-requester. It shall be encoded as an unsigned binary integer and shall use one of the following values 0 – relational queries not supported 1 – relational queries supported
2 Date-time matching This byte field defines whether or not combined date and time attribute range matching is requested by the Association-requester. It shall be encoded as an unsigned binary integer and shall use one of the following values 0 – combined matching not requested 1 – combined matching requested
3 Fuzzy semantic matching of person names This byte field defines whether or not fuzzy semantic person name attribute matching is requested by the Association-requester. It shall be encoded as an unsigned binary integer and shall use one of the following values 0 – fuzzy semantic matching not requested 1 – fuzzy semantic matching requested
4 Timezone query adjustment This byte field defines whether or not the Attribute Timezone Offset From UTC (0008,0201) shall be used to adjust the query meaning for time and datetime fields in queries. 0 - Timezone query adjustment not requested 1 – Timezone query adjustment requested

C.5.1.1.2 SOP Class Extended Negotiation Sub-Item Structure (A-ASSOCIATE-AC)

The SOP Class Extended Negotiation Sub-Item is made of a sequence of mandatory fields as defined by PS 3.7. Table C.5-2 defines the Service-class-application-information field for DICOM Query/Retrieve SOP Classes and Specialized DICOM Query/Retrieve SOP Classes which include the C-FIND operation. This field may be either one or three bytes in length (i.e., item bytes 2 and 3 are optional).

Table C.5-2—SOP CLASS EXTENDED NEGOTIATION SUB-ITEM(service-class-application-information field)—A-ASSOCIATE-AC

Item Bytes Field Name Description of Field
1 Relational-queries This byte field defines relational-query support for the Association-acceptor. It shall be encoded as an unsigned binary integer and shall use one of the following values 0 – relational-queries not supported 1 – relational-queries supported
2 Date-time matching This byte field defines whether or not combined date and time attribute range matching will be performed by the Association-acceptor. It shall be encoded as an unsigned binary integer and shall use one of the following values 0 – combined matching not performed 1 – combined matching performed
3 Fuzzy semantic matching of person names This byte field defines whether or not fuzzy semantic person name attribute matching will be performed by the Association-acceptor. It shall be encoded as an unsigned binary integer and shall use one of the following values 0 – fuzzy semantic matching not performed 1 – fuzzy semantic matching performed
4 Timezone query adjustment This byte field defines whether or not the Attribute Timezone Offset From UTC (0008,0201) shall be used to adjust the query meaning for time and datetime fields in queries. 0 – Timezone adjustment of queries not performed 1 – Timezone adjustment of queries performed

C.5.2 Association Negotiation for C-MOVE SOP Classes

The following negotiation rules apply to DICOM SOP Classes and Specialized DICOM SOP Classes of the Query/Retrieve Service Class which include the C-MOVE operation.

The Association-requester (retrieval SCU role) shall convey in the A-ASSOCIATE request:

The Association-acceptor (retrieval SCP role) of an A-ASSOCIATE request shall accept:

C.5.2.1 SOP Class Extended Negotiation

The SOP Class Extended Negotiation allows, at Association establishment, peer DICOM AEs to exchange application Association information defined by specific SOP Classes. This is achieved by defining the Service-class-application-information field. The Service-class-application-information field is used to define support for relational-retrievals.

This negotiation is optional. If absent, the default condition shall be:

The Association-requester, for each SOP Class, may use one SOP Class Extended Negotiation Sub-Item. The SOP Class is identified by the corresponding Abstract Syntax Name (as defined by PS 3.7) followed by the Service-class-application-information field. This field defines:

The Association-acceptor, for each SOP Class Extended Negotiation Sub-Item offered, either accepts the Association-requester proposal by returning the same value (1) or turns down the proposal by returning the value (0).

If the SOP Class Extended Negotiation Sub-Item is not returned by the Association-acceptor then relational-retrievals are not supported (default condition)

If the SOP Class Extended Negotiation Sub-Items do not exist in the A-ASSOCIATE indication they shall be omitted in the A-ASSOCIATE response.

C.5.2.1.1 SOP Class Extended Negotiation Sub-Item Structure (A-ASSOCIATE-RQ)

The SOP Class Extended Negotiation Sub-Item consists of a sequence of mandatory fields as defined by PS 3.7. Table C.5-3 defines the Service-class-application-information field for DICOM Query/Retrieve SOP Classes and Specialized DICOM Query/Retrieve SOP Classes which include the C-MOVE and C-GET operations.

Table C.5-3—SOP CLASS EXTENDED NEGOTIATION SUB-ITEM(service-class-application-information field)—A-ASSOCIATE-RQ

Item Bytes Field Name Description of Field
1 Relational-retrieval This byte field defines relational-retrieval support by the Association-requester. It shall be encoded as an unsigned binary integer and shall use one of the following values 0 – relational-retrieval not supported 1 – relational-retrieval supported

C.5.2.1.2 SOP Class Extended Negotiation Sub-Item Structure (A-ASSOCIATE-AC)

The SOP Class Extended Negotiation Sub-Item consists of a sequence of mandatory fields as defined by PS 3.7. Table C.5-4 defines the Service-class-application-information field for DICOM Query/Retrieve SOP Classes and Specialized DICOM Query/Retrieve SOP Classes which include the C-MOVE and C-GET operations.

Table C.5-4—SOP CLASS EXTENDED NEGOTIATION SUB-ITEM(service-class-application-information field)—A-ASSOCIATE-AC

Item Bytes Field Name Description of Field
1 Relational-retrieval This byte field defines relational-retrieval support for the Association-acceptor. It shall be encoded as an unsigned binary integer and shall use one of the following values 0 – relational-retrievals not supported 1 – relational-retrievals supported

C.5.3 Association Negotiation for C-GET SOP Classes

When an SCP performs the C-GET operation it induces a C-STORE operation for the purpose of transmitting composite SOP Instances for Storage. This induced C-STORE operation (called a sub-operation) requires a switch from the C-GET Presentation Context to a Presentation Context that supports the specific C-STOREsub-operation.

The following negotiation rules apply to retrieval based DICOM Query/Retrieve SOP Classes and Specialized DICOM Query/Retrieve SOP Classes which include the C-GET operation.

The Association-requester (retrieve SCU role) in the A-ASSOCIATE request shall convey:

a) C-GET operation support with:

b) Induced Storage sub-operation support where the SOP Class (in the retrieval SCU role) is acting as a Storage SOP Class in the SCP Role. See Figure C.5-1. For each supported Storage SOP Class, the A-ASSOCIATE request contains:

[pic]

Figure C.5-1 AN EXAMPLE OF THE SUB-OPERATION SCU/SCP ROLES

Note: This negotiation does not place any requirements on the SCU-flag of the SCP/SCU Role Selection Negotiation Sub-Item. It may be set if the Association-requester supports the Storage Service Class in the SCU role.

The Association-acceptor (retrieve SCP role) in the A-ASSOCIATE response shall convey:

a) C-GET operation support with:

b) Induced Storage sub-operation support where the SOP Class (using the retrieval SCP role) is acting as a Storage SOP Class in the SCU Role. See Figure C.5-1. For each supported Storage SOP Class, the A-ASSOCIATE response contains both:

Note: The negotiation does not place any requirements on the SCU-flag of the SCP/SCU Role Selection Negotiation Sub-Item. It may be set if the Association-acceptor accepts the Storage SCP role. Figure C.5-2 illustrates an example of the retrieve (C-GET) negotiation.

Figure C.5-2 illustrates an example of the retrieve (C-GET) negotiation.

C.5.3.1 SOP Class Extended Negotiation

The SOP Class Extended Negotiation allows, at Association establishment, peer DICOM AEs to exchange application Association information defined by specific SOP Classes.

This is achieved by defining the Service-class-application-information field. The Service-class-application-information field is used to define support for relational-retrievals.

[pic] Figure C.5-2 AN EXAMPLE OF THE RETRIEVE (C-GET) NEGOTIATION

Extended negotiation for SOP Classes based on the retrieval services which include C-GET operations is identical to the negotiation defined for C-MOVE which is defined in Section C.5.2.1 of this Annex.

Extended negotiation for the SOP Classes of the Storage Service Class (for the C-STORE sub-operation) is defined in Annex B.