SOA Throughput Analysis - PowerPoint PPT Presentation

1 / 7
About This Presentation
Title:

SOA Throughput Analysis

Description:

Confidential. SOA Throughput Data. NorthEast Region: ILEC is SPID 9104. NPAC release 3.0. ... Confidential. SOA Traffic Observations ... Confidential. Conclusions ... – PowerPoint PPT presentation

Number of Views:48
Avg rating:3.0/5.0
Slides: 8
Provided by: jimr84
Category:

less

Transcript and Presenter's Notes

Title: SOA Throughput Analysis


1
SOA Throughput Analysis
  • April 11, 2001

2
SOA Throughput Data
  • SOA message counts (Notifications and SV
    operations) in the NE and MA regions were
    collected 3/28/01 0000 UTC though 3/30/01
    235959 UTC.
  • NorthEast Region
  • ILEC is SPID 9104.
  • NPAC release 3.0.
  • 38 of SOA messages were to the ILEC.
  • 317,304 Total SOA messages
  • 83 are Notifications
  • 17 are SV Requests
  • MidAtlantic Region
  • ILEC is SPID 9211.
  • NPAC release 2.0.
  • 40 of SOA messages were to the ILEC.
  • 299,719 Total SOA messages
  • 80 are Notifications
  • 20 are SV Requests

3
SOA Traffic Comparison Region
4
SOA Traffic Comparison - ILEC
5
SOA Interface Requirements
  • R6-28.1 - SOA to NPAC SMS interface transaction
    rates - sustained
  • A transaction rate of 2 CMIP transactions
    (sustained) per second shall be supported by each
    SOA to NPAC SMS interface association.
  • R6-28.2 - SOA to NPAC SMS interface transaction
    rates - peak
  • NPAC SMS shall support a rate of 5.2 CMIP
    operations per second (peak) over a single SOA to
    NPAC SMS interface association.

6
SOA Traffic Observations
  • During peak hours in all NPAC regions more
    notifications are generated than the NPAC can
    send or the ILEC can receive.
  • SOA Messages to the ILEC
  • NE - 38 of the SOA messages are destined to the
    ILEC.
  • MA - 41 of the SOA messages are destined to the
    ILEC.
  • In a worst case scenario, all SOAs in the NE
    region (45) send 2.0 requests/sec sustained, then
    both the NPAC and the ILEC will be required to
    support 137 CMIP message/sec to keep up. (2 m/s
    45 SOAs 4 notifications for each request 38)
  • Peak worst case scenario of 5.2 transactions/sec
    would require both the NPAC and the ILEC to
    support 356 CMIP messages/sec to keep up. (5.2
    m/s 45 SOAs 4 n/r 38)

7
Conclusions
  • Currently ILEC operations are being negatively
    impacted by the large number of notifications
    that are queuing at the NPAC.
  • Many same day ports are happening and
    notifications are not being received by the ILEC
    before the CLECs are calling to get concurrence.
  • When a cancel is done, and the SV is in cancel
    pending, the concurrence is typically needed
    quickly to allow subsequent porting activities.
  • NANC 179 can help with this problem, however its
    only applies to range operations and its
    currently part of release 4.0.
  • The LNP industry may have to evaluate the number
    of notifications that have been specified in the
    industry agreed flows.
Write a Comment
User Comments (0)
About PowerShow.com