|
US$1774.00 · In stock
Delivery: <= 8 days. True-PDF full-copy in English will be manually translated and delivered via email.
GB/T 27918-2011: Geographic information -- Location based services -- Reference model
Status: Valid
| Standard ID | Contents [version] | USD | STEP2 | [PDF] delivered in | Standard Title (Description) | Status | PDF |
| GB/T 27918-2011 | English | 1774 |
Add to Cart
|
8 days [Need to translate]
|
Geographic information -- Location based services -- Reference model
| Valid |
GB/T 27918-2011
|
PDF similar to GB/T 27918-2011
Basic data | Standard ID | GB/T 27918-2011 (GB/T27918-2011) | | Description (Translated English) | Geographic information -- Location based services -- Reference model | | Sector / Industry | National Standard (Recommended) | | Classification of Chinese Standard | A75 | | Classification of International Standard | 35.240.70; 07.040 | | Word Count Estimation | 89,815 | | Date of Issue | 2011-12-30 | | Date of Implementation | 2012-02-01 | | Quoted Standard | GB/T 23707-2009; GB/T 23708-2009; ISO 19109; ISO 19110; ISO 19112; ISO 19133 | | Adopted Standard | ISO 19132-2007, IDT | | Regulation (derived from) | Announcement of Newly Approved National Standards No. 23 of 2011 | | Issuing agency(ies) | General Administration of Quality Supervision, Inspection and Quarantine of the People's Republic of China, Standardization Administration of the People's Republic of China | | Summary | This standard specifies the location-based services (LBS) reference model and conceptual framework, and describes the implementation of LBS applications for the fundamental principles of interoperability. The conceptual framework involves or includes ontology, classification systems, and the use of design patterns represent the core of LBS services UML abstract specification. This standard is also the conceptual framework with other frameworks relationship between geographic information applications and services and client applications are further described. | GB/T 27918-2011: Geographic information -- Location based services -- Reference model---This is a DRAFT version for illustration, not a final translation. Full copy of true-PDF in English version (including equations, symbols, images, flow-chart, tables, and figures etc.) will be manually/carefully translated upon your order.
Geographic information. Location based services. Reference model
ICS 35.240.70; 07.040
A75
National Standards of People's Republic of China
Geographic location-based information services Reference Model
(ISO 19132.2007, IDT)
Issued on. 2011-12-30
2012-02-01 implementation
Administration of Quality Supervision, Inspection and Quarantine of People's Republic of China
Standardization Administration of China released
Table of Contents
Preface Ⅶ
Introduction Ⅷ
1 Scope 1
Consistency 1 2
3 Normative references 2
4 Terms and definitions 2
5 symbols and abbreviations 9
9 5.1 Acronyms
5.2 UML notation 11
5.3 Data and Services Classification. Mapping to RDF 11
6 ODP (Open Distributed Processing) Perspective 12
6.1 enterprise specification 12
6.2 Message Specification 12
6.3 Calculation Specifications 12
7 Participation Model 12
7.1 Model Overview - Package. ISO 19132 (the present standard) 12
7.2 package -LBSParticipants (LBS participants) 13
7.2.1 scene and semantics 13
7.2.2 Type -LBS_Participant (LBS_ participants) 15
7.2.3 Type -LBS_User (LBS_ users) 16
7.2.4 Type -LBS_ApplicationProvider (LBS_ application provider) 19
7.2.5 Type -LBS_DataProvider (LBS_ data provider) 19
7.2.6 Type -LBS_FeatureDataProvider (LBS_ element data provider) 19
7.2.7 Type -LBS_ContentProvider (LBS_ content provider) 19
7.2.8 Type -LBS_SpatialContentProvider (LBS_ space content provider) 19
7.2.9 Type -LBS_ServiceProvider (LBS_ ISP) 19
7.2.10 type -LBS_ServiceBroker (LBS_ service agents) 20
7.2.11 type -LBS_MobileDevice (LBS_ mobile device) 20
7.2.12 type -LBS_DataBroker (LBS_ Data Distributor) - Semantic class 21
8 service model 21
8.1 package -LBS_Services (LBS_ Service) 21
8.1.1 package structure 21
21 8.1.2 Service Categories
8.2 package -BasicService (basic services) 22
8.2.1 package structure 22
8.2.2 Type -LBS_Tracking (LBS_ tracking) 22
8.2.3 Type -LBS_Routing (LBS_ Path Planning) 23
8.2.4 Type -LBS_Navigation (LBS_ Navigation) 24
8.3 package -GeomaticsServices (Geographic Information Service) 25
8.3.1 package structure 25
8.3.2 Type -LBS_LocationTransformation (LBS_ position conversion) 26
8.3.3 Type -LBS_AddressParsing (LBS_ address resolution) 27
8.3.4 Type -LBS_Geoparsing (LBS_ Geographical Analysis) 27
8.3.5 Type -LBS_Gazetteer (LBS_ gazetteer) 28
8.3.6 Type -LBS_MapService (LBS_ Map Service) 28
8.4 package -InformationServices (Information Services) 29
8.4.1 package structure 29
8.4.2 Type -LBS_DataService (LBS_ Data Services) 30
8.4.3 Type -LBS_NetworkDataService (LBS_ Data Network Services) - Semantics 31
8.4.4 Type -LBS_EventSubscription (LBS_ event subscription) 32
8.4.5 Type -LBS_MovingObjectManagement (LBS_ moving object management) 32
8.5 package -SystemManagement (System Administration) 33
8.5.1 Managing users and groups 33
8.5.2 Type -LBS_UserProfileService (LBS_ user-specific standard service) 33
8.5.3 Type -LBS_LocationTriggerControl (LBS_ trigger position control) 33
8.6 package -DigitalRightsManagement (digital rights management) 34
8.6.1 Digital Rights Management 34
8.6.2 Type -LBS_Resource (LBS_ resources) 35
8.6.3 Type -LBS_License (LBS_ License) 35
8.6.4 Type -LBS_Right (LBS_ authority) 35
8.6.5 Type -LBS_RightsCondition (LBS_ permission condition) 35
9 MessageDataModel (message data model) 35
9.1 semantics 35
9.2 package -Package-MessageDataTypes (message data type) 36
9.2.1 package structure 36
9.2.2 Type -LanguageSpecificCharacterString (specific language strings) 36
9.2.3 Type -LBS_AcessInfo (LBS_ access information) 37
9.2.4 Type -LBS_Accuracy (LBS_ accuracy) - Semantic class 38
9.2.5 Type -LBS_Address (LBS_ address) 38
9.2.6 Type -LBS_CostFunction (LBS_ cost function) 38
9.2.7 Type -LBS_Data (LBS_ data) 39
9.2.8 Type -LBS_DataSource (LBS_ data sources) 39
9.2.9 Type -LBS_DisplayParameters (LBS_ display parameters) 39
9.2.10 type -LBS_EventInfo (LBS_ event information) 40
9.2.11 type -LBS_Instruction (LBS_ Directive) 41
9.2.12 type -LBS_Location (LBS_ Location) 42
9.2.13 type -LBS_Maneuver (LBS_ travel policy) 42
9.2.14 type -LBS_MapFormat (LBS_ map format) 43
9.2.15 type -LBS_Notification (LBS_ notification) 43
9.2.16 type -LBS_Position (LBS_ position) 43
9.2.17 type -LBS_Preference (LBS_ preference) 44
9.2.18 type -LBS_Route (LBS_ Path Planning) 44
9.2.19 Type -LBS_RouteConstraint 45
9.2.20 type -LBS_RouteCriteria (LBS_ path Guidelines) 45
9.2.21 type -LBS_SecurityCertificate (LBS_ security verification) 46
9.2.22 type -LBS_SymbolSet (LBS_ symbol sets) 47
9.2.23 type -LBS_TrackingLocation (LBS_ tracking) 47
9.2.24 type -LBS_Trigger (LBS_ trigger) 47
9.2.25 type -LBS_UserID (LBS_ user ID) 48
9.2.26 Joint -LBS_FeatureData (LBS_ element data) 48
9.2.27 Joint -LBS_GeometryChoice (LBS_ geometry selection) 49
9.2.28 Joint -LBS_NamedLocation (LBS_ named location) 49
9.2.29 Joint -LBS_TrackTrigger (LBS_ trigger) 50
Appendix A (normative) Test Suite 51
Annex B (informative) architecture 54
Annex C (normative) scenarios 56
Appendix D (Informative Appendix) LBS standards 61
Appendix E (Informative Appendix) ISO /TC211 and ISO /TC204 terminology track 63
Annex F (informative) Example use location-based services 73
References 76
1 LBS and GIS Ⅶ relationship diagram
Figure 2 represents a simplified diagram of the navigation service 11 RDF
Example 12 3 service configuration
4 UML package diagram overview 13
Figure 5 dependencies with other ISO standard package 13
Figure 6 Enterprise Perspective Role 14
Enterprise perspective in FIG. 7 associated with the communication channel 15
Figure 8 LBS_Participant certificate associated 15
Figure 9 LBS_User associated 16
Figure 10 LBS_ApplicationProvider associated 19
11 associate service providers 20
12 associate service agent 20
13 associated with the mobile device 20
Figure 14 LBS_Services subpackages 21
15 22 basic services
FIG. 16 diagram. LBS_Tracking 23
Figure 17 Diagram. LBS_Routing 24
Figure 18 Diagram. LBS_Navigation 24
19 25 Geographic Information Services
FIG. 20 diagram. LBS_LocationTransformation 26
Figure 21 Diagram. LBS_AddressParsing 27
Figure 22 Diagram. LBS_Geoparsing 27
FIG. 23 diagram. LBS_Gazetteer 28
Figure 24 Diagram. LBS_MapService 29
25 Information services 30
Figure 26 Diagram. LBS_DataService 30
Figure 27 Diagram. LBS_NetworkDataService 31
Figure 28 Diagram. LBS_EventSubscription 32
Figure 29 Diagram. LBS_MovingObjectManagement 33
Figure 30 Diagram. LBS_UserProfileService 33
Figure 31 Diagram. LBS_LocationTriggerControl 34
32 digital rights management 34 type
Figure 33 Type 36 message data
Figure 34 Diagram. LanguageSpecificCharacterString 37
Figure 35 Diagram. LBS_AccessInfo 37
Figure 36 Diagram. LBS_Accuracy 38
Figure 37 Diagram. LBS_Address 38
FIG. 38 diagram. LBS_CostFunction 38
FIG. 39 diagram. LBS_Data 39
Figure 40 Diagram. LBS_DataSource 39
Figure 41 Diagram. LBS_DisplayParameters 40
Figure 42 Diagram. LBS_EventInfo 41
FIG. 43 diagram. LBS_Instruction 41
FIG. 44 diagram. LBS_Location 42
Figure 45 Diagram. LBS_Maneuver 42
Figure 46 Diagram. LBS_MapFormat 43
Figure 47 Diagram. LBS_Notification 43
FIG. 48 diagram. LBS_Position 44
FIG. 49 diagram. LBS_Preference 44
Figure 50 Diagram. LBS_Route 44
Figure 51 Diagram. LBS_RouteConstraint 45
FIG. 52 diagram. LBS_RouteCriteria 45
FIG. 53 diagram. LBS_SecurityCertificate 46
Figure 54 Diagram. LBS_SymbolSet 47
FIG. 55 diagram. LBS_TrackingLocation 47
FIG. 56 diagram. LBS_Trigger 48
FIG. 57 diagram. LBS_UserID 48
FIG. 58 diagram. LBS_FeatureData 48
FIG. 59 diagram. LBS_GeometryChoice 49
FIG. 60 diagram. LBS_NamedLocation 50
FIG. 61 diagram. LBS_TrackTrigger 50
Figure B.1 conceptual structure equivalent to 54 mobile and non-mobile services
Figure B.2 LBS interface mode with the provisional standard item 55
Table B.1 LBS basic components 55
61 Table D.1 LBS Standards Organization
Table E.1 term data model 64
Table E.2 mathematical terms 66
67 Table E.3 terminology mapping
68 Table E.4 geometric terms
Table E.5 world model (element) is defined 69
Table E.6 function definitions 70
Foreword
This standard was drafted in accordance with GB/T 1.1-2009 given rules.
This standard uses the translation method identical with the International Standards Organization for Standardization Technical Committee of Geographic Information (ISO /TC211) developed
ISO 19132.2007 "location-based geographic information service reference model." According to our country, the international standards for the following series
Series of Review.
Write a method --- the implementation of standards GB/T 1.1-2009 "Standardization Guide Part 1. Standard structure and drafting"
GB/T 20000.2-2009 "Standardization Guide Part 2. the use of international standards";
--- Deleted the preface to the international standards;
--- Introduction of this standard uses the ISO 19132.2007 introduction, but made minor modifications;
--- For the ISO 19132.2007 and other international standards are adopted as our reference standard, this standard direct reference to our standards on behalf of the
For the corresponding international standards;
--- Modify the original text with the latest technology applications incompatible Description. text translation appendix C.6 period to the effect that
"This information is ideal for details and format depends on the user and internet access services through phone access is limited to words or language
Sound information, and get access journey PDA or similar device through full-color map "; Currently, 3G mobile phones have been able to
It provides graphics services, current technology does not meet the original application, this standard to increase the labeling will be explained;
--- In order to maintain traceability references, citations of entries use the original English label.
This standard was proposed by the State Bureau of Surveying and Mapping.
This standard by the National Geographic Information Standardization Committee (SAC/TC230) centralized.
This standard was drafted. Beijing NavInfo Technology Co., Ltd., National Geomatics Center of China, Beijing hypergraph Geographic Information Technology
Surgery Ltd., Wuhan University.
Drafters of this standard. Huang Dong, Li Li, Sun Yuguo, CAO Xiao Hang, Li Lin, Li Kai.
Introduction
This standard framework for the establishment of a support system for location-based services (LBS) development. LBS is a software service that request and response
Mode depending on the position of some specific things, these things can be real or conceptual. For example, as defined in ISO 19133 in now
Tracking and navigation are based location services. Since the emergency response service position invariance, that is always very close to the requestor when
Position, and therefore the location-based services. Environmental monitoring and correction also depends on the position and motion of pollution or other continuous process of change.
Even when the requester to obtain certain goods or services and convenient business location search, yellow pages directory service also depends on the position or
The standard definition of location-based services (LBS) reference model and a conceptual framework, and describes the implementation group for interoperable LBS applications
This principle. The conceptual framework involves or includes ontology, classification systems, design patterns and core LBS service abstract use UML representation
specification. This standard is also the relationship between the conceptual framework and other frameworks, geographic information applications and services, and made into a client application
Step instructions.
The system calculates the standard discussion of LBS Reference Model (RM-ODP, see ISO /IEC 10746-1) at a predetermined open distribution
The first three fundamental justice perspective, they are.
a) target enterprise perspective --- refining system, scope and approach.
b) information Angle --- refinement process semantics and system information.
c) function calculates the perspective --- refining system decomposition.
The remaining two perspectives needs or only for example, they are.
Deployment d) Engineering Perspective --- refining infrastructure.
e) Technical Perspective --- refine enabling technologies.
Reference model and framework can be designed at all levels from concept to define software documentation. This standard.
--- The definition contained in the LBS in the conceptual framework and application types;
--- Establish general principles also apply to LBS mobile and fixed clients;
--- Predetermined data when roaming access interface;
--- Definition and other ISO geographic information standards in the framework of the relationship;
--- Identify other aspects in the field of LBS for further standardization.
This standard does not discuss the following questions.
--- Development of LBS rules;
--- General Principles for mobile clients and track targets roaming agreements.
2 Conformance
Any statement to this standard consistent product should meet the requirements of normative provisions and Appendix.
The consistency of this standard have a variety of meanings, depending on the type of entity declaration.
--- Choose to use the term semantic consistency as far as possible correspond with this standard;
--- Data consistency as UML can be used to implement a class type, pattern or design application specification data types
The use of this standard can be mapped to the type;
--- Service request response message consistent use interface to maintain consistency, and packet data interface to maintain consistency.
Consistency can be declared by the standard, data structures, data models (such as encoding defined) or software mode. In all cases, the language
Righteousness and data consistency is achieved. Consistency and services are limited to the software interface specifications or service-oriented architecture. Consistency in service
The data structure as part of a larger hierarchical structure of the operation declared its consistency. (Such as XML SOA SOAP-based applications
In the role. )
Details on conformance testing is given in Appendix A.
Tips & Frequently Asked Questions:Question 1: How long will the true-PDF of GB/T 27918-2011_English be delivered?Answer: Upon your order, we will start to translate GB/T 27918-2011_English as soon as possible, and keep you informed of the progress. The lead time is typically 5 ~ 8 working days. The lengthier the document the longer the lead time. Question 2: Can I share the purchased PDF of GB/T 27918-2011_English with my colleagues?Answer: Yes. The purchased PDF of GB/T 27918-2011_English will be deemed to be sold to your employer/organization who actually pays for it, including your colleagues and your employer's intranet. Question 3: Does the price include tax/VAT?Answer: Yes. Our tax invoice, downloaded/delivered in 9 seconds, includes all tax/VAT and complies with 100+ countries' tax regulations (tax exempted in 100+ countries) -- See Avoidance of Double Taxation Agreements (DTAs): List of DTAs signed between Singapore and 100+ countriesQuestion 4: Do you accept my currency other than USD?Answer: Yes. If you need your currency to be printed on the invoice, please write an email to [email protected]. In 2 working-hours, we will create a special link for you to pay in any currencies. Otherwise, follow the normal steps: Add to Cart -- Checkout -- Select your currency to pay.
|