[go: up one dir, main page]

WO2006054318A2 - Procede unique d'incorporation d'un processus commercial et d'une intelligence de processus commercial dans un reseau rfid - Google Patents

Procede unique d'incorporation d'un processus commercial et d'une intelligence de processus commercial dans un reseau rfid Download PDF

Info

Publication number
WO2006054318A2
WO2006054318A2 PCT/IN2005/000368 IN2005000368W WO2006054318A2 WO 2006054318 A2 WO2006054318 A2 WO 2006054318A2 IN 2005000368 W IN2005000368 W IN 2005000368W WO 2006054318 A2 WO2006054318 A2 WO 2006054318A2
Authority
WO
WIPO (PCT)
Prior art keywords
rfid
business process
business
transponder
tag
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/IN2005/000368
Other languages
English (en)
Other versions
WO2006054318A8 (fr
Inventor
Tiruvadi Yegnan Kaushik
Kancherla Surendra
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Individual
Original Assignee
Individual
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Individual filed Critical Individual
Publication of WO2006054318A2 publication Critical patent/WO2006054318A2/fr
Anticipated expiration legal-status Critical
Publication of WO2006054318A8 publication Critical patent/WO2006054318A8/fr
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/08—Logistics, e.g. warehousing, loading or distribution; Inventory or stock management

Definitions

  • BUSINESS PROCESS INTELLIGENCE INTO RFID GRID Present invention relates to embedding business process and business process intelligence into RFID hardware device (Radio Frequency Identification) grid which is an integral and central part of a RFID based business solution for any business or functional area.
  • RFID hardware device Radio Frequency Identification
  • the present invention relates to a system that allows definition and execution of any business process and business process intelligence involving tracking of moveable and immoveable physical objects to be embedded into an RFID (Radio Frequency Identification) grid built of RFlD (Radio Frequency Identification) devices deployed across the environment that covers the overall process, there by providing the flexibility to define any application for any business or functional area, to incorporate any changes to the existing business process rules or business process intelligence.
  • RFID Radio Frequency Identification
  • RFlD Radio Frequency Identification
  • the object of the present invention is to facilitate RFID end-users who need flexibility to define their own business process into RFID grid and change the same as needed.
  • the purpose of the present invention is facilitating Application/Solution developers who have domain knowledge of a given area and build such solutions based on Business Process Embedding Methodology.
  • the present invention is directed to facilitate RFID end users, who need to comply with a number of industry and federal mandates.
  • Radio frequency identification (“RFID”) Transponder (Tag) s and radio frequency identification Transponder (Tag) systems are known, and find numerous uses.
  • RFID radio frequency identification
  • RFID s are frequently used for personal identification in automated gate sentry applications protecting secured buildings or areas.
  • Information stored on the radio frequency identification Transponder (Tag) identifies the person seeking access to the secured building.
  • Older systems require the person accessing the building to insert or swipe a programmed identification Transponder (Tag) into or through a Reader for the system to read the information from the identification Transponder (Tag).
  • Radio frequency identification Transponder (Tag) conveniently reads the information from the radio frequency identification Transponder (Tag) at a small distance using radio frequency (“RF”) data transmission technology eliminating the inserting or swiping operation.
  • RF radio frequency
  • radio frequency identification Transponder s are capable of retaining and, in operation, transmitting a substantial amount of information- sufficient information to uniquely identify individuals, packages, inventory and the like.
  • a radio frequency identification Transponder includes stored Transponder (Tag) information and at least one antenna element.
  • the Transponder (Tag) also includes a programmable Transponder (Tag) circuit state that is either “on” or “off” based on an "on/off command signal received by the antenna element.
  • the Transponder (Tag) circuit state is "on,” upon receiving an exciter signal from a proximately located electrostatic exciter the Transponder (Tag) becomes energized, thereby causing it to generate a read signal containing a carrier signal and based on the stored Transponder (Tag) information.
  • the antenna element then electro statically sends the read signal to a proximately located Transceiver (Reader), which detects the carrier signal, and, under proper conditions, also the stored Transponder (Tag) information.
  • Radio frequency identification technology has been developed by a number of companies, including Motorola/lndala (U.S. Pat. Nos. 5,378,880 and 5,565,846) Texas Instruments (see U.S. Pat. Nos. 5,347,280 and 5,541 ,604).
  • These Transponder (Tag) s all attempt to provide remote identification without the need for a battery.
  • Systems based on these markers generally operate reliably only when a single Transponder (Tag) is in the interrogation zone at a time. They also tend to be relatively bulky and expensive to manufacture.
  • RFID Transponder RFID Transponder
  • RFID Transponder s may be passive or active.
  • the Transponder (Tag) includes circuitry for converting at least a portion of the received RF signals into electrical power needed by the Transponder (Tag) for signal processing and transmission.
  • RFID Transponder s containing information associated with the identities of inventory items to be tracked is attached to the inventory items.
  • An RFID Transceiver (Reader) is used to detect the presence of an RFID Transponder (Tag) and read the identification information from the Transponder (Tag).
  • a typical RFID Transceivers includes an RF Transceivers (Reader) for transmitting interrogation signals to and receiving response signals from RFID Transponder (Tag) s, one or more antennae connected to the Transceivers (Reader), and associated decoders and encoders for reading and writing the encoded information in the received and transmitted RF signals, respectively.
  • the Transceivers (Reader) may be a portable device, which can be brought near the Transponder (Tag) s to be read, or it may be a stationary device, which reads the Transponder (Tag) s as they are brought to the Transceivers (Reader), as in the case of tagged library books being returned to a return station that is fitted with a Transceiver (Reader).
  • RFID Transponder (Tag) s may also be affixed near a location as a location marker. After detecting both a Transponder (Tag) attached to an inventory item and a location marking Transponder (Tag), a processing unit associated with the Transceivers (Reader) may determine that the inventory item is positioned near the tagged location. While these conventional object tracking systems are capable of keeping a record of the inventory items and sometimes their locations, they are not effective for tracking and/or managing the movement of the inventory items.
  • an object tracking and management system and method using radio-frequency identification (“RFID”) Transponder (Tag) s comprises objects to be moved between locations are outfitted with RFlD Transponder (Tag) s having information relating to the identities of the objects. The locations are also marked by RFID Transponder (Tag) s containing information on the locations.
  • RFID Transponder (Tag) s containing information on the locations.
  • a transport vehicle for moving the objects is equipped with an RFID Transceiver (Reader) capable of detecting signals from the RFID Transponder (Tag) s.
  • An onboard processor provides the operator of the vehicle with instructions on the movement of objects. The processor also determines the identities of the objects and locations from the detected signals and provides the operator with feedback as to the identity of an object being moved, the location of the vehicle and any error in carrying out the instructions.
  • the preferred embodiment includes a single wound radio frequency identification antenna coil; a radio frequency transmitter; a power control, system timing and driver including a low battery indicator, and an optical switch; a rechargeable battery; a main power switch; an infrared activation switch; a radio frequency link antenna, a receiver analog section, a micro controller, an exciter drive and a read switch; and audio feedback to confirm receipt of data (US 6,329,920)
  • An XML system to transparently interact with various hardware devices like barcode Reader, RFID Transceiver etc., through XML input streams is described.
  • An XML system is configured to print bar code labels, tickets, cards or other media, and/or encoded RFlD devices embedded in the media, based upon an extensible markup language (XML) input data stream.
  • XML extensible markup language
  • This system generates a printable representation of the bar code label, tag, ticket, card, and other media and/or generates encoding information for an RFID device.
  • This system describes a common method to present data to the data capture devices mentioned above and does not address any business context or process aspects.
  • the Data Acquisition Device is an integrated casing which houses a Magnetic Stripe Card Reader, an Optical Scanner, an Electronic Signature Pad and a Smart Card Reader, which may be an RFID, enabled device.
  • This device is cable of collecting data from all the mentioned technologies seamlessly and passing on such data to a computer system the Data Acquisition Device is connected to. This does not address the various ways to handle data after capturing such data and is operational at a hardware level (US patent application publication number - US2005139668A1)
  • Hard-coded business processes do not accommodate any changes in the business process itself or any changes in the way various processes interact.
  • the present invention relates to a business process and business process intelligence that is combined with RFID grid to allow the business process to track the turnover of movable and immovable physical objects and embedding it into an RFID (Radio Frequency Identification) grid, built of RFID (radio Frequency Identification) devices that deploys all across the environment to cover the overall process, thereby providing the flexibility to define any application and to incorporate changes, if any, to the process grid.
  • RFID Radio Frequency Identification
  • a unique method for embedding business process into RFID Grid comprising of RFID Transceiver (Reader) s, including antennae that reads RFID Transponders (Tags) of multiple frequencies and multiple protocols; a computer program is developed and is used to automatically discover, configure and control the RFID hardware Devices; these RFID devices namely RFID Transceiver (Reader) s, printers, antennae are attached to the Computer memory system for storing discovery, configuration, control and data; the data collected by these RFID devices are automatically formatted within the system; thereafter a computer program is used to automatically and remotely receive data from the system and to automatically generate a graphical display of all RFID hardware devices; these RFID hardware devices that are attached to the Computer Systems facilitates in running the system and permit them to create representative physical locations as zones; another computer program that embeds location information in terms of physical business context and zone definitions into RFID devices consists of two:
  • the system includes the following:
  • PCM Physical Contexting Module
  • PCM is a software code running on a PC.
  • PCM is responsible for assigning unique IDs to the RFID hardware devices and creating a Device Grid in terms of physical locations (Zones) in business terminology.
  • PCM embeds the Zones into the devices.
  • ADC Engine expanded in Fig 2: Auto Discovery and Configuration Engine is responsible for discovering the devices, configuring and assigning a unique identity to the same and other device interaction activities like Read from the device, Write to the device etc., connected to a PC or connected to a LAN same as that of such PC running PCM. This identifies details like Manufacturer, Model, Operating Frequency, Protocol, Communication parameters etc.
  • Auto Discovery and Configuration Engines comprises
  • Controller uses the specific details discovered by Auto Discovery to communicate with the RFID devices and carry on specific actions as required by the users.
  • MR is responsible for communication between ADC Engine and other modules and sub modules. MR interacts with Grid Builder and Business Process Execution Engine. Internally MR passes requests from Grid Builder and BPE to all other sub modules of ADE.
  • ADC Engine Auto Discovery and Configuration Engine performs the following functions:
  • Grid Builder GB is responsible for gathering configuration details of all the devices and displaying the Device Grid. GB is also responsible for converting user inputs on Zone definitions and passing the same on to ADC Engine for embedding the definitions into the RFID hardware. GB displays the successfully configured Zones so that users can interact with the devices through the displayed Zone Map as user does not need to know technical details like Device ID, Device Type, Manufacturer etc., Grid Builder: Grid Builder performs the following functions:
  • Zone Map (A sample Zone Map is shown in Fig 10)
  • Fig 3 Business Contexting Module: This module is responsible for creating Classes and assigning them a set of characteristics. These definitions are used while writing the Transponders (Tags). This module is also responsible for defining Hierarchy (5) and Association rules (6). Every time a Transponder (Tag) is read, the hierarchy and association rules are applied to the specific Transponder (Tag) for validating if all the rules are satisfied or not.
  • Object Classifier (4) groups various objects in the users' environment that are to be tagged, into Classes.
  • Object Classifier (expanded in Fig. 4): Object Classifier groups various objects in the users' environment that are to be tagged, into Classes. Object Classifier Details: Describes the constituents of OC. Object Classifier defines various Classes, their characteristics and maps the same. OC also identifies the Transponder (Tag) type used for Tagging a specific objects, validates if the Transponder (Tag) type falls in line with other definitions like Mandate Compliance Preparatory, number of characteristics to be written on to the Transponder (Tag) and checks if the data size matches available memory blocks on the Transponder (Tag). This also checks for Transceiver (Reader) and Transponder (Tag) type/protocol compliance.
  • Transponder Transponder
  • Object Classifier has the following sub components: Object Definition Module (7): Creates Classes and defines characteristics for each class
  • All the moving and moveable objects in the users' environment are grouped into Classes based on shared characteristics.
  • Employees of a division employees of the same rank, tooth paste 200 gms blue gel, tooth paste 200 gms red gel etc.
  • This sub modules defines all such Classes.
  • Each Class has a given set of characteristics that are shared across all the objects that belong to this Class.
  • Object Definition modules allows definition of the number of characteristics, type of each characteristic (text, number, date, time, email address etc.,), where to derive this from during the run time (a specific set of values either manually entered or taken from an existing data base - eg. all employee code from HRMS)
  • CM Engine maps the set of characteristics defined for each Class to all the Objects that belong to the Class. All the characteristics defined above are mapped to specific objects that belong to the relevant Class.
  • specific values of the characteristics are assigned to each Transponder (Tag).
  • a reference to the Transponder (Tag) ID and a pointer to the set of values are mapped and stored internally. The values can also be stored on the Transponder (Tag) without a reference to a table if the Transponder (Tag) memory matches the data size.
  • every Transponder (Tag) read is scanned for the Transponder (Tag) ID and the same is used to retrieve assigned values of the characteristics.
  • CM engine is responsible for these run time functions.
  • Transponder (Tag) Identifier and Configuration (9) This is responsible for identifying the Transponder (Tag) details like Transponder (Tag) type, Protocol, usable memory space, data blocks etc., and correlates the same with the data (Values of Characteristics defined for a Class) to be written on to the Transponder (Tag). This also validates if the Transponder (Tag) type falls in line with other definitions like Mandate Compliance Preparatory, number of characteristics to be written on to the Transponder (Tag) and checks if the data size matches available memory blocks on the Transponder (Tag). This also checks for Transceiver (Reader) and Transponder (Tag) type/protocol compliance.
  • Mandate Compliance Preparatory (10) This is responsible for setting up requisite parameters to comply with various mandates - eg. Wal-Mart mandate, DoD mandate etc., each mandate has a set of parameters that are one-time configurable and other data format and data exchange requirements.
  • This module prepares the environment for mandate compliance by including one-time definitions like CAGE code, Company Prefix and Item Reference Numbers. The suppliers invoke the compliance environment thus created while writing Transponders (Tags) for mandate complaint consignments.
  • Hierarchy Builder (5) This organizes the classes according to the existing hierarchy in the users' business environment. Hierarchy builder works on Class definitions only and not on objects. A defined hierarchy works as a skeleton and when the Tagged objects are sensed by the RFID devices, Association Engine uses the Hierarchy skeleton to validate if all the Tagged objects are falling within the Hierarchy definitions.
  • Association Engine (6) This correlates all the Classes assigned to Hierarchy definitions, and specific objects that belong to the Classes. Association Engine also interacts with BPE engine for sending hierarchy validations out.
  • Item Class is a child of Case Class, which in turn is a child of Pallet Class.
  • Another example is Employee-Laptop.
  • Laptop Class is a child of Employee Class - in this scenario, a given Laptop (an object of Laptop Class) may be assigned to multiple employees (Empl ⁇ yeel and his/her boss) defining a multiple parent relationship. Multiple parent relationship is not possible in cases like Pallet-Case-Item Hierarchy.
  • Fig 5 Business Process Definition Module: This module is responsible for defining users' business process by using the context definitions from PCM and BCM. These definitions are stored in Business Process Archive, to be used by Business Process Execution Engine during run time. This module ensures that the defined process is based on process . elements like Zones, Classes, Hierarchy, Association etc that describe the users' environment and are defined in PCM and BCM. This also allows the users to set rules to the processes - Transitions Rules, Event Rules and Action Rules.
  • This module is responsible for defining users' business process by using the Zone, Class and Hierarchy definitions from PCM and BCM. All the physical locations in the users' business environment are mapped as Zones by embedding Zone definitions into RFID devices through Physical Contexting Module.
  • this module has the following components:
  • BPC derives Zone definitions from PCM and Class and Hierarchy definitions from BCM, builds process definitions based on Zones and Classes thus derived and creates process definition in BPEL and XML.
  • a process definition comprises a unique process name, various states that belong to the process, their transition rules, and event and action rules.
  • BP Archive (12) This is responsible for storing all the process definitions and interacting with BPE engine during the runtime.
  • BP Archive exchange references to various components of the process definition like Process Rules, Transition Rules, Event Rules, Action Rules and also the environmental parameters like Zones, Classes and Activities assigned to a specific State, States assigned to a given process etc with Business Process Execution Engine.
  • Fig. 7 Flow Chart 1 wherein
  • the Business Process Configurator assigns a unique ID each process.
  • BP Configurator has three predefined States - Start State as the starting State of a Process, End State as the last State of a Process and Normal State for any number of intermediary States. User selects various States and assigns unique names to the same.
  • BP Configurator has three predefined Activities - RFID Read, RFID Write and RFID Write/Read. User is prompted to assign Activity to the defined States.
  • BP Configurator derives Zone definitions from the PCM and prompts the user to assign the Zones to each State.
  • BP Configurator derives Class definitions from the BCM and prompts the user to assign the Classes to each State.
  • BP Configurator allows the user to move to the next step.
  • BP Configurator fetches all characteristics of the assigned Classes and prompts the user to define Event on the basis of the derived characteristics. Events are assigned to States.
  • Fig 6 Business Process Execution (13): This module is responsible for executing defined business processes. BPE derives process definitions from the BP Archive and executes the same. During execution, BPE interacts with PCM for Zone definitions and passing on relevant requests to the hardware devices (as defined in the process - Activities assigned to a State of a Process). BCE also interacts with BCM for Class and Hierarchy definitions, Association rules and mandate compliance preparatory. For each execution cycle, BPE engine refers to all of the modules mentioned.
  • BPE Engine is a software program running on a PC responsible for executing the defined business process. It may run on the same PC as other components
  • PCM/PCM/BPDE PCM/PCM/BPDE
  • BPE Engine fetches process definitions from BP Archive to a temporary storage with in itself. Once the user initiates a Process, the BPE Engine runs a continuous service that takes care of execution. Various steps in executing the process as shown in (Fig. 8) are as below:
  • the BPE Engine runs a continuous service that takes care of execution.
  • the service checks for the all the States, other components like Activities, Zones, Classes, Hierarchy and other Rules assigned to the Process.
  • BPE instructs the PCM to activate specific modes as defined in Activities on the RFID Transceiver (Reader) s that fall under the Zone definitions.
  • E.g. State 1 has read as the assigned Activity and Receiving Dock as the assigned Zone.
  • So BPE Engine instructs the PCM to activate read mode on the RFID Transceiver (Reader) s and Antennae that are embedded with IDs constituting Receiving Dock Zone. These activities are done separately for each mode - Read and Write, though the working is similar. Details are explained in relevant sections below.
  • the PCM controls the Transceiver (Reader) s and runs the same in the mode as instructed by the BPE Engine. For every Transponder (Tag) Read or Written within the Process Definition, a Process Instance is created by the BCM, which is alive for the life cycle of the tagged objects through all States of the current process.
  • BPE instructs the PCM to identify and activate Write as defined in Activities on the RFID Transceiver (Reader) s that fall under the Zone definitions.
  • State 1 has Write as the assigned Activity and Receiving Dock as the assigned Zone.
  • So BPE Engine instructs the PCM to activate write mode on the RFID Transceiver (Reader) s and Antennae that are embedded with IDs constituting Receiving Dock Zone. Starting the Controller process of ADE does this
  • the activated Controller sets the relevant RFID Transceiver (Reader) to write mode.
  • BPE fetches the details of the Classes, their characteristics, Transponder (Tag) Configuration, Hierarchy and Association details for the classes that belong to the State, from BCM.
  • BPE Engine sends all the above values on to the ADE, along with Transceiver (Reader) and Antenna Ids.
  • Controller sends the details to the RFID Transceiver (Reader) and instructs the Transceiver (Reader) to write into the Transponder (Tag).
  • Transponder (Tag) ID is associated with the Process, State, Zone, Class, specific Characteristics and Hierarchy by the BPE Engine. This completes the Write cycle.
  • BPE identifies all Zones assigned to the State from PCM, instructs the ADE to start Controller for relevant RFID Transceiver (Reader) s in the Zones.
  • Controller sends RFID Transceiver (Reader) IDs to the Controller along with instructions to set the Transceiver (Reader) to Read Mode.
  • Controller sets the RFID Transceiver (Reader) to Read mode.
  • BPE identifies the Process and current State in terms of State definitions.
  • BPE considers the Read only if the Process is a valid Process for the specific Transponder (Tag).
  • BPE checks if the current State of the Transponder (Tag) falls in line with Process Definitions by checking with the BP definition.
  • Stamp and other details are stored internally. (This is used for tracking the path of the tagged object.) If not, Events are generated.
  • BPE then executes Transition Rules for the current State 22. Based on Transition Rule's validity BPE updates the status of Transponder
  • Activity is the function to be undertaken during a particular state of the business process.
  • Association is the definition of the relation between Classes. • For example, one can associate Employee and Asset, Pallets and Cases etc.
  • Class is a set of uniquely identifiable RFID tagged objects or entities, within a particular business enterprise.
  • Hierarchy is the order of the Classes arranged in Levels.
  • Each Level has a set of unique Class names.
  • o START State It is the first State in the business process. For the above example the START State would be 'Receiving'.
  • NORMAL State This is the state following the START State. There can be many NORMAL States between START and END States but not more than 18. Please note that this is generic limitation assigned to SetuTM1.0 and is not limited due to any technology or technical reason.
  • o END State The last State of a business process is the END State Zone
  • a Zone indicates a unique business area of an enterprise in the functional context e.g. Warehouse, Packaging station etc.
  • Zones • A schematic representation of the environment displaying the all computers loaded with the computer programs mentioned in this document with details (type of ports, no. Of ports, etc.), readers connected to such computers with details (type of reader, etc.), antenna for readers (along with antenna id) clubbed in terms of logical groups shown as Zones.
  • JSP Java Server Pages
  • Struts for process definition
  • EJB Enterprise Java Beans
  • Jini Services for control interaction with various RFID devices
  • Java Messaging Service for Data extracting and transportation to and from the RFID devices.
  • the process is independent of software used and can be built using any programming language having the capabilities of all the components (JSP, Struts, EJB, Jini and JMS) mentioned above. Advantages of your invention:
  • a decision facilitated by applying business context as defined in this document can be executed by interaction with the RFID hardware devices by giving the devices feedback.

Landscapes

  • Business, Economics & Management (AREA)
  • Engineering & Computer Science (AREA)
  • Economics (AREA)
  • Quality & Reliability (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Human Resources & Organizations (AREA)
  • Marketing (AREA)
  • Operations Research (AREA)
  • Development Economics (AREA)
  • Strategic Management (AREA)
  • Tourism & Hospitality (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

Cette invention concerne un procédé unique d'incorporation d'un processus commercial dans un réseau RFID (identification par radiofréquence), qui permet de définir et d'exécuter n'importe quel processus commercial et n'importe quelle opération d'intelligence commerciale impliquant le suivi d'objets physiques mobiles et immobiles, à incorporer dans un réseau RFID constitué de dispositifs RFID déployés dans un environnement qui couvre le processus global, permettant ainsi de définir avec flexibilité n'importe quelle application pour n'importe quelle activité commerciale ou zone fonctionnelle, tout en permettant d'apporter des modifications aux règles existantes ou aux opérations d'intelligence existantes du processus commercial.
PCT/IN2005/000368 2004-11-19 2005-11-16 Procede unique d'incorporation d'un processus commercial et d'une intelligence de processus commercial dans un reseau rfid Ceased WO2006054318A2 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
IN1245MU2004 2004-11-19
IN1245/MUM/2004 2004-11-19

Publications (2)

Publication Number Publication Date
WO2006054318A2 true WO2006054318A2 (fr) 2006-05-26
WO2006054318A8 WO2006054318A8 (fr) 2008-06-19

Family

ID=36407552

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IN2005/000368 Ceased WO2006054318A2 (fr) 2004-11-19 2005-11-16 Procede unique d'incorporation d'un processus commercial et d'une intelligence de processus commercial dans un reseau rfid

Country Status (1)

Country Link
WO (1) WO2006054318A2 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11213773B2 (en) 2017-03-06 2022-01-04 Cummins Filtration Ip, Inc. Genuine filter recognition with filter monitoring system

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
No Search *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11213773B2 (en) 2017-03-06 2022-01-04 Cummins Filtration Ip, Inc. Genuine filter recognition with filter monitoring system

Also Published As

Publication number Publication date
WO2006054318A8 (fr) 2008-06-19

Similar Documents

Publication Publication Date Title
US7962096B2 (en) System and method for a RFID transponder file system
RU2463650C2 (ru) Архитектура, модель программирования и api
JP5328052B2 (ja) 情報技術資産のｒｆｉｄでの発見、追跡およびプロビジョニング
KR100945777B1 (ko) Ｒｆｉｄ 태그 에뮬레이션을 위한 내장형 시스템 아키텍쳐
Patel et al. Online students’ attendance monitoring system in classroom using radio frequency identification technology: a proposed system framework
US7504945B2 (en) Method and system for tracking and monitoring status of data storage subsystem components
WO2005045743A2 (fr) Systeme et procede d'integration d'un systeme rfid
JP2006072976A (ja) リーダーアプリケーションマークアップ言語スキーマ
MXPA05008254A (es) Arquitectura, modelo de programacion y apis.
US10878376B2 (en) Method and system to automatically track and manage assets using mobile devices
BRPI0609184A2 (pt) processo de recepção de rfid para uso com sistemas de planejamento de recursos empresariais
US7394379B2 (en) Unique method for embedding business process into RFID grid
CN101438330B (zh) 用于从企业资源规划系统服务器中设置rfid中间件服务器并与其通信的方法和系统
US7619521B2 (en) RFID network configuration program
US7898417B2 (en) Standardized mechanism for printing labels and managing templates within RFID
WO2006054318A2 (fr) Procede unique d'incorporation d'un processus commercial et d'une intelligence de processus commercial dans un reseau rfid
El Khaddar et al. Rfid middleware design and architecture
CN101609512A (zh) 基于射频识别的通用业务处理方法及系统
KR100766587B1 (ko) Ｒｆｉｄ관리 시스템 및 방법
CA2522931C (fr) Systeme et methode pour systeme de fichiers de transpondeur rfid
Bouhouche et al. A new middleware architecture for RFID systems
Repanovici et al. RFID-application in info-documentary systems
US20100214070A1 (en) System and Method for Tracking Items
Qian Mobile Assets Monitoring using RFID for UTAR Hospital
US20100141446A1 (en) Method and system for automatically tracking and controlling the usage of removable hard drives

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A2

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KM KN KP KR KZ LC LK LR LS LT LU LV LY MA MD MG MK MN MW MX MZ NA NG NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SM SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW

AL Designated countries for regional patents

Kind code of ref document: A2

Designated state(s): GM KE LS MW MZ NA SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LT LU LV MC NL PL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

NENP Non-entry into the national phase in:

Ref country code: DE

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 05849066

Country of ref document: EP

Kind code of ref document: A2

122 Ep: pct application non-entry in european phase

Ref document number: 05849066

Country of ref document: EP

Kind code of ref document: A2

WWW Wipo information: withdrawn in national office

Ref document number: 5849066

Country of ref document: EP