INSTITUT BELGE DES SERVICES POSTAUX ET DES TÉLÉCOMMUNICATIONS

Transcription

1 INSTITUT BELGE DES SERVICES POSTAUX ET DES TÉLÉCOMMUNICATIONS PROJET DE DÉCISION DU CONSEIL DE L IBPT DU 14 MARS 2007 CONCERNANT L AMENDEMENT A L OFFRE BROBA 2007 «FULL VP» Méthode d envoi des réactions au présent document Délai de réponse: jusqu au 31 mars 2007 Personne de contact: Alain Maton, Ingénieur-conseiller ( ) et Reinhard Laroy, Ingénieur-conseiller ( ) Adresse de réponse par alain.maton@ibpt.be et reinhard.laroy@ibpt.be Les réponses doivent uniquement être envoyées par voie électronique. Le document doit indiquer clairement ce qui est confidentiel. La présente consultation a lieu conformément à l article 140 de la loi du 13 juin BIPT - Astrotoren - Sterrenkundelaan 14, bus Brussel Tel Fax:

2 Table des matières Objet de la décision... 3 PRESENTATION DE LA PROPOSITION PAR BELGACOM...3 EVALUATION FAITE PAR L INSTITUT...3 DECISION DE L INSTITUT...3 Consultation... 4 Annexe : Proposition d amendement BROBA

3 OBJET DE LA DECISION Belgacom a introduit une proposition d amendement à l offre BROBA reprise en annexe 1 afin de configurer tous les DSLAMs d un même LEX ou d un même LDC afin de pouvoir exécuter des «change owner» sans qu il ne soit nécessaire de faire de migration physique du client vers un DSLAM sur lequel le Bénéficiaire dispose déjà de VP(s). PRESENTATION DE LA PROPOSITION PAR BELGACOM Le 2 mars 2007, Belgacom a présenté son projet à l Institut au cours d une réunion ad-hoc. Elle y a déclaré avoir discuté des différents aspects du projet avec chaque Bénéficiaire BROBA en bilatéral avec un résultat positif à l exception des remarques suivantes : o le délai de fournitures par Belgacom des spécifications techniques, notamment les messages XML, doit être suffisant pour adapter les systèmes des Bénéficiaires o certains Bénéficiaires ont fait état d une augmentation des coûts mais c était entre la situation actuelle et une prévision d augmentations des besoins o un opérateur estime que le coût de l adaptation de ses systèmes est prohibitif par rapport à son nombre de clients ADSL ; il a proposé différentes solutions techniques que Belgacom juge pertinente mais néanmoins trop lourde à mettre en œuvre pour un besoin aussi réduit EVALUATION FAITE PAR L INSTITUT L Institut estime la proposition de Belgacom positive pour l ensemble du secteur car le recours bien plus important à la migration virtuelle libère des ressources pour améliorer les délais d installation. En ce qui concerne les arguments développés par les bénéficiaires : o l offre BROBA 2007 a vu l adjonction d une clause concernant les préavis pour tout changement opérationnel ; il est clair qu il s agit ici d une modification importante qui tombe sous le régime des 6 mois de préavis o Belgacom a fourni à l Institut une simulation de la nouvelle situation pour chacun des Bénéficiaire à capacité inchangée pour chaque LEX ou LDC; dans tous les cas le résultat est positif pour les Bénéficiaires ; étant donné la diversité des situations, il est logique d en déduire que cela doit aussi être le cas en cas d augmentation des besoins o Si le système opérationnel de Belgacom le permet sans développement excessif, une exception peut être faite pour l opérateur estimant l opération trop lourde ; Belgacom ne souhaite pas créer un précédent pouvant amener à d autres exceptions, l Institut fait remarquer que les parties peuvent déroger de commun accord à l offre de référence, donc ne pourrait se prévaloir de ce précédent qu un opérateur ayant un système opérationnel développé sous le process actuel (donc pas un nouveau signataire) et ayant un volume comparable (et non significativement plus important) ; toutefois un tel cas particulier ne peut être une cause de non acceptation d une proposition favorable à l ensemble du marché DECISION DE L INSTITUT L Institut est favorable à cette adaptation de BROBA parce qu elle simplifie les processus d approvisionnement. L Institut est néanmoins préoccupé par les effets quantitatifs de cette décision sur la poursuite de la croissance du marché ainsi que sur les intentions des différents acteurs du marché de passer à des largeurs de bande plus élevées. Dans le cadre de cette 3

