NGN Architectures

and its Management

Dr. Idir FODIL
Idir.fodil@orange-ftgroup.com
Plan
Introduction

3GPP IP Multimedia Subsystem

TISPAN NGN Architecture

NGN Management

Conclusion
What is NGN ?

The “Converged” Next Generation Network will provide:
 A multi-service, multi-protocol, multi-access, IP based network -
secure, reliable and trusted

Multi-services: delivered by a common QoS enabled core network.

Multi-access: several access networks; fixed and mobile terminals.
 An enabler for Service Providers to offer:

real-time and non real-time communication services

Flexible environment for rapid delivery of new services
 Nomadicity and Mobility

of both users and devices

intra- and inter-Network Domains, eventually fully between Fixed
and Mobile networks

“My communications services” always reachable,

everywhere, using any terminal.
Business drivers for NGN

OPEX cost reduction

Revenue enhancement

Coping with various form of disruptive competition (eg supply of VoIP)

Market saturation of existing services

Rapid / cost reduced supply of new services

Renewal of old networks (e.g. PSTN)

Deployment of single networks for any access networks

NGN Architecture Framework
Source: FGNGN-OD-00097 – NGN
Release 1 scope document
Service stratum
Application Functions

Service
Management Functions

User
Service and Control Profile
Functions Functions

Transport
User
Profile Network
Functions Transport Control Media
Attachment
Functions Handling
Control Functions
Functions Other
Customer Gateway Other
Functions Functions networks
networks
Access
Access
Access Transport Edge Core
CoreTransport
Transport
Functions Transport Functions Functions
Functions
functions functions
UNI NNI
Transport stratum
Control
Media
Plan
Introduction

3GPP IP Multimedia Subsystem

TISPAN NGN Architecture

NGN Management

Conclusion
Mobile Networks History

1G: 1st Mobile Networks: 80's  Analog networks
 Proprietary or national solutions :
 No compatibility
 Very expensive for the user
 Very low penetration

2G: 82: Creation of "Groupe Spéciale Mobile" within the European
Conference of Postal and Telecommunications Administrations (CEPT)
 90-91 : The GSM Phase 1 recommendations are frozen
 92 : First GSM networks in operation
 94 : GSM Phase 2 recommendations publication

2.5G: 1997: GPRS – EDGE

3G: 2000: UMTS

2002: IMS (Release 5)

3G+: 2005: HSDPA-HSUPA

4G: Currently: Toward LTE/SAE

In addition
 UMA/GAN
 I-WLAN
 FemtoCell
Toward IMS

Why IMS ?
 Evolution of Mobile Networks

Use of CS and PS Networks

More Bandwidth

Delivery of data services with voice on CS
 Emergence of multimedia services

Growth and large penetration of Internet

Development of content applications

Competitive voice services like Skype, ..

Access to Internet from different network access
 Mobile Operators

Gain control of the extended value chain, otherwise they will become bandwidth
provider

Keeping ownership of subscribers

Extend revenue and potential profits
 The main advantage of mobile operators

Experience of service delivery

Value added services, not only voice but more …

Quality of services

IMS
 1st step towards all IP Network Architectures
 SIP based multimedia control subsystem independent of network access
 Offer SIP converged and multimedia services
 Single sing-in features for services,
What is IMS?

An enabler for Service Providers to offer:
 real-time and non real-time communication services
 Flexible environment for rapid delivery of new services

Nomadicity and Mobility
 of both users and devices
 intra- and inter-Network Domains, eventually fully between Fixed and
Mobile networks

IMS (IP Multimedia Subsystem) specifications are being developed by 3GPP
(3rd Generation Partnership Program)
 IMS will form a major part of a future NGN (Next Generation Network) environment
(eg“My communications
in ITU-T specifications) services” always reachable,
everywhere, using any terminal on any network access
 IMS is a collection of core network functional entities for the support of SIP (Session
Initiation Protocol) based services.
 IMS builds upon other standards eg IETF – SIP, SDP (Session Description Protocol),
Diameter (user authorization and subscriber service profile access), AAA (Access,
Authorisation and Accounting)
 IMS is being accepted and incorporated into specifications being produced by other
standards bodies – eg 3GPP2, ETSI/TISPAN, OMA.
 IMS Architecture and SIP can be extended to support new services
 Why IMS ?
Fournisseurs
Content Providers
d'Applications

Mobile
Network
IMS Internet

Access Network Application & Services Content

Challenges
• SIP based Multimedia Control platform
• Control all SIP traffic to add value
• Control the complete value chain
• Convergent applications and services
• Extend revenues and benefits
• Single authentication
• Keep ownership of subscribers
• Full IP architecture
Convergence
LTE/SAE
PSTN

UMTS

WLAN GSM

IMS
DSL

CABLE
Réseaux IP

WIMAX
3GPP

3GPP consortium was created in 1998 by :CCSA,
ARIB, ETSI, TTC, TTA, et ATIS

Composed of:
 TSG GERAN GSM EDGE (Radio Access Network)
 TSG RAN new Radio Access Network
 TSG SA Service & System Aspects
 TSG CT Core Network & Terminals

3GPP Standards
 3GPP R99, 3GPP R2000, 3GPP R4, 3GPP R5 (IMS),
3GPP R6, 3GPP R7, et 3GPP R8 (All IP Network)
3GPP

Work closely with OMA, IETF, and ETSI TISPAN
 3GPP is in charge of network architecture and SIP
profiles.

OMA: Open Mobile Alliance
 Development of mobile service enablers (presence,
push to talk, ..)

IETF (Internet Engineering Task Force)
 Development of Internet protocols (routing, SIP, RTP,
Diameter, …)

ETSI TISPAN
 NGN development  Fixed access for IMS, IPTV ..
3GPP specifications
Subject of specification series 3G/GSM R99 and later GSM only (Rel-4 and later) GSM only (before Rel-4)

General information (long defunct) 00 series

Requirements 21 series 41 series 01 series

Service aspects ("stage 1") 22 series 42 series 02 series

Technical realization ("stage 2") 23 series 43 series 03 series

Signalling protocols ("stage 3") -

24 series 44 series 04 series
user equipment to network
Radio aspects 25 series 45 series 05 series

CODECs 26 series 46 series 06 series

Data 27 series 47 series (none exists) 07 series

Signalling protocols ("stage 3") -

28 series 48 series 08 series
(RSS-CN)
Signalling protocols ("stage 3") -
29 series 49 series 09 series
intra-fixed-network
Programme management 30 series 50 series 10 series

Subscriber Identity Module (SIM /

31 series 51 series 11 series
USIM), IC Cards. Test specs.
OAM&P and Charging 32 series 52 series 12 series

Access requirements and test

13 series (1) 13 series (1)
specifications
Security aspects 33 series (2) (2)

UE and (U)SIM test specifications 34 series (2) 11 series

