Abstract:
System, device and methods that provide proximate environmental and security intelligence to a guard making a security tour or round in an installation, as well as that provide for certifying that the guard has visited designated and known checkpoints on or about the times at which the guard is expected at those checkpoints.

Description:
CROSS-REFERENCE TO RELATED APPLICATIONS 
       [0001]    Not Applicable 
       STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT 
       [0002]    Not Applicable 
       NAMES OF PARTIES TO A JOINT RESEARCH AGREEMENT 
       [0003]    Not Applicable 
       INCORPORATION-BY-REFERENCE OF MATERIAL SUBMITTED ON A COMPACT DISC 
       [0004]    Not Applicable 
       BACKGROUND OF THE INVENTION 
       [0005]    1. Field of the Invention 
         [0006]    The field of the invention relates to security systems generally, and more particularly to certain new and useful advances in guard communications of which the following is a specification, reference being had to the drawings accompanying and forming a part of the same. 
         [0007]    2. Description of Related Art 
         [0008]    A mobile guard&#39;s awareness is often limited to what may be seen or heard while on a tour through an installation. For example, an emergency situation, such as a fire or an intruder on the other side of a wall, may not be discoverable while the guard is away from a central security console that has displays and sensor presentations. There is therefore a need for a way for a mobile guard to be made aware of visually and audibly blocked surroundings while on tour. 
         [0009]    it is also desirable that there be a way to check that the guard did indeed visit appointed locations during certain time windows. There is therefore also a need for a way to verify that the mobile guard has properly completed appointed rounds. 
       BRIEF SUMMARY OF THE INVENTION 
       [0010]    Various embodiments of a method and system are disclosed that provide proximate environmental and security intelligence to a guard making a security tour or round in an installation. Also disclosed are various embodiments that include a provision for certifying that the guard has visited designated and known checkpoints on or about the times at which the guard is expected at those checkpoints and the provision of sensors and a channel from the guard back to a security station for reporting observed data. 
         [0011]    Other features and advantages of the disclosure will become apparent by reference to the following description taken in connection with the accompanying drawings. 
     
    
     
       BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS 
         [0012]    Reference is now made briefly to the accompanying drawings, in which: 
           [0013]      FIG. 1  is a diagram that illustrates an embodiment of a physical security system; 
           [0014]      FIG. 2  is a diagram of an embodiment of a mobile security device (“MSD”); 
           [0015]      FIG. 3  is a diagram illustrating an embodiment of the physical security system of  FIG. 1  in which sensor location and/or sensor data is transmitted to the MSD together with orientation data; 
           [0016]      FIG. 4  is a diagram illustrating how an event detected by a sensor is displayed on the MSD for viewing by a user of the MSD; 
           [0017]    FIG.,  5  is a flowchart illustrating an embodiment of a method for communicating with the MSD; 
           [0018]      FIG. 6  is a flowchart illustrating an embodiment of a method for communicating with a physical security system sensor via a fixed security console; 
           [0019]      FIG. 7  is a flowchart illustrating an embodiment of a method for using the MSD to report and/or confirm that a security check has been completed; 
           [0020]      FIG. 8  illustrates a fixed security device having a barcode display comprised of one or more light sources, such as Light Emitting Diodes (“LEDs”); and 
           [0021]      FIG. 9  is a block diagram of a computer system that may be used to implement software used by embodiments of the physical security system and/or the MSD. 
       
    
    
       [0022]    Like reference characters designate identical or corresponding components and units throughout the several views, which are not to scale unless otherwise indicated. 
       DETAILED DESCRIPTION OF THE INVENTION 
       [0023]    In the exemplary embodiment, a security guard performing mobile rounds of an installation will carry a Mobile Security Device (“MSD”) that provides at least two functions: display of sensors about a guard&#39;s location together with data from those sensors, and certification, or evidence, that a guard visited one or more checkpoints. 
       First Function—Display of Sensors Surrounding a Guard&#39;s Location 
       [0024]    The first function provides a display of sensors monitoring spaces proximate the guard&#39;s position as he or she progresses through a particular area. The sensors that are displayed on the guard&#39;s MSD may be fixed installation sensors that are linked with an installation&#39;s physical security system. The MSD may receive sensor data sent wirelessly from the central security console, or may query installation sensors directly when allowed by policy. 
         [0025]    Features of the first function comprise, by way of example and not limitation: 
         [0026]    (a) a visual display of one or more sensors in a proximate area (“spatial extent”) surrounding the guard&#39;s present position, and optionally—a visual and/or audible indication of sensor data for the one or more of the sensors; 
         [0027]    (b) a visual display of one or more sensors in an area proximate the guard&#39;s scheduled route, and optionally—a visual and/or audible indication of sensor data for the one or more sensors; or 
         [0028]    (c) a visual display of one or more sensors in an area proximate a path extrapolated from the guard&#39;s most recent direction of movement, and optionally—a visual and/or audible indication of sensor data for the one or more of the sensors. 
         [0029]    The sensor data for which the MSD provides a visual and/or audible indication can comprise, but is not limited, to an alarm, such as a fire alarm, a smoke alarm, a door alarm, and so forth. 
         [0030]    At least the sensor data for the display is sent to the MSD via a wireless transmission from a central security console that has access to the data from the one or more sensors that are proximate to the guard&#39;s present position, scheduled route, or the path extrapolated from the guard&#39;s most recent direction of movement. Map data for the display is also sent to the MSD via wireless transmission from the central security console or other network server. Alternatively, the map data for the display can be preloaded into a memory of the MSD. 
         [0031]    In one embodiment, the map and/or sensor data is processed at the central security console and formatted so that its spatial extent is appropriate for the guard&#39;s position at the time of the guard&#39;s receiving the map and/or sensor data. The spatial extent may also be adjustable by either the guard or an operator of the central security console. 
         [0032]    The spatial extent on the MSD display may be oriented with respect to the guard&#39;s most recent direction of motion or most recent orientation to provide a more natural and instantaneously unambiguous spatial reference to a mobile guard. 
       Second Function—Certification, or Evidence, of Checkpoints Visited 
       [0033]    The second function provided by the MSD provides certification or evidence that the guard did indeed visit specified checkpoints, known to the guard, on or about time targets also known to the guard, during completion of the guard&#39;s appointed patrol. 
         [0034]    in the exemplary embodiment, the evidence is provided by a scanning and recordation—or processed recordation—of an output of a fixed security device (“FSD”) at each checkpoint to be visited during a patrol. The FSD is anchored to structure near its location and is resistant to penetration and unauthorized opening. The FSD output comprises one or more informational elements, which comprise, but are not limited to: 
         [0035]    a fixed security station identifier; 
         [0036]    a time code; and 
         [0037]    a certification informational element such as a symbol string. 
         [0038]    The symbol string may change in a pseudorandom manner with a time code. An algorithm producing the value of the certification informational element may be a cryptographic process with a keying variable involving the security station identifier. 
         [0039]    The FSD output may be electronic and communicated to the MSD by a near field communication (“NFC”) transmission. Other modes of communication between the FSD and the MSD may include acoustic, seismic (or vibration), optical (such as infrared, visible light, or ultra-violet), magnetic, and direct or capacitive electrical contact. 
         [0040]    The central security console may determine the guard&#39;s present position, most recent direction of movement, and/or most recent orientation in at least two ways: 
         [0041]    (a) the MSD contains onboard accelerometers, position sensors, and the like that output the MSD&#39;s location, most recent direction of movement, and/or most recent orientation for wireless transmission to the central security console; or 
         [0042]    (b) alternatively, the MSD wirelessly transmits its present position, most recent direction of movement, and/or most recent orientation to the central security console. This may be accomplished using, by way of example and not limitation: accelerometers, radio or audio-based location techniques, and/or by calculation based on sensor imagery provided to the central security console whose processed outputs are formatted and/or overlaid with map data and/or sensor data, and then wirelessly sent from the central security console to the MSD for display. 
       Physical Security System 
       [0043]      FIG. 1  is a diagram that illustrates an embodiment of a physical security system (“system”)  100 . At a high-level components of system  100  comprise a central security console  101 , which is coupled with one or more actuators  103 , with one or more sensors  105 , and with a mobile security device (“MSD”)  129 . The central security console  101  is wirelessly coupled with the MSD  129 , and may be wired to or wirelessly coupled with the one or more sensors  105 . 
         [0044]    Each of the high-level components comprises one or more sub-components. For example, the central security console comprises a user interface  107 , a server  109 , and an access controller  111 . The user interface  107 , which may be a keypad, a display and/or a computer mouse, is coupled with a server  109  and with one or more of the sensors  105 . The one or more actuators  103  comprise a pan, tilt, and zoom actuator for a security camera and one or more door locks  115 . The one or more sensors  105  comprise biometric identification device(s)  117 , employee badge reader(s)  119 , motion sensor(s)  121 , security camera(s)  123 , door contacts  125 , and (optionally) one or more other sensors  127 . The one or more other sensors  127  may include, without limitation: fire sensors, smoke detectors, microphones, keypads, and so forth. 
         [0045]    The access controller  111  is coupled with the one or more actuators  103  and with the one or more sensors  105 . In particular, the access controller  111  is coupled with the pan, tilt, and zoom motors  113  of a camera, and with one or more door locks  115 . The access controller  111  is also coupled with, and configured to control, sensors  105  such as: motion sensor(s)  121 , security camera(s)  123 , and/or door contact(s)  125 . Optionally, the access controller  111  may be coupled with, and configured to control, the biometric identification device(s)  117 , the employee badge reader(s)  119 , and/or the one or more other sensors  127 . 
         [0046]    Sensor data output from each of the sensors  105  is sent to the central security console  101  and stored in a database on the server  109  for later retrieval, processing, and/or transmission. Additionally or alternatively, each sensor stores sensor data in its memory, for later transmission to the database on the server  109  or for direct retrieval by the MSD  129 . Examples of the sensor data output from each of the sensors  105  comprises, but is not limited to: when an event occurred, the type of event detected, and the sensor that made the detection. Simple sensors, such as the door contact(s)  125  or a fire/smoke detector may output limited data, such as that a door is open/closed or that fire/smoke has been detected. More complex sensors, such as the biometric identification device(s)  117  and/or the security camera(s)  123  may output more robust data that can be processed using known techniques to identify one or more persons (with a given probability) and/or to predict a probable individual and/or group behavior. 
       Mobile Security Device (“MSD”) 
       [0047]      FIG. 2  is a diagram of an embodiment of the mobile security device (“MSD”)  129 , shown in  FIG. 1 . Sub-components of the MSD  129  comprise, without limitation: a display  201 , which is coupled with a suitable computer processor (“processor”)  203  and configured to display map data together with sensor location data and/or sensor data that corresponds to one or more installation sensors  105  (in  FIG. 1 ) in an area proximate a guard&#39;s location, most recent direction of movement, and/or most recent orientation. The display  201  may be a liquid crystal display (“LCD”), a light emitting diode (“LED”) display, an organic light emitting diode (“OLED”) display, a plasma display, or any other type of display technology that is suitable for handheld computing applications. 
         [0048]    The processor  203  is coupled with a memory  205  and configured to process the map data, sensor location data and/or sensor data for display on the display  201 . The processor  203  is further configured to operate the transceiver  207  to send and receive encrypted wireless messages to and from the server  109  ( FIG. 1 ) of a central security station  101  (FIG.  1 )—or to and/or from the one or more sensors  105  ( FIG. 1 ). The processor  203  is further configured to receive and process inputs from an input device  209 , such as a keypad, a computer mouse, a touch screen, and so forth. 
         [0049]    Optionally, the processor  203  may be configured to operate and/or process data received from one or more onboard sensors  211 , a locator  213 , optics  215 , a microphone  217  and/or a speaker  219 . Examples of the one or more onboard sensors  211  comprise, without limitation: a temperature sensor, a gas sensor, a temperature gradient sensor, a humidity sensor, and so forth. For outdoor patrols of an installation, the locator  213  may be a global positioning system (“GPS”) receiver. For indoor patrols of an installation, the locator  213  is any device, or combination of devices, that outputs data, which the processor  203  and/or the server  109  ( FIG. 1 ) can process to calculate the MSD&#39;s location, most recent direction of movement and/or most recent orientation. In one embodiment, the locator  213  comprises an accelerometer. In this embodiment, the processor  203  processes the accelerometer outputs together with triangulation data received in or from wireless signals outputted by different, geographically separate sources and received by the transceiver  207  to calculate one or more of the MSD&#39;s location, most recent direction of motion and/or most recent orientation. The optional optics  215  may comprise one or more of: a still camera, a video camera, a barcode scanner, and/or a barcode reader. The optional microphone  217  is configured to receive voice commands from a user of the MSD  129 , to receive and route voice data to the processor  203  for processing and/or wireless transmission, via the transceiver  207 , to the server  109  ( FIG. 1 ) of the central security console  101  ( FIG. 1 ), and/or to record ambient sounds during a guard&#39;s patrol. The optional speaker  219  is configured to play audible indications of sensor data (such as an indication of a fire alarm, smoke alarm, detection of a hazardous gas, etc.) and/or may be further configured to play voice data received from the central security console  101  ( FIG. 1 ). 
       Examples of Operation 
       [0050]      FIG. 3  is a diagram  300  illustrating an embodiment of the physical security system of  FIG. 1  in which sensor location and/or sensor data is transmitted to the MSD  129  together with orientation data. The central security console  101 , comprising server  109 , is coupled with a motion sensor  121 , a security camera  123 , and one or more other sensors  127  (such as a fire detector and/or a smoke detector). Transported by a guard (not shown), the MSD  129  has a direction of movement and/or an orientation, which is represented by arrow  301 , which points from the MSD  129  toward the sensors  121 ,  123  and  127 . Surrounding the MSD  129  and overlapping at least the sensors  123  and  127  is a spatial extent  302 . As used herein, the term “spatial extent” refers to the area proximate a guard&#39;s location, most recent direction of move ent, and/or most recent orientation. 
         [0051]    The server  109  sends wireless messages  303  and/or  307  to the MSD  129 , and receives wireless messages  305  and/or  309  from the MSD  129 , over an encrypted wireless channel. In operation, the server  109  receives one or more first wireless messages  305  from the MSD  129 , which comprise data indicative of, or which can be processed by the server  109  to calculate, the MSD&#39;s location, most recent direction of motion and/or most recent orientation. Thereafter, the server  109  transmits one or more second wireless messages  303  to the MSD  129 , which comprise one or more of: map data, sensor location data, sensor data and/or orientation data. The sensor location data and/or sensor data is/are provided at least for the sensors  123  and  127  that are within, or overlapped by, the spatial extent  302 . In order to transmit the one or more second wireless messages  303 , the server  109  may compare at least the MSD location data and/or the MSD most recent direction of motion data with one or more previously stored lookup tables that contain sensor location data. The MSD processor  203  ( FIG. 2 ) processes the orientation data, which may be provided by the server  109  and/or the MSD  129 , and outputs display data that orients and/or overlaps the map data, sensor location data and/or sensor data on the MSD display  201  ( FIG. 2 ). 
         [0052]    In an alternative embodiment, the server  109  calculates and transmits to the MSD  129 , in one or more third wireless messages  307 , one or more of MSD location data, MSD most recent direction of motion data, MSD most recent orientation data and sensor location data. Thereafter, the MSD processor  203  ( FIG. 2 ) processes this data to output display data that orients and/or overlaps the map data and/or sensor location data on the MSD display  201  ( FIG. 2 ). Thereafter, the processor  203  ( FIG. 2 ) receives inputs from a user of the MSD  129  that select one or more of the displayed sensor locations. This inputted data is then processed and transmitted, via the MSD transceiver  107  ( FIG. 2 ) to the server  109  in one or more fourth wireless messages  309 . Thereafter, the server  109  retrieves and transmits sensor data back to the MSD  129  for the selected sensor locations. 
         [0053]      FIG. 4  is a diagram  400  illustrating how an event  430  detected by a sensor  127  is displayed on the MSD  129  for viewing by a user  410  of the MSD  129 . The user  410  is depicted, in this non-limiting example, as walking toward a wall  420 . In a space on the user&#39;s right but hidden by an adjacent wall  421  is the event  430 —which for purposes of illustration only, may be a fire. A central security console  101  knows of the event  430  by one or more sensors  127 . The central security console  101  also knows the MSD&#39;s location, most recent direction of motion and/or or most recent orientation and, as previously described, sends map data of the proximate area to the MSD  129 , together with sensor location data, sensor data and/or orientation data. As a result, the MSD&#39;s visual display is oriented with respect to at least one of the MSD&#39;s location, most recent direction of movement and/or most recent orientation. Arrow  450  points from the MSD  129  to a view  460  of what the user  410  sees. 
         [0054]    The view  460  depicts a sample front view of an exemplary MSD  129 , which comprises, by way of example and not limitation, the display  201 , input devices  209  (keypad and computer mouse), and optional camera  215 , microphone  217  and speaker  219 . On the display  201  is shown a map  480  of the area proximate the guard&#39;s/MSD&#39;s location, oriented to the MSD&#39;s most recent direction of motion and/or the MSD&#39;s most recent orientation, as represented by arrow  301 . The map  480  depicts the MSD&#39;s location  470  relative to a location of the detected event  430 . Optionally the display  201  depicts a location, and/or identification of an installation sensor  127   
       Methods 
       [0055]      FIG. 5  is a flowchart illustrating an embodiment of a method  500  for communicating with the MSD  129  ( FIGS. 1 ,  2 ,  3 , and  4 ). Referring to  FIGS. 1 ,  2 ,  3 ,  4 , and  5 , the method  500  begins by locating  501  the MSD  129 . At decision block  503 , the server  109  determines whether location, most recent direction of movement and/or most recent orientation data has been received from the MSD  129  if no, the server  109  calculates  505  the MSD&#39;s location, most recent direction of movement, and/or most recent orientation from sensor data provided at least by the one or more sensors  105 . If yes, the server  109  identities  507  an installation sensor proximate the location of the MSD  129 . Optionally, the identification step  507  may comprise determining  509  a spatial extent  302  about the MSD  129 . The size of the spatial extent  302  varies, but is selected as being appropriate for the MSD&#39;s location. In one embodiment, the spatial extent  302  has a radius that is configurable and adjustable by a user  410  of the MSD  129 . Optionally, the identification step  507  may further comprise identifying one or more installation sensors within, or overlapped, by the spatial extent  511 . Proceeding from either step  507  or  511 , the method  500  may further comprise retrieving  513  at least sensor location data and/or sensor data for the identified installation sensor. Thereafter, the server  109  may transmit  515  the retrieved sensor location data and/or the retrieved sensor data, together with orientation data, which is data configured to orient a map display of the MSD with respect to the MSD&#39;s location, most recent direction of movement and/or most recent orientation. 
         [0056]      FIG. 6  is a flowchart illustrating an embodiment of a method  600  for communicating with a physical security system sensor  105  ( FIG. 1 ) via a fixed security console  101  ( FIGS. 1 ,  3 ,  4 ). Referring to  FIGS. 1 ,  2 ,  3 ,  4  and  6 , one embodiment of the method  600  begins by the MSD  129  receiving  601  from the server  109  retrieved location data about an installation sensor  105  proximate the MSD, together with the orientation data described above. Alternatively, the method  600  begins by the MSD  129  receiving  603  an input that selects a radius of a spatial extent  302  about the MSD  129 . Thereafter, the method  600  optionally timber comprises the MSD  129  transmitting  605  the selected radius of the spatial extent  302  to the server  109 . 
         [0057]    Proceeding from step  601 , the method  600 ) may further comprise showing  607  on the MSD display  201  an indication of the location of the installation sensor  105 ,  127 . Thereafter, the MSD  129  may receive  609  an input that selects the displayed installation sensor  105 ,  127 . Upon receiving  609  this input, the MSD requests  611  sensor data for the selected installation sensor  105 ,  127  from the server  109  of the central security console  101 . Thereafter, the MSD  129  receives  613  the requested sensor data, and may display  615  the received sensor data on the MSD display  201 , together with a representation of the sensor&#39;s location—oriented with respect to the MSD&#39;s location, most recent direction of motion and/or most recent orientation. 
         [0058]      FIG. 7  is a flowchart illustrating an embodiment of a method  700 ) for using the MSD  129  ( FIGS. 1 ,  2 ,  3 ,  4 ) to report and/or confirm that a security check has been completed.  FIG. 8  illustrates a fixed security device (“FSD”)  800  having one or more barcode displays  820 ,  830  and  840 . Each barcode display  820 ,  830  and  840  comprises one or more light sources  850 , such as—but not limited to—Light Emitting Diodes (“LEDs”). Each barcode display  820 ,  830  and  840  is configured to provide a certification informational element (not shown) that identifies the FSD. 
         [0059]    Referring to  FIGS. 1 ,  2 ,  3 ,  4 ,  7  and  8 , the method  700  starts at any of steps  701 ,  707  or  711 . At step  701 , the MSD  129  scans a barcode display  820 ,  830  and/or  840  from a fixed security device  800 . From step  701 , the method  700  may proceed to step  703  or directly to step  705 . Step  703  comprises processing, using a processor  203  of the MSD  129 , the scanned barcode display  820 ,  830  and/or  840  to a smaller data set that retains the certification informational element. Step  705  comprises transmitting, using the transceiver  207  of the MSD  129 , at least the certification informational element, to the server  109  of the central security station  101   
         [0060]    Alternatively, the method  700  begins by a sensor  105  detecting  707  a presence of the MSD proximate an installation sensor  105 . From step  707 , the method comprises the sensor  105  transmitting  709  at least a certification informational element to the MSD  129   
         [0061]    Alternatively, the method  700  begins by a MSD  129  detecting  711  a presence of an installation sensor  105  proximate the MSD  129 . From step  711 , the method  700  comprises the MSD  129  receiving  713  a certification informational element from the detected installation sensor  105 . From step  713 , the method proceeds to previously described step  705 . 
       Computer System 
       [0062]    Referring again to  FIGS. 1 ,  2 ,  3 ,  4 ,  5 ,  6 ,  7  and  8 , the functions or algorithms of the physical security system  100 , and components and subcomponents thereof, may be implemented in software or a combination of software and user-implemented procedures, and executed by machines comprising computer hardware and/or firmware. The software may comprise computer-executable instructions stored on computer readable media, and/or in computer-readable memory. “Computer readable media” comprises disks as well as carrier waves, which are any type of electromagnetic wave that can be modulated, either in frequency, amplitude or phase, to transmit the computer-executable instructions. The functions of MSD  129 , the FSD  800  and/or other components of the physical security system  100  may be represented by one or more software modules. This software and/or its modules can be executed at least by the server  109  and/or the MSD processor  203 . 
         [0063]    Various steps of the methods described herein may be performed serially, or in parallel, using multiple processors or a single processor configured as two or more virtual machines or sub-processors. 
         [0064]      FIG. 9  is a block diagram of a computer system  900  that may be used to implement software used by embodiments of the physical security system  100  ( FIG. 1 ) and/or the MSD  129  ( FIGS. 1 ,  2 ,  3  and  4 ). The computer system  900  comprises a computer  910 , and may optionally comprise external, or network, devices  920 . The computer  910  comprises a processor  903  coupled with a memory  940 , which may comprise a volatile memory  941  and/or a non-volatile memory  942 . A computer software program  943  may be stored in the memory  940  for execution by the processor  930 . The computer  910  may further comprise a removable storage device  951  and/or a non-removable storage device  953 . Via a wireless or wired communication channel, the computer  910  may have access to external volatile memory  921 , external non-volatile memory  923 , external removable storage device(s)  925 , and/or external non-removable storage device(s)  927 . Collectively, the internal storage devices  951 ,  953  and external storage devices  925 ,  927  are referred to as “computer storage”, and may comprise one or more of the following: random access memory (“RAM”), read only memory (“ROM”), erasable programmable read-only memory (“EEPROM”), electrically erasable programmable read-only memory (“EEPROM”), flash memory or other kinds of computer memories, compact disc read-only memory (“CD ROM”), digital versatile discs (“DVD”) or other kinds of optical disc-based storage, magnetic cassettes, magnetic tape, magnetic disc storage or other kinds of magnetic storage technologies, or any other medium configured to store computer-readable instructions. 
         [0065]    The computer  910  may further comprise an input  957 , an output  959 , and a transceiver  955 , comprising an encoder and/or decoder, for formatting and/or encrypting/decrypting wired or wireless signals transmitted from and/or to the computer  910  over a network  960 , which may be either a local area network (“LAN”) or a wide area network (“WAN”). As used herein, the term “computer” may comprise one of: a personal computer, a handheld computer, a server, a router, an access controller, a wireless security device, a network node, a peer device, a fixed security device, a central security console, and the like. 
         [0066]    As used herein, an element or function recited in the singular and preceded with the word “a” or “an” should be understood as not excluding plural said elements or functions, unless such exclusion is explicitly recited. Furthermore, references to “one embodiment” of the claimed invention should not be interpreted as excluding the existence of additional embodiments that also incorporate the recited features. 
         [0067]    This written description uses examples to disclose the invention, including the best mode, and also to enable any person skilled in the art to make and use the invention. The patentable scope of the invention is defined by the claims, and may include other examples that occur to those skilled in the art. Such other examples are intended to be within the scope of the claims if they have structural elements that do not differ from the literal language of the claims, or if they include equivalent structural elements with insubstantial differences from the literal language of the claims. 
         [0068]    Although specific features of the invention are shown in some drawings and not in others, this is for convenience only as each feature may be combined with any or all of the other features in accordance with the invention. The words “including”, “comprising”, “having”, and “with” as used herein are to be interpreted broadly and comprehensively and are not limited to any physical interconnection. Moreover, any embodiments disclosed in the subject application are not to be taken as the only possible embodiments. Other embodiments will occur to those skilled in the art and are within the scope of the following claims.