loveus wp3 ROAD D05 v1 0 by nAnN0r

VIEWS: 0 PAGES: 24

									V1.0, 24 December 2002                                                                                             1




                                     IST–2000-30155 LoVEUS
                                                 Deliverable D05
     Trials Specification of the 2.5 G System and Terminal
                           Prototypes


Contractual Date of Delivery to the CEC                            :   30-09-2002
Actual Date of Delivery to the CEC                                 :   24-12-2002
Responsible                                                        :   ROAD
Editor(s)                                                          :   ROAD, ICOM, OGILVY, MOTOROLA,
                                                                       ARBONAUT, FHG, VODAFONE, UCL
Workpackage                                                        :   WP3
Security                                                           :   PU
Nature                                                             :   Report
Version                                                            :   1.0
Total number of pages                                              :   24



Abstract:

 This deliverable specifies the set-up to be implemented during 2.5 G trials, in what concerns the various
 system components of the LoVEUS application. It contains a description of the set-up of the testing
 environment, the objectives of each test, the data to measure (qualitatively or quantitatively) and the related
 success criteria. It also provides guidelines for system evaluation and the general outline of the
 questionnaires to be submitted to the system users.




Trials Specification of the 2.5 G System and Terminal Prototypes                              LoVEUS Consortium
2                                                                                IST-2000-30155




DOCUMENT HISTORY

     Date       Version      Status   Comments
     19-11-2002 0.1          Draft    First draft. Input from Road, Arbonaut, Vodafone,
                                      Motorola
     22-11-2002      0.2     Draft    Second draft. Input from Ogilvy
     09-12-2002      0.2.1   Draft     -“-
     18-12-2002      0.2.2   Draft    -“-. Input from ICOM
     19-12-2002      0.2.3   Draft    Additional input from Arbonaut, Ogilvy
     23-12-2002      1.0     Final    Input from UCL, FHG




LoVEUS Consortium
V1.0, 24 December 2002                                                                                                                                                             3



TABLE OF CONTENTS

EXECUTIVE SUMMARY ............................................................................................................................... 4

1      INTRODUCTION ..................................................................................................................................... 5
    1.1       PURPOSE ............................................................................................................................................... 5
    1.2       OVERVIEW ............................................................................................................................................ 5
2      PROTOTYPE MOBILE TERMINALS .................................................................................................. 6
    2.1     IPAQ PDA WITH GPS AND GPRS CARD .............................................................................................. 6
       2.1.1    HP iPAQ Pocket PC H3970......................................................................................................... 7
       2.1.2    HP Dual-Slot PC Card* Expansion Pack 216198-B21 ............................................................... 7
       2.1.3    Sierra Wireless ®AirCard 750 Wireless Network Card .............................................................. 7
       2.1.4    Pretec CF PCMICA Adapter EB2CFC1P ................................................................................... 7
       2.1.5    Pretec CF CompactGPS card ...................................................................................................... 7
       2.1.6    Garmin eTrex Summit™ GPS card .............................................................................................. 8
       2.1.7    PNI TCM2-20 3-Axis Magnetometer ........................................................................................... 8
    2.2     MOTOROLA A820, A830 MOBILE TERMINAL ........................................................................................ 8
3      LABORATORY TRIALS ......................................................................................................................... 9
    3.1     SELECTION OF THE TEST AREA ............................................................................................................. 9
    3.2     DESCRIPTION OF THE TEST-SITE ...........................................................................................................10
    3.3     SERVICES TO TEST DURING TRIALS ......................................................................................................11
       3.3.1    Services for AS1 ..........................................................................................................................11
       3.3.2    Services for AS2 ..........................................................................................................................11
       3.3.3    Services for AS3 ..........................................................................................................................11
    3.4     CONTENT TO BE USED FOR TRIALS .......................................................................................................11
       3.4.1    Vector data ..................................................................................................................................11
       3.4.2    Image data ..................................................................................................................................12
       3.4.3    Audio data ...................................................................................................................................12
       3.4.4    Video data ...................................................................................................................................12
       3.4.5    3-D reconstructions ....................................................................................................................12
    3.5     DESCRIPTION OF THE EXPERIMENTAL SET-UP ......................................................................................13
       3.5.1    Server components ......................................................................................................................13
       3.5.2    Client components .......................................................................................................................15
4      EVALUATION METHODOLOGY FOR LOVEUS APPLICATION ................................................18
    4.1     OVERVIEW OF APPROACH ....................................................................................................................18
    4.2     DETAILED EVALUATION STEPS ............................................................................................................19
    4.3     ANALYSIS: QUANTITATIVE & QUALITATIVE TESTS & MEASUREMENTS .............................................19
       4.3.1    Key Performance Indicators .......................................................................................................20
           4.3.1.1       GPRS IP Connectivity test ..................................................................................................................... 20
           4.3.1.2       GPRS connectivity with stored content server at Intracom .................................................................... 20
           4.3.1.3       GPRS connectivity and application performance for stored content ...................................................... 20
           4.3.1.4       Location update file monitoring from Vodafone to Intracom ................................................................ 21
           4.3.1.5       Application server triggers GIS, file preparation ................................................................................... 21
           4.3.1.6       Handover ................................................................................................................................................ 21
           4.3.1.7       MPEG4 Server & Client ........................................................................................................................ 21
       4.3.2    Measurement Plan - Benchmarking ............................................................................................21
    4.4     REPORTING: QUESTIONNAIRES TO BE SUBMITTED TO SYSTEM USERS .................................................23




Trials Specification of the 2.5 G System and Terminal Prototypes                                                                                      LoVEUS Consortium
4                                                                                                 IST-2000-30155




