EN ISO 19132:2008

SLOVENSKI STANDARD
01-maj-2009
*HRJUDIVNHLQIRUPDFLMH6WRULWYHQDSRGODJLORNDFLMH5HIHUHQþQLPRGHO,62

Geographic information - Location-based services - Reference model (ISO 19132:2007)
Geoinformation - Standortbezogene Dienste - Referenzmodell (ISO 19132:2007)
Information géographique - Services basés sur la localisation - Modèle de référence (ISO
19132:2007)
Ta slovenski standard je istoveten z: EN ISO 19132:2008
ICS:
35.240.70 Uporabniške rešitve IT v IT applications in science
znanosti
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EUROPEAN STANDARD
EN ISO 19132
NORME EUROPÉENNE
EUROPÄISCHE NORM
August 2008
ICS 35.240.70
English Version
Geographic information - Location-based services - Reference
model (ISO 19132:2007)
Information géographique - Services basés sur la Geoinformation - Standortbezogene Dienste -
localisation - Modèle de référence (ISO 19132:2007) Referenzmodell (ISO 19132:2007)
This European Standard was approved by CEN on 15 August 2008.
CEN members are bound to comply with the CEN/CENELEC Internal Regulations which stipulate the conditions for giving this European
Standard the status of a national standard without any alteration. Up-to-date lists and bibliographical references concerning such national
standards may be obtained on application to the CEN Management Centre or to any CEN member.
This European Standard exists in three official versions (English, French, German). A version in any other language made by translation
under the responsibility of a CEN member into its own language and notified to the CEN Management Centre has the same status as the
official versions.
CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Cyprus, Czech Republic, Denmark, Estonia, Finland,
France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal,
Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland and United Kingdom.
EUROPEAN COMMITTEE FOR STANDARDIZATION
COMITÉ EUROPÉEN DE NORMALISATION
EUROPÄISCHES KOMITEE FÜR NORMUNG
Management Centre: rue de Stassart, 36  B-1050 Brussels
© 2008 CEN All rights of exploitation in any form and by any means reserved Ref. No. EN ISO 19132:2008: E
worldwide for CEN national Members.

Contents Page
Foreword.3

Foreword
The text of ISO 19132:2007 has been prepared by Technical Committee ISO/TC 211 “Geographic
information/Geomatics” of the International Organization for Standardization (ISO) and has been taken over
as EN ISO 19132:2008 by Technical Committee CEN/TC 287 “Geographic Information” the secretariat of
which is held by NEN.
This European Standard shall be given the status of a national standard, either by publication of an identical
text or by endorsement, at the latest by February 2009, and conflicting national standards shall be withdrawn
at the latest by February 2009.
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent
rights. CEN [and/or CENELEC] shall not be held responsible for identifying any or all such patent rights.
According to the CEN/CENELEC Internal Regulations, the national standards organizations of the following
countries are bound to implement this European Standard: Austria, Belgium, Bulgaria, Cyprus, Czech
Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia,
Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain,
Sweden, Switzerland and the United Kingdom.
Endorsement notice
The text of ISO 19132:2007 has been approved by CEN as a EN ISO 19132:2008 without any modification.

INTERNATIONAL ISO
STANDARD 19132
First edition
2007-10-15
Geographic information — Location-
based services — Reference model
Information géographique — Services basés sur la localisation —
Modèle de référence
Reference number
ISO 19132:2007(E)
©
ISO 2007
ISO 19132:2007(E)
PDF disclaimer
This PDF file may contain embedded typefaces. In accordance with Adobe's licensing policy, this file may be printed or viewed but
shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In
downloading this file, parties accept therein the responsibility of not infringing Adobe's licensing policy. The ISO Central Secretariat
accepts no liability in this area.
Adobe is a trademark of Adobe Systems Incorporated.
Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation
parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In
the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below.

©  ISO 2007
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means,
electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or
ISO's member body in the country of the requester.
ISO copyright office
Case postale 56 • CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail copyright@iso.org
Web www.iso.org
Published in Switzerland
ii © ISO 2007 – All rights reserved

