Intent-Based Orchestration identity
Multi-Domain Intent
Intent considered across more than one management or administrative domain.
Why this identity matters
A bounded technical reference
It provides a bounded identity for cross-domain intent context while leaving decomposition, coordination, and implementation choices to applicable architectures.
This domain provides semantic identity and public orientation. It is not an agent, workload, intent-management system, controller, platform, operational service, API endpoint, or standards authority.
Identity family
End-to-End Intent context
This identity is part of the End-to-End Intent identity family.
Authoritative context
Evidence boundary
ETSI ZSM describes horizontal end-to-end aspects across domains and technologies; TM Forum intent material supplies complementary autonomous-network context. Evidence: C for the exact LJP term.
- 3GPP TS 28.312 — Management and orchestration; Intent driven management services for mobile networks — 3GPP
- ETSI GS ZSM 016 V1.1.1 — Intent-driven Closed Loops — ETSI
- TM Forum Intent toolkit — TM Forum
The sources explain their own technical material. They do not endorse LJP, this domain, a buyer, or an implementation.
Strategic inquiry
Discuss this identity
For licensing, stewardship, partnership, acquisition, or technical-context discussion.
Strategic Inquiry