1461160212-9c70dac5-85ce-43b0-9781-4f4521c41312

I claim:

1. A supported noble metal hydrodechlorination catalyst wherein the noble metal, which is in the zero valent state, predominantly resides adjacent the surface of the support and wherein a predominant amount of the noble metal therein is visible under a microscope having a resolution of about 5 and is in the particle size range of from about 30 to about 200 .
2. A catalyst as claimed in claim 1 wherein the support is an oxidic support.
3. A catalyst as claimed in claim 1 wherein the noble metal is a Group VIII noble metal.
4. A catalyst as claimed in claim 1 wherein the noble metal is selected from the group consisting of platinum and palladium.
5. A catalyst as claimed in claim 1 wherein the support is an oxidic support, and the noble metal is selected from the group consisting of platinum and palladium.
6. A catalyst as claimed in claim 1 wherein the support is a pelletized oxidic support, and the noble metal is selected from the group consisting of platinum and palladium.

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 system, comprising:
a processor-implemented tool configured to generate a layout of an integrated circuit (IC) die;
at least one non-transitory machine readable storage medium, including a first portion encoded with a first gate-level description of first and second circuit patterns to be formed on first and second integrated circuit (IC) dies, respectively, and a second portion encoded with a second gate level description of the first and second circuit patterns received from the processor implemented tool, wherein the second gate level description includes power and ground ports, and the first gate level description does not include power and ground ports;
a processor-implemented first verification module for comparing the first and second gate level descriptions and outputting a verified second gate-level description of the first and second circuit patterns.
2. The system of claim 1, wherein the first verification module includes a first parser module that receives the first and second gate level descriptions of the first and second IC dies and generates a source parsing tree having respective leaves representing each port of the first and second IC dies according to the first gate level description, and a target parsing tree having respective leaves representing each port of the first and second IC dies according to the second gate level description, wherein the first verification module compares each leaf of the target parsing tree to a corresponding leaf of the source parsing tree.
3. The system of claim 2, wherein the first parser module generates:
a source connection list based on the first gate level description, the source connection list including, for each connection between the first IC die and the second IC die, a source die, a destination die, a source port, and a destination port; and
a target connection list based on the second gate level description, the target connection list including, for each connection between the first IC die and the second IC die, a source die, a destination die, a source port, and a destination port.
4. The system of claim 2, wherein the first parser module generates and stores the following parameters in leaves of the source parsing tree:
for each port of the first die or second die identified as a source port of a connection in the source connection list, a corresponding source list destination die and source list destination port;
for each port of the first die or second die identified as a destination port of a connection in the source connection list, a corresponding source list source die and source list source port; and wherein the first parser module generates and stores the following parameters in leaves of the target parsing tree:
for each port of the first die or second die identified as a source port of a connection in the target connection list, a corresponding target list destination die and target list destination port; and
for each port of the first die or second die identified as a destination port of a connection in the target connection list, a corresponding target list source die and target list source port.
5. The system of claim 4, wherein the first parser module generates:
a source connection list based on the first gate level description, the source connection list including, for each connection between the first IC die and the second IC die, a source die, a destination die, a source port, and a destination port; and
a target connection list based on the second gate level description, the target connection list including, for each connection between the first IC die and the second IC die, a source die, a destination die, a source port, and a destination port; and
wherein the first verification module further comprises a compare module that generates and outputs the error report if, for a given leaf of the source parsing tree:
the target list source die of the corresponding leaf of the target parsing tree is different from the source list source die of the given leaf,
the target list source port of the corresponding leaf of the target parsing tree is different from the source list source port of the given leaf,
the target list destination die of the corresponding leaf of the target parsing tree is different from the source list destination die of the given leaf, or
the target list destination port of the corresponding leaf of the target parsing tree is different from the source list destination port of the given leaf.
6. The system of claim 5, further comprising a correction module that corrects an error in at least one of the group consisting of the target list source die, target list source port, target list destination port, and the target list destination die if the compare module generates an error report.
7. The system of claim 1, wherein:
the at least one storage medium includes a third portion for storing the verified second gate level description;
the at least one storage medium includes a fourth portion for storing a first microbump mapping data received from the processor implemented tool, the first microbump mapping data identifying connections between ports of the first die and ports of the second die, the first microbump mapping data having a different format from the verified second gate level description; and
the system further comprises a second verification module for comparing the first microbump mapping data to the verified second gate level description and outputting an error report if the first microbump mapping data has an error, the second verification module outputting verified microbump mapping data.
8. The system of claim 7, wherein the second verification module includes a second parser module that receives the verified second gate level description and the first microbump mapping data and generates a source parsing tree having respective leaves representing each port of the first and second IC dies according to the verified second gate level description, and a target parsing tree having respective leaves representing each port of the first and second IC dies according to the microbump mapping data, wherein the second verification module compares each leaf of the target parsing tree to a corresponding leaf of the source parsing tree.
9. The system of claim 8, wherein the second parser module generates:
a source connection list based on the verified second gate level description, the source connection list including, for each connection between the first IC die and the second IC die, a source die, a destination die, a source port, and a destination port; and
a target connection list based on the microbump mapping data, the target connection list including, for each connection between the first IC die and the second IC die, a source die, a destination die, a source port, and a destination port.
10. The system of claim 8, wherein the second parser module generates and stores the following parameters in leaves of the source parsing tree:
for each port of the first die or second die identified as a source port of a connection in the source connection list, a corresponding source list destination die and source list destination port;
for each port of the first die or second die identified as a destination port of a connection in the source connection list, a corresponding source list source die and source list source port; and wherein the first parser module generates and stores the following parameters in leaves of the target parsing tree:
for each port of the first die or second die identified as a source port of a connection in the target connection list, a corresponding target list destination die and target list destination port; and
for each port of the first die or second die identified as a destination port of a connection in the target connection list, a corresponding target list source die and target list source port.
11. The system of claim 10, wherein the second parser module generates:
a source connection list based on the verified second gate level description, the source connection list including, for each connection between the first IC die and the second IC die, a source die, a destination die, a source port, and a destination port; and
a target connection list based on the microbump mapping data, the target connection list including, for each connection between the first IC die and the second IC die, a source die, a destination die, a source port, and a destination port; and
wherein the second verification module further comprises a compare module that generates and outputs the error report if, for a given leaf of the source parsing tree:
the target list source die of the corresponding leaf of the target parsing tree is different from the source list source die of the given leaf,
the target list source port of the corresponding leaf of the target parsing tree is different from the source list source port of the given leaf,
the target list destination die of the corresponding leaf of the target parsing tree is different from the source list destination die of the given leaf, or
the target list destination port of the corresponding leaf of the target parsing tree is different from the source list destination port of the given leaf.
12. The system of claim 11, further comprising a correction module that corrects an error in at least one of the group consisting of the target list source die, target list source port, target list destination port, and the target list destination die if the compare module generates an error report.
13. The system of claim 7, wherein:
the at least one storage medium includes a fifth portion for storing a translated microbump mapping data received from a translation tool, the translated microbump mapping data identifying connections between the ports of the first die and the ports of the second die, the translated microbump mapping data having a different format from the first microbump mapping data and from the verified second gate level description; and
the system further comprises a third verification module for comparing the translated microbump mapping data to the verified second gate level description and determining whether the translated microbump mapping data has an error, the third verification module outputting verified translated microbump mapping data.
14. A method, comprising:
providing a first gate-level description of first and second circuit patterns to be formed on first and second integrated circuit (IC) dies, respectively, wherein the first gate level description does not include power or ground ports of the IC dies;
using a computer implemented tool to generate a second gate level description of the first and second circuit patterns, wherein the second gate level description includes power and ground ports of the IC dies;
comparing the first and second gate level descriptions and outputting a verified second gate-level description of the first and second circuit patterns if the second gate level description has no error.
15. The method of claim 14, further comprising:
generating a microbump mapping data using the computer implemented tool, the microbump mapping data identifying connections between ports of the first die and ports of the second die, the microbump mapping data having a different format from the verified second gate level description;
comparing the microbump mapping data to the verified second gate level description and outputting a verified microbump mapping data if the microbump mapping data has no error; and
performing inter-die layout-versus-schematic verification based on the verified second gate level description and the verified microbump mapping data.
16. A system comprising:
at least one non-transitory machine readable storage medium, including a portion for storing a verified gate level description of a first IC die and a second IC die,
a processor-implemented tool configured to access the verified gate level description of the first and second IC dies, and for generating a first microbump mapping data identifying connections between ports of the first IC die and ports of the second IC die, the first microbump mapping data having a different format from the verified gate level description; and
a verification module for comparing the first microbump mapping data to the verified second gate level description and outputting an error report if the first microbump mapping data has an error, the second verification module outputting verified microbump mapping data.
17. The system of claim 16, wherein the verification module comprises
a first parser module that receives the verified gate level descriptions of the first and second IC dies and generates a source parsing tree having respective leaves representing each port of the first and second IC dies according to the verified gate level descriptions, and a target parsing tree having respective leaves representing each port of the first and second IC dies according to the first microbump mapping data, wherein the verification module compares each leaf of the target parsing tree to a corresponding leaf of the source parsing tree.
18. The system of claim 17, wherein the verification module generates:
a source connection list based on the verified gate level description, the source connection list including, for each connection between the first IC die and the second IC die, a source die, a destination die, a source port, and a destination port; and
a target connection list based on the first microbump mapping data, the target connection list including, for each connection between the first IC die and the second IC die, a source die, a destination die, a source port, and a destination port.
19. The system of claim 17, wherein the verification module further comprises a compare module that generates and outputs the error report if, for a given leaf of the source parsing tree:
a target list source die of a corresponding leaf of the target parsing tree is different from a source list source die of the given leaf,
a target list source port of a corresponding leaf of the target parsing tree is different from a source list source port of the given leaf,
a target list destination die of a corresponding leaf of the target parsing tree is different from a source list destination die of the given leaf, or
a target list destination port of a corresponding leaf of the target parsing tree is different from a source list destination port of the given leaf.
20. The system of claim 19, further comprising a correction module that corrects an error in at least one of the group consisting of the target list source die, target list source port, target list destination port, and the target list destination die if the compare module generates an error report.

