BS ISO 19080-2016 Intelligent transport systems Communications access for land mobiles (CALM) CoAP facility《智能运输系统 地面移动通讯用通信接入(CALM) CoAP设施》.pdf

1、BS ISO 19080:2016Intelligent transport systems Communications access forland mobiles (CALM) CoAPfacilityBSI Standards PublicationWB11885_BSI_StandardCovs_2013_AW.indd 1 15/05/2013 15:06BS ISO 19080:2016 BRITISH STANDARDNational forewordThis British Standard is the UK implementation of ISO 19080:2016

2、.The UK participation in its preparation was entrusted to TechnicalCommittee EPL/278, Intelligent transport systems.A list of organizations represented on this committee can beobtained on request to its secretary.This publication does not purport to include all the necessaryprovisions of a contract.

3、 Users are responsible for its correctapplication. The British Standards Institution 2016.Published by BSI Standards Limited 2016ISBN 978 0 580 86508 4ICS 03.220.20; 35.240.60Compliance with a British Standard cannot confer immunity fromlegal obligations.This British Standard was published under the

4、 authority of theStandards Policy and Strategy Committee on 31 October 2016.Amendments/corrigenda issued since publicationDate Text affectedBS ISO 19080:2016 ISO 2016Intelligent transport systems Communications access for land mobiles (CALM) CoAP facilitySystmes intelligents de transport Accs aux co

5、mmunications des services mobiles terrestres (CALM) quipements CoAPINTERNATIONAL STANDARDISO19080First edition2016-10-01Reference numberISO 19080:2016(E)BS ISO 19080:2016ISO 19080:2016(E)ii ISO 2016 All rights reservedCOPYRIGHT PROTECTED DOCUMENT ISO 2016, Published in SwitzerlandAll rights reserved

6、. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without prior written permission. Permission can be requested from either ISO at

7、 the address below or ISOs member body in the country of the requester.ISO copyright officeCh. de Blandonnet 8 CP 401CH-1214 Vernier, Geneva, SwitzerlandTel. +41 22 749 01 11Fax +41 22 749 09 47copyrightiso.orgwww.iso.orgBS ISO 19080:2016ISO 19080:2016(E)Foreword ivIntroduction v1 Scope . 12 Normati

8、ve references 13 Terms and definitions . 14 Symbols and abbreviated terms . 35 Requirements 35.1 Categories 35.2 ITS-S nodes implementing CoAP . 45.2.1 General 45.2.2 Requirements on all ITS-S CoAP nodes 65.3 CoAP functional modules . 75.3.1 General 75.3.2 CoAP management module. 85.3.3 CoAP securit

9、y module 115.4 Optional module . 125.4.1 General. 125.4.2 CoAP/HTTP interoperability 135.4.3 Resource directory 155.4.4 Blockwise transfers 165.5 Modules implemented in ITS-S CoAP nodes .175.5.1 General. 175.5.2 ITS-S CoAP full function device modules .175.5.3 ITS-S CoAP reduced function device modu

10、les .17Bibliography .18 ISO 2016 All rights reserved iiiContents PageBS ISO 19080:2016ISO 19080:2016(E)ForewordISO (the International Organization for Standardization) is a worldwide federation of national standards bodies (ISO member bodies). The work of preparing International Standards is normall

11、y 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

12、work. ISO collaborates closely with the International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization.The procedures used to develop this document and those intended for its further maintenance are described in the ISO/IEC Directives, Part 1. In particular the di

13、fferent approval criteria needed for the different types of ISO documents should be noted. This document was drafted in accordance with the editorial rules of the ISO/IEC Directives, Part 2 (see www.iso.org/directives).Attention is drawn to the possibility that some of the elements of this document

14、may be the subject of patent rights. ISO shall not be held responsible for identifying any or all such patent rights. Details of any patent rights identified during the development of the document will be in the Introduction and/or on the ISO list of patent declarations received (see www.iso.org/pat

15、ents).Any trade name used in this document is information given for the convenience of users and does not constitute an endorsement.For an explanation on the meaning of ISO specific terms and expressions related to conformity assessment, as well as information about ISOs adherence to the World Trade

16、 Organization (WTO) principles in the Technical Barriers to Trade (TBT) see the following URL: www.iso.org/iso/foreword.html.The committee responsible for this document is ISO/TC 204, Intelligent transport systems.iv ISO 2016 All rights reservedBS ISO 19080:2016ISO 19080:2016(E)IntroductionThe set o

