Foro4 Alcatel-lucent Epc Enero2013

7/14/2019 Foro4 Alcatel-lucent Epc Enero2013

http://slidepdf.com/reader/full/foro4-alcatel-lucent-epc-enero2013 1/48

COPYRIGHT © 2013 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

J ANUARY 22TH, 2013

ALCATEL-LUCENT EVOLVED PACKET CORE OVERVIEW

Lilia Langan



• What is different on the ePC?

• Alcatel-Lucent ePC solution

• CNT trial overview

ALCATEL LUCENT EPC OVERVIEW

Agenda





LTE NETWORK ARCHITECTURE

NETWORK ELEMENTS AND INTERFACES

COPYRIGHT © 2012 ALCATEL-LUCENT. ALL RIGHTS RESERVED.3



Serving Gateway• Focus on secure data connectivity with many eNB

• Local mobility anchor - for inter-eNB handover and inter-3GPP mobility

• Provides buffering capability in order to ensure lossless data delivery

PDN Gateway• Focus on highly scalable data connectivity (responsible for IP management and

connects with Internet)

• IP anchor

• High volume of real-time QoS processing, lots of per-flow filtering D A T A

( U S E R )

P L A N E

SGW

-


MAIN EPC NETWORK ELEMENTS


• Policy Charging Enforcement Function and interfaces to charging systems

Mobility Management Entity• Control-plane element (mobility management, connection management) for high

volume of mobility/control plane signaling (managing thousands of eNBs)

• Authenticates UEs and controls access to network connections

• Controls attributes of established access (e.g., assignment of network resources)

Policy and Charging Rules Function• Performs network control of flows: detection, gating, QoS and flow-based charging

• Dynamic policy decision on service data flow treatment in the PCEF (xGW)

• Authorizes QoS resources C O N T R O L

P L A N E

4 | EPC update for EMEA | March 2009

MME

PCRF




3G TO LTE NODE MAPPING

GGSN

SGSN

P-GW

MME S-GW

3G LTE

C-Plane C-Plane U-PlaneU-Plane


• In contrast to 3G architecture, no Radio Network Controller(RNC) isrequired: the RNC’s functions are collapsed into the eNodeB, MMEand S-GW

• In LTE the MME takes care of most of the signaling

RNC

NodeB eNodeB



• Default Bearer

• An EPS bearer that established when the UE initially attaches to the network and connects to a PDN, it remains established throughout the lifetime of thePDN connection to provide the UE with always on IP connectivity to the PDN

• Dedicated bearer

LTE TERMINOLOGY

DEFAULT & DEDICATED BEARERS


• Is an additional EPS bearer that is established to the same PDN for which adefault bearer has already established for the same UE

• Only one Default Bearer with one or more dedicated bearers (per APN)



• Aggregate set of packet flows matching a service data flow template

• Service Data Flow Filter• A set of IP header parameter values/ranges used to identify one or more of

the packet flows constituting a service data flow.

• Service Data Flow Tem late

LTE TERMINOLOGY

SERVICE DATA FLOW


• The set of service data flow filters in a PCC rule, required for defining aservice data flow

PDN-GW

IP-Connectivity Access Network Session UE-IP1@

Dedicated bearer (GBR) UE-IP1@

UE Default bearer

SDF-1

SDF-3

SDF-2

UE-IP1@



LTE NETWORK PROTOCOLS

GTP-U PROTOCOL STACK IN EPS


The Key Role of the SGW and PGW is to manage the User plane bearer traffic

• Note the 2 IP headers:

• Inner IP header from the UE going transparent through EPS

• Outer IP header to encapsulate GTP-U and is used inside the EPS



• Diameter is a AAA protocol

• It defines clients, servers, relays, and proxies

• Runs over TCP or SCTP using port 3868

• Base protocol is defined in RFC 3588 (2003)

• Defined as part of the base protocol are a number of messages and AVPs

• AVP = Attribute Value Pair (similar to a TLV)

LTE NETWORK PROTOCOLS

DIAMETER PROTOCOL AND APPLICATIONS


• Capability negotiation, i.e., which applications are supported• The Diameter protocol is used by Diameter applications. Each one defines its

own messages and AVPs on top of the base protocol

• NASREQ (authentication of users)

• Credit Control defined in RFC 4006 (prepaid accounting)• Gx, Rx

• Destination Realm (AVP) identifies the Diameter server

