Doc5-LTE Workshop TUN Session4 Network Architecture

ITU/BDT Arab Regional Workshop on 4G Wireless Systems -Tunisia 2010
/ b l k h ITU/BDTArab Regional Workshopon

4G Wireless Systems 4GWirelessSystems
LTETechnology
Session4:NetworkArchitecture
Speakers M.Lazhar BELHOUCHET
M Hakim EBDELLI M.HakimEBDELLI
Date 27 29January 2010
www.cert.nat.tn
1
NetworkArchitecture
Agenda
Introduction
EvolvedPacketSystem(EPS)Architecture
Subsystems
NetworkArchitectureEvolution
LTE/SAE N k El LTE/SAENetworkElements
LTE/SAENetworkInterfaces /
www.cert.nat.tn
2
NetworkArchitecture
Introduction
LTE/SAE architecture is driven by the goal to
optimize the system for packet data transfer.
No circuit switched components
IMS/PDN
New approach in the inter-connection between
radio access network and core network
TheEPSarchitectureismadeupofanEPC(Packet
k l f d ) d
EPC
CoreNetwork,alsoreferredasSAE)andan
eUTRANRadioAccessNetwork(alsoreferredas
LTE)
The CN provides access to external packet IP
eUTRAN
TheCNprovidesaccesstoexternalpacketIP
networksandperformsanumberofCNrelated
functions(e.g.QoS,security,mobilityandterminal
contextmanagement)foridle(camped)andactive
LTE-UE
terminals
TheRANperformsallradiointerfacerelated
functions
EPS
www.cert.nat.tn
3
NetworkArchitecture
EPS
Evolved Packet System (EPS) Architecture -Subsystems
E-UTRAN SAE or EPC
www.cert.nat.tn
4
NetworkArchitecture
NetworkArchitectureEvolution
Direct tunnel
I-HSPA
HSPA R7 HSPA R7 LTE R8
HSPA
HSPA R6
LTE
SAE GW
GGSN
SGSN
GGSN
SGSN
MME/SGSN
GGSN
SGSN
SGSN
RNC
SGSN
MME/SGSN
SGSN
RNC
Node B
(NB)
Node B +
RNC
Functionality
Evolved
Node B
(eNB)
Node B
(NB)
User plane
Control Plane
www.cert.nat.tn
5
Control Plane
NetworkArchitecture
NetworkArchitectureEvolution Cont.
Internet
3GPP Rel 6 / HSPA
Node B RNC SGSN GGSN
Original 3G architecture
User plane
Original 3G architecture.
2 nodes in the RAN.
2 nodes in the PS Core Network.
Control Plane
Every Node introduces additional delay.
Common path for User plane and Control plane data.
Air interface based on WCDMA. Air interface based on WCDMA.
RAN interfaces based on ATM.
Option for Iu-PS interface to be based on IP.
www.cert.nat.tn
6
NetworkArchitecture
3GPP Rel 7 / Internet HSPA
Internet
SGSN
GGSN
Direct tunnel
Internet
Node B
(RNC Funct.)
User plane User plane
Control Plane
I-HSPA introduces the first true flat architecture to WCDMA.
Standardized in 3GPP Release 7 as Direct Tunnel with collapsed RNC.
M t t f th RNC f ti liti d t th N d B Most part of the RNC functionalities are moved to the Node B.
Direct Tunnels runs now from the GGSN to the Node B.
Solution for cost-efficient broadband wireless access.
Improves the delay performance (less node in RAN).
It can be deployable with existing WCDMA base stations.
Transmission savings
www.cert.nat.tn
7
Transmission savings
NetworkArchitecture
3GPP Rel 8 / LTE
MME
SAE GW
Direct tunnel
Internet
Evolved Node B
User plane
LTE takes the same Flat architecture fromInternet HSPA
User plane
Control Plane
LTE takes the same Flat architecture from Internet HSPA.
Air interface based on OFDMA.
All-IP network.
New spectrum allocation (i.e 2600 MHz band)
Possibility to reuse spectrum (i.e. 900 MHZ)
www.cert.nat.tn
8
NetworkArchitecture
y ( )
LTE/SAENetworkElements
Evolved UTRAN (E-UTRAN)
Evolved Packet Core (EPC)
HSS
S10
S6a
MME: Mobility Management Entity
PCRF:Policy & Charging Rule Function
LTE-UE
MME
S10
S11
S1-MME
PCRF
S7
Rx+
Evolved
Node B
(eNB)
X2
Serving
Gateway
S1-U
PDN
Gateway
PDN
SGi S5/S8
cell
LTE-Uu
Main references to architecture in 3GPP specs.:
TS23 401 TS23 402 TS36 300
Gateway Gateway
SAE
Gateway
www.cert.nat.tn
9
TS23.401,TS23.402,TS36.300
NetworkArchitecture
Evolved
LTE U
LTE-UE
EvolvedNodeB(eNB)
Inter-cell RRM: HO, load balancing between cells
Radio Bearer Control:setup , modifications and
release of Radio Resources
eNB Functions
Evolved
Node B
(eNB)
cell
LTE-Uu
release of Radio Resources
Connection Mgt. Control: UE State Mgmt. MME-UE
Connection
Radio Admission Control
It is the only network element defined as part
of EUTRAN.
It replaces the old Node B / RNC combination
eNode B Measurements Collection and evaluation
Dynamic Resource Allocation (Scheduler)
IP Header Compression/ de-compression
It replaces the old Node B / RNC combination
from 3G.
It terminates the complete radio interface
including physical layer.
Access Layer Security: ciphering and integrity
protection on the radio interface
MME Selection at Attach of the UE
It provides all radio management functions
An eNB can handle several cells.
To enable efficient inter-cell radio
User Data Routing to the SAE GW.
Transmission of Paging Message coming from MME
Transmission of Broadcast Info(System info, MBMS)
management for cells not attached to the
same eNB, there is a inter-eNB interface X2
specified. It will allow to coordinate inter-eNB
handovers without direct involvement of EPC
www.cert.nat.tn
10
during this process.
NetworkArchitecture
MME Functions
Control plane NE in EPC
MobilityManagementEntity(MME)
Evolved
Node B
(eNB)
MME
S1-MME
HSS
S6a
Non-Access-Stratum (NAS)
Security (Authentication,
integrity Protection)
Idle State Mobility Handling
Serving
Gateway
S1-U
S11
S6a Idle State Mobility Handling
Tracking Area updates
Subscriber attach/detach
Radio Security Control
Signalling coordination for
SAE Bearer Setup/Release
It is a pure signaling entity inside the EPC.
SAE uses tracking areas to track the position of idle UEs. The basic
principle is identical to location or routing areas from 2G/3G.
Trigger and distribution of
Paging Messages to eNB
Roaming Control (S6a interface
t HSS)
MME handles attaches and detaches to the SAE system, as well as
tracking area updates
Therefore it possesses an interface towards the HSS (home subscriber
server) which stores the subscription relevant information and the
tl i dMME i it t d t b
to HSS)
Inter-CN Node Signaling
(S10 interface), allows efficient
inter-MME tracking area updates
and attaches
currently assigned MME in its permanent data base.
A second functionality of the MME is the signaling coordination to setup
transport bearers (SAE bearers) through the EPC for a UE.
MMEs can be interconnected via the S10 interface
www.cert.nat.tn
11
and attaches
NetworkArchitecture
Evolved
Node B
MME
ServingSAEGateway
(eNB)
MME
S1-U
S1-MME
S5/S8
S11
S6a
ServingGateway Functions
Serving SAE
Gateway
PDN
Gateway
Local mobility anchor point:
Switching the user plane path to a
new eNB in case of Handover
Serving Gateway Functions
The serving gateway is a network element that manages
the user data path (SAE bearers) within EPC.
It therefore connects via the S1-U interface towards eNB
d i li k k t d t f h d t it
Mobility anchoring for inter-3GPP
mobility. This is sometimes referred
to as the 3GPP Anchor function
and receives uplink packet data from here and transmits
downlink packet data on it.
Thus the serving gateway is some kind of distribution and
packet data anchoring function within EPC.
Idle Mode Packet Buffering and
notification to MME
Packet Routing/Forwarding
packet data anchoring function within EPC.
It relays the packet data within EPC via the S5/S8
interface to or from the PDN gateway.
A serving gateway is controlled by one or more MMEs via
S11 i t f
between eNB, PDN GW and SGSN
Lawful Interception support
www.cert.nat.tn
12
S11 interface.
NetworkArchitecture
PacketDataNetwork(PDN)SAEGateway
MME
PCRF
S7 Rx+
S11
S6a
PDN Gateway Functions
Mobility anchor for mobility between
3GPP access systems and non-3GPP
access systems This is sometimes
Serving
Gateway
S5/S8
PDN SAE
Gateway
PDN
SGi
Policy Enforcement (PCEF)
Per User based Packet Filtering (i e
access systems. This is sometimes
referred to as the SAE Anchor function
The PDN gateway provides the connection between
EPC and a number of external data networks
Gateway Gateway
Per User based Packet Filtering (i.e.
deep packet inspection)
Charging & Lawful Interception support
EPC and a number of external data networks.
Thus it is comparable to GGSN in 2G/3G networks.
A major functionality provided by a PDN gateway is the
QoS coordination between the external PDN and EPC.
IP Address Allocation for UE
Packet Routing/Forwarding between
Serving GW and external Data Network
Therefore the PDN gateway can be connected via S7
to a PCRF (Policy and Charging Rule Function).
Se g G a d e te a ata et o
Packet screening (firewall functionality)
www.cert.nat.tn
13
NetworkArchitecture
PolicyandChargingRuleFunction(PCRF)
MME
S5/S8 SGi
PCRF
S7 Rx+
S11
S6a
PCRF: Policy & Charging
Rule Function
QoS policy negotiation with PDN
Serving
Gateway
S5/S8
PDN SAE
Gateway
PDN
SGi
Charging Policy: determines how
packets should be accounted
Q p y g
The PCRF major functionality is the Quality of Service
(QoS) coordination between the external PDN and EPC. ( )
Therefore the PCRF is connected via Rx+ interface to the
external Data network (PDN)
This function can be used to check and modify the QoS
i t d ith SAE b t f SAE t t associated with a SAE bearer setup from SAE or to request
the setup of a SAE bearer from the PDN.
This QoS management resembles the policy and charging
control framework introduced for IMS with UMTS release 6.
www.cert.nat.tn
14
co o a e o oduced o S U S eease 6
NetworkArchitecture
HomeSubscriberServer(HSS)
Permanent and central subscriber
database
HSS Functions
MME
HSS
S6a
The HSS is already introduced by UMTS
release 5
Stores mobility and service data for
every subscriber
S6a
Contains the Authentication Center
release 5.
With LTE/SAE the HSS will get additionally
data per subscriber for SAE mobility and service
handling
Contains the Authentication Center
(AuC) functionality.
handling.
Some changes in the database as well as in
the HSS protocol (DIAMETER) will be necessary
to enable HSS for LTE/SAE. to enable HSS for LTE/SAE.
The HSS can be accessed by the MME via
S6a interface.
www.cert.nat.tn
15
NetworkArchitecture
LTE/SAENetworkInterfaces
HSS
S6a
MME: Mobility Management Entity
LTE-UE
MME
S10
S1-MME
PCRF
S7
Rx+
Evolved
Node B
(eNB)
X2
S i
S1-U
S11
PDN
PDN
SGi S5/S8
(eNB)
cell
LTE U
SAE
Serving
Gateway
PDN
Gateway
LTE-Uu
SAE
Gateway
www.cert.nat.tn
16
User plane Control Plane Control Plane +User plane
NetworkArchitecture
LTERadioInterfaceandtheX2Interface
LTE-Uu
f f
(E)-RRC User PDUs User PDUs
..
Air interface of EUTRAN
Based on OFDMA in downlink and SC-FDMA in uplink
FDD and TDD duplex methods
Scalable bandwidth1 4MHz to currently20 MHz
(E) RRC User PDUs User PDUs
PDCP (ROHC =RFC 3095)
RLC
MAC
TS 36.300
Scalable bandwidth 1.4MHz to currently 20 MHz
Data rates up to 100 Mbps in DL
MIMO (Multiple Input Multiple Output) is a major
component although optional.
L ) LTE-L1 (FDD/TDD-OFDMA/SC-FDMA)
eNB
LTE-Uu
X2
Inter eNB interface
Handover coordinationwithout involvingthe EPC
User PDUs
X2-UP
(User Plane)
X2-CP
(Control Plane)
Handover coordination without involving the EPC
X2AP: special signalling protocol
During HO, Source eNB can use the X2 interface to
forward downlink packets still buffered or arriving from
th i t t th t t NB
X2
GTP-U
UDP
IP
TS 36.424
X2-AP
SCTP
IP
TS 36.422
TS 36.423
the serving gateway to the target eNB.
This will avoid loss of a huge amount of packets during
inter-eNB handover.
eNB
L1/L2 L1/L2 TS 36.421
TS 36.421
TS 36.420
[ tl l i TS 36 30020]
www.cert.nat.tn
17
[currently also in TS 36.300 20]
NetworkArchitecture
S1MME&S1UInterfaces
S1-MME
C t l i t f b t NB dMME
S1 MME
Control interface between eNB and MME
S1flex allows 1 eNB to connect to several MME
MME and UE will exchange non-access stratum
signaling via eNB through this interface.
MME
S1-MME
(Control Plane)
NAS Protocols
S1-AP TS 36.413
g g g
E.g.: if a UE performs a tracking area update the
TRACKING AREA UPDATE REQUEST message will
be sent from UE to eNB and the eNB will forward the
message via S1-MME to the MME.
SCTP
IP
L1/L2
TS 36.411
TS 36.412
S1AP:S1 Application Protocol
S1-U
User plane interface between eNB and serving
S1-U
(User Plane)
User PDUs
eNB
gateway.
It is a pure user data interface (U=User plane).
S1flex-U also supported: a single eNB can connect to
several Serving GWs.
Serving
Gateway
GTP-U
UDP
IP
TS 36.414
g
Which Serving GW a users SAE bearer will have to
use is signaled from the MME of this user.
L1/L2 TS 36.411
TS 36.410
www.cert.nat.tn
18
[currently in TS 36.300 19]
NetworkArchitecture
EUTRAN&EPCconnectedwithS1flex
Several cases
1
eNB 1 Single S1-MME
Single S1-U
2
eNB 2 Single S1-MME
Multiple S1-US1Flex-U
3
eNB 3 Multiple S1- p
MMES1Flex
Single S1-U
www.cert.nat.tn
19
NetworkArchitecture
S10&S6aInterfaces
HSS
S6a Candidate
(Control Plane)
S6a Appl.
DIAMETER
S10 Candidate
(Control Plane)
GTP-C
MME
HSS
SCTP
IP
L1/L2
DIAMETER
MME
UDP
IP
L1/L2
L1/L2
TR 29.801
TR 29.801
S10
Interface between different MMEs
S6a
Interface between the MME and the HSS
Used during inter-MME tracking area updates
The new MME can contact the old MME the user had
been registered before to retrieve data about identity
(IMSI), security information (security context,
The MME uses it to retrieve subscription information
from HSS (handover/tracking area restrictions,
external PDN allowed, QoS, etc.) during attaches and
updates
( ), y ( y ,
authentication vectors) and active SAE bearers (PDN
gateways to contact, QoS, etc.)
Obviously S10 is a pure signaling interface, no user
data runs on it.
The HSS can during these procedures also store the
users current MME address in its database.
www.cert.nat.tn
20
NetworkArchitecture
S11&S5/S8Interfaces
S5/S8
Interface between Serving GW and PDN GW
S5 If S i GW d PDN GWb l t th
MME
S11 Candidate
S11
Interface between MME and a Serving GW
A single MME can handle multiple Serving
GW each one with its own S11 interface
U dt di t th t bli h t f SAE
S5: If Serving GW and PDN GW belong to the same
network (non-roaming case)
S8:If this is not the case (roaming case)
S8 =S5 +inter-operator security functions
Mainlyused to transfer user packet data between PDN GW S11 Candidate
(Control Plane)
UDP
GTP-C
Used to coordinate the establishment of SAE
bearers within the EPC
SAE bearer setup can be started by the MME
(default SAE bearer) or by the PDN Gateway.
Mainly used to transfer user packet data between PDN GW
and Serving GW
Signaling on S5/S8 is used to setup the associated bearer
resources
S5/S8 can be implemented either by reuse of the GTP
S5/S8 GTP Candidates
(Control and User Plane)
IP
L1/L2
S5/S8 IETF Candidates
p y
protocol from 2G/3G or by using Mobile IPv6 with some
IETF enhancements.
Serving
Gateway
PDN
Gateway
Sgi
User PDUs
GTP-U
UDP
GTP-C
TR 29.801
User PDUs
MIPv6
Tunneling
Layer
PMIPv6
IPv6
PDN
Sgi
UDP
IP
L1/L2
y Layer
IPv4/IPv6
L1/L2
IPv4
IPv6
www.cert.nat.tn
21
TS 23.401 / TR 29.801 TS 23.402 / TR 29.801
NetworkArchitecture
S7&SGi Intefaces
PCRF
S7 (Control Plane)
??
S7
Interface between PDN GW and PCRF
(Policy and Charging Rule Function)
SGi
(User Plane)
??
IP
L1/L2
It allows:
the PCRF to request the setup of a SAE
bearer with appropriate QoS
allows the PDN GWto ask for the QoS of
PDN
Gateway
IMS/PDN
Application
UDP or TCP UDP or TCP
IPv4/IPv6
TR 23.401
allows the PDN GW to ask for the QoS of
an SAE bearer to setup
to indicate EPC status changes to the
PCRF to apply a new policy rule.
SGi
Interface usedby the PDN GWto sendandreceive data to
Gateway
L1/L2
Interface used by the PDN GW to send and receive data to
and from the external data network
It is typically either IPv4 or IPv6 based
Downlink data coming from the external PDN must be
assignedto the right SAE bearer of the right user by analysis assigned to the right SAE bearer of the right user by analysis
of the incoming packets IP addresses, port numbers, etc.
This interface corresponds to the Gi interface in 2G/3G
networks
www.cert.nat.tn
22
NetworkArchitecture
Rx+Interface
Rx+
(Control Plane)
S7
??
PCRF
??
IP
L1/L2
SGi
TR 23.203
R +
PDN
Gateway
PDN
Rx+
Interface between PCRF(Policy & Charging Rules Function) and the external PDN
network/operators IMS
Standardized in 3GPP TS 23 203
www.cert.nat.tn
23
Standardized in 3GPP TS 23.203.
NetworkArchitecture
SAE/LTEInterworkingwith2G/3GNetworks
SGSN
I PS
GERAN
Gb
Gr
GGSN
Gn
PDN
Gi
HSS
S3
UTRAN
Iu-PS
S4
MME
S6a
S7
NB
LTE-UE
S1-U
S11
S1-MME
PDN
PCRF
S7
Rx+
SGi S5/S8
eNB
cell
Evolved UTRAN (E UTRAN)
Serving
Gateway
PDN
Gateway
PDN cell
LTE-
Uu
www.cert.nat.tn
24
NetworkArchitecture
S4
(U Pl )
S3
S3&S4Interfaces
(User Plane)
S3
(Control Plane)
UDP
GTP-C
GTP-U
User PDUs
SGSN
UDP
IP
L1/L2
UDP
IP
L1/L2
MME
Serving
Gateway
TR 29.801 / TS 23.401
TR 29.801 / TS 23.401
MME Gateway
S3/S4
Interfaces between EPC and 2G/3G packet switched core network domain
They would allow inter-system changes between SAE and 2G/3G ey oud a o te syste c a ges bet ee S a d G/3G
The S3 is a pure signalling interface used to coordinate the inter-system change between MME and SGSN
The S4 is the user plane interface and it is located between SGSN and Serving SAE GW.
This would allow to either forward packet data from EUTRAN via Serving SAE GW to SGSN (and then to
GGSN) f 2G/3G RAN t SGSN t S i SAE GWt PDN GW
www.cert.nat.tn
25
GGSN) or from 2G/3G RAN to SGSN to Serving SAE GW to PDN GW.
NetworkArchitecture
SAE/LTEInterworkingwith3G Alternative
SGSN GERAN
Gb
Gr
GGSN
Gn
PDN
Gi
HSS
S3 S4
UTRAN
Iu-PS
Gr
Direct Tunnels from
ServingGWto RNC
MME
S6a
S12
Serving GW to RNC
(User Plane)
MME
S1 U
S11
S1-MME
PCRF
S7
Rx+
SGi S5/S8
eNB
Serving
Gateway
S1-U
PDN
Gateway
PDN
SGi S5/S8
cell
LTE-Uu
www.cert.nat.tn
26
NetworkArchitecture
S12Interface
S12
GTP-U
User PDUs
S12
(User Plane)
Serving
Gateway
UDP
IP
L1/L2
UTRAN
S12
InterfacesbetweenEPCand3GRadioaccessnetwork
It ld ll i t t h b t SAE d 3G
TR 29.801 / TS 23.401
ItwouldallowintersystemchangesbetweenSAEand3G
TheS12istheuserplaneinterfaceusedfortunnelinguserdatadirectlybetweentheServingSAEGW
andtheUTRAN.
This would allow to forward packet data from 3G RAN to Serving SAE GW to PDN GW Thiswouldallowtoforwardpacketdatafrom3GRANtoServingSAEGWtoPDNGW.
ItisbasedontheGninterfacebetweentheSGSNandtheGGSNandsousestheGTPUprotocol.
www.cert.nat.tn
27
NetworkArchitecture
LTE/SAERoamingArchitecture Case1
PCRF
Rx+
HSS
Home PLMN
PDN
Gateway
IMS/PDN
PCRF
S7
SGi
Case 1:
S8
S6a
hPLMN
Visited PLMN
vPLMN
Case 1:
Home Routed Traffic
By connecting Serving GW
in vPLMN to PDN GW in
MME
S11
S1-MME
eNB
vPLMN
hPLMN
GTP tunnel and MIPv6
options over the S8
interface
Serving
Gateway
S1-U
cell
LTE-Uu
interface
Also called Remote
Breakout.
EvolvedUTRAN (E-UTRAN)
www.cert.nat.tn
28
NetworkArchitecture
LTE/SAERoamingArchitecture Case2
Case 2: Local Breakout Case 2: Local Breakout
UE can access the PDN network directly from the
vPLMN rather than traffic being routed through the
hPLMN. Breakout should depend on the service:
i e :internet accesslocal breakout
HSS
Home PLMN
i.e.:internet accesslocal breakout
i.e.:access to corporate VPNremote breakout
S9: PCRF-to-PCRF interface: roaming controlled
by hPLMN policies
Home PLMN
hPLMN
hPCRF
S6a Visited PLMN
vPLMN
S9
MME
S
S11
S1-MME
eNB
vPCRF
S7
Rx+
SGi
S5
Serving
Gateway
S1-U
cell
LTE-Uu
PDN
Gateway
IMS/PDN
SGi
S5
www.cert.nat.tn
29
NetworkArchitecture
S9Interface
??
S9
(Control Plane)
??
IP
??
hPCRF
vPCRF
IP
L1/L2
TR 29 801/ TS 23 401???????
S9
InterfacesbetweenthehPCRFandthevPCRFusedinroamingcases.
TR 29.801 / TS 23.401???????
ItisusedenforcementintheVPLMNofdynamiccontrolpolicesfromtheHPLMN.
www.cert.nat.tn
30
NetworkArchitecture
LTE/SAEInterworking with Non3GPPAccess
EvolvedUTRAN (E UTRAN)
HSS
eNB
MME
S6a
S1 U
S1-MME
PCRF
S7
Rx+
cell
LTE-Uu
Common GW for all accesses
Generic support for any non-3GPP access
Serving
Gateway
S1-U
S11
PDN
Gateway
PDN
SGi S5
SAE
G t (e.g. WLAN, Fixed)
Session Mobility using Mobile IP
Policy control supported for non-3GPP
accesses
A th ti ti f 3GPP
Gateway Gateway
Gateway
S2
Access authentication for non-3GPP
accesses using Authentication,
Authorization and accounting (AAA)
mechanisms
Security support for non-trusted accesses
Non-3GPP Access:
WiMAx, WLAN, Fixed,.
www.cert.nat.tn
31
y pp
NetworkArchitecture
AccountingandCharginginSAE/LTENetworks
ItwillbeanevolutionofthePSDomaincharging
mechanismsforGPRSandUMTS
Itwillfacilitateseamlessinterworkingwithlegacy
chargingsystems.
The charging filter rules are provided by the Policy ThechargingfilterrulesareprovidedbythePolicy
andChargingRuleFunction(PCRF).
TheIMSChargingFunctionprovidesinformation
about the users session (e g call control abouttheuser ssession(e.g.callcontrol,
multimedia,services).
TheApplicationChargingFunctionprovides
f b h f h ff informationaboutthecontentoftheuserstraffic
(e.g.URL,fileormediastreamname).
www.cert.nat.tn
32
NetworkArchitecture
Factorsaffectingthepriceofausersession
Usagetimeorduration.
Transferreddatavolume
Numberofevents(units)
Destinationofsession
Locationandtimezoneofsession
origination
QualityofService(QoS) Q y (Q )
RadioAccessTechnology(RAT,e.g.LTE
and3G/2Ginthecaseofhandover,
non 3GPP access) non3GPPaccess)
TariffTime
Useridentification
www.cert.nat.tn
33
NetworkArchitecture
Thanks for your Attention Thanks foryour Attention
www.cert.nat.tn
34
NetworkArchitecture

Doc5-LTE Workshop TUN Session4 Network Architecture

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Doc5-LTE Workshop TUN Session4 Network Architecture

Uploaded by

Copyright:

Available Formats

ITU/BDT Arab Regional Workshop on 4G Wireless Systems -Tunisia 2010

/ b l k h ITU/BDTArab Regional Workshopon

You might also like