1. Backhaul Design - UCLL and Sub-loop
Final

2. Why does Chorus believe draft STD Sub-loop Backhaul is inappropriate
Draft STD proposed Sub-loop Backhaul links are simply dark fibre. It is not possible for Chorus to provide the SFPs due to their proprietary nature, but even if it were the service would functionally be dark fibre.
Dark fibre services are those where only the fibre is provided with no electronics monitoring or managing service.
Dark fibre is inappropriate as a regulated backhaul services;
The Service Description in the Act does not regulate dark fibre.
No ability to manage link especially speed and fault resolution.
Precludes building an efficient network.
Proposed sub-loop solution is incompatible with UCLL backhaul.
The draft STD has specified a Sub-loop Backhaul Service that is essentially dark fibre provided by chorus and an SFP interface device provided by either Chorus or the Access Seeker. Aside from issues about the jurisdictional appropriateness of this solution, there are issues with its implementation. As Chorus, Vodafone and Telecom Group have all previously submitted that the SFP’s are specific to DSLAM equipment and are generally provided by the manufacturer of that equipment so Chorus will be unable to provide them,
Lack of visibility of the Sub-loop Backhaul links by Chorus management systems will cause several difficulties with the assure process;
It will not be possible to predict laser failure as aging occurs [weak argument as access seeker can monitor and it is their laser].
Reliant on Access Seeker to advise of failure i.e. no proactive fault response.
Once reported there will be delays in location and repair of faults. No work can be done remotely to locate fault man in van will have to work from one end of link with test equipment. Will also mean increased end user disruption of degraded link as it will have to be taken out of service to test.

3. How Chorus builds the regulated UCLL backhaul service
The UCLL Backhaul service uses of regional backhaul network, Ethernet switches and core transport.
Primary link from Local Exchange to POI and Secondary link from POI to ASNAPOI.
Chorus would, given the opportunity, build the Sub-loop backhaul in the same manner as the UCLL Backhaul service will be provided. In most cases, the UCLL Backhaul service will involve use of Ethernet switches and core transport. For example, a fibre pair to an exchange based Ethernet switch providing circuit management as indicated.
Note local exchange can be POI or ASNAPOI and POI can be ASNAPOI

4. How Chorus intends to build the regulated sub-loop backhaul service
Sub-loop backhaul would be built from the same toolkit of local and regional fibre, media converters or Ethernet switches and core transport as the UCLL backhaul.
The exact mix of components will depend on the location, distance and speed required by the Access Seeker.
This will enable Sub-loop backhaul to be seamlessly connected to UCLL backhaul when there is no co-located equipment.
Hence, the Sub-loop backhaul would be built from the same toolkit of local and regional fibre, media converters, Ethernet switches and core transport as the UCLL backhaul. The exact mix of components will depend on the location, distance and speed required by the Access Seeker.

5. Why does Chorus need Management Visibility of Sub-loop Backhaul
Visibility of the Sub-loop Backhaul links by Chorus management systems will provide the following benefits with the assure process;
It will be possible to predict laser failure as aging occurs.
Chorus will not be reliant on Access Seeker to advise of failure.
When fault is reported initial location can be done remotely to direct fault man in van to the most likely fault location.
This will mean decreased end user disruption of degraded link.
The draft STD has specified a Sub-loop Backhaul Service that is essentially dark fibre provided by chorus and an SFP interface device provided by either Chorus or the Access Seeker. Aside from issues about the jurisdictional appropriateness of this solution, there are issues with its implementation. As Chorus, Vodafone and Telecom Group have all previously submitted that the SFP’s are specific to DSLAM equipment and are generally provided by the manufacturer of that equipment so Chorus will be unable to provide them,
Lack of visibility of the Sub-loop Backhaul links by Chorus management systems will cause several difficulties with the assure process;
It will not be possible to predict laser failure as aging occurs.
Reliant on Access Seeker to advise of failure i.e. no proactive fault response.
Once reported there will be delays in location and repair of faults. No work can be done remotely to locate fault man in van will have to work from one end of link with test equipment. Will also mean increased end user disruption of degraded link as it will have to be taken out of service to test.

6. How much backhaul do you need
Circuit Speed
Mbit/sec per user
Number of users at
Mbit/sec 25 50 75
100
200
100kbit/sec
32kbit/sec
1.00
0.50
0.33
0.25
0.13
250
781
2.00
0.67
500
1,563
4.00
1.33
1,000
3,125
8.00
2.67
2,000
6,250
1000
40.00
20.00
13.33
10.00
5.00
10,000
31,250

7. Summary Dark fibre inappropriate
Better to have same build components for Sub-loop and UCLL backhaul and provide a managed service
The Sub-loop Service we have proposed provides multiple speed options