17、f International Standards that collectively refer to communications access for land mobile (CALM) focus on the specification of open interfaces regarding the functionality required by all relevant layers and entities of a Standard ITS station reference architecture.These International Standards are

18、designed to allow interoperable instantiations of ITS stations, which are based on the concept of abstracting applications and services from the underlying communication layers. This abstraction makes the ITS station architecture described herein ideally suited to the development and deployment of C

19、ooperative ITS applications and services.The set of CALM International Standards include specifications for security in ITS communications, ITS-S management, distributed ITS-S implementations, legacy communication media interfaces, legacy application interfaces and new communication interfaces speci

20、fically designed for ITS applications, such as those designed for safety of both life and property.The fundamental advantage of the CALM concept with respect to traditional systems is the ability to support vertical handovers between the various media that can be included in a CALM system. Handover

21、mechanisms are defined within the CALM architecture International Standard (ISO 21217), the CALM medium service access points International Standard (ISO 21218) and the CALM communication and station management International Standard (ISO 24102).At network layer, CALM IPv6 networking ISO 21210 and C

22、ALM 6LoWPAN networking ISO 19079 determine the network protocols to support reachability at a global IPv6 address for Wireless Sensor Networks (WSNs) based on the IEEE 802.15.4 access medium.CALM compliant networks (both in-vehicle and off-vehicle) are expected to interact with each other to seamles

23、sly exchange information. This should be true also for information retrieved from WSN to be dispatched to any ITS-Station. As WSNs are largely based on low-cost Component of The Shelf (COTS), IETF has started the standardization of a set of protocols at network and facility layer suited for constrai

24、ned devices (in terms of capability of processing, storage or communication) based on low-rate wireless personal area networks (LR-WPANs) technologies. An important candidate at application layer in this sense is the IETF Constrained Application Protocol (CoAP) (IETF RFC 7252), an optimized Represen

25、tational State Transfer (REST) protocol built on top of the UDP transport protocol, and implementing a subset of HTTP specifications. This document specifies some facility protocols by leveraging the reachability of the WSN nodes guaranteed by the adoption of 6LoWPAN at the Network Layer, and descri

26、bes how to use CoAP protocol specified by IETF in the context of C-ITS.For a general introduction to CALM architecture, IPv6 networking and 6LoWPAN networking, the reader is referred to ISO 21217, ISO 21210 and ISO 19079, respectively. ISO 2016 All rights reserved vBS ISO 19080:2016BS ISO 19080:2016

27、Intelligent transport systems Communications access for land mobiles (CALM) CoAP facility1 ScopeThis document describes the CoAP facilities between two or more ITS stations communicating over the global internet communication network.It is assumed that the reader is familiar with IETF specifications

28、 found in request for comments (RFCs) of individual CoAP and 6LoWPAN protocol blocks used within this document. This document does not define a new protocol, a new exchange of messages at the CoAP layer, or new data structures. It defines how protocols standardized by IETF are combined so that ITS s

29、tations can communicate with one another using CoAP. Procedures defined to share information between the CoAP layer and other components of the ITS station architecture are defined in ISO 24102 series (Management). In addition to the requirements specified within this document, a number of notes and

30、 examples are provided to illustrate CoAP main facilities.2 Normative referencesThe following documents are referred to in the text in such a way that some or all of their content constitutes requirements of this document. For dated references, only the edition cited applies. For undated references,

31、 the latest edition of the referenced document (including any amendments) applies.ISO 21217:2014, Intelligent transport systems Communications access for land mobiles (CALM) ArchitectureISO 24102-61), Intelligent transport systems Communications access for land mobiles (CALM) ITS station management

32、Part 6: Path and flow managementIETF RFC 6690, The Constrained RESTful Environments (CoRE) Link FormatIETF RFC 7252:2014, The Constrained Application Protocol (CoAP)IETF RFC 7641, Observing Resources in the Constrained Application Protocol (CoAP)3 Terms and definitionsFor the purposes of this docume

33、nt, the terms and definitions given in ISO 19079, ISO 21210, ISO 21217, ISO 21218, ISO 24102-3 and the following apply.ISO and IEC maintain terminological databases for use in standardization at the following addresses: IEC Electropedia: available at http:/www.electropedia.org/ ISO Online browsing p

34、latform: available at http:/www.iso.org/obpNOTE Most of the definitions are taken from IETF RFC 7252, IETF RFC 7228 and IETF RFC 6690.3.1ITS-S CoAP nodedevice/node that implements CoAP protocolSOURCE: IETF RFC 72521) To be published.INTERNATIONAL STANDARD ISO 19080:2016(E) ISO 2016 All rights reserv

