Jian Zhang

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

QNI

Egress QNEIngress QNE

Interior QNEInterior QNE

Egress QNE

Ingress QNE

Interior QNEQNR

Source Domain

NSIS QOSM1NSIS QOSM1

NSIS QOSM1

Transit Domain

Sink Domain

NSIS QOSM1



NSIS QOSM2


NSIS QOSM1 in the source domaincould be ANY type of local NSIS QOSM, e.g. current and/orfuture QOSMs for xDSL, Ethernet, WiFi,UMTS, etc, access networks.Thus, the Ingress QNEs must be ableto support all of them so that the mappingfrom the local NSIS QOSM of the sourcedomain to the local NSIS QOSM of thetransit or sink domains can be donecorrectly. 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 achievedif there exists any non-NSIS domainalong the path from the sender to thereceiver. This is also very hard tosatisfy in the complex, heterogeneousIP 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

Inter-domaincontrol agent

Intra-domain control agent

(centralized or distributed)

(centralized)

<<<<<>>>>> Inter-domaincontrol agent

(centralized)

Intra-domain control agent

(centralized or distributed)

<<<<<>>>>>

Domain B

CommonInter-

domaincontrol

interface

<<<<<>>>>> = 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 twoadjacent domains where the distinct separation between the intra-domainand inter-domain control planes is made and a common inter-domaincontrol 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)

InterDomainQOSM

QoS-NSLP

NTLP*

Intra-domainQOSM1

Intra-domaincontrolagent

QoS Trigger

1 12

2

11

InterDomainQOSM

QoS-NSLP

NTLP*

Intra-domainQOSM2


InterDomainQOSM

QoS-NSLP

NTLP*

Intra-domainQOSM3


3

10

4

5

6

9

7

8

Inter-domaincontrolagent



NTLP*: path-coupled or path-decoupled NTLP

Intra-domain control agent can be centralized or distributed, NSIS based or non-NSIS based

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

<Egress ID> parameter is added to the QSPEC ControlInformation of the InterDomain-QOSM, which describesthe IP interfaces of the egress node to which the signaledtraffic stream is assigned.

15

Ingress ID Parameter

<Ingress ID> parameter is added to the QSPEC ControlInformation of the InterDomain-QOSM, which describesthe IP interfaces of the ingress node to which the signaledtraffic stream is assigned.

16

Absolute Time Specification Parameter

<Absolute Time Specification> defines a time period over whicha SLS will be available or requested by specifying its starting andending time points.

17

Relative Time Specification Parameter

<Absolute Time Specification> defines a time period over whicha 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)

QNI

Egress QNE Ingress QNEInterior QNE

Interior QNE

Egress QNE

Source Domain

Y.1541 QOSM

Y.1541 QOSMInterDomain-QOSM

Transit Domain

Sink Domain

RMD QOSMInterDomain-QOSM RMD QOSM

Y.1541 QOSM


InterDomain-QOSM

QNR

Ingress QNEIngress QNE

Interior QNE

Y.1541 QOSMY.1541 QOSM

12

3

4

5

6

7

8

9

10

11

12

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




InterDomain-QOSM


InterDomain-QOSM

RMD QOSMInterDomain-QOSM



20

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

Egress Node Ingress QNEInterior QNE

Source Domain

Transit Domain

Sink Domain

RMD QOSM

QNR

Ingress QNEIngress QNE

Interior QNE

Y.1541 QOSMY.1541 QOSM

Inter-domain control agent

Inter-domain control agent

13

4

5

6

7

8

9

10

11

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


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



QoS trigger

Intra-domaincontrol agent


2

Egress QNERMD QOSM

InterDomain-QOSM

RMD QOSMInterDomain-QOSM



21

Non-NSIS (source domain) --- Non-NSIS (transit domain) --- Non-NSIS (sink domain)

Egress NodeIngress Node

Source DomainTransit Domain

Sink Domain

Ingress NodeIngress Node

13

7

6Step 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

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

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

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

QoS trigger



2

Egress Node

4



7

7



5

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

Jian Zhang

Documents

Transcript of Jian Zhang