Материал: part07
|
DICOM PS3.7 2020a - Message Exchange |
Page 101 |
|||
Status Field |
Tag |
VR |
VM |
Description of Field |
|
Action Information |
(no tag) |
- |
- Optionally contains the application specific Data Set to only |
||
|
|
|
encode the invalid argument values conveyed in the |
||
|
|
|
N-ACTION-RQ. Permitted only in the N-ACTION-RSP. |
||
C.5.11 Invalid Attribute Value |
|
|
|
|
|
Status Field |
Tag |
VR |
VM |
Description of Field |
|
Status |
(0000,0900) |
US |
1 Confirmationstatusoftheoperation.Thevalueofthisrequired |
||
|
|
|
field shall be set to 0106H. |
|
|
ModificationList/Attribute |
(no tag) |
- |
- Optionally contains the application specific Data Set to only |
||
List |
|
|
encodetheinvalidAttributeValuesconveyedintheModification |
||
|
|
|
List of the N-SET -RQ or the Attribute List of the |
|
|
|
|
|
N-CREATE-RQ. |
|
|
C.5.12 Invalid SOP Instance |
|
|
|
|
|
Status Field |
Tag |
VR |
VM |
Description of Field |
|
Status |
(0000,0900) |
US |
1 Confirmation status of the operation. The value of this |
||
|
|
|
|
required field shall be set to 0117H. |
|
AffectedSOPInstanceUID |
(0000,1000) |
UI |
1 This optional field contains the SOP Instance UID that |
||
|
|
|
|
violated the UID construction rules. |
|
C.5.13 Missing Attribute |
|
|
|
|
|
Status Field |
Tag |
VR |
VM |
Description of Field |
|
Status |
(0000,0900) |
US |
1 Confirmation status of the operation. The value of this |
||
|
|
|
|
required field shall be set to 0120H. |
|
Attribute Identifier List |
(0000,1005) |
AT |
1-n |
This optional field contains an Attribute Tag for each |
|
|
|
|
|
Attribute that was not recognized. |
|
C.5.14 Missing Attribute Value |
|
|
|
|
|
Status Field |
Tag |
VR |
VM |
Description of Field |
|
Status |
(0000,0900) |
US |
1 Confirmationstatusoftheoperation.Thevalueofthisrequired |
||
|
|
|
field shall be set to 0121H. |
|
|
Modification List/Attribute |
(no tag) |
- |
- Optionally contains the application specific Data Set to only |
||
List |
|
|
encode missing Attribute Values conveyed Modification List |
||
|
|
|
of the N-SET -RQ or the Attribute List of the N-CREATE-RQ.. |
||
C.5.15 Mistyped argument |
|
|
|
|
|
Status Field |
Tag |
VR |
VM |
Description of Field |
|
Status |
(0000,0900) |
US |
1 |
Confirmation status of the operation. The value of this |
|
|
|
|
|
required field shall be set to 0212H. |
|
C.5.16 No such argument |
|
|
|
|
|
Status Field |
Tag |
VR |
VM |
Description of Field |
|
AffectedSOPClassUID |
(0000,0002) |
UI |
1 This optional field shall optionally contain the SOP Class UID |
||
|
|
|
for which the argument does not exist. |
|
|
- Standard -
Page 102 |
DICOM PS3.7 2020a - Message Exchange |
|||
Status Field |
Tag |
VR |
VM |
Description of Field |
Status |
(0000,0900) |
US |
1 Confirmationstatusoftheoperation.Thevalueofthisrequired |
|
|
|
|
field shall be set to 0114H. |
|
Event Type ID |
(0000,1002) |
US |
1 ThisoptionalfieldcontainstheIDoftheEventTypeforwhich |
|
|
|
|
the argument does not exist. Permitted only in the |
|
|
|
|
N-EVENT-REPORT-RSP. |
|
Action Type ID |
(0000,1008) |
US |
1 ThisoptionalfieldcontainstheIDoftheActionTypeforwhich |
|
|
|
|
the argument does not exist. Permitted only in the |
|
|
|
|
N-ACTION-RSP. |
|
C.5.17 No such Attribute |
|
|
|
|
Status Field |
Tag |
VR |
VM |
Description of Field |
Status |
(0000,0900) |
US |
1 Confirmation status of the operation. The value of this |
|
|
|
|
|
required field shall be set to 0105H. |
Attribute Identifier List |
(0000,1005) |
AT |
1-n |
This optional field contains an Attribute Tag for each |
|
|
|
|
Attribute that was not recognized. |
C.5.18 No such Event Type |
|
|
|
|
Status Field |
Tag |
VR |
VM |
Description of Field |
Affected SOP Class UID |
(0000,0002) |
UI |
1 ThisoptionalfieldcontainstheSOPClassUIDforwhich |
|
|
|
|
|
the event type does not exist. |
Status |
(0000,0900) |
US |
1 Confirmation status of the operation. The value of this |
|
|
|
|
|
required field shall be set to 0113H. |
Event Type ID |
(0000,1002) |
US |
1 ThisoptionalfieldcontainstheIDoftheEventTypethat |
|
|
|
|
|
does not exist. |
C.5.19 No such SOP Instance |
|
|
|
|
Status Field |
Tag |
VR |
VM |
Description of Field |
Status |
(0000,0900) |
US |
1 Confirmationstatusoftheoperation.Thevalueofthis |
|
|
|
|
|
required field shall be set to 0112H. |
Affected SOP Instance UID (0000,1000) |
UI |
1 This optional field contains the SOP Instance UID |
||
|
|
|
|
that did not exist. |
C.5.20 No such SOP Class |
|
|
|
|
Status Field |
Tag |
VR |
VM |
Description of Field |
Affected SOP Class UID |
(0000,0002) |
UI |
1 This optional field contains the SOP Class UID that |
|
|
|
|
|
does not exist. |
Status |
(0000,0900) |
US |
1 Confirmationstatusoftheoperation.Thevalueofthis |
|
|
|
|
|
required field shall be set to 0118H. |
C.5.21 Processing Failure |
|
|
|
|
Status Field |
Tag |
VR |
VM |
Description of Field |
Affected SOP Class UID |
(0000,0002) |
UI |
1 This optional field contains the SOP Class UID on which |
|
|
|
|
the processing failure occurred. |
|
Status |
(0000,0900) |
US |
1 Confirmation status of the operation. The value of this |
|
|
|
|
required field shall be set to 0110H. |
|
- Standard -
|
DICOM PS3.7 2020a - Message Exchange |
Page 103 |
|||
Status Field |
Tag |
VR |
VM |
Description of Field |
|
Error Comment |
(0000,0902) |
LO |
1 |
This optional field contains an application-specific text |
|
|
|
|
|
description of the error detected. |
|
Error ID |
(0000,0903) |
US |
1 |
This optional field contains an application-specific error |
|
|
|
|
|
code. |
|
Affected SOP Instance |
(0000,1000) |
UI |
1 |
This optional field shall optionally contain the UID of the |
|
UID |
|
|
|
SOP Instance on which the processing failure occurred. |
|
C.5.22 Resource Limitation |
|
|
|
|
|
Status Field |
Tag |
VR |
VM |
Description of Field |
|
Status |
(0000,0900) |
US |
1 |
Confirmation status of the operation. The value of this |
|
|
|
|
|
required field shall be set to 0213H. |
|
C.5.23 Unrecognized operation |
|
|
|
|
|
Status Field |
Tag |
VR |
VM |
Description of Field |
|
Status |
(0000,0900) |
US |
1 |
Confirmation status of the operation. The value of this |
|
|
|
|
|
required field shall be set to 0211H. |
|
C.5.24 No such Action Type |
|
|
|
|
|
Status Field |
Tag |
VR |
VM |
Description of Field |
|
Affected SOP Class UID |
(0000,0002) |
UI |
1 |
ThisoptionalfieldcontainstheSOPClassUIDforwhich |
|
|
|
|
|
the action type does not exist. |
|
Status |
(0000,0900) |
US |
1 |
Confirmation status of the operation. The value of this |
|
|
|
|
|
required field shall be set to 0123H. |
|
Action Type ID |
(0000,1008) |
US |
1 |
This optional field contains the ID of the Action Type |
|
|
|
|
|
that does not exist. |
|
C.5.25 Refused: Not authorized |
|
|
|
|
|
Status Field |
Tag |
VR |
VM |
Description of Field |
|
Status |
(0000,0900) |
US |
1 |
Confirmation status of the operation. The value of this |
|
|
|
|
|
required field shall be set to 0124H. |
|
Error Comment |
(0000,0902) |
LO |
1 |
This optional field contains an application-specific text |
|
|
|
|
|
description of the error detected. |
|
- Standard -
Page 104 |
DICOM PS3.7 2020a - Message Exchange |
- Standard -
DICOM PS3.7 2020a - Message Exchange |
Page 105 |
D Association Negotiation (Normative)
AssociationestablishmentisthefirstphaseofanyinstanceofcommunicationbetweenpeerDICOMAEs.TheAEsusetheAssociation establishment to negotiate how data will be encoded and the type of data to be exchanged. This Annex provides an overview of the negotiation mechanisms plus a discussion of each concept, its objectives, relationships, usage principles and specifications.
D.1 Abstract Syntax
Abstract Syntaxes specify the Application Layer Data Elements and Application Layer protocol control information (with associated semantics) that are independent of the encoding technique used to represent them.
Each Abstract Syntax shall be identified by an Abstract Syntax Name in the form of a UID. DICOM AEs use the Abstract Syntax Name to identify and negotiate which SOP Classes and related options are supported on a specific Association. Abstract Syntax Names shall be defined in the Service Class Definitions specified in PS3.4. Each Abstract Syntax Name defined shall have a value of either
•a Service-Object Pair Class UID
•a Meta Service-Object Pair Group UID
D.1.1 Service-Object Pair Class UID
Each Service Class Definition defines one or more functionally-related Service-Object Pair (SOP) Class definitions that specify well- defined operations and/or notifications that may be performed between peer DICOM Application Entities to provide an application- level service. Each SOP Class, identified by a SOP Class UID, is defined by the union of one Information Object Definition (IOD) and a specific set of one or more DIMSE Services called the DIMSE Service Group (DSG) in that
•The IOD defines the data structures
•The DSG defines the operations and/or notifications that can be performed on this data structure.
Two SOP Classes defined by a single Service Class Definition may differ by the IOD, the DSG or both. Two different IODs shall not, however, be part of the same SOP Class. Figure D.1-1 shows the relationships between Service Classes, IODs, DSGs and SOP Classes.
Service Class a |
|
|
|
|
Service Class b |
|
|
|
|
|
|
||||
SOP CLASS 1 |
SOP CLASS 2 |
|
SOP CLASS 3 |
SOP CLASS 4 |
SOP CLASS 5 |
||||||||||
Identified by SOP Class UID 1 |
Identified by SOP Class UID 2 |
|
Identified by SOP Class UID 3 |
Identified by SOP Class UID 4 |
Identified by SOP Class UID 5 |
||||||||||
|
DSG 1 |
|
DSG 2 |
|
|
DSG 3 |
|
DSG 4 |
|
DSG 5 |
|||||
|
OPERATION X |
|
|
OPERATION Z |
|
|
|
OPERATION W |
|
|
OPERATION V |
|
|
OPERATION W |
|
|
OPERATION Y |
|
|
|
|
|
|
OPERATION X |
|
|
|
|
|
OPERATION X |
|
+ |
|
+ |
|
||||||||||||
|
|
|
|
|
|
|
|
|
|
|
|
||||
|
+ |
|
|
IOD A |
|
|
|
+ |
|
|
IOD A |
|
|
+ |
|
|
IOD A |
|
|
|
|
|
|
IOD A |
|
|
|
|
|
IOD B |
|
|
|
|
|
|
|
||||||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Figure D.1-1. Service Class, IOD, DSG and SOP Class Relationships
Note
1.TwoexamplesofServiceClassesaretheStorageandStudyManagementServiceClasses.TheStorageServiceClass relates to image Information Object Definitions such as CT, MR etc. and the Study Management Service Class relates to the Study Information Object Definition.
2.For readers familiar with OSI terminology, the concept of the Managed Object Class is the equivalent to the DICOM Service-ObjectPairClass.TheSOPClassspecifiesboththedata(AttributesdefinedintheInformationObjectDefinition) and the methods (Operations and Notifications (DSG) defined in the Service Class).
By setting the Abstract Syntax Name to a specific SOP Class UID value, DICOM Application Entities may negotiate Service Class operations and/or notifications for each defined SOP Class individually.
- Standard -