Changes to all ip nam
This presentation is the property of its rightful owner.
Sponsored Links
1 / 6

Changes to All-IP NAM PowerPoint PPT Presentation


  • 93 Views
  • Uploaded on
  • Presentation posted in: General

Changes to All-IP NAM. The current NAM does not represent the domains as documented in the requirement document. Both ANSI41 domain and IP MMed domain should be represented in the architecture. This document proposes a correction to align with requirements and architecture principles.

Download Presentation

Changes to All-IP NAM

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -

Presentation Transcript


Changes to all ip nam

Changes to All-IP NAM

  • The current NAM does not represent the domains as documented in the requirement document.

  • Both ANSI41 domain and IP MMed domain should be represented in the architecture. This document proposes a correction to align with requirements and architecture principles.

  • In addition to domain representations, additional changes are proposed and are described in the accompanying contribution “Analysis on roles of SM, RM, PM, SecM and MM in NRM”.

  • The color code indicate the following: yellow boxes are used to indicate the access level part of the IP MMed domain. Some of these entities are also used for ANSI41 domain access as well.

  • The light blue boxes indicate the pure ANSI41 domain entities.


Changes to all ip nam

AAA,DS,DNS...

3rd party

Services

SCE

IP MMed domain

Service

manager

RSGW

LS+PDE

TSGW

SCM

MGCF

PSTN

ACS

MRF

MGW

WAG

PDN

BSC/RNC

+PCF

PDSN

HA

ANSI41 domain

MSC

server

RSGW

T-SGW

PLMN

SCP

HLR

MGW


Proposed changes 1

Proposed Changes (1)

  • Clear representation of ANSI41 domain containing MSC server, and gateways (media, trunk-signaling and roaming)

  • A set of support framework functions required for network operations is composed of AAA, DS, DNS etc..

  • HA to the AAA interface added

  • New ACS interfaces to WAG and the set of support functions mainly AAA.

  • Removal of interfaces 20, 21 and 22.

  • MSC to HLR interface added.

  • SCP entity added into the ANSI41 domain


Proposed changes 2

Proposed changes (2)

  • Remove SM, MM, PM, SecM, RM from the architecture because as explained earlier, these functions exist in other architecture entities but fulfilling other specific roles (eg. MRF, MGCF, PDSN, AAA, etc..).

  • The functions SM, MM, PM, SecM, RM represent functional model of the architecture, mixed with physical entities such as PDSN containing similar type of functions. This representation brings confusion.


Proposed changes 3

Proposed changes (3)

In the MMed service layer, there is a need for functions

  • to provide control of the MMed sessions,

  • may be locate entities within the domain that best service a specific request,

  • ensure that MMed users and user’s requests are authenticated domain entities

  • communicate with the AAA in order to retrieive user’s policy. All these functions could be housed within one entity that we label SCM for Session Control Manager.


Proposed changes 4

Proposed changes (4)

  • Similarly, in the access layer, a function is created which overlooks resources in the access part of the IP MMed domain. Controls the packet sessions in the access part of the network and allocates, distribute access resources (PDSN) based on the traffic characteristics, etc. It retrieves resource policy decision and apply the policy on the PDSN and RAN. This entity is labeled ACS for Access Control Server.

  • The function of policy manager function is ambiguous and should be removed. The functions of policy are embedded within the architecture entities (see accompanying contribution).


  • Login