Technical Handbook. open eir 1 NGA National Deployment Virtual Unbundled Access Products Bitstream Plus Products. 01/07/17 Version PDF Free Download

Technical Handbook open eir 1 NGA National Deployment Virtual Unbundled Access Products Bitstream Plus Products 1 open eir is a trading name of limited, Registered as a Branch in Ireland Number 907674, Incorporated in Jersey Number 116389, Branch Address : 1 Road, Dublin 8 01/07/17 Version 21.0 - Final 1

Version Control Version Status Update Effective Date 17 20 Minor changes in the figures 12/10/2016 V21 Final This document is based on V20 Implementation of Standardised Change Control 01/07/2017 This document follows change control procedure: Proposed is defined as a document status when the approved document is uploaded to Proposals Section of open eir Website. Final is defined as a document status when the approved document is uploaded to the relevant section of the open eir Website following the publication period. For information: Historical Document History Table located at end of Document. Publish means the action of uploading a document to the website regardless of status or location. control operates. 01/07/17 Version 21.0 - Final 2

Table of Contents 1. Introduction...9 2. Products Overview...9 2.1 Virtual Unbundled Access Products...9 2.1.1 Virtual Unbundled Access Unicast... 10 2.1.1.1 FTTC Virtual Unbundled Access Unicast... 10 2.1.1.2 FTTH Virtual Unbundled Access - Unicast... 10 2.1.2 Virtual Unbundled Access Multicast... 11 2.1.3 Virtual Unbundled Access Redundancy... 12 2.2 Bitstream Plus Products... 13 2.2.1 Bitstream Plus Unicast... 13 2.2.1.1 FTTC Bitstream Plus Unicast... 14 2.2.1.2 FTTH Bitstream Plus Unicast... 14 2.2.2 Bitstream Plus Unicast Redundancy... 15 2.2.3 Bitstream Plus Multicast... 16 2.2.4 Bitstream Plus Multicast Redundancy... 17 2.3 PNs per Operator... 18 2.4 Access Types... 18 3. Network Solution Overview Virtual Unbundled Access... 21 3.1 Unicast: End- -NNI) Traffic Flow... 21 3.2 Unicast: WEIL (E- -User Traffic Flow... 25 3.3 Multicast: End- -NNI) Traffic Flow... 28 4. Network Solution Overview Bitstream Plus Products... 31 4.1 Unicast: End- -NNI) Traffic Flow... 31 4.2 Unicast: WEIL (E- -User Traffic Flow... 35 4.3 Bitstream Plus Multicast: End- -NNI) Traffic Flow... 38 4.4 Unicast Implementation... 42 4.5 Multicast Implementation... 43 01/07/17 Version 21.0 - Final 3

4.5.1 Access Node customer multicast settings... 46 5. VLAN Management, Forwarding Model and Security... 48 5.1 VLAN Management... 48 5.2 Forwarding Model... 48 5.3 Security... 49 6. WEIL and NGA... 50 7. QoS and Service Bandwidth... 53 8. FTTC VDSL2 Implementation... 58 9. VDSL2 CPE Requirements... 58 10. open eir equipment installed at user premises (, )... 62 Appendix I Installation Manual Appendix II Installation Manual List of Figures Figure 1: FTTC Virtual Unbundled Access Unicast...10 Figure 2: FTTH Virtual Unbundled Access Unicast...11 Figure 3: Virtual Unbundled Access Multicast...12 Figure 4: Virtual Unbundled Access Redundancy...13 Figure 5: FTTC Bitstream Plus Unicast...14 Figure 6: FTTH Bitstream Plus Unicast...15 Figure 7: Bitstream Plus Unicast Redundancy...15 Figure 8: Bitstream Plus Multicast...17 Figure 9: Bitstream Plus Multicast Redundancy...17 Figure 10: Virtual Unbundled Access: End- -NNI Traffic Flow single VPLS per Operator...21 Figure 11 Virtual Unbundled Access: End- -NNI Traffic Flow...22 Figure 12: Virtual Unbundled Access: E- -User Traffic Flow single VPLS instance per Operator...25 Figure 13 Virtual Unbundled Access: E- -User Traffic Flow multiple VPLS instances per Operator 26 Figure 14 Virtual Unbundled Access Multicast: End- -NNI) Traffic Flow single VPLS per Operator...28 Figure 15 Virtual Unbundled Access Multicast: End- -NNI) Traffic Flow Operator...29 Figure 16: Bitstream Plus Fibre/VDSL2 Access: End- -NNI Traffic Flow single VPLS per Operator...31 Figure 17 Bitstream Plus Fibre/VDSL2 Access: End- -NNI Traffic Flow 32 01/07/17 Version 21.0 - Final 4

Figure 18: Bitstream Plus Fibre/VDSL2 Access: E- -User Traffic Flow single VPLS per Operator...35 Figure 19 Bitstream Plus Fibre/VDSL2 Access: E- -User Traffic Flow - multiple VPLS's per Operator.36 Figure 20: Bitstream Plus Multicast: End- -NNI) Traffic Flow single VPLS/MVPN per Operator...38 Figure 21: Bitstream Plus Multicast: End- -NNI) Traffic Flow Operator...39 Figure 22: Network Solution Unicast Traffic...42 Figure 23: Network Solution - Multicast Implementation...43 Figure 24: Wholesale Ethernet Interconnect Link...44 Figure 25: Access Node Forwarding Model...49 Figure 26 NGA site with WEIL on "non-nga" NGN node...52 Figure 27: Service Multiplexing and SABs...55 01/07/17 Version 21.0 - Final 5

List of Tables Table 1 Access node multicast user settings...47 Table 2 Mapping of C-VLAN 802.1p bit markings to forwarding classes...53 Table 3: Multicast Bandwidth Options...54 Table 4: High Speed Internet FTTH Profiles...55 Table 5: High Speed Internet Rate Adaptive VDSL2 Profiles...56 Table 6: High Stability VDSL2 profiles (from Exchange DSLAM)...57 Table 7: High Stability VDSL2 profiles (from Cabinet DSLAM)...57 Table 8 Overview of FTTC VDSL2 Implementation...58 Table 9 Key Diagnostic and Test parameters to be reported by CPE...61 Table 10: Specification...62 01/07/17 Version 21.0 - Final 6

Acronyms AES AF BGP BPU BPM CoS CSID C-VLAN DHCP DoS DSL DSLAM EF EVDSL E-NNI EXP FC FTTC FTTH FTTx GEM GPON IGMP IP LAN MAC MED MP-BGP MPLS MVPN NGA NGN ODF OLT PE PIM Advanced Encryption Standard Assured Forwarding Border Gateway Protocol Bitstream Plus Unicast Bitstream Plus Multicast Class of Service Calling Station ID Customer Virtual Local Area Network Dynamic Host Configuration Protocol Denial of Service Digital Subscriber Line Digital Subscriber Line Access Multiplexer Expedited Forwarding Exchange launched VDSL External Network to Network Interface Experimental Forwarding Class Fibre To The Cabinet Fibre To The Home Fibre To The x GPON Encapsulation Method Gigabit Passive Optical Network Internet Group Management Protocol Internet Protocol Local Ethernet Network Media Access Control MULTI_EXIT_DISCRIMINATOR (BGP4) Multi Protocol-Border Gateway Protocol Multiprotocol Label Switching Multicast VPN Next Generation Access Next Generation Network Network Termination Unit Optical Distribution Frame Optical Line Terminal Optical Network Terminal Provider Edge Protocol Independent Multicast 01/07/17 Version 21.0 - Final 7

PON POTS QoS RP SAB S-VLAN UG VDSL VLAN VAU VAM VoIP VUA WEIL WSEA Passive Optical Network Plain old telephone service Quality of Service Rendezvous Point Service Access Bandwidth Service - Virtual Local Area Network Unified Gateway Very high bit-rate Digital Subscriber Line Virtual Local Area Network Virtual Unbundled Access Unicast Virtual Unbundled Access Multicast Voice over Internet Protocol Virtual Unbundled Access Wholesale Ethernet Interconnect Link Wholesale Symmetrical Ethernet Access 01/07/17 Version 21.0 - Final 8

1. Introduction The purpose of this document is to provide a technical description of the open eir Next Generation Access (NGA) Fibre To The Home (FTTH) and VDSL/Fibre To The Cabinet (FTTC) based products, in order to assist Operators in the design and development of their own product offerings. In the FTTH product, GPON technology is used over a Fibre l ises and the OLT in the Access Network. The OLT is connected to the NGN over a Fibre link. premises and the DSLAM in the Access Network. The DSLAM is installed in the Street Cabinet or in the Exchange. The DSLAM is connected to the NGN over a Fibre link. Please note that this is a working document and therefore subject to regular updates as new products and product enhancements are introduced. 2. Products Overview This section provides a high level overview of the open eir Next Generation Access (NGA) fibreand copper/vdsl based products. Two separate product ranges are available: Virtual Unbundled Access (VUA) and Bitstream Plus (BP). 2.1 Virtual Unbundled Access Products The open eir 2 NGA Virtual Unbundled Access (VUA) products provide generic Ethernet access, with traffic-based CoS, between an End-User premises and a WEIL at an Operator handover point. Virtual Unbundled Access is available where the Operator has a presence in the open eir exchange that has an open eir NGN node connected to the Access-node (OLT and/or DSLAM). 2 open eir is a trading name of Limited, Registered as a Branch in Ireland Number 907674, Incorporated in Jersey 01/07/17 Version 21.0 - Final 9

2.1.1 Virtual Unbundled Access Unicast The Virtual Unbundled Access Unicast service provides an individual connection for each End- User. Unicast traffic from each access node within an open eir NGN node footprint is assigned to a single Virtual Private LAN Service (VPLS) per Operator. Aggregated End-User traffic belonging to an Operator within that NGN node footprint is presented in a single VLAN at the point of handover to the Operator. 2.1.1.1 FTTC Virtual Unbundled Access Unicast FTTC Virtual Unbundled Access provides high speed broadband access over a dedicated copper pair using VDSL2 copper access technology from a DSLAM installed in the streetside cabinet and/or in the Exchange. The service demarcation point is the Copper in the End-User premises. The VDSL2 bandwidth options are outlined in the following Tables; Table 5: High Speed Internet Rate Adaptive VDSL2 Profiles Table 6: High Stability VDSL2 profiles (from Exchange DSLAM) Table 7: High Stability VDSL2 profiles (from Cabinet DSLAM). NGN Node SAB DSLAM VPLS Exchange ODF FTTC VUA Access VUA Unicast Logical Connection WEIL Figure 1: FTTC Virtual Unbundled Access Unicast 2.1.1.2 FTTH Virtual Unbundled Access - Unicast FTTH Virtual Unbundled Access provides high speed broadband access over a Gigabit Passive Optical Network (GPON) network. Each End-User port is a 1Gbps 100/1000Base-T interface with 01/07/17 Version 21.0 - Final 10