ISO 19132:2007(E)
Contents Page
Foreword. vii
Introduction . viii
1 Scope . 1
2 Conformance. 2
3 Normative references . 2
4 Terms and definitions. 2
5 Symbols and abbreviated terms . 11
5.1 Acronyms . 11
5.2 UML Notation. 13
5.3 Taxonomy of data and services — Mapping to RDF. 13
6 ODP Viewpoints used. 15
6.1 Enterprise specification . 15
6.2 Information specification . 15
6.3 Computational specification. 15
7 Participation Model. 15
7.1 Model overview – Package: ISO 19132 (this International Standard). 15
7.2 Package – LBS Participants . 17
7.2.1 Scenarios and semantics. 17
7.2.2 Type – LBS_Participant. 19
7.2.3 Type – LBS_User . 20
7.2.4 Type – LBS_ApplicationProvider. 23
7.2.5 Type – LBS_DataProvider. 24
7.2.6 Type – LBS_FeatureDataProvider. 24
7.2.7 Type – LBS_ContentProvider . 24
7.2.8 Type – LBS_SpatialContentProvider . 24
7.2.9 Type – LBS_ServiceProvider. 24
7.2.10 Type – LBS_ServiceBroker. 25
7.2.11 Type – LBS_MobileDevice . 25
7.2.12 Type – LBS_DataBroker – Class semantics . 26
8 Service model. 26
8.1 Package – LBS_Services . 26
8.1.1 Package structure. 26
8.1.2 Service taxonomy . 27
8.2 Package – Basic Services. 27
8.2.1 Package structure. 27
8.2.2 Type – LBS_Tracking . 28
8.2.3 Type – LBS_Routing. 29
8.2.4 Type – LBS_Navigation. 30
8.3 Package – Geomatics services . 31
8.3.1 Package structure. 31
8.3.2 Type – LBS_Location Transformation.32
8.3.3 Type – LBS_AddressParsing. 34
8.3.4 Type – LBS_Geoparsing . 34
8.3.5 Type – LBS_Gazetteer. 35
8.3.6 Type – LBS_MapService . 36
8.4 Package – Information Services. 37
8.4.1 Package structure. 37
8.4.2 Type – LBS_DataService. 37
ISO 19132:2007(E)
8.4.3 Type – LBS_NetworkDataService – semantics. 39
8.4.4 Type – LBS_EventSubscription. 40
8.4.5 Type – LBS_MovingObjectManagement. 41
8.5 Package – System management. 41
8.5.1 Managing users and groups . 41
8.5.2 Type – LBS_UserProfileService. 41
8.5.3 Type – LBS_LocationTriggerControl . 42
8.6 Package – Digital rights management . 42
8.6.1 Digital rights management. 42
8.6.2 Type – LBS_Resource . 43
8.6.3 Type – LBS_License . 43
8.6.4 Type – LBS_Right . 43
8.6.5 Type – LBS_RightsCondition. 44
9 Message Data Model. 44
9.1 Semantics . 44
9.2 Package – Message Data Types . 44
9.2.1 Package structure . 44
9.2.2 Type – LanguageSpecificCharacterString. 45
9.2.3 Type – LBS_AccessInfo . 46
9.2.4 Type – LBS_Accuracy – Class semantics . 47
9.2.5 Type – LBS_Address . 47
9.2.6 Type – LBS_CostFunction . 47
9.2.7 Type – LBS_Data. 48
9.2.8 Type – LBS_DataSource. 48
9.2.9 Type – LBS_DisplayParameters . 49
9.2.10 Type – LBS_EventInfo . 50
9.2.11 Type – LBS_Instruction . 50
9.2.12 Type – LBS_Location. 51
9.2.13 Type – LBS_Maneuver. 51
9.2.14 Type – LBS_MapFormat . 52
9.2.15 Type – LBS_Notification. 52
9.2.16 Type – LBS_Position . 53
9.2.17 Type – LBS_Preference . 53
9.2.18 Type – LBS_Route . 54
9.2.19 Type – LBS_RouteConstraint . 55
9.2.20 Type – LBS_RouteCriteria. 55
9.2.21 Type – LBS_SecurityCertificate. 56
9.2.22 Type – LBS_SymbolSet . 57
9.2.23 Type – LBS_TrackingLocation. 57
9.2.24 Type – LBS_Trigger . 58
9.2.25 Type – LBS_UserID . 58
9.2.26 Union – LBS_FeatureData . 59
9.2.27 Union – LBS_GeometryChoice. 59
9.2.28 Union – LBS_NamedLocation. 60
9.2.29 Union – LBS_TrackTrigger. 61
Annex A (normative) Abstract test suite. 62
Annex B (informative) Architecture . 66
Annex C (informative) Scenarios . 69
Annex D (informative) Standards development in LBS . 75
Annex E (informative) Crosswalk between common terminology in ISO/TC 211 and ISO/TC 204 . 77
Annex F (informative) Use cases for location-based services . 87
Bibliography . 91