Security algorithms (3) 35 series 55 series (4)

Evolved UTRA aspects 36 series - -

 IMS specifications

Stage 1:
 TS 22.228: Service requirements for the IP multimedia core network subsystem (stage 1)

Stage 2:
 TS 23.002: Network Architecture
 TS 23.003: Numbering, Addressing and Identification
 TS 23.008: Organisation of Subscriber Data
 TS 23.218: IP Multimedia session handling
 TS 23.228: IP Multimedia System (IMS)

Stage 3
 TS 24.228: signalling flows for the IP multimedia call control based on SIP and SDP
 TS 24.229: IP call control based on SIP and SDP
 TS 29.163: Interworking between IMS and CS networks
 Autre: TS 29.208, TS 29.228, TS 29.229 ….

Management et Facturation
 TS 32.225, TS 32.240, TS 32.260, TS 32.295, TS 32.299 ….

Sécurité
 TS 33.102, TS 33.203

RFC IETF utilisé ou référencé

 SIP et SDP: RFC 2327, RFC 3261, RFC 3262, RFC 3263 ………..
 Securité: RFC 3323,
 IMS Architecture
Applications
(proprietary of 3rd party)
Presence, Location, games,
videos, conferencing, IM …

Application Application Application

Server Server Server

SIP session control

HSS
Security IMS
Authentication Heart
Interconnection
CSCFs MRF BGCF

Radio Packet Switched

SGSN GGSN Internet
Access Network
Simplified IMS Architeture
 H.248 SIP Diameter

IP Multimedia Networks
Legacy mobile LCS
CS Network signalling Networks Client

Mm Ma Le
Mb Mb CS AS
BGCF I-CSCF
Sh
CS Mg Mk Cx C, D, LRF
Mk Gc, Gr

Mw
HSS Mm
Mj BGCF Ml
Mi Cx

IMS - MGCF Dx SLF

MGW S -CSCF Dh
Mg Dx
Mn
ISC E -CSCF
Mr
Mb Mw
Mw
P -CSCF Mi
MRFP MRFC
Mx
Mp
Rx Mx Mx BGCF
Mb Mb Mb IBCF
Ici
Gm Ix
TrGW
Izi
UE
Ut
Interface

Iinterface Gm UE P-CSCF

 Registration

Mutual authentication

De-registration initiated by the network
 Session Control

Request and answers forward

Interface Mw CSCF CSCF
 Registration

P-CSCF to I-CSCF, I-CSCF to S-CSCF

De-registration initiated by the network
 Session control

P-CSCF to S-CSCF, S-CSCF to I-CSCF

I-CSCF to S-CSCF, S-CSCF to I-CSCF

Session release by the network

Billing information
Interface

Interface ISC CSCF  AS

 S-CSCF analyze initial requests and send them to AS for
treatment

AS can terminate, redirect, or proxy the request
 AS can generate a request

Interface Cx CSCF  HSS
 Location Management

registration, de-registration

Location information (assigned S-CSCF)
 forward user data to S-CSCF
 Authentication

forward Authentication vector from HSS to S-CSCF
Protocols

Signalisation
 SIP: Session Initiation Protocol

AAA
 Diameter
 HSS access
 Billing
 PDF interaction

Control
 COPS

GGSN Control
 H.248

MGW Control
Protocols

SIP: standard RFC 3261 and others

Extensions requested by 3GPP to IETF
 RFC 3608 : Service Route
 RFC 3320 et RFC 3486: SIP compression
 RFC 3327: Path
 RFC 3455 : P-Headers

P-Headers : private header extensions
 Used for carrying information about traversed networks
 Defined headers

P-Charging-Vector (??)

P-Charging-Function-Addresses

P-Access-Network-Info

P-Visited-Network-ID: identify the home network and used for roaming

P-Called-Party-ID

P-Associated-URI: allow association of a URI to 0 multiple URI
 Contain all implicitly registered identities
Header Path

Have all SIP proxies between SIP terminal
and its registrar.
 All request from the network to the terminal
must go through the proxies (path)

REGISTER REGISTER REGISTER

Supported: Path Path: <sip: Proxy 1> Path: <sip: Proxy 2>,<sip: Proxy 1>

Client Proxy 1 Proxy 2 Registrar / Proxy

INVITE INVITE
INVITE
Route: <sip:Proxy 2>,<sip:Proxy1>
Route:,<sip:Proxy1>
INVITE
Header Service Route

Contain a route that is used by a terminal
for its services
 Applyed only for requests from terminals

REGISTER REGISTER REGISTER

Client Proxy 1 Proxy 2 Registrar / Proxy

200 OK
Service-Route:<sip:P1> <sip: P2> <sip:RP>
200 OK
200 OK
Service- Route: <sip:RP>,
Service-Route:<sip:P1><sip:RP>
Service-Route:<sip:P2><sip:RP>

INVITE INVITE INVITE

Route:<sip:P1>,<sip:P2>,<sip:RP> Route:<sip:P2>,<sip:RP> Route:,<sip:RP>
 Service Logic
AS

User Profiles Session and Service

Control

SIP
I-CSCF
HSS

S-CSCF ISUP
SGW
BGCF

P-CSCF Interconnection
Ressource
MRFC MGCF
Control

TDM
PDF
MRFP MGW

GGSN
P-CSCF (Proxy)

1st IMS point of contact for users

 SIP signaling from and to users go through P-CSCF

Proxy functions specified in RFC 3261

One or more P-CSCF for an operator depending
 Client number, P-CSCF capacities, architecture …

Can act as a user agent
P-CSCF (Proxy)

Functions
 forward SIP REGISTER to le I-CSCF based on domain
name provided by the terminal
 forward SIP requests and answers between S-CSCF and
terminals
 Send billing information
 Compression and decompression of SIP messages
 Detect emergency calls
 Media handling

Verify SDP information

Bandwidth allocation

Maintain session timers

Interact with PDF for policy enforcement
PDF

Act as PDP (policy decision point) for IP

resource control

take decisions for resources allocation

Interact with GGSN for resource
reservation
I-CSCF (Interrogating)

Operator network point of contact for all
sessions toward its users
 Located at domain border

Act as SIP proxy

Interact with HSS in order to have the assigned
S-CSCF for a specific user
 During registration
 During session initiation for non registered users

Forward SIP requests and answers to S-CSCF

Realize network hiding function
S-CSCF

IMS heart
 Located in home network
 Control user registration and sessions
 Realize authentication
 Manage sessions state
 Act as registrar and proxy
 May act as user agent

Functions
 Download user profiles from HSS
 Launch services
 Interact with application servers
 Generate billing information
 Route traffic to P-CSCF for incoming calls
 Route traffic to I-CSCF, AS, BGCF for outcoming calls
 Contain an ENUM client : translate E.164 to SIP URI
 Timers supervision
BGCF

Determine next hop for SIP messages

