evolution towards NGN
-
Upload
ajal-jose -
Category
Technology
-
view
425 -
download
1
description
Transcript of evolution towards NGN
synergies between IP, mobile and telephony networks evolution towards NGN
AJAL.A.J
Assistant Professor –Dept of ECE,
Federal Institute of Science And Technology (FISAT) TM
MAIL: [email protected]
Target NGN
• IP services and network current state,
• control plane architecture,
• VoIP,
• Mobility and nomadism ,
• QoS support,
• IPv6 migration,
Network topography & terminology
CoreAccess Edge
ConcentratingMultiplexing
Local switchingor forwarding
Long haul switchingor forwarding
Local
NA
CoreAccess Edge
ConcentratingMultiplexing
Local switchingor forwarding
Long haul switchingor forwarding
Local
NA
I A D
A c c e s s s e r v i c e s M a n a g e m e n t
G P R S , U M T S
r e s i d e n t i a l , S M E
N T U s o h o
O F
C N N C N N
R P F
S P F
A P F
I A D I n t e g r a t e d A c c e s s D e v i c e A N A c c e s s N o d e C N N C o r e N e t w o r k N o d e E N N E d g e N e t w o r k N o d e N T U N e t w o r k T e r m i n a t i o n U n i t O T N O p t i c a l T r a n s p o r t N e t w o r k R P F R e s o u r c e s C o n t r o l P l a t - f o r m S P F S e r v i c e s C o n t r o l P l a t - f o r m A P F A c c e s s t o t h e s e r v i c e s P l a t f o r m
S e r v i c e s M a n a g e m e n t
R e s o u r c e s M a n a g e m e n t
A c c e s s
E d g e / C o r e
N e t w o r k r e s o u r c e s
l o g i c a l l i n k s
x D S L , O F
A N
R P F
E N N
I n t e r n e t
I A P / I S P
B o r d e r N o d e
L o c a l N G N C o r e N G N
POSSIBLE LOCAL AND CORE NGNS
Access Edge+Core
POTS ISDN
ADSL cable
GSM
SS7
Internet
NAS
NAS
BAS
SCP
SG
Call Server
Radius Server
Back O ffice
Leased Line IAP/ISP
Edge Router
Core Router
Edge Router
Border Router
Border Router
BAS: Broadband Access Server NAS : Network Access Server SCP: Service Control Point SG: S ignalling Gateway
Custom er
Traditional domestic IP network
Services
• Two main services are supported:
1. aggregation services that consist in collecting the traffic of not-always connected users through Access Servers such as NAS and BAS and delivering it to IAPs/ISPs,
2. transport services that convey the traffic of always connected users between sites directly attached to the IP network and towards Internet.
Service Plane
PSTNIP
Media gatewayCAA
Gatekeepers
orProxySIP
SCP SCP/IP
Management
CCF
SIP
INAP/IP
SS7
Signaling gateway
H.323
Sigtran
API
Application serverService Plane
PSTNIP
Media gatewayCAA
Gatekeepers
orProxySIP
SCP SCP/IP
Management
CCF
SIP
INAP/IP
SS7
Signaling gateway
H.323
Sigtran
API
Application server
PSTNIP
Media gatewayCAA
Gatekeepers
orProxySIP
SCP SCP/IP
Management
CCF
SIP
INAP/IP
SS7
Signaling gateway
H.323
Sigtran
API
Application server
VoIP (H.323 and SIP) general architecture
Concerning service development, there are two major possibilities:
1. Using an INAP/IP interface, IN existing services could be used. It seems to be a good way in order to offer classical IN services,
2. Using an API or proprietary protocols, application server could be used in order to develop new multimedia services.
Legacy Signaling Network
Multimedia IP Network
Application
Network Service and Control
Transport Transport
Platform (MGW, GSN)
UTRA UTRAN
SCP SCP Application servers (WAP, MExE , … )
AP AP AP AP AP AP AP AP
EIR EIR MGCF MGCF
CSCF CSCF R-SGW R-SGW
T-SGW T-SGW
Transport Platform (MGW, GSN)
MSCS MSCS SGSNS SGSNS
GMSCS GMSCS GGSNS GGSNS
PSTN
MRF MRF MRF
HSS HSS
Mc X
Nc
Mc X Iu
Iu
CAP CAP CAP
Y Gf Gr D C Gc Gi
Mr Mc
Mg
Gi
Mh Cx Ms
Mm
NGN introduction in CS and PS domains – post R5 architecture.
Mobile IP architecture and principles.
IP Network
Sub Network
NC
NM
HA
Home Sub Network
Visited Sub Network
FARegister
DATA
IP Network
Sub Network
NC
NM
HA
Home Sub Network
Visited Sub Network
FARegister
DATA
QoS support
• QoS-enabled applications,• QoS policy management and enforcement,• QoS control through static, dynamic or
scheduled procedures,• QoS monitoring at the network and customer
levels,• per-QoS class accounting and charging,• inter-domain QoS support,• QoS economic model between peers.
IPv6 migration
• IPv6 supports a number of enhanced features, such as:
1. larger unicast and multicast address space,2. anycast address,3. aggregatable addressing for hierarchical routing,4. host address auto configuration,5. easy site renumbering,6. flow identification for QoS support,7. streamlined packet formats for improved forwarding
performance,8. multicast support (explicit scope),9. extension headers used for supplementary capabilities,10.security providing packet authentication and encryption,11.mobility improvement through auto configuration, security,
anycast address and destination options.
References 1. "A Next generation architecture for the public network " ISS20002. TINA-C Network Resource Architecture, version 3.0 – Feb. 19973. TIPHON Network Architecture & reference configurations, DTS 02003 v0.0.1 – ETSI – March
19994. Multiservice Switching Forum Architecture, MSF99.074 – March 19995. Megaco Protocol Proposal Working draft, draft-IETF- megaco-protocol-01.txt – April 1999 6. Draft ITU-T Recommendation Q.BICC, Bearer Independent Call Control protocol definition7. RFC 2543 SIP : Session Initiation Protocol8. RFC 3015 Megaco Protocol v1.0 9. RFC 2002 IP mobility Support (for Ipv4)10. Universal Mobile Telecommunications System (UMTS); Virtual Home Environment (VHE) in
the Integrated Services Digital Network, Evolved UMTS core network, ETSI EG 201 717.11. Universal Mobile Telecommunications System (UMTS); Service aspects; Virtual Home
Environment (VHE), ETSI TR122 970, 3G TR 22.970.12. Eurescom Project P920, UMTS Network Aspects (
http://www.eurescom.de/public/projects/P900-series/p920/P920.htm13. RFC 1633 Integrated Services in the Internet Architecture: an Overview14. RFC 2475: An Architecture for Differentiated Services15. RFC 3031: Multiprotocol Label Switching Architecture16. draft-ietf-mpls-diff-te-reqts-00: Requirements for support of Diff-Serv-aware MPLS Traffic
Engineering17. RFC 1883: Internet Protocol Version 6 (IPv6)