Sie sind auf Seite 1von 77

NGN Architecture and


Jeong Yun KIM


 Introduction
 NGN Components
 NGN Architecture
 Transport Stratum
 Service Stratum
 PSTN/ISDN Emulation Service Component
 Call Server-based
 IMS-based
 Next Step
 Appendix : ETRI’s BcN Products


Current Network NGN

•CAPEX/OPEX efficiency
• Fast service creation/delivery
• Multi-terminal support
• Enabling integrated/blended service

Definition of NGN

General principles of NGN
 Support for Multiple Access Technologies
 Distributed control
 distributed processing nature of IP networks
 location transparency for distributed computing

 Open control
 support service creation, service updating, and incorporation of
service logic provision by third parties
 Independent service provisioning
 Separation network operation from distributed, open control
 promote a competitive environment for NGN development in order
to speed up the provision of diversified value-added services

General principles of NGN
 Support for the services in a converged 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.
 Enhanced security and protection
 This is the basic principle of an open architecture. It is imperative to
protect the network infrastructure by providing mechanisms for
security and survivability in the relevant layers
 Functional entity characteristics
 Functional entities may not be distributed over multiple physical
units but may have multiple instances

NGN Architecture Overview
 NGN functions are divided into service stratum functions and
transport stratum functions

Application Support Functions & Service Support Functions

Service User
Service Control
Management Functions

Profiles Functions
Service stratum

Network Attachment
Control Functions Resource and
Transport User Control Functions
End-User Other
Functions Transport Control Functions

Transport Functions
Transport stratum

NGN Components

NGN Components
Service Stratum
Application Support Functions and
Application Service Support Functions

S. User Other NGN Service Control
Profile Components Functions

PSTN / ISDN Emulation

Service Component

Other Networks
IP Multimedia Component
IP Multimedia
&PSTN/ISDN Simulation
Service Component
Network Access
User Network Attachment
T.User Resource and Admission
GW Profile Control Functions
ProfileAttachment Control Functions
Legacy Functions

Access Network Core
Core Transport
Access Transport
Functions Edge Functions
NGN Functions
End-User Transport Stratum
* Note: Gateway (GW) may exist in either Transport Stratum
or End-User Functions.
NGN service-specific components
 IP Multimedia Service component
 It supports mediated multimedia services
 voice or video telephony or PSTN/ISDN simulation,
 subscribe/notify for presence information and the message method for
message exchange

 PSTN/ISDN Emulation Service component

 It refers to the provision of PSTN/ISDN service capabilities and
interfaces using adaptation to an IP infrastructure.
 It enables the support of legacy terminals connected through a
gateway to an IP network.
 All PSTN/ISDN services remain available and identical, such that end
users are unaware that they are not connected to a TDM-based

NGN service-specific components
 Other NGN service components
 The definition of other NGN service-specific components is for
further study.
 Service specific components may be required in order for the NGN
to support services such as content delivery services, multimedia
multicast or broadcast services , push services, data retrieval
applications, data communication services, online applications,
sensor network services, remote control services, and over-the-
network device management

NGN transport-specific components
 Network Attachment Control Function component
 Network-level Authentication, Authorization and IP address
allocation for a user/terminal

 Resource Admission Control Function component

 QoS management according to the service request from a user

NGN Architecture

Transport Functions
 The transport functions provide the connectivity for all
components and physically separated functions within the
 Access Network functions
 End-users’ access to the network
 collecting and aggregating the traffic coming from these accesses
towards the core network
 perform QoS control mechanisms dealing directly with user traffic

 Edge functions
 used for media and traffic processing when aggregated traffic
coming from different access networks is merged into the core
transport network

Transport Functions
 Core transport functions
 ensuring information transport throughout the core network

 Gateway functions
 interworkwith end user functions and other networks including
other NGNs and many existing networks

 Media handling functions

 media resource processing for the services provision, such as
generation of tone signals and trans-coding

