I want to be precise about the provenance here, because the sequence is the point. I argued at DTW Ignite that the API is not enough, that the interfaces we built for developer access were never designed to let an autonomous agent understand what it is acting on. I argued a few weeks later that the agent runtime is not the agent model, that a place to execute an agent and put guardrails around it supplies none of the topology, ontology, authority and audit that coordination between agents actually needs. NGMN has now enumerated eight cross-organisation challenge areas, and they map almost one for one onto that case. Lack of standards for agent knowledge and context sharing. Incomplete information modelling for networks. Lack of end-to-end security, identity and trust for autonomous functions. Lack of operator-friendly governance and lifecycle tools. Under-addressed economic and organisational readiness. When a body chaired by Orange's group CTO writes the same list I published, the argument stops being a contrarian read and becomes the consensus. That is a good day for the thesis. It is a better day to point out the part the report does not solve.
The report describes coordination inside a boundary the operator owns
Look closely at the architecture NGMN proposes. A supervisory agent coordinates specialist agents, one each for RAN, core, transport, cloud and security, to diagnose a service problem, weigh corrective actions, resolve conflicts, and verify that service was restored. The worked examples are fault management, service assurance and RAN optimisation. In the RAN case, a cross-domain agent delegates intent to a RAN optimisation agent, which supervises a sub-agent in the infrastructure layer, and when an optimisation action collides with network-wide energy management the cross-domain agent arbitrates the trade-off. This is a serious and correct piece of engineering. It is also, in every example, coordination across domains that a single operator owns. RAN, core, transport, cloud and security are five administrative domains inside one company's walls. The hard thing NGMN is describing is getting an operator's own silos, built by different vendors with different data models, to hand each other a shared and trustworthy understanding of state. That is worth doing, and it is exactly why a runtime and a set of guardrails were never going to be enough. But it is one owner reconciling with itself.
The problem I have been pointing at sits one boundary further out, and NGMN's own scope is the clearest evidence that it is a distinct and harder problem. When an enterprise's AI wants to negotiate with an operator's network AI, for a service level, a slice, a capacity commitment, a remediation, there is no shared owner to impose a common ontology, no single authority to issue the identities, and no single audit log that both parties will accept as the record of what was agreed and who was answerable. Everything NGMN specifies, the semantic alignment, the zero-trust identities, the audit trail, is defined for agents operating within the operator's estate. Across an ownership boundary, the same requirements do not disappear. They get harder, because now two parties have to agree on the model before either can trust an action, and neither controls the other. NGMN has validated that the meta-model is necessary. It has not, and by its own framing could not, close the gap where the two hardest words in this whole subject live, which are coordination and accountability between parties who do not report to the same CTO.
Containment, coordination, accountability, in that order of difficulty
It is worth keeping the three layers separate, because vendors and now standards bodies keep collapsing them. Containment is the Zero-Trust Agent Ecosystem: the identity, the authorisation, the runtime monitoring, the kill switch that lets you revoke or quarantine an agent inside your own network. That is genuinely useful and NGMN is right to specify it in detail. Coordination is the shared ontology and semantic mapping that lets one agent understand what another agent is doing, and this is the layer NGMN is now trying to build across an operator's internal domains. Accountability is the ability to produce, on demand, the identity of an agent, the authority under which it acted, and a trail that a regulator and an outside counterparty would both sign, across a boundary you do not own. The industry has spent a year shipping the first layer and calling it the third. NGMN has now, to its credit, put real weight on the second. The third is still open, and it is the one I argued the EU AI Act made expensive when its enforcement powers switched on at the start of this month, because enforcement does not stop at the edge of your administrative domain.
There is a discipline point here that operators should not lose in the enthusiasm of seeing a favourite thesis ratified. NGMN itself flags it: "While technology groups focus on architecture, few have formal guidance on the required telco organisational changes," and it lists economic and organisational readiness as an under-addressed challenge in its own right. The meta-model is not a product you procure. It is a set of agreements about topology, ontology, authority and audit that has to be built and then adopted, and the report's call for alignment across seven standards organisations is a fair description of how long that takes. Cross-SDO harmonisation of information models is measured in years, not quarters. When I helped set network autonomy targets in operator programmes, the technology was rarely the thing that slipped. The organisational change and the cross-domain agreements were. Anyone booking autonomous-network savings against a framework paper rather than a ratified model is doing the same thing I warn against when vendors stack their individual efficiency claims into a total no network has ever achieved. Read this report as the industry agreeing on the destination. Do not read it as arrival.
What to watch
The honest test has not changed, and NGMN has now made it a formal requirement rather than a personal opinion. For any action an agent takes on its own, can you produce its identity, the authority under which it acted, and an audit trail that both a regulator and an outside counterparty would accept. If the answer lives entirely inside one vendor's runtime, you have containment and you should not mistake it for accountability. NGMN has described the plane the runtime runs on, in more detail than anyone in the industry has committed to print, and it has correctly located the work in standards and organisation rather than in any single box. The next phase belongs to whoever builds the ontology and the identity fabric that hold up not just across an operator's own domains, but across the boundary to the enterprise on the other side of the negotiation. That boundary is where the value is, and it is the one the report stops at. Watch for whether the alignment NGMN asks for actually happens across those seven bodies, and watch, as always, for a pilot inside one operator's walls being described as autonomy across everyone's.
No comments:
Post a Comment