Distributed computing, storage and radio resource allocation over cooperative femtocells

Transcription

1 Distributed computing, storage and radio resource allocation over cooperative femtocells Scenarios, system requirements and standardisation activities Josep Vidal UPC

2 Overall objectives of TROPIC To exploit the convergence of pervasive femto-network infrastructure and cloud computing paradigms for virtualisation/distribution of applications and services by investigating and developing appropriate technologies for self-organising small cell deployments evaluating the advantages in terms of spectral/energy efficiency and service effectiveness 2

3 Technical scenario Cloud applications could be burst out to the network of HeNB if these had enough computational/storage resources. Coordinated and uncoordinated management of radio/computation/storage resources in presence of MBS is needed. 3

4 Business scenarios & deployment TROPIC case Macro-cell layout Small-cell deployment TR-1 Urban Microcell scenario TR-2 Urban Macrocell scenario Dense (or urban) deployment TR-3 Suburban Macrocell scenario Suburban (or residential) deployment TR-4 No macrocell Indoor Hotspot Business Scenario 1: Corporate Customer inside Building corporate users inside an office building, daily office activities. TR-1/2 Macrocells are available, but are not able to provide enough indoors coverage Backhaul availability: corporate intranet, metro-ethernet, FTTX (GPON/GEPON). HeNBs deployments: from one to many HeNBs. UE population: medium to high FUE medium to high MUEs in the corporate building Business Scenario 2: Users in Public Places TR-2 public users inside an public building (train station, airport, mall) Macrocells are available, but are not able to provide enough indoors coverage. Backhaul availability: metro-ethernet, FTTX (GPON/GEPON). HeNB deployment: from one to many HeNBs. UE population: medium to high FUE, medium to high MUEs in the public building. Business Scenario 3: Residential Users inside their Premises TR-3/4 residential users inside their premises, supporting their daily home activities. Macrocells are available, but are not able to provide enough indoors coverage Backhaul availability: FTTX (GPON/GEPON), xdsl. HeNB Deployment: one - two HeNBs. UE Population: low FUEs, low-to-medium MUEs. 4

5 Application scenario Top Down Scenario Bottom Up scenario Reading Content Subscriber Basic flow 1. Subscriber starts content downloading 2. Small cells cloud checks data availability 3. Small cells cloud finds data in local virtualized femto storage 4. Small cells cloud returns data to subscriber 5. Data stored in the subscriber's phone Basic flow 1. Subscriber starts an application that spawns heavy load processes. 2. The application finds the mobile phone resources are not sufficient to run the processes. 3. The application scans network for nearby available small cells cloud computing capacity. 4. The application distributes some loads/processes to available small cells cloud. 5. The application receives the results from the cloud and processes it to a form required by user. 5

6 General system requirements and assumptions (1/2) Deployment scenarios and small cells cloud relevance Small cells cloud is rather neighbourhood oriented, not being directly concerned with the frequency-channel related deployment scenarios. Outdoor and indoor For indoor UE, only low UE speed (0 3km/h) is targeted. For outdoor, not only low UE speed, but also medium UE speed (up to 30km/h) and potentially higher speeds are targeted. Only indoor nomadic or fixed UEs are assumed to exploit small cells cloud services. Other UEs are considered for the purpose of investigation of radio paradigms related to the communication among UEs and enbs. Inter SCeNB communication System shall support MP2MP inter enb communication, where the enbs can be many SCeNBs and a MeNB. Deployment density In some scenarios (e.g., hotspot indoor/outdoor places, etc.), single or a few small cell node(s) are sparsely deployed. Meanwhile, in some scenarios (e.g., dense urban, large shopping mall, etc.), a lot of small cell nodes are densely deployed to support huge traffic over a relatively wide area covered by the small cell nodes. The coverage of the small cell layer is generally discontinuous between different hotspot areas. Each hotspot area can be covered by a group of small cells, i.e., a small cell cluster. 6

