Broadband Roadmap – Existing products.ppt

business unit (if required) business unit (if required) MSAN Interconnect Update from Experts’ Group 18th April 2005 Paul RosbothamCo-chair Agenda What’s been going on since our last meeting? Why two distinct requirements? MSAN Point of Handover MSAN Voice Access Next steps What’s been going on since the last meeting? After the last meeting an Experts Group was formed Involvement of BT Wholesale, CW, Energis, Global Crossing, ntl, Telewest Thus An “outline of requirements” developed to scope the discussion area Various meetings held between the altnets Two meetings held with BT Much of the delay has been because of the difficulty in organising these meetings Participants are heavily committed to NGN activity in NICC/Consult21 MSAN Interconnect not seen as highest priority Requirements have been developed Fully agreed for MSAN Point of Handover Largely agreed for MSAN Voice Access Why two sets of requirements? In discussions it became clear that two sets of requirements were being intermingled/confused: A requirement for physical handover of capacity at the MSAN layer This is being termed “MSAN Point of Handover” A requirement for functional control of the MSAN equipment, particularly for baseband voice This is being termed “MSAN Voice Access” The requirements are largely (but not totally) independent of one another MSAN Point of Handover MSAN Point of Handover foresees the provision of the multiservice pipe at the MSAN layer rather than solely at Metronodes. The motivation of MSAN Point of Handover is based upon the premise that the fewer network elements traversed, the lower the cost The driver is that by substituting BT backhaul from the Metronode to MSAN location with their own, operators may be able to reduce conveyance costs MSAN Point of Handover The Experts Group has not gone into the technical detail of the multiservice pipe The logic is that the same standards as used at the Metronode level will apply at the MSAN level These