Transport Control Functions
 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
 act as the arbitrator for resource negotiation and allocation between
Service Control Functions and Transport Functions
 interacts with Service Control Functions and Transport Functions for
Session-based applications (e.g. SIP call or video streaming)
 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

Transport Control Functions
 Network Attachment Control functions (NACF)
 provide registration at access level and initialization of End-user
functions for accessing to the NGN services
 provide network level identification/authentication, manage the IP
address space of the Access Network and authenticate access sessions
 announce the contact point of the NGN Service/Applications
functions to the end user
 Functionalities
 Dynamic provisioning of IP addresses and other user equipment configuration
 By endorsement of user, auto-discovery of user equipment capabilities and other
 Authentication of end user and network 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

Functions of Service Stratum
 Service Control Functions
 include resource control, registration, and authentication and
authorization functions at the service level for both mediated and non-
mediated services
 include functions for controlling media resources, i.e., specialized
resources and gateways at the service-signaling level
 accommodate service user profile

 Application Support Functions and Service Support

Functions (ASF&SSF)
 include functions such as the gateway, registration, authentication and
authorization functions at the application level
 work in conjunction with the Service control functions to provide
end-users and applications with the value added services they request

The others
 End User Functions
 No assumptions are made about the diverse end-user interfaces and
end-user networks that may be connected to the NGN access
network. End-user equipment may be either mobile or fixed
 Management Functions
 manage the NGN in order to provide NGN services with the
expected quality, security, and reliability
 are allocated in a distributed manner to each functional entity (FE)
 interact with network element (NE) management, network
management, and service management FEs
 Fault management
 Configuration management
 Accounting management: include charging and billing functions
 Performance management
 Security management

NGN Service Architecture
 Three distinct domains
 “Applications”
 “Application Support functions and Service Support functions” in the
service stratum of the NGN
 “certain NGN resources and capabilities”, including those in the transport
stratum, capabilities such as presence, location information, charging
function, security schemes

 Applications domain
 those trusted by network/server providers: network/server providers
themselves and subordinate organizations or partners
 those that are not: independent service providers

 Application Network Interface (ANI)

 the functional area of “ASF&SSF” offers service-enabling resources to the
“Applications” area, independently of the underlying network technologies

NGN Functional Architecture
A p p lic a tio n s
Management functions

A p p lic a tio n S u p p o r t F u n c tio n s & S e r v ic e S u p p o r t F u n c tio n s
(m a y in c lu d e o w n A u th en tic atio n , A u th o riza tio n a n d A cc o u n tin g )

S e rvice S -6 : S . S -1 2 : N e tw o r k
co n tro l S -5 : S . U ser A u th e n tic a tio n & S ig n a lin g
S -1 4 : M e d ia
P r o f ile F E A u th o r iz a tio n F E In te rw o r kin g F E
R e so u rce B ro ke r F E
S -3 : In te rro g a tin g C a ll
S -4 : S u b sc r ip tio n S -7 : In te rco n n e c tio n
S e ssio n C o n tro l F E
L o c a to r F E
S -1 5 : G e n e r a l
B o r d er G a tew a y
C o n tro l F E
O th e r N G N
S e r v ice s C o n tr o l F E
S -1 0 : B re a k o u t
S -2 : P ro x y C a ll S e ssio n G a tew a y C o n tr o l
C o n tro l F E S -1 : S er v in g
C a ll S e ssio n C o n tr o l F E
S -9 : M e d ia
S -1 1 : U ser S ig n a lin g S -8 : A cc e ss G W S -1 3 : M e d ia R e so u rce GW
In te rw o r kin g F E C o n tro l F E C o n tro l F E C o n tro l F E
M u ltim e d ia
T -1 5 : H o m e G a te W a y
T -1 6 : P o lic y D ecisio n F E N e tw o rk s
C o n f ig u ra tio n F E T -1 6 : P o lic y D ecisio n F E
T -1 7 : T ra n sp o r t
T -1 2 : T . U s e r T -1 3 : T . L o c a t io n T -1 7 : T r a n sp o r t R e so u r ce C o n tro l F E
P r o file F E m anagem ent FE R e so u rce C o n tr o l F E