35、ed 1BS ISO 19080:2016ISO 19080:2016(E)3.2ITS-S CoAP Endpointentity participating in the CoAP protocolNote 1 to entry: Colloquially, an endpoint lives on a “node”, although “host” would be more consistent with Internet standards usage, and is further identified by transport-layer multiplexing informa

36、tion that can include a UDP port number and a security association.SOURCE: IETF RFC 72523.3ITS-S CoAP Clientoriginating endpoint of a request; the destination endpoint of a responseSOURCE: IETF RFC 72523.4ITS-S Serverdestination endpoint of a request; the originating endpoint of a responseSOURCE: IE

37、TF RFC 72523.5confirmable messagemessage requiring an acknowledgementNote 1 to entry: These messages are called “confirmable”. When no packets are lost, each confirmable message prompts exactly one return message of type acknowledgement or type reset.SOURCE: IETF RFC 72523.6non-confirmable messageme

38、ssage not requiring an acknowledgementNote 1 to entry: This is particularly true for messages that are repeated regularly for application requirements, such as repeated readings from a sensor.SOURCE: IETF RFC 72523.7acknowledgement messagemessage acknowledging that a specific confirmable message arr

39、ivedNote 1 to entry: By itself, an acknowledgement message does not indicate success or failure of any request encapsulated in the confirmable message.SOURCE: IETF RFC 72523.8reset messagemessage indicating that a specific message (confirmable or non-confirmable) was received, but some context is mi

40、ssing to properly process itNote 1 to entry: This condition is usually caused when the receiving node has rebooted and has forgotten some state that would be required to interpret the message. Provoking a reset message (e.g. by sending an empty confirmable message) is also useful as an inexpensive c

41、heck of the aliveness of an endpoint (“CoAP ping”).SOURCE: IETF RFC 72522 ISO 2016 All rights reservedBS ISO 19080:2016ISO 19080:2016(E)3.9subjectresource in the namespace of an ITS-S CoAP serverNote 1 to entry: The state of the resource can change over time, ranging from infrequent updates to conti

42、nuous state transformations.SOURCE: IETF RFC 76413.10observerITS-S CoAP client that is interested in having a current representation of the resource at any given timeSOURCE: IETF RFC 76414 Symbols and abbreviated termsFor the purposes of this document, symbols and abbreviated terms in ISO 21210, ISO

43、 21217, IETF RFC 4944, IETF RFC 6282 apply.5 Requirements5.1 CategoriesClause 5 explains the relationship between the four categories of the requirements. The first category (see 5.2) contains requirements applying to all ITS-S CoAP nodes and it specifies requirements that are applicable to the diff

44、erent types of CoAP nodes in each ITS sub-system. The second category (see 5.3) contains the requirements that define the CoAP functional modules that are mandatory for the implementation of “ITS-S CoAP nodes”. Two different modules are detailed. The third category (see 5.4) contains optional featur

45、es and functions specified as one of the functional modules of the CoAP protocol block. These optional features could be combined to realize a set of ITS-S architecture depending on the specific application. The fourth category (see 5.5) contain requirements defining which of the CoAP functional mod

46、ules specified in 5.3 and 5.4 are combined for each particular “ITS-S CoAP node” specified in 5.3. ISO 2016 All rights reserved 3BS ISO 19080:2016ISO 19080:2016(E)Figure 1 Scope of this document within the architecture of an ITS-S5.2 ITS-S nodes implementing CoAP5.2.1 GeneralAs CoAP was designed acc

47、ording to the REST architecture, it thus exhibits functionality similar to that of the HTTP protocol, it will support web style transactions originated or directed to 6LoWPAN nodes in ITS stations (ISO 19079).4 ISO 2016 All rights reservedBS ISO 19080:2016ISO 19080:2016(E)For a better understanding

48、of CoAP, the terminologies are specified in IETF RFC 7252 and the “Terminologies behind constrained-node networks” in IETF RFC 7228. These documents shall serve as the normative references for how to apply “CoAP” to ITS CALM.Figure 2 CoAP based subsystemA station implementing CoAP (in a PAN) is pict

49、orially represented in Figure 2 together with its connections with other CoAP nodes in the same 6LoWPAN (IETF RFC 4919, IETF RFC 4944, IETF RFC 6282), eventually exploiting the multi-hop forwarding module featured by ad-hoc routers. The forwarding service established with peers of the Internet is also shown leveraging the functionality provided by a “6LoWPAN Border Router” equipped with at least two MAC interfaces.The CoAP-based ITS stations can notably take part in the “road-side” and “vehicular”