1. A heart valve sizing system comprising:
a lumen advanceable in vasculature;
an inside caliper device at a distal end of the lumen, the inside caliper device including:
a four bar linkage with first and second opposing pivot points and third and fourth opposing pivot points, and
a push rod connected to the second pivot point for alternatively urging the third and fourth pivot points together when extended and urging the third and fourth pivot points apart when retracted to gauge the inside dimension of the vasculature; and
means for reading the dimension gauged by the inside caliper device, the means for reading including:
a member connected on one end to the push rod,
a mechanism at the other end of the member which advances and retracts the member,
a position sensor which senses the position of the member, and
a readout device responsive to the position sensor which correlates the position of the member to the dimension gauged by the four bar linkage.
2. The system of claim 1 in which the position sensor is a potentiometer.
3. The system of claim 1 in which the readout device is a digital readout.
4. The system of claim 1 in which the member is a cable located inside the lumen.
5. The system of claim 1 in which the push rod is retractable into the lumen.
6. The system of claim 1 in which the four bar linkage is retractable into the lumen.
7. The system of claim 1 in which the lumen is attached to a handle including the mechanism, the position sensor, and the readout device.
8. The system of claim 7 in which the mechanism is a turning knob threaded into the handle and connected to the member.
9. A heart valve sizing system comprising:
a lumen advanceable in vasculature;
an inside caliper device at a distal end of the lumen including a four bar linkage, one pivot point of the four bar linkage connected to a push rod;
means for reading the dimension gauged by the four bar linkage when extended, the means for reading including:
a member connected on one end to the push rod,
a mechanism at the other end of the member which advances and retracts the member,
a position sensor which senses the position of the member, and
a readout device responsive to the position sensor which correlates the position of the member to the dimension gauged by the four bar linkage.
10. A heart valve sizing system comprising:
a lumen advanceable in vasculature;
an inside caliper device at a distal end of the lumen;
a member connected to the inside caliper device advanceable and retractable within the lumen;
a position sensor at a proximal end of the lumen which senses the position of the member; and
a readout device responsive to the position sensor which correlates the position of the member to the dimension gauged by the inside caliper device.
11. The system of claim 10 in which the inside caliper device includes:
a four bar linkage with first and second opposing pivot points and third and fourth opposing pivot points, and
a push rod connected to the second pivot point for alternatively urging the third and fourth pivot points together when extended and urging the third and fourth pivot points apart when retracted to gauge the inside dimension of the vasculature.
12. A heart valve sizing system comprising:
a catheter advanceable in vasculature;
a handle at a proximal end of the catheter;
an inside caliper device at a distal end of the catheter including a four bar linkage;
means for extending the inside caliper device to gauge the inside dimension of the vasculature and for retracting the inside caliper device to advance the inside caliper device in the vasculature, the means for extending and retracting including a push rod connected to one pivot point of the four bar linkage and a member connected on one end to the push rod and extending to the handle; and
means, at the handle, for detecting the extent of extension of the inside caliper device to measure the inside dimension of the vasculature, said means for detecting including a sensor in the handle configured to sense the position of the member.
13. The system of claim 12 in which the means for extending and retracting further includes a knob connected to the member.
14. The system of claim 12 in which the means for detecting further includes a readout on the handle responsive to the sensor.
15. A heart valve sizing system comprising:
a lumen advanceable in vasculature;
an inside caliper device at a distal end of the lumen, said inside caliper device retractable into the lumen; and
means for reading the dimension gauged by the inside caliper device at a proximal end of the lumen, said means for reading including a member connected to the inside caliper device and a position sensor which senses the position of the member.
The claims below are in addition to those above.
All refrences to claim(s) which appear below refer to the numbering after this setence.
1. A method for synchronous processing of commands in a hardware-independent proxy layer of a mobile telephone comprising the proxy layer, a hardware-specific driver layer, a client application, and a radio, the method comprising:
receiving from the client application a function call of a first application program interface (API), wherein the first API is associated with a function to be performed by the radio;
waiting to receive a first result notify event indicating that the function has been performed; and
after receiving the first result notify event, passing to the client first result data associated with the first result notify event.
2. The method of claim 1, further comprising:
translating the first API into an inputoutput control (IOCTL) code; and
sending the IOCTL code to the driver layer.
3. The method of claim 1, further comprising:
passing the first result data directly to the client application.
4. The method of claim 1, wherein the proxy layer comprises a main thread and a notify thread, the main thread passes the first result data to the client application, and the notify thread receives a first notify event from the driver layer and passes the first result notify event to the main thread.
5. The method of claim 4, further comprising:
receiving from the client application a function call of a second API, wherein the second API is associated with the function to be performed by the radio;
receiving a second notify event that passes to the notify thread second result data associated with the second result notify event; and
conveying the second result data from the notify thread to the client application using a result callback function.
6. The method of claim 5, further comprising:
returning to the client application a first response identifier to indicate that the driver layer has accepted an operation request associated with the second API.
7. The method of claim 6, wherein the result callback function includes a second response identifier having a value that is the same as that of the first response identifier.
8. A mobile telephone comprising:
a client application;
a radio;
a hardware-independent proxy layer and
a hardware-specific driver layer,
wherein the proxy layer is adapted to synchronously process function calls of application program interfaces (APIs) associated with functions to be performed by the radio.
9. The mobile telephone of claim 8, wherein the proxy layer is adapted to receive from the client application a function call of a first application program interface (API), wherein the first API is associated with a function to be performed by the radio, to wait to receive a first result notify event indicating that the function has been performed, and to pass to the client, after receiving the first result notify event, first result data associated with the first result notify event.
10. The mobile telephone of claim 9, wherein the proxy layer comprises a main thread that is adapted to receive the function call from the client application, translate the first API into an inputoutput control (IOCTL) code, and send the IOCTL code to the driver layer.
11. The mobile telephone of claim 10, wherein the proxy layer comprises a notify thread that is adapted to receive a first notify event from the driver layer and to pass the first result notify event to the main thread.
12. The mobile telephone of claim 11, wherein the main thread is further adapted to pass the first result data to the client.
13. The mobile telephone of claim 12, wherein the main thread is further adapted to pass the first result data directly to the client.
14. The mobile telephone of claim 8, wherein the proxy layer is further adapted to asynchronously process function calls of application program interfaces (APIs) associated with functions to be performed by the radio.
15. A hardware-independent proxy layer for synchronous processing of commands in a mobile telephone, the telephone comprising the proxy layer, a hardware-specific driver layer, a client application, and a radio, the proxy layer comprising:
a main thread comprising computer executable instructions for receiving from the client application a function call of a first application program interface (API), wherein the first API is associated with a function to be performed by the radio, waiting to receive a first result notify event indicating that the function has been performed, and, after receiving the first result notify event, passing to the client first result data associated with the first result notify event; and
a notify thread comprising computer executable instructions for receiving from the driver layer a first notify event indicating that the function has been performed and passing the first result notify event to the main thread.
16. The proxy layer of claim 15, wherein the main thread further comprises computer-executable instructions for translating the first API into an inputoutput control (IOCTL) code, and sending the IOCTL code to the driver layer.
17. The proxy layer of claim 16, wherein the main thread is further adapted to pass the first result data directly to the client.
18. The proxy layer of claim 15, wherein the main thread further comprises computer-executable instructions for receiving from the client application a function call of a second API, wherein the second API is associated with the function to be performed by the radio, and
wherein the notify thread further comprises computer-executable instructions for receiving a second notify event from the driver layer that passes to the notify thread second result data associated with the second result notify event, and for conveying the second result data to the client application using a result callback function.
19. The proxy layer of claim 18, wherein the main thread further comprises computer-executable instructions for returning to the client application a first response identifier to indicate that the driver layer has accepted an operation request associated with the second API.
20. The proxy layer of claim 19, wherein the result callback function includes a second response identifier having a value that is the same as that of the first response identifier.