an RJ-45 connector that will have a configured speed determined by the customer s profile. For list of customer profiles reference Table 4: High Speed Internet FTTH Profiles NGN Node SAB Exchange OLT VPLS ODF FTTH VUA Access VUA Unicast Logical Connection WEIL Figure 2: FTTH Virtual Unbundled Access Unicast 2.1.2 Virtual Unbundled Access Multicast All Virtual Unbundled Access products can support multicast traffic, which is available as an additional service. Where multicast is required a dedicated VPLS per Operator is set up to handle all multicast traffic within the NGN node. Multicast traffic can be presented on a VLAN on the same SAB as the unicast traffic, or on a dedicated SAB. 01/07/17 Version 21.0 - Final 11

DSLAM NGN Node VPLS Exchange ODF OLT FTTH/FTTC VUA Access VUA Multicast Logical Connection Figure 3: Virtual Unbundled Access WEIL Multicast 2.1.3 Virtual Unbundled Access Redundancy Virtual Unbundled Access redundancy allows the Operator to order multiple VUA connections to multiple WEILs, in order to provide redundancy for the same VUA access traffic. This protects against failure of the WEIL. Broadcast traffic (e.g. DHCP Discover messages) will be forwarded to both WEILs. Unicast traffic will be forwarded to one WEIL based on MAC learning in the VPLS. Split horizon is applied to the VPLS to prevent routing loops. 01/07/17 Version 21.0 - Final 12

DSLAM NGN Node VPLS Exchange ODF OLT VUA Unicast/Multicast Access VUA Unicast/Multicast Logical Connection WEIL Figure 4: Virtual Unbundled Access Redundancy 2.2 Bitstream Plus Products The open eir NGA Bitstream Plus products provide generic Ethernet access, with traffic-based CoS, between an End-User Operator products are delivered over the following access platforms; Fibre to the Home (FTTH), over a Fibre Line using GPON technology from an OLT installed in the Exchange Fibre to the Cabinet (FTTC) Over a Copper line using VDSL2 technology from an Exchanch DSLAM (EVDSL) or the Cabinet DSLAM Each product provides an enhanced broadband access service between the Service Termination Point (STP), at the End-User premises, and the WEIL at the Operator handover point. 2.2.1 Bitstream Plus Unicast The Bitstream Plus Unicast service supports an individual connection for each End-User. Unicast traffic from each access node within an NGN node footprint is assigned to a single Virtual Private LAN Service (VPLS) per Operator. Aggregated End-User traffic belonging to an Operator 01/07/17 Version 21.0 - Final 13

within that NGN node footprint is presented in a single VLAN at the point of handover to the Operator. 2.2.1.1 FTTC Bitstream Plus Unicast FTTC Bitstream Plus Unicast provides high speed broadband access over a dedicated copper pair using VDSL2 copper access technology from a DSLAM. The service demarcation point is the Copper in the End-User premises. The VDSL2 bandwidth options are outlined in the following Tables;, Table 5: High Speed Internet Rate Adaptive VDSL2 Profiles Table 6: High Stability VDSL2 profiles (from Exchange DSLAM) Table 7: High Stability VDSL2 profiles (from Cabinet DSLAM). DSLAM NGN Node VPLS NGN NGN Node Operator Handover Site SAB FTTC BP Access BP Unicast Logical Connection WEIL Figure 5: FTTC Bitstream Plus Unicast 2.2.1.2 FTTH Bitstream Plus Unicast FTTH Bitstream Plus Unicast provides high speed broadband access over a Gigabit Passive Optical Network (GPON) network. Each End-User port is a 1Gbps 100/1000Base-T interface with an RJ-45 connector that will have a configured speed determined by the customer s profile. For list of customer profiles reference Table 4: High Speed Internet FTTH Profiles 01/07/17 Version 21.0 - Final 14

OLT NGN Node VPLS NGN NGN Node Operator Handover Site SAB FTTH BP Access BP Unicast Logical Connection WEIL Figure 6: FTTH Bitstream Plus Unicast 2.2.2 Bitstream Plus Unicast Redundancy Bitstream Plus Unicast Redundancy allows the Operator to order multiple BPU logical connections to multiple WEILs, in order to provide redundancy for the same BPU access traffic. The VPLS is local to the NGN node and there are separate E-Line services going to the different WEILs. This protects against failure of the BPU connection or the WEIL. Broadcast traffic (e.g. DHCP Discover messages) will be forwarded to both WEILs. Unicast traffic will be forwarded to one WEIL based on MAC learning in the VPLS. Split horizon is applied to the VPLS to prevent routing loops. DSLAM NGN Node NGN NGN Node Operator Handover Site A OLT VPLS NGN Node Operator Handover Site B FTTx BP Access BP Unicast Logical Connection WEIL Figure 7: Bitstream Plus Unicast Redundancy 01/07/17 Version 21.0 - Final 15

2.2.3 Bitstream Plus Multicast All Bitstream Plus products support multicast traffic, which is available as an additional service. Where multicast is required a dedicated VPLS per Operator is set up to handle all multicast traffic within an NGN node. All VPLSs for an Operator are joined to a single Multicast VPN (MVPN). Multicast traffic can be presented on a VLAN on the same SAB as the unicast traffic, or on a dedicated SAB. The default implementation of the Bitstream Plus Multicast Service requires a Rendezvous Point (RP) to be specified by the Operator because the use of IGMPv2 requires PIM-SM and a Rendezvous Point. If a well-known source address is used, a static mapping (i.e. (*,G) -> (S,G)) can be implemented such that IGMPv2 can continue to be used, but PIM-SM can be replaced with PIM-SSM. A Rendezvous Point will therefore no longer be required. In that case, when placing the BPM order, the Operator should specify the source address to which the (*,G) should be mapped instead of the RP. 01/07/17 Version 21.0 - Final 16

DSLAM NGN OLT NGN Node VPLS PE PE MVPN PE PE NGN Node Operator Handover Site SAB FTTx BP Access BP Multicast Logical Connection WEIL Figure 8: Bitstream Plus Multicast 2.2.4 Bitstream Plus Multicast Redundancy Bitstream Plus Multicast Redundancy allows the Operator to order multiple BPM logical connections to multiple WEILs, in order to provide redundancy for the same BPM access traffic. The VPLS service on the NGN node is connected to two separate PE nodes within an NGN region. This protects against failure of the BPM connection or the WEIL. If both WEILs are advertising the RP in BGP, then IGMP joins will be forwarded based upon BGP best path selection. The Operator can influence this using the MED. Split horizon is applied to the VPLS to prevent routing loops. Master Socket Master Socket DSLAM Master Socket NGN Node PE NGN PE NGN Node Operator Handover Site A OLT VPLS PE MVPN PE SAB NGN Node Operator Handover Site B FTTx BP Access BP Multicast Logical Connection WEIL Figure 9: Bitstream Plus Multicast Redundancy 01/07/17 Version 21.0 - Final 17

2.3 An Operator may order up to 10 local accesses at each NGA site for each service type (Bitstream Plus Unicast, Bitstream Plus Multicast, VUA Unicast, VUA Multicast). The traffic is VLAN separated at the local access, is forwarded into a separate VPLS per VLAN, is carried across the network in a separate VLL/MVPN (Bitstream Plus only), and may be handed off either at a single WEIL or separate WEIL handoff points. Within the ordering systems, to distinguish the VLAN/VPLS When the Operator is placing access orders for individual VDSL/GPON connections, an Operator who has multiple Egress Groups must specify the Egress Group to which the VDSL/GPON connection is to be associated. Where an Operator has a single Egress Group, all. The Multicast Egress Group must be linked to the associated Unicast Egress Group within Bitstream Plus and within VUA. 2.4 Access Types The open eir NGA deployment uses the N:1 model for residential services, where there is one SVLAN defined per Operator (per Egress Group). CVLANs are not used in this model. Two access types are supported: DHCP/DHCPv6-based IPoE PPPoE The DSLAM/OLT will not forward traffic unless either DHCP/DHCPv6 or PPPoE is used. When a packet is received, the DSLAM will study the source MAC and VLAN,then record the MAC and VLAN in a table. After this the packet is sent out. The security functions (anti-ipspoofing and antimacspoofing) implemented require that PPPOE or DHCP/DHCPv6 is used to establish the session, otherwise the packet is considered illegal and will be discarded. The MAC filter becomes effective after the DHCP ACK, until the ip address is released,or when a PADT (for PPPOE) is sent. For session establishment of PPPOE or DHCP/DHCPv6,the DSLAM complies with stipulations in the agreement RFC 3315, RFC 2131 and RFC 2516. 01/07/17 Version 21.0 - Final 18

In the case of DHCP, Option 82 for IPv4 is enabled to allow the passing of the Circuit Identifier (CID) and Remote Identifier BRAS/BNG. Similarly in the case of DHCPv6, Option 18 for IPV6 is enabled to allow the passing of the Circuit Identifier (CID) and Remote Identifier (RID) in DHCPv6 packets relayed by the DSLAM/OLT to In the case of PPPoE, authentication is done in the PPP CHAP or PAP session but there is an additional tag that is added (PPPoE+ Intermediate Agent) by the DSLAM/OLT which inserts the physical location of the user. In the case of DHCP, DHCPv6 and PPPoE, the format of the Circuit Identifier is the same: VDSL2 access: <DSLAM Name> eth <Frame>/<Slot>/<Port> e.g. DDM1_061A eth 0/2/0 Note that due to a current software limitation of the DSLAM, open eir recommends enabling only the IA_PD request on the IPV6 DHCPv6 client CPE, unless the CPE supports IAPD & IANA joint DHCPv6 renews. The DSLAM as part of the network security design supports IPv6 anti-spoofing by binding IPv6 settings to a port used by the customer. Currently the DSLAM updates these security port bindings when a DHCPv6 renew packet is received. Some vendor CPEs updates the IANA & IAPD subnets at different time intervals. As a consequence, one of the client subnets will be blocked by the DSLAM IPv6 anti-spoofing mechanism. GPON access: <OLT Name> xpon <Frame>/<Slot>/<Port>:<>.<GEM>.<VLAN> e.g. SND99 xpon 0/1/0:6.1.10 There are 3 Virtual lines. These 3 Virtual lines are mapped into 3 GEM ports over each cu. If the CPE sends Traffic in the upstream to the ; With VLAN 10, pbit-0. will map it into GEM port 1 01/07/17 Version 21.0 - Final 19