• Routing at relays/proxies: based on destination realm and application



• UE sends Attach message to MME to register with the network for service access

• MME will signal the SGW via a Create Default Bearer Request message to establish thedefault bearer after successful authentication

• SGW forwards the request to PGW

• PGW requests from the PCRF the new session policy then installs necessary filter for thenew session

LTE BASIC SIGNALING

ATTACHMENT & DEFAULT-BEARER CREATION


SGi

S11

S5

eUTRANS1-U

S1-MME

MME

SGW PGW IP Network

Gx

X2

eNB

eNB

An Always-on IP connection is

established & anchored at

the PDN-GW

PCRF



• PCRF is consulted when UE attaches (during default bearer creation phase)

• Receives request for dynamic policies for the default bearer (from the PGW)

• Retrieves user profile and executes ruleset for decision on policy & charging

• Responds to PGW with PCC rule

• Traffic Flow Template

• oS rofile

LTE BASIC SIGNALING

PCRF INTERACTION FOR DEFAULT-BEARER CREATION

HSS/SPR


• Charging profile

Other inforules

Rules Engine

1. IMSI,

UEIP@,

location, RAT,

CAN type…

2. IMSI,

subscriptionprofiles

3. PCC rules:

TFT, QoS,Charging rules

PGW

PCRF



LTE BASIC SIGNALING

UE ATTACH & DEFAULT BEFAULT CREATION CALL FLOW

User authentication &confidentiality

PDN-GW & SGW

selection

Setup context for default data path

Attachment RequestSwitch-on

eNB MME SGW PDN-GW PCRF


Default bearer for “always on” IP connectivity

Default Policy &Charging Rules

(per sub, per service)UL/DL MBR, delay,

BER

User IP address

allocation

Default Data pathcreated

UE context setupRadio bearer configuration

SDF IMS signaling

SDF HSI

Downlink Data

Uplink Data

Update default data path(eNB tunnel end-points)



• Two types of service requests are supported by the EPC (UE or Network initiated)

• Either service requests can trigger creation of Dedicated Bearers

• UE can send Request Bearer Allocation message to MME after service request

• PCRF can trigger creation based on received service request

LTE BASIC SIGNALING

SERVICE REQUEST & DEDICATED BEARERS


SGi

S11

S5

eUTRANS1-U

S1-C

MME

SGW PGW IP Network

Gx

X2

eNB

eNB

1. UE sends NAS

Service Request

message towards MME

2. Update Bearer Requestis sent to the S-GW

to establish / modify

S1-bearer

3. Dedicated bearerestablished after

interaction with PCRF



2. PCC Provision:

SDF, QoS,

• Subsequent to interaction with user, the Application requests for a media flowfor the application session. Example: Voice, Video call/streaming, etc.

• PCRF executes ruleset and authorizes a Dedicated Bearer for it (GBR or not)• QoS and charging rules determined and sent to PGW

LTE BASIC SIGNALING

PCRF INTERACTION FOR DEDICATED BEARER REQUEST


Other info

rules

Rules Engine

3. Response

Charging rules

Application

Function

SPR

Cache

. , ,

Media, AF info,

Priority,

Emergency

4. Response

Session

Cache

PGW

PCRF



LTE BASIC SIGNALING

DEDICATED BEARER CREATION CALL FLOW

Service Request & Authentication

Call set-up

SIP: INVITE (SDP Offer)

Application Info

Policy Decision:

eNB MME SGW PDN-GWPCRF P-CSCF


Voice stream = Guaranteed

Bit Rate

SessionModification

Setup context for new

dedicated data path

New dedicated datapath created

Radio bearer configuration

Session modified

Successfulnotification

SIP: 200 OK

Voice stream

Dedicated bearer (GBR) Voice stream (SDF)



• The EPS maintains two types of state information to manage UE mobility & UE/EPC connectivity

• EPS Mobility Management (EMM) states describe the mobility status of UE’s resultedfrom mobility management procedures (e.g. Tracking Area Update)

• EPS Connection Management (ECM) states describe the signaling connectivity between

the UE & the EPC

LTE MOBILITY MANAGEMENT

MOBILITY & CONNECTION MANAGEMENT IN EPS


Air InterfaceConnectivity

Network(Signaling)

Connectivity

Bearer &Mobility

Management




MOBILITY MANAGEMENT STATES

• EMM context holds no valid location

EMM_REGISTEREDEMM_DEREGISTERED