EXECUTIVE SUMMARY

This deliverable will specify the set-up to be implemented during laboratory and real-world trials, in what
concerns the various system components of the LoVEUS application.
The objective of this document is to describe the technical set-up that will combine the usability and the
functionalities required by the users. It also provides guidelines for system evaluation in order to assess its
acceptance by its users, acquire further suggestions concerning its functionality, as well as remove technical
obstacles. Two main sets of parameters have to be distinguished for a successful system evaluation:
        User Interface Parameters: that identifies the level of acceptance of the User Interface (UI) by the
         users
        Functionality Parameters: measuring the level of compliance of the system with the user
         requirements, upon which the system development was based
Thus, at a first stage, the testing environment and set-up will be defined. The evaluation method to be followed
is dictating the first prototype trial and the outcome is the level of acceptance of the system in terms of
functionality and means of accessing (UI) the functionality provided. At a second stage, the criteria and
methodology for usability evaluation, as well as for software and hardware quality assurance, are defined.




LoVEUS Consortium
V1.0, 24 December 2002                                                                                              5




1     INTRODUCTION

1.1       Purpose
This deliverable will specify aspects to be measured within the 2.5 G trials, in what concerns the various
components of the LoVEUS system. The deliverable will contain a description of:
          The set-up of the testing environment
          The objectives of each test and the data to measure (qualitatively or quantitatively)
          The related success criteria
          The general outline of the questionnaires to be used by the users of the system to evaluate the overall
           service acceptability and perceived usefulness for each application demonstrated.


1.2       Overview
The document is organised as follows:
Chapter 2 contains a description of the prototype terminals.
Chapter 3 presents in detail the testing environment: the test-site, as well as the experimental set-up.
Chapter 4 provides a brief description of the evaluation methodology to be followed for the LoVEUS first
prototype trials. It also gives some indication on the quantitative and qualitative tests and measurements to be
performed and provides suggestions on how to build questionnaires for the evaluation of the system.




Trials Specification of the 2.5 G System and Terminal Prototypes                                   LoVEUS Consortium
6                                                                                                    IST-2000-30155




2     PROTOTYPE MOBILE TERMINALS




                                       Figure 2:1 LoVEUS Mobile Terminal Components




2.1       iPAQ PDA with GPS and GPRS card
The solution of developing a PDA-based platform for the LoVEUS prototype will be sustained throughout the
2.5 G phase of the project, keeping in mind that the solution will be ported eventually into the Motorola
device, at a later stage.
Indeed, using Compaq’s iPAQ as a core platform, we do have now the possibility to read attached GPS card
information and further deliver it via Bluetooth and GPRS connections to the LoVEUS location server. Further
the device will be able to communicate bilaterally with the location server, in order to retrieve personally
profiled proximity search output to be displayed on the screen.
Requirements on the functionality of the client can be filled with the following additional client components:
          GPS device connected to iPAQ internally as PCMCIA card, externally via RS232 or with bluetooth
          GPRS modem connected to iPAQ internally as PCMCIA card, externally via RS232 or with bluetooth
          Digital compass module connected to iPAQ with RS232 interface

There are several routes to follow, when integrating the system. If the COMPAQ Bluetooth option is used, any
BT/GPRS phone can be regarded as a modem connected to LoVEUS server. On the other hand, using a two-
card slot jacket for the iPAQ, we can directly use an attached GPRS card. Now the question is whether we
would reserve the BT free for extended functions (as BT GPS) and thus leave us more degrees of freedom to
use the other card slot for the digital compass. On the other hand, by prioritising the BT connection for the
GPRS phone, we can try to connect the remaining add-ons to the twin card slots. We are certainly not
forgetting the usage of the serial interface, since our software for the Compaq controls also the serial to be used
for the messaging.



LoVEUS Consortium
V1.0, 24 December 2002                                                                                           7



After thorough investigation of the various scenarios and careful consideration of which ones are most
appropriate for LoVEUS, it has been decided to test the following client set-ups for the 2.5 G trials:
         iPAQ + Pretec GPS card with a PNI TCM2 digital compass, communicating via a Sierra Aircard
          GPRS card
         iPAQ + Garmin GPS card, communicating via a Bluetooth + GPRS phone
         iPAQ, where the digital compass has been replaced by sending an aerial or panoramic image of the
          area with direction indication overlaid
We shall use J2ME on the device, but possibly also Java 1.3. All traffic between the device and the Intracom
server will be IP based.
Below some details on the technology utilised by Arbonaut for the creation of the LoVEUS 2.5 G prototype
are presented:


2.1.1     HP iPAQ Pocket PC H3970
400 MHz Intel® PXA250 Application Processor
Microsoft Pocket PC 2002
TFT LCD, 64K colours (transflective)
64 MB RAM
48 MB ROM
http://www.compaq.com/products/handhelds/pocketpc/H3970.html


2.1.2     HP Dual-Slot PC Card* Expansion Pack 216198-B21
http://www.compaq.com/products/handhelds/pocketpc/options/expansion_packs.html


2.1.3     Sierra Wireless ®AirCard 750 Wireless Network Card
Type II PC Card (not extended)
GPRS Class 12 Capability (up to 4 Tx, 4 Rx, 5 total)
http://www.sierrawireless.com/ProductsOrdering/AC750_GSM.html

2.1.4     Pretec CF PCMICA Adapter EB2CFC1P
http://www.pretec.com/index2/product/Accessory/adapter.htm


