1461187749-14617b5d-88d1-4d68-9b28-db0b19dee33c

1. A SRAM cell structure comprising:
a first N type switch having a control terminal connected to a word line and a first terminal connected to a bit line;
a second N type switch having a control terminal connected to the word line and a first terminal connected to an inverted bit line;
a first storage node having a first terminal connected to a second terminal of the first N type switch and a floating second terminal; and
a second storage node having a first terminal connected to a second terminal of the second N type switch and a floating second terminal.
2. The SRAM cell structure according to claim 1 wherein the first N type switch is a first NMOS transistor, which has a gate electrode connected to the word line, a drain electrode connected to the bit line and a source electrode connected to the first terminal of the first storage node.
3. The SRAM cell structure according to claim 1 wherein the second first N type switch is a second NMOS transistor, which has a gate electrode connected to the word line, a drain electrode connected to the inverted bit line and a source electrode connected to the first terminal of the second storage node.
4. The SRAM cell structure according to claim 1 wherein the first storage node is a NMOS capacitor including a third NMOS transistor, and the second storage node is a NMOS capacitor including a fourth NMOS transistor.
5. The SRAM cell structure according to claim 4 wherein the gate electrodes of the third NMOS transistor and the fourth NMOS transistor are connected to an external voltage.
6. The SRAM cell structure according to claim 4 wherein the drain electrode of the third NMOS transistor is connected to the second terminal of the first N type switch, and the drain electrode of the third NMOS transistor is floating.
7. The SRAM cell structure according to claim 4 wherein the drain electrode of the fourth NMOS transistor is connected to the second terminal of the second N type switch, and the drain electrode of the fourth NMOS transistor is floating.
8. The SRAM cell structure according to claim 1 wherein complementary data are stored in the first storage node and the second storage node.
9. A static random access memory comprising:
a main control circuit for receiving multiple address signals, a clock signal and a readwrite signal, wherein the address signals includes column address signals and row address signals;
a column decoder connected to the main control circuit, wherein the column address signals are transmitted to the column decoder for controlling a bit line;
a row decoder connected to the main control circuit, wherein the row address signals are transmitted to the row decoder for controlling a word line;
a memory cell array connected to the column decoder and the row decoder;
a sense amplifier and inputoutput control circuit connected to the memory cell array; and
a hidden refresh unit connected to the main control circuit, wherein when the static random access memory is in a normal operation without refresh mode, the hidden refresh unit performs only a normal writeread operation within one clock cycle, and when the static random access memory is in a normal operation with refresh mode, the hidden refresh unit performs a writeread operation followed by a refresh operation on the memory cell array within one clock cycle.
10. The static random access memory according to claim 9 wherein the memory cell array includes multiple memory cells, and each memory cell includes:
a first N type switch having a control terminal connected to a word line and a first terminal connected to a bit line;
a second N type switch having a control terminal connected to the word line and a first terminal connected to an inverted bit line;
a first storage node having a first terminal connected to a second terminal of the first N type switch; and
a second storage node having a first terminal connected to a second terminal of the second N type switch.
11. The static random access memory according to claim 10 wherein the first N type switch is a first NMOS transistor, which has a gate electrode connected to the word line, a drain electrode connected to the bit line and a source electrode connected to the first terminal of the first storage node.
12. The static random access memory according to claim 10 wherein the second first N type switch is a second NMOS transistor, which has a gate electrode connected to the word line, a drain electrode connected to the inverted bit line and a source electrode connected to the first terminal of the second storage node.
13. The static random access memory according to claim 10 wherein the first storage node has a floating second terminal, and the second storage node has a floating second terminal.
14. The static random access memory according to claim 10 wherein the first storage node is a NMOS capacitor including a third NMOS transistor, and the second storage node is a NMOS capacitor including a fourth NMOS transistor.
15. The static random access memory according to claim 14 wherein the gate electrodes of the third NMOS transistor and the fourth NMOS transistor are connected to an external voltage.
16. The static random access memory according to claim 14 wherein the drain electrode of the third NMOS transistor is connected to the second terminal of the first N type switch, and the drain electrode of the third NMOS transistor is floating.
17. The static random access memory according to claim 14 wherein the drain electrode of the fourth NMOS transistor is connected to the second terminal of the second N type switch, and the drain electrode of the fourth NMOS transistor is floating.
18. The static random access memory according to claim 10 wherein complementary data are stored in the first storage node and the second storage node.
19. The static random access memory according to claim 9 wherein the hidden refresh unit includes:
an oscillator for generating an oscillation clock signal having a lower frequency than the clock signal; and
a flag register connected to the oscillator for receiving the oscillation clock signal, wherein in response to a first voltage level of the oscillation clock, the flag register is set and generates a setting signal to the main control circuit, in response to the setting signal, the main control circuit automatically generates a refresh enabling signal and a corresponding refresh address to the row decoder so as to perform the refresh operation, and the refresh enabling signal is transmitted to the flag register to reset the flag register.

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 of importing scanned image data into a production workflow, comprising:
receiving an configuration file having information describing a plurality of image processing plugins;
registering zero or more plugins for each a plurality of event triggers specified in the configuration file;
sequentially initiating the plurality of event triggers to invoke respective registered plugins; and
processing the scanned images using the invoked plugins.
2. The method of claim 1, further comprising loading to memory configuration parameters for a production scanning job.
3. The method of claim 2, further comprising receiving source image directory information that identifies a source directory from which images are to be imported for processing.
4. The method of claim 3, further comprising receiving destination directory information that identifies a destination directory to which processed images will be exported.
5. The method of claim 4, further comprising loading into memory metadata related to images to be processed.
6. The method of claim 1, further comprising invoking at least one Import plugin that generates a list of image objects that represent images to be processed.
7. The method of claim 6, further comprising invoking at least one Pre-Scan plugin that performs operations that do not require image data.
8. The method of claim 7, further comprising invoking at least on In-Scan plugin that processes an image to extract data specified in the In-Scan plugin definition.
9. The method of claim 8, further comprising invoking at least one Post-Scan plugin that evaluates data extracted by the In-Scan plugin and copies source image data into a destination directory.
10. The method of claim 1, wherein the plurality of event triggers comprises one or more of an Import trigger, a Pre-scan trigger, an In-scan trigger, and a Post-scan trigger.
11. The method of claim 1, wherein the configuration file associates plugins with event triggers and an order in which plugins associated with a common trigger are to be invoke relative to each other when the common trigger occurs.
12. A system that facilitates importing scanned image data into a production workflow, comprising:
a processor that receives a configuration file that describes a plurality of image processing plugins, and generates trigger event messages;
a memory that stores the configuration file; and
a plugin handler that receives a trigger event messages from the processor and invokes one or more plugins registered to the trigger event message.
13. The system of claim 12, wherein the trigger event message is at least one of an Import trigger event, a Pre-scan trigger event, an In-scan trigger event, and a Post-scan trigger event.
14. The system of claim 13, wherein the plugin handler invokes at least one Import plugin that generates a list of image objects that represent images to be processed.
15. The system of claim 14, wherein the plugin handler invokes at least one Pre-Scan plugin that performs operations that do not require image data.
16. The system of claim 15, wherein the plugin handler invokes at least on In-Scan plugin that processes an image to extract data specified in the In-Scan plugin definition.
17. The system of claim 16, wherein the In-Scan plugin definition specifies a type of data to be extracted comprising at least one of TIFF-formatted data, jpeg-formatted data, pdf-formatted data, ftp-formatted data, and ZIP-formatted data.
18. The system of claim 16, wherein the plugin handler invokes at least one Post-Scan plugin that evaluates data extracted by the In-Scan plugin and copies source image data into a destination directory.
19. The system of claim 12, wherein the plugin handler invokes plugins having a common event trigger in an order specified in the configuration file when the common trigger occurs.
20. A scanning platform, comprising:
a scanner that generates electronic images of documents for information retrieval;
a memory that stores a received configuration file, which defines an action for at least one plugin that allows the plugin to execute custom code that is at least one of a script or compiled code; and
a plugin handler that recognizes an event trigger and invokes one or more plugins registered to the event trigger to process image data.

