Method, system and support mechanism for object identification

FIELD OF INVENTION

0001The present invention relates to signal processing technology and more particularly to a method, system and support mechanism for object identification.

BACKGROUND OF THE INVENTION

0002Identification of objects and digitization of the identification data allows for control of the flow of said objects through a distribution system, and improves the visibility of objects in the system, to the software controlling the system itself and to remote human observers of the system.

0003Digitization of the location and identity of objects in the system allows for automatic routing of objects in the system to their correct destination via logical software control. It also allows for improved efficiency of the overall system by allowing the present location of an object to be known, and therefore it's likely time of arrival to be better estimated.

0004Automatic identification is a process which allows the identity of objects to be determined without human intervention. Automatic identification is highly desirable in such a system, because of the time saved by not having to rely on a human operator to manually identify an object.

0005One of the most efficient Automatic identification methods is Radio Frequency Identification (RFID), which uses radio waves to power a passive identification tag, so that said tag can reflect identification data stored on the tag back to the RFID interrogator. Identification using RFID is extremely fast, currently allowing for identification of up to 2400 RFID tags per second, by a single interrogator, under ideal conditions.

0006Another method of Automatic identification can be achieved by capturing an image of an object and using machine intelligence to identify the object based on the object's shape and other characteristics.

0007Manual identification is an identification process in which the human intervention is involved. Manual identification can be efficiently achieved by fixing a symbolic representation of identifying data to an object, in the form of a 1D or 2D barcode, and reading said barcode using methods such as laser scanning or image capture.

0008Reliable identification can be achieved by a trained human operator reading a printed description of an object, or merely identifying said object based on visual indicators such as the object's shape, colour size and other attributes, and then feeding the gathered identification data into an electronic system.

0009<figref idref="f0001">Figure 1</figref> illustrates a conventional RFID portal reader and an object to be identified. An object 6, which needs to be identified and is placed on a conveyer 4, moves through an RFID portal reader 2. The RFID portal reader 2 identifies the object 6, as long as interference, reflections or absorption of the identifying radio frequency signal do not prevent the identification from being successful. If the identification is not successful, the object 6 must stop, and a human operator is summoned to manually identify the object, using a handheld terminal to scan a barcode, or entering identification data into the handheld terminal.

0010All of the above means of identification have problems associated with their use. Although extremely fast, RFID is not a completely reliable means of identification. RFID may fail due to the sensitive nature of electromagnetic radiation at radio frequencies to interference, reflection and absorption of the radio waves. Image capture for Automatic identification requires a well illuminated subject, and either a fast microprocessor which consumes a large amount of power, or a long time to process the image, and extract a reliable identification. Manual identification of any means including barcode reading is undesirable because of the need for a human operator. Human visual identification is even more undesirable because of the time it takes for a human to feed the information into an electronic system, and because of the possibility of human error.

0011A system employing Automatic identification, such as RFID, can allow for a very high throughput of objects through the system, but to sustain this high throughput, some quality of identification must be compromised due to the inherent problems with this identification method. If the objects in the system have a high value associated with them, letting the quality of identification fall to maintain the throughput is undesirable, the value added by moving objects through the system quickly may be lost if there are any opportunities for high value items to get lost or stolen. The case where an automatic system of identification fails is known as an exception. The speed which this exception can be resolved so that the object can continue through the system is the limiting factor of the system, if quality is to be maintained.

0012Automatic identification systems also rely on the fact that all of the objects in the system have a functioning RFID tag attached. Only the largest corporations can mandate that the external suppliers into the system attach an RFID tag to an object before it enters the system, and applying RFID tags to all objects is currently not economically viable, because the RFID tag's value could be high compared to the object it is applied to.

0013The conventional Automatic identification systems have to employ a backup means of identification for handling exceptions, which usually takes the form of a handheld computer terminal which has one or more identification sensors fitted, such as a portable RFID reader, barcode scanner or image capture sensor. This handheld computer is a separate entity from the primary means of Automatic identification, and as such has its own capital cost, and cost of ownership associated, on top of the cost of the primary, and unreliable Automatic identification system.

0014Current implementations of RFID Portal readers are usually permanent structures fixed to a frame surrounding a door. If the business process is changed, requiring Automatic identification to occur in a different location, moving the Automatic identification system to a new location is a time consuming and expensive undertaking.

0015Accordingly there is a need for a combination of Manual and Automatic identification, and a method of efficiently combining Manual and Automatic identification to provide a fast means of accurate identification, while allowing the entire apparatus to be somewhat portable.

SUMMARY OF THE INVENTION

0016It is an object of the invention to provide a method and system that obviates or mitigates at least one of the disadvantages of existing systems.

0017In accordance with an aspect of the present invention, there is provided a system for object identification. The system includes a handheld terminal. The handheld terminal includes one or more than one sensor for data capture and identification of an object. The sensor is automatically or manually activated. The handheld terminal includes a rechargeable power storage for operation of the handheld terminal, and a housing including a grip hold by an operator. The system includes a fixture for securely supporting the terminal for a portal use. The fixture includes a shaft and a docking member on the shaft. The docking member includes a docking structure for removably connecting to the handheld terminal, and a docking connector for operably connecting an external device to the handheld terminal when the handheld terminal is connected to the docking structure. The fixture includes a support base for supporting the shaft and the handheld terminal on the docking structure.

0018In accordance with a further aspect of the present invention, there is provided a fixture for a handheld terminal having one or more than one sensor for data capture and object identification. The fixture includes a docking structure. The handheld terminal is docked onto the docking structure for a portal use. The fixture includes a docking connector for operably connecting an external device to the handheld terminal when the handheld terminal is connected to the docking structure.

0019In accordance with a further aspect of the present invention, there is provided a handheld terminal for data capture and identification. The terminal includes one or more than one sensor for data capture and identification of an object. The sensor is automatically or manually activated. The terminal includes a rechargeable power storage for operation of the terminal and a controller for controlling the function of the terminal. The terminal includes a first interface for manual input by an operator. An input from the first interface is capable of activating at least one of the one or more than one sensor. The terminal includes a second interface including a wired network interface, a wireless network interface or a combination thereof. An input from the second interface is capable of activating at least one of the one or more than one sensor. The terminal includes a housing having a grip and a connection member for removably connecting to a fixture for a portal use such that the power storage is chargeable through the connection member and a signal communication is implemented between the terminal and the fixture via the connection member.