2.1.5     Pretec CF CompactGPS card
Pretec CompactGPS™ was selected for the 2.5G terminal, since it is small in size, accurate (at least 12
simultaneous satellites tracked) and acquires fast position info, even on cold start situations. Pretec's
CompactGPS is in CompactFlash form-factor, which can be connected to the 2.5G hardware platform. With
12-Channel architecture technology, Pretec's CompactGPS card can provide rapid Time-First-Fix (TIFF) under
all start-up conditions.
Pretec CompactGPS™ implements the NMEA 0183 (National Marine Electronics Association) interface
standard for providing location information to externally connected devices. NMEA 0183 data is sent at 4800
baud on serial port. The data is transmitted in the form of "sentences". Since we are interested only on satellite
status and user’s position, it is enough to parse the following sentences:
$GPRMC - Recommended minimum specific GPS/Transit data
$GPGSA - GPS DOP and active satellites
http://www.pretec.com/index2/product/Mobile_peripherals/CompactGPS.htm




Trials Specification of the 2.5 G System and Terminal Prototypes                              LoVEUS Consortium
8                                                                                                 IST-2000-30155



2.1.6    Garmin eTrex Summit™ GPS card
http://www.garmin.com/mobile
The eTrex Summit™ is an all-in-one navigation device, combining GPS, altimeter, and electronic compass.
The electronic compass provides bearing information when you're standing still and the altimeter determines
precise altitude. The eTrex Summit comes packaged in a small case with operating buttons located on either
side of the unit. The case is completely waterproof to withstand immersion in one meter of water for up to 30
minutes.
The differential-ready, 12 parallel channel GPS receiver continuously tracks and uses up to 12 satellites to
compute and update position. Position acquisition times vary from ~15 seconds (warm) to ~45 seconds (cold)
or ~5 minutes (AutoLocate™). The accuracy in position is about 15 meters (49 feet) RMS. It implements the
NMEA 0183 (National Marine Electronics Association) interface standard. The electronic compass features an
accuracy of ±2 degrees with proper calibration (±5 degrees in extreme northern and southern latitudes) and a
resolution of 1 degree.


2.1.7    PNI TCM2-20 3-Axis Magnetometer
http://www.pnicorp.com/legacy/compass-sensors-radar-sensors-breath-sensors-and-oem-modules/tcm2-20-
module.html - Module

TCM2 Tilt-Compensated Module was chosen, since it provides accuracy better than 5 degrees and reasonably
good tilt compensation. The TCM2 Tilt-Compensated Module is based on a proprietary tri-axial magnetometer
system and a biaxial electrolytic inclinometer, and contains no moving parts. It “listens” to magnetic field
directions and compares it to its onboard roll and tilt sensor to calculate accurate heading of the device. The
output of selected digital compass bearing information is in a format similar to the GPS NMEA 0183 protocol.
It uses sentence $HCHDM to output its magnetic heading.


2.2     Motorola A820, A830 mobile terminal
Motorola will investigate the portability of the LoVEUS GPRS development to its range of phones.
Candidates are the range of products that incorporate functionality similar to the PDA range of products. In
parallel with the development being performed for the iPAQ and J2ME, compliance will be checked for the
Accompli range, identifying at an early stage potential problems and assisting towards the roadmap for the
UMTS solution.




                            Figure 2:2 Motorola A008 and Motorola A388 phones




LoVEUS Consortium
V1.0, 24 December 2002                                                                                                9




3     LABORATORY TRIALS

3.1       Selection of the Test Area
The aim of LoVEUS is to provide users with personalised, tourism-associated multimedia information related
to their location and orientation within cultural sites or urban settings, enriched with relevant advertisements.
Hence, the nature of the system requires the sites, for which LoVEUS type of services will be available, to be
worth from a cultural and tourist point of view. Consequently, one of the most important criteria for choosing a
test area is its cultural significance and tourist interest. This significance cannot be measured quantitatively,
but is directly linked to some indicators:
     the monuments in the site, or events directly linked with the site that became known throughout the world
     the amount of interest in the site for people to visit and material (historic, scientific etc.) for the system to
      render (acting as a tour guide)
     the need for documentation on the site to record and to present to the visitors, as well as references in
      world literature about the site
From a technical point of view, the area to be covered must not be affected by undesirable interference, so that
the mobile signal is accurate: hills and tall buildings can block signals while different types of soil can also
have some influence. The system also needs to be within the boundaries of a Mobile Network cell, otherwise
the mobile phone may not send and receive reliably. The signal gets weaker the further it is from the Network's
centre of coverage area and there is a potential danger of interference with neighbouring cells.
The same precautions must be taken for the GPS signal to work effectively: there is a definite demand for an
outdoors environment where, usually, there must be a clear view of the sky and a good GPS satellite reception
for the positioning system to work. This implies that in large metropolitan areas where GPS or other
electromagnetic based signals are hard to receive, problems may arise with regards to accurate positioning.
After carefully examining the above-mentioned criteria and taking into account the LoVEUS user
requirements, the geographic area presented in paragraph 3.2, in the centre of Athens, was chosen for the trials
of the 2.5 G. Athens should not be regarded as one huge and faceless tourist venue but more as a peopled,
nuanced cityscape with much to see and experience. Many traces of the multiple layers of cultural
developments and achievements are still visible to the discerning eye to unravel in the seemingly chaotic,
congested but vibrant central core of the city.
The area selected offers the possibility to demonstrate the effectiveness of LoVEUS for every kind of service
the user requires, with respect to the various Application Scenarios, as these have been identified in D02. It is a
part of the city of Athens that combines modern with antique, cultural heritage with trendy spots. Along the
major avenues contained within the test area, many museums and art galleries lie. Archaeological sites and
semi-ruined monuments are within this area, which offer the possibility for augmentation and 3-D
reconstructions.
More specifically, the cultural heritage sites that the LoVEUS user can see or visit if walking through this part
of the city include, among others:
          Archaeological sites, Monuments, Palaces
          Museums, Art Galleries
          Churches
          Statues
          Part of the Old Town
          Athletic courts, parks, gardens




