sdcvsdcs

47
Chapter 2 Chapter 2 NGN NGN Architectu Architectu re re

Upload: faizsiddiqui10

Post on 31-Oct-2014

112 views

Category:

Documents


2 download

DESCRIPTION

dsdf

TRANSCRIPT

Page 1: sdcvsdcs

Chapter 2Chapter 2NGN NGN

ArchitectuArchitecturere

Page 2: sdcvsdcs

NGN Basic Concept

Page 3: sdcvsdcs

NGN is Predicated on:

Transport

Services

Telephone ServicesData Services (WWW, e-mail, etc)

Video Services (TV, movie, etc)

Point to point, Point to multipoint, Multipoint to multipoint

Point to point, Point to multipoint, Multipoint to multipoint

Page 4: sdcvsdcs

Feature of Convergence

Europe(ETSI)

America(ATIS)

Asia(CJK)

FGNGN

Regional Standards

ITUNGN

Asia

America

Europe

Global Standards

Page 5: sdcvsdcs

Impacts of NGNTelephoneServices

DataServices (WWW, e-mail, etc)

Video Services (TV, movie, etc)

TelephoneServicesNetwork

DataServicesNetwork

Pre-NGN

VideoServicesNetwork

SPm

SP3

SP2

ANP 2 (DSL)

New BusinessEnvironment (Compositional)

ANP 1 (DSL)

ANP 3 (Opt)

ANP N (Cable)

SP1

CNP 1 CN

P 2

CNP 3

Access Network Provider Domain

Service/Application Provider Domain

Core Network Provider Domain

User

Resource-based Pol./Reg.

VoiceInternet

IP (Future Packet ?) Platform

xDSL/Opt. based Fixed-Mobile

Pol.Reg.

Pol. XReg. x

VideoMM

Service-based Pol./Reg.

New PolicyRegulationEnvironment (Horizontal)

Page 6: sdcvsdcs

Resulted NGN from FGNGN

NGN is

not but

Next Generation Internet

the IMS based network

only for a Fixed nor a Mobile network

any more best duties

any more closed public network

only for usage awareness

Next Generation PublicTelecommunication Net.IMS is a core part of NGN

Converged capabilities btw.Fixed-Mobile (FMC)

guaranteed duties

fully open I/F in access-core and service-transport

support various businesses

Page 7: sdcvsdcs

Key NGN Concepts

1. Terpisah antara service dan transport2. Personal dan terminal mobility3. Resource dan admission control4. Seleksi dan control QoS5. Akomodasi system dan terminal

legacy

Page 8: sdcvsdcs

Definisi NGNNGN adalah istilah yang luas digunakan untuk

menggambarkan evolusi arsitektur dalam backbone telekomunikasi dan jaringan akses.

Ide umum di belakang NGN adalah membawa informasi dan layanan (suara, data, dan segala macam media seperti video) ke dalam paket, mirip dengan yang digunakan di Internet.

NGN biasanya dibangun menggunakan Internet Protocol, Based On IP kadang-kadang digunakan untuk menggambarkan transformasi menuju NGN.

Page 9: sdcvsdcs

ITU DefinitionsA next-generation network (NGN) is a packet-based

network which can provide services including Telecommunication Services and able to make use of multiple broadband, quality of Service-enabled transport technologies and in which service-related functions are independent from underlying transport-related technologies.

It offers unrestricted access by users to different service providers.

It supports generalized mobility which will allow consistent and ubiquitous provision of services to users

Page 10: sdcvsdcs

Key point of the NGN Definition

Page 11: sdcvsdcs
Page 12: sdcvsdcs

Scope+ServiceReq.+Capa.

(6)

General

Funct.

Archit.

(7)

NGN Definition and Features(ITU-T Rec. Y.2001, 2011)

Future Packet Based Networks (8)

Quality of Service aspects (1)

Control of QoS (2)

Resource Adm./Cont. aspects (3)

Security aspects (4)

Migration aspects (5)

Page 13: sdcvsdcs

Model Referensi Arsitektur Jaringan

Page 14: sdcvsdcs

14

Architecture of Architecture of NGNNGN

Page 15: sdcvsdcs

15

NGN Architecture NGN Architecture OverviewOverview

ServicesApplication Function

Service User Profile

FunctionsControl

Service stratum

Transport stratum

Network Attachment Control Functions

