Download PPT Version

NETLMM Applicability Draft
(Summary)
28 Sep. 2006
Purpose of the Draft
• General
– The initial purpose is to provide the applicability
analysis for WG which makes base protocol
standardization be easier
• Illustrate how NETLMM works under a MN-AR IF, i.e. LTE
access
– The draft aims to illustrate the NETLMM applicability
to the “current” 3GPP SAE architecture
• clarify what parameters are required to activate NETLMM
routing path establishment/modify/delete
• Notes
– May need to update the detail when some key points
for NETLMM applicability, e.g. detail handover
signaling flow, has been fixed
Table of Contents
1.
2.
3.
Introduction
Terminology
Overview of the 3GPP SAE/LTE network
3.1. Simplified SAE Network Architecture
3.2. Network Attachment
3.3. Inter MME/UPE Mobility within the LTE access system
4.
NETLMM Application for SAE network with LTE access system
4.1. NETLMM function entity configuration
4.2. Network Attachment with NETLMM
4.3. Inter UPE mobility by NETLMM
5.
6.
7.
8.
Conclusion
Security Considerations
Acknowledgements
References
*ID management would be described
3.1. SAE Network Architecture for
Mobility Management
Base Line Architecture Figure
HSS
S5a
Evolved RAN
S1
MME
UPE
S5b
3GPP
Anchor
SAE
Anchor
S6
SGi
LTE Anchor*
Evolved Packet Core
• Architecture figure is focused on LTE access accommodation
• MME/UPE is assumed to be logically separated, but for now we
regard they are physically collocated.
• In the document, only single anchor will be illustrated in stead of
3GPP anchor and SAE anchor, i.e. LTE anchor
– Note that LTE anchor is a non-standard term and used only for
explanation purpose in this draft.
Op.
IP
Serv.
(IMS,
PSS,
etc…)
GPRS ID management
• At GGSN,
– GGSN located at home network, except the case of
local breakout
– GGSN maintains IMSI as a key for PDP context at
GGSN
• At SGSN,
– SGSN located at visited network
– SGSN allocates TMSI created from IMSI
• TMSI needs to be updated every time SGSN changes
(P-TMSI Reallocation Procedure between SGSN and MN)
– SGSN maintains IMSI as the main reference key for
PDP context at SGSN
IMSI is used as the main key for PDP context at both GSGN and SGSN
SAE ID management
(under discussion)
• At MME,
– Authentication, authorization (PLMN, TA) and key
management;
• Working With HSS
– Ciphering/integrity termination for signaling;
• S1 C-Plan termination
• S1 U-Plan tunnel termination
– (L2 tunnel  L3 tunnel)
– Management and allocation of temporary user
identities;
• TMSI like identifier allocation, similar to SGSN
IMSI would be necessary to handle the mobility between MME/UPEs
 IMSI seems to be a appropriate identifier for NETLMM used for S5 IF
Figure in TR23.882
Network Attachment
S6
HSS
S1
UE
X?
eNB
MME/UPE
IASA
S5/S8
1. Attach Request (APN)
2. Authentication
3. Update Location
4. Insert Subscriber Data
FFS whether radio bearer
setup during attach or when
needed for data transfer
5. Insert Subscriber Data Ack
6. Update Location Ack
7. Route Update/Bearer Request
9. Route Update response/Bearer Response
11. RRC (radio resource
info, QoS info)
10. Radio Bearer Request (QoS, RRC keys)
8. PCRF Interaction
Application of NETLMM signaling
(Location Reg/Ack)
12. Attach Accept (IP configuration)
13. Attach Complete
• This procedure is under discussion (one of the alternatives)
• But step 7 and 9, target of NETLMM, exists for every alternatives
• Subscriber data transactions with HSS (step4,5) can be combined with steps 3,6
Figure in TR23.882
Inter MME/UPE Mobility within the
LTE access system
eNB 1
MME/UPE
1
S1
Sx
UE
eNB 2
S1
S5/S8
MME/UPE
2
IASA
1. IP bearer service
2. Handover Initiation
UE in ACTIVE mode
3. Handover Required (UE eNB context, eNB2 id)
4. Handover Required (UE eNB context,
eNB2 id, UE MM/SM Context)
5. Handover Request with eNB2 (UE eNB context)
Bearer path established between eNB2 and UPE2
6. Handover Response
7. Means to minimize loss of
data
Parameters Exchange
(Network Attachment)
S6
S1
UE
X?
eNB
HSS
MME/UPE
IASA
S5/S8
NM ID for NETLMM
1. Attach Request (APN)
2. Authentication (IMSI, TMSI)
Could be in step 4
3. Update Location
4. Insert Subscriber Data
FFS whether radio bearer
setup during attach or when
needed for data transfer
5. Insert Subscriber Data Ack
6. Update Location Ack (APN, IASA address, MN prefix)
7. Route Update/Bearer Request (IMSI, MME/UPE address,
(NETLMM Location Reg)
IASA address, MN prefix)
9. Route Update response/Bearer Response
(NETLMM Location Reg Ack)
11. RRC (radio resource
info, QoS info)
10. Radio Bearer Request (QoS, RRC keys)
8. PCRF Interaction
(IMSI, MME/UPE address,
IASA address)
12. Attach Accept (IP configuration)
13. Attach Complete
• IMSI is assumed to be MN ID for NETLMM
• In above, MN prefix is provided by HSS
• IASA may provide MN prefix, but then APN info shall be sent in NETLMM message
Parameters Exchange
(Inter MME/UPE Mobility within the LTE
access system)
eNB 1
MME/UPE
1
S1
Sx
UE
eNB 2
S1
S5/S8
MME/UPE
2
IASA
1. IP bearer service
2. Handover Initiation
UE in ACTIVE mode
MME/UPE can find MN context including MN ID (IMSI) by info in step3
3. Handover Required (UE eNB context, eNB2 id)
4. Handover Required (UE eNB context,
eNB2 id, UE MM/SM Context)
(IMSI, IASA address, MN Prefix)
5. Handover Request with eNB2 (UE eNB context)
Bearer path established between eNB2 and UPE2
6. Handover Response
7. Means to minimize loss of
data
Bearer Management in 3G
(discussion for multiple Prefix to a MN ID)
28 Sep. 2006
What is done in GPRS
• MS can initiate the activation, modification, and
deactivation functions at any time for a PDP context
• MN can have multiple PDP contexts, for instance,
– Register IMS for VoIP (the bearer for VoIP call with IP-1)
– MN starts web access (establish new bearer to access PDN-A
with IP-2)
– Connects to corporate network (establish new bearer to access
PDN-B, corporate network, with IP-3)
It is possible MN to establish PDP context,
similar to NETLMM tunnel, upon necessary
Bearer Management in SAE
• SAE is working on multiple PDN access
– Same as what can be done in GPRS
• The solution is under discussion
– IASA may connect to multiple PDN
• For NETLMM, it means different prefixes are allocated to a
single MN
– Similar to GPRS, it would be required to activate,
modify, and deactivate a connection to PDN for
efficient network resource usage
• Some connection, such as default bearer, would be kept as
long as the MN is attached to the network.
Considering the applicability, it is necessary function to establish,
modity, and delete one NETLMM tunnel form multiple ones