routing

Used to interconnect IMS users with
CS/PSTN users
 Determine in which PSTN will occur the
interconnection
 Select the appropriate MGCF
MGCF

Communicate with CSCF, BGCF, and CS
network equipments

Determine next hop based on phone
numbers

Realize protocol conversion between
ISUP/TCAP and IMS control protocols

Out band information received by the
MGCF are forwarded to CSCF or MGW
SGW/MGW

SGW: Signaling gateway
 Realize protocol conversion at transport level between SS7
networks (MTP) and IP networks (SCTP)
 Realize low level conversion

ISUP or BICC over SS7 MTP to ISUP or BICC over SCTP/IP

MGW: Media Gateway

 Terminate media flows from CS and PS networks

Media conversion, control, payload treatment
 Interact with MGCF for resource control purposes
IBCF/IWF

IBCF: Interconnection Border Control Function
 Provides application specific functions at the SIP/SDP protocol layer
in order to perform interconnection between two operator domains.
 Interaction with transport resources, through the resource and
admission control subsystem (including NAPT and firewall
functions, IPv6 and IPv4 mapping)
 Insertion of the IWF in the signaling route when appropriate
 Screening of signaling information based on source/destination,
beyond what is already performed inside each of the subsystems
(e.g. by the THIG functionality of the I-CSCF for the IMS core
subsystem).

IWF (Interworking Function)

 Performs the interlocking between protocols used within a service
control subsystems and other IP-based protocols (e.g. between the
SIP profile used in the IMS and other SIP profiles or IP-based
protocols such as the H.323 protocol).
MRFC / MRFP

MRFC: Multimedia Resource Function Controller
 Control the media resource in the MRFP (e.g. Announcements?)
 Interprets information coming from AS and S-CSCF (session ID)
and control MRFP accordingly.
 Generate CDRs

MRFP: Multimedia Resource Function Processor

 Control Bearer on Mb ( MRFPIMS-MGW )
 Mixes incoming media streams (e.g. multiple parties)
 Source Media streams (for multimedia announcements).
 Media Resource Management (e.g. manage access rights to
shared resources in conferencing environment)
Application Servers (AS)

An Application Server (AS) i.e., SIP Application Server,
OSA Application Server, or CAMEL IM-SSF, offers value
added IM services
 Resides either in the user's home network or in a third party
location.
 The OSA Application Server does not directly interact with the
IMS network entities but through the OSA Service Capability
Servers (OSA SCS-s)
 The AS (SIP Application Server and/or the OSA Service
Capability Server and/or IM-SSF) can communicate with the
HSS.

Tasks
 Process and may transform incoming SIP sessions
 Originate SIP sessions
 Generate charging information
Application Server

OSA AS CSE

OSA API CAP

SIP AS OSA SCS IM-SSF

ISC

S-CSCF
Application Servers (AS)

Enabling Services
 Presence,
 Location,
 Group
 Content sharing
…

Applications (on top of enabling services)
 Games,
 Conferences
 Video,
 IM
 ….
HSS: Home Subscriber Server

Master database for a given user.
 Evolution of the HLR (Home Location Register)
 Entity containing the subscription-related information to
support the network entities actually handling calls/sessions.
 Subscription Related information

User Identities, Registration information (assigned S-CSCF), Access parameters
(authentication, roaming, ..) and service data

Home Network may contain one or several HSS,
 It depends on the number of mobile subscribers, on the
capacity of the equipment and on the organisation of the
network.

SLF (Subscription Locator Function)
 Resolution server used to find the HSS responsible of a given
subscriber.
HSS : Fonctions Logiques
HSS
M o b ility M a n a g e m e n t Id e n tific a tio n h a n d lin g

U s e r se c u rity in fo . g e n e ra tio n S e rvic e a u th o riza tio n s u p p o rt

U s e r se c u rity s u p p o rt A c c e s s a u th o riza tio n

S e rvic e P ro vis io n in g s u p p o rt A p p lic a tio n S e rvic e s S u p p o rt

C a ll / S e s s io n e sta b lish m e n t su p p o rt C A M E L S e rvic e s S u p p o rt

G U P D a ta R e p o s ito ry

Wx C D Gr Gc Rp Sh Si Cx

gsm SCF S IP
A p p lic a tio n
S er ve r

G MSC M SC / VLR SGSN GGSN OSA SCS IM -S S F CSCF

C S D o m a in P S D o m a in IM C N s u b s ys te m

3 G P P A A A S e rve r A p p lic a tio n s G U P S e rve r

HSS

Data
 User Identities

Private and Public Identities
 Registration Information

Assigned S-CSCF
 Access parameters

Authentication, roaming
 Services (filtering criteria …)

If multiple HSS are deployed, a SLF is used by
the I-CSCF/AS to get the right HSS
Identities

Definitions
 The private identity is assigned by the home network
operator, and used, for example, for Registration,
Authorization, Administration, and Accounting
purposes. This identity shall take the form of a
Network Access Identifier (NAI) as defined in
IETF RFC 2486

 The Public User Identity/identities are used by any

user for requesting communications to other users.
For example, this might be included on a business
card.
Identities
Public
User Identity
Service
Profile

IMS Private Public

Subscription User Identity User Identity

Public Service
User Identity Profile

Public User Service

Identity-1 Profile-1
Private User
Identity-1

IMS Public User

Subscription Identity-2
Service
Private User Profile-2
Identity-2
Public User
Identity-3
Private User Identity (IMPI)

Network access identifier

Permanently allocated to a user and stored in
ISIM.

Valid during home network subscription

Used in all registration requests

Stored in the HSS
 Format: username@realm
 Ex: user@domaine.fr

Identify a subscription and not a user.
Public User Identity (IMPU)

A user can have one or multiple IMPU

Used for communication with other users

Take the form of:
 TelURI: tel: +33 -14526 – 9854
 SIP URI : sip:usert@domaine.fr

We can register all identities by using a single

registration
 Implicit registration sets
Exemple

sip: alain@domaine.Fr
Profile Service
Université
Tel:+3312365236

user@domaine.fr
sip: alain@domaine.Fr
Profile Service
Maison
Tel:+3362365236
Domain Concept

Definitions
 Home network: operator network
 Visited Network: roaming scenario

IMS
 S-CSCF always located in home network
 P-CSCF can be the one of the visited network
 Two roaming types

IMS , GPRS
Roaming

GPRS Roaming

RAN Cœur PS GGSN P-CSCF IMS

IP Connectivity
Visited Network Home
Réseau
Network
Home

IMS Roaming

RAN Cœur PS GGSN P-CSCF IMS

IP Connectivity
Visited Network Home Network
 Registration – Phase 1
CLIENT SGSN GGSN

Attachement
GPRS Attachement
GPRS

Activate PDP Context Request

Create PDP Context Request

Activate PDP Context Response