Transport User Profile

Functions

Transport Control Functions

Media Handling Functions

Gateway FunctionsGateway Functions

Rnd-User Functions

Service and Control Functions

Man

agem

ent F

unct

ions

UNI

Access Functions

Access TransportFunctions

Edge Functions

Core TransportFunctions

Access Functions

Access TransportFunctions

Edge Functions

Access Functions

Access TransportFunctions

Core TransportFunctions

Edge Functions

Access Functions

Access TransportFunctions

Core TransportFunctions

Edge Functions

Access Functions

Access TransportFunctions

Edge Functions

Access Functions

Access TransportFunctions

Core TransportFunctions

NNI

Gateway Functions

Otther networks

ControlMediaManagement

Page 16: sdcvsdcs

General principles of the NGN functional architecture

The NGN functional architecture shall incorporate the following principles.1.1. Support for multiple access technologies :Support for multiple access technologies :

The NGN functional architecture shall offer the configuration flexibility needed to support multiple access technologies.

2. 2. Distributed control:Distributed control:This will enable adaptation to the distributed processing nature of IP networks and support location transparency for distributed computing.

3. 3. Open control:Open control:The network control interface should be open to support service creation, service updating, and incorporation of service logic provision by third parties.

Page 17: sdcvsdcs

4.4. Independent service provisioning:Independent service provisioning:The service provision process should be separated from network operation by using the above-mentioned distributed, open control mechanism. This is intended to promote a competitive environment for NGN development in order to speed up the provision of diversified value-added services.

5.5. Support for services in a converged Support for services in a converged network:network:This is needed to generate flexible, easy-to-use multimedia services, by tapping the technical potential of the converged, fixed-mobile functional architecture of the NGN.

6.6. Enhanced security and protection :Enhanced security and protection :This is the basic principle of an open architecture.It is imperative toprotect the network infrastructure by providing mechanisms for security and survivability in the relevant layers.

Page 18: sdcvsdcs

Prinsip umum dari arsitektur fungsional NGN

Mensupportteknologi multiple akses

Distributed control

Open control

Proses service provision dipisahkan dari operasi jaringan

Support untuk service pada jaringan terpusatSecurity

Enhancements

Page 19: sdcvsdcs

Transport stratum functionsTransport stratum functionsA. Transport functions

• Provide the connectivity for all components and physically separated functions within the NGN.• Provide support for the transfer of media

information,• as well as the transfer of control and

management information.• Transport functions include :

1. access network functions,2. edge functions,3. core transport functions, and4. gateway functions.

Page 20: sdcvsdcs

1. Access network functionsThe access network functions :

• Take care of end-users’access to the network as well as collecting and aggregating the traffic coming from these accesses towards the core network.

• Also perform QoS control mechanisms dealing directly with user traffic.

The access network includes access-technology dependent functions, e.g. related to :

1)Cable access2)xDSL access3)Wireless access, e.g :

a. IEEE 802.11 and 802.16 accessb. 3G RAN access

4)Optical access

Page 21: sdcvsdcs

2. Edge functionsThe edge functions :

• Merge media and traffic processing coming from different access networks into the core transport network;

• Support for QoS and traffic control.The edge functions are also used between

core transport networks.

Page 22: sdcvsdcs

3. Core transport functionsThe Core transport functions are responsible

for ensuring information transport throughout the core network.• Provide the means to differentiate the quality

of transport in the core network.• Provide QoS mechanisms dealing directly with

user traffic

Page 23: sdcvsdcs

4. Gateway functions• Provide capabilities to interwork with end-user

functions and other networks, including other types of NGN and many existing networks, such as the PSTN/ISDN, the public Internet, and so forth.

• Gateway functions can be controlled either directly from the Service Control functions or through the Transport control functions

5. Media handling functions• Provides media resource processing for service

provision, such as generation of tone signals and trans-coding.

• These functions are specific to media resource handling in the transport stratum.

Page 24: sdcvsdcs

B Transport control functionsThe Transport control functions include :

• Resource and Admission Control Functions and• Network Attachment Control Functions.

1. Resource and Admission Control Functions (RACF), provide :

• QoS control (including resource reservation, admission control and gate control), NAPT and/or FW traversal control Functions over access and core transport networks.

• Admission control involves checking authorisation based on user profiles, SLAs, operator specific policy rules, service priority, and resource availability within access and core transport.

