RELIABILITY OF EXECUTION FOR DEVICE PROVIDER IMPLEMENTATIONS

• US 20080001711A1
• Filed: 07/28/2006
• Published: 01/03/2008
• Est. Priority Date: 06/15/2006
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Sundaram, Jayaram Kalyana, Agarwal, Abhishek, Sriram, Balasubramanian, Ahmed, Mohamed Fakrudeen Ali, Goteti, Janaki Ram, Venkatesh, Ramachandran, Kumar, Anush, Sonnathi, Kalyan Chakravarthy
• Application Number:
  US11/460,809
• Publication Number:
  US 20080001711A1
• Time in Patent Office: Days
• US Class Current: 340/10.1
• CPC Class Codes: H04L 67/04 specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
• CPC Class Codes: H04L 67/12 specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
• CPC Class Codes: H04L 67/52 specially adapted for the location of the user terminal
• CPC Class Codes: H04W 4/02 Services making use of location information
• CPC Class Codes: H04W 4/80 Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication

Abstract

The claimed subject matter provides a system and/or a method that facilitates providing reliability associated with radio frequency identification (RFID) technology. An RFID network can include at least one device that wirelessly receives data from a tag. A provider component can have a dedicated execution space independent of an RFID server within a host allowing communication to at least one device within the RFID network.

Claims

1. A system that facilitates providing reliability associated with radio frequency identification (RFID) technology, comprising:

an RFID network that includes at least one device that wirelessly receives data from a tag; and

a provider component that has a dedicated execution space independent of an RFID server within a host to communicate to at least one device within the RFID network.

2. The system of claim 1, the RFID network comprises a collection of devices that form a sub-system which includes:

an RFID reader that receives an RFID signal; and

an RFID tag that transmits to at least one device.

3. The system of claim 1, the device is one of the following:

an RFID reader;

an RFID writer;

an RFID printer;

a reader;

a writer;

an RFID transmitter;

an antenna;

a sensor;

a real-time device;

an RFID receiver;

a real-time sensor;

a device extensible to a web service; and

a real-time event generation system.

4. The system of claim 1, further comprising a dedicated thread to transfer control from RFID server code to provider code.

5. The system of claim 4, further comprising a monitor component that ensures responsiveness of the dedicated thread.

6. The system of claim 5, the monitor component utilizes at least one of a ping and an amount of time to ensure responsiveness.

7. The system of claim 6, the monitor throws a timeout exception when the dedicated thread is abandoned.

8. The system of claim 7, the dedicated thread is abandoned when the provider component has at least one of the following:

an error;

a crash;

a corruption; and

a timeout.

9. The system of claim 4, the dedicated thread prevents a deadlock scenario.

10. The system of claim 9, the deadlock scenario is when a user code calls back into the RFID server and attempts to take a lock through a call that has already been taken.

11. The system of claim 9, the dedicated thread prevents the deadlock scenario by utilizing various components holding granular locks.

12. The system of claim 1, the provider component is associated with a particular device based on at least one of the following:

a make;

a model;

a function;

a type;

a version;

a size;

a serial number; and

a classification.

13. The system of claim 6, further comprising a provider manager within the RFID server that managers a plurality of provider components.

14. The system of claim 6, the plurality of provider components have respective RFID networks with at least one inclusive device.

15. The system of claim 1, further comprising a presentation component that provides at least one user interface to facilitate interaction between a user and the provider component.

16. The system of claim 1, the provider component is sandboxed within the host in comparison to the RFID server.

17. A computer-implemented method that facilitates improving the reliability associated with a radio frequency identification (RFID) technology, comprising:

implementing a provider in a host to communicate to a device within an RFID network; and

dedicating an execution domain for the provider independent of an RFID server within the host.

18. The method of claim 17, further comprising utilizing a dedicated thread to transfer control from the RFID server to the provider.

19. The method of claim 17, further comprising monitoring the thread to ensure responsiveness.

20. A computer-implemented system that facilitates improving the reliability associated with a radio frequency identification (RFID) technology, comprising:

means for wirelessly receiving data from a tag within a RFID network that includes at least one device; and

means for dedicating execution space for a provider component independent of an RFID server within a host to allow communication with the at least one device.