With VLAN 10, pbit-2. will map it into GEM port 2 With VLAN 10, pbit-4. will map it into GEM port 3 The Access Node (OLT) will send CSID to the Radius for authentication. This is based on which particular GEM port it receives the PPPoE Active Discovery Initiation (PADI) or IPoE DHCP Discovery message from the CPE side. If the CPE sends PPPoE Active Discovery Initiation (PADI) or IPoE DHCP Discovery with VLAN 10 pbit-0. Access Node (OLT) will send the following CSID for authentication <OLT Name> xpon <Frame>/<Slot>/<Port>:<>.<GEM 1>.<VLAN> e.g. SND99 xpon 0/1/0:6.1.10 If the CPE sends PPPoE Active Discovery Initiation (PADI) or IPoE DHCP Discovery with VLAN 10 pbit-2. Access Node (OLT) will send the following CSID for authentication <OLT Name> xpon <Frame>/<Slot>/<Port>:<>.<GEM 2>.<VLAN> e.g. SND99 xpon 0/1/0:6.2.10 If the CPE sends PPPoE Active Discovery Initiation (PADI) or IPoE DHCP Discovery with VLAN 10 pbit-4. Access Node (OLT) will send the following CSID for authentication <OLT Name> xpon <Frame>/<Slot>/<Port>:<>.<GEM 3>.<VLAN> e.g. SND99 xpon 0/1/0:6.3.10 01/07/17 Version 21.0 - Final 20

3. Network Solution Overview Virtual Unbundled Access This section provides a high-level technical overview of how the open eir Virtual Unbundled Access (VUA) products are supported on the open eir NGN network. 3.1 Unicast: End-User -NNI) Traffic Flow 1 12 13 14 15 17 CPE S-VLAN OLT End-User Traffic 802.1p marking (C -VLAN 10) Access Connections VPLS S-VLAN Operator Network CPE C-VLAN S-VLAN ODF Exchange DSLAM NGN Node 1a 2a 1 6 Figure 10: Virtual Unbundled Access: End-User -NNI Traffic Flow single VPLS per Operator 01/07/17 Version 21.0 - Final 21

1 1212 1313 1414 1515 RG (CPE) S -VLAN 2 S - VLAN 2 RG (CPE) S -VLAN 1 S - VLAN 1 OLT NGN Node End User Traffic 802.1p marking (C -VLAN 10) VDSL DSLAM VPLS # 1 RG (CPE) VDSL modem Master Socket C -VLAN S -VLAN 1 VPLS # 2 S -VLAN 2 RG (CPE) VDSL modem Master Socket C -VLAN 2a 3a 1 6 1 7 1a Operator Network S -VLAN S -VLAN 2 Figure 11 Virtual Unbundled Access: End- Operator -NNI Traffic Flow The following describes how unicast End-User traffic is treated in the End-User -NNI direction: 1. Fibre access: End-User broadband traffic is presented to the open eir network at a physical port on the (Optical Network Terminal) which is installed at the End-User site. a) VDSL2 access: End-User broadband traffic is presented to the open eir network at the Copper. 01/07/17 Version 21.0 - Final 22

The End-User traffic presented at the / will be VLAN tagged (VLAN 10). The End- User CPE will generate the Ethernet frames with a VLAN tag of 10 and 802.1p QoS markings. 2. Fibre access: The will swap VLAN ID 10 with an S-VLAN tag to identify the Operator (and The assigned S-VLAN ID is not visible to either the End-User or the Operator. The 802.1p QoS markings will be preserved. a). VDSL2 access: The DSLAM will swap VLAN ID 10 with an S-VLAN tag to identify the Operator. The assigned S-VLAN ID is not visible to either the End-User or the Operator. The 802.1p QoS markings will be preserved. 3. The OLT/DSLAM will forward traffic to the open eir NGN node tagged with the S-VLAN ID. The OLT/DSLAM acts as a DHCP relay and inserts DHCP Option82 & DHCPv6 option 18 information including the physical port that will support user identification and authorization. The Option82/Option18 Calling Station ID (CSID) format is as follows: Fibre access: <OLT Name> xpon <Frame>/<Slot>/<Port>:<>.<GEM>.<VLAN> e.g. SND99 xpon 0/1/0:6.1.10 VDSL2 access: <DSLAM Name> eth <Frame>/<Slot>/<Port> e.g. DDM1_061A eth 0/2/0 The DHCP option-82 & DHCPv6 Option 18 remote-id is set to the telephone number. Example below: DHCP options: [82] Relay agent information: len = 35 01/07/17 Version 21.0 - Final 23

[1] Circuit-id: NUT1_001A eth 0/1/8 [2] Remote-id: 8881-4329662 4. The S-VLAN will act as the service selector at the open eir NGN node to map the traffic to the appropriate Virtual Private LAN Service (VPLS). 5. A service policy (i.e. CoS profile/bandwidth) is applied to End-User traffic associated with the S-VLAN and the End-User traffic is mapped to the appropriate Forwarding Class (FC) within the core NGN network. The S-VLAN tag is removed and the End-User traffic is carried within a Local Virtual Leased Line to the port on the open eir NGN node associated with the WEIL. 6. An S-VLAN tag that identifies the source open eir NGN node is added to the End-User traffic on egress of the open eir NGN Node WEIL port and the appropriate CoS profile is applied to the End-User traffic. 7. The open eir NGN E-NNI optical port is presented on the open eir ODF located in the open eir exchange. The E-NNI port is configured as an 802.1ad port. The default is for open eir to assign the S-VLAN ID presented at the E-NNI. The assigned S-VLAN ID will be in the range 10 4000. The Operator can optionally specify the S-VLAN ID presented at the E-NNI. If the Operator chooses to specify their own S-VLAN ID on a specific E-NNI, then the Operator will be responsible for specifying all S-VLAN IDs within the range 10-4000 on that E-NNI. Traffic from each VPLS instance will be presented on a different S-VLAN. 01/07/17 Version 21.0 - Final 24

3.2 Unicast: WEIL (E- End-User Traffic Flow 16 15 14 13 1 CPE S-VLAN OLT End-User Traffic 802.1p marking (C -VLAN 10) Access Connections VPLS S-VLAN Operator Network CPE C-VLAN S-VLAN ODF Exchange DSLAM NGN Node 6a 5a 4a 2 Figure 12: Virtual Unbundled Access: E- End-User Traffic Flow single VPLS instance per Operator 01/07/17 Version 21.0 - Final 25

16 1215 1314 1513 RG (CPE) S -VLAN 2 S - VLAN 2 RG (CPE) S -VLAN 1 S - VLAN 1 OLT NGN Node End User Traffic 802.1p marking (C -VLAN 10) VDSL DSLAM VPLS # 1 RG (CPE) VDSL modem Master Socket C -VLAN S -VLAN 1 VPLS # 2 S -VLAN 2 RG (CPE) VDSL modem Master Socket C -VLAN 2a 5a 3a 4a 1 62 1 1 1a 6a Operator Network S -VLAN S -VLAN 2 Figure 13 Virtual Unbundled Access: E- -User Traffic Flow multiple VPLS instances per Operator The following describes how Operator unicast traffic is treated in the E- End-User direction: 1. End-User traffic is presented to the open eir NGN E-NNI optical port via the open eir ODF located in the open eir exchange. The E-NNI port is configured as an 802.1ad port. The default is for open eir to assign the S-VLAN ID presented at the E-NNI. The assigned S-VLAN ID will be in the range 10 4000. The Operator can optionally specify the S-VLAN ID presented at the E-NNI. If the Operator chooses to specify their own S-VLAN ID on a specific E-NNI, then the Operator will be responsible for specifying all S-VLAN IDs within the range 10-4000 on 01/07/17 Version 21.0 - Final 26

that E-NNI.The Operator must add an S-VLAN tag to their traffic and mark the S-VLAN 802.1p bits prior to presentation at the E-NNI. 2. A service policy (i.e. CoS profile/bandwidth) is applied to the traffic associated with the S- VLAN and the Operator traffic is mapped to the appropriate Forwarding Class (FC). The S- VLAN tag is removed and the Operator traffic is carried within a Virtual Private LAN Service (VPLS) to the /DSLAM connected port on the open eir NGN node. 3. An S-VLAN is added to the Operator traffic and the appropriate QoS is applied. The assigned S-VLAN ID is not visible to either the End-User or the Operator. 4. Fibre access: the OLT will forward traffic from the open eir NGN node to the with the S- VLAN tag. a) VDSL2 access: the DSLAM will swap the SVLAN tag that identifies the Operator with VLAN ID 10. 5. Fibre access: The will swap the S-VLAN tag that identifies the Operator with VLAN ID 10 a) VDSL2 access: the DSLAM will forward traffic from the open eir NGN node to the End- User's CPE via the Copper. 6. Fibre Access: The End-User End-User's CPE by the which is installed at the End-User site. a) VDSL2 access: The End-User End-User's CPE via the Copper. 01/07/17 Version 21.0 - Final 27

3.3 Multicast: End-User -NNI) Traffic Flow 1 2 13 14 15 7 CPE S-VLAN OLT End-User Traffic 802.1p marking (C -VLAN 10) Access Connections VPLS S-VLAN Operator Network CPE C-VLAN S-VLAN ODF Exchange DSLAM NGN Node 2a 1 6 Figure 14 Virtual Unbundled Access Multicast: End-User -NNI) Traffic Flow single VPLS per Operator 01/07/17 Version 21.0 - Final 28