4 consultation, l Institut demande aux différents acteurs du marché d éventuellement fournir davantage d explications en la matière. CONSULTATION L Institut soumet à consultation publique le présent projet de décision jusqu'à 31 mars La réponse doit indiquer clairement ce qui est confidentiel. Si un Bénéficiaire estime que le nouveau système lui serait préjudiciable à l avenir, il doit le démontrer en joignant en annexe confidentielle une simulation de la tarification de sa future situation selon les principes actuels et ceux de la proposition. Les réponses sont à envoyer par mail aux adresses alain.maton@ibpt.be et reinhard.laroy@bipt.be M. VAN BELLINGHEN G. DENEF Lid van de Raad Lid van de Raad C. RUTTEN E. VAN HEESVELDE Lid van de Raad Voorzitter van de Raad 4

5 ANNEXE : PROPOSITION D AMENDEMENT BROBA Full VP I. Scope, objective and general principle This Addendum to the Belgacom Reference Offer for Bitstream Access concerns the project Full VP. The scope of this project is limited to BROBA VP switching services (ADSL+SDSL), regardless of the fact these services are delivered with or without voice. The objective of this project is to improve the provisioning process of the BROBA End-Users Lines in order to better respect the BROBA End-User Lines provisioning timers, as set by the Institute in its decision of November 29 th 2006 on BROBA To reach this objective Belgacom wants to reduce, during the End-User Lines provisioning process, the number of repatching of End-User Line from one DSLAM to another. Indeed, those repatching actions increase the provisioning time, as a manual intervention of a technician is then needed. To avoid those time-consuming repatching actions, Belgacom asks the Operators to order VPs on all the DSLAMS of each LEX/LDC where the Operators offer or start offering BROBA. As a result, when an Operator orders an End-User Line, Belgacom can find a VP of this Operator on the DSLAM where this End-User is provisioned, and the repatching from one DSLAM to another is no more needed. In order to take into account the specific needs of each Operator, a new information must also be added to each new or existing VP: the VP type. The VP type is an additional VP information defined by the Operator which represents a set of parameters (QoS, Access Line, etc ) on one or several LEX. The operational result is that the current process where an Operator orders an End-User Line on a particular VP is replaced by a new provisioning process where the Operator will order an End-User Line on a particular VP type. Belgacom will look on the DSLAM where this End-User Line is connected for a VP of this type for this OLO, and Belgacom will send back to the Operator the VPi of this VP. Another impact of this project is that the current VP ordering process, based on XLS order templates, will be replaced by XML ordering, as it is already the case for the End-User Lines and the provisioning actions on the VC s and the Line Profiles. The purpose of this modification is to balance the operational workload due to higher number of VP actions, to give feedback order per order, and to lower the VP provisioning times. Finally, Belgacom proposes a new method of taking into account the bandwidth to invoice per installed VP, to avoid a negative financial impact on the Operator ATM transport invoices due to the deduplication of the installed VP s. II. Added-value of this project for the Operators The first main advantage of this project for the Operators is the improvement of the provisioning time of the BROBA End-User Lines, which will results in an improved 5

