A global initiative ofDelivered by

App store accreditationVersion 2 June 2011

1. Introduction1.1 Objectives of this document

If you wish to sell your application via the various Movistar and O2 App Stores your application will need to pass the BlueVia App Store accreditation process. This document describes that process and the tests that will be conducted on your application.

The BlueVia App Store Accreditation process is provided by our partner Sogeti.

Hint: If you wish to just plug in the BlueVia API’s and distribute your application independently of Telefonica then this accreditation policy will not apply to you.

2. The application tests2.1.1.1 Installation

We will verify that your application correctly installs on the intended device. Tests covered in this step include:

• Therequiredfilesandresourcesaresuccessfullycopiedtothedevicememory (or to removable memory as appropriate)

• Thedevicedisplaysamessageindicatingthattheinstallationhasendedsuccessfully.

• Ashortcutiscreatedandnoerrorsappearwhentheapplicationislaunched.

Hint: The Installation test is an entry level criteria test, meaning if one of these installation tests fails then your application will be rejected, and no additional testing will be conducted.

2.1.1.2 BlueVia terms & conditions and content guideline compliance

We will verify that your application complies with the BlueVia Terms & Conditions and that the content of your application conform to the BlueVia content guidelines.

To do this, we will use the same documents that are published on BlueVia.com:

• http://bluevia.com/en/page/view/nodepath/boilerplate.TermsAndConds

• http://bluevia.com/en/knowledge/getStarted.App-Stores-Content-Policy

Using the Launch to store form on Bluevia.com you must also ensure you include your contact information, application metadata, price, and the App Stores you wish to submit the application into.

Wewillcheckthattheapplicationcomplieswiththetermsandconditionsandcontent policy for each country you wish to publish into.

Hint: The terms & conditions & policy test is an entry level criteria test, meaning if one of these tests fails then your application will be rejected, and no additional testing will be conducted.

Your application must support the primary regional language of the store you wish to publish into or English as appropriate.

Ifyourapplicationismulti-lingualwewillverifythattheapplicationofferstheoption to switch to the primary regional language, or includes English.

The application will fail the localisation test if the mandatory language for each region is not supported and selectable.

2.1.1.3 Correct categorisation of your application

To ensure your application is published into the correct category of the variousMovistarandO2AppStores,wewillcheckthatyourapplicationmatches the application categorisation option(s) you selected during the submission process.

Hint: If your application fails the categorisation test we will send youareportdetailingthefailureandwillre-categorisemetadata of your application on your behalf. Failure of this test will not result in the rejection of your submission.

2.1.1.4 Correct Localisation

Region Primary languages

Spain Spanish

Argentina Spanish or English

Germany German or English

2.1.1.5 Antivirus scan

This test will scan for the presence of virus and malwares inside your application. It is a condition of the BlueVia terms and conditions that you deliver applications free of virus and malware.

Hint: If your application fails the antivirus test your application willberejected.Telefonicareservestherighttotakeactionagainst any breaches in the service terms and conditions.

2.1.1.6 Networkconfigurationpersistence

We will verify that the installation process does not modify the device’s existingnetworkconfiguration.

Testscoveredinthisstepincludethepostinstallverificationofthefollowingconfigurationsettings:

• APN

• DNS

• SIP

• Proxy

• ConnectionUser/password

Theapplicationwillfailthenetworkconfigurationtestifanymodificationsaremadetotheexistingdeviceconfigurations.

2.1.1.7 Network Impact

Toverifytheimpactonthenetworkbyanapplication,wewillexecute two tests:

• Usetheapplicationtogeneratetraffic.Wewillverifythatthegeneratedtrafficisdirectlyrelatedtotheuseractivity.

• Monitorthenetworktrafficgeneratedbytheapplicationover1hourofconstant usage.

ThesetestsaredesignedtoidentifycodingerrorsintheapplicationlikeaTCP connection opening without posterior closing, which could have an unforeseenimpactonthenetworkand/orcreatethepotentialofbillshockfor the end user.

Theapplicationwillfailthenetworkimpacttestsif:

• Theapplicationattemptstoopenconnectionsinthesamecontextmorethan 3 times per minute

• Theapplicationopensmorethan3TCPconnectionssimultaneously.