• UE successfull re isters with MME

Attach

Detach


or routing info for UE

• UE is not reachable by the MME, asthe UE location is not known

with Attach procedure or a Tracking Area Update (TAU) procedure

• UE location is known withintracking area

• MME can send page to UE

• UE always has at least one activePDN connection

TA2

TA1

MME




CONNECTION MANAGEMENT STATES

ECM_CONNECTEDECM_IDLE

Signaling connectionestablished

Signaling connectionreleased


• Signaling connection isestablished between the UEand MME consists of twocomponents: RRC connectionand S1-MME connection

• UE location is known to the

accuracy of the cell ID

• No signaling connectionbetween UE and core network (no S1-U, S1-MME)

• No RRC connection (RRC_IDLE)

• UE performs cell reselection andtracking area updates (TAU)



• SGW initiates process when it receives downlink packets for a UE in idle mode

• A Downlink Data Notification message is sent from SGW to MME

• SGW begins to buffer the received DL packets• MME sends Paging message eNBs within the TA that the UE is registered. Upon paged,

UE initiates the service request procedure, re-establishing the S1 bearer


PAGING & DOWNLINK PACKET BUFFERING


eNB

SGi

S11

S5

eUTRANS1-U

S1-MME

MME

SGW PGW IP Network

X2

Gx

eNB

2. Downlink Data

Notificaation message

is sent to the MME

1. DL packets received &

buffered by S-GW since

there is no active

S1-bearer

3. MME initiated Paging

procedure towardseNBs

PCRF



• X2 Handovers

• Without SGW relocation: only eNodeB changes but not MME and SGW

• With SGW relocation: eNodeB and SGW changes (but not MME)• S1 Handover

• Only performed when X2 handover is not possible

•


HANDOVER TYPES


• When there is no IP connectivity between source SGW and target eNodeB

• When serving PLMN changes (=provider of access network changes)

• X2 handover failed

• MME and/or SGW can change

• Inter-RAT handovers

• Handovers between 2G/3G and 4G, as well as non-3GPP access (eHRPD, WLAN)




LTE / 3G iRAT HANDOVER (Pre-R8 interworking architecture)





LTE / 3G iRAT HANDOVER (R8 interworking architecture)




SGiHSS

S6a

HPLMN

VPLMN

Gx RxH-PCRF

LTE ROAMING

ROAMING TO HOME NETWORK

UTRAN

GERAN

SGSN

PGWPDN1


S11

S3S8

S4

S1-U

S1-MME

MME

S12X2

eNode B

eNode B

EUTRAN SGW



HSS

S6a

H-PCRF

HPLMN

VPLMN S9

LTE ROAMING

LOCAL BREAKOUT

UTRAN

GERAN

SGSN


SGi

S11

S3

S5

S4

S1-U

S1-MME

MME

V-PCRF

S12

SGW PGW

Gx

X2

eNode B

eNode B

EUTRAN PDN1

Rx



QoSChargingForwardingClassification

Policy 1Policy 1

Policy 2Policy 2

Policy 3Policy 3

Subscriber Traffic inbearer/PDP context

E-mailOffline charging

POLICY AND CHARGING CONTROL

CUSTOMIZED SERVICE TRAFFIC MANAGEMENT


Policy 4Policy 4

Subscriber Traffic Management based on• Subscription package• QoS and Charging profiles• subscriber balance/status•Network and external events

Enforced through PCC architecture

Social NetworkingFree of Charge

Peer-to-PeerOnline charging (real time)

Rate enforcement

Malicious trafficDiscarded



• Subscriber profile/package/class/tariff

• Standard, Lite, Premium, Corporate, …

• Network information• Subcriber location (e.g, home-zone), inter-RAT, …

• Subscriber data consumption (fair usage): € Remaining

POLICY AND CHARGING CONTROL

CUSTOMIZED TRAFFIC MANAGEMENT – CRITERIA


, ,…

• External events

• E.g, Time of day

• Service Provider may have additional constraints

• Peer-to-peer limitation at PGW/GGSN level

• Global or per APN Gi/SGi throughput control

• e.g, per MNO basis for MVNE

Consumed



QCIRESOURCE

TYPEPRIORITY

PACKET DELAY BUDGET

PACKET ERROR LOSS RATE

EXAMPLE SERVICES

1

GBR

2 100 ms 10-2 Conversational Voice

2 4 150 ms 10-3 Conversational Video (Live Streaming)