0020In accordance with a further aspect of the present invention, there is provided a method for object identification and authentication by a system having a handheld terminal for data capture and identification and a fixture for removably connecting to the handheld terminal for a portal use. The handheld terminal includes one or more than one sensor for data capture and identification. The method includes in an idle state, polling detection mechanism to detect an object, and entering an object detect state when the object is detected. The method includes in the object detect state, automatically identifying the object by at least one of the one or more than one sensor in the handheld terminal docked on the fixture, entering an authentication state when the object is identified or entering an automatic identification fail state when the system fails to automatically identify the object. The method includes in the authentication state, authenticating the object and entering the idle state. The method includes in the automatic identification fail state, rejecting the object or removing the terminal from the fixture and entering a manual identification state. The method includes in the manual identification state, operating the handheld terminal by an operator without the fixture to manually identify the object, and entering the authentication state when the object is manually identified or rejecting the object when the system fails to manually identify the object.

0021The present invention provides reliable, fast identification of items at specific points as they travel through a system, by combining manual and automatic identification technologies.

0022This summary of the invention does not necessarily describe all features of the invention.

BRIEF DESCRIPTION OF THE DRAWINGS

0023These and other features of the invention will become more apparent from the following description in which reference is made to the appended drawings wherein: <figref idref="f0001">Figure 1</figref> is a schematic diagram of a conventional RFID portal reader and an item to be tracked;

0024<figref idref="f0002">Figure 2</figref> is a block diagram illustrating an example of an apparatus for manual and automatic object identification in accordance with an embodiment of the present invention;

0025<figref idref="f0003">Figure 3</figref> is a block diagram illustrating another example of the apparatus for manual and automatic object identification;

0026<figref idref="f0004">Figure 4</figref> is a block diagram illustrating a further example of the apparatus for manual and automatic object identification;

0027<figref idref="f0005">Figure 5</figref> is a schematic diagram illustrating an example of a protection circuit of <figref idref="f0004">Figure 4</figref>;

0028<figref idref="f0006">Figure 6</figref> is a diagram illustrating an example of the apparatus of <figref idref="f0002">Figure 2</figref>; <figref idref="f0007">Figure 7</figref> is a diagram illustrating an example of a handheld data capture and identification terminal, a docking member and a positioning member of <figref idref="f0002">Figure 2</figref>;

0029<figref idref="f0008">Figure 8</figref> is a block diagram illustrating an example of an object identification and authentication system in accordance with an embodiment of the present invention;

0030<figref idref="f0009">Figure 9</figref> is a block diagram illustrating another example of the object identification and authentication system;

0031<figref idref="f0010">Figure 10</figref> is a flowchart illustrating of an example of method for object identification and authentication in accordance with an embodiment of the present invention; and

0032<figref idref="f0011">Figure 11</figref> is a block diagram illustrating an example of a fixture in accordance with a further embodiment of the present invention.

DETAILED DESCRIPTION

0033<figref idref="f0002">Figure 2</figref> illustrates an example of an apparatus for manual and automatic identification in accordance with an embodiment of the present invention. The apparatus 100 of <figref idref="f0001">Figure 1</figref> includes a removable handheld data capture and identification terminal 102 and a fixture 104 for securely supporting the handheld terminal 102. The terminal 102 is removable docked onto the fixture 104. The terminal 102 is operated without intervention of the human operator. The terminal 102 is operable under the guidance of the human operator without the fixture 104 (stand alone) if required.

0034In the description, the terms "(removable) handheld data capture and identification terminal 102" and "(handheld) terminal 102" are used interchangeably. In the description, the terms "connect (connected)", "couple (coupled)", "engage (engaged)" may be used interchangeably, and these terms may indicate that two or more elements are in physical or electrical contact with each other. In the description, the terms "removable (removably)" and "releasable (releasably)" may be used interchangeably.

0035In the description below, the terms "automatic identification" and "automatically identifying" indicate that an object is identified without intervention of a human operator. In the description below, the terms "manual identification" and "manually identifying" indicate that the object is identified under the guidance of the human operator. In the description, the terms "human operator", "operator", and "observer" may be used interchangeably.

0036The handheld data capture and identification terminal 102 includes a sensor module 106 having one or more Automatic Identification and Data Capture (AIDC) sensors 170. The AIDC sensors 170 include, for example, an RFID reader 170A with antenna 171, an imaging sensor 170B, a (laser) barcode scanner 170C, a fingerprint scanner 170D, and a thermal image sensor 170E. The sensor module 106 may include any other AIDC sensors, for example, magnetic stripes, smart cards, sound recognition, or other biometrics. These sensors 170A-170E are largely placed at the front part of the terminal 102.

0037When the handheld data capture and identification terminal 102 is docked onto the fixture 104, the apparatus 100 is configured for automatic identification. When in the automatic identification configuration, the terminal 102 becomes the active component of the automatic identification apparatus so that objects are identified without intervention of the operator.

0038The operator may remove the handheld data capture and identification terminal 102 from the fixture 104 and operate the handheld terminal 102 to manually identify the objects by a plurality of methods, if required. The full-range of identification methods is available to the human operator (e.g., RFID 170A, barcode scanner 170C, image capture 170B, and manual identification followed by data entry). For example, if there is an obscured or read range limited RFID tag, the human operator may use the terminal 102 to expedite the reading of the RFID tag. If there is a barcode, the operator may operate the terminal 102 to scan the barcode. If there are no other means of identification, the operator enters the identity of the object into the terminal 102 through a user interface.

0039The fixture 104 includes a docking member 108, a shaft 110 connected to the docking member 108, a positioning member 112 for positioning the handheld data capture and identification terminal 102 on the docking member 108, and a support base 114. The terminal 102 is releasably docked onto the fixture 104 through the docking member 108.

0040The docking member 108 includes a docking station 116, a latch member 118 and a docking connector 120. The docking station 116 is located at the top of the shaft 110. The handheld data capture and identification terminal 102 is removably connected to the docking station 116 by the latch member 118. The latch member 118 includes, for example, one or more than one latch. The latch member 118 retains the terminal 102 onto the docking station 116 by engaging with the terminal 102 and the docking station 116.

0041The docking connector 120 is in two parts that mate with together when the handheld data capture and identification terminal 102 is docked on the fixture 104. One part of the docking connector 120 is coupled with the terminal 102, and the other is coupled with the fixture 104.

0042The docking connector 120 allows power and digital signals to enter the handheld data capture and identification terminal 102. The fixture 104 supplies power to the terminal 102 through the docking member 108, such that the terminal 102 becomes charged and systems comprising the terminal 102 are powered. The docking connector 120 also supports data communication between the terminal 102 and the fixture 104. The docking connector 120 allows data to enter the support base 114 from the terminal 102 and to enter the terminal 102 from the support base 114.

