Links to Exploration step
Le document en format XML
<record><TEI><teiHeader><fileDesc><titleStmt><title xml:lang="en">Smart Roadside System for Driver Assistance and Safety Warnings: Framework and Applications</title><author><name sortKey="Jang, Jeong Ah" sort="Jang, Jeong Ah" uniqKey="Jang J" first="Jeong Ah" last="Jang">Jeong Ah Jang</name></author><author><name sortKey="Kim, Hyun Suk" sort="Kim, Hyun Suk" uniqKey="Kim H" first="Hyun Suk" last="Kim">Hyun Suk Kim</name></author><author><name sortKey="Cho, Han Byeog" sort="Cho, Han Byeog" uniqKey="Cho H" first="Han Byeog" last="Cho">Han Byeog Cho</name></author></titleStmt><publicationStmt><idno type="wicri:source">PMC</idno><idno type="pmid">22164025</idno><idno type="pmc">3231714</idno><idno type="url">http://www.ncbi.nlm.nih.gov/pmc/articles/PMC3231714</idno><idno type="RBID">PMC:3231714</idno><idno type="doi">10.3390/s110807420</idno><date when="2011">2011</date><idno type="wicri:Area/Pmc/Corpus">000590</idno><idno type="wicri:explorRef" wicri:stream="Pmc" wicri:step="Corpus" wicri:corpus="PMC">000590</idno></publicationStmt><sourceDesc><biblStruct><analytic><title xml:lang="en" level="a" type="main">Smart Roadside System for Driver Assistance and Safety Warnings: Framework and Applications</title><author><name sortKey="Jang, Jeong Ah" sort="Jang, Jeong Ah" uniqKey="Jang J" first="Jeong Ah" last="Jang">Jeong Ah Jang</name></author><author><name sortKey="Kim, Hyun Suk" sort="Kim, Hyun Suk" uniqKey="Kim H" first="Hyun Suk" last="Kim">Hyun Suk Kim</name></author><author><name sortKey="Cho, Han Byeog" sort="Cho, Han Byeog" uniqKey="Cho H" first="Han Byeog" last="Cho">Han Byeog Cho</name></author></analytic><series><title level="j">Sensors (Basel, Switzerland)</title><idno type="eISSN">1424-8220</idno><imprint><date when="2011">2011</date></imprint></series></biblStruct></sourceDesc></fileDesc><profileDesc><textClass></textClass></profileDesc></teiHeader><front><div type="abstract" xml:lang="en"><p>The use of newly emerging sensor technologies in traditional roadway systems can provide real-time traffic services to drivers through Telematics and Intelligent Transport Systems (ITSs). This paper introduces a smart roadside system that utilizes various sensors for driver assistance and traffic safety warnings. This paper shows two road application models for a smart roadside system and sensors: a red-light violation warning system for signalized intersections, and a speed advisory system for highways. Evaluation results for the two services are then shown using a micro-simulation method. In the given real-time applications for drivers, the framework and certain algorithms produce a very efficient solution with respect to the roadway type features and sensor type use.</p></div></front><back><div1 type="bibliography"><listBibl><biblStruct></biblStruct><biblStruct></biblStruct><biblStruct></biblStruct><biblStruct><analytic><author><name sortKey="Hirst, S" uniqKey="Hirst S">S Hirst</name></author><author><name sortKey="Graham, R" uniqKey="Graham R">R Graham</name></author></analytic></biblStruct><biblStruct><analytic><author><name sortKey="Klein, La" uniqKey="Klein L">LA Klein</name></author><author><name sortKey="Mills, Mk" uniqKey="Mills M">MK Mills</name></author><author><name sortKey="Gibson, Drp" uniqKey="Gibson D">DRP Gibson</name></author></analytic></biblStruct><biblStruct><analytic><author><name sortKey="Kim, J" uniqKey="Kim J">J Kim</name></author><author><name sortKey="Kwon, Oc" uniqKey="Kwon O">OC Kwon</name></author><author><name sortKey="Kim, H" uniqKey="Kim H">H Kim</name></author></analytic></biblStruct><biblStruct><analytic><author><name sortKey="Pant, P" uniqKey="Pant P">P Pant</name></author><author><name sortKey="Xie, Y" uniqKey="Xie Y">Y Xie</name></author></analytic></biblStruct><biblStruct><analytic><author><name sortKey="Sunkari, S" uniqKey="Sunkari S">S Sunkari</name></author><author><name sortKey="Messer, C" uniqKey="Messer C">C Messer</name></author><author><name sortKey="Charara, H" uniqKey="Charara H">H Charara</name></author></analytic></biblStruct><biblStruct><analytic><author><name sortKey="Carson, J" uniqKey="Carson J">J Carson</name></author><author><name sortKey="Mannering, F" uniqKey="Mannering F">F Mannering</name></author></analytic></biblStruct><biblStruct><analytic><author><name sortKey="Elvik, R" uniqKey="Elvik R">R Elvik</name></author><author><name sortKey="Christensen, P" uniqKey="Christensen P">P Christensen</name></author><author><name sortKey="Amundsen, A" uniqKey="Amundsen A">A Amundsen</name></author></analytic></biblStruct><biblStruct><analytic><author><name sortKey="Jang, J" uniqKey="Jang J">J Jang</name></author><author><name sortKey="Kim, H" uniqKey="Kim H">H Kim</name></author></analytic></biblStruct><biblStruct><analytic><author><name sortKey="Jang, J" uniqKey="Jang J">J Jang</name></author><author><name sortKey="Choi, K" uniqKey="Choi K">K Choi</name></author><author><name sortKey="Moon, Yj" uniqKey="Moon Y">YJ Moon</name></author></analytic></biblStruct><biblStruct></biblStruct><biblStruct><analytic><author><name sortKey="Jang, J" uniqKey="Jang J">J Jang</name></author><author><name sortKey="Kim, H" uniqKey="Kim H">H Kim</name></author><author><name sortKey="Cho, Hb" uniqKey="Cho H">HB Cho</name></author></analytic></biblStruct></listBibl></div1></back></TEI><pmc article-type="research-article"><pmc-dir>properties open_access</pmc-dir>
<front><journal-meta><journal-id journal-id-type="nlm-ta">Sensors (Basel)</journal-id><journal-title-group><journal-title>Sensors (Basel, Switzerland)</journal-title></journal-title-group><issn pub-type="epub">1424-8220</issn><publisher><publisher-name>Molecular Diversity Preservation International (MDPI)</publisher-name></publisher></journal-meta><article-meta><article-id pub-id-type="pmid">22164025</article-id><article-id pub-id-type="pmc">3231714</article-id><article-id pub-id-type="doi">10.3390/s110807420</article-id><article-id pub-id-type="publisher-id">sensors-11-07420</article-id><article-categories><subj-group subj-group-type="heading"><subject>Article</subject></subj-group></article-categories><title-group><article-title>Smart Roadside System for Driver Assistance and Safety Warnings: Framework and Applications</article-title></title-group><contrib-group><contrib contrib-type="author"><name><surname>Jang</surname><given-names>Jeong Ah</given-names></name><xref ref-type="corresp" rid="c1-sensors-11-07420">*</xref></contrib><contrib contrib-type="author"><name><surname>Kim</surname><given-names>Hyun Suk</given-names></name></contrib><contrib contrib-type="author"><name><surname>Cho</surname><given-names>Han Byeog</given-names></name></contrib><aff id="af1-sensors-11-07420">Vehicle-Ship IT Convergence Research Department, ETRI (Electronics and Telecommunications Research Institute), 161 Gajeong-dong, Yuseong-gu, Daejeon 305-350, Korea; E-Mails:<email>hyskim@etri.re.kr</email> (H.S.K.);<email>hbcho@etri.re.kr</email> (H.B.C.)</aff></contrib-group><author-notes><corresp id="c1-sensors-11-07420"><label>*</label>Author to whom correspondence should be addressed; E-Mail: <email>azang@etri.re.kr</email>; Tel.: +82-42-860-5636; Fax: +82-42-860-1085.</corresp></author-notes><pub-date pub-type="collection"><year>2011</year></pub-date><pub-date pub-type="epub"><day>25</day><month>7</month><year>2011</year></pub-date><volume>11</volume><issue>8</issue><fpage>7420</fpage><lpage>7436</lpage><history><date date-type="received"><day>22</day><month>6</month><year>2011</year></date><date date-type="rev-recd"><day>15</day><month>7</month><year>2011</year></date><date date-type="accepted"><day>18</day><month>7</month><year>2011</year></date></history><permissions><copyright-statement>© 2011 by the authors; licensee MDPI, Basel, Switzerland.</copyright-statement><copyright-year>2011</copyright-year><license><license-p><pmc-comment>CREATIVE COMMONS</pmc-comment>This article is an open access article distributed under the terms and conditions of the Creative Commons Attribution license (<ext-link ext-link-type="uri" xlink:href="http://creativecommons.org/licenses/by/3.0/">http://creativecommons.org/licenses/by/3.0/</ext-link>).</license-p></license></permissions><abstract><p>The use of newly emerging sensor technologies in traditional roadway systems can provide real-time traffic services to drivers through Telematics and Intelligent Transport Systems (ITSs). This paper introduces a smart roadside system that utilizes various sensors for driver assistance and traffic safety warnings. This paper shows two road application models for a smart roadside system and sensors: a red-light violation warning system for signalized intersections, and a speed advisory system for highways. Evaluation results for the two services are then shown using a micro-simulation method. In the given real-time applications for drivers, the framework and certain algorithms produce a very efficient solution with respect to the roadway type features and sensor type use.</p></abstract><kwd-group><kwd>ITS (Intelligent Traffic Systems)</kwd><kwd>smart roadside server</kwd><kwd>infrastructure-based sensor</kwd><kwd>vehicle sensor</kwd></kwd-group></article-meta></front><body><sec><label>1.</label><title>Introduction</title><p>Telematics are defined as in-vehicle systems that offer active safety and infotainment services as well as location and traffic information via wireless communication technologies. In many countries, a variety of in-vehicle Telematics systems and Intelligent Transport Systems (ITS) are already available, while new systems are being currently designed.</p><p>According to plans from the U.S. Department of Transportation, the so-called ITS Strategic Research Plan (2010–2014), IntelliDrive projects dealing with ICT and transportation convergence technologies, including vehicle-to-vehicle (V2V) interaction and vehicle-to-infrastructure (V2I) interaction, are concurrently underway. One of the important items of the ITS Strategic Research Plan is making an intelligent roadside system under a Smart Roadside project, which began in 2008. The vision of a Smart Roadside is a system in which commercial vehicles, motor carriers, enforcement resources, highway facilities, intermodal facilities, toll facilities, and other transportation system nodes collect data for their own purposes. The nodes can then share the data seamlessly with relevant parties in order to improve motor carrier safety, security, operational efficiency, and freight mobility. In Europe, Cooperative Vehicle-Infrastructure Systems (CVIS) projects have been underway since 2006, and are supported by a grant from the European Commission. A precondition of the CVIS projects is that users of cooperative systems be made aware of these systems and understand how they can help drivers operate more safely, economically, and comfortably. Operators should also run their roadway networks in more cost- and eco-effective ways. Here, “cooperative” indicates systems that cooperate on two levels: (1) direct communication and the exchange of valuable information between entities; and (2) dynamic interaction amongst roadway users and transport infrastructure, which can provide win-win benefits for both drivers and roadway operators. The main elements of a high-level CVIS system are the vehicle, roadside system, and central system. In particular, a road side system includes standardized access, secure communication between vehicles and infrastructure, authentication, authorization, updates, and software configuration. Driven by the Korean government, the SMART highway R&D project was recently launched in 2008, and is expected to be completed by 2015. A SMART highway is a future high-speed roadway that supports an intelligent and convenient driving environment by providing roadway, vehicle, environmental, and human information, enabling users to concentrate solely on their driving and helping reduce accident rates. The SMART highway system uses a local server as a smart roadside server. This local server has some important functions. Through the IntelliDrive, CVIS, and SMART highway projects, researches regarding infrastructure-based sensors and OBD II-based vehicle sensors for safe driving have been ongoing. These infrastructure, in-vehicle, and smart roadside server sensors can enhance driver capability and perception.</p><p>In this research, we deal with Telematics/ITS service based on new IT technologies using a smart roadside server on a smart road, and we focus in particular on the system architecture and components, including service processing algorithm and issues. We focus particularly on two road safety situations: signalized intersections and the highway system. The problems relating to distributed roadside servers are more complicated than in internal distributed servers due to the complexity of a road environment. Bad weather such as snow, rain, and fog, and unstable traffic elements such as traffic jams, traffic accidents, pedestrians, and bicycles, can be considered at smart roadside servers. Other issues of consideration involve wireless communications and positioning systems, such as stable communication distance in Dedicated Short Range Communication (DSRC) devices, and Global Positioning System (GPS) errors.</p><p>The remainder of this paper is organized as follows: Section 2 introduces sensor technologies such as vehicle sensors, infrastructure sensors, and smart roadside server frameworks. In Sections 3 and 4, we suggest a system model for a roadside server, along with a processing algorithm, evaluation results based on simulation tools, and methods for driver assistance/safety alarms. Finally, in Section 5, we offer some concluding remarks regarding the research described in this paper, and provide some perspectives on future work.</p></sec><sec><label>2.</label><title>Infrastructure Based Sensor and OBDII Based Vehicle Sensor</title><sec><label>2.1.</label><title>Road System and ITS Technology</title><p>The goals of ITS strategies are reducing travel time, easing delays and congestion, improving safety, and reducing pollutant emissions without the need for new roadway construction. ITS strategies that contain electronic surveillance, communications, and traffic analysis and control technologies bring about benefits to transportation system users and managers. ITS sensors often serve as data-gathering elements of an ITS, and therefore dictate ITS operating characteristics, types of data provided, and installation requirements. In particular, ITS and Telematics departments have gradually increased their interest in vehicle data through access to industry-standardized in-vehicle interfaces. This attempt to gather vehicular information and access can be determined differently depending on the type of roadway and collecting sensors used in the service. As shown in <xref ref-type="fig" rid="f1-sensors-11-07420">Figure 1</xref>, roadway types are classified into two categories of flow: uninterrupted and interrupted. Uninterrupted flow facilities have no fixed elements, such as traffic signals, that are external to the traffic stream and may interrupt the traffic flow. Traffic flow conditions result from interactions among vehicles in a traffic stream, and between vehicles and the geometric and environmental characteristics of the roadway. Interrupted flow facilities have fixed elements, such as traffic signals, stop and yield signs, and other types of controls, which may interrupt traffic flow. To capture vehicle movement in real-time, a road sensor is required at each type of facility. There are two popular categories of sensors: infrastructure-based sensors and OBDII-based vehicle sensors. Infrastructure-based sensors include pressure detectors, inductive loop detectors, magnetic detectors, ultrasonic detectors, microwave detectors, infrared detectors, and image detectors. These types of sensors utilize a part of the signal control and traffic operation in an ITS. In contrast, vehicle sensors include GPS, automatic vehicle identification (AVI) using radio frequency identification (RFID) tags, and on-board diagnostics II (OBD)-based vehicle sensors, which are connected to an in-vehicle network.</p></sec><sec><label>2.2.</label><title>Infrastructure-Based Sensor</title><p>In general, infrastructure-based sensors have certain strengths and weaknesses depending on their features, operation, and installation types. However, due to their cost-effectiveness in installation and operation, recent trends in other IT technologies include special traffic sensors for traffic detection. For example, sensors in the form of T-sensor nodes are randomly deployed around a target area where approaching lanes cross at an intersection. In other words, T-sensor nodes can acquire surrounding data, which they transmit to a roadside server through their neighbors based on a predetermined automatic mechanism; the user can then access a database to create a new service. As shown in <xref ref-type="fig" rid="f2-sensors-11-07420">Figure 2</xref>, these types of sensors consist of in-lane T-sensor nodes, T-sink nodes at roadsides, and local roadside equipment (RSE) servers. An RSE server located at the center of a crossroad gathers vehicular information from sensor nodes and transmits the gathered data to approaching vehicles. Using this collection and processing procedure, each vehicle that approaches the crossroad can be provided a new real-time service for avoiding potential traffic accidents.</p></sec><sec><label>2.3.</label><title>OBDII-Based Vehicle Sensor</title><p>An OBDII-based vehicle sensor is a device within a vehicle that senses the conditions inside the vehicle every second. Data from a vehicle sensor include the speed, revolutions per minute (RPM), battery voltage, coolant temperature, coordinates, direction, distance travelled, Diagnostic Trouble Codes (DTC), and fuel consumption, which are supplied by the controller area network (CAN) bus. Through a vehicle sensor placed in each vehicle, vehicle sensor data can be formatted as probe data or messages, which are processed, formatted, and transmitted to a smart road server for further processing to create a clear understanding of the driving environment.</p><p>As shown in <xref ref-type="fig" rid="f3-sensors-11-07420">Figure 3</xref>, an OBD II-based vehicle sensor is connected to the vehicle domain architecture designed by the vehicle manufacturer via a any gateway. The gateway is an interface device placed in a vehicle that acts as a mobile gateway between the vehicle's engine control unit (ECU) and an external device [ISO/DTR 13185-1.3].</p></sec><sec><label>2.4.</label><title>Framework of Smart Road Server and Sensor System</title><p>The framework of a smart road server and sensor system is shown in <xref ref-type="fig" rid="f4-sensors-11-07420">Figure 4</xref>. The framework consists of five parts: infrastructure-based sensors, vehicle sensors, smart roadside server, wireless communication, and traffic service providers. A series of processes for a road and vehicle system consists of data collection, data fusion and processing, and information provisioning. In data collection, not only do infrastructure-based sensors collect certain obstacle data, work zone data, incidents, and traffic signal times, but vehicle sensors also collect emission data as well as vehicle speed, location, and RPM. These data can be transmitted to a smart roadside server using infrastructure-to-infrastructure (I2I) and V2I communication networks such as DSRC and Wireless Access for Vehicular Environments (WAVE). At a roadside server, these data undergo appropriate processing such as data fusion. The optimal information is then provided to drivers through a Telematics The framework of a smart road server and sensor system should have the following capabilities and requirements:
<list list-type="bullet"><list-item><p>Real-time context-aware computing and event stream processing</p></list-item><list-item><p>Interoperability of various road sensors and vehicle data sensors</p></list-item><list-item><p>Wireless and seamless communication (V2I) such as DSRC, WAVE, or Wi-Fi</p></list-item><list-item><p>Distributed data sharing and transmitting to center server</p></list-item><list-item><p>Optimal database design and policy</p></list-item><list-item><p>Connection to Telematics and mobile phones</p></list-item><list-item><p>Authentication, authorization</p></list-item><list-item><p>Open standard platform</p></list-item></list></p><p>In particular, due to increasing user requests for real-time processing of large amounts of data coming from various data sources, the data processing paradigm has shifted from stored, static, and offline storage to streamed, dynamic, and online data sources. Some studies have been conducted on stream data processing like as vehicle and driver management system pattern query (VDMS-PQ) for the vehicle Telematics environment. Consequently, the smart road server and sensor system should be equipped adequate event stream processing method.</p></sec></sec><sec><label>3.</label><title>Application 1: Red-Light Violation Warning System at a Signalized Intersection</title><sec><label>3.1.</label><title>System Model</title><p>Several dangerous situations associated with high-speed approaches require special considerations when setting the signal timing intervals at a signalized intersection. For example, it may be difficult for a driver to decide whether to stop when the vehicle approaches a yellow light. The portion of the roadway before the intersection, where the driver may be indecisive (in stopping or proceeding into and through the intersection at the onset of a yellow light) is called the dilemma zone. Some drivers may violate a red signal due to this indecisiveness.</p><p>As shown in <xref ref-type="fig" rid="f5-sensors-11-07420">Figure 5</xref>, as a vehicle approaches an intersection, we can decide whether it is in a dangerous position in the dilemma zone through the relationship between the remaining green or yellow times and the distance to the stop line. Real-time traveling data is collected at this service intersection through infrastructure-based sensors and vehicle sensors. A smart road server then processes a red-light violation warning algorithm, and the driver is provided the relevant information through a Telematics device.</p><p>In this research, we developed a red-light violation warning algorithm using the minimum safe stopping distance (SSD) and critical crossing distance. There is a relationship between the minimum SSD during the remaining time of a yellow signal and the critical safe crossing distance (CCD). A dilemma exists if SSD is greater than CCD for a vehicle upon data collection. If the intersection has sensor systems and a roadside server, each vehicle that approaches the crossroad can then predict and avoid possible traffic accidents.</p></sec><sec><label>3.2.</label><title>Processing Algorithm</title><p>In this study, we developed a red-violation warning model for potential traffic conflicts at intersections based on real-time traffic data collected on vehicles in the approaching lane. This research also addresses the concept of potential traffic conflicts at an intersection. As a red-light violation warning model for signalized intersections, this research includes a red-light violation warning prediction model that considers the signal phase and remaining signal time when the vehicle’s location, speed, and time data are collected using multiple traffic sensors placed at the approaching lane.</p><p>A flowchart for the algorithm used in the model is shown in <xref ref-type="fig" rid="f6-sensors-11-07420">Figure 6</xref>. There are three types of wating time (WT), WT1, WT2 and WT3, provided in step 4.
<list list-type="bullet"><list-item><p>Step 1: Collect real-time vehicle speed and location data at an intersection using road sensors and vehicular data through V2I communication networks.</p></list-item><list-item><p>Step 2: Calculate whether the time gap between continuous vehicles is longer than the critical length. If so, then go to step 3.</p></list-item><list-item><p>Step 3: Calculate whether the remaining time for a green light is more than 0.</p><p>If so, go to the WT1 process in step 4.</p><p>Otherwise, go to the WT2 process in step 4.</p></list-item><list-item><p>Step 4: In the WT1 case, if the remaining time for a green light is less than k1, calculate the red-light violation warning information as in <xref ref-type="disp-formula" rid="FD1">Equations (1)</xref> and <xref ref-type="disp-formula" rid="FD2">(2)</xref>:
<disp-formula id="FD1"><label>(1)</label><mml:math id="M1"><mml:mrow><mml:mi mathvariant="italic">lower</mml:mi><mml:mo>_</mml:mo><mml:msubsup><mml:mrow><mml:mi mathvariant="italic">CV</mml:mi></mml:mrow><mml:mi>i</mml:mi><mml:mrow><mml:mi mathvariant="italic">WT</mml:mi><mml:mn>1</mml:mn></mml:mrow></mml:msubsup><mml:mo>=</mml:mo><mml:mfrac><mml:mrow><mml:mo>−</mml:mo><mml:msub><mml:mrow><mml:mi>t</mml:mi></mml:mrow><mml:mrow><mml:mi mathvariant="italic">PRT</mml:mi></mml:mrow></mml:msub><mml:mo>+</mml:mo><mml:msqrt><mml:mrow><mml:msubsup><mml:mrow><mml:mi>t</mml:mi></mml:mrow><mml:mrow><mml:mi mathvariant="italic">PRT</mml:mi></mml:mrow><mml:mn>2</mml:mn></mml:msubsup><mml:mo>+</mml:mo><mml:mfrac><mml:mrow><mml:mn>2</mml:mn><mml:mo>⋅</mml:mo><mml:msub><mml:mi>X</mml:mi><mml:mi>i</mml:mi></mml:msub></mml:mrow><mml:mrow><mml:mi>d</mml:mi><mml:mo>+</mml:mo><mml:mi>G</mml:mi><mml:mo>⋅</mml:mo><mml:mi>g</mml:mi></mml:mrow></mml:mfrac></mml:mrow></mml:msqrt></mml:mrow><mml:mrow><mml:mn>1</mml:mn><mml:mo>/</mml:mo><mml:mo stretchy="false">(</mml:mo><mml:mi>d</mml:mi><mml:mo>+</mml:mo><mml:mi>G</mml:mi><mml:mo>⋅</mml:mo><mml:mi>g</mml:mi><mml:mo stretchy="false">)</mml:mo></mml:mrow></mml:mfrac></mml:mrow></mml:math></disp-formula><disp-formula id="FD2"><label>(2)</label><mml:math id="M2"><mml:mrow><mml:mi mathvariant="italic">upper</mml:mi><mml:mo>_</mml:mo><mml:msubsup><mml:mrow><mml:mi mathvariant="italic">CV</mml:mi></mml:mrow><mml:mi>i</mml:mi><mml:mrow><mml:mi mathvariant="italic">WT</mml:mi><mml:mn>1</mml:mn></mml:mrow></mml:msubsup><mml:mo>=</mml:mo><mml:mfrac><mml:mrow><mml:mi>X</mml:mi><mml:mi>i</mml:mi><mml:mo>+</mml:mo><mml:mo stretchy="false">(</mml:mo><mml:mi>W</mml:mi><mml:mo>+</mml:mo><mml:mi>L</mml:mi><mml:mo stretchy="false">)</mml:mo><mml:mo>−</mml:mo><mml:mfrac><mml:mn>1</mml:mn><mml:mn>2</mml:mn></mml:mfrac><mml:mi>a</mml:mi><mml:msup><mml:mrow><mml:mrow><mml:mo stretchy="false">(</mml:mo><mml:mi>r</mml:mi><mml:mi>e</mml:mi><mml:mi>m</mml:mi><mml:mi>a</mml:mi><mml:mi>i</mml:mi><mml:mi>n</mml:mi><mml:mo>_</mml:mo><mml:mi>g</mml:mi><mml:mo>+</mml:mo><mml:mi>e</mml:mi><mml:mi>x</mml:mi><mml:mi>t</mml:mi><mml:mi>e</mml:mi><mml:mi>n</mml:mi><mml:mi>d</mml:mi><mml:mo>_</mml:mo><mml:mi>y</mml:mi><mml:mo>−</mml:mo><mml:msub><mml:mrow><mml:mi>t</mml:mi></mml:mrow><mml:mrow><mml:mi mathvariant="italic">PRT</mml:mi></mml:mrow></mml:msub><mml:mo stretchy="false">)</mml:mo></mml:mrow></mml:mrow><mml:mn>2</mml:mn></mml:msup></mml:mrow><mml:mrow><mml:mi mathvariant="italic">remain</mml:mi><mml:mo>_</mml:mo><mml:mi>g</mml:mi><mml:mo>+</mml:mo><mml:mi>e</mml:mi><mml:mi>x</mml:mi><mml:mi>t</mml:mi><mml:mi>e</mml:mi><mml:mi>n</mml:mi><mml:mi>t</mml:mi><mml:mo>_</mml:mo><mml:mi>y</mml:mi></mml:mrow></mml:mfrac></mml:mrow></mml:math></disp-formula></p></list-item></list></p><p>In this case, if
<inline-formula><mml:math id="M3"><mml:mrow><mml:mi mathvariant="italic">lower</mml:mi><mml:mo>_</mml:mo><mml:mi>C</mml:mi><mml:msubsup><mml:mrow><mml:mi>V</mml:mi></mml:mrow><mml:mi>i</mml:mi><mml:mrow><mml:mi mathvariant="italic">WT</mml:mi><mml:mn>1</mml:mn></mml:mrow></mml:msubsup><mml:mo>≤</mml:mo><mml:msub><mml:mrow><mml:mi>v</mml:mi></mml:mrow><mml:mi>i</mml:mi></mml:msub><mml:mo>≤</mml:mo><mml:mi mathvariant="italic">upper</mml:mi><mml:mo>_</mml:mo><mml:msubsup><mml:mrow><mml:mi mathvariant="italic">CV</mml:mi></mml:mrow><mml:mi>i</mml:mi><mml:mrow><mml:mi mathvariant="italic">WT</mml:mi><mml:mn>1</mml:mn></mml:mrow></mml:msubsup></mml:mrow></mml:math></inline-formula>, a red-light violation is determined. The WT2 case calculates whether the remaining time for a yellow light is greater than 0. If so, the following equation of a dangerous red-light violation is calculated. Otherwise, proceed to the WT3 stage:
<disp-formula id="FD3"><label>(3)</label><mml:math id="M4"><mml:mrow><mml:mi mathvariant="italic">lower</mml:mi><mml:mo>_</mml:mo><mml:msubsup><mml:mrow><mml:mi mathvariant="italic">CV</mml:mi></mml:mrow><mml:mi>i</mml:mi><mml:mrow><mml:mi mathvariant="italic">WT</mml:mi><mml:mn>2</mml:mn></mml:mrow></mml:msubsup><mml:mo>=</mml:mo><mml:mfrac><mml:mrow><mml:mo>−</mml:mo><mml:mo stretchy="false">(</mml:mo><mml:msub><mml:mrow><mml:mi>t</mml:mi></mml:mrow><mml:mrow><mml:mi mathvariant="italic">PRT</mml:mi></mml:mrow></mml:msub><mml:mo>+</mml:mo><mml:mi>r</mml:mi><mml:mi>e</mml:mi><mml:mi>m</mml:mi><mml:mi>a</mml:mi><mml:mi>i</mml:mi><mml:mi>n</mml:mi><mml:mo>_</mml:mo><mml:mi>y</mml:mi><mml:mo>−</mml:mo><mml:mi>Y</mml:mi><mml:mo stretchy="false">)</mml:mo><mml:mo>+</mml:mo><mml:msqrt><mml:mrow><mml:msup><mml:mrow><mml:mrow><mml:mo stretchy="false">(</mml:mo><mml:msub><mml:mrow><mml:mi>t</mml:mi></mml:mrow><mml:mrow><mml:mi mathvariant="italic">PRT</mml:mi></mml:mrow></mml:msub><mml:mo>+</mml:mo><mml:mi mathvariant="italic">remain</mml:mi><mml:mo>_</mml:mo><mml:mi>y</mml:mi><mml:mo>−</mml:mo><mml:mi>Y</mml:mi><mml:mo stretchy="false">)</mml:mo></mml:mrow></mml:mrow><mml:mn>2</mml:mn></mml:msup><mml:mo>+</mml:mo><mml:mfrac><mml:mrow><mml:mn>2</mml:mn><mml:mo>⋅</mml:mo><mml:msub><mml:mi>X</mml:mi><mml:mi>i</mml:mi></mml:msub></mml:mrow><mml:mrow><mml:mi>d</mml:mi><mml:mo>+</mml:mo><mml:mi>G</mml:mi><mml:mo>⋅</mml:mo><mml:mi>g</mml:mi></mml:mrow></mml:mfrac></mml:mrow></mml:msqrt></mml:mrow><mml:mrow><mml:mn>1</mml:mn><mml:mo>/</mml:mo><mml:mo stretchy="false">(</mml:mo><mml:mi>d</mml:mi><mml:mo>+</mml:mo><mml:mi>G</mml:mi><mml:mo>⋅</mml:mo><mml:mi>g</mml:mi><mml:mo stretchy="false">)</mml:mo></mml:mrow></mml:mfrac></mml:mrow></mml:math></disp-formula><disp-formula id="FD4"><label>(4)</label><mml:math id="M5"><mml:mrow><mml:mi mathvariant="italic">upper</mml:mi><mml:mo>_</mml:mo><mml:msubsup><mml:mrow><mml:mi mathvariant="italic">CV</mml:mi></mml:mrow><mml:mi>i</mml:mi><mml:mrow><mml:mi mathvariant="italic">WT</mml:mi><mml:mn>2</mml:mn></mml:mrow></mml:msubsup><mml:mo>=</mml:mo><mml:mfrac><mml:mrow><mml:msub><mml:mi>X</mml:mi><mml:mi>i</mml:mi></mml:msub><mml:mo>+</mml:mo><mml:mo stretchy="false">(</mml:mo><mml:mi>W</mml:mi><mml:mo>+</mml:mo><mml:mi>L</mml:mi><mml:mo stretchy="false">)</mml:mo><mml:mo>−</mml:mo><mml:mfrac><mml:mn>1</mml:mn><mml:mn>2</mml:mn></mml:mfrac><mml:mi>a</mml:mi><mml:msup><mml:mrow><mml:mrow><mml:mo stretchy="false">(</mml:mo><mml:mi mathvariant="italic">remain</mml:mi><mml:mo>_</mml:mo><mml:mi>y</mml:mi><mml:mo>−</mml:mo><mml:msub><mml:mrow><mml:mi>t</mml:mi></mml:mrow><mml:mrow><mml:mi mathvariant="italic">PRT</mml:mi></mml:mrow></mml:msub><mml:mo stretchy="false">)</mml:mo></mml:mrow></mml:mrow><mml:mn>2</mml:mn></mml:msup></mml:mrow><mml:mrow><mml:mi mathvariant="italic">remain</mml:mi><mml:mo>_</mml:mo><mml:mi>y</mml:mi></mml:mrow></mml:mfrac></mml:mrow></mml:math></disp-formula></p><p>In this case, if
<inline-formula><mml:math id="M6"><mml:mrow><mml:mi mathvariant="italic">lower</mml:mi><mml:mo>_</mml:mo><mml:mi>C</mml:mi><mml:msubsup><mml:mrow><mml:mi>V</mml:mi></mml:mrow><mml:mi>i</mml:mi><mml:mrow><mml:mi mathvariant="italic">WT</mml:mi><mml:mn>2</mml:mn></mml:mrow></mml:msubsup><mml:mo>≤</mml:mo><mml:msub><mml:mrow><mml:mi>v</mml:mi></mml:mrow><mml:mi>i</mml:mi></mml:msub><mml:mo>≤</mml:mo><mml:mi mathvariant="italic">upper</mml:mi><mml:mo>_</mml:mo><mml:mi>C</mml:mi><mml:msubsup><mml:mrow><mml:mi>V</mml:mi></mml:mrow><mml:mi>i</mml:mi><mml:mrow><mml:mi mathvariant="italic">WT</mml:mi><mml:mn>2</mml:mn></mml:mrow></mml:msubsup></mml:mrow></mml:math></inline-formula>, a red-light violation is determined. Finally, in the WT3 case, if the speed indicated at the stop line where the detecting sensor nodes are placed is more than 0 km/h during a red light, the potential for a collision is determined. Our proposed algorithms include the following variables and parameters:
<list list-type="simple"><list-item><p>– <italic>v<sub>i</sub></italic> : vehicle speed indicated by a point detection sensor node at location i</p></list-item><list-item><p>– <italic>t<sub>PRT</sub></italic> : driver’s perception and response time (s),</p></list-item><list-item><p>– <italic>a</italic> : acceleration rate (m/s<sup>2</sup>)</p></list-item><list-item><p>– <italic>W</italic> : intersection width (m)</p></list-item><list-item><p>– <italic>L</italic> : vehicle length (m)</p></list-item><list-item><p>– <italic>d</italic> : stationary deceleration rate (gravity rate × friction factor) (m/s<sup>2</sup>)</p></list-item><list-item><p>– <italic>g</italic> : gravity constant (9.8 m/s<sup>2</sup>)</p></list-item><list-item><p>– <italic>G</italic> : grade (m/m, %)</p></list-item><list-item><p>– <italic>extend</italic> _<italic>y</italic> : extended time (s)</p></list-item><list-item><p>– <italic>remain</italic> _<italic>g</italic> : remaining green time (s)</p></list-item><list-item><p>– <italic>remain</italic> _<italic>y</italic> : remaining yellow time (s)</p></list-item><list-item><p>– <italic>X<sub>i</sub></italic> : distance between location i to stop line (m)</p></list-item><list-item><p>–
<inline-formula><mml:math id="M7"><mml:mrow><mml:mi mathvariant="italic">upper</mml:mi><mml:mo>_</mml:mo><mml:msubsup><mml:mrow><mml:mi mathvariant="italic">CV</mml:mi></mml:mrow><mml:mi>i</mml:mi><mml:mrow><mml:mi mathvariant="italic">WT</mml:mi><mml:mn>1</mml:mn></mml:mrow></mml:msubsup></mml:mrow></mml:math></inline-formula>: critical speed at which a vehicle cannot stop in a WT1 case (km/h, m/s)</p></list-item><list-item><p>–
<inline-formula><mml:math id="M8"><mml:mrow><mml:mi mathvariant="italic">upper</mml:mi><mml:mo>_</mml:mo><mml:msubsup><mml:mrow><mml:mi mathvariant="italic">CV</mml:mi></mml:mrow><mml:mi>i</mml:mi><mml:mrow><mml:mi mathvariant="italic">WT</mml:mi><mml:mn>2</mml:mn></mml:mrow></mml:msubsup></mml:mrow></mml:math></inline-formula>: critical speed at which a vehicle cannot stop in a WT2 case (km/h, m/s)</p></list-item><list-item><p>–
<inline-formula><mml:math id="M9"><mml:mrow><mml:mi mathvariant="italic">lower</mml:mi><mml:mo>_</mml:mo><mml:msubsup><mml:mrow><mml:mi mathvariant="italic">CV</mml:mi></mml:mrow><mml:mi>i</mml:mi><mml:mrow><mml:mi mathvariant="italic">WT</mml:mi><mml:mn>1</mml:mn></mml:mrow></mml:msubsup></mml:mrow></mml:math></inline-formula>: critical speed at which a vehicle can stop in a WT1 case (km/h, m/s)</p></list-item><list-item><p>–
<inline-formula><mml:math id="M10"><mml:mrow><mml:mi mathvariant="italic">lower</mml:mi><mml:mo>_</mml:mo><mml:msubsup><mml:mrow><mml:mi mathvariant="italic">CV</mml:mi></mml:mrow><mml:mi>i</mml:mi><mml:mrow><mml:mi mathvariant="italic">WT</mml:mi><mml:mn>2</mml:mn></mml:mrow></mml:msubsup></mml:mrow></mml:math></inline-formula>: critical speed at which a vehicle can stop in a WT2 case (km/h, m/s)</p></list-item></list><list list-type="bullet"><list-item><p>Step 5: Provide a driver safety warning through a Telematics device using a V2I communication network</p></list-item></list></p></sec><sec sec-type="results"><label>3.3.</label><title>Evaluation Results Based on Microscopic Traffic Simulation</title><p>An evaluation of in- and out-of-vehicle traveller information systems is well-suited to virtual testing, which has an advantage over roadway studies, because it allows an examination of parameters of interest in difficult and critical driving situations without subjecting drivers to unnecessary risks. The first step in a simulation experiment is to design a simulated virtual intersection system that can replicate real-world traffic conditions and IT technology. To ensure the reliability and quality of the simulated results, this research has calibrated a simulation program. <xref ref-type="table" rid="t1-sensors-11-07420">Table 1</xref> summarizes the simulated conditions, such as traffic and road situations, signal control factors, and sensing points. After simulating using VISSIM scenarios, we analysed the *.mer file of each point sensor. Using algorithm-equipped automated software, we then performed the warning collision model using real-time synchronized signal times in Java-implemented software.</p><p>The scenarios used for the simulation testing are as follows: there were a total of 120 scenarios used based on roadway design speed, input volume, and driver perception response time parameters.
<list list-type="bullet"><list-item><p>Road design parameters: 50 km/h, 60 km/h, 70 km/h, 80 km/h (4 cases)</p></list-item><list-item><p>Input volume parameters: 100–1,500 (vehicles/h) (15 cases)</p></list-item><list-item><p>Driver perception and response times (<italic>t<sub>PRT</sub></italic>): 1.5 s, 2 s (2 cases)</p></list-item></list></p><p>There are two main methods of verification for the developed model. One method compares the results from the red-light violation warning system with the field value from the ratio of red-light violations in real-world vehicular data The other method compares the results of simulation with the values from the simulation’s red-light violation ratio under simulation environments. We use the second method in which we locate the verification sensors within a dilemma zone at an intersection and analyze whether the vehicle collisions are forecasted. In other words, we compare the ID of a predicted red-light violation warning vehicle with the ID of a simulated vehicle in the red-violation warning system under a potential collision situation. <xref ref-type="table" rid="t2-sensors-11-07420">Table 2</xref> shows the verification results of the red-light violation warning system based on VISSIM tools. For verification, we use a remaining yellow light period of 1 s and a beginning red light period of 5 s. The results are the average values and percentages of all scenarios. In these results, there are 30.4 red-light violating vehicles and 524.4 non red-light violating vehicles predicted by the red-violation warning algorithm at simulation scenarios. In this case, there are around 25.3 really red-light violating vehicles in 30.4 red-light violating vehicles based on the vehicle ID verification. Thus, the percentage of red-light violation warning prediction is 88.5%, that is, 25.3 vehicles divided by 28.6 vehicles. Also, the correct classification rate is 98.5% (4.6% + 93.9%), where correct classification indicates whether red-light violating vehicles are properly classified. Thus, this current model is considered to have a very significant level of accuracy.</p></sec><sec><label>3.4.</label><title>Driver Assistance and Safety Warning using In-Vehicle Telematics Device</title><p>If the discrimination results of red-light violation warning information indicate a red-light violation, a warning is provided to the vehicle’s Telematics device using a wireless communication network such as DSRC, WAVE, or Wi-Fi. Most fatal accidents at signalized intersections are caused by problems within the dilemma zone. The portion of roadway in advance of an intersection where a driver may be indecisive about stopping at the onset of a yellow light is called the dilemma zone. This method of driver assistance and safety warning can reduce the number of dilemma zone accidents. That is, the smart roadside sever system allows a driver to reduce his speed by notifying him when an impending collision is expected. With this information, the driver can safely stop at the stop line. Moreover, in cases in which a car is predicted not to stop at a stop line, the system provides information to the traffic signal controller, which creates a red traffic signal for all lanes. This research considers the possibility that the application of such a new service is possible for the safety of signalized intersections. In this case, the red-light violation warning model may be directly provided to all vehicle users. <xref ref-type="fig" rid="f7-sensors-11-07420">Figure 7</xref> shows the simulation field test results about virtual signalized intersection in which the terminal in vehicles can be provided the red violation warning information to drivers.</p></sec></sec><sec><label>4.</label><title>Application 2: Advisory Speed Providing System on a Highway</title><sec><label>4.1.</label><title>System Model</title><p>A highway traffic system requires basic data such as vehicular data (speed, location), traffic flow, traffic control, safety information, road conditions, and weather information. A smart roadside system receives road surface data from each zone in a service area from at least one road sensor located in such a way as to calculate the road safety coefficient. The system also collects vehicular data from OBDII-based vehicle sensors in order to calculate the traffic flow coefficient. The system provides a vehicular safety service to a telematics device using the road safety coefficient of each zone, along with the traffic flow analysis coefficient. As shown in <xref ref-type="fig" rid="f8-sensors-11-07420">Figure 8</xref>, the recommend speed for an icy road is 60 km/h, which is calculated using traffic data and road surface sensing data. The approaching speeds are also reduced from 80 km/h to 70 km/h, before reaching the 60 km/h recommendation. These approaching speeds are delivered to the drivers.</p></sec><sec><label>4.2.</label><title>Processing Algorithm</title><p>This system also provides driver assistance information through a Telematics device. The additional information includes advisory safety speed information considering road surface data such as snow, rain, obstacles, or ice. The advisory safety speed algorithm is equipped with a smart roadside server in the service area. The method for providing vehicular safety service includes receiving the road surface state data of each zone in the service area from infrastructure-based sensors; receiving location and running data from OBDII-based vehicle sensors; estimating the advisory safety speed based on the road surface status, location, and running data; and transmitting safe-distance risk information based on the advisory safety speed to the in-vehicle Telematics device.</p><p>Our advisory safety speed model consists of two parts: The first part is a macro car-following model that is used for considering highway traffic parameters, while the other is a safe stopping distance model for monitoring road-surface data. The formula used for advisory safety speed adv_u<sub>j</sub> at time period <italic>k</italic> on road section <italic>j</italic> is shown in <xref ref-type="disp-formula" rid="FD5">Equation (5)</xref>. This algorithm is equipped at and performed by the smart roadside sever on a highway:
<disp-formula id="FD5"><label>(5)</label><mml:math id="M11"><mml:mrow><mml:msub><mml:mrow><mml:mrow><mml:mtext>adv</mml:mtext></mml:mrow></mml:mrow><mml:mrow><mml:msub><mml:mrow><mml:mi mathvariant="normal">u</mml:mi></mml:mrow><mml:mi mathvariant="normal">j</mml:mi></mml:msub><mml:mo stretchy="false">(</mml:mo><mml:mi>k</mml:mi><mml:mo stretchy="false">)</mml:mo></mml:mrow></mml:msub><mml:mo>=</mml:mo><mml:mo stretchy="false">[</mml:mo><mml:msub><mml:mrow><mml:mi>t</mml:mi></mml:mrow><mml:mrow><mml:mi mathvariant="italic">PRT</mml:mi></mml:mrow></mml:msub><mml:mo>+</mml:mo><mml:msqrt><mml:mrow><mml:msub><mml:mrow><mml:mi>t</mml:mi></mml:mrow><mml:mrow><mml:mi mathvariant="italic">PRT</mml:mi></mml:mrow></mml:msub><mml:msup><mml:mrow></mml:mrow><mml:mn>2</mml:mn></mml:msup><mml:mo>+</mml:mo><mml:mfrac><mml:mrow><mml:mn>2</mml:mn><mml:mo>⋅</mml:mo><mml:mo stretchy="false">(</mml:mo><mml:msub><mml:mrow><mml:mi>t</mml:mi></mml:mrow><mml:mrow><mml:mi mathvariant="italic">PRT</mml:mi></mml:mrow></mml:msub><mml:mo>⋅</mml:mo><mml:msub><mml:mrow><mml:mi>u</mml:mi></mml:mrow><mml:mi>j</mml:mi></mml:msub><mml:mo stretchy="false">(</mml:mo><mml:mi>k</mml:mi><mml:mo stretchy="false">)</mml:mo><mml:mo>+</mml:mo><mml:mi>L</mml:mi><mml:mo stretchy="false">)</mml:mo><mml:mo>⋅</mml:mo><mml:msub><mml:mrow><mml:mi>t</mml:mi></mml:mrow><mml:mrow><mml:mi mathvariant="italic">PRT</mml:mi></mml:mrow></mml:msub></mml:mrow><mml:mrow><mml:mi>g</mml:mi><mml:mo stretchy="false">(</mml:mo><mml:msub><mml:mrow><mml:mi>f</mml:mi></mml:mrow><mml:mi>j</mml:mi></mml:msub><mml:mo stretchy="false">(</mml:mo><mml:mi>k</mml:mi><mml:mo stretchy="false">)</mml:mo><mml:mo>+</mml:mo><mml:msub><mml:mi>G</mml:mi><mml:mi>j</mml:mi></mml:msub><mml:mo stretchy="false">(</mml:mo><mml:mi>k</mml:mi><mml:mo stretchy="false">)</mml:mo><mml:mo stretchy="false">)</mml:mo></mml:mrow></mml:mfrac></mml:mrow></mml:msqrt><mml:mo stretchy="false">]</mml:mo><mml:mo>⋅</mml:mo><mml:mo stretchy="false">[</mml:mo><mml:mi>g</mml:mi><mml:mo stretchy="false">(</mml:mo><mml:msub><mml:mrow><mml:mi>f</mml:mi></mml:mrow><mml:mi>j</mml:mi></mml:msub><mml:mo stretchy="false">(</mml:mo><mml:mi>k</mml:mi><mml:mo stretchy="false">)</mml:mo><mml:mo>+</mml:mo><mml:msub><mml:mi>G</mml:mi><mml:mi>j</mml:mi></mml:msub><mml:mo stretchy="false">(</mml:mo><mml:mi>k</mml:mi><mml:mo stretchy="false">)</mml:mo><mml:mo stretchy="false">)</mml:mo><mml:mo stretchy="false">]</mml:mo></mml:mrow></mml:math></disp-formula>where:
<list list-type="bullet"><list-item><p><italic>t<sub>PRT</sub></italic>: driver perception and response time (s),</p></list-item><list-item><p><italic>u<sub>j</sub></italic><italic>(k)</italic>: the mean speed (or 85% of the top speed) at time period k on road section j (m/s),</p></list-item><list-item><p>L: the spacing at a vehicle stop (vehicle distance + gap between vehicles),</p></list-item><list-item><p><italic>f<sub>j</sub></italic><italic>(k)</italic>: the road-friction parameter at time period k on road section j,</p></list-item><list-item><p><italic>G<sub>j</sub></italic><italic>(k)</italic>: the grade at link j during collection period k (%),</p></list-item><list-item><p><italic>g</italic>: the acceleration rate of gravity, 9.8 (m/s),</p></list-item><list-item><p><italic>k</italic>: collection time period k (s), and</p></list-item><list-item><p><italic>j</italic>: the number of road sections.</p></list-item></list></p></sec><sec sec-type="results"><label>4.3.</label><title>Evaluation Results Based on Microscopic Traffic Simulation</title><p>In this research, we also evaluated the advisory speed model using VISSIM. After simulating 12 different scenarios, as shown in <xref ref-type="table" rid="t3-sensors-11-07420">Table 3</xref>, we then created the advisory safety speed model using a program in C++. The configuration of the study network used in the simulation is as follows:
<list list-type="bullet"><list-item><p>Length of road section = 1 km</p></list-item><list-item><p>Number of lanes = 2</p></list-item><list-item><p>Vehicle Capacity = 2,200 pcphpl (passenger car per hour per lane)</p></list-item><list-item><p>Design speed = 110 km/h</p></list-item><list-item><p>Location of events = 650–700 m from inflow point</p></list-item></list></p><p>The default parameters upon implementation of the simulation are as given below. Also, the algorithm update and information provisioning period is fixed at 5 min:
<list list-type="bullet"><list-item><p><italic>t<sub>PRT</sub></italic>: 2 s</p></list-item><list-item><p><italic>G<sub>j</sub></italic><italic>(k)</italic>: 0%</p></list-item><list-item><p>L: 10 m</p></list-item></list></p><p>The simulation results for an advisory safety speed show that the most appropriate safety speed has a smaller stopping space than the mean speed for travelling vehicles. In <xref ref-type="fig" rid="f9-sensors-11-07420">Figure 9</xref>, the red line is the average speed per segment based on the simulation results, and the blue line is the advisory safety speed based on the suggested algorithm. For traffic simulation at the microscopic level, main parameters such as traffic condition [good/capacity (jam)], accident state (with/without accident), and road surface condition (dry/wet/ice) determine the advisory safety level and average speed. The results show that the advisory safety speed tends to decrease as the average speed decreases. In particular, the rate of decrease is quite sensitive in cases of accidents. When the traffic condition is at capacity, the average advisory safety speed is 60 km/h. This is 10 km/h less than under good conditions.
<list list-type="bullet"><list-item><p>Horizontal axis: time line (unit: s)</p></list-item><list-item><p>Vertical axis: speed (unit: km/h)</p></list-item><list-item><p>Red line: the average speed per segment based on the simulation results</p></list-item><list-item><p>Blue line: the advisory safety speed based on the suggested algorithm</p></list-item></list></p><p>When the road surface is dry, wet, or icy, the average advisory safety speeds are 80 km/h, 76 km/h, and 68 km/h, respectively. Under an accident situation, the average advisory safety speed is 40 km/h, which is 40 km/h less than when no accidents have occurred. <xref ref-type="fig" rid="f9-sensors-11-07420">Figure 9(a–c)</xref> shows some of the simulation results for 12 scenarios under good traffic conditions and accident states, but where the state of the road surface state varies.</p></sec><sec><label>4.4.</label><title>Driver Assistance and Safety Warning by an In-Vehicle Telematics Device</title><p>As the results of the algorithm are advisory safety speeds for drivers, advisory safety information should be provided to in-vehicle Telematics devices using I2V. <xref ref-type="fig" rid="f10-sensors-11-07420">Figures 10</xref> and <xref ref-type="fig" rid="f11-sensors-11-07420">11</xref> show examples of a GUI used in a Telematics terminal. As shown in <xref ref-type="fig" rid="f11-sensors-11-07420">Figure 11</xref>, the ‘80’ in the left-circle indicates the optimal advisory speed for road surface data such as ice, under the current traffic condition. This GUI displays the results from the developed Telematics device, and shows the total driving distance, total driving time, amount of fuel consumption, and CO<sub>2</sub> emissions of the vehicle via an OBDII interface from an ECU. This device is very useful for driver assistance. In recent research, providing road surface warning signs has shown to be effective in reducing accident frequency and severity. Also, speed is not only related to the risk of being involved in a crash in the first place, but also affects the severity of a crash when one occurs. This processing method from a smart roadside server can be used as a new service model for uninterrupted roads that have implemented new information and communications technologies such as an Intelligent Vehicle Highway System (IVHS).</p></sec></sec><sec><label>5.</label><title>Conclusions</title><p>This paper has presented a framework for a smart roadside system and sensors such as infrastructure-base sensors and OBDII-based vehicle sensors. As application cases for this system, new real-time road services for two road types, signalized intersections and highway roads, were developed and applied to service algorithms for driver assistance and safety information services. The main services for the two road types are a red-light violation warning system at signalized intersections and an advisory speed provisioning system on highways. In this paper, the evaluation results of the simulation method are shown and applied to a real road and vehicle system for driver assistance and safety warnings.</p><p>Under the given real-time application for drivers, the framework and certain algorithms produce a very efficient solution with respect to roadway type features and sensor type use. As shown in some examples using an in-vehicle Telematics device, these technologies are very useful for a real-time application model in the present roadway system. This method was tested in a couple of vehicles at real intersections and highways. However, many vehicle and road types were not applied or tested through the micro traffic simulation tools. As a limitation of this study, the simulation method has certain errors related to the tool used, and has not been calibrated with real vehicle movements and roadway features. However, the suggested method can be applied for all vehicles equipped with Telematics devices and vehicle sensors, when roadway facilities have reliably collected vehicle and road data in real-time through infrastructure-based sensors. In reality, this service may be used in future roadway systems. After the installation and operation of various road and vehicle sensor systems, the qualitative and quantitative effects and benefits of this system can be demonstrated. Although this research is limited to certain sectors, the results of this paper demonstrate the feasibility of applying this new service system using infrastructure-based sensors and OBDII-based vehicle sensors. Under the given system applications, a framework utilizing certain algorithms will be a very efficient solution with respect to roadway-type features and sensor-type use.</p></sec></body><back><ack><p>This work was supported by MKE/ISTK (Mega Convergence Core Technology Development).</p></ack><ref-list><title>References</title><ref id="b1-sensors-11-07420"><label>1.</label><element-citation publication-type="webpage"><person-group person-group-type="author"><collab>RITA</collab></person-group><source>Policy White Paper, Achieving the Vision: From VII to IntelliDrive, ITS JPO U.S. DOT</source><year>2010</year><comment>Available online: <ext-link ext-link-type="uri" xlink:href="www.intellidriveusa.org/documents/White%20Paper%20-%20From%20VII%20to%20IntelliDrive%20_04_28_10_final.pdf">www.intellidriveusa.org/documents/White%20Paper%20-%20From%20VII%20to%20IntelliDrive%20_04_28_10_final.pdf</ext-link> (accessed on 18 July 2011).</comment></element-citation></ref><ref id="b2-sensors-11-07420"><label>2.</label><element-citation publication-type="webpage"><person-group person-group-type="author"><collab>RITA</collab></person-group><source>White Paper: The Scope of Smart Roadside, ITS JPO U.S. DOT, The IntelliDrive</source><year>2010</year><comment>Available online: <ext-link ext-link-type="uri" xlink:href="www.intellidriveusa.org/.../Smart%20Roadside%20White%20Paper%20Final%20April%202010.pdf">www.intellidriveusa.org/.../Smart%20Roadside%20White%20Paper%20Final%20April%202010.pdf</ext-link> (accessed on 18 July 2011).</comment></element-citation></ref><ref id="b3-sensors-11-07420"><label>3.</label><element-citation publication-type="webpage"><person-group person-group-type="author"><collab>EU Information Society and Media Safety</collab></person-group><source>CVIS (Cooperative Vehicle Infrastructure Systems) Mobility 2.0 the New Cooperative Era</source><year>2010</year><comment>Available online: <ext-link ext-link-type="uri" xlink:href="http://cvis.odeum.com/en/public_documents/publications">http://cvis.odeum.com/en/public_documents/publications</ext-link> (accessed on 18 July 2011)</comment></element-citation></ref><ref id="b4-sensors-11-07420"><label>4.</label><element-citation publication-type="book"><person-group person-group-type="author"><name><surname>Hirst</surname><given-names>S</given-names></name><name><surname>Graham</surname><given-names>R</given-names></name></person-group><article-title>The Format and Presentation of Collision Warnings</article-title><source>Ergonomics and Safety of Intelligent Driver Interfaces</source><person-group person-group-type="editor"><name><surname>Noy</surname><given-names>NI</given-names></name></person-group><publisher-name>Lawrence Erlbaum Associates</publisher-name><publisher-loc>Mahwah, NJ, USA</publisher-loc><year>1997</year><fpage>203</fpage><lpage>219</lpage></element-citation></ref><ref id="b5-sensors-11-07420"><label>5.</label><element-citation publication-type="book"><person-group person-group-type="author"><name><surname>Klein</surname><given-names>LA</given-names></name><name><surname>Mills</surname><given-names>MK</given-names></name><name><surname>Gibson</surname><given-names>DRP</given-names></name></person-group><source>Traffic Detector Handbook: Third Edition—Volume I</source><comment>FHWA-HRT-06-108</comment><publisher-name>FHWA</publisher-name><publisher-loc>Washington, DC, USA</publisher-loc></element-citation></ref><ref id="b6-sensors-11-07420"><label>6.</label><element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Kim</surname><given-names>J</given-names></name><name><surname>Kwon</surname><given-names>OC</given-names></name><name><surname>Kim</surname><given-names>H</given-names></name></person-group><article-title>Development of an event stream processing system for the vehicle Telematics environment</article-title><source>ETRI J</source><year>2009</year><volume>31</volume><fpage>463</fpage><lpage>465</lpage></element-citation></ref><ref id="b7-sensors-11-07420"><label>7.</label><element-citation publication-type="book"><person-group person-group-type="author"><name><surname>Pant</surname><given-names>P</given-names></name><name><surname>Xie</surname><given-names>Y</given-names></name></person-group><source>Comparative Study of Advanced Warning Signs at High Speed Signalized Intersections</source><comment>Transportation Research Record 1495</comment><publisher-name>Transportation Research Board</publisher-name><publisher-loc>Washington, DC, USA</publisher-loc><year>1995</year><fpage>28</fpage><lpage>35</lpage></element-citation></ref><ref id="b8-sensors-11-07420"><label>8.</label><element-citation publication-type="book"><person-group person-group-type="author"><name><surname>Sunkari</surname><given-names>S</given-names></name><name><surname>Messer</surname><given-names>C</given-names></name><name><surname>Charara</surname><given-names>H</given-names></name></person-group><source>Performance of Advance Warning for End of Green System for High-Speed Signalized Intersections</source><comment>Transportation Research Record 1925</comment><publisher-name>Transportation Research Board</publisher-name><publisher-loc>Washington, DC, USA</publisher-loc><year>2005</year><fpage>176</fpage><lpage>184</lpage></element-citation></ref><ref id="b9-sensors-11-07420"><label>9.</label><element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Carson</surname><given-names>J</given-names></name><name><surname>Mannering</surname><given-names>F</given-names></name></person-group><article-title>The effect of ice warning signs on ice-accident frequencies and severities</article-title><source>Accid. Anal. Prev</source><year>2001</year><volume>33</volume><fpage>99</fpage><lpage>109</lpage><pub-id pub-id-type="pmid">11189127</pub-id></element-citation></ref><ref id="b10-sensors-11-07420"><label>10.</label><element-citation publication-type="book"><person-group person-group-type="author"><name><surname>Elvik</surname><given-names>R</given-names></name><name><surname>Christensen</surname><given-names>P</given-names></name><name><surname>Amundsen</surname><given-names>A</given-names></name></person-group><source>Speed and Road Accidents, an Evaluation of the Power Model</source><comment>TØI Report 740</comment><publisher-name>Institute of Transport Economics TOI</publisher-name><publisher-loc>Oslo, Norway</publisher-loc><year>2004</year></element-citation></ref><ref id="b11-sensors-11-07420"><label>11.</label><element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Jang</surname><given-names>J</given-names></name><name><surname>Kim</surname><given-names>H</given-names></name></person-group><article-title>Advisory safety speed model using real-time vehicular data at SMART HIGHWAY</article-title><source>J. Korean Soc. Civil Eng</source><year>2010</year><volume>30</volume><fpage>443</fpage><lpage>451</lpage></element-citation></ref><ref id="b12-sensors-11-07420"><label>12.</label><element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Jang</surname><given-names>J</given-names></name><name><surname>Choi</surname><given-names>K</given-names></name><name><surname>Moon</surname><given-names>YJ</given-names></name></person-group><article-title>A development of driver’s safety information service model using point detectors at signalized intersection</article-title><source>J. Korean Soc. Transport</source><year>2009</year><volume>27</volume><fpage>113</fpage><lpage>124</lpage></element-citation></ref><ref id="b13-sensors-11-07420"><label>13.</label><element-citation publication-type="book"><source>Intelligent Transport Systems (ITS)—Vehicle Interface for Provisioning and Support of ITS Services—Part 1: General Information and Use Case Definition</source><comment>ISO/DTR 13185-1.3</comment><publisher-name>ISO</publisher-name><publisher-loc>Geneva, Switzerland</publisher-loc><year>2010</year></element-citation></ref><ref id="b14-sensors-11-07420"><label>14.</label><element-citation publication-type="confproc"><person-group person-group-type="author"><name><surname>Jang</surname><given-names>J</given-names></name><name><surname>Kim</surname><given-names>H</given-names></name><name><surname>Cho</surname><given-names>HB</given-names></name></person-group><article-title>Smart roadside server for driver assistance and safety warning: Framework and applications</article-title><conf-name>Proceedings of CUTE 2010: The 5th International Conference on Ubiquitous Information Technologies and Applications</conf-name><conf-loc>Sanya, Hainan, China</conf-loc><conf-date>16–18 December 2010</conf-date></element-citation></ref></ref-list></back><floats-group><fig id="f1-sensors-11-07420" position="float"><label>Figure 1.</label><caption><p>Roadway system and ITS technology.</p></caption><graphic xlink:href="sensors-11-07420f1"></graphic></fig><fig id="f2-sensors-11-07420" position="float"><label>Figure 2.</label><caption><p>Examples of infrastructure-based sensors and procedures at an intersection.</p></caption><graphic xlink:href="sensors-11-07420f2"></graphic></fig><fig id="f3-sensors-11-07420" position="float"><label>Figure 3.</label><caption><p>OBDII-based vehicle sensor.</p></caption><graphic xlink:href="sensors-11-07420f3"></graphic></fig><fig id="f4-sensors-11-07420" position="float"><label>Figure 4.</label><caption><p>Framework of smart road server and sensor system.</p></caption><graphic xlink:href="sensors-11-07420f4"></graphic></fig><fig id="f5-sensors-11-07420" position="float"><label>Figure 5.</label><caption><p>Red-light violation warning system at a signalized intersection.</p></caption><graphic xlink:href="sensors-11-07420f5"></graphic></fig><fig id="f6-sensors-11-07420" position="float"><label>Figure 6.</label><caption><p>Flowchart for the red-light violation warning model.</p></caption><graphic xlink:href="sensors-11-07420f6"></graphic></fig><fig id="f7-sensors-11-07420" position="float"><label>Figure 7.</label><caption><p>Signalized intersection test: red-light violation warning at signalized intersection.</p></caption><graphic xlink:href="sensors-11-07420f7"></graphic></fig><fig id="f8-sensors-11-07420" position="float"><label>Figure 8.</label><caption><p>Advisory speed provisioning in a highway system.</p></caption><graphic xlink:href="sensors-11-07420f8"></graphic></fig><fig id="f9-sensors-11-07420" position="float"><label>Figure 9.</label><caption><p>Simulation results. (<bold>a</bold>) Freeway-accident01 (Good traffic condition-accident-dry); (<bold>b</bold>) Freeway-accident11 (Good traffic condition-accident-wet); (<bold>c</bold>) Freeway-accident21 (Good traffic condition-accident-ice).</p></caption><graphic xlink:href="sensors-11-07420f9a"></graphic><graphic xlink:href="sensors-11-07420f9b"></graphic></fig><fig id="f10-sensors-11-07420" position="float"><label>Figure 10.</label><caption><p>Example of a Telematics device with normal information.</p></caption><graphic xlink:href="sensors-11-07420f10"></graphic></fig><fig id="f11-sensors-11-07420" position="float"><label>Figure 11.</label><caption><p>Example of a Telematics device with advisory speed and ice surface information.</p></caption><graphic xlink:href="sensors-11-07420f11"></graphic></fig><table-wrap id="t1-sensors-11-07420" position="float"><label>Table 1.</label><caption><p>Simulation input data.</p></caption><table frame="box" rules="all"><thead><tr><th align="left" valign="middle" rowspan="1" colspan="1"><bold>Categories</bold></th><th colspan="2" align="center" valign="middle" rowspan="1"><bold>Detailed Description</bold></th></tr></thead><tbody><tr><td align="left" valign="middle" rowspan="3" colspan="1">Traffic conditions</td><td align="left" valign="middle" rowspan="1" colspan="1">Input volume (vehicles/h)</td><td align="left" valign="middle" rowspan="1" colspan="1">100, 200, 300, 400, 500, 600, 700, 800, 900, 1,000, 1,100, 1,200, 1,300, 1,400, 1,500 (Total of 15 cases)</td></tr><tr><td align="left" valign="middle" rowspan="1" colspan="1">Turning rates</td><td align="left" valign="middle" rowspan="1" colspan="1">Left turn-through-Right turn: 15%–70%–15%</td></tr><tr><td align="left" valign="middle" rowspan="1" colspan="1">Classification</td><td align="left" valign="middle" rowspan="1" colspan="1">Passenger cars: 90%, other vehicles: 10%</td></tr><tr><td align="left" valign="middle" rowspan="3" colspan="1">Road conditions</td><td align="left" valign="middle" rowspan="1" colspan="1">Number of lanes</td><td align="left" valign="middle" rowspan="1" colspan="1">4 lanes × 4 lanes</td></tr><tr><td align="left" valign="middle" rowspan="1" colspan="1">Lane width</td><td align="left" valign="middle" rowspan="1" colspan="1">3.5 m</td></tr><tr><td align="left" valign="middle" rowspan="1" colspan="1">Operation of lanes</td><td align="left" valign="middle" rowspan="1" colspan="1">Lane 1: left turn only, lanes 2–3: through only, lane 4: right turn only</td></tr><tr><td align="left" valign="middle" rowspan="1" colspan="1">Signal control</td><td colspan="2" align="left" valign="middle" rowspan="1">Cycle: 120 s, Green time in each direction: 27 s, Yellow time: 3 s, Red time: 90 s, Phase: Simultaneously with Left + Through direction</td></tr><tr><td align="left" valign="middle" rowspan="1" colspan="1">Sensing point</td><td colspan="2" align="left" valign="middle" rowspan="1">A total of 50 point sensors in lanes 2 and 3.<break></break>First location is the stop line, with 5 m intervals for further sensors</td></tr></tbody></table></table-wrap><table-wrap id="t2-sensors-11-07420" position="float"><label>Table 2.</label><caption><p>Verification of the model results.</p></caption><table frame="box" rules="all"><thead><tr><th colspan="2" align="center" valign="middle" rowspan="2"><bold>Classification</bold></th><th colspan="2" align="center" valign="middle" rowspan="1"><bold>Real running vehicle status (no. of vehicles)(%) at simulation scenarios</bold></th><th align="center" valign="middle" rowspan="2" colspan="1"><bold>Total no. of vehicles (%)</bold></th></tr><tr><th align="center" valign="middle" rowspan="1" colspan="1"><bold>Red-light violation vehicles</bold></th><th align="center" valign="middle" rowspan="1" colspan="1"><bold>Non-red-light violation vehicles</bold></th></tr></thead><tbody><tr><td align="center" valign="middle" rowspan="2" colspan="1">Results of prediction (no. of vehicles in %) through suggested algorithms</td><td align="center" valign="middle" rowspan="1" colspan="1">Red-light violation vehicles</td><td align="center" valign="middle" content-type="background-color:#D9D9D9" rowspan="1" colspan="1"><bold>25.3 (4.6%)</bold></td><td align="center" valign="middle" rowspan="1" colspan="1">5.1 (0.9%)</td><td align="center" valign="middle" rowspan="1" colspan="1">30.4 (5.5%)</td></tr><tr><td align="center" valign="middle" rowspan="1" colspan="1">Non-red-light violation vehicles</td><td align="center" valign="middle" rowspan="1" colspan="1">3.3 (0.6%)</td><td align="center" valign="middle" content-type="background-color:#D9D9D9" rowspan="1" colspan="1"><bold>521.1 (93.9%)</bold></td><td align="center" valign="middle" rowspan="1" colspan="1">524.4 (94.5%)</td></tr><tr><td colspan="2" align="center" valign="middle" rowspan="1">Total no. of vehicles (%)</td><td align="center" valign="middle" content-type="background-color:#D9D9D9" rowspan="1" colspan="1"><bold>28.6 (5.1%)</bold></td><td align="center" valign="middle" rowspan="1" colspan="1">526.3 (94.9%)</td><td align="center" valign="middle" rowspan="1" colspan="1">554.9 (100%)</td></tr></tbody></table></table-wrap><table-wrap id="t3-sensors-11-07420" position="float"><label>Table 3.</label><caption><p>Simulation scenarios.</p></caption><table frame="box" rules="all"><thead><tr><th align="center" valign="middle" rowspan="1" colspan="1"><bold>Traffic condition</bold></th><th align="center" valign="middle" rowspan="1" colspan="1"><bold>Accident status</bold></th><th align="center" valign="middle" rowspan="1" colspan="1"><bold>Road surface status (<italic>f<sub>j</sub></italic> (<italic>k</italic>) )</bold></th><th align="center" valign="middle" rowspan="1" colspan="1"><bold>Scenario ID</bold></th></tr></thead><tbody><tr><td align="center" valign="middle" rowspan="6" colspan="1">LOS = C (Input Volume = 1,500 pcphpl)</td><td align="center" valign="middle" rowspan="3" colspan="1">without accident</td><td align="center" valign="middle" rowspan="1" colspan="1">Dry (f = 0.8)</td><td align="left" valign="middle" rowspan="1" colspan="1">Freeway-Basic01</td></tr><tr><td align="center" valign="middle" rowspan="1" colspan="1">Wet (f = 0.4)</td><td align="left" valign="middle" rowspan="1" colspan="1">Freeway-Basic11</td></tr><tr><td align="center" valign="middle" rowspan="1" colspan="1">Iced (f = 0.2)</td><td align="left" valign="middle" rowspan="1" colspan="1">Freeway-Basic21</td></tr><tr><td align="center" valign="middle" rowspan="3" colspan="1">with accident (accident time = 1,200–2,400 s)</td><td align="center" valign="middle" rowspan="1" colspan="1">Dry (f = 0.8)</td><td align="left" valign="middle" rowspan="1" colspan="1">Freeway-accident01</td></tr><tr><td align="center" valign="middle" rowspan="1" colspan="1">Wet (f = 0.4)</td><td align="left" valign="middle" rowspan="1" colspan="1">Freeway-accident11</td></tr><tr><td align="center" valign="middle" rowspan="1" colspan="1">Iced (f = 0.2)</td><td align="left" valign="middle" rowspan="1" colspan="1">Freeway-acciden21</td></tr><tr><td align="center" valign="middle" rowspan="6" colspan="1">LOS = F (Input Volume = 2,300 pcphpl)</td><td align="center" valign="middle" rowspan="3" colspan="1">without accident</td><td align="center" valign="middle" rowspan="1" colspan="1">Dry (f = 0.8)</td><td align="left" valign="middle" rowspan="1" colspan="1">Freeway-Basic02</td></tr><tr><td align="center" valign="middle" rowspan="1" colspan="1">Wet (f = 0.4)</td><td align="left" valign="middle" rowspan="1" colspan="1">Freeway-Basic12</td></tr><tr><td align="center" valign="middle" rowspan="1" colspan="1">Iced (f = 0.2)</td><td align="left" valign="middle" rowspan="1" colspan="1">Freeway-Basic22</td></tr><tr><td align="center" valign="middle" rowspan="3" colspan="1">with accident (accident time = 1,200–2,400 s)</td><td align="center" valign="middle" rowspan="1" colspan="1">Dry (f = 0.8)</td><td align="left" valign="middle" rowspan="1" colspan="1">Freeway-accident02</td></tr><tr><td align="center" valign="middle" rowspan="1" colspan="1">Wet (f = 0.4)</td><td align="left" valign="middle" rowspan="1" colspan="1">Freeway-accident12</td></tr><tr><td align="center" valign="middle" rowspan="1" colspan="1">Iced (f = 0.2)</td><td align="left" valign="middle" rowspan="1" colspan="1">Freeway-accident22</td></tr></tbody></table></table-wrap></floats-group></pmc></record>Pour manipuler ce document sous Unix (Dilib)
EXPLOR_STEP=$WICRI_ROOT/Ticri/CIDE/explor/TelematiV1/Data/Pmc/Corpus
HfdSelect -h $EXPLOR_STEP/biblio.hfd -nk 0005900 | SxmlIndent | more
Ou
HfdSelect -h $EXPLOR_AREA/Data/Pmc/Corpus/biblio.hfd -nk 0005900 | SxmlIndent | more
Pour mettre un lien sur cette page dans le réseau Wicri
{{Explor lien
|wiki= Ticri/CIDE
|area= TelematiV1
|flux= Pmc
|étape= Corpus
|type= RBID
|clé=
|texte=
}}
| This area was generated with Dilib version V0.6.31. |  |