“LOCATION BASED AD’S SERVICES”

Abstract
The motivation for every location-based information system is To assist with the exact
information, at the right place in real-time with personalized setup and location sensitiveness.
In this era, we are dealing with smartphones, which are going to replace the bulky desktops
even for computational purposes. We have more number of applications and usage where a
person sitting in a roadside café needs and any corner to get relevant data and information.
Such requirements can only be catered with the help of LBS. These applications include
security-related jobs, a general survey regarding traffic patterns, decisions based on vehicular
information for the validity of registration and license numbers, etc. An engaging application
incorporates observation where moment data is expected to choose if the individuals being
checked are any genuine danger or a mistaken objective. We have had the option to make
various applications where we give the client data with respect to a spot the person in
question needs to visit. However, these applications are constrained to work areas as it were.
We have to import them on cell phones. We should guarantee that an individual when visiting
places need not convey the movement guides with him. All the information must be available
in his Web device and also in a user-customized format.

INTRODUCTION

The rapid expansion of wireless technologies has provided a platform to support intelligent
systems in the domain of Web marketing. Utilizing Location Based Services and Global
Navigational Satellite Systems provides the capability for the transport of real-time,
scheduled, location-based advertising to individuals and businesses. This project introduces
location-based marketing and advertising services, and a related intelligent Web advertising
system. Web marketing competes with traditional media channels such as television, radio,
and the printed press. Advertisements are becoming increasingly personalized and context-
aware to fulfill customer needs.
 Location-based advertisement not only helps to improve sales in a particular area but
can also improve brand awareness among potential customers Utilizing the Location Based
Services and Global Navigational Satellite Systems the user can locate the ad poster store in
mop, they can also navigate using routes showed between their current location and ad
poster’s shop. General Packet Radio Service (GPRS) is a packet-oriented Web data service
on the 2G and 3G cellular communication system’s Global System for Web communications
(GSM), we are making use of GPRS facility of Web Web to connect to the remote server.

Existing process and its limitations

Existing advertising systems are web-based such as web-classified advertisements that can be
accessed through desktop computers. Users can browse these ads through Web browsers but
he will face resolution problems and access delay problems. Even there is no ranking concept
to order the ads in the way user need. There is no effective Web-based advertisement system
at present

Proposed System

There is much support for Location Based search and Context Aware Ad Searches. This
application does not take much time to detect the Ads that useful to the user. User should be
able to see the located buildings and stores that has the offers and advertisements on Google
maps application in Web Web. This Web application enables to display the road map
between user’s current location and the store/shop location on Google maps application, users
should be able to navigate between his/her current location and store/shop location using this
Web application.

The users of the application should be able to subscribe to the Ad posters to get
instant emails about the posted Ads. Also, users should be able to unsubscribe from the Ad
posters to stop getting instant emails about the posted Ads. It should be possible for the end-
user to see the Advertisements by specific location in the list form in Web application. It
should also be possible for the user to see the Advertisements by specific Ad category in the
list form in Web application. The proposed application should enable the user to see the
Advertisements by his/her current location in the list form in Web application.
 PROBLEM STATEMENT
There is need of an Web application which enables to subscribe for the ads posted, to display
and navigate the road map between user’s current location and the store/shop location on
Google maps application.

SCOPE
The scope of the project is to develop an Web application and it will work for the
advertising .It ensures portability and therefore compatibility. This is a real-time intelligent
Web ad’s services using GPS technology.
Literature Survey

Bauer, Christine & Strauss, Christine (2016). Location-based Advertising

on Web Devices: A Literature Review and Analysis. Management Review
Quarterly, 66(3), Springer, pp 159-194

Location-based advertising (LBA) allows the delivery of advertising messages to consumers in

places that are known for their particular high and positive advertising effect. While LBA is
recognized for static roadside billboards and the Web, LBA can now be found on Web devices.
This Web advertising adds valuable opportunities for companies: it allows consumers to be
addressed (i) individually, (ii) based on their current location, and (iii) dynamically in real-time;
furthermore, (iv) content may be replaced quickly by remote access. Accordingly, within the Web
marketing domain, LBA on Web devices turns over a new leaf. This young research field is
interdisciplinary at its core and marketing and technical experts expect major impetus. To
contribute to this growing field, we systematically analyze and evaluate existing literature in the
field of LBA on Web devices, and present the results of six analyses. By building bridges
between the involved disciplines, we present existing research in a condensed, concise and
evaluating form which will support researchers in orienting for future research in the field.
Furthermore, we pinpoint selected “white spots” in research and draw attention to promising
areas for future research and directions of future development trends.

