A Network AE is an application entity that provides services on a network. A Network AE will have the same functional capability regardless of the particular network connection used. If there are functional differences based on selected network connection, then these are separate Network AEs. If there are functional differences based on other internal structures, then these are separate Network AEs.
Table H.1-4 Attributes of Network AE Object
|AE Title||1||Unique AE title for this Network AE|
|Description||0..1||Unconstrained text description of the application entity.|
|Vendor Data||0..N||AE specific vendor configuration information|
|Application Cluster||0..N||Locally defined names for a subset of related applications. E.g. “neuroradiology”.|
|Preferred Called AE Title||0..N||AE Title(s) that are preferred for initiating associations.|
|Preferred Calling AE Title||0..N||AE Title(s) that are preferred for accepting associations.|
|Association Acceptor||1||A Boolean value. True if the Network AE can accept associations, false otherwise.|
|Association Initiator||1||A Boolean value. True if the Network AE can accept associations, false otherwise.|
|Network Connection Reference||1..N||The DNs of the Network Connection objects for this AE|
|Supported Character Set||0..N||The Character Set(s) supported by the Network AE for data sets it receives. The value shall be selected from the Defined Terms for Specific Character Set (0008,0005) in PS3.3. If no values are present, this implies that the Network AE supports only the default character repertoire (ISO IR 6).|
|Installed||0..1||A Boolean value. True if the AE is installed on network. If not present, information about the installed status of the AE is inherited from the device|
The “Application Cluster” concept provides the mechanism to define local clusters of systems. The use cases for Configuration Management require a “domain” capability for DICOM applications that would be independent of the network topology and administrative domains that are used by DNS and other TCP level protocols. The Application Cluster is multi-valued to permit multiple clustering concepts for different purposes. It is expected to be used as part of a query to limit the scope of the query.
The “Preferred Called AE Title” concept is intended to allow a site administrator to define a limited default set of AEs that are preferred for use as communication partners when initiating associations. This capability is particularly useful for large centrally administered sites to simplify the configuration possibilities and restrict the number of configured AEs for specific workflow scenarios. For example, the set of AEs might contain the AE Titles of assigned Printer, Archive, RIS and QA Workstations so that the client device could adapt its configuration preferences accordingly. The “Preferred Called AE Title” concept does not prohibit association initiation to unlisted AEs. Associations to unlisted AEs can be initiated if necessary.
The “Preferred Calling AE Title” concept is intended to allow a site administrator to define a default set of AEs that are preferred when accepting assocations. The “Preferred Calling AE Title” concept does not prohibit accepting associations from unlisted AEs.
The “Network Connection Reference” is a link to a separate Network Connection object. The referenced Network Connection object is a sibling the AE object (i.e., both are children of the same Device object).
Table H.1-5 Child Objects of Network AE Object
|Transfer Capability||1..N||The Transfer Capabilities for this Network AE. See Section H.1.4|