1 / 13

Network Structures WG

Network Structures WG. Paul Griffin. 13 January 2006. Agenda. Report back from NICC TSG MSAN Voice Access Requirements Reference Architecture. Report back from NICC TSG. NGN Multi-service Interconnect Documentation.

elsie
Download Presentation

Network Structures WG

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Network Structures WG Paul Griffin 13 January 2006

  2. Agenda • Report back from NICC TSG • MSAN Voice Access Requirements • Reference Architecture

  3. Report back from NICC TSG

  4. NGN Multi-service Interconnect Documentation • Documentation broken down into a structure that is easy to understand and will be simple to update • Layer 1 Top level - defines the scope of Multi-Service Interconnect for UK NGNs, binds related standards at particular versions to an NGN MSI release • Layer 2 Defines all service agnostic common infrastructure for the NGN MSI. • Layer 3 Service interconnect specifications, each service will have a separate document • Layer 4 General Reference ND Documents that are referred to within the main ND layer documents for service specific or common infrastructure implementations.

  5. NGN Multi-service Interconnect Documentation Structure

  6. MSAN Voice Access Requirements

  7. MSAN Voice Access Requirements • The intention is to agree these now to enable them to be passed to the TSG/ARS meeting on the 17th January • As previously agreed, Consult 21 will not define the solution, just the requirements

  8. MSAN Voice Access Requirements • 1. The architecture must provide the ability to provide Operator A with control of Operator B’s MSAN lines. • The capability must be provided via an interconnect defined by NICC • 2. All PSTN Emulation features shall be capable of being provided to Operator A. • 4. What QoS will be available to Operator A? • 5. The architecture shall support an automatic mechanism to prevent overload at the point of interconnect. Including but not limited to: • Signalling transport • Session processing • Bearer control mechanisms • 6. The bearer media stream shall support voiceband data and DTMF. Support for RFC2833 (DTMF out-of-band transport) and T.38 (Fax/modem out-of-band transport) is not required. • 7. The architecture shall provide equivalence of both input and output to all parties

  9. MSAN Voice Access - Security • 8. The architecture shall not require an operator to reveal their internal bearer network topology. • 9. The architecture shall not require an operator to reveal their control network topology. • 10. The architecture shall not make any assumptions about physical network security. • 11. In order to maintain network integrity, authentication and privacy shall be provided for signalling between networks: • The architecture shall provide for signalling privacy between networks. • The architecture shall require authentication between the networks. • 12. The architecture shall not be defined in such a way that policing/policy enforcement of the interface becomes impracticable.

  10. MSAN Voice Access - Management • 13. The architecture shall allow operator A to provision an endpoint on operator B’s MSAN. • 14. The architecture shall allow relevant events from operator B’s MSAN to be received by operator A. Is this a job for Network Hooks?

  11. Reference Architecture

  12. Functional Architecture used in TSG

  13. Thank you

More Related