EAS device full absolute time same code structure that uses a true full absolute time protocol. This improvement will better guarantee absolute time from year to year as well as preventing bad BLU or WTE BLA CEA alerts.The solution is simple. Others have proposed similar ideas but my idea does more with elegant simplicity. The first same code message is transmitted three times as usual but after the same code message station ID of sender the year is added and the originator' senders call letters are added to the message in the same code string. This is to ensure proper absolute date when absolute date required is set on the decoder.
For the validation issues in general false alarms although an issue actually has not been really that serious a problem. Even the Hawaii type thing and pushing the wrong button has really not been a real serious problem simply because of the training people are required to receive and the fact the identical training on the identical presentation is often required on multiple occasions with at least one proficiency test along the way for each lesson and by and large the system does work with little down time and the fact these things generally are figured out before and can be and are corrected of errors before serious harm is done.
So then after the nnnn end of message same code string also then is repeated three times. A message with a validation code is then transmitted and a check sum validation code would be required for BLU and WTE and BLA CAE alerts and optionally used for others or for some others repeated with validation code after validation. The problem comes in certain alerts pertaining to particular people or particular places causing a false alarm which would be difficult to correct due to psychological reasons which make it difficult to correct any errors even if discovered and called out as well as the fact special bios logged logic level uniform utility prom packs are used that cannot be cleared or even canceled. So it is imperative to be extra careful versus general alarms for a particular readily identifiable hazard in an area say a tornado or a Hawaii type thing that gets corrected and an alert can easily be canceled if not deletable and updated or forced to expire. To solve this problem BLU WTE BLA CEA alerts a fact checking and validation process using a form that would need to be validated in addition to cap 1.2 validation which would require certain information fields to be filled out first then verified that all the facts pertaining to the issue and all fields are properly filled out. Then the logic and the facts would be verified and validated and then authenticated and then an authentication code would be issued as a measure to prevent false alarms by checking and verifying the fact before an alert can be created.
ABOUT THE ENTRANT
Name: Ellen Langsetmo
Type of entry: individual
Number of times previously entering contest:1
Ellen's favorite design and analysis
google sketchup for general presentation purposes like this site plus some other software including open source for my project invention things and technology and methuds.
Ellen's hobbies and activities:
Ellen is inspired by:
technology space moon landings nasa and making the world better.computer chip mmic and nanotech and quantum technoligy inspire me to.plus phonon resonance modulation demodulation detection sensor tech and phase two security scanner tech.
Software used for this entry:
html xml sketch up paint cad
Patent status: none