0043The positioning member 112 articulates the handheld data capture and identification terminal 102 such that when the handheld terminal 102 is engaged with the fixture 104, the AIDC sensors 170 are ideally positioned for the automatic identification, as described below.

0044The support base 114 includes a power input connector 122. The power input connector 122 communicates with the docking connector 120 via a power connection 124. The power input connector 122 may accept AC power, DC power or a combination thereof. The power input connector 122 allows an external AC/DC adaptor to be connected to the fixture 104. Alternatively, an AC/DC converter is provided internally to the fixture 104, such that AC power can be connected directly to the fixture 104. The power received by the power input connector 122 is routed through the fixture 104, and supplied to the docked terminal 102 via the docking connector 120.

0045In <figref idref="f0002">Figure 2</figref>, the power input connector 122 is located in the support base 114. However, in anther example, the power input connector 122 may be located in the fixture 104 other than the support base 114 or may be located in the handheld data capture and identification terminal 102.

0046In one example, the power connection 124 may be located outside the shaft 110. In another example, the power connection 124 may be located in the shaft 110 or the fixture 104.

0047In <figref idref="f0002">Figure 2</figref>, one power input connector 122 and one power connection 124 are shown. However, in a further example, the apparatus 100 may include more than one power input connector 124 and more than one power connection 124.

0048The support base 114 includes an Input/Output (I/O) connector 126 for connecting digital I/O devices (e.g., 402 of <figref idref="f0008">Figure 8</figref>). The I/O connector 126 communicates with the docking connector 120 via an I/O connection 128. Examples of the digital input devices connected to the I/O connector 126 are various forms of presence and proximity detection (e.g., 408 of <figref idref="f0008">Figure 8</figref>) such as ultrasonic sensors, pressure sensors, optical detectors, and infra-red, where the proximity/presence signal is converted into a digital signal. Either a digital "zero" or a digital "one" on the input may indicate the presence of the object. Examples of the digital output devices connected to the I/O connector 126 are various forms of control, such as conveyor belt on/off signal (e.g., 410 of <figref idref="f0008">Figure 8</figref>), external alarm on/off signal (e.g., 406 of <figref idref="f0008">Figure 8</figref>), and on/off signals for various coloured lights on a light stack (e.g., 404 of <figref idref="f0008">Figure 8</figref>). A digital "one" may indicate one condition of an external device, and a digital "zero" may indicate another condition (e.g., the opposite condition). The combination of the digital "zero" and "one" may indicate the other condition. The I/O connector 126 may communicate with a server (e.g., 420 of <figref idref="f0008">Figure 8</figref>) using a wired commutation interface.

0049The output connection of the I/O connector 126 or the I/O connection 128 may source up to a certain amount of current, such as 100mA or 1000mA, at a pre-determined voltage when enabled, such that external hardware can be powered. The input connection of the I/O connector 126 may include a wired network interface, a wireless network interface or a combination thereof.

0050In <figref idref="f0002">Figure 2</figref>, the I/O connector 126 is located in the support base 114. However, in anther example, the I/O connector 126 may be located in the fixture 104 other than the support base 114 or may be located in the handheld data capture and identification terminal 102.

0051In one example, the I/O connection 128 is located outside the shaft 110. In another example, the I/O connection 128 may be located in the shaft 110 or the fixture 104.

0052In <figref idref="f0002">Figure 2</figref>, one I/O connector 126 and one I/O connection 128 are shown. However, in a further example, the apparatus 100 may include more than one I/O connector 126 and more than one I/O connection 128.

0053The support base 114 includes a member for stabilizing the entire apparatus 100. The stabilizing member includes, for example, a weight 130 sufficient to prevent the entire apparatus 100 tipping over upon an external force being applied to the apparatus 100 or to prevent damage to the apparatus 100. For example, such force may be applied by a human operator walking into the fixture 104. The external force may be up to and including x Newtons which is a vector component and is a force proportional to the mass of the weight 130. The weight 130 allows a reasonable external force to be applied to the apparatus 100 while preventing the apparatus 100 to tip over or preventing damage to the apparatus 100. The weight 130 may be detachably connected to the support base 114 so that the fixture 104 is easily moved without the weight 130.

0054The base of the shaft 110 is fixed to the support base 114, and the shaft 110 protrudes from the support base 114. In <figref idref="f0002">Figure 2</figref>, the shaft 110 is illustrated separately from the support base 114. However, in another example, the shaft 110 and the support base 114 may form a single unit. In another example, the stabilization member may include a joint member for receiving or absorbing an external force applied to the shaft 110 or the handheld terminal 102 on the shaft 110 to maintain the apparatus 110. The base of the shaft 110 may be attached to the support base 114 via the joint member. The weight 130 may include the joint member.

0055The shaft 110 may include two separate shaft sections; a lower shaft 132 and an upper shaft 134, which allow the shaft 110 and therefore the active component at the top of the shaft 110, to be manipulated in various ways, such that the active component are arranged for the most success in automatically identifying suitable objects.

0056The positioning member 112 includes a shaft height control member 140 for altering the height of the shaft 110. For example, using the positioning member 112, one of the shaft members 132 and 134 slides inside the other shaft member in a telescoping manner.

0057The positioning member 112 includes a tilt/elevation controller 142 for titling/elevating the handheld data capture and identification terminal 102 around the axis of the shaft 110. The shaft 110 is articulated such that the elevation of the active component is adjustable by the tilt/elevation controller 142.

0058The positioning member 112 includes a rotation controller 144 for rotating the handheld data capture and identification terminal 102 around the axis of the shaft 110. The shaft 110 is articulated such that the active component is oriented around the axis of the shaft 110. The AIDC sensors 170 are pointed largely in any direction by the positioning member 112.

0059The handheld data capture and identification terminal 102 includes a human interface 150. The human interface 150 may include, but not limited to, a keypad (e.g., 321 of <figref idref="f0007">Figure 7</figref>), a touch-screen, a pen-type input device, a joystick, a trackball or combinations thereof. The keypad and the touch-screen allow an operator to manually enter alphanumeric data into the terminal 102. The human interface 150 may include any mechanism, such as a mechanical switching mechanism (e.g., 344 of <figref idref="f0007">Figure 7</figref>) through which the operator communicates with the terminal 102. The human interface 150 may include sound recognition through which an operator inputs command/instructions to operate the terminal 102. The human interface 150 may be used to activate one or more than one of the AIDC sensors 170. The human interface 150 may be used to trigger a detection event or an identification event for the one or more than one of the AIDC sensors. The human operator may manually input an object identification via the human interface 150.