6 perception of the service within the customers of the Operators. But this will also result for the Operators in a quicker cash-in of the revenues of the End-User lines. The second financial advantage of this new provisioning process is that in case of change of ownership of a line, or of conversion from a Belgacom retail or Carrier DSL line to BROBA, the migration costs will be lower than today, as the tariffs of the Virtual Migration will be applied, instead of those of the Physical Migration 1. III. Information provided to the Operators The following presentation has been given by Belgacom to the Platform of Operators on January 19 th I:\NPM\WKG\ ACCESS_TEAM\BROB A copy of this presentation has also been sent to every Operator already active in BROBA. Subsequently, Belgacom has also organized bilateral meetings with every Operator active in BROBA ADSL & SDSL VP switching to give more exhaustive explanations and to answer the questions due to each Operator specificities. Operator Meeting date Versatel 24/01/07, 15/02/07 Telenet 29/01/07, 06/03/07 Verizon 30/01/07 BT 08/02/07 Scarlet 14/02/07 Mobistar 15/02/07 Win 14/02/07 Easynet 07/03/07 Additionnally, in order to let the Operators analyse the IT impact of this project and start as soon as possible to plan it in their IT release, Belgacom has sent to all the Operators the new XML content description 2. IV. Planning Taking into account the IT developments needed both at Operator and at Belgacom side, Belgacom plans to start to work with the new End-User Lines and VP ordering process explained in 1 above as from October 23thrd Nevertheless, to insure a smooth transition, Belgacom proposes to the Operators to use a 3- month transitory period, from June 18 th 2007 until October 22 nd 2007, to duplicate the existing park of VPs and to add the VP types. During this transitory period, no End-User Lines would be provisioned on the duplicated VPs. The new billing method would of course only be applicable as from October 23thrd Cfr Annex K : Migrations for BRUO and BROBA. 2 The XML content description are available on the Belgacom Website, on the Personal Page of the OLOs. Those documents describe the type of information needed in the XML files exchanged between the Operators and Belgacom during the ordering process. 6

7 V. Target date for consultation result The importance of the IT developments needed for this project inside Belgacom makes it one of the Top IT projects of the company in Nevertheless, the Belgacom IT department can only develop it if all requirements are delivered before April 16 th This means that the results of the BIPT decision must be known by this date. Any delay can result in a 3 to 6 months delay in the implementation of the project. VI. Adaptation on BROBA documents This addendum impacts the following BROBA documents : BROBA II ADSL Main Body BROBA II ADSL 2007 Annex 3 Exchange of Information BROBA II ADSL 2007 Annex 4 Planning and Operations Annex 5 BROBA II ADSL & BROBA II SDSL VP & VC switching 2007 Basic Service Level Agreement BROBA II ADSL 2007 Annex 6 Pricing and Billing BROBA II ADSL and SDSL VP switching Annex 9 Guaranteed Positions & Related Migrations, Concentrations and Pricing Rules The sections of the BROBA documents which are impacted by this Addendum are indicated in the subsequent paragraph. VII. BROBA II ADSL Main Body In section 4.2, the paragraph 25, 26 & 28 must be replaced by : 25. The Beneficiary will order bandwidth and more precisely Virtual Paths (VPs) between each DSLAM located in the Lex + LDC s + other relevant points where Belgacom installed DSLAM s in which the Beneficiary wants to connect End Users and the Belgacom Access Point to which the Beneficiary is connected. 26. Minimum bandwidth that has to be ordered by the Beneficiary between each DSLAM in a LEX (or LDC or KVD) when provided by Belgacom in the framework of its own retail or wholesale offer) and a Belgacom ATM Access Point is 256kbps PCR 3. Bandwidth is available on request of the Beneficiary with a granularity of 256 kbps. 28. The list of Access Areas is available in Appendix C. The list of DSLAM s is available on the Operator Personnal Page of the NWS secured website. In section 4.4, the paragraph 43 must be replaced by : 43. These VP s can be of the following QoS: - CBR; - VBR rt with PCR/SCR ratio between 1 and 8; - VBR nrt with PCR/SCR ratio between 1 and 8. - UBR+ 4 In section 5.1, the paragraph 81 must be replaced by : 3 Ratio 1 only 3 UBR+ is not specific to Belgacom equipment 7

