Files
UA-.NETStandard/docs/AI.md
T
Marc Schier 2836da7ec8 Fix sessionless ResultTransfer ownership bypass and other issues. (#4834)
# Description

Correct ownership, endpoint validation, policy propagation, subscription
delivery, file handling and generated-model behavior across the stack,
tools and samples. Add focused regression tests and update the
corresponding guides and sample documentation.

### Previously included corrections

- Require an active, matching session to generate or access transient
ResultTransfer file handles. Cover both sessionless generation and reads
against a handle owned by an active session, using live session owners
in the Machinery tests.
- Keep physical filesystem operations within their configured mount and
apply the same confinement checks throughout file operations.
- Validate LDS semaphore paths consistently during server registration
and registration-store maintenance.

### Individual issues addressed

| # | Component | Issue and correction |
|---|---|---|
| 1 | AI jobs and transfers | Jobs and transfers did not consistently
retain their creator's identity and session. Apply ownership checks to
descendants, file handles, subscriptions and execution, and recheck
deployment permissions before dispatch. |
| 2 | Password-management client | Password-bearing calls could use
signing-only channels or follow a replacement connection. Capture an
encrypted transport generation and keep dispatch bound to it; preserve
ordinary non-password edits. |
| 3 | GDS and certificate-push clients | Connections omitted hostname
verification. Validate the original configured DNS name or IP address
before session activation. |
| 4 | Certificate push | Private-key uploads could use signing-only
calls. Require an encrypted, generation-bound dispatch while preserving
certificate-only updates and restoring the caller's identity afterward.
|
| 5 | MQTT client | The .NET Framework custom-trust callback could
discard TLS hostname, certificate-availability and usage errors. Retain
those checks while supporting configured issuer trust. |
| 6 | DTLS handshake | Certificate trust was not tied to the configured
peer address. Match the certificate's DNS or IP identity to the intended
endpoint. |
| 7 | Replicated address spaces | Serialized nodes lost per-node and
descendant permission metadata. Preserve role permissions, user-role
permissions and access restrictions, including updates to existing
replica nodes. |
| 8 | MCP PubSub imports | Imports without groups skipped checks on the
effective broker destination. Check the actual endpoint before resolving
credentials or activating the connection. |
| 9 | Reference-server accounts | A disabled username account could
authenticate again with its previous roles. Reject disabled accounts
during fresh authentication. |
| 10 | Console reference client | The sample disabled hostname checks
when connecting to an otherwise trusted peer. Retain the original
requested host and validate it before activation. |
| 11 | Capture replay and export | Replay and raw export could accept
non-capture files or include key material. Require complete PCAP/PCAPNG
containers and exclude key sidecars and decryption-secret blocks. |
| 12 | PubSub adapter fallback | The fallback client configuration
automatically accepted peer certificates. Apply normal trust and
hostname validation before activation or reads. |
| 13 | Kafka transport | Explicit TLS enablement was checked but did not
reach both final Confluent configurations. Use the same effective
protocol for validation, producers and consumers. |
| 14 | PubSub actions | Configuration rebuilds could widen a
connection-local action handler's scope. Preserve its original
connection association and reject mismatched dispatch. |
| 15 | PubSub readers | Reader-level message-protection settings were
accepted but ignored. Apply the effective group and reader settings
before accepting and publishing received values. |
| 16 | PubSub key groups | Different `SecurityGroupId` values could
share one connection-wide key context. Reject mixed groups on a
connection and require separate connections for distinct groups. |
| 17 | MCP session registrations | Session-name replacement or reuse
could retain another registration's credential bindings. Bind access to
the registration, caller and authenticated endpoint, and preserve that
identity when borrowing sessions. |
| 18 | Viewer HTTP host | Requests reached the viewer's OPC UA session
without consistent Host, Origin and port checks. Validate the request
destination and browser origin before using the session, while retaining
supported local MCP clients. |
| 19 | Vision file operations | File operations did not consistently
apply protected-file checks, and remote handles lacked caller and
connection context. Apply the shared checks and use host-side opaque
handles bound to caller, target and generation. |
| 20 | DTLS record integrity | The integrity-only MAC used a truncated
sequence number. Authenticate the full reconstructed sequence number and
epoch so records remain distinct across rollover. |
| 21 | AMB client sample | Connection setup omitted hostname validation.
Preserve the originally requested host and verify the peer identity
before activation. |
| 22 | Robot sample writes | The R2 `SpeedOverride` callback could
target R1 state. Bind each callback to its own robot and apply that
robot's write policy. |
| 23 | AI result properties | Optional result children inherited
remotely writable defaults. Preserve their declaration restrictions and
keep server-produced results read-only. |
| 24 | WSS peer-trust updates | Existing channels did not consistently
respond to peer-trust changes. Revalidate complete chains for forward
and reverse WSS channels and close only those that no longer validate. |
| 25 | GDS revocation checks | Caller-provided certificates could cause
issuer retrieval from embedded URLs. Resolve validation from configured
local trust, issuers and CRLs without fetching caller-provided
locations. |
| 26 | GMS observations | Published correction observations retained
writable model defaults. Reject remote writes while preserving
publisher-side updates. |
| 27 | Production-dataset monitoring | Subscription admission and
delivery could use the reporter's context instead of each subscriber's
permissions. Evaluate the subscriber at admission and on every delivery,
including cancellation and disposal paths. |
| 28 | WoT MQTT destinations | Hostless MQTT forms could imply a
localhost destination before loopback checks. Reject them before
credential lookup or connection attempts and validate the effective
endpoint. |
| 29 | XRegistry opaque reads | Content-ID reads and notifications did
not consistently honor encrypted-read requirements or the currently
accepted transport. Recheck the bound endpoint and reject transport
downgrades before rebinding, including when protected values are already
queued. |
| 30 | PubSub capture dissection | Key loading did not consistently
check the configured capture-root boundary. Check each actual key path
immediately before opening it. |
| 31 | PubSub publication queues | Imported WriterGroup queues were not
fully checked against publish-topic grants. Check the destination
actually used by each group. |
| 32 | MCP PubSub mutations | A caller-supplied mode could select
subscribe grants for an operation that publishes. Derive the required
direction and parent context from the actual mutation. |
| 33 | Generated write masks | Model import and generation could widen
an explicit `UserWriteMask`. Preserve it through import, copy, merge,
inheritance and dependency metadata. |
| 34 | Generated method flags | An explicit `UserExecutable=false` could
be lost. Preserve its specified state and resulting method behavior
through the same model paths. |
| 35 | Generated role identifiers | Unresolved role identifiers could
cause permission entries to be omitted. Preserve namespace-qualified
role IDs and report a diagnostic when a policy cannot be represented. |
| 36 | Aggregation-server defaults | The `localhost` default did not
reliably constrain listener binding. Use numeric loopback for the
default endpoint and command-line fallback. |
| 37 | Certificate-validation cache | Cached results could skip current
leaf or issuer validity checks. Recheck validity windows on cache hits
and keep hostname validation independent of cached chain trust. |
| 38 | Software-update folders | Revision names and marker contents
containing dot segments could select paths outside the software root.
Normalize and check every derived path against that root. |
| 39 | USDA arrays | Array elements were not encoded for their string or
asset context. Escape them as data and preserve valid composition and
round-trip behavior. |
| 40 | Adapter hot reload | A changed dataset definition with the same
name could keep old fields, subscriptions or cached values active.
Compare complete immutable definitions and retire old state before
replacement. |
| 41 | Adapter index ranges | Subscription publication could ignore
`IndexRange` and return the complete value. Preserve the requested
projection and its status and timestamps; reject unsupported range
providers. |
| 42 | PubSub metadata and targets | Metadata from one connection could
change another connection's target mapping. Scope metadata to its
connection and provenance, and resolve targets using actual typed field
IDs rather than field names or unintended positional fallback. |
| 43 | Scales product locks | Product locks were not applied across
every remote mutation path. Apply them consistently to value writes,
filling calculations and related recipe/controller operations while
retaining permitted updates. |
| 44 | Event permission caching | Cached event decisions could outlive
identity, role or node-policy changes. Revalidate the current
subscriber, event type and source permissions instead of reusing a stale
decision. |
| 45 | WoT Modbus destinations | Hostless Modbus forms could imply
localhost before loopback checks. Reject them before connecting and
validate the effective endpoint. |
| 46 | MCP local PKI tools | Peer-trust mutations did not consistently
require the caller's `CertificateAdministration` grant. Check the
capability before trust and untrust operations. |
| 47 | Robot-control HTTP bridge | The bridge lacked consistent Host,
Origin and port validation and caller-specific session grants. Apply
those checks before borrowing the OPC UA session and retain supported
local clients. |
| 48 | Subscription transfers | Transferred subscriptions could retain
cached notifications after the destination's permissions changed.
Require authorization continuity between source and destination
identities and roles, invalidate stale retransmission data when
continuity fails, and preserve retransmission behavior for compatible
transfers. |

### Compatibility notes

- Replication uses the versioned NSRP v1 policy envelope. Upgrade peers
together and re-encode or reseed legacy topology from the authoritative
model; missing permission metadata is not inferred from old records.
- Integrity-only DTLS peers must be upgraded together for the full
sequence/epoch MAC. AEAD behavior is unchanged.
- Distinct PubSub key groups require separate connections.
- Custom sessions that cannot capture the actual encrypted transport,
and subscription providers that cannot honor a requested range, are
rejected rather than silently changing the requested behavior.
- Subscription transfers retain retransmission data only when the
destination authorization remains compatible with the source snapshot;
otherwise the old sequence numbers and cached data are invalidated.

## Related Issues

No separate tracking issue is linked. The individual corrections are
listed above.

## Checklist

_Put an `x` in the boxes that apply. You can complete these step by step
after opening the PR._

- [ ] I have signed the
[CLA](https://opcfoundation.org/license/cla/ContributorLicenseAgreementv1.0.pdf)
and read the
[CONTRIBUTING](https://github.com/OPCFoundation/UA-.NETStandard/blob/master/CONTRIBUTING.md)
doc.
- [x] I have added tests that prove my fix is effective or that my
feature works and increased code coverage.
- [ ] I have added all necessary documentation.
- [x] I have verified that my changes do not introduce (new) build or
analyzer warnings.
- [ ] I ran **all** tests locally using the **UA.slnx** solution against
at least .net **framework** and .net **10**, and all passed.
- [ ] I fixed **all** failing and flaky tests in the CI pipelines and
**all** CodeQL warnings.
- [ ] I have addressed **all** PR feedback received.
2026-10-21 05:37:29 +02:00

13 KiB

AI Model Management developer guide

The Opc.Ua.AI, Opc.Ua.AI.Server, Opc.Ua.AI.Client, and Opc.Ua.AI.Inference packages implement the draft OPC UA — AI Model Management and Inference companion specification in .NET.

Draft. The namespace http://opcfoundation.org/UA/AI/ and every NodeId in it are provisional until the working group publishes the specification.

AI Model Management exposes model sources, models, datasets, deployments, and inference methods through OPC UA. Clients can discover available resources and read provenance and trust-boundary metadata. They can also invoke Invoke or InvokeAsync and transfer large artefacts with standard file-transfer types.

Contents

Packages

Package What it gives you Depends on
OPCFoundation.NetStandard.Opc.Ua.AI Source-generated AI model — ObjectTypes, ReferenceTypes, DataTypes, enums, node states and model loader Opc.Ua.Core
OPCFoundation.NetStandard.Opc.Ua.AI.Server AINodeManager, AIOptions, fallback reporting, transfer and job support, and AddAI hosting extensions Opc.Ua.AI, Opc.Ua.Server, Opc.Ua.AI.Inference
OPCFoundation.NetStandard.Opc.Ua.AI.Client AIClient, AIClientFactory and AddAIClient() DI registration Opc.Ua.AI, Opc.Ua.Client
OPCFoundation.NetStandard.Opc.Ua.AI.Inference IInferenceBackend, ChatClientInferenceBackend, RestChatCompletionsBackend, credential resolvers and backend options Opc.Ua.AI, Microsoft.Extensions.AI

The AI libraries target modern .NET TFMs used by the sample (net8.0, net9.0 and net10.0). The inference assembly intentionally has no Azure, OpenAI or other vendor SDK dependency.

Model

The Server publishes one AI root below the Server object. The root contains:

  • Model sources
  • Deployments
  • Models
  • Datasets
  • Jobs

Each deployment describes where inference runs and identifies its model source. It also records egress permission, input-retention status, and the maximum inline payload size.

Two properties are especially important:

  • An inference result includes ModelUsed, so callers can tell whether the primary model or a degraded fallback answered.
  • CredentialReference is a name only. An ICredentialResolver resolves the credential value inside the Server process. The address space contains only the reference name, never the credential value.

Large payloads use the standard Part 5 FileType transfer flow. Asynchronous inference jobs use the Part 10 program lifecycle so clients can monitor state instead of polling a private API.

Minimal hosted server

AddAI registers the node manager, options and default backend composition. The host supplies the IChatClient through IChatClientFactory; that keeps vendor packages in the host and out of Opc.Ua.AI.Inference.

using Microsoft.Extensions.Hosting;
using Opc.Ua.AI.Inference;
using Opc.Ua.AI.Server;
using Opc.Ua.AI.Server.Hosting;
using Opc.Ua.Server.Fluent;

HostApplicationBuilder builder = Host.CreateApplicationBuilder(args);

builder.Services.AddRestChatCompletionsAIChatClientFactory();

builder.Services
    .AddOpcUa()
    .AddServer(options =>
    {
        options.ApplicationName = "AIServer";
        options.ApplicationUri = "urn:localhost:OPCFoundation:AIServer";
        options.AutoAcceptUntrustedCertificates = true;
        options.EndpointUrls.Add("opc.tcp://localhost:62640/AIServer");
    })
    .AddAI(
        ai => builder.Configuration.GetSection(AIOptions.SectionName).Bind(ai),
        backend => builder.Configuration
            .GetSection(InferenceBackendOptions.SectionName)
            .Bind(backend),
        fallback => builder.Configuration
            .GetSection(InferenceBackendOptions.FallbackSectionName)
            .Bind(fallback));

using IHost app = builder.Build();
await app.RunAsync().ConfigureAwait(false);

AddRestChatCompletionsAIChatClientFactory() is the sample-friendly factory: it creates an IChatClient over the configured OpenAI-compatible endpoint without adding a vendor SDK. A production host can instead register its own IChatClientFactory. That factory can create IChatClient instances for Azure, OpenAI, Ollama, or an on-device runtime.

The direct construction path remains available for hosts that do not use the generic hosting stack:

var backends = new InferenceBackends(primaryBackend, fallbackBackend);
var factory = new AINodeManagerFactory(
    backends,
    Options.Create(new AIOptions()),
    Options.Create(new InferenceBackendOptions()));

Hosting API

The extension method on IOpcUaServerBuilder is:

Method Purpose
AddAI(Action<AIOptions>?, Action<InferenceBackendOptions>?, Action<InferenceBackendOptions>?) Registers AINodeManagerFactory, AIOptions, primary and fallback InferenceBackendOptions, an InferenceBackends singleton, and the OPC UA node-manager registration

AddAI composes the backend from InferenceBackendOptions.Kind:

  • ChatClient (default) creates ChatClientInferenceBackend from IChatClientFactory.
  • RestChatCompletions creates RestChatCompletionsBackend directly for endpoints whose wire contract is the OpenAI-compatible REST shape.

AIOptions

Property Purpose
PrimaryDeploymentId / FallbackDeploymentId Deployment identifiers published in the address space
EnableFallback Publishes the fallback deployment and FallsBackTo reference
EnableCatalogue Publishes catalogue and import-job nodes
EnableLearningLoop Publishes a LearningJobType node for ground-truth sample accounting
TransferExpiry, MaxTransferSize, MaxConcurrentTransfers, TransferInferenceTimeout Bounds for chunked transfers
AsyncInferenceDelay, MaxRetainedJobs Bounds and timing for asynchronous inference jobs
SourceId Identifier of the model source

When EnableLearningLoop is true, AINodeManager publishes one LearningJobType under LearningJobs. Host-level coordinators report ground-truth corrections through RecordLearningSampleAsync(sampleId, sampleKind). The stable sampleId makes retries idempotent, and AILearningSampleKind.Negative counts empty or retracted observations exactly as positive examples count.

InferenceBackendOptions

Property Purpose
Enabled Enables the backend; most useful for disabling fallback
Kind ChatClient or RestChatCompletions
EndpointUri, ChatCompletionsPath, ProbePath Endpoint and paths for REST-shaped clients
Authentication, CredentialReference, ApiKeyHeader, CredentialDirectory, TokenAudience Server-to-backend authentication
Site, DataJurisdiction, EgressPermitted, RetainsInput Trust-boundary metadata published to clients
MaxInlinePayloadSize UInt32 inline Invoke payload limit; zero permits only an explicitly chosen transfer
Models Configured model catalogue entries

Client surface

AddAIClient() mirrors the other companion-family client extensions. It registers an AIClientFactory and a Func<CancellationToken, Task<AIClient?>> over the managed session.

using Microsoft.Extensions.DependencyInjection;
using Microsoft.Extensions.Hosting;
using Opc.Ua;
using Opc.Ua.AI.Client;
using Opc.Ua.Client;

HostApplicationBuilder builder = Host.CreateApplicationBuilder(args);

builder.Services
    .AddOpcUa()
    .AddClient(options =>
    {
        options.ApplicationName = "AIClient";
        options.ApplicationUri = "urn:localhost:OPCFoundation:AIClient";
        options.AutoAcceptUntrustedCertificates = true;
    })
    .AddDiscoveryAndConnect(options =>
    {
        options.DiscoveryUrl = "opc.tcp://localhost:62640/ModelManagementServer";
        options.SecurityMode = MessageSecurityMode.SignAndEncrypt;
        options.SecurityPolicyUri = SecurityPolicies.Basic256Sha256;
    })
    .AddAIClient();

using IHost app = builder.Build();
await app.StartAsync().ConfigureAwait(false);

var createClient = app.Services
    .GetRequiredService<Func<CancellationToken, Task<AIClient?>>>();
AIClient? client = await createClient(CancellationToken.None)
    .ConfigureAwait(false);

if (client is null)
{
    Console.WriteLine("The Server does not implement AI Model Management.");
}

For one-off code, AIClient.TryCreate(session) is the direct fallback when you already own an ISession.

Inference backends

IInferenceBackend is the server-side contract: list models, invoke a model and probe reachability. Two implementations ship:

  • ChatClientInferenceBackend wraps Microsoft.Extensions.AI.IChatClient. This is the default. Hosts can pair it with any SDK or local runtime that implements the abstraction. The OPC UA address space stays unchanged.
  • RestChatCompletionsBackend speaks the OpenAI-compatible REST chat-completions contract directly. Use it when that REST shape is the actual wire contract and no IChatClient is available.

Both hosted and on-device deployments use the same OPC UA nodes. Their configuration identifies the endpoint, credentials, data jurisdiction, and egress.

Invocation inputs and parameters

Invoke and InvokeAsync accept an inline Payload or a PayloadUri, but the current server accepts inline payloads only. It returns BadNotSupported for URI-only input rather than accepting it and running a backend with no request body.

Inference transfers belong to their creating session and identity. Every file operation, including a new Open, checks that ownership; a file handle alone is not authority. Execute also rechecks the original deployment and invocation method's current permissions before backend dispatch. Authenticated job owners can recover their retained jobs after reconnect within the same stable identity domain; anonymous jobs remain session-bound. Other callers cannot read or modify their payloads or receive their notifications. Server-produced response and provenance properties remain read-only even to the owner.

Both built-in backends accept these parameters:

  • temperature: 0 through 2
  • max_tokens: positive integer
  • top_p: 0 through 1

Clients can provide values as strings, built-in integer or floating-point values, or booleans. Both backends convert values using the invariant culture and forward them through these execution paths:

  • Synchronous and asynchronous calls
  • Fallback execution
  • Oversized-transfer execution

Both backends reject malformed or unsupported parameters. In the REST chat-completions backend, an explicit OPC UA parameter overrides the matching field in the JSON request body. The backend preserves body fields without a matching parameter.

The server sets SpecificationVersion from the source-generated Opc.Ua.AI.ModelVersions.Target constant. The AI NodeSet's target model version determines this constant, so updating the NodeSet also updates the published version without a separately maintained literal.

Example

The sample in samples/AI/ModelManagementServer hosts the node manager with AddAI. By default it uses the ChatClient path and the sample composition root supplies a small IChatClient over the OpenAI-compatible endpoint. verify_backend.py is a throwaway endpoint that speaks enough of that contract for local validation:

python samples/AI/verify_backend.py 5273
dotnet run --project samples/AI/ModelManagementServer
dotnet run --project samples/AI/ModelManagementClient

Set InferenceBackend__Kind=RestChatCompletions to select the REST backend for an endpoint that requires direct REST access. Configure FallbackInferenceBackend__Kind independently when the fallback uses a different wire contract from the primary.

Limitations

  • The companion specification is a draft, so namespace URIs and NodeIds can change.
  • The sample publishes a real LearningJobType instance and a real SamplesCollected counter. Host-level code can call the server-side accounting API when ground-truth corrections arrive, including empty or retracted observations. The sample does not simulate retraining, candidate generation, or promotion.
  • IChatClient has no standard model-enumeration method, so hosts that need a catalogue should configure InferenceBackendOptions.Models.
  • The libraries do not reference vendor SDKs. If your hosting application needs a provider package, add it there and expose it through IChatClientFactory.
  • The AI inference and sample projects disable Native AOT because the Microsoft.Extensions.AI ecosystem uses reflection in areas this repository builds with warnings as errors.

See also