Wifiandpacketcoreintegration Lg 130227043656 Phpapp02

7/28/2019 Wifiandpacketcoreintegration Lg 130227043656 Phpapp02

1/43

Wi-Fi & packetcoreintegration

Kwangwon Kim

Technology research and StandardizationEricsson-LG


2/43

Public | 2012-10-19 | Page 1

Contents

Drivers

Evolution of I-WLAN Integration of Non-3GPP IP access technology with EPC BBAI HS 2.0/Wi-Fi CERTIFIED Passpoint SAMOG & Rel-12 Conclusion


3/43

Public | 2012-10-19 | Page 2

Drivers


4/43

Public | 2012-10-19 | Page 3

Requirements those we will face

Connectivity will be the performance bottleneck and

differentiator in the world of cloud services on mobiledevices. Within 10 years, we predict to see:

X10

devices

X100Service

offerings

X1000

capacity

This requires a new way of building a network =

Heterogeneous Network


5/43

Public | 2012-10-19 | Page 4

Its about end userexperience

Providing connectivity to support individuals creativity

and promote socio-economy

Coverage Capacity

Speed

Low latency

Always on

Coverage is taken for granted

But is bitrate

dependent

Data and voice volume capacity

to serve all subscribers

Cell edge performance

User experienceSignaling capacity

everywhere


6/43Public | 2012-10-19 | Page 5

Network

architecture

Leverage proven macro functionality

Advanced radio coordination Network integrated carrier grade Wi-Fi

CTRL

mRBS pRBS

Wi-Fi

Macro

RBSRRU

MainUnit

mRRU

RRU

Internet

grade pRBS

Iub/S1/X2

Iub/S1/X2


7/43Public | 2012-10-19 | Page 6

Evolution of I-WLAN


8/43Public | 2012-10-19 | Page 7

High level

requirements

3GPP began to speak of inter-working with wireless LAN in Rel-6

6 inter-working scenarios with 3GPP cellular networks are agreedCommon billing, Common customer care

3GPP system based access control, 3GPP system

based access charging

Access to 3GPP system PS based services from WLAN

Service continuity

Seamless service

Access to 3GPP system CS based services with

seamless mobility


9/43Public | 2012-10-19 | Page 8

Network reference

model

3GPP system basedauthentication andaccounting

UE: UICC/NAI

Roaming architecture

W-APN, Local IP & Remote

IP

Ww

3GPP Home Network

WLAN Access Network

WLAN

UE

Packet Data

Gateway

HSS

HLR

OfflineCharging

System

OCS

D'/G

r'Wf

Wo

Intranet / Internet

3GPP Visited Network

3GPP AAA

Proxy

Offline

Charging

System

WAGWn

Wa

Wf

Wd

Wp

Wm

Wi

Wx

WLAN3GPPIPAccess

Wg

Wu

Dw

3GPP AAA

Server

SLF

Wy

Wz

Roaming reference model -

3GPP PS based services provided via the

3GPP Home Network, TS23.234


10/43

Public | 2012-10-19 | Page 9

Mobility support

before EPS

Mobility between 3GPP access network and I-WLAN before EPS (TS23.327)

(FS_SM3GWLAN)

Requested by a couple of European operators (T-Mobile, Orange, Telenor,...)

Unclear standardization timeline of TS23.402

Considering legacy 3GPP system and I-WLAN architecture, DSMIPv6 was

selected as a mobility protocol

HSS3GPP AAA

Server

PDG/AR

WLAN

Access Network

UE HAExternal

PDN

Wn WpWAG

H3

H2

Wx

H1 HGi

WwWu

GERAN/UTRAN

Uu/Um

GGSN/AR

Iu_ps/Gb GnSGSN

H3

Home Mobility Service Architecture for I-WLAN Mobility

, TS23.327


11/43

Public | 2012-10-19 | Page 10

Integration of Non-3GPPIP access technology

with EPC


12/43

Public | 2012-10-19 | Page 11

Trusted vs.

Non-trusted

Recent LS from GSMA to 3GPP regarding how to define trusted and non-

trusted access technology

provides the opportunity to share the definition of