iv © ISO 2007 – All rights reserved

ISO 19132:2007(E)
Figures
Figure 1 — Relation between LBS and GIS. viii
Figure 2 — Simplified navigation service represented as an RDF graph. 14
Figure 3 — Example of composition of services. 14
Figure 4 — Overview of UML package structure. 16
Figure 5 — Package dependencies to other ISO standards. 17
Figure 6 — Roles of the Enterprise view. 18
Figure 7 — Enterprise view communication channels as associations . 19
Figure 8 — License associations for LBS_Participant . 19
Figure 9 — LBS_User associations . 20
Figure 10 — LBS_ApplicationProvider associations. 24
Figure 11 — Service provider associations . 25
Figure 12 — Service broker associations . 25
Figure 13 — Mobile device associations. 26
Figure 14 — Subpackages of LBS_Services. 27
Figure 15 — Basic services . 28
Figure 16 — Context Diagram: LBS_Tracking. 29
Figure 17 — Context Diagram: LBS_Routing . 30
Figure 18 — Context Diagram: LBS_Navigation . 31
Figure 19 — Geomatics services . 32
Figure 20 — Context Diagram: LBS_LocationTransformation . 33
Figure 21 — Context Diagram: LBS_AddressParsing .34
Figure 22 — Context Diagram: LBS_Geoparsing. 34
Figure 23 — Context Diagram: LBS_Gazetteer . 35
Figure 24 — Context Diagram: LBS_MapService. 37
Figure 25 — Information services . 38
Figure 26 — Context Diagram: LBS_DataService . 38
Figure 27 — Context Diagram: LBS_NetworkDataService. 39
Figure 28 — Context Diagram: LBS_EventSubscription. 40
Figure 29 — Context Diagram: LBS_MovingObjectManagement. 41
Figure 30 — Context Diagram: LBS_UserProfileService.41
Figure 31 — Context Diagram: LBS_LocationTriggerControl. 42
Figure 32 — Digital rights management types . 43
Figure 33 — Message data types . 45
Figure 34 — Context diagram: LanguageSpecificCharacterString . 46
Figure 35 — Context diagram: LBS_AccessInfo . 46
Figure 36 — Context Diagram: LBS_Accuracy. 47
Figure 37 — Context Diagram: LBS_Address. 47
Figure 38 — Context Diagram: LBS_CostFunction. 47
ISO 19132:2007(E)
Figure 39 — Context Diagram: LBS_Data . 48
Figure 40 — Context Diagram: LBS_DataSource . 48
Figure 41 — Context Diagram: LBS_DisplayParameters. 49
Figure 42 — Context Diagram: LBS_EventInfo. 50
Figure 43 — Context Diagram: LBS_Instruction. 51
Figure 44 — Context Diagram: LBS_Location . 51
Figure 45 — Context Diagram: LBS_Maneuver . 52
Figure 46 — Context Diagram: LBS_MapFormat. 52
Figure 47 — Context Diagram: LBS_Notification . 53
Figure 48 — Context Diagram: LBS_Position . 53
Figure 49 — Context Diagram: LBS_Preference. 54
Figure 50 — Context Diagram: LBS_Route . 54
Figure 51 — Context Diagram: LBS_RouteConstraint. 55
Figure 52 — Context Diagram: LBS_RouteCriteria . 56
Figure 53 — Context Diagram: LBS_SecurityCertificate . 57
Figure 54 — Context Diagram: LBS_SymbolSet. 57
Figure 55 — Context Diagram: LBS_TrackingLocation .58
Figure 56 — Context Diagram: LBS_Trigger. 58
Figure 57 — Context Diagram: LBS_UserID. 59
Figure 58 — Context Diagram: LBS_FeatureData . 59
Figure 59 — Context Diagram: LBS_GeometryChoice . 60
Figure 60 — Context Diagram: LBS_NamedLocation .61
Figure 61 — Context Diagram: LBS_TrackTrigger . 61
Figure B.1 — Conceptual architecture equating mobile and non-mobile services . 66
Figure B.2 — LBS interface schema and tentative standardization items. 67

Tables
Table B.1 — Elementary components of LBS . 67
Table D.1 — Standards Development Organizations in LBS. 75
Table E.1 — Data model terminology. 79
Table E.2 — Mathematical terminology . 80
Table E.3 — Geodetic terminology. 81
Table E.4 — Geometric terminology . 83
Table E.5 — World model (feature) terminology. 84
Table E.6 — Functional definitions . 85

