The Current Problem Sample Clauses

The Current Problem. ‌ The management of stacks is complex because it is necessary to coordinate vertical as well as horizontal aspects, each separated per component and provided stack element. On the horizontal aspect, each part of a communication service (each stack element on the same layer in each component), needs to be configured individually. A reconfiguration often requires to reconfigure all stack elements of all components. This situation is even more complicated when we apply a real word scenario, in which the ownership of the components varies. Any initial configuration and any further reconfiguration must now be coordinated amongst all components and their respective owner (assuming that the owner has administrative permissions to perform the configuration action). On the vertical, the configuration of each stack element must be configured in a way that the component overall can provide the advertised and required service. Here, ownership is not the problem. Instead the multi-vendor, multi-protocol, and multi-technology aspect of each individual stack layer provides for extensive complexity. In a 5G converged service provider network, we must also consider a separation of technology and ownership across the whole network, for components (here called nodes) as well as the “protocol zoo” dealing with various aspects of the network (and service) operation. Radio nodes form part of the radio network (RAN). Nodes aggregating radio access traffic and managing user sessions are found in the core network. Long distance communication and links to the public Internet belong to the transport network. Each of those networks is often owned by different parts of a provider’s organisation. This mix makes coordinated management of (protocol stacks) virtually impossible, mainly because the state space that needs to be coordinated is too large. The current solution is twofold. First, a large amount of standards is produced as normative source for management activities (the activities themselves as well as for the underlying stack). Those standards provide interoperability but limit flexibility. Second, management is often based on management models using managed objects (with standardised access in form of a defined protocol and standardised information models, often in terms of a management information base). A large number of models exists and needs to be considered for management activities. The figure 8 also shows the management points (blue interfaces) and the internal managem...