Trials Specification of the 2.5 G System and Terminal Prototypes                                   LoVEUS Consortium
10                                                                                                    IST-2000-30155



For these POIs there will be available guided tours (text, pictures and/or video, accompanied by audio
information), reconstructions of a site or building in their original state (text, picture(s) and/or video,
accompanied by audio information), general info (text, picture(s) and/or video, accompanied by audio
information), enhanced views.
As far as technology is concerned, the test area’s illumination conditions throughout the year are favouring the
operation of such a system and are almost ideal: there is low probability of heavily clouded sky even during
winter months. The site is quite open, taking into account the fact that it is located at the centre of a tightly
build city. The route of a LoVEUS user to follow is along major avenues or streets that are surrounded by low
buildings or parks and green open spaces. Initial survey of the site revealed that GPS signal reception is
acceptable almost everywhere. Further, the site’s size and routes selected are appropriate for users to walk,
without getting tired, although they are offered plenty of things to see and savour.


3.2    Description of the test-site




                                         Figure 3:1 Preview of test area


The test area for the first prototype trials is located at the centre of Athens, covering ~ 1.6 km 2. The geographic
coordinates (WGS-84, decimal degrees) of the rectangle are:

Upper left Lat = 37.9726 N           Upper left Long = 23.7287 E
Lower right Lat = 37.9633 N          Lower right Long = 23.7461 E


LoVEUS Consortium
V1.0, 24 December 2002                                                                                           11



3.3       Services to test during trials
The services to be tested are specified according to the application scenarios identified in D02 “LoVEUS
Service and Application Scenarios”. The following three basic application scenarios have been devised, within
the context of LoVEUS:
     AS1: Content at Premium Sites
     AS2: Panoramic View
     AS3: Active Map with City Navigation
These applications can be either system- or user- initiated (“push” or “pull” service, respectively). The main
goal of the trials will be to identify the user demands/satisfaction for the presented value added services. The
categories that will be addressed include:
          Location based streamed information services for cultural heritage
          Location based personalized advertisement
          Personalized guided tours (guidance and navigation)

3.3.1      Services for AS1
          Guided Tours (text, pictures and/or video, accompanied by audible information)
          Reconstruction of a site or building in their original state (text, picture(s) and/or video, accompanied
           by audible information)
          General Info (text, picture(s) and/or video, accompanied by audible information)

3.3.2      Services for AS2
          Panoramic view in case of high-hill places
          Different view of a "key" spot

3.3.3      Services for AS3
          Notification of availability of the other AS
          POIs
          Navigation
          Zoom in/out
          Pan
          Advertisements


3.4       Content to be used for trials

3.4.1      Vector data
The vector layers to be used for LoVEUS are created by digitisation of appropriate input data sources, such as
satellite imagery or topographic diagrams. The data are at a first stage saved in a shapefile format, using ESRI
ArcGIS software. They are then imported to the GIS system of FHG by doing necessary data translations. It is
suggested to use the WGS-84 datum and UTM projection as it is a well-defined system and easy to port from
one platform to the other.
Below, the various layers are presented, with their names and the info contained in the attribute table.
Point layers:
          Hotels = name, hotel class, address, tel. number, postal code
          Transportation = bus stop, trolley stop, metro station with line name and line number


Trials Specification of the 2.5 G System and Terminal Prototypes                                LoVEUS Consortium
12                                                                                                IST-2000-30155



     POIs = pharmacies, newspaper stands, restaurants, coffee shops etc.
Polyline layers:
        Streets = road network with street names, numbering, ZIP code information, indication of traffic flow
         direction
Polygon layers:
        POIs_bldg = land use info (sports areas, schools, public buildings, recreation, etc.), name, address
        Green = green areas, squares, gardens, parks, etc. with their name, if applicable
        ELTA = zip code blocks
        Cult = land use info (museums, monuments, exhibition centres, archaeological sites, etc.), name,
         address, opening hours, ticket price and other info

Eventually, more layers will be digitised, in order to cover all requirements, as these have been identified in
D01 and D02.

3.4.2    Image data
A selection of buildings will be made, like the Parliament, some museums, the National Gallery, etc. and their
photographs will be available to the user. Photographs for the enhanced views of some “key” spots will also be
incorporated to the MM-GIS. The format of the digital photos will be dependent on the client application, so
the choice will be made between various formats, like JPEG, TIFF, BMP or others. The image data will be
accompanied by metadata, like name, info on the represented building, file size, etc., so this information will
assist in deciding if the available image is relevant for the client and data traffic.

3.4.3    Audio data
The navigation and/or routing software will partly create the audio data of the LoVEUS. Navigation
instructions are a product of the routing software whereas audio alerts are a feature of the client terminal.
ROAD will supply the Audio guides in an appropriate format, which will contain tourist information on certain
monuments, as well as some instructions, regarding the route to be followed for the guided tours. Metadata
files will also be created.

3.4.4    Video data
The Guided tours in formats like AVI, MPEG, will be created for certain areas of interest to a tourist.
Advertisement information, by OGILVY, will be provided for certain POIs, like restaurants, bars etc. Metadata
files will also be created.

