lanes). Must assume vehicles are traveling at up to 200kph. Typical data transfers from OBU to RSU are less than 10kbytes. Since it is the average values from multiple vehicles that is of interest, occasional transaction failures can be tolerated. Vehicle anonymity is essential. Must not be possible to identify and track an individual vehicle as it moves around. Must not be possible for false data to be transferred (verify the vehicle as a trusted source). INFORMATION Summary Description A roadside device broadcasts relevant traffic information to all passing cars. Operation is similar to, but typical much more involved than, existing variable message on highways. The roadside device will use a directional antenna to communicate only with cars traveling in a given direction on a particular section of road. In general this is simple broadcast messages, but by using 11ai, the communication zone of a site could be effectively extended (such as with geo-casting). Summary Requirements Impact COLLECTION Summary Description Comparable to existing electronic toll collection systems with the additional need to support open road tolling. Open road tolling system do not use conventional toll booths but instead have the roadside units mounted on gantries over the roadway, collecting the tolls as the vehicles pass underneath while at normal highway speeds. Summary Requirements Impact (all other applications are pending) Requirements Performance Requirements This section lists the System requirements. The requirements will be categorized as follows: Constraint requirements specify predefined behaviors or characteristics of the System and its services. (ed note: do we need this?) Functional requirements specify actionable behaviors of System services. (ed note: this may or may not be necessary) Performance requirements specify quantifiable characteristics of System service operations. (ed note: this is felt to be the primary type of requirements that we need to specify) External interface requirements define system interfaces to other systems. (ed note: in the TGai context, this may consider interfaces to non-802.11 systems or it may be to other 802.11 amendments/functions) The for creating TGai is to facilitate the very rapid creation of new communications links. The question is defining exactly what this means and to establish specific values to be met. At present, it appears that there may be a range of values, from the longest time necessary to be
lanes). Must assume vehicles are traveling at up to 200kph. Typical data transfers from OBU to RSU are less than 10kbytes. Since it is the average values from multiple vehicles that is of interest, occasional transaction failures can be tolerated. Vehicle anonymity is essential. Must not be possible to identify and track an individual vehicle as it moves around. Must not be possible for false data to be transferred (verify the vehicle as a trusted source). INFORMATION Summary Description A roadside device broadcasts relevant traffic information to all passing cars. Operation is similar to, but typical much more involved than, existing variable message on highways. The roadside device will use a directional antenna to communicate only with cars traveling in a given direction on a particular section of road. In general this is simple broadcast messages, but by using 11ai, the communication zone of a site could be effectively extended (such as with geo-casting). Summary Requirements Impact COLLECTION Summary Description Comparable to existing electronic toll collection systems with the additional need to support open road tolling. Open road tolling system do not use conventional toll booths but instead have the roadside units mounted on gantries over the roadway, collecting the tolls as the vehicles pass underneath while at normal highway speeds. Summary Requirements Impact (all other applications are pending) Requirements Performance Requirements This section lists the System requirements. The requirements will be categorized as follows: Constraint requirements specify predefined behaviors or characteristics of the System and its services. (ed note: do we need this?) Functional requirements specify actionable behaviors of System services. (ed note: this may or may not be necessary) Performance requirements specify quantifiable characteristics of System service operations. (ed note: this is felt to be the primary type of requirements that we need to specify) External interface requirements define system interfaces to other systems. (ed note: in the TGai context, this may consider interfaces to non-802.11 systems or it may be to other 802.11 amendments/functions) The for creating TGai is to facilitate the very rapid creation of new communications links. The question is defining exactly what this means and to establish specific values to be met. At present, it appears that there may be a range of values, from the longest time necessary to be
11-11-0148-01-00ai-use-cases-for-tgai.docx