vi © ISO 2007 – All rights reserved

ISO 19132:2007(E)
Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards bodies
(ISO member bodies). The work of preparing International Standards is normally carried out through
ISO technical committees. Each member body interested in a subject for which a technical committee has
been established has the right to be represented on that committee. International organizations, governmental
and non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely with the
International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.
The main task of technical committees is to prepare International Standards. Draft International Standards
adopted by the technical committees are circulated to the member bodies for voting. Publication as an
International Standard requires approval by at least 75 % of the member bodies casting a vote.
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent
rights. ISO shall not be held responsible for identifying any or all such patent rights.
ISO 19132 was prepared by Technical Committee ISO/TC 211, Geographic information/Geomatics.
ISO 19132:2007(E)
Introduction
This International Standard establishes a framework supporting the development of location-based services
(LBS). LBS are software services whose request and response pattern or values depend upon the location of
some number of things, either real or conceptual. For example, tracking and navigation as defined in
ISO 19133 are both location-based. Emergency response services are location-based since the requested
assistance is invariably for a location fairly near the requestor at the time of the request. Environmental
monitoring and remediation is dependent on the location and motion or other continuous change of the
polluting agents. Even yellow-page directory services are dependent on the location, or tentative future
location, of the requestor in search of a convenient business location for the acquisition of specific goods or
services, either near his current location or his planned route.
A reference model is a conceptual framework consisting of a set of system decisions, both architectural and
policy, which construct the logical environment for a set of applications and processes within a specific domain.
A framework contains or references a taxonomy of terms and an ontology that defines the target domain.
A framework can contain or reference other frameworks for related application sets or design paradigms. An
LBS framework may relate to a framework of geographic information services, since much of its activity is
associated to manipulation of location representations and the use of location as a key to other services.
Models for frameworks exist at a variety of levels of abstraction, each of which is a generalization of the more
detailed model, and a specialization of the more general ones. At the highest level, the only entities are the
frameworks representing their respective reference models. This is illustrated in Figure 1.

Figure 1 — Relation between LBS and GIS
What this says, in its simplest and most direct terms, is that the two frameworks are coupled and, depending
on form more than on functionality, each will invoke services (functions) supplied by the other. This
International Standard deals with the communication across the channel depicted in Figure 1. It does so by
creating a reference model for the location-based services framework and linking it to the reference model
defined in ISO 19101 and ISO/TS 19101-2.
1) 2)
A distinction between an LBS service and a GIS service is that LBS will normally have a larger granularity
and significant non-spatial information component, and therefore is able to interact with both geographic data

1) The term “LBS” includes the word “service”, and so the phrase “LBS service” is logically redundant. When discussing
LBSs in relation to other software components, the phrase “LBS service” can be used to maintain symmetry of expression.
While logically inconsistent, this is grammatically and poetically acceptable.
2) It would be useful to redefine GIS as “geographic information service”, but past attempts to override the definition of
“geographic information system” with “geographic information science” have not proven very fruitful. In this International
Standard, all software components are viewed as services, and so mentions of “GIS” will be taken as “service
implementation of GIS functionality”.
viii © ISO 2007 – All rights reserved

ISO 19132:2007(E)
frameworks and with general information frameworks containing non-spatial data. Such data may be spatially
linked in manners not traditionally used in geographic systems, such as by postal address or telephone
number. Another distinction is that LBS services have to deal with the delivery mechanism at a finer level than
GIS frameworks. LBS clients are likely to include mobile devices on a multitude of network types, and with a
wide variety of capabilities. Thus, an LBS framework supports the same services through a variety of different
interface protocols, each tailored for a class of client needs and capabilities. While the details of each client
device's interface protocols are beyond the scope of this International Standard, it does address the common
semantics of all of the LBS client classes by defining a set of common patterns that provide extensible
templates for applications within this domain.
Two of the annexes included in this International Standard are there to highlight the harmonization issue as
the LBS domain develops. Organizations that develop standards in LBS need to be aware of other activities.
Annex D lists some of the important standards development organizations. Annex E is a crosswalk between
common terminology in the geographic information and the intelligent transport system domains. Crosswalks
between common terminologies of differing domains are important for semantic interoperability. ITS is used
only as an example of one crosswalk.

INTERNATIONAL STANDARD ISO 19132:2007(E)