1461160203-ba8cf55e-19fb-4a0c-9c1a-b5fd6acf03a3

1. A method of monitoring, recording and analyzing information associated with use of an ambulance cot comprising providing an ambulance cot, wherein said ambulance cot comprises a tip angle monitoring, recording and alert system, wherein said system comprises a controller and a memory component, wherein said controller records information acquired from said tip angle monitoring, recording and alert system into said memory component.
2. The method of claim 1, wherein said information comprises information regarding when said cot is removed from an ambulance andor when said cot is loaded into an ambulance.
3. The method of claim 1, wherein said information comprises information regarding whether a cot was taken up andor down a surface.
4. The method of claim 1, wherein said information comprises information regarding whether said cot traversed a surface in a foot-first or a head-first orientation.
5. The method of claim 1, wherein said information comprises identification of a specific time at which a subject is placed upon andor removed from said cot.
6. The method of claim 1, wherein said information is utilized in an effort to assist a user of said cot to operate said cot according to one or more identified operating procedures.
7. The method of claim 1, wherein said information associated with use of an ambulance cot is analyzed for a plurality of users.
8. The method of claim 1, wherein said tip angle monitoring, recording and alert system comprises an ultrasonic sensor.
9. The method of claim 8, wherein said information associated with use of an ambulance cot comprises cot height measured by said ultrasonic sensor.
10. The method of claim 1, wherein said tip angle monitoring, recording and alert system comprises an accelerometer.
11. method of claim 10, wherein said information associated with use of an ambulance cot comprises angle of movement of said cot measured by said accelerometer.
12. The method of claim 1, wherein said controller of said tip angle monitoring, recording and alert system records cot operational use information into said memory component of said tip angle monitoring, recording and alert system.
13. The method of claim 12, wherein said cot operational use information comprises information selected from the group consisting of cot angle, cot height, cot load weight, calendar date, and time.
14. The method of claim 1, wherein said ambulance cot comprises a hydraulic system, wherein said hydraulic system comprises a cylinder powered by a hydraulic unit.

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 system for providing a voice dialogue in a telephone network, said system comprising:
a switching point connected to a communication device;
a service control point connected to said switching point;
a voice extensible markup language browser connected to said switching point; and
a converter connected to said service control point and said voice extensible markup language browser,
wherein said converter communicates with said service control point using a call control protocol, and
wherein said converter is adapted to convert said call control protocol to a voice extensible markup language.
2. The system in claim 1, wherein said converter comprises a Hypertext Transfer Protocol (HTTP) server.
3. The system in claim 1, wherein said converter comprises an Advanced Intelligent Network Session Coordinator.
4. The system in claim 1, wherein said converter comprises a Call Control Protocol to Voice Extensible Markup Language (XML) Converter.
5. The system in claim 1, wherein said service control point is connected to said switching point over an advanced intelligent network.
6. The system in claim 1, wherein said voice markup language browser comprises an intelligent peripheral.
7. The system in claim 1, wherein said call control protocol is not publicly available and said voice extensible markup language is publicly available.
8. A system for providing a voice dialogue in a telephone network, said system comprising:
a switching point connected to a communication device;
a service control point connected to said switching point; and
a voice processor connected to said service control point and to said switching point,
wherein said voice processor communicates with said service control point using a call control protocol,
wherein said voice processor comprises:
a voice extensible markup language browser connected to said switching point; and
a converter connected to said service control point and said voice markup language browser,