7 General system requirements and assumptions (2/2) Synchronization Both synchronized and un-synchronized scenarios should be considered between small cells as well as between small cells and macro cell(s). Time synchronized deployments of small cell clusters are prioritized. Frequency channel allocation Different bands for macro and small cells Co-chanel deployment scenarios Backward compatibility Backward compatibility, i.e., the possibility for legacy (pre-release 12) UEs to access a small-cell node/carrier, is desirable for small cell deployments. The introduction of nonbackwards compatible features should be justified by sufficient gains. Energy efficiency TROPIC should target lowering the energy consumption of the UEs. However, also energy efficiency of the whole network should be as high as possible, given a reasonable system complexity while considering the characteristics described above. 7

8 Architecture requirements Small Cell cloud Manager (SCM) New entity in networks that controls and manages computation at the virtual machines deployed at small cells. Functionalities of SCM: Control the placement of virtual machines (VM) across hypervisors deployed at HceNBs. Obtain the necessary information on available radio resources of small cells, backbone load, and computational load. Dynamically modify and allocate resources of VMs to individual running applications depending on their requirements such as disk size, memory space or latency. Decide where to run the application/service. Control and manage access of users to small cells cloud resources in terms of authorization to utilize the resources by a UE Backhaul requirements Broadband access network using GPON as the broadband access technologies that can accommodate bandwidth up to 2.5 Gbps. Transport network, using Metro Ethernet as the Edge network and Router as Core network. 8

9 Cloud requirements Small cells include storage and processing capabilities, several virtual machines can run on it thanks to virtualization and the network access is the air interface of this device. Small cells have to be organised in clusters or small cells cloud networks, i.e., groups of base stations under the same management framework. A cluster is an assembly of M virtualised small cells. Each cell is running up to N virtual machines (VMmn). The entity SCM organizes the deployment and execution of the application out of the information regarding the infrastructure (gathered from the VIM), the application requirements and the radio interface system. 9

10 Standardisation in TROPIC

11 TROPIC standardization objectives 1. Disseminate research results in 3GPP, ITU SG-13 and IETF 2. Influence 3GPP standardisation RAN (Radio Access Networks), for amending the relevant LTE protocols. The contributions to standardisation will be based on the research results provided by the tasks: cooperative communication (from 3A1 * ), HeNB-network coordination (from 3A2 * ), system-level architecture and other aspects (from 5A1 * ). Target: RAN1, RAN2, RAN3, RAN4? SA (Technical Specification Group - Services and System Aspects), mainly SA2 (system architecture); to disseminate the new deployment architecture and spectrum usage. The contributions to standardisation will be based on the research results provided by the task on architecture design (from 2A2 * ) * Activity code in the TROPIC workprogram 11

12 TROPIC initial activity Initial activity during Q1 1. Drafted one contribution to RAN1 2. Participation with contributions in lists on TR Scenarios and Requirements for Small Cells 3. Participation in RAN list on the future Wis, including Small Cells 4. Participation in Nov RAN1 meeting 5. Organizing support for Small Cells WI with UPC and SEQ 6. Provided RAN1 meeting Report 7. Participation in the Dec 2013 RAN meeting in Barcelona 12

13 Approved SI (Study Items) in December RAN meeting - Only those SI/WI which can start in Jan. were approved, more approvals expected in RAN meeting in Vienna - Three SIs of major TROPIC interest were already approved 1. SID: RP122032; RAN1 Leader. Acronym: FS_LTE_SC_enh_L1 Objective: to identify enhancements towards improvement of the spectrum efficiency as well as efficient small cell deployment and operation in order to meet the requirements targeted for small cell enhancements in the identified scenarios in TR36.932, and evaluate the corresponding gain, standardization impact and complexity. 13

14 Approved SIs in December RAN meeting cont. 2. SID: RP12233, RAN2 Leader; Acronym: FS_LTE_SC_enh_hilayer Objective: to identify potential technologies in the protocol and architecture for enhanced support of small cell deployment and operation which should satisfy scenarios and requirements defined in TR SID in RP ; Acronym: FS_LTE_D2D_Prox Objectives: for D2D communication 14