Web design: A key factor for the website success

Web design has been identified as a key factor for the acceptance and success of the websites
and electronic commerce. The purpose of this paper is to analyse, from a marketing point of
view the main aspects that could influence online users' perceptions and behaviours, in order
to achieve a successful e-commerce website. Design/methodology/approach – An extensive
literature review was developed emphasising the special role that web design could play in
the interaction user-interface. Besides, the methodology related to benchmarking allows firms
to know the best practices and to learn some key lessons for developing their businesses
online. Findings – The literature review affirms that web design is a key factor for getting
positive outcomes as it influences on users and online consumers' perceptions and
behaviours. A website design addressed to simplicity and freedom of navigation provides
clear, timely and accurate information in all its contents and an appearance that calls for the
users' attention. Research limitations/implications – The paper offers a Decalogue of
guidelines that could improve the design of the e-commerce websites regarding the aesthetic
appearance of the website, the navigation through the site, the information and contents and
the characteristics of the shopping process. It could be interesting to analyse empirically the
impact of all key attributes on the users' perceptions and behaviours. Originality/value – This
is one of the first studies which explains how a website must be designed from the demand's
perspective. The analysis of the users' perceptions and the marketing view of design could
help designers to find the website that best matches their users' needs and so, to improve the
relationships between users and companies through their interfaces.
A Research Paper OnWebsite Development OptimizationUsing Xampp/PHP
This research paper discussing the various useful tools and techniques that are used in a development
of a website. We also discuss about the procedure follow in a website, mostly focused on a local host
named Xampp tool .Next, we compare different development frameworks web application. In
addition, we discuss life cycle model and framework development of web application. In this report,
various review papers result also included for understanding of problems can be facing by the users.
This Paper tells about the technologies used in this development, PHP and explained in result its
functionality with Xampp with screenshots. It is hoped it will gives a useful framework for guiding
the process.

REQUIREMENT ANALYSIS AND SPECIFICATION

Introduction

A Software Requirements Specification (SRS) is a description of a software system to be

developed. It lays out functional and non-functional requirements, and may include a set of
use cases that describe user interactions that the software must provide.

The software requirements specification document enlists enough and necessary requirements
that are required for the project development. To derive the requirements, the developer
needs to have clear and thorough understanding of the products to be developed or being
developed. This is achieved and refined with detailed and continuous communications with
the project team and customer till the completion of the software.

The introduction of the Software Requirements Specification (SRS) provides an overview of

the entire SRS with purpose, scope, definitions, acronyms, abbreviations, references and
overview of the SRS. The aim of this document is to gather and analyse and give an in-depth
insight of the complete A Responsive Application for Client and user by defining the problem
statement in detail.
3.2 Scope of SRS Document

A Software Requirements Specification (SRS) is a document that describes the nature of a

project, software or application. In simple words, SRS document is a manual of a project
provided it is prepared before you kick-start a project/application. This document is also
known by the names SRS report, software document. A software document is primarily
prepared for a project, software or any kind of application.
There are a set of guidelines to be followed while preparing the software requirement
specification document. This includes the purpose, scope, functional and non-functional
requirements, software and hardware requirements of the project.

Definition Acronyms and Abbreviations

PHP

PHP: Hypertext Preprocessor (or simply PHP) is a server-side scripting language designed

for web development. It was originally created by Rasmus Lerdorf in 1994 the PHP reference
implementation is now produced by The PHP Group. PHP originally stood for Personal
Home Page, but it now stands for the recursive initialism PHP: Hypertext Preprocessor.

PHP code may be embedded into HTML code, or it can be used in combination with

various web template systems, web content management systems, and web frameworks. PHP
code is usually processed by a PHP interpreter implemented as a module in the web server or
as a Common Gateway Interface (CGI) executable. The web server combines the results of
the interpreted and executed PHP code, which may be any type of data, including images,
with the generated web page. PHP code may also be executed with a command-line
interface (CLI) and can be used to implement standalone graphical applications.

Mysql
MySQL is free and open-source software under the terms of the GNU General Public
License, and is also available under a variety of proprietary licenses. MySQL was owned and
sponsored by the Swedish company MySQL AB, which was bought by Sun Microsystems
(now Oracle Corporation).[8] In 2010, when Oracle acquired Sun, Widenius forked the open-
source MySQL project to create MariaDB.

