DICOM PS3.7 2020d - Message Exchange

D.3.3.5 Service-Object Pair (SOP) Class Extended Negotiation (Current)
Prev | D.3.3 DICOM Application Association Information | Next

#### D.3.3.5 Service-Object Pair (SOP) Class Extended Negotiation

The SOP Class Extended Negotiation allows, at Association establishment, peer DICOM AEs to exchange application information defined by specific Service Class specifications. This is an optional feature that various Service Classes may or may not choose to support.

Each Service Class specification is required to document, as part of its SOP Class or Meta SOP Class, the application information it supports and how this information is negotiated between SCUs and SCPs. Service Class specifications shall specify, for both the SCU and SCP roles, the following:

- semantics of the application information (including the negotiation rules)

- encoding of the application information

- conditions for which the application information is mandatory and/or optional

- default conditions of the application information

### Note

The use of the SOP Class Extended Negotiation is not limited to Service Classes defined by this Standard. It may also be used for privately defined Service Classes.

The Association-requester may only offer one SOP Class Extended Negotiation Sub-Item for each SOP Class UID or Meta SOP Class that is present in the A-ASSOCIATE request.

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.

##### D.3.3.5.1 SOP Class Extended Negotiation Sub-Item Structure (A-ASSOCIATE-RQ)

The SOP Class Extended Negotiation Sub-Item shall be made of a sequence of mandatory fields followed by the Service-class-application-information field (specific for each Service Class specification). This Sub-Item is required per the specific Service Class specifications. Multiple SOP Class Extended Negotiation Sub-Items may be present in the User Data Item of the A-ASSOCIATE-RQ, however, only one Sub-Item per SOP Class UID shall be present. Table D.3-11 shows the sequence of mandatory fields.

Table D.3-11. SOP Class Extended Negotiation Sub-Item Fields (A-ASSOCIATE-RQ and A-ASSOCIATE-AC)

Item Bytes | Field Name | Description of Field
--- | --- | ---
1 | Item-type | 56H
2 | Reserved | This reserved field shall be sent with a value 00H but not tested to this value when received.
3-4 | Item-Length | This Item-length shall be the number of bytes from the first byte of the following field to the last byte of the Service-class-application-information field. It shall be encoded as an unsigned binary number.
5-6 | SOP-class-uid-length | The SOP-class-uid-length shall be the number of bytes from the first byte of the following field to the last byte of the SOP-class-uid field. It shall be encoded as an unsigned binary number.
7-xxx | SOP-class-uid | The SOP Class or Meta SOP Class identifier encoded as a UID as defined in PS3.5.
xxx-xxx | Service-class-application-information | This field shall contain the application information specific to the Service Class specification identified by the SOP-class-uid. The semantics and value of this field is defined in the identified Service Class specification.

Prev | Up | Next
D.3.3.4.2 SCP/SCU Role Selection Sub-Item Structure (A-ASSOCIATE-AC) | Home | D.3.3.5.2 SOP Class Extended Negotiation Sub-Item Structure (A-ASSOCIATE-AC)

DICOM PS3.7 2020d - Message Exchange