10.07.2015 Views

Key Scenarios and implications for WINNER II

Key Scenarios and implications for WINNER II

Key Scenarios and implications for WINNER II

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>WINNER</strong> <strong>II</strong> D6.11.2 v1.0Executive SummaryIn the previous phase of <strong>WINNER</strong>, an extensive research was done in the scope of <strong>WINNER</strong>’s scenarios<strong>and</strong> service classification through the analysis of the different inputs linked to the usage scenarios. Apreliminary economic <strong>and</strong> business framework was also started in that <strong>WINNER</strong>’s phase [WIN1D14].The goal of this document is to identify the most relevant scenarios in scope of the <strong>WINNER</strong>, chosen askey scenarios <strong>for</strong> proof-of-concept <strong>and</strong> defined by <strong>WINNER</strong> <strong>II</strong> CGs.An overview of the different <strong>WINNER</strong> scenarios <strong>and</strong> their relationships is provided in chapter 2 in orderto get a clear underst<strong>and</strong>ing of the term “scenario”. A continued discussion from <strong>WINNER</strong> phase I inscope of the service <strong>and</strong> traffic characterisation was per<strong>for</strong>med according to the latest trends in thewireless industry. Each evaluation scenario was characterised in terms of used services, trafficcharacteristics, user density, distribution <strong>and</strong> mobility modelling, <strong>and</strong> linked with the physicaldeployment <strong>and</strong> test scenarios defined by the CGs.The evaluation scenarios are prioritised in terms of the typical usage cases with relevance <strong>for</strong> <strong>WINNER</strong>evaluation in terms of the system requirements <strong>and</strong> design.An extension of the economic impact framework started in phase I is analysed at service level rather thantaking into account the value chain <strong>for</strong> the different players or actors involved. A preliminary analysis ofthe technical <strong>implications</strong> of wireless ecosystems is provided in order to evaluate the flexibility <strong>and</strong>configurability of <strong>WINNER</strong> system upon different deployment scenarios, i.e. network providers, serviceproviders, contents providers <strong>and</strong> other actors in the business models.Page 2 (41)


<strong>WINNER</strong> <strong>II</strong> D6.11.2 v1.0AuthorsPartner Name Phone / Fax / e-mailPTIN Paulo Jesus Phone: +351 234 403 386Fax: +351 234 424 160e-mail: paulo-j-jesus@ptinovacao.ptCarlos Silva e-mail: it-c-silva@ptinovacao.ptAAU Albena Mihovska Phone: +45 96358639e-mail: albena@kom.aau.dkSofoklis Kyriazakos e-mail: sk@kom.aau.dkNTUA Karamolegkos Pantelis Phone: +30 210 772 1513e-mail: karamolegos@telecom.ntua.grKaretsos George Phone: +30 210 772 1511e-mail: karetsos@cs.ntua.grCATR Yutao Zhu Phone: +86 1062304565e-mail: zhuyutao@mail.ritt.com.cnYi Wan Phone: +86 1062302483e-mail: wanyi@mail.ritt.com.cnPage 3 (41)


<strong>WINNER</strong> <strong>II</strong> D6.11.2 v1.0Table of Contents1. Introduction ................................................................................................. 72. Overview of <strong>WINNER</strong> scenarios: definitions <strong>and</strong> relationship................ 72.1 Scenario....................................................................................................................................... 92.2 User scenario ............................................................................................................................... 92.3 Usage scenario............................................................................................................................. 92.4 Location scenario......................................................................................................................... 92.5 Traffic load scenario.................................................................................................................. 102.6 Deployment scenario ................................................................................................................. 102.7 <strong>Key</strong> scenario .............................................................................................................................. 113. Services <strong>and</strong> generic applications .......................................................... 113.1 Service characteristics ............................................................................................................... 113.2 Traffic characteristics ................................................................................................................ 133.3 Communication characteristics.................................................................................................. 154. <strong>Key</strong> scenarios............................................................................................ 174.1 Scenario elements <strong>and</strong> generation methodology ....................................................................... 174.1.1 Environment type <strong>and</strong> cell size ......................................................................................... 184.1.2 Terminal type .................................................................................................................... 184.1.3 User density <strong>and</strong> traffic parameters................................................................................... 184.1.4 User mobility..................................................................................................................... 194.1.5 Mobility models ................................................................................................................ 204.1.5.1 Indoor small (office) environment mobility model................................................ 204.1.5.2 Hotspot environment mobility model .................................................................... 224.1.5.3 Outdoor to indoor (dense urban) mobility model .................................................. 224.1.5.4 Vehicular environment (typical urban) mobility model......................................... 234.1.5.5 Rural environment mobility model........................................................................ 244.1.6 Application usage..............................................................................................................244.2 Selection of key scenarios <strong>for</strong> <strong>WINNER</strong>................................................................................... 274.2.1 Scenario A (related with LA Concept Group)................................................................... 274.2.2 Scenario B (related with MA Concept Group).................................................................. 304.2.3 Scenario C (related with WA Concept Group) ................................................................. 324.2.4 Summary of Parameters <strong>for</strong> the <strong>Key</strong> <strong>Scenarios</strong>................................................................. 355. The impacts of scenarios on economic aspects.................................... 365.1 Economic framework ................................................................................................................ 365.2 Technical <strong>implications</strong> of wireless ecosystems ......................................................................... 385.3 Service classes <strong>and</strong> scenarios classification in the overall value chain ..................................... 39Page 4 (41)


<strong>WINNER</strong> <strong>II</strong> D6.11.2 v1.06. Conclusions .............................................................................................. 417. References................................................................................................. 41Page 5 (41)


<strong>WINNER</strong> <strong>II</strong> D6.11.2 v1.0List of Acronyms <strong>and</strong> Abbreviations3GThird Generation3GPP Third Generation Partnership ProjectAIEAir Interface EvolutionBSBase StationCDMA Code Division Multiple AccessCGConcept GroupDSL Digital Subscriber LineEV-DO Evolution-Data OnlyGERAN GSM/Edge Radio Access NetworkGPRS General Packet Radio ServiceGSM Global System <strong>for</strong> Mobile CommunicationsHSDPA High-Speed Downlink Packet AccessHSUPA High-Speed Uplink Packet AccessIEEE Institute of Electrical <strong>and</strong> Electronics EngineersITUInternational Telecommunication UnionLALocal AreaLAN Local Area NetworkLOS Line of sightLTE Long Term EvolutionMAMetropolitan AreaMAN Metropolitan Area NetworkMIM Mobile Instant MessagingMMS Multimedia MessagingNLOS Non-LOSNRT Non-RTOFDM Orthogonal Frequency-Division MultiplexingRNRelay NodeRTReal TimeSCG Simulation Coordination GroupTD-CDMA Time Division-CDMAUMTS Universal Mobile Telecommunications SystemUTUser TerminalWAWide AreaWAN Wide Area NetworkWiFi Wireless FidelityWiMAX World Interoperability <strong>for</strong> Microwave AccessWLAN Wireless LANWMAN Wireless MANWWAN Wireless WANWPWork PackagePage 6 (41)


<strong>WINNER</strong> <strong>II</strong> D6.11.2 v1.02.5 Traffic load scenarioWhile the location scenario describes the relative user distribution <strong>and</strong> use of different services <strong>for</strong> aparticular location context, the traffic load scenarios further augments this into the absolute traffic loadexperienced. There<strong>for</strong>e user density in<strong>for</strong>mation is required.Traffic load scenarios (TLS) are used to describe the unrestrained end user traffic <strong>and</strong> the correspondingbehaviour of the network. TLS there<strong>for</strong>e refer to the expected nature of the traffic offered to the network,not the actual traffic characteristics over the air interface. No impediment to the build up of traffic isconsidered in the description of the TLS in this document.2.6 Deployment scenarioDeployment scenario comprises relevant features of the environment where the <strong>WINNER</strong> system is to bedeployed (e.g. building density <strong>and</strong> height, user density, mobility, etc.), <strong>and</strong> associated physicaldeployment characteristics used <strong>for</strong> the technical solution provided by <strong>WINNER</strong> (like antennas position,number sectors per BS, frequency, b<strong>and</strong>width, duplexing, physical layer mode, cell layout, etc.)[WIN2D6131]. Furthermore the available alternative radio access technologies (<strong>and</strong> assumptions relatedto their ownership, service offering, <strong>and</strong> type of co-operation) within the considered area are part of thedeployment scenario summarises key questions addressed <strong>and</strong> results obtained by the different scenariotypes.The key characteristics of the locations are: physical characteristics of the place, such as building height,building density, their distribution, etc 1 .Table 2.1: Summary of Considered Scenario TypesUserScenarioUsageScenarioLocationScenarioTraffic LoadScenarioDeploymentScenario<strong>Key</strong> Question Applicable <strong>for</strong> Averaging ResultsWhich services areneeded by a user in aparticular role <strong>and</strong>context?How is a particularservice typically used?Which service mix <strong>and</strong>usage pattern results <strong>for</strong>a user population in aparticular locationcontext?Which userdistribution, density,<strong>and</strong> absolute trafficload are generated in alocation scenario?Which technicalsolutions are deployedin a particular locationscenario?Single userSingle service<strong>and</strong> device typeSingle locationSingle locationSingle locationInstantaneousexamplesAveraged overtimeAveraged overtime <strong>and</strong> usersAveraged overtime <strong>and</strong> usersAveraged overtime <strong>and</strong> usersServices peruser type, role<strong>and</strong> contextTypical usageconditions of aserviceService mix,mobility, userdistributionUser density,traffic loadDeploymentparameters1 These characteristics are valid <strong>for</strong> the deployment <strong>and</strong> location scenarios. The difference is that the deploymentscenario refers to the availability <strong>and</strong> adoption of the technology in that particular area, while the location scenariorefers to the presence of a potential user of this technology. The connection is that if a location scenario ischaracterised by high user density it would mean that it can become a good deployment scenario driver.Page 10 (41)


