<?xml version="1.0" encoding="UTF-8"?>
<collection xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.loc.gov/MARC21/slim http://www.loc.gov/standards/marcxml/schema/MARC21slim.xsd" xmlns="http://www.loc.gov/MARC21/slim">
 <record>
  <leader>00000cab a22000003a 4500</leader>
  <controlfield tag="001">UP-99796217608899753</controlfield>
  <controlfield tag="003">Buklod</controlfield>
  <controlfield tag="005">20231007234008.0</controlfield>
  <controlfield tag="006">m    |o  d |      </controlfield>
  <controlfield tag="007">ta</controlfield>
  <controlfield tag="008">090629s        xx     d | ||r |||||   ||</controlfield>
  <datafield tag="040" ind1=" " ind2=" ">
   <subfield code="a">DENGII</subfield>
  </datafield>
  <datafield tag="041" ind1=" " ind2=" ">
   <subfield code="a">eng</subfield>
  </datafield>
  <datafield tag="100" ind1="0" ind2=" ">
   <subfield code="a">Grover, W.D.</subfield>
  </datafield>
  <datafield tag="245" ind1="0" ind2="4">
   <subfield code="a">The protected working capacity envelope concept</subfield>
   <subfield code="b">an alternate paradigm for automated service provisioning.</subfield>
  </datafield>
  <datafield tag="300" ind1=" " ind2=" ">
   <subfield code="a">pp. 62-69</subfield>
  </datafield>
  <datafield tag="520" ind1=" " ind2=" ">
   <subfield code="a">At present we see only one basic approach being considered by implementors and standards organizations for provisioning of dynamic protected lightpath services that make efficient use of shared protection capacity. This is the paradigm of a primary working path protected end-to-end by a disjoint backup path using shared spare capacity. Sharing is arranged among the backup paths associated with other primary paths that are failure-disjoint from the current primary path. This approach called shared backup path protection (SBPP) has many advantages but also provides a great deal of network state information to be available and current in every node. It also makes the arrangement of protection a per-connection task, rather than user-selectable service option supported by the network itself. We propose an alternative paradigm for consideration, partly summed up as provisioning over protected capacity rather than provisioning protection. Under a given distribution of spare capacity, locally acting protection or restoration schemes create an &quot;envelope&quot; of protected working channels. Dynamic provisioning within this envelope is simplified to a shortest path routing problem and (depending on the mode of operation) requires little or no dissemination of state changes on a per-connection basis. We explain how existing &quot;static&quot; capacity design methods can be adopted to the dimensioning of such a working capacity envelope and the envelope dimensions further adapted online to track evolution of the overall pattern of random demand. An important property is that nothing needs to be done to arrange protection for services on the per-connection timescale other than routing the service itself. Arbitrarily fast-paced demand arrivals and departures can be accommodated within a static distribution of spare capacity. Adjustments to the envelope itself are required only on the timescale on which the statistical parameters of the random demand changes. This may provide an inherently more scalable, less database-dependent, and higher-availability alternative than SBPP, or at least an additional service modality that can be offered to customers.</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
   <subfield code="a">Automated service provisioning.</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
   <subfield code="a">Dynamic protected lightpath services.</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
   <subfield code="a">Protected working capacity envelope concept.</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
   <subfield code="a">Random demand changes.</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
   <subfield code="a">Service modality.</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
   <subfield code="a">Shared protection capacity.</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
   <subfield code="a">Shortest path routing problem.</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
   <subfield code="a">Static capacity design methods.</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
   <subfield code="a">Statistical parameters.</subfield>
  </datafield>
  <datafield tag="773" ind1="0" ind2=" ">
   <subfield code="t">IEEE Communications magazine</subfield>
   <subfield code="g">42, 1 (2004).</subfield>
  </datafield>
  <datafield tag="905" ind1=" " ind2=" ">
   <subfield code="a">FO</subfield>
  </datafield>
  <datafield tag="852" ind1=" " ind2=" ">
   <subfield code="a">UPD</subfield>
   <subfield code="b">DENG-II</subfield>
  </datafield>
  <datafield tag="942" ind1=" " ind2=" ">
   <subfield code="a">Article</subfield>
  </datafield>
 </record>
</collection>
