Proposal to Share Draft Sections with IEEE 1722 by NAV Alliance
Explore how NAV Alliance TWG4 requests to share draft sections with IEEE 1722 to align sensor data formats for Automotive applications efficiently. Access to IEEE 1722b draft document is crucial for developing profiles and proposing new message types to IEEE 1722 WG.
Download Presentation
Please find below an Image/Link to download the presentation.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.
You are allowed to download the files provided on this website for personal or commercial use, subject to the condition that they are used lawfully. All files are the property of their respective owners.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.
E N D
Presentation Transcript
NAV Alliance Request to IEEE 1722 to Share Draft sections Hari Parmar Chair of NAV Alliance TWG4
Motivation: The NAV Alliance working group was tasked to efficiently develop data format/encapsulation over Ethernet for sensors such as Camera, RADAR, LIDAR, Ultrasonics, etc. The use cases for these sensors are primarily for Autonomous driving platforms. The background of the personnel participating in this working group are from the Automotive sector. These include Tier 1s (e.g., Bosch, Continental, Sony, Nvidia) and Marvell currently represented as a Tier 2, semiconductor vendor. The motivation of the members of TWG4 working group is to map these sensor formats into existing IEEE 1722 messages or if that is not possible to propose new message types to the IEEE 1722 WG.
Automotive Use Case As a group we have developed a good level of maturity in terms of understanding use cases and sensor data formats that are needed for Automotive applications. These data would be required to be formatted and transported for Sensor data pertinent to the Automotive sector. TWG4 can only take these concepts developed within the group to a certain level of maturity outside of IEEE 1722. TWG4 s aims have always been to develop these concepts as fast as possible, so that it allows the industry to offer solutions that are based on IEEE 1722.
Access to IEEE 1722b draft document In order to align our work as close as possible to the IEEE 1722 framework, it would be beneficial if we could review the current IEEE 1722b draft specification within NAV Alliance TWG4. As we understand, an appropriate measure to do so, would be the establishment of a draft sharing relation , according to the regulations of the IEEE SA. Therefore we would like you, as the IEEE 1722 Working Group, to decide if you want to follow our request, and if so initiate the IEEE internal process necessary to establish a draft sharing relationship with NAV TWG4. By sharing the draft this would allow NAV TWG4 to work in parallel with IEEE 1722 WG.
Access to IEEE 1722b draft document (Cont) The goals of NAV TWG4 are: To develop profiles for Automotive sensor applications. For sensor that do not map efficiently into existing IEEE 1722 formats, the group would develop formats that will be proposed for 1722c. The work group understands that the proposals to IEEE 1722 work groups can only be made up of the committee work group. We feel it is the right time now to that we have put together within TWG4 and put these concepts forward to IEEE 1722. Our suggestion is that this will be done by individuals who are also members of IEEE 1722 and which would present as individuals (and not under the NAV Alliance banner), as we do for all proposals and presentations in IEEE. The main portion of the IEEE 1722 standard that will be affected would be clause 9 and clause 18. I look forward to your thoughts on the suggested ideas above.
