1 SAE architecture harmonization R RAN2/3, SA2 Drafting Group

2 Architectural principle Standardized interface between MME and Serving SAE GW PDCP and user plane ciphering in eNodeB S5 interface between two different SAE GWs with different roles Chaining of S5 & S8a/b in roaming scenarios is not required. QoS model leaves as TR S1: GTP-U for user plane S2a/b: Client and Network based mobility (IETF Based) S3: GTP S4: GTP S5: GTP and IETF based mobility protocol S8: GTP and IETF based mobility protocol NAS Signalling security terminates in MME Functional allocation between MME and CN UP Node shall be standardised Idle Mode Termination is above eNB Note: Other existing agreement and assumptions are reconfirmed. Reconfirmed assumptions shall not be reopened in future meetings.

3 Non-roaming architecture (for TS ) SGi S4 S3 S1_MME PCRF S7 S6a HSS Operator’s IP Services (e.g. IMS, PSS etc.) Rx+ S10 UE GERANUTRAN SGSN “LTE-Uu” EUTRAN MME S11 S5 Serving SAE gateway PDN SAE gateway S1_U

4 Non-roaming architecture (for TS ) single SAE GW configuration (user plane optimization option) SGi S4 S3 S1_MME PCRF S7 S6a HSS Operator’s IP Services (e.g. IMS, PSS etc.) Rx+ S5 UE GERANUTRAN SGSN “LTE-Uu” EUTRAN MME S11 S1_U Serving SAE Gateway PDN SAE Gateway S10 S5

5 PDN SAE GW: –The PDN SAE GW is the SAE gateway which terminates the SGi interface towards the PDN. –For each UE associated with SAE system, there may be several PDN SAE GW’s to support multiple PDNs (if deemed required). –PDN SAE GW functions include: Policy Enforcement Per-user based packet filtering (by e.g. deep packet inspection) Charging Support User plane anchor for mobility between 3GPP access and non-3GPP access LI Serving SAE GW: –The serving SAE GW is the SAE gateway which terminates the interface towards EUTRAN. –For each UE associated with SAE system, at a given point of time, there is always a single Serving SAE GW. –Serving SAE GW functions include: the local Mobility Anchor point for inter-eNB handover Mobility anchoring for inter-3GPP mobility (terminating S4 and relaying the traffic between 2G/3G and PDN SAE GW) LI Functional split of PDN SAE GW and serving SAE GW shall be the same regardless of IETF or GTP based protocols. The PDN SAE GW and the Serving SAE GW may be implemented in one physical node or separated physical nodes.

6 MME –NAS signaling –NAS signaling security –Inter CN node signaling for mobility between 3GPP access networks (terminating S3) –Idle mode UE Tracking and Reachability –Roaming (S6a towards home HSS) –Authentication The Serving SAE GW and the MME may be implemented in one physical node or separated physical nodes. PDCP and user plane ciphering is in eNodeB. Interfaces –S1-U: per SAE bearer user plane tunneling + inter eNodeB path switching during handover –S1-MME: control plane protocol between eUTRAN and MME –S5: user plane tunneling interface between Serving SAE GW and PDN SAE GW + tunnel management protocol. It is used for 1) Serving SAE GW relocation due to UE mobility and 2) in case the serving SAE GW does not provide the required PDN connectivity. –S10: control plane interface between MME and MME –S11: interface between MME and Serving SAE GW.

7 Roaming architecture for home route traffic (for TS ) SGi S7 S6a HSS Operator’s IP Services (e.g. IMS, PSS etc.) PDN SAE gateway S8a S3 S1_MME S10 GERANUTRAN SGSN MME S11 Serving SAE gateway S1_U UE “LTE-Uu” EUTRAN S4S4 HPLMN VPLMN S8a is variant S5 for roaming (GTP based).

8 Roaming architecture for home route traffic (for TS , only about S2a/b termination aspects) non-3GPP anchor in HPLMN case SGi S6a HSS Operator’s IP Services (e.g. IMS, PSS etc.) PDN SAE gateway S8b S3 S1_MME S10 GERANUTRAN SGSN MME S11 Serving SAE gateway S1_U UE “LTE-Uu” EUTRAN S4S4 HPLMN VPLMN S2a/b Page 8 and 9 do not include any non-3GPP support aspects (e.g. PCC aspect) except termination of S2a/b, and they are described in TS

9 SGi S6a HSS Operator’s IP Services (e.g. IMS, PSS etc.) PDN SAE gateway S8b S3 S1_MME S10 GERANUTRAN SGSN MME S11 Serving SAE gateway + local non-3GPP anchor S1_U UE “LTE-Uu” EUTRAN S4S4 HPLMN VPLMN Serving SAE gateway in VPLMN for this case includes local non-3GPP anchor function. S2a/b Roaming architecture for home route traffic (for TS , only about S2a/b termination aspects) non-3GPP anchor in VPLMN case