1 1212 1313 1414 1515 STB RG (CPE) S-VLAN - 2 S - VLAN 2 STB NGN Node RG (CPE) S-VLAN 2 S-VLAN 1 Access Connections OLT STB DSLAM VPLS #1 RG (CPE) VDSL modem Master Socket C-VLAN S-VLAN 1 VPLS #2 STB S - VLAN 2 RG (CPE) VDSL modem 1a Master Socket C-VLAN 2a 3a 8 1 7 6 1 S-VLAN 1 Operator Network S-VLAN 2 BTV Sources Figure 15 Virtual Unbundled Access Multicast: End- -NNI) Traffic Flow The following describes how Operator multicast traffic is treated: 1. The End-User's CPE sends an IGMP Join specifying the IP multicast group it wants to join. 2. Fibre access: The swaps VLAN ID 10 with the multicast S-VLAN tag that identifies the Operator and forwards to the OLT (The performs IGMP snooping). 01/07/17 Version 21.0 - Final 29

a) VDSL2 access: The DSLAM swaps VLAN ID 10 with the multicast S-VLAN tag that identifies the Operator. 3. The OLT/DSLAM proxies the IGMP Join towards the open eir NGN node. 4. The SVLAN will act as the service selector at the open eir NGN node to map the traffic to the appropriate VPLS. There will be a VPLS for multicast per Operator at each open eir NGN node with connected access nodes. A Real-Time (EF) service policy (i.e. CoS profile/bandwidth) is applied to End-User traffic associated with the multicast S-VLAN and the End-User traffic is mapped to the appropriate EF Forwarding Class (FC). The S-VLAN tag is removed and the End-User traffic is carried within the VPLS to the logical port on the open eir NGN node associated with the WEIL. 5. An S-VLAN tag that identifies the multicast traffic is added to the End-User traffic on egress and the appropriate service policy is applied to the End-User traffic. 6. The open eir NGN E-NNI optical port is presented on the open eir ODF located in the open eir exchange. The E-NNI port is configured as an 802.1ad port. The S-VLAN ID is used to identify multicast traffic. The default is for open eir to assign the multicast S-VLAN ID presented at the E-NNI. The assigned multicast S-VLAN ID will be in the range 10 4000. The Operator can optionally specify the multicast S-VLAN ID presented at the E-NNI. If the Operator chooses to specify their own multicast S-VLAN ID on a specific E-NNI, then the Operator will be responsible for specifying all S-VLAN IDs within the range 10-4000 on that E-NNI. 7. The Operator GMP join. 8. In the reverse direction multicast traffic is forwarded by the Operator through the WEIL to the receiver. The same traffic flow as above applies in reverse. 01/07/17 Version 21.0 - Final 30

4. Network Solution Overview Bitstream Plus Products This section provides a high-level technical overview of how the open eir NGA Bitstream Plus products are supported on the open eir NGN network. 4.1 Unicast: End-User -NNI) Traffic Flow 1 12 13 14 15 16 NGN Network 17 CPE S-VLAN OLT End-User Traffic 802.1p marking (C-VLAN 10) Access Connections VPLS S-VLAN Operator Network CPE C-VLAN S-VLAN Operator Handover Site DSLAM NGN Node NGN Node 1a 2a Figure 16: Bitstream Plus Fibre/VDSL2 Access: End-User -NNI Traffic Flow single VPLS per Operator 01/07/17 Version 21.0 - Final 31

1 12 13 14 15 16 17 RG (CPE) S-VLAN 1 S-VLAN 1 NGN Network WEIL #1 E-NNI GigE Optical or Electrical Port VPLS #1 RG (CPE) S-VLAN 2 OLT S-VLAN 2 VPLS #2 S-VLAN #1 S-VLAN #2 Operator Network End User Traffic 802.1p marking (C-VLAN 10) RG (CPE) VDSL modem Master Socket C-VLAN S-VLAN 1 NGN Node NGN Node WEIL #2 Operator Handover Site S-VLAN 2 Operator Network RG (CPE) VDSL modem Master Socket C-VLAN DSLAM S-VLAN #2 Operator Handover Site 1a 2a 3a Figure 17 Bitstream Plus Fibre/VDSL2 Access: Endper Operator -NNI Traffic Flow The following describes how unicast End-User traffic is treated in the End-User -NNI direction: 1. Fibre access: End-User traffic is presented to the open eir network at a physical port on the (Optical Network Terminal) which is installed at the End-User site. a) VDSL2 access: End-User broadband traffic is presented to the open eir network at the Copper. The End-User traffic presented at the / will be VLAN tagged (VLAN 10). The End- User CPE will generate the Ethernet frames with a VLAN tag of 10 and 802.1p QoS markings. 2. Fibre access: The will swap VLAN ID 10 with an S-VLAN tag to identify the Operator. The assigned S-VLAN ID is not visible to either the End-User or the Operator. The 802.1p QoS markings will be preserved. a). VDSL2 access: The DSLAM will swap VLAN ID 10 with an S-VLAN tag to identify the Operator. The assigned S-VLAN ID is not visible to either the End-User or the Operator. The 802.1p QoS markings will be preserved. 01/07/17 Version 21.0 - Final 32

3. The OLT/DSLAM will forward traffic to the open eir NGN node tagged with the S-VLAN ID. The OLT/DSLAM acts as a DHCP relay and inserts DHCP Option82 & DHCPv6 option 18 information including the physical port that will support user identification and authorization. The Option82/Option18 Calling Station ID (CSID) format is as follows: Fibre access: <OLT Name> xpon <Frame>/<Slot>/<Port>:<>.<GEM>.<VLAN> e.g. SND99 xpon 0/1/0:6.1.10 VDSL2 access: <DSLAM Name> eth <Frame>/<Slot>/<Port> e.g. DDM1_061A eth 0/2/0 4. The S-VLAN will act as the service selector at the open eir NGN node to map the traffic to the appropriate Virtual Private LAN Service (VPLS). 5. A service policy (i.e. CoS profile/bandwidth) is applied to End-User traffic associated with the S-VLAN and the End-User traffic is mapped to the appropriate Forwarding Class (FC) within the core NGN network. The S-VLAN tag is removed and the End-User traffic is carried within a VPLS across the open eir Core NGN network. 6. An S-VLAN tag that identifies the source open eir NGN node is added to the End-User traffic on egress of the open eir Core NGN network and the appropriate CoS profile is applied to the End-User traffic. 7. The End-User traffic is passed to the open eir managed located at the Operator handover site. The S-VLAN on the network-facing port is mapped to the Operator facing port on the (E-NNI port). The E-NNI port is configured as an 802.1ad port. The default is for open eir to assign the S-VLAN ID presented at the E-NNI. The assigned S-VLAN ID will be in the range 10 4000. The Operator can optionally specify the S-VLAN ID presented at the E-NNI. If 01/07/17 Version 21.0 - Final 33

the Operator chooses to specify their own S-VLAN ID on a specific E-NNI, then the Operator will be responsible for specifying all S-VLAN IDs within the range 10-4000 on that E-NNI. The S-VLAN ID is used to identify the open eir NGN node associated with the Bitstream Plus Unicast (BPU) fibre and VDSL2 access. The 802.1p bits marked by the End- are not preserved through the network because the SVLAN is stripped off however the QoS is preserved because the 802.1p bits on the SVLAN at the WEIL are marked according the MPLS EXP bits i.e. CPE SVLAN 802.1p bits 0, 2 and 4 map into MPLS EXP bits 0, 2 and 4, which in turn map to 802.1p bits 0, 2 and 4 on the SVLAN at the WEIL. In the event that an Operator has more than one WEIL, an Operator must specify which WEIL is to be associated with each BPU connection. 01/07/17 Version 21.0 - Final 34

4.2 Unicast: WEIL (E- -User Traffic Flow 16 15 14 13 12 NGN Network 1 CPE S-VLAN OLT End-User Traffic 802.1p marking (C-VLAN 10) Access Connections VPLS S-VLAN Operator Network CPE C-VLAN S-VLAN Operator Handover Site DSLAM NGN Node NGN Node 6a 5a 4a Figure 18: Bitstream Plus Fibre/VDSL2 Access: E- End-User Traffic Flow single VPLS per Operator 01/07/17 Version 21.0 - Final 35

16 15 14 13 12 1 RG (CPE) S-VLAN 1 S-VLAN 1 NGN Network WEIL #1 E-NNI GigE Optical or Electrical Port VPLS #1 RG (CPE) S-VLAN 2 S-VLAN 2 S-VLAN #1 Operator Network OLT VPLS #2 S-VLAN #2 End User Traffic 802.1p marking (C-VLAN 10) RG (CPE) VDSL modem Master C-VLAN S-VLAN 1 NGN Node NGN Node WEIL #2 Operator Handover Site Socket S-VLAN 2 Operator Network RG (CPE) VDSL modem Master Socket C-VLAN DSLAM S-VLAN #2 Operator Handover Site 6a 5a 4a Figure 19 Bitstream Plus Fibre/VDSL2 Access: E- per Operator -User Traffic Flow - multiple VPLS's The following describes how Operator unicast traffic is treated in the E- End-User direction: 1. Broadband End-User traffic is presented to the open eir network at a physical port (E-NNI) on an open eir managed located at the Operator handover site. The E-NNI port is configured as an 802.1ad port. The default is for open eir to assign the S-VLAN ID presented at the E-NNI. The assigned S-VLAN ID will be in the range 10 4000. The Operator can optionally specify the S-VLAN ID presented at the E-NNI. If the Operator chooses to specify their own S-VLAN ID on a specific E-NNI, then the Operator will be responsible for specifying all S-VLAN IDs within the range 10-4000 on that E-NNI. The Operator must add this S-VLAN tag to their traffic and mark the S-VLAN 802.1p bits prior to presentation at the E-NNI. The S- VLAN tag is associated with the open eir NGN node connected to the destination OLT/DSLAM (and the VPLS instance if the Operator has more than one at that NGA site). 2. A service policy (i.e. CoS profile/bandwidth) is applied to the traffic associated with the S- VLAN and the Operator traffic is mapped to the appropriate Forwarding Class (FC) within the open eir Core NGN network. The S-VLAN tag is removed and the Operator traffic is carried within a Virtual Private LAN Service (VPLS) across the open eir Core NGN network. 01/07/17 Version 21.0 - Final 36

3. An S-VLAN is added to the Operator traffic and the appropriate QoS is applied. The assigned S-VLAN ID is not visible to either the End-User or the Operator. 4. Fibre access: the OLT will forward traffic from the open eir NGN Node to the with the S- VLAN tag. a) VDSL2 access: the DSLAM will swap the SVLAN tag that identifies the Operator with VLAN ID 10. 5. Fibre access: The will swap the S-VLAN tag that identifies the Operator with VLAN ID 10. a) VDSL2 access: the DSLAM will forward traffic from the open eir NGN node to the End- User's CPE via the Copper. 6. Fibre Access: The End-User resented to the End-User's CPE by the which is installed at the End-User site. a) VDSL2 access: The End-User End-User's CPE via the Copper at the End-User site. 01/07/17 Version 21.0 - Final 37