0060The handheld data capture and identification terminal 102 includes I/O 152. Through the I/O 152, external devices are connectable to the terminal 102. The I/O 152 provides future expansion of the terminal's capabilities.

0061The handheld data capture and identification terminal 102 draws power from a power store (or storage) 154. The power store 154 includes, for example, but not limited to, a re-chargeable battery, and may be removable, or internal to the terminal 102. Power provided from the support base 114 is used to charge the power store 154 so that the terminal 102 draws power from the power store 154 and therefore continues to operate when the terminal 102 is separated from the fixture 104

0062The handheld data capture and identification terminal 102 includes an electronic display 156 for displaying information to the operator of the terminal 102. The touch-screen may be combined with the display 156.

0063The handheld data capture and identification terminal 102 includes a wireless network interface 158 with an antenna 160 through which the terminal 102 is capable of communicating data obtained by the sensors 170 (e.g., identification data, detection data) and other data entered into it to external systems, such as a server (e.g., 420 of <figref idref="f0008">Figure 8</figref>) on the network or receiving data/information from the external systems. The wireless network interface 158 may include, but not limited to, a wireless LAN interface, a narrowband interface, a Wi-Max interface, or combinations thereof. The wireless network interface 158 may include a short-range wireless interface. The short-range wireless interface may include, for example, but not limited to, Bluetooth^™, wireless USB or wireless zigbee^™.

0064In <figref idref="f0002">Figure 2</figref>, one wireless network interface 158 is shown. However, the handheld data capture and identification terminal 102 may include more than one wireless network interface 158.

0065A digital controller 162 is provided to control the various functions of the handheld data capture and identification terminal 102. The controller 162 allows data obtained by the AIDC sensors (e.g., identification data, detection data) to be communicated to the wireless network via the wireless network interface 158. The controller 162 is also capable of providing control signals to the support base 114 via the I/O connection 128 based on the identification result. The controller 162 has access to a memory 164, so that identification data is stored in the event that the terminal 102 cannot access the wireless network and said identification data is transmitted when the network becomes available. The controller 162 communicates with one or more than one components of the handheld data capture and identification terminal 102, such as human interface 150, the I/O 152, the power store 154, and the network interface 158, in addition to the sensor module 106 and the memory 162. The memory 164 may include, but not limited to, a non-volatile memory, a volatile memory, or a combination thereof.

0066The sensor module 106 captures data and identifies objects based on the control of the controller 162. For the object identification, the controller 162 may control the sensor module 106 based on instructions from external systems (e.g., 402, 420 of <figref idref="f0008">Figure 8</figref>) or manual inputs (e.g., 150), its embedded instructions, or combination thereof. The AIDC sensors 170 may be automatically activated. The AIDC sensors may be manually activated when the handheld data capture and identification terminal 102 is removed from the fixture 104, if required. An identification event may be automatically triggered or manually triggered if required.

0067In an example, the identification event is automatically triggered based on data captured by the handheld data capture and identification terminal 102. In anther example, the identification event is automatically triggered by an external input received through the I/O connector 126 or a wireless communication through the wireless network interface 158. For example, the image sensor 170B may automatically capture data for detecting an object, and the RFID reader 170B or the barcode scanner 170C then automatically identifies the detected object.

0068In a further example, the operator may operate the RFID reader 170A, the barcode scanner 170C or a combination thereof, properly after removing the terminal 102 from the fixture 104. In a further example, the operator may manually input data associated with the object (e.g., identification data) to the terminal 102.

0069The data associated with the object (e.g., identification data), which is manually or automatically obtained, is transferred to external devices/systems (e.g., 420 of <figref idref="f0008">Figure 8</figref>). The external devices/systems may provide feedback to the handheld data capture and identification terminal 102.

0070The objects, which are to be identified, may be on a conveyor belt, or may be transported on a vehicle such as a forklift truck or hand jack, or may be carried by a human operator. Using the apparatus 100 of <figref idref="f0002">Figure 2</figref>, the objects are allowed to travel through a system having the apparatus 100 as quickly as possible by implementing automatic identification where possible, and/or implementing manual identification if required. The manual identification is achievable with the minimum disruption to the flow of the object, while maintaining a high accuracy of identification of said objects.

0071The apparatus 100 may include a device outputting signals sensible by the human operator (e.g., visible light device, audio device). The visual light device and the audio device may be located in the handheld data capture and identification terminal 102, the fixture 104 or a combination thereof. The visual light device and the audio device may be controlled by the controller 162. The visible light device and the audio device may be used to indicate the state/mode of the terminal 102, the apparatus 100 or a combination thereof. The operator may remove the terminal 102 from the fixture 104 based on the output from the visible light device or the audio device.

0072<figref idref="f0003">Figure 3</figref> illustrates another example of the apparatus for manual and automatic identification. The apparatus 100A of <figref idref="f0003">Figure 3</figref> includes a fixture 104A having a support base 114A. The fixture 104A is similar to the fixture 104 of <figref idref="f0002">Figure 2</figref>. The support base 114A includes a stabilization member having a connector 180 for more or less permanently attaching the fixture 104A to a floor, a wall or a ceiling. The support base 114A may be fixed to a vehicle (e.g., forklift truck) by the connector 180. The connector 180 may include, but not limited to, one or more holes for the use of one or more bolts or rivets. The weight 130 of <figref idref="f0002">Figure 2</figref> is not illustrated in <figref idref="f0003">Figure 3</figref>, since an external force may be not applied to a motorized vehicle (e.g., a forklift truck) colliding with the fixture 104A. However, the support base 114A may include the weight 130.

0073<figref idref="f0004">Figure 4</figref> illustrates a further example of the apparatus for manual and automatic identification. The apparatus 100B of <figref idref="f0004">Figure 4</figref> includes a fixture 104B having a support base 114B. The fixture 104B is similar to the fixture 104 of <figref idref="f0002">Figure 2</figref>. The support base 114B includes a protection circuit 182 for preventing damage to the connected handheld data capture and identification terminal 102, upon a fault condition such as electro-static discharge, over voltage, over current, etc. The connection from the protection circuit 182 is routed through the fixture 104B and supplied to the docked terminal 102 via the docking connector 120. The support base 114A of <figref idref="f0003">Figure 3</figref> may include the protection circuit 182 of <figref idref="f0004">Figure 4</figref>.

