MNO Cloud Use Cases 4 to 9

Source: Rogers WirelessContact: Ed O’Leary (ed.oleary@rci.rogers.com), George Babut (gbabut@rci.rogers.com)

3GPP/SA3-LI#44 Tdoc SA3LI12_018Barcelonia, 17 Jan– 19 Jan 2012

Introduction

• This document provides additional use cases• Refer to documents Tdoc SA3LI11_103 Tdoc

SA3LI11_104, SA3LI11_115 and SA3LI11_116 for background material

List of Potential Cloud Use Cases relevant to LI Work

• Use Case 1: Filing Sharing Service with single MNO• Use Case 2: MNO uses a Cloud server

– Use Case 2a: MNO uses a Cloud server that provides redirection• Use Case 3: The MNO hosts a cloud in its network• Use Case 4: SMB or Enterprise use multiple MNO networks• Use Case 5: Same as Use Case 4, but each MNO has a Cloud Server

that proxies (extension of Use Case 2)• Use Case 6: Same as use case 6, however MNO cloud server

provides redirection (extension of Use Case 2a) to the 3rd party cloud App server

• Use case 7:Dynamic triggering (extension of use case 4) (new)• Use Case 8: SMB or Enterprise use multiple MNO with their own

Clouds (extension of Use Case 4)• Use Case 9: Enterprise extension to the cloud• Future Use Cases ; Local Break out, Femto

Use Case 4• SMB or Enterprise use 2 or more MNO for their users (licensing in a

country ie province, State or city requires 2 or more MNO to provide coverage, business reason (diversity, business continuity, costs)

• Each MNO has a white label with the same 3rd party Cloud Service (same as use case 1)– Each MNO will capture traffic for the target while they are on it’s

network.• Assume only one warrant issued against MNO where the target has a

subscription• Roaming traffic is assumed to go home in MNO to MNO IPX• Captures traffic while roaming in other regulatory domains

– Traffic while on internet cafe is not captured by the MNO• Local break out for a target roaming may not be captured either

• Each MNO may use different Keying material for secure access and storage of files (client application)

Use case 5• Same as Use case 4, but each MNO has a Cloud Server

that proxies (use case 2)– DNS

• May route to the wrong MNO Cloud Server • (users that change MNO)

• Each MNO may have initialization strings to provide the URL that resolves to the correct URI from the DNS

– Each MNO may use different Keying material for secure access and storage of files• (issue on the cloud on handling, the cloud could provide a

common key to be used, however file will look encrypted to LEA)– As MNO proxies, all is captured

• Internet cafe, LIPA and SIPTO

Use case 6

• Same as use case 5, however MNO cloud server provides redirection (use case 2a) to the 3rd party cloud App server– Keying material from each MNO may be different

when accessing the same files for different users– Each proxy may behave differently for LI–

Use case 7

• Same case Use case 4 with a dynamic trigger function in the Cloud Server– May only work if in the same regulatory domain,

(MNO and Cloud Service) – Requires Inter-Regulatory Domain agreements if

operated across domains

Use case 8

• Same as Use case 4 but supporting multiple MNO with their own Cloud– Example is MNO Cloud Services which are made available to

other MNOs• CDN, eg Mobile TV content, Media• M2M services• Financial services• File services

– Large carriers providing regional or small carriers access to service• Ie customers that roam

– Carriers providing global services to other carriers

Use case 8

• Implementation issue– Is does request bypass home cloud (via VPN)– Is the content delivered encrypted to the User via

Session key encryptions, thus providing encrypted content to LEA

– Is it handled like case 2, case 2a, or a combination

Use case 9

• Enterprise extension to the cloud– Can access the enterprise and or the cloud• Does this collapse to a vpn solution provided by the

mno?• Issue VPN / SSL usage

– Will enterprise allow Split access from vpn client?

Future Use case

• Sipto, LIPA, and femto use case required– Femto with internal cloud service/ Apps