1461187737-4ad59f08-d750-4fa5-aabf-0ba87cb4e464

1. An optical fiber cord which is a single core optical fiber cord having an outer diameter of 1.2 mm or less, and has a structure in which an optical fiber core wire having a resin coating is provided at the center, a tensile-strength-fiber layer is provided around the outer periphery of the optical fiber core wire, and a coating layer is further provided around the outer periphery of the tensile-strength-fiber layer,
wherein the coating layer is composed of a non-halogen fire-retardant resin, and
wherein the coating layer is formed by a composition in which 18-60 parts by mass of ammonium polyphosphate is blended with 100 parts by mass of a resin component containing at least one selected from the group consisting of polyamide-series thermoplastic resins, polyamide elastomer-series thermoplastic resins and polyester elastomer-series thermoplastic resins, and wherein the bending modulus of the resin component of the coating layer is 500 to 1,300 MPa.
2. The optical fiber cord as claimed in claim 1, wherein the ammonium polyphosphate is one that has been surface-treated.
3. An optical fiber cord which is a single core optical fiber cord having an outer diameter of 1.2 mm or less, and has a structure in which an optical fiber core wire having a resin coating is provided at the center, a tensile-strength-fiber layer is provided around the outer periphery of the optical fiber core wire, and a coating layer is further provided around the outer periphery of the tensile-strength-fiber layer,
wherein the coating layer is composed of a non-halogen fire-retardant resin, and
wherein the coating layer is formed by a composition in which 18-60 parts by mass of a fire retardant, which consists of ammonium polyphosphate and a nitrogen-containing compound, is blended with 100 parts by mass of a resin component containing at least one selected from the group consisting of polyamide-series thermoplastic resins, polyamide elastomer-series thermoplastic resins and polyester elastomer-series thermoplastic resins, and wherein the bending modulus of the resin component of the coating layer is 500 to 1,300 MPa.
4. The optical fiber cord as claimed in claim 3, wherein the ratio of said ammonium polyphosphate to the total amount of said ammonium polyphosphate and said nitrogen-containing compound is 50 mass % or more.
5. The optical fiber cord as claimed in claim 4, wherein said ammonium polyphosphate is one that has been surface-treated.
6. The optical fiber cord as claimed in claim 3, wherein the nitrogen-containing compound is at least one selected from the group consisting of melamine cyanurate, polyphosphoric acid amide, tris-(2hydroxyethyl) isocyanate and melamine.

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. One or more non-transitory computer-storage media storing computer-useable instructions that, when used by a computing device, cause the computing device to perform a method in a clinical computing environment for initiating a technical support session between a client device and at least one support device, the method comprising:
receiving a request to initiate a technical support session including a technical support representative for a client device to aid a clinician employing a clinical application;
receiving clinical context information associated with the client device, wherein the clinical context information comprises data that aids the technical support representative in assisting the clinician during the technical support session;
automatically accessing a profile for each technical support representative and information about each of the at least one support device being operated by each technical support representative, wherein the profile of each technical support representative comprises capabilities of the technical support representative to assist the clinician who is requesting the technical support session;
determining the at least one skilled technical support representative for the technical support session based on matching the capabilities in the profile of each support representative, information about the associated support device being operated by each technical support representative, and the clinical context information associated with the client device;
accessing by the queue manager, a database maintained by the queue manager and containing the security authorization of each of the at least one skilled technical support representative, wherein the security authorization indicates whether each of the at least one skilled technical support representative is authorized to assist the clinician who is requesting the technical support session;
determining by the queue manager device, the at least one authorized technical support representative for the technical support session of the at least one skilled technical support representative based on the at least one skilled technical support representative’s security authorization in the database to enter a technical support session and to assist the clinician who is requesting the technical support session;
determining by the queue manager device, the at least one support device for the technical support session being operated by the at least one authorized technical support representative for the technical support session; and
initiating the technical support session between the client device and the at least one support device.
2. The one or more non-transitory computer-storage media of claim 1, further comprising providing the clinical context information to the at least one support device.
3. The one or more non-transitory computer-storage media of claim 1, wherein initiating a technical support session further comprises comparing the clinical context information associated with the client device with the information about the at least one support device.
4. The one or more non-transitory computer-storage media of claim 1, wherein the information about the at least one support device comprises a profile for each support representative operating the at least one support device.
5. The one or more non-transitory computer-storage media of claim 1, wherein the technical support session comprises a real-time session.
6. The one or more non-transitory computer-storage media of claim 1, wherein initiating a technical support session comprises:
communicating a session request to the at least one support device;
receiving a session acceptance from at least one of the at least one support device; and
initiating a technical support session between the client device and the at least one of the at least one support device.
7. The one or more non-transitory computer-storage media of claim 6, wherein communicating a session request to the at least one support device further comprises communicating clinical context information to the at least one support device.
8. A method in a clinical computing environment for providing technical support to a client device, the method comprising:
receiving by a queue manager device, clinical context information associated with a client device;
automatically accessing by the queue manager device, a profile for each technical support representative and information about each of the at least one support device being operated by each technical support representative, wherein the profile of each technical support representative comprises capabilities of the technical support representative to assist the clinician who is requesting the technical support session;
determining by the queue manager device, the skilled technical support representative for the technical support session based on matching the capabilities in the profile of each technical support representative, information about the at least one support device being operated by each technical support representative, and the clinical context information associated with the client device;
accessing by the queue manager, a database maintained by the queue manager and containing the security authorization of each of the at least one skilled technical support representative, wherein the security authorization indicates whether each of the at least one skilled technical support representative is authorized to enter a technical support session and assist the clinician who is requesting the technical support session;
determining by the queue manager device, the at least one authorized technical support representative for the technical support session of the at least one skilled technical support representative based on the at least one skilled technical support representative’s security authorization in the database to enter a technical support session and to assist the clinician who is requesting the technical support session;
determining by the queue manager device, the at least one support device for the technical support session being operated by the at least one authorized technical support representative for the technical support session;
in response to determining the support device for the technical support session, communicating a session request to the at least one support device, wherein communicating a session request to the at least one support device further comprises communicating clinical context information to the at least one support device;
presenting the clinical context information on the at least one support device in one or more of an incoming queries area and a support request window before one of the at least one authorized technical support representative responds to the session request and the technical support session is initiated; and
moving the clinical context information from one or more of the incoming queries area and the support request window to an ongoing session area on the at least one support device after the at least one authorized technical support representative responds to the session request and the technical support session is initiated.
9. The method of claim 8, further comprising:
providing the technical support session between the client device and the at least one support device.
10. The method of claim 9, wherein the technical support session comprises a real-time session.
11. A method in a clinical computing environment for requesting a technical support session between a client device and at least one support device, the method comprising:
receiving from the client device a command from a clinician to automatically request the technical support session including a technical support representative to aid the clinician employing a clinical application;
directly upon receiving the command, automatically accessing clinical context information from the client device, wherein the clinical context information comprises data that aids the technical support representative in assisting the clinician during the technical support session including at least one of a characteristic of the client device, a characteristic of a clinical application, and information pertaining to the clinician;
communicating a request for the technical support session from the client device to a queue manager device;
communicating from the client device to the queue manager device, the clinical context information;
automatically accessing by the queue manager device, a profile for each technical support representative and information about each of the at least one support device being operated by each technical support representative, wherein the profile of each technical support representative comprises capabilities of the technical support representative to assist the clinician who is requesting the technical support session;
determining by the queue manager device, the at least one skilled technical support representative for the technical support session based on matching the capabilities in the profile of each technical support representative, information about the at least one support device being operated by each technical support representative, and the communicated clinical context information from the client device;
accessing by the queue manager, a database maintained by the queue manager and containing the security authorization of each of the at least one skilled technical support representative, wherein the security authorization indicates whether each of the at least one skilled technical support representative is authorized to enter a technical support session and assist the clinician who is requesting the technical support session;
determining by the queue manager device, the at least one authorized technical support representative for the technical support session of the at least one skilled technical support representative based on the at least one skilled technical support representative’s security authorization in the database to enter a technical support session and to assist the clinician who is requesting the technical support session;
determining by the queue manager device, the at least one support device for the technical support session being operated by the at least one authorized technical support representative for the technical support session;
initiating the technical support session between the client device and the at least one support device in response to determining the at least one support device for the technical support session; and
communicating the clinical context information to the at least one support device in response to the initiation of the technical support session.
12. The method of claim 11, wherein the technical support session comprises a real-time session.
13. The method of claim 11, wherein the clinical context information comprises at least one of an end user’s identification, an end user’s location, an end user’s role, an identification of a clinical application, a name of a clinical application, a current tab within a clinical application, a current location within a clinical application, a physical location of the client device, a software characteristic of the client device, and a hardware characteristic of the client device.