5.8 NodeManagement Service Set

5.8.1 Overview

This Service Set defines Services to add and delete AddressSpace Nodes and References between them. All added Nodes continue to exist in the AddressSpace even if the Client that created them disconnects from the Server.

Calls to NodeManagement Services may result in changes to the AddressSpace in addition to the requested change. The actual behaviour is Server specific.

5.8.2 AddNodes

5.8.2.1 Description

This Service is used to add one or more Nodes into the AddressSpace hierarchy. Using this Service, each Node is added as the TargetNode of a HierarchicalReference to ensure that the AddressSpace is fully connected and that the Node is added as a child within the AddressSpace hierarchy (see OPC 10000-3).

When a Server creates an instance of a TypeDefinitionNode it shall create the same hierarchy of Nodes beneath the new Object or Variable depending on the ModellingRule of each InstanceDeclaration. All Nodes with a ModellingRule of Mandatory shall be created or an existing Node shall be referenced that conforms to the InstanceDeclaration. The creation of Nodes with other ModellingRules is Server specific.

5.8.2.2 Parameters

Table 22 defines the parameters for the Service.

Table 22 – AddNodes Service Parameters
NameTypeDescription
Request

requestHeader

RequestHeaderCommon request parameters (see 7.32 for RequestHeader definition).

nodesToAdd []

AddNodesItemList of Nodes to add. All Nodes are added as a Reference to an existing Node using a hierarchical ReferenceType. This structure is defined in-line with the following indented items.

parentNodeId

Expanded NodeId

ExpandedNodeId of the parent Node for the Reference. The ExpandedNodeId type is defined in 7.16.

If the serverIndex indicates that the parent Node is a remote Node, then the nodeId shall contain the absolute namespace URI. If the parent Node is a local Node the nodeId shall contain the namespace index.

referenceTypeId

NodeId NodeId of the hierarchical ReferenceType to use for the Reference from the parent Node to the new Node.

requestedNewNodeId

Expanded NodeId

Client requested expanded NodeId of the Node to add. The serverIndex in the expanded NodeId shall be 0.

If the Server cannot use this NodeId, it rejects this Node and returns the appropriate error code.

If the Client does not want to request a NodeId, then it sets the value of this parameter to the null expanded NodeId.

If the Node to add is a ReferenceType Node, its NodeId should be a numeric id. See OPC 10000-3 for a description of ReferenceType NodeIds.

browseName

QualifiedNameThe browse name of the Node to add.

nodeClass

NodeClass NodeClass of the Node to add.

nodeAttributes

Extensible Parameter

NodeAttributes

The Attributes that are specific to the NodeClass. The NodeAttributes parameter type is an extensible parameter type specified in 7.24.

A Client is allowed to omit values for some or all Attributes. If an Attribute value is null, the Server shall use the default values from the TypeDefinitionNode. If a TypeDefinitionNode was not provided the Server shall choose a suitable default value.

The Server may still add an optional Attribute to the Node with an appropriate default value even if the Client does not specify a value.

typeDefinition

Expanded NodeId

NodeId of the TypeDefinitionNode for the Node to add. This parameter shall be null for all NodeClasses other than Object and Variable in which case it shall be provided.

If the serverIndex indicates that the type definition Node is a remote Node, then the nodeId shall contain the absolute namespace URI. If the type definition Node is a local Node the nodeId shall contain the namespace index.

Response

responseHeader

Response HeaderCommon response parameters (see 7.33 for ResponseHeader definition).

results []

AddNodesResultList of results for the Nodes to add. The size and order of the list matches the size and order of the nodesToAdd request parameter. This structure is defined in-line with the following indented items.

statusCode

StatusCode StatusCode for the Node to add (see 7.38 for StatusCode definition).

addedNodeId

NodeId Server assigned NodeId of the added Node. Null NodeId if the operation failed.

diagnosticInfos []