<strong>WINNER</strong> <strong>II</strong> D6.11.2 v1.02.7 <strong>Key</strong> scenarioThe term “key scenario” can have different connotations. One might e.g. refer to key scenarios <strong>for</strong>scenarios which are most relevant <strong>for</strong> future business cases, or to such which are most challenging <strong>for</strong>radio access system design. In our context, key scenarios refer to the evaluation scenarios defined by the<strong>WINNER</strong> <strong>II</strong> concept groups [WIN2D6131]. These scenarios have been chosen such that a proof-ofconceptcan be achieved especially in scenarios that will be prevailing in the first deployment phase of<strong>WINNER</strong> systems. They span different physical layer modes <strong>and</strong> parameterisation of the <strong>WINNER</strong>system <strong>and</strong> focus on challenges in system requirements <strong>and</strong> system design [WIN2D6131].This deliverable adds further discussion <strong>and</strong> parameterisation to these evaluation scenarios in the area ofservice <strong>and</strong> traffic characteristics, as well as user behaviour. Typical usage cases in each evaluationscenarios shall be prioritized, i.e. the most used/common applications will be focused upon <strong>and</strong> based onthe location <strong>and</strong> deployment assumptions an appropriate behaviour of the user population will be derived,including service mix, traffic load, user distribution, density, <strong>and</strong> mobility.3. Services <strong>and</strong> generic applicationsService is a generic term <strong>and</strong> can be defined as a generic set of applications that have similarcharacteristics; this is a set of functions <strong>and</strong> facilities offered to users by a provider (service provider).Different services can be provided by the same network element <strong>and</strong> identical services can be provided bydifferent network elements. The applications interact directly with users <strong>and</strong> are characterised by serviceattributes <strong>and</strong> also by traffic <strong>and</strong> communications characteristics. The word “application” is used as ageneric term to represent the set of features, combining communication <strong>and</strong> document processing, inwhich end users may per<strong>for</strong>m operations.As a consequence, an application is an instance of a service with specific characteristics. The mostcommon service/applications characteristics will be presented: service characteristics; trafficcharacteristics; communication characteristics. These characteristics are not specific <strong>for</strong> <strong>WINNER</strong> butapply to all wireless systems. The next tables are based in deliverables [WIN1D11] <strong>and</strong> [WIND12].3.1 Service characteristicsThe service characteristics, <strong>for</strong> each service class, are explained in the following:Delivery requirements: RT (real time) – the processing of in<strong>for</strong>mation returns a result so rapidly that theinteraction appears to be instantaneous; or NRT (non-RT).Directionality: This characteristic intends to identify the nature of the communication <strong>and</strong> its direction.Three classes are identified: one-way – point-to-point (uplink or downlink); two-way – bidirectional(uplink <strong>and</strong> downlink); multi-way – point to multi-point, multi-point to multi-point or multi-point topoint.Symmetry of the connection: the characteristic “symmetry” permits the grouping of applicationsaccording to symmetry in the uplink/downlink data rate. The two classes are: symmetric or asymmetric<strong>and</strong> the respective asymmetry factor (UL <strong>for</strong> upload <strong>and</strong> DL <strong>for</strong> download).Number of parties that interact in the communication: one-to-one, 1 – 1, one-to-many, 1 – m, or multiparty,multi.Service classReal-timecollaboration<strong>and</strong>interactivegamingTable 3.1: Service characteristicsService characteristicsExamples ofapplications DeliveryAsymmetry Nb. ofDirectionality Symmetry/Asymmetryrequirementsfactor partiesVideoconference RT Symmetric/asymmetric 1UL – 1DL multiNavigation systems RTMulti-waySymmetric N/A N/AReal-time gaming RTAsymmetric26UL – 1 – 1,1000DL 1 – mTele-presence RT Two-way Symmetric N/A N/APage 11 (41)


<strong>WINNER</strong> <strong>II</strong> D6.11.2 v1.0Geographicreal-timedatacastGeographicinteractivemultimediabroadcastGeographicdatacastTele-teaching RT Multi-way Symmetric/Asymmetric1UL –1DL/low1 – 1,1 – mTele-working RT Two-way Symmetric 1UL – 1DL 1 – 1Real-time videostreamingRT Asymmetric N/A N/ACollaborative work RT Symmetric 1UL – 1DLMulti-wayTrafficin<strong>for</strong>mation/urbanguidanceVideobroadcasting/streamingLocalised mapdownloadLocaliseddatacast/beaconsAudio streamingAssistance in travelTourist in<strong>for</strong>mationNRT/RTAsymmetric5UL –1e3DL1 – 1,1 – m1 – mNRT/RT N/A N/AMulti-way AsymmetricNRTN/A N/ANRT N/A N/A N/ARTNRT/RTRTMulti-wayAsymmetric4UL –100DL5UL –1e3DL4UL –100DLShort control Alarms RT N/A N/Amessages<strong>and</strong>Remote/voice control RT One-way AsymmetricN/A N/Asignalling Sensors RTN/A N/ASimpleinteractiveapplicationsPresence driventransferInteractivegeographical mapsMobile videosurveillance1 – 1,1 – m1 – 11 – mNRT/RT N/A N/ANRT Two-way AsymmetricN/A N/ART5UL –0.001DLHigh quality videoInteractiveRT Symmetric/asymmetric 1UL – 1DL multiconferenceultra highMulti-waymultimedia 1 – 1,Collaborative work RTSymmetric1UL – 1DL1 – mInteractive Rich data call RT Symmetric/Asymmetric 1UL – 1DL 1 – 1highMulti-waymultimedia Robot security RTAsymmetric N/A N/ASimpletelephony<strong>and</strong>messagingData <strong>and</strong>mediatelephonyVoice telephony RT Symmetric 1UL – 1DLTwo-wayInstant messages4UL –NRTAsymmetric(SMS)100DL1 – 11 – 1,1 – m4UL – 1 – 1,Audio streaming RT Asymmetric100DL 1 – mTwo-wayVideo telephonyRTSymmetric 1UL – 1DL 1 – 1(medium quality)1 – 1Page 12 (41)


<strong>WINNER</strong> <strong>II</strong> D6.11.2 v1.0Multiplayer games RT Multi-way Asymmetric26UL –1000DL1 – 1,1 – mHigh quality videoRich dataRT Symmetric/asymmetric 1UL – 1DL 1 – 1telephony<strong>and</strong> mediaTwo-waytelephony 1 – 1,St<strong>and</strong>ard data call RTSymmetric1UL – 1DL1 - mLAN access<strong>and</strong> fileserviceFileexchangeDatabase <strong>and</strong> filesystem serverData file transfer(FTP)Videodownload/uploadPeer-to-peer filesharingNRT Two-way Asymmetric 4UL – 1DL 1 – 1RT Two-way Asymmetric 4UL – 1DL 1 – 1NRT One-way Asymmetric N/A N/AMessaging(data/voice/media)NRTTwo-way4UL –100DL1 – 1MultimediamessagingAuthentication (mpayment,m-ticket, m-wallet, …)AsymmetricNRT/RT N/A N/AOne-wayMultimedia mailNRT/RTN/AN/ALightweightbrowsingVideostreamingHigh qualityvideostreamingAccess to corporatedatabaseMultimedia webbrowsingE-bankingE-commerceVideo streaming(normal)Micro movies(including video clips)Video streaming(archival)NRT N/A N/ART 1UL – 5DL 1 – 1RTTwo-way Asymmetric4UL –100DL1 – mRT4UL –100DL1 – mRT N/A N/ARTOne-way Asymmetric26UL –1000DL1 – mRT One-way Asymmetric N/A N/A3.2 Traffic characteristicsTraffic characteristics reflect the way the packets flow from the sender to the receiver through thecommunication channel in a top-level view, the most important are:Average duration of connections refers to the connection holding time; this is the time that it takes fromthe beginning of the connection to its end.Latency/delay in a network is the amount of time that one packet takes to travel from its source todestination. The delay is one of the most relevant aspects in QoS per<strong>for</strong>mance.Page 13 (41)


<strong>WINNER</strong> <strong>II</strong> D6.11.2 v1.0Data rate is the speed of a data transfer process, normally expressed in bits per second or bytes persecond. It is a critical measurement when dealing with real time applications such as audio <strong>and</strong> video fileswhich require high b<strong>and</strong>width <strong>and</strong> are delay sensitive.Table 3.2: Traffic characteristicsTraffic characteristicsService class Examples of applications AveragedurationData rateDelayVideoconference30 minNavigation systemsN/AReal-time collaboration <strong>and</strong>interactive gamingReal-time gamingTele-presence10 – 30 minN/A1 – 20Mbps


<strong>WINNER</strong> <strong>II</strong> D6.11.2 v1.0messagingData <strong>and</strong> media telephonyInstant messages (SMS)Audio streamingVideo telephony (medium quality)Multiplayer games0.1 – 15min3 – 60 min5 min10 – 30 minRich data <strong>and</strong> media High quality video telephony 5 mintelephony St<strong>and</strong>ard data call 3 minLAN access <strong>and</strong> file service Database <strong>and</strong> file system server 1 – 5 sKbps64 – 512Kbps2-5Mbps>50Mbps200 ms100 –200 ms100 –200 ms100 –200 msFile data transfer (FTP)1 – 5 sFile exchangeVideo download/uploadPeer-to-peer file sharingN/A>50Mbps>200 msMultimedia messagingMessaging (data/voice/media)Authentication (m-payment, m-ticket, m-wallet, …)0.1 – 15minN/A8 – 64Kbps>200 msMultimedia mailN/AAccess to corporate database1 – 5 sLightweight browsingMultimedia web browsingE-banking1 – 15 min5 – 15 min64 – 512Kbps>200 msE-commerce5 minVideo streamingHigh quality videostreamingVideo streaming (normal)Micro movies (including videoclips)N/A3 – 5 min5 Mbps >200 msVideo streaming (archival) N/A 30 Mbps >200 ms3.3 Communication characteristicsThe communication parameters are required to specify the minimum requirements in order to establish asuitable communication to run one application at high level. During a communication, specificcharacteristics have to be ensured, the communication characteristics are:Burstiness is a source traffic characteristic that is defined as the ratio of the peak <strong>and</strong> the average bitrates.Bit error rate (BER) is a non-dimensional variable that expresses service tolerance to uncorrected errorsin the bearer service, including non-delivered in<strong>for</strong>mation. It is calculated as the ratio between bitsreceived with error or omitted, <strong>and</strong> the overall received bits.Traffic type: SERR – Service Requested Bit Rate, in this case the bit rate is controlled by the client;SYSA – System Assigned Bit Rate, where the bit rate is under the control of the access system/networkaccording to the available resources.Page 15 (41)


<strong>WINNER</strong> <strong>II</strong> D6.11.2 v1.0Service classReal-timecollaboration <strong>and</strong>interactivegamingGeographic realtimedatacastGeographicinteractivemultimediabroadcastTable 3.3: Communication characteristicsExamples of applicationsCommunication CharacteristicsTraffic type Error rate (BER) BurstinessVideoconference 1 – 5Navigation systemsN/AReal-time gaming 1 – 30SERR 10 -6 – 10 -9Tele-presenceN/ATele-teaching 1 – 5Tele-working1 – 20Real-time videostreamingN/ASERR 10 -6 Collaborative work 1 – 20Trafficin<strong>for</strong>mation/urban1 – 5guidanceVideobroadcasting/streamingSERR 10 -6 N/ALocalised map downloadLocaliseddatacast/beaconsN/AGeographicdatacastSERR 10 -3 – 10 -6 Audio streaming 1 – 5Assistance in travel 1 – 51 – 20Short controlmessages <strong>and</strong>signallingSimpleinteractiveapplicationsInteractive ultrahigh multimediaTourist in<strong>for</strong>mationAlarmsRemote/voice controlSensorsPresence driven transferInteractive geographicalmapsMobile videosurveillanceHigh quality videoconferenceCollaborative workSERR 10 -9 N/AN/ASERR 10 -6 N/A1 – 51 – 5SERR 10 -3 – 10 -6 1 – 20Interactive highmultimediaSimpletelephony <strong>and</strong>messagingRich data call 1 – 5SERR 10 -6Robot securityN/AVoice telephony 1Instant messages (SMS)SERR 10 -3 – 10 -6 1 – 20Data <strong>and</strong> media Audio streaming SERR 10 -3 – 10 -6 1 – 5Page 16 (41)