3.4.5    3-D reconstructions
3-D reconstructions of certain archaeological sites/monuments as MAX files are being created and will be
transformed to e.g. VRML as common 3D vector format for web based applications. However, the 3D file
format has to be further investigated and specified more precisely. According to FHG’s experience, files from
3DStudioMax cannot be displayed directly on mobile devices and only VRML files are best supported on this
hardware. Hence, it has to be tested and subsequently decided if the files can be exported from Max to VRML
and then ported to the PDA without problems or if we could use the 3D layer of MPEG4. In all cases, the
multimedia database can hold any of these formats.




LoVEUS Consortium
V1.0, 24 December 2002                                                                                          13




3.5     Description of the experimental set-up




                 Figure 3:2 Vodafone’s experimental setup for the first integration trial (in Greece)


Vodafone Greece, apart from live network, has extensive testing facilities. Part of the project trials and demos
will be hosted in these premises. The setup for the first integration trials will offer the maximum available
GPRS network bandwidth, as well as the maximum backbone bandwidth. This will help the developers of all
other necessary components (terminal application, ASP, content server, etc.) to optimize the partial
performance of each component and perform a perfect debugging, since there will not be bandwidth
constraints.
Most of the required components and sub-systems will be hosted in Intracom premises. There will not be any
connectivity problem with Intracom premises. Vodafone has a node inside Intracom premises and the
interconnection will be relatively easy with minor equipment requirements (possibly a UTP wire and a E1
G.703 channelized card in the output of ICOM router and towards the Vodafone network).
A separate detailed analysis with comments on each component/sub-system will follow. An indicative
experimental setup can be seen in Figure 3.2.


3.5.1     Server components
The major components and subsystems will be hosted in Intracom premises for the first trial. The simpler way
to facilitate the connection among them is to build a LAN. At the point of trials start, it will be defined how
and if they will be connected to the Intracom intranet, router etc., with some private addresses etc.




Trials Specification of the 2.5 G System and Terminal Prototypes                                LoVEUS Consortium
14                                                                                                                                             IST-2000-30155




      LoVEUS Application Server



                                                                            2.5G/3G
                                                                            Network



                        Core System
                                               SMTP                                HTTP            HTTP

                                    SMTP                      SMS                       HTTP
                                   Interface                Interface                  Interface




                                                                                                   Streaming
                          Notification            Application              Content
                                                                                                     Server
                                                    Logic               Transformation

                             Email                    Location
                                                                           Filtering
     Network Operator      Forwarder                  Module
                                                                                                   Streaming
                                                                                                      DB

        Network
       Positioning

                                                                                                               Content Provider

        Charging/                  Log                       User
         Billing                  Manager                   Manager                                                      Multimedia
                                                                                                                           GIS



        Customer                      Log                    User                                                  Map            Multimedia
          DB                          DB                     DB                                                    DB                DB



                                         Figure 3:3 LoVEUS Application Server Components




                           Server modules                                               1st prototype
                           SMS Interface
                           HTTP Interface                                               
                           SMTP Interface
                           Notification                                                 
                           Application Logic                                            
                           Email Forwarder
                           Location Module                                              
                           Filtering                                                    
                           Log Manager                                                  
                           Log DB
                           User Manager                                                 
                           User DB
                           Content Transformation                                       
                           Multimedia GIS                                               
                           Map DB                                                       
                           Multimedia DB                                                
                           Streaming Server
                           Streaming DB
                           MPEG-4 download (FTP)                                        



LoVEUS Consortium
V1.0, 24 December 2002                                                                                        15



Corresponding to the overall architecture of the LoVEUS system, the Multimedia GIS is separated from the
Application Server. The FHG IGD implements the MM-GIS, which will be hosted at their premises. The
implemented architecture is sub-dived into three servers. The first one is a general connection server of the
Multimedia GIS that serves the complete communication between the Application Server and the MM GIS.
This server deals with the Multimedia requests. The second server provides the basic GIS functionality like
routing, map generation and area selection. Both servers are connected with the MM GIS Database that will be
implemented on a further server.
Used system architecture:
      Multimedia and Connection Server
       The Software is implemented on the basis of Java Servlets by using Java 1.4.1, Tomcat 4.1.2, JDOM
       (Java-based "document object model" for XML files). The communication to the LoVEUS Application
       Server is implemented by XML as well as the communication to the GIS Server.
      GIS Server
       The GIS component is realised by commercial products of the company Intergraph, namely IntelliWhere
       as Location Server and the Map Server Geomedia Web Enterprise. These programs require a running
       system with MS Windows 2000 Server, Internet Information Server and MS XML Parser.
      Database Server
       As database the FHG IGD will host an Oracle database extended by Oracle Spatial. The Multimedia data
       are stored in a multimedia data model developed by FHG and in the GIS data model that depends on the
       original shapefiles and the required relation tables by IntelliWhere.
Prior to the first trial period, tests will be conducted in order to access FHG’s Multimedia GIS from Intracom’s
premises. If the performance of the system is not adequate this way, then the Multimedia GIS will be hosted at
Intracom’s premises during the first trials.


3.5.2     Client components
The architecture of the LoVEUS client has been identified at the D04 deliverable named “Overall LOVEUS
architecture and trials plans”, where it has also been functionally decomposed into the following submodules
of: (1) interface layer, (2) application control layer and (3) user interface layer.
The platform that will be used for the GPRS trials will be a PDA solution with A-GPS and digital compass
integrated, as already analysed in chapter 2.
Concerning the development platform, it was evaluated that an appropriate solution is to be based on Java 2
Platform Micro Edition (J2ME). Specifically for Motorola, it is of interest to port the development on MERI,
which stands for Motorola Embedded Reference Implementation for J2ME™ technology. This is a good
candidate to be used, as it will assist towards the portability of the LoVEUS implemented functionality in
GPRS and UMTS handsets solutions. The MERI architecture is illustrated in the following figure.