0074In <figref idref="f0004">Figure 4</figref>, the protection circuit 182 is connected to the I/O connection 128. However, in another example, the protection circuit 182 may be connected to the power connection 124. In a further example, the protection circuit 182 is provided to both of the I/O connection 128 and the power connection 124. In a further example, a connection between the protection circuit 182 and the docking connector 120 may be provided separately from the I/O connection 128. In a further example, the apparatus 100B may include more than one protection circuit 182. In a further example, a plurality of protection circuits 182 are provided to one or more than one power connection 124 and one or more than one I/O connection 128. In a further example, the protection circuit 182 may be located in the fixture 104B other than the support base 114B or the handheld data capture and identification terminal 102.

0075Those of skill in the art will understand that the representation of the terminal 102 and the fixtures 104, 104A and 104B of <figref idref="f0002 f0003 f0004">Figures 2-4</figref> is schematic only, and the actual configuration of the terminal 102 and the fixture may take on a variety of configurations.

0076<figref idref="f0005">Figure 5</figref> illustrates an example of the protection circuit 182 of <figref idref="f0004">Figure 4</figref>. "601" and "602" represents the positive and negative terminals of the I/O port. Static protection diode 603 is a fast diode which protects the system against electrostatic discharge. Zenner Diode 604 has a high power rating, and will allow current to flow to ground if a voltage above its breakdown voltage is applied between the terminals 601 and 602, providing over voltage protection. Resistor 605 sets the I/O ports default condition. Comparator 607 compares the input from a potential divider 606 to a reference input 610, only producing a high output when the voltage between the terminals 601 and 602 is above a predetermined value. If the voltage between the terminals 601 and 602 drops below a pre determined value, the output of the comparator 607 will become low. AND gate 608 allows current to flow through FET 609 when both of its inputs are positive. Out enable signal 611 is positive, as well as the output of the comparator 607 for the FET 609 to be enabled. If too much current is drawn from the terminals 601 and 602, the resulting voltage drop will be detected by the comparator 607, and the FET 609 will be turned off, providing over current protection. Capacitor 612 provides a low impedance current source, to smooth any rapidly increasing current demands. Resistor 613 provides input current protection, and flip-flop 614 synchronizes an input present on its D input to the system clock, providing protection from meta-stability. More than one flip-flop may be cascaded to provide further protection from meta-stability. The output 615 of the flip-flop 614 is the post protection input to the system.

0077<figref idref="f0006">Figure 6</figref> illustrates an example of the apparatus 100 of <figref idref="f0002">Figure 2</figref>. In <figref idref="f0006">Figure 6</figref>, "301" represents a weight and corresponds to 130 of <figref idref="f0002">Figure 2</figref>; "302" represents a support base and corresponds to 114 of <figref idref="f0002">Figure 2</figref>; "303" represents a lower shaft and corresponds to 132 of <figref idref="f0002">Figure 2</figref>; "304" represents a shaft height control and corresponds to 140 of <figref idref="f0002">Figure 2</figref>; "307" represents an upper shaft and corresponds to 134 of <figref idref="f0002">Figure 2</figref>, "309" represents a rotation/tilting member and corresponds to 142 and 144 of <figref idref="f0002">Figure 2</figref>; "310" represents a docking station and corresponds to 116 of <figref idref="f0002">Figure 2</figref>; "311" represents a handheld data capture and identification terminal and corresponds to 102 of <figref idref="f0002">Figure 2</figref>; "322" and "323" represent the power connection and I/O connection, and correspond to 124 and 128 of <figref idref="f0002">Figure 2</figref>; "325" represents digital I/O devices and corresponds to 126 of <figref idref="f0002">Figure 2</figref>; "326" represents a power input connector and corresponds to 122 of <figref idref="f0002">Figure 2</figref>; and "330" represents a fixture and corresponds to 104 of <figref idref="f0002">Figure 2</figref>.

0078The handheld data capture and identification terminal 311 is docked onto the docking station 310 and is securely connected to the fixture 330. The docking station 310 is formed such that the handheld data capture and identification terminal 311 fits inside, with the AIDC sensors (e.g., 170 of <figref idref="f0002">Figure 2</figref>) protruding from the front, un-obstructed. The top of the shaft is fitted into the docking station 310. The shaft height control member 304 is arranged such that the upper shaft 307 is allowed to slide inside the lower shaft 303 in a telescoping manner, hence altering the length of the fixture 330. The shaft height control member 304 may employ, for example, but not limited to, a pneumatic mechanism, or an oil-damped mechanism to provide a tactile feedback to the operator. The shaft height control member 304 may employ, but not limited to, those disclosed in <patcit id="pcit0001" dnum="US7009840B"><text>US Patent Nos. 7,009,840</text></patcit>, <patcit id="pcit0002" dnum="US6056251A"><text>6,056,251 </text></patcit>and <patcit id="pcit0003" dnum="US4684098A"><text>4,684,098</text></patcit>, which are herein incorporated by reference.

0079In <figref idref="f0006">Figure 6</figref>, the lower shaft 303 and the support base 302 are integrated and form a single unit component. In <figref idref="f0006">Figure 6</figref>, the power connection 322 and the I/O connection 323 are routed through the inside of the lower shaft 303 and the upper shaft 307.

0080<figref idref="f0007">Figure 7</figref> illustrates an example of the handheld data capture and identification terminal, the docking member and the positioning member of <figref idref="f0006">Figure 6</figref>. In <figref idref="f0007">Figure 7</figref>, "315" represents an image sensor and corresponds to 170B of <figref idref="f0002">Figure 2</figref>; "319" represents a re-chargeable battery and corresponds to 154 of <figref idref="f0002">Figure 2</figref>; "321" represents a keypad and corresponds to 150 of <figref idref="f0002">Figure 2</figref>; "327" represents a docking connector and corresponds to 120 of <figref idref="f0002">Figure 2</figref>; "328" represents a display and corresponds to 156 of <figref idref="f0002">Figure 2</figref>; "329" represents one or more than one latch and corresponds to 118 of <figref idref="f0002">Figure 2</figref>; "332" represents an RFID antenna and corresponds to 171 of <figref idref="f0002">Figure 2</figref>; "334" represents a wireless network antenna and corresponds to 160 of <figref idref="f0002">Figure 2</figref>; "336" represents a hinge and corresponds to 142 of <figref idref="f0002">Figure 2</figref>; and "340" and "342" represent a rotation support and a pin, respectively, and correspond to 144 of <figref idref="f0002">Figure 2</figref>.

0081In the description, the terms "(removable) handheld data capture and identification terminal 311" and "(handheld) terminal 311" are used interchangeably.

0082The housing of the handheld data capture and identification terminal 311 includes a connection member connectable to the one or more than one latch 329 and the docking connector 327. The latch 329 retains the terminal 311 inside the docking station 310, however, allows the terminal 311 to be easily and quickly removed when required. While the terminal 311 is fitted inside the docking station 310, the docking connector 327 makes contact with the terminal 311 such that power and digital connections are maintained.