DiagnosticInfoList of diagnostic information for the Nodes to add (see 7.12 for DiagnosticInfo definition). The size and order of the list matches the size and order of the nodesToAdd request parameter. This list is empty if diagnostics information was not requested in the request header or if no diagnostic information was encountered in processing of the request.
5.8.2.3 Service results

Table 23 defines the Service results specific to this Service. Common StatusCodes are defined in Table 178.

Table 23 – AddNodes Service Result Codes
Symbolic IdDescription
Bad_NothingToDoSee Table 178 for the description of this result code.
Bad_TooManyOperationsSee Table 178 for the description of this result code.
5.8.2.4 StatusCodes

Table 24 defines values for the operation level statusCode parameter that are specific to this Service. Common StatusCodes are defined in Table 179.

Table 24 – AddNodes Operation Level Result Codes
Symbolic IdDescription
Bad_ParentNodeIdInvalidThe parent node id does not to refer to a valid node.
Bad_ReferenceTypeIdInvalidSee Table 179 for the description of this result code.
Bad_ReferenceNotAllowedThe reference could not be created because it violates constraints imposed by the data model.
Bad_NodeIdRejectedThe requested node id was rejected either because it was invalid or because the Server does not allow node ids to be specified by the Client.
Bad_NodeIdExistsThe requested node id is already used by another node.
Bad_NodeClassInvalidSee Table 179 for the description of this result code.
Bad_BrowseNameInvalidSee Table 179 for the description of this result code.
Bad_BrowseNameDuplicatedThe browse name is not unique among nodes that share the same relationship with the parent.
Bad_NodeAttributesInvalidThe node Attributes are not valid for the node class.
Bad_TypeDefinitionInvalidSee Table 179 for the description of this result code.
Bad_UserAccessDeniedSee Table 178 for the description of this result code.

5.8.3 AddReferences

5.8.3.1 Description

This Service is used to add one or more References to one or more Nodes. The NodeClass is an input parameter that is used to validate that the Reference to be added matches the NodeClass of the TargetNode. This parameter is not validated if the Reference refers to a TargetNode in a remote Server.

In certain cases, adding new References to the AddressSpace shall require that the Server add new Server ids to the Server’s ServerArray Variable. For this reason, remote Servers are identified by their URI and not by their ServerArray index. This allows the Server to add the remote Server URIs to its ServerArray.

5.8.3.2 Parameters

Table 25 defines the parameters for the Service.

Table 25 – AddReferences Service Parameters
NameTypeDescription
Request

requestHeader

Request HeaderCommon request parameters (see 7.32 for RequestHeader definition).

referencesToAdd []

AddReferences ItemList of Reference instances to add to the SourceNode. The targetNodeClass of each Reference in the list shall match the NodeClass of the TargetNode. This structure is defined in-line with the following indented items.

sourceNodeId

NodeId NodeId of the Node to which the Reference is to be added. The source Node shall always exist in the Server to add the Reference. The isForward parameter can be set to FALSE if the target Node is on the local Server and the source Node on the remote Server.

referenceTypeId

NodeId NodeId of the ReferenceType that defines the Reference.

isForward

BooleanIf the value is TRUE, the Server creates a forward Reference. If the value is FALSE, the Server creates an inverse Reference.

targetServerUri

StringURI of the remote Server. If this parameter is not null or empty, it overrides the serverIndex in the targetNodeId.

targetNodeId

Expanded NodeId

Expanded NodeId of the TargetNode. The ExpandedNodeId type is defined in 7.16.

If the serverIndex indicates that the TargetNode is a remote Node, then the nodeId shall contain the absolute namespace URI. If the TargetNode is a local Node the nodeId shall contain the namespace index.

targetNodeClass

NodeClass NodeClass of the TargetNode. The Client shall specify this since the TargetNode might not be accessible directly by the Server.
Response

responseHeader