Trials Specification of the 2.5 G System and Terminal Prototypes                             LoVEUS Consortium
16                                                                                               IST-2000-30155




                     Figure 3:4 Motorola Embedded Reference Implementation for J2ME™


The features of MERI can be summarised as:
        KVM and CLDC/MIDP 1.0 Libraries
        Fully TCK compliant
        J2ME application management modules
             o JAM (Java Application Manager)
             o JAID (Java Application Installer/De-installer)
             o JFI (JAM Functionality Interface)
             o JAL (Java Application Loader)
        Performance enhancers such as: Optimized Byte Code Interpreter, Mini-JIT, Code snippets and other
         performance enhancements
        Supplemental J2ME Test Suites:
             o Internal verification tests
             o Java installer / de-installer tests
             o Porting/Unit tests
             o J2ME test applications
        Linux J2ME Emulator for application development
        Reference Platform
        Compaq iPAQ
        Embedded Linux kernel


Finally, the following identified modules will be integrated and the necessary functionality will be ported to
interface with the network, to support the application and enable user interaction. Test cases and procedures
with incremental complexity and at different phases of the development phase will be compiled.




LoVEUS Consortium
V1.0, 24 December 2002                                                                                                                      17




                    UMTS                      PDA with                       GPS                             Compass
                     UMTS                      PDA with                       GPS                             Compass
                    Phone                     GPRS card
                     Phone                     GPRS card

                Interface         Server                              RS232                               NMEA
                Layer             Interface                           Interface                           Interface




                                  GPRS Server                                                 GPS               Compass
                                  Interface                                                   Interface         Interface




                Application
                Control             Controller
                Layer                                 Session                     Position
                                                      Manager                     Manager


                                                                                                            Preferences
                                                      POI          Map                                      Manager
                                                      Manager      Manager




                User
                Interface                                           Text Viewer              Image          Preferences
                                    Session                                                  Viewer
                Layer
                                    Handler UI



                                                 Map Viewer        Panoramic          Guided Tour             MPEG-4
                                                                   View Viewer        Viewer                  Player




                                      Figure 3:5 Functional Decomposition of the LOVEUS Client


The table below presents the client modules that will be developed and tested for the 2.5 G trials.



                            Client modules                            1st prototype
                            Application Control                       
                            Navigation                                
                            Text Viewer                               
                            Image Viewer                              
                            MPEG-4 Player                             
                            Multimodality
                            Digital Compass                           
                            GPRS card                                 
                            UMTS card
                            GPS receiver                              




Trials Specification of the 2.5 G System and Terminal Prototypes                                                            LoVEUS Consortium
18                                                                                               IST-2000-30155




4     EVALUATION METHODOLOGY FOR LoVEUS APPLICATION
In this section we present the methodology for the evaluation of the functionality and user interface offered
through the first LoVEUS prototype.


4.1        Overview of Approach
The evaluation methodology that will be implemented for the LoVEUS project, is made up of a number of
basic steps, which are the following:
      1.       Analysis
               a.       Establish objectives
               b.       Understand measurements
      2.       Template construction
               a.       Define success metrics (Key Performance Indicators: KPIs)
      3.       Measurement Plan
               a.       Agreed KPIs and measurement requirements
      4.       Benchmarking
               a.       Agree zero base measurement
               b.       Set benchmarks and targets
      5.       Reporting
               a.       Research and reporting
               b.       Distribution of scorecards
      6.       Interpretation
               a.       Relate indicators to project objectives
      7.       Action Planning
               a.       Provide recommendations
               b.       Set new targets


The process steps (above) are a practical way of ensuring that measurement is truly linked to the project’s
objectives. These steps are further detailed below.
The evaluation process should use specially designed templates to guide the consortium through prioritisation,
identification and recording of performance indicators. These templates can be used to generate a scorecard of
performance showing how each indicator performs relative to each other.
The evaluation templates will be structured under specific core dimensions – the areas that have the most
effect on the project’s performance. Each dimension must aim to answer an important question regarding
LoVEUS.
Behind each core dimension, many measures of performance might exist. The process prioritises these
measurement criteria into a set of key performance indicators.
Once the definitive list of indicators has been decided upon, targets can be set based on initial or existing
reporting. These targets can be used to benchmark the performance of each indicator.
In summary, the focus of the evaluation process is to identify criteria and approaches to effectively measure
performance, whilst ensuring acceptance by a wide range of end users.




LoVEUS Consortium
V1.0, 24 December 2002                                                                                         19



4.2       Detailed Evaluation steps
          Analysis – Each interested party will be provided with an initial questionnaire that asks a range of
           short questions relating to metrics and reporting they would like implemented. These questionnaires
           are structured to ensure that all parties get their initial views across.
          Template construction – All the questionnaires are collated and the standard evaluation template is
           configured to hold the indicators.
          Measurement Plan – A document is produced detailing all the agreed indicators and measurement
           requirements.
          Benchmarking – Setting the starting values (zero base) for each indicator allows performance to be
           tracked. These benchmarks are used to understand how the project’s objectives are met.
          Reports - Some Indicators will require information from end users.
          Market Research – Questionnaires or other market research projects may be needed to measure
           customer experience.
          Testing – All reports and associated infrastructure will be tested for reliability, response times and
           accuracy to ensure that the solution truly meets end users’ requirements
          Scorecard Construction – Benchmarking performance of Indicators against agreed targets scores to
           show understanding of the core strengths and weaknesses of the project.
          Reporting and Interpretation – Providing performance information ensures that we can provide
           actionable tasks to improve effectiveness.
          Action Planning – Next steps should be driven by what is effective and provides the most benefit