8 81. Prior to the connection by Belgacom of a specific Beneficiary s End User line, The Beneficiary must have provided Belgacom with a bandwidth order between each DSLAM in a Lex (or LDC or KVD when provided by Belgacom in the framework of its own retail or wholesale offer) in which he wants to connect End Users and Belgacom ATM Access Point to which he is connected. Belgacom must have performed, on the Beneficiary request, the installation of a dedicated Access Line between an ATM switch located in a Belgacom ATM Access Point and the Beneficiary s equipment. In section 5.2.1, the paragraph 86 must be replaced by : 86. At the moment the Beneficiary requests the activation of ADSL on an End User line, within a specific Lex + LDC s + other relevant points where Belgacom installed DSLAM s, Belgacom verifies the existence on the DSLAM where this End User line is connected of the VP necessary to transport the ADSL traffic of this End User between the DSLAM from which this End User depends and the Beneficiary equipment and reversely. In section 5.3, the paragraph 94 and 95 must be replaced by : 94. To be able to offer the Broba II ADSL, the Beneficiary needs to order bandwidth between each DSLAM s in the Lex + LDC s + other relevant points where Belgacom installed DSLAM s to which he wants to connect End Users and the ATM Access Point to which the Beneficiary is connected. 95. In the limits of the VP specifications as mentioned in this offer (VP QoS and VP minimum dimensioning), the Beneficiary can request: - For an upgrade of the total bandwidth he ordered between a specific DSLAM located in a Lex + LDC s + other relevant points where Belgacom installed DSLAM s and the ATM Access Point to which he is connected - For a downgrade of the total bandwidth he ordered between a specific DSLAM located in a Lex + LDC s + other relevant points where Belgacom installed DSLAM s and the ATM Access Point to which he is connected - For a modification of the bandwidth s allocation amongst the different VPs within a specific Lex + LDC s + other relevant points where Belgacom installed DSLAM s. - In section 5.2.1, the paragraph 97 must be replaced by : 97. Firm orders of bandwidth per LEX shall be done through the use of an XML order as described in the XML content description documents available on the Operator Personnal Page of the NWS secured website. VIII. BROBA II ADSL 2007 Annex 3 Exchange of Information In section 2.1, the following bullet points must be deleted : address for ordering Technical Belgacom contact for the synchronization in setting up VP s In section 2.2, the following bullet points must be deleted : Technical Beneficiary contact for the synchronization in setting up VP s address for communication of VP configuration 8