0083The hinge 336 is located at the point where the docking station 310 connects to the upper shaft 307. The hinge 336 is pivotally connected to the docking station 310. The docking station 310 moves in a direction 338 via the hinge 336. The bottom of the docking station 310 includes a connector to be connected to the hinge 336. The rotation support 340 is connected to the docking station 310. The rotation support 340 rotates around the pin 342 that is fixed to the upper shaft 307. Thus, the rotation support 340 rotates the docking station 310 around the axis of the shaft (or pin).

0084The housing of the handheld data capture and identification terminal 311 includes an upper part and a lower part. The user interface (e.g., display, keypads etc) is in the upper part. The lower part has an opening that forms a pistol grip 346. The pistol grip 346 is hold in a hand of the human operator when the operator manually operates the terminal 311.

0085The shape of the grip 346 is not limited to that of <figref idref="f0006 f0007">Figures 6-7</figref>. In another example, the housing of the handheld data capture and identification terminal 311 may have a handle grip hold by the operator.

0086The handheld data capture and identification terminal 311 includes one or more than one manual activator for causing one or more than one of the AIDC sensors (e.g., 170A-170E of <figref idref="f0002">Figure 2</figref>) to become active. The activator may be, for example, but not limited to, a trigger 344 on the pistol grip 346. One or more keys on the keypad 321 may trigger an identification event. These user interfaces may be operable regardless whether the terminal 311 is docked on the docking station 310.

0087<figref idref="f0008">Figure 8</figref> illustrates an example of an object identification and authentication system in accordance with an embodiment of the present invention. The system 400 of <figref idref="f0008">Figure 8</figref> includes an apparatus for manual and automatic identification, labeled as 100C. The apparatus 100C may be the same or similar to the apparatus 100 of <figref idref="f0002">Figure 2</figref>, the apparatus 100A of <figref idref="f0003">Figure 3</figref> or the apparatus 100B of <figref idref="f0004">Figure 4</figref>. The apparatus 100C includes the handheld data capture and identification terminal 102, and a fixture having a support base 114C. The fixture for the apparatus 100C may be the same or similar to the fixture 104 of <figref idref="f0002">Figure 2</figref>, the fixture 104A of <figref idref="f0003">Figure 3</figref> or the fixture 104B of <figref idref="f0004">Figure 4</figref>. The support base 114C may be the same or similar to the support base 114 of <figref idref="f0002">Figure 2</figref>, the support base 114A of <figref idref="f0003">Figure 3</figref> or the support base 114B of <figref idref="f0004">Figure 4</figref>.

0088In <figref idref="f0008">Figure 8</figref>, the I/O 126, the wireless I/F 158, the controller 162, the AIDC sensors 170 are schematically shown. However, the apparatus 100C may include other components as shown in <figref idref="f0002">Figures 2</figref>, <figref idref="f0003">3</figref> and <figref idref="f0004">4</figref>.

0089The system 400 includes one or more than one I/O device 402. The I/O device 402 communicates with the I/O connector 126 via one or more than one wired communications link. The I/O device 402 may communicate with the I/O connector 126 via one or more than one wireless communications link, one or more than one wired communications link, or combinations thereof. The I/O device 402 includes, for example, but not limited to, one or more than one visual indicator 404, one or more than one audio indicator 406, one or more than one external proximity detector 408, one or more than one external device 410, or combinations thereof.

0090The visual indicator 404 is operated by the output of the I/O connector 126. The visual indicator 404 may be a light stack having a plurality of lights (e.g., green, yellow, read, or combinations thereof). The visual indicator 404 may indicate the state/mode of the apparatus 100C or the handheld data capture and identification terminal 102. The audio indicator 406 is operated by the output of the I/O connector 126. The audio indicator 406 creates audible sound and may indicate the state/mode of the apparatus 100C or the terminal 102. The external proximity detector 408 may be provided to detect an object. The detector 408 provides a message associated with the detection result to the I/O connector 126. The message may change the state/mode of the terminal 102. For example, the message from the detector 408 may trigger an identification event and thus activate one or more than one AIDC sensors 170. The external device 410 is operated by the output of the I/O connector 126. The external device 410 may be, but not limited to, a conveyer.

0091In <figref idref="f0008">Figure 8</figref>, the visual indicator 404 and the audio indicator 406 are illustrated separately from the apparatus 100C. However, in another example, the visual indicator 404, the audio indicator 406, or a combination thereof may be located in the fixture of the apparatus 100C, the handheld data capture and identification terminal 102 or a combination thereof.

0092The system 400 includes a server 420 having a database. In <figref idref="f0008">Figure 8</figref>, the server 420 commutates with the handheld data capture and identification terminal 102 via the wireless network interface 158. In another example, the server 420 may communicate with the terminal 102 via a wired network interface connected to the I/O connector 126. The server 420 may control the state/mode of the terminal 102. The apparatus 100C may operate the I/O device 402 based on the current state/mode instructed by the server 420. The server 420 may directly operate the I/O device 402.

0093The server 420 may receive, store and analyze information received from the handheld data capture and identification terminal 102. The information provided from the terminal 102 may include local time information. The information provided from the terminal 102 may include data captured by the terminal 102 or data manually input to the terminal 102. The server 420 may detect the presence of an object based on the sensing information, manual input received from the terminal 102 or a combination thereof, and may send a message to the terminal 102 for object identification when the object is detected. The information provided from the terminal 102 may include identification data acquired by the automatic identification process, the manual identification process, or a combination thereof, for authentication. Based on the information provided from the terminal 102, the server 420 authenticates an object. The server 420 sends a message indicating the result of the authentication to the terminal 102. In a further example, the terminal 102 and the server 420 may use a Confidence of Identification (COI) variable for object identification, as described below.

0094<figref idref="f0009">Figure 9</figref> illustrates another example of the object identification and authentication system. The system 430 of <figref idref="f0009">Figure 9</figref> includes an apparatus for manual and automatic identification, labeled as 100D. The apparatus 100D may be the same or similar to the apparatus 100 of <figref idref="f0002">Figure 2</figref>, the apparatus 100A of <figref idref="f0003">Figure 3</figref> or the apparatus 100B of <figref idref="f0004">Figure 4</figref>. The apparatus 100D includes a handheld data capture and identification terminal 102D and a fixture having a support base 114D. The handheld data capture and identification terminal 102D is similar to the terminal 102 of <figref idref="f0002">Figure 2</figref>. In addition, the terminal 102D includes the visual indicator 404 and the audio indicator 406. The fixture for the apparatus 100D may be the same or similar to the fixture 104 of <figref idref="f0002">Figure 2</figref>, the fixture 104A of <figref idref="f0003">Figure 3</figref> or the fixture 104B of <figref idref="f0004">Figure 4</figref>. The support base 114D may be the same or similar to the support base 114 of <figref idref="f0002">Figure 2</figref>, the support base 114A of <figref idref="f0003">Figure 3</figref> or the support base 114B of <figref idref="f0004">Figure 4</figref>.

