System and method for airport security employing identity validation

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application is a continuation-in-part of co-pending U.S. Utility application Ser. No. 10/242,150 which was filed Sep. 12, 2002, entitled SYSTEM AND METHOD FOR IDENTITY VALIDATION FOR A REGULATED TRANSACTION, which claims priority to U.S. Provisional Application Serial No. 60/323,475 entitled SYSTEM AND METHOD FOR IDENTITY VALIDATION and filed on Sep. 19, 2001, the entire disclosures of which are incorporated herein by reference.

TECHNICAL FIELD

[0002] The present invention relates to the field of systems and methods for identity verification and/or validation for airport security.

BACKGROUND OF THE INVENTION

[0003] Each day, thousands of people travel by air. As demonstrated by the recent hijacking of commercial aircraft and the tragic consequences resulting therefrom, there is a need for systems and methods that increase security measures related to airport(s). However, the flying public has generally been inconvenienced with increased security measures, for example, long lines at ticket counter(s) and/or security check point(s).

SUMMARY OF THE INVENTION

[0004] The following presents a simplified summary of the invention in order to provide a basic understanding of some aspects of the invention. This summary is not an extensive overview of the invention. It is not intended to identify key or critical elements of the invention or to delineate the scope of the invention. Its sole purpose is to present some concepts of the invention in a simplified form as a prelude to the more detailed description that is presented later.

[0005] The present invention relates to a system and method for airport security employing identity validation and/or verification. According to an aspect of the present invention, an airport security system having a first identification input component, a second identification input component, a security output component, and, optionally an identity transaction engine component is provided. The system facilitates airport security by having a person attempting to engage in air travel present identification on at least two occasions via the first identification input component and the second identification input component. The first identification input component initiates identification validation utilizing the identity transaction engine component. The second identification input component facilitates identification of the person so that security information obtained via the identity transaction engine component can be provided to the security output component.

[0006] The first identification input component receives information associated with a person attempting to engage in air travel and provides at least some of the information received to the identity transaction engine component. The first identification input component can receive information from input device(s), for example, a card reader, a magnetic card reader, keyboard, a touch screen device, a DNA fingerprint analyzer, a DNA profile analyzer, an optical character reader (OCR), an iris scanner, a retinal scanner, a thumb print reader, a digital camera, a pointing device, such as a mouse, a microphone, an IR remote control, a joystick, a game pad, a personal digital assistant (PDA), a pager, a text messaging device, a smart card reader or the like.

[0007] The identity transaction engine component can search data store(s) in order to validate identity of the person attempting to engage in air travel based, at least in part, upon information obtained from the first identification input component. For example, the identity transaction engine component can utilize the person's date of birth, name, Social Security Number, identifier (e.g., identification number), address, age, DNA fingerprint, DNA profile, ethnicity, citizenship, religious affiliation, political affiliation, biometric data, height, weight, health status, gender, registration status with Selective Service, history of conviction of felony and/or inclusion on list(s) of governmental agencies and/or private groups in order to determine whether the person should be permitted to engage in air travel.

[0008] The second identification input component receives at least some of the information associated with the person attempting to engage in air travel (e.g., from the person seeking to engage in air travel)., The second identification input component provides at least some of the information received to the identity transaction engine component. Thereafter, the identity transaction engine component provides security information associated with the person to the security output component.

[0009] The security output component provides security information associated with the person attempting to engage in air travel (e.g., to airport security personnel). The security information can be based, at least in part, upon information received from the identity transaction engine component and/or information received via the second identification input component. The security output component can include output device(s), for example, a telephone, a computer system, a light bar, an audible alarm, a touch screen device, a computer monitor, a television screen, a printer, a personal digital assistant, a wireless telephone display and/or speaker(s). The security information can provide information and/or instruction(s) to airport personnel, for example, to detain the person, conduct a thorough search of the person and/or person is to be presumed armed and dangerous.

[0010] The security output component can further forward information (e.g., data packet(s)) to other systems (not shown) to provide security information (e.g., including decision(s) of the identity transaction engine component). For example, these other systems can utilize the information provided (e.g., via data packet(s)) to take some predefined further action (e.g., remove passenger baggage from an aircraft).

[0011] The identity transaction engine component utilizes the information received from the first identification input component to search one or more data store(s) in order to validate the identity of the person attempting to engage in air travel and/or their suitability for engaging in air travel. The identity transaction engine component generates security information associated with the person based, at least in part, upon the information received from the first identification input component and information stored in the data store(s). For example, the identity transaction engine component can at least temporarily store and/or cache security information associated with a plurality of individuals attempting to engage in air travel.

[0012] Thus, the first identification input component can initiate generation of security information by the identity transaction engine component in a non-obtrusive manner since processing of the identity transaction engine component can occur while the person is engaging is other travel and/or non-travel-related activities (e.g., obtaining a boarding pass, purchasing food and/or beverage item(s), shopping, conversing with fellow traveler(s), walking in airport and/or waiting in an airport security queue). The identity transaction engine component can store, at least temporarily, the security information until the person presents himself/herself at the security checkpoint.

[0013] Thereafter, information associated with the person attempting to engage in air travel is received by the second identification input component. The information can be based upon the same, similar and/or different identification received by the first identification input component. The second identification input component can provide at least some of the information received to the identity transaction engine component (e.g., name of person). Based, at least in part, upon the information received from the second identification input component, the identity transaction component can provide security information associated with the person to the security output component (e.g., cleared, not cleared, high alert, processing, etc.).

[0014] Accordingly, security information can seamlessly be generated by the identity transaction engine component for a plurality of people seeking to engage in air travel. The security information can be generated with minimal intrusion for the prospective air travelers and facilitates increased airport security.

[0015] Another aspect of the present invention provides for an airport security system having a first identification input component, a second identification input component, a local identification component and a security output component. The system can further include an identity transaction engine component and/or data store(s).

[0016] The system facilitates airport security in a distributed environment. The local identification component can gather information associated with person(s) attempting to engage in air travel via the first identification input component. The local identification component can provide the information to an identity transaction engine component (not shown), for example, via a secure satellite link. The identity transaction engine component can then provide security information associated with the person(s) to the local identification component which can be provided to the security output component, at an appropriate time (e.g., when a person is participating in a security check). Thus, the local identification component initiates identification validation by the identity transaction engine component based, at least in part, upon information obtained by the first identification input component. The second identification input component facilitates identification of the person so that security information obtained via the identity transaction engine component can be provided to the security output component.