Response HeaderCommon response parameters (see 7.33 for ResponseHeader definition).

results []

StatusCodeList of StatusCodes for the References to add (see 7.38 for StatusCode definition). The size and order of the list matches the size and order of the referencesToAdd request parameter.

diagnosticInfos []

Diagnostic InfoList of diagnostic information for the References to add (see 7.12 for DiagnosticInfo definition). The size and order of the list matches the size and order of the referencesToAdd request parameter. This list is empty if diagnostics information was not requested in the request header or if no diagnostic information was encountered in processing of the request.
5.8.3.3 Service results

Table 26 defines the Service results specific to this Service. Common StatusCodes are defined in Table 178.

Table 26 – AddReferences Service Result Codes
Symbolic IdDescription
Bad_NothingToDoSee Table 178 for the description of this result code.
Bad_TooManyOperationsSee Table 178 for the description of this result code.
5.8.3.4 StatusCodes

Table 27 defines values for the results parameter that are specific to this Service. Common StatusCodes are defined in Table 179.

Table 27 – AddReferences Operation Level Result Codes
Symbolic IdDescription
Bad_SourceNodeIdInvalidSee Table 179 for the description of this result code.
Bad_ReferenceTypeIdInvalidSee Table 179 for the description of this result code.
Bad_ServerUriInvalidSee Table 178 for the description of this result code.
Bad_TargetNodeIdInvalidSee Table 179 for the description of this result code.
Bad_NodeClassInvalidSee Table 179 for the description of this result code.
Bad_ReferenceNotAllowedThe reference could not be created because it violates constraints imposed by the data model on this Server.
Bad_ReferenceLocalOnlyThe reference type is not valid for a reference to a remote Server.
Bad_UserAccessDeniedSee Table 178 for the description of this result code.
Bad_DuplicateReferenceNotAllowedThe reference type between the nodes is already defined.
Bad_InvalidSelfReferenceThe Server does not allow this type of self reference on this node.

5.8.4 DeleteNodes

5.8.4.1 Description

This Service is used to delete one or more Nodes from the AddressSpace.

When any of the Nodes deleted by an invocation of this Service is the TargetNode of a Reference, then those References are left unresolved based on the deleteTargetReferences parameter.

Servers may delete additional Nodes and References like child Nodes that exist based on a TypeDefinition. The behaviour is Server specific.

When any of the Nodes deleted by an invocation of this Service is being monitored, then a Notification containing the status code Bad_NodeIdUnknown is sent to the monitoring Client indicating that the Node has been deleted.

5.8.4.2 Parameters

Table 28 defines the parameters for the Service.

Table 28 – DeleteNodes Service Parameters
NameTypeDescription
Request

requestHeader

Request HeaderCommon request parameters (see 7.32 for RequestHeader definition).

nodesToDelete []

DeleteNodes ItemList of Nodes to delete. This structure is defined in-line with the following indented items.

nodeId

NodeId NodeId of the Node to delete.

deleteTargetReferences

Boolean

A Boolean parameter with the following values:

TRUE delete References in TargetNodes that Reference the Node to delete.

FALSE delete only the References for which the Node to delete is the source.

The Server cannot guarantee that it is able to delete all References from TargetNodes if this parameter is TRUE.

Response

responseHeader

Response HeaderCommon response parameters (see 7.33 for ResponseHeader definition).

results []

StatusCodeList of StatusCodes for the Nodes to delete (see 7.38 for StatusCode definition). The size and order of the list matches the size and order of the list of the nodesToDelete request parameter.

diagnosticInfos []

Diagnostic InfoList of diagnostic information for the Nodes to delete (see 7.12 for DiagnosticInfo definition). The size and order of the list matches the size and order of the nodesToDelete request parameter. This list is empty if diagnostics information was not requested in the request header or if no diagnostic information was encountered in processing of the request.
5.8.4.3 Service results

