← Catalogue
World Models · legacy example

Communications & Data Transmission

This meta-model describes communications as a service layer of the world: the radio spectrum bands and the grants that allocate them, the addressing and numbering resources that make endpoints reachable, the network services operators provide, the interconnection links that stitch networks together, and the aggregate traffic that flows across them. It is its own model because it manages scarce shared resources (spectrum, addresses, numbers) governed by registries, and its unit of flow is traffic measured in aggregates rather than discrete consignments.

AI YAMLAGENTS.mdSource
IDworld.f9-communications-and-data-transmission
Version history0.2.0-legacy
CategoryReference example
IndustryCross-industry
Domainflows-resources
Tagscommunications, data, transmission
Data structure

Bundles and layers

Bundle

spectrum

The shared radio resource

Layers

bandPlan`: frequency bands and their designated uses · `grantsAndLicences`: allocations of bands to operators with conditions and terms

Bundle

addressing

Making endpoints reachable

Layers

numberingPlans`: telephone numbering resources and their assignment · `ipAddressBlocks`: internet address space allocations · `routingRegistry`: autonomous systems and route announcements

Bundle

service

What operators provide

Layers

serviceOfferings`: network services and their characteristics · `coverageAndCapacity`: where services reach and at what capacity

Bundle

traffic

What actually flows

Layers

interconnection`: links and exchange points between networks · `trafficAggregates`: measured volumes per link, service and period

Findings

Catalogue-native findings must describe the information grouped by each layer. This legacy version does not declare them separately.

Questions & artifacts

Questions, artifact requirements and serial naming rules are required by Vercy vNext; they remain unassigned in this reference version.

Service layers

How this specification operates

Dimension & namespace

  • REFERENCE `world.organization` (O1): operators, registries and exchange point stewards as organizations.
  • REFERENCE `world.energy` (F1): network facilities are consumption points in the energy model.
  • COMPOSE `world.money` (F2): interconnection settlement amounts embed the money value object.
  • imports: ITU (ALIGN): spectrum band designation and numbering governance semantics.
  • imports: IETF (ALIGN): internet addressing and routing protocol semantics.
  • imports: BGP registries (REFERENCE): externally governed routing registry objects (route, aut-num).
  • imports: IANA (REFERENCE): externally governed address and protocol registries.

Canon, patches & standards

  • REFERENCE `world.organization` (O1): operators, registries and exchange point stewards as organizations.
  • REFERENCE `world.energy` (F1): network facilities are consumption points in the energy model.
  • COMPOSE `world.money` (F2): interconnection settlement amounts embed the money value object.
  • imports: ITU (ALIGN): spectrum band designation and numbering governance semantics.
  • imports: IETF (ALIGN): internet addressing and routing protocol semantics.
  • imports: BGP registries (REFERENCE): externally governed routing registry objects (route, aut-num).
  • imports: IANA (REFERENCE): externally governed address and protocol registries.

Artifact formats & serial data

Format-independent core. Concrete artifact formats and naming prefixes are not declared in this legacy version.

Policies & accepted processes

  • `publicRegistryLookup`: open resolution of spectrum grants, address blocks, numbering assignments and routing records.
  • `coverageDataAccess`: consumers read service coverage and capacity data for planning and comparison.
  • `trafficStatisticsFeed`: subscribed consumers receive traffic aggregates without endpoint or subscriber detail.

Read / add / edit / delete

CRUD procedures and interface bindings are not declared in this legacy version.

Ownership, roles & access

Operators steward their service, link and traffic records, and registrar archetypes steward the address, numbering and routing registries. Spectrum bands are a commons: grants are recorded through the catalogue's S1 ownership model as commons allocations, access to all records is granted by the respective steward via S1/S2, and registry changes are audited via S4.

Existing assembly

Objects, relationships, events and projections

Objects

  • `networkService`: a communications service offered by an operator; key attributes: serviceType, operatorRef, qualityParameters.
  • `spectrumBand`: a frequency range with a designated use; key attributes: lowerFrequency, upperFrequency, designatedUse.
  • `spectrumGrant`: an allocation of a band to an operator; key attributes: granteeRef, territory, conditions, validity.
  • `addressBlock`: a block of internet address space; key attributes: prefix, allocationStatus, registryRef.
  • `numberingResource`: a telephone numbering range or code; key attributes: rangeType, digits, assigneeRef.
  • `autonomousSystem`: a routing domain identified by number; key attributes: asNumber, operatorRef, routingPolicy.
  • `interconnectionLink`: a traffic exchange link between two networks; key attributes: linkType, capacity, exchangePointRef.
  • `trafficAggregate`: measured traffic volume for a scope and period; key attributes: scope, period, volume, direction.

Relationships

  • `spectrumGrant` -> allocates -> `spectrumBand` (n:1): the band an allocation covers.
  • `networkService` -> operatesUnder -> `spectrumGrant` (n:m): grants a wireless service depends on.
  • `addressBlock` -> announcedBy -> `autonomousSystem` (n:m): who originates routes for a block.
  • `networkService` -> uses -> `numberingResource` (n:m): numbering ranges serving a service.
  • `interconnectionLink` -> connects -> `autonomousSystem` (n:2): the two networks a link joins.
  • `trafficAggregate` -> measuredOn -> `interconnectionLink` (n:1): where a volume was observed.

Events

  • `grantIssued`: a spectrum band was allocated to an operator under stated conditions.
  • `grantExpired`: a spectrum allocation ended and the band returned to the commons pool.
  • `blockAllocated`: an address block or numbering range was assigned to an operator.
  • `routeAnnounced`: an autonomous system began originating routes for an address block.
  • `routeWithdrawn`: a route announcement ceased.
  • `linkEstablished`: a new interconnection between two networks went live.
  • `outageOccurred`: a service, link or coverage area became unavailable.
  • `trafficSampled`: a traffic aggregate was measured and recorded for a scope and period.

Projections

  • `publicRegistryView`: who holds which spectrum, addresses and numbers; omits commercial and operational internals.
  • `operatorCapacityView`: an operator's own services, links, utilization and outages; omits other operators.
  • `nationalTrafficAggregate`: territory-level traffic volumes and trends; omits all per-link and per-subscriber detail.