DICOM PS3.4 2019b - Service Class Specifications

B.3 Association Negotiation (Current)
Prev | B Storage Service Class (Normative) | Next

## B.3 Association Negotiation

SCUs and SCPs of Storage SOP Classes operate on SOP Instances specific to the SOP Class. They may use the SOP Class Extended Negotiation Sub-Item defined in PS3.7. This Sub-Item allows DICOM AEs to exchange application information specific to SOP Class specifications. This is achieved by defining the Service-class-application-information field.

SCUs may use the SOP Class Common Extended Negotiation Sub-Item defined in PS3.7. This Sub-Item allows DICOM AEs to exchange information about the nature of the SOP Classes.

The SOP Class Extended Negotiation Sub-Item and SOP Class Common Extended Negotiation Sub-Item negotiation is optional for storage based SOP Classes.

The following negotiation rules apply to all DICOM SOP Classes and Specialized SOP Classes of the Storage Service Class.

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

- one Abstract Syntax, in a Presentation Context, for each supported SOP Class of the Storage Service Class

- optionally, one SOP Class Extended Negotiation Sub-Item, for each supported SOP Class of the Storage Service Class

- optionally, one SOP Class Common Extended Negotiation Sub-Item, for each supported SOP Class of the Storage Service Class

The Association-acceptor (Storage SCP role) in the A-ASSOCIATE request shall accept:

- one Abstract Syntax, in a Presentation Context, for each supported SOP Class of the Storage Service Class

- optionally, one SOP Class Extended Negotiation Sub-Item, for each supported SOP Class of the Storage Service Class

### B.3.1 Extended Negotiation

At the time of Association establishment implementations may exchange information about their respective capabilities, as described in PS3.7 and PS3.8. SCUs and SCPs may use the SOP Class Extended Negotiation Sub-Item Structure as described in Section D.3.3.5 in PS3.7 to exchange information about the level of conformance and options supported. SCUs may use the SOP Class Common Extended Negotiation Sub-Item defined in Section D.3.3.6 in PS3.7 to exchange information about the nature of the SOP Classes.

Extended negotiation is optional. In the event that either the SCU or the SCP does not support extended negotiation, the defaults shall apply.

#### B.3.1.1 Service-Class-Application-Information (A-ASSOCIATE-RQ)

The SOP Class Extended Negotiation Sub-item is made of a sequence of mandatory fields as defined by PS3.7. Table B.3-1 shows the format of the Service-class-application-information field of the SOP Class Extended Negotiation Sub-Item for SOP Classes of the Storage Service Class in the A-ASSOCIATE-RQ.

Table B.3-1. Service-Class-Application-Information (A-ASSOCIATE-RQ)

Item Bytes | Field Name | Description of Field
--- | --- | ---
1 | Level of support | This byte field defines the supported storage level of the Association-requester. It shall be encoded as an unsigned binary integer and shall use one of the following values: 0 - level 0 SCP 1 - level 1 SCP 2 - level 2 SCP 3 - N/A Association-requester is SCU only If extended negotiation is not supported, the default shall have a value of 3.
2 | Reserved | This reserved field shall be sent with a value 00H but not tested to this value when received.
3 | Level of Digital Signature support | A Level 2 SCP may further define its behavior in this byte field. 0 - The signature level is unspecified, the AE is an SCU only, or the AE is not a level 2 SCP 1 - signature level 1 2 - signature level 2 3 - signature level 3 If extended negotiation is not supported, the default shall have a value of 0.
4 | Reserved | This reserved field shall be sent with a value 00H but not tested to this value when received.
5 | Element Coercion | This byte field defines whether the Association-requester may coerce Data Elements. It shall be encoded as an unsigned binary integer and shall use one of the following values: 0 - does not coerce any Data Element 1 - may coerce Data Elements 2 - N/A - Association-requester is SCU only If extended negotiation is not supported, the default shall have a value of 2.
6 | Reserved | This reserved field shall be sent with a value 00H but not tested to this value when received.

#### B.3.1.2 Service-Class-Application-Information (A-ASSOCIATE-AC)

The SOP Class Extended Negotiation Sub-item is made of a sequence of mandatory fields as defined by PS3.7. Table B.3-2 shows the format of the Service-class-application-information field of the SOP Class Extended Negotiation Sub-Item for SOP Classes of the Storage Service Class in the A-ASSOCIATE-AC.

Table B.3-2. Service-Class-Application-Information (A-ASSOCIATE-AC)