4.3       Analysis: Quantitative & Qualitative Tests & Measurements
The first prototype trial will test and validate what is on offer over a GPRS platform. The functionalities to be
tested will be both on the client and the server, as well as on the authoring tool. Some of the issues to be
addressed are presented below.
All the criteria must be assessed in both a quantitative way (exact measures) and a qualitative one (user
assessment) in order to determine the best compromise for a comfortable usage of the technology.
Overall system integration:
          Robustness of operation
          Accuracy of GPS positioning
          GPS / compass integration on a mobile station
          GIS and MM-GIS integration
          MPEG-4 streaming server: multiple rate, authoring tool
          MPEG-4 client, clickable object functionality
          Client viewpoint according to position and terminal orientation
          Personalization

Network related:
          Scalability (amount of users)
          Mobility of users (Full Mobility, Limited Mobility)
          Speed of establishing connection
          Speed of image and map transfer



Trials Specification of the 2.5 G System and Terminal Prototypes                              LoVEUS Consortium
20                                                                                                  IST-2000-30155



Client related:
         Ease of learning to use the application
         Usefulness of content
         Subjective assessment of the usefulness of digital compass or its replacement with aerial image by
          test users
         Ease of identification of places, monuments etc.
         Ease of following navigation instructions. Assessment of their effectiveness.
         Advertisements relevance
         Level of details per download that satisfies the user
         Application on client: is the user satisfied with functions offered?
         Application bugs and reporting procedures

4.3.1     Key Performance Indicators
The trials to be performed during the first integration setup will be based on the step-by-step description of
D02. Although the following list may not be exhaustive, the tests described are critical in order to evaluate
LoVEUS overall functionality, as well as user interface.

4.3.1.1    GPRS IP Connectivity test
This test will test and demonstrate the capability of the terminal with respect to bit-rate performance. It may be
good to repeat the experiment under decreasing number of dedicated TS (i.e. 4, 3, 2, 1).
Expected performance: As much as the maximum terminal supported TS#
Risks/Open issues: None if there is co-operation of the GPRS card and the PDA. For this reason possibly it is
not required to repeat this trial many times.

4.3.1.2    GPRS connectivity with stored content server at Intracom
This test will test the GPRS connectivity with content server at Intracom through IP. For example a simple ftp
to the terminal must be performed. The ftp must be initiated by the content server (Intracom) because this will
be the real case as well. The ftp latency will be measured. The trials may deserve some repeated tests in the
GPRS BH. Furthermore, it may be good to repeat the experiment under decreasing number of dedicated TS
(i.e. 4, 3, 2, 1).
Expected performance: Excellent. Ftp will face the traffic only from the ICOM LAN and at the delivery from
GGSN to the terminal (negligible).
Risks/Open issues: IP address of terminal is private while GGSN is global.

4.3.1.3    GPRS connectivity and application performance for stored content
This test will identify some application drawbacks, weak points etc. Measure application bit rate (if possible)
and latency (= the time required for application starting (after ftp) and completion). Repeat in the BH. Repeat
for decreasing TS# (i.e. 4, 3, 2, 1). Repeat for "simple" (text) and "complex" (image, video) content. Find
possible "bugs".
Expected performance: Depending on the application.
Risks/Open issues: The application will play "on-line", "streaming" or will it be stored in the terminal and after
the completion of the download it will start playing? This will drive the service performance especially for
decreasing #TS.




LoVEUS Consortium
V1.0, 24 December 2002                                                                                           21



4.3.1.4      Location update file monitoring from Vodafone to Intracom
This test will study the performance of the location update file. The file will be generated in Vodafone and will
be directed to the application server. The IT solution can be, for example, http post. The latency of the file
should be measured. Repeat for the BH. This time delay will have to be minimized because it is added to the
service completion time.
Expected performance: Especially for the trial, with limited customer number "monitored" (i.e. one, two,
three), there will not be a problem with respect to bandwidth.
Risks/Open issues: The sampling interval, e.g. the repetition frequency of file delivery from MNO to ASP.

4.3.1.5      Application server triggers GIS, file preparation
This test will study the time required for preparation of the content to be delivered to the customer. Based on
the info originating from the MNO, the ASP must extract the proper information and direct it to the customer.
It is worth studying the required latency in heavy request traffic situation.
Expected performance: Should be in the range of less than 3 seconds.
Risks/Open issues: As the Multimedia GIS is not located in the same place the network could cause delays.

4.3.1.6      Handover
After optimizing system performance and minimizing service completion time, it is worth repeating trials
under handover situation. This trial may be out of scope for the first lab trial but deserves extensive study
before going to the field trials
Expected performance: Poor results, delayed response.
Risks/Open issues: The performance is mainly driven from the resources available in the arriving cell.

4.3.1.7      MPEG4 Server & Client
The MPEG4 streaming server can provide multiple frame rate (fps), frame size (resolution in pixels) and
image quality video (pSNR). Therefore, for qualitative research, we need to investigate which frame rate and
frame size are suitable for PDA display and which image quality is the minimal requirement for users.
Additionally, these parameters are strongly related to the transmission speed (latency, jitter): therefore we have
to take care of the maximum waiting time for users.
MPEG4 client is the MPEG4 compressed video viewer. Maximum frame rate (fps) of the viewer is based on
the power (CPU) of the PDA, but if some other application uses a lot of machine resources, the viewer can
show a slower frame rate. Such a relationship between the MPEG4 client and other applications should be
investigated.