<strong>WINNER</strong> <strong>II</strong> D6.11.2 v1.0telephonyRich data <strong>and</strong>media telephonyLAN access <strong>and</strong>file serviceVideo telephony(medium quality)1 – 5Multiplayer games 1 – 30High quality videotelephonySt<strong>and</strong>ard data callDatabase <strong>and</strong> file systemserverSERR 10 -3 – 10 -6 11 – 5SYSA 10 -6 1 – 50File data transfer (FTP) 1 – 50File exchangeVideo download/uploadSYSA 10 -6 N/AN/APeer-to-peer file sharingMultimediamessagingMessaging(data/voice/media)Authentication (mpayment,m-ticket, m-wallet, …)1 – 20SYSA 10 -6 – 10 -9 N/AN/AMultimedia mailLightweightbrowsingAccess to corporatedatabaseMultimedia webbrowsing1 – 501 – 20SERR 10 -6 1 – 20E-banking 1 – 50Video streamingHigh qualityvideo streamingE-commerceVideo streaming(normal)Micro movies (includingvideo clips)Video streaming(archival)SERR 10 -6 1N/ASERR 10 -9 N/A4. <strong>Key</strong> scenariosIn this section, the key scenarios are identified taking into account the described inputs <strong>for</strong> the selectionprocedure. <strong>Key</strong> scenarios will be identified according to selection criteria (defined below) <strong>and</strong> linked tothe deployment scenarios.4.1 Scenario elements <strong>and</strong> generation methodologyThe services provided by the <strong>WINNER</strong> system shall be available where they are needed by users.Different users’ profiles/necessities imply different usage percentages per service/application. The<strong>WINNER</strong> will need to support a variety of services, with different requirements, <strong>and</strong> the end-to-end QoSshall be negotiable <strong>and</strong> controllable. The association of the different scenario elements identifies a certainscenario type. Examples of scenario elements are environment type, cell range, terminal type, user profile,user mobility, user density <strong>and</strong> related end user applications, see Table 4.1.Page 17 (41)


<strong>WINNER</strong> <strong>II</strong> D6.11.2 v1.0Table 4.1: Scenario elements characterisationScenario elementsEnvironment typeCell rangeApplicationtypeTerminaltypeUserdensityUserprofileValue/parameterDense urbanMetropolitan Typical urbanBad urbanMetropolitan SuburbanRuralIndoor small(office/residential/commercialzones)Indoor to outdoorOutdoor to indoorIn building(pico-cell)(LA)Hotspot(microcell)(LA)Rural(macrocell)(WA)Urban(microcell)(LA)See chapter3WearableterminalPalmtop(PDA)MobilephoneLaptopDesktopLowMediumHighOldYoungBusinessTouristSportLOS – Stationary feederLOS – FeederRural LOS – Moving networksUrban(macrocell)(MA)Umbrella(WA)4.1.1 Environment type <strong>and</strong> cell sizeThe environment type is one of the most important elements in the scenario characterisation <strong>and</strong> is relatedwith the physical characteristics of the environment <strong>and</strong> wave propagation properties. Differentenvironment types have been defined within <strong>WINNER</strong> associated with coverage <strong>and</strong> cell types. Thetypical distance range is always a question of data rates required by applications: higher data rates lowerdistance range; lower data rates, higher distance range.Local area scenarios (office/residential/commercial) are characterised mainly with low terminal mobility,short-range coverage (pico or micro-cells) with typical distance range of 3 – 100 m (Indoor small office /residential) <strong>and</strong> 20 – 100 m (Hotspot / Typical urban micro-cell), high density of users <strong>and</strong> high data rateapplications. Metropolitan area scenarios (urban/suburban) normally requires ubiquitous coverage (microor macro-cells) with typical distance range of 20 – 400 m <strong>and</strong> are characterised with medium/high trafficdensity with medium terminal velocity. Wide Area scenarios are characterised by a continuous <strong>and</strong>ubiquitous coverage (normally macro-cells), medium/high terminal velocity <strong>and</strong> low rate applicationsmainly based on voice.4.1.2 Terminal typeThe <strong>WINNER</strong> system is user-oriented, which enables communication anytime, anywhere with anyone oranything. Different terminal types are envisaged in <strong>WINNER</strong> evaluation scenarios in order to satisfy enduser requirements <strong>and</strong> taking full part of the available services <strong>and</strong> applications. The terminal types can bederived from a set of physical characteristics <strong>and</strong> capabilities such as: user friendly, display size,portability (size <strong>and</strong> weight), power consumption, maximum transmit power (related with link budget <strong>and</strong>cell range) The identified terminal types <strong>for</strong> scenario generation are (cf. Table 4.1): wearable terminal,palmtop (PDA), mobile phone, laptop <strong>and</strong> desktop.4.1.3 User density <strong>and</strong> traffic parametersUser density depends highly on the environment type <strong>and</strong> can be defined per service/application type. Themost dem<strong>and</strong>ing applications typically experience coverage limitations. The Table 4.2 characterises theuser density <strong>and</strong> traffic parameters such as number of session attempts <strong>and</strong> average session duration perenvironment <strong>and</strong> typical applications [SCE+05].Page 18 (41)


<strong>WINNER</strong> <strong>II</strong> D6.11.2 v1.0Table 4.2: Users density, number of session attempts, <strong>and</strong> average session duration perenvironment typeExample ofapplicationsVoice (CBR)VoIP (ABR)SMS (ABR)MMS (UBR)Video Interactivemobile TV (CBR)Telemedicine (VBR)Streamed video(sports <strong>and</strong> events)(VBR)IP Web radio (VBR)Video streaming(ABR)M-commerce (ABR)M-banking (ABR)E-mail (UBR)CGLAEnvironment typeIndoor small(residential)/dense urbanIndoor small(office)/dense urbanIndoor small(residential)/suburbanUserdensity(users/km 2 ) 2Number ofsessionattempts perday(1/users)26400 5 12030000 10 1506600 6 120MA Typical urban 11000 3 100WALASuburban 2000 10 120Rural 200 6 120Indoor small(residential)/dense urbanIndoor small(office)/dense urbanIndoor small(residential)/suburban2640 1 18015000 1 6004400 1 180MA Typical urban 1100 1 120WASuburban 500 1 600Rural 50 1 120AveragesessiondurationD n,m (s)Note: CBR – Constant bit rate, VBR – Variable bit rate, ABR – Available bit rate, UBR – Unspecified bitrate.4.1.4 User mobilityUser (or terminal) mobility plays an important role as a key scenario element, since system per<strong>for</strong>manceis directly affected in terms of radio resource management, traffic h<strong>and</strong>ling, location <strong>and</strong> QoSmanagement. User mobility requirements have also to be taken into account during system design <strong>and</strong>architecture.In Table 4.3 the ratio of different mobility categories are presented <strong>for</strong> each environment type <strong>and</strong>application.Table 4.3: Mobility distribution (%) in different environment typesExample ofCGEnvironment typeMobility ratio (%)2 These values are different from the ones that can be found in the ITU model (see [SCE+05]) because that valueswere proposed taking into account UMTS system (2.0 GHz).Page 19 (41)


<strong>WINNER</strong> <strong>II</strong> D6.11.2 v1.0applicationsVoice (CBR)VoIP (ABR)SMS (ABR)MMS (UBR)Video Interactivemobile TV (CBR)Telemedicine (VBR)Streamed video(sports <strong>and</strong> events)(VBR)IP Web radio (VBR)Video streaming(ABR)M-commerce (ABR)M-banking (ABR)E-mail (UBR)LAIndoor small(residential)/dense urbanIndoor small(office)/dense urbanIndoor small(residential)/suburban0 – 5km/h5 – 70km/h70 –100km/h100 –250km/h>250km/h90 10 0 0 090 10 0 0 085 15 0 0 0MA Typical urban 10 70 20 0 0WALASuburban 30 40 20 10 0Rural 15 45 20 15 5Indoor small(residential)/dense urbanIndoor small(office)/dense urbanIndoor small(residential)/suburban95 5 0 0 095 5 0 0 090 10 0 0 0MA Typical urban 10 70 20 0 0WASuburban 35 40 25 0 0Rural 10 40 35 10 5Note: CBR – Constant bit rate, VBR – Variable bit rate, ABR – Available bit rate, UBR – Unspecified bitrate.4.1.5 Mobility modelsThe purpose of mobility models is to describe typical terminal movement so that per<strong>for</strong>mance analysiscan be made. Many link <strong>and</strong> system-level simulators require the knowledge of terminal position in eachsimulated time step so that the effectiveness of studied techniques such as link adaptation, transmissiondiversity <strong>and</strong> beam <strong>for</strong>ming may be evaluated.Next mobility models are presented <strong>for</strong> office environment, outdoor to indoor environment, hotspot <strong>and</strong>vehicular environment.4.1.5.1 Indoor small (office) environment mobility modelOffice environments are characterised by a “boxy” topology, where office rooms are interconnected bycorridors. Users will spend most of the time stationary at their desk <strong>and</strong> when in movement they will goto a particular destination. Destinations can be chosen r<strong>and</strong>omly, using a uni<strong>for</strong>m distribution. Two casesmay be considered, concerning the nature of movements: both source <strong>and</strong> destination are an office room(case 1); either source or destination is a corridor position (cases 2 <strong>and</strong> 3).Page 20 (41)


