Материал: part08

- Standard -​

10 Conformance​

10.1 Conformance Requirements​

10.1.1Retired​

10.1.2TCP/IP Network Communication Support​

An implementation claiming conformance to DICOM TCP/IP Network Communication Supportshall:​

a.​Meet the DICOM Upper Layers Protocol requirements as defined in Section 9.​

b.​Use registered Application Context Names, Abstract Syntax Names and Transfer Syntax Names as defined for OSI Object​ Identifiers (ISO 8824 and ISO 9834-1).​

Note​

AnnexFdefinestheDICOMUpperLayerProtocolencodingfortheApplicationContextNames,AbstractSyntaxNames,​ and Transfer Syntax Names. ISO 8825 defined encoding is not used.​

c.​Use one of the published and approved RFCs defining the operation of TCP/IP over specific physical networks.​

10.2 Conformance Statement​

An implementation claiming conformance to DICOM for communication support in a networked environment shall state DICOM V3.0​ TCP/IP Network Communication Support with the list of physical networks and corresponding relevant implementation information.​ This implies that the conformance requirements defined in Section 10.1.2 are met.​

- Standard -​

- Standard -​

A Application Context Names (Informative)​

A.1 Application Context Definition​

An application context explicitly defines the set of application service elements, related options and any other information necessary​ for the interworking of Application Entities on an association. The usage of the application context is defined in PS3.7.​

Two Application Entities when establishing an association agree on an application context. The requestor of an association proposes​ an Application Context Name and the acceptor returns either the same or a different Application Context Name. The returned name​ specifies the application context to be used for this association. The offer of an alternate application context by the acceptor provides​ amechanismforlimitednegotiation.Iftherequestorcannotoperateintheacceptor'sapplicationcontext,itwillissueanA-Abortrequest​ primitive. Such a negotiation will facilitate the introduction of future versions of the DICOM Application Entity.​

A.2 DICOM Application Context Name Encoding and Registration​

The Application Context Name structure is based on the OSI Object Identification (numeric form) as defined by ISO 8824. Application​ Context Names are registered values as defined by ISO 9834-1 to ensure global uniqueness. They are encoded as defined in Annex​ F when the TCP/IP network communication support is used as defined in Section 9.​

A.2.1 DICOM Registered Application Context Names​

The organization responsible for the definition and registration of DICOM Application Context Names is NEMA. NEMA guarantees​ uniquenessforallDICOMApplicationContextNames.AchoiceofDICOMregisteredApplicationContextNamesrelatedtotheDICOM​ Application Entities, as well as the associated negotiation rules, are defined in PS3.7.​

- Standard -​

- Standard -​