wherein said converter is adapted to convert said call control protocol to a voice extensible markup language.
9. The system in claim 8, wherein said converter comprises a Hypertext Transfer Protocol (HTTP) server.
10. The system in claim 8, wherein said converter comprises an Advanced Intelligent Network Session Coordinator.
11. The system in claim 8, wherein said converter comprises a Call Control Protocol to Voice Extensible Markup Language (XML) Converter.
12. The system in claim 8, wherein said service control point is connected to said switching point over an advanced intelligent network.
13. The system in claim 8, wherein said voice markup language browser comprises an intelligent peripheral.
14. The system in claim 8, wherein said call control protocol is not publicly available and said voice extensible markup language is publicly available.
15. A method of providing a voice dialogue in a telephone network, said method comprising:
initiating a telephone call;
routing said telephone call to a voice processor based upon a call control protocol; and
converting said call control protocol to a voice extensible markup language.
16. The method in claim 15, wherein said converting process comprises using a Hypertext Transfer Protocol (HTTP) server.
17. The method in claim 15, wherein said converting process comprises using an Advanced Intelligent Network Session Coordinator.
18. The method in claim 15, wherein said converting process comprises using a Call Control Protocol to Voice Extensible Markup Language (XML) Converter.
19. The method in claim 15, wherein said voice processor provides voice communications between a telephone user and a machine.
20. The method in claim 15, wherein said routing process routes said telephone call to a voice extensible markup language browser and said converting process is performed by a converter connected to said browser.
21. The method in claim 15, wherein said call control protocol is not publicly available and said voice extensible markup language is publicly available.
22. A method of providing a voice dialogue in a telephone network, said method comprising:
directing a telephone call to a switch;
requesting, by said switch, routing instructions from a control point;
routing said telephone call to a voice Extensible Markup Language (XML) browser according to said routing instructions;
forwarding a request for voice instructions from said XML browser to a call control protocol to voice XML converter;
converting said request for voice instructions to said call control protocol using said converter;
forwarding said request for voice instructions from said converter to said control point;
returning voice instructions from said control point to said converter;
converting said voice instructions from said call control protocol to said voice XML;
returning voice instructions from said converter to said voice XML browser; and
executing said voice instructions using said XML browser.
23. The method in claim 22, wherein said converting process comprises using a Hypertext Transfer Protocol (HTTP) server.
24. The method in claim 22, wherein said converting process comprises using an Advanced Intelligent Network Session Coordinator.
25. The method in claim 22, wherein said converting process comprises using a Call Control Protocol to Voice XML Converter.
26. The method in claim 22, wherein said voice processor provides voice communications between a telephone user and a machine.
27. The method in claim 22, wherein said routing process routes said telephone call to a voice extensible markup language browser and said converting process is performed by a converter connected to said browser.
28. The method in claim 22, wherein said call control protocol is not publicly available and said voice extensible markup language is publicly available.