1、 Collection of SANS standards in electronic format (PDF) 1. Copyright This standard is available to staff members of companies that have subscribed to the complete collection of SANS standards in accordance with a formal copyright agreement. This document may reside on a CENTRAL FILE SERVER or INTRA
2、NET SYSTEM only. Unless specific permission has been granted, this document MAY NOT be sent or given to staff members from other companies or organizations. Doing so would constitute a VIOLATION of SABS copyright rules. 2. Indemnity The South African Bureau of Standards accepts no liability for any
3、damage whatsoever than may result from the use of this material or the information contain therein, irrespective of the cause and quantum thereof. ISBN 978-0-626-21871-3 SANS 24730-1:2008Edition 1ISO/IEC 24730-1:2006Edition 1SOUTH AFRICAN NATIONAL STANDARD Information technology Real-time locating s
4、ystems (RTLS) Part 1: Application program interface (API) Published by SABS Standards Division 1 Dr Lategan Road Groenkloof Private Bag X191 Pretoria 0001Tel: +27 12 428 7911 Fax: +27 12 344 1568 www.sabs.co.za SABS This national standard is the identical implementation of ISO/IEC 24730-1:2006 and i
5、s adopted with the permission of the International Organization for Standardization and the International Electrotechnical Commission. SANS 24730-1:2008 Edition 1 ISO/IEC 24730-1:2006 Edition 1 Table of changes Change No. Date Scope National foreword This South African standard was approved by Natio
6、nal Committee SABS SC 71K, Information technology Automatic identification and data capture techniques, in accordance with procedures of the SABS Standards Division, in compliance with annex 3 of the WTO/TBT agreement. This SANS document was published in September 2008. Reference numberISO/IEC 24730
7、-1:2006(E)ISO/IEC 2006INTERNATIONAL STANDARD ISO/IEC24730-1First edition2006-02-15Information technology Real-time locating systems (RTLS) Part 1: Application program interface (API) Technologies de linformation Systmes de localisation en temps rel (RTLS) Partie 1: Interface de programmation dapplic
8、ation (API) SANS 24730-1:2008This s tandard may only be used and printed by approved subscription and freemailing clients of the SABS .ISO/IEC 24730-1:2006(E) PDF disclaimer This PDF file may contain embedded typefaces. In accordance with Adobes licensing policy, this file may be printed or viewed b
9、ut 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 Adobes licensing policy. The ISO Central Secretariat accepts no liability in this
10、 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 u
11、se 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/IEC 2006 All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means
12、, electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or ISOs 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 copyrig
13、htiso.org Web www.iso.org Published in Switzerland ii ISO/IEC 2006 All rights reservedSANS 24730-1:2008This s tandard may only be used and printed by approved subscription and freemailing clients of the SABS .ISO/IEC 24730-1:2006(E) ISO/IEC 2006 All rights reserved iiiContents Page Foreword iv Intro
14、duction v 1 Scope . 1 2 Normative references . 1 3 Terms and definitions. 2 4 Symbols and abbreviated terms . 3 5 The service 3 5.1 Purpose 3 5.2 Specification summary. 3 5.3 Security 4 6 The Application Program Interface (API) 4 6.1 Purpose 4 6.2 Language Independence 4 6.3 Architecture. 4 6.4 Nome
15、nclature and conventions 5 7 Subroutine calls 5 7.1 Overview of SOAP-RPC 5 7.2 Remote Procedure Call: Query 5 7.3 Remote Procedure Call: OpenSession. 10 7.4 Remote Procedure Call: QuerySession 12 7.5 Remote Procedure Call: CloseSession 14 8 Data structures and data types . 17 8.1 TagBlink structure
16、17 8.2 QueryResponse structure 18 8.3 SessionResponse structure 19 8.4 Fault structure. 19 Annex A (normative) XML Schema for Remote Procedure Calls 22 A.1 RTLS API Schema. 22 A.2 SOAP Request Schema: Query. 22 A.3 SOAP Request Schema: OpenSession 24 A.4 SOAP Request Schema: QuerySession .24 A.5 SOA
17、P Request Schema: CloseSession 25 A.6 SOAP Response Schema: TagBlink Type 25 A.7 SOAP Response Schema: QueryResponse. 27 A.8 SOAP Response Schema: SessionResponse . 28 A.9 SOAP Fault Schema: RTLSFaultDetail . 28 SANS 24730-1:2008This s tandard may only be used and printed by approved subscription an
18、d freemailing clients of the SABS .ISO/IEC 24730-1:2006(E) iv ISO/IEC 2006 All rights reservedForeword ISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) form the specialized system for worldwide standardization. National bodies that are
19、members of ISO or IEC participate in the development of International Standards through technical committees established by the respective organization to deal with particular fields of technical activity. ISO and IEC technical committees collaborate in fields of mutual interest. Other international
20、 organizations, governmental and non-governmental, in liaison with ISO and IEC, also take part in the work. In the field of information technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1. International Standards are drafted in accordance with the rules given in the I
21、SO/IEC Directives, Part 2. The main task of the joint technical committee is to prepare International Standards. Draft International Standards adopted by the joint technical committee are circulated to national bodies for voting. Publication as an International Standard requires approval by at least
22、 75 % of the national 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 and IEC shall not be held responsible for identifying any or all such patent rights. ISO/IEC 24730-1 was prepared by Technical Commit
23、tee ISO/TC JTC 1, Information technology, Subcommittee SC 31, Automatic identification and data capture techniques. ISO/IEC 24730 consists of the following parts, under the general title Information technology Real-time locating systems (RTLS): Part 1: Application program interface (API) Part 2: 2,4
24、 GHz air interface protocol The following part is under preparation: Part 3: 433 MHz air interface protocol SANS 24730-1:2008This s tandard may only be used and printed by approved subscription and freemailing clients of the SABS .ISO/IEC 24730-1:2006(E) ISO/IEC 2006 All rights reserved vIntroductio
25、n ISO/IEC 24730 defines two air interface protocols and a single application program interface (API) for real-time locating systems (RTLS) for use in asset management and is intended to allow for compatibility and to encourage interoperability of products for the growing RTLS market. This part of IS
26、O/IEC 24730, the RTLS application program interface, establishes a technical standard for RTLS. To be fully compliant with this standard, RTLS must comply with this part of ISO/IEC 24730 and at least one air interface protocol defined in ISO/IEC 24730. Real-time locating systems are wireless systems
27、 with the ability to locate the position of an item anywhere in a defined space (local/campus, wide area/regional, global) at a point in time that is, or is close to, real time. Position is derived by measurements of the physical properties of the radio link. Conceptually there are four classificati
28、ons of RTLS: Locating an asset via satellite (requires line-of-sight) - accuracy to 10 m. Locating an asset in a controlled area, e.g., warehouse, campus, airport (area of interest is instrumented) - accuracy to 3 m. Locating an asset in a more confined area (area of interest is instrumented) - accu
29、racy to tens of centimetres. Locating an asset over a terrestrial area using a terrestrial mounted receiver over a wide area, cell phone towers for example accuracy 200 m. There are a further two methods of locating an object which are really RFID rather than RTLS: Locating an asset by virtue of the
30、 fact that the asset has passed point A at a certain time and has not passed point B. Locating an asset by virtue of providing a homing beacon whereby a person with a handheld can find an asset. SANS 24730-1:2008This s tandard may only be used and printed by approved subscription and freemailing cli
31、ents of the SABS .ISO/IEC 24730-1:2006(E) vi ISO/IEC 2006 All rights reservedThe method of location is through identification and location, generally through multi-lateration. The different types are Time of Flight Ranging Systems, Amplitude Triangulation, Time Difference of Arrival (TDOA), Cellular
32、 Triangulation, Satellite Multi-lateration, Angle of Arrival. This part of ISO/IEC 24730 defines an API needed for utilizing an RTLS. An API is a boundary across which application software uses facilities of programming languages to invoke services. These facilities may include procedures or operati
33、ons, shared data objects and resolution of identifiers. A wide range of services may be required at an API to support applications. Different methods may be appropriate for documenting API specifications for different types of services. The information flow across the API boundary is defined by the
34、syntax and semantics of a particular programming language, such that the user of that language may access the services provided by the application platform on the other side of the boundary. This implies the specification of a mapping of the functions being made available by the application platform
35、 into the syntax and semantics of the programming language. An API specification documents a service and/or service access method that is available at an interface between the application and an application platform. This API describes the RTLS service and its access methods, to enable client applic
36、ations to interface with the RTLS. This RTLS service is the minimum service that must be provided by an RTLS to be API compatible with this standard. SANS 24730-1:2008This s tandard may only be used and printed by approved subscription and freemailing clients of the SABS .INTERNATIONAL STANDARD ISO/
37、IEC 24730-1:2006(E) ISO/IEC 2006 All rights reserved 1Information technology Real-time locating systems (RTLS) Part 1: Application program interface (API) 1 Scope This part of ISO/IEC 24730 enables software applications to utilize a real-time locating system (RTLS) infrastructure to locate assets wi
38、th RTLS transmitters attached to them. It defines a boundary across which application software uses facilities of programming languages to collect information contained in RTLS tag blinks received by the RTLS infrastructure. 2 Normative references The following referenced documents are indispensable
39、 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/IEC 19762-1, Information technology Automatic identification and data capture (AIDC) techniques H
40、armonized vocabulary Part 1: General terms relating to AIDC ISO/IEC 19762-3, Information technology Automatic identification and data capture (AIDC) techniques Harmonized vocabulary Part 3: Radio frequency identification (RFID) ISO/IEC 9075:2003 (all parts), Information technology Database languages
41、 SQL IETF RFC 2616: June 1999, Hypertext Transfer Protocol HTTP/1.1 (http:/www.ietf.org/rfc/rfc2616.txt) Extensible Markup Language (XML) 1.0, (Third Edition) W3C Recommendation, World Wide Web Consortium (W3C), 4 February 2004. (http:/www.w3.org/TR/REC-xml/) XML Schema Part 1: Structures, W3C Recom
42、mendation, World Wide Web Consortium (W3C), Cambridge Massachusetts, 2 May 2001. (http:/www.w3.org/TR/2001/REC-xmlschema-1-20010502/) XML Schema Part 2: Datatypes, W3C Recommendation, World Wide Web Consortium (W3C), Cambridge Massachusetts, 2 May 2001. (http:/www.w3.org/TR/2001/REC-xmlschema-2-2001
43、0502/) SOAP Version 1.2 Part0: Primer, W3C Recommendation, World Wide Web Consortium (W3C), 24 June 2003, (http:/www.w3.org/TR/2003/REC-soap12-part0-20030624/) SOAP Version 1.2 Part1: Messaging Framework, W3C Recommendation, World Wide Web Consortium (W3C), 24 June 2003. (http:/www.w3.org/TR/2003/RE
44、C-soap12-part1-20030624/) SOAP Version 1.2 Part2: Adjuncts, W3C Recommendation, World Wide Web Consortium (W3C), 24 June 2003. (http:/www.w3.org/TR/2003/REC-soap12-part2-20030624/) SANS 24730-1:2008This s tandard may only be used and printed by approved subscription and freemailing clients of the SA
45、BS .ISO/IEC 24730-1:2006(E) 2 ISO/IEC 2006 All rights reserved3 Terms and definitions For the purposes of this document, the terms and definitions given in ISO/IEC 19762-1, ISO/IEC 19762-3 and the following apply. 3.1 RTLS transmitters active (battery powered) radio transmitters that are attached to
46、 assets (items, people, etc.) NOTE RTLS transmitters send messages containing a unique ID for the asset, and may provide certain status information about the RTLS transmitter (e.g. battery level) and the asset (e.g. temperature). 3.2 tag blink series of transmissions communicating a single asset mov
47、ement or status change NOTE Within the API, a tag blink consists of a “TagID“ property that uniquely identifies the RTLS transmitter, as well as numerous other properties. Within the API, each property is also referred to as a field. 3.3 field element of a data record in which information is stored,
48、 which may contain one or more properties of a tag blink, and which has a unique XML tag associated with it NOTE Each tag blink property has a single, corresponding field in each TagBlink XML message. Conversely, within this API, each field may have one or more properties. 3.4 XML tag marker that qu
49、alifies content in an XML document 3.5 SOAP lightweight protocol intended for exchanging structured information in a decentralized, distributed environment NOTE See references to SOAP Version 1.2 in the bibliography for additional information. 3.6 service software program provides responses to requests from other software programs, which are frequently on other remotely connected computers 3.7 persistent connection network connection between a webserver and a client that is ke