E n d -U se r U N I T -1 1 : T -1 0 : C o re tra n sp o rt
T . A u th e n tic a tio n N e tw o r k A cc e s s
F u n c tio n & A u th o r iza t io n C o n f ig u r a tio n F E T -9 :
FE T -8 :
S ig n a llin g
M e d ia
L eg a cy G a tew a y
R e so u rce
T er m in a l T -1 4 : A c c e ss M a n a g e m e n t F E FE
P ro ce ssin g
RGW T -6 :
A cce ss tra n sp o rt In te r -
C u sto m e r T -4 : A cce ss
T -5 : co n n e c tio n
N e tw o r k R e la y F E
A c ce ss B o r d er
B o r d er G a tew a y F E
T -2 : A cce ss T -3 : E d g e
N ode F E G a te w a y
N ode F E
FE T -7 :
NGN T r u n k in g
T er m in a l T -1 : A cce ss M e d ia
M e d ia A c c e ss P a c k e t T ra n sp o rt F u n c tio n s G a tew a y P S T N /IS D N
G a tew a y FE
L eg a cy FE C o re P a c k e t T ra n sp o rt F u n c tio n s
T er m in a l

Scope of N G N
FEs of Transport Functions

TC-T1 TC-T2 TC-T3 S-T2 TC-T5 TC-T6 TC-T4 S-T1 S-T3 A-T1 TC-T9 S-T5 S-T4

T-9:Signalling T-ON1
Gateway FE

T-U1 T-4:Access Relay

T-8: Media
Resource Processing FE

T-6: Interconnection T-ON2

T-1: Access Media Border Gateway FE
T-U2 Gateway FE Core Transport Functions

T-7:Trunking Media
Gateway FE
T-3: Edge Node T-5:Access Border
T-U3 T-2:Access Node FE Access Transport Functions FE Gateway FE

Access Transport Processing Core Transport Processing

FEs of Transport Functions
 Access Media Gateway Functional Entity (AMG-FE)
 provides interworking between the packet-based transport used in
the NGN and analogue lines or ISDN access
 provides bi-directional media processing functions for user plane
traffic between PSTN/ISDN and the NGN under the control of the
 provides adequate transfer functions for PSTN/ISDN user call
control signalling to the AGC-FE for processing.
 optionally supports payload processing functions (e.g., codecs and
echo cancellers).
 provides the TDM/IP interworking function (refer to Y.TDMIP ) to
support ISDN emulation service in case ISDN unrestricted bearer is

FEs of Transport Functions
 Access Node Functional Entity (AN-FE)
 directly connects to End user functions and terminates the
first/last mile link signals at the network side.
 Generally, it is a Layer 2 device that may be IP capable

 may perform packet filtering, traffic classification, marking,

policing and shaping at flow level or user level under the control of
the RACF
 should support the functions of Policy Enforcement Functional
Entity (PE-FE) and controlled by the RACF

FEs of Transport Functions
 Edge Node Functional Entity (EN-FE)
 connects to core packet transport functions and terminates the
Layer 2 access session with the End-user functions
 It shall be a Layer 3 device with IP forwarding capabilities

 performs packet filtering, traffic classification, marking, policing

and shaping at flow level or user level under the control of the
 should support the functions of Policy Enforcement Functional
Entity (PE-FE) and controlled by the RACF

FEs of Transport Functions
 Access Relay Functional Entity (AR-FE)
 a relay between End-User functions and the NAC-FE that inserts local
pre-configuration information when necessary
 For example when using DHCP, the AR-FE acts as a DHCP Relay Agent

 Access Border Gateway Functional Entity (ABG-FE)

 A packet gateway between an access network and a core network used