<strong>WINNER</strong> <strong>II</strong> D6.11.2 v1.0Figure 4.1: Office environmentThe next text will only consider case 1 <strong>and</strong> derive the basic relationships.The important parameters are the mean ratio of room-situated to corridor-situated mobile terminals, r,average time in office room, T r , <strong>and</strong> mobile speed, v m . Some possible values are presented in Table 4.4 asan example.Table 4.4: Indoor small (office) environment mobility parameters <strong>and</strong> possible valuesParameter Symbol Typical valueAverage ratio of the room to corridor mobile terminals r 85%Average stationary time in office room T r 30 sMobile speed v m 1 m/sSimulation time step0.005 sNumber of office rooms 40Considering the equilibrium between office-to-corridor <strong>and</strong> corridor-to-office flows we have:r ( 1−r)= (4.1)Tr T cwhere T c is the average time in corridor. Using (4.1), the average time in the corridor, T c , may beexpressed in function of the other two:( 1−r)Tc= Tr(4.2)rif the possibility of corridor stops is not modelled. In that case, <strong>and</strong> since all rooms are equally probableas a destination, the average time in corridor will be a direct function of the average distance betweenrooms:LTc= (4.3)vrmIf stationary states are allowed in the corridors some relations will be re<strong>for</strong>mulated. Whenever the r<strong>and</strong>omdestination chosen is a corridor position, T c will be divided in two parts. Each of these parts willcorrespond to a separate event in the simulation. The first part representing the walk component T cm , isdeterministic in nature given by an equation similar to (4.3), which now includes both office rooms <strong>and</strong>corridor positions as possible destinations. The second part, T cs , represents the average stationary time incorridor with a value in compliance with (4.2) <strong>and</strong> (4.3), as follows:Page 21 (41)


<strong>WINNER</strong> <strong>II</strong> D6.11.2 v1.0TcsTcs= T −T(4.4)ccm(1 − r)L= Tr−r vIn this environment we also need to take into account the way buildings are built, <strong>and</strong> how they areorganized inside. In the next table, some typical values are presented [UMTS30.03]:rm(4.5)Table 4.5: Indoor small (office) environment physical parametersArea per floor (m 2 ) Number of floors Room dimensions Log-normal st<strong>and</strong>ard deviation (dB)5000 310x10x3 m (room)100x5x3 m (corridor)74.1.5.2 Hotspot environment mobility modelIn <strong>WINNER</strong> the mobility in a hotspot is modelled as low mobility (3 km/h <strong>and</strong> stationary) with a highprobability of changing the direction of movement (see Figure 4.2). User movements are typicallyr<strong>and</strong>omly distributed.Figure 4.2: Mobility inside Hotspot AreaFor simulations the different mobility in the hotspot will only be applied to the additional users created<strong>for</strong> the hotspot. The users created with the “normal” density function will have the “normal” mobility.The users created, as additional traffic will have the hotspot mobility.With a speed of 3 km/h <strong>and</strong> a direction change probability of 100% every meter the users stay (typically)inside an area of 25 m.With this simple mobility model, the average distance d travelled by a user can be calculated asfollows:where v is the velocity in (m/s) of the user,the mobility update interval in seconds.dtSession= v ⋅ ∆t⋅(4.6)∆ttSessionis the mean lifetime of a user in seconds <strong>and</strong> ∆ t is4.1.5.3 Outdoor to indoor (dense urban) mobility modelIn this environment base stations are placed outdoors but also cover internal building areas. To representcity centres, the Manhattan Model is normally used, which is a rectangular grid of intersecting streets, asshown in Figure 4.3. High, homogeneous squared buildings with small areas, high user density <strong>and</strong> lowmobility (pedestrians) characterise this environment. For simulation purposes, we may consider that eachwall of the buildings has 200 m of width <strong>and</strong> the streets are 30 m wide.Page 22 (41)


<strong>WINNER</strong> <strong>II</strong> D6.11.2 v1.0Figure 4.3: City Centre ModelThe urban mobility model is highly related to the Manhattan-like structure defined above. In such astructure, mobiles move along streets <strong>and</strong> may turn across streets with a given probability. The mobile’sposition is updated every 5 m <strong>and</strong> speed can change at each position, according to certain probability.The mobility model is described by the following parameters:• Mean speed: 3 km/h;• Minimum speed: 0 km/h;• Maximum speed: 5 km/h;• St<strong>and</strong>ard deviation <strong>for</strong> speed (normal distribution): 0.3 km/h;• Probability to change speed at position update: 0.2;• Probability to turn at street crossing: 0.5 (see Figure 4.4).Figure 4.4: Turning probabilityMobiles are uni<strong>for</strong>mly distributed in the street <strong>and</strong> their direction is r<strong>and</strong>omly chosen (horizontal orvertical direction) at initialisation.In this environment the physical characteristics may be the following [WIN2D111]:Table 4.6: Outdoor to indoor mobility model physical environmentBuilding penetration loss/st<strong>and</strong>arddeviation (dB)Log-normal st<strong>and</strong>arddeviation (dB)Outdoor N/A 7 3Indoor 15/8 15 3Mobile velocity(km/h)4.1.5.4 Vehicular environment (typical urban) mobility modelVehicular environment applies to scenarios in urban <strong>and</strong> suburban areas outside the city centres where thebuildings have nearly uni<strong>for</strong>m height <strong>and</strong> are characterised by larger cells <strong>and</strong> higher transmit power.Page 23 (41)


<strong>WINNER</strong> <strong>II</strong> D6.11.2 v1.0The vehicular reference mobility model uses a pseudor<strong>and</strong>om mobility model with semi-directtrajectories. The mobile position gets updated according to the decorrelation length, <strong>and</strong> direction canchange at each position. As a reference example, it can be assumed that the mobile’s speed is constant<strong>and</strong> the mobility model is defined by the following parameters:• Speed value: 120 km/h;• Probability to change direction at position update: 0.2;• Maximal angle <strong>for</strong> direction update: 45º;• Decorrelation length: 20 m.Mobiles are uni<strong>for</strong>mly distributed on the map <strong>and</strong> their directions are r<strong>and</strong>omly chosen.According to <strong>WINNER</strong> CGs, the vehicular environment mobility model may be applied in the followingscenarios (listed in Table 4.7):Table 4.7: Harmonised velocities <strong>for</strong> <strong>WINNER</strong> applied to vehicular mobility modelCG Environment type Mobility (km/h)Wide AreaSuburban 100Urban 50Metropolitan Area Urban 50Local Area Urban


<strong>WINNER</strong> <strong>II</strong> D6.11.2 v1.0Appropriate dem<strong>and</strong> characterization has to reflect the different deployment distributions that are possible<strong>for</strong> different services/applications, as well as their distinguished downlink/uplink asymmetries.The approach is firstly to map the different sub-scenarios identified in [JF05] into the deploymentscenarios identified in the <strong>WINNER</strong> context as shown in Table 4.8 . Thus each application usage will becalculated <strong>and</strong> extrapolated taking into account the figures from the application usage proposal in [JF05].In Table 4.9 a proposal of the applications usage <strong>for</strong> each deployment scenario in <strong>WINNER</strong> is presented.LAMAWATable 4.8: <strong>WINNER</strong> deployment scenariosCG Short scenario characterisation Sub-scenarios [JF05]Short range coverage, lowterminal mobility <strong>and</strong> high datarates applicationsUbiquitous coverage withmedium-high traffic density withmedium terminal velocityContinuous <strong>and</strong> ubiquitouscoverage, medium–high terminalvelocity <strong>and</strong> low rate applicationsmainly based on voiceapplications• Home (HOM), rooms, residential• Offices (OFF), buildings not residential• Commercial zones (COM) such asshopping centres, airports, railways,stations, hospitals• Business city centre, (BCC) pedestrian• Offices (OFF), buildings not residential• Urban residential areas (URB) pedestrian• Urban residential areas (URB) pedestrian<strong>and</strong> vehicular• Industry (IND), large factories areas• Primary roads (ROA) including highways• Trains (TRA)Table 4.9: Proposal of applications usage (%) <strong>for</strong> <strong>WINNER</strong> deployment scenariosCG (usage %)Service classes Applications Local AreaMetropolitanAreaWide AreaVoice over IP 24 26 30Audio Streaming 3 4 4Video-telephony 2 2 2Simple telephony, mediatelephony, messaging, data<strong>and</strong> rich dataVideo streamingHIMM Videoconference,(various purposes)Instant Messaging <strong>for</strong>Multimedia2 2 22 2 1Remote Procedure Call 3 2 2Micro-movies 1 2 3Broadb<strong>and</strong> (Videotex (E-Commerce))4 8 6Mobile Video Surveillance 2 2 3TV Programme distribution(MPEG2-4)2 2 0Real-time collaboration <strong>and</strong> Interactive Remote Games 1 1 1Page 25 (41)


<strong>WINNER</strong> <strong>II</strong> D6.11.2 v1.0interactive gammingFile exchangeLightweight browsingLAN access <strong>and</strong> file serviceMobile Tele-Working 1 3 2Collaborative working (&tele-presence)Videoconference (Teleadvertising)HD Video-telephony (Teleeducation)1 1 21 1 24 5 5Data (FTP) 9 6 5Still Images Communication 6 4 4Professional Images 2 1 0Multimedia (WebBrowsing)14 12 10Mobile Portal 4 3 3E-newspaper 5 5 5Wireless LANInterconnection1 2 1Tourist In<strong>for</strong>mation 2 1 1Geographic datacastAssistance in Travel 1 1 4Urban Guidance 1 1 1Short control messages <strong>and</strong> Control Data 1 1 1signalling Monitoring 1 0 0TOTAL 100 100 100Table 4.10: Proposal <strong>for</strong> services usage (%) <strong>for</strong> <strong>WINNER</strong> deployment scenariosCG (usage %)Service classes Local Area Metropolitan Area Wide AreaSimple telephony,media telephony,messaging, data <strong>and</strong>rich data36 38 41Video streaming 9 14 12Real-time collaboration<strong>and</strong> interactivegamming8 11 12File exchange 17 11 9Lightweight browsing 23 20 18LAN access <strong>and</strong> fileservice1 2 1Geographic datacast 4 3 6Short control messages<strong>and</strong> signalling2 1 1TOTAL 100 100 100Page 26 (41)