4.3.2      Measurement Plan - Benchmarking
An indicative table of the measurements, as suggested by VODAFONE, is presented. The column
“measurement class” refers to the component for which a measurement is performed. As it is commonly
adopted, the measurements are usually executed more than once, in order to study all possible parameters. This
is covered in the column “way of repeat”. Finally, there is a column containing the criteria that will be used, in
order to decide whether the specific measurement is assumed as successful or not.
          Measurement                                                            Way of
   #                           Measurement                         Description              Success criterion
          class                                                                  repeat
   1      Streaming            Min(fps), Max(fps),                               One week   According to apps
          server               Avg(fps)|day,                                                standardization
                               Avg(fps)|BH,



Trials Specification of the 2.5 G System and Terminal Prototypes                                 LoVEUS Consortium
22                                                                                      IST-2000-30155



                       Avg(fps)|long term
                       …
     2   Streaming     Min(bps), Max(bps),                    …              According to apps
         server        Avg(bps)|day,                                         standardization
                       Avg(bps)|BH,
                       Avg(bps)|long term
                       …
     3   Streaming     BER, FER, latency, …                   One day        According to apps
         server                                                              standardization
         Streaming     …                                      …
         server
     n   Stored data   Min(fps), Max(fps),                    One week       According to apps
                       Avg(fps)|day,                                         standardization
                       Avg(fps)|BH,
                       Avg(fps)|long term
                       …
     n   Stored data   Min(bps), Max(bps),                    …              According to apps
     +                 Avg(bps)|day,                                         standardization
     1                 Avg(bps)|BH,
                       Avg(bps)|long term
                       …
         Stored data   BER, FER, latency, …                   One day        According to apps
                                                                             standardization
         Stored data   …                                      …
     m   LBS           Terminal based Cell-ID   If possible   In various     2sec
                       method calculation                     areas (dense
                       time and upload                        urban,
                                                              urban).
     m   LBS           Terminal based Cell-ID   If possible   Under          2sec
     +                 method calculation                     handovers
     1                 time and upload
         LBS           Terminal based Cell-     If possible   In various     2sec
                       ID+TA method                           areas (dense
                       calculation time and                   urban,
                       upload                                 urban).
                                                              Under
                                                              handovers
         LBS           Network based Cell-ID                  In various     2sec
                       method calculation                     areas (dense
                       time and upload                        urban,
                                                              urban).
         LBS           Network based Cell-ID                  Under          2sec
                       method calculation                     handovers
                       time and upload



LoVEUS Consortium
V1.0, 24 December 2002                                                                                                   23



         LBS                   Network based Cell-                               In various      2sec
                               ID+TA method                                      areas (dense
                               calculation time and                              urban,
                               upload                                            urban).
         LBS                   Network based Cell-                               Under           2sec
                               ID+TA method                                      handovers
                               calculation time and
                               upload
         LBS                   GPS activation time                               In various      30 sec in 50% of
                                                                                 areas (dense    time, 20 sec in 66%
                                                                                 urban,          of time
                                                                                 urban).
         LBS                   GPS activation time                               Under
                                                                                 handovers
         LBS                   GPS activation time                               Hot, cold,      >>
                                                                                 spontaneous
         LBS                   …
   k     Terminal              Battery level                       If possible   After
                                                                                 repeated
                                                                                 requests
   k     Terminal              Battery level                       If possible   After
   +                                                                             repeated
   1                                                                             GPS
                                                                                 activations
         Terminal              …
   l     Overall               Multiple users                      Lab           Using
         performance                                                             simulator?
   l     Overall               Multiple users                      Field         Under high
   +     performance                                                             voice traffic
   1
         Overall               Multiple users                      Field         Under low
         performance                                                             voice traffic
         Overall               User satisfaction                   Field         Under low       Semi-qualitative way,
         performance                                                             voice traffic   based on
                                                                                                 questionnaire
         Overall               …
         performance
         …




4.4     Reporting: Questionnaires to be submitted to System Users
As outlined in paragraph 4.2, the questionnaires will be built by using input from all interested parties (i.e.
consortium members), so that these reflect views from all partners. The LoVEUS consortium will decide upon
the criteria for selecting a representative sample of users (definition of how is the selection made, what the
group size shall be, if users at this stage are going to be only consortium members or others as well).


Trials Specification of the 2.5 G System and Terminal Prototypes                                        LoVEUS Consortium
24                                                                                                 IST-2000-30155



The users shall be introduced to the system. Then, some time will be allocated for their familiarisation with
LoVEUS interface and the different functions. After executing some tasks, the users will answer the
questionnaires that will permit evaluation of the system both on the server and the terminal side. There will be
a different questionnaire for each Application Scenario.
The questionnaires shall contain questions on the following (at least):
        General Info on LoVEUS user
        Demographic data
        Questions about the quality of presentation
             o    Quality of 3D representations
             o    Quality of audio/video
             o    MPEG4 video overall quality rating of the service
             o    MPEG4 video quality: users should be asked if their (positive or negative) appreciation is
                  most influenced by: (1) the design/usage, (2) the content, (3) technical issues (like image
                  quality, delay, etc.).
             o    Errors in positioning objects, errors in 3D objects’ orientation
        Questions about the cultural information presented
             o    Information Quality, Content
             o    Information Completeness
             o    Organization of information according to content
        Questions about the system’s functionality
             o    Synchronization of multimedia presentation with the real scene
             o    Delay in completing a task
             o    MPEG4 video quality: if technical issues (like image quality, delay, etc.) appear to be the
                  limiting factor, then the users should be asked about their appreciation regarding: the waiting
                  time for receiving video, the overall quality of video, detailed quality of video in terms of
                  frame rate, image size, image appearance (coding artifacts).
        Advertisement personalisation
        System set-up evaluation




LoVEUS Consortium

								
To top