Host cache for haptic feedback effects

• US 6,715,045 B2
• Filed: 01/29/2002
• Issued: 03/30/2004
• Est. Priority Date: 11/14/1997
• Status: Expired due to Term

• Current Assignee: Immersion Corporation Delaware
• Original Assignee: Immersion Corporation
• Inventors: Beamer, Jonathan L., Chang, Dean C., Braun, Adam C.
• Primary Examiner(s): Kim, Matthew
• Assistant Examiner(s): Anderson, Matthew D.
• Application Number:
  US10/060,472
• Publication Number:
  US 20020095224A1
• Time in Patent Office: 791 Days
• Field of Search: 711/118, 711/133, 711/134, 711/135, 711/136, 711/167, 711/154, 711/159, 710/57, 341/20, 341/27, 345/701, 345/702
• US Class Current: 711/154
• CPC Class Codes: G05B 19/00 Programme-control systems
• CPC Class Codes: G06F 2203/013 Force feedback applied to a game
• CPC Class Codes: G06F 2203/014 Force feedback applied to GUI
• CPC Class Codes: G06F 2203/0333 Ergonomic shaped mouse for one hand
• CPC Class Codes: G06F 3/011 Arrangements for interaction with the human body, e.g. for user immersion in virtual reality blind teaching G09B21/00
• CPC Class Codes: G06F 3/016 Input arrangements with force or tactile feedback as computer generated output to the user
• CPC Class Codes: G06F 3/03543 Mice or pucks G06F3/03541 takes precedence
• CPC Class Codes: G06F 3/03548 Sliders, in which the moving part moves in a plane
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/75 Indicating network or usage conditions on the user display
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]

Abstract

Methods and apparatus for efficient management of memory in a haptic feedback system including a host computer and a haptic feedback device. A representation of device memory is maintained on the host computer to allow the host computer knowledge of force effects stored in the device memory. A host cache for force effects is provided to allow larger numbers of force effects to be created for the device, where force effects not able to fit in device memory can be stored in the host cache.

Claims

1. A method comprising:

creating a representation of a device memory in a computer memory;

storing a force effect in a cache allocated in said computer memory;

determining whether said device memory can store said force effect by examining said representation of said device memory; and

sending said force effect to said device memory.

2. A method as recited in claim 1 wherein said force effect is sent to said device memory only if said device memory can store said force effect.

3. A method as recited in claim 2 wherein determining whether said device memory can store said force effect comprises:

comparing a priority of said force effect with a priority of a loaded force effect already stored in said device memory; and

sending said force effect if said priority of said force effect is greater than said priority of said loaded force effect.

4. A method as recited in claim 1 further comprising storing a plurality of force effects in said cache in said computer memory regardless of whether said device memory comprises sufficient space to store said plurality of force effects.

5. A method as recited in claim 1, further comprising delaying the sending of said force effect to said device memory if said device memory is full.

6. A method as recited in claim 1, further comprising:

storing a plurality of force effects in said computer memory;

sending one of said plurality of force effects to to said device memory when said one of said plurality of force effects is to be played; and

replacing a force effect stored in said device memory with said one of said plurality of force effects.

7. A method comprising:

receiving a force effect create command;

sending a force effect data corresponding to said force effect create command to a device memory if said device memory comprises a sufficient space to store said particular force effect data; and

storing said force effect data in a cache allocated in a computer memory if said device memory does not comprise said sufficient space.

8. A method as recited in claim 7 further comprising:

receiving a command to output a force effect; and

swapping said force effect data with a loaded force effect data in said device memory.

9. A method as recited in claim 8, further comprising storing a representation of said device memory in said computer memory.

10. A method as recited in claim 9, further comprising examining said representation to determine if said device memory comprises said sufficient space.

11. A method as recited in claim 9 wherein said representation and said device memory each comprises an effect block and a parameter block, wherein an identifier of saidforce effect is stored in said effect block and at least one parameter for said force effect is stored in said parameter block.

12. A method as recited in claim 7, further comprising:

querying haptic feedback device comprising said device memory; and

receiving a response indicating whether said device memory comprises said sufficient space.

13. A method as recited in claim 7, further comprising associating a waiting status with said force effect data if said device memory does not comprise said sufficient space.

14. A system comprising:

a haptic feedback device comprising a device memory; and

a computer in communication with said haptic feedback device, said computer comprising system memory in which a cache is implemented, wherein said cache stores a force effect data if said device memory does not have said sufficient space.

15. A system as recited in claim 14 wherein said cache comprises a representation of said device memory.

16. A system as recited in claim 15 wherein said representation and said device memory each comprises an effect block and a parameter block, wherein an identifier of said force effect is stored in said effect block and a parameter for said force effect is stored in said parameter block.

17. A system as recited in claim 14, further comprising a driver said computer for receiving a force effect create command.

18. A system as recited in claim 17 wherein said driver creates a representation of said device memory in said system memory, wherein said driver examines said representation to determine if said device memory has said sufficient space.

19. A system as recited in claim 14 wherein if said force effect is stored in said cache and said force effect is to be played, said force effect data is swapped with a loaded force effect in said device memory.

20. A system as recited in claim 14 wherein when said device memory does not have sufficient space, said force effect is given a waiting status such that said force effect data for said force effect is sent to said device memory at a later time.