<strong>WINNER</strong> <strong>II</strong> D6.11.2 v1.04.2 Selection of key scenarios <strong>for</strong> <strong>WINNER</strong>In this section, an explanation describing the methodology <strong>and</strong> criteria <strong>for</strong> the selection of key scenarios isper<strong>for</strong>med.4.2.1 Scenario A (related with LA Concept Group)LA CG main assumptions <strong>and</strong> <strong>implications</strong>.This section provides a brief overview of the main assumptions considered within the scope of the LocalArea deployment scenario, as also an insight into some high level relevant <strong>implications</strong>.According to [WIN2D6131], where the basic assumptions about the Local Area concept group arepresented, the two main environmental settings dominating the LA-related proof-of-concept are theindoor environment <strong>and</strong> the hotspot areas. In consistency with the scenario definition that was done in<strong>WINNER</strong> I, the high level scenarios that fall within the scope of LA CG are summarized in the next table:Table 4.11: High – level LA CG scenarios descriptionScenario Definition LOS/NLOSMob.(km/h)Distancerange (m)In <strong>and</strong>aroundbuildingsIndoor small office /residentialLOS/NLOSIndoor to outdoor NLOS 0 – 50 – 5 3 – 100HotspotTypical urban micro-cellLOS/NLOS0 – 5 20 – 100Indoor LOS 0 – 5It is evident from the table above that the user mobility considered within such scripts remains low (0 – 5km/h) as also is the case with the coverage range (3 – 100 m).In case of residential services, the main assumption is that the wireless link will be provided through aBS, which will be connected to a backbone network. The residential area is considered to be well isolatedfrom neighbouring BSs, so that intercell interference can be neglected. There<strong>for</strong>e, in case of home access,the two main <strong>implications</strong> as set by the LA CG relate to:• Deployment of efficient self–organisation schemes in order to create provision <strong>for</strong> directcommunication in P2P mode, between <strong>WINNER</strong>-capable terminals within the users residency;• Deficient h<strong>and</strong>-over between <strong>WINNER</strong> modes so as to allow <strong>for</strong> user mobility from onecoverage area (home) to another (urban);• Connectivity provisioning between home BS <strong>and</strong> <strong>WINNER</strong> backbone.Considering now the hotspot related scenario which constitutes the other LA-based proof-of-concept, themain high level assumptions are that the specific mode will be in position of covering larger areas thanthe ones encompassed in the residential usage, <strong>and</strong> with the simultaneous presence of more than one BSs,there<strong>for</strong>e the assumption about limited interference may not be valid. In summary, the main issues thatwill be addressed within this sub category of deployment scenarios include:• P2P communication issues (as in the previous case);• Cooperation schemes between coexisting <strong>WINNER</strong> BSs.The following script addresses the a<strong>for</strong>ementioned issues in order to serve as a representative scenario ofthe LA proof-of-concept:Main actor: John, male, 18 years oldLocation: Urban area (a city of Europe)Page 27 (41)


<strong>WINNER</strong> <strong>II</strong> D6.11.2 v1.0Occupation: StudentDate: A day in 20151. John is woken up by the ringing on his portable device; he has received a multimedia message(video message), sent to him by the relevant service of his university, in<strong>for</strong>ming him about somechange in the daily class schedule.2. Having woke up, he surfs on the Internet using his laptop, while making a voice call to hisgirlfriend.3. He turns on the next generation Winner LA BS that he bough yesterday. The new BS detects theother BSs of John's house, as well as neighbouring ones. <strong>and</strong> all the BSs coordinate with eachother to re<strong>for</strong>m the available frequency <strong>and</strong> optimize the wireless resource usage.4. Visiting an online music store, he selects some new tunes. The songs are purchased <strong>and</strong>transferred directly to his online music server.5. He tries to communicate his roommate that sleeps in the next room, establishing a directconnection with his device.6. His roommate is not responding so John sends him a short video message.7. While having his breakfast, John streams TV news on his device.8. He initiates a voice call (using a VoIP service), while he leaves the house <strong>and</strong> enters the car todrive to the mall, where he is supposed to meet with a fellow student.9. During his drive through the city, the VoIP call is continued, <strong>and</strong> after entering a cafeteria in themall he decides to terminate this session.10. The cafeteria offers online menu, so John selects what to order after browsing on the relevantlocally available web site.As it is obvious, the scenario tries to address most of the important aspects involved within typical LAproof-of-concepts, rather than being exhaustive in terms of service usages. The elements of interestregarding the scenario composition are depicted in the following table:Table 4.12: LA – based scenarioScript ExtractServiceClassUserDensityUserMobilityAssociatedTraffic ModelEnvironment Coverage Implicationshe hasreceived amultimediamessageMultimediamessagingHigh(residential)Low (0– 5km/h)File TransferResidential3 – 100mConnectivitybetween BS<strong>and</strong> <strong>WINNER</strong>backbonehe surfs theInternetLightweightbrowsingHigh(residential)Low (0– 5km/h)Internet /BrowsingResidential3 – 100mConnectivitybetween BS<strong>and</strong> <strong>WINNER</strong>backbonewhile making avoice call tohis girlfriendSimpleTelephony<strong>and</strong>MessagingHigh(residential)Low (0– 5km/h)ConversationalResidential3 – 100mConnectivitybetween BS<strong>and</strong> <strong>WINNER</strong>backbonehe turns on thenextgenerationWinner LABS…Shortcontrolmessages<strong>and</strong>signallingHigh(residential)Low (0– 5km/h)SignallingResidential3 – 100mSelf-Organizationbetween LABSsPage 28 (41)


<strong>WINNER</strong> <strong>II</strong> D6.11.2 v1.0the BS detectsthe other BSsof John’shouse…all BSscoordinatevisiting anonline musicstore…the songsare purchasedLightweightbrowsingHigh(residential)Low (0– 5km/h)Internet /BrowsingResidential3 – 100mConnectivitybetween BS<strong>and</strong> <strong>WINNER</strong>backbone<strong>and</strong>transferreddirectly to hisonline musicserverFileexchangeHigh(residential)Low (0– 5km/h)File TransferResidential3 – 100mConnectivitybetween BS<strong>and</strong> <strong>WINNER</strong>backbone / sel<strong>for</strong>ganizationbetweenresidential<strong>WINNER</strong>devicesHe tries tocommunicatehis roommate…establishinga directconnectionwith hisdevice.Simpletelephony<strong>and</strong>messagingHigh(residential)Low (0– 5km/h)ConversationalResidential(P2P mode)3 – 100mP2Pcommunicationbetween<strong>WINNER</strong>enableddevicesso John sendshim a shortvideo messageFileexchangeHigh(residential)Low (0– 5km/h)File TransferResidential(P2P mode)3 – 100mP2Pcommunicationbetween<strong>WINNER</strong>enableddevicesJohn streamsTV news on hisdeviceVideostreamingHigh(residential)Low (0– 5km/h)VideoStreamingResidential3 – 100mConnectivitybetween BS<strong>and</strong> <strong>WINNER</strong>backboneHe initiates avoice call(using a VoIPservice), whilehe leaves thehouse…Duringhis drivethrough thecity, the VoIPcall iscontinued, <strong>and</strong>after enteringa cafeteria inthe mall hedecides toterminate thissessionSimpletelephony<strong>and</strong>messagingHigh(residential)(<strong>for</strong> as longas the actoris still athome)Low (0– 5km/h)(<strong>for</strong> aslong asthe actoris still athome)ConversationalResidential(<strong>for</strong> as longas the actoris still athome)3 – 100m(<strong>for</strong> aslong asthe actoris still athome)H<strong>and</strong>overbetween<strong>WINNER</strong>modesPage 29 (41)


