This ObjectTyperepresents the logical interface of a Deviceto a Network. A specific subtype shall be defined for each protocol. Figure 20shows the ConnectionPointTypeincluding some specific types.

Figure 20– Example of ConnectionPointType hierarchy

A Devicecan have more than one such interface to the same or to different Networks. Different interfaces usually exist for different protocols. Figure 21shows the ConnectionPointTypecomponents. It is formally defined in Table 41.

Figure 21– ConnectionPointType

Table 41– ConnectionPointType definition

Attribute	Value
BrowseName	ConnectionPointType
IsAbstract	True
References	NodeClass	BrowseName	DataType	TypeDefinition	Other
Subtype of the TopologyElementType defined in 4.2.
0:HasComponent	Object	NetworkAddress		FunctionalGroupType	M
0:HasComponent	Object	<ProfileIdentifier>		ProtocolType	MP
ConnectsTo	Object	<NetworkIdentifier>		NetworkType	OP
Conformance Units
DI ConnectionPoint

ConnectionPointsare components of a Device, represented by a subtype of ComponentType. To allow navigation from a Networkto the connected Devices, the ConnectionPointsshall have the inverse Reference (ComponentOf)to the Device.

ConnectionPointshave Propertiesand other components that they inherit from the TopologyElementType.

The NetworkAddress FunctionalGroupincludes all Parametersneeded to specify the protocol-specific address information of the connected Device. These Parametersmay be components of the NetworkAddress FunctionalGroup, of the ParameterSet, or another Object.

<ProfileIdentifier> identifies the Communication Profilethat this ConnectionPointsupports. ProtocolTypeand Communication Profileare defined in 5.2. It implies that this ConnectionPointcan be used to connect Networksand Devicesof the same Communication Profile.

ConnectionPointsare between a Networkand a Device. The location in the topology is configured by means of the ConnectsTo ReferenceType. Figure 22illustrates some usage models.

Figure 22– ConnectionPoint usage