Create PDP Context Response
(@ P-CSCF optionnel)

P-CSCF discovery
• PDP Context Activation Procedure
• Using DHCP and if necessary DNS
P-CSCF Discovery
CLIENT
GGSN
Serveur DHCP Serveur DNS

DHCP Request
Option : SIP Domain Name List
Option: Recursive DNS Server

DHCP Answer

DNS Request

DNS Answer
 Registration – Phase 2
IMS UE P-CSCF I-CSCF HSS S-CSCF
REGISTER
REGISTER
UAR
UAA
REGISTER

MAR
MAA

401. Unauthorized 401. Unauthorized

401. Unauthorized

REGISTER
REGISTER
UAR
UAA
REGISTER
SAR
SAA
200 OK 200 OK
200 OK
Registration – Phase 2

P-CSCF
 Determine the I-CSCF by using the DNS
 Add the headers: Path, P-Visited-Network-ID

I-CSCF
 Does not keep any state about the registration
 Play a load balancer function
 In the UAR (user authentication request), add: IMPI, IMPU, and
P-Visited-Network-ID

HSS
 Check the identities, and roaming
 Check if a S-CSCF is assigned or send a list of possible S-CSCF
Registration – Phase 2

S-CSCF
 Download user authentication data
 Challenge the user using SIP 401 message

User
 Establishan IPSEC association with P-CSCF
 Send a new REGISTER

S-CSCF
 Authentication
validation
 Download User Profile
 Send SIP 200 OK message containing

P-Associated-URI

Service-Route
 IMS Session
Home
Home
DNS

183
LIR/LAR
HSS

INVITE I-CSCF 183

INVITE S-CSCF

INVITE
183
PRACK

S-CSCF
P-CSCF PRACK

INVITE
183 183 PRACK
INVITE PRACK
183

P-CSCF INVITE

"A" "B"
PRACK
Visited
Visited
 IMS Session

UE "A" P-CSCF S-CSCF I-CSCF HSS S-CSCF P-CSCF UE "B"

INVITE
100 Trying INVITE
100 Trying

Evaluation of IFC

INVITE
100 Trying LIR
LAR

INVITE
100 Trying

Evaluation of IFC

INVITE
100 Trying
INVITE
100 Trying

Session Progress
Session Progress
Session Progress 183
Session Progress 183
183
Session Progress 183
Session Progress 183
183
 IMS Session
UE "A"
P-CSCF I-CSCF HSS P-CSCF UE "B"
S-CSCF
S-CSCF
PRACK
PRACK PRACK
PRACK PRACK

200 OK
200 OK
200 OK
200 OK
200 OK
180
180
180 Ringing Ringing
180 Ringing
180 Ringing
Ringing

PRACK
PRACK
PRACK PRACK
PRACK

200 OK
200 OK
200 OK
200 OK
200 OK 200 OK
200 OK
200 OK
200 OK
200 OK

ACK ACK
ACK ACK
ACK

PLAN MEDIA
 IMS Session
UE "A" P-CSCF I-CSCF HSS P-CSCF
UE "B"
S-CSCF S-CSCF
BYE
BYE
BYE BYE

BYE

200 OK
200 OK

200 OK
200 OK

200 OK
Plan
Introduction

3GPP IP Multimedia Subsystem

TISPAN NGN Architecture

NGN Management

Conclusion
ITU-T, ETSI, 3GPP architectures

ITU-T
Architectural Framework for NGN

3GPP
DSL Architecture
IMS Architecture

ETSI TISPAN
NGN Architecture
TISPAN and ITU-T architecture relationship

Both architectures comply with the principles

defined in Recommendation Y.2011 (w.r.t
transport/service functional split).

The ITU architecture Y.2012 (FGNGN-FRA)

should be considered as a generic architectural
framework while the ETSI TISPAN NGN
functional architecture should be viewed as a
particular – subsystem oriented - realisation of
this framework.
ETSI TISPAN NGN Architecture Design

Consistent with the ITU-T framework

A sub-system oriented approach, enabling:

 The addition of new subsystems over the time
 To import (and adapt) subsystems from other standardisation
bodies.
 Flexibility to adjust a subsystem architecture with almost no
impact on others.

IP connectivity is provided using two subsystems over IP

transport resources (DSL access & aggregation + IP
backbone):
 NASS: Network Attachment Subsystem
 RACS: Resource and Admission Control Subsystem
TISPAN NGN Architecture (ES 282 001)

Applications

Other
Service Layer User subsystems
profiles
Core IMS

PSTN/ISDN

Other networks
Emulation
User Equipment

subsystem

Network
Attachment
Subsystem Resource and
Admission Control
Subsystem

Transport Layer

Transfer Functions
Customer Premises Equipment

The Customer Premises Equipment may be in the form of

a single SIP Device (IP Phone, Soft Phone …) behind a DSL
modem

a Home Gateway (HGW) connecting several SIP Devices
and/Analog Terminals.

The HGW may include NAT functions (also known as
Hosted NAT)

DSL Modem
GW

Routeur
With NAPT/FW
IP-Connectivity in Fixed Broadband Access (DSL)

Transport Functions are provided by a DSL segment (1)

and an aggregation (2) segment. The aggregation
segment is typically based on ATM or Giga Ethernet.

Control Functions are provided by the Network

Attachment Subsystem (NASS) and the Resource and
Admission Control Subsystem (RACS)
(1) (2)

IP

DSLAM B-RAS

Aggregation Segment
TISPAN NGN Architecture (ES 282 001)
Applications

Other
Service Layer User subsystems
profiles
Core IMS

PSTN/ISDN

Other networks
Emulation
User Equipment

subsystem

Network
Attachment
Subsystem Resource and
Admission Control
Subsystem

Transport Layer

Transfer Functions
Network Attachment Subsystem (NASS)

Dynamic provision of IP address and other user equipment
configuration parameters (e.g. using DHCP).

User authentication, prior or during the IP address
allocation procedure.

Authorization of network access based on user network
profile (e.g. subscribed bandwidth capacity).

Access network configuration (default firewall setting),
based on user profile.

Location management (e.g. for emergency call, …).

CPE configuration.
NASS Architecture
Mapping
AF
@IP, Location, Line-Id,
Subscriber-Id
e2 Services

Control Subsystem (RACS)

@IP allocation

Resource and Admission

(e.g. DHCP server)
e4
CPE configuration NASS
CLF

CNGCF NACF UAAF PDBF

AMF

Access Profile

IP ARF Core transport Authentication

Access Transport Network Authorisation
Network
Access IP Edge Core Border
Node Node Node
NASS Roaming
Home Network
The NASS is distributed between the
visited and the home network UAAF PDBF

NASS
NASS CLF
e5

Visited Network

NACF P-UAAF
CNGCF
Proxy UAAF
AMF

IP ARF Core transport