4.3 Bitstream Plus Multicast: End-User -NNI) Traffic Flow 1 12 13 14 15 16 17 18 19 10 1 CPE S-VLAN OLT Access Connections VPLS MVPN S-VLAN Operator Network CPE C-VLAN DSLAM NGN Node NGN PE NGN Network NGN PE NGN Node 1 Gbit/s Access Connection E-NNI GigE Optical or Electrical Port Operator Handover Site Figure 20: Bitstream Plus Multicast: End-User WEIL (E-NNI) Traffic Flow single VPLS/MVPN per Operator 01/07/17 Version 21.0 - Final 38

11a 12 13 14 STB RG (CPE) 1 S-VLAN 1 S-VLAN STB 15 16 17 18 19 10 1 11 1 RG (CPE) STB S-VLAN 2 OLT S-VLAN VPLS #1 MVPN #1 MVPN #2 S-VLAN #1 S-VLAN #2 Operator Network RG (CPE) STB VDSL modem Master Socket C-VLAN S-VLAN VPLS #2 NGN Agg Node NGN PE NGN Network NGN PE NGN Agg Node 1 Gbit/s Access Connection E-NNI GigE Optical or Electrical Port Operator Handover Site BTV Sources S-VLAN RG (CPE) VDSL 1a modem Master Socket C-VLAN DSLAM 11a 12a 3a 4a Figure 21: Bitstream Plus Multicast: End-User WEIL (E-NNI) Traffic Flow multiple The following describes how Operator multicast traffic is treated: 1. The End-User's CPE sends an IGMP Join specifying the IP multicast group it wants to join. 2. Fibre access: The swaps VLAN ID 10 with the multicast S-VLAN tag that identifies the Operator (and the VPLS/MVPN instance if the Operator has more than one) and forwards to the OLT (The performs IGMP snooping). a) VDSL2 access: The DSLAM swaps VLAN ID 10 with the multicast S-VLAN tag that identifies the Operator. 3. The OLT/DSLAM proxies the IGMP Join towards the open eir NGN node. 4. The SVLAN will act as the service selector at the open eir NGN node to map the traffic to the appropriate VPLS. There will be a VPLS for multicast per Operator at each OLT/DSLAM site. 01/07/17 Version 21.0 - Final 39

A Real-Time (EF) service policy (i.e. CoS profile/bandwidth) is applied to End-User traffic associated with the multicast S-VLAN and the End-User traffic is mapped to the appropriate EF Forwarding Class (FC) within the core NGN network. The S-VLAN tag is removed and the End-User traffic is carried within a VPLS to the open eir PE node. 5. The VPLS instance on the open eir NGN node is connected to each of the open eir PE nodes and is terminated directly onto an IP interface of a multicast VPN (MVPN). IGMP will be enabled on the IP interface to support multicast distribution. 6. The open eir PE Node receives the IGMP join from the OLT/DSLAM and forwards the message as a PIM join within the Operator's MVPN. At the far end MP-BGP is enabled on the open eir PE Node in order to exchange routing information with the Operator's edge router. These routes will be used to calculate the appropriate path back to the source (i.e. via the WEIL). The open eir PE Node at the WEIL forms a PIM adjacency with the Operator and a distribution tree is built on which the multicast traffic is forwarded to the receiver. 7. At the WEIL PE, an MVPN with an IP interface is connected to the WEIL aggregation node. The PE router forms a C- RP/multicast source. 8. An S-VLAN tag that identifies the multicast traffic for that MVPN instance is added to the End- User traffic on egress of the open eir Core NGN network and the appropriate service policy is applied to the End-User traffic. 9. The End-User traffic is passed to the open eir managed located at the Operator handover site. The S-VLAN on the network-facing port is mapped to the Operator facing port on the (E-NNI port). The E-NNI port is configured as an 802.1ad port. The S-VLAN ID is used to identify multicast traffic. The default is for open eir to assign the multicast S-VLAN ID presented at the E-NNI. The assigned multicast S-VLAN ID will be in the range 10 4000. The Operator can optionally specify the multicast S-VLAN ID presented at the E-NNI. If the Operator chooses to specify their own multicast S-VLAN ID on a specific E-NNI, then the Operator will be responsible for specifying all S-VLAN IDs within the range 10-4000 on that E-NNI. 01/07/17 Version 21.0 - Final 40

10. When the source tree is built from the receiver to the source, data flows down the source tree to the receiver. 01/07/17 Version 21.0 - Final 41

4.4 Unicast Implementation The following figure provides an overview of the network solution for unicast traffic. Operator A User 1 Operator A User 2 Operator B User 1 VLAN 1100 VLAN 1100 VLAN 1200 OLT VLAN 1100 VLAN 1200 NGN Node VPLS VPLS NGN Node SVLAN 10 SVLAN 20 WEIL Operator A Handover Site Operator B User 2 VLAN 1200 Operator B Handover Site Operator A User 3 Operator A User 4 Operator B User 3 VLAN 1100 VLAN 1100 VLAN 1200 VLAN 1200 OLT VLAN 1100 VLAN 1200 VPLS VPLS NGN Node NGN Node WEIL SVLAN 10 SVLAN 20 Operator B User 4 Operator A User 5 CPE Operator B User 5 CPE DSLAM Figure 22: Network Solution Unicast Traffic End-User traffic presented at the / will be VLAN tagged with the VLAN ID and 802.1p bits marked by the End-. The /DSLAM will swap VLAN ID 10 with an S-VLAN tag to identify the Operator (VLAN 1100 for Operator A and VLAN 1200 for Operator B above). At the open eir NGN Node the VLAN acts as the service selector. The VLAN tag is stripped off and the traffic is forwarded to the WEIL. There will be a VPLS per Operator per open eir NGN node for unicast traffic. 01/07/17 Version 21.0 - Final 42

At the WEIL an SVLAN is added, this identifies the NGN node to which the OLT/DSLAM is connected (VLANs 10 and 20 in the figure above). 4.5 Multicast Implementation The multicast service is delivered using a MVPN solution. The following figure provides an overview of the network solution for multicast traffic. Operator A User 1 CPE RG (CPE) Operator A User 2 IGMP join 239.1.1.1 1100 = unicast 1101 = multicast OLT VLAN 1101 VLAN 1201 NGN Node VPLS VPLS NGN PE MVPN MVPN MVPN MVPNx MVPNy Multicast Core NGN PE MVPN NGN Node WEIL Operator A Handover Site RP Operator Network Operator B User 3 Operator B User 4 1200 = unicast 1201 = multicast MVPN NGN Network PIM adjacency Figure 23: Network Solution - Multicast Implementation The End- sends an IGMP Join to multicast group 239.1.1.1 (IGMP v.2 is supported) to the /DSLAM. The /DSLAM swaps VLAN ID 10 with the multicast S-VLAN tag 1101 that identifies the Operator. For fibre access the snoops and forwards to the OLT. When the Join is received at the OLT/DSLAM on VLAN 1101, the OLT/DSLAM sends the traffic towards the open eir PE node. At the open eir PE Node the Operator multicast VPN within the NGN core network. The Operator's RP address is configured as part of the MVPN so that IGMP joins from the OLT/DSLAM can be forwarded as PIM joins to the Operator. At the WEIL a dedicated VLAN is configured to carry all multicast traffic. WEIL NGN Node 1 Unicast NGN Node 2 Unicast Multicast 01/07/17 Version 21.0 - Final 43

Figure 24: Wholesale Ethernet Interconnect Link For efficiency and scalability a single copy of every multicast stream offered by an Operator is carried from the Operator -off point, through the core network, to the OLT and PON or DSLAM connecting to the End-User. At no point in this path is the channel data replicated unnecessarily. The core network uses the PIM routing protocol to build a multicast tree from the Operator router to the OLT/DSLAM. For fibre access the OLT takes advantage of the shared PON medium to transmit a single stream to all End-Users. The DSLAM will transmit a stream per End- User. The multicast streams from the Operators are transmitted from the encoders as IP packets with multicast addresses. These are grouped into a VLAN and sent to open eir at the Operator handoff WEIL. open eir multicasts the streams across the core and a single copy of each stream is sent to every OLT/DSLAM. At the OLT/DSLAM a multicast VLAN is configured for each Operator such that there is clear separation of streams between Operators. When a GPON/VDSL2 End-User joins the multicast group for a stream the OLT/DSLAM transmits a copy of that stream onto the PON/DSLAM VDSL2 port associated with that End-User. The OLT uses a special multicast GEM (GPON Encapsulation Method) channel on the PON to carry this data. The DSLAM will transmit this data in the EF queue. For fibre access the data is transmitted once on the PON and is available to any of the 31 other End-Users should they join that multicast group. In respect of fibre access, while the multicast traffic is visible on the PON side of all 32 s, the data is not forwarded to the End-User ess an IGMP join has been seen by the. Multicast traffic is not encrypted by the OLT, unlike unicast traffic. Through the use of filters, the OLT is configured with a set of group addresses for each Operator multicast VLAN. End-User s are then permitted access to subsets of these group addresses on an Operator multicast VLAN. This restricts End-Users to receiving only those streams that are transmitted by their Operator. There is no requirement to agree on the multicast address space used by each Operator because the multicast traffic will be carried in an MVPN in the NGN core network. 01/07/17 Version 21.0 - Final 44

01/07/17 Version 21.0 - Final 45