Page 25: sdcvsdcs

• Within the NGN architecture, the RACF act as the arbitrator for resource negotiation and allocation between Service Control Functions and Transport Functions for Session-based applications (e.g. SIP call) and non-session based applications (e.g. Video Streaming) that require the control of NGN transport resource, including QoS control and NAPT/FW control and NAT Traversal.

• The RACF interact with Transport Functions for the purpose of controlling one or more the following functions in the transport layer :• Packet filtering;• Traffic classification, marking, policing, and

priority handling;• Bandwidth reservation and allocation;• Network address and port translation;• Firewall.

Page 26: sdcvsdcs

• The RACF interact with Network Attachment Control Functions (NACF), including :• network access registration,• authentication and authorization,• parameters configuration) for checking user

profiles and SLAs held by them.• For those services across multiple providers or

operators, Service Control Functions, RACF and Transport Functions may interact with the corresponding functions in other packet networks.

NOTE: The details and other aspects of the RACF are specified in TR-RACF [5].

Page 27: sdcvsdcs

2. Network Attachment Control Functions (NACF)

• Provide registration at the access level and initialization of end-user functions for accessing NGN services.

• These functions provide network-level identification/ authentication, manage the IP address space of the access network, and authenticate access sessions.

• They also announce the contact point of NGN Service/Application support functions to the end user.

The NACF provide the following functionalities :• Dynamic provision of IP addresses and other user

equipment configuration parameters.• Authentication at the IP layer (and possibly other

layers)• Authorization of network access, based on user

profiles.• Access network configuration, based on user

profiles.• Location management at the IP layer.

Page 28: sdcvsdcs

Service Stratum functions• This abstract representation of the functional

grouping in the service stratum includes the Service control functions and the Application/ Service support functions, as well as service user profiles.

Page 29: sdcvsdcs

1. Service control functionsThe Service control functions include both session and non-session control, registration, and authentication and authorization functions at the service level. They can also include functions for controlling media resources, i.e., specialized resources and gateways at the service-signalling level.

Page 30: sdcvsdcs

2. Application/Service support functionsThe Application/Service support functions include functions such as the gateway, registration, authentication and authorization functions at the application level. These functions are available to the “Third-Party Applications” and “End-User” functional groups. The Application/Service support functions work in conjunction with the Service control functions to provide end-users and third party application providers with the value added services they request. Through the UNI, the Application/Service support functions provide a reference point to the end-user functions (e.g., in the case of third-party call control for Click to Call service). The Third-party applications’interactions with the Application/Service support functions are handled through the ANI reference point.

Page 31: sdcvsdcs

3. Service user profile functionsThe service user profile functions represent the combination of user information and other control data into a single user profile function in the service stratum, in the form of a functional database. This functional database may be specified and implemented as a set of cooperating databases with functionalities residing in any part of the NGN.

Page 32: sdcvsdcs

End-user functionsNo assumptions are made about the diverse

end-user interfaces and end-user networks that may be connected to the NGN access network. Different categories of end-user equipment are supported in the NGN, from single-line legacy telephones to complex corporate networks. End-user equipment may be either mobile or fixed.

Page 33: sdcvsdcs

Management functionsSupport for management is fundamental to the

operation of the NGN. These functions provide the ability to manage the NGN in order to provide NGN services with the expected quality, security, and reliability. These functions are allocated in a distributed manner to each functional entity (FE), and they interact with network element (NE) management, network management, and service management FEs. Further details of the management functions, including their division into administrative domains, can be found in M.3060 [6]. Management functions apply to the NGN service and transport strata. For each of these strata, they cover the following areas:

Page 34: sdcvsdcs

a) Fault managementb) Configuration managementc) Accounting managementd) Performance managemente) Security managementThe accounting management functions also include charging and billing functions (CBF). These interact with each other in the NGN to collect accounting information, in order to provide the NGN service provider with appropriate resource utilization data, enabling the service provider to properly bill the users of the system. A detailed description of the CBF functions can be found in clause 7.5.

Page 35: sdcvsdcs

35

Bandwidth Saving:64 K compare to 8 kbps (ITU G.729)

Saving about 7/8 = 87,5 % Increasing level of network optimization

Footprint comparison for 36.000 linePSTN : SS = 13 racks : 1 rack171.60 : 13.20 (converting for cost comparison)

