Skip to content

CL-5.0.0

Planned release date: 31/07/2025

general

This is the inital release of the 5th generation, which is not backward compatible with the 4th generation! Main conceptual chages:

  • The reference implementation of 4th generation relied on an interconnected data storage between the Core and Supporting systems. This setup had to be changed due to the requirement for “independent working modes,” therefore in the 5th generation each Core and Support system has its own database.
  • The above described fundamental change also means that database record identifiers are no longer used to identify entities (system instances, service definitions, etc.). Entities have unique identifiers (names) at the cloud level.
  • The previous authentication mechanism relied on X.509 certificates. In addition, the integration of various authentication mechanisms is supported by the introduction of the Authentication Core System.

arrowhead-common-utils

Initial 5th generation release.

arrowhead-data-transfer-objects

Initial 5th generation release.

arrowhead-serviceregistry

Initial 5th generation release. Main changes compared to 4th generation:

  • The system has its own database.
  • Services are represented according to the service-operation design pattern.
  • In addition to service and system data, device data registration is also possible.
  • The interface representation of a service operation is much flexible and more expressive to ensure that translation support services could rely on the interface data stored by Service Registry Core System.
  • MQTT communication protocol support.

arrowhead-serviceorchestration-dynamic

Initial 5th generation release. Main changes compared to 4th generation:

  • The system has its own database.
  • Push orchestration support.
  • This system implements only the dynamic orchestration strategy.
  • MQTT communication protocol support.

arrowhead-authorization

Initial 5th generation release. Main changes compared to 4th generation:

  • The system has its own database.
  • Policy based authorization is implemented (instead of the previous peer-to-peer based).
  • Provider systems are allowed to define their own service authorization policies with the stipulation that rules made by cloud operators always have priority.
  • Simple verifiable authorization tokens are used instead of self-contained tokens.
  • MQTT communication protocol support.

arrowhead-authentication

Initial 5th generation release.

  • This Core System did not exist before.

arrowhead-blacklist

Initial 5th generation release.

  • This Support System did not exist before.