4.5.1 Access Node customer multicast settings In order to enable multicast support for a VDSL or FTTH customer, a multicast user is associated with the VDSL port/ and bound to the multicast VLAN to create a multicast member. The NGA Access Node (DSLAM or OLT) controls the maximum number of multicast groups that can be joined from an individual VDSL port or. For each subscriber, this is set to the maximum value, 32. Quick leave, also known as fast-leave/immediate-leave, is enabled on the Access Node and is MAC based. When IGMP Join messages are received by the Access Node, the Access Node generates a multicast group membership table that contains the multicast user and the MAC addresses of the multicast group members (i.e. the set-top boxes (STBs)) of the multicast user. A maximum of eight MAC addresses is supported for each multicast group/program. When the Access Node receives an IGMP leave message, it deletes the MAC addresses in the multicast group membership table, and it stops forwarding the multicast stream when all the MAC addresses associated with the multicast user are deleted so that the associated bandwidth is released immediately. Multicast authentication is not enabled in the Access Node so IGMP Join messages for any multicast group address will be proxied by the Access Node to the NGN multicast VPN. Table 1 contains the values for the Access Node parameters associated with the multicast user. Parameter Function Value Max-program Limitation on the number of programs that can be watched concurrently by the multicast user 32 quickleave Quick leave/fast leave mode of the multicast user. enabled and MAC-based auth/no-auth Enable/disable multicast user authentication no-auth global-leave Indicates whether to process the global-leave packet received on the user side. Disable 01/07/17 Version 21.0 - Final 46

Parameter Function Value A global leave is an IGMP leave where the group address is 0.0.0.0, indicating a request from a multicast user to leave all multicast groups. IGMP version Multicast user IGMP version version 3 maxbandwidth Maximum multicast bandwidth no-limit Table 1 Access node multicast user settings 01/07/17 Version 21.0 - Final 47

5. VLAN Management, Forwarding Model and Security 5.1 VLAN Management 1. End-User CPE: The Operator is required to tag traffic with a VLAN (VLAN ID 10). The VLAN dot1p bits allows the Operator to classify traffic to support differential treatment on upstream queues. 2. Operator Access: At the NGA network touch point (/DSLAM) the VLAN ID applied by the End-User CPE will be swapped with an S-VLAN that identifies the Operator (and the VPLS instance if the Operator has more than one). If the Operator has multiple VPLS instances per NGA site, there will be up to 10 SVLAN IDs assigned to the Operator. Each S-VLAN ID will be associated with an Egress Group. When an NGA access is ordered, the Egress Group required must be specified on the order so that the VDSL/GPON port is associated with the correct S-VLAN ID for that Operator and VPLS instance. This S-VLAN ID will be unique to the Operator and applied to all of the Operator access services on the network. This VLAN is only locally significant. 3. WEIL: At the WEIL there will be a VLAN per NGN node (and per VPLS instance where the Operator has more than one) which will carry all traffic associated with the NGA access nodes (OLT and or DSLAMs) connected to that NGN node. 5.2 Forwarding Model An N:1 residential forwarding model is utilised on the /DSLAM access nodes for both the Bitstream Plus and Virtual Unbundled Access products. In this model the End- adds an 802.1q Customer VLAN tag (VLAN ID 10) to the End-User traffic (VLAN tags from the End-User will be dropped, if present). The access node swaps the customer VLAN tag for a service VLAN tag that identifies the Operator and VPLS instance if there is more than one for that Operator. The 802.1p QoS markings are preserved. The access node has MAC address learning enabled such that the service VLAN and the MAC address are used to uniquely identify each End-User. 01/07/17 Version 21.0 - Final 48

Frame CPE Frame 10 OLT/ Frame S DSLAM Figure 25: Access Node Forwarding Model 5.3 Security As every PON is effectively a shared medium, when the OLT sends a packet, it is received by everyone on the PON. To overcome this, the OLT encrypts unicast data streams using Advanced Encryption Standard (AES). The VDSL2 DSLAM is not a shared medium so when it sends a packet it is received by the destination VDSL2 modem only. Both FTTH and FTTC/DSLAM employ Anti-DoS, Anti-MAC Spoofing and Anti-IP Spoofing security features. With the Anti-DoS feature the system monitors the control traffic on each user-port that has a destination address of the DSLAM; if the amount of control traffic on a user-port exceeds normal usage levels then that user-port is blacklisted by the system. Control traffic on a userport is shown as follows: L2CP (with MAC address 01-80-C2-00-00-00 to 01-80-C2-00-00-2f) packets, such as Extensible Authentication Protocol over LAN (EAPOL), Ethernet in the first mile (EFM), Link Aggregation Control Protocol (LACP), and Spanning Tree Protocol (STP) 802.1ag connectivity fault management (CFM) packets Address Resolution Protocol (ARP) packets PPPoE discovery packets IGMP DHCP DHCPv6 01/07/17 Version 21.0 - Final 49

ICMPv6 ICMP Network Time Protocol (NTP) packets PPPoA Link Control Protocol (LCP) packets When a port is blacklisted, all packets will be dropped. The rate limit is 63pps (packets per second) for Control Traffic. An Operator will not receive a notification if a port has been blacklisted. The Operator can report a fault to open eir if an end-customer has reported a loss of service and open eir Service Assurance personnel can check the status of the port directly on the relevant element manager/network device to ascertain if a port has been blacklisted. However, it should be noted that a port will only be blacklisted for a period of 5 minutes so in all probability the port will have been unblocked by the time the end-customer engages with the Operator to report a fault. With the Anti-MAC Spoofing feature the system binds all of the MAC addresses learned on a user-port to that port such that those address can only be used on that port. With the Anti-IP Spoofing feature the system binds all of the IP addresses learned on a user-port to that port such that only those address can only be used on that port. Up to 8 MAC/IP addresses can be bound to a single port. MAC/IP address bindings will be deleted when end-customer is offline.to clear the MACs bound to a port to allow re-learning, an Operator can use the RN (Reset NGA) Order Type on the Unified Gateway which will reset the port for FTTH services and the VDSL port on the DSLAM for FTTC services. This will clear the MAC/IP addresses bound to a port to allow relearning. 6. WEIL and NGA All Next Generation Access (NGA) products i.e. Virtual Unbundled Access (VUA) and Bitstream Plus (BP) are associated with one or more Wholesale Ethernet Interconnect Links (WEILs) belonging to the Operator. The WEIL handover site to the open eir NGN and therefore in the case of NGA, the WEIL provides connectivity from the Operator It is possible to use the same Wholesale Ethernet Interconnect Link for handover of traffic belonging to multiple services e.g. Wholesale Symmetrical Ethernet Access (WSEA) and 01/07/17 Version 21.0 - Final 50

Bitstream Plus Unicast (BPU). T open eir NGN www.openeir.ie. The WEIL is provided from an open eir NGN node. There may be multiple open eir NGN Node in an open eir exchange, one of which will be the NGA NGN node. If the WEIL and the associated Bitstream Plus service are at the same site, or in the case of VUA, where the WEIL and VUA service are always at the same site by definition, the WEIL must be connected to the NGA NGN node. If a - open eir NGN node and a Bitstream Plus or VUA service is ordered for that site as shown in Figure 26, open eir will arrange for the WEIL to be moved to the NGA NGN node. When open eir receives a new WEIL order from an Operator, open eir will check if it will be used to provide NGA services and will then ensure the WEIL is provided off the appropriate NGN node. 01/07/17 Version 21.0 - Final 51

Eircom exchange NGN Node (NGA node) CPE C-VLAN S-VLAN DSLAM VPLS CPE C-VLAN S-VLAN CPE C-VLAN NGN core DSLAM Network - Operator S-VLAN NGN NGN Node ( non-nga node) Figure 26 NGA site with WEIL on "non-nga" NGN node 01/07/17 Version 21.0 - Final 52

7. QoS and Service Bandwidth The capacity on the physical connection from the OLT to the open eir NGN node will be managed by open eir to ensure there is no congestion. The End- will tag traffic with VLAN ID 10 and will mark the 802.1p QoS markings in the VLAN header. Frames will be mapped into the service queues at the open eir NGN Node according to the 802.1p marking. It should be noted that the default 802.1p bit marking applied by the End- is vendor specific, typically 0 or 1; supported markings and their associated forwarding class mappings are listed in Table 1. For multicast a Real-Time (EF) QoS profile will be applied. open eir andbook which can be found on www.openeir.ie. C-VLAN 802.1p Marking Forwarding Class 4 EF 2 AF 0 BE Table 2 Mapping of C-VLAN 802.1p bit markings to forwarding classes It is possible to use the same Wholesale Ethernet Interconnect Link for handover of traffic belonging to multiple services e.g. Wholesale Symmetrical Ethernet Access (WSEA) and Bitstream Plus Unicast (BPU) / Bitstream Plus Multicast (BPM). The Operator specifies the aggregate EF and AF bandwidths for each SAB. The existing WEIL rule applies: the sum of the WEIL Service Access Bandwidths which share the same physical Ethernet Interconnect Link bearer cannot exceed the physical speed of the connection. For unicast products the utilisation on the three queues (EF, AF and Standard) at the WEIL associated with an OLT/DSLAM Unicast service will be measured for traffic usage. An indicative forecast of traffic levels on the queues will be provided by the Operator. This will be used for capacity management on the links between the WEIL and OLTs/DSLAMs. A process will be 01/07/17 Version 21.0 - Final 53

implemented so that the bandwidths configured on the queues will be increased as required as the traffic levels on the queues grow. For multicast products billing will be based upon the bandwidth specified in the Bitstream Plus Fibre Multicast (BPM) order, Table 2 lists the available bandwidth options. Other bandwidths may be available on request. This specified bandwidth will be used for capacity management on the links between the WEIL and OLTs/DSLAMs. 1 Gbit/s EIL Multicast Bandwidths (Mbit/s) 10 Gbit/s EIL Multicast Bandwidths (Mbit/s) 10 10 20 20 30 30 40 40 50 50 75 75 100 100 250 250 500 500 750 750 1000 1000 2000 3000 4000 5000 6000 7000 8000 9000 10000 Table 3: Multicast Bandwidth Options 01/07/17 Version 21.0 - Final 54