Access Transport Network
Network
Access IP Edge Core Border
Node Node Node
TISPAN NGN Architecture (ES 282 001)
Applications

Other
Service Layer User subsystems
profiles
Core IMS

PSTN/ISDN

Other networks
Emulation
User Equipment

subsystem

Network
Attachment
Subsystem Resource and
Admission Control
Subsystem

Transport Layer

Transfer Functions
Resource and Admission Control Subsystem (RACS)

Authorisation of resource reservation requests

Admission Control to access network resources

 based on user access profiles and the knowledge of
transport resource availability.

NAPT/ Gate Control: controls near-end and far-

end NAPT and FW functions
 Atthe border between core and access networks
 Between two core TISPAN NGN networks
RACS Architecture
Network Attachment P-CSCF
Subsystem IMS
CLF
Gq'

e
4 (Transport)
Access Profile RACS
SPDF Resource Request
Download
Rq

Admission A-RACF
Control
Gate Control
(incl. NAPT
control)
Re Ia

ARF RCEF BGF

IP
L2TF
Aggregation Core transport
Access Network Network
IP Edge Core Border
Node Node Node
TISPAN NGN Architecture (ES 282 001)
Applications

Other
Service Layer User subsystems
profiles
Core IMS

PSTN/ISDN

Other networks
Emulation
User Equipment

subsystem

Network
Attachment
Subsystem Resource and
Admission Control
Subsystem

Transport Layer

Transfer Functions
 Emulation / Simulation accesses

Analogue access
over voice DSLAM
Emulated
AGW Z
Analogue access
access
over Residential
NGN GateWay
IP access over
RGW Residential
SIP GateWay
H323
Simulated
IP access
access

• Emulation key Scenarios

• PSTN/ISDN Replacement (in whole or in part)
• Support of legacy terminal equipment connected directly or indirectly to NGN
• Simulation
• Provision of services similar to the PSTN/ISDN to voice and other multimedia
terminal equipment
PSTN/ISDN Emulation Subsystem (PES)

PSTN/ISDN Emulation = Provision of PSTN/ISDN
services to legacy terminals connected through a
gateway.

Two competing approaches:

 Softswitch-like approach
 IMS-based approach (TS 182 012)

IMS-Based approach: Avoid a dedicated infrastructure for

supporting PSTN Emulation
 In the mid/long term, Emulation-based configurations are
likely to be substituted by Simulation-based configurations.
IMS-based Emulation Architecture principles

Application Servers

S-CSCF IBCF
P-CSCF
SIP I-CSCF
Home Gateway
AGCF MGCF
Z BGCF
IMS-based PES
H.248

Z
DSLAM/AGW
 IMS and PES merging AS
DIAMETER … "Class 5" logic
IBCF/IWF
UPSF
SIP
NASS
I-CSCF
P-CSCF
S-CSCF
MGCF

Other IP Networks
Service
independent MRFC
logic
IMS
H.248 AGC
F PSTN

Z
RACS MRFP
MGW
Z
GW
W
IP BG
Gate IP Backbone
B-RAS NAPT
DSLAM
AGCF main functions

Act as an MGC for controlling media gateways functions
located in residential and access gateways.

Perform signalling interworking between SIP and analog
signalling (through H.248 signals and events).

Manage SIP registration procedures on behalf of legacy
terminals connected behind the media gateways.

Provide basic feature logic for
 Determining end of dialling;
 Selecting a dial tone
 Processing mid call events (i.e. flash-hook), collecting digits
and mapping received digits to appropriate SIP & H.248
commands.
TISPAN overall architecture (DSL
case) Based on
3GPP IMS

IP Connectivity
Applications
Access Network
And related functionality

User Other Multimedia

Profiles Components …

Streaming Services
(RTSP based)

PSTN / ISDN Emulation

(SIP-I based)

Other Networks
IP Multimedia
Component (Core IMS)
(SIP based)
IBCF

PSTN/ISDN
Network Attachment Resource and Admission
Functionality Control Functionality RACS
R-MGF NASS RACS

RGW A-MGF T-MGF

TGW
RCEF C-BGF
IP ARF Core transport
L2TF I-BGF
Access Transport Network
Network
Access IP Edge Core Border BGW
Node Node Node
Plan
Introduction

3GPP IP Multimedia Subsystem

TISPAN NGN Architecture

NGN Management

Conclusion
 NGN Environment to be Managed

Based on Packet-based transfer

Common control functions supporting a wide range of applications –
via session services

Support for complex value chains, multiple trading partners /
business models (eg B2B interactions)

Support for a wide range of services, applications and mechanisms,
[including real time/ streaming/ non-real time and multimedia services]

Broadband capabilities with end-to-end QoS (Quality of Service)

Inter-working with legacy networks via open interfaces

Generalized mobility, with converged services between fixed/mobile

Personalization of Services in a component-oriented environment

Variety of customer identification schemes (eg Role-based access)

Independence of service-related functions from underlying transport

Compliant with all Legal and regulatory requirements
[Emergency communications, security, privacy, lawful interception, etc.]
NGN OSS Architecture – Characteristics
To fulfill the NGN business and technical vision, design of the OSS
architecture must have the following characteristics:

All systems must embrace a similar component-based, service-

oriented architecture “SOA” – defined in a technology neutral form

Utilise a common information architecture across all management

applications so that :

information can be shared across multiple areas of Management

capabilities can be developed for collecting end-to-end service
measurement data (eg for SLA support).

framework provided for policy-based management for existing or yet to
be defined services.

OSS solutions must be developed according to a common business

process framework

Network Technologies managed in a common way, Services

Managed independently of the Network technologies
TISPAN NGN Management Architecture
Focus on enhancing TMN for NGN
needs.
More Network Centric
OAM for 3GPP Networks ( Include
IMS). More OSS Focus ( eTOM, SID, TNA)
Focus is on Network Level
OSS  Network : MTOSI, MTNM, ..
Integration Reference Points
(IRPs)

ITU-T SG4/Q8 3GPP SA5 TMF

ETSI TISPAN
OASIS SOA WG8

Service Oriented Architecture (SOA)

framework. Web Services application
ETSI TISPAN NGN OSS Architecture
Source: ETSI TS 188 001 - (TISPAN)
OSS Architecture Release 1

Infrastructure Services
MP&CM

Market, Product & Customer

