atis next generation networks ngn framework requirements and architecture n.
Skip this Video
Loading SlideShow in 5 Seconds..
ATIS: Next Generation Networks (NGN) Framework: Requirements and Architecture PowerPoint Presentation
Download Presentation
ATIS: Next Generation Networks (NGN) Framework: Requirements and Architecture

Loading in 2 Seconds...

play fullscreen
1 / 38

ATIS: Next Generation Networks (NGN) Framework: Requirements and Architecture - PowerPoint PPT Presentation

  • Uploaded on

ATIS: Next Generation Networks (NGN) Framework: Requirements and Architecture. Alliance for Telecommunications Industry Solutions 1200 G Street, NW Suite 500 Washington, DC 20005 202/434-8828. Outline. General Requirements End User Applications (Use Cases) Network Service Enablers

I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
Download Presentation

PowerPoint Slideshow about 'ATIS: Next Generation Networks (NGN) Framework: Requirements and Architecture' - zamora

Download Now 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.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.

- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
atis next generation networks ngn framework requirements and architecture

ATIS: Next Generation Networks (NGN)Framework: Requirements and Architecture

Alliance for Telecommunications Industry Solutions

1200 G Street, NW

Suite 500

Washington, DC 20005



General Requirements

End User Applications (Use Cases)

Network Service Enablers

Underlying Network Capabilities

Business Model Requirements

US Regulatory Requirements

Framework Reference Architecture

general requirements
General Requirements


Convergence (fixed / mobile / enterprise)

Access network criteria

Infrastructure evolution & Legacy services

end-to-end transparency

Services guiding principles (for converged networks)

general requirements interconnection
General Requirements:Interconnection
  • Specify a packet based interconnection, suitable for carrier interconnect, that will support:
    • security
    • QoS
    • reliability
    • billing support
    • service transparency
    • performance measurements, monitoring, codecs, etc…
  • Support interconnection between different classes of service providers (e.g. Next Generation Service Providers & Application Service Providers)
general requirements access independence
General Requirements:Access Independence


Core NGN Subsystems


ATIS does not specify that the NGN must support all access technologies

Private Lines



  • Instead, ATIS identifies conditions for support of an IPCAN
    • IP
    • support provision of QoS consistent with Y.1541
    • transport level encryption restricted to IPCAN
    • may support admission control
    • mobility management consistent with NGN Core
general requirements infrastructure evolution

SIP (IMS) Services & Architecture

=> Primary NGN objective






Full PSTN Feature Transparency

=> Secondary NGN objective

General Requirements:Infrastructure Evolution

Evolution to NGN


“SIP” services


“Perfect Simulation”

Target NGN

general requirements services
General Requirements:Services
  • End-to-end transparency
    • backward compatibility for “best effort Internet”
    • NGN network services may be incompatible with end-to-end transparency
  • Service environment
    • service development independent of network & application protocols
    • SIP as core signaling protocol
    • also support service APIs (e.g. Parlay / OSA)
end user applications
End User Applications
  • Selected representative end user services as “use cases” to test and validate NGN requirements. Identified the network service enablers that would be required for application.
    • Interactive voice
    • Content-based services / video
    • Multi-media conferencing
    • Content sharing
    • Interactive gaming
    • Sensor and control networking
    • Mobility management (wireless / wireline)
network service enablers
Network Service Enablers

Network service enablers were defined as network-based communications services that bring value to consumer applications

network service enablers qos
Network Service Enablers: QoS
  • QoS has been identified as one of the key Release 1 requirements for NGN
    • end-to-end
    • inter-carrier
    • evolve incrementally from existing best-effort networks
    • can use complementary techniques
      • Network Engineering
      • Traffic Engineering
      • Packet Scheduling (e.g. Diff Serv)
    • Access networks likely to need packet scheduling QoS mechanisms first
network service enablers presence personal profiles
Network Service Enablers: Presence & Personal Profiles

Key capabilities for Release 1 NGN

endorses the IETF Presence model

Personal profiles & Personal Information Mgmt complement Presence, to link services and enable end-user centric model

Ability to link and unify various identities is a foundation for many other NGN services

End-user centric model will enable significant new service opportunities

network service enablers1
Network Service Enablers
  • Policy
    • mechanism to ensure consistent application of network services across various networks and technologies
    • consistent policy architecture and protocols required
  • Media Resource Functions
    • in legacy networks these were linked to specific services
    • in the NGN media resources are a generic function
    • suitable control mechanism is key
network service enablers2
Network Service Enablers
  • Location
    • Some services (e.g. E.911) require location information
    • Location may also be a value added service
    • Network determined location is access specific
    • Location may also be CPE derived (Network validation may be required…)
  • Content and Service Discovery
    • required to support rapid service introduction
    • independent of underlying network technology
    • discover services based on “interest” (user or device)
    • client-server and peer-to-peer