to mask a service provider’s network from access networks, through
which End-user functions accessing packet-based services
 may include opening and closing gate, packet filtering based firewall,
traffic classification and marking, traffic policing and shaping, network
address and port translation, media relay (i.e. media latching) for NAT
traversal, and collecting and reporting resource usage information
 support the functions of PE-FE controlled by the RACF

FEs of Transport Functions
 Interconnection Border Gateway (IBG)-FE
a packet gateway used to interconnect an operator’s core
network with another operator’s core network supporting the
packet-based services
 shall support the functions of PE-FE (except for remote NAPT
Traversal) controlled by the RACF
 Media conversion (e.g., G.711 and AMR, T.38 and G.711)

 Inter-domain IPv4/IPv6 conversion

 Media encryption

 Fax/modem processing

FEs of Transport Functions
 Trunking Media Gateway (TMG)-FE
 provides interworking between the packet-based transport used in
the NGN and trunk lines from the circuit-switched network.
 It is under the control of the MGC-FE.

 may support payload processing (e.g., codecs, echo cancellers, and

conference bridges)
 optionally provides the TDM/IP interworking function (refer to
Y.1453 ) in order to support ISDN emulation service in case ISDN
unrestricted bearer is needed

 Signalling Gateway (SG)-FE

 isresponsible for signaling transport interworking between the
NGN and existing networks such as PSTN, ISDN, IN networks, and
Signaling System No.7

FEs of Transport Functions
 Media Resource Processing (MRP)-FE
 provides payload processing of packets used in the NGN
 allocates specialized resources (such as announcement server,
notification tone, and voice recognition resources, and voice menu
and conference resources).
 provides media mixing functions under the control of the MRC-
 receives and generates DTMF signals.

 generates tone signals (e.g., ring back).

 generates announcements.

 provides trans-coding, text-to-speech, video mixing, conference

bridge, data conference, fax, voice and video recording, and voice
recognition capabilities.

FEs of Transport Control Functions

TC-Ux T-15: Home GateWay
Configuration FE TC-ON1
T-13: T. Location TC-TC1
T-16: Policy Decision FE
Management FE
T-12: T. User
Profile FE

T-11: T. Authentication T-10: Network

& Authorization FE Access Configuration FE T-17: Transport
Resource Control FE

TC-U1 T-14:
Access Management FE

TC-T1 TC-T3 (Note 1) TC-T2 (Note 3) TC-T5 (Note 3)

TC-T4 (Note 2) TC-T6 (Note 4) TC-T9 (Note 4)

Note 1: applicable when TRC-FE operates in the access network domain

Note 2: applicable when TRC-FE operates in the core network domain
Note 3: applicable when PD-FE operates in the access network domain
Note 4: applicable when PD-FE operates in the core network domain

FEs of Transport Control Functions
 Network Access Configuration (NAC)-FE
 IP address allocation to terminals
 may also distribute other network configuration parameters, such as