Market, Product & Customer
Service
Management
Interface
Management Function
Group(s)
Function Set(s )
Set(s
Set

Service Management

Supplier/ Partner Management

Basic Framework Services
Service Interface Group(s)

B2B
Service Management Connectivity

Service Interface Group(s)

Service Management
Service
Function
Interface
Set(sGroup(s)
)Management
Function Set

Resource Management

Resource Management
Service Interface
Function Group(s)
Set(s )
Service Resource Transport Resource
Service Resource Transport Resource
Management Management
Management
Function Set(s ) Management
Function Set(s )

Managed Resources

Managed NGN Service Resources Managed NGN Transport Resources

TISPAN NGN OSS Architecture – Implementation

NGN OSS Business NGN OSS Business

Service 1
... Service n

Common Communication Vehicle

NGN OSS Basic NGN OSS Basic

Framework ... Framework
Service 1 Service m

Legend:
NGN OSS Service
NGN OSS Service Interface
NGN OSS Service Interface Consumer
Issues in Management of NGN

Control V Management
 Example: IMS Control Functions and their associated
Management needs (Eg - Fulfilment, Assurance,
Billing)

Service Creation V Management

 Example: Service Delivery Framework (SDF) and its
associated Management needs (Eg - Fulfilment,
Assurance, Billing)
Subscription Management

The management of Subscriber and User

Information

Original concept started in 3GPP SA5

Extended by TISPAN WG8 to
Fixed Mobile Convergance
Subscription Management (SuM) - 3GPP viewpoint

Customer
Care Center

User / Subscription
Subscriber Profile

32.140 Subscription Management Requirements

SuM Mapped to TMN Layers

Service Subscription
Operations Management
Management

Network
Operations
Management

Network Domains

Process Subscription Profile Component SuM Systems

32.140 Subscription Management Requirements

3GPP SuM related to HSS
32.140
Application User
Account/Profile Subscription Management
To Network API To B2B Trading Requirements
Features Partners

Service Operations Management

SOM

Subscription
Management Other
Customer Feature Features Application Service
Care Operations Eg. GTTD, SMS Centre,
Presence

Application User
Account/Profile

AuC
HSS

Subscription Location
NPDB
information information

VLR
EIR

MSC Server GMSC Server SGSN GGSN CSCF gsmCSF

CSCF
CS Domain PS Domain IMS CAMEL
Difference between 3GPP and TISPAN SuM
Requirements

3GPP

All (Subscription) Service Profile
Information ultimately held in Home HSS

Distributed by signalling to VHSS

Each user equated to a SIM /UICC
Difference between 3GPP and TISPAN SuM
Requirements
TISPAN

Providers of Access and Service can be different

Hence HSS functionality split between
 IMS (User Profile Service functions –UPSF)
 NASS (Profile Data Base Function – PDBF)

Configuration of the E2E service requires
 Transactional and referential integrity between UPSF and PDBF
 Synchronisation of UPSF/ PDBF with providers OSS (Service
Mngt)
 Ability to synchronise SP SuM Profiles across B2B interfaces

Broadband access means on one access line
 multiple terminals
 multiple Users
 multiple Customers

Distinguish between Customer, Subscriber and User

Different/No Authentication -No equivalent of SIM/UICC
TISPAN Subscription Management (SuM)
Service Provider Service Delivery
Subscribe

Subscriber Auto Configure

Customer Care

Subscription Other Actions/

Management Operations
Give Rights

Network
Use Services
Functionalities/Nodes
Users (AS, CPE, UPSF, ..etc)
TISPAN SuM Use Cases Original
ude Manage "Offered Services"
Incl

Manage Subscription

Service
Provider Inclu
d e Manage "Subscribed Services"

Manage
User

Include

Manage Users
Manage "User Assigned Services" Manage NGN SuM Data
Include

Subscriber TISPAN NGN

Functions

Include

Manage
Subscriber

Manage "User Customized &

Activated Services"

User
TISPAN SuM Use Cases
Manage
Manage “Offered
“Offered
Services”
Services”

<<include>>
<<include>>

Manage
Manage Subscription
Subscription <<include>>
<<include>> Manage
Manage User
User
Service
Service Manage
Manage Offered
Offered
Provider
Provider “ServicesSubscription”
“ServicesSubscription”
<<include>>
<<include>>

Manage
Manage Users
Users <<include>>
<<include>>
Manage
Manage NGN
NGN SuM
SuM Data
Data
Subscriber
Subscriber Manage
Manage “User
“User
Assigned
Assigned Services”
Services”
<<include>>
<<include>>
TISPAN
TISPAN
NGN
NGN
Functions
Manage
Manage Manage
Manage Functions
“User
“User Customerized
Customerized && Subscriber
Activated
Subscriber
User
Activated Services”
Services”
User
TISPAN SuM eTOM processes
Operations
Operations Support & Readiness
Fulfillment
Customer Relationship
Order
Management Handling

Service Management & Operations

A
Service
Managem ent &
Operations
C Service
Configuration
Readiness & Activation

Resource Management & Operations B

Resource Provisioning
Resource
Management &
Operations
D
Readiness

NGN Network
(A): Ordering Specific Subscription Activation (C): Checking Service Availability within Service Catalogue
(B): Ordering Resource Configuration (D): Checking Resource Availability
 TISPAN SuM High Level Information Model
Subscriber

1..1
0..*
1..* 0..*

Subscription User

• Subscription Identitfier • User Identity

1..1 1..1 1..1

1..1 1..1

1..* 1..* 0..* 0..* 0..*

Subscribed NGN Subscribed Network User NGN Network

Service User NGN Service Profile Credentials
Access Access Profile
• User NGN Service
• NGN Service Identifier • Network Access Identifier Profile Identifier • Private User Identity
• NASS User ID
• Network Access Type • Reference location • Authentication Data
• UAAF ID
• Registration Status • Authentication Schema
• Bandwidth capacity per service
1..1 • Subscribed Quality of Service
1..1 1..1 1..1

0..*

1..* 1..* 1..1

1..* 1..*

Logical Access Physical Access Sub Profile User Service Instance

• Logical Access ID • Sub Profile ID • NGN Service Identifier

• Physical Access ID
• RACS Point of Contact • Set of Logical Access ID • Service state
• Network Access • Service options
1..* authentication data • Service data
• Set of QoS profile info
1..1 • Initial gate settings
• Privacy indicator
Location

• Location Information
TISPAN SuM Diagram Key
candidate management entity

entity out of scope of current specification

candidate relationship amongst entities

0..* cardinality of a relationship

. text candidate management entity with associated

attributes
. text
IMS User NGN Service Profile
User NGN Service Profile

• NGN Service Profile Identifier

• Reference location
• Bandwidth capacity per service
• Subscribed Quality of Service

IMS Service Profile Other type of Service Profile

• Public User Identities

• Registration Status
• Initial Filter Criteria
• Application Server Information
• Service Indication
• Attribute 1
• Barring Indication
• Attribute 2
• List of Authorized visited Network Identifier
• ……………
• Services related to unregistered state
• ……………..
• Implicitly registered public user identity sets
• Shared IFC Set Identifier
• Default Public User Identity Indicator
• Subscribed Media Profile Identifier
• Network handling
 Evolved 3GPP-TISPAN SuM Information Model
<<InformationObjectClass>> <<InformationObjectClass>>
<<InformationObjectClass>> +equipmentUser +theEquipment
SuMServiceProfile <<names>> SuMEquipment
SuMUser
0..n relatedEquipment
0..n 1 suMEquipmentList : CM 0..n

<<InformationObjectClass>> <<InformationObjectClass>> <<InformationObjectClass>> <<InformationObjectClass>>

IMSServiceProfile SuMUserProfile SuMSubscriptionProfile MobileUserData
barringIndication : CM userLabel iMSI iMSI
etc mSISDN mSISDN
1 multinumberingMSISDNs multinumberingMSISDNs
iMEISV iMEISV
1 0..n +theIMSServiceProfile privateUserIdentity
publicIdentity
relatedIMSServiceProfile <<names>>
<<names>>
0..n
+iMSServiceProfileUser 0..n

0..n <<InformationObjectClass>>
SuMCredentials
<<InformationObjectClass>> iMSServiceProfileList
IMSPublicIdentification iMSPrivateUserIdentity
publicUserIdentity
barringIndication
TM Forum SDF Program Objectives: Business Perspective

From business perspective the SDF should allow the

stakeholders to:
 Reduce cost and cycle time to translate ideas to market
offerings

e.g. effective product lifecycle management throughout the entire
ecosystem including operation support
 Increase opportunities and innovations for monetizing existing
assets

e.g. repurposing content and applications;
 Adapt swiftly to market changes and customer preferences
 Support many different type of business models

e.g. allow the choices of being an infrastructure provider, a service
wholesaler or a product retailer among different offerings
 Participate effectively in value networks
TM Forum SDF Program Objectives: Technical Requirements

These business objectives translate to the

following technical requirements that the SDF
must to satisfy:
 Endorse a component-based architecture
 All
components within the SDF must comply to a
common management framework
 Consistent service lifecycle operations support
within and across the value network.
 Standardizedmetadata for cataloging and lifecycle
management of Products, Services & Resources
 SDF Lifecycle Operations Support
C ustom er

S trateg y, In frastru cture & Pro du ct O peration s

S trateg y & Infrastru ctu re Pro du ct O peratio ns F ulfillm en t A ssu ran ce B illing
C om m it Lifecycle Lifecycle Su pp ort &
M an ag em ent M an ag em ent R ead in ess
SDF
M arketin g & O ffer M an ag em ent C ustom er R elatio nsh ip M an ag em ent
Service
Strategy
Service D evelo p m en t & M an agem en t S ervice M anagem en t & O peratio ns

SDF SDF
SDF Service
Service Service
R eso urce D evelop m ent & M anag em ent R esou rce MDeployment
an ag em ent & O p eration s
Creation
(A pplication, C om puting and N etw ork)
Operations
(A pplication, C om puting and N etw ork)

Su pp ly C h ain D evelop m en t & M an agem en t S up plier/Partn er R elation sh ip M anagem en t

En terp rise M an agem en t

Strateg ic & E nterprise En terp rise R isk E nterprise Effectiven ess K now ledg e & R esearch
Plan ning M anag em en t M an agem ent M anagem ent
SOA Integration Infrastructure
Financial & A sset S takeh old er & Extern al H um an Resources
SDF Serviceable
R esources to
Execution
M an agem ent R elatio ns M anagem en t expose capabilities
M an agem ent

eTOM
SOA does not
Integration cover
Infrastructure
service execution time
Abstraction
concerns Resources of NGNarchitecture
 A closer look at the SDF building blocks
SDF Managed Resources
Customer

Strategy, Infrastructure & Product Operations

Resources able to
Strategy & Infrastructure Product Operations Fulfillment Assurance Billing
expose capabilities
Commit Lifecycle Lifecycle Support &
Management Management Readiness
Infrastructure for the Application Layer
Marketing & Offer Management Customer Relationship Management
e.g. Middleware, OS and Hardware
SDF Management
Service Development & Management Service Management & Operations

Physical IT
Application Layer
resources
Resource Development & Management Resource Management & Operations
(Application, Computing and Network) (Application, Computing and Network)

Capability Exposure & 3-rd party

Supply Chain Development & Management Supplier/Partner Relationship Management
Integration
Service Applications & Enablers
Enterprise Management Logical IT
Strategic & Enterprise Enterprise Risk Enterprise Effectiveness Knowledge & Research resources Network Abstraction
Planning Management Management Management

Financial & Asset Stakeholder & External Human Resources

Management Relations Management Management

Signaling & Control Layer

Network
Service Delivery resources
Framework
Transport & Aggregation Layer

NGN Resources
SDF Reference Model – Level 0
Customer, Suppliers, Partner Services

Integration Infrastructure
SDF managed resources

Service Lifecycle Service

Operation Support Enabler
& Application

SDF
Management
BSS/OSS Network & IT Resources

End-user Services
SDF service components expose
standardized service & management interfaces

Customer, Suppliers, Partner Services

Integration Infrastructure
SDF managed resources
Service Lifecycle Service Enablers &
Operation Support Applications

Find
Bind
Execute
<<Lifecycle SDF Service <<Consumer>>
Catalogs Management>>

Service
Publish Component Registry/
Subscribe Repository
Metadata
SDF
Management
BSS/OSS Network & IT Resources

End-user Services
What is TMF’s NGOSS?

New Generation Operations Systems and
Software

Major part of TMF’s technical work programme

Has been developed over the past 5 years to

support Management of NGN

Consists of a framework of Architectures and

associated Specifications
 TM Forum Collaboration Program
Thought Leadership/Strategy

OpenOSS, Collaboration Workspace, www, Web Comminities

Drive NGN-M SPLC IGAC TPC
Strategy

ITU-T, ETSI, 3GPP, DMTF, OSS/J,IPDR, Etc Etc

Business Tools
eTOM
Create SLA Management

Industry Groups Liaison

Business Telecom Application Map Benchmarking

Collaboration Tools
Guidelines
Revenue Assurance SID SOX Procurement Guidelines

NGOSS
NGOSS Developers Tools NGOSS
Business Compliant
Requirements Interfaces
Defining Requirements
TNA TAM Using NGOSS to build
eTOM SID
Develop for NGOSS-based Technology Telecoms standard software
Process Information
Software Development Neutral Applications interfaces
Model Model
Architecture Map • mTOP:
•SLA Handbook
MTOSI
•Revenue Assurance
Lifecycle and Methodology MTNM
•Business Process
Management
• OSS/J
Compliance

Demo.
Solutions Catalyst Program
NGOSS Next Generation
Operations Systems and Software
NGOSS

NGOSS Developers Tools 6

NGOSS
Business Compliant
Requirements 1 2 3 4 Interfaces
Defining Requirements eTOM TNA Using NGOSS to build
SID TAM
for NGOSS-based Business Information Technology Telecoms standard software
Development Neutral Interfaces
Process Model Architecture Applications
Model Map
•SLA Handbook
•Revenue Assurance • mTOP:
MTOSI
•Business Process 5 Lifecycle and Methodology
MTNM
Management
Compliance • OSS/J
 NGOSS Next Generation
Operations Systems and Software

NGOSS

NGOSS Developers Tools 6

NGOSS
Compliant
1 2 3 4 Interfaces
Business Using NGOSS to build
Requirements eTOM TNA standard software
Business SID Technology TAM Interfaces
Defining Requirements
for NGOSS-based Process Information Neutral Telecoms
Development
Model Model Architecture Applications • mTOP:
Map
•SLA Handbook MTOSI
•Revenue Assurance
•Business Process MTNM
Management
5 Lifecycle and Methodology • OSS/J

Compliance
eTOM: the Big Picture (Level 0 to 1)
Customer

Strategy, Infrastructure & Product Operations

Strategy & Infrastructure Product Operations Fulfillment Assurance Billing

Commit Lifecycle Lifecycle Support &
Management Management Readiness
Marketing & Offer Management Customer Relationship Management

Service Development & Management Service Management & Operations

Resource Development & Management Resource Management & Operations

(Application, Computing and Network) (Application, Computing and Network)

Supply Chain Development & Management Supplier/Partner Relationship Management

Enterprise Management
Strategic & Enterprise Enterprise Risk Enterprise Effectiveness Knowledge & Research
Planning Management Management Management

Financial & Asset Stakeholder & External Human Resources

Management Relations Management Management
 Level 1 Horizontal Grouping
eTOM - The Level 2 Processes
External Entity
Level 1 Vertical Grouping Level 2 Process Element

Customer
Strategy, Infrastructure & Product Operations
Strategy & Commit Infrastructure Lifecycle Product Lifecycle Operations Support
Management & Readiness
Fulfillment Assurance Billing
Management
Marketing & Offer Management Customer Relationship Customer Interface Management
Management
Product & Offer Product & Offer Marketing Product Marketing Selling
Market
Business Portfolio Capability Development Communications
Strategy & CRM Customer Billing &
Planning & Capability Delivery & Retirement & Promotion Problem
Policy Support & Marketing QoS / SLA Collections
Commitment Delivery Order Handling
Readiness Fulfillment Management Management
Handling
Response
Product & Offer CRM Sales & Channel
Portfolio Strategy, Capability Development
Delivery Retention & Loyalty
Policy & Planning

Service Management & Operations

Service Development & Management
Service Service Service Quality Service &
SM&O
Service Service Service & Service Configuration Problem Management Specific Instance
Support &
Strategy & Planning & Operations Development & & Activation Management Rating
Readiness
Policy Commitment Capability Retirement
Delivery

Resource Management & Operations Resource Resource

Resource Development & Management Trouble Performance
RM&O Management Management
Resource
Resource & Resource & Resource & Support &
Provisioning
Resource Readiness
Technology Technology Operations Resource Data Collection & Processing
Development
Strategy & Policy Plan & Commitment Capability
Delivery

Supplier/Partner Relationship Management

Supply Chain Development & Management S/P S/P Purchase S/P Problem S/P S/P Settlements
S/PRM Buying Order Reporting & Performance & Billing
Support & Management Management Management Management
Supply Chain Supply Chain Supply Chain
Supply Chain Development Readiness
Planning Capability
Strategy & Policy & Change
& Commitment Availability Supplier/Partner Interface Management
Management

Enterprise Management

Strategic & Enterprise Planning Brand Management, Market Research & Advertising Enterprise Quality Mgmt, Process & IT Planning & Arch. Research & Development & Technology
Process Arch. Info Systems
Strategic &
Business
Enterprise Group Brand
Market
Advertising
Enterprise
Management Strategy & Knowledge Research & Technology Acquisition
Business Architecture Enterprise Management Research & Quality
Planning Development Management Analysis & Support Planning Management Development Acquisition
Planning Management

Financial & Asset Management Stakeholder & External Relations Management Human Resources Management Disaster Recovery, Security & Fraud Management
PR & Comm. Shareholder Employee Disaster Recovery
Financial Real Estate Procurement Regulatory Legal HR Policies Workforce Workforce & Contingency Security Fraud
Relations Relations & Labor
Management Management Management Management Management & Practices Strategy Development Planning Management Management
Management Management Relations
The SID Business Framework (GB922)
Market / Sales
Market Strategy & Plan Marketing Campaign Contact/Lead/Prospect

Market Segment Competitor Sales Statistic Sales Channel

ABEs
Product
Strategic Product
Product Portfolio Plan Product Performance

Product Specification Product Offering Product Usage Statistic

Customer
Applied Customer Billing
Customer Customer Order Customer Problem Customer Bill Collection
Rate

Customer Interaction Customer Statistic Customer SLA Customer Bill Customer Bill Inquiry

Service
Service Service Applications Service Performance Service Strategy & Plan

Service Specification Service Configuration Service Usage Service Trouble Service Test

Resource Domains
Resource Strategy &
Resource Resource Topology Resource Performance Plan

Resource Specification Resource Configuration Resource Usage Resource Trouble Resource Test

Supplier / Partner S/P Performance S/P Bill

Supplier/Partner S/P Interaction S/P Order
S/P Problem S/P Bill Inquiry
S/P Plan S/P Product S/P SLA S/P Statistic S/P Payment

Enterprise Common Business

Party Business Interaction
(Under Construction)
Location Policy Agreement
 Product – Service – Resource
ProductReferences

0..n 0..n
Services and Resources are 0..1 Product
delivered through Products 0..1
0..n

ProductBundleComprisedOf

0..1 ProductBundle ProductComponent

ProductHasCustomerFacingServices

ProductHasPhysicalResources

Service Resource

0..n 0..n
ResourceFacingService CustomerFacingService LogicalResource PhysicalResource

0..1 0..1 1..n 0..n 1..n 0..n 0..n 1..n

CFServiceRequiresRFServices PResourceSupportsLResource
LogicalResourcesImplementRFS

PhysicalResourcesHostRFS
 Technology Neutral Architecture
Shared Component Service Contract Contract Instance Processes Policies
Information registrations registrations registrations registrations
Repository

Contract Instance Mandatory

Registration Repository Naming
Location Framework
Service Service Service
Service Services

Contract Inst. Contract Inst. Contract Inst. Contract Inst.

Int. Mech. Int. Mech. Int. Mech. Int. Mech.

Common Communications Vehicle

Int. Mech. Int. Mech. Int. Mech. Int. Mech. Int. Mech.
Contract Inst. Contract Inst. Contract Inst. Contract Inst. Contract Inst.

Service Service
Policy Process Security
Service Service Service
Legacy
Application
Other Mandatory Services
Other Business Services
NGOSS Lifecycle
Plan
Introduction

3GPP IP Multimedia Subsystem

TISPAN NGN Architecture

NGN Management

Conclusion