Vic aco consolidated route option
Download
1 / 7

VIC ACO : Consolidated Route Option - PowerPoint PPT Presentation


  • 115 Views
  • Uploaded on

VIC ACO : Consolidated Route Option. Consolidated VIC ACO. Key points On consolidated option, a VIC to a given DLE covers all traffic to that DLE, regardless of which CP node handles call Strictly there is no “CP-node” end To suit systems, an arbitrary “CP-node” end is used

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about ' VIC ACO : Consolidated Route Option' - macha


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
Vic aco consolidated route option

VIC ACO : Consolidated Route Option


Consolidated vic aco
Consolidated VIC ACO

  • Key points

    • On consolidated option, a VIC to a given DLE covers all traffic to that DLE, regardless of which CP node handles call

      • Strictly there is no “CP-node” end

      • To suit systems, an arbitrary “CP-node” end is used

    • VIC routes are treated as new provides

    • On VIC route entries, associated physical route is shown

      • The VIC route is associated with all physical capacity to the parent NGS, rather than with capacity from an individual CP node

      • As with the VIC details, an arbitrary CP node is assigned


Sample situation before vic
Sample situation – before VIC

L/BOX/1

L/BOX/2

L/BOX3

10E1

CP

10E1

10E1

6E1

L/AXT

OLO transit

700k peak

mins/month

6E1

4E1

L/MER/UB

L/NAT/UF

L/NAT/UD

BT

Collocated

Remote

1.4M peak

mins/month

1.2M peak

mins/month

2.4M peak

mins/month


Sample situation after vic
Sample situation – after VIC

Physical capacity that was on L/MER/UB, L/NAT/UF distributed across CP switches L/BOX/1..3. Traffic can be routed across any of these routes and still secure DLE rate if associated with L/MER/UB or L/NAT/UF ranges.

L/BOX/1

L/BOX/2

L/BOX3

15E1

15E1

L/MER/UB VIC requires e.g. 6E1. As operators don’t in general downsize existing 10E1 would be virtualised

15E1

30E1

L/NAT/UF VIC requires e.g. 5E1. As operators don’t in general downsize existing 6E1 would be virtualised

L/AXT

OLO transit

700k peak

mins/month

10E1

6E1

L/AXT VIC must serve 3.1M so strictly requires 12E1 - physical ports not paid for as VIC charges recover costs so long as Sum(VIC)>Sum(Physical). As operators don’t in general downsize, existing 30E1 would be virtualised.

10 + 6 + 30 > 15 + 15 + 15

So condition that VIC>Physical met

L/MER/UB

L/NAT/UF

L/NAT/UD

Collocated

Remote

1.4M peak

mins/month

1.2M peak

mins/month

2.4M peak

mins/month



Representation on aco1
Representation on ACO

Create

VIC routes

Re-arrange the physical capacity off DLEs


Representation on aco2
Representation on ACO

NB these rows could be replaced by a single row of C / -6 :

In this example broken out to show that 5 are being cease/reprovided, 1 ceased outright

CP switch connection is arbitrary

CP switch connection is arbitrary


ad