0095The apparatus 100D communicates with one or more than one I/O device 402D. The I/O device 402D is similar to the I/O device 402 of <figref idref="f0008">Figure 8</figref>. The I/O device 402D includes, for example, but not limited to, the external proximity detector 408 and the external device 410. The I/O device 402D may be directly operated by the server 420.

0096In <figref idref="f0009">Figure 9</figref>, the I/O 126, the wireless I/F 158, the controller 162, the sensors 170 are schematically shown. However, the apparatus 100D may include other components as shown in <figref idref="f0002">Figures 2</figref>, <figref idref="f0003">3</figref> and <figref idref="f0004">4</figref>.

0097In <figref idref="f0009">Figure 9</figref>, the visual indicator 404 and the audio indicator 406 are located in the handheld data capture and identification terminal 102D. However, in another example, the visual indicator 404 and the audio indicator 406 may be located in the fixture for the terminal 102D. In a further example, one of the visual indicator 404 and the audio indicator 406 may be located in the fixture for the terminal 102D, and the other may be located in the terminal 102D.

0098<figref idref="f0010">Figure 10</figref> illustrates an example of a method for reliable and rapid object identification and authentication. As an example, the steps of <figref idref="f0010">Figure 10</figref> are applied to the system 400 of <figref idref="f0008">Figure 8</figref>. As described above, one of the visual indicator 404 and the audio indicator 406 or both may be located in the apparatus 100C.

0099Referring to <figref idref="f0008">Figures 8</figref> and <figref idref="f0010">10</figref>, when there is no object present in the field of identification (FOI), the system 400 resides in the "System Idle State" (step 442) where the system 400 is waiting for an object to arrive, polling the detection mechanism of the system 400 on a regular basis (step 444). The apparatus 100C is configured for automatic identification. The system 400 determines whether an object is detected (step 444).

0100In the "System Idle State", the system 400 provides a visual/audio indication that the system 400 is in the "System Idle State". The visual indicator 404 (e.g., light stack) may display a specific light (e.g., yellow light) to indicate this state.

0101In an example, the detection mechanism may make use of the I/O connector 126 such that the external proximity detector 408 indicates the presence of the object.

0102In another example, an image sensor (i.e., 170B of <figref idref="f0002">Figure 2</figref>) on the handheld data capture and identification terminal 102 may be used to detect the object. The image sensor may be intermittently enabled. An image from the image sensor is sent to the server 420 over the wireless network interface 158 and stored on the server 420, for security purposes.

0103In a further example, the image sensor may also be employed to detect the presence of a suitable identification subject in the field of identification, using the controller 162 to perform image processing on the detected object. In this case, the apparatus 100C determines whether the object is a suitable candidate for identification.

0104In a further example, the image sent to the server 420 may be analyzed, and a signal may be sent back from the server 420 to the apparatus 100C to indicate that the object is present.

0105In this state health information is returned to the server 420 on a regular basis. This health data may include results of processes such as enabling the RFID reader (i.e., 170A of <figref idref="f0002">Figure 2</figref>) and ensuring that a tag which is always in the RF detection zone can be read, enabling the image sensor and ensuring that a static, easy to recognize image can be captured, and the local time according to the controller 162.

0106When an object is detected ("yes" at step 444), the system 400 transitions into the "Object Detected State" (step 446). The system 400 provides a visual/audio indicator that the system 400 is in the "Object Detected State". The visual indicator 404 (e.g., light stack) indicates that an object has been detected and attempted automatic identification is in progress by flashing one or more than one light.

0107In the "Object Detected State", the RFID reader (i.e., 170A of <figref idref="f0002">Figure 2</figref>) is enabled so that if the object has an RFID tag fitted, the RFID tag is read. The image sensor (i.e., 170B of <figref idref="f0002">Figure 2</figref>) may be enabled to capture an image of the object being identified, and to aid the identification process through pattern recognition. At this time a message may be sent to the server 420 over the wireless network to indicate that the object has been detected. The system 400 attempts to automatically identify the object using all available identification methods (i.e., AIDC sensors 170).

0108The data acquired by the automatic identification process is sent to the server 420 via the wireless network for authentication. The system 400 determines whether the object is authenticated (step 448). The server 420 compares the data captured by the automatic identification process with information stored in a database. If the server 420 can identify the object based on the comparison, the server 410 sends an authenticated message back to the apparatus 100C. If the server 420 cannot identify the object to a sufficient degree, a not-authenticated message is sent back to the apparatus 100C.

0109If the apparatus 100C receives the authenticated message from the server 420, the apparatus 100C enters the "Object Authenticated State" (step 450). In the "Object Authenticated State", the RFID reader (i.e., 170A of <figref idref="f0002">Figure 2</figref>) is turned off. The system 400 provides a visual/audio indication that the system 400 is in the "Object Authenticated State". The visual indicator 404 (e.g., light stack) displays a specific light (e.g., green light) to indicate that the identification process was successful. The audio indicator 406 creates sound to indicate that the successful identification has occurred, such as playing ascending notes in a musical scale.

0110If the object is to be transported by a conveyer (e.g., 410 of <figref idref="f0008">Figure 8</figref>), the conveyor is enabled such that the object moves out of the field of identification. If there is no conveyor belt, and the objects are being manually handheld, the green light and audible indication serve to indicate to an observer that the object can continue through the system. After remaining in this state long enough for the object to be removed from the FOI, the system 100C returns to the "System Idle State"(step 442).

0111If the apparatus 100C does not receive any authenticated message from the server 420, the system enters the "Object Automatic Identification Fail State"(step 452). The visual indicator 404 (e.g., light stack) produces a specific visual output, and the audio indicator 406 creates a specific audible sound, both of which indicate that the Automatic identification has failed. For example, the light stack flashes the red light. The audible signal may be a sequence of descending notes in a musical scale. This audible signal may repeat at regular intervals while in this state, to alert a human operator that action is required. If a conveyor belt (e.g., 410 of <figref idref="f0008">Figure 8</figref>) is present, the conveyor belt will remain stopped. The apparatus 100C stays in this state until the handheld data capture and identification terminal 102 is removed from the fixture (e.g., 104 of <figref idref="f0002">Figure 2</figref>). However, the system 400 may transition directly to step 458 if the human operator is not available to manually identify the object.