9 In section 3.3, the paragraph 10 must be replaced by : 10. Before the Beneficiary can submit an order for the activation of ADSL on a specific End User line, Virtual Paths needs to be in service between each DSLAM located in the Lex (LDC, KVD, if any) from which the End User depends and the Belgacom ATM Access Point to which the Beneficiary is connected. In section 3.3.1, the paragraphs 11 to 14 must be replaced by : 11. Once the Access Line is in place, the Beneficiary will be able to order bandwidth between each DSLAM located in the LEX (LDC, KVD, if any) in which the Beneficiary wants to connect End Users and the Belgacom ATM Access Point to which the Beneficiary is connected. 12. The communication process between the Beneficiary and Belgacom is based on SMTP Mail for the transfer, an ACK/NACK protocol and a message file in attachment with a predefined format. 13. The Beneficiary prepares the file in the predefined XML format, signs it, encrypts it, attaches it to a mail and sends it to the mailbox of Belgacom. The address for Broba II ADSL is is llu.car@belgacom.be. 14. When the VP is created by Belgacom, the Beneficiary will receive an electronic message (done message) with all the necessary information in order to configure the related VP at his side of the network. In section 3.3.2, the paragraphs 16 to 17 must be replaced by : 16. Firm orders of bandwidth modification shall be done through the use of an XML order as described in the XML content description documents available on the NWS secured site. Orders are sent via the secured electronic messaging system. There is one request per XML order. 17. When the VP has been modified by Belgacom, the Beneficiary will receive an electronic message (done message) with all the necessary information in order to make the modification of the related VP at his side of the network. IX. BROBA II ADSL 2007 Annex 4 Planning and Operations In section , the paragraphs 17 and 18 must be replaced by : 17. The Beneficiary will order bandwidth between each DSLAM sited in a LEX/LDC in which the Beneficiary wants to connect End Users and the Belgacom ATM Access Point to which the Beneficiary is connected. Belgacom does the set-up and the configuration of the VP s, between the DSLAM s from which the End Users depend and the Beneficiary equipment, on behalf of the Beneficiary. 18. Firm orders of bandwidth per LEX shall be done through the use of an XML order as described in the XML content description documents available on the NWS secured site. Orders will be considered as valid only when they are properly completed. In case data is missing or is not correct, the order will be rejected. In the latter case, Belgacom will indicate the reasons of rejection on the reject. Orders are sent via the secured electronic messaging system, as described in appendix C of this document and in the 9

10 corresponding XML content description documents. There is one request per XML order. In section , the paragraph 21 must be replaced by : 21. The Beneficiary can order a VP through a firm order. A firm order consists of the requested VP with its associated parameters (bandwidth, PCR, SCR, QoS, VP Type,..). In section , the paragraphs 23 and 24 must be replaced by : 23. When the Beneficiary sends an order to activate the ADSL on an End User line, Belgacom will provide the Beneficiary with all the necessary information in order to configure the related VP at the Beneficiary s side of the network, when the validate XML is sent back to the OLO 24. The Beneficiary is requested to deliver Belgacom with a technical Beneficiary contact for the synchronization in setting up VP s. The Beneficiary will need to communicate Belgacom the Virtual Path identifier (Vpi) at his side of the network. In section , the paragraph 26 must be replaced by : 26. Firm orders of bandwidth modification shall be done through the use of an XML order as described in the XML content description documents available on the NWS secured site. Orders will be considered as valid only when they are properly completed. In case data is missing or is not correct, the order will be rejected. In the latter case, Belgacom will indicate the reasons of rejection on the reject. Orders are sent via the secured electronic messaging system, as described in appendix C of this document and in the corresponding XML content description documents. There is one request per XML order. In section , the paragraph 27 must be suppressed. In section , the paragraph 29 must be replaced by : 29. The order is relative to an existing VP and must contain its correct identification (cfr all informations specified in the XML content description document for VP ordering). In section , the paragraph 30 must be replaced by : 30. The Beneficiary can ask to modify the existing parameters of its VPs through a firm XML order. A firm order consists of the requested VPs parameters per LEX/LDC, per VP. In section , the paragraph 34 must be replaced by : 34. Firm orders of bandwidth cancellation shall be done through the use of an XML order as described in the XML content description documents available on the NWS secured site. Orders will be considered as valid only when they are properly completed. In case data is missing or is not correct, the order will be rejected. In the latter case, Belgacom will indicate the reasons of rejection on the reject. Orders are sent via the secured electronic messaging system, as described in appendix C of this document and in the corresponding XML content description documents. There is one request per XML order. In section , the paragraph 35 must be suppressed. 10

