130 likes | 237 Views
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.
E N D
NGN INTERCONNECT WORKING GROUP4 April 2005Update 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.
# Task Pre- Req Group /Work item Dead- line R / A / G IP TRANSPORT 15 Identify the protocols needed to support user and IP Transport planes and whether they are sufficient to allow implementation 4,6 IP NICC 71 End March 2005 EoSDH defined. Additional protocols identified from task 6 16 Identify any open issues in the required standards and if required, determining solutions for input to the appropriate international standards body. 15 IP NICC 71 End March 2005 Ongoing, Ethernet OAM Frames TSG Project Plan (6)
TSG Project Plan (7) # Task Pre- Req Group /Work item Dead- line R / A / G MANAGEMENT 17 If required, produce NICC specifications and/or guidelines on the transport and physical aspects of IP interconnect. 15 IP NICC 71 End March 2005 18 Develop a list of operational procedures for managing IP interconnect for PSTN/ISDN traffic. 10 MGMT NICC 72 End March 2006
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 172.16.0.0/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
NGN A NGN B Management Funcs Management Funcs Destinatn Session Control Func Source Session Control Func Edge Session Control Func Edge Session Control Func fB1 fMn fMn BW Mang Func BW Mang Func fB3 fB3 fC1 fC3 fB2 fB2 fC4 fC2 fC2 fC1 fB4 fB5 fB5 fB6 fB4 fB6 Management Plane Control Plane Control Plane Bearer Plane Signalling Border Func Signalling Border Func NGN Bearer N/W(s) NGN Bearer N/W(s) IP Session Border Func IP Session Border Func ATM Border Func Other IP Service Border Func TDM Border Func Other IP Service Border Func TDM Border Func ATM Border Func iMn Transport Function iC1 iB1a iB3 iB1b iB1c iB2a iB2b
TDM Services TDM Services PSTN/ISDN Services PSTN/ISDN Services Other Services on IP Other Services on IP ATM Backhaul Services ATM Backhaul Services IP IP IP IP IP IP IP IP ATM Ethernet VLAN Ethernet VLAN ATM GFP GigE Physical GFP VCAT VCAT SDH Physical