Hint: You can read tips on how to write apps for the mobile networkenvironmenthere:http://bluevia.com/en/knowledge/getStarted.TechnicalGoodPractices

2.1.1.8 User Authorisation for charging events

We will verify that your application informs the end user of events that produce charges to the their Movistar or O2 bill, and that the user is correctly askedtogivetheirauthorisationforthecharge at the appropriate time.

BlueVia API usage

If your application uses one or more of the charge generating BlueVia APIs, we will verify that the application successfully launches the BlueVia Connect process at the appropriate time (liketheinitiallaunchoftheapplication),andaskstheusertoauthorisetheapplication to use the BlueVia APIs on their behalf.

The application with fail the authorisation tests if:

• Theapplicationdoesnotsuccessfullylaunch the BlueVia Connect process

• Iftheapplicationdoesnotsuccessfully complete the BlueVia Connect process

Other chargeable events

We shall also verify that:

• IfyourapplicationgeneratesSMS,MMS,orvoice/videocallsoutsideofthe provided BlueVia API’s then the user must always be informed before initiation.

• IfyourapplicationcangenerateSMS,MMS,orvoice/videocallsoutsideofthe provided BlueVia API’s we will verify that it does not generate:

- Morethan100SMSin10minutes

- Morethan50MMSin10minutes

- Morethan5voice/Videocallsin10minutes

The application will fail the user authorisation tests if:

• Iftheapplicationdoesnotwarntheuser of premium service usage

• Iftheapplicationexceedstheaforementioned limits.

Hint: further information on BlueVia API authentication can be found here: http://bluevia.com/en/knowledge/getStarted.Authentication

2.1.1.9 Graceful state transition

Your application must allow the user to pause and reactivate manually without a negative experience.

Tests covered in this step include:

1. The application is running

2.Theapplicationisswitchedtobackgroundmode

3.Theconnectionmanagerisinvoked

4. The connection is closed from within the connection manager

5.Theapplicationisswitchedinforeground

6.Theapplicationisswitchedbacktobackground

7. The connection is open from within the connection manager

8. The application is switched in foreground

The application will fail the graceful state transition test if any error messages are encountered.

2.1.1.10 Compatibility (when application is executed) with SMS service

2.1.1.11 Compatibility (when application is paused) with SMS service

Where applicable we will verify that sending and receiving SMS is possible during the execution of your application.

The application will fail the SMS compatibility test if sending or receiving an SMS effects the execution of your application.

Where applicable we will verify that sending and receiving SMS is possible whilst your application is paused.

The application will fail the SMS compatibility test if sending or receiving an SMS effects the execution of your application.

2.1.1.12 Compatibility (when application is executed) with MMS service

2.1.1.13 Compatibility (when application is paused) with MMS service

Where applicable we will verify that sending and receiving MMS is possible during the execution of your application.

The application will fail the MMS compatibility test if sending or receiving an MMS effects the execution of your application.

Where applicable we will verify that sending and receiving MMS is possible whilst your application is paused.

The application will fail the MMS compatibility test if sending or receiving an MMS effects the execution of your application.

2.1.1.14 Compatibility (when application is executed) with WEB service

2.1.1.15 Compatibility (when application is paused) with WEB service

Where applicable we will verify that using the Web browser is possible during the execution of your application.

The application will fail the web service compatibility test if using the Web browser effects the execution of your application.

Where applicable we will verify that using the Web browser is possible whilst your application is paused.

The application will fail the web service compatibility test if using the Web browser effects the execution of your application.

2.1.1.16 Compatibility (when application is executed) with WAP service

2.1.1.17 Compatibility (when application is paused) with WAP service

Where applicable we will verify that using the WAP browser is possible during the execution of your application.

The application will fail the WAP service compatibility test if using the WAP browser effects the execution of your application.

Where applicable we will verify that using the WAP browser is possible whilst your application is paused.

The application will fail the WAP service compatibility test if using the WAP browser effects the execution of your application.

2.1.1.18 Compatibility (when application is executed) with voice calls

2.1.1.19 Compatibility (when application is paused) with voice calls

Whereapplicablewewillverifythatmakingandreceivingcallsispossibleduring the execution of your application.