open eir NGN Network WEIL Service Access Bandwidth 1 Individual WSEA Logical Connections Individual Logical Connections to OLT/ DSLAMs EF AF BE EF AF BE EF AF BE EF AF BE EF AF BE SAP SAP SAP SAP SAP WEIL Service Access Bandwidth 2 open eir E-NNI WEIL Service Access Bandwidth 3 open eir NGN Node Figure 27: Service Multiplexing and SABs For fibre access, at the, a number of bandwidth options will be offered as shown in Table 4 below. Downstream** Mbps Upstream** Mbps 150 30 300 50 1000 100 Table 4: High Speed Internet FTTH Profiles For VDSL2 access a number of bandwidth options will be offered as shown in the following Tables Table 5: High Speed Internet Rate Adaptive VDSL2 Profiles, 01/07/17 Version 21.0 - Final 55

Table 6: High Stability VDSL2 profiles (from Exchange DSLAM) Line Length (meters) Headline downstream speed (Mbps) Minimum Downstream speed (kbps) Maximum Downstream speed (kbps) Headline upstream speed (Mbps) Minimum Upstream speed (kbps) Maximum Upstream speed (kbps) 350 100 1024 102400 20 1024 20480 500 90 1024 91260 20 1024 20480 615 80 1024 81920 20 1024 20480 700 70 1024 71680 20 1024 20480 750 60 1024 61440 20 1024 20480 850 50 1024 50176 15 1024 15360 950 40 1024 40960 10 1024 10240 1100 30 1024 30720 8 256 8192 1200 25 1024 25600 7 256 7168 1300 18 1024 18432 5 256 5120 1500 15 1024 15360 3 256 3072 1750 12 1024 12288 1 256 1024 2000 7 1024 7168 1 256 1024 Table 5: High Speed Internet Rate Adaptive VDSL2 Profiles Line Length (meters) Headline downstream speed (Mbps) Minimum Downstream speed (kbps) Maximum Downstream speed (kbps) Headline upstream speed (Mbps) Minimum Upstream speed (kbps) Maximum Upstream speed (kbps) 250 100 61440 102400 20 2048 20480 350 85 61440 87040 20 2048 20480 500 80 61440 81920 20 2048 20480 600 70 61440 71680 20 2048 20480 700 60 51200 61440 20 2048 20480 750 50 44032 51200 16 2048 16384 850 43 34816 44032 16 2048 16384 900 40 34816 40960 16 2048 16384 950 34 28672 34816 16 2048 16384 1100 28 20480 28672 16 2048 16384 1100 20 18432 20480 10 1024 10240 1200 20 18432 20480 8 1024 8192 1300 18 12288 18432 7 1024 7168 1500 12 10240 12288 1 256 1024 1750 10 6144 10240 1 256 1024 2000 4 3072 4096 1 256 1024 01/07/17 Version 21.0 - Final 56

8. FTTC VDSL2 Implementation VDSL2 is deployed from a DSLAM installed in a Street Cabinet or in the Exchange. The table below gives an overview of the present VDSL2 Implementation and implementations that are planned in the future. Parameter Present Future Profile 17a B8-11 (Annex B G.993.2) X x Interleaving (INP=2, D=8) X X UPBO (G.993.2) X X PSD Downstream PSD Shaping X X Profile 8b B8-4 (Annex B G.993.2)* X X Retransmission (G.998.4) x x Vectoring (G.993.5) x x SRA (G.993.2) x x AELEM (G.992.3) X Table 8 Overview of FTTC VDSL2 Implementation These parameters are typically available at present on most CPE; a firmware upgrade may be required. *Profile 8b B8-4 (Annex B G.993.2) is used in the case of exchange launched VDSL2 only. This is to deliver lower rate line speeds in order to meet undertakings agreed with the introduction of EVDSL in 2015 9. VDSL2 CPE Requirements This section specifies the functionality required in the VDSL2 modem for correct interworking at the physical layer. The link between the DSLAM and the premises is over copper using VDSL2. In the open eir Access Network, the VDSL2 is deployed from the Cabinet DSLAM as well as from the Exchange DSLAM. Exchange VDSL is launched with appropriate changes to the transmitted line power as permitted by the CLFMP (Copper Loop Frequency Management Plan) 01/07/17 Version 21.0 - Final 58

1. The modem used shall fully comply with the VDSL2 mandatory requirements of G.993.2 2. The modem shall support VDSL2 Profile 17a B8-11 as defined in Annex B of G.993.2. 3. The modem shall support profile 8b B8-4 from G.993.2. 4. The modem shall comply with the requirements of the CLFMP 5. The modem shall support operating with Exchange and cabinet based VDSL2. This involves supporting tone-sets A43 and A43C (as defined in G.994.1 Amendment 1, plus downstream PSD shaping and upstream power back-off as defined in G.997.1 and G.993.2. The use of additional tone-sets (B43, B43c, V43) is not allowed as these may cause adverse interference to other DSL systems operating in the same cable binder. 6. The modem shall support Upstream Power Back Off (UPBO) as defined in G.993.2 7. The modem shall support the use of the upstream band (U0) between 25kHz and 138kHz. 8. The modem shall support seamless rate adaptation (SRA) as defined in Section 13.1 of G.993.2 9. The modem should support downstream PHY layer retransmission as defined in G.998.4. When downstream retrans with Clause 7.1.5.38 of G.997.1. 10. The Modem should support upstream PHY layer retransmission as defined in G.998.4. When upstr 7.1.5.38 of G.997.1 11. The modem shall support 17MHz Vectoring as defined in G.993.5. 12. The modem shall support the alternate electrical length estimation methodology (AELEM)for estimating the electrical length of the connection between the modem and the DSLAM (mode ELE-M1) as defined in G.993.2. This is required to provide accurate estimation of the electrical length of the channel over which the modem is operating (i.e. 01/07/17 Version 21.0 - Final 59

the insertion loss of the cable measured at 1MHz)to help ensure accurate UPBO setting and compliance with the CLFMP 13. The modem shall support bit swap as defined in G.993.2 14. The modem shall support the correct reporting of Vendor ID, Version Number and Serial Number as described in section 11.2.3.6 of G.993.2 15. The modem shall support the correct reporting of key VDSL2 test and diagnostic parameters according to G.997.1. The key parameters are shown in Table 9 below. Parameter Reference XTU-R G.994.1 Vendor ID 7.4.2/G.997.1 xtu-r system vendor ID 7.4.4/G.997.1 xtu-r version number 7.4.6/G.997.1 xtu-r serial number 7.4.8/G.997.1 Upstream Actual data rate 7.5.2.1/G.997.1 Downstream Actual data rate 7.5.2.1/G.997.1 Upstream line attenuation [LATNus] 7.5.1.10/G.997.1 Downstream line attenuation [LATNds] 7.5.1.9/G.997.1 Upstream signal-to-noise (SNR) ratio margin [SNRMus] 7.5.1.16/G.997.1 Downstream signal-to-noise ratio margin [SNRMds] 7.5.1.13/G.997.1 Upstream maximum attainable data rate [ ATTNDRus] 7.5.1.20/G.997.1 Downstream maximum attainable data rate [ATTNDRds] 7.5.1.19/G.997.1 Upstream Actual Aggregate Transmit Power [ACTATPus] 7.5.1.25/G.997.1 Downstream H(f) logarithmic subcarrier group size [HLOGGds] 7.5.1.26.5/G.997.1 Downstream H(f) logarithmic representation [HLOGpsds] 7.5.1.26.6/G.997.1 01/07/17 Version 21.0 - Final 60

Downstream QLN(f) subcarrier group size [QLNGds] 7.5.1.27.2/G.997.1 Downstream QLN(f) [QLNpsds] 7.5.1.27.3/G.997.1 Downstream SNR(f) subcarrier group size [SNRGds] 7.5.1.28.2/G.997.1 Downstream SNR(f) [SNRpsds] 7.5.1.28.3/G.997.1 Downstream bits allocation [BITSpsds] 7.5.1.29.1/G.997.1 Upstream traffic count Downstream traffic count FEC seconds-line far end [ FECS-LFE] (Downstream) 7.2.1.2.1/G.997.1 Errored second-line far end [ES-LFE] (Downstream) 7.2.1.2.2/G.997.1 Severely errored second-line far end [SES-LFE] (Downstream) 7.2.1.2.3/G.997.1 Forward error correction Channel far-end [FEC-CFE] 7.2.2.2.2/G.997.1 Actual INP Upstream [ACTINP] 7.5.2.4/G.997.1 Actual INP Downstream [ACTINP] 7.5.2.4/G.997.1 Table 9 Key Diagnostic and Test parameters to be reported by CPE 01/07/17 Version 21.0 - Final 61

10. open eir equipment installed at user premises (, ) Fibre access: An open eir Network Termination Unit will be installed generally adjacent to the Copper. On occasion it will be located elsewhere, this decision is driven by the cable entry point. The specification of the which will be installed in the End-User premises is shown in the following table: Mounting Dimensions Weight Power adapter type Power adapter input System power supply Wall mounted 143 mm (L) x 113 mm (W) x 30 mm (H) 200g (not including power adapter) Directly moulded onto a BS 1363 3-pin AC plug 100 240 VAC, 50 60 Hz 11 14 VDC, 1A (Maximum power consumption: approx. 5W) Power lead length 1.5m End-User Facing Port Auto-sensing 10/100/1000M Base-T Ethernet port (RJ-45) Table 10: Specification Please note that the above specification is subject to change. VDSL2 access: the demarcation point is the Copper at the End-User premises. An RJ11 interface is provided for POTS and an RJ45 is provided for VDSL. 01/07/17 Version 21.0 - Final 62

Appendix I 01/07/17 Version 21.0 - Final 63

Installation Manual for NGA FTTC Connections in National Roll-Out Installation Manual for NGA FTTC Connections in National Roll-Out Version 2.0 October 2012 01/07/17 Version 21.0 - Final 64

Installation Manual for NGA FTTC Connections in National Roll-Out Version 2.0... 64 Contents... 65 1. Introduction... 66 Incorporation of VoIP into the internal wiring is outside the scope of this document and is not covered.... 66 2. Right to make changes... 66 3. Connection from the FTTC Cabinet... 66 Figure 1: Connection from FTTC Cabinet... 67 4. Installation of... 67 Figure 2: Open eir Base with Back Box... 68 5. POTS with VDSL2... 69 Figure 3: Wiring diagram for POTS + VDSL2 Scenario... 69 Figure 4: DSL and POTS Ports on the Splitter facing plate... 70 Figure 5: Wiring of Rear of Faceplate (Splitter Module)... 70 6. Standalone VDSL2... 71 Figure 6: Wiring diagram for VDSL2 Standalone scenario... 71 01/07/17 Version 21.0 - Final 65

Installation Manual for NGA FTTC Connections in National Roll-Out 1. Introduction The purpose of this document is to provide wiring guidelines to Operators for the installation of a dual interface (Network Terminating Unit) in an End-Users premise in order to facilitate the delivery of NGA VUA and Bitstream Plus services using VDSL2 from an open eir DSLAM as part of the NGA National Roll- Out. NGA VUA or Bitstream Plus connection may be POTS-Based (PB) or Standalone (SA) and the dual interface will be used in both scenarios. The manual covers the following items of interest to the Installer and assumes a level of capability considered appropriate to End-User premises installation. Installation of Dual Interface to Support VDSL2 and POTS on the same copper pair. Installation of Dual Interface to Support Standalone Products The open eir dual Interface provided incorporates a splitter and supports the provision of both a VDSL2 and a POTS connection over the same copper pair as required. It will also support the provision of a VDSL2 connection on its own. Incorporation of VoIP into the internal wiring is outside the scope of this document and is not covered. This is the demarcation point between the open eir he open eir Operator/End-User End-Users Premises Equipment). 2. Right to make changes This manual is specific to NGA National Roll-Out only. The manual is subject to change. These changes can be based on feedback and any technical and/or operational considerations that may arise as part of NGA National Roll-Out. This document may also be modified to meet any changes or enhancements to the NGA products. 3. Connection from the DSLAM The Dual Interface Copper has two interfaces. It has an internal splitter support both a VDSL2 connection and POTS on the same copper pair from the DSLAM. On the left is the VDSL2 Interface and the POTS interface is on right as shown in Figure 1 Part (a). 01/07/17 Version 21.0 - Final 66