3 3 50 ms 10-3 Real Time Gaming

Non-Conversational Video Buffered

QOS IN LTE NETWORKS

EVOLVING TO A QOS-AWARE MULTI-SERVICE CORE


ms - Streaming)

5

Non-GBR

1 100 ms 10-6 IMS Signaling

6 6 300 ms 10-6

Video (Buffered Streaming), TCP-based (e.g.www, e-mail, chat, ftp, p2p, file sharing,

progressive video, etc.)

7 7 100 ms 10-3 Voice, Video (Live Streaming), Interactive

Gaming

8 8300 ms 10-6

Video (Buffered Streaming), TCP-based (e.g.www, e-mail, chat, ftp, p2p, file sharing,

progressive video, etc.)9 9

* 3GPP TS 23.203



QOS IN LTE NETWORKS

KEY BEARER / AGGREGATE ATTRIBUTES

• QoS Class Identifier (QCI)- Used to identify the traffic class of a specific bearer

• Allocation and Retention Priority (ARP)- The primary purpose or ARP is to decide if a bearer establishment/modification request

can be accepted or rejected in case or resource limitation

• Guaranteed Bit Rate (GBR) and Maximum Bit Rate (MBR)


- GBR bearers are assigned a guaranteed rate and a maximum rate• APN Aggregate Maximum Bit Rate (APN-AMBR)- Aggregate rate for the total traffic of a UE’s Non-GBR bearers on a given APN

- Enforced by the PGW on Downlink and the UE on Uplink

• UE Aggregate Maximum Bit Rate (UE-AMBR)- Aggregate rate for the total traffic generated by a UE across all APNs

- Enforced by the eNodeB on Uplink



QOS IN LTE NETWORKS

SDFs AND QOS MANAGEMENT

• The SGW and PGW need to support fine-granularity of QoS andcharging enforcement functions beyond transport / bearer level

- Multiple Service Data Flow (SDF) can be aggregated onto a single bearer- Uplink (UL) and Downlink (DL) packet filters are defined for each bearers

and QoS enforcements (policing, shaping, scheduling, etc.) are applied

- PGW acts as the Policy and Charging Enforcement Function (PCEF) point to


maintain QoS SLA or eac o t e earers an SDFs

TerminaleNodeB Serving GW PDN GW

PCRF

Terminal







Programme




ALCATEL-LUCENT APPROACH

MIRRORING DATA/USER PLANE SPLIT WITH DEDICATED PORTFOLIO

control plane SGSN/MME

PCRF

Control plane:

• Highly scalable, dynamic mobility and

connection management

• Network-wide, real-time policy control

HIGH PERFORMANCE, RELIABLE, SCALABLE,

IN-HOUSE OPTIMIZED ATCA-BASED PLATFORM

FOR PACKET CORE CONTROL-PLANE ELEMENTS

OTHER NETWORKS


E-UTRANUTRANGERAN

user (data) plane PGW/GGSN

SGW

Data plane:

• High aggregate throughput (over 100 Gbps) forhigh bandwidth on-demand services

• Per-subscriber, per-application, per-session

QoS/policy enforcement and control

HIGH PERFORMANCE, RELIABLE AND SCALABLE,PROVEN INDUSTRY-LEADING SERVICE ROUTERSFOR WIRELESS PACKET GATEWAYS

CORE NETWORK (CN)RADIO ACCESS NETWORK (RAN) INTERNET



Converged

Service Control

ALCATEL-LUCENT WIRELESS PACKET CORE

Policymanagement

Sessioncontrol

2G, 3G, LTE

MobilePacketCore

5780 Dynamic ServicesController

PCRF for 3G and LTE

7750 SR Mobile Gateway4G packet gateway for

3G/3G+ GGSN andLTE gateway functions

(SGW, PGW)

9471 Wireless Mobility ManagerMobility managerfor 2G/3G (SGSN)and LTE (MME)

Mobilitymanagement

Common routing stack

Common routing platform

Common control platform


Converged All-IPService-aware

Network Management

Multi-screen servicesWeb and Enterprise 2.0

Mobile

Backhaul

Pre-integrated Solutions5620 Service Aware Manager- NM for Packet Core

- NM for RAN and backhaul

Backbone

KEY GGSN: Gateway GPRS Support NodeSGSN: Serving GPRS Support NodeMME: Mobility Management EntityPCRF: Policy Charging & Rules Function



