Jian Zhang

1
InterDomain-QOSM The NSIS QoS Model for
Inter-domain Signaling to Enable End-to-End QoS
Provisioning Over Heterogeneous Network Domains

• Jian Zhang

2
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

3
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

4
Problem1 The End-to-End QoS Provisioning Cannot
Be Realized Unless Ingress QNE Can Support ANY
Type of Local NSIS QOSM
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.
5
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.
6
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

7
The Distinct Separation Between the Intra-domain
Control Plane and the Inter-domain Control Plane
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.
8
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.

9
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.

10
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.

11
The Operation Model of the InterDomain-QOSM (1)
12
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).

13
Additional QSPEC Parameters for the
InterDomain-QOSM

• Egress ID Parameter
• Ingress ID Parameter
• Absolute Time Specification Parameter
• Relative Time Specification Parameter

14
Egress ID Parameter
ltEgress IDgt 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.
15
Ingress ID Parameter
ltIngress IDgt 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.
16
Absolute Time Specification Parameter
ltAbsolute Time Specificationgt defines a time
period over which a SLS will be available or
requested by specifying its starting and ending
time points.
17
Relative Time Specification Parameter
ltAbsolute Time Specificationgt defines a time
period over which a SLS will be available or
requested by specifying only the length of the
time period.
18
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)

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

20
Non-NSIS (source domain) --- RMD-QOSM (transit
domain) --- Y.1541-QOSM (sink domain)
21
Non-NSIS (source domain) --- Non-NSIS (transit
domain) --- Non-NSIS (sink domain)
22
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.

23
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.

24
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).