Item Bytes | Field Name | Description of Field
--- | --- | ---
1 | Level of support | This byte field defines the supported storage level of the Association-acceptor. It shall be encoded as an unsigned binary integer and shall use one of the following values: 0 - level 0 SCP 1 - level 1 SCP 2 - level 2 SCP 3 - N/A - Association-acceptor is SCU only If extended negotiation is not supported, no assumptions shall be made by the Association-requester about the capabilities of the Association-acceptor based upon this extended negotiation.
2 | Reserved | This reserved field shall be sent with a value 00H but not tested to this value when received.
3 | Level of Digital Signature support | A Level 2 SCP may further define its behavior in this byte field. 0 - The signature level is unspecified, the AE is an SCU only, or the AE is not a level 2 SCP 1 - signature level 1 2 - signature level 2 3 - signature level 3 If extended negotiation is not supported, no assumptions shall be made by the Association-requester about the capabilities of the Association-acceptor based upon this extended negotiation.
4 | Reserved | This reserved field shall be sent with a value 00H but not tested to this value when received.
5 | Element Coercion | This byte field defines whether the Association-acceptor may coerce Data Elements. It shall be encoded as an unsigned binary integer and shall use one of the following values: 0 - does not coerce any Data Element 1 - may coerce Data Elements 2 - N/A - Association-acceptor is SCU only If extended negotiation is not supported, no assumptions shall be made by the Association-requester about the capabilities of the Association-acceptor based upon this extended negotiation.
6 | Reserved | This reserved field shall be sent with a value 00H but not tested to this value when received.

#### B.3.1.3 Service Class UID (A-ASSOCIATE-RQ)

SOP Class Common Extended Negotiation Sub-Item allows the SCU to convey the Service Class UID of each proposed SOP Class.

The Storage Service Class UID shall be "1.2.840.10008.4.2".

#### B.3.1.4 Related General SOP Classes (A-ASSOCIATE-RQ)

A limited set of Standard SOP Classes in the Storage Service Class are defined to have one or more Related General SOP Classes. The Related General SOP Classes may be conveyed using the SOP Class Relationship Extended Negotiation during association establishment as defined in PS3.7. Table B.3-3 identifies which Standard SOP Classes participate in this mechanism. If a Standard SOP Class is not listed in this table, Related General SOP Classes shall not be included in a Related Storage SOP Class Extended Negotiation Sub-Item.

### Note

Implementation-defined Specialized SOP Classes (see PS3.2) of the Storage Service Class may convey a Related General SOP Class.

Table B.3-3. Standard and Related General SOP Classes

SOP Class Name | Related General SOP Class Name
--- | ---
12-lead ECG Waveform Storage | General ECG Waveform Storage
Digital Mammography X-Ray Image Storage - For Presentation | Digital X-Ray Image Storage - For Presentation
Digital Mammography X-Ray Image Storage - For Processing | Digital X-Ray Image Storage - For Processing
Digital Intra-Oral X-Ray Image Storage - For Presentation | Digital X-Ray Image Storage - For Presentation
Digital Intra-Oral X-Ray Image Storage - For Processing | Digital X-Ray Image Storage - For Processing
Basic Text SR | Enhanced SR
Comprehensive SR
Comprehensive 3D SR
Extensible SR
Enhanced SR | Comprehensive SR
Comprehensive 3D SR
Extensible SR
Comprehensive SR | Comprehensive 3D SR
Extensible SR
Comprehensive 3D SR | Extensible SR
Procedure Log | Enhanced SR
Comprehensive SR
Comprehensive 3D SR
Extensible SR
Simplified Adult Echo SR | Enhanced SR
Comprehensive SR
Comprehensive 3D SR
Extensible SR
X-Ray Radiation Dose SR | Enhanced SR
Comprehensive SR
Comprehensive 3D SR
Extensible SR
Radiopharmaceutical Radiation Dose SR | Enhanced SR
Comprehensive SR
Comprehensive 3D SR
Extensible SR
Patient Radiation Dose SR | Enhanced SR
Comprehensive SR
Comprehensive 3D SR
Extensible SR
Acquisition Context SR | Enhanced SR (see note)
Comprehensive SR (see note)
Comprehensive 3D SR
Extensible SR
Spectacle Prescription Report | Enhanced SR
Macular Grid Thickness and Volume Report | Enhanced SR
Enhanced CT Image Storage | Legacy Converted Enhanced CT Image Storage
Enhanced MR Image Storage | Legacy Converted Enhanced MR Image Storage
Enhanced PET Image Storage | Legacy Converted Enhanced PET Image Storage

### Note

The Acquisition Context SR may be encoded as Enhanced or Comprehensive only if it does not contain stereotactic coordinates (SCOORD3D).

Prev | Up | Next
B.2.3 Statuses | Home | B.4 Conformance

DICOM PS3.4 2019b - Service Class Specifications