[0017] Yet another aspect of the present invention provides for a security system having at least one identification input component, a security component having an occupant data store, and, a security output component having output device(s). Optionally, the system can include an identity transaction engine component.

[0018] The system facilitates security by identifying person(s) located within a secured area. The system can store identification information associated with person(s) located within the secured area in the occupant data store. For example, the security component can determine security risk(s) associated with person(s) located within the secured area, change(s) associated with person(s) located within the secured area and/or logical inconsistency(ies) (e.g., person(s) exiting system without having information stored in the occupant data store and/or person(s) entering the system without having exited at an appropriate time).The following description and the annexed drawings set forth in detail certain illustrative aspects of the invention. These aspects are indicative, however, of but a few of the various ways in which the principles of the invention may be employed and the present invention is intended to include all such aspects and their equivalents. Other advantages and novel features of the invention will become apparent from the following detailed description of the invention when considered in conjunction with the drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

[0019]FIG. 1 is a schematic block diagram of an airport security system in accordance with an aspect of the present invention.

[0020]FIG. 2 is a schematic block diagram of an airport security system in accordance with an aspect of the present invention.

[0021]FIG. 3 is a schematic block diagram of an airport security system in accordance with an aspect of the present invention.

[0022]FIG. 4 is a schematic block diagram of an airport security system in accordance with an aspect of the present invention.

[0023]FIG. 5 is a diagram of an exemplary output device in accordance with an aspect of the present invention.

[0024]FIG. 6 is a diagram of an exemplary output device in accordance with an aspect of the present invention.

[0025]FIG. 7 is a diagram of an exemplary output device in accordance with an aspect of the present invention.

[0026]FIG. 8 is a diagram of an exemplary user interface in accordance with an aspect of the present invention.

[0027]FIG. 9 is block diagram of an output device in accordance with an aspect of the present invention.

[0028]FIG. 10 is a block diagram of a security system in accordance with an aspect of the present invention.

[0029]FIG. 11 is a block diagram of a secured area in accordance with an aspect of the present invention.

[0030]FIG. 12 is a flow chart illustrating a methodology for providing airport security in accordance with an aspect of the present invention.

[0031]FIG. 13 is a flow chart illustrating a methodology for providing airport security in accordance with an aspect of the present invention.

[0032]FIG. 14 is a flow chart illustrating a methodology for providing security in accordance with an aspect of the present invention.

DETAILED DESCRIPTION OF THE INVENTION

[0033] The present invention is now described with reference to the drawings, wherein like reference numerals are used to refer to like elements throughout. In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the present invention. It may be evident to one skilled in the art that the present invention may be practiced without these specific details. In other instances, well-known structures and devices are shown in block diagram form in order to facilitate description of the present invention.

[0034] As used in this application, the term “component” is intended to refer to a computer-related entity, either hardware, a combination of hardware and software, software, or software in execution. For example, a component may be, but is not limited to being, a process running on a processor, a processor, an object, an executable, a thread of execution, a program, and a computer. By way of illustration, both an application running on a server and the server can be a component.

[0035] Further, “security information” is intended to refer to security-related information associated with air traveler(s). For example, security information can include conclusory information such as cleared for air travel, not cleared for air travel, detain individual, etc. Additionally and/or alternatively, security information can include information associated with a security risk assessment, for example, a probability and/or likelihood that an air traveler is a security risk (e.g., numerical (75%) and/or range-based (e.g., low, medium, high)). Security information can further include identifying information associated with air traveler(s), for example, digitized fingerprint, digital facial image, digital voice print, etc.

[0036] Referring to FIG. 1, an airport security system <b>100</b> in accordance with an aspect of the present invention is illustrated. The system <b>100</b> includes a first identification input component <b>110</b>, a second identification input component <b>120</b> and a security output component <b>130</b>. Optionally, the system <b>100</b> can further include an identity transaction engine component <b>140</b>.

[0037] The system <b>100</b> facilitates airport security by having a person attempting to engage in air travel present identification on at least two occasions via the first identification input component <b>110</b> and the second identification input component <b>120</b>. The first identification input component <b>110</b> initiates identification validation utilizing an identity transaction engine component <b>140</b>. The second identification input component <b>120</b> facilitates identification of the person so that security information obtained via the identity transaction engine component <b>140</b> can be provided to the security output component <b>130</b>.

[0038] The first identification input component <b>110</b> receives information associated with a person attempting to engage in air travel and provides at least some of the information received to the identity transaction engine component <b>140</b>. The first identification input component <b>110</b> can receive information from input device(s) <b>150</b>, for example, a card reader, a magnetic card reader, keyboard, a touch screen device, a DNA fingerprint analyzer, a DNA profile analyzer, an optical character reader (OCR), an iris scanner, a retinal scanner, a thumb print reader, a digital camera, a pointing device, such as a mouse, a microphone, an IR remote control, a joystick, a game pad, a personal digital assistant (PDA), a pager, a text messaging device, a smart card reader, electronic ticket machine or the like. The first identification input component <b>110</b> can provide information to the identity transaction engine component <b>140</b>, for example, identifying the person attempting to engage in air travel.