11 In section , the paragraph 39 must be replaced by : 39. The Beneficiary can ask the cancellation of its VPs through a firm XML order. A firm order consists of the requested VPs parameters per LEX, per VP. In Appendix E, section 2.2., the paragraph 200 must be replaced by : 200. Ordering Bandwith capacity, as well as changing or cancelling bandwith is done through XML. See for details and examples on the Belgacom NWS secured website. In Appendix E, section 2.2., the paragraph 201 must be suppressed. In Appendix E, section 2.2., the Virtual Path ordering template must be suppressed. X. Annex 5 BROBA II ADSL & BROBA II SDSL VP & VC switching 2007 BASIC SERVICE LEVEL AGREEMENT In section , the paragraph 28 must be replaced by : 28. The set-up and configuration of VP/VC timer is related to the creation of a new VP/VC between a DSLAM and the Beneficiary. The set-up and configuration of VP/VC timer will start on the receipt of the order, submitted to Belgacom through the secured electronic system (XML) or as back up procedure via non-secured electronic system and fax as described in the Annex 4. This receipt is the automated acknowledge message that is sent to the Beneficiary. Messages that are incorrect, due to the reasons as described in the Annex 4 - Planning and Operations will be returned with a Not Acknowledged message. In this case, Beneficiary needs to resend the order with the corrections. The set-up and configuration of VP/VC timer is set at : Set-up & configuration timer (to be respected by Belgacom) Timer 10 working days In section , the paragraph 30 must be replaced by : 30. The modification of a VP/VC parameters timer will start on the receipt of the order, submitted to Belgacom through the secured electronic system (XML) or as back up procedure via non-secured electronic system and fax as described in the Annex 4. This receipt is the automated acknowledge message that is sent to the Beneficiary. Messages that are incorrect, due to the reasons as described in the Annex 4 - Planning and Operations will be returned with a Not Acknowledged message. In this case, Beneficiary needs to resend the order with the corrections. The modification of a VP/VC parameters timer is set at: Modification of VP/VCs parameters timer (to be respected by Belgacom) Timer 3 working days XI. BROBA II ADSL 2007 Annex 6 Pricing and Billing 11

12 The solution present in this addendum is different from that presented during the Platform meeting. The reference bandwidth Bd Min - is calculated neither based on the PCR but well the SCR. It has being modified for the following reason: the billing system was developed to take into account only SCR and ratio and a new development is impossible. In section 1.3.1, the paragraph 30 must be replaced by : 30. The formulas in section are applicable for the aggregated bandwidth per LEX, per VP type, per QoS, per contract duration and per PCR/SCR ratio. Increase of this aggregated bandwidth is not to be considered as an interruption of the ruling duration commitment. The aggregated bandwidth for all VP s of type t and QoS q on a LEX l is calculated as following : A = SUM[IF(BWVP(SCR) tql i > BWmin q ; BWVP(SCR) tql i ;0)] Or (If A=0) : MAX[BWVP(SCR) tql i ] where : i BWVP(SCR) tql = Bandwidth of VP i of type t and QoS q (on all DSLAMs of a LEX l), in SCR 5 BWmin q = minimum bandwidth for Qos q VP QoS CBR VBR nrt VBR rt UBR + (MBR) BWmin q 512 kbps kbps kbps kbps In section , the table must be replaced by : Euro Administration fee per request 6 65,90 Activation fee per VP 7 32,62 This means that in case of creation of duplicated VP s of the same type towards all DSLAM s of a LEX/LDC, the total Activation fee applicable for all those VP s is the same as in today s way of working for only one VP. XII. BROBA II ADSL and SDSL VP switching Annex 9 Guaranteed Positions & Related Migrations, Concentrations and Pricing Rules The entire Annex 9 must be suppressed. The relevant topics will be moved to the right place : 5 In UBR+, the Bandwidth in SCR is replaced by Bandwidth in PCR divided by 4. 6 A request can be related to different VPs at the same time on one or more different sites. 7 Activation fee per VP : limited to 1 per VP type & per LEX. 12

13 5 to the Annex 5 & 5A in BROBA and in Annex G in BRUO : Lines that are being moved in the framework of migrations (Single & Mass) are excluded from the SLA or ISLA timers, availability and compensations conditions during the moving process. migration to the Annex K Migration for BRUO and BROBA