DICOM PS3.7 2016c - Message Exchange

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

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

The SOP Class Common Extended Negotiation allows, at Association establishment, peer DICOM AEs to exchange application information, the form of which is generic, and not specific to individual Service Classes, as compared to the information defined in D.3.3.5. This is an optional feature that Association-requesters and Association-acceptors may or may not choose to support.

The information included for each SOP Class for which a sub-item is present consists of a Service Class UID and (optionally) a Related General SOP Class UID.

The Service Class UID conveys the Service Class of the SOP Class.

### Note

Explicit conveyance of the Service Class may allow the selection of the proper format for the Service-class-application-information of the SOP Class Extended Negotiation Sub-item.

The Related General SOP Class UID conveys zero or more Related General SOP Class for the SOP Class.

### Note

1. Consider the example of negotiation of support for a Procedure Log Storage SOP Class. That SOP Class is of the Storage Service Class. The encoding of the IOD would be compatible with the more general Enhanced SR Storage SOP Class. Therefore, the following common extended negotiation sub-item could optionally be included:

   - SOP Class UID: 1.2.840.10008.5.1.4.1.1.88.40 Procedure Log

   - Service Class UID: 1.2.840.10008.4.2 Storage Service Class

   - Related General SOP Class UID: 1.2.840.10008.5.1.4.1.1.88.22 Enhanced SR

2. The Related SOP Class may be absent, though the Service Class may still be included. For example, there may be a new image storage SOP Class without a Related SOP Class defined in PS3.4, yet it is still useful to an Association-acceptor to be informed that the new SOP Class is of the Storage Service Class:

   - SOP Class UID: 1.2.840.10008.5.1.4.1.1.7.1 MF Single Bit SC Image Storage

   - Service Class UID: 1.2.840.10008.4.2 Storage Service Class

   - Related General SOP Class UID: (none)

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

No response is necessary, hence the SOP Class Common Extended Negotiation items shall be omitted in the A-ASSOCIATE response.

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

The SOP Class Common Extended Negotiation Sub-item shall be made of a sequence of mandatory fields, the last two of which may be zero-length. Multiple SOP Class Common 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-12 shows the sequence of mandatory fields.

Table D.3-12. SOP Class Common Extended Negotiation Sub-Item Fields (A-ASSOCIATE-RQ)

Item Bytes | Field Name | Description of Field
--- | --- | ---
1 | Item-type | 57H
2 | Sub-item-version | This field indicates the version of the Sub-item. Fields added to the Sub-item definition in succeeding editions of the Standard will not affect the semantics of previously defined fields. The version of the Sub-item defined in this edition of the Standard is 0.
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 Reserved 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 in the SOP-class-uid field. It shall be encoded as an unsigned binary number.
7-x | SOP-class-uid | The SOP Class identifier encoded as a UID as defined in PS3.5.
(x+1) - (x+2) | Service-class-uid-length | The Service-class-uid-length shall be the number of bytes in the Service-class-uid field. It shall be encoded as an unsigned binary number.
(x+3) - y | Service-class-uid | The Service Class identifier encoded as a UID as defined in PS3.5.
(y+1) - (y+2) | Related-general-sop-class-identification-length | The Related-general-sop-class-identification-length shall be the number of bytes in the Related-general-sop-class-identification field. Shall be zero if no Related General SOP Classes are identified.
(y+3) - z | Related-general-sop-class-identification | The Related-general-sop-class-identification is a sequence of pairs of length and UID sub-fields. Each pair of sub-fields shall be formatted in accordance with Table D.3-13
(z+1) - k | Reserved | Reserved for additional fields of the sub-item. Shall be zero-length for Version 0 of Sub-item definition.

Table D.3-13. Related-General-SOP-Class-Identification Sub-Fields

Bytes | Sub-Field Name | Description of Sub-Field
--- | --- | ---
1-2 | Related-general-sop-class-uid-length | The Related-general-sop-class-uid-length shall be the number of bytes in the Related-general-sop-class-uid sub-field. It shall be encoded as an unsigned binary number.
3-n | Related-general-sop-class-uid | The Related General SOP Class identifier encoded as a UID as defined in PS3.5.

Prev | Up | Next
D.3.3.5.2 SOP Class Extended Negotiation Sub-Item Structure (A-ASSOCIATE-AC) | Home | D.3.3.7 User Identity Negotiation

DICOM PS3.7 2016c - Message Exchange