HTML:
Hypertext Markup Language (HTML) is the standard markup language for creating web
pages and web applications. with CascadingStyleSheets (CSS) and JavaScript, it forms a triad
of cornerstone technologies for the World Wide Web.

Web browsers receive HTML documents from a web server or from local storage
and render the documents into multimedia web pages. HTML describes the structure of a
web page semantically and originally included cues for the appearance of the document.

HTML elements are the building blocks of HTML pages. With HTML constructs, images and
other objects such as interactive forms may be embedded into the rendered page. HTML
provides a means to create structured documents by denoting structural semantics for text
such as headings, paragraphs, lists, links, quotes and other items. HTML elements are
delineated by tags, written using angle brackets. 

CSS:
CSS is designed to enable the separation of presentation and content, including layout, colors,
and fonts.[3] This separation can improve content accessibility, provide more flexibility and
control in the specification of presentation characteristics, enable multiple web pages to share
formatting by specifying the relevant CSS in a separate .css file, and reduce complexity and
repetition in the structural content.

Bootstrap:
Bootstrap is a free and open-source front-end framework for developing websites and web
applications. It contains HTML and CSS-based design templates for typography, forms,
buttons, navigation and other interface components, as well as optional Java Script
extensions. Unlike many earlier web frameworks, it concerns itself with front-end
development only.
Product Function

It should be possible to open LBAS Ads account for a user and close the account. It
should be possible for the LBAS Ads user to see the Advertisements in the list form in
Web application. It should be possible for the LBAS Ads user to see the
Advertisements by specific location in the list form in Web application. It should be
possible for the LBAS Ads user to see the Advertisements by specific Ad category in
the list form in Web application. It should be possible for the LBAS Ads user to see
the Advertisements by his/her current location in the list form in Web application. User
should be able to see the located buildings and stores that has the offers and
advertisements on Google maps application in Web Web. This Web application should be
able to display the road map between user’s current location and the store/shop
location on Google maps application. LBAS Ads users should be able to navigate between
his/her current location and store/shop location using this Web application. LBAS Ads users
should be able to subscribe to the Ad posters to get instant emails about the posted Ads.

General Constraints

 User must have the knowledge of application working process.

 Internet must be necessary for this application.
 Multiple users can login.
 The Application is available on all the device. It is compatible with all browser and
Web.

Assumption and Dependencies

 User can use this application in any browser or Web there is no restriction but he
should have internet facility
 User must have the knowledge of English
 We assume that the system must be user friendly and self-explanatory
External Requirements

It gives a description of the hardware, software and communication interface and

provide basic prototypes of the user interface. Functional requirements are defined according
to the development of the project.

System Requirements

 Front end - HTML, CSS, Bootstrap

 Middle layer - PHP, Java Script, Google(API)
 Back end - MYSQL.

Software Requirements

 Operating system - Windows XP – SP2 / 7 / 8.1 above.

 Browser - Internet explorer, Google chrome.

Hardware Requirements

 Processor - Dual core (2.0) GHZ or above

 RAM - 1 GB and above
 Hard disk - 20GB and above

Functional Requirement

It should be possible to open LBAS Ads account for a user and close the account. It
should be possible for the LBAS Ads user to see the Advertisements in the list form in
Web application. It should be possible for the LBAS Ads user to see the
Advertisements by specific location in the list form in Web application. It should be
possible for the LBAS Ads user to see the Advertisements by specific Ad category in
the list form in Web application. It should be possible for the LBAS Ads user to see
the Advertisements by his/her current location in the list form in Web application. User
should be able to see the located buildings and stores that has the offers and
advertisements on Google maps application in Web Web. This Web application should be
able to display the road map between user’s current location and the store/shop
location on Google maps application. LBAS Ads users should be able to navigate between
his/her current location and store/shop location using this Web application. LBAS Ads users
should be able to subscribe to the Ad posters to get instant emails about the posted Ads.
Non-Functional Requirements

Availability

This is a Web application and will be available for every registered user. This application is
compatible with all browser and Web. This application helps to user send different type of
request to clients and view the response.

Maintainability

The project is developed using an Open source tool and is easy to maintain. The software
used for the development of the applications are free so there is no necessary to pay and no
maintenances cost.

Security

As the systems all the data are dumped at the server side the server provides the security to
the unauthorized access of data.

Reliability