Installation Manual for NGA FTTC Connections in National Roll-Out = + (a) (b) Base of Line In terminates on L1 and L2 (c) Rear of Removable Faceplate (d) Rear of Base Figure 1: Connection from DSLAM The Incoming line from the DSLAM is terminated on the L1 and L2 terminals at Rear of Base as shown in Figure 1 Part (d). All internal wiring must be disconnected from the line in from the DSLAM to the so that a clean connection from the DSLAM to the Copper is made. 4. Installation of The initial installation of the should be at the nearest suitable location to the line entry into the End- Users Premises / house at the same level as the electrical sockets, approx. 450mm, and as close as the line before the point where it is terminated on the. The should always be located in an accessible position. The should be mounted in such a place that only the End-User that is served from it, can access it (or provide access to it). If the location for the is flush mounting, ensure that the flush box is clean and dry and free from plaster. Remove the packaging from the unit. Remove the customer cover. (See Figure 1(a)) If the is surface mounted, select two wall mounting holes in the back box. Select a hole in base for network wiring cable entry. Secure the back box with screws and rawlplugs if necessary (Figure 2.). Route cable through network cable entry point. Strip the cable outer sheath. Connect the exchange line to L1 and L2. (Figure 2) Secure the open eir connection unit to the back box or flush box (Figure 1(a)). 01/07/17 Version 21.0 - Final 67

Installation Manual for NGA FTTC Connections in National Roll-Out L1 L2 Figure 2: open eir Base with Back Box. 01/07/17 Version 21.0 - Final 68

Installation Manual for NGA FTTC Connections in National Roll-Out 5. POTS with VDSL2 In this scenario POTS /PSTN is provided along with VDSL2 for a VUA or Bitstream Plus connection for the NGA national Roll-Out. The splitter in the isolates the POTS from the DSL and the POTS is available as normal through the splitter face plate. The alarm wiring and internal POTS distribution are taken off the splitter face plate. Line In NGA VUA/BS+ + Splitter S Alarm In Alarm Out Internal Wiring Activity POTS for internal Distribution The DSL port of the Home Gateway is plugged in to the DSL socket in the splitter facing plate POTS appears on the phone socket on the splitter facing plate Alarm can also be wired off alarm terminals on splitter facing plate DSL Home Gate way Figure 3: Wiring diagram for POTS + VDSL2 Scenario 01/07/17 Version 21.0 - Final 69

Installation Manual for NGA FTTC Connections in National Roll-Out POTS DSL Figure 4: DSL and POTS Ports on the Splitter facing plate Alarm Connections, IN Pair to Alarm OUT Pair from Alarm Cut these resistors for Alarm Installation Internal Wiring taken from L1 and L2 Figure 5: Wiring of Rear of Faceplate (Splitter Module) shown in Figure 4 and cutting the resistors as indicated, connects the alarm so it will have priority on the POTS line in the event of an outgoing call by the alarm unit. The internal wiring connection as shown, connects the internal wiring to the POTS output from the internal splitter at L1 and L2 as indicated in Figure 5. If the internal wiring is connected to this point it is isolated appropriately from the VDSL2 connection. (Note: This is different to the L1 and L2 shown in Figure 1 Part (d) which are the input connections from the FTTC cabinet to the splitter) 01/07/17 Version 21.0 - Final 70

Installation Manual for NGA FTTC Connections in National Roll-Out 6. Standalone VDSL2 In this scenario there is no POTS service provided to the End-User over the same copper pair. The is connected to the line in from the DSLAM as shown already in Figure 1 for a connection with both VDSL2 and POTS. This results in the following configuration shown below in Figure 6: NGA VUA/BS+ Internal Wiring Activity Line In DS Home Gate way Figure 6: Wiring diagram for VDSL2 Standalone scenario The Incoming line from the DSLAM is terminated on the L1 and L2 terminals at Rear of Base as shown in Figure 1 Part (d). All internal wiring must be disconnected from the line in from the FTTC cabinet to the so that a clean connection form the cabinet to the Copper is made. The internal wiring should not be connected to the Copper in a standalone scenario as there is no POTS output from the splitter. Where a VoIP or similar POTS emulation service is being provided as a voice solution, the End-User wiring may need to be rear This is the responsibility of the Operator/End-User. 01/07/17 Version 21.0 - Final 71

The Operator/End-User is also responsible for providing a solution to any alarm circuits that may have previously used a POTS-based product and which they may be migrating to a standalone configuration. 01/07/17 Version 21.0 - Final 72

Installation Manual for NGA FTTH Connections in National Roll-Out Appendix II 01/07/17 Version 21.0 - Final 73

Installation Manual for NGA FTTH Connections in National Roll-Out Installation Manual for NGA FTTH Connections in National Roll-Out Version 2.0 October 2012 01/07/17 Version 21.0 - Final 74

Installation Manual for NGA FTTH Connections in National Roll-Out Version 2.0... 74 Contents... 75 1. Introduction... 76 The purpose of this document is to describe the installation of the NGA FTTH fibre and GPON.... 76 Internal wiring is outside the scope of this document and is not covered.... 76 2. Right to make changes... 76 3. Installation of Fibre... 76 The location should be dry and accessible to enable open eir staff to complete the installation.... 76 At the fibre either a field installed connector is fitted on one fibre or a pre terminated fibre cable is used.... 76 Figure 1: Customer premises... 77 4. Connecting the fibre to the... 77 An RJ45 connection is used to connect the to the CPE.... 77 01/07/17 Version 21.0 - Final 75

Installation Manual for NGA FTTH Connections in National Roll-Out 1. Introduction The purpose of this document is to describe the installation of the NGA FTTH fibre and GPON. Internal wiring is outside the scope of this document and is not covered. The fibre is the termination point of the open eir external line plant in the premises. The is the FTTH demarcation point between open eir FTTH Access network and the Operato. 2. Right to make changes This manual is specific to NGA National Roll-Out only. The manual is subject to change. These changes can be based on feedback and any technical and/or operational considerations that may arise as part of NGA National Roll-Out. This document may also be modified to meet any changes or enhancements to the NGA products. 3. Installation of Fibre The open eir Fibre will be generally installed adjacent to the Copper. On occasion it will be located elsewhere, with this decision driven by the cable entry point. Where required a hole is drilled through the wall of the premises to enable the fibre to be installed. Standard safety practice applies to the drilling of such holes. The location should be dry and accessible to enable open eir staff to complete the installation. A two fibre cable is used from the Fibre distribution point to the Fibre via the ETU (External Terminating Unit - where installed). The fibre is located at a point inside the end-user premises, adjacent to the ETU or cable entry point. At the fibre either a field installed connector is fitted on one fibre or a pre terminated fibre cable is used. The fibre is wall mounted. The dimensions of the fibre are approximately 28mm deep 90mm high and 70mm wide. The optical port is fitted with a shutter. 01/07/17 Version 21.0 - Final 76

Installation Manual for NGA FTTH Connections in National Roll-Out Figure 1: Customer premises 4. Connecting the fibre to the A pre terminated fibre patch cord usually of 1 meter length is used to connect the fibre to the Optical Network Termination (). The synchronises with the GPON equipment in the exchange. The requires a mains power socket. The power socket is provided by the end-user. The can be stand alone or wall mounted, however wall mounting is preferred. Usually a wall fitting is also used. The is fitted to the wall with a base plate. Mounting Dimensions Weight Power adapter type Power adapter input System power supply Wall mounted 143 mm (L) x 113 mm (W) x 30 mm (H) 200g (not including power adapter) Directly moulded onto a BS 1363 3-pin AC plug 100 240 VAC, 50 60 Hz 11 14 VDC, 1A (Maximum power consumption: approx. 5W) Power lead length 1.5m End-User Facing Port Auto-sensing 10/100/1000M Base-T Ethernet port (RJ-45) An RJ45 connection is used to connect the to the CPE. Installation Manual for NGA FTTH Connections in National Roll-Out 01/07/17 Version 21.0 - Final 77

Figure 2: connection points 01/07/17 Version 21.0 - Final 78

Technical Handbook. open eir 1 NGA National Deployment Virtual Unbundled Access Products Bitstream Plus Products. 01/07/17 Version 21.