LTE/4G: ALL-IP ENVIRONMENT


• HIGH-SCALE IP ADDRESS SPACEMANAGEMENT (FOR ALL UES)

• APN MANAGEMENT• EPC PDN IP ROUTING

• SESSION MANAGEMENT• QOS ENFORCEMENT• APPLICATION ASSURANCE (L4-L7)• PACKET FILTERING AND CHARGING

• HIGH-SCALE ENODEB AND

MME CONNECTIVITY • PACKET BUFFERING• SESSION MANAGEMENT• ENCRYPTION• HIERARCHICAL QOS• PER-BEARER SCHEDULING

UEs



WHY ATCA FOR CONTROL PLANE?


• Real-time policy management• High-scale processing• Interaction with subscriber

databases, gateways, chargingand reporting systems

• High-scale UE and eNodeBmanagement (millions of

users, thousands of eNBs)• High-performance, low-cost

carrier-class platform• Flexible, multi-core

processors blades distributesignaling load

UEs



7750 SERVICE ROUTER MOBILE GATEWAY

-Mobile Gateway

- -

+ =


• Full-featured service routing platform

• Field-proven as multiservice edge, core routerand broadband network gateway: nearly50,000 units shipped in 6 years

• 99.999+% availability with non-stop services,

in-service software upgrade (ISSU)• I/O Modules (IOM) with 100 Gb/s wire-speed

• Feature-Rich: H-QoS, DPI, IPSec, MPLS...

• Full set of IPv4/IPv6 routing capabilities to tiedirectly to IP aggregation and backbone

• Mobile Gateway Integrated Services Module

• 20M PPS (25 Gb/s) L3/L4 Shallow PacketInspection on Network Processing Units (NPU)

• 2M PPS (7-10 Gb/s) L4-L7 Deep PacketInspection on Central Processing Units (CPU) of

dedicated MG-ISA daughterboard (IntegratedServices Appliance)

• Second MG-ISA entirely dedicated to ControlPlane traffic (GTP-C, RADIUS, DIAMETER,...)

• 1+1 Stateful Resiliency

(SGW, PGW/GGSN)



PGW/GGSN User Plane processing: 5-tuple and L4-L7 (AA)

g f a b r i c

Advanced Data

Plane ISAP-chip

1M Policers

MDA/ISA

SLOT

MDA/ISA

SLOT

I O M 3

Gn/S5

User plane subject to 5-tuple classification

User plane subject to Layer4-L7 protocol analysis

Application Assurance (AA):

Up to 10 Gbps processing

25 Gbps processing


S w i t c h i n

Control Plane

ISA

IOM control

Q-chip

64K Queues

MDA/ISASLOT

MDA/ISASLOT

I O M 3

Gi/SGi



ALCATEL-LUCENT 9471 WIRELESS MOBILITY MANAGER

(MME/SGSN)

Scalability

• Up to 8 million subs, 8 million PDP contexts, and

thousands of eNodeBs

Configuration flexibility

• 2G/3G SGSN, MME, combo SGSN/MME

Performance

High performance, MME/SGSNcombo for 2G, 3G & LTE


• p to ps t roug put us ng ua core,

dual density processors

Carrier-class reliability

• Five 9’s+, field proven

Architecture

ATCA platform, multi-core processors; leverages Alcatel-Lucent LCP middleware

Advanced Optimization capabilities

• Smart paging

• PCMD

Alcatel-Lucent 9471 WMMMME / SGSN

Differentiator: Per Call Measurement Data (PCMD)



Differentiator: Per Call Measurement Data (PCMD)

Post processing

MMEMME

PCMD file

PCMD stream

PCMD start/stop

Real-Time Client(Optional connection)

SGW

OPTIMISATIONPLANNING

CUSTOMER

CARE

Analysis

EVOLVED RANMGMT

LTE no longer has the ‘RNC view’

• Valuable data (e.g. UE RF metrics & TP) is restricted tothe eNB while only the MME has UE IMSI and mobility


eNodeB

eNodeB

PCMD data

eNodeBeNodeB

eNodeB

eNodeB

PCMD data

PCMD data

. . . . . . . . . . .

PCMD start/stopPCMD start/stop

Simplified data collection and analysis for ALL calls at ALL times

• ALU MME aggregates eNB & MME data in a centralized

manner for e2e analysis• All the UE mobility related activities are logged to analyse

the entire call.

