NGN INTERCONNECT WORKING GROUP 4 April 2005 Update on the TSG Project Plan and Technical Work Paul Griffin – Network Architect, Energis Nick Ireland – Secretary TSG, BT Peter Willis – Data Networks Architect, BT The information in this presentation relates to plans currently under development and subject to consultation, and may be subject to change. Detailed implementation depends upon a number of factors including the capabilities of suppliers and the final 21CN network design.

UK Standards Process Structure

TSG Project Plan (1) #TaskPre- Req Group /Work item Dead- line R / A / G REQUIREMENTS 1Scope requirements for the support of PSTN/ISDN services over IP based interconnect -ARS NICC 74 End Feb Identify management requirements impacting on signalling for PSTN/ISDN services. -ARS NICC 72 End Feb 2005 Initial Requirements Incorporated into task 1 3Scope requirements for Phase 2-ARS NICC 74 End July 2005

TSG Project Plan (2) #TaskPre- Req Group /Work item Dead- line R / A / G ARCHITECTURE 4 Describe a signalling architecture for IP based interconnect, identifying services assumed from lower layers; 1ARS NICC 74 Mid March Describe approaches to maintaining the network resilience across an IP based interconnect. 4ARS NICC 74 Mid March Produce a draft design document for the transport architecture to be incorporated into the NGN document set. -ARS NICC 74 End March 2005

TSG Project Plan (3) #TaskPre- Req Group /Work item Dead- line R / A / G SECURITY 7Establish a set of security requirements for NGN interconnect over an IP interconnect for PSTN/ISDN traffic. -ARS NICC 73 Due end March Initial Requirements included in task 1. Work ongoing in ETSI 8Identify network protective controls (e.g. to protect against Mass Calls) (Subset of 7) - 9Identify method to prevent Application Fraud (Subset of 7) -

TSG Project Plan (4) #TaskPre- Req Group /Work item Dead- line R / A / G APPLICATIONS 10Define and document the Specification of the signalling required to establish, clear down, maintain and accurately charge for calls across an IP based interconnect, and subsequently maintain this specification (SIP-I) ETSI TISPAN July 1,2,4,6 App NICC 70 End July 2005 Initial Requirements included in task 1. Work ongoing in ETSI 11Identify the protocols needed to support signalling and whether they are sufficient to allow implementation. (SCTP/UDP) 4App NICC 70 End July 2005

TSG Project Plan (5) #TaskPre- Req Group /Work item Dead- line R / A / G APPLICATIONS 12Identify any open issues in the required standards and if required, determining solutions for input to the appropriate international standards body. 1,4,6,11App NICC 70 End July If required, produce NICC specifications and/or guidelines on the transport and physical aspects of IP interconnect. 1,4,6,11App NICC 70 End July Draft Interconnect Test Specs10App NICC 70 End Aug 2005

TSG Project Plan (6) Ongoing, Ethernet OAM Frames End March 2005 IP NICC 71 15Identify any open issues in the required standards and if required, determining solutions for input to the appropriate international standards body. 16 EoSDH defined. Additional protocols identified from task 6 End March 2005 IP NICC 71 4,6Identify the protocols needed to support user and IP Transport planes and whether they are sufficient to allow implementation 15 IP TRANSPORT R / A / GDead- line Group /Work item Pre- Req Task#

TSG Project Plan (7) MANAGEMENT R / A / GDead- line Group /Work item Pre- Req Task# End March 2006 MGMT NICC 72 10Develop a list of operational procedures for managing IP interconnect for PSTN/ISDN traffic. 18 End March 2005 IP NICC 71 15If required, produce NICC specifications and/or guidelines on the transport and physical aspects of IP interconnect. 17

Key Issues Technical areas NICC Specifications based on existing international standards Current Status Release 1 (PSTN/ISDN) Service requirements agreed Release 1 IP Interconnect Architecture defined (includes security, management, resilience aspects) IP Interconnect physical transport defined – Ethernet over SDH Release 1 IP IX Signalling to be SIP(I) – dependency on ETSI Current key issues SCTP = PSTN/ISDN MTP equivalent Numbering, Addressing, Identifiers = tba

IP Addressing Issues The address range /12 has been proposed (over 1 Million addresses) The intention is that we do not mandate whether or not any CP uses NAT Signalling should be OK, i.e. 6 IP addresses per signalling “ link ” (/29) Unknown volumes of IP addresses will be required for media streams if NAT is not used. Who will administer this address space? This will give visibility of the number and possibly location of interconnects that each operator has. Commercially sensitive Who will define the rules? Should rules and best practices be the work of the standards bodies

Management Plane Control Plane NGN BNGN A iMn Transport Function fB1 fMn Management Funcs fMn Management Funcs BW Mang Func fC2 Signalling Border Func fB2 Edge Session Control Func fC1 NGN Bearer N/W(s) Source Session Control Func fC3 IP Session Border Func fB3 Other IP Service Border Func fB4 Control Plane Bearer Plane ATM Border Func fB5 TDM Border Func fB6 Signalling Border Func fB2 IP Session Border Func fB3 Other IP Service Border Func fB4 ATM Border Func fB5 TDM Border Func fB6 NGN Bearer N/W(s) iB1a iB1b iB1c iB2a iB2b Edge Session Control Func fC1 Destinat n Session Control Func fC4 BW Mang Func fC2 iC1 iB3

GigE Physical IP SDH Physical VCAT ATM ATM Backhaul Services GFP Ethernet VLAN IP VCAT ATM GFP Ethernet VLAN IP PSTN/ISDN Services Other Services on IP TDM Services PSTN/ISDN Services Other Services on IP ATM Backhaul Services TDM Services