the addresses of DNS servers and signalling proxies (e.g., the
address of the P-CSC-FE in order to have access to service stratum
 should be able to provide an access network identifier to a
terminal This information uniquely identifies the access network to
which the terminal is attached
 discovery function to support auto configuration

 Transport Authentication and Authorization (TAA)-FE

 provides authentication and authorization functions in the transport
stratum, based on user profiles (TUP-FE), for network access

FEs of Transport Control Functions
 Transport User Profile (TUP)-FE
 storinguser profiles (e.g., QoS profile, P-CSC-FE address, and
HGC-FE address) related to the transport stratum
 responses to TAA-FE queries for user profiles

 Transport Location Management (TLM)-FE

 registers the association between the IP address allocated to the
User Equipment and related network location information provided
by the NAC-FE (e.g. access line identifier...)
 registers the association between network location information
received from the NAC-FE and geographical location information
 may also store the identity of the user / UE to which the IP address
has been allocated (information received from the TAA-FE), as
well as the user network QoS profile and user preferences regarding
the privacy of location information
FEs of Transport Control Functions
 Access Management (AM)-FE
 translates network access requests issued by the User Equipments.
It forwards the requests for allocation of an IP address and possibly
additional network configuration parameters to/from the NAC-FE
 forwards requests to the TAA-FE to authenticate the user,
authorize or deny the network access, and retrieve user-specific
access configuration parameters

 Home GateWay Configuration (HGWC)-FE

 isused during initialization and update of the HGW
 provides to the HGW with additional configuration information (e.g.
configuration of a firewall internally in the HGW, QoS marking of
IP packets etc.)

FEs of Transport Control Functions
 Policy Decision (PD)-FE
 provides a single contact point to the SCF and hides the details of
transport network to the SCF
 makes the final decision regarding network resource and
admission control based on network policy rules, SLAs, service
information provided by the SCF, transport subscription
information provided by the NACF in access networks, and
resource-based admission decision results provided by TRC-FE.
 controls the gates in the PE-FEs at per flow level.

 consists of transport technology-independent resource control

functions and is independent of the SCF as well.
 The policy rules used by PD-FE are service-based and are assumed
to be provided by the network operators

FEs of Transport Control Functions
 Transport Resource Control (TRC)-FE
 deals with the diversity of underlying transport technologies and
provides the resource-based admission control decision results
to PD-FE
 is service-independent and consists of transport technology-
dependent resource control functions.
 The PD-FE requests the TRC-FE instances in the involved transport
networks through the Rt reference point to detect and determine the
requested QoS resource along the media flow path
 may collect and maintain the transport network topology and
the transport resource status information and authorize
resource admission control of a transport network based on
network information such as topology and/or connectivity, network
and element resource availability, as well as the transport
subscription information in access networks

FEs of Service Control Functions
Application Support Functions & Service Support Functions

A-S1 A-S2 A-S3 A-S4 A-S5 A-S6

Service Control
S-5: Service User
S-14: Media Resource Profile FE
Broker FE
S-6: Service S-4: Subscription
Authentication Locator FE
S-15 General Services & Authorization FE S-12 Network
Control FE Signaling S-ON1
Interworking FE
S-U1 S-11: User S-3: Interrogating
S-2: Proxy Call
Signaling Call Session Control FE
S-U2 Session Control FE S-1: Serving Call Session S-7: Interconnection S-ON2
Interworking FE Control FE Border Gateway
Control FE

S-10 Breakout
Gateway Control S-ON3
S-13: Media S-8: Access FE
Resource Gateway Control
Control FE FE S-9: Media Gateway
Control FE

S-TC1 S-TC2 S-T1 S-TC3 S-T2 S-TC4 S-T3 S-T4 S-TC5 S-T5

FEs of Service Control Functions
 Serving Call Session Control (S-CSC)-FE
 handles functionality related to session control, e.g., registration,
origination of sessions (session setup, modification, and teardown),
and routing of session messages
 Registration: It can learn that a particular user and/or terminal
identifier is currently in service and can interact with the SUP-FE
(possibly via the SL-FE) to obtain relevant service profile and
address information
 Service Triggering: Based on an analysis of the session control
messages it can route session control messages to appropriate
Application Support and Service Support functions
 Determination of Routing of session control messages: It can
determine the routing for session control messages based on routing
(location) information

FEs of Service Control Functions
 Proxy Call Session Control (P-CSC)-FE
 acts as the contact point to the user terminal for session-based services
 forward session control requests related to registration to an appropriate I-
 forward session control requests received from the terminal to the S-CSC-
 forwards session control requests or responses to the terminal

 detects and handles emergency session establishment requests.

 maintains a security association between itself and each terminal.

 perform message compression/decompression

 may perform inter-domain topology hiding

 may perform inter-domain protocol repair

 participate in the authorisation of media resources and QoS management

 supports an NAPT Proxy Function (NPF) for network address hiding and
remote NAPT traversal

FEs of Service Control Functions
 Interrogating Call Session Control (I-CSC)-FE
 thecontact point within an operator's network for all service
connections destined to a user of that network operator
 Registration
 Assigning an S-CSC-FE to a user performing SIP registration
 Session-related and session-unrelated flows
 Obtaining from the SUP-FE the address of the currently assigned S-
 Forwarding a SIP request or response to the S-CSC-FE determined by
the above step for incoming sessions.
 Subscription Locator (SL)-FE
 may be queried by the S-CSC-FE, I-CSC-FE, or AS-FE to obtain
the address of the SUP-FE for the required subscriber
 is not required in networks that utilise a single logical SUP-FE
FEs of Service Control Functions
 Service User Profile (SUP)-FE
 storing user profiles, subscriber-related location data, and presence
status data in the Service stratum
 It performs basic data management and maintenance functions
 User profile management functions
 authentication/authorization/service subscription information
 subscriber mobility/location/presence (e.g., online/offline status)

 charging

 It is responsible for responses to queries for user profiles

 It provides access to user data
 It may also be used for support of commonly AAA and security

FEs of Service Control Functions
 Service Authentication and Authorization (SAA)-FE
 provides authentication and authorization in the service stratum
 It ensures that the end-user has valid utilization rights for the
requested service.
 It performs policy control at the service level by using policy rules
contained in a user profile database.
 It works as the first step in the mobility management process and is
used for authentication, authorization, and accounting of
 The result of the authorization function is a yes/no response to a
user connection request

FEs of Service Control Functions
 Interconnection Border Gateway Control (IBGC)-FE
 controls Interconnection Border Gateway Functional Entities (IBG-
FEs) via RACF to interwork with other packet-based networks
 Inter-domain network topology hiding

 Control of IBG-FEs to implement session-based processing (E.g.

media conversion and NA(P)T).
 Inter-domain protocol repair

 Interaction with PD-FE for resource reservation, resource allocation

and/or other resource related information (e.g., the available
resource parameters if the required resources are not available, QoS
label etc.)

FEs of Service Control Functions
 Access Gateway Control (AGC)-FE
 controls one or more AMG-FEs to access PSTN or ISDN users and
handles registration, authentication, and security for the user
 It originates and terminates session control signaling.

 It originates and terminates gateway control flows to control AMG-

 It may initiate and terminate UNI control flows in order to provide
ISDN (supplementary) services.
 It forwards the session control flow to the S-CSC-FE.

 It processes and forwards requests from the AMG-FE to the S-CSC-

 It may process and forward service requests from the AMG-FE to
the AS-FE through the S-CSC-FE
 It supports an NAPT Proxy Function (NPF) for network address
hiding and remote NAPT traversal
FEs of Service Control Functions
 Media Gateway Control (MGC)-FE
 controls the TMG-FE to interwork with PSTN/ISDN
 It processes and forwards requests from the SG-FE to the S-CSC-
FE through the I-CSC-FE
 It may process and forward value-added service requests from
PSTN/ISDN to the AS-FE through the BGC-FE and S-CSC-FE.

 Breakout Gateway Control (BGC)-FE

 selects
the network in which PSTN breakout is to occur and selects
the MGC-FE

FEs of Service Control Functions
 User Signalling Interworking (USIW)-FE
 the interworking and information screening functions for
different types of application signalling at the subscriber side
(access-to-core), which can be located at the border of the access
and core networks for subscriber-side signalling interworking

 Network Signalling Interworking (NSIW)-FE

 the interworking and information screening functions for
different types of application signalling at the trunk side (inter-
operator), which can be located at the border of the core networks
for trunk-side signalling interworking

FEs of Service Control Functions
 Media Resource Control (MRC)-FE
 controls the Media Resource Processing Functional Entity (MRP-
 allocates/assigns MRP-FE resources that are needed for services
such as streaming, announcements, and Interactive Voice Response
(IVR) support

FEs of Service Control Functions
 Media Resource Broker (MRB)-FE
 assigns specific media server resources to incoming calls at the
request of service applications (i.e., an AS)
 acquires knowledge of media server resource utilization that it can
use to help decide which media server resources to assign to
resource requests from applications.
 employs methods/algorithms to determine media server resource
 acquires knowledge of media server resources status related to in-
service and out-of-service status and reservations via an operational
type of reference point

FEs of Service Control Functions
 General Services Control (GSC)-FE
 Itis expected to provide a platform for all envisaged services over
packet-based networks
 GSC-FE acts as a contact point for application support and service
support functional entities, as well as user terminals
 GSC-FE authenticates communications from these, and based on
those communications, the GSC-FE provides information on
session flows and their required QoS characteristics to the PD-FE,
as well as to the IBC-FE when appropriate.
 The GSC-FE maintains session-related state as needed to assist in
policy actions.


and Service Support Functions

Application Support Functions
A-1: AS-FE*


A-U1 A-S1 A-S2 A-S3 A-S4 A-S5 A-S6 A-T1

S-14: MRB-FE S-6: SAA-FE

Service Control

S-15: GSC-FE S-1: S-CSC-FE S-4: SL-FE

End User
S-13: MRC-FE

T-9: SG-FE

Note: * may include Authentication, Authorization, and Accounting

 provides control for services accessed by interacting with
the S-CSC-FE, GSC-FE, or end-user directly
 may reside either in the End-user’s home network or in a
Third Party location
 may comprise the following Functional Entities:
Application Server FE, Application Gateway FE,
Application Service Coordination Manager FE, and Service
Switching Functional Entity
 generate session control requests and dialogs on behalf of

 It executes service logic based on the subscriber’s service profile
and/or on the terminal capability (device profile)
 It acts via four session interaction models with respect to the S-CSC-FE
(terminating user agent/originating user agent/SIP proxy/Third-Party
Call Control)
 It interacts with the AGC-FE through the S-CSC-FE to provide access
to the applications required to support the legacy terminal users
 It interacts with the MRC-FE directly or via the S-CSC-FE in order to
control MRP-FE
 Optionally, it interacts with the MRB-FE in order to attain an MRC-FE
 It interacts with the End-User Functions via UNI to allow the end-users
to securely manage and configure data for their application services.

 Application Support (AS)-FE
 supports generic application server functions including hosting and
executing services
 The examples of AS-FE are call feature application servers,
presence servers, various messaging servers, conferences servers,
home application servers, and so on

 Application Gateway (APL-GW)-FE

 serves as an interworking entity between the Application and the S-
CSC-FE of the Service stratum
 APL-GW-FE provides a secure open interface for the Applications
to use the capabilities and resources of the NGN
 The Applications connected to APL-GW-FE are usually realized by
OSA Application Servers

 Application Service Coordination Manager (APL-
 Manages interactions between multiple application services (or
 The functional entities of ASF&SSF might interwork with each
other via APL-SCM-FE to provide convergent services to the end

 Service Switching Functional Entity (SS)-FE

 Provides access and interworking to a legacy IN SCP
 For the IN services, the S-CSC-FE is connected through SS-FE to
SG-FE to interact with a legacy IN SCP
 It provides IN service switching functions including service trigger
detection, service filtering, call state management, etc and the
protocol adaptation function between INAP and SIP
PSTN/ISDN Emulation Service Component

 PSTN/ISDN emulation provides the emulation of
PSTN/ISDN services for legacy terminal connected via
residential gateways and access gateways to the NGN

 PSTN/ISDN Emulation Architecture

 CallServer based PIEA
 IMS based PIEA

 The two solutions are suitable for different network

situations, but can provide equal emulation services

Call Server-Based PIEA

Call Server-Based PIEA
 Call Control Function (CCF)
 Two party call control function and multi-party call control;
 Access to IN capabilities (e.g. passes events to the SSF);

 Access to PSTN/ISDN supplementary services in SPF;

 Access to applications (e.g. passes events to the SIF for AS-FE)
 Access Gateway Control Function (AGCF)
 controls one or more AMG-FEs to access PSTN or ISDN users
 Media Resource Control Function (MRCF)
 controls MRP-FE and allocates resources which are needed for
services such as streaming, announcements, and Interactive
Voice Response (IVR) support

Call Server-Based PIEA
 Media Gateway Control Function (MGCF)
 controls
the TMG-FE to allow interworking with the
 Routing Function (RF)
 analysis user characteristics (such as called party number,
service profile) and chooses the route to the destination user
 include a routing policy function (such as routing based on
average load sharing or time of the day etc. ), and the routing
 Service Provider Function (SPF)
 provide the PSTN/ISDN supplementary services to user
 also provides the services logic about PSTN/ISDN
supplementary services

Call Server-Based PIEA
 Service Switching Function (SSF)
 provides to access to IN service logic programs hosted in legacy
Service Control Points (SCPs)
 Signaling Interworking Function (SIF)
 isassociated with CCF and performs the function of Protocol

Call Server-Based PIEA

Relationship bet. CS-PIEA and NGN
CS based PES function and
NGN functional entity
functional entity
RF is particular to CS Based
PSTN/ISDN Service component
Legacy Terminal Terminal Functions

IMS-based PIEA
 Legacy terminals and/or legacy access nodes are connected to VoIP
Gateways (VGW) or Access Media Gateways (AMG) using
standard interfaces.
 AMG or VGW connect to the IMS based PES via either the P1
reference point or the Gm reference point.
 The P1 reference point enables an AMG without session control
capabilities to be accommodated in the architecture whilst the Gm
reference point extends IMS session control to a VGW.
 PSTN/ISDN islands may also be connected via trunking media
gateway, controlled using the Mn reference point

IMS-based PIEA

Next Step

NGN Service Components in NGN R2
New Functions in NGN R2
IPTV Architectural Overview
IPTV Service Component
 IPTV Functions
 End-user functions
 Application functions

 Service control functions

 Content delivery functions

 Network functions

 Management functions

 Content provider functions

 Content provider functions

 Itprovides the content and associated metadata to content preparation
functions, which contain content & metadata sources.
IPTV Service Component
 Content delivery functions
 Itperforms cache and storage functionalities and deliver the content
according to the request from the end-user functions.
 Content distribution & location control functions
 Handling interaction with the IPTV service control functional block
 Controlling the distribution of content from the content preparation functions
to the content delivery & storage functions
 Gathering the information regarding content delivery & storage functions
 Performing the selection of a suitable content delivery & storage functions to
serve end-users functions according to some criteria
 Content delivery & storage functions
 It stores, caches, process the content under the control of content preparation
functions and distribute it among instances of content delivery & storage
 It is responsible for delivering content to the content delivery client functions
using the network functions
MMCF Transport Component
MMCF Transport Component
 MMCF: Mobility Management Controk Function
 MMCF describes an architecture of Mobility Management
and Control Functions for the NGN transport stratum,
which includes the definitions of the functional entities of
MMCF and the scenarios for interactions with the other
NGN functional components
 Mobile Location Management Function (MLMF) are used to provide
location registration of the UE
 Handover Control Functions (HCF) are used to provide session
continuity for ongoing sessions of the moving UE
 ITU-T Rec. Y.2011, General principles and general
reference model for Next Generation Networks, 2004.10
 ITU-T Rec. Y.2012, Functional requirements and
architecture of the NGN, 2006. 9
 ITU-T Rec. Y.2021, IMS for Next Generation Networks,
2006. 9
 ITU-T Rec. Y.2031, PSTN/ISDN emulation architecture,
2006. 9
Appendix : ETRI’s BcN Products

Key Result: Open API
Key Result: NCP & QSR Series
Key Result: PON-based FTTH