InterDomain-QOSM: The NSIS QoS Model for Inter-

domain 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 InterDomain-
QOSM
• 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
Interior QNE
NSIS QOSM1 Egress QNE
Ingress QNE NSIS QOSM2
NSIS QOSM1
NSIS QOSM2
NSIS QOSM1

NSIS QOSM1 in the source domain Egress QNE

NSIS QOSM1
could be ANY type of
local NSIS QOSM, e.g. current and/or
future QOSMs for xDSL, Ethernet, WiFi, Sink Domain

UMTS, etc, access networks. Ingress QNE

NSIS QOSM3
Thus, the Ingress QNEs must be able NSIS QOSM1

to support all of them so that the mapping Interior QNE

from the local NSIS QOSM of the source QNR
NSIS QOSM3 NSIS QOSM3

domain to the local NSIS QOSM of the

transit or sink domains can be done
correctly. This is very hard to satisfy.
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 InterDomain-
QOSM
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 Intra-
domain Control Plane and the Inter-domain
Control Plane

Domain B

Intra-domain <<<<<>>>>> Inter-domain Inter-domain <<<<<>>>>> Intra-domain

control agent control agent Common control agent control agent
Inter-
domain
control
interface
(centralized (centralized) (centralized) (centralized
or distributed) 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 InterDomain-
QOSM (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 InterDomain-
QOSM 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 InterDomain-
QOSM (2)
• The InterDomain-QOSM resides on top of the QoS-
NSLP 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 inter-
domain control agents at the adjacent domains.
• The InterDomain-QOSM makes no assumptions
about the implementation mechanisms of intra-
domain control agent. That is to say that the intra-
domain 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 InterDomain-
QOSM (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 intra-
domain 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 InterDomain-
QOSM (1)

Inter-domain Inter-domain Inter-domain

control control control
agent agent agent

QoS Trigger 3 6
InterDomain InterDomain InterDomain
1 12 QOSM 10 QOSM 9 QOSM

2 4 7
Intra-domain Intra-domain Intra-domain
QOSM1 11 5 8
QOSM2 QOSM3

QoS-NSLP QoS-NSLP QoS-NSLP

Intra-domain Intra-domain Intra-domain
control control control
agent NTLP* NTLP* agent NTLP* 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 InterDomain-
QOSM (2)
• By utilizing the operation model of the InterDomain-
QOSM 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 inter-
domain 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) --- Non-

NSIS (sink domain)

18
Y.1541-QOSM (source domain)--- RMD-QOSM(transit
domain) ---- Y.1541-QOSM (sink domain)
Inter-domain Transit Domain
control agent 4
Source Domain InterDomain-QOSM Inter-domain
control agent
1 InterDomain-QOSM
3
2 5
QNI
Interior QNE
Y.1541 QOSM 6 8
Y.1541 QOSM
Egress QNE Ingress QNE
RMD QOSM Interior QNE
Y.1541 QOSM 7
InterDomain-QOSM RMD QOSM
InterDomain-QOSM

Egress QNE
Steps 1-2: QoS-NSLP message with Y.1541-QOSM QSPEC RMD QOSM 9
InterDomain-QOSM
Steps 3-5: QoS-NSLP message with InterDomain-QOSM QSPEC Y.1541 QOSM
InterDomain-QOSM Y.1541 QOSM
InterDomain-QOSM
Steps 6-7: QoS-NSLP message with RMD-QOSM QSPEC

Steps 8-10: QoS-NSLP message with InterDomain-QOSM QSPEC Ingress QNE 10

Ingress QNE
Sink Domain 11
Steps 11-12: QoS-NSLP message with Y.1541-QOSM QSPEC

12 Inter-domain
control agent
Interior QNE InterDomain-QOSM
QNR Y.1541 QOSM
Y.1541 QOSM

19
Non-NSIS (source domain) --- RMD-QOSM (transit
domain) --- Y.1541-QOSM (sink domain)

Source Domain
Inter-domain Inter-domain
control agent Transit Domain control agent
3
1
QoS trigger 2
4

Intra-domain 5 7
control agent Egress Node Ingress QNE
RMD QOSM Interior QNE
6
InterDomain-QOSM RMD QOSM

Step 1: QoS trigger sends its request to the intra -domain control agent Egress QNE
RMD QOSM 8
Step 2: Intra-domain control agent sends its inter -domain request to InterDomain-QOSM
the inter -domain control agent Y.1541 QOSM
InterDomain-QOSM Y.1541 QOSM
Steps 3-4: QoS-NSLP message with InterDomain-QOSM QSPEC InterDomain-QOSM

Steps 5-6: QoS-NSLP message with RMD-QOSM QSPEC Ingress QNE 9

Ingress QNE
Steps 7-9: QoS-NSLP message with InterDomain-QOSM QSPEC Sink Domain 10

Inter-domain
Steps 10-11: QoS-NSLP message with Y.1541-QOSM QSPEC 11
control agent
Interior QNE
QNR Y.1541 QOSM
Y.1541 QOSM

20
 Non-NSIS (source domain) --- Non-NSIS (transit
domain) --- Non-NSIS (sink domain)
Source Domain
Inter-domain Transit Domain Inter-domain
control agent control agent
3
1
QoS trigger 2 4

5
Intra-domain Intra-domain 7
control agent Egress Node control agent
Ingress Node

Step 1: QoS trigger sends its request to the intra -domain control agent Egress Node 6

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 Ingress Node
Ingress Node Inter-domain
and the IP interface of the ingress node from which the
control agent
signaled stream will be accepted into the transmit domain to the
intra -domain control agent
7
Sink Domain
Step 5: The intra -domain control agent sends its inter -domain request
to the inter -domain control agent
Intra-domain 7
control agent
Step 6: QoS-NSLP message with InterDomain-QOSM QSPEC

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 InterDomain-

QOSM, 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 inter-
domain 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