0112When the handheld data capture and identification terminal 102 is removed from the fixture (e.g., 104 of <figref idref="f0002">Figure 2</figref>), the apparatus 100C enters the "Manual Identity State" (step 454). A signal is sent to the server 420, which indicates that the AIDC sensors 170 have been removed from the fixture. In this state, the human operator attempts to identify the object in all available ways such as barcode scanning (i.e., 170C of <figref idref="f0002">Figure 2</figref>), further close range RFID reading, visual identification of the item by the human operator. When using the visual identification of item, the human operator enters the identity of the object into the handheld data capture and identification terminal 102. The system 400 uses such information in the same way as any other identification data gathered. While in this state, the light stack continues to flash red, but the audible signal may cease, or be reduced in frequency of occurrence.

0113The system 400 determines whether the object is manually identified (step 456). If the object cannot be identified by the human operator in any way, the object is rejected by the system and removed (step 458). If the object is identified by the human operator, the system 400 enters the "Object Authenticated State" (step 450), and the data gathered through manual identification is sent to the server 420. Manual identification by the human operator always leads to data that will definitely be authenticated (step 450), or the object is rejected from the system 400 (step 458).

0114In <figref idref="f0010">Figure 10</figref>, the determination step 444 may be implemented by the server 420 or the terminal 102, and the determination step 456 may be implemented by the server 420 or the terminal 102. In another example, the human operator may make this decision for further data processing.

0115<figref idref="f0011">Figure 11</figref> illustrates an example of a fixture in a further embodiment of the present invention. The fixture 140E of <figref idref="f0011">Figure 11</figref> is similar to those of <figref idref="f0006 f0007">Figures 6-7</figref>, and includes the weight 301, the lower shaft 303, the upper shaft 307, the I/O connector 325, the power input 326, the power connection 322, and the I/O connection. The fixture 140E further includes an auxiliary RFID reader 502, and antennas 504 and 506. The auxiliary RFID reader 502 is connected to the antennas 504 and 506 via a coaxial cable 508. The antennas 504 and 506 are connected to the lower shaft 303 and the upper shaft 307, respectively. An angle member 510 is provided to connect the antenna 504 and the lower shaft 303 so that the antenna angle is adjustable. The angel member 510 may be a hinge for allowing the antenna 504 to rotate in a certain direction. An angle member 512 is provided to connect the antenna 506 to the upper shaft 307 so that the antenna angle is adjustable. The angle member 512 may be a hinge for allowing the antenna 506 to rotate in a certain direction. The angle members 510 and 512 adjust the antennas 504 and 506 to point in a plurality of directions.

0116In <figref idref="f0011">Figure 11</figref>, two antennas 504 and 506 are shown. However, the number of antennas for the auxiliary RFID reader 502 may vary depending on the system design/requirement, and not limited to two. One antenna (504 or 506) may be used for the auxiliary RFID reader 502. However, the multi-antennas 502 and 504 provide greater coverage than that of one antenna, in automatic identification configuration. In <figref idref="f0011">Figure 11</figref>, one auxiliary RFID reader 502 is shown. However, the number of auxiliary RFID readers is not limited to one and may vary depending on the system design/requirement.

0117In <figref idref="f0011">Figure 11</figref>, the tilt/elevation controller 142 of <figref idref="f0002">Figure 2</figref> and the docking member 108 of <figref idref="f0002">Figure 2</figref> are not shown. However, the fixture 140E may include the tilt/elevation controller and the docking member same or similar to those of <figref idref="f0006 f0007">Figures 6-7</figref>.

0118In a further embodiment, "Confidence of Identification" (COI) is assigned to each object for identification. "COI" is a variable which provides a measure of whether the subject of identification requires further identification before it can continue.

0119In one example, if an object is identified using RFID (e.g., 170A of <figref idref="f0002">Figure 2</figref>), this identification information may trigger the server (e.g., 420 of <figref idref="f0008">Figures 8</figref> and <figref idref="f0009">9</figref>) to request further identification to take place, to ensure accurate identification, and to increase the security of the system. In another example, if an object is identified using RFID, and this identification information suggests that said object should not be in the location where it has been detected, further identification may be requested by the server.

0120If an object has a COI of "1", the object may be allowed to continue through the system based on a single source of identification (e.g., reading of an RFID tag, reading of a barcode, etc.).

0121If an object has a COI of "2", the two forms of identification may be required before the object may be allowed to continue. This may trigger a manual identification after an RFID tag read to corroborate the identification based on the RFID read.

0122All objects apart from those expected to be identified at a particular location may have a COI of greater than "1", so that if an unexpected object is detected, further identification would be required to increase the integrity and security of the system.

0123The object may not be identified to a required confidence associated with its COI. If the COI cannot be met where the object cannot be identified to its required confidence, the object may be rejected from the system.

0124The information related to COI may be visually provided to an observer through the system (e.g., 100C of <figref idref="f0008">Figure 8</figref>, 100D of <figref idref="f0009">Figure 9</figref>).

0125According to the embodiments of the present invention, objects can be easily identified by the handheld terminal which supports automatic identification and manual identification. When the state of the system is changed or a certain event is occurred (e.g., failure of automatic identification), the operator is alerted. The operator can easily remove the handheld terminal from the fixture for supporting the handheld terminal and take a control of the handheld terminal. Since the handheld terminal includes a plurality of sensors having an RFID reader, the system can identify both of an RFID item and a non-RFID item. The fixture with the handheld terminal has a greater flexibility comparing to conventional fixed portal RFID reader. In addition, the fixture with the handheld terminal can be implemented for a low cost compared to the conventional automatic identification systems.

0126Various embodiments of the invention may be implemented in one or any combination of hardware, firmware, and software. The invention may also be implemented as instructions contained in or on a machine-readable medium, which may be read and executed by one or more processors to perform the operations described herein. A machine-readable medium may include any mechanism for storing, transmitting, and/or receiving information in a form readable by a machine (e.g., a computer). For example, a machine-readable medium may include a storage medium, such as but not limited to read only memory (ROM); random access memory (RAM); magnetic disk storage media; optical storage media; a flash memory device, etc. A machine-readable medium may also include a propagated signal that has been modulated to encode the instructions, such as but not limited to electromagnetic, optical, or acoustical carrier wave signals.

0127The present invention has been described with regard to one or more embodiments. However, it will be apparent to persons skilled in the art that a number of variations and modifications can be made without departing from the scope of the invention as defined in the claims.