architectureoverviewhangout ws

Upload: lizhaohui

Post on 14-Jan-2016

212 views

Category:

Documents


0 download

DESCRIPTION

ArchitectureOverviewHangout Ws

TRANSCRIPT

Architecture#1: IoT/M2M Local Breakout

Architecture#1: IoT/M2M Local BreakoutNo UICC

eNodeBMobile BackhaulSAE-GWeNodeB

M2M Server

HSS/RegistersProvisioningOperator: NoneOthers: As per app business logic

M2M Provisioning1.1UeM2Prov1.2M2ProvM2SMobile BackhaulSAE-GWeNodeB

M2M Server

HSS/RegistersAuthenticationOperator: Radio fingerprinting to minimize fraudE2e: If required by application1.4UE-Rad1.5UEM2S1.6UEHSSMobile BackhaulSAE-GWeNodeB

M2M Server

HSS/RegistersData FlowBreakout at edge or core 1.7UE-Rad1.8UE-M21.9UE-SAEGWR 18 G 65 B 145R 0 G 201 B 255R 104G 113B 122R 216G 217B 218R 168G 187B 192Core and background colors:# Nokia Solutions and Networks 2014Architecture#2: Special HSSUICC is present; but all devices have same secret / identity?

Mobile BackhaulSAE-GWeNodeB

M2M Server

HSS/RegistersProvisioningOperator: NoneOthers: As per app business logic

M2M Provisioning2.1UeM2Prov2.2M2ProvM2S2.3M2ProvHSSMobile BackhaulSAE-GWeNodeB

M2M Server

HSS/RegistersAuthenticationOperator: 3GPPE2e: If required by application2.4UE-Rad2.5UEM2S2.6UEHSSMobile BackhaulSAE-GWeNodeB

M2M Server

HSS/RegistersData Flow3GPP 2.7UE-Rad2.8UE-M22.9UE-SAEGWR 18 G 65 B 145R 0 G 201 B 255R 104G 113B 122R 216G 217B 218R 168G 187B 192Core and background colors:# Nokia Solutions and Networks 2014Architecture#3: Third Party AuthenticationUICC not present; auth goes over eNodeB up to Weightless GW, non-3GPP security architecture offered from operator n/w, end-2-end authentication

Mobile BackhaulSAE-GWeNodeB

M2M Server

M2M GWProvisioningOperator: Trust Setup/onboarding (as M2M-2-MNO)Others: As per app business logic

M2M Provisioning3.1UeM2Prov3.2M2ProvM2SMobile BackhaulMMEeNodeB

M2M Server

M2M GW(Authentication) AuthenticationOperator: as per protocol chosenE2e: As per protocol chosen3.4UE-Rad3.5M2S-MMEMobile BackhaulSAE-GWeNodeB

M2M Server

M2M GW (Data)Data Flow3GPP 3.7UE-Rad3.8UE-M23.9UE-SAEGW3.6UE-MME3.3 M2ProvMNOR 18 G 65 B 145R 0 G 201 B 255R 104G 113B 122R 216G 217B 218R 168G 187B 192Core and background colors:# Nokia Solutions and Networks 2014Assumptions

R 18 G 65 B 145R 0 G 201 B 255R 104G 113B 122R 216G 217B 218R 168G 187B 192Core and background colors:# Nokia Solutions and Networks 2014Architecture#3: Third Party AuthenticationUICC not present; auth goes over eNodeB up to Weightless GW, non-3GPP security architecture offered from operator n/w, end-2-end authentication

Mobile BackhaulSAE-GWeNodeB

M2M Server

M2M GWProvisioningOperator: Trust Setup/onboarding (as M2M-2-MNO)Others: As per app business logic

M2M Provisioning3.1UeM2Prov3.2M2ProvM2SMobile BackhaulMMEeNodeB

M2M Server

M2M GW(Authentication) AuthenticationOperator: as per protocol chosenE2e: As per protocol chosen3.4UE-Rad3.5M2SGWMobile BackhaulSAE-GWeNodeB

M2M Server

M2M GW (Data)Data Flow3GPP 3.7UE-Rad3.8UE-M23.9UE-SAEGW3.6eNB-M2MG3.3 M2ProvMNOR 18 G 65 B 145R 0 G 201 B 255R 104G 113B 122R 216G 217B 218R 168G 187B 192Core and background colors:# Nokia Solutions and Networks 2014Architecture#4: Nokia Global IoT platform acts a MVNO/HomeNetwork UICC is present

Mobile BackhaulSAE-GWeNodeB

M2M Server

HSS/RegistersProvisioningOperator: 3GPPOthers: As per app business logic

M2M ProvisioningHomeVisited4.1UeM2Prov4.2M2ProvM2S4.3M2ProvHSSMobile BackhaulSAE-GWeNodeB

M2M Server

HSS/RegistersAuthenticationOperator: 3GPPE2e: If required by application4.4UE-Rad4.5UEM2S4.6UEHSSMobile BackhaulSAE-GWeNodeB

M2M Server

HSS/RegistersData Flow3GPP 4.7UE-Rad4.8UE-M24.9UE-SAEGWR 18 G 65 B 145R 0 G 201 B 255R 104G 113B 122R 216G 217B 218R 168G 187B 192Core and background colors:# Nokia Solutions and Networks 2014