Geographic information — Location-based services —
Reference model
1 Scope
This International Standard defines a reference model and a conceptual framework for location-based
services (LBS), and describes the basic principles by which LBS applications may interoperate. This
framework references or contains an ontology, a taxonomy, a set of design patterns and a core set of LBS
service abstract specifications in UML. This International Standard further specifies the framework's
relationship to other frameworks, applications and services for geographic information and to client
applications.
This International Standard addresses, for an LBS system, the first three basic viewpoints as defined in the
Reference Model for Open Distributed Processing (RM-ODP, see ISO/IEC 10746-1). These viewpoints are
the
a) Enterprise Viewpoint – detailing the purpose, scope, and policies of the system,
b) Information Viewpoint – detailing the semantics of information and processing within the system,
c) Computational Viewpoint – detailing the functional decomposition of the system.
The fourth and fifth viewpoints are addressed only in requirements or examples. These are the
d) Engineering Viewpoint – detailing the infrastructure for distribution,
e) Technology Viewpoint – detailing the technology for implementation.
Reference models and frameworks can be defined at a variety of levels, from conceptual design to software
documentation. This International Standard
⎯ defines the conceptual framework for, and the type of applications included within, LBS,
⎯ establishes general principles for LBS for both mobile and fixed clients,
⎯ specifies the interface for data access while roaming,
⎯ defines the architectural relationship with other ISO geographic information standards,
⎯ identifies areas in which further standards for LBS are required.
This International Standard does not address the following issues:
⎯ rules by which LBS are developed;
⎯ general principles for roaming agreements for mobile clients and tracking targets.
ISO 19132:2007(E)
2 Conformance
Conformance to this International Standard takes on several meanings depending on the type of entity
declaring conformance.
⎯ Semantic conformance shall imply that the terminology used by the candidate corresponds explicitly to
this International Standard where possible.
⎯ Data conformance shall imply the usage of data types within application schemas or design
specifications that are mappable into types in this International Standard, as in a UML realization of a type
by a class.
⎯ Service conformance shall imply both the consistent use of message-based request-response
interfaces and data conformance for the message packages used by those interfaces.
Conformance may be claimed by a standard, a data structure or schema (such as an encoding definition) or a
software module. In all cases, semantics and data conformance are possible. Service conformance is limited
to either software or interface specification based on a service-oriented architecture. In service conformance,
a data structure may claim this conformance only as part of a larger operational structure (such as the role of
XML in SOAP-based SOA applications).
Details for conformance tests are given in Annex A.
3 Normative references
The following referenced documents are indispensable for the application of this document. For dated
references, only the edition cited applies. For undated references, the latest edition of the referenced
document (including any amendments) applies.
ISO 19107, Geographic information — Spatial schema
ISO 19109, Geographic information — Rules for application schema
ISO 19110, Geographic information — Methodology for feature cataloguing
ISO 19112, Geographic information — Spatial referencing by geographic identifiers
ISO 19133, Geographic information — Location-based services — Tracking and navigation
ISO 19136, Geographic information — Geography Markup Language (GML)
4 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
4.1
active object
object which is capable of independent actions, and therefore capable of initiating interactions between itself
and other objects without immediate prior external stimulation
cf. passive object (4.35)
NOTE An active object can represent a user or an active service that depends on internal (and therefore not visible)
triggers to start actions. Active and passive states can exist for the same object, and such a service can transition
between these two states depending on invocation of an activation or deactivation operation protocol.
2 © ISO 2007 – All rights reserved

ISO 19132:2007(E)
4.2
basic service
service providing a basic function to other services or applications in a functional manner
cf. interoperate (4.18)
NOTE Basic services lack any persistent, user-specific state information between invocations and are not meant for
direct access by users. Because they act in a functional manner, they are readily replaceable at runtime by other services
using the same interfaces.
4.3
candidate route
any route that satisfies all constraints of the routing request, with the possible exception of optimality of the
cost function
[ISO 19133]
NOTE Navigation is the process of finding the candidate route that optimizes a chosen cost function.
4.4
cluster
collection of targets potentially heterogeneous (each satisfying a different query criteria) whose locations fall
within a small neighbourhood
4.5
constraint
restriction on how a link or turn may be traversed by a vehicle, such as vehicle classification, or a physical
or temporal constraint
[ISO 19133]
4.6
continuous change
change in an attribute whose type has a distance measure such that its value can be assumed to take on
intermediate values between two known measurements
NOTE The interpolation of continuous change is usually done by taking into consideration constraints on the “curve”
joining the two data points (time1, value1) and (time2, value2), looking at the value as a function of time. For example, if
the continuous change is for the motion of a vehicle, then the constraints of physics and of the paths app
...