<strong>WINNER</strong> <strong>II</strong> D6.11.2 v1.0The cafeteriaoffers onlinemenu, so Johnselects what toorder afterbrowsing onthe relevantlocallyavailable websiteLightweightbrowsingMedium(hotspot)Low (0-5 km/h)Internet /BrowsingHotspot20 – 100mCoordinationbetween coexistingBSs /cooperationbetween<strong>WINNER</strong>system modesso as tocomplement<strong>for</strong> coverageareas4.2.2 Scenario B (related with MA Concept Group)MA CG main assumptions <strong>and</strong> <strong>implications</strong>.This section provides a brief overview of the main assumptions considered within the scope of theMetropolitan Area deployment scenario.In [WIN2D6131] the basic assumptions about the evaluation scenario of the Metropolitan Area CG arepresented. Metropolitan Area CG focuses on <strong>WINNER</strong> system design <strong>and</strong> proof-of-concept in urbanenvironments <strong>and</strong> deployment scenarios. The high-level deployment scenarios which can in general beconsidered under metropolitan area defined in <strong>WINNER</strong> I are listed in the next table.NameHotspot/AreaMetropolitanTable 4.13: High – level MA CG scenarios descriptionPropagationTraffic DensityCoverageMobilityConditions(Indicative)Typical UrbanBad UrbanArea wide but0 – 70 km/h [High]non-ubiquitous Outdoor tocoverage IndoorLOS – Stationary0 km/h [High]FeederUbiquitouscoverageSuburbanTypical UrbanBad urbanOutdoor toIndoor0 – 70 km/h[Medium][Medium]/[High][Low]-[High]LOS – Feeder 0 km/h [Low]/[Medium]MA CG is targeting the <strong>WINNER</strong> system design <strong>and</strong> assessment in urban <strong>and</strong> metropolitan areas wherethe user density is high. As the expected throughput requirements per active user are also high, it meansthat the <strong>WINNER</strong> system must provide high system capacities in system deployments in theseenvironments. Thus, the <strong>WINNER</strong> system deployment scenario in these areas is called “Highper<strong>for</strong>mancelayer <strong>for</strong> metropolitan areas”.This deployment scenario provides contiguous coverage in urban areas, <strong>and</strong> especially in the city centresof large <strong>and</strong> medium size cities. As the system throughput requirements are high, system throughputenhancing solutions will be prioritised over coverage providing solutions. Based on these requirements,the Metropolitan Area deployment scenario needs to focus on micro cellular deployment scenarios, i.e. inurban environments base stations, access point, <strong>and</strong> relays are placed clearly below the rooftop level (insuburban deployments the antenna placement can be above rooftop level, but the access point height isPage 30 (41)


<strong>WINNER</strong> <strong>II</strong> D6.11.2 v1.0roughly the same as in the urban environments, i.e. low). While the micro cellular deployment helps inreaching the system throughput requirements, it is challenging from radio propagation point-of-view.The requirement <strong>for</strong> supporting high user density means that MA CG supports outdoor hotspots (LocalArea CG is supporting indoor hotspots), use of small cells, applying efficient multi-antenna techniques, orutilizing smart interference mitigation <strong>and</strong> avoidance schemes in order to provide the high systemthroughput required.Basic assumption of Metropolitan Area deployment scenario is that the deployment is realized outdoors.As how to provide indoor coverage with a “semi-contiguous” coverage systems is always a relevantquestion, outdoor-to-indoor coverage is addressed in metropolitan area deployment scenario. This alsotries to answer the important question that how the “outdoor” <strong>and</strong> “indoor” deployments of the <strong>WINNER</strong>system should cooperate, so that seamless coverage within the <strong>WINNER</strong> system is realized.Main actor: John, male, 18 years oldLocation: Urban area (a city of Europe)Occupation: StudentDate: A day in 20151. When John leaves his house <strong>and</strong> prepares to drive to the shopping mall. He gets in the carwithout the use of a key, as John’s digital ID, existing in his UT, wirelessly authenticates him tothe car security system.2. His UT sets up the songs playing list to the car’s audio system.3. The audio system starts downloading the songs from the common wireless song distributionnetwork used by all the big music companies in order to distribute their songs.4. John’s e-wallet is charged automatically <strong>for</strong> the songs that he hasn’t already bought listeninglicenses <strong>for</strong>.5. John browses sports news using his UT to check the game result of his favourite football team.6. The car’s navigation system traces the optimal way to the shopping mall according to the trafficload of the roads.7. On the way the system identifies a road that is suddenly heavily traffic jammed, probablybecause of a car accident, so it interrupts the audio system to alert John of the situation.8. Then it in<strong>for</strong>ms John of the best alternative way to the shopping mall.9. John sends a voice message to in<strong>for</strong>m his friend that he is going to be late.Table 4.14: MA – based scenarioScriptExtractServiceClassUserDensityUserMobilityAssociatedTraffic ModelEnvironment Coverage Implicationswirelesslyauthenticateshim to thecar securitysystemMultimediamessagingbut with alow delay(


<strong>WINNER</strong> <strong>II</strong> D6.11.2 v1.0devicesthe audiosystem startsdownloadingLightweightbrowsingLow(residential)Low (0– 5km/h)Internet/browsing,File transfermodelResidential3 – 100mConnectivitybetween BS<strong>and</strong> <strong>WINNER</strong>backbonee-wallet ischargedautomaticallyMultimediamessagingLow(residential)Low (0– 5km/h)Internet/browsing,File transfermodelResidential3 – 100mConnectivitybetween BS<strong>and</strong> <strong>WINNER</strong>backbonebrowsessports newsLightweightbrowsingLow(residential)Low (0– 5km/h)Internet/browsing,File transfermodelResidential3 – 100mConnectivitybetween BS<strong>and</strong> <strong>WINNER</strong>backbonecar’snavigationsystem tracesthe optimalwaySimpleinteractiveapplicationsMediumMedium(0 – 70km/h)Internet/browsing,File transfermodelUrban50 –1000 mConnectivitybetween BS<strong>and</strong> <strong>WINNER</strong>backbonedue to cartrafficcongestionSimpletelephony<strong>and</strong>messagingMediumMedium(0 – 70km/h)Internet/browsing,File transfermodelUrban50 –1000 mConnectivitybetween BS<strong>and</strong> <strong>WINNER</strong>backbonedue to cartrafficcongestionGeographicdatacastMediumMedium(0 – 70km/h)Internet/browsing,InteractiveactivityUrban50 –1000 mConnectivitybetween BS<strong>and</strong> <strong>WINNER</strong>backbonevoicemessageSimpletelephony<strong>and</strong>messagingMediumMedium(0 – 70km/h)Conversationalvoice modelUrban50 –1000 mConnectivitybetween BS<strong>and</strong> <strong>WINNER</strong>backbone4.2.3 Scenario C (related with WA Concept Group)A key aspect of mobile cellular systems is the ability to make a call, access content, send an e-mail <strong>and</strong> soon from anywhere. Particularly in Europe GERAN coverage is ubiquitous <strong>and</strong> there is the expectation ofbeing able to be contactable in any geographic location. <strong>WINNER</strong> needs to provide this same ubiquitouscoverage layer <strong>for</strong> minimum user data rate (2 Mbit/s) [WIN2D6131]. This base layer will cover rural,suburban <strong>and</strong> urban areas, providing the umbrella coverage; whilst there will be other deployments (asconsidered in the Metropolitan <strong>and</strong> Local Area CGs), providing more targeted, higher data rate coverage.This scenario is meant to reflect the ubiquitous coverage deployment of <strong>WINNER</strong> in towns <strong>and</strong> cities,where it will overlap with deployments considered by the Metropolitan <strong>and</strong> Local Area CGs. This is<strong>for</strong>eseen as similar to today’s macro-cell deployments. There<strong>for</strong>e, this scenario is not described here (seeprevious section).The WA scenario describes the relevant characteristics of a selection of environments where a <strong>WINNER</strong>system might be deployed. “Environment” means here that the description is independent from thetechnical solution that <strong>WINNER</strong> provides, but refers only to the external characteristics that cannot bechanged by <strong>WINNER</strong>.The benchmark technologies <strong>for</strong> the WA scenario are deployed cellular systems such as GSM/GPRS,cdma2000, UMTS, TD-CDMA, HSDPA/HSUPA <strong>and</strong> EV-DO. Furthermore, systems about to best<strong>and</strong>ardized or deployed during the course of <strong>WINNER</strong> <strong>II</strong> are 3GPP Long Term Evolution (LTE), theevolution of 3GPP2 EV-DO (Revision C or AIE), IEEE 802.16e (“Mobile WiMAX”), IEEE 802.20 <strong>and</strong>proprietary systems like Flash-OFDM initially developed by the company Flarion. Research results from<strong>WINNER</strong> may directly feed into the development of some of these technologies (e.g. 3GPP LTE).Page 32 (41)


<strong>WINNER</strong> <strong>II</strong> D6.11.2 v1.0Ubiquitous coverage means that users should be able to use mobile communication services whilst on themove. At present only aircraft are exempt from this expectation, there<strong>for</strong>e <strong>for</strong> the scenario we assume thatusers get services provided to cars, buses, trains <strong>and</strong> so on. The most challenging of these transportationtypes are high speed trains, which may reach speeds of up to 350 km/h.This set of assumptions is <strong>for</strong> the challenging aspect of providing coverage <strong>and</strong> capacity to high speedtrain lines. Where relaying is considered as a solution <strong>for</strong> this case the in-train (RN to UT) deployment islikely to be very similar to the scenarios/solutions <strong>for</strong> a single-hop deployment (see Local Area scenario).In the WA aspect relaying is important <strong>for</strong> the communication from the BS to the train. A WAdeployment scenario is shown in Figure 4.5.RNUTRNBS RN UTBS: Base StationRN: Relay NodeUT: User TerminalFigure 4.5: WA Deployment Scenario: above roof top, high power, lower user densityThe high-level deployment scenarios which can in general be considered under wide area defined in<strong>WINNER</strong> I are listed in the next table:NameUbiquitouscoveragedeploymentof <strong>WINNER</strong>in citiesUbiquitouscoveragedeploymentof <strong>WINNER</strong>where it willoverlap withdeploymentsfromMetropolitan<strong>and</strong> LA CGTable 4.15: High – level WA CG scenarios descriptionCoveragePropagationTraffic DensityMobilityConditions(Indicative)SuburbanTypical Urban[Medium]Bad Urban 0 – 70 km/h [Medium]/[High]UbiquitouscoverageUbiquitouscoverageOutdoor toIndoorLOS – StationaryFeederSuburbanTypical UrbanBad urbanOutdoor toIndoor[Low]-[High]0 km/h [Low]/[Medium]0 – 70 km/h[Medium][Medium]/[High][Low]-[High]LOS – Feeder 0 km/h [Low]/[Medium]Ubiquitouscoverage inrural areasUbiquitouscoverageRural 0-200 km/h [Low]LOS - MovingNetworks(Feeder)0-300 km/h [High]Page 33 (41)


<strong>WINNER</strong> <strong>II</strong> D6.11.2 v1.0The following script is an example of WA scenario:Main actor: Dimitra, female, 28 years oldLocation: Urban area (a city of Europe)Occupation: Free lancerDate: A day in 2015Dimitra is a free lancer working <strong>and</strong> is active in business development <strong>for</strong> IT companies. She needs tohave ubiquitous access every day <strong>and</strong> be able to exchange Emails with proposals, technical offers <strong>and</strong>multimedia messages. Everyday she wakes up <strong>and</strong> after the breakfast she goes to her office <strong>and</strong>authenticates wirelessly with her PDA device. From that she gets her first Emails <strong>and</strong> she reads theappointments <strong>for</strong> the day, as well as their status (e.g. confirmed, cancelled, etc.).Around 11:00 in the morning she goes in the car <strong>and</strong> by entering, the mobile phone that constantlysynchronizes with the PDA, transfers the location of the venue to the car navigation system thatsubsequently traces the optimal way. While in the car, the UT is switched on <strong>and</strong> selects different RATsto connect due to the fact that there are areas where there is no coverage of <strong>WINNER</strong> systems. Theh<strong>and</strong>over is per<strong>for</strong>med seamlessly by the network in the cast that Dimitra downloads an Email or if shehas a voice call.In addition to that, the UT sets up the songs playing list to the car’s audio system. Suddenly she receives avoice message that is left in her mailbox, while she had another voice-call. Due to traffic congestion, sheis redirected to follow another link. This in<strong>for</strong>mation is transferred to her UT <strong>and</strong> the latter updates the carnavigation system.Table 4.16: WA – based scenarioScriptExtractServiceClassUserDensityUserMobilityAssociatedTraffic ModelEnvironment Coverage Implicationsauthenticateswirelesslywith her PDAdeviceMultimediamessagingbut with alow delay(


<strong>WINNER</strong> <strong>II</strong> D6.11.2 v1.0messagingbackbonedue to cartrafficcongestionGeographicdatacastMediumMedium(0 – 70km/h)Internet/browsing,InteractiveactivityUrban50 –1000 mConnectivitybetween AP<strong>and</strong> <strong>WINNER</strong>backbone4.2.4 Summary of Parameters <strong>for</strong> the <strong>Key</strong> <strong>Scenarios</strong>In this section the main parameters <strong>for</strong> modelling of services, traffic, <strong>and</strong> user behaviour <strong>for</strong> the conceptgroup evaluation scenarios are summarised based on the discussion above <strong>and</strong> [WIN2D6131].Table 4.17: Environment specific parametersBase coverage urban(WA)Microcellular (MA)Indoor (LA)Two-dimensionalwithout topographicdetailsTwo-dimensional regulargrid of buildings(“Manhattan grid”)One floor of a buildingwith regular grid ofrooms <strong>and</strong> corridors,three dimensionalEnvironmentcharacteristicsNumber of buildings:11x11Building block size:200x200 mStreet width: 30 mArea per floor: 5000 m 2Number of rooms: 40Rooms size: 10x10x3 mNumber of floors: 3Corridor size: 100x5x3mUser distributionmodel (atsimulation startup)User density(users/km 2 )Applications basedon voice <strong>and</strong>instant messagingUser density(users/km 2 )Other kind ofapplicationsSimplified service/ traffic mix <strong>for</strong>simulationTraffic loadAll users are uni<strong>for</strong>mlydistributed in the entireareaSuburban: 2000Rural: 200Suburban: 500Rural: 5019% LAN/Web Access9% File Transfer41% Voice12% Streaming19% Other64 kbps – 512 kbps(voice – browsingAll users are uni<strong>for</strong>mlydistributed in the streetsTypical urban: 11000Typical urban: 110022% LAN/Web Access11% File Transfer38% Voice14% Streaming15% Other64 kbps – 512 kbps(voice – browsing)90% of users areuni<strong>for</strong>mly distributed inrooms <strong>and</strong> 10% of usersare uni<strong>for</strong>mly distributedin corridorsIndoor small(residential)/denseurban: 26400Indoor small(office)/dense urban:30000Indoor small/suburban:6600Indoor small(residential)/denseurban: 2640Indoor small(office)/dense urban:15000Indoor small/suburban:440024% LAN/Web Access17% File Transfer36% Voice9% Streaming14% OtherFrom 64 kbps (voice) to5 Mbps (videostreaming)Page 35 (41)


<strong>WINNER</strong> <strong>II</strong> D6.11.2 v1.0Typical devicetypesUser mobilitymodel (class <strong>II</strong>I<strong>and</strong> IV)User mobilitymodel (class I <strong>and</strong><strong>II</strong>)User traffic model(class <strong>II</strong>I)User traffic model(class I <strong>and</strong> <strong>II</strong>)Base coverage urban(WA)• Palmtop• Mobile phone• Wearable terminal• Fixed <strong>and</strong> identicalspeed |v| of all UTs• |v| ∈ {3, 50, 120 km/h}∠v =θ v ∼ U(0 o , 360 o )See section 4.1.5.4(Vehicular environment(typical urban) mobilitymodel) <strong>and</strong> section4.1.5.5 (Ruralenvironment mobilitymodel)Microcellular (MA)• Laptop• Mobile phone• Wearable terminal• Palmtop• Fixed <strong>and</strong> identicalspeed |v| of all UTs• |v| ∈ {3, 50 km/h}∠v: UTs only movealong the streets theyare in. Direction isr<strong>and</strong>om <strong>and</strong> bothdirections are equallyprobableSee section 4.1.5.3(Outdoor to indoor(dense urban) mobilitymodel)Indoor (LA)• Laptop• Desktop• Wearable terminal• Mobile phone• Palmtop• Fixed <strong>and</strong> identicalspeed |v| of all UTs• |v| ∈ {0, 5 km/h}∠v =θ v ∼ U(0 o ,360 o )See section 4.1.5.1(Indoor small (office)environment mobilitymodel) <strong>and</strong> section4.1.5.2 (hotspotenvironment mobilitymodel)Single traffic flow per user; Full queue per user.--- or alternatively ---Number of data packets of size K bits is drawn from a r<strong>and</strong>om distribution <strong>for</strong>each queue at the beginning of each snapshot.The packets in each queue have a linearly increasing expiration date representingan equidistant arrival time.No new data packets arrive during a snapshot.See [WIN1D72]5. The impacts of scenarios on economic aspectsThe main approach regarding the economic aspects of <strong>WINNER</strong> <strong>II</strong> should be a continuation of the workper<strong>for</strong>med in the previous phase, where focus was given on the identification of roles <strong>and</strong> actors in thebusiness field as also on their relationships, rather than the calculation of cost <strong>and</strong> revenue flows. It is tobe noted here that <strong>for</strong> this purpose, the relevant diagrams used arrows to indicate money <strong>and</strong> in<strong>for</strong>mationflows as is explicitly stated in D.1.4. It is proposed to avoid any implication regarding money flow <strong>and</strong>consider only relations in a more abstract level (using only solid lines <strong>and</strong> not arrows indicating any kindof flow). To encompass all possible potential combinations of actor/relation in the value chain,differentiations will be a result of specific instantiations of services, rather than the services themselves.During <strong>WINNER</strong> I, a generalized business framework was introduced, in which all potential actors <strong>and</strong>all potential relationships were identified. The purpose of this generic framework was to encompass allpossible potential combinations of actor/relations. This proof-of-concept was supported with specificexamples, in the <strong>for</strong>m of domains, which <strong>for</strong>med a rather high level instantiation of frameworks <strong>for</strong> theprovisioning of various type of services.5.1 Economic frameworkIn the first phase of <strong>WINNER</strong>, there has been an ef<strong>for</strong>t to try <strong>and</strong> identify the relevant aspectsincorporated within the business modelling of <strong>WINNER</strong> services instantiations, see [WIN1D13] <strong>and</strong>[WIN1D14]. The result of this work was mainly centred on the identification of key players of theeconomic l<strong>and</strong>scape as also the potential interactions that could be established between them in thePage 36 (41)


<strong>WINNER</strong> <strong>II</strong> D6.11.2 v1.0context of service provisioning. This approach resulted to the design of a generalized <strong>and</strong> abstractbusiness framework that depicts a view of the anticipated <strong>WINNER</strong> business scenery.As stated be<strong>for</strong>e, the approach that was adopted throughout the development of the generalised businessframework that was introduced in the previous phase of the project has been based on the identification ofas many as possible potential business actors, i.e. participants in the overall value chain <strong>for</strong> theprovisioning of services that are in the scope of the anticipated <strong>WINNER</strong> plat<strong>for</strong>m. Furthermore <strong>and</strong> oncethese actors were identified, the next step was to address the issue of their potential interplay within thebusiness l<strong>and</strong>scape both in terms of money <strong>and</strong> in<strong>for</strong>mation flow. The process of actors-relationshipsidentifications yielded the so – called generalised business framework that is depicted within thefollowing figure:Figure 5.1: Generalised Business FrameworkThe main usage of this generic framework is to provide the sum of actors – relationships <strong>and</strong> serve as aversatile basis which will be adopted according to business domains or specific scenariosIt is to be noted that the purpose of the development of this framework was not to serve as an extensivestudy of all potential business – market aspects, since it is evident that apart from money – in<strong>for</strong>mationflow there are other types of relationships that may exist between the actors (e.g. trust relationships), norin any case the list of actors can be considered exhaustive. The approach undertaken in [WIN1D14]which is more thoroughly analysed in this document through more extended scenario examples is tocreate an abstract (<strong>and</strong> not quantitative nor qualitative) sketch of the envisioned business aspects that maybe incorporated in the provisioning of <strong>WINNER</strong> – related services.However, as stated be<strong>for</strong>e, the main outcome of this overall process has been the identification of actors<strong>and</strong> their relationships. This concept was further supported by the instantiation of specific examples thatPage 37 (41)


<strong>WINNER</strong> <strong>II</strong> D6.11.2 v1.0were adjusted to the intricacies of three example domains, namely the traditional mobiletelecommunications domain, the broadcast domain <strong>and</strong> finally the fixed internet domain.As an extension to already existing work <strong>and</strong> the results that were established within the business contextduring phase I of <strong>WINNER</strong>, this chapter will provide a mapping of the adopted business framework intothe key scenarios that are cited in this document. The purpose of this process is to give an overview <strong>and</strong>some initial estimates on business <strong>implications</strong> imposed by the service structure as this is envisionedwithin the anticipated <strong>WINNER</strong> environment. It is evident from the list that follows that the business –oriented decomposition deviates from the scenario analysis that preceded <strong>and</strong> focused on the CG – based<strong>implications</strong>.For the detailed list of business actors involved as also a short description of their roles, see [WIN1D14].Throughout the whole scenario, involvement of the actors Equipment Supplier <strong>and</strong> End User is implied,unless otherwise stated. The decomposition of each scenario element into certain actors is by no meansrestrictive but rather serves as an initial approach to the business analysis. Other configurations betweenactors may also be possible.5.2 Technical <strong>implications</strong> of wireless ecosystemsIn [WIN1D14] a generic business framework was developed in order to describe the ever-changingmultitude of possible wireless ecosystems. A key feature of <strong>WINNER</strong> is the flexibility <strong>and</strong> configurabilityto support different ecosystems. Naturally, since <strong>WINNER</strong> defines technology <strong>for</strong> wireless radio accessonly, the discussion will not be on these ecosystems as such, but shall focus on possible technical<strong>implications</strong> of these business models, that need to be considered within <strong>WINNER</strong>. In an extension of<strong>WINNER</strong> I work, the following section will highlight some specific scenarios <strong>for</strong> ecosystems that mightraise such technical <strong>implications</strong>:Scenario: The network provider (the “owner” of the subscribers) is different from the networkowner (operating the transmission network).Technical Implications:• Can extra signalling <strong>and</strong> measurement reports increase support <strong>for</strong> such a fragmented ecosystem,e.g. allowing a network provider to specialize in certain service classes <strong>and</strong> to aggregatedynamically capacity from different network operators?• Will the spectrum technologies be affected if we do not consider one entity selecting the bestsolution (from a spectrum point of view) but competing transmission network operators willoffer available transmission b<strong>and</strong>widths with certain QoS guarantees <strong>and</strong> the network provideronly needs to pick the best? How will the overall system per<strong>for</strong>mance be affected by thisapproach?• Service level agreements (SLA) between network provider <strong>and</strong> transmission network owner thatis required to ensure service QoS.• Transparent <strong>and</strong> common (joint) billing plat<strong>for</strong>m is required to process the user calls/sessionsindependently of the network transmission owner (one single bill to the user).Scenario: The network owner is a small company or a private man (cf. e.g. hotspots)Technical Implications:• Low price, ease of use, self-configurability are key requirements.• How is the network operator able to manager with traffic load situations? Is it required toh<strong>and</strong>over to an upper cell layer in a different network operator even degrading the service QoS,i.e., from WLAN to UMTS? How the billing process is per<strong>for</strong>med?• Could the network users be able to connect to the best ISP according the service <strong>and</strong> contentsavailability, tariffs promotions, etc. <strong>and</strong> through different transmission networks operators(XDSL, wireless systems, satellite)?Page 38 (41)


<strong>WINNER</strong> <strong>II</strong> D6.11.2 v1.0Scenario: Coverage is provided by several (competing) network operators.Technical Implications:• Which technical enablers are required <strong>for</strong> network-based association <strong>and</strong> h<strong>and</strong>over algorithms,which <strong>for</strong> algorithms based on user preferences, which <strong>for</strong> a combination of both (networkdetection, association, etc.)?• UT should be able to rank <strong>and</strong> select the best network operator according to the user preferencesor profile (default network operator, call cost, service availability, etc.) <strong>and</strong> networkmeasurements reports (signal level, network load, etc.).• Load sharing <strong>and</strong> congestion control mechanisms between network operators.• Inter-system h<strong>and</strong>over policy mechanisms (required networks reports in<strong>for</strong>mation to userterminal to ensure the QoS of ongoing calls, i.e. coverage, signal quality, network load, serviceavailability, etc.).• Extra signalling <strong>for</strong> billing in<strong>for</strong>mation exchange between operators (CDRs) or in a commonbilling plat<strong>for</strong>m (one single bill to the user).5.3 Service classes <strong>and</strong> scenarios classification in the overall value chainDuring the previous phase of <strong>WINNER</strong> project, a lot of emphasis has been put in the consideration ofhigh level issues, something that practically translates to the study <strong>and</strong> analysis of the variouscharacteristics of current <strong>and</strong> future mobile services.In fact, a user-centric point of view that was adopted in <strong>WINNER</strong> phase I yielded significant results interms of service categorization in various levels of aggregation, which were based in various services’attributes including traffic, delay <strong>and</strong> b<strong>and</strong>width constraints, etc.The main focus of this chapter is to provide an insight into actual market <strong>and</strong> business aspects of thesemobile services, as this is depicted by related surveys <strong>and</strong> articles. A brief analysis of <strong>for</strong>ecasts (whereveravailable) <strong>and</strong> evaluations will follow, based on a short online survey conducted <strong>for</strong> the purpose ofproviding an in<strong>for</strong>mative feedback regarding the essential market trends as these are being <strong>for</strong>med in thecurrent l<strong>and</strong>scape of mobile services. Whenever possible, there will be a mapping of the reports cited tothe respective <strong>WINNER</strong> services (or service classes).One of the first results that can be extracted by a brief overview of the mobile services market status istheir proliferation <strong>and</strong> their ever-growing penetration rate to mobile users. In terms of specific figures,there are surveys 3 predicting a rise of total revenues at 198.4€ billion in 2011, versus 138.4€ billion in2005, which corresponds to an increase of 43% within 6 years. In a more short term prediction, therelevant mobile services revenues will account <strong>for</strong> almost 20% of the total mobile operators profits 4 .Eventually, penetration of mobile services is also expected to rise <strong>and</strong> average revenue per user isexpected to have an increase of 20% from 31.3€ in 2005 to 37.5€ in 2011. As will be substantiatedthrough other relevant researches, main driving <strong>for</strong>ce behind this market drift is mainly the constant need<strong>and</strong> usage of voice <strong>and</strong> messaging services alongside with the great impact of multimedia applications tonew generations of users.Regarding mobile telephony voice services (<strong>WINNER</strong> service class: Simple Telephony <strong>and</strong> Messaging),although it still remains among the most popular <strong>and</strong> widely used services, the predictions regarding theexpected operator’s incomes which will be based on this class of applications are rather pessimistic, <strong>and</strong>there is a slow anticipated revenue grow rate of about 4.5% until 2007 in developed markets (WesternEurope <strong>and</strong> North America) (fixed voice revenues are on contrast more likely to present a slight fall of0.5%). The relevant values are more optimistic in developing markets where the respective grow isestimated in about 16%. Worldwide, profits of mobile voice services are expected to account <strong>for</strong> about50% of total voice revenues within the next two years. Another important aspect emphasized by the sameresearch that cites the above numbers is an observed tendency of replacement of fixed voice services by3 http://www.ecommercetimes.com/story/51490.html4 http://www.3g.co.uk/PR/Jan2004/6347.htmPage 39 (41)


<strong>WINNER</strong> <strong>II</strong> D6.11.2 v1.0mobile ones, with limiting factors of this process mainly being the cost <strong>and</strong> the reluctance of users ofab<strong>and</strong>oning their fixed lines 5 .On the other h<strong>and</strong>, messaging services will most likely constitute one of the most promising servicesectors in terms of economic impact, since they are expected to will generate two thirds of global servicesrevenues by 2008 6 .A key service that is going to contribute to the widespread of messaging applications is mobile instantmessaging (MIM) (<strong>WINNER</strong> service class: Simple Interactive applications). Reports state that operators,having <strong>for</strong>eseen this new shift of dem<strong>and</strong> by mobile users towards mobile instant messaging services arein the process of implementing customized solutions <strong>for</strong> this type of applications in order to establishtheir position in the overall value chain. The importance of this genre of applications is also emphasizedby the joint announcement made by 15 mobile operators worldwide that are about to start implementinginteroperable MIM services. The competition is however expected to be rough in the struggle <strong>for</strong>prevalence in this business area, since other parties are expected to bring in the field already widespreadinstant messaging applications, such as MSN or Yahoo/AOL messengers. Similar reports furtherunderline the importance of adopting a significant diversification between SMS <strong>and</strong> MIM, so as to keepthese revenue sources as distinct as possible <strong>and</strong> making the most out of both of them. An overview of thecurrent mobile instant messaging market status in Western Europe reveals a customer base of about 5.8million users, which is expected to rise to about 34 million by the end of next year 7 .Despite however the constant popularity of SMS <strong>and</strong> the anticipated widespread of MIM, the MMS(<strong>WINNER</strong> Service class: Multimedia Messaging) market remains rather constrained <strong>and</strong> this is mainlyattributed to pricing issues, since according to recent surveys MMS remain on average about 4-5 timesmore expensive than the SMS, discouraging users of making use of the specific services.One of the most promising areas in terms of expected growth of both users <strong>and</strong> respective revenues arethe services that relate with the concept of entertainment. In total, the entertainment – related services arethe second largest revenue generator while they are expected to account <strong>for</strong> just over a fifth of totalrevenues in 2008 8 .Trying to break down the group of services encompassed within the concept of user – entertainment, <strong>and</strong>to make more concrete evaluations regarding impact <strong>and</strong> penetration rate to mobile customers we see thefollowing:Among the most promising services are the ones related to mobile music, the main contributing marketbeing the one related to ring tones downloads (<strong>WINNER</strong> service: File Exchange), while dem<strong>and</strong> <strong>for</strong> fulltrack downloads (<strong>WINNER</strong> service class: File Exchange) <strong>and</strong> streaming audio (<strong>WINNER</strong> service class:Data <strong>and</strong> Media Telephony) are also gaining interest 9 .On the other h<strong>and</strong>, user dem<strong>and</strong> <strong>for</strong> mobile TV is reported to remain rather modest. In a survey conductedby YankeeGroup, only 11% of participants expressed their interest regarding this service, the lack ofpopularity being mainly attributed to the high cost (the report provides a relevant cost estimate of 15€ permonth) 10 .Predictions related to mobile video (<strong>WINNER</strong> service classes: Video Streaming <strong>and</strong> High Quality VideoStreaming) are rather ambiguous, since most of the researches point out to some <strong>implications</strong> related tothe growth or relevant services, most importantly the lack of commonly agreed st<strong>and</strong>ards <strong>and</strong> viablebusiness models, the need <strong>for</strong> content protection <strong>and</strong> the high price of h<strong>and</strong>held devices able to supportthese applications.Regarding other services outside the area of entertainment, there has been a lot of interest in mobilewallet applications, especially in the US, where according to specific <strong>for</strong>ecasts mobile subscribers usingtheir h<strong>and</strong>held devices <strong>for</strong> executing economic transactions will reach 25 millions by 2011. Mostimportant <strong>implications</strong> in this category include the additional cost incorporated by service providers <strong>and</strong>security risks.5 http://www.thefeaturearchives.com/topic/Business/Toujours_Voice.html6 http://www.3g.co.uk/PR/Jan2004/6347.htm7 http://www.iht.com/articles/2006/07/10/business/wireless11.php; www.telecomsinfo.com8 http://www.3g.co.uk/PR/Jan2004/6347.htm9 http://www.mobilemarketingmagazine.co.uk/stats/index.html10http://www.yankeegroup.com/public/news_releases/news_release_detail.jsp?ID=PressReleases/Euromultimedia_6_12_06.htmPage 40 (41)


<strong>WINNER</strong> <strong>II</strong> D6.11.2 v1.0There has also been optimistic reports regarding the future of mobile Location Based Services (<strong>WINNER</strong>service class: Real Time Collaboration <strong>and</strong> Gaming), where the next five years will see an average annualgrowth rate of 84% is expected. However, according to ITU location in<strong>for</strong>mation constitutes private data,<strong>and</strong> all service implementations must take into consideration local legislations that h<strong>and</strong>le the possibilityof exploitation of such in<strong>for</strong>mation.6. ConclusionsDuring <strong>WINNER</strong> phase I, an extensive research in the scope of <strong>WINNER</strong>’s scenarios <strong>and</strong> serviceclassification was per<strong>for</strong>med through the analysis of the different elements linked to usage scenarios[WIN1D14].An overview of the different contexts of the <strong>WINNER</strong> scenarios <strong>and</strong> their relationships is provided <strong>for</strong>better underst<strong>and</strong>ing to the reader in this deliverable.The focus of this deliverable is to identify <strong>and</strong> characterise the most relevant scenarios in scope of the<strong>WINNER</strong>, selected as key scenarios <strong>for</strong> proof-of-concept, aligned with CGs. <strong>Key</strong> scenarios encompassdifferent aspects such as physical layer modes <strong>and</strong> parameterisation of the <strong>WINNER</strong> system <strong>and</strong> focus onchallenges in system requirements <strong>and</strong> system design [WIN2D6131].Further analysis on the service usage patterns <strong>and</strong> traffic characterisation was driven <strong>for</strong> traffic loaddimensioning using defined traffic models associated with relevant scenarios characteristics such as userdensity, user distribution <strong>and</strong> user mobility. Typical usage cases in the evaluation process shall beprioritised based on the most used applications <strong>and</strong> key scenario parameters with relevance <strong>for</strong> <strong>WINNER</strong>in terms of the system design.An extension of the economic framework started in phase I is analysed, deriving the <strong>implications</strong> atservice level rather than taking into account the value chain <strong>for</strong> the different players or actors involved. Apreliminary analysis of the technical <strong>implications</strong> of wireless ecosystems is provided in order to evaluatethe flexibility <strong>and</strong> configurability of <strong>WINNER</strong> system upon different deployment scenarios, i.e. networkproviders, service providers, contents providers <strong>and</strong> other actors in the business models.7. References[WIN1D11] IST-2003-507581 <strong>WINNER</strong>, “D1.1 First Economic <strong>and</strong> Technical Evaluations perScenario”, July 2004[WIN1D12] IST-2003-507581 <strong>WINNER</strong>, “D1.2 Intermediate requirements per scenario”, March2005[WIN1D13] IST-2003-507581 <strong>WINNER</strong>, “D1.3 Final usage scenarios”, July 2005[WIN1D14] IST-2003-507581 <strong>WINNER</strong>, “D1.4 Final requirements per scenario”, November 2005[WIN2D6131] IST-4-027756 <strong>WINNER</strong> <strong>II</strong>, “D6.13.1 <strong>WINNER</strong> <strong>II</strong> Test scenarios <strong>and</strong> calibration casesissue 1”, June 2006.[UMTS30.03] ETSI TR 101 112 “Selection procedures <strong>for</strong> the choice of radio transmissiontechnologies of the UMTS (UMTS 30.03 version 3.2.0)”, v 3.2.0, April 1998[SCE+05] Forge, Simon, Colin Blackman <strong>and</strong> Erik Bohlin, “The Dem<strong>and</strong> <strong>for</strong> Future MobileCommunications Markets <strong>and</strong> Services in Europe”, Institute <strong>for</strong> ProspectiveTechnological Studies, April 2005[JF05] Ferreira, Jaime <strong>and</strong> Fern<strong>and</strong>o Velez, “Enhanced UMTS services <strong>and</strong> applicationscharacterisation”, Telektronikk, 2005Page 41 (41)

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!