technology between SDOs

Also, Wi-Fi

alliance will allow 3GPP to access their internal specification

regarding

Hotspot 2.0/NGH to be aligned with 3GPP specifications

In TS23.402 4.3.1.2.,

Trusted and Untrusted

Non-3GPP access network

are

described as followings:

Trusted and Untrusted

Non-3GPP Access Network are IP access networks that use

access technology whose specification is out of the scope of 3GPP.

Whether a Non-3GPP IP access network is Trusted or Untrusted

is not a

characteristics

of the access network In non-roaming scenario it is the HPLMN's

operator decision if a Non-3GPP IP access network is used as Trusted or Untrusted

Non-3GPP Access Network.

In roaming scenario, the HSS/3GPP AAA Server in HPLMN makes the final decisionof whether a Non-3GPP IP access network is used as Trusted or Untrusted

non-

3GPP Access Network. The HSS/3GPP AAA Server may take the VPLMN's policy

and capability returned from the 3GPP AAA Proxy or roaming agreement

into

account.


13/43

Public | 2012-10-19 | Page 12

PMIPv6/GTPv2 vs.

DSMIPv6

SGSNS-GW

GGSNP-GW

MAG(S-GW)

LMA(P-GW)

HA(P-GW)

1.Router solicitation

(MN-ID)

2.PBU

(MN-ID,MAG1,Reg)

3. MN-ID@MAG1

4. MN-ID@MAG1, HNP

5.PBA

(MN-ID,HNP)6.Bi-directional tunnel

7.Router Advertisement

(MN-ID, HNP)

1.L3 Trigger

(MN-ID)

3. MN-ID SGSN(S-GW) @

4. Determine MNs L3 Address

5.Create Session

Response (MN-ID,

L3 Address)

6.GTP tunnel

2.Create Session

Request

(MN-ID,S-GW)

7.L3 Address

Configuration

Acquire/Configure CoA

Finding HA

Pre-loaded

DNS look-up

DSMIPv6 bootstrapping

Security

IKEv2 Auth

Home network @

Signaling

Binding update Binding update

Acknowledge


14/43

Public | 2012-10-19 | Page 13

PMIPv6 via S2b

S2b based mobility

Employs IPsec

between UE and ePDG

Requires network based mobility between ePDG

and EPC, GTP or PMIP

PDN-GW as anchor for Mobile Access and IP Fixed Access


15/43

Public | 2012-10-19 | Page 14

DSMIPv6 via S2c

S2c based mobility

DSMIPv6 between UE and PDN GW

Works with both Untrusted

and trusted non-3GPP access



16/43

Public | 2012-10-19 | Page 15

GTP/PMIPv6 via S2a

S2a based mobility

S2a integration between BNG and EPC, GTP or PMIP



17/43

Public | 2012-10-19 | Page 16

multiple access PDNconnectivity

Studied under working item MAPIM (TR23.861) and specified in TS23.402

Enables establishment of PDN connections (different APNs) over multiple

accesses

Support PDN connection level (APN level) hand-over to different access

network

Selective transfer of PDN connections between accesses

Transfer of all PDN connections out of a certain access

Able to utilize all EPS MM protocol e.g. PMIPv6, DSMIPv6 and GTP

PGW

SGW

ePDG

PDN #1

PDN #2

APN #1

APN #2

3GPP Access

Non-3GPP

Access


18/43

Public | 2012-10-19 | Page 17

IP Flow mobility

Support more flexible and ramified traffic flow handling than MAPCON

Enables establishment of multiple IP flows with same APN over multiple

accesses

Support different access network connection although the same APN is used(the same PDN)

The base granularity for mobility and offloading is IP flow e.g.

5 tuple, not PDN

connectivity level

Currently based on only DSMIPv6 (RFC5555) and complementary, specified inTS 23.261

PGW

SGW

ePDG

IP flow #1

IP flow #2

3GPP Access

Non-3GPP

Access

Same PDN

HA


19/43

Public | 2012-10-19 | Page 18

IP Flow mobility

Simplicity of network support mobility increases burdens of each

end node

P-GW (Home agent)/ UE (Mobile node)