Power consumptionPSTN : SS = 600 A : 24 A 62.40 : 4.80 (converting for cost comparison)

• Other benefits of NGN

Page 36: sdcvsdcs

Badan Standardisasi NGN

Page 37: sdcvsdcs

37

• Cooperation with other std bodies

Page 38: sdcvsdcs

ATIS Next Generation Network (NGN) Framework Part I: NGN Definitions, Requirements, and Architecture

* NOTE: ITU-T is recognized as the principal global organization for defining a global NGN standard. The ATIS NGNFG is primarily interacting with the ITU-T FGNGN; however it is recognized that other groups in ITU-T (e.g., SG11, SG13) and other groups in ATIS (e.g., PTSC) that are also concerned with aspects of the NGN.

Page 39: sdcvsdcs

•. ITU-T: SG13, International Standard Union()etworks (FGNGN)•. 3rd Generation Partnership Project (3GPP)•. European Telecommunications Standards Institute (ETSI) TISPAN•. Multiservice Switching Forum (MSF)•. DSL Forum (DSL-F)•. CableLabs™•. Institute for Electrical and Electronics Engineers (IEEE)•. ATIS Technical Committees (e.g., PTSC, TMOC, NIPP)•. 3rd Generation Partnership Project #2 (3GPP2)•. Telecommunications Industry Association (TIA)•. Internet Engineering Task Force (IETF)•. National Emergency Numbering Association (NENA)•. Emergency Services Interconnection Forum (ESIF)•. TTY Forum•. Industry Numbering Committee (INC)•. FCC Network Reliability & Interoperability Council (NRIC)•. Open Mobile Alliance (OMA)•. Metro Ethernet Forum (MEF)•. MPLS and Frame Relay Alliance

Page 40: sdcvsdcs

1.1. ITU-T: ITU-T:The appropriate ITU-T Study Groups, including SG13 and its Focus Group on Next Generation Networks (FGNGN), are responsible for the global standards surrounding NGN telecommunications.The ITU-T work can be expedited by having individual organizations or regional SDOs submitcontributions to the ITU-T that have a regional consensus. While this approach may not eliminateneed for collaboration between ATIS and other standards bodies, it should reduce the amount of such collaboration required, while resulting in more harmonized global standards. Such a workflow recognizes the global scope of the ITU-T, while expediting a path for regional input from ATIS into the global standards. Further more, this flow does not exclude the ability for ATIS to develop regional extensions for the ITU-T standards, although such extensions should be minimized and created onlywhen truly needed. The goal is a universal global standard without the need for regional extensions.

Page 41: sdcvsdcs

22 ETSI TISPAN ETSI TISPANTISPAN is the ETSI core competence center for fixed networks and for migration from switched-circuit networks to packet-based networks with an architecture that can serve in both. TISPAN is the result of the merging of Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) and Service and Protocol for Advance Networks (SPAN) groups in ETSI. TISPAN is the ETSI groupresponsible for all aspects of standardization for present and future converged networks, including the NGN and including service aspects, architectural aspects, protocol aspects, QoS studies, security related studies, and mobility aspects within fixed networks, using existing and emerging technologies.TISPAN is developing a architecture for NGN based on the 3GPP IMS subsystem (release 6). This architecture is named “extended IMS” throughout this document and is considered the base for ATIS NGN work.Please, refer to clause 3 for the description of the ATIS NGN Converged architecture based on TISPAN extended IMS.

Page 42: sdcvsdcs