R 18 G 65 B 145R 0 G 201 B 255R 104G 113B 122R 216G 217B 218R 168G 187B 192Core and background colors:# Nokia Solutions and Networks 2014Architecture#1: IoT/M2M Local BreakoutNo UICC

eNodeBMobile BackhaulSAE-GWeNodeB

M2M Server

HSS/RegistersProvisioningOperator: NoneOthers: As per app business logic

M2M Provisioning1.1UeM2Prov1.2M2ProvM2SArchitecture#2: Special HSSUICC is present; but all devices have same secret / identity?Mobile BackhaulSAE-GWeNodeB

M2M Server

HSS/RegistersProvisioningOperator: NoneOthers: As per app business logic

M2M Provisioning2.1UeM2Prov2.2M2ProvM2S2.3M2ProvHSSR 18 G 65 B 145R 0 G 201 B 255R 104G 113B 122R 216G 217B 218R 168G 187B 192Core and background colors:# Nokia Solutions and Networks 2014Architecture#3: Weightless like overlay UICC may be present; non-3GPP security architecture offered from operator n/w

Mobile BackhaulSAE-GWeNodeB

M2M Server

Weightless GWProvisioningOperator: one time; not per deviceOthers: As per app business logic

M2M Provisioning3.1UeM2Prov3.2M2ProvM2SArchitecture#4: Nokia Global IoT platform acts a MVNO/HomeNetwork UICC is presentMobile BackhaulSAE-GWeNodeB

M2M Server

HSS/RegistersProvisioningOperator: 3GPPOthers: As per app business logic

M2M ProvisioningHomeVisited4.1UeM2Prov4.2M2ProvM2S4.3M2ProvHSSR 18 G 65 B 145R 0 G 201 B 255R 104G 113B 122R 216G 217B 218R 168G 187B 192Core and background colors:# Nokia Solutions and Networks 2014

R 18 G 65 B 145R 0 G 201 B 255R 104G 113B 122R 216G 217B 218R 168G 187B 192Core and background colors:# Nokia Solutions and Networks 2014Architecture#1: IoT/M2M Local BreakoutNo UICC

Mobile BackhaulSAE-GWeNodeB

M2M Server

HSS/RegistersAuthenticationOperator: Radio fingerprinting to minimize fraudE2e: If required by application1.4UE-Rad1.5UEM2S1.6UEHSSArchitecture#2: Special HSSUICC is present; but all devices have same secret / identity?Mobile BackhaulSAE-GWeNodeB

M2M Server

HSS/RegistersAuthenticationOperator: 3GPPE2e: If required by application2.4UE-Rad2.5UEM2S2.6UEHSSR 18 G 65 B 145R 0 G 201 B 255R 104G 113B 122R 216G 217B 218R 168G 187B 192Core and background colors:# Nokia Solutions and Networks 2014Architecture#3: Weightless like overlay UICC may be present; non-3GPP security architecture offered from operator n/w

Mobile BackhaulSAE-GWeNodeB

M2M Server

Weightless GWAuthenticationOperator: as per protocol chosenE2e: As per protocol chosen3.4UE-Rad3.5M2SGW3.6UEGWArchitecture#4: Nokia Global IoT platform acts a MVNO/HomeNetwork UICC is presentMobile BackhaulSAE-GWeNodeB

M2M Server

HSS/RegistersAuthenticationOperator: 3GPPE2e: If required by application4.4UE-Rad4.5UEM2S4.6UEHSSR 18 G 65 B 145R 0 G 201 B 255R 104G 113B 122R 216G 217B 218R 168G 187B 192Core and background colors:# Nokia Solutions and Networks 2014

R 18 G 65 B 145R 0 G 201 B 255R 104G 113B 122R 216G 217B 218R 168G 187B 192Core and background colors:# Nokia Solutions and Networks 2014Architecture#1: IoT/M2M Local BreakoutNo UICC

Mobile BackhaulSAE-GWeNodeB

M2M Server

HSS/RegistersData FlowBreakout at edge or core 1.7UE-Rad1.8UE-M21.9UE-SAEGWArchitecture#2: Special HSSUICC is present; but all devices have same secret / identity?Mobile BackhaulSAE-GWeNodeB

M2M Server

HSS/RegistersData Flow3GPP 2.7UE-Rad2.8UE-M22.9UE-SAEGWR 18 G 65 B 145R 0 G 201 B 255R 104G 113B 122R 216G 217B 218R 168G 187B 192Core and background colors:# Nokia Solutions and Networks 2014Architecture#3: Weightless like overlay UICC may be present; non-3GPP security architecture offered from operator n/w

Mobile BackhaulSAE-GWeNodeB

M2M Server

Weightless GWData Flow3GPP 3.7UE-Rad3.8UE-M23.9UE-SAEGWArchitecture#4: Nokia Global IoT platform acts a MVNO/HomeNetwork UICC is presentMobile BackhaulSAE-GWeNodeB

M2M Server

HSS/RegistersData Flow3GPP 4.7UE-Rad4.8UE-M24.9UE-SAEGWR 18 G 65 B 145R 0 G 201 B 255R 104G 113B 122R 216G 217B 218R 168G 187B 192Core and background colors:# Nokia Solutions and Networks 2014