Reliability is a requirement about how often the software fails. The measurement is often
expressed in mean time between failures. The definition of a failure must be clear. Also, don't
confuse reliability with availability which is quite a different kind of requirement. Be sure to
specify the consequences of software failure, how to protect from failure, a strategy for error
detection, and a strategy for correction.

Simplicity

The project is driven by a simple user interface which helps to interact easily with application
and easy to remember. Application builds by using bootstrap technology hence it compatible
for all devices.

SYSTEM DESIGN

Introduction
 The Software Design Document is a document to provide documentation which will
be used to aid in software development by providing the details for how the software should
be built. Within the Software Design Document are narrative and graphical documentation of
the software design for the project including use case models, sequence diagrams,
collaboration models, object behaviour models, and other supporting requirement
information.

Purpose

The purpose of Software Design Specification (SDS) document is to specify

high level view of the architecture of our system, and on the interaction between the user and
the system. And another purpose is on detailing a low-level view of each component of the
software and how the components interact with each other.

This document's purpose is to provide a high-level design framework around

which to build our project A responsive application for deaf and dumb. It also provides a list
of requirements against which to test the final project and determine whether we were able to
successfully implement the system according to design.

Scope

The system Design (SD) describes how the functional and non-functional
requirements gathered in the requirement phase, preliminary user-oriented functional design
transform into more technical system specifications from which the system is built. This
phase describes the design goals and considerations, provides a high-level overview of the
system architecture, and describes the data design associated with the human-machine
interface and operational scenarios.

4.4 Overview

The system design documents and tracks the necessary information required to
effectively define architecture and design of Request Approval Application system in order to
give the development team guidance on the architecture of the system to be developed.
Design documents are incrementally and iteratively produced during the system development
life cycle, based on the particular circumstances of the Request Approval Application project.
System Architecture

Architecture focuses on looking at a system as a combination of many different

components, and how they interact with each other to produce the desired result. It involves
the process of defining a collection of hardware and software components and their interfaces
to establish the framework for the development of an Web application.

Architecture Diagram
Software Engineering Model Used

Waterfall Model

Waterfall model is the earliest SDLC approach that was used for software
development. It is also referred to as a linear-sequential life cycle model. It is very simple to
understood and use. In a waterfall model, each phase must be completed before the next
phase can begin and there is no overlapping in phases.

Following is a diagrammatic representation of distinct phases of waterfall model.

Waterfall Model

In “The Waterfall” approach, the full process of software development is divided into
separate phases. In Waterfall model, typically, the outcomes of one phase act as the input for
the next phase sequentially. The sequential phases in Waterfall model are:

 Requirement Gathering and analysis

All possible requirements of the system to be developed are captured in this phase and
documented in a requirement specification document.
  System design

The requirement specifications from first phase are studied in this phase and
system design is prepared. Design helps in specifying hardware and system
requirements and also helps in defining overall system architecture.

 Implementation

With inputs from system design, the system is first developed in small
programs called units, which are integrated in the next phase. Each unit is developed
and tested for its functionality which is referred to as Unit Testing.

 Integration and Testing

All the units developed in the implementation phase are integrated into a
system after testing of each unit. Post integration the entire system is tested for any
faults and failures.

Detailed Design of DFD

When it comes to conveying how information data flows through

systems (and how that data is transformed in the process), data flow diagrams
(DFDs) are the method of choice over technical descriptions for three principal
reasons.

• DFDs are easier to understand by technical and nontechnical audiences

• DFDs can provide a high-level system overview, complete with boundaries

and connections to other systems

• DFDs can provide a detailed representation of system components

DFDs help system designers and others during initial analysis stages visualize a
current system or one that may be necessary to meet new requirements.
Systems analysts prefer working with DFDs, particularly when they require a
clear understanding of the boundary between existing systems and postulated
systems. DFDs represent the following:
 • External devices sending and receiving data.

Processes that change that data.

Activity Diagram

• Activity diagram is basically a flowchart to represent the flow form one

activity to another activity. The activity can be described as an operation of
the system.
• Activity diagram for our application shown below, when the activity starts
the user should login to the application allows the user to the next activity
by entering correct username and password.
Use Case Diagram

Use case diagram in the Unified Modelling Language (UML) is a type of behavioural
diagram defined by and created from a Use-case analysis. Its purpose is to present a graphical
overview of the functionality provided by a system in terms of actors, their goals (represented
as use cases), and any dependencies between those use cases.

The main purpose of a use case diagram is to show what system functions are
performed for which actor. Roles of the actors in the system can be depicted.
Sequence Diagram

