Sponsored Content
Special Forums News, Links, Events and Announcements Complex Event Processing RSS News CEP in the 1960s: Air Traffic Control Post 302263657 by Linux Bot on Tuesday 2nd of December 2008 07:00:03 AM
Old 12-02-2008
CEP in the 1960s: Air Traffic Control

Tim Bass
12-02-2008 04:55 AM
Professor Luckham wrote about CEP and the future of global Air Traffic Control (ATC) in The Future Event Driven World: Global Air Traffic Management.** One of the first commercial applications of complex event processing was in the early 1960s in the field of commercial aviation, for example see the history of Air Traffic Control.
“Although experimental use of computers in ATC had begun as early as 1956, a determined drive to apply this technology began in the 1960s. To modernize the National Airspace System, the FAA developed complex computer systems that would replace the plastic markers for tracking aircraft. Instead, controllers viewed information sent by aircraft transponders to form alphanumeric symbols on a simulated three-dimensional radar screen. By automating some routine tasks, the system allowed controllers to focus on providing separation. These capabilities were introduced into the ATC system during the ten years that began in 1965.”
Applying a phrase like “complex event processing” to a subset of software on the market today certainly does not negate all the CEP applications that existed long before the phrase was coined or became popular.* Global ATC has been defined as a future use case for CEP.* Obviously, early ATC history, where processing complex events goes back as far as the early 1960s, is quite significant to our understanding of CEP/EP.

Event processing applications, including complex event processing applications, have been around for over 40 years. There has been four decades of both commercial and military event processing and CEP applications.* ATC is only one example of myriad historical commercial applications of complex event processing.

Note: This post was adapted from my post in the Earliest applications of commercial CEP.</p>

Source...
 
Traffic control index filter(8) 				       Linux					   Traffic control index filter(8)

NAME
tcindex - traffic control index filter SYNOPSIS
tc filter ... tcindex [ hash SIZE ] [ mask MASK ] [ shift SHIFT ] [ pass_on | fall_through ] [ classid CLASSID ] [ action ACTION_SPEC ] DESCRIPTION
This filter allows to match packets based on their tcindex field value, i.e. the combination of the DSCP and ECN fields as present in IPv4 and IPv6 headers. OPTIONS
action ACTION_SPEC Apply an action from the generic actions framework on matching packets. classid CLASSID Push matching packets into the class identified by CLASSID. hash SIZE Hash table size in entries to use. Defaults to 64. mask MASK An optional bitmask to binary AND to the packet's tcindex field before use. shift SHIFT The number of bits to right-shift a packet's tcindex value before use. If a mask has been set, masking is done before shifting. pass_on If this flag is set, failure to find a class for the resulting ID will make the filter fail and lead to the next filter being con- sulted. fall_through This is the opposite of pass_on and the default. The filter will classify the packet even if there is no class present for the resulting class ID. SEE ALSO
tc(8) iproute2 21 Oct 2015 Traffic control index filter(8)
All times are GMT -4. The time now is 01:45 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy