InterDomain-QOSM: The NSIS QoS Model for Interdomain Signaling to Enable End-to-End QoS
Provisioning Over Heterogeneous Network Domains
Jian Zhang
Outline
• The Problems of the Current Solution in NSIS for
End-to-End QoS Provisioning Over Heterogeneous
Network Domains
• The Overview of the NSIS InterDomain-QOSM
– The Operation Model of the InterDomain-QOSM
– Basic Features of InterDomain-QOSM
• Additional QSPEC Parameters for the InterDomainQOSM
• Illustrations of Inter-domain Signalling Interactions
with the InterDomain-QOSM
• Open Issues
• Conclusions
2
The Problems of the Current Solution in NSIS
for End-to-End QoS Provisioning Over
Heterogeneous Network Domains
Problem1: The End-to-End QoS Provisioning Cannot Be Realized Unless
Ingress QNE Can Support ANY Type of Local NSIS QOSM
Problem2: The End-to-End QoS Provisioning Cannot Be Realized Unless
ALL Domains are NSIS-capable
3
Problem1: The End-to-End QoS Provisioning Cannot
Be Realized Unless Ingress QNE Can Support ANY
Type of Local NSIS QOSM
Source Domain
Transit Domain
QNI
NSIS QOSM1
Interior QNE
NSIS QOSM1
Egress QNE
NSIS QOSM1
Interior QNE
Ingress QNE
NSIS QOSM2
NSIS QOSM2
NSIS QOSM1
NSIS QOSM1 in the source domain
could be ANY type of
local NSIS QOSM, e.g. current and/or
future QOSMs for xDSL, Ethernet, WiFi,
UMTS, etc, access networks.
Thus, the Ingress QNEs must be able
to support all of them so that the mapping
from the local NSIS QOSM of the source
domain to the local NSIS QOSM of the
transit or sink domains can be done
correctly. This is very hard to satisfy.
Egress QNE
NSIS QOSM1
Sink Domain
Ingress QNE
NSIS QOSM3
NSIS QOSM1
Interior QNE
QNR
NSIS QOSM3 NSIS QOSM3
4
Problem2: The End-to-End QoS Provisioning Cannot
Be Realized Unless ALL Domains are NSIS-capable
Obviously, the end-to-end QoS
provisioning via the current NSIS
signaling approach can not be achieved
if there exists any non-NSIS domain
along the path from the sender to the
receiver. This is also very hard to
satisfy in the complex, heterogeneous
IP network environment like Internet.
5
The Overview of the NSIS InterDomainQOSM
The Distinct Separation Between the Intra-domain Control
Plane and the Inter-domain Control Plane
Basic Features of InterDomain-QOSM
The Operation Model of the InterDomain-QOSM
6
The Distinct Separation Between the Intradomain Control Plane and the Inter-domain
Control Plane
Domain B
Intra-domain
control agent
(centralized
or distributed)
<<<<<>>>>>
Inter-domain
control agent
(centralized)
Common
Interdomain
control
interface
Inter-domain
control agent
(centralized)
<<<<<>>>>>
Intra-domain
control agent
(centralized
or distributed)
<<<<<>>>>> = interactions between the intra-domain control agent and the inter-domain control agent at a domain
= common inter-domain interface between peer inter-domain control agents at adjacent domains
The high-level view of the inter-domain interactions between two
adjacent domains where the distinct separation between the intra-domain
and inter-domain control planes is made and a common inter-domain
control interface exists.
7
Basic Features of InterDomainQOSM (1)
• The InterDomain-QOSM assumes the concept of the
distinct separation between the intra-domain control
plane and the inter-domain control plane at each
administrative domain.
• The inter-domain control agent is a domain-wide
centralized QNE which is well-known at its
administrative domain and supports the InterDomainQOSM so that the inter-domain interactions between
adjacent domains can be realized in a standardized
way.
• The SLS parameters and QoS control information
required for the inter-domain QoS interactions are
specified by using/extending the QSPEC template.
8
Basic Features of InterDomainQOSM (2)
• The InterDomain-QOSM resides on top of the QoSNSLP and NTLP, which means that it uses the
messages, objects and procedures defined by the
QoS-NSLP for signaling exchanges with other QNEs
and depends on the NTLP to discover the peer interdomain control agents at the adjacent domains.
• The InterDomain-QOSM makes no assumptions
about the implementation mechanisms of intradomain control agent. That is to say that the intradomain control agent might be centralized or
distributed, NSIS based or non-NSIS based.
• The InterDomain-QOSM makes no assumption about
the method that the underlying NTLP might use to
discover the peer inter-domain control agents at
adjacent domains.
9
Basic Features of InterDomainQOSM (3)
• The egress QNE (for a NSIS domain) need to send
its IP interface to which the signaled stream is
assigned to the inter-domain control agent so that the
RESPONSE message can be sent back to the
egress QNE.
• The egress QNE (for a NSIS domain) or the intradomain control agent (for a non-NSIS domain) need
to discover the IP interface of the ingress node from
which the signaled stream will be admitted into its
adjacent downstream domain and send this interface
to the inter-domain control agent at its domain
although the InterDomain-QOSM makes no
assumptions about the discovery method.
10
The Operation Model of the InterDomainQOSM (1)
Inter-domain
control
agent
QoS Trigger
1
Inter-domain
control
agent
3
InterDomain
QOSM
12
6
InterDomain
QOSM
10
2
9
InterDomain
QOSM
4
Intra-domain
11
QOSM1
5
QoS-NSLP
Intra-domain
control
agent
Inter-domain
control
agent
NTLP*
7
Intra-domain
QOSM2
QoS-NSLP
NTLP*
8
Intra-domain
QOSM3
QoS-NSLP
Intra-domain
control
agent
NTLP*
Intra-domain
control
agent
NTLP*: path-coupled or path-decoupled NTLP
Intra-domain control agent can be centralized or distributed, NSIS based or non-NSIS based
11
The Operation Model of the InterDomainQOSM (2)
• By utilizing the operation model of the InterDomainQOSM to enable end-to-end QoS provisioning over
multiple, heterogeneous network domains, the edge
QNEs in NSIS domains need to support only its local
NSIS QOSM and the InterDomain-QOSM.
• By utilizing the InterDomain-QOSM for the interdomain signaling, the inter-domain signaling
interactions can be realized in a standardized way no
matter how the intra-domain control plane is
implemented (centralized or distributed, NSIS based
or non-NSIS based).
12
Additional QSPEC Parameters for the
InterDomain-QOSM
Egress ID Parameter
Ingress ID Parameter
Absolute Time Specification Parameter
Relative Time Specification Parameter
13
Egress ID Parameter
<Egress ID> parameter is added to the QSPEC Control
Information of the InterDomain-QOSM, which describes
the IP interfaces of the egress node to which the signaled
traffic stream is assigned.
14
Ingress ID Parameter
<Ingress ID> parameter is added to the QSPEC Control
Information of the InterDomain-QOSM, which describes
the IP interfaces of the ingress node to which the signaled
traffic stream is assigned.
15
Absolute Time Specification Parameter
<Absolute Time Specification> defines a time period over which
a SLS will be available or requested by specifying its starting and
ending time points.
16
Relative Time Specification Parameter
<Absolute Time Specification> defines a time period over which
a SLS will be available or requested by specifying only the length
of the time period.
17
Illustrations of Inter-domain Signalling
Interactions with the InterDomain-QOSM
Y.1541-QOSM (source domain)--- RMD-QOSM(transit domain) ---Y.1541-QOSM (sink domain)
Non-NSIS (source domain) --- RMD-QOSM (transit domain) --Y.1541-QOSM (sink domain)
Non-NSIS (source domain) --- Non-NSIS (transit domain) --- NonNSIS (sink domain)
18
Y.1541-QOSM (source domain)--- RMD-QOSM(transit
domain) ---- Y.1541-QOSM (sink domain)
Source Domain
Inter-domain
control agent
InterDomain-QOSM
1
2
QNI
Y.1541 QOSM
Transit Domain
4
Inter-domain
control agent
InterDomain-QOSM
3
Interior QNE
5
6
Y.1541 QOSM
Ingress QNE
RMD QOSM
Y.1541 QOSM
InterDomain-QOSM
InterDomain-QOSM
8
Egress QNE
Interior QNE
7
RMD QOSM
Egress QNE
9
RMD QOSM
InterDomain-QOSM
Steps 1-2: QoS-NSLP message with Y.1541-QOSM QSPEC
Steps 3-5: QoS-NSLP message with InterDomain-QOSM QSPEC
Steps 6-7: QoS-NSLP message with RMD-QOSM QSPEC
Steps 8-10: QoS-NSLP message with InterDomain-QOSM QSPEC
Steps 11-12: QoS-NSLP message with Y.1541-QOSM QSPEC
Y.1541 QOSM
InterDomain-QOSM Y.1541 QOSM
InterDomain-QOSM
Ingress QNE
Sink Domain
10
Ingress QNE
11
12
QNR
Y.1541 QOSM
Interior QNE
Y.1541 QOSM
Inter-domain
control agent
InterDomain-QOSM
19
Non-NSIS (source domain) --- RMD-QOSM (transit
domain) --- Y.1541-QOSM (sink domain)
Source Domain
Inter-domain
control agent
1
QoS trigger
Inter-domain
control agent
Transit Domain
3
2
Intra-domain
control agent
4
5
Ingress QNE
RMD QOSM
InterDomain-QOSM
7
Egress Node
Interior QNE
6
RMD QOSM
Step 1: QoS trigger sends its request to the intra-domain control agent
Step 2: Intra-domain control agent sends its inter-domain request to
the inter-domain control agent
Egress QNE
8
RMD QOSM
InterDomain-QOSM
Y.1541 QOSM
InterDomain-QOSM
Steps 3-4: QoS-NSLP message with InterDomain-QOSM QSPEC
Steps 5-6: QoS-NSLP message with RMD-QOSM QSPEC
Steps 7-9: QoS-NSLP message with InterDomain-QOSM QSPEC
Steps 10-11: QoS-NSLP message with Y.1541-QOSM QSPEC
Ingress QNE
Sink Domain
Y.1541 QOSM
InterDomain-QOSM
9
Ingress QNE
10
Inter-domain
control agent
11
QNR
Y.1541 QOSM
Interior QNE
Y.1541 QOSM
20
Non-NSIS (source domain) --- Non-NSIS (transit
domain) --- Non-NSIS (sink domain)
Source Domain
Transit Domain
Inter-domain
control agent
Inter-domain
control agent
3
1
QoS trigger
2
4
5
Intra-domain
control agent
Egress Node
Intra-domain
control agent
7
Ingress Node
Step 1: QoS trigger sends its request to the intra-domain control agent
6
Egress Node
Step 2: Intra-domain control agent sends its inter-domain request to
the inter-domain control agent
Step 3: QoS-NSLP message with InterDomain-QOSM QSPEC
Step 4: Inter-domain control agent sends the requested SLS parameters
and the IP interface of the ingress node from which the
signaled stream will be accepted into the transmit domain to the
intra-domain control agent
Ingress Node
Inter-domain
control agent
Ingress Node
7
Step 5: The intra-domain control agent sends its inter-domain request
to the inter-domain control agent
Step 6: QoS-NSLP message with InterDomain-QOSM QSPEC
Intra-domain
control agent
Sink Domain
7
Step 7: Inter-domain control agent sends the requested SLS parameters
and the IP interface of the ingress node from which the
signaled stream will be accepted into the sink domain to the
intra-domain control agent
21
Open Issues
• For the case that the non-NSIS domain exists, we
currently assume that a domain-wide centralized
intra-domain control agent resides together with the
inter-domain control agent and they interact with
each other via a set of standardized APIs (the
definitions of the APIs also need further discussions).
• The discovery of the IP interface of the ingress node
from which the signaled stream will be admitted into
its adjacent downstream domain could be moved to
the inter-domain control agent.
• More QSPEC parameters may be needed for the
InterDomain-QOSM.
• The support of the automatic inter-domain adjustment
in the scenario of mobile end customers.
22
Conclusions (1)
• The InterDomain-QOSM assumes the
concept of distinct separation between the
intra-domain and inter-domain control agents
at each administrative domain.
• The InterDomain-QOSM allows the QoS
negotiation and setup of inter-domain traffic
streams in a standardized and dynamic way,
hiding the heterogeneity of intra-domain
control mechanisms in use in a chain of
heterogeneous network domains.
23
Conclusions (2)
• By utilizing the operation model of the InterDomainQOSM, the edge QNEs in NSIS domains need to
support only its local NSIS QOSM and the
InterDomain-QOSM for the end-to-end QoS
provisioning over multiple, heterogeneous network
domains.
• By utilizing the InterDomain-QOSM for the interdomain signaling, the inter-domain signaling
interactions can be realized in a standardized way no
matter how the intra-domain control plane is
implemented (centralized or distributed, NSIS based
or non-NSIS based).
24