A sequence diagram shows object interactions arranged in a time sequence. It depicts

the object and classes involved in the scenario and the sequence of messages exchanged
between the objects needed to carry out the functionality of the scenario.

Sequence diagram are typically associated with use case realization in the logical
view of the system under development. Sequence diagrams are sometimes called event
diagrams or event scenario.
ER DIAGRAM
In software engineering, an entity-relationship model (ERM) is an abstract and conceptual
representation of data. Entity-relationship modelling is a modelling method, used to produce a
type of schema or model of a system, often a relational database, and its requirements in a
top-down fashion. Diagrams created by this process are called entity-relationship diagrams,
ER diagrams, or ERDs.

Symbol Description

Entity

Attribute

Entity Relationship

Primary Key
 -------------------- Referential Key

Weak Entity

Entity Relation Diagram

Class diagram
A Class is a Set of object that share a common structure and common behaviour. Class is an
abstraction of real-world items. An object is an instance or occurrence of a class. A Class
describes a group of relationship and semantics. Object in a class have the same attribute and
forma of behaviour. Most objects derive their individuality from difference in their attribute
values and specific relationships to other objects. A Class describe a group of objects with the
same properties, behaviour, kind of relationship and semantics. Class Diagram provides a
Graphic notation for modelling and their relationships, thereby describe the possible objects.
 Implementation

Implementation Approaches

In this stage physical system specifications are converted into a working and reliable
solution. This is where the system is developed. It involves careful planning, investigation of
the current system and its constraints on implementation, design of methods to achieve the
changeover, an evaluation, of change over methods.
The objective of the system implementation phase is to implement a fully functional system,
which deliverables met in order of priority. The result of this phase is an accurately
functioning system. The more complex system implemented, the more involved will be the
system analysis and the design effort required just for implementation.
The implementation phase deals with issues of quality, performance, baselines, libraries, and
debugging. The end deliverable is the product itself. During the implementation phase, the
system built according to the specifications from the previous phases. This includes writing
code, performing code reviews, performing tests, selecting components for integration,
configuration, and integration.
Web Application for report generation is implemented using php Object oriented
programming is an approach that provides a way of modularizing programs by creating
partitioned memory area for both data and functions that can used as templates for creating
copies of such modules on demand.

Project code
 Testing

Introduction

Web applications run on devices with limited memory, CPU power and power supply. The
behaviour of the application also depends on external factors like connectivity, general
system utilization, etc.
Therefore, it is very important to debug, test and optimize Web application. Having
reasonable test coverage for Web application helps to enhance and maintain the Web
application.
As it is not possible to test bootstrap Web applications on all possible device configurations,
it is a common practice to run on typical device configurations. Should test application at
least on one device with the lowest possible configuration. In addition, should test on one
device with the highest available configuration, e.g., pixel density, screen resolution to ensure
that it works fine on these devices.

Testing Concepts
Web application testing based on Unit. In general, a Unit test is a method whose statements
test a part of the application. Organizes test methods into classes called test cases, and group
test cases into test suites.

Unit tests

Local Unit Tests

Unit tests that run on local machine only. These tests compiled to run locally on xampp to
minimize execution time. Use this approach to run unit tests that have no dependencies on
the Web framework or have dependencies that mock objects can satisfy.
Instrumented unit tests
Unit tests that run on device. These tests have access to Instrumentation information, such as
the Context of the application are testing. Use this approach to run unit tests that have Web
application dependencies, which mock objects cannot easily satisfy.

Integration Tests
This type of test verifies that the target app behaves as expected when a user performs a
specific action or enters a specific input in its activities. For example, it allows checking that
the target app returns the correct UI output in response to user interactions in the app’s
activities. UI testing frameworks like Espresso allow programmatically simulating user
actions and testing complex intra-app user interactions.

Cross-app Components
This type of test verifies the correct behaviour of interactions between different user apps or
between user apps and system apps. For example, might want to test that app behaves correctly
when the user performs an action in the Settings menu. UI testing frameworks that support cross-
app interactions, such as UI Automaton, allow creating tests for such scenarios.

Test Cases:
A test case is a set of conditions or variables under which a tester will determine whether a
system under test satisfies requirements or works correctly. The process of developing text
causes can also help find problems in the requirements or design of an application.
The following tables show the various test causes scenarios that are generated along with the
required inputs o the given scenarios, expected outputs, actual output and the result whether
the test passes or fails.
Test causes with positive scenarios:
TC No Positive scenario Required Input Expected Actual output Test Result
output