Theapplicationwillfailthevoicecallservicecompatibilitytestifmakingandreceiving calls effects the execution of your application.

Whereapplicablewewillverifythatmakingandreceivingcallsispossiblewhilst your application is paused.

Theapplicationwillfailthevoicecallservicecompatibilitytestifmakingandreceiving calls effects the execution of your application.

2.1.1.20 Compatibility (when application is executed) with video call service

2.1.1.21 Compatibility (when application is paused) with video call service

Whereapplicablewewillverifythatmakingandreceivingvideocallsispossible during the execution of your application.

Theapplicationwillfailthevideocallservicecompatibilitytestifmakingandreceiving video calls effects the execution of your application.

Whereapplicablewewillverifythatmakingandreceivingvideocallsispossible whilst your application is paused.

Theapplicationwillfailthevideocallservicecompatibilitytestifmakingandreceiving video calls effects the execution of your application.

3 Device Grouping

Your application will be tested against a “family” of similar devices, meaning whenyouuploadyourapplicationwewilltestthatitworksagainstallofthedevices in that category.

Asyoumayknowthemobileenvironmentisfragmented,sothisapproachisdesignedtosaveyoumoneyasyoudonothavetomakemultiplesubmissions for each individual handset type. We have grouped devices supportedintheMovistarandO2AppStores,takingintoaccountcommonfeatures to ensure compatibility.

Pleasetakealookattheavailablegroupingsonpages13-16andcheckoutthe devices included in them.

3 Device Grouping

Platform Devices

Samsungkeyboard

SonyEricssonJP-7

NokiaS603rdFP2

NokiaS603rdFP1

Sony Ericsson JP 8.3

NokiaS405th

Samsung-S3550;Samsung-GT-S3500/GT-3500;Samsung-SGH-A706;Samsung-SGH-D800;Samsung-SGH-D820;Samsung-SGH-D836;Samsung-SGH-D900;Samsung-SGH-G600;Samsung-SGH-G800;Samsung-SGH-U600;Samsung-SGH-U800;Samsung-SGH-U900;Samsung-T809

SonyEricsson-K800i;SonyEricsson-K810x;SonyEricsson-S500x;SonyEricsson-W850x;SonyEricsson-K770x;SonyEricsson-K790;SonyEricsson-K800i;SonyEricsson-S500;SonyEricsson-T650x;SonyEricsson-W580x;SonyEricsson-W880x

Nokia-E75;Nokia-6220classic;Nokia-N78;Nokia-N79;Nokia-N85(3G);Nokia-N96;Nokia-5320;Nokia-5630XpressMusic;Nokia-6210Navigator;Nokia-6700;Nokia-6710Navigator;Nokia-N78;Nokia-N86

Nokia-N95;Nokia-5700XpressMusic;Nokia-6120classic;Nokia-5700;Nokia-6110Navigator;Nokia-E51;Nokia-E66;Nokia-N81;Nokia-N958GB

SonyEricsson-C702x;SonyEricsson-W980x;SonyEricsson-C902x;SonyEricsson-W595x;SonyEricsson-W760i;SonyEricsson-Z780

Nokia-6600slide;Nokia-7610Supernova;Nokia-2700classic;Nokia-5130;Nokia-5220Xpressmusic;Nokia-5310XpressMusic;Nokia-5610;Nokia-6500classic;Nokia-6500slide;Nokia-6600Slide;Nokia-6600islide

3 Device Grouping

Platform Devices

SonyEricssonJP-8

NokiaS403rd

NokiaS605th

Samsungkeyboard

SonyEricssonJP-8.4

SonyEricssonJP-7

Samsung Touch Screen

SonyEricssonJP-6

SonyEricsson-K850x;SonyEricsson-W910i;SonyEricsson-Z750i;SonyEricsson-W890x;SonyEricsson-W995

Nokia-6300;Nokia-6233;Nokia-6131;Nokia-6300

Nokia-N97mini;Nokia-N97;Nokia-5800XpressMusic;Nokia-5530XpressMusic;Nokia-5230Xpressmusic;Nokia-X6;Nokia-C6