underlying network capabilities
Underlying Network Capabilities
  • Identifies network capabilities required for NGN, but which applications cannot directly access. e.g:
    • OAM
    • security
      • authentication
      • non repudiation
      • etc.
    • SLA
    • network survivability
    • service quality measurement
    • mechanisms to predict service quality

ATIS Security Focus Group has completed a detailed gap analysis and prepared a work plan to address these gaps. Topics addressed include:

  • Authentication and Authorization
    • user, device and network entity authentication required for IP-CAN, IMS & applications
  • Integrity
    • level required will depend on the application
  • Confidentiality & Privacy
    • essential for NGN capabilities
business model requirements
Business Model Requirements

Significant revenue generation and cost savings opportunities must justify the substantial investment required to build the NGN.

The NGN must facilitate running a business with the efficiency of WalmartTM and the brand differentiation of Coca-ColaTM.

business drivers
Business Drivers
  • New Retail Revenue
  • New Wholesale Revenue
  • Cost Reduction for Existing Services
  • Regulatory Requirements
methods for success
Methods for Success
  • Customization through User Profile
  • Transparent Third Party Networks
  • Seamless Service Delivery

Service delivery complicated by increased number

of sophisticated interfaces.

user profile
User Profile
  • Targeted Services
  • Rapid and Flexible Service Creation
  • Integrated OSS/BSS
  • Converged Customer Relationship

User-specific, location-agnostic services

differentiate product offering.

third party networks
Third Party Networks
  • Communications Services work across networks
  • Application and Content Services work across networks
  • Architecture must support different types of mobility depending on offering and relationship
third party networks1
Third Party Networks
  • Simple end user access & authentication
  • Secure access to profile
  • Consolidated settlement
  • Foreign Network Support for Services
    • Location, Presence, etc.
third party networks2
Third Party Networks
  • Services must adapt to access capabilities
  • Access protocols interwork to the SIP core
  • QoS and Security must be maintained
  • End-to-end service may span multiple independent networks
service delivery
Service Delivery
  • Blended IT and Telecom Services
  • Leverage third party information
    • Location
  • Support for third party applications
  • Service creation process should support new blended services
service delivery1
Service Delivery
  • Web-based Self Management
  • Support for third party networks
  • Wide range of CPE
  • Scalable and Reliable Platform
  • Support for NG OSS/BSS
us regulatory requirements
US Regulatory Requirements
  • National Security & Critical Infrastructure
    • LAES
    • ETS
  • Consumer Requirements
    • E911
  • Operations Requirements
    • Number Portability
    • Number Pooling
    • Accounting
    • FCC Rules
convergence in atis ngn
Convergence in ATIS NGN

Focus of NGN is converged user-centric Voice & Data services, irrespective of the access & transport technologies used or deployed

atis ngn user side
ATIS NGN: User Side
  • User side includes all “User Domain” or Customer Premises” equipment
    • Signaling and bearer interfaces to both IP and non-IP (wireline wireless) networks are included
    • Both managed and unmanaged Customer prem. networks are supported, including Customer Network Management (CNM)
    • Advanced services like NAPT, FW, I(D/P)S, SLA monitoring/enforcement need to be supported at customer edge as well
atis ngn other network
ATIS NGN: Other Network
  • Other networks include both TDM and IP networks (wireline & wireless)
    • IP network providers interworking with other access network technologies, such as wireline and wireless carriers thru appropriate Border Gateway functions
    • IP network providers interworking with non-IP network technologies for example, the PSTN (thru IP-TDM GW)

Objective is to support high-quality ETE revenue generating service — securely and seamlessly — to the customers, e.g., a handoff for a wireless handset roaming between a wireless and wireline infrastructure without degradation of quality

atis ngn public network
ATIS NGN: Public Network
  • A FOUR layer FUNCTIONAL model is used
  • Transport is IP based with appropriate interfaces to User side, Other networks, and upper layer functional entities (FEs)
  • Session admission, authentication and enforcement of policy are executed via the “Session and Policy” control functions
  • Value-added and enhanced services are hosted in servers in the “Applications and Service Capability” functions
  • Service creation, maintenance, and management thru e.g., Web portals – including FCAPS – are performed via the entities in the OAM&P functions
multiple service provider environment issues
Multiple Service Provider Environment: Issues
  • Multiple administrative and technology domains
  • Multiple instances of Session policy and Apps & Service capability functions must interwork properly to support high-quality ETE revenue generating service — securely and seamlessly — to the customers
    • Interworking with legacy signaling & control instances/paradigms is also a must

Tim to provide