1 Verify login page Enter a valid Should Logged in Pass

username and successfully successfully
password login

2 Verify Register Enter username Should Registered Pass

Page and other successfully successfully
details register

3 Add service Enter details Should display Displays the Pass

information the message post made
service added
successful

4 View service Click view Should display Displays the Pass

service button the record information
view the record information
information

5 Send request Fill proper Should display Displays the Pass

information information to the request booking
send request sent confirmation
successful message

6 View request View request by Display Record Pass

information using view service request displayed
request button successfully

7 Send feedback user can send Send feedback Feedback sent Pass
feedback to successfully
admin

8 View feedback User can view View Feedback pass

to view feedback displayed
feedback information successful
 9 Admin can view View registered View user Display user pass
the registered user users information information
details

10 Session Expiry Logout from the Session should Session Pass

site expire by expires from
erasing logged out
previous
actions of
users

Test Cases with Negative Scenarios:

TC Negative Required Input Expected Actual output Test Result
No. scenario output

1 Verify login Enter a Invalid Should Display error Pass

Page username and display error message
password message

2 Verify Register Enter existing Should not Cannot Pass

Page username register register with
existing users

3 Fill the record Skip some field Display Display error pass
information in request form validation message
information

4 Post request Enter request Should Display error Pass

information details display error message
message

5 Enter feedback Make blank Should Not Display enter Pass

without message updates update validation
 information

6 Send response Send blank Should not Display no Pass

request add to list notifications

Experimental Results

SNAP SHOTS

This chapter highlights the results of project and the snapshots for each of the activities
shown along with a description about the working of each activity. Each snapshot describes
every single step location based ad service management system. All the main activities as
well as the options provided to the users in each activity also shown in the following
snapshots.
 Conclusion and Future Enhancements

Conclusion

The vitality of Location Based Services (LBS) and the commercial promise it presents to both
the traditional industry and the emerging wireless devices industry is now well publicized. As
the location services are GPS-based, it makes the system accurate, sturdy and agile. Our
project presented in this paper give innovative and efficient solutions to generate revenue by
marketers and at the same time ensure happy customers. Better analysis of consumers is
possible with real-time market research resulting in a higher advertising impact.

Future scope:

 Cross platform Web app for better communication

 We can develop this application in cloud based that helps to speed up the process and
manage the data securely
 We can give a custom filter option with good user interface

Reference
 Abowd GD What next, ubicomp?: Celebrating an intellectual disappearing act. In:
2012 ACM Conference on Ubiquitous Computing (UbiComp 2012), Pittsburgh, PA,
5-8 September 2012 ACM, pp 31-40. doi:10.1145/2370216.2370222
 Ajzen I, Fishbein M (1977) Attitude-behavior relations: A theoretical analysis and
review of empirical research. Psychol Bull 84 (5):888-918. doi:10.1037/0033-
2909.84.5.888
 Al Shoaibi DA, Al Rassan IA Web advertising using location based services. In: 1st
International Conference on Internet Operating Systems (ICIOS 2012), Irvine,
CA, 10-12 December 2012. IEEE, pp 13-16. doi:10.1109/ICIOS.2012.15
 Albers A, Kahl C Design and implementation of context-sensitive Web marketing
platforms. In: 10th IEEE Conference on E-Commerce Technology and the 5th
IEEE Conference on Enterprise Computing, E-Commerce and E-Services
(CEC/IEEE 2008), Washington, D.C., 21-24 July 2008. IEEE, pp 273-278.
doi:10.1109/CECandEEE.2008.102
 Alt F, Michelis D, Müller J (2012) Pervasive advertising technologies. In: Pop S,
Stalder U, Tscherteu G, Struppek M (eds) Media cultures. Av Edition, Ludwigsburg,
Germany, pp 121-128 Alt F, Sahami Shirazi A, Pfeiffer M, Holleis P, Schmidt
A Taximedia: An interactive context-aware entertainment and advertising system.
In: 2nd International Workshop on Pervasive Advertising (PerAd 2009) in
conjunction with GI Jahrestagung 2009, Lübeck, Germany, 1 October 2009. pp 3933-
3940
 Alton L (2015) 10 ways location-based marketing will evolve in 2015.
Huffington Post. http://www.huffingtonpost.com/larry-alton/10-ways-locationbased-
mar_b_6423832.html. Accessed 21 July 2015