Re: [ipwave] Protocols and Architectures for Traffic Light Controllers
Alexandre Petrescu <alexandre.petrescu@gmail.com> Thu, 06 June 2019 17:26 UTC
Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: its@ietfa.amsl.com
Delivered-To: its@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4FF4F1200B2 for <its@ietfa.amsl.com>; Thu, 6 Jun 2019 10:26:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.65
X-Spam-Level:
X-Spam-Status: No, score=-1.65 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HTML_FONT_FACE_BAD=0.981, HTML_MESSAGE=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HNZiP8_N_C7o for <its@ietfa.amsl.com>; Thu, 6 Jun 2019 10:26:45 -0700 (PDT)
Received: from cirse-smtp-out.extra.cea.fr (cirse-smtp-out.extra.cea.fr [132.167.192.148]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 27650120092 for <its@ietf.org>; Thu, 6 Jun 2019 10:26:44 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id x56HQhK6006339 for <its@ietf.org>; Thu, 6 Jun 2019 19:26:43 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 511092065ED for <its@ietf.org>; Thu, 6 Jun 2019 19:26:43 +0200 (CEST)
Received: from muguet1-smtp-out.intra.cea.fr (muguet1-smtp-out.intra.cea.fr [132.166.192.12]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 442BE206594 for <its@ietf.org>; Thu, 6 Jun 2019 19:26:43 +0200 (CEST)
Received: from [10.8.68.52] ([10.8.68.52]) by muguet1-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id x56HQg8G014337 for <its@ietf.org>; Thu, 6 Jun 2019 19:26:42 +0200
To: its@ietf.org
References: <61452b20-9cd1-c9ce-1eb2-ebb090efb8c4@gmail.com> <936d2cd6-5381-8387-cd2d-e8b33cb5dd7a@gmail.com> <a29b8c71-a707-7da0-f4a5-0f16796d8803@gmail.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <837d0035-9afa-dc24-f527-55b92f1a9ce2@gmail.com>
Date: Thu, 06 Jun 2019 19:26:42 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.7.0
MIME-Version: 1.0
In-Reply-To: <a29b8c71-a707-7da0-f4a5-0f16796d8803@gmail.com>
Content-Type: multipart/alternative; boundary="------------9E76F7760E92C1B32B8F1F82"
Content-Language: fr
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/TT48sZZhQW5O0Z1eakEenGw3ux8>
Subject: Re: [ipwave] Protocols and Architectures for Traffic Light Controllers
X-BeenThere: its@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IPWAVE - IP Wireless Access in Vehicular Environments WG at IETF <its.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/its>, <mailto:its-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/its/>
List-Post: <mailto:its@ietf.org>
List-Help: <mailto:its-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/its>, <mailto:its-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Jun 2019 17:26:47 -0000
Sorry, I forgot, we already discussed. I am in told in private that: In the US the protocol to communicate with Traffic Lights Controllers is NTCIP. It is on the web at https://www.ntcip.org/document-numbers-and-status/ It has Internet specifically (it has profile for it, dated 2001). I dont see IPv6 mentioned though. Not only a car would need to implement IVERA, DIASER, NTCIP and OCIT to talk to Traffic Lights Controllers, but it would not need IPv6 at all. Because none runs on IPv6. I disagree with this lack of IPv6 support in these protocols. Le 06/06/2019 à 17:18, Alexandre Petrescu a écrit : > > For further completeness... > > The Dutch version of protocols for Traffic Lights Controllers, in > addition to IVERA also include iVRI, on the web at > https://www.crow.nl/thema-s/verkeersmanagement/landelijke-ivri-standaarden > > The German OCIT protocol is on the web at www.ocit.org > > I continue to wonder what is the protocol used for communicating with > Traffic Lights Controllers in Italy, and in America? > > Alex > > Le 06/06/2019 à 05:13, Alexandre Petrescu a écrit : >> >> For completeness, >> >> >> The complete list of protocols to communication to Traffic Lights >> Controllers is: DIASER, IVERA, OCIT. >> >> Because I learn in Germany and the Czech Republic, the OCIT protocol >> (not DIASER) may be used for communication to Traffic Lights >> Controller, with some implementations from Siemens and from Cross. >> Not known whether OCIT works on IP, and on IPv6. >> >> DIASER is known to work on RS232, TCP and UDP. Seen on IPv4; not >> known on IPv6. SEA is a traffic lights controller manufacturer in >> France that produces some, implements DIASER too. There are about 10 >> manufacturers in France (Aximum of Colas, Fareco of Fayat, Lacroix, >> SEA, others?), all doing DIASER. >> >> Basically, if one wants a car to talk to traffic lights controllers >> with low latenccy, one wants to put 3 protocols in that car. >> >> >> Le 29/01/2019 à 15:04, Alexandre Petrescu a écrit : >>> >>> Protocols and Architectures for Traffic Lights >>> Januay 29th, 2019 >>> >>> >>> DIASER: a protocol used to communicate to Traffic Lights controllers. >>> Used in France. Specified by AFNOR. Closed and paying specification. >>> Works on hardware platforms from Lacroix (model Traffy) and Aximum >>> (model Maestro), and probably others. Works on serial and on UDP/IP. >>> Example queries are: "DZ" to reset, "Ck" and "CJ" to query the current >>> color of lights, C# and CU to get the time spent in a color. >>> >>> API WIM 7101, RSGC2: proprietary API interfaces used by organisation >>> NEAVIA of organisation Lacroix in France; it is used to provide access >>> to data of traffic lights controllers. It can be used with DIASER in >>> a sequence way: a gateway converts from one to another. >>> >>> ISO PRESTO 22951: a protocol to communicate with traffic lights >>> controller, to obtain priority for special vehicles. >>> >>> SPAT/SSM/SRM: protocols used by future traffic lights controllers; >>> specified by SAE in J2735. The 2009 version is freely available, >>> whereas the 2016 (non retro-compatible) is paying 100 USD, >>> approximative. SPAT is Signal Phase and Timing, whereas SRM is Signal >>> Request Message. >>> >>> SPAT-EM: an European version of SPAT, specified by ETSI, which >>> encapsulates SPAT. Free access, but SPAT still paying (free >>> encapsulated paying). >>> >>> IVERA: a protocol used in Netherlands to communicate with Traffic >>> Lights controllers. Potentially VLOG is also such a protocol. >>> >>> 3G Segnaletica: an organisation in Italy that provides hardware for >>> controllers for traffic lights. Also has models carried in 'mobile' >>> traffic lights. It provides a Raspberry Pi to access the traffic >>> lights data. The Raspberry Pi uses an API to access the controller >>> status. That API uses HTTP. >>> >>> Siemens: is an organisation that probably provides hardware for >>> traffic lights controllers to be used in America (USA). >>> >>> Architectures: sketches drawing controller, tri-light bulbs, Internet, >>> 802.11-OCB, car, API, SPAT. >>> >>> Acknowledgements: Daniele Brevi, Bart Netten, Stephane Goeuriot, Sri >>> Gundavelli, Bruno Cabon, Paul Thorpe. >>> >>> >>> _______________________________________________ >>> its mailing list >>> its@ietf.org >>> https://www.ietf.org/mailman/listinfo/its >> >> _______________________________________________ >> its mailing list >> its@ietf.org >> https://www.ietf.org/mailman/listinfo/its
- [ipwave] Protocols and Architectures for Traffic … Alexandre Petrescu
- Re: [ipwave] Protocols and Architectures for Traf… Alexandre Petrescu
- Re: [ipwave] Protocols and Architectures for Traf… Alexandre Petrescu
- Re: [ipwave] Protocols and Architectures for Traf… Alexandre Petrescu
- Re: [ipwave] Protocols and Architectures for Traf… Alexandre PETRESCU
- Re: [ipwave] Protocols and Architectures for Traf… Alexandre Petrescu
- Re: [ipwave] Protocols and Architectures for Traf… Alexandre Petrescu
- Re: [ipwave] Protocols and Architectures for Traf… Alexandre Petrescu