Table 29 defines the Service results specific to this Service. Common StatusCodes are defined in Table 178.

Table 29 – DeleteNodes Service Result Codes
Symbolic IdDescription
Bad_NothingToDoSee Table 178 for the description of this result code.
Bad_TooManyOperationsSee Table 178 for the description of this result code.
5.8.4.4 StatusCodes

Table 30 defines values for the results parameter that are specific to this Service. Common StatusCodes are defined in Table 179.

Table 30 – DeleteNodes Operation Level Result Codes
Symbolic IdDescription
Bad_NodeIdInvalidSee Table 179 for the description of this result code.
Bad_NodeIdUnknownSee Table 179 for the description of this result code.
Bad_UserAccessDeniedSee Table 178 for the description of this result code.
Bad_NoDeleteRightsSee Table 179 for the description of this result code.
Uncertain_ReferenceNotDeletedThe Server was not able to delete all target references.

5.8.5 DeleteReferences

5.8.5.1 Description

This Service is used to delete one or more References of a Node.

When any of the References deleted by an invocation of this Service are contained in a View, then the ViewVersion Property is updated if this Property is supported.

Table 31 defines the parameters for the Service.

Table 31 – DeleteReferences Service Parameters
NameTypeDescription
Request

requestHeader

RequestHeaderCommon request parameters (see 7.32 for RequestHeader definition).

referencesToDelete []

DeleteReferences ItemList of References to delete. This structure is defined in-line with the following indented items.

sourceNodeId

NodeId NodeId of the Node that contains the Reference to delete.

referenceTypeId

NodeId NodeId of the ReferenceType that defines the Reference to delete.

isForward

BooleanIf the value is TRUE, the Server deletes a forward Reference. If the value is FALSE, the Server deletes an inverse Reference.

targetNodeId

ExpandedNodeId

NodeId of the TargetNode of the Reference.

If the Server index indicates that the TargetNode is a remote Node, then the nodeId shall contain the absolute namespace URI. If the TargetNode is a local Node the nodeId shall contain the namespace index.

deleteBidirectional

Boolean

A Boolean parameter with the following values:

TRUE delete the specified Reference and the opposite Reference from the TargetNode. If the TargetNode is located in a remote Server, the Server is permitted to delete the specified Reference only.

FALSE delete only the specified Reference.

Response

responseHeader

ResponseHeaderCommon response parameters (see 7.33 for ResponseHeader definition).

results []

StatusCodeList of StatusCodes for the References to delete (see 7.38 for StatusCode definition). The size and order of the list matches the size and order of the referencesToDelete request parameter.

diagnosticInfos []

DiagnosticInfoList of diagnostic information for the References to delete (see 7.12 for DiagnosticInfo definition). The size and order of the list matches the size and order of the referencesToDelete request parameter. This list is empty if diagnostics information was not requested in the request header or if no diagnostic information was encountered in processing of the request.
5.8.5.2 Service results

Table 32 defines the Service results specific to this Service. Common StatusCodes are defined in Table 178.

Table 32 – DeleteReferences Service Result Codes
Symbolic IdDescription
Bad_NothingToDoSee Table 178 for the description of this result code.
Bad_TooManyOperationsSee Table 178 for the description of this result code.
5.8.5.3 StatusCodes

Table 33 defines values for the results parameter that are specific to this Service. Common StatusCodes are defined in Table 179.

Table 33 – DeleteReferences Operation Level Result Codes
Symbolic IdDescription
Bad_SourceNodeIdInvalidSee Table 179 for the description of this result code.
Bad_ReferenceTypeIdInvalidSee Table 179 for the description of this result code.
Bad_ServerIndexInvalidThe Server index is not valid.
Bad_TargetNodeIdInvalidSee Table 179 for the description of this result code.
Bad_UserAccessDeniedSee Table 178 for the description of this result code.
Bad_NoDeleteRightsSee Table 179 for the description of this result code.