[0039] In one example, the first identification input component <b>110</b> includes an electronic ticket (E-ticket) machine. E-ticket machine(s) generally require a form of identification (e.g., driver's license, identification card and/or credit card). Information associated with a person attempting to engage in air travel can be captured via the E-ticket machine and provided to the identity transaction engine component <b>140</b>. Thus, in the time period during which the person is traveling from the E-ticket machine to a security checkpoint, the identity transaction engine component <b>140</b> can search data store(s) and generate security information associated with the person.

[0040] In another example, the first identification input component <b>110</b> receives information from a boarding pass, a governmental identification card, a private identification card and/or an employment identification card.

[0041] Additionally and/or alternatively, input device(s) <b>150</b> can be located at curbside check-in, ticket counter check-in, an entrance to an airport facility, at customs clearing, security check point and/or at a gate.

[0042] The identity transaction engine component <b>140</b> can search data store(s) in order to validate identity of the person attempting to engage in air travel and/or suitability of the person to engage in air travel based, at least in part, upon information obtained from the first identification input component <b>110</b>. For example, the identity transaction engine component <b>140</b> can utilize the person's date of birth, name, Social Security Number, identifier (e.g., identification number), address, age, DNA fingerprint, DNA profile, ethnicity, citizenship, religious affiliation, political affiliation, biometric data, height, weight, health status, gender, registration status with Selective Service, history of conviction of felony and/or inclusion on list(s) of governmental agencies and/or private groups in order to determine whether the person should be permitted to engage in air travel.

[0043] The identity transaction engine component <b>140</b> can communicate with remote system(s) (not shown) (e.g., data store(s), database(s) and/or data storage system(s)). For example, the identity transaction engine component <b>140</b> can search the remote system(s) (not shown) based, at least in part, upon information associated with the person's identity (e.g., name, address, social security number, identification number, passport number, selective service number, voter identification number and/or date of birth) in order to validate and/or verify identity and possession of attribute(s) to engage in air travel.

[0044] The identity transaction engine component <b>140</b> can be coupled to the first identification input component <b>110</b> and/or the second identification input component <b>120</b> utilizing, for example, a telephone connection, a network connection, an extranet, an intranet, the Internet, a satellite link, a wireless communication link, a serial communication link and/or a parallel communication link. Information exchanged between the identity transaction engine component <b>140</b> and the first identification input component <b>110</b>, the second identification input component <b>120</b> and/or the security output component <b>130</b> can be performed in a variety of secure and/or encrypted manners.

[0045] The second identification input component <b>120</b> receives at least some of the information associated with the person attempting to engage in air travel. The second identification input component <b>120</b> can include input device(s) <b>160</b>, for example, a card reader, a magnetic card reader, keyboard, a touch screen device, a DNA fingerprint analyzer, a DNA profile analyzer, an optical character reader (OCR), an iris scanner, a retinal scanner, a thumb print reader, a digital camera, a pointing device, such as a mouse, a microphone, an IR remote control, a joystick, a game pad, a personal digital assistant (PDA), a pager, a text messaging device, a smart card reader, an electronic ticket machine or the like. In one example, the information received by the second identification input component <b>120</b> is from the same identification source as the first identification input component <b>110</b> (e.g., from a registered traveler identification card, a driver's license, passport, government identification card, employee identification card, boarding pass and/or temporary identification). In another example, the information received by the second identification input component <b>120</b> receives is from a different identification source as the first identification input component <b>110</b> (e.g., driver's license used by at first identification input component <b>110</b> and boarding pass used by second identification input component <b>120</b>).

[0046] The second identification input component <b>120</b> provides at least some of the information received to the identity transaction engine component <b>140</b>. Thereafter, the identity transaction engine component <b>140</b> provides security information associated with the person to the security output component <b>130</b>.

[0047] In one example, the second identification input component <b>120</b> includes input device(s) <b>160</b> physically located before a person places carry-on belonging(s) onto a conveyor belt. In another example, the second identification input component <b>120</b> includes input device(s) <b>160</b> physically located after a person places carry-on belonging(s) onto a conveyor belt, but before proceeding through a metal detector (e.g., second identification input component <b>120</b> physically located before person proceeds through metal detector and/or x-ray machine). In a third example, the second identification input component <b>120</b> includes input device(s) <b>160</b> physically located after a person has proceeded through a metal detector, but before the person retrieves the person's carry-on belonging(s). In yet a fourth example, the second identification input component <b>120</b> includes input device(s) <b>160</b> physically located after a person has retrieved the person's carry-on belonging(s).

[0048] The security output component <b>130</b> provides security information associated with the person attempting to engage in air travel (e.g., to airport security personnel) received from the identity transaction engine component. The security output component <b>130</b> can include output device(s) <b>170</b>, for example, a telephone, a computer system, a light bar, an audible alarm, a touch screen device, a computer monitor, a television screen, a printer, a personal digital assistant, a wireless telephone display and/or speaker(s). The security information can provide information and/or instruction(s) to airport personnel, for example, detain person, conduct thorough search of person and/or person is to be presumed armed and dangerous.

[0049] The security output component <b>130</b> can further forward information (e.g., data packet(s)) to other systems (not shown) to provide security information (e.g., including decision(s) of the identity transaction engine component <b>140</b>). For example, these other systems can utilize the information provided (e.g., via data packet(s)) to take some predefined further action (e.g., remove passenger baggage from an aircraft).

[0050] In one example, information associated with a person attempting to engage in air travel is received by the first identification input component <b>110</b>. For example, the information can be based, at least in part, upon a driver's license, identification card and/or passport input via a magnetic card reader at a ticket counter and/or an airport entrance. At least some of the information is then sent to the identity transaction engine component <b>140</b>.

[0051] The identity transaction engine component <b>140</b> utilizes the information received from the first identification input component <b>110</b> to search one or more data store(s) in order to validate identity of the person attempting to engage in air travel and/or their suitability for engaging in air travel. In one example, the identity transaction engine component <b>140</b> utilizes information retrieved from one or more data store(s) to further search yet other data store(s) <b>140</b> in order to validate identity of the person attempting to engage in air travel and/or their suitability for engaging in air travel. For example, specific information (e.g., social security number) can be derived from one data store, received by the identity transaction engine component <b>140</b> and utilized to search yet other data store(s) (e.g., based on enriched data).

[0052] The identity transaction engine component <b>140</b> generates security information associated with the person based, at least in part, upon the information received from the first identification input component <b>110</b> and information stored in the data store(s). For example, the identity transaction engine component <b>140</b> can at least temporarily store and/or cache security information associated with a plurality of individuals attempting to engage in air travel.

[0053] Thus, the first identification input component <b>110</b> can initiate generation of security information by the identity transaction engine component <b>140</b> in a non-obtrusive manner since processing of the identity transaction engine component <b>140</b> can occur while the person is engaging in other-travel and/or non-travel-related activities (e.g., obtaining a boarding pass, purchasing food and/or beverage item(s), shopping, conversing with fellow traveler(s), walking in airport and/or waiting in an airport security queue). The identity transaction engine component <b>140</b> can store, at least temporarily, the security information until the person presents himself/herself at a security checkpoint, gate, ticket counter, law enforcement center etc.

[0054] Thereafter, information associated with the person attempting to engage in air travel is received by the second identification input component <b>120</b>. The information can be based upon the same, similar and/or different identification received by the first identification input component <b>110</b>. For example, the second identification input component <b>120</b> can include a magnetic card reader be located in close proximity to a security metal detector. The second identification input component <b>120</b> can provide at least some of the information received to the identity transaction engine component <b>140</b> (e.g., name of person). Based, at least in part, upon the information received from the second identification input component <b>120</b>, the identity transaction component <b>140</b> can provide security information associated with the person to the security output component <b>130</b> (e.g., cleared, not cleared, high alert, processing, etc.).

[0055] Accordingly, security information can seamlessly be generated by the identity transaction engine component <b>140</b> for a plurality of people seeking to engage in air travel. The security information can be generated with minimal intrusion for prospective air travelers and facilitates increased airport security.

[0056] While the system <b>100</b> has been described with regard to airport security, the system <b>100</b> can be employed to facilitate security of other types of physical area(s). For example, the system <b>100</b> can be employed to secure an airport concourse, an airport terminal, an airport facility (e.g., tarmac and interior), an airport (e.g., physical grounds and interior), building, country, city, county, military base, embassy, cruise ship, hospital, power plant, nuclear facility, train, bridge and/or tunnel in accordance with an aspect of the present invention.

[0057] It is to be appreciated that the system <b>100</b>, the first identification input component <b>110</b>, the second identification input component <b>120</b>, the security output component <b>130</b> and/or the identity transaction engine component <b>140</b> can be component(s) as that term is defined herein.

[0058] Turning next to FIG. 2, an airport security system <b>200</b> in accordance with an aspect of the present invention is illustrated. The system <b>200</b> includes a first identification input component <b>210</b>, a second identification input component <b>220</b>, a local identification component <b>230</b> and a security output component <b>240</b>.

[0059] The system <b>200</b> facilitates airport security in a distributed environment. The local identification component can gather information associated with person(s) attempting to engage in air travel via the first identification input component <b>210</b>. The local identification component <b>230</b> can provide the information to an identity transaction engine component (not shown), for example, via a secure satellite link. The identity transaction engine component can then provide security information associated with the person(s) to the local identification component <b>230</b> which can be provided to the security output component <b>240</b>, at an appropriate time (e.g., when a person is participating in a security check). Thus, the local identification component <b>230</b> initiates identification validation by the identity transaction engine component based, at least in part, upon information obtained by the first identification input component <b>210</b>. The second identification input component <b>220</b> facilitates identification of the person so that security information obtained via the identity transaction engine component can be provided to the security output component.

[0060] The first identification input component <b>210</b> receives information associated with a person attempting to engage in air travel and provides at least some of the information received to the local identification component <b>230</b>. The first identification input component <b>210</b> can receive information from input device(s) <b>250</b>, for example, a card reader, a magnetic card reader, keyboard, a touch screen device, a DNA fingerprint analyzer, a DNA profile analyzer, an optical character reader (OCR), an iris scanner, a retinal scanner, a thumb print reader, a digital camera, a pointing device, such as a mouse, a microphone, an IR remote control, a joystick, a game pad, a personal digital assistant (PDA), a pager, a text messaging device, a smart card reader, an electronic ticket machine or the like. The first identification input component <b>210</b> can provide information to the local identification component <b>230</b>, for example, identifying the person attempting to engage in air travel.

[0061] The local identification component <b>230</b> can provide at least some of the information associated with person(s) attempting to engage in air travel to an identity transaction engine component (not shown). The identity transaction engine component can then provide security information associated with the person(s) to the local identification component <b>230</b> which can be provided to the security output component <b>240</b>, at an appropriate time (e.g., when a person is participating in a security check). Thus, the location identification system <b>230</b> can, at least temporarily, store security information associated with the person(s). This information can be stored, for example, in a security information data store <b>234</b>.

[0062] The local identification component <b>230</b> can be coupled to the first identification input component <b>210</b> and/or the second identification input <b>220</b> by, for example, a telephone connection, a network connection, an extranet, an intranet, the Internet, a satellite link, a wireless communication link, a serial communication link and/or a parallel communication link. Further, the location identification system <b>230</b> can be coupled to the identity transaction engine component by, for example, a telephone connection, a network connection, an extranet, an intranet, the Internet, a satellite link, a wireless communication link, a serial communication link and/or a parallel communication link. Information exchanged between the identity transaction engine component and the local identification component <b>230</b> can be performed in a variety of secure and/or encrypted manners.

[0063] The second identification input component <b>220</b> receives at least some of the information associated with the person attempting to engage in air travel. The second identification input component <b>220</b> can receive information from input device(s) <b>260</b>, for example, a card reader, a magnetic card reader, keyboard, a touch screen device, a DNA fingerprint analyzer, a DNA profile analyzer, an optical character reader (OCR), an iris scanner, a retinal scanner, a thumb print reader, a digital camera, a pointing device, such as a mouse, a microphone, an IR remote control, a joystick, a game pad, a personal digital assistant (PDA), a pager, a text messaging device, a smart card reader, an electronic ticket machine or the like. The second identification input component <b>220</b> provides at least some of the information received to the local identification component <b>230</b>. Thereafter, the local identification component <b>230</b> provides security information associated with the person received from the identity transaction engine component to the security output component <b>240</b> (e.g., from information stored in the security information data store <b>234</b>).

[0064] The security output component <b>240</b> provides security information associated with the person attempting to engage in air travel (e.g., to airport security personnel) received from the local identification component <b>230</b>. The security output component <b>240</b> can include output device(s) <b>270</b>, for example, a telephone, a computer system, a light bar, an audible alarm, a touch screen device, a computer monitor, a television screen, a printer, a personal digital assistant, a wireless telephone display and/or speaker(s).

[0065] It is to be appreciated that the system <b>200</b>, the first identification input component <b>210</b>, the second identification input component <b>220</b>, the local identification component <b>230</b> and/or the security output component <b>240</b> can be component(s) as that term is defined herein.

[0066] While the system <b>200</b> has been described with regard to airport security, the system <b>200</b> can be employed to facilitate security of other types of physical area(s). For example, the system <b>200</b> can be employed to secure an airport concourse, an airport terminal, an airport facility (e.g., tarmac and interior), an airport (e.g., physical grounds and interior), building, country, city, county, military base, embassy, cruise ship, hospital, power plant, nuclear facility, train, bridge and/or tunnel in accordance with an aspect of the present invention.

[0067] Next, referring to FIG. 3, an airport security system <b>300</b> in accordance with an aspect of the present invention is illustrated. The system <b>300</b> includes a first identification input component <b>210</b>, a second identification input component <b>220</b>, a location identification system <b>230</b>, a security output component <b>240</b> and an identity transaction engine component <b>280</b>.

[0068] The identity transaction engine component <b>280</b> can search data store(s) in order to validate identification of the person and/or suitability for air travel based, at least in part, upon information obtained from the local identification component <b>250</b>. For example, the identity transaction engine component <b>280</b> can utilize the person's date of birth, name, Social Security Number, identifier (e.g., identification number), address, age, DNA fingerprint, DNA profile, ethnicity, citizenship, religious affiliation, political affiliation, biometric data, height, weight, health status, gender, registration status with Selective Service, history of conviction of felony and/or inclusion on list(s) of governmental agencies and/or private groups in order to determine whether the person should be permitted to engage in air travel.

[0069] The identity transaction engine component <b>280</b> can communicate with remote system(s) (not shown) (e.g., data store(s), database(s) and/or data storage system(s)). For example, the identity transaction engine component <b>280</b> can search the remote system(s) (not shown) based, at least in part, upon information associated with the person's identity (e.g., name, address, social security number, identification number, passport number, selective service number, voter identification number and/or date of birth) in order to validate and/or verify identity and suitability/eligibility to engage in air travel.

[0070] For example, for a person seeking to board an aircraft, the identity transaction engine component can utilize the attribute(s) of a person's DNA fingerprint, name, date of birth and/or age in order to determine whether the person is on a governmental list of suspected terrorists, fleeing felons and/or fugitives from justice. A person on one of these governmental list(s) would be denied permission to board the aircraft.

[0071] In another example, attribute(s) of a person can be utilized to determine suitability/eligibility to engage in air travel. For example, legal authorities can identify attribute(s) (e.g., country of origin, height, weight, eye color etc.) of person(s) potentially ineligible for air travel (e.g., airport facilities watching for person city A weighing approximately 155 pounds). Person(s) who possess the attribute(s) would be denied permission to board the aircraft, at least temporarily, until a further security screening can be conducted.

[0072] The first identification input component <b>210</b> can further include a DNA fingerprint and/or profile analyzer. For example, a DNA sample (e.g., blood, hair and/or skin sample) can be acquired from a person desiring to engage in air travel. A DNA fingerprint and/or profile of the DNA sample can be sent by the DNA fingerprint and or profile analyzer to the identity transaction engine component <b>280</b>. The identity transaction engine component <b>280</b> can analyze the DNA sample and/or compare it to DNA fingerprint and/or profile information stored in data store(s). Thus, based at least in part upon the DNA sample, the identity transaction engine component <b>280</b> can determine whether the person is suitable to engage in air travel. The identity transaction engine component <b>280</b> can further facilitate determining whether a proposed regulated transaction is logical (e.g., a person boarding an aircraft in New York should not be simultaneously in Seattle).

[0073] It is to be appreciated that the system <b>300</b> and/or the identity transaction engine component <b>280</b> can be component(s) as that term is defined herein.

[0074] While the system <b>300</b> has been described with regard to airport security, the system <b>300</b> can be employed to facilitate security of other types of physical area(s). For example, the system <b>300</b> can be employed to secure an airport concourse, an airport terminal, an airport facility (e.g., tarmac and interior), an airport (e.g., physical grounds and interior), building, country, city, county, military base, embassy, cruise ship, hospital, power plant, nuclear facility, train, bridge and/or tunnel in accordance with an aspect of the present invention.

[0075] Turning next to FIG. 4, an airport security system <b>400</b> in accordance with an aspect of the present invention is illustrated. The system <b>400</b> includes a first identification input component <b>210</b>, a second identification input component <b>220</b>, a location identification system <b>230</b>, a security output component <b>240</b> and an identity transaction engine component <b>280</b>. The system <b>400</b> further includes a first data store <b>290</b>₁through an Nth data store <b>290</b>_N, N being an integer greater than or equal to one. The first data store <b>290</b>₁through the N^thdata store <b>290</b>_Ncan be referred to collectively as the data store(s) <b>290</b>.

[0076] The data store(s) <b>290</b> include information associated with identification of entities (e.g., people). For example, the data store(s) <b>290</b> can be governmental (Federal, state, regional and/or local) data store(s) related to, for example, the Social Security Administration, Drivers' license agencies (e.g., Bureau/Department of Motor Vehicles), state identification card issuing agencies, the Selective Service system, the military, voter registration, birth certificates issuing authorities, the Immigration and Naturalization Service, the Justice Department, the Office of Homeland Security, the Bureau of Alcohol, Tobacco and Firearms, the Federal Bureau of Investigation and/or the Central Intelligence Agency. The data store(s) <b>290</b> can also include private, non-governmental, data store(s) (e.g., commercial data such as credit record(s)) that can include, for example, a periodically updated copy of governmental data and/or a new set of data about an individual. Additionally, the data store(s) <b>290</b> can include DNA information (e.g., collected by governmental and/or private entities) and/or other biometric information. It is to be appreciated that any type of data store(s) suitable for carrying out the present invention can be employed and all such types of data store(s) are intended to fall within the scope of the hereto appended claims.

[0077] Information can be stored in the data store(s) <b>290</b> in a variety of format(s) including, but not limited to, hierarchical database(s) and/or relational database(s). Information can be stored in the data store(s) <b>290</b> in a variety of data structure(s) including, but not limited to, lists, arrays, databases and/or data cubes. For example, information stored in the data store(s) can be text (e.g., alphanumeric), graphical, audio, video and/or digitally stored DNA information. Information can be exchanged between the identification transaction engine component <b>280</b> and data store(s) <b>290</b> can be performed in a variety of secure and/or encrypted manners. For example, the identity transaction engine component <b>280</b> can be coupled to the data store(s) <b>290</b> utilizing a high-speed, secure Internet connection.

[0078] While the system <b>400</b> has been described with regard to airport security, the system <b>400</b> can be employed to facilitate security of other types of physical area(s). For example, the system <b>400</b> can be employed to secure an airport concourse, an airport terminal, an airport facility (e.g., tarmac and interior), an airport (e.g., physical grounds and interior), building, country, city, county, military base, embassy, cruise ship, hospital, power plant, nuclear facility, train, bridge and/or tunnel in accordance with an aspect of the present invention.

[0079] Next, referring to FIG. 5, an exemplary output device <b>500</b> in accordance with an aspect of the present invention is illustrated. The output device <b>500</b> includes a first indicator <b>510</b>₁through an Mth indicator <b>510</b>_M, M being an integer greater than or equal to one. The first indicator <b>510</b>₁through the Mth indicator <b>510</b>_Mcan be referred to collectively as the indicator(s) <b>510</b>.

[0080] The output device <b>500</b> facilitates communication of security information received, for example, from an identity transaction engine component <b>140</b>, identity transaction engine component <b>280</b> and/or a local identification component <b>230</b>. For example, the indicator(s) <b>510</b> can include word(s) and/or color(s) to facilitate communication of security information (e.g., red and/or alert to indicate a high-risk prospective air traveler).

[0081] Turning briefly to FIG. 6, an exemplary output device <b>600</b> in accordance with an aspect of the present invention illustrated. The output device <b>600</b> includes a first indicator <b>610</b>, a second indicator <b>620</b> and a third indicator <b>630</b>.

[0082] In this example, the first indicator <b>610</b> can be activated (e.g., green light) if security information (e.g., received from an identity transaction engine component <b>140</b>, identity transaction engine component <b>280</b> and/or a local identification component <b>230</b>) indicates that a person seeking to engage in air travel has been approved for air travel. The second indicator <b>620</b> can be activated (e.g., yellow light) if the security information is not yet complete. The third indicator <b>630</b> can be activated (e.g., red light) if the security information indicates that the person is high-risk and/or has not been approved for air travel.

[0083] Referring next to FIG. 7, an exemplary output device <b>700</b> in accordance with an aspect of the present invention is illustrated. The output device <b>700</b> includes a first indicator <b>710</b>, a second indicator <b>720</b>, a third indicator <b>730</b> and a fourth indicator <b>740</b>.

[0084] The first indicator <b>710</b> can be activated if a person seeking to engage in air travel has been “cleared” (e.g., approved) for air travel. The second indicator <b>720</b> can be activated if security information is not yet complete. The third indicator <b>730</b> can be activated if the person seeking to engage in air travel has not been cleared (e.g., not approved) for air travel. The fourth indicator <b>740</b> can be activated if the person seeking to engage in air travel is particularly high-risk.

[0085] Turning to FIG. 8, an exemplary user interface <b>800</b> in accordance with an aspect of the present invention is illustrated. The user interface <b>800</b> includes a first field <b>810</b>, a second field <b>820</b>, a third field <b>830</b>, a fourth field <b>840</b> and a fifth field <b>850</b>.

[0086] In this example, the first field <b>810</b> includes information associated with a traveler's name. The second field <b>820</b> includes the traveler's nationality. The third field <b>830</b> includes a probability of security risk. The fourth field <b>840</b> includes an image of the traveler. The fifth field <b>850</b> includes a security identifier (e.g., encoded identifier providing information associated with a security risk of the traveler).

[0087] It is to be appreciated that the exemplary user interface <b>800</b> is included merely for purposes of illustration and that user interface(s) displaying more or less information is intended to be encompassed by the appended claims.

[0088] While the output device <b>500</b>, the output device <b>600</b>, the output device <b>700</b> and the user interface <b>800</b> have been described with regard to airport security, the output device <b>500</b>, the output device <b>600</b>, the output device <b>700</b> and/or the user interface <b>800</b> can be employed to facilitate security of other types of physical area(s). For example, the output device <b>500</b>, the output device <b>600</b>, the output device <b>700</b> and/or the user interface <b>800</b> can be employed to secure an airport concourse, an airport terminal, an airport facility (e.g., tarmac and interior), an airport (e.g., physical grounds and interior), building, country, city, county, military base, embassy, cruise ship, hospital, power plant, nuclear facility, train, bridge and/or tunnel in accordance with an aspect of the present invention.

[0089] Referring to FIG. 9, an output device <b>900</b> in accordance with an aspect of the present invention is illustrated. In this example, the output device <b>900</b> can be a component of a security output component <b>240</b> and/or a security output component <b>130</b>. The output device includes means for detaining <b>920</b> physically located before a security check point <b>930</b>. Based, at least in part, upon security information received from a local security system <b>230</b> and/or an identity transaction engine component <b>140</b>, the means for detaining <b>920</b> can be activated to detain a person seeking to engage in air travel. For example, the means for detaining <b>920</b> can be moveable barriers which are deployed in the event that a high-risk person (e.g., potential terrorist) has been identified by an identity transaction engine component <b>140</b> and/or an identity transaction engine component <b>240</b>. The means for detaining <b>920</b> can include, for example, bulletproof glass, metal and/or other material(s) impenetrable by firearms and/or knives. Additionally and/or alternatively, the means for detaining <b>920</b> can include means for physically isolating the environment within the means for detaining <b>920</b>, for example, to protect other person(s) in the airport from substance(s) the person being detained may have on their person and/or to facilitate apprehension of the person being detained.

[0090] Referring next to FIG. 10, a security system <b>1000</b> in accordance with an aspect of the present invention is illustrated. The system <b>1000</b> includes at least one identification input component <b>1010</b> comprising input device(s) <b>1020</b>. The system <b>1000</b> further includes a security component <b>1030</b> having an occupant data store <b>1040</b>, and, a security output component <b>1050</b> having output device(s) <b>1060</b>. Optionally, the system <b>1000</b> can include an identity transaction engine component <b>1070</b>.

[0091] Turning briefly to FIG. 11, a “secured area” <b>1100</b> is defined as an area bounded by physical barrier(s) <b>1110</b> having entrance(s) <b>1120</b> to which access is monitored via identification input component(s) <b>1010</b>. For example, a secured area can include an airport concourse, an airport terminal, an airport facility (e.g., tarmac and interior), an airport (e.g., physical grounds and interior), building, country, city, county, military base, embassy, cruise ship, hospital, power plant, nuclear facility, train, bridge and/or tunnel.

[0092] Referring back to FIG. 10, the system <b>1000</b> facilitates security by identifying person(s) located within a secured area. The system <b>1000</b> can store identification information associated with person(s) located within the secured area in the occupant data store <b>1040</b>. For example, the security component <b>1030</b> can determine security risk(s) based upon security information associated with person(s) located within the secured area, change(s) associated with person(s) located within the secured area and/or logical inconsistency(ies) (e.g., person(s) exiting system <b>1000</b> without having information stored in the occupant data store <b>1040</b> and/or person(s) entering the system <b>1000</b> without having exited at an appropriate time).

[0093] The identification input component <b>1010</b> receives information associated with a person attempting to enter, attempting to exit, entering the secured area and/or attempting to exit the secured area and provides at least some of the information received to the security component <b>1030</b>. The identification input component <b>1010</b> can receive information from input device(s) <b>1020</b>, for example, a card reader, a magnetic card reader, keyboard, a touch screen device, a DNA fingerprint analyzer, a DNA profile analyzer, an optical character reader (OCR), an iris scanner, a retinal scanner, a thumb print reader, a digital camera, a pointing device, such as a mouse, a microphone, an IR remote control, a joystick, a game pad, a personal digital assistant (PDA), a pager, a text messaging device, a smart card reader, electronic ticket machine or the like. The identification input component <b>1010</b> can provide information to the security component <b>1030</b>, for example, identifying the person attempting to enter the secure area and/or entering the secured area.

[0094] The identity transaction engine component <b>1070</b> can search data store(s) in order to validate identity of the person attempting to enter the secured area, exit the secured area and/or suitability of the person to enter the secured area based, at least in part, upon information obtained from the security component <b>1030</b>. For example, the identity transaction engine component <b>1070</b> can utilize the person's date of birth, name, Social Security Number, identifier (e.g., identification number), address, age, DNA fingerprint, DNA profile, ethnicity, citizenship, religious affiliation, political affiliation, biometric data, height, weight, health status, gender, registration status with Selective Service, history of conviction of felony and/or inclusion on list(s) of governmental agencies and/or private groups in order to determine whether the person presents a security risk to the secured area.

[0095] The identity transaction engine component <b>1070</b> can communicate with remote system(s) (not shown) (e.g., data store(s), database(s) and/or data storage system(s)). For example, the identity transaction engine component <b>1070</b> can search the remote system(s) (not shown) based, at least in part, upon information associated with the person's identity (e.g., name, address, social security number, identification number, passport number, selective service number, voter identification number and/or date of birth) in order to validate and/or verify identity and possession of attribute(s) associated with security risk(s).

[0096] The identity transaction engine component <b>1070</b> can be coupled to the security component <b>1030</b> utilizing, for example, a telephone connection, a network connection, an extranet, an intranet, the Internet, a satellite link, a wireless communication link, a serial communication link and/or a parallel communication link. Information exchanged between the identity transaction engine component <b>1070</b> and the security component <b>1030</b> can be performed in a variety of secure and/or encrypted manners.

[0097] The security output component <b>1050</b> provides security risk information associated with the secured area. The security output component <b>1050</b> can include output device(s) <b>1060</b>, for example, a telephone, a computer system, a light bar, an audible alarm, a touch screen device, a computer monitor, a television screen, a printer, a personal digital assistant, a wireless telephone display and/or speaker(s). The security information can provide information and/or instruction(s) to personnel, for example, detain person, conduct thorough search of person(s) in the secured area and/or person(s) in and/or attempting to enter the secured area.

[0098] The security output component <b>1050</b> can further forward information (e.g., data packet(s)) to other systems (not shown) to provide security information (e.g., including decision(s) of the identity transaction engine component <b>1070</b>). For example, these other systems can utilize the information provided (e.g., via data packet(s)) to take some predefined further action (e.g., remove passenger baggage from an aircraft).

[0099] The identity transaction engine component <b>1070</b> utilizes the information received from the security component <b>1030</b> to search one or more data store(s) in order to validate identity of the person entering the secured area and/or attempting to enter the secured area. The identity transaction engine component <b>1070</b> generates security information associated with the person based, at least in part, upon the information received from the identification input component <b>1010</b> and information stored in the data store(s).

[0100] The security component <b>1030</b> thus receives information from the identification input component <b>1010</b> with regard to person(s) entering, attempting to enter, exiting and/or attempting to exit the secured area. The security component <b>1030</b> can store information associated with person(s) physically located within the secured area in the occupant data store <b>1040</b> received from the identify transaction engine component <b>1070</b>. In one example, the security component <b>1030</b> sends additional request(s) to the identity transaction engine component <b>1070</b> to determine whether security risk(s) associated with person(s) physically located within the secured area have changed. In another example, the security component <b>1030</b> receives update(s) (e.g., periodic) from the identity transaction engine component <b>1070</b> and determines whether security risk(s) associated with person(s) physically located within the secured area have changed.

[0101] Based, at least in part, upon information received from the identity transaction engine component <b>1070</b> and/or stored in the occupant data store <b>1040</b>, the security component <b>1030</b> determines a security risk associated with the secured area. In one example, the security risk is a Boolean value (e.g., secured or not secured). In another example, the security risk is a probability (e.g., percentage likelihood of security risk). Information associated with the security risk can be communicated to the security output component <b>1050</b>. The security component <b>1030</b> can utilize artificial intelligence technique(s) (e.g., Bayesian learning methods that perform analysis over alternative dependent structures and apply a score, Bayesian classifiers and other statistical classifiers, including decision tree learning methods, support vector machines, linear and non-linear regression and/or neural network) in order to determine the security risk associated with the secured area.

[0102] In one example, input device(s) <b>1020</b> are located at substantially all entrance/exit point(s) associated with an airport concourse. Each person entering and/or exiting the airport concourse is required to present identification to the system <b>1000</b> via the input device(s) <b>1020</b>. Thus, the security component <b>1030</b> is able store security information regarding person(s) physically located within the airport concourse.

[0103] In another example, input device(s) <b>1020</b> are located at substantially all entrance/exit point(s) associated with the interior of an airport. Each person entering and/or exiting the interior of the airport is required to present identification to the system <b>1000</b> via the input device(s) <b>1020</b>. The security component <b>1030</b> can thus track person(s) physically located within the interior of the airport. In a third example, input device(s) <b>1020</b> are located at substantially all entrance/exit point(s) associated with the interior of an airport and the airport tarmac. In yet a fourth example, input device(s) <b>1020</b> are located at substantially all entrance/exit point(s) associated with an airport.

[0104] It is to be appreciated that the system <b>1000</b>, the identification input component <b>1010</b>, the security component <b>1030</b>, the occupant data store <b>1040</b>, the security output component <b>1050</b> and/or the identity transaction engine component <b>1070</b> can be component(s) as that term is defined herein.

[0105] In view of the exemplary systems shown and described above, methodologies that may be implemented in accordance with the present invention, will be better appreciated with reference to the flow charts of FIGS. 12, 13 and <b>14</b>. While, for purposes of simplicity of explanation, the methodologies are shown and described as a series of blocks, it is to be understood and appreciated that the present invention is not limited by the order of the blocks, as some blocks may, in accordance with the present invention, occur in different orders and/or concurrently with other blocks from that shown and described herein. Moreover, not all illustrated blocks may be required to implement a methodology in accordance with the present invention. In addition, it will be appreciated that the exemplary methods and other methods according to the invention may be implemented in association with the identification validation system illustrated and described herein, as well as in association with other systems and apparatus not illustrated or described.

[0106] The invention may be described in the general context of computer-executable instructions, such as program modules, executed by one or more computers or other devices. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. Typically the functionality of the program modules may be combined or distributed as desired in various embodiments.

[0107] Turning to FIG. 12, a methodology <b>1200</b> for providing airport security in accordance with an aspect of the present invention is illustrated. At <b>1210</b>, information associated with a person seeking to engage in air travel is received (e.g., from a first identification input component <b>110</b> and/or a first identification input component <b>210</b>). At <b>1220</b>, the information is provided to an identity transaction search engine (e.g., by a first identification input component <b>110</b> and/or a local identification component <b>230</b>). At <b>1230</b>, security information is received from the identity transaction search engine (e.g., by a local identification component <b>230</b>). At <b>1240</b>, information associated with the person seeking to engage in air travel is received (e.g., from a second identification input component <b>120</b> and/or a second identification input component <b>220</b>). At <b>1250</b>, security information is provided (e.g., to a security output component <b>110</b> and/or a security output component <b>210</b>).

[0108] In one example, the security information comprises conclusory information such as cleared for air travel, not cleared for air travel, detain individual etc. In another example, the security information comprises information associated with a security risk assessment, for example, a probability and/or likelihood that an air traveler is a security risk (e.g., numerical (75%) and/or range-based (e.g., low, medium, high)). In yet another example, security information can further comprise identifying information associated with air traveler(s), for example, digitized fingerprint, digital facial image, digital voice print, etc.

[0109] Next, referring to FIG. 13, a methodology <b>1300</b> for providing airport security in accordance with an aspect of the present invention is illustrated. At <b>1310</b>, at least one data store is searched based, at least in part, upon information received regarding a person seeking to engage in air travel. At <b>1320</b>, a determination is made as to whether the person should be permitted to engage in air travel based, at least in part, upon the information received regarding the person and information obtained from the at least one data store. If the determination at <b>1320</b> is YES, at <b>1330</b>, the air travel is allowed and no further processing occurs. If the determination at <b>1330</b> is NO, at <b>1340</b>, the air travel is prohibited and no further processing occurs.

[0110] Turning next to FIG. 14, a methodology <b>1400</b> for providing security in accordance with an aspect of the present invention is illustrated. At <b>1410</b>, identification information associated with a person entering a secured area is received (e.g., from an identification input component <b>1010</b>). At <b>1420</b>, at least some of the identification information is provided to an identity transaction engine component. At <b>1430</b>, security information associated with the person entering the secured area is received from the identity transaction engine component. At <b>1440</b>, the security information is stored in an occupant data store (e.g., occupant data store <b>1040</b>). At <b>1050</b>, a security risk of the secured area is determined based, at least in part, upon security information stored in the occupant data store and/or security information received from the identity transaction engine component. For example, artificial intelligence technique(s) (e.g., Bayesian learning methods that perform analysis over alternative dependent structures and apply a score, Bayesian classifiers and other statistical classifiers, including decision tree learning methods, support vector machines, linear and non-linear regression and/or neural network) can be employed in order to determine the security risk associated with the secured area.

[0111] Although the invention has been shown and described with respect to certain illustrated aspects, it will be appreciated that equivalent alterations and modifications will occur to others skilled in the art upon the reading and understanding of this specification and the annexed drawings. In particular regard to the various functions performed by the above described components (assemblies, devices, circuits, systems, etc.), the terms (including a reference to a “means”) used to describe such components are intended to correspond, unless otherwise indicated, to any component which performs the specified function of the described component (e.g., that is functionally equivalent), even though not structurally equivalent to the disclosed structure, which performs the function in the herein illustrated exemplary aspects of the invention. In this regard, it will also be recognized that the invention includes a system as well as a computer-readable medium having computer-executable instructions for performing the acts and/or events of the various methods of the invention.

[0112] In addition, while a particular feature of the invention may have been disclosed with respect to only one of several implementations, such feature may be combined with one or more other features of the other implementations as may be desired and advantageous for any given or particular application. Furthermore, to the extent that the terms “includes”, “including”, “has”, “having”, and variants thereof are used in either the detailed description or the claims, these terms are intended to be inclusive in a manner similar to the term “comprising.”