DICOM PS3.4 2017b - Service Class Specifications

C.5 Association Negotiation
Prev | C Query/Retrieve Service Class (Normative) | Next

## 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 PS3.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 and Enhanced Multi-Frame Image Conversion.

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 and Enhanced Multi-Frame Image Conversion.

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 that 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 that include the C-FIND operation.

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

- one Abstract Syntax, in a Presentation Context, for each query based SOP Class supported

- optionally, one SOP Class Extended Negotiation Sub-Item, for each query based SOP Class

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

- one Abstract Syntax, in a Presentation Context, for each query based SOP Class supported

- optionally, one SOP Class Extended Negotiation Sub-Item, for each query based SOP Class

#### 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, fuzzy semantic matching of person names, timezone query adjustment and Enhanced Multi-Frame Image Conversion.

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

- no relational-query support

- separate (independent) range matching of date and time Attributes

- literal matching of person names with case sensitivity unspecified

- timezone query adjustment unspecified

- no Enhanced Multi-Frame Image Conversion support

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 PS3.7) followed by the Service-class-application-information field. This field defines one or more sub-fields:

- relational-query support by the Association-requester

- combined date and time range matching by the Association-requester

- literal or fuzzy semantic matching of person names by the Association-requester

- timezone query adjustment by the Association-requester

- Enhanced Multi-Frame Image Conversion support by the Association-requester

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 multiple byte field if offered a multiple byte field by the Association-requester. A one byte response to a multiple byte request means that the missing sub-fields shall be treated as 0 values.

### Note

The restriction to return only a single byte field if that was all that was offered is because the original DICOM standard only contained one byte and older systems may not be expecting more.

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 PS3.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 that include the C-FIND operation. This field may be either one or more bytes in length (i.e., item bytes 2, 3, 4 and 5 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. It shall be encoded as an unsigned binary integer and shall use one of the following values 0 - Timezone query adjustment not requested 1 - Timezone query adjustment requested
5 | Enhanced Multi-Frame Image Conversion | This byte field defines whether or not the Attribute Query/Retrieve View (0008,0053) shall be used to adjust the view returned in queries to consider conversion to or from Enhanced Multi-Frame Images. It shall be encoded as an unsigned binary integer and shall use one of the following values 0 - Query/Retrieve View not supported 1 - Query/Retrieve View supported

##### 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 PS3.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 that include the C-FIND operation. This field may be either one or more bytes in length (i.e., item bytes 2, 3, 4 and 5 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. It shall be encoded as an unsigned binary integer and shall use one of the following values 0 - Timezone adjustment of queries not performed 1 - Timezone adjustment of queries performed
5 | Enhanced Multi-Frame Image Conversion | This byte field defines whether or not the Attribute Query/Retrieve View (0008,0053) shall be used to adjust the view returned in queries to consider conversion to or from Enhanced Multi-Frame Images. It shall be encoded as an unsigned binary integer and shall use one of the following values 0 - Query/Retrieve View not supported 1 - Query/Retrieve View supported

Prev | Up | Next
C.4.3.3.2 Extended Behavior of SCP | Home | C.5.2 Association Negotiation for C-MOVE SOP Classes

DICOM PS3.4 2017b - Service Class Specifications