The Bridge - Issue 3, 2021 - 13

Feature
Quality-of-Service Architecture for Cloud Computing Networking
models as present, the general approach for serviceenabled
model development is based on three categories
beyond best effort.
* Premium service attributes: Highest level of quality
with the strictest assurances in a contract.
* Guaranteed service attributes: Intermediate level of
quality with some assurances in a contract.
* Better-than-best effort service attributes: Lower level
of quality with the minimal assurances in a contract.
* Best effort service attributes: Highest level of quality
with the no assurances.
This structure allows for pricing in four tiers. Given these
general rules for enabled service creation, the service
providers can build their enabled services to conform to
the general rules. One proposed service enabled model
that supports these rules is called the Olympic Service
Model with Gold, Silver, and Bronze Services [10]. Gold,
Silver, and Bronze correspond to Premium, Guaranteed,
and Better-than-Best Effort services.
C. Conceptual Model for Hybrid System
The initial stage in developing the hybrid system QoS
network model is to define the model conceptually.
Network architectures generically describe the data,
control, and management paths of networks and
network element. The functional decomposition of the
hybrid system network architecture conceptual model is
displayed in Figure 1.
interworking functions are provided to complete the
network architecture.
In addition to the transport, control, and protocol layering
of the architecture components and interfaces, the QoS
reference model must specify the following aspects.
* Traffic Engineering implementation of flows with diverse
QoS requirements.
* Definition of a formal architecture to which traffic
engineering policies are attached (such policies include
priority, QoS, preemption, authorization, and logging
of events).
* Definition of policies used by the Network Manager to
disseminate to a switch or a router to meet individual
flow guarantees.
The resulting hybrid concept will have components in
the data plane, control plane, and management plane.
The dataplane includes physical connectivity based
on SONET, SDH, Ethernet, etc., label switching service
through MPLS, and transport layer routing and adaptation
in IP. The control plane includes selected protocols that
are constrained by the QoS rules. The management
plane provides policy schemas and decisions and
element support.
D. Reference Model for Hybrid System
A reference model describes entity partitioning,
functionality, and their components. Additionally, a
reference model describes the communication between
entities. The hybrid system QoS reference model is
displayed in Figure 2.
Figure 1: Functional Decomposition of Hybrid System
Network Architecture
Figure 2: Hybrid System QoS Reference Model
The functional decomposition displays the transport
layer network components to the left of the coordination
function and the control layer network components to
the right of the coordination function. The transport layer
network components are layered based on the protocol
functionality. The coordination function represents
the in-band and out-of-band communication between
the management functions and the data and control
plane functions. The blocks for the timing and
The reference model is partitioned into the element
entities that are connected by the data path. The
element entity represents the transport layer or data
path layer. Each element has an element controller
entity that is connected to the element and the other
element controllers by the control path. Each element
controller entity represents the control layer or control
path. Together the elements and the element controllers
provide all the data and control functionality of the
HKN.ORG
13
http://www.HKN.ORG
The Bridge - Issue 3, 2021

Table of Contents for the Digital Edition of The Bridge - Issue 3, 2021