3.3. 3GPP 3GPPThe 3rd Generation Partnership Project (3GPP) is a collaboration agreement that was established in December 1998. The collaboration agreement brings together a number of telecommunications standards bodies known as Organizational Partners (see < http://www.3gpp.org/Management/OP.htm >).The current Organizational Partners are ARIB, CCSA, ETSI, ATIS, TTA, and TTC. The establishment of 3GPP was formalized in December 1998 by the signing of the 3rd Generation Partnership Project Agreement (see < http://www.3gpp.org/About/3gppagre.pdf >).The original scope of 3GPP was to produce globally-applicable Technical Specifications and Technical Reports for a 3rd Generation Mobile System based on evolved Global System for Mobile communication (GSM) core networks and the radio access technologies that they use. The scope was subsequently amended to include the maintenance and development of the GSM TechnicalSpecifications and Technical Reports including evolved network and radio access technologies -- e.g.,General Packet Radio Service (GPRS), Enhanced Data rates for GSM Evolution (EDGE), Universal Mobile Telephone System (UMTS) and IP Multimedia Subsystem (IMS).3GPP2 is a parallel partnership covering specifications for CDMA-2000. Both 3GPP and 3GPP2 are closely aligned with ITU-T 3G standards.

Page 43: sdcvsdcs

44 MSF MSFThe Multi-service Switching Forum (MSF) is a global forum with the primary objective of accelerating the commercial availability and interoperability of multiservice networks. The MSF accomplishes this objective by focusing on end-to-end solutions leveraging standards, architectures, and inputs from other SDOs (i.e.,, IETF, ITU, Parlay/OSA, 3GPP, etc.) and the prioritization of member companies. The MSF has significant experience in the creation and validation of architectures, Implementation Agreements (IAs), and large scale demonstration of interoperability for VoIP solutions that are fit foruse by service providers. The MSF has significant work in progress that may be useful for the ATIS NGN Framework.

More detailed information on the MSF, MSF GMI-2004 Program, and Published documents can be found at < http://www.msforum.org >. Publicly available MSF documents are available at <http://www.msforum.org/techinfo/approved.shtml >.

Page 44: sdcvsdcs

55 DSL-F DSL-FThe DSL Forum, a consortium of industry telecommunications, equipment, computing, networking, and service provider companies, was established in 1994 and continues its drive for a mass market for DSL to deliver the benefits of this technology to end users around the world over existing copper telephone wire infrastructures. The evolution of existing infrastructure towards NGN services provides a significant mechanism for NGN deployment. DSL Forum < http://www.dslforum.org/ > has developed a number of documents regarding the architecture and capabilities of the DSL based access infrastructure. The following published documents are of particular relevance:. TR-058, Multi-Service Architecture & Framework Requirements, September 2003.. TR-059, DSL Evolution – Architecture Requirements for the Support of QoS Enabled IP services,September 2003.. TR094, Multi-Service Delivery Framework for Home Networks, August 2004.

Current work in progress items are also addressing topics of concern including:. WT-101, Migration to Ethernet Based DSL Aggregation. WT-102, Architecture & Transport: Service Interface Requirements for TR-058 ArchitecturesThe architecture described in the DSL Forum documents is one of the inputs that will be considered in the standards gap analysis.

Page 45: sdcvsdcs

66 CableLabs® CableLabs®Cable Television Laboratories, Inc. (CableLabs®) is a nonprofit research and development consortium that is dedicated to helping its cable operator members integrate new cable telecommunications technologies into their business objectives. A significant portion of consumer wireline Internet access is provided via cable infrastructure.NOTE - Although not further addressed in this document, CableLabs® PacketCableTM Multimedia Architecture (PKTTR-MM-ARCH-V01-030627) should be considered as another technology for delivery of NGN services. The cable operators are expected to continue to evolve their infrastructure capabilities.

77 IEEE IEEEThe IEEE 802 LAN/MAN Standards Committee develops Local Area Network (LAN) standards and Metropolitan Area Network (MAN) standards. The most widely-used standards are for the Ethernet family, Token Ring, Wireless LAN, Bridging, and Virtual Bridged LANs. An individual Working Group provides the focus for each area. The IEEE has significant work in progress that may be useful for the ATIS NGN Framework. This work includes various forms of access to the NGN including:Ethernet in the First Mile (EFM), WiFi, and WiMAX.

Page 46: sdcvsdcs

8 8 ATIS Technical CommitteesATIS Technical CommitteesOne of the primary ATIS Technical Committees for NGN standards is the PTSC.• PTSC (formerly T1S1): the Packet Technologies and Systems Committee

o Coordinates and develops standards and technical reports relevant to telecommunications networks in the U.S.

o Reviews and prepares contributions on such matters for submission to U.S. ITU-T and U.S. ITU-R Study Groups or other standards organizations

o Reviews for acceptability or per contra the positions of other countries in related standards development and takes or recommends appropriate actions

Page 47: sdcvsdcs

Automatic Terminal Information Services (ATIS)

CAKUPAN KERJA

- infrastruktur jaringan IP masa sekarang dan masa datang

- penggabungan layanan multimedia termasuk IPTV

- pengembangan business operation dan business support system

- peningkatan level qualitas layanan dan performansi