• Signalling, User and Scheduler info in one record



9959 NPO

PCMD stream

ARQUITECTURA PCMD

Counters, alarms, parameters, topology, events

User interface

QoS Alerters/ tuning

External query interface

eNodeB data is:

1. Captured from UE to eNB

2. Sent to MME via S1private message

3. Consolidated at the MME

4. Sent to NPO


S-GW

P-GW

5620 SAM

Evolved Packet Core

MME

RAN

counterscounters

eNB records

eNB

C



PCMD content

Control Plane

• Procedure id: Attach/Detach, Bearer Mgt, HO,

TAU, Paging, etc.

• Procedure duration, error code, source failure

User plane

• UL/DL data volume per Bearer (non-

GBR)

• Bearer information (QCI, etc)

•

Record identificationTimestamp, IMSI, EMEI, Cell Id, MME Id, S/GW, …


• Relevant data according to procedure,

RF information• Radio quality: Channel Quality Indicator, dropped packets at RLC layer

• UE measurements: RSRP, RSRQ, etc.

• Round Trip Delay (RTD)

• RF measurement of other cells for HO preparation

A PCMD record is generated for each procedure that is executed for a particular UE.

A PCMD record is a semi-colon separated set of about 200 fields (grows with each release) containing data of interest for

that procedure. The actual structure is different from the figure.

5780 DYNAMIC SERVICES CONTROLLER



5780 DYNAMIC SERVICES CONTROLLER


ALCATEL LUCENT MOBILE CHARGING SOLUTION



Mobile network domain

Subscriber database

ALCATEL-LUCENT MOBILE CHARGING SOLUTION

8650 SDM (HLR/HSS)

Policy management

5780 DSC (PCRF)

Charging domain8610 ICC

(OCS)8615 IECCF

(CGF)

LDAP

GaGyGxS6a/Gr

Sy


eNB

Internet

9471 WMMMME/SGSN

7750 SR SGW

RNC7750 SR

PGW/GGSN

S11

S5

A COMPLETE AND PRE-INTEGRATED SOLUTION RESPECTING 3GPP OPEN INTERFACES

IP/MPLSbackbone

Mobileaccess/backhaul

network

Differentiator: Intelligent Traffic Management



Differentiator: Intelligent Traffic Management


5620 SERVICE AWARE MANAGER



OSS Connected Partner Program

5620 SERVICE AWARE MANAGER

SGSN/MME PCRF

Ultimate Wireless

Packet Core

SGW PGW/GGSN

Mobile Backhaul

GERAN

GPRS, EDGE

E-UTRANLTE

UTRAN

UMTS, HSPA

5620 SAM5620 SAM


• Rapid Provisioning

• Minimized operator errors, optimized workflows, automated configuration

• Proactive Assurance

• Cross-layer visualization and correlation – detect issues before they affect subscribers

• Operational Fit and Flexibility

• Minimized integration cost, effort and risk

Industry-leading IP/MPLS management with over 270 worldwide deployments

Alcatel-Lucent ePC: A fully Geo-redundant solution



BB A1

BB A2

SeGW

PGW

Site A

SGW

MME

PCRF

NMS

MME poolingS1 Flex on eNB

SGW pooling/geo-redundancyStateful geo-redundancy in MG R4.0

Geo-resilient SeGWStateless, stateful in SR R10r4


eNB

BB A1

BB A2

Site B

SeGW

PGW

SGW

MME

PCRF

NMS

PGW geo-redundancyStateful geo-redundancy in MG R5.0

PCRF geo-redundancy Act/Sby stateless in DSC R4.0

Act/Act stateful in DSC R5.0

NMS geo-redundancySAM Main, DB, Call trace








Programme


CNT trial architecture



WINDSServers (2)

FTPServers (2)

d2U

RRH

RRH

RRH

1 BBU

3RRH

eUTRAN

eNodeB #1 (Quito)

Core

Tools/Services

d2U

RRH

RRH

RRH

1 BBU

3RRH

eUTRAN

eNodeB #2 (Quito)

CNT trial architecture


CNTTransport

Network

Internet

NPOClient

SAMClient

SGW PGW

(ePC +HSS)

MMEHSS

PCRF

9959NPO /PCMD OAM

5620SAM

DNS eDATClient

WPSClient

RAMSES

d2U

RRH

Toy Cell

eNodeB

7750 SR



49

Documents

Foro4 Alcatel-lucent Epc Enero2013