HA

IP

HA

IP

1: (HoA1, CoA1, BID1,x)

2: (HoA2, CoA2, BID2,y)

3:

1: (HoA1, CoA1, BID1,x)

2: (HoA2, CoA2, BID2,y)

3:

1: (HoA1, CoA1, BID1,x,FID1,a,RF1)2: (HoA1, CoA1, BID1,x,FID2,b,RF2)3: (HoA2, CoA2, BID2,y,FID3,,)

4:

1: (HoA1, CoA1, BID1,x,FID1,a,RF1)

2: (HoA1, CoA1, BID1,x,FID2,b,RF2)

3: (HoA2, CoA2, BID2,y,FID3,,)

4:

ePDG/IPSEC

ePDG/IPSEC

UE ePDG EUTRAN PDNGWHSS/

AAAPCRF

IP-in-IP tunnel ( in case of standalone HA and dedicated home prefix)

IPSec tunnel with IKEv2 signaling

LTE bearer assignment as per TR23.401

DSMIPv6 bootstrapping & Binding update over LTE

DSMIPv6 bootstrapping & Binding update over Wi-Fi

Wi-Fi

connection preparation as per TR 23.402

IPSec tunnel DSMIPv6 tunnel

Exchange of routing filter, update of binding cache & IP-CAN modification




20/43

Public | 2012-10-19 | Page 19

NON-SEAMLESS

OFFLOADING

Optional capability of a UE supporting WLAN radio access in addition to 3GPPradio access.

Route specific IP flows via the WLAN access without traversing the EPC Non seamless offloaded IP flows are identified:

User preferences

The Local Operating Environment Information defined in TS

23.261

Statistically pre-configured or dynamically provided by ANDSF offloading policies Uses the local IP address allocated by the WLAN access network and no IPaddress preservation is provided between WLAN and 3GPP accesses

PGWSGW

ePDG

IP flow via EPC3GPP Access

Non-3GPP

AccessNon-seamlessly

offloaded traffic


21/43

Public | 2012-10-19 | Page 20

Non-3GPP Access

INTEGRATION

3GPP have developed I-WLAN architecture to allow wireless LAN to access

packet core network & services

Initially focused on core network access using WLAN

Developed to support data offloading

R6/7

3GPP-WLAN Inter-

working scenario

I-WLAN architecture

Access control, billingand service based on

3GPP framework

R8/9

I-WLAN seamless

handover and service

continuity support

I-WLAN mobilitysupport withUTRAN/GERAN overpre-EPS network

R10/11

Multiple access

connectivity

IP flow mobility

(IFOM) & seamless

offloading

Non-seamless WLANoffloading

BBF inter-working

S2a mobility based

on GTP & WLAN


22/43

Public | 2012-10-19 | Page 21

BBAI(Broad band access interworking)


23/43

Public | 2012-10-19 | Page 22

Motivation & Issues

3GPP and Broadband forum agreed the base service scenario and corresponding requirements

Network, PCC and QoS

interworking

architecture

Part of works were standardized in Rel11 (3GPP)

Protocol options for integration

S2b or S2c

Wi-Fi

or H(e)NB

Procedures considerations for each protocol option

Initial attach

Detach

-

UE/GW initiated or HSS/AAA initiated

Network initiated dynamic PCC

-

EPC-routed or NSWOed

traffic

Handover

Additional PDN

Network initiated resource allocation deactivation

Security

Policy & QoS

Interworking

3GPP PCC to Fixed broadband access interworking

QoS

procedures to map QoS

identifier

QCI and DSCP

Authentication & security procedure interworking


24/43

Public | 2012-10-19 | Page 23

Wi-Fi accessarchitectureEvolved Packet System

HSS

PCRF

PDN

Gateway

ePDG

Serving

Gateway

BBF AAA

Proxy

BPCF

BNG/BRAS

AN (e.g.

DSLAM/ONT)

RG

WiFi

AP

BBF

Device

UE

3GPP

Access

S6a

Gxc

S5

S2c

Gx

Gxb*

SWm

Swx

SWaSWn

3GPP AAA