Samsung-E496;Samsung-E570;Samsung-E576;Samsung-E740;Samsung-J800;Samsung-S3100;Samsung-SGH-A736;Samsung-SGH-A767;Samsung-SGH-D500;Samsung-SGH-E380;Samsung-SGH-L700;Samsung-SGH-L760;Samsung-T459;Samsung-X576;Samsung-Z170;Samsung-Z240

SonyEricsson-C510x;SonyEricsson-W508x;SonyEricsson-C905x;SonyEricsson-W705

SonyEricsson-K610i;SonyEricsson-K550x;SonyEricsson-K530i;SonyEricsson-K610i;SonyEricsson-W710;SonyEricsson-Z710

Samsung-S3650;Samsung-SGH-F480i;Samsung-B5310CorbyQwerty;Samsung-F400;Samsung-S5600;Samsung-G400;Samsung-GT-S5620;Samsung-S8000(Jet);Samsung-S5230

SonyEricsson-W810x;SonyEricsson-W550i;SonyEricsson-W600;SonyEricsson-W302

3 Device Grouping

Platform Devices

Windows Mobile Large

Windows Mobile small

Android 1

Android 2

HTC-HD2;HTC-TouchHDT8282;HTC-TouchPro2;O2-XDATouchHD;Samsung-i8000(OmniaII);SonyEricsson-XperiaX2;Toshiba-TG02;Toshiba-TG01;Xda-Diamond2

HTC-Mega;HTC-P3451;HTC-P4351;HTC-TOUCHCRUISE;HTC-TYTN2;Motorola-Q9;O2-XDAOrbit;Samsung-GT-C6620;Samsung-I617;Samsung-i900Omnia;Xda-Guide

HTC-AndroidGeneric;HTC-G1Dream(AlternativeUA);HTC-G1Dream;HTC-G2Magic(AlternativeUA2);HTC-G2Magic(AlternativeUA);HTC-Hero;HTC-G2Magic;HTC-Tattoo(AlternativeUA);HTC-Tattoo;Huawei-U8110;Huawei-U8230;LG-GT540;LG-GW620(AlternativeUA);LG-GW620;Motorola-MB220;Samsung-GT-I5700;Samsung-GT-I7500(Galaxy)(AlternativeUA);Samsung-GT-I7500;SonyEricsson-XperiaX10(AlternativeUA);SonyEricsson-XPERIAX10mini;SonyEricsson-XPERIAX10minipro;SonyEriccson-XPERIAX8

HP-CompaqAirLife100;HTC-Desire(Bravo)(AlternativeUA);HTC-Desire(Bravo);HTC-DesireHD;LG-P350(Pecan);LG-P990(Optimus2X);Motorola-MB220Client;Motorola-MILESTONE;Samsung-GT-I9000(GalaxyS);Samsung-GT-I9003GalaxySL;Samsung-GT-S7070;SonyEricsson-XPERIAArc;SonyEricsson-R800;SonyEricsson-XperiaX10(SafariBrowser)

3 Device Grouping

Platform Devices

BlackBerrylarge

BlackBerrysmall

RIM-BB9000Bold;RIM-BB8900Curve;RIM-BB9700Onyx;RIM-BB9300;RIM-BB8520

RIM-BB8100Pearl;RIM-BB7230;RIM-BB7100;RIM-BB8110;RIM-BB7130;RIM-BB8120

4 Testing Fees

Eachapplicationsubmissionwillcost25eurosregardlessofthenumberofMovistarandO2AppStore’syoupublishinto.Pleasetakeintoaccountthatthis fee only covers one submission to the process. If your application does notpasstheaccreditationyouwillhavetofixtheissueshighlighted,resubmitand pay a second accreditation fee.

5 Reporting

Foreachsubmissionyouwillbesentanemailconfirmingtheresultofthecertificationprocess.Ifpositiveyourappwillbeplacedonsaleinyourchosen Telefonica App Store(s). If negative you will receive a full report highlightingtheissuesthatcausedthefailureincertification.

6 Turnaround

Itgoeswithoutsayingweaimtotestyourapplicationasquicklyaspossible,but our service level agreement with you is to complete accreditation within 5workingdays.

7 Feedback

Ifyouhaveanyquestionsorsuggestionsonhowwecanimproveouraccreditationprocess,pleasecheckouttheFAQ’sonBlueVia.com or contact support@bluevia.com.