|Publication number||US7079023 B2|
|Application number||US 10/307,498|
|Publication date||Jul 18, 2006|
|Filing date||Dec 2, 2002|
|Priority date||Oct 4, 2002|
|Also published as||DE60323251D1, EP1550076A1, EP1550076B1, US20040075549, WO2004032038A1|
|Publication number||10307498, 307498, US 7079023 B2, US 7079023B2, US-B2-7079023, US7079023 B2, US7079023B2|
|Original Assignee||Sap Aktiengesellschaft|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (29), Referenced by (28), Classifications (11), Legal Events (4)|
|External Links: USPTO, USPTO Assignment, Espacenet|
This application is a utility application of and claims priority to U.S. Provisional Application Ser. No. 60/415,774, filed on Oct. 4, 2002.
This description relates to the use of sensors in the active identification of objects and/or collection of data.
Conventional systems exist which attempt to identify objects and/or collect data about the objects. For example, inventory-control systems attempt to identify objects being input to, stored in, or output from, for example, an inventory warehouse. Such identification may include attempts to determine whether the objects have been tampered with or otherwise damaged. Similarly, in a manufacturing environment, it is desirable to know whether an object's actual state of assembly matches its desired state of assembly, during a given point in the assembly process. Many other examples of situations exist in which it is necessary or desirable to obtain an identification of an object, and/or data about the object.
Various sensors exist which allow automated or assisted collection of information that may be useful in the above scenarios. For example, Radio Frequency Identification (“RFID”) tags may be attached to the object in question, and an electronic interrogator may be used to read information about the object from the RFID tag. Similarly, cameras, weight scales, temperature and pressure sensors, and various other sensors exist which assist in the collection of data about a particular object.
According to one general aspect, an implementation may include a first information set related to an object detected at a first sensor, and a second information set related to the object detected at a second sensor. The first information set and the second information set are aggregated to obtain an aggregated information set, and the aggregated information set is compared to an expected information set for the object.
Implementations may include one or more of the following features. For example, when aggregating the first information set and the second information set, the first information set and the second information set may be associated with the object based on a first time at which the first information set was detected and a second time at which the second information set was detected. Also when aggregating the first information set and the second information set, a first portion of the first information set may be determined to be redundant to a second portion of the second information set, and the second portion may be discarded. Also when aggregating the first information set and the second information set, a malfunction of the first sensor may be determined, and the first information set may be discarded.
Also when aggregating the first information set and the second information, a predetermined set of aggregation rules may be applied to the first information set and the second information set. In this case, the aggregation rules may dictate a priority of the first information set over the second information set.
In comparing the aggregated information set, an identity of the object may be provided. In comparing the aggregated information set, a conflict between the aggregated information set and the expected information set may be detected. In this case, a conflict resolution for removing the conflict may be performed. Further in this case, in performing the conflict resolution, an inconsistency between the first information set and the second information set may be determined, and the first information set may be discarded, based on a predetermined rule that prioritizes the second information set over the first information set. Alternatively, in performing the conflict resolution, a human inspection of the object may be performed, and/or the object may be discarded.
In comparing the aggregated information set, additional information may be determined to be required. In this case, a third sensor may be activated, and a third information set may be detected at the third sensor. The third information set may be included within a modified aggregated information set, and the modified aggregated information set may be compared to the expected information set. Alternatively, the first sensor may be adjusted, and a modified first information set may be detected at the first sensor. The modified first information set may be included within a modified aggregated information set, and the modified aggregated information set may be compared to the expected information set.
According to another general aspect, a system may include a first sensor operable to sense an object and output a first information set related to the object, a second sensor operable to sense the object and output a second information set related to the object, an interface operable to input the first information set and the second information set, a database containing characterization data characterizing the object, and a resolver operable to input, via the interface, the first information set and the second information set, aggregate the first information set and the second information set into an aggregated information set, and compare the aggregated information set to the characterization data.
Implementations may include one or more of the following features. For example, the resolver may include a sensor control system operable to control an operation of the first sensor. The resolver may include a sensor behavior system operable to track sensor information regarding an accuracy and reliability of the first sensor and the second sensor. The resolver may be further operable to associate the first information set and the second information set with the object based on a first time at which the first information set was detected and a second time at which the second information set was detected.
The resolver may be further operable to determine that a first portion of the first information set is redundant to a second portion of the second information set, and thereafter discard the second portion. The resolver may be further operable to determine a malfunction of the first sensor, and thereafter discard the first information set.
The resolver may be further operable to apply a predetermined set of aggregation rules to the first information set and the second information set. In this case, the aggregation rules may dictate a priority of the first information set over the second information set. The resolver may be further operable to provide an identity of the object based on the comparing of the aggregated information set to the characterization data.
The resolver may be further operable to detect a conflict between the aggregated information set and the expected information set. In this case, the resolver may be further operable to perform a conflict resolution for removing the conflict. Further in this case, the resolver may perform the conflict resolution by determining an inconsistency between the first information set and the second information set, and discarding the first information set, based on a predetermined rule that prioritizes the second information set over the first information set. Alternatively, the resolver may perform the conflict resolution by requesting a removal of the object for a human inspection thereof. The resolver may perform the conflict resolution by outputting an instruction to discard the object.
The resolver, in comparing the aggregated information set to the characterization data, may determine that additional information is required. In this case, a third sensor operable to detect a third information set may be included, wherein the resolver is further operable to include the third information set within a modified aggregated information set, and compare the modified aggregated information set to the expected information set. Alternatively, the resolver may be further operable to output instructions for adjusting the first sensor, input, via the interface, a modified first information set from the first sensor, include the modified first information set within a modified aggregated information set, and compare the modified aggregated information set to the expected information set.
According to another general aspect, an apparatus includes a storage medium having instructions stored thereon, and the instruction include a first code segment for inputting multiple data sets from a plurality of sensors, a second code segment for associating the multiple data sets with an object, a third code segment for applying a set of aggregation rules to the multiple data sets, to thereby obtain an aggregation set, and a fourth code segment for comparing the aggregation set to an expected data set associated with the object.
Implementations may include one or more of the following features. For example, a fifth code segment may be for detecting a conflict between the aggregation set and the expected data set. In this case, a sixth code segment may be for performing a conflict resolution for removing the conflict. Further in this case, the sixth code segment may include a seventh code segment for determining an inconsistency between a first data set output by a first sensor from among the plurality of sensors and a second data set output by a second sensor from among the plurality of sensors, and an eighth code segment for discarding the data set, based on a predetermined rule that prioritizes the second data set over the first data set. Alternatively, the sixth code segment may include a seventh code segment for outputting an instruction to discard the object.
The fourth code segment may determine that additional information is required. In this case, a fifth code segment may be for inputting an additional data set from a sensor not from among the plurality of sensors, a sixth code segment may be for including the additional data set within a modified aggregation set, and a seventh code segment may be for comparing the modified aggregation set to the expected data set. Alternatively, a fifth code segment may be for outputting instructions for adjusting a first sensor from among the plurality of sensors, a sixth code segment may be for inputting a modified first data set from the first sensor, a seventh code segment for including the modified first data set within a modified aggregation set, and an eighth code segment may be for comparing the modified aggregation set to the expected data set.
The details of one or more implementations are set forth in the accompanying drawings and the description below. Other features will be apparent from the description and drawings, and from the claims.
A camera 120 positioned in proximity to the RFID gate 115 obtains an image of the box 105, and thereby also provides relevant information to a user. For example, in
Finally in the example of
In system 200, a plurality of sensors 205, 210, and 215 independently provide data about an object or a class of objects. Conventional sensors often provide their respective outputs in a pre-determined format. For example, camera 120 may output data as a Joint Photographic Experts Group (“JPEG”) file, or as a Moving Picture Experts Group (“MPEG”) file. Other sensors may output data as numerical data, using a particular file type or formatting preference. Similarly, the sensors 205, 210, and 215 also may input operational commands using different command languages, file types, or formatting preferences.
A sensor controller 222 may be implemented as part of the interface 220 that interacts with the sensors 205, 210, or 215 through a hardware abstraction layer 224, for example that acts as a proxy for the sensor(s). Such sensor controller(s) 222 also may be implemented directly in the sensors 205, 210, 215 themselves (not shown). In this latter case, the sensors 205, 210, 215 may act in a “plug-and-play” manner, in which the sensors 205, 210, 215 can be discovered, configured, and controlled through the network immediately upon being attached to the network.
The interface 220 communicates with a resolver 225 to transmit data pertaining to the various sensors. More specifically, the resolver 225, as discussed in more detail below, is generally operable to aggregate some or all of the data from the sensors 205, 210, and 215. By aggregating the data, more and/or more accurate information about a sensed object can be easily, quickly, and reliably obtained than if only one of the sensors 205, 210, or 215 were used, or if data from the various sensors were considered separately.
The resolver 225 may interact with the interface 220 through, for example, a high-speed, local information bus 227 that may be based on a publish/subscribe or point-to-point communication model. In the case where the sensor controller(s) 222 are implemented within the sensors 205, 210, and 215 themselves, the resolver 225 may be connected to the sensors directly through the local information bus 227. In cases where, for example, real-time requirements are in place, it may be desirable to connect the resolver to the sensors 205, 210, and 215 through, for example, a serial port or specialized network connection (not shown). In the latter two examples, some or all of interface 220 may be considered to be implemented within the resolver 225.
The resolver 225 combines and/or analyzes the sensor data based on information contained within a knowledge base 230. Knowledge base 230 may contain, for example, technical information about each of the sensors 205, 210, and 215, or information about what types of objects expected to be sensed, or information about characteristics of objects to be sensed. Knowledgebase 230 may be implemented using, for example, a relational database.
The resolver 225, in the implementation of system 200, combines data from the sensors 205, 210, and 215 using an aggregation engine 235. The aggregation engine 235 may use different techniques or combinations of techniques to aggregate the sensor data. For example, in situations such as the one shown in
Additionally, the aggregation engine 235 may aggregate sensor data based on the locations of the sensors 205, 210, and 215. For example, data from all sensors within a particular room may be grouped together. This technique may be useful for ensuring that all objects at the location are properly included within a specific object class. Moreover, the location information can be used in conjunction with the time information, in whatever manner is necessary to correlate the sensor outputs and obtain the desired information about the object being sensed. In aggregating the sensor data, aggregation engine 235 may discard any information which is determined to be redundant.
The resolver 225 also may include a rule engine 240. The rule engine 240 is operable to input the aggregated sensor data and apply a plurality of rules, based on information contained within knowledgebase 230, in order to determine a desired piece of information about the object, such as its identity or whether it has been tampered with or damaged.
Rule engines of various types exist in other contexts. For example, rule engines are often used to implement business rules representing business policies in applications including marketing strategies, pricing policies, product and service offerings, customer relationship management practices, and workflow management. Such rule engines may be written in a programming language such as Prolog, and are generally designed to implement assertions with preconditions. In other words, if all of a set of preconditions are met, then the assertion is determined to be true.
The rule engine 240 may operate in a somewhat similar manner, but serves to make inferences and judgments about the aggregated sensor data with respect to the sensed object(s), based on information contained in knowledgebase 230. For example, the rule engine 240 may know from knowledgebase 230 that a package having a certain identity (for example, a television in a box) should have a certain weight. If the rule engine 240 determines, using the aggregated sensor data from aggregation engine 235, that the camera 120 and the RFID reader 115 indicate that a television box is on the scale 130 that weighs significantly less than the expected value, then various responses can be indicated by the rule engine 240 (e.g., removing the box for human inspection, activating other sensors to double-check the result, and other actions described in more detail below with respect to
Some of the responses indicated by rule engine 240 may involve adjusting, activating, or deactivating one of the sensors 205, 210, or 215. In this case, resolver 225 also contains a sensor control system 245 which outputs the necessary commands to the particular sensor(s). More specifically, the sensor control system 245 may control the sensors 205, 210, and 215 by, in the example of
The rule engine 240 also may consider the number or type of sensor when analyzing the sensor data. For example, data from the camera 120 may generally be considered more reliable with respect to a certain characteristic than data from scale 130 (for example, whether the object has been tampered with). Therefore, if there is a conflict between these two sensors with respect to that characteristic, the rule engine 240 may prioritize the camera data. In other words, the rule engine 240 may weight the camera data more heavily, or may discard the scale data entirely. As another example, if the rule engine is comparing data from ten different sensors, a particular characteristic of an object may be determined as an average of data obtained from the sensors. Alternatively, the rule engine may determine that one sensor is outputting results that are inconsistent with the nine remaining sensors, and therefore discard the outlying result.
It should be understood that some of the functionality of determining which sensor data to use or discard, or how to combine the sensor data with respect to a reliability of a particular sensor in a particular situation, could similarly be performed in the aggregation engine 235. Generally speaking, however, the aggregation engine 235 may be more suited to utilize such factors with respect to the sensors and without comparable regard for the particular object currently being detected. In other words, aggregation engine 235 may be more suited for calculations that are broadly applicable to the available sensor array, whereas rule engine 240 may be more suited for situation or object-specific determinations.
In analyzing sensor data, a sensor behavior system 250 also may be utilized. Sensor behavior system 250 determines information about particular sensors that may be used by aggregation engine 235 and/or rule engine 240 in performing their respective functions. Sensor behavior system 250 may, or example, compile statistics about individual sensors, such as the number of times data from a particular sensor was discarded due to inconsistencies between that sensor data and simultaneously-collected sensor data, as determined by aggregation engine 235 and/or rule engine 240.
By performing such statistical analysis on the sensor data, sensor behavior system 250 may allow resolver 225 to learn and improve its performance over time, and/or may allow resolver 225 to alert an operator for system maintenance. For example, if sensor behavior system 250 determines that sensor 205 has provided inaccurate or unusable data for the last five sensing operations, then the sensor behavior system 250 may alert an operator to remove sensor 205 for repair or replacement.
It should be understood that sensor behavior system 250 may employ techniques aside from statistical analysis. For example, the sensor behavior system 250 may utilize Artificial Intelligence (“AI”) techniques and/or agent technology to learn about and/or modify the sensors' behavior over time.
Rules in rule engine 240 for comparing aggregated sensor data from aggregation engine 235 to expected results stored in knowledgebase 230 may vary greatly in terms of number and complexity. Some of the quantity and complexity of the rules can be, in effect, implemented within knowledgebase 230, depending on the capabilities of the particular rule engine 240 being utilized.
For example, in a simple form, knowledgebase 230 may simply be a database listing expected items and their expected characteristics. In this case, rule engine 240 would require many rules to determine what to do if one or more of the expected characteristics is missing or inaccurate. In a different example, knowledgebase 230 may contain many variations of expected characteristics for expected objects, possibly along with explicit instructions as to what to do in each situation. In this latter example, rule engine 240 would, in most cases, simply have to determine which of the variations of the expected values exists with respect to current sensor data, and implement the knowledgebase 230 instructions accordingly.
Once the sensor data has been appropriately combined, rules may be applied accordingly by rule engine 240 (320). Rule application may include, as discussed in more detail above, further refining of the available data and a comparison of the data to expected values contained in the knowledgebase 230.
Rule engine 240 next analyzes the sensor data for conflicts (325). If no conflicts between the sensor data and the expected values in knowledgebase 230 exist, then the sensor data is deemed reliable and an identity or other characteristic of the sensed object is output (330). If conflicts do exist, then a number of options may be implemented. For example, a conflict resolution process may be started (335).
Conflict resolution involves several different options. For example, if the conflict is one sensor providing outlying data with respect to a number of other sensors, then a conflict resolution may be to simply discard the outlying data. This solution may be supported by, for example, data from sensor behavior system 250 indicating that the sensor in question has had low reliability ratings. As another example, if possible (e.g., if the object is still in an appropriate physical location), the sensor control system 245 may be activated in order to instruct the sensor in question to re-obtain the disputed data, or to adjust the sensor to obtain the same data in a different manner (for example, re-adjusting a camera to focus on a different portion of the object).
In addition to, or alternatively from, conflict resolution is the process of exception handling (340). In exception handling, it is determined that a problem may exist with the object itself, as opposed to the sensors. In this case, the object may be removed for human inspection, at which point it may be repaired and replaced, or discarded.
For example, in
Once the sensor data has been appropriately combined, rules may be applied accordingly by rule engine 240 (420). Rule application may include, as discussed in more detail above, further refining of the available data and a comparison of the data to expected values contained in the knowledgebase 230.
Rule engine 240 next determines whether additional sensor data is required (425). If no additional data is required, then an identity of or other characteristic of the object may be output (430).
Additional sensor data may be needed for a variety of reasons. For example, a rule may exist that certain objects require additional sensor data, in order to improve accuracy in sensing those objects (e.g., some objects sensed by a camera may require different or more specific focusing of the camera). This additional sensor data may only be required in specific instances, such as particular environmental conditions (e.g., in inadequate lighting, a camera may require that its contrast be adjusted to improve image accuracy, or, in warm environments, a temperature sensor may be activated to check that an object's temperature is being maintained below a pre-determined level).
As another example, some sensors may be relatively more expensive to utilize, and so may only be activated when necessary, such as when additional information about a particular object is needed. In this way, for example, an expensive sensor such as a camera can be shared between a plurality of sensing situations, rather than requiring a separate camera for each of the situations.
As yet another example, some sensors are slower to operate than others, and so speed in a sensing process may be obtained by only activating the slower sensors for certain objects or in certain situations.
Thus, once it is determined that additional sensor data is needed, sensors may be adjusted in order to obtain that data (435). Additionally, or alternatively, additional sensors, not previously used in the process at all, may be activated in order to supplement the available data (440). Activation may include a command from sensor control system 245, or may include actual physical relocation of a new sensor into the sensor array. In the latter example, it should be understood that adding a new sensor is particularly convenient in the implementations associated with system 200 of
In conclusion, the above description has provided techniques for using a multi-sensor system to quickly, accurately, inexpensively, and reliably identify objects or object characteristics. Moreover, the techniques easily allow tradeoffs between these characteristics for situations in which one of the characteristics is very important. For example, accuracy can be improved to the detriment of speed and expense by activating additional sensors. Such adaptability is facilitated by the ease with which sensors can be added or removed from the system.
A number of implementations have been described. Nevertheless, it will be understood that various modifications may be made. Accordingly, other implementations are within the scope of the following claims.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US4974166||Dec 29, 1989||Nov 27, 1990||Asyst Technologies, Inc.||Processing systems with intelligent article tracking|
|US5166884||Nov 25, 1991||Nov 24, 1992||Asyst Technologies, Inc.||Intelligent system for processing and storing articles|
|US5469363||May 19, 1994||Nov 21, 1995||Saliga; Thomas V.||Electronic tag with source certification capability|
|US5834706||Aug 31, 1995||Nov 10, 1998||Christ; Ferdinand||Method and apparatus for verifying the contents of packages delivered to or leaving a warehouse|
|US5910765 *||Mar 22, 1995||Jun 8, 1999||Advanced Optical Controls, Inc.||Sensor module|
|US5936527||Feb 10, 1998||Aug 10, 1999||E-Tag Systems, Inc.||Method and apparatus for locating and tracking documents and other objects|
|US5963134||Jul 24, 1997||Oct 5, 1999||Checkpoint Systems, Inc.||Inventory system using articles with RFID tags|
|US5971592||Sep 27, 1996||Oct 26, 1999||Kralj; Nicholas L.||Integrated reusable pallet having data collection devices and method for using shipping conveyances|
|US6032127||Oct 21, 1997||Feb 29, 2000||Intermec Ip Corp.||Intelligent shopping cart|
|US6177860||Jul 10, 1998||Jan 23, 2001||International Business Machines Corporation||Method and economical direct connected apparatus for deploying and tracking computers|
|US6195006||Aug 27, 1999||Feb 27, 2001||Checkpoint Systems Inc.||Inventory system using articles with RFID tags|
|US6259367||May 1, 2000||Jul 10, 2001||Elliot S. Klein||Lost and found system and method|
|US6392536 *||Aug 25, 2000||May 21, 2002||Pittway Corporation||Multi-sensor detector|
|US6567162 *||May 31, 2001||May 20, 2003||The Regents Of The University Of Michigan||Reconfigurable apparatus and method for inspection during a manufacturing process|
|US6641042||Aug 22, 2000||Nov 4, 2003||Sick Ag||Method and an apparatus for the identification and localization of objects|
|US6643608 *||Feb 22, 2000||Nov 4, 2003||General Electric Company||System and method for collecting and analyzing shipment parameter data affecting predicted statistical variables of shipped articles|
|US20010000019||Nov 29, 2000||Mar 15, 2001||Bowers John H.||Inventory system using articles with RFID tags|
|US20030023337 *||Feb 21, 2001||Jan 30, 2003||Godfrey James William||Manufacturing method|
|US20030137968 *||Dec 20, 2002||Jul 24, 2003||Lareau Neil William||Monitoring and tracking of assets by utilizing wireless communications|
|DE4341880A1||Dec 8, 1993||Jun 14, 1995||Dinkel Doris||Objects e.g. clothing item control system|
|DE19623893A1||Jun 7, 1996||Dec 11, 1997||Florian Bischof||Transmission process for digitally coded data|
|DE19844631A1||Sep 29, 1998||Apr 6, 2000||Gantner Electronic Gmbh Schrun||System zur Überwachung, Steuerung, Verfolgung und Handling von Objekten|
|DE19951060A1||Oct 22, 1999||May 4, 2000||Dell Usa Lp||Integral automatic customer identification when connecting to customer web site involves using system-specific content from token substitution program installed on hard disc|
|DE19955120A1||Nov 16, 1999||May 23, 2001||Meinen Heinz F||Product documentation and identification method for transportable objects, by applying data carrier connected to sensors|
|EP0908643A2||Oct 7, 1998||Apr 14, 1999||Mitsubishi Jidosha Kogyo Kabushiki Kaisha||Energy absorbing member|
|GB2308947A||Title not available|
|WO2000045324A2||Jan 28, 2000||Aug 3, 2000||Sensormatic Electronics Corporation||Managing production and operations using read/write rfid tags|
|WO2000059648A2||Apr 6, 2000||Oct 12, 2000||Federal Express Corporation||System and method for dimensioning objects|
|WO2002047014A1||Oct 19, 2001||Jun 13, 2002||Sap Aktiengesellschaft||System, method, computer program product for communicating data for objects that are transported|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US7580767 *||Jul 11, 2005||Aug 25, 2009||Kla-Tencor Corporation||Methods of and apparatuses for maintenance, diagnosis, and optimization of processes|
|US7764191||Jul 26, 2005||Jul 27, 2010||Rockwell Automation Technologies, Inc.||RFID tag data affecting automation controller with internal database|
|US7772978||Aug 10, 2010||Rockwell Automation Technologies, Inc.||Intelligent RFID tag for magnetic field mapping|
|US7896030 *||Aug 26, 2005||Mar 1, 2011||Fujikin Incorporated||Sensor-equipped joint member|
|US7931197||Apr 26, 2011||Rockwell Automation Technologies, Inc.||RFID-based product manufacturing and lifecycle management|
|US7932827||Jun 16, 2008||Apr 26, 2011||Rockwell Automation Technologies, Inc.||Mobile RFID reader with integrated location awareness for material tracking and management|
|US7994919||Jun 10, 2009||Aug 9, 2011||Rockwell Automation Technologies, Inc.||Systems and methods that integrate radio frequency identification (RFID) technology with agent-based control systems|
|US7997475||Aug 16, 2011||Rockwell Automation Technologies, Inc.||Systems and methods that integrate radio frequency identification (RFID) technology with industrial controllers|
|US8025227||Sep 30, 2005||Sep 27, 2011||Rockwell Automation Technologies, Inc.||Access to distributed databases via pointer stored in RFID tag|
|US8152053||Mar 12, 2009||Apr 10, 2012||Rockwell Automation Technologies, Inc.||RFID architecture in an industrial controller environment|
|US8200563||Aug 6, 2009||Jun 12, 2012||Chicago Mercantile Exchange Inc.||Publish and subscribe system including buffer|
|US8260052||Nov 30, 2010||Sep 4, 2012||Raytheon Company||Object identification via data fusion|
|US8260948||Sep 4, 2012||Rockwell Automation Technologies, Inc.||Enhanced controller utilizing RFID technology|
|US8384544||Jun 10, 2009||Feb 26, 2013||Rockwell Automation Technologies, Inc.||Systems and methods that integrate radio frequency identification (RFID) technology with agent-based control systems|
|US8468111||Nov 30, 2010||Jun 18, 2013||Raytheon Company||Determining confidence of object identification|
|US8595177||Mar 8, 2011||Nov 26, 2013||Raytheon Company||Risk management for object identification|
|US8947224 *||Oct 21, 2008||Feb 3, 2015||Paksense, Inc.||Environmental data collection|
|US20070005173 *||Aug 10, 2004||Jan 4, 2007||Kanitz William A||System and method for site-specific electronic recordkeeping|
|US20070055403 *||Jul 11, 2005||Mar 8, 2007||Macdonald Paul D||Methods of and apparatuses for maintenance, diagnosis, and optimization of processes|
|US20070192230 *||Mar 13, 2006||Aug 16, 2007||Chicago Mercantile Exchange||Match System that Uses a Non-Indexed Collection of Orders|
|US20070295414 *||Aug 26, 2005||Dec 27, 2007||Fujikin Incorporated||Sensor-Equipped Joint Member|
|US20090066505 *||Oct 21, 2008||Mar 12, 2009||Paksense, Inc.||Environmental data collection|
|US20090127325 *||Feb 29, 2008||May 21, 2009||Rockwell Automation Technologies, Inc.||Systems and methods that integrate radio frequency identification (rfid) technology with industrial controllers|
|US20090292506 *||Aug 7, 2009||Nov 26, 2009||Kla-Tencor Corporation||Methods of and apparatuses for maintenance, diagnosis, and optimization of processes|
|US20090299914 *||Aug 6, 2009||Dec 3, 2009||Chicago Mercantile Exchange Inc.||Publish and Subscribe System Including Buffer|
|US20100164680 *||Dec 31, 2008||Jul 1, 2010||L3 Communications Integrated Systems, L.P.||System and method for identifying people|
|DE102014206742A1 *||Apr 8, 2014||Oct 8, 2015||Bayerische Motoren Werke Aktiengesellschaft||Konfigurierbare Datenerfassung|
|WO2007030394A2 *||Sep 5, 2006||Mar 15, 2007||Rockwell Automation Technologies, Inc.||Sensor fusion for rfid accuracy|
|U.S. Classification||340/522, 705/28, 340/506, 340/572.1, 700/115|
|International Classification||G06K17/00, G08B19/00|
|Cooperative Classification||G06Q10/087, G06K17/0022|
|European Classification||G06Q10/087, G06K17/00G|
|Oct 27, 2003||AS||Assignment|
Owner name: SAP AKTIENGESELLSCHAFT, GERMANY
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:HALLER, STEPHAN;REEL/FRAME:014077/0937
Effective date: 20030820
|Jan 14, 2010||FPAY||Fee payment|
Year of fee payment: 4
|Dec 23, 2013||FPAY||Fee payment|
Year of fee payment: 8
|Aug 26, 2014||AS||Assignment|
Effective date: 20140707
Free format text: CHANGE OF NAME;ASSIGNOR:SAP AG;REEL/FRAME:033625/0334
Owner name: SAP SE, GERMANY