Server

Operators IP

Services

(e.g. IMS, PSS etc.)

Rx

S6bS9a

BBF Defined Access and network

Customer PremisesNetwork

SGi

S2c

Non-Roaming Architecture

for untrusted

fixed broad bad access, TS23.139


25/43

Public | 2012-10-19 | Page 24

H(e)NB accessarchitecture

ServingGateway

S10

S1-U

S1-MME

SeGW

HeNB GW

HNB GW

S9a

BPCFBBF defined access and network

PDNGateway

Operator's IP

(e.g. IMS, PSSServices

SGiS5

Gx

RxGxc (Only for PMIPbased S5)

PCRF

HSS

S6a

Evolved Packet System

MSC Iu-CS

Iu-PSS15

UTRAN

GERAN

E-UTRAN

MME

BBF Device3GPPFemto

RG Customer Premise Network

BRAS/BNG

AN (e.g

DSLAM/ONT)

SGSN

S4

Non-Roaming Architecture, TS23.139


26/43

Public | 2012-10-19 | Page 25

HS 2.0/Wi-Fi CERTIFIEDPasspoint


27/43

Public | 2012-10-19 | Page 26

Motivation

Technology segmentation increases as much as Wi-Fi

access is getting

popular

MAC based, user name and password based... Interoperability and roaming issues

Global roaming like 3G brings up new business opportunity

In 2010, Hotspot 2.0 Task groups in Wi-Fi

Alliance was formed

Common set of standards to improve end user hotspot experience

Source: Driving next generation

Wi-Fi experience,

Tiago Rodrigues ,Wi-Fi global congress 2012


28/43

Public | 2012-10-19 | Page 27

HS 2.0

Specifies capabilities and requirements as per AP and mobile device

Minimal set of capabilities for APs

and mobile devices

WPA2, User credentials, Interworking information element including Venue info andHESSID field

Roaming consortium information element

BSS load element (Mobile device population and channel utilization)

Operators and service providers are specified separately Operators: responsible for the configuration and operation of the hotspot

Service providers: providing a service as a business

Selective ANQP elements

Info. about authentication and roaming including cellular operators

HS 2.0 ANQP elements

Details about operators and WAN link attributes


29/43

Public | 2012-10-19 | Page 28

Wi-Fi CERTIFIEDPasspoint

WBA announced commercial

standardization plan of Wi-Fi CERTIFIED Passpoint program

In Wi-Fi

global congress 2012 Seoul

Mainly focused on the expansion ofWi-Fi hotspot coverage based on the

roaming agreement between different

local/global MNOs

Major underlying technologies

IEEE 802.11u,IEEE 802.11i and EAP

based authenticationBenefit of Wi-Fi

CERTIFIED Passpoint


30/43

Public | 2012-10-19 | Page 29

Network discovery

and selection

Client devices discover and automatically choose networks based on user preferences,provisioned operator policy, and network availability based on IEEE 802.11u

Improve the ability of devices to discover, authenticate, and use nearby Wi-Fi

access

points

Newly introduced SSPN (Subscription service provider networks) concept

Multiple service provider IDs available on the same Aps

Roaming consortium OI (Organization ID)

A roaming consortium is a group of subscription service providers (SSPs) having inter-SSProaming agreements

GAS (Generic advertisement service) in public action frame convey ANQP (Access NetworkQuery Protocol)

ANQP is used to transport information about access network e.g. location, cellular network info.,emergency service and authentication realm

Main extensions to Beacon/Probe/Association messagesInterworking CommentsAdvertising Protocol Identifying a particular advertisement protocol supported. e.g. ANQP or 802.21

Roaming Consortium Identifying roaming consortium and/or SSP authorized to provide accessibility on the AP

QoS

Map Support for the QoS

service

SSPN Interface Indication whether the AP supports an interface to SSPNs


31/43

Public | 2012-10-19 | Page 30

Seamless Network

Access

Traditional Wi-Fi

hotspot access requires an active selection or input from the

subscriber

Manual input of valid credential information in the Web authentication portal

SSID identification by end user

Established security association is usually stored only specific

AP, not managed

central way henceforth, traditional Wi-Fi

authentication produces service discontinuity

and user intervention

The purpose of seamless network access is to remove all complicatedprocedures to establish Wi-Fi

client configuration

No need of user management for Wi-Fi

access/authentication

More preferred option for MNOs: Subscriber identity module based Username/password combinations are also considered for non-MNO Wi-Fi

service

providers

No end-user intervention is required in order to establish a connection

to a trusted

network


32/43

Public | 2012-10-19 | Page 31

SaMOG(S2a Mobility based On GTP & WLAN access to EPC)


33/43

Public | 2012-10-19 | Page 32

Motivation

Existing overlay solution for Wi-Fi

access do not lead to market uptake

IPsec/IKEv2 based client towards TTG/ePDG

DSMIPv6 based client towards PGW CMIPv4 based client towards a standalone HA

GBA-based authentication for HTTP based services

It's all about user experience

Also it heavily impacts to the terminal design

Rising of Wi-Fi

technology to complement operators' MBB offerings

GSMA Wi-Fi

roaming task force pushes each SDOs

Very useful/economical toolset for offloading

More pragmatic approach is required

Integrated operators begin to consider the 3GPP compatibility of

new Wi-Fi

technology e.g. WPA2 and UICC based credential info, authentication


34/43

Public | 2012-10-19 | Page 33

SAMOG Study on S2a Mobility based on GTP & WLAN access to EPC

Part of BBF inter-working activitiesbetween 3GPP and Broadband

forum

Solution to provide the ease ofWLAN access to EPC

Complicated authentication and

security overhead of WLAN interworking have been obstacles of large-scale I-WLAN deployment

IPSec, IKEv2 to encrypt andauthenticate WLAN via ePDG

Increased security, easy discovery

and set up procedure are alreadymature

802.1x/802.1i/802.1u/Hotspot 2.0

BNG (Border network gateway)interconnects trusted WLAN andPDN-GW


35/43

Public | 2012-10-19 | Page 34

Example call flow Additional PDN

USIM-based authentication via communication with the HSS

No need to be aware of complicated user credential such as ID/password

Converged policy control, where a policy controller can provide both fixed and

mobile policy control

The same PCC rule can be installed in the fixed access with single point of control

Full mobile-service availability regardless of access type

BNG

IP fixed access

PCRF MME S/PGWHSS

AAA

PDN #1

PDN #2

SSID: EPC-routed

SSID: NSWO

VLAN-EPC

VLAN-NSWO

LTE Access

EPC

APN 1

APN 2

1. UE establish the first PDN

connection over LTE as per

specified in TS 23.401/402/0602

2. UE detects Wi-Fi

(EPC-routed)

availability and begin to EAP

authentication procedure. AAA

downloads required data for BNG

to create GTP tunnel to PGW

upon successful authorization

4. BNG initiates GTP

tunnel creation session

3. UE triggers L3

establishment

5. PCRF installs PCC

rules except BBERF

interaction

6. PGW responds to

BNG with GTP tunnel

creation

7. UE completes

L3 establishment

with PDN#2


36/43

Public | 2012-10-19 | Page 35

ANDSF highlights

Access Network Discovery and Selection Function

Operators use the ANDSF to assist the UE to scan

and select an appropriate

access network for the establishment of an IP flow. ANDSF contains data management and control functionality necessary toprovide network discovery and selection assistance data as per

operators'

policy

Simple architecture leveraging OMA Device Management

specifications

protocol

Actually, OMA DM uses a SyncML

protocol bound to, e,g, HTTP

The SyncML

protocol carries an ANDSF Management

Object (MO), which is

encoded in XML

or WBXML.

The ANDSF can be located in the home or visited

networks (or both)

UE ANDSF

HTTP Request

HTTP Response


37/43

Public | 2012-10-19 | Page 36

Hotspot 2.0 vs.ANDSF

Created by WiFi

Alliance

HS 2.0 is independent of ANDSF but, somehow related

Defines a protocol that allows the UE to query the Access Point priorto associating with it.

The protocol is called Access Network Query

Protocol (ANQP) and is an

extension

to IEEE 802.11u.

Additionally, HS 2.0 defines policies by means of a a HS ManagementObject

The HS 2.0 MO can be sent from an ANDSF MO using OMA DM

Or it can be sent from a regular HTTP server using SOAP-XML

ANQP Request

ANQP response

AP

QoS Extension to


38/43

Public | 2012-10-19 | Page 37

QoS Extension toWi-Fi access

WMM Qos

with Admin Control on Radio

Session Rate-limit/Throttling/Queue on Core

* EDCF is fairly simple to implement, but does not guarantee bandwidth, Jitter or latency

AP

(802.11p)/DSCP

UE

PCRF

Radius CoA Gx

QoS

PGW

GTP

Per Session Rate-limit

Queue/Qos

Map to L2

802.11e WMM

EDCFBNG

Client or Clientless


39/43

Public | 2012-10-19 | Page 38

Client or Clientless

solutionCriteria Clientless Client Based (I-WLAN)Impact on UE

No impact, based on 802.1x and

available

EAP methods supported by the

device (SIM, AKA, TTLS)

Heavy impact. Requires the integration

of an IPsec

Client, IKEv2 and EAP-

SIM/AKA support

Impact on Fixed Network

Yes, requires 802.1x enabled Wifi

Access

Points on the operators SSID, AAA

supporting EAP and MAP interface

towards HLR

or DIAMETER towards

HSS. User IP packet awareness

No impact. It assumes that the

Device/User

has already managed to

acquire an access i.e. IP@ and uses it to

build the IPsec

Tunnel, No user IP packet

awareness

Impact on Mobile Network

Very low. The fixed edge could look like a

new GGSN or using S2a GTP it could

look

like a new SGSN or SGW

High. Requires to deploy a new accesstechnology

(WAG, PDG/ePDG

and AAA)

End to End QoS

Yes, using S9a

or Policy interfaces

between

Mobile and Fixed Policy

Managers, or also using GTP-C in band

signaling. Marking packets on down and

up streams

Difficult. even if IPsec

packets are marked

the fixed network could choose not to

honor

it

StandardizedYesBBF, 3GPP, WIFI ALLIANCE

(HOTSPOT 2.0)Yes3GPP

Compatible with non SIM

based

Devices

YesNon SIM Based devices are already

802.1x capable and could use any

supported EAP method e.g. EAP-TTLS orTLS

No

Ongoing Working


40/43

Public | 2012-10-19 | Page 39

Ongoing WorkingItems in Release 12

WLAN Network Selection for 3GPP Terminals (WLAN_NS)

To evaluate and if needed enhance existing 3GPP solutions for networkselection for WLAN taking into account WFA Hotspot 2.0 solutions.

The proposed work is based on existing TS 23.402 architectures.

3GPP operators policies for WLAN network selection will be provisionedon 3GPP terminals via pre-configuration or using ANDSF.

Policy and Charging Control for Supporting Fixed Broadband AccessNetworks (P4C)

Policy and Charging Control in the fixed broadband access network in the

convergent scenario where a single operator is deploying both the fixedbroadband access network and the Evolved Packet Core (EPC).


41/43

Public | 2012-10-19 | Page 40

Conclusion

Summary &


42/43

Public | 2012-10-19 | Page 41

Summary &

Conclusion Lots of technology variation emerged to integrate Wi-Fi

and 3GPP

cellular network

And

It is moving towards simplified and pragmatic approach

Driving forces of this trend are MBB penetration and User experienceRelease 8 Release 10 Release 12

Current Future

Single radio connection

NW Discovery &

Selection

Intersystem Mobility,

ANDSF

Policy

Inter-flow mobility

Multiple radio

connections

UE-driven IP flow

mobility

Network driven flowmobility

HS discovery & selection

And more

NW discovery & selection

Seamless authentication,

Wi-Fi

global roaming and

mobility

Load balancing, multi-band

steering

ANDSF policy integration

And more


43/43

Wifiandpacketcoreintegration Lg 130227043656 Phpapp02

Documents

Transcript of Wifiandpacketcoreintegration Lg 130227043656 Phpapp02